9
370 Nokia Network Voyager for IPSO 4.0 Reference Guide
Enabling RIP 2 on an Interface
RIP 2 implements new capabilities to RIP 1: authentication—simple and MD5—and the ability
to explicitly specify the network mask for each network in a packet. Because of these new
capabilities, Nokia recommends RIP 2 over RIP 1.
1. First configure the interface as in “Ethernet Interfaces.”
2. Click RIP under Configuration > Routing Configuration in the tree view.
3. Click on for the eth-s2p1c0 interface; then click Apply.
4. Click on in the Version 2 field for the eth-s2p1c0 interface; then click Apply.
5. (Optional) Enter a new cost in the Metric text box for the eth-s2p1c0 interface; then click
Apply.
6. (Optional) Select MD5 in the Auth Type drop-down list; then click Apply.
Enter a key in the MD5 key text box; then click Apply.
PIM
Protocol-Independent Multicast (PIM) gets its name from the fact that it can work with any
existing unicast protocol to perform multicast forwarding. It supports two types of multipoint
traffic distribution patterns: dense and sparse.
Dense mode is most useful when:
Senders and receivers are in close proximity.
There are few senders and many receivers.
The volume of multicast traffic is high.
The stream of multicast traffic is constant.
Dense-mode PIM resembles Distance Vector Multicast Routing Protocol (DVMRP). Like
DVMRP, dense-mode PIM uses Reverse Path Forwarding and the flood-and-prune model.
Sparse mode is most useful when:
A group has few receivers.
Senders and receivers are separated by WAN links.
The type of traffic is intermittent.
Sparse-mode PIM is based on the explicit join model; the protocol sets up the forwarding state
for traffic by sending join messages. This model represents a substantial departure from flood-
and-prune protocols, such as dense-mode PIM, which set up the forwarding state through he
arrival of multicast data.
The implementation does not support enabling both dense mode and sparse mode or either mode
of PIM and DVMRP on the same appliance. For more information about PIM, read the
following Internet Engineering Task Force (IETF) drafts.
For Dense-Mode PIM, see Protocol-Independent Multicast—Dense Mode (PIM-DM): Protocol
Specification (Revised).