08-11-2014
With a "UNIX terminal" do you mean a real, physical serial console or a telnet/ssh emulator on a desktop? I'm not clear. It might be that you have a console server that you can telnet to that connects you to the serial console.
You might need to tell us what you are using. Be very specific too, although we won't need the unique serial numbers.
Do you mean that you changed the server IP address? As you can see, I'm rather confused.
Thanks, in advance,
Robin
10 More Discussions You Might Find Interesting
1. IP Networking
Hi,
I would like to know how i can setup my unix computer to connect to novell. Anybody any idea? (5 Replies)
Discussion started by: edw1ns
5 Replies
2. Solaris
I have 4 V440 servers running Solaris 9. I have their interfaces configured (ce0) and have connectivity to our network. However, after reboot,...the connectivity is lost although the interface shows that its still up after an ifconfig -a.
Only after I reconfigure the interface do I restore... (19 Replies)
Discussion started by: StorageGuy
19 Replies
3. Solaris
I have a solaris 10 x86 installed on a VMware server. It has been runing well for a couple weeks, but started to have network connectivity issue since last week. The network card seems to be up and down every one minute. So I got connection closed after I sshed to it for about one minute.
#... (2 Replies)
Discussion started by: fredao
2 Replies
4. UNIX for Advanced & Expert Users
Hi guys,
I had two computer which is one with vista and other one with fedora and they are connected via one router.
from vista to fedora is fine.. I can ping or connect via putty using Ip address but I couldn't connect putty using hostname/domain.
If I typed in fedora the hostname,... (0 Replies)
Discussion started by: peac3
0 Replies
5. Linux
I have a cluster set up with a head node and compute nodes running TORQUE and MOAB. The distro is ROCKS 5.3. I've been having problems with the connectivity for the past couple weeks now. Every couple hours it seems like the network connectivity will just stop working: sometimes it'll start back up... (0 Replies)
Discussion started by: gandalf85
0 Replies
6. UNIX for Dummies Questions & Answers
red hat 5 update 4 64bit. linux newby. on an interactive boot i can ping -t my vm linux server from my physical MS XP workstation and a vm W2000 64 bit server until xend is started, after that i get destination unreachable. if i choose not to start xend on the interactive boot i retain... (1 Reply)
Discussion started by: slartibartfast9
1 Replies
7. AIX
Hello Everyone
We have purchased IBM Pureflex chassis with 5 P460 blades. We have configured each blade with dual vios and 4 vio clients. VIOS installation and vio client installation and configuration was completed successfully.
When we tried to connect the network cables from Pureflex... (2 Replies)
Discussion started by: yuvarakasil
2 Replies
8. UNIX for Dummies Questions & Answers
Hi!
I am not sure if this is the right place to post this question. What I did was to download vmware onto my laptop, them install a linux distro as a guest O.S., on VM network configuration I have used "bridge", them I used Virtual Network Editor to chose the network interface, but as I write... (4 Replies)
Discussion started by: fretagi
4 Replies
9. Shell Programming and Scripting
Hello All,
We are running multiple codes in prod all having different sources of databases in other servers. Many times due to network issue connectivity and DB issue the jobs got failed and to recover them become very brainstorming . I planning to create one script that can pre check if all the... (0 Replies)
Discussion started by: looney
0 Replies
10. Solaris
Hi, I am facing a weird issue here. we have a Solaris 10 server running 15 non-global zones. The issue is all the systems suddenly stopped connectivity from outside/remotely..
Ping is also not working.
After some troubleshooting, what I observed is when all the non-global zones are halted,... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
ports(7) Miscellaneous Information Manual ports(7)
NAME
ports, port_names - Device (tty and lp) names for serial and parallel ports
SYNOPSIS
Default Serial Ports:
/dev/tty00
/dev/tty01 (not present on a single-port system)
Parallel Port:
/dev/lp0
DESCRIPTION
AlphaStation and AlphaServer systems provide one or two 9-pin serial communication ports. These ports are usually labelled 1 (COMM1) and 2
(COMM2), but they may be identified by different icons. Using the appropriate serial cable and terminator, you can connect a serial
printer, external modem, or character-cell terminal to a serial port. Most AlphaStation and AlphaServer systems also provide one parallel
port, for use with a parallel printer.
When you add a device to your system, the installation documentation may instruct you to map the device pathname to the port. These
devices are located in the /dev directory.
For serial-line ports, the two default device pathnames are: This pathname always maps to 1, COMM1, the lowest port number, an icon for a
terminal console, or the only serial port (on a single-port system). This pathname always maps to 2, COMM2, the next numbered port, or (if
one serial port is labeled with an icon for a terminal console) the remaining serial port.
If your system hardware has been extended to include additional serial ports, the pathnames /dev/tty02, /dev/tty03, and so forth, may also
be available to you. However, most systems have only /dev/tty00 and /dev/tty01 as the device pathnames for serial ports.
The one parallel port on an AlphaStation or AlphaServer may be labeled with the word printer or a printer icon. On some systems, the paral-
lel port may not be labeled. The device pathname for the parallel port is /dev/lp0. Currently, Tru64 UNIX does not fully support parallel
printers, so fewer devices are connected to this port as compared to serial ports.
If you are connecting a terminal console to your system, it must be connected to the serial port mapped to /dev/tty00. For other serial
devices, it does not matter which of the serial ports you choose for the connection. For example, suppose you are setting up a system that
has two serial ports, labeled 1 and 2. You intend to use a serial-line terminal rather than a workstation monitor as the system console and
also want to connect a serial-line printer to the system. In this case, you must connect the terminal to the port labeled 1 (with the
device pathname /dev/tty00). Therefore, you must connect the printer to the remaining port labeled 2 (with the device pathname /dev/tty01).
If, for the same type of system, you intend to use a workstation monitor as the system console, it does not matter which serial port you
use for a serial-line printer or modem. In other words, you can connect the printer to either port 1 (with pathname /dev/tty00) or port 2
(with pathname /dev/tty01). When prompted to enter a /dev/tty** pathname by the lprsetup script or the Print configuration tool in the CDE
Application Manager, you would specify /dev/tty00 if you connected the printer to port 1 or /dev/tty01 if you connected the printer to port
2.
See the System Administration manual for more information on setting up consoles (including remote consoles) and printers. See the
modem(7) reference page for more information on setting up modems.
SEE ALSO
Commands: lprsetup(8)
Devices: ace(7), modem(7)
System Administration delim off
ports(7)