Vlan Creation And Operation Problems - Brocade Communications Systems CNA 1010 Troubleshooting Manual

Note that you can still create teams even though these conflicts exist. However to avoid conflicts,
make sure the following parameters match for all ports added to a team:
•
•
•
•
•
•
You can view and change these parameters for each port using Windows Device Manager.
1. Run devmgmt.msc to open the Device Manager window.
2. Expand Network Adapters.
3. Right-click an the adapter instance that corresponds to the port where you want to change
4. Select the Advanced tab.
5. Select the property and change the value as appropriate.
For more details, refer to the "Adapter Configuration" appendix in the Brocade Adapters Installation
and Reference Manual.

VLAN creation and operation problems

VLAN creation fails with BCU command or HCM or pass-through VLAN stops working after creating
with Device Manager. These problems result when VLANs are created using HCM or BCU
commands and also using Device Manager. Follow these guidelines to avoid problems:
•
•
1. Symptom: When using BCU commands or HCM, to create VLANs, the initial VLAN fails with an
2. Symptom: Pass-through VLAN stops working.
Brocade Adapters Troubleshooting Guide
53-1001582-01
Header data split
Receive side scaling
Offload parameters
Port VLAN ID (PVID)
MTU size
Link speed
NOTE
For CNAs, link speed is always 10 Gbps. You cannot change this parameter.
An instance of the adapter model should display for each installed adapter port.
parameters, and select Properties.
If you need to create a single VLAN and VLANs have not been created using BCU commands or
HCM, you can use Device Manager.
If you want to configure multiple VLANs, disable the port VLAN created in Device Manager (set
to 0 value), then configure VLANs using HCM or BCU. Refer to the Brocade Adapters
Administrator's Guide for instructions.
error message.
Possible Cause: Port VLAN was created through Device Manager.
Action: Set port VLANID to 0 in Device Manager and create VLANs using BCU commands or
HCM.
Possible Cause: Port VLAN was configured through Device Manager.
Action: Set port VLANID to 0 in Device Manager.
Ethernet network interface problems (CNAs only)
2
27