From: Saleem Rahman (srahman@xxxxxxxxxx)
Date: Thu May 25 2000 - 10:45:14 GMT-3
Thanks to all for their valuable feedback.
Lee, i got it working It was bit tricky and by just introducing the command
"x25 nvc 2 " it started to work.
Joe Martin, The BRI part had the same concept and i somehow manage to
work it out.
Here is the configuration to benefit all:
-R1=====R3-
----------------------------------------------------------------------------
--------
1:
interface Serial1/0
ip address 212.1.34.65 255.255.255.240
encapsulation x25 dce
no ip mroute-cache
x25 address 2222
x25 nvc 2
x25 map ip 212.1.34.65 1111 broadcast
x25 map ip 212.1.34.66 1111 broadcast
clockrate 64000
interface BRI0/0
ip address 1.1.1.2 255.255.255.0
encapsulation ppp
dialer map ip 1.1.1.1 name R3 broadcast 384020
dialer map ip 1.1.1.2 name R3 broadcast 384020
dialer-group 1
isdn switch-type basic-net3
hold-queue 75 in
R3:
interface Serial1/0
ip address 212.1.34.66 255.255.255.240
encapsulation x25
no ip mroute-cache
x25 address 1111
x25 nvc 2
x25 map ip 212.1.34.66 2222 broadcast
x25 map ip 212.1.34.65 2222 broadcast
interface BRI0/0
ip address 1.1.1.1 255.255.255.0
encapsulation ppp
dialer map ip 1.1.1.1 name R1 broadcast 384000
dialer map ip 1.1.1.2 name R1 broadcast 384000
dialer-group 1
isdn switch-type basic-net3
hold-queue 75 in
----------------------------------------------------------------------------
----------------
Best Regards,
Saleem
MSCE,CNE,CCNA,CCNP,CCDA
-----Original Message-----
From: Lee, Vaughan [mailto:vaughan.lee@debis.co.uk]
Sent: Thursday, May 25, 2000 11:43 AM
To: 'ccielab@groupstudy.com'
Subject: RE: Couple of Questions
I sent an answer to Joe directly about the X.25 part of this question as
I've already put this on the list in the past, but as it's clear others need
it again, here's a copy.
I'm not sure about the BRI, but to get the X.25 to ping itself, add the
route back to yourself (x25 map ip etc...), and also add 'x25 nvc 2' to the
X.25 interface at each end of the circuit.
By default, x.25 will only allow 1 virtual circuit between each pair of
hosts per protocol. As the ping over X.25 requires one virtual circuit to
send the ping out on, and a second to 'loop' the ping back, the default
settings won't work. Adding the nvc 2 parameter allows you to increase the
Number of Virtual Circuits to 2 (you can increase this up to 9), so allowing
the ping to work.
Vaughan Lee, Network Specialist.
CCIE #5250
debis IT Services (UK) Ltd.
E-mail: vaughan.lee@debis.co.uk
Direct Phone: 01908 279561
Direct Fax: 01908 279061
-----Original Message-----
From: Saleem Rahman [mailto:srahman@lucent.com]
Sent: 24 May 2000 22:05
To: ccielab@groupstudy.com
Cc: Joe Martin
Subject: RE: Couple of Questions
All,
Any feedback on the below first question i.e. "How to ping X25 and Bri own
interface".
I tried simulating the scenario as Martin mention it does work with FR but
couldn't make it run with X25 & BRI.
Its strange any idea, feedback, solutions will be greatly appreciated.
Regards,
Saleem
MCSE, CNE, CCNA,CCNP,CCDA.
-----Original Message-----
From: Joe Martin [mailto:jmartin@gte.net]
Sent: Tuesday, May 23, 2000 4:48 AM
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:31 GMT-3