From: Joe Chang (changjoe@earthlink.net)
Date: Thu Mar 27 2003 - 21:43:43 GMT-3
An alternative is the "dlsw transparent map" interface-level command. On the
6509, under each vlan interface, you can replace the SMAC of the explorer
with a value of your own invention. It's kind of like NAT, created
specifically for these ethernet switch on DLSW problems.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fibm
_r1/br1fprt2/1027844
----- Original Message -----
From: "David Ham" <ccieau@yahoo.com>
To: "Joe Chang" <changjoe@earthlink.net>; <ccielab@groupstudy.com>
Sent: Thursday, March 27, 2003 9:19 PM
Subject: Re: some DLSW circuit drop on MSFC
> Joe,
>
> Thanks for your reply but moving seperate VLANs to one
> vlan and bridge it cross the DLSW on 6509 might cause
> excessive broadcast traffic.
>
> As I mentioned, I created truck between 6509 and 4006
> so that all the VLANs can cross to 6509.
>
> Here is the part of 6509 config
>
> dlsw local-peer peer-id 10.2.248.4
> dlsw remote-peer 0 tcp 10.0.255.11
> dlsw bridge-group 1
> dlsw bridge-group 2
> dlsw bridge-group 3
> dlsw bridge-group 4
> ; :
> ; :
> ; :
> dlsw bridge-group 27
>
> int vlan 700
> bridge-group 1
>
> int vlan 701
> bridge-group 2
> : :
> : :
> inte vlan 727
> bridge-group 27
> etc
>
> Are you saying like below ??
>
> dlsw local-peer peer-id 10.2.248.4
> dlsw remote-peer 0 tcp 10.0.255.11
> dlsw bridge-group 1
>
>
> int vlan 700
> bridge-group 1
>
> int vlan 701
> bridge-group 1
> : :
> : :
> inte vlan 727
> bridge-group 1
> etc
>
>
> Regards,
>
> David
>
> --- Joe Chang <changjoe@earthlink.net> wrote: >
> > ----- Original Message -----
> > From: "David Ham" <ccieau@yahoo.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Thursday, March 27, 2003 3:26 AM
> > Subject: some DLSW circuit drop on MSFC
> >
> >
> > > Hi all,
> > >
> > > I have urgent question to ask. I am having trouble
> > to
> > > keep the number of dlsw circuits to be stable in
> > > production area.
> > >
> > > Senario is like this
> > >
> > > <--- 6509 MSFC --- trunk --- 4006
> > >
> > > Since 4006 is not capable of handling DLSW, I have
> > set
> > > up a ISL trunk to 6509 and creat vlans and bridge
> > the
> > > vlans into DLSW on 6509 MSFC.
> > >
> > > Objective is that I need get about 20 vlans across
> > and
> > > bridge them into DLSW.
> > >
> > > So far I can see DLSW peer is established and can
> > see
> > > some dlsw circuits that are connected. But the
> > issue
> > > is that I can see only about 10 circuits are
> > stable
> > > and rest of them are repeatly droped out after
> > having
> > > about 10 sec connection and so on.
> > >
> > >
> > > Have you guys seen something like that??
> > > Please let me know if you have any idea.
> > >
> > > Regards,
> > >
> > > David Ham
> >
> > Are each of the SNA terminals on a separate VLAN on
> > the 4006? If so, try
> > moving them all on the same VLAN. Here's a possible
> > reason your scenario is
> > not working.
> >
> > A logical view of your network:
> >
> > <--- 6509 MSFC -- vlan x --- 4006 --- terminal x
> > -- vlan y ---
> > --- terminal y
> > -- vlan z ---
> > --- terminal z
> >
> > When the first explorer is received by the 6509 (say
> > for terminal x) the
> > reachability caches will be empty. 6509 has to send
> > a SNA test frame out
> > each of its dlsw enabled LANs, in this case the VLAN
> > interfaces. The source
> > mac of the replicated test frames will not be that
> > of the vlan, but of the
> > head-end host that is initiating all this. The 4006
> > will receive one copy of
> > the test frame, associate the SMAC with the vlan in
> > its CAM table. Then the
> > switch may receive another copy of the frame,
> > rewrite the CAM so that the
> > SMAC is associated with another vlan, and so on.
> > Receiving the test frame,
> > terminal x will respond with its own frame, which
> > the 6509 may or may not
> > receive from the correct vlan depending on the state
> > of the CAM at that
> > moment. A circuit will be established between the
> > DLSW peers, but the 6509
> > probably will have an incorrect local reachability
> > table. Subsequent test
> > frames for the other terminals will then add to this
> > confusion.
> >
> >
>
> http://mobile.yahoo.com.au - Yahoo! Mobile
> - Check & compose your email via SMS on your Telstra or Vodafone mobile.
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:45 GMT-3