From: DAN DORTON (DHSTS68@xxxxxxxxxxxxxxx)
Date: Tue Apr 23 2002 - 10:21:08 GMT-3
If one of the requirements of the task is to allow one of the remote peers to a
ccess a local port on a non directly connected border peer then you would want
to use the prom keyword on that border peers local peer statement as well.
IE:
(R1 Group1 (R3 Border peer))===((R4 Border peer) Group2 R2)
In this case if R1 needs to reach R2 through the border peers R1 & R2 must have
the prom keyword in their local peer statements, but R3 & R4 do not require it
.
If R2 needs to access lets say Ring 300 on R3 then R3 will need the prom keywor
d in it's local peer statement as well.
Just think of promiscuous as being needed when the router can except remote con
nections to other routers that a remote peer is not configured for.
Hope this helps,
Dan
>>> Jason Sinclair <sinclairj@powertel.com.au> 04/22/02 08:35PM >>>
Dennis,
OK - to clarify this, border peers are used to eliminate the requirement to
have a full mesh of dlsw peers. That said, the prom keyword on the border
peer is for the members of that peer group to connect to the border peer.
Generally you will use the remote-peer statement on border peers to connect
to other border peers.
The way this works is that you have a border peer (RtrA) which will be
connected to border peer (RtrB). RtrX, RtrY are in the same peer group as
RtrA and RtrZ is in the same peer group as RtrB. If you define a remote-peer
from A to B and vice versa, you can also define the local peer on both these
routers as promiscuous to enable you to only have to define remote peer
statements on X, Y and Z.
Regards,
Jason Sinclair CCIE #9100
Manager, Network Support Group
POWERTEL
Ground Level, 55 Clarence Street,
SYDNEY NSW 2000
AUSTRALIA
office: + 61 2 8264 3820
mobile: + 61 416 105 858
* sinclairj@powertel.com.au
-----Original Message-----
From: Dennis.D.Adekola@britishairways.com
[mailto:Dennis.D.Adekola@britishairways.com]
Sent: Monday, 22 April 2002 20:23
To: steven.j.nelson@bt.com
Cc: ccielab@groupstudy.com
Subject: RE: when should we use" promiscuous" keyword
in dlsw config?
Alright i understand that bit
The part that puzzles me is........
How come you would normally configure" Prom" on both border
peers.
How does each border peer create a connection to the other
if they both
have "prom" configured
This is having the impression that "Prom" means "do not
initiate connection
but recieve connections"
Imputs will be well appreciated
Dennis
steven.j.nelson@bt.com@groupstudy.com on 22/04/2002 10:20:15
Please respond to steven.j.nelson@bt.com
Sent by: nobody@groupstudy.com
To: trueccie
ccielab
cc:
bcc:
Subject: RE: when should we use" promiscuous" keyword in
dlsw config?
Steve,
Promiscuous mode simply means allow connections to this box
from anyone,
whether they are a defind peer, by dlsw remote-peer command
or not.
Usefull if you have loads of remote peers peering to one box
and you don't
want to codes loads of lines of remote peer statements.
Peers groups are a bit different, for full explanation I
would look it up
on
CCO if I were you.
Thanks
Steve
-----Original Message-----
From: Steven Owen [mailto:trueccie@yahoo.com]
Sent: 22 April 2002 10:08
To: Nelson,SJ,Steven,IVNH25 C; ccielab
Subject: Re: when should we use" promiscuous" keyword in
dlsw config?
Do you mean this when some time if you don't know a
remote-peer's ip
address?
If two dlsw router configured "local-peer ...promiscuous",no
remote peer
config,
they can build peer relation once they have route to each
other?
Right?
Thanks.
----- Original Message -----
From: <steven.j.nelson@bt.com>
To: <trueccie@yahoo.com>; <ccielab@groupstudy.com>
Sent: Monday, April 22, 2002 4:43 PM
Subject: RE: when should we use" promiscuous" keyword in
dlsw config?
> Steve
>
> also a useful tool when configuring border groups, i.e
peer to peer
> connectivity when no remote statements are present and you
have no direct
> peer to the device that you want to connect to.
>
> Thanks
>
> Steve
>
> -----Original Message-----
> From: Steven Owen [mailto:trueccie@yahoo.com]
> Sent: 22 April 2002 09:23
> To: ccielab
> Subject: when should we use" promiscuous" keyword in dlsw
config?
>
>
> The CCO explains like this "(Optional) Accepts connections
from
> nonconfigured remote peers."
> when you config a dlsw local-peer.
> So does this keyword just save us remote peer configs?any
other use ?
> or when do we have to use it ?
>
> Thanks.
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:58:17 GMT-3