Filter
Top Products
Advanced Control Suite User’s Guide
97
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.
Linux-BASP This section lists known problems and solutions using Linux-BASP.
Problem: When obtaining the IP for a SLB's virtual interface via DHCP,
the IP-gets lost under heavy traffic.
Solution: Always set a static IP for all the virtual interfaces in a SLB team.
Problem: Make install fails on Turbo Linux 7.0 IA64.
Solution: The symbolic link under /lib/modules/<kernel-version>/build
points to an empty directory. To successfully install BASP using `make
install`, re-link /lib/modules/<kernel-version>/build to point to /usr/src/
<kernel-version>/.