Sponsored Content
Operating Systems Solaris SUNW, hme0: Link Down - Cable problem Post 302339128 by ilikecows on Wednesday 29th of July 2009 09:03:57 PM
Old 07-29-2009
Its always good practice to use the correct cable type even when devices are smart enough to use either a straight through or crossover. It doesn't really matter if its an E150 or not . The things that will make a difference are the NIC itself, OBP, and the OS NIC driver. Also if its true that the machine in question can actually detect cable type (I have my doubts considering its age, I could be wrong though) and the cable type detection isn't working then the laptop test wouldn't be a good test in this case (I have seen strange hardware failures where certain components of a piece of hardware fail).

You should always use a crossover when you are connecting two NICs directly. The general rule with twisted pair cable types is like devices use a crossover, different devices use a straight through. Treat router interfaces like a NIC an a network node.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

hme0 babble -- ?

Dear Reader, I have a very unique problem. Quite often my on board ethernet port( hme0 ) related message is appearing in /var/adm/messages. The message is hme0: babble.. The port is up and alive. What does this message mean.. Is the on board port is about to fail?? Thanks in advance, (2 Replies)
Discussion started by: joseph_shibu
2 Replies

2. UNIX for Advanced & Expert Users

Hme0 interfaces...

How do you configure more than one network on a single hme0 interface under SunOS? And why would you want to do this? Thanx :) -Michelle (1 Reply)
Discussion started by: Michelle1977
1 Replies

3. BSD

cable modem problem

hi I want to setup my cable modem under OpenBSD. I did not configure my network while installing the system. When I type, I get # ifconfig -a lo0 : .... ... ... rl0 : .... ... ... vr0 : ... ... ... I have two network cards (the machine will be a router). I created... (1 Reply)
Discussion started by: fnoyan
1 Replies

4. Solaris

Is the cable you are using a null modem cable or a modem cable

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

5. Solaris

hme0 problem after reboot

Hi ..... My problem is that when i reboot the system i can't connect to the network because my ethernet ( hme0 ) is down , i must up it by ifconfig command after reboot : # ifconfig -a lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask... (1 Reply)
Discussion started by: tt155
1 Replies

6. Solaris

sun 420r hme0 not responding

I have a 420r server it boots up all of the network settings are correct, however the machines network connection is not working. Cant ping anything from it, cant ping it from another machine on the network. If I ping 127.0.0.1 it says alive. Is there a chance the network card has been... (2 Replies)
Discussion started by: alanj4
2 Replies

7. Solaris

cannot telnet/ftp to solaris machine by straight cable makes problem ..

Hi All, 1. modify /etc/default/login file as make commented # console= 2.put my laptops ip at both /etc/inet/ipnodes and /etc/host file still i can login via telnet/ftp through a DB9-serial cable, but when i tried through a lan stratight cable directly connected that machine... (7 Replies)
Discussion started by: mahadib
7 Replies

8. Solaris

what is going on with SUNW.HAStoragePlus?!!!!!

Hi all, really interesting thing I have encountered . So : root@host4 # uname -a SunOS host4 5.9 Generic_122300-31 sun4u sparc SUNW,Sun-Fire-880 root@host4 # scinstall -p 3.2 latest recommended patches applied ..all SUN cluster patches applied. SUN cluster software installed without... (2 Replies)
Discussion started by: samar
2 Replies

9. Solaris

Cable link down

We are unable to ping from Sun Ultra 60 to Ultra 10 machine and vice versa. We are getting an error message Cable Link Down ?. It was working fine. Troubleshooting steps taken. 1) Changed the IPaddresses on both machines 192.168.10.10 and 192.168.10.20. These machines connected through 8 port... (2 Replies)
Discussion started by: vijaykrishna
2 Replies

10. Red Hat

Different hostnames with reboot while lan cable, no lan cable

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
LIEBERT(8)							    NUT Manual								LIEBERT(8)

NAME
liebert - Driver for Liebert contact-closure UPS equipment NOTE
This man page only documents the hardware-specific features of the liebert driver. For information about the core driver, see nutupsdrv(8). SUPPORTED HARDWARE
This driver supports some Liebert UPS equipment with a contact-closure interface. This includes the UPStation GXT2 with their contact-closure cable. The smart mode ("Multilink") cable is not supported by this driver. EXTRA ARGUMENTS
This driver does not support any extra settings in the ups.conf(5). BUGS
This driver does not yet support shutdowns by raising DTR. Be aware that shutdowns are not possible with the stock contact-closure cable. You may have to build another cable with DTR connected through to the UPS for it to work. There is no way for this driver to detect the hardware or cable. It will start up successfully even if no UPS is present. This is a fundamental limitation of any contact-closure driver. SEE ALSO
The core driver: nutupsdrv(8) Internet resources: The NUT (Network UPS Tools) home page: http://www.networkupstools.org/ Network UPS Tools 05/21/2012 LIEBERT(8)
All times are GMT -4. The time now is 11:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy