Virtual SAN: Suppress ‘Datastore Usage on Disk’ Alarm

KB ID 0001527

Problem

While deploying a HPE StoreVirtual VSA this week. We noticed all the local Datastore were showing an ‘Alarm’. If you are unfamiliar with Virtual SANs, then you give all the LOCAL Storage to them, which then gets ‘aggregated’ and provided back to the host(s) as fault tolerant clustered storage, like so;

Which is great, but the VMware hosts just see that their LOCAL Datastore(s) are full, and they alarm;

Solution

Whilst in ‘Datastore View’: Create a ‘Local Datastore Folder‘ and add all you local datastore(s) to that, then create a ‘Virtual Datastore Folder’ and add all your virtual/clustered datastore(s) to that. Select the vCenter > Monitor > Issues > Alarm Definitions > Locate the ‘Datastore usage on disk’ alarm and Edit it. 

Untick: Enable this alarm.

You will recreate this alarm again below, so take a note all ALL its settings;

Now select your Virtual Datastore folder > Monitor > Issues > Alarm Definitions > Add > Recreate the alarm again, Note: I’ve called it ‘Virtual-Datastore-Usage-On-Disk‘.

Have a coffee, refresh the page, the alarms should have gone.

Related Articles, References, Credits, or External Links

NA

VMware error on HP Proliant “Host Baseboard Management Controller status”

KB ID 0000418 

Problem

Saw this today on a HP Proliant DL380 G7 Server.

Solution

1. It’s a simple one to solve, the server was built with the HP ESXi build, and the management agents are complaining because the iLO is not connected to the network.

2. When you connect the iLO socket to the network the alarm should change as shown below.

3. Once you have connected or disabled it you can reset the alarm.

4. Take the opportunity to log in and configure the iLO. Access via an internet browser (it will get a DHCP address by default, you can set a static IP address by entering the iLO setup at boot (see disabling iLO section below)).

5. The user name is Administrator (capital A) and the password will be either on a pull out tab on the front of the server, or a brown cardboard label tied to the front of the server (you did keep that didn’t you!), or on a brown sticker on top of the server chassis. On certain models HP also stick this information under the server lid.

6. Then you can log in and configure.

Disable the iLO

1. If you do not want to use the iLO then you can disable it (I cant think why you would want to, because its a handy piece of kit, but heres how to do it.)

2. Reboot the server, and when prompted press F8 to enter the iLO setup.

3. Settings > Configure.

4. These are the default settings, use the cursor keys to select and the space bar to enable/disable the options.

5. All disabled.

 

Related Articles, References, Credits, or External Links

NA

Juniper SRX Firewall Alarm Light Lit

KB ID 0000993

Problem

I noticed the alarm light was lit amber on an SRX240 Juniper firewall.

Solution

This will not serve as a solution to every alarm on the SRX, but it should point you where to look, and show you how to resolve the two problems I identified on my firewall.

View SRX Alarm Status in J-Web

The status is displayed on the ‘Dashboard’ tab, here you can see I’ve got two minor alarms.

View SRX Alarm Status at Command Line

If connected via console cable or SSH.

[box]

root@FW-02> show system alarms
2 alarms currently active
Alarm time Class Description
2014-08-26 21:52:14 GMT Minor Autorecovery information needs to be saved
2014-08-26 21:52:14 GMT Minor Rescue configuration is not set

[/box]

 

Juniper SRX – Rescue Information Is Not Set (J-Web)

This one is easy to fix in J-Web, Maintain > Config Management Rescue > Set Rescue Configuration.

Then click OK.

Juniper SRX – Rescue Information Is Not Set (Command Line)

To do the same via console cable or SSH.

[box]

root@FW-02> request system configuration rescue save

[/box]

Juniper SRX – Autorecovery Information Needs To Be Saved (Command Line)

Despite my best efforts I could not locate how to do this in the GUI, so I had to use command line.

[box]

root@FW-02> show system alarms
1 alarms currently active
Alarm time Class Description
2014-08-26 21:52:14 GMT Minor Autorecovery information needs to be saved

root@FW-02> request system autorecovery state save
Saving config recovery information
Saving license recovery information
Saving BSD label recovery information

root@FW-02>

[/box]

Related Articles, References, Credits, or External Links

NA