Sponsored Content
Top Forums UNIX for Dummies Questions & Answers console access via serial port - settings Post 2918 by simplimarvelous on Saturday 9th of June 2001 08:29:35 PM
Old 06-09-2001
thanks neo, so will a straight thru cable work in the back to back situation?
 

9 More Discussions You Might Find Interesting

1. AIX

Installing via serial console

I'm stuck - when I boot the machine and hit 5 on the keyboard, all I get is an SP login. Can someone give me some tips on how to get to the install via the serial port? (2 Replies)
Discussion started by: tb0ne
2 Replies

2. AIX

cant telnet to aix 5.2 and not even access through serial console

I have installed aix 5.2 on aix box through serial console connected to COM 1 . I even get a login prompt after the fresh installation . But as soon as i give a root & enter i again get a login prompt.i..e I am not able to logon after a fresh installation. and even i configured IP configuration... (0 Replies)
Discussion started by: linuxnightowl84
0 Replies

3. HP-UX

serial console hangs

I have a HP Visualize C200 running hpux that I am trying to boot into using a null modem through com1 from my Sun Ultra 10. I get all the way to the login prompt and then it becomes innactive and wont let me access the machine anymore. Any ideas? (2 Replies)
Discussion started by: trajek
2 Replies

4. Solaris

Sun Fire V890 - Unable to access RSC or Serial console

Hello Folks, I am having trouble to login to rsc or serial console of V890. The rsc2.2.3 has been configured with required parameters, resetrs and even rebooted. When serial port is connected to laptop, The hyper terminal does not get the console or POSt messages when the server is rebooting... (8 Replies)
Discussion started by: defflepord
8 Replies

5. Solaris

Unable to access serial port from non-global solaris zone on netra 240

I am trying to use a serial communications device that is connected to /dev/ttyb on a netra 240 server. This is a solaris zone configuration using solaris 10 0910. I am able to access /dev/ttyb from the global zone but not throught he non-global zone. I have enabled all of the tty devices in my... (0 Replies)
Discussion started by: disagreeable
0 Replies

6. UNIX for Dummies Questions & Answers

IP Console Vs Serial console.

Hi Gurus, Can some one explain me the difference between a IP console and a serial console. (1 Reply)
Discussion started by: rama krishna
1 Replies

7. Solaris

How to enable Serial port on ILOM, when Network Port is enabled in parallel

Hi Everyone, In my environment, I have few T5220. On the iLOM Management Card, I have both Network and Serial port are cabled, I don't have any issues while I try to connect using Network Management port, but when I try to connect the serial port for the same server which is actually connected... (3 Replies)
Discussion started by: bobby320
3 Replies

8. Solaris

How to setup a serial console?

i am running solaris 10 in my vmware workstation. How to setup a console for my solaris box. in Vmware i could see a serial port option. can some one help me on how i can setup a console . (0 Replies)
Discussion started by: chidori
0 Replies

9. Solaris

Cabling and adapters to communicate to service processor serial port from Windows PC with USB port.

Hello, I have an unloaded T5140 machine and want to access the ILOM for the first time and subsequently the network port after that., and then load Solaris 10 the final January 2011 build. The first part is what confuses me -the cabling. I am coming from a Windows machine (w/appropriate... (5 Replies)
Discussion started by: joboy
5 Replies
modem(7)						 Miscellaneous Information Manual						  modem(7)

NAME
modem - Describes guidelines for using modems DESCRIPTION
The Tru64 UNIX system enables you to use a variety of modems for point-to-point connections to systems that are not in close proximity to each other. These connections can be Serial Line Internet Protocol (SLIP), Point-to-Point Protocol (PPP), and UNIX-to-UNIX Copy Program (UUCP) connections. In addition, these connections can be basic dial-out/dial-in connections (for example, to log in to a remote system to perform remote system administration). This section presents general guidelines for using modems on Tru64 UNIX systems for all types of connections. See Network Administration for specific information on SLIP, PPP, and UUCP connections. Using the Correct Modem Cables In order to connect a modem to the serial port of your system, you must use the correct cable. If you do not, you might experience signal loss, resulting in the software not functioning properly. The following table lists the cables you should use. The cable connector is either 25-pin or 9-pin, depending on the type of serial port on your system. See the hardware documentation for your system if you are unsure about the type of serial port. Note OPEN DECconnect cables do not provide a sufficient number of wires for full modem control. You should not use them for connecting modems to the system. ------------------------------------------------------------------------------ Cable Number Description ------------------------------------------------------------------------------ BC22E-xx 16-wire modem cable (Male DB25 pin to female DB25 pin cable) BC22F-xx 25-wire modem cable (Male DB25 pin to female DB25 pin cable) BC29P-xx Male DB25 pin to female DB9 pin cable PC modem cable Male DB25 pin to female DB9 pin cable In the previous table, xx denotes the cable length. For example, BC22E-10 is a ten-foot cable. Configuring a System for Dial-In Access After you have obtained the correct cable and connected your modem to it and the telephone network, do the following: Edit the /etc/remote file and create an entry similar to the kdebug entry. For example, if your modem is connected to tty00 and you are going to use a baud rate of 38400 to access the modem, create an entry similar to the following: b38400:dv=/dev/tty00:br#38400:pa=none Note Some modems set their baud rate to the serial port rate. Be sure to access the modem using the same baud rate that you are going to specify to getty or uugetty. Otherwise, you might not be able to log in because of a mismatch in baud rates. See ports(7) if you are unsure which port your modem is connected to. Use the tip command to access the modem as follows: tip b38400 The tip utility responds with a connected message. You can now communicate with the modem. If your modem is using the AT command language, enter the following command: at<Return> If the modem is not in quiet mode, it responds with an OK message. Set the modem up for dial-in access. The following table lists the AT commands required. Most of these command settings are the default settings. -------------------------------------------------------------------------- Command Description -------------------------------------------------------------------------- at&c1 Normal Carrier Detect (CD) operation. Tells the modem to not raise Carrier Detect until it see Carrier Detect from the other modem. at&d2 Normal Data Terminal Ready (DTR) operation. This is important in that it tells the modem to hang up the line when DTR drops. For example, when the user logs off the system. atq1 Sets the modem into quiet mode. Result codes are not sent to the system. ate0 Echo off. This prevents the modem from echoing back the login prompt issued by the getty process. ats0=n Specifies the number of rings to wait before answering. If n = 0 (zero), the modem will not answer. at&w0 Saves the current modem settings in NVRAM. The operating system supports both hardware and software flow control. If the system supports hardware flow control, set the modem and the serial line up to use hardware flow control by using the appropriate commands. If hardware flow control is not supported, you should use software flow control. Edit the /etc/inittab file and create an entry for the modem. If you want to use the modem line in non-shared mode, create an entry similar to the following: modem:23:respawn:/usr/sbin/getty /dev/tty00 M38400 vt100 If you want to use the modem line in shared mode (for dial-out and dial-in connections), use uugetty instead of getty and create an entry similar to the following: modem:23:respawn:/usr/lib/uucp/uugetty -r -t 60 tty00 38400 With uugetty, you will be able to use the tip and cu utilities, but might not be able to use third-party utilities because of dif- ferences in file locking. Note If you want to use the uugetty utility, you must install the UNIX-to-UNIX Copy Facility subset. As root, start the getty or uugetty process by entering the following command: init q The getty or uugetty process starts, then goes to sleep, waiting for someone to dial into the system. Configuring Your System for Dial-Out Access After you have obtained the correct cable and connected your modem to it and the telephone network, do the following: Verify that there is an entry for the modem name specified with the modemtype subcommand in the /etc/acucap file. If your modem does not have an entry in the /etc/acucap file, do the following: Copy an entry similar to that of your modem. The following entry is for a US Robotics modem for use in shared mode with tip: us|US|US Robotics (28.8 fax/data modem): :cr:hu:ls:re:ss=AT ATE1Q0&C0X0&A0 :sr=OK: :sd#250000:di=ATD:dt= : :dd#50000:fd#50:os=CONNECT:ds=d+++dATZ dATS0=2 : :ab=d+++dATZ dATS0=2: Be sure the entry includes at least the AT commands in the following table. The other modem settings can remain as they are. ------------------------------------- Command Description ------------------------------------- ate1 Turns on echoing. atq0 Displays the result codes. Modify the modem attributes to match your modem's attributes and include the debug option (db). With debugging turned on, the modem will provide you with additional information with which to tune the modem attributes in the file. See acucap(4) for more informa- tion. Create an entry in the /etc/remote for the system you want to call. Among the information you can supply is the Tru64 UNIX device, baud rate, and /etc/acucap that defines your modem. The following two entries are for the modem specified in step 1a. tip38400:tc=us38400 us38400|38400 Baud dial out via US Robotics modem: :el=^U^C^R^O^D^S^Q@:ie=#%$:oe=^D: :dv=/dev/tty00:br#38400:ps=none:at=us:du: In the previous example, the first line is an entry that points to the us38400 entry specifying shared capabilities for modems. The second line is the first line of the us38400 entry. The third line defines end-of-line characters, and input and output end-of-file marks. The fourth line defines the UNIX device to open for the connection, the baud rate, the parity, the name of the /etc/acucap file entry, and the dial-up line. See remote(4) for more information. If you use getty to provide access to the system from a modem and a getty process is already running, do the following: Edit the /etc/inittab file and put a comment character (#) at the beginning of the modem entry. Issue the init q command to terminate the getty process. Use the tip command, specifying the -baud_rate flag and the telephone number to dial out as follows: tip -38400 8881234 In this example, tip strips off the minus sign (-) from the baud rate and concatenates the tip command name and the baud rate to create the string tip38400. Then, tip searches the /etc/remote file for the entry matching the string. The entry in the /etc/remotes file, points the capability information in the us38400 entry to initialize the modem. By specifying the telephone number on the command line, you can share the same modem attributes for outgoing connections that have different telephone numbers. When you log off the remote system and exit tip, the modems saved settings are restored, readying the modem for the next user. If used in shared mode, the modem is available for dial-in access. RELATED INFORMATION
Commands: cu(1), tip(1), getty(8), uugetty(8). Files: acucap(4), inittab(4), remote(4). Devices: ports(7). Network Administration delim off modem(7)
All times are GMT -4. The time now is 07:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy