[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

904.0. "RouteAbout 90EW/IP V2.0-3 V25bis problem" by GIDDAY::LEUNG () Mon May 19 1997 04:30

RouteAbout Access 90EW/IP V2.0-3
US Robotics Courier V34 Fax Modem (V25bis modem)

The same modem work fine with Decbrouter. Customer trying to get it to work 
with RouteAbout but cannot get the modem to dial.
Customer has fixed the following signals on the modem with :
at&c0	CD on
at&r1	cts always on
at&s0	dsr on

Thanks
Dennis

Config>list v25

Address assigned name             Network Address
---------------------             ---------------
sydney                            96666481
thailand                          93168181
Config>list devices
Ifc 0 (Ethernet): CSR 1001600, CSR2 1000C00, vector 94
Ifc 1 (WAN V.25bis): CSR 1001620, CSR2 1000D00, vector 93
Ifc 2 (WAN PPP): CSR 1001640, CSR2 1000E00, vector 92
Ifc 3 (PPP Dial Circuit): CSR      0, vector 0

V.25bis Config> list all
         V.25bis Configuration
Local Network Address Name    = sydney
Local Network Address         = 96666481

Non-Responding addresses:
Retries             = 1
Timeout             = 0 seconds

Call timeouts:
Command Delay       = 0 ms
Connect             = 60 seconds
Disconnect          = 2 seconds

Circuit Config>list all

Base net:       1
Destination name:    thailand
Outbound calls       allowed
Inbound calls        allowed
Idle timer           = 60 sec
SelfTest Delay Timer = 150 ms
Send/Rcv Line ID:    NONE


IP config>list all
Interface addresses
IP addresses for each interface:
   intf  0   203.3.169.249    255.255.255.0    Network broadcast,    fill 1
             203.3.173.253    255.255.255.0    Network broadcast,    fill 1
   intf  1                                     IP disabled on this interface
   intf  2                                     IP disabled on this interface
   intf  3   192.168.200.249  255.255.255.252  Network broadcast,    fill 1

Routing

route to 200.0.0.0,255.255.255.0 via 192.168.200.250, cost 1



Protocols
BOOTP forwarding: disabled
Directed broadcasts: enabled
ARP Subnet routing: disabled
RFC925 routing: disabled
OSPF: disabled
Per-packet-multipath: disabled
RIP: disabled
EGP: disabled

V.25bis> stat
         V.25bis port Statistics

  Adapter cable:             RS-232 DTE  RISC Microcode Revision:            0

   V.24 circuit: 105 106 107 108 109 125 141
   Nicknames:    RTS CTS DSR DTR DCD RI  LL
   RS-232:       CA  CB  CC  CD  CF  CE
   State:        OFF ON  ON  OFF ON  OFF OFF

  Line speed:              unknown
  Last port reset:         2 minutes, 40 seconds ago

  Input frame errors:
   CRC error                          0   alignment (byte length)            0
   missed frame                       0   too long (>  2182 bytes)           0
   aborted frame                      3   DMA/FIFO overrun                   0
   L & F bits not set                 0
  Output frame counters:
   DMA/FIFO underrun errors           0   Output aborts sent                 0


+config

RtAbt Acces EW/IP,  Brouter: 1 Enet 2T1,HW=1,RO=1,#1216,SW=V2.0-3
Hostname: [not configured]
Boot ROM version  1.0      Watchdog timer enabled     Auto-boot switch enabled
Console baud rate: 9600

Num Name  Protocol
0   IP    DOD-IP
3   ARP   Address Resolution
11  SNMP  Simple Network Management Protocol

Num Name  Feature
2   MCF   MAC Filtering

4 Networks:
Net Interface  MAC/Data-Link         Hardware                       State
0   Eth/0      Ethernet/IEEE 802.3   SCC Ethernet                   Up
1   V25/0      V.25bis Base Net      SCC Serial Line                Up
2   PPP/0      Point to Point        SCC Serial Line                Down
3   PPP/1      Point to Point        V.25bis Dial Circuit           Up

Events when ping to remote site, modem does not dial and customer terminated
the ping :
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_XMT nt 3 int PPP/1
V25B.021: Set DSS DTR (Off -> On)  nt 1 int V25/0
V25B.025: Clnt CR 93168181 nt 1 int V25/0
  GW.043: CML state CML_CONNECTING, event CML_XMT nt 3 int PPP/1
  GW.043: CML state CML_CONNECTING, event CML_XMT nt 3 int PPP/1
  GW.043: CML state CML_CONNECTING, event CML_MNT nt 3 int PPP/1
  .
  .
  .
  GW.043: CML state CML_CONNECTING, event CML_XMT nt 3 int PPP/1
  GW.043: CML state CML_CONNECTING, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_CONNECTING, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_CONNECTING, event CML_XMT nt 3 int PPP/1
  GW.043: CML state CML_CONNECTING, event CML_MNT nt 3 int PPP/1
V25B.008: Dead DCE nt 1 int V25/0 
V25B.021: Set DSS DTR (On -> Off) RTS (Off -> Off)  nt 1 int V25/0
  GW.043: CML state CML_CONNECTING, event CML_DIND nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
V25B.021: Set DSS DTR (Off -> Off) RTS (Off -> Off)  nt 1 int V25/0
  SL.007: st slftst nt 1 int V25/0
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
V25B.023: Slftst OK nt 1 int V25/0
V25B.021: Set DSS DTR (On -> Off) RTS (Off -> Off)  nt 1 int V25/0
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1


Tried again and fails with a different message saying that call is blocked 
because interface 1 is already in use!!! If we power off and power on
the modem while the ping is still running, the modem will then dial.
But if we terminate the ping and power off/on the modem, then start
the ping again, the call is again in blckd state. See last ELS trace
below for that case.
  SL.007: st slftst nt 2 int PPP/0
  SL.021: slf tst fl bcs of mdm sts, CTS = OFF, DSR = OFF, DCD = OFF, nt 2 int 0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.007: Mdm Chg 0xE -> 0xA (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.007: Mdm Chg 0xA -> 0x8 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.007: Mdm Chg 0x8 -> 0x0 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.006: FSM st 7: Clearing ev DSS change -> st 1: Idle nt 1 int V25/0
V25B.021: Set DSS DTR (Off -> On)  nt 1 int V25/0
V25B.025: Clnt CR 93168181 nt 1 int V25/0
V25B.007: Mdm Chg 0x0 -> 0x4 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.024: Tx CRN 93168181 nt 1 int V25/0
V25B.006: FSM st 2: DTE_Ready ev DSS change -> st 3+4: DCE_Dial nt 1 int V25/0
V25B.007: Mdm Chg 0x4 -> 0x6 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.007: Mdm Chg 0x6 -> 0x4 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.007: Mdm Chg 0x4 -> 0xC (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.007: Mdm Chg 0xC -> 0x8 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.006: FSM st 3+4: DCE_Dial ev DSS change -> st 5: Answered nt 1 int V25/0
V25B.007: Mdm Chg 0x8 -> 0x0 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.007: Mdm Chg 0x0 -> 0x4 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.007: Mdm Chg 0x4 -> 0x6 (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.007: Mdm Chg 0x6 -> 0xE (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.027: Out Call 93168181 cmp T=5.283 nt 1 int V25/0
V25B.006: FSM st 5: Answered ev DSS change -> st 6+12: Connected nt 1 int V25/0
V25B.021: Set DSS RTS (Off -> On)  nt 1 int V25/0
V25B.007: Mdm Chg 0xE -> 0xA (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.009: RxD Pkt ln 5 nt 1 int V25/0
V25B.017: Indctn "VAL" st 6+12: Connected nt 1 int V25/0
V25B.007: Mdm Chg 0xA -> 0xE (DSR/CTS/CD/CI) nt 1 int V25/0
V25B.009: RxD Pkt ln 7 nt 1 int V25/0
V25B.016: CFI Ind rsn "Engaged Tone" st 6+12: Connected nt 1 int V25/0
V25B.006: FSM st 6+12: Connected ev CFI -> st 7: Clearing nt 1 int V25/0
V25B.021: Set DSS DTR (On -> Off) RTS (On -> Off)  nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
V25B.006: FSM st 7: Clearing ev Timeout -> st 1: Idle nt 1 int V25/0
V25B.021: Set DSS DTR (Off -> On)  nt 1 int V25/0
V25B.025: Clnt CR 93168181 nt 1 int V25/0


Events saying call blckd when trying to ping :
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_XMT nt 3 int PPP/1
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
  GW.043: CML state CML_CONNECTING, event CML_DIND nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_MNT nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_XMT nt 3 int PPP/1
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
  GW.043: CML state CML_CONNECTING, event CML_DIND nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_XMT nt 3 int PPP/1
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
  GW.043: CML state CML_CONNECTING, event CML_DIND nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_XMT nt 3 int PPP/1
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0
  GW.043: CML state CML_CONNECTING, event CML_DIND nt 3 int PPP/1
  GW.043: CML state CML_AVAILABLE, event CML_XMT nt 3 int PPP/1
V25B.026: Clnt CR blckd 93168181 nt 1 int V25/0

T.R	Title	User	Personal Name	Date	Lines
904.1	try these settings	MARVIN::CROWLE	Seek not answers; live the questions	`Mon May 19 1997 05:55`	31
	Dennis, I think you need different modem settings. Try: at&c1 DCD normal at&r0 CTS tracks rts at&s1 DSR normal "Call blocked" happens when the router can't get the response it wants from the modem control signals, so it looks very much like this is your problem. Check also you've got at&d6 DTR 108.2 setting but I think this must be ok or you wouldn't have got as far as you have into the dialup sequence. In note 840.4 I recommended the setting you have used, but only for test purposes. From your events listings it looks like the router is seeing the modem signals, so that side of it should be fine. Of course, you've also got in your listings: > V25B.016: CFI Ind rsn "Engaged Tone" st 6+12: Connected nt 1 int V25/0 Could this be a problem too ;-) ? Brian
904.2		IAMOSI::LEUNG		`Tue May 27 1997 04:22`	81
	RE: .1 Brian, Sorry for the late reply. I now have the customer's modem and it does seem to not work with RouteAbout90EW. I have tried the same modem with a DECBrouter with the same settings on the modem and it works, i could hear the modem start dialing the remote end. Modem : Robotics Courier Dual Standard V.34 Fax with V.32bis The following settings have been set on the modem : at&c1 at&r0 at&s1 Also, using HDLC framing in synchronous mode. Interface signals after powering up the modem : +net 1 V.25bis Console V.25bis> stat V.25bis port Statistics Adapter cable: RS-232 DTE RISC Microcode Revision: 0 V.24 circuit: 105 106 107 108 109 125 141 Nicknames: RTS CTS DSR DTR DCD RI LL RS-232: CA CB CC CD CF CE State: OFF ON OFF OFF OFF OFF OFF Line speed: unknown Last port reset: 6 minutes, 49 seconds ago Input frame errors: CRC error 0 alignment (byte length) 2 missed frame 0 too long (> 2182 bytes) 0 aborted frame 3 DMA/FIFO overrun 0 L & F bits not set 0 Output frame counters: DMA/FIFO underrun errors 0 Output aborts sent 0 On the modem itself, the following LEDS are on : Auto-answer, Receive Data, Send Data, Modem Ready, CTS and Synchronous Mode A) When I ping the remote ip address of the link, DTR LED came up on the modem but the modem does NOT dial at all. Here are the ELS events : *t 2 17:02:48 V25B.021: Set DSS DTR (Off -> On) nt 1 int V25/0 17:02:48 V25B.025: Clnt CR 7247 nt 1 int V25/0 17:03:48 V25B.008: Dead DCE nt 1 int V25/0 17:03:48 V25B.021: Set DSS DTR (On -> Off) RTS (Off -> Off) nt 1 int V25/0 17:03:53 V25B.021: Set DSS DTR (Off -> Off) RTS (Off -> Off) nt 1 int V25/0 17:03:53 SL.007: st slftst nt 1 int V25/0 17:03:55 V25B.023: Slftst OK nt 1 int V25/0 17:03:55 V25B.021: Set DSS DTR (On -> Off) RTS (Off -> Off) nt 1 int V25/0 After about 1 minute, DTR is deasserted by the RouteAbout and the DTR LED on the modem goes off. B) If I redo the ping again, DTR is not asserted by the RouteAbout; DTR LED on modem stays off and the ELS events are : t 2 17:07:05 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:06 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:08 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:09 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:10 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:11 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:12 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:13 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:14 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 17:07:15 V25B.026: Clnt CR blckd 7247 nt 1 int V25/0 If I power off the modem and power it back on, then I get the same events as in A above with DTR getting asserted by the routeabout. Observations with DecBrouter : DTR LED is always being asserted by Brouter. I can ping several times and the modem will start dialing the remote site without having to power off/on the modem. Dennis
904.3	Could be a interoperability problem with these particular modems	MARVIN::CROWLE	Seek not answers; live the questions	`Tue May 27 1997 08:25`	22
	Dennis, It looks to me as if the modem is asserting CTS all the time. Could you verify this please? By setting at&r0, you should have set CTS to follow RTS. So you stats line looks very suspect, with RTS off and CTS on: V.24 circuit: 105 106 107 108 109 125 141 Nicknames: RTS CTS DSR DTR DCD RI LL RS-232: CA CB CC CD CF CE State: OFF ON OFF OFF OFF OFF OFF ^ ^ Bear in mind that we have a very exact implemetation of V.25 bis - perhaps too exact! - and that other implementations may be a bit more relaxed about how they treat modem control signals. With CTS on all the time, the 90EW won't interwork with the modem. I have a feeling that US Robotics modems have been flagged as problem ones for us in the past. Brian
904.4		IAMOSI::LEUNG		`Tue May 27 1997 21:49`	13
	Brian, Thanks for the reply. > It looks to me as if the modem is asserting CTS all the time. Could > you verify this please? By setting at&r0, you should have set CTS to > follow RTS. So you stats line looks very suspect, with RTS off and CTS > on: You are right. The modem is asserted CTS all the time (CTS LED is ON) even though at&r0 has been done and RTS is not being asserted by the RouteAbout (RTS LED on modem is off). I will inform customer. Dennis