Knowledge Search


×
 

[Mobile Control Gateway] NGW blade cannot be locked and taken out of service due to a service unit being actively serviced by it

  [KB24125] Show Article Properties


Summary:
This article describes the issue of being unable to lock and take out the NGW blade out of service, due to a service unit being actively serviced by it.
Symptoms:
When attempting to lock one of the Network Gateway Cards[NGW], the following error message is generated:
cli>hardware app-blade lock 0 0 10 0 force
%Warning: You are about to lock the hardware. Do you want to continue?
confirm (y/n)>y
%Error[0x00000014]: Blade is not allowed to be taken out of service. Reason: L2TPManager_SU_1 Providing active service on 2N redundancy.
Note that the Service-Unit cannot be disabled:
cli>aim service-unit lock L2TPManager 0
%Error[0x000F000C]: command not supported for this service-unit

cli>aim service-unit lock L2TPManager 1
%Error[0x000F000C]: command not supported for this service-unit

cli>aim service-unit lock L2TPManager 1 force
%Error[0x000F000C]: command not supported for this service-unit
Cause:

Solution:
The above error message is generated, when an attempt is made to lock the NGW, as it is servicing one of the base service units. Also, a base service unit cannot be locked, as the base has specific control over these service units. On NGW cards, there are 3 main/base service units that run in the Active/Standby mode. They are L2TPManager, VRDS_CP_NGW, and VRDS_MP_NGW.
cli>aim service-unit show all where slot = 3 or slot = 10

sg-name su adm-state opr-state rdy-state fr sh sl
sb
--------------- -- ------------- --------- -------------- -- -- --
--
L2TPManager 0 unlocked enabled in-service 0 0 3 2
L2TPManager 1 unlocked enabled in-service 0 0 10 2
VRDS_CP_NGW 0 unlocked enabled in-service 0 0 3 2
VRDS_CP_NGW 1 unlocked enabled in-service 0 0 10 2
VRDS_DP1_NGW 0 unlocked enabled in-service 0 0 3 2
VRDS_DP1_NGW 1 unlocked enabled in-service 0 0 10 2
VRDS_DP2_NGW 0 unlocked enabled in-service 0 0 3 1
VRDS_DP2_NGW 1 unlocked enabled in-service 0 0 10 1
VRDS_MP_NGW 0 unlocked enabled in-service 0 0 3 2
VRDS_MP_NGW 1 unlocked enabled in-service 0 0 10 2
VRDS_SYN_NGW 0 unlocked enabled in-service 0 0 3 2
VRDS_SYN_NGW 1 unlocked enabled in-service 0 0 10 2

cli>aim si-assignment show all where slot = 3 or slot = 10

sg-name su si-name ha-state fr sh sl sb
-------------------- -- -------------------- --------- -- -- -- --
L2TPManager 0 SI_0 active 0 0 3 2
L2TPManager 1 SI_0 standby 0 0 10 2
VRDS_CP_NGW 0 SI_0 active 0 0 3 2
VRDS_CP_NGW 1 SI_0 standby 0 0 10 2
VRDS_DP1_NGW 0 SI_0 active 0 0 3 2
VRDS_DP1_NGW 1 SI_1 active 0 0 10 2
VRDS_DP2_NGW 0 SI_0 active 0 0 3 1
VRDS_DP2_NGW 1 SI_1 active 0 0 10 1
VRDS_MP_NGW 0 SI_0 active 0 0 3 2
VRDS_MP_NGW 1 SI_0 standby 0 0 10 2
VRDS_SYN_NGW 0 SI_0 active 0 0 3 2
VRDS_SYN_NGW 1 SI_1 active 0 0 10 2
Operation success
For a NGW blade to be locked, it cannot be hosting an active L2TPManager, VRDS_CP_NGW, or VRDS_MP_NGW service unit. You can verify via the above command, that SU 0 should be NGW 0 (slot3) and SU 1 is NGW 1 (slot10). In this case, if NGW 0 needs to be locked, you will have to swact the 3 SUs and then lock the blade:
aim service-unit swact L2TPManager 0
aim service-unit swact VRDS_CP_NGW 0
aim service-unit swact VRDS_MP_NGW 0

hardware app lock 0 0 3 0
Alternatively, you can run the following command:
firmware remove-activity blade 0 0 3 0
Related Links: