<?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: Valid Role options for syslog servers in Network Platform API</title>
    <link>https://community.cisco.com/t5/network-platform-api/valid-role-options-for-syslog-servers/m-p/5448931#M7617</link>
    <description>&lt;P&gt;If you do not see the 2 roles 'IDS Alerts' and 'Security events' from your dashboard, then you cannot leverage them in the API as roles. I am able to use the Security events role in my syslog settings through the API across several branch locations for one of my clients, all which consist of combined networks (wireless/switch/security). &lt;/P&gt;&lt;P&gt;It is unusual that 'Security events' is not a selectable role, so I would open a case with Meraki support to have them check out what could be going on; I am unsure on the 'IDS alerts' role as I've never seen that as an option in the dashboard, and in the current API library, I do not see that as a role option either.&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jan 2024 22:58:36 GMT</pubDate>
    <dc:creator>kmcgaugh</dc:creator>
    <dc:date>2024-01-18T22:58:36Z</dc:date>
    <item>
      <title>Valid Role options for syslog servers</title>
      <link>https://community.cisco.com/t5/network-platform-api/valid-role-options-for-syslog-servers/m-p/5448930#M7616</link>
      <description>&lt;P&gt;For syslog server settings, on the API docs, it is stated that valid options for role field are these: &lt;SPAN&gt;'Wireless event log', 'Appliance event log', 'Switch event log', 'Air Marshal events', 'Flows', 'URLs', 'IDS alerts', 'Security events'&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;I have a combined (wireless / security / switch) network. For this network, I can successfully create a syslog server if I include any subset of role options except &lt;SPAN&gt;'IDS alerts' and 'Security events'. If I include any one of these two, I get a 400 error with the following message: 'Please select at least one valid role for server_address:port'. I also don't see these 2 roles as options on the dashboard.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Is there a specific network type, account feature or anything for which these syslog role types are enabled? If that is the case, can I get that info from the API? Or maybe are these role types deprecated?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 10 Mar 2021 11:58:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/valid-role-options-for-syslog-servers/m-p/5448930#M7616</guid>
      <dc:creator>Ozgur1</dc:creator>
      <dc:date>2021-03-10T11:58:34Z</dc:date>
    </item>
    <item>
      <title>Re: Valid Role options for syslog servers</title>
      <link>https://community.cisco.com/t5/network-platform-api/valid-role-options-for-syslog-servers/m-p/5448931#M7617</link>
      <description>&lt;P&gt;If you do not see the 2 roles 'IDS Alerts' and 'Security events' from your dashboard, then you cannot leverage them in the API as roles. I am able to use the Security events role in my syslog settings through the API across several branch locations for one of my clients, all which consist of combined networks (wireless/switch/security). &lt;/P&gt;&lt;P&gt;It is unusual that 'Security events' is not a selectable role, so I would open a case with Meraki support to have them check out what could be going on; I am unsure on the 'IDS alerts' role as I've never seen that as an option in the dashboard, and in the current API library, I do not see that as a role option either.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jan 2024 22:58:36 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-platform-api/valid-role-options-for-syslog-servers/m-p/5448931#M7617</guid>
      <dc:creator>kmcgaugh</dc:creator>
      <dc:date>2024-01-18T22:58:36Z</dc:date>
    </item>
  </channel>
</rss>

