From: yijibin (yijibin@xxxxxxxxxxxxxxxx)
Date: Sat Jun 08 2002 - 23:52:50 GMT-3
If you use a border peer in dlsw, R1 will not see the netbios name cache in rem
ote cache, but in the group cache!
----- Original Message -----
From: "Michael Popovich" <m.popovich@mchsi.com>
To: "CCIE GROUPSTUDY" <ccielab@groupstudy.com>
Sent: Sunday, June 09, 2002 6:03 AM
Subject: Question about DLSW and Groups
> Host--R1----Ethernet-----R2
> / \
> FR FR
> / \
> R5 R6
> | |
> |--Ethernet---|
> |
> Server
>
> R2 is a Border Peer for Group 10. R5 and R6 are part of group 10. R5 and R6
> have promiscuous setup on their local peer statements and they each have one
> remote-peer statement to R2
>
> R2 is also setup with promiscuous on it's local peer statement with only one
> remote peer statement to R1.
>
> R1 is a border peer of Group 1 and is the only router in the group. It too ha
s
> promiscuous set on the local peer statement with only 1 remote peer to R2.
>
> The host on the Ethernet segment from R1 tries to browse to the server sittin
g
> on the segment shared by R5 and R6 connects successfully. I can browse and
> download files.
>
> What I am questioning or trying to understand is why the Server NetBIOS name
> is not in R1's remote reachability cache. It shows up in R2's cache but not
> R1.
>
> Any ideas or insights on this?
>
> TIA
>
> MP
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:29 GMT-3