Howdy all,


I would like to know how can I disable hmeX in my server and then stop
messages like "...,hme1 : No response from Ethernet network : Link down
-- cable problem?" while I'm connected in the machine via Console?

Just for information, I don't have any /etc/hostname.hmeX file and the
auto-negotiation parameter (via ndd command) is disabled ("0") for the
interfaces.

See below my ifconfig -a command. As you can see, there is no hme
interface and the problem persists:

-x-
root@mbe-uplinkdb1 # Oct 10 16:56:02 mbe-uplinkdb1 hme: SUNW,hme1 : No
response from Ethernet network : Link down -- cable problem?

root@mbe-uplinkdb1 # ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000

qfe1:
flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPRE CATED,IPv4,NOFAILOVER>
mtu 1500 index 2 inet 10.132.1.101 netmask ff000000 broadcast
10.255.255.255 groupname logserv ether 8:0:20:c9:f3:cd

qfe5:
flags=19040843<UP,BROADCAST,RUNNING,MULTICAST,DEPR ECATED,IPv4,NOFAILOVER,FAILED>
mtu 1500 index 4 inet 10.132.1.103 netmask ff000000 broadcast
10.255.255.255 groupname logserv ether 8:0:20:c9:57:c5

-x-


Tia,


Marcelo Muzilli

In article <1129027673.125906.52660@z14g2000cwz.googlegroups. com>, "mmuzilli@gmail.com" <mmuzilli@gmail.com> wrote:
>Howdy all,
>
>
>I would like to know how can I disable hmeX in my server and then stop
>messages like "...,hme1 : No response from Ethernet network : Link down
>-- cable problem?" while I'm connected in the machine via Console?
>

We used to cut off an ethernet cable, and wire the transmit pair
to the recieve pair. Then it talked to itself, and was happy.

I've also seen this when it wasn't figuring out the 10/100
stuff right (early enough, actually). I eventually found a
way to force it, but I forget how.


>Just for information, I don't have any /etc/hostname.hmeX file and the
>auto-negotiation parameter (via ndd command) is disabled ("0") for the
>interfaces.
>
>See below my ifconfig -a command. As you can see, there is no hme
>interface and the problem persists:
>
>-x-
>root@mbe-uplinkdb1 # Oct 10 16:56:02 mbe-uplinkdb1 hme: SUNW,hme1 : No
>response from Ethernet network : Link down -- cable problem?
>
>root@mbe-uplinkdb1 # ifconfig -a
>lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
>inet 127.0.0.1 netmask ff000000
>
>qfe1:
>flags=9040843<UP,BROADCAST,RUNNING,MULTICAST,DEPR ECATED,IPv4,NOFAILOVER>
>mtu 1500 index 2 inet 10.132.1.101 netmask ff000000 broadcast
>10.255.255.255 groupname logserv ether 8:0:20:c9:f3:cd
>
>qfe5:
>flags=19040843<UP,BROADCAST,RUNNING,MULTICAST,DEP RECATED,IPv4,NOFAILOVER,FAILED
>>
>mtu 1500 index 4 inet 10.132.1.103 netmask ff000000 broadcast
>10.255.255.255 groupname logserv ether 8:0:20:c9:57:c5
>
>-x-
>
>
>Tia,
>
>
>Marcelo Muzilli
>