Jump to content

BIG-IQ upgrade to 8.2.x causes var to run out of space


Cowboy Denny
 Share

Recommended Posts

I've been trying to upgrade from BIG-IQ 8.1.0.2 up to 8.2.x but without much luck since whenever I try to upgrade var runs out of space.  One mistake I did was not leverage the LARGE .ova when deploying BIG-IQ to the CM and the DCD's which if I need to rebuild, I will change this since the disk is 500GB on large vs 95GB on standard.

I've run across this F5 article on how to prep a partition on the CM for the upgrade which I'll do in a few weeks.

Something to note: your cluster MUST BE green.

CLUSTER

curl -s -u admin:admin --insecure https://localhost:9200/_cluster/health?pretty

 

CHECK STATUS OF NODES (CM and DCDs)

curl -s -u admin:admin --insecure https://localhost:9200/_cat/nodes?v

Asterick tells you which one is master and they must all match same device must be master

 

curl -s -u admin:admin --insecure https://localhost:9200/_cluster/settings | jq .

change minimum_master_nodes to 5 from 3

 

ALWAYS reboot DCDs first then CM

curl -s localhost:9210/_cat/indices?v

 

ping 10.47.208.45 | while read pong; do echo "$(date): $pong"; done

Link to comment
Share on other sites

  • 4 weeks later...

Sometimes it helps to alter /etc/biq_daemon_provision.json

Default settings

    "elasticsearch": {
      "active": true,
      "memory_allocation": {
        "SYS_4GB": "100m",
        "SYS_8GB": "200m",
        "SYS_16GB": "500m",
        "SYS_32GB": "2600m",
        "SYS_64GB": "8000m",
        "SYS_96GB": "10000m",
        "SYS_128GB": "12000m"
      }
    },

New settings

    "elasticsearch": {
      "active": true,
      "memory_allocation": {
        "SYS_4GB": "100m",
        "SYS_8GB": "200m",
        "SYS_16GB": "500m",
        "SYS_32GB": "1600m",
        "SYS_64GB": "3200m",
        "SYS_96GB": "4800m",
        "SYS_128GB": "6400m"
      }
    },

bigstart restart restjavad

bigstart restart elasticsearch

curl -s localhost:9210/_cat/indices?v

Link to comment
Share on other sites

If you installed the new version on HD1.2 and the original version is on HD1.1 to rollback you just type:

tmsh reboot volume HD1.1

Then when it finally comes back online delete HD1.1

tmsh delete /sys software volume HD1.2

Before you reinstall 8.2.0 on HD1.2 make sure your cluster is green

curl -s localhost:9200/_cluster/health?pretty

{
  "cluster_name" : "a6f1a0d6-c57a-40bf-8037-eef75a6b7f5b",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 9,
  "number_of_data_nodes" : 8,
  "active_primary_shards" : 1567,
  "active_shards" : 3140,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 100.0

If it's green, then continue to reinstall the image

cd /shared/images

tmsh install /sys software image BIG-IQ-8.2.0-0.0.310.iso volume HD1.2 create-volume

tmsh show sys software status

Once it shows fully installed, reboot to the new image

tmsh reboot volume HD1.1

 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...