When trying to configure a second IPX sub-
interface with the same IPX frame type, the
following error message is displayed:
"Same frame type has exist, you can change to
another frame type in order to config ipx"
To configure multiple IPX networks with the
same IPX frame type, you must use separate
physical interfaces for each network.
1.1.7. Routing Protocol
Symptom Solution
Any route policy that uses ACLs defaults to
permit all
.
Add an explicit
deny all
or
permit all
rule at
the end of all ACL statements.
The OSPF command,
abr-summary not
advertise
is not working correctly.
The
abr-summary not advertise
command
does not filter the initial route in a summary
update. For example, 128.213.64.0/19 filters
the routes 128.213.65.0 to 128.213.95.0 but
does not filter 128.213.64.0.
If necessary, configure an ACL to filter the
route.
Changing the OSPF Area on an interface will
delete the OSPF configuration on that
interface.
Save the OSPF configuration file before the
change.
Changes to an access list are not applied until
the route policy is reapplied.
Reapply the route policy immediately after
making changes to the access list.
The
display bgp route
command only shows
one route even if multiple (backup) routes are
available.
The display only shows detail information for
the best route.
RIP MD5 Authentication types are ambiguous.
For RIP MD5 Authentication, use the default
non-standard
value. This is the most common.
Routing does not function correctly, in a virtual
template with MP and OSPF configuration.
When using MP with OSPF, you must
configure
OSPF peer
ip address
.
When using a serial DTE interface, the OSPF
cost may not be set correctly.
Set the OSPF cost for the DTE manually.
BGP places all internal peers into one peer
group by default
To configure different policies for one peer,
place that peer in a separate peer group and
define policies for that peer group.
The router supports only 15,000 entries.
Receiving over 15,000 BGP routes may cause
the router to hang.
Arrange with the local ISP to filter routes before
updates can reach the router.
With Routing Policies, matching next-hop
based on IP prefix list does not actually match
the BGP next-hop.
Use ACL instead of prefix-list.
Poison Reverse is not supported in this
release.
Poison Reverse is not supported in this
release.
With IBGP, importing direct routes will have
origin attribute of IGP locally. However, when
advertised to a peer, the peer will log the route
as incomplete. This is only a problem with
IBGP peers.
Correct the issue with an export policy if
necessary.
When the
default-local-pref
command is used
with a value other than 100, the value is
reverted back to 100 after a reboot.
Re-configure the
default-local-pref
value after
a reboot.
BGP advertises routes when it is out of
synchronization with the interior routing
protocol
BGP synchronization is not supported.
3Com Router Release Notes for V1.20
7