MPLS-LPS-MIB

Unsigned32 (1..4294967295)

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.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..32) · OCTET STRING · hint 255t

Textual name that represents the MPLS-TP linear protection domain. It facilitates easy administrative identification of each protection domain.

INTEGER1 = psc2 = aps · Integer32

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. ⓘ

INTEGER1 = onePlusOneUnidirectional2 = oneColonOneBidirectional3 = onePlusOneBidirectional · Integer32

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). ⓘ

INTEGER1 = nonrevertive2 = revertive · Integer32

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). ⓘ

Unsigned32 (0..100)

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). ⓘ

Unsigned32 (2..10) · seconds

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). ⓘ

Unsigned32 (2..10) · seconds

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). ⓘ

Unsigned32 (5..12) · minutes

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). ⓘ

Unsigned32 (0..100) · deciseconds

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). ⓘ

Unsigned32 (1..20) · seconds

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). ⓘ

Unsigned32 (1000..20000) · microseconds

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). ⓘ

MplsLpsCommand1 = noCmd2 = clear3 = lockoutOfProtection4 = forcedSwitch5 = manualSwitchToWork6 = manualSwitchToProtect7 = exercise8 = freeze9 = clearfreezeThis command allows a user to perform any action over a protection domain. If the protection command cannot be executed because a request of equal or higher priority is in effect, an inconsistentValue error is returned. The command values are as follows: noCmd This value should be returned by a read request when no command has been written to the object in question since initialization. This value may not be used in a write operation. If noCmd is used in a write operation, a wrongValue error is returned. clear Clears all of the commands listed below for the protection domain. lockoutOfProtection Prevents switching traffic to the protection path. forcedSwitch Switches traffic from the working path to the protection path. manualSwitchToWork Switches traffic from the protection path to the working path. manualSwitchToProtect Switches traffic from the working path to the protection path. exercise Used to verify the correct operation of the PSC communication and the integrity of the protection path. This command is not applicable to the PSC mode. freeze This command freezes the protection state and is a local command that is not signaled to the remote node. This command is not applicable to the PSC mode. clearfreeze Clears the local freeze. This command is not applicable to the PSC mode.Reference: Sections 3.1 and 3.2 of RFC 6378 and Sections 4.3 and 6 of RFC 7271 · Integer32

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). ⓘ

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime at the time the row was created.

RowStatus1 = active2 = notInService3 = notReady4 = createAndGo5 = createAndWait6 = destroyThe RowStatus textual convention is used to manage the creation and deletion of conceptual rows, and is used as the value of the SYNTAX clause for the status column of a conceptual row (as described in Section 7.7.1 of [2].) The status column has six defined values: - `active', which indicates that the conceptual row is available for use by the managed device; - `notInService', which indicates that the conceptual row exists in the agent, but is unavailable for use by the managed device (see NOTE below); 'notInService' has no implication regarding the internal consistency of the row, availability of resources, or consistency with the current state of the managed device; - `notReady', which indicates that the conceptual row exists in the agent, but is missing information necessary in order to be available for use by the managed device (i.e., one or more required columns in the conceptual row have not been instanciated); - `createAndGo', which is supplied by a management station wishing to create a new instance of a conceptual row and to have its status automatically set to active, making it available for use by the managed device; - `createAndWait', which is supplied by a management station wishing to create a new instance of a conceptual row (but not make it available for use by the managed device); and, - `destroy', which is supplied by a management station wishing to delete all of the instances associated with an existing conceptual row. Whereas five of the six values (all except `notReady') may be specified in a management protocol set operation, only three values will be returned in response to a management protocol retrieval operation: `notReady', `notInService' or `active'. That is, when queried, an existing conceptual row has only three states: it is either available for use by the managed device (the status column has value `active'); it is not available for use by the managed device, though the agent has sufficient information to attempt to make it so (the status column has value `notInService'); or, it is not available for use by the managed device, and an attempt to make it so would fail because the agent has insufficient information (the state column has value `notReady'). NOTE WELL This textual convention may be used for a MIB table, irrespective of whether the values of that table's conceptual rows are able to be modified while it is active, or whether its conceptual rows must be taken out of service in order to be modified. That is, it is the responsibility of the DESCRIPTION clause of the status column to specify whether the status column must not be `active' in order for the value of some other column of the same conceptual row to be modified. If such a specification is made, affected columns may be changed by an SNMP set PDU if the RowStatus would not be equal to `active' either immediately before or after processing the PDU. In other words, if the PDU also contained a varbind that would change the RowStatus value, the column in question may be changed if the RowStatus was not equal to `active' as the PDU was received, or if the varbind sets the status to a value other than 'active'. Also note that whenever any elements of a row exist, the RowStatus column must also exist. To summarize the effect of having a conceptual row with a status column having a SYNTAX clause value of RowStatus, consider the following state diagram: STATE +--------------+-----------+-------------+------------- | A | B | C | D | |status col.|status column| |status column | is | is |status column ACTION |does not exist| notReady | notInService| is active --------------+--------------+-----------+-------------+------------- set status |noError ->D|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndGo |inconsistent- | | | | Value| | | --------------+--------------+-----------+-------------+------------- set status |noError see 1|inconsist- |inconsistent-|inconsistent- column to | or | entValue| Value| Value createAndWait |wrongValue | | | --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError column to | Value| entValue| | active | | | | | | or | | | | | | | |see 2 ->D|see 8 ->D| ->D --------------+--------------+-----------+-------------+------------- set status |inconsistent- |inconsist- |noError |noError ->C column to | Value| entValue| | notInService | | | | | | or | | or | | | | | |see 3 ->C| ->C|see 6 --------------+--------------+-----------+-------------+------------- set status |noError |noError |noError |noError ->A column to | | | | or destroy | ->A| ->A| ->A|see 7 --------------+--------------+-----------+-------------+------------- set any other |see 4 |noError |noError |see 5 column to some| | | | value | | see 1| ->C| ->D --------------+--------------+-----------+-------------+------------- (1) goto B or C, depending on information available to the agent. (2) if other variable bindings included in the same PDU, provide values for all columns which are missing but required, and all columns have acceptable values, then return noError and goto D. (3) if other variable bindings included in the same PDU, provide legal values for all columns which are missing but required, then return noError and goto C. (4) at the discretion of the agent, the return value may be either: inconsistentName: because the agent does not choose to create such an instance when the corresponding RowStatus instance does not exist, or inconsistentValue: if the supplied value is inconsistent with the state of some other MIB object's value, or noError: because the agent chooses to create the instance. If noError is returned, then the instance of the status column must also be created, and the new state is B or C, depending on the information available to the agent. If inconsistentName or inconsistentValue is returned, the row remains in state A. (5) depending on the MIB definition for the column/table, either noError or inconsistentValue may be returned. (6) the return value can indicate one of the following errors: wrongValue: because the agent does not support notInService (e.g., an agent which does not support createAndWait), or inconsistentValue: because the agent is unable to take the row out of service at this time, perhaps because it is in use and cannot be de-activated. (7) the return value can indicate the following error: inconsistentValue: because the agent is unable to remove the row at this time, perhaps because it is in use and cannot be de-activated. (8) the transition to D can fail, e.g., if the values of the conceptual row are inconsistent, then the error code would be inconsistentValue. NOTE: Other processing of (this and other varbinds of) the set request may result in a response other than noError being returned, e.g., wrongValue, noCreation, etc. Conceptual Row Creation There are four potential interactions when creating a conceptual row: selecting an instance-identifier which is not in use; creating the conceptual row; initializing any objects for which the agent does not supply a default; and, making the conceptual row available for use by the managed device. Interaction 1: Selecting an Instance-Identifier The algorithm used to select an instance-identifier varies for each conceptual row. In some cases, the instance- identifier is semantically significant, e.g., the destination address of a route, and a management station selects the instance-identifier according to the semantics. In other cases, the instance-identifier is used solely to distinguish conceptual rows, and a management station without specific knowledge of the conceptual row might examine the instances present in order to determine an unused instance-identifier. (This approach may be used, but it is often highly sub-optimal; however, it is also a questionable practice for a naive management station to attempt conceptual row creation.) Alternately, the MIB module which defines the conceptual row might provide one or more objects which provide assistance in determining an unused instance-identifier. For example, if the conceptual row is indexed by an integer-value, then an object having an integer-valued SYNTAX clause might be defined for such a purpose, allowing a management station to issue a management protocol retrieval operation. In order to avoid unnecessary collisions between competing management stations, `adjacent' retrievals of this object should be different. Finally, the management station could select a pseudo-random number to use as the index. In the event that this index was already in use and an inconsistentValue was returned in response to the management protocol set operation, the management station should simply select a new pseudo-random number and retry the operation. A MIB designer should choose between the two latter algorithms based on the size of the table (and therefore the efficiency of each algorithm). For tables in which a large number of entries are expected, it is recommended that a MIB object be defined that returns an acceptable index for creation. For tables with small numbers of entries, it is recommended that the latter pseudo-random index mechanism be used. Interaction 2: Creating the Conceptual Row Once an unused instance-identifier has been selected, the management station determines if it wishes to create and activate the conceptual row in one transaction or in a negotiated set of interactions. Interaction 2a: Creating and Activating the Conceptual Row The management station must first determine the column requirements, i.e., it must determine those columns for which it must or must not provide values. Depending on the complexity of the table and the management station's knowledge of the agent's capabilities, this determination can be made locally by the management station. Alternately, the management station issues a management protocol get operation to examine all columns in the conceptual row that it wishes to create. In response, for each column, there are three possible outcomes: - a value is returned, indicating that some other management station has already created this conceptual row. We return to interaction 1. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it should supply a value for this column when the conceptual row is to be created. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. Once the column requirements have been determined, a management protocol set operation is accordingly issued. This operation also sets the new instance of the status column to `createAndGo'. When the agent processes the set operation, it verifies that it has sufficient information to make the conceptual row available for use by the managed device. The information available to the agent is provided by two sources: the management protocol set operation which creates the conceptual row, and, implementation-specific defaults supplied by the agent (note that an agent must provide implementation-specific defaults for at least those objects which it implements as read-only). If there is sufficient information available, then the conceptual row is created, a `noError' response is returned, the status column is set to `active', and no further interactions are necessary (i.e., interactions 3 and 4 are skipped). If there is insufficient information, then the conceptual row is not created, and the set operation fails with an error of `inconsistentValue'. On this error, the management station can issue a management protocol retrieval operation to determine if this was because it failed to specify a value for a required column, or, because the selected instance of the status column already existed. In the latter case, we return to interaction 1. In the former case, the management station can re-issue the set operation with the additional information, or begin interaction 2 again using `createAndWait' in order to negotiate creation of the conceptual row. NOTE WELL Regardless of the method used to determine the column requirements, it is possible that the management station might deem a column necessary when, in fact, the agent will not allow that particular columnar instance to be created or written. In this case, the management protocol set operation will fail with an error such as `noCreation' or `notWritable'. In this case, the management station decides whether it needs to be able to set a value for that particular columnar instance. If not, the management station re-issues the management protocol set operation, but without setting a value for that particular columnar instance; otherwise, the management station aborts the row creation algorithm. Interaction 2b: Negotiating the Creation of the Conceptual Row The management station issues a management protocol set operation which sets the desired instance of the status column to `createAndWait'. If the agent is unwilling to process a request of this sort, the set operation fails with an error of `wrongValue'. (As a consequence, such an agent must be prepared to accept a single management protocol set operation, i.e., interaction 2a above, containing all of the columns indicated by its column requirements.) Otherwise, the conceptual row is created, a `noError' response is returned, and the status column is immediately set to either `notInService' or `notReady', depending on whether it has sufficient information to (attempt to) make the conceptual row available for use by the managed device. If there is sufficient information available, then the status column is set to `notInService'; otherwise, if there is insufficient information, then the status column is set to `notReady'. Regardless, we proceed to interaction 3. Interaction 3: Initializing non-defaulted Objects The management station must now determine the column requirements. It issues a management protocol get operation to examine all columns in the created conceptual row. In the response, for each column, there are three possible outcomes: - a value is returned, indicating that the agent implements the object-type associated with this column and had sufficient information to provide a value. For those columns to which the agent provides read-create access (and for which the agent allows their values to be changed after their creation), a value return tells the management station that it may issue additional management protocol set operations, if it desires, in order to change the value associated with this column. - the exception `noSuchInstance' is returned, indicating that the agent implements the object-type associated with this column, and that this column in at least one conceptual row would be accessible in the MIB view used by the retrieval were it to exist. However, the agent does not have sufficient information to provide a value, and until a value is provided, the conceptual row may not be made available for use by the managed device. For those columns to which the agent provides read-create access, the `noSuchInstance' exception tells the management station that it must issue additional management protocol set operations, in order to provide a value associated with this column. - the exception `noSuchObject' is returned, indicating that the agent does not implement the object-type associated with this column or that there is no conceptual row for which this column would be accessible in the MIB view used by the retrieval. As such, the management station can not issue any management protocol set operations to create an instance of this column. If the value associated with the status column is `notReady', then the management station must first deal with all `noSuchInstance' columns, if any. Having done so, the value of the status column becomes `notInService', and we proceed to interaction 4. Interaction 4: Making the Conceptual Row Available Once the management station is satisfied with the values associated with the columns of the conceptual row, it issues a management protocol set operation to set the status column to `active'. If the agent has sufficient information to make the conceptual row available for use by the managed device, the management protocol set operation succeeds (a `noError' response is returned). Otherwise, the management protocol set operation fails with an error of `inconsistentValue'. NOTE WELL A conceptual row having a status column with value `notInService' or `notReady' is unavailable to the managed device. As such, it is possible for the managed device to create its own instances during the time between the management protocol set operation which sets the status column to `createAndWait' and the management protocol set operation which sets the status column to `active'. In this case, when the management protocol set operation is issued to set the status column to `active', the values held in the agent supersede those used by the managed device. If the management station is prevented from setting the status column to `active' (e.g., due to management station or network failure) the conceptual row will be left in the `notInService' or `notReady' state, consuming resources indefinitely. The agent must detect conceptual rows that have been in either state for an abnormally long period of time and remove them. It is the responsibility of the DESCRIPTION clause of the status column to indicate what an abnormally long period of time would be. This period of time should be long enough to allow for human response time (including `think time') between the creation of the conceptual row and the setting of the status to `active'. In the absence of such information in the DESCRIPTION clause, it is suggested that this period be approximately 5 minutes in length. This removal action applies not only to newly-created rows, but also to previously active rows which are set to, and left in, the notInService state for a prolonged period exceeding that which is considered normal for such a conceptual row. Conceptual Row Suspension When a conceptual row is `active', the management station may issue a management protocol set operation which sets the instance of the status column to `notInService'. If the agent is unwilling to do so, the set operation fails with an error of `wrongValue' or `inconsistentValue'. Otherwise, the conceptual row is taken out of service, and a `noError' response is returned. It is the responsibility of the DESCRIPTION clause of the status column to indicate under what circumstances the status column should be taken out of service (e.g., in order for the value of some other column of the same conceptual row to be modified). Conceptual Row Deletion For deletion of conceptual rows, a management protocol set operation is issued which sets the instance of the status column to `destroy'. This request may be made regardless of the current value of the status column (e.g., it is possible to delete conceptual rows which are either `notReady', `notInService' or `active'.) If the operation succeeds, then all instances associated with the conceptual row are immediately removed. · Integer32

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.

StorageType1 = other2 = volatile3 = nonVolatile4 = permanent5 = readOnlyDescribes the memory realization of a conceptual row. A row which is volatile(2) is lost upon reboot. A row which is either nonVolatile(3), permanent(4) or readOnly(5), is backed up by stable storage. A row which is permanent(4) can be changed but not deleted. A row which is readOnly(5) cannot be changed nor deleted. If the value of an object with this syntax is either permanent(4) or readOnly(5), it cannot be written. Conversely, if the value is either other(1), volatile(2) or nonVolatile(3), it cannot be modified to be permanent(4) or readOnly(5). (All illegal modifications result in a 'wrongValue' error.) Every usage of this textual convention is required to specify the columnar objects which a permanent(4) row must at a minimum allow to be writable. · Integer32

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.

MplsLpsState1 = normal2 = unavLOlocal3 = unavSFPlocal4 = unavSDPlocal5 = unavLOremote6 = unavSFPremote7 = unavSDPremote8 = protfailSFWlocal9 = protfailSDWlocal10 = protfailSFWremote11 = protfailSDWremote12 = switadmFSlocal13 = switadmMSWlocal14 = switadmMSPlocal15 = switadmFSremote16 = switadmMSWremote17 = switadmMSPremote18 = wtr19 = dnr20 = exerLocal21 = exerRemoteThis textual convention describes an object that stores the current state of the PSC state machine. The values are as follows: normal Normal state. unavLOlocal Unavailable state due to local LO command. unavSFPlocal Unavailable state due to local SF-P. unavSDPlocal Unavailable state due to local SD-P. unavLOremote Unavailable state due to remote LO message. unavSFPremote Unavailable state due to remote SF-P message. unavSDPremote Unavailable state due to remote SD-P message. protfailSFWlocal Protecting Failure state due to local SF-W. protfailSDWlocal Protecting Failure state due to local SD-W. protfailSFWremote Protecting Failure state due to remote SF-W message. protfailSDWremote Protecting Failure state due to remote SD-W message. switadmFSlocal Switching Administrative state due to local FS command. Same as Protecting Administrative state due to local FS command in the PSC mode. switadmMSWlocal Switching Administrative state due to local MS-W command. switadmMSPlocal Switching Administrative state due to local MS-P command. Same as Protecting Administrative state due to local MS command in the PSC mode. switadmFSremote Switching Administrative state due to remote FS message. Same as Protecting Administrative state due to remote FS message in the PSC mode. switadmMSWremote Switching Administrative state due to remote MS-W message. switadmMSPremote Switching Administrative state due to remote MS-P message. Same as Protecting Administrative state due to remote MS message in the PSC mode. wtr Wait-to-Restore state. dnr Do-not-Revert state. exerLocal Exercise state due to local EXER command. exerRemote Exercise state due to remote EXER message.Reference: Sections 3 and 11 of RFC 7271 · Integer32

The current state of the PSC state machine. ⓘ

MplsLpsReq0 = noRequest1 = doNotRevert2 = reverseRequest3 = exercise4 = waitToRestore5 = manualSwitch7 = signalDegrade10 = signalFail12 = forcedSwitch14 = lockoutOfProtectionThis textual convention describes an object that stores the PSC Request field of the PSC control packet. The values are as follows: noRequest No Request doNotRevert Do-not-Revert reverseRequest Reverse Request exercise Exercise waitToRestore Wait-to-Restore manualSwitch Manual Switch signalDegrade Signal Degrade (SD) signalFail Signal Fail (SF) forcedSwitch Forced Switch lockoutOfProtection Lockout of Protection.Reference: Section 4.2.2 of RFC 6378 and Section 8 of RFC 7271 · Integer32

The current value of the PSC Request field received on the most recent PSC packet. ⓘ

MplsLpsReq0 = noRequest1 = doNotRevert2 = reverseRequest3 = exercise4 = waitToRestore5 = manualSwitch7 = signalDegrade10 = signalFail12 = forcedSwitch14 = lockoutOfProtectionThis textual convention describes an object that stores the PSC Request field of the PSC control packet. The values are as follows: noRequest No Request doNotRevert Do-not-Revert reverseRequest Reverse Request exercise Exercise waitToRestore Wait-to-Restore manualSwitch Manual Switch signalDegrade Signal Degrade (SD) signalFail Signal Fail (SF) forcedSwitch Forced Switch lockoutOfProtection Lockout of Protection.Reference: Section 4.2.2 of RFC 6378 and Section 8 of RFC 7271 · Integer32

The current value of the PSC Request field sent on the most recent PSC packet. ⓘ

MplsLpsFpathPathThis textual convention describes an object that stores the Fault Path (FPath) field and Data Path (Path) field of the PSC control packet. FPath is located in the first octet, and Path is located in the second octet. The value and the interpretation of the FPath field are as follows: 2-255 for future extensions 1 the anomaly condition is on the working path 0 the anomaly condition is on the protection path The value and the interpretation of the Path field are as follows: 2-255 for future extensions 1 protection path is transporting user data traffic 0 protection path is not transporting user data traffic.Reference: Sections 4.2.5 and 4.2.6 of RFC 6378 SIZE (2) · OCTET STRING · hint 1x:

The current value of the FPath and Path fields received on the most recent PSC packet. ⓘ

MplsLpsFpathPathThis textual convention describes an object that stores the Fault Path (FPath) field and Data Path (Path) field of the PSC control packet. FPath is located in the first octet, and Path is located in the second octet. The value and the interpretation of the FPath field are as follows: 2-255 for future extensions 1 the anomaly condition is on the working path 0 the anomaly condition is on the protection path The value and the interpretation of the Path field are as follows: 2-255 for future extensions 1 protection path is transporting user data traffic 0 protection path is not transporting user data traffic.Reference: Sections 4.2.5 and 4.2.6 of RFC 6378 SIZE (2) · OCTET STRING · hint 1x:

The current value of the FPath and Path fields sent on the most recent PSC packet. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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. ⓘ

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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. ⓘ

Counter32

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. ⓘ

Counter32

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. ⓘ

Unsigned32

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.

INTEGER1 = working2 = protection · Integer32

This object represents whether the ME is configured as the working path or the protection path. ⓘ

BITS

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. ⓘ

Counter32

Represents the count of Signal Degrade conditions. For the detection and clearance of Signal Degrade, see the description of mplsLpsConfigSdThreshold. ⓘ

Counter32

Represents the count of Signal Fail conditions. This condition occurs when the OAM running on this ME detects the Signal Fail event. ⓘ

Counter32

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. ⓘ

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

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. ⓘ

Counter32 · seconds

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. ⓘ