Link Aggregation discovery
How NNM deals with Link Aggregation discovery when device (cisco ASA5500) doesn't report it over SNMP? LCAP protocol is in use. No CDP (because of security reasons).
Is it possible to define rules when to create Aggregated ports or to influence it? Port-channel and member interface have same MAC address and this leads to not built L2 connection to other device as MAC address is not unique.
After running configpoll.ovpl on the device this errors occurs:
"Get AggregatePort retrieved no data because this device does not support a way of collecting data."
(Full configpoll in attachment)
SNMP is the primary source of information for NNMi. For device connectivy protocols, in the current version, the information needs to be provided via SNMP.
There are two ways that you can influence device connectivity but this will be pure L2 connectivity and not port aggregation.
1) Subnet Connection Rules
You can find information about those two in the online help.
For aggregation, there are no manual tools that you can use to force/influence link aggregation.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
We expect significant enhancements with NIC Teaming and Link Aggregation in the next NNMi version. Unfortunately, we cannot discuss this untill the version is released officially. I hope the new enhancements will solve the problem. Wait a little bit. The new NNMi version will be released very soon.
The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HPE
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember
to give them a KUDOS and show your appreciation