Cisco IOS
The JSA DSM for Cisco IOS accepts Cisco IOS events by using syslog. JSA records all relevant events.
The following Cisco switches and routers are automatically discovered as Cisco IOS series devices, and their events are parsed by the DSM for Cisco IOS:
-
Cisco 12000 Series Routers
-
Cisco 6500 Series Switches
-
Cisco 7600 Series Routers
-
Cisco Carrier Routing System
-
Cisco Integrated Services Router.
Make sure that all access control lists (ACLs) are set to LOG.
Configuring Cisco IOS to Forward Events
You can configure a Cisco IOS-based device to forward events.
Take the following steps to configure your Cisco device:
-
Log in to your Cisco IOS Server, switch, or router.
-
Type the following command to log in to the router in privileged-exec:
enable
-
Type the following command to switch to configuration mode:
conf t
-
Type the following commands:
logging <IP address>
logging source-interface <interface>
Where:
-
<IP address> is the IP address of the JSA host and the SIM components.
-
<interface> is the name of the interface, for example, dmz, lan, ethernet0, or ethernet1.
-
-
Type the following to configure the priority level:
logging trap warning
logging console warning
Where warning is the priority setting for the logs.
-
Configure the syslog facility:
logging facility syslog
-
Save and exit the file.
-
Copy the running-config to startup-config by typing the following command:
copy running-config startup-config
You are now ready to configure the log source in JSA.
The configuration is complete. The log source is added to JSA as Cisco IOS events are automatically discovered. Events that are forwarded to JSA by Cisco IOS-based devices are displayed on the Log Activity tab of JSA.
Syslog Log Source Parameters for Cisco IOS
If JSA does not automatically detect the log source, add a Cisco IOS log source on the JSA Console by using the syslog protocol.
When using the syslog protocol, there are specific parameters that you must use.
The following table describes the parameters that require specific values to collect syslog events from Cisco IOS:
Parameter |
Value |
---|---|
Log Source type |
Select one of the following devices:
|
Protocol Configuration |
Syslog |
Log Source Identifier |
Type the IP address or host name for the log source. The identifier helps you determine which events came from your Cisco IOS device. |
Cisco IOS Sample Event Messages
Use these sample event messages to verify a successful integration with JSA.
Due to formatting issues, paste the message format into a text editor and then remove any carriage return or line feed characters.
Cisco IOS Sample Message when you use the Syslog Protocol
Sample 1: This sample event shows that a TCP session is dropped.
<190>2116989: cisco.ios.test: Aug 1 13:42:04.497: %IOSXE-6-PLATFORM: SIP1: cpp_cp: QFP:0.0 Thread:001 TS:00006808302886264846 %FW-6-DROP_PKT: Dropping tcp pkt from Vlan100 10.1.2.230:12321 => 172.16.3.20:42150(target:class)-(ESP-DMVPN:class-default) due to Policy drop:classify result with ip ident 1203 tcp flag 0x2, seq 1227798955, ack 0
JSA field name |
Highlighted values in the event payload |
---|---|
Event ID |
%FW-6-DROP_PKT |
Event Category |
IOS |
Source IP |
10.1.2.230 |
Source Port |
12321 |
Destination IP |
172.16.3.20 |
Destination Port |
42150 |
Protocol |
6 |
Sample 2: This sample event shows the opening of an inspection session. The message is issued at the start of each inspected session and it records the source and destination addresses, and ports.
<190>1321321: cisco.ios.test: Jul 12 15:42:06.035: %IOSXE-6-PLATFORM: SIP1: cpp_cp: QFP:0.0 Thread:001 TS:00005087480388332015 %FW-6-SESS_AUDIT_TRAIL_START: (target:class)-(DMVPNESP: CLS_ESP-Out):Start tcp session: initiator (192.168.150.120:49290) -- responder (10.40.0.27:20000) from Tunnel1
JSA field name |
Highlighted values in the event payload |
---|---|
Event ID |
SESS_AUDIT_TRAIL_START |
Event Category |
IOS |
Source IP |
192.168.150.120:49290 |
Source Port |
49290 |
Destination IP |
10.40.0.27 |
Destination Port |
20000 |
Protocol |
6 |