Re: neighbor <IP> disable-connected-check

From: Bit Gossip <bit.gossip_at_chello.nl>
Date: Fri, 14 May 2010 20:35:14 +0200

What I want to stress is that the DocCD here is not correct/complete:

DocCD: "This command is required **ONLY** when the neighbor
ebgp-multihop command...."

Bit.Gossip: This command is required **NOT ONLY** with the 'neighbor
ebgp-multihop' command, but **ALSO** with 'neighbor <IP> ttl-security
hops 1'

These 2 statements don't look the same to me.

Bit.

> > is configured with a TTL value of 1."

On Fri, 2010-05-14 at 22:31 +0530, GAURAV MADAN wrote:
> arent you logically referring to same stuff .
>
> this cli is used when ur peer is not directly conneced ..... hence
> once you want to estalish the bgp peering with non-directly connected
> neighbor .
>
> Gaurav Madan
> CCIE
>
> On Fri, May 14, 2010 at 7:54 PM, Bit Gossip <bit.gossip_at_chello.nl> wrote:
> > http://cisco.com/en/US/partner/docs/ios/iproute_bgp/command/reference/irg_bgp3.html#wp1064360
> >
> > "This command is required only when the neighbor ebgp-multihop command
> > is configured with a TTL value of 1."
> >
> > In reality it is required ALSO when:
> > 'neighbor <IP> ttl-security hops 1'
> > is configured !!
> >
> > HTH,
> > L
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Fri May 14 2010 - 20:35:14 ART

This archive was generated by hypermail 2.2.0 : Tue Jun 01 2010 - 07:09:53 ART