The other two commands are specific to icmp and telnet which needs one way translation.
The first rule with reversible option ensures the connectivity is bi-directional direction. The next hop command forces all the translated traffic by first rule to use R6 as next hop. Unless I do the lab, I can't say the reason :-) But the task doesn't seem to ask for it specifically. With regards Kings On Sat, Nov 6, 2010 at 7:31 PM, Johan Bornman <[email protected]> wrote: > Thanks, Kings. I understand that, but why do the other 2 statics not have > the rev command in, when is it necessary? > > > > > > *From:* Kingsley Charles [mailto:[email protected]] > *Sent:* 06 November 2010 03:47 PM > *To:* Johan Bornman > *Cc:* OSL Security > *Subject:* Re: [OSL | CCIE_Security] Task 7.2 > > > > Normal static nat rules without route-maps doesn't have the option of > reversible as it is always bi-directional. > > To make static nat rules with route-maps bi-directional, the reversible > keyword is used. > > > With regards > Kings > > On Sat, Nov 6, 2010 at 6:48 PM, Johan Bornman <[email protected]> wrote: > > Hi, > > > > Please explain the commands in context of the task (in red): > > > > route-map R8R6 permit 10 > > set ip next-hop 7.56.0.6 – Why the next hop? > > > > ip nat inside source static 10.7.8.8 7.56.0.1 route-map R8ANY reversible – > Why the command reversible? The other static nat’s don’t have it as part > of the solution. > > > > Thanks > > > > Johan > > > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
