User manual JUNIPER NETWORKS JUNOS 10.1 CONFIGURATION GUIDE 1-2010

[. . . ] JUNOS® Software Network Interfaces Configuration Guide Release 10. 1 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 USA 408-745-2000 www. juniper. net Published: 2010-01-22 This product includes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. This program and its documentation were developed at private expense, and no part of them is in the public domain. This product includes memory allocation software developed by Mark Moraes, copyright © 1988, 1989, 1993, University of Toronto. This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. [. . . ] Maintenance domains are configured with different level values to keep them separate. Each domain provides enough information for the entities to perform their own management, perform end-to-end monitoring, and still avoid security breaches. IEEE 802. 1ag OAM Connectivity Fault Management Overview 703 JUNOS 10. 1 Network Interfaces Configuration Guide NOTE: As a requirement for Ethernet OAM 802. 1ag to work, distributed periodic packet management (PPM) runs on the Routing Engine and Packet Forwarding Engine (PFE) by default. To disable PPM on the PFE, include the ppm <no-delegate-processing> statement at the [edit routing-options ppm] hierarchy level. IEEE 802. 1ag OAM is supported on untagged, single tagged, and stacked VLAN interfaces. Connectivity Fault Management Key Elements on page 704 Connectivity Fault Management Key Elements Figure 62 on page 704 shows the relationships among the customer, provider, and operator Ethernet bridges, maintenance domains, maintenance association end points (MEPs), and maintenance intermediate points (MIPs). Figure 62: Relationship Among MEPs, MIPs, and Maintenance Domain Levels A maintenance association is a set of MEPs configured with the same maintenance association identifier and maintenance domain level. Figure 63 on page 705 shows the hierarchical relationships between the Ethernet bridge, maintenance domains, maintenance associations, and MEPs. 704 IEEE 802. 1ag OAM Connectivity Fault Management Overview Chapter 43: Configuring IEEE 802. 1ag OAM Connectivity-Fault Management Figure 63: Relationship Among Bridges, Maintenance Domains, Maintenance Associations, and MEPs Creating the Maintenance Domain To enable CFM on an Ethernet interface, maintenance domains, maintenance associations, and MEPs must be created and configured. To create a maintenance domain, include the maintenance-domain domain-name statement at the [edit protocols oam ethernet connectivity-fault-management] hierarchy level. Names can be in one of several formats: Configuring the Maintenance Domain Name Format on page 705 Configuring the Maintenance Domain Level on page 706 Configuring the Maintenance Domain Name Format You can specify the maintenance domain name format as one of the following:. A plain ASCII character string. A domain name service (DNS) format, a MAC address plus a two-octet identifier in the range from 0 through 65, 535, or none. A MAC address plus a two-octet identifier in the range from 0 through 65, 535. Or none. If none is specified, the maintenance domain name is not used. To configure the maintenance domain name format, include the name-format (character-string | none | dns | mac+2octet) statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name] hierarchy level. Creating the Maintenance Domain 705 JUNOS 10. 1 Network Interfaces Configuration Guide Configuring the Maintenance Domain Level The maintenance domain level is a mandatory parameter that indicates the nesting relationship between various maintenance domains. CFM messages within a given level are processed by MEPs at that same level. For example, the operator domain can be level 0, the provider domain can be level 3, and the customer domain can be level 7. To configure the maintenance domain level, include the level number statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name] hierarchy level. Configuring Maintenance Intermediate Points MX Series routers support maintenance intermediate points (MIPs) for the Ethernet OAM 802. 1ag CFM protocol at a bridge-domain level. This enables you to define a maintenance domain for each default level. The MIPs names are created as default-level-number at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain] hierarchy level. Use the bridge-domain, routing-instance, domain-instance, and mip-half-function MIP options to specify the MIP configuration. NOTE: Whenever a MIP is configured and a bridge domain is mapped to multiple maintenance domains or maintenance associations, it is essential that the mip-half-function value for all maintenance domains and maintenance associations be the same. To display MIP configurations, use the show oam ethernet connectivity-fault-management mip (bridge-domain | instance-name | interface-name) command. The following sections describe MIP configuration: Configuring MIP for Bridge Domains of a Virtual Switch on page 706 Configuring the Maintenance Domain Routing Instances Bridge Domain on page 707 Configuring the Maintenance Domain Routing Instance on page 707 Configuring the Maintenance Domain Instance on page 707 Configuring the Maintenance Domain MIP Half Function on page 707 Configuring MIP for Bridge Domains of a Virtual Switch The default maintenance domain configuration allows MIP configuration for bridge domains for a default virtual switch or a user-defined virtual switch. You can use the virtual-switch and bridge-domain statements to specify which MIPs to enable. A bridge domain must be specified by name only if it is configured by including the vlan-id id statement under the virtual-switch statement. 706 Configuring Maintenance Intermediate Points Chapter 43: Configuring IEEE 802. 1ag OAM Connectivity-Fault Management If a bridge domain is configured with a range of VLAN IDs, then the VLAN IDs must be explicitly listed after the bridge domain name. To configure a bridge domain under a user-defined virtual switch, include the virtual-switch name statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name default-x] hierarchy level. [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name default-x] virtual-switch name { bridge-domain { name-1; name-2 { vlan-id [vlan-ids ]; } } } Configuring the Maintenance Domain Routing Instances Bridge Domain The VLAN corresponds to the bridge domain. [. . . ] VPI used in an ATM-to-Ethernet interworking cross-connect. virtual-path-identifier--VPI to be used. Range: 0 through 255 Required Privilege Level interface--To view this statement in the configuration. Configuring ATM-to-Ethernet Interworking on page 236 Configuring ATM Cell-Relay Promiscuous Mode on page 304 Related Topics 1538 vpi (Logical Interface and Interworking) Chapter 62: Summary of Interface Configuration Statements vtmapping Syntax vtmapping (itu-t | klm); Hierarchy Level [edit interfaces interface-name sonet-options]; [edit chassis fpc number pic number] Release Information Description Statement introduced before JUNOS Release 7. 4. For the Channelized STM1 IQ PIC or Channelized STM1 PIC, configure virtual tributary mapping. For the Channelized STM1 PIC, you configure virtual tributary mapping at the [edit chassis fpc number pic number] hierarchy level. Options itu-t--International Telephony Union standard. [. . . ]