To enable the pool member that has been forced offline via a BIG-IQ device,
send a PATCH request with this body to
https://BIGIQ_IP_Address/mgmt/shared/resolver/device-groups/GroupName/devices/BIGIP_Device/rest-proxy/mgmt/tm/ltm/pool/PoolName/members/Member:
    {
    "state": "user-up",
    "session": "user-enabled"
    }
              
To disable it instead, send this body:
    {
    "state": "user-up",
    "session": "user-disabled"
    }

"If the identified BIG-IP has been recently upgraded, make sure that correct
REST framework is installed. To update the framework, use the following procedure.
1. Go to the BIG-IQ Device module, hover over the device entry. Click the gear icon and
select properties.
2. Scroll to the bottom of the page, and select the 'Update
Framework On Rediscover' check box.
3. Enter the credentials, and at the top of the page, click Rediscover.
4. This pushes the newer REST framework to the BIG-IP system.
For a VIPRION system, each blade is represented as a separate managed device in BIG-IQ
system, and so each upgraded blade must have the current REST framework pushed to it.
The high CPU issue should resolve itself after the tasks have time to complete."

"1. Identify the provider:
  restcurl cm/system/authn/providers/radius
or
  restcurl cm/system/authn/providers/ldap.
2. Find the users with no name restcurl
  cm/system/authn/providers/radius/3918ff0c-a6c4-470c-a7d7-09f91648a084/users
2. Delete the user with no name:
  restcurl -X DELETE cm/system/authn/providers/radius/3918ff0c-a6c4-470c-a7d7-09f91648a084/users/ed2d2dca-e78e-47ea-b8d9-f14f91623d13"

"There are two workarounds for this situation. The first (A) is the recommended
workaround.
Workaround A.) With this solution, communication (and device discovery) is
restored and socket reuse is disabled for the BIG-IQ system. Disabling reuse can
impact performance, but future changes to the authentication certificate do not
disable management for the device.
1. Using SSH, log in to the BIG-IQ system as root.
2. Stop restjavad by typing the command, bigstart stop restjavad.
3. In /etc/bigstart/scripts/restjavad, edit ARGS=""--port=8100 ..."" to read as follows:
ARGS=""--port=8100 --isConnectionReUseDisabled=true ..."".
4. Start restjavad by
typing: bigstart start restjavad.
Workaround B.) With this solution, communication
(and device discovery) is restored, but future changes to the managed device's
authentication certificate again disables device management and requires a restjavad
restart.
1. Using SSH, log in to the BIG-IQ system as root.
2. Start restjavad by typing the command, bigstart start restjavad."

1) On the High Availability panel, delete the HA peer and any associated devices.
2) From the command line, type the following command to delete the local device:
curl -X DELETE http://localhost:8100/shared/resolver/device-groups/cm-shared-all-big-iqs/devices
3) To remove the existing certificates and restart the service, type the following commands on each device:
bigstart stop restjavad; rm -rf /shared/em/ssl.crt/*.*; rm -rf /shared/em/ssl.key/*.*;bigstart start restjavad"

1) On a volume running the previous version of BIG-IQ, verify the backup script is executable from
SSH by typing the following:  ""chmod 555 backup_analytics_index,"" and then run it by typing ""./backup_analytics_index.""
This will stop REST services and zip the analytics indexes to the /shared directory, then restart REST services.

2) Once the upgrade has been applied to the new volume, make sure the restore backup script is executable using the
same method as noted above. Run the script with ""./restore_analytics_index.""
This will stop REST services again, check for any new indexes and prompt for deletion if there are conflicting indexes
(a merge of the indexes is not possible currently).

3) If there are no conflicts, the BIG-IQ system restores the backup file from the /shared to the /var/config/rest/analytics
directory on the newly upgraded volume and restarts REST services."

"[I][0][04 Jun 2015 06:32:21 UTC][com.f5.rest.common.WellKnownPorts][setMachineId] machineId set to 10f97dc6-b31c-4e31-8687-66288f92a1a1
[I][1][04 Jun 2015 06:32:22 UTC][RestServer][bindServerChannel] Now accepting connections on port 8100
[I][2][04 Jun 2015 06:32:22 UTC][RestWorkerHost][start] isTmosPlatform = true, isSslEnabled = false, isConnectionReUseDisabled = false, outboundConnectionTimeoutSeconds = 60 isPublic = false isHostInInsecureTestMode = false
[I][3][04 Jun 2015 06:32:22 UTC][GroomerTable][<init>] * hi=10000000 lo=7500000
[SEVERE][4][04 Jun 2015 06:32:22 UTC][RestWorkerHost][main] java.lang.NoSuchFieldError: LUCENE_47
at com.f5.rest.workers.storage.LuceneStorageRequestProcessor.<clinit>(LuceneStorageRequestProcessor.java:60)
at com.f5.rest.workers.storage.StorageWorker.createLuceneStorageProcessor(StorageWorker.java:107)
at com.f5.rest.workers.storage.StorageWorker.<init>(StorageWorker.java:94)
at com.f5.rest.workers.RestWorkerHost.start(RestWorkerHost.java:398)
at com.f5.rest.workers.RestWorkerHost.main(RestWorkerHost.java:335)


Jun  4 06:32:43 ORLHFL01SWL-Z-MSCF-02 emerg logger: Re-starting restjavad
Jun  4 06:32:45 ORLHFL01SWL-Z-MSCF-02 emerg logger: Re-starting restjavad
Jun  4 06:32:47 ORLHFL01SWL-Z-MSCF-02 emerg logger: Re-starting restjavad
Jun  4 06:32:49 ORLHFL01SWL-Z-MSCF-02 emerg logger: Re-starting restjavad
Jun  4 06:32:51 ORLHFL01SWL-Z-MSCF-02 emerg logger: Re-starting restjavad
Jun  4 06:32:52 ORLHFL01SWL-Z-MSCF-02 emerg logger: Re-starting restjavad
Jun  4 06:32:54 ORLHFL01SWL-Z-MSCF-02 emerg logger: Re-starting restjavad
Jun  4 06:32:56 ORLHFL01SWL-Z-MSCF-02 emerg logger: Re-starting restjavad" restjavad restarts in BIG-IP Framework upgrade from BIG-IQ UI

"Manually remove lucene jars using the below process,
   a. mount -o remount,rw /usr
   b. rm -rvf /usr/share/java/lucene-analyzers-common-4.2.1.jar
   c. rm -rvf /usr/share/java/lucene-core-4.2.1.jar
   d. mount -o remount,ro /usr"

1. Identify the BIG-IQ device reference.

[root@localhost:Active] config # restcurl -s -u <admin_user_name>:<admin_password> https://localhost/mgmt/shared/resolver/device-groups/cm-shared-all-big-iqs/devices'?$filter=mcpDeviceName+eq+%27/Common/localhost%27'
{
"selfLink": "https://localhost/mgmt/shared/resolver/device-groups/cm-shared-all-big-iqs/devices",
"totalItems": 1,
"items": [
{
<snip>
"selfLink": "https://localhost/mgmt/shared/resolver/device-groups/cm-shared-all-big-iqs/devices/e4d49be3-55ea-4fb9-a269-967948c05b46"
}
],
"generation": 7,
"kind": "shared:resolver:device-groups:devicegroupdevicecollectionstate",
"lastUpdateMicros": 1456423719860331
}

2. Use the value from "selfLink" attribute as present in "items" field as "deviceReference".

3. Trigger manual refresh for interfaces for Local BIG-IQ device.

[root@localhost:Active] config # restcurl -X POST -d '{ "configPaths": [{"icrObjectPath": "cloud/net/interface"}], "deviceReference": { "link": "http://localhost/shared/resolver/device-groups/cm-shared-all-big-iqs/devices/e4d49be3-55ea-4fb9-a269-967948c05b46" } }' cm/shared/config/refresh-current-config