Reset Search
 

 

Article

Standard MIB doesn't support LAG Ports on Extreme Devices

« Go Back

Information

 
TitleStandard MIB doesn't support LAG Ports on Extreme Devices
Question
  • How to get LACP details from the ports and  Lag port information of the corresponding Physical ports?
Environment
  • EXOS 
  • Summit
  • BlackDiamond
  • SNMP
  • LAG/load share/Sharing
Answer
  • You can't get Lag port information of Corresponding physical ports by using the standard MIB because they don't seem to be Supported on Extreme Devices.
  • Following are the Standard MIBs for Lag ports which aren't supported:
    1) dot3adAggPortTable
    2) dot3adAggPortAttachedAggID
    3) dot3adAggPortAggregateOrIndividual 
  • The following OIDs from Extreme MIB are equivalent to Standard MIB and can be used to poll LACP details from the ports and to get the LAG port information.
    1) dot3adAggPortTable = "extremeLacpTable = 1.3.6.1.4.1.1916.1.19.1"
    2) dot3adAggPortAttachedAggID = "extremeLacpAggStatus = 1.3.6.1.4.1.1916.1.19.1.1.3"
    3) dot3adAggPortAggregateOrIndividual = "extremeLacpMemberPort = 1.3.6.1.4.1.1916.1.19.1.1.2"
    

     
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255