Administration of the Avaya G350 Media Gateway - Avaya Support
13.07.2015 • Views
Share Embed Flag

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
ePAPER READ
DOWNLOAD ePAPER
downloads.avaya.com

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

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

START NOW

Configuring <strong>the</strong> routerThe following are recommended ways to avoid nested tunneling:●Announce policy.Configure a policy rule on <strong>the</strong> receiving tunnel endpoint (router 2) that will cause <strong>the</strong>receiving endpoint to block advertisements <strong>of</strong> <strong>the</strong> source network (192.68.1.0) in its routingupdates. This will prevent <strong>the</strong> source endpoint (router 1) from learning <strong>the</strong> route. Thissolution is for nested tunneling caused by RIP. For example, using <strong>the</strong> network shown inFigure 12 as an illustration, you would configure <strong>the</strong> following policy rule on router 2 andactivate it on <strong>the</strong> router RIP with <strong>the</strong> matching interface:.<strong>G350</strong>-001(super)# ip distribution access-list-name 1 "list #1"Done!<strong>G350</strong>-001(super)# ip distribution access-default-action 1 default-action-permitDone!<strong>G350</strong>-001(super)# ip distribution access-list 1 10 "deny" 192.68.1.0 0.0.0.255Done!<strong>G350</strong>-001(super)# router rip<strong>G350</strong>-001(super router:rip)# distribution-list 1 out FastE<strong>the</strong>rnet 10/2Done!<strong>G350</strong>-001(super router:rip)# exit<strong>G350</strong>-001(super)#●Accept policy.Configure a policy rule on <strong>the</strong> source tunnel endpoint (router 1) that will cause <strong>the</strong> sourceendpoint to not accept routing updates that include <strong>the</strong> source network (192.68.1.0). Thissolution is for nested tunneling caused by RIP. For example, using <strong>the</strong> network shown inFigure 12 as an illustration, you would configure <strong>the</strong> following policy rule on router 1 andactivate it on <strong>the</strong> router RIP with <strong>the</strong> matching interface:<strong>G350</strong>-001(super)# ip distribution access-list-name 1 "list #1"Done!<strong>G350</strong>-001(super)# ip distribution access-default-action 1 default-action-permitDone!<strong>G350</strong>-001(super)# ip distribution access-list 1 10 "deny" 192.68.1.0 0.0.0.255Done!<strong>G350</strong>-001(super)# router rip<strong>G350</strong>-001(super router:rip)# distribution-list 1 in FastE<strong>the</strong>rnet 10/2Done!<strong>G350</strong>-001(super router:rip)# exit<strong>G350</strong>-001(super)#●Static route.Configure a static rule on router 1 telling it <strong>the</strong> route for packets destined to <strong>the</strong> tunnel’sreceiving endpoint (192.68.1.2). This route should be configured with a high routepreference. For example:<strong>G350</strong>-001(super)# ip route 192.68.1.2 255.255.0.0 192.68.1.3 high permanentDone!<strong>G350</strong>-001(super)#170 <strong>Administration</strong> <strong>of</strong> <strong>the</strong> <strong>Avaya</strong> <strong>G350</strong> <strong>Media</strong> <strong>Gateway</strong>

logo

products

Resources

Company

Terms of service
Privacy policy
Cookie policy
Cookie settings
Imprint
Change language
Made with love in Switzerland
© 2024 Yumpu.com all rights reserved

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

Saved successfully!

Ooh no, something went wrong!