From: Earl Aboytes (earl@xxxxxxxxxxxx)
Date: Tue May 23 2000 - 02:31:04 GMT-3
In your dlsw config they might be looking for a dlsw icannotreach saps 04
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Earl Aboytes
Senior Technical Conultant
GTE Managed Solutions
805-381-8817
earl.aboytes@telops.gte.com
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of Joe
Martin
Sent: Monday, May 22, 2000 6:48 PM
To: ccielab@groupstudy.com
Subject: Couple of Questions
Hi all,
I just worked on a lab that said I must be able to ping all addresses,
including my own. With certain types of interfaces it requires a bit of
configuration. For example to ping your own interface on a physical or
multipoint subinterface for frame relay you must add a frame-relay map
statement referencing your own IP and the DLCI being used. How do you make
this work for X.25 and BRI? I tried the same method using X.25 MAP IP local
ip address 1111 br and DIALER MAP IP local ip address 5551212 and it didn't
work. Any thoughts?
Also, I'm having a bit of trouble with DLSW filtering. I understand the
0x0404 0x0d0d for SNA and 0xf0f0 0x0101 for Netbios, and I think I
understand placing LSAP filters on the DLSW remote peer statement, but the
lab I'm working on says to confirm that filtering is functioning by doing a
SHOW DLSW CAPABILITIES on the remote routers. Nothing shows that I'm
blocking anything. Should I be able to see anything? Am I doing it
correctly? I do know how to set up ICANREACH exclusives for MAC-ADDRESSES
and NETBIOS so that it shows in the remote capabilities.
Sample:
DLSW LOCAL PEER 192.168.1.1
DLSW REMOTE 0 TCP 192.168.2.1 LSAP-OUTPUT-LIST 200
ACCESS-LIST 200 PERMIT 0X0404 0X0D0D
Should this be enough to allow only SNA to be sent to the remote peer?
Your assistance is greatly appreciated,
JOE
CCIE Lab Date - MAY 27/28
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:23:30 GMT-3