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 a WAN InterfaceFigure 6: <strong>G350</strong> with T1 and xDSL lines2 x T1/E1 or USP WAN ModuleT1<strong>G350</strong>S8300VoiceVlan1DSCPRouterT1ISPxDSL1DataVlan2DSCPHub/SwitchHeadquartersSmall BranchFor example, your branch <strong>of</strong>fice may have a <strong>G350</strong> that connects to <strong>the</strong> Headquarters over a T1line and via an xDSL connection to <strong>the</strong> Internet. The T1 line is used for voice traffic, while datapackets are sent over <strong>the</strong> xDSL line. Normal keepalive cannot report on <strong>the</strong> status <strong>of</strong> <strong>the</strong> entireWAN path. If <strong>the</strong> FastE<strong>the</strong>rnet line protocol is up but <strong>the</strong> xDSL connected to it is down, normalkeepalive reports that <strong>the</strong> FastE<strong>the</strong>rnet interface is up. Only Extended Keepalive, which checks<strong>the</strong> next hop, correctly reports that <strong>the</strong> WAN path is down. Policy-based-routing, which relies on<strong>the</strong> interface status to determine how packets are routed, can use Extended Keepalive to know<strong>the</strong> status <strong>of</strong> <strong>the</strong> interfaces on its next hop list.Note:Note:Extended Keepalive is not used with a GRE tunnel interface. The GRE tunnel hasits own keepalive mechanism. For details, refer to <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong><strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>, 555-245-501.Use <strong>the</strong> extended-keepalive command in <strong>the</strong> context <strong>of</strong> <strong>the</strong> interface to enable <strong>the</strong>extended keepalive feature. Use <strong>the</strong> no form <strong>of</strong> this command to deactivate <strong>the</strong> feature.The extended-keepalive command includes <strong>the</strong> following parameters:●●destination ip address — <strong>the</strong> destination IP address for <strong>the</strong> keepalive packets.next hop MAC address — <strong>the</strong> next hop MAC address for <strong>the</strong> keepalive packets. Thisparameter is only relevant for <strong>the</strong> WAN Fast E<strong>the</strong>rnet port.Use <strong>the</strong> following commands to define <strong>the</strong> extended keepalive parameters. For moreinformation about <strong>the</strong>se commands, see <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong> CLI Reference,555-245-202.●●Use <strong>the</strong> extended-keepalive timeout command to set <strong>the</strong> timeout (in seconds) forreceiving <strong>the</strong> keepalive response. The default value is 1.Use <strong>the</strong> extended-keepalive success-retries command to set <strong>the</strong> number <strong>of</strong>consecutive successful keepalive packets necessary to set <strong>the</strong> interface’s keepalive statusas up. The default value is 1.100 <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!