Chapter 3
Table 3-6. LAG Configuration Fields - Advanced Tab (Continued)
Field | Description |
|
|
STP Admin P2P | The administrative |
| LAN segment attached to this LAG. Possible |
| statuses include: |
| • True - The LAG should always be treated |
| as if it is connected to a |
| link. |
| • forceFalse - The LAG should be treated |
| as having a shared media connection. |
| • auto - The LAG is considered to have a |
| |
| and all of its members are aggregative, or |
| if the MAC entity is configured for full |
| duplex operation, either through |
| |
| means. |
|
|
STP Oper P2P | The operational |
| LAN segment attached to this LAG. It |
| indicates whether a LAG is considered to have |
| a |
| The value is determined by STP Admin P2P. |
|
|
STP Admin Path Cost | The administratively assigned value for the |
| contribution of this LAG to the path cost of |
| paths towards the spanning tree root. A value |
| of 0 assigns the automatically calculated |
| default Path Cost value to the LAG. |
| STP Admin Path Cost complements STP Path |
| Cost, which returns the operational value of |
| the path cost. |
|
|
STP Path Cost | The operational cost factor used by Spanning |
| Tree Algorithm to determine the most efficient |
| route for forwarding traffic to its destination |
| while removing loops in the network. |
| For more information refer to Spanning Tree |
| Algorithm (STA) in The Reference Guide. |
|
|
STP Force Migration | When checked and in RSTP mode, the LAG is |
| forced to transmit RSTP BPDUs. |
|
|
38 | Avaya C360 Manager User Guide |