- play_arrow Overview
- play_arrow Operation, Administration, and Management Features
- play_arrow Ethernet OAM and Connectivity Fault Management for Routers
- Introduction to OAM Connectivity Fault Management (CFM)
- Configure Connectivity Fault Management (CFM)
- CFM Action Profile
- Ethernet Local Management Interface
- CFM Support for CCC Encapsulated Packets
- Configure Unified ISSU for 802.1ag CFM
- CFM Monitoring between CE and PE Devices
- Configure Continuity Check Messages
- Example: Configure Ethernet CFM on Physical Interfaces
- Example: Configure Ethernet CFM on Bridge Connections
- Example: Configure Ethernet CFM over VPLS
- play_arrow Link Fault Management for Routers
- play_arrow Ethernet OAM Link Fault Management for Switches
- play_arrow Ethernet OAM Connectivity Fault Management for Switches
- play_arrow Ethernet Frame Delay
- Ethernet Frame Delay Measurements on Switches
- Configure MEP Interfaces on Switches to Support Ethernet Frame Delay Measurements (CLI Procedure)
- Configure One-Way Ethernet Frame Delay Measurements on Switches (CLI Procedure)
- Configure an Iterator Profile on a Switch (CLI Procedure)
- Trigger an Ethernet Frame Delay Measurement Session on a Switch
- Configure Two-Way Ethernet Frame Delay Measurements on Switches (CLI Procedure)
- play_arrow Ethernet Service OAM (ITU-TY.1731) for Routers
- ITU-T Y.1731 Ethernet Service OAM Overview
- Configure Ethernet Frame Delay Measurement Sessions
- Configuring MEP Interfaces to Support Ethernet Frame Delay Measurements
- Configure Ethernet Frame Loss Measurement
- Configure an Iterator Profile
- Configure Ethernet Synthetic Loss Measurements
- Ethernet Alarm Indication
- Inline Transmission Mode
-
- play_arrow Network Monitoring by using SNMP
- SNMP Architecture and SNMP MIBs Overview
- Understand SNMP Implementation in Junos OS
- Configure SNMP in Junos OS
- Configure Options on Managed Devices for Better SNMP Response Time
- Enterprise Specific Utility MIB to Enhance SNMP Coverage
- Optimize the Network Management System Configuration for the Best Results
- Interfaces to Accept SNMP Requests
- Configure SNMP for Routing Instances
- Configure SNMP Remote Operations
- SNMP Traps
- SNMP Traps Supported by Junos OS
- Trace SNMP Activity
- Access Privileges for an SNMP Group
- Configure Local Engine ID on SNMPv3
- Configure SNMPv3
- Configure SNMPv3 Authentication Type and Encryption Type
- SNMPv3 Traps
- SNMPv3 Informs
- SNMP Communities
- MIB Views
- SNMP MIBs Supported by Junos OS and Junos OS Evolved
- Junos OS SNMP FAQs
- play_arrow Remote Network Monitoring (RMON) with SNMP Alarms and Events
- play_arrow Accounting Options
- play_arrow Monitoring Options
- play_arrow Interface Alarms
- play_arrow IP Monitoring
- play_arrow sFlow Monitoring Technology
- play_arrow Adaptive Sampling for Routers and Switches
- play_arrow Packet Flow Accelerator Diagnostics Software
-
- play_arrow Monitoring Common Security Features
- play_arrow Performance Management
- play_arrow Port Mirroring
- play_arrow Port Mirroring and Analyzers
- Port Mirroring and Analyzers
- Configuring Port Mirroring and Analyzers
- Configuring Port Mirroring Instances
- Configuring Port Mirroring on Physical Interfaces
- Configuring Port Mirroring on Logical Interfaces
- Configuring Port Mirroring for Multiple Destinations
- Configuring Port Mirroring for Remote Destinations
- Configuring Port Mirroring Local and Remote Analysis
- 1:N Port Mirroring to Multiple Destinations on Switches
- Example: Configure Port Mirroring with Family any and a Firewall Filter
- Monitoring Port Mirroring
- Configure Packet Mirroring with Layer 2 Headers for Layer 3 Forwarded Traffic
- Troubleshooting Port Mirroring
-
- play_arrow System Log Messages
- play_arrow Configuration Statements and Operational Commands
ON THIS PAGE
On-Box Packet Sniffer Overview
A packet sniffer also known as a packet analyzer or network analyzer that is used to monitor and analyze network traffic over ports without using an external device, such as collector or agent.
On-box packet sniffer allows you to monitor IPv4 packets on ingress or egress ports. It matches packets that are based on header attributes, like source IP, destination IP, source MAC, destination MAC, VLAN, and VNID. You can store the sniffed packets in pcap format.
The following configuration statements are used to support this feature:
To enable the tracing operations, configure the
set services pfe traffic traceoptions file filenamestatement.To increase the default timer that is set for uninstalling the filter and deleting the entries, configure the
set services pfe traffic monitor-timer timestatement.To enable egress packet monitoring, configure the
set interface interface-name ether-options loopbackstatement. You must configure an additional unused interface for a virtual loopback interface to achieve egress packet monitoring.
Use the command monitor pfe traffic interface to monitor
data packets and verify the functionality of on-box packet sniffing.
Benefits of On-Box Packet Sniffer
This feature reduces costs by eliminating the need for an external device, such as collector or agent and simplifies the debugging process.
Limitations
Limitations of on-box packet sniffing include the following:
Monitoring of host-generated packets is not supported.
Monitoring of ipv6 packets is not supported.
You need to clean up the pcap files manually once the monitoring activity is done.
For monitoring of the packets on aggregated Ethernet interfaces, you should assign its child interface for packet sniffing.
It is mandatory to configure unused interface in the setup as a loopback interface and provide that interface as value for egress interface argument in the CLI to achieve egress monitoring.
Need to provide at least one of the attributes in the CLI to start the packet monitoring.
Monitoring on IFL interfaces is not supported.
Interface range is not supported.
Monitoring on IRB is not supported.
Matching on priority VLAN is not supported.
Only 32 bits of inner source MAC or destination MAC address is matched with the CLI. The
byte-offsetoption in the CLI commandmonitor pfe traffic interfacehelps in matching the 32 bits of the address.Concurrent capture sessions are not supported.
Monitoring on outer header source MAC and its combinations are not supported on QFX5110.
When providing the IPv4 address in the CLI, the prefix is not supported.
Filter is configured for either Layer 2 or Layer 3 attributes, but not for both.
