"I/O error: 6" and "ERROR: generating vxfentab for cps cpsServer" appear when running cpsadm during the CPS fencing configuration
Article ID: 100031623
Updated On:
Description
Error Message
[ Jul 2 14:37:24 Enabled. ][ Jul 2 14:37:24 Executing start method ("/lib/svc/method/vxfen start"). ]
Starting vxfen..
I/O error: 6
ERROR: generating vxfentab for cps cps1.
[ Jul 2 14:37:25 Method "start" exited with status 1. ]
Cause
This behavior has been observed on Solaris 11 when an IPMP group name has a length that is greater than 14, or contains special characters.
Resolution
A fix for this issue is included in the Veritas VRTScps 7.0.1 package.
For older versions, there are couple of workarounds available:
Figure 2 - An IPMP group name that is greater than 14 characters and contains an underscore
Figure 3 - An IPMP group name that has fewer than 14 characters and does not contain an underscore
For older versions, there are couple of workarounds available:
- Renaming the IPMP group to a name that is shorter than 14 characters and does not contain special characters (Figures 2 and 3).
- Unconfiguring IPMP
Figure 2 - An IPMP group name that is greater than 14 characters and contains an underscore
# ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 ipmp_database1234/v4 static ok 192.168.1.4/24 |
Figure 3 - An IPMP group name that has fewer than 14 characters and does not contain an underscore
# ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 ipmp1234/v4 static ok 192.168.1.4/24 |
Issue/Introduction
The CPS (Coordination Point Server) configuration, using installvcs62 -fencing configures the CPS (Coordination Point Server) but the script fails during vxfen startup on the VCS nodes. The vxfen startup log shows that the cpsadm command failed with "I/O error: 6." This results in the CPI (Common Product Installer) script rolling back the CPS fencing configuration and unregisters the nodes from CPS. It then starts fencing in disabled mode.
Running the cpsadm command on the VCS (Veritas Cluster Server) node, to ping one of the CP servers, fails with the same error (Figure 1).
Figure 1 - The cpsadm command fails with an I/O error
Using ping, or telnet, to test CP server port is successful. This suggests that there is no connectivity issue between the VCS nodes and the CP servers.
Note: The VCS nodes and CP servers IP addresses are configured with IPMP (IP Network Multipathing). The CP Servers listens on port 14250. Using telnet from the VCS nodes to connect to CP Server IP and port 14250 also works.
Running the cpsadm command on the VCS (Veritas Cluster Server) node, to ping one of the CP servers, fails with the same error (Figure 1).
Figure 1 - The cpsadm command fails with an I/O error
# /opt/VRTScps/bin/cpsadm -s 10.50.34.245 -a ping_cps I/O error: 6 |
Using ping, or telnet, to test CP server port is successful. This suggests that there is no connectivity issue between the VCS nodes and the CP servers.
Note: The VCS nodes and CP servers IP addresses are configured with IPMP (IP Network Multipathing). The CP Servers listens on port 14250. Using telnet from the VCS nodes to connect to CP Server IP and port 14250 also works.
Was this article helpful?
Yes
No
Powered by
