Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual

Network interfaces configuration

Table of Contents

Quick Links

Download this manual

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

Table of Contents

Summary of Contents for Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010

Page 1 JUNOS® Software Network Interfaces Configuration Guide Release 10.1 Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, California 94089 408-745-2000 www.juniper.net Published: 2010-01-22...
Page 2 Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312, 6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Page 3 AND (B) YOU MAY CONTACT JUNIPER NETWORKS REGARDING LICENSE TERMS. 1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer s principal office is located in the Americas) or Juniper Networks (Cayman) Limited (if the Customer s principal office is located outside the Americas) (such applicable entity being referred to herein as “Juniper”), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller the applicable license(s) for use of the Software (“Customer”)
Page 4 (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 http://www.gnu.org/licenses/gpl.html...
Page 5 agreements relating to the Software, whether oral or written (including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained herein.
Page 7 Abbreviated Table of Contents About This Guide lxiii Part 1 Network Interfaces Configuration Statements Overview Chapter 1 Network Interfaces Configuration Statements and Hierarchy Part 2 Router Interfaces Configuration Concepts Chapter 2 Understanding Router Interfaces Chapter 3 Configuring Physical Interface Properties Chapter 4 Configuring Logical Interface Properties Chapter 5...
Page 8 JUNOS 10.1 Network Interfaces Configuration Guide Chapter 18 Configuring Channelized OC48/STM16 IQE Interfaces Chapter 19 Configuring Channelized OC12/STM4 Interfaces Chapter 20 Configuring Channelized OC3 IQ and IQE Interfaces Chapter 21 Configuring Channelized STM1 Interfaces Chapter 22 Configuring Channelized T3 Interfaces Chapter 23 Configuring Channelized T1 Interfaces Chapter 24...
Page 9 Abbreviated Table of Contents Chapter 54 Configuring 10-Gigabit Ethernet Framing Chapter 55 Configuring 10-Gigabit Ethernet Notification of Link Down Alarm Chapter 56 Configuring 10-Gigabit Ethernet Notification of Link Down for Optics Alarms Chapter 57 Configuring Point-to-Point Protocol over Ethernet Chapter 58 Configuring Ethernet Ring Protection Switching Chapter 59 Example Ethernet Configurations...
Page 10 JUNOS 10.1 Network Interfaces Configuration Guide...
Page 11: Table Of Contents
Table of Contents About This Guide lxiii JUNOS Documentation and Release Notes ...........lxiii Objectives ....................lxiv Audience ......................lxiv Supported Routing Platforms ...............lxiv Using the Indexes ..................lxv Using the Examples in This Manual ..............lxv Merging a Full Example ................lxv Merging a Snippet .................lxvi Documentation Conventions ...............lxvi Documentation Feedback ................lxviii Requesting Technical Support ..............lxviii...
Page 12 JUNOS 10.1 Network Interfaces Configuration Guide Part 2 Router Interfaces Configuration Concepts Chapter 2 Understanding Router Interfaces Router Interfaces Overview ................32 Types of Interfaces Overview ................32 Permanent Interfaces Overview ..............33 Understanding Management Ethernet Interfaces ...........33 Understanding Internal Ethernet Interfaces ...........34 Understanding Transient Interfaces ...............36 Understanding Services Interfaces ..............36 Container Interfaces Overview ..............38...
Page 13 Table of Contents Specifying OC768-over-OC192 Mode ............107 Adding an Interface Description to the Configuration ........108 Example: Adding an Interface Description to the Configuration ....108 Configuring the Link Characteristics ............109 Configuring the Media MTU .................110 Configuring Interface Encapsulation on Physical Interfaces ......118 Configuring the Encapsulation on a Physical Interface ......118 Encapsulation Capabilities ..............122 Example: Configuring the Encapsulation on a Physical Interface ..123...
Page 14 JUNOS 10.1 Network Interfaces Configuration Guide Chapter 4 Configuring Logical Interface Properties Logical Interfaces Configuration Properties Overview ........155 Logical Interfaces Configuration Statements ..........156 Logical Interfaces Statements List ..............159 Specifying the Logical Interface Number .............166 Configuring Logical System Interface Properties ..........166 Example: Configuring Logical System Interface Properties ....167 Adding a Logical Unit Description to the Configuration .......168 Configuring a Point-to-Point Connection ............168...
Page 15 Table of Contents Assigning a Destination Profile to the Remote End .......191 Configuring an Unnumbered Interface ............192 Configuring an Unnumbered Point-to-Point Interface ......192 Example: Configuring an Unnumbered Point-to-Point Interface ..192 Configuring an Unnumbered Ethernet or Demux Interface ....193 Configuring a Preferred Source Address for Unnumbered Ethernet or Demux Interfaces ..............194 Configuring Static Routes on Unnumbered Ethernet Interfaces ..195 Restrictions for Configuring Unnumbered Ethernet Interfaces ..195...
Page 16 JUNOS 10.1 Network Interfaces Configuration Guide Chapter 6 Configuring Circuit and Translational Cross-Connects Circuit and Translational Cross-Connects Overview ........229 Defining the Encapsulation for Switching Cross-Connects ......231 Configuring PPP or Cisco HDLC Circuits ..........231 Configuring ATM Circuits ..............232 Configuring Frame Relay Circuits ............232 Configuring Ethernet CCC Circuits ............233 Configuring Ethernet VLAN Circuits ............234 Defining the Connection for Switching Cross-Connects .......234...
Page 17 Table of Contents Part 3 Configuring Special Router Interfaces Chapter 8 Displaying the Internal Ethernet Interface Internal Ethernet Interface Overview ............251 Displaying the Internal Ethernet Interface for M Series, MX Series, and Most T Series Routers ..................251 Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus Router ...................252 Chapter 9 Configuring Discard Interfaces...
Page 18 JUNOS 10.1 Network Interfaces Configuration Guide Invalid X.21 Interface Statements ..........274 Configuring the Serial Clocking Mode ............275 Inverting the Serial Interface Transmit Clock ........276 Configuring the DTE Clock Rate ............276 Configuring the Serial Idle Cycle Flag ............277 Configuring the Serial Signal Handling ............278 Configuring the Serial DTR Circuit ...............280 Configuring Serial Signal Polarities ..............281 Configuring Serial Loopback Capability ............281...
Page 19 Table of Contents Configuring Inverse ATM1 or ATM2 ARP .............326 Defining the ATM Traffic-Shaping Profile .............326 Configuring ATM CBR ................328 Configuring ATM2 IQ Real-Time VBR ............328 Configuring ATM VBR ................329 Specifying ATM1 Shaping Values ............329 Example: Specifying ATM1 Shaping Values ........331 Specifying ATM2 IQ Shaping Values .............332 Configuring the ATM1 Queue Length ............333 Configuring the ATM2 IQ EPD Threshold ............334...
Page 20 JUNOS 10.1 Network Interfaces Configuration Guide Chapter 15 Configuring ATM-over-SHDSL Interfaces ATM-over-SHDSL Overview .................369 Configuring ATM Mode for SHDSL Overview ..........370 Configuring ATM Mode on the PIM ..............371 Configuring SHDSL Operating Mode on an ATM Physical Interface .....372 Configuring Encapsulation on the ATM Physical Interface ......372 Configuring Logical Interface Properties ............373 Example: Configuring an ATM-over-SHDSL Interface ........374 Verifying an ATM-over-SHDSL Interface Configuration ........375...
Page 21 Table of Contents Chapter 18 Configuring Channelized OC48/STM16 IQE Interfaces Channelized OC48/STM16 IQE Interfaces Overview ........413 Configuring Channelized OC48/STM16 IQE Interfaces in SONET Mode ..415 Configuring OC12 Interfaces ..............415 Example: Configuring OC12 Interfaces ...........416 Configuring OC3 Interfaces ..............416 Example: Configuring OC3 Interfaces ..........417 Configuring T3 Interfaces ..............417 Example: Configuring T3 Interfaces ..........418 Configuring T1 Interfaces ..............418...
Page 22 JUNOS 10.1 Network Interfaces Configuration Guide Configuring OC3 Interfaces ..............437 Example: Configuring OC3 Interfaces ..........437 Configuring T1 Interfaces on COC12 IQ and IQE Interfaces ....438 Example: Configuring T1 Interfaces ..........439 Configuring NxDS0 Interfaces ...............439 Example: Configuring NxDS0 Interfaces .........441 Configuring Fractional T1 Interfaces .............442 Example: Configuring Fractional T1 Interfaces .......442 Configuring Channelized OC12/STM4 IQE Interfaces (SDH Mode) ....442 Configuring Channelized OC12/STM4 IQE PICs for SDH Mode .....443...
Page 23 Table of Contents Configuring Link PIC Failover on Channelized OC12/STM4 IQ and IQE Interfaces ....................456 Example: Configuring a Channelized OC12 IQ Interface as an Unpartitioned Clear Channel ..................457 Example: Configuring Channelized OC12 Interfaces with Partitioned Channels ....................460 Chapter 20 Configuring Channelized OC3 IQ and IQE Interfaces Channelized OC3 IQ and IQE Overview ............463 Partitions, OC Slices, Interface Types, and Time Slots .........464 Configuring a Clear Channel on Channelized OC3 IQ and IQE PICs .....465...
Page 24 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Fractional T1 IQ and IQE Interfaces ........490 Example: Configuring Fractional T1 IQ Interfaces ......491 Configuring an NxDS0 IQ Interface ............491 Example: Configuring an NxDS0 IQ Interface .........492 Configuring Channelized DS3-to-DS0 Interfaces ..........492 Configuring Channelized DS3-to-DS1 Interfaces ..........495 Example: Configuring Channelized T3 IQ Interfaces ........496 Examples: Configuring Channelized DS3-to-DS0 Interfaces ......497 Examples: Configuring Channelized DS3-to-DS1 Interfaces ......500...
Page 25 Table of Contents Part 8 Configuring Circuit Emulation PICs Chapter 26 Circuit Emulation PICs Overview Mobile Backhaul and Circuit Emulation Overview ........529 Mobile Backhaul Application Overview ............530 Understanding Circuit Emulation PIC Types ..........530 Understanding Circuit Emulation PIC Clocking Features ......531 Understanding T1 and E1 Options Exceptions on Circuit Emulation PICs ..531 Displaying Information About Circuit Emulation PICs .........532 Chapter 27...
Page 26 JUNOS 10.1 Network Interfaces Configuration Guide Minimum Active Links ................546 State Transition Variables: Alpha, Beta, and Gamma ......546 IMA Link Addition and Deletion ............547 IMA Test Pattern Procedure ..............547 Per-PIC Limit on the Number of Links ...........547 IMA Group Alarms and Group Defects ..........547 IMA Link Alarms and Link Defects ............548 IMA Group Statistics ................549 IMA Link Statistics ................550...
Page 27 Table of Contents Chapter 30 Configuring E3 Interfaces E3 Interfaces Overview ................569 Configuring E3 Physical Interface Properties ..........570 Configuring E3 BERT Properties ..............570 Configuring the E3 CSU Compatibility Mode ..........571 Configuring the E3 Frame Checksum ............572 Configuring the E3 Idle Cycle Flag ...............573 Configuring E3 Data Inversion ..............573 Configuring E3 Loopback Capability ............573 Example: Configuring E3 Loopback Capability ........574...
Page 28 JUNOS 10.1 Network Interfaces Configuration Guide Configuring T3 HDLC Payload Scrambling ..........596 Configuring T3 Start and End Flags .............597 Examples: Configuring T3 Interfaces ............597 Part 10 Configuring Ethernet Interfaces Chapter 33 Configuring Ethernet Interfaces Ethernet Interfaces Overview ..............603 Configuring Ethernet Physical Interface Properties ........604 Configuring J Series Services Router Switching Interfaces ......608 Example: Configuring J Series Services Router Switching Interfaces ..609 MX Series Router Interface Identifiers ............609...
Page 29 Table of Contents Binding a List of VLAN IDs to a Logical Interface ........627 Binding a List of VLAN IDs to a Single-Tag Logical Interface ...627 Binding a List of VLAN IDs to a Dual-Tag Logical Interface .....628 Example: Binding Lists of VLAN IDs to Logical Interfaces ....628 Configuring VLAN Encapsulation ..............629 Example: Configuring VLAN Encapsulation on a Gigabit Ethernet Interface ..................630...
Page 30 JUNOS 10.1 Network Interfaces Configuration Guide Chapter 35 Configuring Aggregated Ethernet Interfaces Aggregated Ethernet Interfaces Overview ............643 Platform Support for Aggregated Ethernet Interfaces ......644 Configuration Guidelines for Aggregated Ethernet Interfaces ....644 Configuring an Aggregated Ethernet Interface ..........645 Deleting an Aggregated Ethernet Interface ..........646 Configuring Multi-Chassis Link Aggregation ..........646 Configuring Aggregated Ethernet Link Protection ........647 Configuring Link Protection for Aggregated Ethernet Interfaces ....648...
Page 31 Table of Contents Configuring Dual VLAN Tags ...............669 Configuring Inner and Outer TPIDs and VLAN IDs ........669 Stacking a VLAN Tag ...................673 Removing a VLAN Tag .................673 Removing the Outer and Inner VLAN Tags ..........674 Removing the Outer VLAN Tag and Rewriting the Inner VLAN Tag .....674 Stacking Two VLAN Tags ................675 Rewriting the VLAN Tag on Tagged Frames ..........675 Rewriting a VLAN Tag on Untagged Frames ..........676...
Page 32 JUNOS 10.1 Network Interfaces Configuration Guide Chapter 42 Enabling Passive Monitoring on Ethernet Interfaces Passive Monitoring on Ethernet Interfaces Overview ........701 Enabling Passive Monitoring on Ethernet Interfaces ........701 Chapter 43 Configuring IEEE 802.1ag OAM Connectivity-Fault Management IEEE 802.1ag OAM Connectivity Fault Management Overview ....703 Connectivity Fault Management Key Elements ........704 Creating the Maintenance Domain ..............705 Configuring the Maintenance Domain Name Format ......705...
Page 33 Table of Contents Example E-LMI Configuration ...............719 Configuring PE1 ................719 Configuring PE2 ................721 Configuring Two UNIs Sharing the Same EVC ........722 Configuring Port Status TLV and Interface Status TLV ........723 TLVs Overview ..................723 Various TLVs for CFM PDUs ..............723 Support for Additional Optional TLVs ............725 Port Status TLV ................726 Interface Status TLV ...............728 MAC Status Defects ................731...
Page 34 JUNOS 10.1 Network Interfaces Configuration Guide ETH-DM Frame Counts .................750 ETH-DM Frame Count Retrieval ............751 Frame Counts Stored in CFM Databases .........751 One-Way ETH-DM Frame Counts ...........752 Two-Way ETH-DM Frame Counts ...........752 Configuring Routers to Support an ETH-DM Session ........753 Configuring MEP Interfaces ..............753 Ensuring that Distributed ppm Is Not Disabled ........754 Enabling the Hardware-Assisted Timestamping Option ......755...
Page 35 Table of Contents Monitoring Protocol Status ................780 Configuring Threshold Values for Fault Events in an Action Profile .....780 Applying an Action Profile ................781 Setting a Remote Interface into Loopback Mode .........781 Enabling Remote Loopback Support on the Local Interface ......781 Example: Configuring IEEE 802.3ah OAM Support on an Interface .....782 Chapter 47 Configuring VRRP and VRRP for IPv6...
Page 36 JUNOS 10.1 Network Interfaces Configuration Guide Chapter 52 Configuring 10-port 10-Gigabit Oversubscribed Ethernet PICs 10-port 10-Gigabit Oversubscribed Ethernet PIC Overview ......809 Configuring Line Rate Mode on 10-port 10-Gigabit Oversubscribed Ethernet PIC ......................811 Example: Handling Oversubscription on 10-port 10-Gigabit Oversubscribed Ethernet PIC ..................812 Chapter 53 Configuring the 10-Gigabit Ethernet DWDM Interface Wavelength 10-Gigabit Ethernet DWDM Interface Wavelength Overview .......815...
Page 37 Table of Contents Benefits of Configuring PPPoE Service Name Tables ......829 Configuring PPPoE ..................830 Setting the Appropriate Encapsulation on the PPPoE Interface .....831 Configuring PPPoE Encapsulation on an Ethernet Interface ....831 Configuring PPPoE Encapsulation on an ATM-over-ADSL Interface ..................832 Configuring a PPPoE Interface ..............832 Configuring the PPPoE Underlying Interface ........833 Identifying the Access Concentrator ..........833 Configuring the PPPoE Automatic Reconnect Wait Timer ....833...
Page 38 JUNOS 10.1 Network Interfaces Configuration Guide Logical Ring ..................853 FDB Flush .....................853 Traffic Blocking and Forwarding ............853 RAPS Message Blocking and Forwarding ..........854 Dedicated Signaling Control Channel ............855 RAPS Message Termination ..............855 Manual Switch ..................855 Nonrevertive Switch ................855 Multiple Rings ..................855 Node ID ....................856 Bridge Domains with the Ring Port ............856 Configuring Ethernet Ring Protection Switching ..........856...
Page 39 Table of Contents Example: Complete ISDN Called-Calling Router Configuration ..889 Disabling ISDN Processes ................892 Part 12 Configuring SONET/SDH Interfaces Chapter 61 Configuring SONET/SDH Interfaces SONET/SDH Interfaces Overview ..............895 Configuring SONET/SDH Physical Interface Properties ........896 Configuring SONET/SDH Framing ............898 Configuring SONET/SDH Interface Speed ..........899 Configuring SONET/SDH Header Byte Values ........901 Configuring an Incrementing STM ID ............902 Configuring the SONET/SDH Frame Checksum ........903...
Page 40 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Interface Encapsulation on SONET/SDH Interfaces ....933 Configuring the Encapsulation on a Physical SONET/SDH Interface ..933 Example: Configuring the Encapsulation on a Physical SONET/SDH Interface ..................935 Configuring the Encapsulation on a Logical SONET/SDH Interface ..935 Example: Configuring SONET/SDH Interfaces ..........936 Configuring Aggregated SONET/SDH Interfaces ...........936 Configuring SONET/SDH Link Aggregation ..........937...
Page 41 Table of Contents aggregated-ether-options ................969 aggregated-sonet-options ................971 alarm ......................972 allow-any-vci ....................972 allow-fragmentation ..................973 allow-remote-loopback ................974 annex ......................975 apply-action-profile ..................975 aps ......................976 arp ......................977 asynchronous-notification ................978 atm-encapsulation ..................979 atm-options ....................980 atm-scheduler-map ..................981 authentication .....................982 authentication-key ..................983 authentication-profile-name ................984 authenticator ....................985 auto-configure .....................986 auto-discovery .....................987 auto-negotiation ..................988 auto-negotiation (Gigabit Ethernet) ............989...
Page 42 JUNOS 10.1 Network Interfaces Configuration Guide cbit-parity ....................1017 cbr ......................1018 cell-bundle-size ..................1019 chap ......................1020 chap-secret ....................1021 circuit-type ....................1022 cisco-interoperability .................1022 classifier ....................1023 clear-dont-fragment-bit ................1024 client ......................1024 clock-rate ....................1025 clocking .....................1026 clocking-mode ...................1027 compatibility-mode ...................1028 compression ....................1029 compression (PPP Properties) .............1029 compression (Voice Services) ..............1030 compression-device ...................1031 connections ....................1032...
Page 43 Table of Contents demux-source ...................1058 demux-source (Demux Interface) ............1059 demux-source (Underlying Interface) ..........1060 demux0 .....................1061 description ....................1062 destination ....................1063 destination (IPCP) ................1063 destination (Routing Instance) ............1064 destination (Tunnels) ................1065 destination-class-usage ................1066 destination-profile ..................1067 dial-options ....................1068 dial-string ....................1069 dialer ......................1069 dialer-options ....................1070 dialin ......................1071 direction ....................1072 disable .......................1073...
Page 44 JUNOS 10.1 Network Interfaces Configuration Guide epd-threshold ....................1106 epd-threshold (Logical Interface) ............1107 epd-threshold (Physical Interface) ............1108 es-options ....................1109 ethernet ....................1110 ethernet-policer-profile ................1113 ethernet-ring .....................1114 ethernet-switch-profile ................1115 eui-64 ......................1117 evcs ......................1118 event ......................1119 event-thresholds ..................1120 f-max-period .....................1121 facility-override ..................1122 failover-delay .....................1122 family ......................1123 fastether-options ..................1126 fcs ......................1127...
Page 45 Table of Contents idle-cycle-flag ....................1158 idle-timeout ....................1159 ieee802.1p ....................1160 if-exceeding ....................1161 ignore ......................1162 ignore-all ....................1163 ignore-l3-incompletes ................1163 ilmi ......................1164 ima-group-options ..................1165 ima-link-options ..................1166 inactivity-timeout ..................1167 incoming-called-number ................1168 incoming-map ...................1169 indication ....................1170 indication-polarity ..................1170 ingress-rate-limit ..................1171 init-command-string ..................1172 initial-route-check ..................1173 inner-tag-protocol-id ..................1174 inner-vlan-id ....................1175 inner-vlan-id-range ..................1176 input ......................1177...
Page 46 JUNOS 10.1 Network Interfaces Configuration Guide isdn-options ....................1204 keep-address-and-control ................1205 keepalives ....................1206 key ......................1207 l2tp-interface-id ..................1208 lacp ......................1209 lacp (802.3ad) ..................1210 lacp (Aggregated Ethernet) ..............1211 layer2-policer ....................1212 lcp-max-conf-req ..................1213 lcp-restart-timer ..................1214 level ......................1215 line-encoding .....................1216 line-protocol ....................1217 line-rate .....................1218 linear-red-profile ..................1219 linear-red-profiles ..................1220 link-adjacency-loss ..................1220 link-discovery ....................1221...
Page 47 Table of Contents low-plp-threshold ..................1253 lowest-priority-defect .................1254 lsq-failure-options ..................1255 mac ......................1255 mac-address ....................1256 mac-address (Accept Source Mac) ............1257 mac-address (VLAN and Stacked VLAN Interfaces) ......1257 mac-learn-enable ..................1258 mac-validate ....................1259 maintenance-association ................1260 maintenance-domain ................1261 master-only ....................1262 maximum-contexts ...................1263 maximum-requests ...................1264 maximum-vcs ...................1265 mc-ae ......................1266 member-interface-speed ................1267 member-interface-type ................1267...
Page 48 JUNOS 10.1 Network Interfaces Configuration Guide no-feac-loop-respond .................1295 no-flow-control ..................1295 no-gratuitous-arp-reply ................1295 no-gratuitous-arp-request ................1295 no-keepalives ....................1296 no-long-buildout ..................1296 no-loopback ....................1296 no-mac-learn-enable ..................1296 no-partition ....................1297 no-payload-scrambler ................1298 no-redirects ....................1298 no-source-filtering ..................1298 no-syslog ....................1299 no-termination-request ................1299 no-translate-discard-eligible ...............1299 no-translate-fecn-and-becn ................1299 no-unframed .....................1299 no-z0-increment ..................1300 node-id ......................1300 non-revertive .....................1300...
Page 49 Table of Contents payload-scrambler ..................1331 payload-size ....................1332 pdu-interval ....................1333 pdu-threshold ....................1333 peer-unit ....................1334 per-unit-scheduler ..................1335 performance-monitoring ................1336 periodic .....................1337 pfc ......................1337 pic-type .....................1338 plp-to-clp ....................1338 plp1 ......................1339 point-to-point ....................1340 policer .......................1341 policer (CFM Firewall) .................1341 policer (CFM Global) ................1342 policer (CFM Session) ................1343 policer (CoS) ..................1344 policer (Interface) ................1345 policer (MAC) ..................1346...
Page 50 JUNOS 10.1 Network Interfaces Configuration Guide proxy-arp ....................1372 push ......................1372 push-push ....................1373 queue-depth ....................1374 queue-length .....................1375 queues .......................1376 quiet-period ....................1377 radius-realm ....................1378 ranges .......................1379 ranges (Dynamic Stacked VLAN) ............1380 ranges (Dynamic VLAN) ..............1380 rate ......................1381 reassemble-packets ...................1382 reauthentication ..................1382 receive-bucket ...................1383 receive-options-packets ................1384 receive-ttl-exceeded ..................1384 red-differential-delay .................1385...
Page 51 Table of Contents service-domain ..................1417 service-filter ....................1418 service-name .....................1419 service-name-table ..................1419 service-name-tables ...................1420 service-set ....................1421 services .....................1422 services-options ..................1423 shaping .....................1424 shdsl-options .....................1425 short-name-format ..................1426 short-sequence ..................1427 snext ......................1428 snr-margin ....................1429 sonet-options .....................1430 source .......................1432 source-address-filter ..................1433 source-class-usage ..................1434 source-filtering ..................1435 speed ......................1436 speed (Ethernet) .................1436 speed (MX Series DPC) ...............1437...
Page 52 JUNOS 10.1 Network Interfaces Configuration Guide tag-protocol-id ...................1463 tag-protocol-id (TPIDs Expected to Be Sent or Received) .....1464 tag-protocol-id (TPID to Rewrite) ............1465 tei-option ....................1466 then ......................1467 threshold ....................1468 timeslots ....................1469 tm ......................1471 tm-polarity ....................1471 traceoptions ....................1472 traceoptions (ICCP) ................1473 traceoptions (Individual Interfaces) .............1474 traceoptions (Interface Process) ............1475 traceoptions (LACP) ................1478 traceoptions (PPP Process) ..............1481...
Page 53 Table of Contents vlan-id (VLAN ID to Rewrite) ...............1521 vlan-id-list ....................1522 vlan-id-list (Ethernet VLAN Circuit) ............1523 vlan-id-list (Interface in Bridge Domain) ..........1525 vlan-id-range .....................1526 vlan-ranges ....................1527 vlan-rewrite ....................1528 vlan-tagging ....................1528 vlan-tags ....................1529 vlan-tags (Dual-Tagged Logical Interface) ..........1530 vlan-tags (Stacked VLAN Tags) ............1532 vlan-tags-outer ...................1534 vlan-vci-tagging ..................1534 vpi ......................1535...
Page 54 JUNOS 10.1 Network Interfaces Configuration Guide Table of Contents...
Page 55: List Of Figures
List of Figures Part 2 Router Interfaces Configuration Concepts Chapter 2 Understanding Router Interfaces Figure 1: APS Interface ..................38 Figure 2: Container Interface .................39 Figure 3: Routing Matrix ................59 Figure 4: Routing Matrix Based on a TX Matrix Plus Router ......61 Figure 5: Interface Slot, PIC, and Port Locations ..........64 Figure 6: Clock Sources .................66 Chapter 5...
Page 56 JUNOS 10.1 Network Interfaces Configuration Guide Figure 22: Channelized OC48/STM16 IQE PIC (in SDH Mode) .....404 Figure 23: Channelized OC12 IQ PIC and Channelized OC12/STM4 IQE PIC (in SONET Mode) ..................405 Figure 24: Channelized OC12/STM4 IQE PIC (in SDH Mode) .......405 Figure 25: Channelized OC12/STM4 IQ PIC (in SDH Mode) ......406 Figure 26: Channelized OC3 Ports (in SONET Mode) on Channelized OC3 IQ and Channelized OC3/STM1 IQE PICs ...........406...
Page 57 List of Figures Figure 52: 4-Port Channelized COC3/STM1 Circuit Emulation PIC Possible Interfaces (T1 Size) ................543 Figure 53: 4-Port Channelized COC3/STM1 Circuit Emulation PIC Possible Interfaces (E1 Size) ................543 Part 9 Configuring E1, E3, T1, and T3 Interfaces Chapter 29 Configuring E1 Interfaces Figure 54: Remote and Local E1 Loopback ..........565 Chapter 30...
Page 58 JUNOS 10.1 Network Interfaces Configuration Guide Figure 72: ISDN Backup Topology ...............879 Figure 73: Dialer Filter Topology ..............881 Figure 74: Bandwidth-on-Demand Topology ..........883 Figure 75: Dialer Watch Topology ...............888 Part 12 Configuring SONET/SDH Interfaces Chapter 61 Configuring SONET/SDH Interfaces Figure 76: APS/MSP Configuration Topologies ..........912 Figure 77: APS Load Sharing Between Circuit Pairs ........926 lviii List of Figures...
Page 59: List Of Tables
List of Tables About This Guide lxiii Table 1: Notice Icons ..................lxvii Table 2: Text and Syntax Conventions ............lxvii Part 2 Router Interfaces Configuration Concepts Chapter 2 Understanding Router Interfaces Table 3: Encapsulation Support by Interface Type .........40 Table 4: FPC Numbering for T640 Routers in a Routing Matrix .....60 Table 5: One-to-One FPC Numbering for T640 Routers in a Routing Matrix .....................60 Table 6: FPC Numbering for T1600 Routers in a Routing Matrix ....62...
Page 60 JUNOS 10.1 Network Interfaces Configuration Guide Part 5 Configuring ATM Interfaces Chapter 13 Configuring ATM Interfaces Table 25: ATM1 and ATM2 IQ Supported Features ........294 Table 26: ILMI Support by Encapsulation Type ..........300 Table 27: Shaping Rate Range by Interface Type .........328 Table 28: ATM1 Traffic-Shaping Rates ............331 Table 29: EPD Threshold Range by Interface Type ........335 Table 30: ATM Logical Interface Encapsulation Types .........339...
Page 61 List of Tables Table 51: IMA Link Defects with IMA Standard Requirement Numbers ..549 Table 52: IMA Link Statistics with IMA Standard Requirement Numbers ..550 Part 9 Configuring E1, E3, T1, and T3 Interfaces Chapter 30 Configuring E3 Interfaces Table 53: Subrate Values for E3 Digital Link Compatibility Mode ....572 Chapter 32 Configuring T3 Interfaces Table 54: Subrate Values for T3 Digital Link Compatibility Mode ....591...
Page 62 JUNOS 10.1 Network Interfaces Configuration Guide Table 76: Default Forwarding Classes ............789 Chapter 49 Configuring Gigabit Ethernet Autonegotiation Table 77: Mode and Autonegotiation Status (Local) ........799 Table 78: Mode and Autonegotiation Status (Remote) .........801 Chapter 52 Configuring 10-port 10-Gigabit Oversubscribed Ethernet PICs Table 79: Capabilities of 10-Port 10-Gigabit OSE PICs .........811 Table 80: Handling Oversubscription on 10-port 10-Gigabit OSE PICs ..812 Chapter 53...
Page 63: About This Guide Lxiii
If the information in the latest release notes differs from the information in the documentation, follow the JUNOS Release Notes. To obtain the most current version of all Juniper Networks® technical documentation, see the product documentation page on the Juniper Networks website at http://www.juniper.net/techpubs/...
Page 64 Audience This guide is designed for network administrators who are configuring and monitoring a Juniper Networks M Series, MX Series, T Series, EX Series, or J Series router or switch. To use this guide, you need a broad understanding of networks in general, the Internet in particular, networking principles, and network configuration.
Page 65: Merging A Full Example
About This Guide MX Series T Series Using the Indexes This reference contains two indexes: a complete index that includes topic entries, and an index of statements and commands only. In the index of statements and commands, an entry refers to a statement summary section only.
Page 66: Merging A Snippet
JUNOS 10.1 Network Interfaces Configuration Guide family inet { address 10.0.0.1/24; Merge the contents of the file into your routing platform configuration by issuing load merge configuration mode command: [edit] user@host# load merge /var/tmp/ex-script.conf load complete Merging a Snippet To merge a snippet, follow these steps: From the HTML or PDF version of the manual, copy a configuration snippet into a text file, save the file with a name, and copy the file to a directory on your routing platform.
Page 67: Table 1: Notice Icons
About This Guide Table 1: Notice Icons Icon Meaning Description Informational note Indicates important features or instructions. Caution Indicates a situation that might result in loss of data or hardware damage. Warning Alerts you to the risk of personal injury or death. Laser warning Alerts you to the risk of personal injury from a laser.
Page 68: Documentation Feedback
URL or page number Software release version (if applicable) Requesting Technical Support Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). If you are a customer with an active J-Care or JNASC support lxviii Documentation Feedback...
Page 69: Self-Help Online Tools And Resources
7 days a week, 365 days a year. Self-Help Online Tools and Resources For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings: http://www.juniper.net/customers/support/...
Page 70 JUNOS 10.1 Network Interfaces Configuration Guide Requesting Technical Support...
Page 71: Part 1 Network Interfaces Configuration Statements Overview
Part 1 Network Interfaces Configuration Statements Overview Network Interfaces Configuration Statements and Hierarchy on page 3 Network Interfaces Configuration Statements Overview...
Page 72 JUNOS 10.1 Network Interfaces Configuration Guide Network Interfaces Configuration Statements Overview...
Page 73: Network Interfaces Configuration Statements And Hierarchy
Chapter 1 Network Interfaces Configuration Statements and Hierarchy This chapter shows the complete configuration statement hierarchy, listing all possible configuration statements and showing their level in the configuration hierarchy. When you are configuring the JUNOS Software, your current hierarchy level is shown in the banner on the line preceding the user@host# prompt.
Page 74 JUNOS 10.1 Network Interfaces Configuration Guide device-count number; fpc slot-number{ pic pic-number { adaptive-services{ service-package (layer-2 | layer-3); aggregate-ports; atm-cell-relay-accumulation; atm-l2circuit-mode (aal5 | cell | trunk trunk); ce1 { e1 link-number { channel-group group-number; timeslots time-slot-range; ct1 { t1 link-number { channel-group group-number;...
Page 75 Chapter 1: Network Interfaces Configuration Statements and Hierarchy NOTE: The accounting-profile statement is an exception to this rule. The accounting-profile statement can be configured at the [edit interfaces interface-name hierarchy level, but it cannot be configured at the unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] hierarchy level.
Page 76 JUNOS 10.1 Network Interfaces Configuration Guide pop-all-labels { required-depth number; pic-type (atm1 | atm2); plp-to-clp; promiscuous-mode { vpi vpi-identifier; scheduler-maps map-name { forwarding-class class-name { epd-threshold cells plp1 cells; linear-red-profile profile-name; priority (high | low); transmit-weight (cells number | percent number); vc-cos-mode (alternate | strict);...
Page 77: [Edit Interfaces] Hierarchy Level
Chapter 1: Network Interfaces Configuration Statements and Hierarchy dcd (ignore | normal | require); dsr (ignore | normal | require); dtr signal-handling-option; ignore-all; indication (ignore | normal | require); rts (assert | de-assert | normal); tm (ignore | normal | require); dtr-circuit (balanced | unbalanced);...
Page 78 JUNOS 10.1 Network Interfaces Configuration Guide loopback (local | remote); (payload-scrambler | no-payload-scrambler); start-end-flag (filler | shared); (unframed | no-unframed); encapsulation type; es-options { backup-interface es-fpc/pic/port; fastether-options { 802.3ad aex; (flow-control | no-flow-control); ignore-l3-incompletes; ingress-rate-limit rate; (loopback | no-loopback); mpls { pop-all-labels { required-depth number;...
Page 79 Chapter 1: Network Interfaces Configuration Statements and Hierarchy loss-priority (high | low); policer cos-policer-name { aggregate { bandwidth-limit bps; burst-size-limit bytes; premium { bandwidth-limit bps; burst-size-limit bytes; (gratuitous-arp-reply | no-gratuitous-arp-reply); hold-time up milliseconds down milliseconds; ima-group-options { differential-delay number; frame-length (32 | 64 | 128 | 256); frame-synchronization { alpha number;...
Page 80 JUNOS 10.1 Network Interfaces Configuration Guide static-tei-val value; switch-type (att5e | etsi | ni1 | ntdms100 | ntt); t310 seconds; tei-option (first-call | power-up); keepalives <down-count number> <interval seconds> <up-count number>; link-mode mode; lmi { lmi-type (ansi | itu); n391dte number; n392dce number;...
Page 81 Chapter 1: Network Interfaces Configuration Statements and Hierarchy otn-options { fec (efec | gfec | none); (laser-enable | no-laser-enable); (line-loopback | no-line-loopback); pass-thru; rate (fixed-stuff-bytes | no-fixed-stuff-bytes | pass-thru); transmit-payload-type number trigger (oc-lof | oc-lom | oc-los | oc-wavelength-lock | odu-ais | odu-bbe-th | odu-bdi | odu-es-th | odu-lck | odu-oci | odu-sd | odu-ses-th | odu-ttim | odu-uas-th | opu-ptm | otu-ais | otu-bbe-th | otu-bdi | otu-es-th | otu-fec-deg | otu-fec-exe | otu-iae | otu-sd | otu-ses-th | otu-ttim | otu-uas-th);...
Page 82 JUNOS 10.1 Network Interfaces Configuration Guide satop-options { payload-size n; schedulers number; serial-options { clock-rate rate; clocking-mode (dce | internal | loop); control-polarity (negative | positive); cts-polarity (negative | positive); dcd-polarity (negative | positive); dce-options { control-signal (assert | de-assert | normal); cts (ignore | normal | require);...
Page 83 Chapter 1: Network Interfaces Configuration Statements and Hierarchy line-rate line-rate; loopback (local | remote); snr-margin { current margin; snext margin; sonet-options { aggregate asx; aps { advertise-interval milliseconds; annex-b authentication-key key; force; hold-time milliseconds; lockout; neighbor address; paired-group group-name; preserve-interface; protect-circuit group-name;...
Page 84 JUNOS 10.1 Network Interfaces Configuration Guide speed (10m | 100m | 1g); link-mode (full-duplex | half-duplex); t1-options { bert-algorithm algorithm; bert-error-rate rate; bert-period seconds; buildout value; byte-encoding (nx56 | nx64); crc-major-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5); crc-minor-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5 | 5e-6 | 1e-6);...
Page 85 Chapter 1: Network Interfaces Configuration Statements and Hierarchy policer { input cos-policer-name; output cos-policer-name; accounting-profile name; allow-any-vci; atm-scheduler-map (map-name | default); backup-options { interface interface-name; bandwidth rate; cell-bundle-size cells; clear-dont-fragment-bit; compression { rtp { f-max-period number; maximum-contexts number <force>; queues [ queue-numbers ]; port { minimum port-number;...
Page 86 JUNOS 10.1 Network Interfaces Configuration Guide disable; disable-mlppp-inner-ppp-pfc; dlci dlci-identifier; drop-timeout milliseconds; dynamic-call-admission-control { activation-priority priority; bearer-bandwidth-limit kilobits-per-second; encapsulation type; epd-threshold cells plp1 cells; fragment-threshold bytes; inner-vlan-id-range start start-id end end-id; input-vlan-map { (pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap); inner-tag-protocol-id tpid;...
Page 87 Chapter 1: Network Interfaces Configuration Statements and Hierarchy passive; compression { acfc; pfc; pap; default-pap-password password; local-name name; local-password password; passive; dynamic-profile profile-name; lcp-max-conf-req number lcp-restart-timer milliseconds; loopback-clear-timer seconds; ncp-max-conf-req number ncp-restart-timer milliseconds; pppoe-options { access-concentrator name; auto-reconnect seconds; (client | server); service-name name;...
Page 88 JUNOS 10.1 Network Interfaces Configuration Guide accounting { destination-class-usage; source-class-usage { direction; address address { destination address; bundle ml-fpc/pic/port | ls-fpc/pic/port); filter { group filter-group-number; input filter-name; input-list { [ filter-names ]; output filter-name; output-list { [ filter-names ]; ipsec-sa sa-name; keep-address-and-control;...
Page 89 Chapter 1: Network Interfaces Configuration Statements and Hierarchy unnumbered-address interface-name <destination address destination-profile profile-name | preferred-source-address address>; address address { arp ip-address (mac | multicast-mac) mac-address <publish>; broadcast address; destination address; destination-profile name; eui-64; multipoint-destination address (dlci dlci-identifier | vci vci-identifier); multipoint-destination address { epd-threshold cells plp1 cells;...
Page 90 JUNOS 10.1 Network Interfaces Configuration Guide [edit logical-systems] Hierarchy Level The following lists the statements that can be configured at the [edit logical-systems] hierarchy level that are also documented in this manual. For more information about logical systems, see the JUNOS Routing Protocols Configuration Guide. logical-systems logical-system-name { interfaces interface-name { unit logical-unit-number {...
Page 91 Chapter 1: Network Interfaces Configuration Statements and Hierarchy disable; dlci dlci-identifier; drop-timeout milliseconds; dynamic-call-admission-control { activation-priority priority; bearer-bandwidth-limit kilobits-per-second; encapsulation type; epd-threshold cells plp1 cells; fragment-threshold bytes; input-vlan-map { inner-tag-protocol-id; inner-vlan-id; (pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap); tag-protocol-id tpid;...
Page 92 JUNOS 10.1 Network Interfaces Configuration Guide compression { acfc; pfc; dynamic-profile profile-name; pap { default-pap-password password; local-name name; local-password password; passive; proxy-arp; service-domain (inside | outside); shaping { (cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst length);...
Page 93 Chapter 1: Network Interfaces Configuration Statements and Hierarchy output-list { [ filter-names ]; ipsec-sa sa-name; keep-address-and-control; mtu bytes; multicast-only; no-redirects; policer { arp policer-template-name; input policer-template-name; output policer-template-name; primary; proxy inet-address address; receive-options-packets; receive-ttl-exceeded; remote (inet-address address | mac-address address); rpf-check <fail-filter filter-name>...
Page 94: [Edit Protocols Connections] Hierarchy Level
JUNOS 10.1 Network Interfaces Configuration Guide queue-length number; vci vpi-identifier.vci-identifier; preferred; primary; (vrrp-group | vrrp-inet6-group) group-number { (accept-data | no-accept-data); advertise interval seconds; authentication-type authentication; authentication-key key; fast-interval milliseconds; (preempt | no-preempt) { hold-time seconds; priority-number number; track { priority-cost seconds; priority-hold-time interface-name { interface priority;...
Page 95: [Edit Protocols Dot1X] Hierarchy Level
Chapter 1: Network Interfaces Configuration Statements and Hierarchy [edit protocols dot1x] Hierarchy Level dot1x { authenticator authentication-profile-name access-profile-name; interface interface-ids { maximum-requests integer; retries integer; quiet-period seconds; transmit-period seconds; reauthentication (disable | interval seconds); server-timeout seconds; supplicant (single); supplicant-timeout seconds; [edit protocols iccp] Hierarchy Level iccp { traceoptions;...
Page 96 JUNOS 10.1 Network Interfaces Configuration Guide linktrace { age (30m | 10m | 1m | 30s | 10s); path-database-size path-database-size; maintenance-domain domain-name { bridge-domain name; routing-instance r1 { bridge-domain name; instance vpls-instance; interface (ge | xe) fpc/pic/port.domain; level number; maintenance-association name{ mep identifier { direction (up | down) interface (ge | xe) fpc/pic/port.domain;...
Page 97 Chapter 1: Network Interfaces Configuration Statements and Hierarchy frame-error count; frame-period count; frame-period-summary count; symbol-period count; protocol-down; interface interface-name { apply-action-profile profile-name; event-thresholds { frame-error count; frame-period count; frame-period-summary count; symbol-period count; link-discovery (active | passive); negotiation-options { allow-remote-loopback; no-allow-link-events; pdu-interval interval;...
Page 98 JUNOS 10.1 Network Interfaces Configuration Guide [edit protocols protection-group] Hierarchy Level ethernet-ring ring-name { east-interface { control-channel channel-name { vlan number; guard-interval number; node-id mac-address; restore-interval number; ring-protection-link-owner; west-interface { control-channel channel-name { vlan number; [edit protocols vrrp] Hierarchy Level traceoptions { file <filename>...
Page 99: Part 2 Router Interfaces Configuration Concepts
Part 2 Router Interfaces Configuration Concepts Understanding Router Interfaces on page 31 Configuring Physical Interface Properties on page 69 Configuring Logical Interface Properties on page 155 Configuring Protocol Family and Interface Address Properties on page 181 Configuring Circuit and Translational Cross-Connects on page 229 Tracing Interface Operations on page 247 Router Interfaces Configuration Concepts...
Page 100 JUNOS 10.1 Network Interfaces Configuration Guide Router Interfaces Configuration Concepts...
Page 101: Chapter 2 Understanding Router Interfaces
Chapter 2 Understanding Router Interfaces Router Interfaces Overview on page 32 Types of Interfaces Overview on page 32 Permanent Interfaces Overview on page 33 Understanding Management Ethernet Interfaces on page 33 Understanding Internal Ethernet Interfaces on page 34 Understanding Transient Interfaces on page 36 Understanding Services Interfaces on page 36 Container Interfaces Overview on page 38 Interface Encapsulations Overview on page 40...
Page 102: Router Interfaces Overview
JUNOS 10.1 Network Interfaces Configuration Guide Router Interfaces Overview Routers typically contain several different types of interfaces suited to various functions. For the interfaces on a router to function, you must configure them, specifying properties such as the interface location (that is, the slot in which the Flexible PIC Concentrator [FPC] or Dense Port Concentrator [DPC] is installed, and the location where the Physical Interface Card [PIC] is installed), the interface type (such as SONET/SDH, Asynchronous Transfer Mode [ATM], or Ethernet),...
Page 103: Permanent Interfaces Overview
J Series routers—For the Juniper Networks J Series Services Routers, you can use any of the built-in Ethernet ports as a management interface. To use a built-in interface as a management Ethernet interface, configure it with a valid IP address.
Page 104: Understanding Internal Ethernet Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide statement at the interface-name [edit system services web-management http] hierarchy level. For information about establishing basic connectivity and configuring a management port, see the Getting Started guide for your router. Permanent Interfaces Overview on page 33 Related Topics Understanding Internal Ethernet Interfaces Internal Ethernet interfaces on the router provide communication between the...
Page 105 Chapter 2: Understanding Router Interfaces If a TX Matrix Plus router contains redundant host subsystems, the independent control planes are connected by two physical links between the two 10-Gigabit Ethernet ports on their respective Routing Engines. The primary link to the remote Routing Engine is at the interface;...
Page 106: Understanding Transient Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Permanent Interfaces Overview on page 33 Related Topics Understanding Transient Interfaces The M Series, MX Series, and T Series routers contain slots for installing FPCs. PICs can be installed in FPCs. The number of PICs that can be installed varies by router and type of FPC.
Page 107 Chapter 2: Understanding Router Interfaces Monitoring Services PICs—Enable you to monitor traffic flow and export the monitored traffic. Monitoring traffic allows you to gather and export detailed information about IPv4 traffic flows between source and destination nodes in your network; sample all incoming IPv4 traffic on the monitoring interface and present the data in cflowd record format;...
Page 108: Container Interfaces Overview
JUNOS 10.1 Network Interfaces Configuration Guide Types of Interfaces Overview on page 32 Related Topics Container Interfaces Overview Container interfaces provide the following features: APS on SONET links are supported using container infrastructure. Container physical interfaces and logical interfaces remain up on switchover. APS parameters are auto-copied from the container interface to the member links.
Page 109 Chapter 2: Understanding Router Interfaces underlying logical interfaces, and brings down the working link and its underlying logical interfaces, causing the routing protocols to reconverge. This consumes time and leads to traffic loss even though the APS infrastructure has performed the switch quickly.
Page 110: Interface Encapsulations Overview
JUNOS 10.1 Network Interfaces Configuration Guide Configuring Container Interfaces on page 915. Related Topics Interface Encapsulations Overview Table 3 on page 40 lists encapsulation support by interface type. Table 3: Encapsulation Support by Interface Type Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —Aggregated Ethernet ethernet-ccc...
Page 111 Chapter 2: Understanding Router Interfaces Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —ATM2 intelligent —ATM cell relay encapsulation —ATM cell relay for CCC atm-ccc-cell-relay atm-ccc-cell-relay queuing (IQ) interface for a cross-connect —ATM VC for CCC atm-ccc-vc-mux atm-pvc...
Page 112 JUNOS 10.1 Network Interfaces Configuration Guide Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —DS0 interface —Cisco-compatible HDLC framing —Frame Relay DLCI for CCC cisco-hdlc frame-relay-ccc —Cisco-compatible HDLC framing —PPP over Frame Relay cisco-hdlc-ccc frame-relay-ppp for a cross-connect...
Page 113 Chapter 2: Understanding Router Interfaces Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —E1 interface (including —Cisco-compatible HDLC framing —Frame Relay DLCI for CCC cisco-hdlc frame-relay-ccc channelized STM1-to-E1 interfaces) —Cisco-compatible HDLC framing —PPP over Frame Relay cisco-hdlc-ccc frame-relay-ppp...
Page 114 JUNOS 10.1 Network Interfaces Configuration Guide Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —E3 interface (including —Cisco-compatible HDLC framing —Frame Relay DLCI for CCC cisco-hdlc frame-relay-ccc E3 IQ and IQE interfaces) —Cisco-compatible HDLC framing —PPP over Frame Relay cisco-hdlc-ccc...
Page 115 Chapter 2: Understanding Router Interfaces Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —Fast Ethernet interface —Ethernet cross-connect —Ethernet DIXv2 (RFC 894) ethernet-ccc —Ethernet translational —802.1Q tagging for a cross-connect ethernet-tcc vlan-ccc cross-connect —VLAN virtual private LAN service vlan-vpls...
Page 116 JUNOS 10.1 Network Interfaces Configuration Guide Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —Loopback interface; the JUNOS Software automatically configures one loopback interface —Link services interface multilink-frame-relay-uni-nni —Multilink Frame multilink-frame-relay-end-to-end —Multilink Frame Relay UNI NNI (FRF.16) encapsulation Relay end-to-end (FRF.15) —Multilink PPP...
Page 117 Chapter 2: Understanding Router Interfaces Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —Serial interface —Cisco-compatible HDLC framing —Frame Relay DLCI for CCC cisco-hdlc frame-relay-ccc (including EIA-530, V.35, and X.21 interfaces) —Cisco-compatible HDLC framing —PPP over Frame Relay cisco-hdlc-ccc frame-relay-ppp...
Page 118 JUNOS 10.1 Network Interfaces Configuration Guide Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —SONET/SDH interface —Cisco-compatible HDLC framing —Frame Relay DLCI for CCC cisco-hdlc frame-relay-ccc —Cisco-compatible HDLC framing —PPP over Frame Relay cisco-hdlc-ccc frame-relay-ppp for a cross-connect...
Page 119 Chapter 2: Understanding Router Interfaces Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —T1 interface (including —Cisco-compatible HDLC framing —Frame Relay DLCI for CCC cisco-hdlc frame-relay-ccc channelized DS3-to-DS1 interfaces) —Cisco-compatible HDLC framing —PPP over Frame Relay cisco-hdlc-ccc frame-relay-ppp...
Page 120 JUNOS 10.1 Network Interfaces Configuration Guide Table 3: Encapsulation Support by Interface Type (continued) Interface Type Physical Interface Encapsulation Logical Interface Encapsulation —T3 interface (including —Cisco-compatible HDLC framing —Frame Relay DLCI for CCC cisco-hdlc frame-relay-ccc channelized OC12-to-DS3 interfaces) —Cisco-compatible HDLC framing —PPP over Frame Relay cisco-hdlc-ccc frame-relay-ppp...
Page 121: Interface Descriptors Overview
Chapter 2: Understanding Router Interfaces Interface Descriptors Overview When you configure an interface, you are effectively specifying the properties for a physical interface descriptor. In most cases, the physical interface descriptor corresponds to a single physical device and consists of the following parts: The interface name, which defines the media type The slot in which the FPC or DPC is located The location on the FPC in which the PIC is installed...
Page 122: Interface Naming Overview
JUNOS 10.1 Network Interfaces Configuration Guide You configure the various interface descriptors as follows: You configure the physical interface descriptor by including the interfaces statement. interface-name You configure the logical interface descriptor by including the unit statement within the statement or by including the interfaces interface-name .logical descriptor at the end of the interface name, as in...
Page 123: Interface Naming For A Routing Matrix Based On A Tx Matrix Router
Chapter 2: Understanding Router Interfaces Interface Naming for a Routing Matrix Based on a TX Matrix Router on page 58 Interface Naming for a Routing Matrix Based on a TX Matrix Plus Router on page 60 Chassis Interface Naming on page 62 Examples: Interface Naming on page 63 Physical Part of an Interface Name The physical part of an interface name identifies the physical device, which...
Page 124 JUNOS 10.1 Network Interfaces Configuration Guide —Channelized STM1 IQ interface (configured on the Channelized STM1 cstm1 IQ or IQE PIC). cstm4 —Channelized STM4 IQ interface (configured on the Channelized OC12 IQ and IQE PICs). —Channelized STM16 IQ interface (configured on the Channelized cstm16 OC48/STM16 and Channelized OC48/STM16 IQE PICs).
Page 125 Chapter 2: Understanding Router Interfaces out-of-band management interface, and the internal Ethernet interface, fxp1 which connects the Routing Engine with the router s packet-forwarding components. If the router has redundant Routing Engines, another internal Ethernet interface, fxp2 , is created on each Routing Engine ( ) in order to support fault tolerance.
Page 126 JUNOS 10.1 Network Interfaces Configuration Guide —Internally generated interface that is not configurable. pime rlsq —Container interface, numbered from 0 through 127, used to tie the primary and secondary LSQ PICs together in high availability configurations. Any failure of the primary PIC results in a switch to the secondary PIC and vice versa. —Redudant interface for two MultiServices interfaces.
Page 127 Chapter 2: Understanding Router Interfaces numbering. For information about compatible FPCs and PICs, see the MX Series PIC Guide. For information about DPCs, see the MX Series DPC Guide. MX Series routers support Type 2 and Type 3 FPCs. On MX Series routers, the Type 2 and Type 3 FPCs support Type 2 and Type 3 SONET/SDH PICs, respectively.
Page 128 Interface Naming for a Routing Matrix Based on a TX Matrix Router A routing matrix based on a Juniper Networks TX Matrix Router is a multichassis architecture composed of one TX Matrix router and from one to four interconnected T640 routers.
Page 129: Figure 3: Routing Matrix
Chapter 2: Understanding Router Interfaces Figure 3: Routing Matrix (LCC 0) (LCC 1) T640 T640 TX Matrix (SCC) (LCC 2) (LCC 3) T640 T640 Data path Control path A TX Matrix router is also referred to as a switch-card chassis (SCC). The CLI uses to refer to the TX Matrix router.
Page 130: Table 4: Fpc Numbering For T640 Routers In A Routing Matrix
Interface Naming for a Routing Matrix Based on a TX Matrix Plus Router A routing matrix based on a Juniper Networks TX Matrix Plus Router is a multichassis architecture composed of one TX Matrix Plus router and from one to four interconnected T1600 routers.
Page 131: Figure 4: Routing Matrix Based On A Tx Matrix Plus Router
Chapter 2: Understanding Router Interfaces Figure 4: Routing Matrix Based on a TX Matrix Plus Router T1600 Router T1600 Router (LCC 0) (LCC 1) TX Matrix Plus Router (SFC) T1600 Router T1600 Router Node (LCC 2) (LCC 3) Data path Control path A TX Matrix Plus router is also referred to as a switch-fabric chassis (SFC).
Page 132: Table 6: Fpc Numbering For T1600 Routers In A Routing Matrix
JUNOS 10.1 Network Interfaces Configuration Guide Table 6 on page 62 summarizes the FPC numbering for a routing matrix based on a TX Matrix Plus router. Table 6: FPC Numbering for T1600 Routers in a Routing Matrix LCC Numbers Assigned to the T1600 Router Configuration Numbers 0 through 7...
Page 133 Chapter 2: Understanding Router Interfaces [edit chassis] fpc slot-number { pic pic-number { To configure PIC properties for a T640 or T1600 router configured in a routing matrix, you must specify the LCC, FPC, and PIC numbers, as follows: [edit chassis] lcc lcc-number { fpc slot-number { # Use the hardware FPC slot number pic pic-number {...
Page 134: Figure 5: Interface Slot, Pic, And Port Locations
JUNOS 10.1 Network Interfaces Configuration Guide Figure 5: Interface Slot, PIC, and Port Locations For an FPC in slot 1 with two OC3 SONET/SDH PICs in PIC positions 0 and 1, each PIC with two ports uses the following names: so-1/0/0.0 so-1/0/1.0 so-1/1/0.0...
Page 135: Displaying Interface Configurations Overview
Chapter 2: Understanding Router Interfaces at-1/1/0.0 at-1/2/0.0 at-1/3/0.0 In a routing matrix on the T640 router labeled lcc1 , for an FPC in slot 5 with four SONET OC192 PICs, the four PICs, each with a single port and a single logical unit, have the following names: so-13/0/0.0 so-13/1/0.0...
Page 136: Figure 6: Clock Sources
JUNOS 10.1 Network Interfaces Configuration Guide on interface A s received clock (external, loop timing) or the Stratum 3 clock (internal, line timing). Interface A cannot use a clock from any other source. By default, each interface uses the router s internal Stratum 3 clock. To configure the clock source of each interface, include the statement at the clocking...
Page 137 Chapter 2: Understanding Router Interfaces For more information about the external synchronization interface, see the JUNOS System Basics Configuration Guide. Router Interfaces Overview on page 32 Related Topics Interface and Router Clock Sources Overview...
Page 138 JUNOS 10.1 Network Interfaces Configuration Guide Interface and Router Clock Sources Overview...
Page 139: Configuring Physical Interface Properties
Chapter 3 Configuring Physical Interface Properties Physical Interface Configuration Statements Overview on page 70 Physical Interfaces Properties Statements List on page 79 Interface Ranges on page 95 Specifying an Aggregated Interface on page 104 Specifying a USB Modem Interface on J Series Routers on page 105 Specifying OC768-over-OC192 Mode on page 107 Adding an Interface Description to the Configuration on page 108 Configuring the Link Characteristics on page 109...
Page 140: Physical Interface Configuration Statements Overview
JUNOS 10.1 Network Interfaces Configuration Guide Physical Interface Configuration Statements Overview The software driver for each network media type sets reasonable default values for general interface properties, such as the interface s maximum transmission unit (MTU) size, receive and transmit leaky bucket properties, link operational mode, and clock source.
Page 141 Chapter 3: Configuring Physical Interface Properties low-plp-max-threshold percent; queue-depth cells high-plp-threshold percent low-plp-threshold percent; mpls { pop-all-labels { required-depth number; pic-type (atm1 | atm2); plp-to-clp; promiscuous-mode { vpi vpi-identifier; scheduler-maps map-name { forwarding-class class-name { epd-threshold cells plp1 cells; linear-red-profile profile-name; priority (high | low);...
Page 142 JUNOS 10.1 Network Interfaces Configuration Guide dsr-polarity (negative | positive); dte-options { control-signal (assert | de-assert | normal); cts (ignore | normal | require); dcd (ignore | normal | require); dsr (ignore | normal | require); dtr signal-handling-option; ignore-all; indication (ignore | normal | require); rts (assert | de-assert | normal);...
Page 143 Chapter 3: Configuring Physical Interface Properties fcs (16 | 32); framing (g.751 | g.832); idle-cycle-flag (filler | shared); invert-data; loopback (local | remote); (payload-scrambler | no-payload-scrambler); start-end-flag (filler | shared); (unframed | no-unframed); encapsulation type; es-options { backup-interface es-fpc/pic/port; fastether-options { 802.3ad aex;...
Page 144 JUNOS 10.1 Network Interfaces Configuration Guide classifier { premium { forwarding-class class-name { loss-priority (high | low); policer cos-policer-name { aggregate { bandwidth-limit bps; burst-size-limit bytes; premium { bandwidth-limit bps; burst-size-limit bytes; (gratuitous-arp-reply | no-gratuitous-arp-reply); hold-time up milliseconds down milliseconds; interface-set interface-set-name { interface ethernet-interface-name { (unit unit-number | vlan-tags-outer vlan-tag);...
Page 145 Chapter 3: Configuring Physical Interface Properties mlfr-uni-nni-bundle-options { acknowledge-retries number; acknowledge-timer milliseconds; action-red-differential-delay (disable-tx | remove-link); cisco-interoperability send-lip-remove-link-for-link-reject; drop-timeout milliseconds; fragment-threshold bytes; hello-timer milliseconds; link-layer-overhead percent; lmi-type (ansi | itu); minimum-links number; mrru bytes; n391 number; n392 number; n393 number; red-differential-delay milliseconds;...
Page 146 JUNOS 10.1 Network Interfaces Configuration Guide compression { acfc; pfc; dynamic-profile profile-name; no-termination-request; pap { access-profile name; local-name name; local-password password; passive; receive-bucket { overflow (discard | tag); rate percentage; threshold bytes; redundancy-options { primary sp-fpc/pic/port; secondary sp-fpc/pic/port; schedulers number; serial-options { clock-rate rate;...
Page 147 Chapter 3: Configuring Physical Interface Properties indication-polarity (negative | positive); line-protocol protocol; loopbackmode; rts-polarity (negative | positive); tm-polarity (negative | positive); transmit-clock invert; services-options { inactivity-timeout seconds; open-timeout seconds; syslog { host hostname { facility-override facility-name; log-prefix prefix-number; services priority-level; shdsl-options { annex (annex-a | annex-b);...
Page 148 JUNOS 10.1 Network Interfaces Configuration Guide pop-all-labels { required-depth number; path-trace trace-string; (payload-scrambler | no-payload-scrambler); rfc-2615; trigger { defect ignore; hold-time up milliseconds down milliseconds; vtmapping (itu-t | klm); (z0-increment | no-z0-increment); (speed (10m | 100m | 1g | auto) | speed (auto | 1Gbps | 100Mbps | 10Mbps) | speed (oc3 | oc12 | oc48));...
Page 149: Physical Interfaces Properties Statements List
Chapter 3: Configuring Physical Interface Properties loopback (local | payload | remote); (mac | no-mac); (payload-scrambler | no-payload-scrambler); start-end-flag (filler | shared); traceoptions { flag flag <flag-modifier> <disable>; transmit-bucket { overflow discard; rate percentage; threshold bytes; (traps | no-traps); unidirectional; vlan-tagging;...
Page 150 JUNOS 10.1 Network Interfaces Configuration Guide Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines action-red-differential-delay Link services and voice services interfaces JUNOS Services Interfaces Configuration Guide (disable-tx | remove-link) advertise-interval milliseconds SONET/SDH interfaces “Configuring APS and MSP” on page 911 Gigabit Ethernet intelligent queuing (IQ “Configuring Gigabit Ethernet Policers”...
Page 151 Chapter 3: Configuring Physical Interface Properties Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines bchannel-allocation (ascending | J Series routers equipped with a Dual-Port “Allocating B-Channels for Dialout” on Channelized T1/E1 PIM; for Integrated page 523 descending) Services Digital Network Primary Rate Interfaces (ISDN PRI)
Page 152 JUNOS 10.1 Network Interfaces Configuration Guide Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines clocking clock-source ATM, DS0, E1, E3, SONET/SDH, T1, and “Configuring the Clock Source” on page 140 T3 interfaces Serial interfaces (EIA-530 and V.35) “Configuring the Serial Clocking Mode”...
Page 153 Chapter 3: Configuring Physical Interface Properties Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines disable “Disabling a Physical Interface” on page 152 and “Tracing Operations of an Individual Router Interface” on page 149 802.1x Port-Based Network Access Control “IEEE 802.1x Port-Based Network Access dot1x Control Overview”...
Page 154 JUNOS 10.1 Network Interfaces Configuration Guide Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines ethernet-policer-profile Gigabit Ethernet and Gigabit Ethernet IQ “Configuring Gigabit Ethernet Policers” on and IQE PICs with SFPs (except the page 787 10-port Gigabit Ethernet PIC, and the built-in Gigabit Ethernet port on the M7i router)
Page 155 Chapter 3: Configuring Physical Interface Properties Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines gigether-options Gigabit Ethernet and Tri-Rate Ethernet “Ethernet Interfaces Overview” on copper interfaces page 603 Ethernet interfaces “Configuring Gratuitous ARP” on page 614 (gratuitous-arp-reply | no-gratuitous-arp-reply) Link services and voice services interfaces...
Page 156 JUNOS 10.1 Network Interfaces Configuration Guide Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines init-command-string For USB ports ( ) on J4350 and J6350 “Specifying a USB Modem Interface on J umd0 Series Routers” on page 105 initialization-command-string;...
Page 157 Chapter 3: Configuring Physical Interface Properties Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines lmi lmi-options Interfaces with Frame Relay encapsulation “Configuring Tunable Keepalives for Frame Relay LMI” on page 386 and JUNOS Services Interfaces Configuration Guide OAM CFM Ethernet Local Management “Configuring Ethernet Local Management Interface...
Page 158 JUNOS 10.1 Network Interfaces Configuration Guide Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines low-plp-threshold percent ATM2 interfaces “Configuring ATM2 IQ VC Tunnel CoS Components” on page 347 Link services IQ (lsq) interfaces JUNOS Services Interfaces Configuration lsq-failure-options Guide “Configuring the MAC Address on the...
Page 159 Chapter 3: Configuring Physical Interface Properties Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines n391 number Link services and voice services interfaces JUNOS Services Interfaces Configuration Guide Link services and voice services interfaces JUNOS Services Interfaces Configuration n392 number Guide Link services and voice services interfaces...
Page 160 JUNOS 10.1 Network Interfaces Configuration Guide Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines passive Interfaces with PPP encapsulation “Configuring the PPP Challenge Handshake Authentication Protocol” on page 124 SONET/SDH interfaces “Enabling Passive Monitoring on passive-monitor-mode SONET/SDH Interfaces”...
Page 161 Chapter 3: Configuring Physical Interface Properties Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines premium Gigabit Ethernet IQ interfaces (policer) “Configuring Gigabit Ethernet Policers” on page 787 Gigabit Ethernet IQ interfaces (output “Configuring MAC Address Filtering” on premium priority map) page 791...
Page 162 JUNOS 10.1 Network Interfaces Configuration Guide Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines rfc-2615 SONET/SDH interfaces “Configuring SONET/SDH RFC 2615 Support” on page 907 Serial interfaces (EIA-530 and V.35) “Configuring the Serial Signal Handling” rts (assert | de-assert | normal) on page 278 Serial interfaces (EIA-530 and V.35)
Page 163 Chapter 3: Configuring Physical Interface Properties Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines (source-filtering | Aggregated Ethernet, Fast Ethernet, “Enabling Ethernet MAC Address Filtering” Tri-Rate Ethernet copper, Gigabit Ethernet, on page 610 no-source-filtering) Gigabit Ethernet IQ and IQE, and Gigabit Ethernet interfaces with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i...
Page 164 JUNOS 10.1 Network Interfaces Configuration Guide Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines threshold bytes All interfaces, except ATM, channelized “Configuring Receive and Transmit Leaky E1, E1, Fast Ethernet, Gigabit Ethernet, Bucket Properties” on page 141 and and channelized IQ “Configuring Receive and Transmit Leaky Bucket Properties on SONET/SDH...
Page 165: Interface Ranges
Chapter 3: Configuring Physical Interface Properties Table 8: Statements for Physical Interface Properties (continued) Statement Interface Types Usage Guidelines vlan-tagging Fast Ethernet, Tri-Rate Ethernet copper, “802.1Q VLANs Overview” on page 619 and Gigabit Ethernet interfaces Fast Ethernet, Tri-Rate Ethernet copper, “Configuring ATM-to-Ethernet vlan-vci-tagging Gigabit Ethernet, 10-Gigabit Ethernet, and...
Page 166 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Interface Ranges To configure an interface range, include the statement at the interface-range [edit interfaces] hierarchy level. statement accepts only physical networking interface names in interface-range its definition. The following interface types are supported and example CLI descriptors are shown: Ethernet—...
Page 167 Chapter 3: Configuring Physical Interface Properties To specify the list of interface range members individually or for multiple interfaces using regex, use the statement. member list of interface names member ge-0/0/0; Example: Specifying an member ge-0/*/* Interface Range Member member ge-0/[1-10]/0; member ge-0/[1,2,3]/3;...
Page 168 JUNOS 10.1 Network Interfaces Configuration Guide should be an defined at the hierarchy level. In the interface-range [interfaces] above example, the interface node can accept both individual interfaces and interface ranges. TIP: To view an interface range in expanded configuration, use the (show | display command.
Page 169 Chapter 3: Configuring Physical Interface Properties protocols stp interface protocols rstp interface protocols mstp interface protocols vstp interface protocols mstp msti id interface protocols mstp msti vlan id interface protocols vstp vlan name interface protocols gvrp interface protocols igmp-snooping vlan name interface protocols lldp interface protocols lldp-med interface protocols sflow interfaces...
Page 170 JUNOS 10.1 Network Interfaces Configuration Guide For the statement, all possible interfaces between member-range start-range end-range are considered in expanding the members. For example, the following statement: member-range member-range ge-0/0/0 to ge-4/0/20 expands to: [ge-0/0/0, ge-0/0/1 ... ge-0/0/max_ports ge-0/1/0 ge-0/1/1 ... ge-0/1/max_ports ge-0/2/0 ge-0/2/1 ...
Page 171: Groups
Chapter 3: Configuring Physical Interface Properties member-range ge-1/0/0/ to ge-10/0/47; mtu 256; ge-1/0/1 { mtu 1024; In the preceding example, interface will have an MTU value of 1024. ge-1/0/1 This can be verified with output of the show interfaces | display inheritance command, as follows: user@host: # show interfaces | display inheritance...
Page 172: Interfaces Inheriting Common Configuration
JUNOS 10.1 Network Interfaces Configuration Guide hold-time up 10; apply-groups [global]; interfaces { interface-range foo { member-range ge-1/0/0 to ge-10/0/47; mtu 256; configuration is applied to all members of hold-time interface-range foo This can be verified with as below: show interfaces | display inheritance user@host# show interfaces | display inheritance ge-1/0/0 { ## '256' was expanded from interface-range 'foo'...
Page 173: Configuring Inheritance Range Priorities
Chapter 3: Configuring Physical Interface Properties interface-range foo { member-range ge-1/0/0 to ge-10/0/47; mtu 256; interfaces { interface-range zoo { member-range ge-10/0/0 to ge-10/0/47; hold-time up 10; In this example, interfaces through will have both ge-10/0/0 ge-10/0/47 hold-time Configuring Inheritance Range Priorities The interface ranges are defined in the order of inheritance priority, with the first interface range configuration data taking priority over subsequent interface ranges.
Page 174: Specifying An Aggregated Interface
JUNOS 10.1 Network Interfaces Configuration Guide speed { 100m; 802.3ad primary; protocols { dot1x { authenticator { interface foo{ retries 1; interface node present under authenticator is expanded into member interfaces of the as follows: interface-range foo protocols { dot1x { authenticator { interface ge-10/1/1 { retries 1;...
Page 175: Specifying A Usb Modem Interface On J Series Routers
Chapter 3: Configuring Physical Interface Properties The maximum number of aggregated Ethernet interfaces is 128, and the assigned number can be from 0 through 127. The maximum number of aggregated Ethernet interfaces (LAG bundles) on all MX Series routers is 480, and the assigned number can be from 0 through 479.
Page 176 JUNOS 10.1 Network Interfaces Configuration Guide pool pool-name <priority priority>; modem-options { dialin (console | routable); init-command-string initialization-command-string; The pool name specified at the [edit interfaces umd0 dialer-options pool] hierarchy level must be the same as the pool name specified at the [edit interfaces dln unit logical-unit-number dialer-options pool] hierarchy level.
Page 177: Specifying Oc768-Over-Oc192 Mode
Chapter 3: Configuring Physical Interface Properties For more information about configuring dial-in, see “Configuring Dial-In and Callback” on page 884. Specifying OC768-over-OC192 Mode The T Series routers support OC768-over-OC192 mode on the 4-port OC192c PIC. In OC768-over-OC192 mode, four OC192 links are aggregated into one OC768 link with one logical interface.
Page 178: Adding An Interface Description To The Configuration
JUNOS 10.1 Network Interfaces Configuration Guide When you configure the 4-port OC192 PIC for OC768-over-OC192 mode, only port 0 (the first port) needs be configured as the OC768 port. To display logical and physical interface information, use the operational mode command .
Page 179: Configuring The Link Characteristics
Chapter 3: Configuring Physical Interface Properties Physical interface: fe-0/0/1, Enabled, Physical link is Up Interface index: 129, SNMP ifIndex: 23 Description: Backbone connection to PHL01 To display the interface description from the interfaces MIB, use the snmpwalk command from a server. To isolate information for a specific interface, search for the interface index shown in the field of the command...
Page 180: Table 9: Media Mtu Sizes By Interface Type For M5, M7I With Cfeb, M10, M10I With Cfeb, M20, And M40 Routers
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces interface-name] link-mode (full-duplex | half-duplex); Configuring the Media MTU The default media MTU size used on a physical interface depends on the encapsulation used on that interface. In some cases, the default IP Protocol MTU depends on whether the protocol used is IP version 4 (IPv4) or International Organization for Standardization (ISO).
Page 181: Table 11: Media Mtu Sizes By Interface Type For M160 Routers
Chapter 3: Configuring Physical Interface Properties Table 10: Media MTU Sizes by Interface Type for M40e Routers (continued) Default Media Default IP Protocol Interface Type MTU (Bytes) Maximum MTU (Bytes) MTU (Bytes) E3/T3 4474 4500 4470 9192 (4-port) E3/DS3 IQ 4474 9192 4470...
Page 182: Table 12: Media Mtu Sizes By Interface Type For M7I With Cfeb-E, M10I With Cfeb-E, M320 And M120 Routers
JUNOS 10.1 Network Interfaces Configuration Guide Table 11: Media MTU Sizes by Interface Type for M160 Routers (continued) Default Media Default IP Protocol Interface Type MTU (Bytes) Maximum MTU (Bytes) MTU (Bytes) E1/T1 1504 4500 1500 E3/T3 4474 4500 4470 E3/DS3 IQ 4474 9192...
Page 183: Table 13: Media Mtu Sizes By Interface Type For T320 Routers
Chapter 3: Configuring Physical Interface Properties Table 12: Media MTU Sizes by Interface Type for M7i with CFEB-E, M10i with CFEB-E, M320 and M120 Routers (continued) Default Media Maximum MTU Default IP Protocol Interface Type MTU (Bytes) (Bytes) MTU (Bytes) 1504 4500 1500...
Page 184: Table 16: Media Mtu Sizes By Interface Type For J4300 And J6300 Platforms
JUNOS 10.1 Network Interfaces Configuration Guide Table 15: Media MTU Sizes by Interface Type for J2300 Platforms (continued) Default Media Maximum MTU Default IP Protocol Interface Type MTU (Bytes) (Bytes) MTU (Bytes) G.SHDSL 4482 9150 4470 ISDN BRI 1504 4092 1500 Serial 1504...
Page 185 Chapter 3: Configuring Physical Interface Properties Table 17: Media MTU Sizes by Interface Type for J4350 and J6350 Platforms (continued) Default Media Maximum MTU Default IP Protocol Interface Type MTU (Bytes) (Bytes) MTU (Bytes) Dual-port Fast 1514 9192 1500 Ethernet (10/100) PIM Dual-port Serial PIM 1504 9150...
Page 186: Table 18: Encapsulation Overhead By Encapsulation Type
JUNOS 10.1 Network Interfaces Configuration Guide NOTE: On Gigabit Ethernet ePIMs in J4350 and J6350 Services Routers, you can configure a maximum transmission unit (MTU) size of only 9018 bytes even though the CLI indicates that you can configure an MTU of up to 9192 bytes. If you configure an MTU greater than 9018 bytes, the router does not accept the configuration and generates a system log error message similar to the following: /kernel: ge-0/0/0: Illegal media change.
Page 187 Chapter 3: Configuring Physical Interface Properties Table 18: Encapsulation Overhead by Encapsulation Type (continued) Interface Encapsulation Encapsulation Overhead (Bytes) VLAN CCC VLAN VPLS VLAN TCC The default media MTU is calculated as follows: Default media MTU = Default IP MTU + encapsulation overhead When you are configuring point-to-point connections, the MTU sizes on both sides of the connections must be the same.
Page 188: Configuring Interface Encapsulation On Physical Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces interface-name] mtu bytes; If you change the size of the media MTU, you must ensure that the size is equal to or greater than the sum of the protocol MTU and the encapsulation overhead. NOTE: Changing the media MTU or protocol MTU causes an interface to be deleted and added again.
Page 189 Chapter 3: Configuring Physical Interface Properties encapsulation (atm-ccc-cell-relay | atm-pvc | cisco-hdlc | cisco-hdlc-ccc | cisco-hdlc-tcc | ethernet-ccc | ethernet-over-atm | ethernet-tcc | ethernet-vpls | extended-frame-relay-ccc | extended-frame-relay-ether-type-tcc | extended-frame-relay-tcc | extended-vlan-ccc | extended-vlan-tcc | extended-vlan-vpls | flexible-ethernet-services | flexible-frame-relay | frame-relay | frame-relay-ccc | frame-relay-ether-type | frame-relay-ether-type-tcc | frame-relay-port-ccc | frame-relay-tcc | multilink-frame-relay-uni-nni | ppp | ppp-ccc | ppp-tcc | vlan-ccc | vlan-vpls);...
Page 190 JUNOS 10.1 Network Interfaces Configuration Guide address match, the packet is encapsulated with an LLC/SNAP and media access control (MAC) header, and the packet is forwarded to the ATM interface. Ethernet cross-connect—Ethernet interfaces without VLAN tagging can use Ethernet CCC encapsulation. Two related versions are supported: CCC version ( )—Ethernet interfaces with standard Tag Protocol ethernet-ccc...
Page 191 Chapter 3: Configuring Physical Interface Properties Ethernet services encapsulation on the physical interface, VLAN IDs from 1 through 511 are no longer reserved for normal VLANs. Flexible Frame Relay ( )—IQ and IQE interfaces can use flexible flexible-frame-relay Frame Relay encapsulation. You use flexible Frame Relay encapsulation when you want to configure multiple per-unit Frame Relay encapsulations.
Page 192: Encapsulation Capabilities
JUNOS 10.1 Network Interfaces Configuration Guide Extended TCC version ( )—This encapsulation extended-frame-relay-ether-type-tcc allows you to dedicate Cisco-compatible Frame Relay TCC for DLCIs 1 through 1022. This encapsulation is used for circuits with different media on either side of the connection. Multilink Frame Relay (MLFR) UNI and NNI ( multilink-frame-relay-uni-nni )—Link...
Page 193: Example: Configuring The Encapsulation On A Physical Interface
Chapter 3: Configuring Physical Interface Properties on the physical interface. For interfaces with flexible-ethernet-services encapsulation, all VLAN IDs are valid. VLAN IDs from 1 through 511 are not reserved. For encapsulation types extended-vlan-ccc extended-vlan-vpls , all VLAN IDs are valid. The upper limits for configurable VLAN IDs vary by interface type.
Page 194: Configuring The Ppp Challenge Handshake Authentication Protocol
JUNOS 10.1 Network Interfaces Configuration Guide family mpls; Configuring the PPP Challenge Handshake Authentication Protocol For interfaces with PPP encapsulation, you can configure interfaces to support the PPP Challenge Handshake Authentication Protocol (CHAP), as defined in RFC 1994, PPP Challenge Handshake Authentication Protocol (CHAP). When you enable CHAP on an interface, the interface can authenticate its peer and can be authenticated by its peer.
Page 195: Configuring The Local Name
Chapter 3: Configuring Physical Interface Properties Configuring the Local Name on page 125 Configuring Passive Mode on page 126 Example: Configuring the PPP Challenge Handshake Authentication Protocol on page 126 When you configure PPP over ATM or Multilink PPP over ATM encapsulation, you can enable CHAP on the logical interface.
Page 196: Configuring The Ppp Password Authentication Protocol
JUNOS 10.1 Network Interfaces Configuration Guide Configuring Passive Mode By default, when CHAP is enabled on an interface, the interface always challenges its peer and responds to challenges from its peer. You can configure the interface not to challenge its peer, and only respond when challenged.
Page 197 Chapter 3: Configuring Physical Interface Properties 2 seconds, similar to the CHAP challenge, until a response is received (acknowledgment packet, nonacknowledgment packet). If an acknowledgment packet is received, the PPP link transitions to the next state, the network phase. If a nonacknowledgment packet is received, an LCP terminate request is sent, and the PPP link goes back to the link establishment phase.
Page 198: Configuring The Local Name
JUNOS 10.1 Network Interfaces Configuration Guide To configure PPP PAP on a logical interface with PPP encapsulation, include the statement with options: pap { default-pap-password password; local-name name; local-password password; passive; You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]...
Page 199: Configuring Passive Mode
Chapter 3: Configuring Physical Interface Properties Configuring Passive Mode By default, when PAP is enabled on an interface, the interface expects authenticate-request packets from the peer. However, the interface can be configured to send authentication request packets to the peer by configuring PAP to operate in passive mode.
Page 200: Monitoring A Ppp Session
JUNOS 10.1 Network Interfaces Configuration Guide boston { pap-password "#%@^***"; # SECRET-DATA; Configure the physical interface, including the access profile name to be used for PPP authentication: [edit interfaces so-0/0/0] ppp-options { pap { access-profile “pap-profile”; local-name "rtrnum1"; local-password "XXXXXXX"; #SECRET-DATA passive;...
Page 201: Tracing Operations Of The Pppd Process
Chapter 3: Configuring Physical Interface Properties To configure PPP packet monitoring, include the statement at the monitor-session [edit protocols ppp] hierarchy level: [edit protocols ppp] monitor-session (interface-name | all); When monitoring is configured, the operational mode commands show ppp summary show ppp interface display a Monitored...
Page 202: Configuring Ppp Address And Control Field Compression
JUNOS 10.1 Network Interfaces Configuration Guide —Timer code timer —User interface code For general information about tracing, see the tracing and logging information in the JUNOS System Basics Configuration Guide. Configuring PPP Address and Control Field Compression For interfaces with PPP, PPP CCC, or PPP TCC encapsulation, you can configure compression of the Data Link Layer address and control fields, as defined in RFC 1661, The Point-to-Point Protocol (PPP).
Page 203: Configuring The Ppp Protocol Field Compression
Chapter 3: Configuring Physical Interface Properties user@router# run show interfaces so-0/1/1 Physical interface: so-0/1/1, Enabled, Physical link is Up Interface index: 133, SNMP ifIndex: 27 Link-level type: PPP, MTU: 4474, Clocking: Internal, SONET mode, Speed: OC3, Loopback: None, FCS: 16 Payload scrambler: Enabled Device flags : Present Running...
Page 204: Configuring The Interface Speed
JUNOS 10.1 Network Interfaces Configuration Guide local router can receive packets with compression. If the peer indicates that it, too, can receive packets with compression, then PFC is negotiated. If PFC is successfully negotiated, the local router can receive packets with either 2-byte (uncompressed) or 1-byte (compressed) protocol fields.
Page 205 Chapter 3: Configuring Physical Interface Properties statement in the configuration hierarchy, as described no-concatenate [edit chassis] in the JUNOS System Basics Configuration Guide). NOTE: For M Series, MX Series, and most T Series routers, the management Ethernet interface is fxp0 .
Page 206 JUNOS 10.1 Network Interfaces Configuration Guide in multiplexed mode (using the statement at the hierarchy no-concatenate [edit chassis] level, as described in the JUNOS System Basics Configuration Guide). If the link partner does not support autonegotiation, configure either Fast Ethernet port manually to match its link partner's speed and link mode.
Page 207: Table 19: Type 1 Pic Mode Combinations
Chapter 3: Configuring Physical Interface Properties bandwidth of the interface is in a single channel. In nonconcatenated mode, the PIC operates in channelized (multiplexed) mode. Table 19 on page 137 shows the mode combinations for the next-generation SONET/SDH Type 1 PICs with SFP. Table 19: Type 1 PIC Mode Combinations Mode Speed Configuration...
Page 208: Configuring Keepalives
JUNOS 10.1 Network Interfaces Configuration Guide Table 20: Type 2 PIC Mode Combinations (continued) Mode Speed Configuration Default Mode 4-port OC3, IQ 1xOC12 concatenated fpc/pic/0 speed oc12 — and IQE 1xOC12 nonconcatenated nonconcatenated fpc/pic/0:0 speed oc3 4xOC3 concatenated fpc/pic/port speed oc3 concatenated By default, SONET/SDH PICs operate in concatenated mode.
Page 209 Chapter 3: Configuring Physical Interface Properties statement at the hierarchy level along with the [edit interfaces interface-name] encapsulation cisco-hdlc-tcc statement: [edit interfaces interface-name] encapsulation cisco-hdlc-tcc; no-keepalives; For more information about translation cross-connections, see “Circuit and Translational Cross-Connects Overview” on page 229. When you configure PPP over ATM or Multilink PPP over ATM encapsulation, you can enable or disable keepalives on the logical interface.
Page 210: Configuring The Clock Source
JUNOS 10.1 Network Interfaces Configuration Guide Configuring the Clock Source For both the router and interfaces, the clock source can be the router s internal Stratum 3 clock, which resides on the System Control Board (SCB), the System and Switch Board (SSB), the Forwarding Engine Board (FEB), or the Miscellaneous Control Subsystem (MCS) (depending on the router model), or an external clock that is received on the interface.
Page 211: Configuring Receive And Transmit Leaky Bucket Properties
Chapter 3: Configuring Physical Interface Properties Configuring Receive and Transmit Leaky Bucket Properties Congestion control is particularly difficult in high-speed networks with high volumes of traffic. When congestion occurs in such a network, it is usually too late to react. You can avoid congestion by regulating the flow of packets into your network.
Page 212: Configuring Accounting For The Physical Interface
Configuring Accounting for the Physical Interface Juniper Networks routers can collect various kinds of data about traffic passing through the router. You can set up one or more accounting profiles that specify some common characteristics of this data, including the following:...
Page 213: Example: Applying An Accounting Profile To The Physical Interface
Chapter 3: Configuring Physical Interface Properties Example: Applying an Accounting Profile to the Physical Interface Configure an accounting profile for an interface and apply it to a physical interface: [edit] accounting-options { file if_stats { size 4m files 10 transfer-interval 15; archive-sites { "ftp://login:password@host/path";...
Page 214: Table 21: Loopback Modes By Interface Type
JUNOS 10.1 Network Interfaces Configuration Guide To do this, configure a line loopback on one of the routers. Instead of transmitting the signal toward the far-end device, the line loopback sends the signal back to the originating router. If the originating router receives back its own data link layer packets, you have verified that the problem is beyond the originating router.
Page 215 Chapter 3: Configuring Physical Interface Properties Table 21: Loopback Modes by Interface Type (continued) Interface Loopback Modes Usage Guidelines Circuit Emulation T1 Local and remote “Configuring T1 Loopback Capability” on page 583 E1 and E3 Local and remote “Configuring E1 Loopback Capability” on page 564 and “Configuring E3 Loopback Capability”...
Page 216: Interface Diagnostics
JUNOS 10.1 Network Interfaces Configuration Guide Interface Diagnostics BERT allows you to troubleshoot problems by checking the quality of links. You can configure any of the following interfaces to execute a BERT when the interface receives a request to run this test: E1, E3, T1, T3; the channelized DS3, OC3, OC12, and STM1 interfaces;...
Page 217 Chapter 3: Configuring Physical Interface Properties NOTE: The 4-port E1 PIC supports only the following algorithms: pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 standard) pseudo-2e15-o151 Pattern is 2^15 - 1 (per O.151 standard) pseudo-2e20-o151 Pattern is 2^20 - 1 (per O.151 standard) pseudo-2e23-o151 Pattern is 2^23 (per O.151 standard) When you issue the...
Page 218: Starting And Stopping A Bert Test
JUNOS 10.1 Network Interfaces Configuration Guide Table 22 on page 148 shows the BERT capabilities for various interface types. Table 22: BERT Capabilities by Interface Type Interface T1 BERT T3 BERT Comments 12-port T1/E1 Yes (ports 0–11) Limited algorithms Circuit Emulation 4-port Yes (port 0–3) Limited algorithms...
Page 219: Example: Configuring Bit Error Rate Testing
Chapter 3: Configuring Physical Interface Properties The test runs for the duration you specify with the statement. If you wish bert-period to terminate the test sooner, issue the test interface interface-name command: interface-type-bert-stop user@host> test interface interface-name interface-type-bert-stop For example: user@host>...
Page 220: Damping Interface Transitions
JUNOS 10.1 Network Interfaces Configuration Guide You can specify the following interface tracing flags: —Trace all interface operations. event —Trace all interface events. —Trace all interface interprocess communication (IPC) messages. —Trace all interface media changes. media The interfaces statement does not support a trace file. The logging is traceoptions done by the kernel, so the tracing information is placed in the system syslog...
Page 221: Enabling Or Disabling Snmp Notifications On Physical Interfaces
Chapter 3: Configuring Physical Interface Properties To configure multiservice physical interface properties on the collector, monitoring services, and AS interfaces, include the statement: multiservice-options multiservice-options { (core-dump | no-core-dump); (syslog | no-syslog); You can include these statements at the following hierarchy levels: [edit interfaces cp-fpc/pic/port] [edit interfaces mo-fpc/pic/port] [edit interfaces sp-fpc/pic/port]...
Page 222: Disabling A Physical Interface
JUNOS 10.1 Network Interfaces Configuration Guide To enable unidirectional link mode on a physical interface, include the unidirectional statement at the [edit interfaces interface-name] hierarchy level: [edit interfaces interface-name] unidirectional; NOTE: Unidirectional link mode is currently supported on only the following hardware: 4–Port 10–Gigabit Ethernet DPC on the MX960 router 10–Gigabit Ethernet IQ2 PIC and 10–Gigabit Ethernet IQ2E PIC on the T Series router...
Page 223: Example: Disabling A Physical Interface
Chapter 3: Configuring Physical Interface Properties WARNING: Do not stare into the laser beam or view it directly with optical instruments even if the interface has been disabled. Example: Disabling a Physical Interface Disable a physical interface: [edit interfaces] so-1/1/0 { mtu 8000;...
Page 224 JUNOS 10.1 Network Interfaces Configuration Guide Disabling a Physical Interface...
Page 225: Chapter 4 Configuring Logical Interface Properties
Chapter 4 Configuring Logical Interface Properties Logical Interfaces Configuration Properties Overview on page 155 Logical Interfaces Configuration Statements on page 156 Logical Interfaces Statements List on page 159 Specifying the Logical Interface Number on page 166 Configuring Logical System Interface Properties on page 166 Adding a Logical Unit Description to the Configuration on page 168 Configuring a Point-to-Point Connection on page 168 Configuring a Multipoint Connection on page 169...
Page 226 JUNOS 10.1 Network Interfaces Configuration Guide Logical Interfaces Configuration Statements To configure logical interface properties, include the following statements: unit logical-unit-number { accept-source-mac { mac-address mac-address { policer { input cos-policer-name; output cos-policer-name; accounting-profile name; allow-any-vci; atm-scheduler-map (map-name | default); backup-options { interface interface-name;...
Page 227: Configuring Logical Interface Properties
Chapter 4: Configuring Logical Interface Properties load-interval seconds; load-threshold number; pool pool-name; redial-delay time; watch-list { [ routes ]; disable; disable-mlppp-inner-ppp-pfc; dlci dlci-identifier; drop-timeout milliseconds; dynamic-call-admission-control { activation-priority priority; bearer-bandwidth-limit kilobits-per-second; encapsulation type; epd-threshold plp1 cells; filter filter-name; fragment-threshold bytes; inner-vlan-id-range start start-id end end-id;...
Page 228 JUNOS 10.1 Network Interfaces Configuration Guide passive-monitor-mode; peer-unit unit-number; plp-to-clp; point-to-point; ppp-options { chap { access-profile name; default-chap-secret name; local-name name; passive; compression { acfc; pfc; dynamic-profile profile-name; lcp-restart-timer milliseconds; loopback-clear-timer seconds; ncp-restart-timer milliseconds; pap { default-pap-password password; local-name name; local-password password;...
Page 229: Logical Interfaces Statements List
Chapter 4: Configuring Logical Interface Properties vpi vpi-identifier; vlan-id number; vlan-id-range number-number; vlan-tags inner tpid.vlan-id outer tpid.vlan-id; family family { [ family-statements ]; You can include these statements at the following hierarchy levels: [edit interfaces interface-name] [edit logical-systems logical-system-name interfaces interface-name] For information about interface-specific logical properties, see Table 23 on page 159.
Page 230 JUNOS 10.1 Network Interfaces Configuration Guide Table 23: Statements for Logical Interface Properties (continued) Statement Interface Types Usage Guidelines backup-options J Series routers ISDN interfaces “Configuring an ISDN Dialer Interface as a Backup Interface” on page 878 All interfaces, except multilink and “Configuring the Interface Bandwidth”...
Page 231 Chapter 4: Configuring Logical Interface Properties Table 23: Statements for Logical Interface Properties (continued) Statement Interface Types Usage Guidelines disable-mlppp-inner-ppp-pfc MLPPP interfaces JUNOS Services Interfaces Configuration Guide Point-to-point interfaces with Frame Relay “Configuring Frame Relay DLCIs” on dlci dlci-identifier encapsulation page 388 Multilink interfaces JUNOS Services Interfaces Configuration...
Page 232 JUNOS 10.1 Network Interfaces Configuration Guide Table 23: Statements for Logical Interface Properties (continued) Statement Interface Types Usage Guidelines input AS PIC or MultiServices link services JUNOS Services Interfaces Configuration Guide For 1-Gigabit Ethernet and 10-Gigabit JUNOS Services Interfaces Configuration input-policer policer-name Ethernet IQ2 and IQ2-E interfaces on M Guide and “Applying a Policer”...
Page 233 Chapter 4: Configuring Logical Interface Properties Table 23: Statements for Logical Interface Properties (continued) Statement Interface Types Usage Guidelines minimum-links number Multilink interfaces JUNOS Services Interfaces Configuration Guide Multilink interfaces JUNOS Services Interfaces Configuration mrru bytes Guide Point-to-multipoint Frame Relay interfaces “Configuring a Multicast-Capable Frame multicast-dlci dlci-identifier Relay Connection”...
Page 234 JUNOS 10.1 Network Interfaces Configuration Guide Table 23: Statements for Logical Interface Properties (continued) Statement Interface Types Usage Guidelines plp1 cells ATM2 IQ interfaces “Configuring the ATM2 IQ EPD Threshold” on page 334 ATM2 IQ interfaces “Enabling the PLP Setting to Be Copied to plp-to-clp the CLP Bit”...
Page 235 Chapter 4: Configuring Logical Interface Properties Table 23: Statements for Logical Interface Properties (continued) Statement Interface Types Usage Guidelines service-domain (inside | outside) Adaptive services interfaces JUNOS Services Interfaces Configuration Guide ATM1 and ATM2 IQ interfaces “Defining the ATM Traffic-Shaping Profile” shaping on page 326 Multilink interfaces...
Page 236: Specifying The Logical Interface Number
JUNOS 10.1 Network Interfaces Configuration Guide Table 23: Statements for Logical Interface Properties (continued) Statement Interface Types Usage Guidelines vci-range ATM2 IQ interfaces “Configuring ATM-to-Ethernet Interworking” on page 236 ATM1 and ATM2 IQ point-to-point “Configuring a Point-to-Point ATM1 or vpi vpi-identifier interfaces ATM2 IQ Connection”...
Page 237: Example: Configuring Logical System Interface Properties
Chapter 4: Configuring Logical Interface Properties [edit logical-systems logical-system-name] interfaces interface-name { unit logical-unit-number { logical-interface-statements; policy-options { policy-options-statements; protocols { protocols-statements; routing-instances { routing-instances-statements; routing-options { routing-options-statements; For an overview of logical systems, see the JUNOS Feature Guide. For detailed information about logical system configuration, see the JUNOS Routing Protocols Configuration Guide.
Page 238: Adding A Logical Unit Description To The Configuration
JUNOS 10.1 Network Interfaces Configuration Guide Adding a Logical Unit Description to the Configuration You can include a text description of each logical unit in the configuration file. Any descriptive text you include is displayed in the output of the show interfaces commands, and is also exposed in the Management Information Base (MIB)
Page 239: Configuring A Multipoint Connection
Configuring Accounting for the Logical Interface Juniper Networks routing platforms can collect various kinds of data about traffic passing through the routing platform. You can set up one or more accounting profiles that specify some common characteristics of this data, including the following:...
Page 240: Example: Applying An Accounting Profile To The Logical Interface
JUNOS 10.1 Network Interfaces Configuration Guide Example: Applying an Accounting Profile to the Logical Interface Configure an accounting profile for an interface and apply it to a logical interface: [edit] accounting-options { file if_stats { size 4m files 10 transfer-interval 15; archive-sites { "ftp://login:password@host/path";...
Page 241: Enabling Or Disabling Snmp Notifications On Logical Interfaces
Chapter 4: Configuring Logical Interface Properties is the peak rate, in bps or cps. You can specify a value in bits per second either rate as a complete decimal number or as a decimal number followed by the abbreviation (1000), (1,000,000), or (1,000,000,000).
Page 242 JUNOS 10.1 Network Interfaces Configuration Guide frame-relay-ether-type | frame-relay-ether-type-tcc | frame-relay-ccc | frame-relay-tcc | multilink-frame-relay-end-to-end | multilink-ppp | vlan-ccc | vlan-tcc | vlan-vpls); You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] Some of the ATM encapsulations are defined in RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5.
Page 243: Configuring The Lcp Configure-Request Maximum Sent
Chapter 4: Configuring Logical Interface Properties For more information about multilink encapsulations, see the JUNOS Services Interfaces Configuration Guide. Configuring the LCP Configure-Request Maximum Sent Link Control Protocol (LCP) Configure-Request is used to establish a link. You can configure the maximum number of LCP Configure-Requests to send. The router stops sending LCP Configure-Requests after the specified maximum number is sent.
Page 244: Configuring The Ppp Clear Loop Detected Timer
JUNOS 10.1 Network Interfaces Configuration Guide user@host> run show interfaces t1-0/0/0:1:1.0 detail Logical interface t1-0/0/0:1:1.0 (Index 67) (SNMP ifIndex 40) (Generation 156) Flags: Hardware-Down Device-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPP PPP parameters: LCP restart timer: 2000 msec NCP restart timer: 2000 msec Protocol inet, MTU: 1500, Generation: 163, Route table: 0 Flags: Protocol-Down Addresses, Flags: Dest-route-down Is-Preferred Is-Primary...
Page 245: Configuring Ppp Chap Authentication
Chapter 4: Configuring Logical Interface Properties For information about creating dynamic profiles, see Configuring a Basic Dynamic Profile in the JUNOS Subscriber Access Configuration Guide. For information about assigning a dynamic profile to a PPP interface, see Attaching Dynamic Profiles to Static PPP Subscriber Interfaces in the JUNOS Subscriber Access Configuration Guide.
Page 246: Configuring A Default Pap Password
JUNOS 10.1 Network Interfaces Configuration Guide You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] For more information about configuring PAP for physical interfaces, see “Configuring the PPP Password Authentication Protocol” on page 126. For information about configuring tracing operations for the PPP protocol, see “Tracing Operations of the pppd Process”...
Page 247: Configuring The Local Password
Chapter 4: Configuring Logical Interface Properties Configuring the Local Password You need to configure the password to be used for authentication. To configure the host password for sending PAP requests, include the local-password statement: local-password password; You can include the statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number ppp-options pap] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number ppp-options pap]...
Page 248: Example: Configuring Dynamic Cac
JUNOS 10.1 Network Interfaces Configuration Guide bandwidth limit available for voice packets on the interface and requests the MGC to block new calls when the bandwidth is exhausted. Dynamic CAC is useful when a primary link becomes unavailable and a backup link with less bandwidth takes its place.
Page 249: Disabling A Logical Interface
Chapter 4: Configuring Logical Interface Properties dynamic-call-admission-control { bearer-bandwidth-limit 900 kbps; activation-priority 75; Disabling a Logical Interface You can unconfigure a logical interface, effectively disabling that interface, without removing the logical interface configuration statements from the configuration. To do this, include the statement: disable disable;...
Page 250 JUNOS 10.1 Network Interfaces Configuration Guide Disabling a Logical Interface...
Page 251: Configuring Protocol Family And Interface Address Properties
Chapter 5 Configuring Protocol Family and Interface Address Properties Protocol Family Configuration and Interface Address Statements on page 181 Configuring the Protocol Family on page 184 Configuring the Interface Address on page 186 Configuring ICCP for MC-LAG on page 188 Configuring IPCP Options on page 189 Configuring an Unnumbered Interface on page 192 Setting the Protocol MTU on page 197...
Page 252 JUNOS 10.1 Network Interfaces Configuration Guide filter { dialer filter-name; input filter-name; output filter-name; group filter-group-number; interface-mode (access | trunk); ipsec-sa sa-name; keep-address-and-control; mtu bytes; multicast-only; negotiate-address; no-redirects: policer { arp policer-template-name; input policer-template-name; output policer-template-name; primary; protocols [inet iso mpls]; proxy inet-address address;...
Page 253: Chapter 5 Configuring Protocol Family And Interface Address Properties
Chapter 5: Configuring Protocol Family and Interface Address Properties oam-period (disable | seconds); shaping { (cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst length); queue-length number; vci vpi-identifier.vci-identifier; primary; preferred; (vrrp-group | vrrp-inet6-group) group-number { (accept-data | no-accept-data);...
Page 254 JUNOS 10.1 Network Interfaces Configuration Guide Configuring the Protocol Family For each logical interface, you can configure one or more of the following protocols that run on the interface: —Protocol-independent family used for Layer 2 packet filtering. This option is not supported on J Series routers. —(M Series and T Series routers only) Configure only when the physical bridge interface is configured with...
Page 255: Configuring The Protocol Family
Chapter 5: Configuring Protocol Family and Interface Address Properties Layer 2 VPN to connect customer edge (CE) routers across an MPLS backbone. When you configure a VPLS encapsulation type, the statement is family vpls assumed by default. MX Series routers support dynamic profiles for VPLS pseudowires, VLAN identifier translation, and automatic bridge domain configuration.
Page 256: Vrrp Properties
JUNOS 10.1 Network Interfaces Configuration Guide the key factor in the successful deployment of IPv6. Because millions of IPv4 nodes already exist, upgrading every node to IPv6 at the same time is not feasible. As a result, transition from IPv4 to IPv6 happens gradually, allowing nodes to be upgraded independently and without disruption to other nodes.
Page 257: Configuring An Interface Ipv4 Address
Chapter 5: Configuring Protocol Family and Interface Address Properties For each address, you can optionally configure one or more of the following: Broadcast address for the interface s subnet—Specify this in the broadcast statement; this applies only to Ethernet interfaces, such as the management interface fxp0 , the Fast Ethernet interface, and the Gigabit Ethernet...
Page 258: Configuring Iccp For Mc-Lag
<inet> level. NOTE: Juniper Networks routers support /31 destination prefixes when used in point-to-point Ethernet configurations; however, it is not supported by many other devices, such as hosts, hubs, or routers. You must determine if the peer system also supports /31 destination prefixes before configuration.
Page 259: Configuring Ipcp Options
Chapter 5: Configuring Protocol Family and Interface Address Properties peer ip-address{ authentication-key string; liveness-detection { detection-time { threshold milliseconds; minimum-interval milliseconds; minimum-receive-interval milliseconds; multiplier number; no-adaptation; transmit-interval { minimum-interval milliseconds; threshold milliseconds; version (1 | automatic); local-ip-addr ipv4-address; redundancy-group-id-list [ redundancy-groups ]; session-establishment-hold-time value;...
Page 260: Configuring An Ip Address For An Interface
JUNOS 10.1 Network Interfaces Configuration Guide When you enable a PPP interface, you can configure an IP address, enable the interface to negotiate an IP address assignment from the remote end, or allow the interface to be unnumbered. You can also assign a destination profile to the remote end.
Page 261 Chapter 5: Configuring Protocol Family and Interface Address Properties have a configured address (see “Configuring the Interface Address” on page 186). Specify the IP address of the remote interface with the statement. destination You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family inet] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family inet]...
Page 262: Configuring An Unnumbered Interface
JUNOS 10.1 Network Interfaces Configuration Guide Configuring an Unnumbered Interface When you need to conserve IP addresses, you can configure unnumbered interfaces. Setting up an unnumbered interface enables IP processing on the interface without assigning an explicit IP address to the interface. For IPv6, in which conserving addresses is not a major concern, you can configure unnumbered interfaces to share the same subnet across multiple interfaces.
Page 263 Chapter 5: Configuring Protocol Family and Interface Address Properties Configuring an Unnumbered Ethernet or Demux Interface To configure an unnumbered Ethernet or demultiplexing interface, include the unnumbered-address statement in the configuration: unnumbered-address interface-name; You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family family] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family]...
Page 264: Configuring A Preferred Source Address For Unnumbered Ethernet Or Demux Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide For more information, see the following sections: Configuring a Preferred Source Address for Unnumbered Ethernet or Demux Interfaces on page 194 Configuring Static Routes on Unnumbered Ethernet Interfaces on page 195 Restrictions for Configuring Unnumbered Ethernet Interfaces on page 195 Example: Configuring an Unnumbered Ethernet Interface on page 196 Example: Configuring the Preferred Source Address for an Unnumbered Ethernet Interface on page 196...
Page 265: Restrictions For Configuring Unnumbered Ethernet Interfaces
Chapter 5: Configuring Protocol Family and Interface Address Properties You cannot delete an address on a donor loopback interface while it is being used as the preferred source address for an unnumbered Ethernet or demux interface. The router uses the preferred source address, if configured for an unnumbered Ethernet or demux interface, in ARP requests and replies.
Page 266 JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring an Unnumbered Ethernet Interface In this example, ge-1/0/0 is the unnumbered interface and ge-0/0/0 is the donor interface from which “borrows” an IP address. ge-1/0/0 interfaces { ge-0/0/0 { unit 0 { family inet { address 4.4.4.1/24;...
Page 267: Example: Configuring An Unnumbered Ethernet Interface As The Next Hop For A Static Route
Chapter 5: Configuring Protocol Family and Interface Address Properties Example: Configuring an Unnumbered Ethernet Interface as the Next Hop for a Static Route In this example, is the unnumbered interface and a loopback interface, ge-0/0/0 , is the donor interface from which ge-0/0/0 “borrows”...
Page 268: Disabling The Removal Of Address And Control Bytes
JUNOS 10.1 Network Interfaces Configuration Guide If you increase the size of the protocol MTU, you must ensure that the size of the media MTU is equal to or greater than the sum of the protocol MTU and the encapsulation overhead. For a list of encapsulation overhead values, see Table 18 on page 116.
Page 269: Configuring Default, Primary, And Preferred Addresses And Interfaces
Chapter 5: Configuring Protocol Family and Interface Address Properties To disable the sending of protocol redirect messages for the entire router, include statement at the hierarchy level. no-redirects [edit system] Configuring Default, Primary, and Preferred Addresses and Interfaces The router has a default address and a primary interface, and interfaces have primary and preferred addresses.
Page 270 JUNOS 10.1 Network Interfaces Configuration Guide could be picked. In practice, this means that, on the router, the interface fxp0 is picked by default. To configure a different interface to be the primary interface, include the primary statement: primary; You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family family] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family]...
Page 271: Applying Policers
Chapter 5: Configuring Protocol Family and Interface Address Properties [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family address address] Applying Policers Policers allow you to perform simple traffic policing on specific interfaces or Layer 2 virtual private networks (VPNs) without configuring a firewall filter. To apply policers, include the policer statement:...
Page 272: Applying Aggregate Policers
JUNOS 10.1 Network Interfaces Configuration Guide If you apply both policers and firewall filters to an interface, input policers are evaluated before input firewall filters, and output policers are evaluated after output firewall filters. If you apply the policer to the interface , it is applied to packets received or transmitted by the Routing Engine.
Page 273: Example: Applying Aggregate Policers
Chapter 5: Configuring Protocol Family and Interface Address Properties and IPv6 traffic and you apply the logical interface policer to only the IPv4 policer1 and IPv6 protocol families, MPLS traffic is not subject to the constraints of policer1 If you apply to a different logical interface, there are two instances of the policer1 policer.
Page 274: Applying Hierarchical Policers On Enhanced Intelligent Queuing Pics
JUNOS 10.1 Network Interfaces Configuration Guide family inet6 { policer { input aggregate_police1; family ccc { policer { input aggregate_police2; family mpls { policer { input aggregate_police2; unit 1 { family inet { policer { input aggregate_police1; family inet6 { policer { input aggregate_police1;...
Page 275: Hierarchical Policer Overview
Chapter 5: Configuring Protocol Family and Interface Address Properties Again, the interface here may be a physical interface or logical interface (for example, DLCI). With BA classification, the miscellaneous traffic (the traffic not matching with any of the BA classification DSCP/EXP bits) will be policed as non-EF traffic. No separate policers will be installed for this traffic.
Page 276: Configuring Hierarchical Policers
JUNOS 10.1 Network Interfaces Configuration Guide Policer1—EF traffic Policer2—non-EF traffic Shared token bucket is used to police the traffic as follows: Policer1 is set to EF rate (for example, 2 Mbps) Policer2 is set to aggregate interface policed rate (for example, 10 Mbps). EF traffic gets applied to Policer1.
Page 277: Configuring A Single-Rate Two-Color Policer
Chapter 5: Configuring Protocol Family and Interface Address Properties bandwidth-limit 70m; burst-size-limit 1500; then { discard; premium { if-exceeding { bandwidth-limit 50m; burst-size-limit 1500; then { discard; You can apply the hierarchical policer as follows: [edit interfaces so-0/1/0 unit 0 layer-2-policer] input-hierarchical-policer foo;...
Page 278: Configuring A Two-Rate Tricolor Marker Policer
JUNOS 10.1 Network Interfaces Configuration Guide Configuring a Single-Rate Color-Blind Policer You can configure a single-rate color blind policer as follows: [edit firewall three-color-policer foo] single-rate { color-blind; committed-information-rate 50m; committed-burst-size 1500; excess-burst-size 1500; You can apply the single-rate color blind policer as follows: [edit interfaces so-0/1/0 unit 0 layer-2-policer] input-three-color foo;...
Page 279 Chapter 5: Configuring Protocol Family and Interface Address Properties After +/- byte adjust offset Marking is color aware and color blind: Color aware needs to have the color set by q-tree lookup based on: Programmable marking actions: Color (red, yellow, green) Drop based on color and congestion profile Policer is selected based on the arriving channel number: Channel number LUT produces policer index and queue index...
Page 280: Applying A Filter To An Interface
JUNOS 10.1 Network Interfaces Configuration Guide Configuring a [edit firewall three-color-policer bar] two-rate { Color-Aware trTCM color-aware; committed-information-rate 50m; committed-burst-size 1500; peak-information-rate 100m; peak-burst-size 3k; You can apply the three-color two-rate color-aware policer as follows: [edit interfaces so-0/1/0 unit 0 layer-2-policer] input-three-color bar;...
Page 281 Chapter 5: Configuring Protocol Family and Interface Address Properties When you apply filters using the statement or the statement, a input-list output-list new filter is created with the name <interface-name>.<unit-direction>. This filter is exclusively interface-specific. You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family family] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family family]...
Page 282: Defining Interface Groups In Firewall Filters
JUNOS 10.1 Network Interfaces Configuration Guide If you apply the filter to the interface , it is applied to packets received or transmitted by the Routing Engine. You cannot apply MPLS filters to the management interface ( fxp0 ) or the loopback interface ( For more information about firewall filters, see the JUNOS Policy Framework Configuration Guide.
Page 283 Chapter 5: Configuring Protocol Family and Interface Address Properties Example: Applying a Filter to an Interface For M Series and T Series routers only, apply an input filter to VPLS traffic. Output Input Filter for VPLS filters do not work for broadcast and multicast traffic, including VPLS traffic. Traffic [edit interfaces] fe-2/2/3 {...
Page 284 JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces] so-0/0/3 { unit 0 { family inet { filter { output fbf; address 10.50.10.2/25; fe-1/2/0 { unit 0 { family inet { address 10.50.50.2/25; so-2/0/0 { unit 0 { family inet { address 10.50.20.2/25;...
Page 285: Configuring Unicast Rpf
Chapter 5: Configuring Protocol Family and Interface Address Properties fbf-group { import-rib [inet.0 fbf.inet.0]; Configuring Unicast RPF For interfaces that carry IPv4 or IPv6 traffic, you can reduce the impact of denial of service (DoS) attacks by configuring unicast reverse path forwarding (RPF). Unicast RPF helps determine the source of attacks and rejects packets from unexpected source addresses on interfaces where unicast RPF is enabled.
Page 286 JUNOS 10.1 Network Interfaces Configuration Guide The optional fail filter allows you to apply a filter to packets that fail the unicast RPF check. You can define the fail filter to perform any filter operation, including accepting, rejecting, logging, sampling, or policing. When unicast RPF is enabled on an interface, Bootstrap Protocol (BOOTP) packets and Dynamic Host Configuration Protocol (DHCP) packets are not accepted on the interface.
Page 287: Unicast Rpf Behavior With A Default Route
Chapter 5: Configuring Protocol Family and Interface Address Properties To configure unicast RPF loose mode, include the mode mode loose; You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family (inet | inet6) rpf-check <fail-filter filter-name>] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family (inet | inet6) rpf-check <fail-filter filter-name>]...
Page 288: Unicast Rpf With Routing Asymmetry
JUNOS 10.1 Network Interfaces Configuration Guide The packet is not accepted when either of the following is true: The source address of the packet does not match a prefix in the routing table. The interface does not expect to receive a packet with this source address prefix. Unicast RPF Behavior Without a Default Route If you do not configure a default route, or if the default route does not use an interface configured with unicast RPF, unicast RPF behaves as described in “Configuring...
Page 289: Configuring Unicast Rpf On A Vpn
Chapter 5: Configuring Protocol Family and Interface Address Properties Configuring Unicast RPF on a VPN You can configure unicast RPF on a VPN interface by enabling unicast RPF on the interface and including the statement at the interface [edit routing-instances hierarchy level.
Page 290: Enabling Source Class And Destination Class Usage
JUNOS 10.1 Network Interfaces Configuration Guide address { 255.255.255.255/32; then { count rpf-dhcp-bootp-traffic; accept; term default { then { log; reject; [edit] interfaces { so-0/0/0 { unit 0 { family inet { rpf-check fail-filter rpf-special-case-dhcp-bootp; Enabling Source Class and Destination Class Usage For interfaces that carry IPv4, IPv6, or MPLS traffic, you can maintain packet counts based on the entry and exit points for traffic passing through your network.
Page 291: Figure 9: Prefix Accounting With Source And Destination Classes
Chapter 5: Configuring Protocol Family and Interface Address Properties NOTE: SCU and DCU accounting are supported on the J Series router only for IPv4 and IPv6 traffic. NOTE: We recommend that you stop the network traffic on an interface before you modify the DCU or SCU configuration for that interface.
Page 292 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: Performing DCU accounting when an output service is enabled produces inconsistent behavior in the following configuration: Both SCU input and DCU are configured on the packet input interface. SCU output is configured on the packet output interface. Interface services is enabled on the output interface.
Page 293: Examples: Enabling Source Class And Destination Class Usage
Chapter 5: Configuring Protocol Family and Interface Address Properties On T Series, M120, and M320 routers, the source class and destination classes are not carried across the router fabric. The implications of this are as follows: On T Series, M120, and M320 routers, SCU and DCU accounting is performed before the packet enters the fabric.
Page 294 JUNOS 10.1 Network Interfaces Configuration Guide Source routers A and B use loopback addresses as the prefixes to be monitored. Most Complete SCU of the configuration tasks and actual monitoring occur on transit Router SCU. Configuration The loopback address on Router A contains the origin of the prefix that is to be assigned to source class A on Router SCU.
Page 295 Chapter 5: Configuring Protocol Family and Interface Address Properties source-class-usage { input; output; address 10.255.50.1/24; so-0/0/3 { unit 0 { family inet { accounting { source-class-usage { input; output; address 10.255.10.3/24; lo0 { unit 0 { family inet { address 10.255.6.111/32; protocols { ospf { area 0.0.0.0 {...
Page 296 JUNOS 10.1 Network Interfaces Configuration Guide Just as Router A provides a source prefix, Router B's loopback address matches the Router B prefix assigned to scu-class-b on Router SCU. Again, no SCU processing happens on this router, so configure Router B for basic OSPF routing and include your loopback interface and interface so-0/0/4 in the OSPF process.
Page 297 Chapter 5: Configuring Protocol Family and Interface Address Properties Map the VRF instance type to the virtual loopback tunnel interface. For SCU and DCU to work, you must not include the statement at the vrf-table-label [edit routing-instances instance-name] hierarchy level. [edit routing-instances] VPN-A { instance-type vrf;...
Page 298 JUNOS 10.1 Network Interfaces Configuration Guide Enabling Source Class and Destination Class Usage...
Page 299: Chapter 6 Configuring Circuit And Translational Cross-Connects
Chapter 6 Configuring Circuit and Translational Cross-Connects Circuit and Translational Cross-Connects Overview on page 229 Defining the Encapsulation for Switching Cross-Connects on page 231 Defining the Connection for Switching Cross-Connects on page 234 Configuring MPLS for Switching Cross-Connects on page 235 Configuring IS-IS or MPLS Traffic for TCC Interfaces on page 235 Configuring ATM-to-Ethernet Interworking on page 236 Examples: Configuring Switching Cross-Connects on page 239...
Page 300: Figure 10: Layer 2 Switching Circuit Cross-Connect
Router A and Router C have Frame Relay connections to Router B, which is a Juniper Networks router. CCC allows you to configure Router B to act as a Frame Relay (Layer 2) switch. To do this, configure a circuit from Router A to Router C that passes through Router B, effectively configuring Router B as a Frame Relay switch with respect to these routers.
Page 301 Chapter 6: Configuring Circuit and Translational Cross-Connects This chapter discusses the Layer 2 switching cross-connect configuration tasks. For information about MPLS tunneling and LSP stitching, see the JUNOS MPLS Applications Configuration Guide. For information about Layer 2 and Layer 2.5 VPNs, see the JUNOS VPNs Configuration Guide.
Page 302 JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces interface-name] encapsulation (ppp-ccc | cisco-hdlc-ccc | ppp-tcc | cisco-hdlc-tcc); unit 0; Configuring ATM Circuits For ATM circuits, include the statement [edit interfaces interface-name atm-options] hierarchy level: [edit interfaces at-fpc/pic/port] atm-options { vpi vpi-identifier; On the logical interface, include the following statements: point-to-point;...
Page 303 Chapter 6: Configuring Circuit and Translational Cross-Connects The encapsulation type can be one of the following: Flexible Frame Relay ( )—Intelligent queuing (IQ) interfaces can flexible-frame-relay use flexible Frame Relay encapsulation. You use flexible Frame Relay encapsulation when you want to configure multiple per-unit Frame Relay encapsulations.
Page 304 JUNOS 10.1 Network Interfaces Configuration Guide For Ethernet CCC circuits, specify the encapsulation by including the encapsulation statement at the [edit interfaces interface-name] hierarchy level. This statement configures the entire physical device. [edit interfaces interface-name] encapsulation ethernet-ccc; unit logical-unit-number { [edit interfaces aex] encapsulation ethernet-ccc;...
Page 305 Chapter 6: Configuring Circuit and Translational Cross-Connects in Figure 10 on page 230). The connection joins the interface that comes from the circuit s source to the interface that leads to the circuit s destination. When you specify the interface names, include the logical portion of the name, which corresponds to the logical unit number.
Page 306: Configuring Atm-To-Ethernet Interworking
JUNOS 10.1 Network Interfaces Configuration Guide [edit protocols isis interface interface-name] point-to-point; For more information about Layer 2.5 VPNs, see the JUNOS VPNs Configuration Guide and the Translational Cross-Connect and Layer 2.5 VPNs Feature Guide. Configuring ATM-to-Ethernet Interworking The ATM-to-Ethernet interworking feature is useful where ATM2 interfaces are used to terminate ATM DSLAM traffic.
Page 307: Configuring The Atm-To-Ethernet Interworking Protocol Family
Chapter 6: Configuring Circuit and Translational Cross-Connects Configuring the ATM-to-Ethernet Interworking Protocol Family on page 239 Configuring the ATM-to-Ethernet Interworking Logical Interface VPI on page 239 Configuring the ATM-to-Ethernet Interworking Logical Interface VCI on page 239 Enabling ATM-to-Ethernet Interworking To enable the ATM-to-Ethernet interworking cross-connect function, include the statement at the hierarchy level: vlan-vci-tagging...
Page 308 JUNOS 10.1 Network Interfaces Configuration Guide Configuring the ATM-to-Ethernet Interworking Inner VLAN Identifier Range Configure the Ethernet logical interface inner VLAN ID range by including the statement and specifying the starting VLAN ID and ending VLAN inner-vlan-id-range ID at the [edit interfaces interface-name unit logical-unit-number] hierarchy level: [edit interfaces interface-name unit logical-unit-number]...
Page 309: Examples: Configuring Switching Cross-Connects
Chapter 6: Configuring Circuit and Translational Cross-Connects The ATM2 OC48 PIC does not support the encapsulation type vlan-vci-ccc The encapsulation type vlan-vci-ccc only supports the protocol family. Attempts to configure any other interface protocol family are rejected. Configuring the ATM-to-Ethernet Interworking Protocol Family Configure the ATM logical interface protocol family by including the statement family...
Page 310: Example: Configuring A Ccc Over Frame Relay Encapsulated Interface
Example: Configuring a CCC over Frame Relay Encapsulated Interface Configure a full-duplex Layer 2 switching circuit cross-connect between Router A and Router C, using a Juniper Networks router, Router B, as the virtual switch. See the topology in Figure 11 on page 240.
Page 311: Figure 12: Layer 2.5 Switching Translational Cross-Connect
Chapter 6: Configuring Circuit and Translational Cross-Connects In this topology, Router B has a PPP connection to Router A and an ATM connection to Router C. Figure 12: Layer 2.5 Switching Translational Cross-Connect On Router A [edit] interfaces { so-0/1/0 { description "to Router B so-1/0/0";...
Page 312: Example: Configuring Ccc Over Aggregated Ethernet
JUNOS 10.1 Network Interfaces Configuration Guide [edit] On Router C interfaces { at-0/3/0 { description "to Router B at-1/1/0"; atm-options { vpi 0 maximum-vcs 2000; unit 32 { vci 32; encapsulation atm-vc-mux; family inet { address 10.1.1.2/30; Example: Configuring CCC over Aggregated Ethernet See the topology in Figure 13 on page 242.
Page 313 Chapter 6: Configuring Circuit and Translational Cross-Connects On Router B [edit interfaces] ae0 { encapsulation vlan-ccc; vlan-tagging; aggregated-ether-options { minimum-links 1; link-speed 1g; unit 0 { # CCC switch encapsulation vlan-ccc; vlan-id 600; family ccc; ae1 { encapsulation vlan-ccc; vlan-tagging; aggregated-ether-options { minimum-links 1;...
Page 314: Example: Configuring A Remote Lsp Ccc Over Aggregated Ethernet
JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring a Remote LSP CCC over Aggregated Ethernet See the topology in Figure 14 on page 244. In this topology, CE Router G has an aggregated Ethernet connection to PE Router F. CE Router D has an aggregated Ethernet connection to PE Router E.
Page 315 Chapter 6: Configuring Circuit and Translational Cross-Connects [edit protocols] mpls { interface all; connections { remote-interface-switch remote-sw-1 { interface ae0.0; receive-lsp lsp2_1; transmit-lsp lsp1_2; [edit interfaces] On Router F ae1 { encapsulation ethernet-ccc; aggregated-ether-options { minimum-links 1; link-speed 100m; lacp { active;...
Page 316: Example: Configuring Atm-To-Ethernet Interworking
JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring ATM-to-Ethernet Interworking The following example shows the configuration of the ATM and Ethernet interfaces for an ATM-to-Ethernet interworking cross connect. In the example ATM DSLAM traffic is terminated on an ATM2 interface. The ATM traffic is forwarded using encapsulation type to a local Ethernet IQ2 and IQ2-E interface.
Page 317: Tracing Interface Operations
Chapter 7 Tracing Interface Operations Tracing Interface Operations Overview on page 247 Tracing Operations of an Individual Router Interface on page 247 Tracing Operations of the Interface Process on page 248 Tracing Interface Operations Overview You can trace the operations of individual router interfaces and those of the interface process (dcd).
Page 318: Tracing Operations Of The Interface Process
JUNOS 10.1 Network Interfaces Configuration Guide Tracing Operations of the Interface Process To trace the operations of the router s interface process, dcd, include the traceoptions statement at the hierarchy level: [edit interfaces] [edit interfaces] traceoptions { file <filename> <files number> <match regular-expression> <size size> <world-readable | no-world-readable>;...
Page 319: Part 3 Configuring Special Router Interfaces
Part 3 Configuring Special Router Interfaces Displaying the Internal Ethernet Interface on page 251 Configuring Discard Interfaces on page 255 Configuring IP Demultiplexing Interfaces on page 257 Configuring the Loopback Interface on page 263 Configuring Special Router Interfaces...
Page 320 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Special Router Interfaces...
Page 321: Displaying The Internal Ethernet Interface
Chapter 8 Displaying the Internal Ethernet Interface Internal Ethernet Interface Overview on page 251 Displaying the Internal Ethernet Interface for M Series, MX Series, and Most T Series Routers on page 251 Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus Router on page 252 Internal Ethernet Interface Overview The router internal Ethernet interface connects the Routing Engine with the router s...
Page 322 JUNOS 10.1 Network Interfaces Configuration Guide unit 0 { family tnp { address 1; Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus Router The router internal Ethernet interface connects the Routing Engine with the router s packet forwarding components.
Page 323 Chapter 8: Displaying the Internal Ethernet Interface The following example is a sequence of commands issued in a CLI show interfaces session with a T1600 router in a routing matrix. In the example, the T1600 router, which is also called the line-card chassis (LCC), is known by the IP host name host-sfc-0-lcc-2 and contains redundant Routing Engines.
Page 324 JUNOS 10.1 Network Interfaces Configuration Guide Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus Router...
Page 325: Configuring Discard Interfaces
Chapter 9 Configuring Discard Interfaces Discard Interfaces Overview on page 255 Example: Discard Interface on page 256 Discard Interfaces Overview On the routing platform, you can configure one physical discard interface, dsc . The discard interface allows you to identify the ingress point of a denial-of-service (DoS) attack.
Page 326 JUNOS 10.1 Network Interfaces Configuration Guide Example: Discard Interface on page 256 Related Topics Example: Discard Interface To configure a discard interface, include the following statements at the [edit interfaces] hierarchy level: [edit interfaces] dsc { unit 0 { family inet { filter { output filter-name;...
Page 327: Configuring Ip Demultiplexing Interfaces
Chapter 10 Configuring IP Demultiplexing Interfaces IP Demultiplexing Interface Overview on page 257 Configuring an IP Demultiplexing Interface on page 257 Configuring an IP Demux Underlying Interface on page 258 Specifying the Demux Underlying Interface on page 259 Configuring IP Demux Prefixes on page 260 Configuring MAC Address Validation on Static Demux Interfaces on page 260 Example: Configuring a Demux Interface on page 261 IP Demultiplexing Interface Overview...
Page 328 JUNOS 10.1 Network Interfaces Configuration Guide demux0 { unit logical-unit-number { demux-options { underlying-interface interface-name; family family { demux-destination { destination-prefix; demux-destination { source-prefix; mac-validate (loose | strict) unnumbered-address interface-name <preferred-source-address address>; Keep the following guidelines in mind when configuring the demux interface: Demux interfaces are supported on M120 or MX Series routers only.
Page 329: Specifying The Demux Underlying Interface
Chapter 10: Configuring IP Demultiplexing Interfaces NOTE: IP demux interfaces support only Gigabit Ethernet, Fast Ethernet, 10-Gigabit Ethernet, or aggregated Ethernet underlying interfaces. To determine which IP demux interface to use, the destination or source prefix is matched against the destination or source address of packets that the underlying interface receives.
Page 330: Configuring Ip Demux Prefixes
JUNOS 10.1 Network Interfaces Configuration Guide Configuring IP Demux Prefixes You configure demux prefixes for use by the underlying interface. The demux prefixes can represent individual hosts or networks. For a given demux interface unit, you can configure either demux source or demux destination prefixes but not both. You can choose not to configure a demux source or demux destination prefix.
Page 331: Example: Configuring A Demux Interface
Chapter 10: Configuring IP Demultiplexing Interfaces Strict—Forwards packets when both the IP source address and the MAC source address match one of the trusted address tuples. Drops packets when the MAC address does not match the tuple's MAC source address, or when IP source address of the incoming packet does not match any of the trusted IP addresses.
Page 332 JUNOS 10.1 Network Interfaces Configuration Guide demux0 { unit 101 { description vlan1-sub1; demux-options { underlying-interface fe-0/0/0.100; family inet { demux-source 10.1.1.0/24; filter { input vlan1-sub1-in-filter; output vlan1-sub1-out-filter; mac-validate loose; unit 102 { description vlan1-sub2; demux-options { underlying-interface fe-0/0/0.100; family inet { demux-source { 10.1.0.0/16;...
Page 333: Configuring The Loopback Interface
Chapter 11 Configuring the Loopback Interface Configuring the Loopback Interface on page 263 Configuring the Loopback Interface On the router, you can configure one physical loopback interface, lo0 , and one or more addresses on the interface. To configure the physical loopback interface, include the following statements at the hierarchy level: [edit interfaces] [edit interfaces]...
Page 334: Example: Configuring The Loopback Interface
JUNOS 10.1 Network Interfaces Configuration Guide If you configure the loopback interface, it is automatically used for unnumbered interfaces. If you do not configure the loopback interface, the router chooses the first interface to come online as the default. If you configure more than one address on the loopback interface, we recommend that you configure one to be the primary address to ensure that it is selected for use with unnumbered interfaces.
Page 335 Chapter 11: Configuring the Loopback Interface 127.0.0.1/32; 192.16.0.1/24; Configure an IP and an IPv6 address on the loopback interface with subnetwork routes: [edit] user@host# edit interfaces lo0 unit 0 family inet [edit interfaces lo0 unit 0 family inet] user@host# set address 192.16.0.1/24 [edit interfaces lo0 unit 0 family inet] user@host# up [edit interfaces lo0 unit 0 family]...
Page 336 JUNOS 10.1 Network Interfaces Configuration Guide Configuring the Loopback Interface...
Page 337: Configuring Serial Interfaces
Part 4 Configuring Serial Interfaces Configuring Serial Interfaces on page 269 Configuring Serial Interfaces...
Page 338 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Serial Interfaces...
Page 339: Serial Interfaces Overview
Chapter 12 Configuring Serial Interfaces Serial Interfaces Overview on page 269 Example: Physical Interface Configuration Statements for Serial Interfaces on page 270 Configuring the Serial Line Protocol on page 271 Configuring the Serial Clocking Mode on page 275 Configuring the Serial Idle Cycle Flag on page 277 Configuring the Serial Signal Handling on page 278 Configuring the Serial DTR Circuit on page 280 Configuring Serial Signal Polarities on page 281...
Page 340 ITU-T Recommendation V.35, Data Transmission at 48 kbit/s Using 60-108 kHz Group Band Circuits. Note that the Juniper Networks Serial PIC supports V.35 interfaces with speeds higher than 48 kilobits per second.
Page 341 Chapter 12: Configuring Serial Interfaces control-signal (assert | de-assert | normal); cts (ignore | normal | require); dcd (ignore | normal | require); dsr (ignore | normal | require); dtr signal-handling-option; ignore-all; indication (ignore | normal | require); rts (assert | de-assert | normal); tm (ignore | normal | require);...
Page 342: Serial Interface Default Settings
JUNOS 10.1 Network Interfaces Configuration Guide For more information about serial interfaces, see the following sections: Serial Interface Default Settings on page 272 Invalid Serial Interface Statements on page 273 Serial Interface Default Settings EIA-530 Interface Default Settings on page 272 V.35 Interface Default Settings on page 272 X.21 Interface Default Settings on page 273 EIA-530 Interface Default Settings...
Page 343: Invalid Eia-530 Interface Statements
Chapter 12: Configuring Serial Interfaces dsr normal; dtr normal; rts normal; clock-rate 16.384mhz; clocking-mode loop; cts-polarity positive; dcd-polarity positive; dsr-polarity positive; dtr-circuit balanced; dtr-polarity positive; encoding nrz; rts-polarity positive; You can include the line-protocol statement at the following hierarchy levels: [edit interfaces se-pim/0/port serial-options] [edit interfaces se-fpc/pic/port serial-options] X.21 Interface Default Settings...
Page 344 JUNOS 10.1 Network Interfaces Configuration Guide Invalid EIA-530 Interface Statements If you do not include the line-protocol statement or if you explicitly configure the default EIA-530 line protocol, the following statements are invalid: dce-options | dte-options { control-signal (assert | de-assert | normal); indication (ignore | normal | require);...
Page 345: Configuring The Serial Clocking Mode
Chapter 12: Configuring Serial Interfaces dsr-polarity (negative | positive); dtr-circuit (balanced | unbalanced); dtr-polarity (negative | positive); loopback (dce-local | dce-remote); rts-polarity (negative | positive); tm-polarity (negative | positive); You can include the line-protocol statement at the following hierarchy levels: [edit interfaces se-pim/0/port serial-options] [edit interfaces se-fpc/pic/port serial-options] Configuring the Serial Clocking Mode...
Page 346: Inverting The Serial Interface Transmit Clock
JUNOS 10.1 Network Interfaces Configuration Guide To configure the clocking mode of a serial interface, include the clocking-mode statement: clocking-mode (dce | internal | loop); You can include this statement at the following hierarchy levels: [edit interfaces se-pim/0/port serial-options] [edit interfaces se-fpc/pic/port serial-options] For more information about clocking on serial interfaces, see the following sections: Inverting the Serial Interface Transmit Clock on page 276 Configuring the DTE Clock Rate on page 276...
Page 347: Configuring The Serial Idle Cycle Flag
Chapter 12: Configuring Serial Interfaces 2.048 MHz 2.341 MHz 2.731 MHz 3.277 MHz 4.096 MHz 5.461 MHz 8.192 MHz 16.384 MHz Although the serial interface is intended for use at the default rate of 16.384 MHz, you might need to use a slower rate if any of the following conditions prevail: The interconnecting cable is too long for effective operation.
Page 348: Configuring The Serial Signal Handling
JUNOS 10.1 Network Interfaces Configuration Guide Configuring the Serial Signal Handling By default, normal signal handling is enabled for all signals. For each signal, the normal option applies to the normal signal handling for that signal, as defined by the following standards: TIA/EIA Standard 530 ITU-T Recommendation V.35...
Page 349 Chapter 12: Configuring Serial Interfaces [edit interfaces se-pim/0/port serial-options] [edit interfaces se-fpc/pic/port serial-options] For EIA-530 and V.35 interfaces, configure to-DCE signals by including the statements, specifying the assert de-assert , or normal option: dtr (assert | de-assert | normal); rts (assert | de-assert | normal); For X.21 interfaces, configure to-DCE signals by including the statement, control-signal...
Page 350: Configuring The Serial Dtr Circuit
JUNOS 10.1 Network Interfaces Configuration Guide NOTE: For V.35 and X.21 interfaces, you cannot include the statement in the configuration. For X.21 interfaces, you cannot include the , and statements in the configuration. For EIA-530 and V.35 interfaces, you cannot include the control-signal indication statements in the configuration.
Page 351: Configuring Serial Signal Polarities
Chapter 12: Configuring Serial Interfaces dtr-circuit (balanced | unbalanced); You can include this statement at the following hierarchy levels: [edit interfaces se-pim/0/port serial-options] [edit interfaces se-fpc/pic/port serial-options] Configuring Serial Signal Polarities Serial interfaces use a differential protocol signaling technique. Of the two serial signals associated with a circuit, the one referred to as the A signal is denoted with a plus sign, and the one referred to as the B signal is denoted with a minus sign;...
Page 352: Figure 17: Serial Interface Liu Loopback
JUNOS 10.1 Network Interfaces Configuration Guide Figure 17: Serial Interface LIU Loopback DCE local and DCE remote control the EIA-530 interface-specific signals for enabling local and remote loopback on the link partner DCE. Local loopback is shown in Figure 18 on page 282. Figure 18: Serial Interface Local Loopback For EIA-530 interfaces, you can configure DCE local, DCE remote, local, and remote (LIU) loopback capability.
Page 353: Example: Configuring Serial Loopback Capability
Chapter 12: Configuring Serial Interfaces You can determine whether there is an internal or external problem by checking the error counters in the output of the command: show interface se-fpc/pic/port extensive user@host> show interfaces se-fpc/pic/port extensive Example: Configuring Serial Loopback Capability To determine the source of a problem, loop packets on the local router, the local DCE, the remote DCE, and the remote line interface unit (LIU).
Page 354 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Serial Line Encoding...
Page 355: Part 5 Configuring Atm Interfaces
Part 5 Configuring ATM Interfaces Configuring ATM Interfaces on page 287 Configuring ATM-over-ADSL Interfaces on page 363 Configuring ATM-over-SHDSL Interfaces on page 369 Configuring ATM Interfaces...
Page 356: Configuring Atm Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Configuring ATM Interfaces...
Page 357: Atm Interfaces Overview
Chapter 13 Configuring ATM Interfaces ATM Interfaces Overview on page 288 ATM1 Physical and Logical Configuration Statement Hierarchies on page 290 ATM2 IQ Physical and Logical Configuration Statement Hierarchies on page 292 Supported Features on ATM1 and ATM2 IQ Interfaces on page 294 Configuring Communication with Directly Attached ATM Switches and Routers on page 299 Enabling ILMI for Cell Relay on page 300...
Page 358 JUNOS 10.1 Network Interfaces Configuration Guide Configuring the ATM OAM F5 Loopback Cell Threshold on page 337 Configuring ATM Interface Encapsulation on page 338 Configuring an ATM1 Cell-Relay Circuit on page 340 Configuring PPP over ATM2 Encapsulation on page 342 Configuring E3 and T3 Parameters on ATM Interfaces on page 345 Configuring SONET/SDH Parameters on ATM Interfaces on page 346 Configuring ATM2 IQ VC Tunnel CoS Components on page 347...
Page 359 Chapter 13: Configuring ATM Interfaces Configuring Communication with Directly Attached ATM Switches and Routers on page 299 Enabling ILMI for Cell Relay on page 300 Configuring Communication with Directly Attached ATM Switches and Routers on page 299 Enabling ILMI for Cell Relay on page 300 Enabling Passive Monitoring on ATM Interfaces on page 301 Removing MPLS Labels from Incoming Packets on page 302 Configuring the ATM PIC Type on page 303...
Page 360 JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring ATM1 Interfaces on page 358 Example: Configuring ATM2 IQ Interfaces on page 360 ATM1 Physical and Logical Configuration Statement Hierarchies To configure ATM1 physical interface properties, include the atm-options e3-options t3-options , and sonet-options statements at the [edit interfaces at-fpc/pic/port]...
Page 361 Chapter 13: Configuring ATM Interfaces z3 value ; z4 value; loopback (local | remote); (payload-scrambler | no-payload-scrambler); rfc-2615; trigger { defect ignore { hold-time up milliseconds down milliseconds; (z0-increment | no-z0-increment); t3-options { atm-encapsulation (direct | plcp); buildout feet; (cbit-parity | no-cbit-parity); loopback (local | payload | remote);...
Page 362 JUNOS 10.1 Network Interfaces Configuration Guide You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] ATM2 IQ Physical and Logical Configuration Statement Hierarchies To configure ATM2 IQ physical interface properties, include the atm-options sonet-options statements at the...
Page 363 Chapter 13: Configuring ATM Interfaces authentication-key key; force; hold-time milliseconds; lockout; neighbor address; paired-group group-name; protect-circuit group-name; request; revert-time seconds; working-circuit group-name; bytes { e1-quiet value; f1 value; f2 value; s1 value; z3 value; z4 value; loopback (local | remote); (payload-scrambler | no-payload-scrambler);...
Page 364: Table 25: Atm1 And Atm2 Iq Supported Features
JUNOS 10.1 Network Interfaces Configuration Guide oam-liveness { up-count cells; down-count cells; oam-period (disable | seconds); shaping { (cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst length); transmit-weight number; vci vpi-identifier.vci-identifier; You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit...
Page 365 Chapter 13: Configuring ATM Interfaces Table 25: ATM1 and ATM2 IQ Supported Features (continued) Item ATM1 ATM2 IQ Comments Cell-relay promiscuous port mode: Supported Supported For promiscuous mode, you must configure the port with All cells from 0 through 65,535 of all atm-ccc-cell-relay encapsulation.
Page 366 JUNOS 10.1 Network Interfaces Configuration Guide Table 25: ATM1 and ATM2 IQ Supported Features (continued) Item ATM1 ATM2 IQ Comments Layer 2 circuit cell-relay, Layer 2 Supported Transport mode is per PIC, not per port. If you configure circuit AAL5, and Layer 2 circuit supported Layer 2 circuit cell-relay, Layer 2 circuit AAL5, or Layer 2 trunk transport modes: Allow you to...
Page 367 Chapter 13: Configuring ATM Interfaces Table 25: ATM1 and ATM2 IQ Supported Features (continued) Item ATM1 ATM2 IQ Comments OAM F5 loopback cell responses Supported Supported For ATM1 interfaces, when an OAM F5 loopback request is received, the response cell is sent by the PIC. The request and response cells are not counted in the VC, logical interface, or physical interface statistics.
Page 368 JUNOS 10.1 Network Interfaces Configuration Guide Table 25: ATM1 and ATM2 IQ Supported Features (continued) Item ATM1 ATM2 IQ Comments Shaping rates: Peak and sustained Supported Supported For ATM1 OC3 interfaces, the rate can be from 33 kilobits rates of traffic. per second (Kbps) through 135.6 megabits per second (Mbps);...
Page 369: Example: Configuring Communication With Directly Attached Atm Switches And Routers
Chapter 13: Configuring ATM Interfaces Table 25: ATM1 and ATM2 IQ Supported Features (continued) Item ATM1 ATM2 IQ Comments VCI management Supported Supported For ATM1 interfaces, you must specify the maximum number of VCIs by including the maximum-vcs statement in the configuration.
Page 370: Enabling Ilmi For Cell Relay
JUNOS 10.1 Network Interfaces Configuration Guide at-0/1/0 { atm-options { vpi 0; ilmi; unit 0 { vci 0.120; family inet { address 10.33.33.1/30; Enabling ILMI for Cell Relay The JUNOS Software supports standard AAL5 and three Layer 2 circuit transport modes: Layer 2 circuit AAL5, Layer 2 circuit cell-relay, and Layer 2 circuit trunk transport mode.
Page 371: Example: Enabling Ilmi For Cell Relay
Chapter 13: Configuring ATM Interfaces pic-type atm2; unit logical-unit-number { trunk-id number; For more information about ILMI, see “Configuring Communication with Directly Attached ATM Switches and Routers” on page 299. Example: Enabling ILMI for Cell Relay On an ATM2 IQ PIC with Layer 2 circuit trunk transport mode, enable ILMI on an interface with cell-relay encapsulation: [edit chassis] fpc 0 {...
Page 372: Removing Mpls Labels From Incoming Packets
JUNOS 10.1 Network Interfaces Configuration Guide For conformity with cflowd record structure, you must include the statements at the receive-options-packets receive-ttl-exceeded [edit interfaces mo-fpc/pic/port unit logical-unit-number family inet] hierarchy level: [edit interfaces mo-fpc/pic/port unit logical-unit-number family inet] receive-options-packets; receive-ttl-exceeded; For the monitoring services interface, you can configure multiservice physical interface properties.
Page 373: Configuring The Atm Pic Type
Chapter 13: Configuring ATM Interfaces You use the statement to enable passive monitoring applications, pop-all-labels not active monitoring. You cannot apply MPLS filters or accounting to the MPLS labels because the labels are removed as soon as the packet arrives on the interface. The following ATM encapsulation types are not supported on interfaces with MPLS label removal: atm-ccc-cell-relay...
Page 374: Configuring Atm Cell-Relay Promiscuous Mode
JUNOS 10.1 Network Interfaces Configuration Guide On an ATM1 Interface [edit interfaces] at-1/0/0 { atm-options { pic-type atm1; vpi 0 maximum-vcs 256; vpi 1 maximum-vcs 512; On an ATM2 IQ Interface [edit interfaces] at-1/1/0 { atm-options { pic-type atm2; vpi 0; vpi 2 { oam-period 6;...
Page 375: Examples: Configuring Atm Cell-Relay Promiscuous Mode
Chapter 13: Configuring ATM Interfaces Also, note the following: For promiscuous mode, you must configure the port with atm-ccc-cell-relay encapsulation. For ATM1 and ATM2 IQ PICs, changing modes between promiscuous and nonpromiscuous causes all physical interfaces to be deleted and re-added. For ATM1 and ATM2 IQ PICs, when you configure promiscuous mode, you cannot configure VCIs.
Page 376 JUNOS 10.1 Network Interfaces Configuration Guide unit 0 { encapsulation atm-ccc-cell-relay; # at the logical interface level only vpi 0; unit 1 { encapsulation atm-ccc-cell-relay; vpi 1; unit 2 { encapsulation atm-snap; vci 2.100; unit 3 { encapsulation atm-vc-mux; vci 3.100; To map incoming traffic from a port to an LSP, include the allow-any-vci statement...
Page 377: Configuring The Maximum Number Of Atm1 Vcs On A Vp
Chapter 13: Configuring ATM Interfaces vpi 10; vpi 20; unit 0 { encapsulation atm-ccc-cell-relay; vpi 10; unit 1 { encapsulation atm-ccc-cell-relay; vpi 20; [edit interfaces at-3/1/0] encapsulation atm-ccc-cell-relay; atm-options { pic-type atm2; promiscuous-mode { vpi 10; vpi 20; unit 0 { encapsulation atm-ccc-cell-relay;...
Page 378: Configuring Layer 2 Circuit Transport Mode
JUNOS 10.1 Network Interfaces Configuration Guide maximum-vcs maximum-vcs; The VP identifier can be a value from 0 through 255. For most interfaces, you can define a maximum of 4090 VCs per interface, and some interfaces have higher limits. Promiscuous mode removes these limits. For more information, see “Configuring ATM Cell-Relay Promiscuous Mode”...
Page 379 Chapter 13: Configuring ATM Interfaces into individual ATM cells and forwarded to the ATM virtual circuit configured for the far-end router. The uses for the four transport modes are defined as follows: To tunnel IP packets over an ATM backbone, use the default standard AAL5 transport mode.
Page 380: Examples: Configuring Iq Layer 2 Circuit Transport Mode
JUNOS 10.1 Network Interfaces Configuration Guide For Layer 2 circuit trunk mode only, you must also configure a trunk identification number by including the statement: trunk-id trunk-id number; You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systemslogical-system-name interfaces interface-name unit logical-unit-number] The trunk identification number can be from 0 through 31;...
Page 381 In Figure 19 on page 312, Router A is a local PE router. Router B is a remote PE router. Configuring Layer 2 Both Juniper Networks routers have Layer 2 circuit cell-relay capability. You configure Circuit Trunk Transport an ATM physical interface on Router A in Layer 2 circuit trunk mode and specify Mode trunks that are allowed to send traffic over the LSP.
Page 382: Figure 19: Layer 2 Circuit Trunk Topology
JUNOS 10.1 Network Interfaces Configuration Guide Figure 19: Layer 2 Circuit Trunk Topology [edit chassis] On Router A fpc 0 { pic 1 { atm-l2circuit-mode trunk uni; [edit interfaces] at-0/0/0 { encapsulation atm-ccc-cell-relay; atm-options { pic-type atm2; ilmi; unit 0 { trunk-id 0;...
Page 383 Chapter 13: Configuring ATM Interfaces mtu 9192; unit 0 { family inet { address 10.0.1.1/24; family mpls; lo0 { unit 0 { family inet { address 172.16.0.1/32; address 10.255.245.1/32; [edit protocols] rsvp { interface all; mpls { interface all; ldp { interface all;...
Page 384 JUNOS 10.1 Network Interfaces Configuration Guide interface at-0/1/0.6 { virtual-circuit-id 106; interface at-0/1/0.7 { virtual-circuit-id 107; On Router B [edit chassis] fpc 0 { pic 1 { atm-l2circuit-mode trunk uni; [edit interfaces] at-0/0/1 { encapsulation atm-ccc-cell-relay; atm-options { pic-type atm2; unit 0 { trunk-id 0;...
Page 385 Chapter 13: Configuring ATM Interfaces mtu 9192; unit 0 { family inet { address 10.0.1.2/24; family mpls; lo0 { unit 0 { family inet { address 172.16.0.1/32; address 10.255.245.2/32; [edit protocols] rsvp { interface all; mpls { interface all; ldp { interface all;...
Page 386: Configuring Layer 2 Circuit Cell-Relay Promiscuous Mode
JUNOS 10.1 Network Interfaces Configuration Guide interface at-0/1/0.6 { virtual-circuit-id 106; interface at-0/1/0.7 { virtual-circuit-id 107; Configuring Layer 2 Circuit Cell-Relay Promiscuous Mode By default, all incoming cells are mapped from a single VC to an external LSP. For ATM interfaces with Layer 2 circuit cell-relay transport mode and atm-ccc-cell-relay encapsulation, you can configure promiscuous mode.
Page 387: Configuring Layer 2 Circuit Trunk Mode Scheduling
Chapter 13: Configuring ATM Interfaces Configuring Layer 2 Circuit Trunk Mode Scheduling For ATM2 IQ interfaces configured to use Layer 2 circuit trunk mode, you can share a scheduler among 32 trunks on an ATM port. A weighted round robin scheduling algorithm ensures each trunk receives a proportional share of the bandwidth when all trunks are active, and redistributes bandwidth that would have otherwise been reserved by an inactive trunk, thus minimizing the latency on each trunk.
Page 388: Configuring Cos Queues In Layer 2 Circuit Trunk Mode
JUNOS 10.1 Network Interfaces Configuration Guide ilmi; scheduler-maps { trunk-map { vc-cos-mode strict; forwarding-class cbr-class { priority high; transmit-weight percent 40; epd-threshold 100; forwarding-class rtvbr-class { priority low; transmit-weight percent 30; epd-threshold 100; forwarding-class nrtvbr-class { priority low; transmit-weight percent 20; epd-threshold 100;...
Page 389 Chapter 13: Configuring ATM Interfaces a weighted round robin (WRR) algorithm. One queue is serviced with strictly high priority and the remaining queues are serviced with the WRR. For Layer 2 circuit trunk mode, only strict mode is supported. Alternate mode is not supported.
Page 390: Example: Configuring Cos Queues In Layer 2 Circuit Trunk Mode
JUNOS 10.1 Network Interfaces Configuration Guide Within a single trunk, the maximum latency of a priority queue is the time it high takes to transmit one ATM cell. The latency of a priority queue is the sum of high priority queue burst time and the transmission time of the remaining priority queues weight.
Page 391: Configuring The Layer 2 Circuit Cell-Relay Cell Maximum
Chapter 13: Configuring ATM Interfaces priority low; transmit-weight percent 20; forwarding-class nrtvbr-class { priority low; transmit-weight percent 30; forwarding-class ubr-class { priority low; transmit-weight percent 40; unit 0 { trunk-id 0; trunk-bandwidth 10m; atm-scheduler-map cos0; Configuring the Layer 2 Circuit Cell-Relay Cell Maximum By default, each frame contains one cell.
Page 392: Class-Based Cell Bundling
JUNOS 10.1 Network Interfaces Configuration Guide Class-Based Cell Bundling For Layer 2 circuit trunk mode only, cell bundling is enhanced by a set of CoS and traffic shaping rules, as follows: CBR and real-time variable bit rate (RTVBR) cells are not bundled. They are always sent as single-cell packets.
Page 393 Chapter 13: Configuring ATM Interfaces On each VP, you can configure an interval during which to transmit loopback cells by including the statement at the oam-period [edit interfaces interface-name atm-options vpi vpi-identifier] hierarchy level: [edit interfaces interface-name atm-options vpi vpi-identifier] oam-period (disable | seconds);...
Page 394: Defining Virtual Path Tunnels
JUNOS 10.1 Network Interfaces Configuration Guide Defining Virtual Path Tunnels For ATM2 IQ interfaces, you can configure shaping on a VPI. When you do this, the VPI is called a VP tunnel. If your router is equipped with an ATM2 IQ PIC, you can configure VP tunnels and a weight for each VC.
Page 395: Configuring A Point-To-Multipoint Atm1 Or Atm2 Iq Connection
Chapter 13: Configuring ATM Interfaces configured for the interface with the statement, as described in “Configuring the Maximum Number of ATM1 VCs on a VP” on page 307. VCIs 0 through 31 are reserved for specific ATM values designated by the ATM Forum. ATM2 IQ interfaces support only one invalid VC counter for all ports.
Page 396: Configuring A Multicast-Capable Atm1 Or Atm2 Iq Connection
JUNOS 10.1 Network Interfaces Configuration Guide Configuring a Multicast-Capable ATM1 or ATM2 IQ Connection For ATM1 and ATM2 IQ interfaces, you can configure a multicast-capable connection. By default, ATM connections assume unicast traffic. If your ATM switch performs multicast replication, you can configure the connection to support multicast traffic by including the multicast-vci statement:...
Page 397: Configuring Atm Cbr
Chapter 13: Configuring ATM Interfaces of cells that can be included in a burst, and the long-term sustained ATM cell traffic rate. If your router is equipped with an ATM2 IQ PIC, each VC can have independent shaping parameters. For more information, see “Defining Virtual Path Tunnels” on page 324.
Page 398: Table 27: Shaping Rate Range By Interface Type
JUNOS 10.1 Network Interfaces Configuration Guide Configuring ATM CBR For traffic that does not require the ability to periodically burst to a higher rate, you can specify a constant bit rate (CBR). To specify a CBR on ATM1 and ATM2 IQ interfaces, include the statement: cbr rate;...
Page 399 Chapter 13: Configuring ATM Interfaces rtvbr peak rate sustained rate burst length; For a list of hierarchy levels at which you can include this statement, see rtvbr. When configuring RTVBR, you can define the following shaping properties: Peak rate—Top rate at which traffic can burst. Sustained rate—Normal traffic rate averaged over time.
Page 400 JUNOS 10.1 Network Interfaces Configuration Guide reason for this is that fractional shaping is ignored at rates below 1/127. This results in a total of about 32,384 distinct rates for OC12c. When n is larger than or equal to 127, the steps are 1/n. For OC3c, the starting point is full line rate, the fraction/integer breakpoint is about 1/31, and there is a maximum of 4096 scheduler slots for use after 1/31 of line rate, producing about 8032 total distinct rates.
Page 401: Example: Specifying Atm1 Shaping Values
Chapter 13: Configuring ATM Interfaces Table 28: ATM1 Traffic-Shaping Rates Percentage of Total Interface Type Line Rate (bps) Line Rate (cps) Line Rate 135,600,000 353,125 100.00 134,542,320 350,370.66 99.22 133,511,760 347,686.88 98.46 132,494,760 345,038.44 97.71 131,491,320 342,425.31 96.97 130,501,440 339,847.5 96.24 129,525,120 337,305...
Page 402: Specifying Atm2 Iq Shaping Values
JUNOS 10.1 Network Interfaces Configuration Guide Because 108,480,000 bps is greater than 1/31 of OC3 ATM cell line rate: actual-rate = (128 * 135,600,000.1) / (trunc ((128 * 135,600,000.1) / 108,480,000)) actual-rate = 17,356,800,013 / (trunc (17,356,800,013 / 108,480,000)) actual-rate = 17,356,800,013 / 160 actual-rate = 108,480,000 bps OC12c: 271,263,396 bps * 0.8 = 217,010,716.8 bps...
Page 403: Configuring The Atm1 Queue Length
Chapter 13: Configuring ATM Interfaces Configuring the ATM1 Queue Length ATM1 PICs contain a transmit buffer pool of 16,382 buffers, which are shared by all the PVCs that you configure on the PIC. Even multiple-port ATM PICs have a single buffer pool shared by all the ports.
Page 404: Configuring The Atm2 Iq Epd Threshold
JUNOS 10.1 Network Interfaces Configuration Guide and the physical interface MTU. You can use the following formula to calculate the maximum lifetime that packets can sustain while transiting a PVC: ( PVC queue-length in packets x MTU ) / ( PVC shaping in bps / 8 ) For example, if you configure a PVC on an ATM1 interface with the default MTU, a CBR shaping rate of 3,840,000 bps (10,000 cps), and a queue length of 25 packets.
Page 405: Example: Configuring The Atm2 Iq Epd Threshold
Chapter 13: Configuring ATM Interfaces Table 29: EPD Threshold Range by Interface Type Interface Type EPD Range 1-port OC48 48 through 425,984 cells 1-port and 2-port OC12 48 through 425,984 cells 2-port OC3, DS3, and E3 48 through 212,992 cells 4-port DS3 and E3 48 through 106,496 cells You should include the...
Page 406: Configuring Two Epd Thresholds Per Queue
JUNOS 10.1 Network Interfaces Configuration Guide Configuring Two EPD Thresholds per Queue For ATM2 IQ interfaces configured to use Layer 2 circuit trunk mode, you can set two EPD thresholds that depend on the PLPs of the packets. When you set a threshold with the epd-threshold statement, it applies to packets that have a PLP of 0.
Page 407: Defining The Atm Oam F5 Loopback Cell Period
Chapter 13: Configuring ATM Interfaces The number of cells can be from 1 through 32,000. For a configuration example, see “Example: Configuring ATM2 IQ Interfaces” on page 360. Defining the ATM OAM F5 Loopback Cell Period For ATM1 and ATM2 IQ interfaces with an ATM encapsulation, you can configure the OAM F5 loopback cell period on virtual circuits.
Page 408: Configuring Atm Interface Encapsulation
JUNOS 10.1 Network Interfaces Configuration Guide Configuring ATM Interface Encapsulation To configure ATM encapsulation on a physical interface, include the encapsulation statement at the hierarchy level: [edit interfaces interface-name] [edit interfaces interface-name] encapsulation (atm-ccc-cell-relay | atm-pvc | ethernet-over-atm); For ATM interfaces, the physical interface encapsulation can be one of the following: ATM cell-relay—This encapsulation connects two remote virtual circuits or ATM physical interfaces with an LSP.
Page 409: Table 30: Atm Logical Interface Encapsulation Types
Chapter 13: Configuring ATM Interfaces Table 30: ATM Logical Interface Encapsulation Types Encapsulation Types Comments ATM CCC cell relay This encapsulation type connects two remote virtual circuits or ATM physical interfaces with an LSP. This encapsulation type carries traffic in ATM cells. When you use this encapsulation type, you can configure the family only.
Page 410: Configuring An Atm1 Cell-Relay Circuit
JUNOS 10.1 Network Interfaces Configuration Guide Table 30: ATM Logical Interface Encapsulation Types (continued) Encapsulation Types Comments PPP over AAL5 LLC This encapsulation type is for ATM2 IQ interfaces only. When you use this encapsulation type, you cannot configure point-to-multipoint interfaces.
Page 411 Chapter 13: Configuring ATM Interfaces atm-options { pic-type atm1; vpi 0 maximum-vcs 256; unit 0 { point-to-point; encapsulation atm-ccc-cell-relay; allow-any-vci; [edit interfaces at-1/1/0] Configuring an Individual encapsulation atm-ccc-cell-relay; VC on a Logical atm-options { Interface pic-type atm1; vpi 0 maximum-vcs 256; unit 120 { encapsulation atm-ccc-cell-relay;...
Page 412: Configuring Ppp Over Atm2 Encapsulation
JUNOS 10.1 Network Interfaces Configuration Guide Configuring [edit interfaces at-0/0/1] encapsulation atm-ccc-cell-relay; Nonpromiscuous VCI atm-options { Mode pic-type atm1; vpi 0 { maximum-vcs 100; unit 0 { encapsulation atm-ccc-cell-relay; vci 0.50 Configuring PPP over ATM2 Encapsulation For ATM2 IQ interfaces, you can configure PPP over AAL5 encapsulation, as described in RFC 2364, PPP over AAL5.
Page 413: Example: Configuring Ppp Over Atm2 Iq Encapsulation
Chapter 13: Configuring ATM Interfaces Example: Configuring PPP over ATM2 IQ Encapsulation Configure three logical interfaces with PPP over ATM encapsulation: [edit interfaces] at-0/1/0 { atm-options { pic-type atm2; vpi 0; vpi 2; unit 0 { encapsulation atm-ppp-llc; ppp-options { chap { access-profile pe-B-ppp-clients;...
Page 414 JUNOS 10.1 Network Interfaces Configuration Guide access-profile pe-B-ppp-clients; local-name “ pe-A-at-0/0/0”; keepalive interval 5 up-count 6 down-count 4; vci 10.120; family mlppp { bundle ls-0/3/0.0; at-0/0/1 { atm-options { pic-type atm2; vpi 11; unit 1 { encapsulation atm-mlppp-llc; ppp-options { chap { access-profile pe-B-ppp-clients;...
Page 415: Configuring E3 And T3 Parameters On Atm Interfaces
Chapter 13: Configuring ATM Interfaces unit 0 { mrru 4500; short-sequence; fragment-threshold 16320; drop-timeout 2000; encapsulation multilink-ppp; interleave-fragments; minimum-links 8; family inet { address 10.10.0.1/32 { destination 10.10.0.2; family iso; family inet6 { address 8090::0:1/128 { destination 8090::0:2; Configuring E3 and T3 Parameters on ATM Interfaces For ATM1 and ATM2 IQ interfaces, you can configure ATM E3 and T3 interfaces by including the following statements at the hierarchy...
Page 416: Configuring Sonet/Sdh Parameters On Atm Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide —There is no default option for E3 interfaces; T3 interfaces use the framing cbit-parity statement in place of the framing statement. —By default, loopback is disabled. loopback payload-scrambler —The default option is to enable payload scrambling. In addition, the ATM E3 and T3 PICs support the statement at the interface clocking...
Page 417: Configuring Atm2 Iq Vc Tunnel Cos Components
Chapter 13: Configuring ATM Interfaces (z0-increment | no-z0-increment); For information about configuring specific SONET/SDH statements, see “SONET/SDH Interfaces Overview” on page 895. Configuring ATM2 IQ VC Tunnel CoS Components The ATM2 IQ interface allows multiple IP queues into each VC. On M Series routers (except the M320 and M120 router), a VC tunnel can support four CoS queues.
Page 418 JUNOS 10.1 Network Interfaces Configuration Guide vci vpi-identifier.vci-identifier; This section contains the following topics: Configuring Linear RED Profiles on page 348 Configuring an ATM Scheduler Map on page 349 Enabling Eight Queues on ATM2 IQ Interfaces on page 350 Configuring VC CoS Mode on page 356 Enabling the PLP Setting to Be Copied to the CLP Bit on page 356 Configuring ATM CoS on the Logical Interface on page 357 Example: Configuring ATM2 IQ VC Tunnel CoS Components on page 357...
Page 419 Chapter 13: Configuring ATM Interfaces —Define CoS VC drop profile fill-level percentage when linear high-plp-threshold RED is applied to cells with high PLP. When the fill level exceeds the defined percentage, packets with high PLP are randomly dropped by RED. low-plp-threshold —Define CoS VC drop profile fill-level percentage when linear RED is applied to cells with low PLP.
Page 420 JUNOS 10.1 Network Interfaces Configuration Guide By default, if you include the statement at the scheduler-maps [edit interfaces at-fpc/pic/port atm-options] hierarchy level, the interface uses an EPD threshold that is determined by the JUNOS Software based on the available bandwidth and other parameters.
Page 421: Example: Enabling Eight Queues On T Series, M120, And M320 Platforms
Chapter 13: Configuring ATM Interfaces When you include the statement and commit the max-queues-per-interface configuration, all physical interfaces on the ATM2 IQ PIC are deleted and re-added. Also, the PIC is taken offline and then brought back online immediately. You do not need to manually take the PIC offline and online.
Page 422 JUNOS 10.1 Network Interfaces Configuration Guide [edit chassis] fpc 0 { pic 1 { max-queues-per-interface 8; fpc 6 { pic 1 { max-queues-per-interface 8; [edit interfaces] at-0/1/0 { atm-options { linear-red-profiles { red_1 queue-depth 1k high-plp-threshold 50 low-plp-threshold 80; red_2 queue-depth 2k high-plp-threshold 40 low-plp-threshold 70; red_3 queue-depth 3k high-plp-threshold 30 low-plp-threshold 60;...
Page 423 Chapter 13: Configuring ATM Interfaces linear-red-profile red_3; forwarding-class fc_q7 { priority low; transmit-weight percent 20; linear-red-profile red_4; sch_epd { vc-cos-mode alternate; forwarding-class fc_q0 { priority high; transmit-weight percent 5; epd-threshold 1024; forwarding-class fc_q1 { priority low; transmit-weight percent 10; epd-threshold 2048; forwarding-class fc_q2 { priority low;...
Page 424 JUNOS 10.1 Network Interfaces Configuration Guide unit 0 { vci 0.100; shaping { cbr 1920000; atm-scheduler-map sch_red; family inet { address 172.16.0.1/24; unit 1 { vci 0.101; shaping { vbr peak 1m sustained 384k burst 256; atm-scheduler-map sch_epd; family inet { address 172.16.1.1/24;...
Page 425 Chapter 13: Configuring ATM Interfaces forwarding-class fc_q5 { loss-priority low code-points 101; forwarding-class fc_q6 { loss-priority low code-points 110; forwarding-class fc_q7 { loss-priority low code-points 111; forwarding-classes { queue 0 fc_q0; queue 1 fc_q1; queue 2 fc_q2; queue 3 fc_q3; queue 4 fc_q4;...
Page 426: Configuring Vc Cos Mode
JUNOS 10.1 Network Interfaces Configuration Guide To see the results of this configuration, you can issue the following operational mode Verifying the commands: Configuration show interfaces at-0/1/0 extensive show interfaces queue at-0/1/0 show class-of-service forwarding-class Configuring VC CoS Mode VC CoS mode defines the CoS queue scheduling priority. By default, the VC CoS mode is alternate.
Page 427: Configuring Atm Cos On The Logical Interface
Chapter 13: Configuring ATM Interfaces You can enable the PLP information to be copied into the CLP bit by including the statement: plp-to-clp plp-to-clp; You can include this statement at the following hierarchy levels: [edit interfaces interface-name atm-options] [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] Configuring ATM CoS on the Logical Interface...
Page 428: Example: Configuring Atm1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide vc-cos-mode strict; forwarding-class best-effort { priority low; transmit-weight percent 25; linear-red-profile red-profile-1; unit 0 { vci 0.128; shaping { vbr peak 20m sustained 10m burst 20; atm-scheduler-map map-1; family inet { address 192.168.0.100/32 { destination 192.168.0.101;...
Page 429 Chapter 13: Configuring ATM Interfaces address 192.168.0.3/32 { destination 192.168.0.1; unit 3 { encapsulation atm-snap; vci 0.32; oam-period 60; family inet { mtu 1500; address 192.168.4.3/32 { destination 192.168.4.2; at-0/2/0 { encapsulation atm-pvc; atm-options { vpi 0 maximum-vcs 1200; unit 2 { encapsulation atm-snap;...
Page 430: Example: Configuring Atm2 Iq Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide unit 0 { encapsulation atm-snap; vci 0.32; family inet { address 192.168.12.3/32 { destination 192.168.12.2; Example: Configuring ATM2 IQ Interfaces Configure VP tunnel-shaping and OAM F4 on an ATM2 IQ interface: interfaces { at-5/2/0 { atm-options { vpi 0 { shaping {...
Page 431 Chapter 13: Configuring ATM Interfaces family inet { address 192.168.9.226/32 { destination 192.168.9.227; unit 2 { vci 5.123; shaping { vbr peak 60m sustained 4m burst 24; family inet { address 192.168.9.227/32 { destination 192.168.9.230; Example: Configuring ATM2 IQ Interfaces...
Page 432 JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring ATM2 IQ Interfaces...
Page 433: Configuring Atm-Over-Adsl Interfaces
Chapter 14 Configuring ATM-over-ADSL Interfaces ATM-over-ADSL Overview on page 363 Configuring Physical ATM Interfaces and Logical Interface Properties for ADSL on page 364 Configuring the ATM-over-ADSL Virtual Path Identifier on page 365 Configuring the ATM-over-ADSL Physical Interface Operating Mode on page 365 Configuring the ATM-over-ADSL Physical Interface Encapsulation Type on page 366 Configuring the ATM-over-ADSL Logical Interface Encapsulation Type on page 366 Configuring the ATM-over-ADSL Protocol Family on page 367...
Page 434 JUNOS 10.1 Network Interfaces Configuration Guide When you configure a point-to-point encapsulation such as PPP on a physical interface, the physical interface can have only one logical interface (only one statement) unit associated with it. For more information about configuring PPPoE, see “Configuring PPPoE” on page 830. Related Topics Configuring Physical ATM Interfaces and Logical Interface Properties for ADSL To configure physical ATM interfaces for ADSL, include the...
Page 435: Table 31: Atm-Over-Adsl Operational Modes
Chapter 14: Configuring ATM-over-ADSL Interfaces Configuring the ATM-over-ADSL Protocol Family on page 367 Configuring the ATM-over-ADSL Virtual Channel Identifier on page 368 Configuring the ATM-over-ADSL Virtual Path Identifier Set the ATM virtual path identifier (VPI) to 0 (zero) by including the statement vpi 0 at the...
Page 436 JUNOS 10.1 Network Interfaces Configuration Guide Table 31: ATM-over-ADSL Operational Modes (continued) Encapsulation Types Comments Annex B PIMs Set the ADSL line to train in the ITU G.992.5 mode. adsl2plus Set the ADSL line after autonegotiating the setting to auto match the setting of the DSLAM located at the central office.
Page 437: Table 32: Atm-Over-Adsl Encapsulation Types
Chapter 14: Configuring ATM-over-ADSL Interfaces Table 32: ATM-over-ADSL Encapsulation Types Encapsulation Types Comments Physical Interface Ethernet over ATM encapsulation. ether-over-atm Use this type of encapsulation for interfaces that carry IPv4 traffic. ATM permanent virtual circuits (PVCs). atm-pvc Logical Interface Use ATM VC multiplex encapsulation. atm-vc-mux You can only configure the inet...
Page 438 JUNOS 10.1 Network Interfaces Configuration Guide You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] Configuring the ATM-over-ADSL Virtual Channel Identifier Configure the virtual channel identifier (VCI) type and value by including the statement: [edit interfaces at-pim/0/port unit logical-unit-number] vci vpi-identifier.vci-identifier;...
Page 439: Configuring Atm-Over-Shdsl Interfaces
Chapter 15 Configuring ATM-over-SHDSL Interfaces ATM-over-SHDSL Overview on page 369 Configuring ATM Mode for SHDSL Overview on page 370 Configuring ATM Mode on the PIM on page 371 Configuring SHDSL Operating Mode on an ATM Physical Interface on page 372 Configuring Encapsulation on the ATM Physical Interface on page 372 Configuring Logical Interface Properties on page 373 Example: Configuring an ATM-over-SHDSL Interface on page 374...
Page 440 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: You can configure J Series routers with SHDSL PIMs for connections through SHDSL only, not for direct ATM connections. Related Topics Configuring ATM Mode for SHDSL Overview To configure the ATM mode for SHDSL, include the pic-mode statement at the [edit...
Page 441 Chapter 15: Configuring ATM-over-SHDSL Interfaces For more information about configuring ATM VPI options, see “Configuring the Maximum Number of ATM1 VCs on a VP” on page 307. To configure logical interface properties, include the encapsulation statement, family statement, and statement: unit logical-unit-number { encapsulation type;...
Page 442 JUNOS 10.1 Network Interfaces Configuration Guide For more information about configuring the statement, see the JUNOS pic-mode System Basics Configuration Guide. For information about configuring the ATM mode, see the JUNOS Software Interfaces and Routing Configuration Guide. Configuring SHDSL Operating Mode on an ATM Physical Interface To configure the SHDSL operating mode on the physical ATM interface, include the statement at the hierarchy level:...
Page 443 Chapter 15: Configuring ATM-over-SHDSL Interfaces encapsulation (atm-pvc | ether-over-atm); Configure one of the following: —ATM permanent virtual circuits (PVCs), used for PPP over ATM over atm-pvc SHDSL interfaces. This is the default encapsulation. ether-over-atm —Ethernet over ATM encapsulation. For interfaces that carry IPv4 traffic, use this type of encapsulation.
Page 444 JUNOS 10.1 Network Interfaces Configuration Guide —Use ATM subnetwork attachment point (SNAP) encapsulation. atm-snap atm-mlppp-llc —For ATM2 IQ interfaces only, use Multilink PPP (MLPPP) over AAL5 LLC. For this encapsulation type, your router must be equipped with a Link Services or Voice Services PIC. MLPPP over ATM encapsulation is not supported on ATM2 IQ OC48 interfaces.
Page 445 Chapter 15: Configuring ATM-over-SHDSL Interfaces Configuration for the [edit interfaces at-6/0/0/0 unit 3] encapsulation atm-nlpid; Logical Interface family inet { vci 25; Verifying an ATM-over-SHDSL Interface Configuration To verify an ATM-over-SHDSL interface configuration, you can issue the following operational mode command: user@host>...
Page 446 JUNOS 10.1 Network Interfaces Configuration Guide Verifying an ATM-over-SHDSL Interface Configuration...
Page 447: Configuring Frame Relay
Part 6 Configuring Frame Relay Configuring Frame Relay on page 379 Configuring Frame Relay...
Page 448 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Frame Relay...
Page 449: Frame Relay Overview
Chapter 16 Configuring Frame Relay Frame Relay Overview on page 379 Configuring Frame Relay Interface Encapsulation on page 380 Configuring Frame Relay Control Bit Translation on page 383 Configuring the Media MTU on Frame Relay Interfaces on page 384 Setting the Protocol MTU with Frame Relay Encapsulation on page 385 Configuring Frame Relay Keepalives on page 385 Configuring Inverse Frame Relay ARP on page 387 Configuring the Router as a DCE with Frame Relay Encapsulation on page 388...
Page 450: Configuring The Frame Relay Encapsulation On A Physical Interface
JUNOS 10.1 Network Interfaces Configuration Guide Configuring Frame Relay Interface Encapsulation Point-to-Point Protocol (PPP) encapsulation is the default encapsulation type for physical interfaces. You need not configure encapsulation for any physical interfaces that support PPP encapsulation. If you do not configure encapsulation, PPP is used by default.
Page 451: Table 33: Pic Support For Enhanced Frame Relay Encapsulation Types
Chapter 16: Configuring Frame Relay Extended CCC version ( )—This encapsulation type extended-frame-relay-ccc allows you to dedicate DLCIs 1 through 1022 to CCC. The logical interface must have frame-relay-ccc encapsulation. When you use this encapsulation type, you can configure the family only.
Page 452: Example: Configuring The Encapsulation On A Physical Interface
JUNOS 10.1 Network Interfaces Configuration Guide Table 33: PIC Support for Enhanced Frame Relay Encapsulation Types (continued) Extended Frame Extended Frame Flexible Frame PIC Type Relay CCC Relay TCC Relay 4-port Channelized DS3 IQ 10-port Channelized E1 IQ 4-port E3 IQ 1-port Channelized STM1 IQ SONET/SDH 1-port OC12...
Page 453: Configuring The Frame Relay Encapsulation On A Logical Interface
Chapter 16: Configuring Frame Relay address 192.168.1.113/32 { destination 192.168.1.114; family iso; family mpls; Configuring the Frame Relay Encapsulation on a Logical Interface Generally, you configure an interface s encapsulation at the [edit interfaces hierarchy level. However, for Frame Relay encapsulation, you can interface-name] also configure the encapsulation type that is used inside the Frame Relay packet itself.
Page 454: Configuring The Media Mtu On Frame Relay Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Backward explicit congestion notification (BECN)—A header bit transmitted by the destination router requesting that the source router send data more slowly. By default, translation of Frame Relay control bits is disabled. If you enable Frame Relay control bit translation, the bits are translated in both directions (CE to PE and PE to CE): From CE to PE—At ingress, the DE, FECN, and BECN header bits from the...
Page 455: Setting The Protocol Mtu With Frame Relay Encapsulation
Chapter 16: Configuring Frame Relay To modify the default media MTU size for a physical interface, include the statement at the [edit interfaces interface-name] hierarchy level: [edit interfaces interface-name] mtu bytes; If you change the size of the media MTU, you must ensure that the size is equal to or greater than the sum of the protocol MTU and the encapsulation overhead.
Page 456: Configuring Tunable Keepalives For Frame Relay Lmi
JUNOS 10.1 Network Interfaces Configuration Guide To disable the sending of keepalives on a physical interface, include the no-keepalives statement at the [edit interfaces interface interface-name] hierarchy level: [edit interfaces interface-name] no-keepalives; For back-to-back Frame Relay connections, either disable the sending of keepalives on both sides of the connection, or configure one side of the connection as a data terminal equipment (DTE) (the default JUNOS configuration) and the other as a data circuit-terminating equipment (DCE).
Page 457: Configuring Inverse Frame Relay Arp
Chapter 16: Configuring Frame Relay You can include the following statements: —DTE full status polling interval. The DTE sends a status inquiry to the n391dte DCE at the interval specified by t391dte n391dte specifies the frequency at which these inquiries expect a full status report; for example, a value n391dte of 10 would specify a full status report in response to every tenth inquiry.
Page 458: Configuring The Router As A Dce With Frame Relay Encapsulation
JUNOS 10.1 Network Interfaces Configuration Guide Configuring the Router as a DCE with Frame Relay Encapsulation By default, when you configure an interface with Frame Relay encapsulation, the routing platform is assumed to be DTE. That is, the routing platform is assumed to be at a terminal point on the network.
Page 459: Configuring A Multicast-Capable Frame Relay Connection
Chapter 16: Configuring Frame Relay NOTE: For information about Frame Relay DLCI limitations for channelized interfaces, see “Data-Link Connection Identifiers on Channelized Interfaces” on page 396. You configure the router to use DLCI sparse mode by including the sparse-dlcis statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level.
Page 460 JUNOS 10.1 Network Interfaces Configuration Guide [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] The DLCI identifier is a value from 16 through 1022 that defines the Frame Relay DLCI over which the switch expects to receive multicast packets for replication. You can configure multicast support only on point-to-multipoint Frame Relay connections.
Page 461: Configuring Channelized Interfaces
Part 7 Configuring Channelized Interfaces Channelized Interfaces on page 393 Configuring Channelized OC48/STM16 IQE Interfaces on page 413 Configuring Channelized OC12/STM4 Interfaces on page 431 Configuring Channelized OC3 IQ and IQE Interfaces on page 463 Configuring Channelized STM1 Interfaces on page 473 Configuring Channelized T3 Interfaces on page 489 Configuring Channelized T1 Interfaces on page 505 Configuring Channelized E1 Interfaces on page 511...
Page 462 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Channelized Interfaces...
Page 463: Channelized Interfaces
Chapter 17 Channelized Interfaces This section provides a high-level overview of channelized interfaces, focusing mainly on the capabilities, properties, and structure of channelized IQ and IQE interfaces, and includes the following topics: Channelized Interfaces Overview on page 393 Channelized Interface Capabilities on page 394 Data-Link Connection Identifiers on Channelized Interfaces on page 396 Clock Sources on Channelized Interfaces on page 398 Channelized E1 and T1 PIM Properties on page 401...
Page 464 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: Channelized intelligent queuing (IQ) and channelized enhanced intelligent queuing (IQE) interfaces require M Series Enhanced Flexible PIC Concentrators (FPCs) and MX Series Enhanced Flexible PIC Concentrators (FPCs). Wherever JUNOS configuration guides refer to channelized interfaces and PICs without the “intelligent queuing IQ or IQE”...
Page 465 Chapter 17: Channelized Interfaces This section lists the channelized interface names. Channelized Interface Names —Channelized OC48 IQE interface. Configure on a Channelized coc48-fpc/pic/port OC48 IQE PIC. coc12-fpc/pic/port —Channelized OC12 interface. Configure on Channelized OC12 IQ or IQE PICs. —Channelized OC3 interface. Configure on Channelized coc3-fpc/pic/port:channel OC3 IQ or IQE, Channelized OC12 IQ or IQE PICs.
Page 466: Table 34: Frame Relay Dlci Limitations For Channelized Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide on Channelized OC48 IQE, or one STM1 channel on a Channelized STM1 IQ or IQE PICs. —T1 channel. Configure on Channelized T1 IQ or IQE, t1-fpc/pic/port:channel Channelized OC3 IQ or IQE, Channelized OC12 IQ or IQE, Channelized OC48 IQE, or Channelized DS3 IQ or IQE PICs.
Page 467: Table 35: Per Unit Scheduler Dlci Limitations For Channelized
Chapter 17: Channelized Interfaces Table 34: Frame Relay DLCI Limitations for Channelized Interfaces (continued) Number of DLCIs PIC Types per Level Range E1 level channels (Channelized STM1 IQ or IQE PIC) 1–1022 (0 is reserved for the LMI) OC3 level channels (Channelized OC3 IQ or IQE, or Channelized 1022 1–1022 (0 is reserved for the LMI) OC12 IQ or IQE PIC)
Page 468 JUNOS 10.1 Network Interfaces Configuration Guide Table 36: Protocol Family Combinations (continued) Protocol Family Combinations Number of DLCIs per PIC inet, inet6 2400 inet, mpls 2000 inet6, mpls 2000 inet, inet6, mpls 1550 Clock Sources on Channelized Interfaces Channelized interfaces and channelized IQ and IQE interfaces have different clocking capabilities.
Page 469: Table 37: Clocking Capabilities By Channelized Pic Type
Chapter 17: Channelized Interfaces For Channelized OC12, DS3, and E1 PICs, the statement is supported clocking only for channel 0; it is ignored if included in the configuration of other channels. The clock source configured for channel 0 applies to all channels on these channelized interfaces.
Page 470 JUNOS 10.1 Network Interfaces Configuration Guide Table 37: Clocking Capabilities by Channelized PIC Type (continued) PIC Type SONET/SDH Level DS3 Level DS1/E1 Level Channelized DS3 Not applicable. statement is For T1 channels, the clocking clocking IQ or IQE supported at the [edit interfaces statement is supported at the [edit...
Page 471 Chapter 17: Channelized Interfaces Table 37: Clocking Capabilities by Channelized PIC Type (continued) PIC Type SONET/SDH Level DS3 Level DS1/E1 Level Channelized statement is Not applicable. For E1 and NxDS0 channels, the clocking STM1 IQ or IQE supported at the [edit interfaces clocking statement is supported at...
Page 472 JUNOS 10.1 Network Interfaces Configuration Guide E1 and T1 time slots unused by ISDN PRI can operate normally as DS0 interfaces. PRI B-channels run at 64 Kbps, but do not support the 56-Kbps line rate. For more information about Channelized E1 PIMs, ISDN PRI connectivity, and the ISDN features they support, see the JUNOS Software Interfaces and Routing Configuration Guide.
Page 473 For channelized interfaces, you can configure class of service (CoS) on channels, but not at the controller level. For original Channelized OC12 PICs, limited CoS functionality is supported. For more information, contact Juniper Networks customer support. CoS is not configurable on controller interfaces. Structure of Channelized IQ and Channelized IQE PICs Figure 21 on page 404 through Figure 33 on page 409 show the structural organization of the channelized PICs, channelized IQ PICs, and channelized IQE PICs.
Page 474: Figure 21: Channelized Oc48/Stm16 Iqe Pic (In Sonet Mode)
JUNOS 10.1 Network Interfaces Configuration Guide on page 410 through Table 40 on page 412 show the structure of channelized IQE PICs, channelized IQ PICs, and channelized PICs. Figure 21: Channelized OC48/STM16 IQE PIC (in SONET Mode) SONET transport layer: -coc48-fpc/pic/port SONET path layer: OC12 and OC3 path layer :...
Page 475: Figure 23: Channelized Oc12 Iq Pic And Channelized Oc12/Stm4 Iqe Pic
Chapter 17: Channelized Interfaces Figure 23: Channelized OC12 IQ PIC and Channelized OC12/STM4 IQE PIC (in SONET Mode) SONET transport layer: -coc12-fpc/pic/port Clear-channel path layer SONET path layer: OC12 and OC3: -coc1-fpc/pic/port:[1-12] -so-fpc/pic/port M13-mapped CT3: VT-mapped CT1: VT-mapped T1: Clear-chan. T3: -ct3-fpc/pic/port: -ct1-fpc/pic/port: -t1-fpc/pic/port:...
Page 476: Figure 25: Channelized Oc12/Stm4 Iq Pic (In Sdh Mode)
JUNOS 10.1 Network Interfaces Configuration Guide Figure 25: Channelized OC12/STM4 IQ PIC (in SDH Mode) SDH transport layer: -cstm4-fpc/pic/port SDH path layer: STM1 and STM4: -cau4-fpc/pic/port -so-fpc/pic/port [1:4] CT3: -ct3- fpc/pic/port: -t3- fpc/pic/port: [1-4]:[1-3] [1-4]:[1-3] CT1: -ct1- fpc/pic/port: -t1- fpc/pic/port: [1-4]:[1-3]:[1-28] [1-4]:[1-3]:[1-28] HDLC...
Page 477: Figure 27: Channelized Cstm1 Ports (In Sdh Mode) On Channelized
Chapter 17: Channelized Interfaces Figure 27: Channelized CSTM1 Ports (in SDH Mode) on Channelized OC3/STM1 IQE PIC SDH transport layer: -cstm1-fpc/pic/port Clear-channel path SDH path layer: layer STM1: -cau4-fpc/pic/port -so- fpc/pic/port NxDS0: -ds- fpc/pic/port [1-63]:[1-31] HDLC Figure 28: Channelized STM1 IQ PIC SDH transport layer: -cstm1-fpc/pic/port SDH path layer:...
Page 478: Figure 29: Channelized Cds3/E3 Iqe Pic (In Ds3 Mode)
JUNOS 10.1 Network Interfaces Configuration Guide Figure 29: Channelized CDS3/E3 IQE PIC (in DS3 Mode) CDS3 IQE (per port) CT3: cte-fpc/pic/port CT1: ct1-fpc/pic/port t1-fpc/pic/port t3-fpc/pic/port :[1-28] :[1-28] NxDS0: ds-fpc/pic/port :[1-28]:[1-24] Figure 30: Channelized CDS3/E3 IQE PIC (in E3 Mode) E3 IQE (per port) e3-fpc/pic/port Figure 31: Channelized DS3 IQ PIC CDS3 IQ...
Page 479: Figure 33: Channelized E1 Iq And Iqe Pic
Chapter 17: Channelized Interfaces Figure 33: Channelized E1 IQ and IQE PIC E1 IQ and IQE Structure of Channelized IQ and Channelized IQE PICs...
Page 480: Table 38: Structural Differences: Channelized Iqe Pics
JUNOS 10.1 Network Interfaces Configuration Guide Table 38: Structural Differences: Channelized IQE PICs PIC Type Transport Path DS1/E1 Channelized IQE PICs Channelized Not applicable. coc48-fpc/pic/port coc1-fpc/pic/port ct3-fpc/pic/port ct1-fpc/pic/port OC48/STM16 :[1-48] :[1-48] :[1-48]:[1-28] IQE (SONET Mode) so-fpc/pic/port t3-fpc/pic/port t1-fpc/pic/port :[1-48] :[1-48]:[1-28] Channelized cstm16-fpc/pic/port cau4-fpc/pic/port...
Page 481: Table 39: Structural Differences: Channelized Iq Pics
Chapter 17: Channelized Interfaces Table 38: Structural Differences: Channelized IQE PICs (continued) PIC Type Transport Path DS1/E1 Channelized DS3 Not applicable. Not applicable. Not applicable. ct3-fpc/pic/port ct1-fpc/pic/port :[1-28] t3-fpc/pic/port t1-fpc/pic/port :[1-28] Channelized E3 Not applicable. Not applicable. Not applicable. Not applicable. e3-fpc/pic/port :[1:4] Channelized T1...
Page 482: Table 40: Structural Differences: Channelized Pics
JUNOS 10.1 Network Interfaces Configuration Guide Table 39: Structural Differences: Channelized IQ PICs (continued) PIC Type Transport Path DS1/E1 Channelized E1 Not applicable. Not applicable. Not applicable. Not applicable. ce1-fpc/pic/port e1-fpc/pic/port Table 40: Structural Differences: Channelized PICs PIC Type Transport Path DS1/E1 Channelized PICs...
Page 483: Channelized Oc48/Stm16 Iqe Interfaces Overview
Chapter 18 Configuring Channelized OC48/STM16 IQE Interfaces Channelized OC48/STM16 IQE Interfaces Overview on page 413 Configuring Channelized OC48/STM16 IQE Interfaces in SONET Mode on page 415 Configuring Channelized OC48/STM16 IQE Interfaces (SDH Mode) on page 423 Configuring Link PIC Failover on Channelized OC48/STM16 IQE Interfaces on page 428 Example: Configuring Channelized OC48 Interfaces with Partitioned Channels on page 429...
Page 484: Figure 35: Sample Channelization Of Oc48/Stm16 Iqe Pic (Sdh Mode)
JUNOS 10.1 Network Interfaces Configuration Guide A channelized COC1 partitioned into T1 interfaces. d. A channelized COC1 partitioned into a T3 interface. e. A channelized COC1 partitioned into CT3, partitioned into T1 interfaces, and CT1s partitioned into NxDS0 interfaces. A channelized COC1 partitioned into CT3, partitioned into T1 interfaces. g.
Page 485: Configuring Channelized Oc48/Stm16 Iqe Interfaces In Sonet Mode
Chapter 18: Configuring Channelized OC48/STM16 IQE Interfaces Figure 36: Sample Channelization of OC48/STM16 IQE PIC to E3 Channels OC48/STM16 supports up to 48 E3s Figure 36 on page 415 shows five E3 channels configured on the Channelized OC48/STM16 IQE PIC. You can configure 43 additional E3 channels. For more information about configuring E3 channels on Channelized OC48/STM16 IQE PICs, see “Configuring E3 Interfaces”...
Page 486: Example: Configuring Oc12 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide 25–26 37–48 By contrast, the T3 and OC1 interfaces each occupy one OC slice per interface and OC3 interfaces occupy three slices per interface. The interface type is the channelized interface type or data channel you are creating. For channelized OC48 IQE interfaces, the interface type can be Example: Configuring OC12 Interfaces Configure an OC12 interface, using partition 1 and OC slices 1 through 12.
Page 487: Example: Configuring Oc3 Interfaces
Chapter 18: Configuring Channelized OC48/STM16 IQE Interfaces The interface type is the channelized interface type or data channel you are creating. For channelized OC48 IQE interfaces, the interface type can be Example: Configuring OC3 Interfaces Configure an OC3 interface, using partition 1 and OC slices 4 through 6. This configuration creates interface so-1/1/0:1 [edit interfaces coc48-1/1/0]...
Page 488: Example: Configuring T3 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide NOTE: Channelized OC48/STM16 IQE interfaces in M Series, MX Series, and T Series routers reserve channels 0 through 3 of each OC12 space for STS3C SONET channels. When you configure E3 or T3 channels in OC12 spaces on the described PICs, the JUNOS Software allocates them starting from channel 4 because channels 0 through 3 are reserved for four STS3c SONET channels.
Page 489: Example: Configuring T1 Interfaces
Chapter 18: Configuring Channelized OC48/STM16 IQE Interfaces [edit interfaces coc1-fpc/pic/port:channel] partition partition-number interface-type t1; If your network equipment uses M13 or C-bit parity, convert the channelized OC1 interface into a channelized T3 interface by including the no-partition interface-type statements at the [edit interfaces coc1- fpc/pic/port:channel] hierarchy level, specifying the...
Page 490: Configuring Fractional T1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide VT-Mapped [edit interfaces coc48-0/0/0] partition 1 oc-slice 1 interface-type coc1; Configuration [edit interfaces coc1-0/0/0:1] partition 1-5 interface-type t1; [edit interfaces coc48-0/0/0] M13 or C-bit partition 1 oc-slice 1 interface-type coc1; Parity-Mapped Configuration [edit interfaces coc1-0/0/0:1] no-partition interface-type ct3;...
Page 491: Configuring Nxds0 Interfaces
Chapter 18: Configuring Channelized OC48/STM16 IQE Interfaces Configuring NxDS0 Interfaces To configure NxDS0 interfaces on a Channelized OC48 IQE PIC, perform the following tasks: Partition the channelized OC48 IQE interface into channelized OC1 interfaces by including the , and statements at the partition oc-slice interface-type...
Page 492: Example: Configuring Nxds0 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces ct1-fpc/pic/port:channel:channel] partition partition-number timeslots time-slot-range interface-type ds; Figure 38 on page 422 shows VT-mapped and M13 or C-bit parity-mapped configurations of NxDS0 interfaces. Figure 38: Sample Channelization of OC48 IQE PIC Example: Configuring NxDS0 Interfaces Configure the following two NxDS0 interfaces with 10 time slots and 4 time slots, respectively: ds-0/0/0:1:2:1...
Page 493: Configuring Channelized Oc48/Stm16 Iqe Interfaces (Sdh Mode)
Chapter 18: Configuring Channelized OC48/STM16 IQE Interfaces [edit interfaces ct1-0/0/0:1:2] partition 1 timeslots 1-10 interface-type ds; partition 2 timeslots 12-15 interface-type ds; For a full configuration example, see the JUNOS Feature Guide. Configuring Channelized OC48/STM16 IQE Interfaces (SDH Mode) The Channelized OC48 IQE PIC configured for SDH mode creates a single channelized STM16 interface.
Page 494: Example: Configuring Channelized Au-4 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Configuring Clear Channel STM1 and STM4 Interfaces On a Channelized OC48/STM16 IQE PIC, you can partition the CSTM16 transport layer into 4 clear channel STM4 interfaces or 16 clear channel STM1 interfaces. Combinations of STM4 and STM1 are also permitted, but you must observe the OC-slice parameters.
Page 495: Configuring E3 Interfaces
Chapter 18: Configuring Channelized OC48/STM16 IQE Interfaces Configuring E3 Interfaces To configure E3 interfaces, include the statements at the partition interface-type [edit interfaces cau4-fpc/pic/port] hierarchy level, specifying the interface type: [edit interfaces] cau4-fpc/pic/port { partition partition-number interface-type e3; This configuration creates the interfaces e3-fpc/pic/port:channel NOTE: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQE interfaces.
Page 496: Configuring E1 Or Channelized E1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Configuring E1 or Channelized E1 Interfaces To configure E1 or channelized E1 interfaces, include the partition interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy level, specifying the interface type: [edit interfaces] cau4-fpc/pic/port { partition partition-number interface-type e1; cau4-fpc/pic/port { partition partition-number interface-type ce1;...
Page 497: Example: Configuring Nxds0 Iqe Interfaces
Chapter 18: Configuring Channelized OC48/STM16 IQE Interfaces 1,9-18,21 Example: Configuring NxDS0 IQE Interfaces Configure channelized NxDS0 interfaces, using partition 4 and time slots 1 through [edit interfaces] ce1-0/2/0:1:2:3 { partition 4 interface-type ds0 timeslots 1-10; This configuration creates interface ds0-0/2/0:1:2:3:4 Configuring T3 or Channelized T3 Interfaces To configure T3 or channelized T3 interfaces, include the partition...
Page 498: Configuring T1 Or Channelized T1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Configuring T1 or Channelized T1 Interfaces To configure T1 or channelized T1 interfaces, include the partition interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy level, specifying the interface type: [edit interfaces] cau4-fpc/pic/port { partition partition-number interface-type t1; cau4-fpc/pic/port { partition partition-number interface-type ct1;...
Page 499: Example: Configuring Channelized Oc48 Interfaces With Partitioned Channels
Chapter 18: Configuring Channelized OC48/STM16 IQE Interfaces Example: Configuring Channelized OC48 Interfaces with Partitioned Channels The following configuration is sufficient to get the channelized OC48 interface up and running. The OC48 interface can be divided into up to 4 OC12 channels, up to 16 OC3 channels, or up to 48 OC1 channels and combinations are permitted;...
Page 500 JUNOS 10.1 Network Interfaces Configuration Guide address 10.11.30.9/30; family iso; unit 1 { dlci 101; family inet { address 10.11.31.9/30; family iso; t3-1fpc/pic/port:3 { encapsulation cisco-hdlc-ccc; t3-options { compatibility-mode larscom; payload-scrambler; unit 0; t3-fpc/pic/port:4 { encapsulation ppp-ccc; t3-options { compatibility-mode larscom; payload-scrambler;...
Page 501: Configuring Channelized Oc12/Stm4 Interfaces
Chapter 19 Configuring Channelized OC12/STM4 Interfaces Channelized OC12/STM4 IQ and IQE Interfaces Overview on page 431 Channelization of OC12/STM4 IQ and Channelized OC12/STM4 IQE PICs (SONET Mode) on page 432 Channelization of OC12/STM4 IQE PIC (SDH Mode) on page 433 Channelization of OC12/STM4 IQ PIC (SDH Mode) on page 434 Channelization of OC12 PIC (SONET Mode) on page 434 Configuring Channelized OC12/STM4 IQ and IQE Interfaces (SONET...
Page 502: Figure 39: Sample Channelization Of Oc12/Stm4 Iq Or Iqe Pic
JUNOS 10.1 Network Interfaces Configuration Guide Channelization of OC12/STM4 IQ and Channelized OC12/STM4 IQE PICs (SONET Mode) Channelized OC12/STM4 IQ PICs and Channelized OC12/STM4 IQE PICs can be configured to operate in SONET or SDH mode and partitioned into various partitions. Figure 39 on page 432 illustrates one possible channelization configuration for Channelized OC12/STM4 IQ and IQE PICs operating in SONET mode.
Page 503: Figure 40: Sample Channelization Of Oc12/Stm4 Iqe Pic (Sdh Mode)
Chapter 19: Configuring Channelized OC12/STM4 Interfaces Channelization of OC12/STM4 IQE PIC (SDH Mode) Channelized OC12/STM4 IQE PICs can be configured to operate in SONET or SDH mode and partitioned to various smaller partitions. Figure 40 on page 433 illustrates one possible channelization configuration for Channelized OC12/STM4 IQE PICs operating in SDH mode.
Page 504: Figure 41: Sample Channelization Of Oc12/Stm4 Iq Pic (Sdh Mode)
JUNOS 10.1 Network Interfaces Configuration Guide Channelization of OC12/STM4 IQ PIC (SDH Mode) Channelized OC12/STM4 IQ PICs can be configured to operate in SONET or SDH mode and partitioned into various smaller partitions. Figure 41 on page 434 illustrates one possible channelization configuration for Channelized OC12/STM4 IQ PICs operating in SDH mode.
Page 505: Configuring An Oc12/Stm4 Interface
Chapter 19: Configuring Channelized OC12/STM4 Interfaces Figure 42: Sample Channelization of OC12 PIC (non IQ and IQE) Figure 42 on page 435 shows five T3 channels configured on the Channelized OC12 PIC. You can configure seven additional T3 channels. For more information about configuring Channelized OC12 PICs, see “Configuring Channelized OC12 Interfaces”...
Page 506 JUNOS 10.1 Network Interfaces Configuration Guide This configuration creates interface coc1-fpc/pic/port:channel Then, include the no-partition interface-type statement at the [edit interfaces hierarchy level, specifying the interface type: coc1-fpc/pic/port:channel] [edit interfaces coc1-fpc/pic/port:channel] no-partition interface-type t3; This configuration creates interface t3-fpc/pic/port:channel The partition number is the sublevel interface partition index and is correlated with the channel number.
Page 507: Example: Configuring T3 Interfaces
Chapter 19: Configuring Channelized OC12/STM4 Interfaces Example: Configuring T3 Interfaces Configure a T3 interface using partition 3 and OC slice 3. This configuration creates interface t3-1/1/0:3 [edit interfaces coc12-1/1/0] partition 3 oc-slice 3 interface-type coc1; [edit interfaces coc1-1/1/0:3] no-partition interface-type t3; For a full configuration example, see the JUNOS Feature Guide.
Page 508 JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces coc12-1/1/0] partition 1 oc-slice 4-6 interface-type so; For a full configuration example, see the JUNOS Feature Guide. Configuring T1 Interfaces on COC12 IQ and IQE Interfaces To configure T1 interfaces on a Channelized OC12 IQ or IQE PIC, perform the following tasks: Partition the channelized OC12 interface into channelized OC1 interfaces by including the...
Page 509: Figure 43: T1 Interfaces On A Channelized Oc12 Pic
Chapter 19: Configuring Channelized OC12/STM4 Interfaces Figure 43: T1 Interfaces on a Channelized OC12 PIC Example: Configuring T1 Interfaces Configure the following T1 interfaces: t1-0/0/0:1:1 t1-0/0/0:1:2 t1-0/0/0:1:3 t1-0/0/0:1:4 t1-0/0/0:1:5 [edit interfaces coc12-0/0/0] VT-Mapped partition 1 oc-slice 1 interface-type coc1; Configuration [edit interfaces coc1-0/0/0:1] partition 1-5 interface-type t1;...
Page 510 JUNOS 10.1 Network Interfaces Configuration Guide partition partition-number oc-slice oc-slice-range interface-type coc1; If your network equipment uses VT mapping, partition the channelized OC1 interface into channelized T1 interfaces by including the partition interface-type statements at the [edit interfaces coc1-fpc/pic/port] hierarchy level, specifying interface type: [edit interfaces coc1-fpc/pic/port] partition partition-number interface-type ct1;...
Page 511: Figure 44: Sample Channelization Of Oc12 Iqe Pic
Chapter 19: Configuring Channelized OC12/STM4 Interfaces Figure 44: Sample Channelization of OC12 IQE PIC Example: Configuring NxDS0 Interfaces Configure the following two NxDS0 interfaces with 10 time slots and 4 time slots, respectively: ds-0/0/0:1:2:1 ds-0/0/0:1:2:2 VT-Mapped [edit interfaces coc12-0/0/0] partition 1 oc-slice 1 interface-type coc1; Configuration [edit interfaces coc1-0/0/0:1] partition 2 interface-type ct1;...
Page 512 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Fractional T1 Interfaces By default, all the time slots on a channelized T1 interface are used. To configure a fractional T1 interface on a Channelized OC12 IQE PIC, perform the following tasks: Configure a T1 interface. For more information, see “Configuring T1 Interfaces” on page 418.
Page 513: Configuring Channelized Oc12/Stm4 Iqe Pics For Sdh Mode
Chapter 19: Configuring Channelized OC12/STM4 Interfaces This section describes how to configure the following channelized OC12 IQE interfaces on a Channelized OC12 IQE PIC configured in SDH mode: Configuring Channelized OC12/STM4 IQE PICs for SDH Mode on page 443 Configuring an Unpartitioned SDH (VC-4-4C) Interface on a Channelized OC12/STM4 IQE PIC on page 444 Configuring SDH (VC-4) Interfaces on Channelized OC12/STM4 IQE PICs on page 444...
Page 514: Example: Configuring An Unpartitioned Sdh (Vc-4-4C) Interface
JUNOS 10.1 Network Interfaces Configuration Guide Configuring an Unpartitioned SDH (VC-4-4C) Interface on a Channelized OC12/STM4 IQE On a Channelized OC12 IQE PIC, you can configure one SDH (VC-4-4C) interface. To configure an SDH (VC-4-4C) interface, include the no-partition interface-type statements at the [edit interfaces cstm4-fpc/pic/port] hierarchy level:...
Page 515: Example: Configuring Sdh (Vc-4) Interfaces
Chapter 19: Configuring Channelized OC12/STM4 Interfaces The interface type is the channelized interface type or data channel you are creating. Example: Configuring SDH (VC-4) Interfaces Configure SDH (VC-4) interfaces: [edit interfaces cstm4-0/2/0] partition 1 oc-slice 1-3 interface-type so; partition 2 oc-slice 4-6 interface-type so; partition 3 oc-slice 7-9 interface-type so;...
Page 516: Configuring E3 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces cstm4-0/2/0] partition 1 oc-slice 1-3 interface-type cau4; partition 2 oc-slice 4-6 interface-type cau4; partition 3 oc-slice 7-9 interface-type cau4; partition 4 oc-slice 10-12 interface-type cau4; This configuration creates the interfaces through cau4-0/2/0:1 cau4-0/2/0:4 Configuring E3 Interfaces To configure E3 interfaces, include the...
Page 517: Configuring E1 Or Channelized E1 Interfaces
Chapter 19: Configuring Channelized OC12/STM4 Interfaces [edit interfaces] cau4-0/2/0:1 { partition 1 interface-type e3; e3-0/2/0:1:1; Configuring E1 or Channelized E1 Interfaces To configure E1 or channelized E1 interfaces, include the partition interface-type statements at the [edit interfaces cau4-fpc/pic/port] hierarchy level, specifying the interface type: [edit interfaces] cau4-fpc/pic/port {...
Page 518: Example: Configuring Nxds0 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide The time-slot range is from 1 through 32. You can designate any combination of time slots. To configure ranges, use hyphens. To configure discontinuous time slots, use commas. You can use a combination of ranges and discontinuous time slots, for example: 1,9-18,21 Example: Configuring NxDS0 Interfaces...
Page 519: Example: Configuring An Unpartitioned Sdh (Vc-4-4C) Interface
Chapter 19: Configuring Channelized OC12/STM4 Interfaces Configuring T1 or Channelized T1 Interfaces Under Channelized T3 Interfaces on page 452 Configuring NxDS0 Interfaces on Channelized OC12/STM4 IQ PICs on page 453 Configuring Channelized OC12/STM4 IQ PICs for SDH Mode To configure a Channelized OC12 IQ PIC to operate in SDH mode, include the framing statement at the hierarchy level:...
Page 520: Example: Configuring Sdh (Vc-4) Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide The partition number is the sublevel interface partition index and is correlated with the channel number. For Channelized OC12 IQ PICs, the OC-slice range can be from 1 through 12. NOTE: For channelized OC12 IQ interfaces, channel numbering begins with 1 (:1). The OC-slice range is the range of SONET/SDH slices.
Page 521: Example: Configuring Channelized Au-4 Interfaces
Chapter 19: Configuring Channelized OC12/STM4 Interfaces The OC-slice range is the range of SONET/SDH slices. For SDH interfaces, the OC-slice range specifies the bandwidth size required for the interface type you are configuring. Channelized AU-4 IQ interfaces must occupy three consecutive OC slices per interface, in one of the following forms: 1–3 4–6...
Page 522: Configuring T1 Or Channelized T1 Interfaces Under Channelized Au-4 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces] cau4-0/2/0:1 { partition 1 interface-type t3; cau4-0/2/0:1 { partition 2 interface-type ct3; t3-0/2/0:1:1 ct3-0/2/0:1:2; Configuring T1 or Channelized T1 Interfaces Under Channelized AU-4 Interfaces To configure T1 or channelized T1 interfaces under channelized AU-4 interfaces, include the partition interface-type...
Page 523: Example: Configuring T1 Or Channelized T1 Interfaces Under Channelized T3 Interfaces
Chapter 19: Configuring Channelized OC12/STM4 Interfaces ct3-fpc/pic/port { partition partition-number interface-type t1; ct3-fpc/pic/port { partition partition-number interface-type ct1; This configuration creates the interfaces t1-fpc/pic/port:channel ct1-fpc/pic/port:channel NOTE: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQ interfaces. You can only apply CoS rules to the aggregate bit streams.
Page 524: Configuring Channelized Oc12 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces] ct1-0/2/0:1:2:3 { partition 4 interface-type ds0 timeslots 1-10; This configuration creates interface ds-0/2/0:1:2:3:4 Configuring Channelized OC12 Interfaces On Channelized OC12 PICs, you can configure 12 T3 channels per port. To configure channelized OC12 interface properties, you can include the sonet-options t3-options statements at the...
Page 525: Example: Configuring Channelized Oc12 Interfaces
Chapter 19: Configuring Channelized OC12/STM4 Interfaces Table 41: OC12-to-DS3 Numbering Scheme (continued) Two-Level STS-1 Number OC12-to-DS3 PIC DS3 (STS-3,STS-1) One-Level STS Number Number Example: Configuring Channelized OC12 Interfaces The following configuration is sufficient to get the channelized OC12 interface up and running.
Page 526: Configuring Link Pic Failover On Channelized Oc12/Stm4 Iq And Iqe Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide compatibility-mode larscom; payload-scrambler; unit 0 { dlci 100; family inet { address 10.11.30.9/30; family iso; unit 1 { dlci 101; family inet { address 10.11.31.9/30; family iso; t3-1fpc/pic/port:3 { encapsulation cisco-hdlc-ccc; t3-options { compatibility-mode larscom; payload-scrambler;...
Page 527: Example: Configuring A Channelized Oc12 Iq Interface As An Unpartitioned Clear Channel
Chapter 19: Configuring Channelized OC12/STM4 Interfaces messages to the remote host if the link PIC fails. To do this, include the no-termination-request statement at the [edit interfaces interface-name ppp-options] hierarchy level: no-termination-request; no-termination-request statement is supported only with MLPPP and SONET APS configurations and works with PPP, PPP over Frame Relay, and MLPPP interfaces only.
Page 528 JUNOS 10.1 Network Interfaces Configuration Guide partition 6 oc-slice 10 interface-type coc1; # (f) coc1-1/1/0:6 partition 7 oc-slice 11 interface-type coc1; # (g) coc1-1/1/0:7 partition 8 oc-slice 12 interface-type coc1; # (h) coc1-1/1/0:8 so-1/1/0:1 { description “(a) OC-slice 1-3 of coc12-1/1/0. COC12 > OC3.; sonet-options { sonet-options-statements;...
Page 529 Chapter 19: Configuring Channelized OC12/STM4 Interfaces partition 4 interface-type ct1; # ct1-1/1/0:5:4 t1-1/1/0:5:1 { description “(e) OC-slice 9 of coc12-1/1/0. T1 interface configuration.”; t1-options { t1-options-statements; ct1-1/1/0:5:4 { description “(e) OC-slice 9 of coc12-1/1/0. CT1 to NxDSOs.; t1-options { t1-options-statements; partition 1 timeslots 0 - 10 interface-type ds0;...
Page 530: Example: Configuring Channelized Oc12 Interfaces With Partitioned Channels
JUNOS 10.1 Network Interfaces Configuration Guide partition 1 - 10 interface-type t1; # t1-1/1/0:7:[1-10] partition 2 interface-type ct1; # ct1-1/1/0:7:11 t1-1/1/0:7:1 { description “(g) T1 interface configuration.”; t1-options { t1-options-statements; ct1-1/1/0:7:11 { description “(g) CT1 to NxDSOs.”; t1-options { t1-options-statements; partition 1 timeslots 0 - 10 interface-type ds0;...
Page 531 Chapter 19: Configuring Channelized OC12/STM4 Interfaces The channels can also have logical interfaces. [edit interfaces] t3-fpc/pic/port:0 { encapsulation cisco-hdlc; t3-options { compatibility-mode larscom; payload-scrambler; unit 0 { family inet { address 10.11.30.1/30; family iso; t3-fpc/pic/port:1 { encapsulation ppp; t3-options { compatibility-mode larscom;...
Page 532 JUNOS 10.1 Network Interfaces Configuration Guide unit 0; t3-fpc/pic/port:4 { encapsulation ppp-ccc; t3-options { compatibility-mode larscom; payload-scrambler; unit 0; t3-fpc/pic/port:5 { dce; encapsulation frame-relay-ccc; t3-options { compatibility-mode larscom; payload-scrambler; unit 0 { encapsulation frame-relay-ccc; dlci 1000; unit 1 { encapsulation frame-relay-ccc; dlci 1001;...
Page 533: Configuring Channelized Oc3 Iq And Iqe Interfaces
Chapter 20 Configuring Channelized OC3 IQ and IQE Interfaces Channelized OC3 IQ and IQE Overview on page 463 Partitions, OC Slices, Interface Types, and Time Slots on page 464 Configuring a Clear Channel on Channelized OC3 IQ and IQE PICs on page 465 Configuring T3 Interfaces on IQ and IQE Interfaces on page 465 Configuring T1 and NxDS0 Interfaces on page 466 Configuring Fractional T1 IQ Interfaces on page 470...
Page 534: Figure 45: Channelized Oc3 Iq Interface Example For Show Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Figure 45: Channelized OC3 IQ Interface Example for Show Interfaces Controller You can configure the following encapsulation types: Frame Relay Cisco HDLC MPLS—On IQE interfaces. For more information about interface encapsulation, see “Configuring Interface Encapsulation on Physical Interfaces”...
Page 535 Chapter 20: Configuring Channelized OC3 IQ and IQE Interfaces You configure the OC-slice range for SONET/SDH interfaces only. The OC-slice range is correlated with the bandwidth size required for the interface type you are configuring. For example, a channelized OC3 interface ( ) can be divided into coc3 three OC1 interfaces, each containing one OC slice.
Page 536: Example: Configuring T3 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide When you include the statement at the partition [edit interfaces coc3-fpc/pic/port] hierarchy level, the only configurable interface type is coc1 . This configuration creates interface coc1-fpc/pic/port:channel NOTE: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQ interfaces.
Page 537 Chapter 20: Configuring Channelized OC3 IQ and IQE Interfaces statements at the hierarchy interface-type [edit interfaces coc1-fpc/pic/port:channel] level, specifying the interface type: [edit interfaces coc1-fpc/pic/port:channel] no-partition partition-number interface-type ct3; NOTE: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQ interfaces.
Page 538: Example: Configuring T1 And Nxds0 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Figure 46: T1 Interfaces on a Channelized OC3 PIC Configure channelized NxDS0 IQ interfaces on the channelized T1 IQ interface by including the partition timeslots , and interface-type statements at the [edit hierarchy level, specifying the interface interfaces ct1-fpc/pic/port:channel] type:...
Page 539: Example: Setting Remote Loopback And Running Bert Tests On Nxds0 Interfaces
Chapter 20: Configuring Channelized OC3 IQ and IQE Interfaces [edit interfaces coc1-0/0/0:1] partition 1-5 interface-type t1; M13 or C-bit [edit interfaces coc3-0/0/0] partition 1 oc-slice 1 interface-type coc1; Parity-Mapped [edit interfaces coc1-0/0/0:1] Configuration no-partition interface-type ct3; [edit interfaces ct3-0/0/0:1] partition 1-5 interface-type t1; Configure the following two NxDS0 interfaces with 10 time slots and 4 time slots, respectively: ds-0/0/0:1:2:1...
Page 540: Configuring Fractional T1 Iq Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide bert-period 30; Remote router: [edit interfaces] ct1-0/0/0:2:2 { partition 1 timeslots 1-10 interface-type ds; t1-options { loopback remote; Configuring Fractional T1 IQ Interfaces By default, all the time slots on a channelized T1 interface are used. To configure a fractional T1 interface on a Channelized OC3 IQ or IQE PIC, you must perform the following tasks: Configure a T1 interface on the Channelized OC3 IQ or IQE PIC.
Page 541 Chapter 20: Configuring Channelized OC3 IQ and IQE Interfaces messages to the remote host if the link PIC fails. To do this, include the statement at the no-termination-request [edit interfaces interface-name ppp-options] hierarchy level: no-termination-request; no-termination-request statement is supported only with MLPPP and SONET APS configurations and works with PPP, PPP over Frame Relay, and MLPPP interfaces only.
Page 542 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Link PIC Failover on Channelized OC3 IQ and IQE Interfaces...
Page 543: Configuring Channelized Stm1 Interfaces
Chapter 21 Configuring Channelized STM1 Interfaces Channelized STM1 Interfaces Overview on page 473 Configuring Channelized STM1 IQ and IQE Interfaces on page 473 Configuring Channelized STM1 Interfaces on page 479 Configuring Link PIC Failover on Channelized STM1 Interfaces on page 486 Example: Configuring Channelized STM1 Interfaces on page 487 Channelized STM1 Interfaces Overview Each Channelized STM1 PIC and Channelized STM1 Intelligent Queuing (IQ) PIC has...
Page 544: Example: Configuring E1 Iq And Iqe Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide no-partition interface-type so; This configuration creates interface so-fpc/pic/port NOTE: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQ and IQE interfaces. You can only apply CoS rules to the aggregate bit streams. Configuring E1 IQ and IQE Interfaces To configure an E1 interface on a Channelized STM1 IQ or IQE PIC, perform the following tasks:...
Page 545: Configuring Fractional E1 Iq And Iqe Interfaces
Chapter 21: Configuring Channelized STM1 Interfaces e1-0/0/0:3 e1-0/0/0:4 e1-0/0/0:5 [edit interfaces cstm1-0/0/0] no-partition interface-type cau4; [edit interfaces cau4-0/0/0] partition 1-5 interface-type e1; For a full configuration example, see the JUNOS Feature Guide. Configuring Fractional E1 IQ and IQE Interfaces By default, all the time slots on a channelized E1 interface are used. To configure a fractional E1 interface on a Channelized STM1 IQ or IQE PIC, perform the following tasks: Include the...
Page 546: Example: Configuring Fractional E1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide For more information about E1 time slots, see “Configuring Fractional E1 Time Slots” on page 566. Example: Configuring Fractional E1 Interfaces Configure a fractional E1 interface that uses time slots 2 through 10: [edit interfaces cstm1-0/0/0] no-partition cau4;...
Page 547: Example: Configuring An Nxds0 Iq Interface
Chapter 21: Configuring Channelized STM1 Interfaces NOTE: Class-of-service (CoS) rules cannot be applied to an individual channel configured on channelized IQ and IQE interfaces. You can only apply CoS rules to the aggregate bit streams. NOTE: For channelized STM1 interfaces, channel numbering begins with 0 (:0). For channelized STM1 IQ and IQE interfaces, channel numbering begins with 1 (:1).
Page 548 JUNOS 10.1 Network Interfaces Configuration Guide e1-1/1/0:1 { unit 0 { family inet { address 10.10.10.1/30; Fractional E1 Interface [edit interfaces] cstm1-1/0/0 { no-partition interface-type cau4; [edit interfaces] cau4-1/0/0 { partition 1-63 interface-type e1; [edit interfaces] e1-1/1/0:1 { e1-options { timeslots 2-10;...
Page 549: Configuring Channelized Stm1 Interfaces
Chapter 21: Configuring Channelized STM1 Interfaces Configuring Channelized STM1 Interfaces To specify the channel number, include it after the colon (:) in the interface name. For example, a Channelized STM1-to-E1 PIC in FPC 1 and slot 1 will have the following physical interface, depending on the media type: e1-1/1/0:x The E1 channel number can be from 0 through 62.
Page 550: Configuring Virtual Tributary Mapping Of Channelized Stm1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide hold-time milliseconds; lockout; neighbor address; paired-group group-name; protect-circuit group-name; request; revert-time seconds; switching-mode (bidirectional | unidirectional); working-circuit group-name; bytes { e1-quiet value; f1 value; f2 value; s1 value; z3 value; z4 value; loopback (local | remote); NOTE: On channelized STM1 interfaces, you should configure the clock source on one side of the connection to be internal (the default JUNOS configuration) and on the other side of the connection to be external.
Page 551: Table 42: Channelized Stm1-To-E1 Channel Mapping
Chapter 21: Configuring Channelized STM1 Interfaces [edit interfaces cau4-fpc/pic/port sonet-options] vtmapping (klm | itu-t); Table 42 on page 481 lists the KLM mappings used by the channelized STM1-to-E1 PIC interfaces. The PIC defaults to KLM numbering with an offset of –1; for example, KLM 1= STM1 PIC 0.
Page 552 JUNOS 10.1 Network Interfaces Configuration Guide Table 42: Channelized STM1-to-E1 Channel Mapping (continued) Channel Tributary Unit Tributary Unit Virtual ITU-T Number KLM Number Group 3 Group 2 Tributary Number Configuring Channelized STM1 Interfaces...
Page 553: Table 43: Channelized Stm1-To-T1 Channel Mapping
Chapter 21: Configuring Channelized STM1 Interfaces Table 42: Channelized STM1-to-E1 Channel Mapping (continued) Channel Tributary Unit Tributary Unit Virtual ITU-T Number KLM Number Group 3 Group 2 Tributary Number Table 43 on page 483 lists the KLM mappings used by the channelized STM1-to-T1 PIC interfaces.
Page 554 JUNOS 10.1 Network Interfaces Configuration Guide Table 43: Channelized STM1-to-T1 Channel Mapping (continued) Channel Tributary Unit Tributary Unit Virtual ITU-T Number KLM Number Group 3 Group 2 Tributary Number Configuring Channelized STM1 Interfaces...
Page 555 Chapter 21: Configuring Channelized STM1 Interfaces Table 43: Channelized STM1-to-T1 Channel Mapping (continued) Channel Tributary Unit Tributary Unit Virtual ITU-T Number KLM Number Group 3 Group 2 Tributary Number Configuring Channelized STM1 Interfaces...
Page 556: Configuring Link Pic Failover On Channelized Stm1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Table 43: Channelized STM1-to-T1 Channel Mapping (continued) Channel Tributary Unit Tributary Unit Virtual ITU-T Number KLM Number Group 3 Group 2 Tributary Number Configuring Link PIC Failover on Channelized STM1 Interfaces For Channelized STM1 IQ and IQE PICs used as linking PICs in redundant LSQ configurations, you can inhibit the router from sending PPP termination-request messages to the remote host if the link PIC fails.
Page 557: Example: Configuring Channelized Stm1 Interfaces
Chapter 21: Configuring Channelized STM1 Interfaces statement at the no-termination-request [edit interfaces interface-name ppp-options] hierarchy level: no-termination-request; no-termination-request statement is supported only with MLPPP and SONET APS configurations and works with PPP, PPP over Frame Relay, and MLPPP interfaces only. For information about interchassis and intrachassis LSQ failover, see the JUNOS Services Interfaces Configuration Guide.
Page 558 JUNOS 10.1 Network Interfaces Configuration Guide unit 1 { dlci 16; family inet { address 10.11.31.9/30; e1-fpc/pic/port:2 { encapsulation ppp; no-keepalives; unit 0 { family inet { address 10.11.31.47/30; [edit] chassis { fpc 2 { pic 0 { vtmapping klm; Example: Configuring Channelized STM1 Interfaces...
Page 559: Configuring Channelized T3 Interfaces
Chapter 22 Configuring Channelized T3 Interfaces Configuring Channelized T3 IQ Interfaces on page 489 Configuring Channelized DS3-to-DS0 Interfaces on page 492 Configuring Channelized DS3-to-DS1 Interfaces on page 495 Example: Configuring Channelized T3 IQ Interfaces on page 496 Examples: Configuring Channelized DS3-to-DS0 Interfaces on page 497 Examples: Configuring Channelized DS3-to-DS1 Interfaces on page 500 Configuring Channelized T3 IQ Interfaces NOTE: Class-of-service (CoS) rules cannot be applied to an individual channel...
Page 560: Example: Configuring T1 Iq And Iqe Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Configuring T1 IQ Interfaces On a Channelized DS3 IQ or IQE Physical Interface Card (PIC), you can create up to 112 T1 interfaces. To configure a T1 interface on a Channelized DS3 IQ or IQE PIC, include the statements at the partition...
Page 561: Example: Configuring Fractional T1 Iq Interfaces
Chapter 22: Configuring Channelized T3 Interfaces [edit interfaces t1-fpc/pic/port t1-options] timeslots time-slot-range; For channelized T1 IQ interfaces, the time-slot range is from 1 through 24. You can designate any combination of time slots. To configure ranges, use hyphens. To configure discontinuous time slots, use commas. Do not include spaces. For more information about T1 time slots, see “Configuring Fractional T1 Time Slots”...
Page 562: Example: Configuring An Nxds0 Iq Interface
JUNOS 10.1 Network Interfaces Configuration Guide For channelized T1 IQ interfaces, the partition number range is from 1 through 28; the time-slot range is from 1 through 24. You can designate any combination of time slots. To configure ranges, use hyphens. To configure discontinuous time slots, use commas.
Page 563: Table 44: Ranges For Channelized Ds3-To-Ds0 Configuration
Chapter 22: Configuring Channelized T3 Interfaces By default, all the time slots are used. To configure the channel groups and time slots for a channelized DS3-to-DS0 interface, include the channel-group timeslots statements at the [edit chassis fpc slot-number pic pic-number ct3 port port-number t1 hierarchy level: link-number] [edit chassis fpc slot-number pic pic-number ct3 port port-number t1 link-number ]...
Page 564 JUNOS 10.1 Network Interfaces Configuration Guide are valid for this configuration, and the , and buildout invert-data line-encoding statements at the [edit interfaces interface-name t1-options] hierarchy level are ignored. Likewise, only a subset of the DS0 options are valid for this configuration, and the , and statements at the bert-algorithm...
Page 565: Configuring Channelized Ds3-To-Ds1 Interfaces
Chapter 22: Configuring Channelized T3 Interfaces loopback payload; start-end-flag (filler | shared); For more information about specific parameters, see “E1 Interfaces Overview” on page 561, “E3 Interfaces Overview” on page 569, “T1 Interfaces Overview” on page 577, and “T3 Interfaces Overview” on page 587. For a configuration example, see “Examples: Configuring Channelized DS3-to-DS0 Interfaces”...
Page 566: Example: Configuring Channelized T3 Iq Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide The statements in the hierarchy are supported only for channel 0; they t3-options are ignored if configured on other channels. To specify options for each of the T1 channels, include the t1-options statement at hierarchy level: [edit interfaces interface-name] [edit interfaces interface-name]...
Page 567: Examples: Configuring Channelized Ds3-To-Ds0 Interfaces
Chapter 22: Configuring Channelized T3 Interfaces Figure 48: Sample Channelization of DS3 IQ or IQE PIC [edit interfaces] ct3-1/1/0 { description “CT3 to CT1 and CT3 to T1.”; t3-options { loopback remote; looptiming; partition 1 interface-type ct1; # ct1-1/1/0:1. partition 2-28 interface-type t1; # t1-1/1/0:[2-28] ct1-1/1/0:1 { description “case (a) CT1s to NxDSOs.”;...
Page 568 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: All these configuration examples specify channel group 0 in the interface address, which is required for configuring the t3-options t1-options statements. Configuring Cisco HDLC [edit interfaces] ds-2/0/1:20:0 { Encapsulation on a encapsulation cisco-hdlc; Channelized DS3-to-DS0 unit 0 { Interface...
Page 569 Chapter 22: Configuring Channelized T3 Interfaces Configuring Three Frame [edit interfaces] t1-5/1/3:0 { Relay DLCIs on a mtu 9192; Channelized DS3 encapsulation frame-relay; Interface unit 1 { dlci 101; family inet { mtu 9000; address 10.123.1.2/32 { destination 10.123.1.1; family iso { mtu 9000;...
Page 570: Examples: Configuring Channelized Ds3-To-Ds1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide byte-encoding nx56; unit 0 { family inet { address 10.221.2.8/24; [edit interfaces ds-0/1/0:5:0] Configuring Cisco HDLC no-keepalives; Encapsulation with encapsulation cisco-hdlc; Byte-Encoding and t1-options { Framing byte-encoding nx56; framing sf; unit 0 { family inet { address 10.221.2.8/24;...
Page 571 Chapter 22: Configuring Channelized T3 Interfaces Configuring PPP [edit interfaces] t1-2/0/1:20 { Encapsulation on a encapsulation ppp; Channelized DS3 unit 0 { Interface family inet { address 10.0.4.40/32 { destination 10.0.4.41; Configuring Five Frame [edit interfaces] t1-5/1/3:0 { Relay DLCIs on a mtu 9192;...
Page 572 JUNOS 10.1 Network Interfaces Configuration Guide mtu 9000; address 10.123.1.6/32 { destination 10.123.1.5; family iso { mtu 9000; family mpls { mtu 9000; unit 4 { dlci 104; family inet { mtu 9000; address 10.123.1.8/32 { destination 10.123.1.7; family iso { mtu 9000;...
Page 573 Chapter 22: Configuring Channelized T3 Interfaces Configuring Cisco HDLC [edit interfaces t1-1/1/0:1] no-keepalives; Encapsulation with encapsulation cisco-hdlc; Byte-Encoding and t1-options { Framing byte-encoding nx56; framing sf; unit 0 { family inet { address 10.221.2.8/24; Examples: Configuring Channelized DS3-to-DS1 Interfaces...
Page 574 JUNOS 10.1 Network Interfaces Configuration Guide Examples: Configuring Channelized DS3-to-DS1 Interfaces...
Page 575: Configuring Channelized T1 Interfaces
Chapter 23 Configuring Channelized T1 Interfaces Channelized T1 IQ and IQE Interfaces Overview on page 505 Configuring Channelized T1 IQ and IQE Interfaces on page 505 Example: Configuring Channelized T1 IQ and IQE Interfaces on page 509 Channelized T1 IQ and IQE Interfaces Overview The Channelized T1 intelligent queuing (IQ) and enhanced intelligent queuing (IQE) PICs have 10 T1 ports that you can channelize to the DS0 level.
Page 576: Example: Configuring Fractional T1 Iq And Iqe Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide NOTE: For a T1 (t1-) interface configured on channelized T1 (ct1-) interface on a Channelized T1 IQ or IQE PIC, you can configure the following T1 options, but these options do not take effect for the T1 interface: bert-algorithm bert-error-rate bert-period...
Page 577: Configuring Nxds0 Iq And Iqe Interfaces
Chapter 23: Configuring Channelized T1 Interfaces timeslots 1-10; For a full configuration example, see the JUNOS Feature Guide. Configuring NxDS0 IQ and IQE Interfaces By default, all the time slots on a channelized T1 interface are used. To configure an NxDS0 IQ or IQE interface on a Channelized T1 IQ or IQE PIC, you must configure the number of time slots allocated to the NxDS0 IQ or IQE interface by including the partition...
Page 578: Table 45: Ranges For Channelized T1 Iq Configuration
JUNOS 10.1 Network Interfaces Configuration Guide is a DS0 channel group from 1 through 24 (for more information about ranges, see Table 45 on page 508). You can use any of the values within the range available for ; you do not have to configure the links sequentially.
Page 579: Configuring Channelized T1 Interface Properties
Chapter 23: Configuring Channelized T1 Interfaces Configuring Channelized T1 Interface Properties To configure channelized T1 IQ or IQE interface properties, include the t1-options statement at the [edit interfaces interface-name] hierarchy level: [edit interfaces interface-name] t1-options { byte-encoding (nx56 | nx64) fcs (16 | 32);...
Page 580 JUNOS 10.1 Network Interfaces Configuration Guide Configure a partitioned channel group. Configuring a Channel [edit interfaces] ct1-0/0/1 { Group partition 1 interface-type ds0 timeslots 1-10; partition 2interface-type ds0 timeslots 11-20; The following configuration is sufficient to get the channelized T1 IQ or IQE interface up and running: [edit] Configuring Multiple...
Page 581: Configuring Channelized E1 Interfaces
Chapter 24 Configuring Channelized E1 Interfaces Channelized E1 IQ and IQE Interfaces Overview on page 511 Configuring Channelized E1 IQ and IQE Interfaces on page 511 Configuring Channelized E1 Interfaces on page 513 Example: Configuring Channelized E1 IQ or IQE Interfaces on page 515 Example: Configuring Channelized E1 Interfaces on page 516 Channelized E1 IQ and IQE Interfaces Overview Each Channelized E1 PIC, Channelized E1 Intelligent Queuing (IQ) PIC and...
Page 582: Example: Configuring Fractional E1 Iq And Iqe Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Configuring Fractional E1 IQ and IQE Interfaces By default, all the time slots on a channelized E1 interface are used. To configure a fractional E1 interface on a Channelized E1 IQ PIC, perform the following tasks: Include the statement at the hierarchy...
Page 583: Example: Configuring An Nxds0 Iq Or Iqe Interface
Chapter 24: Configuring Channelized E1 Interfaces For channelized E1 IQ and IQE interfaces, the partition number range is from 1 through 31. For E1 IQ and IQE interfaces ( ), the time-slot range is from 2 through e1-fpc/pic/port 31. For channelized E1 IQ and IQE interfaces ( ce1-fpc/pic/port ), the time-slot range is from 1 through 31.
Page 584: Table 46: Ranges For Channelized E1 Configuration
JUNOS 10.1 Network Interfaces Configuration Guide ce1 { e1 link-number { channel-group group-number; timeslots time-slot-range; NOTE: If you commit the interface name but do not include the [edit chassis] configuration, the Channelized E1 PIC behaves like a standard E1 PIC, and none of the DS0 functionality is accessible.
Page 585: Configuring Channelized E1 Interface Properties
Chapter 24: Configuring Channelized E1 Interfaces Configuring Channelized E1 Interface Properties To configure channelized E1 interface properties, include the statement e1-options at the [edit interfaces interface-name] hierarchy level: [edit interfaces interface-name] e1-options { fcs (16 | 32); framing (g704 | g704-no-crc4 | unframed); idle-cycle-flag (flags | ones);...
Page 586: Example: Configuring Channelized E1 Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide The following configuration is sufficient to get the channelized E1 IQ or IQE interface up and running: Configuring Multiple [edit] interfaces { Interface Types ce1-1/2/3 { partition 1 timeslots 10 interface-type ds; # ds-1/2/3:1 partition 2 timeslots 1-9 interface-type ds;...
Page 587 Chapter 24: Configuring Channelized E1 Interfaces e1 4 { channel-group 10 timeslots 11,17,28-31; [edit interfaces ds-0/1/0:0] e1-options { fcs 32; framing g704-non-grc; loopback remote; [edit interfaces ds-0/1/4:10] ds0-options { byte-encoding nx56; start-end-flag filler; The above configuration results in the following interfaces: ds-0/1/0:1, with time slot 1 allocated ds-0/1/0:5, with time slots 5 through 7 allocated ds-0/1/4:10, with time slots 11, 17, and 28 through 31 allocated...
Page 588 JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring Channelized E1 Interfaces...
Page 589: Channelized E1 Pri And T1 Pri Overview
Chapter 25 Configuring Channelized E1 PRI and T1 PRI Interfaces Channelized E1 PRI and T1 PRI Overview on page 519 Configuring a Clear Channel on a Dual-Port Channelized T1-E1 PIM on page 520 Configuring a Channelized T1/E1 Interface to Drop and Insert Time Slots on page 520 Configuring Primary Rate Interfaces on page 522 Allocating B-Channels for Dialout on page 523...
Page 590: Interface
JUNOS 10.1 Network Interfaces Configuration Guide Either a channelized E1 ( ) or channelized T1 ( port port interface. Time slots within a port interface or port interface. A bearer (B) channel interface for each time slot that bc-pim/0/port:channel you want to function as an ISDN PRI B-channel. The B-channel is used for data, video, voice, and multimedia.
Page 591 Chapter 25: Configuring Channelized E1 PRI and T1 PRI Interfaces Engine. This feature, known as drop and insert, allows you to integrate voice and data on a single T1 or E1 link by removing the DS0 time slots of one T1 or E1 port and replacing them by inserting the time slots of another T1 or E1 port.
Page 592 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Primary Rate Interfaces Primary rate interfaces are a combination of B-channels with one controlling D-channel for the group. Configure B-channel interfaces for each time slot that you want to function as an ISDN PRI interface. The B-channel is used for data, video, voice, and multimedia.
Page 593 Chapter 25: Configuring Channelized E1 PRI and T1 PRI Interfaces show interfaces interface-name detail show interface dln show isdn calls show isdn history show isdn q921 statistics show isdn q931 statistics show isdn status NOTE: You must configure a D-channel and B-channels to complete your ISDN PRI line configuration.
Page 594 JUNOS 10.1 Network Interfaces Configuration Guide partition 2 timeslots 11-24 interface-type pr; This configuration creates interfaces ds-pim/0/port:1 through pr-pim/0/port:2 Use the same configuration to create interfaces on a channelized E1 interface by including the statement and options at the partition [edit interfaces ce1-pim/0/port] hierarchy level.
Page 595 Chapter 25: Configuring Channelized E1 PRI and T1 PRI Interfaces isdn-options { switch-type att5e; bchannel-allocation descending; incoming-called-number 384101; incoming-called-number 384102; incoming-called-number 384103; [edit interfaces] dl0 { unit 0 { dialer-options { pool 1; dial-string 384010; incoming-map { accept-all; family inet { filter { dialer int-packet;...
Page 596 JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring a Channelized T1 Interface as Primary Rate Interface...
Page 597: Part 8 Configuring Circuit Emulation Pics
Part 8 Configuring Circuit Emulation PICs Circuit Emulation PICs Overview on page 529 Configuring SAToP Support on Circuit Emulation PICs on page 533 Configuring ATM Support on Circuit Emulation PICs on page 539 Configuring Circuit Emulation PICs...
Page 598 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Circuit Emulation PICs...
Page 599: Circuit Emulation Pics Overview
Displaying Information About Circuit Emulation PICs on page 532 Mobile Backhaul and Circuit Emulation Overview Juniper Networks mobile backhaul (IP/MPLS) solutions provide the following benefits: Flexibility to support converged networks that accommodate both IP and legacy services (leveraging proven circuit emulation techniques).
Page 600: Figure 49: Mobile Backhaul Application
JUNOS 10.1 Network Interfaces Configuration Guide Mobile Backhaul Application Overview This section provides an application example (see Figure 49 on page 530) based on the mobile backhaul reference model where customer edge 1 (CE1) is a base station controller (BSC), Provider Edge 1 (PE1) is a cell site router, PE2 is an M Series (aggregation) router, and CE2 is a BSC and Radio Network Controller (RNC).
Page 601 Chapter 26: Circuit Emulation PICs Overview Understanding Circuit Emulation PIC Clocking Features All Circuit Emulation PICs support the following clocking features: External clocking—Also known as loop timing. Clock is distributed via TDM interfaces. Internal clocking with external synchronization—Also known as external timing or external synchronization.
Page 602 JUNOS 10.1 Network Interfaces Configuration Guide are not supported. crc-major-alarm-threshold crc-minor-alarm-threshold remote-loopback-respond is not supported. It is not applicable in SAToP configurations. The 4-port Channelized OC3/STM1 Circuit Emulation PICs support T1 and E1 options with the following exceptions: , and options are supported for CT1 or bert-algorithm bert-error-rate...
Page 603: Configuring Satop Support On Circuit Emulation Pics
Chapter 27 Configuring SAToP Support on Circuit Emulation PICs Configuring SAToP on 4-port Channelized OC3/STM1 Circuit Emulation PICs on page 533 Configuring SAToP Emulation on T1/E1 Interfaces on Circuit Emulation PICs on page 535 Configuring SAToP on 4-port Channelized OC3/STM1 Circuit Emulation PICs This configuration example applies to the mobile backhaul application shown in Figure 49 on page 530.
Page 604 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: If you set the option incorrectly for the PIC type, the commit operation framing fails. Bit error rate test (BERT) patterns with all ones received by T1/E1 interfaces on Circuit Emulation PICs configured for SAToP do not result in alarm indication signal (AIS) defect.
Page 605: Setting The Emulation Mode
Chapter 27: Configuring SAToP Support on Circuit Emulation PICs [edit interfaces] cstm1-1/0/1 { no-partition interface-type cau4; cau4-1/0/1 { partition 1 interface-type e1; e1-1/0/1:1 { encapsulation satop; unit 0; After you configure the E1 channels, configure SAToP options on them in the same way as for E1 interfaces.
Page 606: Setting The Encapsulation Mode
JUNOS 10.1 Network Interfaces Configuration Guide Configuring SAToP Emulation on T1/E1 Interfaces Setting the Encapsulation Mode on page 536 T1/E1 Loopback Support on page 536 T1 FDL Support on page 536 Setting the SAToP Options on page 536 Pseudowire Interface Configuration on page 537 Setting the Encapsulation Mode T1/E1 channels on circuit emulation PICs can be configured with SAToP encapsulation at the PE router, as follows:...
Page 607: Pseudowire Interface Configuration
Chapter 27: Configuring SAToP Support on Circuit Emulation PICs —Number of milliseconds over which excessive packet loss rate is sample-period calculated. threshold —Percentile designating the threshold of excessive packet loss rate (from 1 to 100 percent). The following example shows the SAToP configuration options: [edit interfaces (t1|e1)-fpc/pic/port] satop-options { excessive-packet-loss-rate {...
Page 608 JUNOS 10.1 Network Interfaces Configuration Guide For detailed information about PICs, see the PIC Guide for your router. Configuring SAToP Emulation on T1/E1 Interfaces on Circuit Emulation PICs...
Page 609: Configuring Atm Support On Circuit Emulation Pics
Chapter 28 Configuring ATM Support on Circuit Emulation PICs ATM Support on Circuit Emulation PICs Overview on page 539 Configuring the 12-Port Channelized T1/E1 Circuit Emulation PIC Operating Mode on page 541 Configuring the 4-Port Channelized COC3/STM1 Circuit Emulation PIC Operating Mode on page 542 ATM IMA Configuration Overview on page 545 Configuring ATM IMA on page 551...
Page 610 JUNOS 10.1 Network Interfaces Configuration Guide ATM OAM support: Generation and monitoring of F4 and F5 OAM cells Generation and monitoring of end-to-end cells of type AIS and RDI Monitor and terminate loopback cells Supports OAM on each VP and VC simultaneously The following protocols are not supported: QoS or COS queues.
Page 611: T1/E1 Mode Selection
Chapter 28: Configuring ATM Support on Circuit Emulation PICs Configuring Layer 2 Circuit and Layer 2 VPN Pseudowires on page 556 ATM Limitations on page 557 Configuring the 12-Port Channelized T1/E1 Circuit Emulation PIC Operating Mode This section contains the following topics: T1/E1 Mode Selection on page 541 12-Port Channelized T1/E1 Circuit Emulation PIC Configuration Statements on page 541...
Page 612: Configuring The 4-Port Channelized Coc3/Stm1 Circuit Emulation Pic Operating Mode
JUNOS 10.1 Network Interfaces Configuration Guide Or specify the following: chassis { fpc fpc-slot { pic pic-slot { framing (t1 | e1); After the PIC is brought online, 12 ct1 interfaces or 12 ce1 interfaces are created. If the mode is not manually configured, then the PIC defaults to T1. To create an ATM interface on a CT1, enter the following command: Creating an ATM Interface on a CT1 or...
Page 613: Figure 52: 4-Port Channelized Coc3/Stm1 Circuit Emulation Pic Possible
Chapter 28: Configuring ATM Support on Circuit Emulation PICs T1/E1 Mode Selection All ATM interfaces are either T1 or E1 channels within the COC3/CSTM1 hierarchy. Each COC3 can be partitioned as 3 COC1 slices, each of which in turn can be partitioned further into 28 ATM interfaces and the size of each interface created is that of a T1.
Page 614: Configuring A Port For Sonet Or Sdh Mode On A 4-Port Channelized Coc3/Stm1 Circuit Emulation Pic
JUNOS 10.1 Network Interfaces Configuration Guide Configuring a Port for SONET or SDH Mode on a 4-Port Channelized COC3/STM1 Circuit Emulation PIC Each port of the 4-port Channelized COC3/STM1 Circuit Emulation PIC can be independently configured for either SONET or SDH mode. To configure a port for either SONET or SDH mode, enter the [ statement at the framing (sonet | sdh)
Page 615: Atm Ima Configuration Overview
Chapter 28: Configuring ATM Support on Circuit Emulation PICs The interfaces are created. at-x/y/z:1:2 To create an ATM interface on CAU4, enter the following command: set interfaces cau4-fpc/pic/port partition 2 interface-type at Or specify the following: interfaces { cau4-fpc/pic/port { partition number { interface-type at;...
Page 616 JUNOS 10.1 Network Interfaces Configuration Guide IMA Version Either IMA 1.0 (af-phy-0086.000-IMA) or IMA 1.1 (af-phy-0086.001-IMA) can be selected through the CLI. If not specified, IMA 1.1 is selected by default. IMA 1.0 and IMA 1.1 do not interoperate. IMA Groups You can configure up to 42 IMA groups.
Page 617: Table 47: Ima Frame Synchronization Link State Transition Variables
Chapter 28: Configuring ATM Support on Circuit Emulation PICs Table 47: IMA Frame Synchronization Link State Transition Variables Setting Range Default Description alpha Consecutive invalid ICP cells beta Consecutive errored ICP cells gamma Consecutive valid ICP cells IMA Link Addition and Deletion When an IMA group is up, you can add links to or delete links from the group without dropping cells.
Page 618: Table 49: Ima Group Defects With Ima Standard Requirement Numbers
JUNOS 10.1 Network Interfaces Configuration Guide Table 48: IMA Group Alarms with IMA Standard Requirement Numbers (continued) Alarm IMA Standard Requirement Number Insufficient-Links R-148 Insufficient-Links-FE R-149 Blocked-FE R-150 GR-Timing-Mismatch R-151 Table 49 on page 548 shows the supported IMA group defects and their associated IMA standard requirement numbers.
Page 619: Table 51: Ima Link Defects With Ima Standard Requirement Numbers
Chapter 28: Configuring ATM Support on Circuit Emulation PICs Table 50: IMA Link Alarms with IMA Standard Requirement Numbers (continued) IMA Standard Requirement Alarm Number Description Tx-Unusable-FE R-143 Transmit unusable far end Rx-Unusable-FE R-144 Receive unusable far end Link Fault Link fault Table 51 on page 549 shows the supported IMA link defects and their associated IMA standard requirement numbers.
Page 620: Table 52: Ima Link Statistics With Ima Standard Requirement Numbers
JUNOS 10.1 Network Interfaces Configuration Guide IMA Link Statistics Table 52 on page 550 shows the IMA link statistics. Table 52: IMA Link Statistics with IMA Standard Requirement Numbers Performance Parameter IMA Standard Requirement Number Rx LIF Rx ICP cells Rx errored ICP cells R-106 Rx LODS...
Page 621: Ima Clocking
Chapter 28: Configuring ATM Support on Circuit Emulation PICs IMA Clocking Clocking is applicable only to IMA links. The clocking statement does not apply to interface because the IMA group it represents is a virtual interface. at-x/y/g Configuring ATM IMA Creating the IMA Groups (ATM Interfaces) on page 551 Linking Constituents to Form Group and T1/E1 Options on page 551 ATM Options and Encapsulations and Families on page 552...
Page 622 JUNOS 10.1 Network Interfaces Configuration Guide coc1-x/y/1:1 -> t1-x/y/1:1:1 / Partitions of COC1 and CT1 Interfaces ct1-x/y/0 -> t1-x/y/0 \ ct1-x/y/1 -> t1-x/y/1 -o-> at-x/y/101 ct1-x/y/2 -> t1-x/y/2 / ATM Options and Encapsulations and Families [edit interfaces] at-fpc/pic/port { atm-options { unit 0 { encapsulation (atm-ccc-vc-mux | atm-ccc-cell-relay);...
Page 623: Configuring Atm Pseudowires
Chapter 28: Configuring ATM Support on Circuit Emulation PICs period 1-4294967294 Configuring ATM Pseudowires ATM pseudowires are described in RFC 4717. Pseudowire encapsulation is selected by configuring for a cell-relay pseudowire: [edit interfaces at-fpc/pic/port:unit n] encapsulation atm-ccc-cell-relay; atm-l2circuit-mode cell; Or for an AAL5 pseudowire: encapsulation atm-ccc-vc-mux;...
Page 624 JUNOS 10.1 Network Interfaces Configuration Guide Configuring VP or Port Promiscuous Mode By default, all incoming cells are mapped from a single VC to an ATM pseudowire. For ATM physical interfaces configured with atm-l2circuit-mode cell , you can configure port or VP promiscuous mode. In VP promiscuous mode, all cells with the same VPI are forwarded on a single pseudowire: [edit interfaces at-fpc/pic/port]...
Page 625: Atm Oam
Chapter 28: Configuring ATM Support on Circuit Emulation PICs ATM OAM Circuit Emulation PICs provide ATM support for the following OAM-FM cell types: F4 AIS (end-to-end) F4 RDI (end-to-end) F4 loopback (end-to-end) F5 loopback F5 AIS F5 RDI For information on OAM configuration (for loopback OAM cells) and behavior (for AIS and RDI) see the Network Interfaces Configuration Guide.
Page 626: Congestion Control
JUNOS 10.1 Network Interfaces Configuration Guide Congestion Control ATM encapsulations provide congestion control via EPD thresholds on a per logical interface basis. For Circuit Emulation PICs, the EPD number specifies the number of packets (or frames or cell bundles). [edit interfaces at-fpc/pic/port unit logical-unit-number] epd-threshold packets plp1 packets;...
Page 627: Atm Limitations
Chapter 28: Configuring ATM Support on Circuit Emulation PICs atm-options { pic-type atm-ce; e1-options { framing g704; t1-options { framing sf; NOTE: In the sample configuration above, both T1 and E1 framing are set. Depending on which Circuit Emulation PIC you are using (T1 or E1), only the appropriate options are functional.
Page 628 JUNOS 10.1 Network Interfaces Configuration Guide OAM-FM segment—Segment F4 flows are not supported. Only end-to-end F4 flows are supported. IP and Ethernet encapsulations—IP and Ethernet encapsulations are not supported. F5 OAM—OAM termination is not supported. ATM Limitations...
Page 629: Part 9 Configuring E1, E3, T1, And T3 Interfaces
Part 9 Configuring E1, E3, T1, and T3 Interfaces Configuring E1 Interfaces on page 561 Configuring E3 Interfaces on page 569 Configuring T1 Interfaces on page 577 Configuring T3 Interfaces on page 587 Configuring E1, E3, T1, and T3 Interfaces...
Page 630 JUNOS 10.1 Network Interfaces Configuration Guide Configuring E1, E3, T1, and T3 Interfaces...
Page 631: Chapter 29 Configuring E1 Interfaces
ITU-T Recommendation G.775, Loss of Signal (LOS) and Alarm Indication Signal (AIS) Defect Detection and Clearance Criteria, describes alarm reporting methods. NOTE: The Juniper Networks E1 Physical Interface Card (PIC) does not support Channel Associated Signaling (CAS). Configuring E1 Physical Interface Properties...
Page 632 JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces interface-name] e1-options { bert-error-rate rate; bert-period seconds; fcs (16 | 32); framing (g704 | g704-no-crc4 | unframed); idle-cycle-flag (flags | ones); invert-data; loopback (local | remote); start-end-flag (filler | shared); timeslots time-slot-range; Configuring E1 BERT Properties This section discusses BERT properties for the E1 interface specifically.
Page 633 Chapter 29: Configuring E1 Interfaces hierarchy ce1-fpc/pic/port e1-options] [edit interfaces e1-fpc/pic/port e1-options] level: [edit interfaces ce1-fpc/pic/port e1-options] bert-algorithm algorithm; [edit interfaces e1-fpc/pic/port e1-options] bert-algorithm algorithm; For a list of supported algorithms, enter a after the bert-algorithm statement; for example: [edit interfaces ce1-0/0/0 e1-options] user@host# set bert-algorithm ? Possible completions: pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 standard)
Page 634 JUNOS 10.1 Network Interfaces Configuration Guide framing unframed; To explicitly configure G704 framing, include the framing statement at the [edit hierarchy level, specifying the option: interfaces interface-name e1-options] g704 [edit interfaces interface-name e1-options] framing g704; By default, G704 framing uses CRC4. To explicitly configure an interface s G704 framing to not use CRC4, include the framing statement at the...
Page 635: Example: Configuring E1 Loopback Capability
Chapter 29: Configuring E1 Interfaces E1 interface, forwarded if there is a valid route, and immediately retransmitted to the CSU. Figure 54: Remote and Local E1 Loopback To configure loopback capability on an E1 interface, include the statement loopback at the [edit interfaces interface-name e1-options] hierarchy level: [edit interfaces interface-name e1-options]...
Page 636: Configuring E1 Start And End Flags
JUNOS 10.1 Network Interfaces Configuration Guide With this configuration, the link stays up, so you can loop ping packets to a remote router. The statement causes the interface to loop within the PIC just loopback local before the data reaches the transceiver. [edit interfaces] e1-1/0/0 { no-keepalives;...
Page 637: Example: Configuring Fractional E1 Time Slots
Chapter 29: Configuring E1 Interfaces Time slot numbering constraints vary for different E1 PICs, as follows: For 4-port E1 PICs, the configurable time slot range is 1 through 31 (time slot 0 is reserved for framing). For 10-port Channelized E1 and 10-port Channelized E1 Intelligent Queuing (IQ) PICs, the configurable time slot range is 2 through 32 (time slots 0 and 1 are reserved for framing).
Page 638 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Fractional E1 Time Slots...
Page 639: Chapter 30 Configuring E3 Interfaces
Chapter 30 Configuring E3 Interfaces E3 Interfaces Overview on page 569 Configuring E3 Physical Interface Properties on page 570 Configuring E3 BERT Properties on page 570 Configuring the E3 CSU Compatibility Mode on page 571 Configuring the E3 Frame Checksum on page 572 Configuring the E3 Idle Cycle Flag on page 573 Configuring E3 Data Inversion on page 573 Configuring E3 Loopback Capability on page 573...
Page 640 JUNOS 10.1 Network Interfaces Configuration Guide Configuring E3 Physical Interface Properties To configure E3-specific physical interface properties, include the e3-options statement at the hierarchy level: [edit interfaces interface-name] [edit interfaces interface-name] e3-options { bert-algorithm algorithm; bert-error-rate rate; bert-period seconds; compatibility-mode (digital-link | kentrox | larscom) <subrate value>; fcs (16 | 32);...
Page 641 Chapter 30: Configuring E3 Interfaces For a list of supported algorithms, enter a after the statement; for bert-algorithm example: [edit interfaces e3-0/0/0 e3-options] user@host# set bert-algorithm ? Possible completions: pseudo-2e11-o152 Pattern is 2^11 -1 (per O.152 standard) pseudo-2e15-o151 Pattern is 2^15 - 1 (per O.152 standard) pseudo-2e20-o151 Pattern is 2^20 - 1 (per O.151 standard) pseudo-2e20-o153 Pattern is 2^20 - 1 (per O.153 standard) For specific hierarchy information, see individual interface types.
Page 642: Table 53: Subrate Values For E3 Digital Link Compatibility Mode
JUNOS 10.1 Network Interfaces Configuration Guide Table 53: Subrate Values for E3 Digital Link Compatibility Mode 358 Kbps 7.2 Mbps 14.0 Mbps 20.8 Mbps 27.6 Mbps 716 Kbps 7.5 Mbps 14.3 Mbps 21.1 Mbps 27.9 Mbps 1.1 Mbps 7.9 Mbps 14.7 Mbps 21.5 Mbps 28.3 Mbps...
Page 643 Chapter 30: Configuring E3 Interfaces [edit interfaces interface-name e3-options] fcs 32; To return to the default 16-bit frame checksum, delete the fcs 32 statement from the configuration: [edit] user@host# delete interfaces e3-fpc/pic/port e3-options fcs 32 To explicitly configure a 16-bit checksum, include the statement at the [edit hierarchy level:...
Page 644: Example: Configuring E3 Loopback Capability
JUNOS 10.1 Network Interfaces Configuration Guide Figure 55: Remote and Local E3 Loopback To configure loopback capability on an E3 interface, include the statement loopback at the [edit interfaces interface-name e3-options] hierarchy level: [edit interfaces interface-name e3-options] loopback (local | remote); Packets can be looped on either the local router or the remote CSU.
Page 645: Configuring E3 Hdlc Payload Scrambling
Chapter 30: Configuring E3 Interfaces e3-options { loopback local; unit 0 { family inet { address 10.100.100.1/24; Configuring E3 HDLC Payload Scrambling E3 HDLC payload scrambling, which is disabled by default, provides better link stability. Both sides of a connection must either use or not use scrambling. To configure scrambling on the interface, you can include the payload-scrambler statement at the...
Page 646: Configuring E3 Iq And Iqe Unframed Mode
JUNOS 10.1 Network Interfaces Configuration Guide Configuring E3 IQ and IQE Unframed Mode For E3 IQ and IQE interfaces only, you can enable or disable unframed mode. In unframed mode, the E3 IQ and IQE interfaces do not detect yellow ( ) or loss-of-frame ( ) alarms.
Page 647: Chapter 31 Configuring T1 Interfaces
Chapter 31 Configuring T1 Interfaces T1 Interfaces Overview on page 577 Configuring T1 Physical Interface Properties on page 578 Configuring T1 BERT Properties on page 578 Configuring the T1 Buildout on page 579 Configuring T1 Byte Encoding on page 579 Configuring T1 CRC Error Major Alarm Thresholds on page 580 Configuring T1 CRC Error Minor Alarm Thresholds on page 580 Configuring T1 Data Inversion on page 581...
Page 648 JUNOS 10.1 Network Interfaces Configuration Guide Configuring T1 Physical Interface Properties To configure T1-specific physical interface properties, include the t1-options statement at the hierarchy level: [edit interfaces interface-name] [edit interfaces interface-name] t1-options { bert-algorithm algorithm; bert-error-rate rate; bert-period seconds; buildout value; byte-encoding (nx56 | nx64);...
Page 649 Chapter 31: Configuring T1 Interfaces NOTE: When configuring T1 and CT1 interfaces on 10-port Channelized E1/T1 IQE PICs, the bert-period statement must be included at the [edit interfaces ct1-fpc/pic/port] hierarchy level. is the bit error rate. This can be an integer from 0 through 7, which corresponds rate –0 –7...
Page 650 JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces interface-name t1-options] byte-encoding nx56; To explicitly configure nx64 byte encoding, include the byte-encoding statement at hierarchy level, specifying the [edit interfaces interface-name t1-options] nx64 option: [edit interfaces interface-name t1-options] byte-encoding nx64; Configuring T1 CRC Error Major Alarm Thresholds JUNOS Software collects CRC errors from PICs every second.
Page 651 Chapter 31: Configuring T1 Interfaces [edit interfaces interface-name t1-options] crc-minor-alarm-threshold (1e-3 | 5e-4 | 1e-4 | 5e-5 | 1e-5 | 5e-6 | 1e-6); –4 To configure a T1 CRC error minor alarm for five errors in 10 bits, include the crc-minor-alarm-threshold statement at the [edit interfaces interface-name t1-options]...
Page 652: Configuring The T1 Remote Loopback Response
JUNOS 10.1 Network Interfaces Configuration Guide Configuring the T1 Remote Loopback Response The T1 facilities data-link loop request signal is used to communicate various network information in the form of in-service monitoring and diagnostics. Extended superframe, through the facilities data link (FDL), supports nonintrusive signaling and control, thereby offering clear-channel communication.
Page 653: Configuring T1 Loopback Capability
Chapter 31: Configuring T1 Interfaces ports 2 and 3 must share the same value, but ports 0 and 1 can have a different value from that of ports 2 and 3. Configuring T1 Loopback Capability You can configure loopback capability between the local T1 interface and the remote channel service unit (CSU), as shown in Figure 56 on page 583.
Page 654: Configuring The T1 Idle Cycle Flag
JUNOS 10.1 Network Interfaces Configuration Guide are the same. If you configure one, the other is ignored. NxDS0 IQ interfaces do not support local loopback. To determine whether a problem is internal or external, you can loop packets on both the local and the remote router. To do this, include the no-keepalives encapsulation cisco-hdlc statements at the...
Page 655: Configuring T1 Start And End Flags
Chapter 31: Configuring T1 Interfaces Configuring T1 Start and End Flags By default, a T1 interface shares the transmission of the start and end flags. To configure a T1 interface to wait two idle cycles between the start and end flags, include the statement with the option at the...
Page 656 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Fractional T1 Time Slots...
Page 657: Chapter 32 Configuring T3 Interfaces
Chapter 32 Configuring T3 Interfaces T3 Interfaces Overview on page 587 Configuring T3 Physical Interface Properties on page 588 Configuring T3 BERT Properties on page 588 Disabling T3 C-Bit Parity Mode on page 589 Configuring the T3 CSU Compatibility Mode on page 590 Configuring the T3 Frame Checksum on page 592 Configuring the T3 FEAC Response on page 593 Configuring the T3 Idle Cycle Flag on page 593...
Page 658 JUNOS 10.1 Network Interfaces Configuration Guide Configuring T3 Physical Interface Properties To configure T3-specific physical interface properties, include the t3-options statement at the hierarchy level: [edit interfaces interface-name] [edit interfaces interface-name] t3-options { bert-algorithm algorithm; bert-error-rate rate; bert-period seconds; (cbit-parity | no-cbit-parity); compatibility-mode (adtran | digital-link | kentrox | larscom | verilink) <subrate value>;...
Page 659: Disabling T3 C-Bit Parity Mode
Chapter 32: Configuring T3 Interfaces On T3 interfaces, you can also select the pattern to send in the bit stream by including statement at the bert-algorithm [edit interfaces interface-name interface-options] hierarchy level: [edit interfaces interface-name interface-options] bert-algorithm algorithm; For a list of supported algorithms, enter a after the statement;...
Page 660: Configuring The T3 Csu Compatibility Mode
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces interface-name t3-options] cbit-parity; Configuring the T3 CSU Compatibility Mode Subrating a T3 interface reduces the maximum allowable peak rate by limiting the HDLC-encapsulated payload. Subrate modes configure the PIC to connect with channel service units (CSUs) that use proprietary methods of multiplexing.
Page 661: Table 54: Subrate Values For T3 Digital Link Compatibility Mode
Chapter 32: Configuring T3 Interfaces A subrate value of 1 corresponds to 44.2 / 14, which is 3.16 Mbps, 7.15 percent of the HDLC-encapsulated payload. For Verilink CSUs, specify the subrate as a number from 1 through 28 that exactly matches the value configured on the CSU.
Page 662: Configuring The T3 Frame Checksum
JUNOS 10.1 Network Interfaces Configuration Guide Table 54: Subrate Values for T3 Digital Link Compatibility Mode (continued) 5.7 Mbps 14.7 Mbps 23.8 Mbps 32.8 Mbps 41.8 Mbps 6.0 Mbps 15.0 Mbps 24.1 Mbps 33.1 Mbps 42.1 Mbps 6.3 Mbps 15.3 Mbps 24.4 Mbps 33.4 Mbps 42.4 Mbps...
Page 663: Configuring The T3 Feac Response
Chapter 32: Configuring T3 Interfaces [edit interfaces interface-name t3-options] fcs 16; Configuring the T3 FEAC Response The T3 far-end alarm and control (FEAC) signal is used to send alarm or status information from the far-end terminal back to the near-end terminal and to initiate T3 loopbacks at the far-end terminal from the near-end terminal.
Page 664: Configuring The Channelized T3 Loop Timing
JUNOS 10.1 Network Interfaces Configuration Guide statements apply only to copper-cable-based long-buildout no-long-buildout T3 interfaces. You cannot configure a line buildout for a DS3 channel on a channelized OC12 interface, which runs over fiber-optic cable. If you configure this statement on a channelized OC12 interface, it is ignored.
Page 665: Figure 57: Remote And Local T3 Loopback
Chapter 32: Configuring T3 Interfaces or remote. With local loopback, the T3 interface can transmit packets to the CSU, but receives its own transmission back again and ignores data from the CSU. With remote loopback, packets sent from the CSU are received by the T3 interface, forwarded if there is a valid route, and immediately retransmitted to the CSU.
Page 666: Configuring T3 Hdlc Payload Scrambling
JUNOS 10.1 Network Interfaces Configuration Guide encapsulation cisco-hdlc; t3-options { loopback local; unit 0 { family inet { address 10.100.100.1/24; With this configuration, the link stays up, so you can loop ping packets to a remote router. The statement causes the interface to loop within the PIC just loopback local before the data reaches the transceiver.
Page 667: Configuring T3 Start And End Flags
Chapter 32: Configuring T3 Interfaces If you enable HDLC payload scrambling on a T3 interface, you must also configure the interface to be compatible with the channel service unit (CSU) at the remote end of the line before you commit the interface configuration. For information about subrating a T3 interface, see “Configuring the T3 CSU Compatibility Mode”...
Page 668 JUNOS 10.1 Network Interfaces Configuration Guide unit 0 { family inet { address 10.0.0.1/32 { destination 10.0.0.2; family iso; Cisco HDLC [edit] interfaces { Encapsulation on a DS3 t3-0/0/1 { encapsulation cisco-hdlc; t3-options { no-long-buildout; compatibility-mode larscom; payload-scrambler; unit 0 { family inet { address 10.0.0.1/32 { destination 10.0.0.2;...
Page 669 Chapter 32: Configuring T3 Interfaces family inet { address 10.0.0.3/32 { destination 10.0.0.4; family iso; On DCE Router [edit] interfaces { t3-1/1/1 { dce; encapsulation frame-relay; t3-options { no-long-buildout; compatibility-mode larscom; payload-scrambler; unit 1 { dlci 1; family inet { address 10.0.0.2/32 { destination 10.0.0.1;...
Page 670 JUNOS 10.1 Network Interfaces Configuration Guide Examples: Configuring T3 Interfaces...
Page 671: Part 10 Configuring Ethernet Interfaces
Part 10 Configuring Ethernet Interfaces Configuring Ethernet Interfaces on page 603 Configuring 802.1Q VLANs on page 619 Configuring Aggregated Ethernet Interfaces on page 643 Stacking and Rewriting Gigabit Ethernet VLAN Tags on page 665 Configuring Layer 2 Bridging Interfaces on page 687 Configuring TCC and Layer 2.5 Switching on page 689 Configuring Static ARP Table Entries on page 693 Configuring Unrestricted Proxy ARP on page 695...
Page 672 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Ethernet Interfaces...
Page 673: Ethernet Interfaces Overview
10Base-T. More recently, 100Base-TX (Fast Ethernet, 100 Mbps), Gigabit Ethernet (1 gigabit per second [Gbps]), and 10-Gigabit Ethernet (10 Gbps) have become available. Juniper Networks routers support the following types of Ethernet interfaces: Fast Ethernet Tri-Rate Ethernet copper...
Page 674 JUNOS 10.1 Network Interfaces Configuration Guide Gigabit Ethernet IQ2 and IQ2-E 10-Gigabit Ethernet IQ2 and IQ2-E 10-Gigabit Ethernet 10-Gigabit Ethernet dense wavelength-division multiplexing (DWDM) Management Ethernet interface, which is an out-of-band management interface within the router Internal Ethernet interface, which connects the Routing Engine to the packet forwarding components Aggregated Ethernet interface, a logical linkage of Fast Ethernet, Gigabit Ethernet, or 10-Gigabit Ethernet physical connections...
Page 675 Chapter 33: Configuring Ethernet Interfaces NOTE: The statement applies to the management Ethernet interface ( speed fxp0 ), the Fast Ethernet 12-port and 48-port Physical Interface Card (PIC) interfaces, the J Series Gigabit Ethernet uPIM interfaces and the MX Series Tri-Rate Ethernet copper interfaces.
Page 676 JUNOS 10.1 Network Interfaces Configuration Guide To configure Gigabit Ethernet IQ-specific physical interface properties, include the statement at the hierarchy level. These gigether-options [edit interfaces ge-fpc/pic/port] statements are supported on 10-Gigabit Ethernet IQ2 and IQ2-E PIC. Some of these statements are also supported on Gigabit Ethernet PICs with small form-factor pluggable transceivers (SFPs) (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router).
Page 677 Chapter 33: Configuring Ethernet Interfaces xe-0/0/0 { framing { (lan-phy | wan-phy); To configure OAM 802.3ah support for Ethernet interfaces, include the statement at the [edit protocols] hierarchy level. oam { ethernet { link-fault-management { interfaces { interface-name{ pdu-interval interval; link-discovery (active | passive);...
Page 678 JUNOS 10.1 Network Interfaces Configuration Guide To configure aggregated Ethernet-specific physical interface properties, include the statement at the hierarchy level: aggregated-ether-options [edit interfaces aex] [edit interfaces aex] aggregated-ether-options { ethernet-switch-profile { tag-protocol-id tpid; (flow-control | no-flow-control); lacp mode { periodic interval; link-protection;...
Page 679: Example: Configuring J Series Services Router Switching Interfaces
Chapter 33: Configuring Ethernet Interfaces link-mode (full-duplex | half-duplex); Access switching mode is supported on the 6-port, 8-port, and 16-port Gigabit Ethernet uPIMs. The multiport Gigabit Ethernet uPIMs are supported on the J2320, J2350, J4350, and J6350 Services Routers. The 6-port and 8-port multiport Gigabit Ethernet uPIM occupies a single slot and can be installed in any slot.
Page 680: Enabling Ethernet Mac Address Filtering
JUNOS 10.1 Network Interfaces Configuration Guide Ports are numbered from 0 through 9 for Gigabit Ethernet and Tri-Rate Ethernet copper interfaces. Port numbers are always 0 for 10-Gigabit Ethernet interfaces. NOTE: In certain displays, the MX Series routers identify the Packet Forwarding Engine (PFE) rather than the PIC number.
Page 681: Filtering Specific Mac Addresses
Chapter 33: Configuring Ethernet Interfaces Filtering Specific MAC Addresses When source address filtering is enabled, you can configure the interface to receive packets from specific MAC addresses. To do this, specify the MAC addresses in the statement: source-address-filter source-address-filter { mac-address;...
Page 682: Configuring Ethernet Loopback Capability
JUNOS 10.1 Network Interfaces Configuration Guide NOTE: On untagged Gigabit Ethernet interfaces, you should not configure the source-address-filter statement at the [edit interfaces ge-fpc/pic/port gigether-options] hierarchy level and the statement at the accept-source-mac [edit interfaces ge-fpc/pic/port gigether-options unit logical-unit-number] hierarchy level simultaneously. If these statements are configured for the same interfaces at the same time, an error message is displayed.
Page 683: Configuring Flow Control
Chapter 33: Configuring Ethernet Interfaces Configuring Flow Control By default, the routing platform imposes flow control to regulate the amount of traffic sent out on a Fast Ethernet, Tri-Rate Ethernet copper, Gigabit Ethernet, and 10-Gigabit Ethernet interface. Flow control is not supported on the 4-port Fast Ethernet PIC. This is useful if the remote side of the connection is a Fast Ethernet or Gigabit Ethernet switch.
Page 684: Configuring Gratuitous Arp
JUNOS 10.1 Network Interfaces Configuration Guide interfaces can operate only in full-duplex mode. For Gigabit Ethernet and 10-Gigabit Ethernet, the link partner must also be set to full duplex. NOTE: For M Series, MX Series, and most T Series routers, the management Ethernet interface is .
Page 685: Adjusting The Arp Aging Timer
Chapter 33: Configuring Ethernet Interfaces By default, the router responds to gratuitous ARP requests. On Ethernet interfaces, you can disable responses to gratuitous ARP requests. To disable responses to gratuitous ARP requests, include the statement at the no-gratuitous-arp-request [edit interfaces interface-name] hierarchy level: [edit interfaces interface-name] no-gratuitous-arp-request;...
Page 686: Configuring The Interface Speed On Ethernet Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Configuring the Interface Speed on Ethernet Interfaces For M Series and T Series Fast Ethernet 12-port and 48-port PIC interfaces, the management Ethernet interface ( fxp0 ), the J Series Gigabit Ethernet uPIM interfaces, and the MX Series Tri-Rate Ethernet copper interfaces, you can explicitly set the interface speed.
Page 687 Chapter 33: Configuring Ethernet Interfaces For information on configuring WRED, see the JUNOS Class of Service Configuration Related Topics Guide. Configuring Weighted Random Early Detection...
Page 688 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Weighted Random Early Detection...
Page 689: Chapter 34 Configuring 802.1Q Vlans
Chapter 34 Configuring 802.1Q VLANs 802.1Q VLANs Overview on page 619 Configuring Dynamic 802.1Q VLANs on page 620 802.1Q VLAN IDs and Ethernet Interface Types on page 620 Enabling VLAN Tagging on page 621 Binding VLAN IDs to Logical Interfaces on page 624 Configuring VLAN Encapsulation on page 629 Configuring Extended VLAN Encapsulation on page 630 Guidelines for Configuring VLAN ID List-Bundled Logical Interfaces That Connect...
Page 690: Table 55: Vlan Id Range By Interface Type
JUNOS 10.1 Network Interfaces Configuration Guide Configuring Dynamic 802.1Q VLANs You can configure the router to dynamically create VLANs when a client accesses an interface and requests a VLAN ID that does not yet exist. When a client accesses a VLAN interface, the router instantiates a VLAN dynamic profile that you have associated with the interface.
Page 691: Configuring Single-Tag Framing
Chapter 34: Configuring 802.1Q VLANs Table 55: VLAN ID Range by Interface Type (continued) Interface Type VLAN ID Range 48-port Fast Ethernet 1 through 4094 Tri-Rate Ethernet copper 1 through 4094 Gigabit Ethernet 1 through 4094 Gigabit Ethernet IQ 1 through 4094 10-Gigabit Ethernet 1 through 4094 Management and internal Ethernet interfaces...
Page 692 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Single-Tag Framing To configure the router to receive and forward single-tag frames with 802.1Q VLAN tags, include the statement at the hierarchy vlan-tagging [edit interfaces interface-name] level: [edit interfaces interface-name] vlan-tagging; Configuring Dual Tagging To configure the routing platform to receive and forward dual-tag frames with 802.1Q VLAN tags, include the stacked-vlan-tagging...
Page 693 Chapter 34: Configuring 802.1Q VLANs NOTE: When you configure the physical interface MTU for mixed tagging, you must increase the MTU to 4 bytes more than the MTU value you would configure for a standard VLAN-tagged interface. For example, if the MTU value is configured to be 1018 on a VLAN-tagged interface, then the MTU value on a flexible VLAN tagged interface must be 1022—4 bytes more.
Page 694: Binding Vlan Ids To Logical Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide For information about binding VLAN IDs to logical interfaces, see “Binding VLAN IDs to Logical Interfaces” on page 624. For information about configuring dual VLAN tags using the vlan-tag statement, see “Stacking a VLAN Tag” on page 673. Example: Configuring Mixed Tagging to Support Untagged Packets The following example configures untagged packets to be mapped to logical unit number 0:...
Page 695: Binding A Vlan Id To A Single-Tag Logical Interface
Chapter 34: Configuring 802.1Q VLANs Table 56: Configuration Statements Used to Bind VLAN IDs to Logical Interfaces Type of VLAN Framing Supported on the Logical Interface Scope of VLAN ID Matching Single-Tag Framing Dual-Tag Framing VLAN ID vlan-id vlan-id; vlan-tags outer tpid.<vlan-id> inner tpidvlan-id; VLAN ID Range vlan-id-range vlan-id vlan-id;...
Page 696: Binding A Range Of Vlan Ids To A Logical Interface
JUNOS 10.1 Network Interfaces Configuration Guide You can include the statement at the following hierarchy levels: [edit interfaces ethernet-interface-name unit logical-unit-number] [edit logical-systems logical-system-name interfaces ethernet-interface-name unit logical-unit-number] To configure an Ethernet interface to support dual-tag logical interfaces, include the stacked-vlan-tagging statement at the [edit interfaces ethernet-interface-name]...
Page 697: Example: Binding Ranges Vlan Ids To Logical Interfaces
Chapter 34: Configuring 802.1Q VLANs Example: Binding Ranges VLAN IDs to Logical Interfaces The following example configures two different ranges of VLAN IDs on two different logical ports: [edit interfaces] ge-3/0/0 { unit 0 { encapsulation vlan-bridge; vlan-id-range 500-600; ge-3/0/1 { flexible-vlan-tagging;...
Page 698: Binding A List Of Vlan Ids To A Dual-Tag Logical Interface
JUNOS 10.1 Network Interfaces Configuration Guide [edit logical-systems logical-system-name interfaces ethernet-interface-name unit logical-unit-number] To configure an Ethernet interface to support single-tag logical interfaces, include statement at the hierarchy vlan-tagging [edit interfaces ethernet-interface-name] level. To support mixed tagging, include the flexible-vlan-tagging statement instead.
Page 699: Configuring Vlan Encapsulation
Chapter 34: Configuring 802.1Q VLANs encapsulation vlan-ccc; vlan-tags outer 200 inner-list [50 60 80 90 100]; In the example configuration above, supports single-tag logical interfaces, ge-1/1/0 ge-1/1/1 supports mixed tagging. The single-tag logical interfaces ge-1/1/0.10 each bundle lists of VLAN IDs. The dual-tag logical interface ge-1/1/1.20 ge-1/1/1.20 bundles lists of inner VLAN IDs.
Page 700: Example: Configuring Vlan Encapsulation On A Gigabit Ethernet Interface
JUNOS 10.1 Network Interfaces Configuration Guide [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] You cannot configure a logical interface with VLAN CCC or VLAN VPLS encapsulation unless you also configure the physical device with the same encapsulation or with flexible Ethernet services encapsulation. In general, the logical interface must have a VLAN ID of 512 or higher;...
Page 701: Example: Configuring Extended Vlan Encapsulation On A Gigabit Ethernet Interface
Chapter 34: Configuring 802.1Q VLANs NOTE: For extended VLAN CCC, the VLAN IDs on ingress and egress interfaces must be the same. For back-to-back connections, all VLAN IDs must be the same. Example: Configuring Extended VLAN Encapsulation on a Gigabit Ethernet Interface Configure extended VLAN CCC encapsulation on Gigabit Ethernet ingress and egress interfaces: interfaces ge-0/0/0 {...
Page 702: Guidelines For Configuring Vlan Id List-Bundled Logical Interfaces That Connect Cccs
JUNOS 10.1 Network Interfaces Configuration Guide Guidelines for Configuring VLAN ID List-Bundled Logical Interfaces That Connect CCCs For MX Series routers, you can bind a list of VLAN IDs to a logical interface, configure a Layer 2 VPN routing instance or Layer 2 circuit on the logical interface, and then use the logical interface to configure a circuit cross-connect (CCC) to another Layer 2 VPN routing instance or Layer 2 circuit.
Page 703: Table 57: Encapsulation Inside Circuits Ccc-Connected By Vlan-Bundled
Chapter 34: Configuring 802.1Q VLANs Table 57 on page 633 describes the logical link-layer encapsulation types used within circuits connected using VLAN-bundled logical interfaces of the same type. Table 57: Encapsulation Inside Circuits CCC-Connected by VLAN-Bundled Logical Interfaces Encapsulation Layer 2 Circuit Joined by Configuring an Interface-to-Interface CCC Connection Inside the Circuit Layer 2 VPN Routing Instance...
Page 704: Configuring A Layer 2 Vpn Routing Instance On A Vlan-Bundled Logical Interface
JUNOS 10.1 Network Interfaces Configuration Guide Configuring a Layer 2 VPN Routing Instance on a VLAN-Bundled Logical Interface This topic describes how to configure a Layer 2 VPN routing instance on a logical interface bound to a list of VLAN IDs. Configuring a VLAN-Bundled Logical Interface on page 634 Specifying the Interface Over Which VPN Traffic Travels to the CE Router on page 634...
Page 705: Configuring A Layer 2 Circuit On A Vlan-Bundled Logical Interface
Chapter 34: Configuring 802.1Q VLANs Specifying the Interface to Handle Traffic for a CCC To configure the VLAN-bundled logical interface as the interface to handle traffic for a circuit connected to the Layer 2 VPN routing instance, include the following statements: protocols { l2vpn {...
Page 706: Specifying The Interface To Handle Traffic For A Ccc Connected To The Layer 2 Circuit
JUNOS 10.1 Network Interfaces Configuration Guide Configuring a VLAN-Bundled Logical Interface To configure a VLAN-bundled logical interface, specify the list of VLAN IDs by including statement or the statement: vlan-id-list vlan-tags interfaces { ethernet-interface-name { vlan-tagging; # Support single- or dual-tag logical interfaces flexible-vlan-tagging;...
Page 707: Example: Configuring A Layer 2 Vpn Routing Instance On A Vlan-Bundled Logical Interface
Chapter 34: Configuring 802.1Q VLANs To configure the router as a neighbor for a Layer 2 circuit, specify the neighbor address using the statement. neighbor To specify the interface to handle traffic for a circuit connected to the Layer 2 circuit, include the interface statement and specify the VLAN-bundled logical interface.
Page 708: Example: Configuring A Layer 2 Circuit On A Vlan-Bundled Logical Interface
JUNOS 10.1 Network Interfaces Configuration Guide traffic-engineering; area 0.0.0.0 { interface lo0.0; interface ge-1/1/1.0; The following configuration shows that the VLAN-bundled logical interface is the interface over which VPN traffic travels to the CE router and handles traffic for a CCC to which the VPN connects.
Page 709: Configuring A Logical Interface For Access Mode
Chapter 34: Configuring 802.1Q VLANs family inet { address 10.30.1.1/30; family mpls; The following configuration shows the type of traffic supported on the Layer 2 VPN routing instance, and shows that the VLAN-bundled logical interface handles traffic for a CCC to which the Layer 2 circuit connects: [edit protocols] rsvp { interface all;...
Page 710: Example: Configuring A Logical Interface For Access Mode
JUNOS 10.1 Network Interfaces Configuration Guide [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family bridge] When an untagged or tagged packet is received on an access interface, the packet is accepted, the VLAN ID is added to the packet, and the packet is forwarded within the bridge domain that is configured with the matching VLAN ID.
Page 711: Configuring A Trunk Interface On A Bridge Network
Chapter 34: Configuring 802.1Q VLANs You can include this statement at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family bridge interface-mode trunk] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family bridge interface-mode trunk] When a packet is received that is tagged with a VLAN ID specified in the trunk interface list of VLAN IDs, the packet is accepted and forwarded within the bridge domain that is configured with the matching VLAN ID.
Page 712 JUNOS 10.1 Network Interfaces Configuration Guide Configuring a Trunk Interface on a Bridge Network...
Page 713: Configuring Aggregated Ethernet Interfaces
Chapter 35 Configuring Aggregated Ethernet Interfaces Aggregated Ethernet Interfaces Overview on page 643 Configuring an Aggregated Ethernet Interface on page 645 Deleting an Aggregated Ethernet Interface on page 646 Configuring Multi-Chassis Link Aggregation on page 646 Configuring Aggregated Ethernet Link Protection on page 647 Configuring the Number of Aggregated Ethernet Interfaces on the Device on page 649 Configuring Aggregated Ethernet LACP on page 649...
Page 714: Platform Support For Aggregated Ethernet Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Platform Support for Aggregated Ethernet Interfaces You configure an aggregated Ethernet virtual link by specifying the link number as a physical device and then associating a set of ports that have the same speed and are in full-duplex mode.
Page 715: Configuring An Aggregated Ethernet Interface
Chapter 35: Configuring Aggregated Ethernet Interfaces rewrite operations on dual-tagged frames, which consist of the following configuration statements: inner-tag-protocol-id inner-vlan-id pop-pop pop-swap push-push swap-push swap-swap In all cases, you must set the number of aggregated Ethernet interfaces on the chassis. You can also set the link speed and the minimum links in a bundle.
Page 716: Deleting An Aggregated Ethernet Interface
JUNOS 10.1 Network Interfaces Configuration Guide Configuring the Number of Aggregated Ethernet Interfaces on the Device on Related Topics page 649 Deleting an Aggregated Ethernet Interface on page 646 Aggregated Ethernet Interfaces Overview on page 643 Deleting an Aggregated Ethernet Interface There are two approaches to deleting an aggregated Ethernet interface: You can delete an aggregated Ethernet interface from the interface configuration.
Page 717: Configuring Aggregated Ethernet Link Protection
Chapter 35: Configuring Aggregated Ethernet Interfaces On one end of MC-LAG is an MC-LAG client device that has one or more physical links in a link aggregation group (LAG). This client device does not need to be aware of MC-LAG. On the other side of MC-LAG are two MC-LAG network devices. Each of these network devices has one or more physical links connected to a single client device.
Page 718 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Link Protection for Aggregated Ethernet Interfaces Aggregated Ethernet interfaces support link protection to ensure QoS on the interface. To configure link protection: Specify that you want to configure the options for an aggregated Ethernet interface.
Page 719: Configuring The Number Of Aggregated Ethernet Interfaces On The Device
Chapter 35: Configuring Aggregated Ethernet Interfaces Disabling Link Protection for Aggregated Ethernet Interfaces To disable link protection, issue the request interface revert aex operational command. user@host# delete interfaces aex aggregated-ether-options link-protection Configuring the Number of Aggregated Ethernet Interfaces on the Device By default, no aggregated Ethernet interfaces are created.
Page 720: Configuring The Lacp Interval
JUNOS 10.1 Network Interfaces Configuration Guide LACP exchanges are made between actors and partners. An actor is the local interface in an LACP exchange. A partner is the remote interface in an LACP exchange. LACP is defined in IEEE 802.3ad, Aggregation of Multiple Link Segments. LACP was designed to achieve the following: Automatic addition and deletion of individual links to the aggregate bundle without user intervention...
Page 721 Chapter 35: Configuring Aggregated Ethernet Interfaces [edit interfaces interface-name aggregated-ether-options lacp] periodic interval; The interval can be fast (every second) or slow (every 30 seconds). You can configure different periodic rates on active and passive interfaces. When you configure the active and passive interfaces at different rates, the transmitter honors the receiver s rate.
Page 722: Enabling Lacp Link Protection
JUNOS 10.1 Network Interfaces Configuration Guide Enabling LACP Link Protection To enable LACP link protection for an aggregated Ethernet interfaces, use the link-protection statement at the [ edit interfaces aeX aggregated-ether-options lacp] hierarchy level: [edit interfaces aeX aggregated-ether-options lacp] link-protection; disable;...
Page 723: Configuring Lacp Port Priority
Chapter 35: Configuring Aggregated Ethernet Interfaces Configuring LACP Port Priority To configure LACP port priority for aggregated Ethernet interfaces, use the port-priority statement at the [edit interfaces interface-name gigether-options 802.3ad aeX lacp] [edit interfaces interface-name fastether-options 802.3ad aeX lacp] hierarchy levels: [edit interfaces interface-name gigether-options 802.3ad aeX lacp] port-priority priority;...
Page 724: Example: Configuring Aggregated Ethernet Lacp
JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring Aggregated Ethernet LACP Configure aggregated Ethernet LACP over a VLAN-tagged interface: LACP with VLAN-Tagged [edit interfaces] fe-5/0/1 { Aggregated Ethernet fastether-options { 802.3ad ae0; ae0 { aggregated-ether-options { lacp { active; vlan-tagging; unit 0 { vlan-id 100;...
Page 725: Configuring Untagged Aggregated Ethernet Interfaces
Chapter 35: Configuring Aggregated Ethernet Interfaces Configuring Untagged Aggregated Ethernet Interfaces When you configure an untagged Aggregated Ethernet interface, the existing rules for untagged interfaces apply. These rules are as follows: You can configure only one logical interface (unit 0) on the port. The logical unit 0 is used to send and receive LACP or marker protocol data units (PDUs) to and from the individual links.
Page 726: Example: Configuring Untagged Aggregated Ethernet Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring Untagged Aggregated Ethernet Interfaces Configure an untagged aggregated Ethernet interface by omitting the vlan-tagging vlan-id statements from the configuration: [edit interfaces] fe-5/0/1 { fastether-options { 802.3ad ae0; ae0 { unit 0 { family inet { address 13.1.1.2/24 { vrrp-group 0 {...
Page 727: Configuring Aggregated Ethernet Minimum Links
Chapter 35: Configuring Aggregated Ethernet Interfaces —Links are 100 Mbps. 100m —Links are 10 Gbps. —Links are 1 Gbps. OC192 —Links are OC192 or STM64c. Configuring Aggregated Ethernet Minimum Links On aggregated Ethernet interfaces, you can configure the minimum number of links that must be up for the bundle as a whole to be labeled .
Page 728: Configuring Symmetrical Load Balancing On An 802.3Ad Link Aggregation Group On Mx Series Routers
JUNOS 10.1 Network Interfaces Configuration Guide To configure the hierarchical scheduler on aggregated Ethernet interfaces in the non link-protect mode, include the statement at the hierarchical-scheduler [edit interfaces aeX] hierarchy level: [edit interfaces aeX hierarchical-scheduler] Prior to JUNOS Release 9.6, the hierarchical scheduler mode on these models required statement option, otherwise a configuration aggregated-ether-options...
Page 729: Figure 58: Symmetric Load Balancing On An 802.3Ad Lag On Mx Series
Chapter 35: Configuring Aggregated Ethernet Interfaces By using this feature, a given flow of traffic (duplex) is ensured for the same devices in both directions. Symmetrical load balancing on an 802.3ad LAG utilizes a mechanism of interchanging the source and destination addresses for a hash computation of fields, such as source address and destination address.
Page 730 JUNOS 10.1 Network Interfaces Configuration Guide connected, so that the traffic flows through the same DPI devices in both directions. To make sure this happens, you need to also configure the counterpart ports (ports that are connected to same DPI-iN) with the identical link index. This is done when configuring a child-link into the LAG bundle.
Page 731 Chapter 35: Configuring Aggregated Ethernet Interfaces layer-3; layer-4; symmetric-hash { [complement;] family multiservice { source-mac; destination-mac; payload { ip { layer-3 { source-ip-only | destination-ip-only; layer-4; symmetric-hash { [complement;] For load-balancing Layer 2 traffic based on Layer 3 fields, you can configure 802.3ad LAG parameters at a per PIC level.
Page 732: Example Configurations
JUNOS 10.1 Network Interfaces Configuration Guide Example Configurations Example Configurations of Chassis Wide Settings Router A user@host> show configuration forwarding-options hash-key family multiservice { payload { ip { layer-3; symmetric hash; user@host> show configuration forwarding-options hash-key Router B family multiservice { payload { ip { layer-3;...
Page 733 Chapter 35: Configuring Aggregated Ethernet Interfaces symmetric-hash { complement; Configuring Symmetrical Load Balancing on an 802.3ad Link Aggregation Group on MX Series Routers...
Page 734 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Symmetrical Load Balancing on an 802.3ad Link Aggregation Group on MX Series Routers...
Page 735: Stacking And Rewriting Gigabit Ethernet Vlan Tags
Chapter 36 Stacking and Rewriting Gigabit Ethernet VLAN Tags Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 665 Stacking and Rewriting Gigabit Ethernet VLAN Tags on page 666 Configuring Frames with Particular TPIDs to Be Processed as Tagged Frames on page 668 Configuring Stacked VLAN Tagging on page 669 Configuring Dual VLAN Tags on page 669...
Page 736 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: On IQ2 and IQ2-E interfaces and MX Series interfaces, when a VLAN tag is pushed, the inner VLAN IEEE 802.1p bits are copied to the IEEE bits of the VLAN or VLANs being pushed. If the original packet is untagged, the IEEE bits of the VLAN or VLANs being pushed are set to 0.
Page 737: Table 59: Rewrite Operations On Untagged, Single-Tagged, And Dual-Tagged
Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] The type of VLAN rewrite operation permitted depends upon whether the frame is single-tagged or dual-tagged. Table 59 on page 667 shows supported rewrite operations and whether they can be applied to single-tagged frames or dual-tagged frames.
Page 738: Configuring Frames With Particular Tpids To Be Processed As Tagged Frames
JUNOS 10.1 Network Interfaces Configuration Guide operation is applied to it. The resulting frame will be dual-tagged at the push-push logical interface output. Depending on the VLAN rewrite operation, you configure the rewrite operation for the interface in the input VLAN map, the output VLAN map, or in both the input VLAN map and the output VLAN map.
Page 739: Configuring Stacked Vlan Tagging
Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags tag-protocol-id [ tpids ]; You can include this statement at the following hierarchy levels: [edit interfaces interface-name gigether-options ethernet-switch-profile] [edit interfaces interface-name aggregated-ether-options ethernet-switch-profile] All TPIDs you include in input and output VLAN maps must be among those you specify at the [edit interfaces interface-name gigether-options ethernet-switch-profile tag-protocol-id [ tpids ]]...
Page 740 JUNOS 10.1 Network Interfaces Configuration Guide On Ethernet IQ, IQ2, and IQ2-E interfaces; on MX Series router Gigabit Ethernet, Tri-Rate Ethernet copper, and 10-Gigabit Ethernet interfaces; and on aggregated Ethernet interfaces using Gigabit Ethernet IQ2 and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers, to configure the inner TPID, include the inner-tag-protocol-id statement:...
Page 741: Table 61: Rewrite Operations And Statement Usage For Input Vlan
Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] The VLAN IDs you define in the input VLAN maps are stacked on top of the VLAN ID bound to the logical interface. For more information about binding a VLAN ID to the logical interface, see “802.1Q VLANs Overview”...
Page 742: Table 62: Rewrite Operations And Statement Usage For Output Vlan
JUNOS 10.1 Network Interfaces Configuration Guide Table 62: Rewrite Operations and Statement Usage for Output VLAN Maps Output VLAN Map Statements Rewrite Operation vlan-id tag-protocol-id inner-vlan-id inner-tag-protocol-id Optional push Optional swap Optional Optional push-push Optional Optional swap-push Optional Optional swap-swap Optional pop-swap pop-pop...
Page 743: Stacking A Vlan Tag
Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags Stacking a VLAN Tag To stack a VLAN tag on all tagged frames entering or exiting the interface, include push vlan-id , and tag-protocol-id statements in the input VLAN map or the output VLAN map: input-vlan-map { push;...
Page 744: Removing The Outer And Inner Vlan Tags
JUNOS 10.1 Network Interfaces Configuration Guide [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number input-vlan-map] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number output-vlan-map] Removing the Outer and Inner VLAN Tags On Ethernet IQ, IQ2 and IQ2-E interfaces, on MX Series router Gigabit Ethernet, Tri-Rate Ethernet copper, and 10-Gigabit Ethernet interfaces, and on aggregated Ethernet interfaces using Gigabit Ethernet IQ2 and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers, to remove both the outer and inner VLAN tags of the frame,...
Page 745: Stacking Two Vlan Tags
Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number input-vlan-map] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number output-vlan-map] See Table 61 on page 671 and Table 62 on page 672 for information about configuring inner and outer VLAN ID values and inner and outer TPID values required for VLAN maps.
Page 746: Rewriting A Vlan Tag On Untagged Frames
JUNOS 10.1 Network Interfaces Configuration Guide swap; vlan-id number; tag-protocol-id tpid; You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number input-vlan-map] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number input-vlan-map] You cannot include both the swap statement and the vlan-id...
Page 747: Table 63: Input Vlan Map Statements Allowed For Ethernet-Ccc And
Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags IQ2 and 10-Gigabit Ethernet PICs support all rewrite operations described above. Details on the possible combinations of usage are explained later in this section. NOTE: The push-push pop-pop operations are not supported on the Gigabit Ethernet IQ PIC.
Page 748 JUNOS 10.1 Network Interfaces Configuration Guide Table 65: Rules for Applying Rewrite Operations to VLAN Maps (continued) push-push ge-3/1/0 { Example: push and pop encapsulation ethernet-ccc; with Ethernet CCC unit 0 { Encapsulation encapsulation ethernet-ccc; input-vlan-map { push; tag-protocol-id 0x8100; vlan-id 600;...
Page 749: Rewriting A Vlan Tag And Adding A New Tag
Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags Example: push-push and ge-3/1/0 { encapsulation ethernet-vpls; pop-pop with Ethernet unit 0 { VPLS Encapsulation encapsulation ethernet-vpls; input-vlan-map { push-push; tag-protocol-id 0x8100; inner-tag-protocol-id 0x8100; vlan-id 600; inner-vlan-id 575; output-vlan-map pop-pop; family vpls; You can use the show interface interface-name command to display the status of a...
Page 750: Examples: Stacking And Rewriting Gigabit Ethernet Iq Vlan Tags
JUNOS 10.1 Network Interfaces Configuration Guide Ethernet interfaces using Gigabit Ethernet IQ2 and IQ2-E or 10-Gigabit Ethernet PICs on MX Series routers, to replace both the inner and the outer VLAN tags of the incoming frame with a user-specified VLAN tag value, include the statement swap-swap in the input VLAN map or output VLAN map:...
Page 751 Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags encapsulation vlan-ccc; gigether-options { ethernet-switch-profile { tag-protocol-id 0x9909; unit 0 { encapsulation vlan-ccc; vlan-id 512; input-vlan-map { push; tag-protocol-id 0x9909; vlan-id 520; output-vlan-map pop; ge-4/2/0 { vlan-tagging; encapsulation vlan-ccc; unit 0 { encapsulation vlan-ccc;...
Page 752 JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces] Swap a VLAN ID on ge-4/0/0 { Ingress vlan-tagging; encapsulation vlan-ccc; gigether-options { ethernet-switch-profile { tag-protocol-id 0x9100; unit 1 { encapsulation vlan-ccc; vlan-id 1000; input-vlan-map { swap; tag-protocol-id 0x9100; vlan-id 2000; ge-4/2/0 { vlan-tagging;...
Page 753 Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags unit 1 { encapsulation vlan-ccc; vlan-id 1000; ge-4/2/0 { vlan-tagging; encapsulation vlan-ccc; gigether-options { ethernet-switch-profile { tag-protocol-id 0x8800; unit 1 { encapsulation vlan-ccc; vlan-id 2000; output-vlan-map { swap; tag-protocol-id 0x8800; [edit protocols] mpls { interface ge-4/0/0.1;...
Page 754 JUNOS 10.1 Network Interfaces Configuration Guide ge-4/2/0 { vlan-tagging; encapsulation vlan-ccc; gigether-options { ethernet-switch-profile { tag-protocol-id [ 0x8800 0x9100 ]; unit 1 { encapsulation vlan-ccc; vlan-id 2000; output-vlan-map { swap; tag-protocol-id 0x8800; [edit protocols] mpls { interface ge-4/0/0.1; interface ge-4/2/0.1; connections { interface-switch vlan-tag-swap { interface ge-4/2/0.1;...
Page 755 Chapter 36: Stacking and Rewriting Gigabit Ethernet VLAN Tags unit 0 { Tags on Ingress and on vlan-tags { Egress inner 0x9100.425; outer 0x9200.525; input-vlan-map { swap-swap; tag-protocol-id 0x9100; vlan-id 400; inner-tag-protocol-id 0x9100; inner-vlan-id 500; output-vlan-map { swap-swap; tag-protocol-id 0x9200; inner-tag-protocol-id 0x9100;...
Page 756 JUNOS 10.1 Network Interfaces Configuration Guide Pop an Outer VLAN Tag [edit interfaces] ge-1/1/0 { to Connect an Untagged vlan-tagging; VPLS Interface to encapsulation extended-vlan-vpls; Tagged VPLS Interfaces unit 0 { vlan-id 0; input-vlan-map { push; vlan-id 0; output-vlan-map pop; family vpls;...
Page 757: Configuring Layer 2 Bridging Interfaces
Chapter 37 Configuring Layer 2 Bridging Interfaces Layer 2 Bridging Interfaces Overview on page 687 Configuring Layer 2 Bridging Interfaces on page 687 Layer 2 Bridging Interfaces Overview Bridging operates at Layer 2 of the OSI reference model while routing operates at Layer 3.
Page 758: Example: Configuring Layer 2 Bridging Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide unit logical-unit-number { family inet { address address { For examples of Layer 2 bridging configuration, see the JUNOS Routing Protocols Configuration Guide. Example: Configuring Layer 2 Bridging Interfaces The following example configures an IRB logical interface and Layer 3 information on the interface.
Page 759: Configuring Tcc And Layer 2.5 Switching
Chapter 38 Configuring TCC and Layer 2.5 Switching TCC and Layer 2.5 Switching Overview on page 689 Configuring VLAN TCC Encapsulation on page 689 Configuring Ethernet TCC on page 690 TCC and Layer 2.5 Switching Overview Translational cross-connect (TCC) is a switching concept that allows you to forward traffic between a variety of Layer 2 protocols or circuits.
Page 760 JUNOS 10.1 Network Interfaces Configuration Guide (inet-address | mac-address); You can include these statements at the following hierarchy levels: [edit interfaces interface-name unit logical-unit-number family tcc] [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number family tcc] The proxy address is the IP address of the non-Ethernet TCC neighbor for which the TCC router is acting as a proxy.
Page 761: Example: Configuring An Ethernet Tcc Or Extended Vlan Tcc
Example: Configuring an Ethernet TCC or Extended VLAN TCC Configure a full-duplex Layer 2.5 translational cross-connect between Router A and Router C, using a Juniper Networks router, Router B, as the TCC interface. Ethernet TCC encapsulation provides an Ethernet wide area circuit for interconnecting IP traffic.
Page 762 10.10.10.2; Configure a full-duplex Layer 2.5 translational cross-connect between Router A and Router C, using a Juniper Networks router, Router B, as the TCC interface. Extended VLAN TCC encapsulation provides an Ethernet wide area circuit for interconnecting IP traffic. (See the topology in Figure 59 on page 691.)
Page 763: Configuring Static Arp Table Entries
Chapter 39 Configuring Static ARP Table Entries Static ARP Table Entries Overview on page 693 Configuring Static ARP Table Entries on page 693 Static ARP Table Entries Overview For Fast Ethernet, Gigabit Ethernet, Tri-Rate Ethernet copper, and 10-Gigabit Ethernet interfaces, you can configure static ARP table entries, defining mappings between IP and MAC addresses.
Page 764: Example: Configuring Static Arp Table Entries
JUNOS 10.1 Network Interfaces Configuration Guide NOTE: By default, an ARP policer is installed that is shared among all the Ethernet interfaces on which you have configured the family inet statement. By including the statement at the [edit interfaces interface-name unit logical-unit-number family inet policer] hierarchy level, you can apply a specific ARP-packet policer to an interface.
Page 765: Configuring Unrestricted Proxy Arp
Chapter 40 Configuring Unrestricted Proxy ARP Unrestricted Proxy ARP Overview on page 695 Configuring Unrestricted Proxy ARP on page 696 Unrestricted Proxy ARP Overview By default, the JUNOS Software responds to an ARP request only if the destination address of the ARP request is local to the incoming interface. For Ethernet interfaces, you can configure unrestricted proxy ARP, which enables the router to respond to any ARP request, on condition that the router has an active route to the destination address of the ARP request.
Page 766: Figure 60: Edge Device Case For Unrestricted Proxy Arp
JUNOS 10.1 Network Interfaces Configuration Guide In Figure 60 on page 696, the edge device is not running any IP protocols. In this case, you configure the core router to perform unrestricted proxy ARP. The edge device is the client of the proxy. In Figure 61 on page 696, the Broadcast Remote Access Server (B-RAS) routers are not running any IP protocols.
Page 767 Chapter 40: Configuring Unrestricted Proxy ARP [edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number] To return to the default—that is, to disable unrestricted proxy ARP—delete the statement from the configuration: proxy-arp [edit] user@host# delete interfaces interface-name unit logical-unit-number proxy-arp You can track the number of unrestricted proxy ARP requests processed by the router by issuing the operational mode command.
Page 768 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Unrestricted Proxy ARP...
Page 769: Configuring Mac Address Validation On Static Ethernet Interfaces
Chapter 41 Configuring MAC Address Validation on Static Ethernet Interfaces MAC Address Validation on Static Ethernet Interfaces Overview on page 699 Configuring MAC Address Validation on Static Ethernet Interfaces on page 699 MAC Address Validation on Static Ethernet Interfaces Overview MAC address validation enables the router to validate that received packets contain a trusted IP source and an Ethernet MAC source address.
Page 770: Example Of Strict Mac Validation On A Static Ethernet Interface
JUNOS 10.1 Network Interfaces Configuration Guide Example of Strict MAC Validation on a Static Ethernet Interface This example shows strict MAC address validation on a static Ethernet interface without VLAN tagging. [edit interfaces] ge-2/1/9 { unit 0 { proxy-arp; family inet { mac-validate strict;...
Page 771: Chapter 42 Enabling Passive Monitoring On Ethernet Interfaces
Chapter 42 Enabling Passive Monitoring on Ethernet Interfaces Passive Monitoring on Ethernet Interfaces Overview on page 701 Enabling Passive Monitoring on Ethernet Interfaces on page 701 Passive Monitoring on Ethernet Interfaces Overview The Monitoring Services I and Monitoring Services II PICs are designed to enable IP services.
Page 772 JUNOS 10.1 Network Interfaces Configuration Guide For conformity with cflowd record structure, you must include the statements at the receive-options-packets receive-ttl-exceeded [edit interfaces mo-fpc/pic/port unit logical-unit-number family inet] hierarchy level: [edit interfaces mo-fpc/pic/port unit logical-unit-number family inet] receive-options-packets; receive-ttl-exceeded; For the monitoring services interface, you can configure multiservice physical interface properties.
Page 773: Chapter 43 Configuring Ieee 802.1Ag Oam Connectivity-Fault Management
Chapter 43 Configuring IEEE 802.1ag OAM Connectivity-Fault Management IEEE 802.1ag OAM Connectivity Fault Management Overview on page 703 Creating the Maintenance Domain on page 705 Configuring Maintenance Intermediate Points on page 706 Creating a Maintenance Association on page 708 Continuity Check Protocol on page 708 Configuring a Maintenance Endpoint on page 709 Configuring a Connectivity Fault Management Action Profile on page 712 Configuring Linktrace Protocol in CFM on page 715...
Page 774: Connectivity Fault Management Key Elements
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. You can only disable PPM on the PFE. To disable PPM on the PFE, include the statement at the [edit routing-options ppm]...
Page 775: Creating The Maintenance Domain
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...
Page 776: Configuring Maintenance Intermediate Points
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. The level is embedded in each of the CFM frames. CFM messages within a given level are processed by MEPs at that same level.
Page 777 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 statement at the virtual-switch name [edit protocols oam ethernet...
Page 778: Creating A Maintenance Association
JUNOS 10.1 Network Interfaces Configuration Guide Creating a Maintenance Association To create a maintenance association, include the maintenance-association ma-name statement at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain domain-name] hierarchy level. Maintenance association names can be in one of the following formats: As a plain ASCII character string As the VLAN identifier of the VLAN you primarily associate with the maintenance association...
Page 779: Configuring A Maintenance Endpoint
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management Configuring the Continuity Check Hold Interval You can specify the continuity check hold interval. The hold interval is the number of minutes to wait before flushing the MEP database if no updates occur. The default value is 10 minutes.
Page 780: Configuring The Maintenance Endpoint Lowest Priority Defect
JUNOS 10.1 Network Interfaces Configuration Guide Configuring the Maintenance Endpoint Lowest Priority Defect on page 711 Configuring a Remote Maintenance Endpoint on page 712 Enabling Maintenance Endpoint Automatic Discovery You can enable the MEP to accept continuity check messages from all remote MEPs of the same maintenance association.
Page 781: Table 66: Lowest Priority Defect Options
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management auto-discovery; priority number; Configuring the Maintenance Endpoint Priority You can specify the IEEE 802.1 priority bits that are used by continuity check and link trace messages. To configure the priority, include the priority statement at the [edit protocols oam...
Page 782: Configuring A Remote Maintenance Endpoint Action Profile
JUNOS 10.1 Network Interfaces Configuration Guide maintenance-association ma6 { mep 200 { interface ge-5/0/0.0; direction down; lowest-priority-defect mac-rem-err-xcon; Configuring a Remote Maintenance Endpoint You can configure a remote MEP from which CCM messages are expected. If autodiscovery is not enabled, the remote MEP must be configured under the statement.
Page 783 Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management To configure the action profile s action, include the statement at the action [edit protocols oam ethernet connectivity-fault-management action-profile profile-name] hierarchy level. user@host# show protocols oam ethernet { connectivity-fault-management { action-profile bring-down { event { interface-status-tlv down;...
Page 784 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: Associating an action-profile with the action of interface-down on an up MEP CFM session running over a CCC interface (l2circuit/l2vpn) is not advisable and could result in a deadlock situation. Configuring a CFM Action Profile Event You can configure one or more events under the action profile, the occurrence of which will trigger the corresponding action to be taken.
Page 785: Configuring Linktrace Protocol In Cfm
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management Configuring Linktrace Protocol in CFM The linktrace protocol is used for path discovery between a pair of maintenance points. Linktrace messages are triggered by an administrator using the traceroute command to verify the path between a pair of MEPs under the same maintenance association.
Page 786: Figure 64: Scope Of The E-Lmi Protocol
JUNOS 10.1 Network Interfaces Configuration Guide configuration parameters of Ethernet services available on the CE port. The scope of the E-LMI protocol is shown in Figure 64 on page 716. Figure 64: Scope of the E-LMI Protocol Metro Ethernet Network E-LMI E-LMI The E-LMI implementation on MX Series routers includes only the PE side of the...
Page 787: Configuring An Oam Protocol (Cfm)
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management EVC type (point-to-point or multipoint-to-multipoint) EVC ID (a user-configured name for EVC) Bandwidth profile (not supported) CE-VLAN ID/EVC map E-LMI on MX Series routers supports the following EVC types: QinQ SVLAN (point-to-point or multipoint-to-multipoint)—Requires an end-to-end CFM session between UNI-Ns to monitor the EVS status.
Page 788: Enabling E-Lmi On An Interface And Mapping Ce Vlan Ids To An Evc
JUNOS 10.1 Network Interfaces Configuration Guide You can configure an EVC by including the evcs statement at the [edit protocols oam ethernet] hierarchy level: [edit protocols oam ethernet] evcs evc-id { evc-protocol ( <cfm (<management-domain name> <management-association name> ) |<< vpls (routing-instance name>>> )) { remote-uni-count <number>;...
Page 789: Example E-Lmi Configuration
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management as the default EVC interface using the statement at the default-evc [edit protocols oam ethernet lmi interface name evc evc-id] hierarchy level. All VIDs that are not mapped to any other EVCs are mapped to this EVC. Only one EVC can be configured as the default.
Page 790 JUNOS 10.1 Network Interfaces Configuration Guide unit 1 { vlan-id 200; family bridge { interface-mode trunk; inner-vlan-id-list 2049-4096; protocols { oam { ethernet { connectivity-fault-management { maintenance-domain md { level 0; maintenance-association 1 { name-format vlan; mep 1 { direction up; interface ge-1/1/1.0 vlan 1;...
Page 791: Configuring Pe2
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management Configuring PE2 [edit] interfaces { ge-2/2/1 { unit 0 { family bridge { interface-mode trunk; vlan-id-list 1-2048; unit 1 { family bridge { interface-mode trunk; vlan-id-list 2049-4096; ge-2/2/2 { unit 0 { vlan-id 100;...
Page 792: Configuring Two Unis Sharing The Same Evc
JUNOS 10.1 Network Interfaces Configuration Guide evcs { evc1 { evc-protocol cfm management-domain md management-association 1; remote-uni-count 1; evc2 { evc-protocol cfm management-domain md management-association 2049; uni-count 2; lmi { interface ge-2/2/1 { evc evc1 { vlan-list 1-2048; evc evc2 { vlan-list 2049-4095;...
Page 793: Configuring Port Status Tlv And Interface Status Tlv
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management Configuring Port Status TLV and Interface Status TLV TLVs Overview on page 723 Various TLVs for CFM PDUs on page 723 Support for Additional Optional TLVs on page 725 MAC Status Defects on page 731 Configuring Remote MEP Action Profile Support on page 732 TLVs Overview Type, Length, and Value (TLVs) are described in the IEEE 802.1ag standard for CFM...
Page 794 JUNOS 10.1 Network Interfaces Configuration Guide Table 68: Type Field Values for Various TLVs for CFM PDUs (continued) TLV or Organization Type Field Port Status TLV Data TLV Interface Status TLV Reply Ingress TLV Reply Egress TLV LTM Egress Identifier TLV LTR Egress Identifier TLV Reserved for IEEE 802.1 9 to 30...
Page 795 Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management TLVs applicable for linktrace message (LTM): End TLV LTM Egress Identifier TLV Sender ID TLV Organization-Specific TLV TLVs applicable for linktrace reply (LTR): End TLV LTR Egress Identifier TLV Reply Ingress TLV Reply Egress TLV Sender ID TLV Organization-Specific TLV...
Page 796: Port Status Tlv
JUNOS 10.1 Network Interfaces Configuration Guide For configuration information, see the following sections: Port Status TLV on page 726 Interface Status TLV on page 728 Port Status TLV The Port Status TLV indicates the ability of the bridge port on which the transmitting MEP resides to pass ordinary data, regardless of the status of the MAC.
Page 797 Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain identifier maintenance-association identifier continuity-check] hierarchy level. NOTE: Port Status TLV configuration is not mandated by IEEE 802.1ag. The JUNOS Software provides it in order to give more flexibility to the operator; however it receives and processes CCMs with a Port Status TLV, regardless of this configuration.
Page 798: Interface Status Tlv
JUNOS 10.1 Network Interfaces Configuration Guide Remote MEP identifier: 1001, State: ok MAC address: 00:19:e2:b0:74:00, Type: Learned Interface: ge-2/0/0.0 Last flapped: Never Remote defect indication: false Port status TLV: none # RX PORT STATUS Interface status TLV: none Displaying the Transmitted Port Status TLV The JUNOS Software saves the last transmitted Port Status TLV from a local MEP.
Page 799: Table 72: Interface Status Tlv Values
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management Table 72: Interface Status TLV Values Mnemonic Interface Status Value isUp isDown down isTesting testing isUnknown unknown isDormant dormant isNotPresent notPresent isLowerLayerDown lowerLayerDown Configuring Interface Status TLV The JUNOS Software provides configuration support for the Interface Status TLV, thereby allowing operators to control the transmission of this TLV in CCM PDUs through configuration at the continuity-check level.
Page 800 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: The JUNOS Software supports transmission of only three out of seven possible values for the Interface Status TLV. The supported values are 1, 2, and 7. However, the JUNOS Software is capable of receiving any value for the Interface Status TLV. Displaying the Received Interface Status TLV The JUNOS Software saves the last received Interface Status TLV from the remote MEP.
Page 801: Mac Status Defects
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management Remote MEP identifier: 1001, State: ok MAC address: 00:19:e2:b0:74:00, Type: Learned Interface: ge-2/0/0.0 Last flapped: Never Remote defect indication: false Port status TLV: none Interface status TLV: none MAC Status Defects The JUNOS Software provides MAC status defect information, indicating that one or more of the remote MEPs is reporting a failure in its Port Status TLV or Interface Status TLV.
Page 802: Configuring Remote Mep Action Profile Support
JUNOS 10.1 Network Interfaces Configuration Guide Identifier MAC address State Interface 00:05:85:73:39:4a xe-5/0/0.0 Use the command to display MAC status defects: interfaces user@host> show oam ethernet connectivity-fault-management interfaces detail Interface name: xe-5/0/0.0, Interface status: Active, Link status: Up Maintenance domain name: md6, Format: string, Level: 6 Maintenance association name: ma6, Format: string Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames Interface status TLV: up, Port status TLV: up...
Page 803: Monitoring A Remote Mep Action Profile
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management The following example shows an action profile configuration with explanatory comments added: [edit protocols oam ethernet connectivity-fault-management] action-profile tlv-action { event { # If interface status tlv with value specified in the config is received interface-status-tlv down|lower-layer-down;...
Page 804: Configuring M120 And Mx Series Routers For Ccc Encapsulated Packets
JUNOS 10.1 Network Interfaces Configuration Guide Remote defect indication: false Port status TLV: none Interface status TLV: lower-layer-down Action profile: juniper # displays remote MEP s action profile identifier Last event: Interface-status-tlv lower-layer-down # last remote MEP event # to trigger action Action: Interface-down, Time: 2009-03-27 14:25:10 PDT (00:00:02 ago) # action occurrence time Configuring M120 and MX Series Routers for CCC Encapsulated Packets...
Page 805: Configuring Rate Limiting Of Ethernet Oam Messages
Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management To monitor the L2VPN circuit, a CFM up MEP (Level 6 in Figure 66 on page 734) can be configured on the CE-facing logical interfaces of provider edge routers PE1 and PE2. To monitor the CE-PE attachment circuit, a CFM down MEP can be configured on the customer logical interfaces of CE1-PE1 and CE2-PE2 (Level 0 in Figure 66 on page 734).
Page 806 JUNOS 10.1 Network Interfaces Configuration Guide To configure global-level CFM policing, include the statement and its options policer at the [edit protocols oam ethernet connectivity-fault-management] hierarchy level. To configure session-level CFM policing, include the statement at the policer [edit protocols oam ethernet connectivity-fault-management maintenance-domain name level hierarchy level.
Page 807 Chapter 43: Configuring IEEE 802.1ag OAM Connectivity-Fault Management continuity-check { interval 1s; policer { continuity-check cfm-policer; other cfm-policer1; # all cfm-policer2; mep 1 { interface ge-3/3/0.0; direction up; auto-discovery; In the case of global CFM policing, the same policer is shared across multiple CFM sessions.
Page 808 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Rate Limiting of Ethernet OAM Messages...
Page 809: Chapter 44 Configuring Itu-T Y.1731 Ethernet Service Oam
Chapter 44 Configuring ITU-T Y.1731 Ethernet Service Ethernet Frame Delay Measurements Overview on page 739 Guidelines for Configuring Routers to Support an ETH-DM Session on page 745 Guidelines for Starting an ETH-DM Session on page 746 Guidelines for Managing ETH-DM Statistics and ETH-DM Frame Counts on page 748 Configuring Routers to Support an ETH-DM Session on page 753 Starting an ETH-DM Session on page 756 Managing ETH-DM Statistics and ETH-DM Frame Counts on page 758...
Page 810: Ethernet Cfm
JUNOS 10.1 Network Interfaces Configuration Guide These capabilities allow operators to offer binding service-level agreements (SLAs) and generate new revenues from rate- and performance-guaranteed service packages that are tailored to the specific needs of their customers. Ethernet CFM The IEEE 802.1ag standard for connectivity fault management (CFM) defines mechanisms to provide for end-to-end Ethernet service assurance over any path, whether a single link or multiple links spanning networks composed of multiple LANs.
Page 811: Ethernet Frame Delay Measurement
Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM Ethernet Frame Delay Measurement Two key objectives of OAM functionality are to measure quality-of-service attributes such as frame delay and frame delay variation (also known as “frame jitter”). Such measurements can enable you to identify network problems before customers are impacted by network defects.
Page 812: One-Way Eth-Dm Frame Counts
JUNOS 10.1 Network Interfaces Configuration Guide One-Way ETH-DM Frame Counts Each router counts the number of one-way ETH-DM frames sent and received: For an initiator MEP, the router counts the number of 1DM frames sent. For a receiver MEP, the router counts the number of valid 1DM frames received and the number of invalid 1DM frames received.
Page 813: Dmr Reception
Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM DMR Reception When an MEP receives a valid DMR, the router that contains the MEP measures the two-way delay for that frame based on the following sequence of timestamps: TxDMM Time at which the initiator MEP transmits a two-way ETH-DM DMM frame to the responder MEP.
Page 814: Choosing Between One-Way And Two-Way Eth-Dm
JUNOS 10.1 Network Interfaces Configuration Guide database information for Ethernet interfaces assigned to MEPs or for MEPs in CFM sessions. NOTE: For a given two-way Ethernet frame delay measurement, frame delay and frame delay variation values are available only at the router that contains the initiator MEP.
Page 815: Guidelines For Configuring Routers To Support An Eth-Dm Session
Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM ETH-DM frame counts are collected at both MEPs and are stored in the respective CFM databases. If graceful Routing Engine switchover (GRES) occurs, any collected ETH-DM statistics are lost, and ETH-DM frame counts are reset to zeroes. GRES enables a router with dual Routing Engines to switch from a master Routing Engine to a backup Routing Engine without interruption to packet forwarding.
Page 816: Guidelines For Starting An Eth-Dm Session
JUNOS 10.1 Network Interfaces Configuration Guide enabled on the Packet Forwarding Engine of both routers. For more information about , see the JUNOS Routing Protocols Configuration Guide. If the PPM process ( ) is disabled on the Packet Forwarding Engine, you must re-enable it.
Page 817 Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM NOTE: The Ethernet frame delay measurement feature is supported only for maintenance association end points configured on Ethernet physical or logical interfaces on DPCs in MX Series routers. The ETH-DM feature is not supported on aggregated Ethernet interfaces or LSI pseudowires.
Page 818: Guidelines For Managing Eth-Dm Statistics And Eth-Dm Frame Counts
JUNOS 10.1 Network Interfaces Configuration Guide Restrictions for an ETH-DM Session The following restrictions apply to an ETH-DM session: You cannot run multiple simultaneous ETH-DM sessions with the same remote MEP or MAC address. For a given ETH-DM session, you can collect frame delay information for a maximum of 65,535 frames.
Page 819 Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM ETH-DM Statistics Ethernet frame delay statistics are the frame delay and frame delay variation values determined by the exchange of frames containing ETH-DM protocol data units (PDUs). For a one-way ETH-DM session, statistics are collected in an ETH-DM database at the router that contains the receiver MEP.
Page 820: Eth-Dm Frame Counts
JUNOS 10.1 Network Interfaces Configuration Guide Table 73: ETH-DM Statistics (continued) Field Name Field Description † When you start a two-way frame delay measurement, the CLI output includes a runtime display Average delay variation of the average two-way frame delay variation among the statistics collected for the ETH-DM session only.
Page 821: Eth-Dm Frame Count Retrieval
Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM Table 74: ETH-DM Frame Counts Field Name Field Description Number of one-way delay measurement (1DM) PDU frames sent to the peer MEP in this session. 1DMs sent Stored in the CFM database of the MEP initiating a one-way frame delay measurement. Number of valid 1DM frames received.
Page 822: One-Way Eth-Dm Frame Counts
JUNOS 10.1 Network Interfaces Configuration Guide One-Way ETH-DM Frame Counts For a one-way ETH-DM session, delay statistics are collected at the receiver MEP only, but frame counts are collected at both MEPs. As indicated in Table 74 on page 751, one-way ETH-DM frame counts are tallied from the perspective of each router in the session: At the initiator MEP, the router counts the number of 1DM frames sent.
Page 823: Configuring Routers To Support An Eth-Dm Session
Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM Configuring Routers to Support an ETH-DM Session Configuring MEP Interfaces on page 753 Ensuring that Distributed ppm Is Not Disabled on page 754 Enabling the Hardware-Assisted Timestamping Option on page 755 Configuring MEP Interfaces Before you can start an Ethernet frame delay measurement session across an Ethernet service, you must configure two MX Series routers to support ETH-DM.
Page 824 JUNOS 10.1 Network Interfaces Configuration Guide Ensuring that Distributed ppm Is Not Disabled By default, the router s period packet management process ( ) runs sessions distributed to the Packet Forwarding Engine in addition to the Routing Engine. This process is responsible for periodic transmission of packets on behalf of its various client processes, such as Bidirectional Forwarding Detection (BFD), and it also receives packets on behalf of client processes.
Page 825 Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM Modify the router configuration to re-enable distributed and restart the Ethernet OAM Connectivity Fault Management process ONLY IF distributed is disabled (as determined in the previous step). Before continuing, make any necessary preparations for the possible loss of connectivity on the router.
Page 826: Starting An Eth-Dm Session
JUNOS 10.1 Network Interfaces Configuration Guide performance-monitoring { hardware-assisted-timestamping; Starting an ETH-DM Session Using the monitor ethernet delay-measurement Command on page 756 Starting a One-Way ETH-DM Session on page 757 Starting a Two-Way ETH-DM Session on page 757 Using the monitor ethernet delay-measurement Command After you have configured two MX Series routers to support ITU-T Y.1731Ethernet frame delay measurement (ETH-DM), you can initiate a one-way or two-way Ethernet frame delay measurement session from the CFM maintenance association end point...
Page 827 Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM For a complete description of the operational monitor ethernet delay-measurement command, see the JUNOS System Basics and Services Command Reference. Starting a One-Way ETH-DM Session To start a one-way Ethernet frame delay measurement session, enter the monitor command from operational mode, and specify ethernet delay-measurement one-way...
Page 828: Managing Eth-Dm Statistics And Eth-Dm Frame Counts
JUNOS 10.1 Network Interfaces Configuration Guide NOTE: If you attempt to monitor delays to a nonexistent MAC address, you must type Ctrl + C to explicitly quit the monitor ethernet delay-measurement command and return to the CLI command prompt. Ethernet Frame Delay Measurements Overview on page 739 Related Topics Guidelines for Starting an ETH-DM Session on page 746 monitor ethernet delay-measurement...
Page 829 Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM Displaying ETH-DM Statistics and Frame Counts Display ETH-DM statistics and ETH-DM frame counts. Purpose By default, the show oam ethernet connectivity-fault-management mep-statistics command displays ETH-DM statistics and frame counts for MEPs in the specified CFM maintenance association (MA) within the specified CFM maintenance domain (MD).
Page 830 JUNOS 10.1 Network Interfaces Configuration Guide To display CFM database information (including ETH-DM frame counts) only for local MEP in MA within MD user@host> show oam ethernet connectivity-fault-management mep-database maintenance-domain md2 maintenance-association ma2 local-mep 201 To display CFM database information (including ETH-DM frame counts) only for remote MEP in MD within MA...
Page 831: Example: One-Way Ethernet Frame Delay Measurement
Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM By default, statistics and frame counts are deleted for all MEPs attached to CFM-enabled interfaces on the router. However, you can filter the scope of the command by specifying an interface name. To clear the ETH-DM statistics and ETH-DM frame counts for all MEPs attached Action to CFM-enabled interfaces on the router:...
Page 832: Eth-Dm Frame Counts For This Example
JUNOS 10.1 Network Interfaces Configuration Guide On router , interface is an Ethernet port on an Enhanced or MX-PE1 ge-5/2/9 Enhanced Queuing Dense Port Concentrator (DPC). The traffic load received on this DPC is heavy. On router MX-PE2 , interface ge-0/2/5 is an Ethernet port on a DPC.
Page 833: Steps For The Example One-Way Frame Delay Measurement
Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM Steps for the Example One-Way Frame Delay Measurement The following steps describe an example one-way Ethernet frame delay measurement: At router , configure MEP as a CFM maintenance association end MX-PE1 point in CFM maintenance domain as follows: Define the maintenance domain by associating it with maintenance...
Page 834 JUNOS 10.1 Network Interfaces Configuration Guide At router , configure MEP as a CFM maintenance association end MX-PE2 point in CFM maintenance domain as follows: Define the maintenance domain by associating it with maintenance domain level and maintenance association identifier Configure the maintenance association by specifying continuity protocol options and specifying MEP identifier Configure MEP...
Page 835 Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM ethernet { connectivity-fault-management { performance-monitoring { hardware-assisted-timestamping; NOTE: The hardware-assisted timestamping option for ETH-DM is available for Ethernet interfaces on Enhanced or Enhanced Queuing DPCs only. At router MX-PE2 , start a one-way frame delay measurement session from local to remote MEP on router MX-PE1...
Page 836 JUNOS 10.1 Network Interfaces Configuration Guide Auto-discovery: enabled, Priority: 0 Interface name: ge-0/2/5.0, Interface status: Active, Link status: Up Defects: Remote MEP not receiving CCM : no Erroneous CCM received : no Cross-connect CCM received : no RDI sent by some MEP : no Statistics: CCMs sent...
Page 837 Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM CCMs sent : 1590 CCMs received out of sequence LBMs sent Valid in-order LBRs received Valid out-of-order LBRs received LBRs received with corrupted data LBRs sent LTMs sent LTMs received LTRs sent LTRs received Sequence number of next LTM request 1DMs sent...
Page 838 JUNOS 10.1 Network Interfaces Configuration Guide Average one-way delay : 312 usec Average one-way delay variation: 11 usec Best case one-way delay : 255 usec Worst case one-way delay : 370 usec To display both the ETH-DM statistics and the CFM database information (which includes any ETH-DM frame counts), use the form of mep-statistics...
Page 839 Chapter 44: Configuring ITU-T Y.1731 Ethernet Service OAM Guidelines for Managing ETH-DM Statistics and ETH-DM Frame Counts on page 748 Example: One-Way Ethernet Frame Delay Measurement...
Page 840 JUNOS 10.1 Network Interfaces Configuration Guide Example: One-Way Ethernet Frame Delay Measurement...
Page 841: Configuring Ieee 802.1X Port-Based Network Access Control
Chapter 45 Configuring IEEE 802.1x Port-Based Network Access Control IEEE 802.1x Port-Based Network Access Control Overview on page 771 Understanding the Administrative State of the Authenticator Port on page 772 Understanding the Administrative Mode of the Authenticator Port on page 772 Configuring the Authenticator on page 772 Viewing the dot1x Configuration on page 773 IEEE 802.1x Port-Based Network Access Control Overview...
Page 842 JUNOS 10.1 Network Interfaces Configuration Guide Understanding the Administrative State of the Authenticator Port The administrative state of an authenticator port can take any of the following three states: Force authorized—Allows network access to all users of the port without requiring them to be authenticated.
Page 843 Chapter 45: Configuring IEEE 802.1x Port-Based Network Access Control supplicant-timeout seconds; transmit-period seconds; Viewing the dot1x Configuration To review and verify the dot1x configuration. Purpose To view all configurations, use the operational mode Action dot1x show dot1x interface command. To view a dot1x configuration for a specific interface, use the show dot1x...
Page 844 JUNOS 10.1 Network Interfaces Configuration Guide Viewing the dot1x Configuration...
Page 845: Configuring Ieee 802.3Ah Oam Link-Fault Management
Chapter 46 Configuring IEEE 802.3ah OAM Link-Fault Management IEEE 802.3ah OAM Link-Fault Management Overview on page 775 Configuring IEEE 802.3ah OAM Link-Fault Management on page 776 Enabling IEEE 802.3ah OAM Support on page 776 Configuring Link Discovery on page 776 Configuring the OAM PDU Interval on page 777 Configuring the OAM PDU Threshold on page 777 Configuring Threshold Values for Local Fault Events on an Interface on page 777...
Page 846 JUNOS 10.1 Network Interfaces Configuration Guide The features of link-fault management are: Discovery Link monitoring Remote fault detection Remote loopback NOTE: Ethernet running on top of a Layer 2 protocol, such as Ethernet over ATM, is not supported in OAM configurations. Configuring IEEE 802.3ah OAM Link-Fault Management You can configure threshold values for fault events that trigger the sending of link event TLVs when the values exceed the threshold.
Page 847 Chapter 46: Configuring IEEE 802.3ah OAM Link-Fault Management You can specify the discovery mode used for IEEE 802.3ah OAM support. The discovery process is triggered automatically when OAM IEEE 802.3ah functionality is enabled on a port. Link monitoring is done when the interface sends periodic OAM PDUs.
Page 848 JUNOS 10.1 Network Interfaces Configuration Guide hierarchy oam ethernet link-fault-management interface interface-name event-thresholds] level: [edit protocol oam ethernet link-fault-management interface interface-name] event-thresholds { frame-error count; frame-period count; frame-period-summary count; symbol-period count; Disabling the Sending of Link Event TLVs You can disable the sending of link event TLVs. To disable the monitoring and sending of PDUs containing link event TLVs in periodic PDUs, include the statement at the...
Page 849 Chapter 46: Configuring IEEE 802.3ah OAM Link-Fault Management action { syslog; link-down; send-critical-event; event { link-adjacency-loss; link-event-rate { frame-error count; frame-period count; frame-period-summary count; symbol-period count; protocol-down; Specifying the Actions to Be Taken for Link-Fault Management Events You can specify the action to be taken by the system when the configured link-fault event occurs.
Page 850 JUNOS 10.1 Network Interfaces Configuration Guide NOTE: If multiple actions are specified in the action profile, all of the actions are executed in no particular order. Monitoring the Loss of Link Adjacency You can specify actions be taken when link adjacency is lost. When link adjacency is lost, the system takes the action defined in the action statement of the action...
Page 851: Setting A Remote Interface Into Loopback Mode
Chapter 46: Configuring IEEE 802.3ah OAM Link-Fault Management Applying an Action Profile You can apply an action profile to one or more interfaces. To apply an action profile to an interface, include the statement apply-action-profile at the [edit protocols oam ethernet link-fault-management action-profile interface hierarchy level: interface-name] [edit protocol oam ethernet link-fault-management interface interface-name]...
Page 852: Example: Configuring Ieee 802.3Ah Oam Support On An Interface
JUNOS 10.1 Network Interfaces Configuration Guide [edit protocol oam ethernet link-fault-management interface interface-name negotiation-options] allow-remote-loopback; NOTE: Activation of OAM remote loopback may result in data frame loss. Example: Configuring IEEE 802.3ah OAM Support on an Interface Configure 802.3ah OAM support on an MX Series 10-Gigabit Ethernet interface: [edit] protocols { oam {...
Page 853: Configuring Vrrp And Vrrp For Ipv6
Chapter 47 Configuring VRRP and VRRP for IPv6 VRRP and VRRP for IPv6 Overview on page 783 Configuring VRRP and VRRP for IPv6 on page 783 VRRP and VRRP for IPv6 Overview For Ethernet, Fast Ethernet, Tri-Rate Ethernet copper, Gigabit Ethernet, 10-Gigabit Ethernet, and Ethernet logical interfaces, you can configure the Virtual Router Redundancy Protocol (VRRP) and VRRP for IPv6.
Page 854 JUNOS 10.1 Network Interfaces Configuration Guide (preempt | no-preempt) { hold-time seconds; priority-number number; track { priority-hold-time; interface interface-name { priority-cost priority; bandwidth-threshold bits-per-second { priority-cost; virtual-address [ addresses ]; To trace VRRP and VRRP for IPv6 operations, include the traceoptions statement at hierarchy level:...
Page 855: Chapter 48 Configuring Gigabit Ethernet Accounting And Policing
Chapter 48 Configuring Gigabit Ethernet Accounting and Policing Gigabit Ethernet Accounting and Policing Overview on page 785 Configuring Gigabit Ethernet Policers on page 787 Configuring Gigabit Ethernet Two-Color and Tricolor Policers on page 793 Configuring MAC Address Accounting on page 796 Gigabit Ethernet Accounting and Policing Overview For Gigabit Ethernet IQ PICs and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), you...
Page 856 JUNOS 10.1 Network Interfaces Configuration Guide Table 75: Capabilities of Gigabit Ethernet IQ and Gigabit Ethernet with SFPs (continued) Gigabit Ethernet Gigabit Ethernet Capability IQ (SFP) (SFP) Maximum VLANs per port 1023 Maximum transmission unit (MTU) size 9192 9192 MAC learning MAC accounting MAC filtering Destinations per port...
Page 857: Configuring Gigabit Ethernet Policers
Chapter 48: Configuring Gigabit Ethernet Accounting and Policing Configuring Gigabit Ethernet Policers On Gigabit Ethernet IQ and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), you can define rate limits for premium and aggregate traffic received on the interface. These policers allow you to perform simple traffic policing without configuring a firewall filter.
Page 858 JUNOS 10.1 Network Interfaces Configuration Guide policer cos-policer-name { aggregate { bandwidth-limit bps; burst-size-limit bytes; premium { bandwidth-limit bps; burst-size-limit bytes; In the Ethernet policer profile, the aggregate-priority policer is mandatory; the premium-priority policer is optional. For aggregate and premium policers, you specify the bandwidth limit in bits per second.
Page 859: Table 76: Default Forwarding Classes
Chapter 48: Configuring Gigabit Ethernet Accounting and Policing NOTE: On IQ2 and IQ2-E interfaces and MX Series interfaces, when a VLAN tag is pushed, the inner VLAN IEEE 802.1p bits are copied to the IEEE bits of the VLAN or VLANs being pushed.
Page 860 JUNOS 10.1 Network Interfaces Configuration Guide logical interface. Aggregate policers are supported on Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router). These policers allow you to perform simple traffic policing without configuring a firewall filter.
Page 861 Chapter 48: Configuring Gigabit Ethernet Accounting and Policing The MAC addresses you include in the configuration are entered into the router s MAC database. To view the router s MAC database, enter the show interfaces mac-database interface-name command: user@host> show interfaces mac-database interface-name In the statement, list the name of one policer template to be evaluated when input...
Page 862 JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring Gigabit Ethernet Policers Configure interface to treat priority values 2 and 3 as premium. On ingress, ge-6/0/0 this means that IEEE 802.1p priority values are treated as premium. On egress, it means traffic that is classified into queue 0 or 1 with PLP of low and queue 2 or 3 with PLP of high, is treated as premium.
Page 863: Configuring Gigabit Ethernet Two-Color And Tricolor Policers
Juniper Networks router architectures support three types of policer: Two-color policer—A two-color policer (or “policer” when used without...
Page 864: Configuring A Policer
JUNOS 10.1 Network Interfaces Configuration Guide (DiffServ) environment. This type of policer meters traffic based on the configured CIR and peak information rate (PIR), along with their associated burst sizes, the CBS and EBS. Traffic is marked as belonging to one of three categories (green, yellow, or red) based on whether the packets arriving are below the CIR (green), exceed the CIR (yellow) but not the PIR, or exceed the PIR (red).
Page 865 Chapter 48: Configuring Gigabit Ethernet Accounting and Policing For more information about configuring tricolor policer markings, see the JUNOS Policy Framework Configuration Guide and the JUNOS Class of Service Configuration Guide. Applying a Policer Apply a two-color policer or tricolor policer to a logical interface to prevent traffic on the interface from consuming bandwidth inappropriately.
Page 866: Configuring Mac Address Accounting
JUNOS 10.1 Network Interfaces Configuration Guide peak-burst-size 300; [edit interfaces ge-1/1/0] unit 1 { layer2-policer { input-three-color three-color-policer-color-blind; output-three-color three-color-policer-color-aware; Configure a two-color policer and apply it to an interface: [edit firewall] policer two-color-policer { logical-interface-policer; if-exceeding { bandwidth-percent 90; burst-size-limit 300;...
Page 867: Chapter 49 Configuring Gigabit Ethernet Autonegotiation
Chapter 49 Configuring Gigabit Ethernet Autonegotiation Gigabit Ethernet Autonegotiation Overview on page 797 Configuring Gigabit Ethernet Autonegotiation on page 797 Gigabit Ethernet Autonegotiation Overview Autonegotiation is enabled by default on all Gigabit Ethernet and Tri-Rate Ethernet copper interfaces. However, you can explicitly enable autonegotiation to configure remote fault options manually.
Page 868 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Gigabit Ethernet Autonegotiation with Remote Fault To configure explicit autonegotiation and remote fault, include the auto-negotiation statement and the remote-fault option at the [edit interfaces ge-fpc/pic/port hierarchy level. gigether-options] [edit interfaces ge-fpc/pic/port gigether-options] (auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online | local-interface-offline>...
Page 869: Table 77: Mode And Autonegotiation Status (Local)
Chapter 49: Configuring Gigabit Ethernet Autonegotiation Table 77: Mode and Autonegotiation Status (Local) Transmit Receive Mode Link Autonegotiation Status Default Green Complete Default DOWN Default DOWN Default DOWN Default DOWN Default Green No-autonegotiation Default DOWN Default DOWN Default Green Default DOWN No-autonegotiation Green...
Page 870 JUNOS 10.1 Network Interfaces Configuration Guide Table 77: Mode and Autonegotiation Status (Local) (continued) Transmit Receive Mode Link Autonegotiation Status Explicit+RFI-Offline DOWN Explicit+RFI-Offline DOWN Explicit+RFI-Offline Green No-autonegotiation Explicit+RFI-Offline DOWN Explicit+RFI-Offline Green Explicit+RFI-Offline DOWN Explicit+RFI-Offline DOWN Explicit+RFI-Offline DOWN Complete Explicit+RFI-Offline DOWN Explicit+RFI-Online DOWN Explicit+RFI-Online...
Page 871: Table 78: Mode And Autonegotiation Status (Remote)
Chapter 49: Configuring Gigabit Ethernet Autonegotiation Table 78: Mode and Autonegotiation Status (Remote) Transmit Receive Mode Link Autonegotiation Status Default Green Complete Default DOWN Default DOWN Default DOWN Default DOWN No-autonegotiation Green Incomplete No-autonegotiation DOWN No-autonegotiation DOWN No-autonegotiation Green No-autonegotiation DOWN Explicit Green...
Page 872 JUNOS 10.1 Network Interfaces Configuration Guide Table 78: Mode and Autonegotiation Status (Remote) (continued) Transmit Receive Mode Link Autonegotiation Status Explicit+RFI-Online DOWN Configuring Gigabit Ethernet Autonegotiation...
Page 873: Chapter 50 Configuring Gigabit Ethernet Otn Options
Chapter 50 Configuring Gigabit Ethernet OTN Options Gigabit Ethernet OTN Options Configuration Overview on page 803 Gigabit Ethernet OTN Options on page 803 Gigabit Ethernet OTN Options Configuration Overview M120, M320, T320, T640, and T1600 router platforms support Optical Transport Network (OTN) interfaces, including the 10-Gigabit Ethernet DWDM OTN PIC, and provide ITU-G.709 support.
Page 874 JUNOS 10.1 Network Interfaces Configuration Guide —See the JUNOS System Basics and Services Command show chassis hardware Reference for command details. show chassis pic —See the JUNOS System Basics and Services Command Reference for command details. Gigabit Ethernet OTN Options...
Page 875: Chapter 51 Configuring The Management Ethernet Interface
Chapter 51 Configuring the Management Ethernet Interface Management Ethernet Interface Overview on page 805 Configuring a Consistent Management IP Address on page 805 Configuring the MAC Address on the Management Ethernet Interface on page 807 Management Ethernet Interface Overview The router s management Ethernet interface, fxp0 or em0 , is an out-of-band management interface that needs to be configured only if you want to connect to the router through the management port on the front of the router.
Page 876 JUNOS 10.1 Network Interfaces Configuration Guide management Ethernet interface for the master Routing Engine. During switchover, the address moves to the new master Routing Engine. NOTE: For M Series, MX Series, and most T Series routers, the management Ethernet interface is .
Page 877 Chapter 51: Configuring the Management Ethernet Interface Configuring the MAC Address on the Management Ethernet Interface By default, the router s management Ethernet interface uses as its MAC address the MAC address that is burned into the Ethernet card. NOTE: For M Series, MX Series, and most T Series routers, the management Ethernet interface is fxp0 .
Page 878 JUNOS 10.1 Network Interfaces Configuration Guide Configuring the MAC Address on the Management Ethernet Interface...
Page 879: Configuring 10-Port 10-Gigabit Oversubscribed Ethernet Pics
This section describes the main features and caveats of the 10-port 10-Gigabit Oversubscribed Ethernet (OSE) PIC and specifies which routers support these PICs. The 10-port 10-Gigabit OSE PIC is supported by Juniper Networks TX Matrix and TX Matrix Plus and Juniper Networks T640 and T1600 Core Routers. It has the following...
Page 880 JUNOS 10.1 Network Interfaces Configuration Guide —Ethernet virtual private LAN service ethernet-vpls vlan-vpls —VLAN virtual private LAN service —Allows per-unit Ethernet encapsulation configuration flexible-ethernet-services Single, stacked, and flexible VLAN tagging modes Native VLAN configuration to allow untagged frames to be received on the tagged interfaces Maximum transmission unit (MTU) size of up to 9192 bytes for Ethernet frames Link aggregation group (LAG) on single chassis...
Page 881: Table 79: Capabilities Of 10-Port 10-Gigabit Ose Pics
Chapter 52: Configuring 10-port 10-Gigabit Oversubscribed Ethernet PICs Committed information rate and peak information rate configurations are not supported at the physical interface level. There is limited packet buffering of 2 MB. Delay-bandwidth buffering configuration is not supported. Multifield classifiers are not supported at the PIC level. The multifield classification can be done at the Packet Forwarding Engine using the firewall filters, which overrides the classification done at the PIC level.
Page 882: Table 80: Handling Oversubscription On 10-Port 10-Gigabit Ose Pics
JUNOS 10.1 Network Interfaces Configuration Guide Line Rate Mode: In this mode, only five alternate ports (ports 0, 2, 4, 6, and 8) are enabled. The PIC operates in line rate mode at 50 Gbps. To configure the PIC in line rate mode, include the statement at the linerate-mode [edit chassis set fpc fpc-number pic pic-number]...
Page 883 Chapter 52: Configuring 10-port 10-Gigabit Oversubscribed Ethernet PICs Table 80: Handling Oversubscription on 10-port 10-Gigabit OSE PICs (continued) Total Number of Number of Port Number of Port Ports Used on Groups with Two Groups with One PIC (C = Ax2 + Active Ports (A) Active Port (B) Status of Oversubscription and Throughput...
Page 884 JUNOS 10.1 Network Interfaces Configuration Guide Example: Handling Oversubscription on 10-port 10-Gigabit Oversubscribed Ethernet PIC...
Page 885: Configuring The 10-Gigabit Ethernet Dwdm Interface Wavelength
Chapter 53 Configuring the 10-Gigabit Ethernet DWDM Interface Wavelength 10-Gigabit Ethernet DWDM Interface Wavelength Overview on page 815 Configuring the 10-Gigabit Ethernet DWDM Interface Wavelength on page 815 10-Gigabit Ethernet DWDM Interface Wavelength Overview For M320, M120, T320, and T640 routers, the 10-Gigabit Ethernet DWDM PIC enables you to configure 10-Gigabit Ethernet DWDM interfaces with full C-band International Telecommunication Union (ITU)-Grid tunable optics, as defined in the following specifications:...
Page 886: Table 81: Wavelength-To-Frequency Conversion Matrix
JUNOS 10.1 Network Interfaces Configuration Guide Table 81: Wavelength-to-Frequency Conversion Matrix Wavelength (nm) Frequency (THz) Wavelength (nm) Frequency (THz) Wavelength (nm) Frequency (THz) 1528.77 196.10 1540.56 194.60 1552.52 193.10 1529.55 196.00 1541.35 194.50 1553.33 193.00 1530.33 195.90 1542.14 194.40 1554.13 192.90 1531.12 195.80...
Page 887: Configuring 10-Gigabit Ethernet Framing
Chapter 54 Configuring 10-Gigabit Ethernet Framing 10-Gigabit Ethernet Framing Overview on page 817 Configuring 10-Gigabit Ethernet Framing on page 817 10-Gigabit Ethernet Framing Overview The 10-Gigabit Ethernet IQ2 and IQ2-E PIC for the M120, M320, and T Series routers operates with Type 3 FPCs. The 10-Gigabit Ethernet IQ2 and IQ2-E PIC supports all features of the IQ2 and IQ2-E family PICs.
Page 888 JUNOS 10.1 Network Interfaces Configuration Guide framing (lan-phy | wan-phy); To display interface information, use the operational mode command show interfaces xe-fpc/pic/port extensive NOTE: If you configure the WAN PHY mode on an aggregated Ethernet interface, you must set the aggregated Ethernet link speed to OC192. Configuring 10-Gigabit Ethernet Framing...
Page 889: Configuring 10-Gigabit Ethernet Notification Of Link Down Alarm
Chapter 55 Configuring 10-Gigabit Ethernet Notification of Link Down Alarm 10-Gigabit Ethernet Notification of Link Down Alarm Overview on page 819 Configuring 10-Gigabit Ethernet Notification of Link Down Alarm on page 819 10-Gigabit Ethernet Notification of Link Down Alarm Overview Notification of link down alarm generation and transfer is supported for all 10-Gigabit Ethernet PIC interfaces, M120, M320.
Page 890 JUNOS 10.1 Network Interfaces Configuration Guide Configuring 10-Gigabit Ethernet Notification of Link Down Alarm...
Page 891: Configuring 10-Gigabit Ethernet Notification Of Link Down For Optics Alarms
Chapter 56 Configuring 10-Gigabit Ethernet Notification of Link Down for Optics Alarms 10-Gigabit Ethernet Notification of Link Down for Optics Options Overview on page 821 Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or Warning on page 821 10-Gigabit Ethernet Notification of Link Down for Optics Options Overview Notification of link down is supported for IQ2 10-Gigabit Ethernet interfaces and MX Series DPCs.
Page 892 JUNOS 10.1 Network Interfaces Configuration Guide Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or Warning...
Page 893: Configuring Point-To-Point Protocol Over Ethernet
Chapter 57 Configuring Point-to-Point Protocol over Ethernet PPPoE Overview on page 824 Understanding PPPoE Service Name Tables on page 827 Configuring PPPoE on page 830 Disabling the Sending of PPPoE Keepalive Messages on page 837 Configuring PPPoE Service Name Tables on page 837 Creating a Service Name Table on page 838 Configuring the Action Taken When the Client Request Includes an Empty Service Name Tag on page 839...
Page 894: Pppoe Overview
JUNOS 10.1 Network Interfaces Configuration Guide PPPoE Overview The Point-to-Point Protocol over Ethernet (PPPoE) connects multiple hosts on an Ethernet LAN to a remote site through a single customer premises equipment (CPE) device. Hosts share a common digital subscriber line (DSL), a cable modem, or a wireless connection to the Internet.
Page 895: Ethernet Interface
Chapter 57: Configuring Point-to-Point Protocol over Ethernet PPPoE configuration is the same for both interfaces. The only difference is the encapsulation for the underlying interface to the access concentrator: If the interface is Fast Ethernet, use a PPPoE encapsulation. If the interface is ATM over ADSL, use a PPPoE over ATM encapsulation. The PPPoE interface on M120 or M320 routers acting as a access concentrator can be a Gigabit Ethernet or 10-Gigabit Ethernet interface.
Page 896: Pppoe Session Stage
JUNOS 10.1 Network Interfaces Configuration Guide PPPoE active discovery initiation (PADI)—The client initiates a session by broadcasting a PADI packet on the LAN to request a service. PPPoE active discovery offer (PADO)—Any access concentrator that can provide the service requested by the client in the PADI packet replies with a PADO packet that contains it own name, the unicast address of the client, and the service requested.
Page 897: Understanding Pppoe Service Name Tables
Chapter 57: Configuring Point-to-Point Protocol over Ethernet it responds to the challenge. If you do not include the statement, the interface passive always challenges its peer. For more information about CHAP, see “Configuring the PPP Challenge Handshake Authentication Protocol” on page 124. Understanding PPPoE Service Name Tables On an M120 router or M320 router acting as a remote access concentrator (AC), also referred to as a PPPoE server, you can configure up to 16 PPPoE service name tables...
Page 898 JUNOS 10.1 Network Interfaces Configuration Guide The PPPoE client sends a unicast PPPoE Active Discovery Request (PADR) packet to the AC to which it wants to connect, based on the responses received in the PADO packets. The selected AC sends a PPPoE Active Discovery Session (PADS) packet to establish the PPPoE connection with the client.
Page 899 Chapter 57: Configuring Point-to-Point Protocol over Ethernet pairs to accept specific service name tags only from specific subscribers, as described in the following information about ACI/ARI pairs. ACI/ARI pair—Specifies the agent circuit identifier (ACI) and agent remote identifier (ARI) information for a service name tag. An ACI/ARI pair contains an agent circuit ID string that identifies the DSLAM interface that initiated the service request, and an agent remote ID string that identifies the subscriber on the DSLAM interface that initiated the service request.
Page 900: Configuring Pppoe
JUNOS 10.1 Network Interfaces Configuration Guide send a PADO packet to the client within the delay period configured on the backup AC, then the backup AC sends the PADO packet after the delay period expires. Configuring PPPoE Service Name Tables on page 837 Related Topics Example: Configuring a PPPoE Service Name Table on page 841 Configuring PPPoE...
Page 901: Configuring Pppoe Encapsulation On An Ethernet Interface
Chapter 57: Configuring Point-to-Point Protocol over Ethernet Setting the Appropriate Encapsulation on the PPPoE Interface For PPPoE on an Ethernet interface, you must configure encapsulation on the logical interface and use PPP over Ethernet encapsulation. For PPPoE on an ATM-over-ADSL interface, you must configure encapsulation on both the physical and logical interfaces.
Page 902: Configuring A Pppoe Interface
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces pp0 unit logical-unit-number] [edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number] Configuring PPPoE Encapsulation on an ATM-over-ADSL Interface To configure the PPPoE encapsulation on a ATM-over-ADSL interface, perform the following steps: Include the statement at the hierarchy encapsulation...
Page 903 Chapter 57: Configuring Point-to-Point Protocol over Ethernet Configuring the PPPoE Underlying Interface To configure the underlying Fast Ethernet, Gigabit Ethernet, 10-Gigabit Ethernet, or ATM interface, include the statement: underlying-interface underlying-interface interface-name; You can include this statement at the following hierarchy levels: [edit interfaces pp0 unit logical-unit-number pppoe-options] [edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number pppoe-options]...
Page 904 JUNOS 10.1 Network Interfaces Configuration Guide Configuring the PPPoE Service Name When configuring a PPPoE client, identify the type of service provided by the access concentrator—such as the name of the Internet service provider (ISP), class, or quality of service—by including the service-name statement: service-name name;...
Page 905 Chapter 57: Configuring Point-to-Point Protocol over Ethernet [edit logical-systems logical-system-name interfaces pp0.0 family inet] Deriving the PPPoE Source Address From a Specified Interface For a router supporting PPPoE, you can derive the source address from a specified interface—for example, the loopback interface, lo0.0 —and assign a destination address—for example,...
Page 906 JUNOS 10.1 Network Interfaces Configuration Guide The default media MTU size used and the range of available sizes on a physical interface depends on the encapsulation used on that interface. Example: Configuring a PPPoE Client Interface on a J Series Services Router Configure a PPPoE over ATM-over-ADSL interface: [edit interfaces]...
Page 907: Example: Configuring A Pppoe Server Interface On An M120 Or M320 Router
Chapter 57: Configuring Point-to-Point Protocol over Ethernet Example: Configuring a PPPoE Server Interface on an M120 or M320 Router Configure a PPPoE server over a Gigabit Ethernet interface: [edit interfaces] ge-1/0/0 { vlan-tagging; unit 1 { encapsulation ppp-over-ether; vlan-id 10; pp0 { unit 0 { pppoe-options {...
Page 908: Creating A Service Name Table
JUNOS 10.1 Network Interfaces Configuration Guide See “Configuring the Action Taken When the Client Request Includes an Empty Service Name Tag” on page 839. Assign a service to the service name table and optionally configure the action taken for the specified service name. See “Assigning a Service to a Service Name Table and Configuring the Action Taken When the Client Request Includes a Non-zero Service Name Tag”...
Page 909: Configuring The Action Taken When The Client Request Includes An Empty Service Name Tag
Chapter 57: Configuring Point-to-Point Protocol over Ethernet Configuring PPPoE Service Name Tables on page 837 Related Topics Configuring the Action Taken When the Client Request Includes an Empty Service Name Tag You can configure the action taken by the PPPoE underlying interface when it receives a PADI packet that includes a zero-length (empty) service name tag.
Page 910: Assigning An Aci/Ari Pair To A Service Name And Configuring The Action Taken When The Client Request Includes Aci/Ari Information
JUNOS 10.1 Network Interfaces Configuration Guide Configuring PPPoE Service Name Tables on page 837 Related Topics Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the Client Request Includes ACI/ARI Information You can specify up to 16 ACI/ARI (agent specifier) pairs for each PPPoE service name. You can optionally configure the action taken by the PPPoE underlying interface when it receives a PADI packet that includes a service name (service name tag) and the vendor-specific tag with ACI/ARI information that matches the ACI/ARI that you...
Page 911: Assigning A Service Name Table To A Pppoe Underlying Interface
Chapter 57: Configuring Point-to-Point Protocol over Ethernet Configuring PPPoE Service Name Tables on page 837 Related Topics Assigning a Service Name Table to a PPPoE Underlying Interface You must assign the PPPoE service name table to an underlying PPPoE interface. Before you assign a service name table to a PPPoE underlying interface, specify PPPoE as the encapsulation method on the underlying interface: See the section, Setting the Appropriate Encapsulation on the PPPoE Interface, in...
Page 912 JUNOS 10.1 Network Interfaces Configuration Guide service user1-service { terminate; agent-specifier { aci “east*” ari “wfd*” delay 10; aci “west*” ari “svl*” delay 10; service user2-service { delay 20; This example creates a PPPoE service name table named Table1 with three service name tags, as follows: tag is configured with the action.
Page 913 Chapter 57: Configuring Point-to-Point Protocol over Ethernet (Optional) Verify the PPPoE service name table configuration. user@host> show pppoe service-name-tables Table1 Service Name Table: Table1 Service Name: <empty> Service Action: Drop Service Name: user1–service Service Action: Terminate ACI: east* ARI: wfd* ACI/ARI Action: Delay 10 seconds ACI: west* ARI: svl*...
Page 914: Tracing Pppoe Operations
JUNOS 10.1 Network Interfaces Configuration Guide Understanding PPPoE Service Name Tables on page 827 Related Topics Configuring PPPoE Service Name Tables on page 837 Troubleshooting PPPoE Service Name Tables on page 847 Tracing PPPoE Operations PPPoE supports tracing operations. PPPoE tracing operations track PPPoE operations and record them in a log file.
Page 915: Configuring The Pppoe Trace Log Filename
Chapter 57: Configuring Point-to-Point Protocol over Ethernet The PPPoE traceoptions operations are described in the following sections: Configuring the PPPoE Trace Log Filename on page 845 Configuring the Number and Size of PPPoE Log Files on page 845 Configuring Access to the PPPoE Log File on page 845 Configuring a Regular Expression for PPPoE Lines to Be Logged on page 846 Configuring the PPPoE Tracing Flags on page 846 Configuring the PPPoE Trace Log Filename...
Page 916: Table 82: Pppoe Trace Operation Flags
JUNOS 10.1 Network Interfaces Configuration Guide To specify that all users can read the log file, configure the log file to be world-readable: [edit protocols pppoe traceoptions] user@host# set file pppoe_1 _logfile_1 world-readable To explicitly set the default behavior, only the user who configured tracing can read the log file, configure the log file to be no-world-readable: [edit protocols pppoe traceoptions] user@host# set file pppoe_1 _logfile_1 no-world-readable...
Page 917: Troubleshooting Pppoe Service Name Tables
Chapter 57: Configuring Point-to-Point Protocol over Ethernet Table 82: PPPoE Trace Operation Flags (continued) Flag Description Trace signal operations signal Trace state handling events state Trace timer processing timer Trace user interface processing To configure the flags for the events to be logged, configure the flags: [edit protocols pppoe traceoptions] user@host# set flag authentication Troubleshooting PPPoE Service Name Tables...
Page 918: Verifying A Pppoe Configuration
JUNOS 10.1 Network Interfaces Configuration Guide interface is increasing, but the number of PADO packets sent remains at zero. The following sample output shows a PADI count of 100 and a PADO count of 0. user@host> show pppoe statistics ge-2/0/3.1 Active PPPoE sessions: 0 PacketType Sent...
Page 919 Chapter 57: Configuring Point-to-Point Protocol over Ethernet To verify a PPPoE configuration, you can issue the following operational mode Action commands: show interfaces at-fpc/pic/port extensive show interfaces pp0 show pppoe interfaces show pppoe version show pppoe service-name-tables show pppoe statistics show pppoe underlying-interfaces For more information about these operational mode commands, see the JUNOS Software Administration Guide and the JUNOS Interfaces Command Reference.
Page 920 JUNOS 10.1 Network Interfaces Configuration Guide Verifying a PPPoE Configuration...
Page 921: Configuring Ethernet Ring Protection Switching
Chapter 58 Configuring Ethernet Ring Protection Switching Ethernet Ring Protection Switching Overview on page 851 Understanding Ethernet Ring Protection Switching Functionality on page 852 Configuring Ethernet Ring Protection Switching on page 856 Example: Ethernet Ring Protection Switching Configuration on page 857 Ethernet Ring Protection Switching Overview MX Series routers support Ethernet ring protection switching, which helps achieve high reliability and network stability.
Page 922: Acronyms
JUNOS 10.1 Network Interfaces Configuration Guide Understanding Ethernet Ring Protection Switching Functionality Acronyms on page 852 Ring Nodes on page 852 Ring Node States on page 853 Failure Detection on page 853 Logical Ring on page 853 FDB Flush on page 853 Traffic Blocking and Forwarding on page 853 RAPS Message Blocking and Forwarding on page 854 Dedicated Signaling Control Channel on page 855...
Page 923 Chapter 58: Configuring Ethernet Ring Protection Switching Ring Node States There are three different states for each node of a specific ring: init—Not a participant of a specific ring. idle—No failure on the ring, the node is performing normally. For normal node, traffic is unblocked on both ring ports.
Page 924: Figure 69: Protocol Packets From The Network To The Router
(01-19-a7-00-00-01) west ring port (STP index state does not apply) Juniper Networks routers use an implicit filter to achieve these routes. Each implicit filter binds to a bridge domain. Therefore, the east ring port control channel and the west ring port control channel of a particular ring instance must be configured to the same bridge domain.
Page 925: Manual Switch
Chapter 58: Configuring Ethernet Ring Protection Switching Control channel related terms: if [destination is the RAPS PDU multicast address(0x01,0x19,0xa7,0x00,0x00, 0x01] AND[ring port STP status is FORWARDING] AND [Incoming interface IFL equal to control channel IFL] { send packet to CPU and send to the other ring port } default term: accept packet.
Page 926: Node Id
JUNOS 10.1 Network Interfaces Configuration Guide Node ID For each node in the ring, a unique node ID identifies each node. The node ID is the node's MAC address. You can configure this node ID when configuring the ring on the node or automatically select an ID such as STP.
Page 927: Example: Ethernet Ring Protection Switching Configuration
Chapter 58: Configuring Ethernet Ring Protection Switching Example: Ethernet Ring Protection Switching Configuration This example describes how to configure Ethernet ring protection switching: Requirements on page 857 Ethernet Ring Overview and Topology on page 857 Configuring a Three-Node Ring on page 857 Requirements This example uses the following hardware and software components: Router node 1 running JUNOS Software with two Gigabit Ethernet interfaces.
Page 928 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Node 1 interfaces { Step-by-Step Procedure ge-1/0/1 { vlan-tagging; encapsulation flexible-ethernet-services; unit 1 { encapsulation vlan-bridge; vlan-id 100; ge-1/2/4 { vlan-tagging; encapsulation flexible-ethernet-services; unit 1 { encapsulation vlan-bridge; vlan-id 100; bridge-domains { bd1 { domain-type bridge;...
Page 929 Chapter 58: Configuring Ethernet Ring Protection Switching maintenance-association 100 { mep 1 { interface ge-1/0/1; remote-mep 2 { action-profile rmep-defaults; maintenance-domain d2 { level 0; maintenance-association 100 { mep 1 { interface ge-1/2/4; remote-mep 2 { action-profile rmep-defaults; Configuring Node 2 interfaces { Step-by-Step Procedure ge-1/0/2 {...
Page 930 JUNOS 10.1 Network Interfaces Configuration Guide interface ge-1/0/2.1; protocols { protection-group { ethernet-ring pg102 { east-interface { control-channel ge-1/0/2.1; west-interface { control-channel ge-1/2/1.1; protocols { oam { ethernet { connectivity-fault-management { action-profile rmep-defaults { default-action { interface-down; maintenance-domain d1 { level 0;...
Page 931 Chapter 58: Configuring Ethernet Ring Protection Switching Configuring Node 3 interfaces { Step-by-Step Procedure ge-1/0/4 { vlan-tagging; encapsulation flexible-ethernet-services; unit 1 { encapsulation vlan-bridge; vlan-id 100; ge-1/0/3 { vlan-tagging; encapsulation flexible-ethernet-services; unit 1 { encapsulation vlan-bridge; vlan-id 100; bridge-domains { bd1 { domain-type bridge;...
Page 932 JUNOS 10.1 Network Interfaces Configuration Guide maintenance-domain d2 { level 0; maintenance-association 100 { mep 2 { interface ge-1/0/4; remote-mep 1 { action-profile rmep-defaults; maintenance-domain d3 { level 0; maintenance-association 100 { mep 2 { interface ge-1/0/3; remote-mep 1 { action-profile rmep-defaults;...
Page 933 Chapter 58: Configuring Ethernet Ring Protection Switching Restore Timer Quard Timer Operation state disabled disabled operational user@node1> show protection-group ethernet-ring statistics group-name pg101 Ethernet Ring statistics for PG pg101 RAPS sent RAPS received Local SF happened: Remote SF happened: NR event happened: NR-RB event happened: For Node 2 and Node 3, the outputs should be the same: Normal Situation—Other...
Page 934 JUNOS 10.1 Network Interfaces Configuration Guide Clear IFF ready Clear IFF ready user@node1> show protection-group ethernet-ring node-state Ethernet ring APS State Event Ring Protection Link Owner pg101 protected Restore Timer Quard Timer Operation state disabled disabled operational user@node1> show protection-group ethernet-ring statistics group-name pg101 Ethernet Ring statistics for PG pg101 RAPS sent RAPS received...
Page 935: Chapter 59 Example Ethernet Configurations
Chapter 59 Example Ethernet Configurations Example: Configuring Fast Ethernet Interfaces on page 865 Example: Configuring Gigabit Ethernet Interfaces on page 865 Example: Configuring Aggregated Ethernet Interfaces on page 866 Example: Configuring Aggregated Ethernet Link Protection on page 867 Example: Configuring Fast Ethernet Interfaces The following configuration is sufficient to get a Fast Ethernet interface up and running.
Page 936 JUNOS 10.1 Network Interfaces Configuration Guide The M160, M320, M120, T320, and T640 2-port Gigabit Ethernet PIC supports two independent Gigabit Ethernet links. Each of the two interfaces on the PIC is named: ge-fpc/pic/[0.1] Each of these interfaces has functionality identical to the Gigabit Ethernet interface supported on the single-port PIC.
Page 937 Chapter 59: Example Ethernet Configurations address 14.0.101.50/24; unit 2 { vlan-id 1025; family inet { address 14.0.102.50/24; unit 3 { vlan-id 4094; family inet { address 14.0.103.50/24; Example: Configuring Aggregated Ethernet Link Protection The following configuration enables link protection on the interface, and specifies interface as the primary link and as the secondary link.
Page 938 JUNOS 10.1 Network Interfaces Configuration Guide Example: Configuring Aggregated Ethernet Link Protection...
Page 939: Part 11 Configuring Isdn Interfaces
Part 11 Configuring ISDN Interfaces Configuring ISDN Interfaces on page 871 Configuring ISDN Interfaces...
Page 940 JUNOS 10.1 Network Interfaces Configuration Guide Configuring ISDN Interfaces...
Page 941: Isdn Interfaces Overview
Chapter 60 Configuring ISDN Interfaces ISDN Interfaces Overview on page 871 Configuring ISDN Services Physical and Logical Interface Properties on page 872 Configuring ISDN Physical Interface Properties on page 873 Configuring an ISDN Interface to Screen Incoming Calls on page 875 Configuring ISDN Logical Interface Properties on page 875 Disabling ISDN Processes on page 892 ISDN Interfaces Overview...
Page 942: Configuring Isdn Services Physical And Logical Interface Properties
JUNOS 10.1 Network Interfaces Configuration Guide Configuring ISDN Services Physical and Logical Interface Properties To configure ISDN services physical interface properties, include the isdn-options statement at the hierarchy level: [edit interfaces br-pim/0/port] [edit interfaces br-pim/0/port] isdn-options { calling-number number; incoming-called-number number <reject>; spid1 spid-string;...
Page 943: Configuring Isdn Physical Interface Properties
Chapter 60: Configuring ISDN Interfaces backup-options { interface dln.0; You can include these statements at the following hierarchy levels: [edit interfaces] [edit logical-systems logical-system-name interfaces] To configure the Services Router to reject incoming ISDN calls (supported when dial-in is configured), include the reject-incoming statement at the [edit system...
Page 944 JUNOS 10.1 Network Interfaces Configuration Guide calling-number number; incoming-called-number number <reject>; spid1 spid-string; spid2 spid-string; static-tei-val value; switch-type (att5e | etsi | ni1 | ntdms100 | ntt); t310 seconds; tei-option (first-call | power-up); dialer-options { pool pool-name <priority priority>; You can configure the following ISDN options: —The calling number included in outgoing calls.
Page 945: Configuring An Isdn Interface To Screen Incoming Calls
Chapter 60: Configuring ISDN Interfaces —Northern Telecom DMS-100 ntdms100 —NTT Group switch for Japan —When the Terminal Endpoint Identifier (TEI) negotiates with the ISDN tei-option provider. Specify first-call (activation does not occur until the call setup is sent) or power-up (activation occurs when the Services Router is powered on). The default value is power-up.
Page 946 JUNOS 10.1 Network Interfaces Configuration Guide encapsulation. For example, you cannot have both as multilink dialers simultaneously. If you need to have multiple multilink dialers, then the values should be dln.1 dln.2 , and so forth. Normal mode using encapsulation. This mode is used when the cisco-hdlc router is using one B-channel.
Page 947 Chapter 60: Configuring ISDN Interfaces deactivation-delay seconds; dial-string dial-string-numbers; idle-timeout seconds; incoming-map { caller (caller-id | accept-all); initial-route-check seconds; load-interval seconds; load-threshold percent; pool pool-name; redial-delay time; watch-list { [ routes ]; You can configure the following options: —ISDN activation delay, in seconds. Specify a number from activation-delay through 4294967295...
Page 948: Configuring An Isdn Dialer Interface As A Backup Interface
JUNOS 10.1 Network Interfaces Configuration Guide —Interval used to calculate the average load on the network. By load-interval default, the average interface load is calculated every 60 seconds. You can specify an interval from 20 through 180 seconds, configurable in intervals of 10 seconds. For more information about the load interval, see “Configuring Bandwidth on Demand”...
Page 949: Figure 72: Isdn Backup Topology
Chapter 60: Configuring ISDN Interfaces See Figure 72 on page 879 for the topology used for this example. Figure 72: ISDN Backup Topology ISDN network 172.16.10.2 172.16.10.1 br-6/0/0 Serial network 192.168.10.2 192.168.10.1 Configure dialer interface as the backup interface on the primary serial interface t1-4/0/1: [edit interfaces] Configuration on the...
Page 950: Applying The Dial-On-Demand Dialer Filter To The Dialer Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide isdn-options { calling-number 5558888; spid1 51255511110101 5551111; spid2 51255511120101 5551112; switch-type ni1; t310 70; dialer-options { pool 10 priority 3; pool 2 priority 25; Applying the Dial-on-Demand Dialer Filter to the Dialer Interfaces Dial-on-demand routing (DDR) links two sites over a public network and provides bandwidth.
Page 951: Configuring Bandwidth On Demand
Chapter 60: Configuring ISDN Interfaces Figure 73: Dialer Filter Topology ISDN switch Configuration for the [edit firewall family inet] dialer-filter interesting-traffic { Dialer Filter term 1 { from { destination-address { 10.2.1.1/30; then note; Configuration on the [edit interfaces] dl0 { Dialer Interface encapsulation ppp;...
Page 952: Configuring The Dialer Interface
JUNOS 10.1 Network Interfaces Configuration Guide To configure bandwidth on demand, perform the steps in the following sections to configure the dialer interface and the physical ISDN interfaces: Configuring the Dialer Interface on page 882 Configuring the ISDN Interface on page 883 Example: Configuring Bandwidth on Demand on page 883 Configuring the Dialer Interface To configure the dialer interface for bandwidth on demand, include the...
Page 953: Example: Configuring Bandwidth On Demand
Chapter 60: Configuring ISDN Interfaces —Protocol family information for the logical interface. For , specify family family inet (for Internet Protocol version 4 [IPv4]) suite. —Dialer filter name. The dialer filter applied here is configured at the filter [edit firewall family inet] hierarchy level and also applied to the physical ISDN interface.
Page 954: Configuring Dial-In And Callback
JUNOS 10.1 Network Interfaces Configuration Guide mrru 1500; #Allowed only when dialer is in multilink mode encapsulation multilink-ppp; rtp { f-max-period 100; queues q3; family inet { negotiate-address; [edit interfaces] Configuration for the br-3/0/0 { First Physical ISDN isdn-options { Interface switch-type ni1;...
Page 955: Configuring Callback
Chapter 60: Configuring ISDN Interfaces Configuring Callback on page 886 Example: Configuring Dial-In and Callback on page 886 Configuring Dial-In To configure the dialer interface for dial-in operation, include the incoming-map statement with options at the [edit interfaces dln unit logical-unit-number dialer-options] hierarchy level: [edit interfaces dln unit logical-unit-number] dialer-options {...
Page 956 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Callback To configure the dialer interface to call back a specific caller, include the caller caller-id statement and the statement at the callback [edit interfaces dln unit logical-unit-number dialer-options] hierarchy level: [edit interfaces dln unit logical-unit-number] dialer-options { incoming-map { caller caller-id;...
Page 957: Configuring Dialer Watch
Chapter 60: Configuring ISDN Interfaces dialer-options { incoming-map { caller 14082711234; pool 1; family inet { address 10.2.1.1; [edit interfaces] Configuration to Call dl0 { Back Calls from a encapsulation ppp; Specific Caller ID unit 0 { dialer-options { incoming-map { caller 14082711234;...
Page 958: Figure 75: Dialer Watch Topology
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces] dln { encapsulation (cisco-hdlc | multilink-ppp | ppp); hold-time (up | down) milliseconds; unit logical-unit-number { dialer-options { activation-delay seconds; deactivation-delay seconds; dial-string dial-string-numbers; hold-time seconds; initial-route-check seconds pool pool-name; watch-list { [ routes ];...
Page 959 Chapter 60: Configuring ISDN Interfaces pool 1 priority 1; Configuration for the [edit interfaces] dl0 { Dialer Interface unit 0 { dialer-options { pool 1; dial-string 384030; watch-list { 2.2.2.2/24; 3.3.3.3/24; family inet { address 40.0.0.1/8; Example: Complete ISDN Called-Calling Router Configuration This example configures the calling J Series router (R1) and the calling J Series router (R2).
Page 960 JUNOS 10.1 Network Interfaces Configuration Guide br-3/0/0 { traceoptions { flag q921; flag q931; file { isdn_logg; isdn-options { switch-type etsi; spid1 116; dialer-options { pool 100; dl100 { encapsulation ppp; unit 0 { dialer-options { pool 100; dial-string 119; family inet { filter { dialer nss;...
Page 961 Chapter 60: Configuring ISDN Interfaces Configuration of Called [edit] system { Router (R1) root-authentication { encrypted-password "$1$UfcFhjcm$ftfgaLjMgRvFHrT3obrHu."; ## SECRET-DATA services { web-management { http { interface [ fe-0/0/0.0 fe-0/0/1.0 ]; syslog { user * { any emergency; file messages { any any;...
Page 962: Disabling Isdn Processes
JUNOS 10.1 Network Interfaces Configuration Guide firewall { family inet { dialer-filter nss { term 1 { from { address { 10.1.1.0/24; then note; Disabling ISDN Processes You can disable ISDN entirely or disable certain processes at the system process level. To disable ISDN entirely, include the disable statement at the...
Page 963: Part 12 Configuring Sonet/Sdh Interfaces
Part 12 Configuring SONET/SDH Interfaces Configuring SONET/SDH Interfaces on page 895 Configuring SONET/SDH Interfaces...
Page 964 JUNOS 10.1 Network Interfaces Configuration Guide Configuring SONET/SDH Interfaces...
Page 965: Sonet/Sdh Interfaces Overview
Chapter 61 Configuring SONET/SDH Interfaces SONET/SDH Interfaces Overview on page 895 Configuring SONET/SDH Physical Interface Properties on page 896 Configuring the Media MTU on SONET/SDH Interfaces on page 928 Enabling Passive Monitoring on SONET/SDH Interfaces on page 929 Configuring the Clock Source on SONET/SDH Interfaces on page 930 Configuring Receive and Transmit Leaky Bucket Properties on SONET/SDH Interfaces on page 931 Damping Interface Transitions on SONET/SDH Interfaces on page 932...
Page 966 OC48c. SONET and SDH traffic streams exhibit very few differences in behavior that are significant to Juniper Networks SONET/SDH interfaces; in general, this chapter uses SONET/SDH to indicate behavior that is identical for the two standards. However, there is one important difference that requires you to configure the interface specifically for SONET or SDH mode.
Page 967: Configuring Sonet/Sdh Framing
Chapter 61: Configuring SONET/SDH Interfaces protect-circuit group-name; request; revert-time seconds; switching-mode (bidirectional | unidirectional); working-circuit group-name; bytes { e1-quiet value; f1 value; f2 value; s1 value; z3 value; z4 value; fcs (16 | 32); loopback (local | remote); mpls { pop-all-labels { required-depth number;...
Page 968: Configuring Sonet/Sdh Header Byte Values
JUNOS 10.1 Network Interfaces Configuration Guide Configuring SONET/SDH Header Byte Values on page 901 Configuring an Incrementing STM ID on page 902 Configuring the SONET/SDH Frame Checksum on page 903 Configuring Channelized IQ and IQE SONET/SDH Loop Timing on page 904 Configuring SONET/SDH Loopback Capability on page 904 Configuring the SONET/SDH Path Trace Identifier on page 905 Configuring SONET/SDH HDLC Payload Scrambling on page 906...
Page 969: Table 83: Type 1 Pic Mode Combinations
Chapter 61: Configuring SONET/SDH Interfaces NOTE: Automatic Protection Switching (APS) is used by SONET add/drop multiplexers (ADMs) to protect against circuit failures. If APS is configured, and you do not change the SONET/SDH mode on both the working and protection port, APS support will not function properly.
Page 970: Table 84: Type 2 Pic Mode Combinations
JUNOS 10.1 Network Interfaces Configuration Guide Table 84: Type 2 PIC Mode Combinations Mode Speed Configuration Default Mode 1-port OC48 1xOC48 concatenated Concatenated fpc/pic/0 speed oc48 1xOC48 nonconcatenated Nonconcatenated fpc/pic/0:0 speed oc12 1xOC12 concatenated fpc/pic/0 speed oc12 1xOC12 nonconcatenated fpc/pic/0 0 speed oc3 1xOC3 concatenated fpc/pic/0 speed oc3 4-port OC12...
Page 971: Table 85: Sonet/Sdh Framing Bytes For Specific Speeds
Chapter 61: Configuring SONET/SDH Interfaces Configuring SONET/SDH Header Byte Values To configure values in SONET/SDH header bytes, include the statement at the bytes [edit interfaces interface-name sonet-options] hierarchy level: [edit interfaces so-fpc/pic/port sonet-options] bytes { c2 value; e1-quiet value; f1 value; f2 value;...
Page 972 Z3, Z4—SONET/SDH overhead bytes E1—quiet default idle byte Configuring an Incrementing STM ID When configured in SDH framing mode, SONET/SDH interfaces on a Juniper Networks router might not interoperate with some older versions of ADMs or regenerators that require an incrementing STM ID.
Page 973 3, ..., 3*n. Their use was still unspecified although they might have been used to assist in frame alignment. You can configure an incrementing STM ID to enable your Juniper Networks router to interoperate with older equipment that relies on these bytes for frame alignment.
Page 974 JUNOS 10.1 Network Interfaces Configuration Guide Configuring Channelized IQ and IQE SONET/SDH Loop Timing By default, internal clocking (line timing) is used on channelized IQ and IQE interfaces. To configure SONET/SDH or DS3-level clocking, include the statement: loop-timing loop-timing; To explicitly configure the default line timing, include the no-loop-timing statement in the configuration:...
Page 975 Chapter 61: Configuring SONET/SDH Interfaces For channel 0 on channelized interfaces only, you can include the statement loopback at the [edit interfaces interface-name interface-type-options] hierarchy level. The loopback setting configured for channel 0 applies to all channels on the channelized interface. statement is ignored if you include it at this hierarchy level in the loopback configuration of other channels.
Page 976 JUNOS 10.1 Network Interfaces Configuration Guide identifier might be longer then 16 bytes. The SDH standards define a maximum 16-byte path trace. For this reason, the default path trace identifier might be truncated in SDH mode. You can prevent the path trace identifier from being truncated in SDH mode by configuring a path trace identifier that is under 16-bytes long.
Page 977: Table 86: Sonet/Sdh Default Settings
Table 86 on page 907 shows the older (RFC 1619) and newer (RFC 2615) values, together with the Juniper Networks default values. Table 86: SONET/SDH Default Settings Value...
Page 978 JUNOS 10.1 Network Interfaces Configuration Guide Table 87: SONET/SDH and ATM Active Alarms and Defects (continued) Alarm Description Line ais-l Alarm indication signal—line rfi-l Remote failure indication—line ber-sd Bit error rate defect-signal degrade ber-sf Bit error rate fault-signal fail Path ais-p Alarm indication signal—path (ATM only)
Page 979 Chapter 61: Configuring SONET/SDH Interfaces To prevent route flaps from happening before a defect has been outstanding for a longer period than would be expected for an Automatic Protection Switching (APS) cutover To reduce the number of interface transitions NOTE: On M Series and T Series routers with Channelized SONET IQ PICs and Channelized SONET IQE PICs, the SONET defect alarm trigger hold-time statement...
Page 980 JUNOS 10.1 Network Interfaces Configuration Guide the defect is still present, the SONET/SDH defect starts the 250 millisecond down timer. After this has expired and again assuming the defect is still outstanding, the interface will be marked down. For more information about interface hold timers, see “Damping Interface Transitions”...
Page 981 Chapter 61: Configuring SONET/SDH Interfaces [edit interfaces cau4-fpc/pic/port sonet-options] vtmapping (klm | itu-t); For the STM1 PIC, you can configure virtual tributary mapping by including the vtmapping statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level: [edit chassis fpc slot-number pic pic-number] vtmapping (klm | itu-t);...
Page 982: Configuring Basic Aps Support
JUNOS 10.1 Network Interfaces Configuration Guide Figure 76: APS/MSP Configuration Topologies To configure APS or MSP, include the statement at the [edit interfaces hierarchy level: interface-name sonet-options] [edit interfaces interface-name sonet-options] aps { advertise-interval milliseconds; annex-b authentication-key key; force; hold-time milliseconds; lockout;...
Page 983 Chapter 61: Configuring SONET/SDH Interfaces NOTE: This implementation of APS is not supported on Layer 2 circuits. For Layer 2 circuits, configure APS by including the protect-interface statement. You can include this statement at the following hierarchy levels: [edit logical-systems logical-system-name protocols l2circuit neighbor neighbor-id interface interface-name] [edit protocols l2circuit neighbor neighbor-id interface interface-name] For more information and a configuration example, see the JUNOS VPNs Configuration...
Page 984 JUNOS 10.1 Network Interfaces Configuration Guide working and protect routers and that you configure the interface address of this shared network as the neighbor address. The working and protect configurations on the routers must match the circuit configurations on the ADM; that is, the working router must be connected to the ADM s working circuit and the protect router must be connected to the protect circuit.
Page 985 Chapter 61: Configuring SONET/SDH Interfaces Configuring Container Interfaces The JUNOS Software supports container interfaces for APS on SONET links. Physical interfaces and logical interfaces remain up on switchover, and their APS parameters are auto-copied from the container interface to the member links. See “Container Interfaces Overview”...
Page 986 JUNOS 10.1 Network Interfaces Configuration Guide b. Specify the container interface encapsulation as cisco-hdlc [edit interfaces cin] user@host# set encapsulation (cisco-hdlc | ppp) Specify the container options ; a SONET interface is container-type required for APS selection: [edit interfaces cin] user@host# set container-options container-type aps d.
Page 987 Chapter 61: Configuring SONET/SDH Interfaces user@host# set container-options container-list ci0 standby # Set so-0/0/1 as APS standby interface Optionally, you can set the statement to allow the allow-configuration-override physical configuration of a member link to override the container configuration: [edit interfaces so-0/0/1] user@host# set container-options container-list ci0 standby allow-configuration-override The following is a sample container interface configuration:...
Page 988 JUNOS 10.1 Network Interfaces Configuration Guide so-1/2/2 MEMBER_OF_ci0 Working enabled, up so-1/2/3 MEMBER_OF_ci0 Protect disabled, up Configuring APS Using a Container Interface with ATM Encapsulation M Series, T Series, and TX Matrix platforms with ATM-II PICs automatically copy the parent container interface (CI) configuration to the specified children interfaces. All ATM configurations configured in a single location on the parent container interface are automatically copied to the children interfaces.
Page 989 Chapter 61: Configuring SONET/SDH Interfaces aps; member-interface-type { atm { member-interface-speed oc3; unit 0 { vci 100; oam-period 3; family inet { address 1.0.0.1/30; unit 1 { vci 200; oam-period 3; family inet { address 2.0.0.1/30; Viewing the APS Container Interface Configuration You can use the following show commands to view the APS container interface...
Page 990 JUNOS 10.1 Network Interfaces Configuration Guide disabled. The input traffic received on the working circuit (current backup) is accepted by the PIC but discarded in the PFE. The show interface extensive show monitor interface traffic commands displays live statistics for the traffic since it is accepted by the PIC.
Page 991 Chapter 61: Configuring SONET/SDH Interfaces To configure a lockout of protection, forcing the use of the working circuit and locking out the protect circuit regardless of anything else, include the statement at lockout [edit interfaces interface-name sonet-options aps] hierarchy level: [edit interfaces so-fpc/pic/port sonet-options aps] lockout;...
Page 992 JUNOS 10.1 Network Interfaces Configuration Guide If you are using nonrevertive APS, you can use the statement to request working switch the circuit manually to being the working circuit or to override the revert timer (configured with the revert-time statement). Configuring Unidirectional Switching Mode Support You can configure interoperation with SONET/SDH Line Terminating Equipment (LTE) that is provisioned for unidirectional linear APS in 1+1 architecture on the...
Page 993 Chapter 61: Configuring SONET/SDH Interfaces To restore the default behavior, include the statement, switching-mode bidirectional at the [edit interfaces interface-name sonet-options aps] hierarchy level: [edit interfaces interface-name sonet-options aps] switching-mode bidirectional; Configuring APS Timers The protect and working routers periodically send packets to their neighbors to advertise that they are operational.
Page 994 JUNOS 10.1 Network Interfaces Configuration Guide To configure link state replication, include the statement at the preserve-interface [edit interfaces interface-name sonet-options aps] hierarchy level on the interfaces on both PICs: preserve-interface; APS functionality must be available on the SONET PICs and the interface configurations must be identical on both ends of the link.
Page 995 Chapter 61: Configuring SONET/SDH Interfaces working circuit “Start” were to fail, Router B would end up carrying all the traffic for both the “Start” and “Up” circuits. To balance the load between the circuits, you pair the two circuits. In this case, you pair the “Start”...
Page 996: Figure 77: Aps Load Sharing Between Circuit Pairs
JUNOS 10.1 Network Interfaces Configuration Guide Figure 77: APS Load Sharing Between Circuit Pairs To configure load sharing between two working–protect circuit pairs, include the paired-group statement when configuring one of the circuits on one of the routers. In this statement, the is the name of the group you assigned to one of the group-name circuits with the...
Page 997: Configuring Sonet Options For 10-Gigabit Ethernet Interfaces
Chapter 61: Configuring SONET/SDH Interfaces automatically configures the remainder of the load-sharing setup based on the group name. [edit interfaces so-fpc/pic/port sonet-options aps] paired-group group-name; Example: Configuring APS Load Sharing Between Circuit Pairs Configure APS load sharing to match the configuration shown in Figure 77 on page 926: [edit interfaces so-7/0/0 sonet-options aps] On Router A user@host# set working-circuit start...
Page 998: Configuring The Media Mtu On Sonet/Sdh Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces] xe-0/0/0 { sonet-options { loopback (local | remote); mpls { pop-all-labels { required-depth number; path-trace trace-string; trigger { defect ignore { defect hold-time up milliseconds down milliseconds; For information about using the loopback statement, see “Configuring SONET/SDH Loopback Capability”...
Page 999: Enabling Passive Monitoring On Sonet/Sdh Interfaces
Chapter 61: Configuring SONET/SDH Interfaces Enabling Passive Monitoring on SONET/SDH Interfaces The Monitoring Services I and Monitoring Services II PICs are designed to enable IP services. If you have a Monitoring Services PIC and a SONET/SDH PIC installed in an M160, M40e, or T Series router, you can monitor IPv4 traffic from another router. On SONET/SDH interfaces, you enable packet flow monitoring by including the statement: passive-monitor-mode...
Page 1000: Configuring The Clock Source On Sonet/Sdh Interfaces
JUNOS 10.1 Network Interfaces Configuration Guide [edit interfaces interface-name sonet-options mpls] pop-all-labels { required-depth number; By default, the statement takes effect for incoming packets with one or pop-all-labels two labels. You can specify the number of MPLS labels an incoming packet must have for the pop-all-labels statement to take effect by including the...
Page 1001: Configuring Receive And Transmit Leaky Bucket Properties On Sonet/Sdh Interfaces
Chapter 61: Configuring SONET/SDH Interfaces NOTE: On channelized STM1 interfaces, you should configure the clock source at one side of the connection to be internal (the default JUNOS Software configuration) and configure the other side of the connection to be external. To configure loop timing on an interface, include the statement at clocking external...

This manual is also suitable for:

Junos 10.1

Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010 Configuration Manual

About this Guide Lxiii

Part 1 Network Interfaces Configuration Statements Overview

Chapter 1 Network Interfaces Configuration Statements and Hierarchy

Part 2 Router Interfaces Configuration Concepts

Chapter 2 Understanding Router Interfaces

Configuring Physical Interface Properties

Chapter 4 Configuring Logical Interface Properties

Configuring Logical Interface Properties

Configuring Protocol Family and Interface Address Properties

Chapter 5 Configuring Protocol Family and Interface Address Properties

Chapter 6 Configuring Circuit and Translational Cross-Connects

Tracing Interface Operations

Displaying the Internal Ethernet Interface

Configuring Discard Interfaces

Configuring IP Demultiplexing Interfaces

Configuring the Loopback Interface

Configuring Serial Interfaces

Chapter 12 Configuring Serial Interfaces

Quick Links

Related Manuals for Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010

Summary of Contents for Juniper JUNOS 10.1 - CONFIGURATION GUIDE 1-2010