13.07.2015 Views

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support

Administration of the Avaya G350 Media Gateway - Avaya Support

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.

Configuring policy-based routingPolicy-based routing only operates on routed packets. Packets traveling within <strong>the</strong> same subnetare not routed, and are <strong>the</strong>refore not affected by policy-based routing.The Loopback interface is a logical interface which handles traffic that is sent to and from <strong>the</strong><strong>G350</strong> itself. This includes ping packets to or from <strong>the</strong> <strong>G350</strong>, as well as telnet, FTP, DHCP Relay,TFTP, HTTP, NTP, SNMP, H.248, and o<strong>the</strong>r types <strong>of</strong> traffic. The Loopback interface is also usedfor traffic to and from analog and DCP phones connected to <strong>the</strong> device via IP phone entities.The Loopback interface is always up. You should attach a PBR list to <strong>the</strong> Loopback interface ifyou want to route specific packets generated by <strong>the</strong> <strong>G350</strong> to a specific next-hop.Unlike <strong>the</strong> case with o<strong>the</strong>r interfaces, PBR lists on <strong>the</strong> Loopback interface are applied topackets when <strong>the</strong>y leave <strong>the</strong> <strong>G350</strong>, ra<strong>the</strong>r than when <strong>the</strong>y enter.Certain types <strong>of</strong> packets are not considered router packets (on <strong>the</strong> Loopback interface only),and are <strong>the</strong>refore not affected by policy-based routing. These include RIP, OSPF, VRRP, GRE,and keepalive packets. On <strong>the</strong> o<strong>the</strong>r hand, packets using SNMP, Telnet, Bootp, ICMP, FTP,SCP, TFTP, HTTP, NTP, and H.248 protocols are considered routed packets, and are <strong>the</strong>reforeaffected by policy-based routing on <strong>the</strong> Loopback interface.ApplicationsThe most common application for policy-based routing is to provide for separate routing <strong>of</strong> voiceand data traffic. It can also be used as a means to provide backup routes for defined traffictypes.Separate routing <strong>of</strong> voice and data trafficAlthough <strong>the</strong>re are many possible applications for policy-based routing, <strong>the</strong> most commonapplication is to create separate routing for voice and data traffic.For example, <strong>the</strong> application shown in Figure 24: Policy-based routing — Voice/Data DivisionBy DSCP on page 275 uses <strong>the</strong> DSCP field to identify VoIP control packets (DSCP=34, 41),VoIP Bearer RESV packets (DSCP = 43, 44), and VoIP Bearer packets (DSCP = 46).Policy-based routing sends <strong>the</strong>se packets over <strong>the</strong> T1 WAN line, and sends o<strong>the</strong>r packets over<strong>the</strong> Internet. This saves bandwidth on <strong>the</strong> more expensive serial interface.274 <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>

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

Saved successfully!

Ooh no, something went wrong!