Differences

This shows you the differences between two versions of the page.

--- infoblox_nios:misc [2024/10/01 06:58] – bstafford
+++ infoblox_nios:misc [2025/09/19 08:50] (current) – [Disk] bstafford
@@ Line 27: / Line 27: @@
 Enter the command ‘reset database’ from the Emergency prompt to erase and reset the database on the appliance (NOTE: ***All previous data on the appliance will be lost and cannot be recovered***).
+===== Grid Communication =====
+NIOS uses the Grid VPN for syncing the relevant bits of the OneDB database as well as upgrade image distribution and NTP sync to GM.
 ===== Replacing NIOS Member =====
 [[https://support.infoblox.com/s/article/2896|Infoblox hardware replacement/swaps for NIOS]]
@@ Line 98: / Line 100: @@
 ===== Memory Footprint Usage=====
 Recursive client queries take up about 20Kb per query.
-===== Disable Telemetry ======
-BloxConnect is a useful source of telemetry to help Infoblox develop and improve NIOS ([[https://insights.infoblox.com/resources-datasheets/infoblox-datasheet-infoblox-bloxconnect|datasheet]]). It is recommended to enable it as it also allows your account team at Infoblox to provide better service by providing them a summary of the features you have enabled.
-<code>set bloxconnect disable/enable</code>
-<code>show bloxconnect</code>
-  - In the NIOS GUI Mode → Grid Properties Editor or Grid Member properties→ Toggle Advanced Mode → CSP Config → Advanced (Tab) and uncheck the "BloxConnect Data Collection and Opt-in Notice"
-  - Then log into NIOS CLI and run these commands
-    - ''set maintenancemode''
-    - ''set cloud off''
 ===== Latency =====
@@ Line 124: / Line 118: @@
 You do not need to resize previous 250 GB images to upgrade NIOS. Changing the disk size has no effect on the previously created VM partitions or file systems. You can only change the disk size when the VM is first created using a resizable image.
+[[https://docs.infoblox.com/space/nios90/1367016071/VM+Disk+Partition|Documentation]]
+Infoblox uses an "A/B" upgrade scheme. There are two root partitions and two storage partitions. On an upgrade, the "alternate" partitions are populated must be rebooted. They flip back and forth for successive upgrades. (This is also what allows a revert to the previous version when necessary.)
+ The 500 GB disk size partition is as follows:
+<code>NAME   PARTLABEL   SIZE
+sda                  500 GB
+|-sda1 root1         8 GB
+|-sda2 root2         8 GB
+|-sda3 boot          1 GB
+|-sda4 config        1 GB
+|-sda5 storage1    229 GB
+|-sda6 storage2    229 GB
+\-sda7 swap         24 GB</code>
+The formula for storage size is: (disk - (2*8+2*1+24))/2
+That is, the disk size minus the space for root1, root2, boot, config, and swap, divided by half.
+For a 500 GB disk: (500-(2*8+2*1+24))/2 = 229
+For a 250 GB disk, (250-(2*8+2*1+24))/2 = 104. That is, each storage partition will be 104 GB.
@@ Line 132: / Line 149: @@
 | 250G | ~104Gb |
 | 500G | ~229Gb |
+VM using default 500GB disk image
+<code>Infoblox > show disk
+                            Capacity  Available     Use%
+Disk space for data:             225G        200G      7%</code>
+VM using 150GB resizable image
+<code>Infoblox > show disk
+                            Capacity  Available     Use%
+Disk space for data:             53G        26G      49%</code>
+VM using default 500GB disk image + 1TB reporting disk
+<code>Infoblox > show disk
+                            Capacity  Available     Use%
+Disk space for data:             225G        192G    11%
+Disk space for reporting:       1007G        950G     1%</code>