<?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: FWSM admin access issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278020#M833931</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;I am sure that the module is in the slot 3. There are no idle connection on the switch. FWSM code is 3.2.1. But I can't upgrade to 3.2.2 because I don't have access to system context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mvz-rd-csw1-b1a#sh tcp brief all&lt;/P&gt;&lt;P&gt;TCB                 Local Address        Foreign Address  (state)&lt;/P&gt;&lt;P&gt;0x105A2A8              0.0.0.0:23              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1090B40              0.0.0.0:80              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1059420             0.0.0.0:113              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1078C38             0.0.0.0:544              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1058F48            0.0.0.0:1979              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1098E10            0.0.0.0:1989              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1098938            0.0.0.0:1992              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x105A978           10.X.1.Y:23     10.X.28.Y:22498  ESTAB&lt;/P&gt;&lt;P&gt;0x105B53C           10.X.0.Z:23     10.X.48.Z:1121  ESTAB&lt;/P&gt;&lt;P&gt;0x105A780                 ????:23                 ????:0  LISTEN&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Jul 2009 06:08:16 GMT</pubDate>
    <dc:creator>kalashnikovsg</dc:creator>
    <dc:date>2009-07-06T06:08:16Z</dc:date>
    <item>
      <title>FWSM admin access issue</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278018#M833929</link>
      <description>&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;I need to gain access to admin context which is located on FWSM module. I don't know it IP-addresses, because other man performed configuration before me. The command "session slot" didn't help me:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;session slot 3 processor 1&lt;/P&gt;&lt;P&gt;The default escape character is Ctrl-^, then x.&lt;/P&gt;&lt;P&gt;You can also type 'exit' at the remote prompt to end the session&lt;/P&gt;&lt;P&gt;Trying 127.0.0.31 ...&lt;/P&gt;&lt;P&gt;% Connection refused by remote host&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There are two other contexts on it (not admin). I can log to this contexts. But I can't â&amp;#128;&amp;#156;changetoâ&amp;#128;&amp;#157; admin context because of privileges absence. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is the next. Is it possible to log to admin context in my situation without resetting the module? How?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:50:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278018#M833929</guid>
      <dc:creator>kalashnikovsg</dc:creator>
      <dc:date>2019-03-11T15:50:46Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM admin access issue</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278019#M833930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are you sure the module is in slot 3? Could you check on the switch config if telnet is not an allowed transport input under the line vty 0 4 config?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From the swtich you can try to do&lt;/P&gt;&lt;P&gt;     #sh tcp brief all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;    and then&lt;/P&gt;&lt;P&gt;    #clear tcp tcb &lt;TCB of="" the="" idle="" connections=""&gt;&lt;/TCB&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and then try to session in. This is the only way to get to the admin context if you do not remember the IP add to the admin context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are right, you cannot change to  from other context if it is not designated as the admin context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure what code you are running in the FWSM but, read up this defect&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSCsj82547    Management sessions to the FWSM are refused but should be allowed&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;fixed in 3.2.2&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 03 Jul 2009 12:50:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278019#M833930</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2009-07-03T12:50:34Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM admin access issue</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278020#M833931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi!&lt;/P&gt;&lt;P&gt;I am sure that the module is in the slot 3. There are no idle connection on the switch. FWSM code is 3.2.1. But I can't upgrade to 3.2.2 because I don't have access to system context.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mvz-rd-csw1-b1a#sh tcp brief all&lt;/P&gt;&lt;P&gt;TCB                 Local Address        Foreign Address  (state)&lt;/P&gt;&lt;P&gt;0x105A2A8              0.0.0.0:23              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1090B40              0.0.0.0:80              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1059420             0.0.0.0:113              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1078C38             0.0.0.0:544              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1058F48            0.0.0.0:1979              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1098E10            0.0.0.0:1989              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x1098938            0.0.0.0:1992              0.0.0.0:0  LISTEN&lt;/P&gt;&lt;P&gt;0x105A978           10.X.1.Y:23     10.X.28.Y:22498  ESTAB&lt;/P&gt;&lt;P&gt;0x105B53C           10.X.0.Z:23     10.X.48.Z:1121  ESTAB&lt;/P&gt;&lt;P&gt;0x105A780                 ????:23                 ????:0  LISTEN&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Jul 2009 06:08:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278020#M833931</guid>
      <dc:creator>kalashnikovsg</dc:creator>
      <dc:date>2009-07-06T06:08:16Z</dc:date>
    </item>
    <item>
      <title>Re: FWSM admin access issue</title>
      <link>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278021#M833932</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;0x105A978 10.X.1.Y:23 10.X.28.Y:22498 ESTAB&lt;/P&gt;&lt;P&gt;0x105B53C 10.X.0.Z:23 10.X.48.Z:1121 ESTAB &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You would see 127.0.0.31 as the IP address for the module in slot 3. But, I do not see that in the output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you reload the blade I am sure you will be able to session in after which you can upgrade.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you are not sure of the password to session in the only way is to do password recovery. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can read here:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/fwsm/fwsm32/configuration/guide/troubl_f.html#wp1049302" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/fwsm/fwsm32/configuration/guide/troubl_f.html#wp1049302&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Jul 2009 10:25:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fwsm-admin-access-issue/m-p/1278021#M833932</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2009-07-06T10:25:19Z</dc:date>
    </item>
  </channel>
</rss>

