<?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: Console Access in Communications and Wireless</title>
    <link>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469352#M7</link>
    <description>I solved the problem. I bought a Cabletron switch with FDDI backbone A B connectors. It does what I want it to do. &lt;BR /&gt; &lt;BR /&gt;Thanks anyway, &lt;BR /&gt;Todd MCSE, ASE</description>
    <pubDate>Sun, 11 Feb 2001 00:00:00 GMT</pubDate>
    <dc:creator>Ayman Altounji</dc:creator>
    <dc:date>2001-02-11T00:00:00Z</dc:date>
    <item>
      <title>Console Access</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469349#M4</link>
      <description>I give up! I have been trying for a week to use a null modem cable to connect to a 5226A switch that I have. I need to assign it an IP address so that I can use the CNMS to manage the beast while it is on the lan.  &lt;BR /&gt; &lt;BR /&gt;So far I have tried 2 different cables, and 4 different computers. Nothing seems to work. I was able to get this to work once before. Then, while trying to diagnose an extremely sluggish performance issue, I removed the IP thinking that it would be rather easy to assign another one once I was able to solve the problem. Well, I never solved the problem, and I want to use this switch to create a series of VLANs for an Internet project I have recently started.  &lt;BR /&gt; &lt;BR /&gt;I have thoroughly read the doc on this switch, and I have tried to use the oldest and newest hyperterminal application that I can get my hands on. The settings have been 9600,8,N,1,None per the documentation. It also says to type vt100 when the terminal opens, and I would then be able to get to the login screen the then access the setup. I have tried every possible combination trying to get this to work and it will not.  &lt;BR /&gt; &lt;BR /&gt;I have opened the unit (the warrenty expired a long time ago, so what the hey....) and there is an SW1 switch and a single 3 post jumper in there. &lt;BR /&gt; &lt;BR /&gt;Is there some way that I can use these to revert back to the default configuration? something like an NVRAM clear, or the like? &lt;BR /&gt; &lt;BR /&gt;I would really love to know.  &lt;BR /&gt;Thanks,  &lt;BR /&gt;Todd Hayward MCSE ASE</description>
      <pubDate>Fri, 01 Dec 2000 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469349#M4</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2000-12-01T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Console Access</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469350#M5</link>
      <description>Is this switch coming up fully (i.e. scanning ports) or are the LEDS stuck on a port or flashing?&lt;BR /&gt;&lt;BR /&gt;Are you not using BOOTP on this network (when no IP is assigned, the switch should ask for one)?</description>
      <pubDate>Mon, 18 Dec 2000 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469350#M5</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2000-12-18T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Console Access</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469351#M6</link>
      <description>Yes, the switch seems to initialize correctly. there is nothing that I can do to ping an address it might have taken from dhcp. I tried to give it an IP by associating a number in my local arp cache, then telnet to it, but that failed too. I simply cannot access the console anymore. Not over the LAN, not from a serial or null-modem to the DB9 (rs-232) in the back of the unit.  &lt;BR /&gt;  &lt;BR /&gt;Anything else I can try before I toss the beast into the trash?  &lt;BR /&gt;  &lt;BR /&gt;Todd Hayward, MCSE Compaq ASE</description>
      <pubDate>Sat, 27 Jan 2001 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469351#M6</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-01-27T00:00:00Z</dc:date>
    </item>
    <item>
      <title>Re: Console Access</title>
      <link>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469352#M7</link>
      <description>I solved the problem. I bought a Cabletron switch with FDDI backbone A B connectors. It does what I want it to do. &lt;BR /&gt; &lt;BR /&gt;Thanks anyway, &lt;BR /&gt;Todd MCSE, ASE</description>
      <pubDate>Sun, 11 Feb 2001 00:00:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/communications-and-wireless/console-access/m-p/2469352#M7</guid>
      <dc:creator>Ayman Altounji</dc:creator>
      <dc:date>2001-02-11T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

