<?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 How to make suspended device functional from other peer in General Topics</title>
    <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-make-suspended-device-functional-from-other-peer/m-p/248955#M70820</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We were&amp;nbsp;attempting a firmware update to&amp;nbsp;HA pair. After upgrading the passive peer, we confirmed it was up and the user-id was populated and then suspended the active peer in order to update that. Unfortunately it turns out that management was only enabled on the WAN interface of the originally active peer meaning we can no longer access the suspended peer.&lt;/P&gt;&lt;P&gt;We’ve been able to ping it via the HA IP address and I can SSH via port 28 to the HA IP address but none of the credentials we’ve tried work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Short of going on-site and physically connecting to the management port, is there any way to bring the peer out of a suspended state from the other peer?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
    <pubDate>Wed, 06 Feb 2019 01:55:47 GMT</pubDate>
    <dc:creator>FarzanaMustafa</dc:creator>
    <dc:date>2019-02-06T01:55:47Z</dc:date>
    <item>
      <title>How to make suspended device functional from other peer</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-make-suspended-device-functional-from-other-peer/m-p/248955#M70820</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We were&amp;nbsp;attempting a firmware update to&amp;nbsp;HA pair. After upgrading the passive peer, we confirmed it was up and the user-id was populated and then suspended the active peer in order to update that. Unfortunately it turns out that management was only enabled on the WAN interface of the originally active peer meaning we can no longer access the suspended peer.&lt;/P&gt;&lt;P&gt;We’ve been able to ping it via the HA IP address and I can SSH via port 28 to the HA IP address but none of the credentials we’ve tried work.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Short of going on-site and physically connecting to the management port, is there any way to bring the peer out of a suspended state from the other peer?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance!&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 01:55:47 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-make-suspended-device-functional-from-other-peer/m-p/248955#M70820</guid>
      <dc:creator>FarzanaMustafa</dc:creator>
      <dc:date>2019-02-06T01:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: How to make suspended device functional from other peer</title>
      <link>https://live.paloaltonetworks.com/t5/general-topics/how-to-make-suspended-device-functional-from-other-peer/m-p/248973#M70823</link>
      <description>&lt;P&gt;&lt;a href="https://live.paloaltonetworks.com/t5/user/viewprofilepage/user-id/98673"&gt;@FarzanaMustafa&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Unfortunately, by design, once you've suspended the firewall that's sort of it. If you could have someone physically restart the box by pulling the plug and completely power cycling the device, then HA is functional again once it comes back online. If you have someone on-site that could actually identify the proper device with certainty that might be the way to go?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Feb 2019 03:27:04 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/general-topics/how-to-make-suspended-device-functional-from-other-peer/m-p/248973#M70823</guid>
      <dc:creator>BPry</dc:creator>
      <dc:date>2019-02-06T03:27:04Z</dc:date>
    </item>
  </channel>
</rss>

