<?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: DS25 Problems... in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190293#M95807</link>
    <description>Which model A or B?&lt;BR /&gt;&lt;BR /&gt;Have you tried to access the system through RMC? If nothing works RMC should answer up with just AC plugged in. Check the system using env and status commands in RMC. &lt;BR /&gt;&lt;BR /&gt;Chapter 6:&lt;BR /&gt;&lt;A href="http://www.compaq.com/alphaserver/download/ek-ds250-ug-d01.pdf" target="_blank"&gt;http://www.compaq.com/alphaserver/download/ek-ds250-ug-d01.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If RMC corruption is suspect, then check the system modules jumpers and switches to make sure they match the correct system configuration for the CPU installed per the service guide. You may have to reflash the system from Fail-safe mode.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 29 Jul 2009 17:25:55 GMT</pubDate>
    <dc:creator>cnb</dc:creator>
    <dc:date>2009-07-29T17:25:55Z</dc:date>
    <item>
      <title>DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190290#M95804</link>
      <description>I bought a one CPU DS25 on eBay. Before it was sent to me they removed the 2nd CPU and said they had made no other changes.&lt;BR /&gt;When I try to start it up I get&lt;BR /&gt;2 1 2 Beeps&lt;BR /&gt;1 3 3 Beeps&lt;BR /&gt;The first 3 LEDs are lite up, which makes no sense.&lt;BR /&gt; &lt;BR /&gt;I opened the box and everything looks good. The remaining CPU is in slot 0. The 2GB of memory (4 x 512MB) are in memory array 0. There are no options in the PCI slots.&lt;BR /&gt;&lt;BR /&gt;Any ideas</description>
      <pubDate>Wed, 29 Jul 2009 16:31:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190290#M95804</guid>
      <dc:creator>Stephen C. Jackson</dc:creator>
      <dc:date>2009-07-29T16:31:02Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190291#M95805</link>
      <description>2-1-2 says Configuration error on CPU or system configuration error.&lt;BR /&gt;&lt;BR /&gt;1-3-3 says No Usable memory detected.&lt;BR /&gt;&lt;BR /&gt;L1, L2, L3 lit up means Bad RMC Flash&lt;BR /&gt;&lt;BR /&gt;I just pulled those off the owner's manual.&lt;BR /&gt;&lt;BR /&gt;I'd say check and reseat the memory dimms first.&lt;BR /&gt;</description>
      <pubDate>Wed, 29 Jul 2009 16:50:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190291#M95805</guid>
      <dc:creator>EdgarZamora</dc:creator>
      <dc:date>2009-07-29T16:50:09Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190292#M95806</link>
      <description>I have the same manual and I am aware of what the beeps and leds mean.&lt;BR /&gt;&lt;BR /&gt;I reset all the memory before I posed the forum questions.&lt;BR /&gt;&lt;BR /&gt;Any other ideas?&lt;BR /&gt;</description>
      <pubDate>Wed, 29 Jul 2009 16:58:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190292#M95806</guid>
      <dc:creator>Stephen C. Jackson</dc:creator>
      <dc:date>2009-07-29T16:58:06Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190293#M95807</link>
      <description>Which model A or B?&lt;BR /&gt;&lt;BR /&gt;Have you tried to access the system through RMC? If nothing works RMC should answer up with just AC plugged in. Check the system using env and status commands in RMC. &lt;BR /&gt;&lt;BR /&gt;Chapter 6:&lt;BR /&gt;&lt;A href="http://www.compaq.com/alphaserver/download/ek-ds250-ug-d01.pdf" target="_blank"&gt;http://www.compaq.com/alphaserver/download/ek-ds250-ug-d01.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;If RMC corruption is suspect, then check the system modules jumpers and switches to make sure they match the correct system configuration for the CPU installed per the service guide. You may have to reflash the system from Fail-safe mode.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 29 Jul 2009 17:25:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190293#M95807</guid>
      <dc:creator>cnb</dc:creator>
      <dc:date>2009-07-29T17:25:55Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190294#M95808</link>
      <description>I've not tried to run an AlphaServer DS25 with one CPU.&lt;BR /&gt;&lt;BR /&gt;And with what the occasional misadventures that can arise with eBay and with shipping and with the removal of the CPU, the operational pedigree of the hardware here is somewhat questionable.&lt;BR /&gt;&lt;BR /&gt;Burn a current AlphaServer firmware CD-ROM.&lt;BR /&gt;&lt;BR /&gt;Use the failsafe loader (FSL, or sometimes Failsafe Boot FSB) to re-flash the system, and to also reset the RMC to factory.&lt;BR /&gt;&lt;BR /&gt;Details of both are in the AlphaServer DS25 User's Guide.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 29 Jul 2009 17:35:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190294#M95808</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-07-29T17:35:06Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190295#M95809</link>
      <description>I have changed the FSB jumper and got the same response - nothing at the console still.</description>
      <pubDate>Wed, 29 Jul 2009 18:19:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190295#M95809</guid>
      <dc:creator>Stephen C. Jackson</dc:creator>
      <dc:date>2009-07-29T18:19:34Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190296#M95810</link>
      <description>&amp;gt;I have changed the FSB jumper and got the same response - nothing at the console still.&lt;BR /&gt;&lt;BR /&gt;To confirm the "nothing" here and the status, you're on the COM1 serial line, you've reset the RMC to factory, and you've tried to reload the firmware using the FSL, and you've (still) received a fault indication?&lt;BR /&gt;&lt;BR /&gt;If so and then based on your other comments around re-seating all modules, etc, then I think the box is busted.  Or it considers itself busted, due to the removal of the CPU.</description>
      <pubDate>Wed, 29 Jul 2009 18:35:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190296#M95810</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-07-29T18:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190297#M95811</link>
      <description>Have you tried connecting a serial terminal to the *modem* (bottom or left 9-pin rs-232 depending on system orientation) port (9600,8,N) and issuing the RMC sequence per the manual?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;^[^[ rmc&lt;BR /&gt;&lt;BR /&gt;This *should* get a response as long as AC is plugged in. &lt;BR /&gt;&lt;BR /&gt;Hope this helps.</description>
      <pubDate>Wed, 29 Jul 2009 18:40:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190297#M95811</guid>
      <dc:creator>cnb</dc:creator>
      <dc:date>2009-07-29T18:40:14Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190298#M95812</link>
      <description>You've mentioned that you get no console response, but have you actually tried to get to the RMC?  Press ctrl-[ ctrl-[ RMC (to get the RMC prompt.)&lt;BR /&gt;</description>
      <pubDate>Wed, 29 Jul 2009 18:40:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190298#M95812</guid>
      <dc:creator>EdgarZamora</dc:creator>
      <dc:date>2009-07-29T18:40:30Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190299#M95813</link>
      <description>Just to refresh evryones memory as to what I have tried:&lt;BR /&gt;&lt;BR /&gt;System gives series of beeps. No response at console.&lt;BR /&gt;&lt;BR /&gt;1) System down. Poser on. Connect serial terminal (Reflections - I have used it as a console on other computers)(null-modem) to port 1.  clrl[ ctrl[ RMC gives me no response from computer. I have not set RMC switches to default.&lt;BR /&gt;&lt;BR /&gt;2) Changed FSB jummper J25 to 2 &amp;amp; 3. System gave me same beep errors as before. No response at console terminal.&lt;BR /&gt;&lt;BR /&gt;3) Tried other memory - as before.&lt;BR /&gt;&lt;BR /&gt;Any other ideas?</description>
      <pubDate>Wed, 29 Jul 2009 19:14:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190299#M95813</guid>
      <dc:creator>Stephen C. Jackson</dc:creator>
      <dc:date>2009-07-29T19:14:17Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190300#M95814</link>
      <description>Looks to be firmly DOA.  Call the seller?</description>
      <pubDate>Wed, 29 Jul 2009 19:42:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190300#M95814</guid>
      <dc:creator>Hoff</dc:creator>
      <dc:date>2009-07-29T19:42:27Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190301#M95815</link>
      <description>More ideas...&lt;BR /&gt;&lt;BR /&gt;Verify 20-01EBA-09 512MB dimms are installed.&lt;BR /&gt;&lt;BR /&gt;Verify Clock and TIG switch settings.&lt;BR /&gt;&lt;BR /&gt;Clear RMC via J66.&lt;BR /&gt;&lt;BR /&gt;Try to access RMC from the other port.&lt;BR /&gt;&lt;BR /&gt;Install J68 1-2 to direct all traffic through the RMC, move the console cable and then issue the rmc escape sequence ^[^[rmc&lt;BR /&gt;&lt;BR /&gt;-or-&lt;BR /&gt;&lt;BR /&gt;Change J46 to load TIG from SROM.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-or-&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;From the Service Manual:&lt;BR /&gt;&lt;BR /&gt;3.5 Forcing a Fail-Safe Load&lt;BR /&gt;The fail-safe booter (FSB) is another variant of the SRM console. The&lt;BR /&gt;FSB provides an emergency recovery mechanism if the firmware image&lt;BR /&gt;contained in flash memory becomes corrupted. You can run the FSB&lt;BR /&gt;and boot another image from a CD-ROM or network that is capable of&lt;BR /&gt;reprogramming the flash ROM.&lt;BR /&gt;Use the FSB when one of the following failures at power-up prohibits you from&lt;BR /&gt;getting to the console program:&lt;BR /&gt;Ã¢Â Â¢ Firmware image in flash memory corrupted&lt;BR /&gt;Ã¢Â Â¢ Power failure or accidental power-down during a firmware upgrade&lt;BR /&gt;Ã¢Â Â¢ Error in the nonvolatile RAM (NVRAM) file&lt;BR /&gt;Ã¢Â Â¢ Incorrect environment variable setting&lt;BR /&gt;Ã¢Â Â¢ Driver error&lt;BR /&gt;3.5.1 Starting the FSB Automatically&lt;BR /&gt;If the firmware image is unavailable when the system is powered on or reset,&lt;BR /&gt;the FSB runs automatically.&lt;BR /&gt;1. Reset the system to restart the FSB. The FSB loads from the flash.&lt;BR /&gt;2. Update the firmware as described in Chapter 7.&lt;BR /&gt;3.5.2 Starting the FSB Manually&lt;BR /&gt;1. Power the system off, unplug the power supplies, and remove the cover.&lt;BR /&gt;2. Remove CPU0 to gain access to J25 jumper on the system board. See&lt;BR /&gt;Chapter 8.&lt;BR /&gt;3. Move jumper from pins 1-2 to 2-3 on J25.&lt;BR /&gt;4. Reconnect CPU0.&lt;BR /&gt;5. Reconnect the power supplies and reinstall the system cover. Power up the&lt;BR /&gt;system to the FSB console.&lt;BR /&gt;&lt;BR /&gt;3.6 Updating the RMC&lt;BR /&gt;Under certain circumstances, the RMC will not function. If the&lt;BR /&gt;problem is caused by corrupted RMC flash ROM, you need to update&lt;BR /&gt;RMC firmware.&lt;BR /&gt;The RMC will not function if:&lt;BR /&gt;Ã¢Â Â¢ No AC power is provided to any of the power supplies.&lt;BR /&gt;Ã¢Â Â¢ DPR does not pass its self-test (DPR is corrupted).&lt;BR /&gt;Ã¢Â Â¢ RMC flash ROM is corrupted, but the system will still power-up.&lt;BR /&gt;If the RMC is not working, the control panel displays the following message:&lt;BR /&gt;Bad RMC flash&lt;BR /&gt;The SRM console also sends a message to the terminal screen:&lt;BR /&gt;*** Error - RMC detected power up error - RMC Flash corrupted ***&lt;BR /&gt;******************************************&lt;BR /&gt;NOTE: If the RMC is corrupt, you may not get an output from COM1. If this&lt;BR /&gt;occurs, remove J68 and move the serial line to the COM2 port.&lt;BR /&gt;******************************************&lt;BR /&gt;You can update the remote management console firmware from flash ROM&lt;BR /&gt;using the LFU.&lt;BR /&gt;1. Load the update medium.&lt;BR /&gt;2. At the UPD&amp;gt; prompt, exit from the update utility, and answer y to the&lt;BR /&gt;manual update prompt. Enter update RMC to update the firmware.&lt;BR /&gt;UPD&amp;gt; exit&lt;BR /&gt;Do you want to do a manual update [y/(n)] y&lt;BR /&gt;***** Loadable Firmware Update Utility *****&lt;BR /&gt;-------------------------------------------------------------&lt;BR /&gt;Function Description&lt;BR /&gt;-------------------------------------------------------------&lt;BR /&gt;Display Displays the systemâ  s configuration table.&lt;BR /&gt;Exit Done exit LFU (reset).&lt;BR /&gt;List Lists the device, revision, firmware name, and&lt;BR /&gt;update revision.&lt;BR /&gt;Readme Lists important release information.&lt;BR /&gt;Update Replaces current firmware with loadable data&lt;BR /&gt;image.&lt;BR /&gt;Verify Compares loadable and hardware images.&lt;BR /&gt;? or Help Scrolls this function table.&lt;BR /&gt;-----------------------------------------------------------&lt;BR /&gt;UPD&amp;gt; update RMC&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;.&lt;BR /&gt;&lt;BR /&gt;After updating the RMC you should regain console functionality and can update the remainder of the system f/w using the manual update procedures. &lt;BR /&gt;&lt;BR /&gt;fwiw:&lt;BR /&gt;&lt;BR /&gt;This *WILL* work if your emulation software is mapped and passing the correct escape sequence to the port. Otherwise, suggest using a direct attached VT serial terminal to the port(s) mentioned above if the console port is not producing output.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;LED 1 LED 2 LED 3 LED 4 Power-Up Message &lt;BR /&gt;ON ON ON Off Bad RMC flash [ 1 ] &lt;BR /&gt;&lt;BR /&gt;Note 1: If the RMC flash is bad the system will still come up, however the bad RMC flash LED will remain lit until a new RMC flash image is loaded. RMC will not have full functionality, use COM2 or VGA display to flash the RMC.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;-or-&lt;BR /&gt;&lt;BR /&gt;Just replace the system and cpu modules ;-)&lt;BR /&gt;&lt;BR /&gt;HTH</description>
      <pubDate>Wed, 29 Jul 2009 20:14:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190301#M95815</guid>
      <dc:creator>cnb</dc:creator>
      <dc:date>2009-07-29T20:14:29Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190302#M95816</link>
      <description>Please don't think I am ignoring your responses. I will be out of town and will look at this again next Tuesday.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Wed, 29 Jul 2009 21:00:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190302#M95816</guid>
      <dc:creator>Stephen C. Jackson</dc:creator>
      <dc:date>2009-07-29T21:00:14Z</dc:date>
    </item>
    <item>
      <title>Re: DS25 Problems...</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190303#M95817</link>
      <description>I have decided to close this thread and award points. The problem was not solved and I am sending it back.&lt;BR /&gt;&lt;BR /&gt;Thanks for your help.&lt;BR /&gt;Stephen Jackson</description>
      <pubDate>Thu, 06 Aug 2009 22:34:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/ds25-problems/m-p/5190303#M95817</guid>
      <dc:creator>Stephen C. Jackson</dc:creator>
      <dc:date>2009-08-06T22:34:42Z</dc:date>
    </item>
  </channel>
</rss>

