From: Bhisham Bajaj (bhishambajaj@xxxxxxxxx)
Date: Sun Mar 31 2002 - 12:26:46 GMT-3
It worked for me some how
on the Fr physical int , fr sub int PTP & Mult also
one thing but i have not got is that it only works
when u map the LLc2 and when i map DLSW it does not
work
my question is when and why do we need the command
frame-relay map DLSW 101 broadcast
r1--- (FR & dlsw) --------r2
hostname R1
!
frame-relay switching
!
dlsw local-peer peer-id 1.1.1.1
dlsw remote-peer 0 frame-relay interface Serial0.2 101
dlsw bridge-group 1
!
interface Loopback5
ip address 1.1.1.1 255.255.0.0
!
interface Ethernet0
no ip address
ip directed-broadcast
no keepalive
bridge-group 1
!
interface Serial0
no ip address
encapsulation frame-relay
clockrate 64000 ( this is the dce end)
frame-relay intf-type dce ( this is the Fr switch)
!
interface Serial0.2 multipoint
no ip directed-broadcast
frame-relay map llc2 101 broadcast
frame-relay interface-dlci 101
!
bridge 1 protocol ieee
!
end
hostname R2
!
dlsw local-peer peer-id 2.2.2.2
dlsw remote-peer 0 frame-relay interface Serial0.2 101
dlsw bridge-group 1
!
interface Loopback5
ip address 2.2.2.2 255.255.0.0
!
interface Ethernet0
no ip address
no keepalive
bridge-group 1
!
interface Serial0
no ip address
encapsulation frame-relay
!
interface Serial0.2 multipoint
frame-relay map llc2 101 broadcast
frame-relay interface-dlci 101
!
bridge 1 protocol ieee
!
end
R1#sh dlsw peer
Peers: state pkts_rx pkts_tx
type drops ckts TCP uptime
LLC2 Se0.2 101 CONNECT 13 13
conf 0 0 - 00:05:49
Total number of connected peers: 1
Total number of connections: 1
R1#sh dlsw c
R1#sh dlsw ca
R1#sh dlsw capabilities
DLSw: Capabilities for peer on interface Serial0
vendor id (OUI) : '00C' (cisco)
version number : 2
release number : 0
init pacing window : 20
unsupported saps : none
num of tcp sessions : 1
loop prevent support : no
icanreach mac-exclusive : no
icanreach netbios-excl. : no
reachable mac addresses : none
reachable netbios names : none
V2 multicast capable : yes
DLSw multicast address : none
cisco version number : 1
peer group number : 0
border peer capable : no
peer cost : 3
biu-segment configured : no
UDP Unicast support : yes
NetBIOS Namecache length : 15
local-ack configured : yes
priority configured : no
configured ip address : 2.2.2.2
peer type : conf
version string :
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-INS-L), Version
12.0(20), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Tue 02-Oct-01 08:20 by nmasa
BB
--- yakout esmat <yesmat@iprimus.com.au> wrote:
> After many trials, here is the outcome:
>
> 1) IP address in the local peer command can be used
> (which is usefull in
> exam environment, because you most probably will
> need that for other tcp
> peering sessions with other peers)
> 2) Loopback IP address will work fine, (DON'T have
> to use serial IP
> addresses)
> 2) PHYSICAL INTERFACE ONLY, NO SUBINTERFACE ever
> worked.
>
> If anybody needs the config, let me know
>
> Thanks
>
> -----Original Message-----
> From: nobody@groupstudy.com
> [mailto:nobody@groupstudy.com]On Behalf Of
> MOLINA, MARTIN J *Internet* (PBI)
> Sent: Saturday, March 30, 2002 4:31 PM
> To: 'yakout esmat'; Groupstudy
> Subject: RE: DLSW Direct encap
>
>
> Check out the archives my friend. I believe you have
> to do 3 things:
> 1. Do not specify an IP address in your local peer
> statements on either side
> 2. Frame map dlsw (which you already have done)
> 3. And I believe you have to use physical interfaces
> as opposed to
> sub-interfaces
> Good luck!
>
> -----Original Message-----
> From: yakout esmat [mailto:yesmat@iprimus.com.au]
> Sent: Friday, March 29, 2002 8:58 PM
> To: Groupstudy
> Subject: DLSW Direct encap
>
>
> Hi all,
>
> I am having a problem getting my direct
> encapsulation peers connected.
>
> r5 is hub r6,r3&r1 are spokes: (encap frame relay)
>
> Following is my configs:
>
> r5#
> !
> dlsw local-peer peer-id 200.200.100.1
> dlsw remote-peer 0 frame-relay interface Serial0.1
> 405 pass-thru
> dlsw remote-peer 0 frame-relay interface Serial0.1
> 403 pass-thru
> dlsw remote-peer 0 frame-relay interface Serial0.2
> 402 pass-thru
> !
> !
> interface Serial0
> no ip address
> encapsulation frame-relay
> no fair-queue
> frame-relay traffic-shaping
> !
> interface Serial0.1 multipoint
> description link to r3&r1
> ip address 155.10.100.5 255.255.255.240
> ip ospf authentication message-digest
> ip ospf message-digest-key 1 md5 cisco
> ip ospf dead-interval 40
> ip ospf priority 200
> frame-relay class cisco
> frame-relay map dlsw 403
> frame-relay map dlsw 405
> frame-relay map ip 155.10.100.1 403 broadcast
> frame-relay map ip 155.10.100.3 405 broadcast
> !
> interface Serial0.2 point-to-point
> description link to r6
> ip address 155.10.200.5 255.255.255.0
> ip ospf message-digest-key 1 md5 cisco
> frame-relay interface-dlci 402
> !
> r1&r3&r6#
> dlsw local-peer peer-id 155.10.1.1
> dlsw remote-peer 0 frame-relay interface Serial0 304
> pass-thru
> !
> interface Serial0
> ip address 155.10.100.1 255.255.255.240
> encapsulation frame-relay
> ip ospf authentication message-digest
> ip ospf message-digest-key 1 md5 cisco
> ip ospf dead-interval 40
> ip ospf priority 0
> frame-relay map dlsw 304
> frame-relay map ip 155.10.100.3 304 broadcast
> frame-relay map ip 155.10.100.5 304 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type cisco
> !
>
> When I use direct encap no connection gets formed,
> but when I use DLSW Lite
> (llc2) it works fine. Am I missing some thing?
>
> Thanks
>
> ya
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:27 GMT-3