From: Jason Sinclair (sinclairj@xxxxxxxxxxxxxxx)
Date: Mon Aug 06 2001 - 03:02:35 GMT-3
Fred,
Thanks for that, however can you tell me the state the RSRB peer will be in
if there are no hosts on the ring? When I do it I see the state as closed?
Regards,
Jason Sinclair
Team Leader - NSG
POWERTEL Limited
Level 11, 55 Clarence Street, SYDNEY
Phone: 61-2-8264-3820
Mobile: 0416 105 858
jasons@powertel.net.au
-----Original Message-----
From: Fred Ingham [mailto:fningham@worldnet.att.net]
Sent: Sunday, 5 August 2001 14:47
To: Jason Sinclair
Cc: ccielab@groupstudy.com
Subject: Re: DLSW and RSRB
Jason: The config is correct for DLSW with one MINOR exception.
You need to add the ring-speed <4|16> to the token ring interfaces to have
them insert. With RSRB the ring groups need to be the same and the peer
statement is different (source-bridge remote-peer 100 tcp 2.2.2.2, for
example).
Cheers, Fred.
Jason Sinclair wrote:
>
> Hi,
>
> With DLSW and RSRB the whole purpose is to transport LLC frames?
However,
> when you lab this up with DLSW and no hosts connected to your
media, you
> will have a connected DSLW peer state, HOWEVER will not have a
DLSW circuit
> establisehd. With RSRB the peer state will be closed? Is this
correct or
> have I done something wrong? Partial config below:
>
> Router1
> Source-bridge ring-group 100
> Dlsw local-peer peer-id 1.1.1.1
> Dlsw remote-peer 0 tcp 2.2.2.2
> !
> Int to0
> Ip address 1.1.1.1 255.255.255.0
> Source-bridge 16 1 100
> Source bridge spanning
>
> Router1
> Source-bridge ring-group 200
> Dlsw local-peer peer-id 2.2.2.2
> Dlsw remote-peer 0 tcp 1.1.1.1
> !
> Int to0
> Ip address 2.2.2.2 255.255.255.0
> Source-bridge 17 1 200
> Source bridge spanning
>
> Regards,
>
>
**********************************************************************
> This email (including all attachments) is intended solely for the
named
> addressee. It is confidential and may contain commercially
sensitive
> information. If you receive it in error, please let us know by
reply email,
> delete it from your system and destroy any copies.
>
> This email is also subject to copyright. No part of it should be
reproduced,
> adapted or transmitted without the prior written consent of the
copyright owner.
>
> Emails may be interfered with, may contain computer viruses or
other defects
> and may not be successfully replicated on other systems. We give
no
> warranties in relation to these matters. If you have any doubts
about
> the authenticity of an email purportedly sent by us, please
contact us
> immediately.
>
>
**********************************************************************
> **Please read:http://www.groupstudy.com/list/posting.html
> majordomo@groupstudy.com <mailto:majordomo@groupstudy.com> with
the body containing:
> unsubscribe ccielab
**********************************************************************
This email (including all attachments) is intended solely for the named
addressee. It is confidential and may contain commercially sensitive
information. If you receive it in error, please let us know by reply email,
delete it from your system and destroy any copies.
This email is also subject to copyright. No part of it should be reproduced,
adapted or transmitted without the prior written consent of the copyright owner
.
Emails may be interfered with, may contain computer viruses or other defects
and may not be successfully replicated on other systems. We give no
warranties in relation to these matters. If you have any doubts about
the authenticity of an email purportedly sent by us, please contact us
immediately.
**********************************************************************
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:31:45 GMT-3