Comments (7)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 cggibbo commented Permalink

Good one Anthony! If I had a dollar for everytime I've seen this......... <div>&nbsp;</div> BTW, this is usually accompanied by LED 569 being displayed for the LPAR, while AIX tries to configure the FCS SCSI protocol device....it can take some time to return if there are many adapters when uncabled ports! i.e. 4 dual port FC adapters, with only the first port cabled up... <div>&nbsp;</div> Classic stuff! <div>&nbsp;</div> And as an interesting side note. With my recent work with Virtual FC adapters, I found (not surprisingly I guess), that I also saw the same fscsi errors when I ran cfgmgr in a client LPAR. The physical adapters had been connected to the SAN but the WWPNs for the client VFC adapters had not been zoned.

2 AnthonyEnglish commented Permalink

Thanks Chris. For the benefit of those who are not familiar with it, virtual fibre channel adapters connect on the virtual client LPAR to NPIV-capable adapters on the VIO server. <div>&nbsp;</div> You can find more information about them here: <br /> http://www.ibm.com/developerworks/wikis/download/attachments/53871900/NPIV+-+VUG+12-18-2008.pdf?version=1

3 AnthonyEnglish commented Permalink

Oh, and thanks for the star, Chris. I'm glad someone took up my subtle hint. I was almost going to give the post a star myself.

4 Ed@TW commented Permalink

Thanks! Very helpful. <div>&nbsp;</div> I also just learned that if you put a wrap plug in the port on the adapter then AIX will not give you the warning.

5 marcinek commented Permalink

Hi, I;ve noticed the same errors when I messed up with zonning too. <br /> marcin

6 Wkrongard commented Permalink

But what if I accidentlly removed vfchost prior to setting the adapter to blank, as that is what I did and now cfgdev returns an error code that is not a 0, but rather "Method error: 0514-061 Cannot find a child device." --- you see I ran "rmdev -dev vfchost##" without first running "vfcmap -vadapater {vfchost##} -fcp", how do I now resolve this error? is there a simple command to correct this mistake?

7 AnthonyEnglish commented Permalink

It's an easy mistake to make. So it sounds like you have the map still in place. So you can't remove the map? If you could do that, you should be able to add or remove the vfchost via DLPAR through the HMC or IVM. <div>&nbsp;</div> Probably best to raise a call with your support so they can get a look at the environment in more detail. Sorry I'm not able to offer better than that. Once you've found out the solution, would you mind adding a comment to this blog post? <div>&nbsp;</div> Also, you may know that when you run commands as padmin, you can get a verbose look at what's happening by running this: <br /> export CLI_DEBUG=33 <div>&nbsp;</div> then run the VIOS command as padmin.