<?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: cannot access 4402 controller management IP in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228903#M53441</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Taken from Cisco 440X Series Wireless LAN Controllers Deployment Guide&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Management Interface&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;The Management interface is the default interface for in-band management of theWLC and connectivity to enterprise services such as AAA servers.  The Management interface is the &lt;B&gt;only consistently "pingable" in-band interface IP address&lt;/B&gt; on the WLC.&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Service-Port Interface&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;The service port interface must have an IP address on a different subnet from the Management, AP Manager, and any dynamic interfaces. The service port can get an IP address via DHCP or it can be assigned a static IP address, but a default-gateway cannot be assigned to the Service-port interface.  The Service-port is typically&lt;/I&gt;&lt;/P&gt;&lt;P&gt;reserved for out-of-band management in the event of a network failure. It is also the only port that is active when the controller is in boot mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.  &lt;I&gt;Please rate when applicable.&lt;/I&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 21 May 2009 03:08:09 GMT</pubDate>
    <dc:creator>Leo Laohoo</dc:creator>
    <dc:date>2009-05-21T03:08:09Z</dc:date>
    <item>
      <title>cannot access 4402 controller management IP</title>
      <link>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228900#M53438</link>
      <description>&lt;P&gt;I just purchased a wireless controller 4402 and I'm new to using a controller. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I booted it up and I setup the ip address information on it.  (management IP, service port IP, AP-management IP).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm able to access the device from the CLI thru a serial cable and also if I'm plugged in with a laptop thru the service port.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not able to ping or access the device via its management IP address or its service port IP address from any PC on the network.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I tried different settings on the switch port (i.e. trunk, access).  &lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 00:37:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228900#M53438</guid>
      <dc:creator>gflorescu</dc:creator>
      <dc:date>2021-07-04T00:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: cannot access 4402 controller management IP</title>
      <link>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228901#M53439</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you place both the management address and the service port address in the same network? This will cause failure as the service port must be out of band.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 May 2009 09:35:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228901#M53439</guid>
      <dc:creator>dennischolmes</dc:creator>
      <dc:date>2009-05-20T09:35:34Z</dc:date>
    </item>
    <item>
      <title>Re: cannot access 4402 controller management IP</title>
      <link>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228902#M53440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you set a vlan for your management interface? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your management vlan should be 0 if the native vlan (or access vlan) is the vlan for the management interface.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 May 2009 02:01:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228902#M53440</guid>
      <dc:creator>weterry</dc:creator>
      <dc:date>2009-05-21T02:01:48Z</dc:date>
    </item>
    <item>
      <title>Re: cannot access 4402 controller management IP</title>
      <link>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228903#M53441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Taken from Cisco 440X Series Wireless LAN Controllers Deployment Guide&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Management Interface&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;The Management interface is the default interface for in-band management of theWLC and connectivity to enterprise services such as AAA servers.  The Management interface is the &lt;B&gt;only consistently "pingable" in-band interface IP address&lt;/B&gt; on the WLC.&lt;/I&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Service-Port Interface&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&lt;I&gt;The service port interface must have an IP address on a different subnet from the Management, AP Manager, and any dynamic interfaces. The service port can get an IP address via DHCP or it can be assigned a static IP address, but a default-gateway cannot be assigned to the Service-port interface.  The Service-port is typically&lt;/I&gt;&lt;/P&gt;&lt;P&gt;reserved for out-of-band management in the event of a network failure. It is also the only port that is active when the controller is in boot mode.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.  &lt;I&gt;Please rate when applicable.&lt;/I&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 May 2009 03:08:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228903#M53441</guid>
      <dc:creator>Leo Laohoo</dc:creator>
      <dc:date>2009-05-21T03:08:09Z</dc:date>
    </item>
    <item>
      <title>Re: cannot access 4402 controller management IP</title>
      <link>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228904#M53442</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, it was all kind of weird because I am able to access it now from a different VLAN without a problem and I didn't change anything.  &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 May 2009 14:08:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cannot-access-4402-controller-management-ip/m-p/1228904#M53442</guid>
      <dc:creator>gflorescu</dc:creator>
      <dc:date>2009-05-21T14:08:36Z</dc:date>
    </item>
  </channel>
</rss>

