<?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 ssh key isn't surviving a reboot in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ssh-key-isn-t-surviving-a-reboot/m-p/49534#M13159</link>
    <description>Create Date: Aug 29 2013 12:19PM&lt;BR /&gt;
&lt;BR /&gt;
I have one Summit which refuses to preserve its ssh key after a reboot. This is the case even after upgrading the firmware (including the ssh.xmod) and disabling and reenabling ssh. I've even tried providing a pregenerated key. (and saving before rebooting of course).&lt;BR /&gt;
&lt;BR /&gt;
After upgrading several switches, using the same procedure for all of them, one of those switches is now also exhibiting this symptom, while the rest all went fine. The new switch in question was upgraded from 15.3.1.4 to 15.3.2.11p1-2, and ssh was working fine before the upgrade.&lt;BR /&gt;
&lt;BR /&gt;
Is the key stored in a particular (apparently hidden) file? Where can I look or what can I do to fix this?&lt;BR /&gt;
&lt;BR /&gt;
I just tried:&lt;BR /&gt;
dis ssh&lt;BR /&gt;
save&lt;BR /&gt;
reboot&lt;BR /&gt;
en ssh&lt;BR /&gt;
yes (10 minute key generation)&lt;BR /&gt;
save&lt;BR /&gt;
show ssh2 priv (shows that the key is there&lt;BR /&gt;
reboot&lt;BR /&gt;
&lt;BR /&gt;
But that didn't work either; after the reboot: show ssh2 priv (just a blank line) and attempts to ssh to the switch are rejected.&lt;BR /&gt;
&lt;BR /&gt;
sho cpu | include ssh&lt;BR /&gt;
exsshd        0.0  0.0  0.0  0.0  4.8  0.8  0.4 99.9     0.10       0.15&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
  (from xxiii)</description>
    <pubDate>Wed, 08 Jan 2014 08:56:00 GMT</pubDate>
    <dc:creator>EtherNation_Use</dc:creator>
    <dc:date>2014-01-08T08:56:00Z</dc:date>
    <item>
      <title>ssh key isn't surviving a reboot</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ssh-key-isn-t-surviving-a-reboot/m-p/49534#M13159</link>
      <description>Create Date: Aug 29 2013 12:19PM&lt;BR /&gt;
&lt;BR /&gt;
I have one Summit which refuses to preserve its ssh key after a reboot. This is the case even after upgrading the firmware (including the ssh.xmod) and disabling and reenabling ssh. I've even tried providing a pregenerated key. (and saving before rebooting of course).&lt;BR /&gt;
&lt;BR /&gt;
After upgrading several switches, using the same procedure for all of them, one of those switches is now also exhibiting this symptom, while the rest all went fine. The new switch in question was upgraded from 15.3.1.4 to 15.3.2.11p1-2, and ssh was working fine before the upgrade.&lt;BR /&gt;
&lt;BR /&gt;
Is the key stored in a particular (apparently hidden) file? Where can I look or what can I do to fix this?&lt;BR /&gt;
&lt;BR /&gt;
I just tried:&lt;BR /&gt;
dis ssh&lt;BR /&gt;
save&lt;BR /&gt;
reboot&lt;BR /&gt;
en ssh&lt;BR /&gt;
yes (10 minute key generation)&lt;BR /&gt;
save&lt;BR /&gt;
show ssh2 priv (shows that the key is there&lt;BR /&gt;
reboot&lt;BR /&gt;
&lt;BR /&gt;
But that didn't work either; after the reboot: show ssh2 priv (just a blank line) and attempts to ssh to the switch are rejected.&lt;BR /&gt;
&lt;BR /&gt;
sho cpu | include ssh&lt;BR /&gt;
exsshd        0.0  0.0  0.0  0.0  4.8  0.8  0.4 99.9     0.10       0.15&lt;BR /&gt;
&lt;BR /&gt;
&lt;BR /&gt;
  (from xxiii)</description>
      <pubDate>Wed, 08 Jan 2014 08:56:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ssh-key-isn-t-surviving-a-reboot/m-p/49534#M13159</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T08:56:00Z</dc:date>
    </item>
  </channel>
</rss>

