From: hiler john (o_hiler@xxxxxxxxx)
Date: Mon May 21 2001 - 04:29:27 GMT-3
'show dlsw rechbility' seems like, but there isn't any
mask information. So it let me a little puzzled. for
example:
the fisrt condition:
r1 and r2 are peers. there is one host 2222.2222.0 on
the r2 side. in order to control explore frame. we
have two way:
"dlsw mac-addr 2222.2222.0 remo ip-a 2.2.2.2" on r1
or "dlsw icanreach mac-add 2222.2222.0 mask
ffff.ffff.ffff" on r2(by the way, the cisco already
corrected their misktake aboute mask, you can check it
on cco)
the second condition:
there are some hosts 2222.2222.x on the r2 side. So we
only have one way? right?
"dlsw icanreach mac-add 2222.2222.0 mask
ffff.ffff.0000" on r2 side.
but all three commands got the same "show dlsw
reachbility" .of course, they got different "show dlsw
capability". when using "dlsw mac-addr",there isn't
any mask information(there shouldn't).
because their have the same reachbility table. so how
the dlsw know which macs the remote-peer can reach in
our conditions? for example, when one user on r1 side
want to find 2222.2222.0. In conditon one or two, r1
know the r2 can reach. but if the user want to find
2222.2222.1. In first condition, the r1 don't know
which peer can reach, but in second condition, r1 know
r2 can reach. So I think there are really some tables
just like ip routing table store all information,
include masks. reachbility table is not such table,
the capability table still not enough. So can someone
tell me how the dlsw handle such things?
thanks
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:47 GMT-3