Have you seen this???

[Jorge Cocomess]

Greetings,

Has anyone seen this opcom message before??

%%%%%%%%%%% OPCOM 25-JAN-2006 22:35:22.12 %%%%%%%%%%%
Message from user SYSTEM on ELMO
Event: Carrier Check Failure from: Node LOCAL:.ELMO CSMA-CD Station CSMACD-0,
at: 2006-01-26-04:35:22.121+00:00Iinf
eventUid DED8FA3F-8DF2-11DA-914B-AA0004000404
entityUid 69D827EC-8CF1-11DA-8517-AA0004000404
streamUid 6CC0B824-8CF1-11DA-85F2-AA0004000404

Where do I go to look for this message? Do I need to call HP on this?

Please help!!

Thanks,
J

[Steven Schweda]

Looks like a complaint about an Ethernet
interface. If it recurs, check your network
hardware.

[Jorge Cocomess]

Constantly complaining about this device. I only have two (2) NICs on this server. Would you know which one is complaining about? I have to trouble connecting to my network either 10/100 or 1GB NIC.

Where do I go from here?

Thanks,
J

[Allan Bowman]

Jorge,

In addition to the NIC, I have also seen this problem with a bad cable - usually a bad crimp on an RJ45 connector.

Allan in Atlanta

[Karl Rohwedder · Accepted solution]

Acc. to tge message the errors are occurring on station CSMACD-0, so do a

$ MC NCL sho csma-cd station csmacd-0 all attr

to see which interface causes the problems.

regards Kalle

[Heinz W Genhart]

Hi Jorge

You can also use LANCP

$ MC LANCP SHO DEVICE

Device Listing, volatile database:
Device
------
EIA0
EIB0

$ MC LANCP SHO DEV EIA0/COUNTER
Device Counters EIA0:
Value Counter
----- -------
18876452 Seconds since last zeroed
606768811699 Bytes received
1627222720560 Bytes sent
2060201760 Packets received
2331385153 Packets sent
7159418541 Multicast bytes received
1398263199 Multicast bytes sent
47808782 Multicast packets received
10788996 Multicast packets sent
28 Unrecognized unicast destination packets
6009146 Unrecognized multicast destination packets
0 Unavailable station buffers
0 Unavailable user buffers
0 Alignment errors
0 Frame check errors
0 Frame size errors
0 Frame status errors
0 Frame length errors
0 Frame too long errors
3 Data overruns
0 Send data length errors
0 Receive data length errors
0 Transmit underrun errors
0 Transmit failures
0 Carrier check failures
0 Station failures
0 Initially deferred packets sent
0 Single collision packets sent
0 Multiple collision packets sent
0 Excessive collisions
0 Late collisions
0 Collision detect check failures


If You do this with every of your interfaces then you will find the problem interface. Have a look at the counters for Allignement & frame check Errors

Regards

Heinz

[Colin Butcher]

Carrier check failure usually means that there is no valid signal between the network infrastructure and the physical interface on the machine. Typically you see it when you start DECnet Phase V on an interface which is not connected to anything.

So, check if it's meant to be connected, if not then disable it in NCL.

If it is meant to be connected (which seems likely given that it's CSMACD-0) then check the physical connections and the switch port that it's plugged into. It may be as simple as the network switch has been shut down. It's possible that it could be a bad cable. I generally use high quality shielded Cat5/5e/6 cables and have then carefully routed to avoid physical damage from peple working in cabinets or the computer room. It may be that you're using fibre and a GBIC has failed.

Good luck!
Cheers, COlin.