HPUX :vmunix: vxfs: WARNING: msgcnt 3 mesg 014: V-2-14: vx_iget - inode table overflow

Error Message :
vmunix: vxfs: WARNING: msgcnt 1 mesg 014: V-2-14: vx_iget - inode table overflow
vmunix: vxfs: WARNING: msgcnt 1 mesg 014: V-2-14: vx_iget - inode table overflow
vmunix: vxfs: WARNING: msgcnt 2 mesg 014: V-2-14: vx_iget - inode table overflow
vmunix: vxfs: WARNING: msgcnt 2 mesg 014: V-2-14: vx_iget - inode table overflow
vmunix: vxfs: WARNING: msgcnt 3 mesg 014: V-2-14: vx_iget - inode table overflow
vmunix: vxfs: WARNING: msgcnt 3 mesg 014: V-2-14: vx_iget - inode table overflow
vmunix: vxfs: WARNING: msgcnt 4 mesg 014: V-2-14: vx_iget - inode table overflow

You can monitor the inode usage using vxfsstat command.
"/opt/VRTS/bin/vxfsstat -i / " command will provide you the inode cache statistics. If the inode usage is high, it's recommended to increase it.
And yes, if it's too inode cache is too low, it may cause system hang.
It may be possible that the inode cache filling up could cause the system to hang.  If a new process starts and cannot add needed entry into the inode cache, then I can see what that would cause an application to hang or cause the system to appear to hang.
 
# kctune vx_ninode
Tunable Value Expression Changes
vx_ninode 40000 40000 Immed
# kctune vx_ninode=131072
==> Update the automatic 'backup' configuration first? once
* The automatic 'backup' configuration has been updated.
* Future operations will ask whether to update the backup.
* The requested changes have been applied to the currently
running configuration.
Tunable Value Expression Changes
vx_ninode (before) 40000 40000 Immed
(now) 131072 131072
# kctune vx_ninode
Tunable Value Expression Changes
vx_ninode 131072 131072 Immed