[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference irocz::common_brouters

Title:	Digital Brouters Conference
Notice:	New common-code brouter family: RouteAbout, DECswitch 900
Moderator:	MARVIN::HARTLL

Created:	Mon Jul 17 1995
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	929
Total number of notes:	3736

827.0. "Multilink PPP on dialup ISDN for Access EI fails." by SNOFS2::JEYACHANDRAN () Wed Apr 02 1997 06:15

        Cust is trying to set up unnumbered IP for his ISDN interface 
 	with Multilink PPP on routeabout access EI. Cust is aware of 
	the three options for configuring multilink as per SPD.

        He is using V2.0 IP. He is not even getting the connection. 

        I have asked cust to check event logging monitor.

        1. Does dial up circuits in general require IP address on the 
	   interface? 
        
	2. What is the following S/W? I did not find any reference to 
	   the normal routeabout H/W. Is this used on some new H/W 	   
	   platform?

		PRODUCT NAME:  RouteAbout[TM] Access ISDN   SPD 56.55.00
               	Software V2.3a
        

	Thanks in advance.

        Daniel.

T.R	Title	User	Date	Lines
827.1	Config info & ELS messages.	SNOFS2::JEYACHANDRAN	`Thu Apr 03 1997 00:40`	248
	Some more info re. .0 with configuration details & the ELS messages. The ELS messages were generated by pinging to an address not within their local ethernet network The first ELS msg ISDN.023 does not have an ID. Is that the reason why the response from GW of the router with ELS msg GW.072? I have asked cust to delete the int 2 address 0.0.0.2 & do a trace again. Is there a sample config & trace I can refer to? Any ideas? Thanks in advance. Daniel. ============================================================================ IP PROTOCOL ======================================================================= IP config>list all Interface addresses IP addresses for each interface: intf 0 203.61.81.1 255.255.255.248 Network broadcast, fill 1 intf 1 IP disabled on this interface intf 2 0.0.0.2 0.0.0.0 Network broadcast, fill 1 intf 3 0.0.0.3 0.0.0.0 Network broadcast, fill 1 Router-ID: 203.61.81.1 Routing route to 0.0.0.0,0.0.0.0 via 0.0.0.3, cost 1 Protocols BOOTP forwarding: disabled Directed broadcasts: enabled ARP Subnet routing: disabled RFC925 routing: disabled OSPF: enabled Per-packet-multipath: disabled RIP: enabled RIP default origination: disabled Per-interface address flags: intf 0 203.61.81.1 Send net, subnet, static and default routes Received RIP packets are ignored. intf 1 IP & RIP are disabled on this interface intf 2 0.0.0.2 Send net, subnet, static and default routes Received RIP packets are ignored. intf 3 0.0.0.3 Send net, subnet, static and default routes Received RIP packets are ignored. Per-interface Triggered Rip values : Accept RIP updates always for: [NONE] EGP: disabled IP config> ======================================================================== = DIALER CONFIG ======================================================================== = Config>net 3 Circuit configuration Circuit Config>list all Base net: 2 Destination name: Access One Adelaide Outbound calls allowed Idle timer = 0 (fixed circuit) SelfTest Delay Timer = 150 ms Send Line ID: NO Circuit Config>enc PPP Multilink Protocol user configuration MP Config>list all LCP Parameters -------------- Config Request Tries: 20 Config Nak Tries: 10 Terminate Tries: 10 Retry Timer: 3000 LCP Options ----------- Max Receive Unit: 1500 Magic Number: Yes Authentication Protocol: CHAP PAP Parameters -------------- Authent Request Tries: 20 Retry Timer: 3000 Request Timer: 15000 PAP Ids/Passwords ----------------- Local ID: (None) Local Password: (None) Remote ID: (None) Remote Password: (None) CHAP Parameters -------------- Authent Request Tries: 20 Retry Timer: 3000 Request Timer: 15000 Repeat Authentication Timer: 0 CHAP Ids/Passwords ----------------- Local ID: ia043380 Local Password: xxxxxx Remote ID: aoneadl Remote Password: <same as local password> MP Options -------------- Base Links: 1 Max Links: 2 BoD threshold: 70 BoD sample time: 30 BoD base link line speed: 64000 BoD add link persistence: 5 BoD delete link persistence: 10 Default destination address name: Access One Adelaide NCP Parameters --------------- Config Request Tries: 20 Config Nak Tries: 10 Terminate Tries: 10 Retry Timer: 3000 IPCP Options ------------ IPCP Compression: None IP Address: Don't Send or Request CCP Options ----------- Data Compression disabled Algorithm: Stac-LZS Stac: histories 1 Stac: check_mode SEQ MP Config> Config>list isdn Address assigned name Network Address Network Subaddress --------------------- --------------- ------------------ Access One Adelaide 08-8203 2845 Cybergraphic Melbourne 03-9235-9500 Config> =========================================================== ELS Messages we are receiving ============================================================== ISDN.023: ConnID 0x0 Rxd N_STAT_IN ln 0 cause 0x4:0x30 nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 GW.070: LID tmo on id nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.033: Chn 1 ConnID 0x0 FSM st DataXfer ev DiscReq -> Clearing nt 2 int ISDN/ 0 ISDN.033: Chn 1 ConnID 0x0 FSM st Clearing ev DiscCnf -> Idle nt 2 int ISDN/0 ISDN.003: ConnID 0x70 Status msg cause (0x3:0xB) Start call alerting on nt 2 int ISDN/0 ISDN.033: Chn 1 ConnID 0x0 FSM st Idle ev ConnInd -> Call_Rxd nt 2 int ISDN/0 ISDN.033: Chn 1 ConnID 0x0 FSM st Call_Rxd ev StopAlert -> DataXfer nt 2 int ISD N/0 ISDN.023: ConnID 0x0 Rxd N_STAT_IN ln 0 cause 0x4:0x30 nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 PPP.018: LCP request retr exc nt 3 int MP/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 GW.070: LID tmo on id nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.033: Chn 1 ConnID 0x0 FSM st DataXfer ev DiscReq -> Clearing nt 2 int ISDN/ 0 ISDN.033: Chn 1 ConnID 0x0 FSM st Clearing ev DiscCnf -> Idle nt 2 int ISDN/0 ISDN.003: ConnID 0x44 Status msg cause (0x3:0xB) Start call alerting on nt 2 int ISDN/0 ISDN.033: Chn 1 ConnID 0x0 FSM st Idle ev ConnInd -> Call_Rxd nt 2 int ISDN/0 ISDN.033: Chn 1 ConnID 0x0 FSM st Call_Rxd ev StopAlert -> DataXfer nt 2 int ISD N/0 ISDN.023: ConnID 0x0 Rxd N_STAT_IN ln 0 cause 0x4:0x30 nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 IP.008: no rte 203.61.81.3 -> 203.5.40.139 dsc IP.008: no rte 203.61.81.3 -> 203.5.40.139 dsc IP.008: no rte 203.61.81.3 -> 203.5.40.139 dsc ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 IP.008: no rte 203.61.81.3 -> 203.5.40.139 dsc ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0 ISDN.021: Chn 1 ConnID 0x0 RxD Pkt ln 19 nt 2 int ISDN/0 GW.072: LID no dflt circt; data ign nt 2 int ISDN/0
827.2	easy answers first	MARVIN::CLEVELAND	`Thu Apr 03 1997 05:09`	11
	> 2. What is the following S/W? I did not find any reference to > the normal routeabout H/W. Is this used on some new H/W > platform? > > PRODUCT NAME: RouteAbout[TM] Access ISDN SPD 56.55.00 > Software V2.3a That's the newest member of the RouteAbout family (sort of a second cousin, really). It's a rebadged Proteon Globetrotter.
827.3		MARVIN::CLEVELAND	`Thu Apr 03 1997 05:41`	16
	Assuming this is really a RouteAbout Access EI ... There should be no IP address at all on net 2. In fact, I wonder how you got it there -- usually IP refuses to allow this! No problem using the 0.0.0.3 address on the dial circuit however. It looks like you've posted the configuration of the caller, and a trace from the answerer -- is that right? I'd need to see the answerer's configuration to debug this. From the trace, it appears you do not have Calling Line ID. That means the answering dial circuit will need to be set to ANY_INBOUND ('set calls any'), since you have also disabled outbound Line ID on the caller. You might want to try that as a first test.
827.4	"delete address 0.0.0.2" improved status.	SNOFS2::JEYACHANDRAN	`Thu Apr 03 1997 21:11`	36
	>> Assuming this is really a RouteAbout Access EI ... It is. >> There should be no IP address at all on net 2. In fact, I wonder how >> you got it there -- usually IP refuses to allow this! I don't know how cust managed to get it. After deleting address 0.0.0.2 the trace seemed to get the ISDN connection OK, but failed in PPP negitiation. I think he has set up unnumbered interface assuming it will just work fine irrespective of how the WAN link is configured. I am asking cust to set up the interface IP exactly as per the Service Provider's WAN interface - with correct subnet address if it has an IP address. >> It looks like you've posted the configuration of the caller, and a >> trace from the answerer -- is that right? I'd need to see the >> answerer's configuration to debug this. I did post the config & Trace of the caller, when cust did the ping from a PC on the local ethernet to another node on the other side of WAN. >> ... since you have also disabled outbound Line ID on the caller. In fact "outbound call = allowed". Have I missed anything? Thanks for your replies. Daniel.
827.5		MARVIN::CLEVELAND	`Fri Apr 04 1997 05:21`	9
	Hmm, I didn't understand your configuration. What type of box is the customer calling? Not a routeabout, I presume? I don't know why removing the address would have helped, but I'm not complaining ;-). Most likely, the line should be set up just like the other end, with a compatible address and mask. If you now have a PPP problem you can use DTF to trace the connection. It should tell you what is going wrong...
827.6	WAN i/f serial IP address & mask.	SNOFS2::JEYACHANDRAN	`Tue Apr 08 1997 01:15`	15
	>> Hmm, I didn't understand your configuration. What type of box is the >> customer calling? Not a routeabout, I presume? A cisco router. >> I don't know why removing the address would have helped, but I'm not >> complaining ;-). Most likely, the line should be set up just like the >> other end, with a compatible address and mask. The problem was precisely the WAN serial I/F address & mask which cust assumed would work with his end with unnumbered IP. Thanks for the help. Daniel.