07-04-2012 01:00 AM
Are there any plans to support the definition of VLANs on teamed fiber-pairs for Linux-hosts?
From firmware v220.127.116.11 there is support for this on Windows-hosts - and works best from v18.104.22.168 onwards. The feature offers redundancy on case one of the VDXs fails (we have implemented CNA1020 adapters in various hosts working with two VDXs).
Are there developments to facilitate this feature for Linux-hosts and from which firmware version is this expected?
Thanks in advance and warm regards,
08-24-2012 02:34 PM
Can you tell me what is the configuration in the switch side where the hosts ports are connected.
Also your port-channel configurations on the switch ?
what type of NIC teaming are you trying to configure ?
What version of firmware are you using on the CNA 1020 adpaters?
01-15-2013 07:06 AM
sorry for the late reply.
The host ports are connected to two VDXs - one leg in one, one in the other. The intention is to have a fail-back configuration, just as we implemented on our Windows hosts.
e are trying to team a Brocade 1020 CNA adapter. We have tried both software and firmware v22.214.171.124 and v126.96.36.199.
I hope this answers your questions.
Furtermore when installing the CNA1020 on a SLES10.3 platform, we find we can no longer bind the CNA to the platform. In the HCM application the adapter is visible and shows no problems. However, when defining the VLANs within YAST the defined NICs show up as 'not connected'. We are unable to establish IP connectivity this way.
Should we use a different application/mechanism to define the IP connectivity and which is this?
This issue is also being addressed through Brocade case #1122762 - for which we receive little to no input.