From: carnold_@onebox.com
Date: Fri Dec 06 2002 - 20:39:52 GMT-3
Hello,
The only one that has an implicit deny all at the end is the statement for Saps:
r1(config)#dlsw icanreach saps ?
<0-FE> Even SAP Value (hex)
Arnold C.
-- Arnold Connell carnold_@onebox.com - email (877)866-3490 voicemail/fax-----Original Message----- From: Sam.MicroGate@usa.telekom.de Sent: Fri, 6 Dec 2002 17:04:07 -0500 To: ybae@cisco.com; ccielab@groupstudy.com Subject: RE: ICANREACH Mac-Exclusive
Hello,
1- The mac-exclusive has nothing to do with the deny statement at the end. It is just telling the remote peer do not send me any explorer packet for any other mac address. All I know is mac address 4000.3745.0000. Nothing else.
2- True you have to change the mac add from its canonical to non-canonical format.
Sam
-----Original Message----- From: Young K. Bae [mailto:ybae@cisco.com] Sent: Friday, December 06, 2002 4:29 PM To: ccielab@groupstudy.com Subject: ICANREACH Mac-Exclusive
A quick sanity check on the ICANREACH statement:
dlsw icanreach mac-exclusive dlsw icanreach mac-address 4000.3745.0000 mask ffff.ffff.ffff
1. According to the documentation, there is an 'implicit deny-all' within the ICANREACH <mac-address> statement. If that's true, why would one need to configure 'dlsw icanreach mac-exclusive'?
2. Considering above configuration, if the device (MAC 4000.3745.0000) resides on an Ethernet segment, the true MAC address of the device is 0200.ECA2.0000, correct?
TIA, . .
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:40 GMT-3