Configuration Parameters for ATM MPOA Client
The ATM LANE device driver supports the following configuration parameters for the MPOA Client:
| Item | Description |
|---|---|
| auto_cfg | Auto Configuration with LEC/LECS. Specifies whether the MPOA Client is to be automatically configured using LANE Configuration Server (LECS). Select Yes if a primary LE Client is used to obtain the MPOA configuration attributes, which overrides any manual or default values. The default value is No (manual configuration). The attribute values are: Yes - auto configuration No - manual configuration |
| debug_trace | Specifies whether this MPOA Client should keep a real time debug log within the kernel and allow full system trace capability. Select Yes to enable full tracing capabilities for this MPOA Client. Select No for optimal performance when minimal tracing is desired. The default is Yes (full tracing capability). |
| fragment | Enables MPOA fragmentation and specifies whether fragmentation should be performed on packets that exceed the maximum transmission unit (MTU) returned in the MPOA Resolution Reply. Select Yes to have outgoing packets fragmented as needed. Select No to avoid having outgoing packets fragmented. Selecting No causes outgoing packets to be sent down the LANE path when fragmentation must be performed. Incoming packets are always fragmented as needed even if No has been selected. The default value is Yes. |
| hold_down_time | Failed resolution request retry Hold Down Time (in seconds). Specifies the length of time to wait before reinitiating a failed address resolution attempt. This value is normally set to a value greater than retry_time_max. This attribute correlates to ATM Forum MPC Configuration parameter MPC-p6. The default value is 160 seconds. |
| init_retry_time | Initial Request Retry Time (in seconds). Specifies the length of time to wait before sending the first retry of a request that does not receive a response. This attribute correlates to ATM Forum MPC Configuration parameter MPC-p4. The default value is 5 seconds. |
| retry_time_max | Maximum Request Retry Time (in seconds). Specifies the maximum length of time to wait when retrying requests that have not received a response. Each retry duration after the initial retry are doubled (2x) until the retry duration reaches this Maximum Request Retry Time. All subsequent retries wait this maximum value. This attribute correlates to ATM Forum MPC Configuration parameter MPC-p5. The default value is 40 seconds. |
| sc_setup_count | Shortcut Setup Frame Count. This attribute is used in conjunction with sc_setup_time to determine when to establish a shortcut path. After the MPC has forwarded at least sc_setup_count packets to the same target within a period of sc_setup_time, the MPC attempts to create a shortcut VCC. This attribute correlates to ATM Forum MPC Configuration parameter MPC-p1. The default value is 10 packets. |
| sc_setup_time | Shortcut Setup Frame Time (in seconds). This attribute is used in conjunction with sc_setup_count above to determine when to establish a shortcut path. After the MPC has forwarded at least sc_setup_count packets to the same target within a period of sc_setup_time, the MPC attempts to create a shortcut VCC. This attribute correlates to ATM Forum MPC Configuration parameter MPC-p2. The default value is 1 second. |
| vcc_inact_time | VCC Inactivity Timeout value (in minutes). Specifies the maximum length of time to keep a shortcut VCC enabled when there is no send or receive activity on that VCC. The default value is 20 minutes. |