<?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 WCS Multi-Homed in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390990#M74712</link>
    <description>&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;I've upgraeded a multi-homed WCS server to version 6.0.170 (from 5.2.x)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;This server is multi-homed and I think my client has selected the wrong interface when installing the 5.2.x version.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Is it possible to change the network interface card after installation (by adding a property file e.g.) ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;TACACS+ is not working, When adding a tacacs+ server, the local interface ip (automatically selected when adding) is using the secondary NIC. I think that's the reason for the tacacs+ failures. &lt;/SPAN&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;E-mail output from sheduled reports is not working either. I think all issues are caused by the multi-homed issue.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;thanks for your help&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 01:31:03 GMT</pubDate>
    <dc:creator>vergeerf</dc:creator>
    <dc:date>2021-07-04T01:31:03Z</dc:date>
    <item>
      <title>WCS Multi-Homed</title>
      <link>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390990#M74712</link>
      <description>&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;I've upgraeded a multi-homed WCS server to version 6.0.170 (from 5.2.x)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;This server is multi-homed and I think my client has selected the wrong interface when installing the 5.2.x version.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Is it possible to change the network interface card after installation (by adding a property file e.g.) ?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;TACACS+ is not working, When adding a tacacs+ server, the local interface ip (automatically selected when adding) is using the secondary NIC. I think that's the reason for the tacacs+ failures. &lt;/SPAN&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;E-mail output from sheduled reports is not working either. I think all issues are caused by the multi-homed issue.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;thanks for your help&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 01:31:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390990#M74712</guid>
      <dc:creator>vergeerf</dc:creator>
      <dc:date>2021-07-04T01:31:03Z</dc:date>
    </item>
    <item>
      <title>Re: WCS Multi-Homed</title>
      <link>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390991#M74713</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Frank!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you change the network interface order in Microsoft Windows putting the management interface on top, you might find that should do it! &lt;SPAN __jive_emoticon_name="wink" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/wink.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;You do need to reboot to get this to work..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Richard.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Feb 2010 07:52:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390991#M74713</guid>
      <dc:creator>richard.schaareman</dc:creator>
      <dc:date>2010-02-22T07:52:05Z</dc:date>
    </item>
    <item>
      <title>Re: WCS Multi-Homed</title>
      <link>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390992#M74714</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have exactly the same problem with WCS 6.0.181 !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Multi-homed 2003 server (2 NIC's) and it alway choose wrong nic when I tries to use radius in local wcs management.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There should be a choice that let the user choose which interface that should send out the radius packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've tried to rename the nic's, but it didn't work. Also changed the ip adresses between the nic's, still wrong local interface. &lt;span class="lia-unicode-emoji" title=":disappointed_face:"&gt;😞&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anybody have a solution ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Feb 2010 12:14:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390992#M74714</guid>
      <dc:creator>rpettersen</dc:creator>
      <dc:date>2010-02-23T12:14:38Z</dc:date>
    </item>
    <item>
      <title>Re: WCS Multi-Homed</title>
      <link>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390993#M74715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I might not have been very clear, but the network card order DID SOLVE our problem!&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;During installation WCS &lt;EM&gt;should&lt;/EM&gt; ask which interface to use, but in our case, there was an interface added after installation for backup purposes.&lt;/P&gt;&lt;P&gt;After that we also did a upgrade, but during that process the software doesn't ask about interfaces to be used. This settings seem to be inherited from the original installation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See attached printscreen for Windows 2003 server settings..&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Feb 2010 12:27:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390993#M74715</guid>
      <dc:creator>richard.schaareman</dc:creator>
      <dc:date>2010-02-23T12:27:03Z</dc:date>
    </item>
    <item>
      <title>Re: WCS Multi-Homed</title>
      <link>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390994#M74716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi !&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;On our WCS I have two nic's, one for public (wcs admin,etc) and one for private (wism comunication). The radius use&lt;/P&gt;&lt;P&gt;always the private ip address (10.0.0.X) which is wrong because I have the radius server on the public network.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I guess that the solution will be a second nic in the radius server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hpoe that cisco will let us choose which local ip interface to use when wcs are using radius authnetication.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Feb 2010 14:48:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wcs-multi-homed/m-p/1390994#M74716</guid>
      <dc:creator>rpettersen</dc:creator>
      <dc:date>2010-02-23T14:48:44Z</dc:date>
    </item>
  </channel>
</rss>

