Sponsored Content
Operating Systems Solaris SUNW, hme0: Link Down - Cable problem Post 302328378 by AlSmith1964 on Wednesday 24th of June 2009 08:16:41 AM
Old 06-24-2009
SUNW, hme0: Link Down - Cable problem

Ultra E150 Solaris 2.5.1 Oracle server. was working fine, then started losing network connection. I can see in messages file that it was complaining about another device using its ip address. Though not any longer, though I wonder if that was a red herring. My IT guys have now re-reserved its ip address on the dhcp server. I have restarted it several times but it won't talk to the network. I tried changing its ip address to another reserved one, but Oracle complains, the ip must be embedded in that somewhere. Should the ethernet cable socket flash when connected on this hardware? it doesn't. I tried a different cable, direct into a different hub.
 

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
DE(4)							     Kernel Interfaces Manual							     DE(4)

NAME
de - DEC DEUNA 10 Mb/s Ethernet interface SYNOPSIS
/sys/conf/SYSTEM: NDE de_controllers # DEUNA DESCRIPTION
The de interface provides access to a 10 Mb/s Ethernet network through a Digital Equipment UNIBUS Network Adapter (DEUNA). Each of the host's network addresses is specified at boot time with an SIOCSIFADDR ioctl. The de interface employs the address resolution protocol described in arp(4P) to dynamically map between Internet and Ethernet addresses on the local network. The interface normally tries to use a ``trailer'' encapsulation to minimize copying data on input and output. The use of trailers is nego- tiated with ARP. This negotiation may be disabled, on a per-interface basis, by setting the IFF_NOTRAILERS flag with an SIOCSIFFLAGS ioctl. DIAGNOSTICS
de%d: hardware address %s. This is a normal autoconfiguration message noting the 6 byte physical ethernet address of the adapter. de%d: oerror, flags=%b tdrerr=%b (len=%d). The hardware indicated an error in transmitting a packet to the cable. The status and error flags are reported. de%d: ierror, flags=%b lenerr=%b (len=%d). The hardware indicated an error in reading a packet from the cable. The status and error flags are reported. de%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was dropped. de%d: buffer unavailable. The interface received more packets than it had buffers allocated to receive them. de%d: address change failed, csr0=%b csr1=%b. The interface was unable to reprogram its physical ethernet address. This may happen with very early models of the interface. This facility is used only when the controller is not the first network interface configured for XNS. The following messages indicate a probable hardware error performing the indicated operation during autoconfiguration or initialization. The two control and status registers should indicate the nature of the failure. See the hardware manual for details. de%d: reset failed, csr0=%b csr1=%b. de%d: ppcb failed, csr0=%b csr1=%b. de%d: read addr failed, csr0=%b csr1=%b. de%d: wtring failed, csr0=%b csr1=%b. de%d: wtmode failed, csr0=%b csr1=%b. SEE ALSO
intro(4N), inet(4F), arp(4P) 3rd Berkeley Distribution August 20, 1987 DE(4)
All times are GMT -4. The time now is 01:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy