Points to Note when using the Switch 3226 and Switch 3250
9
This message can be caused by one of the
following situations:
■
if there are more than14 routes whose next hop
is not the default gateway. 3Com recommends
reconfiguring the network so that the uplink
from the Switch goes directly to another layer 3
router which is configured as the default gate-
way.
■
if the unit is unable to contact one or more of
its next-hop routers then software routing will
be used. Find the reason why the router cannot
be contacted and correct the problem.
■
if there is no default gateway configured. Con-
figure a default gateway and check to see if the
problem is solved.
■
when the Switch is learning new routes. The
Switch may take up to a minute to learn new
routes. The above message may be displayed
for a short time while a route is learned. This is
normal behavior.
■
When the unit is in the default IP mode of
auto
it
will attempt to contact a DHCP server on the
network to obtain an IP address. If there is no
DHCP server available on the network then the
unit will not be accessible using TCP/IP.
Please use the console to configure the unit with
an IP address or connect the unit to a network
with a DHCP server. If using DHCP you will need to
use a console connection or log information from
your DHCP server to discover the address which
has been assigned to the unit.
■
Reconfiguring an IP interface may cause the RIP
configuration and static routes settings for that
interface to be lost.
■
When adding or modifying an IP interface the CLI
and Web interface may appear to hang for up to
30 seconds while the operation takes place.
■
When forwarding DHCP and BOOTP requests in a
multinetted environment, the UDP helper will only
use the primary IP interface in the forwarded
requests. This will cause the BOOTP/DHCP server to
allocate all dynamic addresses from the primary
subnet of a multinetted VLAN.
■
If the number of multicast traffic groups on your
network exceeds the maximum supported by the
Switch (64) then you may see occasional bursts of
multicast traffic as the Switch updates its internal
configuration.
■
Some combinations of IP commands in a
multinetted environment may cause the IP address
of interface 1 to become a secondary address.
Rebooting the unit will reset this interface as the
primary address. There is no other means of
clearing this condition.
Access Control Lists
When trying to bind an Access Control List (ACL) to a
port you may see the following error generated:
Fail to bind port 26 ACL
This error will appear if:
