Multicast Protocol - 3Com Router 3000 Series Manual

1.1.8. Multicast Protocol

Symptom
The router does not support IP multicast
forwarding on an IGMP interface without the
multicast routing protocol enabled.
Enabling ip unnumbered on a PIM-SM
interface disables PIM-SM routing.
1.1.9. Security
Symptom
ACL match counts are not logged.
IPSec in transport mode will transmit transit
traffic with no security headers. IPSec in
transport mode is designed for direct
communications between two peers running
IPSec.
IPSec nesting (i.e. the encrypting of already
encrypted packets) is not supported in this
release.
The Encryption card status message,
Order: Not consistent with host
can be misleading.
Only one security association is used for each
ACL-incompatible with per-rule implementation.
To telnet or SSH to a 3Com Router there must
be a local user defined on that 3Com router.
Routers that are defined within a Server ACL
on the Master Clock router will not sync to the
Master
The encryption card in combination with some
features may cause ping responses or traffic to
be slowed. Example: Encryption card with
GRE, MP, IPSec.
It is difficult to exit from the SSH public key
configuration without a valid key
3Com Router Release Notes for V1.20
Keep PIM-SM or PIM-DM enabled on the
IGMP interface to insure multicast runs
correctly.
Do not configure ip unnumbered on a PIM-SM
interface.
ACL match counting is only supported with the
firewall feature.
Use Tunnel mode if you are configuring the
router to be an IPSec gateway.
IPSec nesting is not supported in this release.
Disregard this status message.
Byte
,
Create one separate ACL for each permit
statement in the third-party access list.
Configure a local-user on the router for telnet
or SSH access
From the Master Clock router, define each
router as a Peer of the clock source router
within a Peer ACL if these routers are to be
synchronized by the Master.
In addition, direct NTP messages to the master
using the unicast server command on the
routers.
If problems occur with securely managing or
pinging the router via an IPSec tunnel, use a
software encryption policy instead of an
encryption card policy.
Enter another view, such as interface view,
using the command interface Ethernet 0, then
quit.
8
Solution
Solution