topic Re: LAN Card Replace in Cluster mode in Operating System - OpenVMS

LAN Card Replace in Cluster mode

YAQUB_1 — Tue, 25 Nov 2008 06:47:00 GMT

Dear Friends,

We have replaced in a LAN card AB545-60001 (PCI-X 4-PORT 1000BASETX LAN CARD) in our existing environment.

I would like to inform you, I am not familiar with HP OpenVMS but I have work in HP-UX platform. I will share with you my current systems info:-

H/W: rx3600
OS: HP OpenVMS v8.3 with Cluster
Storage: MSA30 (connect with SCSI)

Could you please assist to me how I can solve this issue?

Rgds--Yaqub

Re: LAN Card Replace in Cluster mode

Karl Rohwedder — Tue, 25 Nov 2008 06:58:37 GMT

Perhaps you should tell us something about the issue you have... :-)

regards Kalle

Re: LAN Card Replace in Cluster mode

YAQUB_1 — Tue, 25 Nov 2008 07:11:41 GMT

Hi Karl,

Thanks for your reply.

"H/W alarms in CISCO ITP 7301" second node (Cluster).

If you need other info, pls acknowledge me.

Rgdsâ Yaqub

Re: LAN Card Replace in Cluster mode

Volker Halle — Tue, 25 Nov 2008 07:25:16 GMT

Yaqub,

knowing nothing about CISCO ITP 7301 and SS7, consider that the MAC address of the network card will have changed.

You can look at the characteristics and counters of the network cards on your OpenVMS system mit $ MC LANCP SHOW DEV/CHAR and /COUNT.

Volker.

Re: LAN Card Replace in Cluster mode

Hoff — Tue, 25 Nov 2008 15:15:02 GMT

This does not appear to be an OpenVMS question on the face of it; the NIC was changed and the MAC address swap has apparently confounded or perturbed some Cisco network widget upstream.

Reasons for the NIC swap that occurred here are unclear, and could well be related to the NIC swap or some other problem within the network configuration or the LAN; somebody could be chasing network problems.

Assuming that OpenVMS itself and its networking is entirely happy, go ask your local network folks and/or Cisco for assistance with resolving this Cisco error.

But regardless, go check with your Cisco LAN folks or with your Cisco escalation resource(s). Let them know the NIC was swapped.

And if you want to pursue this case (and in any forum), you need to get the specific details from the Cisco switch. Specific error messages. Specific error codes. Specific configuration details. Specific simplex and duplex settings. And regardless, errors on the Cisco switch involved here needs to be investigated and addressed first in the Cisco context. Not in the OpenVMS context.

If these Cisco hardware errors are secondary to a bogus duplex setting, those knobs can be invoked in the LANCP utility. In most cases, the NIC LAN devices should be left set to auto-negotiate per HP recommendations.

Re: LAN Card Replace in Cluster mode

YAQUB_1 — Wed, 26 Nov 2008 06:06:11 GMT

Hi Volkar,

Attached you quarry output.

Hi Hoff,

When we execute "show dev/char and /count" that time EIJ0 lan device is not able to list. That why we suspect LAN card faulty.

If you have any alternative guide line, please assist to me.

BR/
Yaqub

Re: LAN Card Replace in Cluster mode

Volker Halle — Wed, 26 Nov 2008 07:35:41 GMT

Yaqub,

if you look at the MAC adresses of the LAN devices, you have to wonder, why the first card seems to only show 3 adresses with the same basic MAC address (just incrementing the last byte).

If you look at the back of your RX3600, I bet their will be 10 network cable sockets, but OpenVMS has only configured 9 LAN interfaces. The problem seems to be with the first LAN network card - assuming it's also a 4-port card.

You can look at the hardware of the system using SDA:

$ SET TERM/WID=132
$ ANAL/SYS
SDA> CLUE CONFIG
... ! need to type a couple of
SDA> EXIT

This will give you a list of the hardware configuration. You may want to post this data, so we can determine exactly which LAN cards are present.

Volker.

Re: LAN Card Replace in Cluster mode

Hoff — Wed, 26 Nov 2008 21:36:08 GMT

You can re-run the configuration tool, and specifically the core environments - interfaces section.

@SYS$MANAGER:TCPIP$CONFIG

Ensure all devices are configured, and that all are wired.

Otherwise, swap the card.

These boxes are comparatively and unfortunately weak around the hardware user interface and the management of the device and network connectivity; I've usually ended up pulling the box off-line and probing the connections individually to figure out which device is which. Then label them. (The LANCP utility should be able to show you the network link state.) This too is an area of the hardware UI that is lacking: you have to create and mount your own labels for the devices including the NIC sockets.