Failed To Create Nodes For Pwwn= Error=0
Contents |
LinkedIn How to Use this Site ? Storage : "Failed to create nodes for pwwn" cfgadm: library error: report luns failed: error during solaris boot June 18, 2011By RamdevOther Learning Articles that
Cfgadm: Insufficient Condition
you may like to read Latest ArticlesInformation CentersLinux AdminSolaris AdminVxVM AdminVCS AdminCareer GuidanceScriptingStorage AdminQuick ReferenceLatest Articles Information Centers Linux Admin Solaris Admin VxVM Admin VCS Admin Career Guidance Scripting Storage Admin Quick Reference Free Courses We Offer Linux Administration Interview Preparation [Free Email Crash Course] Roles and Responsibilities of System Admin [Free Course] Getting Started with RHEL7 Administration [Free Course] Paid Training Courses we Offer Self Paced CoursesLive WebexSelf Paced CoursesSolaris11 Self Paced Video Learning RHEL7 Self Paced Video Learning VxVM + VCS Self Paced Video Learning Solaris10 Self Paced Video Learning Puppet Automation Self Paced Video Learning Live WebexSolaris 11 Administration Live WebEx Puppet Automation - Live WebEx Veritas ( VCS+VxVM) Live Webex If Fibre Channel devices are not present or turned off, boot errors will occur. Without corrective action, these errors will persist for every re-boot. The boot errors which are linked to this problem, can be found in the /var/adm/messages file, and are formatted as follows: luxadm[90]: [ID 593423 user.error] ID[luxadm.create_fabric_device.2316] configuration failed for line (/devices/pci@8,600000/SUNW,qlc@2,1/fp@0,0:fc::256000c0ffc028e4) in file: /etc/cfg/fp/fabric_WWN_map. I/O error scsi: [ID 243001 kern.warning] WARNING: /pci@8,600000/SUNW,qlc@2,1/fp@0,0 (fcp4): Failed to create nodes for pwwn=266000c0ffe028e4; error=5 The reason for these errors is that the device in question cannot be seen by the Solaris[TM] Operating System that is connected to a Fibre Channel Storage Area Network. Solaris[TM] will continue to report this error, every time it boots, until corrective action is taken. This error only pertains to fabric (switch) attached devices, as direct attached devices do not invoke the luxadm command at boot that can
Expert Users Expert-to-Expert. Learn advanced UNIX, UNIX commands, Linux, Operating Systems, System Administration, Programming, Shell, Shell Scripts, Solaris, Linux, HP-UX, AIX, OS X, BSD. Search Forums Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... learn linux and unix commands - unix shell scripting SAN Configuration in Solaris UNIX for Advanced & Expert Users Thread Tools Search this Thread Display Modes http://unixadminschool.com/blog/2011/06/storage-failed-to-create-nodes-for-pwwn-error-during-solaris-boot/ #1 02-28-2007 Remi Registered User Join Date: Nov 2006 Last Activity: 11 June 2007, 12:45 PM EDT Posts: 36 Thanks: 0 Thanked 0 Times in 0 Posts SAN Configuration in Solaris Hi, I have 4 servers that I connected SUN HBAs on. (SAN is IBM - ESS 800 with Brocade switch) I installed the SAN http://www.unix.com/unix-for-advanced-and-expert-users/35773-san-configuration-solaris.html foundation kit, IBMsdd drivers, Solaris Patch 108974-50 & SANsurfer CLI. (I'm running Solaris 8 - HBA is SG-XPC11FC-QL2 On 1 of the 4 servers show the HBAs as CONNECTED, but will not configure. cfgadm -al Shows # cfgadm -al Ap_Id Type Receptacle Occupant Condition c0 scsi-bus connected configured unknown c0::dsk/c0t0d0 CD-ROM connected configured unknown c1 scsi-bus connected configured unknown c1::dsk/c1t0d0 disk connected configured unknown c1::dsk/c1t1d0 disk connected configured unknown c2 scsi-bus connected unconfigured unknown c3 fc-fabric connected unconfigured unknown c3::5005076300c49b00 disk connected unconfigured unknown c3::5005076300c89b00 disk connected unconfigured unknown c4 fc-fabric connected unconfigured unknown c4::5005076300cc9b00 disk connected unconfigured unknown c4::5005076300d09b00 disk connected unconfigured unknown # I tried to configure these disks, & I got the following message : # cfgadm -c configure c3 cfgadm: Library error: failed to create device node: 5005076300c49b00: Invalid argument failed to create device node: 5005076300c89b00: Invalid argument failed to configure ANY device on FCA port I tried forcing the configuration & still got the same error message # cfgadm -o force_update -c configure c3 cfgadm -o force_update -c confi
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 https://vox.veritas.com/t5/NetBackup/robot-issue-with-OS-system/td-p/217775 CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results http://docs.oracle.com/cd/E19253-01/816-5166/cfgadm-fp-1m/index.html by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : robot issue with OS system VOX : Backup and Recovery : NetBackup : robot issue with OS system Subscribe to RSS Feed Mark Topic as New Mark Topic as Read failed to Float this Topic to the Top Bookmark Subscribe Printer Friendly Page robot issue with OS system Manfred_Ratzke Level 4 01-21-2009 03:18 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, after reboot th erobot cannot initialized and I see on the OS systembash host# cfgadm -c configure c4cfgadm: Library error: failed to create device node: 500104f0006e46a8: failed to create I/O errorOperation partially successful. Some failures seenbash host# cfgadm -c unconfigure c4::500104f0006e46a8cfgadm: Library error: remove operation failed: /devices/pci@8,700000/SUNW,qlc@5/fp@0,0/sg@w500104f0006e46a8,0: Inappropriate ioctl for device Labels: 7.1.x and Earlier Backup and Recovery NetBackup 0 Kudos Reply 6 Replies Re: robot issue with OS system Amit_Karia Level 6 01-21-2009 04:13 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Can you run#luxadm probecommand and send the o/p 0 Kudos Reply Re: robot issue with OS system Manfred_Ratzke Level 4 01-21-2009 05:02 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Let me explain before:when I go and reset the robot and bott the server then all drives are ok and robot initializedwhen I then start backups the first 3 run fine, further more will cause that thesystemmessage"cannot initialize robot"g1bs01 console login: Jan 21 13:06:46 g1bs01 ltid[848]: Request for media ID 000316 is being rejected because it cannot be found in designated slotJan 21 13:07:23 g1bs01 tldcd[1853]: TLD(0) key = 0x4, asc = 0x40, ascq = 0x1, HARDWARE ERROR, GENERALJan 21 13:07:23 g1bs01 tldcd[1853]: TLD(0) Move_medium error: CHECK CONDITIONJan 21 13:07:23 g1bs01 tldcd[1853]: TLD(0) could n
Options | Examples | Files | Attributes | See Also | Warnings | Notes Name cfgadm_fp– driver specific commands for cfgadm Synopsis /usr/sbin/cfgadm [-f] [-n | -y] [-v] [-o hardware_options] -c function ap_id [ap_id] /usr/sbin/cfgadm [-v] [-a] [-s listing_options] [-o hardware_options] [-l [ap_id]] /usr/sbin/cfgadm [-v] [-o hardware_options] -h [ap_id] Description The fp port driver plug-in /usr/lib/cfgadm/fp.so.1 provides the functionality for Fibre Channel Fabric device node management through cfgadm(1M). cfgadm operates on attachment points. Attachment points are locations in the system where hardware resources can be dynamically reconfigured. Refer to cfgadm(1M) for additional details on attachment points. For Fibre Channel Fabric device node management, each fp port node is represented by an attachment point in the device tree. In addition, each Fibre Channel device is represented by a dynamic attachment point. Attachment points are named through ap_ids. Two types of ap_ids are defined: logical and physical. The physical ap_id is based on the physical pathname. The logical ap_id is a shorter, more user-friendly name. For fp port nodes, the logical ap_id is the corresponding disk controller number. For example, c0 is a typical logical ap_id. Fibre Channel devices are named with a port World Wide Name (WWN). If a disk device is connected to controller c0, its ap_id can be: c0::50020f2300006077 where 50020f2300006077 identifies the port WWN of a specific Fibre Channel device. Each device on the Fibre Channel private loop port, Fabric port or public loop port is probed and made available to Solaris by default. Devices connected to the Fibre Channel Fabric port or public loop port can be made unavailable to Solaris by initiating an application or an end user operation. The operation is similar to the hot unplugging of devices by way of management user interfaces. Applications or users can use the /usr/lib/cfgadm/fp.so.1 library to enable libcfgadm to provide interfaces to accomplish this task. The list of currently connected Fabric devices is generated in the form of the attachment point. A simple listing of attachment points in the system includes attachment points at fp port nodes but not Fibre Channel devices. The following example uses the -a flag to the list option (-l) to list Fibre Channel devices: # cfgadm -l Ap_Id Type Receptacle Occupant Condition c0 fc-fabric connected configured unknown c1 fc-private connected configured unknown c2 fc connected unconfigured unknown sysctr