Sponsored Content
Full Discussion: sun 420r hme0 not responding
Operating Systems Solaris sun 420r hme0 not responding Post 302155643 by alanj4 on Friday 4th of January 2008 09:59:01 PM
Old 01-04-2008
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 disabled?

or is a service not started?

Thanks
 

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. 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

4. Solaris

Install solaris 2.6 on Enterprise 420R

I am needing to install solaris 2.6 on a Enterprise 420R with 4X450mHz. Documentation says you need Operating Enviroment Installation CD February 2000(704-7076-10). Does anyone know where I can get this? (4 Replies)
Discussion started by: jenyart
4 Replies

5. Solaris

Sun V890: RSC firmware not responding

Hi all, After the V890 server shutdown unexpectedly, it became unaccessible from RSC. There is one error message about it: rscadm: RSC firmware not responding Do you have experienced this? Please help! (1 Reply)
Discussion started by: bamboonix
1 Replies

6. Solaris

How to show memory modules on 420R

I'm trying to determine what memory modules the box has so they can be ordered from a 3rd-party source and be replaced in-house (the box is not under warranty) I have a 420R running Solaris 9. # uname -a SunOS agatlsun04 5.9 Generic_118558-36 sun4u sparc SUNW,Ultra-80 Recently got a... (4 Replies)
Discussion started by: agcodba
4 Replies

7. UNIX for Dummies Questions & Answers

Console connection enterprise 420r

Hellow, i bought a sun enterprise 420r. I would like to connect to the console for installation of a new operating system (solaris 10) I made a connection from a usb --> com-port --> serial port of the server. I configured my hyperterminal (9600 8n1) and when i connect to my server and... (2 Replies)
Discussion started by: chelle007
2 Replies

8. Solaris

Sun Enterprise 420R

I am trying to connect to our Sun Enterprise 420R server via Hyperterminal. Using settings of 9600,n,1,n, I am getting nothing on COM4 (my laptop's ethernet port). I've also tried COM3, COM2, and COM5 - but at least I can type in COM4: the other three I cannot type when trying to connect. I am... (2 Replies)
Discussion started by: jmcgranahan
2 Replies

9. Solaris

ifconfig hme0 plumb not working

Hiii folks,, I am unable to configure NIC using hme0 command. I am getting an error message as "hme0: File or directory not found.." can someone help me... Bhagi... (9 Replies)
Discussion started by: bhargav90
9 Replies

10. Solaris

Sun enterprise 420R boot issue

Hi, I am using sun enterprise 420R server. Problem is on the monitor i am not able to see anything. I tried Serial connection, on terminal(using serial) i could see that POST(power on start tests) tests are being done, after that "timeout waiting for arp rarp packet" message keep displaying... (11 Replies)
Discussion started by: kkittu009
11 Replies
HOBBITPING(1)						      General Commands Manual						     HOBBITPING(1)

NAME
hobbitping - Xymon ping tool SYNOPSIS
hobbitping [--retries=N] [--timeout=N] [IP-adresses] DESCRIPTION
hobbitping(1) is used for ping testing of the hosts monitored by the xymon(7) monitoring system. It reads a list of IP adresses from stdin, and performs a "ping" check to see if these hosts are alive. It is normally invoked by the bbtest-net(1) utility, which performs all of the Xymon network tests. Optionally, if a list of IP-adresses is passed as commandline arguments, it will ping those IP's instead of reading them from stdin. hobbitping only handles IP-adresses, not hostnames. hobbitping was inspired by the fping(1) tool, but has been written from scratch to implement a fast ping tester without much of the over- head found in other such utilities. The output from hobbitping is similar to that of "fping -Ae". hobbitping probes multiple systems in parallel, and the runtime is therefore mostly dependant on the timeout-setting and the number of retries. With the default options, hobbitping takes approximately 18 seconds to ping all hosts (tested with an input set of 1500 IP adresses). SUID-ROOT INSTALLATION REQUIRED hobbitping needs to be installed with suid-root privileges, since it requires a "raw socket" to send and receive ICMP Echo (ping) packets. hobbitping is implemented such that it immediately drops the root privileges, and only regains them to perform two operations: Obtaining the raw socket, and optionally binding it to a specific source address. These operations are performed as root, the rest of the time hob- bitping runs with normal user privileges. Specifically, no user-supplied data or network data is used while running with root privileges. Therefore it should be safe to provide hobbitping with the necessary suid-root privileges. OPTIONS
--retries=N Sets the number of retries for hosts that fail to respond to the initial ping, i.e. the number of ping probes sent in addition to the initial probe. The default is --retries=2, to ping a host 3 times before concluding that it is not responding. --timeout=N Determines the timeout (in seconds) for ping probes. If a host does not respond within N seconds, it is regarded as unavailable, unless it responds to one of the retries. The default is --timeout=5. --responses=N hobbitping normally stops pinging a host after receiving a single response, and uses that to determine the round-trip time. If the first response takes longer to arrive - e.g. because of additional network overhead when first determining the route to the target host - it may skew the round-trip-time reports. You can then use this option to require N responses, and hobbitping will calculate the round-trip time as the average of all of responsetimes. --max-pps=N Maximum number of packets per second. This limits the number of ICMP packets hobbitping will send per second, by enforcing a brief delay after each packet is sent. The default setting is to send a maximum of 50 packets per second. Note that increasing this may cause flooding of the network, and since ICMP packets can be discarded by routers and other network equipment, this can cause erratic behaviour with hosts recorded as not responding when they are in fact OK. --source=ADDRESS Use ADDRESS as the source IP address of the ping packets sent. On multi-homed systems, allows you to select the source IP of the hosts going out, which might be necessary for ping to work. --debug Enable debug output. This prints out all packets sent and received. SEE ALSO
xymon(7), bbtest-net(1), fping(1) Xymon Version 4.2.3: 4 Feb 2009 HOBBITPING(1)
All times are GMT -4. The time now is 01:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy