We are currently working in a lab to configure our first pair of 5548UP(with a 2232PP on each) with FCoE to an IBM p740 AIX server. On the Nexus side I have confugured the physical port e100/1/1 (2232pp) to be in a channel-group that will be part of a vpc with the other 5548UP switch, I am trunking all vlans in the etherchannel with the IBM server. Everything is working, i have the port-channel UP, the vfc and vpc when I use ''channel-group x mode ON'' on the physical ports and on the server side the 803.2ad is not active, it's configured ''roundRobin''.
Suppose I want to use LACP for the connections with the server should I configure the Nexus switch port with ''channel-group x mode active'' or ''channel-group x mode passive''? When the server is configured with ''802.3ad'' enabled and when I have ''channel-group x mode active'' or ''passive'' it doesn't work, the port-channel x does not come UP.
Does anyone have an explenation of how I should be configure?
Using LACP passive or active mode should not make much of a difference as long as one of the sides of the port-channel actively negotiates LACP. In most cases, we just configure both sides to be LACP active.
When you say the port-channel is not working when using LACP, what are the symptoms?
Are the physical ports in "I" state?'
'show port-channel summary' will show this
What does the output of "show lacp counters interface port-channel X" show?
This command will tell you if the Nexus 5K/2K is receiving LACPDUs from the IBM device (and if we are sending them). I would suggest to collect the LACP counters to verify that we are receiving the LACP packets from IBM, otherwise Nexus will not bring up the port-channel. Here is an example output from my lab switch:
5548-2019# show lacp counters interface port-channel 500
I have this same issue with an IBM Power7-780 system using a Cisco 5548UP with 10Gb SFP's. When we would look at the "show lacp counters" we would see sent counter incrementing but the received was 0. We were/have not able to find a resolution.
It' been a while since we that problem originaly if I remember correctly it was an issue with the version of the drivers on the NIC card of the IBM server, make sure you have the last version of drivers on the servers.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...