hp - compaq interface woes

[Mark Greene_1]

I've got an L2000 I'm trying to setup a on a private network with a DEC^H^H^Compaq Alpha. Things were going ok until this morning when the HP box started having issues.

At first it was refusing the network connection. The HP saw the NIC fine, the config looked ok, but it refused to send to or recieve from the Compaq. Off-the-wall messages like "incompatable network" and "redundant line" were displaying on the console.

Upgrading the ethernet to FDDI seemed to work for a while, then the HP started spontaneously rebooting. "Packet overflow" and "non-trusted system interface" errors. Dropping the FDDI to half duplex stopped the reboots, but not the thing just hangs like it is waiting for something to finish.

The last message line on the console is....


"waiting for final tally...."


what ever could this mean?

--
mark

[Wodisch · Accepted solution]

Hi,

I guess you have an "LirPa first" error there;
the solution is perhaps to get rid of your
local "walter" to get your share of packets
flowing, again...

Just my $0.02,
Wodisch

[Darrell Allen]

Hi Mark,

I've been seeing this same problem. HPUX wants to claim exclusive use of the connection to the Compaq however there is a conflict with the NIC which, as you have noted, is refusing the connection. The contention is causing excessive CPU cycles and system overhead.

At this point it is undetermined whether the problem is best solved by replacing the CPU or by replacing the NIC although it is apparant that one or the other will have to be replaced. Additionally, there is the possibility that both will need to be replaced to ensure this issue doesn't arise again in the future.

Darrell

[Mark Greene_1]

Wodisch,

As per your usual, your 2 cents are right on the money!

Darrel,

Good thought, we'll have to see what happens.

I had hoped to have had more replies than just the two of you, perhaps I made it all to obvious, but a nice bit of fun nonetheless, thanks for playing along!

mark