Board index Solaris

very odd problem with hme1

very odd problem with hme1

Post by Samee » Fri, 30 Jan 2004 18:03:09



hmm, this is an odd one.  i have an additional fastethernet card in my
ultra2.  it's acting up.

when i rebooted, the nic was intermittant in response.  here's the output:

------------------
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.200.4: bytes=32 time=2ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.200.4: bytes=32 time=1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Request timed out.
----------------------

eventually, the card becomes inresponsive and doesn't respond to anything.
i've configured it properly, and the ultra2's onboard fastethernet works w/o
any hiccups.

so i don't get what's going on with this one.

is there anyway to test the hardware to see if the card's defective?

 
 
 
Top

very odd problem with hme1

Post by Mr. Johan Andersso » Fri, 30 Jan 2004 19:00:40



> hmm, this is an odd one.  i have an additional fastethernet card in my
> ultra2.  it's acting up.

> when i rebooted, the nic was intermittant in response.  here's the output:

> ------------------
> Request timed out.
> Request timed out.
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time=2ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time=1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Reply from 192.168.200.4: bytes=32 time<1ms TTL=255
> Request timed out.
> Request timed out.
> Request timed out.
> Request timed out.
> ----------------------

> eventually, the card becomes inresponsive and doesn't respond to anything.
> i've configured it properly, and the ultra2's onboard fastethernet works w/o
> any hiccups.

> so i don't get what's going on with this one.

> is there anyway to test the hardware to see if the card's defective?

Are you sure its the card?
Have you done all other tests?

* checked that cable is properly attached and not broken?
* changed cable anyway, just to check.
* checked that switch/hub/cross is ok?
* try connecting the working cable from the other port (or other system)
  and see if you get proper link ups and such.
  Direct connect to another system (any with an ethernet) to take all else
  out of the loop.

If all thoose doesnt make any diff, then I would suspect a broken card or
possibly that you need a patch/fw for the card.

/Johan A

 
 
 
Top

very odd problem with hme1

Post by Marc Doumayro » Fri, 30 Jan 2004 23:29:56


Sameer a crit :
Quote:

> hmm, this is an odd one.  i have an additional fastethernet card in my
> ultra2.  it's acting up.

> when i rebooted, the nic was intermittant in response.  here's the output:

that looks like a problem I see from time to time : duplicate ip
adresses
on your lan. try unplugin that station an pinging the ip again.

Regards, Marc

 
 
 
Top

1. Problem with hme1 on Netra t1 and Solaris 2.6

After installing Solaris 2.6 and on Netra t1 I'm having a problem with
getting Firewall-1 to work. It was supposed to be a simple move of a
firewall from Ultra 10 to Netra t1. The FW-1 license depends on
IP number and not the hostID.

I also tried to run firewall install to see if it makes any difference.

The message during boot up:

FireWall-1: Starting fwd
FireWall-1: Starting fwd (Remote Management Server)
fwm: FireWall-1 Management Server is running

FireWall-1: Fetching Security Policy from localhost
Trying to fetch Security Policy from localhost:


Using external interface 'hme1'
Has only loopback (lo) interface, aborting...
Failed to Load Security Policy: No such file or directory
Fetching Security Policy from locahost failed
FireWall-1 started

ifconfig -a

hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
W             inet 192.168.12.1 netmask ffffff00 broadcast
192.168.12.255
-1: fwsm_qdata_init: device hme is unknown (609d4730)
FW-1: initialized on hme0 (1)
                 ether 8:0:20:b2:97:43

hme1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
W             inet 192.168.12.1 netmask ffffff00 broadcast
209.137.xxx.255
-1: fwsm_qdata_init: device hme is unknown (609d4730)
FW-1: initialized on hme1 (2)
                 ether 8:0:20:b2:97:43

Note that the mask for hme1 is incorrect. It's supposed to be fffffff8.
I'm pretty sure that all the files needed for correct configuration are
in place.  /etc/netmasks has a correct entry. ifconfig shows MAC # the
same for both interfaces, but that's identical with Ultra 10.
I can ping to other machines on both sides of the machine, I can ftp and
telnet on 192 network.

It seems to me that the firewall fails due to incorrect hme1 setup. If I
bootup with Solaris 7, then the interfaces work fine and netmask is
correct but the Firewall-1 doesn't work with it :-(

I installed all the recommended patches for Solaris 2.6.  I wish that
Firewall-1 would work with Solaris 7 and all I would need to do is use a
spare drive which still has the original Solaris 7. Is it possible that
one of the patches was not supposed to be installed? I would preffer
Solaris 7 with all the patches for Netra t1 since it's a new machine and
has some features that were not available in solaris 2.6 days.

I must have overlooked something; any suggestions?

Thanks,

Rafael Skodlar
Systems Administrator

2. Help with CD Writer - Yamaha CRW4416S

3. le0 and hme1 problem

4. -=-=-= A challenge, a prize and a good cause =-=-=-

5. i810-tco : odd behavior, odd driver ?

6. Latency with SLIP

7. Linux FTP problem -- A VERY ODD problem

8. XFree86 3.2A fixes Mach64 problems!

9. Problems with Fall '94 Yggdrasil (odd cd problems)

10. Linux FTP problem -- A VERY ODD problem

11. hme or (hme0 and hme1)

12. hme1: ddi_map_regs for hme global reg failed

13. hostname.hme0 or hostname.hme1


All times are UTC
Board index