メインコンテンツまでスキップ

Install Validation Failed エラー: LIF の十分性チェックに失敗しました

Views:
10
Visibility:
Public
Votes:
0
Category:
data-ontap-8
Specialty:
core
Last Updated:

のしんだ

に適用されます

『Data ONTAP 8.

問題

Upgrade Advisorsystem node image update を使用して clustered Data ONTAP 8.3 以降にアップグレードすると、コマンドの出力が大量に表示され、次のエラーメッセージが表示されて失敗します。
Install Failed. Install Validation Failed. ERROR: LIF sufficiency check failed.  

'LIF sufficiency check「」は、 clustered Data ONTAP 8.3 ソフトウェアから実行される検証スクリプトで、 SVM ごとに設定が有効かどうかをテストします。そうでない場合は、詳細のリストが表示されます。考えられる障害の出力例を次に示します。

 

Software update started on node nasclus-01. Updating image2 with package 83P2_q_image.tgz.
....
Checking Vserver(s) (nas01 nas02 nas03 nas04 vfs01) for sufficiency LIFs.

After upgrade, KDC Server 10.116.22.200 WILL BE UNREACHABLE from Vserver nas04.
After upgrade, AD Server 10.116.22.200 WILL BE UNREACHABLE from Vserver nas04.
After upgrade, Admin Server 10.116.22.200 WILL BE UNREACHABLE from Vserver nas04.
After upgrade, Password Server 10.116.22.200 WILL BE UNREACHABLE from Vserver nas04.
After upgrade, NIS domain Server 10.116.15.16 WILL BE UNREACHABLE from Vserver vfs01.
.....********************************************************************************
* *** FAILURES FOUND. ***
* You must correct these failures to avoid service disruptions.
*
* One way to avoid failures in most environments is to create a
* Vserver management LIF, one for each Vserver, that has connectivity to all
* external servers (infrastructure servers such as DNS/NIS/LDAP).
* Add a route for this LIF, if necessary, to provide connectivity to servers.
* This LIF's home-node should be the first node that will upgrade to 8.3.0.
* The LIF should have a failover group that includes ONLY the home node
* and its HA partner.  It should have auto-revert enabled.
* (Failover-group, failover-policy, and auto-revert may be set to other
* values as desired AFTER the cluster upgrade is complete.)
*       Command to add LIFs:
*         network interface create -vserver <Vserver_name> -lif <lif_name> -role data -data-protocol none
*         -home-node <node_in_first_ha_pair> -home-port <port_name> -address <IP_addr> -netmask-length <bits> -auto-revert true
*       Command to add routes:
*         network routing-groups route create -vserver <Vserver_name>
*       Commands to manage failover groups:
*         network interface failover-groups
*         network interface modify -vserver <Vserver_name> -lif <lif_name> -failover-group <group_name>
*       Command to modify a LIF's failover policy:
*         network interface modify -vserver <Vserver_name> -lif <lif_name> -failover-policy <policy>
*       Commands to modify a LIF's home node:
*         network interface modify -vserver <Vserver_name> -lif <lif_name> -home-node <node_name> -home-port <port_name>
*             network interface revert -vserver <Vserver_name> -lif <lif_name>
*       Command to modify a LIF's auto-revert settings:
*         network interface modify -vserver <Vserver_name> -lif <lif_name> -auto-revert true
*
* Other corrective actions may include:
*   - Remove any decommissioned external servers from the Vserver configuration.
*       Commands to show/modify/delete server configurations are in directories:
*         vserver services dns
*         vserver services nis-domain
*         vserver services kerberos-realm
*         vserver services ldap
*         vserver cifs domain
*         vserver fpolicy policy external-engine
*         vserver iscsi isns
*   - Restore any LIFs that are administratively down.
*       Command to determine if any LIFs are down:
*         network interface show -role data -status-admin down
*       Command to restore down LIFs:
*         network interface modify -vserver <Vserver_name> -lif <lif_name> 
-status-admin up           
*   - Restore any LIFs that are operationally down.
*       Command to determine if any LIFs are down:
*         network interface show -role data -status-oper down
*       Operationally down LIFs are generally caused by infrastructure issues.
*
* For more information, see the "Clustered Data ONTAP 8.3 Upgrade and
* Revert/Downgrade Guide".
********************************************************************************
Retry the image installation after taking corrective action.
ERROR: LIF sufficiency check failed.
Install Failed.
Software update/install aborted.
Error: command failed: Install Failed. Software update/install aborted.
 

: LIF の十分性チェッカーでもエラーが表示されない場合がありますが、アップグレードが完了する前にホストされているノードがフェイルオーバーし、ノード HA パートナーがフェイルオーバーグループに含まれていない場合に SVM に発生する可能性があることを示す警告が表示されます。

例:

************************************************************************************************

* *** WARNING ***

* Although SVM1 has the LIFs and routes that it needs to contact all external servers, NODE01 will not have access to
* sufficient LIFs for SVM1 to reach all external servers if NODE02 experiences a failure before additional nodes are upgraded.
* This could result in a service disruption if a node fails during the upgrade process.
*
* To prevent this type of service disruption during an upgrade, ensure that sufficient LIFs will be located on each NODE01 and
* NODE02 if the other nodes fails, by doing the following:
* Place LIFs with NODE01 or NODE02 as the home-node.
* Use failover groups/policies so that the LIF will only move between NODE01 and NODE02.
*       Commands to manage failover groups:
*         network interface failover-groups
*         network interface modify -vserver <Vserver_name> -lif <lif_name> -failover-group <group_name>
*       Command to modify a LIF's failover policy:
*         network interface modify -vserver <Vserver_name> -lif <lif_name> -failover-policy <policy>
*       Commands to modify a LIF's home node:
*         network interface modify -vserver <Vserver_name> -lif <lif_name> -home-node <node_name> -home-port <port_name>
*         network interface revert -vserver <Vserver_name> -lif <lif_name>
*       Command to modify a LIF's auto-revert settings:
*         network interface modify -vserver <Vserver_name> -lif <lif_name> -auto-revert true

************************************************************************************************

この場合、ノード 02 でホストされている SVM 1 に HA パートナー(ノード 01 )でフェイルオーバー用に設定されていない LIF があり、ノード 02 で障害が発生した場合、ノード 01 は SVM 1 の LIF をホストできません。

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support