Author: krrunch

Posted on

Misc: Resynchronise the HP 2.4 GHz Wireless Optical Mouse FHA3510

Totally off topic but if you’ve had the misfortune to have one of these stop working on you then never fear as the solution is below.

Symptoms:

The USB receiver is inserted and installs fine but one day the mouse appears to give up the ghost and no longer connect.

Cause:

The mouse has become disassociated with the receiver, there are no obvious “sync” buttons on the mouse. As th mouse functions on 2.4 GHz, it may become disrupted by anything else using this frequency band e.g. microwaves, bluetooth, cordless phones etc.

Fix:

Set the mouse close to the inserted USB receiver and hold down the button just behind the wheel – it has a little paper icon on it, as shown in the image below. The blue wheel LED will start to flash – keep holding the button until it has stopped blinking – your mouse is now functional again!

HP FHA3510 Mouse

 

Posted on

Checkpoint: Best Practice Kernel Parameters for ClusterXL Stability

This article details how to configure the best practice kernel parameters to ensure ClusterXL stability.

It is recommended to set ALL of those values on your cluster – also see sk92723 on Cluster flapping prevention.

Make sure the changes to the kernel parameters are performed on both members!

To test (will not survive a reboot):

fw ctl set int fwha_freeze_state_machine_timeout 200
fw ctl set int fwha_policy_update_timeout_factor 3
fw ctl set int fwha_pnote_timeout_mechanism_monitor_cpu 1
fw ctl set int fwha_pnote_timeout_mechanism_cpu_load_limit 80
fw ctl set int fwha_if_connectivity_tolerance 3

Once you are happy with the above you can enter the values into the $FWDIR/boot/modules/fwkern.conf file to make sure that the parameters stick after a reboot.

If the fwkern.conf doesn’t exist create it using the “touch” command:

[Expert@fw-trinity:0] # touch $FWDIR/boot/modules/fwkern.conf

Using the vi editor, insert the below commands into the fwkern.conf file:
fwha_freeze_state_machine_timeout = 200
fwha_policy_update_timeout_factor = 3
fwha_pnote_timeout_mechanism_monitor_cpu = 1
fwha_pnote_timeout_mechanism_cpu_load_limit = 80
fwha_if_connectivity_tolerance = 3

Posted on

Checkpoint: Using “dmidecode” to Find the Appliance Model of a UTM-1

This article details how to use “dmidecode” to find out your Checkpoint UTM-1’s model number.

Dmidecode reports information about your system’s hardware as described in your system BIOS according to the SMBIOS/DMI standard  – see here for a sample output.

This information typically includes system manufacturer, model name, serial number, BIOS version, asset tag as well as a lot of other details of varying level of interest and reliability depending on the manufacturer. This will often include usage status for the CPU sockets, expansion slots (e.g. AGP, PCI, ISA) and memory module slots, and the list of I/O ports (e.g. serial, parallel, USB).

This also works on a number of linux-based operating systems including (but not limited to):

  • Linux i386, x86-64, ia64
  • FreeBSD i386, amd64
  • NetBSD i386, amd64
  • OpenBSD i386, amd64
[Expert@fw-trinity:0]# /usr/sbin/dmidecode | grep "Product Name"
Product Name: U-5-00

Here is the Product Name dmidecode table for the UTM-1/Power-1 appliances:

DMI Code: Model of UTM:
C2_UTM UTM-1 450 Appliance
C6P_UTM UTM-1 2050 Appliance
C6_UTM UTM-1 1050 Appliance
P-10-00 Power-1 5070 Appliance
P-20-00 Power-1 9070 Appliance
U-10-00 UTM-1 270 Appliance
U-15-00 UTM-1 570 Appliance
U-20-00 UTM-1 1070 Appliance
U-30-00 UTM-1 2070 Appliance
U-40-00 UTM-1 3070 Appliance
U-5-00 UTM-1 130 Appliance