Resource - MTP3NAManager

About this Resource

Defines an MTP3NAManager managed object.

REST API Methods for this Resource

Resource Schema

Configuration

Parameter Name Required Create Read-Only Data Type Description
NADebugLevel No No No int32 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 adversely impact performance. Default value: 1. TL1Name: NA_DBG_LEVEL
LDLDebugLevel No No No int32 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 adversely impact performance. Default value: 2. TL1Name: LDL_DBG_LEVEL
SCTPDebugLevel No No No int32 MTP3 SCTP Debug Level (0 - 255). 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 adversely impact performance. Default value: 0. Obsolete as of 15.1.0 for LK SCTP deployments. TL1Name: SCTP_DBG_LEVEL
LDLSCTPDebugLevel No No No int32 MTP3 LDL SCTP Debug Level (0 - 255). LDL 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 adversely impact performance. Default value: 0. Obsolete as of 15.1.0 for LK SCTP deployments. TL1Name: LDL_SCTP_DBG_LEVEL
DRETelemetryDiagnostics No No No LoggingFeature 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. The recommended default setting of this flag is NOT LOGGED, so that the user could monitor the telemetry data. TL1Name: TELEDIAG
SNMTelemetryDiagnostics No No No LoggingFeature If the Debug Telemetry Diagnostics flag is set to LOGGED, then information concerning SNM telemetry diagnostics data will be sent to the Debug log file every 5 minutes. The recommended default setting of this flag is NOT LOGGED, so that the user could monitor the telemetry data. TL1Name: SNMTELEDIAG
MSUQueueDepth No No No int32 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. TL1Name: MSUQ
TimeCongOnset1 No No No Timer 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. TL1Name: TIME_CONG1
TimeCongOnset2 No No No Timer 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. TL1Name: TIME_CONG2
TimeCongOnset3 No No No Timer 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. TL1Name: TIME_CONG3
ReportZeroStats No No No Feature Report zero value for SCTP_Path stats file. When enabled, the SCTP Assoc be included in the report for every 5-minute interval between the creation and deletion. When disabled, the stats file only report when we have the path state change. Default value: DISABLED. TL1Name: REPORT_ZERO_STATS

  • No labels