From: Aidan Marks (amarks@cisco.com)
Date: Fri Jan 03 2003 - 09:08:57 GMT-3
A peer group/border peer is a scalability enhancement...
from the CCO docs...
"Perhaps the most significant optimization in DLSw+ is a feature known as
peer groups. Peer groups are designed to address the broadcast replication
that occurs in a fully meshed network. When any-to-any communication is
required (for example, for NetBIOS or Advanced Peer-to-Peer Networking
[APPN] environments), RSRB or standard DLSw implementations require peer
connections between every pair of routers. This setup is not only difficult
to configure, but it results in branch access routers having to replicate
search requests for each peer connection. This setup wastes bandwidth and
router cycles. A better concept is to group routers into clusters and
designate a focal router to be responsible for broadcast replication. This
capability is included in DLSw+."
and peer on demand...
"A peer-on-demand peer is a non-configured remote-peer that was connected
because of an LLC2 session established through a border peer DLSw+ network.
On-demand peers greatly reduce the number of peers that must be configured.
You can use on-demand peers to establish an end-to-end circuit even though
the DLSw+ routers servicing the end systems have no specific configuration
information about the peers. This configuration permits casual, any-to-any
connection without the burden of configuring the connection in advance. It
also allows any-to-any switching in large internetworks where persistent
TCP connections would not be possible."
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fibm_c/bcfpart2/bcfdlsw.htm
Make sense?
Aidan
At 02:51 PM 3/01/2003, Hunt Lee wrote:
>Hey Tim,
>
>How did your testing go. Did you managed to find out what is the difference
>between DLSW Peer Groups & Peer-on-demand? I am still very confused whether
>there is any difference between the two.
>
>Thanks in advance,
>
>Best regards,
>Hunt Lee
>
>-----Original Message-----
>From: Ouellette, Tim [mailto:tim.ouellette@eds.com]
>Sent: Wednesday, 1 January 2003 6:46 PM
>To: 'Hunt Lee'
>Cc: 'ccielab@groupstudy.com'
>Subject: RE: Question RE: DLSW Peer Groups and Peer-On-Demand
>
>
>Hunt,
>
>I think based on the fact that you used the promiscious that you are
>basically doing the same as PoD.
>
>This is also shown in your "sh dlsw peer" for RTC
>
> TCP 5.5.5.5 CONNECT 523 532 pod 0 1 0
>00:12:35
>
>I was wondering also if the POD and the promiscious basically did the same
>thing but I think the promiscious just allows a connection from anywhere,
>whereas the POD default allows a session from another router that is
>connected to a peer of your border peer. If that makes sense. I'll try and
>test tonight.
>
>Tim
>
>
>-----Original Message-----
>From: Hunt Lee [mailto:ciscoforme3@yahoo.com.au]
>Sent: Wednesday, January 01, 2003 2:55 AM
>To: ccielab@groupstudy.com
>Subject: Question RE: DLSW Peer Groups and Peer-On-Demand
>
>
>Hi
>
>Happy Holiday to all.
>
>I have some question that I would like to ask the group regarding DLSW Peer
>Groups
>and Peer-On-Demand.
>
>I have a home lab where the topology is as follows:
>
>RTA & RTC are DLSW Border Peers, while the others are DLSW Remote Peers
>
>SNA PU2 -- RTE ------- RTA --- RTC --- SNA PU5
> | |
> RTB RTD
>
>
>
>According to Solie, one needs to use "dlsw peer-on-demand-default
>tcp-queue-max"
>command to setup Peer-On-Demand. However, on my setup above, I didn't use
>it at
>all, yet I still gets the POD Peer establiahsed.
>
>RTC#sh dlsw peer
>Peers: state pkts_rx pkts_tx type drops ckts TCP
>uptime
> TCP 1.1.1.1 CONNECT 344 342 prom 0 0 0
>02:27:42
> TCP 5.5.5.5 CONNECT 523 532 pod 0 1 0
>00:12:35
> TCP 4.4.4.4 CONNECT 312 366 prom 0 0 0
>02:25:49
>
>So are DLSW Peer Groups(Border Peers) & Peer-on-Demand the SAME THING????
>If not,
>what is the difference, & when would one wants to use the "dlsw
>peer-on-demand-default tcp-queue-max" command?
>
>Anyway, below are my partial configs:-
>
>RTA#sh run
>Building configuration...
>
>hostname RTA
>!
>!
>dlsw local-peer peer-id 1.1.1.1 group 1 border promiscuous
>dlsw remote-peer 0 tcp 3.3.3.3
>dlsw bridge-group 1
>!
>interface Loopback0
> ip address 1.1.1.1 255.255.255.255
>!
>interface FastEthernet0/0
> ip address 172.16.3.1 255.255.255.0
> speed 10
> half-duplex
> bridge-group 1
>!
>interface Serial0/0
> description to RTC
> ip address 10.64.3.177 255.255.255.240
> clockrate 64000
>!
>!
>interface Serial1/2
> description to RTB
> ip address 10.64.3.99 255.255.255.240
> no ip mroute-cache
> clockrate 64000
>!
>interface Serial1/3
> description to RTE
> ip address 10.64.3.161 255.255.255.240
> clockrate 64000
>!
>router eigrp 1
> network 1.0.0.0
> network 10.0.0.0
> no auto-summary
> no eigrp log-neighbor-changes
>!
>!
>bridge 1 protocol ieee
>!
>!
>end
>
>RTA#
>
>=====================================================
>
>RTB#sh run
>Building configuration...
>
>hostname RTB
>!
>dlsw local-peer peer-id 2.2.2.2 group 1 promiscuous
>dlsw remote-peer 0 tcp 1.1.1.1
>dlsw bridge-group 1
>!
>!
>interface Loopback0
> ip address 2.2.2.2 255.255.255.255
>!
>interface Ethernet0
> no ip address
> bridge-group 1
>!
>interface Serial0
> description to RTA
> ip address 10.64.3.97 255.255.255.240
> no fair-queue
>!
>!
>router eigrp 1
> network 2.0.0.0
> network 10.0.0.0
> no auto-summary
> no eigrp log-neighbor-changes
>!
>!
>!
>end
>
>RTB#
>
>=====================================================
>
>RTC#sh run
>Building configuration...
>!
>hostname RTC
>!
>!
>!
>!
>dlsw local-peer peer-id 3.3.3.3 group 2 border promiscuous
>dlsw bridge-group 1
>!
>interface Loopback0
> ip address 3.3.3.3 255.255.255.255
>!
>interface FastEthernet0/0
> no ip address
> speed 10
> half-duplex
> bridge-group 1
>!
>interface Serial0/0
> description to RTA
> ip address 10.64.3.178 255.255.255.240
> no fair-queue
>!
>interface Serial0/1
> description to RTD
> ip address 10.64.3.194 255.255.255.240
>!
>router eigrp 1
> network 3.0.0.0
> network 10.0.0.0
> no auto-summary
>!
>!
>!
>bridge 1 protocol ieee
>end
>
>RTC#
>
>========================================================
>
>RTD#sh run
>!
>hostname RTD
>!
>!
>dlsw local-peer peer-id 4.4.4.4 group 2 promiscuous
>dlsw remote-peer 0 tcp 3.3.3.3
>dlsw bridge-group 1
>!
>interface Loopback0
> ip address 192.168.1.1 255.255.255.255
>!
>interface Loopback1
> ip address 4.4.4.4 255.255.255.255
>!
>interface Ethernet0
> no ip address
> bridge-group 1
>!
>interface Serial0
> description to RTC
> ip address 10.64.3.195 255.255.255.240
> no fair-queue
> clockrate 64000
>!
>!
>router eigrp 1
> network 4.0.0.0
> network 10.0.0.0
> no auto-summary
> no eigrp log-neighbor-changes
>!
>!
>bridge 1 protocol ieee
>!
>!
>end
>
>RTD#
>
>=================================================
>
>RTE#sh run
>!
>hostname RTE
>!
>!
>!
>dlsw local-peer peer-id 5.5.5.5 group 1 promiscuous
>dlsw remote-peer 0 tcp 1.1.1.1
>dlsw bridge-group 1
>!
>!
>interface Loopback0
> ip address 5.5.5.5 255.255.255.255
>!
>interface Ethernet0
> no ip address
> bridge-group 1
>!
>!
>interface Serial1
> description to RTA
> ip address 10.64.3.162 255.255.255.240
> no fair-queue
>!
>!
>router eigrp 1
> network 5.0.0.0
> network 10.0.0.0
> no auto-summary
> no eigrp log-neighbor-changes
>!
>!
>!
>bridge 1 protocol ieee
>!
>!
>end
>
>RTE#
>
>Any help on this topic would be helpful. I am trying to understand how all
>these 2
>component can work together / related?
>
>Thanks.
>Hunt Lee
>
>http://movies.yahoo.com.au - Yahoo! Movies
>- What's on at your local cinema?
>.
>.
>.
.
This archive was generated by hypermail 2.1.4 : Sat Feb 01 2003 - 07:33:39 GMT-3