<?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: Service port interface in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066317#M187715</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks a lot buddy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regrds&lt;/P&gt;&lt;P&gt;subharose&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 12 Sep 2008 18:16:52 GMT</pubDate>
    <dc:creator>subharojdahal</dc:creator>
    <dc:date>2008-09-12T18:16:52Z</dc:date>
    <item>
      <title>Service port interface</title>
      <link>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066315#M187712</link>
      <description>&lt;P&gt;What is service port interface in WiSM? I know it is used to communication with Supervisor Engine but just want to know in details ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thnx&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;subharose&lt;/P&gt;</description>
      <pubDate>Sat, 03 Jul 2021 23:27:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066315#M187712</guid>
      <dc:creator>subharojdahal</dc:creator>
      <dc:date>2021-07-03T23:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: Service port interface</title>
      <link>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066316#M187714</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The service-port interface is reserved for out-of-band management of the controller and&lt;/P&gt;&lt;P&gt;system recovery and maintenance in the event of a network failure. It is also the only port that is active when the controller is in boot mode. WiSM use the service port for internal protocol communication between the&lt;/P&gt;&lt;P&gt;controllers and the Supervisor 720. For example, if you want to use "session slot x proc 1" to access WiSM's CLI through sup720, you have to enable a service VLAN which is local to the chassis and is used for&lt;/P&gt;&lt;P&gt;communication between Cisco WiSM and Catalyst Supervisor 720 over a Gigabit Interface on the Supervisor and a service port in the Cisco WiSM. See following link for more detail:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/modules/ps2706/products_tech_note09186a00808330a9.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/modules/ps2706/products_tech_note09186a00808330a9.shtml&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Sep 2008 02:34:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066316#M187714</guid>
      <dc:creator>bbxie</dc:creator>
      <dc:date>2008-09-12T02:34:55Z</dc:date>
    </item>
    <item>
      <title>Re: Service port interface</title>
      <link>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066317#M187715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks a lot buddy&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regrds&lt;/P&gt;&lt;P&gt;subharose&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 12 Sep 2008 18:16:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066317#M187715</guid>
      <dc:creator>subharojdahal</dc:creator>
      <dc:date>2008-09-12T18:16:52Z</dc:date>
    </item>
    <item>
      <title>Re: Service port interface</title>
      <link>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066318#M187716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can the service-port interface be placed in its own VRF if it's only used for intra-chassis communication between the Sup720 and the WiSM(s)?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Dec 2008 19:12:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066318#M187716</guid>
      <dc:creator>mmelbourne</dc:creator>
      <dc:date>2008-12-05T19:12:02Z</dc:date>
    </item>
    <item>
      <title>Re: Service port interface</title>
      <link>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066319#M187717</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's not "only" used for intra-chassis communication - or at least, it doesn't have to be. Although no default gateway can be assigned on the service port interface, so it has no way to get off-subnet, you can certainly spread that vlan around as far as you want and communicate directly with the wism from your desk or wherever the service vlan is trunked to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No idea on your VRF question, though.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Dec 2008 15:21:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/service-port-interface/m-p/1066319#M187717</guid>
      <dc:creator>gamccall</dc:creator>
      <dc:date>2008-12-06T15:21:53Z</dc:date>
    </item>
  </channel>
</rss>

