<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Problem with MSL6000 and In_sync state in switch fc 300 in StoreEver Tape Storage</title>
    <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528327#M24901</link>
    <description>full or null?</description>
    <pubDate>Tue, 24 Nov 2009 15:05:58 GMT</pubDate>
    <dc:creator>Torsten.</dc:creator>
    <dc:date>2009-11-24T15:05:58Z</dc:date>
    <item>
      <title>Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528314#M24888</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm having trouble with a MSL6000 and its communication by fiber channel throwgh a switch Brocade to a HP server.&lt;BR /&gt;&lt;BR /&gt;I tryied to change the wire but it still fail.&lt;BR /&gt;&lt;BR /&gt;Problem:&lt;BR /&gt;&lt;BR /&gt;- Until two weeks ago all was working ok&lt;BR /&gt;- Then it stopped to work (this message was displayed a lot of times):&lt;BR /&gt;Oct 23 15:31:04 backup kernel: st0: Error 70000 (sugg. bt 0x0, driver&lt;BR /&gt;bt 0x0, host bt 0x7).&lt;BR /&gt;&lt;BR /&gt;This was triggered by a backup software operation (bacula in this case) try.&lt;BR /&gt;&lt;BR /&gt;- Investing this issue:&lt;BR /&gt;# mtx -f /dev/autochanger1 status&lt;BR /&gt;cannot open SCSI device '/dev/autochanger1' - No such file or&lt;BR /&gt;directory&lt;BR /&gt;# ls -l /dev/autochanger1&lt;BR /&gt;lrwxrwxrwx 1 root root 3 2009-10-30 09:47 /dev/autochanger1 -&amp;gt; sg4&lt;BR /&gt;The device MSL6000 seems to be present in the system:&lt;BR /&gt;# lsscsi -g&lt;BR /&gt;...&lt;BR /&gt;[0:0:2:0]    mediumx HP       MSL6000 Series   0520  /dev/sch0  /dev/&lt;BR /&gt;sg4&lt;BR /&gt;[0:0:2:1]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st2  /dev/&lt;BR /&gt;sg5&lt;BR /&gt;[0:0:2:2]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st3  /dev/&lt;BR /&gt;sg6&lt;BR /&gt;[0:0:2:3]    storage HP       NS E1200-320     571f  -         /dev/&lt;BR /&gt;sg7&lt;BR /&gt;[1:0:3:0]    tape    HP       Ultrium 3-SCSI   G63W  /dev/st0  /dev/&lt;BR /&gt;sg2&lt;BR /&gt;[1:0:4:0]    tape    HP       Ultrium 3-SCSI   G54W  /dev/st1  /dev/&lt;BR /&gt;sg3&lt;BR /&gt;&lt;BR /&gt;- I tried to remove and add the device:&lt;BR /&gt;# echo "scsi remove-single-device 0 0 2 0" &amp;gt; /proc/scsi/scsi&lt;BR /&gt;# echo "scsi add-single-device 0 0 2 0" &amp;gt; /proc/scsi/scsi&lt;BR /&gt;# dmesg&lt;BR /&gt;lpfc 0000:03:01.0: 0:0713 SCSI layer issued LUN reset (2, 0) Data:&lt;BR /&gt;x2002 x3 x2&lt;BR /&gt;lpfc 0000:03:01.0: 0:0714 SCSI layer issued Bus Reset Data: x2002&lt;BR /&gt;scsi 0:0:2:0: scsi: Device offlined - not ready after error recovery&lt;BR /&gt;&lt;BR /&gt;I had to turn off the MSL6000 and then turn on, and then server saw again the devices and mtx works again. (Too in fc switch (zone viewer) I saw msl device without any color and after turn on it is with color again)&lt;BR /&gt;&lt;BR /&gt;One hour latter, again the same issue.&lt;BR /&gt;&lt;BR /&gt;Then I look at fc switch and I discovered the port where msl6000 is attached in In_Sync state many many time.&lt;BR /&gt;&lt;BR /&gt;I tried changing the port ... with no succesfull result.&lt;BR /&gt;&lt;BR /&gt;How can I test fc from MSL6000 ? It is possible to know if its hba (or like it is named) is working fine?&lt;BR /&gt;&lt;BR /&gt;Do you know what In_sync is mean ?&lt;BR /&gt;&lt;BR /&gt;Thank you very much, any help is appreciated</description>
      <pubDate>Thu, 05 Nov 2009 10:35:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528314#M24888</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-05T10:35:51Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528315#M24889</link>
      <description>May this  could be caused by licenses issues ?&lt;BR /&gt;&lt;BR /&gt;My port is in In_sync when it doesn't work.&lt;BR /&gt;&lt;BR /&gt;When I turn off and turn on MSL6000 it works 1 hour more or less then port state go to In_sync.&lt;BR /&gt;&lt;BR /&gt;My system tells:&lt;BR /&gt;Nov  5 11:52:42 backup kernel: lpfc 0000:03:01.0: 0:0203 Nodev timeout on WWPN 10:0:0:e0:2:23:a7:c5 NPort x11500 Data: x2000008 x7 x6&lt;BR /&gt;Nov  5 11:52:47 backup kernel:  rport-0:0-8: blocked FC remote port time out: removing target and saving binding&lt;BR /&gt;&lt;BR /&gt;And in brocade manual switch I can read (Add Configuring Dynamic Ports on Demand Section):&lt;BR /&gt;If the switch detects more active links than allowed by the current POD licenses, then some ports will&lt;BR /&gt;not be assigned a POD license. Ports that do not receive a POD assignments have a state of No Sync or&lt;BR /&gt;In Sync; these ports are not allowed to progress to the online state. Ports that cannot be brought online&lt;BR /&gt;because insufficient POD licenses have a state of (No POD License) Disabled. (Use the switchShow&lt;BR /&gt;command to display the port states.)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&amp;gt; licenseshow&lt;BR /&gt;bycSQQezz9czdTRM:&lt;BR /&gt;    Web license&lt;BR /&gt;    Zoning license&lt;BR /&gt;    Fabric license&lt;BR /&gt;RRycezeSRSSi3dfZ:&lt;BR /&gt;    Full Ports on Demand license - additional 16 port upgrade&lt;BR /&gt;&lt;BR /&gt;However:&lt;BR /&gt;&amp;gt; licenseport --show&lt;BR /&gt;licenseport failed : this command is not supported on this product.&lt;BR /&gt;&lt;BR /&gt;It is a license issue ?&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Thu, 05 Nov 2009 12:12:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528315#M24889</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-05T12:12:43Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528316#M24890</link>
      <description>First I would update the NSR firmware and check the FC settings of the NSR. Point your browser to the NSR management page.</description>
      <pubDate>Thu, 05 Nov 2009 13:34:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528316#M24890</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-05T13:34:53Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528317#M24891</link>
      <description>How can I know the nsr ip ?&lt;BR /&gt;&lt;BR /&gt;I can log in msl6000 by web where I can see the next menus:&lt;BR /&gt;&lt;BR /&gt;Status&lt;BR /&gt;Move Media&lt;BR /&gt;Setup&lt;BR /&gt;Functions&lt;BR /&gt;History&lt;BR /&gt;&lt;BR /&gt;I think that is not the nsr web, isn't?&lt;BR /&gt;&lt;BR /&gt;Thank you very much</description>
      <pubDate>Thu, 05 Nov 2009 15:35:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528317#M24891</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-05T15:35:09Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528318#M24892</link>
      <description>The NSR (network storage router) is the card next to the library controller. The default is DHCP - name "Router".&lt;BR /&gt;&lt;BR /&gt;You can also connect the serial cable to a PC's COM port and connect via terminal emulator (e.g. putty) with 115200 as speed.</description>
      <pubDate>Thu, 05 Nov 2009 15:48:26 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528318#M24892</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-05T15:48:26Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528319#M24893</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I tried to sniff with a wire dhcp petitions (turning off and turning on NSR), but I couldn't get any packet.&lt;BR /&gt;&lt;BR /&gt;Too I tried to go to 1.1.1.1 (default ip but it didn't reply)&lt;BR /&gt;&lt;BR /&gt;So I guess my only posibility to update the firmware is using a serial wire, which I haven't in this moment. I'll wait to have one to continue...&lt;BR /&gt;&lt;BR /&gt;If is there any possibility to continue without serial wire, please tell me which .&lt;BR /&gt;&lt;BR /&gt;Thank you very much.</description>
      <pubDate>Mon, 09 Nov 2009 15:56:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528319#M24893</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-09T15:56:38Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528320#M24894</link>
      <description>As said, with newer firmware (since some years) the default setting is DHCP (name: Router). If the deice did not get an IP, you cannot access via network. &lt;BR /&gt;&lt;BR /&gt;The serial cable was delivered with the device, have a look.</description>
      <pubDate>Mon, 09 Nov 2009 16:29:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528320#M24894</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-09T16:29:41Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528321#M24895</link>
      <description>I connected through hyperterminal / minicom and no response from nsr. &lt;BR /&gt;&lt;BR /&gt;I configured the connexion like says the manual.&lt;BR /&gt;&lt;BR /&gt;Any tip more ?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 24 Nov 2009 13:05:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528321#M24895</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-24T13:05:38Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528322#M24896</link>
      <description>Did you use the correct speed setting and the _correct_ cable? The cable is different from the MSL cable!</description>
      <pubDate>Tue, 24 Nov 2009 13:18:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528322#M24896</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-24T13:18:02Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528323#M24897</link>
      <description>I connected with a usb-serial cable to other cable "connector which I don't known how it is named in msr"-serial.&lt;BR /&gt;&lt;BR /&gt;One extreme was male and the other female.&lt;BR /&gt;&lt;BR /&gt;The speed was 115200&lt;BR /&gt;&lt;BR /&gt;Thank you</description>
      <pubDate>Tue, 24 Nov 2009 14:35:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528323#M24897</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-24T14:35:41Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528324#M24898</link>
      <description>3 possibilities:&lt;BR /&gt;&lt;BR /&gt;1) still wrong canle&lt;BR /&gt;2) wrong speed (maybe modified)&lt;BR /&gt;3) NSR is frozen</description>
      <pubDate>Tue, 24 Nov 2009 14:39:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528324#M24898</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-24T14:39:31Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528325#M24899</link>
      <description>Maybe I'm using a not valid manual.&lt;BR /&gt;&lt;BR /&gt;Do you have the link to it ?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 24 Nov 2009 14:53:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528325#M24899</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-24T14:53:00Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528326#M24900</link>
      <description>Which mode is Â¿full or null?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 24 Nov 2009 15:02:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528326#M24900</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-24T15:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528327#M24901</link>
      <description>full or null?</description>
      <pubDate>Tue, 24 Nov 2009 15:05:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528327#M24901</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-24T15:05:58Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528328#M24902</link>
      <description>Sorry, my mistake.&lt;BR /&gt;&lt;BR /&gt;I wanted to say "cross" or "direct" cable.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Tue, 24 Nov 2009 15:58:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528328#M24902</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-24T15:58:12Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528329#M24903</link>
      <description>There are 2 cables delivered with the lib - both look very similar. They are RJ11 on both sides + a small converter box.&lt;BR /&gt;&lt;BR /&gt;One is for the lib controller, the other is for the NSR. The pinout is different.</description>
      <pubDate>Tue, 24 Nov 2009 16:08:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528329#M24903</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-24T16:08:24Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528330#M24904</link>
      <description>I understand then, I need a "direct" usb-serial cable, isn't it?</description>
      <pubDate>Tue, 24 Nov 2009 16:15:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528330#M24904</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-24T16:15:39Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528331#M24905</link>
      <description>The "device offline" message may point to a problem with the NSR. &lt;BR /&gt;&lt;BR /&gt;However, if no network or serial connection possible now, I would try to discover the device with LTT and update the firmware.&lt;BR /&gt;&lt;BR /&gt;BTW, the web interface and the FTP interface will give access to the config in order to save - you should consider to do this.</description>
      <pubDate>Tue, 24 Nov 2009 16:22:48 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528331#M24905</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-24T16:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528332#M24906</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Do you mean &lt;A href="http://h18000.www1.hp.com/products/storageworks/ltt/index.html" target="_blank"&gt;http://h18000.www1.hp.com/products/storageworks/ltt/index.html&lt;/A&gt; ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 25 Nov 2009 07:22:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528332#M24906</guid>
      <dc:creator>i5513</dc:creator>
      <dc:date>2009-11-25T07:22:52Z</dc:date>
    </item>
    <item>
      <title>Re: Problem with MSL6000 and In_sync state in switch fc 300</title>
      <link>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528333#M24907</link>
      <description>Exactly.&lt;BR /&gt;&lt;BR /&gt;If your NSR is presented to outside, LTT is able to update.</description>
      <pubDate>Wed, 25 Nov 2009 07:26:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storeever-tape-storage/problem-with-msl6000-and-in-sync-state-in-switch-fc-300/m-p/4528333#M24907</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2009-11-25T07:26:20Z</dc:date>
    </item>
  </channel>
</rss>

