Chapter 13 Displaying and Capturing Live Traffic on an Interface

Displaying Live Traffic on an Interface

Start: yyyy/mm/dd hh:mm:ss zone, End: yyyy/mm/dd hh:mm:ss zone or in-progress.

Where user = the username of user initiating capture, id = the CLI ID of the user, and cliCmd = the command entered to perform the capture.

Caution Executing the packet display command causes significant performance degradation.

Displaying Live Traffic From an Interface

To configure the sensor to display live traffic from an interface on the screen, follow these steps:

 

Step 1

Log in to the sensor using an account with administrator or operator privileges.

 

 

 

 

 

 

Step 2

Display the live traffic on the interface you are interested in, for example, GigabitEthernet0/1.

 

 

sensor# packet display GigabitEthernet0/1

 

 

 

 

 

 

 

 

Warning: This command will cause significant performance degradation

 

 

 

 

 

 

 

tcpdump: listening

on ge0_1, link-type

EN10MB (Ethernet), capture size

65535 bytes

 

 

03:43:05.691883 IP

(tos 0x10, ttl

64,

id 55460,

offset 0, flags [DF],

length:

100)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 4233955485:4233955533(48) ack

 

 

1495691730 win 8576 <nop,nop,timestamp

44085169 226014949>

 

 

 

 

 

 

 

03:43:05.691975 IP

(tos 0x10, ttl

64,

id 55461,

offset 0, flags [DF],

length:

164)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 48:160(112) ack 1

win 8576

 

 

 

 

 

 

<nop,nop,timestamp

44085169 226014949>

 

 

 

 

 

 

 

 

 

03:43:05.691998 IP

(tos 0x10, ttl

64,

id 53735,

offset 0, flags [DF],

length:

52)

 

 

 

10.89.147.50.41805

> 10.89.147.31.22: . [tcp sum

ok] 1:1(0) ack 48 win

11704

 

 

 

 

 

 

<nop,nop,timestamp

226014949 44085169>

 

 

 

 

 

 

 

 

 

03:43:05.693165 IP

(tos 0x10, ttl

64,

id 53736,

offset 0, flags [DF],

length:

52)

 

 

 

10.89.147.50.41805

> 10.89.147.31.22: . [tcp sum

ok] 1:1(0) ack 160 win 11704

 

 

 

 

 

 

<nop,nop,timestamp

226014949 44085169>

 

 

 

 

 

 

 

 

 

03:43:05.693351 IP

(tos 0x10, ttl

64,

id 55462,

offset 0, flags [DF],

length:

316)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 160:424(264) ack 1 win 8576

 

 

<nop,nop,timestamp

44085169 226014949>

 

 

 

 

 

 

 

 

 

03:43:05.693493 IP

(tos 0x10, ttl

64,

id 55463,

offset 0, flags [DF],

length:

292)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 424:664(240) ack 1 win 8576

 

 

<nop,nop,timestamp

44085169 226014949>

 

 

 

 

 

 

 

 

 

03:43:05.693612 IP

(tos 0x10, ttl

64,

id 55464,

offset 0, flags [DF],

length:

292)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 664:904(240) ack 1 win 8576

 

 

<nop,nop,timestamp

44085169 226014949>

 

 

 

 

 

 

 

 

 

03:43:05.693628 IP

(tos 0x10, ttl

64,

id 53737,

offset 0, flags [DF],

length:

52)

 

 

 

10.89.147.50.41805

> 10.89.147.31.22: . [tcp sum

ok] 1:1(0) ack 424 win 11704

 

 

 

 

 

 

<nop,nop,timestamp

226014949 44085169>

 

 

 

 

 

 

 

 

 

03:43:05.693654 IP

(tos 0x10, ttl

64,

id 53738,

offset 0, flags [DF],

length:

52)

 

 

 

10.89.147.50.41805

> 10.89.147.31.22: . [tcp sum

ok] 1:1(0) ack 664 win 11704

 

 

 

 

 

 

<nop,nop,timestamp

226014949 44085169>

 

 

 

 

 

 

 

 

 

03:43:05.693926 IP

(tos 0x10, ttl

64,

id 55465,

offset 0, flags [DF],

length:

292)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 904:1144(240) ack

1 win 8576

 

 

<nop,nop,timestamp

44085169 226014949>

 

 

 

 

 

 

 

 

 

03:43:05.694043 IP

(tos 0x10, ttl

64,

id 55466,

offset 0, flags [DF],

length:

292)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 1144:1384(240) ack 1 win 8576

 

 

<nop,nop,timestamp

44085169 226014949>

 

 

 

 

 

 

 

 

 

03:43:05.694163 IP

(tos 0x10, ttl

64,

id 55467,

offset 0, flags [DF],

length:

292)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 1384:1624(240) ack 1 win 8576

 

 

<nop,nop,timestamp

44085169 226014949>

 

 

 

 

 

 

 

 

 

03:43:05.694209 IP

(tos 0x10, ttl

64,

id 53739,

offset 0, flags [DF],

length:

52)

 

 

 

10.89.147.50.41805

> 10.89.147.31.22: . [tcp sum

ok] 1:1(0) ack 1384 win 11704

 

 

 

 

 

 

<nop,nop,timestamp

226014950 44085169>

 

 

 

 

 

 

 

 

 

03:43:05.694283 IP

(tos 0x10, ttl

64,

id 55468,

offset 0, flags [DF],

length:

292)

 

 

 

10.89.147.31.22 > 10.89.147.50.41805: P [tcp sum

ok] 1624:1864(240) ack 1 win 8576

 

 

<nop,nop,timestamp

44085169 226014950>

 

 

 

 

 

 

 

 

 

 

Cisco Intrusion Prevention System Sensor CLI Configuration Guide for IPS 7.2

 

 

 

 

 

 

 

 

 

 

 

 

OL-29168-01

 

 

 

 

 

 

 

 

13-3

 

 

 

 

 

 

 

 

 

 

 

Page 368 Page 370
Page 369
Image 369
Cisco Systems IPS4510K9 manual Displaying Live Traffic From an Interface, 13-3, Sensor# packet display GigabitEthernet0/1
Page 368 Page 370

IPS4510K9 specifications

Cisco Systems has long been a leading player in network security, and its IPS (Intrusion Prevention System) series is a testament to its commitment to safeguarding digital environments. Among its notable offerings are the IPS4510K9 and IPS4520K9 models, both designed to provide advanced threat protection for mid-sized to large enterprise networks.

The Cisco IPS4510K9 and IPS4520K9 are distinguished by their cutting-edge features that help organizations defend against a myriad of cyber threats. These systems utilize a multi-layered approach to security, integrating intrusion prevention, advanced malware protection, and comprehensive visibility across the network.

One of the primary characteristics of the IPS4510K9 is its high performance. It boasts a throughput of up to 1 Gbps, making it suitable for environments that demand rapid data processing and real-time responses to threats. The IPS4520K9, on the other hand, enhances that capability with improved throughput of up to 2 Gbps, accommodating larger enterprises with heavier network traffic. These models are equipped with powerful processors that support complex signature matching and can intelligently distinguish between legitimate traffic and potential threats.

In addition to performance, both models are designed with scalability in mind. They can be easily integrated into existing Cisco infrastructures. This facilitates a seamless enhancement of security without causing significant interruptions to ongoing operations. Moreover, they offer flexible deployment options, allowing organizations to operate them inline or out of band depending on their specific needs.

The Cisco IPS4510K9 and IPS4520K9 leverage advanced detection technologies, utilizing a variety of signature types and heuristic analysis to detect known and unknown threats effectively. They are equipped with real-time alerting and reporting capabilities, giving security teams immediate visibility into potential breaches and enabling them to respond swiftly.

Furthermore, both models support a range of management options through the Cisco Security Manager, allowing for centralized administration, streamlined policy management, and enhanced monitoring capabilities. Automated updates ensure the systems remain current with the latest threat intelligence, vital for staying ahead of evolving cyber threats.

In summary, the Cisco Systems IPS4510K9 and IPS4520K9 represent powerful solutions for organizations seeking robust intrusion prevention capabilities. With their high performance, scalability, and advanced detection technologies, these systems are essential tools in the ever-changing landscape of cybersecurity, providing enterprises with the peace of mind needed to operate securely in today's digital world.
Top Page Image Contents