Hang up F5 Device

Question

Dear all;&nbsp;
i have a big problem.&nbsp;
i use F5 device for delegate DNS from DNS Server to F5 Device. ( web...)&nbsp;
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. &nbsp;
Please help me to solve it &nbsp;
this is log file &nbsp;
 &nbsp;
ltm 05-22 08:56:31  wip : info mprov:2628:: Checking for and completing any disk management transactions: &nbsp;
ltm 05-22 08:56:31  wip : info mprov:2628:: Invoked as: /usr/bin/mprov.pl (pid=2628) --logicaldisk --boot --quiet &nbsp;
ltm 05-22 08:56:32  wip : info mprov:2633:: Checking for and completing any logical disk transactions: &nbsp;
ltm 05-22 08:56:32  wip : info mprov:2633:: Invoked as: /usr/bin/mprov.pl (pid=2633) --diskmgmt --boot --quiet &nbsp;
ltm 05-22 08:56:34  wip : info mprov:2638:: /bin/mkdir -p /dev/mprov/wom &nbsp;
ltm 05-22 08:56:34  wip : info mprov:2638:: /bin/mkdir -p /dev/mprov/ltm &nbsp;
ltm 05-22 08:56:34  wip : info mprov:2638:: /bin/mkdir -p /dev/mprov/vcmp &nbsp;
ltm 05-22 08:56:34  wip : info mprov:2638:: /bin/mkdir -p /dev/mprov/tmm &nbsp;
ltm 05-22 08:56:34  wip : info mprov:2638:: Invoked as: /usr/bin/mprov.pl (pid=2638) --boot --quiet &nbsp;
ltm 05-22 08:56:36  wip : info mprov:2638:: /bin/mount -t hugetlbfs none /dev/mprov/tmm 2&gt;&amp;1 1&gt;/dev/null &nbsp;
ltm 05-22 08:56:36  wip : info mprov:2638:: /usr/bin/numactl --interleave=all /sbin/sysctl -w vm.nr_hugepages=1019 &nbsp;
ltm 05-22 08:56:36  wip : info mprov:2638:: rm -vf /dev/shm/wam.umem_shared &nbsp;
ltm 05-22 08:56:36  wip : info mprov:2638:: rm -vf /dev/shm/avr.umem_shared &nbsp;
ltm 05-22 08:56:37  wip : info mprov:2638:: Provisioning successful. &nbsp;
ltm 05-22 08:56:37  wip : info mprov:2638:: /usr/bin/setdb Provision.Action none &nbsp;
ltm 05-22 08:56:39  wip : info mprov:3147:: Provisioning (legacy update) successful. &nbsp;
ltm 05-22 08:56:39  wip : info mprov:3147:: Invoked as: /usr/bin/mprov.pl (pid=3147) --legacy --quiet &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: &gt;&gt;&gt;********** AOM **********&gt;&gt;&gt; &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: &lt;&lt;&lt;********** BIOS **********&lt;&lt;&lt; &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: Latest BIOS (ver 150) already installed &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: Found BIOS images /usr/firmware/c102-bios-0332-01-150.bin. &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: Looking for latest BIOS image in dir /usr/firmware &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: Currently installed BIOS version: 150 &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: &gt;&gt;&gt;********** BIOS **********&gt;&gt;&gt; &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: BIOS: F5 Platform: C102 OBJ-0332-01 BIOS (build: 150) Date: 02/16/12 &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: host         = Mercury &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: platform     = C102 &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: probeBits    = 0x20000001 &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: family       = 0x90000000 &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: systype      = 0x66 &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: Mercury: pfm detected from /BOARD: C102 &nbsp;
ltm 05-22 08:56:56 info wip chmand[4025]: Found platform 'Mercury' in /PLATFORM &nbsp;
ltm 05-22 08:56:56 notice wip chmand[4025]: Checking for firmware update ... &nbsp;
ltm 05-22 08:57:01 info wip chmand[4025]: aom_flash: No CFE update required, exiting. &nbsp;
ltm 05-22 08:57:01 info wip chmand[4025]: Flash: CFE version: 1.5.1 (010501) &nbsp;
ltm 05-22 08:57:01 info wip chmand[4025]: Image: CFE version: 1.5.1 (010501) &nbsp;
ltm 05-22 08:57:03 info wip chmand[4025]: copying cpld image to AOM &nbsp;
ltm 05-22 08:57:06 info wip chmand[4025]: checking installed version: &nbsp;
ltm 05-22 08:57:06 info wip chmand[4025]:   CPLD file expected   md5sum: 2e4b79d2a48c76252bb8abc7ac8c546d &nbsp;
ltm 05-22 08:57:06 info wip chmand[4025]:   CPLD file calculated md5sum: 2e4b79d2a48c76252bb8abc7ac8c546d &nbsp;
ltm 05-22 08:57:06 info wip chmand[4025]: verifying file copy: &nbsp;
ltm 05-22 08:57:12 info wip chmand[4025]: aom_flash: No CPLD update required, exiting. &nbsp;
ltm 05-22 08:57:12 info wip chmand[4025]: Cpld: v19 (base:0060) &nbsp;
ltm 05-22 08:57:12 info wip chmand[4025]: File: v19 (base:0060) &nbsp;
ltm 05-22 08:57:14 info wip chmand[4025]: MD5SUM check succeed. &nbsp;
ltm 05-22 08:57:14 info wip chmand[4025]: Check Image md5sum: &nbsp;
ltm 05-22 08:57:14 info wip chmand[4025]: Image Version: 10011103590000 &nbsp;
ltm 05-22 08:57:16 notice wip chmand[4025]: Firmware check finished. &nbsp;
ltm 05-22 08:57:16 notice wip chmand[4025]: firmware update succeeded. &nbsp;
ltm 05-22 08:57:16 info wip chmand[4025]: &lt;&lt;&lt;********** AOM **********&lt;&lt;&lt; &nbsp;
ltm 05-22 08:57:16 info wip chmand[4025]: aom_flash: No Kernel update required, exiting. &nbsp;
ltm 05-22 08:57:16 info wip chmand[4025]: Flash Version: 10011103590000 &nbsp;
ltm 05-22 08:57:20 notice wip overdog[4271]: Watchdog touch enabled. &nbsp;
ltm 05-22 08:57:20 info wip overdog[4271]: Overdog daemon startup. &nbsp;
ltm 05-22 08:57:20 info wip promptstatusd[4270]: Per-invocation log rate exceeded; throttling. &nbsp;
ltm 05-22 08:57:20 notice wip promptstatusd[4270]: semaphore tmm.running(1) held &nbsp;
ltm 05-22 08:57:20 warning wip promptstatusd[4270]: mcpd.running(1) held, wait for mcpd &nbsp;
ltm 05-22 08:57:20 notice wip promptstatusd[4270]:  &nbsp;
ltm 05-22 08:57:20 notice wip promptstatusd[4270]: semaphore mcpd.running(1) held &nbsp;
ltm 05-22 08:57:20 notice wip promptstatusd[4270]:  &nbsp;
ltm 05-22 08:57:20 notice wip promptstatusd[4270]: semaphore chmand.running(1) held &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: Host CPU subsystem reset caused by a Southbridge system reset &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: Host CPU subsystem reset - PCI reset asserted &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: AOM reset caused by other sources (standby power loss, JTAG or pushbutton reset) &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: CPLD indicates prior power-up or 3.3V standby power rail fault &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: CPLD indicates prior Host CPU subsystem power-off &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: CPLD indicates prior Host CPU subsystem reset &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: CPLD indicates prior AOM reset &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: MCP initial connection not ready. &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: HAL sys service initialized. &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: Base service initialized. &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: Publish total 2 virtual Nitrox crypto devices. &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: Detected total 1 Nitrox crypto devices for total 2 Tmms. &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: Initialized platform: C102 &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: host         = Mercury &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: platform     = C102 &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: probeBits    = 0x20000001 &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: family       = 0x90000000 &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: systype      = 0x66 &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: Mercury: pfm detected from /BOARD: C102 &nbsp;
ltm 05-22 08:57:22 info wip chmand[4752]: Found platform 'Mercury' in /PLATFORM &nbsp;
ltm 05-22 08:57:22 notice wip chmand[4752]: Starting ChassisManager (chmand) &nbsp;
ltm 05-22 08:57:23 notice wip mcpd[4339]: User requested database size set to 512MB &nbsp;
 &nbsp;
Thanks for view &nbsp;
 &nbsp;
Klien.Mai&nbsp;
 &nbsp;

nitass · Answer

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

mai_tan_linh_50 · Answer

thanks for respond Nitass. I will open a case support.&nbsp;
Klien.Mai &nbsp;

hamish · Answer

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. 
&nbsp;  
&nbsp; H

amarc_141952 · Answer

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

mai_tan_linh_50 · Answer

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

Forum Discussion

Hang up F5 Device

5 Replies

Recent Discussions

Port Group on F5OS network setting

F5Access | MacOS Sonoma

Rewrite uri translation not working

Chrome V 124+ on MacOS - Virtual Server Access Issue

Transaction looks successful but file not downloading

Related Content

Hanging with DevCentral at RSA Conference 2023

Device Management

Device ID not working for IOS iPhone devices

Security for IoT Devices and Why It’s Important

what's Device ID in asm?