Error Module Vxfen Is In Use
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Business Continuity : Discussions : Unable to load vxfen module on to Coordination poi... VOX : Business Continuity : Discussions : Unable to load vxfen module on to Coordination poi... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Unable to load vxfen module on to Coordination point server UmeshCM Level 3 10-17-2011 02:29 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content OS installed: RHEL 5.5 X86_64 Veritas Package: SFHA 5.1 Sp1RP2 It's a Single node VCS coordination point server. #rpm -qa| grep -i vxfen VRTSvxfen-5.1.132.000-SP1RP2_RHEL5 # vxfenadm -d VXFEN vxfenadm ERROR V-11-2-1101 Open failed for device: /dev/vxfen # vxfenconfig -l VXFEN vxfenconfig ERROR V-11-2-1002 Open failed for device: /dev/vxfen with error 2 # cat /etc/vxfenmode cat: /etc/vxfenmode: No such file or directory #ls -l /dev/vxfen ls: /dev/vxfen: No such file or directory # ls -l /dev/vxfend ls: /dev/vxfend: No such file or directory more /var/VRTSvcs/log/vxfen/vxfen.log Tue Nov 15 01:49:46 EST 2011 Invoked vxfen. Starting Tue Nov 15 01:49:46 EST 2011 starting vxfen.. Tue Nov 15 01:49:46 EST 2011 vxfen module load failed. Tue Nov 15 01:58:17 EST 2011 Invoked vxfen. Starting Tue Nov 15 01:58:17 EST 2011 starting vxfen.. Tue Nov 15 01:58:17 EST 2011 vxfen module load failed. Tue Nov 15 01:59:29 EST 2011 Invoked vxfen. Starting Tue Nov 15 01:59:29 EST 2011 vxfen module is not loaded. Tue Nov 15 02:01:14 EST 2011 Invoked vxfen. Starting Labels: Business Continuity Cluster Server Troubleshooting 0 Kudos Reply 8 Replies Does anyone have idea? Please Umes
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Vxfen driver not getting loaded after upgrading to 5.0MP3 for linux. Article:000042160 Publish: Article URL:http://www.veritas.com/docs/000042160 Support https://vox.veritas.com/t5/Discussions/Unable-to-load-vxfen-module-on-to-Coordination-point-server/td-p/429575 / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage https://www.veritas.com/support/en_US/article.TECH88086 your Subscriptions Problem Vxfen driver not getting loaded after upgrading to 5.0MP3 for linux. Solution Trying to start fencing reported the following error message:./vxfen startStarting VxFEN: ./vxfen: line 169: vcsmodinst: command not foundVxFEN:Error: cannot find compatible module binaryVxFEN:ERROR: module load failed...Exiting/etc/init.d/vxfen script had a wrong entry.SOLUTION:There is an error is our script which starts fencing.It should be modinst instead of vcsmodinst as in the script.Change 'vcsmodinst' to 'modinst' in /etc/init.d/vxfen and restart vxfen. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of tpanics At the time of a network partition the lowest node in each sub-cluster races for the coordination points on behalf of that sub-cluster. If the lowest node is unable to contact a majority of https://sort.symantec.com/public/documents/sfha/5.1sp1/solaris/productguides/html/sfrac_notes/ch01s10s02s25.htm the coordination points or the lowest node itself unexpectedly panics during the race, then all the nodes in that sub-cluster will panic. [1965954] Coordination Point agent does not provide detailed log message for inaccessible CP servers The Coordination Point agent does not log detailed information of the CP servers that are inaccessible. When CP server is not accessible, the agent does not mention the UUID or the virtual IP of the CP server in the engine log. error module [1907648] Preferred fencing does not work as expected for large clusters in certain cases If you have configured system-based or group-based preferred fencing policy, preferred fencing does not work if all the following cases are true: The fencing setup uses customized mode with one or more CP servers. The application cluster has more than eight nodes. The node weight for a single node (say galaxy with node id 0) is more than the sum total of node weights error module vxfen for the rest of the nodes. A network fault occurs and the cluster partitions into two with the single node (galaxy) on one part and the rest of the nodes on the other part. Under such circumstances, for group-based preferred fencing, the single node panics even though more high priority services are online on that node. For system-based preferred fencing, the single node panics even though more weight is assigned to the node. [2161816] See the Veritas Storage Foundation for Oracle RAC Administrator's Guide for more information on preferred fencing. Server-based I/O fencing fails to start after configuration on nodes with different locale settings On each (application cluster) node, the vxfen module retrieves and stores the list of the UUIDs of coordination points. When different nodes have different locale settings, the list of UUIDs on one (application) node does not match with that of the other (application) nodes. Hence, I/O fencing does not start after configuration. [2112742] Workaround: Start I/O fencing after fixing the locale settings to use the same values on all the (application) cluster nodes. Reconfiguring SF Oracle RAC with I/O fencing fails if you use the same CP servers When you reconfigure an application cluster that uses server-based I/O fencing (customized fencing mode), the installer does not remove the application cluster information from the CP servers before the reconfiguration. As a result, if you reconfigure the applicatio