Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
Scott_Paisley
Advisor
Jump to solution

API disabled on R81 management server

We recently upgraded both our management servers to R81

One is a hardware appliance, one is a VM.

On the VM, the API status appears as Unknown during start up, and then shows as disabled.

On the hardware, it shows as enabled.

We can restart it on the VM and it runs fine, but why does it not start automatically?

0 Kudos
1 Solution

Accepted Solutions
Scott_Paisley
Advisor

TAC were able to resolve the issue.

There was a problem with one of the files on the server

View solution in original post

20 Replies
_Val_
Admin
Admin
0 Kudos
Scott_Paisley
Advisor

Yes. The documentation mentions enabling the API, then says it is enabled or disabled automatically. We have more than 4GB RAM.

This was all working prior to the R81 upgrade.

0 Kudos
_Val_
Admin
Admin

The VM MGMT station, is it secondary? It yes, please perform the failover, make sure API is once again enabled via SmartConsol, publish session, and run api restart on CLI

0 Kudos
_Val_
Admin
Admin

Also, API should only be active on your primary/active server. That might be the main cause of the observed situation.

0 Kudos
Scott_Paisley
Advisor

We are running on our Active/Secondary server.

This worked fine on R80.40

0 Kudos
_Val_
Admin
Admin

Please elaborate

0 Kudos
Scott_Paisley
Advisor

We failed over to our secondary management server, so it is currently the active box.

We have been running that way for over a year. On R80.40 the API started automatically. On R81 it does not.

0 Kudos
_Val_
Admin
Admin

So, if I understand correctly, you are currently running the secondary management as active. Did you try to re-activate API on it, from SmartConsole, as mentioned above?

Did you try enabling api from the CLI? Run the following:

api start

api reconfigure

api restart

 

and check if it stays UP after those commands. 

0 Kudos
Scott_Paisley
Advisor

There is no enable option in smartconsole. see screenshot attached.

We can start from the CLI. I will try the commands listed

0 Kudos
_Val_
Admin
Admin

You are right, in R81 the API start is automatic. Did you originally install your VM with just 4 GB of RAM?

0 Kudos
Scott_Paisley
Advisor

No, it always had more than 8GB

0 Kudos
_Val_
Admin
Admin

Okay, try the CLI. If it is still disabled after reboot, please open a support call.

0 Kudos
Scott_Paisley
Advisor

No change. After a restart the API state is disabled until I restart it manually.

0 Kudos
_Val_
Admin
Admin

Okay, that's too bad. Please take it with TAC

0 Kudos
Omer_Kleinstern
Employee
Employee

Hi @Scott_Paisley ,

Can you run the following commands:

mgmt_cli show api-settings -r true -d "System Data" -f json | jq '."automatic-start"'

$CPDIR/bin/cpprod_util CPPROD_GetValue Products MGMTAPI 1
 
Thanks,
Omer
0 Kudos
Scott_Paisley
Advisor

# mgmt_cli show api-settings -r true -d "System Data" -f json | jq '."automatic-start"'
true

 

# $CPDIR/bin/cpprod_util CPPROD_GetValue Products MGMTAPI 1
Failed to find the value

0 Kudos
Omer_Kleinstern
Employee
Employee

Please open a TAC case for further investigation.

0 Kudos
Scott_Paisley
Advisor

TAC were able to resolve the issue.

There was a problem with one of the files on the server

PhoneBoy
Admin
Admin

What files did they precisely fix?
Did they give you an SK?

0 Kudos
Scott_Paisley
Advisor

/opt/CPshrd-R81/registry/HKLM_registry.data

They gave me a custom file, no SK.

Leaderboard

Epsum factorial non deposit quid pro quo hic escorol.

Upcoming Events

    CheckMates Events