From: Bernard Dunn (dunn@xxxxxxxxx)
Date: Thu Jan 18 2001 - 12:24:00 GMT-3
My bad - CCO doc has a problem..
On Wed, 17 Jan 2001, Jeffrey Wacaser wrote:
> From the 12.0 docs:
> http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121cgcr/ibm_r
/brprt2/br1ddlsw.htm#xtocid2979814
>
> Optional) MAC address mask in hexadecimal h.h.h. The "f" value
> represents the "don't care" bit and the "0" value represents the "care"
> bit. The mask indicates which bits in the MAC address
> are relevant.
>
> I believe the 12.1 and 11.3 etc state the same. This would mean 12.0
> docs are incorrect along with the 12.1 and 11.3. What am I missing?
>
> Bernard Dunn wrote:
>
> > All,
> >
> > The 12.0 Command Reference is correct. We have lots of banking customers
> > using 'dlsw icanreach mac' commands.
> >
> > The mask bits are:
> >
> > '1' = care bits
> > '0' = don't care bits
> >
> > Again, use the latest IOS version documentation. Example configs from old
> > versions maybe good for conceptual understanding, but we sometimes can
> > only chase down latest version documentation and fix them, since we've
> > restructured CCO documentation so much of late.
> >
> >
> > Regards
> >
> > Bernard.
> >
> >
> > On Tue, 16 Jan 2001, Barry J. Bocaner wrote:
> >
> >> OK, I couldn't wait until work was over, had to test this now.
> >>
> >> I am reversing myself on this one! I believe the command reference is
> >> wrong.
> >>
> >> I am *now* of the opinion that in an icanreach mac-address mask a 'f' is a
> >> care and a '0' is a don't care. Again, it is *not* an inverse mask.
> >>
> >> Here's how I tested it... please let me know if you have a problem with my
> >> config or methodology:
> >>
> >> netbios LABPC --------- R1 -----frame----- R2 ----- netbios BARRYBOOK2
> >>
> >> I plugged the lab PC into R1's fa0/0, configured connectivity between R1
> >> and R2, and plugged my notebook into R2 fa0/1. I then put in my dlsw
> >> config. Here are the configs:
> >>
> >> version 12.1
> >> service timestamps debug uptime
> >> service timestamps log uptime
> >> no service password-encryption
> >> !
> >> hostname router1
> >> !
> >> !
> >> !
> >> !
> >> !
> >> !
> >> ip subnet-zero
> >> no ip finger
> >> !
> >> ip audit notify log
> >> ip audit po max-events 100
> >> cns event-service server
> >> !
> >> !
> >> !
> >> dlsw local-peer peer-id 10.0.0.1
> >> dlsw remote-peer 0 tcp 10.0.0.2
> >> dlsw bridge-group 1
> >> !
> >> !
> >> !
> >> !
> >> !
> >> interface Loopback0
> >> ip address 10.0.0.1 255.255.255.255
> >> !
> >> interface FastEthernet0/0
> >> no ip address
> >> duplex auto
> >> speed auto
> >> bridge-group 1
> >> !
> >> interface Serial0/0
> >> no ip address
> >> encapsulation frame-relay
> >> !
> >> interface Serial0/0.102 point-to-point
> >> ip address 10.10.1.1 255.255.255.0
> >> frame-relay interface-dlci 102
> >> !
> >> interface FastEthernet0/1
> >> no ip address
> >> shutdown
> >> duplex auto
> >> speed auto
> >> !
> >> interface Serial0/1
> >> no ip address
> >> shutdown
> >> !
> >> router ospf 1
> >> log-adjacency-changes
> >> network 10.0.0.1 0.0.0.0 area 0
> >> network 10.10.1.0 0.0.0.255 area 0
> >> !
> >> ip classless
> >> no ip http server
> >> !
> >> !
> >> bridge 1 protocol ieee
> >> !
> >> line con 0
> >> transport input none
> >> line aux 0
> >> line vty 0 4
> >> !
> >> no scheduler allocate
> >> end
> >>
> >> !
> >> version 12.1
> >> service timestamps debug uptime
> >> service timestamps log uptime
> >> no service password-encryption
> >> !
> >> hostname router2
> >> !
> >> !
> >> !
> >> !
> >> !
> >> !
> >> ip subnet-zero
> >> no ip finger
> >> !
> >> ip audit notify log
> >> ip audit po max-events 100
> >> cns event-service server
> >> !
> >> !
> >> !
> >> dlsw local-peer peer-id 10.0.0.2
> >> dlsw remote-peer 0 tcp 10.0.0.1
> >> dlsw bridge-group 1
> >> !
> >> !
> >> !
> >> !
> >> !
> >> interface Loopback0
> >> ip address 10.0.0.2 255.255.255.255
> >> !
> >> interface FastEthernet0/0
> >> no ip address
> >> shutdown
> >> duplex auto
> >> speed auto
> >> !
> >> interface Serial0/0
> >> no ip address
> >> encapsulation frame-relay
> >> !
> >> interface Serial0/0.201 point-to-point
> >> ip address 10.10.1.2 255.255.255.0
> >> frame-relay interface-dlci 201
> >> !
> >> interface FastEthernet0/1
> >> no ip address
> >> shutdown
> >> duplex auto
> >> speed auto
> >> bridge-group 1
> >> !
> >> interface Serial0/1
> >> no ip address
> >> shutdown
> >> !
> >> router ospf 1
> >> log-adjacency-changes
> >> network 10.0.0.2 0.0.0.0 area 0
> >> network 10.10.1.0 0.0.0.255 area 0
> >> !
> >> ip classless
> >> no ip http server
> >> !
> >> !
> >> bridge 1 protocol ieee
> >> !
> >> line con 0
> >> transport input none
> >> line aux 0
> >> line vty 0 4
> >> !
> >> no scheduler allocate
> >> end
> >>
> >> OK, I can browse and read files on LABPC from BARRYBOOK2.
> >>
> >> Now, on R1 I add:
> >>
> >> dlsw icanreach mac-exclusive
> >> dlsw icanreach mac-address 1111.1111.1111
> >>
> >> the router automatically added the mask ffff.ffff.ffff onto the end of
> >> that.
> >>
> >> Now, assuming ffff.ffff.ffff is all don't care, I should still be able to
> >> access LABPC from BARRYBOOK2, right?
> >>
> >> Well... *drumroll* I can't.
> >>
> >> I remove the dlsw icanreach mac-exclusive and it once again works.
> >>
> >> OK, did I do this right? Is my logic correct?
> >>
> >> If you get stuck with this on your exam, you'd better be prepared to PROVE
> >> it to the proctor that this is the way it works.
> >>
> >>
> >> --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >> Barry J. Bocaner
> >> Sr. Network Engineer TruEdge Technologies
> >> <barry@truedge.com> 703-573-9884 x 103
> >> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
> >>
> >>
> >>
> >>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:34 GMT-3