Submit a ticketCall us

whitepaperYour VM Perplexities Called, and They Need You to Read This.

Virtualization can give you enormous flexibility with future workloads and can be a key enabler for other areas, like cloud computing and disaster recovery. So, how can you get a handle on the performance challenges in your virtual environment and manage deployments without erasing the potential upside? Learn the four key areas you need to be focusing on to help deliver a healthy and well-performing data center.

Get your free white paper.

Home > Success Center > Network Configuration Manager (NCM) > NCM Documentation > NCM 7.9 Administrator Guide > About real-time change detection > Examples of commands to send syslog or trap messages to the Orion server

Examples of commands to send syslog or trap messages to the Orion server

Updated: August 14, 2018

When you configure real-time change detection, you must configure devices to send either syslog or trap messages to the Orion server. The following sections provide examples of commands used for some device types. For more information, see your device documentation.

Syslog (IOS)

This example configures a Cisco router to send syslog events whose severity level is informational or greater (logging trap level 6) to the Orion server (IP address 10.199.3.43).

config terminal
logging 10.199.3.43
logging trap 6
end

Syslog (CatOS)

The example configures a Catalyst switch to send syslog events whose severity level is notification or greater to the Orion server (192.168.0.30).

set logging server 192.168.0.30
set logging server facility local4
set logging server severity 5
set logging server enable

The commands do the following:

  • set logging timestamp adds timestamps to all syslog events.
  • set logging server adds the Orion server (192.168.0.30) as an export target.
  • set logging server severity limits syslog exports to events with a severity level of notification (level 5) or greater.
  • set logging server specifically enables the switch to export relevant syslog data to the logging server you have already specified (the Orion server).

Traps (IOS)

This example configures a device to send trap alerts to the Orion server when a config-related event occurs on the device.

snmp-server 10.110.68.33 public config
snmp-server enable traps config

Here are the commands with variable names instead of sample values:

snmp-server {host_name|IP_address} community_stringtrap_type
snmp-server enable traps trap_type

Traps (CatOS)

This example configures a device to send trap alerts to the Orion server when a config-related event occurs on the device.

set snmp trap 10.110.68.33 public config
set snmp trap enable config

Here are the commands with variable names instead of sample values:

set snmp trap {host_name|IP_address}community_stringtrap_type
set snmp trap {enable|disable} trap_type

 

Last modified

Tags

Classifications

Public