<?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: DataProtector - exchanger control device in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453800#M10464</link>
    <description>Without knowing much about your configuration, I would check the fibre channel switch if the library is connected to the same fibre channel switch like your EVA's controller A, Port_2.</description>
    <pubDate>Mon, 03 Jan 2005 03:11:18 GMT</pubDate>
    <dc:creator>Uwe Zessin</dc:creator>
    <dc:date>2005-01-03T03:11:18Z</dc:date>
    <item>
      <title>DataProtector - exchanger control device</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453799#M10463</link>
      <description>Here is the error message that I get when my DataProtector tries to take backup my Oracle DB.&lt;BR /&gt;&lt;BR /&gt;-----------&lt;BR /&gt;[Critical] From: BMA@host1 "HP:MSL6000_1_host1"  Time: 1/1/2005 11:04:46 Î¼Î¼&lt;BR /&gt;[90:59]      host1:/dev/rac/c5t0d0&lt;BR /&gt;    Cannot open exchanger control device ([6] No such device or address)&lt;BR /&gt;&lt;BR /&gt;Decription:&lt;BR /&gt;&lt;BR /&gt; The xMA could not open the specified exchanger control device. The &lt;BR /&gt;error message indicates the reason as reported by the OS. &lt;BR /&gt;Frequently, a 'No such device or address' message from an exchanger &lt;BR /&gt;control device indicates that a wrong device file is specified for this &lt;BR /&gt;device. In the SAN environment the reason for this message can be a  &lt;BR /&gt;changed SCSI address of the device that occurred in SAN. This could  &lt;BR /&gt;happen if a reset in the SAN occurred through a reboot or power  &lt;BR /&gt;failure.  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Action:&lt;BR /&gt;&lt;BR /&gt; Verify that the control device file exists on the appropriate host &lt;BR /&gt;and can be accessed by the xMA process. Check if device file in  &lt;BR /&gt;device configuration is correct. &lt;BR /&gt;-----------&lt;BR /&gt;&lt;BR /&gt;Also I checked my EVA and I noticed that in my Controller A the Port 2 has Operational State:Failed and Connection State:Link to switch failed but Port 1 is OK.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;I have attached all the log files that might be helpful.&lt;BR /&gt;Any suggestion to my probl</description>
      <pubDate>Mon, 03 Jan 2005 02:37:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453799#M10463</guid>
      <dc:creator>ATHANASOPOULOS PANAGIOT</dc:creator>
      <dc:date>2005-01-03T02:37:55Z</dc:date>
    </item>
    <item>
      <title>Re: DataProtector - exchanger control device</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453800#M10464</link>
      <description>Without knowing much about your configuration, I would check the fibre channel switch if the library is connected to the same fibre channel switch like your EVA's controller A, Port_2.</description>
      <pubDate>Mon, 03 Jan 2005 03:11:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453800#M10464</guid>
      <dc:creator>Uwe Zessin</dc:creator>
      <dc:date>2005-01-03T03:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: DataProtector - exchanger control device</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453801#M10465</link>
      <description>Hi,&lt;BR /&gt;Is the devicefile correct ? Try:&lt;BR /&gt;/opt/omni/lbin/uma -ioctl /dev/rac/c5t0d0&lt;BR /&gt;&lt;BR /&gt;If it don't work, do a :&lt;BR /&gt;ioscan -fnC&lt;BR /&gt;&lt;BR /&gt;Is the robotics listed and, is any devicefile for the robotics listed ?&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Jan 2005 03:17:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453801#M10465</guid>
      <dc:creator>Leif Halvarsson_2</dc:creator>
      <dc:date>2005-01-03T03:17:20Z</dc:date>
    </item>
    <item>
      <title>Re: DataProtector - exchanger control device</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453802#M10466</link>
      <description>The first command line "/dev/omni..." appears me an error similar with the DP error. With "ioscan -funC autoch" I can find the MSL6000 device and the /dev/rac/c5t0d0.</description>
      <pubDate>Mon, 03 Jan 2005 06:14:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453802#M10466</guid>
      <dc:creator>ATHANASOPOULOS PANAGIOT</dc:creator>
      <dc:date>2005-01-03T06:14:10Z</dc:date>
    </item>
    <item>
      <title>Re: DataProtector - exchanger control device</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453803#M10467</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Was the robotics listed as "CLAIMED" ?&lt;BR /&gt;(if not, recreate the devicefiles).&lt;BR /&gt;&lt;BR /&gt;Also, try the "mc" command, just to check that there is nothing wrong with the DP binarys.&lt;BR /&gt;&lt;BR /&gt;It is recommended for DP that the sctl driver should be used instead of schgr but, if everything is ok, you should get response, also with the schgr driver.&lt;BR /&gt;&lt;BR /&gt;The devicefile for the sctl driver has to be created manually (using the mknod command). &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 03 Jan 2005 06:36:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/3453803#M10467</guid>
      <dc:creator>Leif Halvarsson_2</dc:creator>
      <dc:date>2005-01-03T06:36:27Z</dc:date>
    </item>
    <item>
      <title>Re: DataProtector - exchanger control device</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/7233557#M69202</link>
      <description>&lt;P&gt;can you pls. share complete "MC" command&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2025 11:49:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/7233557#M69202</guid>
      <dc:creator>Piyush_Parmar</dc:creator>
      <dc:date>2025-01-22T11:49:53Z</dc:date>
    </item>
    <item>
      <title>Re: DataProtector - exchanger control device</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/7234128#M69203</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/2091641"&gt;@Piyush_Parmar&lt;/a&gt;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you for posting.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You might want to consider creating a new topic by utilizing the "New Discussion" button if you are facing any issues, as this will not only enhance visibility compared to the old topic but also boost your chances of receiving responses from experts.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jan 2025 13:51:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/dataprotector-exchanger-control-device/m-p/7234128#M69203</guid>
      <dc:creator>Sunitha_Mod</dc:creator>
      <dc:date>2025-01-30T13:51:25Z</dc:date>
    </item>
  </channel>
</rss>

