Hang up F5 Device

[Mai_Tan_Linh_50]

Dear all;

i have a big problem.

i use F5 device for delegate DNS from DNS Server to F5 Device. ( web...)

i use sevice about one week. it hangs up. i don't know why it hangs up. when i reboot F5 device, it work normally.

Please help me to solve it

this is log file

ltm 05-22 08:56:31 wip : info mprov:2628:: Checking for and completing any disk management transactions:

ltm 05-22 08:56:31 wip : info mprov:2628:: Invoked as: /usr/bin/mprov.pl (pid=2628) --logicaldisk --boot --quiet

ltm 05-22 08:56:32 wip : info mprov:2633:: Checking for and completing any logical disk transactions:

ltm 05-22 08:56:32 wip : info mprov:2633:: Invoked as: /usr/bin/mprov.pl (pid=2633) --diskmgmt --boot --quiet

ltm 05-22 08:56:34 wip : info mprov:2638:: /bin/mkdir -p /dev/mprov/wom

ltm 05-22 08:56:34 wip : info mprov:2638:: /bin/mkdir -p /dev/mprov/ltm

ltm 05-22 08:56:34 wip : info mprov:2638:: /bin/mkdir -p /dev/mprov/vcmp

ltm 05-22 08:56:34 wip : info mprov:2638:: /bin/mkdir -p /dev/mprov/tmm

ltm 05-22 08:56:34 wip : info mprov:2638:: Invoked as: /usr/bin/mprov.pl (pid=2638) --boot --quiet

ltm 05-22 08:56:36 wip : info mprov:2638:: /bin/mount -t hugetlbfs none /dev/mprov/tmm 2>&1 1>/dev/null

ltm 05-22 08:56:36 wip : info mprov:2638:: /usr/bin/numactl --interleave=all /sbin/sysctl -w vm.nr_hugepages=1019

ltm 05-22 08:56:36 wip : info mprov:2638:: rm -vf /dev/shm/wam.umem_shared

ltm 05-22 08:56:36 wip : info mprov:2638:: rm -vf /dev/shm/avr.umem_shared

ltm 05-22 08:56:37 wip : info mprov:2638:: Provisioning successful.

ltm 05-22 08:56:37 wip : info mprov:2638:: /usr/bin/setdb Provision.Action none

ltm 05-22 08:56:39 wip : info mprov:3147:: Provisioning (legacy update) successful.

ltm 05-22 08:56:39 wip : info mprov:3147:: Invoked as: /usr/bin/mprov.pl (pid=3147) --legacy --quiet

ltm 05-22 08:56:56 info wip chmand[4025]: >>>********** AOM **********>>>

ltm 05-22 08:56:56 info wip chmand[4025]: <<<********** BIOS **********<<<

ltm 05-22 08:56:56 info wip chmand[4025]: Latest BIOS (ver 150) already installed

ltm 05-22 08:56:56 info wip chmand[4025]: Found BIOS images /usr/firmware/c102-bios-0332-01-150.bin.

ltm 05-22 08:56:56 info wip chmand[4025]: Looking for latest BIOS image in dir /usr/firmware

ltm 05-22 08:56:56 info wip chmand[4025]: Currently installed BIOS version: 150

ltm 05-22 08:56:56 info wip chmand[4025]: >>>********** BIOS **********>>>

ltm 05-22 08:56:56 info wip chmand[4025]: BIOS: F5 Platform: C102 OBJ-0332-01 BIOS (build: 150) Date: 02/16/12

ltm 05-22 08:56:56 info wip chmand[4025]: host = Mercury

ltm 05-22 08:56:56 info wip chmand[4025]: platform = C102

ltm 05-22 08:56:56 info wip chmand[4025]: probeBits = 0x20000001

ltm 05-22 08:56:56 info wip chmand[4025]: family = 0x90000000

ltm 05-22 08:56:56 info wip chmand[4025]: systype = 0x66

ltm 05-22 08:56:56 info wip chmand[4025]: Mercury: pfm detected from /BOARD: C102

ltm 05-22 08:56:56 info wip chmand[4025]: Found platform 'Mercury' in /PLATFORM

ltm 05-22 08:56:56 notice wip chmand[4025]: Checking for firmware update ...

ltm 05-22 08:57:01 info wip chmand[4025]: aom_flash: No CFE update required, exiting.

ltm 05-22 08:57:01 info wip chmand[4025]: Flash: CFE version: 1.5.1 (010501)

ltm 05-22 08:57:01 info wip chmand[4025]: Image: CFE version: 1.5.1 (010501)

ltm 05-22 08:57:03 info wip chmand[4025]: copying cpld image to AOM

ltm 05-22 08:57:06 info wip chmand[4025]: checking installed version:

ltm 05-22 08:57:06 info wip chmand[4025]: CPLD file expected md5sum: 2e4b79d2a48c76252bb8abc7ac8c546d

ltm 05-22 08:57:06 info wip chmand[4025]: CPLD file calculated md5sum: 2e4b79d2a48c76252bb8abc7ac8c546d

ltm 05-22 08:57:06 info wip chmand[4025]: verifying file copy:

ltm 05-22 08:57:12 info wip chmand[4025]: aom_flash: No CPLD update required, exiting.

ltm 05-22 08:57:12 info wip chmand[4025]: Cpld: v19 (base:0060)

ltm 05-22 08:57:12 info wip chmand[4025]: File: v19 (base:0060)

ltm 05-22 08:57:14 info wip chmand[4025]: MD5SUM check succeed.

ltm 05-22 08:57:14 info wip chmand[4025]: Check Image md5sum:

ltm 05-22 08:57:14 info wip chmand[4025]: Image Version: 10011103590000

ltm 05-22 08:57:16 notice wip chmand[4025]: Firmware check finished.

ltm 05-22 08:57:16 notice wip chmand[4025]: firmware update succeeded.

ltm 05-22 08:57:16 info wip chmand[4025]: <<<********** AOM **********<<<

ltm 05-22 08:57:16 info wip chmand[4025]: aom_flash: No Kernel update required, exiting.

ltm 05-22 08:57:16 info wip chmand[4025]: Flash Version: 10011103590000

ltm 05-22 08:57:20 notice wip overdog[4271]: Watchdog touch enabled.

ltm 05-22 08:57:20 info wip overdog[4271]: Overdog daemon startup.

ltm 05-22 08:57:20 info wip promptstatusd[4270]: Per-invocation log rate exceeded; throttling.

ltm 05-22 08:57:20 notice wip promptstatusd[4270]: semaphore tmm.running(1) held

ltm 05-22 08:57:20 warning wip promptstatusd[4270]: mcpd.running(1) held, wait for mcpd

ltm 05-22 08:57:20 notice wip promptstatusd[4270]:

ltm 05-22 08:57:20 notice wip promptstatusd[4270]: semaphore mcpd.running(1) held

ltm 05-22 08:57:20 notice wip promptstatusd[4270]:

ltm 05-22 08:57:20 notice wip promptstatusd[4270]: semaphore chmand.running(1) held

ltm 05-22 08:57:22 notice wip chmand[4752]: Host CPU subsystem reset caused by a Southbridge system reset

ltm 05-22 08:57:22 notice wip chmand[4752]: Host CPU subsystem reset - PCI reset asserted

ltm 05-22 08:57:22 notice wip chmand[4752]: AOM reset caused by other sources (standby power loss, JTAG or pushbutton reset)

ltm 05-22 08:57:22 notice wip chmand[4752]: CPLD indicates prior power-up or 3.3V standby power rail fault

ltm 05-22 08:57:22 notice wip chmand[4752]: CPLD indicates prior Host CPU subsystem power-off

ltm 05-22 08:57:22 notice wip chmand[4752]: CPLD indicates prior Host CPU subsystem reset

ltm 05-22 08:57:22 notice wip chmand[4752]: CPLD indicates prior AOM reset

ltm 05-22 08:57:22 info wip chmand[4752]: MCP initial connection not ready.

ltm 05-22 08:57:22 notice wip chmand[4752]: HAL sys service initialized.

ltm 05-22 08:57:22 notice wip chmand[4752]: Base service initialized.

ltm 05-22 08:57:22 notice wip chmand[4752]: Publish total 2 virtual Nitrox crypto devices.

ltm 05-22 08:57:22 notice wip chmand[4752]: Detected total 1 Nitrox crypto devices for total 2 Tmms.

ltm 05-22 08:57:22 info wip chmand[4752]: Initialized platform: C102

ltm 05-22 08:57:22 info wip chmand[4752]: host = Mercury

ltm 05-22 08:57:22 info wip chmand[4752]: platform = C102

ltm 05-22 08:57:22 info wip chmand[4752]: probeBits = 0x20000001

ltm 05-22 08:57:22 info wip chmand[4752]: family = 0x90000000

ltm 05-22 08:57:22 info wip chmand[4752]: systype = 0x66

ltm 05-22 08:57:22 info wip chmand[4752]: Mercury: pfm detected from /BOARD: C102

ltm 05-22 08:57:22 info wip chmand[4752]: Found platform 'Mercury' in /PLATFORM

ltm 05-22 08:57:22 notice wip chmand[4752]: Starting ChassisManager (chmand)

ltm 05-22 08:57:23 notice wip mcpd[4339]: User requested database size set to 512MB

Thanks for view

Klien.Mai

[nitass]

have you opened a support case? i think it had better open a case.

[Mai_Tan_Linh_50]

thanks for respond Nitass. I will open a case support.

Klien.Mai

[Hamish]

Only time I've had this happen it was a known issue where sometimes the swapspace doesn't get created... The RAM fills up, no swap and box goes down too quick to even panic. The official fix is to reinstall and restore your backups. However you could also probably do the swapspace creation by hand if you're good with Linux. H

[AmarC_141952]

Mai Tan Linh , What solution did you get from your case ?

[Mai_Tan_Linh_50]

Dear AmarC; I opened a case support. After that, a supporter of F5 Comp came our office and checked thier fail F5 device. The problems were some errors hardware in my F5 box. Then, they changed to me a new F5 device. that's all Thanks Klien.Mai