Format Of Possible File Exception Messages; File Example 1; File Suggested Action 1; File Example 2 - HP 3PAR StoreServ 7000 Troubleshooting Manual

Format of Possible file Exception Messages

File <nodeID> "Filesystem <filesystem> mounted on "<mounted on>" is over <count>% full"
File <nodeID> "Behavior altering file "<filename>" exists, created on <date&time>"
File <nodeID> "Dump or HBA core files found"
File <nodeID> "sr_mnt is full"
File -- "sr_mnt not mounted"
File -- "Admin Volume is not mounted"
File -- "An online upgrade is in progress"

file Example 1

File node:2

file Suggested Action 1

After understanding why the files are present, the file should be removed to prevent unwanted
behavior. As root on a node, remove the file using the UNIX rm command.
Known condition: some undesirable touch files are not being detected (bug 45661).

file Example 2

Component -----------Summary Description----------- Qty
File Admin Volume is not mounted

file Suggested Action 2

Each node has a file system link so that the admin volume can be mounted if that node is the master
node. This exception is reported if the link is missing or if the System Manager (sysmgr) is not
running at the time. For example, sysmgr might have been restarted manually, due to error or
during a change of master-nodes. If sysmgr was restarted, it tries to remount the admin volume
every few minutes.
Every node should have the following file system link so that the admin volume can be mounted,
should that node become the master node:
root@1001356-1~# onallnodes ls -l /dev/tpd_vvadmin
Node 0:
lrwxrwxrwx 1 root root 12 Oct 23 09:53 /dev/tpd_vvadmin -> tpddev/vvb/0
Node 1:
ls: /dev/tpd_vvadmin: No such file or directory
The corresponding alert when the admin volume is not properly mounted is as follows:
Message Code: 0xd0002
Severity : Minor
Type : PR transition
Message : The PR is currently getting data from the internal drive on node 1, not the admin volume. Previously recorded
alerts will not be visible until the PR transitions to the admin volume.
If a link for the admin volume is not present, it can be recreated by rebooting the node.

file Example 3

Component -----------Summary Description----------- Qty
File Nodes with Dump or HBA core files
Component ----Identifier----- ----Detailed Description------
File node:1
Behavior altering file "manualstartup" exists created on Oct 7 14:16
Dump or HBA core files found
1
1
Troubleshooting Storage System Components 45