Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CMS R13 Modem

Status
Not open for further replies.

Avayatech713

IS-IT--Management
Aug 23, 2007
81
US
Looking for ideas on why I can't dial into our new CMS server (Sun netra 2100) - remotely thru ASA.

Running R3-V13 CMS software - just did a fresh install of the CMS software - install went perfect.

The factory supplied DB9 connector are installed correctly on the Netra and the DB25 connector on the Sportster 33.6 and the factory CAT5 cable is connected to the DB9 & DB25.

ASA software settings are exactly what I use to dial remote to all our switches & VMs - 8-N-1 Hardware - Emulation 4425 (from my IBM Notebook) and I have tried the analog modem setting - generic 1200/2400/9600 - generic 9600 etc and while the modem answers and handshakes every time - and the ASA terminal Emulation screen opens up when connected - I cannot get a Login.

This is driving me crazy. Should be simple. I have tried (4) different Sportster 33.6 modems - same result.

I put an RS-232 tester on the DB25 connector from the CMS - no connecttion to the Sprotser yet - got green LED on TD & Red on RTS & DTR. When I connected the tester w/ the DB25 to the Sportser and turned it on - Green was TD-CD-RD & Red was RTS-DSR-CTS-DTR. When I dialed into the CMS - and got a successful handshake - the TD & RD were green and other LEDs were red .... but no data shows on the ASA terminal screen?

Very strange. I'm guessing it is something simple so any help or tips would be helpful.
 
If the modem is answering but no login prompt

run ps -ef | grep tty.

go into the install and maintenance manual and look for how to install/uninstall the modem. Run the uninstall then the install.

run ps -ef | grep tty and you should see the new process. This will provide the login to the modem port.
 
Here is the problem in detail I am getting with trying to setup the modem for remote console connectivity via ASA.

Page 34 of the CMS Install manual shows - after setting the DIP switches to 1-3-7-8 down on the 33.6 Sportster - run this command line.

/cms/install/bin/abcadm -r ttyb

Running this command returned the correct message "ttyb is currently set to be incoming - are you sure you want to change it Y/N?"

Selected Y and the message was returned "TTYB admin removed"

The 2nd command to run is ...

cu -s 9600 -b 8 -1 cua/b (typed it exactly as in the manual)

This command is supposed to return the message "connected" and then your run the modem setup commands ... AT AT&F1 AT&W0

The problem is when I run the CU line command I get the following syntax message error

cu [-dhtnlc] [-c device] [-s speed] [-1 line] [-b 718] [-0 | -E] telno | systemname [local-cmd]

Looks like Unix is looking for additional parameters in the "cu -s 9600 -b 8 -1 cua/b" command line ... but I'm not sure what to add to run it correctly. I tried some possible add-ins but nothing works.

Any ideas from some of the CMS techs?

Also - have the ASA properties for this dial-in connection set to 9600-8-N-1-hardware and the modem type set to 9600 Generic w/ terminal Emulation as 4425.

 
Have you tried "tip hardwire" to get to modem for AT commands. Are you using usb modem or serial port?


Chapter 7 Using USB Devices (Overview)
This chapter provides an overview of Universal Serial Bus (USB) devices in the
Solaris OS.
For recent information about USB devices, go to the following site:


For general information about USB devices, go to the following site:


For step-by-step instructions on using USB devices in the Solaris OS, see
Chapter 8, Using USB Devices (Tasks).

For general information about dynamic reconfiguration and hot-plugging, see
Chapter 6, Dynamically Configuring Devices (Tasks).


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
# for tip hardwire default serial port change a: to b:
# as shown below in /etc/remote serial port "a" (rs232) is
# setup for connecting to modem

drsun [403885]-> vi /etc/remote
hardwire:\
:dv=/dev/term/a:br#9600:el=^C^S^Q^U^D:ie=%$:eek:e=^D:

drsun [608885]-> tip hardwire
connected

at&v

ACTIVE PROFILE:
B1 E1 L2 M1 Q0 T V1 X1 Y1 &C1 &D2 &G0 &M0 &P0 &R1 &S0 &T4 &X0 &Y0
%A013 %B28800 %C1 %M0 \A3 \C0 \D0 \E0 \G0 \J0 \K5 \N7 \Q3 \T000 \X0
S00:001 S02:255 S03:013 S04:010 S05:008 S06:002 S07:045 S08:002 S09:006
S10:014 S11:095 S12:255 S18:000 S25:000 S26:001 S76:0 S78:0

STORED PROFILE 0:
B1 E1 L2 M1 Q0 T V1 X4 Y1 &C1 &D2 &G0 &M0 &P0 &R1 &S0 &T4 &X0
%A013 %B28800 %C1 %M0 \A3 \C0 \D0 \E0 \G0 \J0 \K5 \N7 \Q3 \T000 \X0
S00:001 S02:043 S06:002 S07:045 S08:002 S09:006
S10:014 S12:050 S25:000 S26:001 S76:0 S78:0

STORED PROFILE 1:
B1 E1 L2 M1 Q0 T V1 X4 Y1 &C1 &D2 &G0 &M0 &P0 &R1 &S0 &T4 &X0
%A013 %B28800 %C1 %M0 \A3 \C0 \D0 \E0 \G0 \J0 \K5 \N7 \Q3 \T000 \X0
S00:001 S02:043 S06:002 S07:045 S08:002 S09:006
S10:014 S12:050 S25:000 S26:001 S76:0 S78:0

TELEPHONE NUMBERS:
&Z0=
&Z1=

OK

# from another window, use pkill -x tip to drop "tip hardwire"

drsun [11397]-> pkill -x tip


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
Code:
cu -s 9600 -b 8 -1 cua/b   (typed it exactly as in the manual)

change the -1 to -l (for line)

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
Code:
drsun [608905]-> cu -d -1 cua/a -s9600            
cu: illegal option -- 1
Usage: cu [-dhtnLC] [-c device] [-s speed] [-l line] [-b 7|8]
        [-o | -e] telno | systemname [local-cmd]
drsun [608906]-> cu -d -l cua/a -s9600
altconn called
Device Type Direct wanted
Trying device entry 'cua/a' from '/etc/uucp/Devices'.
processdev: calling setdevcfg(cu, Direct)
fd_mklock: ok
fixline(6, 9600)
gdial(direct) called
Trying caller script 'direct' from '/etc/uucp/Dialers'.
getto ret 6
device status for fd=6
F_GETFL=2,iflag=`12045',oflag=`0',cflag=`2655',lflag=`0',line=`0'
cc[0]=`3',[1]=`34',[2]=`177',[3]=`25',[4]=`1',[5]=`0',[6]=`0',[7]=`0',
call _mode(1)
Connected
transmit started
_receive started
at
OK

~[drsun].
call tilda(.)
call _quit(0)
call _bye(0)

Disconnected
call cleanup(0)
call _mode(0)
drsun [608907]->

~. is to drop the connection


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

35 years Bell, AT&T, Lucent, Avaya
Tier 3 for 25 years and counting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top