05-08-2010
Corona688 is correct. Generally no need for a crossover cable for Gigabit NICs.
If you connect these systems into your network, can they communicate with each other?
I see you have other network adapters in your systems. Are they in use?
Are you using the exact same NICs (make, model#, driver) on both systems? NC373i?
Last edited by fpmurphy; 05-08-2010 at 11:57 AM..
9 More Discussions You Might Find Interesting
1. Solaris
Hi all,
Is there any difference between a null modem cable or a modem cable ?
i assume that a null modem cable is a normal cable that i used from cpu serial ports to a modem for dialup.
please correct if i am wrong,
thks (2 Replies)
Discussion started by: waterbear
2 Replies
2. High Performance Computing
Hi grus,
has anybody tried for Sun cluster interconnect normal cable ,, I mean not interconnect .. What do u think ..does it support this ?
Not long ago I tried Veritas cluster and its interconnections work great with normal cable .. I wonder what will Sun cluster say to it :)) (3 Replies)
Discussion started by: samar
3 Replies
3. Red Hat
hi..
I unplug my eth0 lan cable.. and suddenly my system shutdown... no idea :eek::confused: (3 Replies)
Discussion started by: flekzout
3 Replies
4. IP Networking
Hi, I am trying to implement a server-client socket communication. My server and clients are in different PCs. During communications if the ethernet cable is removed from the server side it shows broken pipe due to unable to write on the socket. I want to know how to check whether the ethernet... (0 Replies)
Discussion started by: JagadishB
0 Replies
5. UNIX for Dummies Questions & Answers
how to change ethernet cable of iscsi initiator (iscsi client) (0 Replies)
Discussion started by: pankajd
0 Replies
6. Programming
Hi,
I want to code TCP/IP client/server in linux application capable to fastly detect ethernet cable disconnection in any condition.
So I have activate SO_KEEPALIVE options and set TCP_KEEPCNT, TCP_KEEPIDLE and TCP_KEEPINTVL to 1.
When I disconnect ethernet cable I have the following... (5 Replies)
Discussion started by: jeje_clb
5 Replies
7. Red Hat
I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable
Reboot with lan cable:
The hostname is ubunut
Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies
8. AIX
Hi
In the vio server when I do # lsattr -El hdisk*, I get a PVID. The same PVID is also seen when I put the lspv command on the vio client partition. This way Im able to confirm the lun using the PVID.
Similarly how does the vio client partition gets the virtual ethernet scsi client adapter... (1 Reply)
Discussion started by: newtoaixos
1 Replies
9. AIX
Hi Techies,
I have a doubt.
ent0 Available Logical Host Ethernet Port (lp-hea)
ent1 Available Logical Host Ethernet Port (lp-hea)
ent2 Available Logical Host Ethernet Port (lp-hea)
ent3 Available Logical Host Ethernet Port (lp-hea)
ent4 Available... (4 Replies)
Discussion started by: jayadeava
4 Replies
LEARN ABOUT DEBIAN
x_init
X_INIT(1gmt) Generic Mapping Tools X_INIT(1gmt)
NAME
x_init - Initialization of Cross-Over Data Bases.
SYNOPSIS
x_init -I
DESCRIPTION
The purpose of x_init is to create two key files that will be holding all the cross-over information for all the cruises tested. These
files are called xx_base.b and xx_legs.b, and they will contain data for each cross-over and totals for each leg, respectively. x_init
will create these two files in the current directory, and write out the fileheader with a 1 as the next record number in the case of
xx_base.b. NB! Any previous files with the same names in the current directory will be erased, so use with caution.
-I Must be present form initialization to take effect.
BEWARE
Both files are binary and have fixed record lengths. The formats of the files are as follows:
xx_base.b:
Record length = 40 bytes.
Rec # 1: fileheader
Rec # 2: pairheader
Next n recs: crossover-structure
Rec # n+3: pairheader etc.
The fileheader is a 40 byte character string where the last 10 bytes contains the record number of the last record in the file. The
pairheader is a 40 byte character string which contains the names of the two legs in question and the number of COEs generated
between them. The crossover-structure contains all the information for one COE, that is lat, lon, time along leg values of gravity,
magnetics, and bathymetry at the cross-over point, the heading of track #1, and the heading of track #2. See program listing for
more details on formats. The file is sequential in that new data are appended at the end of the file.
xx_legs.b:
Record length = 204 bytes.
Each record contains the complete information for each leg that has been checked. The leg-structure contains fields like year of
cruise, number of internal/external COEs for gravity, magnetics, and bathymetry, their means and standard deviations, and the best
fitting regression lines, i.e. the dc-shifts and drift-rates computed from the time/error data points. See program listing for com-
plete description of record format.
SEE ALSO
GMT(1), x_system(1)
REFERENCES
Wessel, P. XOVER: A Cross-over Error Detector for Track Data, Computers & Geosciences, 15, 333-346.
GMT 4.5.7 15 Jul 2011 X_INIT(1gmt)