MTP3 Commands

NA_DBG_LEVEL - NA Debug Level
Permissions: Writeable
Type: int
Description: MTP3 NA Debug Level (0 - 255). System wide MTP3 related events will be traced and logged to the Debug Log. Please do not change the NA Debug Level attribute unless instructed by support as increased logging beyond default setting may adversly impact performance. Default value: 1.

LDL_DBG_LEVEL - LDL Debug Level
Permissions: Writeable
Type: int
Description: MTP3 LDL Debug Level (0 - 255). Layer Distribtion Library (LDL) related events will be traced and logged to the Debug Log. Please do not change the LDL Debug Level attribute unless instructed by support as increased logging beyond default setting may adversly impact performance. Default value: 2.

SCTP_DBG_LEVEL - SCTP Debug Level
Permissions: Writeable
Type: int
Description: MTP3 SCTP Debug Level (0 - 255). Ribbon SCTP related events will be traced and logged to the Debug Log. Please do not change the SCTP Debug Level attribute unless instructed by support as increased logging beyond default setting may adversly impact performance. Default value: 0. Obsolete as of 15.1.0 for LK SCTP deployments.

LDL_SCTP_DBG_LEVEL - LDL SCTP Debug Level
Permissions: Writeable
Type: int
Description: MTP3 LDL SCTP Debug Level (0 - 255). LDL Ribbon SCTP related events will be traced and logged to the Debug Log. Please do not change the LDL SCTP Debug Level attribute unless instructed by support as increased logging beyond default setting may adversly impact performance. Default value: 0. Obsolete as of 15.1.0 for LK SCTP deployments.

TELEDIAG - Telemetry Diagnostics
Permissions: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the Debug Telemetry Diagnostics flag is set to LOGGED, then information concerning DRE telemetry diagnostics data will be sent to the Debug log file every minute. \n The recommended default setting of this flag is LOGGED, so that the user could monitor the telemetry data.

MSUQ - MSU Queue Depth
Permissions: Writeable
Type: int(Range: [50000..2e+06])
Description:  Please do not change these parameters unless instructed by Customer Support. The parameters on this page affect the queueing of MSUs between processes, especially between DREs. Configuring the queues to be too small may result in the queues overflowing under normal conditions, hence resulting in unnecessary MSU loss. Configuring the queues to be too large can result in problems during overload, including long delay in MSUs delivery, possible MSU missequencing, and possibly exceeding system resources. The queues have the following configurable thresholds: * The MSU threshold is the most MSUs that will be queued before the queue is considered full. Any further MSUs requiring queueing are discarded until space opens in the queue. * The time-based thresholds indicate the age beyond which MSUs in the queue should be considered obsolete and should be discarded to shed work. Setting this value higher that time-controlled changeover (T1) or changeback timer (T3) values could result in MSU missequencing if these procedures are executed during heavy overload conditions. This parameter has three levels and should satisfy Onset 1 <= Onset 2 <= Onset 3. Onset levels 1 and 2 generate log warnings, Onset 3 begins discarding MSUs.

TIME_CONG1 - Time Cong Onset 1
Permissions: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [100..20000])
Description:  Please do not change these parameters unless instructed by Customer Support. The parameters on this page affect the queueing of MSUs between processes, especially between DREs. Configuring the queues to be too small may result in the queues overflowing under normal conditions, hence resulting in unnecessary MSU loss. Configuring the queues to be too large can result in problems during overload, including long delay in MSUs delivery, possible MSU missequencing, and possibly exceeding system resources. The queues have the following configurable thresholds: * The MSU threshold is the most MSUs that will be queued before the queue is considered full. Any further MSUs requiring queueing are discarded until space opens in the queue. * The time-based thresholds indicate the age beyond which MSUs in the queue should be considered obsolete and should be discarded to shed work. Setting this value higher that time-controlled changeover (T1) or changeback timer (T3) values could result in MSU missequencing if these procedures are executed during heavy overload conditions. This parameter has three levels and should satisfy Onset 1 <= Onset 2 <= Onset 3. Onset levels 1 and 2 generate log warnings, Onset 3 begins discarding MSUs.

TIME_CONG2 - Time Cong Onset 2
Permissions: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [100..20000])
Description:  Please do not change these parameters unless instructed by Customer Support. The parameters on this page affect the queueing of MSUs between processes, especially between DREs. Configuring the queues to be too small may result in the queues overflowing under normal conditions, hence resulting in unnecessary MSU loss. Configuring the queues to be too large can result in problems during overload, including long delay in MSUs delivery, possible MSU missequencing, and possibly exceeding system resources. The queues have the following configurable thresholds: * The MSU threshold is the most MSUs that will be queued before the queue is considered full. Any further MSUs requiring queueing are discarded until space opens in the queue. * The time-based thresholds indicate the age beyond which MSUs in the queue should be considered obsolete and should be discarded to shed work. Setting this value higher that time-controlled changeover (T1) or changeback timer (T3) values could result in MSU missequencing if these procedures are executed during heavy overload conditions. This parameter has three levels and should satisfy Onset 1 <= Onset 2 <= Onset 3. Onset levels 1 and 2 generate log warnings, Onset 3 begins discarding MSUs.

TIME_CONG3 - Time Cong Onset 3
Permissions: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [100..20000])
Description:  Please do not change these parameters unless instructed by Customer Support. The parameters on this page affect the queueing of MSUs between processes, especially between DREs. Configuring the queues to be too small may result in the queues overflowing under normal conditions, hence resulting in unnecessary MSU loss. Configuring the queues to be too large can result in problems during overload, including long delay in MSUs delivery, possible MSU missequencing, and possibly exceeding system resources. The queues have the following configurable thresholds: * The MSU threshold is the most MSUs that will be queued before the queue is considered full. Any further MSUs requiring queueing are discarded until space opens in the queue. * The time-based thresholds indicate the age beyond which MSUs in the queue should be considered obsolete and should be discarded to shed work. Setting this value higher that time-controlled changeover (T1) or changeback timer (T3) values could result in MSU missequencing if these procedures are executed during heavy overload conditions. This parameter has three levels and should satisfy Onset 1 <= Onset 2 <= Onset 3. Onset levels 1 and 2 generate log warnings, Onset 3 begins discarding MSUs.

CONTEXT - Context
Permissions: Read-only
Type: string
Description: A condensed textual representation of the signaling node object

LOCAL_PC - Local Point Code
Permission: Writeable
Type: pointcode
Description: The SS7 local point code of this signaling node in the format Network.Cluster.Member. Maximum value is 255.255.255. If the personality is ITU, the format is Zone.Area.Member and the range for Zone and Member is 0 to 7, Area is 0 to 255.

SS7_NODETYPE - SS7 Node Type
Permission: Writeable
Type: NodeType={STP,END_NODE}
Description: Obsolete as of 12.0.0. The node type of this Network Appearance, should be set to either STP or END_NODE depending upon MTP3 Routing needs. The ability to route messages at the MTP3 level is a licensed feature.

SS7_VARIANT - SS7 Variant
Permission: Writeable
Type: PersCode={ITU,ANSI,TTC,NTT,CHINA,PAKISTAN,INDIA,NEW_ZEALAND}
Description: The SS7 Variant supported at the MTP3 level. This value should also be set at the SCCP, GTT and SG layers, if they are in use. Valid options are: ITU, ANSI, CHINA, JAPAN (NTT and TTC), PAKISTAN, INDIA, NEW_ZEALAND. Not all variants are supported on all product lines. For example, many of the variants other than ANSI and ITU are used only with the Level 4 Converter module.

PC_DISPLAY - PC Display Format
Permission: Writeable
Type: string
Description:  Point Code Display Format based on SS7 Variant. For ITU based, must be 14-bit compatible, for Japan 16-bit, while ANSI and China 24-bit. Valid options are: 8.8.8, 3.8.3, ff-ff, 4.4.6, 5.4.7, 3.4.7, 4.3.7, 4.6.4, 6.4.4, 4.7.3, 5.4.5, and Decimal. Note that the dash delimiter is also accepted (i.e. 8-8-8). For ANSI platforms using SNAMI, the format must be 8.8.8

PC_ROUTING - PC Routing Format
Permission: Writeable
Type: string
Description: Point Code Routing Format based on SS7 Variant. For ITU based, must be 14-bit compatible, for Japan 16-bit, while ANSI and China 24-bit. The x-y or x-y-z fields must be 8-bit or less. Valid options are: 8.8.8, 3.8.3, 4.4.6, 5.4.7, 3.4.7, 4.3.7, 4.6.4, 6.4.4, 4.7.3, and 5.4.5.

NET_IND - Network Indicator
Permission: Writeable
Type: NetId={NI_00,NI_01,NI_10,NI_11}
Description: The Network Indicator is a 2 bit value that identifies the network in the MTP3 service indicator octet. Valid options are: NI_00 for International, NI_01 for Spare International, NI_10 for National (default), NI_11 for National Spare. When PT_C20 Application ID Management is used, the NI may not be modified after the NA is activated. Modification requires the NA to be deleted

STATUS - Status
Permission: Read-only
Type: epx_node_status={ACTIVE,INACTIVE,UNLICENSED}
Description: Node Status is a Permission: Read-only attribute that shows your system status of this Network Appearance. Valid options are: ACTIVE, INACTIVE. Traffic will not flow, and links will not align on an Inactive node.

CLLI - CLLI
Permission: Writeable
Type: string
Description: Set this attribute to the Common Language Location Identifier (CLLI) of the NA. The CLLI is used in the system log file for debugging purposes. Our system allows for alphanumeric characters, punctuation marks, and keyboard symbols. However, some other systems will only allow for alphanumeric characters. The CLLI code is usually unique to a network and is often provided by the network design team. Note: Only the first 16 characters in this attribute are used in the logs. It is recommend a unique and meaningful entry for this attribute to make the syslog events easier to interpret, especially when running multiple Network Appearances. When SONUS_C20 Application ID Management is used, the CLLI may not contain spaces, dots, or other special characters. The CLLI may not be modified after the NA is activated. Modification requires the NA to be deleted. When NA is used for SNAMI application: the CLLI may not contain spaces, the CLLI must be UPPERCASE, the CLLI is exactly 11 characters in length.

RXMSU - Rx MSU Count
Permissions: Read-only
Type: int
Description: Number of MSUs received per second for the NA

TXMSU - Tx MSU Count
Permissions: Read-only
Type: int
Description: Number of MSUs transmitted per second for the NA

ACTV_SNMSLOT - Active SNM Slot
Permission: Read-only
Type: int(Range: [0..255])
Description: Peer Identifier of the Active SNM. The SNM is one of two processes running our MTP3 layer. A process is either 'active' or 'standby'. On a two slot system there will be one of each. Both are processing traffic, but the 'active' is the SNM that controls the User Interface and the SLC tables. During some upgrade procedures you may be asked (in the upgrade instructions) to consult this attribute so that you may bring to down the Standby SNM first.

SLSSIZE - SLS Size
Permission: Writeable
Type: SLSSize={FOUR,FIVE,EIGHT}
Description: Signaling Link Selector Size (4, 5, 8 bits). This sets the number of bits used in the SLS field of the MTP routing label. ANSI network typically use 8 or 5 bits, and the ITU network typically use 4 bits.

ROTATESLS - Rotate SLS
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: SLS rotation is used to load share traffic across links in an ANSI network. This flag enables or disables the SLS rotation on a Network appearance basis. An ANSI STP will typically rotate the SLS after selecting a link. An ITU STP will typically not rotate the SLS. In either case the SLS value is not rotated when a message is sent across the C-Link (see the Linkset 'Rotate SLS' attribute).If SLS rotation is disabled here, the corresponding Linkset attributes become meaningless.

SLS_IGNBIT - SLS Ignore Bit
Permission: Writeable
Type: SLSIgnoreBit={NONE,ZERO,ONE,TWO,THREE,FIVE}
Description: Setting SLS ignore bit allows better loadsharing distribution between links. Ability to change SLS Ignore bit depends on the standard. For ANSI SLS Ignore Bit is always set to bit 5 as per clause T1.111.5.

SLS_LSSELECTBIT - SLS Linkset Select Bit
Permission: Writeable
Type: SLSLinksetSelectBit={ZERO,ONE,TWO,THREE}
Description: Select SLS Linkset Selection bit is applicable for ITU only. It allows better loadsharing distribution between links

MAX_ECR - Max Equal Cost Routes
Permission: Writeable
Type: int(Range: [2..4])
Description: Set the maximum number of equal cost routes per routeset.

GENUPU - Generate UPU
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable User Part Unavailable (UPU) message generation for the signaling node. It is recommended to enable the generation of UPUs.

LCLMTPRSTSUP - Local MTP Restart Support
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Indicates whether this node supports Local MTP Restart procedures. MTP Restart procedures invoke a set of timers (t25, t27 and t28) that are used when an isolated node is returning to service. These timers allow the node to get routing information from the adjacent nodes before attempting to run traffic. We recommend Restart be set to ENABLED, unless you have a specific network condition that does not allow Restart. For example older adjacent nodes may not support this feature at this node and might be confused by the Traffic-Restart-Allowed (TRA) message sent out at the start of this process. Restart Support may also be set on a per link basis if you have one particular adjacent node that does not handle MTP Restart procedures. For more information about Restart feature, see the appropriate sections in the T1.111.4 Signaling Network Functions and Messages (ANSI) and Q.704 Signaling Network Functions and Messages (ITU-T).

PCNUMVALID - PC Numbering Validation
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: When Point Code Numbering Validation is turned on, the system will require that all Point Codes used are allowed under the appropriate ITU or ANSI standards. For example 0.1.3 is not a valid point code in ANSI. Turning off PC Numbering Validation would allow the point code on this node, however it does not indicate that other external nodes and systems who received this PC will be able to process it.

SPARESSFBITS - Spare SSF Bits
Permission: Writeable
Type: SpareSSFBits={SPARE_SSF_BITS,SPARE_SSF_BITS_00,SPARE_SSF_BITS_01,SPARE_SSF_BITS_10,SPARE_SSF_BITS_11}
Description: Spare Bits in the SSF are normally used as either spare or as priority bits (default behavior). In some National variants the spare bits may be configured and act like an extension of the Network Indicator: messages are only accepted if the spare bits match the configured value.

NI_USER_OVERRIDE - NI User Override
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: NI User Override for incoming MSUs. If enabled, the Network Indicator from the MTP3 NA will override the NI value in the MSUs coming from the L4 Connection users. NI override only applies to MSUs with SI greater or equal to 3.

M2PADFTVER - M2PA Default Version
Permission: Writeable
Type: M2paDefaultVersion={Draft 6,RFC 4165}
Description: M2PA Default Version sets the standard SIGTRAN version to which the M2PA messages will conform. This need only be set if this node is using M2PA links. The current M2PA standard, and the recommended value is RFC 4165. Connections to older systems may require use of the earlier Draft 6.

LOADSHARE_MODE - Loadshare Mode
Permission: Writeable
Type: LoadsharingMode={SLS,SCCP0,ENHANCED SLS,ENHANCED SLS AND SCCP0,TTC AB PLANE}
Description: Loadshare mode affects the algorithm that determines which MSUs are routed on which links (the loadsharing algorithm). When set to 'SLS', the usual loadsharing algorithm is used, based on the SLS in the incoming MSU. This algorithm is usually satisfactory, but may have drawbacks in some SS7 variants and network configurations in which the range of meaningful SLS values may be limited. Also, MSUs such as SCCP messages with Protocol Class 0 do not have sequencing requirements. When set to 'SCCP0', SCCP messages that do not require sequencing are loadshared evenly between links without regard to the incoming SLS and the outgoing SLS is modified. Other MSUs are loadshared in the usual way using the MSU SLS. When set to 'ENHANCED SLS', a new SLS value is generated based on incoming information such as OPC, DPC and link SLC. When set to ENHANCED SLS AND SCCP0, the option will process Protocol class 0 messages first and use the same functionality at SCCP0, plus remaining messages are processed using the same functionality as the ENHANCED SLS option. Applies to SI > 2 messages only. When set to 'TTC AB PLANE' the A/B Plane Bit is used to select the outgoing linkset. This attribute only takes effect if a routeset is using a combined linkset (two routes with equal cost), and if one linkset is configured as a A-plane linkset (using the Linkset 'AB Plane Bit' attribute) and the other linkset is configured as a B-plane linkset. In this case, the A/B Plane Bit in the MSU SLS is used to select the outgoing linkset when sufficient links are available. In some cases there is a trade-off between evenly distributing traffic across available links and respecting the A/B bit for linkset selection. These cases are handled as follows. If each linkset has half or more its links available, the AB Plane Bit is used to select the outgoing linkset and the other SLS bits are used to select the link within the linkset. If one of the linksets has less than half its links available (''abnormal'' or ''quasi-normal'') but the other linkset has half or more its links available (''normal'' or ''fully normal''), then only one linkset is used for traffic: the linkset with half or more of its links available. If each linkset has less than half its links available, priority is given to making the traffic on each link as even as possible, while respecting the AB Plane Bit when this doesn't further unbalance traffic.

SISLT - SLT SI
Permission: Writeable
Type: SIForSlt={AUTO,NTM_REGULAR,NTM_SPECIAL}
Description: The Service Indicator (SI) used for Signaling Link Test (SLT) messages. AUTO sets the value based on SS7 Variant NTM_REGULAR uses the SI value 1 NTM_SPECIAL uses the SI value 2 The default value is AUTO. This value is used to customize the Signaling Link Test Messages (SLTM) and Signaling Link Test Message Acknowledgements (SLTA). This is not a value that should be changed on a running system. As such you must deactivate all linksets on the NA before you will be allowed to change the SLT parameters for this NA. Reactivate the links after the change has been made.

SLTMPATTERN - SLTM Pattern
Permission: Writeable
Type: string
Description: The Test Pattern Used for Signaling Link Test Messages (SLTM) messages written in hexadecimal format. Enter this value as a string representing the hex value (for example, AABBCCDD). This value is used to customize the Signaling Link Test Messages (SLTM) and Signaling Link Test Message Acknowledgements (SLTA). This is not a value that should be changed on a running system. As such you must deactivate all linksets on the NA before you will be allowed to change the SLT parameters for this NA. Reactivate the links after the change has been made.

MSUSIZE - Maximum MSU Length
Permission: Writeable
Type: MsuSize={273 to 4092} (Units: bytes)
Description: The maximum number of bytes allowed, including routing label and SIO, for an MSU in this NA. Range is 273 to 4092 bytes. The value should remain at the default of 273 unless the NA is meant to support MTP3B with long MSUs.

LONGMSUINTERVAL - Long MSU Discard Interval
Permission: Writeable
Type: IntervalMinutes={1 to 1440} (Units: minutes)
Description: The interval in which the maximum number of traps can be raised to report a Long MSU discard for an unsupported destination. Unsupported destination could be a linkset, user part or application. This timer also indicates how long the dashboard alarm will remain visible after the last Long MSU discard by the unsupported destination.

LONGMSUTRAPS - Long MSU Discard Maximum
Permission: Writeable
Type: MaxTrapGen={1 to 100}
Description: The maximum number of SNMP traps that can be raised in the Long MSU Discard Interval for a particular destination.

APPIDMGMT - Application ID Mgmt
Permission: Writeable
Type: ApplicationIDMgmt={NONE,PT_C20}
Description: Application ID Management feature for registered AppID special handling. This feature is designed for application related deployments where the registration of the associated Application ID (aka same name as this attribute) triggers predetermined MTP3 events such as link outage, special user messaging, and so forth. Supported values: NONE and PT_C20. By default, the attribute is set to NONE. The attribute can only modified when the node is cleared and inactive. Must be set to PT_C20 for Ribbon SP2K deployments interfacing with a C20 call agents.

GENERATETFM - Generate TFM
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: TFM generation for PT_C20 End Nodes. Enabled by default. Can only be disabled if the Application ID Mgmt is set to PT_C20 and the VNode and Routing features are disabled. When disabled, all TFM messages (TFP, TFA, TCP, etc.) are not generated by the MTP3 NA.

ALARMSACTIVATE - Enable Alarms on Activate
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable Alarms on Activate. When ENABLED, Alarms are forced to the enabled state when the object is Activated. When DISABLED, Alarms retain their current state when the object is Activated. Default Value: ENABLED. Valid values: ENABLED, DISABLED

MTP4CXPORT - L4 Connection Port
Permission: Read-only
Type: int(Range: [0..9999])
Description: L4 Connection Port is the internal TCP/IP port on which the internal processes (SCCP and Signaling Gateway) connect. This is a Permission: Read-only informational attribute

MATESTP - Mate STP
Permission: Read-only
Type: pointcode
Description: The Mate STP point code is the local point code of the other signaling node in a mated-pair configuration. On STP products, there should be a Routeset and a Linkset to the Mate-STP, and typically all Routesets to other nodes will contain a route through the mate STP at a higher cost. The signaling gateway may have at most one mate.

VNDFEAT - VNode Feature
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: The Virtual Nodes feature is enabled by license on our SS7 Gateway and STP products. Virtual nodes are used by gateway applications. The Local Point Code (LPC) identifies the node to which links terminate. However if we are using a point code to be shared across a pair of nodes and to which an application will register, then a Virtual Node (VPC) is required. The VNode feature must be turned on before VNodes may be created on this system.

ROUTINGFEAT - Routing Feature
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: The STP function of routing SS7 messages at MTP level 3 is enabled by license. With this enabled the node will be able to receive messages and forward messages destined for one of its available routesets. Without MTP routing the system will act only as a gateway for IP applications. The feature is Available on our SS7 Gateway and STP products and is not available on Edge products.

R4_8COMPL - R4_8 Compliance
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: This flag is used to turn on or off R4-8 compliance for SS7 messages during STP routing. Typically all traffic that has be GTT routed or from a user application will have the OPC set to LPC. However for some of our custom routing products (converters and PCE) this may not be desirable. The feature is Available on our SS7 Gateway and STP products and is not available on Edge products. R4_8 Compliance is typically set to ENABLED.

DBGFEAT - Debug
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: If set to ENABLED, the debug flags that follow in this screen are applied. This is a setting for the debug system as a whole. The remaining flags are individual settings for specific debug features. It is strongly recommended that this flag be set to ENABLED on all systems.

DBGERR - Errors
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If set to LOGGED the Debug Error flag will enable all logs sent to Syslog to also be sent to the Debug log. With Error messages and other Debug information in the one Debug log file, it is easier to interpret the log events. It is strongly recommended that this flag be set to LOGGED on all systems.

DBGSNMMGMT - SNM Management
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the Debug SNM Management flag is set to LOGGED, then information concerning the state of management of the MTP Level 3 will be sent to the Debug log file. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGPEERADM - Peer Administration
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the Peer Administration flag is set to LOGGED, then activities with the distributed peer of the MTP will be logged to the Debug log file. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGL2CON - L2 Connection
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the L2 Connection flag is set to LOGGED, then the then activities concerning the internal connections to the L2 process will be logged to the Debug log file. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGDRECON - DRE Connection
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the DRE Connection flag is set to LOGGED, then activities concerning the internal connections to the DRE process will be logged to the Debug log file. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGDREADM - DRE Administration
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the DRE Administration flag is set to LOGGED, then activities concerning the management of the DRE process will be logged to the Debug log file. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGDRESWTCH - DRE Switchover
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the DRE Switchover flag is set to LOGGED, then these activities will be logged to the Debug log file. The DRE Switchover activities take place when one DRE process takes over for a DRE process that has become unavailable for some reason. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGSETUP - Setup
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the Setup flag is set to LOGGED, then activities associated with the startup of the process and its initial configuration will be logged in the Debug log file. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGOTIMERS - Other Timers
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the Other Timers flag is set to LOGGED , then an information message will be placed in the Debug Log file when various timers ( other than the IO Timers) are used. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGREROUTPROC - Rerouting Procedure
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If Rerouting Procedure flag is set to LOGGED, then informational messages are placed in the Debug Log File when the MTP level 3 invokes Rerouting procedures. Controlled Rerouting is the SS7 concept whereby the networked adjusts routing to state changes in nodes. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGCO_CBPROC - CO CB Procedure
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If Change Over / Change Back (CO/CB) Procedure flag, is set to LOGGED, then informational messages concerning how links go through Change Over and Change Back procedures are placed in the Debug Log. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGLINKSTATUS - Link Status
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If Link Status flag is set to LOGGED, then informational messages concerning the state changes of the SS7 links are placed in the Debug Log. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGL2MSG - L2 Messages
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If Level 2 messages flag is set to LOGGED, then informational messages detailing the communications between the DRE and its Level 2 module are placed in the Debug Log. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGUSRMGMT - User Management
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If MTP User management flag is set to LOGGED, then information concerning the state of communications between the DRE and its connected users (SCCP or Signaling Gateway) are placed in the Debug Log. This feature is applicable on the SS7 Gateway and STP products, and not on Edge devices. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGUSRPRIM - User Primitives
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If MTP User Primitive message flag is set to LOGGED, then the messages used for communications between the DRE and its connected users (SCCP or Signaling Gateway) are placed in the Debug Log. The API used is internal and not meant to be readable by customers, thus this flag is typically only used at the request of Customer Support. This feature is applicable on the SS7 Gateway and STP products, and not on Edge devices. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGMSU - MSU Traffic
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the MSU Traffic flag is set to LOGGED, then a summary of each MSU will be presented as the MSU enters or leaves MTP Level 3. CAUTION: this flag can produce a huge volume of data, and can easily swamp a busy system with logging requests. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGMSURAW - MSU Traffic Raw
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the MSU Traffic Raw flag is set to LOGGED, then all messages and contents received or sent at the MTP Level 3 will be placed in the Debug Log in a hexadecimal representation. The format used is internal and not meant to be readable by customers, thus this flag is o typically only used at the request of Customer Support. CAUTION: this flag can produce a huge volume of data, and can easily swamp a busy system with logging requests. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGSLT - SLT
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the Debug SLT flag is set to LOGGED, then the messages and procedures concerning SLTM/SLTA/SRT/SRA functionality at MTP level 3 will be traced and logged to the Debug Log. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

DBGSLSTABLES - SLS Tables
Permission: Writeable
Type: LoggingFeature={NOT LOGGED,LOGGED}
Description: If the Debug SLS Tables flag is set to LOGGED, then information concerning changes to the state of the SLS Tables is presented in the logs. Changes to the SLS tables take place when links change state. This information is internal and not typically needed by customers. This flag is typically only used at the request of Customer Support. The recommended setting of this flag is NOT_LOGGED, so that the system resources are not unduly taken up in the production of log messages.

L3T1 - L3 T1
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [500..1200])
Description: Changeover delay ( 500 - 1200 ms ) [ANSI/ITU/JT] The default value is 1000 ms. Setting MTP Level 3 timers on the NA will encompass all linkset, routeset and NA functionality. The L3 T1 timer can be overridden from a Linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T2 - L3 T2
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [700..2000])
Description: Waiting for COA ( 700 - 2000 ms ) [ANSI/ITU/JT]. The default value is 1000 ms. Setting MTP Level 3 timers on the NA will encompass all linkset, routeset and NA functionality. The L3 T2 timer can be overridden from a Linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

Waiting for COA ( 700 - 2000 ms ) [ANSI/ITU/JT] The default value is 1000 ms. Setting MTP Level 3 timers on the NA will encompass all linkset, routeset and NA functionality. The L3 T2 timer can be overridden from a Linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T3 - L3 T3
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [500..1200])
Description: Changeback delay ( 500 - 1200 ms ) [ANSI/ITU/JT]. The default value is 1000 ms. Setting MTP Level 3 timers on the NA will encompass all linkset, routeset and NA functionality. The L3 T3 timer can be overridden from a Linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T4 - L3 T4
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [500..1200])
Description: Waiting for CBA: first attempt ( 500 - 1200 ms ) [ANSI/ITU/JT]. The default value is 1000 ms. Setting MTP Level 3 timers on the NA will encompass all linkset, routeset and NA functionality. The L3 T4 timer can be overridden from a Linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T5 - L3 T5
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [500..1200])
Description: Waiting for CBA: second attempt (500 - 1200 ms) [ANSI/ITU] The default value is 1000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

Waiting for CBA: second attempt ( 500 - 1200 ms ) [ANSI/ITU] The default value is 1000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T6 - L3 T6
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [500..1200])
Description:Controlled rerouting delay ( 500 - 1200 ms ) [ANSI/ITU/JT] The default value is 1000 ms. Setting MTP Level 3 timers on the NA will encompass all linkset, routeset and NA functionality. The L3 T6 timer can be overridden from a Linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T7 - L3 T7
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [1000..2000])
Description: Waiting for CSS/CNS/CNP (1000 - 2000 ms) [ANSI/ITU] The default value is 1500 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T8 - L3 T8
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [800..1200])
Description: TFP inhibition timer (800 - 1200 ms) [ANSI/ITU/JT] The default value is 1000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T10 - L3 T10
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [30000..60000])
Description: Waiting to repeat RSM (30,000 - 60,000 ms) [ANSI/ITU/JT] The default value is 30,000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T11 - L3 T11
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [30000..90000])
Description: TFR timer (30,000 - 90,000 ms) [ANSI/ITU] The default value is 60,000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T12 - L3 T12
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [800..1500])
Description: Waiting for LUA (800 - 1500 ms) [ANSI/ITU] The default value is 1000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T13 - L3 T13
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [800..1500])
Description: Waiting for LFU (800 - 1500 ms) [ANSI/ITU] The default value is 1000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T14 - L3 T14
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [2000..3000])
Description: Waiting for LIA (2000 - 3000 ms) [ANSI/ITU] The default value is 3000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T15 - L3 T15
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [2000..3000])
Description: Waiting to repeat RCT (2000 - 3000 ms) [ANSI/ITU/JT] The default value is 2000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T16 - L3 T16
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [1400..2000])
Description: Waiting for congestion status update (1400 - 2000 ms) [ANSI/ITU/JT] The default value is 2000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T17 - L3 T17
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [800..1500])
Description: Alignment failure and restart delay (800 - 1500 ms) [ANSI/ITU] The value is set to 1 ms in SS7 variants where the L3 T17 is not applicable. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T18 - L3 T18
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Repeat TFR once by response method (2000 - 20000 ms) The default value in ANSI is 2000 ms. ITU: Internal MTP restart timer. The Q704 standard lists this value as being network dependent. We have set the ITU default value as 5000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T19 - L3 T19
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Failed link craft referral (480,000 - 600,000 ms) The default ANSI value is 480,000 ms. ITU: MTP restart timer to control ping-pong TFP/TFR/TFA (67,000 - 69,000 ms) The default ITU value is 68,000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T20 - L3 T20
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Waiting to repeat local inhibit test (90,000 - 120,000 ms) ITU: MTP restart timer at Signaling Point whose MTP restarts (59,000 - 61,000 ms) The default ITU value is 60,000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T21 - L3 T21
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Waiting to repeat remote inhibit test (90,000 - 120,000 ms) The default ANSI value is 90,000 ms. ITU: MTP restart timer used at Signaling Point adjacent to the restarting Signaling Point (63,000 - 65,000 ms) The default value is 64,000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T22 - L3 T22
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Wait to receive TRA during a Signaling Point Restart The default ANSI value is 10,000 ms. ITU: Local inhibit test timer (180,000 - 360,000 ms) The default ITU value is 180,000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T23 - L3 T23
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Wait to broadcast all traffic restart allowed messages. The default ANSI value is 10,000 ms. ITU:Remote inhibit test timer (180,000 - 360,000 ms) The default ITU value is 180,000 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T24 - L3 T24
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Waiting to broadcast TRA on SP Restart. The default ANSI value is 10,000 ms. ITU: Stabilizing timer for latching LPO to RPO. The default ITU value is 500 ms. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T25 - L3 T25
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Wait for TRA from adjacent restarting SP (30,000 - 35,000 ms). The default ANSI value is 1000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T26 - L3 T26
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Wait to repeat TRW at restarting Signaling Point (12,000 - 15,000 ms). The default ANSI value is 12,000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T27 - L3 T27
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Minimum duration of unavailability for full restart (2000 - 5000 ms). The default ANSI value is 5000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T28 - L3 T28
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: Waiting for TRW at the Signaling Point adjacent to the restarting Signaling Point (30,000 - 35,000 ms). The default ANSI value is 30,000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T29 - L3 T29
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: TRA sent in response to unexpected TRA or TRW (60,000 - 65,000). The default ANSI value is 60,000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T30 - L3 T30
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Limit transmission of TFP/TFR's after receiving unexpected TRA/TRW's (30,000-35,000). The default ANSI value is 30,000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T31 - L3 T31
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [10000..120000])
Description: ANSI: False link congestion detection (10,000-120,000). The default ANSI value is 30,000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T32 - L3 T32
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Link oscillation - Procedure A The default ANSI value is 90,000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T33 - L3 T33
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: ANSI: Probation for link oscillation - Procedure B GR-246_CORE (60,000-600,000). The default ANSI value is 90,000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T34 - L3 T34
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [0..2147483647])
Description: Suspension for link oscillation - Procedure B GR-246_CORE (5,000-120,000). The default ANSI value is 90,000 ms. ITU: This timer is not used in ITU networks. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers through the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

TXLIST - X-List Lifespan
Permission: Writeable
Type: XLifeTimer={DISABLED,TEN_MINUTES,THIRTY_MINUTES,ONE_HOUR,TWO_HOURS,THREE_HOURS,FOUR_HOURS,SIX_HOURS,TWELVE_HOURS,ONE_DAY,TWO_DAYS}
Description: The X-List Life Timer sets the lifespan of the dynamically created X-Routesets. If an X-Routeset has not received traffic for the given period of time, the X-Routeset will be deleted from the system. The available options for this attribute are: DISABLED (implies X-routesets are never to be deleted); TEN_MINUTES;  THRITY_MINUTES;  ONE_HOUR;  TWO_HOURS;  THREE_HOURS;  FOUR_HOURS;  SIX_HOURS;  TWELVE_HOURS;  ONE_DAY;  TWO_DAYS. The default value is DISABLED. Setting MTP Level 3 timers is only done one time for the entire NA as they encompass all linkset, routeset and NA functionality. CAUTION: It is recommended that you do not change this timer value without prior forethought and planning. Removal of X-List entries enables one to 'clean-up' seldom used entries, but could impact system and network performance. Timer values generally should be modified with care, especially on a live system. Interaction of timers though the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

T19NOTIF - L3 T19 Notification
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: This parameter affects the behavior of the ANSI Link Craft Referral Timer (ANSI T19). See GR-246-CORE issue 10 T1.111.4 section 12.2 and 12.3 and GR-82-CORE section 4.2.4.10.1 for more details. If the Notification is set to enabled, then the system logs each T19 expiry event after unsuccessful activation of a link. If this attribute is set to disabled, then no system logs are generated when a link fails to come into service within T19.

T19LRESET - L3 T19 Link Reset
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: This parameter affects the behavior of the ANSI Link Craft Referral Timer (ANSI T19). See GR-246-CORE issue 10 T1.111.4 section 12.2 and 12.3 and GR-82-CORE section 4.2.4.10.1 for more details. If this attribute is set to enabled, then the link will be reset after each expiry of T19 timer. If this attribute is disabled, then the link will not be reset after the expiry of T19 timer.

T19ATTMPTS - L3 T19 Attempts
Permission: Writeable
Type: L3FailedLinkCraftRefTimer={ZERO,ONE,TWO,THREE,FOREVER}
Description: This parameter affects the behavior of the ANSI Link Craft Referral Timer (ANSI T19). See GR-246-CORE issue 10 T1.111.4 section 12.2 and 12.3 and GR-82-CORE section 4.2.4.10.1 for more details.   If this attribute is set to FOREVER, then the timer runs forever until the link gets activated. After each expiry of the timer, the link is either reset or continued for activation depending on the L3 T19 Link Reset setting.   If this attribute is set to ZERO, then the timer is totally disabled and will not run at all. If this attribute is set to ONE, then the link will stop activating and is deactivated after the first T19 expiry.   If this attribute is set to TWO or THREE and if the L3 T19 Link Reset setting is enabled then the link-reset continue forever. If this attribute is set to TWO or THREE and if L3 T19 Link Reset attribute is disabled then the link will continue to get activated for 1 or 2 periods of T19 duration depending on the selection, and finally timer will stop the link activation, and it deactivates the link after the last T19 expiry.

T31FLINKCONG - L3 T31 False Link Congestion
Permission: Writeable
Type: L3FalseLinkCongestionTimer={DISABLED_ALL_CONGESTION_LEVELS,ENABLED_ALL_CONGESTION_LEVELS,ENABLED_ALL_EXCEPT_LEVEL1}
Description: This parameter affects the behavior of L3 False Link Congestion timer (ANSI T31). See GR-246-CORE issue 10 T1.111.4 section 3.8.2.2 and GR-82-CORE section 4.2.4.1 R4-42 to R4-44 for more details.   If L3 T31 False Link Congestion attribute is set to DISABLED_ALL_CONGESTION_LEVELS, then the timer will not run at all.   If the attribute is set to ENABLED_ALL_CONGESTION_LEVELS, then the timer is started whenever the link congestion level changes to a value greater than level 0. The timer is restarted on every change of congestion level between level 1, level 2 and level 3. When the congestion level drops to level 0 then the timer is cancelled or if the timer expires then the link is restarted.   If the attribute is set to ENABLED_ALL_EXCEPT_LEVEL1, then the congestion level 1 is not considered for starting and restarting the timer. If the congestion level changes to level 2 or level 3 then the timer is started. The timer is restarted whenever the congestion level changes between level 2 and level 3. When the congestion level drops to level 1 or level 0, then the timer is cancelled or if the timer expires then the link is restarted.   The timer value is taken from the timer T31 and it should be in the range of 10000 msec to 120000 msec and the default value is 30000 msec. Whenever the link is restarted due to expiry of the timer, then the management is notified by the system log.

CRDTSUPPORT - CRDT Support
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: The ANSI CRDT procedure is supported on ANSI STPs, as per GR-246-CORE Issue 10 T1.111.7 (Method A) and GR-82-CORE Issue 10. It describes an MTP3 procedure with three configurable parameters: 'M', 'N' and 'TLoop'. The CRDT procedure may be explicitly enabled or disabled for ANSI STPs via this attribute. If the 'SS7 Variant' is not set to ANSI, or if the 'STP Routing' feature is not enabled then this attribute has no effect. Setting this attribute to DISABLED resets the state of all routes that were marked as prohibited for failing a CRDT test.

NTTUSNSUPPORT - NTT USN Support
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: The NTT USN message is part of the NTT standard. This attribute allows USN support to be enabled in TTC also.

CRDTN - CRDT N
Permission: Writeable
Type: int(Range: [50..200])
Description: The ANSI CRDT procedure is supported on ANSI STPs, as per GR-246-CORE Issue 10 T1.111.7 (Method A) and GR-82-CORE Issue 10. It describes an MTP3 procedure with three configurable parameters: 'M', 'N' and 'TLoop'. This attribute is the 'N'. The rest of this description is a summary of the CRDT procedure. ANSI CRDT Method A is performed by MTP3 as follows (overview): - when congestion status increases on a link, sample N MSUs (range 50-200) sent on that link. - From the N MSUs, compute the M most common DPCs (range 3-10). - Send test messages to those destinations. - If a test message comes back within TLoop (10 - 20s) then there is a loop in the MTP3 routing tables in the network. Disable the tested routes and those of lower priority.

CRDTM - CRDT M
Permission: Writeable
Type: int(Range: [3..10])
Description: The ANSI CRDT procedure is supported on ANSI STPs, as per GR-246-CORE Issue 10 T1.111.7 (Method A) and GR-82-CORE Issue 10. It describes an MTP3 procedure with three configurable parameters: 'M', 'N' and 'TLoop'. This attribute is the 'M'. The rest of this description is a summary of the CRDT procedure. ANSI CRDT Method A is performed by MTP3 as follows (overview): - when congestion status increases on a link, sample N MSUs (range 50-200) sent on that link. - From the N MSUs, compute the M most common DPCs (range 3-10). - Send test messages to those destinations. - If a test message comes back within TLoop (10 - 20s) then there is a loop in the MTP3 routing tables in the network. Disable the tested routes and those of lower priority.

CRDTTLOOP - CRDT Timer Loop
Permission: Writeable
Type: Seconds={0 to 1000000} (Units: s)(Range: [10..20])
Description: The ANSI CRDT procedure is supported on ANSI STPs, as per GR-246-CORE Issue 10 T1.111.7 (Method A) and GR-82-CORE Issue 10. It describes an MTP3 procedure with three configurable parameters: 'M', 'N' and 'TLoop'. This attribute is the 'TLoop'. The rest of this description is a summary of the CRDT procedure. ANSI CRDT Method A is performed by MTP3 as follows (overview): - when congestion status increases on a link, sample N MSUs (range 50-200) sent on that link. - From the N MSUs, compute the M most common DPCs (range 3-10). - Send test messages to those destinations. - If a test message comes back within TLoop (10 - 20s) then there is a loop in the MTP3 routing tables in the network. Disable the tested routes and those of lower priority.

CONF_REQUEST - Confirmation Required
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: This flag is used to turn on the confirmation request dialogue when the last link in a linkset is deactivated. The dialogue notifies the user of the possible consequences of deactivation the last link in a linkset.

CLLI - CLLI
Permission: Writeable
Type: string
Description: CLLI code of this DRE object. The CLLI code may be specified by your network designer. The value here is for informational purposes only and may be left blank.

STATE - State
Permission: Read-only
Type: AvailState={INACTIVE,UNAVAILABLE,AVAILABLE,VERSION MISMATCH}
Description: Status of the DRE connection (AVAILABLE or UNAVAILABLE). Must show as AVAILABLE to be functional. If it is UNAVAILABLE links using it will not align. In this case you should check the IP addressing in the next attributes.

IPADDR1 - IP Address 1
Permission: Writeable
Type: string
Description: Primary IP address of this DRE. A host name from /etc/hosts or an IP address can be used. A host name is preferred.

IPADDR2 - IP Address 2
Permission: Writeable
Type: string
Description: Secondary IP address of this DRE. A host name from /etc/hosts or an IP address can be used. A host name is preferred.

CAGENAME - Cage Name
Permission: Writeable
Type: string
Description: A descriptive name for the chassis running the L2 Connection object. In many case this is the same chassis as the CPU. This attribute is text only and is used for operator informational purposes only.

STATE - State
Permission: Read-only
Type: AvailState={INACTIVE,UNAVAILABLE,AVAILABLE,VERSION MISMATCH}
Description: Status of this L2 Connection (INACTIVE, UNAVAILABLE, VERSION MISMATCH, AVAILABLE). The most common cause of an UNAVAILABLE destination is an IP configuration issue. Should the connection between the DRE and the L2 Connection be UNAVAILABLE, we suggest you see if any of the IP configuration was recently changed and refer to the log messages. VERSION MISMATCH means mismatch between protocol type and protocol version.

MTP2VERSION - MTP2 Protocol Version
Permission: Read-only
Type: int
Description: The Internal Protocol version used to interact with this L2 Connection is displayed in this attribute. It is here for informational purposes only and indicates to Customer Support the relative ages of the software loads being used. The values for Type, MTP2 Protocol Type, and MTP2 Protocol Version are related. These are layers in a protocol between the DRE and the Level 2 modules.

LOCAL_IPADDR1 - Local IP Address 1
Permission: Writeable
Type: string
Description: Primary local address of this L2 Connection. This may be a hostname provisioned in /etc/hosts or an IP Address. This information is only used if the connection between the DRE and MTP2 uses SCTP. TCP/IP does not require knowledge of the local address. This value should not require modification in most configurations.

LOCAL_IPADDR2 - Local IP Address 2
Permission: Writeable
Type: string
Description: Secondary local IP address of this L2 Connection. This may be a hostname provisioned in /etc/hosts or an IP Address. This information is only used if the connection between the DRE and MTP2 uses SCTP. TCP/IP does not require knowledge of the local address. This value should not require modification in most configurations.

LOCAL_L2PORT - Local Port
Permission: Writeable
Type: int(Range: [0..9999])
Description: Local port of L2 Connection. This value is used for SCTP only and should not require modification in most configurations.

REMOTE_IPADDR1 - Remote IP Address 1
Permission: Writeable
Type: string
Description: Primary remote IP address of this L2 Connection. This is the address of an MTP2 process. It should be a hostname provisioned in /etc/hosts or an IP Address. This value should not require modification in most configurations. When the connection to MTP2 uses SCTP, this address is the SCTP Primary Path.

REMOTE_IPADDR2 - Remote IP Address 2
Permission: Writeable
Type: string
Description: Secondary remote IP address of this L2 Connection. This is the address of an MTP2 process. It should be a hostname provisioned in /etc/hosts or an IP Address. This value should not require modification in most configurations.

REMOTE_L2PORT - Remote Port
Permission: Writeable
Type: int(Range: [0..9999])
Description: Remote port of MTP2. This value should not require modification in most configurations.

ASSOCNUM - Association Number
Permission: Read-only
Type: int(Range: [0..2147483647])
Description: SCTP Association Number

HB - Heartbeat
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enabling the Heartbeat Feature causes test message to the remote connection to determine its availability on the network. The default value is ON.

HB_INV - Heartbeat Interval
Permission: Writeable
Type: int(Range: [0..65535])
Description: Heartbeat interval in milliseconds for the SCTP association. The default value is 100 milliseconds.

RTO_INIT - RTO Initial
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Round-Trip Delay (RTO) Initial sets the initial expected time for packets to be sent and returned. Entered in milliseconds. The default is 180 (ms).

RTO_MIN - RTO Minimum
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Round Trip Delay (RTO) Minimum is the smallest expected time for packets to be sent and returned. Entered in milliseconds. The default is 180 (ms).

RTO_MAX - RTO Maximum
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Round Trip Delay (RTO) Maximum is the largest expected time for packets to be sent and returned. Entered in milliseconds. The default is 250 (ms).

MX_PATH_RETRANS - Maximum Path Retrans
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum path retransmissions sets the number of retransmissions that will be attempted over the current transmission path without success before the path is deemed unavailable and a new transmission path is sought. The default value is 10 and is to be used on a good quality local network.

MX_ASSOC_RETRANS - Maximum Assoc Retrans
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum association retransmissions sets the number of retransmissions to a remote device over all possible paths that will be attempted without success before deeming the end device as unavailable. The default value is 15, and is to be used on a good quality local network.

BUNDLING - Bundling
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enabling Bundling allows the bundling of messages into larger packets for greater line efficiency. The default value is ON.

BUNDLING_TO - Bundling TO
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Bundling Time Out (TO) is set in milliseconds and indicates the length of time that messages will be queued before being bundled into larger packets. This is only applicable if the Bundling attribute is set to ON. The default value is 20 milliseconds.

DELAYACK_TO - Delayed ACK TO
Permission: Writeable
Type: DelayedACKTO={DISABLED, 10 to 500}
Description: Delayed Acknowledgement Time Out (ACK TO) sets the time that the system waits after receiving a packet before sending an acknowledgement (10 to 500 ms). To disable Delayed ACK feature, set the value to 0. Default value: 20 ms.

FAST_RETRANS_TH - Fast Retrans Threshold
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Fast Retransmit Threshold sets the number of times a packet can be reported as missing before SCTP on the originating system retransmits packets using fast retransmission. The default value is 4.

CHECKSUM - Checksum
Permission: Writeable
Type: SCTPCheckSum={CRC32C,ADLER32,NONE,AUTO}
Description: Checksum sets the error detection algorithm on the SCTP connection. Valid values are: CRC32C, ADLER32, NONE, or AUTO. Not all options are available on all systems. The default value is CRC32C.

SCTP_DBG_LVL - SCTP Debug Level
Permission: Writeable
Type: int(Range: [0..255])
Description: SCTP debug level determines how much information is tracked and logged to the Debug Log file. It is recommended that one does NOT raise this value on a busy system, so that the CPU is not unduly busy proving log information rather that processing traffic. The values range from 0, meaning no debugging information, to 5, which provides a considerable amount of information. The default value is 1.

CONTIMEOUT - Connection Timeout
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [1000..2147483647])
Description: Connection timeout (ms), the amount of time we wait for a connection to establish before reporting a failure.

CONRETRY - Connection Retry
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [1000..2147483647])
Description: Connection retry interval (ms). This is the amount of time between connection attempts.

CMDTIMEOUT - Command Timeout
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [1000..2147483647])
Description: Command timeout (ms), the amount of time we wait for an acknowledgement of a Link command before declaring the link failed and starting the Command Retry timer.

CMDRETRY - Command Retry
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000} (Units: ms)(Range: [5000..2147483647])
Description: Command Retry (ms). If a command timeout occurs, mark the link as failed. Attempt to recover after this timer expires.

M2UA_VARIANT - M2UA Variant
Permission: Writeable
Type: M2UAFlavour={GENERIC,AUDIOCODES}
Description: M2UA variant. The protocol defined in RFC3331, however there are many aspects described as implementation specific.

DSCP - DSCP
Permissions: Writeable
Type: int
Description: Differentiated Services Code Point is used to classify traffic within a network in order to determine the priority of the various classes of traffic (0 to 63). Default value: 0.

CLLI - CLLI
Permission: Writeable
Type: string
Description: Common Language Location Identifier (CLLI) of this virtual node. This is an informational attribute only.

DESC - Description
Permission: Writeable
Type: string
Description: A textual description of this virtual node. This attribute is for Operator informational purposes only.

STATE - State
Permission: Read-only
Type: ActivationState={INACTIVE,ACTIVE}
Description: The Virtual Node Status indicates if this Vnode is available to be used by a registration to register to. It does NOT indicate whether an application has actually registered to the Vnode. That information can be found on the Level 4 connections screen.

TFA - Broadcast TFA
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFA SS7 messages for this virtual node. It is recommended to leave the broadcast as enabled.

TFP - Broadcast TFP
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFP SS7 messages for this virtual node. It is recommended to leave the broadcast as enabled.

TFR - Broadcast TFR
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFR SS7 messages for this virtual node. It is recommended to leave the broadcast as enabled.

MATE_DIST - Mate STP Distribution
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the mate STP distribution of the virtual node. This feature is set to ENABLED by default. It is modifiable only if the L4Converter is licensed and is set to DISABLED to allow SCCP Relay support. The L4 application is not distributed over the mate STP and thus incoming message must use the C-Link instead of sending the message back up to the application.

COUNT - Count
Permission: Read-only
Type: int
Description: Number of Routeset Lists

ID - Identifier
Permission: Read-only
Type: int
Description: Routeset List Identifier. Internal use only.

CLLI - CLLI
Permission: Writeable
Type: string
Description: Common Language Location Identifier (CLLI) of this routeset.

STATE - Routeset State
Permission: Read-only
Type: RoutesetState={ACTIVE,INACTIVE,XLIST}
Description: Status of this routeset (active, inactive, xlist) xlist means that the routeset was dynamically created by the MTP L3 and has exceptions, such as some routes may not be available.

CNGSTLVL - Congestion Level
Permissions: Read-only
Type: CongestionLevel={FALSE,LEVEL1,LEVEL2,LEVEL3,TRUE}
Description: Congestion level of the routeset. In ANSI, TTC and NTT networks the values range from 1 to 3 or FALSE if not congested. In ITU networks the values are TRUE or FALSE.

DESTSTATE - Destination State
Permission: Read-only
Type: DestState={INACCESSIBLE,ACCESSIBLE,ACCESSIBLE_ALT,MANUALLY_BLOCKED}
Description: Status of the routeset destination. The possible states are, inaccessible, accessible, manually blocked, accessible via alternate route. When a routeset is deactivated the routeset destination state is set to manually blocked and the routeset state is set to inactive whether the destination state is accessible or inaccessible.

TCA - Broadcast TCA
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TCA SS7 messages for this routeset

TCP - Broadcast TCP
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TCP SS7 messages for this routeset

TCR - Broadcast TCR
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TCR SS7 messages for this routeset.

TFA - Broadcast TFA
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFA SS7 messages for this routeset.

TFP - Broadcast TFP
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFP SS7 messages for this routeset.

TFR - Broadcast TFR
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFR SS7 messages for this routeset.

CNGSTNOTIFUPS - Congestion Notif of UPs
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Number of messages between congestion notification of User Part (Default 8). Use of this value limits a flood of congestion notices to a connected application.

ALWXRTST - Allow X-Routesets
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the creation of X-List routesets

TESTSTATE - Test State
Permission: Read-only
Type: SLT={IDLE,WAIT_TRY_1,WAIT_TRY_2,FAILED,SUCCESS}
Description: Signaling Test State is a value used only Japanese and New Zealand networks.

RSID - Routeset ID
Permission: Writeable
Type: RoutesetID={PENDING,UNDEFINED, 0 to 4000}
Description: SONUS_C20 Application ID Mgmt Routeset unique identifier. Valid values: 0 to 4000, PENDING, and UNDEFINED. By default, the attribute is set to UNDEFINED. The PENDING value is a transient value only and cannot be set by the user. The attribute can only be modified if the Application ID Mgmt attribute is set to SONUS_C20. If defined, attribute value must be unique across all NAs. The attribute, if defined, must be reset to UNDEFINED to permit the deletion of the routeset object.

LOADSHARE_MODE - Loadshare Mode
Permission: Writeable
Type: RSLoadShareMode={NODE_VALUE,SLS,SCCP0,ENHANCED SLS,ENHANCED SLS AND SCCP0,TTC AB PLANE}
Description: Loadshare mode affects the algorithm that determines which MSUs are routed on which links (the loadsharing algorithm). When set to 'NODE_VALUE', the load sharing algorithm will be based upon the Loadshare Mode value in the network appearance. The default value is NODE_VALUE. When set to 'SLS', the usual loadsharing algorithm is used, based on the SLS in the incoming MSU. This algorithm is usually satisfactory, but may have drawbacks in some SS7 variants and network configurations in which the range of meaningful SLS values may be limited. Also, MSUs such as SCCP messages with Protocol Class 0 do not have sequencing requirements. When set to 'SCCP0', SCCP messages that do not require sequencing are loadshared evenly between links without regard to the incoming SLS and the outgoing SLS is modified. Other MSUs are loadshared in the usual way using the MSU SLS. When set to 'ENHANCED SLS', a new SLS value is generated based on incoming information such as OPC, DPC and link SLC. When set to 'ENHANCED SLS AND SCCP0', the option will process Protocol class 0 messages first and use the same functionality at SCCP0, plus remaining messages are processed using the same functionality as the ENHANCED SLS option. Applies to SI > 2 messages only. When set to 'TTC AB PLANE' the A/B Plane Bit is used to select the outgoing linkset. This attribute only takes effect if a routeset is using a combined linkset (two routes with equal cost), and if one linkset is configured as a A-plane linkset (using the Linkset 'AB Plane Bit' attribute) and the other linkset is configured as a B-plane linkset. In this case, the A/B Plane Bit in the MSU SLS is used to select the outgoing linkset when sufficient links are available. In some cases there is a trade-off between evenly distributing traffic across available links and respecting the A/B bit for linkset selection. These cases are handled as follows.  If each linkset has half or more its links available, the AB Plane Bit is used to select the outgoing linkset and the other SLS bits are used to select the link within the linkset. If one of the linksets has less than half its links available (''abnormal'' or ''quasi-normal'') but the other linkset has half or more its links available (''normal'' or ''fully normal''), then only one linkset is used for traffic: the linkset with half or more of its links available. If each linkset has less than half its links available, priority is given to making the traffic on each link as even as possible, while respecting the AB Plane Bit when this doesn't further unbalance traffic.

ALARMS - Alarms
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Alarms affect the alarms associated with the Routeset. DISABLED mode: Alarms will not be raised. ENABLED mode: Alarms will be raised. Valid values: ENABLED and DISABLED. Default value: ENABLED

COST - Cost
Permissions: Writeable and Createable
Type: int(Range: [0..100])
Description: Cost of this route

CLLI - CLLI
Permission: Read-only
Type: string
Description: Common Language Location Identifier (CLLI) of the associated linkset.

LINKSETNAME - Linkset Name
Permissions: Read-only
Type: string
Description: Linkset Name of this route.

STATE - State
Permission: Read-only
Type: RouteState={UNAVAILABLE,AVAILABLE,PROHIBITED,RESTRICTED,PROHIBITED_CRDT}
Description: Status of this route (unavailable, available, prohibited, restricted or prohibited_crdt). PROHIBITED_CRDT applies only in ANSI and indicates that the route failed the ANSI Circular Route Detection Test (CRDT). The route remains unavailable until it is reset by maintenance personnel using the Reset State action.

LINKT - Link Type
Permissions: Writeable
Type: LinkType={A_LINK,B_LINK,C_LINK,D_LINK,E_LINK,F_LINK}
Description: Type of SS7 linkset. (A, B, C, D, E, F). Changing the type for the NTT variant to F forces the AB Plane Bit to A, and from F forces it to SLC_ENCODED, and requires the linkset to be empty.

LINKSETNAME - Linkset Name
Permission: Writeable
Type: string
Description: An NA unique linkset name between 2 and 16 characters.

CLLI - CLLI
Permission: Writeable
Type: string
Description: Common Language Location Identifier (CLLI) of this linkset.

STATE - State
Permission: Read-only
Type: LinksetState={INACTIVE,ACTIVE,FAILED}
Description: Status of this linkset (inactive, active, failed)

ABPLANEBIT - AB Plane Bit
Permissions: Writeable
Type: ABPlaneBit={A,B,SLC_ENCODED}
Description: Sets the AB plane bit for TTC links. When set to A or B, the link's SLC value represents the 3-bit LSN in the SLS field. When set to SLC Encoded, the AB plane bit is encoded as part of the link's SLC value. You must delete all the links within the linkset to modify this field. The AB Plane Bit is always set to A for NTT F-links. Default value: SLC Encoded

ROTATESLS - Rotate SLS
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable SLS rotation of MSUs that are sent on this linkset.If SLS rotation is disabled for the node (via the 'MTP3 NA' 'Rotate SLS' attribute) then this parameter has no effect. SLS Rotation is only applied to MSUs with SI at least 3 (SLS is not rotated for MTP3 management messages).

REVROTATESLS - Reverse Rotate SLS
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Reverse rotate the SLS of incoming MSUs.Setting this parameter with traffic running may result in MSU missequencing.SLS Rotation is commonly used in ANSI networks. In some network configurations though SLS rotation can be detrimental, such as when routes via an STP have no cross links.One option in such configurations is to disable SLS rotation on pertinent linksets. If the adjacent node does not support disabling SLS rotation, we can fake it for them by enabling this feature.This feature performs a reverse rotation on the SLS of incoming MSUs before routing/loadsharing decisions or SLS rotation are performed. This modification affects the SLS of the outgoing MSU.If SLS rotation is disabled for the node (via the 'MTP3 NA' 'Rotate SLS' attribute) then this parameter has no effect. Reverse rotation of the SLS is only applied to MSUs with SI at least 3 (it does not apply to MTP3 management messages).

RMMTPRSTSUP - Remote MTP Restart Support
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Adjacent node MTP restart support

RTSTNAME - Routeset List Name
Permission: Writeable
Type: string
Description: Name of the Routeset List used to route MSUs received by this linkset. Routeset Lists are represented by Routeset List objects. Changing this value while traffic is running will likely cause MSU missequencing.

IMF - IMF Support
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Integrated Monitoring Feed feature support for this linkset. IMF must be licensed to enable this attribute. All the linkset IMF Support attributes can be cleared simultaneously by using the Reset IMF action in the Linksets object.

ALARMS - Alarms
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Alarms affect the alarms associated with the Linkset. DISABLED mode: Alarms will not be raised. ENABLED mode: Alarms will be raised.
Valid values: ENABLED and DISABLED

PCMAPPING - PC Mapping Table Name
Permissions: Writeable
Type: string
Description: An existing NA PC Mapping table name. (up to 32 characters). Default value: Empty, no mapping is applied.

USRACTV - User Activated
Permission: Read-only
Type: Feature={DISABLED,ENABLED}
Description: Attempt to activate when possible

TCA - Broadcast TCA
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TCA SS7 messages for this linkset

TCP - Broadcast TCP
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TCP SS7 messages for this linkset

TCR - Broadcast TCR
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TCR SS7 messages for this linkset

TFA - Broadcast TFA
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFA SS7 messages for this linkset

TFP - Broadcast TFP
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFP SS7 messages for this linkset

TFR - Broadcast TFR
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the broadcasting of TFR SS7 messages for this linkset.

NI - Network Indicator
Permissions: Writeable
Type: NetIdLS={NODE_VALUE,NI_00,NI_01,NI_10,NI_11}
Description: Network Indicator override on a per linkset basis. By default, the MTP3 NA attribute is used (NODE_VALUE). If set to a value other than NODE_VALUE, the 2 bit value identifying the network in the MTP3 service indicator octet are overwritten to the specified value (NI_00, NI_01, NI_10, or NI_11) on incoming and outgoing MSUs from/to the associated links. Modification requires the linkset to be inactive.

SISLT - SLT SI
Permission: Writeable
Type: LS_SIForSlt={NODE_VALUE,NTM_REGULAR,NTM_SPECIAL}
Description: The SI used for SLT messages. NODE_VALUE sets the value based on Node Value NTM_REGULAR uses the SI value 1 NTM_SPECIAL uses the SI value 2

SLTMPATTERN - SLTM Pattern
Permission: Writeable
Type: string
Description: The Test Pattern Used for SLTM messages (hex format) Enter as a string representing the hex value (for example, AABBCCDD)

RPTSLT - Repeat SLT
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the repeating of Signaling Link Test Message (SLTM or SRT in Japan) SS7 messages for this linkset.

OPC_VERIFICATION - OPC Verification
Permission: Writeable
Type: opcVerification={LPC MATE PC,ENABLED,NONE,LPC}
Description: OPC Verification. Please do not change this attribute unless instructed by Customer Support. OPC Verification is defined in GR82CORE Issue 10 Section 4.2.7 'OPC Verification' to provide some protection against an entity transmitting an MSU using an OPC that is valid but does not belong to that entity (OPC Spoofing). The behaviour is slightly different for MSUs received on a C-link linkset compared to another linkset type. MSUs with the OPC of the Mate STP are accepted from a C-link linkset regardless of the value in this attribute. For a linkset other than the linkset to the Mate STP (not a C-linkset): If the 'OPC Verification' attribute is set to ENABLED then the DSC discards MSUs received on this linkset that have OPC set to the Local Point Code (LPC), the point code of the Mate STP (Mate STP PC) or the point code of a VNode. When 'OPC Verification' is set to LPC_MATEPC then the DSC discards MSUs received on this linkset that have OPC set to the LPC or the Mate STP PC. When 'OPC Verification' is set to LPC then the DSC discards MSUs received on this linkset that have OPC set to the LPC. When 'OPC Verification' is set to NONE then no OPC Verification is performed. For a linkset to the Mate STP (a C-linkset), MSUs with the OPC set to the Mate STP PC always pass OPC Verification. Hence the OPC Verification checks on a C-linkset are as follows: When the 'OPC Verification' attribute is set to ENABLED the STP discards MSUs received on this linkset that have OPC set to the LPC or the point code of a VNode. An MSU received with the OPC set to the Mate STP PC is not discarded. When 'OPC Verification' is set to LPC_MATEPC MSUs received on this linkset and an MSU is received on this linkset that has OPC set to the LPC of the DSC then the MSU is discarded. An MSU received with the OPC set to the Mate STP PC is not discarded. When 'OPC Verification' is set to LPC and an MSU is received on this linkset that has OPC set to the LPC of the DSC then the MSU is discarded. When 'OPC Verification' is set to NONE, no OPC verification is performed. OPC Verification failures are typically caused by either a circular route or by OPC Spoofing. Either case can cause problems on its own. For instance, OPC spoofing can make network troubleshooting more difficult and may impair the effectiveness of MTP Transfer Controlled procedures (for managing congestion). It is strongly recommended to address the root cause of OPC Verification failures rather than disabling this attribute. This attribute defaults to ENABLED for all linksets except C-link linksets. This attribute defaults to LPC_MATEPC for C-link linksets to support configurations with a protocol converter or PCE where R4-8 compliance at the Mate STP may have been disabled.

LONG_MSU_SUPPORT - Long MSU Support
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or Disable support for MSUs greater than 273 bytes. This attribute defaults to DISABLED

LONG_MSU_PROVING - Long MSU Proving
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or Disable support proving with long MSUs greater than 273 bytes. This attribute defaults to ENABLED. Long MSU proving messages are only sent if the Long MSU Support feature is ENABLED. The length of the proving messages is defined by the Maximum MSU Length value for the NA.

SCTP_CLIENT - SCTP Client
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: All M3UA MG and IPSP links in the linkset operate as an SCTP Client if enabled. The Client is the process that initiates establishing the SCTP association. When disabled the links operate as an SCTP Server. Only IPSP links support both client and server. MG links support client.

M3UA_CLIENT - M3UA Client
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description:  All M3UA MG and IPSP links in the linkset operate as an M3UA Client if enabled. The Client is the process that initiates activation of the link at the M3UA level. When disabled the links operate as an M3UA Server. Only IPSP links support both client and server. MG links support client.

M3UA_MG_SPC - M3UA MG Shared PC
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: All M3UA MG links in the linkset will operate as shared PCs

M3UA_SSNM_MSGS - Extended SSNM Messages
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: When enabled all M3UA SG and Server links in the linkset will send/receive additional Signalling Network Management Messages. When using Sigtran to connect STPs we recommend using M2PA links. This flag provides additional SSNM messages for cases where customers are unable to use M2PA or need to use one of our M3UA link types. The flag enables SG links to transmit the M3UA equivalent TFMs ie. M3UA DUNA and DAVA. The flag enables Server links to transmit the M3UA equivalent of RSP and RSTs ie. M3UA DAUD. The flag is disabled by default. 

TXABTL1 - TX Abatement L1
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Congestion Abatement Level 1 (% of buffer usage)

TXONSTL1 - TX Onset L1
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Congestion Onset Level 1 (% of buffer usage)

TXABTL2 - TX Abatement L2
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Congestion Abatement Level 2 (% of buffer usage)

TXONSTL2 - TX Onset L2
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Congestion Onset Level 2 (% of buffer usage)

TXABTL3 - TX Abatement L3
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Congestion Abatement Level 3 (% of buffer usage)

TXONSTL3 - TX Onset L3
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Congestion Onset Level 3 (% of buffer usage)

M2PA_RXABT_BUSY - M2PA RX Abatement Busy
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Receive Congestion Abatement Busy (bytes per second). When the M2PA RX Abatement value is cleared (less than) on a given link and the link was previously set to locally busy, an M2PA LSBE message is sent on the link to notify the adjacent point code of the end of the local congestion. Applies to both the D6 and RFC-4165 M2PA versions.

M2PA_RXONST_BUSY - M2PA RX Onset Busy
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Receive Congestion Onset Busy (bytes per second). When the M2PA RX Onset Busy value is reached on a given link, an M2PA LSB message is sent on the link to notify the adjacent point code of the local congestion. Applies to both the D6 and RFC-4165 M2PA versions.

M2PA_TXQSIZE - M2PA TX Queue Size
Permission: Writeable
Type: int(Range: [4000..2147483647])
Description: Size of the M2PA Transmit and Retransmit buffer (Bytes). The M2PA TX Queue Size attribute is used to determine the congestion TX percentage based on the current transmit and retransmit buffer size and maps the value to the appropriate TX Abatement and Onset congestion levels. The congestion level will be updated and displayed on a per link basis in the M2PA Link Congestion Level attribute as required. If an outgoing M2PA message has its message length + the retransmit buffer and the transmit buffer exceed the M2PA TX Queue Size, the message is discarded. Applies to both the D6 and RFC-4165 M2PA versions.

M2PA_RTBSIZE - M2PA RTB Size
Permission: Writeable
Type: int(Range: [4000..500000])
Description: Size of the M2PA Retransmit buffer (Bytes). A larger RTB generally improves throughput but decreases responsiveness. More specifically, with a larger RTB the other end may need to wait longer for M2PA Data Acknowledgment. This value is only used with RFC 4165 links.

LU_PERCT - Usage Percentage
Permission: Writeable
Type: int
Description: Link usage alarm is triggered when average traffic in percentage exceeds the value entered in this attribute. The average is calculated over period of time defined in Usage Interval Minutes and Usage Interval Seconds.

LU_MIN - Usage Interval Minutes
Permission: Read-only
Type: int
Description: Link Usage Interval Minutes defines time interval in minutes used for calculating average traffic load.

LU_SEC - Usage Interval Seconds
Permission: Read-only
Type: int
Description: Link Usage Interval Seconds defines time interval in seconds used for calculating average traffic load.

ERRCM - Error Correction Mode
Permission: Writeable
Type: ErrorCorrection={BASIC,PCR}
Description: Error Correction Mode (BASIC, Preventive Cyclic Retransmission (PCR))

NAERM - NAERM
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Normal Alignment Error Rate Monitor Threshold

EAERM - EAERM
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Emergency Alignment Error Rate Monitor Threshold

SUERM - SUERM
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Signal Unit Error Rate Monitor Threshold

MXMSURTB - Maximum MSUs RTB
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum MSUs in Retransmit Buffer before forced retransmission (PCR only)

MXOCTRTB - Maximum Octets RTB
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum Octets in Retransmit Buffer before forced retransmission (PCR only)

HB - Heartbeat
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable the Heartbeat Feature.

HB_INV - Heartbeat Interval
Permission: Writeable
Type: int(Range: [0..65535])
Description: Heartbeat interval (ms).

RTO_INIT - RTO Initial
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Initial (ms).

RTO_MIN - RTO Minimum
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Minimum (ms).

RTO_MAX - RTO Maximum
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Maximum (ms).

MX_PATH_RETRANS - Maximum Path Retrans
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum path retransmissions.

MX_ASSOC_RETRANS - Maximum Assoc Retrans
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum association retransmissions.

BUNDLING - Bundling
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Enable or disable Bundling.

BUNDLING_TO - Bundling TO
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Bundling TO (ms).

DELAYACK_TO - Delayed ACK TO
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Delayed ACK TO (ms).

FAST_RETRANS_TH - Fast Retrans Threshold
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Fast Retransmit Threshold.

CHECKSUM - Checksum
Permission: Writeable
Type: SCTPCheckSum={CRC32C,ADLER32,NONE,AUTO}
Description: SCTP Checksum

BYTES_B4_ACK - Bytes Before Ack
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Acknowledgment Threshold (Bytes) - If this many bytes of User Data have been received but not acknowledged then an explicit acknowledgment is generated.

MSG_B4_ACK - Messages Before Ack
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Acknowledgment Threshold (Message Count) - If this many User Data messages have been received but not acknowledged then an explicit acknowledgment is generated.

PROVING_MSG_SZ - Proving Message Size
Permissions: Writeable
Type: ProvingMsuSize={0 to 4092} (Units: bytes)
Description: Proving Message Size (bytes) - Only applicable for M2PA links. If Long MSU proving is enabled, this value is ignored.

DSCP - DSCP
Permission: Writeable
Type: int(Range: [0..63])
Description: Differentiated Services Code Point is used to classify traffic within a network in order to determine the priority of the various classes of traffic (0 to 63).
Default value: 0.

L2T1 - L2 T1
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Aligned/Ready ( 13,000 ms ) [ANSI], ( 4.8 Kbps: 500,000-600,000 ms, 64 Kbps: 40,000-50,000 ms ) [ITU] ( suggested, 15,000 ms ) [JT]

ANNEXAT1 - Annex A T1
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [25000..350000])
Description: Aligned/Ready For Annex A links (Q.703) range 25-350s default 300000 ms

L2T2 - L2 T2
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Not Aligned ( 11,500 - 23,000 ms ) [ANSI], ( 5,000 - 150,000 ms) [ITU] ( suggested, 480,000 ms ) [JT]

L2T3 - L2 T3
Permissions: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..1e+07])
Description: Aligned ( 11,500 ms ) [ANSI], ( 1,500 ms ) [ITU], ( suggested, 3,000 ms ) [JT]

L2T4e - L2 T4e
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Proving period ( 2^12 octets, 600 ms ) [ANSI] Proving period ( 2^12 octets, 4.8 Kbps: 6000-8000 ms, 64 Kbps: 400-600 ms ) [ITU] ( suggested, 3,000 ms ) [JT]

L2T4n - L2 T4n
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Proving period ( 2^14 octets, 2300 ms) [ANSI] ( 2^16 octets, 4.8 Kbps: 100,000-120,000 ms, 64 Kbps: 7500-9500 ms) [ITU] N/A [JT]

ANNEXAT4N - Annex A T4n
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [3000..70000])
Description: Proving Period for Annex A links (Q.703) range 3-70s, default 30000 ms

L2T5 - L2 T5
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Sending SIB ( 80 - 120 ms ) [ANSI/ITU] (suggested, 200 ms ) [JT]

L2T6 - L2 T6
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Remote Congestion ( 4.8 Kbps: 8000 - 12000 ms, 64 Kbps: 3000 - 6000 ms ) [ANSI/ITU] ( suggested, 3,000 ms ) [JT]

L2T7 - L2 T7
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Excessive delay of ACK ( 4.8 Kbps: 4000 - 6000 ms, 64 Kbps: 500 - 2000 ms ) [ANSI/ITU] ( suggested, 2,000 ms ) [JT]

 L3T1 - L3 T1
Permissions: Writeable
Type: LinksetTimer={NODE VALUE, 0 to 10000000}
Description: Changeover delay ( 500 - 1200 ms ) [ANSI/ITU/JT]. The default value is NODE VALUE. Setting MTP Level 3 timers on the Linkset to a value other than NODE VALUE overrides the value from the NA and affects all links in the linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T2 - L3 T2
Permissions: Writeable
Type: LinksetTimer={NODE VALUE, 0 to 10000000}
Description: Waiting for COA ( 700 - 2000 ms ) [ANSI/ITU/JT]. The default value is NODE VALUE. Setting MTP Level 3 timers on the Linkset to a value other than NODE VALUE overrides the value from the NA and affects all links in the linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T3 - L3 T3
Permissions: Writeable
Type: LinksetTimer={NODE VALUE, 0 to 10000000}
Description: Changeback delay ( 500 - 1200 ms ) [ANSI/ITU/JT]. The default value is NODE VALUE. Setting MTP Level 3 timers on the Linkset to a value other than NODE VALUE overrides the value from the NA and affects all links in the linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T4 - L3 T4
Permissions: Writeable
Type: LinksetTimer={NODE VALUE, 0 to 10000000}
Description: Waiting for CBA: first attempt ( 500 - 1200 ms ) [ANSI/ITU/JT]. The default value is NODE VALUE. Setting MTP Level 3 timers on the Linkset to a value other than NODE VALUE overrides the value from the NA and affects all links in the linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

L3T6 - L3 T6
Permissions: Writeable
Type: LinksetTimer={NODE VALUE, 0 to 10000000}
Description: Controlled rerouting delay ( 500 - 1200 ms ) [ANSI/ITU/JT]. The default value is NODE VALUE. Setting MTP Level 3 timers on the Linkset to a value other than NODE VALUE overrides the value from the NA and affects all links in the linkset. CAUTION: It is recommended that you do not change the timer default values unless instructed otherwise by Customer Support. Timer values should be modified with care, especially on a live system. Interaction of timers trough the various MTP3 procedures is complex and changing them incorrectly can reduce system stability.

SLTMT1 - SLTM T1
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: SLTM Timer 1 defines interval (4 - 12 sec) that Signaling Link Test Message (SLTM) [ANSI/ITU] or Signaling Routing Test message (SRT) [TTC/NTT] message must be acknowledged. A value of 0 shuts off the timer and SLTM/SRT signaling.

SLTMT2 - SLTM T2
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: SLTM Timer 2 defines interval (30-90 sec) when Signaling Link Test Message (SLTM) [ANSI/ITU] or Signaling Routing Test (SRT) message [TTC/NTT] is periodically repeated. A value of 0 shuts off the timer and SLTM/SRT signaling.

RFC4165_T1 - RFC 4165 T1
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Alignment Ready. References:  - Q.703 Timer T1  - T1.111.3 Timer T1  - M2PA RFC 4165 (www.ietf.org)  - draft-bidulock-sigtran-m2pa-test-06.txt. The default value is taken from draft-bidulock-sigtran-m2pa-test-06.txt and is consistent with Q.703.

RFC4165_T2 - RFC 4165 T2
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Timer Not Aligned. References:  - Q.703 Timer T2  - T1.111.3 Timer T2  - M2PA RFC 4165 (www.ietf.org)  - draft-bidulock-sigtran-m2pa-test-06.txt. The default value is taken from draft-bidulock-sigtran-m2pa-test-06.txt and is consistent with Q.703.

RFC4165_T3 - RFC 4165 T3
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Timer Aligned. References:  - Q.703 Timer T3  - T1.111.3 Timer T3  - M2PA RFC 4165 (www.ietf.org)  - draft-bidulock-sigtran-m2pa-test-06.txt. The default value is taken from draft-bidulock-sigtran-m2pa-test-06.txt and is consistent with Q.703.

RFC4165_T4n - RFC 4165 T4n
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Timer Proving Normal. References:  - Q.703 Timer T4n  - T1.111.3 Timer T4n  - M2PA RFC 4165 (www.ietf.org)  - draft-bidulock-sigtran-m2pa-test-06.txt. The default value is taken from  draft-bidulock-sigtran-m2pa-test-06.txt and is consistent with Q.703.

RFC4165_T4e - RFC 4165 T4e
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Timer Proving Emergency. References:  - Q.703 Timer T4e  - T1.111.3 Timer T4e  - M2PA RFC 4165 (www.ietf.org)  - draft-bidulock-sigtran-m2pa-test-06.txt. The default value is taken from draft-bidulock-sigtran-m2pa-test-06.txt and is consistent with Q.703.

RFC4165_T6 - RFC 4165 T6
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Timer Remote Congestion. References:  - Q.703 Timer T6  - T1.111.3 Timer T6  - M2PA RFC 4165 (www.ietf.org)  - draft-bidulock-sigtran-m2pa-test-06.txt. The default value is taken from draft-bidulock-sigtran-m2pa-test-06.txt and is consistent with Q.703.

RFC4165_T7 - RFC 4165 T7
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Timer Excessive Delay of Acknowledgment. References:  - Q.703 Timer T7  - T1.111.3 Timer T7  - M2PA RFC 4165 (www.ietf.org)  - draft-bidulock-sigtran-m2pa-test-06.txt. The default value is consistent with Q.703.

RFC4165_STATINV - RFC 4165 Status Interval
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Status Interval. The frequency with which LS Processor Outage messages are sent while LPO.

RFC4165_PROVRATE - RFC 4165 Proving Rate
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Proving Rate. The frequency with which LS Proving messages are sent while proving.

RFC4165_ACKINV - RFC 4165 Acknowledgement Interval
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Maximum time interval before explicitly acknowledging User Data. This can be important in the case of unidirectional or low traffic.

DRAFTV6_T1 - Draft 6 T1
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Alignment - Range 1 - 60 seconds with default of 10 seconds. These values are taken from draft-ietf-sigtran-m2pa-06.txt.

DRAFTV6_T3 - Draft 6 T3
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Ready - Range 1 - 60 seconds with default of 10 seconds. These values are taken from draft-ietf-sigtran-m2pa-06.txt.

DRAFTV6_T4n - Draft 6 T4n
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Proving Normal - Range 1-60 seconds with default of 10 seconds. These values are taken from draft-ietf-sigtran-m2pa-06.txt.

DRAFTV6_T4e - Draft 6 T4e
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Proving Emergency - Range 400-600 ms with default of 500 ms. These values are taken from draft-ietf-sigtran-m2pa-06.txt.

DRAFTV6_T6 - Draft 6 T6
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Remote Congestion - Range 1-6 seconds with default of 3 seconds. The range is taken from draft-ietf-sigtran-m2pa-06.txt, the default value is implementation dependent.

DRAFTV6_T7 - Draft 6 T7
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Excessive Delay in Acknowledgment - Range 0.5 - 2 seconds with default of 2 seconds. The range is taken from draft-ietf-sigtran-m2pa-06.txt, the default value is implementation dependent.

DRAFTV6_STATINV - Draft 6 Status Interval
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Status Interval - default 1 second, The frequency with which LS Processor Outage messages are sent while LPO (implementation dependent)

DRAFTV6_PROVRATE - Draft 6 Proving Rate
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Proving Rate- default 0.1 second, The frequency with which LS Proving messages are sent while proving (implementation dependent)

DRAFTV6_ACKINV - Draft 6 Acknowledgement Interval
Permission: Writeable
Type: Timer={DEFAULT, 0 to 10000000}  (Units: ms)(Range: [0..2147483647])
Description: Maximum time interval before explicitly acknowledging User Data. This can be important in the case of unidirectional or low traffic (implementation dependent).

PCMAPPING - PC Mapping Table Name
Permissions: Writeable
Type: string
Description: An existing NA PC Mapping table name. (up to 32 characters). Default value: Empty, no mapping is applied.

MONITOR - Monitoring
Permissions: Read-only
Type: Feature={DISABLED,ENABLED}
Description: Traffic Monitoring (ENABLED/DISABLED)

SLC00RX - SLC 00 Rx
Permissions: Read-only
Type: string
Description: SLC 0 Rx Erlang

SLC00TX - SLC 00 Tx
Permissions: Read-only
Type: string
Description: SLC 0 Tx Erlang

SLC01RX - SLC 01 Rx
Permissions: Read-only
Type: string
Description: SLC 1 Rx Erlang

SLC01TX - SLC 01 Tx
Permissions: Read-only
Type: string
Description: SLC 1 Tx Erlang

SLC02RX - SLC 02 Rx
Permissions: Read-only
Type: string
Description: SLC 2 Rx Erlang

SLC02TX - SLC 02 Tx
Permissions: Read-only
Type: string
Description: SLC 2 Tx Erlang

SLC03RX - SLC 03 Rx
Permissions: Read-only
Type: string
Description: SLC 3 Rx Erlang

SLC03TX - SLC 03 Tx
Permissions: Read-only
Type: string
Description: SLC 3 Tx Erlang

SLC04RX - SLC 04 Rx
Permissions: Read-only
Type: string
Description: SLC 4 Rx Erlang

SLC04TX - SLC 04 Tx
Permissions: Read-only
Type: string
Description: SLC 4 Tx Erlang

SLC05RX - SLC 05 Rx
Permissions: Read-only
Type: string
Description: SLC 5 Rx Erlang

SLC05TX - SLC 05 Tx
Permissions: Read-only
Type: string
Description: SLC 5 Tx Erlang

SLC06RX - SLC 06 Rx
Permissions: Read-only
Type: string
Description: SLC 6 Rx Erlang

SLC06TX - SLC 06 Tx
Permissions: Read-only
Type: string
Description: SLC 6 Tx Erlang

SLC07RX - SLC 07 Rx
Permissions: Read-only
Type: string
Description: SLC 7 Rx Erlang

SLC07TX - SLC 07 Tx
Permissions: Read-only
Type: string
Description: SLC 7 Tx Erlang

SLC08RX - SLC 08 Rx
Permissions: Read-only
Type: string
Description: SLC 8 Rx Erlang

SLC08TX - SLC 08 Tx
Permissions: Read-only
Type: string
Description: SLC 8 Tx Erlang

SLC09RX - SLC 09 Rx
Permissions: Read-only
Type: string
Description: SLC 9 Rx Erlang

SLC09TX - SLC 09 Tx
Permissions: Read-only
Type: string
Description: SLC 9 Tx Erlang

SLC10RX - SLC 10 Rx
Permissions: Read-only
Type: string
Description: SLC 10 Rx Erlang

SLC10TX - SLC 10 Tx
Permissions: Read-only
Type: string
Description: SLC 10 Tx Erlang

SLC11RX - SLC 11 Rx
Permissions: Read-only
Type: string
Description: SLC 11 Rx Erlang

SLC11TX - SLC 11 Tx
Permissions: Read-only
Type: string
Description: SLC 11 Tx Erlang

SLC12RX - SLC 12 Rx
Permissions: Read-only
Type: string
Description: SLC 12 Rx Erlang

SLC12TX - SLC 12 Tx
Permissions: Read-only
Type: string
Description: SLC 12 Tx Erlang

SLC13RX - SLC 13 Rx
Permissions: Read-only
Type: string
Description: SLC 13 Rx Erlang

SLC13TX - SLC 13 Tx
Permissions: Read-only
Type: string
Description: SLC 13 Tx Erlang

SLC14RX - SLC 14 Rx
Permissions: Read-only
Type: string
Description: SLC 14 Rx Erlang

SLC14TX - SLC 14 Tx
Permissions: Read-only
Type: string
Description: SLC 14 Tx Erlang

SLC15RX - SLC 15 Rx
Permissions: Read-only
Type: string
Description: SLC 15 Rx Erlang

SLC15TX - SLC 15 Tx
Permissions: Read-only
Type: string
Description: SLC 15 Tx Erlang

DRE_ID - DRE ID
Permission: Read-only
Type: int
Description: DRE to own this link.

CAGE - Cage
Permission: Writeable
Type: int(Range: [-1..64])
Description: Cage used by this link.

CHASSIS_SLOT - Chassis Slot
Permission: Writeable
Type: int(Range: [-1..255])
Description: Chassis Slot used by this link.

CHANNEL - Channel
Permission: Writeable
Type: int(Range: [-1 | 1..65535])
Description: Channel used by this link.

LINK_NAME - Link Name
Permissions: Read-only
Type: string
Description: Link Name based on the Linkset Name.

L2_STATE - L2 State
Permission: Read-only
Type: L2LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,FAILED,LOCAL_PROC_OUTAGE,REM_PROC_OUTAGE,BO_PROC_OUTAGE,LOCAL_LOOPBACK,NOT_ENABLED,NOT_INITIALIZED,USER_SHUTDOWN}
Description: Status of MTP Level 2 for this link. Deactivated, Proving, In-Service, Out of Service, Failed, Local Processor Outage, Remote Processor Outage, Both Processor Outage, Local Loopback mode, Not Enabled, Not Initialized

L3_STATE - L3 State
Permission: Read-only
Type: L3LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,LOCALLY_INHIBITED,REM_INHIBITED,BOTH_INHIBITED,BLOCKED,BLOCKED_INHIBITED,LOCAL_PROC_OUTAGE}
Description: Status of MTP Level 3 for this link. Deactivated, Proving, In-Service, Out of Service, Locally Inhibited, Remotely Inhibited, Both Inhibited, Blocked, Blocked and inhibited, Local Processor Outage

CONGESTION_LVL - Congestion Level
Permissions: Read-only
Type: CongestionLevel={FALSE,LEVEL1,LEVEL2,LEVEL3,TRUE}
Description: Congestion level of this link. For ANSI, TTC and NTT networks the values range from 1 to 3 or FALSE if not congested. For ITU networks the value is either TRUE or FALSE.

RXMSU - Rx MSU Count
Permissions: Read-only
Type: int
Description: Received MSU count, per second.

TXMSU - Tx MSU Count
Permissions: Read-only
Type: int
Description: Transmitted MSU count, per second.

DIAG_MSG - Diagnostic Message
Permission: Read-only
Type: string
Description: Link management diagnostic message

ALARMS - Alarms
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Alarms affect the alarms associated with the Link. DISABLED mode: Alarms will not be raised. ENABLED mode: Alarms will be raised. Valid values: ENABLED and DISABLED. Default value: ENABLED.

USR_ACTIVATED - User Activated
Permission: Read-only
Type: Feature={DISABLED,ENABLED}
Description: Link activation flag. Used on stack restart for alignment attempt.

L2_DBG_LVL - L2 Debug Level
Permission: Writeable
Type: int(Range: [0..3])
Description: MTP Level 2 Debug Level

DRE_ID - DRE ID
Permission: Read-only
Type: int
Description: DRE to own this link.

CAGE - Cage
Permission: Writeable
Type: int(Range: [-1..64])
Description: Cage used by this link

LINK_NAME - Link Name
Permissions: Read-only
Type: string
Description: Link Name based on the Linkset Name.

CHANNEL - Channel
Permission: Writeable
Type: int(Range: [-1 | 1..8])
Description: Channel used by this link, valid values are 1 to 8

RXMSU - Rx MSU Count
Permissions: Read-only
Type: int
Description: Received MSU count, per second.

TXMSU - Tx MSU Count
Permissions: Read-only
Type: int
Description: Transmitted MSU count, per second.

L2_STATE - L2 State
Permission: Read-only
Type: L2LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,FAILED,LOCAL_PROC_OUTAGE,REM_PROC_OUTAGE,BO_PROC_OUTAGE,LOCAL_LOOPBACK,NOT_ENABLED,NOT_INITIALIZED,USER_SHUTDOWN}
Description:  Status of MTP Level 2 for this link. Deactivated, Proving, In-Service, Out of Service, Failed, Local Processor Outage, Remote Processor Outage, Both Processor Outage, Local Loopback mode, Not Enabled, Not Initialized

L3_STATE - L3 State
Permission: Read-only
Type: L3LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,LOCALLY_INHIBITED,REM_INHIBITED,BOTH_INHIBITED,BLOCKED,BLOCKED_INHIBITED,LOCAL_PROC_OUTAGE}
Description: Status of MTP Level 3 for this link. Deactivated, Proving, In-Service, Out of Service, Locally Inhibited, Remotely Inhibited, Both Inhibited, Blocked, Blocked and Uninhibited, Local Processor Outage

CONGESTION_LVL - Congestion Level
Permissions: Read-only
Type: CongestionLevel={FALSE,LEVEL1,LEVEL2,LEVEL3,TRUE}
Description: Congestion level of this link. For ANSI networks the values range from 1 to 3 or FALSE if not congested. For ITU networks the value is either TRUE or FALSE.

DIAG_MSG - Diagnostic Message
Permission: Read-only
Type: string
Description: Link management diagnostic message

ALARMS - Alarms
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Alarms affect the alarms associated with the Link. DISABLED mode: Alarms will not be raised. ENABLED mode: Alarms will be raised. Valid values: ENABLED and DISABLED. Default value: ENABLED

USR_ACTIVATED - User Activated
Permission: Read-only
Type: Feature={DISABLED,ENABLED}
Description: Link activation flag. Used on stack restart for alignment attempt.

L2_DBG_LVL - L2 Debug Level
Permission: Writeable
Type: int(Range: [0..3])
Description: MTP Level 2 Debug Level

DRE_ID - DRE ID
Permission: Read-only
Type: int
Description: DRE to own this link.

CAGE - Cage
Permission: Writeable
Type: int(Range: [-1..64])
Description: Cage used by this link

CHASSIS_SLOT - Chassis Slot
Permission: Writeable
Type: int(Range: [-1..255])
Description: Chassis Slot used by this link

CHANNEL - Channel
Permission: Writeable
Type: int(Range: [-1 | 1..65535])
Description: Channel used by this link

LINK_NAME - Link Name
Permissions: Read-only
Type: string
Description: Link Name based on the Linkset Name.

RXMSU - Rx MSU Count
Permissions: Read-only
Type: int
Description: Received MSU count, per second.

TXMSU - Tx MSU Count
Permissions: Read-only
Type: int
Description: Transmitted MSU count, per second.

L2_STATE - L2 State
Permission: Read-only
Type: L2LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,FAILED,LOCAL_PROC_OUTAGE,REM_PROC_OUTAGE,BO_PROC_OUTAGE,LOCAL_LOOPBACK,NOT_ENABLED,NOT_INITIALIZED,USER_SHUTDOWN}
Description: Status of MTP Level 2 for this link. Deactivated, Proving, In-Service, Out of Service, Failed, Local Processor Outage, Remote Processor Outage, Both Processor Outage, Local Loopback mode, Not Enabled, Not Initialized

L3_STATE - L3 State
Permission: Read-only
Type: L3LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,LOCALLY_INHIBITED,REM_INHIBITED,BOTH_INHIBITED,BLOCKED,BLOCKED_INHIBITED,LOCAL_PROC_OUTAGE}
Description: Status of MTP Level 3 for this link. Deactivated, Proving, In-Service, Out of Service, Locally Inhibited, Remotely Inhibited, Both Inhibited, Blocked, Blocked and Uninhibited, Local Processor Outage

CONGESTION_LVL - Congestion Level
Permission: Read-only
Type: CongestionLevel={FALSE,LEVEL1,LEVEL2,LEVEL3,TRUE}
Description: Congestion level of this link. For ANSI networks the values range from 1 to 3 or FALSE if not congested. For ITU networks the value is either TRUE or FALSE.

DIAG_MSG - Diagnostic Message
Permission: Read-only
Type: string
Description: Link management diagnostic message

ALARMS - Alarms
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Alarms affect the alarms associated with the Link. DISABLED mode: Alarms will not be raised. ENABLED mode: Alarms will be raised. Valid values: ENABLED and DISABLED. Default value: ENABLED.

USR_ACTIVATED - User Activated
Permission: Read-only
Type: Feature={DISABLED,ENABLED}
Description: Link activation flag. Used on stack restart for alignment attempt.

L2_DBG_LVL - L2 Debug Level
Permission: Writeable
Type: int(Range: [0..3])
Description: MTP Level 2 Debug Level

DRE_ID - DRE ID
Permission: Read-only
Type: int
Description: DRE to own this link.

CAGE - Cage
Permission: Writeable
Type: int(Range: [-1..64])
Description: Cage used by this link

IID - IID
Permission: Writeable
Type: int(Range: [-1 | 1..65534])
Description: Channel used by this link

L2_STATE - L2 State
Permission: Read-only
Type: L2LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,FAILED,LOCAL_PROC_OUTAGE,REM_PROC_OUTAGE,BO_PROC_OUTAGE,LOCAL_LOOPBACK,NOT_ENABLED,NOT_INITIALIZED,USER_SHUTDOWN}
Description: Status of MTP Level 2 for this link. Deactivated, Proving, In-Service, Out of Service, Failed, Local Processor Outage, Remote Processor Outage, Both Processor Outage, Local Loopback mode, Not Enabled, Not Initialized

L3_STATE - L3 State
Permission: Read-only
Type: L3LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,LOCALLY_INHIBITED,REM_INHIBITED,BOTH_INHIBITED,BLOCKED,BLOCKED_INHIBITED,LOCAL_PROC_OUTAGE}
Description: Status of MTP Level 3 for this link. Deactivated, Proving, In-Service, Out of Service, Locally Inhibited, Remotely Inhibited, Both Inhibited, Blocked, Blocked and Uninhibited, Local Processor Outage

RXMSU - Rx MSU Count
Permissions: Read-only
Type: int
Description: Received MSU count, per second.

TXMSU - Tx MSU Count
Permissions: Read-only
Type: int
Description: Transmitted MSU count, per second.

CONGESTION_LVL - Congestion Level
Permission: Read-only
Type: CongestionLevel={FALSE,LEVEL1,LEVEL2,LEVEL3,TRUE}
Description: Congestion level of this link. For ANSI networks the values range from 1 to 3 or FALSE if not congested. For ITU networks the value is either TRUE or FALSE.

DIAG_MSG - Diagnostic Message
Permission: Read-only
Type: string
Description: Link management diagnostic message

OSC_FILTER - Link Oscillation Filter
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Link Oscillation Filter. The timer can be enabled by setting this attribute to ENABLED. It can be disabled by setting this filed to DISABLED. The timer if enabled, prevents this M2UAlink from oscillating between aligned and non-aligned states repeatedly. It works in ANSI only using timer value from T32.

DLINK_BANDWITH - DataLink Bandwidth
Permission: Writeable
Type: LinkBandwidth={FIFTY_SIX_KBPS,SIXTY_FOUR_KBPS}
Description: Link Baud Rate used to calculate Erlang.

ALARMS - Alarms
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Alarms affect the alarms associated with the Link. DISABLED mode: Alarms will not be raised. ENABLED mode: Alarms will be raised. Valid values: ENABLED and DISABLED. Default value: ENABLED.

USR_ACTIVATED - User Activated
Permission: Read-only
Type: Feature={DISABLED,ENABLED}
Description: Link activation flag. Used on stack restart for alignment attempt. Only affected by link activation/deactivation.

L2_DBG_LVL - L2 Debug Level
Permission: Writeable
Type: int(Range: [0..3])
Description: MTP Level 2 Debug Level

DRE_ID - DRE ID
Permission: Createable
Type: int(Range: [1..64])
Description: DRE ID of the DRE that owns this link. Since the corresponding DRE process runs on a specific slot, this ID implies the slot where the M2PA terminates locally, and hence the choice of valid local IP addresses for this link.

LOCAL_IPADDR1 - Local IP Address 1
Permission: Writeable
Type: string
Description: Primary local address. This may be a hostname or an IP Address. If a hostname is used it must be provisioned in /etc/hosts and should resolve to a subset of the local IP Addresses configured for the slot where the link terminates. The slot where the link terminates is indirectly implied by the DRE ID.

LOCAL_IPADDR2 - Local IP Address 2
Permission: Writeable
Type: string
Description: Secondary local address. This may be a hostname or an IP Address. If a hostname is used it must be provisioned in /etc/hosts and should resolve to a subset of the local IP Addresses configured for the slot where the link terminates. The slot where the link terminates is indirectly implied by the DRE ID.

LOCAL_PORT - Local Port
Permission: Writeable
Type: int(Range: [0..65535])
Description: M2PA Local Port.

REMOTE_IPADDR1 - Remote IP Address 1
Permission: Writeable
Type: string
Description: Primary remote address. This may be a hostname or an IP Address. If a hostname is used it must be provisioned in /etc/hosts. This value is used as the SCTP Primary path to the remote SCTP endpoint.

REMOTE_IPADDR2 - Remote IP Address 2
Permission: Writeable
Type: string
Description: Secondary remote address. This may be a hostname or an IP Address. If a hostname is used it must be provisioned in /etc/hosts.

REMOTE_PORT - Remote Port
Permission: Writeable
Type: int(Range: [0..65535])
Description: M2PA Remote Port.

LINK_NAME - Link Name
Permissions: Read-only
Type: string
Description: Link Name based on the Linkset Name.

L2_STATE - L2 State
Permission: Read-only
Type: L2LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,FAILED,LOCAL_PROC_OUTAGE,REM_PROC_OUTAGE,BO_PROC_OUTAGE,LOCAL_LOOPBACK,NOT_ENABLED,NOT_INITIALIZED,USER_SHUTDOWN}
Description: Status of M2PA for this link. Deactivated, Proving, In-Service, Out-of-service, Failed, Local Processor Outage, Remote Processor Outage, Both Processor Outage, Local Loopback mode, Not Enabled, Not Initialized, User Shutdown

L3_STATE - L3 State
Permission: Read-only
Type: L3LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,LOCALLY_INHIBITED,REM_INHIBITED,BOTH_INHIBITED,BLOCKED,BLOCKED_INHIBITED,LOCAL_PROC_OUTAGE}
Description: Status of MTP Level 3 for this link. Deactivated, Proving, In-Service, Out-of-Service, Locally Inhibited, Remotely Inhibited, Both Inhibited, Blocked, Blocked and Uninhibited, Local Processor Outage.

RXMSU - Rx MSU Count
Permissions: Read-only
Type: int
Description: Received MSU count, per second.

TXMSU - Tx MSU Count
Permissions: Read-only
Type: int
Description: Transmitted MSU count, per second.

CONGESTION_LVL - Congestion Level
Permission: Read-only
Type: CongestionLevel={FALSE,LEVEL1,LEVEL2,LEVEL3,TRUE}
Description: Congestion level of this link. From 1 to 3, or FALSE if not congested.

DIAG_MSG - Diagnostic Message
Permission: Read-only
Type: string
Description: Link management diagnostic message.

GR310_M2PAVLK - GR310 Virtual Link
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Only for the DSC 8000. Indicates whether the M2PA Link represents GR-310-CORE M2PA virtual link (ENABLED/DISABLED). This attribute is only used for GR-310-CORE provisioning and is not relevant for non SNAMI licensed deployments. There is no impact on the CMU and TL1 provisioning interfaces. The GR-310-CORE provisioning model splits the creation of M2PA links into two entities, an M2PA virtual link (M2PAVLK) and a signaling link (SLK), where the M2PAVLK must be created first. In this implementation, the M2PAVLK parameters are stored in the M2PA Link object. In order to support the GR-310-CORE provisioning model, this attribute indicates whether this M2PA Link object should be treated as a full SLK with an associated M2PAVLK, or as simply an M2PAVLK. If this attribute is set to ENABLED then this object is not considered a full link from GR-310-CORE prespective. Default value: DISABLED.

M2PA_DLINK_BANDWITH - DataLink Bandwidth
Permission: Writeable
Type: int(Range: [1..2147483647])
Description: M2PA DataLink Baud Rate in kbps used to calculate Erlang.

M2PA_VERSION - M2PA Version
Permission: Writeable
Type: M2paDefaultVersion={Draft 6,RFC 4165}
Description: M2PA Version used to manage this link.To change, make sure the link is deactivated.

ALARMS - Alarms
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Alarms affect the alarms associated with the Link. DISABLED mode: Alarms will not be raised. ENABLED mode: Alarms will be raised. Valid values: ENABLED and DISABLED. Default value: ENABLED.

USR_ACTIVATED - User Activated
Permission: Read-only
Type: Feature={DISABLED,ENABLED}
Description: Link activation flag. Used on stack restart for alignment attempt. Only affected by link activation/deactivation.

DATA_DBG_LVL - Data Debug Level
Permission: Writeable
Type: int(Range: [0..255])
Description: Data Debug Level Amount of information displayed concerning MSU transfers. Higher is more information, 0 is DISABLED.

PROT_DBG_LVL - Protocol Debug Level
Permission: Writeable
Type: int(Range: [0..255])
Description: Protocol Debug Level Amount of information displayed concerning the M2PA protocol. This includes interaction with the M2PA Peer as well as with MTP3 and the SCTP. Higher values cause more logging, a value of 0 disables logging of M2PA Protocol related messages.

SW_DBG_LVL - Software Debug Level
Permission: Writeable
Type: int(Range: [0..255])
Description: Software Debug Level indicates how much information to display concerning the internals of the software. A value of 0 indicates no software related information is to be displayed, 1 shows only errors, more than 1 shows more detail.

SCTP_DBG_LVL - SCTP Debug Level
Permission: Writeable
Type: int(Range: [0..255])
Description: Debug: SCTP debug level for association debugging.

TXABTL1 - TX Abatement L1
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Abatement Level 1 (% of buffer usage)

TXONSTL1 - TX Onset L1
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Onset Level 1 (% of buffer usage)

TXABTL2 - TX Abatement L2
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Abatement Level 2 (% of buffer usage)

TXONSTL2 - TX Onset L2
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Onset Level 2 (% of buffer usage)

TXABTL3 - TX Abatement L3
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Abatement Level 3 (% of buffer usage)

TXONSTL3 - TX Onset L3
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Onset Level 3 (% of buffer usage)

RXABT_BUSY - RX Abatement Busy
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Receive Congestion Abatement Busy (bytes per second). When the RX Abatement value is cleared (less than) on this link and the link was previously set to locally busy, an M2PA LSBE message is sent on the link to notify the adjacent point code of the end of the local congestion. Applies to both the D6 and RFC-4165 M2PA versions.

RXONST_BUSY - RX Onset Busy
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Receive Congestion Onset Busy (bytes per second). When the RX Onset Busy value is reached on this link, an M2PA LSB message is sent on the link to notify the adjacent point code of the local congestion. Applies to both the D6 and RFC-4165 M2PA versions.

TXQSIZE - TX Queue Size
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum M2PA TX Queue Size (number of bytes). The TX Queue Size attribute is used to determine the congestion TX percentage based on the current transmit and retransmit buffer size and maps the value to the appropriate TX Abatement and Onset congestion levels. The congestion level will be updated and displayed in the Congestion Level attribute as required. If an outgoing M2PA message has its message length + the retransmit buffer and the transmit buffer exceed the TX Queue Size, the message is discarded. Applies to both the D6 and RFC-4165 M2PA versions.

LS_SCTP_VALUES - Linkset SCTP Values
Permission: Writeable
Type: YesNoState={NO,YES}
Description: When this is set, the link uses the M2PA Linkset SCTP values. In that case, the SCTP parameters may not be modified at the M2PA Link level.

HB - Heartbeat
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: On / Off Heartbeat Feature

HB_INV - Heartbeat Interval
Permission: Writeable
Type: int(Range: [0..65535])
Description: Heartbeat interval (ms)

RTO_INIT - RTO Initial
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Initial (ms)

RTO_MIN - RTO Minimum
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Minimum (ms)

RTO_MAX - RTO Maximum
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Maximum (ms)

MX_PATH_RETRANS - Maximum Path Retrans
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum path retransmissions

MX_ASSOC_RETRANS - Maximum Assoc Retrans
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum association retransmissions

BUNDLING - Bundling
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Bundling On / Off

BUNDLING_TO - Bundling TO
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Bundling TO (ms)

DELAYACK_TO - Delayed ACK TO
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Delayed ACK TO (ms)

FAST_RETRANS_TH - Fast Retrans Threshold
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Fast Retransmit Threshold

CHECKSUM - Checksum
Permission: Read-only
Type: SCTPCheckSum={CRC32C,ADLER32,NONE,AUTO}
Description: SCTP Checksum

SEND_INIT - Send INIT
Permissions: Writeable
Type: {DISABLED, ENABLED} 
Description: When ENABLED, the local endpoint sends SCTP INIT to the remote endpoint. When DISABLED, the local endpoint does NOT send SCTP INIT to the remote endpoint. This attribute can be modified only when the SCTP association is down.

DSCP - DSCP
Permission: Writeable
Type: int(Range: [0..63])
Description: Differentiated Services Code Point is used to classify traffic within a network in order to determine the priority of the various classes of traffic (0 to 63).
Default value: 0.

LINK_TYPE - Link Type
Permission: Createable
Type: genericLinkType={IPSP, M3UA_MG, M3UA_SG, M3UA_SERVER}
Description: Link Type.

DRE_ID - DRE ID
Permission: Createable
Type: int(Range: [1..64])
Description: DRE ID of the DRE that owns this link. Since the corresponding DRE process runs on a specific slot, this ID implies the slot where the link terminates locally, and hence the choice of valid local IP addresses for this link.

LOCAL_IPADDR1 - Local IP Address 1
Permission: Writeable
Type: string
Description: Primary local address. This may be a hostname or an IP Address. If a hostname is used it must be provisioned in /etc/hosts and should resolve to a subset of the local IP Addresses configured for the slot where the link terminates. The slot where the link terminates is indirectly implied by the DRE ID.

LOCAL_IPADDR2 - Local IP Address 2
Permission: Writeable
Type: string
Description: Secondary local address. This may be a hostname or an IP Address. If a hostname is used it must be provisioned in /etc/hosts and should resolve to a subset of the local IP Addresses configured for the slot where the link terminates. The slot where the link terminates is indirectly implied by the DRE ID.

LOCAL_PORT - Local Port
Permission: Writeable
Type: int(Range: [0..65535])
Description: Local Port.

NETWORK_APPEARANCE - Network Appearance
Permissions: Writeable
Type: NetworkApp={UNSET, 1 to 32767}
Description: The Network Appearance in the M3UA SG and M3UA Server links is used to populate the outgoing M3UA Data message Network Appearance Parameter. The NA parameter may be used by the receiving SGP or ASP. The NA should be UNSET (-1) when NA parameter inclusion is not required. The valid range for this parameter is 1 to 32,767

RC - Routing Context
Permissions: Writeable
Type: RContext={UNSET, 0 to 214748367}
Description: The Routing Context (RC) in the M3UA Server link is used to populate the outgoing M3UA Data message routing context parameter. The RC parameter may be required by the ASP receiving the M3UA Data. It is an optional attribute which does not always have to be configured. The RC can be UNSET (-1) when its inclusion is not required. Additionally, if the RC parameter is configured for a link, then it is expected that the received M3UA ASP Active message will contain an RC value which will match with the configured one. If an M3UA ASP Active message is received on the link that contains multiple RC parameters, then at least one RC must match the parameter configured for the link. If the RC matches or the RC is not configured for the link, then the incoming RC value of the M3UA ASP Active message is accepted regardless and responded to with an M3UA ASP Active Ack message and the link transitions to IN Service state at L3. The valid range for this parameter is 0 to 214,748,367.

REMOTE_IPADDR1 - Remote IP Address 1
Permission: Writeable
Type: string
Description: Primary remote address. This may be a hostname or an IP Address. If a hostname is used it must be provisioned in /etc/hosts. This value is used as the SCTP Primary path to the remote SCTP endpoint.

REMOTE_IPADDR2 - Remote IP Address 2
Permission: Writeable
Type: string
Description: Secondary remote address. This may be a hostname or an IP Address. If a hostname is used it must be provisioned in /etc/hosts.

REMOTE_PORT - Remote Port
Permission: Writeable
Type: int(Range: [0..65535])
Description: Remote Port.

L2_STATE - L2 State
Permission: Read-only
Type: L2LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,FAILED,LOCAL_PROC_OUTAGE,REM_PROC_OUTAGE,BO_PROC_OUTAGE,LOCAL_LOOPBACK,NOT_ENABLED,NOT_INITIALIZED,USER_SHUTDOWN}
Description: Status of this link. Deactivated, Proving, In-Service, Out-of-service, Failed, Local Processor Outage, Remote Processor Outage, Both Processor Outage, Local Loopback mode, Not Enabled Not Initialized.

L3_STATE - L3 State
Permission: Read-only
Type: L3LinkState={DEACTIVATED,PROVING,IN_SERVICE,OUT_OF_SERVICE,LOCALLY_INHIBITED,REM_INHIBITED,BOTH_INHIBITED,BLOCKED,BLOCKED_INHIBITED,LOCAL_PROC_OUTAGE}
Description: Status of MTP Level 3 for this link. Deactivated, Proving, In-Service, Out-of-Service, Locally Inhibited, Remotely Inhibited, Both Inhibited, Blocked, Blocked and Uninhibited, Local Processor Outage.

RXMSU - Rx MSU Count
Permissions: Read-only
Type: int
Description: Received MSU count, per second.

TXMSU - Tx MSU Count
Permissions: Read-only
Type: int
Description: Transmitted MSU count, per second.

DIAG_MSG - Diagnostic Message
Permission: Read-only
Type: string
Description: Link management diagnostic message.

GENERIC_DL_BANDWITH - DataLink Bandwidth
Permission: Writeable
Type: int(Range: [1..2147483647])
Description: Generic DataLink Baud Rate in kbps used to calculate Erlang.

ALARMS - Alarms
Permissions: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Alarms affect the alarms associated with the Link. DISABLED mode: Alarms will not be raised. ENABLED mode: Alarms will be raised. Valid values: ENABLED and DISABLED. Default value: ENABLED

USR_ACTIVATED - User Activated
Permission: Read-only
Type: Feature={DISABLED,ENABLED}
Description: Link activation flag. Used on stack restart for alignment attempt. Only affected by link activation/deactivation.

DATA_DBG_LVL - Data Debug Level
Permission: Writeable
Type: int(Range: [0..255])
Description: Data Debug Level Amount of information displayed concerning MSU transfers. Higher is more information, 0 is DISABLED.

SW_DBG_LVL - Software Debug Level
Permission: Writeable
Type: int(Range: [0..255])
Description: Software Debug Level indicates how much information to display concerning the internals of the software. A value of 0 indicates no software related information is to be displayed, 1 shows only errors, more than 1 shows more detail.

SCTP_DBG_LVL - SCTP Debug Level
Permission: Writeable
Type: int(Range: [0..255])
Description: Debug: SCTP debug level for association debugging.

LS_SCTP_VALUES - Linkset SCTP Values
Permission: Writeable
Type: YesNoState={NO,YES}
Description: When this is set, the link uses the Linkset SCTP values. In that case, the SCTP parameters may not be modified at the Link level.

HB - Heartbeat
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: On / Off Heartbeat Feature

HB_INV - Heartbeat Interval
Permission: Writeable
Type: int(Range: [0..65535])
Description: Heartbeat interval (ms)

RTO_INIT - RTO Initial
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Initial (ms)

RTO_MIN - RTO Minimum
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Minimum (ms)

RTO_MAX - RTO Maximum
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: RTO Maximum (ms)

MX_PATH_RETRANS - Maximum Path Retrans
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum path retransmissions

MX_ASSOC_RETRANS - Maximum Assoc Retrans
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Maximum association retransmissions

BUNDLING - Bundling
Permission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Bundling On / Off

BUNDLING_TO - Bundling TO
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Bundling TO (ms)

DELAYACK_TO - Delayed ACK TO
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Delayed ACK TO (ms)

FAST_RETRANS_TH - Fast Retrans Threshold
Permission: Writeable
Type: int(Range: [0..2147483647])
Description: Fast Retransmit Threshold

CHECKSUM - Checksum
Permission: Writeable
Type: SCTPCheckSum={CRC32C,ADLER32,NONE,AUTO}
Description: SCTP Checksum

INSTREAMS - In Streams
Permission: Writeable
Type: int(Range: [0..65355])
Description: Number of in streams.

OUTSTREAMS - Out Streams
Permission: Writeable
Type: int(Range: [0..65355])
Description: Number of out streams.

DSCP - DSCP
Permission: Writeable
Type: int(Range: [0..63])
Description: Differentiated Services Code Point is used to classify traffic within a network in order to determine the priority of the various classes of traffic (0 to 63).
Default value: 0.

TXABTL1 - TX Abatement L1
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Abatement Level 1 (% of buffer usage)

TXONSTL1 - TX Onset L1
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Congestion Onset Level 1 (% of buffer usage)

TXABTL2 - TX Abatement L2
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Abatement Level 2 (% of buffer usage)

TXONSTL2 - TX Onset L2
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Onset Level 2 (% of buffer usage)

TXABTL3 - TX Abatement L3
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Abatement Level 3 (% of buffer usage)

TXONSTL3 - TX Onset L3
Permission: Writeable
Type: Percent10to100={10 to 100}  (Units: %)
Description: Transmit Congestion Onset Level 3 (% of buffer usage)

ASSOC_TXQSIZE - TX Queue Size
Permission: Writeable
Type: int(Range: [4000..2147483647])
Description: Size of the SCTP Association Transmit buffer in bytes. Read from /proc/net/sctp/assocs, the TX Queue Size attribute shows the current buffer allocated by the OS for the association. The size of the TX Queue being currently used is also read from /proc/net/sctp/assocs. The current usage is calculated as a percentage of the allocated Buffer Size and determines the congestion level of the SCTP association based on the configured onset and abatement values.

CONGESTION_LVL - Congestion Level
Permission: Read-only
Type: CongestionLevel={FALSE,LEVEL1,LEVEL2,LEVEL3,TRUE}
Description: Congestion level of this link. For ANSI networks the values range from 1 to 3 or FALSE if not congested. For ITU networks the value is either TRUE or FALSE.

DISCARD_LVL - M3UA Message DiscardPermission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: M3UA Message Discard Congestion level of this Link. ANSI variant has 3 congestion levels, while ITU uses only 1. Valid values range from 1 to 3, or DISABLED to never discard. A data message will be discarded if the message priority is less than or equal to both the configured discard level and the current congestion level of the association.

REPORT_CONGESTION - Report CongestionPermission: Writeable
Type: Feature={DISABLED,ENABLED}
Description: Used to determine if congestion alarms are raised

NAME - PC Mapping Name
Permissions: Createable
Description: The name of the PC Mapping. This name is used to reference the PC Mapping from a linkset. It must be unique among the PC Mappings within the NA. It must consist of at most 32 alphanumeric characters, hyphens, and underscores

DIR - Direction
Permissions: Writeable and Createable
Type: direction={ANY,INCOMING,OUTGOING}
Description: Direction. Allowed values: ANY, INCOMING, and OUTGOING. Default value: ANY.

LOCAL_PC - Local PC
Permissions: Writeable and Createable
Type: string
Description: Local Point Code. A string representing a point code in the PC Display Format used by the Node. This represents the point code as understood by the local node.

RPC - Remote PC
Permissions: Writeable and Createable
Type: string
Description: Remote Point Code. A string representing a point code in the PC Display Format used by the Node. This represents the point code as understood by the adjacent node.

OPC - OPC
Permissions: Writeable and Createable
Type: string
Description: Originating Point Code. A string that represents a point code, in the PC Display Format used by the NA.

DPC - DPC
Permissions: Writeable and Createable
Type: string
Description: Destination Point Code. A string that represents a point code, in the PC Display Format used by the NA.

MSGCAT - Message Category
Permissions: Writeable and Createable
Type: migrationRecMsgCat={AM Messages}
Description: Message Category. An identifier for the class of messages that are affected by this record. Currently there is only one allowed value: AM Messages (MTP3 Adjacent Management Messages).

NEWDPC - New DPC
Permissions: Writeable and Createable
Type: string
Description: New Destination Point Code. A string that represents a point code, in the PC Display Format used by the NA. The special value ''Discard'' may also be used, indicating that a matching MSU should be discarded without sending a TFP.

DPC - DPC
Permissions: Writeable and Createable
Type: string
Description: Destination Point Code. A string that represents a point code, in the PC Display Format used by the NA.

MSGCAT - Message Category
Permissions: Writeable and Createable
Type: localRedirectRecMsgCat={FCM,TFC,RCT,SSP,SSA,SST,SCCP Data,SCMG}
Description: The class of message affected by the local redirect. The valid values are TFC, RCT, SSP, SSA, SST, SCCP Data, FCM, and SCMG. SCCP Data means SCCP messages other than SCMG messages (Called Party SSN is not 1). SCMG means any type of SCCP management message (e.g. SSA, SSP or SST). SST, SCMG and SCCP Data values may not be used with the Duplicate modifier. FCM means the flow control MTP management messages (TFC and RCT). Default value: FCM.

NEWDPC - New DPC
Permissions: Writeable and Createable
Type: string
Description: New Destination Point Code. A string that represents a point code, in the PC Display Format used by the NA.

MOD - Modifier
Permissions: Writeable and Createable
Type: string
Description: This is a string that describes any modification to the behaviour of this record. This may be the empty string or the string ''Duplicate'' or a string of the form ''Duplicate <max>'' or of the form ''Duplicate <max> <overload behaviour>''. If the max is specified, it must be a positive integer between 1 and 1000 that indicates the number of MSUs per second that may be duplicated. If the overload behaviour is specified, it must be one of the following strings: modify, original or alternate. If the number of duplicated MSUs exceeds the provisioned maximum for the record (per second) then the MSU is not duplicated, instead the behaviour depends on the provisioned overload behaviour. If the overload behaviour is set to ''modify'' then the MSU is modified and processed, if the overload behaviour is set to ''original'' then the MSU is processed unchanged and if the overload behavior is set to ''alternate'' then the behaviour alternates between ''modify'' and ''original''. The default values for the max is 1000 and the default value for the overload behaviour is alternate. For example, ''Duplicate'' is the same as ''Duplicate 1000 alternate''.