Scsi-target auto-poll

SANOS configuration guide mentions the command "show scsi-target auto-poll". It doesn't explain in detail what auto-poll is and how to activate it. It vaguely mentions that it has to do with "CSM or an IPS module is in the chassis". Can someone please clarify? Does this mean that the switch will attempt scsi-target on all IPS ports if it's inserted into the chassis? Because I thought the scsi target discovery can only be done on demand.
thanks

Whenever an IPS or CSM blade is in an MDS, the MDS will login to storage just the same as a real initiator would. We send Inquiry, Report Luns, and read capacity to learn about the storage out on the SAN. This process is done when the storage device comes online or when manually initiated. However, with auto-poll, we will go thru the discovery process every X number of seconds that can be configured.
This is not on the IPS ports but rather on any FC attached device that registers itself as a target. We use the pwwn seen as the result of show scsi-target internal driver. If the storage has any kind of LUN security, this pwwn will need to be permited or our discovery process will fail due to it being denied.

Similar Messages

  • Target Auto Discovery fails

    Hi,
    I have EMC12 installed on WinServer2008 R2 SP1. Cygwin ssh deamon started and configured. Agent is running on local account (LA) with administrative privileges and additional setting configured according to docs. OMS is running on local system account.
    When I start target auto discovery I get following error:
    Status          Failed
         Exit Code          4
         Step ID          1022
         Started          01-Jun-2012 11:06:54 GMT+02:00
         Ended          01-Jun-2012 11:06:54 GMT+02:00
         Step Elapsed Time          0 seconds
         Management Service          OracleEM.Myhost:4889_Management_Service
    Output Log
    Host discovery job failed. Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
    Even I had created such directory manually it stills shows the same error. I have also verified that LA account has full control to C:/MiddlewareHome/agent/agent_inst directory.
    Cygwin doesnt have sudo option installed (not needed according to docs on Windows, although job credentials require sudo delegation - what for?).
    Any ideas?
    Thanks,
    JP

    Logs show following:
    [2012-06-04T15:40:46.267+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.Util.class] [tid: [ACTIVE].ExecuteThread: '11' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: SYSMAN] [ecid: d70f67283c055146:772f8397:137b7b1143f:-8000-0000000000000252,0] [APP: emgc] oracle.sysman.core.discovery.uimodel: MissingResourceException: nlsid=OSB_DISCOVERY_TEXT, rb=oracle.sysman.db.rsc.ob
    [2012-06-04T15:41:27.281+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] Exception occurred while creating discovery directory under:C:/MiddlewareHome/agent/agent_inst:java.security.PrivilegedActionException: oracle.sysman.emSDK.agent.client.exception.PerformOperationException: Failed to launch process: Cannot run program "mkdir": CreateProcess error=2, The system cannot find the file specified
    [2012-06-04T15:41:27.281+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] Unable to create discovery directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
    [2012-06-04T15:41:27.312+02:00] [EMGC_OMS1] [WARNING] [] [oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand] [tid: RemoteJobWorker 1931] [userId: SYSMAN] [ecid: 0000JUrgIZnFKA05zzK6yW1FnBYO000001,1:26629:3] [APP: emgc] executeNMapCommand: Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst[[
    java.lang.Exception: Unable to create directory:discoveryunder:C:/MiddlewareHome/agent/agent_inst
         at oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand.executeNMapCommand(RunNMapCommand.java:633)
         at oracle.sysman.emdrep.disc.nmap.jobs.RunNMapCommand.executeCommand(RunNMapCommand.java:337)
         at oracle.sysman.emdrep.jobs.CommandStepExecutor.execute(CommandStepExecutor.java:153)
         at oracle.sysman.emWebservices.inbound.jobs.worker.ConsoleJobStepExecutor.execute(ConsoleJobStepExecutor.java:316)
         at oracle.sysman.emWebservices.inbound.jobs.worker.ConsoleJobStepExecutor.executeStep(ConsoleJobStepExecutor.java:182)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:597)
         at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:369)
         at oracle.j2ee.ws.server.jaxws.ServiceEndpointRuntime.processMessage(ServiceEndpointRuntime.java:201)
         at oracle.j2ee.ws.server.jaxws.JAXWSRuntimeDelegate.processMessage(JAXWSRuntimeDelegate.java:479)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doEndpointProcessing(ProviderProcessor.java:1187)
         at oracle.j2ee.ws.server.WebServiceProcessor$1.run(WebServiceProcessor.java:1089)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAsPrivileged(Subject.java:517)
         at oracle.security.jps.internal.jaas.AccActionExecutor.execute(AccActionExecutor.java:47)
         at oracle.security.jps.internal.jaas.CascadeActionExecutor$SubjectPrivilegedExceptionAction.run(CascadeActionExecutor.java:79)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:146)
         at weblogic.security.Security.runAs(Security.java:61)
         at oracle.security.jps.wls.jaas.WlsActionExecutor.execute(WlsActionExecutor.java:48)
         at oracle.security.jps.internal.jaas.CascadeActionExecutor.execute(CascadeActionExecutor.java:52)
         at oracle.security.jps.internal.jaas.AbstractSubjectSecurity.executeAs(AbstractSubjectSecurity.java:138)
         at oracle.j2ee.ws.server.provider.GenericProviderPlatform.runAs(GenericProviderPlatform.java:304)
         at oracle.j2ee.ws.server.WebServiceProcessor.invokeEndpointImplementation(WebServiceProcessor.java:1096)
         at oracle.j2ee.ws.server.provider.ProviderProcessor.doRequestProcessing(ProviderProcessor.java:581)
         at oracle.j2ee.ws.server.WebServiceProcessor.processRequest(WebServiceProcessor.java:232)
         at oracle.j2ee.ws.server.WebServiceProcessor.doService(WebServiceProcessor.java:192)
         at oracle.j2ee.ws.server.WebServiceServlet.doPost(WebServiceServlet.java:484)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.sysman.eml.app.EMRepLoginFilter.doFilter(EMRepLoginFilter.java:315)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.sysman.emas.fwk.MASConnectionFilter.doFilter(MASConnectionFilter.java:41)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adf.library.webapp.LibraryFilter.doFilter(LibraryFilter.java:175)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.sysman.eml.app.ContextInitFilter.doFilter(ContextInitFilter.java:555)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.adfinternal.view.faces.caching.filter.AdfFacesCachingFilter.doFilter(AdfFacesCachingFilter.java:129)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
         at java.security.AccessController.doPrivileged(Native Method)
         at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
         at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
         at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
         at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
         at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
    That seems strange as mkdir is WinSrvr system command.
    JP

  • SCSI target driver won't attach

    I am writing a SCSI target driver for a data acquisition system with Solaris 8 X86. When I try the add_drv command: add_drv ds21 I get the following errors:
    devfsadm: driver failed to attach: ds21
    Warning: Driver (ds21) successfully added to system but failed to attach
    I probably need to include an alias with the add_drv command, but, I have used the prtconf -vp command to list the devices names however, none of the devices tied to the SCSI bus show up on the list. Any suggestions?

    I think that you are missing entries in your driver.conf file for the devices that your driver is controlling. See the bst sample driver.
    If you have just one scsi bus, it should take the form
    name="ds21" class="scsi" target=t lun=0;
    where t is the SCSI Target ID
    If you have more than one scsi bus, it should take the form
    name="sd21" parent="/sbus@1,f8000000/esp@0,8000" target=t lun=0;

  • SCSI targets

    Hi, I'm getting the following warning messsage from a Solaris 2.6 system. The equipment has 2 internal disks at target 0,2 and 5 external disks on 1,3,4,5 and 6.
    WARNING: /sbus@1f,0/SUNW,fas@e,8800000 (fas0):
    data transfer overrun: current fas state:
    fas: Latched stat=0x90<IPND,XZERO> intr=0x10<BUS>
    fas: last msgout: <unknown msg>, last msgin:IDENTIFY
    fas: DMA csr=0xb2bf8810<TWOCYC,BRST1,BST0,DSB
    LEDRN,WIDE,INTEN>
    fas: addr=0 dmacnt=0 test=0 last=f0520000 last_cnt=800
    fas: fas state:
    fas: count(32)=0 cmd=1 stat=13 stat2=80 intr=0
    fas: step=cc fifoflag=80 conf=17 test=13 conf2=90 conf3=c3
    fas: Cmd dump for Target 0 Lun 0:
    fas: cdb=[ 0xa 0x0 0x0 0x10 0x4 0x0 ]
    fas: State=DATA Last State=DATA_DONE
    fas: pkt_state=0xf<XFER,CMD,SEL,ARB> pkt_flags=0x4000 pkt_statistics=0x3
    WARNING: /sbus@1f,0/SUNW,fas@e,8800000 (fas0):
    Target 0 reducing sync. transfer rate
    WARNING: /sbus@1f,0/SUNW,fas@e,8800000/sd@0,0 (sd0):
    SCSI transport failed: reason 'data_ovr': retrying command
    Eventhough the system works fine (apparently) I'm a little worried about this message... any idea?
    thanks!!

    Thanks
    Is it supported to create a symbolic link in the /dev/rdsk t opoint to the devices under /devices? Anyways, the entries under /dev/rdsk are all symbolic links, so can I just create an entry with the same name on the two nodes to poing to the device?

  • Target AUTO CLI :)

    SO... We all know that target is notoriously stingy with limits. I saw a week or so ago that someone had an insanely huge limit, like 2k! I didn't use my card for about 3 months. It showed a ZERO balance until I used the card a week or so ago just to show some activity so it wouldn't get closed! I received in the mail today that my limit has increased from $300 to $800 I guess thats better than the 3 hundred huh!!!

    dk2003 wrote:
    SO... We all know that target is notoriously stingy with limits. I saw a week or so ago that someone had an insanely huge limit, like 2k! I didn't use my card for about 3 months. It showed a ZERO balance until I used the card a week or so ago just to show some activity so it wouldn't get closed! I received in the mail today that my limit has increased from $300 to $800 I guess thats better than the 3 hundred huh!!!You bet it is!  In my wallet: Venture 15k; Barclay Ring 12.5k; Discover 10k; CareCredit 7.7k; Amazon Store Card 5k. QS 5k; BofA Travel Rewards 3.5k; BofA Travel Rewards 3.5k; BofA Platinum Visa 2k; Barclay Apple Rewards 2k. Total Credit: 66,200. 7/1-FICO: EQ - 789; TU - 781; EX - 690; GOAL: 780 across the board then 800 across the board. Inquiries: EQ: 4; TU: 7; EX 7; Chapter 13 seven years May, 2015. Reset my garden date to 6/27. Gardening until further notice.

  • SCSI auto sense failure when SCSI tape drives are present

    I've got a driver based on Sun's old SCSI Solaris 8 bst.c sample that worked fine up until the latest Solaris 10. Now I get a "Check condition with Auto Sensing" failure on all SCSI targets using this driver whenever a SCSI tape drive is present.
    Is there a document that describes SCSI driver changes with the latest Solaris 10?

    When a failure occurs pkt_r is 0 (command complete), pkt_state has flags 0x17 (which mean xfer didn't happen and STATE_ARQ_DONE didn't happen), but the sts_chk bit is true indicating a check condition.
    rqsense option is set, so the driver doesn't attempt to manually retrieve sense data. Should it?
    Anyone at Sun want to advise on an OS behavior change that might be linked to this?

  • WHY IS S.M.A.R.T STATUS SUPPORTED ON ATA BUS BUT NOT ON SCSI?

    I have 4 internal HD's on a G4 733 S-Drive (Digital Audio) running X.4.4
    and my question is:
    Why is S.M.A.R.T STATUS supported on the ATA bus but not on the SCSI bus?
    Is there something wrong with my computer if only 2 of the 4 internal HD's read "Verified" and the other two state "SMART STATUS NOT SUPPORTED"?
    The only reason I noticed this is because I decided to clone my main HD running X.4.2 (supported) to a larger 7200 rpm HD connected to the SCSI. My Main HD is in position one on the ATA Bus. All four internal hard drives are currently running well although the SCSI bus was a bit slower upon startup only. So I updated the cloned HD to X.4.4 and then loaded iLife '06 to the cloned drive just to make sure all runs as expected. Which it did.
    I ran apple's DU on all four internal HD's and all of them showed the green writing with No red lettering. But can someone please help me interpret the following from apple's DU on each HD which reads follows:
    Disk Description : IBM-IC35L060AVER07-0 Total Capacity : 57.3 GB (61,492,838,400 Bytes)
    Connection Bus : ATA Write Status : Read/Write
    Connection Type : Internal S.M.A.R.T. Status : Verified
    Connection ID : Device 0
    Disk Description : WDC WD1200JB-00HUA0 Total Capacity : 111.8 GB (120,034,123,776 Bytes)
    Connection Bus : ATA Write Status : Read/Write
    Connection Type : Internal S.M.A.R.T. Status : Verified
    Connection ID : Device 1
    Disk Description : ATA WDC WD1200JB-00G Media Total Capacity : 111.8 GB (120,034,123,776 Bytes)
    Connection Bus : SCSI Write Status : Read/Write
    Connection Type : External S.M.A.R.T. Status : Not Supported
    Connection ID : SCSI Target ID 0, Logical Unit 0
    Disk Description : ATA Maxtor 6Y120P0 Media Total Capacity : 114.5 GB (122,942,324,736 Bytes)
    Connection Bus : SCSI Write Status : Read/Write
    Connection Type : External S.M.A.R.T. Status : Not Supported
    Connection ID : SCSI Target ID 2, Logical Unit 0
    Thanks in Advance.
    SDMacuser

    Hi, SD!
    I haven't found anything specific on this, but I have always been under the impression that S.M.A.R.T. simply doesn't work with SCSI or externals. In my own experience, if I switch a drive from FW to my IDE bus, it reports. If I switch from the IDE bus to FW, the drive's S.M.A.R.T isn't supported.
    Other than being unable to actually run and verify S.M.A.R.T. on your SCSI or external drives, I really don't think that you need be concerned with the "not supported" message, which simply is telling you that the particular drive or bus can't run S.M.A.R.T. (man! I hate typing all those "periods"...).
    It also isn't supported on some old hard drives, even if they're connected to the IDE bus (like those 6-10 giggers I scrounge from ancient PCs that my friends and relatives junk when they finally switch and get new Macs...)
    Regards,
    Gary
    1GH DP G4 Quicksilver 2002, 400MH B&W rev.2 G3, Mac SE30   Mac OS X (10.4.2)   5G iPod, Epson 2200 & R300 & LW Select 360 Printers, Epson 3200 Scanner
    1GH DP G4 Quicksilver 2002, 400MH B&W rev.2 G3, Mac SE30   Mac OS X (10.4.2)   5G iPod, Epson 2200 & R300 & LW Select 360 Printers, Epson 3200 Scanner

  • Re: How to add targets manually, in OEM 12C, through command line...

    I am trying to add the rac targets using emcli interface. Before adding rac_database as target type we need to add a cluster. I Used the following command to add a cluster but it fails with internal error. and the log files do not show any error.
    Any idea how to fix this?
    ./emcli add_target -name="bacalbdb01n_cluster" -type="cluster" -host="bacalbdb01n1" -monitor_mode="1" -properties="OracleHome:/u01/crs/oracle/product/11/app;scanName:bacalbdb01n-scan;scanPort:1521" -instances="bacalbdb01n1:host;bacalbdb01n2:host"
    Internal Error: The EM CLI system has encountered an internal error. Details have been added to the EM CLI log files.

    Looks like it might be bug 15982024 where the target is already part of a cluster.   Can you check your unpromoted targets (Setup -> Add Target -> Auto Discovery Results -> tab Agent Based Targets) and see if a cluster on either of those hosts is already discovered but not yet promoted.  If so, you can try to delete that discovered cluster, and retry the cmd.
    Log File Locations
    The following examples show possible log file locations:
    Example 2-3 No Configuration Directory Specified with Setup Verb (default location)
    user.home/.emcli/.emcli.log user.home/.emcli/.emcli.log.1
    If you do not specify a configuration directory when you run the setup verb (-dir option is omitted), EM CLI assumes the .emcli configuration directory is located within your local home directory. The log files are placed at the root level of the .emcli directory. The .emcli directory must be local (not mounted remotely).

  • Send a SCSI command to the device in attach ( )

    I want to send an Inquiry Page and Read Buffer SCSI command to the device in attach( ). Can I do that? How to do that?
    Thanks.

    I assume you are talking about a SCSI Target driver, not an HBA driver.
    Using scsi_probe() would be the normal way to send an inquiry. Once you have initialized everything in the attach routine, I don't think there is any reason you can't start a normal transfer. Have you looked at the sample drivers?
    http://developers.sun.com/prodtech/solaris/driverdev/reference/codesamples/
    Richard

  • Scsi device discovery in Cisco MDS switches

    I was using this device discovery to find out how many luns can be seen on that server.
    I tried to use discover scsi-target command and it does not give much useful information. and I do not want to add the OS WWNS on my LUN security in addition to HBA WWNS for the host group on the array end.
    The problem that I am having is that I can see 7 LUNs out of 9 when I connect to Cisco MDS where as in brocade I can see all the LUNs.
    I checked the LUN security and zoning and everything seems to be correct.
    If Cisco SAN OS has commands where by I can see what LUNs can be seen on the switch, that would be really helpful. But It looks like LUN/LDEV info cannot be seen through discover command.
    Please let me know how to troubleshoot this problem
    Thanks

    In the array, I tried to add switch wwn to the LUN Security and zoned the same switch wwn on the MDS. Is there anything I am missing. Thanks in advance
    But still I could not see any LUNs. When I do discover command, NLUNS shows 0.
    and the command sh scsi-target lun os win shows nothing.
    discover scsi-target vsan 21 fcid 0xea000b os win
    VSAN: 21 FCID: 0xea000b
    PRLI RSP: 0x01 SPARM: 0x0012
    SCSI TYPE: 31 NLUNS: 0
    Vendor: HITACHI Model: DISK-SUBSYSTEM Rev: 5007
    Other: 7f:00:03:12:cf:00:00:02

  • Trying to go into Target mode shuts down dual 800mhz G4

    I have a Dual 800 G4 and am trying to set it up so I can use the Migration Assistant on my new MacPro. When I try and restart holding down 'T' the computer just abruptly shuts down. I'm wondering if this has something to do with the fact that I have a PCI scsi card installed in the G4, the details of the drives in the G4 are here:
    SCSI Parallel Domain 65536:
    Initiator Identifier: 7
    ATA WDC WD800BB-40BS:
    Capacity: 74.53 GB
    Manufacturer: ATA
    Model: WDC WD800BB-40BS
    Revision: A0
    Removable Media: Yes
    BSD Name: disk1
    OS9 Drivers: Yes
    SCSI Target Identifier: 0
    SCSI Logical Unit Identifier: 0
    S.M.A.R.T. status: Not Supported
    Volumes:
    Mac Diddly:
    Capacity: 74.53 GB
    Available: 61.17 GB
    Writable: Yes
    File System: HFS+
    BSD Name: disk1s6
    Mount Point: /Volumes/Mac Diddly
    ATA WDC WD800JB-00CR:
    Capacity: 74.53 GB
    Manufacturer: ATA
    Model: WDC WD800JB-00CR
    Revision: A1
    Removable Media: Yes
    BSD Name: disk0
    OS9 Drivers: No
    SCSI Target Identifier: 1
    SCSI Logical Unit Identifier: 0
    S.M.A.R.T. status: Not Supported
    Volumes:
    Macintosh HD:
    Capacity: 74.53 GB
    Available: 6.67 GB
    Writable: Yes
    File System: Journaled HFS+
    BSD Name: disk0s2
    Mount Point: /
    Anyone have any ideas why my G4 won't enter Target mode? And if not, is there another way I can migrate all my user info to the new MacPro.
    Thanks in advance...
    Dual 800 G4   Mac OS X (10.4.9)   PCI SCSI card, firewire drives, additional firewire 800 PCI card, additional PCI USB card

    See this article for information.
    (20727)

  • Can't use scsi scanner?

    I have a Sharp JX-320 scanner. I've been using it on an older Mac, but I want to get rid of some clutter and use it on my Mac G4 OS X Tiger.
    It shows up through System Profiler (see profile below). But when I try to scan, either through Photoshop's scanning plugin or through VueScan, the scanning utilities are unable to find the scanner. This happens whether I work in OS X (using Photoshop 7 or VueScan), or in Classic (Photoshop 6)
    The scanner is plugged in to the scsi card, is the only thing on the chain, and is terminated. I can't really figure out what the scsi device number is, or how to change it, if that might be the problem.
    What's going on? Is there any way to get the scanner to show up?
    SCSI Parallel Domain 65536:
    Initiator Identifier: 7
    SHARP JX320 SCSI:
    Manufacturer: SHARP
    Model: JX320 SCSI
    Revision: 071I
    SCSI Target Identifier: 4
    SCSI Logical Unit Identifier: 0

    Well, I only tried downloading the VueScan utility since the Photoshop plugins aren't working. I couldn't find my scanner in their unsupported list, but I didn't really expect it to work. (I was testing for an OS X native scanning utility, but it's not worth paying the $50 to license the utility when I can get a USB scanner for about the same cost.)
    Unfortunately, this computer won't boot in OS 9: I can only run OS 9.2.2 in Classic.
    In PS 7 my plug-in doesn't work. It doesn't even show up. Which is about what I'd expect. But I can't find an OS X plug-in for PS 7.
    In Classic, I've tried it both in PS 4 and PS 6. The utility opens as it always has on my OS 8.6 and OS 9.2.2 Macs. But when I try to scan, I get an error (GPIB Device "DEV7"not found).
    Any idea why the scanner would show up in System Profiler, but not be found by the scanning utility?
    Any idea if there's something that can be done to "fix" that?
    Any idea where I could get an OS X plug-in for Photoshop 7 that might work with this scanner?
    Thanks for any advice or help.

  • Relation between ssd and SCSI

    When I use Fibre Channel disk via sd driver, I know what cntndnsn
    means. But changed to ssd, the special files are
    c1t200600004C7F3E2Dd19, where following 't' is not a normal target
    number, but WWN of disk array. I guess ssd belongs to some kind of SCSI
    disk driver. But how to get the SCSI target number of ssd disk through
    programming?
    Message was edited by:
    Pukras

    Thanks a lot., Darren.
    I can understand 'Other drivers may fake a low 't' number'.
    But problem is how to get the faked number. Like the following name='target'...
    # prtconf -v
    ssd, instance #45
    System software properties:
    name='sd_retry_on_reservation_conflict' type=int items=1
    value=00000000
    Driver properties:
    name='pm-hardware-state' type=string items=1 dev=none
    value='needs-suspend-resume'
    name='ddi-failfast-supported' type=boolean dev=none
    name='ddi-kernel-ioctl' type=boolean dev=none
    Hardware properties:
    name='devid' type=string items=1
    value='id1,ssd@x00004c7f3e2d0270'
    name='inquiry-revision-id' type=string items=1
    value='2800'
    name='inquiry-product-id' type=string items=1
    value='iStorage 2000'
    name='inquiry-vendor-id' type=string items=1
    value='NEC'
    name='inquiry-device-type' type=int items=1
    value=00000000
    name='sam-lun' type=int64 items=1
    value=0016000000000000
    name='lun' type=int items=1
    value=00000016
    name='target' type=int items=1
    value=00b600dc
    name='port-wwn' type=byte items=8
    value=20.06.00.00.4c.7f.3e.2d
    name='node-wwn' type=byte items=8
    value=20.00.00.00.4c.7f.3e.2d
    name='compatible' type=string items=5
    value='scsiclass,00.vNEC.piStorage_2000.r2800' + 'scsiclass,00.vNEC.piStorage_2000' + 'scsa,00.bfcp' + 'scsiclass,00' + 'scsiclass'
    Pukras

  • Scsi offline or reservation conflict errors afer swapping HBAs

    We swapped out all of our EMC branded Emulex LP10000 HBAs and replaced them with the Sun branded Emulex LP11000 (SG-XPCI1FC-EM4-Z). We now receive a steady stream of SCSI errors in /var/ad/messages similar to the following:
    Nov 8 13:37:29 fhtulsaps201 scsi: [ID 107833 kern.warning] WARNING: /ssm@0,0/pci@19,600000/SUNW,emlxs@1/fp@0,0/ssd@w50060482d52dd0b7,16 (ssd27):
    Nov 8 13:37:29 fhtulsaps201 offline or reservation conflict
    These devices are target devices from a remote server and are kept in sync using EMCs RecoverPoint appliances. They are normally in a read write disabled state. I do not have access to SRDF but expect I would get the same errors since SRDF also puts the target devices in the same read write disabled state.
    As you can see the messages file fills up rather quickly and is basically unusable.
    root@fhtulsaps201# wc -l /var/adm/messages
    208634 /var/adm/messages
    root@fhtulsaps201# ls -l /var/adm/messages*
    -rw-r--r-- 1 root root 28340369 Nov 8 13:52 /var/adm/messages
    -rw-r--r-- 1 root root 94960043 Nov 7 03:07 /var/adm/messages.0
    -rw-r--r-- 1 root root 94643625 Oct 31 03:08 /var/adm/messages.1
    -rw-r--r-- 1 root root 113367276 Oct 24 03:07 /var/adm/messages.2
    -rw-r--r-- 1 root root 118930213 Oct 17 03:08 /var/adm/messages.3
    root@fhtulsaps201#
    As a part of the HBA upgrade we applied several kernel patches so at this point I'm not sure if the new HBAs are to blame or one of the patches.
    The old HBAs never produced these errors.
    I would like to know it there's a way to reduce the logging output from the scsi driver.
    Thanks for any help.

    We see the same error, though not nearly in such abundance, on our Clariion systems when they are using "explicit trespass" mode. In this mode the "passive" path is completely inaccessible until a special control message is sent to it. Veritas sends that special control message when the primary path has failed (EMC's PowerPath does the same thing).
    I know EMC recommends this because you should never end up with I/O going to the wrong service processor accidentally (a trespass) because it simply won't service such I/O's unless explicitly told to do so (gee, I wonder where the name explicit trespass came from? :)
    I'd guess your RecoverPoint devices behave similarly.
    The relevant code appears to this this bit from http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/io/scsi/targets/sd.c#9589:
       9570           /*
       9571            * If the target is not yet ready here (defined by a TUR
       9572            * failure), invalidate the geometry and print an 'offline'
       9573            * message. This is a legacy message, as the state of the
       9574            * target is not actually changed to SD_STATE_OFFLINE.
       9575            *
       9576            * If the TUR fails for EACCES (Reservation Conflict),
       9577            * SD_RESERVED_BY_OTHERS will be returned to indicate
       9578            * reservation conflict. If the TUR fails for other
       9579            * reasons, SD_NOT_READY_VALID will be returned.
       9580            */I'm not a SCSI expert by any stretch of the imagination, but it seems to me that either Solaris is misinterpreting the "EACCES" error code or EMC is mis-using it. Could be that there's no good code in the SCSI protocol to say "Yea, I'm here, but I won't talk to you right now" except this one.
    This exists in the "sd_ready_and_valid" function which appears to be called any time I/O is attempted to the device if the geometry of the device is not yet known (which it never will be for these standby devices).
    So, in summary, if your system can "see" a SCSI LUN which responds to a Test Unit Ready (TUR) with "EACCES" then you're going to be seeing these messages. I think your only hope it to check your systems carefully and find out what process is trying to do I/O to them and fix that process.
    Best of luck!

  • Enterprise manager cloud control 12c issue configuring Target Disconvery

    I've performed a silent agent install of Oracle Enterprise Cloud Control Agent 12c on the first node of a RAC two node cluster (oracle 11gR2) on Red Hat Linux 5.6 64bit.
    oemgrid>./emctl status agent
    Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
    Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
    Agent Version : 12.1.0.1.0
    OMS Version : (unknown)
    Protocol Version : 12.1.0.1.0
    Agent Home : /emcc/agent12c/agent_inst
    Agent Binaries : /emcc/agent12c/core/12.1.0.1.0
    Agent Process ID : 31354
    Parent Process ID : 31302
    Agent URL : http://rac1.respecti.com:3872/emd/main/
    Repository URL : https://emcc.respecti.com:14511/empbs/upload/
    Started at : 2011-10-25 16:36:47
    Started by user : oemgrid
    Last Reload : (none)
    Last successful upload : (none)
    Last attempted upload : (none)
    Total Megabytes of XML files uploaded so far : 0
    Number of XML files pending upload : 1
    Size of XML files pending upload(MB) : 0
    Available disk space on upload filesystem : 91.95%
    Collection Status : Collections enabled
    Last attempted heartbeat to OMS : 2011-10-25 16:36:52
    Last successful heartbeat to OMS : (none)
    Agent is Running and Ready
    However from OMS server (OECC 12c)
    From Setup -> Add Target -> Configure Auto Discovery
    Configure Auto Discovery -> Database - Listener -> Agent Based -> Configure
    Add Host -> Target Type = Host
    Target Name = rac1
    Host Name = 192.168.1.12 -> Search -> AND NO TARGETS FOUND
    Why
    Recommendations Appreciated!

    If I am understanding correctly, you are looking to discovery a RAC DB on a host on which you deployed an agent. The auto discovery configuration you mention is used to configure the frequency of automatic discovery on a given host after the initial deployment. Normally, you do not need to do anything in this screen.
    Immediately after initial installation and successful registration, the agent will search the host automatically for database installations and report its findings to the OMS. These results can be seen in Setup->Add Target->Auto Discovery Results on the Non-Host targets tab. Here you can search by host and you should see a Cluster Database target. To get the target under management, select it and click Promote and follow the wizard.
    You can also initiate a discovery of databases on a host by going to Setup->Add Target->Add Targets Manually. Select Add Non-Host targets using Guided process. Select target type in drop down of "oracle database, Listener and Automatic Storeage management". The click Add Using Guided Discovery. Here the agent will immediately scan the host and show the results which you can then complete the target addition process.
    If I am misunderstanding you please let me know.
    Dave

Maybe you are looking for