Broadcom advanced server program (basp) – Allied Telesis AT-2916SX User Manual

Page 74

Advertising
background image

Chapter 5: Troubleshooting

74

Problem: Team configuration is not retained when you edit it.

Solution: In configuring BASP team configuration, the actual changes of
the configuration are not committed until you click "OK" in the "Network
Properties" window. If you do not click "OK" and, instead, return to the
BASP team configuration window, all the previous uncommitted changes
are lost. This requires you to reenter the configuration. As a workaround,
always click "OK" in the "Network Properties" window after making
changes.

Problem: IP address is configurable on a member of the team.

Solution: When a team is created, the TCP/IP properties for the adapters
are unselected. You can select and configure the TCP/IP properties of the
adapters and configure an IP address manually. This issue is a limitation
of the Windows 2000 network installation paradigm where this invalid
configuration is still allowed.

Problem: When creating 64 VLANs, all virtual adapters are displayed as
disconnected or one of the 64 VLANs is displayed as disabled.

Solution: The maximum VLAN configurations are 63 tagged and one
untagged VLAN ID 0. If 64 tagged VLANs are created, they are
disconnected. A reboot is required and only the 63 tagged VLANs show
links, while the 64th VLAN is disabled.

Broadcom

Advanced Server

Program (BASP)

This section lists known BASP problems and solutions that apply to all
operating systems.

Problem: 802.3ad team member links disconnect and reconnect
continuously.

Solution: This is a 3rd party issue. It is seen only when configuring an
802.3ad team with more than 2 members on the server and connecting an
HP2524 switch, with LACP enabled as passive or active. The HP switch
shows an LACP channel being brought up successfully with only 2
members. All other member's links disconnect and reconnect.

Note

This issue does not occur with a Cisco Catalyst 6500.

Advertising