5.1.36 M2PA Config
A M2pa Config is an entity to configure all the m2pa timers.
Select the M2PA Config View, Insert,
and Edit pages.
page. The page displays the elements on the Note:
Data Input Notes apply to the Insert and Edit pages only; the View page is read-only.Table 5-36 M2PA Config Elements
Element | Description | Data Input Notes |
---|---|---|
Name | Name for this M2PA Config, which must be unique
within the VSTP site.
This is a mandatory field. |
Valid names are strings between one and 32 characters, inclusive. Valid characters are alphanumeric and underscore. The name must contain at least one alpha and must not start with a digit. |
T1 Timer | Alignment timer in milliseconds. The amount of time M2PA waits to receive a Link Status Alignment message from the peer. | Typical value is 10000. Default: 35000, minimum: 1000, maximum: 350000 |
T2 Timer | M2PA Timer "not aligned" in milliseconds. | Typical value is 2000. Default: 20000, minimum: 5000, maximum: 150000 |
T3 Timer | Ready Timer in milliseconds. The amount of time after proving that M2PA waits to receive a Link Status Ready message from the peer. | Typical value is 2000. Default: 2000, minimum: 1000, maximum: 60000 |
T4 Emergency Timer | Emergency proving timer in milliseconds. The amount of time M2PA generates Link Status Proving messages during emergency proving. | Typical value is 500. Default: 500, minimum: 400, maximum: 5000 |
T4 Normal Timer | Normal proving timer in milliseconds. The amount of time M2PA generates Link Status Proving messages during normal proving. | Typical value is 10000. Default: 30000, minimum: 1000, maximum: 70000 |
T5 Timer | Busy rate timer in milliseconds. The amount of time between sending Link Status Busy messages while the link is in service. | Typical value is 100. Default: 100, minimum: 80, maximum: 10000 |
T6 Timer | Remote congestion timer in milliseconds. The amount of time that a congested link will remain in service. | Typical value is 3000. default: 3000, minimum: 1000, maximum: 6000 |
T7 Timer | Excessive acknowledgment delay timer in milliseconds. The maximum amount of time that can pass between transmission of a user data message and receipt of an acknowledgment for that message from the peer. If this timer expires, the link is taken out of service. | Typical value is 1200. default: 1200, minimum: 200, maximum: 2000 |
T16 Timer | Proving rate timer in milliseconds. The amount of time between sending Link Status Proving messages while T2N or T2E is running. | Range: 1 - 500
Default: 200 |
T17 Timer | Ready rate timer in milliseconds. The amount of time between sending Link Status Ready messages while T3 is running. | Typical value is 250. default: 250, minimum: 100, maximum: 500 |
T18 Timer | Processor outage rate timer in milliseconds. The amount of time between sending Link Status Processor Outage messages while the link is in service. | Range: 100 - 10000
Default: 1000 |
Note:
The timer values discussed in the above table are in milliseconds.You can perform add, edit, or delete tasks on VSTPConfigurationM2PA Config page.
Adding a M2PA Config
Perform the following steps to configure a new M2PA Config:
- Click Insert.
Note:
The new M2PA Config must have a name that is unique across all M2PA Config at the SOAM. In addition, the M2PA Config's IP Port combination must also be unique across all M2PA Config configured at the SOAM. - Enter the applicable values.
- Click OK, Apply, or Cancel
Editing a M2PA Config
Use this procedure to change the field values for a selected M2PA
Config. (The M2PA Config Name field cannot be
changed.):
- Select the M2PA Config row to be edited.
- Click Edit
- Enter the updated values.
- Click OK, Apply, or Cancel
Deleting a M2PA Config
Use the following procedure to delete a M2PA Config.
Note:
You cannot delete a M2PA Config if it is part of the configuration of one or more Linksets.- Select the M2PA Config to be deleted.
- Click Delete.
- Click OK or Cancel.