12.03.2015 Views

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

FortiGate Administration Guide - FirewallShop.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Multicast<br />

Router Dynamic<br />

Networks<br />

Delete icon<br />

The IP addresses and network masks of networks to advertise to BGP<br />

peers. The <strong>FortiGate</strong> unit may have a physical or VLAN interface<br />

connected to those networks.<br />

IP/Netmask Enter the IP address and netmask of the network to be<br />

advertised.<br />

Add Select to add the network information to the Networks list.<br />

Network<br />

The IP addresses and network masks of major networks that<br />

are advertised to BGP peers.<br />

Select to delete a BGP neighbor entry or a BGP network definition.<br />

Multicast<br />

A <strong>FortiGate</strong> unit can operate as a Protocol Independent Multicast (PIM) version 2<br />

router in the root virtual domain. <strong>FortiGate</strong> units support PIM sparse mode (RFC<br />

2362) and PIM dense mode (RFC 3973) and can service multicast servers or<br />

receivers on the network segment to which a <strong>FortiGate</strong> interface is connected.<br />

Multicast server applications use a (Class D) multicast address to send one copy<br />

of a packet to a group of receivers. The PIM routers throughout the network<br />

ensure that only one copy of the packet is forwarded through the network until it<br />

reaches an end-point destination. At the end-point destination, copies of the<br />

packet are made only when required to deliver the information to multicast client<br />

applications that request traffic destined for the multicast address.<br />

Note: To support PIM <strong>com</strong>munications, the sending/receiving applications and all<br />

connecting PIM routers in between must be enabled with PIM version 2. PIM can use static<br />

routes, RIP, OSPF, or BGP to forward multicast packets to their destinations. To enable<br />

source-to-destination packet delivery, either sparse mode or dense mode must be enabled<br />

on all the PIM-router interfaces. Sparse mode routers cannot send multicast messages to<br />

dense mode routers. In addition, if a <strong>FortiGate</strong> unit is located between a source and a PIM<br />

router, two PIM routers, or is connected directly to a receiver, you must create a firewall<br />

policy manually to pass encapsulated (multicast) packets or decapsulated data (IP traffic)<br />

between the source and destination.<br />

A PIM domain is a logical area <strong>com</strong>prising a number of contiguous networks. The<br />

domain contains at least one Boot Strap Router (BSR). If sparse mode is enabled,<br />

the domain also contains a number of Rendezvous Points (RPs) and Designated<br />

Routers (DRs). When PIM is enabled on a <strong>FortiGate</strong> unit, the <strong>FortiGate</strong> unit can<br />

perform any of these functions at any time as configured. If required for sparse<br />

mode operation, you can define static RPs.<br />

Note: Basic options can be configured through the web-based manager. Many additional<br />

options may be configured through CLI <strong>com</strong>mands only. For <strong>com</strong>plete descriptions and<br />

examples of how to use CLI <strong>com</strong>mands to configure PIM settings, see “multicast” in the<br />

“router” chapter of the <strong>FortiGate</strong> CLI Reference.<br />

Viewing and editing multicast settings<br />

When multicast (PIM) routing is enabled, you can configure sparse mode or dense<br />

mode operation on any <strong>FortiGate</strong> interface.<br />

<strong>FortiGate</strong> Version 3.0 MR5 <strong>Administration</strong> <strong>Guide</strong><br />

258 01-30005-0203-20070830

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!