HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Failover devices cannot be changed?

 
Fredrik.eriksson
Valued Contributor

Failover devices cannot be changed?

Hi,

I'm trying to set up a 2 failover devices with 4 network cards.

My current setup looks like this:
V0003 Device Listing, volatile database (13-JUL-2009 10:29:09.88):
Device
------
EWA0
EWB0
EIA0
EIB0
LLA0

Where LLA0 is a failover set with EWA0 and EWB0.
This is no longer the correct setup since the net guys wants us to use EWA and EIA for LLA0 and EWB and EIB for LLB0.

When I try to change LLA0 I get this:
LANCP> define dev LLA0 /fail=(EWA0,EIA0) /enab
LANCP> set dev LLA0 /fail=(EWA0,EIA0)/enab
%LANCP-W-LLANON, Logical LAN already enabled, device LLA0
-LANCP-E-LLANACT, LAN device active, cannot be added to or removed from Logical LAN LLA0

If I then try disable the device:
LANCP> set dev lla0 /disab
%LANCP-E-LLANACT, LAN device active, cannot be added to or removed from Logical LAN LLA0

What am I doing wrong?

I've tried to clear/purge dev lla0 and redefining them without success..

Best regards
Fredrik Eriksson
4 REPLIES
The Brit
Honored Contributor

Re: Failover devices cannot be changed?

Hi Fredrik,
As the message indicated, it looks like you can't do anything with LLA0 because the device is active.

I think this can only be changed by rebooting. Set everything up in the permanent DB.

LANCP> PURGE DEV LLA0
LANCP> DEFINE DEV LLA0/FAILOVER=(EWA0,EIA0)
LANCP> DEFINE DEV LLA0/ENABLE
LANCP>

You should now be able to do a

LANCP> LIST DEV LLA0 /CHAR

and it should show the new device makeup.

Now Boot and the new device will be created. Remember your TCPIP setup if this device is your main network interface.

hth

Dave.

ps. I only THINK a reboot is necessary. Someone else may know better.
The Brit
Honored Contributor

Re: Failover devices cannot be changed?

It just occurred to me that you might be able to impliment the change by shutting down your network software (TCPIP/DECNET). Which wouldn't necessarily require a reboot, but it probably would take all of your users off the system.


Dave
Richard Stockdale
Frequent Advisor

Re: Failover devices cannot be changed?

You can find out what applications are using the ll device by doing:

mc lancp show config/user

Also, to do what you want, you can add and remove devices until you get the configuration you want, but if a particular device is active then you can't remove it. But you could do a LANCP SET DEV/SWITCH LLA to switch to the other device and then you could remove the device that is no longer active. So you can add and remove devices as long as they are not active (and of course not standby in another failover set).

- Dick
Fredrik.eriksson
Valued Contributor

Re: Failover devices cannot be changed?

Thank you all for the replies but I figured it out.

Seems like SCACP locked all devices at boot for use in my cluster communication.

Doing this solved it:
node> mc scacp
SCACP> stop lan EIA
SCACP> stop lan EWA
SCACP> stop lan LLA0
SCACP> exit
node> mc lancp
LANCP> define dev LLA0 /fail=(EIA,EWA)/enab
LANCP> set dev LLA0 /fail=(EIA,EWA)/enab
LANCP> exit
node> mc scacp
SCACP> start lan LLA0
SCACP> stop lan EIB
SCACP> stop lan EWB
SCACP> stop lan LLB0
SCACP> exit
node> mc lancp
LANCP> define dev LLB0 /fail=(EIB,EWB)/enab
LANCP> set dev LLB0 /fail=(EIB,EWB)/enab
LANCP> exit
node> mc scacp
SCACP> start lan LLB0

I did have to reboot (involuntary thou) since I accidently disabled all devices for cluster communication (which created a state transition), but it didn't release the devices.

Best regards
Fredrik Eriksson