- play_arrow Overview
- 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 Network Management and Troubleshooting
- Compressing Troubleshooting Logs from /var/logs to Send to Juniper Networks Technical Support
- Monitoring and Troubleshooting
- Troubleshooting System Performance with Resource Monitoring Methodology
- Configuring Data Path Debugging and Trace Options
- Using MPLS to Diagnose LSPs, VPNs, and Layer 2 Circuits
- Using Packet Capture to Analyze Network Traffic
- On-Box Packet Sniffer Overview
- Troubleshooting Security Devices
- play_arrow Configuration Statements and Operational Commands
Example: Configure Ethernet CFM over VPLS
In this example, both the customer and service provider are running Ethernet CFM over a VPLS and a multiprotocol label switching (MPLS) network. The network is shown in Figure 1. The customer has configured Ethernet CFM on MX Series routers L2-CE1 and L2-CE2. The service provider has configured Ethernet CFM on MX Series routers PE1, P, and PE2.
The configurations in this example are only partial examples of complete and functional router configurations. Do not copy these configurations and use them directly on an actual system.
The service provider is using CFM level 5 and the customer is using CFM level 7. The boundaries are marked with “up mep” and “down mep” CFM terminology in the figure.
The logical interfaces in a VPLS routing instance might have the same or different VLAN configurations. VLAN normalization is required to switch packets correctly among these interfaces. Normalization supports automatic mapping of VLANs and performs operations on VLAN tags to achieve the desired translation. See Configuring a Normalized VLAN for Translation or Tagging.
The logical interfaces in a VPLS routing instance might have the same or different VLAN configurations. VLAN normalization is required to switch packets correctly among these interfaces. VLAN normalization is effectively VLAN translation wherein the VLAN tags of the received packet need to be translated if they are different than the normalized VLAN tags.
For MX Series routers, the normalized VLAN is specified using one of the following configuration statements in the VPLS routing instance:
vlan-id vlan-number
vlan-id none
vlan-tags outer outer-vlan-number inner inner-vlan-number
You must configure vlan-maps
explicitly on all interfaces belonging
to the routing instance.
The following forwarding path considerations must be observed:
Packet receives path:
This is the forwarding path for packets received on the interfaces.
802.1ag Ethernet OAM for VPLS uses implicit interface filters and forwarding table filters to flood, accept, and drop the CFM packets.
Packet transmits path:
The Junos Software uses the router’s hardware-based forwarding for CPU-generated packets.
For Down MEPs, the packets are transmitted on the interface on which the MEP is configured.
For Up MEPs, the MX Series routers must flood the packet to other interfaces within the VPLS routing instance. The routers generate a flood route that is linked to a flood next hop with all flood interfaces and then forwards the packet using this flood route.
The router also uses implicit-based forwarding for CPU generated packets. The result is for the flood next hop tied to the flood route to be tied to the filter term. The filter term uses match criteria to correctly identify the host- generated packets.
The following are the configurations of the VPLS and CFM on the service provider routers.
Configuration of PE1
[edit chassis] fpc 5 { pic 0 { tunnel-services { bandwidth 1g; } } } [edit interfaces] ge-1/0/7 { encapsulation flexible-ethernet-services; vlan-tagging; unit 1 { encapsulation vlan-vpls; vlan-id 2000; } } ge-0/0/0 { unit 0 { family inet { address 10.200.1.1/24; } family mpls; } } lo0 { unit 0 { family inet { address 10.255.168.231/32 { primary; } address 127.0.0.1/32; } } } [edit routing-instances] vpls-vlan2000 { instance-type vpls; vlan-id 2000; interface ge-1/0/7.1; route-distinguisher 10.255.168.231:2000; vrf-target target:1000:1; protocols { vpls { site-range 10; site vlan2000-PE1 { site-identifier 2; } } } } [edit protocols] rsvp { interface ge-0/0/0.0; } mpls { label-switched-path PE1-to-PE2 { to 10.100.1.1; } interface ge-0/0/0.0; } bgp { group PE1-to-PE2 { type internal; local-address 10.200.1.1; family l2vpn { signaling; } local-as 65000; neighbor 10.100.1.1; } } ospf { traffic-engineering; reference-bandwidth 4g; area 0.0.0.0 { interface all; interface fxp0.0 { disable; } interface ge-0/0/0.0; } } oam { ethernet { connectivity-fault-management { maintenance-domain customer-site1 { level 5; maintenance-association customer-site1 { continuity-check { interval 1s; } mep 100 { interface ge-1/0/7.1; direction up; auto-discovery; } } } } } }
Configuration of PE2
[edit chassis] fpc 5 { pic 0 { tunnel-services { bandwidth 1g; } } } [edit interfaces] ge-5/0/9 { vlan-tagging; encapsulation flexible-ethernet-services; unit 1 { encapsulation vlan-vpls; vlan-id 2000; } } ge-5/2/7 { unit 0 { family inet { address 10.100.1.1/24; } family mpls; } } lo0 { unit 0 { family inet { address 10.255.168.230/32 { primary; } address 127.0.0.1/32; } } } [edit routing-instances] vpls-vlan2000 { instance-type vpls; vlan-id 2000; interface ge-5/0/9.1; route-distinguisher 10.255.168.230:2000; vrf-target target:1000:1; protocols { vpls { site-range 10; site vlan2000-PE2 { site-identifier 1; } } } } [edit protocols] rsvp { interface ge-5/2/7.0; } mpls { label-switched-path PE2-to-PE1 { to 10.200.1.1; } interface ge-5/2/7.0; } bgp { group PE2-to-PE1 { type internal; local-address 10.100.1.1; family l2vpn { signaling; } local-as 65000; neighbor 10.200.1.1; } } ospf { traffic-engineering; reference-bandwidth 4g; area 0.0.0.0 { interface all; interface fxp0.0 { disable; } interface ge-5/2/7.0; } } oam { ethernet { connectivity-fault-management { maintenance-domain customer-site1 { level 5; maintenance-association customer-site1 { continuity-check { interval 1s; } mep 200 { interface ge-5/0/9.1; direction up; auto-discovery; } } } } } }
Configuration of P router
MPLS only, no CFM needed:
[edit] interfaces { ge-5/2/7 { # Connected to PE1 unit 0 { family inet { address 10.200.1.10/24; } family mpls; } } ge-0/1/0 { # Connected to PE2 unit 0 { family inet { address 10.100.1.10/24; } family mpls; } } lo0 { unit 0{ family inet { address 10.255.168.240/32; } } } } [edit] protocols { rsvp { interface ge-0/1/0.0; interface ge-5/2/7.0; } mpls { interface ge-0/1/0.0; interface ge-5/2/7.0; } ospf { traffic-engineering; reference-bandwidth 4g; area 0.0.0.0 { interface all; interface fxp0.0 { disable; } interface ge-0/1/0.0; interface ge-5/2/7.0; } } }
CFM on L2-CE1
Here is the configuration of CFM on L2-E1:
[edit interfaces] ge-5/2/3 { vlan-tagging; unit 0 { vlan-id 2000; } } [edit protocols oam] ethernet { connectivity-fault-management { maintenance-domain customer { level 7; maintenance-association customer-site1 { continuity-check { interval 1s; } mep 800 { interface ge-5/2/3.0; direction down; auto-discovery; } } } } }
CFM on L2-CE2
Here is the configuration of CFM L2-CE2:
[edit interfaces] ge-0/2/9 { vlan-tagging; unit 0 { vlan-id 2000; } } [edit protocols oam] ethernet { connectivity-fault-management { maintenance-domain customer { level 7; maintenance-association customer-site1 { continuity-check { interval 1s; } mep 700 { interface ge-0/2/9.0; direction down; auto-discovery; } } } } }