ISO8859-1  $%%-9S'   3If     8#S$w$-&4Tpw @ | P 6EP ATM LAN Emulation MPOA ClientAuto Configuration with LEC/LECSShortcut Setup Frame CountShortcut Setup Frame Time in secondsInitial Request Retry Time in secondsMaximum Request Retry Time in secondsFailed Resolution request retry Hold Down Time in secondsVCC Inactivity Timeout value in minutesDebug Trace EnabledEnable MPOA FragmentationMulti-Protocol Over ATM (MPOA)List All Defined MPOA ClientsAdd an MPOA ClientName of Device to AddChange / Show an MPOA ClientName of Device to Change / ShowRemove an MPOA ClientName of Device to RemoveKEEP definition in databaseGenerate an Error ReportTrace an MPOA ClientMPOA Client Device NameAutomatic Configuration via LECSShortcut Setup Frame CountShortcut Setup Frame Time (seconds)Initial Request Retry Time (seconds)Maximum Request Retry Time (seconds)Failed request retry Hold Down Time (seconds)VCC Inactivity Timeout value (minutes)Apply change to DATABASE onlyConfigure a Defined MPOA ClientName of Device to ConfigureNo,YesDebug Trace EnabledEnable MPOA FragmentationAuto Configuration with LEC/LECS. Specifies whether MPOA Client is to be automatically configured via Configuration Server (LECS). Select "Yes" if a primary LE Client will be used to obtain the MPOA configuration attributes, which will override any manual or default values. The default value is "No" manual configuration). The attribute values are: Yes - auto configuration No - manual configuration Shortcut Setup Frame Count. This attribute is used in conjunction with "sc_setup_time" to determine when to establish a shortcut path. Once 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. 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. Once 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. 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. 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 will wait this maximum value. This attribute correlates to ATM Forum MPC Configuration parameter MPC-p5. The default value is 40 seconds. Failed resolution request retry Hold Down Time (in seconds). Specifies the length of time to wait before reinitiating a 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. 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. Specifies whether this MPOA Client should keep a real time debug log within the kernel and allow full system trace capability. Select "Yes" if full tracing should be operational for this MPOA Client. Select "No" for better performance when minimal tracing is desired. The default is "Yes" (provide full tracing capability). Enable MPOA Fragmentation. Specifies whether fragmentation should be performed on packets that exceed the MTU returned in the MPOA Resolution Reply. Select "Yes" to have outgoing packets fragmented as needed. Select "No" to never have outgoing packets fragmented. Selecting "No" will cause outgoing packets to be sent down the LANE path when fragmentation must be performed. Incoming packets will always be fragmented as needed even if "No" has been selected. The default value is Yes.