Professional Documents
Culture Documents
Junos Guide To Configuring Interfaces
Junos Guide To Configuring Interfaces
Junos Guide To Configuring Interfaces
Release
15.1
Modified: 2015-08-17
ii
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlv
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlv
Supported Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlv
Using the Examples in This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlv
Merging a Full Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlvi
Merging a Snippet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlvi
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlvii
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlix
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlix
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . xlix
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . l
Part 1
Ethernet Interfaces
Chapter 1
Chapter 2
iii
Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus
Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Chapter 3
Chapter 4
Chapter 5
Chapter 6
iv
Table of Contents
Chapter 7
MACsec Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Configuring Media Access Control Security (MACsec) on MX Series Routers . . . 98
Configuring MACsec Using Static Connectivity Association Key Security
Mode (Recommended for Enabling MACsec on Router-to-Router
Links) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Configuring MACsec on the Router Using Dynamic Secure Association Key
Security Mode to Secure a Router-to-Host Link . . . . . . . . . . . . . . . . . . . 104
Configuring MACsec Using Static Secure Association Key Security Mode to
Secure a Router-to-Router Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Example: Configuring MACsec over an MPLS CCC on MX Series Routers . . . . . . . 111
Chapter 8
vi
Table of Contents
vii
Chapter 9
Chapter 10
Chapter 11
viii
Table of Contents
Chapter 12
ix
Chapter 13
Table of Contents
Chapter 14
Chapter 15
Chapter 16
Chapter 17
xi
Chapter 18
Chapter 19
Chapter 20
Part 2
Chapter 21
xii
Table of Contents
Chapter 22
Chapter 23
Chapter 24
Chapter 25
Chapter 26
xiii
Chapter 27
Chapter 28
xiv
Table of Contents
Chapter 29
Chapter 30
xv
Part 3
Chapter 31
xvi
Table of Contents
Chapter 32
xvii
Chapter 33
xviii
Table of Contents
xix
xx
Table of Contents
Chapter 34
Part 4
Troubleshooting Information
Chapter 35
xxi
Part 5
Chapter 36
xxii
Table of Contents
xxiii
xxiv
Table of Contents
erroneous-ccm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 949
ether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
ethernet (Chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951
ethernet (Protocols OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
ethernet-policer-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 955
ethernet-ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
ethernet-switch-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
evcs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
evc-protocol cfm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
event (LFM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
event-thresholds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
exclude-protocol (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
exercise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
failover-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
fast-aps-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
fastether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 969
fec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
fixed-stuff-bytes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
flexible-vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
flow-control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
fnp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
force switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
force-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
forwarding-class (Gigabit Ethernet IQ Classifier) . . . . . . . . . . . . . . . . . . . . . . . . . 975
forwarding-mode (100-Gigabit Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
forwarding-mode (PTX Series Packet Transport Routers) . . . . . . . . . . . . . . . . . . 977
frame-error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
frame-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
frame-period-summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
framing (10-Gigabit Ethernet Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
gigether-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
gratuitous-arp-reply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
guest-vlan (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . . . . . 984
guard-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
hardware-assisted-timestamping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
hold-interval (OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
hold-interval (Protection Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
hold-multiplier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
iccp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
id (MACsec for MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
ieee802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
igmp-snooping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
ignore-l3-incompletes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
include-sci (MACsec for MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
ingress-policer-overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
ingress-rate-limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
inner-tag-protocol-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
inner-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
xxv
input-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
input-priority-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
input-three-color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
input-vlan-map (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
input-vlan-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1000
interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
interface (IEEE 802.1x) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
interface (OAM Link-Fault Management) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
interface (Static MAC Bypass) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
interface-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
interfaces (MACsec for MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1006
interface-none . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
interface-status-tlv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1008
interval (CFM MEP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
is-ma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
isolated-vlan (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
iteration-count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
iteration-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
key (MACsec for MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
key-server-priority (MACsec for MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1014
lacp (802.3ad) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
lacp (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
laser-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
layer2-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
level (CFM MEP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1019
line-loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
linktrace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
link-adjacency-loss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
link-discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
link-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
link-event-rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
link-fault-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023
link-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1025
link-protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1027
link-speed (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
link-speed (Aggregated SONET/SDH) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
lldp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
lldp-configuration-notification-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
lmi (Ethernet OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
load-balance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034
load-balance-stateful (Aggregated Ethernet Interfaces) . . . . . . . . . . . . . . . . . . 1035
load-type (Aggregated Ethernet Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1036
local-loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
lockout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
log-and-generate-ais . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
xxvi
Table of Contents
logical-interface-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) . . . . . . . 1040
loopback-tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
loss-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
loss-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
lowest-priority-defect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1043
mac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
mac (IRB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
mac-address (Accept Source Mac) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1045
mac-address (MACsec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1046
mac-learn-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047
mac-radius (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . . . . 1048
mac-validate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
macsec (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
maintenance-association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
maintenance-domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1052
major-ring-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
manual switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
master-only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1054
max-sessions (PPPoE Service Name Tables) . . . . . . . . . . . . . . . . . . . . . . . . . . 1055
max-sessions-vsa-ignore (Static and Dynamic Subscribers) . . . . . . . . . . . . . . 1056
maximum-links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1057
maximum-requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1058
maximum-requests (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . 1058
mc-ae . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059
measurement-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
mep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
minimum-bandwidth (aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064
minimum-links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1065
mip-half-function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1066
mixed-rate-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
mka (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1067
monitor-end-point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
must-secure (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069
mtu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
multicast-router-interface (IGMP Snooping) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
multi-chassis-protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1075
name-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076
native-vlan-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
negotiate-address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
negotiation-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
no-adaptive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079
no-allow-link-events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1079
no-encryption (MACsec for MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1080
no-auto-mdix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
no-gratuitous-arp-request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1081
no-keepalives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1082
no-mac-table-binding (802.1X for MX Series in Enhanced LAN Mode) . . . . . . 1082
no-odu-backward-frr-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083
xxvii
no-odu-signal-degrade-monitor-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1083
no-pre-classifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1084
no-reauthentication (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . 1084
no-send-pads-ac-info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
no-send-pads-error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1085
non-revertive (Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086
non-revertive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1086
non-vc-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087
node-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1087
number-of-frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1088
offset (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1089
oam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091
oc192 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093
odu-delay-management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094
odu-backward-frr-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1094
odu-signal-degrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1095
odu-signal-degrade-monitor-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
odu-ttim-action-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1096
optics-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1097
otn-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098
otu-ttim-action-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1099
otu4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1100
output-policer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1101
output-priority-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1102
output-three-color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1103
output-vlan-map (Aggregated Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104
output-vlan-map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1105
pado-advertise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
pass-through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1106
passive-monitor-mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1107
path-database-size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
pdu-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1108
pdu-threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
per-flow (Aggregated Ethernet Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1109
peer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1110
performance-monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1111
periodic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1112
policer (CFM Firewall) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1113
policer (CFM Global) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114
policer (CFM Session) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1115
policer (CoS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1116
policer (MAC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117
pop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1118
pop-pop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1119
pop-swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1120
port-description-type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121
port-id (MACsec for MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1122
port-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123
port-id-subtype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
xxviii
Table of Contents
port-status-tlv . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1125
pp0 (Dynamic PPPoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1126
ppm (Ethernet Switching) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1127
pppoe-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1128
pppoe-underlying-options (Static and Dynamic Subscribers) . . . . . . . . . . . . . . 1129
pre-shared-key (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1130
premium (Output Priority Map) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
premium (Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131
priority (Protocols OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132
priority (CFM MEP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1132
priority (OAM Connectivity-Fault Management) . . . . . . . . . . . . . . . . . . . . . . . . . 1133
propagate-tc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1133
protection-group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134
protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1136
protocol (Server MEP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
protocol-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1137
ptopo-configuration-maximum-hold-time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
ptopo-configuration-trap-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1138
push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1139
push-push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140
prbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1140
preemptive-fast-reroute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1141
premium (Output Priority Map) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
premium (Policer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
protect-maintenance-association (OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143
proxy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143
proxy-arp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1144
push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145
push-push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146
quiet-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1147
quiet-period (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . . . . 1147
rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1148
reauthentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1149
reauthentication (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . 1149
rebalance (Aggregated Ethernet Interfaces) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150
receive-ais . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1150
receive-options-packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151
receive-ttl-exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151
remote . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152
remote-loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1152
remote-maintenance-association (OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153
remote-mep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153
replay-window-size (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1154
replay-protect (MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155
restore-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1156
retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
retries (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1157
revertive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
ring-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1158
xxix
ring-protection-link-end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
ring-protection-link-owner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1159
routing-instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1160
routing-instance (PPPoE Service Name Tables) . . . . . . . . . . . . . . . . . . . . . . . . . 1161
sa-multicast (100-Gigabit Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1162
sa-multicast (PTX Series Packet Transport Routers) . . . . . . . . . . . . . . . . . . . . . 1163
secure-authentication (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . 1164
secure-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1165
security-association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1166
send-critical-event . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
server-fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1168
server-reject-vlan (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . 1169
server-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1170
server-timeout (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . . 1170
service (PPPoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1171
service-name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1172
service-name-table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1173
service-name-tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1174
session-expiry (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . . 1175
short-name-format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176
signal-degrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1177
signal-degrade-monitor-enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1178
source-address-filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1180
source-filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1181
speed (Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1182
speed (MX Series DPC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1183
sla-iterator-profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1184
sla-iterator-profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1185
stacked-vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1186
static (Protocols 802.1X) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1187
static-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1188
start-measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
supplicant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1189
supplicant (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . . . . . 1190
supplicant-timeout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1191
supplicant-timeout (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . 1191
swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
swap-by-poppush . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1192
swap-push . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1193
swap-swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194
switch-options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1194
switch-port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1195
symbol-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
syslog (OAM Action) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1196
system-id . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1197
system-priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1198
tag-protocol-id (TPIDs Expected to Be Sent or Received) . . . . . . . . . . . . . . . . . 1199
tag-protocol-id (TPID to Rewrite) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1200
xxx
Table of Contents
tca . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201
terminate (PPPoE Service Name Tables) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1203
traceoptions (Protocols LLDP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1204
traceoptions (Ethernet Ring Protection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1206
traceoptions (Interface Process) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1208
traceoptions (LACP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1210
traceoptions (PPPoE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1212
traceoptions (802.1X and Captive Portal for MX Series in Enhanced LAN
Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215
transmit-delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1216
transmit-interval (MACsec for MX Series) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1217
transmit-period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1218
transmit-period (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . 1218
transport-monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1219
trigger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1220
tti . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1225
tx-power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1226
uac-policy (MX Series in Enhanced LAN Mode) . . . . . . . . . . . . . . . . . . . . . . . . . 1226
underlying-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1227
unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1228
unnumbered-address (PPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234
version-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
virtual-control-channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236
virtual-switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1236
vlan-assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1237
vlan-id (VLAN ID to Be Bound to a Logical Interface) . . . . . . . . . . . . . . . . . . . . . 1237
vlan-id (VLAN ID to Rewrite) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1238
vlan-id-list (Ethernet VLAN Circuit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1239
vlan-id-list (Interface in Bridge Domain) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241
vlan-id-range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1242
vlan-rewrite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1243
vlan-rule (100-Gigabit Ethernet Type 4 PIC with CFP) . . . . . . . . . . . . . . . . . . . . 1244
vlan-steering (100-Gigabit Ethernet Type 4 PIC with CFP) . . . . . . . . . . . . . . . . 1245
vlan-tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
vlan-tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1247
vlan-tags (Dual-Tagged Logical Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1248
vlan-tags (Stacked VLAN Tags) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1250
wait-to-block-interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1251
warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1252
wavelength . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1253
west-interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
Chapter 37
xxxi
xxxii
Table of Contents
Part 6
Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1849
xxxiii
xxxiv
List of Figures
Part 1
Ethernet Interfaces
Chapter 6
Chapter 8
Chapter 9
Chapter 10
Chapter 13
Chapter 14
Chapter 17
xxxv
Chapter 18
Chapter 20
Part 2
Chapter 21
Chapter 30
Part 3
Chapter 31
Chapter 32
Chapter 33
Chapter 34
xxxvi
List of Figures
Figure 50: ERP with Multiple Protection Instances Configured on Three MX Series
Routers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 754
Part 4
Troubleshooting Information
Chapter 35
xxxvii
xxxviii
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlv
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlvii
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xlviii
Part 1
Ethernet Interfaces
Chapter 6
Chapter 7
Chapter 8
Chapter 12
Chapter 13
xxxix
Table 21: Components of the Topology for Configuring a Secondary VLAN Trunk
on Switch 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Table 22: Components of the Topology for Configuring a Secondary VLAN Trunk
on Switch 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Part 2
Chapter 21
Chapter 22
Chapter 26
Chapter 27
Chapter 28
Chapter 29
Chapter 30
xl
List of Tables
Part 3
Chapter 31
Chapter 33
Chapter 34
Part 4
Troubleshooting Information
Chapter 35
xli
Part 5
Chapter 36
Chapter 37
xlii
List of Tables
xliii
xliv
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/.
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Supported Platforms
For the features described in this document, the following platforms are supported:
ACX Series
M Series
MX Series
T Series
PTX Series
xlv
configuration into the current candidate configuration. The example does not become
active until you commit the candidate configuration.
If the example configuration contains the top level of the hierarchy (or multiple
hierarchies), the example is a full example. In this case, use the load merge command.
If the example configuration does not start at the top level of the hierarchy, the example
is a snippet. In this case, use the load merge relative command. These procedures are
described in the following sections.
From the HTML or PDF version of the manual, copy a configuration example into a
text file, save the file with a name, and copy the file to a directory on your routing
platform.
For example, copy the following configuration to a file and name the file ex-script.conf.
Copy the ex-script.conf file to the /var/tmp directory on your routing platform.
system {
scripts {
commit {
file ex-script.xsl;
}
}
}
interfaces {
fxp0 {
disable;
unit 0 {
family inet {
address 10.0.0.1/24;
}
}
}
}
2. Merge the contents of the file into your routing platform configuration by issuing the
Merging a Snippet
To merge a snippet, follow these steps:
1.
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.
For example, copy the following snippet to a file and name the file
ex-script-snippet.conf. Copy the ex-script-snippet.conf file to the /var/tmp directory
on your routing platform.
xlvi
commit {
file ex-script-snippet.xsl; }
2. Move to the hierarchy level that is relevant for this snippet by issuing the following
For more information about the load command, see the CLI User Guide.
Documentation Conventions
Table 1 on page xlvii defines notice icons used in this guide.
Meaning
Description
Informational note
Caution
Warning
Laser warning
Tip
Best practice
Table 2 on page xlviii defines the text and syntax conventions used in this guide.
xlvii
Description
Examples
| (pipe symbol)
broadcast | multicast
# (pound sign)
[ ] (square brackets)
; (semicolon)
[edit]
root@# set system domain-name
domain-name
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
GUI Conventions
xlviii
Description
Examples
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
Online feedback rating systemOn any page at the Juniper Networks Technical
Documentation site at http://www.juniper.net/techpubs/index.html, simply click the
stars to rate the content, and use the pop-up form to provide us with information about
your experience. Alternately, you can use the online feedback form at
https://www.juniper.net/cgi-bin/docbugreport/.
JTAC hours of operationThe JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
xlix
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
PART 1
Ethernet Interfaces
Configuring Ethernet Automatic Protection Switching for High Availability on page 215
Configuring Ethernet Ring Protection Switching for High Availability on page 223
CHAPTER 1
Fast Ethernet
Gigabit Ethernet
10-Gigabit Ethernet
100-Gigabit Ethernet
Internal Ethernet interface, which connects the Routing Engine to the packet forwarding
components
Related
Documentation
Related
Documentation
CHAPTER 2
Configuring MAC Address Filtering on PTX Series Packet Transport Routers on page 17
Displaying Internal Ethernet Interfaces for a Routing Matrix with a TX Matrix Plus
Router on page 23
fe-5/2/1 {
unit 0 {
family inet {
address local-address;
}
}
}
}
Related
Documentation
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.
Related
Documentation
(flow-control | no-flow-control);
ignore-l3-incompletes;
ingress-rate-limit rate;
(loopback | no-loopback);
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
native-vlan-id number;
}
To configure OAM 802.3ah support for Ethernet interfaces, include the oam statement
at the [edit protocols] hierarchy level.
oam {
ethernet {
link-fault-management {
interfaces {
interface-name{
pdu-interval interval;
link-discovery (active | passive);
pdu-threshold count;
}
}
}
}
}
Related
Documentation
NOTE: On MX Series routers with tri-rate copper SFP interfaces, if the port
speed is negotiated to the configured value and the negotiated speed and
interface speed do not match, the link will not be brought up.
10
NOTE: When you configure the Tri-Rate Ethernet copper interface to operate
at 1 Gbps, autonegotiation must be enabled.
To explicitly configure the speed, include the speed statement at the [edit interfaces
interface-name] hierarchy level:
[edit interfaces interface-name]
speed (10m | 100m | 1g);
Related
Documentation
Related
Documentation
11
When the receive buffers on interface Node A reach a certain level of fullness, the
interface generates and sends an Ethernet PAUSE message to the connected peer
(interface Node B) to tell the peer to stop sending frames. The Node B buffers store
frames until the time period specified in the Ethernet PAUSE frame elapses; then Node
B resumes sending frames to Node A.
When interface Node A receives an Ethernet PAUSE message from interface Node B,
interface Node A stops transmitting frames until the time period specified in the Ethernet
PAUSE frame elapses; then Node A resumes transmission. (The Node A transmit
buffers store frames until Node A resumes sending frames to Node B.)
In this scenario, if Node B sends an Ethernet PAUSE frame with a time value of 0 to
Node A, the 0 time value indicates to Node A that it can resume transmission. This
happens when the Node B buffer empties to below a certain threshold and the buffer
can once again accept traffic.
12
When you enable symmetric flow control on an interface, the Ethernet PAUSE behavior
depends on the configuration of the connected peer. With symmetric flow control enabled,
the interface can perform any Ethernet PAUSE functions that the connected peer can
perform. (When symmetric flow control is disabled, the interface does not send or respond
to Ethernet PAUSE messages.)
Related
Documentation
Related
Documentation
13
NOTE: For M Series, MX Series, and most T Series routers, the management
Ethernet interface is fxp0. For T1600 and T4000 routers configured in a
routing matrix, and TX Matrix Plus routers, the management Ethernet interface
is em0.
NOTE: Automated scripts that you have developed for standalone T1600
routers (T1600 routers that are not in a routing matrix) might contain
references to the fxp0 management Ethernet interface. Before reusing the
scripts on T1600 routers in a routing matrix, edit the command lines that
reference the fxp0 management Ethernet interface so that the commands
reference the em0 management Ethernet interface instead.
NOTE: When you configure the Tri-Rate Ethernet copper interface to operate
at 1 Gbps, autonegotiation must be enabled.
NOTE: When you manually configure Fast Ethernet interfaces on the M Series
and T Series routers, link mode and speed must both be configured. If both
these values are not configured, the router uses autonegotiation for the link
and ignores the user-configured settings.
14
Related
Documentation
NOTE: When you integrate a standalone T640 router into a routing matrix,
the PIC media access control (MAC) addresses for the integrated T640
router are derived from a pool of MAC addresses maintained by the TX
Matrix router. For each MAC address you specify in the configuration of a
formerly standalone T640 router, you must specify the same MAC address
in the configuration of the TX Matrix router.
Similarly, when you integrate a T1600 or T4000 router into a routing matrix,
the PIC MAC addresses for the integrated T1600 or T4000 router are
derived from a pool of MAC addresses maintained by the TX Matrix Plus
router. For each MAC address you specify in the configuration of a formerly
standalone T1600 or T4000 router, you must specify the same MAC
address in the configuration of the TX Matrix Plus router.
15
source-address-filter {
mac-address;
<additional-mac-address>;
}
You can specify the MAC address as nn:nn:nn:nn:nn:nn or nnnn .nnnn.nnnn, where n is a
hexadecimal number. You can configure up to 64 source addresses. To specify more
than one address, include the source-address-filter statement multiple times.
16
Related
Documentation
When you filter logical and physical interfaces, you can specify up to 1000 MAC source
addresses per port.
To configure MAC source address filtering for a physical interface, include the
source-filtering and source-address-filter statements at the [edit interfaces et-fpc/pic/port
gigether-options] hierarchy level:
[edit interfaces]
et-x/y/z {
gigether-options {
source-filtering;
source-address-filter {
mac-address;
}
}
}
The source-address-filter statement configures which MAC source addresses are filtered.
The specified physical interface drops all packets from the MAC source addresses you
specify. You can specify the MAC address as nn:nn:nn:nn:nn:nn where n is a decimal digit.
To specify more than one address, include multiple mac-address options in the
source-address-filter statement.
17
To configure MAC source address filtering for a logical interface, include the
accept-source-mac statement at the [edit interfaces et-fpc/pic/port unit
logical-unit-number] hierarchy level:
[edit interfaces]
et-x/y/z {
gigether-options {
source-filtering;
}
unit logical-unit-number {
accept-source-mac {
mac-address mac-address;
}
}
}
The accept-source-mac statement configures which MAC source addresses are accepted
on the logical interface. You can specify the MAC address as nn:nn:nn:nn:nn:nn where n
is a decimal digit. To specify more than one address, include multiple mac-address
mac-address options in the accept-source-mac statement.
After an interface filter is configured, there is an accounting entry that is associated with
the MAC address filter. Counters accumulate if there are packets with matching MAC
source addresses. You can use the show interfaces mac-database Junos OS CLI command
to view the address count.
Related
Documentation
18
behavior occurs because MPCs do not support destination MAC address learning. As a
result, if a packet exits a child link without passing in the ingress direction through that
link, destination MAC (DMAC) accounting for this packet occurs at the child link level
and this data is not available at the aggregate level. Dynamic learning of MAC addresses
can be supported on only the AE interface or on selective individual member links. MAC
learning support on the bundle depends on the capability of individual member links. If
a link in the bundle does not contain the capability to support MAC learning or accounting,
it is disabled on the AE bundle.
The MAC data for the aggregated bundle is displayed by collecting data form individual
child links. This data is collected when the command to display the MAC database is
triggered from the CLI. This method of data collection implies that based on the number
of child links and the size of the MAC database, the time take to display the database
differs. This approach to obtain the current snapshot of the MAC database from the
currently active child links is used instead of maintaining a database at the Routing Engine
because of the dynamic nature of the MAC database and the overhead required to
maintain the database information in synchronization with all the child Packet Forwarding
Engines. A difference in the DMAC-based accounting for packets generated from the
Routing Engine (packets sent in the host path). On DPCs, these packets are accounted
in egress direction (Output Packet/Byte count), whereas on MPCs, these packets are
not accounted because DMAC learning is not supported. This difference in behavior also
occurs between child links on DPCs and MPCs. Because this feature to enable dynamic
learning is related to collecting MAC database statistics from child links based on the
command issued from the CLI, there is a impact on the time it takes to display the data
on the console based on the size of the MAC database and the number of child-links
spread across different FPCs. The limit on the maximum number of MAC addresses that
can be learned from an interface does not apply to this dynamic learning of MAC addresses
functionality.
Related
Documentation
NOTE: If you configure a local loopback on a 1-port 10-Gigabit IQ2 and IQ2-E
PIC using the loopback statement at the [edit interfaces interface-name
gigether-options] hierarchy level, the transmit-path stops working, causing
the remote end to detect a link down.
19
You can include the loopback and no-loopback statements at the following hierarchy
levels:
Related
Documentation
Related
Documentation
20
Gratuitous ARP replies are reply packets sent to the broadcast MAC address with the
target IP address set to be the same as the senders IP address. When the router or switch
receives a gratuitous ARP reply, the router or switch can insert an entry for that reply in
the ARP cache.
Gratuitous ARP packets are sent across unnumbered interfaces only when a change in
the local MAC address occurs.
By default, updating the ARP cache on gratuitous ARP replies is disabled on the router
or switch. On Ethernet interfaces, you can enable handling of gratuitous ARP replies on
a specific interface by including the gratuitous-arp-reply statement at the [edit interfaces
interface-name] hierarchy level:
[edit interfaces interface-name]
gratuitous-arp-reply;
Related
Documentation
21
ARP entries. In most environments, the default ARP aging timer value does not need to
be adjusted.
To configure the system-wide ARP aging timer, include the aging-timer statement at the
[edit system arp] hierarchy level:
[edit system arp]
user@host# aging-timer minutes
The aging timer range is from 1 through 240 minutes. The timer value you configure takes
effect as ARP entries expire. In other words, each subsequent refreshed ARP entry receives
the new timer value. The new timer value does not apply to ARP entries that exist at the
time you commit the configuration.
For more information about statements you can configure at the [edit system] hierarchy
level, see the Junos OS Administration Library for Routing Devices.
Related
Documentation
arp (System)
For information on configuring WRED, see the Class of Service Feature Guide for Routing
Devices.
22
To display multicast statistics, use the show interfaces interface-name statistics detail
command.
Related
Documentation
multicast-statistics
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 routers
packet forwarding components. The Junos OS automatically configures internal Ethernet
interfaces. For TX Matrix Plus routers, the internal Ethernet interfaces are ixgbe0 and
ixgbe1. For T1600 routers configured in a routing matrix, the internal Ethernet interfaces
are bcm0 and em1. For more information about internal Ethernet interfaces, see
Understanding Internal Ethernet Interfaces.
NOTE: Do not modify or remove the configuration for the internal Ethernet
interface that the Junos OS automatically configures. If you do, the router
will stop functioning.
Local
Remote
192.168.35.95/24
Local
Remote
23
ixgbe0.0
up
up
inet
inet6
tnp
10.34.0.4/8
162.0.0.4/2
fe80::200:ff:fe22:4/64
fec0::a:22:0:4/64
0x22000004
Local
Remote
10.34.0.4/8
162.0.0.4/2
fe80::200:1ff:fe22:4/64
fec0::a:22:0:4/64
0x22000004
The following example is a sequence of show interfaces commands issued in a CLI 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.
This T1600 router is connected to the routing matrix through a connection in the
TXP-SIB-F13 in slot 2 of the SCC. The commands display information about the
management Ethernet interface and both internal Ethernet interfaces configured on the
Routing Engine to which you are currently logged in:
The previous example shows a CLI session with the TX Matrix Plus router. To display
interface information about the T1600 router known as host-sfc-0-lcc-2, first use the
request routing-engine login command to log in to that LCC.
user@host-sfc-0> request routing-engine login lcc 2
--- JUNOS 9.6I built 2009-06-22 18:13:04 UTC
% cli
warning: This chassis is a Line Card Chassis (LCC) in a multichassis system.
warning: Use of interactive commands should be limited to debugging.
warning: Normal CLI access is provided by the Switch Fabric Chassis (SFC).
warning: Please logout and log into the SFC to use CLI.
24
Remote
Remote
inet6
tnp
129.0.0.5/2
fe80::201:ff:fe01:5/64
fec0::a:1:0:5/64
0x1000005
Related
Documentation
25
26
CHAPTER 3
Configuring MAC Address Filtering on PTX Series Packet Transport Routers on page 17
27
NOTE: For M Series, MX Series, and most T Series routers, the management
Ethernet interface is fxp0. For TX Matrix Plus routers and T1600 or T4000
routers configured in a routing matrix, the management Ethernet interface
is em0.
NOTE: Automated scripts that you have developed for standalone T1600
routers (T1600 routers that are not in a routing matrix) might contain
references to the fxp0 management Ethernet interface. Before reusing the
scripts on T1600 routers in a routing matrix, edit the command lines that
reference the fxp0 management Ethernet interface so that the commands
reference the em0 management Ethernet interface instead.
28
address 10.17.40.133/25;
}
}
This feature is available on all routers that include dual Routing Engines. On the TX Matrix
router, this feature is applicable to the switch-card chassis (SCC) only.
Related
Documentation
NOTE: For M Series, MX Series, and most T Series routers, the management
Ethernet interface is fxp0. For TX Matrix Plus routers and T1600 routers
configured in a routing matrix, and TX Matrix Plus routers with 3D SIBs, T1600
routers, and T4000 routers configured in a routing matrix, the management
Ethernet interface is em0.
NOTE: Automated scripts that you have developed for standalone T1600
routers (T1600 routers that are not in a routing matrix) might contain
references to the fxp0 management Ethernet interface. Before reusing the
scripts on T1600 routers in a routing matrix, edit the command lines that
reference the fxp0 management Ethernet interface so that the commands
reference the em0 management Ethernet interface instead.
To display the MAC address used by the routers management Ethernet interface, enter
the show interface fxp0 or show interface em0 operational mode command.
To change the management Ethernet interfaces MAC address, include the mac statement
at the [edit interfaces fxp0] or [edit interfaces em0] hierarchy level:
[edit interfaces (fxp0 | em0)]
mac mac-address;
Specify the MAC address as six hexadecimal bytes in one of the following formats:
nnnn.nnnn.nnnn (for example, 0011.2233.4455) or nn:nn:nn:nn:nn:nn (for example,
00:11:22:33:44:55).
29
NOTE: If you integrate a standalone T640 router into a routing matrix, the
PIC MAC addresses for the integrated T640 router are derived from a pool
of MAC addresses maintained by the TX Matrix router. For each MAC address
you specify in the configuration of a formerly standalone T640 router, you
must specify the same MAC address in the configuration of the TX Matrix
router.
Similarly, if you integrate a standalone T1600 router into a routing matrix,
the PIC MAC addresses for the integrated T1600 router are derived from a
pool of MAC addresses maintained by the TX Matrix Plus router. For each
MAC address you specify in the configuration of a formerly standalone T1600
router, you must specify the same MAC address in the configuration of the
TX Matrix Plus router.
Related
Documentation
30
Configuring MAC Address Filtering on PTX Series Packet Transport Routers on page 17
CHAPTER 4
NOTE: I2.0 based M120 routers and I3.0 based M320 routers with the PICs
in the preceding list support passive monitoring starting with Junos OS Release
9.5. Other M Series and T Series routers with the PICs listed above started
supporting passive monitoring before Junos OS Release 7.3. Support for 1-port
10-Gigabit Ethernet PIC with XENPAK on I2.0-based M120 routers and
I3.0-based M320 routers was added in Junos OS Release 9.5.
4-port 10-Gigabit Ethernet LAN/WAN PIC with XFP (T640, T1600, and T4000 Core
Routers) (supported on both WAN-PHY and LAN-PHY modes for both IPv4 and IPv6
addresses)
The following interfaces support passive monitoring on the I3.0-based MX 240, MX 480,
and MX 960 routers, starting with Junos OS Release 8.5:
31
Type 2 MX FPCs
Type 3 MX FPCs
The following interfaces support passive monitoring on the Trio-based MX 240, MX 480,
and MX 960 routers:
4-port 10-Gigabit Ethernet LAN/WAN PIC with XFP (supported on both WAN-PHY
and LAN-PHY modes for both IPv4 and IPv6 addresses)
Related
Documentation
32
When you configure an interface in passive monitoring mode, the Packet Forwarding
Engine silently drops packets coming from that interface and destined to the router itself.
Passive monitoring mode also stops the Routing Engine from transmitting any packet
from that interface. Packets received from the monitored interface can be forwarded to
monitoring interfaces. If you include the passive-monitor-mode statement in the
configuration:
Gigabit and Fast Ethernet interfaces can support both per-port passive monitoring and
per-VLAN passive monitoring. The destination MAC filter on the receive port of the
Ethernet interfaces is disabled.
Ethernet interfaces do not support the stacked-vlan-tagging statement for both IPv4
and IPv6 packets in passive monitor mode.
For IPv4 monitoring services interfaces, enable packet flow monitoring by including the
family statement at the [edit interfaces mo-fpc/pic/port unit logical-unit-number] hierarchy
level, specifying the inet option:
[edit interfaces mo-fpc/pic/port unit logical-unit-number]
family inet;
For conformity with the cflowd record structure, you must include the
receive-options-packets and receive-ttl-exceeded statements at the [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;
IPv6 passive monitoring is not supported on monitoring services PICs. A user must
configure port mirroring to forward the packets from the passive monitored ports to other
interfaces.
For information on FPCs and PICs that support IPv6 passive monitoring on the T640,
T1600, and T4000 routers, see Passive Monitoring on Ethernet Interfaces Overview on
page 31. Interfaces configured on these FPCs and PICs support IPv6 passive monitoring.
To configure port mirroring, include the port-mirroring statement at the [edit
forwarding-options] hierarchy level.
For the monitoring services interface, you can configure multiservice physical interface
properties. For more information, see Configuring Multiservice Physical Interface Properties
and the Junos OS Services Interfaces Library for Routing Devices.
33
Related
Documentation
34
CHAPTER 5
You can use both client and server certificates in all types of authentication except
EAP-MD5.
NOTE: On the MX Series router, 802.1x can be enabled on bridged ports only
and not on routed ports.
35
Dynamic changes to a user session are supported to allow the router administrator to
terminate an already authenticated session by using the RADIUS disconnect message
defined in RFC 3576.
Related
Documentation
Force authorizedAllows network access to all users of the port without requiring
them to be authenticated. This is equivalent to not having any authentication enabled
on the port.
Force unauthorizedDenies network access to all users of the port. This is equivalent
to disabling the port.
In Junos OS, the default mode is automatic. The force authorized and force
unauthorized admin modes are not supported. You can achieve the functionality of
force authorized mode by disabling dot1x on the required port. You can achieve the
functionality of force unauthorized mode by disabling the port itself.
Related
Documentation
36
Related
Documentation
Related
Documentation
37
Related
Documentation
38
CHAPTER 6
Configuring Server Fail Fallback on MX Series Routers in Enhanced LAN Mode on page 57
Authentication Process Flow for MX Series Routers in Enhanced LAN Mode on page 60
39
40
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
MPC4E with two 100-Gigabit Ethernet ports and eight 10-Gigabit Ethernet ports
MPC1E with forty 1-Gigabit Ethernet ports or twenty 1-Gigabit Ethernet ports
You must reboot the router when you configure or delete the enhanced LAN mode on
the router. Configuring the network-services lan option implies that the system is running
in the enhanced IP mode. When you configure a device to function in MX-LAN mode, only
the supported configuration statements and operational show commands that are
available for enabling or viewing in this mode are displayed in the CLI interface. If your
system contains parameters that are not supported in MX-LAN mode in a configuration
file, you cannot commit those unsupported attributes. You must remove the settings
that are not supported and then commit the configuration. After the successful CLI
commit, a system reboot is required for the attributes to be come effective. Similarly, if
you remove the network-services lan statement, the system does not run in MX-LAN
mode. Therefore, all of the settings that are supported outside of the MX-LAN mode are
displayed and are available for definition in the CLI interface. If your configuration file
contains settings that are supported only in MX-LAN mode, you must remove those
attributes before you commit the configuration. After the successful CLI commit, a system
reboot will be required for the CLI settings to take effect. The Layer 2 Next-Generation
CLI configuration settings are supported in MX-LAN mode. As a result, the typical MX
Series-format of CLI configurations might differ in MX-LAN mode.
This functionality is supported on an MX Series Virtual Chassis combination that functions
in enhanced LAN mode (by entering the network-services lan statement at the [edit
chassis] hierarchy level). Port-based network access control is supported on MX240,
MX480, and MX960 routers with MPCs in both the MX-LAN mode and the non-MX-LAN
mode (with other supported network services modes on MPCs on these routers). To
configure the IEEE 802.1x port-based network access control (PNAC) protocol on Ethernet
interfaces, you must configure the authenticator statement at the [edit protocols
authentication-access- control] hierarchy level. You can also configure captive portal
authentication on a router so that users connected to the switch are authenticated before
being allowed to access the network. You can also configure Junos Pulse Access Control
Service as the access policy to authenticate and authorize users connected to the switch
for admission to the network and for access to protected network resources by using the
uac-policy statement.
41
802.1X authentication works by using an Authenticator Port Access Entity (the switch) to
block all traffic to and from a supplicant (end device) at the port until the supplicant's
credentials are presented and matched on the Authentication server (a RADIUS server).
When authenticated, the switch stops blocking traffic and opens the port to the supplicant.
The end device is authenticated in either single mode, single-secure mode, or multiple
mode:
singleAuthenticates only the first end device. All other end devices that connect later
to the port are allowed full access without any further authentication. They effectively
piggyback on the end devices authentication.
single-secureAllows only one end device to connect to the port. No other end device
multipleAllows multiple end devices to connect to the port. Each end device will be
authenticated individually.
Network access can be further defined using VLANs and firewall filters, which both act
as filters to separate and match groups of end devices to the areas of the LAN they
require. For example, you can configure VLANs to handle different categories of
authentication failures depending upon:
Whether or not MAC RADIUS authentication has been configured on the switch
interfaces to which the hosts are connected.
42
Guest VLANProvides limited access to a LAN, typically just to the Internet, for
nonresponsive end devices that are not 802.1X-enabled when MAC RADIUS
authentication has not been configured on the switch interfaces to which the hosts
are connected . Also, a guest VLAN can be used to provide limited access to a LAN for
guest users. Typically, the guest VLAN provides access just to the Internet and to other
guests end devices.
Server-reject VLANProvides limited access to a LAN, typically just to the Internet, for
responsive end devices that are 802.1X-enabled but that have sent the wrong
credentials.
Server-fail VLANProvides limited access to a LAN, typically just to the Internet, for
802.1X end devices during a RADIUS server timeout.
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
43
The router also uses these protocols to ensure that voice traffic gets tagged and prioritized
with the correct values at the source itself. For example, 802.1p CoS and 802.1Q tag
information can be sent to the IP telephone.
EX Series routeres support the following basic TLVs:
NOTE: The Chassis ID TLV has a subtype for Network Address Family. LLDP
frames are validated only if this subtype has a value of 1 (IPv4) or 2 (IPv6).
For any other value, the transmitting device is detected by LLDP as a
neighbor and displayed in the output of the "show lldp neighbors"
command, but is not assigned to the VLAN.
Port IdentifierThe port identification for the specified port in the local system.
Port DescriptionTextual description of the interface or the logical unit. The description
for the logical unit is used, if available; otherwise, the Port Description TLV will contain
the description configured on the physical interface. For example, LAG member
interfaces do not contain a logical unit, so only the description configured on the physical
interface can be used.
System NameThe user-configured name of the local system. The system name can
and current image running on the system. This information is not configurable, but
taken from the software.
that system supports; for example, bridge or router. This information is not configurable,
but based on the model of the product.
Power via MDIA TLV that advertises MDI power support, PSE power pair, and power
class information.
MAC/PHY Configuration StatusA TLV that advertises information about the physical
interface, such as autonegotiation status and support and MAU type. The information
is not configurable, but based on the physical interface structure.
NOTE: The MAC/PHY Configuration Status TLV has a subtype for the PMD
Auto-Negotiation Advertised Capability field. This field will contain a value
of other or unknown if the LLDP packet was transmitted from a 10-gigabit
SFP+ port.
Link AggregationA TLV that advertises if the port is aggregated and its aggregated
port ID.
44
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
Maximum Frame SizeA TLV that advertises the Maximum Transmission Unit (MTU)
Port VlanA TLV that advertises the VLAN name configured on the interface.
LLDP MED CapabilitiesA TLV that advertises the primary function of the port. The
0 Capabilities
1 Network Policy
2 Location Identification
4 Inventory
515 Reserved
1 Class 1 Device.
2 Class 2 Device.
3 Class 3 Device.
5255 Reserved.
Network PolicyA TLV that advertises the port VLAN configuration and associated
Layer 2 and Layer 3 attributes. Attributes include the policy identifier, application types,
such as voice or streaming video, 802.1Q VLAN tagging, and 802.1p priority bits and
Diffserv code points.
Endpoint Location A TLV that advertises the physical location of the endpoint.
Extended Power via MDI A TLV that advertises the power type, power source, power
priority, and power value of the port. It is the responsibility of the PSE device (network
connectivity device) to advertise the power priority on a port.
45
A RADIUS accounting server listens for User Datagram Protocol (UDP) packets on a
specific port. For example, on FreeRADIUS, the default port is 1813.
stop-accounting records. The records are in a file. On FreeRADIUS, the file name is
the server's address; for example, 122.69.1.250.
4. The accounting server sends an accounting-response packet back to the switch
46
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
If an 802.1X-compatible IP telephone does not have an 802.1X host but has another
802.1X-compatible device connected to its data port, you can connect the phone to an
interface in single-supplicant mode. In single-supplicant mode, the 802.1X process
authenticates only the first supplicant. All other supplicants who connect later to the
interface are allowed full access without any further authentication. They effectively
47
If an IP telephone does not support 802.1X, you can configure VoIP to bypass 802.1X and
LLDP-MED and have the packets forwarded to a VoIP VLAN,
Understanding Guest VLANs for 802.1X on MX Series Routers in Enhanced LAN Mode
Guest VLANs can be configured on switches that are using 802.1X authentication to
provide limited accesstypically only to the Internetfor:
Corporate guests
Nonresponsive end devices when MAC RADIUS authentication has not been configured
on the switch interfaces to which the hosts are connected
A guest VLAN is not used for supplicants sending incorrect credentials. Those supplicants
are directed to the server-reject VLAN instead.
For end devices that are not 802.1X-enabled, a guest VLAN can allow limited access to
a server from which the non-802.1X-enabled end device can download the supplicant
software and attempt authentication again.
A guest VLAN is not used when MAC RADIUS authentication has been configured on the
switch interfaces to which the hosts are connected. Some end devices, such as a printer,
48
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
cannot be enabled for 802.1X. The hosts for such devices should be connected to switch
interfaces that are configured for MAC RADIUS authentication.
Permit authentication, allowing traffic to flow from the end device through the interface
as if the end device were successfully authenticated by the RADIUS server.
Deny authentication, preventing traffic from flowing from the end device through the
interface. This is the default.
Move the end device to a specified VLAN. (The VLAN must already exist on the router.)
Sustain authenticated end devices that already have LAN access and deny
unauthenticated end devices. If the RADIUS servers time out during reauthentication,
previously authenticated end devices are reauthenticated and new users are denied
LAN access.
49
Server fail fallback is triggered most often during reauthentication when the already
configured and in-use RADIUS server becomes inaccessible. However, server fail fallback
can also be triggered by an end devices first attempt at authentication through the
RADIUS server.
Server fail fallback allows you to specify that an end device be moved to a specified
VLAN if the router receives a RADIUS access-reject message. The configured VLAN name
overrides any attributes sent by the server.
Specify the accounting servers to which the switch will forward accounting statistics:
[edit access ]
user@router# set profile profile1 radius accounting-serveraccounting-server [122.69.1.250
122.69.1.252]
server:
[edit access ]
user@router# set profile profile1 accounting accounting-stop-on-access-deny
user@router# set profile profile1 accounting accounting-stop-on-failure
6. Display accounting statistics collected on the router:
user@router> show network-access aaa statistics accounting
Accounting module statistics
Requests received: 1
Accounting Response failures: 0
Accounting Response Success: 1
Requests timedout: 0
7. Open an accounting log on the RADIUS accounting server using the server's address,
50
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
detail-20071214
Related
Documentation
51
NOTE:
You can also specify an 802.1X exclusion list to specify supplicants can
that can bypass authentication and be automatically connected to the
LAN.
Before you begin, specify the RADIUS server or servers to be used as the authentication
server.
To configure 802.1X on an interface:
1.
52
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
initial failure. The port remains in a wait state during the quiet period after the
authentication attempt.
[edit protocols authentication-access-control]
user@switch# set interface ge-0/0/5 retries 1
NOTE: This setting specifies the number of tries before the switch puts the
interface in a HELD state.
Related
Documentation
53
user@router# set interface ge-0/0/2.0 location civic-based ca-type 6 ca-value Mount Aukum
Road
user@router# set interface ge-0/0/2.0 location civic-based ca-type 19 ca-value 6450
user@router# set interface ge-0/0/2.0 location civic-based ca-type 21 ca-value Holiday
Market
Related
Documentation
54
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
To specify the frequency at which LLDP advertisements are sent (in seconds):
[edit protocols lldp]
user@router# set advertisement-interval seconds
To specify the number of seconds that LLDP information is held before it is discarded
(the multiplier value is used in combination with the advertisement-interval value):
[edit protocols lldp]
user@router# set hold-multiplier seconds
To specify the number of seconds the device delays before sending advertisements
to neighbors after a change is made in a TLV (type, length, or value) element in LLDP
or in the state of the local system, such as a change in hostname or management
address, set the transmit delay. The transmit delay is enabled by default on switches
to reduce the delay in notifying neighbors of a change in the local system. The default
value is 2 seconds (if the advertisement-interval value is set to 8 seconds or more) or
1 second (if the advertisement-interval value is set to less than 8 seconds).
[edit protocols lldp]
user@router# set transmit-delay seconds
For example:
[edit protocols lldp]
user@router# set transmit-delay 2
55
To specify the frequency at which LLDP database changes are sent (in seconds):
[edit protocols lldp]
user@router# set lldp-configuration-notification-interval seconds
For example:
[edit protocols lldp]
user@router# set lldp-configuration-notification-interval 600
To configure the time interval for SNMP trap notifications to wait for topology changes
(in seconds):
[edit protocols lldp]
user@router# set ptopo-configuration-trap-interval seconds
For example:
[edit protocols lldp]
user@router# set ptopo-configuration-trap-interval 600
For example:
[edit protocols lldp]
user@router# set ptopo-configuration-maximum-hold-time 2147483647
NOTE: Ensure that the interface with the configured management address
has LLDP enabled using the set protocols lldp interface command. If you
configure a customized management address for LLDP on an interface that
has LLDP disabled, the show lldp local-information command output will not
display the correct interface information.
56
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
57
Configure an interface to allow traffic to flow from a supplicant to the LAN if a RADIUS
server timeout occurs (as if the end device had been successfully authenticated by a
RADIUS server):
[edit protocols authentication-access-control]
user@router# set interface ge-0/0/1 dot1x server-fail permit
Configure an interface to prevent traffic flow from an end device to the LAN (as if the
end device had failed authentication and had been rejected by the RADIUS server):
[edit protocols authentication-access-control]
user@router# set interface ge-0/0/1 dot1x server-fail deny
58
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
If there are clients that are not HTTP-enabled connected to the captive portal interface,
you can allow them to bypass captive portal authentication by adding their MAC address
to an authentication whitelist. (If the MAC address has already been learned on the
interface, you must clear it using the clear captive-portal interface interface-name) before
adding it to the whitelist.)
When the user is authenticated by the RADIUS server, any per-user policies (attributes)
associated with that user are also sent to the switch.
The captive portal interface must be configured for family ethernet-switching and set
to port mode access. The VLAN must be configured with a routed VLAN interface (RVI).
The DHCP gateway IP address for the switch must be configured as the IP address of
the routed VLAN interface.
Captive portal does not support dynamic assignment of VLANs downloaded from the
RADIUS server.
If the user is idle for more than about 5 minutes and there is no traffic passed, the user
is required to log back in to the captive portal.
59
timestamp for that network node in the Ethernet switching table. A timer on the switch
periodically checks the timestamp and if its value exceeds the user-configured
mac-table-aging-time value, the switch removes the MAC address from the Ethernet
switching table. When a MAC address ages out of the Ethernet switching table, the entry
for that MAC address is also removed from the authentication database, with the result
that the session ends.
You can control variables affecting timeout of authentication sessions in the following
ways:
Set the authentication session timeout on all interfaces or on selected interfaces using
the reauthentication statement.
Disassociate the authentication session table from the Ethernet switching table using
the no-mac-table-binding statement. This setting prevents the termination of the
authentication session when the associated MAC address ages out of the Ethernet
switching table.
60
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
61
Define the IP address of the RADIUS server, the RADIUS server authentication port
number, and the secret password. You can define more than one RADIUS server. The
secret password on the router must match the secret password on the server:
[edit access]
user@router# set radius-server 10.0.0.100 port 1812 secret abc
NOTE: Specifying the authentication port is optional, and port 1812 is the
default. However, we recommend that you configure it in order to avoid
confusion as some RADIUS servers might refer to an older default.
2. (Optional) Specify the IP address by which the router is identified by the RADIUS
server. If you do not specify this, the RADIUS server uses the address of the interface
sending the RADIUS request. We recommend that you specify this IP address because
if the request gets diverted on an alternate route to the RADIUS server, the interface
relaying the request might not be an interface on the router.
[edit access]
user@router# set radius-server source-address 10.93.14.100
3. Configure the authentication order, making radius the first method of authentication:
[edit access]
user@router# set profile profile1 authentication-order radius
4. Create a profile and specify the list of RADIUS servers to be associated with the profile.
For example, you might choose to group your RADIUS servers geographically by city.
This feature enables easy modification whenever you want to change to a different
sent of authentication servers.
[edit access profile]
user@router# set atlanta radius authentication-server 10.0.0.100 10.2.14.200
5. Specify the group of servers to be used for 802.1X or MAC RADIUS authentication by
62
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
6. Configure the IP address of the MX Series router in the list of clients on the RADIUS
server. For specifics on configuring the RADIUS server, consult the documentation for
your server.
NOTE: This example uses Junos OS for MX240, MX480, and MX960 routers
with support for the Enhanced LAN mode configuration style. If your router
does not run MX-LAN mode, you cannot configure port-based authentication
settings in the same manner as described in this section. If you remove the
network-services lan statement at the [edit chassis] hierarchy level, the
system does not run in MX-LAN mode. Therefore, all of the settings that are
supported outside of the MX-LAN mode are displayed and are available for
definition in the CLI interface. In such a scenario, you must use the statements
at the [edit protocols dot1x] hierarchy level to configure 802.1x and MAC
RADIUS authentication, and the options at the [edit services captive-portal]
hierarchy level to configure captive portal authentication. In MX-LAN mode,
you can configure all the port-based network access control methodologies
using the statements at the [edit protocols authentication-access-control]
hierarchy level.
Configured basic access between the MX Series router and the RADIUS server.
Associate the security certificate with the Web server and enable HTTPS on the router:
63
[edit]
user@router# set system services web-management https local-certificate my-signed-cert
NOTE: You can enable HTTP instead of HTTPS, but we recommend HTTPS
for security purposes.
NOTE: If the client is already attached to the router, you must clear its MAC
address from the captive portal authentication by using the clear captive-portal
mac-address session-mac-addr command after adding its MAC address to the
whitelist. Otherwise the new entry for the MAC address will not be added to
the Ethernet switching table and the authentication bypass will not be
allowed.
64
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
Table 3 on page 65 summarizes the configurable elements of a captive portal login page.
CLI Statement
Description
Footer background
color
footer-bgcolor hex-color
The HTML hexadecimal code for the background color of the captive portal
login page footer.
65
CLI Statement
Description
Footer message
footer-message
text-string
Text displayed in the footer of the captive portal login page. You can include
copyright information, links, and additional information such as help
instructions, legal notices, or a privacy policy
The default text shown in the footer is Copyright @2010, Juniper Networks
Inc.
Form header
background color
form-header-bgcolor
hex-color
The HTML hexadecimal code for the background color of the header bar
across the top of the form area of the captive portal login page.
Form header
message
form-header-message
text-string
Text displayed in the header of the captive portal login page. The default
text is Captive Portal User Authentication
Color of the text in the form header. The default color is black.
form-reset-label
label-name
Using the Reset button, the user can clear the username and password fields
on the form.
form-submit-label
label-name
Using the Login button, the user can submit the login information.
Header background
color
header-bgcolor hex-color
The HTML hexadecimal code for the background color of the captive portal
login page header.
Header logo
header-logo filename
Filename of the file containing the image of the logo that you want to appear
in the header of the captive portal login page. The image file can be in GIF,
JPEG, or PNG format
color
You can upload a logo image file to the switch. Copy the logo to the /var/tmp
directory on the switch (during commit, the files are saved to persistent
locations).
If you do not specify a logo image, the Juniper Networks logo is displayed.
Header message
header-message
text-string
Text displayed in the page header. The default text is User Authentication.
header-text- colorcolor
Post-authentication
URL
post-authentication-url
url
2. Configure the custom options to specify the background colors and text displayed in
66
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
[edit protocols]
user@router# set captive-portal-custom-options header-bgcolor #006600
set captive-portal-custom-options header-message Welcome to Our Network
set captive-portal-custom-options banner-message Please enter your username and
password.The banner displays the message XXXXXXX by default. The user can modify this
message.
set custom-options footer-message Copyright 2010, Our Network
NOTE: For the custom options that you do not specify, the default value is
used.
67
Related
Documentation
68
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
NOTE: You can also allow non-802.1X-enabled devices to access the LAN
by configuring their MAC address for static MAC bypass of authentication.
You can configure MAC RADIUS authentication on an interface that also allows 802.1X
authentication, or you can configure either authentication method alone.
If both MAC RADIUS and 802.1X authentication are enabled on the interface, the router
first sends the host three EAPOL requests to the host. If there is no response from the
host, the router sends the hosts MAC address to the RADIUS server to check whether it
is a permitted MAC address. If the MAC address is configured as permitted on the RADIUS
server, the RADIUS server sends a message to the router that the MAC address is a
permitted address, and the router opens LAN access to the nonresponsive host on the
interface to which it is connected.
If MAC RADIUS authentication is configured on the interface but 802.1X authentication
is not (by using the mac-radius restrict option), the router attempts to authenticate the
MAC address with the RADIUS server without delaying by attempting 802.1X
authentication first.
Before you configure MAC RADIUS authentication, be sure you have:
Configured basic access between the MX Series router and the RADIUS server.
Configured MX240, MX480, and MX960 routers to function in enhanced LAN mode
by entering the network-services lan statement at the [edit chassis] hierarchy level.
69
On the router, configure the interfaces to which the nonresponsive hosts are attached
for MAC RADIUS authentication, and add the restrict qualifier for interface ge-0/0/20
to have it use only MAC RADIUS authentication:
[edit]
user@router# set protocols authentication-access-control interface ge-0/0/19 dot1x
mac-radius
user@router# set protocols authentication-access-control interface ge-0/0/20 dot1x
mac-radius restrict
On a RADIUS authentication server, create user profiles for each nonresponsive host
using the MAC address (without colons) of the nonresponsive host as the username
and password (here, the MAC addresses are 00:04:0f:fd:ac:fe and 00:04:ae:cd:23:5f):
[root@freeradius]#
edit /etc/raddb
vi users
00040ffdacfe Auth-type:=Local, User-Password = "00040ffdacfe"
0004aecd235f Auth-type:=Local, User-Password = "0004aecd235f"
Related
Documentation
Requirements on page 70
Configuration on page 72
Verification on page 73
Requirements
This example uses the following hardware and software components:
70
Junos OS Release 14.2 or later for MX240, MX480, or MX960 routers running in
enhanced LAN mode.
An MX Series router acting as an authenticator port access entity (PAE). The ports on
the authenticator PAE form a control gate that blocks all traffic to and from supplicants
until they are authenticated.
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
Before you connect the server to the router, be sure you have:
Settings
Router hardware
VLAN name
sales
Connections to printers
RADIUS server
The printer with the MAC address 00040ffdacfe is connected to access interface
ge-0/0/19. A second printer with the MAC address 0004aecd235f is connected to access
interface ge-0/0/20. In this example, both interfaces are configured for MAC RADIUS
authentication on the router, and the MAC addresses (without colons) of both printers
are configured on the RADIUS server. Interface ge-0/0/20 is configured to eliminate the
normal delay while the router attempts 802.1X authentication; MAC RADIUS
authentication is enabled and 802.1X authentication is disabled using the mac radius
restrict option.
71
Configuration
CLI Quick
Configuration
To quickly configure MAC RADIUS authentication, copy the following commands and
paste them into the router terminal window:
[edit]
set protocols authentication-access-control interface ge-0/0/19 dot1x mac-radius
set protocols authentication-access-control authenticator interface ge-0/0/20 dot1x mac-radius
restrict
NOTE: You must also configure the two MAC addresses as usernames and
passwords on the RADIUS server, as is done in step 2 of the Step-by-Step
Procedure.
Step-by-Step
Procedure
Configure MAC RADIUS authentication on the router and on the RADIUS server:
1.
On the router, configure the interfaces to which the printers are attached for MAC
RADIUS authentication, and configure the restrict option on interface ge-0/0/20,
so that only MAC RADIUS authentication is used:
[edit]
user@router# set protocols authentication-access-control interface ge-0/0/19 dot1x
mac-radius
user@router# set protocols authentication-access-control authenticator interface
ge-0/0/20 dot1x mac-radius restrict
2.
Results
72
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
}
}
}
Verification
Verify that the supplicants are authenticated:
After supplicants are configured for MAC RADIUS authentication on the router and on
the RADIUS server, verify that they are authenticated and display the method of
authentication:
73
Action
Meaning
74
The sample output from the show dot1x interface detail command displays the MAC
address of the connected end device in the Supplicant field. On interface ge-0/0/19, the
MAC address is 00:04:0f:fd:ac:fe, which is the MAC address of the first printer configured
for MAC RADIUS authentication. The Authentication method field displays the
authentication method as MAC Radius. On interface ge-0/0/20, the MAC address is
00:04:ae:cd:23:5f, which is the MAC address of the second printer configured for MAC
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
Requirements on page 75
Configuration on page 75
Verification on page 78
Troubleshooting on page 78
Requirements
This example uses the following hardware and software components:
Configured basic access between the MX Series router and the RADIUS server.
Configuration
To configure captive portal on your router:
75
CLI Quick
Configuration
To quickly configure captive portal on the router after completing the tasks in the
Requirements section, copy the following commands and paste them into the router
terminal window:
[edit]
set system services web-management http
set system services web-management https local-certificate my-signed-cert
set protocols captive-portal-custom-options secure-authentication https
set protocols authentication-access-control interface ge-0/0/10.0 supplicant multiple
set protocols authentication-access-control static 00:10:12:e0:28:22
set protocols captive-portal-custom-options post-authentication-url
http://www.my-home-page.com
Step-by-Step
Procedure
2.
To create a secure channel for Web access to the router, configure captive portal
for HTTPS:
a. Associate the security certificate with the Web server and enable HTTPS access
on the router:
[edit]
user@router# set system services web-management https local-certificate
my-signed-cert
b. Configure captive portal to use HTTPS:
[edit]
user@router# set protocols captive-portal-custom-options secure-authentication
https
3.
4.
NOTE: If the client is already attached to the router, you must clear its
MAC address from the captive portal authentication by using the clear
captive-portal mac-address mac-address command after adding its MAC
address to the whitelist. Otherwise the new entry for the MAC address
will not be added to the Ethernet routering table and authentication
bypass will not be allowed.
[edit]
user@router# set protocols authentication-access-control static 00:10:12:e0:28:22
76
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
5.
(Optional) To redirect clients to a specified page rather than the page they originally
requested, configure the post-authentication URL:
[edit services captive-portal]
user@router# set protocols captive-portal-custom-options post-authentication-url
http://www.my-home-page.com
Results
77
Verification
To confirm that captive portal is configured and working properly, perform these tasks:
Action
Use the operational mode command show captive-portal interface interface-name detail:
user@router> show captive-portal interface ge-0/0/10.0 detail
ge-0/0/10.0
Supplicant mode: Multiple
Number of retries: 3
Quiet period: 60 seconds
Configured CP session timeout: 3600 seconds
Server timeout: 15 seconds
Meaning
The output confirms that captive portal is configured on interface ge-0/0/10 with the
default settings for number of retries, quiet period, CP session timeout, and server timeout.
Troubleshooting
To troubleshoot captive portal, perform these tasks:
78
Problem
The router does not return the captive portal login page when a user connected to a
captive portal interface on the router requests a Web page.
Solution
You can examine the ARP, DHCP, HTTPS, and DNS countersif one or more of these
counters are not incrementing, this provides an indication of where the problem lies. For
example, if the client cannot get an IP address, check the router interface to determine
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
whether the DHCP counter is incrementingif the counter increments, the DHCP packet
was received by the router.
user@router> show captive-portal firewall ge-0/0/10.0
ge-0/0/10.0
Filter name: dot1x_ge-0/0/10
Counters:
Name
Bytes
Packets
dot1x_ge-0/0/10_CP_arp
7616
119
dot1x_ge-0/0/10_CP_dhcp
0
0
dot1x_ge-0/0/10_CP_http
0
0
dot1x_ge-0/0/10_CP_https
0
0
dot1x_ge-0/0/10_CP_t_dns
0
0
dot1x_ge-0/0/10_CP_u_dns
0
0
Requirements on page 79
Configuration on page 80
Verification on page 81
Requirements
This example uses the following hardware and software components:
Junos OS Release 14.2 or later for MX240, MX480, or MX960 routers running in
enhanced LAN mode.
One router acting as an authenticator port access entity (PAE). The ports on the
authenticator PAE form a control gate that blocks all traffic to and from supplicants
until they are authenticated.
One RADIUS authentication server that supports 802.1X. The authentication server
acts as the backend database and contains credential information for hosts
(supplicants) that have permission to connect to the network.
Before you connect the server to the router, be sure you have:
79
Settings
Router hardware
MX Series router
VLAN name
default
In this example, connect the RADIUS server to access port ge-0/0/10 on the MX Series
router. The switch acts as the authenticator and forwards credentials from the supplicant
to the user database on the RADIUS server. You must configure connectivity between
the MX Series router and the RADIUS server by specifying the address of the server and
configuring the secret password. This information is configured in an access profile on
the switch.
Configuration
CLI Quick
Configuration
To quickly connect the RADIUS server to the switch, copy the following commands and
paste them into the switch terminal window:
[edit]
set access radius-server 10.0.0.100 secret juniper
set access radius-server 10.0.0.200 secret juniper
set access profile profile1 authentication-order radius
set access profile profile1 radius authentication-server [10.0.0.100 10.0.0.200]
Step-by-Step
Procedure
Define the address of the servers, and configure the secret password. The secret
password on the switch must match the secret password on the server:
[edit]
user@switch# set access radius-server 10.0.0.100 secret juniper
user@switch# set access radius-server 10.0.0.200 secret juniper
2.
Configure the authentication order, making radius the first method of authentication:
[edit]
user@switch# set access profile profile1 authentication-order radius
3.
80
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
[edit]
user@switch# set access profile profile1 radius authentication-server [10.0.0.100
10.0.0.200]
Results
Verification
To confirm that the configuration is working properly, perform these tasks:
Verify That the Switch and RADIUS Server are Properly Connected on page 81
Verify That the Switch and RADIUS Server are Properly Connected
Purpose
Action
Verify that the RADIUS server is connected to the switch on the specified port.
Ping the RADIUS server to verify the connection between the switch and the server:
user@switch> ping 10.0.0.100
PING 10.0.0.100 (10.0.0.100): 56 data bytes
64 bytes from 10.93.15.218: icmp_seq=0 ttl=64 time=9.734 ms
64 bytes from 10.93.15.218: icmp_seq=1 ttl=64 time=0.228 ms
Meaning
ICMP echo request packets are sent from the switch to the target server at 10.0.0.100 to
test whether it is reachable across the IP network. ICMP echo responses are being returned
from the server, verifying that the switch and the server are connected.
81
This example describes how to create a guest VLAN and configure 802.1X authentication
for it.
Requirements on page 82
Verification on page 83
Requirements
This example uses the following hardware and software components:
Junos OS Release 14.2 or later for MX240, MX480, or MX960 routers running in
enhanced LAN mode.
One router acting as an authenticator port access entity (PAE). The ports on the
authenticator PAE form a control gate that blocks all traffic to and from supplicants
until they are authenticated.
One RADIUS authentication server that supports 802.1X. The authentication server
acts as the backend database and contains credential information for hosts
(supplicants) that have permission to connect to the network.
Before you connect the server to the router, be sure you have:
Settings
Router hardware
MX Series router
VLAN name
default
82
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
In this example, access interface ge-0/0/1 provides LAN connectivity in the conference
room. Configure this access interface to provide LAN connectivity to visitors in the
conference room who are not authenticated by the corporate VLAN.
To quickly configure a guest VLAN, with 802.1X authentication, copy the following
commands and paste them into the switch terminal window:
[edit]
set vlans guest-vlan vlan-id 300
set protocols authentication-access-control interface all dot1x guest-vlan guest-vlan
Step-by-Step
Procedure
2.
Results
Verification
To confirm that the configuration is working properly, perform these tasks:
83
Action
Verify that the guest VLAN is created and that an interface has failed authentication and
been moved to the guest VLAN.
Bridging Domain
Type
Primary Table
vs1
Active
dynamic
bridge
guest
bridge
guest-vlan
bridge
vlan_dyn
bridge
bridge.0
vs1
bridge.0
vs1
bridge.0
vs1
bridge.0
Meaning
The output from the show bridge domain command shows guest-vlan as the name of
the VLAN and the VLAN ID as 300.
The output from the show dot1x interface ge-0/0/1.0 detail command displays the Guest
VLAN membership field, indicating that a supplicant at this interface failed 802.1X
authentication and was passed through to the guest-vlan.
84
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
Requirements on page 85
Configuration on page 86
Verification on page 87
Requirements
This example uses the following hardware and software components:
Junos OS Release 14.2 or later for MX240, MX480, or MX960 routers running in
enhanced LAN mode.
One router acting as an authenticator port access entity (PAE). The ports on the
authenticator PAE form a control gate that blocks all traffic to and from supplicants
until they are authenticated.
Before you connect the server to the router, be sure you have:
85
The interfaces shown in Table 7 on page 86 will be configured for static MAC
authentication.
Settings
Router hardware
MX Series router
VLAN name
default
The printer with the MAC address 00:04:0f:fd:ac:fe is connected to access interface
ge-0/0/19. A second printer with the MAC address 00:04:ae:cd:23:5f is connected to
access interface ge-0/0/20. Both printers will be added to the static list and bypass
802.1X authentication.
Configuration
CLI Quick
Configuration
To quickly configure static MAC authentication, copy the following commands and paste
them into the router terminal window:
[edit]
set protocols authentication-access-control static [00:04:0f:fd:ac:fe 00:04:ae:cd:23:5f]
set protocols authentication-access-control interface all supplicant multiple
set protocols authentication-access-control authenticaton-profile-name profile1
Step-by-Step
Procedure
2.
3.
Configure the authentication profile name (access profile name) to use for
authentication:
[edit protocols]
user@router# set authentication-access-control authentication-profile-name profile1
Results
86
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
ge-0/0/19 {
unit 0 {
family bridge {
vlan-id 10;
}
}
}
ge-0/0/20 {
unit 0 {
family bridge {
vlan-id 10;
}
}
}
}
protocols {
authentication-access-control {
authentication-profile-name profile1;
static [00:04:0f:fd:ac:fe 00:04:ae:cd:23:5f];
interface {
all {
supplicant multiple;
}
}
}
}
Verification
To confirm that the configuration is working properly, perform these tasks:
Action
Verify that the MAC address for both printers is configured and associated with the correct
interfaces.
Meaning
VLAN-Assignment
default
default
Interface
ge-0/0/19.0
ge-0/0/20.0
The output field MAC address shows the MAC addresses of the two printers.
The output field Interface shows that the MAC address 00:04:0f:fd:ac:fe can connect to
the LAN through interface ge-0/0/19.0 and that the MAC address 00:04:ae:cd:23:5f can
connect to the LAN through interface ge-0/0/20.0.
87
Requirements on page 88
Configuration on page 90
Verification on page 92
Requirements
This example uses the following hardware and software components:
One RADIUS authentication server. The authentication server acts as the backend
database and contains credential information for hosts (supplicants) that have
permission to connect to the network.
Before you apply firewall filters to an interface for use with multiple supplicants, be sure
you have:
Configured 802.1X authentication on the router, with the authentication mode for
interface ge-0/0/2 set to multiple.
88
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
When a new user (or a nonresponsive host) is authenticated on an interface, the system
adds a term to the firewall filter associated with the interface, and the term (policy) for
each user is associated with the MAC address of the user. The term for each user is based
on the user-specific filters set on the RADIUS server and the filters configured on the
interface. For example, as shown in Figure 5 on page 89, when User1 is authenticated by
the MX Series router, the system creates the firewall filter dynamic-filter-example. When
User2 is authenticated, another term is added to the firewall filter, and so on.
Figure 5: Conceptual Model: Dynamic Filter Updated for Each New User
This is a conceptual model of the internal processyou cannot access or view the dynamic
filter.
NOTE: If the firewall filter on the interface is modified after the user (or
nonresponsive host) is authenticated, the modifications are not reflected in
the dynamic filter unless the user is reauthenticated.
In this example, you configure a firewall filter to count the requests made by each endpoint
authenticated on interface ge-0/0/2 to the file server, which is located on subnet
192.0.2.16/28, and set policer definitions to rate limit the traffic. Figure 6 on page 90 shows
the network topology for this example.
89
Configuration
To configure firewall filters for multiple supplicants on 802.1X-enabled interfaces:
Step-by-Step
Procedure
2.
90
Chapter 6: Configuring IEEE 802.1x Port-Based Network Access Control in Enhanced LAN Mode
Configure a firewall filter to count packets from each user and a policer that limits
the traffic rate. As each new user is authenticated on the multiple supplicant
interface, this filter term will be included in the dynamically created term for the
user:
[edit firewall family bridge]
user@router# set filter filter1 term term1 from destination-address 192.0.2.16/28
user@router# set filter filter1 term term1 then count counter1
user@router# set filter filter1 term term2 then policer p1
Results
91
Verification
To confirm that the configuration is working properly, perform these tasks:
Verify that firewall filters are functioning on the interface with multiple supplicants.
1.
Check the results with one user authenticated on the interface. In this case, the user
is authenticated on ge-0/0/2:
user@router> show dot1x firewall
Filter: dot1x_ge-0/0/2
Counters
counter1_dot1x_ge-0/0/2_user1 100
2. When a second user, User2, is authenticated on the same interface, ge-0/0/2, you
can verify that the filter includes the results for both of the users authenticated on the
interface:
user@router> show dot1x firewall
Filter: dot1x-filter-ge-0/0/0
Counters
counter1_dot1x_ge-0/0/2_user1 100
counter1_dot1x_ge-0/0/2_user2 400
Meaning
92
The results displayed by the show dot1x firewall command output reflect the dynamic
filter created with the authentication of each new user. User1 accessed the file server
located at the specified destination address 100 times, while User2 accessed the same
file server 400 times.
CHAPTER 7
Example: Configuring MACsec over an MPLS CCC on MX Series Routers on page 111
93
94
parameters; all configuration is done in the connectivity association outside of the secure
channels.
95
96
must support MACsec and must be running software that allows it to enable a
MACsec-secured connection with the router.
The router:
must be an MX240, MX480, or MX960 router running Junos OS Release 15.1 or later,
and configured with enhanced LAN mode or non-enhanced LAN mode.
must be configured with a port-based service to connect the provider edge (PE) router
to a customer edge (CE) device or host (only the Ethernet CCC and Ethernet VPLS
encapsulation options are supported, and the Ethernet VLAN VPLS and Ethernet VLAN
CCC encapsulation options are not supported).
can be multiple hops from the router and the host device.
97
MACsec Limitations
All types of Spanning Tree Protocol frames cannot currently be encrypted using MACsec.
Related
Documentation
98
Configuring MACsec on the Router Using Dynamic Secure Association Key Security
Mode to Secure a Router-to-Host Link on page 104
Configuring MACsec Using Static Secure Association Key Security Mode to Secure a
Router-to-Router Link on page 108
99
Configuring MACsec Using Static Connectivity Association Key Security Mode (Recommended
for Enabling MACsec on Router-to-Router Links)
You can enable MACsec using static connectivity association key (CAK) security mode
or static secure association keys (SAK) security mode on a point-to-point Ethernet link
connecting switches. This procedure shows you how to configure MACsec using static
CAK security mode.
When you enable MACsec using static CAK security mode, a pre-shared key is exchanged
between the switches on each end of the point-to-point Ethernet link. The pre-shared
key includes a connectivity association name (CKN) and a connectivity association key
(CAK). The CKN and CAK are configured by the user in the connectivity association and
must match on both ends of the link to initially enable MACsec.
After the pre-shared keys are exchanged and verified, the MACsec Key Agreement (MKA)
protocol, which enables and maintains MACsec on the link, is enabled. The MKA is
responsible for selecting one of the two switches on the point-to-point link as the key
server. The key server then creates a randomized security key that is shared only with the
other device over the MACsec-secured link. The randomized security key enables and
maintains MACsec on the point-to-point link. The key server will continue to periodically
create and share a randomly-created security key over the point-to-point link for as long
as MACsec is enabled.
You enable MACsec using static CAK security mode by configuring a connectivity
association on both ends of the link. All configuration is done within the connectivity
association but outside of the secure channel. Two secure channelsone for inbound
traffic and one for outbound trafficare automatically created when using static CAK
security mode. The automatically-created secure channels do not have any
user-configurable parameters that cannot already be configured in the connectivity
association.
To configure MACsec using static CAK security mode to secure a router-to-router Ethernet
link:
100
1.
Create a connectivity association. You can skip this step if you are configuring an
existing connectivity association.
[edit security macsec]
user@host# set connectivity-association connectivity-association-name
After the pre-shared keys are successfully exchanged and verified by both ends of
the link, the MACsec Key Agreement (MKA) protocol is enabled and manages the
secure link. The MKA protocol then elects one of the two directly-connected switches
as the key server. The key server then shares a random security with the other device
over the MACsec-secure point-to-point link. The key server will continue to periodically
create and share a random security key with the other device over the MACsec-secured
point-to-point link as long as MACsec is enabled.
To configure a CKN of
37c9c2c45ddd012aa5bc8ef284aa23ff6729ee2e4acb66e91fe34ba2cd9fe311 and CAK
101
Specifies the key server priority used by the MKA protocol to select the key server. The
switch with the lower priority-number is selected as the key server.
The default priority-number is 16.
If the key-server-priority is identical on both sides of the point-to-point link, the MKA
protocol selects the interface with the lower MAC address as the key server. Therefore,
if this statement is not configured in the connectivity associations at each end of a
MACsec-secured point-to-point link, the interface with the lower MAC address
becomes the key server.
To change the key server priority to 0 to increase the likelihood that the current device
is selected as the key server when MACsec is enabled on the interface using
connectivity association ca1:
[edit security macsec connectivity-association ca1]
user@host# set mka key-server-priority 0
To change the key server priority to 255 to decrease the likelihood that the current
device is selected as the key server in connectivity association ca1:
[edit security macsec connectivity-association ca1]
user@host# set mka key-server-priority 255
5. (Optional) Set the MKA transmit interval:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set mka transmit-interval interval
The MKA transmit interval setting sets the frequency for how often the MKA protocol
data unit (PDU) is sent to the directly connected device to maintain MACsec
connectivity on the link. A lower interval increases bandwidth overhead on the link; a
higher interval optimizes MKA protocol communication.
The default interval is 2000ms. We recommend increasing the interval to 6000 ms
in high-traffic load environments. The transmit interval settings must be identical on
both ends of the link when MACsec using static CAK security mode is enabled.
For instance, if you wanted to increase the MKA transmit interval to 6000 milliseconds
when connectivity association ca1 is attached to an interface:
[edit security macsec connectivity-association ca1]
user@host# set mka transmit-interval 6000
102
Encryption is enabled for all traffic entering or leaving the interface when MACsec is
enabled using static CAK security mode, by default.
When encryption is disabled, traffic is forwarded across the Ethernet link in clear text.
You are able to view unencrypted data in the Ethernet frame traversing the link when
you are monitoring it. The MACsec header is still applied to the frame, however, and
all MACsec data integrity checks are run on both ends of the link to ensure the traffic
sent or received on the link has not been tampered with and does not represent a
security threat.
7. (Optional) Set an offset for all packets traversing the link:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set offset (0 | 30 | 50)
For instance, if you wanted to set the offset to 30 in the connectivity association
named ca1:
[edit security macsec connectivity-association ca1]
user@host# set offset 30
The default offset is 0. All traffic in the connectivity association is encrypted when
encryption is enabled and an offset is not set.
When the offset is set to 30, the IPv4 header and the TCP/UDP header are unencrypted
while encrypting the rest of the traffic. When the offset is set to 50, the IPv6 header
and the TCP/UDP header are unencrypted while encrypting the rest of the traffic.
You would typically forward traffic with the first 30 or 50 octets unencrypted if a
feature needed to see the data in the octets to perform a function, but you otherwise
prefer to encrypt the remaining data in the frames traversing the link. Load balancing
features, in particular, typically need to see the IP and TCP/UDP headers in the first
30 or 50 octets to properly load balance traffic.
8. (Optional) Enable replay protection.
[edit security macsec connectivity-association connectivity-association-name]
user@host# set replay-protect replay-window-size number-of-packets
103
the receiving link out of sequence, so replay protection helps ensure the replayed
packet is dropped instead of forwarded through the network.
Replay protection should not be enabled in cases where packets are expected to
arrive out of order.
You can require that all packets arrive in order by setting the replay window size to 0.
To enable replay protection with a window size of five on connectivity association ca1:
[edit security macsec connectivity-association ca1]
user@host# set replay-protect replay-window-size 5
9. (Optional) Exclude a protocol from MACsec:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set exclude-protocol protocol-name
For instance, if you did not want Link Level Discovery Protocol (LLDP) to be secured
using MACsec:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set exclude-protocol lldp
When this option is enabled, MACsec is disabled for all packets of the specified
protocolin this case, LLDPthat are sent or received on the link.
10. Assign the connectivity association to an interface:
[edit security macsec]
user@host# set interfaces interface-names connectivity-association
connectivity-association-name
MACsec using static CAK security mode is not enabled until a connectivity association
on the opposite end of the link is also configured, and contains pre-shared keys that
match on both ends of the link.
Configuring MACsec on the Router Using Dynamic Secure Association Key Security Mode to
Secure a Router-to-Host Link
Before you begin to enable MACsec on a router-to-host link:
104
must have connectivity to the switch and to the host. The RADIUS server can be
multiple hops from the switch or the host.
The procedures for enabling MACsec on the host device varies by host device, and is
beyond the scope of this document.
To configure MACsec using dynamic security mode to secure a router-to-host Ethernet
link:
1.
Create a connectivity association. You can skip this step if you are configuring an
existing connectivity association.
[edit security macsec]
user@host# set connectivity-association connectivity-association-name
When the must-secure option is enabled, all traffic that is not MACsec-secured that
is received on the interface is dropped.
When the must-secure option is disabled, all traffic from devices that support MACsec
is MACsec-secured while traffic received from devices that do no support MACsec is
forwarded through the network.
The must-secure option is particularly useful in scenarios where multiple devices,
such as a phone and a PC, are accessing the network through the same Ethernet
interface. If one of the devices supports MACsec while the other device does not
support MACsec, the device that doesnt support MACsec can continue to send and
receive traffic over the networkprovided the must-secure option is disabledwhile
traffic to and from the device that supports MACsec is MACsec-secured. In this
scenario, traffic to the device that is not MACsec-secured must be VLAN-tagged.
The must-secure option is disabled, by default.
4. (Required only if the host device requires SCI tagging) Enable SCI tagging:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set include-sci
You should only use this option when connecting a switch to a host that requires SCI
tags. SCI tags are eight octets long, so appending an SCI tag to all traffic on the link
adds a significant amount of unneeded overhead.
5. (Optional) Set the MKA key server priority:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set mka key-server-priority priority-number
105
Specifies the key server priority used by the MKA protocol to select the key server. The
switch with the lower priority-number is selected as the key server.
The default priority-number is 16. If the key-server-priority is identical on both sides
of the point-to-point link, the MKA protocol selects the interface with the lower MAC
address as the key server. Therefore, if this statement is not configured in the
connectivity associations at each end of a MACsec-secured point-to-point link, the
interface with the lower MAC address becomes the key server.
To change the key server priority to 0 to increase the likelihood that the current device
is selected as the key server when MACsec is enabled on the interface using
connectivity association ca1:
[edit security macsec connectivity-association ca-dynamic1]
user@host# set mka key-server-priority 0
To change the key server priority to 255 to decrease the likelihood that the current
device is selected as the key server in connectivity association ca-dynamic1:
[edit security macsec connectivity-association ca-dynamic1]
user@host# set mka key-server-priority 255
6. (Optional) Set the MKA transmit interval:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set mka transmit-interval interval
The MKA transmit interval setting sets the frequency for how often the MKA protocol
data unit (PDU) is sent to the directly connected device to maintain MACsec
connectivity on the link. A lower interval increases bandwidth overhead on the link; a
higher interval optimizes MKA protocol communication.
The default interval is 2000ms. We recommend increasing the interval to 6000 ms
in high-traffic load environments. The transmit interval settings must be identical on
both ends of the link.
For instance, if you wanted to increase the MKA transmit interval to 6000 milliseconds
when connectivity association ca-dynamic1 is attached to an interface:
[edit security macsec connectivity-association ca-dynamic1]
user@host# set mka transmit-interval 6000
7. (Optional) Disable MACsec encryption:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set no-encryption
Encryption is enabled for all traffic entering or leaving the interface when MACsec is
enabled using dynamic security mode, by default. When encryption is disabled, traffic
is forwarded across the Ethernet link in clear text. You are able to view unencrypted
data in the Ethernet frame traversing the link when you are monitoring it. The MACsec
header is still applied to the frame, however, and all MACsec data integrity checks are
run on both ends of the link to ensure the traffic sent or received on the link has not
been tampered with and does not represent a security threat.
8. (Optional) Set an offset for all packets traversing the link:
[edit security macsec connectivity-association connectivity-association-name]
user@host# set offset (0 | 30 | 50)
For instance, if you wanted to set the offset to 30 in the connectivity association
named ca-dynamic1:
106
The default offset is 0. All traffic in the connectivity association is encrypted when
encryption is enabled and an offset is not set.
When the offset is set to 30, the IPv4 header and the TCP/UDP header are unencrypted
while encrypting the rest of the traffic. When the offset is set to 50, the IPv6 header
and the TCP/UDP header are unencrypted while encrypting the rest of the traffic.
You would typically forward traffic with the first 30 or 50 octets unencrypted if a
feature needed to see the data in the octets to perform a function, but you otherwise
prefer to encrypt the remaining data in the frames traversing the link. Load balancing
features, in particular, typically need to see the IP and TCP/UDP headers in the first
30 or 50 octets to properly load balance traffic.
9. (Optional) Enable replay protection.
[edit security macsec connectivity-association connectivity-association-name]
user@host# set replay-protect replay-window-size number-of-packets
For instance, if you did not want Link Level Discovery Protocol (LLDP) to be secured
using MACsec:
[edit security macsec connectivity-association ca-dynamic1]
user@host# set exclude-protocol lldp
107
When this option is enabled, MACsec is disabled for all packets of the specified
protocolin this case, LLDPthat are sent or received on the link.
11. Assign the connectivity association to an interface:
[edit security macsec]
user@host# set interfaces interface-names connectivity-association
connectivity-association-name
Configuring MACsec Using Static Secure Association Key Security Mode to Secure a
Router-to-Router Link
When you enable MACsec using static secure association key (SAK) security mode, one
of up to two manually configured security keys is used to secure the point-to-point
Ethernet link between the switches. All security key names and values are configured by
the user; there is no key server or other tool that creates security keys. Security is
maintained on the point-to-point Ethernet link by periodically rotating the security keys.
Each security key name and value must have a corresponding matching value on the
interface at the other end of the point-to-point Ethernet link to maintain MACsec on the
link.
You configure static SAKs within secure channels when you are enabling MACsec using
static SAK security mode. You configure secure channels within connectivity associations.
A typical connectivity association for MACsec using static SAK security mode contains
two secure channelsone for inbound traffic and one for outbound trafficthat have
each been configured with two static SAKs. You must attach the connectivity association
with the secure channel configurations to an interface to enable MACsec using static
SAK security mode.
To configure MACsec on a router-to-router Ethernet link using static SAK security mode:
1.
Create a connectivity association. You can skip this step if you are configuring an
existing connectivity association.
[edit security macsec]
user@host# set connectivity-association connectivity-association-name
108
3. Create a secure channel within the connectivity association. You can skip this step if
For instance, to create secure channel sc1 in connectivity association ca1, enter:
[edit security macsec]
user@host# set connectivity-association ca1 secure-channel sc1
4. Define the security associations and the static SAKs for the secure channel:
[edit security macsec]
user@host# set connectivity-association connectivity-association-name secure-channel
secure-channel-name security-association number key key-string
where the security-association number is a number between 0 and 3, and the key-string
is a 32-digit key defined statically by the network administrator.
The key string is a 32-digit hexadecimal number. The key string and the security
association must match on both sides of an Ethernet connection to secure traffic
using MACsec.
A secure channel must have at least two security associations with unique key strings.
MACsec uses a security associations to establish a secure communications link, and
periodically rotates to a new security association to keep the link secure. MACsec,
therefore, must have at least one backup security association and key at all times.
To create one secure channel with two security associations and keys, for example:
[edit security macsec]
user@host# set connectivity-association ca1 secure-channel sc1 security-association 0 key
d183c4002fa6fe3d2d9a852c20ab8412
user@host# set connectivity-association ca1 secure-channel sc1 security-association 1 key
b976c7494ab6fe2f2d4c432a90fd90a8
5. Specify whether the secure channel should be applied to traffic entering or leaving
the switch:
[edit security macsec]
user@host# set connectivity-association connectivity-association-name secure-channel
secure-channel-name direction [inbound | outbound]
where inbound applies the secure channel to traffic entering the switch, and outbound
applies the secure channel to traffic leaving the switch.
For instance, to configure secure channel sc1 to apply MACsec to incoming traffic:
[edit security macsec]
user@host# set connectivity-association ca1 secure-channel sc1 direction inbound
109
If you are configuring a MAC address on a secure channel in the outbound direction,
you should specify the MAC address of the interface as the mac-address.
If you are configuring a MAC address on a secure channel in the inbound direction, you
should specify the MAC address of the interface at the other end of the link as the
mac-address.
The mac-address variables must match on the sending and receiving secure channel
on each side of a link to enable MACsec using static SAK security mode.
NOTE: You can see the MAC address of an interface in the show interfaces
output.
The port-id-number variables must match on a sending and receiving secure channel
on each side of a link to enable MACsec.
You can enable MACsec without enabling encryption. If a secure channel is configured
on an interface without encryption, traffic is forwarded across the Ethernet link in clear
text, and you will be able to view unencrypted data in the Ethernet frame traversing
110
the link when you are monitoring it. The MACsec header is still applied to the frame,
however, and all MACsec data integrity checks are run on both ends of the link to
ensure the traffic on the link does not represent a security threat.
Encryption is disabled by default when you are enabling MACsec using static SAK
security mode. To ensure all traffic traversing secure-channel sc1 is encrypted:
[edit security macsec]
user@host# set connectivity-association ca1 secure-channel sc1 encryption
9. (Optional) Set an offset to send the first 30 or 50 octets in unencrypted plain text
When the offset is set to 30, the IPv4 header and the TCP/UDP header are unencrypted
while encrypting the rest of the traffic. When the offset is set to 50, the IPv6 header
and the TCP/UDP header are unencrypted while encrypting the rest of the traffic.
You would typically forward traffic with the first 30 or 50 octets unencrypted if a
feature needed to see the data in the octets to perform a function, but you otherwise
prefer to encrypt the remaining data in the frames traversing the link. Load balancing
features, in particular, typically need to see the IP and TCP/UDP headers in the first
30 or 50 octets to properly load balance traffic.
The default offset is 0, so all traffic on the link is encrypted when the encryption option
is enabled and an offset is not set.
To change the offset to 30 for secure channel sc1:
[edit security macsec]
user@host# set connectivity-association ca1 secure-channel sc1 offset 30
10. Assign the connectivity association to an interface:
[edit security macsec]
user@host# set interfaces interface-names connectivity-association
connectivity-association-name
MACsec using static SAK security mode is not enabled until a connectivity association
on the opposite end of the link is also configured, and the configuration match on both
ends of the link.
111
Configuring VLANs to Direct Traffic onto the MACsec-Secured CCC on page 124
Requirements
This example uses the following hardware and software components:
Three MX Series routers used as the PE and provider routers in the MPLS network
One MX Series router used as the CE router connecting site A to the MPLS network
One MX240, MX480, or MX960 router with the enhanced 20-port Gigabit Ethernet
MIC (model number MIC-3D-20GE-SFP-E) used as the CE router connecting site B to
the MPLS network
Junos OS Release 15.1R1 or later running on all MX Series routers in the MPLS network
(PE1, PE2, or the provider router)
Junos OS Release 15.1R1 or later running on the CE router at site A and the CE router at
site B
112
Table 10 on page 114 provides a summary of the bridge domain and VLAN IDs used in this
topology. The VLAN is used in this topology to direct all communication from the user at
site A to the user at site B onto the MACsec-secured CCC.
Description
PE1
PE router.
lo0:
IP address: 130.1.1.1/32
ge-0/0/0:
ge-0/0/1:
Provider
IP address: 10.1.5.2/24
Provider router.
lo0:
IP address: 130.1.1.2/32
ge-0/0/10:
IP address: 10.1.5.1/24
xe-0/0/0:
IP address: 10.1.9.1/24
113
Description
PE2
PE router.
lo0:
IP address: 130.1.1.3/32
xe-0/1/0
IP address: 10.1.9.2/24
xe-0/1/1
lsp_to_pe2_xe1
label-switched path
lsp_to_pe1_ge0
label-switched path
Description
ccc-macsec
Description
macsec
VLAN directing traffic between the user at site A and the user at site B onto the MACsec-secured
CCC.
The bridge domain includes the following interfaces:
Configuring MPLS
This section explains how to configure MPLS on each router in the MPLS network.
114
To quickly configure the MPLS configuration on the PE1 router, use the following
commands:
[edit]
set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface lo0.0
set protocols ospf area 0.0.0.0 interface ge-0/0/1.0
set protocols mpls label-switched-path lsp_to_pe2_xe1 to 130.1.1.3
set protocols mpls interface ge-0/0/1.0
set protocols rsvp interface lo0.0
set protocols rsvp interface ge-0/0/1.0
set interfaces lo0 unit 0 family inet address 130.1.1.1/32
set interfaces ge-0/0/1 unit 0 family inet address 10.1.5.2/24
set interfaces ge-0/0/1 unit 0 family mpls
set interfaces ge-0/0/0 unit 0 family ccc
set protocols connections remote-interface-switch ge-1-to-pe2 interface ge-0/0/0.0
set protocols connections remote-interface-switch ge-1-to-pe2 transmit-lsp lsp_to_pe2_xe1
set protocols connections remote-interface-switch ge-1-to-pe2 receive-lsp lsp_to_pe1_ge0
Step-by-Step
Procedure
2.
3.
Configure MPLS on this router, PE1, with an LSP to the PE2 router:
[edit protocols]
user@router-PE1# set mpls label-switched-path lsp_to_pe2_xe1 to 130.1.1.3
4.
5.
6.
Configure IP addresses for the loopback interface and the core interfaces:
[edit]
user@router-PE1# set interfaces lo0 unit 0 family inet address 130.1.1.1/32
user@router-PE1# set interfaces ge-0/0/1 unit 0 family inet address 10.1.5.2/24
7.
Configure family mpls on the logical unit of the core interface addresses:
[edit]
115
9.
Results
interfaces {
ge-0/0/0 {
unit 0 {
family ccc;
}
}
ge-0/0/1{
unit 0 {
family inet {
address 130.1.5.2/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 130.1.1.1/32;
}
}
}
}
protocols {
rsvp {
interface lo0.0;
interface ge-0/0/1.0;
}
mpls {
label-switched-path lsp_to_pe2_xe1 {
to 130.1.1.3;
}
interface ge-0/0/1.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface lo0.0;
interface ge-0/0/1.0;
}
}
connections {
116
remote-interface-switch ge-1-to-pe2 {
interface ge-0/0/0.0;
transmit-lsp lsp_to_pe2_xe1;
receive-lsp lsp_to_pe1_ge0;
}
}
}
To quickly configure the MPLS configuration on the provider router, use the following
commands:
[edit]
set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface lo0.0
set protocols ospf area 0.0.0.0 interface ge-0/0/10.0
set protocols ospf area 0.0.0.0 interface xe-0/0/0.0
set protocols mpls interface ge-0/0/10.0
set protocols mpls interface xe-0/0/0.0
set protocols mpls label-switched-path lsp_to_pe2_xe1 to 130.1.1.3
set protocols rsvp interface lo0.0
set protocols rsvp interface ge-0/0/10.0
set protocols rsvp interface xe-0/0/0.0
set interfaces lo0 unit 0 family inet address 130.1.1.2/32
set interfaces ge-0/0/10 unit 0 family inet address 10.1.5.1/24
set interfaces ge-0/0/10 unit 0 family mpls
set interfaces xe-0/0/0 unit 0 family inet address 10.1.9.1/24
set interfaces xe-0/0/0 unit 0 family mpls
Step-by-Step
Procedure
2.
3.
4.
5.
Configure IP addresses for the loopback interface and the core interfaces:
[edit]
user@router-P# set interfaces lo0 unit 0 family inet address 130.1.1.2/32
user@router-P# set interfaces ge-0/0/10 unit 0 family inet address 10.1.5.1/24
user@router-P# set interfaces xe-0/0/0 unit 0 family inet address 10.1.9.1/24
6.
Configure family mpls on the logical unit of the core interface addresses:
117
[edit]
user@router-P# set interfaces ge-0/0/10 unit 0 family mpls
user@router-P# set interfaces xe-0/0/0 unit 0 family mpls
7.
Results
interfaces {
ge-0/0/10 {
unit 0 {
family inet {
address 10.1.5.1/24;
}
family mpls;
}
}
xe-0/0/0 {
unit 0 {
family inet {
address 10.1.9.1/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 130.1.1.2/32;
}
}
}
}
protocols {
rsvp {
interface lo0.0;
interface ge-0/0/10.0;
interface xe-0/0/0.0;
}
mpls {
label-switched-path lsp_to_pe2_xe1 {
to 130.1.1.3;
}
interface ge-0/0/10.0;
interface xe-0/0/0.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface lo0.0;
interface ge-0/0/10.0;
interface xe-0/0/0.0;
}
118
}
}
To quickly configure the MPLS configuration on router PE2, use the following commands:
Step-by-Step
Procedure
[edit]
set protocols ospf traffic-engineering
set protocols ospf area 0.0.0.0 interface lo0.0
set protocols ospf area 0.0.0.0 interface xe-0/1/0.0
set protocols mpls label-switched-path lsp_to_pe1_ge0 to 130.1.1.1
set protocols mpls interface xe-0/1/0.0
set protocols rsvp interface lo0.0
set protocols rsvp interface xe-0/1/0.0
set interfaces lo0 unit 0 family inet address 130.1.1.3/32
set interfaces xe-0/1/0 unit 0 family inet address 10.1.9.2/24
set interfaces xe-0/1/0 unit 0 family mpls
set interfaces xe-0/1/1 unit 0 family ccc
set protocols connections remote-interface-switch xe-1-to-pe1 interface xe-0/1/1.0
set protocols connections remote-interface-switch xe-1-to-pe1 transmit-lsp lsp_to_pe1_ge0
set protocols connections remote-interface-switch xe-1-to-pe1 receive-lsp lsp_to_pe2_xe1
1.
2.
3.
Configure MPLS on this router (PE2) with a label-switched path (LSP) to the other
PE router (PE1):
[edit protocols]
user@router-PE2# set mpls label-switched-path lsp_to_pe1_ge0 to 130.1.1.1
4.
5.
6.
Configure IP addresses for the loopback interface and the core interface:
[edit]
user@router-PE2# set interfaces lo0 unit 0 family inet address 130.1.1.3/32
user@router-PE2# set interfaces xe-0/1/0 unit 0 family inet address 10.1.9.2/24
7.
8.
119
9.
Results
Display the results of the configuration:
user@router-PE2> show configuration
interfaces {
xe-0/1/0 {
unit 0 {
family inet {
address 10.1.9.2/24;
}
family mpls;
}
}
xe-0/1/1 {
unit 0 {
family ccc;
}
}
lo0 {
unit 0 {
family inet {
address 130.1.1.3/32;
}
}
}
}
protocols {
rsvp {
interface lo0.0;
interface xe-0/1/0.0;
}
mpls {
label-switched-path lsp_to_pe1_ge0 {
to 130.1.1.1;
}
interface xe-0/1/0.0;
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface lo0.0;
interface xe-0/1/0.0;
}
}
connections {
remote-interface-switch xe-1-to-pe1 {
120
interface xe-0/1/1.0;
transmit-lsp lsp_to_pe1_ge0;
receive-lsp lsp_to_pe2_xe1;
}
}
}
Configuring MACsec
This section explains how to configure MACsec on each router in the topology.
It includes the following sections:
Configuring MACsec on the Site A CE Router to Secure Traffic to Site B on page 121
Configuring MACsec on the Site B CE Router to Secure Traffic to Site A on page 123
[edit]
set security macsec connectivity-association ccc-macsec security-mode static-cak
set security macsec connectivity-association ccc-macsec pre-shared-key ckn
37c9c2c45ddd012aa5bc8ef284aa23ff6729ee2e4acb66e91fe34ba2cd9fe311
set security macsec connectivity-association ccc-macsec pre-shared-key cak
228ef255aa23ff6729ee664acb66e91f
set security macsec interfaces ge-0/0/0 connectivity-association ccc-macsec
Step-by-Step
Procedure
In this example, the traffic between the users that often exchange financially-sensitive
data is sent between the sites on a CCC through the MPLS cloud. MACsec is enabled on
the CCC by configuring a MACsec connectivity association on the interfaces on the site
A and site B CE routers that connect to the MPLS PE routers. The connectivity associations
must have matching connectivity-association names (in this example, ccc-macsec),
matching CKNs (in this example,
37c9c2c45ddd012aa5bc8ef284aa23ff6729ee2e4acb66e91fe34ba2cd9fe311), and
CAKs (in this example, 228ef255aa23ff6729ee664acb66e91f) in order to establish a
MACsec-secure connection.
To enable MACsec on the CCC connecting site A to site B, perform the following procedure
on the site A CE router:
1.
Create the connectivity association named ccc-macsec, and configure the MACsec
security mode as static-cak:
[edit security macsec]
user@router-CE-A# set connectivity-association ccc-macsec security-mode static-cak
2.
3.
Assign the connectivity association to the interface connecting to the PE1 router:
[edit security macsec]
user@router-CE-A# set interfaces ge-0/0/0 connectivity-association ccc-macsec
121
This completes the steps for configuring the connectivity association on one end
of the CCC. MACsec is not enabled until a connectivity association with matching
pre-shared keys is enabled on the opposite end of a link, which in this case is the
interface on the site B CE router, of the CCC. The process for configuring the
connectivity association on the site B CE router is described in the following section.
Results
security {
macsec {
connectivity-association {
ccc-macsec {
pre-shared-key {
cak "$9$rJ-lWLxNdw24Xxik.PQzreK"; ## SECRET-DATA
ckn 37c9c2c45ddd012aa5bc8ef284aa23ff6729ee2e4acb66e91fe34ba2cd9fe311;
}
security-mode {
static-cak;
}
}
}
interfaces {
ge-0/0/0 {
connectivity-association {
ccc-macsec;
}
}
}
}
}
122
[edit]
set security macsec connectivity-association ccc-macsec security-mode static-cak
set security macsec connectivity-association ccc-macsec pre-shared-key ckn
37c9c2c45ddd012aa5bc8ef284aa23ff6729ee2e4acb66e91fe34ba2cd9fe311
set security macsec connectivity-association ccc-macsec pre-shared-key cak
228ef255aa23ff6729ee664acb66e91f
set security macsec interfaces xe-0/1/0 connectivity-association ccc-macsec
Step-by-Step
Procedure
Traffic travels from site B to site A over the MPLS network using a CCC. MACsec is enabled
on the CCC by configuring a MACsec connectivity association on the interfaces on the
site A and site B CE routers that connect to the MPLS PE routers. The connectivity
associations must have matching connectivity-association names (in this example,
ccc-macsec), matching CKNs
(37c9c2c45ddd012aa5bc8ef284aa23ff6729ee2e4acb66e91fe34ba2cd9fe311), and
matching CAKs (228ef255aa23ff6729ee664acb66e91f) in order to establish a
MACsec-secure connection.
To enable MACsec on the CCC connecting site B to site A, perform the following procedure
on the site B CE router:
1.
Create the connectivity association named ccc-macsec, and configure the MACsec
security mode as static-cak:
[edit security macsec]
user@router-CE-B# set connectivity-association ccc-macsec security-mode static-cak
2.
3.
MACsec is enabled for the CCC after the pre-shared keys are exchanged, which is
shortly after this procedure is completed.
Results
security {
macsec {
connectivity-association {
ccc-macsec {
security-mode {
static-cak;
}
pre-shared-key {
cak "$9$rJ-lWLxNdw24Xxik.PQzreK"; ## SECRET-DATA
ckn 37c9c2c45ddd012aa5bc8ef284aa23ff6729ee2e4acb66e91fe34ba2cd9fe311;
}
123
}
}
interfaces {
xe-0/1/0 {
connectivity-association {
ccc-macsec;
}
}
}
}
}
Configuring the Bridge Domain to Direct Traffic to the MACsec CCC on the Site A CE
Router on page 124
Configuring the Bridge Domain to Direct Traffic to the MACsec CCC on the Site B CE
Router on page 126
Configuring the Bridge Domain to Direct Traffic to the MACsec CCC on the Site A
CE Router
CLI Quick
Configuration
[edit]
set interfaces ge-0/0/0 unit 0 encapsulation vlan-bridge
set interfaces ge-0/0/0 unit 0 family bridge
set interfaces ge-0/0/2 unit 0 encapsulation vlan-bridge
set interfaces ge-0/0/2 unit 0 family bridge
set bridge-domains macsec vlan-id 50
set bridge-domains macsec domain-type bridge
set bridge-domains macsec vlan-id all
set bridge-domains macsec interface ge-0/0/0
set bridge-domains macsec interface ge-0/0/2
set interfaces irb vlan-id 50 family inet address 5.5.5.1/24
Step-by-Step
Procedure
To create a bridge domain (VLAN ID 50) that directs traffic from the user at site A onto
the MACsec-secured CCC:
1.
Configure the ge-0/0/0 interface with VLAN encapsulation and the bridge family.
user@router-CE-A# set interfaces ge-0/0/0 unit 0 encapsulation vlan-bridge
user@router-CE-A# set interfaces ge-0/0/0 unit 0 family bridge vlan-id 50
2.
Configure the ge-0/0/2 interface with VLAN encapsulation and the bridge family.
[edit]
user@router-CE-A#set interfaces ge-0/0/2 unit 0 encapsulation vlan-bridge
user@router-CE-A#set interfaces ge-0/0/2 unit 0 family bridge vlan-id 50
3.
Define the macsec bridge domain and associate the interfaces, ge-0/0/0 and
ge-0/0/2, with the bridge domain.
[edit]
user@router-CE-A# set bridge-domains macsec vlan-id 50
user@router-CE-A# set bridge-domains macsec domain-type bridge
124
Results
125
Configuring the Bridge Domain to Direct Traffic to the MACsec CCC on the Site B
CE Router
CLI Quick
Configuration
[edit]
set interfaces xe-0/1/0 unit 0 encapsulation vlan-bridge
set interfaces xe-0/1/0 unit 0 family bridge
set interfaces ge-0/0/2 unit 0 encapsulation vlan-bridge
set interfaces ge-0/0/2 unit 0 family bridge
set bridge-domains macsec vlan-id 50
set bridge-domains macsec domain-type bridge
set bridge-domains macsec vlan-id all
set bridge-domains macsec interface ge-0/0/2
set bridge-domains macsec interface xe-0/1/0
set interfaces irb vlan-id 50 family inet address 5.5.5.2/24
Step-by-Step
Procedure
To create a bridge domain (VLAN ID 50) to direct traffic for the user at site B onto the
MACsec-secured CCC:
1.
Configure the xe-0/1/0 interface with VLAN encapsulation and the bridge family.
user@router-CE-A# set interfaces xe-0/1/0 unit 0 encapsulation vlan-bridge
user@router-CE-A# set interfaces xe-0/1/0 unit 0 family bridge vlan-id 50
2.
Configure the ge-0/0/2 interface with VLAN encapsulation and the bridge family.
[edit]
user@router-CE-A#set interfaces ge-0/0/2 unit 0 encapsulation vlan-bridge
user@router-CE-A#set interfaces ge-0/0/2 unit 0 family bridge vlan-id 50
3.
Define the macsec bridge domain and associate the interfaces, xe-0/1/0 and
ge-0/0/2, with the bridge domain.
[edit]
user@router-CE-A#
user@router-CE-A#
user@router-CE-A#
user@router-CE-A#
4.
Results
126
}
}
}
irb {
vlan-id 50 {
family inet address 5.5.5.2/24;
}
}
}
bridge-domains {
macsec {
domain-type bridge;
vlan-id 50;
interface xe-0/1/0;
interface ge-0/0/2;
}
}
Verification
To confirm that the configuration is working properly, perform these tasks:
Verifying That the MPLS and CCC Protocols Are Enabled on the Provider Edge and
Provider Switch Interfaces on page 128
127
Meaning
The Interface name: and CA name: outputs shows that the ccc-macsec connectivity
association is operational on interface ge-0/0/0. The output does not appear when the
connectivity association is not operational on the interface.
For additional verification that MACsec is operational on the CCC, you can also enter the
show security macsec connections command on the other CE switch.
Meaning
The Encrypted packets line under the Secure Channel transmitted output is incremented
each time a packet is sent from the interface that is secured and encrypted by MACsec.
The Encrypted packets output shows that 9784 encrypted and secured packets have
been transmitted from interface ge-0/0/0. MACsec-secured traffic is, therefore, being
sent on interface ge-0/0/0.
The Accepted packets line under the Secure Association received output is incremented
each time a packet that has passed the MACsec integrity check is received on the interface.
The Decrypted bytes line under the Secure Association received output is incremented
each time an encrypted packet is received and decrypted. The output shows that 9791
MACsec-secured packets have been received on interface ge-0/0/0, and that 2823555
bytes from those packets have been successfully decrypted. MACsec-secured traffic is,
therefore, being received on interface ge-0/0/0.
For additional verification, you can also enter the show security macsec statistics command
on the other CE switch.
Verifying That the MPLS and CCC Protocols Are Enabled on the Provider Edge
and Provider Switch Interfaces
Purpose
128
Verify that MPLS is enabled on the correct interfaces for the PE and provider switches.
Action
Enter the show interfaces terse command on both of the PE routers and the provider
switch:
user@router-PE1> show interfaces terse
Interface
Admin Link Proto
ge-0/0/0
up
up
ge-0/0/0.0
up
up
ccc
ge-0/0/1
up
up
ge-0/0/1.0
up
up
inet
mpls
<some output removed for brevity>
user@router-P> show interfaces terse
Interface
Admin Link Proto
xe-0/0/0
up
up
xe-0/0/0.0
up
up
inet
mpls
ge-0/0/10
up
up
ge-0/0/10.0
up
up
inet
mpls
<some output removed for brevity>
user@router-PE2> show interfaces terse
Interface
Admin Link Proto
xe-0/1/0
up
up
xe-0/1/0.0
up
up
inet
mpls
xe-0/1/1
up
up
xe-0/1/1.0
up
up
ccc
<some output removed for brevity>
Meaning
Local
Remote
10.1.5.2/24
Local
Remote
10.1.9.1/24
10.1.5.1/24
Local
Remote
10.1.9.2/24
The output confirms that the MPLS protocol is up for the provider switch interfaces
passing MPLS trafficxe-0/0/0 and ge-0/0/10and on the PE router interfaces passing
MPLS traffic, which is interface ge-0/0/1 on the PE1 switch and interface xe-0/1/0 on
the PE2 router.
The output also confirms that CCC is enabled on the PE router interfaces facing the CE
switches, which are interface ge-0/0/0 on the PE1 switch and interface xe-0/1/1 on the
PE2 router.
Action
Verify which interface is being used as the beginning of the CCC and which interface is
being used to push the MPLS packet to the next hop.
Enter the show route forwarding-table family mpls on one or both of the PE routers.
user@router-PE1> show route forwarding-table family mpls
Routing table: default.mpls
MPLS:
Destination
Type RtRef Next hop
default
perm
0
0
user
0
1
user
0
2
user
0
13
user
0
129
299856
ge-0/0/0.0
Meaning
(CCC)
user
user
0
0 10.1.5.1
Pop
1327
2 ge-0/0/0.0
Push 299952 1328
2 ge-0/0/1.0
This output confirms that the CCC is configured on interface ge-0/0/0.0. The switch
receives ingress traffic on ge-0/0/1.0 and pushes label 299952 onto the packet, which
exits the switch through interface ge-0/0/1.0. The output also shows that when the
switch receives an MPLS packet with label 299856, it pops the label and sends the packet
out through interface ge-0/0/0.0
For further verification of MPLS label operations, enter the show route forwarding-table
family mpls on the other PE router.
Connection/Circuit
ge-1-to-pe2
ge-0/0/0.0
lsp_to_pe2_xe1
lsp_to_pe1_ge0
Type
rmt-if
intf
tlsp
rlsp
St
Up
Up
Up
Up
Time last up
# Up trans
May 30 19:01:45
1
Connection/Circuit
xe-1-to-pe1
xe-0/1/1.0
130
Type
rmt-if
intf
St
Up
Up
Time last up
# Up trans
May 30 09:39:15
1
lsp_to_pe1_ge0
lsp_to_pe2_xe1
tlsp
rlsp
Up
Up
The show connections command displays the status of the CCC connections. This output
verifies that the CCC interfaces and their associated transmit and receive LSPs are Up
on both PE routers.
Meaning
State
Full
Full
ID
130.1.1.1
130.1.1.3
Pri
128
128
Dead
33
38
The State output is Full on all interfaces using OSPF, so OSPF is operating.
For further verification on OSPF, enter the show ospf neighbor command on the PE routers
in addition to the provider switch.
Meaning
131
132
CHAPTER 8
Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on page 148
Configuring the Number of Aggregated Ethernet Interfaces on the Device on page 154
133
Example: Configuring Independent Micro BFD Sessions for LAG on page 203
For information about mixed rates and mixed modes on an aggregated Ethernet bundle,
see Understanding Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on
page 141.
134
Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links.
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
NOTE:
TIP:
Going forward:
Table 11 on page 135 lists the platforms and corresponding hardware components that
support mixed aggregated Ethernet bundles.
Table 11: Platform Support Matrix for Mixed Aggregated Ethernet Bundles
Rate and
Mode
Supported
Platform
10-Gigabit
Ethernet LAN
and WAN
T640, T1600,
T4000, and TX
Matrix Plus routers
Supported FPCs
Supported PICs
(WAN rate:
OC192)
135
Table 11: Platform Support Matrix for Mixed Aggregated Ethernet Bundles (continued)
Rate and
Mode
Supported
Platform
40-Gigabit
Ethernet,
100-Gigabit
Ethernet
Supported FPCs
Supported PICs
T4000 and TX
Matrix Plus routers
T640, T1600,
T4000, and TX
Matrix Plus routers
All Juniper routers support at least eight physical interfaces per aggregated Ethernet
bundle. See maximum-links configuration page for platform specific limits.
On M Series and T Series routers, you can create a maximum of 1024 logical interfaces
on an aggregated Ethernet interface.
Aggregated Ethernet interfaces can use interfaces from different FPCs, DPCs, PICs, or
MPCs.
Simple filters are not supported for interfaces in aggregated Ethernet bundles:
On MX Series routers, simple filters are supported in Enhanced Queuing Dense Port
Concentrator (EQ DPC) interfaces only, except when the interface is part of an
aggregated Ethernet bundle.
For more information about simple filters, see the Class of Service Feature Guide for
Routing Devices.
136
Aggregated Ethernet interfaces can be either tagged or untagged, with LACP enabled
or disabled. Aggregated Ethernet interfaces on MX Series routers support the
configuration of flexible-vlan-tagging and native-vlan-id on dual-tagged frames, which
consist of the following configuration statements:
inner-tag-protocol-id
inner-vlan-id
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
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.
When configuring mixed aggregated Ethernet bundles on T640, T1600, T4000, and
TX Matrix Plus routers, consider the following:
Link Aggregation Control Protocol (LACP), aggregated Ethernet link protection, and
LACP link protection are supported only on mixed aggregated Ethernet link configured
on a 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4).
Traffic distribution is based on the hash calculated on the egress packet header.
Hash range is fairly distributed according to member links speed. This guarantees
hash fairness but it does not guarantee fair traffic distribution depending on the rate
of the egress streams.
Packets are dropped when the total throughput of the hash flow exiting a member
link (or multiple hash flows exiting a single member link) exceeds the link speed of
the member link. This can happen when egress member link changes because of a
link failure and the hash flow switches to a member link of speed that is less than
the total throughput of the hash flow.
Rate-based CoS components such as scheduler, shaper, and policer are not
supported on mixed rate aggregated Ethernet links. However, the default CoS settings
are supported by default on the mixed rate aggregated Ethernet links.
Load balancing of the egress traffic across the member links of a mixed rate
aggregated Ethernet link is proportional to the rates of the member links.
137
of on T640, T1600, T4000, and TX Matrix Plus routers, leads to aggregated Ethernet
link flapping.
Related
Documentation
The show interfaces aex command displays the link speed of the aggregated Ethernet
interface, which is the sum of the link speeds of all the active member links.
Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on page 148
Capabilities of Gigabit Ethernet IQ PICs and Gigabit Ethernet PICs with SFPs on page 461
138
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
NOTE: On a Junos Fusion Fabric, you can include extended ports (physical
interface on a satellite device that provides a connection to servers or
endpoints) or local ports in link aggregation groups (LAGs) and MC-LAGs,
but not both. For information on extended ports, see Understanding Junos
Fusion Ports.
Specify that you want to configure the link aggregation group interface.
user@host# edit interfaces interface-name
You specify the interface instance number x to complete the link association; x can be
from 0 through 127, for a total of 128 aggregated interfaces on M Series and T Series
routers and can be from 1 through 480, for a total of 480 aggregated interfaces on MX
Series routers. For MX Series routers running Junos release 14.2R3 and later you can
configure a maximum of 1000 aggregated interfaces. Aggregated interfaces are numbered
from ae0 through ae4092.
You must also include a statement defining aex at the [edit interfaces] hierarchy level.
You can optionally specify other physical properties that apply specifically to the
aggregated Ethernet interfaces; for details, see Ethernet Interfaces Overview on page 3,
and for a sample configuration, see Example: Configuring Aggregated Ethernet Interfaces
on page 151.
139
Related
Documentation
Configuring the Number of Aggregated Ethernet Interfaces on the Device on page 154
Fault tolerance
Advanced features including flexible VLAN tagging and Ethernet services encapsulation
Aggregated Ethernet interfaces can use interfaces from different FPCs or PICs. The
following configuration is sufficient to get an aggregated Gigabit Ethernet interface up
and running.
[edit chassis]
aggregated-devices {
ethernet {
device-count 2;
}
}
[edit interfaces]
et-0/0/0 {
140
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
gigether-options {
802.3ad ae0;
}
}
et-0/0/1 {
gigether-options {
802.3ad ae0;
}
}
ae0 {
vlan-tagging;
unit 0 {
vlan-id 100;
family inet {
address 200.200.1.2/24;
}
}
unit 1 {
vlan-id 101;
family inet {
address 200.200.2.2/24;
}
}
}
Related
Documentation
Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on page 148
Aggregated Ethernet Bundle with Mixed Rates and Mixed Modes on T Series
Routers on page 142
Aggregated Ethernet Bundles with Mixed Rates on MX Series Routers on page 145
141
Supported Platforms
Table 12 on page 142 summarizes the first Junos OS release that supports aggregated
Ethernet bundles on the various Juniper Networks routers and their components:
Junos OS Release
Mixed rates and mixed modes on T640, T1600, T4000, and TX Matrix Plus routers
13.2
14.1R2
14.2
14.2
15.1
Aggregated Ethernet Bundle with Mixed Rates and Mixed Modes on T Series Routers
The following sections explain mixed rates and mixed modes on T Series routers:
Platform Support Matrix for Mixed Aggregated Ethernet Bundles on page 143
Guidelines to Follow When Configuring Aggregated Ethernet Bundles with Mixed Rates
and Mixed Modes on page 144
142
Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links.
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
NOTE:
Going forward:
Table 13: Platform Support Matrix for Mixed Aggregated Ethernet Bundles
Rate and
Mode
Supported
Platform
10-Gigabit
Ethernet LAN
and WAN
T640, T1600,
T4000, and TX
Matrix Plus routers
Supported FPCs
Supported PICs
(WAN rate:
OC192)
143
Table 13: Platform Support Matrix for Mixed Aggregated Ethernet Bundles (continued)
Rate and
Mode
Supported
Platform
40-Gigabit
Ethernet,
100-Gigabit
Ethernet
Supported FPCs
Supported PICs
T4000 and TX
Matrix Plus routers
T640, T1600,
T4000, and TX
Matrix Plus routers
144
Link Aggregation Control Protocol (LACP), aggregated Ethernet link protection, and
LACP link protection are supported only on mixed aggregated Ethernet bundles
configured on a 100-Gigabit Ethernet PIC with CFP (PD-1CE-CFP-FPC4).
Traffic distribution is based on the hash calculated on the egress packet header. Hash
range is fairly distributed according to member links speed. This guarantees hash
fairness but it does not guarantee fair traffic distribution depending on the rate of the
egress streams.
Packets are dropped when the total throughput of the hash flow exiting a member link
(or multiple hash flows exiting a single member link) exceeds the link speed of the
member link. This can happen when egress member link changes because of a link
failure and the hash flow switches to a member link of speed that is less than the total
throughput of the hash flow.
Rate-based CoS components such as scheduler, shaper, and policer are not supported
on mixed-rate aggregated Ethernet links. However, the default CoS settings are
supported by default on the mixed-rate aggregated Ethernet links.
Load balancing is performed at the ingress Packet Forwarding Engine. Therefore, you
must ensure that the egress traffic on the aggregated Ethernet link enters through the
hardware platforms that support mixed aggregated Ethernet bundles.
Table 11 on page 135 lists the platforms and corresponding hardware components that
support mixed aggregated Ethernet bundles.
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Mixed aggregated Ethernet links can interoperate with non-Juniper Networks aggregated
Ethernet member links provided that mixed aggregated Ethernet load balancing is
configured at egress.
Load balancing of the egress traffic across the member links of a mixed-rate aggregated
Ethernet link is proportional to the rates of the member links.
When configuring a mixed aggregated Ethernet link on a 100-Gigabit Ethernet PIC with
CFP (PD-1CE-CFP-FPC4), ensure that you add both the 50-Gigabit Ethernet interfaces
of the 100-Gigabit Ethernet PIC with CFP to the aggregated Ethernet bundle. Moreover,
both these 50-Gigabit Ethernet interfaces must be included in the same aggregated
Ethernet bundle.
The show interfaces aex command displays the link speed of the aggregated Ethernet
interface, which is the sum of the link speeds of all the active member links.
Enable the mixed-rate configuration on all the aggregated Ethernet bundles on the
egress side of the Modular Port Concentrators (MPCs).
145
Enable the router to detect child links of different speed values in the aggregated
Ethernet bundle.
You can also configure the minimum bandwidth on an aggregated Ethernet bundle when
you configure mixed rate on that aggregated Ethernet bundle.
Supported Features
The following features are supported on mixed-rate aggregated Ethernet bundles on MX
Series routers:
Non link-protect mode. For more information, see Configuring Scheduler on Aggregated
Ethernet Interfaces Without Link Protection on page 170.
LACP for slow and fast interval for periodic transmission of LACP packets.
Scheduler parameters for aggregated interface member links in a scaled manner with
the member-link-scheduler scale statement at the [edit class-of-service interfaces]
hierarchy level.
Configuration of following statements as percentages only for mixed rates at the [edit
class-of-service schedulers scheduler-name] hierarchy level:
146
buffer-size
excess-rate
shaping-rate
transmit-rate
Configuration of the following statements for mixed rates at the [edit class-of-service
schedulers scheduler-name] hierarchy level:
drop-profile-map
excess-priority
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
priority
Unicast load balancing, where the load balancing happens on ingress-only selectors.
Make-before-break (MBB) for multicast LDP (MLDP) and fast reroute (FRR).
Source class usage (SCU) and destination class usage (DCU) accounting.
The following features are not supported on mixed-rate aggregated Ethernet bundles
on MX Series routers:
Related
Documentation
Shaping rate, where traffic shaping is achieved by specifying the amount of bandwidth
to be allocated to a logical interface.
Ingress queuing.
Options that are configured with nonpercentage values at the [edit class-of-service
schedulers scheduler-name] hierarchy level.
Layer 2 features.
Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on page 148
147
Configuring Mixed Rates and Mixed Modes on an Aggregated Ethernet Bundle on T Series
Routers
In releases before Junos OS Release 13.2, all interfaces that form an aggregated Ethernet
bundle must have the same speed and must be in full-duplex mode. Starting with Junos
OS Release 13.2, aggregated Ethernet supports the following mixed rates and mixed
modes on T640, T1600, T4000, and TX Matrix Plus routers:
Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links.
NOTE:
148
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
[edit chassis]
user@host# set aggregated-devices ethernet device-count number
3. Go to the [edit interfaces] hierarchy level.
user@host# top
user@host# edit interfaces
4. Configure the minimum number of links that are required for the aggregated Ethernet
NOTE: By default, only one link needs to be up for the bundle to be labeled
up.
5. Configure the link-speed statement and specify the mixed option for the link-speed
statement to indicate the mixed-rate and mixed-mode support for the aggregated
Ethernet bundle configuration.
[edit interfaces]
user@host# set aex aggregated-ether-options link-speed mixed
[edit interfaces]
user@host# set interface-name gigether-options 802.3ad aex
7. Configure an interface family and an IP address for the aggregated Ethernet bundle.
[edit interfaces]
user@host# set aex unit number family (inet | inet6 | mpls ) address address
8. Commit the configuration.
[edit interfaces]
user@host# commit
149
[edit chassis]
user@host# set aggregated-devices ethernet device-count number
3. Go to the [edit interfaces] hierarchy level.
user@host# top
user@host# edit interfaces
4. Configure the link-speed statement and specify the mixed option for the link-speed
statement to indicate the mixed-rate support for the aggregated Ethernet bundle
configuration.
[edit interfaces]
user@host# set aex aggregated-ether-options link-speed mixed
5. Configure the members links of the aggregated Ethernet bundle:
[edit interfaces]
user@host# set interface-name gigether-options 802.3ad aex
6. Configure an interface family for the aggregated Ethernet bundle as inet, inet6, or
mpls:
[edit interfaces]
user@host# set aex unit number family (inet | inet6 | mpls)
7. Configure the minimum bandwidth unit as bps, gbps, kbps, or mbps and the bandwidth
[edit interfaces]
user@host# commit
Related
Documentation
150
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
151
family inet {
address 14.0.102.50/24;
}
}
unit 3 {
vlan-id 4094;
family inet {
address 14.0.103.50/24;
}
}
}
Related
Documentation
Configure 'link-speed' for Gigabit Ethernet based Aggregate Ethernet interface bundles
For M Series and T Series routers you can configure a maximum of 128 aggregated
interfaces (LAG bundles). On MX Series routers running Junos release 14.2R2 and earlier,
you can configure a maximum of 480 aggregated interfaces. For MX Series routers running
Junos release 14.2R3 and later you can configure a maximum of 1000 aggregated
interfaces. For MX2010 and MX2020 routers you can configure a maximum of 800
152
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
aggregated interfaces. In all cases the aggregated interfaces are numbered from ae0
through ae4092
For SONET/SDH, starting with Junos OS Release 13.2, the maximum number of logical
interfaces is 64, numbered from as0 through as63. In releases before Junos OS Release
13.2, the maximum was 16.
NOTE: LACP link protection also uses port priority. You can configure port
priority at the Ethernet interface [gigether-options] hierarchy level using the
port-priority statement. If you choose not to configure port priority, LACP link
protection uses the default value for port priority (127).
153
The system priority is a 2-octet binary value that is part of the LACP system ID. The LACP
system ID consists of the system priority as the two most-significant octets and the
interface MAC address as the six least-significant octets. The system with the numerically
lower value for system priority has the higher priority. By default, system priority is 127,
with a range of 0 through 65,535.
Related
Documentation
154
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
you can configure a maximum of 480 aggregated interfaces. For MX Series routers running
Junos release 14.2R3 and later you can configure a maximum of 1000 aggregated
interfaces. For MX2010 and MX2020 routers you can configure a maximum of 800
aggregated interfaces. In all cases the aggregated interfaces are numbered from ae0
through ae4092
NOTE: On a Junos Fusion Fabric, you can include extended ports (physical
interface on a satellite device that provides a connection to servers or
endpoints) or local ports in link aggregation groups (LAGs) and MC-LAGs,
but not both. For information on extended ports, see Understanding Junos
Fusion Ports.
For SONET/SDH, starting with Junos OS Release 13.2, the maximum number of logical
interfaces is 16, numbered from as0 through as15.
1.
Specify that you want to access the aggregated Ethernet configuration on the device.
user@host# edit chassis aggregated-devices ethernet
You must also specify the constituent physical links by including the 802.3ad statement
at the [edit interfaces interface-name fastether-options] or [edit interfaces interface-name
gigether-options] hierarchy level.
Related
Documentation
For information about physical links, see Configuring an Aggregated Ethernet Interface
on page 138
For information about configuring aggregated devices, see the Junos OS Administration
Library for Routing Devices.
Member links of different modes (WAN and LAN) for 10-Gigabit Ethernet links.
155
Starting with Junos OS Release 14.2, aggregated Ethernet supports mixed link speeds on
PTX Series Packet Transport Routers.
NOTE:
To configure member links of mixed rates and mixed modes on T640, T1600, T4000,
and TX Matrix Plus routers, you need to configure the mixed option for the [edit interfaces
aex aggregated-ether-options link-speed] statement.
To set the required link speed:
1.
156
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Related
Documentation
Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on page 148
157
On M120, M320, MX Series, T Series, and TX Matrix routers with Ethernet interfaces, and
EX 9200 switches, the valid range for minimum-links number is 1 through 16. When the
maximum value (16) is specified, all configured links of a bundle must be up for the bundle
to be labeled up.
On all other routers and on EX Series switches, other than EX8200 switches, the range
of valid values for minimum-links number is 1 through 8. When the maximum value (8) is
specified, all configured links of a bundle must be up for the bundle to be labeled up.
On EX8200 switches, the range of valid values for minimum-links number is 1 through 12.
When the maximum value (12) is specified, all configured links of a bundle must be up
for the bundle to be labeled up.
On MX Series routers, when Link Aggregation Control Protocol (LACP) is enabled on a
link aggregation group (LAG) interface along with minimum links configuration, the bundle
is considered to be up when the following two conditions are met:
The links are in collecting distributing statethat is, collecting and distributing states
are merged together to form a combined state (coupled control) for the aggregated
port. Because independent control is not possible, the coupled control state machine
does not wait for the partner to signal that collection has started before enabling both
collection and distribution.
If the number of links configured in an aggregated Ethernet interface is less than the
minimum link value configured under the aggregated-ether-options statement, the
configuration commit fails and an error message is displayed.
Related
Documentation
158
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
For more information about the vlan-tagging and vlan-id statements, see 802.1Q VLANs
Overview on page 244.
Related
Documentation
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.
You cannot include the vlan-id statement in the configuration of the logical interface.
Table 14 on page 159 lists untagged aggregated Ethernet and LACP support by PIC and
router.
Table 14: Untagged Aggregated Ethernet and LACP Support by PIC and
Platform
PIC Type
M Series
LACP
T Series
LACP
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
NA
NA
Yes
Yes
Yes
N/A
NA
Yes
Yes
Yes
Yes
Yes
Yes
The 8port Fast Ethernet PIC does not support untagged aggregated Ethernet or LACP.
Syslog messages are logged if you try to configure an untagged aggregated Ethernet
interface using an unsupported PIC type.
For more information about configuring LACP, see Configuring LACP for Aggregated
Ethernet Interfaces on page 160.
159
Related
Documentation
For more information about configuring LACP, see Configuring LACP for Aggregated
Ethernet Interfaces on page 160.
NOTE: Starting with Junos OS Release 14.1, you can configure aggregated
Ethernet interfaces with LACP on logical systems within an MX Series router.
For Multichassis Link Aggregation (MC-LAG), you must specify the system-id and admin
key. MC-LAG peers use the same system-id while sending the LACP messages. The
system-id can be configured on the MC-LAG network device and synchronized between
peers for validation.
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.
160
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Automatic addition and deletion of individual links to the aggregate bundle without
user intervention
Link monitoring to check whether both ends of the bundle are connected to the correct
group
The Junos OS implementation of LACP provides link monitoring but not automatic addition
and deletion of links.
The LACP mode can be active or passive. If the actor and partner are both in passive
mode, they do not exchange LACP packets, which results in the aggregated Ethernet
links not coming up. If either the actor or partner is active, they do exchange LACP packets.
By default, LACP is turned off on aggregated Ethernet interfaces. If LACP is configured,
it is in passive mode by default. To initiate transmission of LACP packets and response
to LACP packets, you must configure LACP in active mode.
To enable LACP active mode, include the lacp statement at the [edit interfaces
interface-name aggregated-ether-options] hierarchy level, and specify the active option:
[edit interfaces interface-name aggregated-ether-options]
lacp {
active;
}
NOTE: The LACP process exists in the system only if you configure the system
in either active or passive LACP mode.
If you restart the Link Aggregation Control Protocol (LACP) process
consecutively without adequate sleep or pause time between the successive
restarts, the LACP links might flap. To avoid this problem, you must restart
the LACP process only after the refresh time of the periodic packet
management (PPM) process is completed.
To restore the default behavior, include the lacp statement at the [edit interfaces
interface-name aggregated-ether-options] hierarchy level, and specify the passive option:
[edit interfaces interface-name aggregated-ether-options]
lacp {
passive;
}
Starting with Junos OS Release 12.2, you can also configure LACP to override the IEEE
802.3ad standard and to allow the standby link always to receive traffic. Overriding the
default behavior facilitates subsecond failover.
To override the IEEE 802.3ad standard and facilitate subsecond failover, include the
fast-failover statement at the [edit interfaces interface-name aggregated-ether-options
lacp] hierarchy level.
161
When you configure the accept-data statement at the [edit interfaces aeX
aggregated-ether-options lacp] hierarchy level, the router processes packets received on
a member link irrespective of the LACP state if the aggregated Ethernet bundle is up.
NOTE: When you use the accept-data statement at the [edit interfaces aeX
aggregated-ether-options lacp] hierarchy level, this behavior occurs:
When LACP is down and a member link receives packets, the router does
not process packets as defined in the IEEE 802.1ax standard. According to
this standard, the packets should be dropped, but they are processed
instead because the accept-data statement is configured.
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 receivers rate.
162
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
NOTE: Source address filtering does not work when LACP is enabled. This
behavior is not applicable to T Series routers and PTX Series Packet Transport
Routers. For more information about source address filtering, see Enabling
Ethernet MAC Address Filtering on page 15.
Percentage policers are not supported on aggregated Ethernet interfaces
with the CCC protocol family configured. For more information about
percentage policers, see the Routing Policies, Firewall Filters, and Traffic
Policers Feature Guide for Routing Devices.
Generally, LACP is supported on all untagged aggregated Ethernet interfaces.
For more information, see Configuring Untagged Aggregated Ethernet
Interfaces on page 159.
For M Series Multiservice Edge Routers with enhanced Flexible PIC
Concentrators (FPCs) and T Series routers, LACP over VLAN-tagged
aggregated Ethernet interfaces is supported. For 8-port, 12-port, and 48-port
Fast Ethernet PICs, LACP over VLAN-tagged interfaces is not supported.
LACP Fast Periodic, which is achieved by configuring fast (every second)
intervals for periodic transmission of LACP packets, is supported with graceful
Routing Engine switchover (GRES) on MX Series routers only.
To force active and standby links within an aggregated Ethernet, you can configure LACP
link protection and system priority at the aggregated Ethernet interface level using the
link-protection and system-priority statements. Configuring values at this level results in
only the configured interfaces using the defined configuration. LACP interface
configuration also enables you to override global (chassis) LACP settings.
LACP link protection also uses port priority. You can configure port priority at the Ethernet
interface [gigether-options] hierarchy level using the port-priority statement. If you choose
not to configure port priority, LACP link protection uses the default value for port priority
(127).
163
164
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
The system priority is a 2-octet binary value that is part of the LACP system ID. The LACP
system ID consists of the system priority as the two most-significant octets and the
interface MAC address as the six least-significant octets. The system with the numerically
lower value for system priority has the higher priority. By default, system priority is 127,
with a range of 0 to 65,535.
You must not configure the LACP system identifier by using the system-id system-id
statement at the [edit interfaces aeX aggregated-ether-options lacp] hierarchy level to
be all zeros (00:00:00:00:00:00). If you attempt to commit a configuration with the
system identifier to be all zeros, an error occurs during the commit operation.
The user-defined system identifier in LACP enables two ports from two separate routers
(M Series or MX Series routers) to act as though they were part of the same aggregate
group.
The system identifier is a 48-bit (6-byte) globally unique field. It is used in combination
with a 16-bit system-priority value, which results in a unique LACP system identifier.
The port priority is a 2-octet field that is part of the LACP port ID. The LACP port ID consists
of the port priority as the two most-significant octets and the port number as the two
165
least-significant octets. The system with the numerically lower value for port priority has
the higher priority. By default, port priority is 127, with a range of 0 to 65,535.
Port aggregation selection is made by each system based on the highest port priority
and is assigned by the system with the highest priority. Ports are selected and assigned
starting with the highest priority port of the highest priority system and working down in
priority from there.
You can specify the following flags in the protocols lacp traceoptions statement:
configurationConfiguration code
For general information about tracing, see the tracing and logging information in the
Junos OS Administration Library for Routing Devices.
LACP Limitations
LACP can link together multiple different physical interfaces, but only features that are
supported across all of the linked devices will be supported in the resulting link aggregation
group (LAG) bundle. For example, different PICs can support a different number of
forwarding classes. If you use link aggregation to link together the ports of a PIC that
supports up to 16 forwarding classes with a PIC that supports up to 8 forwarding classes,
the resulting LAG bundle will only support up to 8 forwarding classes. Similarly, linking
166
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
together a PIC that supports WRED with a PIC that does not support it will result in a
LAG bundle that does not support WRED.
[edit interfaces]
fe-5/0/1 {
fastether-options {
802.3ad ae0;
}
}
ae0 {
aggregated-ether-options {
lacp {
active;
}
}
vlan-tagging;
unit 0 {
vlan-id 100;
family inet {
address 10.1.1.2/24 {
vrrp-group 0 {
virtual-address 10.1.1.4;
priority 200;
}
}
}
}
}
[edit interfaces]
fe-5/0/1 {
fastether-options {
802.3ad ae0;
}
}
ae0 {
aggregated-ether-options {
lacp {
active;
}
}
unit 0 {
family inet {
address 10.1.1.2/24 {
vrrp-group 0 {
virtual-address 10.1.1.4;
priority 200;
}
}
}
167
}
}
Related
Documentation
Specify that you want to configure the options for an aggregated Ethernet interface.
user@host# edit interfaces aex aggregated-ether-options
Configuring Primary and Backup Links for Link Aggregated Ethernet Interfaces
To configure link protection, you must specify a primary and a secondary, or backup, link.
168
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Reverting Traffic to a Primary Link When Traffic is Passing Through a Backup Link
On aggregated Ethernet interfaces, you designate a primary and backup link to support
link protection. Egress traffic passes only through the designated primary link. This includes
transit traffic and locally generated traffic on the router or switch. When the primary link
fails, traffic is routed through the backup link. Because some traffic loss is unavoidable,
egress traffic is not automatically routed back to the primary link when the primary link
is reestablished. Instead, you manually control when traffic should be diverted back to
the primary link from the designated backup link.
To manually control when traffic should be diverted back to the primary link from the
designated backup link, enter the following operational command:
user@host> request interface revert aex
169
Related
Documentation
Specify that you want to configure the options for an aggregated Ethernet interface.
user@host# edit interfaces aex aggregated-ether-options
Related
Documentation
MX-Series
Hierarchical scheduler
170
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Prior to Junos OS Release 9.6, the hierarchical scheduler mode on these models required
the aggregated-ether-options statement link-protection option. If a link-protection option
is not specified, the scheduler is configured in non-link-protect mode.
To specify the member link bandwidth derivation based on the equal division model
(scale) or the replication model (replicate) on aggregated Ethernet interfaces, include
the member-link-scheduler (scale | replicate) option at the [edit class-of-service interfaces
aeX] hierarchy level. The default setting is scale.
[edit class-of-service interfaces aeX member-link-scheduler (scale | replicate)]
NOTE: In link-protect mode, only one link is active at a time and the other
link acts as the backup link, whereas in a non link-protect mode, all the links
of the aggregate bundle are active at the same time. There is no backup link.
If a link goes down or a new link is added to the bundle, traffic redistribution
occurs.
Related
Documentation
For more information on the hierarchical scheduler (CoS), see the Class of Service
Feature Guide for Routing Devices.
171
address and destination address. The result of a hash computed on these fields is used
to choose the link of the LAG. The hash-computation for the forward and reverse flow
must be identical. This is achieved by swapping source fields with destination fields for
the reverse flow. The swapped operation is referred to as complement hash computation
or symmetric-hash complement and the regular (or unswapped) operation as
symmetric-hash computation or symmetric-hash. The swappable fields are MAC address,
IP address, and port.
i2
MX-series router
i3
MX-series router
Forward traffic
Reverse traffic
g017349
Intelligent Devices
Router A is configured with symmetric hash and Router B is configured with symmetric
hash complement. Thus, for a given flow fx, post hash computation is from Router A to
Router B through i2. The reverse traffic for the same flow fx is from Router B to Router A
through the same i2 device as its hashing (done after swapping source and destination
fields) and returns the same link index; since it is performed on the interchanged source
and destination addresses.
However, the link chosen may or may not correspond to what was attached to the DPI.
In other words, the hashing result should point to the same links that are 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
172
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
the LAG bundle. This ensures that the link chosen for a given hash result is always the
same on either router.
Note that any two links connected to each other should have the same link index and
these link indices must be unique in a given bundle.
NOTE:
The following restrictions apply when configuring symmetric load balancing
on an 802.3ad LAG on MX Series routers:
The Packet Forwarding Engine (PFE) can be configured to hash the traffic
in either symmetric or complement mode. A single PFE complex cannot
work simultaneously in both operational modes and such a configuration
can yield undesirable results.
The per-PFE setting overrides the chassis-wide setting only for the family
configured. For the other families, the PFE complex still inherits the
chassis-wide setting (when configured) or the default setting.
For additional information, see the Junos OS VPNs Library for Routing Devices and the
Junos OS Administration Library for Routing Devices.
Example Configuration
Statements
173
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. These configuration options are available under the
chassis hierarchy as follows:
[edit chassis]
fpc X {
pic Y {
.
.
.
hash-key {
family inet {
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;]
}
}
}
.
.
.
}
}
174
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
When symmetrical load balancing is enabled on Trio-based MPCs, keep in mind the
following caveats:
Traffic polarization is a phenomenon that occurs when using topologies that distribute
traffic by using hashing of the same type. When routers are cascaded, traffic polarization
can occur, and this can lead to unequal traffic distribution.
175
Traffic polarization occurs when LAGs are configured on cascaded routers. For example,
in Figure 8 on page 176, if a certain flow uses Link 1 of the aggregated Ethernet bundle
between Device R1 and Device R2, the flow also uses Link 1 of the aggregated Ethernet
bundle between Device R2 and Device R3.
R3
2
g041440
1
R1
This is unlike having a random link selection algorithm, where a flow might use Link 1
of the aggregated Ethernet bundle between Device R1 and Device R2, and Link 2 of the
aggregated Ethernet bundle between Device R2 and Device R3.
Symmetric load balancing is not applicable to MPLS or VPLS traffic, because in these
scenarios the labels are not the same in both directions.
Example Configurations
Example Configurations of Chassis Wide Settings
Router A
Router B
176
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
}
}
symmetric hash;
}
Router B
Related
Documentation
For additional information, see the Junos OS VPNs Library for Routing Devices and the
Junos OS Administration Library for Routing Devices.
177
By default, when there are multiple equal-cost paths to the same destination for the
active route, Junos OS uses a hash algorithm to choose one of the next-hop addresses
to install in the forwarding table. Whenever the set of next hops for a destination
changes in any way, the next-hop address is rechosen using the hash algorithm. There
is also an option that allows multiple next-hop addresses to be installed in the
forwarding table, known as per-packet load balancing.
ECMP load balancing can be:
In complex Ethernet topologies, traffic imbalances occur due to increased traffic flow,
and load balancing becomes challenging for some of the following reasons:
As a result of traffic imbalance, the load is not well distributed causing congestion in
certain links, whereas some other links are not efficiently utilized.
To overcome these challenges, Junos OS provides the following solutions for resolving
the genuine traffic imbalance on aggregated Ethernet bundles (IEEE 802.3ad).
To configure the tolerance value as a percentage, include the tolerance optional keyword
at the [edit interfaces aex aggregated-ether-options load-balance adaptive] hierarchy
level.
To configure adaptive load balancing based on packets per second (instead of the
default bits per second setting), include the pps optional keyword at the [edit interfaces
aex aggregated-ether-options load-balance adaptive] hierarchy level.
178
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
To configure the scan interval for the hash value based on the sample rate for the last
two seconds, include the scan-interval optional keyword at the [edit interfaces aex
aggregated-ether-options load-balance adaptive] hierarchy level.
NOTE: The pps and scan-interval optional keywords are supported on PTX
Series Packet Transport Routers only.
NOTE: The Per-Packet option for load balancing is not supported on PTX
Series Packet Transport Routers.
The aggregated Ethernet load-balancing solutions are mutually exclusive. When more
than one of the load-balancing solutions is configured, the solution that is configured
last overrides the previously configured one. You can verify the load-balancing solution
being used by issuing the show interfaces aex aggregated-ether-options load-balance
command.
Related
Documentation
179
In complex Ethernet topologies, traffic imbalances occur due to increased traffic flow,
and load balancing becomes challenging for some of the following reasons:
180
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
As a result of traffic imbalance, the load is not well distributed causing congestion in
certain links, whereas some other links are not efficiently utilized.
To overcome these challenges, Junos OS provides the following solutions for resolving
the genuine traffic imbalance on aggregated Ethernet bundles (IEEE 802.3ad).
To configure the tolerance value as a percentage, include the tolerance optional keyword
at the [edit interfaces aex aggregated-ether-options load-balance adaptive] hierarchy
level.
To configure adaptive load balancing based on packets per second (instead of the
default bits per second setting), include the pps optional keyword at the [edit interfaces
aex aggregated-ether-options load-balance adaptive] hierarchy level.
To configure the scan interval for the hash value based on the sample rate for the last
two seconds, include the scan-interval optional keyword at the [edit interfaces aex
aggregated-ether-options load-balance adaptive] hierarchy level.
NOTE: The pps and scan-interval optional keywords are supported on PTX
Series Packet Transport Routers only.
NOTE: The Per-Packet option for load balancing is not supported on PTX
Series Packet Transport Routers.
181
The aggregated Ethernet load-balancing solutions are mutually exclusive. When more
than one of the load-balancing solutions is configured, the solution that is configured
last overrides the previously configured one. You can verify the load-balancing solution
being used by issuing the show interfaces aex aggregated-ether-options load-balance
command.
Requirements
This example uses the following hardware and software components:
Three MX Series routers with MIC and MPC interfaces or three PTX Series Packet
Transport Routers with PIC and FPC interfaces
Overview
Load balancing is required on the forwarding plane when there are multiple paths or
interfaces available to the next hop router, and it is best if the incoming traffic is load
balanced across all available paths for better link utilization.
Aggregated Ethernet bundle is a typical application that uses load balancing to balance
traffic flows across the member links of the bundle (IEEE 802.3ad).
Starting with Junos OS Release 13.3, aggregated Ethernet load balancing is enhanced to
provide two solutions for resolving genuine traffic imbalance on aggregated Ethernet
bundles on MICs or MPCs of MX Series routers. Starting with Junos OS Release 14.1,
aggregated Ethernet load balancing is enhanced to provide two solutions for resolving
genuine traffic imbalance on aggregated Ethernet bundles on PICs or FPCs of PTX Series
Packet Transport Routers.
The aggregated Ethernet load-balancing solutions are:
182
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
feedback loop, which over a period of time ensures that the same amount of byte rate
is offered to all the member links, thus providing efficient traffic distribution across
each member link in the AE bundle.
To configure adaptive load balancing, include the adaptive statement at the [edit
interfaces aex aggregated-ether-options load-balance] hierarchy level.
The pps option enables load balancing based on the packets-per-second rate. The
default setting is bits-per-second load balancing.
The scan-interval value configures the length of time for scanning as a multiple of 30
seconds.
The tolerance value is the limit to the variance in the packet traffic flow to the
aggregated Ethernet links in the bundle. You can specify a maximum of 100-percent
variance. When the tolerance attribute is not configured, a default value of 20 percent
is enabled for adaptive load balancing. A smaller tolerance value balances better
bandwidth, but takes a longer convergence time.
NOTE: The pps and scan-interval optional keywords are supported on PTX
Series Packet Transport Routers only.
NOTE: The Per-Packet option for load balancing is not supported on the
PTX Series Packet Transport Routers.
The aggregated Ethernet load-balancing solutions are mutually exclusive. When more
than one of the load-balancing solutions is configured, the solution that is configured
last overrides the previously configured one. You can verify the load-balancing solution
being implemented by issuing the show interfaces aex aggregated-ether-options
load-balance command.
183
Topology
In this topology, two aggregated Ethernet bundles - ae0 and ae1 - are configured on the
links between the R2 and R3 routers.
Configuration
CLI Quick
Configuration
R1
184
To quickly configure this example, copy the following commands, paste them into a text
file, remove any line breaks, change any details necessary to match your network
configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy
level.
set chassis aggregated-devices ethernet device-count 12
set interfaces xe-0/0/0 unit 0 family inet address 120.168.1.1/30
set interfaces xe-0/0/0 unit 0 family iso
set interfaces xe-0/0/0 unit 0 family mpls
set interfaces xe-0/0/1 unit 0 family inet address 120.168.2.1/30
set interfaces xe-0/0/1 unit 0 family iso
set interfaces xe-0/0/1 unit 0 family mpls
set interfaces ge-1/0/0 unit 0 family inet address 120.168.100.2/30
set interfaces ge-1/0/0 unit 0 family iso
set interfaces ge-1/0/0 unit 0 family mpls
set interfaces ge-1/0/1 unit 0 family inet address 120.168.101.2/30
set interfaces ge-1/0/1 unit 0 family iso
set interfaces ge-1/0/1 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 120.168.0.2/32
set interfaces lo0 unit 0 family iso address 49.0001.1201.6800.0002.00
set routing-options router-id 120.168.0.2
set routing-options autonomous-system 55
set protocols rsvp interface ge-1/0/0.0
set protocols rsvp interface ge-1/0/1.0
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
185
186
R2
R3
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
187
The following example requires you to navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode.
To configure the R2 router:
NOTE: Repeat this procedure for the other routers, after modifying the
appropriate interface names, addresses, and any other parameters for each
router.
1.
2.
3.
188
Configure the five member links of the ae0 aggregated Ethernet bundle.
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
[edit interfaces]
user@R2# set ge-1/3/0 gigether-options 802.3ad ae0
user@R2# set ge-1/3/1 gigether-options 802.3ad ae0
user@R2# set ge-1/3/2 gigether-options 802.3ad ae0
user@R2# set ge-1/3/3 gigether-options 802.3ad ae0
user@R2# set ge-1/3/4 gigether-options 802.3ad ae0
4.
Configure the eight member links of the ae1 aggregated Ethernet bundle.
[edit interfaces]
user@R2# set ge-2/2/1 gigether-options 802.3ad ae1
user@R2# set ge-2/2/2 gigether-options 802.3ad ae1
user@R2# set ge-2/2/3 gigether-options 802.3ad ae1
user@R2# set ge-2/2/4 gigether-options 802.3ad ae1
user@R2# set ge-2/2/5 gigether-options 802.3ad ae1
user@R2# set ge-2/2/6 gigether-options 802.3ad ae1
user@R2# set ge-2/2/7 gigether-options 802.3ad ae1
user@R2# set ge-2/2/8 gigether-options 802.3ad ae1
5.
6.
Configure the link speed for the ae0 aggregated Ethernet bundle.
[edit interfaces]
user@R2# set ae0 aggregated-ether-options link-speed 1g
7.
8.
Configure the interface parameters for the ae0 aggregated Ethernet bundle.
[edit interfaces]
user@R2# set ae0 unit 0 family inet address 120.168.104.1/30
user@R2# set ae0 unit 0 family iso
user@R2# set ae0 unit 0 family mpls
9.
10.
Configure the link speed for the ae1 aggregated Ethernet bundle.
[edit interfaces]
user@R2# set ae1 aggregated-ether-options link-speed 1g
11.
12.
Configure the interface parameters for the ae1 aggregated Ethernet bundle.
[edit interfaces]
user@R2# set ae1 unit 0 family inet address 120.168.105.1/30
user@R2# set ae1 unit 0 family iso
user@R2# set ae1 unit 0 family mpls
189
13.
14.
15.
16.
Results
From configuration mode, confirm your configuration by entering the show chassis, show
interfaces, show accounting-options, and show protocols commands. If the output does
not display the intended configuration, repeat the instructions in this example to correct
the configuration.
user@R2# show chassis
aggregated-devices {
ethernet {
device-count 5;
}
}
user@R2# show interfaces
ge-1/2/0 {
unit 0 {
family inet {
address 120.168.100.1/30;
}
family iso;
family mpls;
}
}
ge-1/2/1 {
unit 0 {
190
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
family inet {
address 120.168.101.1/30;
}
family iso;
family mpls;
}
}
ge-1/3/0 {
gigether-options {
802.3ad ae0;
}
}
ge-1/3/1 {
gigether-options {
802.3ad ae0;
}
}
ge-1/3/2 {
gigether-options {
802.3ad ae0;
}
}
ge-1/3/3 {
gigether-options {
802.3ad ae0;
}
}
ge-1/3/4 {
gigether-options {
802.3ad ae0;
}
}
ge-2/2/1 {
gigether-options {
802.3ad ae1;
}
}
ge-2/2/2 {
gigether-options {
802.3ad ae1;
}
}
ge-2/2/3 {
gigether-options {
802.3ad ae1;
}
}
ge-2/2/4 {
gigether-options {
802.3ad ae1;
}
}
ge-2/2/5 {
gigether-options {
802.3ad ae1;
}
191
}
ge-2/2/6 {
gigether-options {
802.3ad ae1;
}
}
ge-2/2/7 {
gigether-options {
802.3ad ae1;
}
}
ge-2/2/8 {
gigether-options {
802.3ad ae1;
}
}
ae0 {
aggregated-ether-options {
load-balance {
adaptive tolerance 10;
}
link-speed 1g;
lacp {
active;
}
}
unit 0 {
family inet {
address 120.168.104.1/30;
}
family iso;
family mpls;
}
}
ae1 {
aggregated-ether-options {
load-balance {
adaptive tolerance 10;
}
link-speed 1g;
lacp {
active;
}
}
unit 0 {
family inet {
address 120.168.105.1/30;
}
family iso;
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 120.168.0.4/32;
192
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
}
family iso {
address 49.0001.1201.6800.0004.00;
}
}
}
user@R2# show accounting-options
selective-aggregate-interface-stats disable;
user@R2# show protocols
rsvp {
interface ge-1/2/0.0;
interface ge-1/2/1.0;
interface ae0.0;
interface ae1.0;
}
mpls {
interface ge-1/2/0.0;
interface ge-1/2/1.0;
interface ae0.0;
interface ae1.0;
}
isis {
traffic-engineering {
family inet {
shortcuts;
}
}
level 1 disable;
interface ge-1/2/0.0;
interface ge-1/2/1.0;
interface ae0.0;
interface ae1.0;
interface lo0.0;
}
Verification
Confirm that the configuration is working properly.
Verify that packets received on the ae0 aggregated Ethernet bundle are load-balanced
among the five member links.
193
Action
From operational mode, run the show interfaces ae0 extensive command.
user@R2> show interfaces ae0 extensive
Logical interface ae0.0 (Index 325) (SNMP ifIndex 917) (Generation 134)
Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2
Statistics
Packets
pps
Bytes
bps
Bundle:
Input :
848761
9
81247024
7616
Output: 166067308909
3503173 126900990064983 21423804256
Adaptive Statistics:
Adaptive Adjusts:
264
Adaptive Scans :
27682
Adaptive Updates:
10
Link:
ge-1/3/0.0
Input :
290888
5
29454436
3072
Output:
33183442699
704569 25358563587277
4306031760
ge-1/3/1.0
Input :
162703
1
14806325
992
Output:
33248375409
705446 25406995966732
4315342152
ge-1/3/2.0
Input :
127448
1
12130566
992
Output:
33184552729
697572 25354827700261
4267192376
ge-1/3/3.0
Input :
121044
1
11481262
1280
Output:
33245875402
697716 25405953405192
4265750584
ge-1/3/4.0
Input :
146678
1
13374435
1280
Output:
33205071207
697870 25374651121458
4269487384
Meaning
194
The member links of the ae0 aggregated Ethernet bundle are fully utilized with adaptive
load balancing.
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Stateful Load Balancing for Aggregated Ethernet Interfaces Using 5-Tuple Data
When multiple flows are transmitted out of an aggregated Ethernet (ae) interface, the
flows must be distributed across the different member links evenly to enable an effective
and optimal load-balancing behavior. To obtain a streamlined and robust method of
load-balancing, the member link of the aggregated Ethernet interface bundle that is
selected each time for load balancing plays a significant part. In Junos OS releases earlier
than Release 13.2R1, on MX Series routers with Trio-based FPCs (MPCs), the selection
of a member link of the ae interface bundle or the next-hop (or unilist of next-hops) for
equal-cost multipath ECM) links is performed using a balanced mode next-hop selection
methodology and an unbalanced mode of member link or next-hop selection
methodology. The balanced mode of link selection uses 'n' bits in a precomputed hash
value if it needs to select one of 2^n (2 raised to the power of n) next-hop in the unilist.
The unbalanced mode of member-link or next-hop selection uses 8 bits in a precomputed
hash to select an entry in a selector table, which is randomly done with the member link
IDs of the link aggregation group (LAG) or aebundle.
The term balanced versus unbalanced indicates whether a selector table is used for load
balancing mechanism or not. The LAG bundle uses the unbalanced mode (selector table
balancing) to balance the traffic across member links. When the traffic flows are minimal,
the following problems might occur with the unbalanced mode: The link selection logic
utilizes only subset bits of the precomputed hash. Regardless of the efficiency of the
hashing algorithm, it is only the compressed representation of a flow. Because the
inter-flow variance is very low, the resultant hashes and the subset that are computed
do not provide the necessary variability to effectively utilize all the LAG member links.
An excessive amount of random nature exists in the hash computation and also in the
selector table. As a result, the deviation from being an optimal load-balancing technique
for each child link that is selected is higher when the number of flows is lower.
The deviation per child link is defined as
Vi = ((Ci - (M/N)))/N
where
Because of these drawbacks, for smaller number of flows, or flows with less inter-flow
variance, the link utilization is skewed, and a high probability of a few child links not being
utilized entirely exists. Starting with Junos OS Release 13.2R1, the capability to perform
uniform load balancing and also perform rebalancing is introduced on MX Series routers
with MPCs, except MPC3Es and MPC4Es. Rebalancing is not supported when
load-balancing is skewed or distorted owing to a change in the number of flows.
195
The mechanism to record and retain states for the flows and distribute the traffic load
accordingly is added. As a result, for m number of flows, they are distributed among n
member links of a LAG bundle or among the unilist of next-hops in an ECMP link. This
method of splitting the load among member links is called stateful load balancing and it
uses 5-tuple information (source and destination addresses, protocol, source and
destination ports). Such a method can be mapped directly to the flows, or to a precompute
hash based on certain fields in the flow. As a result, the deviation observed on each child
link is reduced.
This mechanism works efficiently only for minimal number of flows (less than thousands
of flows, approximately). For a larger number of flows (between 1000 and 10,000 flows),
we recommend that distributed Trio-based load-balancing mechanism is used.
Consider a sample scenario in which 'n' links in the LAG are identified with link IDs of 0
through n-1. A hash table or a flow table is used to record the flows as and when they
show up. The hashing key is constructed using the fields that uniquely identify a flow.
The result of the lookup identifies the link_id that the flow is currently using. For each
packet, the flow table based on the flow identifier is examined. If a match is found, it
denotes a packet that belongs to a flow that is previously processed or detected. The
link ID is associated with the flow. If a match is not found, it is the first packet that belongs
to the flow. The link ID is used to select the link and the flow is inserted into the flow
table.
To enable per-flow load balancing based on hash values, include the per-flow statement
at the at the [edit interfaces aeX unit logical-unit-number forwarding-options
load-balance-stateful] hierarchy level. By default, Junos OS uses a hashing method based
only on the destination address to elect a forwarding next hop when multiple equal-cost
paths are available. All Packet Forwarding Engine slots are assigned the same hash value
by default. To configure the load-balancing algorithm to dynamically rebalance the LAG
using existing parameters, include the rebalance interval statement at the [edit interfaces
aeX unit logical-unit-number forwarding-options load-balance-stateful] hierarchy level.
This parameter periodically load balances traffic by providing a synchronized rebalance
switchover across all the ingress Packet Forwarding Engines (PFEs) over a rebalance
interval. You can specify the interval as a value in the range of 1 through 1000 flows per
minute. To configure the load type, include the load-type (low | medium | high) statement
at the [edit interfaces aeX unit logical-unit-number forwarding-options
load-balance-stateful] hierarchy level.
The stateful per-flow option enables the load-balancing capability on AE bundles. The
rebalance option clears the load balance state at specified intervals. The load option
informs the Packet Forwarding Engine regarding the appropriate memory pattern to be
used. If the number of flows that flow on this aggregated Ethernet interface is less
(between 1 and 100 flows), then the low keyword can be used. Similarly for relatively
higher flows (between 100 and 1000 flows), the medium keyword can be used and the
large keyword can be used for the maximum flows (between 1000 and 10,000 flows).
The approximate number of flows for effective load-balancing for each keyword is a
derivative.
The clear interfaces aeX unit logical-unit-number forwarding-options load-balance state
command clears the load balance state at the hardware level and enables rebalancing
196
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
from the cleaned up, empty state. This clear state is triggered only when you use this
command. The clear interfaces aggregate forwarding-options load-balance state command
clears all the aggregate Ethernet interface load balancing states and re-creates them
newly.
Guidelines for Configuring Stateful Load Balancing for Aggegated Ethernet Interfaces or LAG
Bundles
Keep the following points in mind while configuring stateful load-balancing for aggregated
Ethernet interfaces:
When a child link is removed or added, a new aggregate selector is selected and traffic
flows onto the new selector. Because the selector is empty, flows are filled in the
selector. This behavior causes redistribution of flows because the old state is lost. This
is the existing behavior without enabling stateful per-flow load-balancing.
Related
Documentation
Enabling the rebalance option or clearing the load balance state can cause packet
reordering for active flows because different sets of links can be selected for traffic
flows.
Although the feature performance is high, it consumes significant amount of line card
memory. Approximately, 4000 logical interfaces or 16 aggregated Ethernet logical
interfaces can have this feature enabled on supported MPCs. However, when the
Packet Forwarding Engine hardware memory is low, depending upon the available
memory, it falls back to the default load balancing mechanism. A system logging
message is generated in such a situation and sent to the Routing Engine. A restriction
on the number of AE interfaces that support stateful load-balancing does not exist;
the limit is determined by the line cards.
If the traffic flows become aged frequently, then the device needs to remove or refresh
the load balancing states. As a result, you must configure rebalancing or run the clear
command at periodic intervals for proper load-balancing. Otherwise, traffic skewing
can occur. When a child link goes down or comes up, the load balancing behavior does
not undergo changes on existing flows. This condition is to avoid packet reordering.
New flows pick up the child link that come up. If you observe load distribution to be
not very effective, you can clear the load-balancing states or use rebalancing
functionality to cause an automatic clearance of the hardware states. When you
configure the rebalancing facility, traffic flows can get redirected to different links,
which can cause packet reordering.
197
appropriate memory pattern to be used for traffic flows. The approximate number of
flows for effective load-balancing for each keyword is a derivative.
[edit interfaces aeX unit logical-unit-number load-balance-stateful]
user@R2# set load-type (low | medium | large)
6. Configure the address family and IP address for the ae interface.
[edit interfaces]
user@R2# set ae0 aggregated-ether-options load-balance adaptive tolerance 10
7. Configure the link speed for the ae0 aggregated Ethernet bundle.
Related
Documentation
198
Stateful Load Balancing for Aggregated Ethernet Interfaces Using 5-Tuple Data on
page 195
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Configure a set of interfaces with a protocol family and IP address. These interfaces
can make up the membership for the AE bundle.
2. Configure the scan interval value for adaptive load balancing on the AE bundle. The
scan interval value determines the length of the traffic scan by multiplying the integer
value with a 30-second time period:
[edit interfaces ae-x aggregated-ether-options load-balance adaptive]
user@router# set scan-interval multiplier
3. Configure the tolerance percentage value. The tolerance value determines the allowed
deviation in the traffic rates among the members of the AE bundle before the router
triggers an adaptive load balancing update:
[edit interfaces ae-x aggregated-ether-options load-balance adaptive]
user@router# set tolerance percentage
4. (Optional) Enable packet-per-second-based adaptive load balancing on the AE
bundle:
[edit interfaces ae-x aggregated-ether-options load-balance adaptive]
user@router# set pps
Related
Documentation
199
200
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Starting with Junos OS Release 13.3, this feature is supported on the following PIC/FPC
types:
All FPCs on PTX Series with Ethernet interfaces in Junos OS Release 14.1R3 and later
14.1 releases, and Junos OS Release 14.2 and later
TIP: See PTX Series PIC/FPC Compatibility for a list of PICs that are supported
on each PTX Series FPC.
201
Non-Distribution ModeYou can configure the BFD session to run in this mode by
including the no-delegate-processing statement under periodic packet management
(PPM). In this mode the packets are being sent or received by the Routing Engine at
Layer 2.
A pair of routing devices in a LAG exchange BFD packets at a specified, regular interval.
The routing device detects a neighbor failure when it stops receiving a reply after a
specified interval. This allows the quick verification of member link connectivity with or
without LACP. A UDP port distinguishes BFD over LAG packets from BFD over single-hop
IP.
NOTE: IANA has allocated 6784 as the UDP destination port for micro BFD.
To enable failure detection for LAG networks for aggregated Ethernet interfaces:
Specify a hold-down interval value to set the minimum time that the BFD session must
remain up before a state change notification is sent to the other members in the LAG
network.
Specify the minimum interval that indicates the time interval for transmitting and
receiving data.
Specify the neighbor in a BFD session. The neighbor address can be either an IPv4 or
an IPv6 address.
NOTE: This feature works only when both the devices support BFD. If BFD is
configured at one end of the LAG, this feature does not work.
Related
Documentation
202
authentication
detection-time
transmit-interval
Example: Configuring Independent Micro BFD Sessions for LAG on page 203
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Requirements
This example uses the following hardware and software components:
Overview
The example includes two routers that are directly connected. Configure two aggregated
Ethernet interfaces AE0 and AE1 that are assigned four and two IP addresses respectively.
Configure BFD sessions on the aggregated Ethernet interfaces on both ends of the
connection. This example verifies that independent micro BFD sessions are active in the
output.
Topology
Figure 10 on page 203 shows the sample topology.
Configuration
CLI Quick
Configuration
Router R0
To quickly configure this example, copy the following commands, paste them into a text
file, remove any line breaks, change any details necessary to match your network
configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy
level.
set interfaces ge-1/0/1 unit 0 family inet address 20.20.20.1/30
set interfaces ge-1/0/1 unit family inet6 address 3ffe::1:1/126
set interfaces xe-4/0/0 gigether-options 802.3ad ae0
set interfaces xe-4/0/1 gigether-options 802.3ad ae0
set interfaces xe-4/1/0 gigether-options 802.3ad ae1
set interfaces xe-4/1/1 gigether-options 802.3ad ae1
set lo0 unit 0 family inet address 10.255.106.107/32
203
Router R1
204
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
The following example requires that you navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
NOTE: Repeat this procedure for Router R1, modifying the appropriate
interface names, addresses, and any other parameters for each router.
To configure micro BFD session for aggregated Ethernet interfaces on Router R0:
1.
2.
205
3.
Configure four IP addresses on the aggregated Ethernet interface ae0 with either
IPv4 or IPv6 addresses, as per your network requirements.
[edit interfaces]
user@R0# set ae0 unit 0 family inet address 10.0.0.1/30
user@R0# set ae0 unit 0 family inet address 10.0.0.5/30
user@R0# set ae0 unit 0 family inet address 10.0.0.9/30
user@R0# set ae0 unit 0 family inet address 10.0.0.13/30
user@R0# set ae0 unit 0 family inet6 address 1111::1/126
user@R0# set ae0 unit 0 family inet6 address 2222::1/126
user@R0# set ae0 unit 0 family inet6 address 3333::1/126
user@R0# set ae0 unit 0 family inet6 address 4444::1/126
4.
Set the routing option, create a static route, and set the next-hop address.
NOTE: You can configure either an IPv4 or IPv6 static route depending
on your network requirements.
[edit routing-options]
user@R0# set nonstop-routing
user@R0# set static route 30.30.30.0/30 next-hop 10.0.0.2
user@R0# set static route 3ffe::1:2/126 next-hop 1111::2
5.
6.
Configure BFD for the aggregated Ethernet interface ae0 and specify the minimum
interval, local IP address, and the neighbor IP address.
[edit interfaces]
user@R0# set ae0 aggregated-ether-options bfd-liveness-detection
minimum-interval 100
user@R0# set ae0 aggregated-ether-options bfd-liveness-detection neighbor
10.255.106.102
user@R0# set ae0 aggregated-ether-options bfd-liveness-detection local-address
10.255.106.107
user@R0# set ae0 aggregated-ether-options minimum-links 1
user@R0# set ae0 aggregated-ether-options link-speed 10g
7.
8.
206
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Results
From configuration mode, enter the show interfaces, show protocols, and show
routing-options commands and confirm your configuration. If the output does not display
the intended configuration, repeat the instructions in this example to correct the
configuration.
user@R0> show interfaces
traceoptions {
flag bfd-events;
}
ge-1/0/1 {
unit 0 {
family inet {
address 20.20.20.1/30;
}
family inet6 {
address 3ffe::1:1/126;
}
}
}
xe-4/0/0 {
enable;
gigether-options {
802.3ad ae0;
}
}
xe-4/0/1 {
gigether-options {
802.3ad ae0;
}
}
xe-4/1/0 {
enable;
gigether-options {
802.3ad ae1;
}
}
207
xe-4/1/1 {
gigether-options {
802.3ad ae1;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.106.107/32;
}
family inet6 {
address 201:DB8:251::aa:aa:1/128;
}
}
}
ae0 {
aggregated-ether-options {
bfd-liveness-detection {
minimum-interval 100;
neighbor 10.255.106.102;
local-address 10.255.106.107;
}
minimum-links 1;
link-speed 10g;
lacp {
active;
}
}
unit 0 {
family inet {
address 10.0.0.1/30;
address 10.0.0.5/30;
address 10.0.0.9/30;
address 10.0.0.13/30;
}
family inet6 {
address 1111::1/126;
address 2222::1/126;
address 3333::1/126;
address 4444::1/126;
}
}
}
ae1 {
aggregated-ether-options {
bfd-liveness-detection {
minimum-interval 100;
multiplier 3;
neighbor 201:DB8:251::bb:bb:1;
local-address 201:DB8:251::aa:aa:1;
}
minimum-links 1
link-speed 10g;
}
unit 0 {
family inet {
208
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
address 50.0.0.1/30;
address 51.0.0.1/29;
}
family inet6 {
address 5555::1/126;
address 6666::1/126;
}
}
}
user@R0> show protocols
bfd {
traceoptions {
file bfd size 100m files 10;
flag all;
}
}
user@R0> show routing-options
nonstop-routing ;
rib inet6.0 {
static {
route 3ffe:1:2/126 {
next-hop 1111::2;
}
}
}
static {
route 30.30.30.0/30 {
next-hop 10.0.0.2;
}
}
Verification
Confirm that the configuration is working properly.
Verify that the micro BFD sessions are up, and view details about the BFD sessions.
209
Action
From operational mode, enter the show bfd session extensive command
user@R0> show bfd session extensive
Address
10.255.106.102
State
Up
Detect
Transmit
Interface
Time
Interval Multiplier
xe-4/0/0
9.000
3.000
3
Address
10.255.106.102
State
Up
Detect
Transmit
Interface
Time
Interval Multiplier
xe-4/0/1
9.000
3.000
3
210
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
Detect
Transmit
Address
State
Interface
Time
Interval Multiplier
201:DB8:251::bb:bb:1
UP
xe-4/1/0
9.000
3.000
3
Client LACPD, TX interval 0.100, RX interval 0.100
Session up time 4d 23:13
Local diagnostic None, remote diagnostic None
Remote not heard, hears us, version 1
Replicated
Session type: Micro BFD
Min async interval 0.100, min slow interval 1.000
Adaptive async TX interval 0.100, RX interval 0.100
Local min TX interval 1.000, minimum RX interval 0.100, multiplier 3
Remote min TX interval 3.000, min RX interval 3.000, multiplier 3
Local discriminator 16, remote discriminator 66
Echo mode disabled/inactive, no-absorb, no-refresh
Remote is control-plane independent
Session ID: 0x0
4 sessions, 4 clients
Cumulative transmit rate 2.0 pps, cumulative receive rate 1.7 pps
Meaning
The Micro BFD field represents the independent micro BFD sessions running on the links
in a LAG. The TX interval [item], RX interval [item] output represents the setting
configured with the minimum-interval statement. All of the other output represents the
default settings for BFD. To modify the default settings, include the optional statements
under bfd-liveness-detection statement.
View the contents of the BFD trace file to assist in troubleshooting, if required.
From operational mode, enter the file show /var/log/bfd command.
user@R0> file show /var/log/bfd
Jun 5 00:48:59
Protocol (1) len 1: BFD
Jun 5 00:48:59
Data (9) len 41: (hex) 42 46 44 20 6e 65 69 67 68 62 6f 72 20
31 30 2e 30 2e 30
Jun 5 00:48:59 PPM Trace: BFD neighbor 10.255.106.102 (IFL 349) set, 9 0
Jun 5 00:48:59 Received Downstream RcvPkt (19) len 108:
Jun 5 00:48:59
IfIndex (3) len 4: 329
Jun 5 00:48:59
Protocol (1) len 1: BFD
Jun 5 00:48:59
SrcAddr (5) len 8: 10.255.106.102
Jun 5 00:48:59
Data (9) len 24: (hex) 00 88 03 18 00 00 00 4b 00 00 00 15 00
2d c6 c0 00 2d c6
Jun 5 00:48:59
PktError (26) len 4: 0
Jun 5 00:48:59
RtblIdx (24) len 4: 0
Jun 5 00:48:59
MultiHop (64) len 1: (hex) 00
Jun 5 00:48:59
Unknown (168) len 1: (hex) 01
Jun 5 00:48:59
Unknown (171) len 2: (hex) 02 3d
Jun 5 00:48:59
Unknown (172) len 6: (hex) 80 71 1f c7 81 c0
Jun 5 00:48:59
Authenticated (121) len 1: (hex) 01
Jun 5 00:48:59 BFD packet from 10.0.0.2 (IFL 329), len 24
Jun 5 00:48:59
Ver 0, diag 0, mult 3, len 24
Jun 5 00:48:59
Flags: IHU Fate
Jun 5 00:48:59
My discr 0x0000004b, your discr 0x00000015
Jun 5 00:48:59
Tx ivl 3000000, rx ivl 3000000, echo rx ivl 0
Jun 5 00:48:59 [THROTTLE]bfdd_rate_limit_can_accept_pkt: session 10.255.106.102
211
Meaning
Related
Documentation
authentication
detection-time
To display multicast statistics, use the show interfaces interface-name statistics detail
command.
Related
Documentation
212
multicast-statistics
Chapter 8: Configuring Aggregated Ethernet Interfaces for Increased Throughput and Link Redundancy
You can delete an aggregated Ethernet interface from the interface configuration. The
Junos OS removes the configuration statements related to aex and sets this interface
to down state.
You can also permanently remove the aggregated Ethernet interface from the device
configuration by deleting it from the device-count on the routing device.
[edit]
user@host# delete chassis aggregated-devices ethernet device-count
Related
Documentation
Configuring the Number of Aggregated Ethernet Interfaces on the Device on page 154
213
Related
Documentation
214
CHAPTER 9
215
NOTE: The configuration on both the provider edge (PE) routers have to be
either in revertive mode or non-revertive mode.
MPLS Core
PE1
PE2
Customer site A
Attachment
circuit
CE2
Customer site B
G.8031
g017516
CE1
Attachment
circuit
In the scenario diagramed in Figure 11 on page 216, a Virtual Private Wire Service (VPWS)
is provisioned between customer sites A and B using a single pseudowire (layer 2 circuit)
in the core network, and two Multiprotocol Label Switching (MPLS) Label Switched
Paths (LSPs) are provisioned, one for the working path and the other one for the protection
216
path. CFM CCM will be used to monitor the status of each LSP. Provider edge routers PE1
and PE2 run G.8031 Ethernet APS to select one of the LSPs as the active path. Once the
active path is elected at the source end of the protection group, PE1 forwards to traffic
from site A to the elected active path. At the sink end of the protection group, PE2
implements a merging selector, meaning it forwards the traffic coming from both the
LSPs to the customer site B.
Attachment
circuit
PE1
MTU
Customer site A
Attachment
circuit
CE2
Customer site B
G.8031
g017517
PE3
recovers. The revert-time statement specifies how much time should elapse before the
path for data should be switched from Protection to Working once recovery for Working
has occurred. A revert-time of zero indicates no reversion. It will default to 300 sec (5
minutes) if not configured.
hold-time- Once a failure is detected, APS waits until this timer expires before initiating
the protection switch. The range of the hold-time timer is 0 to 10,000 milliseconds. It
will default to zero if not configured.
217
Interface down
CCM expiry
DegradedThe monitored path is declared degraded if any of the following MEP defects
occur:
FRR on
FRR-ACK on
UpThe monitored path is declared up in the absence of any of the above events.
Up
Working
Down
Degraded
APS
Event
Generator
Up
Down
Degraded
g017520
Protection
As show in Figure 13 on page 218, the APS event generator generates the following APS
events based on the status of the working and protection paths:
218
Related
Documentation
Requirements
This example uses the following hardware and software components:
2 MX Series PE routers
MPLS Core
PE1
PE2
Customer site A
Attachment
circuit
CE2
Customer site B
G.8031
g017516
CE1
Attachment
circuit
The following definitions describe the meaning of the device abbreviations used in
Figure 14 on page 219.
Customer edge (CE) deviceA device at the customer site that provides access to the
service providers VPN over a data link to one or more provider edge (PE) routers.
Provider edge (PE) deviceA device, or set of devices, at the edge of the provider
network that presents the provider's view of the customer site.
Configuration
Step-by-Step
Procedure
219
protocols {
protection-group {
ethernet-aps {
profile-1 {
protocol g8031;
hold-time 1000s;
revert-time 5m;
}
}
}
2.
3.
4.
Results
220
}
}
ethernet {
oam {
connectivity-fault-management {
maintenance-domain md1 {
level 5;
maintenance-association W {
protect maintenance-association P {
aps-profile profile-1;
}
continuity-check {
interval 1s;
}
mep 100 {
interface ge-1/0/0.0 working;
direction down;
auto-discovery;
}
}
maintenance-association P {
continuity-check {
interval 1s;
}
mep 100 {
interface ge-1/0/0.0 protect;
direction down;
auto-discovery;
}
}
}
}
}
}
Related
Documentation
221
222
CHAPTER 10
223
Bridge Domains with the Ring Port (MX Series Routers Only) on page 229
Acronyms
The following acronyms are used in the discussion about Ethernet ring protection switching
(ERPS):
224
MAMaintenance association
Chapter 10: Configuring Ethernet Ring Protection Switching for High Availability
WTBWait to block
WTRWait to restore
Ring Nodes
Multiple nodes are used to form a ring. There are two different node types:
RPL owner nodeThe node owns the RPL and blocks or unblocks traffic over the RPL.
idleNo failure on the ring; the node is performing normally. For a normal node, traffic
is unblocked on both ring ports. For the RPL owner or RPL neighbor, traffic is blocked
on the ring port that connects to the RPL and unblocked on the other ring port.
protectionA failure occurred on the ring. For a normal node, traffic is blocked on the
ring port that connects to the failing link and unblocked on working ring ports. For the
RPL owner, traffic is unblocked on both ring ports if they connect to non-failure links.
pendingThe node is recovering from failure or its state after a clear command is used
to remove the previous manual command. When a protection group is configured, the
node enters the pending state. When a node is in pending state, the WTR or WTB timer
will be running. All nodes are in pending state till WTR or WTB timer expiry.
force switchA force switch is issued. When a force switch is issued on a node in the
ring all nodes in the ring will move into the force switch state.
manual switchA manual switch is issued. When a manual switch is issued on a node
in the ring all nodes in the ring will move into the manual switch state.
There can be only one RPL owner for each ring. The user configuration must guarantee
this, because the APS protocol cannot check this.
Failure Detection
Ethernet ring operation depends on quick and accurate failure detection. The failure
condition signal failure (SF) is supported. For SF detection, an Ethernet continuity check
MEP must be configured for each ring link. For fast protection switching, a 10-ms
transmission period for this MEP group is supported. OAM monitors the MEP group's MA
and reports SF or SF clear events to the Ethernet ring control module. For this MEP group,
225
the action profile must be configured to update the interface device IFF_LINKDOWN flag.
OAM updates the IFF_LINKDOWN flag to notify the Ethernet ring control module.
Logical Ring
You can define multiple logical-ring instances on the same physical ring. The logical ring
feature currently supports only the physical ring, which means that two adjacent nodes
of a ring must be physically connected and the ring must operate on the physical interface,
not the VLAN. Multiple ring instances are usually defined with trunk mode ring interfaces.
FDB Flush
When ring protection switching occurs, normally an FDB flush is executed. The Ethernet
ring control module uses the same mechanism as the STP to trigger the FDB flush. The
Ethernet ring control module controls the ring port physical interface's default STP index
to execute the FDB flush.
Starting with Junos OS Release 14.2, the FDB flush depends on the RAPS messages
received on the both the ports of the ring node.
226
Chapter 10: Configuring Ethernet Ring Protection Switching for High Availability
Figure 16: Protocol Packets from the Router or Switch to the Network
g017270
Juniper Networks switches and Juniper Networks routers use different methods to achieve
these routes.
The switches use forwarding database entries to direct the RAPS messages. The
forwarding database entry (keyed by the RAPS multicast address and VLAN) has a
composite next hop associated with itthe composite next hop associates the two ring
interfaces with the forwarding database entry and uses the split horizon feature to prevent
sending the packet out on the interface that it is received on. This is an example of the
forwarding database entry relating to the RAPS multicast MAC (a result of the show
ethernet-switching table detail command):
VLAN: v1, Tag: 101, MAC: 01:19:a7:00:00:01, Interface: ERP
Interfaces:
ge-0/0/9.0, ge-0/0/3.0
Type: Static
Action: Mirror
Nexthop index: 1333
The routers use an implicit filter to achieve ERP 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. For
each ring port control channel, a filter term is generated to control RAPS message
forwarding. The filter number is the same as the number of bridge domains that contain
the ring control channels. If a bridge domain contains control channels from multiple
rings, the filter related to this bridge domain will have multiple terms and each term will
relate to a control channel. The filter has command parts and control-channel related
parts, as follows:
Common terms:
227
Multiple Rings
The Ethernet ring control module supports multiple rings in each node (two logical
interfaces are part of each ring). The ring control module also supports the interconnection
of multiple rings. Interconnection of two rings means that two rings might share the same
link or share the same node. Ring interconnection is supported only using
non-virtual-channel mode. Ring interconnection using virtual channel mode is not
supported.
Node ID
For each node in the ring, a unique node ID identifies each node. The node ID is the node's
MAC address.
For routers only, you can configure this node ID when configuring the ring on the node or
automatically select an ID like STP does. In most cases, you will not configure this and
the router will select a node ID, like STP does. It should be the manufacturing MAC address.
The ring node ID should not be changed, even if you change the manufacturing MAC
address. Any MAC address can be used if you make sure each node in the ring has a
228
Chapter 10: Configuring Ethernet Ring Protection Switching for High Availability
different node ID. The node ID on switches is selected automatically and is not
configurable.
Ring ID
The ring ID is used to determine the value of the last octet of the MAC destination address
field of the RAPS protocol data units (PDUs) generated by the ERP control process. The
ring ID is also used to discard any RAPS PDU, received by this ERP control process with
a non-matching ring ID. Ring ID values 1 through 239 are supported.
Bridge Domains with the Ring Port (MX Series Routers Only)
On the routers, the protection group is seen as an abstract logical port that can be
configured to any bridge domain. Therefore, if you configure one ring port or its logical
interface in a bridge domain, you must configure the other related ring port or its logical
interface to the same bridge domain. The bridge domain that includes the ring port acts
as any other bridge domain and supports the IRB Layer 3 interface.
Wait-to-Block Timer
The RPL owner node uses a delay timer before initiating an RPL block in revertive mode
of operation or before reverting to IDLE state after clearing manual commands. The
Wait-to-Block (WTB) timer is used when clearing force switch and manual switch
commands. As multiple force switch commands are allowed to coexist in an Ethernet
ring, the WTB timer ensures that clearing of a single force switch command does not
trigger the re-blocking of the RPL. When clearing a manual switch command, the WTB
timer prevents the formation of a closed loop due to a possible timing anomaly where
the RPL Owner Node receives an outdated remote manual switch request during the
recovery process.
When recovering from a manual switch command, the delay timer must be long enough
to receive any latent remote force switch, signal failure, or manual switch commands.
This delay timer is called the WTB timer and is defined to be 5 seconds longer than the
guard timer. This delay timer is activated on the RPL Owner Node. When the WTB timer
expires, the RPL Owner Node initiates the reversion process by transmitting an RAPS
(NR, RB) message. The WTB timer is deactivated when any higher-priority request
preempts it.
229
For each ring, a protection group must be configured. There may be several rings in each
node, so there should be multiple protection groups corresponding to the related Ethernet
rings.
Three interval parameters (restore-interval, guard-interval, and hold-interval) can be
configured at the protection group level. These configurations are global configurations
and apply to all Ethernet rings if the Ethernet ring doesn't have a more specific
configuration for these values. If no parameter is configured at the protection group level,
the global configuration of this parameter uses the default value.
Related
Documentation
230
Chapter 10: Configuring Ethernet Ring Protection Switching for High Availability
Requirements
This example uses the following hardware and software components:
node 1
ge-1/0/4
ge-1/2/1
ge-1/0/2
node 2
ge-1/0/3
node 3
g017272
ge-1/2/4
The configuration in this section is only for the RAPS channel. The bridge domain for user
traffic is the same as the normal bridge domain. The only exception is if a bridge domain
includes a ring port, then it must also include the other ring port of the same ring.
1.
Configuring Node 1
interfaces {
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;
231
vlan-id 100;
}
}
}
bridge-domains {
bd1 {
domain-type bridge;
interface ge-1/2/4.1;
interface ge-1/0/1.1;
}
}
protocols {
protection-group {
ethernet-ring pg101 {
node-id 00:01:01:00:00:01;
ring-protection-link-owner;
east-interface {
control-channel ge-1/0/1.1;
ring-protection-link-end;
}
west-interface {
control-channel ge-1/2/4.1;
}
}
}
}
protocols {
oam {
ethernet {
connectivity-fault-management {
action-profile rmep-defaults {
default-action {
interface-down;
}
}
maintenance-domain d1 {
level 0;
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;
}
}
}
232
Chapter 10: Configuring Ethernet Ring Protection Switching for High Availability
}
}
}
}
}
}
2.
Configuring Node 2
interfaces {
ge-1/0/2 {
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-bridge;
vlan-id 100;
}
}
ge-1/2/1 {
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-bridge;
vlan-id 100;
}
}
}
bridge-domains {
bd1 {
domain-type bridge;
interface ge-1/2/1.1;
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 {
233
default-action {
interface-down;
}
}
maintenance-domain d1 {
level 0;
maintenance-association 100 {
mep 2 {
interface ge-1/2/1;
remote-mep 1 {
action-profile rmep-defaults;
}
}
}
}
maintenance-domain d3 {
level 0;
maintenance-association 100 {
mep 1 {
interface ge-1/0/2;
remote-mep 2 {
action-profile rmep-defaults;
}
}
}
}
}
}
}
}
3.
Configuring Node 3
interfaces {
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;
interface ge-1/0/4.1;
234
Chapter 10: Configuring Ethernet Ring Protection Switching for High Availability
interface ge-1/0/3.1;
}
}
protocols {
protection-group {
ethernet-ring pg103 {
east-interface {
control-channel ge-1/0/3.1;
}
west-interface {
control-channel ge-1/0/4.1;
}
}
}
}
protocols {
oam {
ethernet {
connectivity-fault-management {
action-profile rmep-defaults {
default-action {
interface-down;
}
}
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;
}
}
}
}
}
}
}
}
235
Examples: Ethernet
RPS Output
This section provides output examples based on the configuration shown in Example:
Ethernet Ring Protection Switching Configuration on MX Routers on page 230. The show
commands used in these examples can help verify configuration and correct operation.
Request/state
NR
No Flush
No
Remote Node ID
Control Channel
ge-1/0/1.1
ge-1/2/4.1
Forward State
discarding
forwarding
Remote Node ID
00:01:01:00:00:01
Control Channel
ge-1/2/1.1
ge-1/0/2.1
Signal Failure
236
Forward State
forwarding
forwarding
Admin State
Chapter 10: Configuring Ethernet Ring Protection Switching for High Availability
Clear
Clear
IFF ready
IFF ready
Remote Node ID
00:01:02:00:00:01
Control Channel
ge-1/0/1.1
ge-1/2/4.1
Signal Failure
Clear
Clear
Forward State
forwarding
forwarding
Admin State
IFF ready
IFF ready
Quard Timer
disabled
Operation state
operational
237
Request/state
SF
No Flush
No
Remote Node ID
00:00:00:00:00:00
Control Channel
ge-1/2/1.1
ge-1/0/2.1
Signal Failure
Clear
set
Forward State
forwarding
discarding
Admin State
IFF ready
IFF ready
Quard Timer
disabled
Operation state
operational
Related
Documentation
238
CHAPTER 11
Disabling MAC Address Learning of Neighbors Through ARP or Neighbor Discovery for
IPv4 and IPv6 Neighbors on page 240
LooseForwards packets when both the IP source address and the MAC source address
match one of the trusted address tuples.
Drops packets when the IP source address matches one of the trusted tuples, but the
MAC address does not support the MAC address of the tuple
Continues to forward packets when the source address of the incoming packet does
not match any of the trusted IP addresses.
StrictForwards 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.
Related
Documentation
Disabling MAC Address Learning of Neighbors Through ARP or Neighbor Discovery for
IPv4 and IPv6 Neighbors on page 240
239
Related
Documentation
Disabling MAC Address Learning of Neighbors Through ARP or Neighbor Discovery for
IPv4 and IPv6 Neighbors
The Junos OS provides the no-neighbor-learn configuration statement at the [edit
interfaces interface-name unit interface-unit-number family inet] and [edit interfaces
interface-name unit interface-unit-number family inet6] hierarchy levels.
To disable ARP address learning by not sending arp-requests and not learning from ARP
replies for IPv4 neigbors, include the no-neighbor-learn statement at the [edit interfaces
interface-name unit interface-unit-number family inet] hierarchy level:
[edit interfaces interface-name unit interface-unit-number family inet]
no-neighbor-learn;
To disable neighbor discovery for IPv6 neighbors, include the no-neighbor-learn statement
at the [edit interfaces interface-name unit logical-unit-number family inet6] hierarchy level:
[edit interfaces interface-name unit interface-unit-number family inet6]
no-neighbor-learn;
240
Related
Documentation
Configuring Junos OS ARP Learning and Aging Options for Mapping IPv4 Network
Addresses to MAC Addresses
241
242
CHAPTER 12
Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers on page 249
Specifying the Interface Over Which VPN Traffic Travels to the CE Router on page 262
Specifying the Interface to Handle Traffic for a CCC Connected to the Layer 2
Circuit on page 273
243
244
Guidelines for Configuring VLAN ID List-Bundled Logical Interfaces That Connect CCCs
on page 270
Specifying the Interface Over Which VPN Traffic Travels to the CE Router on page 259
Specifying the Interface to Handle Traffic for a CCC Connected to the Layer 2 Circuit
on page 268
VLAN ID Range
1 through 1023
1 through 4094
1 through 1023
1 through 4094
1 through 4094
Gigabit Ethernet
1 through 4094
Gigabit Ethernet IQ
1 through 4094
10-Gigabit Ethernet
1 through 4094
1 through 1023
245
NOTE: For Gigabit Ethernet IQ and Gigabit Ethernet PICs with SFPs (except
the built-in Gigabit Ethernet port on the M7i router), VLAN IDs on a single
interface can differ from each other.
Because IS-IS has an 8-bit limit for broadcast multiaccess media, you cannot
set up more than 255 adjacencies over Gigabit Ethernet using VLAN tagging.
For more information, see the Junos OS Routing Protocols Library for Routing
Devices.
Related
Documentation
Configure a dynamic profile for dynamic VLAN or dynamic stacked VLAN creation.
2. Associate the VLAN or stacked VLAN dynamic profile with the interface.
3. Specify the Ethernet packet type that the VLAN dynamic profile accepts.
4. Define VLAN ranges for use by the dynamic profile when creating VLAN IDs.
For procedures on how to configure dynamic VLANs and dynamic stacked VLANs for
client access, see the Junos OS Broadband Subscriber Management and Services Library.
Related
Documentation
246
NOTE: If you configure VLAN tagging on Gigabit Ethernet IQ, IQ2 and IQ2-E
interfaces on M320, M120, and T Series routers, the Junos OS creates an
internal logical interface that reserves 50 Kbps of bandwidth from Gigabit
Ethernet IQ interfaces and 2 Mbps of bandwidth from Gigabit Ethernet IQ2
and IQ2-E interfaces. As a result, the effective available bandwidth for these
interface types is now 999.5 Mbps and 998 Mbps, respectively.
247
address address;
}
}
unit logical-unit-number {
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
family family {
address address;
}
}
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
10224 bytes more. The additional 4 bytes accommodates the future addition
of a stacked VLAN tag configuration on the same physical interface.
If the same physical interface MTU value is configured on both the VLAN and
flexible VLAN-tag routers, the L2 circuit configuration does not come up and
a MTU mismatch is logged. However, normal traffic flow is unaffected.
For encapsulation type flexible-ethernet-services, all VLAN IDs are valid. See Configuring
VLAN Encapsulation on page 256.
The logical interface on which untagged packets are to be received must be configured
with the same native VLAN ID as that configured on the physical interface. To configure
the logical interface, include the vlan-id statement (matching the native-vlan-id statement
on the physical interface) at the [edit interfaces interface-name unit logical-unit-number]
hierarchy level.
248
For information about binding VLAN IDs to logical interfaces, see Binding VLAN IDs to
Logical Interfaces on page 250. For information about configuring dual VLAN tags using
the vlan-tag statement, see Stacking a VLAN Tag on page 499.
Related
Documentation
249
with inner and outer options or the vlan-id statement at the [edit interfaces et-fpc/pic/port
unit logical-unit-number] hierarchy level:
[edit interfaces et-fpc/pic/port]
flexible-vlan-tagging;
unit logical-unit-number {
vlan-id number;
}
unit logical-unit-number {
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
}
Related
Documentation
Table 16: Configuration Statements Used to Bind VLAN IDs to Logical Interfaces
Scope of VLAN
ID Matching
Dual-Tag Framing
VLAN ID
vlan-id vlan-id;
VLAN ID Range
vlan-id-range vlan-idvlan-id;
VLAN ID List
vlan-id-list [vlan-id
vlan-idvlan-id];
You can include all of the statements at the following hierarchy levels:
250
NOTE: The inner-list option of the vlan-tags statement does not support Tag
Protocol ID (TPID) values.
251
252
253
NOTE: The inner-list option of the vlan-tags statement does not support Tag
Protocol ID (TPID) values.
In the example configuration above, ge-1/1/0 supports single-tag logical interfaces, and
ge-1/1/1 supports mixed tagging. The single-tag logical interfaces ge-1/1/0.10 and
ge-1/1/1.20 each bundle lists of VLAN IDs. The dual-tag logical interface ge-1/1/1.20
bundles lists of inner VLAN IDs.
TIP: You can group a range of identical interfaces into an interface range and
then apply a common configuration to that interface range. For example, in
the above example configuration, both interfaces ge-1/1/0 and ge-1/1/1 have
the same physical encapsulation type of flexible-ethernet-services. Thus you
can define an interface range with the interfaces ge-1/1/0 and ge-1/1/1 as its
254
Related
Documentation
Table 17: Configuration Statements Used to Associate VLAN IDs to VLAN Demux Interfaces
Statement
Format
Single-Tag Framing
Dual-Tag Framing
vlan-id vlan-id;
You can include all of the statements at the following hierarchy levels:
255
To configure an interface to support single-tag logical interfaces, you must also include
the vlan-tagging statement at the [edit interfaces interface-name] hierarchy level. To
support mixed tagging, include the flexible-vlan-tagging statement instead.
Ethernet interfaces in VLAN mode can have multiple logical interfaces. In CCC and VPLS
modes, VLAN IDs from 1 through 511 are reserved for normal VLANs, and VLAN IDs
512 through 4094 are reserved for CCC or VPLS VLANs. For 4-port Fast Ethernet interfaces,
you can use VLAN IDs 512 through 1024 for CCC or VPLS VLANs.
For encapsulation type flexible-ethernet-services, all VLAN IDs are valid.
256
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; if the VLAN ID is 511 or lower, it will be subject to the normal destination
filter lookups in addition to source address filtering. However if you configure flexible
Ethernet services encapsulation, this VLAN ID restriction is removed.
Related
Documentation
257
For extended VLAN CCC and extended VLAN VPLS encapsulation, all VLAN IDs 1 and
higher are valid. VLAN ID 0 is reserved for tagging the priority of frames.
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.
258
Related
Documentation
Specifying the Interface Over Which VPN Traffic Travels to the CE Router on page 259
[edit]
Specifying the Interface Over Which VPN Traffic Travels to the CE Router
To configure a Layer 2 VPN routing instance on a PE router, include the instance-type
statement and specify the value l2vpn. To specify an interface connected to the router,
include the interface statement and specify the VLAN-bundled logical interface:
instance-type l2vpn;
interface logical-interface-name;
259
You can include the statements at the same hierarchy level at which you include the
instance-type l2vpn and interface logical-interface-name statements:
To enable a Layer 2 VPN routing instance on a PE router, include the l2vpn statement.
For more information, see the Junos OS VPNs Library for Routing Devices.
The encapsulation-type statement specifies the Layer 2 protocol used for traffic from
the customer edge (CE) router. If the Layer 2 VPN routing instance is being connected
to a single-tag Layer 2 circuit, specify ethernet as the encapsulation type. If the Layer 2
VPN routing instance is being connected to a dual-tag Layer 2 circuit, specify ethernet-vlan
as the encapsulation type.
To specify the interface to handle traffic for a circuit connected to the Layer 2 VPN routing
instance, include the interface statement and specify the VLAN-bundled logical interface.
260
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:
[edit protocols]
rsvp {
interface all;
interface lo0.0;
}
mpls {
label-switched-path lsp {
to 10.255.69.128;
}
interface all;
}
bgp {
group g1 {
type internal;
local-address 10.255.69.96;
family l2vpn {
signaling;
}
neighbor 10.255.69.128;
}
}
ospf {
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.
[edit routing-instances]
red {
instance-type l2vpn;
interface ge-1/0/5.0; # VLAN-bundled logical interface
route-distinguisher 10.255.69.96:100;
vrf-target target:1:1;
protocols {
l2vpn {
encapsulation-type ethernet; # For single-tag VLAN logical interface
site CE_ultima {
site-identifier 1;
interface ge-1/0/5.0;
}
}
261
}
}
Related
Documentation
Specifying the Interface Over Which VPN Traffic Travels to the CE Router
To configure a Layer 2 VPN routing instance on a PE router, include the instance-type
statement and specify the value l2vpn. To specify an interface connected to the router,
include the interface statement and specify the VLAN-bundled logical interface:
instance-type l2vpn;
interface logical-interface-name;
Related
Documentation
262
Related
Documentation
Related
Documentation
263
the ID numbers, or specify a combination of individual VLAN IDs and a range of VLAN
IDs.
vlan-id-list [number number-number];
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.
When a packet is received that is tagged with a VLAN ID not specified in the trunk interface
list of VLAN IDs, the native VLAN ID is pushed in front of the existing VLAN tag or tags
and the packet is forwarded within the bridge domain that is configured with the matching
VLAN ID.
When an untagged packet is received on a trunk interface, the native VLAN ID is added
to the packet and the packet is forwarded within the bridge domain that is configured
with the matching VLAN ID.
A bridge domain configured with a matching VLAN ID must be configured before the
trunk interface is configured. To learn more about configuring bridge domains, see the
Junos Routing Protocols Configuration Guide.
Related
Documentation
264
}
ge-2/0/1 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 1;
}
}
If you want igmp-snooping to be functional for a bridge domain, then you should not
configure interface-mode and irb for that bridge domain. Such a configuration commit
succeeds, but IGMP snooping is not functional, and a message informing the same is
displayed as shown after the sample configuration below:
user@host# run show configuration
interfaces {
ge-5/1/1 {
flexible-vlan-tagging;
native-vlan-id 1;
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 401;
}
}
}
irb {
unit 401 {
family inet {
address 192.168.2.2/27;
}
}
}
}
protocols {
igmp {
interface all;
}
}
bridge-domains {
VLAN-401 {
vlan-id 401;
routing-interface irb.401;
protocols {
igmp-snooping;
}
}
}
user@host# commit
[edit bridge-domains]
'VLAN-401'
IGMP Snooping not supported with IRB and trunk mode interface ge-5/1/1.0
commit complete
To achieve IGMP snooping for a bridge domain, you should use such a configuration as
shown in the following example:
user@host# run show configuration
265
interfaces {
ge-0/0/1 {
flexible-vlan-tagging;
native-vlan-id 1;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 401;
}
}
irb {
unit 401 {
family inet {
address 192.168.2.2/27;
}
}
}
}
protocols {
igmp {
interface all;
}
}
bridge-domains {
VLAN-401 {
vlan-id 401;
interface ge-0/0/1.0;
routing-interface irb.401;
protocols {
igmp-snooping;
}
}
}
user@host# commit
commit complete
Related
Documentation
interface-mode
266
...
}
}
Related
Documentation
[edit]
[edit]
For a single-tag logical interface, include the encapsulation statement and specify vlan-ccc
so that CCC circuit encapsulation is used inside the Layer 2 circuit.
Related
Documentation
Specifying the Interface to Handle Traffic for a CCC Connected to the Layer 2 Circuit
on page 268
267
Specifying the Interface to Handle Traffic for a CCC Connected to the Layer 2
Circuit on page 268
[edit]
For a single-tag logical interface, include the encapsulation statement and specify vlan-ccc
so that CCC circuit encapsulation is used inside the Layer 2 circuit.
Specifying the Interface to Handle Traffic for a CCC Connected to the Layer 2 Circuit
To configure the VLAN-bundled logical interface as the interface to handle traffic for a
circuit connected to the Layer 2 circuit, include the following statements:
l2circuit {
neighbor address {
interface logical-interface-name {
virtual-circuit-id number;
no-control-word;
}
268
}
}
[edit protocols]
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;
interface lo0.0;
}
mpls {
label-switched-path lsp {
to 10.255.69.128;
}
interface all;
}
ospf {
269
traffic-engineering;
area 0.0.0.0 {
interface lo0.0;
interface ge-1/1/1.0;
}
}
ldp {
interface ge-1/1/1.0;
interface ge-1/0/5.0; # VLAN-bundled logical interface
interface lo0.0;
}
l2circuit {
neighbor 10.255.69.128 {
interface ge-1/0/5.0 { # VLAN-bundled logical interface
virtual-circuit-id 3;
no-control-word;
}
}
}
Related
Documentation
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.
A CCC allows you to configure transparent connections between two circuits so that
packets from the source circuit are delivered to the destination circuit with, at most, the
Layer 2 address being changed. You configure a CCC by connecting circuit interfaces of
the same type. For more information, see Circuit and Translational Cross-Connects
Overview.
The following configuration guidelines apply to bundling lists of VLAN IDs to Ethernet
logical interfaces used to configure CCCs:
270
Guidelines for Configuring Logical Link-Layer Encapsulation to Support CCCs on page 271
Layer 2 Circuit
Syntax
encapsulation vlan-ccc;
Hierarchy Level
Usage
Guidelines
For a
Single-Tag
Logical
Interface
271
Layer 2 Circuit
For a Dual-Tag
Logical
Interface
Related
Documentation
You can include the statements at the same hierarchy level at which you include the
instance-type l2vpn and interface logical-interface-name statements:
To enable a Layer 2 VPN routing instance on a PE router, include the l2vpn statement.
For more information, see the Junos OS VPNs Library for Routing Devices.
The encapsulation-type statement specifies the Layer 2 protocol used for traffic from
the customer edge (CE) router. If the Layer 2 VPN routing instance is being connected
to a single-tag Layer 2 circuit, specify ethernet as the encapsulation type. If the Layer 2
272
VPN routing instance is being connected to a dual-tag Layer 2 circuit, specify ethernet-vlan
as the encapsulation type.
To specify the interface to handle traffic for a circuit connected to the Layer 2 VPN routing
instance, include the interface statement and specify the VLAN-bundled logical interface.
Related
Documentation
Specifying the Interface to Handle Traffic for a CCC Connected to the Layer 2 Circuit
To configure the VLAN-bundled logical interface as the interface to handle traffic for a
circuit connected to the Layer 2 circuit, include the following statements:
l2circuit {
neighbor address {
interface logical-interface-name {
virtual-circuit-id number;
no-control-word;
}
}
}
[edit protocols]
273
274
CHAPTER 13
Example: Configuring PVLANs with Secondary VLAN Trunk Ports and Promiscuous
Access Ports on page 289
Guidelines for Configuring IRB Interfaces in PVLANs on MX Series Routers on page 302
275
Just like regular VLANs, PVLANs are isolated on Layer 2 and require an external router to
route traffic among them.
PVLANs are useful for restricting the flow of broadcast and unknown unicast traffic and
for limiting the communication between known hosts. Service providers use PVLANs to
keep their customers isolated from each other. Another typical use for a PVLAN is to
provide per-room Internet access in a hotel.
This topic explains the following concepts regarding PVLANs on MX Series routers:
PVLANs Use Four Different Ethernet Switch Port Types on page 278
276
Secondary isolated VLANVLAN that receives packets only from the primary VLAN
and forwards frames upstream to the primary VLAN.
277
Isolated portIsolated ports have Layer 2 connectivity only with promiscuous ports
and PVLAN trunk portsan isolated port cannot communicate with another isolated
port even if these two ports are members of the same isolated VLAN (or interswitch
isolated VLAN) domain. Typically, a server, such as a mail server or a backup server, is
connected on an isolated port. In a hotel, each room would typically be connected on
an isolated port, meaning that room-to-room communication is not possible, but each
room can access the Internet on the promiscuous port.
Interswitch link portAn interswitch link (ISL) port is a trunk port that connects two
routers when a PVLAN spans those routers. The ISL port is a member of all VLANs
within the PVLAN (that is, the primary VLAN, the community VLANs, and the isolated
VLAN).
Communication between an ISL port and an isolated port is unidirectional. An ISL ports
membership in the interswitch isolated VLAN is egress-only, meaning that incoming
traffic on the ISL port is never assigned to the isolated VLAN. An isolated port can
forward packets to a PVLAN trunk port, but a PVLAN trunk port cannot forward packets
to an isolated port. Table 20 on page 279 summarizes whether Layer 2 connectivity
exists between the different types of ports.
278
Promiscuous
Port
Community Port
Isolated Port
Promiscuous
Yes
Yes
Yes
Yes
Community
Yes
Yessame community
only.
No
Yes
Isolated
Yes
No
No
Yes
NOTE: This
communication is
unidirectional.
Interswitch Link
Yes
Yessame community
only.
Yes
Yes
This communication is
unidirectional.
Creating a PVLAN
The flowchart shown in Figure 19 on page 280 gives you a general idea of the process for
creating PVLANs. If you complete your configuration steps in the order shown, you will
not violate these PVLAN rules. (In the PVLAN rules, configuring the PVLAN trunk port
applies only to a PVLAN that spans multiple routers.)
If you are going to configure a community VLAN ID, you must first configure the primary
VLAN.
If you are going to configure an isolation VLAN ID, you must first configure the primary
VLAN.
Configuring a VLAN on a single router is relatively simple, as shown in Figure 19 on page 280.
279
Within a primary VLAN, you can configure secondary community VLANs or secondary
isolated VLANs or both. Configuring a secondary community VLAN consists of these
steps:
1.
Isolated VLANs are created internally when the isolated VLAN has access interfaces as
members and the option no-local-switching is enabled on the primary VLAN.
802.1Q tags are required for interswitch isolated VLANs because IEEE 802.1Q uses an
internal tagging mechanism by which a trunking device inserts a 4-byte VLAN frame
identification tab into the packet header.
Trunk ports are only needed for multirouter PVLAN configurationsthe trunk port carries
traffic from the primary VLAN and all secondary VLANs.
Related
Documentation
280
Community VLAN = Cx
Bridge domains are provisioned for each of the VLANs, namely, Vp, Vi, and Vcx. Assume
the bridge domains to be configured as follows:
VpBD_primary_Vp (ports contained are p1, t1, i1, i2, cx1, cx2)
ViBD_isolate_Vi (ports contained are p1, t1, *i1, *i2)
VcxBD_community_Vcx (ports contained are p1, t1, cx1, cx2)
The bridge domains for community, primary, and isolated VLANs are automatically
created by the system internally when you configure a bridge domain with a trunk interface,
access interface, or interswitch link. The bridge domains contain the same VLAN ID
corresponding to the VLANs. To use bridge domains for PVLANs, you must configure the
following additional attributes:
isolated-vlan optionThis option denotes the vlan tag to be used for isolation BD
inter-switch-link option with the interface-mode trunk statement at the [edit interfaces
interface-name family bridge] or the [edit interfaces interface-name unit
logical-unit-number family bridge] hierarchy levelThis configuration specifies whether
the particular interface assumes the role of interswitch link for the PVLAN domains of
which it is a member.
You can use the vlan-id configuration statement for PVLAN ports to identify the port role.
All the logical interfaces involved in PVLANs must be configured with a VLAN ID and the
Layer 2 process uses this VLAN tag to classify a port role as promiscuous, isolated, or
community port by comparing this value with the VLANs configured in the PVLAN bridge
domain (using the bridge-domains statement at the [edit] hierarchy level). The ISL port
role is identified by the inter-switch-link option. The VLAN ID for ISL port is required and
281
must be set to to the primary VLAN ID. The ISL must be a trunk interface. A list of VLAN
IDs is not needed because the Layer 2 process creates such a list internally based on
PVLAN bridge domain configuration. For untagged promiscuous, isolated or community,
logical interfaces or ports, access mode must be used as the interface mode. For tagged
promiscuous, isolated, or community interfaces, trunk mode must be specified as the
interface mode.
The bridge domain interface families are enhanced to include ingress-only and egress-only
association. The association for the interface family bridge domain (IFBD) is created in
the following manner:
For BD_primary_Vp, IFBD for i1, i2, cx1 and cx2 are egress only.
BD_isolate_Vi, IFBD for p1 will be egress only and for i1 and i2 are ingress only.
BD_community_Vcx , IFBD for p1 are egress only. VLAN translation rules ensure the
following VLAN mappings to work properly:
VLAN mapping on isolation ports: On tagged isolated ports, the VLAN tag, Vp, is
mapped to Vi on egress.
VLAN mapping on community ports: On tagged community ports, the VLAN tag, Vp,
is mapped to Vcx on egress.
A management bridge domain for PVLAN that exists only in the Layer 2 address learning
process called PBD to denote bridge domain for VLAN is used by the system. This bridge
domain has the same name as the user-configured name. Under this bridge domain, one
primary PVLAN bridge domain for the primary vlan, one isolation bridge domain for the
isolation vlan, and one community bridge domain for each community vlan are
programmed internally. You might find separate bridge domains for the PVLAN ports to
be useful if you want to configure a policy for a specific community VLAN or isolation
VLAN.
The management bridge domain maintains a list to include all internal bridge domains
that belong to this PVLAN bridge domain. Isolation and community bridge domains
contain a pointer or a flag to indicate that this bridge domain is for PVLANs and maintain
the information about the primary bridge domain index and primary VLAN. All this
information is available across the bridge domain interfaces that are mapped to this
bridge domain. MAC learning occurs only in the primary bridge domain and the MAC
forwarding entry is programmed into the primary bridge domain only. As a result, the
isolation bridge domain and all community bridge domains share the same forwarding
table as the primary bridge domain.
For the isolation bridge domain, BD_isolate_Vi, isolation port i1 and i2 function as a
non-local-switch access port and the flood group for this bridge domain contains only
the promiscuous port, p1, and ISL ports, t1 and t2.
282
2. A source MAC address (SMAC) lookup is performed to find out whether this MAC
addresses is learned or not. If it is not a learned address, an MLP packet (route for
flooding traffic to MAC learning chips) is sent to all the other Packet Forwarding
Engines that are mapped with this bridging domain. In addition, an MLP packet is also
sent to the host.
3. A destination MAC address (DMAC) lookup using the tuple (bridge domain ID, VLAN,
egress next-hop. The egress Packet Forwarding Engine is used to forward the packet.
5. If a miss occurs during the lookup, the flood next-hop is determined using the mesh
283
A source MAC address (SMAC) lookup is performed to find out whether this MAC
address is learned or not. If it is not a learned address, an MLP packet (route for flooding
traffic to MAC learning chips) is sent to all the other Packet Forwarding Engines that
are mapped with this bridging domain. In addition, an MLP packet is also sent to the
host.
A destination MAC address (DMAC) lookup using the tuple (bridge domain ID, VLAN,
and destination MAC address).
If a match is observed for the MAC address, the result of the lookup points to the egress
next-hop. The egress Packet Forwarding Engine is used to forward the packet.
If a miss occurs during the lookup, the flood next-hop is determined using the mesh
group ID to flood the packet.
If a match occurs, the group ID is derived from the VLAN lookup table and the following
validation is performed to enforce primary VLAN forwarding:
Here, {*} is a wildcard in regular expression notation referring to any value. Step 1 ensures
all forwarding from promiscuous or inter switch link ports to any other port is permitted.
Step 2 ensures all forwarding from any port to promiscuous or interswitch link ports is
permitted. Step 3 ensures any isolated port to another isolated port is dropped. Step 4
ensures community port forwarding is permitted only within same community(X == Y)
and dropped when its across community (X Y).
Related
Documentation
Community VLAN = Cx
Bridge domains are provisioned for each of the VLANs, namely, Vp, Vi, and Vcx. Assume
the bridge domains to be configured as follows:
284
VpBD_primary_Vp (ports contained are p1, t1, i1, i2, cx1, cx2)
ViBD_isolate_Vi (ports contained are p1, t1, *i1, *i2)
VcxBD_community_Vcx (ports contained are p1, t1, cx1, cx2)
The bridge domains for community, primary, and isolated VLANs are automatically
created by the system internally when you configure a bridge domain with a trunk interface,
access interface, or interswitch link. The bridge domains contain the same VLAN ID
corresponding to the VLANs. To use bridge domains for PVLANs, you must configure the
following additional attributes:
285
Community1
Community2
C11 C12
C21 C22
Internally, one global BD called the primary vlan BD is created that consists of all the
ports. One isolation bridge domain consisting of all isolation ports in addition the
promiscuous and ISL ports and one bridge domain per community is defined consisting
of community ports in addition to the promiscuous and ISL ports internally configured
in the system. The bridge domains with the PVLAN ports are as follows:
Primary Vlan BD P1 P2 L1 L2 I1 I2 C11 C12 C21 C22
Isolated BD
I1 I2 P1 P2 L1 L2
Community1 BD
C11 C12 P1 P2 L1 L2
Community 2 BD
C21 C22 P1 P2 L1 L2
The following PVLAN forwarding events take place among these ports with the
appropriate VLAN translation as described in the following table:
Port Type
To:
From:
Isolated
Community
Promiscuous
Inter-switch Link
Isolated
Dropped
Dropped
Promiscuous
Dropped
No translation if it is
the same community;
else dropped.
Community
Isolated VLAN
tag to Primary
VLAN tag
No translation
Interswitch Link
No translation
No translation
No translation
No translation
286
PVLANs are supported on MX80 routers, on MX240, MX480, and MX960 routers with
DPCs in LAN mode, on MX Series routers with MPC1, MPC2, and Adaptive Services
PICs.
Isolated ports, promiscuous ports, community ports, and interswitch links (ISL) adhere
to the following rules of tagging and forwarding:
The frames received on the primary VLAN on promiscuous ports can go to any port.
The frames received on isolated ports can only go to promiscuous ports and ISL
ports.
Related
Documentation
The frames received on community ports can only go to ports of the same community,
promiscuous ports, and ISL ports.
The frames received on ISL ports with an isolation VLAN tag or ID can only go to
promiscuous ports or ISL ports.
The frames received on ISL ports with a community VLAN tag can only go to
promiscuous ports, ISL ports, or ports belonging to a corresponding community port.
The frames being sent out of promiscuous ports should have a primary VLAN tag or
should be untagged. It is considered untagged if the port is configured as an untagged
member of the primary VLAN. The frames going out of isolated or community ports
are generally untagged. However, they can also be tagged depending on the port
configuration. In any case, the configured VLAN tag must be the same as the related
isolated VLAN tag or community VLAN tag.
The frames going out of ISL ports are tagged with the primary VLAN if they are
received on a promiscuous port. An untagged frame cannot exit out of an ISL port
in the context of a primary VLAN, isolated VLAN, or community VLAN, but for any
other VLAN, it can be untagged depending on the configuration.
The frames going out of ISL ports are tagged with an isolated VLAN (isolation ID) if
received on the isolated port.
The frames going out of ISL ports are tagged with the community VLAN tag, if it is
received on the corresponding community port.
A virtual switch instance that contains a bridge domain associated with logical
interfaces is supported.
Aggregated Ethernet (ae) interfaces for all types of ports are supported.
Virtual private LAN service (VPLS) instances is not supported. Integrated routing and
bridging (IRB) interfaces in PVLANs are supported.
MC-LAG interfaces are not supported. All ports that are associated with PVLAN bridge
domains cannot be mc-ae interfaces.
287
Created and configured the necessary VLANs. See Configuring VLAN Encapsulation
on page 256 and Enabling VLAN Tagging on page 246.
Configured MX240, MX480, and MX960 routers to function in enhanced LAN mode
by entering the network-services lan statement at the [edit chassis] hierarchy level.
You must reboot the router when you configure or delete the enhanced LAN mode on
the router. Configuring the network-services lan option implies that the system is running
in the enhanced IP mode. When you configure a device to function in MX-LAN mode,
only the supported configuration statements and operational show commands that
are available for enabling or viewing in this mode are displayed in the CLI interface.
If your system contains parameters that are not supported in MX-LAN mode in a
configuration file, you cannot commit those unsupported attributes. You must remove
the settings that are not supported and then commit the configuration. After the
successful CLI commit, a system reboot is required for the attributes to become
effective. Similarly, if you remove the network-services lan statement, the system does
not run in MX-LAN mode. Therefore, all of the settings that are supported outside of
the MX-LAN mode are displayed and are available for definition in the CLI interface. If
your configuration file contains settings that are supported only in MX-LAN mode, you
must remove those attributes before you commit the configuration. After the successful
CLI commit, a system reboot is required for the CLI parameters to take effect. The
Layer 2 Next-Generation CLI configuration settings are supported in MX-LAN mode.
As a result, the typical format of CLI configurations might differ in MX-LAN mode.
To configure a PVLAN:
1.
2. Create the interswitch link (ISL) trunk port for the PVLAN.
[edit interfaces]
user@host# set interface interface-name unit logical-unit-number family bridge
interface-mode trunk inter-switch-link
user@host# set interface interface-name unit logical-unit-number family bridge vlan-id
vlan-id
288
3. Create the isolated port for the PVLAN. The port is identified as an isolated port or a
community port, based on the VLAN ID or the list of VLAN IDs to which the interface
corresponds. For example, if you configure a port with a VLAN ID of 50, and if you
specify a VLAN ID of 50 as the isolated VLAN or tag in the bridge domain, the port is
considered as an isolation port.
[edit interfaces]
user@host# set interface interface-name unit logical-unit-number family bridge
interface-mode access
user@host# set interface interface-name unit logical-unit-number family bridge vlan-id
vlan-id
4. Create the community port for the PVLAN. The port is identified as an isolated port
or a community port, based on the VLAN ID or the list of VLAN IDs to which the interface
corresponds. For example, if you configure a port with a VLAN ID of 50, and if you
specify a VLAN ID of 50 as the community VLAN or tag in the bridge domain, the port
is considered as a community port.
[edit interfaces]
user@host# set interface interface-name unit logical-unit-number family bridge
interface-mode access
user@host# set interface interface-name unit logical-unit-number family bridge vlan-id
vlan-id
5. Create a virtual switch instance with a bridge domain and associate the logical
interfaces.
[edit routing-instances]
user@host# set routing-instance-name instance-type virtual-switch
user@host# set routing-instance-name interface interface-name unit
logical-unit-number
user@host# set routing-instance-name bridge-domains bridge-domain-name
6. Specify the primary, isolated, and community VLAN IDs, and associate the VLANs
Related
Documentation
Example: Configuring PVLANs with Secondary VLAN Trunk Ports and Promiscuous
Access Ports
This example shows how to configure secondary VLAN trunk ports and promiscuous
access ports as part of a private VLAN configuration. Secondary VLAN trunk ports carry
secondary VLAN traffic.
For a given private VLAN, a secondary VLAN trunk port can carry traffic for only one
secondary VLAN. However, a secondary VLAN trunk port can carry traffic for multiple
secondary VLANs as long as each secondary VLAN is a member of a different private
(primary) VLAN. For example, a secondary VLAN trunk port can carry traffic for a
289
community VLAN that is part of primary VLAN pvlan100 and also carry traffic for an
isolated VLAN that is part of primary VLAN pvlan400.
To configure a trunk port to carry secondary VLAN traffic, use the isolated and interface
statements, as shown in steps 12 and 13 of the example configuration for Switch 1.
NOTE: When traffic egresses from a secondary VLAN trunk port, it normally
carries the tag of the primary VLAN that the secondary port is a member of.
If you want traffic that egresses from a secondary VLAN trunk port to retain
its secondary VLAN tag, use the extend-secondary-vlan-id statement.
A promiscuous access port carries untagged traffic and can be a member of only one
primary VLAN. Traffic that ingresses on a promiscuous access port is forwarded to the
ports of the secondary VLANs that are members of the primary VLAN that the promiscuous
access port is a member of. This traffic carries the appropriate secondary VLAN tags
when it egresses from the secondary VLAN ports if the secondary VLAN port is a trunk
port.
To configure an access port to be promiscuous, use the promiscuous statement, as shown
in step 12 of the example configuration for Switch 2.
If traffic ingresses on a secondary VLAN port and egresses on a promiscuous access port,
the traffic is untagged on egress. If tagged traffic ingresses on a promiscuous access
port, the traffic is discarded.
Requirements
This example uses the following hardware and software components:
290
The figure also shows how traffic would flow after ingressing on the secondary VLAN
trunk ports on Switch 1.
Figure 20: PVLAN Topology with Secondary VLAN Trunk Ports and
Promiscuous Access Port
Secondary VLAN Trunk Ports
(pvlan100 and pvlan400)
xe-0/0/0
xe-0/0/01
Tag
600
Isolated Access
Port xe-0/0/2
(isolated200)
Tag
200
Tag
600
Tag Tag
100 400 Untagged
xe-0/0/01
Isolated Access
Port xe-0/0/5
(isolated500)
Community
Port xe-0/0/3
(comm300)
Community
Port (trunk)
xe-0/0/6
(comm600)
Secondary
VLAN Trunk
Port xe-0/0/2
(isolated200)
Untagged
Isolated Access
Port xe-0/0/5
(isolated500)
Community
Port xe-0/0/3
(comm300)
Switch 1
Community
Port (access)
xe-0/0/6
(comm600)
Switch 2
g041292
Tag Tag
200 600
Table 21 on page 291 and Table 22 on page 292 list the settings for the example topology
on both switches.
Table 21: Components of the Topology for Configuring a Secondary VLAN Trunk on Switch 1
Component
Description
pvlan100, ID 100
Primary VLAN
pvlan400, ID 400
Primary VLAN
comm300, ID 300
comm600, ID 600
isolation-vlan-id 200
isolationvlan-id 500
xe-0/0/0.0
Secondary VLAN trunk port for primary VLANs pvlan100 and pvlan400
xe-0/0/1.0
xe-0/0/2.0
xe-0/0/3.0
xe-0/0/5.0
xe-0/0/6.0
291
Table 22: Components of the Topology for Configuring a Secondary VLAN Trunk on Switch 2
Component
Description
pvlan100, ID 100
Primary VLAN
pvlan400, ID 400
Primary VLAN
comm300, ID 300
comm600, ID 600
isolation-vlan-id 200
isolationvlan-id 500
xe-0/0/0.0
xe-0/0/1.0
xe-0/0/2.0
xe-0/0/3.0
xe-0/0/5.0
xe-0/0/6.0
To quickly create and configure the PVLANs on Switch 1, copy the following commands
and paste them into a switch terminal window:
[edit]
set interfaces xe-0/0/0 unit 0 family ethernet-switching port-mode trunk
set interfaces xe-0/0/1 unit 0 family ethernet-switching port-mode trunk
set interfaces xe-0/0/1 unit 0 family ethernet-switching vlan members pvlan100
set interfacesxe-0/0/1 unit 0 family ethernet-switching vlan members pvlan400
set interfaces xe-0/0/2 unit 0 family ethernet-switching port-mode access
set interfaces xe-0/0/3 unit 0 family ethernet-switching port-mode access
set interfaces xe-0/0/5 unit 0 family ethernet-switching port-mode access
set interfaces xe-0/0/6 unit 0 family ethernet-switching port-mode trunk
set vlans pvlan100 vlan-id 100
set vlans pvlan400 vlan-id 400
set vlans pvlan100 pvlan
set vlans pvlan400 pvlan
set vlans pvlan100 interface xe-0/0/1.0 pvlan-trunk
set vlans pvlan400 interface xe-0/0/1.0 pvlan-trunk
set vlans comm300 vlan-id 300
set vlans comm300 primary-vlan pvlan100
set vlans comm300 interface xe-0/0/3.0
set vlans comm600 vlan-id 600
set vlans comm600 primary-vlan pvlan400
set vlans comm600 interface xe-0/0/6.0
set vlans pvlan100 pvlan isolation-vlan-id 200
292
Step-by-Step
Procedure
2.
NOTE: Primary VLANs must always be tagged VLANs, even if they exist
on only one device.
3.
4.
Configure the PVLAN trunk port to carry the private VLAN traffic between the
switches:
[edit vlans]
user@switch# set pvlan100 interface xe-0/0/1.0 pvlan-trunk
user@switch# set pvlan400 interface xe-0/0/1.0 pvlan-trunk
5.
6.
7.
8.
9.
293
[edit vlans]
user@switch# set comm600 primary-vlan pvlan400
10.
11.
[edit vlans]
user@switch# set pvlan100 pvlan isolation-vlan-id 200
user@switch# set pvlan400 pvlan isolation-vlan-id 500
12.
Enable trunk port xe-0/0/0 to carry secondary VLANs for the primary VLANs:
[edit vlans]
user@switch# set pvlan100 interface xe-0/0/0.0 isolated
user@switch# set pvlan400 interface xe-0/0/0.0 isolated
13.
14.
Results
Check the results of the configuration on Switch 1:
[edit]
user@switch# show
interfaces {
xe-0/0/0 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members pvlan100;
members pvlan400;
294
}
}
}
}
xe-0/0/1 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members pvlan100;
members pvlan400;
}
}
}
}
xe-0/0/2 {
unit 0 {
family ethernet-switching {
port-mode access;
}
}
}
xe-0/0/3 {
unit 0 {
family ethernet-switching {
port-mode access;
}
}
}
xe-0/0/5 {
unit 0 {
family ethernet-switching {
port-mode access;
}
}
}
xe-0/0/6 {
unit 0 {
family ethernet-switching {
port-mode trunk;
}
}
}
}
vlans {
comm300 {
vlan-id 300;
interface {
xe-0/0/3.0;
}
primary-vlan pvlan100;
}
comm600 {
vlan-id 600;
interface {
xe-0/0/6.0;
295
}
primary-vlan pvlan400;
}
pvlan100 {
vlan-id 100;
interface {
xe-0/0/0.0;
xe-0/0/2.0;
xe-0/0/3.0;
xe-0/0/1.0 {
pvlan-trunk;
}
}
no-local-switching;
isolation-id 200;
}
pvlan400 {
vlan-id 400;
interface {
xe-0/0/0.0;
xe-0/0/5.0;
xe-0/0/6.0;
xe-0/0/1.0 {
pvlan-trunk;
}
}
no-local-switching;
isolation-id 500;
}
}
To quickly create and configure the PVLANs on Switch 2, copy the following commands
and paste them into a switch terminal window:
[edit]
set interfaces xe-0/0/0 unit 0 family ethernet-switching port-mode access
set interfaces xe-0/0/1 unit 0 family ethernet-switching port-mode trunk
296
Step-by-Step
Procedure
2.
3.
4.
Configure the PVLAN trunk port to carry the private VLAN traffic between the
switches:
[edit vlans]
user@switch# set pvlan100 interface xe-0/0/1.0 pvlan-trunk
user@switch# set pvlan400 interface xe-0/0/1.0 pvlan-trunk
5.
6.
297
7.
[edit vlans]
user@switch# set comm300 interface xe-0/0/3.0
8.
[edit vlans]
user@switch# set comm600 vlan-id 600
9.
[edit vlans]
user@switch# set comm600 primary-vlan pvlan400
10.
11.
[edit vlans]
user@switch# set pvlan100 pvlan isolation-vlan-id 200
user@switch# set pvlan400 pvlan isolation-vlan-id 500
12.
13.
Results
Check the results of the configuration on Switch 2:
[edit]
user@switch# show
interfaces {
xe-0/0/0 {
unit 0 {
family ethernet-switching {
port-mode access;
vlan {
members pvlan100;
}
}
}
}
xe-0/0/1 {
unit 0 {
family ethernet-switching {
port-mode trunk;
298
vlan {
members pvlan100;
members pvlan400;
}
}
}
}
xe-0/0/2 {
unit 0 {
family ethernet-switching {
port-mode trunk;
}
}
}
xe-0/0/3 {
unit 0 {
family ethernet-switching {
port-mode access;
}
}
}
xe-0/0/5 {
unit 0 {
family ethernet-switching {
port-mode access;
}
}
}
xe-0/0/6 {
unit 0 {
family ethernet-switching {
port-mode access;
}
}
}
vlans {
comm300 {
vlan-id 300;
interface {
xe-0/0/3.0;
}
primary-vlan pvlan100;
}
comm600 {
vlan-id 600;
interface {
xe-0/0/6.0;
}
primary-vlan pvlan400;
}
pvlan100 {
vlan-id 100;
interface {
xe-0/0/0.0;
xe-0/0/2.0;
xe-0/0/3.0;
299
xe-0/0/1.0 {
pvlan-trunk;
}
}
no-local-switching;
isolation-id 200;
}
pvlan400 {
vlan-id 400;
interface {
xe-0/0/5.0;
xe-0/0/6.0;
xe-0/0/1.0 {
pvlan-trunk;
}
}
no-local-switching;
isolation-id 500;
}
}
Verification
To confirm that the configuration is working properly, perform these tasks:
Verifying That the Private VLAN and Secondary VLANs Were Created on page 300
Verifying That the Private VLAN and Secondary VLANs Were Created
Purpose
Action
Verify that the primary VLAN and secondary VLANs were properly created on Switch 1.
Use the show vlans command:
user@switch> show vlans private-vlan
Meaning
Name
pvlan100
xe-0/0/3.0
__iso_pvlan100__
comm300
Role
Primary
Tag
100
Interfaces
xe-0/0/0.0, xe-0/0/1.0, xe-0/0/2.0,
Isolated
Community
200
300
xe-0/0/2.0
xe-0/0/3.0
pvlan400
xe-0/0/6.0
__iso_pvlan400__
comm600
Primary
400
Isolated
Community
500
600
xe-0/0/5.0
xe-0/0/6.0
The output shows that the private VLANs were created and identifies the interfaces and
secondary VLANs associated with them.
300
Verify that the Ethernet switching table entries were created for primary VLAN pvlan100.
Action
Related
Documentation
Understanding Secondary VLAN Trunk Ports and Promiscuous Access Ports on PVLANs
301
port, the device first locates the secondary bridge domain, based on secondary bridge
domain to find primary bridge domain identifier. If the destination MAC address is the
local IRB MAC address, the microcode transmits the packet to IRB interface associated
with primary bridge domain for further processing. The same procedure occurs for receiver
Layer 3 packets in an interswitch link (ISL) port with the isolated or community VLAN
tag.
For the ingress Layer 3 packet with Layer 3 forwarding logic sent to IRB interfaces
associated with a PVLAN bridge domain, the device processes and determines the ARP
entry to send packet to the related interface that might be an isolated port or a community
port. The microcode appends or translates the packet VLAN ID to the isolation or
community vlan ID based on the port type. The VLAN ID is removed if the related port is
untagged. A special operational case exists for Layer 3 packets that are forwarded to
remote isolated or community port through the ISL link. The Layer 3 packet might contain
the primary bridge domain VLAN ID and the remote node performs the translation or pop
operation when it sends the packet out on the related port. This method of processing
is different from Layer 2 domains. Because all forwarding base on ARP must be unicast
traffic and in the remote node, the port that must be used to forward is known and the
transmission of PVLAN ID occurs properly.
An ARP entry carries only the primary bridge domain information. When an ARP response
is received from an isolated port or a promiscuous port, the system identifies the secondary
bridge domain, and based on the secondary bridge domain, it attempts to retrieve the
primary bridge domain identifier. ARP packets eventually reach the IRB interface
associated with the primary bridge domain. The kernel considers this ARP packet as a
normal bridge domain and creates and maintains the ARP entry only for the primary
bridge domain. The same procedure is adopted for ARP request packets that are destined
for the local IRB MAC address. The response is transmitted through the IRB interface and
appropriate VLAN translation or a pop operation is performed, depending on the received
interface.
302
All of the IP applications such as IP multicast, IPv4, IPv6, and VRRP that are compatible
with IRB in normal bridge domains function properly when IRB for PVLAN bridge
domains is configured.
MC-LAG interfaces are not supported. All ports that are associated with PVLAN bridge
domains cannot be mc-ae interfaces.
A virtual switch instance that contains a bridge domain associated with logical
interfaces is supported.
Virtual private LAN service (VPLS) and Etherent VPN (EVPN) in virtual switch routing
instances are not supported. A validation is performed if you attempt to configure Layer
3 interfaces in a secondary VLAN.
303
the flooding in the remote PVLAN domain, a copy of the packet is sent to the ISL port.
The ISL port processes this packet as though it was received on the local isolated port
or community port and the aforementioned method of processing takes place
304
Created and configured the necessary VLANs. See Configuring VLAN Encapsulation
on page 256 and Enabling VLAN Tagging on page 246.
Configured MX240, MX480, and MX960 routers to function in enhanced LAN mode
by entering the network-services lan statement at the [edit chassis] hierarchy level.
You must reboot the router when you configure or delete the enhanced LAN mode on
the router. Configuring the network-services lan option implies that the system is running
in the enhanced IP mode. When you configure a device to function in MX-LAN mode,
only the supported configuration statements and operational show commands that
are available for enabling or viewing in this mode are displayed in the CLI interface.
If your system contains parameters that are not supported in MX-LAN mode in a
configuration file, you cannot commit those unsupported attributes. You must remove
the settings that are not supported and then commit the configuration. After the
successful CLI commit, a system reboot is required for the attributes to become
effective. Similarly, if you remove the network-services lan statement, the system does
not run in MX-LAN mode. Therefore, all of the settings that are supported outside of
the MX-LAN mode are displayed and are available for definition in the CLI interface. If
your configuration file contains settings that are supported only in MX-LAN mode, you
must remove those attributes before you commit the configuration. After the successful
CLI commit, a system reboot is required for the CLI parameters to take effect. The
Layer 2 Next-Generation CLI configuration settings are supported in MX-LAN mode.
As a result, the typical format of CLI configurations might differ in MX-LAN mode.
To configure an IRB interface in a PVLAN bridge domain associated with a virtual switch
instance:
1.
305
2. Create the interswitch link (ISL) trunk port for the PVLAN.
[edit interfaces]
user@host# set interface interface-name unit logical-unit-number family bridge
interface-mode trunk inter-switch-link
user@host# set interface interface-name unit logical-unit-number family bridge vlan-id
vlan-id
3. Create the isolated port for the PVLAN. The port is identified as an isolated port or a
community port, based on the VLAN ID or the list of VLAN IDs to which the interface
corresponds. For example, if you configure a port with a VLAN ID of 50, and if you
specify a VLAN ID of 50 as the isolated VLAN or tag in the bridge domain, the port is
considered as an isolation port.
[edit interfaces]
user@host# set interface interface-name unit logical-unit-number family bridge
interface-mode access
user@host# set interface interface-name unit logical-unit-number family bridge vlan-id
vlan-id
4. Create the community port for the PVLAN. The port is identified as an isolated port
or a community port, based on the VLAN ID or the list of VLAN IDs to which the interface
corresponds. For example, if you configure a port with a VLAN ID of 50, and if you
specify a VLAN ID of 50 as the community VLAN or tag in the bridge domain, the port
is considered as a community port.
[edit interfaces]
user@host# set interface interface-name unit logical-unit-number family bridge
interface-mode access
user@host# set interface interface-name unit logical-unit-number family bridge vlan-id
vlan-id
5. Create a virtual switch instance with a bridge domain and associate the logical
interfaces.
[edit routing-instances]
user@host# set routing-instance-name instance-type virtual-switch
user@host# set routing-instance-name interface interface-name unit
logical-unit-number
user@host# set routing-instance-name bridge-domains bridge-domain-name
6. Create an IRB interface and specify the IRB interface in the bridge domain associated
with the virtual switch instance. IRB provides simultaneous support for Layer 2 bridging
and Layer 3 IP routing on the same interface. IRB enables you to route local packets
to another routed interface or to another bridge domain that has a Layer 3 protocol
configured.
[edit]
user@host# set interfaces irb unit logical-unit-number family family-name address
ip-address
[edit routing-instances instance-name bridge-domains bridge-domain-name]
user@host# set routing-interface irb unit logical-unit-number
7. Specify the primary, isolated, and community VLAN IDs, and associate the VLANs
306
Related
Documentation
Requirements
This example uses the following hardware and software components:
Created and configured the necessary VLANs. See Configuring VLAN Encapsulation
on page 256 and Enabling VLAN Tagging on page 246.
Configured MX240, MX480, and MX960 routers to function in enhanced LAN mode
by entering the network-services lan statement at the [edit chassis] hierarchy level.
307
Assume a sample deployment in which a primary VLAN named VP contains ports, p1,
p2, t1, t2, i1, i2, cx1, and cx2. The port types of these configured ports are as follows:
Community VLAN = Cx
An IRB interface, irb.0, is configured and mapped to the bridge domain in the virtual switch
instance.
Bridge domains are provisioned for each of the VLANs, namely, Vp, Vi, and Vcx. Assume
the bridge domains to be configured as follows:
VpBD_primary_Vp (ports contained are p1, t1, i1, i2, cx1, cx2)
ViBD_isolate_Vi (ports contained are p1, t1, *i1, *i2)
VcxBD_community_Vcx (ports contained are p1, t1, cx1, cx2)
The bridge domains for community, primary, and isolated VLANs are automatically
created by the system internally when you configure a bridge domain with a trunk interface,
access interface, or interswitch link. The bridge domains contain the same VLAN ID
corresponding to the VLANs. To use bridge domains for PVLANs, you must configure the
following additional attributes:
Configuration
To configure an IRB interface in a PVLAN, perform these tasks:
CLI Quick
Configuration
Configuring an IRB
Interface
Configuring
Promiscuous, ISL,
Isolated, and
Community Ports
308
To quickly create and configure a PVLAN and include an IRB interface in a PVLAN bridge
domain associated with a virtual switch instance, copy the following commands and
paste them into the router terminal window:
set interfaces irb unit 0 family inet address 22.22.22.1/24
Configuring a Virtual
Switch Instance With
Bridge Domain
Interfaces
To configure the interswitch link (ISL) for a PVLAN, the PVLAN port types, and secondary
VLANs for the PVLAN:
1.
2.
3.
Create the interswitch link (ISL) trunk port for the PVLAN.
[edit interfaces]
user@host# set ge-0/0/13 unit 0 family bridge interface-mode trunk inter-switch-link
user@host# set ge-0/0/13 unit 0 family bridge vlan-id 100
4.
5.
309
6.
Create a virtual switch instance with a bridge domain and associate the logical
interfaces.
[edit routing-instances]
user@host# set vs-1 instance-type virtual-switch
user@host# set vs-1 interface ge-0/0/1.0
user@host# set vs-1 interface ge-0/0/2.0
user@host# set vs-1 interface ge-0/0/3.0
user@host# set vs-1 interface ge-0/0/4.0
user@host# set vs-1 interface ge-0/0/9.0
user@host# set vs-1 interface ge-0/0/10.0
user@host# set vs-1 interface ge-0/0/12.0
user@host# set vs-1 interface ge-0/0/13.0
user@host# set vs-1 bridge-domains bd1
7.
Specify the IRB interface, primary, isolated, and community VLAN IDs, and associate
the VLANs with the bridge domain.
[edit routing-instances vs1 bridge-domains bd1]
user@host# set vlan-id 100
user@host# set isolated-vlan 10
user@host# set community-vlans [50 60]
user@host# set routing-interface irb.0
Results
Check the results of the configuration:
[edit]
[interfaces]
ge-0/0/9 {
unit 0 {
family bridge {
interface-mode trunk;
vlan-id 100;
}
}
}
ge-0/0/13 {
unit 0 {
family bridge {
interface-mode trunk inter-switch-link; ISL trunk
vlan-id 100;
}
}
}
ge-0/0/10 {
unit 0 {
family bridge {
interface-mode access;
vlan-id 10;
isolated port by vlan ID
}
}
}
ge-0/0/12 {
310
unit 0 {
family bridge {
interface-mode access;
vlan-id 10;
isolated port by vlan ID
}
}
}
ge-0/0/1 {
unit 0 {
family bridge {
interface-mode access;
vlan-id 50;
community port by vlan ID
}
}
}
ge-0/0/2 {
unit 0 {
family bridge {
interface-mode access;
vlan-id 50;
community port by vlan ID
}
}
}
ge-0/0/3 {
unit 0 {
family bridge {
interface-mode access;
vlan-id 60;
community port by vlan ID
}
}
}
ge-0/0/4 {
unit 0 {
family bridge {
interface-mode access;
vlan-id 60;
community port by vlan ID
}
}
}
irb {
unit 0 {
family inet {
address 22.22.22.1/24;
}
}
}
[edit]
routing-instances {
vs-1 {
instance-type virtual-switch;
interface ge-0/0/1.0;
interface ge-0/0/2.0;
interface ge-0/0/3.0;
interface ge-0/0/4.0;
interface ge-0/0/9.0;
311
interface ge-0/0/10.0;
interface ge-0/0/12.0;
interface ge-0/0/13.0;
bridge-domains {
bd1 {
vlan-id 100;
/* primary vlan */
isolated-vlan 10;
community-vlans [50 60]
routing-interface irb.0 /* IRB interface */
}
}
}
Verification
To confirm that the configuration is working properly, perform these tasks:
Verifying That the Private VLAN and Secondary VLANs Were Created on page 312
Verifying That the Private VLAN and Secondary VLANs Were Created
Purpose
Action
Verify that the primary VLAN and secondary VLANs were properly created on the switch.
Use the show bridge domain command:
user@host> show bridge domain
Routing instance
Bridge domain
default-switch
bd1-primary-100
VLAN ID
Interfaces
100
ge-0/0/9.0
ge-0/0/10.0
ge-0/0/12.0
ge-0/0/13.0
ge-0/0/1.0
ge-0/0/2.0
ge-0/0/3.0
ge-0/0/4.0
default-switch
bd1-isolation-10
10
ge-0/0/9.0
ge-0/0/10.0
ge-0/0/12.0
ge-0/0/13.0
default-switch
bd1-comunity-50
50
ge-0/0/9.0
ge-0/0/13.0
ge-0/0/1.0
ge-0/0/2.0
default-switch
bd1-comunity-60
60
ge-0/0/9.0
ge-0/0/13.0
ge-0/0/3.0
ge-0/0/4.0
Meaning
312
The output shows that the primary VLAN was created and identifies the interfaces and
secondary VLANs associated with it.
Related
Documentation
313
314
CHAPTER 14
Related
Documentation
Route a packet if the destination MAC address is the MAC address of the router and
the packet ethertype is IPv4, IPv6, or MPLS.
Switch all multicast and broadcast packets within a bridging domain at layer 2.
Route a copy of the packet if the destination MAC address is a multicast address and
the ethertype is IPv4 or IPv6.
315
You can configure Layer 3 information on the IRB logical interface by including the irb
statement at the [edit interfaces] hierarchy level:
[edit interfaces]
irb {
unit logical-unit-number {
family inet {
address address {
}
}
}
}
For examples of Layer 2 bridging configuration, see the Junos OS Routing Protocols Library
for Routing Devices.
Related
Documentation
316
Requirements
This example requires the following hardware and software components:
Overview
Junos OS Release 13.2 and later support the assignment of MAC addresses to IRB logical
interfaces. The IRB logical interfaces provide support for simultaneous Layer 2 bridging
and Layer 3 routing within the same bridge domain. Packets that arrive on an interface
of the bridge domain are either switched or routed, based on the destination MAC address
of the packet. The packets with the routers Layer 2 virtual MAC address, which is manually
configured, are switched to Layer 2 interfaces.
Configuring a MAC address of an IRB logical interface allows the use of a transparent
firewall between two VLANs on the same switch. When both VLANs are on the same
subnet and traffic from one VLAN needs to go through the firewall to the host on the
other VLAN, then the VLAN tag is changed to communicate with the host on the other
VLAN.
Before the introduction of this feature, if the MAC address of an IRB logical interface was
the same for both VLANs, the firewall dropped the traffic. This new feature allows you
to configure distinct MAC addresses for different VLANs, which facilitates the exchange
of traffic between two VLANs on the same switch.
In case of VPLS multihoming, if there is a failover of the primary provider edge (PE) router
to a secondary PE router, the MAC address of an IRB changes. The hosts connected to
the customer edge (CE) router must change their Address Resolution Protocol (ARP)
for IRBs IP and MAC address. This feature allows you to configure the same MAC address
for IRB interfaces in both the primary and secondary PE routers and eliminates the need
for changing the ARP binding of the IRB logical interface in CE routers, in case of a failover.
Figure 21 on page 318 shows the sample topology.
317
lo0 = 4.4.4.4/32
lo0 = 5.5.5.5/32
R0
R1
ge-1/3/8 (IRB)
1.1.23.20/24
MAC 00:00:00:00:00:02ge-1/2/8 (IRB)
1.1.22.30/24
MAC 00:00:00:00:00:03
ge-1/3/8 (IRB)
1.1.23.10/24
MAC 00:00:00:00:00:01
ge-1/2/8 (IRB)
1.1.22.40/24
MAC 00:00:00:00:00:04
lo0 = 6.6.6.6/32
g040936
R2
Configuration
CLI Quick
Configuration
Router R0
318
To quickly configure this example, copy the following commands, paste them into a text
file, remove any line breaks, change any details necessary to match your network
configuration, and then copy and paste the commands into the CLI at the [edit] hierarchy
level.
set interfaces ge-1/3/8 vlan-tagging
set interfaces ge-1/3/8 encapsulation flexible-ethernet-services
set interfaces ge-1/3/8 unit 10 encapsulation vlan-bridge
set interfaces ge-1/3/8 unit 10 vlan-id 10
set interfaces irb unit 10 family inet address 1.1.23.1/24
set interfaces irb unit 10 family mpls
set interfaces irb unit 10 mac 00:00:00:00:00:01
set interfaces lo0 unit 10 family inet address 4.4.4.4/32
set protocols rsvp interface irb.10
set protocols mpls label-switched-path R0-1-R2 to 6.6.6.6
set protocols mpls label-switched-path R0-1-R2 install 6.6.6.6/32 active
set protocols mpls label-switched-path R0-1-R2 no-cspf
set protocols mpls interface irb.10
set protocols bgp group ibgp type internal
set protocols bgp group ibgp local-address 4.4.4.4
set protocols bgp group ibgp neighbor 6.6.6.6
set protocols ospf area 0.0.0.0 interface irb.10
set protocols ospf area 0.0.0.0 interface lo0.10 passive
set protocols ldp interface irb.10
set protocols ldp interface lo0.10
set routing-options autonomous-system 400
set bridge-domains lsbd1 vlan-id 10
set bridge-domains lsbd1 interface ge-1/3/8.10
Router R1
Router R2
319
The following example requires that you navigate various levels in the configuration
hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration
Mode in the CLI User Guide.
NOTE: Repeat this procedure for Juniper Networks Routers R1 and R2,
modifying the appropriate interface names, addresses, and any other
parameters for each router.
2.
3.
4.
5.
320
6.
7.
8.
9.
Results
From configuration mode, enter the show interfaces, show protocols and show
bridge-domains, commands and confirm your configuration. If the output does not
display the intended configuration, repeat the instructions in this example to correct the
configuration.
user@R0# show interfaces
ge-1/3/8 {
unit 10 {
encapsulation vlan-bridge;
vlan-id 10;
}
}
irb {
unit 10 {
family inet {
mtu 1450;
address 1.1.1.1/24;
address 1.1.23.1/24;
}
family mpls;
mac 00:00:00:00:00:01;
}
}
lo0 {
unit 10 {
family inet {
address 4.4.4.4/32;
}
}
}
user@R0# show protocols
321
rsvp {
interface irb.10;
}
mpls {
label-switched-path R0-1-R2 {
to 6.6.6.6;
install 6.6.6.6/32 active;
no-cspf;
}
interface irb.10;
}
bgp {
group ibgp {
type internal;
local-address 4.4.4.4;
neighbor 6.6.6.6;
}
}
ospf {
area 0.0.0.0 {
interface irb.10;
interface lo0.10 {
passive;
}
}
}
ldp {
interface irb.10;
interface lo0.10;
}
user@R0# show bridge-domains
lsbd1 {
vlan-id 10;
interface ge-1/3/8.10;
routing-interface irb.10;
}
Verification
Confirm that the configuration is working properly.
322
Verify that the specified MAC address is assigned to the IRB interface.
Action
From operational mode, run the show interfaces irb command on the device.
user@host# show interfaces irb
Physical interface: irb, Enabled, Physical link is Up
Interface index: 132, SNMP ifIndex: 505
Type: Ethernet, Link-level type: Ethernet, MTU: 1514
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Current address: 80:71:1f:c2:58:f0, Hardware address: 80:71:1f:c2:58:f0
Last flapped
: Never
Input packets : 0
Output packets: 0
Logical interface irb.10 (Index 326) (SNMP ifIndex 634)
Flags: SNMP-Traps 0x0 Encapsulation: ENET2
MAC: 00:00:00:00:00:01
Bandwidth: 1000mbps
Routing Instance: LS1/default Bridging Domain: lsbd1+10
Input packets : 55202
Output packets: 69286
Protocol inet, MTU: 1450
Flags: Sendbcast-pkt-to-re, Is-Primary, User-MTU
Addresses, Flags: Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.1, Broadcast: 1.1.1.255
Addresses, Flags: Is-Preferred
Destination: 1.1.23/24, Local: 1.1.23.1, Broadcast: 1.1.23.255
Protocol mpls, MTU: 1500, Maximum labels: 3
Flags: Is-Primary
Protocol multiservice, MTU: 1500
Logical interface irb.20 (Index 358) (SNMP ifIndex 635)
Flags: SNMP-Traps 0x0 Encapsulation: ENET2
MAC: 00:00:00:00:00:02
Bandwidth: 1000mbps
Routing Instance: LS2/default Bridging Domain: lsbd2+10
Input packets : 66044
Output packets: 68464
Protocol inet, MTU: 1450
Flags: Sendbcast-pkt-to-re, Is-Primary, User-MTU
Addresses, Flags: Is-Preferred Is-Primary
Destination: 1.1.1/24, Local: 1.1.1.2, Broadcast: 1.1.1.255
Addresses, Flags: Is-Preferred
Destination: 1.1.23/24, Local: 1.1.23.2, Broadcast: 1.1.23.255
Protocol mpls, MTU: 1500, Maximum labels: 3
Flags: Is-Primary
Protocol multiservice, MTU: 1500
Logical interface irb.30 (Index 360) (SNMP ifIndex 636)
Flags: SNMP-Traps 0x0 Encapsulation: ENET2
MAC: 00:00:00:00:00:03
Bandwidth: 1000mbps
Routing Instance: LS2/default Bridging Domain: lsbd3+40
Input packets : 26948
Output packets: 53605
Protocol inet, MTU: 1500
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
323
Meaning
The output shows the manually configured MAC address in the MAC field.
NOTE: If you did not configure the MAC address for a logical interface, the
output does not include this value. However, the device uses the MAC address
of the physical interface during data transmission.
Related
Documentation
324
Active-Active Bridging and VRRP over IRB Functionality on MX Series Routers Overview
CHAPTER 15
LLDP Overview
The Link Layer Discovery Protocol (LLDP) is an industry-standard, vendor-neutral method
to allow networked devices to advertise capabilities, identity, and other information onto
a LAN. The Layer 2 protocol, detailed in IEEE 802.1AB-2005, replaces several proprietary
protocols implemented by individual vendors for their equipment.
LLDP allows network devices that operate at the lower layers of a protocol stack (such
as Layer 2 bridges and switches) to learn some of the capabilities and characteristics of
LAN devices available to higher layer protocols, such as IP addresses. The information
gathered through LLDP operation is stored in a network device and is queried with SNMP.
Topology information can also be gathered from this database.
Some of the information that can be gathered by LLDP (only minimal information is
mandatory) is:
Power information
325
LLDP frames are sent at fixed intervals on each port that runs LLDP. LLDP protocol data
units (LLDP PDUs) are sent inside Ethernet frames and identified by their destination
Media Access Control (MAC) address (01:80:C2:00:00:0E) and Ethertype (0x88CC).
Mandatory information supplied by LLDP is chassis ID, port ID, and a time-to-live value
for this information.
LLDP is a powerful way to allow Layer 2 devices to gather details about other
network-attached devices.
Related
Documentation
Configuring LLDP
You configure LLDP by including the lldp statement and associated parameters at the
[edit protocols] hierarchy level. The complete set of LLDP statements follows:
lldp {
advertisement-interval seconds;
disable;
hold-multiplier number;
interface (all | interface-name) {
disable;
}
lldp-configuration-notification-interval seconds;
management-address ip-management-address;;
port-description-type {
interface-alias;
interface-description;
}
port-id-subtype {
interface-name;
locally-assigned;
}
ptopo-configuration-maximum-hold-time seconds;
ptopo-configuration-trap-interval seconds;
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable>;
flag flag <flag-modifier> <disable>;
}
transmit-delay seconds
}
326
8192 seconds.
The following statements must be explicitly configured:
Starting with Junos OS Release 14.2, you can configure management interfaces, such as
fxp0 or me0, on MX Series routers to send LLDP frames to and receive LLDP frames from
neighboring LLDP interfaces by including the interface interface-name statement at the
[edit protocols lldp] and [edit routing-instances routing-instance-name protocols lldp]
hierarchy levels. By default, the functionality to send LLDP frames is enabled. You can
also specify a management interface with the show lldp neighbors interface interface-name
command to view configuration details about LLDP neighbors for the corresponding
management interface.
To configure LLDP on a T Series router within a TX Matrix, you must specify the interface
name in the LLDP configuration for the TX Matrix. For information about interface names
for TX Matrix routers, see TX Matrix Router Chassis and Interface Names. For information
about FPC numbering, see Routing Matrix with a TX Matrix Router FPC Numbering.
327
LLDP is supported on extended ports in the Junos Fusion technology. For information
about interface names in the Junos Fusion technology, see Understanding Junos Fusion
Ports.
The advertisement interval determines the frequency that an LLDP interface sends LLDP
advertisement frames. The default value is 30 seconds. The allowable range is from 5
through 32768 seconds. You adjust this parameter by including the advertisement-interval
statement at the [edit protocols lldp] hierarchy level.
The hold multiplier determines the multiplier to apply to the advertisement interval. The
resulting value in seconds is used to cache learned LLDP information before discard. The
default value is 4. When used with the default advertisement interval value of 30 seconds,
this makes the default cache lifetime 120 seconds. The allowable range of the hold
multiplier is from 2 through 10. You adjust this parameter by including the hold-multiplier
statement at the [edit protocols lldp] hierarchy level.
The transmit delay determines the delay between any two consecutive LLDP
advertisement frames. The default value is 2 seconds. The allowable range is from 1
through 8192 seconds. You adjust this parameter by including the transmit-delay
statement at the [edit protocols lldp] hierarchy level.
The physical topology configuration maximum hold time determines the time interval
for which an agent device maintains physical topology database entries. The default
value is 300 seconds. The allowable range is from 1 through 2147483647 seconds. You
adjust this parameter by including the ptopo-configuration-maximum-hold-time statement
at the [edit protocols lldp] hierarchy level.
The LLDP configuration notification interval determines the period for which trap
notifications are sent to the SNMP Master Agent when changes occur in the database
of LLDP information. This capability is disabled by default. The allowable range is from 0
(disabled) through 3600 seconds. You adjust this parameter by including the
lldp-configuration-notification-interval statement at the [edit protocols lldp] hierarchy
level.
The physical topology configuration trap interval determines the period for which trap
notifications are sent to the SNMP Master Agent when changes occur in the global
physical topology statistics. This capability is disabled by default. The allowable range
is from 0 (disabled) through 3600 seconds. The LLDP agent sends traps to the SNMP
Master Agent if this interval has a value greater than 0 and there is any change during
the lldp-configuration-notification-interval trap interval. You adjust this parameter by
including the ptopo-configuration-trap-interval statement at the [edit protocols lldp]
hierarchy level.
By default, LLDP generates the SNMP index of the interface for the port ID Type, Length,
and Value (TLV). Starting with Junos OS Release 12.3R1, you can generate the interface
name as the port ID TLV by including the interface-name statement at the [edit protocols
lldp port-id-subtype] hierarchy level. When the interface-name statement is configured
on the remote LLDP neighbor, the show lldp neighbors command output displays the
interface name in the Port ID field rather than the SNMP index of the interface, which is
displayed by default. If you change the default behavior of generating the SNMP index
328
of the interface as the Port ID TLV, you can reenable the default behavior by including
the locally-assigned statement at the [edit protocols lldp port-id-subtype] hierarchy level.
NOTE: The value of the MIB variable lldpLocPortId depends on the SNMP
MIB object entity that is used to generate the port ID TLV. If the port ID TLV
generation is configured to use the interface name in the set port-id-subtype
interface-name command, then the value of the MIB variable lldpLocPortId
is the interface name and not the SNMP index.
Related
Documentation
329
You can display basic information about LLDP with the show lldp detail command:
user@host> show lldp detail
LLDP
:
Advertisement interval :
Transmit delay
:
Hold timer
:
Notification interval :
Config Trap Interval
:
Connection Hold timer :
Interface
ge-1/1/1
LLDP
Enabled
Enabled
30 Second(s)
2 Second(s)
4 Second(s)
30 Second(s)
300 Second(s)
60 Second(s)
Neighbor count
0
For more details about the output of these commands, see the CLI Explorer.
Related
Documentation
You can specify the following LLDP-specific options in the LLDP traceoptions statement:
330
NOTE: Use the trace flag all with caution. This flag may cause the CPU to
become very busy.
For general information about tracing and global tracing options, see the statement
summary for the global traceoptions statement in the Junos OS Routing Protocols Library
for Routing Devices.
Related
Documentation
331
332
CHAPTER 16
Ethernet
Fast Ethernet
Gigabit Ethernet
VRRP and VRRP for IPv6 allow hosts on a LAN to make use of redundant routers on that
LAN without requiring more than the static configuration of a single default route on the
hosts. The VRRP routers share the IP address corresponding to the default route
configured on the hosts. At any time, one of the VRRP routers is the master (active) and
the others are backups. If the master fails, one of the backup routers becomes the new
master router, thus always providing a virtual default router and allowing traffic on the
LAN to be routed without relying on a single router.
VRRP is defined in RFC 3768, Virtual Router Redundancy Protocol.
For VRRP and VRRP for IPv6 overview information, configuration guidelines, and
statement summaries, see the Junos OS High Availability Library for Routing Devices.
Related
Documentation
333
When there are multiple VRRP groups, there is a few seconds delay between the time
the first gratuitous ARP is sent out and the rest of the gratuitous ARP are sent. Configuring
failover-delay compensates for this delay. To configure the failover delay from 500 to
2000 milliseconds for VRRP and VRRP for IPv6 operations, include the failover-delay
milliseconds statement at the [edit protocols vrrp] hierarchy level:
[edit protocols vrrp]
failover-delay milliseconds;
334
To configure the startup period for VRRP and VRRP for IPv6 operations, include the
startup-silent-period statement at the [edit protocols vrrp] hierarchy level:
[edit protocols vrrp]
startup-silent-period seconds;
To enable VRRPv3, set the version-3 statement at the [edit protocols vrrp] hierarchy
level:
[edit protocols vrrp]
version-3;
Related
Documentation
vrrp-group
335
336
CHAPTER 17
Configuring the Number and Size of PPPoE Log Files on page 350
Configuring the Severity Level to Filter Which PPPoE Messages Are Logged on page 351
337
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.
To use PPPoE, you must configure the router as a PPPoE client, encapsulate PPP packets
over Ethernet, and initiate a PPPoE session.
M120, M320, and MX Series routers can be configured as a PPPoE access concentrator
server. To configure a PPPoE server on an M120, M320, or MX Series Ethernet logical
interface, specify PPPoE encapsulation, include the pp0 statement for the pseudo PPPoE
physical interface, and include the server statement in the PPPoE options under the
logical interface.
Multiple hosts can be connected to the Services Router, and their data can be
authenticated, encrypted, and compressed before the traffic is sent to the PPPoE session
on the Services Routers Fast Ethernet or ATM-over-ADSL interface. PPPoE is easy to
configure and enables services to be managed on a per-user basis rather than on a
per-site basis.
This overview contains the following topics:
PPPoE Interfaces
The 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 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.
Ethernet Interface
The Services Router encapsulates each PPP frame in an Ethernet frame and transports
the frames over an Ethernet loop. Figure 22 on page 339 shows a typical PPPoE session
between a Services Router and an access concentrator on the Ethernet loop.
338
PPPoE Stages
PPPoE has two stages, the discovery stage and the PPPoE session stage. In the discovery
stage, the client discovers the access concentrator by identifying the Ethernet media
access control (MAC) address of the access concentrator and establishing a PPPoE
session ID. In the PPPoE session stage, the client and the access concentrator build a
point-to-point connection over Ethernet, based on the information collected in the
discovery stage.
NOTE: A Services Router cannot receive PPPoE packets from two different
access concentrators on the same physical interface.
2. 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. An
access concentrator can also use the PADO packet to offer other services to the client.
339
3. PPPoE active discovery request (PADR)From the PADOs it receives, the client selects
one access concentrator based on its name or the services offered and sends it a
PADR packet to indicate the service or services needed.
4. PPPoE active discovery session-Confirmation (PADS)When the selected access
concentrator receives the PADR packet, it accepts or rejects the PPPoE session.
To accept the session, the access concentrator sends the client a PADS packet
with a unique session ID for a PPPoE session and a service name that identifies the
service under which it accepts the session.
To reject the session, the access concentrator sends the client a PADS packet with
a service name error and resets the session ID to zero.
340
Evaluation Order for Matching Client Information in PPPoE Service Name Tables
Configuring the Action Taken When the Client Request Includes an Empty Service Name
Tag
Assigning a Service to a Service Name Table and Configuring the Action Taken When the
Client Request Includes a Non-zero Service Name Tag
Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the
Client Request Includes ACI/ARI Information
Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
Configuring PPPoE
To configure PPPoE on an M120 or M320 Multiservice Edge Router or MX Series Universal
Edge Router operating as an access concentrator, perform the following tasks:
1.
2. Specify the logical Ethernet interface as the underlying interface for the PPPoE session.
3. Optionally, configure the maximum transmission unit (MTU) of the interface.
4. Configure the operational mode as server.
5. Configure the PPPoE interface address.
6. Configure the destination PPPoE interface address.
7. Optionally, configure the MTU size for the protocol family.
341
8. Optionally, configure one or more PPPoE service name tables and the action taken
Perform the task appropriate for the interface on which you are using PPPoE:
342
Deriving the PPPoE Source Address from a Specified Interface on page 346
Example: Configuring a PPPoE Server Interface on an M120 or M320 Router on page 347
NOTE: When you configure a static PPPoE logical interface, you must include
the pppoe-options subhierarchy at the [edit interfaces pp0 unit
logical-unit-number] hierarchy level or at the [edit logical-systems
logical-system-name interfaces pp0 unit logical-unit-number] hierarchy level.
If you omit the pppoe-options subhierarchy from the configuration, the commit
operation fails.
343
Specify the logical Ethernet, Fast Ethernet, Gigabit Ethernet, 10-Gigabit Ethernet, or ATM
interface as the underlying interfacefor example, at-0/0/1.0 (ATM VC), fe-1/0/1.0 (Fast
Ethernet interface), or ge-2/0/0 (Gigabit Ethernet interface).
You can configure the reconnection attempt to occur in 0 through 4,294,967,295 seconds
after the session terminates.
344
345
You can modify the MTU size of the interface by including the mtu bytes statement at
the [edit interfaces pp0] hierarchy level:
[edit interfaces pp0]
mtu bytes;
The default media MTU size used and the range of available sizes on a physical interface
depends on the encapsulation used on that interface.
346
Related
Documentation
Related
Documentation
You can use show commands to display and verify the PPPoE configuration.
347
Action
To verify a PPPoE configuration, you can issue the following operational mode commands:
For more information about these operational mode commands, see CLI Explorer.
Related
Documentation
Important events are logged in a file called pppoed located in the /var/log directory.
You cannot change the directory (/var/log) in which trace files are located.
2. When the file pppoed reaches 128 kilobytes (KB), it is renamed pppoed.0, then pppoed.1,
and finally pppoed.2, until there are three trace files. Then the oldest trace file
(pppoed.2) is overwritten.
You can optionally specify the number of trace files to be from 2 through 1000. You
can also configure the maximum file size to be from 10 KB through 1 gigabyte (GB).
(For more information about how log files are created, see the Junos OS System Log
Messages Reference.)
By default, only the user who configures the tracing operation can access log files. You
can optionally configure read-only access for all users.
To configure PPPoE tracing operations:
1.
2. (Optional) Configure the name for the file used for the trace output.
348
Configuring the Number and Size of PPPoE Log Files on page 349
349
Related
Documentation
350
Related
Documentation
Configuring the Severity Level to Filter Which PPPoE Messages Are Logged
The messages associated with a logged event are categorized according to severity level.
You can use the severity level to determine which messages are logged for the event
type. The severity level that you configure depends on the issue that you are trying to
resolve. In some cases you might be interested in seeing all messages relevant to the
logged event, so you specify all or verbose. Either choice generates a large amount of
output. You can specify a more restrictive severity level, such as notice or info to filter the
messages . By default, the trace operation output includes only messages with a severity
level of error.
To configure the type of messages to be logged:
351
Related
Documentation
352
CHAPTER 18
NOTE: From Junos OS Release 10.0 onward, Junos OS does not respond to
proxy ARP requests with the default route 0.0.0.0. This behavior is in
compliance with RFC 1027.
353
WARNING: If you configure unrestricted proxy ARP, the proxy router replies
to ARP requests for the target IP address on the same interface as the
incoming ARP request. This behavior is appropriate for cable modem
termination system (CMTS) environments, but might cause Layer 2
reachability problems if you enable unrestricted proxy ARP in other
environments.
When an IP client broadcasts the ARP request across the Ethernet wire, the end node
with the correct IP address responds to the ARP request and provides the correct MAC
address. If the unrestricted proxy ARP feature is enabled, the router response is redundant
and might fool the IP client into determining that the destination MAC address within its
own subnet is the same as the address of the router.
NOTE: While the destination address can be remote, the source address of
the ARP request must be on the same subnet as the interface upon which
the ARP request is received. For security reasons, this rule applies to both
unrestricted and restricted proxy ARP.
354
Related
Documentation
You can track the number of restricted or unrestricted proxy ARP requests processed by
the router or switch by issuing the show system statistics arp operational mode command.
355
Related
Documentation
356
CHAPTER 19
The IP address that you specify must be part of the subnet defined in the enclosing
address statement.
To associate a multicast MAC address with a unicast IP address, include the multicast-mac
statement.
Specify the MAC address as six hexadecimal bytes in one of the following formats:
nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn; for example, 0011.2233.4455 or 00:11:22:33:44:55.
For unicast MAC addresses only, if you include the publish option, the router or switch
replies to proxy ARP requests.
357
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 arp 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. This feature is not available on EX Series
switches.
When you need to conserve IP addresses, you can configure an Ethernet
interface to be unnumbered by including the unnumbered-address statement
at the [edit interfaces interface-name unit logical-unit-number family inet]
hierarchy level.
NOTE: The Junos OS supports the IPv6 static neighbor discovery cache
entries, similar to the static ARP entries in IPv4.
Related
Documentation
358
Applying Policers
CHAPTER 20
359
Additionally, configure the logical interface by including the proxy and remote statements:
proxy {
inet-address;
}
remote {
(inet-address | mac-address);
}
The proxy address is the IP address of the non-Ethernet TCC neighbor for which the TCC
router is acting as a proxy.
The remote address is the IP or MAC address of the remote router. The remote statement
provides ARP capability from the TCC switching router to the Ethernet neighbor. The
MAC address is the physical Layer 2 address of the Ethernet neighbor.
When VLAN TCC encapsulation is configured on the logical interface, you also must
specify flexible Ethernet services on the physical interface. To specify flexible Ethernet
services, include the encapsulation statement at the [edit interfaces interface-name]
hierarchy level and specify the flexible-ethernet-services option:
[edit interfaces interface-name]
encapsulation flexible-ethernet-services;
Extended VLAN TCC encapsulation supports TPIDs 0x8100 and 0x9901. Extended VLAN
TCC is specified at the physical interface level. When configured, all units on that interface
must use VLAN TCC encapsulation, and no explicit configuration is needed on logical
interfaces.
One-port Gigabit Ethernet, 2-port Gigabit Ethernet, and 4-port Fast Ethernet PICs with
VLAN tagging enabled can use VLAN TCC encapsulation. To configure the encapsulation
on a physical interface, include the encapsulation statement at the [edit interfaces
interface-name] hierarchy level and specify the extended-vlan-tcc option:
[edit interfaces interface-name]
encapsulation extended-vlan-tcc;
For VLAN TCC encapsulation, all VLAN IDs from 1 through 1024 are valid. VLAN ID 0 is
reserved for tagging the priority of frames.
Extended VLAN TCC is not supported on 4-port Gigabit Ethernet PICs.
Related
Documentation
360
For Ethernet TCC encapsulation, you must also configure the logical interface by including
the proxy and remote statements:
proxy {
inet-address;
}
remote {
(inet-address | mac-address);
}
The proxy address is the IP address of the non-Ethernet TCC neighbor for which the TCC
router is acting as a proxy.
The remote address is the IP or MAC address of the remote router. The remote statement
provides ARP capability from the TCC switching router to the Ethernet neighbor. The
MAC address is the physical Layer 2 address of the Ethernet neighbor.
Ethernet TCC is supported on interfaces that carry IPv4 traffic only. For 8-port, 12-port,
and 48-port Fast Ethernet PICs, TCC and extended VLAN CCC are not supported. For
4-port Gigabit Ethernet PICs, extended VLAN CCC and extended VLAN TCC are not
supported.
361
If traffic flows from Router A to Router C, the Junos OS strips all PPP encapsulation data
from incoming packets and adds Ethernet encapsulation data before forwarding the
packets. If traffic flows from Router C to Router A, the Junos OS strips all Ethernet
encapsulation data from incoming packets and adds PPP encapsulation data before
forwarding the packets.
On Router B
interfaces
The Router A-to-Router B circuit is PPP, and the Router B-to-Router C circuit is Ethernet
with VLAN tagging enabled.
On Router B
Related
Documentation
362
interfaces
ge-0/0/0 {
vlan-tagging;
encapsulation extended-vlan-tcc;
unit 0 {
vlan-id 1;
family tcc {
proxy {
inet-address 10.10.10.3;
}
remote {
inet-address 10.10.10.2;
}
}
}
PART 2
363
364
CHAPTER 21
12-port 10-Gigabit Ethernet LAN/WAN PIC on Type 5 FPC Overview on page 369
24-port 10-Gigabit Ethernet LAN/WAN PIC on Type 5 FPC Overview on page 371
Line-rate operation for five 10-Gigabit Ethernet ports from each port group, or a total
WAN bandwidth of 100 Gbps with Packet Forwarding Engine bandwidth of 50 Gbps
Flexible encapsulation, source address and destination address media access control
(MAC) filtering, source address MAC learning, MAC accounting, and MAC policing
365
ethernet-cccEthernet cross-connect
cross-connect
NOTE: The T4000 Core Router supports only LAN PHY mode in Junos OS
Release 12.1R1. Starting with Junos OS Release 12.1R2, WAN PHY mode is
supported on the T4000 routers with the 12-port 10-Gigabit Ethernet
LAN/WAN PIC with SFP+ (PF-12XGE-SFPP). Starting with Junos OS Release
12.2, WAN PHY mode is supported on the T4000 routers with the 24-port
10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PF-24XGE-SFPP).
Maximum transmission unit (MTU) size of up to 9192 bytes for Ethernet frames
Interoperability with other 10-Gigabit Ethernet PICs in M Series and T Series routers in
the LAN PHY and WAN PHY modes
366
Four queues per physical interface on ingress and eight queues per physical interface
on egress
A separate control queue per physical interface to ensure that the control packets are
not dropped during oversubscribed traffic. The control queue can be disabled in the
CLI.
Optical diagnostics
Behavior aggregate (BA) classification (IPv4 DSCP, IPv6 DSCP, Inet precedence, IEEE
802.1P, IEEE 802.1AD, MPLS EXP) and fixed classification
Weighted round-robin scheduling with two queue priorities (low and strict-high)
Committed information rate and peak information rate shaping on a per-queue basis
Link discovery
Linktrace
Loopback
The 10-port 10-Gigabit Ethernet LAN/WAN PIC has the following caveats:
Source address and destination address MAC filtering takes place after oversubscription
is handled.
Oversubscription on the PIC operates across a port group of two ports and not at the
PIC level.
Committed information rate and peak information rate configurations are not supported
at the physical interface level.
367
classification at the Packet Forwarding Engine occurs after the PIC handles the
oversubscribed traffic.
Non-standard TPID for VLAN tagging is not supported, except for 0x8100.
The guaranteed-rate and shaping-rate statements are not supported at the IFD level.
Only the strict-high and low levels of scheduling priorities are supported.
Table 23 on page 368 10-port 10-Gigabit Ethernet LAN/WAN PIC with SFP+
(PD-5-10XGE-SFPP).
368
Capability
Support
4065
1022
Support
960
960
MAC policers
Classifers
Related
Documentation
Logical interfacelevel MAC filtering, accounting, policing, and learning for source
media access control (MAC).
Flexible encapsulation.
Maximum transmission unit (MTU) size of up to 9192 bytes for Ethernet frames.
369
Interoperability with other 10-Gigabit Ethernet PICs on M Series and T Series routers
in LAN PHY mode.
Behavior aggregate (BA) classification (IPv4 DSCP, IPv6 DSCP, Inet precedence, IEEE
802.1P, IEEE 802.1AD, MPLS EXP) and fixed classification.
Defining the VLAN rewrite operation to be applied to the incoming and outgoing frames
on logical interfaces on this PIC.
You can configure only one logical interface (unit 0) on the port.
You cannot include the vlan-id statement in the configuration of the logical
interface.
vlan-taggingEnable VLAN tagging for all logical interfaces on the physical interface.
physical interface.
ethernet-cccEthernet cross-connect.
cross-connect.
translational cross-connect.
370
IPv4
IPv6
MPLS
NOTE: The T4000 Core Router supports only LAN PHY mode in Junos OS
Release 12.1R1. Starting with Junos OS Release 12.1R2, WAN PHY mode is
supported on T4000 routers with 12-port 10-Gigabit Ethernet LAN/WAN
PIC with SFP+.
The 10-Gigabit Ethernet LAN/WAN PIC on Type 5 FPC does not support:
MAC filtering, accounting, and policing for destination MAC at the logical interface
level.
Multiple TPIDs
Capability
Support
32,000
Classifers
Related
Documentation
371
The following major software features are supported on the 24-port 10-Gigabit Ethernet
LAN/WAN PIC with SFP+ (model number PF-24XGE-SFPP):
The output of the show interfaces extensive operational mode command now displays
preclassification queue counters.
Line-rate mode operation of the first 12 ports can be achieved by using the [set chassis
fpc fpc-number pic pic-number linerate-mode] command. By default, the 24-port
10-Gigabit Ethernet LAN/WAN PIC with SFP+ works in oversubscribed mode.
LAN PHY mode and WAN PHY mode on a per-port basis. WAN PHY mode can be
achieved by using the [set interfaces interface-name framing wan-phy] command.
4000 logical interfaces per physical interface and 32,000 logical interfaces per chassis.
Related
Documentation
372
12-port 10-Gigabit Ethernet LAN/WAN PIC on Type 5 FPC Overview on page 369
Line-rate modeBy default, the 12-port 10-Gigabit Ethernet LAN/WAN PIC with SFP+
(PF-12XGE-SFPP) operates in line-rate mode.
In a 24-port 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PF-24XGE-SFPP), 12 ports
(ports 011)can operate in line-rate mode . To configure the PF-24XGE-SFPP PIC to
operate in line-rate mode, include the linerate-mode statement at the [edit chassis set
fpc fpc-number pic pic-number] hierarchy level.
Oversubscribed modeIn this mode, all ports on the PIC are enabled with two-to-one
oversubscription. In a PF-24XGE-SFPP PIC, by default, two-to-one oversubscription
of traffic is achieved in oversubscribed modeTraffic from 24 ingress ports to the
Packet Forwarding Engine is statically mapped to one of the 12 egress ports. 10 Gbps
of bandwidth traffic moving toward the Packet Forwarding Engine is shared by two
ingress ports (called a port group), thereby achieving two-to-one oversubscription.
This scheme provides two-to-one oversubscription across a port group and not across
the entire PIC.
Related
Documentation
373
[edit chassis]
set fpc fpc-number pic pic-number linerate-mode;
NOTE: When the mode of operation of a PIC is changed, the PIC is taken
offline and then brought back online immediately.
Related
Documentation
24-port 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (model number PF-24XGE-SFPP)
24-port 10-Gigabit Ethernet LAN/WAN PIC on Type 5 FPC Overview on page 371
374
OSPF
OSPF3
VRRP
IGMP
RSVP
PIM
BGP
BFD
LDP
IS-IS
RIP
RIPV6
LACP
ARP
IPv6 NDP
These control packets can either terminate locally or transit through the router. The
control queue has a rate limiter to limit the control traffic to 2 Mbps (fixed, not
user-configurable) per port. Hence, if transit control traffic is taking too much bandwidth,
then it can cause drops on locally terminating control traffic, as shown in
Figure 26 on page 375.
End-user A
End-user B
Provider network
g017487
If the end users generate a mass of malicious traffic for which the port number is 179
(BGP), the router dispatches that traffic to the ingress control queue. Further, if congestion
occurs in this ingress control queue due to this malicious traffic, the provider's network
control packets may be affected.
In some applications, this can be perceived as a new vulnerability. To address this concern,
you can disable the control queue feature. With the control queue feature disabled, you
must take precautions to protect control traffic through other means, such as mapping
control packets (using BA classification) to a queue that is marked strict-high or is
configured with a high CIR.
You can disable the control queue for all ports on the PIC. To disable the control queue,
use the set chassis fpc n pic n no-pre-classifier command. By default, the no-pre-classifier
statement is not configured and the control queue is operational.
Deleting the no-pre-classifier statement re-enables the control queue feature on all ports
of the 10-Gigabit Ethernet LAN/WAN PIC.
375
NOTE:
The control queue feature is enabled by default in both OSE and line-rate
modes, which can be overridden by the user configuration.
When the control queue is disabled, various show queue commands will
show control queue in the output. However, all control queue counters are
reported as zeros.
Once the control queue is disabled, the Layer 2/Layer 3 control packets are subject to
queue selection based on BA classification. However, some control protocol packets will
not be classified using BA classification, because they might not have a VLAN, MPLS, or
IP header. These are:
When the control queue feature is disabled, untagged ARP, IS-IS, and other untagged
Layer 2 control packets will go to the restricted queue corresponding to the forwarding
class associated with queue 0, as shown in the following two examples.
Forwarding Untagged
Layer2 Control Packets
to Queue 3
With this configuration, the forwarding class (FC) associated with queue 0 is "be" (based
on the forwarding-class statement configuration). "be" maps to restricted-queue number
3 (based on the "restricted-queue" configuration). Hence, with this particular
configuration, untagged ARP, IS-IS, and other untagged Layer 2 control packets will go
to ingress queue 3 (not to ingress queue 0).
[edit chassis]
forwarding-classes {
queue 0 be;
queue 1 af-low8;
queue 2 af-high;
queue 3 ef;
queue 4 ops_control;
queue 5 net_control;
queue 6 af-low10_12;
}
restricted-queues {
forwarding-class ef queue-num 0;
forwarding-class af-low8 queue-num 1;
forwarding-class af-low10_12 queue-num 1;
forwarding-class af-high queue-num 2;
forwarding-class be queue-num 3;
}
376
Forwarding Untagged
Layer2 Control Packets
to Queue 3
With this configuration, the FC associated with queue 0 is "ef" (based on the
forwarding-class statement configuration). "ef" maps to restricted-queue number 0
(based on the restricted-queue statement configuration). Hence, with this particular
configuration, untagged ARP, IS-IS, and other untagged Layer 2 control packets would
go to ingress queue 0.
For tagged ARP, IS-IS, or Layer2 control packets, users should configure an explicit
dot1p/dot1ad classifier to make sure these packets are directed to the correct queue.
Without an explicit dot1p/dot1ad classifier, tagged ARP, IS-IS, or Layer 2 control packets
will go to the restricted-queue corresponding to the forwarding class associated with
queue 0.
[edit chassis]
forwarding-classes {
queue 0 ef; <<< ef and be are interchanged
queue 1 af-low8;
queue 2 af-high;
queue 3 be; <<< ef and be are interchanged
queue 4 ops_control;
queue 5 net_control;
queue 6 af-low10_12;
}
restricted-queues {
forwarding-class ef queue-num 0;
forwarding-class af-low8 queue-num 1;
forwarding-class af-low10_12 queue-num 1;
forwarding-class af-high queue-num 2;
forwarding-class be queue-num 3;
}
Related
Documentation
377
Number of Port
Groups with
One Active Port
(B)
Total Number
of Ports Used
on PIC (C = Ax2
+ B)
10
Related
Documentation
statement at the [edit chassis fpc slot-number pic pic-number] hierarchy level.
[edit chassis]
user@host# set fpc fpc-slot pic pic-number mixed-rate-mode
378
To disable mixed-rate mode operation, include the delete chassis fpc x pic y
mixed-rate-mode statement at the [edit chassis] hierarchy level.
Related
Documentation
You can configure the interfaces on this PIC to be a part of the mixed rates and mixed
mode aggregated Ethernet bundles. For information about mixed rates, see
Understanding Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on
page 141.
379
The following sections describe the P2-10G-40G-QSFPP PIC and the various framing
modes that are supported on it:
10-Gigabit Ethernet in LAN PHY framing mode (also known as native Ethernet mode)
and WAN PHY framing mode.
NOTE:
If you want configure the PIC in 10-Gigabit Ethernet mode to operate in
40-Gigabit Ethernet mode, you must:
1.
Delete all the interfaces in the PIC at the [edit interfaces] hierarchy level.
set chassis fpc fpc-slot pic pic-slot pic-mode 40G configuration command
and commit.
The PIC reboots and starts operating in the new mode.
The same procedure is applicable when you can configure the PIC in
40-Gigabit Ethernet PIC to operate in 10-Gigabit Ethernet mode. In this case,
you must execute the set chassis fpc fpc-slot pic pic-slot pic-mode 10G
configuration mode command.
To check the current diagnostics of the PIC, you must run the relevant operational mode
CLI commands such as show chassis hardware, show interfaces, show interfaces
diagnostics optics interface-name, and so on.
380
et-1/1/0
et-1/1/0:0
et-1/1/0:1
et-1/1/0:2
et-1/1/0:3
et-1/1/1
et-1/1/1:0
et-1/1/1:1
et-1/1/1:2
et-1/1/1:3
et-1/1/2
et-1/1/2:0
et-1/1/2:1
et-1/1/2:2
et-1/1/2:3
et-1/1/3
et-1/1/3:0
et-1/1/3:1
et-1/1/3:2
et-1/1/3:3
et-1/1/4
et-1/1/4:0
et-1/1/4:1
et-1/1/4:2
et-1/1/4:3
et-1/1/5
et-1/1/5:0
et-1/1/5:1
et-1/1/5:2
et-1/1/5:3
381
et-1/1/6
et-1/1/6:0
et-1/1/6:1
et-1/1/6:2
et-1/1/6:3
et-1/1/7
et-1/1/7:0
et-1/1/7:1
et-1/1/7:2
et-1/1/7:3
et-1/1/8
et-1/1/8:0
et-1/1/8:1
et-1/1/8:2
et-1/1/8:3
et-1/1/9
et-1/1/9:0
et-1/1/9:1
et-1/1/9:2
et-1/1/9:3
10
et-1/1/10
et-1/1/10:0
et-1/1/10:1
et-1/1/10:2
et-1/1/10:3
11
et-1/1/11
et-1/1/11:0
et-1/1/11:1
et-1/1/11:2
et-1/1/11:3
382
You can configure a 10-Gigabit Ethernet interface at the [edit interface interface-name
framing-mode (lan-phy | wan-phy)] hierarchy level to operate in 10-Gigabit Ethernet LAN
PHY framing mode or in 10-Gigabit Ethernet WAN PHY framing mode.
Each P2-10G-40G-QSFPP PIC provides 48 physical interfaces. The interfaces are
represented by the et-fpc/pic/QSFP+ port:channel interface naming convention, where
the value of the QSFP+ port option ranges from 0 through 11 and the value of the channel
option ranges from 0 through 3.
When a P2-10G-40G-QSFPP PIC is configured in 10-Gigabit Ethernet framing mode, it
can operate in one of the following framing modes:
LAN PHY framing mode. Note that by default, the PIC is in 10-Gigabit Ethernet LAN
PHY framing mode.
NOTE: The ports are set to LAN PHY framing mode by default when the
framing-mode statement is not configured at the [edit interface
interface-name] hierarchy level.
383
2. Configure the PIC in 10-Gigabit Ethernet mode or in 40-Gigabit Ethernet mode after
specifying the required FPC slot and PIC slot. Note that all the PIC ports in a PIC are
configured at once with this configuration command.
[edit chassis]
user@host# set fpc fpc-slot pic pic-slot pic-mode (10G | 40G)
Configuring the PIC in 10-Gigabit Ethernet Mode to Operate in 40-Gigabit Ethernet Mode
To configure the P2-10G-40G-QSFPP PIC that is configured in 10-Gigabit Ethernet mode
to operate in 40-Gigabit Ethernet mode:
1.
2. Delete all the interfaces in the PIC, commit, and then move to the top of the hierarchy
level.
[edit interfaces]
user@host# delete interface-name
user@host# delete ...
user@host# commit
user@host# top
3. Configure the PIC to operate in 40-Gigabit Ethernet mode and commit.
[edit]
user@host# set chassis fpc fpc-slot pic pic-slot pic-mode 40G
user@host# commit
After the configuration is committed, the PIC reboots and starts operating in the
40-Gigabit Ethernet mode. You can now configure the parameters, such as encapsulation,
framing mode, and so on, for the twelve 40-Gigabit Ethernet interfaces in the PIC as
needed.
Configuring the PIC in 40-Gigabit Ethernet Mode to Operate in 10-Gigabit Ethernet Mode
To configure the P2-10G-40G-QSFPP PIC that is configured in 40-Gigabit Ethernet mode
to operate in 10-Gigabit Ethernet mode:
1.
384
2. Delete all the interfaces in the PIC, commit, and then move to the top of the hierarchy
level.
[edit interfaces]
user@host# delete interface-name
user@host# delete ...
user@host# commit
user@host# top
3. Configure the PIC to operate in 10-Gigabit Ethernet mode and commit.
[edit]
user@host# set chassis fpc fpc-slot pic pic-slot pic-mode 10G
user@host# commit
After the configuration is committed, the PIC reboots and starts operating in the 10-Gigabit
Ethernet mode. You can now configure the parameters, such as encapsulation, framing
mode, and so on, for the forty-eight 10-Gigabit Ethernet interfaces in the PIC as needed.
2. Configure the framing mode as LAN PHY or WAN PHY and commit.
For example, you can configure the framing mode as LAN PHY or WAN PHY on the
et-1/1/1:0 interface.
To configure the P2-10G-40G-QSFPP PIC in 40-Gigabit Ethernet mode to operate in
LAN PHY framing mode:
1.
For example, you can configure the framing mode as LAN PHY on the et-2/2/2
interface.
385
Related
Documentation
Requirements
This example uses the following hardware and software components:
Overview
Starting with Junos OS Release 14.1R2 and 14.2R1, PTX5000 supports the
P2-10G-40G-QSFPP PIC on the FPC2-PTX-P1A FPC.
All the ports on the P2-10G-40G-QSFPP PIC are QSFP+ basedthat is, all the ports are
connected to fiber-optic cables by means of QSFP+ transceivers. The P2-10G-40G-QSFPP
PIC provides forty-eight 10-Gigabit Ethernet ports or twelve 40-Gigabit Ethernet ports.
The QSFP+ modulewhich includes the transceiver and the fiber-optic cablesupports
the following standards on the P2-10G-40G-QSFPP PIC:
10-Gigabit Ethernet in LAN PHY framing mode (also known as native Ethernet mode)
and WAN PHY framing mode.
Configuration
To configure the P2-10G-40G-QSFPP PIC to operate in 10-Gigabit Ethernet mode, and
to set the framing mode and other options on an interface on this PIC, perform the
following tasks:
386
Configure the PIC in 10-Gigabit Ethernet mode after specifying the required FPC
slot and PIC slot. Note that the PIC restarts after the configuration is committed
and all the ports in the PIC come up in the 10-Gigabit Ethernet mode.
[edit chassis]
user@host# set fpc 1 pic 1 pic-mode 10G
2.
Configure the framing mode for the interface as LAN PHY and commit.
[edit interfaces et-1/1/1:0]
user@host# set framing lan-phy
user@host# commit
Similarly, you can configure LAN PHY or WAN PHY framing mode for the other
interfaces in the PIC.
Configure the interface options for the interface et-1/1/1:0 as needed. The following
procedure configures a few interface-specific options.
1.
2.
3.
4.
Enable flow control to regulate the flow of packets from the router to the remote
side of the network connection.
[edit interfaces et-1/1/1:0 gigether-options]
user@host# set flow-control
5.
Enable loopback mode for the interface, commit the configuration, and exit the
configuration mode.
[edit interfaces et-1/1/1:0 gigether-options]
user@host# set loopback
387
user@host# commit
user@host# quit
Verification
Displaying Interface Details
Purpose
Action
Meaning
Related
Documentation
388
The interface details are displayed. Note that to display information for an interface in
10-Gigabit Ethernet mode for the P2-10G-40G-QSFPP PIC, you must use the
et-fpc/pic/port:channel format.
CHAPTER 22
Intel TXN13600 Optical Transceiver I2C Interface and Customer EEPROM Preliminary
Specification, July 2004.
I2C Reference Document for 300-Pin MSA 10G and 40G Transponder, Edition 4, August
04, 2003.
389
To display the currently tuned wavelength and frequency for the interface, use the show
interfaces interface-name operational mode command.
For interface diagnostics, issue the show interfaces diagnostics optics interface-name
operational mode command.
Table 26 on page 390 shows configurable wavelengths and the corresponding frequency
for each configurable wavelength.
Frequency (THz)
Wavelength
(nm)
Frequency (THz)
Wavelength
(nm)
Frequency (THz)
1528.38
196.15
1542.14
194.40
1556.15
192.65
1528.77
196.10
1542.54
194.35
1556.55
192.60
1529.16
196.05
1542.94
194.30
1556.96
192.55
1529.55
196.00
1543.33
194.25
1557.36
192.50
1529.94
195.95
1543.73
194.20
1557.77
192.45
1530.33
195.90
1544.13
194.15
1558.17
192.40
1530.72
195.85
1544.53
194.10
1558.58
192.35
1531.12
195.80
1544.92
194.05
1558.98
192.30
1531.51
195.75
1545.32
194.00
1559.39
192.25
1531.90
195.70
1545.72
193.95
1559.79
192.20
1532.29
195.65
1546.12
193.90
1560.20
192.15
1532.68
195.60
1546.52
193.85
1560.61
192.10
1533.07
195.55
1546.92
193.80
1561.01
192.05
1533.47
195.50
1547.32
193.75
1561.42
192.00
1533.86
195.45
1547.72
193.70
1561.83
191.95
1534.25
195.40
1548.11
193.65
1562.23
191.90
1534.64
195.35
1548.51
193.60
1562.64
191.85
1535.04
195.30
1548.91
193.55
1563.05
191.80
1535.43
195.25
1549.32
193.50
1563.45
191.75
390
Frequency (THz)
Wavelength
(nm)
Frequency (THz)
Wavelength
(nm)
Frequency (THz)
1535.82
195.20
1549.72
193.45
1563.86
191.70
1536.22
195.15
1550.12
193.40
1564.27
191.65
1536.61
195.10
1550.52
193.35
1564.68
191.60
1537.00
195.05
1550.92
193.30
1565.09
191.55
1537.40
195.00
1551.32
193.25
1565.50
191.50
1537.79
194.95
1551.72
193.20
1565.90
191.45
1538.19
194.90
1552.12
193.15
1566.31
191.40
1538.58
194.85
1552.52
193.10
1566.72
191.35
1538.98
194.80
1552.93
193.05
1567.13
191.30
1539.37
194.75
1553.33
193.00
1567.54
191.25
1539.77
194.70
1553.73
192.95
1567.95
191.20
1540.16
194.65
1554.13
192.90
1568.36
191.15
1540.56
194.60
1554.54
192.85
1568.77
191.10
1540.95
194.55
1554.94
192.80
1541.35
194.50
1555.34
192.75
1541.75
194.45
1555.75
192.70
Related
Documentation
391
392
CHAPTER 23
Understanding WAN Framing for 10-Gigabit Ethernet Trio Interfaces on page 394
When the external interface is running in LAN PHY mode, it bypasses the WIS sublayer
to directly stream block-encoded Ethernet frames on a 10-Gigabit Ethernet serial interface.
When the external interface is running in WAN PHY mode, it uses the WIS sublayer to
transport 10-Gigabit Ethernet frames in an OC192c SONET payload.
WAN PHY mode is supported on MX240, MX480, MX960, T640, T1600, T4000 and
PTX Series Packet Transport routers only.
NOTE: The T4000 Core Router supports only LAN PHY mode in Junos OS
Release 12.1R1. Starting with Junos OS Release 12.1R2, WAN PHY mode is
supported on the T4000 routers with the 12-port 10-Gigabit Ethernet
LAN/WAN PIC with SFP+ (PF-12XGE-SFPP). Starting with Junos OS Release
12.2, WAN PHY mode is supported on the T4000 routers with the 24-port
10-Gigabit Ethernet LAN/WAN PIC with SFP+ (PF-24XGE-SFPP).
Although the external interface provides a lower throughput when running in WAN PHY
mode because of the extra SONET overhead, it can interoperate with SONET section or
line level repeaters. This creates an advantage when the interface is used for
long-distance, point-to-point 10-Gigabit Ethernet links. When the external interface is
running in WAN PHY mode, some SONET options are supported. For information about
SONET options supported on this interface, see Configuring SONET Options for 10-Gigabit
Ethernet Interfaces.
393
Related
Documentation
Understanding WAN Framing for 10-Gigabit Ethernet Trio Interfaces on page 394
The interface does not distinguish between loss of light (LOL), loss of phase lock loop
(PLL), or loss of signal (LOS). If a loss of PLL or LOS alarm occurs, then both PLL and
LOS alarms are raised. LOL is also raised because there is no separate LOL indication
from the hardware.
The interface does not raise LOS, PLL, or LOL alarms when the fiber in disconnected
from the interface port. You must remove the hardware to raise this alarm.
The interface line-level alarm indicator signal (AIS-L) is not always raised in response
to a loss of framing (LOF) defect alarm.
If the AIS-L or path-level AIS (AIS-P) occurs, the interface path-level loss of code
delineation (LCD-P) is not detected. LCD-P is seen during the path-level remote defect
indicator (RDI-P) alarm.
If an AIS-L alarm occurs, the AIS-P is not detected, but the LOP alarm is detected.
None of the alarm issues are misleading, but they make troubleshooting the root cause
of problems more complex.
Related
Documentation
394
NOTE:
The T4000 Core Router supports only LAN PHY mode in Junos OS Release
12.1R1. Starting with Junos OS Release 12.1R2, WAN PHY mode is supported
on the T4000 routers with the 12-port 10-Gigabit Ethernet LAN/WAN PIC
with SFP+ (PF-12XGE-SFPP). Starting with Junos OS Release 12.2, WAN
PHY mode is supported on the T4000 routers with the 24-port 10-Gigabit
Ethernet LAN/WAN PIC with SFP+ (PF-24XGE-SFPP).
When the PHY mode changes, interface traffic is disrupted because of port
reinitialization.
To display interface information, use the operational mode command show interfaces
xe-fpc/pic/port extensive.
NOTE:
Related
Documentation
Understanding WAN Framing for 10-Gigabit Ethernet Trio Interfaces on page 394
395
396
CHAPTER 24
10-Gigabit Ethernet Notification of Link Down for Optics Options Overview on page 397
Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or
Warning on page 398
Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or
Warning on page 398
397
[edit interfaces]
ge-fpc/pic/port {
gigether-options {
asynchronous-notification;
}
}
Related
Documentation
Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or
Warning
To configure this option, include the alarm or warning statement at the [edit interfaces
ge- fpc/pic/port optics-options] hierarchy level:
[edit interfaces]
ge-fpc/pic/port {
optics-options {
alarm alarm-name {
(syslog | link-down);
}
warning warning-name {
(syslog | link-down);
}
}
}
Related
Documentation
398
10-Gigabit Ethernet Notification of Link Down for Optics Options Overview on page 397
CHAPTER 25
Layer 2 protocols
VLAN CCC
VLAN VPLS
Layer 3 protocols
IPv4
IPv6
399
MPLS
Graceful Routing Engine switchover (GRES) (in all PIC and chassis configurations).
Interface creation:
When the PIC is brought online, the router creates one interface, et-x/y/0, where x
represents the FPC slot number and y represents PIC slot number. The physical
interface represents internal Ethernet Packet Forwarding Engines.
The FPC slot number ranges from 0 through 7 in T640, T1600, and T4000 routers.
The PIC slot numbers are 0 and 1.
Packet Forwarding Engine 0 is the physical interface 0, and Packet Forwarding Engine
1 is the physical interface 1.
The configuration of the 40-Gigabit Ethernet PIC with CFP complies with that of the
existing 1-Gigabit or 10-Gigabit Ethernet PIC and aggregated Ethernet interfaces.
For Junos OS configuration information about this PIC, see Configuring 40-Gigabit
Ethernet PICs on page 401. For hardware compatibility information, see the T1600 PICs
Supported topic in the T1600 Core Router Hardware Guide hardware guide and the T640
PICs Supported topic in the T640 Core Router Hardware Guide hardware guide, and the
T4000 PICs Supported topic in the T4000 Core Router Hardware Guide hardware guide.
Related
Documentation
400
The following features are not supported on the 40-Gigabit Ethernet PIC with CFP:
MAC learning
MAC policing
Layer 2 rewrite
NOTE: Each 40-Gigabit Ethernet PIC with CFP creates a single et- physical
interface in the Routing Engine and Packet Forwarding Engine.
The 40-Gigabit Ethernet PIC with CFP supports aggregated Ethernet
configuration to achieve higher throughput capability, whereby the
configuration is similar to the 1-Gigabit or 10-Gigabit aggregated Ethernet
interface configuration. A maximum of 40-Gigabit Ethernet PIC links can be
bundled into a single aggregated Ethernet configuration depending on the
system implementation.
401
A single physical interface is created when the 40-Gigabit Ethernet PIC with CFP is
brought online (et-x/y/0, where x represents the FPC slot number and y represents
the PIC slot number). For more information, see Configuring a Logical Interface for
Access Mode on page 262 and Configuring a Logical Interface for Trunk Mode on
page 263.
3. Configure the 802.3 link aggregation.
The configuration of the 40-Gigabit Ethernet PIC with CFP complies with the
configuration of the 1-Gigabit Ethernet PIC, 10-Gigabit Ethernet PIC, and the
aggregated Ethernet interfaces. In each aggregated bundle, Junos OS supports a
maximum of 40-Gigabit Ethernet links. For more information, see Configuring an
Aggregated Ethernet Interface on page 138 and 10-port 10-Gigabit Ethernet
LAN/WAN PIC Overview on page 365.
The 40-Gigabit Ethernet PIC with CFP supports all classification, firewall filters, queuing
model, and rewrite functionality features of the Gigabit Ethernet PICs. To configure
these parameters, see Configuring Gigabit Ethernet Policers on page 471, Configuring
MAC Address Filtering on page 475, and Stacking and Rewriting Gigabit Ethernet
VLAN Tags Overview on page 489.
Related
Documentation
402
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489
CHAPTER 26
Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with
CFP on page 414
100-Gigabit Ethernet
Juniper Networks supports a variety of !00-Gigabit Ethernet interfaces. Ethernet was
developed in the early 1970s at the Xerox Palo Alto Research Center (PARC) as a data-link
control layer protocol for interconnecting computers.
403
100-Gigabit Ethernet transmits Ethernet frames at a rates of 100 gigabits per second,
and was first defined by the IEEE 802.3ba-2010 standard. It is used for very high speed
transmission of voice and data signals across the numerous world-wide fiber-optic
networks.
Model Number
Routers Supported
MIC3-3D-1X100GE-CFP
MX240
MX480
MX960
MX2010
MX2020
100-Gigabit Ethernet MIC
with CXP
MIC3-3D-1X100GE-CXP
MX240
MX480
MX960
MX2010
MX2020
100-Gigabit Ethernet ports
on the MPC4E
MPC4E-3D-2CGE-8XGE
MX240
MX480
2x100GE + 8x10GE MPC4E
MX960
MX2010
MX2020
Model Number
Routers Supported
P1-PTX-2-100GE-CFP
PTX5000
404
Model Number
Routers Supported
PD-1CE-CFP-FPC4
T1600
T4000
100-Gigabit Ethernet PIC with
CFP (T4000 Router)
100-Gigabit Ethernet Type
4 PIC with CFP Overview on
page 407
Configuring 100-Gigabit
Ethernet Type 4 PIC With
CFP on page 410
100-Gigabit Ethernet PIC
with CFP (Type 5)
PF-1CGE-CFP
T4000
Related
Documentation
405
The MPC3E has two separate configurable MIC slots. Each MIC corresponds to a single
PIC and the mapping between the MIC and PIC is 1 to 1 (one MIC is treated as one PIC).
The MIC plugged into slot 0 corresponds to PIC 0 and the MIC plugged into slot 1
corresponds to PIC 2.
The MPC3E also supports these legacy MICs:
The 100-Gigabit Ethernet CFP MIC supports the IEEE standardscompliant 100BASE-LR4
interface, using the 100G CFP optical transceiver modules for connectivity. The 100-Gigabit
Ethernet CXP MIC supports the 100BASE-SR10 interface, using 100-Gigabit CXP optical
transceiver modules for connectivity. The 2-port 40-Gigabit Ethernet QSFPP MIC supports
the 40BASE-SR4 interface and uses quad small form-factor pluggable (QSFPP) optical
transceivers for connectivity. The 10-port 10-Gigabit Ethernet SFPP MIC uses SFP+ optical
transceiver modules for connectivity.
For detailed information about each MIC, see 100-Gigabit Ethernet MIC with CFP,
100-Gigabit Ethernet MIC with CXP, 40-Gigabit Ethernet MIC with QSFP+. For information
about supported hardware and transceivers, see MPC3E.
The MPC3E supports these features:
Synchronous Ethernet
MAC accounting and policingDynamic local address learning of source MAC addresses
NOTE: The MPC3E supports Ethernet interfaces only. SONET interfaces are
not supported.
For information about the supported and unsupported Junos OS features for this MPC,
see Protocols and Applications Supported by the MPC3E (MX-MPC3E) in the MX Series
Interface Module Reference.
Related
Documentation
406
Protocols and Applications Supported by the MX240, MX480, MX960, MX2010, and
MX2020 MPC3E
Layer 2 protocols
VLAN CCC
VLAN VPLS
Layer 3 protocols
IPv4
Ipv6
MPLS
Graceful Routing Engine switchover (GRES) is supported in all PIC and chassis
configurations.
407
Interface creation:
When the PIC, is brought online, the router creates two 50 gigabit capable interfaces,
et-x/0/0:0 and et-x/0/0:1, where x represents the FPC slot number. Each physical
interface represents two internal 50 gigabit Ethernet Packet Forwarding Engines.
Two logical interfaces are configured under each physical interface.
Two logical interfaces are created for each 100-Gigabit Ethernet PIC. To utilize
bandwidth beyond 50 gigabits per second, an aggregate interface must be explicitly
configured on the 100-Gigabit Ethernet PIC that includes the two 50 gigabit interfaces.
Each 100 gigabit Ethernet aggregate consumes one of the router-wide aggregated
Ethernet device pools. The number of 100-Gigabit Ethernet PICs cannot exceed the
router-wide limit, which is 128 for Ethernet.
In each aggregate bundle, each 100-Gigabit Ethernet PIC consumes two members.
Hence, an aggregate bundle that consists purely of 100-Gigabit Ethernet PICs
supports a maximum of half of the software limit for the number of members.
Therefore, with a maximum of 16 links, up to 8 100-Gigabit Ethernet links are
supported.
Combining 100-Gigabit Ethernet PICs into aggregate interfaces with other Ethernet
PICs is not permitted. However, other Ethernet PICs can also be configured within
the same T1600 with 100-Gigabit Ethernet PICs, and used in separate aggregate
interfaces.
408
Starting with Junos OS Release 13.2, aggregated Ethernet supports mixed rates and
mixed modes on 100-Gigabit Ethernet PIC.
Static link protection and Link Aggregation Control Protocol (LACP) is supported on
mixed aggregated Ethernet link configured on a 100-Gigabit Ethernet PIC.
Related
Documentation
VLAN steering modeIn this mode, the 100-Gigabit Ethernet Type 4 PIC with CFP
supports interoperability with 100 gigabit Ethernet interfaces from other vendors
only.
409
MAC accounting in RX
Layer 2 rewrite
The following features are not supported on the 100-Gigabit Ethernet Type 4 PIC with
CFP:
Multiple TPID
MAC learning
MAC policing
NOTE:
410
For the 100-Gigabit Ethernet Type 4 PIC with CFP, only the PIC0 online and
offline CLI commands are supported. The PIC1 online and offline CLI
commands are not supported.
Each 100-Gigabit Ethernet Type 4 PIC with CFP creates two et- physical
interfaces, defined as 50-gigabit physical interfaces in the Routing Engine
and Packet Forwarding Engine. By default, these are independent physical
interfaces and are not configured as an aggregated Ethernet interface.
a. Two physical interfaces are created when the 100-Gigabit Ethernet Type 4 PIC
with CFP is brought online (et-x/0/0:0 and et-x/0/0:1, where x represents the FPC
slot number). Each physical interface represents two internal 50-gigabit Ethernet
Packet Forwarding Engines.
b. Two logical interfaces are configured under each physical interface: Packet
Forwarding Engine 0 is physical interface 0 and Packet Forwarding Engine 1 is
physical interface 1.
3. Configure the 802.3 link aggregation:
411
NOTE:
The 100-Gigabit Ethernet Type 4 PIC with CFP has the following
restrictions for same rate and same mode aggregated Ethernet
configuration:
e. Starting with Junos OS Release 13.2, aggregated Ethernet supports mixed rates
and mixed modes on 100-Gigabit Ethernet PIC. When configuring a mixed
aggregated Ethernet link on a 100-Gigabit Ethernet PIC, ensure that you add both
the 50-Gigabit Ethernet interfaces of the 100-Gigabit Ethernet PIC to the aggregated
Ethernet bundle. Moreover, both these 50-Gigabit Ethernet interfaces must be
included in the same aggregated Ethernet bundle.
412
NOTE:
The 100-Gigabit Ethernet Type 4 PIC with CFP has the following restrictions
for mixed rate and mixed mode aggregated Ethernet configuration:
Packets are dropped when the total throughput of the hash flow exiting
a member link (or multiple hash flows exiting a single member link)
exceeds the link speed of the member link. This can happen when egress
member link changes because of a link failure and the hash flow switches
to a member link of speed that is less than the total throughput of the
hash flow.
Load balancing of the egress traffic across the member links of a mixed
rate aggregated Ethernet link is proportional to the rates of the member
links.
413
The show interfaces aex command displays the link speed of the
aggregated Ethernet interface, which is the sum of the link speeds of
all the active member links.
a. The 100-Gigabit Ethernet Type 4 PIC with CFP supports all classification, firewall
filters, queuing model, and rewrite functionality features of the Gigabit Ethernet
PICs. To configure these parameters, see Configuring Gigabit Ethernet Policers
on page 471, Configuring MAC Address Filtering on page 475, and Stacking and
Rewriting Gigabit Ethernet VLAN Tags Overview on page 489.
NOTE: When using the show interfaces extensive command with a 100-Gigabit
Ethernet Type 4 PIC with CFP, the Filter statistics section will not be
displayed because the hardware does not include those counters.
Related
Documentation
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489
Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP
In Junos OS Release 10.4 and later, you can configure the 100-Gigabit Ethernet Type 4
PIC with CFP (PD-1CE-CFP-FPC4) to interoperate with routers using 100 gigabit Ethernet
interfaces from other vendors by using the forwarding-mode statement with the
vlan-steering option at the [edit chassis fpc slot pic slot] hierarchy level. On ingress, the
router compares the outer VLAN ID against the user-defined VLAN ID and VLAN mask
combination and steers the packet accordingly. You can program a custom VLAN ID and
corresponding mask for PFE0.
General information on the VLAN steering mode:
414
In VLAN steering mode, the SA multicast parameters are not used for packet steering.
In SA multicast bit steering mode, the VLAN ID and VLAN masks are not used for packet
steering.
Configuration to set the packet distribution mode and VLAN steering rule is done
through CLI commands. Both CLI commands result in a PIC reboot.
Ingress packet with one VLANThe packet is forwarded to the corresponding PFE
based on the VLAN ID.
Ingress packet with two VLANsThe packet is forwarded to the corresponding PFE
based on the outer VLAN ID.
VLAN rules describe how the router distributes packets. Two VLAN rules are provided
by the CLI:
Odd-Even ruleOdd number VLAN IDs go to PFE1; even number of VLAN IDs go to
PFE0.
Hi-Low ruleVLAN IDs 1 through 2047 go to PFE0; VLAN IDs 2048 through 4096 go
to PFE1.
When the 100-Gigabit Ethernet Type 4 PIC with CFP is configured in VLAN steering
mode, it can be configured in a two physical interfaces mode or in aggregate Ethernet
(AE) mode:
Two physical interfaces modeWhen the PIC is in the two physical interfaces mode,
it creates the physical interfaces et-x/0/0:0 and et-x/0/0:1. Each physical interface
can configure its own logical interface and VLAN. The CLI enforces the following
restrictions at the commit time:
The VLAN ID configuration must comply with the selected VLAN rule.
The previous restriction implies that the same VLAN ID cannot be configured on
both physical interfaces.
AE modeWhen the PIC is in aggregated Ethernet mode, the two physical interfaces
on the same PIC are aggregated into one AE physical interface. The PIC egress traffic
is based on an AE internal hash algorithm. The PIC ingress traffic steering is based
on the customized VLAN ID rule. The CLI enforces the following restrictions at the
commit time:
The PICs AE working in VLAN steering mode includes both links of that PIC, and
only the links of that PIC.
The PIC AE working in SA multicast steering mode can include more than one
100-Gigabit Ethernet Type 4 PIC with CFP to achieve more than 100 gigabit
Ethernet capacity.
To configure SA multicast mode, use the set chassis fpc slot pic slot forwarding-mode
sa-multicast command.
SA Multicast Mode
415
To configure the Juniper Networks 100-Gigabit Ethernet Type 4 PIC with CFP for VLAN
steering mode for interoperation with a 100 gigabit Ethernet interface from another
vendors router, use the set chassis fpc slot pic slot forwarding-mode vlan-steering
command with the vlan-rule (high-low | odd-even) statement. You can use the show
forwarding-mode command to view the resulting configuration, as follows:
[edit chassis fpc slot pic slot]
user@host# show forwarding-mode
forwarding-mode {
vlan-steering {
vlan-rule odd-even;
}
}
Related
Documentation
Logical interfacelevel MAC filtering, accounting, policing, and learning for source
media access control (MAC).
Defining the rewrite operation to be applied to the incoming and outgoing frames on
logical interfaces on this PIC.
416
You can configure only one logical interface (unit 0) on the port.
You cannot include the vlan-id statement in the configuration of the logical
interface.
vlan-taggingEnable VLAN tagging for all logical interfaces on the physical interface.
physical interface.
ethernet-cccEthernet cross-connect.
cross-connect.
IPv4
IPv6
MPLS
The configuration of the 100-Gigabit Ethernet Type 5 PIC with CFP complies with
that of the existing 1-Gigabit or 10-Gigabit Ethernet PIC and aggregated Ethernet
interfaces.
The 100-Gigabit Ethernet Type 5 PIC with CFP supports all Gigabit Ethernet PIC
classification, firewall filters, queuing model, and Layer 2 rewrite functionality features
of the Gigabit Ethernet PICs. To configure these parameters, see Configuring Gigabit
Ethernet Policers on page 471, Configuring MAC Address Filtering on page 475, and
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489.
A Type 5 FPC can support up to two 100-Gigabit Ethernet PICs. Both the PICs (that is,
PIC 0 and PIC 1) can be offline or online independently.
417
The following features are not supported on the 100-Gigabit Ethernet Type 5 PIC with
CFP:
MAC filtering, accounting, and policing for destination MAC at the logical interface
level.
Multiple TPIDs.
Table 30 on page 418 lists the capabilities of 100-Gigabit Ethernet Type 5 PIC with CFP.
Support
4093
Related
Documentation
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489
Enabling source address (SA) multicast bit steering mode on the 100-Gigabit Ethernet
PIC PF-1CGE-CFP.
Configuring the two 50-Gigabit Ethernet physical interfaces on the 100-Gigabit Ethernet
PIC PD-1CE-CFP-FPC4 as one aggregated Ethernet physical interface.
SA multicast mode uses the multicast bit in the source MAC address for packet steering.
By default, the SA multicast bit is set to 0 for all packets sent by the 100-Gigabit Ethernet
418
PIC PF-1CGE-CFP. The 100-Gigabit Ethernet PIC PD-1CE-CFP-FPC4 looks at the bit and
forwards the packets to either Packet Forwarding Engine 0 or Packet Forwarding Engine
1. When the PIC sends out a packet, the multicast bit is set based on the egress Packet
Forwarding Engine number (0 or 1).
The default packet steering mode for PD-1CE-CFP-FPC4 is SA multicast bit mode. No
SA multicast configuration is required to enable this mode.
PD-1CE-CFP-FPC4 uses two 50 Gpbs Packet Forwarding Engines to achieve 100 Gbps
throughput. The 50-Gigabit Ethernet physical interfaces are created when the 100-Gigabit
Ethernet PIC is plugged in. The two physical interfaces are visible and configuration is
allowed on both the physical interfaces. You must configure the physical interfaces on
PD-1CE-CFP-FPC4 in static link aggregation group (LAG) mode without enabling Link
Aggregation Control Protocol (LACP). This ensures that a single 100-Gigabit aggregated
interface is visible on the link connecting to the 100-Gigabit Ethernet PIC PF-1CGE-CFP
instead of two independent 50-Gigabit Ethernet interfaces.
Related
Documentation
Configuring the two 50-Gigabit Ethernet physical interfaces on the 100-Gigabit Ethernet
PIC PD-1CE-CFP-FPC4 as one aggregated Ethernet physical interface.
Configuring source address (SA) multicast bit steering mode on the 100-Gigabit
Ethernet PIC P1-PTX-2-100GE-CFP.
419
SA multicast bit steering mode uses the multicast bit in the source MAC address for
packet steering.
The 100-Gigabit Ethernet PIC PD-1CE-CFP-FPC4 uses two 50-Gpbs Packet Forwarding
Engines to achieve 100-Gbps throughput. The 50-Gigabit Ethernet physical interfaces
are created when the 100-Gigabit Ethernet PIC is plugged in. The two physical interfaces
are visible and configuration is allowed on both the physical interfaces. You must configure
the physical interfaces on the 100-Gigabit Ethernet PIC PD-1CE-CFP-FPC4 in static link
aggregation group (LAG) mode without enabling Link Aggregation Control Protocol
(LACP). This ensures that a single 100-Gigabit aggregated interface is visible on the link
connecting to the 100-Gigabit Ethernet PIC P1-PTX-2-100GE-CFP.
On the 100-Gigabit Ethernet PIC PD-1CE-CFP-FPC4, ingress packets are forwarded to
either Packet Forwarding Engine number 0 or 1 based on the SA multicast bit in the
received packet. The SA multicast bit of egress packets is set based on whether the
packet is forwarded from Packet Forwarding Engine number 0 or 1. As the default packet
steering mode is SA multicast bit steering mode, no configuration is necessary to enable
this mode.
On the 100-Gigabit Ethernet PIC P1-PTX-2-100GE-CFP, the SA multicast bit is ignored
in ingress packets. When SA multicast bit steering mode is enabled, the SA multicast bit
in the egress packets is set to 0 or 1 based on the flow hash value that is computed
internally by the Packet Forwarding Engine complex for each packet. No CLI configuration
is required to generate the flow hash value as this computation is done automatically.
The flow hash algorithm uses fields in the packet header to compute the flow hash value.
By default, the SA multicast bit is set to 0 in egress packets. You must configure SA
multicast bit steering mode to enable interoperability with the 100-Gigabit Ethernet PIC
PD-1CE-CFP-FPC4 .
Related
Documentation
420
Configuring SA Multicast Bit Steering Mode on the 100-Gigabit Ethernet PIC PF-1CGE-CFP
To enable the interoperability between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4
and PF-1CGE-CFP, you need to enable source address (SA) multicast bit steering mode
on PF-1CGE-CFP.
To configure SA multicast mode on PF-1CGE-CFP:
1.
For example:
[edit ]
user@host# edit chassis fpc 1 pic 0
2. Configure the interoperation mode (SA multicast bit steering mode).
For example:
[edit fpc 1 pic 0]
user@host# set forwarding-mode sa-multicast
3. Verify the configuration.
[edit ]
user@host# show chassis
fpc 1 {
pic 0 {
forwarding-mode {
sa-multicast;
}
}
}
421
NOTE: The default packet steering mode for the 100-Gigabit Ethernet PIC
PD-1CE-CFP-FPC4 is SA multicast bit mode. No SA multicast configuration
is required to enable this mode.
Configuring Two 50-Gigabit Ethernet Physical Interfaces on the 100-Gigabit Ethernet PIC
PD-1CE-CFP-FPC4 as One Aggregated Ethernet Interface
To enable the interoperability between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4
and PF-1CGE-CFP or P1-PTX-2-100GE-CFP, you need to configure the two 50-Gigabit
Ethernet physical interfaces on PD-1CE-CFP-FPC4 as one aggregated Ethernet physical
interface. This ensures that a single 100-Gigabit aggregated interface is visible on the
link connecting to PF-1CGE-CFP or P1-PTX-2-100GE-CFP instead of two independent
50-Gigabit Ethernet interfaces.
When the PIC is in aggregated Ethernet mode, the two physical interfaces on the same
PIC are aggregated into one aggregated Ethernet physical interface. When the PIC is
configured with two physical interfaces, it creates the physical interfaces et-fpc/pic/0:0
and et-fpc/pic/0:1, where fpc is the FPC slot number and pic is the PIC slot number. For
example, to configure two physical interfaces for PIC slot 0 in FPC slot 5:
1.
For example:
[edit chassis]
user@host# set aggregated devices ethernet device-count 1
2. Specify the members to be included within the aggregated Ethernet bundle.
[edit interfaces ]
user@host# set interface-name gigether-options 802.3ad bundle
The following example shows how to configure two physical interfaces for PIC 0 on
a T1600 router.
[edit interfaces ]
user@host# set et-5/0/0:0 gigether-options 802.3ad ae0
user@host# set et-5/0/0:1 gigether-options 802.3ad ae0
3. Verify the configuration at the chassis.
[edit ]
user@host# show chassis
aggregated-devices {
ethernet {
device-count 1;
}
}
[edit ]
422
Related
Documentation
NOTE: When you configure the SA multicast bit steering mode on the PTX
Series PIC P1-PTX-2-100GE-CFP, we recommend that you do not configure
the PIC ports as member links of an aggregated Ethernet interface because
this prevents load balancing on the peering T Series PIC PD-1CE-CFP-FPC4.
This T Series PIC must be in aggregated Ethernet mode to share bandwidth
between its two 50-Gigabit Ethernet interfaces.
423
For example:
[edit ]
user@host# edit chassis fpc 1 pic 0 port 0
2. Configure the interoperation mode (SA multicast bit steering mode).
[edit ]
user@host# show chassis
fpc 1 {
pic 0 {
port 0 {
forwarding-mode {
sa-multicast;
}
}
}
}
NOTE: As the default packet steering mode for the 100-Gigabit Ethernet PIC
PD-1CE-CFP-FPC4 is SA multicast bit steering mode, no configuration is
necessary to enable this mode.
Configuring Two 50-Gigabit Ethernet Physical Interfaces on the 100-Gigabit Ethernet PIC
PD-1CE-CFP-FPC4 as One Aggregated Ethernet Interface
To enable the interoperability between the 100-Gigabit Ethernet PICs PD-1CE-CFP-FPC4
and PF-1CGE-CFP or P1-PTX-2-100GE-CFP, you need to configure the two 50-Gigabit
Ethernet physical interfaces on PD-1CE-CFP-FPC4 as one aggregated Ethernet physical
interface. This ensures that a single 100-Gigabit aggregated interface is visible on the
link connecting to PF-1CGE-CFP or P1-PTX-2-100GE-CFP instead of two independent
50-Gigabit Ethernet interfaces.
When the PIC is in aggregated Ethernet mode, the two physical interfaces on the same
PIC are aggregated into one aggregated Ethernet physical interface. When the PIC is
configured with two physical interfaces, it creates the physical interfaces et-fpc/pic/0:0
and et-fpc/pic/0:1, where fpc is the FPC slot number and pic is the PIC slot number. For
example, to configure two physical interfaces for PIC slot 0 in FPC slot 5:
1.
For example:
[edit chassis]
user@host# set aggregated devices ethernet device-count 1
424
[edit interfaces ]
user@host# set interface-name gigether-options 802.3ad bundle
The following example shows how to configure two physical interfaces for PIC 0 on
a T1600 router.
[edit interfaces ]
user@host# set et-5/0/0:0 gigether-options 802.3ad ae0
user@host# set et-5/0/0:1 gigether-options 802.3ad ae0
3. Verify the configuration at the chassis.
[edit ]
user@host# show chassis
aggregated-devices {
ethernet {
device-count 1;
}
}
[edit ]
user@host# show interfaces
et-5/0/0:0 {
gigether-options {
802.3ad ae0;
}
}
et-5/0/0:1 {
gigether-options {
802.3ad ae0;
}
}
Related
Documentation
425
To display the currently tuned wavelength and frequency for the interface, use the show
interfaces interface-name operational mode command.
For interface diagnostics, issue the show interfaces diagnostics optics interface-name
operational mode command.
Table 26 on page 390 shows configurable wavelengths and the corresponding frequency
for each configurable wavelength.
Frequency (THz)
Wavelength
(nm)
Frequency (THz)
Wavelength
(nm)
Frequency (THz)
1528.38
196.15
1542.14
194.40
1556.15
192.65
1528.77
196.10
1542.54
194.35
1556.55
192.60
1529.16
196.05
1542.94
194.30
1556.96
192.55
1529.55
196.00
1543.33
194.25
1557.36
192.50
1529.94
195.95
1543.73
194.20
1557.77
192.45
1530.33
195.90
1544.13
194.15
1558.17
192.40
1530.72
195.85
1544.53
194.10
1558.58
192.35
1531.12
195.80
1544.92
194.05
1558.98
192.30
1531.51
195.75
1545.32
194.00
1559.39
192.25
1531.90
195.70
1545.72
193.95
1559.79
192.20
1532.29
195.65
1546.12
193.90
1560.20
192.15
1532.68
195.60
1546.52
193.85
1560.61
192.10
1533.07
195.55
1546.92
193.80
1561.01
192.05
1533.47
195.50
1547.32
193.75
1561.42
192.00
1533.86
195.45
1547.72
193.70
1561.83
191.95
1534.25
195.40
1548.11
193.65
1562.23
191.90
1534.64
195.35
1548.51
193.60
1562.64
191.85
1535.04
195.30
1548.91
193.55
1563.05
191.80
1535.43
195.25
1549.32
193.50
1563.45
191.75
426
Frequency (THz)
Wavelength
(nm)
Frequency (THz)
Wavelength
(nm)
Frequency (THz)
1535.82
195.20
1549.72
193.45
1563.86
191.70
1536.22
195.15
1550.12
193.40
1564.27
191.65
1536.61
195.10
1550.52
193.35
1564.68
191.60
1537.00
195.05
1550.92
193.30
1565.09
191.55
1537.40
195.00
1551.32
193.25
1565.50
191.50
1537.79
194.95
1551.72
193.20
1565.90
191.45
1538.19
194.90
1552.12
193.15
1566.31
191.40
1538.58
194.85
1552.52
193.10
1566.72
191.35
1538.98
194.80
1552.93
193.05
1567.13
191.30
1539.37
194.75
1553.33
193.00
1567.54
191.25
1539.77
194.70
1553.73
192.95
1567.95
191.20
1540.16
194.65
1554.13
192.90
1568.36
191.15
1540.56
194.60
1554.54
192.85
1568.77
191.10
1540.95
194.55
1554.94
192.80
1541.35
194.50
1555.34
192.75
1541.75
194.45
1555.75
192.70
Related
Documentation
427
428
CHAPTER 27
429
preemptive-fast-reroute {
(backward-frr-enable | no-backward-frr-enable);
(signal-degrade-monitor-enable | no-signal-degrade-monitor-enable);
odu-backward-frr-enable | no-odu-backward-frr-enable;
odu-signal-degrade-monitor-enable | no-odu-signal-degrade-monitor-enable;
}
rate {
(fixed-stuff-bytes | no-fixed-stuff-bytes);
oc192;
otu4;
(pass-through | no-pass-through);
}
signal-degrade {
ber-threshold-clear value;
ber-threshold-signal-degrade value;
interval value;
}
tca tca-identifier (enable-tca | no-enable-tca) (threshold number | threshold-24hrs
number);
transport-monitoring;
trigger trigger-identifier;
tti tti-identifier;
}
NOTE: The Gigabit Ethernet interface and the XENPAK interface support the
read/write overhead bytes only for the APS/PPC (bytes 0 through 3).
You can use the following show commands to view the OTN configuration:
Related
Documentation
430
Transparent transport of 24 10-Gigabit Ethernet signals with optical channel data unit
2 (ODU2) and ODU2e framing on a per-port basis
Pre-forward error correction (pre-FEC)-based bit error rate (BER). Fast reroute (FRR)
uses the pre-FEC BER as an indication of the condition of an OTN link.
To configure the OTN options on the specified MX routers, use the set otn-options
statement at the [edit interfaces interfaceType-fpc/pic/port] hierarchy level.
Related
Documentation
Interface Features
The following interface features are supported on the P1-PTX-24-10G-W-SFPP PIC:
Link-level pause framesYou can halt the Ethernet interface from transmitting packets
for a configured period of time.
Interface hold timer and interface dampingYou can set the hold-time statement (in
milliseconds) to damp interface transitions.
External clock.
431
For each 10-Gigabit Ethernet port, you can configure up to eight TPIDs by using the
tag-protocol-id statement at the [edit interfaces interface-name gigether-options
ethernet-switch-profile] hierarchy level.
The tag-protocol-id statement can be configured only on the first port (port 0) of
the PIC. If any other (nonzero) port has the tag-protocol-id configuration, the Routing
Engine registers an error in the system log and the configuration is ignored.
The tag-protocol-id statement configured on port 0 of the PIC also applies to the
rest of the ports on that PIC.
Generic forward error correction (GFEC),ultra forward error correction (UFEC), enhanced
forward error correction (EFEC), and no-FEC modes of operation are supported.
Diagnostics tools:
Line loopback
Local loopback
Fast reroute (FRR)Based on configurable pre-FEC, bit error rate (BER) is supported
and is configured using the ber-threshold-signal-degrade statement at the [edit
interfaces interface-name otn-options signal-degrade] hierarchy level.
jnx-ifotn.mib and otn-mib as defined in RFC 3591. Note that according to Junos OS
security standard, configurable parameters are not supported through SNMP. Only
the get operation is available through SNMP.
At the logical interface level dix, vlan-ccc, and vlan-tcc encapsulations are supported.
SNMP management of the PIC based on RFC 3591, Definitions of Managed Objects
for the Optical Interface Type:
432
Set functionality
IFOTN MIB
Optics MIB
FRU MIB
Threshold-crossing alerts
MAC policing
MAC detect link up and link down based on local fault signal or remote fault signal.
MAC statistics.
Flow control.
MAC oversized packet counters based on default MTU value or user-configured MTU
value.
433
Aggregated Ethernet supports 64 child links that can be configured using the set chassis
aggregated-devices maximum-links configuration command.
Support for V LAN tagging, flexible VLAN tagging, and stacked VLAN tagging.
LACP.
Link protection.
802.3 ah OAM.
802.1 ag OAM.
MPLS FRR.
SNMP.
434
LOSLoss Of Signal
LOFLoss Of Frame
LOMLoss Of Multiframe
OTU-SDSignal Degrade
OTU-SFSignal Fail
ODU-SDSignal Degrade
ODU-SFSignal Fail
TCA Alarms
Threshold-crossing alarms (TCA) are alarms that are activated when a certain
configurable thresholdnear-end measurement threshold or far-end measurement
thresholdis crossed and remains so until the end of the 15 minute interval for parameters
such as OTU and ODU. The following alarms are supported:
Related
Documentation
2. Configure the VLAN tagging option on the OTN interface to enable the reception and
435
2. Enable the OTN mode as OTU2e, OTU1e, or OTU2 for the interface.
3. Enable the laser on the OTN interface. The laser is disabled by default for all OTN
interfaces.
[edit interfaces interface-name otn-options]
user@host# set laser-enable
4. Set an trail trace identifier for the source access point and for the destination access
436
up with a valueWait for the hold time delay before clearing the alarm when the
defect is absent on the OTN interface.
down with a valueWait for the hold time delay before raising the alarm when the
defect occurs for the OTN interface.
[edit interfaces interface-name otn-options]
user@host# set trigger (oc-lof | oc-lom | oc-los | oc-tsf | odu-ais | odu-bdi | odu-bei |
odu-iae | odu-lck | odu-oci | odu-sd | odu-ttim |opu-ptim | otu-ais | otu-bdi |
otu-fec-deg | otu-fec-exe | otu-iae | otu-sd | otu-ttim) (hold-time (down value | up
value) | ignore)
6. Enable the threshold crossing alarms for the OTN interface along with the trigger for
the defect.
[edit interfaces interface-name otn-options]
user@host# set tca (odu-tca-bbe | odu-tca-es | odu-tca-ses | odu-tca-uas | otu-tca-bbe
| otu-tca-es | otu-tca-ses | otu-tca-uas ) (enable-tca | no-enable-tca | threshold)
7. Set the OTN header bytes as a transmit payload type from 0 bytes through 255 bytes
(GFEC), Enhanced Forward Error Correction (EFEC), Ultra Forward Error Correction
(UFEC), or no-FEC (none) for the OTN interface.
[edit interfaces interface-name otn-options]
user@host# set fec (gfec | ufec | efec | none)
9. Enable a consequent action as listed in the ITU-T G.798 standard for ODU trail trace
Configure the threshold value after signal degradation when the alarm needs to be
cleared. When you configure the interval along with the ber-threshold-signal-degrade
value statement, the bit error rate (BER) must stay above the signal degradation
threshold for the configured interval after which the alarm is raised. When the interval
is configured along with the ber-threshold-clear value statement, then BER must stay
below the clear threshold for the configured interval after which the alarm is cleared.
[edit interfaces interface-name otn-options signal-degrade]
user@host# set ber-threshold-signal-degrade value
user@host# set ber-threshold-clear value
437
Backward FRRInsert the local pre-FEC status into the transmitted OTN frames
and monitor the received OTN frames for the pre-FEC status.
[edit interfaces interface-name otn-options preemptive-fast-reroute]
user@host# set backward-frr-enable
Related
Documentation
Pre-forward error correction (pre-FEC)-based bit error rate (BER) monitoring. Pre-FEC
BER monitoring uses the pre-FEC BER as an indication of the condition of an OTN link.
See Understanding Pre-FEC BER Monitoring and BER Thresholds on page 439 for more
information.
For more information about the 100-Gigabit DWDM OTN PIC, see 100-Gigabit DWDM
OTN PIC in the PTX Series Interface Module Reference.
PTX Series routers also support the 100-Gigabit Ethernet OTN PIC (P2-100GE-OTN),
which provides four 100-Gigabit Ethernet interfaces, independently configurable in LAN
PHY framing mode or in optical channel transport unit 4 (OTU4) mode. See
Understanding the P2-100GE-OTN PIC on page 453 for more information.
See Supported OTN Options on PTX Series Routers on page 444 for a comparison of
the features supported on PTX Series OTN PICs.
438
MX2020, MX2010, MX960, MX480, and MX240 routers support OTN interfaces on MPC5E
and MPC6E. MPC5E-100G10G and MPC5EQ-100G10G support 100-Gigabit Ethernet
OTN interfaces and 10-Gigabit Ethernet OTN interfaces on MX240, MX480, and MX960
routers. The OTN MIC MIC6-100G-CFP2 on MPC6E supports OTN on 100-Gigabit Ethernet
interfaces on MX2020 and MX2010 routers. OTN support on the specified MX Series
routers includes:
To configure the OTN options for PTX Series routers and specific MX Series routers, use
the set otn-options statement at the [edit interfaces interfaceType-fpc/pic/port] hierarchy
level.
Use the set optics-options statement at the [edit interfaces interfaceType-fpc/pic/port]
hierarchy level to configure the optics options.
Use the show interfaces extensive, show interfaces diagnostics optics (Gigabit Ethernet,
10-Gigabit Ethernet, 40-Gigabit Ethernet, and 100-Gigabit Ethernet), and show
interfaces interval commands to view optics and OTN PM information. To display the
current time interval and clear the channel service unit (CSU) alarm and defect counters,
use the clear interfaces interval command.
Related
Documentation
P1-PTX-2-100G-WDM
PTX-2-100G-WDM-M
P2-100GE-OTN
P1-PTX-24-10G-W-SFPP
With pre-FEC BER monitoring enabled, when the configured pre-FEC BER signal degrade
threshold is reached, the PIC stops forwarding packets to the remote interface and raises
439
You can also configure the pre-FEC BER thresholds that raise or clear a signal degrade
alarm and the time interval for the thresholds. If the BER thresholds and interval are not
configured, the default values are used.
The pre-FEC BER signal degrade threshold value defines a specific amount of system
margin relative to the BER correction limit (or FEC limit) of the PICs receive FEC decoder.
The FEC limit is fixed on each PICit is intrinsic to the FEC decoder implementation.
To calculate Q -factor:
= 20 * LOG10(NORMSINV(BER))
To calculate BER:
2
= 1 NORMSDIST(10^(0.05 * Q -factor))
440
Table 32 on page 441 shows the relationship between the fixed FEC limit, the configurable
signal degrade threshold, and the configurable clear threshold for different PICs. In this
example, approximately 1 dBQ of system margin has been set between the FEC limit,
signal degrade threshold, and clear threshold.
FEC Limit
PIC
FEC Type
Clear Threshold
2
Q -Factor
BER
Q -Factor
BER
Q -Factor
BER
SD-FEC
6.7 dBQ
1.5E2
7.7 dBQ
7.5E3
8.7 dBQ
3.0E3
P2-100GE-OTN
G.709 GFEC
11.5 dBQ
8.0E5
12.5 dBQ
1.1E5
13.5 dBQ
1.0E6
P1-PTX-24-10G-W-SFPP
G.975.1 I.4
(UFEC)
9.1 dBQ
2.2E3
10.1 dBQ
6.9E4
11.1 dBQ
1.6E4
G.975.1 I.7
(EFEC)
9.6 dBQ
1.3E3
10.6 dBQ
3.6E4
11.6 dBQ
7.5E5
G.709 GFEC
11.5 dBQ
8.0E5
12.5 dBQ
1.1E5
13.5 dBQ
1.0E6
P1-PTX-2-100G-WDM
PTX-2-100G-WDM-M
To adjust the signal degrade threshold, you must first decide on a new system margin
target and then calculate the respective BER value (using the equation to convert from
2
Q -factor to BER). Table 33 on page 441 shows the values if 3 dBQ of system margin
relative to the FEC limit is desired for the signal degrade threshold (while maintaining
the clear threshold at 1 dBQ relative to the signal degrade threshold).
FEC Limit
PIC
P1-PTX-2-100G-WDM
FEC Type
Clear Threshold
2
Q -Factor
BER
Q -Factor
BER
Q -Factor
BER
SD-FEC
6.7 dBQ
1.5E2
9.7 dBQ
1.1E3
10.7 dBQ
2.9E4
G.709 GFEC
11.5 dBQ
8.0E5
14.5 dBQ
4.9E8
15.5 dBQ
1.1E9
PTX-2-100G-WDM-M
P2-100GE-OTN
441
Table 33: ExampleSignal Degrade and Clear Thresholds After Configuration (continued)
Signal Degrade
Threshold
FEC Limit
PIC
FEC Type
P1-PTX-24-10G-W-SFPP
Clear Threshold
2
Q -Factor
BER
Q -Factor
BER
Q -Factor
BER
G.975.1 I.4
(UFEC)
9.1 dBQ
2.2E3
12.1 dBQ
2.8E5
13.1 dBQ
3.1E6
G.975.1 I.7
(EFEC)
9.6 dBQ
1.3E3
12.6 dBQ
1.1E5
13.6 dBQ
9.1E7
G.709 GFEC
11.5 dBQ
8.0E5
14.5 dBQ
4.8E8
15.5 dBQ
1.1E9
NOTE: Configuring a high BER threshold for signal degradation and a long
interval might cause the internal counter register to be saturated. Such a
configuration is ignored by the router, and the default values are used instead.
A system log message is logged for this error.
Related
Documentation
See wavelength.
442
See tca.
4. (Optional) Set the trace identifiers:
See tti.
5. (Optional) Specify defect triggers:
See trigger.
6. (Optional) Enable VLAN tagging. See Enabling VLAN Tagging.
7. (Optional) Set the media MTU. See Configuring the Media MTU.
8. (Optional) Set the unit VLAN ID, family inet, and IP address:
to monitor the pre-FEC BER status of the link and to insert the local pre-FEC status
into transmitted OTN frames:
[edit interfaces interface-name otn-options preemptive-fast-reroute]
user@host# set signal-degrade-monitor-enable
user@host# set backward-frr-enable
443
for monitoring the pre-forward error correction (pre-FEC) status of the OTN link:
a. Set the BER signal-degrade threshold:
Related
Documentation
444
level. Note that the term NA denotes that the statement is not applicable for that
particular component:
Table 34: Statements Supported on 100-Gigabit Ethernet PICs on PTX Series Routers
Statement
Options
bytes
(otn-options)
transmit-payloadtype value
P1-PTX-2-100G-WDM
(PTX5000 / PTX3000)
P2-100GE-OTN
(PTX5000)
P1-PTX-24-10G-W-SFPP
(PTX5000)
13.2/13.3
14.1R2
14.2
14.2
fec
13.2/13.3
14.1R2
14.2
14.2
(gfec, none)
insertodu-lck
13.2/13.3
14.1R2
14.2
14.2
insertodu-oci
13.2/13.3
14.1R2
14.2
14.2
is-ma
| no-is-ma
13.2/13.3
NA
14.2
laser-enable
| no-laser-enable
13.2/13.3
14.1R2
14.2
14.2
line-loopback
| no-line-loopback
13.2/13.3
14.1R2
14.2
14.2
local-loopback
|
no-local-loopback
13.2/13.3
14.1R2
14.2
odu-delay-management
bypass |
no-bypass
13.2/13.3
NA
NA
monitor-end-point |
no-monitor-end-point
13.2/13.3
NA
NA
number-of-frames value
13.2/13.3
NA
NA
no-start-measurement |
start-measurement
13.2/13.3
NA
NA
14.2
445
Options
P1-PTX-2-100G-WDM
(PTX5000 / PTX3000)
P2-100GE-OTN
(PTX5000)
P1-PTX-24-10G-W-SFPP
(PTX5000)
odu-signaldegrade
ber-threshold-clear value
NA
14.1R2
NA
NA
14.2
NA
14.1R2
NA
14.2
NA
14.1R2
ber-threshold-signal-degrade
value
interval value
NA
NA
14.2
odu-ttim-action-enable
|
no-odu-ttim-action-enable
otu-ttim-action-enable
|
no-otu-ttim-action-enable
prbs | no-prbs
13.2/13.3
14.1R2
14.2
14.2
13.2/13.3
14.1R2
14.2
14.2
13.2/13.3
14.1R2
14.2
14.2
preemptive-fast-reroute
backward-frr-enable |
no-backward-frr-enable
13.2/13.3
14.1R2
14.2
14.2
446
signal-degrade-monitor-enable
|
no-signal-degrade-monitor-enable
13.2/13.3
odu-backward-frr-enable
|
no-odu-backward-frr-enable
NA
odu-signal-degrade-monitor-enable
|
no-odu-signal-degrade-monitor-enable
NA
14.1R2
14.2
14.2
14.1R2
NA
14.2
14.1R2
NA
14.2
P2-100GE-OTN
(PTX5000)
P1-PTX-24-10G-W-SFPP
(PTX5000)
fixed-stuff-bytes |
no-fixed-stuff-bytes
13.2/13.3
NA
14.2
oc192
13.2/13.3
NA
14.2
otu4
13.2/13.3
14.1R2
NA
Statement
Options
rate
14.2
signal-degrade
pass-through |
no-pass-through
13.2/13.3
NA
NA
ber-threshold-clear value
13.2/13.3
14.1R2
14.2
14.2
ber-threshold-signal-degrade
value
13.2/13.3
14.1R2
14.2
14.2
interval value
13.2/13.3
14.1R2
14.2
14.2
447
P2-100GE-OTN
(PTX5000)
P1-PTX-24-10G-W-SFPP
(PTX5000)
odu-tca-bbe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
odu-tca-bbe-fe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
NA
14.2
odu-tca-es
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
odu-tca-es-fe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
NA
14.2
odu-tca-ses
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
odu-tca-ses-fe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
NA
14.2
odu-tca-uas
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
otu-tca-bbe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
13.2/13.3
NA
14.2
Statement
Options
tca
448
P1-PTX-2-100G-WDM
(PTX5000 / PTX3000)
P2-100GE-OTN
(PTX5000)
P1-PTX-24-10G-W-SFPP
(PTX5000)
otu-tca-es
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
otu-tca-es-fe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
NA
14.2
otu-tca-fec-ber
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
otu-tca-ses
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
otu-tca-ses-fe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
NA
14.2
otu-tca-uas
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
14.2
14.2
otu-tca-uas-fe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
13.2/13.3
NA
14.2
NA
NA
14.2
Options
otu-tca-bbe-fe
(enable-tca |
no-enable-tca |
threshold |
threshold-24hrs)
transport-monitoring
449
P2-100GE-OTN
(PTX5000)
P1-PTX-24-10G-W-SFPP
(PTX5000)
oc-lof
(hold-time (down | up) |
ignore)
13.2/13.3
14.1R2
14.2
oc-lom
(hold-time (down | up) |
ignore)
13.2/13.3
oc-los
(hold-time (down | up) |
ignore)
13.2/13.3
oc-tsf
(hold-time (down | up) |
ignore)
13.2/13.3
oc-wavelength-lock
(hold-time (down | up) |
ignore)
13.2/13.3
NA
14.2
odu-ais
(hold-time (down | up) |
ignore)
13.2/13.3
14.1R2
14.2
odu-bdi
(hold-time (down | up) |
ignore)
13.2/13.3
odu-bei
(hold-time (down | up) |
ignore)
13.2/13.3
odu-iae
(hold-time (down | up) |
ignore)
13.2/13.3
odu-lck
(hold-time (down | up) |
ignore)
13.2/13.3
odu-oci
(hold-time (down | up) |
ignore)
13.2/13.3
odu-sd (hold-time
(down | up) | ignore)
13.2/13.3
Statement
Options
trigger
trigger-identifier
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
odu-ttim
450
13.2/13.3
14.2
Options
P1-PTX-2-100G-WDM
(PTX5000 / PTX3000)
P2-100GE-OTN
(PTX5000)
P1-PTX-24-10G-W-SFPP
(PTX5000)
14.1R2
14.2
opu-ptim
(hold-time (down | up) |
ignore)
13.2/13.3
otu-ais
(hold-time (down | up) |
ignore)
13.2/13.3
otu-bdi
(hold-time (down | up) |
ignore)
13.2/13.3
otu-fec-deg
(hold-time (down | up) |
ignore)
13.2/13.3
otu-fec-exe
(hold-time (down | up) |
ignore)
13.2/13.3
otu-iae
(hold-time (down | up) |
ignore)
13.2/13.3
otu-sd
(hold-time (down | up) |
ignore)
13.2/13.3
13.2/13.3
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
451
Options
tti tti-identifier
odu-dapi
identifier
P1-PTX-2-100G-WDM
(PTX5000 / PTX3000)
P2-100GE-OTN
(PTX5000)
P1-PTX-24-10G-W-SFPP
(PTX5000)
13.2/13.3
14.1R2
14.2
14.2
odu-expectedreceive-dapi
identifier
13.2/13.3
odu-expectedreceive-sapi
identifier
13.2/13.3
odu-sapi
identifier
13.2/13.3
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
13.2/13.3
otu-dapi
identifier
14.1R2
14.2
14.2
otu-expectedreceive-dapi
identifier
13.2/13.3
otu-expectedreceive-sapi
identifier
13.2/13.3
otu-sapi
identifier
13.2/13.3
14.1R2
14.2
14.2
14.1R2
14.2
14.2
14.1R2
14.2
14.2
Related
Documentation
452
You can configure the interfaces on this PIC to be a part of the mixed rates and mixed
mode aggregated Ethernet bundles. For information about mixed rates, see
Understanding Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on
page 141.
Interface Features
The following interface features are supported on a P2-100GE-OTN PIC:
Each port maps to a single Packet Forwarding Engine in the FPC2-PTX-P1A FPC.
Link-level pause framesYou can halt the Ethernet interface from transmitting packets
for a configured period of time.
Interface hold timer and interface dampingYou can set the hold-time statement (in
milliseconds) to damp interface transitions.
External clock
453
For each 100-Gigabit Ethernet port, you can configure up to eight TPIDs by using the
tag-protocol-id statement at the [edit interfaces interface-name gigether-options
ethernet-switch-profile] hierarchy level.
The tag-protocol-id statement can be configured only on the first port (port 0) of
the PIC. If any other (nonzero) port has the tag-protocol-id configuration, the Routing
Engine registers an error in the system log and the configuration is ignored.
The tag-protocol-id statement configured on port 0 of the PIC also applies to the
rest of the ports on that PIC.
The interface Link Down event always generates an interrupt; however, the interface
Link Up event does not generate an interrupt. Therefore, the interface link-up event is
detected during the 1-second PIC periodic polling process.
Generic forward error correction (GFEC) (G.709) and no-FEC modes of operation.
Diagnostics tools:
Line loopback
Local loopback
Fast reroute (FRR)Based on configurable pre-FEC, bit error rate (BER) is supported
and is configured using the ber-threshold-signal-degrade statement at the [edit
interfaces interface-name otn-options signal-degrade] hierarchy level.
jnx-ifotn.mib and otn-mib as defined in RFC 3591. Note that according to Junos OS
security standard, configurable parameters are not supported through SNMP. Only
the get operation is available through SNMP.
At the logical interface level, dix, vlan-ccc, and vlan-tcc encapsulations are supported.
MAC policing
454
MAC detect link up and link down based on local fault signal or remote fault signal.
MAC statistics.
Flow control.
MAC oversized packet counters based on default MTU value or user-configured MTU
value.
Aggregated Ethernet supports 64 child links that can be configured using the set chassis
aggregated-devices maximum-links configuration command.
Support for VLAN tagging, flexible VLAN tagging, and stacked VLAN tagging.
LACP.
Link protection.
802.3 ah OAM.
802.1 ag OAM.
455
MPLS FRR.
SNMP.
LOSLoss Of Signal
LOFLoss Of Frame
LOMLoss Of Multiframe
OTUDegrade
OTUAIS
OTUIAE
OTUBDI
OTUTTIM
OTUSignal Degrade
OTUSignal Fail
ODUSignal Fail
OTU-FECDegrade
OTU-FECExcessive errors
ODUSignal Degrade
ODUAIS
ODUBDI
ODUOCI
ODULCK
ODUTTIM
OPUPTM
TCA Alarms
Threshold-crossing alarms (TCA) are alarms that are activated when a certain
configurable thresholdnear-end measurement threshold or far-end measurement
thresholdis crossed and remains so until the end of the 15 minute interval for parameters
such as OTU and ODU. The following alarms are supported:
456
Related
Documentation
2. Configure VLAN tagging on the OTN interface to enable the reception and transmission
2. Enable the laser on the OTN interface. The laser is disabled by default for all OTN
interfaces.
[edit interfaces interface-name otn-options]
457
up with a valueWait for the hold time delay before clearing the alarm when the
defect is absent on the OTN interface.
down with a valueWait for the hold time delay before raising the alarm when the
defect occurs for the OTN interface.
[edit interfaces interface-name otn-options]
user@host# set trigger (oc-lof | oc-lom | oc-los | oc-tsf | odu-ais | odu-bdi | odu-bei |
odu-iae | odu-lck | odu-oci | odu-sd | odu-ttim |opu-ptim | otu-ais | otu-bdi |
otu-fec-deg | otu-fec-exe | otu-iae | otu-sd | otu-ttim) (hold-time (down value | up
value) | ignore)
5. Enable the threshold crossing alarms for the OTN interface along with the trigger for
the defect.
6. Set the OTN header bytes as a transmit payload type from 0 bytes through 255 bytes
458
9. Enable an ODU locked maintenance signal on the OTN interface to send the signal
pattern 01010101.
[edit interfaces interface-name otn-options]
user@host# set insert-odu-lck
10. Enable an ODU open connection indication signal on the OTN interface to send to
interface.
[edit interfaces interface-name otn-options]
user@host# set prbs
14. Configure the OTN mode as OTU4 for the OTN interface.
Configure the threshold value after signal degradation when the alarm needs to be
cleared. When you configure the interval along with the ber-threshold-signal-degrade
value statement, the bit error rate (BER) must stay above the signal degradation
threshold for the configured interval after which the alarm is raised. When the interval
is configured along with the ber-threshold-clear value statement, then BER must stay
below the clear threshold for the configured interval after which the alarm is cleared.
[edit interfaces interface-name otn-options signal-degrade]
user@host# set ber-threshold-signal-degrade value
user@host# set ber-threshold-clear value
user@host# set interval value
16. Enable the following actions for the preemptive-fast-reroute statement:
Backward FRRInsert the local pre-FEC status into the transmitted OTN frames
and monitor the received OTN frames for the pre-FEC status.
[edit interfaces interface-name otn-options preemptive-fast-reroute]
user@host# set backward-frr-enable
ODU backward FRRInsert the ODU status into the transmitted OTN frames and
monitor the received OTN frames for the ODU BER status.
[edit interfaces interface-name otn-options preemptive-fast-reroute]
459
17. Configure the following options for ODU BER signal degradation on the OTN interface:
Configure the threshold for signal degradation for ODU BER when an alarm needs
to be raised.
[edit interfaces interface-name otn-options odu-signal-degrade]
user@host# set ber-threshold-signal-degrade value
Configure the threshold for ODU BER after signal degradation when the alarm needs
to be cleared.
[edit interfaces interface-name otn-options odu-signal-degrade]
user@host# set ber-threshold-clear value
When you configure the interval along with the ber-threshold-signal-degrade value
statement, the ODU bit error rate (BER) must stay above the signal degradation
threshold for the configured interval after which the alarm is raised. When the interval
is configured along with the ber-threshold-clear value statement, then ODU BER
must stay below the clear threshold for the configured interval after which the alarm
is cleared.
[edit interfaces interface-name otn-options odu-signal-degrade]
user@host# set interval value
Related
Documentation
460
CHAPTER 28
Capabilities of Gigabit Ethernet IQ PICs and Gigabit Ethernet PICs with SFPs on page 461
Capabilities of Gigabit Ethernet IQ PICs and Gigabit Ethernet PICs with SFPs
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 can
configure granular per-VLAN class-of-service (CoS) capabilities and extensive
instrumentation and diagnostics on a per-VLAN and per-MAC address basis.
VLAN rewrite, tagging, and deleting enables you to use VLAN address space to support
more customers and services.
VPLS allows you to provide a point-to-multipoint LAN between a set of sites in a VPN.
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) are combined with VPLS to
deliver metro Ethernet service.
For Gigabit Ethernet IQ2 and IQ2-E and 10-Gigabit Ethernet IQ2 and IQ2-E interfaces, you
can apply Layer 2 policing to logical interfaces in the egress or ingress direction. Layer 2
policers are configured at the [edit firewall] hierarchy level. You can also control the rate
of traffic sent or received on an interface by configuring a policer overhead at the [edit
chassis fpc slot-number pic slot-number] hierarchy level.
461
Table 35 on page 462 lists the capabilities of 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).
Gigabit
Ethernet (SFP)
Yes
Yes
384
1023
9192
9192
MAC learning
Yes
Yes
MAC accounting
Yes
Yes
MAC filtering
Yes
Yes
960
960
64
64
Yes, premium
and aggregate
No, aggregate
only
Yes
Yes
Yes
Yes
Yes
No
VLAN rewrite
Yes
No
VLAN CCC
Yes
Yes
Port-based CCC
Yes
Yes
Yes
Yes
Yes
Yes
Capability
Layer 2
Layer 2 VPNs
CoS
PIC-based egress queues
462
Capability
Gigabit
Ethernet IQ
(SFP)
Gigabit
Ethernet (SFP)
Queued VLANs
Yes
No
VPLS
Yes
Yes
For more information about configuring VPLS, see the Junos OS VPNs Library for Routing
Devices and the Junos OS, Release 15.1.
You can also configure CoS on logical IQ interfaces. For more information, see the Class
of Service Feature Guide for Routing Devices.
Related
Documentation
To prohibit an interface from dynamically learning source and destination MAC addresses,
do not include the mac-learn-enable statement.
To disable dynamic learning of the source and destination MAC addresses after it has
been configured, you must delete mac-learn-enable from the configuration.
463
Related
Documentation
Capabilities of Gigabit Ethernet IQ PICs and Gigabit Ethernet PICs with SFPs on page 461
464
triggered from the CLI. This method of data collection implies that based on the number
of child links and the size of the MAC database, the time take to display the database
differs. This approach to obtain the current snapshot of the MAC database from the
currently active child links is used instead of maintaining a database at the Routing Engine
because of the dynamic nature of the MAC database and the overhead required to
maintain the database information in synchronization with all the child Packet Forwarding
Engines. A difference in the DMAC-based accounting for packets generated from the
Routing Engine (packets sent in the host path). On DPCs, these packets are accounted
in egress direction (Output Packet/Byte count), whereas on MPCs, these packets are
not accounted because DMAC learning is not supported. This difference in behavior also
occurs between child links on DPCs and MPCs. Because this feature to enable dynamic
learning is related to collecting MAC database statistics from child links based on the
command issued from the CLI, there is a impact on the time it takes to display the data
on the console based on the size of the MAC database and the number of child-links
spread across different FPCs. The limit on the maximum number of MAC addresses that
can be learned from an interface does not apply to this dynamic learning of MAC addresses
functionality.
Related
Documentation
465
The input and output octets at the logical interface configured on the PIC includes all
the Layer 2 headers. All the logical interfaces on the PIC, including the ae and the non-ae
interfaces, are processed for Layer 2 overhead accounting for the arriving and exiting
packets. This method of operation impacts the transit statistics that are primarily used
for subscriber accounting and billing purposes in customer networks.
Table 36 on page 466 lists the adjustment bytes that are counted based on the
encapsulation on the logical interface over the Ethernet interface, when you enable
accounting of Layer 2 overhead in interface statistics at the PIC level. The values for the
adjustment bytes that are listed for all types of encapsulation are the same for DPCs
and MPCs, with the only exception being for the VLAN CCC adjustment value. On DPCs,
the VLAN CCC adjustment value is 4 bytes and on MPCs, the VLAN CCC adjustment
value is +4 bytes.
Table 36: Adjustment Bytes for Logical Interfaces over Ethernet Interfaces
Encapsulation Type on
Logical Interfaces
Number of Adjustment
Bytes
Description
18
22
26
VLAN Bridge
CRC
VLAN CCC
CRC
VLAN TCC
18
VLAN TCC
22
VLAN TCC
26
VLAN VPLS
CRC
466
When you configure a native VLAN ID on a logical interface, the Layer 2 header
adjustment for input statistics is different for tagged and untagged packets. For such
interfaces, if you configure the setting to account for Layer 2 overhead, incorrect
statistics might be displayed.
Related
Documentation
The computed statistics might not be completely accurate in scenarios where the
packets are dropped after they have been included in the interface statistics, but before
the packets reach the destination.
Layer 2 overhead accounting is not supported for inline service (si) interfaces.
The total statistics of interfaces do not indicate the complete Layer 2 adjusted statistics.
This behavior occurs because the total statistics count is the sum of transit and local
statistics. Only the transit statistics are adjusted for Layer 2 and the local statistics are
not adjusted for Layer 2.
Adjustment bytes are applicable only for transit statistics that are displayed for logical
interfaces.
For physical interfaces, the adjustment bytes for transit traffic and the non-adjusted
bytes for local or protocol-specific traffic are combined and displayed in the output of
the show interfaces command. (Segregation is not possible.)
Layer 2 overhead accounting can be enabled at both PIC level and logical interface
level.
The Layer 2 overhead bytes in interface statistics are saved across a unified ISSU or a
graceful Routing Engine switchover (GRES) operation.
467
Enabling the Accounting of Layer 2 Overhead in Interface Statistics at the PIC Level
You can configure the account-layer2-overhead statement at the edit chassis fpc
slot-number pic pic-number hierarchy level to enable accounting of Layer 2 overhead bytes
in the ingress and egress interface statistics at the PIC level.
CAUTION: If you modify the setting for accounting of Layer 2 overhead bytes
at the PIC level, the PIC is rebooted, causing all of the physical and logical
interfaces to be deleted and readded on the PIC. Due to this behavior, we
recommend that you exercise caution while using this feature.
For non-Ethernet interfaces, the Frame Relay, PPP, or Cisco HDLC headers are counted,
while the bit or byte stuffing headers are excluded.
To enable accounting of Layer 2 overhead at the PIC level for ingress and egress traffic
on interfaces:
1.
Access a DPC or an MPC-occupied slot and the PIC where the interface is to be
enabled.
[edit chassis]
user@host# edit fpc slot-number pic number
2. Specify the Layer 2 overhead value in bytes that is the octet adjustment per packet
added to the total octet count for ingress and egress traffic on all the interfaces in the
PIC.
[edit chassis fpc slot-number pic number]
user@host# set account-layer2-overhead
Action
468
Display information about the Layer 2 overhead bytes that are counted in interface
statistics for egress and ingress traffic on Ethernet interfaces.
To display information about the Layer 2 overhead bytes that are counted in interface
statistics:
NOTE: For physical and logical interfaces, the values displayed for the
Input rate and Output rate fields under the Traffic statistics section include
the Layer 2 overhead of the packets.
None,
Online
L2 channel
0, HS link
469
Logical interface ge-5/2/0.0 (Index 71) (SNMP ifIndex 573) (Generation 135)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
Egress account overhead: 100
Ingress account overhead: 90
Traffic statistics:
Input bytes :
271524
Output bytes :
37769598
Input packets:
3664
Output packets:
885790
IPv6 transit statistics:
Input bytes :
0
Output bytes :
16681118
Input packets:
0
Output packets:
362633
Local statistics:
Input bytes :
271524
Output bytes :
308560
Input packets:
3664
Output packets:
3659
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
37461038
0 bps
Input packets:
0
0 pps
Output packets:
882131
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
16681118
Input packets:
0
Output packets:
362633
Multicast statistics:
IPV4 multicast statistics:
Input bytes :
112048
0 bps
Output bytes :
20779920
0 bps
Input packets:
1801
0 pps
Output packets:
519498
0 pps
IPV6 multicast statistics:
Input bytes :
156500
0 bps
Output bytes :
16681118
0 bps
Input packets:
1818
0 pps
Output packets:
362633
0 pps
Protocol inet, MTU: 1500, Generation: 151, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 40.40.40.0/30, Local: 40.40.40.2, Broadcast: 40.40.40.3, Generation: 167
Protocol inet6, MTU: 1500, Generation: 152, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: ::40.40.40.0/126, Local: ::40.40.40.2
Generation: 169
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::21d:b5ff:fe61:d974
Protocol multiservice, MTU: Unlimited, Generation: 171
Generation: 153, Route table: 0
Policer: Input: __default_arp_policer__
Related
Documentation
470
NOTE:
On MX Series routers with Gigabit Ethernet or Fast Ethernet PICs, the following
considerations apply:
Interface counters do not count the 7-byte preamble and 1-byte frame
delimiter in Ethernet frames.
In MAC statistics, the frame size includes MAC header and CRC before any
VLAN rewrite/imposition rules are applied.
In traffic statistics, the frame size encompasses the L2 header without CRC
after any VLAN rewrite/imposition rule.
For information on understanding Ethernet frame statistics, see the MX Series Layer 2
Configuration Guide.
This section contains the following topics:
Configuring a Policer
To configure an Ethernet policer profile, include the ethernet-policer-profile statement
at the [edit interfaces interface-name gigether-options ethernet-switch-profile] hierarchy
level:
471
If you do not know the interface bandwidth, you can multiply the maximum MTU of the
traffic on the interface by 10 to obtain a value. For example, the burst size for an MTU of
4700 would be 47,000 bytes. The burst size should be at least 10 interface MTUs. The
maximum value for the burst-size limit is 100 MB.
The priority values can be from 0 through 7. The remaining traffic is classified as
nonpremium (or aggregate). For a configuration example, see Example: Configuring
Gigabit Ethernet Policers on page 476.
472
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.
You can define a forwarding class, or you can use a predefined forwarding class.
Table 37 on page 473 shows the predefined forwarding classes and their associated queue
assignments.
Queue
best-effort
Queue 0
expedited-forwarding
Queue 1
assured-forwarding
Queue 2
network-control
Queue 3
For more information about CoS forwarding classes, see the Class of Service Feature
Guide for Routing Devices. For a configuration example, see Example: Configuring Gigabit
Ethernet Policers on page 476.
Applying a Policer
On all MX Series Router interfaces, Gigabit Ethernet IQ, IQ2, and IQ2-E 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 can apply input and output policers that define rate
limits for premium and aggregate traffic received on the logical interface. Aggregate
473
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. For information about defining these policers, see Configuring Gigabit Ethernet
Policers on page 471.
To apply policers to specific source MAC addresses, include the accept-source-mac
statement:
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
NOTE: If the remote Ethernet card is changed, the interface does not accept
traffic from the new card because the new card has a different MAC address.
474
The MAC addresses you include in the configuration are entered into the routers MAC
database. To view the routers MAC database, enter the show interfaces mac-database
interface-name command:
user@host> show interfaces mac-database interface-name
In the input statement, list the name of one policer template to be evaluated when
packets are received on the interface.
In the output statement, list the name of one policer template to be evaluated when
packets are transmitted on the interface.
NOTE: On IQ2 and IQ2-E PIC interfaces, the default value for maximum
retention of entries in the MAC address table has changed, for cases in which
the table is not full. The new holding time is 12 hours. The previous retention
time of 3 minutes is still in effect when the table is full.
For more information about the source-filtering statement, see Enabling Ethernet MAC
Address Filtering on page 15.
To accept traffic even though it does not have a source address specified in the
accept-source-mac statement, include the no-source-filtering statement at the [edit
interfaces interface-name gigether-options] hierarchy level:
[edit interfaces interface-name gigether-options]
no-source-filtering;
For more information about the accept-source-mac statement, see Applying a Policer
on page 473.
475
476
}
}
}
}
unit 0 {
accept-source-mac {
mac-address 00:01:02:03:04:05 {
policer {
input policer-1;
output policer-1;
}
}
}
}
}
Related
Documentation
Capabilities of Gigabit Ethernet IQ PICs and Gigabit Ethernet PICs with SFPs on page 461
Two-color policerA two-color policer (or policer when used without qualification)
meters the traffic stream and classifies packets into two categories of packet loss
priority (PLP) according to a configured bandwidth and burst-size limit. You can mark
packets that exceed the bandwidth and burst-size limit in some way, or simply discard
them. A policer is most useful for metering traffic at the port (physical interface) level.
477
environment. This type of policer meters traffic based on the configured committed
information rate (CIR), committed burst size (CBS), and excess burst size (EBS).
Traffic is classified into the following three categories:
GreenBurst size of the packets that arrive is less than the sum of the configured
CIR and CBS.
RedBurst size of the packets that arrive is greater than the sum of the configured
CIR and EBS.
YellowBurst size of the packets that arrive is greater than the CBS but less than
the EBS.
Single-rate TCM is most useful when a service is structured according to packet length
and not peak arrival rate.
Two-rate Tricolor Marking (two-rate TCM)This type of policer is defined in RFC 2698,
A Two Rate Three Color Marker, as part of an assured forwarding per-hop-behavior
(PHB) classification system for a Differentiated Services (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 classified into the following three categories:
GreenBurst size of the packets that arrive is less than the sum of the configured
CIR and CBS.
RedBurst size of the packets that arrive is greater than the sum of the configured
PIR and EBS.
YellowTraffic does not belong to either the green or the red category.
Two-rate TCM is most useful when a service is structured according to arrival rates
and not necessarily packet length.
Unlike policing (described in Configuring Gigabit Ethernet Policers on page 471),
configuring two-color policers and tricolor marking policers requires that you configure
a firewall filter.
This section contains the following topics:
Configuring a Policer
Two-color and tricolor marking policers are configured at the [edit firewall] hierarchy
level.
A tricolor marking policer polices traffic on the basis of metering rates, including the CIR,
the PIR, their associated burst sizes, and any policing actions configured for the traffic.
478
For more information about configuring tricolor policer markings, see the Routing Policies,
Firewall Filters, and Traffic Policers Feature Guide for Routing Devices and the Class of
Service Feature Guide for Routing Devices.
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. To apply two-color or tricolor
policers, include the layer2-policer statement:
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
policer-name;
}
479
480
Related
Documentation
Capabilities of Gigabit Ethernet IQ PICs and Gigabit Ethernet PICs with SFPs on page 461
481
482
CHAPTER 29
NOTE:
Related
Documentation
483
484
Receive
Mode
LED
Link
Autonegotiation Status
ON
ON
Default
Green
UP
Complete
ON
OFF
Default
Red
DOWN
OFF
ON
Default
Red
DOWN
OFF
OFF
Default
Red
DOWN
ON
ON
Default
Red
DOWN
ON
ON
Default
Green
UP
ON
OFF
Default
Red
DOWN
OFF
OFF
Default
Red
DOWN
ON
ON
Default
Green
UP
ON
ON
Default
Red
DOWN
ON
ON
No-autonegotiation
Green
UP
ON
OFF
No-autonegotiation
Red
DOWN
OFF
ON
No-autonegotiation
Green
UP
OFF
OFF
No-autonegotiation
Red
DOWN
ON
ON
No-autonegotiation
Red
DOWN
ON
ON
Explicit
Green
UP
ON
OFF
Explicit
Red
DOWN
OFF
ON
Explicit
Red
DOWN
OFF
OFF
Explicit
Red
DOWN
ON
ON
Explicit
Red
DOWN
ON
ON
Explicit
Green
UP
ON
OFF
Explicit
Red
DOWN
OFF
ON
Explicit
Green
UP
OFF
OFF
Explicit
Red
DOWN
No-autonegotiation
Incomplete
Complete
No-autonegotiation
485
Receive
Mode
LED
Link
ON
ON
Explicit
Red
DOWN
ON
ON
Explicit+RFI-Offline
Green
UP
OFF
ON
Explicit+RFI-Offline
Red
DOWN
OFF
OFF
Explicit+RFI-Offline
Red
DOWN
ON
ON
Explicit+RFI-Offline
Red
DOWN
ON
ON
Explicit+RFI-Offline
Green
UP
ON
OFF
Explicit+RFI-Offline
Red
DOWN
OFF
ON
Explicit+RFI-Offline
Green
UP
OFF
OFF
Explicit+RFI-Offline
Red
DOWN
ON
ON
Explicit+RFI-Offline
Red
DOWN
ON
ON
Explicit+RFI-Offline
Red
DOWN
ON
OFF
Explicit+RFI-Offline
Red
DOWN
OFF
ON
Explicit+RFI-Online
Red
DOWN
OFF
OFF
Explicit+RFI-Online
Red
DOWN
ON
ON
Explicit+RFI-Online
Red
DOWN
ON
ON
Explicit+RFI-Online
Green
UP
ON
OFF
Explicit+RFI-Online
Red
DOWN
OFF
ON
Explicit+RFI-Online
Green
UP
OFF
OFF
Explicit+RFI-Online
Red
DOWN
ON
ON
Explicit+RFI-Online
Green
UP
ON
ON
Explicit+RFI-Online
Red
DOWN
ON
ON
Explicit+RFI-Online
Red
DOWN
ON
OFF
Explicit+RFI-Online
Red
DOWN
OFF
ON
Explicit+RFI-Online
Red
DOWN
486
Autonegotiation Status
Complete
No-autonegotiation
Complete
No-autonegotiation*
Complete
Receive
Mode
LED
Link
Autonegotiation Status
OFF
OFF
Explicit+RFI-Online
Red
DOWN
ON
ON
Explicit+RFI-Online
Red
DOWN
ON
ON
Explicit+RFI-Online
Green
UP
Complete
Receive
Mode
LED
Link
Autonegotiation Status
ON
ON
Default
Green
UP
Complete
ON
ON
Default
Red
DOWN
ON
OFF
Default
Red
DOWN
OFF
ON
Default
Red
DOWN
OFF
OFF
Default
Red
DOWN
ON
ON
No-autonegotiation
Green
UP
ON
ON
No-autonegotiation
Red
DOWN
ON
OFF
No-autonegotiation
Red
DOWN
OFF
ON
No-autonegotiation
Green
UP
OFF
OFF
No-autonegotiation
Red
DOWN
ON
ON
Explicit
Green
UP
ON
ON
Explicit
Red
DOWN
ON
OFF
Explicit
Red
DOWN
OFF
ON
Explicit
Red
DOWN
OFF
OFF
Explicit
Red
DOWN
ON
ON
Explicit
Red
DOWN
ON
OFF
Explicit
Red
DOWN
OFF
ON
Explicit
Red
DOWN
OFF
OFF
Explicit
Red
DOWN
Incomplete
Complete
Complete
487
Receive
Mode
LED
Link
Autonegotiation Status
ON
ON
Explicit+RFI-Offline
Red
DOWN
Complete
ON
OFF
Explicit+RFI-Offline
Red
DOWN
OFF
ON
Explicit+RFI-Offline
Red
DOWN
OFF
OFF
Explicit+RFI-Offline
Red
DOWN
ON
ON
Explicit+RFI-Online
Green
UP
ON
ON
Explicit+RFI-Online
Red
DOWN
ON
OFF
Explicit+RFI-Online
Red
DOWN
OFF
ON
Explicit+RFI-Online
Red
DOWN
OFF
OFF
Explicit+RFI-Online
Red
DOWN
Related
Documentation
488
Complete
CHAPTER 30
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489
Configuring Frames with Particular TPIDs to Be Processed as Tagged Frames on page 493
Configuring Inner and Outer TPIDs and VLAN IDs on page 495
Removing the Outer VLAN Tag and Rewriting the Inner VLAN Tag on page 502
Examples: Stacking and Rewriting Gigabit Ethernet IQ VLAN Tags on page 508
Understanding Transparent Tag Operations and IEEE 802.1p Inheritance on page 515
Configuring IEEE 802.1p Inheritance push and swap from the Transparent
Tag on page 517
489
You can stack and rewrite VLAN tags on the following interfaces:
Related
Documentation
Gigabit Ethernet
Gigabit Ethernet IQ
10-Gigabit Ethernet IQ2 and IQ2-E interfaces, and MX Series router Gigabit Ethernet
Interfaces
Tri-Rate Ethernet copper, and 10-Gigabit Ethernet interfaces with the VLAN
encapsulation type configured to support Layer 2 tunneling protocols such as circuit
cross-connect (CCC) or virtual private LAN service (VPLS) (as described in 802.1Q
VLANs Overview on page 244)
popRemove a VLAN tag from the top of the VLAN tag stack. The outer VLAN tag of
pop-popFor Ethernet IQ2, 10-Gigabit Ethernet LAN/WAN PIC, and IQ2-E interfaces,
remove both the outer and inner VLAN tags of the frame.
490
pop-swapFor Ethernet IQ2, 10-Gigabit Ethernet LAN/WAN PIC, and IQ2-E interfaces,
remove the outer VLAN tag of the frame, and replace the inner VLAN tag of the frame
with a user-specified VLAN tag value. The inner tag becomes the outer tag in the final
frame.
pushAdd a new VLAN tag to the top of the VLAN stack. An outer VLAN tag is pushed
push-pushFor Ethernet IQ2, 10-Gigabit Ethernet LAN/WAN PIC, and IQ2-E interfaces,
swap-pushFor Ethernet IQ2, 10-Gigabit Ethernet LAN/WAN PIC, and IQ2-E interfaces,
replace the outer VLAN tag of the frame with a user-specified VLAN tag value. A
user-specified outer VLAN tag is pushed in front. The outer tag becomes an inner tag
in the final frame.
swap-swapFor Ethernet IQ2, 10-Gigabit Ethernet LAN/WAN PIC, and IQ2-E interfaces,
replace both the inner and the outer VLAN tags of the incoming frame with a
user-specified VLAN tag value.
You configure VLAN rewrite operations for logical interfaces in the input VLAN map for
incoming frames and in the output VLAN map for outgoing frames. To configure the input
VLAN map, include the input-vlan-map statement:
input-vlan-map {
...interface-specific configuration...
}
The type of VLAN rewrite operation permitted depends upon whether the frame is
single-tagged or dual-tagged. Table 40 on page 491 shows supported rewrite operations
and whether they can be applied to single-tagged frames or dual-tagged frames. The
table also indicates the number of tags being added or removed during the operation.
Untagged
Single-Tagged
Dual-Tagged
Number of Tags
pop
No
Yes
Yes
push
Sometimes
Yes
Yes
+1
491
Untagged
Single-Tagged
Dual-Tagged
Number of Tags
swap
No
Yes
Yes
push-push
Sometimes
Yes
Yes
+2
swap-push
No
Yes
Yes
+1
swap-swap
No
No
Yes
pop-pop
No
No
Yes
pop-swap
No
No
Yes
The rewrite operations push and push-push can be valid in certain circumstances on
frames that are not tagged. For example, a single-tagged logical interface (interface 1)
and a dual-tagged logical interface (interface 2) have the following configurations:
Interface 1
Interface 2
492
none
push
pop
swap
push-push
swap-push
swap-swap
pop-pop
swap-pop
none
Yes
No
No
Yes
No
No
Yes
No
No
push
No
No
Yes
No
No
No
No
No
No
pop
No
Yes
No
No
No
No
No
No
No
swap
Yes
No
No
Yes
No
No
No
No
No
push-push
No
No
No
No
No
No
No
Yes
No
swap-push
No
No
No
No
No
No
No
No
Yes
swap-swap
Yes
No
No
No
No
No
Yes
No
No
pop-pop
No
No
No
No
Yes
No
No
No
No
pop-swap
No
No
No
No
No
Yes
No
No
No
You must know whether the VLAN rewrite operation is valid and is applied to the input
VLAN map or the output VLAN map. You must also know whether the rewrite operation
requires you to include statements to configure the inner and outer TPIDs and inner and
outer VLAN IDs in the input VLAN map or output VLAN map. For information about
configuring inner and outer TPIDs and inner and outer VLAN IDs, see Configuring Inner
and Outer TPIDs and VLAN IDs on page 495.
Related
Documentation
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489
493
tag-protocol-id [ tpids ];
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 ]] or [edit interfaces interface-name aggregated-ether-options
ethernet-switch-profile tag-protocol-id [ tpids ]] hierarchy level.
Related
Documentation
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489
Configuring Tag Protocol IDs (TPIDs) on PTX Series Packet Transport Routers
This topic describes how to configure the TPIDs expected to be sent or received on a
particular VLAN for PTX Series Packet Transport Routers.
For other types of Juniper Networks Ethernet PICs, you could configure 8 TPIDs per port.
However, the PTX Series Packet Transport Routers use MTIP and TL to classify a specific
TPID and Ethernet type. For MTIP, you can configure a maximum of 8 TPIDs for each
MAC chip.
As a consequence, you can specify the tag-protocol-id configuration statement only for
the first port (0) of a PTX Series Ethernet PIC. If you configure tag-protocol-id statements
on the other port, the configuration is ignored and a system error is recorded.
For example, the following is a supported configuration:
[edit interfaces et-2/0/0]
gigether-options {
ethernet-switch-profile {
tag-protocol-id [0x8100 0x9100];
}
}
494
Configuring Frames with Particular TPIDs to Be Processed as Tagged Frames on page 493
Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers on page 249
If you include the stacked-vlan-tagging statement in the configuration, you must configure
dual VLAN tags for all logical interfaces on the physical interface. For more information,
see Stacking a VLAN Tag on page 499.
Related
Documentation
The outer tag VLAN ID range is from 1 through 511 for normal interfaces, and from 512
through 4094 for VLAN CCC or VLAN VPLS interfaces. The inner tag is not restricted.
You must also include the stacked-vlan-tagging statement in the configuration. See
Examples: Stacking and Rewriting Gigabit Ethernet IQ VLAN Tags on page 508.
Related
Documentation
Examples: Stacking and Rewriting Gigabit Ethernet IQ VLAN Tags on page 508
495
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:
inner-tag-protocol-id tpid;
For the inner VLAN ID, include the inner-vlan-id statement. For the outer TPID, include
the tag-protocol-id statement. For the outer VLAN ID, include the vlan-id statement:
input-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
For aggregated Ethernet interfaces using Gigabit Ethernet IQ interfaces, include the
tag-protocol-id statement for the outer TPID. For the outer VLAN ID, include the vlan-id
statement:
input-vlan-map {
(pop | push | swap);
tag-protocol-id tpid;
vlan-id number;
}
output-vlan-map {
(pop | push | swap);
tag-protocol-id tpid;
vlan-id number;
}
496
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 on page 244.
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 ]] hierarchy level or [edit interfaces interface-name
aggregated-ether-options ethernet-switch-profile tag-protocol-id [ tpids ]] hierarchy level.
For more information, see Configuring Frames with Particular TPIDs to Be Processed as
Tagged Frames on page 493.
Table 42 on page 497 and Table 43 on page 498 specify when these statements are required.
Table 42 on page 497 indicates valid statement combinations for rewrite operations for
the input VLAN map. No means the statement must not be included in the input VLAN
map for the rewrite operation. Optional means the statement may be optionally specified
for the rewrite operation in the input VLAN map. Any means that you must include the
vlan-id statement, tag-protocol-id statement, inner-vlan-id statement, or
inner-tag-protocol-id statement.
Table 42: Rewrite Operations and Statement Usage for Input VLAN Maps
Input VLAN Map Statements
Rewrite Operation
vlan-id
tag-protocol-id
inner-vlan-id
inner-tag-protocol-id
push
Optional
Optional
No
No
pop
No
No
No
No
swap
Any
Any
No
No
push-push
Optional
Optional
Optional
optional
swap-push
Optional
Optional
Any
Any
swap-swap
Optional
Optional
Any
Any
pop-swap
No
No
Any
Any
pop-pop
No
No
No
No
Table 43 on page 498 indicates valid statement combinations for rewrite operations for
the output VLAN map. No means the statement must not be included in the output
VLAN map for the rewrite operation. Optional means the statement may be optionally
specified for the rewrite operation in the output VLAN map.
497
Table 43: 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
push
No
Optional
No
No
pop
No
No
No
No
swap
No
Optional
No
No
push-push
No
Optional
No
Optional
swap-push
No
Optional
No
Optional
swap-swap
No
Optional
No
Optional
pop-swap
No
No
No
Optional
pop-pop
No
No
No
No
The following examples use Table 42 on page 497 and Table 43 on page 498 and show
how the pop-swap operation can be configured in an input VLAN map and an output
VLAN map:
Input VLAN Map with
inner-vlan-id
Statement, Output
VLAN Map with
Optional
inner-tag-protocol-id
Statement
498
Related
Documentation
If you include the push statement in an interfaces input VLAN map, see Table 41 on
page 493 for information about permissible rewrite operations,
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 on page 244.
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 ]] hierarchy level. For more information, see Configuring Inner and
Outer TPIDs and VLAN IDs on page 495.
Related
Documentation
499
Configuring Inner and Outer TPIDs and VLAN IDs on page 495
See Table 42 on page 497 and Table 43 on page 498 for information about configuring inner
and outer VLAN ID values and inner and outer TPID values required for VLAN maps.
Related
Documentation
See Table 42 on page 497 and Table 43 on page 498 for information about configuring
inner and outer VLAN ID values and inner and outer TPID values required for VLAN
maps.
500
Related
Documentation
See Table 42 on page 497 and Table 43 on page 498 for information about configuring inner
and outer VLAN ID values and inner and outer TPID values required for VLAN maps.
Related
Documentation
501
See Table 42 on page 497 and Table 43 on page 498 for information about configuring
inner and outer VLAN ID values and inner and outer TPID values required for VLAN
maps.
Removing the Outer VLAN Tag and Rewriting the Inner VLAN Tag
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 the outer VLAN tag of the frame and replace the inner VLAN tag of
the frame with a user-specified VLAN tag value, include the pop-swap statement in the
input VLAN map or output VLAN map:
pop-swap;
The inner tag becomes the outer tag in the final frame.
You can include this statement at the following hierarchy levels:
See Table 42 on page 497 and Table 43 on page 498 for information about configuring inner
and outer VLAN ID values and inner and outer TPID values required for VLAN maps.
Related
Documentation
See Table 42 on page 497 and Table 43 on page 498 for information about configuring
inner and outer VLAN ID values and inner and outer TPID values required for VLAN
maps.
502
input-vlan-map {
swap;
vlan-id number;
tag-protocol-id tpid;
}
To rewrite the VLAN tag on all tagged frames exiting the interface to a specified VLAN
ID and TPID, include the swap and tag-protocol-id statements in the output VLAN map:
output-vlan-map {
swap;
vlan-id number;
tag-protocol-id tpid;
}
You cannot include both the swap statement and the vlan-id statement in the output
VLAN map configuration. If you include the swap statement in the configuration, the
VLAN ID in outgoing frames is rewritten to 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 on page 244.
The swap operation works on the outer tag only, whether or not you include the
stacked-vlan-tagging statement in the configuration. For more information, see Examples:
Stacking and Rewriting Gigabit Ethernet IQ VLAN Tags on page 508.
Related
Documentation
For more information about binding a VLAN ID to the logical interface, see 802.1Q
VLANs Overview on page 244.
For more information about the swap operation, see Examples: Stacking and Rewriting
Gigabit Ethernet IQ VLAN Tags on page 508.
503
On M Series routers with Gigabit Ethernet IQ2 PICs and Gigabit Ethernet Enhanced IQ2
(IQ2E) PICs, you can perform all the rewrite VLAN tag operations.
Consider a network where two provider edges (PE) are connected by a Layer 2 circuit.
PE1 is receiving traffic on an untagged port while the corresponding port on PE2 is tagged.
In the normal case, packets coming from PE1 will be dropped at PE2 because it is expecting
tagged packets. However, if PE1 can push a VLAN tag on the incoming packet before
sending it across to PE2, you can ensure that packets are not dropped. To make it work
in both directions, PE1 must strip the VLAN tag from outgoing packets. Therefore, a push
on the ingress side is always paired with a pop on the egress side.
The rewrite operations represented by the following statement options are supported
under ethernet-ccc and ethernet-vpls encapsulations:
push-pushAn outer and inner VLAN tag are added to the incoming untagged frame.
pop-popBoth the outer and inner VLAN tags of the outgoing frame are removed.
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 and pop-pop operations are not supported on the
Gigabit Ethernet IQ PIC.
504
For the input-vlan-map statement, only the push and push-push options are supported
because it does not make sense to remove a VLAN tag from an incoming untagged frame.
Similarly, only the pop and pop-pop options are supported for the output-vlan-map
statement. Also, with the push and push-push options, the tag parameters have to be
explicitly specified. Apart from this, the other rules for configuring the input-vlan-map
and output-vlan-map statements are the same as for tagged frames. Table 44 on page 505
through Table 46 on page 505 explain the rules in more detail.
For the input-vlan-map statement, only the push and push-push options are supported
because it does not make sense to remove a VLAN tag from an incoming untagged frame.
Similarly, only the pop and pop-pop options are supported for the output-vlan-map
statement. Also, with the push and push-push options, the vlan-id parameters (vlan-id
for push and vlan-id or inner-vlan-id for push-push) have to be explicitly specified. TPID
however, is optional and the default value of 0x8100 is set if not configured. Apart from
this, the other rules for configuring the input-vlan-map and output-vlan-map statements
are the same as for tagged frames.
Table 44: Input VLAN Map Statements Allowed for ethernet-ccc and ethernet-vpls
Encapsulations
Operation
vlan-id
tag-protocol-id
inner-vlan-id
inner-tag-protocol-id
push
Yes
Optional
No
Optional
push-push
Yes
Optional
Yes
Optional
Table 45: Output VLAN Map Statements Allowed for ethernet-ccc and ethernet-vpls
Encapsulations
Operation
vlan-id
tag-protocol-id
inner-vlan-id
inner-tag-protocol-id
pop
No
No
No
No
pop-pop
No
No
No
No
None
pop
pop-pop
None
Yes
No
No
push
No
Yes
No
push-push
No
No
Yes
ge-3/1/0 {
encapsulation ethernet-ccc;
unit 0 {
encapsulation ethernet-ccc;
input-vlan-map {
push;
505
tag-protocol-id 0x8100;
vlan-id 600;
}
output-vlan-map pop;
family ccc;
}
}
Example: push-push
and pop-pop with
Ethernet CCC
Encapsulation
Example: push-push
and pop-pop with
Ethernet VPLS
Encapsulation
506
ge-3/1/0 {
encapsulation ethernet-ccc;
unit 0 {
encapsulation ethernet-ccc;
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 ccc;
}
}
ge-3/1/0 {
encapsulation ethernet-vpls;
unit 0 {
encapsulation ethernet-vpls;
input-vlan-map {
push;
tag-protocol-id 0x8100;
vlan-id 700;
}
output-vlan-map pop;
family vpls;
}
}
ge-3/1/0 {
encapsulation ethernet-vpls;
unit 0 {
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
modified VLAN map for the specified interface.
Related
Documentation
A user-specified outer VLAN tag is pushed in front. The outer tag becomes an inner tag
in the final frame.
You can include this statement at the following hierarchy levels:
See Table 42 on page 497 and Table 43 on page 498 for information about configuring inner
and outer VLAN ID values and inner and outer TPID values required for VLAN maps.
Related
Documentation
507
See Table 42 on page 497 and Table 43 on page 498 for information about configuring inner
and outer VLAN ID values and inner and outer TPID values required for VLAN maps.
Related
Documentation
508
Swap the Outer VLAN Tag and Push a New VLAN Tag on Ingress; Pop the Outer VLAN
Tag and Swap the Inner VLAN Tag on Egress on page 512
Swap a TPID and VLAN ID Pair for Both VLAN Tags on Ingress and on Egress on page 513
Pop the Outer VLAN Tag and Swap the Inner VLAN Tag on Ingress; Swap the Outer
VLAN Tag and Push a New VLAN Tag on Egress on page 513
Pop a TPID and VLAN ID Pair on Ingress; Push a VLAN ID and TPID Pair on Egress on
page 513
Pop an Outer VLAN Tag to Connect an Untagged VPLS Interface to Tagged VPLS
Interfaces on page 514
[edit interfaces]
ge-4/0/0 {
vlan-tagging;
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;
vlan-id 515;
input-vlan-map {
swap-push;
vlan-id 520;
inner-vlan-id 512;
}
output-vlan-map {
pop-swap;
}
}
[edit protocols]
mpls {
interface ge-4/0/0.0;
interface ge-4/2/0.0;
}
connections {
interface-switch vlan-tag-push {
interface ge-4/0/0.0;
interface ge-4/2/0.0;
}
509
}
}
Swap a VLAN ID on
Ingress
510
[edit interfaces]
ge-0/2/0 {
stacked-vlan-tagging;
mac 00.01.02.03.04.05;
gigether-options {
loopback;
}
unit 0 {
vlan-tags outer 0x8100.200 inner 0x8100.200;
}
}
[edit interfaces]
ge-4/0/0 {
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;
encapsulation vlan-ccc;
...
unit 1 {
encapsulation vlan-ccc;
vlan-id 2000;
input-vlan-map {
swap;
tag-protocol-id 0x9100;
vlan-id 1000;
}
}
[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;
interface ge-4/0/0.1;
}
}
}
Swap a VLAN ID on
Egress
[edit interfaces]
ge-4/0/0 {
vlan-tagging;
encapsulation vlan-ccc;
...
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;
interface ge-4/2/0.1;
}
connections {
...
interface-switch vlan-tag-swap {
interface ge-4/2/0.1;
interface ge-4/0/0.1;
}
}
Swap a VLAN ID on
Both Ingress and
Egress
[edit interfaces]
ge-4/0/0 {
vlan-tagging;
encapsulation vlan-ccc;
gigether-options {
511
ethernet-switch-profile {
tag-protocol-id [ 0x8800 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;
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;
interface ge-4/0/0.1;
}
}
512
[edit interfaces]
ge-1/1/0 {
unit 1 {
vlan-id 200;
input-vlan-map {
swap-push;
tag-protocol-id 0x9100;
vlan-id 400;
inner-tag-protocol-id 0x9100;
inner-vlan-id 500;
}
output-vlan-map {
pop-swap;
inner-tag-protocol-id 0x9100;
}
}
}
[edit interfaces]
ge-1/1/0 {
unit 0 {
vlan-tags {
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;
}
}
}
[edit interfaces]
ge-1/1/0 {
unit 0 {
vlan-tags {
inner 0x9100.425;
outer 0x9200.525;
}
input-vlan-map {
pop-swap;
tag-protocol-id 0x9100;
vlan-id 400;
}
output-vlan-map{
swap-push;
tag-protocol-id 0x9200;
inner-tag-protocol-id 0x9100;
}
}
}
[edit interfaces]
ge-1/1/0 {
unit 0 {
vlan-tags {
inner 0x9100.425;
513
outer 0x9200.525;
}
input-vlan-map{
pop-pop;
}
output-vlan-map {
push-push;
tag-protocol-id 0x9200;
inner-tag-protocol-id 0x9100;
}
}
}
Related
Documentation
514
[edit interfaces]
ge-1/1/0 {
vlan-tagging;
encapsulation extended-vlan-vpls;
unit 0 {
vlan-id 0;
input-vlan-map {
push;
vlan-id 0;
}
output-vlan-map pop;
family vpls;
}
}
Untagged
Logical
Interface
Transparent tag
IEEE 802.1p
Inheritance
Single-tagged
Logical
Interface
Change in number of
tags
push-push
yes
OUTER, INNER
NA
no operation
+2
swap-push
NA
no operation
yes
OUTER, INNER
+1
push
yes
OUTER
yes
*none
+1
swap
NA
NA
yes
OUTER
NOTE: *In a push operation on a single-tagged logical interface, none of the tags (inner, or outer) inherit the IEEE 802.1p bits
from the transparent tag.
The following section shows four different examples of the inheritance of the transparent
IEEE 802.1p values into the outer and inner VLAN tags.
Figure 27 on page 515 shows an incoming packet with a transparent tag. A swap-push
operation swaps the outer VLAN tag and pushes another VLAN tag. The IEEE 802.1p
values are inherited from the transparent tag.
S.1p
100
0x9100
H.1p
1000
g017527
(swap-push)
H.1p
Outer VLAN tag
400
0x9100
H.1p
Inner VLAN tag
500
0x9100
H.1p
1000
transparent
515
Figure 28 on page 516 shows an incoming packet with no transparent tag. A swap-push
operation swaps the outer VLAN tag and pushes another VLAN tag. The IEEE 802.1p
value is set to zero, as there is no transparent tag.
S.1p
100
g017528
(swap-push)
400
0x9100
500
Figure 29 on page 516 shows an incoming packet with a transparent tag. A push operation
pushes another VLAN tag. The IEEE 802.1p value is inherited from the transparent tag.
1000
g017529
0x9100
(push)
Outgoing Packet tags: (802.1p set from transparent tag)
0x9100
H.1p
400
0x9100
H.1p
1000
transparent
Figure 30 on page 516 shows an incoming packet with a transparent tag. A push-push
operation pushes the outer and inner VLAN tags, respectively. The IEEE 802.1p values
are inherited from the transparent tag.
1000
g017530
0x9100
(push-push)
Outgoing Packet tags: (802.1p copied from transparent tag)
0x9100
H.1p
Outer VLAN tag
Related
Documentation
516
400
0x9100
H.1p
Inner VLAN tag
500
0x9100
H.1p
1000
transparent
Understanding IEEE 802.1p Inheritance push and swap from a Transparent Tag
Configuring IEEE 802.1p Inheritance push and swap from the Transparent Tag on
page 517
transparent
Understanding swap-by-poppush
By default, during a swap operation, the IEEE 802.1p bits of the VLAN tag remain
unchanged. When the swap-by-poppush operation is enabled on a logical interface, the
swap operation is treated as a pop operation followed by push operation. The pop
operation removes the existing tag and the associated IEEE 802.1p bits and the push
operation copies the inner VLAN IEEE 802.1p bits to the IEEE bits of the VLAN or VLANs
being pushed. As a result, the IEEE 802.1p bits are inherited from the incoming transparent
tag.
In effect, swap-by-poppush serves as a VLAN operation property and is used along with
a swap or swap-push VLAN rewrite operation, indicating the nature of the swap operation
being performed.
Related
Documentation
transparent
Understanding IEEE 802.1p Inheritance push and swap from a Transparent Tag
Configuring IEEE 802.1p Inheritance push and swap from the Transparent Tag on
page 517
Understanding Transparent Tag Operations and IEEE 802.1p Inheritance on page 515
Configuring IEEE 802.1p Inheritance push and swap from the Transparent Tag
To classify incoming packets based on the IEEE 802.1p bits from the transparent tag,
include the transparent statement at the [edit class-of-service interfaces interface-name
unit logical-unit-number classifiers ieee-802.1 vlan-tag] hierarchy level.
Tagged Interface
Example
The following example configuration specifies the classification based on the transparent
VLAN tag.
edit
class-of-service {
interfaces {
ge-3/0/1 {
unit 0 {
classifiers {
ieee-802.1 default vlan-tag transparent;
}
}
}
}
}
517
To configure Junos OS to inherit the IEEE 802.1p bits from the transparent tag, include
the swap-by-poppush statement at the [edit interfaces interface-name unit
logical-unit-number] hierarchy level.
The following is a configuration to swap and push VLAN tags and allow inheritance of
the IEEE 802.1p value from the transparent VLAN tag in incoming packets.
edit
ge-3/0/0 {
vlan-tagging;
encapsulation vlan-ccc;
unit 0 {
encapsulation vlan-ccc;
vlan-id 100;
swap-by-poppush;
input-vlan-map {
swap-push;
tag-protocol-id 0x9100;
inner-tag-protocol-id 0x9100;
vlan-id 500;
inner-vlan-id 400;
}
output-vlan-map {
pop-swap;
inner-vlan-id 100;
inner-tag-protocol-id 0x88a8;
}
}
}
The following is a configuration to push two VLAN tags and allow inheritance of the IEEE
802.1p value from the transparent VLAN tag in the incoming packet.
[edit]
ge-3/0/1 {
encapsulation ccc;
unit 0 {
input-vlan-map {
push-push;
tag-protocol-id 0x9100;
inner-tag-protocol-id 0x9100;
vlan-id 500;
inner-vlan-id 400;
}
output-vlan-map{
pop-pop;
}
}
}
518
No additional configuration is required to inherit the IEEE 802.1p value, as the push
operation inherits the IEEE 802.1p values by default.
The following configuration specifies the classification based on the transparent VLAN
tag.
[edit]
class-of-service {
interfaces {
ge-3/0/1 {
unit 0 {
classifiers {
ieee-802.1 default vlan-tag transparent;
}
}
}
}
}
Related
Documentation
transparent
Understanding IEEE 802.1p Inheritance push and swap from a Transparent Tag
Understanding Transparent Tag Operations and IEEE 802.1p Inheritance on page 515
519
520
PART 3
521
522
CHAPTER 31
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Example: Configuring an Action Profile Based on Connection Protection TLVs on page 569
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
523
Rely only on the media access control (MAC) address or virtual local area network
(VLAN) identifier for troubleshooting.
Work independently of the actual Ethernet transport and function over physical Ethernet
ports, or a virtual service such as pseudowire, and so on.
Isolate faults over a flat (or single operator) network architecture or a nested or
hierarchical (or multi-provider) network.
OAM can provide simple link-level information, provide performance statistics, or track
end-to-end connectivity across the network. Simple link fault management (LFM) for
Ethernet links is defined in IEEE 802.3ah.
IEEE 802.1ag OAM is supported on untagged, single tagged, and stacked VLAN interfaces.
Ethernet OAM functions are implemented as:
Fault isolation, verification, and recovery (isolation and verification are provided by a
combination of protocols, while recovery is the function of protocols such as spanning
tree)
The loopback protocol used in Ethernet OAM is modeled on the standard IP ping. After
a fault is detected, the loopback protocol performs fault verification and isolation under
the direction of a network operator.
The loopback is performed using request and response message pairs. A unicast loopback
message is generated by a maintenance endpoint (MEP), and a loopback reply is
generated by the destination maintenance intermediate point (MIP) or MEP.
The target MAC address is learned by the continuity check protocol or linktrace protocol.
The loopback message's packet is always forwarded to a unique port by the originating
MEP, as determined by a MAC table lookup or the MEP interface MAC address.
The target MIP or MEP generates a unicast loopback reply in response to the received
loopback message. The loopback message follows the same path as a data packet, and
intermediate bridges simply forward the packet to the destination MIP or MEP.
524
Related
Documentation
NOTE:
525
IEEE 802.1ag OAM supports graceful Routing Engine switchover (GRES). IEEE 802.1ag
OAM is supported on untagged, single tagged, and stacked VLAN interfaces.
Best Practices for Configuring 802.1ag Ethernet OAM for VPLS on page 527
526
NOTE: Maintenance intermediate points (MIP) are not supported on the ACX
Series routers.
vlan-id vlan-number
vlan-id none
527
Related
Documentation
802.1ag Ethernet OAM for VPLS uses implicit interface filters and
forwarding table filters to flood, accept, and drop the CFM packets.
For Down MEPs, the packets are transmitted on the interface on which
the MEP is configured.
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
528
Configuring Multiple Down MEPs for a Single Maintenance Domain on page 530
A domain name service (DNS) format, a MAC address plus a two-octet identifier in
the range from 0 through 65,535, or none.
A MAC address plus a two-octet identifier in the range from 0 through 65,535.
Or none.
NOTE:
529
To configure the maintenance domain level, include the level number statement at the
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name] hierarchy level.
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
530
531
532
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
As the VLAN identifier of the VLAN you primarily associate with the maintenance
association
Related
Documentation
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
533
receiving MEPs use the continuity check messages to build a MEP database of all MEPs
in the maintenance association.
The continuity check protocol packets use the ethertype value 0x8902 and the multicast
destination MAC address 01:80:c2:00:00:32.
hold-interval minutes
interval time
loss-threshold number
detect-loc
To enable the continuity check protocol, include the continuity-check statement at the
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name] hierarchy level.
NOTE: Hold timer based flushing is applicable only for auto discovered remote
MEPs and not for statically configured remote MEPs.
534
To configure the interval, include the interval statement at the [edit protocols oam ethernet
connectivity-fault-management maintenance-domain md-name maintenance-association
ma-name continuity-check] hierarchy level.
535
Continuity Measurement
Continuity measurement is provided by an existing continuity check protocol. The
continuity for every remote MEP is measured as the percentage of time that remote MEP
was operationally up over the total administratively enabled time. Here, the operational
uptime is the total time during which the CCM adjacency is active for a particular remote
MEP and the administrative enabled time is the total time during which the local MEP is
active. You can also restart the continuity measurement by clearing the currently measured
operational uptime and the administrative enabled time.
Related
Documentation
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
configure multiple down MEPs for a single instance of maintenance domain and
maintenance association to monitor services provided on the VPLS, bridge, circuit
cross-connect (CCC), and IPv4 domains.
536
Configuring the Transmission Direction for CFM packets for a MEP on page 537
Configuring the Lowest Priority Defect for Which an MEP Should Generate an
Alarm on page 538
Configuring MEP Service Protection for VPWS over MPLS on page 540
NOTE: Ports in the Spanning Tree Protocol (STP) blocking state do not block
CFM packets destined to a down MEP. Ports in an STP blocking state without
the continuity check protocol configured do block CFM packets.
To configure the MEP direction, include the direction statement at the [edit protocols
oam ethernet connectivity-fault-management maintenance-domain domain-name
maintenance-association ma-name mep mep-id] hierarchy level.
NOTE: Starting with Junos OS Release 12.3, for all interfaces configured on
Modular Port Concentrators (MPCs) on MX Series 3D Universal Edge Routers,
you no longer need to configure the no-control-word statement for all Layer
2 VPNs and Layer 2 circuits over which you are running CFM MEPs. For all
other interfaces on MX Series routers and on all other routers and switches,
you must continue to configure the no-control-word statement at the [edit
routing-instances routing-instance-name protocols l2vpn] or [edit protocols
l2circuit neighbor neighbor-id interface interface-name] hierarchy level when
you configure CFM MEPs. Otherwise, the CFM packets are not transmitted,
and the show oam ethernet connectivity-fault-management mep-database
command does not display any remote MEPs.
537
Configuring the Lowest Priority Defect for Which an MEP Should Generate an Alarm
You can specify the lowest priority defect that is allowed to generate a fault alarm. This
configuration determines whether to generate a fault alarm whenever it detects a defect.
This configuration is done at the MEP level.
To configure the lowest priority defect, include the lowest-priority-defect options statement
at the [edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id] hierarchy level.
Table 48 on page 538 describes the available lowest priority defect options.
Description
all-defects
err-xcon
Allows only erroneous CCM and cross-connect CCM defects to raise an alarm.
mac-rem-err-xcon
Allows only MAC, not receiving CCM, erroneous CCM, and cross-connect defects to raise
an .
538
Description
no-defect
rem-err-xcon
Allows only not receiving CCM, erroneous CCM, and cross-connect CCM defects to raise
an alarm.
xcon
hierarchy level. The profile must already be defined at the [edit protocols oam ethernet
connectivity-fault-management] hierarchy level.
539
statement, specify the path as (working | protect). The direction must also be configured
as direction down for both sessions.
NOTE: If the path is not specified, the session monitors the active path.
Description
working
protect
The following configuration example shows that service protection is enabled for the
VPWS service. The CCM session is configured for the working path and references the
CCM session configured for the protect path in the protect-maintenance-association
statement. The APS profile is configured and associated with the maintenance association
for the working path:
[edit protocols]
oam {
ethernet {
connectivity-fault-management {
maintenance-domain vpws-service-1 {
name-format none;
540
level 5;
maintenance-association W {
short-name-format character-string;
protect-maintenance-association P {
aps-profile aps-profile-1;
}
continuity-check {
interval 1s;
}
mep 1 {
interface ge-1/3/5.0 working;
direction down;
auto-discovery;
}
}
maintenance-association P {
short-name-format character-string;
continuity-check {
interval 1s;
}
mep 1 {
interface ge-1/3/5.0 protect;
direction down;
auto-discovery;
}
}
}
}
}
}
Related
Documentation
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
541
542
action-profile bring-down {
default-actions {
interface-down;
}
}
maintenance-domain md1 {
level 0;
maintenance-association ma1 {
continuity-check {
interval 100 ms;
}
mep 4001 {
interface ge-4/1/0;
direction down;
remote-mep 1 {
action-profile bring-down;
}
}
}
}
}
}
}
}
hierarchy level.
543
To configure an RDI event to bring an interface down on reception of an RDI bit from a
MEP, include the rdi statement at the (edit protocols oam ethernet
connectivity-fault-management action-profile profile-name event] hierarchy level.
[edit protocols oam]
ethernet {
connectivity-fault-management {
action-profile bring-down {
event {
adjacency-loss;
interface-status-tlv (down | lower-layer-down);
port-status-tlv blocked;
rdi;
}
action {
interface-down;
}
clear-action {
interface-down peer-interface ;
}
}
}
}
NOTE: You cannot configure multiple actions at this time. Only one action
can be configured. This limitation affects both the action and clear-action
statements.
Related
Documentation
544
event (CFM)
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
545
The E-LMI specification is available at the Metro Ethernet Forum. E-LMI procedures and
protocols are used for enabling automatic configuration of the customer edge (CE) to
support Metro Ethernet services. The E-LMI protocol also provides user-to-network
interface (UNI) and Ethernet virtual connection (EVC) status information to the CE. The
UNI and EVC information enables automatic configuration of CE operation based on the
Metro Ethernet configuration.
The E-LMI protocol operates between the CE device and the provider edge (PE) device.
It runs only on the PE-CE link and notifies the CE of connectivity status and configuration
parameters of Ethernet services available on the CE port. The scope of the E-LMI protocol
is shown in Figure 33 on page 546.
UNI
E-LMI
UNI
E-LMI
CE
g017277
CE
The E-LMI implementation on MX Series routers includes only the PE side of the E-LMI
protocol.
E-LMI interoperates with an OAM protocol, such as Connectivity Fault Management
(CFM), that runs within the provider network to collect OAM status. CFM runs at the
provider maintenance level (UNI-N to UNI-N with up MEPs at the UNI). E-LMI relies on
the CFM for end-to-end status of EVCs across CFM domains (SVLAN domain or VPLS).
The E-LMI protocol relays the following information:
546
UNI attributes:
CE-VLAN ID/EVC map type (all-to-one bundling, service multiplexing with bundling,
or no bundling)
CM (coupling mode)
CF (color flag)
EVC attributes:
EVC reference ID
547
Enabling E-LMI on an Interface and Mapping CE VLAN IDs to an EVC on page 548
548
vlan-list [ vlan-ids ];
}
evc-map-type (all-to-one-bundling | bundling | service-multiplexing);
polling-verification-time value; # Optional, defaults to global value
status-counter count; # Optional, defaults to global value
uni-id value; # Optional, defaults to interface-name
}
}
You can set the status counter to count consecutive errors using the status-counter count
statement at the [edit protocols oam ethernet lmi] hierarchy level. The status counter is
used to determine if E-LMI is operational or not. The default value is 4.
You can set the polling-verification-timer value statement at the [edit protocols oam
ethernet lmi] hierarchy level. The default value is 15 seconds.
You can enable an interface and set its options for use with E-LMI using the interface
name statement at the [edit protocols oam ethernet lmi] hierarchy level. Only ge, xe, and
ae interfaces are supported. You can use the interface uni-id option to specify a name
for the UNI. If uni-id is not configured, it defaults to the name variable of interface name.
You can specify the CE-VLAN ID/EVC map type using the evc-map-type type interface
option. The options are all-to-one-bundling, bundling, or service-multiplexing. Service
multiplexing is with no bundling. The default type is all-to-one-bundling.
To specify the EVC that an interface uses, use the evc evc-id statement at the [edit
protocols oam ethernet lmi interface name] hierarchy level. You can specify an interface
as the default EVC interface using the default-evc statement at the [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.
You can map a list of VLANs to an EVC using the vlan-list vlan-id-list statement at the
[edit protocols oam ethernet lmi interface name evc evc-id] hierarchy level.
ge-1/1/1
PE1
ge-1/1/2
ge-2/2/2
PE2
ge-2/2/1
CE2
CFM sessions
UNI-C
E-LMI
UNI-N
CFM up MEP
Ethernet Virtual Connections
UNI-N
E-LMI
UNI-C
g017278
CFM up MEP
549
Configuring PE1
[edit]
interfaces {
ge-1/1/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-1/1/2 {
unit 0 {
vlan-id 100;
family bridge {
interface-mode trunk;
inner-vlan-id-list 1-2048;
}
}
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;
}
}
maintenance-association 2049 {
name-format vlan;
mep 1 {
direction up;
interface ge-1/1/1.1 vlan 2049;
}
}
550
}
}
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;
remote-uni-count 1;
}
}
lmi {
interface ge-1/1/1 {
evc evc1 {
vlan-list 1-2048;
}
evc evc2 {
vlan-list 2049-4096;
}
evc-map-type bundling;
uni-id uni-ce1;
}
}
}
}
}
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;
family bridge {
interface-mode trunk;
inner-vlan-id-list 1-2048;
}
}
unit 1 {
vlan-id 200;
551
family bridge {
interface-mode trunk;
inner-vlan-id-list 2049-4095;
}
}
}
}
protocols {
oam {
ethernet {
connectivity-fault-management {
maintenance-domain md {
level 0;
maintenance-association 1 {
name-format vlan;
mep 1 {
direction up;
interface ge-2/2/1.0 vlan 1;
}
}
maintenance-association 2049 {
name-format vlan;
mep 1 {
direction up;
interface ge-2/2/1.1 vlan 2049;
}
}
}
}
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;
}
evc-map-type bundling;
uni-id uni-ce2;
}
}
}
}
}
552
Related
Documentation
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
553
TLVs Overview
Type, Length, and Value (TLVs) are described in the IEEE 802.1ag standard for CFM as
a method of encoding variable-length and/or optional information in a PDU. TLVs are
not aligned to any particular word or octet boundary. TLVs follow each other with no
padding between them.
Table 50 on page 554 shows the TLV format and indicates if it is required or optional.
Octet (sequence)
Description
Type
Length
23
Required if the Type field is not 0. Not present if the Type field is 0. The 16 bits
of the Length field indicate the size, in octets, of the Value field. 0 in the Length
field indicates that there is no Value field.
Value
Length specified by the Length field. Optional. Not present if the Type field is
0 or if the Length field is 0.
Table 51: Type Field Values for Various TLVs for CFM PDUs
TLV or Organization
Type Field
End TLV
Sender ID TLV
Data TLV
554
Table 51: Type Field Values for Various TLVs for CFM PDUs (continued)
TLV or Organization
Type Field
9 to 30
Organization-Specific TLV
31
32 to 63
64 to 255
End TLV
Sender ID TLV
Organization-Specific TLV
End TLV
Sender ID TLV
Data TLV
Organization-Specific TLV
End TLV
Sender ID TLV
Data TLV
Organization-Specific TLV
555
End TLV
Sender ID TLV
Organization-Specific TLV
End TLV
Sender ID TLV
Organization-Specific TLV
The following TLVs are currently supported in the applicable CFM PDUs:
End TLV
Data TLV
MX Series routers support configuration of port status TLV and interface status TLV.
Configuring the Port Status TLV allows the operator to control the transmission of the
Port Status TLV in CFM PDUs.
NOTE: Although Port Status TLV configuration statements are visible in the
CLI on M120 and M320 routers, Port Status TLV cannot be configured on
these systems. Port Status TLV can be enabled on a MEP interface only if it
is a bridge logical interface, which is not possible on these systems.
556
Octet (Sequence)
Type = 2
Length
23
Value
psBlocked
psUp
The bridge port is set in a state where the traffic can pass through it.
557
NOTE: Port Status TLV configuration is not mandated by IEEE 802.1ag. The
Junos OS 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.
You cannot enable Port Status TLV transmission in the following two cases:
558
Interface: ge-2/0/0.0
Last flapped: Never
Remote defect indication: false
Port status TLV: none # RX PORT STATUS
Interface status TLV: none
Octet (Sequence)
Type = 4
Length
23
Interface Status
Value
isUp
up
559
Interface Status
Value
isDown
down
isTesting
testing
isUnknown
unknown
isDormant
dormant
isNotPresent
notPresent
isLowerLayerDown
lowerLayerDown
NOTE: When the operational status of a logical interface changes from the
down state (status value of 2) to the lower layer down state (status value
of 7) and vice versa, the LinkDown SNMP trap is not generated. For example,
if you configure an aggregated Ethernet interface bundle with a VLAN tag
and add a physical interface that is in the operationally down state to the
bundle, the operational status of the aggregated Ethernet logical interface
bundle at that point is lower layer down (7). If you take the MIC associated
with the interface offline, the LinkDown trap is not generated when the logical
interface shifts from the lower layer down state to the down state.
Similarly, consider another sample scenario in which an physical interface is
added to an aggregated Ethernet bundle that has VLAN tagging and the
aggregated Ethernet logical interface is disabled. When the logical interface
is disabled, the operational status of the logical interface changes to down.
If you disable the physical interface that is part of the aggregated Ethernet
bundle, the operational status of the aggregated Ethernet logical interface
remains down. If you reenable the aggregated Ethernet logical interface, the
operational status of it changes from down to lower layer down. The LinkDown
SNMP trap is not generated at this point.
560
NOTE: The Junos OS 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 OS is capable of receiving any value for the Interface
Status TLV.
561
562
: no
: no
: yes # MAC Status Defects yes/no
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
1658
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Interface
xe-5/0/0.0
563
DMRs sent
Valid DMRs received
Invalid DMRs received
Remote MEP count: 1
Identifier
MAC address
200
00:05:85:73:39:4a
: 0
: 0
: 0
State
ok
Interface
xe-5/0/0.0
564
Related
Documentation
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
565
566
MX-P
A-x200
A-x200
MX-PE
E-Domain
MX-PE
A-4100
A-x100
MPLS Core
MX-PE
MX-PE
A-x100
A-Domain
A-4100
A-x100
A-x100
g017521
A-x200
MX-P
Customer
Site
Customer
Site
HELLO PDU
Customer
Site
IWF
Figure 35 on page 567 describes the dual homed topology on MX Series PE routers
connected to the A-domain. When an A-domain device triggers a switchover, it starts
switching the service traffic to the new active path. This change is communicated in the
HELLO protocol data units (PDUs) sent by that A-domain device on the working and
protection paths. When the IWF in A4100 recieves these HELLO PDUs, it converts them
to standard CCM messages and also inserts a connection protection TLV. The
Protection-in-use field of the connection protection TLV is encoded with the currently
active path, and is included in the CCM message. CCM messages are received by the MX
Series PE routers through the VLAN spoke in A4100. In the above dual homed scenario,
one MX Series PE router monitors the working path, and the other MX Series PE router
monitors the protection path.
A MAC flush occurs when the CFM session that is monitoring the working path detects
that the service traffic has moved to the protection path or when the CFM session that
is monitoring the protection path detects that the service traffic has moved to the working
path.
567
MX-P
A-x200
A-x200
MX-PE
E-Domain
MX-PE
A-4100
A-x100
MPLS Core
MX-PE
A-x100
A-Domain
A-4100
A-x100
A-x100
g017522
A-x200
MX-P
Customer
Site
Customer
Site
Customer
Site
Figure 36 on page 568 describes the dual attached topology on MX Series PE routers
connected to the A-domain. The MAC flush mechanism used in this case is also the same
as the one used for the A-domain in the dual homed scenario (Figure 1). However in this
case both the CFM sessions are hosted by only one MX Series PE router. When Ax100 in
the A-domain detects topology changes, the MX Series PE router receives the connection
protection TLV in the CCM message for the working and protection paths with the value
of Protection-in-use indicating which path is the active one. Based upon the event that
is generated for the CFM session, the MX Series PE router will bring down the appropriate
interface which will trigger a local MAC flush.
Related
Documentation
568
connection-protection-tlv
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
Requirements
This example uses the following hardware and software components:
A MX series PE router
569
MX-P
A-x200
A-x200
MX-P
MX-PE
MX-PE
E-Domain
A-4100
A-x100
MPLS Core
MX-PE
MX-PE
A-x100
A-Domain
A-4100
A-x100
A-x100
g017521
A-x200
Customer
Site
Customer
Site
HELLO PDU
Customer
Site
IWF
The following definitions describe the meaning of the device abbreviation and terms
used in Figure 37 on page 570.
Provider edge (PE) deviceA device, or set of devices, at the edge of the provider
network that presents the provider's view of the customer site.
E-domainNokia Siemens Networks Carrier Ethernet Switches that run standard based
protocols and are used in the access side.
Configuration
Step-by-Step
Procedure
To configure an action profile based on the connection protection TLV, preform these
tasks:
1.
2.
3.
4.
570
interface-down;
}
}
Results
Related
Documentation
connection-protection-tlv
IEEE 802.1ag CFM OAM Support for CCC Encapsulated Packets Overview on page 571
IEEE 802.1ag CFM OAM Support for CCC Encapsulated Packets Overview
Layer 2 virtual private network (L2VPN) is a type of virtual private network service used
to transport customer's private Layer 2 traffic (for example, Ethernet, ATM or Frame
Relay) over the service provider's shared IP/MPLS infrastructure. The service provider
edge (PE) router must have an interface with circuit cross-connect (CCC) encapsulation
to switch the customer edge (CE) traffic to the public network.
The IEEE 802.1ag Ethernet Connectivity Fault Management (CFM) is an OAM standard
used to perform fault detection, isolation, and verification on virtual bridge LANs. M120
and MX Series routers provide CFM support for bridge/VPLS/routed interfaces and
support 802.1ag Ethernet OAM for CCC encapsulated packets.
571
Support for action profiles to bring the CE-facing logical interfaces down when loss of
connectivity is detected.
CE1
ge-1/1/1
Down MEP
Up MEP
PE1
Down MEP
ge-2/2/0
Level 0
pseudowire
ge-0/0/0
ge-2/0/0
PE2
Up MEP
Down MEP
ge-0/0/0
ge-1/0/1
CE2
Down MEP
g017327
Level 0
To monitor the L2VPN circuit, a CFM up MEP (Level 6 in Figure 38 on page 572) 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 38 on page 572).
Related
Documentation
572
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Global-level CFM policinguses a policer at the global level to police the CFM traffic
belonging to all the sessions.
Session-level CFM policinguses a policer created to police the CFM traffic belonging
to one session.
To configure global-level CFM policing, include the policer statement and its options at
the [edit protocols oam ethernet connectivity-fault-management] hierarchy level.
To configure session-level CFM policing, include the policer statement at the [edit
protocols oam ethernet connectivity-fault-management maintenance-domain md-name
level number maintenance-association ma-name] hierarchy level.
The following example shows a CFM policer used for rate-limiting CFM:
[edit]
firewall {
policer cfm-policer {
if-exceeding {
bandwidth-limit 8k;
burst-size-limit 2k;
}
then discard;
573
}
}
Case 1: Global-Level
CFM Policing
This example shows a global level policer, at the CFM level, for rate-limiting CFM. The
continuity-check cfm-policer statement at the global [edit protocols oam ethernet
connectivity-fault-management policer] hierarchy level specifies the policer to use for
policing all continuity check packets of the CFM traffic belonging to all sessions. The
other cfm-policer1 statement at the [edit protocols oam ethernet
connectivity-fault-management policer] hierarchy level specifies the policer to use for
policing all non-continuity check packets of the CFM traffic belonging to all sessions. The
all cfm-policer2 statement specifies to police all CFM packets with the specified policer
cfm-policer2. If the all policer-name option is used, then the user cannot specify the
previous continuity-check and other options.
[edit protocols oam ethernet]
connectivity-fault-management {
policer {
continuity-check cfm-policer;
other cfm-policer1 ;
all cfm-policer2;
}
}
Case 2: Session-Level
CFM Policing
This example shows a session-level CFM policer used for rate-limiting CFM. The policer
statement at the session [edit protocols oam ethernet connectivity-fault-management
maintenance-domain md-name maintenance-association ma-name] hierarchy level
specifies the policer to use for policing only continuity check packets of the CFM traffic
belonging to the specified session. The other cfm-policer1 statement at the [edit protocols
oam ethernet connectivity-fault-management maintenance-domain md-name
maintenance-association ma-name] hierarchy level specifies the policer to use for policing
all non-continuity check packets of the CFM traffic belonging to this session only. The
all cfm-policer2 statement specifies to police all CFM packets with the specified policer
cfm-policer2. If the all policer-name option is used, then the user cannot specify the
previous continuity-check and other options.
[edit protocols oam ethernet]
connectivity-fault-management {
maintenance-domain md {
level number;
maintenance-association ma {
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;
}
}
}
574
In the case of global CFM policing, the same policer is shared across multiple CFM sessions.
In per-session CFM policing, a separate policer must be created to rate-limit packets
specific to that session.
NOTE:
Service-level policer configuration for any two CFM sessions on the same
interface at different levels must satisfy the following constraints if the
direction of the sessions is the same:
If one session is configured with policer all, then the other session cannot
have a policer all or policer other configuration.
If one session is configured with policer other, then the other session cannot
have a policer all or policer other configuration.
Related
Documentation
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Configuring Port Status TLV and Interface Status TLV on page 554
Configuring M120 and MX Series Routers for CCC Encapsulated Packets on page 571
575
The Junos OS provides support for unified ISSU using the loss threshold type length value
(TLV), which is automatically enabled for CFM. TLVs are described in the IEEE 802.1ag
standard for CFM as a method of encoding variable-length and optional information in
a protocol data unit (PDU). The loss threshold TLV indicates the loss threshold value of
a remote MEP. The loss threshold TLV is transmitted as part of the CFM continuity check
messages.
NOTE: Configuring ISSU with CFM (802.1ag) is supported only between two
MX routers that support TLV. Interoperation with other vendors is not
supported.
During a unified ISSU, the control plane may go down for several seconds and cause CFM
continuity check packets to get dropped. This may cause the remote MEP to detect a
connectivity loss and mark the MEP as down. To keep the MEP active during a unified
ISSU, the loss threshold TLV communicates the minimum threshold value the receiving
MEP requires to keep the MEP active. The receiving MEP parses the TLV and updates the
loss threshold value, but only if the new threshold value is greater than the locally
configured threshold value.
An overview of CFM is described starting in IEEE 802.1ag OAM Connectivity Fault
Management Overview on page 525, and you should further observe the additional
requirements described in this topic.
Table 56 on page 576 shows the Loss Threshold TLV format.
Octet (sequence)
Description
Type=31
Length=12
Required if the Type field is not 0. Not present if the Type field is 0. The
16 bits of the Length field indicate the size, in octets, of the Value field. 0
in the Length field indicates that there is no Value field.
OUI
Subtype
Value
Flag
576
PDUs. The convey-loss-threshold statement specifies that the loss threshold TLV must
be transmitted as part of the continuity check messages. If the convey-loss-threshold
statement is not specified, continuity check messages transmit this TLV only when a
unified ISSU is in progress. The Junos OS provides this configuration at the
continuity-check level. By default, continuity check messages do not include the loss
threshold TLV.
To configure the convey loss threshold, use the convey-loss-threshold statement at the
[edit protocols oam ethernet connectivity-fault-management maintenance-domain identifier
maintenance-association identifier continuity-check] hierarchy level.
For the remote MEP, the loss threshold TLV is transmitted only during the unified ISSU
if the convey-loss-threshold statement is not configured. The remote MEP switches back
to the default loss threshold if no loss threshold TLV is received or the TLV has a default
threshold value of 3.
An example of the ISSU configuration statements follows:
protocols {
oam {
ethernet {
connectivity-fault-management {
maintenance-domain identifier {
level number;
maintenance-association identifier {
continuity-check {
convey-loss-threshold;
interval number;
loss-threshold number;
hold-interval number;
}
}
}
}
}
}
}
The Junos OS saves the last received loss threshold TLV from the remote MEP. You can
display the last saved loss threshold TLV that is received by the remote MEP, using the
show oam ethernet connectivity-fault-management mep-database maintenance-domain
identifier maintenance-association identifier local-mep identifier remote-mep identifier
577
Loss Threshold: 3
, Flag:
0x0
The Junos OS saves the last transmitted loss threshold TLV from a local MEP. You can
display the last transmitted loss threshold TLV and the effective loss (operational)
threshold for the remote MEP, using the show oam ethernet connectivity-fault-management
mep-database maintenance-domain identifier maintenance-association identifier local-mep
identifier remote-mep identifier command, as in the following example:
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain md3 maintenance-association ma5 local-mep 2 remote-mep 1
Maintenance domain name: md3, Format: string, Level: 3
Maintenance association name: ma3, Format: string
Continuity-check status: enabled, Interval: 1s, Loss-threshold: 3 frames
MEP identifier: 2, Direction: up, MAC address: 00:19:e2:b0:76:be
Auto-discovery: enabled, Priority: 0
Interface status TLV: none, Port status TLV: none
Connection Protection TLV: yes
Prefer me: no, Protection in use: no, FRR Flag: no
Interface name: xe-4/1/1.0, Interface status: Active, Link status: Up
Loss Threshold TLV:
#Displays last transmitted value
Loss Threshold: 3 , Flag:
0x0
Remote MEP identifier: 1, State: ok
MAC address: 00:1f:12:b7:ce:79, Type: Learned
Interface: xe-4/1/1.0
Last flapped: Never
Continuity: 100%, Admin-enable duration: 45sec, Oper-down duration: 0sec
Effective loss threshold: 3 frames
#Displays operational threshold
Remote defect indication: falsePort status TLV: none
Interface status TLV: none
Connection Protection TLV:
Prefer me: no, Protection in use: no, FRR Flag: no
Loss Threshold TLV:
Loss Threshold: 3 , Flag:
0x0
Related
Documentation
578
failures in Ethernet domains for Carrier Ethernet services. These enhancements can be
used when CE devices in the Ethernet domain detect faster service failures and propagates
the information in the interface-status TLV of the continuity-check messages (CCMs).
When CCMs are received, PE devices can perform certain actions which facilitates faster
protection-switching and convergence.
To configure CCM for better scalability:
Related
Documentation
You can apply an action profile to provide faster protection switching for point-to-point
network topologies with local switching configured. See Configuring Faster Protection
Switching for Point-to-Point Network Topologies on page 579.
You can apply an action profile to provide faster convergence for dual-homed
multipoint-to-multipoint network topologies. See Configuring Faster Convergence
for Dual-Homed Multipoint-to-Multipoint Network Topologies on page 581.
You can assign a primary virtual LAN (VLAN) ID in the maintenance association for
increased flexibility in the number of tags. See Configuring a Primary VLAN ID for
Increased Flexibility on page 582.
579
In this action profile configuration, when the interface-status TLV is received as up, the
peer-interface is marked as down.
The peer-interface is configured in the protect-maintenance-association statement.
Consider the following example using the protect-maintenance-association statement
in the configuration:
[edit protocols oam]
ethernet {
connectivity-fault-management {
action-profile p1 {
event {
adjacency-loss;
}
action {
interface-down;
}
clear-action {
interface-down peer-interface;
}
}
maintenance-domain nsn {
level 5;
maintenance-association ma1 {
protect-maintenance-association ma2;
continuity-check {
interval 100ms;
connection-protection-tlv;
}
mep 100 {
580
interface ge-1/1/0.0;
direction down;
auto-discovery;
}
}
maintenance-association ma2 {
continuity-check {
interval 100ms;
connection-protection-tlv;
}
mep 101 {
interface ge-1/2/0.0;
direction down;
auto-discovery;
}
remote-mep 100
action-profile p1;
}
}
}
}
Related
Documentation
581
In this action profile configuration, when the incoming CCM packet contains the
interface-status TLV with value down, the propagate-remote-mac-flush action is triggered
for the action-profile.
Related
Documentation
582
auto-discovery;
}
}
}
Related
Documentation
connection-protection-tlv
Using this configuration, interoperability is improved for CCMs with low-end CE devices
supporting fixed maintenance association identifier configurations.
Related
Documentation
583
connection-protection-tlv
Requirements
This example uses the following hardware and software components:
Overview
CFM can be used to monitor the physical link between two routers. This functionality is
similar to that supported by the IEEE 802.3ah LFM protocol.
In Junos OS Release 9.3 and later, CFM also supports aggregated Ethernet interfaces.
On interfaces configured on Modular Port Concentrators (MPCs) and Modular Interface
Cards (MICs) on MX Series routers, CFM is not supported on untagged aggregated Ethernet
member links. MPCs and MICs do support CFM on untagged and tagged aggregated
Ethernet logical interfaces.
Configuration
In the following example, two routers (Router 1 and Router 2) are connected by a
point-to-point Gigabit Ethernet link. The link between these two routers is monitored
using CFM. This is shown in Figure 39 on page 584. The single boundary is a down mep
in CFM terminology.
584
CLI
Router
Quick1
Configuration
The configuration on Router 2 mirrors that on Router 1, with the exception of the mep-id.
Router 2
585
}
}
}
}
}
}
}
To verify that the physical interface is configured correctly for CFM, use the show interface
command. To verify the CFM configuration, use one or more of the show oam ethernet
connectivity-fault-management commands listed in the CLI Explorer.
Related
Documentation
The service provider is using CFM level 3 for the link between PE1 and PE2 and level 5
from one CE facing port to the other. The customer is using CFM level 7. The boundaries
are marked with up mep and down mep CFM terminology in the figure.
586
CFM on L2-CE1
[edit interfaces]
ge-0/2/9 {
vlan-tagging;
unit 0 {
vlan-id 2000;
}
}
[edit protocols oam ethernet]
connectivity-fault-management {
maintenance-domain customer {
level 7;
maintenance-association customer-site1 {
continuity-check {
interval 1s;
}
mep 700 {
interface ge-0/2/9.0;
direction down;
auto-discovery;
}
}
}
}
CFM on L2-CE2
[edit interfaces]
ge-1/0/7 {
vlan-tagging;
unit 0 {
vlan-id 2000;
}
}
[edit protocols oam ethernet]
connectivity-fault-management {
maintenance-domain customer {
level 7;
maintenance-association customer-site2 {
continuity-check {
interval 1s;
}
mep 800 {
interface ge-1/0/7.0;
direction down;
auto-discovery;
}
}
}
}
[edit interfaces]
ge-5/0/9 {
vlan-tagging;
587
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 2000;
}
}
ge-5/1/7 {
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 2000;
}
}
[edit bridge-domains]
bridge-vlan2000 {
domain-type bridge;
vlan-id 2000;
interface ge-5/0/9.0;
interface ge-5/1/7.0;
}
[edit protocols oam ethernet connectivity-fault-management]
maintenance-domain provider-outer {
level 5;
maintenance-association provider-outer-site1 {
continuity-check {
interval 1s;
}
mep 200 {
interface ge-5/0/9.0;
direction up;
auto-discovery;
}
}
}
maintenance-domain provider-inner {
level 3;
maintenance-association provider-inner-site1 {
continuity-check {
interval 1s;
}
mep 200 {
interface ge-5/1/7.0;
direction down;
auto-discovery;
}
}
}
CFM on PE2
588
[edit interfaces]
ge-5/1/7 {
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 2000;
}
}
ge-5/2/3 {
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 0 {
encapsulation vlan-bridge;
vlan-id 2000;
}
}
[edit bridge-domains]
bridge-vlan2000 {
domain-type bridge;
interface ge-5/2/3.0;
interface ge-5/1/7.0;
}
[edit protocols oam ethernet connectivity-fault-management]
maintenance-domain provider-outer {
level 5;
maintenance-association provider-outer-site1 {
continuity-check {
interval 1s;
}
mep 100 {
interface ge-5/2/3.0;
direction up;
auto-discovery;
}
}
}
maintenance-domain provider-inner {
level 3;
maintenance-association provider-inner-site1 {
continuity-check {
interval 1s;
}
mep 100 {
interface ge-5/1/7.0;
direction down;
auto-discovery;
}
}
}
Related
Documentation
589
The service provider is using CFM level 5 and the customer is using CFM level 7. The
boundaries are marked with up mep and down mep CFM terminology in the figure.
NOTE: The logical interfaces in a VPLS routing instance might have the same
or different VLAN configurations. VLAN normalization is required to switch
packets correctly among these interfaces. Normalization supports automatic
mapping of VLANs and performs operations on VLAN tags to achieve the
desired translation. See Configuring a Normalized VLAN for Translation or
Tagging.
590
NOTE:
The following forwarding path considerations must be observed:
802.1ag Ethernet OAM for VPLS uses implicit interface filters and
forwarding table filters to flood, accept, and drop the CFM packets.
For down MEPs, the packets are transmitted on the interface on which
the MEP is configured.
The following are the configurations of the VPLS and CFM on the service provider routers.
Configuration of PE1
[edit chassis]
fpc 5 {
pic 0 {
tunnel-services {
bandwidth 1g;
}
}
}
[edit interfaces]
ge-1/0/7 {
encapsulation flexible-ethernet-services;
vlan-tagging;
unit 1 {
encapsulation vlan-vpls;
vlan-id 2000;
}
}
ge-0/0/0 {
unit 0 {
family inet {
address 10.200.1.1/24;
}
family mpls;
}
}
lo0 {
unit 0 {
591
family inet {
address 10.255.168.231/32 {
primary;
}
address 127.0.0.1/32;
}
}
}
[edit routing-instances]
vpls-vlan2000 {
instance-type vpls;
vlan-id 2000;
interface ge-1/0/7.1;
route-distinguisher 10.255.168.231:2000;
vrf-target target:1000:1;
protocols {
vpls {
site-range 10;
site vlan2000-PE1 {
site-identifier 2;
}
}
}
}
[edit protocols]
rsvp {
interface ge-0/0/0.0;
}
mpls {
label-switched-path PE1-to-PE2 {
to 10.100.1.1;
}
interface ge-0/0/0.0;
}
bgp {
group PE1-to-PE2 {
type internal;
local-address 10.200.1.1;
family l2vpn {
signaling;
}
local-as 65000;
neighbor 10.100.1.1;
}
}
ospf {
traffic-engineering;
reference-bandwidth 4g;
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
592
interface ge-0/0/0.0;
}
}
oam {
ethernet {
connectivity-fault-management {
maintenance-domain customer-site1 {
level 5;
maintenance-association customer-site1 {
continuity-check {
interval 1s;
}
mep 100 {
interface ge-1/0/7.1;
direction up;
auto-discovery;
}
}
}
}
}
}
Configuration of PE2
[edit chassis]
fpc 5 {
pic 0 {
tunnel-services {
bandwidth 1g;
}
}
}
[edit interfaces]
ge-5/0/9 {
vlan-tagging;
encapsulation flexible-ethernet-services;
unit 1 {
encapsulation vlan-vpls;
vlan-id 2000;
}
}
ge-5/2/7 {
unit 0 {
family inet {
address 10.100.1.1/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.168.230/32 {
primary;
}
593
address 127.0.0.1/32;
}
}
}
[edit routing-instances]
vpls-vlan2000 {
instance-type vpls;
vlan-id 2000;
interface ge-5/0/9.1;
route-distinguisher 10.255.168.230:2000;
vrf-target target:1000:1;
protocols {
vpls {
site-range 10;
site vlan2000-PE2 {
site-identifier 1;
}
}
}
}
[edit protocols]
rsvp {
interface ge-5/2/7.0;
}
mpls {
label-switched-path PE2-to-PE1 {
to 10.200.1.1;
}
interface ge-5/2/7.0;
}
bgp {
group PE2-to-PE1 {
type internal;
local-address 10.100.1.1;
family l2vpn {
signaling;
}
local-as 65000;
neighbor 10.200.1.1;
}
}
ospf {
traffic-engineering;
reference-bandwidth 4g;
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
interface ge-5/2/7.0;
}
}
oam {
594
ethernet {
connectivity-fault-management {
maintenance-domain customer-site1 {
level 5;
maintenance-association customer-site1 {
continuity-check {
interval 1s;
}
mep 200 {
interface ge-5/0/9.1;
direction up;
auto-discovery;
}
}
}
}
}
}
Configuration of P
router
595
}
mpls {
interface ge-0/1/0.0;
interface ge-5/2/7.0;
}
ospf {
traffic-engineering;
reference-bandwidth 4g;
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
interface ge-0/1/0.0;
interface ge-5/2/7.0;
}
}
}
CFM on L2-CE1
CFM on L2-CE2
596
}
}
[edit protocols oam]
ethernet {
connectivity-fault-management {
maintenance-domain customer {
level 7;
maintenance-association customer-site1 {
continuity-check {
interval 1s;
}
mep 700 {
interface ge-0/2/9.0;
direction down;
auto-discovery;
}
}
}
}
}
Related
Documentation
597
598
CHAPTER 32
Configuring Ethernet 802.3ah OAM on PTX Series Packet Transport Routers on page 602
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
599
Discovery
Link monitoring
Remote loopback
Ethernet running on top of a Layer 2 protocol, such as Ethernet over ATM, is not
supported in OAM configurations.
Remote loopback is not supported on the 10-Gigabit Ethernet LAN/WAN PIC with
SFP+.
The remote loopback feature mentioned in section 57.2.11 of IEEE 802.3ah is not
supported on T4000 routers.
NOTE: Aggregated Ethernet member links will now use the physical MAC
address as the source MAC address in 802.3ah OAM packets.
Related
Documentation
600
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
Configuring Threshold Values for Local Fault Events on an Interface on page 606
601
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
To configure 802.3ah OAM support for Ethernet interfaces, include the oam statement
at the [edit protocols] hierarchy level:
oam {
ethernet {
link-fault-management {
interfaces {
602
interface-name {
pdu-interval interval;
link-discovery (active | passive);
pdu-threshold count;
}
}
}
}
}
Related
Documentation
When you enable IEEE 802.3ah OAM on a physical interface, the discovery process is
automatically triggered.
Related
Documentation
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
603
In active mode, the interface discovers and monitors the peer on the link if the peer also
supports IEEE 802.3ah OAM functionality. In passive mode, the peer initiates the discovery
process. After the discovery process has been initiated, both sides participate in discovery.
Related
Documentation
604
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
The periodic OAM PDU interval range is from 100 through 1000 milliseconds. The default
sending interval is 1000 milliseconds.
Related
Documentation
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
605
The threshold value range is from 3 through 10. The default is three PDUs.
Related
Documentation
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
606
To set the error threshold values for sending event TLVs, include the frame-error,
frame-period, frame-period-summary, and symbol-period statements at the [edit protocols
oam ethernet link-fault-management interface interface-name event-thresholds] hierarchy
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;
}
Related
Documentation
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
607
Related
Documentation
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
608
Critical Event
Dying Gasp
Link Fault
The link event TLVs are sent by the remote DTE by means of event notification PDUs.
Link event TLVs are:
Related
Documentation
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
609
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;
}
}
Related
Documentation
610
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
To create a system log entry when the link-fault event occurs, include the syslog
statement.
To administratively disable the link when the link-fault event occurs, include the link-down
statement.
To send IEEE 802.3ah link event TLVs in the OAM PDU when a link-fault event occurs,
include the send-critical-event statement.
NOTE: If multiple actions are specified in the action profile, all of the actions
are executed in no particular order.
Related
Documentation
611
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Configuring Threshold Values for Fault Events in an Action Profile on page 614
Related
Documentation
612
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
NOTE: If multiple events are specified in the action profile, all the events
must occur before the specified action is taken.
Related
Documentation
613
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
Related
Documentation
614
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Related
Documentation
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
615
Configuring Threshold Values for Fault Events in an Action Profile on page 614
Junos OS can place a remote DTE into loopback mode (if remote-loopback mode is
supported by the remote DTE). When you place a remote DTE into loopback mode, the
interface receives the remote-loopback request and puts the interface into
remote-loopback mode. When the interface is in remote-loopback mode, all frames
except OAM PDUs are looped back without any changes made to the frames. OAM PDUs
continue to be sent to the management plane and processed.
To configure remote loopback, include the remote-loopback statement at the [edit
protocol oam ethernet link-fault-management interface interface-name] hierarchy level:
[edit protocol oam ethernet link-fault-management interface interface-name]
remote-loopback;
To take the remote DTE out of loopback mode, remove the remote-loopback statement
from the configuration.
Related
Documentation
616
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
hierarchy level:
[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.
Related
Documentation
Configuring Threshold Values for Local Fault Events on an Interface on page 606
617
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
Related
Documentation
618
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
Configuring Threshold Values for Fault Events in an Action Profile on page 614
Example: Configuring Ethernet LFM Between Provider Edge and Customer Edge
In this example, LFM is enabled on an IP link between the provider edge (PE) and customer
edge (CE) interfaces. If the link goes down, the fault will be detected by LFM and the
interfaces on both sides will be marked Link-Layer-Down. This results in notifications to
various subsystems (for example, routing) which will take appropriate action.
The link running LFM is shown in Figure 42 on page 619.
Figure 42: Ethernet LFM Between Provider Edge and Customer Edge
619
ethernet {
link-fault-management {
interface ge-1/1/0 {
pdu-interval 1000;
pdu-threshold 5;
}
}
}
}
}
2. Configure LFM on the CE router:
[edit]
interfaces ge-1/1/0 {
unit 0 {
family inet {
address 11.11.11.2/24;
}
}
}
protocols {
oam {
ethernet {
link-fault-management {
interface ge-1/1/0 {
pdu-interval 1000;
pdu-threshold 5;
}
}
}
}
}
Related
Documentation
620
[edit]
interfaces ge-1/0/0 {
encapsulation ethernet-ccc;
unit 0;
}
protocols {
oam {
ethernet {
link-fault-management {
interface ge-1/0/0 {
pdu-interval 1000;
pdu-threshold 5;
}
}
}
}
}
Related
Documentation
Example: Configuring Ethernet LFM Between Provider Edge and Customer Edge on
page 619
621
622
ethernet {
link-fault-management {
interface ae0;
}
}
}
}
2. Configure LFM on Router 2 for AE0:
[edit]
chassis {
aggregated-devices {
ethernet {
device-count 1;
}
}
}
interfaces ge-1/0/0 {
gigether-options {
802.3ad ae0;
}
}
interfaces ge-5/0/0 {
gigether-options {
802.3ad ae0;
}
}
interfaces ae0 {
unit 0 {
family inet {
address 11.11.11.1/24;
}
}
}
protocols {
oam {
ethernet {
link-fault-management {
interface ae0;
}
}
}
}
Related
Documentation
Example: Configuring Ethernet LFM Between Provider Edge and Customer Edge on
page 619
623
[edit]
interfaces ge-1/1/0 {
unit 0 {
family inet {
address 11.11.11.2/24;
}
}
}
protocols {
oam {
ethernet {
624
link-fault-management {
interface ge-1/1/0 {
pdu-interval 1000;
pdu-threshold 5;
negotiation-options {
allow-remote-loopback;
}
}
}
}
}
}
Related
Documentation
Example: Configuring Ethernet LFM Between Provider Edge and Customer Edge on
page 619
625
626
CHAPTER 33
Configuring Statistical Frame Loss Measurement for VPLS Connections on page 669
Guidelines for Managing ETH-DM Statistics and ETH-DM Frame Counts on page 673
627
Displaying ETH-DM Frame Counts for MEPs by Enclosing CFM Entity on page 688
Displaying ETH-DM Frame Counts for MEPs by Interface or Domain Level on page 689
Example: Measuring Ethernet Frame Loss for Single-Tagged LMM/LMR PDUs on page 716
Example: Measuring Ethernet Frame Loss for Dual-Tagged LMM/LMR PDUs on page 727
628
Junos OS supports key OAM standards that provide for automated end-to-end
management and monitoring of Ethernet service by service providers:
ITU-T Recommendation Y.1731, which uses different terminology than IEEE 802.1ag and
defines Ethernet service OAM features for fault monitoring, diagnostics, and
performance monitoring.
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.
For Ethernet interfaces on M320, MX Series, and T Series routers, Junos OS supports the
following key elements of the Ethernet CFM standard:
Fault monitoring using the IEEE 802.1ag Ethernet OAM Continuity Check protocol
Path discovery and fault verification using the IEEE 802.1ag Ethernet OAM Linktrace
protocol
Fault isolation using the IEEE 802.1ag Ethernet OAM Loopback protocol
In a CFM environment, network entities such as network operators, service providers, and
customers may be part of different administrative domains. Each administrative domain
is mapped into one maintenance domain. Maintenance domains are configured with
different level values to keep them separate. Each domain provides enough information
for the entities to perform their own management and end-to-end monitoring, and still
avoid security breaches.
Figure 46 on page 630 shows the relationships among the customer, provider, and operator
Ethernet bridges, maintenance domains, maintenance association end points (MEPs),
and maintenance intermediate points (MIPs).
629
NOTE: Maintenance intermediate points (MIP) are not supported on the ACX
Series routers.
630
1DM Transmission
When you start a one-way frame delay measurement, the router sends 1DM
framesframes that carry the protocol data unit (PDU) for a one-way delay
measurementfrom the initiator MEP to the receiver MEP at the rate and for the number
of frames you specify. The router marks each 1DM frame as drop-ineligible and inserts a
timestamp of the transmission time into the frame.
1DM Reception
When an MEP receives a 1DM frame, the router that contains the receiver MEP measures
the one-way delay for that frame (the difference between the time the frame was received
and the timestamp contained in the frame itself) and the delay variation (the difference
between the current and previous delay values).
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.
Each router stores ETH-DM frame counts in the CFM database. The CFM database stores
CFM session statistics and, for interfaces that support ETH-DM, any ETH-DM frame
counts. You can access the frame counts at any time by displaying CFM database
information for Ethernet interfaces assigned to MEPs or for MEPs in CFM sessions.
NOTE: For a given one-way Ethernet frame delay measurement, frame delay
and frame delay variation values are available only on the router that contains
the receiver MEP.
631
DMM Transmission
When you start a two-way frame delay measurement, the router sends delay
measurement message (DMM) frames frames that carry the PDU for a two-way
ETH-DM requestfrom the initiator MEP to the responder MEP at the rate and for the
number of frames you specify. The router marks each DMM frame as drop-ineligible and
inserts a timestamp of the transmission time into the frame.
DMR Transmission
When an MEP receives a DMM frame, the responder MEP responds with a delay
measurement reply (DMR) frame, which carries ETH-DM reply information and a copy
of the timestamp contained in the DMM frame.
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:
1.
TI
TxDMM
2. TR
RxDMM
3. TR
TxDMR
4. TI
RxDMR
RxDMR
TI
] [TR
TxDMM
TxDMR
TR
RxDMM
The calculation show that frame delay is the difference between the time at which the
initiator MEP sends a DMM frame and the time at which the initiator MEP receives the
associated DMR frame from the responder MEP, minus the time elapsed at the responder
MEP.
The delay variation is the difference between the current and previous delay values.
632
For an initiator MEP, the router counts the number DMM frames transmitted, the number
of valid DMR frames received, and the number of invalid DMR frames received.
For a responder MEP, the router counts the number of DMR frames sent.
Each router stores ETH-DM frame counts in the CFM database. The CFM database stores
CFM session statistics and, for interfaces that support ETH-DM, any ETH-DM frame
counts. You can access the frame counts at any time by displaying CFM 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.
Ethernet frame delay measurements can be triggered only when the distributed periodic
packet management daemon (ppm) is enabled. For more information about this
limitation, see Guidelines for Configuring Routers to Support an ETH-DM Session on
page 670 and Ensuring That Distributed ppm Is Not Disabled on page 679.
You can monitor only one session at a time to the same remote MEP or MAC address.
For more information about starting an ETH-DM session, see Starting an ETH-DM
Session on page 681.
633
Related
Documentation
ETH-DM statistics are collected at only one of the two peer routers in the ETH-DM
session. For a one-way ETH-DM session, you can display frame ETH-DM statistics at
the receiver MEP only, using ETH-DM-specific show commands. For a two-way ETH-DM
session, you can display frame delay statistics at the initiator MEP only, using the same
ETH-DM-specific show commands. For more information, see Managing ETH-DM
Statistics and ETH-DM Frame Counts on page 685.
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. Therefore, the collection of
ETH-DM statistics and ETH-DM frame counters has to be restarted, after the switchover
is complete. 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.
For more information, see the Junos OS High Availability Library for Routing Devices.
Accuracy of frame delay statistics is compromised when the system is changing (such
as from reconfiguration). We recommend performing Ethernet frame delay
measurements on a stable system.
Guidelines for Managing ETH-DM Statistics and ETH-DM Frame Counts on page 673
634
from the peer MEP. This type of frame loss measurement is also known as single-ended
Ethernet loss measurement.
ETH-LM supports the following frame loss measurements:
Example: Measuring Ethernet Frame Loss for Dual-Tagged LMM/LMR PDUs on page 727
635
NOTE:
The Ethernet VPN services can be classified into:
For more information about frame delay measurement, see Ethernet Frame Delay
Measurements Overview on page 628. For more information about frame loss
measurement, see Ethernet Frame Loss Measurement Overview on page 634. Note that
Ethernet frame delay measurement and Ethernet frame loss measurement are not
supported on the ae interface.
Related
Documentation
636
637
Enable the deactivate sla-iterator-profile statement at the [edit protocols oam ethernet
connectivity-fault-management maintenance-domain md-name maintenance association
ma-name mep mep-id remote-mep mep-id] hierarchy level. For more information, see
638
Provision a disable statement under the corresponding iterator profile at the [edit
protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name] hierarchy level. For more information, see Configuring
639
640
641
642
Source MEP IDSource MEP ID is a 2-octet field where the last 13 least significant bits
are used to identify the MEP transmitting the SLM frame. MEP ID is unique within the
MEG.
Test IDTest ID is a 4-octet field set by the transmitting MEP and is used to identify a
test when multiple tests run simultaneously between MEPs (including both concurrent
on-demand and proactive tests).
TxFCfTxFCf is a 4-octet field that carries the number of SLM frames transmitted by
the MEP toward its peer MEP.
Version0.
TLV Offset16.
Source MEP IDA 2-octet field used to identify the MEP transmitting the SLM frame.
In this 2-octet field, the last 13 least significant bits are used to identify the MEP
transmitting the SLM frame. MEP ID is unique within the MEG.
Test IDA 4-octet field set by the transmitting MEP and used to identify a test when
multiple tests run simultaneously between MEPs (including both concurrent on-demand
and proactive tests).
TxFCfA 4-octet field that carries the number of SLM frames transmitted by the MEP
toward its peer MEP.
Optional TLVA data TLV may be included in any SLM transmitted. For the purpose
of ETH-SLM, the value part of data TLV is unspecified.
643
MEG LevelA 3-bit field the value of which is copied from the last received SLM PDU.
VersionA 5-bit field the value of which is copied from the last received SLM PDU.
Source MEP IDA 2-octet field copied from the SLM PDU.
Responder MEP IDA 2-octet field used to identify the MEP transmitting the SLR
frame.
TxFCbA 4 octet field. This value represents the number of SLR frames transmitted
for this test ID.
Related
Documentation
644
TypeIdentifies the TLV type; value for this TLV type is Data (3).
LengthIdentifies the size, in octets, of the Value field containing the data pattern.
The maximum value of the Length field is 1440.
Data patternAn n-octet (n denotes length) arbitrary bit pattern. The receiver ignores
it.
TxFClNumber of synthetic frames transmitted toward the peer MEP for a test ID. A
source MEP increments this number for successive transmission of synthetic frames
with ETH-SLM request information while a destination or receiving MEP increments
this value for successive transmission of synthetic frames with the SLR information.
RxFClNumber of synthetic frames received from the peer MEP for a test ID. A source
MEP increments this number for successive reception of synthetic frames with SLR
information while a destination or receiving MEP increments it for successive reception
of synthetic frames with ETH-SLM request information.
The following sections describe the phases of processing of SLM PDUs to determine
synthetic frame loss:
645
All the fields in the SLM PDUs are copied from the SLM request except for the following
fields:
The source MAC address is copied to the destination MAC address and the source
address contains the MEPs MAC address.
The value of the OpCode field is changed from SLM to SLR (54).
TxFCb is saved with the value of the local counter RxFCl at the time of SLR frame
transmission.
An SLR frame is generated every time an SLM frame is received; therefore, RxFCl in
the responder is equal to the number of SLM frames received and also equal to the
number of SLR frames sent. At the responder or receiving MEP, RxFCl equals TxFCl.
Reception of SLRs
After an SLM frame (with a given TxFCf value) is transmitted, a MEP expects to receive
a corresponding SLR frame (carrying the same TxTCf value) within the timeout value
from its peer MEP. SLR frames that are received after the timeout value (5 seconds) are
discarded. With the information contained in SLR frames, a MEP determines the frame
loss for the specified measurement period. The measurement period is a time interval
during which the number of SLM frames transmitted is statistically adequate to make a
measurement at a given accuracy. A MEP uses the following values to determine near-end
and far-end frame loss during the measurement period:
Last received SLR frame's TxFCf and TxFCb values and the local counter RxFCl value
at the end of the measurement period. These values are represented as TxFCf[tc],
TxFCb[tc], and RxFCl[tc], where tc is the end time of the measurement period.
SLR frame's TxFCf and TxFCb values of the first received SLR frame after the test
starts and local counter RxFCl at the beginning of the measurement period. These
values are represented as TxFCf[tp], TxFCb[tp], and RxFCl[tp], where tp is the start
time of the measurement period.
For each SLR packet that is received, the local RxFCl counter is incremented at the sending
or source MEP.
646
The monitoring application for Ethernet OAM is initiated in the master Routing Engine.
When a stateful switchover process occurs, the monitoring application is disabled. For
on-demand ETH-SLM, graceful Routing Engine switchover (GRES) support is not
applicable. For proactive ETH-SLM, the service-level agreement (SLA) iterators are
restored during a stateful switchover process. If the adjacencies do not time out, the
ETH-SLM statistics are preserved and proactive ETH-SLM supports GRES.
ETH-SLM is initiated only when the MEP session is up. Unified in-service software
upgrade (ISSU) support for ETH-SLM depends on the unified ISSU support for CFM.
For CFM, unified ISSU is supported using the loss threshold TLV to avoid CFM
connectivity loss during the upgrade. The receiving or the destination MEP increases
the threshold time during the termination of sessions. If you start a unified ISSU
operation when on-demand ETH-SLM is in progress, the SLM request and reply
messages are lost at the local Packet Forwarding Engine.
When an on-demand ETH-SLM is requested, if the local source MEP undergoes a
unified ISSU, a message is displayed stating that the MEP is undergoing a unified ISSU.
If the remote MEP is undergoing a unified ISSU (detected through the loss threshold
TLV), a message is displayed stating that the remote MEP is undergoing a unified ISSU.
Also, if it is not possible to identify whether unified ISSU is in progress on a remote MEP,
the SLM packets are lost at the system where unified ISSU is in progress and the loss
calculation results do not provide a valid cause for the loss. Unified ISSU is not
supported for both on-demand and proactive ETH-SLM.
The maximum number of SLA iterator profiles that can be configured in the system is
255.
ETH-SLM is not supported for virtual private LAN service (VPLS) (point-to-multipoint
measurements are not supported). The ETH-SLM frames are not generated with
multicast class 1 destination address. Similarly, ETH-SLM does not respond to ETH-SLM
requests with multicast DA. ETH-SLM for VPLS for point-to-point Ethernet connection
is supported using directed unicast destination MAC addresses, although
point-to-multipoint topologies are not supported.
647
of the downstream MEP must have been configured on the MEP transmitting an alarm
indication signal (AIS).
Related
Documentation
The number of ETH-SLM sessions for proactive ETH-SLM that can be supported is
limited to the total number of iterators that can be supported in the system. This
limitation includes the iterator support for other measurement types such as loss,
statistical frame loss, and two-way delay. A new iterator type, SLM, is added to support
ETH-SLM. The total number of SLA iterators that you can configure in the system is
equal to the total number of iterations supported in the system.
For on-demand SLM, the minimum period between two SLM requests is 100
milliseconds.
For proactive SLM, the minimum period between two SLM requests is 10 milliseconds
for distributed mode and 100 milliseconds for non-distributed mode.
ETH-SLM frames are always marked as drop-ineligible in compliance with the ITU-T
Y.1731 standard.
648
Associating the Iterator Profile with MEPs for ETH-SLM on page 651
is typical:
[edit protocols]
oam {
ethernet {
connectivity-fault-management {
maintenance-domain md-name { # On both routers
level number;
maintenance-association ma-name { # On both routers
continuity-check {
interval 100ms;
hold-interval 1;
}
mep mep-id { # Attach to VLAN interface
auto-discovery;
direction (up | down);
interface interface-name;
priority number;
}
}
}
}
}
}
649
between back-to-back transmission of SLA frames for one connection, with a value
from 10 through 3,600,000. The default value is 1000 ms.
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles i1]
user@host# set cycle-time cycle-time-value
5. (Optional) Configure the iteration period, which indicates the maximum number of
cycles per iteration (the number of connections registered to an iterator cannot exceed
this value), with a value from 1 through 2000. The default value is 2000.
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles i1]
user@host# set iteration-period iteration-period-value
6. Configure the measurement type as synthetic loss measurement.
650
measurement-type slm;
this connection should partake in the iterator for acquiring SLA measurements, with
a value from 1 through 65,535. The default value is 0 (that is, infinite iterations).
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id
sla-iterator-profile profile-name]
user@host# set iteration-count count-value
6. (Optional) Set the priority, which is the vlan-pcp value that is sent in the Y.1731 data
651
iteration-count count-value;
priority priority-value;
}
Related
Documentation
Related
Documentation
652
Displaying ETH-SLM Frame Counts for MEPs by Enclosing CFM Entity on page 654
Displaying ETH-SLM Frame Counts for MEPs by Interface or Domain Level on page 655
Action
To display the on-demand ETH-SLM statistics collected for ETH-SLM sessions for the
local MEP 201 belonging to maintenance association ma2 within maintenance
domain md2:
user@host> show oam ethernet connectivity-fault-management synthetic-loss-statistics
maintenance-domain md2 maintenance-association ma2 local-mep 201
To display the on-demand ETH-SLM statistics collected for ETH-SLM sessions from
local MEPs belonging to maintenance association ma3 within maintenance domain md3
to the remote MEP 302:
user@host> show oam ethernet connectivity-fault-management synthetic-loss-statistics
maintenance-domain md3 maintenance-association ma3 remote-mep 302
Meaning
The output displays on-demand ETH-SLM statistics for MEPs in the specified maintenance
association within the specified maintenance domain. For details about the output of
653
this command and the descriptions of the output fields, see show oam ethernet
connectivity-fault-management synthetic-loss-statistics.
Action
To display the on-demand ETH-SLM statistics and ETH-SLM frame counts for MEPs
in maintenance association ma1 within maintenance domain md1:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md1 maintenance-association ma1
To display the on-demand ETH-SLM statistics and ETH-SLM frame counts for the
local MEP 201 in maintenance association ma2 within maintenance domain md2:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md2 maintenance-association ma2 local-mep 201
To display the on-demand ETH-SLM statistics and ETH-SLM frame counts for the
local MEP in maintenance association ma3 within maintenance domain md3 that
participates in an ETH-SLM session with the remote MEP 302:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain ma3 maintenance-association ma3 remote-mep 302
Meaning
The output displays on-demand ETH-SLM statistics and ETH-SLM frame counts for
MEPs in the specified maintenance association within the specified maintenance domain.
For details about the output of this command and the descriptions of the output fields,
see show oam ethernet connectivity-fault-management mep-statistics.
Display on-demand ETH-SLM frame counts for CFM maintenance association end points
(MEPs).
By default, the show oam ethernet connectivity-fault-management mep-database
command displays CFM database information for MEPs in the specified CFM maintenance
association within the specified CFM maintenance domain.
NOTE: At the router attached to the initiator MEP for a one-way session, or
at the router attached to the receiver MEP for a two-way session, you can
only display the ETH-SLM frame counts and not the MEP database details.
Action
654
To display CFM database information (including ETH-SLM frame counts) for all MEPs
in MA ma1 within maintenance domain md1:
To display CFM database information (including ETH-SLM frame counts) only for the
local MEP 201 in MA ma1 within maintenance domain md1:
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-SLM frame counts) only for the
remote MEP 302 in MA ma3 within maintenance domain md3:
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain ma3 maintenance-association ma3 remote-mep 302
Meaning
The output displays ETH-SLM frame counts for MEPs within a particular maintenance
domain, or for a specific local or remote MEP. For details about the output of this
command and the descriptions of the output fields, see show oam ethernet
connectivity-fault-management mep-database.
Display on-demand ETH-SLM frame counts for CFM maintenance association end points
(MEPs).
By default, the show oam ethernet connectivity-fault-management interfaces command
displays CFM database information for MEPs attached to CFM-enabled Ethernet
interfaces on the router or at a maintenance domain level. For Ethernet interfaces that
support ETH-SLM, any frame counts are also displayed when you specify the detail or
extensive command option.
NOTE: At the router attached to the initiator MEP, you can only display the
ETH-SLM frame counts and not the MEP database details.
Action
To display CFM database information (including ETH-SLM frame counts) for all MEPs
attached to CFM-enabled Ethernet interfaces on the router:
user@host> show oam ethernet connectivity-fault-management interfaces detail
To display CFM database information (including ETH-SLM frame counts) only for the
MEPs attached to CFM-enabled router interface ge-5/2/9.0:
user@host> show oam ethernet connectivity-fault-management interfaces ge-5/2/9.0 detail
To display CFM database information (including ETH-SLM frame counts) only for
MEPs enclosed within CFM maintenance domains at level 6:
user@host> show oam ethernet connectivity-fault-management interfaces level 6 detail
Meaning
The output displays ETH-SLM frame counts for MEPs for the specified interface. For
details about the output of this command and the descriptions of the output fields, see
show oam ethernet connectivity-fault-management interfaces.
655
Action
To clear the on-demand ETH-SLM statistics and ETH-SLM frame counts for all MEPs
attached to CFM-enabled interfaces on the router:
user@host> clear oam ethernet connectivity-fault-management synthetic-loss-measurement
To clear the on-demand ETH-SLM statistics and ETH-SLM frame counts only for MEPs
attached to the logical interface ge-0/5.9.0:
user@host> clear oam ethernet connectivity-fault-management synthetic-loss-measurement
ge-0/5/9.0
Action
To clear the iterator statistics for remote MEP 1 and iterator profile i1 with MEPs
belonging to the maintenance association ma1 within the maintenance domain
default-1:
user@host> clear oam ethernet connectivity-fault-management sla-iterator-statistics
sla-iterator i1 maintenance-domain default-1 maintenance-association ma1 local-mep 1
remote-mep 1
To clear the iterator statistics for remote MEP 1 and iterator profile i2 with MEPs
belonging to the maintenance association ma1 within the maintenance domain default-1:
user@host> clear oam ethernet connectivity-fault-management sla-iterator-statistics
sla-iterator i2 maintenance-domain default-1 maintenance-association ma1 local-mep 1
remote-mep 1
Related
Documentation
656
Solution
Perform the following steps to analyze and debug any problems with the ETH-SLM
functionality.
1.
2. Examine any failures that might have occurred in the CFM session for which the
ETH-SLM feature is enabled. The CFM session must be in the up state for the ETH-SLM
functionality to work correctly. Use the show oam ethernet
connectivity-fault-management mep-database maintenance-domain md-name
maintenance-association ma-name local-mep mep-id remote-mep remote-mep-id
all of the preceding troubleshooting steps, enable the tracing operations for Ethernet
CFM by including the traceoptions statement at the [edit protocols oam ethernet
connectivity-fault-management] hierarchy level.
[edit protocols oam ethernet connectivity-fault-management]
traceoptions {
file <filename> <files number <match regular-expression microsecond-stamp>>
<size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
Related
Documentation
657
between back-to-back transmission of SLA frames for one connection, with values
from 10 through 3,600,000. The default value is 1000 ms.
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles i1]
user@host# set cycle-time cycle-time-value
5. (Optional) Configure the iteration period, which indicates the maximum number of
cycles per iteration (the number of connections registered to an iterator cannot exceed
this value), with values from 1 through 2000. The default value is 2000.
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles i1]
user@host# set iteration-period iteration-period-value
6. Configure the measurement type as loss measurement, statistical frame-loss
65,535. The default value is 1 (applicable only for two-way delay measurement).
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles i1]
user@host# set calculation-weight delay delay-value
8. (Optional) Configure the calculation weight for delay variation with values from 1
through 65,535. The default value is 1 (applicable only for two-way delay
measurement).
658
for two-way Ethernet frame delay measurement (ETH-DM). When the configured
threshold for average frame delay is exceeded, an SNMP trap is generated for ETH-DM.
The range is from 1 through 4294967295 microseconds.
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles i1]
user@host# set avg-fd-twoway-threshold avg-fd-twoway-threshold-value
10. (Optional) Configure the threshold value for average frame delay variation, in
in the upward or forward direction for Ethernet loss measurement (ETH-LM) and
Ethernet synthetic loss measurement (ETH-SLM). When the configured threshold for
average forward frame loss ratio is exceeded, an SNMP trap is generated for ETH-LM
and ETH-SLM. The range is from 1 through 100000 milli-percent.
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles i1]
user@host# set avg-flr-forward-threshold avg-flr-forward-threshold-value
12. (Optional) Configure the threshold value for average frame loss ratio, in milli-percent,
659
avg-flr-forward-threshold avg-flr-forward-threshold-value;
avg-flr-backward-threshold avg-flr-backward-threshold-value;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
Related
Documentation
Displaying the Configuration of an Iterator Profile for Loss Measurement on page 661
Displaying the Configuration of a Remote MEP with an Iterator Profile on page 662
660
profile-namei1
cycle-time1000 milliseconds
delay1
delay-variation1:
Action
To display information about the iterator profile, run the show command at the [edit
protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles] hierarchy level:
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles]
user@host# show
i1 {
cycle-time 1000;
iteration-period 2000;
measurement-type two-way-delay;
calculation-weight {
delay 1;
delay-variation 1;
}
}
Meaning
Action
Display the configuration of an iterator profile for loss measurement as configured in the
Configuring an Iterator Profile on page 658 topic with the following values:
profile-name12
cycle-time1000 milliseconds
To display information about the iterator profile, run the show command at the [edit
protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles] hierarchy level:
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles]
user@host# show
12 {
cycle-time 1000;
iteration-period 2000;
measurement-type loss;
}
Meaning
The configuration for an iterator profile for loss measurement is displayed as expected
with set values.
661
Action
profile-namei3
maintenance-domaindefault-1
maintenance-association1
short-name-format2octet
mep1
remote-mep1
data-tlv-size1
iteration-count1
priority1
To display information about the remote MEP, run the show command at the [edit
protocols oam ethernet connectivity-fault-management maintenance-domain default-1
maintenance association ma1 mep 1 remote-mep 1] hierarchy level:
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
default-1 maintenance association 1 short-name-format 2octet mep 1 remote-mep 1]
user@host# show
sla-iterator-profile i3 {
data-tlv-size 1;
iteration-count 1;
priority 1;
}
Meaning
The configuration for a remote MEP for two-way measurement is displayed as expected
with set values.
To disable an iterator profile for two-way delay measurement and for a remote MEP.
To disable an iterator profile (for example, i1) with the disable configuration command
for two-way measurement at the [edit protocols oam ethernet
connectivity-fault-management performance-monitoring sla-iterator-profiles i1] hierarchy
level:
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles i1]
user@host# disable
662
To disable an iterator profile for a remote MEP (for example, i2) with the deactivate
configuration command at the [edit protocols oam ethernet
Related
Documentation
Action
To display the iterator statistics for remote MEP 1 and iterator profile i1 with MEPs
belonging to the maintenance association ma1 and within the maintenance domain
default-1 (here, the iterator profile i1 is configured for two-way delay measurement):
user@host> show oam ethernet connectivity-fault-management sla-iterator-statistics
sla-iterator i1 maintenance-domain default-1 maintenance-association ma1 local-mep 1
remote-mep 1
Iterator statistics:
Maintenance domain: md6, Level: 6
Maintenance association: ma6, Local MEP id: 1000
Remote MEP id: 103, Remote MAC address: 00:90:69:0a:43:92
Iterator name: i1, Iterator Id: 1
Iterator cycle time: 10ms, Iteration period: 1 cycles
Iterator status: running, Infinite iterations: true
Counter reset time: 2010-03-19 20:42:39 PDT (2d 18:24 ago)
Reset reason: Adjacency flap
Iterator delay measurement statistics:
Delay weight: 1, Delay variation weight: 1
DMM sent
DMM skipped for threshold hit
DMM skipped for threshold hit window
DMR received
DMR out of sequence
DMR received with invalid time stamps
Average two-way delay
Average two-way delay variation
:
:
:
:
:
:
:
:
23898520
11000
0
23851165
1142
36540
129 usec
15 usec
663
:
:
:
:
:
:
22 usec
22 usec
134 usec
8 usec
6 usec
2 usec
Output fields are listed in the approximate order in which they appear.
Table 57: Displaying Iterator Statistics for Ethernet Delay Measurement Output Fields
Output Field Name
Maintenance domain
Level
Maintenance association
Local MEP id
Remote MEP id
Iterator name
Name of iterator.
Iterator Id
Number of cycles (in milliseconds) taken between back-to-back transmission of SLA frames for
this connection
Iteration period
Iterator status
Infinite iterations
Reset reason
Delay weight
DMM sent
Delay measurement message (DMM) PDU frames sent to the peer MEP in this session.
Number of DMM frames sent to the peer MEP in this session skipped during threshold hit.
Number of DMM frames sent to the peer MEP in this session skipped during the last threshold hit
window.
664
Table 57: Displaying Iterator Statistics for Ethernet Delay Measurement Output Fields (continued)
Output Field Name
DMR received
Average one-way forward delay variation for the statistics displayed in microseconds.
Average one-way backward delay variation for the statistics displayed in microseconds.
Weighted average two-way delay variation for the statistics displayed in microseconds.
Weighted average one-way forward delay variation for the statistics displayed in microseconds.
Weighted average one-way backward delay variation for the statistics displayed in microseconds.
To display the iterator statistics for remote MEP 1 and iterator profile i2 with MEPs
belonging to the maintenance association ma1 and within the maintenance domain
default-1 (here, the iterator profile i1 is configured for loss measurement):
user@host> show oam ethernet connectivity-fault-management sla-iterator-statistics
sla-iterator i2 maintenance-domain default-1 maintenance-association ma1 local-mep 1
remote-mep 1
Iterator statistics:
Maintenance domain: md6, Level: 6
Maintenance association: ma6, Local MEP id: 1000
Remote MEP id: 103, Remote MAC address: 00:90:69:0a:43:92
Iterator name: i2, Iterator Id: 2
Iterator cycle time: 1000ms, Iteration period: 2000 cycles
Iterator status: running, Infinite iterations: true
Counter reset time: 2010-03-19 20:42:39 PDT (2d 18:25 ago)
Reset reason: Adjacency flap
Iterator loss measurement statistics:
LMM sent
LMM skipped for threshold hit
LMM skipped for threshold hit window
: 238970
: 60
: 0
665
LMR received
LMR out of sequence
: 238766
: 43
:
:
:
:
0
0
0
0
:
:
:
:
0
0
0
0
:
:
:
:
0
0
0
0
(0.00%)
(0.00%)
(0.00%)
(0.00%)
Output fields are listed in the approximate order in which they appear.
Table 58: Displaying Iterator Statistics for Ethernet Loss Measurement Output Fields
Output Field Name
Maintenance domain
Level
Maintenance association
Local MEP id
RemoteMEP identifier
Iterator name
Name of iterator.
Iterator Id
Number of cycles (in milliseconds) taken between back-to-back transmission of SLA frames for
this connection
Iteration period
Iterator status
Infinite iterations
Reset reason
666
Table 58: Displaying Iterator Statistics for Ethernet Loss Measurement Output Fields (continued)
Output Field Name
LMM sent
Number of loss measurement message (LMM) PDU frames sent to the peer MEP in this session.
Number of LMM frames sent to the peer MEP in this session skipped during threshold hit.
Number of LMM frames sent to the peer MEP in this session skipped during the last threshold hit
window.
LMR received
Near-end (CIR)
Frame loss associated with ingress data frames for the statistics displayed.
Far-end (CIR)
Frame loss associated with egress data frames for the statistics displayed.
Near-end (EIR)
Frame loss associated with ingress data frames for the statistics displayed.
Far-end (EIR)
Frame loss associated with egress data frames for the statistics displayed.
Action
To clear the iterator statistics for remote MEP 1 and iterator profile i1 with MEPs
belonging to the maintenance association ma1 and within the maintenance domain
default-1:
user@host> clear oam ethernet connectivity-fault-management sla-iterator-statistics
sla-iterator i1 maintenance-domain default-1 maintenance-association ma1 local-mep 1
remote-mep 1
To clear the iterator statistics for remote MEP 1 and iterator profile i2 with MEPs
belonging to the maintenance association ma1 and within the maintenance
domain default-1:
user@host> clear oam ethernet connectivity-fault-management sla-iterator-statistics
sla-iterator i2 maintenance-domain default-1 maintenance-association ma1 local-mep 1
remote-mep 1
Related
Documentation
667
this connection should partake in the iterator for acquiring SLA measurements, with
values from 1 through 65,535. The default value is 0 (that is, infinite iterations).
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id
sla-iterator-profile profile-name]
user@host# set iteration-count count-value
6. (Optional) Set the priority, which is the vlan-pcp value that is sent in the Y.1731 data
668
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
Related
Documentation
for the VPLS connection using the sla-iterator-profiles statement at the [edit protocols
oam ethernet connectivity-fault-management performance-monitoring] hierarchy level.
For detailed instructions, see Configuring an Iterator Profile on page 658.
3. As part of the iterator configuration, include the statistical-frame-loss option for the
669
Related
Documentation
670
The two MEPs must be configured on two Ethernet physical interfaces or on two
Ethernet logical interfaces. For more information, see Configuring a MEP to Generate
and Respond to CFM Protocol Messages on page 536.
The two MEPs must be configuredon their respective routersunder the same
maintenance association (MA) identifier. For more information, see Creating a
Maintenance Association on page 533.
On both routers, the MA must be associated with the same maintenance domain (MD)
name. For more information, see Creating the Maintenance Domain on page 528.
On both routers, periodic packet management (PPM) must be running on the Routing
Engine and Packet Forwarding Engine, which is the default configuration. You can
disable PPM on the Packet Forwarding Engine only. However, the Ethernet frame delay
measurement feature requires that distributed PPM remain enabled on the Packet
Forwarding Engine of both routers. For more information about ppm, see the Junos OS
Routing Protocols Library for Routing Devices.
If the PPM process (ppm) is disabled on the Packet Forwarding Engine, you must
re-enable it. Re-enabling distributed ppm entails restarting the
ethernet-connectivity-fault-management process, which causes all connectivity fault
management (CFM) sessions to re-establish. For more information about CFM sessions,
see Configuring Ethernet Local Management Interface on page 546.
NOTE: The Ethernet frame delay measurement feature is supported only for
MEPs 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.
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.
For specific information about configuring routers to support ETH-DM, see Guidelines
for Configuring Routers to Support an ETH-DM Session on page 670 and Configuring
Routers to Support an ETH-DM Session on page 677.
671
Remote CFM maintenance association end pointThe unicast MAC address or the
numeric identifier of the remote maintenance association end point (MEP)the
physical or logical interface on the remote router that resides in the specified MD
and is named in the specified MAwith which to perform the ETH-DM session. For
more information, see Configuring a MEP to Generate and Respond to CFM Protocol
Messages on page 536.
Optional specifications:
CountYou can specify the number of ETH-DM requests to send for this frame delay
measurement session. The range is from 1 through 65,535 frames. The default value
is 10 frames.
NOTE: Although you can trigger frame delay collection for up to 65,535 ETH-DM
requests at a time, a router stores only the last 100 frame delay statistics per CFM
session (pair of peer MEPs).
Frame intervalYou can specify the number of seconds to elapse between ETH-DM
frame transmittals. The default value is 1 second.
For more detailed information about the parameters you can specify to start an ETH-DM
session, see the monitor ethernet delay-measurement operational command description
in the CLI Explorer.
672
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.
For a given CFM session (pair of peer MEPs), the ETH-DM database stores a maximum
of 100 statistics, with the older statistics being aged out as newer statistics are
collected for that pair of MEPs.
For one-way delay measurements collected within the same CFM session, the 100
most recent ETH-DM statistics can be retrieved at any point of time at the router on
which the receiver MEP is defined.
For two-way delay measurements collected within the same CFM session, the 100
most recent ETH-DM statistics can be retrieved at any point of time at the router on
which the initiator MEP is defined.
Related
Documentation
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. For more information, see the Junos
OS High Availability Library for Routing Devices.
Accuracy of frame delay data is compromised when the system is changing (such as
from reconfiguration). We recommend performing Ethernet frame delay measurements
on a stable system.
Guidelines for Managing ETH-DM Statistics and ETH-DM Frame Counts on page 673
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. For a detailed description of one-way Ethernet
frame delay measurement, including the exchange of one-way delay PDU frames, see
Ethernet Frame Delay Measurements Overview on page 628.
673
For a two-way ETH-DM session, statistics are collected in an ETH-DM database at the
router that contains the initiator MEP. For a detailed description of two-way Ethernet
frame delay measurement, including the exchange of two-way delay PDU frames, see
Ethernet Frame Delay Measurements Overview on page 628.
A CFM database stores CFM-related statistics andfor Ethernet interfaces that support
ETH-DMthe 100 most recently collected ETH-DM statistics for that pair of MEPs. You
can view ETH-DM statistics by using the delay-statistics or mep-statistics form of the
show oam ethernet connectivity-fault-management command to display the CFM statistics
for the MEP that collects the ETH-DM statistics you want to view.
Table 59 on page 674 describes the ETH-DM statistics calculated in an ETH-DM session.
Field Description
For a one-way ETH-DM session, the frame delay, in microseconds, collected at the receiver MEP.
To display frame delay statistics for a given one-way ETH-DM session, use the delay-statistics or
mep-statistics form of the show oam ethernet connectivity-fault-management command at the
receiver MEP for that session.
For a two-way ETH-DM session, the frame delay, in microseconds, collected at the initiator MEP.
When you start a two-way frame delay measurement, the CLI output displays each DMR frame
receipt timestamp and corresponding DMM frame delay and delay variation collected as the
session progresses.
To display frame delay statistics for a given two-way ETH-DM session, use the delay-statistics or
mep-statistics form of the show oam ethernet connectivity-fault-management command at the
initiator MEP for that session.
Average delay
When you start a two-way frame delay measurement, the CLI output includes a runtime display
of the average two-way frame delay among the statistics collected for the ETH-DM session only.
When you display ETH-DM statistics using a show command, the Average delay field displays the
average one-way and two- frame delays among all ETH-DM statistics collected at the CFM
session level.
For example, suppose you start two one-way ETH-DM sessions for 50 counts each, one after the
other. If, after both measurement sessions complete, you use a show command to display 100
ETH-DM statistics for that CFM session, the Average delay field displays the average frame delay
among all 100 statistics.
When you start a two-way frame delay measurement, the CLI output includes a runtime display
of the average two-way frame delay variation among the statistics collected for the ETH-DM
session only.
When you display ETH-DM statistics using a show command, the Average delay variation field
displays the average one-way and two- frame delay variations among all ETH-DM statistics
collected at the CFM session level.
674
Field Description
When you start a two-way frame delay measurement, the CLI output includes a runtime display
of the lowest two-way frame delay value among the statistics collected for the ETH-DM session
only.
Best-case delay
When you display ETH-DM statistics using a show command, the Best case delay field displays
the lowest one-way and two-way frame delays among all ETH-DM statistics collected at the
CFM session level.
Worst-case delay
When you start a two-way frame delay measurement, the CLI output includes a runtime display
of the highest two-way frame delay value among the statistics collected for the ETH-DM session
only.
When you display ETH-DM statistics using a show command, the Worst case delay field displays
the highest one-way and two-way frame delays among all statistics collected at the CFM session
level.
When you start a one-way frame delay measurement, the CLI output displays NA (not available) for this field. One-way
ETH-DM statistics are collected at the remote (receiver) MEP. Statistics for a given one-way ETH-DM session are available
only by displaying CFM statistics for the receiver MEP.
Field Description
1DMs sent
Number of one-way delay measurement (1DM) PDU frames sent to the peer MEP in this session.
Stored in the CFM database of the MEP initiating a one-way frame delay measurement.
675
Field Description
Stored in the CFM database of the MEP receiving a one-way frame delay measurement.
Number of delay measurement message (DMM) PDU frames sent to the peer MEP in this session.
DMMs sent
Stored in the CFM database of the MEP initiating a two-way frame delay measurement.
Number of delay measurement reply (DMR) frames sent (in response to a received DMM).
DMRs sent
Stored in the CFM database of the MEP responding to a two-way frame delay measurement.
Number of valid DMR frames received.
Stored in the CFM database of the MEP initiating a two-way frame delay measurement.
Number of invalid DMR frames received.
Stored in the CFM database of the MEP initiating a two-way frame delay measurement.
676
At the initiator MEP, the router counts the number of 1DM frames sent.
At the receiver MEP, the router counts the number of valid 1DM frames received and
the number of invalid 1DM frames received.
You can also view one-way ETH-DM frame countsfor a receiver MEPby using the
show oam ethernet connectivity-fault-management mep-statistics command to display
one-way statistics and frame counts together.
At the initiator MEP, the router counts the number of DMM frames sent, valid DMR
frames received, and invalid DMR frames received.
At the responder MEP, the router counts the number of DMR frames sent.
You can also view two-way ETH-DM frame countsfor an initiator MEPby using the
show oam ethernet connectivity-fault-management mep-statistics command to display
two-way statistics and frame counts together.
Related
Documentation
677
is typical:
[edit protocols]
oam {
ethernet {
connectivity-fault-management {
maintenance-domain md-name { # On both routers
level number;
maintenance-association ma-name { # On both routers
continuity-check {
interval 100ms;
hold-interval 1;
}
mep mep-id { # Attach to VLAN interface
auto-discovery;
direction (up | down);
interface interface-name;
priority number;
}
}
}
}
}
}
678
Ethernet frame delay measurement requires that ppm remains distributed to the Packet
Forwarding Engine. If ppm is not distributed to the Packet Forwarding Engines of both
routers, ETH-DM PDU frame timestamps and ETH-DM statistics are not valid.
Before you start ETH-DM, you must verify that the following configuration statement
is NOT present:
[edit]
routing-options {
ppm {
no-delegate-processing;
}
}
If distributed ppm processing is disabled (as shown in the stanza above) on either router,
you must re-enable it in order to use the ETH-DM feature.
Procedure to Ensure
that Distributed ppm is
Not Disabled
To ensure that distributed ppm is not disabled on a router:
1.
In the following example, distributed ppm is enabled on the router. In this case, you
do not need to modify the router configuration:
[edit]
user@host# show routing-options
ppm;
In the following example, distributed ppm is disabled on the router. In this case,
you must proceed to Step 2 to modify the router configuration:
[edit]
user@host show routing-options
ppm {
no-delegate-processing;
}
679
2. Modify the router configuration to re-enable distributed ppm and restart the Ethernet
[edit]
user@host# delete routing-options ppm no-delegate-processing
c. Commit the updated router configuration. For example:
[edit]
user@host# commit and-quit
commit complete
exiting configuration mode
d. To restart the Ethernet OAM Connectivity-Fault-Management process, enter the
680
}
}
}
Related
Documentation
681
delay measurement session from the CFM maintenance association end point (MEP)
on one of the routers to the peer MEP on the other router.
To start an ETH-DM session between the specified local MEP and the specified remote
MEP, enter the monitor ethernet delay-measurement command at operational mode.
The syntax of the command is as follows:
monitor ethernet delay-measurement
(one-way | two-way)
maintenance-domain md-name
maintenance-association ma-name
(remote-mac-address | mep remote-mep-id)
<count frame-count>
<wait interval-seconds>
<priority 802.1p value>
<size>
<no-session-id-tlv>
<xml>
For a one-way frame delay measurement, the command displays a runtime display of
the number of 1DM frames sent from the initiator MEP during that ETH-DM session.
One-way frame delay and frame delay variation measurements from an ETH-DM session
are collected in a CFM database at the router that contains the receiver MEP. You can
retrieve ETH-DM statistics from a CFM database at a later time.
For a two-way frame delay measurement, the command displays two-way frame delay
and frame delay variation values for each round-trip frame exchange during that ETH-DM
session, as well as a runtime display of useful summary information about the session:
average delay, average delay variation, best-case delay, and worst-case delay. Two-way
frame delay and frame delay variation values measurements from an ETH-DM session
are collected in a CFM database at the router that contains the initiator MEP. You can
retrieve ETH-DM statistics from a CFM database at a later time.
682
Packets transmitted: 10
Average delay: NA, Average delay variation: NA
Best case delay: NA, Worst case delay: NA
0 usec
8 usec
0 usec
19 usec
1 usec
9 usec
3 usec
30 usec
0 usec
16 usec
--- Delay measurement statistics --Packets transmitted: 10, Valid packets received: 10
Average delay: 103 usec, Average delay variation: 8 usec
Best case delay: 92 usec, Worst case delay: 122 usec
Related
Documentation
Guidelines for Managing ETH-DM Statistics and ETH-DM Frame Counts on page 673
683
Related
Documentation
0 usec
8 usec
0 usec
19 usec
1 usec
9 usec
3 usec
30 usec
0 usec
16 usec
--- Delay measurement statistics --Packets transmitted: 10, Valid packets received: 10
Average delay: 103 usec, Average delay variation: 8 usec
Best case delay: 92 usec, Worst case delay: 122 usec
684
Related
Documentation
Displaying ETH-DM Frame Counts for MEPs by Enclosing CFM Entity on page 686
Displaying ETH-DM Frame Counts for MEPs by Interface or Domain Level on page 686
Action
To display the ETH-DM statistics collected for MEPs belonging to MA ma1 and within
MD md1:
user@host> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain ma1 maintenance-association ma1
To display the ETH-DM statistics collected for ETH-DM sessions for the local MEP 201
belonging to MA ma2 and within MD md2:
user@host> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain md2 maintenance-association ma2 local-mep 201
To display the ETH-DM statistics collected for ETH-DM sessions from local MEPs
belonging to MA ma3 and within MD md3 to remote MEP 302:
user@host> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain md3 maintenance-association ma3 remote-mep 302
Action
To display the ETH-DM statistics and ETH-DM frame counts for MEPs in MA ma1 and
within MD md1:
685
To display the ETH-DM statistics and ETH-DM frame counts for the local MEP 201 in
MA ma2 and within MD md2:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md2 maintenance-association ma2 local-mep 201
To display the ETH-DM statistics and ETH-DM frame counts for the local MEP in
MD md3 and within MA ma3 that participates in an ETH-DM session with the remote
MEP 302:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain ma3 maintenance-association ma3 remote-mep 302
Display ETH-DM frame counts for CFM maintenance association end points (MEPs).
By default, the show oam ethernet connectivity-fault-management mep-database
command displays CFM database information for MEPs in the specified CFM maintenance
association (MA) within the specified CFM maintenance domain (MD).
NOTE: At the router attached to the initiator MEP for a one-way session, or
at the router attached to the receiver MEP for a two-way session, you can
only display ETH-DM frame counts.
Action
To display CFM database information (including ETH-DM frame counts) for all MEPs
in MA ma1 within MD md1:
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain ma1 maintenance-association ma1
To display CFM database information (including ETH-DM frame counts) only for local
MEP 201 in MA ma1 within MD md1:
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 302 in MD md3 within MA ma3:
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain ma3 maintenance-association ma3 remote-mep 302
Display ETH-DM frame counts for CFM maintenance association end points (MEPs).
By default, the show oam ethernet connectivity-fault-management interfaces command
displays CFM database information for MEPs attached to CFM-enabled Ethernet
interfaces on the router or at a maintenance domain level. For Ethernet interfaces that
support ETH-DM, any frame counts are also displayed when you specify the detail or
extensive command option.
686
NOTE: At the router attached to the initiator MEP for a one-way session, or
at the router attached to the receiver MEP for a two-way session, you can
only display ETH-DM frame counts.
Action
To display CFM database information (including ETH-DM frame counts) for all MEPs
attached to CFM-enabled Ethernet interfaces on the router:
user@host> show oam ethernet connectivity-fault-management interfaces detail
To display CFM database information (including ETH-DM frame counts) only for the
MEPs attached to CFM-enabled router interface ge-5/2/9.0:
user@host> show oam ethernet connectivity-fault-management interfaces ge-5/2/9.0 detail
To display CFM database information (including ETH-DM frame counts) only for MEPs
enclosed within CFM maintenance domains (MDs) at level 6:
user@host> show oam ethernet connectivity-fault-management interfaces level 6 detail
Action
To clear the ETH-DM statistics and ETH-DM frame counts for all MEPs attached to
CFM-enabled interfaces on the router:
user@host> clear oam ethernet connectivity-fault-management statistics
To clear the ETH-DM statistics and ETH-DM frame counts only for MEPs attached to
the logical interface ge-0/5.9.0:
user@host> clear oam ethernet connectivity-fault-management statistics ge-0/5/9.0
Related
Documentation
687
To display the ETH-DM statistics collected for MEPs belonging to MA ma1 and within
MD md1:
user@host> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain ma1 maintenance-association ma1
To display the ETH-DM statistics collected for ETH-DM sessions for the local MEP 201
belonging to MA ma2 and within MD md2:
user@host> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain md2 maintenance-association ma2 local-mep 201
To display the ETH-DM statistics collected for ETH-DM sessions from local MEPs
belonging to MA ma3 and within MD md3 to remote MEP 302:
user@host> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain md3 maintenance-association ma3 remote-mep 302
Related
Documentation
Action
To display the ETH-DM statistics and ETH-DM frame counts for MEPs in MA ma1 and
within MD md1:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md1 maintenance-association ma1
To display the ETH-DM statistics and ETH-DM frame counts for the local MEP 201 in
MA ma2 and within MD md2:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md2 maintenance-association ma2 local-mep 201
To display the ETH-DM statistics and ETH-DM frame counts for the local MEP in
MD md3 and within MA ma3 that participates in an ETH-DM session with the remote
MEP 302:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain ma3 maintenance-association ma3 remote-mep 302
Related
Documentation
688
Display ETH-DM frame counts for CFM maintenance association end points (MEPs).
NOTE: At the router attached to the initiator MEP for a one-way session, or
at the router attached to the receiver MEP for a two-way session, you can
only display ETH-DM frame counts.
Action
To display CFM database information (including ETH-DM frame counts) for all MEPs
in MA ma1 within MD md1:
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain ma1 maintenance-association ma1
To display CFM database information (including ETH-DM frame counts) only for local
MEP 201 in MA ma1 within MD md1:
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 302 in MD md3 within MA ma3:
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain ma3 maintenance-association ma3 remote-mep 302
Related
Documentation
Display ETH-DM frame counts for CFM maintenance association end points (MEPs).
By default, the show oam ethernet connectivity-fault-management interfaces command
displays CFM database information for MEPs attached to CFM-enabled Ethernet
interfaces on the router or at a maintenance domain level. For Ethernet interfaces that
support ETH-DM, any frame counts are also displayed when you specify the detail or
extensive command option.
NOTE: At the router attached to the initiator MEP for a one-way session, or
at the router attached to the receiver MEP for a two-way session, you can
only display ETH-DM frame counts.
Action
To display CFM database information (including ETH-DM frame counts) for all MEPs
attached to CFM-enabled Ethernet interfaces on the router:
user@host> show oam ethernet connectivity-fault-management interfaces detail
To display CFM database information (including ETH-DM frame counts) only for the
MEPs attached to CFM-enabled router interface ge-5/2/9.0:
689
To display CFM database information (including ETH-DM frame counts) only for MEPs
enclosed within CFM maintenance domains (MDs) at level 6:
user@host> show oam ethernet connectivity-fault-management interfaces level 6 detail
Related
Documentation
Action
To clear the ETH-DM statistics and ETH-DM frame counts for all MEPs attached to
CFM-enabled interfaces on the router:
user@host> clear oam ethernet connectivity-fault-management statistics
To clear the ETH-DM statistics and ETH-DM frame counts only for MEPs attached to
the logical interface ge-0/5.9.0:
user@host> clear oam ethernet connectivity-fault-management statistics ge-0/5/9.0
Related
Documentation
is typical:
[edit protocols]
690
oam {
ethernet {
connectivity-fault-management {
maintenance-domain md-name { # On both routers
level number;
maintenance-association ma-name { # On both routers
continuity-check {
interval 100ms;
hold-interval 1;
}
mep mep-id { # Attach to VLAN interface
auto-discovery;
direction (up | down);
interface interface-name;
priority number;
}
}
}
}
}
}
Related
Documentation
Ethernet frame delay measurement requires that ppm remains distributed to the Packet
Forwarding Engine. If ppm is not distributed to the Packet Forwarding Engines of both
routers, ETH-DM PDU frame timestamps and ETH-DM statistics are not valid.
Before you start ETH-DM, you must verify that the following configuration statement
is NOT present:
[edit]
routing-options {
ppm {
no-delegate-processing;
}
}
691
If distributed ppm processing is disabled (as shown in the stanza above) on either router,
you must re-enable it in order to use the ETH-DM feature.
Procedure to Ensure
that Distributed ppm is
Not Disabled
To ensure that distributed ppm is not disabled on a router:
1.
In the following example, distributed ppm is enabled on the router. In this case, you
do not need to modify the router configuration:
[edit]
user@host# show routing-options
ppm;
In the following example, distributed ppm is disabled on the router. In this case,
you must proceed to Step 2 to modify the router configuration:
[edit]
user@host show routing-options
ppm {
no-delegate-processing;
}
692
2. Modify the router configuration to re-enable distributed ppm and restart the Ethernet
[edit]
user@host# delete routing-options ppm no-delegate-processing
c. Commit the updated router configuration. For example:
[edit]
user@host# commit and-quit
commit complete
exiting configuration mode
d. To restart the Ethernet OAM Connectivity-Fault-Management process, enter the
Related
Documentation
693
Related
Documentation
For a one-way frame delay measurement, the command displays a runtime display of
the number of 1DM frames sent from the initiator MEP during that ETH-DM session.
One-way frame delay and frame delay variation measurements from an ETH-DM session
are collected in a CFM database at the router that contains the receiver MEP. You can
retrieve ETH-DM statistics from a CFM database at a later time.
For a two-way frame delay measurement, the command displays two-way frame delay
and frame delay variation values for each round-trip frame exchange during that ETH-DM
session, as well as a runtime display of useful summary information about the session:
average delay, average delay variation, best-case delay, and worst-case delay. Two-way
694
frame delay and frame delay variation values measurements from an ETH-DM session
are collected in a CFM database at the router that contains the initiator MEP. You can
retrieve ETH-DM statistics from a CFM database at a later time.
Action
To display the ETH-LM statistics for all MEPs attached to CFM-enabled interfaces on
the router:
user@host> show oam ethernet connectivity-fault-management loss-statistics
695
To display the ETH-DM statistics collected for MEPs belonging to MA ma1 and within
MD md1:
user@host> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain md1 maintenance-association ma1
To display the ETH-DM statistics and ETH-DM frame counts for MEPs in MA ma1 and
within MD md1:
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md1 maintenance-association ma1
To display CFM database information (including ETH-DM frame counts) for all MEPs
in MA ma1 within MD md1:
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain md1 maintenance-association ma1
Action
To clear the ETH-LM statistics for all MEPs attached to CFM-enabled interfaces on
the router:
user@host> clear oam ethernet connectivity-fault-management loss-statistics
Related
Documentation
Action
To display the ETH-DM statistics collected for MEPs belonging to MA ma1 and within
MD md1:
user@host> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain md1 maintenance-association ma1
696
Action
To clear the continuity measurement statistics for all MEPs attached to CFM-enabled
interfaces on the router:
user@host> clear oam ethernet connectivity-fault-management continuity-measurement
maintenance-domain md-name maintenance-association ma-name local-mep local-mep-id
remote-mep remote-mep-id
Related
Documentation
The interval statement specifies the time between the transmission of FNP messages.
You can specify 10 minutes (10m), 1 minute (1m), 10 seconds (10s), 1 second (1s), and
100 milliseconds (100ms). The loss-threshold statement specifies how many FNP
messages can be lost before the FNP message is considered aged out and flushed. You
must include the interface interface-name statement with the domain-id domain-id
statement. The domain-id statement specifies a domain ID for the route. FNP messages
can be received and processed on MX Series routers, but generating FNP messages is
not supported.
The show oam ethernet fnp interface, show oam ethernet fnp status, and show oam ethernet
fnp messages operational commands display the configured information.
697
FNP can be enabled only on logical interfaces that are part of a VPLS routing instance,
and none of the logical interfaces in the VPLS routing instance should have CCM
configured. FNP can be enabled on only one logical interface per physical interface.
Related
Documentation
698
Service providers need not raise alarms if there are lower-level failures.
Service providers can provide a refund to their subscribers or avail a refund from their
Internet provider based on service unavailability.
MX Series routers support ITU-T Y.1731 ETH-AIS to provide fault management for service
providers who provide carrier Ethernet services using IEEE 802.1ag standard.
Note that in the absence of AIS, a client MEP resumes generating loss-of-continuity
alarms when it detects the loss-of-continuity defect conditions from its server layer.
For point-to-point Ethernet services layer connectivity, a MEP has only one peer MEP.
Therefore, there is no ambiguity regarding the peer MEP for which the MEP should suppress
alarms when it receives the ETH-AIS information.
For multipoint Ethernet services layer connectivity, a MEP that receives ETH-AIS
information cannot determine the exact MEP that encountered the fault and, therefore,
cannot isolate the exact peer MEP to suppress the alarms. To avoid this scenario, Y.1731
recommends suppressing alarms for all peer MEPs in the same domain level irrespective
of connectivity status in a multipoint Ethernet services layer connectivity setup.
Table 61 on page 700 lists the operational mode commands that you can use in a
maintenance domain to check the various parameters pertaining to a MEP.
699
Terms Defined
AIS transmissionA MEP upon detecting a defect condition transmits AIS frames in
a direction opposite to its peer MEPs. The periodicity of AIS frames transmission is on
the basis of the AIS transmission period. An AIS transmission period of 1 second is
recommended. The first AIS frame must always be transmitted immediately following
the detection of a defect condition.
AIS receptionUpon receiving an AIS frame, a MEP examines it to ensure that the
frames maintenance domain level is the same as its own maintenance domain level.
The period field in the frame indicates the period at which the AIS frames can be
expected. When a MEP receives an AIS frame, it detects the defect condition. After
detection, when no AIS frames are received within an interval of 3.5 timesthe AIS
transmission period indicated in the AIS frames receivedthe MEP clears the AIS defect
condition. When the AIS condition is cleared and defects still exist, then the MEPs
continue to report alarms.
a. MEG LevelAlso called the maintenance domain level, it is a 3-bit field that is used
to carry the maintenance domain level of the client MEG.
b. VersionValue is always 0.
700
Period Value
Comments
000-011
Invalid value
100
1s
101
Invalid value
110
1 min
111
Invalid value
e. TLV offsetSet to 0.
f. End TLVAll-zeroes octet value.
Related
Documentation
Server layer and client layerThese layers are part of the ITU-T Recommendation
G.805 transport network functional model. This model is based on the concept of
layering within a transport network. A transport network is divided into several
independent transport layer networks that have a client-server association between
adjacent layer networks.
Ethernet services (ETH) layerA layer in the metro Ethernet network model, where
this layer is responsible for the OAM services that are required to support the Ethernet
services in the network.
701
hierarchy level. Therefore, alarms are reported according to the defect priority
configured.
Alarms are reported even when the higher domain levels exchange CCMs at a faster
rate than the lower domain levels.
When the service provider requests the MEP to generate an AIS for a lower level or for
the same level, the request is rejected.
AIS generation is stopped when the MEP clears the remote MEP within the maintenance
association.
When the auto-discovery statement is enabled for a MEP, the remote MEP information
is cleared after the configured hold interval expires.
The following tasks explain how to enable ETH-AIS in a maintenance domain, configure
an action to be taken when a defect is detected, and to attach the action profile to a CFM
MEP:
1.
2. Configure an action profile to use when one or more remote MEPs are down.
702
continuity check messages (CCMs) are received by the MEP and to raise an alarm
indication signal in response.
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event ais-trigger-condition]
user@host# set cross-connect-ccm
8. Configure the erroneous-ccm statement to inform the operator when CCMs with
unexpected MEP ID or maintenance domain level are received by the MEP and an AIS
alarm is raised in response.
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event ais-trigger-condition]
user@host# set erroneous-ccm
9. Configure the receive-ais statement to inform the operator that an AIS message has
been received from the peer MEP in its own maintenance level.
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event ais-trigger-condition]
user@host# set receive-ais
703
2. Configure the log-and-generate-ais statement to log the event that generated the AIS
message.
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name action]
user@host# edit log-and-generate-ais
3. Configure the interval between AIS messages that are to be received by the MEP as
1 minute or 1 second.
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name action log-and-generate-ais]
user@host# set interval (1m | 1s)
4. Configure the server maintenance domain level range of the MEP from 1 through 7.
level or maintenance association levelthe level which the client layer maintenance
association intermediate point (MIPs) and the MEPs existfrom 0 through 7.
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name]
user@host# edit level level
704
5. Configure the continuity check that is performed on all the MEPs in a domain level by
Related
Documentation
705
ge-5/2/9 {
vlan-tagging;
unit 0 {
vlan-id 512;
}
}
}
protocols {
oam {
ethernet {
connectivity-fault-management {
traceoptions {
file eoam_cfm.log size 1g files 2 world-readable;
flag all;
}
linktrace {
path-database-size 255;
age 10s;
}
maintenance-domain md6 {
level 6;
maintenance-association ma6 {
continuity-check {
interval 100ms;
hold-interval 1;
}
mep 201 {
interface ge-5/2/9.0;
direction down;
auto-discovery;
}
}
}
}
}
}
}
706
}
linktrace {
path-database-size 255;
age 10s;
}
maintenance-domain md6 {
level 6;
maintenance-association ma6 {
continuity-check {
interval 100ms;
hold-interval 1;
}
mep 101 {
interface ge-0/2/5.0;
direction down;
auto-discovery;
}
}
}
}
}
}
}
The counters are displayed as part of the local MEP database on Router MX-2.
user@MX-2> show oam ethernet connectivity-fault-management mep-database
maintenance-domain md6 maintenance-domain ma6
Maintenance domain name: md6, Format: string, Level: 6
Maintenance association name: ma6, Format: string
Continuity-check status: enabled, Interval: 100ms, Loss-threshold: 3 frames
MEP identifier: 101, Direction: down, MAC address: 00:90:69:0a:48:57
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
: 1590
CCMs received out of sequence
: 0
LBMs sent
: 0
Valid in-order LBRs received
: 0
Valid out-of-order LBRs received
: 0
LBRs received with corrupted data
: 0
LBRs sent
: 0
LTMs sent
: 0
707
LTMs received
LTRs sent
LTRs received
Sequence number of next LTM request
1DMs sent
Valid 1DMs received
Invalid 1DMs received
DMMs sent
DMRs sent
Valid DMRs received
Invalid DMRs received
Remote MEP count: 1
Identifier
MAC address
State
201
00:90:69:0a:43:94
ok
:
:
:
:
:
:
:
:
:
:
:
0
0
0
0
10
0
0
0
0
0
0
Interface
ge-0/2/5.0
The remote Router MX-1 should also collect the delay statistics (up to 100 per session)
for display with mep-statistics or delay-statistics.
user@MX-1> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md6
708
709
NOTE: When two systems are close to each other, their one-way delay values
are very high compared to their two-way delay values. This is because
one-way delay measurement requires the timing for the two systems to be
synchronized at a very granular level and MX Series routers do not support
this granular synchronization. However, two-way delay measurement does
not require synchronized timing, making two-way delay measurements more
accurate.
Related
Documentation
710
711
mep 101 {
interface ge-0/2/5.0;
direction down;
auto-discovery;
}
}
}
}
}
}
}
The counters are displayed as part of the MEP database on Router MX-1 maintenance
domain MD6.
user@MX-1> show oam ethernet connectivity-fault-management mep-database
maintenance-domain md6
Maintenance domain name: md6, Format: string, Level: 6
Maintenance association name: ma6, Format: string
Continuity-check status: enabled, Interval: 100ms, Loss-threshold: 3 frames
MEP identifier: 201, Direction: down, MAC address: 00:90:69:0a:43:94
Auto-discovery: enabled, Priority: 0
Interface name: ge-5/2/9.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
: 894
CCMs received out of sequence
: 0
LBMs sent
: 0
Valid in-order LBRs received
: 0
Valid out-of-order LBRs received
: 0
LBRs received with corrupted data
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
712
LTRs received
Sequence number of next LTM request
1DMs sent
Valid 1DMs received
Invalid 1DMs received
DMMs sent
DMRs sent
Valid DMRs received
Invalid DMRs received
Remote MEP count: 1
Identifier
MAC address
State
101
00:90:69:0a:48:57
ok
:
:
:
:
:
:
:
:
:
0
0
0
0
0
10
0
10
0
Interface
ge-5/2/9.0
The collected MEP statistics are saved (up to 100 per remote MEP or per CFM session)
and displayed as part of the MEP statistics on Router MX-1.
user@MX-1> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md6
MEP identifier: 201, MAC address: 00:90:69:0a:43:94
Remote MEP count: 1
CCMs sent
: 3154
CCMs received out of sequence
: 0
LBMs sent
: 0
Valid in-order LBRs received
: 0
Valid out-of-order LBRs received
: 0
LBRs received with corrupted data
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
Sequence number of next LTM request
: 0
1DMs sent
: 0
Valid 1DMs received
: 0
Invalid 1DMs received
: 0
DMMs sent
: 10
DMRs sent
: 0
Valid DMRs received
: 10
Invalid DMRs received
: 0
Remote MEP identifier: 101
Remote MAC address: 00:90:69:0a:48:57
Delay measurement statistics:
Index One-way delay Two-way delay
(usec)
(usec)
1
100
2
92
3
92
4
111
5
110
6
119
7
122
8
92
9
92
10
108
Average two-way delay
: 103 usec
Average two-way delay variation: 8 usec
Best case two-way delay
: 92 usec
Worst case two-way delay
: 122 usec
713
The collected delay statistics are also saved (up to 100 per session) and displayed as
part of the MEP delay statistics on Router MX-1.
user@MX-1> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain md6
MEP identifier: 201, MAC address: 00:90:69:0a:43:94
Remote MEP count: 1
Remote MAC address: 00:90:69:0a:48:57
Delay measurement statistics:
Index One-way delay Two-way delay
(usec)
(usec)
1
100
2
92
3
92
4
111
5
110
6
119
7
122
8
92
9
92
10
108
Average two-way delay
: 103 usec
Average two-way delay variation: 8 usec
Best case two-way delay
: 92 usec
Worst case two-way delay
: 122 usec
Related
Documentation
714
}
ge-5/2/9 {
unit 0;
}
}
protocols {
oam {
ethernet {
connectivity-fault-management {
traceoptions {
file eoam_cfm.log size 1g files 2 world-readable;
flag all;
}
linktrace {
path-database-size 255;
age 10s;
}
maintenance-domain md6 {
level 6;
maintenance-association ma6 {
continuity-check {
interval 100ms;
hold-interval 1;
}
mep 201 {
interface ge-5/0/0;
direction down;
auto-discovery;
}
}
}
}
}
}
}
715
path-database-size 255;
age 10s;
}
maintenance-domain md6 {
level 6;
maintenance-association ma6 {
continuity-check {
interval 100ms;
hold-interval 1;
}
mep 101 {
interface ge-0/2/2;
direction down;
auto-discovery;
}
}
}
}
}
}
}
Related
Documentation
Requirements
This example uses the following hardware and software components:
716
Two MX Series 3D Universal Edge Routers with Rev-B Dense Port Concentrators (DPCs)
MX-PE1 router has two Ethernet interfaces, ge-5/0/4 and ge-5/1/9. Virtual LAN (VLAN)
is configured on ge-5/0/4 and MPLS is configured on the ge-5/1/9 interface. The
ge-5/0/4.11 interface is used to configure the Layer 2 virtual circuit with MX-PE2 router.
The UP MEP, mep 2, is attached to the ge-5/0/4.11 interface. The three-color policer
firewall filter is also configured for the MX-PE1 router.
Similarly, MX-PE2 router has two Ethernet interfaces, ge-8/0/8 and ge-8/0/9. Virtual
LAN (VLAN) is configured on ge-8/0/8 and MPLS is configured on the ge-8/0/9 interface.
The ge-8/0/8.11 interface is used to configure the Layer 2 virtual circuit with MX-PE1
router. The UP MEP, mep 1, is attached to the ge-8/0/8.11 interface. The three-color policer
firewall filter is also configured for the MX-PE2 router.
Configuration
CLI Quick
Configuration
To quickly configure ETH-LM for single-tagged LMM/LMR PDUs, copy the following
commands, remove any line breaks, and then paste the commands into the CLI of each
device.
On Router PE1:
[edit]
set interfaces ge-5/0/4 encapsulation flexible-ethernet-services
set interfaces ge-5/0/4 unit 11 encapsulation vlan-ccc
set interfaces ge-5/0/4 unit 11 layer2-policer input-three-color abc
set interfaces ge-5/0/4 unit 11 family ccc
set interfaces ge-5/1/9 enable
set interfaces ge-5/1/9 unit 0 family inet address 12.1.1.1/24
set interfaces ge-5/1/9 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 4.4.4.4/32
717
On Router PE2:
[edit]
set interfaces ge-8/0/8 encapsulation flexible-ethernet-services
set interfaces ge-8/0/8 unit 11 encapsulation vlan-ccc
set interfaces ge-8/0/8 unit 11 layer2-policer input-three-color abc
set interfaces ge-8/0/8 unit 11 family ccc
set interfaces ge-8/0/9 enable
set interfaces ge-8/0/9 unit 0 family inet address 12.1.1.1/24
set interfaces ge-8/0/9 unit 0 family mpls
set interfaces ae0 unit 0 family inet
set interfaces lo0 unit 0 family inet address 3.3.3.3/32
set interfaces ge-8/0/8 flexible-vlan-tagging
set interfaces ge-8/0/8 unit 11 vlan-id 2000
set interfaces ge-8/0/8 unit 11 input-vlan-map swap
set interfaces ge-8/0/8 unit 11 input-vlan-map vlan-id 4094
set interfaces ge-8/0/8 unit 11 output-vlan-map swap
set routing-options router-id 3.3.3.3
set protocols mpls interface all
set protocols mpls interface fxp0.0 disable
set protocols ospf area 0.0.0.0 interface all
set protocols ospf area 0.0.0.0 interface fxp0.0 disable
set protocols ldp interface all
718
2.
3.
4.
719
6.
7.
8.
Results
From configuration mode, confirm your configuration by entering the show interfaces,
show protocols, show routing-options, and show firewall commands. If the output does
not display the intended configuration, repeat the instructions in this example to correct
the configuration.
user@PE1# show interfaces
interfaces {
ge-5/0/4 {
flexible-vlan-tagging;
720
encapsulation flexible-ethernet-services;
unit 11 {
encapsulation vlan-ccc;
vlan-id 2000;
input-vlan-map {
swap;
vlan-id 4094;
}
output-vlan-map swap;
layer2-policer {
input-three-color abc;
}
family ccc;
}
}
ge-5/1/9 {
enable;
unit 0 {
family inet {
address 12.1.1.1/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 4.4.4.4/32;
}
}
}
}
user@PE1# show protocols
protocols {
mpls {
interface all;
interface fxp0.0 {
disable;
}
}
ospf {
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
}
}
ldp {
interface all;
interface fxp0.0 {
disable;
}
}
l2circuit {
721
neighbor 3.3.3.3 {
interface ge-5/0/4.11 {
virtual-circuit-id 1003;
no-control-word;
}
}
}
oam {
ethernet {
connectivity-fault-management {
performance-monitoring {
delegate-server-processing;
}
maintenance-domain md {
level 4;
maintenance-association ma {
continuity-check {
interval 1s;
}
mep 2 {
interface ge-5/0/4.11;
direction up;
remote-mep 1;
}
}
}
}
}
}
}
user@PE1# show routing-options
routing-options {
router-id 4.4.4.4;
}
user@PE1# show firewall
firewall {
three-color-policer abc {
logical-interface-policer;
two-rate {
color-blind;
committed-information-rate 10m;
committed-burst-size 1500;
peak-information-rate 20m;
peak-burst-size 15k;
}
}
}
722
3.
4.
5.
6.
723
8.
Results
From configuration mode, confirm your configuration by entering the show interfaces,
show protocols, show routing-options, and show firewall commands. If the output does
not display the intended configuration, repeat the instructions in this example to correct
the configuration.
user@PE2# show interfaces
interfaces {
ge-8/0/8 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 11 {
encapsulation vlan-ccc;
vlan-id 2000;
input-vlan-map {
swap;
vlan-id 4094;
}
output-vlan-map swap;
layer2-policer {
input-three-color abc;
}
family ccc;
}
}
ge-8/0/9 {
unit 0 {
family inet {
address 12.1.1.2/24;
}
family mpls;
}
}
ae0 {
unit 0 {
family inet;
}
724
}
lo0 {
unit 0 {
family inet {
address 3.3.3.3/32;
}
}
}
}
user@PE2# show protocols
protocols {
mpls {
interface all;
interface fxp0.0 {
disable;
}
}
ospf {
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
}
}
ldp {
interface all;
interface fxp0.0 {
disable;
}
}
l2circuit {
neighbor 4.4.4.4 {
interface ge-8/0/8.11 {
virtual-circuit-id 1003;
no-control-word;
}
}
}
oam {
ethernet {
connectivity-fault-management {
maintenance-domain md {
level 4;
maintenance-association ma {
continuity-check {
interval 1s;
}
mep 1 {
interface ge-8/0/8.11;
direction up;
remote-mep 2;
}
}
}
725
}
}
}
}
user@PE2# show routing-options
routing-options {
router-id 3.3.3.3;
}
user@PE2# show firewall
firewall {
three-color-policer abc {
logical-interface-policer;
two-rate {
color-blind;
committed-information-rate 10m;
committed-burst-size 1500;
peak-information-rate 20m;
peak-burst-size 15k;
}
}
}
Verification
To start monitoring the Ethernet frame loss, issue the monitor ethernet loss-measurement
maintenance-domain md maintenance-association ma mep 1 command. Frame loss is
calculated by collecting the counter values applicable for ingress and egress service
frames where the counters maintain a count of transmitted and received data frames
between a pair of MEPs. The loss measurement statistics are retrieved as the output of
the monitor ethernet loss-measurement command. You can also issue the show oam
ethernet connectivity-fault-management interfaces detail ge-5/0/4.11 command to display
ETH-LM statistics.
Viewing ETH-LM
Purpose
Action
726
Meaning
Related
Documentation
The Ethernet interface details and statistics are displayed. This output indicates that the
ge-5/0/4.11 interface is active and its link status is up. Its maintenance domain name is
md and its level is 4. The MEP identifier of the ge-5/0/4.11 interface is indicated as 2 and
its direction is up. Under the statistics section, the output indicates that 10 LMMs were
sent and 10 valid LMRs were received by the interface.
Example: Measuring Ethernet Frame Loss for Dual-Tagged LMM/LMR PDUs on page 727
727
protocol data units (PDUs). By configuring ETH-LM, you can measure the Ethernet frame
loss that occur in your network.
Requirements
This example uses the following hardware and software components:
Two MX Series 3D Universal Edge Routers with Rev-B Dense Port Concentrators (DPCs)
MX-PE1 router has two Ethernet interfaces, ge-5/0/4 and ge-5/1/9. Virtual LAN (VLAN)
is configured on ge-5/0/4 and MPLS is configured on the ge-5/1/9 interface. The
ge-5/0/4.11 interface is used to configure the Layer 2 virtual circuit with MX-PE2 router.
The UP MEP, mep 2, is attached to the ge-5/0/4.11 interface. The three-color policer
firewall filter is also configured for the MX-PE1 router.
Similarly, MX-PE2 router has two Ethernet interfaces, ge-8/0/8 and ge-8/0/9. Virtual
LAN (VLAN) is configured on ge-8/0/8 and MPLS is configured on the ge-8/0/9 interface.
The ge-8/0/8.11 interface is used to configure the Layer 2 virtual circuit with MX-PE1
router. The UP MEP, mep 1, is attached to the ge-8/0/8.11 interface. The three-color policer
firewall filter is also configured for the MX-PE2 router.
728
Configuration
CLI Quick
Configuration
To quickly configure ETH-LM for dual tagged LMM/LMR PDUs, copy the following
commands, remove any line breaks, and then paste the commands into the CLI of each
device.
On Router PE1:
[edit]
set interfaces ge-5/0/4 encapsulation flexible-ethernet-services
set interfaces ge-5/0/4 unit 11 encapsulation vlan-ccc
set interfaces ge-5/0/4 unit 11 layer2-policer input-three-color abc
set interfaces ge-5/0/4 unit 11 family ccc
set interfaces ge-5/1/9 enable
set interfaces ge-5/1/9 unit 0 family inet address 12.1.1.1/24
set interfaces ge-5/1/9 unit 0 family mpls
set interfaces lo0 unit 0 family inet address 4.4.4.4/32
set interfaces ge-5/0/4 flexible-vlan-tagging
set interfaces ge-5/0/4 unit 11 vlan-tags outer 2000 inner 1000
set interfaces ge-5/0/4 unit 11 input-vlan-map swap-swap
set interfaces ge-5/0/4 unit 11 input-vlan-map vlan-id 4094
set interfaces ge-5/0/4 unit 11 input-vlan-map inner-vlan-id 4093
set interfaces ge-5/0/4 unit 11 output-vlan-map swap-swap
set routing-options router-id 4.4.4.4
set protocols mpls interface all
set protocols mpls interface fxp0.0 disable
set protocols ospf area 0.0.0.0 interface all
set protocols ospf area 0.0.0.0 interface fxp0.0 disable
set protocols ldp interface all
set protocols ldp interface fxp0.0 disable
set protocols l2circuit neighbor 3.3.3.3 interface ge-5/0/4.11 virtual-circuit-id 1003
set protocols l2circuit neighbor 3.3.3.3 interface ge-5/0/4.11 no-control-word
set protocols oam ethernet connectivity-fault-management performance-monitoring
delegate-server-processing
set protocols oam ethernet connectivity-fault-management maintenance-domain md
level 4
set protocols oam ethernet connectivity-fault-management maintenance-domain md
maintenance-association ma continuity-check interval 1s
set protocols oam ethernet connectivity-fault-management maintenance-domain md
maintenance-association ma mep 2 interface ge-5/0/4.11
set protocols oam ethernet connectivity-fault-management maintenance-domain md
maintenance-association ma mep 2 direction up
set protocols oam ethernet connectivity-fault-management maintenance-domain md
maintenance-association ma mep 2 remote-mep 1
set firewall three-color-policer abc logical-interface-policer
set firewall three-color-policer abc two-rate color-blind
set firewall three-color-policer abc two-rate committed-information-rate 10m
set firewall three-color-policer abc two-rate committed-burst-size 1500
set firewall three-color-policer abc two-rate peak-information-rate 20m
set firewall three-color-policer abc two-rate peak-burst-size 15k
On Router PE2:
[edit]
set interfaces ge-8/0/8 encapsulation flexible-ethernet-services
set interfaces ge-8/0/8 unit 11 encapsulation vlan-ccc
729
730
2.
3.
4.
5.
6.
7.
731
Results
From configuration mode, confirm your configuration by entering the show interfaces,
show protocols, show routing-options, and show firewall commands. If the output does
not display the intended configuration, repeat the instructions in this example to correct
the configuration.
user@PE1# show interfaces
interfaces {
ge-5/0/4 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 11 {
encapsulation vlan-ccc;
vlan-tags outer 2000 inner 1000;
input-vlan-map {
swap-swap;
vlan-id 4094;
inner-vlan-id 4093;
}
output-vlan-map swap-swap;
layer2-policer {
input-three-color abc;
}
family ccc;
}
}
ge-5/1/9 {
enable;
unit 0 {
family inet {
address 12.1.1.1/24;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 4.4.4.4/32;
}
}
}
}
user@PE1# show protocols
protocols {
mpls {
interface all;
732
interface fxp0.0 {
disable;
}
}
ospf {
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
}
}
ldp {
interface all;
interface fxp0.0 {
disable;
}
}
l2circuit {
neighbor 3.3.3.3 {
interface ge-5/0/4.11 {
virtual-circuit-id 1003;
no-control-word;
}
}
}
oam {
ethernet {
connectivity-fault-management {
performance-monitoring {
delegate-server-processing;
}
maintenance-domain md {
level 4;
maintenance-association ma {
continuity-check {
interval 1s;
}
mep 2 {
interface ge-5/0/4.11;
direction up;
remote-mep 1;
}
}
}
}
}
}
}
user@PE1# show routing-options
routing-options {
router-id 4.4.4.4;
}
user@PE1# show firewall
firewall {
733
three-color-policer abc {
logical-interface-policer;
two-rate {
color-blind;
committed-information-rate 10m;
committed-burst-size 1500;
peak-information-rate 20m;
peak-burst-size 15k;
}
}
}
2.
3.
4.
734
6.
7.
8.
Results
From configuration mode, confirm your configuration by entering the show interfaces,
show protocols, show routing-options, and show firewall commands. If the output does
not display the intended configuration, repeat the instructions in this example to correct
the configuration.
user@PE2# show interfaces
interfaces {
ge-8/0/8 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
unit 11 {
encapsulation vlan-ccc;
vlan-tags outer 2000 inner 1000;
input-vlan-map {
swap-swap;
vlan-id 4094;
735
inner-vlan-id 4093;
}
output-vlan-map swap-swap;
layer2-policer {
input-three-color abc;
}
family ccc;
}
}
ge-8/0/9 {
unit 0 {
family inet {
address 12.1.1.2/24;
}
family mpls;
}
}
ae0 {
unit 0 {
family inet;
}
}
lo0 {
unit 0 {
family inet {
address 3.3.3.3/32;
}
}
}
}
user@PE2# show protocols
protocols {
mpls {
interface all;
interface fxp0.0 {
disable;
}
}
ospf {
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
}
}
ldp {
interface all;
interface fxp0.0 {
disable;
}
}
l2circuit {
neighbor 4.4.4.4 {
interface ge-8/0/8.11 {
736
virtual-circuit-id 1003;
no-control-word;
}
}
}
oam {
ethernet {
connectivity-fault-management {
maintenance-domain md {
level 4;
maintenance-association ma {
continuity-check {
interval 1s;
}
mep 1 {
interface ge-8/0/8.11;
direction up;
remote-mep 2;
}
}
}
}
}
}
}
user@PE2# show routing-options
routing-options {
router-id 3.3.3.3;
}
user@PE2# show firewall
firewall {
three-color-policer abc {
logical-interface-policer;
two-rate {
color-blind;
committed-information-rate 10m;
committed-burst-size 1500;
peak-information-rate 20m;
peak-burst-size 15k;
}
}
}
Verification
To start the Ethernet frame loss measurement session, issue the monitor ethernet
loss-measurement maintenance-domain md maintenance-association ma mep 1 command.
Frame loss is calculated by collecting the counter values applicable for ingress and egress
service frames where the counters maintain a count of transmitted and received data
frames between a pair of MEPs. The loss measurement statistics are retrieved as the
output of the monitor ethernet loss-measurement command. You can also issue the show
oam ethernet connectivity-fault-management interfaces detail ge-5/0/4.11 command to
display ETH-LM statistics.
737
Viewing ETH-LM
Purpose
Action
738
Meaning
Related
Documentation
00:05:85:76:e5:30
ok
ge-5/0/4.11
The Ethernet interface details and statistics are displayed. This output indicates that the
ge-5/0/4.11 interface is active and its link status is up. Its maintenance domain name is
md and its level is 4. The MEP identifier of the ge-5/0/4.11 interface is indicated as 2 and
its direction is up. Under the statistics section, the output indicates that 10 LMMs were
sent and 10 valid LMRs were received by the interface.
operational command.
The fields for this command are described in Table 63 on page 739.
Parameter Range
Description
one-way or two-way
NA
remote-mac-address
mep identifier
18191
The MEP identifier to use for the measurement. The discovered MAC
address for this MEP identifier is used.
maintenance-domain
name
Existing MD name
maintenance-association
ma-id
Existing MA identifier
count count
wait time
1255 seconds
(default: 1)
If you attempt to monitor delays to a nonexistent MAC address, you must exit the
application manually using ^C:
739
Related
Documentation
For all OAM frame counters and Ethernet frame delay measurement statistics
To retrieve all Ethernet frame delay measurement statistics for a given session, use the
show oam ethernet connectivity-fault-management mep-statistics maintenance-domain
name maintenance-association name [local-mep identifier] [remote-mep identifier] [count
count] command.
To retrieve only Ethernet frame delay measurement statistics for a given session, use
the show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain name maintenance-association name [local-mep identifier]
[remote-mep identifier] [count count] command.
NOTE: The only difference in the two commands is the use of the
mep-statistics and delay-statistics keyword.
The fields for these commands are described in Table 64 on page 741.
740
Parameter Range
Description
maintenance-domain name
Existing MD name
maintenance-association ma-id
Existing MA identifier
local-mep identifier
18191
When a MEP has been specified, display statistics only for the
local MEP.
remote-mep identifier
18191
When a MEP has been specified, display statistics only for the
discovered MEP.
count count
1100 (default:100)
NOTE: For each MEP, you will see frame counters for sent and received
Ethernet frame delay measurement frames whenever MEP statistics are
displayed.
Related
Documentation
741
742
CHAPTER 34
Ethernet Ring Protection Using Ring Instances for Load Balancing on page 745
Example: Configuring Ethernet Ring Protection for MX Series Routers on page 746
Example: Configuring Load Balancing Within Ethernet Ring Protection for MX Series
Routers on page 752
Example: Viewing Ethernet Ring Protection StatusNormal Ring Operation on page 769
Example: Viewing Ethernet Ring Protection StatusRing Failure Condition on page 771
743
RPL owner nodeThis node owns the RPL and blocks or unblocks the RPL as conditions
require. This node initiates the R-APS message.
Normal nodeAll other nodes on the ring (that is, those that are not the RPL owner
node) operate as normal nodes and have no special role on the ring.
In addition to roles, each node on the Ethernet ring can be in one of several states:
IdleThe node is performing normally (there is no link failure on the ring). In this state,
traffic is unblocked on both ring ports, except for the RPL owner node, which blocks
the RPL port (the other RPL owner port is unblocked).
ProtectionWhen a failure occurs on the ring, a normal node will have traffic blocked
on the ring port that connects to the failed link. The RPL owner, if it is not at one end
of the failed link, will then unblock the RPL port so both ports are active.
NOTE: The R-APS protocol does not detect the number of RPL owner nodes
configured on the ring. You must configure only one RPL and RPL owner per
ring or protection switching will not work properly.
Ethernet ring protection only works when one link on the ring fails. Multiple link failures
will break the ring and cause protection switching to fail.
Several restrictions apply to Ethernet ring protection:
The Ethernet ring protection configured as a single instance only works at the physical
level (adjacent nodes must be directly connected). The ring protection operates at
the interface (port) level and not at the VLAN level.
Nonrevertive switching is not supported. When the link failure is cleared, traffic always
returns to normal operation.
You can configure Ethernet ring protection to optimize traffic load-balancing by using
multiple ring instances. For more information about multiple ring instances, see Ethernet
Ring Protection Using Ring Instances for Load Balancing on page 745
Related
Documentation
744
Example: Configuring Ethernet Ring Protection for MX Series Routers on page 746
Example: Viewing Ethernet Ring Protection StatusNormal Ring Operation on page 769
Example: Viewing Ethernet Ring Protection StatusRing Failure Condition on page 771
Ethernet Ring Protection Using Ring Instances for Load Balancing on page 745
Example: Configuring Load Balancing Within Ethernet Ring Protection for MX Series
Routers on page 752
NOTE: To learn how ERP works in a single-ring topology, see Ethernet Ring
Protection on page 743.
MX Series routers now support ERP ring instances. Whereas traffic in a single-ring topology
follows the same path, traffic within ring instances allows some traffic to pass through
one path while other traffic can follow a different path. Dividing traffic in this way supports
traffic load balancing in the physical ring.
Ring instances are like traffic channels that contain different sets of virtual LANS (VLANs).
A ring instance is responsible for the protection of a subset of VLANs that transport traffic
over the physical ring. When ring instances are configured for the ring, each ring instance
should have its own RPL owner, an east and a west interface, and a ring protection link
end.
Each ring instance has a control channel and a specific data channel. A data channel is
a group of bridge domain VLAN IDs. All VLAN IDs within the same ring interface share
the same data-forwarding properties controlled by the ERP. If no data channel is defined
in the ring configuration, ERP will only operate on the physical link instead of as a ring
instance using logical links.
When operating ERP in a topology with other protocols, the following considerations
should be observed:
Related
Documentation
ERP and Per-VLAN Spanning Tree (PVST) can be configured on the same topology
as long as PVST doesn't share the same VLAN with any Ethernet ring instance
configured on the physical port.
If ERP is configured only as a physical ring instance (a ring without a data channel) in
a topology also configured for PVST, ERP checks the PVST configuration on two ring
interfaces and automatically creates a data channel excluding VLANs used by PVST.
Example: Configuring Ethernet Ring Protection for MX Series Routers on page 746
745
Example Topology
The links connecting the three MX Series routers are shown in Figure 49 on page 746.
West
ge-1/0/1
East
R-APS
Channel
g016988
pg101
ge-1/0/4
West
pg103
ge-1/2/1
West
ge-1/0/3
ge-1/0/2
East
East
pg102
This example uses the following topology details for Ethernet ring protection:
746
Router 1 is the RPL owner. The node identification for Router 1 is MAC address
00:01:01:00:00:01.
The RPL link is ge-1/0/1.1 (this is also the R-APS messaging control channel).
Traffic flows among the nodes in the configured bridge domains. (That is, only the
control channels are configured.)
Router 1s east control channel interface is ge-1/0/1.1 (the RPL) and the west control
channel interface is ge-1/2/4.1. The protection group is pg101.
Router 2s east control channel interface is ge-1/0/2.1 (the RPL) and the west control
channel interface is ge-1/2/1.1. The protection group is pg102.
Router 3s east control channel interface is ge-1/0/3.1 (the RPL) and the west control
channel interface is ge-1/0/4.1. The protection group is pg103.
NOTE: Although not strictly required for physical ring protection, this example
configures Ethernet OAM with MEPs.
[edit]
bridge-domains {
bd1 {
domain-type bridge;
vlan-id 100;
interface ge-1/2/4.1;
interface ge-1/0/1.1;
routing-interface irb.0;
}
}
747
[edit]
protocols {
protection-group {
ethernet-ring pg101 {
node-id 00:01:01:00:00:01;
ring-protection-link-owner;
east-interface {
control-channel ge-1/0/1.1;
}
ring-protection-link-end;
west-interface {
control-channel ge-1/2/4.1;
}
}
}
}
4. Configure Ethernet OAM:
[edit]
protocols {
oam {
ethernet {
connectivity-fault-management {
action-profile rmep-defaults {
default-action {
interface-down;
}
}
maintenance-domain d1 {
level 0;
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;
}
}
}
}
}
}
}
}
748
Router 2 Configuration
To configure Router 2:
1.
[edit]
bridge-domains {
bd1 {
domain-type bridge;
vlan-id 100;
interface ge-1/2/1.1;
interface ge-1/0/2.1;
routing-interface irb.0;
}
}
3. Configure the Ethernet protection group:
[edit]
protocols {
protection-group {
ethernet-ring pg102 {
node-id 00:22:22:22:22:22;
east-interface {
control-channel ge-1/0/2.1;
}
west-interface {
749
control-channel ge-1/2/1.1;
}
}
}
}
4. Configure Ethernet OAM:
[edit]
protocols {
oam {
ethernet {
connectivity-fault-management {
action-profile rmep-defaults {
default-action {
interface-down;
}
}
maintenance-domain d1 {
level 0;
maintenance-association 100 {
mep 2 {
interface ge-1/2/1;
remote-mep 1 {
action-profile rmep-defaults;
}
}
}
}
maintenance-domain d3 {
level 0;
maintenance-association 100 {
mep 1 {
interface ge-1/0/2;
remote-mep 2 {
action-profile rmep-defaults;
}
}
}
}
}
}
}
}
Router 3 Configuration
To configure Router 3:
1.
750
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;
}
}
irb {
unit 0 {
family inet {
address 192.1.1.33/24;
}
}
}
}
2. Configure the bridge domain:
[edit]
bridge-domains {
bd1 {
domain-type bridge;
vlan-id 100;
interface ge-1/0/4.1;
interface ge-1/0/3.1;
routing-interface irb.0;
}
}
3. Configure the Ethernet protection group:
[edit]
protocols {
protection-group {
ethernet-ring pg103 {
node-id 00:33:33:33:33:33;
east-interface {
control-channel ge-1/0/3.1;
}
west-interface {
control-channel ge-1/0/4.1;
}
}
}
}
4. Configure Ethernet OAM:
[edit]
protocols {
oam {
ethernet {
751
connectivity-fault-management {
action-profile rmep-defaults {
default-action {
interface-down;
}
}
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;
}
}
}
}
}
}
}
}
Related
Documentation
Example: Viewing Ethernet Ring Protection StatusNormal Ring Operation on page 769
Example: Viewing Ethernet Ring Protection StatusRing Failure Condition on page 771
Example: Configuring Load Balancing Within Ethernet Ring Protection for MX Series
Routers
MX Series routers support Ethernet ring protection (ERP) to help achieve high reliability
and network stability. ERP is used in router or bridge networks to protect against link
failure. A single-ring topology is configured that uses one specific link called a ring
protection link (RPL) to protect the whole ring. When all links are up and running, the
RPL blocks traffic and remains idle. However, if a link fails, the RPL routes traffic to bypass
the failure on the ring.
MX Series routers now support ERP ring instances. Whereas traffic in a ring topology
follows the same path, traffic within a ring instance uses data channels to allow some
752
traffic to pass through one path while other traffic can follow a different one. Dividing
traffic in this way supports traffic load-balancing in the ring.
This example describes how to use ERP with ring instances to load-balance traffic while
still providing network protection from link failure:
Requirements
This example uses the following hardware and software components:
753
ring-2
data-channel [500,600]
ring-1
data-channel [200,300]
RPL owner
ring-1
CS1
RPL owner
ring-2
ge-5/2/3.0
west-interface
ge-2/0/4.0
east-interface
ge-3/2/4.0
east-interface
RP link end ring-1
CS2
ge-2/0/8.0
west-interface
RP link end ring-2
ge-2/0/5.0
west-interface
ge-2/1/1.0
east-interface
Customer Site 1
VLANs [200,300]
Customer Site 2
VLANs [500,600]
g017469
AS1
Settings
Ring instances
Customer sites
754
Settings
CS1 router
RPL ownerring-1.
East interfacege-3/2/4.0.
West interfacege-5/2/3.0.
CS2 router
Routing instancevs.
Bridge domains:
RPL ownerring-2.
East interfacege-2/0/4.0.
West interfacege-2/0/8.0.
755
Settings
AS1 router
East interfacege-2/0/5.0.
West interfacege-2/1/1.0.
Configuration
To enable ERP with ring instances on CS1, CS2, and AS1, perform these tasks:
To quickly configure CS1 for ERP, copy the following commands and paste them into the
switch terminal window of CS1:
[edit]
set interfaces ge-3/2/4 vlan-tagging
set interfaces ge-3/2/4 unit 0 family bridge interface-mode trunk
set interfaces ge-3/2/4 unit 0 family bridge vlan-id-list 100-1000
set interfaces ge-5/2/3 vlan-tagging
set interfaces ge-5/2/3 unit 0 family bridge interface-mode trunk
set interfaces ge-5/2/3 unit 0 family bridge vlan-id-list 100-1000
set protocols protection-group ethernet-ring ring-1 ring-protection-link-owner
set protocols protection-group ethernet-ring ring-1 east-interface control-channel ge-3/2/4.0
set protocols protection-group ethernet-ring ring-1 east-interface control-channel vlan 100
set protocols protection-group ethernet-ring ring-1 east-interface ring-protection-link-end
set protocols protection-group ethernet-ring ring-1 west-interface control-channel ge-5/2/3.0
set protocols protection-group ethernet-ring ring-1 west-interface control-channel vlan 100
set protocols protection-group ethernet-ring ring-1 data-channel vlan [200, 300]
set protocols protection-group ethernet-ring ring-2 east-interface control-channel ge-3/2/4.0
set protocols protection-group ethernet-ring ring-2 east-interface control-channel vlan 101
set protocols protection-group ethernet-ring ring-2 west-interface control-channel ge-5/2/3.0
set protocols protection-group ethernet-ring ring-2 west-interface control-channel vlan 101
set protocols protection-group ethernet-ring ring-2 data-channel vlan [500, 600]
set routing-instances vs instance-type virtual-switch
set routing-instances vs interface ge-3/2/4.0
set routing-instances vs interface ge-5/2/3.0
set routing-instances vs bridge-domains bd101 vlan-id 101
756
Step-by-Step
Procedure
Configure the trunk interface ge-3/2/4 to connect CS1 to CS2 and the trunk interface
ge-5/2/3 to connect CS1 to AS, and configure the family statement as bridge with
a VLAN ID list of 100 through 1000:
[edit interfaces]
user@cs1# set ge-3/2/4 vlan-tagging
user@cs1# set ge-3/2/4 unit 0 family bridge interface-mode trunk
user@cs1# set ge-3/2/4 unit 0 family bridge vlan-id-list 100-1000
user@cs1# set ge-5/2/3 vlan-tagging
user@cs1# set ge-5/2/3 unit 0 family bridge interface-mode trunk
user@cs1# set ge-5/2/3 unit 0 family bridge vlan-id-list 100-1000
2.
Enable ERP, specifying the control channels and data channels for ring-1 and ring-2,
and configure ring-1 as the ring protection link owner:
[edit protection-group]
user@cs1# set ethernet-ring ring-1 ring-protection-link-owner
user@cs1# set ethernet-ring ring-1 east-interface control-channel ge-3/2/4.0
user@cs1# set ethernet-ring ring-1 east-interface control-channel vlan 100
user@cs1# set ethernet-ring ring-1 east-interface ring-protection-link-end
user@cs1# set ethernet-ring ring-1 west-interface control-channel ge-5/2/3.0
user@cs1# set ethernet-ring ring-1 west-interface control-channel vlan 100
user@cs1# set ethernet-ring ring-1 data-channel vlan [200, 300]
user@cs1# set ethernet-ring ring-2 east-interface control-channel ge-3/2/4.0
user@cs1# set ethernet-ring ring-2 east-interface control-channel vlan 101
user@cs1# set ethernet-ring ring-2 west-interface control-channel ge-5/2/3.0
user@cs1# set ethernet-ring ring-2 west-interface control-channel vlan 101
user@cs1# set ethernet-ring ring-2 data-channel vlan [500, 600]
3.
Configure the routing instance, the bridge domains, and the VLAN IDs associated
with each bridge domain:
[edit routing-instances]
user@cs1# set vs instance-type virtual-switch
user@cs1# set vs interface ge-3/2/4.0
user@cs1# set vs interface ge-5/2/3.0
user@cs1# set vs bridge-domains bd100 vlan-id 100
user@cs1# set vs bridge-domains bd101 vlan-id 101
user@cs1# set vs bridge-domains bd200 vlan-id 200
user@cs1# set vs bridge-domains bd300 vlan-id 300
user@cs1# set vs bridge-domains bd500 vlan-id 500
user@cs1# set vs bridge-domains bd600 vlan-id 600
Results
757
vlan-tagging;
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 100-1000;
}
}
}
ge-5/2/3 {
vlan-tagging;
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 100-1000;
}
}
}
protocols {
protection-group {
ethernet-ring ring-1 {
east-interface {
control-channel {
ge-3/2/4.0;
vlan 100;
}
ring-protection-link-end;
}
west-interface {
control-channel {
ge-5/2/3.0;
vlan 100;
}
}
data-channel {
vlan [ 200 300 ];
}
}
}
protection-group {
ethernet-ring ring-2{
east-interface {
control-channel {
ge-3/2/4.0;
vlan 101;
}
}
west-interface {
control-channel {
ge-5/2/3.0;
vlan 101;
}
}
data-channel {
vlan [ 500 600 ];
}
}
758
}
}
routing-instances {
vs {
instance-type virtual-switch;
interface ge-3/2/4.0;
interface ge-5/2/3.0;
bridge-domains {
bd100 {
vlan-id 100;
}
bd101 {
vlan-id 101;
}
bd200 {
vlan-id 200;
}
bd300 {
vlan-id 300;
}
bd500 {
vlan-id 500;
}
bd600 {
vlan-id 600;
}
}
}
}
}
To quickly configure CS2 for ERP, copy the following commands and paste them into
the switch terminal window of CS2:
[edit]
set interfaces ge-2/0/4 unit 0 family bridge interface-mode trunk
set interfaces ge-2/0/4 unit 0 family bridge vlan-id-list 100-1000
set interfaces ge-2/0/8 unit 0 family bridge interface-mode trunk
set interfaces ge-2/0/8 unit 0 family bridge vlan-id-list 100-1000
set protocols protection-group ethernet-ring ring-1 east-interface control-channel ge-2/0/4.0
set protocols protection-group ethernet-ring ring-1 east-interface control-channel vlan 100
set protocols protection-group ethernet-ring ring-1 west-interface control-channel ge-2/0/8.0
set protocols protection-group ethernet-ring ring-1 west-interface control-channel vlan 100
set protocols protection-group ethernet-ring ring-1 data-channel vlan [200, 300]
set protocols protection-group ethernet-ring ring-2 ring-protection-link-owner
set protocols protection-group ethernet-ring ring-2 east-interface control-channel ge-2/0/4.0
set protocols protection-group ethernet-ring ring-2 east-interface control-channel vlan 101
set protocols protection-group ethernet-ring ring-2 west-interface control-channel ge-2/0/8.0
set protocols protection-group ethernet-ring ring-2 west-interface ring-protection-link-end
set protocols protection-group ethernet-ring ring-2 west-interface control-channel vlan 101
set protocols protection-group ethernet-ring ring-2 data-channel vlan [500, 600]
set bridge-domains bd100 vlan-id 100
set bridge-domains bd101 vlan-id 101
set bridge-domains bd200 vlan-id 200
set bridge-domains bd300 vlan-id 300
759
Step-by-Step
Procedure
Configure the trunk interface ge-2/0/4 to connect CS2 to CS1 and trunk interface
ge-2/0/8 to connect CS2 to CS1, and configure the family statement as bridge with
a VLAN ID list of 100 through 1000:
[edit interfaces]
user@cs2# set ge-2/0/4 unit 0 family bridge interface-mode trunk
user@cs2# set ge-2/0/4 unit 0 family bridge vlan-id-list 100-1000
user@cs2# set ge-2/0/8 unit 0 family bridge interface-mode trunk
user@cs2# set ge-2/0/8 unit 0 family bridge vlan-id-list 1001000
2.
Enable ERP, specifying the control channels and data channels for ring-1 and ring-2,
and configure ring-2 as the ring protection link owner:
[edit protection-group]
user@cs2# set ethernet-ring ring-1 east-interface control-channel ge-2/0/4.0
user@cs2# set ethernet-ring ring-1 east-interface control-channel vlan 100
user@cs2# set ethernet-ring ring-1 west-interface control-channel ge-2/0/8.0
user@cs2# set ethernet-ring ring-1 west-interface control-channel vlan 100
user@cs2# set ethernet-ring ring-2 data-channel vlan [200, 300]
user@cs2# set ethernet-ring ring-2 east-interface control-channel ge-2/0/4.0
user@cs2# set ethernet-ring ring-2 east-interface control-channel vlan 101
user@cs2# set ethernet-ring ring-2 ring-protection-link-owner
user@cs2# set ethernet-ring ring-2 west-interface control-channel ge-2/0/8.0
user@cs2# set ethernet-ring ring-2 west-interface control-channel vlan 101
user@cs2# set ethernet-ring ring-2 west-interface ring-protection-link-end
user@cs2# set ethernet-ring ring-2 data-channel vlan [500, 600]
3.
Configure the routing instance, the bridge domains, and the VLAN IDs associated
with each bridge domain:
[edit bridge-domains]
user@cs2# set bd100 vlan-id 100
user@cs2# set bd101 vlan-id 101
user@cs2# set bd200 vlan-id 200
user@cs2# set bd300 vlan-id 300
user@cs2# set bd500 vlan-id 500
user@cs2# set bd600 vlan-id 600
Results
760
}
ge-2/0/8 {
unit 0 {
family bridge {
interface-mode trunk;
vlan-id-list 100-1000;
}
}
}
protocols {
protection-group {
ethernet-ring ring-1 {
east-interface {
control-channel {
ge-2/0/4.0;
vlan 100;
}
}
west-interface {
control-channel {
ge-2/0/8.0;
vlan 100;
}
}
data-channel {
vlan [200, 300];
}
}
}
ethernet-ring ring-2 {
east-interface {
control-channel {
ge-2/0/4.0;
vlan 101;
}
}
west-interface {
control-channel {
ge-2/0/8.0;
vlan 101;
}
ring-protection-link-end;
}
data-channel {
vlan [500, 500];
}
}
}
bridge-domains {
bd100 {
vlan-id 100;
}
bd101 {
vlan-id 101;
}
bd200 {
761
vlan-id 200;
}
bd300 {
vlan-id 300;
}
bd500 {
vlan-id 500;
}
bd600 {
vlan-id 600;
}
}
}
To quickly configure AS1 for ERP, copy the following commands and paste them into the
switch terminal window of AS1:
[edit]
set interfaces ge-2/0/5 unit 0 family bridge interface-mode trunk
set interfaces ge-2/0/5 unit 0 family bridge vlan-id-list 100-1000
set interfaces ge-2/1/1 unit 0 family bridge interface-mode trunk
set interfaces ge-2/1/1 unit 0 family bridge vlan-id-list 100-1000
set protocols protection-group ethernet-ring ring-1 east-interface control-channel ge-2/0/5.0
set protocols protection-group ethernet-ring ring-1 east-interface control-channel vlan 100
set protocols protection-group ethernet-ring ring-1 west-interface control-channel ge-2/1/1.0
set protocols protection-group ethernet-ring ring-1 west-interface control-channel vlan 100
set protocols protection-group ethernet-ring ring-1 data-channel vlan [200, 300]
set protocols protection-group ethernet-ring ring-2 east-interface control-channel ge-2/0/5.0
set protocols protection-group ethernet-ring ring-2 east-interface control-channel vlan 101
set protocols protection-group ethernet-ring ring-2 west-interface control-channel ge-2/1/1.0
set protocols protection-group ethernet-ring ring-2 west-interface control-channel vlan 101
set protocols protection-group ethernet-ring ring-2 data-channel vlan [500, 600]
set bridge-domains bd100 vlan-id 100
set bridge-domains bd101 vlan-id 101
set bridge-domains bd200 vlan-id 200
set bridge-domains bd300 vlan-id 300
set bridge-domains bd500 vlan-id 500
set bridge-domains bd600 vlan-id 600
Step-by-Step
Procedure
Configure the trunk interface ge-2/0/5 to connect CS2 to CS1 and trunk interface
ge-2/1/1 to connect CS2 to CS1, and configure the family statement as bridge with
a VLAN ID list of 100 through 1000:
[edit interfaces]
user@as1# set ge-2/0/5 unit 0 family bridge interface-mode trunk
user@as1# set ge-2/0/5 unit 0 family bridge vlan-id-list 100-1000
user@as1# set ge-2/1/1 unit 0 family bridge interface-mode trunk
user@as1# set ge-2/1/1 unit 0 family bridge vlan-id-list 100
2.
Enable ERP, specifying the control channels and data channels for ring-1 and ring-2:
762
[edit protection-group]
user@as1# set ethernet-ring ring-1 east-interface control-channel ge-2/0/5.0
user@as1# set ethernet-ring ring-1 east-interface control-channel vlan 100
user@as1# set ethernet-ring ring-1 west-interface control-channel ge-2/1/1.0
user@as1# set ethernet-ring ring-1 west-interface control-channel vlan 100
user@as1# set ethernet-ring ring-2 east-interface control-channel ge-2/0/5.
user@as1# set ethernet-ring ring-2 east-interface control-channel vlan 101
user@as1# set ethernet-ring ring-2 west-interface control-channel ge-2/1/1.0
user@as1# set ethernet-ring ring-2 west-interface control-channel vlan 101
user@as1# set ethernet-ring ring-2 data-channel vlan [500, 600]
3.
Configure the routing instance, the bridge domains, and the VLAN IDs associated
with each bridge domain:
[edit bridge-domains]
user@as1# set bd100 vlan-id 100
user@as1# set bd101 vlan-id 101
user@as1# set bd200 vlan-id 200
user@as1# set bd300 vlan-id 300
user@as1# set bd500 vlan-id 500
user@as1# set bd600 vlan-id 600
Results
763
Verification
To confirm that the ERP configuration for multiple ring instances is operating, perform
these tasks:
764
Meaning
Request/state
ring-1
ring-2
13:22:af:31:fc:00
NR
NR
No Flush
No
No
Ring Protection
Link Blocked
Yes
Yes
Originator
Remote
Yes
No
The output displayed shows that protection groups ring-1 and ring-2 have a Request/state
of NR, meaning there is no request for APS on the ring. If a Request/state of SF is displayed,
it indicates there is a signal failure on the ring. The output also shows that the ring
protection link is not blocked. The No Flush field displays No, indicating that MAC
addresses will be flushed when the ring nodes receive this message first time. A value of
Yes would indicate MAC address flushing is not needed. The Originator field for ring-1
displays yes, indicating that this node is an R-APS originator.
STP index
122
123
Forward State
forwarding
forwarding
STP index
Forward State
ge-3/2/4
ge-5/2/3
124
125
discarding
forwarding
765
Meaning
The output displayed shows the STP index number used by each interface in ring instances
ring-1 and ring-2. The STP index controls the forwarding behavior for a set of VLANs on
the data channel of a ring instance on a ring interface. For ring instances, there are multiple
STP index numbers (here representing VLANs 200, 300, 500, and 600). The Forward
State shows whether the data channel is forwarding or discarding traffic.
Action
Verify the data channel logical interfaces and the VLAN IDs controlled by a ring instance
data channel.
List dynamic VLAN membership:
user@cs1>show protection-group ethernet-ring vlan
Ethernet ring IFBD parameters for protection group ring-1
Interface
ge-3/2/4
ge-5/2/3
ge-3/2/4
ge-5/2/3
Vlan
200
200
300
300
STP Index
122
123
122
123
Bridge Domain
vs/bd200
vs/bd200
vs/bd300
vs/bd300
Meaning
Vlan
500
500
600
600
STP Index
124
125
124
125
Bridge Domain
vs/bd500
vs/bd500
vs/bd600
vs/bd600
The output displayed shows the ring interfaces ge-3/2/4 and ge-5/2/3 in protection
groups ring-1 and ring-2. For ring-1, VLAN 200 and VLAN 300 are being supported on both
STP Index 122 and 123 on bridge domains bd200 and bd300. For ring-2, VLAN 500 and
VLAN 600 are being supported on both STP Index 124 and 125 on bridge domains bd500
and bd600. The data channel controls the traffic on the VLAN IDs to facilitate load
balancing.
Meaning
766
Request/state
No Flush
Ring Protection
Originator
NR
No
Link Blocked
No
No
NR
No
Yes
Yes
Remote
The output displayed shows that protection groups ring-1 and ring-2 have a Request/state
of NR, meaning there is no request for APS on the ring. If a Request/state of SF is displayed,
it indicates there is a signal failure on the ring. The output also shows that the ring
protection link is not blocked. The No Flush field displays No, indicating that MAC
addresses will be flushed when the ring nodes receive this message first time. A value of
Yes would indicate MAC address flushing is not needed. The Originator field for ring-1
displays yes, indicating that this node is an R-APS originator. The Originator field for ring-2
displays No, indicating that this node is not an R-APS originator.
STP index
44
45
Forward State
forwarding
forwarding
Meaning
STP index
46
47
Forward State
forwarding
discarding
The output displayed shows the STP index number used by each interface in ring instances
ring-1 and ring-2. The STP index controls the forwarding behavior for a set of VLANs on
the data channel of a ring instance on a ring interface. For ring instances, there are multiple
STP index numbers (here representing VLANs 200, 300, 500, and 600). The Forward
State shows whether the data channel is forwarding or discarding traffic.
Action
Verify the data channel logical interfaces and the VLAN IDs controlled by a ring instance
data channel.
List dynamic VLAN membership:
user@cs2> show protection-group ethernet-ring vlan
Ethernet ring IFBD parameters for protection group ring-1
Interface
ge-2/0/4
ge-2/0/8
ge-2/0/4
ge-2/0/8
Vlan
200
200
300
300
STP Index
44
45
44
45
Bridge Domain
defaultswitch/bd200
default-switch/bd200
defaultswitch/bd300
default-switch/bd300
Vlan
500
500
STP Index
46
47
Bridge Domain
defaultswitch/bd500
default-switch/bd500
767
ge-2/0/4
ge-2/0/8
Meaning
600
600
46
47
defaultswitch/bd600
default-switch/bd600
The output displayed shows the ring interfaces ge-2/0/4 and ge-2/0/8 in protection
groups ring-1 and ring-2. For ring-1, VLAN 200 and VLAN 300 are being supported on both
STP Index 44 and 45 on bridge domains bd200 and bd300. For ring-2, VLAN 500 and
VLAN 600 are being supported on both STP Index 46 and 47 on bridge domains bd500
and bd600. The data channel controls the traffic on the VLAN IDs to facilitate load
balancing.
Request/state
Ring Protection
Originator
NR
No
Link Blocked
Yes
No
NR
No
Yes
No
Ring-1
00:21:59:03:ff:d0
Ring-2
13:22:af:31:fc:00
Meaning
No Flush
Remote
The output displayed shows that protection groups ring-1 and ring-2 have a Request/state
of NR, meaning there is no request for APS on the ring. If a Request/state of SF is displayed,
it indicates there is a signal failure on the ring. The output also shows that the ring
protection link is not blocked. The No Flush field displays No, indicating that MAC
addresses will be flushed when the ring nodes receive this message first time. A value of
Yes would indicate MAC address flushing is not needed. The Originator field for ring-1 and
ring-2 displays No, indicating that this node is not the R-APS originator.
STP index
22
23
Forward State
forwarding
forwarding
768
STP index
24
25
Forward State
forwarding
forwarding
Meaning
The output displayed shows the STP index number used by each interface in ring instances
ring-1 and ring-2. The STP index controls the forwarding behavior for a set of VLANs on
the data channel of a ring instance on a ring interface. For ring instances, there are multiple
STP index numbers (here representing VLANs 200, 300, 500, and 600). The Forward
State shows whether the data channel is forwarding or discarding traffic. All data channels
are forwarding traffic.
Action
Verify the data channel logical interfaces and the VLAN IDs controlled by a ring instance
data channel.
List dynamic VLAN membership:
user@as1>show protection-group ethernet-ring vlan
Ethernet ring IFBD parameters for protection group ring-1
Interface
ge-2/0/5
ge-2/1/1
ge-2/0/5
ge-2/1/1
Vlan
200
200
300
300
STP Index
22
23
22
23
Bridge Domain
default-switch/bd200
default-switch/bd200
default-switch/bd300
default-switch/bd300
Meaning
Related
Documentation
Vlan
500
500
600
600
STP Index
24
25
24
25
Bridge Domain
default-switch/bd500
default-switch/bd500
default-switch/bd600
default-switch/bd600
The output displayed shows the ring interfaces ge-2/0/5 and ge-2/1/1 in protection groups
ring-1 and ring-2. For ring-1, VLAN 200 and VLAN 300 are being supported on both STP
Index 22 and 23 on bridge domains bd200 and bd300. For ring-2, VLAN 500 and VLAN
600 are being supported on both STP Index 24 and 25 on bridge domains bd500 and
bd600. The data channel controls the traffic on the VLAN IDs to facilitate load-balancing.
Ethernet Ring Protection Using Ring Instances for Load Balancing on page 745
769
Originator
Yes
Remote Node ID
Note that the ring protection link is blocked and the node is marked as the originator of
the protection.
user@router1> show protection-group ethernet-ring interface
Ethernet ring port parameters for protection group pg101
Interface
ge-1/0/1
ge-1/2/4
Control Channel
ge-1/0/1.1
ge-1/2/4.1
Forward State
discarding
forwarding
Note that the protection interface is discarding while the other interface is forwarding.
user@router1> show protection-group ethernet-ring node-state
Ethernet ring
APS State
Event
Ring Protection Link Owner
pg101
idle
NR-RB
Yes
Restore Timer
disabled
Note that only minimal RAPS messages have been sent to establish the ring.
Under normal operating conditions, the other routers on the ring (Router 2 and Router
3) will see the following similar output:
Router 2 and Router 3 Operational Commands (Normal Ring Operation)
user@router2> show protection-group ethernet-ring aps
Ethernet Ring Name Request/state No Flush Ring Protection Link Blocked
pg102
NR
No
Yes
Originator
No
Remote Node ID
00:01:01:00:00:01
770
Control Channel
ge-1/2/1.1
ge-1/0/2.1
Forward State
forwarding
forwarding
Note that both interfaces are forwarding. Router 3 will see almost identical information.
user@router2> show protection-group ethernet-ring node-state
Ethernet ring
APS State
Event
Ring Protection Link Owner
pg102
idle
NR-RB
No
Restore Timer
disabled
Note that Router 2 is not the owner. Router 3 will see almost identical information.
user@router2> show protection-group ethernet-ring statistics group-name pg102
Ethernet Ring statistics for PG pg102
RAPS sent
: 0
RAPS received
: 1
Local SF happened:
: 0
Remote SF happened:
: 0
NR event happened:
: 0
NR-RB event happened:
: 1
Related
Documentation
Example: Configuring Ethernet Ring Protection for MX Series Routers on page 746
Example: Viewing Ethernet Ring Protection StatusRing Failure Condition on page 771
Remote Node ID
00:01:02:00:00:01
Note that the ring protection link is no longer blocked and the node is no longer marked
as originator.
user@router1> show protection-group ethernet-ring interface
Ethernet ring port parameters for protection group pg101
Interface
ge-1/0/1
Control Channel
ge-1/0/1.1
Forward State
forwarding
771
ge-1/2/4
ge-1/2/4.1
Signal Failure
Clear
Clear
forwarding
No
Admin State
IFF ready
IFF ready
Note that the protection interface is now forwarding (so is the other interface).
user@router1> show protection-group ethernet-ring node-state
how protection-group ethernet-ring node-state
Ethernet ring
APS State
Event
Ring Protection Link Owner
pg101
protected
SF
Yes
Restore Timer
disabled
Quard Timer
disabled
Operation state
operational
Note that the R-APS messages have recorded the remote failure.
Under a failure condition, the other routers on the ring (Router 2 and Router 3) will see
the following similar output:
Router 2 and Router 3 Operational Commands (Failure Condition)
user@router2> show protection-group ethernet-ring aps
Ethernet Ring Name Request/state No Flush Ring Protection Link Blocked
pg102
SF
No
No
Originator
Yes
Remote Node ID
00:00:00:00:00:00
Note the failure event (SF). Router 3 will see almost identical information.
user@router2> show protection-group ethernet-ring interface
Ethernet ring port parameters for protection group pg102
Interface
ge-1/2/1
ge-1/0/2
Control Channel
ge-1/2/1.1
ge-1/0/2.1
Signal Failure
Clear
set
Forward State
forwarding
discarding
Admin State
IFF ready
IFF ready
Note that the failed interface (ge-1/0/2.1) is not forwarding. Router 3 will see almost
identical information.
user@router2> show protection-group ethernet-ring node-state
Ethernet ring
APS State
Event
Ring Protection Link Owner
pg102
idle
NR-RB
No
772
Restore Timer
disabled
Quard Timer
disabled
Operation state
operational
Note that Router 2 is not the owner. Router 3 will see almost identical information.
user@router2> show protection-group ethernet-ring statistics group-name pg102
Ethernet Ring statistics for PG pg102
RAPS sent
: 1
RAPS received
: 1
Local SF happened:
: 1
Remote SF happened:
: 0
NR event happened:
: 0
NR-RB event happened:
: 1
Note that the R-APS messages have recorded the remote failure. Router 3 will see almost
identical information.
Related
Documentation
Example: Configuring Ethernet Ring Protection for MX Series Routers on page 746
Example: Viewing Ethernet Ring Protection StatusNormal Ring Operation on page 769
773
774
PART 4
Troubleshooting Information
775
776
CHAPTER 35
Locating the Fast Ethernet and Gigabit Ethernet LINK Alarm and Counters on page 803
777
Link Layer packets, you can assume that the problem is on one of the segments between
the local router and the remote routers interface card. In this case, the next
troubleshooting step is to configure a line loopback closer to the local router to find the
source of the problem.
The following types of loopback testing are supported by Junos OS:
DCE localLoops packets back on the local data circuit-terminating equipment (DCE).
PayloadUseful for troubleshooting the physical circuit problems between the local
router and the remote router. A payload loopback loops data only (without clocking
information) on the remote routers PIC. With payload loopback, overhead is
recalculated.
RemoteUseful for troubleshooting the physical circuit problems between the local
router and the remote router. A remote loopback loops packets, including both data
and timing information, back on the remote routers interface card. A router at one end
of the circuit initiates a remote loopback toward its remote partner. When you configure
a remote loopback, the packets received from the physical circuit and CSU are received
by the interface. Those packets are then retransmitted by the PIC back toward the
CSU and the circuit. This loopback tests all the intermediate transmission segments.
Table 66 on page 778 shows the loopback modes supported on the various interface
types.
778
Interface
Loopback Modes
Usage Guidelines
Aggregated Ethernet,
Fast Ethernet, Gigabit
Ethernet
Local
Circuit Emulation E1
Circuit Emulation T1
E1 and E3
Loopback Modes
Usage Guidelines
NxDS0
Payload
Serial (EIA-530)
SONET/SDH
T1 and T3
BERT Testing
A bit error rate test (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; and the channelized DS3 IQ, E1 IQ, and OC12 IQ interfaces.
779
A BERT test requires a line loop to be in place on either the transmission devices or the
far-end router. The local router generates a known bit pattern and sends it out the transmit
path. The received pattern is then verified against the sent pattern. The higher the bit
error rate of the received pattern, the worse the noise is on the physical circuit. As you
move the position of the line loop increasingly downstream toward the far-end router,
you can isolate the troubled portion of the link.
To configure BERT, you must configure the duration of the test, the bit pattern to send
on the transmit path, and the error rate to monitor when the inbound pattern is received.
To configure the duration of the test, the pattern to send in the bit stream, and the error
rate to include in the bit stream, include the bert-period, bert-algorithm, and bert-error-rate
statements, respectively, at the [edit interfaces interface-name interface-type-options]
hierarchy level:
[edit interfaces interface-name interface-type-options]
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
By default, the BERT period is 10 seconds. You can configure the BERT period to last
from 1 through 239 seconds on some PICs and from 1 through 240 seconds on other PICs.
rate is the bit error rate. This can be an integer from 0 through 7, which corresponds to a
0
algorithm is the pattern to send in the bit stream. For a list of supported algorithms, enter
is
is
is
is
2^11
2^15
2^20
2^20
Pattern
Pattern
Pattern
Pattern
is
is
is
is
2^11
2^15
2^20
2^23
When you issue the help command from the CLI, all BERT algorithm options
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in system log messages.
780
NOTE: The 12-port T1/E1 Circuit Emulation (CE) PIC supports only the
following algorithms:
all-ones-repeating
Repeating one bits
all-zeros-repeating Repeating zero bits
alternating-double-ones-zeros Alternating pairs of ones and zeros
alternating-ones-zeros Alternating ones and zeros
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-2e7
Pattern is 2^7 - 1
pseudo-2e9-o153
Pattern is 2^9 - 1 (per O.153 standard)
repeating-1-in-4
1 bit in 4 is set
repeating-1-in-8
1 bit in 8 is set
repeating-3-in-24
3 bits in 24 are set
When you issue the help command from the CLI, all BERT algorithm options
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in system log messages.
When you issue the help command from the CLI, all BERT algorithm options
are displayed, regardless of the PIC type, and no commit check is available.
Unsupported patterns for a PIC type can be viewed in system log messages.
781
Table 67 on page 782 shows the BERT capabilities for various interface types.
T1 BERT
T3 BERT
Comments
12-port T1/E1
Circuit Emulation
Limited algorithms
4-port
Channelized
OC3/STM1
Circuit Emulation
Limited algorithms
E1 or T1
Limited algorithms
E3 or T3
Channelized
OC12
Yes (channel
011)
Limited algorithms
No bit count
Multiple channels
No error insert
No bit count
Channelized
STM1
Channelized T3
and Multichannel
T3
782
Yes (channel
062)
Yes (channel
027)
Yes (port 03 on
channel 0)
These limitations do not apply to channelized IQ interfaces. For information about BERT
capabilities on channelized IQ interfaces, see Channelized IQ and IQE Interfaces Properties.
After you configure the BERT properties and commit the configuration, begin the test by
issuing the test interface interface-name interface-type-bert-start operational mode
command:
user@host> test interface interface-name interface-type-bert-start
The test runs for the duration you specify with the bert-period statement. If you want to
terminate the test sooner, issue the test interface interface-name interface-type-bert-stop
command:
user@host> test interface interface-name interface-type-bert-stop
For example:
user@host> test interface t3-1/2/0 t3-bert-start
user@host> test interface t3-1/2/0 t3-bert-stop
To view the results of the BERT test, issue the show interfaces extensive | find BERT
command:
user@host> show interfaces interface-name extensive | find BERT
For more information about running and evaluating the results of the BERT procedure,
see the CLI Explorer.
783
}
}
Checklist for Monitoring Fast Ethernet and Gigabit Ethernet Interfaces on page 784
Action
To monitor Fast Ethernet and Gigabit Ethernet interfaces and begin the process of isolating
interface problems when they occur.
Table 68 on page 784 provides links and commands for monitoring Fast Ethernet and
Gigabit Ethernet interfaces.
Table 68: Checklist for Monitoring Fast Ethernet and Gigabit Ethernet
Interfaces
Tasks
Command or Action
Meaning
You can use the above described commands to monitor and to display the configurations
for Fast Ethernet and Gigabit Ethernet interfaces.
784
4. Display Extensive Status Information for a Specific Fast Ethernet or Gigabit Ethernet
Action
To display the status of Fast Ethernet interfaces, use the following Junos OS
command-line interface (CLI) operational mode command:
user@host> show interfaces terse (fe* | ge*)
Sample Output
user@host> show interfaces terse fe*
Interface
Admin Link Proto
fe-2/1/0
up
up
fe-2/1/0.0
up
up
inet
fe-3/0/2
up
down
fe-3/0/2.0
up
down
fe-3/0/3
up
up
fe-3/0/3.0
up
up
inet
fe-4/1/0
down up
fe-4/1/0.0
up
down inet
fe-4/1/1
up
up
fe-4/1/1.0
up
up
inet
fe-4/1/2
up
down
fe-4/1/2.0
up
down
Meaning
Local
Remote
10.116.115.217/29
192.168.223.65/30
10.150.59.133/30
10.150.59.129/30
The sample output lists only the Fast Ethernet interfaces. It shows the status of both the
physical and logical interfaces. For a description of what the output means, see
Table 69 on page 785.
Logical
Interface
fe-2/1/0
fe-2/1/0.0
Admin Up
Admin Up
Link Up
Link Up
fe-3/0/2
fe-3/0/2.0
Admin Up
Admin Up
Link Down
Link Down
fe-4/1/0
fe-4/1/0.0
Admin Down
Admin Up
Link Up
Link Down
Status Description
This interface has both the physical and logical links up
and running.
This interface has the physical link down, the link layer
down, or both down (Link Down). The logical link is also
down as a result.
785
Logical
Interface
Status Description
fe-4/1/2
fe-4/1/2.0
This interface has both the physical and logical links down.
Admin Up
Admin Up
Link Down
Link Down
To display the status of Gigabit Ethernet interfaces, use the following Junos OS
command-line interface (CLI) operational mode command:
Meaning
Local
Remote
65.113.23.105/30
65.115.56.57/30
65.115.56.193/30
This sample output lists only the Gigabit Ethernet interfaces. It shows the status of both
the physical and logical interfaces. See Table 70 on page 786 for a description of what
the output means.
786
Physical
Interface
Logical
Interface
ge-2/2/0
ge-2/2/0.0
Admin Down
Admin Up
Link Down
Link Down
ge-2/3/0
ge-2/3/0.0
Admin Up
Admin Up
Link Up
Link Up
ge-3/2/0
ge-3/2/0.0
Admin Up
Admin Up
Link Down
Link Down
Status Description
This interface is administratively disabled (Admin Down).
Both the physical and logical links are down (Link Down).
This interface has both the physical link and the logical
interface down.
Action
To display the status of a specific Fast Ethernet or Gigabit Ethernet interface when you
need to investigate its status further, use the following Junos OS CLI operational mode
command:
user@host> show interfaces (fe-fpc/pic/port | ge-fpc/pic/port)
Sample Output 1
The following sample output is for a Fast Ethernet interface with the physical link up:
user@host> show interfaces fe-2/1/0
Physical interface: fe-2/1/0, Enabled, Physical link is Up
Interface index: 31, SNMP ifIndex: 35
Description: customer connection
Link-level type: Ethernet, MTU: 1514, Source filtering: Disabled
Speed: 100mbps, Loopback: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps
Link flags
: None
Current address: 00:90:69:86:71:1b, Hardware address: 00:90:69:86:71:1b
Input rate
: 25768 bps (11 pps), Output rate: 1576 bps (3 pps)
Active alarms : None
Active defects : None
Logical interface fe-2/1/0.0 (Index 2) (SNMP ifIndex 43)
Flags: SNMP-Traps, Encapsulation: ENET2
Protocol inet, MTU: 1500, Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.116.151.218/29, Local: 10.119.115.217
Broadcast: 10.116.151.225
Sample Output 2
The following output is for a Gigabit Ethernet interface with the physical link up:
user@host> show interfaces ge-3/1/0
Physical interface: ge-3/1/0, Enabled, Physical link is Up
Interface index: 41, SNMP ifIndex: 55
Description: customer connection
Link-level type: Ethernet, MTU: 1514, Source filtering: Disabled
Speed: 1000mbps, Loopback: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps
Link flags
: None
Current address: 00:90:69:85:71:99, Hardware address: 00:90:69:85:71:99
Input rate
: 7412216 bps (1614 pps), Output rate: 2431184 bps (1776 pps)
Active alarms : None
Active defects : None
Logical interface ge-3/1/0.0 (Index 11) (SNMP ifIndex 57)
Flags: SNMP-Traps, Encapsulation: ENET2
Protocol inet, MTU: 1500
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.117.65.192/30, Local: 10.115.65.193
Broadcast: 10.115.65.195
Meaning
The first line of sample output 1 and 2 shows that the physical link is up. This means that
the physical link is healthy and can pass packets. Further down the sample output, look
787
for active alarms and defects. If you see active alarms or defects, to further diagnose the
problem, see Step 3, Display Extensive Status Information for a Specific Fast Ethernet
or Gigabit Ethernet Interface on page 788, to display more extensive information about
the Fast Ethernet interface and the physical interface that is down.
Action
To display extensive status information about a specific Fast Ethernet or Gigabit Ethernet
interface, use the following Junos OS CLI operational mode command:
user@host> show interfaces (fe-fpc/pic/port | ge-fpc/pic/port) extensive
Sample Output
The following sample output is for a Fast Ethernet interface:
user@router> show interfaces fe-1/3/3 extensive
Physical interface: fe-1/3/3, Enabled, Physical link is Up
Interface index: 47, SNMP ifIndex: 38
Description: Test
Link-level type: Ethernet, MTU: 1514, Source filtering: Disabled
Speed: 100mbps, Loopback: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps
Link flags
: None
Current address: 00:90:69:8d:2c:de, Hardware address: 00:90:69:8d:2c:de
Statistics last cleared: 2002-01-11 23:03:09 UTC (1w2d 23:54 ago)
Traffic statistics:
Input bytes :
373012658
0 bps
Output bytes :
153026154
1392 bps
Input packets:
1362858
0 pps
Output packets:
1642918
3 pps
Input errors:
Errors: 0 , Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 503660
L3 incompletes: 1 , L2 channel errors: 0 , L2 mismatch timeouts: 0
FIFO errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Collisions: 0, Drops: 0, Aged packets: 0
HS link CRC errors: 0, FIFO errors: 0
Active alarms : None
Active defects : None
MAC statistics:
Receive
Transmit
Total octets
439703575
177452093
Total packets
1866532
1642916
Unicast packets
972137
1602563
Broadcast packets
30
2980
Multicast packets
894365
37373
CRC/Align errors
0
0
FIFO errors
0
0
MAC control frames
0
0
MAC pause frames
0
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
1866532
788
Meaning
The sample output shows where the errors might be occurring and includes
autonegotiation information. See Table 71 on page 789 for a description of errors to look
for.
Meaning
Policed discards
L2 channel errors
Packets for which the router could not find a valid logical interface. For example, the packet is for
a virtual LAN (VLAN) that is not configured on the interface.
MTU
The maximum transmission unit (MTU) must match the interface of either the router at the remote
end of the Fast Ethernet or Gigabit Ethernet link, or that of the switch.
Input DA rejects
Number of packets with a destination Media Access Control (MAC) address that is not on the
accept list. It is normal to see this number increment.
Input SA rejects
Number of packets with a source MAC address that is not on the accept list. This number only
increments when source MAC address filtering is configured.
If the physical link is down, look at the active alarms and defects for the Fast Ethernet or
Gigabit Ethernet interface and diagnose the Fast Ethernet or Gigabit Ethernet media
accordingly. See Checklist for Locating Fast Ethernet and Gigabit Ethernet Alarms and
Counters on page 803 for an explanation of Fast Ethernet and Gigabit Ethernet alarms.
Table 72 on page 790 lists and describes some MAC statistics errors to look for.
789
Meaning
CRC/Align errors
The total number of packets received that had a length (excluding framing bits, but including
FCS octets) of between 64 and 1518 octets, inclusive, but had either a bad FCS with an integral
number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
Jabber frames
The total number of packets received that were longer than 1518 octets (excluding framing bits,
but including FCS octets), and had either an FCS error or an alignment error.
Note that this definition of jabber is different from the definition in IEEE-802.3 section 8.2.1.5
(10BASE5) and section 10.3.1.4 (10BASE2). These documents define jabber as the condition
where any packet exceeds 20 ms. The allowed range to detect jabber is between 20 ms and 150
ms.
The total number of packets received that were less than 64 octets in length (excluding framing
bits, but including FCS octets), and had either an FCS error an alignment error.
Fragment frames
Note that it is entirely normal for fragment frames to increment because both runts (which are
normal occurrences due to collisions) and noise hits are counted.
Explanation
The Negotiation status field shows Incomplete when the Ethernet interface has the
speed or link mode configured.
The Negotiation status field shows No autonegotiation when the remote Ethernet
interface has the speed or link mode configured, or does not perform autonegotiation.
The Negotiation status field shows Complete and the Link partner field shows OK when
the Ethernet interface is connected to a device that performs autonegotiation and the
autonegotiation process completes successfully.
The Link partner field can be Full-duplex or Half-duplex depending on the capability of
the attached Ethernet device.
The Flow control field displays the types of flow control supported by the remote Ethernet
device.
790
Action
To monitor statistics for a Fast Ethernet or Gigabit Ethernet interface, use the following
Junos OS CLI operational mode command:
user@host> monitor interface (fe-fpc/pic/port | ge-fpc/pic/port)
Sample Output
The following sample output is for a Fast Ethernet interface:
user@host> monitor interface fe-2/1/0
Interface: fe-2/1/0, Enabled, Link is Up
Encapsulation: Ethernet, Speed: 100mbps
Traffic statistics:
Input bytes:
282556864218
Output bytes:
42320313078
Input packets:
739373897
Output packets:
124798688
Error statistics:
Input errors:
0
Input drops:
0
Input framing errors:
0
Policed discards:
6625892
L3 incompletes:
75
L2 channel errors:
0
L2 mismatch timeouts:
0
Carrier transitions:
1
Output errors:
0
Output drops:
0
Aged packets:
0
Active alarms : None
Active defects: None
Input MAC/Filter statistics:
Unicast packets
464751787
Packet error count
0
Meaning
(14208 bps)
(384 bps)
(11 pps)
(1 pps)
Current Delta
[40815]
[890]
[145]
[14]
[0]
[0]
[0]
[6]
[0]
[0]
[0]
[0]
[0]
[0]
[0]
[154]
[0]
Use the information from this command to help narrow down possible causes of an
interface problem.
NOTE: If you are accessing the router from the console connection, make
sure you set the CLI terminal type using the set cli terminal command.
791
The statistics in the second column are the cumulative statistics since the last time they
were cleared using the clear interfaces statistics interface-name command. The statistics
in the third column are the cumulative statistics since the monitor interface interface-name
command was executed.
If the input errors are increasing, verify the following:
1.
Check the cabling to the router and have the carrier verify the integrity of the line. To
verify the integrity of the cabling, make sure that you have the correct cables for the
interface port. Make sure you have single-mode fiber cable for a single-mode interface
and multimode fiber cable for a multimode interface.
2. For a fiber-optic connection, measure the received light level at the receiver end and
make sure that it is within the receiver specification of the Ethernet interface. See
Fiber-Optic Ethernet Interface Specifications on page 792 for the fiber-optic Ethernet
interface specifications.
3. Measure the transmit light level on the Tx port to verify that it is within specification.
See Fiber-Optic Ethernet Interface Specifications on page 792 for the optical
specifications.
Average
Launch Power
Receiver
Saturation
Receiver
Sensitivity
1480 to 1580
nm
-3 to +2 dBm
-3 dBm
1270 to 1355 nm
-11 to -3 dBm
-3 dBm
-19 dBm
830 to 860 nm
-9.5 to -4 dBm
-3 dBm
-17 dBm
Length
Wavelength
LH optical interface
LX optical interface
Gigabit Ethernet
Duplex SC connector
792
Wavelength
Average
Launch Power
Receiver
Saturation
Receiver
Sensitivity
1270 to 1380 nm
-14 dBm
-34 dBm
FX optical interface
with MT-RJ connector
Length
Performing Loopback Testing for Fast Ethernet and Gigabit Ethernet Interfaces
Checklist for Using Loopback Testing for Fast Ethernet and Gigabit Ethernet
Interfaces on page 793
Verify That the Fast Ethernet or Gigabit Ethernet Interface Is Up on page 797
Check for Fast Ethernet or Gigabit Ethernet Interface Error Statistics on page 801
Checklist for Using Loopback Testing for Fast Ethernet and Gigabit Ethernet Interfaces
Purpose
Action
To use loopback testing to isolate Fast Ethernet and Gigabit Ethernet interface problems.
Table 75 on page 793 provides links and commands for using loopback testing for Fast
Ethernet and Gigabit Ethernet interfaces.
Table 75: Checklist for Using Loopback Testing for Fast Ethernet and
Gigabit Ethernet Interfaces
Tasks
Command or Action
Diagnose a Suspected Hardware Problem with a Fast Ethernet or Gigabit Ethernet Interface on page 794
1.
793
Table 75: Checklist for Using Loopback Testing for Fast Ethernet and
Gigabit Ethernet Interfaces (continued)
Tasks
Command or Action
Diagnose a Suspected Hardware Problem with a Fast Ethernet or Gigabit Ethernet Interface
Problem
Description: When you suspect a hardware problem, take the following steps to help
verify if there is a problem.
Solution
To diagnose a suspected hardware problem with the Ethernet interface, follow these
steps:
Verify That the Fast Ethernet or Gigabit Ethernet Interface Is Up on page 797
Check for Fast Ethernet or Gigabit Ethernet Interface Error Statistics on page 801
Create a Loopback
You can create a physical loopback or configure a local loopback to help diagnose a
suspected hardware problem. Creating a physical loopback is recommended because
it allows you to test and verify the transmit and receive ports. If a field engineer is not
794
available to create the physical loopback, you can configure a local loopback for the
interface. The local loopback creates a loopback internally in the Physical Interface Card
(PIC).
1.
NOTE: Make sure you use single-mode fiber for a single-mode port and
multimode fiber for a multimode port.
Meaning
When you create and then test a physical loopback, you are testing the transmit and
receive ports of the PIC. This action is recommended if a field engineer is available to
create the physical loop as it provides a more complete test of the PIC.
An RJ-45 connector
A crimping tool
Figure 51 on page 796 illustrates how to create a loopback plug for an RJ-45 Ethernet
interface.
795
Meaning
When you create and then test a physical loopback, you are testing the RJ-45 interface
of the PIC. This action is recommended if a field engineer is available to create the physical
loop as it provides a more complete test of the PIC.
user@host# show
For example:
[edit interfaces fe-1/0/0 fastether-options]
user@host# show
loopback;
4. Commit the change:
user@host# commit
For example:
[edit interfaces fe-1/0/0 fastether-options]
user@host# commit
commit complete
796
When you create a local loopback, you create an internal loop on the interface being
tested. A local loopback loops the traffic internally on that PIC. A local loopback tests
the interconnection of the PIC but does not test the transmit and receive ports. On an
Ethernet interface, you cannot create a remote loopback, therefore there is no option to
use a local or remote statement. Simply including the loopback statement at the [edit
interfaces interface-name (fastether-options | gigether-options] hierarchy level, places
the interface into local loopback mode.
Action
Display the status of the Fast Ethernet or Gigabit Ethernet interface to provide the
information you need to determine whether the physical link is up or down.
To verify that the status of the Fast Ethernet or Gigabit Ethernet interface is up, use the
following Junos OS command-line interface (CLI) operational mode command:
user@host> show interfaces (fe-fpc/port | ge-fpc/pic/port)
Sample Output
user@host# show interfaces fe-1/3/0
Physical interface: fe-1/3/0, Enabled, Physical link is Up
Interface index: 44, SNMP ifIndex: 35
Link-level type: Ethernet, MTU: 1514, Source filtering: Disabled
Speed: 100mbps, Loopback: Disabled , Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps
Link flags
: None
Current address: 00:90:69:8d:2c:db, Hardware address: 00:90:69:8d:2c:db
Input rate
: 0 bps (0 pps), Output rate: 0 bps (0 pps)
Active alarms : None
Active defects : None
MAC statistics:
Input octets: 0, Input packets: 0, Output octets: 0, Output packets: 0
Filter statistics:
Filtered packets: 0, Padded packets: 0, Output packet errors: 0
Autonegotiation information:
Negotiation status: Incomplete, Link partner status: OK
Link partner: Full-duplex, Flow control: None
Meaning
The sample output shows that the link is up and there are no alarms in this loopback
configuration. When an internal loopback is configured, the physical loopback should
come up without an alarm.
Sample Output
When you see that the physical link is down, there may be a problem with the port. The
following output is an example of the show interfaces fe-fpc/pic/port command when
the physical link is down:
797
Meaning
The sample output shows that the physical link is down and there are active alarms and
defects.
Table 76 on page 798 presents problem situations and actions for a physical link that is
down.
Table 76: Problems and Solutions for a Physical Link That Is Down
Problem
Action
Cable mismatch
Verify that the fiber can successfully loop a known good port of the same type.
Verify that the attenuation is correct per the PIC optical specifications.
Verify that the Tx power of the optics is within range of the PIC optical specification.
Verify that a single-mode fiber cable is connected to a single-mode interface and that
a multimode fiber cable is connected to a multimode interface. (This problem does
not always cause the physical link to go down; errors and dropped packets are
sometimes the result.)
798
NOTE: Remove the static ARP entry at the end of the loop test after you have
completed the ping test, checked interface statistics, and monitored interface
traffic.
Action
To configure a static ARP table entry for a Gigabit Ethernet interface, follow these steps.
You can follow the same procedure to configure a static ARP entry for a Fast Ethernet
interface.
1.
Find the Media Access Control (MAC) address for the Gigabit Ethernet interface:
user@host> show interfaces ge-fpc/pic/port
[edit]
user@host# edit interfaces interface-name unit logical-unit-number family inet address
address
3. Configure the static ARP entry:
NOTE: The MAC address used should be the same as the physical address
of the port being tested because this allows the port to receive the frames
when you run the ping test.
user@host# show
5. Commit the configuration:
user@host# commit
6. Verify that the static ARP entry is installed:
Sample Output
user@host> show interfaces ge-7/2/1
Physical interface: ge-7/2/1, Enabled, Physical link is Down
Interface index: 44, SNMP ifIndex: 35
Link-level type: Ethernet, MTU: 1514, Source filtering: Disabled
Speed: 100mbps, Loopback: Disabled, Flow control: Enabled
Device flags
: Present Running Down
Interface flags: Hardware-Down SNMP-Traps
Link flags
: None
Current address: 00:90:69:8d:2c:db, Hardware address: 00:90:69:8d:2c:db
Input rate
: 0 bps (0 pps), Output rate: 0 bps (0 pps)
[edit interfaces ge-7/2/1 unit 0 family inet address 10.108.120.1/30]
user@host# set arp 10.108.120.2 mac 00:90:69:8d:2c:db
[edit interfaces ge-7/2/1 unit 0 family inet address 10.108.120.1/30]
799
user@host# show
arp 10.108.120.2 mac 00:90:69:8d:2c:db;
[edit interfaces ge-7/2/1 unit 0 family inet address 10.108.120.1/30]
user@host# commit
commit complete
[edit interfaces ge-7/2/1 unit 0 family inet address 10.108.120.1/30]
user@host# run show arp no-resolve
MAC Address
Address
00:90:69:8d:2c:db 10.108.120.2
00:e0:34:bb:8c:40 209.211.135.1
00:a0:a5:28:0c:70 209.211.135.8
00:a0:a5:12:12:c7 209.211.135.10
00:90:ab:3c:68:a0 209.211.135.31
08:00:20:a1:53:15 209.211.135.65
00:a0:cc:66:3e:85 209.211.135.98
Total entries: 7
Interface
ge-7/2/1.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
fxp0.0
Flags
permanent
none
none
none
none
none
none
Meaning
The sample output is for Step 1 through Step 6 and shows that a static ARP entry was
configured on Gigabit Ethernet interface ge-7/2/1. The MAC address used is the same as
the physical address of the port being tested because this allows the port to receive the
frames when you run the ping test. The port is working as expected if you see that the
time to live (TTL) expired; if you do not receive a response to your ping test, it indicates
a hardware problem.
Sample Output
user@host> clear interfaces statistics ge-7/2/0
user@host>
Meaning
This command clears the interface statistics counters for the Gigabit Ethernet interface
only.
800
Action
To send ping packets from the Ethernet interface, use the following Junos OS CLI
operational mode command:
user@host> ping remote-IP-address bypass-routing interface (fe-fpc/pic/port |
ge-fpc/pic/port) count 100 rapid
Sample Output
user@router> ping 10.108.120.2 bypass-routing interface ge-7/2/1 count 100 rapid
PING 10.108.120.2 (10.108.120.2): 56 data bytes
36 bytes from 10.108.120.1: Time to live exceeded
Vr HL TOS Len
ID Flg off TTL Pro cks
Src
Dst
4 5 00 0054 e871
0 0000 01 01 cc5c 10.108.120.1 10.108.120.2
.36 bytes from 10.108.120.1: Time to live exceeded
Vr HL TOS Len
ID Flg off TTL Pro cks
Src
Dst
4 5 00 0054 e874
0 0000 01 01 cc59 10.108.120.1 10.108.120.2
.36 bytes from 10.108.120.1: Time to live exceeded
Vr HL TOS Len
ID Flg off TTL Pro cks
Src
Dst
4 5 00 0054 e878
0 0000 01 01 cc55 10.108.120.1 10.108.120.2
.36 bytes from 10.108.120.1: Time to live exceeded
Vr HL TOS Len
ID Flg off TTL Pro cks
Src
Dst
4 5 00 0054 e87c
0 0000 01 01 cc51 10.108.120.1 10.108.120.2
.36 bytes from 10.108.120.1: Time to live exceeded
Vr HL TOS Len
ID Flg off TTL Pro cks
Src
Dst
4 5 00 0054 e880
0 0000 01 01 cc4d 10.108.120.1 10.108.120.2
.36 bytes from 10.108.120.1: Time to live exceeded
Vr HL TOS Len
ID Flg off TTL Pro cks
Src
Dst
4 5 00 0054 e884
0 0000 01 01 cc49 10.108.120.1 10.108.120.2
.36 bytes from 10.108.120.1: Time to live exceeded
Meaning
The sample output shows that the time to live (TTL) expired, indicating that the link is
receiving the frames from the ping test. The MAC address used is the same as the physical
address of the port being tested because this allows the port to accept the frames from
the ping test. As the packet is looped over the link, you expect to receive a TLL exceeded
message for each ping sent. These messages are generated because the ping packets
are repeatedly looped between the router and the physical loopback. When the packet
is sent to the other end of the link, which does not exist, the loopback returns the packet
back to the same interface, where it is again subjected to the Packet Forwarding Engine
fabric for routing. After the route lookup, the TTL is decremented, and the packet is again
sent out of the looped interface. This process repeats until the packed is either lost, or
the TLL expires with subsequent TTL expired message displayed. Should any errors occur,
the packet is discarded and a time-out error is displayed, rather than the expected TTL
expired message. Note that the default TTL for ICMP echo packets in Junos OS is 64.
This means a given test packet must be successfully sent and received 63 times before
a TTL expired message can be generated. You can alter the TTL value to adjust the
tolerance for loss, for example, a value of 255 is the most demanding test because now
the packet must be sent and received error free 254 times.
Persistent interface error statistics indicate that you need to open a case with the Juniper
Networks Technical Assistance Center (JTAC).
Action
To check the local interface for error statistics, use the following Junos OS CLI operational
mode command:
801
Sample Output
user@router> show interfaces ge-7/2/1 extensive
Physical interface: ge-7/2/1, Enabled, Physical link is Up
Interface index: 25, SNMP ifIndex: 32, Generation: 41
Description: Test
Link-level type: Ethernet, MTU: 4470, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Disabled
Device flags
: Present Running
Interface flags: SNMP-Traps
Link flags
: None
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:90:69:4c:17:b1, Hardware address: 00:90:69:4c:17:b1
Statistics last cleared: 2002-01-07 17:53:19 UTC (2w2d 03:20 ago)
Traffic statistics:
Input bytes :
3799515503823
0 bps
Output bytes :
7325566425
0 bps
Input packets:
4628009535
0 pps
Output packets:
30678225
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3
incompletes: 0,
L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0
Output errors:
Carrier transitions: 14, Errors: 0, Drops: 0, Collisions: 0, Aged packets:
0,
FIFO errors: 0, HS link CRC errors: 0
Active alarms : None
Active defects : None
MAC statistics:
Receive
Transmit
Total octets
3883579444813
7880356346
Total packets
4628009534
30678237
Unicast packets
4627879788
29893563
Broadcast packets
30
464
Multicast packets
129716
784210
CRC/Align errors
0
0
FIFO errors
0
0
MAC control frames
0
0
MAC pause frames
0
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
4628009244
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
30678237
Output packet pad count
856248
Output packet error count
0
CAM destination filters: 9, CAM source filters: 0
Autonegotiation information:
Negotiation status: Complete, Link partner status: Ok, Link partner:
Full-duplex,
Flow control: None
PFE configuration:
Destination slot: 7
CoS transmit queue
Bandwidth
Buffer
Priority
Limit
802
%
bps
%
bytes
0 best-effort
0
0
0
0
low
none
1 expedited-forwarding
0
0
0
0
low
none
2 assured-forwarding
0
0
0
0
low
none
3 network-control
0
0
0
0
low
none
Logical interface ge-7/2/1.0 (Index 23) (SNMP ifIndex 48) (Generation 38)
Description: To Cosine Left 23/1
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 4456, Flags: None, Generation: 85 Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.108.120.0/30, Local: 10.108.120.1, Broadcast: 10.108.120.3,
Generation: 81
Protocol iso, MTU: 4453, Flags: None, Generation: 86 Route table: 0
Meaning
Check for any error statistics. There should not be any input or output errors. If there are
any persistent input or output errors, open a case with the Juniper Networks Technical
Assistance Center (JTAC) at support@juniper.net, or at 1-888-314-JTAC (within the United
States) or 1-408-745-9500 (from outside the United States).
Action
When you suspect a circuit problem, it is important to work with the transport-layer
engineer to resolve the problem. The transport-layer engineer may create a loop to the
router from various points in the network. You can then perform tests to verify the
connection from the router to that loopback in the network.
After the transport-layer engineer has created the loop to the router from the network,
you must verify the connection from the router to the loopback in the network. Follow
Step 2 through Step 8 in Diagnose a Suspected Hardware Problem with a Fast Ethernet
or Gigabit Ethernet Interface on page 794. Keep in mind that any problems encountered
in the test indicate a problem with the connection from the router to the loopback in the
network.
By performing tests to loopbacks at various points in the network, you can isolate the
source of the problem.
Locating the Fast Ethernet and Gigabit Ethernet LINK Alarm and Counters
Checklist for Locating Fast Ethernet and Gigabit Ethernet Alarms and
Counters on page 803
Display the Fast Ethernet or Gigabit Ethernet Interface LINK Alarm on page 804
Checklist for Locating Fast Ethernet and Gigabit Ethernet Alarms and Counters
Purpose
Action
To locate LINK alarm and major counters associated with Fast Ethernet and Gigabit
Ethernet interfaces.
Table 77 on page 804 provides links and commands for locating LINK alarm and major
counters for Fast Ethernet and Gigabit Ethernet interfaces.
803
Table 77: Checklist for Locating Fast Ethernet and Gigabit Ethernet Alarms
and Counters
Tasks
Command or Action
Solution
Description: To display the Fast Ethernet or Gigabit Ethernet LINK alarm, use the following
Junos OS command-line interface (CLI) operational mode command:
Sample Output
The following sample output is for a Fast Ethernet interface:
user@host> show interfaces fe-1/3/3 extensive
Physical interface: fe-1/3/3, Enabled, Physical link is Down
Interface index: 47, SNMP ifIndex: 38
Description: Test
Link-level type: Ethernet, MTU: 1514, Source filtering: Disabled
Speed: 100mbps, Loopback: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps
Link flags
: None
Current address: 00:90:69:8d:2c:de, Hardware address: 00:90:69:8d:2c:de
Statistics last cleared: 2002-01-11 23:03:09 UTC (1w2d 23:54 ago)
Traffic statistics:
Input bytes :
373012658
0 bps
Output bytes :
153026154
1392 bps
Input packets:
1362858
0 pps
Output packets:
1642918
3 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 503660
L3 incompletes: 1 , L2 channel errors: 0, L2 mismatch timeouts: 0
FIFO errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Collisions: 0, Drops: 0, Aged packets: 0
HS link CRC errors: 0, FIFO errors: 0
Active alarms : LINK
Active defects : LINK
MAC statistics:
Receive
Transmit
Total octets
439703575
177452093
Total packets
1866532
1642916
Unicast packets
972137
1602563
Broadcast packets
30
2980
Multicast packets
894365
37373
CRC/Align errors
0
0
FIFO errors
0
0
MAC control frames
0
0
MAC pause frames
0
0
Oversized frames
0
Jabber frames
0
804
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
1866532
Input packet rejects
0
Input DA rejects
503674
Input SA rejects
0
Output packet count
1642916
Output packet pad count
0
Output packet error count
0
CAM destination filters: 5, CAM source filters: 0
Autonegotiation information:
Negotiation status: Complete, Link partner status: OK
Link partner: Full-duplex, Flow control: None
PFE configuration:
Destination slot: 1, Stream number: 15
CoS transmit queue bandwidth:
Queue0: 95, Queue1: 0, Queue2: 0, Queue3: 5
CoS weighted round-robin:
Queue0: 95, Queue1: 0, Queue2: 0, Queue3: 5
Logical interface fe-1/3/3.0 (Index 8) (SNMP ifIndex 69)
Description: Test
Flags: SNMP-Traps, Encapsulation: ENET2
Protocol inet, MTU: 1500, Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.115.107.192/29, Local: 10.115.107.193
Broadcast: 10.115.107.199
Meaning
The sample output shows where the alarm and other errors might be occurring and any
counters that are incrementing. The only alarm associated with Fast Ethernet or Gigabit
Ethernet interfaces is the LINK alarm. A LINK alarm indicates a physical problem. To
isolate where the physical problem might be occurring, conduct loopback testing. See
Checklist for Using Loopback Testing for Fast Ethernet and Gigabit Ethernet Interfaces
on page 793 for information on conducting a loopback test.
NOTE: Since link status is polled once every second, some items that require
fast link down detection, such as Multiprotocol Label Switching (MPLS) fast
reroute, take longer to execute.
Description: Table 78 on page 806 shows the major counters that appear in the output
for the show interfaces fe-fpc/pic/port extensive and the show interfaces ge-fpc/pic/port
extensive commands. These counters generally increment when there is a problem with
a Fast Ethernet or Gigabit Ethernet interface. In the Counters column, the counters are
listed in the order in which they are displayed in the output.
805
Description
Input Errors:
Errors
Policed discards
Drops
If the interface is saturated, this number increments once for every packet
that is dropped by the ASICs random early detection (RED) mechanism.
L3 incompletes
This counter increments when the incoming packet fails Layer 3 (usually
IPv4) checks of the header. For example, a frame with less than 20 bytes
of available IP header would be discarded and this counter would
increment.
L2 channel errors
This error increments when, for example, a lookup for a virtual LAN
(VLAN) fails.
L2 mismatch
timeouts
FIFO errors
The value in this field should always be 0. If this value is not zero, cabling
could be badly organized or the PIC could be broken.
Output Errors
Errors
Collisions
The Fast Ethernet PIC supports only full-duplex operation, so this number
should always remain 0. If it is incrementing, there is a software bug.
Drops
If the interface is saturated, this number increments once for every packet
that is dropped by the ASICs RED mechanism.
Aged packets
806
Table 78: Major Fast Ethernet and Gigabit Ethernet Counters (continued)
Counter
Description
HS link FCS
errors, FIFO errors
The value in this field should always be 0. If it increments, either the FPC
or the PIC is broken.
Miscellaneous Counters
Input DA rejects
Output packet
pad count
Usually, padding is done only on small ARP packets, but some very small
Internet Protocol (IP) packets can also require padding. If this value
increments rapidly, either the system is trying to find an ARP entry for a
far-end system that does not exist, or it is misconfigured.
Output packet
error count
These packets are usually aged packets or are the result of a bandwidth
problem on the FPC hardware. On a normal system, the value of this
field should not increment.
CAM destination
filters, CAM
source filters
Diagnosis
Try disabling and reenabling the interface and resetting the transceiver and cable. If the
interface remains down, it can be stuck in DPC or PIC down state.
Does the router function normally after disabling and reenabling the interface and resetting
the transceiver and cable?
Yes:
The system is not stuck in DPC or PIC down state. Disabling and reenabling the interface
or resetting the transceiver, and cable resolved the issue.
No:
807
The interface might be stuck in DPC or PIC down state. Refer to the Resolution on
page 808 section for recovery options.
Resolution
1.
2. Toggle the framing mode. In the following configuration, WAN-PHY mode is toggled.
Related
Documentation
808
PART 5
809
810
CHAPTER 36
Configuration Statements
811
812
813
814
815
816
loopback (Aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet) on page 1040
817
818
819
820
821
822
823
}
ct3 {
port port-number {
t1 link-number {
channel-group group-number;
timeslots time-slot-range;
}
}
framing sdh;
}
max-queues-per-interface number;
mlfr-uni-nni-bundles num-intf;
no-concatenate;
shdsl {
pic-mode (1-port-atm | 2-port-atm);
}
vtmapping (klm | itu-t);
}
}
fpc slot-number{
pic pic-number{
account-layer2-overhead
egress-policer-overhead bytes;
ingress-policer-overhead bytes;
mlfr-uni-nni-bundles-inline number;
multi-link-layer-2-inline;
}
}
}
Related
Documentation
interfaces {
traceoptions {
file filename <files number> <match regular-expression> <size size> <world-readable |
no-world-readable> ;
flag flag <disable>;
}
interface-name {
824
accounting-profile name;
aggregated-ether-options {
(flow-control | no-flow-control);
lacp {
(active | passive);
link-protection {
disable;
(revertive | non-revertive);
periodic interval;
system-priority priority;
}
link-protection;
link-speed speed;
(loopback | no-loopback);
mc-ae{
chassis-id chassis-id;
mc-ae-id mc-ae-id;
mode (active-active | active-standby);
redundancy-group group-id;
status-control (active | standby);
}
minimum-links number;
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
shared-scheduler;
aggregated-sonet-options {
link-speed speed | mixed;
minimum-links number;
}
atm-options {
cell-bundle-size cells;
ilmi;
linear-red-profiles profile-name {
high-plp-max-threshold percent;
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);
transmit-weight (cells number | percent number);
825
}
vc-cos-mode (alternate | strict);
}
use-null-cw;
vpi vpi-identifier {
maximum-vcs maximum-vcs;
oam-liveness {
down-count cells;
up-count cells;
}
oam-period (seconds | disable);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}
}
}
clocking clock-source;
damping {
enable;
half-life seconds;
max-suppress seconds;
reuse number;
suppress number;
}
data-input (system | interface interface-name);
dce;
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);
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);
}
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);
tm (ignore | normal | require);
826
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;
loopback mode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}
description text;
alias alias-name;
dialer-options {
pool pool-name <priority priority>;
}
disable;
ds0-options {
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
byte-encoding (nx56 | nx64);
fcs (16 | 32);
idle-cycle-flag (flags | ones);
invert-data;
loopback payload;
start-end-flag (filler | shared);
}
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;
}
e3-options {
atm-encapsulation (direct | plcp);
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
framing feet;
compatibility-mode (digital-link | kentrox | larscom) <subrate value>;
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;
827
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;
}
}
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
flexible-vlan-tagging;
gigether-options {
802.3ad aex;
(asynchronous-notification | no-asynchronous-notification);
(auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online |
local-interface-offline>;
auto-reconnect seconds;
(flow-control | no-flow-control);
ignore-l3-incompletes;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
no-auto-mdix;
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
ethernet-switch-profile {
(mac-learn-enable | no-mac-learn-enable);
tag-protocol-id [ tpids ];
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
policer cos-policer-name {
828
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;
beta number;
gamma number;
}
minimum-links number;
symmetry (symmetrical-config-and-operation |
symmetrical-config-asymmetrical-operation);
test-procedure {
ima-test-start;
ima-test-stop;
interface name;
pattern number;
period number;
}
transmit-clock (common | independent);
version (1.0 |1.1);
}
ima-link-options group-id group-id;
interface-set interface-set-name {
interface ethernet-interface-name {
(unit unit-number | vlan-tags-outer vlan-tag);
}
interface interface-name {
(unit unit-number);
}
}
isdn-options {
bchannel-allocation (ascending | descending);
calling-number number;
pool pool-name <priority priority>;
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);
}
keepalives <down-count number> <interval seconds> <up-count number>;
829
link-mode mode;
lmi {
lmi-type (ansi | itu | c-lmi);
n391dte number;
n392dce number;
n392dte number;
n393dce number;
n393dte number;
t391dte seconds;
t392dce seconds;
}
lsq-failure-options {
no-termination-request;
[ trigger-link-failure interface-name ];
}
mac mac-address;
mlfr-uni-nni-bundle-options {
acknowledge-retries number;
acknowledge-timer milliseconds;
action-red-differential-delay (disable-tx | remove-link);
drop-timeout milliseconds;
fragment-threshold bytes;
cisco-interoperability send-lip-remove-link-for-link-reject;
hello-timer milliseconds;
link-layer-overhead percent;
lmi-type (ansi | itu | c-lmi);
minimum-links number;
mrru bytes;
n391 number;
n392 number;
n393 number;
red-differential-delay milliseconds;
t391 seconds;
t392 seconds;
yellow-differential-delay milliseconds;
}
modem-options {
dialin (console | routable);
init-command-string initialization-command-string;
}
mtu bytes;
multi-chassis-protection {
peer a.b.c.d {
interfaceinterface-name;
}
}
multiservice-options {
(core-dump | no-core-dump);
(syslog | no-syslog);
}
native-vlan-id number;
no-gratuitous-arp-request;
no-keepalives;
no-partition {
interface-type type;
}
830
no-vpivci-swapping;
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);
tti;
}
optics-options {
wavelength nm;
alarm alarm-name {
(syslog | link-down);
}
warning warning-name {
(syslog | link-down);
}
}
partition partition-number oc-slice oc-slice-range interface-type type;
timeslots time-slot-range;
passive-monitor-mode;
per-unit-scheduler;
ppp-options {
chap {
access-profile name;
default-chap-secret name;
local-name name;
passive;
}
compression {
acfc;
pfc;
}
dynamic-profile profile-name;
no-termination-request;
pap {
access-profile name;
local-name name;
local-password password;
compression;
}
}
psn-vcipsn-vci-identifier;
psn-vpipsn-vpi-identifier;
receive-bucket {
overflow (discard | tag);
rate percentage;
threshold bytes;
}
redundancy-options {
priority sp-fpc/pic/port;
831
secondary sp-fpc/pic/port;
hot-standby;
}
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);
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);
}
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);
tm (ignore | normal | require);
}
dtr-circuit (balanced | unbalanced);
dtr-polarity (negative | positive);
encoding (nrz | nrzi);
indication-polarity (negative | positive);
line-protocol protocol;
loopback mode;
rts-polarity (negative | positive);
tm-polarity (negative | positive);
transmit-clock invert;
}
services-options {
inactivity-timeout seconds;
open-timeout seconds;
session-limit {
maximum number;
rate new-sessions-per-second;
}
syslog {
host hostname {
facility-override facility-name;
832
log-prefix prefix-number;
services priority-level;
}
}
}
shdsl-options {
annex (annex-a | annex-b);
line-rate line-rate;
loopback (local | remote);
snr-margin {
snext margin;
}
}
sonet-options {
aggregate asx;
aps {
advertise-interval milliseconds;
annex-b;
authentication-key key;
fast-aps-switch;
force;
hold-time milliseconds;
lockout;
neighbor address;
paired-group group-name;
preserve-interface;
protect-circuit group-name;
request;
revert-time seconds;
switching-mode (bidirectional | unidirectional);
working-circuit group-name;
}
bytes {
c2 value;
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;
}
}
path-trace trace-string;
(payload-scrambler | no-payload-scrambler);
rfc-2615;
trigger {
defect ignore;
hold-time up milliseconds down milliseconds;
}
vtmapping (itu-t | klm);
833
(z0-increment | no-z0-increment);
}
speed (10m | 100m | 1g | oc3 | oc12 | oc48);
stacked-vlan-tagging;
switch-options {
switch-port port-number {
(auto-negotiation | no-auto-negotiation);
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);
fcs (16 | 32);
framing (esf | sf);
idle-cycle-flag (flags | ones);
invert-data;
line-encoding (ami | b8zs);
loopback (local | payload | remote);
remote-loopback-respond;
start-end-flag (filler | shared);
timeslots time-slot-range;
}
t3-options {
atm-encapsulation (direct | plcp);
bert-algorithm algorithm;
bert-error-rate rate;
bert-period seconds;
buildout feet;
(cbit-parity | no-cbit-parity);
compatibility-mode (adtran | digital-link | kentrox | larscom | verilink) <subrate
value>;
fcs (16 | 32);
(feac-loop-respond | no-feac-loop-respond);
idle-cycle-flag value;
(long-buildout | no-long-buildout);
(loop-timing | no-loop-timing);
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;
}
834
(traps | no-traps);
unidirectional;
vlan-tagging;
vlan-vci-tagging;
unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
accounting-profile name;
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
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;
maximum port-number;
}
}
}
compression-device interface-name;
copy-tos-to-outer-ip-header;
demux-destination family;
demux-source family;
demux-options {
underlying-interface interface-name;
}
description text;
alias alias-name;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
callback;
callback-wait-period time;
deactivation-delay seconds;
dial-string [ dial-string-numbers ];
835
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 ];
}
}
}
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;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
interleave-fragments;
inverse-arp;
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
link-layer-overhead percent;
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
multicast-vci vpi-identifier.vci-identifier;
multilink-max-classes number;
multipoint;
oam-liveness {
down-count cells;
up-count cells;
}
oam-period (seconds | disable);
output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
836
tag-protocol-id tpid;
vlan-id number;
}
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;
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;
underlying-interface interface-name;
}
proxy-arp;
service-domain (inside | outside);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate
burst length);
queue-length number;
}
short-sequence;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
837
source source-address;
ttl number;
}
vci vpi-identifier.vci-identifier;
vci-range start start-vci end end-vci;
vpi vpi-identifier;
vlan-id number;
vlan-id-list [vlan-id vlan-idvlan-id];
vlan-id-range number-number;
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
vlan-tags-outer tpid.vlan-id inner-list [vlan-id vlan-idvlan-id];
family family {
accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
access-concentrator name;
address address {
destination address;
}
bundle ml-fpc/pic/port | ls-fpc/pic/port);
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
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;
max-sessions number;
max-sessions-vsa-ignore;
mtu bytes;
multicast-only;
negotiate-address;
no-redirects;
policer {
arp policer-template-name;
disable-arp-policer
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);
838
rpf-check {
fail-filter filter-name;
mode loose;
}
sampling {
direction;
}
service {
input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
output {
service-set service-set-names <service-filter filter-name>;
}
}
service-name-table table-name;
short-cycle-protection <lockout-time-min minimum-seconds lockout-time-max
maximum-seconds>;
targeted-broadcast {
forward-and-send-to-re;
forward-only;
}
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
translate-plp-control-word-de;
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;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
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;
}
preferred;
primary;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
authentication-type authentication;
839
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority-number number;
track {
priority-cost seconds;
priority-hold-time interface-name {
bandwidth-threshold bits-per-second {
priority;
}
interface priority;
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
virtual-address [ addresses ];
}
}
}
}
}
}
Related
Documentation
840
logical-systems logical-system-name {
interfaces interface-name {
unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
allow-any-vci;
atm-scheduler-map (map-name | default);
bandwidth rate;
backup-options {
interface interface-name;
}
cell-bundle-size cells;
clear-dont-fragment-bit;
compression {
rtp {
f-max-period number;
port {
minimum port-number;
maximum port-number;
}
queues [ queue-numbers ];
}
}
compression-device interface-name;
description text;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
deactivation-delay seconds;
dial-string [ dial-string-numbers ];
idle-timeout seconds;
initial-route-check seconds;
load-threshold number;
pool pool;
remote-name remote-callers;
watch-list {
[ routes ];
}
}
disable;
dlci dlci-identifier;
drop-timeout milliseconds;
dynamic-call-admission-control {
activation-priority priority;
bearer-bandwidth-limit kilobits-per-second;
}
encapsulation type;
841
842
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);
queue-length number;
}
short-sequence;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;
ttl number;
}
vci vpi-identifier.vci-identifier;
vlan-id number;
vlan-id-list [vlan-id vlan-idvlan-id]
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
vlan-tags outer tpid.vlan-id inner-list [vlan-id vlan-idvlan-id]
vpi vpi-identifier;
family family {
accounting {
destination-class-usage;
source-class-usage {
direction;
}
}
bundle interface-name;
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;
mtu bytes;
multicast-only;
no-redirects;
843
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> {
<mode loose>;
}
sampling {
direction;
}
service {
input {
service-set service-set-name <service-filter filter-name>;
post-service-filter filter-name;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
unnumbered-address interface-name destination address destination-profile
profile-name;
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;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (seconds | disable);
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;
}
preferred;
primary;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
844
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;
bandwidth-threshold bits-per-second {
priority;
}
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
}
virtual-address [ addresses ];
}
}
}
}
}
Related
Documentation
Supported statements are those that you can use to configure some aspect of a
software feature on the switch.
Unsupported statements are those that appear in the command-line interface (CLI)
on the switch, but that have no effect on switch operation if you configure them.
845
846
footer-message string;
footer-text-color color;
form-header-bgcolor color;
form-header-message string;
form-header-text-color color;
form-reset-label label name;
form-submit-label label name;
header-bgcolor color;
header-logo filename;
header-message string;
header-text-color color;
post-authentication-url url-string;
secure-authentication (http | https);
}
}
847
Related
Documentation
Related
Documentation
Related
Documentation
848
Related
Documentation
Related
Documentation
849
850
sla-iterator-profiles {
profile-name {
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
no-aggregate-delegate-processing;
}
link-fault-management {
action-profile profile-name {
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;
}
}
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;
pdu-threshold threshold-value;
remote-loopback;
}
}
fnp {
interval <100ms | 1s | 10s | 1m | 10m>;
loss-threshold number
interface interface name {
domain-id domain-id
851
}
}
}
Related
Documentation
Related
Documentation
852
filter {
aci regular-expression;
ari regular-expresion;
service-name regular-expresion;
underlying-interface interface-name;
}
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
}
}
Related
Documentation
853
no-remote-trace;
}
version-3;
}
}
Related
Documentation
Supported statements are those that you can use to configure some aspect of a
software feature on the router.
Unsupported statements are those that appear in the command-line interface (CLI)
on the router, but that have no effect on router operation if you configure them.
Supported Statements in the [edit security macsec] Hierarchy Level on page 854
Unsupported Statements in the [edit security macsec] Hierarchy Level on page 855
854
replay-window-size number-of-packets;
}
secure-channel secure-channel-name {
direction (inbound | outbound);
encryption ;
id {
mac-address mac-address;
port-id port-id-number;
}
offset (0|30|50);
security-association security-association-number {
key key-string;
}
}
security-mode security-mode;
}
interfaces interface-name {
connectivity-association connectivity-association-name;
}
}
}
Related
Documentation
855
802.3ad
Syntax
Hierarchy Level
Release Information
Description
Options
802.3ad {
ae interface-number (primary | backup);
lacp {
port-priority;
}
}
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]
Range: 0 through 15
primaryFor link protection configurations, specify the primary link for egress traffic.
backupFor link protection configurations, specify the backup link for egress traffic.
Required Privilege
Level
Related
Documentation
856
accept-source-mac
Syntax
Hierarchy Level
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Release Information
Description
For Gigabit Ethernet intelligent queuing (IQ) interfaces only, accept traffic from and to
the specified remote media access control (MAC) address.
The accept-source-mac statement is equivalent to the source-address-filter statement,
which is valid for aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces
only. To allow the interface to receive packets from specific MAC addresses, include the
accept-source-mac statement.
On untagged Gigabit Ethernet interfaces, you should not configure the source-address-filter
statement and the accept-source-mac statement simultaneously. On tagged Gigabit
Ethernet interfaces, you should not configure the source-address-filter statement and
the accept-source-mac statement with an identical MAC address specified in both filters.
The statements are explained separately.
NOTE: The policer statement is not supported on PTX Series Packet Transport
Routers.
Required Privilege
Level
857
Related
Documentation
Configuring MAC Address Filtering on PTX Series Packet Transport Routers on page 17
access-concentrator
Syntax
Hierarchy Level
Release Information
Description
access-concentrator name;
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family
pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit interfaces interface-name unit logical-unit-number family pppoe],
[edit interfaces interface-name unit logical-unit-number pppoe-options],
[edit interfaces interface-name unit logical-unit-number pppoe-underlying-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family pppoe],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
pppoe-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
pppoe-underlying-options]
NOTE: The [edit ... family pppoe] hierarchies are supported only on MX Series
routers with MPCs.
Options
Required Privilege
Level
Related
Documentation
858
Required Privilege
Level
Related
Documentation
account-layer2-overhead;
[edit chassis fpc slot-number pic pic-number]
action (OAM)
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
action {
link-down;
send-critical-event;
syslog;
}
[edit protocols oam ethernet link-fault-management action-profile]
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
859
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
860
action-profile profile-name;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id remote-mep mep-id]
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
Hierarchy Level
Release Information
Description
Options
action-profile profile-name {
event {
ais-trigger-condition {
adjacency-loss;
all-defects;
cross-connect-ccm;
erroneous-ccm;
receive-ais;
}
interface-status-tlv (down | lower-layer-down);
port-status-tlv blocked;
rdi;
}
action {
interface-down;
log-and-generate-ais {
interval(1m | 1s);
levelvalue;
priority value;
}
}
default-actions {
interface-down;
}
}
[edit protocols oam ethernet connectivity-fault-management]
event (CFM)
861
Hierarchy Level
Release Information
Description
Options
action-profile profile-name {
action {
link-down;
send-critical-event;
syslog;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
}
[edit protocols oam ethernet link-fault-management]
862
action-profile (MEP)
Syntax
Hierarchy Level
Release Information
Description
Options
action-profile action-profile-name;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain md-name
maintenance-association ma-name mep mep-id]
863
adaptive
Syntax
Hierarchy Level
Release Information
Description
Options
adaptive {
pps;
scan-interval multiple;
tolerance tolerance-percentage;
}
[edit interfaces aex aggregated-ether-options load-balance]
measured packets per second. The default rate type is bytes per second.
scan-interval multiple(PTX Series only) Scan interval, as a multiple of a 30-second
interval.
Range: 1 through 5
Default: 1
tolerance tolerance-percentage(MX Series and PTX Series) Limit to the variance in the
864
address
Syntax
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;
eui-64;
master-only;
multipoint-destination address dlci dlci-identifier;
multipoint-destination address {
epd-threshold cells;
inverse-arp;
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);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
primary;
preferred;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval 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;
bandwidth-threshold bits-per-second {
priority;
}
}
route ip-address/mask routing-instance instance-name priority-cost cost;
}
virtual-address [ addresses ];
}
}
Hierarchy Level
865
Release Information
Description
Options
In Junos OS Release 13.3 and later, when you configure an IPv6 host address and an
IPv6 subnet address on an interface, the commit operation fails.
In releases earlier than Junos OS Release 13.3, when you use the same configuration
on an interface, the commit operation succeeds, but only one of the IPv6 addresses
that was entered is assigned to the interface. The other address is not applied.
NOTE: If you configure the same address on multiple interfaces in the same
routing instance, Junos OS uses only the first configuration. The remaining
address configurations are ignored and can leave interfaces without an
address. Interfaces that do not have an assigned address cannot be used as
a donor interface for an unnumbered Ethernet interface.
For example, in the following configuration the address configuration of
interface xe-0/0/1.0 is ignored:
interfaces {
xe-0/0/0 {
unit 0 {
family inet {
address 192.168.1.1/24;
}
}
}
xe-0/0/1 {
unit 0 {
family inet {
address 192.168.1.1/24;
}
}
}
Required Privilege
Level
866
Related
Documentation
unnumbered-address (Ethernet)
adjacency-loss
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
adjacency-loss;
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event ais-trigger-condition]
867
advertisement-interval
Syntax
Hierarchy Level
Release Information
Description
advertisement-interval seconds;
[edit protocols lldp],
[edit routing-instances routing-instance-name protocols lldp]
Statement introduced in Junos OS Release 9.6 for MX Series and T Series routers.
Statement introduced in Junos OS Release 9.0 for EX Series switches.
Statement introduced in Junos OS Release 14.1X53-D20 for OCX Series switches.
Statement introduced in Junos OS Release 11.1 for the QFX Series.
Statement introduced in Junos OS Release 14.1X53-D20 for OCX Series switches.
Configure an interval for LLDP advertisement.
For switches configured for Link Layer Discovery Protocol, configure the frequency at
which LLDP advertisements are sent.
The advertisement-interval value must be greater than or equal to four times the
transmit-delay value, or an error will be returned when you attempt to commit the
configuration.
Default
Options
Disabled.
secondsInterval between LLDP advertisement.
Default: 30
Range: 5 through 32768
Required Privilege
Level
Related
Documentation
868
show lldp
transmit-delay
Understanding LLDP
age
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation
869
agent-specifier
Syntax
Hierarchy Level
Release Information
Description
agent-specifier {
aci circuit-id-string ari remote-id-string {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
static-interface interface-name;
}
}
[edit protocols pppoe service-name-tables table-name service service-name]
Default
Options
870
Required Privilege
Level
Related
Documentation
Assigning an ACI/ARI Pair to a Service Name and Configuring the Action Taken When the
Client Request Includes ACI/ARI Information
Hierarchy Level
Release Information
Description
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name]
Required Privilege
Level
Related
Documentation
871
aggregated-devices
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
872
aggregated-devices {
ethernet {
device-count number;
lacp {
link-protection {
non-revertive;
}
system-priority;
}
}
sonet {
device-count number;
}
maximum-links maximum-links-limit;
}
[edit chassis]
aggregated-ether-options
Syntax
aggregated-ether-options {
ethernet-switch-profile {
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
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;
}
}
}
(mac-learn-enable | no-mac-learn-enable);
}
(flow-control | no-flow-control);
lacp {
(active | passive);
link-protection {
disable;
(revertive | non-revertive);
periodic interval;
system-priority priority;
system-id system-id;
}
link-protection;
load-balance;
link-speed speed;
logical-interface-chassis-redundancy;
logical-interface-fpc-redundancy;
(loopback | no-loopback);
minimum-links number;
rebalance-periodic time hour:minute <interval hours>;
source-address-filter {
mac-address;
(source-filtering | no-source-filtering);
}
}
873
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
ais-trigger-condition
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
874
ais-trigger-condition {
adjacency-loss;
all-defects;
cross-connect-ccm;
erroneous-ccm;
receive-ais;
}
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event]
alarm (optics-options)
Syntax
Hierarchy Level
Release Information
Description
Options
alarm low-lightalarm {
(link-down | syslog);
}
[edit interfaces interface-name optics-options]
Required Privilege
Level
Related
Documentation
Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or
Warning on page 398
alarms
Syntax
alarms;
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
For 10-Gigabit Ethernet DPCs, configure the DPC to drop the interface link when the
receive power falls below the alarm threshold.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
875
all-defects
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
all-defects;
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event ais-trigger-condition]
allow-remote-loopback
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
876
allow-remote-loopback;
[edit protocols oam link-fault-management interface interface-name negotiation-options]
apply-action-profile
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
apply-action-profile profile-name;
[edit protocols oam ethernet link-fault-management interface]
877
arp (Interfaces)
Syntax
Hierarchy Level
Release Information
Description
Options
the multicast MAC address as six hexadecimal bytes in one of the following formats:
nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn. For example, 0011.2233.4455 or 00:11:22:33:44:55.
publish(Optional) Have the router or switch reply to ARP requests for the specified IP
address. If you omit this option, the router or switch uses the entry to reach the
destination but does not reply to ARP requests.
Required Privilege
Level
Related
Documentation
878
asynchronous-notification
Syntax
Hierarchy Level
(asynchronous-notification | no-asynchronous-notification);
[edit interfaces ge-fpc/pic/port gigether-options ]
Release Information
Description
For all 10-Gigabit Ethernet interfaces, M120, M320, and T Series routers, configure support
for notification of link down alarm generation and transfer.
transfer.
transfer.
Default
Required Privilege
Level
Related
Documentation
Support for notification of link down alarm generation and transfer is not enabled.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
879
Hierarchy Level
Release Information
880
authentication-access-control {
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable> <match
regex>;
flag flag ;
}
uac-policy;
authentication-profile-name access-profile-name;
no-mac-table-binding {
interface interface-names
static mac-address
}
static mac-address {
interface interface-names;
vlan-assignment (vlan-id |vlan-name);
}
interface (all | [ interface-names ]) {
session-expiry seconds;
quiet-period seconds;
reauthentication {
interval seconds;
}
retries number;
server-timeout seconds;
supplicant (single | single-secure | multiple);
dot1x {
disable;
guest-vlan (vlan-id | vlan-name);
mac-radius {
flap-on-disconnect;
restrict;
}
maximum-requests number;
no-reauthentication;
server-fail (deny | permit | use-cache | vlan-id | vlan-name);
server-reject-vlan (vlan-id | vlan-name) {
eapol-block;
block-interval block-interval;
}
supplicant-timeout seconds;
transmit-period seconds;
}
}
}
(captive-portal | no-captive-portal);
}
[edit protocols]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
Default
Required Privilege
Level
authentication-profile-name
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
authentication-profile-name access-profile-name;
[edit protocols dot1x authenticator]
881
authenticator
Syntax
Hierarchy Level
Release Information
Description
Options
authenticator {
authentication-profile-name access-profile-name;
interface interface-id {
maximum-requests integer;
quiet-period seconds;
reauthentication (disable | interval seconds);
retries integer;
server-timeout seconds;
supplicant (single);
supplicant-timeout seconds;
transmit-period seconds;
}
}
[edit protocols dot1x]
882
auto-discovery
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
auto-discovery;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name mep mep-id]
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
883
auto-negotiation
Syntax
Hierarchy Level
Release Information
Description
2. Set the link speed to 10 or 100 Mbps, set no-auto-negotiation, and commit
the configuration.
On EX Series switches, if the link speed and duplex mode are also configured, the
interfaces use the values configured as the desired values in the negotiation. If
autonegotiation is disabled, the link speed and link mode must be configured.
884
Default
Options
MX Series, T Series, TX Matrix routers, and ACX Series routers only, manually configure
remote fault on an interface.
Default: local-interface-online
Required Privilege
Level
Related
Documentation
auto-reconnect
Syntax
Hierarchy Level
Release Information
Description
Options
auto-reconnect seconds;
[edit interfaces interface-name unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces interface-name
unit logical-unit-number pppoe-options]
885
avg-fd-twoway-threshold
Syntax
Hierarchy Level
Release Information
Description
avg-fd-twoway-threshold avg-fd-twoway-threshold-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]
Options
886
avg-ifdv-twoway-threshold
Syntax
Hierarchy Level
Release Information
Description
avg-ifdv-twoway-threshold avg-ifdv-twoway-threshold-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]
Options
887
avg-flr-forward-threshold
Syntax
Hierarchy Level
Release Information
Description
avg-flr-forward-threshold avg-flr-forward-threshold-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]
Options
888
avg-flr-backward-threshold
Syntax
Hierarchy Level
Release Information
Description
avg-flr-backward-threshold avg-flr-backward-threshold-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]
Options
889
backward-frr-enable
Syntax
Hierarchy Level
Release Information
Description
(backward-frr-enable | no-backward-frr-enable);
[edit interfaces interface-name otn-options preemptive-fast-reroute]
You can also configure the pre-FEC BER thresholds that raise or clear a signal degrade
alarm and the time interval for the thresholds. If the BER thresholds and interval are not
configured, the default values are used. Include the ber-threshold-signal-degrade value,
ber-threshold-clear value, and interval value statements at the [edit interfaces
interface-name otn-options signal-degrade] hierarchy level to configure the BER thresholds
and time interval. See Understanding Pre-FEC BER Monitoring and BER Thresholds on
page 439 for more information about pre-FEC BER monitoring and determining BER
threshold settings.
Default
Options
Required Privilege
Level
Related
Documentation
890
Release Information
Description
Options
bandwidth-limit bps;
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name aggregate],
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name premium]
891
bridge-domain
Syntax
Hierarchy Level
Release Information
Description
Options
bridge-domain name;
vlan-id [ vlan-identifiers ];
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
maintenance-domain-name],
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
maintenance-domain-name virtual-switch virtual-switch-name]
Required Privilege
Level
Related
Documentation
892
bridge-domains
Syntax
Hierarchy Level
bridge-domains bridge-domain-name;
bridge-options {
interface interface-name {
static-mac mac-address;
action-priority number;
}
interface-mac-limit limit;
mac-statistics;
mac-table-size limit;
no-mac-learning;
}
community-vlans number number;
isolated-vlan vlan-id
description;
domain-type bridge;
enable-mac-move-action;
forwarding-options
interface interface-name;
mcae-mac-flush;
mcae-mac-synchronize;
multicast-snooping-options;
no-irb-layer-2-copy;
no-local-switching;
protocols
routing-interface routing-interface-name;
service-id number;
vlan-id (all | none | number);
vlan-id-list [ vlan-id-numbers ];
vlan-tags outer number inner number;
[edit logical-systems logical-system-name bridge-domains bridge-domain-name],
[edit logical-systems logical-system-name routing-instances routing-instance-name],
[edit routing-instances routing-instance-name]
Release Information
Description
(MX Series routers only) Configure a domain that includes a set of logical ports that share
the same flooding or broadcast characteristics in order to perform Layer 2 bridging.
Options
893
894
ber-threshold-clear
Syntax
Hierarchy Level
Release Information
Description
ber-threshold-clear value;
[edit interfaces interface-name otn-options signal-degrade]
[edit interfaces interface-name otn-options odu-signal-degrade]
NOTE: Configuring a high BER threshold for signal degradation and a long
interval might cause the internal counter register to be saturated. Such a
configuration is ignored by the router, and the default values are used instead.
A system log message is logged for this error.
If you configure the BER thresholds at the [edit interfaces interface-name otn-options
signal-degrade] hierarchy level, then the thresholds are calculated using the pre-forward
error correction (pre-FEC) BER (the BER before FEC correction). These thresholds are
used for pre-FEC BER monitoring. See Understanding Pre-FEC BER Monitoring and BER
Thresholds on page 439 for more information about pre-FEC BER monitoring and
determining BER threshold settings.
If you configure the BER thresholds at the [edit interfaces interface-name otn-options
odu-signal-degrade] hierarchy level, then the thresholds are calculated using the post-FEC
BER (the BER after FEC correction). This BER is referred to as the optical channel data
unit (ODU) BER.
NOTE: You can configure ODU BER thresholds only at the [edit interfaces
interface-name otn-options odu-signal-degrade] hierarchy level on the
P2-100GE-OTN PIC.
Table 79 on page 896 shows the default values for pre-FEC BER and ODU BER signal
degrade threshold values for different PICs. If the BER signal degrade threshold is not
configured, the default value is used.
895
P1-PTX-2-100G-WDM
3.0E3
Not supported
P2-100GE-OTN
3.0E3
1.0E9
P1-PTX-24-10G-W-SFPP
3.0E3
Not supported
PTX-2-100G-WDM-M
To configure the threshold that raises the signal degrade alarm, include the
ber-threshold-signal-degrade statement at the same hierarchy level. To configure the
time interval during which the BER must stay above or below the configured thresholds
to raise or clear the alarm, include the interval statement at the same hierarchy level.
Options
Values: valueBER threshold for clearing the signal degradation in scientific notation.
Both the mantissa and exponent are configurable. Enter the value in the format xE-n,
where x is the mantissa and n is the exponent. For example, 4.5E-3.
Range: The mantissa must be a decimal number. There is no limit on the number of
digits before or after the decimal point.The exponent must be an integer from 0
through 9.
Default: See Table 79 on page 896.
NOTE: In Junos OS Release 13.2R1, only the exponent is valid input for the
BER threshold value, the mantissa is not configurable. The BER threshold
value is 1.0En where n > 0, and the valid range of n is from 1 through 10.
Required Privilege
Level
896
Related
Documentation
897
ber-threshold-signal-degrade
Syntax
Hierarchy Level
Release Information
Description
ber-threshold-signal-degrade value;
[edit interfaces interface-name otn-options signal-degrade]
[edit interfaces interface-name otn-options odu-signal-degrade]
NOTE: Configuring a high BER threshold for signal degradation and a long
interval might cause the internal counter register to be saturated. Such a
configuration is ignored by the router, and the default values are used instead.
A system log message is logged for this error.
If you configure the BER thresholds at the [edit interfaces interface-name otn-options
signal-degrade] hierarchy level, then the thresholds are calculated using the pre-forward
error correction (pre-FEC) BER (the BER before FEC correction). These thresholds are
used for pre-FEC BER monitoring. See Understanding Pre-FEC BER Monitoring and BER
Thresholds on page 439 for more information about pre-FEC BER monitoring and
determining BER threshold settings.
If you configure the BER thresholds at the [edit interfaces interface-name otn-options
odu-signal-degrade] hierarchy level, then the thresholds are calculated using the post-FEC
BER (the BER after FEC correction). This BER is referred to as the optical channel data
unit (ODU) BER.
NOTE: You can configure ODU BER thresholds only at the [edit interfaces
interface-name otn-options odu-signal-degrade] hierarchy level on the
P2-100GE-OTN PIC.
Table 80 on page 899 shows the default values for pre-FEC BER and ODU BER signal
degrade threshold values for different PICs. If the BER signal degrade threshold is not
configured, the default value is used.
898
P1-PTX-2-100G-WDM
7.5E3
Not supported
P2-100GE-OTN
7.5E3
1.0E6
P1-PTX-24-10G-W-SFPP
7.5E3
Not supported
PTX-2-100G-WDM-M
To configure the threshold that clears the signal degrade alarm, include the
ber-threshold-clear statement at the same hierarchy level. To configure the time interval
during which the BER must stay above or below the configured thresholds to raise or
clear the alarm, include the interval statement at the same hierarchy level.
Options
valueBER threshold for signal degradation in scientific notation. Both the mantissa and
exponent are configurable. Enter the value in the format xEn, where x is the mantissa
and n is the exponent. For example, 4.5E3.
Range: The mantissa must be a decimal number. There is no limit on the number of
digits before or after the decimal point.The exponent must be an integer from 0
through 9.
Default: See Table 80 on page 899.
NOTE: In Junos OS Release 13.2R1, only the exponent is valid input for the
BER threshold value, the mantissa is not configurable. The BER threshold
value is 1.0En where n > 0, and the valid range of n is from 1 through 10.
Required Privilege
Level
899
Related
Documentation
900
bfd-liveness-detection (LAG)
Syntax
Hierarchy Level
Release Information
Description
Options
bfd-liveness-detection {
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
holddown-interval milliseconds;
local-address bfd-local-address;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
neighbor bfd-neighbor-address;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | automatic);
}
[edit interfaces aex aggregated-ether-options]
that a BFD session remains up before a state change notification is sent. If the BFD
session goes down and then comes back up during the hold-down interval, the timer
is restarted.
Range: 0 through 255,000
Default: 0
local-address bfd-local-address Specify the loopback address of the source of the BFD
session.
minimum-interval milliseconds Specify a minimum time interval after which the local
routing device transmits a BFD packet and then expects to receive a reply from the
BFD neighbor. Optionally, instead of using this statement, you can configure the
minimum transmit and receive intervals separately using the transmit-interval
minimum-interval statement.
Range: 1 through 255,000
minimum-receive-interval milliseconds Specify the minimum time interval after which
the routing device expects to receive a reply from the BFD neighbor.
901
the BFD sessions to adapt to changing network conditions. We recommend that you
do not disable BFD adaptation unless it is preferable not to have BFD adaptation
enabled in your network.
version Configure the BFD version to detect (BFD version 1) or autodetect (the BFD
version).
Default: automatic
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation
902
authentication
detection-time
transmit-interval
Example: Configuring Independent Micro BFD Sessions for LAG on page 203
Release Information
Description
Options
burst-size-limit bytes;
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name aggregate],
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name premium]
bypass
Syntax
Hierarchy Level
Release Information
Description
Default
(bypass | no-bypass);
[edit interfaces interface-name otn-options odu-delay-management]
Options
Required Privilege
Level
Related
Documentation
903
bytes (otn-options)
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
ckn hexadecimal-number;
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Default
Options
The key name is 32 hexadecimal characters in length. If you enter a key name that
is less then 32 characters long, the remaining characters are set to 0.
Required Privilege
Level
Related
Documentation
904
calculation-weight
Syntax
Hierarchy Level
Release Information
Description
calculation-weight {
delay delay-value;
delay-variation delay-variation-value;
}
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]
905
(captive-portal | no-captive-portal);
[edit protocols authentication-access-control]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
Specify whether captive portal authentication needs to be enabled or disabled. You can
set up captive portal authentication (hereafter referred to as captive portal) on a switch
to redirect Web browser requests to a login page that requires the user to input a username
and password. Upon successful authentication, the user is allowed to continue with the
original page request and subsequent access to the network.
Default
Options
Not enabled
captive-portalEnable captive portal authentication.
no-captive-portalDisable captive portal authentication.
Required Privilege
Level
906
Hierarchy Level
Release Information
Description
Options
captive-portal-custom-options {
banner-message string;
footer-bgcolor color;
footer-message string;
footer-text-color color;
form-header-bgcolor color;
form-header-message string;
form-header-text-color color;
form-reset-label label name;
form-submit-label label name;
header-bgcolor color;
header-logo filename;
header-message string;
header-text-color color;
post-authentication-url url-string;
}
[edit protocols]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Specify the design elements of a captive portal login page.
banner-messageThe first screen displayed before the captive portal login page is
bottom of the captive portal login pagefor example, #2E8B57 (sea green).
Values: # symbol followed by six characters.
footer-messageText message displayed in the footer bar across the bottom of the
header bar across the top of the form area of the captive portal login page.
Values: # symbol followed by six characters.
form-header-messageText message displayed in the header bar across the top of the
907
of the captive portal login page. The image file can be in GIF, JPEG, or PNG format.
Default: The Juniper Networks logo
header-messageText displayed in the header bar across the bottom of the captive
908
centralized
Syntax
Hierarchy Level
Release Information
Description
centralized;
[edit protocols lacp ppm]
Default
Required Privilege
Level
Related
Documentation
Distributed PPM processing is enabled for all packets that use PPM.
routingTo view this statement in the configuration.
routing-controlTo add this statement to the configuration.
909
chassis
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
chassis { ... }
[edit]
ckn hexadecimal-number;
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specifies the connectivity association key name (CKN) for a pre-shared key.
A pre-shared key includes a CKN and a connectivity association key (CAK). A pre-shared
key is exchanged between two devices at each end of a point-to-point link to enable
MACsec using dynamic security keys. The MACsec Key Agreement (MKA) protocol is
enabled once the pre-shared keys are successfully exchanged. The pre-shared keythe
CKN and CAKmust match on both ends of a link
Default
Options
The key name is 32 hexadecimal characters in length. If you enter a key name that
is less then 32 characters long, the remaining characters are set to 0.
Required Privilege
Level
Related
Documentation
910
classifier
Syntax
Hierarchy Level
Release Information
Description
classifier {
per-unit-scheduler {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile output-priority-map]
Required Privilege
Level
Related
Documentation
clear
Syntax
Hierarchy Level
Description
Required Privilege
Level
Related
Documentation
Clears the lockout, force switch, manual switch, exercise, and wait-to-restore (WTR)
states.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
911
client
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
client;
[edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number
pppoe-options]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers.
Description
Configure the specified community VLAN to be a secondary VLAN of the specified primary
VLAN. A community VLAN is used to transport frames among members of a community,
which is a subset of users within the VLAN, and to forward frames upstream to the primary
VLAN.
Options
Required Privilege
Level
Related
Documentation
912
compatibility-version
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
compatibility-version;
[edit protocols protection-group ethernet-ring ring-name]
Default
Options
connectivity-association connectivity-association-name;
[edit security macsec interfaces interface-name]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Applies a connectivity association to an interface, which enables Media Access Control
Security (MACsec) on that interface.
No connectivity associations are associated with any interfaces.
connectivity-association-nameName of the MACsec connectivity association.
913
Hierarchy Level
Release Information
Description
connectivity-association connectivity-association-name {
exclude-protocol protocol-name;
include-sci;
mka {
must-secure;
key-server-priority priority-number;
transmit-interval interval;
}
no-encryption;
offset (0|30|50);
pre-shared-key {
cak hexadecimal-number;
ckn hexadecimal-number;
}
replay-protect{
replay-window-size number-of-packets;
}
secure-channel secure-channel-name {
direction (inbound | outbound);
encryption ;
id {
mac-address mac-address;
port-id port-id-number;
}
offset (0|30|50);
security-association security-association-number {
key key-string;
}
}
security-mode security-mode;
}
[edit security macsec]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Create or configure a MACsec connectivity association.
A connectivity association is not applying MACsec to traffic until it is associated with an
interface. MACsec connectivity associations are associated with interfaces using the
interfaces statement in the [edit security macsec] hierarchy.
Default
Options
914
Required Privilege
Level
Related
Documentation
915
connectivity-fault-management
Syntax
916
connectivity-fault-management {
action-profile profile-name {
action {
interface-down;
log-and-generate-ais {
interval(1m | 1s);
levelvalue;
priority value;
}
}
default-actions {
interface-down;
}
event {
ais-trigger-condition {
adjacency-loss;
all-defects;
cross-connect-ccm;
erroneous-ccm;
receive-ais;
}
adjacency-loss;
interface-status-tlv (down | lower-layer-down);
port-status-tlv blocked;
rdi;
}
}
performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
avg-fd-twoway-threshold;
avg-ifdv-twoway-threshold;
avg-flr-forward-threshold;
avg-flr-backward-threshold;
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
maintenance-domain domain-name {
Hierarchy Level
Release Information
Description
917
Required Privilege
Level
Related
Documentation
continuity-check
Syntax
Hierarchy Level
Release Information
Description
Options
continuity-check {
convey-loss-threshold;
hold-interval minutes;
interface-status-tlv;
interval (10m | 10s | 1m | 1s| 100ms | 10ms);
loss-threshold number;
port-status-tlv;
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name]
Required Privilege
Level
Related
Documentation
918
control-channel
Syntax
Hierarchy Level
Release Information
control-channel channel-name {
vlan vlan-id;
interface name interface-name
}
[edit protocols protection-group ethernet-ring name (east-interface | west-interface)]
Description
Configure the Ethernet RPS control channel logical interface to carry the RAPS PDU. The
related physical interface is the physical ring port.
Options
vlan vlan-idIf the control channel logical interface is a trunk port, then a dedicated vlan
vlan-id defines the dedicated VLAN channel to carry the RAPS traffic. Only configure
the vlan-id when the control channel logical interface is the trunk port.
interface name interface-nameInterface name of the control channel.
Required Privilege
Level
Related
Documentation
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
convey-loss-threshold
Syntax
Hierarchy Level
Description
Required Privilege
Level
convey-loss-threshold;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name continuity-check]
919
cross-connect-ccm
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
cross-connect-ccm;
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event ais-trigger-condition]
cycle-time
Syntax
Hierarchy Level
Release Information
Description
Options
cycle-time cycle-time-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]
920
data-channel
Syntax
Hierarchy Level
Release Information
Description
data-channel {
vlan number;
}
[edit protocols protection-group ethernet-ring ring-name]
Options
Required Privilege
Level
Related
Documentation
vlan numberSpecify (by VLAN ID) one or more VLANs that belong to a ring instance.
Ethernet Ring Protection Using Ring Instances for Load Balancing on page 745
Example: Configuring Load Balancing Within Ethernet Ring Protection for MX Series
Routers on page 752
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
921
data-tlv-size
Syntax
Hierarchy Level
Release Information
Description
Options
data-tlv-size size;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id
sla-iterator-profile profile-name]
922
default-actions
Syntax
Hierarchy Level
Release Information
Description
Default
Options
default-actions {
interface-down;
}
[edit protocols oam ethernet connectivity-fault-management action-profile profile-name]
down.
Required Privilege
Level
Related
Documentation
923
delay
Syntax
Hierarchy Level
Release Information
Description
Options
delay delay-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name calculation-weight]
924
delay seconds;
Hierarchy Level
Release Information
Description
Configure the PPPoE underlying interface on the router to wait a specified number of
seconds after receiving a PPPoE Active Discovery Initiation (PADI) control packet from
a PPPoE client before sending a PPPoE Active Discovery Offer (PADO) packet to indicate
that it can service the client request
The router (PPPoE server) does not check whether another server has already sent a
PADO packet during the delay period in response to the PPPoE clients PADI packet. It
is up to the PPPoE client to determine whether another PPPoE server has responded to
its PADI request, or if it must respond to the delayed PADO packet to establish a PPPoE
session.
Options
secondsNumber of seconds that the PPPoE underlying interface waits after receiving
a PADI packet from a PPPoE client before sending a PADO packet in response.
Range: 1 through 120 seconds
Required Privilege
Level
Related
Documentation
925
delegate-server-processing
Syntax
Hierarchy Level
Release Information
Description
delegate-server-processing;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring]
Required Privilege
Level
Related
Documentation
delay-variation
Syntax
Hierarchy Level
Release Information
Description
Options
delay-variation delay-variation-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name calculation-weight]
926
destination (IPCP)
Syntax
Hierarchy Level
Release Information
Description
Options
detect-loc
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation
detect-loc;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep mep-id ]
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
927
device-count
Syntax
Hierarchy Level
Release Information
Description
device-count number;
[edit chassis aggregated-devices ethernet]
[edit chassis aggregated-devices sonet]
Options
numberSet the number of aggregated logical devices that will be available for
configuration.
928
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Configure whether the secure channel applies MACsec security to traffic entering or
leaving an interface.
If you need to apply MACsec on traffic entering and leaving an interface, you need to
create one secure channel to apply MACsec on incoming traffic and another secure
channel to apply MACsec on outgoing traffic within the same connectivity association.
When you associate the connectivity association with an interface, MACsec is applied
on traffic entering and leaving that interface.
You only use this configuration option when you are configuring MACsec using static
secure association keys (SAK) security mode. When you are configuring MACsec using
static connectivity association keys (CAK) security mode, two secure channels that are
not user-configurableone inbound secure channel and one outbound secure
channelare automatically created within the connectivity association.
Default
Options
inboundEnable MACsec security on traffic entering the interface that has applied the
secure channel.
outboundEnable MACsec security on traffic leaving the interface that has applied the
secure channel.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation
929
direction
Syntax
Hierarchy Level
Release Information
Description
Options
same bridging or vpls instance except for the interface configured on this MEP.
downDown MEP CCMs are transmitted only out the interface configured on this MEP.
Required Privilege
Level
Related
Documentation
930
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
disable
Syntax
Hierarchy Level
Release Information
Description
disable;
[edit protocols lldp],
[edit protocols lldp interface (all | interface-name)],
[edit routing-instances routing-instance-name protocols lldp],
[edit routing-instances routing-instance-name protocols lldp interface (all | interface-name)]
Required Privilege
Level
Related
Documentation
Description
Required Privilege
Level
Related
Documentation
disable;
[edit interfaces aeX aggregated-ether-options lacp link-protection]
931
Description
Default
Required Privilege
Level
disable;
[edit protocols authentication-access-control interface (all | [interface-names]) dot1x]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Disable 802.1X authentication on a specified interface or all interfaces.
802.1X authentication is disabled on all interfaces.
routingTo view this statement in the configuration.
routing-controlTo add this statement to the configuration.
dot1p-priority
Syntax
Hierarchy Level
Release Information
Description
Options
dot1p-priority number;
[edit protocols protection-group ethernet-ring ring-name]
Range: 0 through 7
Default: 0
Required Privilege
Level
Related
Documentation
932
dot1x
Syntax
Hierarchy Level
Release Information
Description
dot1x {
authenticator {
authentication-profile-name access-profile-name;
interface interface-id {
maximum-requests integer;
quiet-period seconds;
reauthentication (disable | interval seconds);
retries integer;
server-timeout seconds;
supplicant (single);
supplicant-timeout seconds;
transmit-period seconds;
}
}
}
[edit protocols]
Required Privilege
Level
Related
Documentation
933
Hierarchy Level
dot1x {
disable;
guest-vlan (vlan-id | vlan-name);
mac-radius {
flap-on-disconnect;
restrict;
}
maximum-requests number;
no-reauthentication;
server-fail (deny | permit | use-cache | vlan-id | vlan-name);
server-reject-vlan (vlan-id | vlan-name) {
eapol-block;
block-interval block-interval;
}
supplicant-timeout seconds;
transmit-period seconds;
}
[edit protocols authentication-access-control interface (all | [ interface-names ])]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
Default
Required Privilege
Level
934
802.1X is disabled.
routingTo view this statement in the configuration.
routing-controlTo add this statement to the configuration.
domain-id
Syntax
Hierarchy Level
Release Information
Description
Options
domain-id domain-id;
[edit logical-systems logical-system-name routing-instances routing-instance-name protocols
(ospf | ospf3)],
[edit routing-instances routing-instance-name protocols (ospf | ospf3)]
drop;
Hierarchy Level
Release Information
Description
Direct the router to drop (ignore) a PPPoE Active Discovery Initiation (PADI) control
packet received from a PPPoE client that contains the specified service name tag or
agent circuit identifier/agent remote identifier (ACI/ARI) information. This action
effectively denies the clients request to provide the specified service, or to accept requests
from the subscriber or subscribers represented by the ACI/ARI information.
Required Privilege
Level
Related
Documentation
935
Release Information
Description
dynamic-profile profile-name;
[edit protocols pppoe service-name-tables table-name service service-name],
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier
aci circuit-id-string ari remote-id-string]
at this level. The dynamic-profile and static-interface statements are mutually exclusive
for ACI/ARI pair configurations.
Options
profile-nameName of the dynamic profile that the router uses to instantiate a dynamic
PPPoE interface.
Required Privilege
Level
Related
Documentation
936
Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for
Dynamic PPPoE Interface Creation
east-interface
Syntax
Hierarchy Level
Release Information
Description
east-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
}
[edit protocols protection-group ethernet-ring ring-name]
NOTE: Always configure this port first, before configuring the west-interface
statement.
Ethernet Ring Protection Using Ring Instances for Load Balancing on page 745
937
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
egress-policer-overhead
Syntax
Hierarchy Level
Release Information
Description
egress-policer-overhead bytes;
[edit chassis fpc slot-number pic pic-number]
Options
938
egress-shaping-overhead
Hierarchy Level
Release Information
Description
Options
When you use this encapsulation type, you can configure the ccc family only.
atm-cisco-nlpidUse Cisco ATM network layer protocol identifier (NLPID) encapsulation.
When you use this encapsulation type, you can configure the inet family only.
atm-mlppp-llcFor ATM2 IQ interfaces only, use Multilink Point-to-Point (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.
atm-nlpidUse ATM NLPID encapsulation. When you use this encapsulation type, you
the ATM MIC with SFP only) Use PPP over AAL5 LLC encapsulation.
atm-ppp-vc-mux(ATM2 IQ interfaces and MX Series routers with MPC/MIC interfaces
using the ATM MIC with SFP only) Use PPP over ATM AAL5 multiplex encapsulation.
atm-snap(All interfaces including MX Series routers with MPC/MIC interfaces using
the ATM MIC with SFP) Use ATM subnetwork attachment point (SNAP)
encapsulation.
atm-tcc-snapUse ATM SNAP encapsulation on translational cross-connect (TCC)
circuits.
939
this encapsulation type, you can configure the tcc family only.
atm-vc-mux(All interfaces including MX Series routers with MPC/MIC interfaces using
the ATM MIC with SFP) Use ATM VC multiplex encapsulation. When you use this
encapsulation type, you can configure the inet family only.
ether-over-atm-llc(All IP interfaces including MX Series routers with MPC/MIC interfaces
using the ATM MIC with SFP) For interfaces that carry IP traffic, use Ethernet over
ATM LLC encapsulation. When you use this encapsulation type, you cannot configure
multipoint interfaces.
ether-vpls-over-atm-llcFor ATM2 IQ interfaces only, use the Ethernet virtual private
LAN service (VPLS) over ATM LLC encapsulation to bridge Ethernet interfaces and
ATM interfaces over a VPLS routing instance (as described in RFC 2684, Multiprotocol
Encapsulation over ATM Adaptation Layer 5). Packets from the ATM interfaces are
converted to standard ENET2/802.3 encapsulated Ethernet frames with the frame
check sequence (FCS) field removed.
ether-vpls-over-frFor E1, T1, E3, T3, and SONET interfaces only, use the Ethernet virtual
private LAN service (VPLS) over Frame Relay encapsulation to support Bridged
Ethernet over Frame Relay encapsulated TDM interfaces for VPLS applications, per
RFC 2427, Multiprotocol Interconnect over Frame Relay.
ether-vpls-over-pppFor E1, T1, E3, T3, and SONET interfaces only, use the Ethernet
virtual private LAN service (VPLS) over Point-to-Point Protocol (PPP) encapsulation
to support Bridged Ethernet over PPP-encapsulated TDM interfaces for VPLS
applications.
ethernetUse Ethernet II encapsulation (as described in RFC 894, A Standard for the
enabled and that must accept packets carrying standard Tag Protocol ID (TPID)
values.
NOTE: The built-in Gigabit Ethernet PIC on an M7i router does not support
extended VLAN VPLS encapsulation.
940
Relay on TCC circuits to connect different media. The physical interface must be
configured with flexible-frame-relay encapsulation.
frame-relay-pppUse PPP over Frame Relay circuits. When you use this encapsulation
media. When you use this encapsulation type, you can configure the tcc family only.
gre-fragmentationFor adaptive services interfaces only, use GRE fragmentation
is used only on multilink, link services, and voice services interfaces and their
constituent T1 or E1 interfaces, and is supported on LSQ and redundant LSQ interfaces.
multilink-pppUse MLPPP encapsulation. This encapsulation is used only on multilink,
link services, and voice services interfaces and their constituent T1 or E1 interfaces.
ppp-over-etherYou use PPP over Ethernet encapsulation to configure an underlying
only) For underlying ATM interfaces, use PPP over Ethernet over ATM LLC
encapsulation. When you use this encapsulation type, you cannot configure the
interface address. Instead, configure the interface address on the PPP interface.
vlan-bridgeUse Ethernet VLAN bridge encapsulation on Ethernet interfaces that have
IEEE 802.1Q tagging, flexible-ethernet-services, and bridging enabled and that must
accept packets carrying TPID 0x8100 or a user-defined TPID.
vlan-cccUse Ethernet virtual LAN (VLAN) encapsulation on CCC circuits. When you use
this encapsulation type, you can configure the ccc family only.
941
you use this encapsulation type, you can configure the ccc family only.
vlan-tccUse Ethernet VLAN encapsulation on TCC circuits. When you use this
Required Privilege
Level
Related
Documentation
942
Hierarchy Level
Release Information
Description
Default
Options
different media.
ethernet-bridgeUse Ethernet bridge encapsulation on Ethernet interfaces that have
packets carrying standard Tag Protocol ID (TPID) values. For 8-port, 12-port, and
48-port Fast Ethernet PICs, CCC is not supported.
ethernet-over-atmFor interfaces that carry IPv4 traffic, use Ethernet over ATM
encapsulation. When you use this encapsulation type, you cannot configure multipoint
interfaces. As defined in RFC 2684, Multiprotocol Encapsulation over ATM Adaptation
Layer 5, this encapsulation type allows ATM interfaces to connect to devices that
support only bridge protocol data units (BPDUs). Junos OS does not completely
support bridging, but accepts BPDU packets as a default gateway. If you use the
router as an edge device, then the router acts as a default gateway. It accepts
Ethernet LLC/SNAP frames with IP or ARP in the payload, and drops the rest. For
packets destined to the Ethernet LAN, a route lookup is done using the destination
943
IP address. If the route lookup yields a full address match, the packet is encapsulated
with an LLC/SNAP and MAC header, and the packet is forwarded to the ATM interface.
ethernet-tccFor interfaces that carry IPv4 traffic, use Ethernet TCC encapsulation on
interfaces that must accept packets carrying standard TPID values. For 8-port,
12-port, and 48-port Fast Ethernet PICs, TCC is not supported.
ethernet-vplsUse Ethernet VPLS encapsulation on Ethernet interfaces that have VPLS
enabled and that must accept packets carrying standard TPID values. On M Series
routers, except the M320 router, the 4-port Fast Ethernet TX PIC and the 1-port,
2-port, and 4-port, 4-slot Gigabit Ethernet PICs can use the Ethernet VPLS
encapsulation type.
ethernet-vpls-frUse in a VPLS setup when a CE device is connected to a PE device over
a time division multiplexing (TDM) link. This encapsulation type enables the PE
device to terminate the outer Layer 2 Frame Relay connection, use the 802.1p bits
inside the inner Ethernet header to classify the packets, look at the MAC address
from the Ethernet header, and use the MAC address to forward the packet into a
given VPLS instance.
ethernet-vpls-pppUse in a VPLS setup when a CE device is connected to a PE device
over a time division multiplexing (TDM) link. This encapsulation type enables the PE
device to terminate the outer Layer 2 PPP connection, use the 802.1p bits inside the
inner Ethernet header to classify the packets, look at the MAC address from the
Ethernet header, and use it to forward the packet into a given VPLS instance.
ether-vpls-over-atm-llcFor ATM intelligent queuing (IQ) interfaces only, use the Ethernet
virtual private LAN service (VPLS) over ATM LLC encapsulation to bridge Ethernet
interfaces and ATM interfaces over a VPLS routing instance (as described in
RFC 2684, Multiprotocol Encapsulation over ATM Adaptation Layer 5). Packets from
the ATM interfaces are converted to standard ENET2/802.3 encapsulated Ethernet
frames with the frame check sequence (FCS) field removed.
extended-frame-relay-cccUse Frame Relay encapsulation on CCC circuits. This
Cisco-compatible Frame Relay for DLCIs 1 through 1022. This encapsulation type is
used for circuits with different media on either side of the connection.
extended-frame-relay-tccUse Frame Relay encapsulation on TCC circuits to connect
different media. This encapsulation type allows you to dedicate DLCIs 1 through 1022
to TCC.
extended-vlan-bridgeUse extended VLAN bridge encapsulation on Ethernet interfaces
that have IEEE 802.1Q VLAN tagging and bridging enabled and that must accept
packets carrying TPID 0x8100 or a user-defined TPID.
944
Ethernet and 4-port Fast Ethernet interfaces that must accept packets carrying
802.1Q values. For 8-port, 12-port, and 48-port Fast Ethernet PICs, extended VLAN
CCC is not supported. For 4-port Gigabit Ethernet PICs, extended VLAN CCC is not
supported.
extended-vlan-tccFor interfaces that carry IPv4 traffic, use extended VLAN encapsulation
on TCC circuits with Gigabit Ethernet interfaces on which you want to use 802.1Q
tagging. For 4-port Gigabit Ethernet PICs, extended VLAN TCC is not supported.
extended-vlan-vplsUse extended VLAN VPLS encapsulation on Ethernet interfaces
that have VLAN 802.1Q tagging and VPLS enabled and that must accept packets
carrying TPIDs 0x8100, 0x9100, and 0x9901. On M Series routers, except the M320
router, the 4-port Fast Ethernet TX PIC and the 1-port, 2-port, and 4-port, 4-slot
Gigabit Ethernet PICs can use the Ethernet VPLS encapsulation type.
NOTE: The built-in Gigabit Ethernet PIC on an M7i router does not support
extended VLAN VPLS encapsulation.
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), use flexible
Ethernet services encapsulation when you want to configure multiple per-unit
Ethernet encapsulations. Aggregated Ethernet bundles can use this encapsulation
type. This encapsulation type allows you to configure any combination of route, TCC,
CCC, Layer 2 virtual private networks (VPNs), and VPLS encapsulations on a single
physical port. If you configure flexible Ethernet services encapsulation on the physical
interface, VLAN IDs from 1 through 511 are no longer reserved for normal VLANs.
flexible-frame-relayFor IQ interfaces only, use flexible Frame Relay encapsulation when
all the DLCIs between two customer edge (CE) routers without explicitly configuring
each DLCI on the two provider edge (PE) routers with Frame Relay transport. When
you use this encapsulation type, you can configure the ccc family only.
945
media.
generic-servicesUse generic services encapsulation for services with a hierarchical
scheduler.
multilink-frame-relay-uni-nniUse MLFR UNI NNI encapsulation. This encapsulation is
used on link services, voice services interfaces functioning as FRF.16 bundles, and
their constituent T1 or E1 interfaces, and is supported on LSQ and redundant LSQ
interfaces.
pppUse serial PPP encapsulation.
ppp-cccUse serial PPP encapsulation on CCC circuits. When you use this encapsulation
When you use this encapsulation type, you can configure the tcc family only.
vlan-cccUse Ethernet VLAN encapsulation on CCC circuits.
vlan-vci-cccUse ATM-to-Ethernet interworking encapsulation on CCC circuits. When
you use this encapsulation type, you can configure the ccc family only. All logical
interfaces configured on the Ethernet interface must also have the encapsulation
type set to vlan-vci-ccc.
vlan-vplsUse VLAN VPLS encapsulation on Ethernet interfaces with VLAN tagging and
VPLS enabled. Interfaces with VLAN VPLS encapsulation accept packets carrying
standard TPID values only. On M Series routers, except the M320 router, the 4-port
Fast Ethernet TX PIC and the 1-port, 2-port, and 4-port, 4-slot Gigabit Ethernet PICs
can use the Ethernet VPLS encapsulation type.
NOTE:
Required Privilege
Level
946
Starting with Junos OS release 13.3, a commit error occurs when you
configure vlan-vpls encapsulation on a physical interface and configure
family inet on one of the logical units. Previously, it was possible to commit
this invalid configuration.
Related
Documentation
Configuring TCC
947
encryption;
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Default
Required Privilege
Level
Related
Documentation
948
MACsec encryption is disabled when MACsec is configured using static SAK security
mode, by default.
adminTo view this statement in the configuration.
admin-controlTo add this statement to the configuration.
erroneous-ccm
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
erroneous-ccm;
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event ais-trigger-condition]
949
ether-options
Syntax
Hierarchy Level
Release Information
Description
ether-options {
802.3ad {
aex;
(backup | primary);
lacp {
force-up;
port-priority
}
}
(auto-negotiation | no-auto-negotiation);
ethernet-switch-profile {
tag-protocol-id;
}
(flow-control | no-flow-control);
ieee-802-3az-eee;
link-mode mode;
(loopback | no-loopback);
speed (speed | auto-negotiation);
}
[edit interfaces interface-name],
[edit interfaces interface-range range]
Required Privilege
Level
Related
Documentation
950
ethernet (Chassis)
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
ethernet {
device-count number;
lacp {
link-protection {
non-revertive;
}
system-priority;
}
}
[edit chassis aggregated-devices]
951
952
ethernet {
connectivity-fault-management {
action-profile profile-name {
default-actions {
interface-down;
}
}
performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
avg-fd-twoway-threshold;
avg-ifdv-twoway-threshold;
avg-flr-forward-threshold;
avg-flr-backward-threshold;
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
maintenance-domain domain-name {
level number;
name-format (character-string | none | dns | mac+2octet);
maintenance-association ma-name {
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
continuity-check {
convey-loss-threshold;
hold-interval minutes;
interface-status-tlv;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number;
port-status-tlv;
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon );
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
}
}
}
evcs evc-id {
evc-protocol cfm management-domain domain-id (management-association
association-id | vpls (routing-instance instance-id);
remote-uni-count count;
multipoint-to-multipoint;
}
link-fault-management {
action-profile profile-name {
action {
link-down;
send-critical-event;
syslog;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
}
interface interface-name {
apply-action-profile;
link-discovery (active | passive);
loopback-tracking;
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
}
}
953
lmi {
status-counter count;
polling-verification-timer value;
interface name {
uni-id uni-name;
status-counter number;
polling-verification-timer value;
evc-map-type (all-to-one-bundling | bundling | service-multiplexing);
evc evc-name {
default-evc;
vlan-list vlan-id-list;
}
}
}
}
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
954
ethernet-policer-profile
Syntax
Hierarchy Level
Release Information
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
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;
}
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile]
Description
For Gigabit Ethernet IQ, 10-Gigabit Ethernet, Gigabit Ethernet PICs with SFPs (except the
10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), and
100-Gigabit Ethernet Type 5 PIC with CFP, configure a class of service (CoS)-based
policer. Policing applies to the inner VLAN identifiers, not to the outer tag. For Gigabit
Ethernet interfaces with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in
Gigabit Ethernet port on the M7i router), the premium policer is not supported.
The statements are explained separately.
Required Privilege
Level
Related
Documentation
955
ethernet-ring
Syntax
Hierarchy Level
Release Information
Description
Options
ethernet-ring ring-name {
control-vlan (vlan-id | vlan-name);
data-channel {
vlan number
}
east-interface {
control-channel channel-name {
vlan number;
interface name interface-name
}
}
guard-interval number;
node-id mac-address;
restore-interval number;
ring-protection-link-owner;
west-interface {
control-channel channel-name {
vlan number;
}
}
}
[edit protocols protection-group]
Required Privilege
Level
Related
Documentation
956
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
ethernet-switch-profile
Syntax
Hierarchy Level
Release Information
ethernet-switch-profile {
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [values];
}
output-priority-map {
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;
}
}
tag-protocol-id tpid;
}
mac-learn-enable;
}
[edit interfaces interface-name gigether-options],
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options]
Description
For Gigabit Ethernet IQ, 10-Gigabit Ethernet IQ2 and IQ2-E, and Gigabit Ethernet PICs
with SFPs (except the 10-port Gigabit Ethernet PIC, aggregated Ethernet with Gigabit
Ethernet IQ interfaces, the built-in Gigabit Ethernet port on the M7i router); 100-Gigabit
Ethernet Type 5 PIC with CFP; and Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit
957
Ethernet, and aggregated Ethernet interfaces on EX Series switches, configure VLAN tag
and MAC address accounting and filtering properties.
The remaining statements are explained separately.
Default
Required Privilege
Level
Related
Documentation
958
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489
evcs
Syntax
Hierarchy Level
Release Information
evcs evc-id {
evc-protocol cfm;
remote-uni-count count;
multipoint-to-multipoint;
}
[edit protocols oam ethernet]
Description
On MX Series routers with ge, xe, or ae interfaces, configure an OAM Ethernet virtual
connection.
Options
959
evc-protocol cfm
Syntax
Hierarchy Level
Release Information
Description
Options
evc-protocol cfm {
maintenance-association association-name | vpls routing-instance routing-id;
maintenance-domain domain-id;
mep-id mep-id;
}
[edit protocols oam ethernet evcs]
domain.
management-association association-id(Optional) For CFM, specify the CFM
management association.
routing-instance instance-id(Optional) For VPLS, specify the VPLS routing instance.
mep-id mep-id(Required for CFM) Identifier for the maintenance association endpoint
960
event (LFM)
Syntax
Hierarchy Level
Release Information
Description
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
[edit protocols oam ethernet link-fault-management action-profile]
Required Privilege
Level
Related
Documentation
event-thresholds
Syntax
Hierarchy Level
Release Information
Description
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
[edit protocols oam link-fault-management interface interface-name]
Required Privilege
Level
Related
Documentation
Configuring Threshold Values for Local Fault Events on an Interface on page 606
961
exclude-protocol protocol-name;
[edit security macsec connectivity-association connectivity-association-name]
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specifies protocols whose packets are not secured using Media Access Control Security
(MACsec) when MACsec is enabled on a link using static connectivity association key
(CAK) security mode.
When this option is enabled in a connectivity association that is attached to an interface,
MACsec is not enabled for all packets of the specified protocols that are sent and received
on the link.
Default
Disabled.
All packets are secured on a link when MACsec is enabled, with the exception of all types
of Spanning Tree Protocol (STP) packets.
Options
Options include:
Required Privilege
Level
Related
Documentation
exercise
Syntax
Hierarchy Level
Description
Required Privilege
Level
Related
Documentation
962
This configuration statement is used to test if APS is operating correctly, it does not
interrupt regular APS operations.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
failover-delay
Syntax
Hierarchy Level
Release Information
Description
Options
failover-delay milliseconds;
[edit protocols vrrp]
963
family
Syntax
964
family family {
accounting {
destination-class-usage;
source-class-usage {
(input | output | input output);
}
}
access-concentrator name;
address address {
... the address subhierarchy appears after the main [edit interfaces interface-name unit
logical-unit-number family family-name] hierarchy ...
}
bundle interface-name;
core-facing;
demux-destination {
destination-prefix;
}
demux-source {
source-prefix;
}
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
group filter-group-number;
input filter-name;
input-list [ filter-names ];
output filter-name;
output-list [ filter-names ];
}
interface-mode (access | trunk);
ipsec-sa sa-name;
keep-address-and-control;
mac-validate (loose | strict);
max-sessions number;
max-sessions-vsa-ignore;
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;
receive-options-packets;
receive-ttl-exceeded;
remote (inet-address address | mac-address address);
rpf-check {
fail-filter filter-name
mode loose;
}
sampling {
input;
output;
}
service {
input {
post-service-filter filter-name;
service-set service-set-name <service-filter filter-name>;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
service-name-table table-name;
short-cycle-protection <lockout-time-min minimum-seconds lockout-time-max
maximum-seconds>;
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
translate-plp-control-word-de;
unnumbered-address interface-name destination address destination-profile profile-name;
vlan-id number;
vlan-id-list [number number-number];
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;
eui-64;
master-only;
multipoint-destination address dlci dlci-identifier;
multipoint-destination address {
epd-threshold cells;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);
shaping {
(cbr rate | rtvbr burst length peak rate sustained rate | vbr burst length peak rate
sustained rate);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
preferred;
primary;
vrrp-groupgroup-id {
(accept-data | no-accept-data);
advertise-interval seconds;
authentication-key key;
authentication-type authentication;
fast-interval milliseconds;
965
(preempt | no-preempt) {
hold-time seconds;
}
priority number;
track {
interface interface-name {
bandwidth-threshold bits-per-second priority-cost priority;
priority-cost priority;
}
priority-hold-time seconds;
route prefix routing-instance instance-name priority-cost priority;
}
}
virtual-address [ addresses ];
}
virtual-link-local-address ipv6-address;
}
}
Hierarchy Level
Release Information
Description
NOTE: Not all subordinate stanzas are available to every protocol family.
966
Options
familyProtocol family:
bridge(M Series and T Series routers only) Configure only when the physical interface
ethernet-switching(M Series and T Series routers only) Configure only when the
vpls(M Series and T Series routers only) Virtual private LAN service
967
fast-aps-switch
Syntax
Hierarchy Level
Release Information
Description
fast-aps-switch;
[edit interfaces interface-name sonet-options aps]
NOTE:
Required Privilege
Level
Related
Documentation
968
Configuring this statement reduces the APS switchover time only when
the Layer 2 circuit encapsulation type for the interface receiving traffic from
a Layer 2 circuit neighbor is SAToP.
To prevent the logical interfaces in the data path from being shut down,
configure appropriate hold-time values on all the interfaces in the data
path that support TDM.
fastether-options
Syntax
Hierarchy Level
Release Information
Description
fastether-options {
802.3ad {
aex (primary | backup);
lacp {
port-priority;
}
}
(flow-control | no-flow-control);
ignore-l3-incompletes;
ingress-rate-limit rate;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
}
[edit interfaces interface-name]
Required Privilege
Level
Related
Documentation
969
fec
Syntax
Hierarchy Level
Release Information
Description
Default
If you do not specify a mode, the default mode on PTX Series routers is gfec-sdfec for
routers supporting gfec-sdfec mode. . Else, the default value is gfec.
Options
efec(For M Series, MX Series, and SRX Series routers only) G.975.1 I.4 enhanced forward
error correction (EFEC) is configured to detect and correct bit errors.
gfec(For M Series, MX Series, and SRX Series routers only) G.709 generic forward error
correction (GFEC) mode is configured to detect and correct bit errors.
gfec-sdfec(For PTX Series routers only) GFEC and soft-decision forward error correction
(SD-FEC) modes are configured to detect and correct bit errors.
none(For M Series, MX Series, and SRX Series routers only) FEC mode is not configured.
ufec(MX Series and PTX Series routers only) Ultra Forward Error Correction (UFEC)
mode is configured to detect and correct bit errors.
Required Privilege
Level
Related
Documentation
970
fixed-stuff-bytes
Syntax
(fixed-stuff-bytes | no-fixed-stuff-bytes);
Hierarchy Level
Release Information
Description
Default
Options
Required Privilege
Level
Related
Documentation
971
flexible-vlan-tagging
Syntax
Hierarchy Level
Release Information
Description
flexible-vlan-tagging;
[edit interfaces aex],
[edit interfaces ge-fpc/pic/port],
[edit interfaces et-fpc/pic/port],
[edit interfaces ps0],
[edit interfaces xe-fpc/pic/port]
Required Privilege
Level
Related
Documentation
972
Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers on page 249
flow-control
Syntax
Hierarchy Level
(flow-control | no-flow-control);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces interface-name multiservice-options],
[edit interfaces interface-range name aggregated-ether-options],
[edit interfaces interface-range name ether-options]
Release Information
Description
For aggregated Ethernet, Fast Ethernet, and Gigabit Ethernet interfaces only, explicitly
enable flow control, which regulates the flow of packets from the router or switch to the
remote side of the connection. Enabling flow control is useful when the remote device
is a Gigabit Ethernet switch. Flow control is not supported on the 4-port Fast Ethernet
PIC.
Default
Required Privilege
Level
Related
Documentation
973
fnp
Syntax
Hierarchy Level
Release Information
Description
Options
fnp {
interval <100ms | 1s | 10s | 1m | 10m>;;
loss-threshold number
interface interface name {
domain-id domain-id
}
}
[edit protocols oam ethernet]
Required Privilege
Level
Related
Documentation
force switch
Syntax
Hierarchy Level
Description
Required Privilege
Level
Related
Documentation
974
Forces traffic to switch from the active path to the alternate path. If the working path is
the active path, traffic will be switched to the protection path. If the protection path is
the active path, traffic will be switched to the protection path.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
force-up
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
force-up;
[edit interfaces aggregathed-ethernet-options lacp]
Hierarchy Level
Release Information
Description
Options
forwarding-class class-name {
loss-priority (high | low);
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile output-priority-map classifier premium]
forwarding-class statement in the Class of Service Feature Guide for Routing Devices
975
Hierarchy Level
Release Information
Description
forwarding-mode {
(sa-multicast | ...the following vlan-steering statement...);
vlan-steering {
vlan-rule (high-low | odd-even);
}
}
[edit chassis fpc slot pic slot]
Required Privilege
Level
Related
Documentation
976
Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP on
page 414
Hierarchy Level
Release Information
Description
forwarding-mode {
sa-multicast
}
[edit chassis fpc slot pic slot port port-number]
Required Privilege
Level
Related
Documentation
977
frame-error
Syntax
Hierarchy Level
Release Information
Description
frame-error count;
[edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds]
Options
978
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Configuring Threshold Values for Fault Events in an Action Profile on page 614
frame-period
Syntax
Hierarchy Level
Release Information
Description
frame-period count;
[edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds]
Options
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Configuring Threshold Values for Fault Events in an Action Profile on page 614
979
frame-period-summary
Syntax
Hierarchy Level
Release Information
Description
frame-period-summary count;
[edit protocols oam ethernet link-fault-management action-profile event link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds]
Options
980
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Configuring Threshold Values for Fault Events in an Action Profile on page 614
Release Information
Description
NOTE:
Default
Options
The T4000 Core Router supports only LAN PHY mode in Junos OS Release
12.1R1. Starting with Junos OS Release 12.1R2, WAN PHY mode is supported
on the T4000 routers with the 12-port 10-Gigabit Ethernet LAN/WAN PIC
with SFP+ (PF-12XGE-SFPP). Starting with Junos OS Release 12.2, WAN
PHY mode is supported on the T4000 routers with the 24-port 10-Gigabit
Ethernet LAN/WAN PIC with SFP+ (PF-24XGE-SFPP).
On PTX Series routers, WAN PHY mode is supported only on the 24-port
10-Gigabit Ethernet LAN/WAN PIC with SFP+ .
When the PHY mode changes, interface traffic is disrupted because of port
reinitialization.
981
gigether-options
Syntax
982
gigether-options {
802.3ad {
aex (primary | backup);
lacp {
port-priority;
}
}
(asynchronous-notification | no-asynchronous-notification);
(auto-negotiation | no-auto-negotiation) remote-fault <local-interface-online |
local-interface-offline>;
(flow-control | no-flow-control);
ignore-l3-incompletes;
(loopback | no-loopback);
mpls {
pop-all-labels {
required-depth number;
}
}
no-auto-mdix
source-address-filter {
mac-address;
}
(source-filtering | no-source-filtering);
speed
ethernet-switch-profile {
(mac-learn-enable | no-mac-learn-enable);
tag-protocol-id [ tpids ];
ethernet-policer-profile {
input-priority-map {
ieee802.1p premium [ values ];
}
output-priority-map {
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;
}
}
}
}
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
gratuitous-arp-reply
Syntax
Hierarchy Level
(gratuitous-arp-reply | no-gratuitous-arp-reply);
[edit interfaces interface-name]
Release Information
Description
For Ethernet interfaces, enable updating of the Address Resolution Protocol (ARP) cache
for gratuitous ARPs.
Default
Required Privilege
Level
Related
Documentation
983
Description
Default
Options
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Specify the VLAN to which an interface is moved when no 802.1X supplicants are
connected on the interface. The VLAN specified must already exist on the switch.
None
vlan-idVLAN tag identifier of the guest VLAN.
vlan-nameName of the guest VLAN.
Required Privilege
Level
984
guard-interval
Syntax
Hierarchy Level
Release Information
Description
Options
guard-interval number;
[edit protocols protection-group ethernet-ring ring-name]
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
985
hardware-assisted-timestamping
Syntax
Hierarchy Level
Release Information
Description
hardware-assisted-timestamping;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring]
Required Privilege
Level
Related
Documentation
hold-interval (OAM)
Syntax
Hierarchy Level
hold-interval minutes;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name continuity-check]
Release Information
Description
The time to wait before flushing the maintenance association end point (MEP) database,
if no updates occur. The configurable range is 1 minute through 30240 minutes.
Options
Required Privilege
Level
Related
Documentation
986
hold-interval number;
[edit protocols protection-group ethernet-ring name]
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
hold-multiplier
Syntax
Hierarchy Level
Release Information
Description
hold-multiplier number;
[edit protocols lldp],
[edit routing-instances routing-instance-name protocols lldp]
Options
Default: 4 (giving 120 second LLDP cache lifetime with other defaults)
Range: 2 through 10
Required Privilege
Level
Related
Documentation
987
iccp
Syntax
Hierarchy Level
Release Information
iccp {
traceoptions; {
file <filename> <files number> <match regular-expression> <microsecond-stamp>
<size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
local-ip-address ip address;
session-establishment-hold-time value;
authentication-key string;
peer ip-address {
local-ip-address ip address;
session-establishment-hold-time value;
authentication-key string;
redundancy-group-id-list redundancy-group-id-list;
liveness-detection;
}
}
[edit protocols iccp]
[edit logical-systems logical-system-name protocols iccp]
Description
Configure Interchassis Control Protocol (ICCP) between the multichassis link aggregation
group (MC-LAG) peers. ICCP replicates forwarding information, validates configurations,
and propagates the operational state of the MC-LAG members.
Default
If you do not include this statement, no ICCP protocol tracing operations are performed.
Options
ICCP session.
authentication-key Specify TCP Message Digest 5 (MD5) option for an ICCP TCP session.
peer ip-addressSpecify the IP address of the peer that hosts an MC-LAG. You must
Required Privilege
Level
988
Related
Documentation
id {
mac-address mac-address;
port-id port-id-number;
}
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Options
Required Privilege
Level
Related
Documentation
Specify a MAC address and a port that traffic on the link must be from to be accepted
by the interface when MACsec is enabled using static secure association key (SAK)
security mode.
The remaining statements are explained separately.
adminTo view this statement in the configuration.
admin-controlTo add this statement to the configuration.
ieee802.1p
Syntax
Hierarchy Level
Release Information
Description
Options
Range: 0 through 7
Required Privilege
Level
Related
Documentation
989
igmp-snooping
Syntax
Hierarchy Level
Release Information
Description
990
igmp-snooping {
immediate-leave;
interface interface-name {
group-limit limit;
host-only-interface;
immediate-leave;
multicast-router-interface;
static {
group ip-address {
source ip-address;
}
}
}
proxy {
source-address ip-address;
}
query-interval seconds;
query-last-member-interval seconds;
query-response-interval seconds;
robust-count number;
vlan vlan-id {
immediate-leave;
interface interface-name {
group-limit limit;
host-only-interface;
immediate-leave;
multicast-router-interface;
static {
group ip-address {
source ip-address;
}
}
}
proxy {
source-address ip-address;
}
query-interval seconds;
query-last-member-interval seconds;
query-response-interval seconds;
robust-count number;
}
}
[edit bridge-domains bridge-domain-name protocols],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols]
[edit routing-instances routing-instance-name protocols]
[edit protocols]
NOTE: IGMP snooping must be disabled on the router before enabling ISSU.
Default
Options
Required Privilege
Level
Related
Documentation
ignore-l3-incompletes
Syntax
Hierarchy Level
ignore-l3-incompletes;
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]
Release Information
Description
Ignore the counting of Layer 3 incomplete errors on Fast Ethernet, Gigabit Ethernet, and
10-Gigabit Ethernet interfaces.
Required Privilege
Level
Related
Documentation
991
include-sci;
[edit security macsec connectivity-association connectivity-association-name]
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specifies that the SCI tag should be appended to each packet on a link that has enabled
MACsec.
SCI tags are automatically appended to packets leaving a MACsec-enabled interface
on an MX240, MX480, or MX960 router. This option is, therefore, redundant to be
configured.
This option is used only when connecting a router to a host device that requires SCI
tagging. SCI tags are eight octets long, so appending an SCI tag to all traffic on the link
adds a significant amount of unneeded overhead.
Default
Required Privilege
Level
Related
Documentation
992
SCI tagging is enabled on MX Series routers that have enabled MACsec using static
connectivity association key (CAK) security mode, by default.
adminTo view this statement in the configuration.
admin-controlTo add this statement to the configuration.
ingress-policer-overhead
Syntax
Hierarchy Level
Release Information
Description
Options
ingress-policer-overhead bytes;
[edit chassis fpc slot-number pic pic-number]
ingress-shaping-overhead
ingress-rate-limit
Syntax
Hierarchy Level
Release Information
Description
Options
ingress-rate-limit rate;
[edit interfaces interface-name fastether-options]
993
inner-tag-protocol-id
Syntax
Hierarchy Level
Release Information
Description
inner-tag-protocol-id tpid;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Default
Required Privilege
Level
Related
Documentation
994
Configuring Inner and Outer TPIDs and VLAN IDs on page 495
inner-vlan-id
Syntax
Hierarchy Level
Release Information
Description
inner-vlan-id number;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Options
numberVLAN ID number.
Configuring Inner and Outer TPIDs and VLAN IDs on page 495
995
input-policer
Syntax
Hierarchy Level
Release Information
Description
Options
input-policer policer-name;
[edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer]
Required Privilege
Level
Related
Documentation
996
input-priority-map
Syntax
Hierarchy Level
Release Information
Description
input-priority-map {
ieee802.1p premium [ values ];
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile]
[edit interfaces interface-name ether-options ethernet-switch-profile
ethernet-policer-profile]
Required Privilege
Level
Related
Documentation
997
input-three-color
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
998
input-three-color policer-name;
[edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer]
Hierarchy Level
Release Information
Description
input-vlan-map {
(pop | push | swap);
tag-protocol-id tpid;
vlan-id number;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Required Privilege
Level
Related
Documentation
999
input-vlan-map
Syntax
Hierarchy Level
Release Information
Description
input-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Required Privilege
Level
Related
Documentation
instance
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1000
instance vpls-instance-name;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain name]
interface
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1001
Hierarchy Level
Release Information
Description
interface interface-id {
maximum-requests integer;
quiet-period seconds;
reauthentication (disable | interval seconds);
retries integer;
server-timeout seconds;
supplicant (single);
supplicant-timeout seconds;
transmit-period seconds;
}
[edit protocols dot1x authenticator]
Default
The default values are provided for the options below on the respective statement pages.
Options
Request packet to the client before it times out the authentication session.
quiet-periodSpecify the number of seconds the port remains in the wait state following
retriesSpecify the number of tries after which the port remains in the wait state for
quiet-period seconds before reattempting the authentication.
server-timeoutSpecify the number of seconds the port waits for a reply when relaying
a response from the client to the authentication server before timing out and invoking
the server-fail action.
supplicant (single)Specify supplicant single mode. See the usage guidelines to configure
other modes.
supplicant-timeoutSpecify the number of seconds the port waits for a response when
relaying a request from the authentication server to the client before resending the
request.
transmit-periodSpecify the number of seconds the port waits before retransmitting the
1002
Required Privilege
Level
Related
Documentation
Hierarchy Level
Release Information
interface interface-name {
apply-action-profile profile-name;
link-discovery (active | passive);
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
}
[edit protocols oam ethernet link-fault-management]
Description
For Ethernet interfaces on M320, MX Series, and T Series routers, configure IEEE 802.3ah
Operation, Administration, and Management (OAM) support.
Options
OAM support.
The remaining statements are described separately.
Required Privilege
Level
Related
Documentation
1003
interface [interface-names];
[edit protocols authentication-access-control]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
Configure interfaces on which the specified MAC addresses are allowed to bypass RADIUS
authentication and allowed to connect to the LAN without authentication.
Options
Required Privilege
Level
interface-namesList of interfaces.
Related
Documentation
interface-down
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1004
interface-down;
[edit protocols oam ethernet connectivity-fault-management action-profile profile-name
default-actions]
interfaces
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation
interfaces { ... }
[edit]
1005
Hierarchy Level
interfaces interface-name {
connectivity-association connectivity-association-name;
}
[edit security macsec]
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Applies the specified connectivity association to the specified interface to enable MACsec.
One connectivity association can be applied to multiple interfaces.
You must always use this statement to apply a connectivity association to an interface
to enable MACsec. You must complete this configuration step regardless of whether
MACsec is enabled using static connectivity association key (CAK) security mode or
static secure association key (SAK) security mode.
If you are enabling MACsec using static SAK security mode and need to configure MACsec
on inbound and outbound traffic on the same interface, you must configure a connectivity
association with one secure channel for inbound traffic and a second secure channel for
outbound traffic. The connectivity association is then applied to the interface using this
statement to enable MACsec for traffic entering and leaving the interface.
Default
Required Privilege
Level
Related
Documentation
1006
interface-none
Syntax
Hierarchy Level
interface-none;
[edit protocols protection-group ethernet-ring ring-name east-interface]
[edit protocols protection-group ethernet-ring ring-name west-interface]
Description
Required Privilege
Level
Related
Documentation
Ethernet Ring Protection Using Ring Instances for Load Balancing on page 745
interface-status-tlv
Syntax
Hierarchy Level
Release Information
Description
Options
1007
interval
Syntax
Hierarchy Level
Release Information
Description
interval value;
[edit interfaces interface-name otn-options signal-degrade]
[edit interfaces interface-name otn-options odu-signal-degrade]
NOTE: Configuring a high BER threshold for signal degradation and a long
interval might cause the internal counter register to be saturated. Such a
configuration is ignored by the router, and the default values are used instead.
A system log message is logged for this error.
If you configure the BER thresholds at the [edit interfaces interface-name otn-options
signal-degrade] hierarchy level, then the thresholds are calculated using the pre-forward
error correction (pre-FEC) BER (the BER before FEC correction). These thresholds are
used for pre-FEC BER monitoring. See Understanding Pre-FEC BER Monitoring and BER
Thresholds on page 439 for more information about pre-FEC BER monitoring and
determining BER threshold settings.
If you configure the BER thresholds at the [edit interfaces interface-name otn-options
odu-signal-degrade] hierarchy level, then the thresholds are calculated using the post-FEC
BER (the BER after FEC correction). This BER is referred to as the optical channel data
unit (ODU) BER.
NOTE: You can configure ODU BER thresholds only at the [edit interfaces
interface-name otn-options odu-signal-degrade] hierarchy level on the
P2-100GE-OTN PIC.
Options
1008
the signal degradation threshold for 100 ms (10 ms * 10 intervals) for the
alarm to be raised, or below the clear threshold for 100 ms for the alarm to
be cleared.
Release Information
Description
Required Privilege
Level
Related
Documentation
1009
is-ma
Syntax
Hierarchy Level
Release Information
Description
Default
Options
(is-ma | no-is-ma);
[edit interfaces interface-name otn-options]
Required Privilege
Level
Related
Documentation
1010
Release Information
Description
isolated-vlan vlan-id;
[edit bridge-domains bridge-domain-name ],
[edit logical-systems logical-system-name routing-instances routing-instance-name
bridge-domains bridge-domain-name bridge-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name
bridge-domains bridge-domain-name ,
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name ],
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers.
Configure the specified isolated VLAN to be a secondary VLAN of the specified primary
VLAN. An isolated VLAN receives packets only from the primary VLAN and forwards
frames upstream to the primary VLAN.
Options
Required Privilege
Level
Related
Documentation
1011
iteration-count
Syntax
Hierarchy Level
Release Information
Description
Options
iteration-count count-value;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id
sla-iterator-profile profile-name]
iteration-period
Syntax
Hierarchy Level
Release Information
Description
Options
iteration-period iteration-period-value;
[edit protocols oam ethernet connectivity-fault-management performance-monitoring
sla-iterator-profiles profile-name]
1012
key key-string;
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specifies the static security key to exchange to enable MACsec using static secure
association key (SAK) security mode.
The key string is a 32-digit hexadecimal number. The key string and the security association
must match on both sides of an Ethernet connection to secure traffic using MACsec when
enabling MACsec using SAK security mode.
You must configure at least two security associations with unique security association
numbers and key strings to enable MACsec using static SAK security mode. MACsec
initially establishes a secure connection when a security association number and key
match on both ends of an Ethernet link. After a certain number of Ethernet frames are
securely transmitted across the Ethernet link, MACsec automatically rotates to a new
security association with a new security association number and key to maintain the
secured Ethernet link. This rotation continues each time a certain number of Ethernet
frames are securely transmitted across the secured Ethernet link, so you must always
configure MACsec to have at least two security associations.
Default
Options
channel. The key-string is a 32-digit hexadecimal string that is created by the user.
Required Privilege
Level
Related
Documentation
1013
key-server-priority priority-number;
[edit security macsec connectivity-association connectivity-association-name mka]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Specifies the key server priority used by the MACsec Key Agreement (MKA) protocol to
select the key server when MACsec is enabled using static connectivity association key
(CAK) security mode.
The switch with the lower priority-number is selected as the key server.
If the priority-number is identical on both sides of a point-to-point link, the MKA protocol
selects the device with the lower MAC address as the key server.
Default
Options
The priority-number can be any number between 0 and 255. The lower the number,
the higher the priority.
Required Privilege
Level
Related
Documentation
1014
lacp (802.3ad)
Syntax
Hierarchy Level
Release Information
Description
Options
lacp {
port-priority port-priority
}
[edit interfaces interface-name fastether-options 802.3ad],
[edit interfaces interface-name gigether-options 802.3ad]
Required Privilege
Level
Related
Documentation
1015
Hierarchy Level
Release Information
Description
lacp {
(active | passive);
admin-key key;
accept-data;
fast-failover;
link-protection {
disable;
(revertive |non-revertive);
}
periodic interval;
system-id mac-address;
system-priority priority;
}
[edit interfaces aex aggregated-ether-options]
[edit logical-systems logical-system-name interfaces aeX aggregated-ether-options]
NOTE: When you configure the accept-data statement at the [edit interfaces
aeX aggregated-ether-options lacp] hierarchy level, this behavior occurs:
Default
Options
1016
When LACP is down and a member link receives packets, the router or
switch does not process packets as defined in the IEEE 802.1ax standard.
According to this standard, the packets should be dropped, but they are
processed instead because the accept-data statement is configured.
If you do not specify LACP as either active or passive, LACP remains passive.
activeInitiate transmission of LACP packets.
fast-failoverSpecify to override the IEEE 802.3ad standard and allow the standby link
laser-enable
Syntax
Hierarchy Level
Release Information
Description
Default
Options
(laser-enable | no-laser-enable);
[edit interfaces interface-name otn-options]
Required Privilege
Level
Related
Documentation
1017
layer2-policer
Syntax
Hierarchy Level
Release Information
Description
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number],
Two-color
Two-color and tricolor policers are configured at the [edit firewall] hierarchy level.
Options
1018
level
Syntax
Hierarchy Level
Release Information
Description
Options
level number;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name]
belongs.
Range: 0 through 7
Required Privilege
Level
Related
Documentation
Release Information
Description
Options
level value;
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name action log-and-generate-ais]
Range: 1 through 7
Required Privilege
Level
Related
Documentation
1019
line-loopback
Syntax
Hierarchy Level
Release Information
Description
Default
Options
(line-loopback-enable | no-line-loopback);
[edit interfaces interface-name otn-options]
Required Privilege
Level
Related
Documentation
linktrace
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1020
linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
[edit protocols oam ethernet connectivity-fault-management]
link-adjacency-loss
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
link-adjacency-loss;
[edit protocols oam ethernet link-fault-management action-profile event]
link-discovery
Syntax
Hierarchy Level
Release Information
Description
Options
monitors the peer on the link if the peer also supports IEEE 802.3ah OAM functionality.
In passive mode, the peer initiates the discovery process. Once the discovery process
is initiated, both sides participate in discovery.
Required Privilege
Level
Related
Documentation
1021
link-down
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
link-down;
[edit protocols oam ethernet link-fault-management ]
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
link-event-rate
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1022
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
[edit protocols oam ethernet link-fault-management action-profile event]
Configuring Threshold Values for Fault Events in an Action Profile on page 614
link-fault-management
Syntax
Hierarchy Level
Release Information
Description
link-fault-management {
action-profile profile-name {
action {
link-down;
send-critical-event;
syslog;
}
event {
link-adjacency-loss;
link-event-rate {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
protocol-down;
}
}
interface interface-name {
apply-action-profile profile-name;
link-discovery (active | passive);
loopback-tracking;
pdu-interval interval;
pdu-threshold threshold-value;
remote-loopback;
event-thresholds {
frame-error count;
frame-period count;
frame-period-summary count;
symbol-period count;
}
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
}
}
[edit protocols oam ethernet]
Required Privilege
Level
1023
Related
Documentation
1024
link-mode
Syntax
Hierarchy Level
Release Information
Description
Options
link-mode mode;
[edit interfaces interface-name],
[edit interfaces interface-name ether-options],
[edit interfaces ge-pim/0/0 switch-options switch-port port-number]
Default: Fast Ethernet interfaces, can operate in either full-duplex or half-duplex mode.
The routers management Ethernet interface, fxp0 or em0, and the built-in Fast
Ethernet interfaces on the FIC (M7i router) autonegotiate whether to operate in
full-duplex or half-duplex mode. Unless otherwise noted here, all other interfaces
operate only in full-duplex mode.
NOTE:
Required Privilege
Level
Related
Documentation
1025
1026
link-protection
Syntax
Hierarchy Level
Release Information
Description
linkprotection {
disable;
(revertive |non-revertive);
}
[edit interfaces aex aggregated-ether-options]
[edit interfaces aex aggregated-ether-options lacp]
For LACP standards link protection, specify link-protection at the following hierarchy
levels:
For global LACP link protection, specify at [edit chassis aggregated-devices ethernet
lacp]
1027
Related
Documentation
1028
Release Information
Description
Options
link-speed speed;
[edit interfaces aex aggregated-ether-options],
[edit interfaces interface-range name aggregated-ether-options],
[edit interfaces interface-range name aggregated-sonet-options]
Aggregated Ethernet links on T Series routers can be configured to operate at one of the
following speeds:
1029
Required Privilege
Level
Related
Documentation
Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on page 148
Description
Options
mixedFor aggregated SONET/SDH links on T Series routers, you can mix interface
1030
lldp
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
lldp {
advertisement-interval seconds;
disable;
hold-multiplier number;
interface (all | interface-name) {
disable;
}
lldp-configuration-notification-interval seconds;
management-address ip-management-address;;
port-description-type {
interface-alias;
interface-description;
}
port-id-subtype {
interface-name;
locally-assigned;
}
ptopo-configuration-maximum-hold-time seconds;
ptopo-configuration-trap-interval seconds;
traceoptions {
file filename <files number> <size maximum-file-size> <world-readable |
no-world-readable>;
flag flag <disable>;
}
transmit-delay seconds;
}
[edit protocols],
[edit routing-instances routing-instance-name protocols]
1031
lldp-configuration-notification-interval
Syntax
Hierarchy Level
Release Information
Description
Options
lldp-configuration-notification-interval seconds;
[edit protocols lldp],
[edit routing-instances routing-instance-name protocols lldp]
1032
Hierarchy Level
Release Information
Description
lmi {
status-counter count;
polling-verification-timer value;
interface name {
uni-id uni-name;
status-counter number;
polling-verification-timer value;
evc-map-type (all-to-one-bundling | bundling | service-multiplexing);
evc evc-name {
default-evc;
vlan-list vlan-id-list;
}
}
}
[edit protocols oam ethernet]
Options
Required Privilege
Level
1033
Related
Documentation
load-balance
Syntax
Hierarchy Level
load-balance {
adaptive{
pps;
scan-interval multiple;
tolerance percentage;
}
no-adaptive;
per-packet;
}
[edit interfaces aex aggregated-ether-options]
Release Information
Description
Load-balances the received traffic across all the available paths of aggregated Ethernet
bundles for better link utilization.
Options
adaptive (MX Series and PTX Series) Corrects a genuine traffic imbalance by using a
1034
Hierarchy Level
Release Information
load-balance-stateful {
per-flow;
rebalance interval;
load-type (low | medium | large);
}
[edit interfaces aeX unit logical-unit-number forwarding-options]
Description
Define the capability to perform uniform load balancing and also perform rebalancing is
introduced on MX Series routers with MPCs, except MPC3Es and MPC4Es. Rebalancing
is not supported when load-balancing is skewed or distorted owing to a change in the
number of flows. The mechanism to record and retain states for the flows and distribute
the traffic load accordingly is added. As a result, for m number of flows, they are distributed
among n member links of a LAG bundle or among the unilist of next-hops in an ECMP
link. This method of splitting the load among member links is called stateful load balancing
and it uses 5-tuple information (source and destination addresses, protocol, source and
destination ports). Such a method can be mapped directly to the flows, or to a precompute
hash based on certain fields in the flow. As a result, the deviation observed on each child
link is reduced.
Options
Ethernet interfaces.
Required Privilege
Level
Related
Documentation
1035
Options
that flow on the specified aggregated Ethernet interface is relatively higher (between
100 and 1000 flows).
largeDefine a high load-balancing method if the number of flows that flow on the
1036
local-loopback
Syntax
Hierarchy Level
Release Information
Description
Default
Options
(local-loopback-enable | no-local-loopback);
[edit interfaces interface-name otn-options]
Required Privilege
Level
Related
Documentation
lockout
Syntax
Hierarchy Level
Description
Required Privilege
Level
Related
Documentation
Configure a lockout of the protection path, forcing the use of the working path and locking
out the protect path regardless of anything else.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
1037
log-and-generate-ais
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1038
log-and-generate-ais {
interval (1m | 1s);
level level;
priority level;
}
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name action]
logical-interface-policer
Syntax
Hierarchy Level
Release Information
Description
logical-interface-policer;
[edit dynamic-profiles profile-name firewall policer policer-name],
[edit dynamic-profiles profile-name firewall three-color-policer name],
[edit firewall atm-policeratm-policer-name]
[edit firewall policer policer-name],
[edit firewall policer policer-template-name],
[edit firewall three-color-policer policer-name],
[edit logical-systems logical-system-name firewall policer policer-name],
[edit logical-systems logical-system-name firewall three-color-policer name]
Required Privilege
Level
Related
Documentation
action
action
1039
Release Information
Description
(loopback | no-loopback);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options],
[edit interfaces interface-range name ether-options]
NOTE:
Required Privilege
Level
Related
Documentation
1040
loopback-tracking
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
loopback-tracking;
[edit protocols oam ethernet link-fault-management]
loss-priority
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1041
loss-threshold
Syntax
Hierarchy Level
Release Information
loss-threshold number;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name continuity-check]
Description
Specify the number of continuity check messages lost before marking the remote MEP
as down.
Options
numberThe number of continuity check messages that can be lost before the remote
1042
lowest-priority-defect
Syntax
Hierarchy Level
Release Information
Description
Options
cross-connect defects.
no-defectAllows no defects.
rem-err-xconAllows only not receiving CCM, erroneous CCM, and cross-connect CCM
defects.
xconAllows only cross-connect CCM defects.
Required Privilege
Level
Related
Documentation
Configuring the Lowest Priority Defect for Which an MEP Should Generate an Alarm
on page 538
1043
mac
Syntax
Hierarchy Level
Release Information
Description
mac mac-address;
[edit interfaces interface-name]
Options
mac-addressMAC address. Specify the MAC address as six hexadecimal bytes in one
mac (IRB)
Syntax
Hierarchy Level
Release Information
Description
Options
mac mac-address;
[edit interfaces irb unit logical-unit-number ]
1044
Hierarchy Level
Release Information
Description
For 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), for Gigabit Ethernet
DPCs on MX Series routers, and 100-Gigabit Ethernet Type 5 PIC with CFP, specify a
remote MAC address on which to count incoming and outgoing packets.
Options
mac-addressMAC address. Specify the MAC address as six hexadecimal bytes in one
Required Privilege
Level
Related
Documentation
1045
mac-address (MACsec)
Syntax
mac-address mac-address;
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specify a MAC address to enable MACsec using static secure association key (SAK)
security mode. The mac-address variables must match on the sending and receiving ends
of a link to enable MACsec using static SAK security mode.
If you are configuring a MAC address on a secure channel in the outbound direction, you
should specify the MAC address of the interface as the mac-address.
If you are configuring a MAC address on a secure channel in the inbound direction, you
should specify the MAC address of the interface at the other end of the link as the
mac-address.
You only use this configuration option when you are configuring MACsec using static SAK
security mode. This option does not need to be specified when you are enabling MACsec
using static connectivity association key (CAK) security mode.
Default
Options
Required Privilege
Level
Related
Documentation
1046
mac-learn-enable
Syntax
Hierarchy Level
Release Information
Description
mac-learn-enable;
[edit interfaces interface-name gigether-options ethernet-switch-profile]
[edit interfaces aex aggregated-ether-options ethernet-switch-profile]
Required Privilege
Level
Related
Documentation
1047
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
Configure MAC RADIUS authentication for specific interfaces. MAC RADIUS authentication
allows LAN access to permitted MAC addresses. When a new MAC address appears on
an interface, the switch consults the RADIUS server to check whether the MAC address
is a permitted address. If the MAC address is configured on the RADIUS server, the device
is allowed access to the LAN.
If MAC RADIUS is configured, the switch first tries to get a response from the host for
802.1X authentication. If the host is unresponsive, the switch attempts to authenticate
using MAC RADIUS.
To restrict authentication to MAC RADIUS only, use the restrict option. In restrictive mode,
all 802.1X packets are eliminated and the attached device on the interface is considered
a nonresponsive host.
Options
no other 802.1X authentication methods, such as guest VLAN, are needed on the
interface, and eliminates the delay that occurs while the switch determines that a
connected device is a non-802.1X-enabled host.
Required Privilege
Level
1048
mac-validate
Syntax
Hierarchy Level
Release Information
Description
Enable IP and MAC address validation for static Ethernet, IP demux interfaces, and VLAN
demux interfaces.
Options
looseForwards incoming packets when both the IP source address and the MAC source
address match one of the trusted address tuples. Drops packets when the IP source
address matches one of the trusted tuples, but the MAC address does not match
the MAC address of the tuple. Continues to forward incoming packets when the
source address of the incoming packet does not match any of the trusted IP
addresses.
strictForwards incoming 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.
Required Privilege
Level
Related
Documentation
1049
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1050
macsec {
connectivity-association connectivity-association-name {
exclude-protocol protocol-name;
include-sci;
mka {
must-secure;
key-server-priority priority-number;
transmit-interval interval;
}
no-encryption;
offset (0|30|50);
pre-shared-key {
cak hexadecimal-number;
ckn hexadecimal-number;
}
replay-protect{
replay-window-size number-of-packets;
}
secure-channel secure-channel-name {
direction (inbound | outbound);
encryption ;
id {
mac-address mac-address;
port-id port-id-number;
}
offset (0|30|50);
security-association security-association-number {
key key-string;
}
}
security-mode security-mode;
}
interfaces interface-name {
connectivity-association connectivity-association-name;
}
}
[edit security]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Configure Media Access Control Security (MACsec) on MX Series routers.
The remaining statements are explained separately.
adminTo view this statement in the configuration.
admin-controlTo add this statement to the configuration.
maintenance-association
Syntax
Hierarchy Level
Release Information
Description
Options
maintenance-association ma-name {
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
continuity-check {
hold-interval minutes;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number;
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon );
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name]
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
1051
maintenance-domain
Syntax
Hierarchy Level
Release Information
Description
maintenance-domain domain-name {
bridge-domain name <vlan-id [ vlan-ids ]>;
instance vpls-instance-name;
level number;
maintenance-association ma-name {
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
continuity-check {
hold-interval minutes;
interval (10m | 10s | 1m | 1s| 100ms);
loss-threshold number
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
lowest-priority-defect (all-defects | err-xcon | mac-rem-err-xcon | no-defect |
rem-err-xcon | xcon );
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
mip-half-function(none | default | explicit);
name-format (character-string | none | dns | mac+2oct);
}
virtual-switch name {
bridge-domain name <vlan-id [ vlan-ids ]>;
}
}
[edit protocols oam ethernet connectivity-fault-management]
NOTE: For MX Series Routers, you can configure multiple down MEPs for a
single instance of maintenance domain identifier and maintenance
1052
Options
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
major-ring-name
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
major-ring-name name;
[edit protocols protection-group ethernet-ring ring-name]
1053
manual switch
Syntax
Hierarchy Level
Description
Required Privilege
Level
Related
Documentation
Forces traffic to switch from the active path to the alternate path, even in the absence
of a failure on the working path. If the working path is the active path, traffic will be
switched to the protection path. If the protection path is the active path, traffic will be
switched to the protection path.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
master-only
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1054
master-only;
[edit groups rex interfaces (fxp0 | em0) unit logical-unit-number family family address],
[edit groups rex logical-systems logical-system-name interfaces fxp0 unit logical-unit-number
family family address],
[edit interfaces (fxp0 | em0) unit logical-unit-number family family address],
[edit logical-systems logical-system-name interfaces fxp0 unit logical-unit-number family
family address]
max-sessions number;
[edit protocols pppoe service-name-tables table-name service service-name]
Options
numberMaximum number of active PPPoE sessions that the router can establish with
the specified PPPoE service name table entry, in the range 1 to the platform-specific
maximum PPPoE sessions supported for your router. The default value is equal to
the maximum number of PPPoE sessions supported on your routing platform.
For information about scaling values for PPPoE interfaces, access the Subscriber
Management Scaling Values (XLS) spreadsheet from the Downloads box on the
Junos OS Subscriber Management pathway page for the current release.
Required Privilege
Level
Related
Documentation
Limiting the Number of Active PPPoE Sessions Established with a Specified Service Name
1055
Release Information
Description
Configure the router to ignore (clear) the value returned by RADIUS in the
Max-Clients-Per-Interface Juniper Networks vendor-specific attribute (VSA) [26-143],
and restore the PPPoE maximum session value on the underlying interface to the value
configured in the CLI with the max-sessions statement. The PPPoE maximum session
value specifies the maximum number of concurrent static or dynamic PPPoE logical
interfaces (sessions) that the router can activate on the PPPoE underlying interface, or
the maximum number of active static or dynamic PPPoE sessions that the router can
establish with a particular service entry in a PPPoE service name table.
Default
If you do not include the max-sessions-vsa-ignore statement, the maximum session value
returned by RADIUS in the Max-Clients-Per-Interface VSA takes precedence over the
PPPoE maximum session value configured with the max-sessions statement.
Required Privilege
Level
Related
Documentation
1056
max-sessions-vsa-ignore;
maximum-links
Syntax
Hierarchy Level
Release Information
Description
maximum-links maximum-links-limit;
[edit chassis aggregated-devices]
Options
network-services
1057
maximum-requests
Syntax
Hierarchy Level
Release Information
Description
Options
maximum-requests times;
[edit protocols dot1x authenticator interface interface-id]
maximum-requests number;
[edit protocols authentication-access-control interface (all | [interface-names]) dot1x]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
For 802.1X authentication, configure the maximum number of times an EAPOL request
packet is retransmitted to the supplicant before the authentication session times out.
Default
Options
Range: 1 through 10
Default: 2
Required Privilege
Level
1058
mc-ae
Syntax
Hierarchy Level
Release Information
Description
Options
mc-ae {
chassis-id chassis-id;
events {
iccp-peer-down;
force-icl-down;
prefer-status-control-active;
}
init-delay-time seconds;
mc-ae-id mc-ae-id;
mode (active-active | active-standby);
redundancy-group group-id;
revert-time revert-time;
status-control (active | standby);
switchover-mode (non-revertive |revertive);
}
[edit interfaces aeX aggregated-ether-options],
[edit logical-systems logical-system-name interfaces aeX aggregated-ether-options]
logical interface.
prefer-status-control-activeSpecify that the node configured as status-control
active become the active node if the peer of this node goes down.
1059
init-delay-time secondsTo minimize traffic loss, specify the number of seconds in which
to delay bringing the multichassis aggregated Ethernet interface back to the up state
when you reboot an MC-LAG peer.
mc-ae-id mc-ae-idSpecify the identification number of the MC-LAG device. The two
MC-LAG network devices that manage a given MC-LAG must have the same
identification number.
Range: 1 through 65,535
mode (active-active | active-standby)Specify whether the MC-LAG is in active-active
or active-standby mode.
NOTE: You can configure IPv4 (inet) and IPv6 (inet6) addresses on
mc-ae interfaces when the active-standby mode is configured.
1060
link switchover to the preferred node when the active node is available.
init-delay-time secondsTo minimize traffic loss, specify the number of seconds by which
Active-Active Bridging and VRRP over IRB Functionality on MX Series Routers Overview
Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation
on MX Series Routers
1061
measurement-type
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1062
mep
Syntax
Hierarchy Level
Release Information
Description
Options
mep mep-id {
action-profile action-profile-name
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
priority number;
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
}
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name]
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
1063
Options
Statement introduced before Junos OS Release 14.1R1 and 14.2 for MX Series.
Configure the minimum bandwidth unit for an aggregated Ethernet bundle as bps, Gbps,
Kbps, or Mbps and the bandwidth value from 1 through 128,000.
unitMinimum bandwidth unit for the aggregated Ethernet bundle as bps, Gbps, Kbps,
or Mbps.
valueMinimum bandwidth value from 1 through 128,000.
Required Privilege
Level
Related
Documentation
1064
Configuring Mixed Rates and Mixed Modes on Aggregated Ethernet Bundles on page 148
minimum-links
Syntax
Hierarchy Level
Release Information
Description
Options
minimum-links number;
[edit interfaces aex aggregated-ether-options],
[edit interfaces aex aggregated-sonet-options],
[edit interfaces interface-name mlfr-uni-nni-bundle-options],
[edit interfaces interface-name unit logical-unit-number],
[edit interfaces interface-range range aggregated-ether-options],
[edit interfaces interface-range range aggregated-sonet-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Range: On M120, M320, MX Series, T Series, and TX Matrix routers with Ethernet
interfaces, the valid range for minimum-links number is 1 through 64. When the
maximum value (16) is specified, all configured links of a bundle must be up for the
bundle to be labeled up.On all other routers and on EX Series switches, other than
EX8200 switches, the range of valid values for minimum-links number is 1 through
8. When the maximum value (8) is specified, all configured links of a bundle must
be up for the bundle to be labeled upOn EX8200 switches, the range of valid values
for minimum-links number is 1 through 12. When the maximum value (12) is specified,
all configured links of a bundle must be up for the bundle to be labeled up.
Default: 1
Required Privilege
Level
Related
Documentation
1065
mip-half-function
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1066
mixed-rate-mode
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
mixed-rate-mode;
[edit chassis fpc slot-number pic pic-number mixed-rate-mode],
[edit chassis lcc number fpc slot-number pic pic-number mixed-rate-mode] (Routing Matrix)
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
mka {
must-secure;
key-server-priority priority-number;
transmit-interval interval;
}
[edit security macsec connectivity-association connectivity-association-name]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Specify parameters for the MACsec Key Agreement (MKA) protocol.
The remaining statements are explained separately.
adminTo view this statement in the configuration.
admin-controlTo add this statement to the configuration.
1067
monitor-end-point
Syntax
Hierarchy Level
Release Information
Description
Default
Options
(monitor-end-point | no-monitor-end-point);
[edit interfaces interface-name otn-options odu-delay-management]
Required Privilege
Level
Related
Documentation
1068
must-secure;
[edit security macsec connectivity-association connectivity-association-name mka]
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specifies that all traffic travelling on the MACsec-secured link must be MACsec-secured
to be forwarded onward.
When the must-secure option is enabled, all traffic that is not MACsec-secured that is
received on the interface is dropped.
When the must-secure option is disabled, all traffic from devices that support MACsec
is MACsec-secured while traffic received from devices that do no support MACsec is
forwarded through the network.
The must-secure option is particularly useful in scenarios where multiple devices, such
as a phone and a PC, are accessing the network through the same Ethernet interface. If
one of the devices supports MACsec while the other device does not support MACsec,
the device that doesnt support MACsec can continue to send and receive traffic over
the networkprovided the must-secure option is disabledwhile traffic to and from the
device that supports MACsec is MACsec-secured. In this scenario, traffic to the device
that is not MACsec-secured must be VLAN-tagged.
Default
Required Privilege
Level
Related
Documentation
1069
mtu
Syntax
mtu bytes;
Hierarchy Level
Release Information
Description
Specify the maximum transmission unit (MTU) size for the media or protocol. The default
MTU size depends on the device type. Changing the media MTU or protocol MTU causes
an interface to be deleted and added again.
To route jumbo data packets on an integrated routing and bridging (IRB) interface or
routed VLAN interface (RVI) on EX Series switches, you must configure the jumbo MTU
size on the member physical interfaces of the VLAN that you have associated with the
IRB interface or RVI, as well as on the IRB interface or RVI itself (the interface named irb
or vlan, respectively).
CAUTION: For EX Series switches, setting or deleting the jumbo MTU size on
an IRB interface or RVI while the switch is transmitting packets might cause
packets to be dropped.
1070
NOTE:
The MTU for an IRB interface is calculated by removing the Ethernet header
overhead [6(DMAC)+6(SMAC)+2(EtherType)]. Because, the MTU is the
lower value of the MTU configured on the IRB interface and the MTU
configured on the IRBs associated bridge domain IFDs or IFLs, the IRB MTU
is calculated as follows:
In case of Layer 2 IFL configured with the vlan-tagging statement, the IRB
MTU is calculated by including a single VLAN 4 bytes overhead.
1071
NOTE:
If a packet whose size is larger than the configured MTU size is received on
the receiving interface, the packet is eventually dropped. The value
considered for MRU (maximum receive unit) size is also the same as the
MTU size configured on that interface.
Not all devices allow you to set an MTU value, and some devices have
restrictions on the range of allowable MTU values. You cannot configure
an MTU for management Ethernet interfaces (fxp0, em0, or me0) or for
loopback, multilink, and multicast tunnel devices.
On ACX Series routers, you can configure the protocol MTU by including
the mtu statement at the [edit interfaces interface-name unit
logical-unit-number family inet] or [edit interfaces interface-name unit
logical-unit-number family inet6] hierarchy level.
If you configure the protocol MTU at any of these hierarchy levels, the
configured value is applied to all families that are configured on the
logical interface.
If you are configuring the protocol MTU for both inet and inet6 families
on the same logical interface, you must configure the same value for
both the families. It is not recommended to configure different MTU size
values for inet and inet6 families that are configured on the same logical
interface.
Configured MTU
1072
For more information about configuring MTU for specific interfaces and router or switch
combinations, see Configuring the Media MTU.
Options
bytesMTU size.
Range: 256 through 9192 bytes, 256 through 9216 (EX Series switch interfaces), 256
through 9500 bytes (Junos OS 12.1X48R2 for PTX Series routers)
Default: 1500 bytes (INET, INET6, and ISO families), 1448 bytes (MPLS), 1514 bytes (EX
Series switch interfaces)
Required Privilege
Level
Related
Documentation
1073
Release Information
Description
multicast-router-interface;
[edit bridge-domains bridge-domain-name protocols igmp-snooping interface
interface-name],
[edit bridge-domains bridge-domain-name protocols igmp-snooping vlan vlan-id interface
interface-name],
[edit protocols igmp-snooping vlan (all | vlan-name) interface (all | interface-name)],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols
igmp-snooping interface interface-name],
[edit routing-instances routing-instance-name bridge-domains bridge-domain-name protocols
vlan vlan-id igmp-snooping interface interface-name]
Default
Required Privilege
Level
Related
Documentation
1074
host-only-interface
multi-chassis-protection
Syntax
Hierarchy Level
Release Information
Description
multi-chassis-protection {
peer a.b.c.d {
interface interface-name;
}
}
[edit interfaces interface-name]
NOTE: A bridge domain cannot have MC-AE logical interfaces which belong
to different redundancy groups.
If the Inter-Chassis Control Protocol (ICCP) connection is UP and the interchassis data
link (ICL) comes UP, the router configured as standby will bring up the MC-AE interfaces
shared with the peer.
The remaining statements are explained separately.
Options
Required Privilege
Level
Related
Documentation
Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation
on MX Series Routers
1075
name-format
Syntax
Hierarchy Level
Release Information
Description
Options
1076
native-vlan-id
Syntax
Hierarchy Level
Release Information
Description
native-vlan-id number;
[edit interfaces ge-fpc/pic/port],
[edit interfaces interface-name]
M Series routers with Gigabit Ethernet IQ PICs with SFP and Gigabit Ethernet IQ2 PICs
with SFP configured for 802.1Q flexible VLAN tagging
MX Series routers with Gigabit Ethernet DPCs and MICs, Tri-Rate Ethernet DPCs and
MICs, and 10-Gigabit Ethernet DPCs and MICs and MPCs configured for 802.1Q flexible
VLAN tagging
numberVLAN ID number.
1077
negotiate-address
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
negotiate-address;
[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]
negotiation-options
Syntax
Hierarchy Level
Release Information
Description
negotiation-options {
allow-remote-loopback;
no-allow-link-events;
}
[edit protocols oam link-fault-management interface interface-name]
Required Privilege
Level
Related
Documentation
1078
no-adaptive
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
no-adaptive;
[edit interfaces aex aggregated-ether-options load-balance]
no-allow-link-events
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
no-allow-link-events;
[edit protocols oam ethernet link-fault-management interface interface-name
negotiation-options]
1079
no-encryption;
[edit security macsec connectivity-association connectivity-association-name]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Disables MACsec encryption for a connectivity association that is configured to enable
MACsec using static connectivity association key (CAK) or dynamic security mode.
You can enable MACsec without enabling encryption. If a connectivity association that
has not enabled MACsec encryption is associated with an interface, traffic is forwarded
across the Ethernet link in clear text. You are, therefore, able to view this unencrypted
traffic when you are monitoring the link. The MACsec header is still applied to the packet,
however, and all MACsec data integrity checks are run on both ends of the link to ensure
the traffic does not represent a security threat.
This command is used to disable encryption when MACsec is configured using static CAK
or dynamic security mode only. When MACsec is configuring using static secure association
key (SAK) security mode, the encryption setting is managed in the secure channel using
the encryption configuration statement.
Default
Required Privilege
Level
Related
Documentation
1080
MACsec encryption is enabled if MACsec is enabled using static CAK or dynamic security
mode.
adminTo view this statement in the configuration.
admin-controlTo add this statement to the configuration.
no-auto-mdix
Syntax
Hierarchy Level
Release Information
Description
no-auto-mdix;
[edit interface ge-fpc/port/pic gigether-options]
Default
Options
Required Privilege
Level
Related
Documentation
no-gratuitous-arp-request
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation
no-gratuitous-arp-request;
[edit interfaces interface-name]
1081
no-keepalives
Syntax
Hierarchy Level
Release Information
Description
no-keepalives;
[edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Required Privilege
Level
Related
Documentation
Configuring Keepalives
Description
Default
Required Privilege
Level
no-mac-table-binding;
[edit protocols authentication-access-control]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
For 802.1X authentication, disable the removal of the session from the authentication
session table when the MAC address ages out of the Ethernet switching table.
Not enabled
routingTo view this statement in the configuration.
routing-controlTo add this statement to the configuration.
Related
Documentation
1082
no-odu-backward-frr-enable
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation
no-odu-backward-frr-enable;
[edit interfaces interface-name otn-options preemptive-fast-reroute]
no-odu-signal-degrade-monitor-enable
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation
no-odu-signal-degrade-monitor-enable;
[edit interfaces interface-name otn-options preemptive-fast-reroute]
1083
no-pre-classifier
Syntax
Hierarchy Level
Release Information
Description
no-pre-classifier;
[edit chassis fpc n pic n]
NOTE: For the 10-Gigabit Ethernet LAN/WAN PIC with SFP+ (model number
PD-5-10XGE-SFPP), the control queue has a rate limiter to limit the control
traffic to 2 Mbps (fixed, not user-configurable) per port. If the transit control
traffic crosses this limit, then it can cause drops on locally terminating control
traffic, causing flap of protocols such as BGP and OSPF. To avoid the control
traffic being dropped, configure the no-pre-classifier statement to disable
the control queue.
Default
Required Privilege
Level
Related
Documentation
The no-pre-classifier statement is not configured and the control queue is operational.
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
Description
Default
Required Privilege
Level
1084
no-reauthentication;
[edit protocols authentication-access-control interface (all | [interface-names]) dot1x]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
For 802.1X authentication, disables reauthentication.
Not disabled
routingTo view this statement in the configuration.
routing-controlTo add this statement to the configuration.
no-send-pads-ac-info
Syntax
no-send-pads-ac-info;
Hierarchy Level
Release Information
Description
NOTE: In Junos OS Release 12.1 and earlier, only the Service-Name, Host-Uniq,
Relay-Session-Id, and PPP-Max-Payload tags are contained in the PADS
packet by default. The AC-Name and AC-Cookie tags are not transmitted in
the PADS packet by default.
Required Privilege
Level
Related
Documentation
no-send-pads-error
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
no-send-pads-error;
[edit protocols pppoe]
1085
non-revertive (Interfaces)
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
non-revertive;
[edit interfaces aeX aggregated-ether-options lacp link-protection]
non-revertive
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1086
non-revertive;
[edit protocols protection-group ethernet-ring ring-name]
non-vc-mode
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
non-vc-mode;
[edit protocols protection-group ethernet-ring ring-name]
node-id
Syntax
Hierarchy Level
Release Information
Description
node-id mac-address;
[edit protocols protection-group ethernet-ring ring-name]
Required Privilege
Level
Related
Documentation
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
1087
number-of-frames
Syntax
Hierarchy Level
Release Information
Description
Options
number-of-frames value;
[edit interfaces interface-name otn-options odu-delay-management]
Required Privilege
Level
Related
Documentation
1088
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specifies the number of octets in an Ethernet frame that are sent in unencrypted plain-text
when encryption is enabled for MACsec.
Setting the offset to 30 allows a feature to see the IPv4 header and the TCP/UDP header
while encrypting the remaining traffic. Setting the offset to 50 allows a feature to see
the IPv6 header and the TCP/UDP header while encrypting the remaining traffic.
You would typically forward traffic with the first 30 or 50 octets unencrypted if a feature
needed to see the data in the octets to perform a function, but you otherwise prefer to
encrypt the remaining data in the frames traversing the link. Load balancing features, in
particular, typically need to see the IP and TCP/UDP headers in the first 30 or 50 octets
to properly load balance traffic.
You configure the offset in the [edit security macsec connectivity-association
connectivity-association-name] hierarchy when you are enabling MACsec using static
connectivity association key (CAK) or dynamic security mode.
You configure the offset in the [edit security macsec connectivity-association
connectivity-association-name secure-channelsecure-channel-name] hierarchy when you
are enabling MACsec using static secure association key (SAK) security mode.
Default
Options
0
0Specifies that no octets are unencrypted. When you set the offset to 0, all traffic on
NOTE: In IPv4 traffic, setting the offset to 30 allows a feature to see the
IPv4 header and the TCP/UDP header while encrypting the rest of the
traffic. An offset of 30, therefore, is typically used when a feature needs
this information to perform a task on IPv4 traffic.
50Specified that the first 50 octets of each Ethernet frame are unencrypted.
1089
NOTE: In IPv6 traffic, setting the offset to 50 allows a feature to see the
IPv6 header and the TCP/UDP header while encrypting the rest of the
traffic. An offset of 50, therefore, is typically used when a feature needs
this information to perform a task on IPv6 traffic.
Required Privilege
Level
Related
Documentation
1090
oam
Syntax
oam {
ethernet {
connectivity-fault-management {
action-profile profile-name {
default-actions {
interface-down;
}
}
performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
avg-fd-twoway-threshold;
avg-ifdv-twoway-threshold;
avg-flr-forward-threshold;
avg-flr-backward-threshold;
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
linktrace {
age (30m | 10m | 1m | 30s | 10s);
path-database-size path-database-size;
}
maintenance-domain domain-name {
level number;
name-format (character-string | none | dns | mac+2octet);
maintenance-association ma-name {
short-name-format (character-string | vlan | 2octet | rfc-2685-vpn-id);
protect-maintenance-association protect-ma-name;
remote-maintenance-association remote-ma-name;
continuity-check {
convey-loss-threshold;
hold-interval minutes;
interface-status-tlv;
interval (100ms | 10m | 10ms | 10s | 1m | 1s);
loss-threshold number;
port-status-tlv;
}
mep mep-id {
auto-discovery;
direction (up | down);
interface interface-name (protect | working);
1091
1092
Hierarchy Level
Release Information
Description
[edit protocols]
Required Privilege
Level
Related
Documentation
oc192
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
oc192;
[edit interfaces interface-name otn-options rate]
1093
odu-delay-management
Syntax
Hierarchy Level
Release Information
Description
odu-delay-management {
(bypass | no-bypass);
(monitor-end-point | no-monitor-end-point);
number-of-frames value;
(no-start-measurement | start-measurement;
}
[edit interfaces interface-name otn-options]
Default
If you omit the odu-delay-management statement, the ODU delay management options
are disabled.
Options
Required Privilege
Level
Related
Documentation
odu-backward-frr-enable
Syntax
Hierarchy Level
odu-backward-frr-enable;
[edit interfaces interface-name otn-options preemptive-fast-reroute]
Release Information
Description
Insert the ODU status into the transmitted OTN frames and monitor the received OTN
frames for the ODU BER status.
Default
Required Privilege
Level
Related
Documentation
1094
odu-signal-degrade
Syntax
Hierarchy Level
Release Information
Description
Default
odu-signal-degrade {
ber-threshold-clear;
ber-threshold-signal-degrade;
interval
}
[edit interfaces interface-name otn-options]
Options
Required Privilege
Level
Related
Documentation
ber-threshold-clear1E-09
ber-threshold-signal-degrade1E-06
interval10 ms
1095
odu-signal-degrade-monitor-enable
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation
odu-signal-degrade-monitor-enable;
[edit interfaces interface-name otn-options preemptive-fast-reroute]
odu-ttim-action-enable
Syntax
Hierarchy Level
Release Information
Description
Default
Options
(odu-ttim-action-enable | no-odu-ttim-action-enable);
[edit interfaces interface-name otn-options]
Required Privilege
Level
Related
Documentation
1096
optics-options
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
optics-options {
alarm low-light-alarm {
(link-down | syslog);
}
tca tca-identifier (enable-tca | no-enable-tca) (threshold number | threshold-24hrs number);
tx-power dbm;
warning low-light-warning {
(link-down | syslog);
}
wavelength nm;
}
[edit interfaces interface-name]
1097
otn-options
Syntax
Hierarchy Level
Release Information
1098
otn-options {
bytes (otn-options) transmit-payload-type value;
fec (efec | gfec | gfec-sdfec | none );
(is-ma | no-is-ma);
(laser-enable | no-laser-enable);
(line-loopback | no-line-loopback);
(local-loopback | no-local-loopback);
(odu-ttim-action-enable | no-odu-ttim-action-enable);
(otu-ttim-action-enable | no-otu-ttim-action-enable);
odu-delay-management {
(bypass | no-bypass);
(monitor-end-point | no-monitor-end-point);
number-of-frames value;
(no-start-measurement | start-measurement;
}
odu-signal-degrade {
ber-threshold-clear value;
ber-threshold-signal-degrade value;
interval value;
}
(prbs | no-prbs);
preemptive-fast-reroute {
(backward-frr-enable | no-backward-frr-enable);
(signal-degrade-monitor-enable | no-signal-degrade-monitor-enable);
odu-backward-frr-enable | no-odu-backward-frr-enable;
odu-signal-degrade-monitor-enable | no-odu-signal-degrade-monitor-enable;
}
rate {
(fixed-stuff-bytes | no-fixed-stuff-bytes);
oc192;
otu4;
(pass-through | no-pass-through);
}
signal-degrade {
ber-threshold-clear value;
ber-threshold-signal-degrade value;
interval value;
}
tca tca-identifier (enable-tca | no-enable-tca) (threshold number | threshold-24hrs number);
transport-monitoring;
trigger trigger-identifier;
tti tti-identifier;
}
[edit interfaces ge-fpc/pic/port]
[edit interfaces xe-fpc/pic/port]
[edit interfaces et-fpc/pic/port]
Specify the Ethernet optical transport network (OTN) interface and options.
The remaining statements are explained separately.
interfacesTo view this statement in the configuration.
interfaces-controlTo add this statement to the configuration.
otu-ttim-action-enable
Syntax
Hierarchy Level
Release Information
(otu-ttim-action-enable | no-otu-ttim-action-enable);
[edit interfaces interface-name otn-options]
Description
Specify whether consequent action for Optical Channel Transport Unit (OTU) TTIM is
enabled or disabled.
Default
If you omit the otu-ttim-action-enable statement, consequent action for OTU TTIM is
disabled.
Options
Required Privilege
Level
Related
Documentation
1099
otu4
Syntax
Hierarchy Level
Release Information
Description
Default
Options
Required Privilege
Level
Related
Documentation
1100
otu4;
[edit interfaces interface-name otn-options rate]
output-policer
Syntax
Hierarchy Level
Release Information
Description
Options
output-policer policer-name;
[edit interfaces interface-name unit logical-unit-number layer2-policer],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer]
Required Privilege
Level
Related
Documentation
1101
output-priority-map
Syntax
Hierarchy Level
Release Information
Description
output-priority-map {
classifier {
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile]
[edit interfaces interface-name ether-options ethernet-switch-profile
ethernet-policer-profile]
Required Privilege
Level
Related
Documentation
1102
output-three-color
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
output-three-color policer-name;
[edit interfaces interface-name unit logical-unit-number layer2-policer]
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
layer2-policer]
1103
Hierarchy Level
Release Information
Description
output-vlan-map {
(pop | push | swap);
tag-protocol-id tpid;
vlan-id number;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Required Privilege
Level
Related
Documentation
1104
output-vlan-map
Syntax
output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap | swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
Hierarchy Level
Release Information
Description
For Gigabit Ethernet IQ, 10-Port 10-Gigabit Ethernet SFPP interfaces, 100-Gigabit Ethernet
Type 5 PIC with CFP only, Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet,
and aggregated Ethernet interfaces, define the rewrite operation to be applied to outgoing
frames on this logical interface.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation
1105
pado-advertise
Syntax
Hierarchy Level
Release Information
Description
pado-advertise;
[edit protocols pppoe]
Required Privilege
Level
Related
Documentation
pass-through
Syntax
(pass-through | no-pass-through);
Hierarchy Level
Release Information
Description
Default
Options
Required Privilege
Level
Related
Documentation
1106
passive-monitor-mode
Syntax
Hierarchy Level
Release Information
Description
passive-monitor-mode;
[edit interfaces interface-name],
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Required Privilege
Level
Related
Documentation
multiservice-options
1107
path-database-size
Syntax
Hierarchy Level
Release Information
Description
Options
path-database-size path-database-size;
[edit protocols oam ethernet connectivity-fault-management linktrace]
pdu-interval
Syntax
Hierarchy Level
Release Information
Description
Options
pdu-interval interval;
[edit protocols oam ethernet link-fault-management interface interface-name]
1108
pdu-threshold
Syntax
Hierarchy Level
Release Information
Description
Options
pdu-threshold threshold-value;
[edit protocols oam ethernet link-fault-management interface interface-name]
Options
per-flow;
[edit interfaces aeX unit logical-unit-number forwarding-options load-balance-stateful]
1109
peer
Syntax
Hierarchy Level
Release Information
Description
Options
peer a.b.c.d {
interface interface-name;
}
[edit interfaces interface-name multi-chassis-protection]
interface-name-fpc/pic/port
Required Privilege
Level
Related
Documentation
1110
Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation
on MX Series Routers
performance-monitoring
Syntax
Hierarchy Level
Release Information
Description
performance-monitoring {
delegate-server-processing;
hardware-assisted-timestamping;
sla-iterator-profiles {
profile-name {
avg-fd-twoway-threshold;
avg-ifdv-twoway-threshold;
avg-flr-forward-threshold;
avg-flr-backward-threshold;
disable;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period connections;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
}
[edit protocols oam ethernet connectivity-fault-management]
Required Privilege
Level
Related
Documentation
1111
periodic
Syntax
Hierarchy Level
Release Information
Description
Options
periodic interval;
[edit interfaces aex aggregated-ether-options lacp],
[edit interfaces interface-range name aggregated-ether-options lacp]
Default: fast
Required Privilege
Level
Related
Documentation
1112
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
policer cfm-policer {
if-exceeding {
bandwidth-limit 8k;
burst-size-limit 2k;
}
then discard;
}
[edit firewall]
1113
Hierarchy Level
Release Information
Description
Options
policer {
all cfm-policer-name;
continuity-check cfm-policer-name;
other cfm-policer-name;
}
}
[edit protocols oam ethernet connectivity-fault-management]
specified.
other cfm-policer-namePolice all non-continuity check packets with the policer specified.
all cfm-policer-namePolice all CFM packets with policer specified. If the all option is
1114
Hierarchy Level
Release Information
Description
Options
policer {
all cfm-policer-name;
continuity-check cfm-policer-name;
other cfm-policer-name;
}
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain name
level number maintenance-association name]
session.
other cfm-policer-namePolice all non-continuity check packets belonging to this
session.
all cfm-policer-namePolice all CFM packets belonging to this session. If the all option
Required Privilege
Level
Related
Documentation
1115
policer (CoS)
Syntax
Hierarchy Level
Release Information
policer cos-policer-name {
aggregate {
bandwidth-limit bps;
burst-size-limit bytes;
}
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile]
Description
For Gigabit Ethernet IQ , Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit
Ethernet PIC and the built-in Gigabit Ethernet port on the M7i router), and 100-Gigabit
Ethernet Type 5 PIC with CFP, define a CoS policer template to specify the premium
bandwidth and burst-size limits, and the aggregate bandwidth and burst-size limits. The
premium policer is not supported on MX Series routers or for Gigabit Ethernet interfaces
with SFPs (except the 10-port Gigabit Ethernet PIC and the built-in Gigabit Ethernet port
on the M7i router).
Options
1116
policer (MAC)
Syntax
Hierarchy Level
Release Information
Description
policer {
input cos-policer-name;
output cos-policer-name;
}
[edit interfaces interface-name unit logical-unit-number accept-source-mac
mac-address mac-address],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
accept-source-mac mac-address mac-address]
NOTE:
On MX Series routers with Gigabit Ethernet or Fast Ethernet PICs, the following
considerations apply:
Options
Interface counters do not count the 7-byte preamble and 1-byte frame
delimiter in Ethernet frames.
In MAC statistics, the frame size includes MAC header and CRC before any
VLAN rewrite/imposition rules are applied.
In traffic statistics, the frame size encompasses the L2 header without CRC
after any VLAN rewrite/imposition rule.
aggregate bandwidth.
output cos-policer-nameName of one policer to specify the premium bandwidth and
aggregate bandwidth.
Required Privilege
Level
Related
Documentation
1117
pop
Syntax
Hierarchy Level
Release Information
pop;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Description
For Gigabit Ethernet IQ, 10-Gigabit Ethernet IQ2, and IQ2-E interfaces; 10-Gigabit Ethernet
LAN/WAN PIC; aggregated Ethernet interfaces using Gigabit Ethernet IQ interfaces;
100-Gigabit Ethernet Type 5 PIC with CFP; and Gigabit Ethernet, 10-Gigabit Ethernet,
40-Gigabit Ethernet, and aggregated Ethernet interfaces, specify the VLAN rewrite
operation to remove a VLAN tag from the top of the VLAN tag stack. The outer VLAN tag
of the frame is removed.
Required Privilege
Level
Related
Documentation
1118
pop-pop
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
pop-pop;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
1119
pop-swap
Syntax
Hierarchy Level
Release Information
Description
pop-swap;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Required Privilege
Level
Related
Documentation
1120
Removing the Outer VLAN Tag and Rewriting the Inner VLAN Tag on page 502
port-description-type
Syntax
Hierarchy Level
Release Information
Description
Options
port-description-type {
interface-alias;
interface-description;
}
[edit protocols lldp]
[edit routing- instances routing-instance-name protocols lldp]
TLV.
Default: By default, interface-alias is used for generation of port description TLV. The
interface-alias value is same as description of an interface configured by statement
set interface name description description.
NOTE: The LLDP MIB lldpLocPortDesc value gets changed depending on the
setting of port-description-type statement. That is:
Required Privilege
Level
Related
Documentation
1121
port-id port-id-number;
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specify a port ID in a secure channel when enabling MACsec using static secure association
key (SAK) security mode. The port IDs must match on a sending and receiving secure
channel on each side of a link to enable MACsec.
Once the port numbers match, MACsec is enabled for all traffic on the connection.
You only use this configuration option when you are configuring MACsec using static SAK
security mode. This option does not need to be specified when you are enabling MACsec
using static connectivity association key (CAK) security mode.
Default
Options
Required Privilege
Level
Related
Documentation
1122
No port ID is specified.
port-id-numberThe port ID number.
port-priority
Syntax
Hierarchy Level
Release Information
Description
Options
port-priority priority;
[edit interfaces interface-name gigether-options 802.3ad lacp]
1123
port-id-subtype
Syntax
Hierarchy Level
Release Information
Description
Options
port-id-subtype {
interface-name;
locally-assigned;
}
[edit protocols lldp]
[edit routing- instances routing-instance-name protocols lldp]
Default: Use the SNMP index of the interface to generate the port ID TLV. This is the
default option used to generate port ID TLV.
NOTE: The show lldp neighbors command displays the content of the port ID
TLV received from the peer in the port Info field. Changing the configuration
of port-id-subtype affects the display of the show lldp neighbors command
on the peer device running Junos OS.
When the value of port-id-subtype is set to locally-assigned, which is the
default value, the show lldp neighbors command on the peer device running
Junos OS displays the SNMP index as the port information for the local device.
When the value of port-id-subtype is set to interface-name, the show lldp
neighbors command on the peer device running Junos OS displays the
interface name as the port information for the local device.
The value of the MIB variable lldpLocPortId depends on the SNMP MIB object
entity that is used to generate the port ID TLV. If the port ID TLV generation
is configured to use the interface name in the set port-id-subtype
interface-name command, then the value of the MIB variable lldpLocPortId
is the interface name and not the SNMP index.
Required Privilege
Level
Related
Documentation
1124
port-status-tlv
Syntax
Hierarchy Level
Release Information
port-status-tlv blocked;
[edit protocols oam ethernet connectivity-fault-management action-profile tlv-action event]
Description
Define an action-profile consisting of various events and the action. Based on values of
port-status-tlv in the received CCM packets, specific action such as interface-down can
be taken using action-profile options.
Options
blockedWhen the incoming CCM packet contains port status TLV with value blocked,
1125
Hierarchy Level
Release Information
Description
1126
pp0 {
unit logical-unit-number {
keepalives interval seconds;
no-keepalives;
pppoe-options {
underlying-interface interface-name;
server;
}
ppp-options {
authentication [ authentication-protocols ];
chap {
challenge-length minimum minimum-length maximum maximum-length;
}
pap;
}
family inet {
unnumbered-address interface-name;
address address;
service {
input {
service-set service-set-name {
service-filter filter-name;
}
post-service-filter filter-name;
}
output {
service-set service-set-name {
service-filter filter-name;
}
}
}
filter {
input filter-name {
precedence precedence;
}
output filter-name {
precedence precedence;
}
}
}
}
}
[edit dynamic-profiles profile-name interfaces]
For information about creating static PPPoE interfaces, see Configuring PPPoE on
page 341
Hierarchy Level
Release Information
Description
ppm {
centralized;
}
[edit protocols lacp]
Default
Required Privilege
Level
Related
Documentation
Distributed PPM processing is enabled for all packets that use PPM.
routingTo view this statement in the configuration.
routing-controlTo add this statement to the configuration.
1127
pppoe-options
Syntax
Hierarchy Level
Release Information
Description
pppoe-options {
access-concentrator name;
auto-reconnect seconds;
(client | server);
service-name name;
underlying-interface interface-name;
}
[edit interfaces pp0 unit logical-unit-number],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number]
Required Privilege
Level
Related
Documentation
1128
Hierarchy Level
Release Information
Description
pppoe-underlying-options {
access-concentrator name;
dynamic-profile profile-name;
direct-connect
duplicate-protection;
max-sessions number;
max-sessions-vsa-ignore;
service-name-table table-name;
short-cycle-protection <lockout-time-min minimum-seconds> <lockout-time-max
maximum-seconds> <filter [aci]>;
}
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Required Privilege
Level
Related
Documentation
1129
Hierarchy Level
pre-shared-key {
cak hexadecimal-number;
ckn hexadecimal-number;
}
[edit security macsec connectivity-association connectivity-association-name]
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specifies the pre-shared key used to enable MACsec using static connectivity association
key (CAK) security mode.
A pre-shared key includes a connectivity association key name (CKN) and a connectivity
association key (CAK). A pre-shared key is exchanged between two devices at each end
of a point-to-point link to enable MACsec using static CAK security mode. The MACsec
Key Agreement (MKA) protocol is enabled after the pre-shared keys are successfully
verified and exchanged. The pre-shared keythe CKN and CAKmust match on both
ends of a link.
Default
Options
Required Privilege
Level
Related
Documentation
1130
Hierarchy Level
Release Information
Description
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile output-priority-map classifier]
Required Privilege
Level
Related
Documentation
premium (Policer)
Syntax
Hierarchy Level
Release Information
Description
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name]
Required Privilege
Level
Related
Documentation
1131
Release Information
Description
Options
priority priority-value;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id
sla-iterator-profile profile-namesla-iterator-profile]
frames.
Range: 0 through 7
Default: 0
Required Privilege
Level
Related
Documentation
Release Information
Description
Options
priority value;
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name action log-generate-ais]
Range: 0 through 7
Required Privilege
Level
Related
Documentation
1132
priority number;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id]
Release Information
Description
Options
packets.
Range: 0 through 7
Required Privilege
Level
Related
Documentation
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
propagate-tc
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
propagate-tc;
[edit protocols protection-group ethernet-ring ring-name]
1133
protection-group
Syntax
1134
protection-group {
ethernet-ring ring-name {
data-channel {
vlan number
}
east-interface {
control-channel channel-name {
vlan number;
interface name interface-name
}
}
guard-interval number;
node-id mac-address;
restore-interval number;
ring-protection-link-owner;
non-revertive;
wait-to-block-interval number;
major-ring-name name;
propagate-tc;
compatibility-version (1|2);
ring-id number;
non-vc-mode;
dot1p-priority number;
west-interface {
control-channel channel-name {
vlan number;
interface name interface-name
}
virtual-control-channel {
west-interface name;
east-interface name;
}
}
}
control-vlan (vlan-id | vlan-name);
east-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
}
}
control-channel channel-name {
vlan number;
interface name interface-name
}
}
data-channel {
vlan number
}
guard-interval number;
node-id mac-address;
restore-interval number;
ring-protection-link-owner;
west-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
}
control-channel channel-name {
vlan number;
interface name interface-name
}
}
}
guard-interval number;
restore-interval number;
traceoptions {
file filename <no-stamp> <world-readable | no-world-readable> <replace> <size size>;
flag flag;
}
}
Hierarchy Level
Release Information
Description
[edit protocols]
Required Privilege
Level
Related
Documentation
Ethernet Ring Protection Using Ring Instances for Load Balancing on page 745
Example: Configuring Load Balancing Within Ethernet Ring Protection for MX Series
Routers on page 752
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
1135
protocols
Syntax
Hierarchy Level
Release Information
Description
NOTE: Some platform and FPC combinations can not pass TCC encapsulated
ISO traffic. See Platforms/FPCs That Cannot Forward TCC Encapsulated ISO
Traffic for details.
Required Privilege
Level
Related
Documentation
1136
Hierarchy Level
Release Information
Description
Options
protocol-down
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
protocol-down;
[edit protocols oam ethernet link-fault-management action-profile event]
1137
ptopo-configuration-maximum-hold-time
Syntax
Hierarchy Level
Release Information
Description
Options
ptopo-configuration-maximum-hold-time seconds;
[edit protocols lldp],
[edit routing-instances routing-instance-name protocols lldp]
Default: 300
Range: 1 through 2147483647
Required Privilege
Level
Related
Documentation
ptopo-configuration-trap-interval
Syntax
Hierarchy Level
Release Information
Description
Options
ptopo-configuration-trap-interval seconds;
[edit protocols lldp],
[edit routing-instances routing-instance-name protocols lldp]
1138
push
Syntax
Hierarchy Level
Release Information
push;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Description
Specify the VLAN rewrite operation to add a new VLAN tag to the top of the VLAN stack.
An outer VLAN tag is pushed in front of the existing VLAN tag.
You can use this statement on Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2 and IQ2-E
interfaces; 10-Gigabit Ethernet LAN/WAN PIC; aggregated Ethernet interfaces using
Gigabit Ethernet IQ interfaces; 100-Gigabit Ethernet Type 5 PIC with CFP; and Gigabit
Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet, and aggregated Ethernet interfaces.
If you include the push statement in the configuration, you must also include the pop
statement at the [edit interfaces interface-name unit logical-unit-number output-vlan-map]
hierarchy level.
Required Privilege
Level
Related
Documentation
1139
push-push
Syntax
Hierarchy Level
Release Information
Description
push-push;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Required Privilege
Level
Related
Documentation
prbs
Syntax
Hierarchy Level
Release Information
Description
Default
Options
(prbs | no-prbs);
[edit interfaces interface-name otn-options]
Required Privilege
Level
Related
Documentation
1140
preemptive-fast-reroute
Syntax
Hierarchy Level
Release Information
Description
preemptive-fast-reroute {
(backward-frr-enable | no-backward-frr-enable);
(signal-degrade-monitor-enable | no-signal-degrade-monitor-enable);
(odu-backward-frr-enable | no-odu-backward-frr-enable); # applicable for P2-100GE-OTN
PIC only
(odu-signal-degrade-monitor-enable |no-odu-signal-degrade-monitor-enable);
#applicable for P2-100GE-OTN PIC only
}
[edit interfaces interface-name otn-options]
Default
By default, backward fast reroute insertion and signal degradation monitoring are disabled.
Options
Required Privilege
Level
Related
Documentation
1141
Hierarchy Level
Release Information
Description
premium {
forwarding-class class-name {
loss-priority (high | low);
}
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile output-priority-map classifier]
Required Privilege
Level
Related
Documentation
premium (Policer)
Syntax
Hierarchy Level
Release Information
Description
premium {
bandwidth-limit bps;
burst-size-limit bytes;
}
[edit interfaces interface-name gigether-options ethernet-switch-profile
ethernet-policer-profile policer cos-policer-name]
Required Privilege
Level
Related
Documentation
1142
protect-maintenance-association (OAM)
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
protect-maintenance-association protect-ma-name;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name ]
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
proxy
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1143
proxy-arp
Syntax
Hierarchy Level
Release Information
Description
NOTE: You must configure the IP address and the inet family for the interface
when you enable proxy ARP.
Default
Options
Proxy ARP is not enabled. The router or switch responds to an ARP request only if the
destination IP address is its own.
noneThe router or switch responds to any ARP request for a local or remote address
physical networks of the source and target are different and does not respond if the
source and target IP addresses are in the same subnet. The router or switch must also
have a route to the target IP address.
unrestricted(Optional) The router or switch responds to any ARP request for a local
or remote address if the router or switch has a route to the target IP address.
Default: unrestricted
Required Privilege
Level
Related
Documentation
1144
push
Syntax
Hierarchy Level
Release Information
push;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Description
Specify the VLAN rewrite operation to add a new VLAN tag to the top of the VLAN stack.
An outer VLAN tag is pushed in front of the existing VLAN tag.
You can use this statement on Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2 and IQ2-E
interfaces; 10-Gigabit Ethernet LAN/WAN PIC; aggregated Ethernet interfaces using
Gigabit Ethernet IQ interfaces; 100-Gigabit Ethernet Type 5 PIC with CFP; and Gigabit
Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet, and aggregated Ethernet interfaces.
If you include the push statement in the configuration, you must also include the pop
statement at the [edit interfaces interface-name unit logical-unit-number output-vlan-map]
hierarchy level.
Required Privilege
Level
Related
Documentation
1145
push-push
Syntax
Hierarchy Level
Release Information
Description
push-push;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Required Privilege
Level
Related
Documentation
1146
quiet-period
Syntax
Hierarchy Level
Release Information
Description
Options
quiet-period seconds;
[edit protocols dot1x authenticator interface interface-id]
Description
Default
Options
quiet-period seconds;
[edit protocols authentication-access-control interface (all | [interface-names])]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
For 802.1X and captive portal authentication, configure the number of seconds the
interface remains in the wait state following a failed authentication attempt by a
supplicant before reattempting authentication.
60 seconds
secondsNumber of seconds the interface remains in the wait state.
1147
rate
Syntax
rate {
(fixed-stuff-bytes | no-fixed-stuff-bytes);
otu4; oc192;
(pass-through | no-pass-through);
}
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1148
reauthentication
Syntax
Hierarchy Level
Release Information
Description
Options
Description
Options
reauthentication interval;
[edit protocols authentication-access-control interface (all | [interface-names]) dot1x]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
For 802.1X authentication, specify the number of seconds before an authentication
session times out.
intervalSets the periodic reauthentication time interval in seconds.
Range: 1 through 4,294,967,296 seconds
Default: 3600 seconds
Required Privilege
Level
1149
Release Information
Description
Options
rebalance interval
[edit interfaces aeX unit logical-unit-number forwarding-options load-balance-stateful
per-flow]
receive-ais
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1150
receive-ais;
[edit protocols oam ethernet connectivity-fault-management action-profile
action-profile-name event ais-trigger-condition]
receive-options-packets
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
receive-options-packets;
[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]
receive-ttl-exceeded
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
receive-ttl-exceeded;
[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]
1151
remote
Syntax
Hierarchy Level
Release Information
Description
Options
remote {
(inet-address address | mac-address address);
}
[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]
Required Privilege
Level
Related
Documentation
remote-loopback
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1152
remote-loopback;
[edit protocols oam link-fault-management interface interface-name]
remote-maintenance-association (OAM)
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
remote-maintenance-association remote-ma-name;
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
domain-name maintenance-association ma-name]
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
remote-mep
Syntax
Hierarchy Level
Release Information
Description
Options
remote-mep mep-id {
action-profile profile-name;
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
detect-loc;
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id]
Configuring a MEP to Generate and Respond to CFM Protocol Messages on page 536
1153
replay-window-size number-of-packets;
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Default
Options
When this variable is set to 0, all packets that arrive out-of-order are dropped.
Required Privilege
Level
Related
Documentation
1154
Hierarchy Level
Release Information
Description
replay-protect {
replay-window-size number-of-packets;
}
[edit security macsec connectivity-associationconnectivity-association-name]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Enable replay protection for MACsec.
A replay window size specified using the replay-window-size number-of-packets statement
must be specified to enable replay protection.
Options
Required Privilege
Level
Related
Documentation
1155
restore-interval
Syntax
Hierarchy Level
Release Information
Description
Options
restore-interval number;
[edit protocols protection-group ethernet-ring ring-name]
Required Privilege
Level
Related
Documentation
1156
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
retries
Syntax
Hierarchy Level
Release Information
Description
Options
retries integer;
[edit protocols dot1x authenticator interface interface-id]
Range: 1 through 10
Default: 3 retries
Required Privilege
Level
Related
Documentation
retries number;
[edit protocols authentication-access-control interface (all | [interface-names])]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
For 802.1X and captive portal authentication, configure the number of times the switch
attempts to authenticate the port after an initial failure. The port remains in a wait state
during the quiet period after the authentication attempt.
Options
numberNumber of retries.
Default: 3 retries
Range: 1 through 10
Required Privilege
Level
1157
revertive
Syntax
Hierarchy Level
revertive;
[edit interfaces aeX aggregated-ether-options lacp link-protection]
Release Information
Description
Enable the ability to switch to a better priority link (if one is available).
NOTE: By default, LACP link protection is revertive. However, you can use
this statement to define a specific aggregated Ethernet interface as revertive
to override a global non-revertive statement specified at the [edit chassis]
hierarchy level.
Required Privilege
Level
Related
Documentation
non-revertive (Chassis)
ring-id
Syntax
Hierarchy Level
Release Information
Description
Options
ring-id number;
[edit protocols protection-group ethernet-ring ring-name]
1158
ring-protection-link-end
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
ring-protection-link-end;
[edit protocols protection-group ethernet-ring ring-name (east-interface | west-interface)]
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
ring-protection-link-owner
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
ring-protection-link-owner;
[edit protocols protection-group ethernet-ring ring-name]
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
1159
routing-instance
Syntax
Hierarchy Level
Release Information
Description
Default
Required Privilege
Level
Related
Documentation
1160
routing-instance {
destination routing-instance-name;
}
[edit interfaces interface-name unit logical-unit-number tunnel],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
tunnel]
Release Information
Description
routing-instance routing-instance-name;
[edit protocols pppoe service-name-tables table-name service service-name],
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier
aci circuit-id-string ari remote-id-string]
at this level. The routing-instance and static-interface statements are mutually exclusive
for ACI/ARI pair configurations.
Options
Assigning a Dynamic Profile and Routing Instance to a Service Name or ACI/ARI Pair for
Dynamic PPPoE Interface Creation
1161
sa-multicast;
[edit chassis fpc slot pic slot forwarding-mode]
Required Privilege
Level
Related
Documentation
1162
100-Gigabit Ethernet Type 5 PIC with CFP (PF-1CGE-CFP) and the 100-Gigabit Ethernet
Type 4 PIC with CFP (PD-1CE-CFP-FPC4) .
100-Gigabit Ethernet MICs and the 100-Gigabit Ethernet Type 4 PIC with CFP
(PD-1CE-CFP-FPC4).
Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP on
page 414
sa-multicast;
[edit chassis fpc slot pic slot port port-number forwarding-mode]
Required Privilege
Level
Related
Documentation
1163
Description
Default
Options
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Enable HTTP or HTTPS access on the captive portal interface.
http
httpEnables HTTP access on the captive portal interface.
httpsEnables HTTPS access on the captive portal interface. HTTPS is recommended.
Required Privilege
Level
1164
secure-channel
Syntax
Hierarchy Level
Release Information
Description
secure-channel secure-channel-name {
direction (inbound | outbound);
encryption (MACsec);
id {
mac-address mac-address;
port-idport-id-number;
}
offset (0|30|50);
security-association security-association-number {
key key-string;
}
}
[edit security macsec connectivity-association connectivity-association-name]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Create and configure a secure channel to enable and configure MACsec when MACsec
is enabled using static secure association key (SAK) security mode.
You do not need to use this option to enable MACsec using static connectivity association
key (CAK) security mode. All configuration for MACsec using static CAK security mode
is done inside of the connectivity association but outside of the secure channel. When
MACsec is enabled using static CAK security mode, an inbound and an outbound secure
channelneither of which is user-configurableis automatically created within the
connectivity association.
Options
Required Privilege
Level
Related
Documentation
1165
security-association
Syntax
security-association security-association-number {
key key-string;
}
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Description
Specifies the number of one of the security associations in the secure channel when
MACsec is enabled using static secure association key (SAK) security mode. Because
SAKs are created by the key server when MACsec is enabled using static connectivity
association key (CAK) security mode, the security-association statement is not used
when enabling MACsec using static CAK security mode.
You must configure at least two security associations to enable MACsec using static SAK
security mode. MACsec initially establishes a secure connection when a security
association number and key match on both ends of an Ethernet link. After a certain
number of Ethernet frames are securely transmitted across the Ethernet link, MACsec
automatically rotates to a new security association with a new security association
number and key to maintain the secured Ethernet link. This rotation continues each time
a certain number of Ethernet frames are securely transmitted across the secured Ethernet
link, so you must always configure MACsec to have at least two security associations.
Default
Options
SAK.
The security association number is a whole number between 0 and 3. You can
configure two security associations in a secure channel when enabling MACsec using
static security keys.
Required Privilege
Level
Related
Documentation
1166
send-critical-event
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
send-critical-event;
[edit protocols oam ethernet link-fault-management action-profile action]
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
server
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
server;
[edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number
pppoe-options]
1167
server-fail
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
For EX Series switches configured for 802.1X authentication, specify the server fail fallback
action the switch takes when all RADIUS authentication servers are unreachable.
When you specify the action vlan-name or vlan-id, the VLAN must already be configured
on the switch.
Default
Options
Authentication is denied.
denyForce fail the supplicant authentication. No traffic will flow through the interface.
permitForce succeed the supplicant authentication. Traffic will flow through the interface
This action is allowed only if it is the first supplicant connecting to the interface. If
an authenticated supplicant is already connected, then the supplicant is not moved
to the VLAN and is not authenticated.
vlan-nameMove supplicant on the interface to the VLAN specified by this name. This
1168
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
For EX Series switches configured for 802.1X authentication, specify that when the switch
receives an Extensible Authentication Protocol Over LAN (EAPoL) Access-Reject message
during the authentication process between the switch and the RADIUS authentication
server, supplicants attempting access to the LAN are granted access and moved to a
specific VLAN. Any VLAN name or VLAN ID sent by a RADIUS server as part of the EAPoL
Access-Reject message is ignored.
When you specify the VLAN ID or VLAN name, the VLAN must already be configured on
the switch.
The remaining statements are explained separately.
Default
Options
None
vlan-idNumeric identifier of the VLAN to which the supplicant is moved.
vlan-nameName of the VLAN to which the supplicant is moved.
Required Privilege
Level
1169
server-timeout
Syntax
Hierarchy Level
Release Information
Description
Options
server-timeout seconds;
[edit protocols dot1x authenticator interface interface-id]
from the authentication server to the client before resending the request.
Range: 1 through 60 seconds
Default: 30 seconds
Required Privilege
Level
Related
Documentation
server-timeout seconds;
[edit protocols authentication-access-control interface (all | [interface-names])]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
For 802.1X and captive portal authentication, configure the amount of time a port will
wait for a reply when relaying a response from the supplicant to the authentication server
before timing out and invoking the server-fail action.
Default
Options
30 seconds
seconds Number of seconds.
1170
service (PPPoE)
Syntax
Hierarchy Level
Release Information
Description
Default
Options
service service-name {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
max-sessions number;
agent-specifier {
aci circuit-id-string ari remote-id-string {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
static-interface interface-name;
}
}
}
[edit protocols pppoe service-name-tables table-name]
You can configure a maximum of 512 named service entries across all PPPoE service
name tables on the router.
emptyService entry of zero length that represents an unspecified service. Each PPPoE
anyDefault service for non-empty service entries that do not match the named or
empty service entries configured in the PPPoE service name table. Each PPPoE service
1171
Related
Documentation
Assigning a Service to a Service Name Table and Configuring the Action Taken When the
Client Request Includes a Non-zero Service Name Tag
Configuring the Action Taken When the Client Request Includes an Empty Service Name
Tag
service-name
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1172
service-name name;
[edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number
pppoe-options]
service-name-table
Syntax
Hierarchy Level
Release Information
Description
service-name-table table-name;
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number family
pppoe],
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number family
pppoe],
[edit interfaces interface-name unit logical-unit-number family pppoe],
[edit interfaces interface-name unit logical-unit-number pppoe-underlying-options],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
family pppoe],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number
pppoe-underlying-options]
NOTE: The [edit ... family pppoe] hierarchies are supported only on MX Series
routers with MPCs.
Options
characters.
Required Privilege
Level
Related
Documentation
1173
service-name-tables
Syntax
Hierarchy Level
service-name-tables table-name {
service service-name {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
max-sessions number;
agent-specifier {
aci circuit-id-string ari remote-id-string {
drop;
delay seconds;
terminate;
dynamic-profile profile-name;
routing-instance routing-instance-name;
static-interface interface-name;
}
}
}
}
[edit protocols pppoe]
Release Information
Description
Create and configure a PPPoE service name table. Specify the action taken for each
service and remote access concentrator on receipt of a PPPoE Active Discovery Initiation
(PADI) packet. You can also specify the dynamic profile and routing instance that the
router uses to instantiate a dynamic PPPoE interface, and the maximum number of active
PPPoE sessions that the router can establish with the specified service. A maximum of
32 PPPoE service name tables is supported per router.
Options
characters.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation
1174
Description
Options
session-expiry seconds;
[edit protocols authentication-access-control interface (all | [interface-names])]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Configure the maximum duration in seconds of a session.
secondsDuration of session.
1175
short-name-format
Syntax
Hierarchy Level
Release Information
Description
Options
Default: character-string
NOTE: The PTX Series Packet Transport Routers support the vlan and 2octet
options only.
Required Privilege
Level
Related
Documentation
1176
signal-degrade
Syntax
Hierarchy Level
Release Information
Description
signal-degrade {
ber-threshold-clear value;
ber-threshold-signal-degrade value;
interval value;
}
[edit interfaces interface-name otn-options]
Default
If you omit the signal-degrade statement, the default threshold values are used.
Options
Required Privilege
Level
Related
Documentation
1177
signal-degrade-monitor-enable
Syntax
Hierarchy Level
Release Information
Description
(signal-degrade-monitor-enable | no-signal-degrade-monitor-enable);
[edit interfaces interface-name otn-options preemptive-fast-reroute]
You can also configure the pre-FEC BER thresholds that raise or clear a signal degrade
alarm and the time interval for the thresholds. If the BER thresholds and interval are not
configured, the default values are used. Include the ber-threshold-signal-degrade value,
ber-threshold-clear value, and interval value statements at the [edit interfaces
interface-name otn-options signal-degrade] hierarchy level to configure the BER thresholds
and time interval. See Understanding Pre-FEC BER Monitoring and BER Thresholds on
page 439 for more information about pre-FEC BER monitoring and determining BER
threshold settings.
Default
Options
Required Privilege
Level
1178
Related
Documentation
1179
source-address-filter
Syntax
Hierarchy Level
Release Information
source-address-filter {
mac-address;
}
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]
Description
For aggregated Ethernet, Fast Ethernet, Gigabit Ethernet, Gigabit Ethernet IQ interfaces,
and Gigabit Ethernet PICs with SFPs (except the 10-port Gigabit Ethernet PIC and the
built-in Gigabit Ethernet port on the M7i router), specify the MAC addresses from which
the interface can receive packets. For this statement to have any effect, you must include
the source-filtering statement in the configuration to enable source address filtering.
Options
mac-addressMAC address filter. You can specify the MAC address as nn:nn:nn:nn:nn:nn
1180
Configuring MAC Address Filtering on PTX Series Packet Transport Routers on page 17
source-filtering
Syntax
Hierarchy Level
Release Information
Description
(source-filtering | no-source-filtering);
[edit interfaces interface-name aggregated-ether-options],
[edit interfaces interface-name fastether-options],
[edit interfaces interface-name gigether-options]
Default
Required Privilege
Level
Related
Documentation
Configuring MAC Address Filtering on PTX Series Packet Transport Routers on page 17
1181
speed (Ethernet)
Syntax
Hierarchy Level
Release Information
Description
Configure the interface speed. This statement applies to the management Ethernet
interface (fxp0 or em0), Fast Ethernet 12-port and 48-port PICs, the built-in Fast Ethernet
port on the FIC (M7i router), Combo Line Rate DPCs and Tri-Rate Ethernet Copper
interfaces on MX Series routers,and Gigabit Ethernet interfaces on EX Series switches.
When you configure the Tri-Rate Ethernet copper interface to operate at 1 Gbps,
autonegotiation must be enabled. When you configure 100BASE-FX SFP, you must set
the port speed at 100 Mbps.
Options
You can specify the speed as either 10m (10 Mbps), 100m (100 Mbps), and on MX Series
routers, 1g (1 Gbps). You can also specify the auto option on MX Series routers.
For Gigabit Ethernet interfaces on EX Series switches, you can specify one of the following
options:
10m10 Mbps
100m100 Mbps
1g1 Gbps
autoAutomatically negotiate the speed (10 Mbps, 100 Mbps, or 1 Gbps) based on
1182
NOTE: If the negotiated speed and the interface speed do not match, the
link will not be brought up. Half duplex mode is not supported.
Options
Required Privilege
Level
Related
Documentation
You can specify the speed as either auto (autonegotiate), 10Mbps (10 Mbps), 100Mbps
(100 Mbps), or 1Gbps (1 Gbps).
interfaceTo view this statement in the configuration.
interface-controlTo add this statement to the configuration.
1183
sla-iterator-profile
Syntax
Hierarchy Level
Release Information
Description
Options
sla-iterator-profile profile-name {
data-tlv-size size;
iteration-count count-value;
priority priority-value;
}
[edit protocols oam ethernet connectivity-fault-management maintenance-domain
md-name maintenance-association ma-name mep mep-id remote-mep remote-mep-id]
information about configuring a remote MEP with an iterator profile, see Configuring
a Remote MEP with an Iterator Profile on page 668.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation
1184
sla-iterator-profiles
Syntax
Hierarchy Level
Release Information
Description
Options
sla-iterator-profiles {
profile-name {
avg-fd-twoway-threshold;
avg-ifdv-twoway-threshold;
avg-flr-forward-threshold;
avg-flr-backward-threshold;
calculation-weight {
delay delay-weight;
delay-variation delay-variation-weight;
}
cycle-time milliseconds;
iteration-period iteration-period-value;
measurement-type (loss | statistical-frame-loss | two-way-delay);
}
}
[edit protocols oam ethernet connectivity-fault-management performance-monitoring]
1185
stacked-vlan-tagging
Syntax
Hierarchy Level
stacked-vlan-tagging;
[edit interfaces interface-name]
Release Information
Description
For Gigabit Ethernet IQ interfaces, Gigabit Ethernet, 10-Gigabit Ethernet LAN/WAN PIC,
and 100-Gigabit Ethernet Type 5 PIC with CFP, enable stacked VLAN tagging for all
logical interfaces on the physical interface.
For pseudowire subscriber interfaces, enable stacked VLAN tagging for logical interfaces
on the pseudowire service.
Required Privilege
Level
Related
Documentation
1186
Stacking and Rewriting Gigabit Ethernet VLAN Tags Overview on page 489
Hierarchy Level
Release Information
Description
static mac-address {
interface interface-names;
vlan-assignment (vlan-id |vlan-name );
}
[edit protocols authentication-access-control]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Configure MAC addresses to exclude from 802.1X authentication. The static MAC list
provides an authentication bypass mechanism for supplicants connecting to a port,
permitting devices such as printers that are not 802.1X-enabled to be connected to the
network on 802.1X-enabled ports.
Using this 802.1X authentication-bypass mechanism, the supplicant connected to the
MAC address is assumed to be successfully authenticated and the port is opened for it.
No further authentication is done for the supplicant.
You can optionally configure the VLAN that the supplicant is moved to or the interfaces
on which the MAC address can gain access from.
Options
mac-address The MAC address of the device for which 802.1X authentication should
1187
static-interface
Syntax
Hierarchy Level
Release Information
Description
static-interface interface-name;
[edit protocols pppoe service-name-tables table-name service service-name agent-specifier
aci circuit-id-string ari remote-id-string]
Options
interface-nameName of the static PPPoE interface reserved for use by the PPPoE client
with matching ACI/ARI information. Specify the interface in the format pp0.logical,
where logical is a logical unit number from 0 through 16385 for static interfaces.
Required Privilege
Level
Related
Documentation
1188
start-measurement
Syntax
Hierarchy Level
Release Information
Description
Default
Options
(no-start-measurement | start-measurement);
[edit interfaces interface-name otn-options odu-delay-management]
Required Privilege
Level
Related
Documentation
supplicant
Syntax
Hierarchy Level
Release Information
Description
supplicant single;
[edit protocols dot1x authenticator interface interface-id]
Options
Required Privilege
Level
Related
Documentation
1189
Description
Default
Options
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Configure the MAC-based method used to authenticate clients for 802.1X or captive
portal authentication.
single
singleAuthenticates only the first client that connects to an authenticator port. All other
clients connecting to the authenticator port after the first are permitted free access
to the port without further authentication. If the first authenticated client logs out,
all other supplicants are locked out until a client authenticates again.
single-secureAuthenticates only one client to connect to an authenticator port. The
configure the number of clients per port. If you also configure a maximum number
of devices that can be connected to a port through port security settings, the lower
of the configured values is used to determine the maximum number of clients allowed
per port.
Required Privilege
Level
1190
supplicant-timeout
Syntax
Hierarchy Level
Release Information
Description
Options
supplicant-timeout seconds;
[edit protocols dot1x authenticator interface interface-id]
supplicant-timeout seconds;
[edit protocols authentication-access-control interface (all | [interface-names]) dot1x]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
For 802.1X authentication, configure how long the port waits for a response when relaying
a request from the authentication server to the supplicant before resending the request.
Default
Options
30 seconds
seconds Number of seconds.
1191
swap
Syntax
Hierarchy Level
Release Information
Description
swap;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Required Privilege
Level
Related
Documentation
swap-by-poppush
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
1192
swap-by-poppush;
[edit interfaces interface-name unit logical-unit-number]
swap-push
Syntax
Hierarchy Level
Release Information
Description
swap-push;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Required Privilege
Level
Related
Documentation
1193
swap-swap
Syntax
Hierarchy Level
Release Information
Description
swap-swap;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Required Privilege
Level
Related
Documentation
switch-options
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
1194
switch-options {
switch-port port-number {
(auto-negotiation | no-auto-negotiation);
speed (10m | 100m | 1g);
link-mode (full-duplex | half-duplex);
}
}
[edit interfaces ge-pim/0/0]
switch-port
Syntax
Hierarchy Level
Release Information
Description
switch-port port-number {
(auto-negotiation | no-auto-negotiation);
speed (10m | 100m | 1g);
link-mode (full-duplex | half-duplex);
}
[edit interfaces ge-pim/0/0 switch-options]
Default
Autonegotiation is enabled by default. If the link speed and duplex are also configured,
the interfaces use the values configured as the desired values in the negotiation.
Options
through 7 on the 8-port Gigabit Ethernet uPIM, and 0 through 15 on the 16-port Gigabit
Ethernet uPIM.
The remaining statements are explained separately.
Required Privilege
Level
1195
symbol-period
Syntax
Hierarchy Level
Release Information
Description
symbol-period count;
[edit protocols oam ethernet link-fault-management action-profile event, link-event-rate],
[edit protocols oam link-fault-management interface interface-name event-thresholds]
Options
Configuring Threshold Values for Local Fault Events on an Interface on page 606
Configuring Threshold Values for Fault Events in an Action Profile on page 614
Required Privilege
Level
Related
Documentation
1196
syslog;
[edit protocols oam ethernet link-fault-management action-profile action]
Specifying the Actions to Be Taken for Link-Fault Management Events on page 611
system-id
Syntax
Hierarchy Level
Release Information
Description
system-id system-id;
[edit interfaces aeX aggregated-ether-options lacp]
Required Privilege
Level
Related
Documentation
1197
system-priority
Syntax
Hierarchy Level
Release Information
Description
system-priority priority;
[edit interfaces aeX aggregated-ether-options lacp]
Options
priorityPriority for the aggregated Ethernet system. A smaller value indicates a higher
priority.
Range: 0 through 65535
Default: 127
Required Privilege
Level
1198
tag-protocol-id [tpids];
[edit interfaces interface-name gigether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile],
[edit interfaces interface-name aggregated-ether-options ethernet-switch-profile],
[edit interfaces interface-name ether-options ethernet-switch-profile]
Release Information
Description
For Gigabit Ethernet IQ and 10-Gigabit Ethernet IQ2 and IQ2-E interfaces, aggregated
Ethernet with Gigabit Ethernet IQ interfaces, and Gigabit Ethernet PICs with SFPs (except
the 10-port Gigabit Ethernet PIC, and the built-in Gigabit Ethernet port on the M7i router),
define the TPIDs expected to be sent or received on a particular VLAN. For each Gigabit
Ethernet port, you can configure up to eight TPIDs using the tag-protocol-id statement;
but only the first four TPIDs are supported on IQ2 and IQ2-E interfaces.
For 10-Gigabit Ethernet LAN/WAN PIC interfaces on T Series routers only the default
TPID value (0x8100) is supported.
For Gigabit Ethernet, 10-Gigabit Ethernet, 40-Gigabit Ethernet, and aggregated Ethernet
interfaces on EX Series switches, define the TPIDs expected to be sent or received on a
particular VLAN. The default TPID value is 0x8100. Other supported values are 0x88a8,
0x9100, and 0x9200.
Options
Required Privilege
Level
Related
Documentation
Configuring Frames with Particular TPIDs to Be Processed as Tagged Frames on page 493
1199
Release Information
Description
tag-protocol-id tpid;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Default
Required Privilege
Level
Related
Documentation
1200
Configuring Inner and Outer TPIDs and VLAN IDs on page 495
tca
Syntax
Hierarchy Level
Release Information
Description
Laser power
Laser temperature
Default
Options
trigger
1201
Required Privilege
Level
Related
Documentation
1202
terminate;
Hierarchy Level
Release Information
Description
Direct the router to immediately respond to a PPPoE Active Discovery Initiation (PADI)
control packet received from a PPPoE client by sending the client a PPPoE Active
Discovery Offer (PADO) packet. The PADO packet contains the name of the access
concentrator (router) that can service the client request. The terminate action is the
default action for a named service entry, empty service entry, any service entry, or agent
circuit identifier/agent remote identifier (ACI/ARI) pair in a PPPoE service name table.
Required Privilege
Level
Related
Documentation
1203
Hierarchy Level
Release Information
Description
traceoptions {
file filename <files number> <size maximum-file-size> <world-readable |
no-world-readable>;
flag flag <disable>;
}
[edit protocols lldp],
[edit routing-instances routing-instance-name protocols lldp]
Default
The default LLDP protocol-level trace options are inherited from the global traceoptions
statement.
Options
disable(Optional) Disable the tracing operation. One use of this option is to disable a
single operation when you have defined a broad group of tracing operations, such
as all.
file filenameName of the file to receive the output of the tracing operation. Enclose the
so on, until the maximum number of trace files is reached. Then, the oldest trace file
is overwritten.
If you specify a maximum number of files, you must also specify a maximum file size with
the size option.
Range: 2 through 1000 files
Default: 1 trace file only
flagTracing operation to perform. To specify more than one tracing operation, include
multiple flag statements. The following are the LLDP-specific tracing options:
1204
normalAll normal events. This is the default. If you do not specify this option, only
no-world-readable(Optional) Prevent any user from reading the log file. This is the
default. If you do not include this option, tracing output is appended to an existing
trace file.
size maximum-file-size(Optional) Maximum size of each trace file, in kilobytes (KB)
or megabytes (MB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is renamed
trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme continues
until the maximum number of trace files is reached. Then the oldest trace file is
overwritten.
If you specify a maximum file size, you must also specify a maximum number of trace
files with the files option.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through the maximum file size supported on your system
Default: 1 MB
world-readable(Optional) Allow any user to read the log file.
Required Privilege
Level
Related
Documentation
1205
Hierarchy Level
Release Information
Description
traceoptions {
file filename <no-stamp> <world-readable | no-world-readable> <replace> <size size>;
flag flag;
}
[edit protocols protection-group]
Default
Trace options are not set by default. On some EX Series switches, logging of basic ERPS
state transitions is set by default. You can configure trace options on those switches to
obtain more details than are provided by the default log. See Understanding Ethernet
Ring Protection Switching Functionality on page 224 for additional information about
default logging of the basic state transitions.
Options
file filenameName of the file to receive the output of the tracing operation. All files are
placed in the directory /var/log. You can include the following file options:
flag flagTracing operation to perform. To specify more than one tracing operation,
include multiple flag statements. The following flags are available for both EX
Switches and MX Series routers:
1206
allTrace all
Required Privilege
Level
Related
Documentation
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
1207
Hierarchy Level
Release Information
Description
Default
Options
traceoptions {
file <filename> <files number> <match regular-expression> <size size> <world-readable |
no-world-readable>;
flag flag <disable>;
no-remote-trace;
}
[edit interfaces]
single operation when you have defined a broad group of tracing operations, such
as all.
filenameName of the file to receive the output of the tracing operation. Enclose the
name within quotation marks. All files are placed in the directory /var/log. By default,
interface process tracing output is placed in the file dcd.
files number(Optional) Maximum number of trace files. When a trace file named
trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and
so on, until the maximum number of trace files is reached. Then the oldest trace file
is overwritten.
If you specify a maximum number of files, you also must specify a maximum file size with
the size option.
Range: 2 through 1000
Default: 3 files
flagTracing operation to perform. To specify more than one tracing operation, include
all
1208
size size(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB),
or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is renamed
trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme continues
until the maximum number of trace files is reached. Then, the oldest trace file is
overwritten.
If you specify a maximum file size, you also must specify a maximum number of trace
files with the files option.
Syntax: xk to specify kilobytes, xm to specify megabytes, or xg to specify gigabytes
Range: 10 KB through the maximum file size supported on your router
Default: 1 MB
world-readable(Optional) Allow any user to read the log file.
match regex(Optional) Refine the output to include only those lines that match the
1209
traceoptions (LACP)
Syntax
Hierarchy Level
Release Information
Description
Default
Options
traceoptions {
file <filename> <files number> <size size> <world-readable | no-world-readable>;
flag flag;
no-remote-trace;
}
[edit protocols lacp]
name within quotation marks. All files are placed in the directory /var/log. By default,
interface process tracing output is placed in the file lacpd.
files number(Optional) Maximum number of trace files. When a trace file named
trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and
so on, until the maximum number of trace files is reached. Then the oldest trace file
is overwritten.
If you specify a maximum number of files, you also must specify a maximum file size with
the size option.
Range: 2 through 1000
Default: 3 files
flagTracing operation to perform. To specify more than one tracing operation, include
configurationConfiguration code
or gigabytes (GB). When a trace file named trace-file reaches this size, it is renamed
trace-file.0. When the trace-file again reaches its maximum size, trace-file.0 is renamed
trace-file.1 and trace-file is renamed trace-file.0. This renaming scheme continues
1210
until the maximum number of trace files is reached. Then the oldest trace file is
overwritten.
If you specify a maximum file size, you also must specify a maximum number of trace
files with the files option:
Syntax: xk to specify kilobytes, xm to specify megabytes, or xg to specify gigabytes
Range: 10 KB through the maximum file size supported on your router
Default: 1 MB
world-readable(Optional) Allow any user to read the log file.
Required Privilege
Level
Related
Documentation
1211
traceoptions (PPPoE)
Syntax
Hierarchy Level
Release Information
Description
Options
traceoptions {
file <filename> <files number> <match regular-expression > <size maximum-file-size>
<world-readable | no-world-readable>;
filter {
aci regular-expression;
ari regular-expresion;
service-name regular-expresion;
underlying-interface interface-name;
}
flag flag;
level (all | error | info | notice | verbose | warning);
no-remote-trace;
}
[edit protocols pppoe]
name within quotation marks. All files are placed in the directory /var/log.
files number(Optional) Maximum number of trace files to create before overwriting the
oldest one. If you specify a maximum number of files, you also must specify a
maximum file size with the size option.
Range: 2 through 1000
Default: 3 files
disableDisable this trace flag.
filterAdditional filter to refine the output to display particular subscribers. Filtering
BEST PRACTICE: Due to the complexity of agent circuit identifiers and agent
remote identifiers, we recommend that you do not try an exact match when
filtering on these options. For service names, searching on the exact name is
appropriate, but you can also use a regular expression with that option.
by PPPoE client.
by PPPoE client.
1212
include multiple flag statements. You can include the following flags:
eventsTrace events.
levelLevel of tracing to perform. You can specify any of the following levels:
Default: error
match regular-expression(Optional) Refine the output to include lines that contain the
regular expression.
no-remote-traceDisable remote tracing.
no-world-readable(Optional) Disable unrestricted file access.
1213
size maximum-file-size(Optional) Maximum size of each trace file. By default, the number
entered is treated as bytes. Alternatively, you can include a suffix to the number to
indicate kilobytes (KB), megabytes (MB), or gigabytes (GB). If you specify a maximum
file size, you also must specify a maximum number of trace files with the files option.
Syntax: sizek to specify KB, sizem to specify MB, or sizeg to specify GB
Range: 10240 through 1073741824
Default: 128 KB
world-readable(Optional) Enable unrestricted file access.
Required Privilege
Level
Related
Documentation
1214
traceoptions (802.1X and Captive Portal for MX Series in Enhanced LAN Mode)
Syntax
Hierarchy Level
traceoptions {
file filename <files number> <size size> <world-readable | no-world-readable> <match
regex>;
flag flag;
}
[edit protocols authentication-access-control]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
Define tracing operations for the 802.1X protocol, LLDP, and captive portal authentication.
Default
Options
name within quotation marks. All files are placed in the directory /var/log.
files number(Optional) Maximum number of trace files. When a trace file named
trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and
so on, until the maximum number of trace files is reached. Then the oldest trace file
is overwritten. If you specify a maximum number of files, you also must specify a
maximum file size by using the size option.
Range: 2 through 1000
Default: 3 files
flag flagTracing operation to perform. To specify more than one tracing operation,
include multiple flag statements. You can include the following flags:
1215
match regex(Optional) Refine the output to include lines that contain the regular
expression.
no-world-readable(Optional) Restrict file access to the user who created the file.
size size(Optional) Maximum size of each trace file, in kilobytes (KB), megabytes (MB),
or gigabytes (GB). When a trace file named trace-file reaches its maximum size, it
is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of
trace files is reached. Then the oldest trace file is overwritten. If you specify a
maximum number of files with the files option, you also must specify a maximum
file size.
Syntax: xk to specify KB, xm to specify MB, or xg to specify GB
Range: 10 KB through 1 GB
Default: 128 KB
world-readable(Optional) Enable unrestricted file access.
Required Privilege
Level
transmit-delay
Syntax
Hierarchy Level
Release Information
Description
Options
transmit-delay seconds;
[edit protocols lldp],
[edit routing-instances routing-instance-name protocols lldp]
Default: 2
Range: 1 through 8192
Required Privilege
Level
Related
Documentation
1216
transmit-interval interval;
[edit security macsec connectivity-association connectivity-association-name mka]
Statement introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Specifies the transmit interval for MACsec Key Agreement (MKA) protocol data units
(PDUs).
The MKA transmit interval setting sets the frequency for how often the MKA PDU is sent
to the directly connected device to maintain MACsec on a point-to-point Ethernet link.
A lower interval increases bandwidth overhead on the link; a higher interval optimizes the
MKA protocol data unit exchange process.
The transmit interval settings must be identical on both ends of the link when MACsec
using static connectivity association key (CAK) security mode is enabled.
We recommend increasing the interval to 6000 ms in high-traffic load environments.
Default
Options
Required Privilege
Level
Related
Documentation
1217
transmit-period
Syntax
Hierarchy Level
Release Information
transmit-period seconds;
[edit protocols dot1x authenticator interface interface-id]
Description
Set the number of seconds the port waits before retransmitting the initial EAPOL PDUs
to the client.
Options
secondsThe number of seconds the port waits before retransmitting the initial EAPOL
transmit-period seconds;
[edit protocols authentication-access-control interface (all | [interface-names]) dot1x]
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
For 802.1X authentication, how long the port waits before retransmitting the initial EAPOL
PDUs to the supplicant.
Default
30 seconds
Options
secondsNumber of seconds the port waits before retransmitting the initial EAPOL PDUs
to the supplicant.
Range: 1 through 65,535 seconds
Default: 30 seconds
Required Privilege
Level
1218
transport-monitoring
Syntax
Hierarchy Level
Release Information
Description
transport-monitoring;
[edit interfaces]
Statement introduced in Junos OS Release 14.2 for PTX5000 and PTX3000 routers.
Monitor the performance and state of packet transport for OTN and optics modules. The
following statistics are monitored:
Packet transport for ninety-six 15minute intervals for the current 24 hours.
1219
trigger
Syntax
Hierarchy Level
Release Information
Description
Default
Options
trigger-identifier(For M Series, MX Series, SRX Series, and T Series routers only) Trigger
identifier. It can be one of the following:
odu-aisOptical channel data unit (ODU) Alarm Indication Signal defect trigger.
odu-bei(MX Series routers only) ODU Backward Error Indication defect trigger.
odu-iae(MX Series routers only) ODU Incoming Alignment Error defect trigger.
odu-tca-es(MX Series routers only) ODU Errored Seconds Threshold crossing defect
trigger.
defect trigger.
1220
opu-ptim(MX Series routers only) Payload Type Identifier Mismatch defect trigger.
otu-aisOptical Channel Transport Unit (OTU) Alarm Indication Signal defect trigger.
otu-tca-es(MX Series routers only) OTU Errored Seconds Threshold crossing defect
trigger.
otu-tca-ses(MX Series routers only) OTU Severely Errored Seconds Threshold crossing
defect trigger.
defect trigger.
1221
trigger-identifier(For PTX Series routers only) Trigger identifier. It can be one of the
following:
1222
trigger.
trigger.
trigger.
1223
trigger.
milliseconds).
NOTE: The trigger hold time value alone does not mark an interface to be up
when the defect is absent or mark an interface to be down when the defect
occurs. The hold time value only impacts the alarm reporting time. To mark
an interface up or down, you must also configure the physical interface hold
time at the [edit interfaces interface-name hierarchy level].
Required Privilege
Level
Related
Documentation
1224
tti
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
tti tti-identifier;
[edit interfaces interface-name otn-options]
1225
tx-power
Syntax
Hierarchy Level
Release Information
Description
Default
Options
Required Privilege
Level
Related
Documentation
tx-power dbm;
[edit interfaces interface-name optics-options]
Description
Default
Required Privilege
Level
uac-policy;
[edit protocols authentication-access-control]
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Configure Junos Pulse Access Control Service as the access policy to authenticate and
authorize users connected to the switch for admission to the network and for access to
protected network resources.
The Access Control Service access policy is disabled.
routingTo view this statement in the configuration.
routing-controlTo add this statement to the configuration.
Related
Documentation
1226
underlying-interface
Syntax
Hierarchy Level
Release Information
Description
underlying-interface interface-name;
[edit interfaces pp0 unit logical-unit-number pppoe-options],
[edit interfaces demux0 unit logical-unit-number demux-options],
[edit logical-systems logical-system-name interfaces demux0 unit logical-unit-number
demux-options],
[edit logical-systems logical-system-name interfaces pp0 unit logical-unit-number
pppoe-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
demux0 unit logical-unit-number demux-options],
[edit logical-systems logical-system-name routing-instances routing-instance-name interfaces
pp0 unit logical-unit-number pppoe-options]
Options
For example, at-0/0/1.0 (ATM VC), fe-1/0/1.0 (Fast Ethernet interface), ge-2/0/0.0
(Gigabit Ethernet interface), ae1.0 (for IP demux on an aggregated Ethernet interface),
or ae1 (for VLAN demux on an aggregated Ethernet interface).
Required Privilege
Level
Related
Documentation
1227
unit
Syntax
1228
unit logical-unit-number {
accept-source-mac {
mac-address mac-address {
policer {
input cos-policer-name;
output cos-policer-name;
}
}
}
accounting-profile name;
advisory-options {
downstream-rate rate;
upstream-rate rate;
}
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 {
maximum-contexts number <force>;
f-max-period number;
queues [queue-numbers];
port {
minimum port-number;
maximum port-number;
}
}
}
compression-device interface-name;
copy-tos-to-outer-ip-header;
demux-destination family;
demux-source family;
demux-options {
underlying-interface interface-name;
}
description text;
interface {
l2tp-interface-id name;
(dedicated | shared);
}
dialer-options {
activation-delay seconds;
callback;
callback-wait-period time;
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];
}
}
}
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;
family family-name {
... the family subhierarchy appears after the main [edit interfaces interface-name unit
logical-unit-number] hierarchy ...
}
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;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
interleave-fragments;
inverse-arp;
layer2-policer {
input-policer policer-name;
input-three-color policer-name;
output-policer policer-name;
output-three-color policer-name;
}
link-layer-overhead percent;
minimum-links number;
mrru bytes;
multicast-dlci dlci-identifier;
multicast-vci vpi-identifier.vci-identifier;
multilink-max-classes number;
multipoint;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);
1229
output-vlan-map {
(pop | pop-pop | pop-swap | push | push-push | swap |
swap-push | swap-swap);
inner-tag-protocol-id tpid;
inner-vlan-id number;
tag-protocol-id tpid;
vlan-id number;
}
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 {
access-profile name;
default-pap-password password;
local-name name;
local-password password;
passive;
}
}
pppoe-options {
access-concentrator name;
auto-reconnect seconds;
(client | server);
service-name name;
underlying-interface interface-name;
}
pppoe-underlying-options {
access-concentrator name;
direct-connect;
dynamic-profile profile-name;
max-sessions number;
}
proxy-arp;
service-domain (inside | outside);
shaping {
(cbr rate | rtvbr peak rate sustained rate burst length | vbr peak rate sustained rate burst
length);
queue-length number;
}
short-sequence;
1230
targeted-distribution;
transmit-weight number;
(traps | no-traps);
trunk-bandwidth rate;
trunk-id number;
tunnel {
backup-destination address;
destination address;
key number;
routing-instance {
destination routing-instance-name;
}
source source-address;
ttl number;
}
vci vpi-identifier.vci-identifier;
vci-range start start-vci end end-vci;
vpi vpi-identifier;
vlan-id number;
vlan-id-range number-number;
vlan-tags inner tpid.vlan-id outer tpid.vlan-id;
family family {
accounting {
destination-class-usage;
source-class-usage {
(input | output | input output);
}
}
access-concentrator name;
address address {
... the address subhierarchy appears after the main [edit interfaces interface-name unit
logical-unit-number family family-name] hierarchy ...
}
bundle interface-name;
core-facing;
demux-destination {
destination-prefix;
}
demux-source {
source-prefix;
}
direct-connect;
duplicate-protection;
dynamic-profile profile-name;
filter {
group filter-group-number;
input filter-name;
input-list [filter-names];
output filter-name;
output-list [filter-names];
}
interface-mode (access | trunk);
ipsec-sa sa-name;
keep-address-and-control;
mac-validate (loose | strict);
max-sessions number;
1231
mtu bytes;
multicast-only;
no-redirects;
policer {
arp policer-template-name;
input policer-template-name;
output policer-template-name;
}
primary;
protocols [inet iso mpls];
proxy inet-address address;
receive-options-packets;
receive-ttl-exceeded;
remote (inet-address address | mac-address address);
rpf-check {
fail-filter filter-name
mode loose;
}
sampling {
input;
output;
}
service {
input {
post-service-filter filter-name;
service-set service-set-name <service-filter filter-name>;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
service-name-table table-name
(translate-discard-eligible | no-translate-discard-eligible);
(translate-fecn-and-becn | no-translate-fecn-and-becn);
translate-plp-control-word-de;
unnumbered-address interface-name destination address
destination-profile profile-name;
vlan-id number;
vlan-id-list [number number-number];
address address {
arp ip-address (mac | multicast-mac) mac-address <publish>;
broadcast address;
destination address;
destination-profile name;
eui-64;
master-only;
multipoint-destination address {
dlci dlci-identifier;
epd-threshold cells <plp1 cells>;
inverse-arp;
oam-liveness {
up-count cells;
down-count cells;
}
oam-period (disable | seconds);
shaping {
1232
(cbr rate | rtvbr burst length peak rate sustained rate | vbr burst length peak rate
sustained rate);
queue-length number;
}
vci vpi-identifier.vci-identifier;
}
preferred;
primary;
(vrrp-group | vrrp-inet6-group) group-number {
(accept-data | no-accept-data);
advertiseinterval seconds;
authentication-type authentication;
authentication-key key;
fast-interval milliseconds;
(preempt | no-preempt) {
hold-time seconds;
}
priority number;
track {
interface interface-name {
bandwidth-threshold bits-per-second priority-cost number;
}
priority-hold-time seconds;
route ip-address/prefix-length routing-instance instance-name priority-cost cost;
}
virtual-address [addresses];
virtual-link-local-address ipv6address;
vrrp-inherit-from {
active-interface interface-name;
active-group group-number;
}
}
}
}
}
Hierarchy Level
Release Information
Description
Options
Range: 0 through 1,073,741,823 for demux and PPPoE static interfaces. 0 through 16,385
for all other static interface types.
The remaining statements are explained separately.
Required Privilege
Level
1233
unnumbered-address (PPP)
Syntax
Hierarchy Level
Release Information
Description
Options
must include a logical unit number and must have a configured address.
The remaining statements are explained separately.
Required Privilege
Level
Related
Documentation
1234
version-3
Syntax
Hierarchy Level
Release Information
Description
version-3;
[edit protocols vrrp]
NOTE:
Required Privilege
Level
Related
Documentation
Even though the version-3 statement can be configured only at the [edit
protocols vrrp] hierarchy level, VRRPv3 is enabled on all the configured
logical systems as well.
When enabling VRRPv3, you must ensure that VRRPv3 is enabled on all
the VRRP routers in the network. This is because VRRPv3 does not
interoperate with the previous versions of VRRP.
1235
virtual-control-channel
Syntax
Hierarchy Level
Release Information
Description
Options
virtual-control-channel channel-name {
west-interface name;
east-interface name;
}
[edit protocols protection-group ethernet-ring name (east-interface | west-interface)]
Required Privilege
Level
Related
Documentation
virtual-switch
Syntax
Hierarchy Level
Release Information
Description
Required Privilege
Level
Related
Documentation
1236
vlan-assignment
Syntax
Hierarchy Level
Release Information
Statement introduced in Junos OS Release 14.2 for MX240, MX480, and MX960 routers
in enhanced LAN mode.
Description
Configure the VLAN that is associated with the list of MAC addresses that are excluded
from RADIUS authentication.
Options
vlan-id | vlan-nameThe name of the VLAN or the VLAN tag identifier to associate with
Release Information
Description
Options
vlan-id number;
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
Range: For aggregated Ethernet, 4-port, 8-port, and 12-port Fast Ethernet PICs, and for
management and internal Ethernet interfaces, 1 through 1023.
For 48-port Fast Ethernet and Gigabit Ethernet PICs, 1 through 4094.
VLAN ID 0 is reserved for tagging the priority of frames.
Required Privilege
Level
Related
Documentation
1237
Release Information
Description
vlan-id number;
[edit interfaces interface-name unit logical-unit-number input-vlan-map],
[edit interfaces interface-name unit logical-unit-number output-vlan-map],
[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]
Required Privilege
Level
Related
Documentation
1238
Release Information
Description
NOTE:
When you create a circuit cross-connect (CCC) using VLAN-bundled
single-tag logical interfaces on Layer 2 VPN routing instances, the circuit
automatically uses ethernet encapsulation. For Layer 2 VPN, you need to
include the encapsulation-type statement and specify the value ethernet at
either of the following hierarchy levels:
Options
[vlan-id vlan-idvlan-id]A list of valid VLAN ID numbers. Specify the VLAN IDs individually
by using a space to separate each ID, as an inclusive list by separating the starting
VLAN ID and ending VLAN ID with a hyphen, or as a combination of both.
Range: 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
1239
vlan-id-range 1-4094;
}
[edit interfaces interface-name]
unit 0;
Required Privilege
Level
Related
Documentation
1240
encapsulation-type (Layer 2 VPN routing instance), see the Junos OS VPNs Library for
Routing Devices
Release Information
Description
Options
1241
vlan-id-range
Syntax
Hierarchy Level
Release Information
Description
Options
vlan-id-range vlan-idvlan-id
[edit interfaces interface-name unit logical-unit-number],
[edit logical-systems logical-system-name interfaces interface-name unit logical-unit-number]
1242
vlan-rewrite
Syntax
Hierarchy Level
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
1243
Options
high-lowVLAN IDs 1 through 2047 are distributed to PFE0 and VLAN IDs 2048 through
distributed to PFE0.
Required Privilege
Level
Related
Documentation
1244
Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP on
page 414
Hierarchy Level
Release Information
Description
vlan-steering {
vlan-rule (high-low | odd-even);
}
[edit chassis fpc slot pic slot forwarding-mode]
Required Privilege
Level
Related
Documentation
Configuring VLAN Steering Mode for 100-Gigabit Ethernet Type 4 PIC with CFP on
page 414
1245
vlan-tagging
Syntax
Hierarchy Level
Release Information
Description
vlan-tagging;
[edit interfaces interface-name],
[edit logical-systems logical-system-name interfaces interface-name]
NOTE: On EX Series switches except for EX4300 and EX9200 switches, the
vlan-tagging and family ethernet-switching statements cannot be configured
on the same interface. Interfaces on EX2200, EX3200, EX3300, EX4200,
and EX4500 switches are set to family ethernet-switching by the default
factory configuration. EX6200 and EX8200 switch interfaces do not have a
default family setting.
Required Privilege
Level
Related
Documentation
1246
vlan-tags
Syntax
Hierarchy Level
Release Information
Description
Options
inner [tpid].vlan-idA TPID (optional) and a valid VLAN identifier in the format tpid.vlan-id.
1247
Release Information
Description
NOTE:
To create a circuit cross-connect (CCC) using VLAN-bundled dual-tag logical
interfaces on Layer 2 VPN routing instances, you must include the
encapsulation-type statement and specify the value ethernet-vlan at the one
of the following hierarchy levels:
Options
inner-list [vlan-id vlan-id vlan-id-vlan-id]A list of valid VLAN ID numbers. Specify the
VLAN IDs individually by using a space to separate each ID, as an inclusive list by
separating the starting VLAN ID and ending VLAN ID with a hyphen, or as a
combination of both.
Range: 1 through 4094. VLAN ID 0 is reserved for tagging the priority of frames.
outer <tpid.>vlan-idAn optional Tag Protocol ID (TPID) and a valid VLAN ID.
1248
Required Privilege
Level
Related
Documentation
encapsulation-type (Layer 2 VPN routing instance), see the Junos OS VPNs Library for
Routing Devices.
1249
Release Information
Description
Options
Range: (most routers) For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging
the priority of frames. For PTX Series, VLAN ID 0 is not supported.
inner-range vid1vid2For MX Series routers with Enhanced IQ (IQE) PICs only; specify
a range of VLAN IDs where vid1 is the start of the range and vid2 is the end of the
range.
Range: For VLAN ID, 1 through 4094. VLAN ID 0 is reserved for tagging the priority of
frames.
outer tpid.vlan-idA TPID and a valid VLAN identifier.
Range: (most routers) For VLAN ID, 1 through 511 for normal interfaces, and 512 through
4094 for VLAN CCC interfaces. VLAN ID 0 is reserved for tagging the priority of
frames. For PTX Series, VLAN ID 0 is not supported.
NOTE: Configuring inner-range with the entire vlan-id range consumes system
resources and is not a best practice. It should be used only when a subset of
VLAN IDs of inner tag (not the entire range) needs to be associated with a
logical interface. If you specify the entire range (14094), it has the same
result as not specifying a range; however, it consumes Packet Forwarding
Engine resources such as VLAN lookup table entries, and so on.
The following examples illustrate this further:
[edit interfaces interface-name]
stacked-vlan-tagging;
unit number {
vlan-tags outer vid inner-range 1-4094;
}
1250
Required Privilege
Level
Related
Documentation
Configuring Flexible VLAN Tagging on PTX Series Packet Transport Routers on page 249
wait-to-block-interval
Syntax
Hierarchy Level
Release Information
Description
Options
wait-to-block-interval number;
[edit protocols protection-group ethernet-ring ring-name]
Range: 5 through 10 s
Default: 5 s
Required Privilege
Level
Related
Documentation
1251
warning
Syntax
Hierarchy Level
Release Information
Description
Options
warning low-light-warning {
(link-down | syslog);
}
[edit interfaces interface-name optics-options]
Required Privilege
Level
Related
Documentation
1252
Configuring 10-Gigabit Ethernet Link Down Notification for Optics Options Alarm or
Warning on page 398
wavelength
Syntax
Hierarchy Level
Release Information
Description
Options
wavelength nm;
[edit interfaces interface-name optics-options]
NOTE: All values are displayed. However, if you configure a value that is not
supported by the device, an error message is displayed and the device is not
tuned to the specified wavelength.
1253
1254
1255
1256
west-interface
Syntax
Hierarchy Level
Release Information
Description
west-interface {
node-id mac-address;
control-channel channel-name {
vlan number;
interface name interface-name
}
interface-none
ring-protection-link-end;
virtual-control-channel {
west-interface name;
east-interface name;
}
}
[edit protocols protection-group ethernet-ring ring-name]
NOTE: Always configure this port second, after configuring the east-interface
statement.
Ethernet Ring Protection Using Ring Instances for Load Balancing on page 745
Example: Configuring Ethernet Ring Protection Switching on EX Series Switches and QFX
Switches
1257
1258
CHAPTER 37
Operational Commands
show iccp
1259
1260
show interfaces (M Series, MX Series, T Series Routers, and PTX Series Management
and Internal Ethernet)
show lldp
show vrrp
traceroute ethernet
1261
can be used in the interface set name. This command will not clear the statistics of
the member logical interfaces.
Required Privilege
Level
List of Sample Output
Output Fields
clear
Sample Output
clear interfaces interface-set statistics
user@host> clear interfaces interface-set statistics
1262
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
clear
Sample Output
clear interfaces interval
The following example displays the output for a T3 interface before and after the clear
interfaces command is entered:
user@host> show interfaces interval t3-0/3/0:4
Physical interface: t3-0/3/0:4, SNMP ifIndex: 23
17:43-current:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
17:28-17:43:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
17:13-17:28:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
16:58-17:13:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
16:43-16:58:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
16:28-16:43:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
CES: 195, CSES: 195, SEFS: 195, UAS: 206
14:58-15:13:
LCV: 35, PCV: 163394, CCV: 54485, LES: 0, PES: 35, PSES: 35, CES:
35, CSES: 35, SEFS: 35, UAS: 32
Interval Total:
LCV: 230, PCV: 1145859, CCV: 455470, LES: 0, PES: 230, PSES: 230,
CES: 230, CSES: 230, SEFS: 230, UAS: 238
1263
1264
1265
Release Information
Description
Options
clear
Sample Output
clear interfaces aeX aggregate forwarding-options
user@host> clear interfaces ae1 aggregate forwarding-options load-balance state
1266
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
clear
Sample Output
clear interfaces aggregate forwarding-options
user@host> clear interfaces aggregate forwarding-options load-balance state
1267
Release Information
Description
Options
clear interfaces transport pm (all | optics | otn) (all | current | current-day) (all |
interface-name)
Required Privilege
Level
Related
Documentation
clear
Sample Output
clear interfaces transport pm
user@host> clear interfaces transport pm transport otn current all
1268
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
clear
Sample Output
clear lldp neighbors
user@switch> clear lldp neighbors
1269
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
clear
Sample Output
clear lldp statistics
user@switch> clear lldp statistics
1270
Release Information
Description
Options
Output Fields
view
Sample Output
clear oam ethernet connectivity-faultmanagement continuity-measurement
user@host> clear oam ethernet connectivity-fault-management continuity-measurement
maintenance-domain md5 maintenance-association ma5 local-mep 100 remote-mep 102
Continuity measurement restarted.
1271
Release Information
Description
Clear all the linktrace entries and the relevant path information from the database for a
particular remote host on M320, MX Series, T320, and T640 routers.
Options
view
Sample Output
clear oam ethernet connectivity-faultmanagement linktrace path-database
user@host> clear oam ethernet connectivity-fault-management linktrace path-database
maintenance-domain md1 maintenance-association ma3 00058573e483
This command produces no output.
1272
Release Information
Description
Options
counts only for MEPs attached to the specified Ethernet physical interface.
level md-level(Optional) Clear ETH-LM statistics and ETH-LM frame counts only for
view
Sample Output
clear oam ethernet connectivity-faultmanagement loss-statistics
user@host> clear oam ethernet connectivity-fault-management loss-statistics
Cleared loss measurements statistics of all CFM sessions
1273
Release Information
Description
Options
option is not specified, policer statistics are cleared for all maintenance associations
for all maintenance domains.
maintenance-association ma-name Name of an existing CFM maintenance association.
If this option is not specified, policer statistics are cleared for all maintenance
associations for given maintenance domain. This option cannot be specified without
specifying maintenance-domain name.
Required Privilege
Level
Related
Documentation
Output Fields
view
When you enter this command, you are provided feedback on the status of your request.
1274
Release Information
Description
Options
frame counts only for MEPs attached to the specified Ethernet physical interface.
level(Optional) Clear CFM statistics, ETH-DM statistics, and ETH-DM frame counts
only for MEPs within CFM maintenance domains (MDs) of the specified level.
Required Privilege
Level
Related
Documentation
view
Sample Output
clear oam ethernet connectivity-faultmanagement statistics
user@host> clear oam ethernet connectivity-fault-management statistics
Cleared statistics of all CFM sessions
1275
Release Information
Description
Options
Output Fields
view
Sample Output
clear oam ethernet connectivity-faultmanagement synthetic-lossmeasurement
user@host> clear oam ethernet connectivity-fault-management synthetic-loss-measurement
maintenance-domain md5 maintenance-association ma5 local-mep 100 remote-mep 102
Synthetic loss measurement restarted.
1276
Options
process, and reset OAM loopback state (if set previously) on all Ethernet interfaces.
interface-name(Optional) Clear OAM link fault management state information, restart
the link discovery process, and reset OAM loopback state (if set previously) on the
specified Ethernet interface only.
Required Privilege
Level
List of Sample Output
Output Fields
view
Sample Output
clear oam ethernet link-fault-management state
user@host> clear oam ethernet link-fault-management state ge-0/3/3
Cleared link-fault-management state for interface ge-0/3/3
1277
Options
view
Sample Output
clear oam ethernet link-fault-management statistics
user@host> clear oam ethernet link-fault-management statistics
Cleared link-fault-management statistics for all interfaces
1278
Release Information
Description
Options
specified group.
Required Privilege
Level
List of Sample Output
Output Fields
view
Sample Output
clear protection-group ethernet-ring statistics
To clear all Ethernet ring protection group statistics for all protection groups, use the
following command:
user@host> clear protection-group ethernet-ring statistics
Sample Output
clear protection-group ethernet-ring statistics
To clear Ethernet ring protection group statistics for the group my_prot_group, use the
following command:
user@host> clear protection-group ethernet-ring statistics group-name my_prot_group
1279
Release Information
Description
Command introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Clearreset to zero (0)all MACsec Key Agreement (MKA) protocol statistics.
You are clearing the statistics that are viewed using the show security mka statistics when
you enter this command.
Options
only.
Required Privilege
Level
clear
Sample Output
clear security mka statistics
user@switch> clear security mka statistics
1280
Release Information
Description
Command introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Clearreset to zero (0)all MACsec Key Agreement (MKA) protocol statistics.
You are clearing the statistics that are viewed using the show security mka statistics when
you enter this command.
Options
only.
Required Privilege
Level
clear
Sample Output
clear security mka statistics
user@switch> clear security mka statistics
1281
Release Information
Description
To start an Ethernet frame delay measurement session, the router initiates an exchange
of frames carrying one-way or two-way frame delay measurement protocol data units
(PDUs) between the local and remote MEPs. The frame countsthe types of and number
of Ethernet frame delay measurement PDU frames exchanged to measure frame delay
timesare displayed as the runtime output of the monitor ethernet delay-measurement
command and are also stored at both the initiator and receiver MEPs for later retrieval.
Ethernet frame delay measurement statistics, described below, are measured and stored
at only one of the MEPs:
Frame delayThe difference, in microseconds, between the time a frame is sent and
when it is received.
Frame delay variationThe difference, in microseconds, between consecutive frame delay
1282
based on the difference between the time at which the initiator MEP sends a one-way
delay measurement request (1DM) frame and the time at which the receiver MEP
receives the frame.
two-wayMeasurement type is two-way Ethernet frame delay measurement, which is
based on the difference between the time at which the initiator MEP sends a two-way
delay measurement message (DMM) frame and the time at which the initiator MEP
receives an associated two-way delay measurement reply (DMR) frame from the
responder MEP, subtracting the time elapsed at the responder MEP.
mep remote-mep-idNumeric identifier of the peer MEP with which to perform Ethernet
frame delay measurement. The discovered MAC address of the peer MEP is used.
The range of values is 1 through 8191.
remote-mac-addressUnicast MAC address of the peer MEP with which to perform
Ethernet frame delay measurement. Specify the MAC address as six hexadecimal
bytes in one of the following formats: nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn. For
example, 0011.2233.4455 or 00:11:22:33:44:55. Multicast MAC addresses are not
supported.
count frame-count(Optional) Number of frames to send to the specified peer MEP. The
The range of values is from 1 through 255 seconds. The default value is 1 second.
priority 802.1p value(Optional) Priority of the delay measurement request frame
To display the frame counts collected at an MEP as the result of this command, see the
following command descriptions in the CLI Explorer:
1283
To display the statistics collected at an MEP as the result of this command, see the
following command descriptions in the CLI Explorer.
To clear both the frame counts and the statistics collected for MEPs, use the clear oam
ethernet connectivity-fault-management statistics command, described in the CLI Explorer.
For a complete description of Ethernet frame delay measurement, see the ITU-T Y.1731
Ethernet Service OAM topics in the Junos OS Network Interfaces Library for Routing Devices.
Required Privilege
Level
List of Sample Output
Output Fields
Table 81 on page 1284 lists the run-time output fields for the monitor ethernet
delay-measurement one-way command.
Table 82 on page 1285 lists the run-time output fields for the monitor ethernet
delay-measurement two-way command.
Output fields are listed in the approximate order in which they appear.
Interface
Name of the Ethernet physical, logical, or trunk interface to which the local MEP is attached.
Packets transmitted
Total number of 1DM PDU frames sent to the remote MEP during this measurement session.
Average delay
1284
NOTE: For one-way delay measurement, these CLI output fields display NA (not applicable) at the initiator MEP because
one-way frame delay measurements occur at the receiver MEP.
Interface
Name of the Ethernet physical, logical, or trunk interface to which the local MEP is attached.
Unicast MAC address of the remote MEP that transmitted this DMR frame in response to a DMM
frame.
Delay
Delay variation
Difference, in microseconds, between the current and previous delay values. This is also known as
frame jitter.
Packets transmitted
Total number of DMM PDU frames sent to the remote MEP in this measurement session.
Total number of DMR PDU frames received from the remote MEP in this measurement session.
Average delay
Sample Output
monitor ethernet delay-measurement one-way
user@host> monitor ethernet delay-measurement one-way 00:05:85:73:39:4a
maintenance-domain md6 maintenance-association ma6 count 10
One-way ETH-DM request to 00:05:85:73:39:4a, Interface xe-5/0/0.0
1DM Frames sent : 10
--- Delay measurement statistics --Packets transmitted: 10
Average delay: NA, Average delay variation: NA
Best case delay: NA, Worst case delay: NA
1285
0 usec
8 usec
0 usec
19 usec
1 usec
9 usec
3 usec
30 usec
0 usec
16 usec
--- Delay measurement statistics --Packets transmitted: 10, Valid packets received: 10
Average delay: 103 usec, Average delay variation: 8 usec
Best case delay: 92 usec, Worst case delay: 122 usec
0 usec
8 usec
0 usec
19 usec
1 usec
9 usec
3 usec
30 usec
16 usec
--- Delay measurement statistics --Packets transmitted: 10, Valid packets received: 9, Invalid packets received: 1
Average delay: 105 usec, Average delay variation: 9 usec
Best case delay: 92 usec, Worst case delay: 122 usec
1286
Release Information
Description
To start an Ethernet frame loss measurement session, the router first sends frames with
ETH-LM information to a peer MEP and similarly receives frames with ETH-LM information
from the peer MEP. Frame loss is calculated by collecting the counter values applicable
for ingress and egress service frames where the counters maintain a count of transmitted
and received data frames between a pair of MEPs. The loss measurement statistics are
retrieved as the output of the monitor ethernet loss-measurement command and are also
stored at the initiator. The frames counts are stored at both the initiator and the receiver
MEPs for later retrieval.
Options
frame loss measurement. The discovered MAC address of the peer MEP is used. The
range of values is from 1 through 8192.
remote-mac-addressUnicast MAC address of the peer MEP with which to perform
Ethernet frame loss measurement. Specify the MAC address as six hexadecimal
bytes in one of the following formats: nnnn.nnnn.nnnn or nn:nn:nn:nn:nn:nn (for
1287
range of values is from 1 through 65535 frames. The default value is 10 frames.
local-mep mep-id(Required when multiple MEPs are configured) Identifier for the local
maintenance endpoint.
wait interval-seconds(Optional) Number of seconds to wait between sending frames.
The range of values is from 1 through 255 seconds. The default value is 1 second.
priority 802.1p value(Optional) Priority of the delay measurement request frame. The
frame.
xml(Optional) Allow the output of the command to be displayed in XML format.
Additional Information
To display the interator output for an LM session, run the following command:
To display the frame counts collected at an MEP as the result of this command, see the
following command descriptions in the CLI Explorer:
To display the statistics collected at an MEP as the result of this command, see the
following command descriptions in the CLI Explorer:
To clear both the frame counts and the statistics collected for MEPs, use the clear oam
ethernet connectivity-fault-management loss-statistics maintenance-domain md-name
maintenance-association ma-name command, as described in the CLI Explorer.
For a complete description of Ethernet frame loss measurement, see the ITU-T Y.1731
Ethernet Service OAM topics in the Junos OS Network Interfaces Library for Routing Devices.
Required Privilege
Level
1288
Related
Documentation
CLI Explorer
Interface
Name of the Ethernet physical, logical, or trunk interface to which the local MEP is attached.
Unicast MAC address of the remote MEP that transmitted this LMR frame in response to a loss
measurement message (LMM) frame.
Ratio, expressed as a percentage, of the number of service frames not delivered divided by the
total number of service frames during time interval T at the ingress interface.
Ratio, expressed as a percentage, of the number of service frames not delivered divided by the
total number of service frames during time interval T at the egress interface.
Total number of LMM PDU frames sent to the remote MEP in this measurement session.
Total number of LMR PDU frames received from the remote MEP in this measurement session.
Average frame loss measured in this session associated with ingress data frames.
Average frame loss ratio measured in this session associated with ingress data frames.
Average frame loss measured in this session associated with egress data frames.
Average frame loss ratio measured in this session associated with egress data frames.
Lowest frame loss measured in this session associated with ingress data frames.
Lowest frame loss ratio measured in this session associated with ingress data frames.
1289
Highest frame loss measured in this session associated with ingress data frames.
Highest frame loss ratio measured in this session associated with ingress data frames.
Lowest frame loss measured in this session associated with egress data frames.
Lowest frame loss ratio measured in this session associated with egress data frames.
Highest frame loss measured in this session associated with egress data frames.
Highest frame loss ratio measured in this session associated with egress data frames.
Note that in the preceding table, the term number of service frames not delivered is the
difference between the number of service frames arriving at the ingress Ethernet flow
point and the number of service frames delivered at the egress Ethernet flow point in a
point-to-point Ethernet connection.
Sample Output
monitor ethernet lossmeasurement
user@host> monitor ethernet loss-measurement mep 2 64:87:88:6a:da:94 maintenance-domain
md maintenance-association ma count 10
ETH-LM request to 64:87:88:6a:da:94, Interface ge-2/3/2.0
LMR received from 64:87:88:6a:da:94
Near-end frame loss(CIR)
:0
Far-end frame loss(CIR):0
Near-end frame loss ratio(CIR):0.00000% Far-end frame loss ratio(CIR):0.00000%
Near-end frame loss(EIR)
:0
Far-end frame loss(EIR):260
Near-end frame loss ratio(EIR):0.00000% Far-end frame loss ratio(EIR):88.43537%
LMR received from 64:87:88:6a:da:94
Near-end frame loss(CIR)
:0
Far-end frame loss(CIR):1
Near-end frame loss ratio(CIR):0.00000% Far-end frame loss ratio(CIR):0.51546%
Near-end frame loss(EIR)
:0
Far-end frame loss(EIR):257
Near-end frame loss ratio(EIR):0.00000% Far-end frame loss ratio(EIR):88.31615%
LMR received from 64:87:88:6a:da:94
Near-end frame loss(CIR)
:0
Far-end frame loss(CIR):0
Near-end frame loss ratio(CIR):0.00000% Far-end frame loss ratio(CIR):0.00000%
Near-end frame loss(EIR)
:0
Far-end frame loss(EIR):261
Near-end frame loss ratio(EIR):0.00000% Far-end frame loss ratio(EIR):88.77551%
LMR received from 64:87:88:6a:da:94
Near-end frame loss(CIR)
:0
Far-end frame loss(CIR):0
Near-end frame loss ratio(CIR):0.00000% Far-end frame loss ratio(CIR):0.00000%
1290
1291
Release Information
Description
Options
is not configured, Junos OS waits for the timer configured using the revert-time
statement at the [edit interfaces aeX mc-ae] hierarchy level to expire before it triggers
the switchover.
mcae-id mcae-idTriggers switchover for the specified mc-ae interface.
Required Privilege
Level
Related
Documentation
Output Fields
view
Sample Output
request interface mc-ae switchover immediate mcae-id
user@host >request interface mc-ae switchover immediate mcae-id 2
MCAE: Switchover Done
Sample Output
request interface mc-ae switchover mcae-id
user@host >request interface mc-ae switchover mcae-id 2
1292
1293
On M Series and T Series routers, use the request interface (revert | switchover) (Adaptive
Services) operational command to manually revert to the primary adaptive services
interface or link services interface, or to switch from the primary to the secondary interface.
For information about this command, see request interface (revert | switchover) (Adaptive
Services).
Options
Required Privilege
Level
List of Sample Output
Output Fields
view
Sample Output
request interface revert
user@host >request interface revert ae1
1294
Options
Required Privilege
Level
List of Sample Output
Output Fields
view
Sample Output
request lacp link-switchover aeX
user@host >request lacp link-switchover ae0ae0: Request succeeded
1295
Syntax
Syntax (T4000
Router)
Syntax (MX104,
MX2010, and MX2020
1296
3D Universal Edge
Routers)
<models>
<satellite [slot-id slot-id |device-alias alias-name]>
Release Information
Description
On EX8208 and EX8216 switchesRefers to a line card; FPC number equals the slot
number for the line card.
1297
On QFX3500, QFX5100, and OCX Series standalone switches, both the FPC and FPC
number are always 0.
On T4000 Type 5 FPCs, there are no top temperature sensor or bottom temperature
sensor parameters. Instead, fan intake temperature sensor and fan exhaust temperature
sensors parameters are displayed.
Starting from Junos OS Release 11.4, the output of the show chassis hardware models
operational mode command displays the enhanced midplanes FRU model numbers
(CHAS-BP3-MX240-S, CHAS-BP3-MX480-S or CHAS-BP3-MX960-S) based on the
router. Prior to release 11.4, the FRU model numbers are left blank when the router has
enhanced midplanes. Note that the enhanced midplanes are introduced through the
Junos OS Release 13.3, but can be supported on all Junos OS releases.
Starting with Junos OS Release 14.1, the output of the show chassis hardware detail |
extensive | clei-models | models operational mode command displays the new DC power
supply module (PSM) and power distribution unit (PDU) that are added to provide power
to the high-density FPC (FPC2-PTX-P1A) and other components in a PTX5000 Packet
Transport Router.
Options
about the TX Matrix router and its attached T640 routers. For a TX Matrix Plus router,
display information about the TX Matrix Plus router and its attached routers.
clei-models(Optional) Display Common Language Equipment Identifier (CLEI) barcode
router, display hardware information for a specified T640 router (line-card chassis)
that is connected to the TX Matrix router. On a TX Matrix Plus router, display hardware
information for a specified router (line-card chassis) that is connected to the
TX Matrix Plus router.
Replace number with the following values depending on the LCC configuration:
1298
0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local(MX Series routers only) (Optional) Display hardware-specific information for the
for components that use ID EEPROM format v2, the CLEI code.
node-device name(QFabric systems only) (Optional) Display hardware-specific
hardware information for the specified satellite device in a Junos Fusion, or for all
satellite devices in the Junos Fusion if no satellite devices are specified.
scc(TX Matrix router only) (Optional) Display hardware information for the TX Matrix
the TX Matrix Plus router (switch-fabric chassis). Replace number variable with 0.
Additional Information
The show chassis hardware detail command now displays DIMM information for the
following Routing Engines:
Routers
RE-A-1800x2
In Junos OS Release 11.4 and later, the output for the show chassis hardware models
operational mode command for MX Series routers display the enhanced midplanes FRU
model numbersCHAS-BP3-MX240-S, CHAS-BP3-MX480-S, or
CHAS-BP3-MX960-Sbased on the router. In releases before Junos OS Release 11.4,
the FRU model numbers are left blank when the router has enhanced midplanes. Note
that the enhanced midplanes are introduced through Junos OS Release 13.3, but can be
supported on all Junos OS releases.
Required Privilege
Level
view
1299
Related
Documentation
List of Sample Output
1300
show chassis hardware models (MX960 Router with Enhanced MX SCB) on page 1338
show chassis hardware (MX960 Router with MPC5EQ) on page 1339
show chassis hardware detail (MX960 Router) on page 1342
show chassis hardware detail (MX960 Router with MPC5EQ) on page 1342
show chassis hardware extensive (MX960 Router with MPC5EQ) on page 1345
show chassis hardware models (MX960 Router with MPC5EQ) on page 1354
show chassis hardware clei-models (MX960 Router with MPC5EQ) on page 1354
show chassis hardware (MX2010 Router) on page 1355
show chassis hardware detail (MX2010 Router) on page 1357
show chassis hardware extensive (MX2010 Router) on page 1362
show chassis hardware models (MX2010 Router) on page 1367
show chassis hardware clei-models (MX2010 Routers) on page 1368
show chassis hardware (MX2010 Routers with MPC6E and OTN MIC) on page 1368
show chassis hardware detail (MX2010 Routers with MPC6E and OTN MIC) on page 1370
show chassis hardware extensive (MX2010 Routers with MPC6E and OTN
MIC) on page 1372
show chassis hardware (MX2020 Router) on page 1377
show chassis hardware detail (MX2020 Router) on page 1386
show chassis hardware models (MX2020 Router) on page 1394
show chassis hardware clei-models (MX2020 Router) on page 1396
show chassis hardware (MX2020 Router with MPC5EQ and MPC6E) on page 1397
show chassis hardware detail (MX2020 Router with MPC5EQ and MPC6E) on page 1402
show chassis hardware extensive (MX2020 Router with MPC5EQ and
MPC6E) on page 1403
show chassis hardware models (MX2020 Routers with MPC5EQ and
MPC6E) on page 1409
show chassis hardware clei-models (MX2020 Router with MPC5EQ and
MPC6E) on page 1410
show chassis hardware (MX Series routers with ATM MIC) on page 1411
show chassis hardware (MX240, MX480, MX960 routers with Application Services
Modular Line Card) on page 1412
show chassis hardware extensive (MX240, MX480, MX960 routers with Application
Services Modular Line Card) on page 1412
show chassis hardware (MX480 Router with MPC4E) on page 1413
show chassis hardware (MX2020 Router with MPC4E) on page 1414
show chassis hardware (MX5, MX10, MX40, MX80, MX240, MX480, and MX960
routers with Enhanced 20-port Gigabit Ethernet MIC) on page 1416
show chassis hardware models (MX5, MX10, MX40, MX80, MX240, MX480, and
MX960 routers with Enhanced 20-port Gigabit Ethernet MIC) on page 1416
show chassis hardware (T320 Router) on page 1417
show chassis hardware (T640 Router) on page 1418
show chassis hardware models (T640 Router) on page 1418
show chassis hardware extensive (T640 Router) on page 1419
show chassis hardware (T4000 Router) on page 1420
show chassis hardware (T4000 Router with 16 GB line card chassis (LCC) Routing
Engine) on page 1422
show chassis hardware (T4000 Router with LSR FPC) on page 1422
show chassis hardware clei-models (T4000 Router) on page 1422
show chassis hardware detail (T4000 Router) on page 1423
1301
1302
Table 85 on page 1303 lists the output fields for the show chassis hardware command.
Output fields are listed in the approximate order in which they appear.
Field Description
Level of Output
Item
Chassis component:
All levels
Version
All levels
1303
Field Description
Level of Output
Part number
All levels
Serial number
Serial number of the chassis component. The serial number of the backplane
is also the serial number of the router chassis. Use this serial number when you
need to contact Juniper Networks Customer Support about the router or switch
chassis.
All levels
Assb ID or
Assembly ID
(extensive keyword only) Identification number that describes the FRU hardware.
extensive
Assembly Version
extensive
Assembly Flags
extensive
(clei-models, extensive, and models keyword only) Model number of the FRU
hardware component.
none specified
CLEI code
none specified
EEPROM Version
ID EEPROM version used by the hardware component: 0x00 (version 0), 0x01
(version 1), or 0x02 (version 2).
extensive
Description
All levels
Type of PIC. If the PIC type is not supported on the current software release,
the output states Hardware Not Supported.
Type of FPC: FPC Type 1, FPC Type 2, FPC Type 3, FPC Type 4 , or FPC
TypeOC192.
On EX Series switches, a brief description of the FPC.
The following list shows the PIM abbreviation in the output and the
corresponding PIM name.
1000-Mbps port)
1304
2x T1Dual-port T1 PIM
2x E1Dual-port E1 PIM
Field Description
Level of Output
1x ADSL Annex AADSL 2/2+ Annex A PIM (one port, for POTS)
1x ADSL Annex BADSL 2/2+ Annex B PIM (one port, for ISDN)
module)
media module with one E1 or T1 trunk termination port and ISDN PRI
backup)
ports)
For small form-factor pluggable transceiver (SFP) modules, the type of fiber:
LX, SX, LH, or T.
Sample Output
show chassis hardware (EX8216 Switch)
user@host> show chassis hardware
Hardware inventory:
Item
Version Part number
Chassis
REV 06
Midplane
REV 06
710-016845
CB 0
REV 22
710-020771
Serial number
CY0109220035
BA0909120112
AX0109197723
Description
EX8216
EX8216-MP
EX8216-RE320
1305
CB 1
Routing Engine
FPC 3
CPU
FPC 4
CPU
PIC 0
Base-X
Xcvr 1
Xcvr 11
Xcvr 12
Xcvr 13
Xcvr 14
Xcvr 15
Xcvr 21
Xcvr 22
Xcvr 23
Xcvr 24
Xcvr 25
Xcvr 26
Xcvr 27
Xcvr 28
Xcvr 29
Xcvr 30
Xcvr 31
Xcvr 32
Xcvr 33
Xcvr 34
Xcvr 35
Xcvr 36
Xcvr 37
Xcvr 38
Xcvr 39
Xcvr 40
Xcvr 41
Xcvr 43
Xcvr 45
FPC 13
CPU
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
SIB 5
SIB 6
SIB 7
PSU 0
PSU 1
PSU 2
PSU 3
PSU 4
PSU 5
Top Fan Tray
FTC 0
FTC 1
Bottom Fan Tray
FTC 0
FTC 1
LCD 0
1306
REV
1
REV
REV
REV
REV
22
710-020771
BUILTIN
710-020683
710-020598
710-020683
710-020598
BUILTIN
AX0109197726
BUILTIN
BC0109083125
BF0109144549
BC0108500127
BF0108460510
BUILTIN
EX8216-RE320
RE-EX8216
EX8200-48F
EX8200-CPU
EX8200-48F
EX8200-CPU
48x 100 Base-QFX/1000
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
16
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011782
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
740-011613
710-016837
PE70V89
PE70YCE
PE70VSH
E08C02063
PE70VKU
E08E03372
PE70VAD
E08E01228
PE70VSL
E08E03409
PE70VL4
PDQ4L2Z
PE70WFK
PBD2B5U
PE70UQX
PE70VL5
PE70V0F
E08C02052
E08C02197
PE70V0L
E08E03390
PDQ4VL9
E08E03370
E08E03362
E08C02065
E08E03405
E08E03411
E08C02171
E08E03410
BB0109051344
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
EX8200-8XS
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
10
10
10
10
10
10
10
10
17
17
17
17
17
17
710-021613
710-021613
710-021613
710-021613
710-021613
710-021613
710-021613
710-021613
740-021466
740-021466
740-021466
740-021466
740-021466
740-021466
AY0109166244
AY0109166357
AY0109166362
AY0109166338
AY0109166350
AY0109166365
AY0109166361
AY0109166399
BG0709170003
BG0709170004
BG0709170020
BG0709170017
BG0709170008
BG0709170018
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8216-SF320
EX8200-AC2K
EX8200-AC2K
EX8200-AC2K
EX8200-AC2K
EX8200-AC2K
EX8200-AC2K
REV 4
REV 4
760-022620
760-022620
CX1209140212
CX1209140212
EX8216-FT
EX8216-FT
REV 4
REV 4
REV 04
760-022620
760-022620
710-025742
CX1209140211
CX1209140211
CE0109186919
EX8216-FT
EX8216-FT
EX8200 LCD
19
13
17
10
1307
PIC 3
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
15
07
07
07
07
07
750-009450
710-013074
710-013074
710-013074
710-013074
710-013074
PC-1OC192-SON-SR2
SIB-I-T1600-S
SIB-I-T1600-S
SIB-I-T1600-S
SIB-I-T1600-S
SIB-I-T1600-S
FANTRAY-T-S
FANTRAY-T-S
FAN-REAR-TX-T640-S
Serial number
BM0208327733
BM0208327733
BM0208327733
BM0208327733
BUILTIN
BUILTIN
AR0208162285
AK0208328289
AT0508346354
Description
EX4200-24T
EX4200-24T, 8 POE
EX4200-24T, 8 POE
EX4200-24T, 8 POE
FPC CPU
24x 10/100/1000 Base-T
4x GE SFP
EX4200-24T, 8 POE
PS 320W AC
Fan Tray
Serial number
PD3713160055
PD3713160055
PD3713160055
BUILTIN
BUILTIN
BUILTIN
1EDA3090026
Description
EX4300-48P
EX4300-48P
EX4300-48P
FPC CPU
48x 10/100/1000 Base-T
4x 40GE
JPSU-1100-AC-AFO-A
Fan Module, Airflow Out
Serial number
GG0210271867
GG0210271867
BUILTIN
H884FS00JC09
Serial number
JN111DA44RFB
TS2912
XN1804
Description
EX9208
EX9208-BP
Front Panel Display
1308
Part number
710-017414
710-017254
PEM 0
Rev 01
740-022697
QCS0906C033
AC in
PEM 1
Rev 01
740-022697
QCS0906C095
AC in
Routing Engine 0 REV 08
740-031116
9009122883
CB 0
REV 16
750-031391
CAAW4391
PC 0
REV 07
750-049612
CABJ9312
CPU
REV 04
711-038484
CABH8268
MIC 0
REV 02
750-049607
CABT9623
PIC 0
BUILTIN
BUILTIN
PIC 1
BUILTIN
BUILTIN
PIC 2
BUILTIN
BUILTIN
PIC 3
BUILTIN
BUILTIN
FPC 1
REV 10
710-013699
CAAN3529
CPU
REV 04
711-038484
CAAL7608
MIC 0
REV 26
750-028392
CAAS5151
PIC 0
BUILTIN
BUILTIN
PIC 1
BUILTIN
BUILTIN
MIC 1
REV 26
750-028392
CAAC8006
PIC 2
BUILTIN
BUILTIN
Xcvr 8
REV 01
740-011613
E08L03674
Xcvr 9
REV 01
740-011613
E08M00243
PIC 3
BUILTIN
BUILTIN
FPC 3
REV 10
710-013699
CAAR5261
CPU
REV 04
711-038484
CAAS2118
MIC 0
REV 26
750-028392
CAAS5067
PIC 0
BUILTIN
BUILTIN
Xcvr 2
REV 01
740-031851
PNA7L8U
Xcvr 3
REV 02
740-011613
AM0943SEKGZ
Xcvr 4
REV 02
740-011613
AM0943SEJZ9
PIC 1
BUILTIN
BUILTIN
MIC 1
REV 26
750-028392
CAAS5132
PIC 2
BUILTIN
BUILTIN
Xcvr 4
REV 01
740-011613
E08D02625
Xcvr 9
REV 02
740-011613
PJH4RD9
PIC 3
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-011613
AM0813S8YME
Fan Tray
PS 1.2-1.7kW; 100-240V
PS 1.2-1.7kW; 100-240V
RE-S-EX9200-1800X4
EX9200-SCBEF
EX9200 40x1G Copper
MPCE PMB 2G
40x 1GE RJ45
10x 1GE RJ45
10x 1GE RJ45
10x 1GE RJ45
10x 1GE RJ45
EX9200-40x1G-SFP
MPCE PMB 2G
20x 1GE SFP
10x 1GE SFP
10x 1GE SFP
20x 1GE SFP
10x 1GE SFP
SFP-SX
SFP-SX
10x 1GE SFP
EX9200-40x1G-SFP
MPCE PMB 2G
20x 1GE SFP
10x 1GE SFP
SFP-SX
SFP-SX
SFP-SX
10x 1GE SFP
20x 1GE SFP
10x 1GE SFP
SFP-SX
SFP-SX
10x 1GE SFP
SFP-SX
Left Fan Tray
Part number
710-008761
Serial number
31959
CA0209
PD10272
1000396803
CA0166
HM2275
CA0142
Description
M7i
M7i Midplane
AC Power Supply
RE-5.0
Internet Processor IIv1
E-FPC
1x G/E, 1000 BASE-SX
1x G/E, 1000 BASE-SX
1x G/E, 1000 BASE-SX
1x G/E, 1000 BASE-SX
E-FPC
ASP - Integrated
2x F/E, 100 BASE-TX
Serial number
B1157
DM0840
Description
M7i
M7i Midplane
HJ6416
HJ6423
HJ6421
HJ0425
1309
Power Supply 0
Routing Engine
CFEB
FPC 0
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 3
PIC 2
PIC 3
FPC 1
PIC 2
PIC 3
Xcvr 0
Fan Tray
Rev 08
REV 07
REV 09
740-008537
740-011202
750-010463
TE53755
1000736567
DK6952
REV
REV
REV
REV
12
01
01
01
REV
REV
REV
REV
REV
REV
03
01
01
01
15
01
750-012838
740-011614
740-011615
740-011614
NON-JNPR
750-023116
740-012434
740-012434
740-016064
750-014895
750-025390
DL7993
PD94TDJ
PAD5EER
PD94THU
PDC2E7A
JT0203
AGT063832PS
AGT063832LY
C06J19018
DM5757
JW9448
REV 09
REV 01
BUILTIN
750-009099
740-012434
BUILTIN
DM0899
AGT07150HGJ
AC Power Supply
RE-850
Internet Processor II
E-FPC
4x 1GE(LAN), IQ2
SFP-LX10
UNSUPPORTED
SFP-LX10
SFP-LX10
4x CHSTM1 SDH CE SFP
SFP-SR
SFP-SR
SFP-LR
MultiServices 100
12x T1/E1 CE
E-FPC
1x Tunnel
1x G/E, 1000 BASE
UNSUPPORTED
Rear Fan Tray
Serial number
1122
S/N AC6626
S/N LC36095
S/N LC36100
S/N AC6656
18000005dfb3fb01
S/N AC6632
Description
M10
S/N AB2485
S/N AA1048
AC
AC
teknor
Internet Processor II
FANTRAY-M10I-S
FANTRAY-M10I-S
1310
CLEI code
Fan Tray 0
Fan Tray 1
FANTRAY-M10I-S
FANTRAY-M10I-S
Serial number
20033
S/N AA7940
S/N 000001
S/N AA9704
98000004f8f27501
S/N AD5905
S00480
S00490
S001:?
S00483
N/A
S/N AB7528
S/N 304209
S/N 000603
S/N 000414
S/N AB8433
S/N AA1168
S/N AA1008
S/N AD5810
S/N AC0119
S/N 503241
S/N 306835
S/N 306832
Description
M20
CLEI code
AC
teknor
Internet Processor II
2 MB
2 MB
2 MB
2 MB
Backup
1 MB
64 MB
64 MB
2x OC-3 ATM, MM
1x OC-12 ATM, MM
1x OC-12 SONET, SMIR
4x E3
1 MB
64 MB
64 MB
Front Upper Fan Tray
Front Middle Fan Tray
Front Bottom Fan Tray
Rear Fan Tray
FPC-E
P-4FE-TX
P-2MCDS3
PE-4CHDS3
FPC-E
P-2OC3-ATM-MM
FANTRAY-F-M20-S
FANTRAY-F-M20-S
FANTRAY-F-M20-S
FANTRAY-R-M20-S
1311
Serial number
S/N AA0053
S/N 000042
S/N AAO139
S/N AA0201
S/N AA0905
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
Description
DC
cpv5000
Internet Processor I
1 MB
1 MB
1 MB
1 MB
AA0158
AA2267
AA2270
AA2269
AA2268
AA0048
AA2333
AA2332
AA2337
aa0343
AA0379
AA0377
AA0378
AA0042
AA2288
AA2331
AA2330
AA0143
AA0149
AA0148
AA0330
AA0050
AA2327
AA2329
AA2328
AA0320
AA1341
AB2462
AA7663
501590
300949
300868
AB1670
1 MB
64 MB
64 MB
1x OC-12 SONET, SMIR
1x OC-12 SONET, SMIR
1x OC-12 SONET, SMIR
1x Tunnel
1 MB
64 MB
64 MB
4x OC-3 SONET, SMIR
4x OC-3 SONET, MM
4x OC-3 SONET, MM
1x OC-12 SONET, SMIR
1 MB
64 MB
64 MB
1x OC-12 SONET, SMIR
1x OC-12 ATM, MM
1x G/E, 1000 BASE-SX
1 MB
64 MB
64 MB
1x Tunnel
1312
Serial number
AX3671
AR9074
AR7331
BB4449
MC12364
MC12383
AG1332
AR3789
3e000007c8176601
AN5813
Description
m40e
Present
SFM 0
SFM 0
SFM 1
SFM 1
FPC 0
CPU
PIC
FPC 1
CPU
PIC
FPC 2
CPU
PIC
FPC 4
CPU
PIC
PIC
FPC 6
CPU
PIC
PIC
SPP
SPR
SPP
SPR
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
0
2
0
2
07
05
07
05
01
01
03
01
01
07
02
01
03
02
01
03
01
02
01
02
01
710-001228
710-002189
710-001228
710-002189
710-011725
710-004600
750-003737
710-005197
710-004600
750-001900
710-005197
710-004600
750-003737
710-005078
710-004600
750-001894
750-002575
710-005078
710-004600
750-002911
750-002577
AG4676
AE4735
AP1347
BE0063
BE0669
BD9504
AY3991
BD9842
BB4869
AR8278
BD9824
BD9531
AY3986
BE0664
BD9559
AG7963
AF2472
BE0652
BD9607
AN2286
AP6345
Internet Processor II
Internet Processor II
M40e-EP-FPC Type 1
4x G/E, 1000 BASE-SX
M40e-FPC Type 2
1x OC-48 SONET, SMSR
M40e-FPC Type 2
4x G/E, 1000 BASE-SX
M40e-FPC Type 1
1x G/E, 1000 BASE-SX
4x OC-3 SONET, SMIR
M40e-FPC Type 1
4x F/E, 100 BASE-TX
4x OC-3 SONET, MM
0
1
2
3
4
REV
REV
REV
REV
REV
01
01
01
01
01
740-011782
740-011782
740-011782
740-011782
740-009029
Serial number
JN000054AC
RB4170
CJ9186
CJ9173
CJ9221
RM28320
RM28321
1000642883
CM8346
CP6728
CP6925
BUILTIN
62E204N00007
CJ9234
NB5229
P9F15JB
P4Q0R9G
CG4360
ND7787
P9F12AS
P9F1ALU
JW1284
P9F1AM6
P9F16NN
P8C29Y7
CN3754
CP6741
NB2855
Description
M120
M120 Midplane
M120 FPM Board
M120 FPM Display
M120 FPM CIP
AC Power Entry Module
AC Power Entry Module
RE-A-1000
M120 Control Board
M120 Control Board
M120 CFPC 10GE
1x 10GE(LAN/WAN) XFP
XFP-10G-LR
M120 FPC Type 2
2x G/E IQ, 1000 BASE
SFP-SX
SFP-SX
4x OC-3 SONET, SMIR
2x G/E IQ, 1000 BASE
SFP-SX
SFP-SX
8x 1GE(LAN), IQ2
SFP-SX
SFP-SX
SFP-SX
M120 FPC Mezz
M120 FPC Type 3
10x 1GE(LAN), 1000 BASE
P922A1F
P922A16
P922A0U
P9229UZ
P11JXWP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-LX
1313
Xcvr 6
FPC 5
PIC 0
PIC 1
REV
REV
***
REV
01
740-011613
P9F1ALW
01
710-011388
CJ9088
Hardware Not Supported ***
05
750-012052
NB0410
PIC 2
PIC 3
Board B
FEB 3
FEB 4
FEB 5
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
REV
REV
REV
REV
REV
REV
01
01
01
04
04
04
750-013167
750-010240
710-011390
710-011663
710-011663
710-011663
CM3824
CB5366
CJ9103
CP6673
CJ9368
CJ9386
SFP-SX
M120 FPC Type 1
1x CHOC3 IQ SONET, SMLR
4x CHDS3 IQ
1x G/E SFP, 1000 BASE
M120 FPC Mezz Board
M120 FEB
M120 FEB
M120 FEB
Front Top Fan Tray
Front Bottom Fan Tray
Rear Top Fan Tray
Rear Bottom Fan Tray
1314
0
1
2
3
4
6
REV
REV
REV
REV
REV
REV
REV
***
REV
01
740-011782
P922A1F
01
740-011782
P922A16
01
740-011782
P922A0U
01
740-011782
P9229UZ
01
740-009029
P11JXWP
01
740-011613
P9F1ALW
01
710-011388
CJ9088
Hardware Not Supported ***
05
750-012052
NB0410
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-LX
SFP-SX
M120 FPC Type 1
1x CHOC3 IQ SONET, SMLR
PIC 2
PIC 3
Board B
FEB 3
FEB 4
FEB 5
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
REV
REV
REV
REV
REV
REV
01
01
01
04
04
04
750-013167
750-010240
710-011390
710-011663
710-011663
710-011663
CM3824
CB5366
CJ9103
CP6673
CJ9368
CJ9386
4x CHDS3 IQ
1x G/E SFP, 1000 BASE
M120 FPC Mezz Board
M120 FEB
M120 FEB
M120 FEB
Front Top Fan Tray
Front Bottom Fan Tray
Rear Top Fan Tray
Rear Bottom Fan Tray
CLEI code
CRAFT-M120-S
PWR-M120-AC-S
PWR-M120-AC-S
RE-A-1000-2048-S
CB-M120-S
CB-M120-S
M120-cFPC-1XGE-XFP
PB-2GE-SFP-QPP
PC-4OC3-SON-SMIR
PB-2GE-SFP-QPP
PB-8GE-TYPE2-SFP-IQ2
PC-10GE-SFP
PB-1CHOC3-SMIR-QPP
PE-4CHDS3-QPP
PB-1GE-SFP
FFANTRAY-M120-S
FFANTRAY-M120-S
RFANTRAY-M120-S
RFANTRAY-M120-S
Serial number
101
S/N AB4107
S/N AA2911
S/N AA2999
S/N AA9563
S/N KJ35769
S/N KJ35765
S/N AA9794
S/N AA9804
da000004f8d57001
S/N AA9777
S/N AA2975
S/N AA9838
S/N AA2860
S/N AB0139
S/N AA9806
Description
M160
DC
DC
teknor
Internet Processor I
Internet Processor I
FPC Type 1
1315
CPU
PIC 1
PIC 2
PIC 3
FPC 1
CPU
PIC 0
PIC 1
FPC 2
CPU
PIC 0
Fan Tray
Fan Tray
Fan Tray
Fan Tray
REV
REV
REV
REV
REV
REV
REV
REV
02
05
05
01
02
02
03
01
710-001217
750-000616
750-000616
750-000616
710-001611
710-001217
750-001900
710-002381
S/N
S/N
S/N
S/N
S/N
S/N
S/N
S/N
AA9590
AA1527
AA1535
AA1519
AA9523
AA9571
AA9626
AD3633
REV 03
REV 01
710-001217
S/N AB3329
1x OC-12
1x OC-12
1x OC-12
FPC Type
ATM, MM
ATM, MM
ATM, MM
2
0
1
2
3
1316
CLEI code
Fan Tray 0
Fan Tray 1
Fan Tray 2
FFANTRAY-M320-S
FFANTRAY-M320-S
RFANTRAY-M320-S
Serial number
101
S/N AB4107
S/N AA2911
S/N AA2999
S/N AA9563
S/N KJ35769
S/N KJ35765
S/N AA9794
S/N AA9804
da000004f8d57001
S/N AA9777
S/N AA2975
S/N AA9838
S/N 306456
S/N 306474
S/N 306388
S/N 306392
S/N AA2860
S/N AB0139
S/N 302917
S/N 302662
S/N 302593
S/N 100160
S/N AA9806
S/N AA9590
S/N 302836
S00141
S0010;
S/N 302633
S00143
S00115
S/N 302952
S00135
S001=3
S/N 302892
S000?6
S001=5
S/N AA1527
S/N AA1535
S/N AA1519
S/N AA9523
S/N AA9571
S/N 306340
S00012
S0001?
S/N 306454
S00028
S0002?
S/N 306492
S00015
S00031
S/N 306363
Description
M160
DC
DC
teknor
Internet Processor I
1 MB
1 MB
1 MB
1 MB
Internet Processor I
1 MB
1 MB
1 MB
1 MB
FPC Type 1
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1x OC-12
1x OC-12
1x OC-12
FPC Type
ATM, MM
ATM, MM
ATM, MM
2
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1 MB
32 MB
32 MB
1 MB
1317
SDRAM 0
SDRAM 1
PIC 0
PIC 1
FPC 2
... SSRAM
REV
REV
REV
REV
01
01
03
01
REV 01
710-001196
710-001196
750-001900
710-002381
710-000077
S00013
S00032
S/N AA9626
S/N AD3633
S/N 306466
32 MB
32 MB
1x STM-16 SDH, SMIR
2x G/E, 1000 BASE-SX
FPC Type OC192
1 MB
Serial number
67245
RB1202
HZ5697
HR1464
HT8672
QK34208
QK34262
QF10449
QJ18257
P11123901185
JB2382
CD9926
CJ6940
AT1594
HS2746
JE7117
HE6083
CH0319
CJ6942
BD8705
CD9938
Description
M320
M320 Midplane
M320 Board
M320 FPM Display
M320 CIP
DC Power Entry Module
DC Power Entry Module
DC Power Entry Module
DC Power Entry Module
RE-4.0
M320 Control Board
M320 FPC Type 2
M320 PCA SCPU
1x OC-48 SONET, SMSR
1x Tunnel
4x G/E SFP, 1000 BASE
1x OC-48 SONET, SMSR
M320 FPC Type 1
M320 PCA SCPU
4x OC-3 SONET, SMIR
M320 FPC Type 2
CD9934
JA6540
HV9511
HW2057
JA6687
M320 SIB
M320 SIB
M320 SIB
M320 SIB
Front Top Fan Tray
Front Bottom Fan Tray
Rear Fan Tray
CLEI code
1318
FPC 1
PIC 0
PIC 1
PIC 3
FPC 2
PIC 0
PIC 1
PIC 2
PIC 3
PIC 1
PIC 2
PIC 3
FPC 3
PIC 0
PIC 1
PIC 3
FPC 4
FPC 5
FPC 6
FPC 7
PIC 0
PIC 1
PIC 2
PIC 3
SIB 0
SIB 1
SIB 2
SIB 3
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
02
04
04
03
02
10
10
07
07
10
07
07
710-010419
750-001894
750-001894
750-001894
710-010419
750-005634
750-005634
750-005634
750-005634
750-005634
750-005634
750-005634
M320-FPC1
PB-1GE-SX
PB-1GE-SX
PB-1GE-SX
M320-FPC1
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
PB-1CHOC12SMIR-QPP
REV
REV
REV
REV
REV
REV
03
04
04
02
02
02
750-001895
750-001894
750-003141
710-010419
710-010419
710-010419
PB-1OC12-SON-MM
PB-1GE-SX
PB-1GE-SX-B
M320-FPC1
M320-FPC1
M320-FPC1
REV
REV
REV
REV
REV
REV
REV
REV
15
06
07
05
03
03
03
03
750-001901
750-001900
750-001900
750-003737
710-009184
710-009184
710-009184
710-009184
PB-4OC12-SON-SMIR
PB-1OC48-SON-SMSR
PB-1OC48-SON-SMSR
PB-4GE-SX
SIB-M-S
SIB-M-S
SIB-M-S
SIB-M-S
FFANTRAY-M320-S
FFANTRAY-M320-S
RFANTRAY-M320-S
Serial number
E1368
YF5288
VA01215
VA01218
BUILTIN
BUILTIN
Description
MX5-T
MX5-T
AC Power Entry Module
AC Power Entry Module
Routing Engine
Forwarding Engine
ZA9136
BUILTIN
BUILTIN
BUILTIN
BUILTIN
YX9820
BUILTIN
AM1045SUAQ3
AM1045SUAPA
AM1045SUAN7
AM1045SU91Q
AM1045SUDDR
AM0848SB6A1
BUILTIN
AM1045SUAN0
AS0812S0719
AM0821SA121
MPC QXM
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
MPC BUILTIN
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
1319
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
PIC 3
Fan Tray
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
20
740-011613
740-011613
740-011782
740-011613
740-011613
740-011613
740-011782
750-028380
BUILTIN
BUILTIN
PF21K21
AM0848SB69Z
P9P0XV3
AM0812S8WJN
PAM3G9Q
AM0848SB4A6
P9M0U37
ZG2657
BUILTIN
BUILTIN
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
3D 2x 10GE XFP
1x 10GE XFP
1x 10GE XFP
Fan Tray
Serial number
E1372
YF5285
VB01678
BUILTIN
BUILTIN
Description
MX10-T
MX10-T
AC Power Entry Module
Routing Engine
Forwarding Engine
ZA9053
BUILTIN
BUILTIN
BUILTIN
BUILTIN
YX9436
BUILTIN
AM1107SUFQW
BUILTIN
MPC QXM
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
MPC BUILTIN
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
10x 1GE(LAN) SFP
Fan Tray
Serial number
E1367
YF5284
VB01680
VB01700
BUILTIN
BUILTIN
Description
MX40-T
MX40-T
AC Power Entry Module
AC Power Entry Module
Routing Engine
Forwarding Engine
ZA9048
BUILTIN
BUILTIN
BUILTIN
M7067UPP
K9J02UN
BUILTIN
YX3504
BUILTIN
AM0812S8WTE
PFA6KV2
AM1045SUDDM
PD63C7M
PD63DJY
AA0950STLL9
MPC QXM
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
XFP-10G-LR
XFP-10G-LR
MPC BUILTIN
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1320
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
PIC 3
Xcvr
Fan Tray
6
7
8
9
REV
REV
REV
REV
01
01
01
01
0
1
2
3
4
5
6
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
REV 01
740-011782
740-011782
740-011613
740-031851
BUILTIN
740-011613
740-031851
740-031851
740-011613
740-031851
740-031851
740-031851
740-011613
740-011613
750-021130
BUILTIN
740-011571
BUILTIN
NON-JNPR
PAR1YHC
P9P0XXL
PD63D95
AM1045SU9B8
BUILTIN
PF21L3Z
AM1045SU7M9
AM1045SUAPT
PFF2BZH
AM1045SUDDN
AM1039S00ZR
AM1045SUD6Y
PFM1QBS
PFF2E25
KG4391
BUILTIN
C645XJ04G
BUILTIN
CA49BK0AE
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
3D 2x 10GE XFP
1x 10GE XFP
XFP-10G-SR
1x 10GE XFP
XFP-10G-SR
Fan Tray
Serial number
Description
MX80-48T
MX80-48T
Routing Engine
Forwarding Engine Board
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
XFP-10G-LR
XFP-10G-LR
XFP-10G-SR
XFP-10G-SR
MPC BUILTIN
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
12x 1GE(LAN) RJ45
Fan Tray
KF9250
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
M6439D41
6XE931N00202
C715XU05F
C650XU0EP
BUILTIN
JR6981
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
Part number
Serial number
711-031594
740-028288
BUILTIN
BUILTIN
JR7084
000018
BUILTIN
BUILTIN
Description
MX80
MX80
AC Power Entry Module
Routing Engine
Forwarding Engine Board
QXM 0
FPC 0
MIC 0
711-028408
BUILTIN
BUILTIN
JR7041
BUILTIN
BUILTIN
MPC QXM
MPC BUILTIN
4x 10GE XFP
REV 05
1321
PIC 0
FPC 1
MIC 0
PIC 0
Xcvr
PIC 1
Xcvr
MIC 1
PIC 2
Xcvr
PIC 3
Xcvr
Fan Tray
REV 02
0
REV 01
REV 01
REV 02
REV 02
REV 02
BUILTIN
BUILTIN
750-028380
BUILTIN
740-014289
BUILTIN
740-014289
750-028380
BUILTIN
740-014289
BUILTIN
740-014289
BUILTIN
BUILTIN
JR6598
BUILTIN
T07M86365
BUILTIN
T07M71094
JG8548
BUILTIN
T08L86302
BUILTIN
C810XU0BA
4x 10GE XFP
MPC BUILTIN
3D 2x 10GE XFP
1x 10GE XFP
XFP-10G-SR
1x 10GE XFP
XFP-10G-SR
3D 2x 10GE XFP
1x 10GE XFP
XFP-10G-SR
1x 10GE XFP
XFP-10G-SR
Fan Tray
Serial number
G3503
CAAX5741
1H072500016
1H073050017
CAAY7935
CAAM6380
BUILTIN
Description
MX104
MX104
AC Power Entry Module
DC Power Entry Module
RE-MX-104
RE-MX-104
Forwarding Engine
BUILTIN
BUILTIN
CAAF7948
BUILTIN
PCQ0U2J
PJL7A6G
PJL7A5J
PJN5HPZ
PKB38TL
P6A107G
PKB38TR
PBK0NK3
MPC BUILTIN
MPC BUILTIN
2xOC12/8xOC3 CC-CE
2xOC12/8xOC3 CC-CE
SFP-IR
SFP-SR
SFP-SR
SFP-SR
SFP-LR
SFP-LR
SFP-LR
SFP-LR
BUILTIN
BUILTIN
BUILTIN
B10F00465
B10F00461
B10G01545
B10G01385
CAAX6538
MPC BUILTIN
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Fan Tray
Serial number
G3503
CAAX5741
1H072500016
1H073050017
CAAY7935
Description
MX104
MX104
AC Power Entry Module
DC Power Entry Module
RE-MX-104
Nand Flash 0
uhub0
1322
Freescale
usb0 (addr 2)
usb0 (addr 3)
Routing Engine 1
da0
7836 MB
AFEB 0
Processor
FPC 0
FPC 1
MIC 0
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
MIC 1
FPC 2
MIC 0
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Fan Tray 0
USB2513Bi 9491
ATP IG eUSB SSD 44801
REV 13
750-044228
ATP IG eUSB SSD
BUILTIN
BUILTIN
uhub1
umass0
RE-MX-104
Nand Flash 0
Forwarding Engine
01
01
01
01
01
01
01
01
BUILTIN
BUILTIN
750-036132
BUILTIN
740-011615
740-016068
740-016068
740-016065
740-029122
740-011787
740-029122
740-011787
BUILTIN
BUILTIN
CAAF7948
BUILTIN
PCQ0U2J
PJL7A6G
PJL7A5J
PJN5HPZ
PKB38TL
P6A107G
PKB38TR
PBK0NK3
MPC BUILTIN
MPC BUILTIN
2xOC12/8xOC3 CC-CE
2xOC12/8xOC3 CC-CE
SFP-IR
SFP-SR
SFP-SR
SFP-SR
SFP-LR
SFP-LR
SFP-LR
SFP-LR
01
01
01
01
02
BUILTIN
BUILTIN
BUILTIN
740-031980
740-031980
740-031980
740-031980
711-049570
BUILTIN
BUILTIN
BUILTIN
B10F00465
B10F00461
B10G01545
B10G01385
CAAX6538
MPC BUILTIN
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Fan Tray
REV 15
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
SMSC
ATP Electronics
CAAM6380
1323
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 34 32 31 39 00 00
Address 0x20: 53 2f 4e 20 43 41 41 58 35 37 34 31 00 1b 03 07
Address 0x30: dd ff ff ff ad 01 08 00 b0 a8 6e a7 f8 00 ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43 4c 45 49 50
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c 59 00 00 00
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff c2 47 33 35 30 33 00 00 00 00 00 00 00
PEM 0
REV 03
740-045933
1H072500016
AC Power Entry Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-045933
S/N:
1H072500016
Assembly ID: 0x0475
Assembly Version: 00.03
Date:
12-14-2012
Assembly Flags:
0x00
Version:
REV 03
CLEI Code:
IPUPAJ9KAA
ID: AC Power Entry Module
FRU Model Number: PWR-AMX1100-AC-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff 02 02 00 ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 75 00 03 52 45 56 20 30 33 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 39 33 33 00 00
Address 0x20: 31 48 30 37 32 35 30 30 30 31 36 00 00 0e 0c 07
Address 0x30: dc 30 43 ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: 02 02 00 ff 01 49 50 55 50 41 4a 39 4b 41 41 50
Address 0x50: 57 52 2d 41 4d 58 31 31 30 30 2d 41 43 2d 53 00
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 70 ff ff ff ff ff ff ff ff ff ff ff ff
PEM 1
REV 03
740-045932
1H073050017
DC Power Entry Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-045932
S/N:
1H073050017
Assembly ID: 0x0476
Assembly Version: 00.03
Date:
01-30-2013
Assembly Flags:
0x00
Version:
REV 03
CLEI Code:
IPUPAJ8KAA
ID: DC Power Entry Module
FRU Model Number: PWR-AMX1100-DC-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff 02 02 00 ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 76 00 03 52 45 56 20 30 33 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 39 33 32 00 00
Address 0x20: 31 48 30 37 33 30 35 30 30 31 37 00 00 1e 01 07
Address 0x30: dd 30 44 ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: 02 02 00 ff 01 49 50 55 50 41 4a 38 4b 41 41 50
Address 0x50: 57 52 2d 41 4d 58 31 31 30 30 2d 44 43 2d 53 00
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 72 ff ff ff ff ff ff ff ff ff ff ff ff
Routing Engine 0 REV 20
750-044228
CAAY7935
RE-MX-104
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-044228
S/N:
CAAY7935
Assembly ID: 0x0b81
Assembly Version: 01.20
Date:
03-18-2013
Assembly Flags:
0x00
Version:
REV 20
CLEI Code:
PROTOXCLEI
ID: RE-MX-104
FRU Model Number: PROTO-ASSEMBLY
Board Information Record:
Address 0x00: ad 01 00 08 b0 a8 6e a6 fc 10 ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 fe 0b 81 01 14 52 45 56 20 32 30 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 34 32 32 38 00 00
Address 0x20: 53 2f 4e 20 43 41 41 59 37 39 33 35 00 12 03 07
Address 0x30: dd ff ff ff ad 01 00 08 b0 a8 6e a6 fc 10 ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43 4c 45 49 50
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c 59 00 00 00
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff c2 ff ff ff ff ff ff ff ff ff ff ff ff
1324
da0
7836 MB ATP IG eUSB SSD
Nand Flash 0
usb0 (addr 1) EHCI root hub 0
Freescale
uhub0
usb0 (addr 2) USB2513Bi 9491
SMSC
uhub1
usb0 (addr 3) ATP IG eUSB SSD 44801 ATP Electronics
umass0
Routing Engine 1 REV 13
750-044228
CAAM6380
RE-MX-104
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-044228
S/N:
CAAM6380
Assembly ID: 0x0b81
Assembly Version: 01.13
Date:
09-17-2012
Assembly Flags:
0x00
Version:
REV 13
CLEI Code:
PROTOXCLEI
ID: RE-MX-104
FRU Model Number: PROTO-ASSEMBLY
Board Information Record:
Address 0x00: ad 01 00 08 64 87 88 27 08 18 ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 fe 0b 81 01 0d 52 45 56 20 31 33 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 34 32 32 38 00 00
Address 0x20: 53 2f 4e 20 43 41 41 4d 36 33 38 30 00 11 09 07
Address 0x30: dc ff ff ff ad 01 00 08 64 87 88 27 08 18 ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43 4c 45 49 50
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c 59 00 00 00
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff c2 ff ff ff ff ff ff ff ff ff ff ff ff
da0
7836 MB ATP IG eUSB SSD
Nand Flash 0
AFEB 0
BUILTIN
BUILTIN
Forwarding Engine
Processor
FPC 0
BUILTIN
BUILTIN
MPC BUILTIN
FPC 1
BUILTIN
BUILTIN
MPC BUILTIN
MIC 0
REV 15
750-036132
CAAF7948
2xOC12/8xOC3 CC-CE
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-036132
S/N:
CAAF7948
Assembly ID: 0x0a1a
Assembly Version: 01.15
Date:
07-03-2012
Assembly Flags:
0x00
Version:
REV 15
CLEI Code:
IP9IAM2DAA
ID: 2xOC12/8xOC3 CC-CE
FRU Model Number: MIC-3D-8OC3-2OC12-ATM
Board Information Record:
Address 0x00: 12 01 05 03 05 ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0a 1a 01 0f 52 45 56 20 31 35 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 36 31 33 32 00 00
Address 0x20: 53 2f 4e 20 43 41 41 46 37 39 34 38 00 03 07 07
Address 0x30: dc ff ff ff 12 01 05 03 05 ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 39 49 41 4d 32 44 41 41 4d
Address 0x50: 49 43 2d 33 44 2d 38 4f 43 33 2d 32 4f 43 31 32
Address 0x60: 2d 41 54 4d 00 00 41 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff e3 c0 02 a3 9c 00 00 00 00 0a 60 00 00
PIC 0
BUILTIN
BUILTIN
2xOC12/8xOC3 CC-CE
Xcvr 0
REV 01
740-011615
PCQ0U2J
SFP-IR
Xcvr 1
REV 01
740-016068
PJL7A6G
SFP-SR
Xcvr 2
REV 01
740-016068
PJL7A5J
SFP-SR
Xcvr 3
REV 01
740-016065
PJN5HPZ
SFP-SR
Xcvr 4
REV 01
740-029122
PKB38TL
SFP-LR
Xcvr 5
REV 01
740-011787
P6A107G
SFP-LR
Xcvr 6
REV 01
740-029122
PKB38TR
SFP-LR
Xcvr 7
REV 01
740-011787
PBK0NK3
SFP-LR
MIC 1
FPC 2
BUILTIN
BUILTIN
MPC BUILTIN
MIC 0
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
Jedec Code:
0x0000
EEPROM Version:
0x00
P/N:
BUILTIN
S/N:
BUILTIN
Assembly ID: 0x0a60
Assembly Version: 00.00
Date:
00-00-0000
Assembly Flags:
0x00
1325
00 00 00 00
00
4d
00
00
00
00
00
0a
00
58
00
00
00
00
00
1a
00 00
43 00
00 00
00 00
00 00
00 00
00 00
01 0f
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Fan Tray
0x02
CAAX6538
01.02
0x00
PROTOXCLEI
PROTO-ASSEMBLY
ff ff ff ff
30
37
00
ff
4c
59
ff
ff
32
30
01
ff
45
00
ff
ff
00
00
03
ff
49
00
ff
ff
00
00
07
ff
50
00
ff
ff
Serial number
CAAS5849
1H072400065
CAAR5915
BUILTIN
BUILTIN
BUILTIN
CAAK7103
BUILTIN
CAAX6538
MIC-3D-20GE-SFP-EH
PROTO-ASSEMBLY
1326
FPC 1
MIC 0
FPC 2
Fan Tray
REV 01
REV 02
BUILTIN
750-046905
BUILTIN
711-049570
PROTOXCLEI
CAAX6538
MIC-3D-20GE-SFP-EH
PROTO-ASSEMBLY
Serial number
JN10C7F7EAFC
TR1502
KD4017
000332
Description
MX240
MX240 Backplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
000226
PS 1.2-1.7kW; 100-240V
1000703522
1000687625
KC9057
JY4760
KC7340
KD4078
BUILTIN
P9F18ME
BUILTIN
BUILTIN
BUILTIN
JS4529
KB3969
BUILTIN
PBG3Y79
PBG3XU8
PBG3YG6
PBG3XUG
PBG3XTJ
BUILTIN
PBG3ZUM
PBG3Y5H
PBG3UZT
PBG3US1
BUILTIN
PBG3YG7
PBG3XZ9
PBG3XTY
PBG3UZG
BUILTIN
PBG3Y8W
PBG3YVX
PBG3YB3
PBG43VQ
JS4642
RE-S-2000
RE-S-1300
MX SCB
MX SCB
DPCE 40x 1GE R
DPC PMB
10x 1GE(LAN)
SFP-SX
10x 1GE(LAN)
10x 1GE(LAN)
10x 1GE(LAN)
DPCE 40x 1GE R EQ
DPC PMB
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
MX240 Fan Tray
show chassis hardware detail (MX 240 Router with Routing Engine Displaying DIMM information)
user@host> show chassis hardware detail
Item
Chassis
Midplane
FPM Board
Version
Part number
REV 07
REV 03
760-021404
760-021392
Serial number
JN11279B4AFC
TS2474
XC2643
Description
MX240 Backplane
MX240 Backplane
Front Panel Display
1327
PEM 0
Rev 03
740-017343
QCS0908A068
DC Power Entry Module
Routing Engine 0 REV 01
740-031117
AARCHOO
RE-S-1800x4
ad0
3764 MB STEC M2+ CF 9.0.2
STIM2Q3209239145303 Removable Compact Flash
ad1
28626 MB
usb0 (addr 1)
usb0 (addr 2)
DIMM 0
DIMM 1
DIMM 2
DIMM 3
CB 0
Fan Tray 0
1328
Serial number
JN10C7F7EAFC
TR1502
KD4017
000332
Description
MX240
MX240 Backplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
000226
PS 1.2-1.7kW; 100-240V
1000703522
1000687625
YE8494
YOP5764
KC7340
KD4078
BUILTIN
P9F18ME
BUILTIN
BUILTIN
BUILTIN
JS4529
KB3969
BUILTIN
PBG3Y79
PBG3XU8
PBG3YG6
PBG3XUG
PBG3XTJ
BUILTIN
PBG3ZUM
PBG3Y5H
PBG3UZT
PBG3US1
BUILTIN
PBG3YG7
PBG3XZ9
PBG3XTY
PBG3UZG
BUILTIN
PBG3Y8W
PBG3YVX
PBG3YB3
PBG43VQ
JS4642
RE-S-2000
RE-S-1300
Enhanced MX SCB
Enhanced MX SCB
DPCE 40x 1GE R
DPC PMB
10x 1GE(LAN)
SFP-SX
10x 1GE(LAN)
10x 1GE(LAN)
10x 1GE(LAN)
DPCE 40x 1GE R EQ
DPC PMB
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
MX240 Fan Tray
Serial number
JN10C7F7FAFB
TR2071
KB8459
QCS07519029
Description
MX480
MX480 Midplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
QCS07519041
PS 1.2-1.7kW; 100-240V
QCS07519097
PS 1.2-1.7kW; 100-240V
1000733381
1000733540
KA8022
KA8303
KA8660
KA8185
BUILTIN
BUILTIN
BUILTIN
BUILTIN
RE-S-2000
RE-S-2000
MX SCB
MX SCB
DPCE 40x 1GE X EQ
DPC PMB
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
Left Fan Tray
Serial number
JN10C7F7FAFB
TR2071
KB8459
QCS07519029
Description
MX480
MX480 Midplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
QCS07519041
PS 1.2-1.7kW; 100-240V
QCS07519097
PS 1.2-1.7kW; 100-240V
1000733381
1000733540
KA8022
KA8303
KA8660
KA8185
BUILTIN
BUILTIN
BUILTIN
BUILTIN
RE-S-2000
RE-S-2000
Enhanced MX SCB
Enhanced MX SCB
DPCE 40x 1GE X EQ
DPC PMB
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
10x 1GE(LAN) EQ
Left Fan Tray
show chassis hardware (MX480 Routers with MPC5E and built-in OTN PIC)
user@host> show chassis hardware
Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 05
710-017414
FPM Board
REV 02
710-017254
PEM 0
Rev 05
740-029970
Serial number
JN11C0338AFB
ABAB8430
ZS8005
QCS1024U089
Description
MX480
MX480 Midplane
Front Panel Display
PS 1.4-2.52kW; 90-264V
1329
AC in
PEM 1
Rev 10
740-029970
QCS1314U0FJ
AC in
PEM 2
Rev 07
740-029970
QCS1121U076
AC in
Routing Engine 0 REV 05
740-031116
9009092471
Routing Engine 1 REV 05
740-031116
9009097958
CB 0
REV 16
750-031391
CAAX0789
CB 1
REV 16
750-031391
CAAX0856
FPC 0
REV 32
750-028467
ABBP1782
CPU
REV 10
711-029089
ABBP5410
PIC 0
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-021308
983152A00038
Xcvr 1
REV 01
740-031980
B11F00211
Xcvr 2
REV 01
740-031980
AQ72LPB
Xcvr 3
REV 01
740-031980
AHN0WR5
PIC 1
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-031980
B11J03627
Xcvr 1
REV 01
740-031980
B11F00300
Xcvr 2
REV 01
740-021308
AQ42WSS
Xcvr 3
REV 01
740-021308
AQ43HGC
PIC 2
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-021308
ANA0ND0
Xcvr 1
REV 01
740-021308
ANA0NGF
Xcvr 2
REV 01
740-021308
ANA0NG9
Xcvr 3
REV 01
740-021308
ANA0MP9
PIC 3
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-021308
AQA06CG
Xcvr 1
REV 01
740-021308
19T511100493
Xcvr 2
REV 01
740-031980
APR040J
FPC 1
REV 26
750-046005
CACN1894
CPU
REV 09
711-045719
CACN8698
PIC 0
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-031980
163363A03046
Xcvr 1
REV 01
740-031980
AJ40JS8
PIC 1
BUILTIN
BUILTIN
PIC 2
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-031980
153363A00593
Xcvr 1
REV 01
740-031980
AJ40JUJ
PIC 3
BUILTIN
BUILTIN
Xcvr 0
NON-JNPR
UQC0B53
FPC 2
REV 26
750-046005
CACN1891
CPU
REV 09
711-045719
CACN8694
PIC 0
BUILTIN
BUILTIN
Xcvr 0
NON-JNPR
URA012A
PIC 1
BUILTIN
BUILTIN
Xcvr 0
NON-JNPR
J13F47042
PIC 2
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-031980
AJC0BM3
Xcvr 1
REV 01
740-021308
11T511100917
PIC 3
BUILTIN
BUILTIN
Xcvr 0
NON-JNPR
UQK07SU
FPC 3
REV 03
750-045372
CAAD9425
CPU
REV 08
711-035209
CAAD9094
MIC 0
REV 14
750-033196
CAAW9204
PIC 0
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-046563
XD16FC034
MIC 1
REV 19
750-033199
CAAJ1814
PIC 2
BUILTIN
BUILTIN
FPC 4
REV 21.0.11 750-045715 CAAY3568
CPU
REV 07
711-045719
CAAW7430
1330
PS 1.4-2.52kW; 90-264V
PS 1.4-2.52kW; 90-264V
RE-S-1800x4
RE-S-1800x4
Enhanced MX SCB
Enhanced MX SCB
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC5E 3D Q 2CGE+4XGE
RMPC PMB
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-LR4-D
MPC5E 3D Q 2CGE+4XGE
RMPC PMB
2X10GE SFPP OTN
SFP+-10G-LR
1X100GE CFP2 OTN
CFP2-100G-LR4-D
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-LR4-D
MPCE Type 3 3D
HMPC PMB 2G
1X100GE CXP
1X100GE CXP
CFP2-100G-SR10
1X100GE CFP
1X100GE CFP
MPC5E 3D Q 24XGE+6XLGE
RMPC PMB
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
PIC 1
PIC 2
PIC 3
WAN MEZZ
FPC 5
CPU
MIC 0
PIC 0
Xcvr 0
MIC 1
PIC 2
Xcvr 0
Fan Tray
REV 01
REV 01
REV 01
REV
REV
REV
REV
12
11
08
19
REV 01
REV 07
REV 01
BUILTIN
740-031980
740-021308
740-031980
BUILTIN
BUILTIN
BUILTIN
750-049136
750-045372
711-035209
750-033199
BUILTIN
740-035329
750-033196
BUILTIN
740-046563
BUILTIN
AP406NG
AR41NLP
B11D05630
BUILTIN
BUILTIN
BUILTIN
CACM6678
CABK7539
CABJ2466
CAAJ9719
BUILTIN
UP1020P
YZ0797
BUILTIN
XC42FC022
show chassis hardware detail (MX480 Routers with MPC5E and built-in OTN PIC)
user@host> show chassis hardware detail
Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11C0338AFB
MX480
Midplane
REV 05
710-017414
ABAB8430
MX480 Midplane
FPM Board
REV 02
710-017254
ZS8005
Front Panel Display
PEM 0
Rev 05
740-029970
QCS1024U089
PS 1.4-2.52kW; 90-264V
AC in
PEM 1
Rev 10
740-029970
QCS1314U0FJ
PS 1.4-2.52kW; 90-264V
AC in
PEM 2
Rev 07
740-029970
QCS1121U076
PS 1.4-2.52kW; 90-264V
AC in
Routing Engine 0 REV 05
740-031116
9009092471
RE-S-1800x4
ad0
3896 MB VRFCF14096DIHK1
VM4096MB 6862
Compact Flash
ad1
30533 MB UGB94ARF32H0S3-KC
UNIGEN-478612-001127 Disk 1
usb0 (addr 1) EHCI root hub 0
Intel
uhub0
usb0 (addr 2) product 0x0020 32
vendor 0x8087
uhub1
DIMM 0
SGU04G72H1BB2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 1
SGU04G72H1BB2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 2
SGU04G72H1BB2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 3
SGU04G72H1BB2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
Routing Engine 1 REV 05
740-031116
9009097958
RE-S-1800x4
ad0
3896 MB VRFCF14096DIHK1
VM4096MB 6145
Compact Flash
ad1
30533 MB UGB94ARF32H0S3-KC
UNIGEN-499551-000273 Disk 1
CB 0
REV 16
750-031391
CAAX0789
Enhanced MX SCB
CB 1
REV 16
750-031391
CAAX0856
Enhanced MX SCB
FPC 0
REV 32
750-028467
ABBP1782
MPC 3D 16x 10GE
CPU
REV 10
711-029089
ABBP5410
AMPC PMB
PIC 0
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
Xcvr 0
REV 01
740-021308
983152A00038
SFP+-10G-SR
Xcvr 1
REV 01
740-031980
B11F00211
SFP+-10G-SR
Xcvr 2
REV 01
740-031980
AQ72LPB
SFP+-10G-SR
Xcvr 3
REV 01
740-031980
AHN0WR5
SFP+-10G-SR
PIC 1
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
Xcvr 0
REV 01
740-031980
B11J03627
SFP+-10G-SR
Xcvr 1
REV 01
740-031980
B11F00300
SFP+-10G-SR
Xcvr 2
REV 01
740-021308
AQ42WSS
SFP+-10G-SR
Xcvr 3
REV 01
740-021308
AQ43HGC
SFP+-10G-SR
PIC 2
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
Xcvr 0
REV 01
740-021308
ANA0ND0
SFP+-10G-SR
Xcvr 1
REV 01
740-021308
ANA0NGF
SFP+-10G-SR
1331
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
FPC 1
CPU
PIC 0
Xcvr 0
Xcvr 1
PIC 1
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
FPC 2
CPU
PIC 0
Xcvr 0
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
FPC 3
CPU
MIC 0
PIC 0
Xcvr 0
MIC 1
PIC 2
FPC 4
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
PIC 1
PIC 2
PIC 3
WAN MEZZ
FPC 5
CPU
MIC 0
PIC 0
Xcvr 0
MIC 1
PIC 2
Xcvr 0
Fan Tray
REV 01
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
740-021308
ANA0NG9
740-021308
ANA0MP9
BUILTIN
BUILTIN
01
740-021308
AQA06CG
01
740-021308
19T511100493
01
740-031980
APR040J
26
750-046005
CACN1894
09
711-045719
CACN8698
BUILTIN
BUILTIN
01
740-031980
163363A03046
01
740-031980
AJ40JS8
BUILTIN
BUILTIN
BUILTIN
BUILTIN
01
740-031980
153363A00593
01
740-031980
AJ40JUJ
BUILTIN
BUILTIN
NON-JNPR
UQC0B53
26
750-046005
CACN1891
09
711-045719
CACN8694
BUILTIN
BUILTIN
NON-JNPR
URA012A
BUILTIN
BUILTIN
NON-JNPR
J13F47042
BUILTIN
BUILTIN
01
740-031980
AJC0BM3
01
740-021308
11T511100917
BUILTIN
BUILTIN
NON-JNPR
UQK07SU
03
750-045372
CAAD9425
08
711-035209
CAAD9094
14
750-033196
CAAW9204
BUILTIN
BUILTIN
01
740-046563
XD16FC034
19
750-033199
CAAJ1814
BUILTIN
BUILTIN
21.0.11 750-045715 CAAY3568
07
711-045719
CAAW7430
BUILTIN
BUILTIN
01
740-031980
AP406NG
01
740-021308
AR41NLP
01
740-031980
B11D05630
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
12
750-049136
CACM6678
11
750-045372
CABK7539
08
711-035209
CABJ2466
19
750-033199
CAAJ9719
BUILTIN
BUILTIN
01
740-035329
UP1020P
07
750-033196
YZ0797
BUILTIN
BUILTIN
01
740-046563
XC42FC022
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC5E 3D Q 2CGE+4XGE
RMPC PMB
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-LR4-D
MPC5E 3D Q 2CGE+4XGE
RMPC PMB
2X10GE SFPP OTN
SFP+-10G-LR
1X100GE CFP2 OTN
CFP2-100G-LR4-D
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-LR4-D
MPCE Type 3 3D
HMPC PMB 2G
1X100GE CXP
1X100GE CXP
CFP2-100G-SR10
1X100GE CFP
1X100GE CFP
MPC5E 3D Q 24XGE+6XLGE
RMPC PMB
12X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
12X10GE SFPP OTN
3X40GE QSFPP
3X40GE QSFPP
MPC5E 24XGE OTN Mezz
MPCE Type 3 3D
HMPC PMB 2G
1X100GE CFP
1X100GE CFP
CFP-100G-SR10
1X100GE CXP
1X100GE CXP
CFP2-100G-SR10
Enhanced Left Fan Tray
show chassis hardware extensive (MX480 Routers with MPC5E and built-in OTN PIC)
user@host> show chassis hardware extensive
Hardware inventory:
Item
Version Part number Serial number
1332
Description
Chassis
Jedec Code:
0x7fb0
JN11C0338AFB
EEPROM Version:
S/N:
Assembly Version:
Assembly Flags:
MX480
0x02
JN11C0338AFB
00.00
0x02
00 00 00 00
00
00
02
00
00
00
00
00
00
00
00
00
00
00
00
00
00 00
00 00
00 00
00 00
00 00
00 00
00 00
00 00
MX480 Midplane
0x01
ABAB8430
01.05
0x00
CHAS-BP-MX480-S
ff ff ff ff
30
31
00
98
00
2d
ff
ff
35
34
0d
00
00
53
ff
ff
00 00
00 00
0c 07
ff ff
00 43
00 00
ff ff
ff ff
Front Panel Display
0x01
ZS8005
01.02
0x00
CRAFT-MX480-S
ff ff ff ff
30
35
00
ff
00
00
ff
ff
32 00 00
34 00 00
15 0b 07
ff ff ff
00 00 43
00 00 00
ff ff ff
ff ff ff
PS 1.4-2.52kW; 90-264V
0x01
QCS1024U089
01.05
0x00
PWR-MX480-2520-AC-S
1333
1334
00 00 00 00
30
37
00
ff
00
30
00
00
35 00 00
30 00 00
11 06 07
ff ff ff
00 00 50
2d 41 43
00 00 00
00 00 00
PS 1.4-2.52kW; 90-264V
0x01
QCS1314U0FJ
01.10
0x00
PWR-MX480-2520-AC-S
00 00 00 00
31
37
00
ff
00
30
00
00
30 00 00
30 00 00
04 04 07
ff ff ff
00 00 50
2d 41 43
00 00 00
00 00 00
PS 1.4-2.52kW; 90-264V
0x01
QCS1121U076
01.07
0x00
PWR-MX480-2520-AC-S
00 00 00 00
30
37
00
ff
00
30
00
00
37
30
17
ff
00
2d
00
00
00 00
00 00
05 07
ff ff
00 50
41 43
00 00
00 00
RE-S-1800x4
0x02
9009092471
01.05
0x00
COUCALDBAA
RE-S-1800X4-16G-S
23 23 23 00
30 35 00 00
31 36 00 00
Address 0x20: 39 30 30 39 30 39 32 34 37 31 00 00 00 01 0b 07
Address 0x30: db ff ff ff 54 32 30 32 37 43 41 2d 34 32 46 42
Address 0x40: 23 23 23 00 01 43 4f 55 43 41 4c 44 42 41 41 52
Address 0x50: 45 2d 53 2d 31 38 30 30 58 34 2d 31 36 47 2d 53
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 4b ff ff ff ff ff ff ff ff ff ff ff ff
ad0
3896 MB VRFCF14096DIHK1
VM4096MB 6862
Compact Flash
ad1
30533 MB UGB94ARF32H0S3-KC
UNIGEN-478612-001127 Disk 1
usb0 (addr 1) EHCI root hub 0
Intel
uhub0
usb0 (addr 2) product 0x0020 32
vendor 0x8087
uhub1
DIMM 0
SGU04G72H1BB2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 1
SGU04G72H1BB2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 2
SGU04G72H1BB2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 3
SGU04G72H1BB2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
Routing Engine 1 REV 05
740-031116
9009097958
RE-S-1800x4
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-031116
S/N:
9009097958
Assembly ID: 0x09c0
Assembly Version: 01.05
Date:
02-06-2012
Assembly Flags:
0x00
Version:
REV 05
CLEI Code:
COUCALDBAA
ID: RE-S-1800x4
FRU Model Number: RE-S-1800X4-16G-S
Board Information Record:
Address 0x00: 54 32 30 32 37 43 41 2d 34 32 46 42 23 23 23 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 c0 01 05 52 45 56 20 30 35 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 33 31 31 31 36 00 00
Address 0x20: 39 30 30 39 30 39 37 39 35 38 00 00 00 06 02 07
Address 0x30: dc ff ff ff 54 32 30 32 37 43 41 2d 34 32 46 42
Address 0x40: 23 23 23 00 01 43 4f 55 43 41 4c 44 42 41 41 52
Address 0x50: 45 2d 53 2d 31 38 30 30 58 34 2d 31 36 47 2d 53
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 4b ff ff ff ff ff ff ff ff ff ff ff ff
ad0
3896 MB VRFCF14096DIHK1
VM4096MB 6145
Compact Flash
ad1
30533 MB UGB94ARF32H0S3-KC
UNIGEN-499551-000273 Disk 1
...
Serial number
AA6082
000008
Description
MX960
MX960 Midplane
Power Inlet Module
000038
1000617944
JK6947
JM7617
PS 1.7kW; 200-240VAC in
RE-S-1300
MX960 Test SCB
MX960 Test DPC
BUILTIN
BUILTIN
JL9634
1x 10GE(LAN/WAN)
10x 1GE
MX960 Test DPC
BUILTIN
MYBG65I82C
BUILTIN
P7N0368
P8J1W27
P8J1VSD
1x 10GE(LAN/WAN)
XFP-10G-SR
10x 1GE
SFP-SX
SFP-SX
SFP-SX
1335
Xcvr 9
Fan Tray 0
Fan Tray 1
REV 01
740-011782
P8J1W25
SFP-SX
Description
MX960
MX960 Backplane
Front Panel Display
Power Distribution Module
PS 1.7kW; 200-240VAC in
PS 1.7kW; 200-240VAC in
PS 1.7kW; 200-240VAC in
RE-S-2000
MX SCB
MX SCB
DPCE 40x 1GE R
DPCE 40x 1GE R
DPC PMB
10x 1GE(LAN)
SFP-1000BASE-BX40-D
SFP-1000BASE-BX40-D
SFP-1000BASE-BX10-U
SFP-1000BASE-BX40-U
SFP-1000BASE-BX40-U
10x 1GE(LAN)
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
10x 1GE(LAN)
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-D
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
SFP-1000BASE-BX10-U
10x 1GE(LAN)
SFP-EX
SFP-EX
SFP-EX
SFP-1000BASE-BX10-U
Fan Tray
1336
Serial number
JN1096805AFA
Description
MX960
Midplane
REV 03
710-013698
TR0183
MX960 Backplane
Fan Extender
REV 02
710-018051
JY5227
Extended Cable Manager
FPM Board
REV 03
710-014974
JZ6876
Front Panel Display
PDM
Rev 03
740-013110
QCS11035023
Power Distribution Module
PEM 1
Rev 03
740-013682
QCS1109400L
PS 1.7kW; 200-240VAC in
PEM 2
Rev 03
740-013682
QCS11094015
PS 1.7kW; 200-240VAC in
PEM 3
Rev 03
740-013682
QCS11094012
PS 1.7kW; 200-240VAC in
Routing Engine 0 REV 06
740-013063
1000687969
RE-S-2000
Routing Engine 1 REV 06
740-013063
1000687955
RE-S-2000
CB 0
REV 11
750-031391
YZ6072
Enhanced MX SCB
CB 1
REV 11
750-031391
YZ6068
Enhanced MX SCB
CB 2
REV 11
750-031391
YZ6081
Enhanced MX SCB
FPC 0
REV 01
750-018122
KA5576
DPCE 40x 1GE R
CPU
REV 06
710-013713
KB3961
DPC PMB
PIC 0
BUILTIN
BUILTIN
10x 1GE(LAN)
Xcvr 0
REV 01
740-011613
P9F18GF
SFP-SX
Xcvr 2
REV 01
740-011782
P9M0TL9
SFP-SX
Xcvr 7
REV 01
740-011782
P9P0XXH
SFP-SX
Xcvr 9
REV 01
740-011782
P9M0TN1
SFP-SX
PIC 1
BUILTIN
BUILTIN
10x 1GE(LAN)
Xcvr 0
REV 01
740-011613
PAJ4UHC
SFP-SX
PIC 2
BUILTIN
BUILTIN
10x 1GE(LAN)
Xcvr 0
REV 01
740-011613
PFF2CD0
SFP-SX
Xcvr 1
REV 01
740-011613
PBG3ZUT
SFP-SX
Xcvr 2
REV 01
740-011613
PFF2DDV
SFP-SX
Xcvr 5
REV 01
740-011613
P8E2SST
SFP-SX
Xcvr 9
REV 01
740-011782
PB8329N
SFP-SX
PIC 3
BUILTIN
BUILTIN
10x 1GE(LAN)
Xcvr 0
REV 01
740-026192
1U0201084503342
SFP-100BASE-BX10-U
Xcvr 1
REV 01
740-026193
1U1201084503313
SFP-100BASE-BX10-D
Xcvr 2
REV 01
740-011613
PAJ4Y5B
SFP-SX
Xcvr 6
REV 01
740-011782
P9M0U3M
SFP-SX
Xcvr 7
REV 01
740-011782
P9M0TLA
SFP-SX
FPC 1
REV 16
750-031089
YL0719
MPC Type 2 3D
CPU
REV 06
711-030884
YL1463
MPC PMB 2G
MIC 0
REV 07
750-028387
JR6500
3D 4x 10GE XFP
PIC 0
BUILTIN
BUILTIN
2x 10GE XFP
Xcvr 0
REV 01
740-014279
733019A00154
XFP-10G-LR
Xcvr 1
REV 02
740-014289
T09F55034
XFP-10G-SR
PIC 1
BUILTIN
BUILTIN
2x 10GE XFP
Xcvr 0
REV 01
740-014279
913019B00791
XFP-10G-LR
Xcvr 1
REV 01
740-014289
98S803A90384
XFP-10G-SR
MIC 1
REV 24
750-028387
YJ3950
3D 4x 10GE XFP
PIC 2
BUILTIN
BUILTIN
2x 10GE XFP
Xcvr 0
REV 02
740-014279
T10B36134
XFP-10G-LR
Xcvr 1
REV 01
740-014289
T07M86354
XFP-10G-SR
PIC 3
BUILTIN
BUILTIN
2x 10GE XFP
FPC 2
REV 08
710-014219
JY9654
DPCE 4x 10GE R
CPU
REV 06
710-013713
JZ6549
DPC PMB
PIC 0
BUILTIN
BUILTIN
1x 10GE(LAN/WAN)
PIC 1
BUILTIN
BUILTIN
1x 10GE(LAN/WAN)
PIC 2
BUILTIN
BUILTIN
1x 10GE(LAN/WAN)
Xcvr 0
REV 03
740-011571
C931BK028
XFP-10G-SR
PIC 3
BUILTIN
BUILTIN
1x 10GE(LAN/WAN)
FPC 3
REV 10
750-024199
XJ6692
MX FPC Type 3
CPU
REV 03
710-022351
XF5182
DPC PMB
PIC 0
REV 17
750-009553
RJ2945
4x OC-48 SONET
Xcvr 1
REV 01
740-011785
PCP3YLL
SFP-SR
Xcvr 3
REV 01
740-011785
PDS0MRY
SFP-SR
PIC 1
REV 32
750-003700
DP2113
1x OC-192 12xMM VSR
FPC 5
REV 25
750-028467
YM8256
MPC 3D 16x 10GE
1337
CPU
PIC 0
Xcvr 1
PIC 1
PIC 2
PIC 3
FPC 7
CPU
MIC 0
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
QXM 0
FPC 8
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
PIC 1
Xcvr 0
Xcvr 3
FPC 10
CPU
PIC 0
Xcvr 5
Xcvr 6
PIC 1
PIC 2
Xcvr 0
Xcvr 5
Xcvr 6
Xcvr 8
PIC 3
Fan Tray 0
Fan Tray 1
REV 10
REV 01
REV 02
REV 01
REV 08
0
2
4
7
8
REV 01
0
1
9
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
04
05
03
08
01
REV
REV
REV
REV
REV
REV
01
08
01
01
04
05
REV 01
REV 01
REV 01
REV 01
REV 01
REV
REV
REV
REV
01
01
01
01
REV 03
REV 03
711-029089
BUILTIN
740-031980
BUILTIN
BUILTIN
BUILTIN
750-031092
711-030884
750-028392
BUILTIN
740-011782
NON-JNPR
740-011613
740-011613
740-011613
BUILTIN
740-011782
740-011613
740-011613
711-028408
750-024387
710-022351
750-014730
740-016065
NON-JNPR
740-011618
750-014637
740-011785
740-011785
710-013699
710-013713
BUILTIN
740-011782
740-011782
BUILTIN
BUILTIN
740-011782
740-011782
740-011782
740-011782
BUILTIN
740-014971
740-014971
YL3029
BUILTIN
AHN0X1Z
BUILTIN
BUILTIN
BUILTIN
JR6658
JZ9038
JZ8737
BUILTIN
PBE2C6Y
U8105N8
PFM18EF
PFF2AM8
PFF2CT6
BUILTIN
PB82VHH
PFF2CSW
PFF2BY0
JR6372
JW9754
KF1651
DM3664
81S290N00077
2191844
PD81EE5
DM3671
PCK3UNK
PDS0MPZ
JY4654
JS9717
BUILTIN
PAR1L72
P8N1YQ4
BUILTIN
BUILTIN
P8Q2AVL
PAR1L7B
PAR1L2J
P8N1YMY
BUILTIN
TP0567
TP0702
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
MPC Type 1 3D Q
MPC PMB 2G
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
MPC QXM
MX FPC Type 2
DPC PMB
4x OC-3 1x OC-12 SFP
SFP-SR
SFP-SR
SFP-IR
4x OC-12-3 SFP
SFP-SR
SFP-SR
DPCE 40x 1GE R
DPC PMB
10x 1GE(LAN)
SFP-SX
SFP-SX
10x 1GE(LAN)
10x 1GE(LAN)
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN)
Fan Tray
Fan Tray
1338
Serial number
TR0183
JY5227
JZ6876
1000687969
1000687955
YZ6072
YZ6068
YZ6081
KA5576
YL0719
JR6500
YJ3950
FPC 2
FPC 3
PIC 0
PIC 1
FPC 5
FPC 7
MIC 0
FPC 8
PIC 0
PIC 1
FPC 10
Fan Tray 0
Fan Tray 1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
08
10
17
32
25
02
08
05
08
08
04
03
03
710-014219
750-024199
750-009553
750-003700
750-028467
750-031092
750-028392
750-024387
750-014730
750-014637
710-013699
740-014971
740-014971
JY9654
XJ6692
RJ2945
DP2113
YM8256
JR6658
JZ8737
JW9754
DM3664
DM3671
JY4654
TP0567
TP0702
DPC-R-4XGE-XFP
MX-FPC3
PC-4OC48-SON-SFP
PC-1OC192-SON-VSR
MPC-3D-16XGE-SFPP
MX-MPC1-3D-Q
MIC-3D-20GE-SFP
MX-FPC2
PB-4OC3-1OC12-SON2-SFP
PB-4OC3-4OC12-SON-SFP
DPC-R-40GE-SFP
FFANTRAY-MX960-S
FFANTRAY-MX960-S
Description
MX960
MX960 Backplane
Front Panel Display
Power Distribution Module
PS 4.1kW; 200-240V AC
PS 4.1kW; 200-240V AC
PS 4.1kW; 200-240V AC
RE-S-1800x4
RE-S-1800x4
Enhanced MX SCB
Enhanced MX SCB
Enhanced MX SCB
MPC5E 3D Q 2CGE+4XGE
RMPC PMB
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-SR10
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-LR4
MPCE Type 3 3D
HMPC PMB 2G
10X10GE SFPP
10X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CXP
1X100GE CXP
1339
Xcvr 0
FPC 3
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 4
CPU
PIC 0
Xcvr 0
Xcvr 1
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
FPC 5
CPU
PIC 0
Xcvr 0
Xcvr 1
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
FPC 7
CPU
PIC 0
Xcvr 0
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
FPC 8
1340
REV 01
REV 35
REV 11
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
740-046563
XD16FC064
750-028467
CAAT9156
711-029089
CAAV4645
BUILTIN
BUILTIN
01
740-021308
AQ43HZ1
01
740-021308
AQ43HZC
01
740-021308
AQ43HD2
01
740-021308
AQ502HN
BUILTIN
BUILTIN
01
740-021308
AQ43HGF
01
740-021308
AQ501RZ
01
740-021308
AQ5029V
01
740-021308
AQ501X9
BUILTIN
BUILTIN
01
740-021308
AQ502ZN
740-021308
AQ43H86
01
740-021308
AQ502ZY
01
740-021308
AQ502PZ
BUILTIN
BUILTIN
01
740-021308
AQ503E6
01
740-021308
AQ502XN
01
740-031980
B11F00213
01
740-021308
AQ50336
18
750-046005
CACE6568
09
711-045719
CACG8900
BUILTIN
BUILTIN
01
740-021308
AQA095A
01
740-021308
AQG0M1E
BUILTIN
BUILTIN
NON-JNPR
FE13F000F
BUILTIN
BUILTIN
01
740-021308
AQG0LYC
01
740-021308
AQG0LYB
BUILTIN
BUILTIN
01
740-048813
XD32FE00Z
18
750-046005
CACE6577
09
711-045719
CACG8902
BUILTIN
BUILTIN
01
740-021308
AQG0MXE
01
740-021308
AQG0LVY
BUILTIN
BUILTIN
01
740-046563
XD16FC03T
BUILTIN
BUILTIN
01
740-021308
AQG0LW1
01
740-021308
AQG0LW3
BUILTIN
BUILTIN
NON-JNPR
FE13F000J
09
750-037355
CAAF0937
08
711-035209
CAAD8004
BUILTIN
BUILTIN
01
740-021308
ANA0MM3
BUILTIN
BUILTIN
01
740-035329
X000C163
BUILTIN
BUILTIN
01
740-021308
AQG0MS6
01
740-021308
AQG0MRX
01
740-021308
AQG0M6Y
01
740-021308
AQG0LZM
BUILTIN
BUILTIN
01
740-035329
X12J00499
39
750-045715
CACD1903
CFP-100G-SR10
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC5E 3D Q 2CGE+4XGE
RMPC PMB
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-SR10
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-SR10
MPC5E 3D Q 2CGE+4XGE
RMPC PMB
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-SR10
2X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
CFP2-100G-SR10
MPC4E 3D 2CGE+8XGE
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
MPC5E 3D Q 24XGE+6XLGE
CPU
PIC 0
PIC 1
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
WAN MEZZ
FPC 9
CPU
MIC 0
PIC 0
Xcvr 0
Xcvr 1
PIC 1
Xcvr 0
QXM 0
QXM 1
FPC 10
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 9
Xcvr 10
Xcvr 11
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 9
Xcvr 10
Xcvr 11
PIC 2
PIC 3
WAN MEZZ
FPC 11
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
REV 09
REV
REV
REV
REV
REV
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
711-045719
CACD1815
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
01
740-046565
QC480289
01
740-046565
QC480274
01
740-046565
QD130190
BUILTIN
BUILTIN
01
740-046565
QD130197
01
740-046565
QD130180
740-046565
QD130199
09
750-049136
CABN0415
05
750-044444
CAAY9801
04
711-038484
CAAW3673
28
750-028387
CAAX1071
BUILTIN
BUILTIN
NON-JNPR
T12L92342
NON-JNPR
T12L92303
BUILTIN
BUILTIN
NON-JNPR
CC07BK02X
06
711-028408
CAAW4883
06
711-028408
CAAW4603
21.0.11 750-045715 CAAY3541
07
711-045719
CAAW7426
BUILTIN
BUILTIN
01
740-031980
AHK01AP
01
740-021308
AQ502ZU
01
740-031980
AP41BLS
01
740-021308
AQA08YA
01
740-021308
AQA0K26
01
740-021308
AQA06S3
01
740-021308
AQA06AS
01
740-021308
AQA053N
01
740-021308
AQA0E97
01
740-021308
AQA0GS4
01
740-021308
AQA0JVA
BUILTIN
BUILTIN
01
740-021308
AQA057A
01
740-021308
ANA0MLS
01
740-021308
AQA093A
01
740-021309
943153A00075
01
740-021308
AQA077B
01
740-021308
AQA0JSC
01
740-021308
AQA0735
01
740-021308
AQ5028N
01
740-031980
AP40VN5
01
740-021308
AQA0K0J
01
740-021308
AQA07AP
01
740-021308
AQA08YB
BUILTIN
BUILTIN
BUILTIN
BUILTIN
07
750-045717
CAAX3123
17
750-037355
CAAT3986
08
711-035209
CAAR3972
BUILTIN
BUILTIN
01
740-021308
AQA0DSE
01
740-021308
AQ501Y3
01
740-021308
AQ501XU
01
740-021308
AQ5036Y
BUILTIN
BUILTIN
NON-JNPR
X12J00247
RMPC PMB
12X10GE SFPP OTN
12X10GE SFPP OTN
3X40GE QSFPP
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
3X40GE QSFPP
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
MPC5E 24XGE OTN Mezz
MPCE Type 2 3D P
MPCE PMB 2G
3D 4x 10GE XFP
2x 10GE XFP
XFP-10G-SR
XFP-10G-SR
2x 10GE XFP
XFP-10G-SR
MPC QXM
MPC QXM
MPC5E 3D Q 24XGE+6XLGE
RMPC PMB
12X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
12X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
3X40GE QSFPP
3X40GE QSFPP
MPC5E 24XGE Mezz
MPC4E 3D 2CGE+8XGE
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
1341
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Fan Tray
Fan Tray
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
0
1
REV 01
REV 08
REV 08
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-035329
740-031521
740-031521
BUILTIN
ALQ1DKF
AJ403YA
AP40TY0
ALQ14G0
BUILTIN
X12J00095
ACAF4219
ACAF4225
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
Enhanced Fan Tray
Enhanced Fan Tray
Serial number
AA6082
000008
Description
MX960
MX960 Midplane
Power Inlet Module
000038
1000617944
111419E1805T1141
NR0WT5925N77
JK6947
JM7617
PS 1.7kW; 200-240VAC in
RE-S-1300
Compact Flash
Hard Disk
MX960 Test SCB
MX960 Test DPC
BUILTIN
BUILTIN
JL9634
1x 10GE(LAN/WAN)
10x 1GE
MX960 Test DPC
BUILTIN
MYBG65I82C
BUILTIN
P7N0368
P8J1W27
P8J1VSD
P8J1W25
1x 10GE(LAN/WAN)
XFP-10G-SR
10x 1GE
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1342
DIMM 1
DIMM 2
DIMM 3
Routing Engine 1
ad0
3831 MB
ad1
30533 MB
CB 0
CB 1
CB 2
FPC 0
CPU
PIC 0
Xcvr 0
Xcvr 1
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
FPC 1
CPU
MIC 0
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
MIC 1
PIC 2
Xcvr 0
FPC 3
CPU
PIC 0
Xcvr 0
Xcvr 1
REV
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 4
CPU
1343
PIC 0
Xcvr 0
Xcvr 1
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
FPC 5
CPU
PIC 0
Xcvr 0
Xcvr 1
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 0
FPC 7
CPU
PIC 0
Xcvr 0
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
FPC 8
CPU
PIC 0
PIC 1
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
WAN MEZZ
FPC 9
CPU
MIC 0
PIC 0
Xcvr 0
Xcvr 1
PIC 1
Xcvr 0
QXM 0
QXM 1
FPC 10
CPU
PIC 0
1344
BUILTIN
BUILTIN
740-021308
AQA095A
740-021308
AQG0M1E
BUILTIN
BUILTIN
NON-JNPR
FE13F000F
BUILTIN
BUILTIN
01
740-021308
AQG0LYC
01
740-021308
AQG0LYB
BUILTIN
BUILTIN
01
740-048813
XD32FE00Z
18
750-046005
CACE6577
09
711-045719
CACG8902
BUILTIN
BUILTIN
01
740-021308
AQG0MXE
01
740-021308
AQG0LVY
BUILTIN
BUILTIN
01
740-046563
XD16FC03T
BUILTIN
BUILTIN
01
740-021308
AQG0LW1
01
740-021308
AQG0LW3
BUILTIN
BUILTIN
NON-JNPR
FE13F000J
09
750-037355
CAAF0937
08
711-035209
CAAD8004
BUILTIN
BUILTIN
01
740-021308
ANA0MM3
BUILTIN
BUILTIN
01
740-035329
X000C163
BUILTIN
BUILTIN
01
740-021308
AQG0MS6
01
740-021308
AQG0MRX
01
740-021308
AQG0M6Y
01
740-021308
AQG0LZM
BUILTIN
BUILTIN
01
740-035329
X12J00499
39
750-045715
CACD1903
09
711-045719
CACD1815
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
BUILTIN
01
740-046565
QC480289
01
740-046565
QC480274
01
740-046565
QD130190
BUILTIN
BUILTIN
01
740-046565
QD130197
01
740-046565
QD130180
01
740-046565
QD130199
09
750-049136
CABN0415
05
750-044444
CAAY9801
04
711-038484
CAAW3673
28
750-028387
CAAX1071
BUILTIN
BUILTIN
NON-JNPR
T12L92342
NON-JNPR
T12L92303
BUILTIN
BUILTIN
NON-JNPR
CC07BK02X
06
711-028408
CAAW4883
06
711-028408
CAAW4603
21.0.11 750-045715 CAAY3541
07
711-045719
CAAW7426
BUILTIN
BUILTIN
REV 01
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 9
Xcvr 10
Xcvr 11
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 9
Xcvr 10
Xcvr 11
PIC 2
PIC 3
WAN MEZZ
FPC 11
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Fan Tray 0
Fan Tray 1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV 01
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
740-031980
AHK01AP
740-021308
AQ502ZU
740-031980
AP41BLS
740-021308
AQA08YA
740-021308
AQA0K26
740-021308
AQA06S3
740-021308
AQA06AS
740-021308
AQA053N
740-021308
AQA0E97
740-021308
AQA0GS4
740-021308
AQA0JVA
BUILTIN
BUILTIN
01
740-021308
AQA057A
01
740-021308
ANA0MLS
01
740-021308
AQA093A
01
740-021309
943153A00075
01
740-021308
AQA077B
01
740-021308
AQA0JSC
01
740-021308
AQA0735
01
740-021308
AQ5028N
01
740-031980
AP40VN5
01
740-021308
AQA0K0J
01
740-021308
AQA07AP
01
740-021308
AQA08YB
BUILTIN
BUILTIN
BUILTIN
BUILTIN
07
750-045717
CAAX3123
17
750-037355
CAAT3986
08
711-035209
CAAR3972
BUILTIN
BUILTIN
01
740-021308
AQA0DSE
01
740-021308
AQ501Y3
01
740-021308
AQ501XU
740-021308
AQ5036Y
BUILTIN
BUILTIN
NON-JNPR
X12J00247
BUILTIN
BUILTIN
01
740-031980
ALQ1DKF
01
740-031980
AJ403YA
01
740-031980
AP40TY0
01
740-031980
ALQ14G0
BUILTIN
BUILTIN
01
740-035329
X12J00095
08
740-031521
ACAF4219
08
740-031521
ACAF4225
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
12X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
3X40GE QSFPP
3X40GE QSFPP
MPC5E 24XGE Mezz
MPC4E 3D 2CGE+8XGE
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
Enhanced Fan Tray
Enhanced Fan Tray
1345
Address 0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x20: 4a 4e 31 32 31 34 38 35 32 41 46 41 00 00 00 00
Address 0x30: 00 00 00 ff 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Midplane
REV 01
710-030012
ACAX3674
MX960 Backplane
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
710-030012
S/N:
ACAX3674
Assembly ID: 0x01df
Assembly Version: 01.01
Date:
01-19-2013
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
COM8T00CRB
ID: MX960 Backplane
FRU Model Number: CHAS-BP-MX960-S
Board Information Record:
Address 0x00: ad 01 08 00 54 e0 32 bc 68 00 ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 01 df 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 31 30 2d 30 33 30 30 31 32 00 00
Address 0x20: 53 2f 4e 20 41 43 41 58 33 36 37 34 00 13 01 07
Address 0x30: dd ff ff ff ad 01 08 00 54 e0 32 bc 68 00 ff ff
Address 0x40: ff ff ff ff 01 43 4f 4d 38 54 30 30 43 52 42 43
Address 0x50: 48 41 53 2d 42 50 2d 4d 58 39 36 30 2d 53 00 00
Address 0x60: 00 00 00 00 00 00 42 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff aa ff ff ff ff ff ff ff ff ff ff ff ff
FPM Board
REV 03
710-014974
CAAZ9326
Front Panel Display
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
710-014974
S/N:
CAAZ9326
Assembly ID: 0x01e6
Assembly Version: 01.03
Date:
12-31-2012
Assembly Flags:
0x00
Version:
REV 03
ID: Front Panel Display
FRU Model Number: CRAFT-MX960-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 01 e6 01 03 52 45 56 20 30 33 00 00
Address 0x10: 00 00 00 00 37 31 30 2d 30 31 34 39 37 34 00 00
Address 0x20: 53 2f 4e 20 43 41 41 5a 39 33 32 36 00 1f 0c 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 00 00 00 00 00 00 00 00 00 00 43
Address 0x50: 52 41 46 54 2d 4d 58 39 36 30 2d 53 00 00 00 00
Address 0x60: 00 00 00 00 00 00 ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
PDM
Rev 03
740-013110
QCS17025017
Power Distribution Module
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
740-013110
S/N:
QCS17025017
Assembly ID: 0x0416
Assembly Version: 01.03
Date:
01-10-2013
Assembly Flags:
0x00
Version:
Rev 03
ID: Power Distribution Module
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff 00 00 00
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 16 01 03 52 65 76 20 30 33 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 31 33 31 31 30 00 00
Address 0x20: 51 43 53 31 37 30 32 35 30 31 37 00 00 0a 01 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1346
PEM 0
Rev 10
740-027760
QCS1702N062
PS 4.1kW; 200-240V AC
in
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
740-027760
S/N:
QCS1702N062
Assembly ID: 0x0430
Assembly Version: 01.10
Date:
01-15-2013
Assembly Flags:
0x00
Version:
Rev 10
ID: PS 4.1kW; 200-240V AC in
FRU Model Number: PWR-MX960-4100-AC-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff 00 00 00 00
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 30 01 0a 52 65 76 20 31 30 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 32 37 37 36 30 00 00
Address 0x20: 51 43 53 31 37 30 32 4e 30 36 32 00 00 0f 01 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 50
Address 0x50: 57 52 2d 4d 58 39 36 30 2d 34 31 30 30 2d 41 43
Address 0x60: 2d 53 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PEM 1
Rev 04
740-027760
QCS1422N02C
PS 4.1kW; 200-240V AC
in
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
740-027760
S/N:
QCS1422N02C
Assembly ID: 0x0430
Assembly Version: 01.04
Date:
06-04-2010
Assembly Flags:
0x00
Version:
Rev 04
ID: PS 4.1kW; 200-240V AC in
FRU Model Number: PWR-MX960-4100-AC-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff 00 00 00 00
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 30 01 04 52 65 76 20 30 34 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 32 37 37 36 30 00 00
Address 0x20: 51 43 53 31 34 32 32 4e 30 32 43 00 00 04 06 07
Address 0x30: da ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 50
Address 0x50: 57 52 2d 4d 58 39 36 30 2d 34 31 30 30 2d 41 43
Address 0x60: 2d 53 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
PEM 2
Rev 09
740-027760
QCS1614N01X
PS 4.1kW; 200-240V AC
in
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
740-027760
S/N:
QCS1614N01X
Assembly ID: 0x0430
Assembly Version: 01.09
Date:
04-07-2012
Assembly Flags:
0x00
Version:
Rev 09
ID: PS 4.1kW; 200-240V AC in
FRU Model Number: PWR-MX960-4100-AC-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff 00 00 00 00
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 30 01 09 52 65 76 20 30 39 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 32 37 37 36 30 00 00
Address 0x20: 51 43 53 31 36 31 34 4e 30 31 58 00 00 07 04 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: 00 00 00 00 01 00 00 00 00 00 00 00 00 00 00 50
Address 0x50: 57 52 2d 4d 58 39 36 30 2d 34 31 30 30 2d 41 43
Address 0x60: 2d 53 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Routing Engine 0 REV 08
740-031116
9009131803
RE-S-1800x4
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-031116
S/N:
9009131803
Assembly ID: 0x09c0
Assembly Version: 01.08
1347
Date:
03-04-2013
Assembly Flags:
0x00
Version:
REV 08
CLEI Code:
COUCASKBAA
ID: RE-S-1800x4
FRU Model Number: RE-S-1800X4-16G-S
Board Information Record:
Address 0x00: 54 32 30 32 37 44 42 2d 34 34 47 42 23 42 23 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 c0 01 08 52 45 56 20 30 38 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 33 31 31 31 36 00 00
Address 0x20: 39 30 30 39 31 33 31 38 30 33 00 00 00 04 03 07
Address 0x30: dd ff ff ff 54 32 30 32 37 44 42 2d 34 34 47 42
Address 0x40: 23 42 23 00 01 43 4f 55 43 41 53 4b 42 41 41 52
Address 0x50: 45 2d 53 2d 31 38 30 30 58 34 2d 31 36 47 2d 53
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 59 ff ff ff ff ff ff ff ff ff ff ff ff
ad0
3831 MB UGB30SFA4000T1
SFA4000T1 000016CD Compact Flash
ad1
30533 MB UGB94BPH32H0S1-KCI
11000061346
Disk 1
usb0 (addr 1) EHCI root hub 0
Intel
uhub0
usb0 (addr 2) product 0x0020 32
vendor 0x8087
uhub1
DIMM 0
VL31B5263F-F8SD DIE REV-0 PCB REV-0
MFR ID-ce80
DIMM 1
VL31B5263F-F8SD DIE REV-0 PCB REV-0
MFR ID-ce80
DIMM 2
VL31B5263F-F8SD DIE REV-0 PCB REV-0
MFR ID-ce80
DIMM 3
VL31B5263F-F8SD DIE REV-0 PCB REV-0
MFR ID-ce80
Routing Engine 1 REV 08
740-031116
9009124913
RE-S-1800x4
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-031116
S/N:
9009124913
Assembly ID: 0x09c0
Assembly Version: 01.08
Date:
01-09-2013
Assembly Flags:
0x00
Version:
REV 08
CLEI Code:
COUCASKBAA
ID: RE-S-1800x4
FRU Model Number: RE-S-1800X4-16G-S
Board Information Record:
Address 0x00: 54 32 30 32 37 44 42 2d 34 34 47 42 23 42 23 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 c0 01 08 52 45 56 20 30 38 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 33 31 31 31 36 00 00
Address 0x20: 39 30 30 39 31 32 34 39 31 33 00 00 00 09 01 07
Address 0x30: dd ff ff ff 54 32 30 32 37 44 42 2d 34 34 47 42
Address 0x40: 23 42 23 00 01 43 4f 55 43 41 53 4b 42 41 41 52
Address 0x50: 45 2d 53 2d 31 38 30 30 58 34 2d 31 36 47 2d 53
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 59 ff ff ff ff ff ff ff ff ff ff ff ff
ad0
3831 MB UGB30SFA4000T1
SFA4000T1 0000106D Compact Flash
ad1
30533 MB UGB94BPH32H0S1-KCI
11000052402
Disk 1
CB 0
REV 18
750-031391
CABF0579
Enhanced MX SCB
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-031391
S/N:
CABF0579
Assembly ID: 0x09b0
Assembly Version: 01.18
Date:
04-15-2013
Assembly Flags:
0x00
Version:
REV 18
CLEI Code:
COUCASRBAA
ID: Enhanced MX SCB
FRU Model Number: SCBE-MX-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 b0 01 12 52 45 56 20 31 38 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 31 33 39 31 00 00
Address 0x20: 53 2f 4e 20 43 41 42 46 30 35 37 39 00 0f 04 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 43 4f 55 43 41 53 52 42 41 41 53
Address 0x50: 43 42 45 2d 4d 58 2d 53 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 43 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 7d ff ff ff ff ff ff ff ff ff ff ff ff
CB 1
REV 16
750-031391
CAAZ2471
Enhanced MX SCB
1348
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-031391
S/N:
CAAZ2471
Assembly ID: 0x09b0
Assembly Version: 01.16
Date:
03-09-2013
Assembly Flags:
0x00
Version:
REV 16
CLEI Code:
COUCARCBAB
ID: Enhanced MX SCB
FRU Model Number: SCBE-MX-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 b0 01 10 52 45 56 20 31 36 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 31 33 39 31 00 00
Address 0x20: 53 2f 4e 20 43 41 41 5a 32 34 37 31 00 09 03 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 43 4f 55 43 41 52 43 42 41 42 53
Address 0x50: 43 42 45 2d 4d 58 2d 53 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 42 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 6d ff ff ff ff ff ff ff ff ff ff ff ff
CB 2
REV 16
750-031391
CAAW9595
Enhanced MX SCB
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-031391
S/N:
CAAW9595
Assembly ID: 0x09b0
Assembly Version: 01.16
Date:
02-01-2013
Assembly Flags:
0x00
Version:
REV 16
CLEI Code:
COUCARCBAB
ID: Enhanced MX SCB
FRU Model Number: SCBE-MX-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 b0 01 10 52 45 56 20 31 36 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 31 33 39 31 00 00
Address 0x20: 53 2f 4e 20 43 41 41 57 39 35 39 35 00 01 02 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 43 4f 55 43 41 52 43 42 41 42 53
Address 0x50: 43 42 45 2d 4d 58 2d 53 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 42 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 6d ff ff ff ff ff ff ff ff ff ff ff ff
FPC 0
REV 18
750-046005
CACE6574
MPC5E 3D Q 2CGE+4XGE
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-046005
S/N:
CACE6574
Assembly ID: 0x0b8c
Assembly Version: 01.18
Date:
11-20-2013
Assembly Flags:
0x00
Version:
REV 18
CLEI Code:
PROTOXCLEI
ID: MPC5E 3D Q 2CGE+4XGE
FRU Model Number: PROTO-ASSEMBLY
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 8c 01 12 52 45 56 20 31 38 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 36 30 30 35 00 00
Address 0x20: 53 2f 4e 20 43 41 43 45 36 35 37 34 00 14 0b 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43 4c 45 49 50
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c 59 00 00 00
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff c2 ff ff ff ff ff ff ff ff ff ff ff ff
CPU
REV 09
711-045719
CACG8908
RMPC PMB
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
711-045719
S/N:
CACG8908
Assembly ID: 0x0b85
Assembly Version: 01.09
Date:
11-13-2013
Assembly Flags:
0x00
Version:
REV 09
ID: RMPC PMB
Board Information Record:
1349
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 85 01 09 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 34 35 37
Address 0x20: 53 2f 4e 20 43 41 43 47 38 39 30 38
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 50 52 4f 54 4f 58 43
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff
Address 0x70: ff ff ff c2 00 00 00 00 00 00 00 00
PIC 0
BUILTIN
BUILTIN
Jedec Code:
0x0000
EEPROM Version:
P/N:
BUILTIN
S/N:
Assembly ID: 0x0a90
Assembly Version:
Date:
00-00-0000
Assembly Flags:
ID: 2X10GE SFPP OTN
Board Information Record:
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 00 00 00 00 0a 90 00 00 00 00 00 00
Address 0x10: 00 00 00 00 42 55 49 4c 54 49 4e 00
Address 0x20: 42 55 49 4c 54 49 4e 00 25 73 3a 20
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 c0 02 ae dc 00 00 00 00
Xcvr 0
REV 01
740-021308
AQA0DYT
Xcvr 1
REV 01
740-021308
AQG0MS7
PIC 1
BUILTIN
BUILTIN
Jedec Code:
0x0000
EEPROM Version:
P/N:
BUILTIN
S/N:
Assembly ID: 0x0a6e
Assembly Version:
Date:
00-00-0000
Assembly Flags:
ID: 1X100GE CFP2 OTN
Board Information Record:
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 00 00 00 00 0a 6e 00 00 00 00 00 00
Address 0x10: 00 00 00 00 42 55 49 4c 54 49 4e 00
Address 0x20: 42 55 49 4c 54 49 4e 00 25 73 3a 20
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 c0 03 f3 8c 31 5c e7 80
Xcvr 0
REV 01
740-046563
XD16FC03Z
PIC 2
BUILTIN
BUILTIN
Jedec Code:
0x0000
EEPROM Version:
P/N:
BUILTIN
S/N:
Assembly ID: 0x0a90
Assembly Version:
Date:
00-00-0000
Assembly Flags:
ID: 2X10GE SFPP OTN
Board Information Record:
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 00 00 00 00 0a 90 00 00 00 00 00 00
Address 0x10: 00 00 00 00 42 55 49 4c 54 49 4e 00
Address 0x20: 42 55 49 4c 54 49 4e 00 25 73 3a 20
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00
1350
ff ff ff ff
30
31
00
ff
4c
59
ff
00
39
39
0d
ff
45
00
ff
00
00 00
00 00
0b 07
ff ff
49 50
00 00
ff ff
00 00
2X10GE SFPP OTN
0x00
BUILTIN
00.00
0x00
00 00 00 00
00
25
00
00
00
00
00
0a
00 00 00
73 3a 20
00 00 00
00 00 00
00 00 00
00 00 00
00 00 00
6e 00 00
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
0x00
BUILTIN
00.00
0x00
00 00 00 00
00
25
00
00
00
00
00
00
00
73
00
00
00
00
00
00
00 00
3a 20
00 00
00 00
00 00
00 00
00 00
00 02
CFP2-100G-SR10
2X10GE SFPP OTN
0x00
BUILTIN
00.00
0x00
00 00 00 00
00
25
00
00
00
00
73
00
00
00
00
3a
00
00
00
00
20
00
00
00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 c0 03 f5 6c 31 5c db 40
Xcvr 0
REV 01
740-021308
ANA0NAJ
Xcvr 1
REV 01
740-021308
AQG0MRQ
PIC 3
BUILTIN
BUILTIN
Jedec Code:
0x0000
EEPROM Version:
P/N:
BUILTIN
S/N:
Assembly ID: 0x0a6e
Assembly Version:
Date:
00-00-0000
Assembly Flags:
ID: 1X100GE CFP2 OTN
Board Information Record:
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 00 00 00 00 0a 6e 00 00 00 00 00 00
Address 0x10: 00 00 00 00 42 55 49 4c 54 49 4e 00
Address 0x20: 42 55 49 4c 54 49 4e 00 25 73 3a 20
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 c0 03 ed ec 31 5c e2 e8
Xcvr 0
REV 01
740-049775
J13K72993
FPC 1
REV 11
750-045372
CABK8154
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-045372
S/N:
Assembly ID: 0x09db
Assembly Version:
Date:
05-18-2013
Assembly Flags:
Version:
REV 11
CLEI Code:
ID: MPCE Type 3 3D
FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 db 04 0b 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 35 33
Address 0x20: 53 2f 4e 20 43 41 42 4b 38 31 35 34
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 43 4f 55 49 42 42 4e
Address 0x50: 58 2d 4d 50 43 33 45 2d 33 44 00 00
Address 0x60: 00 00 00 00 00 00 44 00 00 ff ff ff
Address 0x70: ff ff ff cf ff ff ff ff ff ff ff ff
CPU
REV 08
711-035209
CABE7370
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-035209
S/N:
Assembly ID: 0x0b04
Assembly Version:
Date:
05-08-2013
Assembly Flags:
Version:
REV 08
ID: HMPC PMB 2G
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 0b 04 01 08 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 35 32
Address 0x20: 53 2f 4e 20 43 41 42 45 37 33 37 30
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff 00 00 00 00 00 00 00 00
MIC 0
REV 07
750-033307
CABD5255
Jedec Code:
0x7fb0
EEPROM Version:
00 00 00 00
00 00 00 00
00 00 00 02
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP2 OTN
0x00
BUILTIN
00.00
0x00
00 00 00 00
00
25
00
00
00
00
00
00
00 00 00
73 3a 20
00 00 00
00 00 00
00 00 00
00 00 00
00 00 00
00 00 02
CFP2-100G-LR4
MPCE Type 3 3D
0x02
CABK8154
04.11
0x00
COUIBBNBAA
MX-MPC3E-3D
ff ff ff ff
31
37
00
ff
42
00
ff
ff
31
32
12
ff
41
00
ff
ff
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
ff ff
HMPC PMB 2G
0x01
CABE7370
01.08
0x00
ff ff ff ff
30
30
00
ff
ff
ff
ff
00
38
39
08
ff
ff
ff
ff
00
00 00
00 00
05 07
ff ff
ff ff
ff ff
ff ff
00 00
10X10GE SFPP
0x02
1351
P/N:
750-033307
S/N:
CABD5255
Assembly ID: 0x0a2a
Assembly Version: 02.07
Date:
04-25-2013
Assembly Flags:
0x00
Version:
REV 07
CLEI Code:
COUIBBJBAA
ID: 10X10GE SFPP
FRU Model Number: MIC3-3D-10XGE-SFPP
Board Information Record:
Address 0x00: 34 01 03 03 05 ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 fe 0a 2a 02 07 52 45 56 20 30 37 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 33 33 30 37 00 00
Address 0x20: 53 2f 4e 20 43 41 42 44 35 32 35 35 00 19 04 07
Address 0x30: dd ff ff ff 34 01 03 03 05 ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 43 4f 55 49 42 42 4a 42 41 41 4d
Address 0x50: 49 43 33 2d 33 44 2d 31 30 58 47 45 2d 53 46 50
Address 0x60: 50 00 00 00 00 00 41 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 82 c0 03 f0 bc 57 79 83 80 00 00 00 02
PIC 0
BUILTIN
BUILTIN
10X10GE SFPP
Xcvr 0
REV 01
740-021308
AQ50319
SFP+-10G-SR
Xcvr 1
REV 01
740-021308
AQ5035V
SFP+-10G-SR
Xcvr 2
REV 01
740-021308
AQ502XJ
SFP+-10G-SR
Xcvr 3
REV 01
740-021308
AQ43HHR
SFP+-10G-SR
Xcvr 4
REV 01
740-021308
AQ502YA
SFP+-10G-SR
Xcvr 5
REV 01
740-021308
AQ502EU
SFP+-10G-SR
Xcvr 6
REV 01
740-021308
AQ502HR
SFP+-10G-SR
Xcvr 7
REV 01
740-021308
AQ502A6
SFP+-10G-SR
Xcvr 8
REV 01
740-021308
AQ43H8M
SFP+-10G-SR
MIC 1
REV 14
750-033196
CAAP1398
1X100GE CXP
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-033196
S/N:
CAAP1398
Assembly ID: 0x0a29
Assembly Version: 03.14
Date:
10-27-2012
Assembly Flags:
0x00
Version:
REV 14
CLEI Code:
COUIBBKBAA
ID: 1X100GE CXP
FRU Model Number: MIC3-3D-1X100GE-CXP
Board Information Record:
Address 0x00: 34 01 07 07 08 ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 fe 0a 29 03 0e 52 45 56 20 31 34 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 33 31 39 36 00 00
Address 0x20: 53 2f 4e 20 43 41 41 50 31 33 39 38 00 1b 0a 07
Address 0x30: dc ff ff ff 34 01 07 07 08 ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 43 4f 55 49 42 42 4b 42 41 41 4d
Address 0x50: 49 43 33 2d 33 44 2d 31 58 31 30 30 47 45 2d 43
Address 0x60: 58 50 00 00 00 00 41 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 96 c0 03 ef cc 57 79 85 08 00 00 00 02
PIC 2
BUILTIN
BUILTIN
1X100GE CXP
Xcvr 0
REV 01
740-046563
XD16FC064
CFP2-100G-SR10
FPC 3
REV 35
750-028467
CAAT9156
MPC 3D 16x 10GE
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
750-028467
S/N:
CAAT9156
Assembly ID: 0x0997
Assembly Version: 01.35
Date:
12-17-2012
Assembly Flags:
0x00
Version:
REV 35
ID: MPC 3D 16x 10GE
FRU Model Number: MPC-3D-16XGE-SFPP
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 09 97 01 23 52 45 56 20 33 35 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 32 38 34 36 37 00 00
Address 0x20: 53 2f 4e 20 43 41 41 54 39 31 35 36 00 11 0c 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 00 00 00 00 00 00 00 00 00 00 4d
1352
Address 0x50: 50 43 2d 33 44 2d 31 36 58 47 45 2d
Address 0x60: 00 00 00 00 00 00 ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff
CPU
REV 11
711-029089
CAAV4645
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-029089
S/N:
Assembly ID: 0x0998
Assembly Version:
Date:
12-13-2012
Assembly Flags:
Version:
REV 11
ID: AMPC PMB
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 09 98 01 0b 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 32 39 30
Address 0x20: 53 2f 4e 20 43 41 41 56 34 36 34 35
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff 00 00 00 00 00 00 00 00
PIC 0
BUILTIN
BUILTIN
Jedec Code:
0x0000
EEPROM Version:
P/N:
BUILTIN
S/N:
Assembly ID: 0x02fe
Assembly Version:
Date:
00-00-0000
Assembly Flags:
ID: 4x 10GE(LAN) SFP+
Board Information Record:
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 00 00 00 00 02 fe 00 00 00 00 00 00
Address 0x10: 00 00 00 00 42 55 49 4c 54 49 4e 00
Address 0x20: 42 55 49 4c 54 49 4e 00 25 73 3a 20
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 c0 02 6b 94 00 00 00 00
Xcvr 0
REV 01
740-021308
AQ43HZ1
Xcvr 1
REV 01
740-021308
AQ43HZC
Xcvr 2
REV 01
740-021308
AQ43HD2
Xcvr 3
REV 01
740-021308
AQ502HN
PIC 1
BUILTIN
BUILTIN
Jedec Code:
0x0000
EEPROM Version:
P/N:
BUILTIN
S/N:
Assembly ID: 0x02fe
Assembly Version:
Date:
00-00-0000
Assembly Flags:
ID: 4x 10GE(LAN) SFP+
Board Information Record:
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 00 00 00 00 02 fe 00 00 00 00 00 00
Address 0x10: 00 00 00 00 42 55 49 4c 54 49 4e 00
Address 0x20: 42 55 49 4c 54 49 4e 00 25 73 3a 20
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 c0 02 ac 0c 00 00 00 00
Xcvr 0
REV 01
740-021308
AQ43HGF
Xcvr 1
REV 01
740-021308
AQ501RZ
53 46 50 50
ff ff ff ff
ff ff ff ff
AMPC PMB
0x01
CAAV4645
01.11
0x00
ff ff ff ff
31
38
00
ff
ff
ff
ff
00
31
39
0d
ff
ff
ff
ff
00
00 00
00 00
0c 07
ff ff
ff ff
ff ff
ff ff
00 00
4x 10GE(LAN) SFP+
0x00
BUILTIN
00.00
0x00
00 00 00 00
00
25
00
00
00
00
00
02
00
73
00
00
00
00
00
fe
00 00
3a 20
00 00
00 00
00 00
00 00
00 00
00 00
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
0x00
BUILTIN
00.00
0x00
00 00 00 00
00
25
00
00
00
00
00
02
00
73
00
00
00
00
00
fe
00 00
3a 20
00 00
00 00
00 00
00 00
00 00
00 00
SFP+-10G-SR
SFP+-10G-SR
1353
Xcvr 2
Xcvr 3
PIC 2
Jedec Code:
P/N:
Assembly ID:
Date:
......
REV 01
REV 01
740-021308
AQ5029V
740-021308
AQ501X9
BUILTIN
BUILTIN
0x0000
EEPROM Version:
BUILTIN
S/N:
0x02fe
Assembly Version:
00-00-0000
Assembly Flags:
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
0x00
BUILTIN
00.00
0x00
1354
FPC 5
FPC 7
FPC 8
FPC 9
MIC 0
FPC 10
FPC 11
Fan Tray 0
Fan Tray 1
REV
REV
REV
REV
REV
REV
REV
REV
REV
18
750-046005
PROTOXCLEI
09
750-037355
PROTOXCLEI
39
750-045715
PROTOXCLEI
05
750-044444
COUIBBGBAA
28
750-028387
COUIA16BAA
21.0.11 750-045715 PROTOXCLEI
17
750-037355
IPU3A4DHAA
08
740-031521
08
740-031521
PROTO-ASSEMBLY
MPC4E-2CGE-8XGE
PROTO-ASSEMBLY
MX-MPC2E-3D-P
MIC-3D-4XGE-XFP
PROTO-ASSEMBLY
MPC4E-3D-2CGE-8XGE
FFANTRAY-MX960-HC-S
FFANTRAY-MX960-HC-S
Serial number
JN11E3217AFK
ABAB8506
ZY8296
ACAJ1388
ZX8744
VK00254
Description
MX2010
Lower Backplane
Upper Backplane
Power Midplane
Front Panel Display
DC 52V Power Supply
VG00015
VH00097
VJ00151
VJ00149
WA00008
WA00014
9009094134
9009094141
CAAB3491
CAAB3489
CAAA6135
CAAA6137
ZV1828
ZZ2568
ZZ2563
ZZ2564
ZZ2580
ZZ2579
CAAB4882
CAAB4898
CAAB1919
CAAB7174
BUILTIN
AMH02RE
AMH038C
AMH0390
AMG0SUA
BUILTIN
AMH0579
AMG0SGP
AMH04SV
AMH04X3
BUILTIN
AMH0135
AMH02NC
1355
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 1
CPU
MIC 0
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
FPC 8
CPU
MIC 0
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
Xcvr
PIC 3
FPC 9
CPU
1356
REV 01
REV 01
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
21
04
03
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
03
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
22
06
26
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
02
02
02
02
01
01
01
01
0
1
2
3
4
5
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
26
0
1
REV 11
REV 10
740-021308
740-021308
BUILTIN
740-021308
740-021308
740-021308
740-021308
750-033205
711-035209
750-033307
BUILTIN
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021308
740-021308
750-033307
BUILTIN
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021308
740-021308
750-031089
711-030884
750-028392
BUILTIN
740-031851
740-031851
740-011613
740-011613
740-011613
740-011613
740-031851
740-031851
740-031851
740-031851
BUILTIN
740-031851
740-031851
740-031851
740-031851
740-031851
740-031851
750-028387
BUILTIN
NON-JNPR
NON-JNPR
BUILTIN
750-036284
711-029089
AMH02XB
AMH02PN
BUILTIN
AMH057Y
AMG0JHE
AMH02HT
AMH04V4
ZG5027
YT4780
ZV6299
BUILTIN
083363A00410
083363A00334
113363A00125
083363A00953
AHR013D
AJ40JUR
AJ40JKL
AJ30ECK
19T511100864
19T511100868
ZV6268
BUILTIN
AJC0JML
AJ403PC
AJ10N25
AJ40JF4
AJ40JSJ
AJ403V7
AJ40JN3
AJ40JSU
19T511100468
19T511101363
ZT9746
ZS1271
ABBS1150
BUILTIN
PLG023C
PLG09C6
AM0950SF9L7
AM1001SFN1H
AM1001SFM9D
AM1001SFLTJ
AC1108S03L9
AC1102S00NC
AC1102S00MX
AC1102S0085
BUILTIN
AC1102S00KU
AC1102S00NG
AC1102S00K3
AC1102S008R
AM1107SUFVJ
AC1108S03LG
ABBR9582
BUILTIN
T10A91703
T09L42604
BUILTIN
ZL3591
ZL0513
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC Type 3
HMPC PMB 2G
10X10GE SFPP
10X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
10X10GE SFPP
10X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC Type 2 3D
MPC PMB 2G
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
3D 4x 10GE XFP
2x 10GE XFP
XFP-10G-SR
XFP-10G-SR
2x 10GE XFP
MPC 3D 16x 10GE EM
AMPC PMB
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
ADC 0
ADC 1
ADC 8
ADC 9
Fan Tray
Fan Tray
Fan Tray
Fan Tray
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
05
01
01
02
2A
2A
2A
2A
0
1
2
3
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
BUILTIN
1YT517101825
1YT517101821
1YT517101682
ALQ13R6
BUILTIN
1YT517101828
1YT517101716
1YT517101732
ALP0TR1
BUILTIN
1YT517101741
1YT517101829
1YT517101669
ALQ14E3
BUILTIN
1YT517101826
1YT517101817
1YT517101735
ALQ159A
CAAC2073
ZV4117
ZV4107
ZW1555
ACAY0015
ACAY0019
ACAY0020
ACAY0021
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Adapter Card
Adapter Card
Adapter Card
Adapter Card
172mm FanTray - 6
172mm FanTray - 6
172mm FanTray - 6
172mm FanTray - 6
Serial number
JN11E233DAFK
ABAB9357
ABAB8643
ACAJ1677
ABBV9726
1E02224000P
Description
MX2010
Lower Backplane
Upper Backplane
Power Midplane
Front Panel Display
DC 52V Power Supply
1E02224000M
1E022240010
1E02224000G
1E022240013
1E022240007
1E02224001C
1E02224001D
1E02224001B
Fans
Fans
Fans
Fans
1E262250067
DC Power Dist Module
9009099704
RE-S-1800x4
SFA4000T1 00000651 Compact Flash
11000019592
Disk 1
1357
usb0 (addr 1)
usb0 (addr 2)
DIMM 0
DIMM 1
DIMM 2
DIMM 3
Routing Engine 1
ad0
3998 MB
ad1
30533 MB
CB 0
CB 1
SPMB 0
SPMB 1
SFB 0
SFB 1
SFB 2
SFB 3
SFB 4
SFB 5
SFB 6
SFB 7
FPC 0
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
FPC 1
CPU
MIC 0
PIC 0
Xcvr 0
MIC 1
PIC 2
Xcvr 0
FPC 2
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
1358
Flash
Board
Board
Board
Board
Board
Board
Board
Board
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
FPC 3
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 4
CPU
MIC 0
PIC 0
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
Xcvr
FPC 5
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
0
1
REV
REV
REV
0
1
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
740-031980
AMA0629
740-021308
973152A00053
740-031980
193363A00344
740-021308
973152A00046
BUILTIN
BUILTIN
01
740-031980
AMA062M
01
740-021308
973152A00080
01
740-031980
193363A00580
01
740-021308
973152A00064
01
740-031980
093363A01494
01
740-021308
973152A00020
01
740-031980
123363A00047
01
740-021308
973152A00072
BUILTIN
BUILTIN
01
740-021308
03DZ06A01033
01
740-021308
973152A00022
01
740-021308
03DZ06A01026
01
740-021308
973152A00013
01
740-021308
03DZ06A01028
01
740-021308
973152A00079
01
740-021308
03DZ06A01018
01
740-021308
973152A00025
33
750-028467
CAAF5400
11
711-029089
CAAH7626
BUILTIN
BUILTIN
01
740-021308
973152A00066
01
740-021308
973152A00021
01
740-021308
973152A00062
01
740-021308
973152A00027
BUILTIN
BUILTIN
01
740-021308
973152A00065
740-021308
973152A00069
01
740-021308
973152A00026
01
740-021308
973152A00003
BUILTIN
BUILTIN
01
740-021308
973152A00035
01
740-021308
973152A00004
01
740-021308
973152A00049
01
740-021308
973152A00055
BUILTIN
BUILTIN
01
740-021308
973152A00010
01
740-021308
973152A00001
01
740-021308
973152A00073
01
740-021308
973152A00012
21
750-033205
ZG5028
05
711-035209
YX3911
03
750-036233
ZL2036
BUILTIN
BUILTIN
01
740-032986
QB220708
01
740-032986
QB220735
03
750-036233
ZL2028
BUILTIN
BUILTIN
01
740-032986
QB220727
01
740-032986
QB220715
11
750-037358
CAAE2196
08
711-035209
CAAD9074
BUILTIN
BUILTIN
01
740-031980
AMA062S
01
740-031980
AMA062P
01
740-031980
AMA052R
01
740-031980
AMA0632
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC Type 3
HMPC PMB 2G
2X40GE QSFP
2X40GE QSFP
QSFP+-40G-SR4
QSFP+-40G-SR4
2X40GE QSFP
2X40GE QSFP
QSFP+-40G-SR4
QSFP+-40G-SR4
MPC Type 4-1
HMPC PMB 2G
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1359
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 7
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
1360
4
5
6
7
REV
REV
REV
REV
0
1
2
3
4
5
6
7
REV
REV
REV
REV
REV
REV
REV
REV
0
1
2
3
4
5
6
7
REV
REV
REV
REV
REV
REV
REV
REV
0
1
2
REV
REV
REV
REV 01
REV
REV
REV
REV
REV
REV
4
5
6
7
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
4
REV
REV
REV
REV
REV
01
01
01
01
740-031980
193363A00564
740-031980
193363A00229
740-031980
193363A00363
740-031980
193363A00278
BUILTIN
BUILTIN
01
740-031980
AMA04CC
01
740-021308
AD0927A001W
01
740-031980
AMA04N2
01
740-031980
AMA062U
01
740-031980
193363A00491
01
740-031980
183363A01511
01
740-031980
193363A00565
01
740-031980
193363A00405
BUILTIN
BUILTIN
01
740-031980
AMA07QX
01
740-031980
AMA06MS
01
740-031980
193363A00318
01
740-031980
193363A00402
01
740-031980
193363A00174
01
740-031980
193363A00388
01
740-031980
193363A00377
01
740-031980
193363A00234
BUILTIN
BUILTIN
01
740-031980
AMA062T
01
740-031980
193363A00550
01
740-031980
193363A00364
740-031980
AMA0630
01
740-031980
193363A00509
01
740-031980
193363A00459
01
740-031980
113363A00191
01
740-031980
193363A00352
33
750-028467
CAAF5552
11
711-029089
CAAH7601
BUILTIN
BUILTIN
01
740-021308
AD0927A0036
01
740-021308
AD0927A003M
01
740-021308
AD0927A003G
01
740-021308
AD0927A0031
BUILTIN
BUILTIN
01
740-031980
193363A00331
01
740-031980
193363A00325
01
740-031980
193363A00417
01
740-031980
183363A02509
BUILTIN
BUILTIN
01
740-021308
T09K75140
01
740-031980
B11A04356
01
740-031980
B11K01952
01
740-031980
B11K01914
BUILTIN
BUILTIN
01
740-021308
T09K75157
01
740-021308
T09K75194
01
740-031980
B11K01926
01
740-031980
B11K01936
16
750-037358
CAAL1012
08
711-035209
CAAJ3851
BUILTIN
BUILTIN
01
740-031980
AMA04NK
01
740-031980
B11F00260
01
740-031980
B11E02192
01
740-031980
AMA04CP
01
740-031980
AJ40JKK
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC Type 4-1
HMPC PMB 2G
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Xcvr 5
Xcvr 6
Xcvr 7
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
FPC 8
CPU
MIC 0
PIC 0
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
Xcvr
FPC 9
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
ADC 0
ADC 1
ADC 2
ADC 3
ADC 4
ADC 5
ADC 6
REV 01
REV 01
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
03
08
03
0
1
REV 01
REV 01
REV 03
0
1
REV
REV
REV
REV
01
01
09
08
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
REV
REV
REV
13
13
13
13
13
13
13
740-031980
B11F00238
740-031980
B10M00275
740-031980
193363A00211
BUILTIN
BUILTIN
740-031980
B11D05577
740-031980
B11G00586
740-031980
AMA08B7
740-031980
AMA04Q0
740-031980
B11D05840
740-031980
B11E00467
740-031980
B11E00029
740-021308
19T511101712
BUILTIN
BUILTIN
740-031980
193363A00568
740-031980
B10M00166
740-031980
B10M00212
740-031980
B11D05823
740-021308
03DZ06A01005
740-021308
03DZ06A01003
740-021308
03DZ06A01009
740-021308
03DZ06A01004
BUILTIN
BUILTIN
740-021308
03DZ06A01017
740-021308
03DZ06A01016
740-021308
03DZ06A01024
740-021308
03DZ06A01008
740-030658
AD0946A02UH
740-021308
T09J67913
740-021308
AD0837ES09G
740-021308
03DZ06A01015
750-045372
CAAD3111
711-035209
CAAD8033
750-036233
ZL2032
BUILTIN
BUILTIN
740-032986
QB230273
740-032986
QB230254
750-036233
ZL2021
BUILTIN
BUILTIN
740-032986
QB390962
740-032986
QB390960
750-037355
CAAF1531
711-035209
CAAB9927
BUILTIN
BUILTIN
740-031980
193363A00525
740-031980
193363A00504
740-031980
193363A00368
740-031980
AJ40JSS
BUILTIN
BUILTIN
BUILTIN
BUILTIN
740-031980
123363A00042
740-031980
B10M00023
740-031980
AJ802EM
740-031980
B11E02348
BUILTIN
BUILTIN
750-043596
ABBX5532
750-043596
ABBX5550
750-043596
ABBX5571
750-043596
ABBX5568
750-043596
ABBX5556
750-043596
ABBX5553
750-043596
ABBX5541
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
8X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-USR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC Type 3
HMPC PMB 2G
2X40GE QSFP
2X40GE QSFP
QSFP+-40G-SR4
QSFP+-40G-SR4
2X40GE QSFP
2X40GE QSFP
QSFP+-40G-SR4
QSFP+-40G-SR4
MPC Type 4-2
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
1361
ADC
ADC
ADC
Fan
Fan
Fan
Fan
7
8
9
Tray
Tray
Tray
Tray
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
13
13
07
03
2A
2A
2A
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
ABBX5578
ABBX5560
ABBV7188
ACAY0127
ACAY0068
ACAY0072
ACAY0070
Adapter Card
Adapter Card
Adapter Card
172mm FanTray
172mm FanTray
172mm FanTray
172mm FanTray
6
6
6
6
Fans
Fans
Fans
Fans
1362
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
PMP
REV 04
711-032426
ACAJ1677
Power Midplane
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
711-032426
S/N:
ACAJ1677
Assembly ID: 0x045d
Assembly Version: 01.04
Date:
07-20-2012
Assembly Flags:
0x00
Version:
REV 04
ID: Power Midplane
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 5d 01 04 52 45 56 20 30 34 00 00
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 32 34 32 36 00 00
Address 0x20: 53 2f 4e 20 41 43 41 4a 31 36 37 37 00 14 07 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
FPM Board
REV 08
760-044634
ABBV9726
Front Panel Display
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
760-044634
S/N:
ABBV9726
Assembly ID: 0x0b64
Assembly Version: 01.08
Date:
09-10-2012
Assembly Flags:
0x00
Version:
REV 08
CLEI Code:
IPMYA4EJRA
ID: Front Panel Display
FRU Model Number: MX2010-CRAFT-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 64 01 08 52 45 56 20 30 38 00 00
Address 0x10: 00 00 00 00 37 36 30 2d 30 34 34 36 33 34 00 00
Address 0x20: 53 2f 4e 20 41 42 42 56 39 37 32 36 00 0a 09 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 4d 59 41 34 45 4a 52 41 4d
Address 0x50: 58 32 30 31 30 2d 43 52 41 46 54 2d 53 00 00 00
Address 0x60: 00 00 00 00 00 00 41 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 93 ff ff ff ff ff ff ff ff ff ff ff ff
PSM 0
REV 01
740-045050
1E02224000P
DC 52V Power Supply
Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-045050
S/N:
1E02224000P
Assembly ID: 0x0478
Assembly Version: 01.01
Date:
12-06-2012
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
XXXXXXXXXX
ID: DC 52V Power Supply Module FRU Model Number: MX2000-PSM-HC-DC-S-A
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 30 35 30 00 00
Address 0x20: 31 45 30 32 32 32 34 30 30 30 50 00 00 06 0c 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 58 58 58 58 58 58 58 58 58 58 4d
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 48 43 2d 44 43 2d
Address 0x60: 53 2d 41 00 00 00 31 30 31 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 4a 00 00 00 00 00 00 00 00 00 00 00 00
PSM 1
REV 01
740-045050
1E02224000M
DC 52V Power Supply
1363
Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-045050
S/N:
1E02224000M
Assembly ID: 0x0478
Assembly Version: 01.01
Date:
12-06-2012
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
XXXXXXXXXX
ID: DC 52V Power Supply Module FRU Model Number: MX2000-PSM-HC-DC-S-A
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 30 35 30 00 00
Address 0x20: 31 45 30 32 32 32 34 30 30 30 4d 00 00 06 0c 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 58 58 58 58 58 58 58 58 58 58 4d
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 48 43 2d 44 43 2d
Address 0x60: 53 2d 41 00 00 00 31 30 31 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 4a 00 00 00 00 00 00 00 00 00 00 00 00
...
PDM 0
REV 01
740-045234
1E262250067
DC Power Dist Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-045234
S/N:
1E262250067
Assembly ID: 0x047b
Assembly Version: 01.01
Date:
06-28-2012
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
IPUPAJSKAA
ID: DC Power Dist Module
FRU Model Number: MX2000-PDM-DC-S-A
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 7b 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 32 33 34 00 00
Address 0x20: 31 45 32 36 32 32 35 30 30 36 37 00 00 1c 06 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4a 53 4b 41 41 4d
Address 0x50: 58 32 30 30 30 2d 50 44 4d 2d 44 43 2d 53 2d 41
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 89 00 00 00 00 00 00 00 00 00 00 00 00
Routing Engine 0 REV 02
740-041821
9009099704
RE-S-1800x4
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-041821
S/N:
9009099704
Assembly ID: 0x09c0
Assembly Version: 01.02
Date:
03-15-2012
Assembly Flags:
0x00
Version:
REV 02
ID: RE-S-1800x4
FRU Model Number: RE-S-1800X4-16G-S
Board Information Record:
Address 0x00: 54 32 30 32 37 44 41 2d 34 34 47 42 23 41 23 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 c0 01 02 52 45 56 20 30 32 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 31 38 32 31 00 00
Address 0x20: 39 30 30 39 30 39 39 37 30 34 00 00 00 0f 03 07
Address 0x30: dc ff ff ff 54 32 30 32 37 44 41 2d 34 34 47 42
Address 0x40: 23 41 23 00 01 00 00 00 00 00 00 00 00 00 00 52
Address 0x50: 45 2d 53 2d 31 38 30 30 58 34 2d 31 36 47 2d 53
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 8c ff ff ff ff ff ff ff ff ff ff ff ff
ad0
3831 MB UGB30SFA4000T1
SFA4000T1 00000651 Compact Flash
ad1
30533 MB UGB94BPH32H0S1-KCI
11000019592
Disk 1
usb0 (addr 1) EHCI root hub 0
Intel
uhub0
usb0 (addr 2) product 0x0020 32
vendor 0x8087
uhub1
DIMM 0
SGU04G72H1BD2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 1
SGU04G72H1BD2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
1364
DIMM 2
SGU04G72H1BD2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 3
SGU04G72H1BD2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
Routing Engine 1 REV 02
740-041821
9009099706
RE-S-1800x4
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-041821
S/N:
9009099706
Assembly ID: 0x09c0
Assembly Version: 01.02
Date:
02-23-2012
Assembly Flags:
0x00
Version:
REV 02
ID: RE-S-1800x4
FRU Model Number: RE-S-1800X4-16G-S
Board Information Record:
Address 0x00: 54 32 30 32 37 44 41 2d 34 34 47 42 23 41 23 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 09 c0 01 02 52 45 56 20 30 32 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 31 38 32 31 00 00
Address 0x20: 39 30 30 39 30 39 39 37 30 36 00 00 00 17 02 07
Address 0x30: dc ff ff ff 54 32 30 32 37 44 41 2d 34 34 47 42
Address 0x40: 23 41 23 00 01 00 00 00 00 00 00 00 00 00 00 52
Address 0x50: 45 2d 53 2d 31 38 30 30 58 34 2d 31 36 47 2d 53
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 8c ff ff ff ff ff ff ff ff ff ff ff ff
ad0
3998 MB Virtium - TuffDrive VCF P1T0200262860208 114 Compact Flash
ad1
30533 MB UGB94ARF32H0S3-KC
UNIGEN-499551-000404 Disk 1
CB 0
REV 13
750-040257
CAAF8436
Control Board
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-040257
S/N:
CAAF8436
Assembly ID: 0x0b26
Assembly Version: 01.13
Date:
08-29-2012
Assembly Flags:
0x00
Version:
REV 13
CLEI Code:
PROTOXCLEI
ID: Control Board
FRU Model Number: PROTO-ASSEMBLY
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 26 01 0d 52 45 56 20 31 33 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 30 32 35 37 00 00
Address 0x20: 53 2f 4e 20 43 41 41 46 38 34 33 36 00 1d 08 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43 4c 45 49 50
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c 59 00 00 00
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff ff ff ff ff
Address 0x70: ff ff ff c2 ff ff ff ff ff ff ff ff ff ff ff ff
...
SPMB 0
REV 02
711-041855
ABBV3825
PMB Board
Jedec Code:
0x7fb0
EEPROM Version:
0x01
P/N:
711-041855
S/N:
ABBV3825
Assembly ID: 0x0b29
Assembly Version: 01.02
Date:
08-14-2012
Assembly Flags:
0x00
Version:
REV 02
ID: PMB Board
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 0b 29 01 02 52 45 56 20 30 32 00 00
Address 0x10: 00 00 00 00 37 31 31 2d 30 34 31 38 35 35 00 00
Address 0x20: 53 2f 4e 20 41 42 42 56 33 38 32 35 00 0e 08 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff 00 00 00 00 00 00 00 00 00 00 00 00
...
SFB 0
REV 05
711-044466
ABBX5682
Switch Fabric Board
1365
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-044466
S/N:
Assembly ID: 0x0b25
Assembly Version:
Date:
09-07-2012
Assembly Flags:
Version:
REV 05
CLEI Code:
ID: Switch Fabric Board
FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 25 01 05 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 34 34 34
Address 0x20: 53 2f 4e 20 41 42 42 58 35 36 38 32
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43
Address 0x50: 52 4f 54 4f 2d 41 53 53 45 4d 42 4c
Address 0x60: 00 00 00 00 00 00 41 30 30 ff ff ff
Address 0x70: ff ff ff c2 00 00 00 01 00 00 00 00
...
FPC 0
REV 09
750-037355
CAAF0924
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037355
S/N:
Assembly ID: 0x0b4e
Assembly Version:
Date:
05-21-2012
Assembly Flags:
Version:
REV 09
CLEI Code:
ID: MPC Type 4-2
FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 4e 01 09 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 33
Address 0x20: 53 2f 4e 20 43 41 41 46 30 39 32 34
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43
Address 0x50: 50 43 34 45 2d 32 43 47 45 2d 38 58
Address 0x60: 00 00 00 00 00 00 30 39 00 ff ff ff
Address 0x70: ff ff ff c6 ff ff ff ff ff ff ff ff
CPU
REV 08
711-035209
CAAB9842
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-035209
S/N:
Assembly ID: 0x0b04
Assembly Version:
Date:
05-17-2012
Assembly Flags:
Version:
REV 08
ID: HMPC PMB 2G
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 0b 04 01 08 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 35 32
Address 0x20: 53 2f 4e 20 43 41 41 42 39 38 34 32
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff 00 00 00 00 00 00 00 00
PIC 0
BUILTIN
BUILTIN
Jedec Code:
0x0000
EEPROM Version:
P/N:
BUILTIN
S/N:
Assembly ID: 0x0a53
Assembly Version:
Date:
00-00-0000
Assembly Flags:
ID: 4x10GE SFPP
Board Information Record:
1366
0x02
ABBX5682
01.05
0x00
PROTOXCLEI
PROTO-ASSEMBLY
ff ff ff ff
30
36
00
ff
4c
59
ff
00
35
36
07
ff
45
00
ff
00
00
00
09
ff
49
00
ff
48
00
00
07
ff
50
00
ff
00
39
35
15
ff
45
45
ff
ff
00 00
00 00
05 07
ff ff
49 4d
00 00
ff ff
ff ff
HMPC PMB 2G
0x01
CAAB9842
01.08
0x00
ff ff ff ff
30
30
00
ff
ff
ff
ff
00
38
39
11
ff
ff
ff
ff
00
00 00
00 00
05 07
ff ff
ff ff
ff ff
ff ff
00 00
4x10GE SFPP
0x00
BUILTIN
00.00
0x00
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 00 00 00 00 0a 53 00 00 00 00 00 00 00 00 00 00
Address 0x10: 00 00 00 00 42 55 49 4c 54 49 4e 00 4d 58 43 00
Address 0x20: 42 55 49 4c 54 49 4e 00 4d 58 43 00 00 00 00 00
Address 0x30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 c0 02 ae 64 00 00 00 00 0a 52 00 00
Xcvr 0
REV 01
740-021308
19T511101656
SFP+-10G-SR
Xcvr 1
REV 01
740-031980
AMA04RU
SFP+-10G-SR
Xcvr 2
REV 01
740-031980
193363A00558
SFP+-10G-SR
Xcvr 3
REV 01
740-031980
B10M00202
SFP+-10G-SR
...
ADC 0
REV 13
750-043596
ABBX5532
Adapter Card
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
750-043596
S/N:
ABBX5532
Assembly ID: 0x0b3d
Assembly Version: 01.13
Date:
09-12-2012
Assembly Flags:
0x00
Version:
REV 13
CLEI Code:
IPUCBA8CAA
ID: Adapter Card
FRU Model Number: MX2000-LC-ADAPTER
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 3d 01 0d 52 45 56 20 31 33 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 33 35 39 36 00 00
Address 0x20: 53 2f 4e 20 41 42 42 58 35 35 33 32 00 0c 09 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 43 42 41 38 43 41 41 4d
Address 0x50: 58 32 30 30 30 2d 4c 43 2d 41 44 41 50 54 45 52
Address 0x60: 00 00 00 00 00 00 41 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 3a 00 00 00 00 00 00 00 00 00 00 00 00
...
Serial number
ZX8744
VK00254
VG00015
VH00097
VJ00151
VJ00149
WA00008
WA00014
9009094134
9009094141
CAAB3491
CAAB3489
ZV1828
ZZ2568
ZZ2563
ZZ2564
ZZ2580
ZZ2579
CAAB4882
CAAB4898
CAAB1919
RE-S-1800X4-16G-S
RE-S-1800X4-16G-S
750-040257
750-040257
711-032385
711-032385
711-032385
711-032385
711-032385
711-0323856
711-044170
711-044170
MPC-3D-16XGE-SFPP
1367
FPC 1
MIC 0
MIC 1
FPC 8
MIC 0
MIC 1
FPC 9
ADC 0
ADC 1
ADC 8
ADC 9
Fan Tray
Fan Tray
Fan Tray
Fan Tray
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
21
03
03
22
26
26
11
05
01
01
02
2A
2A
2A
2A
750-033205
750-033307
750-033307
750-031089
750-028392
750-028387
750-036284
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
ZG5027
ZV6299
ZV6268
ZT9746
ABBS1150
ABBR9582
ZL3591
CAAC2073
ZV4117
ZV4107
ZW1555
ACAY0015
ACAY0019
ACAY0020
ACAY0021
MX-MPC3-3D
MIC3-3D-10XGE-SFPP
MIC3-3D-10XGE-SFPP
MX-MPC2-3D
MIC-3D-20GE-SFP
MIC-3D-4XGE-XFP
MPCE-3D-16XGE-SFPP
750-043596
750-043596
750-043596
750-043596
RE-S-1800X4-16G-S
RE-S-1800X4-16G-S
750-040257
750-040257
711-032385
711-032385
711-032385
711-032385
711-032385
711-0323856
711-044170
711-044170
MPC-3D-16XGE-SFPP
MX-MPC3-3D
MIC3-3D-10XGE-SFPP
MIC3-3D-10XGE-SFPP
MX-MPC2-3D
MIC-3D-20GE-SFP
MIC-3D-4XGE-XFP
MPCE-3D-16XGE-SFPP
750-043596
750-043596
750-043596
750-043596
show chassis hardware (MX2010 Routers with MPC6E and OTN MIC)
user@host> show chassis hardware
1368
Hardware inventory:
Item
Version Part number Serial number
Chassis
JN11C9AFEAFK
Midplane
REV 35
750-044636
ABAB9188
Midplane 1
REV 02
711-044557
ABAB8729
PMP
REV 04
711-032426
ACAJ2432
FPM Board
REV 09
760-044634
ABCA4314
PSM 0
REV 01
740-050037
1EDB321015C
Module
PSM 1
REV 01
740-050037
1EDB321015J
Module
PSM 2
REV 01
740-050037
1EDB32000K8
Module
PSM 3
REV 01
740-050037
1EDB32101JW
Module
PSM 4
REV 01
740-050037
1EDB321015G
Module
PSM 5
REV 01
740-050037
1EDB32101HH
Module
PSM 6
REV 01
740-050037
1EDB32101HD
Module
PSM 7
REV 01
740-050037
1EDB321015F
Module
PSM 8
REV 01
740-050037
1EDB321015B
Module
PDM 0
REV 03
740-045234
1EFA3220433
PDM 1
REV 03
740-045234
1EFA3220425
Routing Engine 0 REV 02
740-041821
9009115685
Routing Engine 1 REV 02
740-041821
9009099711
CB 0
REV 23
750-040257
CABE8395
CB 1
REV 12
750-040257
CAAD9499
SPMB 0
REV 02
711-041855
ABCG8426
SPMB 1
REV 02
711-041855
ABBS1481
SFB 0
REV 06
711-044466
ABCD5013
SFB 1
REV 06
711-044466
ABCD5160
SFB 2
REV 06
711-044466
ABCD5175
SFB 3
REV 06
711-044466
ABCD4938
SFB 4
REV 06
711-044466
ABCD4944
SFB 5
REV 06
711-044466
ABCD4968
SFB 6
REV 06
711-044466
ABCD5267
SFB 7
REV 06
711-044466
ABCD4997
FPC 0
REV 59
750-044130
ABCT7676
CPU
REV 10
711-045719
ABCK8527
XLM 0
REV 13
711-046638
ABCT7810
XLM 1
REV 13
711-046638
ABCT7811
FPC 2
REV 27
750-033205
ZL6014
CPU
REV 07
711-035209
ZK9068
MIC 0
REV 14
750-033196
CAAW9214
PIC 0
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-046563
XC49FC030
MIC 1
REV 18
750-033199
CAAC3231
PIC 2
BUILTIN
BUILTIN
FPC 3
REV 59
750-044130
ABCT7682
CPU
REV 10
711-045719
ABCK8531
XLM 0
REV 13
711-046638
ABCT7818
XLM 1
REV 13
711-046638
ABCT7819
FPC 4
REV 33
750-044130
ABBY9278
CPU
REV 09
711-045719
ABBY8677
XLM 0
REV 06.2.00 711-046638 ABBY8844
XLM 1
REV 06.2.00 711-046638 ABBY8830
FPC 5
REV 59
750-044130
ABCT7675
Description
MX2010
Lower Backplane
Upper Backplane
Power Midplane
Front Panel Display
DC 52V Power Supply
DC 52V Power Supply
DC 52V Power Supply
DC 52V Power Supply
DC 52V Power Supply
DC 52V Power Supply
DC 52V Power Supply
DC 52V Power Supply
DC 52V Power Supply
DC Power Dist Module
DC Power Dist Module
RE-S-1800x4
RE-S-1800x4
Control Board
Control Board
PMB Board
PMB Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
Switch Fabric Board
MPC6E 3D
RMPC PMB
MPC6E XL
MPC6E XL
MPCE Type 3 3D
HMPC PMB 2G
1X100GE CXP
1X100GE CXP
CFP2-100G-SR10
1X100GE CFP
1X100GE CFP
MPC6E 3D
RMPC PMB
MPC6E XL
MPC6E XL
MPC6E 3D
RMPC PMB
MPC6E XL
MPC6E XL
MPC6E 3D
1369
CPU
XLM 0
XLM 1
FPC 6
CPU
PIC 0
Xcvr 0
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
PIC 3
Xcvr 0
FPC 8
CPU
MIC 0
PIC 0
Xcvr
PIC 1
QXM 0
QXM 1
FPC 9
CPU
MIC 0
PIC 0
Xcvr
Xcvr
MIC 1
PIC 1
Xcvr
Xcvr
XLM 0
XLM 1
ADC 1
ADC 2
ADC 6
ADC 8
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
REV 10
REV 13
REV 13
REV 30
REV 10
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
0
REV
REV
REV
REV
REV
REV
0
1
REV
0
1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
711-045719
ABCK8526
711-046638
ABCT7808
711-046638
ABCT7809
750-028467
ZM4986
711-029089
ZP6541
BUILTIN
BUILTIN
01
740-021308
AQ43GAC
BUILTIN
BUILTIN
01
740-031980
ALM0A6D
01
740-031980
AQF0RB3
01
740-031980
153363A00333
01
740-021308
AN10KYE
BUILTIN
BUILTIN
01
740-021308
APK04YM
BUILTIN
BUILTIN
01
740-031980
AQF0H44
38
750-031090
CABF7313
08
711-030884
CABE6727
18
750-028380
YK8253
BUILTIN
BUILTIN
03
740-014289
AD1148M00TP
BUILTIN
BUILTIN
06
711-028408
CABC5614
06
711-028408
CABC5550
39
750-044130
ABCK1652
09
711-045719
ABCK1655
09
750-049457
ABCP1230
BUILTIN
BUILTIN
NON-JNPR
37300222WP0002
NON-JNPR
FD46F001Y
07
750-049457
ABCV6662
BUILTIN
BUILTIN
NON-JNPR
UQD0014
NON-JNPR
J13J68335
07.2.00 711-046638 ABCK5491
07.2.00 711-046638 ABCK5475
17
750-043596
ABCG9023
01
750-043596
ZV4079
17
750-043596
ABCG8866
17
750-043596
ABCA8993
06
760-046960
ACAY0354
06
760-046960
ACAY0831
06
760-046960
ACAY0892
06
760-046960
ACAY0839
RMPC PMB
MPC6E XL
MPC6E XL
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
MPC Type 2 3D EQ
MPC PMB 2G
3D 2x 10GE XFP
1x 10GE XFP
XFP-10G-SR
1x 10GE XFP
MPC QXM
MPC QXM
MPC6E 3D
RMPC PMB
2X100GE CFP2 OTN
2X100GE CFP2 OTN
CFP2-100G-LR4-D
CFP2-100G-SR10
2X100GE CFP2 OTN
2X100GE CFP2 OTN
CFP2-100G-LR4-D
CFP2-100G-LR4-D
MPC6E XL
MPC6E XL
Adapter Card
Adapter Card
Adapter Card
Adapter Card
172mm FanTray - 6
172mm FanTray - 6
172mm FanTray - 6
172mm FanTray - 6
Fans
Fans
Fans
Fans
show chassis hardware detail (MX2010 Routers with MPC6E and OTN MIC)
user@host> show chassis hardware detail
Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 35
750-044636
Midplane 1
REV 02
711-044557
PMP
REV 04
711-032426
FPM Board
REV 09
760-044634
PSM 0
REV 01
740-050037
Module
PSM 1
REV 01
740-050037
Module
PSM 2
REV 01
740-050037
Module
1370
Serial number
JN11C9AFEAFK
ABAB9188
ABAB8729
ACAJ2432
ABCA4314
1EDB321015C
Description
MX2010
Lower Backplane
Upper Backplane
Power Midplane
Front Panel Display
DC 52V Power Supply
1EDB321015J
1EDB32000K8
PSM 3
REV 01
740-050037
1EDB32101JW
DC 52V Power Supply
Module
PSM 4
REV 01
740-050037
1EDB321015G
DC 52V Power Supply
Module
PSM 5
REV 01
740-050037
1EDB32101HH
DC 52V Power Supply
Module
PSM 6
REV 01
740-050037
1EDB32101HD
DC 52V Power Supply
Module
PSM 7
REV 01
740-050037
1EDB321015F
DC 52V Power Supply
Module
PSM 8
REV 01
740-050037
1EDB321015B
DC 52V Power Supply
Module
PDM 0
REV 03
740-045234
1EFA3220433
DC Power Dist Module
PDM 1
REV 03
740-045234
1EFA3220425
DC Power Dist Module
Routing Engine 0 REV 02
740-041821
9009115685
RE-S-1800x4
ad0
3998 MB Virtium - TuffDrive VCF P1T0200274310822 191 Compact Flash
ad1
30533 MB UGB94BPH32H0S1-KCI
11000043190
Disk 1
usb0 (addr 1) EHCI root hub 0
Intel
uhub0
usb0 (addr 2) product 0x0020 32
vendor 0x8087
uhub1
DIMM 0
VL31B5263F-F8SD DIE REV-0 PCB REV-0
MFR ID-ce80
DIMM 1
VL31B5263F-F8SD DIE REV-0 PCB REV-0
MFR ID-ce80
DIMM 2
VL31B5263F-F8SD DIE REV-0 PCB REV-0
MFR ID-ce80
DIMM 3
VL31B5263F-F8SD DIE REV-0 PCB REV-0
MFR ID-ce80
Routing Engine 1 REV 02
740-041821
9009099711
RE-S-1800x4
ad0
3998 MB Virtium - TuffDrive VCF P1T0200262860208 30 Compact Flash
ad1
30533 MB UGB94ARF32H0S3-KC
UNIGEN-499551-000146 Disk 1
CB 0
REV 23
750-040257
CABE8395
Control Board
CB 1
REV 12
750-040257
CAAD9499
Control Board
SPMB 0
REV 02
711-041855
ABCG8426
PMB Board
SPMB 1
REV 02
711-041855
ABBS1481
PMB Board
SFB 0
REV 06
711-044466
ABCD5013
Switch Fabric Board
SFB 1
REV 06
711-044466
ABCD5160
Switch Fabric Board
SFB 2
REV 06
711-044466
ABCD5175
Switch Fabric Board
SFB 3
REV 06
711-044466
ABCD4938
Switch Fabric Board
SFB 4
REV 06
711-044466
ABCD4944
Switch Fabric Board
SFB 5
REV 06
711-044466
ABCD4968
Switch Fabric Board
SFB 6
REV 06
711-044466
ABCD5267
Switch Fabric Board
SFB 7
REV 06
711-044466
ABCD4997
Switch Fabric Board
FPC 0
REV 59
750-044130
ABCT7676
MPC6E 3D
CPU
REV 10
711-045719
ABCK8527
RMPC PMB
XLM 0
REV 13
711-046638
ABCT7810
MPC6E XL
XLM 1
REV 13
711-046638
ABCT7811
MPC6E XL
FPC 2
REV 27
750-033205
ZL6014
MPCE Type 3 3D
CPU
REV 07
711-035209
ZK9068
HMPC PMB 2G
MIC 0
REV 14
750-033196
CAAW9214
1X100GE CXP
PIC 0
BUILTIN
BUILTIN
1X100GE CXP
Xcvr 0
REV 01
740-046563
XC49FC030
CFP2-100G-SR10
MIC 1
REV 18
750-033199
CAAC3231
1X100GE CFP
PIC 2
BUILTIN
BUILTIN
1X100GE CFP
FPC 3
REV 59
750-044130
ABCT7682
MPC6E 3D
CPU
REV 10
711-045719
ABCK8531
RMPC PMB
XLM 0
REV 13
711-046638
ABCT7818
MPC6E XL
XLM 1
REV 13
711-046638
ABCT7819
MPC6E XL
FPC 4
REV 33
750-044130
ABBY9278
MPC6E 3D
CPU
REV 09
711-045719
ABBY8677
RMPC PMB
XLM 0
REV 06.2.00 711-046638 ABBY8844
MPC6E XL
XLM 1
REV 06.2.00 711-046638 ABBY8830
MPC6E XL
FPC 5
REV 59
750-044130
ABCT7675
MPC6E 3D
CPU
REV 10
711-045719
ABCK8526
RMPC PMB
XLM 0
REV 13
711-046638
ABCT7808
MPC6E XL
XLM 1
REV 13
711-046638
ABCT7809
MPC6E XL
1371
FPC 6
CPU
PIC 0
Xcvr 0
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
PIC 3
Xcvr 0
FPC 8
CPU
MIC 0
PIC 0
Xcvr
PIC 1
QXM 0
QXM 1
FPC 9
CPU
MIC 0
PIC 0
Xcvr
Xcvr
MIC 1
PIC 1
Xcvr
Xcvr
XLM 0
XLM 1
ADC 1
ADC 2
ADC 6
ADC 8
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
REV 30
REV 10
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
0
REV
REV
REV
REV
REV
REV
0
1
REV
0
1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
750-028467
ZM4986
711-029089
ZP6541
BUILTIN
BUILTIN
01
740-021308
AQ43GAC
BUILTIN
BUILTIN
01
740-031980
ALM0A6D
01
740-031980
AQF0RB3
01
740-031980
153363A00333
01
740-021308
AN10KYE
BUILTIN
BUILTIN
01
740-021308
APK04YM
BUILTIN
BUILTIN
01
740-031980
AQF0H44
38
750-031090
CABF7313
08
711-030884
CABE6727
18
750-028380
YK8253
BUILTIN
BUILTIN
03
740-014289
AD1148M00TP
BUILTIN
BUILTIN
06
711-028408
CABC5614
06
711-028408
CABC5550
39
750-044130
ABCK1652
09
711-045719
ABCK1655
09
750-049457
ABCP1230
BUILTIN
BUILTIN
NON-JNPR
37300222WP0002
NON-JNPR
FD46F001Y
07
750-049457
ABCV6662
BUILTIN
BUILTIN
NON-JNPR
UQD0014
NON-JNPR
J13J68335
07.2.00 711-046638 ABCK5491
07.2.00 711-046638 ABCK5475
17
750-043596
ABCG9023
01
750-043596
ZV4079
17
750-043596
ABCG8866
17
750-043596
ABCA8993
06
760-046960
ACAY0354
06
760-046960
ACAY0831
06
760-046960
ACAY0892
06
760-046960
ACAY0839
Fans
Fans
Fans
Fans
show chassis hardware extensive (MX2010 Routers with MPC6E and OTN MIC)
user@host> show chassis hardware extensive
Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11C9AFEAFK
MX2010
Jedec Code:
0x7fb0
EEPROM Version:
0x02
S/N:
JN11C9AFEAFK
Assembly ID: 0x0557
Assembly Version: 00.00
Date:
00-00-0000
Assembly Flags:
0x00
ID: MX2010
Board Information Record:
Address 0x00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I2C Hex Data:
Address 0x00: 7f b0 02 ff 05 57 00 00 00 00 00 00 00 00 00 00
Address 0x10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x20: 4a 4e 31 31 43 39 41 46 45 41 46 4b 00 00 00 00
Address 0x30: 00 00 00 ff 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
1372
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x70: 00 00 00 00 00 00 00 00 00 00 00 00
Midplane
REV 35
750-044636
ABAB9188
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-044636
S/N:
Assembly ID: 0x0b66
Assembly Version:
Date:
06-21-2013
Assembly Flags:
Version:
REV 35
CLEI Code:
ID: Lower Backplane
FRU Model Number:
Board Information Record:
Address 0x00: ad 01 08 00 3c 8a b0 38 68 00 ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 66 01 23 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 34 36
Address 0x20: 53 2f 4e 20 41 42 41 42 39 31 38 38
Address 0x30: dd ff ff ff ad 01 08 00 3c 8a b0 38
Address 0x40: ff ff ff ff 01 49 50 4d 55 38 31 30
Address 0x50: 48 41 53 2d 42 50 2d 4d 58 32 30 31
Address 0x60: 00 00 00 00 00 00 30 36 00 ff ff ff
Address 0x70: ff ff ff f8 ff ff ff ff ff ff ff ff
Midplane 1
REV 02
711-044557
ABAB8729
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-044557
S/N:
Assembly ID: 0x0b65
Assembly Version:
Date:
03-21-2013
Assembly Flags:
Version:
REV 02
ID: Upper Backplane
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 0b 65 01 02 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 34 34 35
Address 0x20: 53 2f 4e 20 41 42 41 42 38 37 32 39
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff
PMP
REV 04
711-032426
ACAJ2432
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-032426
S/N:
Assembly ID: 0x045d
Assembly Version:
Date:
03-28-2013
Assembly Flags:
Version:
REV 04
ID: Power Midplane
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 5d 01 04 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 32 34
Address 0x20: 53 2f 4e 20 41 43 41 4a 32 34 33 32
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff
FPM Board
REV 09
760-044634
ABCA4314
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
760-044634
S/N:
Assembly ID: 0x0b64
Assembly Version:
00 00 00 00
00 00 00 00
00 00 00 00
Lower Backplane
0x02
ABAB9188
01.35
0x00
IPMU810ARA
CHAS-BP-MX2010-S
ff ff ff ff
33
33
00
68
41
30
ff
ff
35
36
15
00
52
2d
ff
ff
00 00
00 00
06 07
ff ff
41 43
53 00
ff ff
ff ff
Upper Backplane
0x01
ABAB8729
01.02
0x00
ff ff ff ff
30
35
00
ff
00
00
ff
ff
32
37
15
ff
00
00
ff
ff
00 00
00 00
03 07
ff ff
00 00
00 00
ff ff
ff ff
Power Midplane
0x01
ACAJ2432
01.04
0x00
ff ff ff ff
30
32
00
ff
00
00
ff
ff
34
36
1c
ff
00
00
ff
ff
00 00
00 00
03 07
ff ff
00 00
00 00
ff ff
ff ff
Front Panel Display
0x02
ABCA4314
01.09
1373
Date:
03-28-2013
Assembly Flags:
0x00
Version:
REV 09
CLEI Code:
IPMYA4EJRA
ID: Front Panel Display
FRU Model Number: MX2010-CRAFT-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 64 01 09 52 45 56 20 30 39 00 00
Address 0x10: 00 00 00 00 37 36 30 2d 30 34 34 36 33 34 00 00
Address 0x20: 53 2f 4e 20 41 42 43 41 34 33 31 34 00 1c 03 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 4d 59 41 34 45 4a 52 41 4d
Address 0x50: 58 32 30 31 30 2d 43 52 41 46 54 2d 53 00 00 00
Address 0x60: 00 00 00 00 00 00 41 00 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 93 ff ff ff ff ff ff ff ff ff ff ff ff
PSM 0
REV 01
740-050037
1EDB321015C
DC 52V Power Supply
Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-050037
S/N:
1EDB321015C
Assembly ID: 0x0478
Assembly Version: 01.01
Date:
05-28-2013
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
IPUPAKRKAA
ID: DC 52V Power Supply Module FRU Model Number: MX2000-PSM-DC-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30 33 37 00 00
Address 0x20: 31 45 44 42 33 32 31 30 31 35 43 00 00 1c 05 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52 4b 41 41 4d
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43 2d 53 00 00
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00 00 00 00 00
PSM 1
REV 01
740-050037
1EDB321015J
DC 52V Power Supply
Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-050037
S/N:
1EDB321015J
Assembly ID: 0x0478
Assembly Version: 01.01
Date:
05-28-2013
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
IPUPAKRKAA
ID: DC 52V Power Supply Module FRU Model Number: MX2000-PSM-DC-S
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20 30 31 00 00
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30 33 37 00 00
Address 0x20: 31 45 44 42 33 32 31 30 31 35 4a 00 00 1c 05 07
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52 4b 41 41 4d
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43 2d 53 00 00
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00 00 00 00 00
PSM 2
REV 01
740-050037
1EDB32000K8
DC 52V Power Supply
Module
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
740-050037
S/N:
1EDB32000K8
Assembly ID: 0x0478
Assembly Version: 01.01
Date:
05-23-2013
Assembly Flags:
0x00
Version:
REV 01
CLEI Code:
IPUPAKRKAA
ID: DC 52V Power Supply Module FRU Model Number: MX2000-PSM-DC-S
Board Information Record:
1374
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 30 30 30 4b 38 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 3
REV 01
740-050037
1EDB32101JW
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-30-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 31 30 31 4a 57 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 4
REV 01
740-050037
1EDB321015G
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-28-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 31 30 31 35 47 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 5
REV 01
740-050037
1EDB32101HH
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-30-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
17
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB32101JW
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
1e
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB321015G
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
1c
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB32101HH
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30 31 00 00
33 37 00 00
1375
Address 0x20: 31 45 44 42 33 32 31 30 31 48 48 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 6
REV 01
740-050037
1EDB32101HD
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-30-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 31 30 31 48 44 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 7
REV 01
740-050037
1EDB321015F
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-28-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 31 30 31 35 46 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 8
REV 01
740-050037
1EDB321015B
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-28-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 31 30 31 35 42 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
1376
00
ff
4b
2d
ff
00
1e
ff
41
53
ff
00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB32101HD
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
1e
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB321015F
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
1c
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB321015B
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
31
37
1c
ff
41
53
00
00
05
ff
41
00
00
00
07
ff
4d
00
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PDM 0
REV 03
740-045234
1EFA3220433
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-045234
S/N:
Assembly ID: 0x047b
Assembly Version:
Date:
05-30-2013
Assembly Flags:
Version:
REV 03
CLEI Code:
ID: DC Power Dist Module
FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 7b 01 03 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 34 35 32
Address 0x20: 31 45 46 41 33 32 32 30 34 33 33 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4a 53
Address 0x50: 58 32 30 30 30 2d 50 44 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 33 ff ff ff
Address 0x70: ff ff ff 1d 00 00 00 00 00 00 00 00
PDM 1
REV 03
740-045234
1EFA3220425
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-045234
S/N:
Assembly ID: 0x047b
Assembly Version:
Date:
05-30-2013
Assembly Flags:
Version:
REV 03
CLEI Code:
ID: DC Power Dist Module
FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
..
ff ff ff ff
00 00 00 00
DC Power Dist Module
0x02
1EFA3220433
01.03
0x00
IPUPAJSKAA
MX2000-PDM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
33
34
1e
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC Power Dist Module
0x02
1EFA3220425
01.03
0x00
IPUPAJSKAA
MX2000-PDM-DC-S
ff ff ff ff
Serial number
JN11E2227AFJ
ABAB9384
ABAB9386
ACAJ1579
ACAJ1524
ABBT8837
1E022240056
Description
MX2020
Lower Power Midplane
Upper Backplane
Upper Power Midplane
Lower Power Midplane
Front Panel Display
DC 52V Power Supply
1E022240054
1E02224005H
1E022240053
1E02224004K
1E02224006W
1E022240062
1E02224005B
1E02224005A
1E022240052
1377
Module
PSM 12
REV 01
Module
PSM 13
REV 01
Module
PSM 14
REV 01
Module
PSM 15
REV 01
Module
PSM 16
REV 01
Module
PSM 17
REV 01
Module
PDM 0
REV 01
PDM 1
REV 01
PDM 2
REV 01
PDM 3
REV 01
Routing Engine 0 REV 02
Routing Engine 1 REV 02
CB 0
REV 14
CB 1
REV 08
SPMB 0
REV 01
SPMB 1
REV 02
SFB 0
REV 03
SFB 1
REV 05
SFB 2
REV 05
SFB 3
REV 05
SFB 4
REV 05
SFB 5
REV 05
SFB 6
REV 03
SFB 7
REV 05
FPC 0
REV 30
CPU
REV 10
PIC 0
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 1
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 2
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 3
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
FPC 1
REV 30
CPU
REV 10
PIC 0
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 1
1378
740-045050
1E022240051
740-045050
1E022240058
740-045050
1E02224004L
740-045050
1E02224005M
740-045050
1E02224006S
740-045050
1E02224005Z
740-045234
740-045234
740-045234
740-045234
740-041821
740-041821
750-040257
750-040257
711-041855
711-041855
711-044466
711-044466
711-044466
711-044466
711-044466
711-044466
711-044466
711-044466
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
1E012150033
1E012150027
1E012150028
1E012150045
9009089704
9009094138
CAAF8430
CAAB3482
ZS2290
CAAA6141
ABBV6789
ABBX5666
ABBX5678
ABBX5687
ABBX5609
ABBX5675
ABBV6805
ABBX5701
ABBN0284
ABBN0507
BUILTIN
B11E00990
B11E04357
B11F01327
B11E04375
BUILTIN
B11E02760
B11E02904
B11E03963
B11E00756
BUILTIN
B11E04418
B11E01077
B11E01128
B11F01253
BUILTIN
B11E01140
B11F01626
B11E01075
B11E01177
ABBN0208
ABBJ1084
BUILTIN
B11E04745
B11F01570
B11E04388
B11F01439
BUILTIN
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 2
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 3
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 4
CPU
PIC 0
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-031980
750-028467
711-029089
BUILTIN
B11E04739
B11F01869
B11F01675
B11F01901
BUILTIN
B11F01346
B11F01288
B11F01824
B11E04312
BUILTIN
B11E02811
B11E03847
B11F01495
B11F01265
ZM5111
ZP6607
BUILTIN
AK80LJA
AK80MFZ
AK80NKL
AK80KF4
BUILTIN
AK80FBJ
AK80MM2
AK80LJV
AK80NXV
BUILTIN
AK80N1H
AK80NLS
AK80FL5
AK80NL9
BUILTIN
AK80NG2
AK80KDU
AK80MG1
AK80MM0
ABBN0302
ABBN0495
BUILTIN
B11F01581
B11E01176
B11F01251
B11E02752
BUILTIN
B11E00786
B11E01020
B11E01023
B11E02819
BUILTIN
B11E02812
B11D04437
B11F01279
B11F01333
BUILTIN
B11E00978
B11E01018
B11F01784
AK80NKP
ABBN0308
ABBJ1095
BUILTIN
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
1379
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
1380
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
REV 01
REV 01
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
B11E04305
B11E01147
B11E01195
B11F01743
BUILTIN
B11F01892
B11E02880
B11E00725
B11E01057
BUILTIN
B11E02816
B11C04501
B11E02764
B11E00789
BUILTIN
B11F01250
B11E02847
B11E00787
B11E03803
ABBN0316
ABBJ1082
BUILTIN
B11K00523
B11K01848
B11K01865
B11K00540
BUILTIN
B11K00422
B11K00428
B11K00423
B11K01855
BUILTIN
B11K01847
B11K00526
B11K00529
B11K00525
BUILTIN
B11K00425
B11K00530
B11K01851
B11K00528
ABBN6832
ABBK6534
BUILTIN
AK80MB4
AK80FQ6
AK80N1F
AK80NLQ
BUILTIN
AK80KDR
AK80FGJ
AK80N5G
AK80KD8
BUILTIN
AK80LET
AK80N1X
AK80NRF
AK80NL2
BUILTIN
AK80N3D
AK80MRB
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
Xcvr
Xcvr
FPC 7
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 8
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 9
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
2
3
REV
REV
REV
REV
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
23
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
REV 01
REV 01
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-021308
740-031980
740-021308
740-021308
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
AK80LEQ
AK80LER
ABBN6811
ABBN7288
BUILTIN
AK80NK8
AK80LJG
AK80LBU
AK80N21
BUILTIN
AK80LEU
AK80NLM
AK80NL6
AK80LES
BUILTIN
AK80LEN
AK80ME0
AK80LMG
AK80MM1
BUILTIN
AK80MG7
AK80KF9
AK80NRQ
AK80NLE
YN2977
YP1856
BUILTIN
183363A00875
183363A00851
183363A00772
183363A00882
BUILTIN
183363A00735
183363A00169
183363A00726
183363A00077
BUILTIN
183363A00168
183363A00676
183363A00732
183363A00091
BUILTIN
183363A00725
183363A00642
183363A00871
183363A00853
ABBN6798
ABBK6556
BUILTIN
9ZDZ06A00055
183363A00239
AD0915E003K
AD0915E003A
BUILTIN
AK80MRC
AK80NL5
AK80NKN
AK80N3U
BUILTIN
AK80N1T
AJ808DJ
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
1381
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 10
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 11
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 12
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
1382
2
3
REV 01
REV 01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
REV 01
REV 01
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-021308
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
AK80NG4
AK80FND
BUILTIN
AK80FKQ
AK80NLT
AK80NKR
AK80LKM
ABBN6813
ABBK6542
BUILTIN
AK80NA3
AK80NLF
AK80MRH
AK80KE4
BUILTIN
973152A00030
AK80L9H
AK80ME8
AK80NLR
BUILTIN
AK80NG1
AK80MCA
AK80LFC
AK80LEM
BUILTIN
AK80N9X
AK80LAC
AK80LF2
AK80N8T
ABBN0281
ABBN0526
BUILTIN
B11F01326
B11E03973
B11E00950
B11E00674
BUILTIN
B11E00775
B11E04461
B11E01074
B11E02821
BUILTIN
B11E04501
B11E00757
B11F01623
B11E01022
BUILTIN
B11E04359
B11E02751
B11E02736
B11E01178
ABBN6796
ABBN7259
BUILTIN
B11K01856
B11K01853
B11K01863
163363A02863
BUILTIN
163363A02668
163363A02881
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 13
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 14
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 15
CPU
PIC 0
Xcvr
Xcvr
2
3
REV 01
REV 01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
REV 01
REV 01
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-021310
740-021310
740-021310
740-021310
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-021308
750-028467
711-029089
BUILTIN
740-031980
740-031980
163363A01671
163363A02627
BUILTIN
163363A02725
163363A02692
163363A02730
163363A03081
BUILTIN
163363A02736
163363A02568
163363A02747
163363A02579
ABBN0270
ABBJ0966
BUILTIN
AK80NL1
AK80NXW
AK80KD2
AK80FMD
BUILTIN
AK80NKQ
AK80MGH
AK80N38
AK80NL7
BUILTIN
AK80LEL
AK80NKD
AK80KCY
AK80LHK
BUILTIN
AK80M5J
AK80MBE
AK80NLG
AK80LFH
ABBN6790
ABBK6515
BUILTIN
AK80LZM
AK80MCC
AK80KCM
AK80KE0
BUILTIN
C10F99155
C10F99049
C10F99128
C10F99169
BUILTIN
AK80LF3
163363A02597
163363A03060
163363A03057
BUILTIN
AK80LEX
AK80FEU
AK80FNM
AJQ0Q5G
ABBN6791
ABBN7289
BUILTIN
B11K00424
B11K01849
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-LRM
SFP+-10G-LRM
SFP+-10G-LRM
SFP+-10G-LRM
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
1383
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 16
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 17
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
1384
2
3
REV 01
REV 01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-030658
740-030658
740-030658
740-031980
750-028467
711-029089
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
B11K01862
B11K01852
BUILTIN
B11K00427
B11K00430
B11K01854
B11K00426
BUILTIN
B11K00429
B11K01864
B11K01850
B11K00522
BUILTIN
B11E01144
B11E00985
B11E00796
B11K01866
ABBM4592
ABBN0465
BUILTIN
B11F01435
B11E01052
B11F01328
B11F01254
BUILTIN
B11E02738
B11E02881
B11F01624
B11E00889
BUILTIN
B11E02883
B11E00681
B11E04306
B11E02813
BUILTIN
B11F01801
B11E02753
B11E01156
B11E04324
ABBN6810
ABBN7237
BUILTIN
163363A02638
163363A02082
163363A01674
163363A03058
BUILTIN
163363A03048
163363A02729
163363A02566
163363A02567
BUILTIN
163363A02878
163363A02739
163363A01959
163363A02660
BUILTIN
163363A02731
163363A02588
163363A02673
163363A02654
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
FPC 18
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 19
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
ADC 0
ADC 1
ADC 2
ADC 3
ADC 4
ADC 5
ADC 6
ADC 7
ADC 8
ADC 9
ADC 10
ADC 11
ADC 12
ADC 13
ADC 14
ADC 15
ADC 16
REV 30
REV 10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
13
13
13
13
13
13
13
07
07
07
13
13
13
13
13
13
13
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031981
740-031981
740-031981
740-031981
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
ABBM4739
ABBN0487
BUILTIN
163363A02569
163363A02886
163363A03082
133363A00297
BUILTIN
163363A02726
163363A03050
163363A02884
163363A03076
BUILTIN
163363A02581
163363A02873
163363A02582
163363A03083
BUILTIN
UL70BU6
UL50QC6
UL708N6
UL603KK
ABBN6827
ABBK6508
BUILTIN
163363A01688
163363A01724
163363A01773
163363A02593
BUILTIN
163363A03061
163363A03056
163363A02669
163363A03070
BUILTIN
163363A02572
163363A02697
163363A02585
163363A03052
BUILTIN
163363A02591
163363A02649
163363A02577
163363A02698
ABBX5561
ABBX5546
ABBX5535
ABBX5552
ABBX5581
ABBX5545
ABBX5554
ABBV7194
ABBV7251
ABBV7202
ABBX5538
ABBX5566
ABBX5542
ABBX5539
ABBX5555
ABBX5557
ABBX5536
1385
ADC
ADC
ADC
Fan
Fan
Fan
Fan
17
18
19
Tray
Tray
Tray
Tray
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
13
13
11
2A
2A
2A
2A
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
ABBX5559
ABBX5537
ABBW5685
ACAY0030
ACAY0039
ACAY0033
ACAY0062
Adapter Card
Adapter Card
Adapter Card
172mm FanTray
172mm FanTray
172mm FanTray
172mm FanTray
6
6
6
6
Fans
Fans
Fans
Fans
1386
Routing Engine 1
ad0
3831 MB
ad1
30533 MB
CB 0
CB 1
SPMB 0
SPMB 1
SFB 0
SFB 1
SFB 2
SFB 3
SFB 4
SFB 5
SFB 6
SFB 7
FPC 0
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
REV
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 1
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
FPC 2
CPU
REV 02
740-041821
9009089709
RE-S-1800x4
UGB30SFA4000T1
SFA4000T1 00000113 Compact Flash
UGB94ARF32H0S3-KC
UNIGEN-478612-001044 Disk 1
REV 08
750-040257
CAAB3482
Control Board
REV 04
750-040257
ZT2864
Control Board
REV 02
711-041855
CAAA6141
PMB Board
REV 01
711-041855
ZS2275
PMB Board
REV 05
711-044466
ABBT2161
Switch Fabric Board
REV 05
711-044466
ABBT2159
Switch Fabric Board
REV 05
711-044466
ABBX3718
Switch Fabric Board
REV 05
711-044466
ABBT2152
Switch Fabric Board
REV 05
711-044466
ABBT2160
Switch Fabric Board
REV 05
711-044466
ABBT2145
Switch Fabric Board
REV 05
711-044466
ABBT2150
Switch Fabric Board
REV 05
711-044466
ABBT2163
Switch Fabric Board
REV 30
750-028467
ABBN0284
MPC 3D 16x 10GE
REV 10
711-029089
ABBN0507
AMPC PMB
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E00990
SFP+-10G-USR
REV 01
740-030658
B11E04357
SFP+-10G-USR
REV 01
740-030658
B11F01327
SFP+-10G-USR
01
740-030658
B11E04375
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E02760
SFP+-10G-USR
REV 01
740-030658
B11E02904
SFP+-10G-USR
REV 01
740-030658
B11E03963
SFP+-10G-USR
REV 01
740-030658
B11E00756
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E04418
SFP+-10G-USR
REV 01
740-030658
B11E01077
SFP+-10G-USR
REV 01
740-030658
B11E01128
SFP+-10G-USR
REV 01
740-030658
B11F01253
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E01140
SFP+-10G-USR
REV 01
740-030658
B11F01626
SFP+-10G-USR
REV 01
740-030658
B11E01075
SFP+-10G-USR
REV 01
740-030658
B11E01177
SFP+-10G-USR
REV 30
750-028467
ABBN0308
MPC 3D 16x 10GE
REV 10
711-029089
ABBJ1095
AMPC PMB
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E04305
SFP+-10G-USR
REV 01
740-030658
B11E01147
SFP+-10G-USR
REV 01
740-030658
B11E01195
SFP+-10G-USR
REV 01
740-030658
B11F01743
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11F01892
SFP+-10G-USR
REV 01
740-030658
B11E02880
SFP+-10G-USR
REV 01
740-030658
B11E00725
SFP+-10G-USR
REV 01
740-030658
B11E01057
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11E02816
SFP+-10G-USR
REV 01
740-030658
B11C04501
SFP+-10G-USR
REV 01
740-030658
B11E02764
SFP+-10G-USR
REV 01
740-030658
B11E00789
SFP+-10G-USR
BUILTIN
BUILTIN
4x 10GE(LAN) SFP+
REV 01
740-030658
B11F01250
SFP+-10G-USR
REV 01
740-030658
B11E02847
SFP+-10G-USR
REV 01
740-030658
B11E00787
SFP+-10G-USR
REV 01
740-030658
B11E03803
SFP+-10G-USR
REV 30
750-028467
ABBN0316
MPC 3D 16x 10GE
REV 10
711-029089
ABBJ1082
AMPC PMB
1387
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr 0
Xcvr
Xcvr
Xcvr
FPC 3
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 4
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
1388
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
1
2
3
REV 01
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
BUILTIN
BUILTIN
740-031980
B11K00523
740-031980
B11K01848
740-031980
B11K01865
740-031980
B11K00540
BUILTIN
BUILTIN
01
740-031980
B11K00422
01
740-031980
B11K00428
01
740-031980
B11K00423
01
740-031980
B11K01855
BUILTIN
BUILTIN
01
740-031980
B11K01847
01
740-031980
B11K00526
01
740-031980
B11K00529
01
740-031980
B11K00525
BUILTIN
BUILTIN
740-031980
B11K00425
01
740-031980
B11K00530
01
740-031980
B11K01851
01
740-031980
B11K00528
32
750-028467
ABBN6832
10
711-029089
ABBK6534
BUILTIN
BUILTIN
01
740-031980
AK80MB4
01
740-031980
AK80FQ6
01
740-031980
AK80N1F
01
740-031980
AK80NLQ
BUILTIN
BUILTIN
01
740-031980
AK80KDR
01
740-031980
AK80FGJ
01
740-031980
AK80N5G
01
740-031980
AK80KD8
BUILTIN
BUILTIN
01
740-031980
AK80LET
01
740-031980
AK80N1X
01
740-031980
AK80NRF
01
740-031980
AK80NL2
BUILTIN
BUILTIN
01
740-031980
AK80N3D
01
740-031980
AK80MRB
01
740-031980
AK80LEQ
01
740-031980
AK80LER
32
750-028467
ABBN6811
10
711-029089
ABBN7288
BUILTIN
BUILTIN
01
740-031980
AK80NK8
01
740-031980
AK80LJG
01
740-031980
AK80LBU
01
740-031980
AK80N21
BUILTIN
BUILTIN
01
740-031980
AK80LEU
01
740-031980
AK80NLM
01
740-031980
AK80NL6
01
740-031980
AK80LES
BUILTIN
BUILTIN
01
740-031980
AK80LEN
01
740-031980
AK80ME0
01
740-031980
AK80LMG
01
740-031980
AK80MM1
BUILTIN
BUILTIN
01
740-031980
AK80MG7
01
01
01
01
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
Xcvr
Xcvr
Xcvr
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr 0
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 7
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
1
2
3
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
1
2
3
REV 01
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
01
01
01
32
10
740-031980
AK80KF9
740-031980
AK80NRQ
740-031980
AK80NLE
750-028467
ABBN6791
711-029089
ABBN7289
BUILTIN
BUILTIN
01
740-031980
B11K00424
01
740-031980
B11K01849
01
740-031980
B11K01862
01
740-031980
B11K01852
BUILTIN
BUILTIN
740-031980
B11K00427
01
740-031980
B11K00430
01
740-031980
B11K01854
01
740-031980
B11K00426
BUILTIN
BUILTIN
01
740-031980
B11K00429
01
740-031980
B11K01864
01
740-031980
B11K01850
01
740-031980
B11K00522
BUILTIN
BUILTIN
01
740-030658
B11E01144
01
740-030658
B11E00985
01
740-030658
B11E00796
01
740-031980
B11K01866
30
750-028467
ABBM4592
10
711-029089
ABBN0465
BUILTIN
BUILTIN
01
740-030658
B11F01435
01
740-030658
B11E01052
01
740-030658
B11F01328
01
740-030658
B11F01254
BUILTIN
BUILTIN
01
740-030658
B11E02738
01
740-030658
B11E02881
01
740-030658
B11F01624
01
740-030658
B11E00889
BUILTIN
BUILTIN
01
740-030658
B11E02883
01
740-030658
B11E00681
01
740-030658
B11E04306
01
740-030658
B11E02813
BUILTIN
BUILTIN
01
740-030658
B11F01801
01
740-030658
B11E02753
01
740-030658
B11E01156
01
740-030658
B11E04324
32
750-028467
ABBN6810
10
711-029089
ABBN7237
BUILTIN
BUILTIN
01
740-031980
163363A03058
01
740-031980
163363A02082
01
740-031980
163363A01674
01
740-031980
163363A02638
BUILTIN
BUILTIN
01
740-031980
163363A03048
01
740-031980
163363A02729
01
740-031980
163363A02566
01
740-031980
163363A02567
BUILTIN
BUILTIN
01
740-031980
163363A02878
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
1389
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr 2
Xcvr
FPC 8
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 9
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 10
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
1390
1
2
3
0
1
3
REV 01
REV 01
REV 01
REV
REV
REV 01
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
REV
0
1
2
3
REV
REV
REV
REV
REV
740-031980
163363A02739
740-031980
163363A01959
740-031980
163363A02660
BUILTIN
BUILTIN
01
740-031980
163363A02731
01
740-031980
163363A02588
740-031980
163363A02673
01
740-031980
163363A02654
30
750-028467
ABBM4739
10
711-029089
ABBN0487
BUILTIN
BUILTIN
01
740-031980
163363A02569
01
740-031980
163363A02886
01
740-031980
163363A03082
01
740-031980
133363A00297
BUILTIN
BUILTIN
01
740-031980
163363A02726
01
740-031980
163363A03050
01
740-031980
163363A02884
01
740-031980
163363A03076
BUILTIN
BUILTIN
01
740-031980
163363A02581
01
740-031980
163363A02873
01
740-031980
163363A02582
01
740-031980
163363A03083
BUILTIN
BUILTIN
01
740-031981
UL70BU6
01
740-031981
UL50QC6
01
740-031981
UL708N6
01
740-031981
UL603KK
32
750-028467
ABBN6827
10
711-029089
ABBK6508
BUILTIN
BUILTIN
01
740-031980
163363A01688
01
740-031980
163363A01724
01
740-031980
163363A01773
01
740-031980
163363A02593
BUILTIN
BUILTIN
01
740-031980
163363A03061
01
740-031980
163363A03056
01
740-031980
163363A02669
01
740-031980
163363A03070
BUILTIN
BUILTIN
01
740-031980
163363A02572
01
740-031980
163363A02697
01
740-031980
163363A02585
01
740-031980
163363A03052
BUILTIN
BUILTIN
01
740-031980
163363A02591
01
740-031980
163363A02649
01
740-031980
163363A02577
01
740-031980
163363A02698
30
750-028467
ABBN0302
10
711-029089
ABBN0495
BUILTIN
BUILTIN
01
740-030658
B11F01581
01
740-030658
B11E01176
01
740-030658
B11F01251
01
740-030658
B11E02752
BUILTIN
BUILTIN
01
740-030658
B11E00786
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-LR
SFP+-10G-LR
SFP+-10G-LR
SFP+-10G-LR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
Xcvr
Xcvr 2
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 11
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 12
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 13
CPU
PIC 0
Xcvr
1
3
0
1
2
3
0
1
2
3
0
1
2
3
0
1
2
3
0
1
2
3
0
1
2
3
0
1
2
3
0
1
2
3
0
1
2
3
0
1
2
3
REV 01
740-030658
B11E01020
REV 01
740-030658
B11E01023
REV 01
740-030658
B11E02819
BUILTIN
BUILTIN
REV 01
740-030658
B11E02812
REV 01
740-030658
B11D04437
REV 01
740-030658
B11F01279
REV 01
740-030658
B11F01333
BUILTIN
BUILTIN
REV 01
740-030658
B11E00978
REV 01
740-030658
B11E01018
REV 01
740-030658
B11F01784
REV 01
740-031980
AK80NKP
REV 32
750-028467
ABBN6790
REV 10
711-029089
ABBK6515
BUILTIN
BUILTIN
REV 01
740-031980
AK80LZM
REV 01
740-031980
AK80MCC
REV 01
740-031980
AK80KCM
REV 01
740-031980
AK80KE0
BUILTIN
BUILTIN
REV 01
740-021310
C10F99155
REV 01
740-021310
C10F99049
REV 01
740-021310
C10F99128
REV 01
740-021310
C10F99169
BUILTIN
BUILTIN
REV 01
740-031980
AK80LF3
REV 01
740-031980
163363A02597
REV 01
740-031980
163363A03060
REV 01
740-031980
163363A03057
BUILTIN
BUILTIN
REV 01
740-031980
AK80LEX
REV 01
740-031980
AK80FEU
REV 01
740-031980
AK80FNM
REV 01
740-021308
AJQ0Q5G
REV 30
750-028467
ZM5111
REV 10
711-029089
ZP6607
BUILTIN
BUILTIN
REV 01
740-031980
AK80LJA
REV 01
740-031980
AK80MFZ
REV 01
740-031980
AK80NKL
REV 01
740-031980
AK80KF4
BUILTIN
BUILTIN
REV 01
740-031980
AK80FBJ
REV 01
740-031980
AK80MM2
REV 01
740-031980
AK80LJV
REV 01
740-031980
AK80NXV
BUILTIN
BUILTIN
REV 01
740-031980
AK80N1H
REV 01
740-031980
AK80NLS
REV 01
740-031980
AK80FL5
REV 01
740-031980
AK80NL9
BUILTIN
BUILTIN
REV 01
740-031980
AK80NG2
REV 01
740-031980
AK80KDU
REV 01
740-031980
AK80MG1
REV 01
740-031980
AK80MM0
REV 30
750-028467
ABBN0208
REV 10
711-029089
ABBJ1084
BUILTIN
BUILTIN
REV 01
740-030658
B11E04745
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-LRM
SFP+-10G-LRM
SFP+-10G-LRM
SFP+-10G-LRM
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
1391
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 14
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 15
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
1392
1
2
3
REV 01
REV 01
REV 01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
23
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
REV 01
REV 01
REV 01
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-028467
711-029089
BUILTIN
740-021308
740-031980
740-021308
740-021308
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
B11F01570
B11E04388
B11F01439
BUILTIN
B11E04739
B11F01869
B11F01675
B11F01901
BUILTIN
B11F01346
B11F01288
B11F01824
B11E04312
BUILTIN
B11E02811
B11E03847
B11F01495
B11F01265
YN2977
YP1856
BUILTIN
183363A00875
183363A00851
183363A00772
183363A00882
BUILTIN
183363A00735
183363A00169
183363A00726
183363A00077
BUILTIN
183363A00168
183363A00676
183363A00732
183363A00091
BUILTIN
183363A00725
183363A00642
183363A00871
183363A00853
ABBN6798
ABBK6556
BUILTIN
9ZDZ06A00055
183363A00239
AD0915E003K
AD0915E003A
BUILTIN
AK80MRC
AK80NL5
AK80NKN
AK80N3U
BUILTIN
AK80N1T
AJ808DJ
AK80NG4
AK80FND
BUILTIN
AK80FKQ
AK80NLT
AK80NKR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Xcvr
FPC 16
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 17
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 18
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
REV 01
REV 30
REV 10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
30
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
REV 01
REV 01
REV 01
740-031980
AK80LKM
750-028467
ABBN0270
711-029089
ABBJ0966
BUILTIN
BUILTIN
740-031980
AK80NL1
740-031980
AK80NXW
740-031980
AK80KD2
740-031980
AK80FMD
BUILTIN
BUILTIN
740-031980
AK80NKQ
740-031980
AK80MGH
740-031980
AK80N38
740-031980
AK80NL7
BUILTIN
BUILTIN
740-031980
AK80M5J
740-031980
AK80NKD
740-031980
AK80KCY
740-031980
AK80LHK
BUILTIN
BUILTIN
740-031980
AK80LEL
740-031980
AK80MBE
740-031980
AK80NLG
740-031980
AK80LFH
750-028467
ABBN6796
711-029089
ABBN7259
BUILTIN
BUILTIN
740-031980
B11K01856
740-031980
B11K01853
740-031980
B11K01863
740-031980
163363A02863
BUILTIN
BUILTIN
740-031980
163363A02668
740-031980
163363A02881
740-031980
163363A01671
740-031980
163363A02627
BUILTIN
BUILTIN
740-031980
163363A02725
740-031980
163363A02692
740-031980
163363A02730
740-031980
163363A03081
BUILTIN
BUILTIN
740-031980
163363A02736
740-031980
163363A02568
740-031980
163363A02747
740-031980
163363A02579
750-028467
ABBN0281
711-029089
ABBN0526
BUILTIN
BUILTIN
740-030658
B11F01326
740-030658
B11E03973
740-030658
B11E00950
740-030658
B11E00674
BUILTIN
BUILTIN
740-030658
B11E00775
740-030658
B11E04461
740-030658
B11E01074
740-030658
B11E02821
BUILTIN
BUILTIN
740-030658
B11E04501
740-030658
B11E00757
740-030658
B11F01623
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
1393
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
FPC 19
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
Xcvr
Xcvr
Xcvr
Xcvr
ADC 0
ADC 1
ADC 2
ADC 3
ADC 4
ADC 5
ADC 6
ADC 7
ADC 8
ADC 9
ADC 10
ADC 11
ADC 12
ADC 13
ADC 14
ADC 15
ADC 16
ADC 17
ADC 18
ADC 19
Fan Tray
Fan Tray
Fan Tray
Fan Tray
REV 01
0
1
2
3
REV
REV
REV
REV
REV
REV
01
01
01
01
32
10
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
01
01
01
01
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
13
13
13
13
13
13
13
07
07
07
13
13
13
13
13
13
13
13
13
11
04
04
04
04
0
1
2
3
740-030658
BUILTIN
740-030658
740-030658
740-030658
740-030658
750-028467
711-029089
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-021308
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
BUILTIN
740-031980
740-031980
740-031980
740-031980
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
B11E01022
BUILTIN
B11E04359
B11E02751
B11E02736
B11E01178
ABBN6813
ABBK6542
BUILTIN
AK80NA3
AK80NLF
AK80MRH
AK80KE4
BUILTIN
973152A00030
AK80L9H
AK80ME8
AK80NLR
BUILTIN
AK80NG1
AK80MCA
AK80LFC
AK80LEM
BUILTIN
AK80N9X
AK80LAC
AK80LF2
AK80N8T
ABBX5561
ABBX5546
ABBX5535
ABBX5552
ABBX5581
ABBX5545
ABBX5554
ABBV7194
ABBV7251
ABBV7202
ABBX5579
ABBX5548
ABBX5575
ABBX5539
ABBX5555
ABBX5557
ABBX5536
ABBX5559
ABBX5537
ABBW5685
ACAY0090
ACAY0088
ACAY0089
ACAY0108
SFP+-10G-USR
4x 10GE(LAN) SFP+
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
SFP+-10G-USR
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
172mm FanTray - 6
172mm FanTray - 6
172mm FanTray - 6
172mm FanTray - 6
Serial number
ABAB9384
ABBT8837
1E02224006G
Fans
Fans
Fans
Fans
1394
PSM 1
REV 01
PSM 2
REV 01
PSM 3
REV 01
PSM 4
REV 01
PSM 5
REV 01
PSM 6
REV 01
PSM 7
REV 01
PSM 8
REV 01
PSM 9
REV 03
PSM 10
REV 03
PSM 11
REV 03
PSM 12
REV 03
PSM 13
REV 03
PSM 15
REV 03
PDM 0
REV 01
PDM 1
REV 01
PDM 2
REV 01
Routing Engine 0 REV 02
Routing Engine 1 REV 02
CB 0
REV 08
CB 1
REV 04
SFB 0
REV 05
SFB 1
REV 05
SFB 2
REV 05
SFB 4
REV 05
SFB 5
REV 05
SFB 7
REV 05
FPC 0
REV 30
FPC 1
REV 30
FPC 2
REV 30
FPC 3
REV 32
FPC 4
REV 32
FPC 5
REV 32
FPC 6
REV 30
FPC 7
REV 32
FPC 8
REV 30
FPC 9
REV 32
FPC 10
REV 30
FPC 11
REV 32
FPC 12
REV 30
FPC 13
REV 30
FPC 14
REV 23
FPC 15
REV 32
FPC 16
REV 30
FPC 17
REV 32
FPC 18
REV 30
FPC 19
REV 32
ADC 0
REV 13
ADC 1
REV 13
ADC 2
REV 13
ADC 3
REV 13
ADC 4
REV 13
ADC 5
REV 13
ADC 6
REV 13
ADC 7
REV 07
ADC 8
REV 07
ADC 9
REV 07
ADC 10
REV 13
ADC 12
REV 13
ADC 13
REV 13
ADC 14
REV 13
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045050
740-045234
740-045234
740-045234
740-041821
740-041821
750-040257
750-040257
711-044466
711-044466
711-044466
711-044466
711-044466
711-044466
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-028467
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
1E022240053
1E02224004K
1E022240056
1E022240054
1E02224005H
1E02224006S
1E02224005M
1E022240062
1EDB2350095
1EDB235009L
1EDB2350092
1EDB23500AT
1EDB2350094
1EDB235008X
1E012150033
1E012150027
1E262250072
9009094138
9009089709
CAAB3482
ZT2864
ABBT2161
ABBT2159
ABBX3718
ABBT2160
ABBT2145
ABBT2163
ABBN0284
ABBN0308
ABBN0316
ABBN6832
ABBN6811
ABBN6791
ABBM4592
ABBN6810
ABBM4739
ABBN6827
ABBN0302
ABBN6790
ZM5111
ABBN0208
YN2977
ABBN6798
ABBN0270
ABBN6796
ABBN0281
ABBN6813
ABBX5561
ABBX5546
ABBX5535
ABBX5552
ABBX5581
ABBX5545
ABBX5554
ABBV7194
ABBV7251
ABBV7202
ABBX5579
ABBX5575
ABBX5539
ABBX5555
MX2000-PSM-HC-DC-S-A
MX2000-PSM-HC-DC-S-A
MX2000-PSM-HC-DC-S-A
MX2000-PSM-HC-DC-S-A
MX2000-PSM-HC-DC-S-A
MX2000-PSM-HC-DC-S-A
MX2000-PSM-HC-DC-S-A
MX2000-PSM-HC-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PSM-DC-S-A
MX2000-PDM-DC-S-A
RE-S-1800X4-16G-S
RE-S-1800X4-16G-S
750-040257
750-040257
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
1395
ADC
ADC
ADC
ADC
ADC
Fan
Fan
Fan
Fan
15
16
17
18
19
Tray
Tray
Tray
Tray
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
13
13
13
13
11
04
04
04
04
750-043596
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
ABBX5557
ABBX5536
ABBX5559
ABBX5537
ABBW5685
ACAY0090
ACAY0088
ACAY0089
ACAY0108
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
1396
MX2000-PDM-DC-S-A
RE-S-1800X4-16G-S
RE-S-1800X4-16G-S
750-040257
750-040257
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MX2000-SFB-S
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
FPC
FPC
FPC
FPC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
Fan
Fan
Fan
Fan
16
17
18
19
0
1
2
3
4
5
6
7
8
9
10
12
13
14
15
16
17
18
19
Tray
Tray
Tray
Tray
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
30
32
30
32
13
13
13
13
13
13
13
07
07
07
13
13
13
13
13
13
13
13
11
04
04
04
04
750-028467
750-028467
750-028467
750-028467
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
PROTOXCLEI
PROTOXCLEI
IPUCBA8CAA
IPUCBA8CAA
IPUCBA8CAA
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
IPUCBA8CAA
IPUCBA8CAA
PROTOXCLEI
PROTOXCLEI
IPUCBA8CAA
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
MPC-3D-16XGE-SFPP
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
Serial number
JN120BADBAFJ
ABAB9243
ABAB9399
ACAJ2541
ACAJ2194
ABCA8835
1EDB32403L5
Description
MX2020
Lower Backplane
Upper Backplane
Upper Power Midplane
Lower Power Midplane
Front Panel Display
DC 52V Power Supply
1EDB32403L3
1EDB32403KM
1EDB3130079
1EDB3130077
1EDB3130020
1EDB313009S
1EDB313008E
1EDB3130063
1EDB3130026
1EDB3130074
1397
PSM 14
REV
Module
PSM 15
REV
Module
PSM 16
REV
Module
PSM 17
REV
Module
PDM 0
REV
PDM 1
REV
PDM 2
REV
PDM 3
REV
Routing Engine 0 REV
Routing Engine 1 REV
CB 0
REV
CB 1
REV
SPMB 0
REV
SPMB 1
REV
SFB 0
REV
SFB 1
REV
SFB 2
REV
SFB 3
REV
SFB 4
REV
SFB 5
REV
SFB 6
REV
SFB 7
REV
FPC 0
REV
CPU
REV
PIC 0
Xcvr 0
REV
Xcvr 2
REV
Xcvr 3
REV
Xcvr 4
REV
Xcvr 5
REV
Xcvr 6
REV
Xcvr 7
REV
Xcvr 8
REV
Xcvr 9
REV
Xcvr 10
REV
Xcvr 11
REV
PIC 1
Xcvr 0
REV 01
Xcvr 1
REV
Xcvr 2
REV
Xcvr 3
REV
Xcvr 4
REV
Xcvr 5
REV
Xcvr 6
REV
Xcvr 7
REV
Xcvr 8
REV
Xcvr 9
REV
Xcvr 10
REV
Xcvr 11
REV
PIC 2
PIC 3
WAN MEZZ
REV
FPC 1
REV
CPU
REV
MIC 0
REV
PIC 0
Xcvr 0
REV
1398
01
740-050037
1EDB313009D
01
740-050037
1EDB3130024
01
740-050037
1EDB3130054
01
740-050037
1EDB3130080
03
03
03
03
02
02
23
23
02
02
06
06
06
06
06
06
06
06
39
09
740-045234
1EGA3170144
740-045234
1EGA3170158
740-045234
1EGA3170182
740-045234
1EGA3170207
740-041821
9009112112
740-041821
9009112087
750-040257
CABA2295
750-040257
CABE8379
711-041855
ABCE8851
711-041855
ABCE8839
711-044466
ABCD5001
711-044466
ABCD5034
711-044466
ABCH3899
711-044466
ABCD5020
711-044466
ABCD4975
711-044466
ABCH3881
711-044466
ABCD5026
711-044466
ABCD5032
750-045715
CACD1902
711-045719
CACB1933
BUILTIN
BUILTIN
01
740-031980
B11F00361
01
740-021308
19T511101854
01
740-021308
19T511100377
01
740-031980
ANT0878
01
740-021308
19T511100398
01
740-021308
AQ4363J
01
740-021308
19T511101377
01
740-031980
ANT072M
01
740-021308
AG90C7N
01
740-031980
AM30M09
01
740-031980
B10E01016
BUILTIN
BUILTIN
740-031980
B10L04151
01
740-021308
19T511101379
01
740-021308
AQ5036J
01
740-021308
AG90C4M
01
740-021308
19T511101104
01
740-021308
AQ502ZM
01
740-021308
AN10KY2
01
740-021308
AQ43G41
01
740-021308
AQ41F04
01
740-031980
AMS16N3
01
740-021308
AMH04Y3
01
740-021308
ANA093E
BUILTIN
BUILTIN
BUILTIN
BUILTIN
09
750-049136
CABN0410
11
750-045372
CABK8112
08
711-035209
CABJ6621
07
750-033307
CAAZ2897
BUILTIN
BUILTIN
01
740-021308
AQ501VK
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
FPC 2
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
Xcvr 3
PIC 3
FPC 3
CPU
MIC 0
PIC 0
Xcvr
Xcvr
PIC 1
Xcvr
QXM 0
QXM 1
FPC 4
CPU
PIC 0
PIC 1
Xcvr 0
PIC 2
PIC 3
Xcvr 0
FPC 5
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 3
1
2
3
4
5
6
7
8
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV 01
REV 17
REV 08
REV
REV
REV
REV
01
01
01
01
01
01
01
01
14
01
01
01
01
REV 01
REV 01
REV 01
REV 01
REV 05
REV 04
REV 28
0
1
REV 01
0
REV 06
REV 06
REV 18
REV 09
REV 01
REV 01
REV 35
REV 11
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
01
01
01
01
740-021308
740-021308
740-021308
740-021308
740-031980
740-021308
740-031980
740-031980
750-033196
BUILTIN
740-032166
750-037355
711-035209
BUILTIN
740-021308
740-031980
740-021308
740-021308
BUILTIN
740-035329
BUILTIN
740-031980
740-031980
740-031980
BUILTIN
750-044444
711-038484
750-028387
BUILTIN
NON-JNPR
740-011571
BUILTIN
NON-JNPR
711-028408
711-028408
750-046005
711-045719
BUILTIN
BUILTIN
740-046563
BUILTIN
BUILTIN
740-049775
750-028467
711-029089
BUILTIN
740-021308
740-021308
740-021308
740-021308
BUILTIN
740-021308
740-021308
740-021308
740-021308
BUILTIN
740-021308
740-021308
740-021308
740-021308
BUILTIN
AQ501YC
AQ43HJF
AQ43H8D
19T511100370
153363A00763
APH2LXB
AMC0LVV
B11F00230
CAAP1390
BUILTIN
XB11F000M
CAAS5826
CAAR3986
BUILTIN
T09F43722
ALP0KXF
AQ502FG
AQ502T7
BUILTIN
X12J00571
BUILTIN
AJ71KEH
B11E01355
B11F00249
BUILTIN
CAAY9920
CAAW3639
CAAX1083
BUILTIN
CC07BK05B
C728XJ00U
BUILTIN
T12L92339
CAAW4915
CAAW4894
CACH5661
CACF2880
BUILTIN
BUILTIN
XD16FC03Y
BUILTIN
BUILTIN
J13K72997
CAAR2623
CAAR0491
BUILTIN
AQ5027T
AQ502J0
AQ5027S
AQ501Y7
BUILTIN
AQ501YB
AQ503EB
AQ43HJH
AQ43J0Y
BUILTIN
AQ50352
AQ501X6
AQ502NV
AQ502ZJ
BUILTIN
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CXP
1X100GE CXP
CFP2-100G-SR10
MPC4E 3D 2CGE+8XGE
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
MPCE Type 2 3D P
MPCE PMB 2G
3D 4x 10GE XFP
2x 10GE XFP
XFP-10G-SR
XFP-10G-SR
2x 10GE XFP
XFP-10G-SR
MPC QXM
MPC QXM
MPC5E 3D Q 2CGE+4XGE
RMPC PMB
2X10GE SFPP OTN
1X100GE CFP2 OTN
CFP2-100G-SR10
2X10GE SFPP OTN
1X100GE CFP2 OTN
CFP2-100G-LR4-D
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
1399
Xcvr 0
Xcvr 1
Xcvr 2
FPC 9
CPU
MIC 0
PIC 0
Xcvr 0
Xcvr 1
MIC 1
PIC 1
Xcvr 0
Xcvr 1
XLM 0
XLM 1
FPC 10
CPU
MIC 0
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 9
Xcvr 10
Xcvr 11
Xcvr 12
Xcvr 13
Xcvr 14
Xcvr 15
Xcvr 16
Xcvr 17
Xcvr 18
Xcvr 19
Xcvr 20
Xcvr 21
Xcvr 22
Xcvr 23
MIC 1
PIC 1
Xcvr 3
XLM 0
XLM 1
FPC 17
CPU
MIC 0
PIC 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 9
1400
REV
REV
REV
REV
REV
REV
01
01
01
30
09
05
740-021308
AQ502H4
740-021308
AQ43HJK
740-031980
AJ30CU7
750-044130
ABCF5773
711-045719
ABCF1270
750-049457
ABCD7829
BUILTIN
BUILTIN
NON-JNPR
FE13F000K
REV 01
740-048813
XD32FE017
REV 07
750-049457
ABCK2812
BUILTIN
BUILTIN
REV 01
740-048813
XD32FE018
NON-JNPR
FE13F000E
REV 05.2.00 711-046638 ABCF5915
REV 05.2.00 711-046638 ABCF5916
REV 36
750-044130
ABCS8602
REV 09
711-045719
ABCS8779
REV 06
750-049979
ABCK2656
BUILTIN
BUILTIN
REV 01
740-021308
AQ43J08
REV 01
740-021308
AQE1Y2E
REV 01
740-021308
AQE1UW4
REV 01
740-021308
AQE1MQF
REV 01
740-021308
AQG0MN1
REV 01
740-021308
AQE1L9M
REV 01
740-021308
AQG0MPD
REV 01
740-021308
AQE1Y2B
REV 01
740-021308
AQG0LT5
REV 01
740-021308
AQD2ET4
REV 01
740-021308
AQG0MPC
REV 01
740-021308
AQG0M63
REV 01
740-021308
AQG0LT1
REV 01
740-021308
AQG0M4L
REV 01
740-021308
AQG0LS7
REV 01
740-021308
AQE1MQB
REV 01
740-021308
AQG0LZP
REV 01
740-021308
AQE1LU9
REV 01
740-021308
AQG0MRZ
REV 01
740-021308
AQE1MQ9
REV 01
740-021308
AQG0LRX
REV 01
740-021308
AQE1UWD
REV 01
740-021308
AQG0LT4
REV 01
740-021308
AQE1MQL
REV 12
750-050008
ABCK5372
BUILTIN
BUILTIN
REV 01
740-046563
XD16FC02Z
REV 07.2.00 711-046638 ABCK3481
REV 07.2.00 711-046638 ABCK4725
REV 28
750-044130
ABBZ3873
REV 08
711-045719
ABBZ3770
REV 11
750-046535
ABCC7731
BUILTIN
BUILTIN
REV 01
740-021308
APK0543
REV 01
740-031980
B10G01119
REV 01
740-021308
AQ502SX
REV 01
740-021308
AQ43H84
REV 01
740-021308
AQ501TB
REV 01
740-021308
AQ502JZ
REV 01
740-021308
AQ502SC
REV 01
740-021308
AQ502JW
REV 01
740-021308
AQ502RM
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
MPC6E 3D
RMPC PMB
2X100GE CFP2 OTN
2X100GE CFP2 OTN
CFP2-100G-SR10
CFP2-100G-LR-D
2X100GE CFP2 OTN
2X100GE CFP2 OTN
CFP2-100G-SR10
CFP2-100G-LR4-D
MPC6E XL
MPC6E XL
MPC6E 3D
RMPC PMB
24X10GE SFPP OTN
24X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
4X100GE CXP
4X100GE CXP
CFP2-100G-SR10
MPC6E XL
MPC6E XL
MPC6E 3D
RMPC PMB
24X10GE SFPP
24X10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Xcvr 10
REV 01
740-031980
AHK013B
Xcvr 11
REV 01
740-021308
AQG0MRT
Xcvr 13
REV 01
740-031980
AMC0JTC
Xcvr 14
REV 01
740-021308
ANA0MQ0
Xcvr 15
REV 01
740-021308
AQ502GS
Xcvr 16
REV 01
740-021308
AQG0M0J
Xcvr 17
REV 01
740-021308
AQG0MUR
Xcvr 18
REV 01
740-021308
AQG0MRR
Xcvr 19
REV 01
740-021308
AQG0M0F
Xcvr 20
REV 01
740-021308
AQ50312
Xcvr 21
REV 01
740-021308
AQ5032U
Xcvr 22
REV 01
740-021308
APE17B5
Xcvr 23
REV 01
740-021309
91D104A00011
MIC 1
REV 03
750-050008
ABCC4522
PIC 1
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-046563
XD16FC02U
Xcvr 1
REV 01
740-046563
XC42FC03K
Xcvr 2
REV 01
740-046563
XC42FC01Z
Xcvr 3
REV 01
740-046563
XC42FC02U
XLM 0
REV 04.2.00 711-046638 ABBZ3779
XLM 1
REV 04.2.00 711-046638 ABBZ3780
FPC 18
REV 39
750-045715
CACD1910
CPU
REV 09
711-045719
CACD1817
PIC 0
BUILTIN
BUILTIN
PIC 1
BUILTIN
BUILTIN
PIC 2
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-046565
QD130194
Xcvr 1
REV 01
740-046565
QD130193
Xcvr 2
REV 01
740-046565
QD130196
PIC 3
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-046565
QD130191
Xcvr 1
REV 01
740-046565
QD130198
Xcvr 2
REV 01
740-046565
QD130192
WAN MEZZ
REV 09
750-049136
CABN0411
FPC 19
REV 39
750-045715
CACD1908
CPU
REV 09
711-045719
CACD1820
PIC 0
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-021308
AQA0EXJ
Xcvr 1
REV 01
740-021308
AQG0M6D
Xcvr 2
REV 01
740-021308
AQG0LW7
Xcvr 3
REV 01
740-021308
AQA0JKB
Xcvr 4
REV 01
740-021308
AQG0MTM
Xcvr 5
REV 01
740-021308
AQA07NE
Xcvr 6
REV 01
740-021308
AQG0M41
Xcvr 7
REV 01
740-021308
AQG0MU7
Xcvr 8
REV 01
740-021308
AQG0MUG
Xcvr 9
REV 01
740-021308
AQG0MMX
Xcvr 10
REV 01
740-021308
AQG0M5K
Xcvr 11
REV 01
740-021308
AQG0LVZ
PIC 1
BUILTIN
BUILTIN
PIC 2
BUILTIN
BUILTIN
PIC 3
BUILTIN
BUILTIN
Xcvr 0
REV 01
740-046565
QD130242
Xcvr 1
REV 01
740-046565
QD130245
Xcvr 2
REV 01
740-046565
QD130613
WAN MEZZ
REV 09
750-049136
CABN0418
ADC 0
REV 17
750-043596
ABCD5378
ADC 1
REV 17
750-043596
ABCD5465
ADC 2
REV 17
750-043596
ABCD5431
ADC 3
REV 17
750-043596
ABCD5356
ADC 4
REV 02
750-043596
ZW1545
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-LR
4X100GE CXP
4X100GE CXP
CFP2-100G-SR10
CFP2-100G-SR10
CFP2-100G-SR10
CFP2-100G-SR10
MPC6E XL
MPC6E XL
MPC5E 3D Q 24XGE+6XLGE
RMPC PMB
12X10GE SFPP OTN
12X10GE SFPP OTN
3X40GE QSFPP
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
3X40GE QSFPP
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
MPC5E 24XGE OTN Mezz
MPC5E 3D Q 24XGE+6XLGE
RMPC PMB
12X10GE SFPP OTN
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
12X10GE SFPP OTN
3X40GE QSFPP
3X40GE QSFPP
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
MPC5E 24XGE OTN Mezz
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
1401
ADC
ADC
ADC
Fan
Fan
Fan
Fan
5
18
19
Tray
Tray
Tray
Tray
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
17
17
01
06
06
06
06
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
ABCD5517
ABCD5535
ZV4127
ACAY0791
ACAY0788
ACAY0755
ACAY0441
Adapter Card
Adapter Card
Adapter Card
172mm FanTray
172mm FanTray
172mm FanTray
172mm FanTray
6
6
6
6
Fans
Fans
Fans
Fans
show chassis hardware detail (MX2020 Router with MPC5EQ and MPC6E)
user@host>show chassis hardware detail
Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN120BADBAFJ
MX2020
Midplane
REV 51
750-040240
ABAB9243
Lower Backplane
Midplane 1
REV 04
711-032386
ABAB9399
Upper Backplane
PMP 1
REV 05
711-032428
ACAJ2541
Upper Power Midplane
PMP 0
REV 04
711-032426
ACAJ2194
Lower Power Midplane
FPM Board
REV 13
760-040242
ABCA8835
Front Panel Display
PSM 0
REV 01
740-050037
1EDB32403L5
DC 52V Power Supply
Module
PSM 1
REV 01
740-050037
1EDB32403L3
DC 52V Power Supply
Module
PSM 2
REV 01
740-050037
1EDB32403KM
DC 52V Power Supply
Module
PSM 3
REV 01
740-050037
1EDB3130079
DC 52V Power Supply
Module
PSM 4
REV 01
740-050037
1EDB3130077
DC 52V Power Supply
Module
PSM 5
REV 01
740-050037
1EDB3130020
DC 52V Power Supply
Module
PSM 6
REV 01
740-050037
1EDB313009S
DC 52V Power Supply
Module
PSM 7
REV 01
740-050037
1EDB313008E
DC 52V Power Supply
Module
PSM 8
REV 01
740-050037
1EDB3130063
DC 52V Power Supply
Module
PSM 12
REV 01
740-050037
1EDB3130026
DC 52V Power Supply
Module
PSM 13
REV 01
740-050037
1EDB3130074
DC 52V Power Supply
Module
PSM 14
REV 01
740-050037
1EDB313009D
DC 52V Power Supply
Module
PSM 15
REV 01
740-050037
1EDB3130024
DC 52V Power Supply
Module
PSM 16
REV 01
740-050037
1EDB3130054
DC 52V Power Supply
Module
PSM 17
REV 01
740-050037
1EDB3130080
DC 52V Power Supply
Module
PDM 0
REV 03
740-045234
1EGA3170144
DC Power Dist Module
PDM 1
REV 03
740-045234
1EGA3170158
DC Power Dist Module
PDM 2
REV 03
740-045234
1EGA3170182
DC Power Dist Module
PDM 3
REV 03
740-045234
1EGA3170207
DC Power Dist Module
Routing Engine 0 REV 02
740-041821
9009112112
RE-S-1800x4
ad0
3998 MB Virtium - TuffDrive VCF P1T0200274310822 113 Compact Flash
ad1
30533 MB UGB94BPH32H0S1-KCI
11000031656
Disk 1
usb0 (addr 1) EHCI root hub 0
Intel
uhub0
usb0 (addr 2) product 0x0020 32
vendor 0x8087
uhub1
DIMM 0
SGU04G72H1BD2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 1
SGU04G72H1BD2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
DIMM 2
SGU04G72H1BD2SA-BB DIE REV-52 PCB REV-54 MFR ID-ce80
1402
DIMM 3
Routing Engine 1
ad0
3998 MB
ad1
30533 MB
CB 0
CB 1
SPMB 0
SPMB 1
FPC 0
CPU
FPC 1
CPU
FPC 2
CPU
FPC 3
CPU
FPC 4
CPU
FPC 5
CPU
FPC 9
CPU
FPC 10
CPU
FPC 17
CPU
FPC 18
CPU
FPC 19
CPU
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
REV 39
750-045715
CACD1902
MPC5E 3D Q 24XGE+6XLGE
REV 11
750-045372
CABK8112
MPCE Type 3 3D
REV 17
750-037355
CAAS5826
MPC4E 3D 2CGE+8XGE
REV 05
750-044444
CAAY9920
MPCE Type 2 3D P
REV 18
750-046005
CACH5661
MPC5E 3D Q 2CGE+4XGE
REV 35
750-028467
CAAR2623
REV 30
750-044130
ABCF5773
MPC6E 3D
REV 36
750-044130
ABCS8602
MPC6E 3D
REV 28
750-044130
ABBZ3873
MPC6E 3D
REV 39
750-045715
CACD1910
MPC5E 3D Q 24XGE+6XLGE
REV 39
750-045715
CACD1908
MPC5E 3D Q 24XGE+6XLGE
REV
REV
REV
REV
760-046960
760-046960
760-046960
760-046960
ACAY0791
ACAY0788
ACAY0755
ACAY0441
172mm
172mm
172mm
172mm
06
06
06
06
FanTray
FanTray
FanTray
FanTray
6
6
6
6
Fans
Fans
Fans
Fans
show chassis hardware extensive (MX2020 Router with MPC5EQ and MPC6E)
Hardware inventory:
Item
Version
Chassis
Jedec Code:
0x7fb0
Part number
Serial number
Description
JN120BADBAFJ
MX2020
EEPROM Version:
0x02
S/N:
JN120BADBAFJ
Assembly Version: 00.00
Assembly Flags:
0x00
00 00 00 00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00
00 00
00 00
00 00
00 00
00 00
00 00
00 00
00 00
Lower Backplane
0x02
ABAB9243
01.51
0x00
1403
Version:
REV 51
CLEI Code:
ID: Lower Backplane
FRU Model Number:
Board Information Record:
Address 0x00: ad 01 10 00 4c 96 14 72 30 08 ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 22 01 33 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 34 30 32
Address 0x20: 53 2f 4e 20 41 42 41 42 39 32 34 33
Address 0x30: dd ff ff ff ad 01 10 00 4c 96 14 72
Address 0x40: ff ff ff ff 01 49 50 4d 55 37 31 30
Address 0x50: 48 41 53 2d 42 50 2d 4d 58 32 30 32
Address 0x60: 00 00 00 00 00 00 41 00 00 ff ff ff
Address 0x70: ff ff ff d3 ff ff ff ff ff ff ff ff
Midplane 1
REV 04
711-032386
ABAB9399
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-032386
S/N:
Assembly ID: 0x0b23
Assembly Version:
Date:
10-22-2012
Assembly Flags:
Version:
REV 04
ID: Upper Backplane
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 fe 0b 23 01 04 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 32 33
Address 0x20: 53 2f 4e 20 41 42 41 42 39 33 39 39
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff
PMP 1
REV 05
711-032428
ACAJ2541
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-032428
S/N:
Assembly ID: 0x045c
Assembly Version:
Date:
04-26-2013
Assembly Flags:
Version:
REV 05
ID: Upper Power Midplane
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 5c 01 05 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 32 34
Address 0x20: 53 2f 4e 20 41 43 41 4a 32 35 34 31
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff
PMP 0
REV 04
711-032426
ACAJ2194
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-032426
S/N:
Assembly ID: 0x045d
Assembly Version:
Date:
01-29-2013
Assembly Flags:
Version:
REV 04
ID: Lower Power Midplane
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 04 5d 01 04 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 32 34
1404
IPMU710ARA
CHAS-BP-MX2020-S
ff ff ff ff
35
34
00
30
41
30
ff
ff
31
30
1e
08
52
2d
ff
ff
00 00
00 00
05 07
ff ff
41 43
53 00
ff ff
ff ff
Upper Backplane
0x01
ABAB9399
01.04
0x00
ff ff ff ff
30
38
00
ff
ff
ff
ff
ff
34
36
16
ff
ff
ff
ff
ff
00 00
00 00
0a 07
ff ff
ff ff
ff ff
ff ff
ff ff
Upper Power Midplane
0x01
ACAJ2541
01.05
0x00
ff ff ff ff
30
32
00
ff
ff
ff
ff
ff
35
38
1a
ff
ff
ff
ff
ff
00 00
00 00
04 07
ff ff
ff ff
ff ff
ff ff
ff ff
Lower Power Midplane
0x01
ACAJ2194
01.04
0x00
ff ff ff ff
30 34 00 00
32 36 00 00
Address 0x20: 53 2f 4e 20 41 43 41 4a 32 31 39 34
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff ff ff ff ff ff ff ff ff
FPM Board
REV 13
760-040242
ABCA8835
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
760-040242
S/N:
Assembly ID: 0x0b24
Assembly Version:
Date:
04-13-2013
Assembly Flags:
Version:
REV 13
CLEI Code:
ID: Front Panel Display
FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 24 01 0d 52 45 56 20
Address 0x10: 00 00 00 00 37 36 30 2d 30 34 30 32
Address 0x20: 53 2f 4e 20 41 42 43 41 38 38 33 35
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 4d 59 41 45 35
Address 0x50: 58 32 30 32 30 2d 43 52 41 46 54 2d
Address 0x60: 00 00 00 00 00 00 41 00 00 ff ff ff
Address 0x70: ff ff ff 95 ff ff ff ff ff ff ff ff
PSM 0
REV 01
740-050037
1EDB32403L5
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
06-21-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 34 30 33 4c 35 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 1
REV 01
740-050037
1EDB32403L3
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
06-21-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 34 30 33 4c 33 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
00
ff
ff
ff
ff
ff
1d
ff
ff
ff
ff
ff
01 07
ff ff
ff ff
ff ff
ff ff
ff ff
Front Panel Display
0x02
ABCA8835
01.13
0x00
IPMYAE5JRA
MX2020-CRAFT-S
ff ff ff ff
31
34
00
ff
4a
53
ff
ff
33
32
0d
ff
52
00
ff
ff
00 00
00 00
04 07
ff ff
41 4d
00 00
ff ff
ff ff
DC 52V Power Supply
0x02
1EDB32403L5
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
15
ff
41
53
ff
00
00 00
00 00
06 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB32403L3
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
31
37
15
ff
41
53
ff
00
00
06
ff
41
00
ff
00
00
07
ff
4d
00
ff
1405
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 2
REV 01
740-050037
1EDB32403KM
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
06-21-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 32 34 30 33 4b 4d 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 3
REV 01
740-050037
1EDB3130079
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-16-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 31 33 30 30 37 39 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 4
REV 01
740-050037
1EDB3130077
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-17-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 31 33 30 30 37 37 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 5
REV 01
740-050037
1EDB3130020
Module
Jedec Code:
0x7fb0
EEPROM Version:
1406
00 00 00 00
DC 52V Power Supply
0x02
1EDB32403KM
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
15
ff
41
53
ff
00
00 00
00 00
06 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB3130079
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
10
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB3130077
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
11
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-16-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 31 33 30 30 32 30 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 6
REV 01
740-050037
1EDB313009S
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-17-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 31 33 30 30 39 53 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 7
REV 01
740-050037
1EDB313008E
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-17-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 31 33 30 30 38 45 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 8
REV 01
740-050037
1EDB3130063
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-17-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
1EDB3130020
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
10
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB313009S
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
11
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB313008E
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
11
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB3130063
01.01
0x00
IPUPAKRKAA
1407
1408
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
11
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB3130026
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
10
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB3130074
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30
33
00
ff
4b
2d
ff
00
31
37
11
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB313009D
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 34 30 2d 30 35 30 30
Address 0x20: 31 45 44 42 33 31 33 30 30 39 44 00
Address 0x30: dd ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 49 50 55 50 41 4b 52
Address 0x50: 58 32 30 30 30 2d 50 53 4d 2d 44 43
Address 0x60: 00 00 00 00 00 00 31 30 31 ff ff ff
Address 0x70: ff ff ff 2a 00 00 00 00 00 00 00 00
PSM 15
REV 01
740-050037
1EDB3130024
Module
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
740-050037
S/N:
Assembly ID: 0x0478
Assembly Version:
Date:
05-16-2013
Assembly Flags:
Version:
REV 01
CLEI Code:
ID: DC 52V Power Supply Module FRU Model Number:
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 04 78 01 01 52 45 56 20
...
30
33
00
ff
4b
2d
ff
00
31
37
11
ff
41
53
ff
00
00 00
00 00
05 07
ff ff
41 4d
00 00
ff ff
00 00
DC 52V Power Supply
0x02
1EDB3130024
01.01
0x00
IPUPAKRKAA
MX2000-PSM-DC-S
ff ff ff ff
30 31 00 00
show chassis hardware models (MX2020 Routers with MPC5EQ and MPC6E)
user@host> show chassis hardware models
Hardware inventory:
Item
Version Part number
Midplane
REV 51
750-040240
FPM Board
REV 13
760-040242
PSM 0
REV 01
740-050037
PSM 1
REV 01
740-050037
PSM 2
REV 01
740-050037
PSM 3
REV 01
740-050037
PSM 4
REV 01
740-050037
PSM 5
REV 01
740-050037
PSM 6
REV 01
740-050037
PSM 7
REV 01
740-050037
PSM 8
REV 01
740-050037
PSM 12
REV 01
740-050037
PSM 13
REV 01
740-050037
PSM 14
REV 01
740-050037
PSM 15
REV 01
740-050037
PSM 16
REV 01
740-050037
PSM 17
REV 01
740-050037
PDM 0
REV 03
740-045234
PDM 1
REV 03
740-045234
PDM 2
REV 03
740-045234
PDM 3
REV 03
740-045234
Routing Engine 0 REV 02
740-041821
Routing Engine 1 REV 02
740-041821
CB 0
REV 23
750-040257
CB 1
REV 23
750-040257
SFB 0
REV 06
711-044466
SFB 1
REV 06
711-044466
SFB 2
REV 06
711-044466
SFB 3
REV 06
711-044466
SFB 4
REV 06
711-044466
SFB 5
REV 06
711-044466
SFB 6
REV 06
711-044466
SFB 7
REV 06
711-044466
FPC 0
REV 39
750-045715
Serial number
ABAB9243
ABCA8835
1EDB32403L5
1EDB32403L3
1EDB32403KM
1EDB3130079
1EDB3130077
1EDB3130020
1EDB313009S
1EDB313008E
1EDB3130063
1EDB3130026
1EDB3130074
1EDB313009D
1EDB3130024
1EDB3130054
1EDB3130080
1EGA3170144
1EGA3170158
1EGA3170182
1EGA3170207
9009112112
9009112087
CABA2295
CABE8379
ABCD5001
ABCD5034
ABCH3899
ABCD5020
ABCD4975
ABCH3881
ABCD5026
ABCD5032
CACD1902
1409
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
FPC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
ADC
Fan
Fan
Fan
Fan
1
2
3
4
5
9
10
17
18
19
0
1
2
3
4
5
18
19
Tray
Tray
Tray
Tray
0
1
2
3
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
11
17
05
18
35
30
36
28
39
39
17
17
17
17
02
17
17
01
06
06
06
06
750-045372
750-037355
750-044444
750-046005
750-028467
750-044130
750-044130
750-044130
750-045715
750-045715
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
CABK8112
CAAS5826
CAAY9920
CACH5661
CAAR2623
ABCF5773
ABCS8602
ABBZ3873
CACD1910
CACD1908
ABCD5378
ABCD5465
ABCD5431
ABCD5356
ZW1545
ABCD5517
ABCD5535
ZV4127
ACAY0791
ACAY0788
ACAY0755
ACAY0441
MX-MPC3E-3D
MPC4E-3D-2CGE-8XGE
MX-MPC2E-3D-P
PROTO-ASSEMBLY
MPC-3D-16XGE-SFPP
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
750-043596
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
750-043596
MX2000-FANTRAY-S
MX2000-FANTRAY-S
MX2000-FANTRAY-S
MX2000-FANTRAY-S
show chassis hardware clei-models (MX2020 Router with MPC5EQ and MPC6E)
user@host> show chassis hardware clei-models
Hardware inventory:
Item
Version Part number CLEI code
Midplane
REV 51
750-040240
IPMU710ARA
FPM Board
REV 13
760-040242
IPMYAE5JRA
PSM 0
REV 01
740-050037
IPUPAKRKAA
PSM 1
REV 01
740-050037
IPUPAKRKAA
PSM 2
REV 01
740-050037
IPUPAKRKAA
PSM 3
REV 01
740-050037
IPUPAKRKAA
PSM 4
REV 01
740-050037
IPUPAKRKAA
PSM 5
REV 01
740-050037
IPUPAKRKAA
PSM 6
REV 01
740-050037
IPUPAKRKAA
PSM 7
REV 01
740-050037
IPUPAKRKAA
PSM 8
REV 01
740-050037
IPUPAKRKAA
PSM 12
REV 01
740-050037
IPUPAKRKAA
PSM 13
REV 01
740-050037
IPUPAKRKAA
PSM 14
REV 01
740-050037
IPUPAKRKAA
PSM 15
REV 01
740-050037
IPUPAKRKAA
PSM 16
REV 01
740-050037
IPUPAKRKAA
PSM 17
REV 01
740-050037
IPUPAKRKAA
PDM 0
REV 03
740-045234
IPUPAJSKAA
PDM 1
REV 03
740-045234
IPUPAJSKAA
PDM 2
REV 03
740-045234
IPUPAJSKAA
PDM 3
REV 03
740-045234
IPUPAJSKAA
CB 0
REV 23
750-040257
IPUCBA7CTA
CB 1
REV 23
750-040257
IPUCBA7CTA
SFB 0
REV 06
711-044466
IPUCBA6CAA
SFB 1
REV 06
711-044466
IPUCBA6CAA
SFB 2
REV 06
711-044466
IPUCBA6CAA
SFB 3
REV 06
711-044466
IPUCBA6CAA
SFB 4
REV 06
711-044466
IPUCBA6CAA
SFB 5
REV 06
711-044466
IPUCBA6CAA
SFB 6
REV 06
711-044466
IPUCBA6CAA
SFB 7
REV 06
711-044466
IPUCBA6CAA
FPC 0
REV 39
750-045715
PROTOXCLEI
FPC 1
REV 11
750-045372
COUIBBNBAA
1410
FPC 2
FPC 3
MIC 0
FPC 4
FPC 5
FPC 9
MIC 0
FPC 10
MIC 0
MIC 1
FPC 17
MIC 1
FPC 18
FPC 19
ADC 0
ADC 1
ADC 2
ADC 3
ADC 4
ADC 5
ADC 18
ADC 19
Fan Tray
Fan Tray
Fan Tray
Fan Tray
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
0
1
2
3
17
05
28
18
35
30
05
36
06
12
28
03
39
39
17
17
17
17
02
17
17
01
06
06
06
06
750-037355
750-044444
750-028387
750-046005
750-028467
750-044130
750-049457
750-044130
750-049979
750-050008
750-044130
750-050008
750-045715
750-045715
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
760-046960
760-046960
IPU3A4DHAA
COUIBBGBAA
COUIA16BAA
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
IPUCBA8CAA
IPUCBA8CAA
IPUCBA8CAA
IPUCBA8CAA
PROTOXCLEI
IPUCBA8CAA
IPUCBA8CAA
PROTOXCLEI
IPUCBA5CAA
IPUCBA5CAA
IPUCBA5CAA
IPUCBA5CAA
MPC4E-3D-2CGE-8XGE
MX-MPC2E-3D-P
MIC-3D-4XGE-XFP
PROTO-ASSEMBLY
MPC-3D-16XGE-SFPP
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
PROTO-ASSEMBLY
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
750-043596
MX2000-LC-ADAPTER
MX2000-LC-ADAPTER
750-043596
MX2000-FANTRAY-S
MX2000-FANTRAY-S
MX2000-FANTRAY-S
MX2000-FANTRAY-S
Serial number
JN115736EAFC
ABAA5038
ABBA2758
QCS0937C07K
Description
MX240
MX240 Backplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
QCS0939C04X
PS 1.2-1.7kW; 100-240V
QCS0937C06B
PS 1.2-1.7kW; 100-240V
QCS0937C07U
PS 1.2-1.7kW; 100-240V
1
2
3
4
5
6
REV
REV
REV
REV
9009042291
9009042266
ABBC1435
ABBC1497
YH9612
RE-S-2000
RE-S-2000
MX SCB
MX SCB
MPC Type 2 3D Q
MPC PMB 2G
ZP7062
BUILTIN
NON-JNPR
23393-00492
NON-JNPR
23393-00500
NON-JNPR
23393-00912
01
740-015638
22216-00575
01
740-015638
24145-00110
01
740-015638
24145-00016
01
740-015638
24145-00175
2xOC12/8xOC3 CC-CE
2xOC12/8xOC3 CC-CE
UNKNOWN
UNKNOWN
UNKNOWN
Load SFP
Load SFP
Load SFP
Load SFP
1411
Xcvr 7
QXM 0
QXM 1
Fan Tray 0
REV 05
REV 05
REV 01
NON-JNPR
711-028408
711-028408
710-021113
23393-00627
YF4681
YF4817
XL3645
UNKNOWN
MPC QXM
MPC QXM
MX240 Fan Tray
show chassis hardware (MX240, MX480, MX960 routers with Application Services Modular Line Card)
user@host>show chassis hardware
Hardware inventory:
Item
Version Part number Serial number
Chassis
JN11D969BAFA
Midplane
REV 03
710-013698
ACAA2362
FPM Board
REV 03
710-014974
ZR0639
PDM
Rev 03
740-013110
QCS152250SX
PEM 0
Rev 10
740-013683
QCS1512718W
PEM 1
Rev 10
740-013683
QCS1512702Y
Routing Engine 0 REV 15
740-013063
9012024667
Routing Engine 1 REV 15
740-013063
9012024649
CB 0
REV 14
750-031391
ZJ7749
CB 1
REV 14
750-031391
ZJ7750
CB 2
REV 14
750-031391
ZY9233
FPC 0
REV 17
750-031089
YR7434
CPU
FPC 1
REV 11
750-037207
ZW9727
CPU
REV 04
711-038173
ZW4817
MIC 0
REV 01
750-037214
ZH3764
PIC 0
BUILTIN
BUILTIN
MIC 1
REV 01
711-028408
JZ9200
PIC 2
BUILTIN
BUILTIN
FPC 4
REV 30
750-028467
ABBN0232
CPU
FPC 5
REV 04
750-037207
ZK9074
CPU
Fan Tray 0
REV 05
740-014971
VT5683
Fan Tray 1
REV 05
740-014971
VT5684
Description
MX960
MX960 Backplane
Front Panel Display
Power Distribution Module
DC Power Entry Module
DC Power Entry Module
RE-S-2000
RE-S-2000
Enhanced MX SCB
Enhanced MX SCB
Enhanced MX SCB
MPC Type 2 3D
AS-MCC
AS-MCC-PMB
AS-MSC
AS-MSC
AS-MXC
AS-MXC
MPC 3D 16x 10GE
AS-MCC
Fan Tray
Fan Tray
show chassis hardware extensive (MX240, MX480, MX960 routers with Application Services Modular Line
Card)
user@host> show chassis hardware extensive
ID: AS-MCC
FRU Model Number: 750-037207
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 37 01 0b 52 45 56 20 31 31 00 00
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32 30 37 00 00
Address 0x20: 53 2f 4e 20 5a 57 39 37 32 37 00 00 00 11 02 07
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43 4c 45 49 37
Address 0x50: 35 30 2d 30 33 37 32 30 37 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 31 31 00 ff ff ff ff ff ff ff
Address 0x70: ff ff ff 5e ff ff ff ff ff ff ff ff ff ff ff ff
CPU
REV 04
711-038173
ZW4817
AS-MCC-PMB
Jedec Code:
0x7fb0
EEPROM Version:
0x02
P/N:
711-038173
S/N:
ZW4817
Assembly ID: 0x0b38
Assembly Version: 01.04
Date:
12-30-2011
Assembly Flags:
0x00
Version:
REV 04
ID: AS-MCC-PMB
Board Information Record:
1412
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x00: 7f b0 02 ff 0b 38 01 04 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 38 31
Address 0x20: 53 2f 4e 20 5a 57 34 38 31 37 00 00
Address 0x30: db ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 50 52 4f 54 4f 58 43
Address 0x50: 31 31 2d 30 33 38 31 37 33 00 00 00
Address 0x60: 00 00 00 00 00 00 30 34 00 ff ff ff
Address 0x70: ff ff ff 60 00 00 00 00 00 00 00 00
MIC 0
REV 01
750-037214
ZH3764
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037214
S/N:
Assembly ID: 0x0a44
Assembly Version:
Date:
07-04-2011
Assembly Flags:
Version:
REV 01
ID: AS-MSC
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x00: 7f b0 02 ff 0a 44 01 01 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32
Address 0x20: 53 2f 4e 20 5a 48 33 37 36 34 00 00
Address 0x30: db ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 00 00 00 00 00 00 00
Address 0x50: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x60: 00 00 00 00 00 00 00 00 00 ff ff ff
Address 0x70: ff ff ff f6 c0 03 e1 bc 00 00 00 00
PIC 0
BUILTIN
BUILTIN
FPC 4
REV 30
750-028467
ABBN0232
Jedec Code:
0x7fb0
EEPROM Version:
ff
30
37
00
ff
4c
00
ff
00
ff
34
33
1e
ff
45
00
ff
00
ff ff
00 00
00 00
0c 07
ff ff
49 37
00 00
ff ff
00 00
AS-MSC
0x02
ZH3764
01.01
0x00
ff
30
31
00
ff
00
00
ff
00
ff
31
34
04
ff
00
00
ff
00
0x01
Serial number
JN10FF57BAFB
Good
KG2066
QCS081590BJ
Description
MX480
MX480 Midplane
Front Panel Display
PS 1.2-1.7kW; 100-240V
QCS0815908Z
PS 1.2-1.7kW; 100-240V
QCS1001U001
PS 1.4-2.52kW; 90-264V
9009089502
9009089624
YE8506
ZK8265
ZT0638
ZK3187
BUILTIN
BUILTIN
BUILTIN
BUILTIN
CAAB1144
CAAB1278
BUILTIN
B11E01439
B11D05809
BUILTIN
D5418
RE-S-1800x4
RE-S-1800x4
Enhanced MX SCB
Enhanced MX SCB
MPC4E 3D 32XGE
HMPC PMB 2G
8X10GE SFPP
8X10GE SFPP
8X10GE SFPP
8X10GE SFPP
MPC4E 3D 2CGE+8XGE
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
UNKNOWN
1413
PIC 2
PIC 3
Xcvr 0
FPC 4
CPU
Fan Tray
BUILTIN
BUILTIN
BUILTIN
BUILTIN
NON-JNPR
X12J00362
REV 12.3.10 750-033205 YR9445
4x10GE SFPP
1X100GE CFP
CFP-100G-SR10
MPCE Type 3 3D
Enhanced Left Fan Tray
1414
Serial number
JN11E188CAFJ
ABAC7474
ABAC7408
ACAJ1137
ACAJ1016
ABBT8832
VK00255
Description
MX2020
Lower Backplane
Upper Backplane
Upper Power Midplane
Lower Power Midplane
Front Panel Display
DC 52V Power Supply
VJ00148
VK00207
VK00319
VK00264
VG00025
VK00274
VJ00167
VK00299
VK00213
VK00253
VJ00040
VJ00025
9009089735
9009089731
ZT2846
ZT2877
ZS2282
ZS2261
ZZ2582
ZV4229
CAAB4902
CAAB4891
CAAB4883
CAAB4889
ZV1818
CAAB4897
ZT9799
ZS1122
CAAD7674
BUILTIN
753019A00404
MIC 1
PIC 2
Xcvr
Xcvr
Xcvr
QXM 0
QXM 1
FPC 9
CPU
MIC 0
PIC 0
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
MIC 1
PIC 2
Xcvr
QXM 0
QXM 1
FPC 10
CPU
MIC 0
PIC 0
Xcvr
PIC 1
Xcvr
FPC 14
CPU
PIC 0
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
PIC 1
Xcvr 0
PIC 2
Xcvr 0
Xcvr 1
Xcvr 3
PIC 3
FPC 19
CPU
PIC 0
Xcvr 0
Xcvr 1
PIC 1
Xcvr 0
PIC 2
Xcvr 0
PIC 3
Xcvr 0
ADC 0
ADC 9
ADC 10
ADC 14
ADC 19
Fan Tray 0
Fan Tray 1
REV 14
0
1
2
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
06
06
34
06
24
0
1
0
1
REV 02
REV 11
REV
REV
REV
REV
REV
REV
REV 01
REV 02
REV 09
REV 08
REV
REV
REV
REV
01
06
06
27
07
18
01
01
01
01
REV 01
REV 01
REV 01
REV 32
REV 10
REV 01
REV 01
REV 01
REV 01
REV
REV
REV
REV
REV
REV
REV
REV
01
05
01
05
02
01
03
2A
750-031967
BUILTIN
740-011615
740-011615
740-021308
711-028408
711-028408
750-031090
711-030884
750-028387
BUILTIN
NON-JNPR
NON-JNPR
BUILTIN
740-014289
NON-JNPR
750-033535
BUILTIN
740-014279
711-028408
711-028408
750-033205
711-035209
750-028380
BUILTIN
740-014289
BUILTIN
740-014289
750-037355
711-035209
BUILTIN
740-021308
740-031980
740-031980
740-021308
BUILTIN
NON-JNPR
BUILTIN
740-021308
740-021308
740-021308
BUILTIN
750-028467
711-029089
BUILTIN
740-021308
740-021308
BUILTIN
740-021308
BUILTIN
740-021308
BUILTIN
740-031980
750-043596
750-043596
750-043596
750-043596
750-043596
760-046960
760-046960
ZM6103
BUILTIN
PEF1AZP
PEF1AZN
ANA0N8S
ZT9339
ZT9237
ZT9770
ZS1302
YJ3950
BUILTIN
T09M52516
CA49BK095
BUILTIN
C834XU01T
T09M52515
CAAD7681
BUILTIN
KBQ02BE
ZT9151
ZT9116
ZL6215
ZK9038
YG6885
BUILTIN
C706XU0AG
BUILTIN
T08L84366
CAAF1534
CAAB9879
BUILTIN
21T511100436
AHP0GPM
123363A00032
19T511100477
BUILTIN
X12J00260
BUILTIN
21T511104086
21T511104627
21T511104644
BUILTIN
ZR2008
ZT6933
BUILTIN
19T511100291
AMH02VE
BUILTIN
23T511102128
BUILTIN
AMS15PP
BUILTIN
123363A00716
CAAC2072
ZV4111
CAAC2058
ZW1561
ZV4127
ACAY0124
ACAY0022
MIC-3D-8OC3OC12-4OC48
MIC-3D-8OC3OC12-4OC48
SFP-IR
SFP-IR
SFP+-10G-SR
MPC QXM
MPC QXM
MPC Type 2 3D EQ
MPC PMB 2G
3D 4x 10GE XFP
2x 10GE XFP
XFP-10G-SR
XFP-10G-SR
2x 10GE XFP
XFP-10G-SR
XFP-10G-SR
MIC-3D-1OC192-XFP
MIC-3D-1OC192-XFP
XFP-OC192-SR
MPC QXM
MPC QXM
MPCE Type 3 3D
HMPC PMB 2G
3D 2x 10GE XFP
1x 10GE XFP
XFP-10G-SR
1x 10GE XFP
XFP-10G-SR
MPC4E 3D 2CGE+8XGE
HMPC PMB 2G
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
CFP-100G-SR10
4x10GE SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
1X100GE CFP
MPC 3D 16x 10GE
AMPC PMB
4x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
4x 10GE(LAN) SFP+
SFP+-10G-SR
Adapter Card
Adapter Card
Adapter Card
Adapter Card
Adapter Card
172mm FanTray - 6 Fans
172mm FanTray - 6 Fans
1415
Fan Tray 2
Fan Tray 3
REV 2A
REV 2A
760-046960
760-046960
ACAY0023
ACAY0025
show chassis hardware (MX5, MX10, MX40, MX80, MX240, MX480, and MX960 routers with Enhanced 20-port
Gigabit Ethernet MIC)
user@host> show chassis hardware
Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
711-044315
PEM 0
Rev 04
740-028288
PEM 1
Rev 04
740-028288
Routing Engine
BUILTIN
TFEB 0
BUILTIN
Processor
QXM 0
REV 05
711-028408
FPC 0
BUILTIN
MIC 0
BUILTIN
PIC 0
BUILTIN
FPC 1
BUILTIN
MIC 0
REV 02
750-049846
PIC 0
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 1
REV 02
740-011613
Xcvr 2
REV 01
740-011613
Xcvr 3
REV 01
740-011613
Xcvr 4
REV 01
740-011613
Xcvr 5
REV 01
740-011613
Xcvr 6
REV 01
740-031851
Xcvr 8
REV 02
740-013111
PIC 1
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 4
REV 01
740-011613
Xcvr 6
REV 02
740-011613
Xcvr 9
REV 01
740-011613
MIC 1
REV 26
750-028392
PIC 2
BUILTIN
Xcvr 0
REV 01
740-011613
Xcvr 5
REV 02
740-011613
Xcvr 9
REV 01
740-031851
PIC 3
BUILTIN
Xcvr 4
REV 01
740-011613
Xcvr 7
+
NON-JNPR
Xcvr 8
NON-JNPR
Xcvr 9
REV 01
740-031851
Fan Tray
Serial number
F3434
ZK2681
VE05267
VE05270
BUILTIN
BUILTIN
Description
MX80-P
MX80-P
AC Power Entry Module
AC Power Entry Module
Routing Engine
Forwarding Engine
ZK0952
BUILTIN
BUILTIN
BUILTIN
BUILTIN
CAAV2153
BUILTIN
AM0816S9B81
AM0925SBLK7
UAQ0005
UAQ000C
P9F195E
UAQ0003
AM1041SU1LD
B101501
BUILTIN
PFM1ML7
PE729P6
AM1014SGC84
AM0812S8UK3
ZY0187
BUILTIN
P9F1AN9
AM1003SFUF4
AM1041SU1LM
BUILTIN
PAJ4MYT
XG32A024
PFR0V6J
AM1041SU02U
MPC QXM
MPC BUILTIN
4x 10GE XFP
4x 10GE XFP
MPC BUILTIN
3D 20x 1GE(LAN)-E,SFP
10x 1GE(LAN) -E SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-T
10x 1GE(LAN) -E SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
3D 20x 1GE(LAN) SFP
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
10x 1GE(LAN) SFP
SFP-SX
SFP-SX
SFP-SX
SFP-SX
show chassis hardware models (MX5, MX10, MX40, MX80, MX240, MX480, and MX960 routers with Enhanced
20-port Gigabit Ethernet MIC)
user@host> show chassis hardware models
Hardware inventory:
Item
Version Part number
PEM 0
Rev 04
740-028288
PEM 1
Rev 04
740-028288
Routing Engine
BUILTIN
TFEB 0
BUILTIN
FPC 0
BUILTIN
FPC 1
BUILTIN
MIC 0
REV 02
750-049846
1416
Serial number
VE05267
VE05270
BUILTIN
BUILTIN
BUILTIN
BUILTIN
CAAV2153
MIC-3D-20GE-SFP-E
MIC 1
Fan Tray
REV 26
750-028392
ZY0187
MIC-3D-20GE-SFP
FANTRAY-MX80-S
Description
T320
T320 Backplane
T320 FPM Board
FPM Display
T Series CIP
Power Entry Module
T320 Sonet
unknown
T Series
T Series
FPC Type 2
FPC CPU
4x G/E SFP,
SFP-SX
SFP-SX
SFP-SX
SFP-SX
4x G/E SFP,
SFP-T
SFP-SX
SFP-SX
SFP-LX
MMB-288mbit
PPB Type 2
FPC Type 1
FPC CPU
1x G/E QPP,
SFP-SX
MMB-288mbit
PPB Type 2
FPC Type 1
FPC CPU
1x G/E SFP,
SFP-SX
4x OC-3 SONET,
MMB-288mbit
PPB Type 2
FPC Type 4
FPC CPU
FPC Type 2
FPC CPU
2x G/E QPP,
SFP-SX
SFP-SX
1417
PIC 1
1000 BASE
SFP 0
SFP 1
MMB 1
PPB 0
FPC 7
...
REV 01
750-008155
REV 01
740-007326
NON-JNPR
710-005555
710-003758
710-005803
REV 01
REV 03
REV 01
BE2116
2x G/E QPP,
P4R0PNZ
2908
AZ2246
AY4839
AZ2123
SFP-SX
SFP-T
MMB-288mbit
PPB Type 2
FPC Type 3
Serial number
19182
AX5608
HE3064
HE7864
HA5024
VH26235
VH26230
HA4508
210865700483
HD3044
HD5572
HA4712
HV2331
USC202R103
HV2332
USC202R112
HX4416
434TC004
HX4420
434TC124
JE4839
JW9163
HX4419
USC202RT05
HN7426
03L90051
HT7423
Description
T640
T640 Backplane
T640 FPM Board
FPM Display
T Series CIP
AC PEM 10kW US
AC PEM 10kW US
T640 Sonet Clock Gen.
RE-3.0 (RE-600)
T Series Control Board
FPC Type 3
FPC CPU
1x 10GE(LAN),XENPAK
XENPAK-SR
1x 10GE(LAN),XENPAK
XENPAK-ZR
1x 10GE(LAN),XENPAK
XENPAK-CX4
1x 10GE(LAN),XENPAK
XENPAK-LX4
E2-FPC Type 1
FPC CPU
1x 10GE(LAN),XENPAK
XENPAK-LR
1x 10GE(LAN),XENPAK
XENPAK-ER
1x 10GE(LAN),XENPAK
UNKNOW0N
1x 10GE(LAN),DWDM
FPC Type 4
FPC CPU
Front Top Fan Tray
Front Bottom Fan Tray
Rear Fan Tray
AY4850
JD3872
JB6042
1418
CLEI code
740-005022
710-002726
710-002728
710-007527
750-002510
750-001901
710-001721
750-009553
750-005486
RE-600-2048-S
CHAS-BP-T640-S
CB-L-T-S
T640-FPC2
PB-2GE-SX
PB-4OC12-SON-SMIR
T640-FPC3
PC-4OC48-SON-SFP
SIB-I-T640-S
FANTRAY-T-S
FANTRAY-T-S
FAN-REAR-TX-T640-S
1419
...
CB 0
...
FPC 1
...
REV 06
710-002728
HE3614
REV 01
REV 06
710-002385
710-001726
HE3009
HC0010
FPC Type 1
Serial number
JN1172F25AHA
RC8355
BBAE0927
EF6764
BBAD9210
VA00016
BBAD7248
BBAE3874
P737F-002248
P737F-002653
ED0295
EA6050
EK1173
EJ8584
EF6837
123363A01145
123363A01147
AJJ01P3
B10M03256
AJJ01M2
123363A01137
AJJ01PN
AJJ01NW
123363A01139
AJJ01KE
123363A01336
B10M01325
EF6800
AJJ01SA
AJJ01QZ
AJH0217
AJJ01TE
AJJ01KV
AJJ01MU
AJJ01R0
AJJ01TC
AJJ0364
AJD0GV3
B10M03343
AJJ01QJ
EJ8490
EJ8517
EJ8489
EG3637
EG0150
EF3657
C22CQNJ
BBAN4098
B11J04902
B11J04891
Description
T4000
T-series Backplane
T640 FPM Board
T1600 FPM Display
T-series CIP
Power Entry Module 6x60
T640 Sonet Clock Gen.
T640 Sonet Clock Gen.
RE-DUO-1800
RE-DUO-1800
LCC Control Board
LCC Control Board
FPC Type 5-3D
SNG PMB
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
FPC Type 5-3D
SNG PMB
1x100GE
CFP-100G-LR4
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
SFP+-10G-SR
1420
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
FPC 5
CPU
PIC 0
PIC 1
Xcvr
BRIDGE
MMB 0
MMB 1
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray
Fan Tray
2
3
4
5
6
7
8
9
10
11
0
0
0
1
2
3
4
5
6
7
8
9
10
11
0
1
2
3
4
5
6
7
8
9
10
11
0
1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
04
03
04
03
11
09
03
01
03
07
07
05
06
10
01
01
01
01
01
01
01
01
01
01
01
01
02
01
01
01
01
01
01
01
01
01
01
01
01
04
03
04
05
05
02
07
07
02
02
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
710-033871
710-016744
750-029262
750-034781
740-032210
711-029995
710-025563
710-025563
750-010153
711-030686
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
710-023321
710-023321
711-036340
711-036340
711-036340
711-036340
711-036340
AJJ01MX
B11J04183
B11J04894
B11J04184
B11J04897
B11J04899
AJJ01TV
B11J04057
AJJ01M4
B11J04905
EG1524
EG0345
EG1522
BBAJ0768
BBAH9342
EE6789
EE6655
J11A22334
EE6572
BBAJ4657
BBAJ3073
EF4936
EF4189
BBAN4109
B11J04895
B11J04898
B11J04021
B11J04903
B11J04311
B11J04059
B11J04016
B11J04017
B11J04887
B11J04297
B11J04893
B11J04022
EE3711
AJH033X
AJJ01N0
AJJ01SV
AJJ032L
B10M01593
AJD0FF1
AJJ01NU
123363A01305
B10M00361
AJJ01M7
AJJ032X
AJJ01PG
EF3838
EF3821
EF3834
ED1990
EA2768
EF8802
EG2286
EG2252
EF1358
EF8806
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
FPC Type 4-ES
ST-PMB2
100GE
100GE CFP
CFP-100G-LR4
100GE Bridge Board
ST-MMB2
ST-MMB2
FPC Type 5-3D
SNG PMB
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
LCC Switch CPU
LCC Switch CPU
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
Front Top Fan Tray
Front Bottom Fan Tray
1421
-- Rev 2
Fan Tray 2
show chassis hardware (T4000 Router with 16 GB line card chassis (LCC) Routing Engine)
user@host> show chassis hardware
Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 01
710-027486
FPM GBUS
REV 13
710-002901
FPM Display
REV 04
710-021387
CIP
REV 06
710-002895
PEM 0
Rev 03
740-026384
PEM 1
Rev 03
740-026384
SCG 0
REV 18
710-003423
SCG 1
REV 18
710-003423
Routing Engine 0 REV 01
740-042243
Routing Engine 1 REV 01
740-042243
CB 1
REV 11
710-022597
CB 1
REV 11
710-022597
FPC 0
REV 05
710-033871
CPU
REV 11
710-016744
PIC 0
REV 20
750-017405
PIC 1
REV 17
750-026962
MMB 0
REV 07
710-025563
MMB 1
REV 07
710-025563
FPC 1
REV 05
710-033871
CPU
REV 11
710-016744
PIC 0
REV 17
750-026962
MMB 0
REV 07
710-025563
MMB 1
REV 07
710-025563
SPMB 1
REV 05
710-023321
SIB 0
REV 11
710-013074
SIB 1
REV 11
710-013074
SIB 2
REV 11
710-013074
SIB 3
REV 11
710-013074
SIB 4
REV 11
710-013074
Fan Tray 0
Fan Tray 1
Fan Tray 2
Serial number
JN11BDF2CAHA
ACAJ0774
BBAL6812
BBAP2679
BBAP4758
XF86421
XF86429
BBAP1896
BBAN8659
737F-002238
737F-002403
EK4526
EK4527
EK5644
EK3428
EJ3041
EH7536
EK6039
EK6086
EK6583
EK3401
EJ8948
EK6202
EK6112
EK4900
EK5958
EK4606
EK5971
EK4609
EK4602
Description
T1600
T640 Backplane
T640 FPM Board
T1600 FPM Display
T-series CIP
Power Entry Module 3x80
Power Entry Module 3x80
T640 Sonet Clock Gen.
T640 Sonet Clock Gen.
RE-DUO-1800-16G
RE-DUO-1800-16G
LCC Control Board
LCC Control Board
FPC Type 4-ES
ST-PMB2
4x 10GE (LAN/WAN) XFP
10x10GE(LAN/WAN) SFPP
ST-MMB2
ST-MMB2
FPC Type 4-ES
ST-PMB2
10x10GE(LAN/WAN) SFPP
ST-MMB2
ST-MMB2
LCC Switch CPU
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
Front Top Fan Tray
Front Bottom Fan Tray
Rear Fan Tray -- Rev 2
Serial number
JN1173A24AHA
AN7797
AN6649
EF6830
Description
T4000
FPC Type 5-LSR
SNG PMB
12x10GE (LAN/WAN) SFPP
1422
SCG 1
REV 18
Routing Engine 0 REV 05
Routing Engine 1 REV 06
CB 0
REV 09
CB 1
REV 09
FPC 3
PIC 0
REV 08
PIC 1
REV 10
FPC 5
REV 03
PIC 1
REV 03
FPC 6
PIC 0
REV 10
Fan Tray 0
Fan Tray 1
Fan Tray 2
710-003423
740-026941
740-026941
710-022597
710-022597
SCG-T-S
RE-DUO-C1800-8G-S
RE-DUO-C1800-8G-S
CB-LCC-S
CB-LCC-S
750-035293
750-034624
710-033871
750-034781
XXXXXXXXBB
XXXXXXXXCC
IPUCAMBCTD
IPUIBKLMAA
PF-1CGE-CFP
PF-12XGE-SFPP
T1600-FPC4-ES
PD-1CE-CFP-FPC4
750-034624
XXXXXXXXCC
PF-12XGE-SFPP
FANTRAY-T-S
FANTRAY-T4000-S
FANTRAY-TXP-R-S
1423
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
FPC 3
CPU
PIC 0
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
FPC 5
CPU
PIC 0
PIC 1
Xcvr
BRIDGE
MMB 0
MMB 1
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
1424
8
9
10
11
0
0
1
2
3
4
5
6
7
8
9
10
11
0
0
0
1
2
3
4
5
6
7
8
9
10
11
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
05
04
05
07
09
08
01
10
01
01
01
01
01
01
01
01
01
01
01
01
04
03
04
03
11
09
03
01
03
07
07
05
06
10
01
01
01
01
01
01
01
01
01
01
01
01
02
01
01
01
01
01
01
01
01
01
01
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
750-032819
711-030686
750-035293
740-032210
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
711-034381
711-035774
711-034381
710-033871
710-016744
750-029262
750-034781
740-032210
711-029995
710-025563
710-025563
750-010153
711-030686
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
750-034624
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
AJJ0364
AJD0GV3
B10M03343
AJJ01QJ
EJ8490
EJ8517
EJ8489
EG3637
EG0150
EF3657
C22CQNJ
BBAN4098
B11J04902
B11J04891
AJJ01MX
B11J04183
B11J04894
B11J04184
B11J04897
B11J04899
AJJ01TV
B11J04057
AJJ01M4
B11J04905
EG1524
EG0345
EG1522
BBAJ0768
BBAH9342
EE6789
EE6655
J11A22334
EE6572
BBAJ4657
BBAJ3073
EF4936
EF4189
BBAN4109
B11J04895
B11J04898
B11J04021
B11J04903
B11J04311
B11J04059
B11J04016
B11J04017
B11J04887
B11J04297
B11J04893
B11J04022
EE3711
AJH033X
AJJ01N0
AJJ01SV
AJJ032L
B10M01593
AJD0FF1
AJJ01NU
123363A01305
B10M00361
AJJ01M7
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
FPC Type 5-3D
SNG PMB
1x100GE
CFP-100G-LR4
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
FPC Type 4-ES
ST-PMB2
100GE
100GE CFP
CFP-100G-LR4
100GE Bridge Board
ST-MMB2
ST-MMB2
FPC Type 5-3D
SNG PMB
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
12x10GE (LAN/WAN) SFPP
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
Xcvr
Xcvr
LMB 0
LMB 1
LMB 2
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray
Fan Tray
-- Rev 2
Fan Tray
10
11
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
04
03
04
05
05
02
07
07
02
02
740-031980
740-031980
711-034381
711-035774
711-034381
710-023321
710-023321
711-036340
711-036340
711-036340
711-036340
711-036340
AJJ032X
AJJ01PG
EF3838
EF3821
EF3834
ED1990
EA2768
EF8802
EG2286
EG2252
EF1358
EF8806
0
1
SFP+-10G-SR
SFP+-10G-SR
Type-0 LMB
Type-1 LMB
Type-0 LMB
LCC Switch CPU
LCC Switch CPU
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
SIB-HC-3D
Front Top Fan Tray
Front Bottom Fan Tray
Part number
710-027486
710-021387
710-002895
740-036442
710-003423
710-003423
740-026941
740-026941
710-022597
710-022597
Serial number
RC8355
EF6764
BBAD9210
VA00016
BBAD7248
BBAE3874
P737F-002248
P737F-002653
ED0295
EA6050
750-035293
750-034624
710-033871
750-034781
EF3657
BBAN4098
BBAJ0768
EE6655
PF-1CGE-CFP
PF-12XGE-SFPP
T1600-FPC4-ES
PD-1CE-CFP-FPC4
750-034624
BBAN4109
PF-12XGE-SFPP
FANTRAY-T-S
FANTRAY-T4000-S
FAN-REAR-TXP-LCC
1425
FPC 1
CPU
PIC 0
PIC 1
PIC 2
PIC 3
SFP 0
SFP 1
MMB 1
PPB 0
PPB 1
FPC 2
CPU
PIC 0
SFP 0
PIC 1
PIC 2
PIC 3
REV
REV
REV
REV
REV
REV
05
14
02
02
14
09
01
02
04
04
08
05
02
01
03
01
07
710-007527
710-001726
750-007218
750-007745
750-001901
750-008155
NON-JNPR
740-007326
710-005555
710-003758
710-003758
710-010154
710-010169
750-009567
740-009898
750-003336
750-004535
750-007141
HM3245
HM1084
AZ1112
HG3462
BA5390
HS3012
P1186TY
P11WLTF
HL7514
HM4405
AV1960
HZ3578
HZ3219
HX2882
USC202U709
HJ9954
HC0235
HX1699
FPC Type 2
FPC CPU
2x OC-12 ATM2 IQ, SMIR
4x OC-3 SONET, SMIR
4x OC-12 SONET, SMIR
2x G/E IQ, 1000 BASE
SFP-S
SFP-SX
MMB-288mbit
PPB Type 2
PPB Type 2
E-FPC Type 3
FPC CPU-Enhanced
1x 10GE(LAN),XENPAK
XENPAK-LR
4x OC-48 SONET, SMSR
1x OC-192 SM SR1
10x 1GE(LAN), 1000 BASE
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
SFP 0
SFP 1
MMB 0
MMB 1
SPMB 0
SIB 3
B Board
SIB 4
B Board
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
03
03
09
07
06
07
06
740-007326
740-007326
710-010171
710-010171
710-003229
710-005781
710-005782
710-005781
710-005782
2441042
2441027
HV2365
HZ3888
HW5245
HR5927
HR5971
HR5903
HZ5275
SFP-SX
SFP-SX
MMB-5M3-288mbit
MMB-5M3-288mbit
T Series Switch CPU
SIB-L8-F16
SIB-L8-F16 (B)
SIB-L8-F16
SIB-L8-F16 (B)
1426
Serial number
B2703
RC4137
DT7062
DS3067
DT3386
UA26344
Description
T1600
T640 Backplane
T640 FPM Board
FPM Display
T-series CIP
Power Entry Module 3x80
PEM 1
Rev 18
SCG 0
REV 15
Routing Engine 0 REV 08
Routing Engine 1 REV 07
CB 0
REV 05
CB 1
REV 03
FPC 0
REV 07
CPU
REV 05
PIC 0
REV 01
Xcvr 0
REV 01
Xcvr 1
REV 01
Xcvr 2
REV 01
PIC 1
REV 06
PIC 2
REV 14
PIC 3
REV 07
MMB 1
REV 07
FPC 1
REV 06
CPU
REV 04
PIC 0
REV 08
PIC 1
REV 10
Xcvr 0
REV 01
Xcvr 2
REV 01
Xcvr 3
REV 01
PIC 2
REV 22
740-002595
710-003423
740-014082
740-014082
710-007655
710-017707
710-013558
710-013563
750-010618
740-011613
740-011613
740-011782
750-001900
750-001901
750-001900
710-010171
710-013553
710-013563
750-001072
750-012266
740-011613
740-011613
740-011782
750-005634
MMB 1
FPC 2
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
PIC 3
Xcvr
Xcvr
MMB 0
MMB 1
PPB 0
PPB 1
FPC 3
CPU
PIC 0
Xcvr
PIC 1
0
1
2
4
5
6
7
8
9
0
1
2
4
5
6
7
0
1
UF38441
DV0941
9009014502
9009009591
JA9360
DT3251
DR4253
DS3902
CB5446
P9F11CW
P9F15C2
PB94K0L
HB6399
AP1092
AR8275
DS1524
DL9067
DM1685
AB1688
JX5519
AM0812S8UK6
AM0812S8UK1
P8N1YHG
DP0083
REV
REV
REV
REV
07
01
06
16
710-008923
710-005548
710-001726
750-007141
DN1862
HJ9899
HC0586
NC9660
MMB
FPC
FPC
10x
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
06
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
05
17
01
01
03
03
02
02
01
01
07
740-011613
740-011782
740-011613
740-011613
740-011613
740-011613
740-011613
740-011782
740-011613
750-015217
740-011782
740-013111
740-011613
NON-JNPR
740-011782
740-011613
740-011613
750-004695
750-009553
740-011785
740-011785
710-004047
710-004047
710-002845
710-002845
710-010154
710-010169
750-012793
NON-JNPR
750-007141
AM0812S8XAR
P920E7B
AM0812S8XAU
AM0812S8XAK
AM0812S8XAA
PAJ4NKY
AM0812S8UJW
PB81X89
AM0812S8UJX
DK3280
P8P0A3T
5090002
AM0814S93BQ
PDE0FAN
P8Q20XY
AM0812S8UJV
AM0812S8UP7
HT4383
RL0204
PDS3T23
P6Q0F3E
HD5843
HE3208
HA4524
HA4766
HR0863
HN3422
WF5096
M64294TP
DV2127
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-T
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x Tunnel
4x OC-48 SONET
SFP-SR
SFP-SR
MMB-288mbit
MMB-288mbit
PPB Type 3
PPB Type 3
E-FPC Type 3
FPC CPU-Enhanced
1x 10GE(LAN/WAN) IQ2
XFP-10G-LR
10x 1GE(LAN), 1000 BASE
0
REV 25
3M 288-bit
Type 3
CPU
1GE(LAN), 1000 BASE
1427
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
PIC 3
MMB 0
MMB 1
FPC 4
CPU
PIC 0
PIC 1
Xcvr
BRIDGE
MMB 0
MMB 1
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
MMB 0
MMB 1
FPC 6
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
MMB 0
MMB 1
FPC 7
CPU
PIC 0
Xcvr
PIC 1
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 3
MMB 0
MMB 1
1428
0
1
2
4
5
0
0
0
0
1
2
3
0
1
2
3
0
1
2
3
0
0
1
0
1
2
3
4
5
6
7
REV
REV
REV
REV
01
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
17
01
32
01
01
16
09
03
05
0
02
04
04
02
04
16
01
01
01
01
01
04
04
14
09
11
01
01
01
01
13
02
02
02
02
01
01
09
15
10
02
01
01
01
01
01
01
01
01
01
01
01
01
15
03
03
740-011613
740-011782
740-011782
740-011782
NON-JNPR
750-009553
740-011785
750-003700
710-010171
710-010171
710-013037
710-016744
711-029996
711-029999
740-032210
711-029995
710-025563
710-025563
710-013037
710-016744
750-012518
740-014279
740-014279
740-014279
740-014279
750-010850
710-016036
710-016036
710-013037
710-016744
750-017405
740-014289
740-014279
740-014289
740-014289
750-017405
740-011571
740-014289
740-014289
740-014289
710-025563
710-025563
710-007529
710-001726
750-012793
740-011571
750-015217
740-011782
740-011782
750-015217
740-011613
740-011613
740-011613
740-011613
740-011613
740-011782
740-011782
740-011613
750-009450
710-005555
710-005555
PFA6LTJ
P9P0XV4
P9M0TNX
P9B0TTP
PBS4LED
RL0212
PDS3T8G
DL1279
HR0821
HR0818
EB4919
BBAA4382
EB1569
EB9983
J10G80746
EB2235
BBAA7112
BBAA7149
DE3407
DA2124
DF2554
AA0745N1FX8
AA0748N1HN5
AA0748N1HT6
AA0744N1EC9
JA0329
DE9577
DK4060
DV1431
DT9020
DM6261
C701XU05Q
AA0748N1HPT
T08E19189
C715XU058
DP8772
C850XJ037
C839XU0L9
C834XU05A
C810XU0CE
DT8454
DT8366
HZ7624
HZ1413
DM5627
C831XJ062
JT6762
P8Q25JU
P9B0U0K
JS4268
AM0812S8XBZ
AM0812S8XAP
AM0812S8XBY
AM0812S8XBX
P9F1652
P8Q21YC
P8Q27HQ
P8E2SSU
NB6790
HZ3450
HZ3415
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
4x OC-48 SONET
SFP-SR
1x OC-192 12xMM VSR
MMB-288mbit
MMB-288mbit
FPC Type 4-ES
ST-PMB2
100GE
100GE CFP
CFP-100G-LR4
100GE Bridge Board
ST-MMB2
ST-MMB2
FPC Type 4-ES
ST-PMB2
4x OC-192 SONET XFP
XFP-OC192-SR
XFP-OC192-SR
XFP-OC192-SR
XFP-OC192-SR
1x OC-768 SONET SR
ST-MMB2
ST-MMB2
FPC Type 4-ES
ST-PMB2
4x 10GE (LAN/WAN) XFP
XFP-10G-SR
XFP-10G-LR
XFP-10G-SR
XFP-10G-SR
4x 10GE (LAN/WAN) XFP
XFP-10G-SR
XFP-10G-SR
XFP-10G-SR
XFP-10G-SR
ST-MMB2
ST-MMB2
FPC Type 3
FPC CPU
1x 10GE(LAN/WAN) IQ2
XFP-10G-SR
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-SX
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x OC-192 SM SR2
MMB-288mbit
MMB-288mbit
PPB 0
PPB 1
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
REV
REV
REV
04
04
10
12
07
07
07
07
07
710-002845
710-002845
710-003229
710-003229
710-013074
710-013074
710-013074
710-013074
710-013074
HP0887
HW5255
HX3699
DT3091
DS4747
DS4942
DS4965
DS4990
DS4944
PPB Type 3
PPB Type 3
T-series Switch CPU
T-series Switch CPU
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
SIB-I8-SF
Front Top Fan Tray
Front Bottom Fan Tray
Rear Fan Tray -- Rev 2
1429
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
Fan
Fan
Fan
Fan
Fan
Fan
Board
F2S 2/2
Board
F2S 2/4
Board
F2S 2/6
Board
F2S 3/0
Board
F2S 3/2
Board
F2S 3/4
Board
F2S 3/6
Board
F2S 4/0
Board
F2S 4/2
Board
F2S 4/4
Board
F2S 4/6
Board
Tray 0
Tray 1
Tray 2
Tray 3
Tray 4
Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
05
04
05
05
05
04
05
05
05
03
03
05
05
03
03
03
03
05
05
04
05
03
03
02
02
05
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
760-024497
760-024497
760-024502
DW8498
DW4845
DW8457
DW7802
DW7562
DW4822
DW8467
DW7815
DW7518
DV0068
DT9974
DW7874
DW7601
DV0033
DT9969
DV0043
DT9948
DW5446
DW7611
DW4826
DW8458
DV0026
DT9963
DR8290
DR8293
DR8280
REV 05
REV 02
760-024502
760-024502
DR8276
DP5643
lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11036F8AHA
T1600
Midplane
REV 03
710-017247
RC3799
T-series Backplane
FPM GBUS
REV 10
710-002901
DP7009
T640 FPM Board
FPM Display
REV 01
710-021387
DN7026
T1600 FPM Display
CIP
REV 06
710-002895
DP6024
T-series CIP
PEM 1
Rev 02
740-023211
WA50019
Power Entry Module 4x60A
SCG 0
REV 15
710-003423
DR6757
T640 Sonet Clock Gen.
SCG 1
REV 15
710-003423
DS2225
T640 Sonet Clock Gen.
Routing Engine 0 REV 01
740-026941
737F-1040
RE-DUO-1800
Routing Engine 1 REV 01
740-026941
737F-1016
RE-DUO-1800
CB 0
REV 06
710-022597
DX4011
LCC Control Board
CB 1
REV 06
710-022597
DX4017
LCC Control Board
FPC 1
REV 07
710-013035
DN5847
FPC Type 3-ES
CPU
REV 08
710-016744
DP2570
ST-PMB2
PIC 0
REV 05
750-015217
DB0418
8x 1GE(TYPE3), IQ2
Xcvr 0
REV 01
740-011782
P8Q27ZG
SFP-SX
Xcvr 1
NON-JNPR
PDA1U0D
SFP-SX
Xcvr 2
REV 01
740-011613
P9F1ALW
SFP-SX
Xcvr 3
REV 01
740-011782
PBA403V
SFP-SX
Xcvr 4
NON-JNPR
PDE09DP
SFP-SX
Xcvr 5
REV 01
740-011782
PCH2P4K
SFP-SX
Xcvr 6
REV 01
740-011782
PB94K0F
SFP-SX
Xcvr 7
REV 01
740-011782
PBA2R2A
SFP-SX
PIC 1
REV 03
750-004424
HJ4020
1x 10GE(LAN),DWDM
PIC 2
REV 01
750-003336
HG6073
4x OC-48 SONET, SMSR
MMB 0
REV 04
710-016036
DP3401
ST-MMB2
FPC 3
REV 12
710-013037
DR1169
FPC Type 4-ES
1430
CPU
PIC 0
MMB 0
MMB 1
FPC 4
CPU
PIC 0
Xcvr 0
PIC 1
REV
REV
REV
REV
REV
REV
REV
REV
REV
08
02
04
04
05
08
04
02
22
710-016744
750-010850
710-016036
710-016036
710-021534
710-016744
750-014627
740-011615
750-005634
PIC 2
PIC 3
Xcvr 0
MMB 0
FPC 5
CPU
PIC 0
Xcvr 0
PIC 1
REV 09
REV 08
REV
REV
REV
REV
REV
REV
04
07
15
14
01
16
750-002911
750-021652
NON-JNPR
710-016036
710-007529
710-001726
750-009567
740-013170
750-007141
CF4539
DR2827
8
DR0809
HS5608
HX4351
WJ8961
J05K05961
JJ8146
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
MMB 0
MMB 1
PPB 0
PPB 1
FPC 6
CPU
PIC 0
Xcvr
PIC 1
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 2
Xcvr
Xcvr
Xcvr
Xcvr
MMB 0
FPC 7
CPU
PIC 0
PIC 1
PIC 2
Xcvr
Xcvr
PIC 3
Xcvr
MMB 0
SPMB 0
SPMB 1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
12
02
03
03
04
04
07
08
09
02
06
01
01
01
01
01
01
02
01
06
01
01
01
01
04
03
09
13
05
10
01
01
03
01
05
04
04
740-011613
740-011782
740-011782
740-011613
750-009567
740-013170
710-005555
710-005555
710-002845
710-002845
710-013035
710-016744
750-009567
740-013170
750-015217
740-011782
740-011613
740-011782
740-011782
740-011782
740-011613
740-013111
740-011782
750-015217
740-011613
740-013111
740-011782
740-011613
710-016036
710-021540
710-016744
750-001901
750-001900
750-008155
740-011782
740-011782
750-014638
740-011785
710-016036
710-023321
710-023321
P9F117T
PBA2VCL
PB83DRB
AM0812S8UP8
WF3566
T07C94489
HZ1907
HW5283
HZ7717
HS0110
DP7486
DP2545
NE6323
T09C71959
DN4775
P7E0T6M
AM0812S8XAY
P7E0T6J
PCH2P7D
P9B0QYT
AM0812S8WQJ
9301220
P9B0TZ5
DM6747
PAP0ZB2
70191002
PBA29H8
AM0812S8WQG
DP3238
DV3154
DT9053
HB4225
AD3644
HV0335
PCH2UKF
PCH2V19
JS9493
P6Q0ENK
DP3323
DX3004
DX3009
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x 10GE(LAN),XENPAK
XENPAK-LR
MMB-288mbit
MMB-288mbit
PPB Type 3
PPB Type 3
FPC Type 3-ES
ST-PMB2
1x 10GE(LAN),XENPAK
XENPAK-LR
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-T
SFP-SX
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-T
SFP-SX
SFP-SX
ST-MMB2
FPC Type 2-ES
ST-PMB2
4x OC-12 SONET, SMIR
1x OC-48 SONET, SMSR
2x G/E IQ, 1000 BASE
SFP-SX
SFP-SX
1x OC-48-12-3 SFP
SFP-SR
ST-MMB2
LCC Switch CPU
LCC Switch CPU
1
2
3
4
0
0
0
1
2
3
4
5
6
7
0
1
6
7
0
1
0
DP9429
JA0332
DR0628
DR0592
DR7350
DP8096
DP9171
PDE2RVR
DS5815
ST-PMB2
1x OC-768 SONET SR
ST-MMB2
ST-MMB2
FPC Type 1-ES
ST-PMB2
4x OC-3 1x OC-12 SFP
SFP-SR
1x CHOC12 IQ SONET, SMIR
1431
SIB
B
SIB
B
SIB
SIB
B
SIB
B
Fan
Fan
Fan
0
Board
1
Board
2
3
Board
4
Board
Tray 0
Tray 1
Tray 2
REV
REV
REV
REV
07
07
07
07
710-022594
710-023185
710-022594
710-023185
DW4195
DW3930
DW4179
DW3919
LCC
LCC
LCC
LCC
SIB
SIB Mezz
SIB
SIB Mezz
REV
REV
REV
REV
06
06
08
07
710-022594
710-023185
710-022594
710-023185
DT8251
DT5792
DW8014
DW3917
LCC SIB
LCC SIB Mezz
LCC SIB
LCC SIB Mezz
Front Top Fan Tray
Front Bottom Fan Tray
Rear Fan Tray -- Rev 3
lcc1-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN1102270AHA
T1600
Midplane
REV 04
710-017247
RC5358
T-series Backplane
FPM GBUS
REV 10
710-002901
DS3443
T640 FPM Board
FPM Display
REV 01
710-021387
DS6411
T1600 FPM Display
CIP
REV 06
710-002895
DS4235
T-series CIP
PEM 0
Rev 02
740-023211
VM82438
Power Entry Module 4x60A
SCG 0
REV 15
710-003423
DS6649
T640 Sonet Clock Gen.
SCG 1
REV 15
710-003423
DR6775
T640 Sonet Clock Gen.
Routing Engine 0 REV 01
740-026941
737F-1083
RE-DUO-1800
Routing Engine 1 REV 01
740-026941
737F-1104
RE-DUO-1800
CB 0
REV 06
710-022597
DW8542
LCC Control Board
CB 1
REV 06
710-022597
DW8530
LCC Control Board
FPC 0
REV 02
710-010845
JE2392
FPC Type 4
CPU
REV 02
710-011481
JF6820
FPC CPU-Enhanced
PIC 0
REV 11
750-017405
DP7259
4x 10GE (LAN/WAN) XFP
Xcvr 0
REV 01
740-014279
AA0741N1C8T
XFP-10G-LR
Xcvr 1
REV 01
740-014279
AA0746N1GAM
XFP-10G-LR
Xcvr 2
REV 01
740-014279
AA0747N1H0B
XFP-10G-LR
Xcvr 3
REV 01
740-014279
AA0748N1HZ5
XFP-10G-LR
MMB 0
REV 03
710-010842
HY7601
ST-MMB
FPC 1
REV 16
710-013037
BBAA7398
FPC Type 4-ES
CPU
REV 09
710-016744
BBAA2329
ST-PMB2
PIC 0
REV 03
711-029996
EB1575
100GE
PIC 1
REV 06
750-034781
EB9980
100GE CFP
MMB 0
REV 04
710-025563
BBAA5325
ST-MMB2
MMB 1
REV 04
710-025563
BBAA5444
ST-MMB2
FPC 2
REV 16
710-013037
BBAA7185
FPC Type 4-ES
CPU
REV 09
710-016744
BBAA3522
ST-PMB2
PIC 0
REV 03
711-029996
EB1557
100GE
PIC 1
REV 05
750-034781
EB4660
100GE CFP
Xcvr 0
REV 0
740-032210
J10F73666
CFP-100G-LR4
BRIDGE 0
REV 02
711-029995
EB2237
100GE Bridge Board
MMB 0
REV 04
710-025563
BBAA5347
ST-MMB2
MMB 1
REV 04
710-025563
BBAA5401
ST-MMB2
FPC 3
REV 10
710-021534
DZ0941
FPC Type 1-ES
CPU
REV 09
710-016744
DY6364
ST-PMB2
PIC 0
REV 13
750-012266
DK9192
4x 1GE(LAN), IQ2
Xcvr 0
REV 01
740-011613
AM0812S8WVD
SFP-SX
Xcvr 1
NON-JNPR
PDD63Q4
SFP-SX
Xcvr 2
NON-JNPR
PDE4G54
SFP-SX
Xcvr 3
NON-JNPR
PD40MAG
SFP-SX
PIC 1
REV 01
750-007641
HJ2003
1x G/E IQ, 1000 BASE
Xcvr 0
REV 01
740-011613
AM0812S8WVG
SFP-SX
PIC 3
REV 17
750-007444
JB6873
1x CHSTM1 IQ SDH, SMIR
1432
MMB 0
FPC 4
CPU
PIC 0
REV
REV
REV
REV
04
06
07
22
710-025563
710-013035
710-016744
750-007141
DZ0281
DK0614
DK1616
DM1870
ST-MMB2
FPC Type 3-ES
ST-PMB2
10x 1GE(LAN), 1000 BASE
0
1
2
3
4
5
6
7
8
9
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
16
05
740-011782
740-011782
740-007326
740-011782
740-011782
740-011782
740-011782
740-011782
740-011613
740-011782
750-009450
750-004424
PCL3UKW
P7E0T73
P4T0WLR
PAR1LRL
P9M0U3Z
P9M0U0C
P9M0TLG
P9M0U0F
PFA6LAP
PCH2P0U
CV2565
HH3057
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
SFP-SX
1x OC-192 SM SR2
1x 10GE(LAN),10GBASE-LR
PIC 3
MMB 0
FPC 5
CPU
PIC 0
Xcvr 0
PIC 1
PIC 2
PIC 3
Xcvr 0
Xcvr 1
Xcvr 3
MMB 0
MMB 1
FPC 6
CPU
PIC 0
Xcvr 3
Xcvr 4
Xcvr 5
PIC 1
PIC 3
MMB 0
FPC 7
CPU
PIC 0
Xcvr 1
Xcvr 2
Xcvr 3
MMB 0
SPMB 0
SPMB 1
SIB 0
B Board
SIB 1
B Board
SIB 2
SIB 3
B Board
SIB 4
B Board
Fan Tray 0
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
12
04
07
05
11
01
01
32
12
01
01
01
07
07
07
07
07
01
01
01
03
02
04
08
04
11
01
02
01
04
04
04
07
07
07
07
750-013423
710-016036
710-013560
710-013563
750-012793
740-014289
750-004695
750-003700
750-009553
740-011785
740-011785
740-011785
710-010171
710-010171
710-013035
710-016744
750-015217
740-011613
740-011782
740-011782
750-003336
750-012793
710-016036
710-010845
710-011481
750-017405
740-014279
740-011571
740-014279
710-010842
710-023321
710-023321
710-022594
710-023185
710-022594
710-023185
DP0403
DK1988
DR0004
DR0089
DR6107
C743XU074
HD5980
DL3770
WB8901
P9D1GTQ
PDS0MMB
PDE1KXP
DP7374
DP7404
DM0994
DM3651
DN4743
AM0812S8XB0
PB829RB
P8J1SYX
HJ9954
JM7665
DN6913
JM3958
JK3669
DP8837
753019A00277
C850XJ00P
AA0813N1RTG
JN1971
DW3629
DW3621
DW4200
DW3932
DW4193
DW3904
MultiServices 500
ST-MMB2
E2-FPC Type 3
FPC CPU-Enhanced
1x 10GE(LAN/WAN) IQ2
XFP-10G-SR
1x Tunnel
1x OC-192 12xMM VSR
4x OC-48 SONET
SFP-SR
SFP-SR
SFP-SR
MMB-5M3-288mbit
MMB-5M3-288mbit
FPC Type 3-ES
ST-PMB2
8x 1GE(TYPE3), IQ2
SFP-SX
SFP-SX
SFP-SX
4x OC-48 SONET, SMSR
1x 10GE(LAN/WAN) IQ2
ST-MMB2
FPC Type 4
FPC CPU-Enhanced
4x 10GE (LAN/WAN) XFP
XFP-10G-LR
XFP-10G-SR
XFP-10G-LR
ST-MMB
LCC Switch CPU
LCC Switch CPU
LCC SIB
LCC SIB Mezz
LCC SIB
LCC SIB Mezz
REV
REV
REV
REV
07
06
08
06
710-022594
710-023185
710-022594
710-023185
DW4210
DT5780
DW8019
DT5795
LCC SIB
LCC SIB Mezz
LCC SIB
LCC SIB Mezz
Front Top Fan Tray
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
PIC 2
1433
Fan Tray 1
Fan Tray 2
1434
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
Fan
Fan
Fan
Fan
Fan
Fan
Board
F2S 2/4
Board
F2S 2/6
Board
F2S 3/0
Board
F2S 3/2
Board
F2S 3/4
Board
F2S 3/6
Board
F2S 4/0
Board
F2S 4/2
Board
F2S 4/4
Board
F2S 4/6
Board
Tray 0
Tray 1
Tray 2
Tray 3
Tray 4
Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
06
06
06
06
06
06
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
710-022603
710-023787
760-024497
760-024497
760-024502
760-024502
760-024502
760-024502
DW7591
DW7907
DW7590
DW7785
DW7524
DW7782
DW7634
DW7793
DW7548
DW7779
DW7587
DW7930
DW7505
DW7867
DW7656
DW7917
DW7640
DW7929
DW7643
DW7870
DW7635
DV7831
DV9614
DV9618
DV9616
DV7807
DV7828
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
F2S SIB
NEO PMB
Front Fan Tray
Front Fan Tray
Rear Fan Tray
Rear Fan Tray
Rear Fan Tray
Rear Fan Tray
1435
30
37
00
00
ff
ff
ff
ff
35
34
17
00
ff
ff
ff
ff
00
00
03
ff
ff
ff
ff
ff
TXP
00
00
07
ff
ff
ff
ff
ff
FPM Display
0x01
DX0282
01.03
0x00
CRAFT-TXP
ff ff ff ff
30
32
00
ff
00
00
ff
ff
33
37
0a
ff
00
00
ff
ff
00
00
02
ff
00
00
ff
ff
TXP
00
00
07
ff
43
00
ff
ff
CIP
0x01
DW4889
01.04
0x00
CIP-TXP
ff ff ff ff
1436
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
Fan
Fan
Fan
Fan
Fan
Fan
F2S 0/4
F2S 0/6
F2S 1/0
F2S 1/2
F2S 1/4
F2S 1/6
F2S 2/0
F2S 2/2
F2S 2/4
F2S 2/6
F2S 3/0
F2S 3/2
F2S 3/4
F2S 3/6
F2S 4/0
F2S 4/2
F2S 4/4
F2S 4/6
Tray 0
Tray 1
Tray 2
Tray 3
Tray 4
Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
04
04
04
05
04
05
04
04
05
04
05
03
05
03
03
05
04
03
02
02
05
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
760-024497
760-024497
760-024502
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
SIB-TXP-F2S-S
FANTRAY-TXP-H-S
FANTRAY-TXP-H-S
FANTRAY-TXP-V-S
REV 05
REV 02
760-024502
760-024502
FANTRAY-TXP-V-S
FANTRAY-TXP-V-S
lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number CLEI code
FRU model number
Midplane
REV 03
710-017247
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
CRAFT-T1600-S
CIP
REV 06
710-002895
CIP-L-T640-S
PEM 1
Rev 02
740-023211
IPUPAC8KTA
PWR-T1600-4-60-DC-S
SCG 0
REV 15
710-003423
SCG-T-S
SCG 1
REV 15
710-003423
SCG-T-S
Routing Engine 0 REV 01
740-026941
RE-DUO-C1800-8G-S
Routing Engine 1 REV 01
740-026941
RE-DUO-C1800-8G-S
CB 0
REV 06
710-022597
CB-LCC-S
CB 1
REV 06
710-022597
CB-LCC-S
FPC 1
REV 07
710-013035
T640-FPC3-ES
PIC 0
REV 05
750-015217
PC-8GE-TYPE3-SFP-IQ2
PIC 1
REV 03
750-004424
PC-1XGE-LR
PIC 2
REV 01
750-003336
PC-4OC48-SON-SMSR
FPC 3
REV 12
710-013037
T1600-FPC4-ES
PIC 0
REV 02
750-010850
PD-1OC768-SON-SR
FPC 4
REV 05
710-021534
T640-FPC1-ES
PIC 0
REV 04
750-014627
PB-4OC3-1OC12-SON-SFP
PIC 1
REV 22
750-005634
PB-1CHOC12SMIR-QPP
PIC 2
REV 09
750-002911
PB-4FE-TX
PIC 3
REV 08
750-021652
PB-1CHOC12-STM4-IQE-SFP
FPC 5
REV 07
710-007529
T640-FPC3
PIC 0
REV 14
750-009567
PC-1XGE-XENPAK
PIC 1
REV 16
750-007141
PC-10GE-SFP
PIC 2
REV 12
750-009567
PC-1XGE-XENPAK
FPC 6
REV 07
710-013035
T640-FPC3-ES
PIC 0
REV 09
750-009567
PC-1XGE-XENPAK
PIC 1
REV 06
750-015217
PC-8GE-TYPE3-SFP-IQ2
PIC 2
REV 06
750-015217
PC-8GE-TYPE3-SFP-IQ2
FPC 7
REV 03
710-021540
T640-FPC2-ES
PIC 0
REV 13
750-001901
PB-4OC12-SON-SMIR
PIC 1
REV 05
750-001900
PB-1OC48-SON-SMSR
1437
PIC 2
PIC 3
SIB 0
SIB 1
SIB 3
SIB 4
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
10
03
07
07
06
08
750-008155
750-014638
710-022594
710-022594
710-022594
710-022594
PB-2GE-SFP-QPP
PB-1OC48-SON-B-SFP
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
SIB-TXP-T1600-S
FANTRAY-T-S
FANTRAY-T-S
FANTRAY-TXP-R-S
lcc1-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number CLEI code
FRU model number
Midplane
REV 04
710-017247
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
CRAFT-T1600-S
CIP
REV 06
710-002895
CIP-L-T640-S
PEM 0
Rev 02
740-023211
IPUPAC8KTA
PWR-T1600-4-60-DC-S
SCG 0
REV 15
710-003423
SCG-T-S
SCG 1
REV 15
710-003423
SCG-T-S
Routing Engine 0 REV 01
740-026941
RE-DUO-C1800-8G-S
Routing Engine 1 REV 01
740-026941
RE-DUO-C1800-8G-S
CB 0
REV 06
710-022597
CB-LCC-S
CB 1
REV 06
710-022597
CB-LCC-S
FPC 0
REV 02
710-010845
T640-FPC4-ES
PIC 0
REV 11
750-017405
PD-4XGE-XFP
FPC 1
REV 16
710-013037
T1600-FPC4-ES
PIC 1
REV 06
750-034781
PD-1CE-CFP
FPC 2
REV 16
710-013037
T1600-FPC4-ES
PIC 1
REV 05
750-034781
PD-1CE-CFP
FPC 3
REV 10
710-021534
T640-FPC1-ES
PIC 0
REV 13
750-012266
PB-4GE-TYPE1-SFP-IQ2
PIC 1
REV 01
750-007641
PE-1GE-SFP-QPP
PIC 3
REV 17
750-007444
PB-1CHSTM1-SMIR-QPP
FPC 4
REV 06
710-013035
T640-FPC3-ES
PIC 0
REV 22
750-007141
PC-10GE-SFP
PIC 1
REV 16
750-009450
PC-1OC192-SON-SR2
PIC 2
REV 05
750-004424
PC-1XGE-LR
PIC 3
REV 12
750-013423
PC-MS-500-3
FPC 5
REV 07
710-013560
T640-FPC3-E2
PIC 0
REV 11
750-012793
PC-1XGE-TYPE3-XFP-IQ2
PIC 1
REV 01
750-004695
PC-TUNNEL
PIC 2
REV 32
750-003700
PC-1OC192-SON-VSR
PIC 3
REV 12
750-009553
PC-4OC48-SON-SFP
FPC 6
REV 07
710-013035
T640-FPC3-ES
PIC 0
REV 07
750-015217
PC-8GE-TYPE3-SFP-IQ2
PIC 1
REV 03
750-003336
PC-4OC48-SON-SMSR
PIC 3
REV 02
750-012793
PC-1XGE-TYPE3-XFP-IQ2
FPC 7
REV 08
710-010845
T640-FPC4-ES
PIC 0
REV 11
750-017405
PD-4XGE-XFP
SIB 0
REV 07
710-022594
SIB-TXP-T1600-S
SIB 1
REV 07
710-022594
SIB-TXP-T1600-S
SIB 3
REV 07
710-022594
SIB-TXP-T1600-S
SIB 4
REV 08
710-022594
SIB-TXP-T1600-S
Fan Tray 0
FANTRAY-T-S
Fan Tray 1
FANTRAY-T-S
Fan Tray 2
FANTRAY-TXP-R-S
1438
sfc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN111B023AHB
TXP
Midplane
REV 01
710-022574
TR7990
SFC Midplane
FPM Display
REV 03
710-024027
DW4699
TXP FPM Display
CIP 0
REV 01
710-023792
DR1437
TXP CIP
CIP 1
REV 02
710-023792
DS4564
TXP CIP
PEM 0
Rev 07
740-027463
UM26360
Power Entry Module
Routing Engine 0 REV 01
740-026942
737A-1024
SFC RE
ad0
3887 MB SMART CF
200811050193CEB1CEB1 Compact Flash
ad1
30533 MB SAMSUNG MCBQE32G8MPP-0V SY814A0762
Disk 1
Routing Engine 1 REV 01
740-026942
737A-1024
SFC RE
ad0
3887 MB SMART CF
20081105004C19A019A0 Compact Flash
ad1
30533 MB SAMSUNG MCBQE32G8MPP-0V SY814A0794
Disk 1
CB 0
REV 03
710-022606
DR7134
SFC Control Board
CB 1
REV 01
710-022606
DP8890
SFC Control Board
SPMB 0
BUILTIN
SFC Switch CPU
SPMB 1
BUILTIN
SFC Switch CPU
SIB F13 0
REV 03
750-024564
DT9478
F13 SIB
B Board
REV 02
710-023431
DT6554
F13 SIB
SIB F13 1
REV 03
750-024564
DT9454
F13 SIB
B Board
REV 02
710-023431
DT6551
F13 SIB
SIB F2S 0/0
REV 02
710-022603
DT2838
F2S SIB
B Board
REV 02
710-023787
DT1725
NEO PMB
SIB F2S 0/2
REV 02
710-022603
DT2824
F2S SIB
B Board
REV 02
710-023787
DT1706
NEO PMB
SIB F2S 0/4
REV 02
710-022603
DT2822
F2S SIB
B Board
REV 02
710-023787
DT1696
NEO PMB
SIB F2S 0/6
REV 02
710-022603
DT2823
F2S SIB
B Board
REV 02
710-023787
DT1717
NEO PMB
SIB F2S 1/0
REV 03
710-022603
DV0059
F2S SIB
B Board
REV 03
710-023787
DT9942
NEO PMB
SIB F2S 1/2
REV 02
710-022603
DT2826
F2S SIB
B Board
REV 02
710-023787
DT1713
NEO PMB
SIB F2S 1/4
REV 03
710-022603
DV0092
F2S SIB
B Board
REV 03
710-023787
DV0000
NEO PMB
SIB F2S 1/6
REV 03
710-022603
DV0079
F2S SIB
B Board
REV 03
710-023787
DT9972
NEO PMB
SIB F2S 2/0
REV 03
710-022603
DV0100
F2S SIB
B Board
REV 03
710-023787
DT9925
NEO PMB
SIB F2S 2/2
REV 03
710-022603
DV0050
F2S SIB
B Board
REV 03
710-023787
DV0005
NEO PMB
SIB F2S 2/4
REV 03
710-022603
DV0097
F2S SIB
B Board
REV 03
710-023787
DT9936
NEO PMB
Fan Tray 0
REV 02
760-024497
DR8286
Front Fan Tray
Fan Tray 1
REV 06
760-024497
DV9624
Front Fan Tray
Fan Tray 2
REV 02
760-024502
DR8259
Rear Fan Tray
Fan Tray 3
REV 02
760-024502
DR8270
Rear Fan Tray
Fan Tray 4
REV 02
760-024502
DR8284
Rear Fan Tray
Fan Tray 5
REV 06
760-024502
DV7813
Rear Fan Tray
lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN1101F27AHA
T1600
Midplane
REV 04
710-017247
RC5317
T Series Backplane
FPM GBUS
REV 10
710-002901
DS8197
T640 FPM Board
FPM Display
REV 01
710-021387
DS6433
T1600 FPM Display
1439
CIP
PEM 0
SCG 0
SCG 1
Routing Engine 0
ad0
3887 MB
ad1
30533 MB
Routing Engine 1
ad0
3887 MB
ad1
30533 MB
CB 0
CB 1
FPC 0
CPU
PIC 0
PIC 1
MMB 0
MMB 1
FPC 1
CPU
PIC 0
PIC 1
MMB 0
MMB 1
SPMB 0
SPMB 1
SIB 0
B Board
SIB 1
B Board
SIB 2
B Board
SIB 3
B Board
SIB 4
B Board
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV 06
710-002895
DS1493
T Series CIP
Rev 08
740-017906
UD26601
Power Entry Module 3x80
REV 15
710-003423
DP5847
T640 Sonet Clock Gen.
REV 15
710-003423
DR0924
T640 Sonet Clock Gen.
REV 01
740-026942
737F-1024
LCC RE
SMART CF
2008110502B63E513E51 Compact Flash
SAMSUNG MCBQE32G8MPP-0V SY814A1208
Disk 1
REV 01
740-026942
737F-1024
LCC RE
SMART CF
2008110500F9A8A8A8A8 Compact Flash
SAMSUNG MCBQE32G8MPP-0V SY814A1076
Disk 1
REV 05
710-022597
DV4264
LCC Control Board
REV 03
710-022597
DP8558
LCC Control Board
REV 14
710-013037
DS9967
FPC Type 4-ES
REV 08
710-016744
DS3989
ST-PMB2
REV 12
750-013198
DL7506
1x Tunnel
REV 12
750-013198
DL7505
1x Tunnel
REV 01
710-025563
DS8524
ST-MMB2
REV 01
710-025563
DS8373
ST-MMB2
REV 14
710-013037
DT0027
FPC Type 4-ES
REV 09
710-016744
DS7684
ST-PMB2
REV 12
750-013198
DL7512
1x Tunnel
REV 12
750-013198
DL7498
1x Tunnel
REV 01
710-025563
DS8494
ST-MMB2
REV 01
710-025563
DS8436
ST-MMB2
REV 04
710-023321
DV3867
LCC Switch CPU
REV 02
710-023321
DP0238
LCC Switch CPU
REV 06
710-022594
DT8268
LCC SIB
REV 06
710-023185
DT5791
LCC SIB Mezz
REV 06
710-022594
DT8261
LCC SIB
REV 06
710-023185
DT5769
LCC SIB Mezz
REV 04
710-022594
DS2315
LCC SIB
REV 06
710-023185
DT5788
LCC SIB Mezz
REV 06
710-022594
DT8253
LCC SIB
REV 06
710-023185
DT5811
LCC SIB Mezz
REV 06
710-022594
DT8248
LCC SIB
REV 06
710-023185
DT5812
LCC SIB Mezz
Front Top Fan Tray
Front Bottom Fan Tray
Rear Fan Tray
1440
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
SIB
Fan
Fan
Fan
Fan
Fan
Fan
F13 9
F13 12
F2S 0/0
F2S 0/2
F2S 0/4
F2S 0/6
F2S 1/0
F2S 1/2
F2S 1/4
F2S 1/6
F2S 2/0
F2S 2/2
F2S 2/4
F2S 2/6
F2S 3/0
F2S 3/2
F2S 3/4
F2S 3/6
F2S 4/0
F2S 4/2
F2S 4/4
F2S 4/6
Tray 0
Tray 1
Tray 2
Tray 3
Tray 4
Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
04
04
05
05
05
05
04
05
05
05
05
05
05
05
05
05
05
05
05
05
05
05
06
06
06
06
06
06
750-024564
750-024564
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
710-022603
760-024497
760-024497
760-024502
760-024502
760-024502
760-024502
DW5754
DW5794
DW7897
DW7833
DW7875
DW7860
DW4820
DW7849
DW7927
DW7866
DW7880
DW7895
DW7907
DW7785
DW7782
DW7793
DW7779
DW7930
DW7867
DW7917
DW7929
DW7870
DV7831
DV9614
DV9618
DV9616
DV7807
DV7828
SIB-TXP-F13
SIB-TXP-F13
SIB-TXP-F2S
FANTRAY-TXP-F
FANTRAY-TXP-F
FANTRAY-TXP-R
FANTRAY-TXP-R
FANTRAY-TXP-R
FANTRAY-TXP-R
lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
FRU model number
Midplane
REV 03
710-017247
RC3765
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
DN5441
CRAFT-T1600-S
CIP
REV 06
710-002895
DP6021
CIP-L-T640-S
PEM 0
Rev 07
740-017906
UA26384
PWR-T1600-3-80-DC-S
PEM 1
Rev 07
740-017906
UA26296
PWR-T1600-3-80-DC-S
SCG 0
REV 15
710-003423
DR0875
SCG-T-S
CB 0
REV 06
710-022597
DW8534
CB-LCC
CB 1
REV 06
710-022597
DW8527
CB-LCC
FPC 4
REV 12
710-013037
DJ8717
T1600-FPC4-ES
PIC 0
REV 11
750-017405
DP8795
PD-4XGE-XFP
PIC 1
REV 11
750-017405
DP8794
PD-4XGE-XFP
FPC 6
REV 14
710-013037
DS5335
T1600-FPC4-ES
PIC 0
REV 13
750-017405
DS7634
PD-4XGE-XFP
PIC 1
REV 13
750-017405
DS7637
PD-4XGE-XFP
FPC 7
REV 07
710-013035
DM0990
T1600-FPC3-ES
PIC 0
REV 16
750-007141
JJ8067
PC-10GE-SFP
PIC 1
REV 08
750-015749
WE9598
PC-1OC192-SON-XFP
PIC 2
REV 10
750-009450
HX6466
PC-1OC192-SON-SR2
SIB 0
REV 08
710-022594
DW8033
SIB-TXP-T1600-S
SIB 1
REV 08
710-022594
DW8044
SIB-TXP-T1600-S
SIB 2
REV 08
710-022594
DW8020
SIB-TXP-T1600-S
SIB 3
REV 08
710-022594
DW8063
SIB-TXP-T1600-S
SIB 4
REV 08
710-022594
DW8064
SIB-TXP-T1600-S
Fan Tray 0
FANTRAY-T-S
Fan Tray 1
FANTRAY-T-S
Fan Tray 2
FANTRAY-TXP-R-S
lcc1-re0:
1441
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
FRU model number
Midplane
REV 04
710-017247
RC5361
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
DS6430
CRAFT-T1600-S
CIP
REV 06
710-002895
DS4239
CIP-L-T640-S
PEM 0
Rev 08
740-017906
UD26649
PWR-T1600-3-80-DC-S
SCG 0
REV 15
710-003423
DP5820
SCG-T-S
CB 0
REV 06
710-022597
DW8523
CB-LCC
CB 1
REV 06
710-022597
DW8528
CB-LCC
FPC 4
REV 12
710-013037
DP8509
T1600-FPC4-ES
PIC 0
REV 11
750-017405
DP8808
PD-4XGE-XFP
PIC 1
REV 11
750-017405
DP7263
PD-4XGE-XFP
FPC 6
REV 14
710-013037
DS9961
T1600-FPC4-ES
PIC 0
REV 13
750-017405
DS5532
PD-4XGE-XFP
PIC 1
REV 13
750-017405
DS7639
PD-4XGE-XFP
FPC 7
REV 03
710-013035
DF5564
T1600-FPC3-ES
PIC 0
REV 16
750-007141
JJ8063
PC-10GE-SFP
SIB 0
REV 08
710-022594
DW8035
SIB-TXP-T1600-S
SIB 1
REV 10
710-022594
DX7672
SIB-TXP-T1600-S
SIB 2
REV 08
710-022594
DW8060
SIB-TXP-T1600-S
SIB 3
REV 08
710-022594
DW8072
SIB-TXP-T1600-S
SIB 4
REV 08
710-022594
DW8043
SIB-TXP-T1600-S
Fan Tray 0
FANTRAY-T-S
Fan Tray 1
FANTRAY-T-S
Fan Tray 2
FANTRAY-TXP-R-S
lcc2-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
FRU model number
Midplane
REV 03
710-017247
RC3956
CHAS-BP-T1600-S
FPM Display
REV 01
710-021387
DN7030
CRAFT-T1600-S
CIP
REV 06
710-002895
DM3962
CIP-L-T640-S
PEM 0
Rev 08
740-017906
UD26519
PWR-T1600-3-80-DC-S
PEM 1
Rev 07
740-017906
UC26601
PWR-T1600-3-80-DC-S
SCG 0
REV 15
710-003423
DP0277
SCG-T-S
CB 0
REV 06
710-022597
DW8524
CB-LCC
CB 1
REV 06
710-022597
DW8536
CB-LCC
FPC 4
REV 12
710-013037
DR1194
T1600-FPC4-ES
PIC 0
REV 11
750-017405
DP8811
PD-4XGE-XFP
PIC 1
REV 11
750-017405
DP8823
PD-4XGE-XFP
FPC 5
REV 12
710-013037
DR1184
T1600-FPC4-ES
PIC 1
REV 11
750-017405
DP4744
PD-4XGE-XFP
FPC 6
REV 12
710-013037
DN8622
T1600-FPC4-ES
PIC 0
REV 14
750-012518
JY9924
PD-4OC192-SON-XFP
PIC 1
REV 11
750-017405
DP8776
PD-4XGE-XFP
FPC 7
REV 04
710-013560
JR3968
T640-FPC3-E2
PIC 0
REV 16
750-007141
NC9330
PC-10GE-SFP
SIB 0
REV 07
710-022594
DW4217
SIB-TXP-T1600-S
SIB 1
REV 07
710-022594
DW4213
SIB-TXP-T1600-S
SIB 2
REV 07
710-022594
DW4189
SIB-TXP-T1600-S
SIB 3
REV 07
710-022594
DW4173
SIB-TXP-T1600-S
SIB 4
REV 07
710-022594
DW4201
SIB-TXP-T1600-S
Fan Tray 0
FANTRAY-T-S
Fan Tray 1
FANTRAY-T-S
Fan Tray 2
FANTRAY-TXP-R-S
lcc3-re0:
-------------------------------------------------------------------------Hardware inventory:
1442
Item
Midplane
FPM Display
CIP
PEM 0
PEM 1
SCG 0
CB 0
CB 1
FPC 0
PIC 0
PIC 1
FPC 1
PIC 0
PIC 1
FPC 2
PIC 0
PIC 1
FPC 4
PIC 0
FPC 5
PIC 0
FPC 7
PIC 0
PIC 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
Fan Tray 0
Fan Tray 1
Fan Tray 2
Version
REV 04
REV 01
REV 06
Rev 07
Rev 07
REV 15
REV 06
REV 06
REV 14
REV 13
REV 13
REV 14
REV 13
REV 13
REV 14
REV 13
REV 13
REV 10
REV 14
REV 14
REV 14
REV 07
REV 16
REV 13
REV 07
REV 07
REV 06
REV 07
REV 07
Part number
710-017247
710-021387
710-002895
740-017906
740-017906
710-003423
710-022597
710-022597
710-013037
750-017405
750-017405
710-013037
750-017405
750-017405
710-013037
750-017405
750-017405
710-010845
750-012518
710-013037
750-012518
710-013035
750-007141
750-004695
710-022594
710-022594
710-022594
710-022594
710-022594
Serial number
RC5319
DS6402
DR9973
UC26496
UC26599
DP5831
DW8533
DW8538
DS5345
DS7641
DS5479
DS7338
DS7631
DS7632
DS9962
DS7581
DS7627
JZ6573
JT5124
DT0016
JY9918
DM0967
JJ8059
DM5712
DW4174
DW4207
DT8231
DW4175
DW4209
1443
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 3
B Board
P Board
Xcvr 0
Xcvr 2
Xcvr 4
Xcvr 6
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 6
B Board
P Board
Xcvr 0
Xcvr 2
Xcvr 4
Xcvr 6
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 12
B Board
P Board
SIB F2S 0/0
B Board
SIB F2S 0/2
B Board
SIB F2S 0/4
B Board
SIB F2S 0/6
B Board
SIB F2S 1/0
B Board
SIB F2S 1/2
B Board
SIB F2S 1/4
B Board
SIB F2S 1/6
B Board
SIB F2S 2/0
B Board
SIB F2S 2/2
B Board
SIB F2S 2/4
B Board
SIB F2S 2/6
B Board
SIB F2S 3/0
B Board
SIB F2S 3/2
B Board
SIB F2S 3/4
B Board
Fan Tray 0
Fan Tray 1
1444
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
05
03
04
01
01
01
01
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
02
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
02
10
10
740-047547
740-047547
740-047547
740-047547
710-035001
711-035082
711-043544
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
750-035002
711-035082
711-043544
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
NON-JNPR
710-035001
711-035082
711-043544
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
750-034978
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
750-034978
711-034979
760-024497
760-024497
XB48FB00W
XB34FB01S
XB34FB03H
XB34FB023
EJ2612
EJ3815
EJ2678
XB48FB04C
XB48FB00Z
XB47FB036
XB47FB029
XB48FB02N
XB42FB0CS
XB47FB01X
XB48FB02F
EK2675
EK2612
EK1179
XB48FB01T
XB48FB02M
XB48FB031
XB48FB04P
XB48FB02T
XB34FB01V
XB48FB02C
EJ2631
EJ3808
EJ2676
EH9829
EH9927
EH9791
EH9852
EH9803
EH9915
EH9763
EH9880
EH9757
EH9889
EH9815
EH9890
EN1954
EN1436
EJ7054
EJ8238
EH9830
EH9844
EH9818
EH9888
EH9795
EH9869
EJ7026
EJ8273
EH9811
EH9892
EH9812
EH9877
EN1947
EN1471
EH3313
EH3290
CXP Module
CXP Module
CXP Module
CXP Module
F13 SIB 3D
F13 SIB 3D Mezz
F13 SIB 3D Power
CXP Module
CXP Module
CXP Module
CXP Module
CXP Module
CXP Module
CXP Module
CXP Module
F13 SIB 3D
F13 SIB 3D Mezz
F13 SIB 3D Power
CXP Module
CXP Module
CXP Module
CXP Module
CXP Module
CXP Module
CXP Module
No Module
F13 SIB 3D
F13 SIB 3D Mezz
F13 SIB 3D Power
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
F2S SIB 3D
F2S SIB 3D Mezz
Front Fan Tray
Front Fan Tray
Fan
Fan
Fan
Fan
Tray
Tray
Tray
Tray
2
3
4
5
REV
REV
REV
REV
10
10
10
10
760-024502
760-024502
760-024502
760-024502
EH3292
EH3287
EH3286
EH3285
Rear
Rear
Rear
Rear
Fan
Fan
Fan
Fan
Tray
Tray
Tray
Tray
lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11B23FEAHA
T1600
Midplane
REV 01
710-027486
RC9787
T-series Backplane
FPM GBUS
REV 13
710-002901
BBAG5132
T640 FPM Board
FPM Display
REV 04
710-021387
BBAL9612
T1600 FPM Display
CIP
REV 06
710-002895
BBAN0605
T-series CIP
PEM 0
REV 05
740-036442
1G022060143
Power Entry Module 6x60
PEM 1
REV 05
740-036442
1G022060011
Power Entry Module 6x60
SCG 0
REV 18
710-003423
BBAL7318
T640 Sonet Clock Gen.
SCG 1
REV 18
710-003423
BBAL7255
T640 Sonet Clock Gen.
Routing Engine 0 REV 07
740-026941
P737F-002933
RE-DUO-1800
Routing Engine 1 REV 06
740-026941
P737F-002749
RE-DUO-1800
CB 0
REV 11
710-022597
EH3611
LCC Control Board
CB 1
REV 11
710-022597
EH4798
LCC Control Board
FPC 5
REV 17
710-013037
BBAC5333
FPC Type 4-ES
CPU
REV 10
710-016744
BBAB7619
ST-PMB2
PIC 0
REV 18
750-017405
BBAE3420
4x 10GE (LAN/WAN) XFP
Xcvr 0
REV 03
740-014289
T10C90659
XFP-10G-SR
MMB 0
REV 05
710-025563
BBAB9538
ST-MMB2
MMB 1
REV 05
710-025563
BBAB9502
ST-MMB2
FPC 7
REV 01
750-045173
BBAV0032
FPC Type 5-3D
CPU
SPMB 0
REV 05
710-023321
EG9434
LCC Switch CPU
SPMB 1
REV 05
710-023321
EH3878
LCC Switch CPU
SIB 0
REV 01
750-041657
EH7997
LCC SIB 3D
B Board
REV 01
711-042424
EH7674
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB48FB014
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB05A
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB052
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB01B
CXP Module
SIB 1
REV 01
750-041657
EH8023
LCC SIB 3D
B Board
REV 01
711-042424
EH7659
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB48FB05J
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB01E
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB01J
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB02S
CXP Module
SIB 2
REV 03
750-041657
EJ6554
LCC SIB 3D
B Board
REV 02
711-042424
EJ5756
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB34FB01Z
CXP Module
Xcvr 2
REV 01
740-047547
XB34FB013
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB04Z
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB05N
CXP Module
Fan Tray 0
Front Top Fan Tray
Fan Tray 1
Front Bottom Fan Tray
Fan Tray 2
Rear Fan Tray -- Rev 4
lcc2-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11B3975AHA
T1600
Midplane
REV 01
710-027486
RC9826
T-series Backplane
FPM GBUS
REV 13
710-002901
BBAG5124
T640 FPM Board
1445
FPM Display
REV 03
CIP
REV 06
PEM 0
REV 05
PEM 1
REV 05
SCG 0
REV 18
SCG 1
REV 18
Routing Engine 0 REV 07
Routing Engine 1 REV 07
CB 0
REV 11
CB 1
REV 11
FPC 1
REV 01
CPU
REV 11
MMB 0
REV 06
FPC 5
REV 04
CPU
REV 11
PIC 1
REV 20
Xcvr 0
REV 03
MMB 0
REV 07
MMB 1
REV 07
SPMB 0
REV 05
SPMB 1
REV 05
SIB 0
REV 01
B Board
REV 01
Xcvr 0
REV 01
Xcvr 2
REV 01
Xcvr 4
REV 01
Xcvr 6
REV 01
SIB 1
REV 01
B Board
REV 01
Xcvr 0
REV 01
Xcvr 2
REV 01
Xcvr 4
REV 01
Xcvr 6
REV 01
SIB 2
REV 01
B Board
REV 01
Xcvr 0
REV 01
Xcvr 2
REV 01
Xcvr 4
REV 01
Xcvr 6
REV 01
Fan Tray 0
Fan Tray 1
Fan Tray 2
710-021387
710-002895
740-036442
740-036442
710-003423
710-003423
740-026941
740-026941
710-022597
710-022597
710-033873
710-016744
710-025563
710-033871
710-016744
750-017405
740-014289
710-025563
710-025563
710-023321
710-023321
750-041657
711-042424
740-047547
740-047547
740-047547
740-047547
750-041657
711-042424
740-047547
740-047547
740-047547
740-047547
750-041657
711-042424
740-047547
740-047547
740-047547
740-047547
BBAJ1112
BBAL3744
1G022060081
1G022060188
BBAH8775
BBAL7272
P737F-002992
P737F-002938
EH4805
EH4786
BBAH0320
BBAF3281
BBAF5061
BBAM5070
BBAM6653
BBAM1296
T10B42981
BBAN2631
BBAN2538
EH3903
EH3902
EH8019
EH7680
XB48FB04F
XB48FB04S
XB48FB04B
XB48FB043
EH8012
EH7658
XB48FB05E
XB48FB01Z
XB48FB018
XB48FB054
EH7993
EH7678
XB48FB05C
XB47FB00N
XB48FB05U
XB48FB05L
show chassis hardware clei-models (TX Matrix Plus router with 3D SIBs)
user@host> show chassis hardware clei-models
sfc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number CLEI code
FRU model number
Midplane
REV 05
710-022574
CHAS-BP-TXP-S
FPM Display
REV 09
710-024027
CRAFT-TXP-S
CIP 0
REV 12
710-023792
CIP-TXP-S
CIP 1
REV 12
710-023792
CIP-TXP-S
PEM 0
Rev 06
740-027463
IPUPAFGKTA
PWR-TXP-7-60-DC-S
Routing Engine 0 REV 07
740-026942
RE-DUO-C2600-16G-S
Routing Engine 1 REV 07
740-026942
RE-DUO-C2600-16G-S
CB 0
REV 13
710-022606
CB-TXP-S
CB 1
REV 14
710-022606
CB-TXP-S
SIB F13 0
REV 10
750-035002
PROTOXCLEI
SIB-TXP-3D-F13-S
Xcvr 0
REV 01
740-048813
1446
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 1
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 6
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
10
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
16
01
01
01
01
01
01
01
01
01
01
01
01
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-047547
740-047547
740-047547
740-047547
750-035002
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
750-035002
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-047547
740-047547
740-047547
740-047547
PROTOXCLEI
PROTOXCLEI
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
SIB-TXP-3D-F13-S
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
SIB-TXP-3D-F13
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
1447
SIB F13 7
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 9
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 11
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 12
Xcvr 14
SIB F13 12
Xcvr 0
Xcvr 1
Xcvr 2
Xcvr 3
Xcvr 4
Xcvr 5
Xcvr 6
Xcvr 7
Xcvr 8
Xcvr 10
1448
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
10
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
16
01
01
01
01
01
01
01
01
01
01
01
01
10
01
01
01
01
01
01
01
01
01
01
01
16
01
01
01
01
01
01
01
01
01
01
750-035002
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-048813
740-048813
740-048813
740-048813
740-048813
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
750-035002
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
750-035002
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-047547
740-048813
740-047547
740-047547
740-047547
750-035002
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
740-047547
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
SIB-TXP-3D-F13-S
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
SIB-TXP-3D-F13
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
750-035002
CXP-TXP-3D
PROTOXCLEI
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
SIB-TXP-3D-F13
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
CXP-TXP-3D
Xcvr 12
Xcvr 14
SIB F2S 0/0
SIB F2S 0/2
SIB F2S 0/4
SIB F2S 0/6
SIB F2S 1/0
SIB F2S 1/2
SIB F2S 1/4
SIB F2S 1/6
SIB F2S 2/0
SIB F2S 2/2
SIB F2S 2/4
SIB F2S 2/6
SIB F2S 3/0
SIB F2S 3/2
SIB F2S 3/4
SIB F2S 3/6
SIB F2S 4/0
SIB F2S 4/2
SIB F2S 4/4
SIB F2S 4/6
Fan Tray 0
Fan Tray 1
Fan Tray 2
Fan Tray 3
Fan Tray 4
Fan Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
06
07
06
06
07
07
07
08
06
06
07
06
07
06
06
06
07
06
06
06
10
10
10
10
10
10
740-047547
740-047547
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
750-034978
760-024497
760-024497
760-024502
760-024502
760-024502
760-024502
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
CXP-TXP-3D
CXP-TXP-3D
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
SIB-TXP-3D-F2S
FANTRAY-TXP-H-S
FANTRAY-TXP-H-S
FANTRAY-TXP-V-S
FANTRAY-TXP-V-S
FANTRAY-TXP-V-S
FANTRAY-TXP-V-S
lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number CLEI code
FRU model number
Midplane
REV 01
710-027486
IPMJ700DRD
CHAS-BP-T1600-S
FPM Display
REV 04
710-021387
CRAFT-T1600-S
CIP
REV 06
710-002895
CIP-L-T640-S
PEM 0
REV 05
740-036442
IPUPAG6KAA
PWR-T-6-60-DC-S
PEM 1
REV 05
740-036442
IPUPAG6KAA
PWR-T-6-60-DC-S
SCG 0
REV 18
710-003423
SCG-T-S
SCG 1
REV 18
710-003423
SCG-T-S
Routing Engine 0 REV 10
740-026941
RE-DUO-C1800-8G-S
Routing Engine 1 REV 07
740-026941
RE-DUO-C1800-8G-S
CB 0
REV 11
710-022597
CB-LCC-S
CB 1
REV 11
710-022597
CB-LCC-S
FPC 0
REV 01
750-045173
IP9IAL4DAB
T4000-FPC5-3D
PIC 0
REV 17
750-034624
IP9IAL2DAA
PF-12XGE-SFPP
PIC 1
REV 17
750-034624
IP9IAL2DAA
PF-12XGE-SFPP
FPC 3
REV 01
750-045173
IP9IAL4DAB
T4000-FPC5-3D
PIC 0
REV 13
750-033423
XXXXXXXXDD
PF-12-24XGE-SFPP
FPC 4
REV 02
750-045173
IP9IAL4DAC
T4000-FPC5-3D
PIC 0
REV 17
750-034624
IP9IAL2DAA
PF-12XGE-SFPP
PIC 1
REV 17
750-034624
IP9IAL2DAA
PF-12XGE-SFPP
FPC 5
REV 01
750-045173
IP9IAL4DAB
T4000-FPC5-3D
PIC 0
REV 17
750-034624
IP9IAL2DAA
PF-12XGE-SFPP
PIC 1
REV 17
750-034624
IP9IAL2DAA
PF-12XGE-SFPP
FPC 6
REV 01
750-045173
IP9IAL4DAB
T4000-FPC5-3D
PIC 0
REV 17
750-034624
IP9IAL2DAA
PF-12XGE-SFPP
PIC 1
REV 10
750-035293
IP9IAL3DAA
PF-1CGE-CFP
SIB 0
REV 06
750-041657
PROTOXCLEI
SIB-TXP-3D-LCC
Xcvr 0
REV 01
740-048813
Xcvr 1
REV 01
740-048813
1449
Xcvr 2
REV
Xcvr 3
REV
Xcvr 4
REV
Xcvr 5
REV
Xcvr 6
REV
Xcvr 7
REV
SIB 1
REV
Xcvr 0
REV
Xcvr 1
REV
Xcvr 2
REV
Xcvr 3
REV
Xcvr 4
REV
Xcvr 5
REV
Xcvr 6
REV
Xcvr 7
REV
SIB 2
REV
Xcvr 0
REV
Xcvr 1
REV
Xcvr 2
REV
Xcvr 3
REV
Xcvr 4
REV
Xcvr 5
REV
Xcvr 6
REV
Xcvr 7
REV
SIB 3
REV
Xcvr 0
REV
Xcvr 1
REV
Xcvr 2
REV
Xcvr 3
REV
Xcvr 4
REV
Xcvr 5
REV
Xcvr 6
REV
Xcvr 7
REV
SIB 4
REV
Xcvr 0
REV
Xcvr 1
REV
Xcvr 2
REV
Xcvr 3
REV
Xcvr 4
REV
Xcvr 5
REV
Xcvr 6
REV
Xcvr 7
REV
Fan Tray 0
Fan Tray 1
Fan Tray 2
[Output Truncated]
01
01
01
01
01
01
06
01
01
01
01
01
01
01
01
06
01
01
01
01
01
01
01
01
07
01
01
01
01
01
01
01
01
06
01
01
01
01
01
01
01
01
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
750-041657
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
750-041657
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
750-041657
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
750-041657
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
740-048813
PROTOXCLEI
SIB-TXP-3D-LCC
PROTOXCLEI
SIB-TXP-3D-LCC
PROTOXCLEI
SIB-TXP-3D-LLC
PROTOXCLEI
SIB-TXP-3D-LCC
FANTRAY-T-S
FANTRAY-T-S
FANTRAY-TXP3D-LCC-R-S
show chassis hardware detail (TX Matrix Plus router with 3D SIBs)
user@host> show chassis hardware detail
sfc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11CAAA4AHB
TXP
Midplane
REV 05
710-022574
ABAC4696
SFC Midplane
FPM Display
REV 09
710-024027
EH3138
TXP FPM Display
CIP 0
REV 12
710-023792
EF6349
TXP CIP
CIP 1
REV 12
710-023792
EG5294
TXP CIP
PEM 0
Rev 06
740-027463
XH04595
Power Entry Module
PEM 1
Rev 06
740-027463
XH04592
Power Entry Module
1450
Routing Engine 0
ad0
3823 MB
ad1
62720 MB
Routing Engine 1
ad0
3823 MB
ad1
62720 MB
CB 0
CB 1
SPMB 0
SPMB 1
SIB F13 0
B Board
P Board
Xcvr 0
Xcvr 2
Xcvr 4
Xcvr 6
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 3
B Board
P Board
Xcvr 0
Xcvr 2
Xcvr 4
Xcvr 6
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 6
B Board
P Board
Xcvr 0
Xcvr 2
Xcvr 4
Xcvr 6
Xcvr 8
Xcvr 10
Xcvr 12
Xcvr 14
SIB F13 12
B Board
P Board
SIB F2S 0/0
B Board
SIB F2S 0/2
B Board
SIB F2S 0/4
B Board
SIB F2S 0/6
B Board
SIB F2S 1/0
B Board
SIB F2S 1/2
B Board
SIB F2S 1/4
B Board
SIB F2S 1/6
REV 07
SMART
SMART
REV 07
SMART
SMART
REV 15
REV 15
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
10
06
05
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
05
03
04
01
01
01
01
01
01
01
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
02
01
740-026942
P737A-002541
RE-DUO-2600
CF
2011030400062C132C13 Compact Flash
Lite SATA Drive 201105100009A452A452 Disk 1
740-026942
P737A-002602
RE-DUO-2600
CF
20110508085EE471E471 Compact Flash
Lite SATA Drive 201110210089DF39DF39 Disk 1
710-022606
EH4376
SFC Control Board
710-022606
EH4379
SFC Control Board
BUILTIN
SFC Switch CPU
BUILTIN
SFC Switch CPU
750-035002
EM9305
F13 SIB 3D
711-035082
EM9667
F13 SIB 3D Mezz
711-043544
EM9708
F13 SIB 3D Power
740-047547
XB34FB00S
CXP Module
740-047547
XB48FB01H
CXP Module
740-047547
XB34FB02W
CXP Module
740-047547
XB34FB01T
CXP Module
740-047547
XB48FB00W
CXP Module
740-047547
XB34FB01S
CXP Module
740-047547
XB34FB03H
CXP Module
740-047547
XB34FB023
CXP Module
710-035001
EJ2612
F13 SIB 3D
711-035082
EJ3815
F13 SIB 3D Mezz
711-043544
EJ2678
F13 SIB 3D Power
740-047547
XB48FB04C
CXP Module
740-047547
XB48FB00Z
CXP Module
740-047547
XB47FB036
CXP Module
740-047547
XB47FB029
CXP Module
740-047547
XB48FB02N
CXP Module
740-047547
XB42FB0CS
CXP Module
740-047547
XB47FB01X
CXP Module
740-047547
XB48FB02F
CXP Module
750-035002
EK2675
F13 SIB 3D
711-035082
EK2612
F13 SIB 3D Mezz
711-043544
EK1179
F13 SIB 3D Power
740-047547
XB48FB01T
CXP Module
740-047547
XB48FB02M
CXP Module
740-047547
XB48FB031
CXP Module
740-047547
XB48FB04P
CXP Module
740-047547
XB48FB02T
CXP Module
740-047547
XB34FB01V
CXP Module
740-047547
XB48FB02C
CXP Module
NON-JNPR
No Module
710-035001
EJ2631
F13 SIB 3D
711-035082
EJ3808
F13 SIB 3D Mezz
711-043544
EJ2676
F13 SIB 3D Power
711-034977
EH9829
F2S SIB 3D
711-034979
EH9927
F2S SIB 3D Mezz
711-034977
EH9791
F2S SIB 3D
711-034979
EH9852
F2S SIB 3D Mezz
711-034977
EH9803
F2S SIB 3D
711-034979
EH9915
F2S SIB 3D Mezz
711-034977
EH9763
F2S SIB 3D
711-034979
EH9880
F2S SIB 3D Mezz
711-034977
EH9757
F2S SIB 3D
711-034979
EH9889
F2S SIB 3D Mezz
711-034977
EH9815
F2S SIB 3D
711-034979
EH9890
F2S SIB 3D Mezz
750-034978
EN1954
F2S SIB 3D
711-034979
EN1436
F2S SIB 3D Mezz
711-034977
EJ7054
F2S SIB 3D
1451
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
Fan
Fan
Fan
Fan
Fan
Fan
Board
F2S 2/0
Board
F2S 2/2
Board
F2S 2/4
Board
F2S 2/6
Board
F2S 3/0
Board
F2S 3/2
Board
F2S 3/4
Board
Tray 0
Tray 1
Tray 2
Tray 3
Tray 4
Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
01
01
08
02
10
10
10
10
10
10
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
750-034978
711-034979
760-024497
760-024497
760-024502
760-024502
760-024502
760-024502
EJ8238
EH9830
EH9844
EH9818
EH9888
EH9795
EH9869
EJ7026
EJ8273
EH9811
EH9892
EH9812
EH9877
EN1947
EN1471
EH3313
EH3290
EH3292
EH3287
EH3286
EH3285
lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11B23FEAHA
T1600
Midplane
REV 01
710-027486
RC9787
T-series Backplane
FPM GBUS
REV 13
710-002901
BBAG5132
T640 FPM Board
FPM Display
REV 04
710-021387
BBAL9612
T1600 FPM Display
CIP
REV 06
710-002895
BBAN0605
T-series CIP
PEM 0
REV 05
740-036442
1G022060143
Power Entry Module 6x60
PEM 1
REV 05
740-036442
1G022060011
Power Entry Module 6x60
SCG 0
REV 18
710-003423
BBAL7318
T640 Sonet Clock Gen.
SCG 1
REV 18
710-003423
BBAL7255
T640 Sonet Clock Gen.
Routing Engine 0 REV 07
740-026941
P737F-002933
RE-DUO-1800
ad0
3823 MB SMART CF
201103030490604E604E Compact Flash
ad1
62720 MB SMART Lite SATA Drive 20110729028B11D411D4 Disk 1
Routing Engine 1 REV 06
740-026941
P737F-002749
RE-DUO-1800
ad0
3823 MB SMART CF
2011010504EB99649964 Compact Flash
ad1
62720 MB SMART Lite SATA Drive 201102140058934A934A Disk 1
CB 0
REV 11
710-022597
EH3611
LCC Control Board
CB 1
REV 11
710-022597
EH4798
LCC Control Board
FPC 5
REV 17
710-013037
BBAC5333
FPC Type 4-ES
CPU
REV 10
710-016744
BBAB7619
ST-PMB2
PIC 0
REV 18
750-017405
BBAE3420
4x 10GE (LAN/WAN) XFP
Xcvr 0
REV 03
740-014289
T10C90659
XFP-10G-SR
MMB 0
REV 05
710-025563
BBAB9538
ST-MMB2
MMB 1
REV 05
710-025563
BBAB9502
ST-MMB2
FPC 7
REV 01
750-045173
BBAV0032
FPC Type 5-3D
CPU
SPMB 0
REV 05
710-023321
EG9434
LCC Switch CPU
SPMB 1
REV 05
710-023321
EH3878
LCC Switch CPU
SIB 0
REV 01
750-041657
EH7997
LCC SIB 3D
B Board
REV 01
711-042424
EH7674
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB48FB014
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB05A
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB052
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB01B
CXP Module
SIB 1
REV 01
750-041657
EH8023
LCC SIB 3D
B Board
REV 01
711-042424
EH7659
LCC SIB 3D Mezz
1452
Xcvr 0
Xcvr 2
Xcvr 4
Xcvr 6
SIB 2
B Board
Xcvr 0
Xcvr 2
Xcvr 4
Xcvr 6
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
03
02
01
01
01
01
740-047547
740-047547
740-047547
740-047547
750-041657
711-042424
740-047547
740-047547
740-047547
740-047547
XB48FB05J
XB48FB01E
XB48FB01J
XB48FB02S
EJ6554
EJ5756
XB34FB01Z
XB34FB013
XB48FB04Z
XB48FB05N
CXP Module
CXP Module
CXP Module
CXP Module
LCC SIB 3D
LCC SIB 3D Mezz
CXP Module
CXP Module
CXP Module
CXP Module
Front Top Fan Tray
Front Bottom Fan Tray
Rear Fan Tray -- Rev 4
lcc2-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11B3975AHA
T1600
Midplane
REV 01
710-027486
RC9826
T-series Backplane
FPM GBUS
REV 13
710-002901
BBAG5124
T640 FPM Board
FPM Display
REV 03
710-021387
BBAJ1112
T1600 FPM Display
CIP
REV 06
710-002895
BBAL3744
T-series CIP
PEM 0
REV 05
740-036442
1G022060081
Power Entry Module 6x60
PEM 1
REV 05
740-036442
1G022060188
Power Entry Module 6x60
SCG 0
REV 18
710-003423
BBAH8775
T640 Sonet Clock Gen.
SCG 1
REV 18
710-003423
BBAL7272
T640 Sonet Clock Gen.
Routing Engine 0 REV 07
740-026941
P737F-002992
RE-DUO-1800
ad0
3823 MB SMART CF
201103030356329E329E Compact Flash
ad1
62720 MB SMART Lite SATA Drive 2011051000488D8B8D8B Disk 1
Routing Engine 1 REV 07
740-026941
P737F-002938
RE-DUO-1800
ad0
3823 MB SMART CF
20110304000F02680268 Compact Flash
ad1
62720 MB SMART Lite SATA Drive 201105300A70F325F325 Disk 1
CB 0
REV 11
710-022597
EH4805
LCC Control Board
CB 1
REV 11
710-022597
EH4786
LCC Control Board
FPC 1
REV 01
710-033873
BBAH0320
FPC Type 3-ES
CPU
REV 11
710-016744
BBAF3281
ST-PMB2
MMB 0
REV 06
710-025563
BBAF5061
ST-MMB2
FPC 5
REV 04
710-033871
BBAM5070
FPC Type 4-ES
CPU
REV 11
710-016744
BBAM6653
ST-PMB2
PIC 1
REV 20
750-017405
BBAM1296
4x 10GE (LAN/WAN) XFP
Xcvr 0
REV 03
740-014289
T10B42981
XFP-10G-SR
MMB 0
REV 07
710-025563
BBAN2631
ST-MMB2
MMB 1
REV 07
710-025563
BBAN2538
ST-MMB2
SPMB 0
REV 05
710-023321
EH3903
LCC Switch CPU
SPMB 1
REV 05
710-023321
EH3902
LCC Switch CPU
SIB 0
REV 01
750-041657
EH8019
LCC SIB 3D
B Board
REV 01
711-042424
EH7680
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB48FB04F
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB04S
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB04B
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB043
CXP Module
SIB 1
REV 01
750-041657
EH8012
LCC SIB 3D
B Board
REV 01
711-042424
EH7658
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB48FB05E
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB01Z
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB018
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB054
CXP Module
SIB 2
REV 01
750-041657
EH7993
LCC SIB 3D
B Board
REV 01
711-042424
EH7678
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB48FB05C
CXP Module
1453
Xcvr 2
Xcvr 4
Xcvr 6
Fan Tray 0
Fan Tray 1
Fan Tray 2
REV 01
REV 01
REV 01
740-047547
740-047547
740-047547
XB47FB00N
XB48FB05U
XB48FB05L
CXP Module
CXP Module
CXP Module
Front Top Fan Tray
Front Bottom Fan Tray
Rear Fan Tray -- Rev 4
show chassis hardware lcc (TX Matrix Plus router with 3D SIBs)
user@host> show chassis hardware lcc 0
lcc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11B23FEAHA
T1600
Midplane
REV 01
710-027486
RC9787
T-series Backplane
FPM GBUS
REV 13
710-002901
BBAG5132
T640 FPM Board
FPM Display
REV 04
710-021387
BBAL9612
T1600 FPM Display
CIP
REV 06
710-002895
BBAN0605
T-series CIP
PEM 0
REV 05
740-036442
1G022060143
Power Entry Module 6x60
PEM 1
REV 05
740-036442
1G022060011
Power Entry Module 6x60
SCG 0
REV 18
710-003423
BBAL7318
T640 Sonet Clock Gen.
SCG 1
REV 18
710-003423
BBAL7255
T640 Sonet Clock Gen.
Routing Engine 0 REV 07
740-026941
P737F-002933
RE-DUO-1800
Routing Engine 1 REV 06
740-026941
P737F-002749
RE-DUO-1800
CB 0
REV 11
710-022597
EH3611
LCC Control Board
CB 1
REV 11
710-022597
EH4798
LCC Control Board
FPC 5
REV 17
710-013037
BBAC5333
FPC Type 4-ES
CPU
REV 10
710-016744
BBAB7619
ST-PMB2
PIC 0
REV 18
750-017405
BBAE3420
4x 10GE (LAN/WAN) XFP
Xcvr 0
REV 03
740-014289
T10C90659
XFP-10G-SR
MMB 0
REV 05
710-025563
BBAB9538
ST-MMB2
MMB 1
REV 05
710-025563
BBAB9502
ST-MMB2
FPC 7
REV 01
750-045173
BBAV0032
FPC Type 5-3D
CPU
SPMB 0
REV 05
710-023321
EG9434
LCC Switch CPU
SPMB 1
REV 05
710-023321
EH3878
LCC Switch CPU
SIB 0
REV 01
750-041657
EH7997
LCC SIB 3D
B Board
REV 01
711-042424
EH7674
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB48FB014
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB05A
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB052
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB01B
CXP Module
SIB 1
REV 01
750-041657
EH8023
LCC SIB 3D
B Board
REV 01
711-042424
EH7659
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB48FB05J
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB01E
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB01J
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB02S
CXP Module
SIB 2
REV 03
750-041657
EJ6554
LCC SIB 3D
B Board
REV 02
711-042424
EJ5756
LCC SIB 3D Mezz
Xcvr 0
REV 01
740-047547
XB34FB01Z
CXP Module
Xcvr 2
REV 01
740-047547
XB34FB013
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB04Z
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB05N
CXP Module
Fan Tray 0
Front Top Fan Tray
Fan Tray 1
Front Bottom Fan Tray
Fan Tray 2
Rear Fan Tray -- Rev 4
1454
show chassis hardware sfc (TX Matrix Plus router with 3D SIBs)
user@host> show chassis hardware sfc 0
sfc0-re0:
-------------------------------------------------------------------------Hardware inventory:
Item
Version Part number Serial number
Description
Chassis
JN11CAAA4AHB
TXP
Midplane
REV 05
710-022574
ABAC4696
SFC Midplane
FPM Display
REV 09
710-024027
EH3138
TXP FPM Display
CIP 0
REV 12
710-023792
EF6349
TXP CIP
CIP 1
REV 12
710-023792
EG5294
TXP CIP
PEM 0
Rev 06
740-027463
XH04595
Power Entry Module
PEM 1
Rev 06
740-027463
XH04592
Power Entry Module
Routing Engine 0 REV 07
740-026942
P737A-002541
RE-DUO-2600
Routing Engine 1 REV 07
740-026942
P737A-002602
RE-DUO-2600
CB 0
REV 15
710-022606
EH4376
SFC Control Board
CB 1
REV 15
710-022606
EH4379
SFC Control Board
SPMB 0
BUILTIN
SFC Switch CPU
SPMB 1
BUILTIN
SFC Switch CPU
SIB F13 0
REV 10
750-035002
EM9305
F13 SIB 3D
B Board
REV 06
711-035082
EM9667
F13 SIB 3D Mezz
P Board
REV 05
711-043544
EM9708
F13 SIB 3D Power
Xcvr 0
REV 01
740-047547
XB34FB00S
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB01H
CXP Module
Xcvr 4
REV 01
740-047547
XB34FB02W
CXP Module
Xcvr 6
REV 01
740-047547
XB34FB01T
CXP Module
Xcvr 8
REV 01
740-047547
XB48FB00W
CXP Module
Xcvr 10
REV 01
740-047547
XB34FB01S
CXP Module
Xcvr 12
REV 01
740-047547
XB34FB03H
CXP Module
Xcvr 14
REV 01
740-047547
XB34FB023
CXP Module
SIB F13 3
REV 01
710-035001
EJ2612
F13 SIB 3D
B Board
REV 01
711-035082
EJ3815
F13 SIB 3D Mezz
P Board
REV 01
711-043544
EJ2678
F13 SIB 3D Power
Xcvr 0
REV 01
740-047547
XB48FB04C
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB00Z
CXP Module
Xcvr 4
REV 01
740-047547
XB47FB036
CXP Module
Xcvr 6
REV 01
740-047547
XB47FB029
CXP Module
Xcvr 8
REV 01
740-047547
XB48FB02N
CXP Module
Xcvr 10
REV 01
740-047547
XB42FB0CS
CXP Module
Xcvr 12
REV 01
740-047547
XB47FB01X
CXP Module
Xcvr 14
REV 01
740-047547
XB48FB02F
CXP Module
SIB F13 6
REV 05
750-035002
EK2675
F13 SIB 3D
B Board
REV 03
711-035082
EK2612
F13 SIB 3D Mezz
P Board
REV 04
711-043544
EK1179
F13 SIB 3D Power
Xcvr 0
REV 01
740-047547
XB48FB01T
CXP Module
Xcvr 2
REV 01
740-047547
XB48FB02M
CXP Module
Xcvr 4
REV 01
740-047547
XB48FB031
CXP Module
Xcvr 6
REV 01
740-047547
XB48FB04P
CXP Module
Xcvr 8
REV 01
740-047547
XB48FB02T
CXP Module
Xcvr 10
REV 01
740-047547
XB34FB01V
CXP Module
Xcvr 12
REV 01
740-047547
XB48FB02C
CXP Module
Xcvr 14
NON-JNPR
No Module
SIB F13 12
REV 01
710-035001
EJ2631
F13 SIB 3D
B Board
REV 01
711-035082
EJ3808
F13 SIB 3D Mezz
P Board
REV 01
711-043544
EJ2676
F13 SIB 3D Power
SIB F2S 0/0
REV 01
711-034977
EH9829
F2S SIB 3D
B Board
REV 01
711-034979
EH9927
F2S SIB 3D Mezz
SIB F2S 0/2
REV 01
711-034977
EH9791
F2S SIB 3D
B Board
REV 01
711-034979
EH9852
F2S SIB 3D Mezz
SIB F2S 0/4
REV 01
711-034977
EH9803
F2S SIB 3D
1455
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
SIB
B
Fan
Fan
Fan
Fan
Fan
Fan
Board
F2S 0/6
Board
F2S 1/0
Board
F2S 1/2
Board
F2S 1/4
Board
F2S 1/6
Board
F2S 2/0
Board
F2S 2/2
Board
F2S 2/4
Board
F2S 2/6
Board
F2S 3/0
Board
F2S 3/2
Board
F2S 3/4
Board
Tray 0
Tray 1
Tray 2
Tray 3
Tray 4
Tray 5
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
08
02
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
02
10
10
10
10
10
10
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
750-034978
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
711-034977
711-034979
750-034978
711-034979
760-024497
760-024497
760-024502
760-024502
760-024502
760-024502
EH9915
EH9763
EH9880
EH9757
EH9889
EH9815
EH9890
EN1954
EN1436
EJ7054
EJ8238
EH9830
EH9844
EH9818
EH9888
EH9795
EH9869
EJ7026
EJ8273
EH9811
EH9892
EH9812
EH9877
EN1947
EN1471
EH3313
EH3290
EH3292
EH3287
EH3286
EH3285
show chassis hardware (16-Port 10-Gigabit Ethernet MPC with SFP+ Optics [MX Series Routers])
user@host> show chassis hardware
Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 03
710-013698
FPM Board
REV 03
710-014974
PDM
Rev 03
Module
PEM 0
Rev 04
in
PEM 1
Rev 04
in
PEM 2
Rev 04
in
Routing Engine 0 REV 07
Routing Engine 1 REV 07
CB 0
REV 03
CB 1
REV 03
CB 2
REV 03
FPC 4
REV 02
CPU
REV 02
PIC 0
PIC 1
PIC 2
PIC 3
1456
740-013110
Serial number
JN112D865AFA
TS3339
WW6267
Description
MX960
MX960 Backplane
Front Panel Display
QCS12485026
Power Distribution
740-013682
QCS12434086
PS 1.7kW; 200-240VAC
740-013682
QCS1243408Z
PS 1.7kW; 200-240VAC
740-013682
QCS1243407X
PS 1.7kW; 200-240VAC
9009009677
9009011510
XF0394
XF0550
XD7455
JR6127
JX0129
BUILTIN
BUILTIN
BUILTIN
BUILTIN
RE-S-1300
RE-S-1300
MX SCB
MX SCB
MX SCB
MPC M 16x 10GE
AS PMB
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
4x 10GE(LAN) SFP+
740-015113
740-015113
710-021523
710-021523
710-021523
750-028467
711-029089
BUILTIN
BUILTIN
BUILTIN
BUILTIN
Fan Tray 0
Fan Tray 1
REV 05
REV 05
740-014971
740-014971
TP9990
VS1709
Fan Tray
Fan Tray
Serial number
JN1101AFEAFB
TR4444
KG6056
Description
MX480
MX480 Midplane
Front Panel Display
Rev 03
740-017330
QCS082090FC
PS 1.2-1.7kW; 100-240V
PEM 1
Rev 03
740-017330
QCS082090FD
PS 1.2-1.7kW; 100-240V
9009004124
9009005569
XZ3587
KH8306
P1240
YL0504
YX4495
BUILTIN
C22CQNE
KH0045
KF5448
BUILTIN
PF21JHU
BUILTIN
AM0813S8ZL6
BUILTIN
PGL2KYF
AM0806S8N4P
BUILTIN
AM0815S967N
AM0806S8N1X
AM0815S967J
AM0815S967M
YR9443
YL6931
YR3269
BUILTIN
ULH0KG3
YG3245
BUILTIN
ULH0KGF
YR9437
YT5857
YR3295
BUILTIN
X12000187
YX4518
BUILTIN
X12J00008
JW9769
JR6158
JR6197
BUILTIN
T07M71112
T08L85610
RE-S-2000
RE-S-2000
MX SCB
MX SCB
MPC Type 3
HMPC PMB 2G
1X100GE CFP
1X100GE CFP
CFP-100G-LR4
DPCE 40x 1GE R EQ
DPC PMB
10x 1GE(LAN) EQ
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
10x 1GE(LAN) EQ
SFP-SX
SFP-SX
SFP-SX
SFP-SX
MPC Type 3
HMPC PMB 2G
1X100GE CFP
1X100GE CFP
CFP-100G-LR4
1X100GE CFP
1X100GE CFP
CFP-100G-LR4
MPC Type 3
HMPC PMB 2G
1X100GE CFP
1X100GE CFP
CFP-100G-SR10
1X100GE CFP
1X100GE CFP
CFP-100G-SR10
MPC Type 2 3D EQ
MPC PMB 2G Proto
3D 4x 10GE XFP
2x 10GE XFP
XFP-10G-SR
XFP-10G-SR
1457
PIC 1
MIC 1
REV 22
PIC 2
Xcvr 0
Xcvr 1
PIC 3
Xcvr 5
Xcvr 9
Fan Tray
REV 01
REV 01
REV 01
REV 02
BUILTIN
750-028392
BUILTIN
YM0053
2x 10GE XFP
3D 20x 1GE(LAN) SFP
BUILTIN
740-011613
740-011613
BUILTIN
740-013111
740-013111
BUILTIN
AM0703S005B
E07L01352
BUILTIN
6500217
8499527
The PIC number for MIC 1 always starts from 2 (even if the first MIC is a 1X100GE CFP or
a legacy MIC).
show chassis hardware (QFX3500 Switches)
user@switch> show chassis hardware
Hardware inventory:
Item
Version Part number
Chassis
Routing Engine 0
BUILTIN
FPC 0
REV 04
750-044071
CPU
BUILTIN
PIC 0
BUILTIN
PIC 1
BUILTIN
MGMT BRD
REV 02
750-044063
Xcvr 0
REV 01
740-011614
Xcvr 1
REV 02
740-013111
Power Supply 0
Rev 04
740-032091
Power Supply 1
REV 00
740-041741
Fan Tray 0
Front Airlfow
Fan Tray 1
Front Airlfow
Fan Tray 2
Front Airlfow
Serial number
BUILTIN
BBAR3902
BUILTIN
BUILTIN
BUILTIN
BBAR0398
AC0946S0BD1
A281922
UI00677
VJ00162
Description
QFX3500
QFX Routing Engine
QFX3500-48S4Q-AFI
FPC CPU
48x 10G-SFP+
15x 10G-SFP+
QFX3500-MGMT-SFP-AFO
SFP-LX10
SFP-T
JPSU-650W-AC-AFI
JPSU-650W-AC-AFO
QFX Fan Tray, Back to
QFX Fan Tray, Back to
QFX Fan Tray, Back to
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
1458
0
1
2
3
4
5
6
7
8
9
10
11
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
01
01
01
01
01
01
BUILTIN
BUILTIN
740-030589
740-030589
740-030589
740-030589
740-030589
740-030589
740-030589
740-030589
740-030589
740-030589
740-030589
740-030589
Serial number
JN000TEST5
BUILTIN
EE0823
Description
QFX3500
QFX Routing Engine
QFX3500-48S4Q-AFI
BUILTIN
BUILTIN
S99E270079
S9AK450099
S99E270078
S9AK450098
S99E270075
S9AK450093
S9AK450097
S9AK450095
S99E270072
S99E270073
S99E270080
S9AK450169
FPC CPU
48x 10G-SFP+
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
Xcvr 12
REV 01
740-030589
S99E270076
Xcvr 13
REV 01
740-030589
S9AK450167
Xcvr 14
REV 01
740-030589
S9AK450170
Xcvr 15
REV 01
740-030589
S9AK450166
Xcvr 16
REV 01
740-030589
S9AK450092
Xcvr 17
REV 01
740-030589
S9AK450163
Xcvr 18
REV 01
740-030589
S9AK450094
Xcvr 19
REV 01
740-030589
S9AK450100
Xcvr 20
REV 01
740-030589
S9AK450168
Xcvr 21
REV 01
740-030589
S9AK450165
Xcvr 22
REV 01
740-030589
S9AK450073
Xcvr 23
REV 01
740-030589
S9AK450164
Xcvr 24
REV 01
740-030589
S9AK450074
Xcvr 25
REV 01
740-030589
SA62270195
Xcvr 26
REV 01
740-030589
S9AK450078
Xcvr 27
REV 01
740-030589
S9AK450024
Xcvr 28
REV 01
740-030589
S9AK450027
Xcvr 29
REV 01
740-030589
S9AK450080
Xcvr 30
REV 01
740-030589
S9AK450030
Xcvr 31
REV 01
740-030589
S9AK450025
Xcvr 32
REV 01
740-030589
S9AK450023
Xcvr 33
REV 01
740-030589
S9AK450075
Xcvr 34
REV 01
740-030589
S9AK450161
Xcvr 35
REV 01
740-030589
S9AK450071
Xcvr 36
REV 01
740-030589
S9AK450072
Xcvr 37
REV 01
740-030589
S9AK450022
Xcvr 38
REV 01
740-030589
S9AK450021
Xcvr 39
REV 01
740-030589
S9AK450175
Xcvr 40
REV 01
740-030589
S9AK450162
Xcvr 41
REV 01
740-030589
S99E270074
Xcvr 42
REV 01
740-030589
S9AK450174
Xcvr 43
REV 01
740-030589
S9AK450077
Xcvr 44
REV 01
740-030589
S9AK450076
Xcvr 45
REV 01
740-030589
S9AK450026
Xcvr 46
REV 01
740-030589
S9AK450079
Xcvr 47
REV 01
740-030589
S9AK450029
PIC 1
BUILTIN
BUILTIN
Xcvr 1
REV 01
740-032986
QA170087
Xcvr 4
REV 01
740-032986
QA360442
Xcvr 8
REV 01
740-032986
QA170091
Xcvr 12
REV 01
740-032986
QA170042
MGMT BRD
REV 08
750-036946
EE0731
Power Supply 0
Rev 04
740-032091
UI00690
Power Supply 1
Rev 04
740-032091
UI00679
Fan Tray 0
Fan Tray 1
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
SFP+-10G-LPBK
15x 10G-SFP+
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-SR4
QFX3500-MB
QFX PS 650W AC
QFX PS 650W AC
QFX Fan Tray
QFX Fan Tray
1459
Routing Engine 0
FPC 0
REV 02
Power Supply 0
PSMI 2C
BUILTIN
711-032234
11-d65800
JPSU-850W-AC-AFO
JPSU-850W-AC-AFO
QFX5100-96S-FANAF0
QFX5100-96S-FANAF0
QFX5100-96S-FANAF0
CPU
PIC 0
Xcvr 8
...
REV 01
BUILTIN
BUILTIN
740-030658
BUILTIN
BUILTIN
AD0946A028B
FPC CPU
48x 10G-SFP+
SFP+-10G-USR
Serial number
JN11D1FD7AJA
ABAC5589
EG1679
ZE00006
ZJ00018
ZC00052
ZD00051
ZJ00060
EG3703
EG3698
P737A-002231
P737A-002438
EG5519
EG5516
EJ3080
EJ3260
EG5065
Description
PTX5000
Midplane-8S
Front Panel Display
DC Power Dist Unit
DC 12V Power Supply
DC 12V Power Supply
DC 12V Power Supply
DC 12V Power Supply
Clock Generator
Clock Generator
RE-DUO-2600
RE-DUO-2600
Control Board
Control Board
FPC
SNG PMB
FPC
1460
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
FPC 3
CPU
PIC 1
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
FPC 6
CPU
FPC 7
CPU
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
SIB 5
SIB 6
SIB 7
SIB 8
Fan Tray
0
1
2
3
4
6
7
8
10
11
12
14
15
16
19
21
22
23
0
1
2
5
6
7
10
11
12
15
16
18
19
22
23
0
1
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
09
14
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
13
09
10
06
711-030686
750-031913
740-031980
740-031981
740-031980
740-031981
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021309
740-031980
740-031981
740-031980
750-036844
711-030686
750-031903
750-036844
EG4082
EG5127
143363A00240
UK90PZ1
AD1141A04XH
UK90Q46
AD1141A04X4
B11H02560
B11C01589
AD1141A04XF
123363A01094
AK80LKF
183363A01528
193363A01079
AK80MC8
AJC0BHC
J08D26856
AK80KCT
UK90PZL
AK80N1V
EG5074
EG4064
EG0325
EH3198
SNG PMB
24x 10GE(LAN) SFP+
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
FPC
SNG PMB
SNG Load
FPC
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
14
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
01
01
18
12
18
12
10
09
07
07
07
07
07
07
07
07
07
04
750-031913
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021309
740-031980
740-031980
750-036710
740-034554
740-034554
750-036844
711-030686
750-036844
711-030686
711-030686
711-030686
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
760-032784
EG5134
AK80LBH
B11B03724
AK80FMH
B11J00818
193363A00743
B11B06125
B11H02529
AK80LFB
193363A01061
B11J00687
193363A00738
AK80MQX
J08C17257
B11J00730
AK80KEE
EG3105
B260HLT
B11C02847
EJ4391
EJ3257
EJ4382
EJ3238
EG5418
EG5373
EG4858
EG4872
EG4866
EG6011
EG4907
EG4879
EG4864
EG4899
EG4880
EG1496
1461
Fan Tray 1
Fan Tray 2
REV 04
REV 02
760-030642
760-030642
EG1335
ED4952
show chassis hardware (PTX5000 Packet Transport Router with AC PSM and PDU)
user@host> show chassis hardware
Hardware inventory:
Item
Version Part number Serial number
Chassis
JN12223A6AJA
Midplane
REV 16
750-035893
ACRA1350
FPM
REV 12
760-030647
BBBD5625
PDU 0
Rev 01
740-048338
1GB83360005
Description
PTX5000
Midplane-8S
Front Panel Display
High Capacity AC WYE PDU
PSM
PSM
PSM
PSM
PSM
PSM
PSM
PSM
PDU 1
0
1
2
3
4
5
6
7
PSM
PSM
PSM
PSM
PSM
PSM
PSM
PSM
CCG 0
...
0
1
2
3
4
5
6
7
Rev 01
Rev 01
Rev 01
Rev 01
Rev 01
Rev 01
Rev 01
Rev 01
Rev 01
Rev
Rev
Rev
Rev
Rev
Rev
Rev
Rev
REV
01
01
01
01
01
01
01
01
09
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
740-048338
1GB43360074
1GB43360001
1GB43360104
1GB43360042
1GB43360068
1GB43360080
1GB43360046
1GB43360100
1GB83360006
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
750-030653
1GB43360069
1GB43360099
1GB43360050
1GB43360095
1GB43360101
1GB43360075
1GB43360047
1GB43360019
BBAZ5345
High Capacity AC
High Capacity AC
High Capacity AC
High Capacity AC
High Capacity AC
High Capacity AC
High Capacity AC
High Capacity AC
Clock Generator
PSM
PSM
PSM
PSM
PSM
PSM
PSM
PSM
Serial number
JN1204FC0AJA
ACAB8038
BBBD5619
Description
PTX5000
Midplane-8S
Front Panel
1GB93470043
1GB63500184
1GB63500169
1GB63500306
1GB63500074
1GB93470045
1GB63500193
1GB63500143
1GB63500146
1GB63500192
BBBC1909
BBBD2970
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
Clock Generator
Clock Generator
PDU
PSM
PSM
PSM
PSM
PDU
PSM
PSM
PSM
PSM
1462
FPM
REV 08
PDU 0
Rev 05
PSM 0
Rev 05
PSM 1
Rev 04
PSM 2
Rev 04
PSM 3
Rev 05
CCG 0
REV 04
CCG 1
REV 04
Routing Engine 0 REV 05
Routing Engine 1 REV 06
CB 0
REV 08
CB 1
REV 08
FPC 0
REV 18
FPC 2
REV 13
PIC 0
REV 14
FPC 3
REV 13
FPC 5
PIC 0
REV 14
FPC 6
REV 18
FPC 7
REV 18
SIB 0
REV 07
SIB 1
REV 07
SIB 2
REV 07
SIB 3
REV 07
SIB 4
REV 07
SIB 5
REV 07
SIB 6
REV 07
SIB 7
REV 07
SIB 8
REV 07
Fan Tray 1
REV 04
760-030647
740-032019
740-032022
740-032022
740-032022
740-032022
750-030653
750-030653
740-026942
740-026942
750-030625
750-030625
750-036844
750-036844
750-031913
750-036844
PROTOXCLEI
IPUPAHLKAA
IPUPAHNKAA
032022XXXX
032022XXXX
IPUPAHNKAA
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
CRAFT-PTX5000-S
PWR-SAN-PDU-DC
PSM-PTX-DC-120-S
PWR-SAN-12-DC
PWR-SAN-12-DC
PSM-PTX-DC-120-S
CCG-PTX-S
CCG-PTX-S
RE-DUO-C2600-16G-S
RE-DUO-C2600-16G-S
CB-PTX-S
CB-PTX-S
FPC-PTX-P1-A
FPC-PTX-P1-A
P1-PTX-24-10GE-SFPP
FPC-PTX-P1-A
750-031913
750-036844
750-036844
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
760-030642
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
PROTOXCLEI
P1-PTX-24-10GE-SFPP
FPC-PTX-P1-A
FPC-PTX-P1-A
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
FAN-PTX-H-S
show chassis hardware clei-models (PTX5000 Packet Transport Router with AC PSM and PDU)
user@host> show chassis hardware clei-models
Hardware inventory:
Item
Version Part number CLEI code
Midplane
REV 16
750-035893
IPMUN00ARA
FPM
REV 12
760-030647
IPUCA7SCAA
PDU 0
Rev 01
740-048338
PROTOACPDU
PSM 0
Rev 01
740-048334
PROTOACPSM
PSM 1
Rev 01
740-048334
PROTOACPSM
PSM 2
Rev 01
740-048334
PROTOACPSM
PSM 3
Rev 01
740-048334
PROTOACPSM
PSM 4
Rev 01
740-048334
PROTOACPSM
PSM 5
Rev 01
740-048334
PROTOACPSM
PSM 6
Rev 01
740-048334
PROTOACPSM
PSM 7
Rev 01
740-048334
PROTOACPSM
PDU 1
Rev 01
740-048338
PROTOACPDU
PSM 0
Rev 01
740-048334
PROTOACPSM
PSM 1
Rev 01
740-048334
PROTOACPSM
PSM 2
Rev 01
740-048334
PROTOACPSM
PSM 3
Rev 01
740-048334
PROTOACPSM
PSM 4
Rev 01
740-048334
PROTOACPSM
PSM 5
Rev 01
740-048334
PROTOACPSM
PSM 6
Rev 01
740-048334
PROTOACPSM
PSM 7
Rev 01
740-048334
PROTOACPSM
CCG 0
REV 09
750-030653
IPUCA7DCAA
...
1463
show chassis hardware clei-models (PTX5000 Packet Transport Router with FPC2-PTX-P1A)
user@host> show chassis hardware clei-models
Hardware inventory:
Item
Version Part number CLEI code
Midplane
REV 11
750-035893
IPMUN00ARA
FPM
REV 12
760-030647
IPUCA7SCAA
PDU 0
Rev 04
740-048336
IPUPAL7KAA
PSM 0
Rev 04
740-046988
IPUPAL8KAA
PSM 2
Rev 04
740-046988
IPUPAL8KAA
PSM 4
Rev 04
740-046988
IPUPAL8KAA
PSM 6
Rev 04
740-046988
IPUPAL8KAA
PDU 1
Rev 04
740-048336
IPUPAL7KAA
PSM 1
Rev 04
740-046988
IPUPAL8KAA
PSM 3
Rev 04
740-046988
IPUPAL8KAA
PSM 5
Rev 04
740-046988
IPUPAL8KAA
PSM 7
Rev 04
740-046988
IPUPAL8KAA
CCG 0
REV 09
750-030653
IPUCA7DCAA
CCG 1
REV 09
750-030653
IPUCA7DCAA
...
1464
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
FPC 3
CPU
PIC 1
FPC 5
CPU
PIC 0
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
Xcvr
PIC 1
Xcvr
Xcvr
FPC 6
CPU
FPC 7
CPU
SPMB 0
SPMB 1
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
SIB 5
SIB 6
SIB 7
SIB 8
Fan Tray
Fan Tray
Fan Tray
15
16
19
21
22
23
0
1
2
5
6
7
10
11
12
15
16
18
19
22
23
0
1
0
1
2
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
01
01
01
01
13
09
10
06
740-031980
740-031980
740-021309
740-031980
740-031981
740-031980
750-036844
711-030686
750-031903
750-036844
AK80MC8
AJC0BHC
J08D26856
AK80KCT
UK90PZL
AK80N1V
EG5074
EG4064
EG0325
EH3198
SFP+-10G-SR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
SFP+-10G-LR
SFP+-10G-SR
FPC
SNG PMB
SNG Load
FPC
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
14
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
08
01
01
18
12
18
12
10
09
07
07
07
07
07
07
07
07
07
04
04
02
750-031913
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-031980
740-021309
740-031980
740-031980
750-036710
740-034554
740-034554
750-036844
711-030686
750-036844
711-030686
711-030686
711-030686
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
760-032784
760-030642
760-030642
EG5134
AK80LBH
B11B03724
AK80FMH
B11J00818
193363A00743
B11B06125
B11H02529
AK80LFB
193363A01061
B11J00687
193363A00738
AK80MQX
J08C17257
B11J00730
AK80KEE
EG3105
B260HLT
B11C02847
EJ4391
EJ3257
EJ4382
EJ3238
EG5418
EG5373
EG4858
EG4872
EG4866
EG6011
EG4907
EG4879
EG4864
EG4899
EG4880
EG1496
EG1335
ED4952
show chassis hardware detail (PTX5000 Packet Transport Router with AC PSM and PDU)
user@host> show chassis hardware detail
Hardware inventory:
Item
Version Part number Serial number
Chassis
JN12223A6AJA
Midplane
REV 16
750-035893
ACRA1350
FPM
REV 12
760-030647
BBBD5625
PDU 0
Rev 01
740-048338
1GB83360005
PSM 0
PSM 1
Rev 01
Rev 01
740-048334
740-048334
1GB43360074
1GB43360001
Description
PTX5000
Midplane-8S
Front Panel Display
High Capacity AC WYE PDU
High Capacity AC PSM
High Capacity AC PSM
1465
PSM
PSM
PSM
PSM
PSM
PSM
PDU 1
2
3
4
5
6
7
PSM
PSM
PSM
PSM
PSM
PSM
PSM
PSM
CCG 0
0
1
2
3
4
5
6
7
Rev 01
Rev 01
Rev 01
Rev 01
Rev 01
Rev 01
Rev 01
Rev
Rev
Rev
Rev
Rev
Rev
Rev
Rev
REV
01
01
01
01
01
01
01
01
09
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
740-048338
1GB43360104
1GB43360042
1GB43360068
1GB43360080
1GB43360046
1GB43360100
1GB83360006
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
740-048334
750-030653
1GB43360069
1GB43360099
1GB43360050
1GB43360095
1GB43360101
1GB43360075
1GB43360047
1GB43360019
BBAZ5345
PSM
PSM
PSM
PSM
PSM
PSM
PSM
PSM
show chassis hardware detail (PTX5000 Packet Transport Router with FPC2-PTX-P1A)
user@host> show chassis hardware detail
Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 11
750-035893
FPM
REV 12
760-030647
Display
PDU 0
Rev 04
740-048336
PSM 0
Rev 04
740-046988
PSM 2
Rev 04
740-046988
PSM 4
Rev 04
740-046988
PSM 6
Rev 04
740-046988
PDU 1
Rev 04
740-048336
PSM 1
Rev 04
740-046988
PSM 3
Rev 04
740-046988
PSM 5
Rev 04
740-046988
PSM 7
Rev 04
740-046988
CCG 0
REV 09
750-030653
CCG 1
REV 09
750-030653
...
Serial number
JN1204FC0AJA
ACAB8038
BBBD5619
Description
PTX5000
Midplane-8S
Front Panel
1GB93470043
1GB63500184
1GB63500169
1GB63500306
1GB63500074
1GB93470045
1GB63500193
1GB63500143
1GB63500146
1GB63500192
BBBC1909
BBBD2970
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
High Capacity DC
Clock Generator
Clock Generator
PDU
PSM
PSM
PSM
PSM
PDU
PSM
PSM
PSM
PSM
1466
Serial number
EG1679
ZE00006
ZJ00018
ZC00052
ZD00051
ZJ00060
EG3703
EG3698
P737A-002231
P737A-002438
EG5519
EG5516
EJ3080
EG5065
EG5127
FPC 3
FPC 5
PIC 0
FPC 6
FPC 7
SIB 0
SIB 1
SIB 2
SIB 3
SIB 4
SIB 5
SIB 6
SIB 7
SIB 8
Fan Tray 1
REV 13
750-036844
EG5074
FPC-PTX-P1-A
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
750-031913
750-036844
750-036844
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
750-030631
760-030642
EG5134
EJ4391
EJ4382
EG4858
EG4872
EG4866
EG6011
EG4907
EG4879
EG4864
EG4899
EG4880
EG1335
P1-PTX-24-10GE-SFPP
FPC-PTX-P1-A
FPC-PTX-P1-A
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
SIB-I-PTX5008
FAN-PTX-H-S
14
18
18
07
07
07
07
07
07
07
07
07
04
show chassis hardware models (PTX5000 Packet Transport Router with AC PSM and PDU)
user@host> show chassis hardware models
Hardware inventory:
Item
Version Part number
Midplane
REV 16
750-035893
FPM
REV 12
760-030647
PDU 0
Rev 01
740-048338
PSM 0
Rev 01
740-048334
PSM 1
Rev 01
740-048334
PSM 2
Rev 01
740-048334
PSM 3
Rev 01
740-048334
PSM 4
Rev 01
740-048334
PSM 5
Rev 01
740-048334
PSM 6
Rev 01
740-048334
PSM 7
Rev 01
740-048334
PDU 1
Rev 01
740-048338
PSM 0
Rev 01
740-048334
PSM 1
Rev 01
740-048334
PSM 2
Rev 01
740-048334
PSM 3
Rev 01
740-048334
PSM 4
Rev 01
740-048334
PSM 5
Rev 01
740-048334
PSM 6
Rev 01
740-048334
PSM 7
Rev 01
740-048334
CCG 0
REV 09
750-030653
...
Serial number
ACRA1350
BBBD5625
1GB83360005
1GB43360074
1GB43360001
1GB43360104
1GB43360042
1GB43360068
1GB43360080
1GB43360046
1GB43360100
1GB83360006
1GB43360069
1GB43360099
1GB43360050
1GB43360095
1GB43360101
1GB43360075
1GB43360047
1GB43360019
BBAZ5345
show chassis hardware models (PTX5000 Packet Transport Router with FPC2-PTX-P1A)
user@host> show chassis hardware models
Hardware inventory:
Item
Version Part number
Midplane
REV 11
750-035893
FPM
REV 12
760-030647
PDU 0
Rev 04
740-048336
PSM 0
Rev 04
740-046988
PSM 2
Rev 04
740-046988
PSM 4
Rev 04
740-046988
PSM 6
Rev 04
740-046988
PDU 1
Rev 04
740-048336
PSM 1
Rev 04
740-046988
PSM 3
Rev 04
740-046988
PSM 5
Rev 04
740-046988
PSM 7
Rev 04
740-046988
Serial number
ACAB8038
BBBD5619
1GB93470043
1GB63500184
1GB63500169
1GB63500306
1GB63500074
1GB93470045
1GB63500193
1GB63500143
1GB63500146
1GB63500192
1467
CCG 0
CCG 1
...
REV 09
REV 09
750-030653
750-030653
BBBC1909
BBBD2970
CCG-PTX-S
CCG-PTX-S
show chassis hardware (MX Routers with Media Services Blade [MSB])
user@switch> show chassis hardware
Hardware inventory:
Item
Version Part number
Chassis
Midplane
REV 05
710-017414
FPM Board
REV 02
710-017254
PEM 2
Rev 02
740-017343
PEM 3
Rev 02
740-017343
Routing Engine 0 REV 07
740-015113
CB 0
REV 03
710-021523
FPC 1
REV 11
750-037207
1468
Serial number
JN1100FB1AFB
TR3310
KG1872
QCS0812A00N
QCS0812A00U
1000740938
KF4630
ZW9726
Description
MX480
MX480 Midplane
Front Panel Display
DC Power Entry Module
DC Power Entry Module
RE-S-1300
MX SCB
AS-MCC
CPU
MIC 0
PIC 0
MIC 1
PIC 2
REV 04
REV 06
REV 00
711-038173
750-037214
BUILTIN
750-037211
BUILTIN
ZW4819
ZW3574
BUILTIN
AS-MCC PMB
AS-MSC
AS-MSC
AS-MXC
AS-MXC
BUILTIN
show chassis hardware extensive (MX Routers with Media Services Blade [MSB])
user@switch> show chassis hardware extensive
FPC 1
REV 11
750-037207
ZW9726
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037207
S/N:
Assembly ID: 0x0b37
Assembly Version:
Date:
02-17-2012
Assembly Flags:
Version:
REV 11
CLEI Code:
ID: AS-MCC
FRU Model Number: 750-037207
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 37 01 0b 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32
Address 0x20: 53 2f 4e 20 5a 57 39 37 32 36 00 00
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43
Address 0x50: 35 30 2d 30 33 37 32 30 37 00 00 00
Address 0x60: 00 00 00 00 00 00 31 31 00 ff ff ff
Address 0x70: ff ff ff 5e ff ff ff ff ff ff ff ff
CPU
REV 04
711-038173
ZW4819
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
711-038173
S/N:
Assembly ID: 0x0b38
Assembly Version:
Date:
12-30-2011
Assembly Flags:
Version:
REV 04
ID: AS-MCC PMB
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0b 38 01 04 52 45 56 20
Address 0x10: 00 00 00 00 37 31 31 2d 30 33 38 31
Address 0x20: 53 2f 4e 20 5a 57 34 38 31 39 00 00
Address 0x30: db ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 50 52 4f 54 4f 58 43
Address 0x50: 31 31 2d 30 33 38 31 37 33 00 00 00
Address 0x60: 00 00 00 00 00 00 30 34 00 ff ff ff
Address 0x70: ff ff ff 60 00 00 00 00 00 00 00 00
MIC 0
REV 06
750-037214
ZW3574
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037214
S/N:
Assembly ID: 0x0a44
Assembly Version:
Date:
02-19-2012
Assembly Flags:
Version:
REV 06
CLEI Code:
ID: AS-MSC
FRU Model Number: 750-037214
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 02 ff 0a 44 01 06 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32
Address 0x20: 53 2f 4e 20 5a 57 33 35 37 34 00 00
Address 0x30: dc ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 01 50 52 4f 54 4f 58 43
AS-MCC
0x02
ZW9726
01.11
0x00
PROTOXCLEI
ff ff ff ff
31
30
00
ff
4c
00
ff
ff
31
37
11
ff
45
00
ff
ff
00 00
00 00
02 07
ff ff
49 37
00 00
ff ff
ff ff
AS-MCC-PMB
0x02
ZW4819
01.04
0x00
ff ff ff ff
30
37
00
ff
4c
00
ff
00
34
33
1e
ff
45
00
ff
00
00 00
00 00
0c 07
ff ff
49 37
00 00
ff ff
00 00
AS-MSC
0x02
ZW3574
01.06
0x00
PROTOXCLEI
ff ff ff ff
30
31
00
ff
4c
36
34
13
ff
45
00
00
02
ff
49
00
00
07
ff
37
1469
Address 0x50: 35 30 2d 30 33 37 32 31 34 00 00 00
Address 0x60: 00 00 00 00 00 00 30 36 00 ff ff ff
Address 0x70: ff ff ff 60 c0 03 e5 f4 00 00 00 00
PIC 0
BUILTIN
BUILTIN
MIC 1
REV 00
750-037211
Jedec Code:
0x7fb0
EEPROM Version:
P/N:
750-037211
Assembly ID: 0x0a43
Assembly Version:
Date:
255-255-65535
Assembly Flags:
Version:
REV 00
ID: AS-MXC
Board Information Record:
Address 0x00: ff ff ff ff ff ff ff ff ff ff ff ff
I2C Hex Data:
Address 0x00: 7f b0 01 ff 0a 43 01 00 52 45 56 20
Address 0x10: 00 00 00 00 37 35 30 2d 30 33 37 32
Address 0x20: 00 00 00 00 00 00 00 00 00 00 00 00
Address 0x30: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x40: ff ff ff ff 00 ff ff ff ff ff ff ff
Address 0x50: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x60: ff ff ff ff ff ff ff ff ff ff ff ff
Address 0x70: ff ff ff ff c0 02 e6 6c 7f b0 02 ff
PIC 2
BUILTIN
BUILTIN
00 00 00 00
ff ff ff ff
00 00 00 00
AS-MSC
AS-MXC
0x01
01.00
0x00
ff ff ff ff
30
31
00
ff
ff
ff
ff
0a
30
31
ff
ff
ff
ff
ff
44
00 00
00 00
ff ff
ff ff
ff ff
ff ff
ff ff
01 06
AS-MXC
Serial number
P3566
Description
QFX3500
BUILTIN
P3566-C
BUILTIN
BUILTIN
AD1125A0438
AD1125A02GN
BUILTIN
BBAW0328
WA13035
QFX3500-MGMT-RJ45-AFI
JPSU-650W-AC-AFI
QFX3500 Fan Tray, Front
QFX3500 Fan Tray, Front
QFX3500 Fan Tray, Front
1470
Serial number
TB3113280048
Description
QFX5100-24Q-2P
BUILTIN
TB3113280048
BUILTIN
BUILTIN
Xcvr 8
Xcvr 14
PIC 1
Xcvr 0
Xcvr 1
Xcvr 2
PIC 2
Xcvr 0
Xcvr 1
Xcvr 2
Power Supply 0
Power Supply 1
Fan Tray 0
to Back Airflow
Fan Tray 1
to Back Airflow
Fan Tray 2
to Back Airflow
Fan Tray 3
to Back Airflow
Fan Tray 4
to Back Airflow
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
REV
01
01
02
01
01
01
02
01
01
01
03
03
740-032986
740-032986
611-049555
740-032986
740-032986
740-035085
611-049555
740-032986
740-035085
740-032986
740-041741
740-041741
QA470143
QB500525
RR3113310169
QC440904
QB240154
018110105
RR3113310209
QB190270
018110063
QB210034
1GA23110973
1GA23090878
QSFP+-40G-SR4
QSFP+-40G-SR4
QFX-EM-4Q
QSFP+-40G-SR4
QSFP+-40G-SR4
QSFP+-40G-LPBK
QFX-EM-4Q
QSFP+-40G-SR4
QSFP+-40G-LPBK
QSFP+-40G-SR4
JPSU-650W-AC-AFO
JPSU-650W-AC-AFO
QFX5100 Fan Tray 0, Front
- AFO
QFX5100 Fan Tray 1, Front
- AFO
QFX5100 Fan Tray 2, Front
- AFO
QFX5100 Fan Tray 3, Front
- AFO
QFX5100 Fan Tray 4, Front
- AFO
1471
Syntax
Syntax (MX104,
MX2010 and MX2020
3D Universal Edge
Routers)
Release Information
1472
Description
Options
Display status information about the PIC installed in the specified Flexible PIC
Concentrator (FPC) and PIC slot.
fpc-slot slot-numberDisplay information about the PIC in this particular FPC slot:
On a TX Matrix router, if you specify the number of the T640 router by using the
lcc number option (the recommended method), replace slot-number with a value
from 0 through 7. Otherwise, replace slot-number with a value from 0 through 31.
Likewise, on a TX Matrix Plus router, if you specify the number of the T1600 router
by using the lcc number option (the recommended method), replace slot-number
with a value from 0 through 7. Otherwise, replace slot-number with a value from
0 through 31. For example, the following commands have the same result:
user@host> show chassis pic fpc-slot 1 lcc 1 pic-slot 1
user@host> show chassis pic fpc-slot 9 pic-slot 1
EX Series switches:
QFX Series:
1473
all-members(MX Series routers and EX Series switches only) (Optional) Display PIC
display PIC information for a specified T640 router (line-card chassis) that is
connected to the TX Matrix router. On a TX Matrix Plus router, display PIC information
for a specified router (line-card chassis) that is connected to the TX Matrix Plus
router.
Replace number with the following values depending on the LCC configuration:
0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D
SIBs in a routing matrix.
local(MX Series routers and EX Series switches only) (Optional) Display PIC information
PIC information for the specified member of the Virtual Chassis configuration. Replace
member-id with a value of 0 or 1.
node-device name(QFabric systems only) (Optional) Display PIC information for a
routers, replace slot-number with a value from 0 through 3. For EX3200 and EX4200
switches, replace slot-number with 0 for built-in network interfaces and 1 for interfaces
on uplink modules. For EX8208 and EX8216 switches, replace slot-number with 0.
For the QFX3500, QFX3600, QFX5100, and OCX Series standalone switches , replace
slot-number with 0.
transportDisplay PIC information for optical transport network.
Required Privilege
Level
Related
Documentation
1474
view
1475
show chassis pic FPC slot PIC slot (MX Series Routers with Media Services Blade
[MSB]) on page 1487
show chassis pic transport fpc-slot pic-slot (PTX Series Packet Transport
Routers) on page 1487
Output Fields
Table 86 on page 1476 lists the output fields for the show chassis pic command. Output
fields are listed in the approximate order in which they appear.
Field Description
Type
PIC type.
NOTE: On the 1-port OC192/STM64 MICs with the SDH framing
mode, the type is displayed as MIC-3D-1STM64-XFP and with the
SONET framing mode, the type is displayed as MIC-3D-1OC192-XFP.
By default, the 1-port OC192/STM64 MICs displays the type as
MIC-3D-1OC192-XFP.
1476
ASIC type
State
Status of the PIC. State is displayed only when a PIC is in the slot.
PIC version
Uptime
Package
Port Number
Cable Type
PortPort number
Field Description
PortPort number
PortPort number.
PortPort number
Multirate Mode
Channelization
Sample Output
show chassis pic fpc-slot pic-slot
user@host> show chassis pic fpc-slot 2 pic-slot 0
PIC fpc slot 2 pic slot 0 information:
Type
10x 1GE(LAN), 1000 BASE
1477
ASIC type
State
PIC version
Uptime
PIC Port Information:
Port
Cable
Number
Type
0
GIGE 1000EX
1
GIGE 1000EX
H chip
Online
1.1
1 day, 50 minutes, 58 seconds
Xcvr
Vendor Name
FINISAR CORP.
FINISAR CORP.
Xcvr Vendor
Part Number
FTRJ8519P1BNL-J3
FTRJ-8519-7D-JUN
Xcvr
Vendor Name
FINISAR CORP.
FINISAR CORP.
Xcvr Vendor
Part Number
FTRJ8519P1BNL-J3
FTRJ-8519-7D-JUN
1478
Xcvr vendor
Wave-
type
Xcvr vendor
part number
length
n/a
Methode Elec.
SP7041-M1-JN
n/a
Xcvr
0.0
GIGE 1000LX10
SM
FINISAR CORP.
FTLF1318P2BTL-J1
1310 nm
0.0
GIGE 1000T
n/a
Methode Elec.
SP7041-M1-JN
n/a
0.0
GIGE 1000T
n/a
Methode Elec.
SP7041-M1-JN
n/a
0.0
show chassis pic fpc-slot pic-slot (MX960 Router with Bidirectional Optics)
user@host> show chassis pic fpc-slot 4 pic-slot 1
FPC slot 4, PIC slot 1 information:
Type
10x 1GE(LAN)
Account Layer2 Overhead
Enabled
State
Online
PIC version
0.0
Uptime
18 days, 5 hours, 41 minutes, 54 seconds
PIC port information:
Port
0
1
2
3
4
5
6
7
8
9
Fiber
Cable type
type
SFP-1000BASE-BX10-D SM
SFP-1000BASE-BX10-D SM
SFP-1000BASE-BX10-D SM
SFP-1000BASE-BX10-D SM
SFP-1000BASE-BX10-D SM
SFP-1000BASE-BX10-U SM
SFP-1000BASE-BX10-U SM
SFP-1000BASE-BX10-U SM
SFP-1000BASE-BX10-U SM
SFP-1000BASE-BX10-U SM
Xcvr vendor
part number
SBP6H44-J3-BW-49
SBP6H44-J3-BW-49
SBP6H44-J3-BW-49
TRXBG1LXDBVM2-JW
TRXBG1LXDBVM2-JW
SBP6H44-J3-BW-31
SBP6H44-J3-BW-31
TRXBG1LXDBBMH-J1
TRXBG1LXDBBMH-J1
SBP6H44-J3-BW-31
Xcvr vendor
SumitomoElectric
SumitomoElectric
SumitomoElectric
OCP
OCP
SumitomoElectric
SumitomoElectric
OCP
OCP
SumitomoElectric
Wavelength
1490 nm
1490 nm
1490 nm
1490 nm
1490 nm
1310 nm
1310 nm
1310 nm
1310 nm
1310 nm
show chassis pic fpc-slot pic-slot (MX480 Router with 100-Gigabit Ethernet MIC)
user@host> show chassis pic fpc-slot 1 pic-slot 2
FPC slot 1, PIC slot 2 information:
Type
1X100GE CFP
State
Online
PIC version
2.10
Uptime
4 minutes, 48 seconds
PIC port information:
Fiber
Port Cable type
0
100GBASE LR4
type
SM
Xcvr vendor
Xcvr vendor
FINISAR CORP.
part number
FTLC1181RDNS-J3
Wavelength
1310 nm
Xcvr vendor
firmware version
1.8
show chassis pic fpc-slot pic-slot (MX240, MX480, MX960 Routers with Application Services Modular Line
Card)
user@host> show chassis pic fpc-slot 1 pic-slot 2
FPC slot 1, PIC slot 2 information:
Type
AS-MXC
State
Online
PIC version
1.0
Uptime
11 hours, 18 minutes, 3 seconds
1479
Xcvr vendor
Wave-
type
Xcvr vendor
part number
length
n/a
Oclaro Inc.
TRB5E20FNF-LF150
1309 nm
Xcvr
1.0
10GBASE SR
Xcvr vendor
Wave-
Xcvr
type
Xcvr vendor
part number
length
MM
OPNEXT, INC.
TRS2001EM-0014
850 nm
0.0
MM
OPNEXT, INC.
TRS2001EM-0014
850 nm
0.0
show chassis pic fpc-slot pic-slot (MX480 router with OTN Interface)
user@host> show chassis pci fpc-slot 4 pic-slot 0
FPC slot 4, PIC slot 0 information:
Type
12X10GE SFPP OTN
State
Online
PIC version
0.0
Uptime
5 hours, 28 minutes, 23 seconds
PIC port information:
Fiber
Port Cable type
Firmware
0
10GBASE SR
Xcvr vendor
Wave-
Xcvr
type
Xcvr vendor
part number
length
MM
FINISAR CORP.
FTLX8571D3BNL-J1
850 nm
0.0
10GBASE SR
MM
FINISAR CORP.
FTLX8571D3BCL-J1
850 nm
0.0
10GBASE SR
MM
OPNEXT, INC.
TRS2001EM-0014
850 nm
0.0
show chassis pic fpc-slot pic-slot (MX2010 Router with OTN Interfaces)
user@host> show chassis pic fpc-slot 9 pic-slot 0
1480
100GBASE SR10
Xcvr vendor
Wave-
Xcvr
type
Xcvr vendor
part number
length
SM
FUJITSU
FIM37300/222
1310 nm
1.3
MM
AVAGO
AFBR-8420Z
n/a
1.0
Xcvr vendor
Wave-
Xcvr
type
Xcvr vendor
part number
length
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
10GBASE SR
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
10GBASE SR
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
10GBASE SR
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
show chassis pic fpc-slot pic-slot (MX2020 Router with MPC5EQ and MPC6E)
user@host> show chassis pic fpc-slot 18 pic-slot 2
FPC slot 18, PIC slot 2 information:
Type
3X40GE QSFPP
State
Online
PIC version
0.0
Uptime
6 minutes, 31 seconds
PIC port information:
Fiber
Port Cable type
type
Xcvr vendor
Xcvr vendor
part number
Wave-
Xcvr
length
1481
Firmware
0
40GBASE SR4
MM
AVAGO
AFBR-79E4Z-D-JU2
850 nm
0.0
40GBASE SR4
MM
AVAGO
AFBR-79E4Z-D-JU2
850 nm
0.0
40GBASE SR4
MM
AVAGO
AFBR-79E4Z-D-JU2
850 nm
0.0
show chassis pic fpc-slot pic-slot (MX2020 Router with MPC6E and OTN MIC)
user@host> show chassis pic fpc-slot 3 pic-slot 0
FPC slot 0, PIC slot 1 information:
Type
24X10GE SFPP OTN
State
Online
PIC version
1.1
Uptime
1 hour, 33 minutes, 59 seconds
PIC port information:
Fiber
Port Cable type
Firmware
7
10GBASE SR
Xcvr vendor
Wave-
Xcvr
type
Xcvr vendor
part number
length
MM
SumitomoElectric
SPP5200SR-J6-M
850 nm
0.0
10GBASE SR
MM
FINISAR CORP.
FTLX8571D3BNL-J1
850 nm
0.0
12
10GBASE LR
SM
FINISAR CORP.
FTLX1472M3BNL-J3
1310 nm
0.0
20
10GBASE ZR
SM
FINISAR CORP.
FTLX1871M3BNL-J3
1550 nm
0.0
21
10GBASE ER
SM
FINISAR CORP.
FTLX1671D3BTL-J4
1550 nm
0.0
22
10GBASE LR
SM
SOURCEPHOTONICS
SPP10SLREDFCJNP
1310 nm
0.0
23
10GBASE LR
SM
FINISAR CORP.
FTLX1471D3BNL-J1
1310 nm
0.0
Xcvr vendor
Wave-
Xcvr
type
Xcvr vendor
part number
length
MM
SumitomoElectric
SPP5100SR-J3
850 nm
0.0
10GBASE SR
MM
SumitomoElectric
SPP5100SR-J3
850 nm
0.0
10GBASE SR
MM
SumitomoElectric
SPP5100SR-J3
850 nm
0.0
show chassis pic fpc-slot pic-slot (T1600 Router with 100-Gigabit Ethernet PIC)
user@host> run show chassis pic fpc-slot 3 pic-slot 1
FPC slot 3, PIC slot 1 information:
Type
100GE SLOT1
1482
ASIC type
State
PIC version
Uptime
Cable type
100GBASE LR4
Fiber
type Xcvr vendor
SM
Opnext Inc.
Xcvr vendor
part number
TRC5E20ENFSF000F
Wavelength
1310 nm
show chassis pic fpc-slot pic-slot lcc (TX Matrix Plus Router)
user@host> show chassis pic pic-slot 0 fpc-slot 8
lcc0-re0:
-------------------------------------------------------------------------FPC slot 8, PIC slot 0 information:
Type
1x 10GE(LAN/WAN)
State
Online
Uptime
2 hours, 46 minutes, 23 seconds
PIC port information:
Port
Cable type
Fiber
type Xcvr vendor
part number
Wavelength
0
0
10GBASE ZR
10GBASE ZR
SM
SM
TRF7061BN-LF150
FTRX-1811-3-J2
1550 nm
1550 nm
Opnext Inc.
FINISAR CORP.
Cable type
Fiber
type Xcvr vendor
Xcvr vendor
part number
Wavelength
0
1
2
3
SM
MM
MM
SM
FTRJ1321P1BTL-J2
TRPA03MM3BAS-JE
TRXA03MM3BAS-JW
FTLF1322P1BTR
1310
1310
1310
1310
FINISAR CORP.
OCP
OCP
FINISAR CORP.
nm
nm
nm
nm
1483
Cable type
OC3 short reach
OC3 short reach
OC3 long reach
Fiber
type
MM
MM
SM
Xcvr vendor
AVAGO
AVAGO
OPNEXT INC
Xcvr vendor
part number
HFBR-57E0P-JU2
HFBR-57E0P-JU2
TRF5456AVLB314
Wavelength
n/a
n/a
1310 nm
show chassis pic fpc-slot pic-slot (SONET/SDH OC3/STM1 [Multi-Rate] MIC with SFP)
user@host> show chassis pic fpc-slot 0 pic-slot 0
FPC slot 0, PIC slot 0 information:
Type
MIC-3D-8OC3OC12-4OC48
State
Online
PIC version
1.8
Uptime
3 days, 22 hours, 3 minutes, 50 seconds
PIC port information:
Port Cable type
1
OC12 inter reach
7
OC12 inter reach
Multirate Mode
Fiber
type Xcvr vendor
SM
FINISAR CORP
SM
FINISAR CORP
Enabled
Xcvr vendor
part number
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
Wavelength
1310 nm
1310 nm
show chassis pic fpc-slot pic-slot (8-Port Channelized SONET/SDH OC3/STM1 [Multi-Rate] MIC with SFP)
user@host> show chassis pic fpc-slot 3 pic-slot 0
FPC slot 3, PIC slot 0 information:
Type
MIC-3D-8CHOC3-4CHOC12
State
Online
PIC version
1.9
Uptime
1 hour, 21 minutes, 24 seconds
PIC port information:
Port
1484
Cable type
Fiber
type Xcvr vendor
Xcvr vendor
part number
Wavelength
0
1
2
4
5
6
7
OC12
OC12
OC12
OC12
OC12
OC12
OC12
short
short
inter
short
short
short
short
reach
reach
reach
reach
reach
reach
reach
SM
SM
SM
SM
SM
SM
SM
FINISAR
FINISAR
FINISAR
FINISAR
FINISAR
FINISAR
FINISAR
CORP.
CORP.
CORP.
CORP.
CORP.
CORP.
CORP.
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J2
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
1310
1310
1310
1310
1310
1310
1310
nm
nm
nm
nm
nm
nm
nm
show chassis pic fpc-slot pic-slot (4-Port Channelized SONET/SDH OC3/STM1 [Multi-Rate] MIC with SFP)
user@host> show chassis pic fpc-slot 5 pic-slot 0
FPC slot 5, PIC slot 0 information:
Type
MIC-3D-4CHOC3-2CHOC12
State
Online
PIC version
1.9
Uptime
1 hour, 21 minutes
PIC port information:
Port
1
2
3
Cable type
OC12 inter reach
OC12 inter reach
OC12 short reach
Fiber
type
SM
SM
SM
Xcvr vendor
FINISAR CORP.
FINISAR CORP.
FINISAR CORP.
Xcvr vendor
part number
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
FTRJ1322P1BTR-J3
Wavelength
1310 nm
1310 nm
1310 nm
show chassis pic fpc-slot pic-slot (1-Port OC192/STM64 MIC with XFP)
user@host> show chassis pic fpc-slot 1 pic-slot 0
FPC slot 1, PIC slot 0 information:
Type
MIC-3D-1OC192-XFP
State
Online
PIC version
1.2
Uptime
1 day, 11 hours, 4 minutes, 6 seconds
PIC port information:
Port
0
Fiber
Cable type
type Xcvr vendor
OC192 short reach n/a
FINISAR CORP.
Xcvr vendor
part number
FTLX1412M3BCL-J3
Wavelength
1310 nm
1485
show chassis pic fpc-slot pic-slot (QFX5100 Switches and OCX Series )
user@switch> show chassis pic fpc-slot 0 pic-slot 0
FPC slot 0, PIC slot 0 information:
Type
Unknown Builtin
State
Online
Uptime
1 day, 17 hours, 5 minutes, 9 seconds
1486
Cable type
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
10GBASE SR
Fiber
type
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
Xcvr vendor
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
Xcvr vendor
part number
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
Wavelength
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
850 nm
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
10GBASE
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
SR
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
MM
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SumitomoElectric
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
SPP5101SR-J3
850
850
850
850
850
850
850
850
850
850
850
850
850
850
850
850
850
850
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
nm
show chassis pic fpc-slot pic-slot (MX Series Routers with Media Services Blade [MSB])
user@switch> show chassis pic fpc-slot 1 pic-slot 0
FPC slot 1, PIC slot 0 information:
Type
AS-MSC
State
Online
PIC version
1.6
Uptime
11 hours, 17 minutes, 56 seconds
show chassis pic FPC slot PIC slot (MX Series Routers with Media Services Blade [MSB])
user@switch> show chassis pic fpc-slot 1 pic-slot 2
Type
AS-MXC
State
Online
PIC version
1.0
Uptime
11 hours, 18 minutes, 3 seconds
show chassis pic transport fpc-slot pic-slot (PTX Series Packet Transport Routers)
user@host> show chassis pic transport fpc-slot 2 pic-slot 0
Administrative State:
In Service
Operational
State:
Normal
1487
show iccp
Syntax
Release Information
Description
Display Inter-chassis Control Protocol (ICCP) information about the multichassis link
aggregation group (MC-LAG) peers, including the state of the TCP connection,
Bidirectional Forwarding Detection protocol, backup liveness peer status, and mcnsoopd,
lacpd, and eswd applications.
Options
connection and Bidirectional Forwarding Detection protocol, and mcnsoopd, lacpd, and
eswd applications.
briefDisplay brief ICCP information about the MC-LAG peers, including the state of the
TCP connection and Bidirectional Forwarding Detection protocol, and mcnsoopd, lacpd,
and eswd applications.
detailDisplay detailed ICCP information about the MC-LAG peers, including the state
of the TCP connection and Bidirectional Forwarding Detection protocol, and mcnsoopd,
lacpd, and eswd applications.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
view
Field Description
Redundancy Group
Information for peer
TCP Connection
Specifies if the TCP connection between the peers hosting the MC-LAG is up or down.
Status
Redundancy Group ID
Displays the redundancy group identifier that is used to associate with multiple chassis that perform
similar failover operations.
1488
Field Description
Status
Client Application
Specifies information regarding the state of the mcnsoopd and eswd client applications.
Denotes the redundancy group unique identifier that is associated for the particular client application
or process.
Sample Output
show iccp
user@switch> show iccp
Redundancy Group Information for peer 7.7.7.1
TCP Connection
: Established
Liveliness Detection : Up
Redundancy Group ID
100
Status
Up
1489
Release Information
Description
Options
of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
List of Sample Output
Output Fields
view
Table 88: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields
Field Name
Field Description
Level of Output
Physical interface
All levels
Enabled
State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
All levels
Interface index
SNMP ifIndex
Physical Interface
1490
Table 88: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields
(continued)
Field Name
Field Description
Level of Output
Generation
detail extensive
Type
All levels
Link-level type
All levels
MTU
All levels
Clocking
All levels
Speed
All levels
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
Interface flags
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
All levels
Link type
Link flags
Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description.
Physical info
detail extensive
Hold-times
detail extensive
Current address
Hardware address
Alternate link
address
Last flapped
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate
Input rate in bits per second (bps) and packets per second (pps).
None specified
Output Rate
None specified
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
1491
Table 88: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields
(continued)
Field Name
Field Description
Level of Output
Traffic statistics
Number and rate of bytes and packets received and transmitted on the physical
interface.
detail extensive
Input errors
Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
(FCS).
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
Output errors
Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
Carrier transitionsNumber of times the interface has gone from down to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly
(perhaps once every 10 seconds), the cable, the far-end system, or the PIC
is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
Logical Interface
Logical interface
All levels
Index
SNMP ifIndex
Generation
detail extensive
1492
Table 88: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields
(continued)
Field Name
Field Description
Level of Output
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
All levels
Encapsulation
All levels
Input packets
None specified
Output packets
None specified
Traffic statistics
Number and rate of bytes and packets received and transmitted on the logical
interface.
detail extensive
Local statistics
Statistics for traffic received from and transmitted to the Routing Engine. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. It takes awhile (generally, less than 1 second) for this
counter to stabilize.
detail extensive
Transit statistics
Statistics for traffic transiting the router. When a burst of traffic is received, the
value in the output packet rate field might briefly exceed the peak cell rate. It
takes generally less than 1 second for the counter to stabilize.
detail extensive
protocol-family
Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.
brief
Protocol
Protocol family configured on the logical interface, such as iso, inet6, mpls.
MTU
Generation
detail extensive
Route table
Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
detail extensive
Flags
Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description.
Addresses, Flags
Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
Destination
Local
1493
Table 88: Adaptive Services and Redundant Adaptive Services show interfaces Output Fields
(continued)
Field Name
Field Description
Level of Output
Broadcast
Broadcast address.
Generation
detail extensive
1494
Sample Output
show interfaces (Adaptive Services)
user@host> show interfaces sp-1/2/0
Physical interface: sp-1/2/0, Enabled, Physical link is Up
Interface index: 147, SNMP ifIndex: 72
Type: Adaptive-Services, Link-level type: Adaptive-Services, MTU: 9192,
Speed: 800mbps
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps Internal: 0x4000
Link type
: Full-Duplex
Link flags
: None
Last flapped
: 2006-03-06 11:37:18 PST (00:57:29 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Logical interface sp-1/2/0.16383 (Index 68) (SNMP ifIndex 73)
Flags: Point-To-Point SNMP-Traps Encapsulation: Adaptive-Services
Input packets : 3057
Output packets: 3044
Protocol inet, MTU: 9192
Flags: Receive-options, Receive-TTL-Exceeded
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.0.34, Local: 10.0.0.1
1495
1496
Input bytes :
125547
Output bytes :
1483353
Input packets:
3065
Output packets:
3052
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
Protocol inet, MTU: 9192, Generation: 20, Route table: 1
Flags: Receive-options, Receive-TTL-Exceeded
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.0.0.34, Local: 10.0.0.1, Broadcast: Unspecified,
Generation: 22
1497
Release Information
Description
Options
of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Level of Output
Physical interface
All levels
Enabled
State of the physical interface. Possible values are described in the Enabled
Field section under Common Output Fields Description.
All levels
Physical Interface
1498
Field Description
Level of Output
Interface index
Index number of the physical interface, which reflects its initialization sequence.
All levels
SNMP ifIndex
Generation
detail extensive
Link-level type
All levels
MTU
All levels
Speed
All levels
Loopback
All levels
Source filtering
All levels
Flow control
All levels
Minimum links
needed
Number of child links that must be operational for the aggregate interface to
be operational.
All levels
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
Interface flags
Information about the interface. Possible values are described in the Interfaces
Flags section under Common Output Fields Description.
All levels
Current address
detail extensive
Hardware address
detail extensive
Last flapped
Date, time, and how long ago the interface went from down to up or from up
to down. The format is Last flapped: year-month-day hours:minutes:seconds
timezone (hours:minutes:seconds ago). For example, Last flapped: 2002-04-26
detail extensive
Input rate in bits per second (bps) and packets per second (pps).
None specified
Output Rate
None specified
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
1499
Field Description
Level of Output
Traffic statistics
Number of and rate at which bytes and packets are received and transmitted
on the physical interface.
detail extensive
Input bytesNumber of bytes and rate, in bps, at which bytes are received
on the interface.
Output bytesNumber of bytes and rate, in bps, at which bytes are transmitted
on the interface.
detail extensive
errors.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's random early detection (RED)
mechanism.
RuntsNumber of frames received that are smaller than the runt threshold.
GiantsNumber of frames received that are larger than the giant threshold.
discarded because they were not recognized or were not of interest. Usually,
this field reports protocols that Junos OS does not handle.
Output errors
detail extensive
Carrier transitions Number of times the interface has gone from down to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly
(perhaps once every 10 seconds), then the cable, the far-end system, or the
PIC is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
IPv6 transit
statistics
1500
MTU errorsNumber of packets whose size exceeded the MTU of the interface.
Number of IPv6 transit bytes and packets received and transmitted on the
physical interface if IPv6 statistics tracking is enabled.
detail extensive
Field Description
Level of Output
Queue counters
CoS queue number and its associated user-configured forwarding class name.
detail extensive
NOTE: In DPCs that are not of the enhanced type, such as DPC 40x 1GE R,
DPCE 20x 1GE + 2x 10GE R, or DPCE 40x 1GE R, you might notice a discrepancy
in the output of the show interfaces command because incoming packets
might be counted in the Egress queues section of the output. This problem
occurs on non-enhanced DPCs because the egress queue statistics are polled
from IMQ (Inbound Message Queuing) block of the I-chip. The IMQ block
does not differentiate between ingress and egress WAN traffic; as a result,
the combined statistics are displayed in the egress queue counters on the
Routing Engine. In a simple VPLS scenario, if there is no MAC entry in DMAC
table (by sending unidirectional traffic), traffic is flooded and the input traffic
is accounted in IMQ. For bidirectional traffic (MAC entry in DMAC table), if
the outgoing interface is on the same I-chip then both ingress and egress
statistics are counted in a combined way. If the outgoing interface is on a
different I-chip or FPC, then only egress statistics are accounted in IMQ. This
behavior is expected with non-enhanced DPCs
Logical Interface
Logical interface
All levels
Index
Index number of the logical interface (which reflects its initialization sequence).
SNMP ifIndex
Generation
detail extensive
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags Field section under Common Output Fields Description.
All levels
VLAN-Tag
All levels
Demux
Encapsulation
All levels
1501
Field Description
Level of Output
Statistics
Information about the number of packets, packets per second, number of bytes,
and bytes per second on this aggregate interface.
on an AE bundle.
port.
Ethernet type value (43B.4) but contain a badly formed PDU or an illegal
value of protocol subtype (43B.4).
LACP info
Port keyOperational key value assigned to the port by the actor or partner,
1502
Field Description
LACP Statistics
LACP RxLACP received counter that increments for each normal hello.
Level of Output
NOTE: For LACP Rx and LACP Tx, Packet count is updated only on snmp timer
expiry (30 secs).
protocol-family
Protocol family configured on the logical interface. Possible values are described
in the Protocol Field section under Common Output Fields Description.
brief
Protocol
Protocol family configured on the logical interface. Possible values are described
in the Protocol Field section under Common Output Fields Description.
MTU
Maximum labels
Maximum number of MPLS labels configured for the MPLS protocol family on
the logical interface.
Generation
detail extensive
Route Table
Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
detail extensive
Flags
Information about protocol family flags. Possible values are described in the
Family Flags Field section under Common Output Fields Description.
Mac-Validate
Failures
Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.
Addresses, Flags
Information about address flags. Possible values are described in the Addresses
Flags section under Common Output Fields Description.
Destination
Local
Broadcast
Generation
detail extensive
Sample Output
show interfaces (Aggregated Ethernet)
user@host> show interfaces ae0
1503
1504
7375
7375
1 expedited-fo
2 assured-forw
3 network-cont
2268
2268
Logical interface ae0.0 (Index 72) (SNMP ifIndex 60) (Generation 18)
Flags: SNMP-Traps 16384 Encapsulation: ENET2
Statistics
Packets
pps
Bytes
bps
Bundle:
Input :
0
0
0
0
Output:
0
0
0
0
Link:
fe-0/1/0.0
Input :
0
0
0
0
Output:
0
0
0
0
fe-0/1/2.0
Input :
0
0
0
0
Output:
0
0
0
0
fe-0/1/3.0
Input :
0
0
0
0
Output:
0
0
0
0
Marker Statistics:
Marker Rx
Resp Tx
Unknown Rx
Illegal Rx
fe-0/1/0.0
0
0
0
0
fe-0/1/2.0
0
0
0
0
fe-0/1/3.0
0
0
0
0
Protocol inet, MTU: 1500, Generation: 37, Route table: 0
Flags: Is-Primary, Mac-Validate-Strict
Mac-Validate Failures: Packets: 0, Bytes: 0
Destination: 10.100.1/24, Local: 10.100.1.2, Broadcast: 10.100.1.255,
Generation: 49
7375
7375
1 expedited-fo
2 assured-forw
3 network-cont
2268
2268
1505
Logical interface ae0.0 (Index 73) (SNMP ifIndex 563) (Generation 176)
Flags: Up SNMP-Traps 0x4000 Encapsulation: ENET2
Statistics
Packets
pps
Bytes
bps
Bundle:
Input :
0
0
0
0
Output:
0
0
0
0
Adaptive Statistics:
Adaptive Adjusts:
0
Adaptive Scans :
0
Adaptive Updates:
0
Link:
fe-1/0/3.0
Input :
0
0
0
0
Output:
0
0
0
0
LACP info:
Role
System
System
Port
Port
priority
Port
identifier
priority
number
key
fe-1/0/3.0
Actor
127
00:24:dc:85:af:f0
127
fe-1/0/3.0
Partner
127
00:23:9c:c3:1f:f0
127
LACP Statistics:
LACP Rx
LACP Tx
Unknown Rx
Illegal Rx
fe-1/0/3.0
3188
3186
0
0
Marker Statistics:
Marker Rx
Resp Tx
Unknown Rx
Illegal Rx
fe-1/0/3.0
0
0
0
0
Protocol inet, MTU: 1500, Generation: 224, Route table: 0
Flags: Sendbcast-pkt-to-re
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.40.1.0/30, Local: 10.40.1.1, Broadcast: 10.40.1.3,
Generation: 187
Protocol multiservice, MTU: Unlimited, Generation: 225, Route table: 0
Flags: Is-Primary
Policer: Input: __default_arp_policer__
1506
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards:
0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Ingress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort
859777
1 expedited-fo
2 assured-forw
3 network-cont
Transmitted packets
Dropped packets
0 best-effort
1897615
1 expedited-fo
2 assured-forw
3 network-cont
662505
Logical interface ae0.451 (Index 69) (SNMP ifIndex 167) (Generation 601)
Flags: SNMP-Traps VLAN-Tag [ 0x8100.451 ] Encapsulation: VLAN-VPLS
Statistics
Packets
pps
Bytes
bps
Bundle:
Input :
289
0
25685
376
Output:
1698
4
130375
3096
Link:
ge-1/2/0.451
Input :
289
0
25685
376
Output:
0
0
0
0
ge-1/2/1.451
Input :
0
0
0
0
Output:
1698
4
130375
3096
Marker Statistics:
Marker Rx
Resp Tx
Unknown Rx
Illegal Rx
ge-1/2/0.451
0
0
0
0
ge-1/2/1.451
0
0
0
0
Protocol vpls, MTU: 1518, Generation: 849, Route table: 3
Flags: Is-Primary
Logical interface ae0.452 (Index 70) (SNMP ifIndex 170) (Generation 602)
Flags: SNMP-Traps VLAN-Tag [ 0x8100.452 ] Encapsulation: VLAN-VPLS
Statistics
Packets
pps
Bytes
bps
Bundle:
Input :
293
1
26003
1072
Output:
1694
3
130057
2400
Link:
ge-1/2/0.452
Input :
293
1
26003
1072
Output:
1694
3
130057
2400
ge-1/2/1.452
Input :
0
0
0
0
Output:
0
0
0
0
1507
Marker Statistics:
Marker Rx
Resp Tx
Unknown Rx
Illegal Rx
ge-1/2/0.452
0
0
0
0
ge-1/2/1.452
0
0
0
0
Protocol vpls, MTU: 1518, Generation: 850, Route table: 3
Flags: None
...
1508
Release Information
Description
Options
of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
Related
Documentation
view
Output Fields
Table 90 on page 1509 lists the output fields for the show interfaces demux0 (Demux
Interfaces) command. Output fields are listed in the approximate order in which they
appear.
Field Description
Level of Output
Physical Interface
Physical interface
none
1509
Table 90: show interfaces demux0 (Demux Interfaces) Output Fields (continued)
Field Name
Field Description
Level of Output
Interface index
Index number of the physical interface, which reflects its initialization sequence.
none
State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
Physical link
Admin
terse
Interface index
Index number of the physical interface, which reflects its initialization sequence.
Link
terse
Targeting summary
Status of aggregated Ethernet links that are configured with targeted distribution
(primary or backup)
extensive
Bandwidth
Bandwidth allocated to the aggregated Ethernet links that are configured with
targeted distribution.
extensive
Proto
terse
SNMP ifIndex
Generation
detail extensive
Type
Link-level type
MTU
Clocking
Speed
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
Link type
Link flags
Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description.
Enabled
Interface flags
1510
none
none
none
none
Table 90: show interfaces demux0 (Demux Interfaces) Output Fields (continued)
Field Name
Field Description
Level of Output
Physical info
detail extensive
Hold-times
detail extensive
Current address
detail extensive
Hardware address
detail extensive
Alternate link
address
detail extensive
Last flapped
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
Traffic statistics
Number and rate of bytes and packets received and transmitted on the physical
interface.
detail extensive
1511
Table 90: show interfaces demux0 (Demux Interfaces) Output Fields (continued)
Field Name
Field Description
Level of Output
Input errors
extensive
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
(FCS).
RuntsNumber of frames received that are smaller than the runt threshold.
GiantsNumber of frames received that are larger than the giant packet
threshold.
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
Input Rate
Input rate in bits per second (bps) and packets per second (pps).
none
Output errors
Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
Carrier transitionsNumber of times the interface has gone from down to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly
(perhaps once every 10 seconds), the cable, the far-end system, or the PIC
or PIM is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
Output Rate
MTU errorsNumber of packets whose size exceeded the MTU of the interface.
none
Logical Interface
Logical interface
none
Index
Index number of the logical interface, which reflects its initialization sequence.
SNMP ifIndex
Generation
detail
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
Encapsulation
1512
none
Table 90: show interfaces demux0 (Demux Interfaces) Output Fields (continued)
Field Name
Field Description
Level of Output
Name of the dynamic profile that defines the agent circuit identifier (ACI)
interface set. If configured, the ACI interface set enables the underlying demux
interface to create dynamic VLAN subscriber interfaces based on ACI
information.
Demux
none
interface.
underlying interface.
protocol-family
brief
Traffic statistics
Number and rate of bytes and packets received and transmitted on the specified
interface set.
detail extensive
interface set.
Local statistics
Number of transit bytes and packets received and transmitted on the local
interface.
detail extensive
1513
Table 90: show interfaces demux0 (Demux Interfaces) Output Fields (continued)
Field Name
Field Description
Level of Output
Transit statistics
detail extensive
NOTE: The packet and byte counts in these fields include traffic that is dropped
and does not leave the router.
IPv6 Transit
statistics
Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.
detail extensive
NOTE: The packet and byte counts in these fields include traffic that is dropped
and does not leave the router.
Input packets
none
Output packets
none
Protocol
Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description.
MTU
Maximum labels
Maximum number of MPLS labels configured for the MPLS protocol family on
the logical interface.
Generation
detail extensive
Route table
Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
detail extensive
Flags
Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description.
Mac-Validate
Failures
Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.
Addresses, Flags
Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
Destination
detail extensive
statistics none
1514
Table 90: show interfaces demux0 (Demux Interfaces) Output Fields (continued)
Field Name
Field Description
Level of Output
Local
none
Remote
terse
Broadcast
Generation
detail extensive
Link
Dynamic-profile
Name of the PPPoE service name table assigned to the PPPoE underlying
interface.
Max Sessions
Maximum number of dynamic PPPoE logical interfaces that the router can
activate on the underlying interface.
Duplicate
Protection
Direct Connect
State of the configuration to ignore DSL Forum VSAs: On or Off. When configured,
the router ignores any of these VSAs received from a directly connected CPE
device on the interface.
AC Name
Sample Output
show interfaces demux0 (Demux)
user@host> show interfaces demux0
Physical interface: demux0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 79, Generation: 129
Type: Software-Pseudo, Link-level type: Unspecified, MTU: 9192, Clocking: 1,
Speed: Unspecified
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: Unspecified, Hardware address: Unspecified
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
1515
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0,
Resource errors: 0
Logical interface demux0.0 (Index 87) (SNMP ifIndex 84) (Generation 312)
Flags: SNMP-Traps 0x4000 Encapsulation: ENET2
Demux:
Underlying interface: ge-2/0/1.0 (Index 74)
Family Inet Source prefixes, total 1
Prefix: 1.1.1/24
Traffic statistics:
Input bytes :
0
Output bytes :
1554
Input packets:
0
Output packets:
37
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
1554
Input packets:
0
Output packets:
37
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 395, Route table: 0
Flags: Is-Primary, Mac-Validate-Strict
Mac-Validate Failures: Packets: 0, Bytes: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 11.1.1/24, Local: 11.1.1.1, Broadcast: 11.1.1.255,
Generation: 434
1516
Demux:
Underlying interface: ae0 (Index 199)
Link:
ge-1/0/0
ge-1/1/0
Input packets : 0
Output packets: 0
Protocol pppoe
Dynamic Profile: pppoe-profile,
Service Name Table: service-table1,
Max Sessions: 100, Duplicate Protection: On,
Direct Connect: Off,
AC Name: pppoe-server-1
show interfaces demux0 extensive (Targeted Distribution for Aggregated Ethernet Links)
user@host> show interfaces demux0.1073741824 extensive
Logical interface demux0.1073741824 (Index 75) (SNMP ifIndex 558) (Generation
346)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.1 ] Encapsulation: ENET2
Demux:
Underlying interface: ae0 (Index 201)
Link:
ge-1/0/0
ge-1/1/0
ge-2/0/7
ge-2/0/8
Targeting summary:
ge-1/1/0, primary, Physical link is Up
ge-2/0/8, backup, Physical link is Up
Bandwidth: 1000mbps
1517
Description
Options
Additional Information
The transceivers are polled in 1-second intervals for diagnostics data, warnings, and
alarms. The alarms do not cause the links to go down or the LEDs to change color, nor
generate SNMP traps. Changes in alarm and warning status generate system log
messages.
Thresholds that trigger a high alarm, low alarm, high warning, or low warning are set by
the transceiver vendors. Generally, a high alarm or low alarm indicates that the optics
module is not operating properly. This information can be used to diagnose why a device
is not working.
You can configure the P2-10G-40G-QSFPP PIC to operate either in 10-Gigabit Ethernet
mode or in 40-Gigabit Ethernet mode. When the PIC is in 40-Gigabit Ethernet mode, you
must execute the show interfaces diagnostics optics et-fpc/pic/port command. The output
of this command displays the diagnostic optics information of the corresponding
40-Gigabit Ethernet port of the PIC. However, when the PIC is in 10-Gigabit Ethernet
mode, you must execute the show interfaces diagnostics optics et-fpc/pic/port:channel
command. The output of this command displays the diagnostic optics information of
the corresponding 10-Gigabit Ethernet port of the PIC. For information about the
P2-10G-40G-QSFPP PIC, see P2-10G-40G-QSFPP PIC Overview on page 379.
1518
Required Privilege
Level
Related
Documentation
view
Supported Network Interface Standards by Transceiver for ACX, M, MX, and T Series
Routers
show interfaces diagnostics optics (DWDM and DWDM OTN) on page 1531
show interfaces diagnostics optics (MPC6E with OTN MIC) on page 1532
show interfaces diagnostics optics (Bidirectional SFP) on page 1532
show interfaces diagnostics optics (SFP) on page 1533
show interfaces diagnostics optics (SFP) on page 1534
show interfaces diagnostics optics (XFP and CFP Optics) on page 1535
show interfaces diagnostics optics for 10-Gigabit Ethernet (PTX
24-10GE-SFPP) on page 1536
show interfaces diagnostics optics for 40-Gigabit Ethernet on page 1536
show interfaces diagnostics optics (P1-PTX-24-10G-W-SFPP ) on page 1539
show interfaces diagnostics optics (P2-10G-40G-QSFPP PIC in 40-Gigabit Ethernet
speed) on page 1540
show interfaces diagnostics optics (P2-10G-40G-QSFPP PIC in 10-Gigabit Ethernet
speed) on page 1542
Output Fields
Table 91 on page 1519 lists the output fields for the show interfaces diagnostics optics
command for DWDM and DWDM OTN PICs. Output fields are listed in the approximate
order in which they appear.
Table 91: show interfaces diagnostics optics Output Fields for 10-Gigabit Ethernet DWDM and
DWDM OTN PICs
Field Name
Field Description
Physical interface
Magnitude of the laser bias power setting current, in milliamperes (mA). The laser bias provides direct
modulation of laser diodes and modulates currents.
Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm). This is a software
equivalent to the LsPOWMON pin in hardware.
Average received optical power, in mW and dBm. This indicator is a software equivalent to the
RxPOWMON pin in hardware. Average optical power is vendor-specific.
Laser temperature
alarm
1519
Table 91: show interfaces diagnostics optics Output Fields for 10-Gigabit Ethernet DWDM and
DWDM OTN PICs (continued)
Field Name
Field Description
Modulator temperature
alarm
Tx multiplexer FIFO
error alarm
Transmit multiplexer first in, first out (FIFO) error alarm: On or Off.
Rx loss of average
optical power alarm
Rx loss of AC power
alarm
Table 92 on page 1520 lists the output fields for the show interfaces diagnostics optics
command when the router is operating with bidirectional SFP optics. Output fields are
listed in the approximate order in which they appear.
Table 92: show interfaces diagnostics optics Output Fields for Gigabit Ethernet Bidirectional
SFP Optics
Field Name
Field Description
Physical interface
Magnitude of the laser bias power setting current, in milliamperes (mA). The laser bias provides direct
modulation of laser diodes and modulates currents.
Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm).
Module temperature
Module voltage
1520
Table 92: show interfaces diagnostics optics Output Fields for Gigabit Ethernet Bidirectional
SFP Optics (continued)
Field Name
Field Description
Wavelength Channel
number
Wavelength setpoint
Tx Dither
Frequency Error
Wavelength Error
Module temperature
high alarm
Module temperature
low alarm
Module temperature
high warning
Module temperature
low warning
1521
Table 92: show interfaces diagnostics optics Output Fields for Gigabit Ethernet Bidirectional
SFP Optics (continued)
Field Name
Field Description
Wavelength unlocked
alarm
TxTune
Display whether the optical transmit side is not ready due to tuning.
Vendor-specified threshold for the laser bias current high alarm: 70.000 mA.
Vendor-specified threshold for the laser bias current low alarm: 0.0002 mA.
Vendor-specified threshold for the laser bias current high warning: 65.000 mA.
Vendor-specified threshold for the laser bias current low warning: 0.0002 mA.
Vendor-specified threshold for the laser output power high alarm: 1.0000 mW or 0.00 dBm.
Vendor-specified threshold for the laser output power low alarm: 0.0560 mW or -12.52 dBm.
1522
Table 92: show interfaces diagnostics optics Output Fields for Gigabit Ethernet Bidirectional
SFP Optics (continued)
Field Name
Field Description
Vendor-specified threshold for the laser output power high warning: 0.6300 mW or -2.01 dBm.
Vendor-specified threshold for the laser output power low warning: 0.0890 mW or -10.51 dBm.
Module temperature
high alarm threshold
Vendor-specified threshold for the module temperature high alarm: 100 C or 212 F.
Module temperature
low alarm threshold
Vendor-specified threshold for the module temperature low alarm: -50 C or -58 F.
Module temperature
high warning threshold
Module temperature
low warning threshold
Vendor-specified threshold for the module temperature low warning: -48 C or -54 F.
Vendor-specified threshold for the laser Rx power high alarm: 1.9953 mW or 3.00 dBm.
Vendor-specified threshold for the laser Rx power low alarm: 0.0001 mW or -40.00 dBm.
Vendor-specified threshold for the laser Rx power high warning: 1.0000 mW or 0.00 dBm.
Vendor-specified threshold for the laser Rx power low warning: 0.0010 mW or -30.00 dBm.
Table 93 on page 1524 lists the output fields for the show interfaces diagnostics optics
command for SFP transceivers. Output fields are listed in the approximate order in which
they appear.
1523
Table 93: show interfaces diagnostics Output Fields for Gigabit Ethernet SFP Transceivers
Field Name
Field Description
Physical interface
Module temperature
Module voltage
Laser rx power
Laser bias current high alarm: On or Off. Alarm ranges are vendor-specific.
Laser bias current low alarm: On or Off. Alarm ranges are vendor-specific.
Laser output power high alarm: On or Off. Alarm ranges are vendor-specific.
Laser output power low alarm: On or Off. Alarm ranges are vendor-specific.
Laser receive power high alarm: On or Off. Alarm ranges are vendor-specific.
Laser receive power low alarm: On or Off. Alarm ranges are vendor-specific.
Laser bias current high warning: On or Off. Warning ranges are vendor-specific.
Laser bias current low warning: On or Off. Warning ranges are vendor-specific.
Laser output power high warning: On or Off. Warning ranges are vendor-specific.
Laser output power low warning: On or Off. Warning ranges are vendor-specific.
Module temperature
high warning
1524
Table 93: show interfaces diagnostics Output Fields for Gigabit Ethernet SFP
Transceivers (continued)
Field Name
Field Description
Module temperature
low warning
Laser receive power high warning: On or Off. Warning ranges are vendor-specific.
Laser receive power low warning: On or Off. Warning ranges are vendor-specific.
Laser bias current high alarm threshold. Alarm threshold ranges are vendor-specific.
Laser bias current low alarm threshold. Alarm threshold ranges are vendor-specific.
Laser bias current high warning threshold. Warning ranges are vendor-specific.
Laser bias current low warning threshold. Warning ranges are vendor-specific.
Laser output power high alarm threshold. Alarm threshold ranges are vendor-specific.
Laser output power low alarm threshold. Alarm threshold ranges are vendor-specific.
Laser output power high warning threshold. Warning ranges are vendor-specific.
Laser output power low warning threshold. Warning ranges are vendor-specific.
Module temperature
high alarm threshold
Module temperature high alarm threshold. Alarm threshold ranges are vendor-specific.
Module temperature
low alarm threshold
Module temperature low alarm threshold. Alarm threshold ranges are vendor-specific.
Module temperature
high warning threshold
Module temperature
low warning threshold
1525
Table 93: show interfaces diagnostics Output Fields for Gigabit Ethernet SFP
Transceivers (continued)
Field Name
Field Description
Laser receive power high alarm threshold. Alarm threshold ranges are vendor-specific.
Laser receive power low alarm threshold. Alarm threshold ranges are vendor-specific.
Laser receive power high warning threshold. Warning threshold ranges are vendor-specific.
Laser receive power high warning threshold. Warning threshold ranges are vendor-specific.
Table 94 on page 1526 lists the output fields for the show interfaces diagnostics optics
command for 10-Gigabit Ethernet transceivers. Output fields are listed in the approximate
order in which they appear.
Table 94: show interfaces diagnostics optics Output Fields for 10-Gigabit Ethernet Transceivers
Field Name
Field Description
Physical interface
Module temperature
Laser rx power
Laser bias current high alarm: On or Off. Alarm ranges are vendor-specific.
Laser bias current low alarm: On or Off. Alarm ranges are vendor-specific.
Laser output power high alarm: On or Off. Alarm ranges are vendor-specific.
1526
Table 94: show interfaces diagnostics optics Output Fields for 10-Gigabit Ethernet
Transceivers (continued)
Field Name
Field Description
Laser output power low alarm: On or Off. Alarm ranges are vendor-specific.
Laser receive power high alarm: On or Off. Alarm ranges are vendor-specific.
Laser receive power low alarm: On or Off. Alarm ranges are vendor-specific.
Laser bias current high warning: On or Off. Warning ranges are vendor-specific.
Laser bias current low warning: On or Off. Warning ranges are vendor-specific.
Laser output power high warning: On or Off. Warning ranges are vendor-specific.
Laser output power low warning: On or Off. Warning ranges are vendor-specific.
Module temperature
high warning
Module temperature
low warning
Laser receive power high warning: On or Off. Warning ranges are vendor-specific.
Laser receive power low warning: On or Off. Warning ranges are vendor-specific.
Laser bias current high alarm threshold. Alarm threshold ranges are vendor-specific.
Laser bias current low alarm threshold. Alarm threshold ranges are vendor-specific.
Laser output power high alarm threshold. Alarm threshold ranges are vendor-specific.
1527
Table 94: show interfaces diagnostics optics Output Fields for 10-Gigabit Ethernet
Transceivers (continued)
Field Name
Field Description
Laser output power low alarm threshold. Alarm threshold ranges are vendor-specific.
Module temperature
high alarm threshold
Module temperature high alarm threshold. Alarm threshold ranges are vendor-specific.
Module temperature
low alarm threshold
Module temperature low alarm threshold. Alarm threshold ranges are vendor-specific.
Laser receive power high alarm threshold. Alarm threshold ranges are vendor-specific.
Laser receive power low alarm threshold. Alarm threshold ranges are vendor-specific.
Laser bias current high warning threshold. Warning ranges are vendor-specific.
Laser bias current low warning threshold. Warning ranges are vendor-specific.
Laser output power high warning threshold. Warning ranges are vendor-specific.
Laser output power low warning threshold. Warning ranges are vendor-specific.
Module temperature
high warning threshold
Module temperature
low warning threshold
Laser receive power high warning threshold. Warning threshold ranges are vendor-specific.
Laser receive power low warning threshold. Warning threshold ranges are vendor-specific.
Table 95 on page 1529 lists the output fields for the show interfaces diagnostics optics
command for XFP transceivers. Output fields are listed in the approximate order in which
they appear.
1528
Table 95: show interfaces diagnostics optics Output Fields for 10-Gigabit Ethernet XFP
Transceivers
Field Name
Field Description
Physical interface
Magnitude of the laser bias power setting current, in milliamperes (mA). The laser bias provides direct
modulation of laser diodes and modulates currents.
Laser output power, in milliwatts (mW) and decibels, referenced to 1.0 mW (dBm). This is a software
equivalent to the LsPOWMON pin in hardware.
Module temperature
Laser rx power
Module temperature
high alarm
Module temperature
low alarm
Module temperature
high warning
Module temperature
low warning
1529
Table 95: show interfaces diagnostics optics Output Fields for 10-Gigabit Ethernet XFP
Transceivers (continued)
Field Name
Field Description
Module not ready alarm. When on, indicates the module has an operational fault. Displays on or off.
Module power down alarm. When on, module is in a limited power mode, low for normal operation.
Displays on or off.
Any condition leading to invalid data on the transmit path. Displays on or off.
Any condition leading to invalid data on the transmit path. Displays on or off.
Transmit clock and data recovery (CDR) loss of lock. Loss of lock on the transmit side of the CDR.
Displays on or off.
Any condition leading to invalid data on the receive path. Displays on or off.
Receive Loss of Signal alarm. When on, indicates insufficient optical input power to the module.
Displays on or off.
Receive CDR loss of lock. Loss of lock on the receive side of the CDR. Displays on or off.
Vendor-specified threshold for the laser bias current high alarm: 130.000 mA.
Vendor-specified threshold for the laser bias current low alarm: 10.000 mA.
Vendor-specified threshold for the laser bias current high warning: 120.000 mA.
Vendor-specified threshold for the laser bias current low warning: 12.000 mA.
Vendor-specified threshold for the laser output power high alarm: 0.8910 mW or -0.50 dBm.
1530
Table 95: show interfaces diagnostics optics Output Fields for 10-Gigabit Ethernet XFP
Transceivers (continued)
Field Name
Field Description
Vendor-specified threshold for the laser output power low alarm: 0.2230 mW or -6.52 dBm.
Vendor-specified threshold for the laser output power high warning: 0.7940 mW or -100 dBm.
Vendor-specified threshold for the laser output power low warning: 0.2510 mW or -600 dBm.
Module temperature
high alarm threshold
Module temperature
low alarm threshold
Module temperature
high warning threshold
Module temperature
low warning threshold
Vendor-specified threshold for the laser Rx power high alarm: 1.2589 mW or 1.00 dBm.
Vendor-specified threshold for the laser Rx power low alarm: 0.0323 mW or -14.91 dBm.
Vendor-specified threshold for the laser Rx power high warning: 1.1220 mW or 0.50 dBm.
Vendor-specified threshold for the laser Rx power low warning: 0.0363 mW or -14.40 dBm.
Sample Output
show interfaces diagnostics optics (DWDM and DWDM OTN)
user@host> show interfaces diagnostics optics ge-5/0/0
Physical interface: ge-5/0/0
Laser bias current
: 79.938 mA
Laser output power
: 1.592 mW / 2.02 dBm
Receiver signal average optical power : 1.3854 mW / 1.42 dBm
Laser end-of-life alarm
: Off
Laser wavelength alarm
: Off
Laser bias current alarm
: Off
Laser temperature alarm
: Off
Laser power alarm
: Off
Modulator temperature alarm
: Off
Modulator bias alarm
: Off
Tx multiplexer FIFO error alarm
: Off
1531
Tx
Rx
Rx
Rx
loss
loss
loss
loss
of
of
of
of
Off
Off
Off
Off
7.806 mA
0.5660 mW / -2.47 dBm
32 degrees C / 89 degrees F
3.3560 V
0.5501 mW / -2.60 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
11.800 mA
4.000 mA
10.800 mA
5.000 mA
0.8310 mW / -0.80 dBm
0.2510 mW / -6.00 dBm
0.6600 mW / -1.80 dBm
0.3160 mW / -5.00 dBm
78 degrees C / 172 degrees F
-13 degrees C / 9 degrees F
73 degrees C / 163 degrees F
-8 degrees C / 18 degrees F
3.700 V
2.900 V
3.600 V
3.000 V
1.0000 mW / 0.00 dBm
0.0100 mW / -20.00 dBm
0.7943 mW / -1.00 dBm
0.0158 mW / -18.01 dBm
1532
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
23.408 mA
1.479 mW / 1.70 dBm
37 degrees C / 99 degrees F
0.121 mW / -9.16 dBm
Off
Off
Off
Off
Off
Off
Off
Off
1533
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Off
Off
Off
Off
Off
Off
Off
Off
31.000 mA
10.000 mA
6.000 mW / 7.78 dBm
0.100 mW / -10.00 dBm
85 degrees C / 185 degrees F
0 degrees C / 32 degrees F
1.000 mW / 0.00 dBm
0.001 mW / -30.00 dBm
28.000 mA
11.000 mA
5.000 mW / 6.99 dBm
0.500 mW / -3.01 dBm
70 degrees C / 158 degrees F
10 degrees C / 50 degrees F
0.501 mW / -3.00 dBm
0.001 mW / -28.86 dBm
1534
:
:
:
49.010 mA
1.263 mW / 1.01 dBm
17 degrees C / 62 degrees F
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
4.21 V
0.060 mW / -12.21 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
70.000 mA
20.000 mA
65.000 mA
25.000 mA
1.4120 mW / 1.50 dBm
0.1990 mW / -7.01 dBm
13 degrees C / 9 degrees F
75 degrees C /167 degrees F
10 degrees C / 14 degrees F
Module voltage
Module voltage
Module voltage
Module voltage
Laser rx power
Laser rx power
Laser rx power
Laser rx power
:
:
:
:
:
:
:
:
5.71 V
2.05 V
5.20 V
3.11 V
1.7783
0.0100
1.5849
0.0158
mW
mW
mW
mW
/
/
/
/
2.50 dBm
-20.00 dBm
2.00 dBm
-18.01 dBm
52.060 mA
0.5640 mW / -2.49 dBm
31 degrees C / 88 degrees F
0.0844 mW / -10.74 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
130.000 mA
10.000 mA
120.000 mA
12.000 mA
0.8910 mW / -0.50 dBm
0.2230 mW / -6.52 dBm
0.7940 mW / -1.00 dBm
0.2510 mW / -6.00 dBm
90 degrees C / 194 degrees F
-5 degrees C / 23 degrees F
1535
:
:
:
:
:
:
1536
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
34 degrees C / 94 degrees F
3.4720 V
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
80 degrees C / 176 degrees F
-10 degrees C / 14 degrees F
75 degrees C / 167 degrees F
-5 degrees C / 23 degrees F
3.5990 V
3.0000 V
3.5000 V
3.0990 V
100.000 mA
10.000 mA
80.000 mA
15.000 mA
2.8180 mW / 4.50 dBm
0.2390 mW / -6.22 dBm
2.2380 mW / 3.50 dBm
0.3010 mW / -5.21 dBm
2.5119 mW / 4.00 dBm
0.0316 mW / -15.00 dBm
1.9953 mW / 3.00 dBm
0.0631 mW / -12.00 dBm
80 degrees C / 176 degrees F
-10 degrees C / 14 degrees F
75 degrees C / 167 degrees F
-5 degrees C / 23 degrees F
:
:
:
:
:
:
:
:
:
:
:
:
:
27.829 mA
0.851 mW / -0.70 dBm
34 degrees C / 94 degrees F
0.894 mW / -0.49 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
1537
1538
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
35.374 mA
0.896 mW / -0.48 dBm
34 degrees C / 94 degrees F
0.707 mW / -1.50 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
29.173 mA
0.890 mW / -0.51 dBm
34 degrees C / 94 degrees F
0.704 mW / -1.52 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
:
:
:
:
:
:
:
:
:
Off
Off
Off
Off
Off
Off
Off
Off
Off
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
36.164 mA
0.899 mW / -0.46 dBm
34 degrees C / 94 degrees F
0.892 mW / -0.50 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
13.356 mA
0.2210 mW / -6.56 dBm
36 degrees C / 96 degrees F
3.2180 V
0.2429 mW / -6.15 dBm
1
1568.80 nm
Disabled
0.00 GHz
0.00 nm
Off
Off
Off
Off
Off
Off
Off
Off
Off
1539
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
70.000 mA
0.002 mA
65.000 mA
0.002 mA
1.0000 mW / 0.00 dBm
0.0560 mW / -12.52 dBm
0.6300 mW / -2.01 dBm
0.0890 mW / -10.51 dBm
100 degrees C / 212 degrees F
-50 degrees C / -58 degrees F
95 degrees C / 203 degrees F
-48 degrees C / -54 degrees F
3.700 V
2.900 V
3.600 V
3.000 V
1.9953 mW / 3.00 dBm
0.0001 mW / -40.00 dBm
1.0000 mW / 0.00 dBm
0.0010 mW / -30.00 dBm
1540
30 degrees C / 85 degrees F
3.2760 V
Off
Off
Off
Off
Off
Off
Off
Off
75 degrees C / 167 degrees F
5 degrees C / 41 degrees F
70 degrees C / 158 degrees F
0 degrees C / 32 degrees F
3.6300 V
2.9700 V
3.4640 V
3.1340 V
10.000 mA
0.500 mA
9.500 mA
1.000 mA
:
:
:
:
:
:
:
:
0.0000
0.0000
0.0000
0.0000
2.1878
0.0446
1.7378
0.1122
mW
mW
mW
mW
mW
mW
mW
mW
/
/
/
/
/
/
/
/
- Inf dBm
- Inf dBm
- Inf dBm
- Inf dBm
3.40 dBm
-13.51 dBm
2.40 dBm
-9.50 dBm
:
:
:
:
:
:
:
:
:
:
:
:
:
7.065 mA
0.710 mW / -1.49 dBm
0.472 mW / -3.26 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
:
:
:
:
:
:
:
:
:
:
:
:
:
6.978 mA
0.771 mW / -1.13 dBm
0.450 mW / -3.47 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
:
:
:
:
:
:
:
:
:
:
:
:
:
6.955 mA
0.760 mW / -1.19 dBm
0.556 mW / -2.55 dBm
Off
Off
Off
Off
Off
Off
Off
Off
Off
Off
:
:
:
:
:
:
:
:
:
:
6.981 mA
0.736 mW / -1.33 dBm
0.537 mW / -2.70 dBm
Off
Off
Off
Off
Off
Off
Off
1541
:
:
:
Off
Off
Off
1542
Output Fields
Field Description
Physical interface
SNMP ifIndex
ES-L/P
SES-L/P
UAS-L/P
Sample Output
show interfaces far-end-interval coc12-5/2/0
user@host> show interfaces far-end-interval coc12-5/2/0
Physical interface: coc12-5/2/0, SNMP ifIndex: 121
05:30-current:
ES-L: 1, SES-L: 1, UAS-L: 0
05:15-05:30:
ES-L: 0, SES-L: 0, UAS-L: 0
05:00-05:15:
ES-L: 0, SES-L: 0, UAS-L: 0
04:45-05:00:
ES-L: 0, SES-L: 0, UAS-L: 0
04:30-04:45:
ES-L: 0, SES-L: 0, UAS-L: 0
04:15-04:30:
ES-L: 0, SES-L: 0, UAS-L: 0
04:00-04:15:
...
1543
1544
0
0
0
0
0
0
Release Information
Description
Options
of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Level of Output
Physical interface
All levels
Enabled
State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
All levels
Interface index
Index number of the physical interface, which reflects its initialization sequence.
SNMP ifIndex
Generation
detail extensive
Physical Interface
1545
Field Description
Level of Output
Link-level type
All levels
MTU
All levels
Link-mode
extensive
Half-duplex
Speed
All levels
Loopback
All levels
Source filtering
All levels
LAN-PHY mode
All levels
WAN-PHY mode
All levels
Unidirectional
All levels
Flow control
All levels
Auto-negotiation
All levels
Remote-fault
All levels
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
Interface flags
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
All levels
Link flags
Information about the link. Possible values are described in the Links Flags
section under Common Output Fields Description.
All levels
Wavelength
All levels
Frequency
All levels
1546
Field Description
Level of Output
CoS queues
Schedulers
extensive
Hold-times
detail extensive
Current address
Hardware address
Last flapped
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate
Input rate in bits per second (bps) and packets per second (pps).
None specified
Output Rate
None specified
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
Traffic statistics
Number and rate of bytes and packets received and transmitted on the physical
interface.
detail extensive
Gigabit Ethernet and 10-Gigabit Ethernet IQ PICs count the overhead and CRC
bytes.
For Gigabit Ethernet IQ PICs, the input byte counts vary by interface type. For
more information, see Table 31 under the show interfaces (10-Gigabit Ethernet)
command.
1547
Field Description
Level of Output
Input errors
Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
(FCS).
RuntsNumber of frames received that are smaller than the runt threshold.
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
Layer 3 (usually IPv4) sanity checks of the header. For example, a frame with
less than 20 bytes of available IP header is discarded. L3 incomplete errors
can be ignored by configuring the ignore-l3-incompletes statement.
L2 channel errorsNumber of times the software did not find a valid logical
FIFO errorsNumber of FIFO errors in the receive direction that are reported
by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
1548
Field Description
Level of Output
Output errors
Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
Carrier transitionsNumber of times the interface has gone from down to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly
(perhaps once every 10 seconds), the cable, the far-end system, or the PIC
or PIM is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
only full-duplex operation, so for Gigabit Ethernet PICs, this number should
always remain 0. If it is nonzero, there is a software bug.
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or possibly
malfunctioning hardware.
ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
Egress queues
MTU errorsNumber of packets whose size exceeded the MTU of the interface.
detail extensive
NOTE: In DPCs that are not of the enhanced type, such as DPC 40x 1GE R, DPCE
20x 1GE + 2x 10GE R, or DPCE 40x 1GE R, you might notice a discrepancy in the
output of the show interfaces command because incoming packets might be
counted in the Egress queues section of the output. This problem occurs on
non-enhanced DPCs because the egress queue statistics are polled from IMQ
(Inbound Message Queuing) block of the I-chip. The IMQ block does not
differentiate between ingress and egress WAN traffic; as a result, the combined
statistics are displayed in the egress queue counters on the Routing Engine. In
a simple VPLS scenorio, if there is no MAC entry in DMAC table (by sending
unidirectional traffic), traffic is flooded and the input traffic is accounted in IMQ.
For bidirectional traffic (MAC entry in DMAC table), if the outgoing interface is
on the same I-chip then both ingress and egress statistics are counted in a
combined way. If the outgoing interface is on a different I-chip or FPC, then only
egress statistics are accounted in IMQ. This behavior is expected with
non-enhanced DPCs
Queue counters
(Egress)
CoS queue number and its associated user-configured forwarding class name.
detail extensive
1549
Field Description
Level of Output
Ingress queues
extensive
Queue counters
(Ingress)
CoS queue number and its associated user-configured forwarding class name.
Displayed on IQ2 interfaces.
extensive
Ethernet-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain amount of time, it is promoted to an alarm.
Based on the routing device configuration, an alarm can ring the red or yellow
alarm bell on the routing device, or turn on the red or yellow alarm LED on the
craft interface. These fields can contain the value None or Link.
LinkInterface has lost its link state, which usually means that the cable is
unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
OTN FEC statistics
The forward error correction (FEC) counters provide the following statistics:.
Corrected Error RatioThe corrected error ratio in the last 25 seconds. For
detail extensive
Bit errorsThe number of seconds during which at least one bit error rate
1550
Field Description
Level of Output
MAC statistics
Receive and Transmit statistics reported by the PIC's MAC subsystem, including
extensive
the following:
Total octets and total packetsTotal number of octets and packets. For
Gigabit Ethernet IQ PICs, the received octets count varies by interface type.
For more information, see Table 31 under the show interfaces (10-Gigabit
Ethernet) command.
(excluding framing bits, but including FCS octets) of between 64 and 1518
octets, inclusive, and had either a bad FCS with an integral number of octets
(FCS Error) or a bad FCS with a nonintegral number of octets (Alignment
Error).
FIFO errorNumber of FIFO errors that are reported by the ASIC on the PIC.
code.
Jabber framesNumber of frames that were longer than 1518 octets (excluding
framing bits, but including FCS octets), and had either an FCS error or an
alignment error. This definition of jabber is different from the definition in
IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition in which any packet exceeds 20
ms. The allowed range to detect jabber is from 20 ms to 150 ms.
length (excluding framing bits, but including FCS octets), and had either an
FCS error or an alignment error. Fragment frames normally increment because
both runts (which are normal occurrences caused by collisions) and noise
hits are counted.
VLAN tagged framesNumber of frames that are VLAN tagged. The system
uses the TPID of 0x8100 in the frame to determine whether a frame is tagged
or not.
extensive
OTN Transmitted
Overhead Bytes
extensive
1551
Field Description
Level of Output
Filter statistics
Receive and Transmit statistics reported by the PIC's MAC address filter
extensive
destination MAC address of the packet is not on the accept list. It is normal
for this value to increment. When it increments very quickly and no traffic is
entering the routing device from the far-end system, either there is a bad ARP
entry on the far-end system, or multicast routing is not on and the far-end
system is sending many multicast packets to the local routing device (which
the routing device is rejecting).
source MAC address of the packet is not on the accept list. The value in this
field should increment only if source MAC address filtering has been enabled.
If filtering is enabled, if the value increments quickly, and if the system is not
receiving traffic that it should from the far-end system, it means that the
user-configured source MAC addresses for this interface are incorrect.
Output packet countNumber of packets that the filter has given to the MAC
hardware.
minimum Ethernet size (60 bytes) before giving the packet to the MAC
hardware. Usually, padding is done only on small ARP packets, but some very
small IP packets can also require padding. If this value increments rapidly,
either the system is trying to find an ARP entry for a far-end system that does
not exist or it is misconfigured.
the filter was given to transmit. These packets are usually aged packets or
are the result of a bandwidth problem on the FPC hardware. On a normal
system, the value of this field should not increment.
dedicated to destination and source MAC address filters. There can only be
up to 64 source entries. If source filtering is disabled, which is the default, the
values for these fields should be 0.
PMA PHY
CountNumber of times that the defect has gone from inactive to active.
extensive
Subfields are:
1552
Field Description
Level of Output
WIS section
extensive
CountNumber of times that the defect has gone from inactive to active.
Subfields are:
WIS line
LOLLoss of light
LOFLoss of frame
(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information.
CountNumber of times that the defect has gone from inactive to active.
extensive
Subfields are:
1553
Field Description
Level of Output
WIS path
(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information.
extensive
CountNumber of times that the defect has gone from inactive to active.
Subfields are:
1554
UNEQ-PPath unequipped
Field Description
Level of Output
Autonegotiation
information
extensive
Negotiation status:
Link partner:
detected on receive).
Received path
trace, Transmitted
path trace
extensive
Packet Forwarding
Engine
configuration
extensive
1555
Field Description
Level of Output
CoS information
extensive
This value is nonzero only if the buffer size is configured in terms of time.
Logical Interface
Logical interface
All levels
Index
Index number of the logical interface, which reflects its initialization sequence.
SNMP ifIndex
Generation
detail extensive
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
All levels
VLAN-Tag
Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN
tag or for both the outer and inner (In) VLAN tags.
pushAn outer VLAN tag is pushed in front of the existing VLAN tag.
swapThe outer VLAN tag of the incoming frame is overwritten with the user
none
pushAn outer VLAN tag is pushed in front of the existing VLAN tag.
swap-swapBoth the inner and the outer VLAN tags of the incoming frame
pop-swapThe outer VLAN tag of the incoming frame is removed, and the
inner VLAN tag of the incoming frame is replaced by the user-specified VLAN
tag value. The inner tag becomes the outer tag in the final frame.
pop-popBoth the outer and inner VLAN tags of the incoming frame are
removed.
1556
Field Description
Level of Output
Demux:
Encapsulation
All levels
Protocol
Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description.
MTU
Maximum labels
Maximum number of MPLS labels configured for the MPLS protocol family on
the logical interface.
Traffic statistics
Number and rate of bytes and packets received and transmitted on the specified
interface set.
detail extensive
interface set
Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.
extensive
Local statistics
Number and rate of bytes and packets destined to the routing device.
extensive
Transit statistics
extensive
NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the logical
interface egress statistics might not accurately reflect the traffic on the wire
when output shaping is applied. Traffic management output shaping might
drop packets after they are tallied by the Output bytes and Output packets
interface counters. However, correct values display for both of these egress
statistics when per-unit scheduling is enabled for the Gigabit Ethernet IQ2
physical interface, or when a single logical interface is actively using a shared
scheduler.
Generation
detail extensive
Route Table
Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
Flags
Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description.
detail extensive
Donor interface
1557
Field Description
Level of Output
Preferred source
address
Input Filters
Names of any input filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parenthesis next to all interfaces.
detail extensive
Output Filters
Names of any output filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parenthesis next to all interfaces.
detail extensive
Mac-Validate
Failures
Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.
Addresses, Flags
Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
protocol-family
Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.
brief
Flags
Information about address flag (possible values are described in the Addresses
Flags section under Common Output Fields Description.
Destination
Local
Broadcast
Generation
detail extensive
Sample Output
show interfaces (Fast Ethernet)
user@host> show interfaces fe-0/0/0
Physical interface: fe-0/0/0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 22
Link-level type: Ethernet, MTU: 1514, Speed: 100mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
CoS queues
: 4 supported, 4 maximum usable queues
Current address: 00:05:85:02:38:00, Hardware address: 00:05:85:02:38:00
Last flapped
: 2006-01-20 14:50:58 PST (2w4d 00:44 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Active alarms : None
Active defects : None
Logical interface fe-0/0/0.0 (Index 66) (SNMP ifIndex 198)
Flags: SNMP-Traps Encapsulation: ENET2
1558
1559
Traffic statistics:
Input bytes :
0
0 bps
Output bytes :
42
0 bps
Input packets:
0
0 pps
Output packets:
1
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
FIFO errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 3, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Active alarms : None
Active defects : None
MAC statistics:
Receive
Transmit
Total octets
0
64
Total packets
0
1
Unicast packets
0
0
Broadcast packets
0
1
Multicast packets
0
0
CRC/Align errors
0
0
FIFO errors
0
0
MAC control frames
0
0
MAC pause frames
0
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
1
Output packet pad count
0
Output packet error count
0
CAM destination filters: 1, CAM source filters: 0
Autonegotiation information:
Negotiation status: Complete
Link partner:
Link partner: Full-duplex, Flow control: None, Remote fault: Ok
Local resolution:
Packet Forwarding Engine configuration:
Destination slot: 0
CoS information:
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 best-effort
95
950000000 95
0
low
none
3 network-control
5
50000000
5
0
low
none
Logical interface fe-0/0/0.0 (Index 66) (SNMP ifIndex 198) (Generation 67)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 105, Route table: 0
Flags: None
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.10.10/24, Local: 10.10.10.1, Broadcast: 10.10.10.255,
Generation: 136
1560
Release Information
Description
Options
interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information about network interfaces.
snmp-index snmp-index(Optional) Display information for the specified SNMP index
of the interface.
statistics(Optional) Display static interface statistics.
Additional Information
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
In a logical system, this command displays information only about the logical interfaces
and not about the physical interfaces.
view
1561
Field Description
Level of Output
Physical interface
All levels
Enabled
State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
All levels
Interface index
Index number of the physical interface, which reflects its initialization sequence.
SNMP ifIndex
Generation
detail extensive
Link-level type
All levels
MTU
All levels
Speed
All levels
Loopback
All levels
Source filtering
All levels
LAN-PHY mode
All levels
WAN-PHY mode
All levels
Unidirectional
All levels
Flow control
All levels
Auto-negotiation
All levels
Remote-fault
All levels
Physical Interface
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
Interface flags
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
All levels
1562
Field Description
Level of Output
Link flags
Information about the link. Possible values are described in the Links Flags
section under Common Output Fields Description.
All levels
Wavelength
All levels
Frequency
All levels
CoS queues
Schedulers
extensive
Hold-times
detail extensive
Current address
Hardware address
Last flapped
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate
Input rate in bits per second (bps) and packets per second (pps). The value in
this field also includes the Layer 2 overhead bytes for ingress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or the
logical interface level.
None
Output Rate
Output rate in bps and pps. The value in this field also includes the Layer 2
overhead bytes for egress traffic on Ethernet interfaces if you enable accounting
of Layer 2 overhead at the PIC level or the logical interface level.
None
Time when the statistics for the interface were last set to zero.
detail extensive
Egress account
overhead
Layer 2 overhead in bytes that is accounted in the interface statistics for egress
traffic.
detail extensive
Ingress account
overhead
Layer 2 overhead in bytes that is accounted in the interface statistics for ingress
traffic.
detail extensive
1563
Field Description
Level of Output
Traffic statistics
Number and rate of bytes and packets received and transmitted on the physical
interface.
detail extensive
Input bytesNumber of bytes received on the interface. The value in this field
also includes the Layer 2 overhead bytes for ingress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or
the logical interface level.
this field also includes the Layer 2 overhead bytes for egress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or
the logical interface level.
Gigabit Ethernet and 10-Gigabit Ethernet IQ PICs count the overhead and CRC
bytes.
For Gigabit Ethernet IQ PICs, the input byte counts vary by interface type. For
more information, see Table 31 under the show interfaces (10-Gigabit Ethernet)
command.
Input errors
Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
(FCS).
RuntsNumber of frames received that are smaller than the runt threshold.
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that Junos OS does not handle.
Layer 3 (usually IPv4) sanity checks of the header. For example, a frame with
less than 20 bytes of available IP header is discarded. L3 incomplete errors
can be ignored by configuring the ignore-l3-incompletes statement.
L2 channel errorsNumber of times the software did not find a valid logical
FIFO errorsNumber of FIFO errors in the receive direction that are reported
by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
1564
Field Description
Level of Output
Output errors
Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
Carrier transitionsNumber of times the interface has gone from down to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly
(perhaps once every 10 seconds), the cable, the far-end system, or the PIC
or PIM is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
NOTE: Due to accounting space limitations on certain Type 3 FPCs (which
are supported in M320 and T640 routers), the Drops field does not always
use the correct value for queue 6 or queue 7 for interfaces on 10-port 1-Gigabit
Ethernet PICs.
only full-duplex operation, so for Gigabit Ethernet PICs, this number should
always remain 0. If it is nonzero, there is a software bug.
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or possibly
malfunctioning hardware.
ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
Egress queues
MTU errorsNumber of packets whose size exceeded the MTU of the interface.
detail extensive
NOTE: In DPCs that are not of the enhanced type, such as DPC 40x 1GE R, DPCE
20x 1GE + 2x 10GE R, or DPCE 40x 1GE R, you might notice a discrepancy in the
output of the show interfaces command because incoming packets might be
counted in the Egress queues section of the output. This problem occurs on
non-enhanced DPCs because the egress queue statistics are polled from IMQ
(Inbound Message Queuing) block of the I-chip. The IMQ block does not
differentiate between ingress and egress WAN traffic; as a result, the combined
statistics are displayed in the egress queue counters on the Routing Engine. In
a simple VPLS scenario, if there is no MAC entry in DMAC table (by sending
unidirectional traffic), traffic is flooded and the input traffic is accounted in IMQ.
For bidirectional traffic (MAC entry in DMAC table), if the outgoing interface is
on the same I-chip then both ingress and egress statistics are counted in a
combined way. If the outgoing interface is on a different I-chip or FPC, then only
egress statistics are accounted in IMQ. This behavior is expected with
non-enhanced DPCs
1565
Field Description
Level of Output
Queue counters
(Egress)
CoS queue number and its associated user-configured forwarding class name.
detail extensive
Ingress queues
extensive
Queue counters
(Ingress)
CoS queue number and its associated user-configured forwarding class name.
Displayed on IQ2 interfaces.
extensive
Ethernet-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain amount of time, it is promoted to an alarm.
Based on the router configuration, an alarm can ring the red or yellow alarm
bell on the router, or turn on the red or yellow alarm LED on the craft interface.
These fields can contain the value None or Link.
LinkInterface has lost its link state, which usually means that the cable is
unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
Interface transmit
statistics
detail extensive
in the configuration. If this is not configured, the interface statistics show the
offered load on the interface.
OTN FEC statistics
The forward error correction (FEC) counters provide the following statistics:
Corrected Error RatioCorrected error ratio in the last 25 seconds. For example,
detail extensive
1566
Field Description
Level of Output
PCS statistics
detail extensive
Bit errorsNumber of seconds during which at least one bit error rate (BER)
1567
Field Description
Level of Output
MAC statistics
Receive and Transmit statistics reported by the PIC's MAC subsystem, including
extensive
the following:
Total octets and total packetsTotal number of octets and packets. For
Gigabit Ethernet IQ PICs, the received octets count varies by interface type.
For more information, see Table 31 under the show interfaces (10-Gigabit
Ethernet) command.
(excluding framing bits, but including FCS octets) of between 64 and 1518
octets, inclusive, and had either a bad FCS with an integral number of octets
(FCS Error) or a bad FCS with a nonintegral number of octets (Alignment
Error).
FIFO errorNumber of FIFO errors that are reported by the ASIC on the PIC.
code.
of oversized frames:
Jabber framesNumber of frames that were longer than 1518 octets (excluding
framing bits, but including FCS octets), and had either an FCS error or an
alignment error. This definition of jabber is different from the definition in
IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition in which any packet exceeds 20
ms. The allowed range to detect jabber is from 20 ms to 150 ms.
length (excluding framing bits, but including FCS octets) and had either an
FCS error or an alignment error. Fragment frames normally increment because
both runts (which are normal occurrences caused by collisions) and noise
hits are counted.
VLAN tagged framesNumber of frames that are VLAN tagged. The system
uses the TPID of 0x8100 in the frame to determine whether a frame is tagged
or not.
NOTE: The 20-port Gigabit Ethernet MIC (MIC-3D-20GE-SFP) does not have
hardware counters for VLAN frames. Therefore, the VLAN tagged frames field
displays 0 when the show interfaces command is executed on a 20-port
Gigabit Ethernet MIC. In other words, the number of VLAN tagged frames
cannot be determined for the 20-port Gigabit Ethernet MIC.
extensive
OTN Transmitted
Overhead Bytes
extensive
1568
Field Description
Level of Output
Filter statistics
Receive and Transmit statistics reported by the PIC's MAC address filter
extensive
destination MAC address of the packet is not on the accept list. It is normal
for this value to increment. When it increments very quickly and no traffic is
entering the router from the far-end system, either there is a bad ARP entry
on the far-end system, or multicast routing is not on and the far-end system
is sending many multicast packets to the local router (which the router is
rejecting).
source MAC address of the packet is not on the accept list. The value in this
field should increment only if source MAC address filtering has been enabled.
If filtering is enabled, if the value increments quickly, and if the system is not
receiving traffic that it should from the far-end system, it means that the
user-configured source MAC addresses for this interface are incorrect.
Output packet countNumber of packets that the filter has given to the MAC
hardware.
minimum Ethernet size (60 bytes) before giving the packet to the MAC
hardware. Usually, padding is done only on small ARP packets, but some very
small IP packets can also require padding. If this value increments rapidly,
either the system is trying to find an ARP entry for a far-end system that does
not exist or it is misconfigured.
the filter was given to transmit. These packets are usually aged packets or
are the result of a bandwidth problem on the FPC hardware. On a normal
system, the value of this field should not increment.
dedicated to destination and source MAC address filters. There can only be
up to 64 source entries. If source filtering is disabled, which is the default, the
values for these fields should be 0.
PMA PHY
CountNumber of times that the defect has gone from inactive to active.
extensive
Subfields are:
1569
Field Description
Level of Output
WIS section
extensive
CountNumber of times that the defect has gone from inactive to active.
Subfields are:
WIS line
LOLLoss of light
LOFLoss of frame
(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information:
CountNumber of times that the defect has gone from inactive to active.
extensive
Subfields are:
1570
Field Description
Level of Output
WIS path
(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information:
extensive
CountNumber of times that the defect has gone from inactive to active.
Subfields are:
UNEQ-PPath unequipped
1571
Field Description
Level of Output
Autonegotiation
information
extensive
Negotiation status:
detected on receive).
Received path trace,
Transmitted path trace
extensive
Packet Forwarding
Engine configuration
extensive
1572
Field Description
Level of Output
CoS information
extensive
This value is nonzero only if the buffer size is configured in terms of time.
Logical Interface
Logical interface
All levels
Index
Index number of the logical interface, which reflects its initialization sequence.
SNMP ifIndex
Generation
detail extensive
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
All levels
1573
Field Description
Level of Output
VLAN-Tag
Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN
tag or for both the outer and inner (In) VLAN tags.
pushAn outer VLAN tag is pushed in front of the existing VLAN tag.
swapThe outer VLAN tag of the incoming frame is overwritten with the
none
pushAn outer VLAN tag is pushed in front of the existing VLAN tag.
swap-swapBoth the inner and the outer VLAN tags of the incoming frame
pop-swapThe outer VLAN tag of the incoming frame is removed, and the
inner VLAN tag of the incoming frame is replaced by the user-specified VLAN
tag value. The inner tag becomes the outer tag in the final frame.
pop-popBoth the outer and inner VLAN tags of the incoming frame are
removed.
Demux
Encapsulation
All levels
Name of the dynamic profile that defines the agent circuit identifier (ACI)
interface set. If configured, the ACI interface set enables the underlying Ethernet
interface to create dynamic VLAN subscriber interfaces based on ACI
information.
Protocol
Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description.
MTU
Neighbor Discovery
Protocol (NDP)Queue
Statistics
All levels
Curr new hold cntCurrent number of unresolved nexthops in the NDP queue.
none
Dynamic Profile
Name of the dynamic profile that was used to create this interface configured
with a Point-to-Point Protocol over Ethernet (PPPoE) family.
Name of the service name table for the interface configured with a PPPoE family.
1574
Field Description
Level of Output
Max Sessions
Duplicate Protection
Direct Connect
State of the configuration to ignore DSL Forum VSAs: On or Off. When configured,
the router ignores any of these VSAs received from a directly connected CPE
device on the interface.
AC Name
Maximum labels
Maximum number of MPLS labels configured for the MPLS protocol family on
the logical interface.
Traffic statistics
Number and rate of bytes and packets received and transmitted on the specified
interface set.
detail extensive
interface set. The value in this field also includes the Layer 2 overhead bytes
for ingress or egress traffic on Ethernet interfaces if you enable accounting
of Layer 2 overhead at the PIC level or the logical interface level.
Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.
extensive
Local statistics
extensive
Transit statistics
extensive
NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the logical
interface egress statistics might not accurately reflect the traffic on the wire
when output shaping is applied. Traffic management output shaping might
drop packets after they are tallied by the Output bytes and Output packets
interface counters. However, correct values display for both of these egress
statistics when per-unit scheduling is enabled for the Gigabit Ethernet IQ2
physical interface, or when a single logical interface is actively using a shared
scheduler.
Generation
detail extensive
Route Table
Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
Flags
Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description.
detail extensive
1575
Field Description
Level of Output
Donor interface
Preferred source
address
Input Filters
Names of any input filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parentheses next to all interfaces.
detail extensive
Output Filters
Names of any output filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parentheses next to all interfaces.
detail extensive
Mac-Validate Failures
Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.
Addresses, Flags
Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
protocol-family
Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.
brief
Flags
Information about the address flag. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
Destination
Local
Broadcast
Generation
detail extensive
Table 99: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type
Interface Type
Sample Command
Comments
Inbound physical
interface
show interfaces
ge-0/3/0 extensive
Traffic statistics:
1576
Table 99: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type (continued)
Interface Type
Sample Command
Inbound logical
interface
show interfaces
ge-0/3/0.50 extensive
Traffic statistics:
Comments
show interfaces
ge-0/0/0 extensive
Traffic statistics:
Input bytes: 490 bytes per packet, representing
the Layer 3 packet + 12 bytes
MAC statistics:
show interfaces
ge-0/0/0.50 extensive
Traffic statistics:
Input bytes: 478 bytes per packet, representing
the Layer 3 packet
Sample Output
show interfaces (Gigabit Ethernet)
user@host> show interfaces ge-3/0/2
Physical interface: ge-3/0/2, Enabled, Physical link is Up
Interface index: 167, SNMP ifIndex: 35
Link-level type: 52, MTU: 1522, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled
Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
CoS queues
: 4 supported, 4 maximum usable queues
Current address: 00:05:85:4a:e9:7c, Hardware address: 00:05:85:4a:e9:7c
Last flapped
: 2006-08-10 17:25:10 PDT (00:01:08 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Ingress rate at Packet Forwarding Engine
: 0 bps (0 pps)
Ingress drop rate at Packet Forwarding Engine : 0 bps (0 pps)
Active alarms : None
Active defects : None
Logical interface ge-3/0/2.0 (Index 72) (SNMP ifIndex 69)
Flags: SNMP-Traps 0x4000
VLAN-Tag [ 0x8100.512 0x8100.513 ] In(pop-swap 0x8100.530) Out(swap-push
0x8100.512 0x8100.513)
Encapsulation: VLAN-CCC
Egress account overhead: 100
Ingress account overhead: 90
Input packets : 0
Output packets: 0
Protocol ccc, MTU: 1522
Flags: Is-Primary
1577
show interfaces extensive (Gigabit Ethernet on MX Series Routers showing interface transmit statistics
configuration)
user@host> show interfaces ge-2/1/2 extensive | match "output|interface"
Physical interface: ge-2/1/2, Enabled, Physical link is Up
Interface index: 151, SNMP ifIndex: 530, Generation: 154
Interface flags: SNMP-Traps Internal: 0x4000
Output bytes :
240614363944
772721536 bps
Output packets:
3538446506
1420444 pps
Direction : Output
Interface transmit statistics: Enabled
Logical interface ge-2/1/2.0 (Index 331) (SNMP ifIndex 955) (Generation 146)
Output bytes :
195560312716
522726272 bps
Output packets:
4251311146
1420451 pps
1578
Encapsulation: ENET2
1 expedited-fo
2 assured-forw
3 network-cont
Transmitted packets
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
1579
3 network-cont
1580
CoS queues
: 8 supported, 4 maximum usable queues
Schedulers
: 256
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:14:f6:30:5e:74, Hardware address: 00:14:f6:30:5e:74
Last flapped
: 2007-11-07 21:31:41 PST (02:03:33 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
38910844056
7952 bps
Output bytes :
7174605
8464 bps
Input packets:
418398473
11 pps
Output packets:
78903
12 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Ingress traffic statistics at Packet Forwarding Engine:
Input bytes :
38910799145
7952 bps
Input packets:
418397956
11 pps
Drop
bytes :
0
0 bps
Drop
packets:
0
0 pps
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0,
L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0,
FIFO errors: 0, Resource errors: 0
Output errors:
Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0,
FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Ingress queues: 4 supported, 4 in use
Queue counters:
Queued packets Transmitted packets
Dropped packets
0 best-effort
418390823
418390823
1 expedited-fo
2 assured-forw
3 network-cont
7133
7133
Transmitted packets
Dropped packets
1031
1031
1 expedited-fo
2 assured-forw
3 network-cont
77872
77872
0 best-effort
Receive
38910844056
418398473
408021893366
10
418398217
0
0
Transmit
7174605
78903
1026
12
77865
0
0
1581
1582
Input packets:
9429
Output packets:
9449
Transit statistics:
Input bytes :
0
7440 bps
Output bytes :
0
7888 bps
Input packets:
0
10 pps
Output packets:
0
11 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 169, Route table: 0
Flags: Is-Primary, Mac-Validate-Strict
Mac-Validate Failures: Packets: 0, Bytes: 0
Addresses, Flags: Is-Preferred Is-Primary
Input Filters: F1-ge-3/0/1.0-in, F3-ge-3/0/1.0-in
Output Filters: F2-ge-3/0/1.0-out (53)
Destination: 10.74.2/24, Local: 10.74.2.2, Broadcast: 10.74.2.255,
Generation: 196
Protocol multiservice, MTU: Unlimited, Generation: 170, Route table: 0
Flags: Is-Primary
Policer: Input: __default_arp_policer__
NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the logical interface
egress statistics displayed in the show interfaces command output might not accurately
reflect the traffic on the wire when output shaping is applied. Traffic management output
shaping might drop packets after they are tallied by the interface counters. For detailed
information, see the description of the logical interface Transit statistics fields in
Table 98 on page 1562.
show interfaces (Gigabit Ethernet Unnumbered Interface)
user@host> show interfaces ge-3/2/0
Physical interface: ge-3/2/0, Enabled, Physical link is Up
Interface index: 148, SNMP ifIndex: 50
Link-level type: Ethernet, MTU: 1514, Speed: 1000mbps, Loopback: Disabled,
Source filtering: Disabled, Flow control: Enabled, Auto-negotiation: Enabled,
Remote fault: Online
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 4 maximum usable queues
Current address: 00:14:f6:11:26:f8, Hardware address: 00:14:f6:11:26:f8
Last flapped
: 2006-10-27 04:42:23 PDT (08:01:52 ago)
Input rate
: 0 bps (0 pps)
Output rate
: 624 bps (1 pps)
Active alarms : None
Active defects : None
Logical interface ge-3/2/0.0 (Index 67) (SNMP ifIndex 85)
Flags: SNMP-Traps Encapsulation: ENET2
Input packets : 0
Output packets: 6
Protocol inet, MTU: 1500
Flags: Unnumbered
Donor interface: lo0.0 (Index 64)
Preferred source address: 22.22.22.22
1583
1584
Release Information
Description
Options
interface.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information about network interfaces.
snmp-index snmp-index(Optional) Display information for the specified SNMP index
of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
List of Sample Output
Output Fields
view
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, IQ2) on page 1600
show interfaces extensive (10-Gigabit Ethernet, WAN PHY Mode) on page 1603
show interfaces extensive (10-Gigabit Ethernet, DWDM OTN PIC) on page 1605
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional
Mode) on page 1607
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode,
Transmit-Only) on page 1607
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode,
Receive-Only) on page 1608
See Table 100 on page 1586 for the output fields for the show interfaces (10Gigabit
Ethernet) command.
1585
Field Description
Level of Output
Physical interface
All levels
Enabled
State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
All levels
Interface index
Index number of the physical interface, which reflects its initialization sequence.
SNMP ifIndex
Generation
detail extensive
Link-level type
All levels
MTU
All levels
Speed
All levels
Loopback
All levels
Source filtering
All levels
LAN-PHY mode
All levels
WAN-PHY mode
All levels
Unidirectional
All levels
Flow control
All levels
Auto-negotiation
All levels
Remote-fault
All levels
Physical Interface
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
Interface flags
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
All levels
1586
Field Description
Level of Output
Link flags
Information about the link. Possible values are described in the Links Flags
section under Common Output Fields Description.
All levels
Wavelength
All levels
Frequency
All levels
CoS queues
Schedulers
extensive
Hold-times
detail extensive
Current address
Hardware address
Last flapped
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hour:minute:second:timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input Rate
Input rate in bits per second (bps) and packets per second (pps). The value in
this field also includes the Layer 2 overhead bytes for ingress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or the
logical interface level.
None specified
Output Rate
Output rate in bps and pps. The value in this field also includes the Layer 2
overhead bytes for egress traffic on Ethernet interfaces if you enable accounting
of Layer 2 overhead at the PIC level or the logical interface level.
None specified
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
Egress account
overhead
Layer 2 overhead in bytes that is accounted in the interface statistics for egress
traffic.
detail extensive
Ingress account
overhead
Layer 2 overhead in bytes that is accounted in the interface statistics for ingress
traffic.
detail extensive
detail
extensive
1587
Field Description
Level of Output
Traffic statistics
Number and rate of bytes and packets received and transmitted on the physical
interface.
detail extensive
Input bytesNumber of bytes received on the interface. The value in this field
also includes the Layer 2 overhead bytes for ingress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or
the logical interface level.
this field also includes the Layer 2 overhead bytes for egress traffic on Ethernet
interfaces if you enable accounting of Layer 2 overhead at the PIC level or
the logical interface level.
Gigabit Ethernet and 10-Gigabit Ethernet IQ PICs count the overhead and CRC
bytes.
For Gigabit Ethernet IQ PICs, the input byte counts vary by interface type. For
more information, see Table 100 on page 1586.
Input errors
Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
(FCS).
RuntsNumber of frames received that are smaller than the runt threshold.
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
Layer 3 (usually IPv4) sanity checks of the header. For example, a frame with
less than 20 bytes of available IP header is discarded. L3 incomplete errors
can be ignored by configuring the ignore-l3-incompletes statement.
L2 channel errorsNumber of times the software did not find a valid logical
FIFO errorsNumber of FIFO errors in the receive direction that are reported
by the ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
1588
Field Description
Level of Output
Output errors
Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
Carrier transitionsNumber of times the interface has gone from down to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly
(perhaps once every 10 seconds), the cable, the far-end system, or the PIC
or PIM is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
only full-duplex operation, so for Gigabit Ethernet PICs, this number should
always remain 0. If it is nonzero, there is a software bug.
so long that the system automatically purged them. The value in this field
should never increment. If it does, it is most likely a software bug or possibly
malfunctioning hardware.
ASIC on the PIC. If this value is ever nonzero, the PIC is probably
malfunctioning.
Egress queues
MTU errorsNumber of packets whose size exceeded the MTU of the interface.
detail extensive
NOTE: In DPCs that are not of the enhanced type, such as DPC 40x 1GE R, DPCE
20x 1GE + 2x 10GE R, or DPCE 40x 1GE R, you might notice a discrepancy in the
output of the show interfaces command because incoming packets might be
counted in the Egress queues section of the output. This problem occurs on
non-enhanced DPCs because the egress queue statistics are polled from IMQ
(Inbound Message Queuing) block of the I-chip. The IMQ block does not
differentiate between ingress and egress WAN traffic; as a result, the combined
statistics are displayed in the egress queue counters on the Routing Engine. In
a simple VPLS scenorio, if there is no MAC entry in DMAC table (by sending
unidirectional traffic), traffic is flooded and the input traffic is accounted in IMQ.
For bidirectional traffic (MAC entry in DMAC table), if the outgoing interface is
on the same I-chip then both ingress and egress statistics are counted in a
combined way. If the outgoing interface is on a different I-chip or FPC, then only
egress statistics are accounted in IMQ. This behavior is expected with
non-enhanced DPCs
Queue counters
(Egress)
CoS queue number and its associated user-configured forwarding class name.
detail extensive
1589
Field Description
Level of Output
Ingress queues
extensive
Queue counters
(Ingress)
CoS queue number and its associated user-configured forwarding class name.
Displayed on IQ2 interfaces.
extensive
Ethernet-specific defects that can prevent the interface from passing packets.
When a defect persists for a certain amount of time, it is promoted to an alarm.
Based on the routing device configuration, an alarm can ring the red or yellow
alarm bell on the routing device, or turn on the red or yellow alarm LED on the
craft interface. These fields can contain the value None or Link.
LinkInterface has lost its link state, which usually means that the cable is
unplugged, the far-end system has been turned off, or the PIC is
malfunctioning.
OTN alarms
detail extensive
OTN defects
detail extensive
detail extensive
OTN Rate
OTN mode.
detail extensive
Status of the line loopback, if configured for the DWDM OTN PIC. Its value can
be: enabled or disabled.
detail extensive
The forward error correction (FEC) counters for the DWDM OTN PIC.
detail extensive
Corrected Error RatioThe corrected error ratio in the last 25 seconds. For
1590
Field Description
Level of Output
detail extensive
OTN OC
OTN OTU
detail extensive
detail extensive
Received DAPI
Destination Access Port Interface (DAPI) from which the packets were received.
detail extensive
Received SAPI
Source Access Port Interface (SAPI) from which the packets were received.
detail extensive
Transmitted DAPI
Destination Access Port Interface (DAPI) to which the packets were transmitted.
detail extensive
Transmitted SAPI
Source Access Port Interface (SAPI) to which the packets were transmitted.
detail extensive
PCS statistics
detail extensive
Bit errorsThe number of seconds during which at least one bit error rate
1591
Field Description
Level of Output
MAC statistics
Receive and Transmit statistics reported by the PIC's MAC subsystem, including
extensive
the following:
Total octets and total packetsTotal number of octets and packets. For
Gigabit Ethernet IQ PICs, the received octets count varies by interface type.
For more information, see Table 101 on page 1600
(excluding framing bits, but including FCS octets) of between 64 and 1518
octets, inclusive, and had either a bad FCS with an integral number of octets
(FCS Error) or a bad FCS with a nonintegral number of octets (Alignment
Error).
FIFO errorNumber of FIFO errors that are reported by the ASIC on the PIC.
code.
Jabber framesNumber of frames that were longer than 1518 octets (excluding
framing bits, but including FCS octets), and had either an FCS error or an
alignment error. This definition of jabber is different from the definition in
IEEE-802.3 section 8.2.1.5 (10BASE5) and section 10.3.1.4 (10BASE2). These
documents define jabber as the condition in which any packet exceeds 20
ms. The allowed range to detect jabber is from 20 ms to 150 ms.
length (excluding framing bits, but including FCS octets), and had either an
FCS error or an alignment error. Fragment frames normally increment because
both runts (which are normal occurrences caused by collisions) and noise
hits are counted.
VLAN tagged framesNumber of frames that are VLAN tagged. The system
uses the TPID of 0x8100 in the frame to determine whether a frame is tagged
or not.
extensive
OTN Transmitted
Overhead Bytes
extensive
1592
Field Description
Level of Output
Filter statistics
Receive and Transmit statistics reported by the PIC's MAC address filter
extensive
destination MAC address of the packet is not on the accept list. It is normal
for this value to increment. When it increments very quickly and no traffic is
entering the routing device from the far-end system, either there is a bad ARP
entry on the far-end system, or multicast routing is not on and the far-end
system is sending many multicast packets to the local routing device (which
the routing device is rejecting).
source MAC address of the packet is not on the accept list. The value in this
field should increment only if source MAC address filtering has been enabled.
If filtering is enabled, if the value increments quickly, and if the system is not
receiving traffic that it should from the far-end system, it means that the
user-configured source MAC addresses for this interface are incorrect.
Output packet countNumber of packets that the filter has given to the MAC
hardware.
minimum Ethernet size (60 bytes) before giving the packet to the MAC
hardware. Usually, padding is done only on small ARP packets, but some very
small IP packets can also require padding. If this value increments rapidly,
either the system is trying to find an ARP entry for a far-end system that does
not exist or it is misconfigured.
the filter was given to transmit. These packets are usually aged packets or
are the result of a bandwidth problem on the FPC hardware. On a normal
system, the value of this field should not increment.
dedicated to destination and source MAC address filters. There can only be
up to 64 source entries. If source filtering is disabled, which is the default, the
values for these fields should be 0.
PMA PHY
CountNumber of times that the defect has gone from inactive to active.
extensive
Subfields are:
1593
Field Description
Level of Output
WIS section
extensive
CountNumber of times that the defect has gone from inactive to active.
Subfields are:
WIS line
LOLLoss of light
LOFLoss of frame
(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information.
CountNumber of times that the defect has gone from inactive to active.
extensive
Subfields are:
1594
Field Description
Level of Output
WIS path
(10-Gigabit Ethernet interfaces, WAN PHY mode) Active alarms and defects,
plus counts of specific SONET errors with detailed information.
extensive
CountNumber of times that the defect has gone from inactive to active.
Subfields are:
UNEQ-PPath unequipped
1595
Field Description
Level of Output
Autonegotiation
information
extensive
Negotiation status:
Link partner:
detected on receive).
Received path
trace, Transmitted
path trace
extensive
Packet Forwarding
Engine
configuration
extensive
1596
Field Description
Level of Output
CoS information
extensive
This value is nonzero only if the buffer size is configured in terms of time.
Logical Interface
Logical interface
All levels
Index
Index number of the logical interface, which reflects its initialization sequence.
SNMP ifIndex
Generation
detail extensive
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
All levels
1597
Field Description
Level of Output
VLAN-Tag
Rewrite profile applied to incoming or outgoing frames on the outer (Out) VLAN
tag or for both the outer and inner (In) VLAN tags.
pushAn outer VLAN tag is pushed in front of the existing VLAN tag.
swapThe outer VLAN tag of the incoming frame is overwritten with the user
none
pushAn outer VLAN tag is pushed in front of the existing VLAN tag.
swap-swapBoth the inner and the outer VLAN tags of the incoming frame
pop-swapThe outer VLAN tag of the incoming frame is removed, and the
inner VLAN tag of the incoming frame is replaced by the user-specified VLAN
tag value. The inner tag becomes the outer tag in the final frame.
pop-popBoth the outer and inner VLAN tags of the incoming frame are
removed.
Demux:
Encapsulation
All levels
Protocol
Protocol family. Possible values are described in the Protocol Field section
under Common Output Fields Description.
MTU
Maximum labels
Maximum number of MPLS labels configured for the MPLS protocol family on
the logical interface.
Traffic statistics
Number and rate of bytes and packets received and transmitted on the specified
interface set.
detail extensive
interface set. The value in this field also includes the Layer 2 overhead bytes
for ingress or egress traffic on Ethernet interfaces if you enable accounting
of Layer 2 overhead at the PIC level or the logical interface level.
Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.
extensive
Local statistics
Number and rate of bytes and packets destined to the routing device.
extensive
1598
Field Description
Level of Output
Transit statistics
extensive
NOTE: For Gigabit Ethernet intelligent queuing 2 (IQ2) interfaces, the logical
interface egress statistics might not accurately reflect the traffic on the wire
when output shaping is applied. Traffic management output shaping might
drop packets after they are tallied by the Output bytes and Output packets
interface counters. However, correct values display for both of these egress
statistics when per-unit scheduling is enabled for the Gigabit Ethernet IQ2
physical interface, or when a single logical interface is actively using a shared
scheduler.
Generation
detail extensive
Route Table
Route table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
Flags
Information about protocol family flags. Possible values are described in the
Family Flags section under Common Output Fields Description.
detail extensive
Donor interface
Preferred source
address
Input Filters
Names of any input filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parenthesis next to all interfaces.
detail extensive
Output Filters
Names of any output filters applied to this interface. If you specify a precedence
value for any filter in a dynamic profile, filter precedence values appear in
parenthesis next to all interfaces.
detail extensive
Mac-Validate
Failures
Number of MAC address validation failures for packets and bytes. This field is
displayed when MAC address validation is enabled for the logical interface.
Addresses, Flags
Information about the address flags. Possible values are described in the
Addresses Flags section under Common Output Fields Description.
protocol-family
Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.
brief
Flags
Information about address flag (possible values are described in the Addresses
Flags section under Common Output Fields Description.
Destination
Local
Broadcast
1599
Field Description
Level of Output
Generation
detail extensive
For Gigabit Ethernet IQ PICs, traffic and MAC statistics output varies. Table 101 on page 1600
describes the traffic and MAC statistics for two sample interfaces, each of which is sending
traffic in packets of 500 bytes (including 478 bytes for the Layer 3 packet, 18 bytes for
the Layer 2 VLAN traffic header, and 4 bytes for cyclic redundancy check [CRC]
information). In Table 101 on page 1600, the ge-0/3/0 interface is the inbound physical
interface, and the ge-0/0/0 interface is the outbound physical interface. On both
interfaces, traffic is carried on logical unit .50 (VLAN 50).
Table 101: Gigabit Ethernet IQ PIC Traffic and MAC Statistics by Interface Type
Interface Type
Sample Command
Comments
Inbound physical
interface
show interfaces
ge-0/3/0 extensive
Traffic statistics:
show interfaces
ge-0/3/0.50 extensive
Traffic statistics:
Input bytes: 478 bytes per packet, representing
the Layer 3 packet
Outbound physical
interface
show interfaces
ge-0/0/0 extensive
Traffic statistics:
Input bytes: 490 bytes per packet, representing
the Layer 3 packet + 12 bytes
MAC statistics:
Received octets: 478 bytes per packet,
representing the Layer 3 packet
Outbound logical
interface
show interfaces
ge-0/0/0.50 extensive
Traffic statistics:
Input bytes: 478 bytes per packet, representing
the Layer 3 packet
Sample Output
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, IQ2)
user@host> show interfaces xe-5/0/0 extensive
Physical interface: xe-5/0/0, Enabled, Physical link is Up
Interface index: 177, SNMP ifIndex: 99, Generation: 178
Link-level type: Ethernet, MTU: 1518, LAN-PHY mode, Speed: 10Gbps, Loopback:
1600
81049992
81049992
1 expedited-fo
2 assured-forw
3 network-cont
Transmitted packets
Dropped packets
0 best-effort
1 expedited-fo
2 assured-forw
3 network-cont
Seconds
0
0
1601
MAC statistics:
Receive
Total octets
6970332384
Total packets
81050506
Unicast packets
81050000
Broadcast packets
506
Multicast packets
0
CRC/Align errors
0
FIFO errors
0
MAC control frames
0
MAC pause frames
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
81050506
Input packet rejects
506
Input DA rejects
0
Input SA rejects
0
Output packet count
Output packet pad count
Output packet error count
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 5
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
%
bps
%
0 best-effort
95
950000000
95
3 network-control
5
50000000
5
Direction : Input
CoS transmit queue
0 best-effort
3 network-control
%
95
5
Bandwidth
bps
950000000
50000000
%
95
5
Transmit
0
0
0
0
0
0
0
0
0
0
0
0
Buffer Priority
usec
0
low
0
low
Limit
Buffer Priority
usec
0
low
0
low
Limit
none
none
none
none
Logical interface xe-5/0/0.0 (Index 71) (SNMP ifIndex 95) (Generation 195)
Flags: SNMP-Traps 0x4000 VLAN-Tag [ 0x8100.100 ] Encapsulation: ENET2
Egress account overhead: 100
Ingress account overhead: 90
Traffic statistics:
Input bytes :
0
Output bytes :
46
Input packets:
0
Output packets:
1
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
46
Input packets:
0
Output packets:
1
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
1602
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 253, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.1.1/24, Local: 192.1.1.1, Broadcast: 192.1.1.255,
Generation: 265
Protocol multiservice, MTU: Unlimited, Generation: 254, Route table: 0
Flags: None
Policer: Input: __default_arp_policer__
1603
CRC/Align errors
0
0
FIFO errors
0
0
MAC control frames
0
0
MAC pause frames
0
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
0
Output packet pad count
0
Output packet error count
0
CAM destination filters: 0, CAM source filters: 0
PMA PHY:
Seconds
Count State
PLL lock
0
0 OK
PHY light
63159
1 Light Missing
WIS section:
BIP-B1
0
0
SEF
434430
434438 Defect Active
LOS
434430
1 Defect Active
LOF
434430
1 Defect Active
ES-S
434430
SES-S
434430
SEFS-S
434430
WIS line:
BIP-B2
0
0
REI-L
0
0
RDI-L
0
0 OK
AIS-L
434430
1 Defect Active
BERR-SF
0
0 OK
BERR-SD
0
0 OK
ES-L
434430
SES-L
434430
UAS-L
434420
ES-LFE
0
SES-LFE
0
UAS-LFE
0
WIS path:
BIP-B3
0
0
REI-P
0
0
LOP-P
0
0 OK
AIS-P
434430
1 Defect Active
RDI-P
0
0 OK
UNEQ-P
0
0 OK
PLM-P
0
0 OK
ES-P
434430
SES-P
434430
UAS-P
434420
ES-PFE
0
SES-PFE
0
UAS-PFE
0
Received path trace:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Transmitted path trace: orissa so-1/0/0
6f 72 69 73 73 61 20 73 6f 2d 31 2f 30 2f 30 00
orissa so-1/0/0.
Packet Forwarding Engine configuration:
1604
Destination slot: 1
CoS information:
CoS transmit queue
0 best-effort
3 network-control
%
95
5
Bandwidth
bps
950000000
50000000
%
95
5
Buffer
bytes
0
0
Priority
low
low
Limit
none
none
1 expedited-fo
2 assured-forw
3 network-cont
Queue number:
0
1
2
3
Active alarms : LINK
Active defects : LINK
MAC statistics:
Total octets
Total packets
Receive
0
0
Transmit
0
0
1605
Unicast packets
0
0
Broadcast packets
0
0
Multicast packets
0
0
CRC/Align errors
0
0
FIFO errors
0
0
MAC control frames
0
0
MAC pause frames
0
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
Total octets
0
0
Total packets
0
0
Unicast packets
0
0
Broadcast packets
0
0
Multicast packets
0
0
CRC/Align errors
0
0
FIFO errors
0
0
MAC control frames
0
0
MAC pause frames
0
0
Oversized frames
0
Jabber frames
0
Fragment frames
0
VLAN tagged frames
0
Code violations
0
OTN alarms
:
None
OTN defects
:
None
OTN FEC Mode
: GFEC
OTN Rate
: Fixed Stuff Bytes 11.0957Gbps
OTN Line Loopback : Enabled
OTN FEC statistics :
Corrected Errors
0
Corrected Error Ratio (
0 sec average)
0e-0
OTN FEC alarms:
Seconds
Count State
FEC Degrade
0
0 OK
FEC Excessive
0
0 OK
OTN OC:
Seconds
Count State
LOS
2
1 OK
LOF
67164
2 Defect Active
LOM
67164
71 Defect Active
Wavelength Lock
0
0 OK
OTN OTU:
AIS
0
0 OK
BDI
65919
4814 Defect Active
IAE
67158
1 Defect Active
TTIM
7
1 OK
SF
67164
2 Defect Active
SD
67164
3 Defect Active
TCA-ES
0
0 OK
TCA-SES
0
0 OK
TCA-UAS
80
40 OK
TCA-BBE
0
0 OK
BIP
0
0 OK
BBE
0
0 OK
ES
0
0 OK
SES
0
0 OK
UAS
587
0 OK
Received DAPI:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
Received SAPI:
1606
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
Transmitted DAPI:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
Transmitted SAPI:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................
OTN Received Overhead Bytes:
APS/PCC0: 0x02, APS/PCC1: 0x42, APS/PCC2: 0xa2, APS/PCC3: 0x48
Payload Type: 0x03
OTN Transmitted Overhead Bytes:
APS/PCC0: 0x00, APS/PCC1: 0x00, APS/PCC2: 0x00, APS/PCC3: 0x00
Payload Type: 0x03
Filter statistics:
Input packet count
0
Input packet rejects
0
Input DA rejects
0
Input SA rejects
0
Output packet count
0
Output packet pad count
0
Output packet error count
0
CAM destination filters: 0, CAM source filters: 0
Packet Forwarding Engine configuration:
Destination slot: 7
CoS information:
Direction : Output
CoS transmit queue
Bandwidth
Buffer Priority
Limit
%
bps
%
usec
0 best-effort
95
9500000000
95
0
low
none
3 network-control
5
500000000
5
0
low
none
...
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode)
user@host> show interfaces xe-7/0/0 extensive
Physical interface: xe-7/0/0, Enabled, Physical link is Up
Interface index: 173, SNMP ifIndex: 212, Generation: 174
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps,
Unidirectional: Enabled,
Loopback: None, Source filtering: Disabled, Flow control: Enabled
Device flags
: Present Running
...
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode, Transmit-Only)
user@host> show interfaces xe-7/0/0tx extensive
Physical interface: xe-7/0/0-tx, Enabled, Physical link is Up
Interface index: 176, SNMP ifIndex: 137, Generation: 177
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps,
Unidirectional: Tx-Only
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:73:e4:83, Hardware address: 00:05:85:73:e4:83
Last flapped
: 2007-06-01 09:08:19 PDT (3d 02:31 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
0 bps
1607
Output bytes :
Input packets:
Output packets:
322891152287160
0
328809727380
9627472888 bps
0 pps
1225492 pps
...
Filter statistics:
Output packet count
Output packet pad count
Output packet error count
...
328810554250
0
0
Logical interface xe-7/0/0-tx.0 (Index 73) (SNMP ifIndex 138) (Generation 139)
Flags: SNMP-Traps Encapsulation: ENET2
Egress account overhead: 100
Ingress account overhead: 90
Traffic statistics:
Input bytes :
0
Output bytes :
322891152287160
Input packets:
0
Output packets:
328809727380
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
322891152287160
9627472888 bps
Input packets:
0
0 pps
Output packets:
328809727380
1225492 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 147, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 10.11.12/24, Local: 10.11.12.13, Broadcast: 10.11.12.255,
Generation: 141
Protocol multiservice, MTU: Unlimited, Generation: 148, Route table: 0
Flags: None
Policer: Input: __default_arp_policer__
show interfaces extensive (10-Gigabit Ethernet, LAN PHY Mode, Unidirectional Mode, Receive-Only)
user@host> show interfaces xe-7/0/0rx extensive
Physical interface: xe-7/0/0-rx, Enabled, Physical link is Up
Interface index: 174, SNMP ifIndex: 118, Generation: 175
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps,
Unidirectional: Rx-Only
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
CoS queues
: 8 supported, 8 maximum usable queues
1608
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:05:85:73:e4:83, Hardware address: 00:05:85:73:e4:83
Last flapped
: 2007-06-01 09:08:22 PDT (3d 02:31 ago)
Statistics last cleared: Never
Traffic statistics:
Input bytes :
322857456303482
9627496104 bps
Output bytes :
0
0 bps
Input packets:
328775413751
1225495 pps
Output packets:
0
0 pps
...
Filter statistics:
Input packet count
Input packet rejects
Input DA rejects
328775015056
1
0
...
Logical interface xe-7/0/0-rx.0 (Index 72) (SNMP ifIndex 120) (Generation 138)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
322857456303482
Output bytes :
0
Input packets:
328775413751
Output packets:
0
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Transit statistics:
Input bytes :
322857456303482
9627496104 bps
Output bytes :
0
0 bps
Input packets:
328775413751
1225495 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 145, Route table: 0
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.1.1/24, Local: 192.1.1.1, Broadcast: 192.1.1.255,
Generation: 139
Protocol multiservice, MTU: Unlimited, Generation: 146, Route table: 0
Flags: None
Policer: Input: __default_arp_policer__
1609
show interfaces (M Series, MX Series, T Series Routers, and PTX Series Management
and Internal Ethernet)
List of Syntax
Syntax (M Series, MX
Series, T Series, and
PTX Series Routers
Management Ethernet
Interface)
Syntax (M Series, MX
Series, T Series, and
PTX Series Routers
Internal Ethernet
Interface)
Release Information
Syntax (M Series, MX Series, T Series, and PTX Series Routers Management Ethernet
Interface) on page 1610
Syntax (M Series, MX Series, T Series, and PTX Series Routers Internal Ethernet
Interface) on page 1610
show interfaces em0 | fxp0
<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>
show interfaces bcm0 | em0 | em1| fxp1 | fxp2 | ixgbe0 | ixgbe1
<brief | detail | extensive | terse>
<descriptions>
<media>
<snmp-index snmp-index>
<statistics>
Description
(M Series, T Series, TX Matrix Plus, and PTX Series devices only) Display status information
about the management Ethernet and internal Ethernet interfaces.
Options
em0 | fxp0(M Series, MX Series, T Series, and PTX Series) Display standard information
Series) Display standard information about the internal Ethernet interfaces. See
Supported Routing Engines by Router for the internal Ethernet interface names for
each Routing Engine by hardware platform.
brief | detail | extensive | terse(Optional) Display the specified level of output.
descriptions(Optional) Display interface description strings.
media(Optional) Display media-specific information.
snmp-index snmp-index(Optional) Display information for the specified SNMP index
of the interface.
statistics(Optional) Display static interface statistics.
Required Privilege
Level
1610
view
Output Fields
Table 102: show interfaces Output Fields for M Series, MX Series, T Series, and PTX Series
Routers Management Ethernet Interface
Field Name
Field Description
Level of Output
Physical interface
All levels
Enabled
State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
All levels
Interface index
SNMP ifIndex
Generation
detail extensive
Type
Type of interface.
All levels
Link-level type
All levels
MTU
All levels
Physical Interface
1611
Table 102: show interfaces Output Fields for M Series, MX Series, T Series, and PTX Series
Routers Management Ethernet Interface (continued)
Field Name
Field Description
Level of Output
Clocking
All levels
Speed
All levels
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
Interface flags
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
All levels
Link type
Link flags
Information about the link. Possible values are described in the Link Flags
section under Common Output Fields Description.
detail extensive
Physical info
detail extensive
Hold-times
detail extensive
Current address
Hardware address
Alternate link
address
detail extensive
Last flapped
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hour:minute:second timezone (hour:minute:second
ago). For example, Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Input packets
None specified
Output packets
None specified
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
Traffic statistics
Number and rate of bytes and packets received and transmitted on the logical
and physical interface.
detail extensive
interface.
on the interface.
1612
Table 102: show interfaces Output Fields for M Series, MX Series, T Series, and PTX Series
Routers Management Ethernet Interface (continued)
Field Name
Field Description
Level of Output
Input errors
extensive
ASIC.
(FCS).
because they were not recognized or were not of interest. Usually, this field
reports protocols that Junos does not support.
Output errors
Carrier transitionsNumber of times the interface has gone from down to up.
extensive
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly,
possibly once every 10 seconds, the cable, the remote system, or the interface
is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet dropped by the ASIC RED mechanism.
Logical Interface
Logical interface
All levels
Index
SNMP ifIndex
Generation
detail extensive
Flags
Information about the logical interface; values are described in the Device
Flags section under Common Output Fields Description.
All levels
Encapsulation
inet
brief
Protocol
MTU
Generation
detail extensive
1613
Table 102: show interfaces Output Fields for M Series, MX Series, T Series, and PTX Series
Routers Management Ethernet Interface (continued)
Field Name
Field Description
Level of Output
Route table
Route table in which this address exists. For example, Route table:0 refers to
inet.0.
detail extensive
Flags
Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description.
Addresses, Flags
Information about address flags. Possible values are described in the Addresses
Flags section under Common Output Fields Description.
Destination
Local
Broadcast
Broadcast address.
Generation
detail extensive
Sample Output
show interfaces brief (Management Ethernet)
user@host> show interfaces fxp0 brief
Physical interface: fxp0, Enabled, Physical link is Up
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 100mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Logical interface fxp0.0
Flags: SNMP-Traps Encapsulation: ENET2
inet 192.168.70.143/21
1614
1615
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:a0:a5:56:01:89, Hardware address: 00:a0:a5:56:01:89
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
6484031
Output bytes :
167503
Input packets:
81008
Output packets:
1110
Logical interface fxp0.0 (Index 2) (SNMP ifIndex 13) (Generation 1)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 6, Route table: 0
Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.64/21, Local: 192.168.70.143,
Broadcast: 192.168.71.255, Generation: 1
1616
1617
1618
Input bytes :
119748
Output bytes :
1335719
Input packets:
1843
Output packets:
5372
Local statistics:
Input bytes :
119748
Output bytes :
1335719
Input packets:
1843
Output packets:
5372
Protocol inet, MTU: 1500, Generation: 1, Route table: 0
Flags: Is-Primary
Addresses, Flags: Is-Preferred Is-Primary
Destination: 192.168.178.0/25, Local: 192.168.178.11, Broadcast:
192.168.178.127, Generation: 1
show interfaces extensive (Management Ethernet [PTX Series Packet Transport Routers])
user@host> show interfaces extensive em0
Physical interface: em0, Enabled, Physical link is Up
Interface index: 8, SNMP ifIndex: 0, Generation: 3
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 00:80:f9:25:00:1b, Hardware address: 00:80:f9:25:00:1b
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
15236459
Output bytes :
4608
Input packets:
214482
Output packets:
72
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0,
Resource errors: 0
Logical interface em0.0 (Index 3) (SNMP ifIndex 0) (Generation 1)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
14376264
Output bytes :
3024
Input packets:
214452
Output packets:
72
Local statistics:
Input bytes :
14376264
Output bytes :
3024
Input packets:
214452
Output packets:
72
1619
show interfaces brief (Management Ethernet [PTX Series Packet Transport Routers])
user@host> show interfaces em0 brief
Physical interface: em0, Enabled, Physical link is Up
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: 1000mbps
Device flags
: Present Running
Interface flags: SNMP-Traps
Logical interface em0.0
Flags: SNMP-Traps Encapsulation: ENET2
inet 192.168.3.30/24
root@aboslutely> show interfaces em0 terse
Interface
Admin Link Proto
em0
up
up
em0.0
up
up
inet
Local
Remote
192.168.3.30/24
1620
Link type
: Full-Duplex
Current address: 02:00:00:00:00:04, Hardware address: 02:00:00:00:00:04
Last flapped
: Never
Input packets : 30655
Output packets: 33323
Logical interface fxp1.0 (Index 3) (SNMP ifIndex 14)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 10/8, Local: 10.0.0.4, Broadcast: 10.255.255.255
Protocol inet6, MTU: 1500
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe00:4
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::10:0:0:4
Protocol tnp, MTU: 1500
Flags: Primary, Is-Primary
Addresses
Local: 4
1621
1622
0
0
0
0
1623
Traffic statistics:
Input bytes :
2349897
Output bytes :
15888605
Input packets:
30896
Output packets:
33607
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0,
Policed discards: 0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0,
Resource errors: 0
Logical interface fxp1.0 (Index 3) (SNMP ifIndex 14) (Generation 2)
Flags: SNMP-Traps Encapsulation: ENET2
Protocol inet, MTU: 1500, Generation: 7, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: 10/8, Local: 10.0.0.4, Broadcast: 10.255.255.255,
Generation: 3
Protocol inet6, MTU: 1500, Generation: 8, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe00:4,
Broadcast: Unspecified, Generation: 5
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::10:0:0:4, Broadcast: Unspecified,
Generation: 7
Protocol tnp, MTU: 1500, Generation: 9, Route table: 1
Flags: Primary, Is-Primary
Addresses, Flags: None
Destination: Unspecified, Local: 4, Broadcast: Unspecified,
Generation: 8
1624
0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Logical interface ixgbe0.0 (Index 4) (SNMP ifIndex 117) (Generation 2)
Flags: SNMP-Traps Encapsulation: ENET2
Traffic statistics:
Input bytes :
233127252
Output bytes :
1269350897
Input packets:
2398594
Output packets:
4133510
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
233127252
Output bytes :
1269350897
Input packets:
2398594
Output packets:
4133510
Protocol inet, MTU: 1500, Generation: 2, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: 10/8, Local: 10.34.0.4, Broadcast: 10.255.255.255, Generation:
2
Addresses, Flags: Primary Is-Default Is-Preferred Is-Primary
Destination: 128/2, Local: 162.0.0.4, Broadcast: 191.255.255.255,
Generation: 3
Protocol inet6, MTU: 1500, Generation: 3, Route table: 1
Flags: Is-Primary
Addresses, Flags: Is-Preferred
Destination: fe80::/64, Local: fe80::200:ff:fe22:4
Generation: 4
Addresses, Flags: Is-Default Is-Preferred Is-Primary
Destination: fec0::/64, Local: fec0::a:22:0:4
Protocol tnp, MTU: 1500, Generation: 5
Generation: 4, Route table: 1
Flags: Primary, Is-Primary
Addresses, Flags: None
Destination: Unspecified, Local: 0x22000004, Broadcast: Unspecified,
Generation: 6
1625
Release Information
Description
Options
of the interface.
statistics(Optional) Display PPPoE interface statistics.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Level of Output
Physical interface
All levels
Enabled
State of the interface. Possible values are described in the Enabled Field
section under Common Output Fields Description.
All levels
Interface index
SNMP ifIndex
Physical Interface
1626
Field Description
Level of Output
Generation
detail extensive
Type
All levels
Link-level type
All levels
MTU
All levels
Clocking
All levels
Speed
All levels
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
All levels
Interface flags
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
All levels
Link type
All levels
Link flags
Information about the interface. Possible values are described in the Link Flags
section under Common Output Fields Description.
All levels
Input rate
Input rate in bits per second (bps) and packets per second (pps).
None specified
Output rate
None specified
Physical Info
All levels
Hold-times
detail extensive
Current address
detail extensive
Hardware address
detail extensive
Alternate link
address
detail extensive
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
Traffic statistics
Number and rate of bytes and packets received and transmitted on the physical
interface.
detail extensive
1627
Field Description
Level of Output
IPv6 transit
statistics
Number of IPv6 transit bytes and packets received and transmitted on the
physical interface if IPv6 statistics tracking is enabled.
detail extensive
NOTE: These fields include dropped traffic and exception traffic, as those fields
are not separately defined.
Input errors
extensive
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
(FCS).
RuntsNumber of frames received that are smaller than the runt threshold.
GiantsNumber of frames received that are larger than the giant threshold.
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
Output errors
Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
extensive
Carrier transitions Number of times the interface has gone from down to up.
This number does not normally increment quickly, increasing only when the
cable is unplugged, the far-end system is powered down and then up, or
another problem occurs. If the number of carrier transitions increments quickly
(perhaps once every 10 seconds), then the cable, the far-end system, or the
PIM is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
MTU errorsNumber of packets whose size exceeded the MTU of the interface.
Logical Interface
Logical interface
All levels
Index
SNMP ifIndex
Generation
detail extensive
1628
Field Description
Level of Output
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
All levels
Encapsulation
All levels
PPP parameters
PPP status:
detail
PPPoE
PPPoE status:
All levels
Idle TimeoutLength of time (in seconds) that a connection can be idle before
disconnecting.
Link
All levels
Traffic statistics
Total number of bytes and packets received and transmitted on the logical
interface. These statistics are the sum of the local and transit statistics. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. This counter usually takes less than 1 second to
stabilize.
detail extensive
IPv6 transit
statistics
Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.
detail extensive
NOTE: The packet and byte counts in these fields include traffic that is dropped
and does not leave the router.
Local statistics
Statistics for traffic received from and transmitted to the Routing Engine. When
a burst of traffic is received, the value in the output packet rate field might briefly
exceed the peak cell rate. This counter usually takes less than 1 second to
stabilize.
detail extensive
1629
Field Description
Level of Output
Transit statistics
Statistics for traffic transiting the router. When a burst of traffic is received, the
value in the output packet rate field might briefly exceed the peak cell rate. This
counter usually takes less than 1 second to stabilize.
detail extensive
NOTE: The packet and byte counts in these fields include traffic that is dropped
and does not leave the router.
Keepalive settings
Keepalive statistics
detail extensive
detail extensive
(last seen 00:00:00 ago)Time the last keepalive packet was received,
in the format hh:mm:ss.
OutputNumber of keepalive packets sent by PPP and how long ago the last
(last seen 00:00:00 ago)Time the last keepalive packet was sent, in the
format hh:mm:ss.
(MX Series routers with MPCs/MICs) When an MX Series router with MPCs/MICs
is using PPP fast keepalive for a PPP link, the display does not include the
number of keepalive packets received or sent, or the amount of time since the
router received or sent the last keepalive packet.
Input packets
None specified
Output packets
None specified
LCP state
1630
Field Description
Level of Output
NCP state
CHAP state
CHAP has not yet moved into the Success state. (Most likely with RADIUS
authentication.)
Protocol
protocol-family
Protocol family configured on the logical interface. If the protocol is inet, the IP
address of the interface is also displayed.
brief
MTU
Generation
detail extensive
Route table
Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
Flags
Information about the protocol family flags. Possible values are described in
the Family Flags section under Common Output Fields Description.
Addresses, Flags
Information about the addresses configured for the protocol family. Possible
values are described in the Addresses Flags section under Common Output
Fields Description.
Destination
Local
Broadcast
Broadcast address.
1631
Sample Output
show interfaces (PPPoE)
user@host> show interfaces pp0
Physical interface: pp0, Enabled, Physical link is Up
Interface index: 128, SNMP ifIndex: 24
Type: PPPoE, Link-level type: PPPoE, MTU: 1532
Device flags
: Present Running
Interface flags: Point-To-Point SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Input rate
: 0 bps (0 pps)
Output rate
: 0 bps (0 pps)
Logical interface pp0.0 (Index 72) (SNMP ifIndex 72)
Flags: Hardware-Down Point-To-Point SNMP-Traps 0x4000 Encapsulation: PPPoE
PPPoE:
State: SessionDown, Session ID: None,
Service name: None, Configured AC name: sapphire,
Auto-reconnect timeout: 100 seconds, Idle timeout: Never,
Underlying interface: at-5/0/0.0 (Index 70)
Input packets : 0
Output packets: 0
LCP state: Not-configured
NCP state: inet: Not-configured, inet6: Not-configured, iso: Not-configured,
mpls: Not-configured
CHAP state: Closed
Protocol inet, MTU: 100
Flags: User-MTU, Negotiate-Address
mpls:
1632
1633
1634
1635
Release Information
Description
Display information about the specified gigabit or 10-Gigabit Ethernet interface set.
You can also use the show interfaces interface-set command to display information about
agent circuit identifier (ACI) interface sets.
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
view
Field Description
Level of Output
Interface set
All levels
Index number of the interface set. For ACI interface sets, the following fields
are displayed:
detail none
Physical Interface
ACI VLANACI interface set that the router uses to create dynamic VLAN
For ACI interface sets, string in DHCP or PPPoE control packets that uniquely
identifies the subscribers access node and and the DSL line on the access node.
detail none
Max Sessions
detail none
1636
Field Description
Level of Output
detail none
Traffic statistics
Number and rate of bytes and packets received and transmitted on the specified
interface set.
detail
Input bytes, Output bytesNumber of bytes and number of bytes per second
detail
Egress queues in
use
detail
Queue counters
Queued packets, Transmitted packets, and Dropped packets statistics for the
detail
List of all interface sets or, for ACI interface sets, list of all subscriber interfaces
belonging to the specified ACI interface set.
detail none
Sample Output
show interfaces interface-set terse
user@host> show interfaces interface-set terse
Interface set:
iflset-xe-11/3/0-0
ge-1/0/1-0
ge-1/0/1-2
1637
1638
Release Information
Description
Options
10-Gigabit Ethernet interface set. Wildcard values can be used in the interface set
name.
aggregate(Optional) Display the aggregated queuing statistics of all member logical
forwarding class.
ingress(Optional) On Gigabit Ethernet IQ2 PICs, display ingress queue statistics.
remaining-traffic(Optional) Display the queuing statistics of all member logical
interfaces for interface sets that do not have traffic-control profiles configured.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Level of Output
Interface set
All levels
All levels
Physical Interface
1639
Table 105: Ethernet show interfaces interface-set queue Output Fields (continued)
Field Name
Field Description
Level of Output
Forwarding classes
supported
All levels
Forwarding classes
in use
All levels
Egress queues
supported
All levels
Egress queues in
use
All levels
Ingress queues
supported
All levels
Ingress queues in
use
All levels
Queue
All levels
Forwarding classes
All levels
Queued
All levels
Transmitted
All levels
second.
Sample Output
show interfaces interface-set queue (Gigabit Ethernet)
user@host> show interfaces interface-set queue ge-2/2/0-0
Interface set: ge-2/2/0-0
Interface set index: 3
Forwarding classes: 8 supported, 4 in use
Egress queues: 4 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Packets
:
3998482
1640
1 pps
Bytes
:
271896884
Transmitted:
Packets
:
1077474
Bytes
:
73268340
Tail-dropped packets :
0
RED-dropped packets :
2921008
Low
:
2921008
Medium-low
:
0
Medium-high
:
0
High
:
0
RED-dropped bytes
:
198628544
Low
:
198628544
Medium-low
:
0
Medium-high
:
0
High
:
0
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets
:
0
Bytes
:
0
Transmitted:
...
688 bps
1
688
0
0
0
0
0
0
0
0
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
bps
bps
bps
0 pps
0 bps
pps
bps
pps
bps
pps
pps
bps
pps
bps
pps
bps
pps
pps
bps
pps
bps
pps
bps
pps
pps
bps
1641
Packets
:
0
Bytes
:
0
Transmitted:
Packets
:
0
Bytes
:
0
Tail-dropped packets :
0
RED-dropped packets :
0
RED-dropped bytes
:
0
Forwarding classes: 16 supported, 4 in use
Egress queues: 4 supported, 4 in use
Queue: 0, Forwarding classes: best-effort
Queued:
Packets
:
5417304
Bytes
:
368429508
Transmitted:
Packets
:
5014996
Bytes
:
341019728
Tail-dropped packets :
0
RED-dropped packets :
402189
Low
:
402189
Medium-low
:
0
Medium-high
:
0
High
:
0
RED-dropped bytes
:
27348852
Low
:
27348852
Medium-low
:
0
Medium-high
:
0
High
:
0
Queue: 1, Forwarding classes: expedited-forwarding
Queued:
Packets
:
0
Bytes
:
0
Transmitted:
Packets
:
0
Bytes
:
0
Tail-dropped packets :
0
RED-dropped packets :
0
Low
:
0
Medium-low
:
0
Medium-high
:
0
High
:
0
RED-dropped bytes
:
0
Low
:
0
Medium-low
:
0
Medium-high
:
0
High
:
0
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets
:
5770534
Bytes
:
396943252
Transmitted:
Packets
:
3945152
Bytes
:
268270336
Tail-dropped packets :
0
RED-dropped packets :
1815141
Low
:
1815141
Medium-low
:
0
Medium-high
:
0
High
:
0
RED-dropped bytes
:
123429524
Low
:
123429524
1642
0 pps
0 bps
0
0
0
0
0
pps
bps
pps
pps
bps
13797 pps
7506096 bps
12769
6946560
0
1028
1028
0
0
0
559536
559536
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
bps
bps
bps
0 pps
0 bps
0
0
0
0
0
0
0
0
0
0
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
bps
bps
bps
3963 pps
2156144 bps
1457
792608
0
2506
2506
0
0
0
1363536
1363536
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
Medium-low
:
Medium-high
:
High
:
Queue: 3, Forwarding classes: network-control
Queued:
Packets
:
Bytes
:
Transmitted:
Packets
:
Bytes
:
Tail-dropped packets :
RED-dropped packets :
Low
:
Medium-low
:
Medium-high
:
High
:
RED-dropped bytes
:
Low
:
Medium-low
:
Medium-high
:
High
:
0
0
0
0 bps
0 bps
0 bps
0
0
0 pps
0 bps
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
bps
bps
bps
13822 pps
7519712 bps
12729
6924848
0
1093
1093
0
0
0
594864
594864
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
bps
bps
bps
0 pps
0 bps
0
0
0
0
0
0
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
1643
Low
:
0
Medium-low
:
0
Medium-high
:
0
High
:
0
Queue: 2, Forwarding classes: assured-forwarding
Queued:
Packets
:
5350989
Bytes
:
368412924
Transmitted:
Packets
:
3790469
Bytes
:
257751892
Tail-dropped packets :
0
RED-dropped packets :
1550282
Low
:
1550282
Medium-low
:
0
Medium-high
:
0
High
:
0
RED-dropped bytes
:
105419176
Low
:
105419176
Medium-low
:
0
Medium-high
:
0
High
:
0
Queue: 3, Forwarding classes: network-control
Queued:
Packets
:
0
Bytes
:
0
Transmitted:
Packets
:
0
Bytes
:
0
Tail-dropped packets :
0
RED-dropped packets :
0
Low
:
0
Medium-low
:
0
Medium-high
:
0
High
:
0
RED-dropped bytes
:
0
Low
:
0
Medium-low
:
0
Medium-high
:
0
High
:
0
0
0
0
0
bps
bps
bps
bps
3904 pps
2124048 bps
1465
796960
0
2439
2439
0
0
0
1327088
1327088
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
bps
bps
bps
0 pps
0 bps
0
0
0
0
0
0
0
0
0
0
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
bps
bps
bps
1644
RED-dropped bytes
Low
Medium-low
Medium-high
High
:
:
:
:
:
6655225776
6655225776
0
0
0
742339808
742339808
0
0
0
bps
bps
bps
bps
bps
473711 pps
204642936 bps
13891
6000912
0
459820
198642024
pps
bps
pps
pps
bps
0 pps
0 bps
0
0
0
0
0
pps
bps
pps
pps
bps
473605 pps
204597576 bps
3959
1710504
0
469646
202887072
pps
bps
pps
pps
bps
0 pps
0 bps
0
0
0
0
0
pps
bps
pps
pps
bps
1645
1646
0 pps
0 bps
0
0
0
0
0
0
0
0
0
0
0
0
0
pps
bps
pps
pps
pps
pps
pps
pps
bps
bps
bps
bps
bps
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
view
Field Description
Physical interface
SNMP ifIndex
hh:mm-current
Time of day (in hours and minutes) at the beginning of the latest
counter interval. The value of the latest counter interval is always
less than 15 minutes.
hh:mm-hh:mm
Time of day (in hours and minutes) at the beginning and end of
each 15-minute interval.
alarm or event: n
Interval Total
Sum of all the alarm and defect counters for the last 24-hour period.
1647
Sample Output
show interfaces interval (Channelized OC12)
user@host> show interfaces interval t3-0/3/0:0
Physical interface: t3-0/3/0:0, SNMP ifIndex: 23
17:43-current:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
17:28-17:43:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
17:13-17:28:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
16:58-17:13:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
SEFS: 0, UAS: 0
16:43-16:58:
LCV: 0, PCV: 0, CCV: 0, LES: 0, PES: 0, PSES: 0, CES: 0, CSES: 0,
...
Interval Total:
LCV: 230, PCV: 1145859, CCV: 455470, LES: 0, PES: 230, PSES: 230,
CES: 230, CSES: 230, SEFS: 230, UAS: 238
1648
19:17-19:32:
ES-S: 0, SES-S: 0, SEFS-S: 0, ES-L: 0, SES-L: 0, UAS-L: 0, ES-P: 0,
SES-P: 0, UAS-P: 0
19:02-19:17:
.....
1649
Release Information
Description
Options
SNMP index.
statistics(Optional) Display static interface statistics.
Additional Information
Required Privilege
Level
List of Sample Output
Output Fields
Integrated routing and bridging (IRB) provides simultaneous support for Layer 2 bridging
and Layer 3 IP routing on the same interface. IRB enables you to route local packets to
another routed interface or to another bridging domain that has a Layer 3 protocol
configured.
view
Field Description
Level of Output
Physical interface
All levels
Enabled
State of the physical interface. Possible values are described in the Enabled
Field section under Common Output Fields Description.
All levels
Proto
terse
Physical Interface
1650
Field Description
Level of Output
Interface index
SNMP ifIndex
Type
Link-level type
none
MTU
none
Clocking
Speed
Device flags
Information about the physical device. Possible values are described in the
Device Flags section under Common Output Fields Description.
Information about the interface. Possible values are described in the Interface
Flags section under Common Output Fields Description.
detail extensive
Interface flags
Link type
none
none
none
Link flags
Information about the link. Possible values are described in the Links Flags
section under Common Output Fields Description.
Physical Info
All levels
Hold-times
detail extensive
Current address
Hardware address
Alternate link
address
detail extensive
Last flapped
Date, time, and how long ago the interface went from down to up. The format
is Last flapped: year-month-day hours:minutes:seconds timezone
(hours:minutes:seconds ago). For example, Last flapped: 2002-04-26 10:52:40
PDT (04:33:20 ago).
Statistics last
cleared
Time when the statistics for the interface were last set to zero.
detail extensive
1651
Field Description
Level of Output
Traffic statistics
Number and rate of bytes and packets received and transmitted on the physical
interface.
detail extensive
Input errors
Number of IPv6 transit bytes and packets received and transmitted on the
physical interface if IPv6 statistics tracking is enabled.
Input errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
detail extensive
detail extensive
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
(FCS).
RuntsNumber of frames received that are smaller than the runt threshold.
GiantsNumber of frames received that are larger than the giant threshold.
discarded because they were not recognized or not of interest. Usually, this
field reports protocols that the Junos OS does not handle.
Output errors
Output errors on the interface. The following paragraphs explain the counters
whose meaning might not be obvious:
detail extensive
the cable is unplugged, the far-end system is powered down and up, or
another problem occurs. If the number of carrier transitions increments
quickly (perhaps once every 10 seconds), the cable, the far-end system, or
the DPC is malfunctioning.
ASIC. If the interface is saturated, this number increments once for every
packet that is dropped by the ASIC's RED mechanism.
interface.
Logical Interface
1652
Field Description
Level of Output
Logical interface
All levels
Index
Index number of the logical interface (which reflects its initialization sequence).
detail extensive
none
SNMP ifIndex
detail extensive
none
Generation
detail extensive
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
detail extensive
Encapsulation
detail extensive
Bandwidth
detail extensive
Routing Instance
detail extensive
Bridging Domain
detail extensive
Traffic statistics
Number and rate of bytes and packets received and transmitted on the logical
interface.
detail extensive
Number of IPv6 transit bytes and packets received and transmitted on the
logical interface if IPv6 statistics tracking is enabled.
detail extensive
Local statistics
Statistics for traffic received from and transmitted to the Routing Engine.
detail extensive
Transit statistics
detail extensive
Protocol
Protocol family configured on the local interface. Possible values are described
in the Protocol Field section under Common Output Fields Description.
detail extensive
MTU
detail extensive
Maximum labels
Maximum number of MPLS labels configured for the MPLS protocol family on
the logical interface.
detail extensive
none
1653
Field Description
Level of Output
Generation
detail extensive
Route table
Routing table in which the logical interface address is located. For example, 0
refers to the routing table inet.0.
detail extensive
Addresses, Flags
Information about address flags. Possible values are described in the Addresses
Flags section under Common Output Fields Description.
detail extensive
Policer
detail extensive
Flags
Information about the logical interface. Possible values are described in the
Logical Interface Flags section under Common Output Fields Description.
detail extensive
Sample Output
show interfaces irb extensive
user@host> show interfaces irb extensive
Physical interface: irb, Enabled, Physical link is Up
Interface index: 129, SNMP ifIndex: 23, Generation: 130
Type: Ethernet, Link-level type: Ethernet, MTU: 1514, Clocking: Unspecified,
Speed: Unspecified
Device flags
: Present Running
Interface flags: SNMP-Traps
Link type
: Full-Duplex
Link flags
: None
Physical info : Unspecified
Hold-times
: Up 0 ms, Down 0 ms
Current address: 02:00:00:00:00:30, Hardware address: 02:00:00:00:00:30
Alternate link address: Unspecified
Last flapped
: Never
Statistics last cleared: Never
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Input errors:
Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Giants: 0, Policed discards:
0, Resource errors: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, MTU errors: 0, Resource errors:
0
Logical interface irb.0 (Index 68) (SNMP ifIndex 70) (Generation 143)
Flags: Hardware-Down SNMP-Traps 0x4000 Encapsulation: ENET2
Bandwidth: 1000mbps
Routing Instance: customer_0 Bridging Domain: bd0
1654
Traffic statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Local statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Transit statistics:
Input bytes :
0
0 bps
Output bytes :
0
0 bps
Input packets:
0
0 pps
Output packets:
0
0 pps
IPv6 transit statistics:
Input bytes :
0
Output bytes :
0
Input packets:
0
Output packets:
0
Protocol inet, MTU: 1500, Generation: 154, Route table: 0
Addresses, Flags: Dest-route-down Is-Preferred Is-Primary
Destination: 10.51.1/24, Local: 10.51.1.2, Broadcast: 10.51.1.255,
Generation: 155
Protocol multiservice, MTU: 1500, Generation: 155, Route table: 0
Flags: Is-Primary
Policer: Input: __default_arp_policer
1655
Release Information
Description
Options
interface.
aexDisplay MAC addresses that have been learned on a particular aggregated Ethernet
interface.
xe-fpc/pic/portDisplay MAC addresses that have been learned on all logical interfaces
interface.
et-fpc/pic/portDisplay MAC addresses that have been learned on all logical interfaces
interface.
mac-address mac-address(Optional) Display detailed MAC address statistics, including
Required Privilege
Level
List of Sample Output
1656
On IQ2 PIC interfaces, the default value for maximum retention of entries in the MAC
address table has changed, for cases in which the table is not full. The new holding time
is 12 hours. The previous retention time of 3 minutes is still in effect when the table is full.
view
Output Fields
Table 108 on page 1657 lists the output fields for the show interfaces mac-database
command. Output fields are listed in the approximate order in which they appear.
Field Description
Physical Interface
Physical interface
Enabled
State of the physical interface. Possible values are described in the Enabled Field section under
Common Output Fields Description.
Interface index
SNMP ifIndex
Description
Link-level type
MTU
Speed
Loopback
Source filtering
Flow control
(Aggregated Ethernet interfaces only) Number of child links that must be operational for the aggregated
interface to be operational.
Minimum bandwidth
needed
(Aggregated Ethernet interfaces only) Minimum amount of bandwidth of child links that must be
operational for the aggregated interface to be operational.
Device flags
Information about the physical device. Possible values are described in the Device Flags section
under Common Output Fields Description.
Currrent address
Hardware address
Last flapped
(Aggregated Ethernet interfaces only) Date, time, and how long ago the interface went from down
to up or from up to down. The format is Last flapped: year-month-day hours:minutes:seconds timezone
(wweeksddays hours:minutes ago). For example, Last flapped: 2013-12-18 04:33:22 PST (1w5d 22:23
ago).
Input Rate
(Aggregated Ethernet interfaces only) Input rate in bits per second (bps) and packets per second
(pps).
1657
Field Description
Output Rate
Interface flags
Information about the interface. Possible values are described in the Links Flags section under
Common Output Fields Description.
Link flags
Information about the link. Possible v4alues are described in the Device Flags section under Common
Output Fields Description.
Logical Interface
Logical interface
Index
SNMP ifIndex
Flags
Information about the logical interface (possible values are described in the Logical Interface Flags
section under Common Output Fields Description.
Encapsulation
MAC address and corresponding number of input frames, input bytes, output frames, and output
bytes.
Number of MAC
addresses
Policer Statistics
(Displayed for mac-address option for ge, xe, and et interface types only) Display information about
policers applied to a logical interface-MAC pair.
Policer typeType of policer that is out of spec with respect to the configuration. It can be one or
Sample Output
show interfaces mac-database (All MAC Addresses on a Port)
user@host> show interfaces mac-database xe-0/3/3
Physical interface: xe-0/3/3, Enabled, Physical link is Up
Interface index: 372, SNMP ifIndex: 788
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: 10Gbps, Loopback:
None, Source filtering: Disabled, Flow control: Enabled
1658
Device flags
: Present Running
Interface flags: SNMP-Traps Internal: 0x4000
Link flags
: None
Logical interface xe-0/3/3.0 (Index 364) (SNMP ifIndex 829)
Flags: SNMP-Traps 0x4004000 Encapsulation: ENET2
MAC address
Input frames
Input bytes Output frames
00:00:00:00:00:00
1
56
0
00:00:c0:01:01:02
7023810
323095260
0
00:00:c0:01:01:03
7023810
323095260
0
00:00:c0:01:01:04
7023810
323095260
0
00:00:c0:01:01:05
7023810
323095260
0
00:00:c0:01:01:06
7023810
323095260
0
00:00:c0:01:01:07
7023810
323095260
0
00:00:c0:01:01:08
7023809
323095214
0
00:00:c0:01:01:09
7023809
323095214
0
00:00:c0:01:01:0a
7023809
323095214
0
00:00:c0:01:01:0b
7023809
323095214
0
00:00:c8:01:01:02
30424784
1399540064
37448598
00:00:c8:01:01:03
30424784
1399540064
37448598
00:00:c8:01:01:04
30424716
1399536936
37448523
00:00:c8:01:01:05
30424789
1399540294
37448598
00:00:c8:01:01:06
30424788
1399540248
37448597
00:00:c8:01:01:07
30424783
1399540018
37448597
00:00:c8:01:01:08
30424783
1399540018
37448596
00:00:c8:01:01:09
8836796
406492616
8836795
00:00:c8:01:01:0a
30424712
1399536752
37448521
00:00:c8:01:01:0b
30424715
1399536890
37448523
Number of MAC addresses : 21
Output bytes
0
0
0
0
0
0
0
0
0
0
0
1722635508
1722635508
1722632058
1722635508
1722635462
1722635462
1722635416
406492570
1722631966
1722632058
Output bytes
00:00:00:aa:00:02
23888711
2627758118
300
22200
00:00:00:aa:00:03
00:00:00:aa:00:04
1659
Output bytes
0
0
0
0
0
0
0
0
0
0
0
1749857526
1749857572
1749854076
1749857526
1749857526
1749857480
1749857434
433714680
1749853984
1749854122
1660
Release Information
Description
Options
Ethernet interface.
identifier(Optional) Identifier of the multichassis aggregated Ethernet interface.
number(Optional) Specify the logical interface by unit number.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
view
Field Description
Member Link
Local Status
Peer Status
Local State
1661
Field Description
Peer State
on the AE.
Local StateUp or down state of the local device.
Peer StateUp or down state of the peer device.
Peer Ip/ICL-PL/StateAddress, interface and state of the peer
device.
Logical Interface
ICL-PL
switchover mode
switchover status
revert time
Sample Output
show interfaces mc-ae
user@host> show interfaces mc-ae ae0 unit 512
Member Links
: ae0
Local Status
: active
Peer Status
: active
Logical Interface
: ae0.512
Core Facing Interface : Label Ethernet Interface
ICL-PL
: Label Ethernet Interface
show interfaces mc-ae (Active/Active Bridging and VRRP over IRB on MX Series Routers)
user@host# show interfaces mc-ae ge-0/0/0.0
Member Link
: ae0
Current State Machine's State: active
1662
Local Status
Local State
Peer Status
Peer State
Logical Interface
Topology Type
Local State
Peer State
Peer Ip/ICL-PL/State
:
:
:
:
:
:
:
:
:
active
up
active
up
ae0.0
bridge
up
up
192.168.100.10 ge-0/0/0.0 up
1663
Release Information
Description
Options
show interfaces transport pm (all | optics | otn) (all | current | currentday | interval |
previousday) (all |interface-name)
Required Privilege
Level
Related
Documentation
view
Field Description
Physical interface
Interval
Suspect Flag
Reason
COUNT
Measured value.
THRESHOLD
1664
Field Description
TCA-ENABLED
TCA-RAISED
Near End PM
Near end threshold crossing defect trigger. For more information abo
Far End PM
Far end threshold crossing defect trigger. For more information abou
FEC PM
BER PM
Bit error rate threshold crossing defect trigger. For more information a
CURRENT
PM
Performance monitor.
MIN
MAX
AVG
Average value.
q Value
SNR
Laser tx power
Laser rx power
Magnitude of the laser bias power setting current. The laser bias provi
and modulates currents.
1665
Sample Output
show interfaces transport pm
user@host> show interfaces transport pm all current et-0/1/0
Physical interface: et-0/1/0, SNMP ifIndex 515
14:45-current
Elapse time:900 Seconds
Near End
Suspect Flag:False
Reason:None
PM
COUNT
THRESHOLD
TCA-ENABLED
OTU-BBE
OTU-ES
OTU-SES
OTU-UAS
Far End
PM
0
0
0
427
Suspect Flag:True
COUNT
OTU-BBE
OTU-ES
OTU-SES
OTU-UAS
Near End
PM
0
0
0
0
Suspect Flag:False
COUNT
ODU-BBE
ODU-ES
ODU-SES
ODU-UAS
Far End
PM
0
0
0
427
Suspect Flag:True
COUNT
ODU-BBE
ODU-ES
ODU-SES
ODU-UAS
FEC
PM
0
0
0
0
Suspect Flag:False
COUNT
TCA-RAISED
800
135
90
90
No
No
No
No
Reason:Unknown
THRESHOLD
TCA-ENABLED
800
135
90
90
THRESHOLD
No
No
No
No
TCA-RAISED
No
No
No
No
No
No
No
No
Reason:None
TCA-ENABLED
TCA-RAISED
800
135
90
90
No
No
No
No
Reason:Unknown
THRESHOLD
TCA-ENABLED
800
135
90
90
THRESHOLD
No
No
No
No
TCA-RAISED
No
No
No
No
No
No
No
No
Reason:None
TCA-ENABLED
FEC-CorrectedErr
2008544300
0
NA
FEC-UncorrectedWords
0
0
NA
BER
Suspect Flag:False
Reason:None
PM
MIN
MAX
AVG
THRESHOLD
TCA-RAISED
BER
3.6e-5
5.8e-5
3.6e-5
10.0e-3
Yes
Physical interface: et-0/1/0, SNMP ifIndex 515
14:45-current
Suspect Flag:True
Reason:Object Disabled
PM
CURRENT
MIN
MAX
AVG
TCA-ENABLED
TCA-RAISED
TCA-RAISED
NA
NA
TCA-ENABLED
No
THRESHOLD
(MIN)
(MAX)
(MIN) (MAX)
(MIN) (MAX)
Lane chromatic dispersion
0
0
NA
NA
NA
NA
Lane differential group delay
0
0
NA
NA
NA
NA
Lane state of polarization
0
0
NA
NA
NA
NA
Lane Polarization Dependent loss 0
0
NA
NA
NA
NA
q Value
120
1666
120
120
120
0
NA
NA
NA
SNR
0
NA
NA
NA
Laser tx power(0.01dBm)
-100
No
No
No
Laser rx power(0.01dBm)
-500
No
No
No
Module temperature(Celsius)
75
No
No
No
Tx laser bias current(0.1mA)
0
NA
NA
NA
Rx laser bias current(0.1mA)
0
NA
NA
NA
Carrier frequency offset(MHz)
5000
No
No
No
NA
28
NA
-5000
No
-3642
No
46
No
0
NA
1270
NA
-186
No
28
29
28
-5000
-5000
-5000
-300
-3665
-3626
-3637
-1800
46
46
46
-5
1270
1270
1270
-186
-186
-186
-5000
1667
Release Information
Description
Display Layer 2 learning properties for all the configured routing instances.
Options
Required Privilege
Level
view
Output Fields
Table 111 on page 1668 describes the output fields for the show l2-learning instance
command. Output fields are listed in the approximate order in which they appear.
Field Description
Routing Instance
Bridging Domain
Index
Logical System
LHThe maximum number of MAC addresses has been learned on the routing instance. The routing
Maximum number of MAC addresses that can be learned from each interface in the routing instance
or bridging domain.
Sample Output
show l2-learning instance
user@host> show l2-learning instance
Information for routing instance:
Routing Instance flags (DL -disable learning, SE -stats enabled,
1668
Bridging
Domain
vlan100
vlan200
Index
1
3
4
Logical
System
Default
Default
Default
Routing
flags
MAC
limit
5000
5120
5120
1669
Release Information
Description
(MX Series routers and EX9200 switches only) Display ARP statistics, Neighbor Discovery
statistics, or remote MAC addresses for the Multi-Chassis Aggregated Ethernet (MC-AE)
nodes for all or specified redundancy groups on a router or switch or logical systems on
a router or switch. Note that the Redundancy Group ID is inherited by the bridging domain
or VLAN from member AE interfaces.
Options
nodes.
nd-statistics(Optional) Count of Neighbor Discovery packets sent and received by the
1670
view
Configuring Active-Active Bridging and VRRP over IRB in Multichassis Link Aggregation
on MX Series Routers
Output fields are listed in the approximate order in which they appear.
Field Description
Redundancy Group ID
ARP statistics for this Multichassis Link Aggregation Group (MC-LAG) instance.
Service-id
Field Description
Redundancy Group ID
MCLAG ND Statistics
Group ID
Neighbor Discovery statistics for this Multichassis Link Aggregation Group (MC-LAG) instance.
ND Tx Count To Peer
ND Drop Count
received from line
Total number of Neighbor Discovery packets sent by the peer that were received.
1671
Field Description
ND Drop Count
received from peer
Total number of Neighbor Discovery packets sent by the peer that were dropped
Service-id
Field Description
Redundancy Group ID
Peer-Addr
VLAN
MAC
Hardware media access control address associated with the redundancy group.
MCAE-ID
Flags
Connection state: local connect or Remote connect. If no flag is shown, the redundancy group may not
be connected.
Status
Sample Output
show l2-learning redundancy-groups arp-statistics
user@host> show l2-learning redundancy-groups arp-statistics
Logical System : default
Redundancy Group ID : 1
Flags : Local Connect, Remote Connect
MCLAG ARP Statistics
Group ID
ARP Rx Count From Line
ARP Tx Count To Peer
ARP Rx Count From Peer
ARP Install Count
ARP Drop Count received from line
ARP Drop Count received from peer
:
:
:
:
:
:
:
1
52
15
39
34
37
5
1672
ND Statistics
ID
Count From Line
Count To Peer
: 1
: 52
: 15
ND
ND
ND
ND
:
:
:
:
39
34
37
5
VLAN
100
MAC
MCAE-ID
64:87:88:6a:df:f0
Subunit
0
Opcode
1
:
:
:
:
:
:
:
1
52
15
39
34
37
5
MCLAG ND Statistics
Group ID
ND Rx Count From Line
ND Tx Count To Peer
ND Rx Count From Peer
ND Install Count
ND Drop Count received from line
ND Drop Count received from peer
: 1
52
15
39
34
37
5
:
:
:
:
:
:
1673
Release Information
Description
Options
Aggregated Ethernetaenumber
Fast Ethernetfe-fpc/pic/port
Gigabit Ethernetge-fpc/pic/port
NOTE: The show lacp interfaces command returns the following error message
if your system is not configured in either active or passive LACP mode:
Warning: lacp subsystem not running not needed by configuration
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Aggregated interface
1674
Field Description
LACP State
ExpExpired state. Yes indicates the actor or partner is in an expired state. No indicates the actor
DefDefault. Yes indicates that the actors receive machine is using the default operational partner
information, administratively configured for the partner. No indicates the operational partner
ColCollection of incoming frames. Yes indicates collection of incoming frames on the link is
currently enabled and is not expected to be disabled. Otherwise, the value is No.
SynSynchronization. If the value is Yes, the link is considered synchronized. It has been allocated
to the correct link aggregation group, the group has been associated with a compatible aggregator,
and the identity of the link aggregation group is consistent with the system ID and operational key
information transmitted. If the value is No, the link is not synchronized. It is currently not in the right
aggregation.
AggrAbility of aggregation port to aggregate (Yes) or to operate only as an individual link (No).
TimeoutLACP timeout preference. Periodic transmissions of LACP PDUs occur at either a slow
or fast transmission rate, depending upon the expressed LACP timeout preference (Long Timeout
or Short Timeout).
ActivityActor or partners port activity. Passive indicates the ports preference for not transmitting
LAC PDUs unless its partners control value is Active. Active indicates the ports preference to
1675
Field Description
LACP Protocol
Link state (active or standby) indicated in parentheses next to the interface when link protection
is configured.
CurrentThe state machine receives an LACP PDU and enters the Current state.
DefaultedIf no LACP PDU is received before the timer for the Current state expires a second
time, the state machine enters the Defaulted state.
ExpiredIf no LACP PDU is received before the timer for the Current state expires once, the state
machine enters the Expired state.
InitializeWhen the physical connectivity of a link changes or a Begin event occurs, the state
machine enters the Initialize state.
LACP DisabledIf the port is operating in half duplex, the operation of LACP is disabled on the
port, forcing the state to LACP Disabled. This state is similar to the Defaulted state, except that
Port DisabledIf the port becomes inoperable and a Begin event has not occurred, the state
machine enters the Port Disabled state.
Mux StateState of the multiplexer state machine for the aggregation port. The state is one of the
following values:
AttachedMultiplexer state machine initiates the process of attaching the port to the selected
aggregator.
CollectingYes indicates that the receive function of this link is enabled with respect to its
participation in an aggregation. Received frames are passed to the aggregator for collection. No
indicates the receive function of this link is not enabled.
Collecting DistributingCollecting and distributing states are merged together to form a combined
state (coupled control). Because independent control is not possible, the coupled control state
machine does not wait for the partner to signal that collection has started before enabling both
collection and distribution.
DistributingYes indicates that the transmit function of this link is enabled with respect to its
participation in an aggregation. Frames may be passed down from the aggregators distribution
function for transmission. No indicates the transmit function of this link is not enabled.
LACP Statistics
1676
LACP statistics are returned when the extensive option is used and provides the following information:
LACP RxLACP received counter that increments for each normal hello.
Sample Output
show lacp interfaces (Aggregated Ethernet)
user@host> show lacp interfaces ae0 extensive
Aggregated interface: ae0
LACP state:
Role
Exp
Def Dist
ge-1/0/1
Actor
No
Yes
ge-1/0/1
Partner
No
Yes
ge-1/0/2
Actor
No
Yes
ge-1/0/2
Partner
No
Yes
LACP protocol:
ge-1/0/1
distributing
ge-1/0/2
distributing
ge-1/0/1 (active)
distributing
ge-1/0/2 (standby)
LACP Statistics:
ge-1/0/1
ge-1/0/2
No
No
Receive State
CURRENT
Syn
Aggr
Timeout
Activity
No
No
Yes
Fast
Active
No
No
No
Col
No
No
No
No
No
Yes
Yes
Yes
Fast
Passive
Fast
Fast
Active
Passive
Transmit State
Fast periodic
Mux State
Collecting
CURRENT
Fast periodic
Collecting
CURRENT
Fast periodic
Collecting
CURRENT
LACP Rx
0
0
Fast periodic
LACP Tx
Unknown Rx
0
0
0
0
WAITING
Illegal Rx
0
0
1677
show lldp
Syntax
Release Information
Description
Options
Required Privilege
Level
List of Sample Output
Output Fields
show lldp
<detail>
view
Field Description
LLDP
Advertisement
interval
Transmit delay
Hold timer
Notification interval
Connection Hold
timer
1678
Field Description
Port Description
TLV type
Name of the interface for which LLDP configuration information is being reported
For information about interface names, see Interface Naming Overview. For
information about interface names for TX Matrix routers, see TX Matrix Router
Chassis and Interface Names. For information about FPC numbering on TX Matrix
routers, see Routing Matrix with a TX Matrix Router FPC Numbering.
Parent Interface
Name of the aggregated Ethernet interface, if any, to which the interface belongs.
LLDP
LLDP-MED
Power Negotiation
LLDP power negotiation operating state. The state can be Enabled or Disabled.
List of IEEE 802.1 LLDP TLVs supported by this device (detail only).
1679
Sample Output
show lldp
user@host> show lldp
LLDP
Advertisement interval
Transmit delay
Hold timer
Notification interval
Config Trap Interval
Connection Hold timer
Port ID TLV subtype
Port Description TLV type
Interface
all
:
:
:
:
:
:
:
:
:
Enabled
30 seconds
2 seconds
120 seconds
0 Second(s)
0 seconds
300 seconds
locally-assigned
interface-description (ifDescr)
Parent Interface
-
LLDP
Enabled
LLDP-MED
Power Negotiation
Sample Output
show lldp detail
user@host> show lldp detail
LLDP
Advertisement interval
Transmit delay
Hold timer
Notification interval
Config Trap Interval
Connection Hold timer
Port ID TLV subtype
Port Description TLV type
:
:
:
:
:
:
:
:
:
Enabled
30 seconds
2 seconds
120 seconds
0 Second(s)
0 seconds
300 seconds
locally-assigned
interface-description (ifDescr)
Interface
Parent Interface
Neighbor count
all
2
Interface
xe-0/0/0
xe-0/0/1
Parent Interface
-
LLDP
LLDP-MED
Power Negotiation
Enabled
Vlan-id
4080
4080
Vlan-name
vlan-4080
vlan-4080
1680
Output Fields
Field Description
LLDP Local
Information details
Chassis ID
System name
System descr
System Capabilities
Management
Information
Listed by Interface Name, Address Subtype (such as ipv4, ipv6), Address (such
as 192.168.168.229, 1fd::1a10), Interface Number, and Interface Numbering Subtype.
Interface Name
Parent Interface
Interface ID
1681
1682
Field Name
Field Description
Interface
Description
Status
Sample Output
show lldp local-information(Management Information Address Subtype is IPv4)
user@host> show lldp local-information
LLDP Local Information details
Chassis ID
: 64:87:88:65:37:c0
System name : apg-hp1
System descr : Juniper Networks, Inc. mx240 , version 14.1I20131231_0701_builder
[builder] Build date: 2013-12-31 07:13:42 UTC
System Capabilities
Supported
: Bridge Router
Enabled
: Bridge Router
Management Information
Interface Name : Unknown
Address Subtype : IPv4(1)
Address
: 10.216.97.103
Interface Number
: 1
Interface Numbering Subtype
: ifIndex(2)
Interface name
fxp0
me0
ge-2/0/0
ge-2/0/1
Parent Interface
ae0
ae0
Interface ID
1
33
1475
1476
Interface description
fxp0
me0
ge-2/0/0
ge-2/0/1
Status
Up
Up
Up
Up
Parent Interface
-
: 1
: ifIndex(2)
Interface ID
530
531
528
529
Interface description
ge-1/2/2
ge-1/2/3
Status
Down
Down
Up
Up
1683
Release Information
Description
Options
physical interface.
NOTE: Starting with Junos OS Release 14.2, you can also display LLDP
neighbor details for management interfaces, such as fxp or me, on MX
Series routers.
Required Privilege
Level
Related
Documentation
view
Output Fields
Table 118 on page 1684 describes the output fields for the show lldp neighbors command.
Output fields are listed in the approximate order in which they appear.
1684
Field Name
Field Description
LLDP Remote
Devices Information
LocalInterface
ChassisId
Field Description
PortInfo
List of port information gathered from neighbors. This could be the port
identifier or port description.
SysName
LLDP Neighbor
Information
Information about both local and neighbor systems on the interface (appears
when the interface option is used).
Local Information
Information about local systems on the interface (appears when the interface
option is used).
Neighbor
Information
Information about both local and neighbor system on the interface (appears
when the interface option is used).
Index
Time Mark
Time To Live
Number of seconds for which this information is valid (appears when the
interface option is used).
Local Interface
Name of the local physical interface (appears when the interface option is
used).
Parent Interface
Local Port ID
Neighbor
Information
Chassis type
Type of chassis identifier supplied, such as MAC address (appears when the
interface option is used).
Chassis ID
Chassis identifier of type listed (appears when the interface option is used).
Port type
Type of port identifier supplied, such as local (appears when the interface
option is used).
Port ID
Port identifier of type listed (appears when the interface option is used).
Port description
System name
Name supplied by the system on the interface (appears when the interface
option is used).
System Description
1685
1686
Field Name
Field Description
System Capabilities
Management
address
Details of the management address: Address Type (such as ipv4 and ipv6),
Address (such as 10.204.34.35, 1fd::1a10), Interface Number, Interface Subtype,
and Organization Identifier (OID) (appears when the interface option is used).
Organization Info
Sample Output
show lldp neighbors
user@host> show lldp neighbors
Local Interface
ge-2/0/0
ge-2/0/1
Parent Interface
ae0
ae0
Chassis Id
ac:4b:c8:92:67:c0
ac:4b:c8:92:67:c0
Port info
528
529
System Name
apg-hp
apg-hp
Sample Output
show lldp neighbors interface ge-0/0/4 (Management Address is IPv4)
user@host> show lldp neighbors interface ge-0/0/4
LLDP Neighbor Information:
Local Information:
Index: 2 Time to live: 120 Time mark: Tue Dec 31 11:47:46 2013 Age: 15 secs
Local Interface
: ge-2/0/1
Parent Interface
: ae0
Local Port ID
: 1476
Ageout Count
: 0
Neighbour Information:
Chassis type
: Mac address
Chassis ID
: ac:4b:c8:92:67:c0
Port type
: Locally assigned
Port ID
: 529
Port description
: ge-1/2/3
System name
: apg-hp
System Description : Juniper Networks, Inc. mx240 , version 14.1-20131222.0
[builder] Build date: 2013-12-22 09:13:26 UTC
System capabilities
Supported: Bridge Router
Enabled : Bridge Router
Management address
Address Type
Address
Interface Number
Interface Subtype
OID
:
:
:
:
:
IPv4(1)
10.216.98.57
1
ifIndex(2)
1.3.6.1.2.1.31.1.1.1.1.1.
Organization Info
OUI
: IEEE 802.3 Private (0x00120f)
Subtype : MAC/PHY Configuration/Status (1)
Info
: Autonegotiation [supported, enabled (0x3)], PMD Autonegotiation
Capability (0x1d), MAU Type (0x0)
Index
: 1
Organization Info
OUI
:
Subtype :
Info
:
Index
:
Organization Info
OUI
: IEEE 802.3 Private (0x00120f)
1687
Subtype
Info
Index
System capabilities
Supported: Bridge Router
Enabled : Bridge Router
Management address
Address Type
Address
Interface Number
Interface Subtype
OID
:
:
:
:
:
IPv6(2)
1fd::1a10
1
ifIndex(2)
1.3.6.1.2.1.31.1.1.1.1.1.
Organization Info
OUI
: IEEE 802.3 Private (0x00120f)
Subtype : MAC/PHY Configuration/Status (1)
Info
: Autonegotiation [supported, enabled (0x3)], PMD Autonegotiation
Capability (0x5), MAU Type (0x0)
Index
: 1
Organization Info
OUI
:
Subtype :
Info
:
Index
:
Organization Info
OUI
:
Subtype :
Info
:
Index
:
Organization Info
OUI
: Ethernet Bridged (0x0080c2)
Subtype : VLAN Name (3)
1688
Info
Index
Parent Interface
Chassis Id
Port info
78:fe:3d:ee:4e:00
151
a8:d0:e5:50:26:c0
512
a8:d0:e5:50:26:c0
513
1689
1690
Field Name
Field Description
LLDP Remote
Database Table
Counters
LastchangeTime
Time elapsed between LLDP agent startup and the last change to the remote
database table information.
Inserts
Deletes
Drops
Number of LLDP frames dropped from the remote database table because of
errors.
Ageouts
Number of remote database table entries that have aged out of the table.
Sample Output
show lldp remote-global-statistics
user@host> show lldp remote-global-statistics
user@host> show lldp remote-global-statistics
LLDP Remote Database Table Counters
LastchangeTime
Inserts
Deletes
00:00:76 (76 sec)
192
0
Drops
0
Ageouts
0
1691
Release Information
Description
Options
interface.
NOTE: Starting with Junos OS Release 14.2, you can also display LLDP
statistical details for management interfaces, such as fxp or me, on MX
Series routers.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
view
Field Description
Interface
Interface name.
For information about interface names, see Interface Naming Overview. For
information about interface names for TX Matrix routers, see TX Matrix Router
Chassis and Interface Names. For information about FPC numbering on TX
Matrix routers, see Routing Matrix with a TX Matrix Router FPC Numbering.
For information about extended port names in the Junos Fusion technology,
see Understanding Junos Fusion Ports.
1692
Received
Transmitted
Unknown-TLVs
With-Errors
Field Description
Discarded
Transmitted
Untransmitted
1693
Sample Output
show lldp statistics
user@host> show lldp statistics
Interface
xe-3/0/0.0
xe-3/0/1.0
xe-3/0/2.0
xe-3/0/3.0
xe-3/0/4.0
xe-3/0/5.0
xe-3/0/6.0
xe-3/0/7.0
xe-5/0/6.0
xe-5/0/7.0
Parent Interface
ae31.0
ae31.0
ae31.0
ae31.0
ae31.0
ae31.0
ae31.0
ae31.0
-
Discarded TLVs
0
0
0
0
0
0
0
0
0
0
Transmitted
3044
3044
3044
3044
3075
3075
3075
3075
17312
17312
Received
1564
1564
1565
1566
1598
1598
1596
1597
0
0
Unknown TLVs
0
0
0
0
0
0
0
0
0
0
With Errors
0
0
0
0
0
0
0
0
0
0
Untransmitted
1
1
1
1
1
1
1
1
0
0
Sample Output
show lldp statistics interface ge-0/1/1
user@host> show lldp statistics interface ge-0/1/1
Interface Received Transmitted Unknown-TLVs With-Errors Discarded
--------- -------- ----------- ------------ ----------- --------ge-0/1/1 544
540
0
0
0
1694
Release Information
Description
Options
count entry-count(Optional) Number of entries to display from the statistics table. The
the range of values is 1 through 8192. On EX Series switches, the range of values is 1
through 8191.
maintenance-association ma-nameName of an existing CFM maintenance association.
maintenance-domain md-nameName of an existing connectivity fault management
Series routers, the range of values is 1 through 8192. On EX Series switches, the range
of values is 1 through 8191.
Required Privilege
Level
Related
Documentation
Output Fields
view
1695
Field Description
MEP identifier
MAC address
Index
Index number that corresponds to the ETH-DM entry in the CFM database.
For a one-way ETH-DM session, the frame delay time, in microseconds, measured
at the receiver MEP.
For a detailed description of one-way Ethernet frame delay measurement, see
the ITU-T Y.1731 Ethernet Service OAM topics in the Junos OS Network Interfaces
Library for Routing Devices.
For a two-way ETH-DM session, the frame delay time, in microseconds, measured
at the initiator MEP.
For a detailed description of two-way Ethernet frame delay measurement, see
the ITU-T Y.1731 Ethernet Service OAM topics in the Junos OS Network Interfaces
Library for Routing Devices.
1696
Sample Output
show oam ethernet connectivity-faultmanagement
delay-statistics
user@switch> show oam ethernet connectivity-fault-management delay-statistics
maintenance-domain md6 maintenance-association ma6
MEP identifier: 100, MAC address: 00:05:85:73:7b:39
Remote MEP count: 2
Remote MEP identifier: 101
Remote MAC address: 00:05:85:73:39:4a
Delay measurement statistics:
Index One-way delay Two-way delay
(usec)
(usec)
1
259
519
2
273
550
3
287
571
4
299
610
5
313
650
Average one-way delay
: 286 usec
Average one-way delay variation: 62 usec
Best case one-way delay
: 259 usec
Worst case one-way delay
: 313 usec
Average two-way delay
: 580 usec
Average two-way delay variation: 26 usec
Best case two-way delay
: 519 usec
Worst case two-way delay
: 650 usec
Remote MEP identifier: 102
Remote MAC address: 00:04:55:63:39:5a
Delay measurement statistics:
Index One-way delay Two-way delay
(usec)
(usec)
1
29
58
2
23
59
3
27
56
4
29
62
5
33
68
Average one-way delay
: 28 usec
Average one-way delay variation: 3 usec
Best case one-way delay
: 23 usec
Worst case one-way delay
: 33 usec
Average two-way delay
: 60 usec
Average two-way delay variation: 3 usec
Best case two-way delay
: 56 usec
Worst case two-way delay
: 68 usec
1697
2
273
550
3
287
571
4
299
610
5
313
650
Average one-way delay
:
Average one-way delay variation:
Best case one-way delay
:
Worst case one-way delay
:
Average two-way delay
:
Average two-way delay variation:
Best case two-way delay
:
Worst case two-way delay
:
1698
286 usec
62 usec
259 usec
313 usec
580 usec
26 usec
519 usec
650 usec
Release Information
Description
On M7i and M10i with the Enhanced CFEB (CFEB-E), M320, MX Series, T320, and T640
routers, display IEEE 802.1ag Operation, Administration, and Management (OAM)
connectivity fault management forwarding state information for Ethernet interfaces.
Options
interface only.
instance instance-nameDisplay forwarding state information for the specified forwarding
instance only.
brief | detail | extensive(Optional) Display the specified level of output.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Level of Output
Interface name
Interface identifier.
All levels
Link (Status)
All levels
Filter action
All levels
Next-hop type.
All levels
Next index
brief
Level
detail
1699
Field Description
Level of Output
Direction
none
Instance name
All levels
CEs
All levels
VEs
All levels
Sample Output
show oam ethernet
connectivity-faultmanagement forwardingstate instance
user@host> show oam ethernet connectivityfault-management forwarding-state instance
Instance name: __+bd1__
CEs: 3
VEs: 0
Maintenance domain forwarding state:
Level
Direction
0
1
2
3
4
5
6
7
Filter action
Drop
Drop
Drop
Drop
Drop
Drop
Drop
Drop
Nexthop
type
none
none
none
none
none
none
none
none
Nexthop
index
1700
Direction
Filter action
down
Drop
Drop
Drop
Drop
Drop
Drop
Drop
Receive
Nexthop
type
none
none
none
none
none
none
none
none
Nexthop
index
Direction
Filter action
down
Drop
Drop
Drop
Drop
Drop
Drop
Drop
Receive
Nexthop
type
none
none
none
none
none
none
none
none
Nexthop
index
1701
Level: 0
Filter action: Drop
Nexthop type: none
Level: 1
Filter action: Drop
Nexthop type: none
...
1702
Direction
Filter action
down
Drop
Drop
Drop
Drop
Drop
Drop
Drop
Receive
Nexthop
type
none
none
none
none
none
none
none
none
Nexthop
index
Release Information
Description
Options
view
1703
Table 123 on page 1704 lists the output fields for the show oam ethernet
connectivity-fault-management interfaces command. Output fields are listed in the
approximate order in which they appear.
Field Description
Level of Output
Interface
Interface identifier.
All levels
Interface status
All levels
Link status
All levels
Maintenance
domain name
detail extensive
Format
(Maintenance
domain)
detail extensive
Level
All levels
Maintenance
association name
detail extensive
Format
(Maintenance
association)
detail extensive
Continuity-check
status
Continuity-check status.
detail extensive
Ethernet-ais status
detail extensive
Interval
detail extensive
Loss-threshold
detail extensive
Interface status
TLV
Status of the interface status TLV, if configured on the MEP interface: none, up,
down, testing, unknown, dormant, notPresent, lowerLayerDown
detail extensive
Status of the port status TLV, if configured on the MEP interface: none, no, yes
detail extensive
Connection
Protection TLV
Status of the connection protection TLV if configured on the MEP interface: no,
detail extensive
yes
If yes, then the transmitted connection protection TLV is decoded and the
following three fields are displayed: Prefer me, Protection in use, FRR Flag
1704
Field Description
Level of Output
Prefer me
If set to yes, the path through which CCM was transmitted is preferred (unless
the path fails). It is used for signaling a manual-switch command to the remote
side.
detail extensive
Used for protection decision coordination. Its value is set to yes if the endpoint
transmitting the CCM is currently transmitting the user traffic to protection path.
detail extensive
detail extensive
All levels
Neighbors
All levels
Direction
detail extensive
MAC address
detail extensive
MEP status
detail extensive
Whether the remote MEP is not receiving connectivity check messages (CCMs).
detail extensive
Erroneous CCM
received
detail extensive
Cross-connect CCM
received
detail extensive
Whether the remote defect indication (RDI) bit is set in messages that have
been received. The absence of the RDI bit in a CCM indicates that the
transmitting MEP is receiving CCMs from all configured MEPs.
detail extensive
Some remote
MEP's MAC in error
state
detail extensive
Alarm Indication
Signal
detail extensive
CCMs sent
detail extensive
1705
Field Description
Level of Output
detail extensive
LBMs sent
detail extensive
detail extensive
Valid out-of-order
LBRs received
Number of LBRs received that were valid messages and not in sequence.
detail extensive
detail extensive
LBRs sent
detail extensive
LTMs sent
detail extensive
LTMs received
detail extensive
LTRs sent
detail extensive
LTRs received
detail extensive
Sequence number
of next LTM request
detail extensive
1DMs sent
detail extensive
detail extensive
detail extensive
1706
detail extensive
Field Description
Level of Output
DMMs sent
detail extensive
detail extensive
Invalid DMMs
received
detail extensive
DMRs sent
detail extensive
detail extensive
detail extensive
detail extensive
detail extensive
Invalid LMM
received
detail extensive
LMR sent
detail extensive
detail extensive
Invalid LMR
received
detail extensive
detail extensive
1707
Field Description
Level of Output
detail extensive
SLM sent
detail extensive
detail extensive
Invalid SLM
received
detail extensive
SLR sent
detail extensive
detail extensive
detail extensive
extensive
Identifier (remote
extensive
extensive
extensive
extensive
MEP)
MAC address
(remote MEP)
State (remote
MEP)
Interface (remote
MEP)
Sample Output
show oam ethernet connectivity-faultmanagement interfaces
user@host> show oam ethernet connectivity-fault-management interfaces
Interface
Link
Status
Level
MEP
Identifier
ge-1/1/0.0
Up
Active
0
2
ge-1/1/0.1
Up
Active
0
2
1708
Neighbors
1
1
ge-1/1/0.10
ge-1/1/0.100
ge-1/1/0.101
ge-1/1/0.102
ge-1/1/0.103
ge-1/1/0.104
ge-1/1/0.105
ge-1/1/0.106
Up
Up
Up
Up
Up
Up
Up
Up
Active
Active
Active
Active
Active
Active
Active
Active
0
0
0
0
0
0
0
0
2
2
2
2
2
2
2
2
1
1
1
1
1
1
1
1
...
:
:
:
:
:
:
:
:
:
:
:
:
:
:
0
0
0
0
0
0
0
10
20
0
20
10
0
0
: 0
: 10
: 20
: 0
: 20
: 10
1709
: 0
State
ok
ok
Interface
ge-5/2/9.0
ge-5/2/9.0
:
:
:
:
:
:
:
State
ok
10
0
0
0
0
0
0
Interface
ge-0/2/5.0
1710
Defects:
Remote MEP not receiving CCM
Erroneous CCM received
Cross-connect CCM received
RDI sent by some MEP
Some remote MEP's MAC in error state
Statistics:
CCMs sent
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
Valid 1DMs received
Invalid 1DMs received
Out of sync 1DMs received
DMMs sent
Valid DMMs received
Invalid DMMs received
DMRs sent
Valid DMRs received
Invalid DMRs received
LMMs sent
Valid LMMs received
Invalid LMMs received
LMRs sent
Valid LMRs received
Invalid LMRs received
Remote MEP count: 1
Identifier
MAC address
2
00:90:69:7f:e4:30
State
:
:
:
:
:
no
no
no
no
no
:
:
:
:
:
:
:
:
:
:
:
:
225
0
0
0
0
0
0
0
0
0
0
1244305646
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Interface
: yes
1711
CCMs sent
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
:
:
:
:
:
:
:
:
:
:
:
:
76
0
0
0
0
0
0
0
0
0
0
1645032434
1DMs sent
Valid 1DMs received
Invalid 1DMs received
DMMs sent
DMRs sent
Valid DMRs received
Invalid DMRs received
:
:
:
:
:
:
:
0
0
0
0
0
0
0
: 0
: 0
: 10
: 20
: 0
: 20
: 10
: 0
State
ok
ok
Interface
ge-5/2/9.0
ge-5/2/9.0
Link
Status
Level
Up
Down
Up
Active
Inactive
Active
5
4
6
MEP
Identifier
100
400
200
Neighbors
0
0
0
1712
Interface
Link
Status
Level
ge-4/0/0.0
Up
Active
MEP
Identifier
200
Neighbors
0
Link
Status
Level
Up
Active
MEP
Identifier
100
Neighbors
0
Link
Status
Level
Down
Inactive
MEP
Identifier
400
Neighbors
0
1713
Release Information
Description
Options
Output Fields
view
Field Description
Linktrace to
MAC address of the 802.1ag node to which the linktrace message is targeted.
Interface
Interface used by the local MEP to send the linktrace message (LTM).
Maintenance Domain
Maintenance
Association
Level
Local Mep
Hop
1714
Field Description
TTL
Number of hops remaining in the linktrace message (LTM). The time to live (TTL) is decremented at
each hop.
MAC address of the egress interface of the node to which the LTM is forwarded or
the next-hop MAC address derived from the next egress identifier in the Egress-ID TLV of the LTR
PDU.
Transaction Identifier
4-byte identifier maintained by the MEP. Each LTM uses a transaction identifier. The transaction
identifier is maintained globally across all maintenance domains. Use the transaction identifier to
match an incoming linktrace responses (LTR), with a previously sent LTM.
Sample Output
show oam ethernet connectivity-faultmanagement linktrace path-database
user@host> show oam ethernet connectivity-fault-management linktrace path-database
maintenance-domain MD1 maintenance-association MA1 00:01:02:03:04:05
Linktrace to 00:01:02:03:04:05, Interface : ge-5/0/0.0
Maintenance Domain: MD1, Level: 7
Maintenance Association: MA1, Local Mep: 1
Hop
TTL
Source MAC address
Transaction Identifier:100001
1
63
00:00:aa:aa:aa:aa
2
62
00:00:bb:bb:bb:bb
3
61
00:00:cc:cc:cc:cc
4
60
00:01:02:03:04:05
00:00:ab:ab:ab:ab
1715
2
3
4
1716
62
61
60
00:00:bb:bb:bb:bb
00:00:cc:cc:cc:cc
00:01:02:03:04:05
00:00:bc:bc:bc:bc
00:00:cd:cd:cd:cd
00:00:00:00:00:00
Release Information
Description
Options
view
Table 125 on page 1717 lists the output fields for the show oam ethernet
connectivity-fault-management loss-statistics command. Output fields are listed in the
approximate order in which they appear.
Field Description
MEP identifier
MAC address
Index
Index number that corresponds to the ETH-LM entry in the CFM database.
1717
Field Description
Average frame loss measured in this session associated with ingress data frames.
Average frame loss ratio measured in this session associated with ingress data
frames.
Average frame loss measured in this session associated with egress data frames.
Average frame loss ratio measured in this session associated with egress data
frames.
Lowest frame loss measured in this session associated with ingress data frames.
Lowest frame loss ratio measured in this session associated with ingress data
frames.
Highest frame loss measured in this session associated with ingress data frames.
Highest frame loss ratio measured in this session associated with ingress data
frames.
Lowest frame loss measured in this session associated with egress data frames.
Lowest frame loss ratio measured in this session associated with egress data
frames.
Highest frame loss measured in this session associated with egress data frames.
Highest frame loss ratio measured in this session associated with egress data
frames.
1718
Far-end
Near-end
Frame loss
Total tx
(CIR)
(CIR)
244
489
733
976
Far-end
Frame loss
(EIR)
Near-end
Total tx
(EIR)
273
545
819
1093
1719
1720
0.00000%
0.00000
0.00000%
0.00000
0.00000%
0
0.00000%
0
0.00000%
0
0.00000%
0
0.00000%
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
view
1721
Table 126 on page 1722 lists the output fields for the show oam ethernet
connectivity-fault-management mep-database command. Output fields are listed in the
approximate order in which they appear.
Field Description
Maintenance domain
name
Format (Maintenance
domain)
Level
Maintenance
association name
Format (Maintenance
association)
Continuity-check status
Continuity-check status.
Interval
Loss-threshold
Connection Protection
TLV
Status of the connection protection TLV, if configured on the MEP interface: no, yes
If yes, then the transmitted connection protection TLV is decoded and the following three fields are
displayed: Prefer me, Protection in use, FRR Flag
Prefer me
If set to yes, the path through which CCM was transmitted is preferred (unless the path fails). It is
used for signaling a manual-switch command to remote side.
Its value can be yes or no.
Protection in use
Used for protection decision coordination. Its value is set to yes if the endpoint transmitting the CCM
is currently transmitting the user traffic to protection path.
Its value can be yes or no.
FRR Flag
1722
Field Description
MEP identifier
Direction
MAC address
Auto-discovery
Priority
Priority used for CCMs and linktrace messages transmitted by the MEP.
Interface name
Interface identifier.
Interface status
Link status
Cross-connect CCM
received
Whether the remote defect indication (RDI) bit is set in messages that have been received. The
absence of the RDI bit in a CCM indicates that the transmitting MEP is receiving CCMs from all
configured MEPs.
CCMs sent
LBMs sent
Number of loopback response messages (LBRs) received that were valid messages and in sequence.
1DMs sent
If the MEP is an initiator for a one-way ETH-DM session: Number of one-way delay measurement
(1DM) PDU frames sent to the peer MEP in this session.
For all other cases, this field displays 0.
If the MEP is a receiver for a one-way ETH-DM session: Number of valid 1DM frames received.
For all other cases, this field displays 0.
1723
Field Description
If the MEP is a receiver for a one-way ETH-DM session: Number of invalid 1DM frames received.
For all other cases, this field displays 0.
If the MEP is a receiver for a one-way ETH-DM session: Number of out-of-sync one-way delay
measurement request packets received.
DMMs sent
If the MEP is an initiator for a two-way ETH-DM session: Number of Delay Measurement Message
(DMM) PDU frames sent to the peer MEP in this session.
For all other cases, this field displays 0.
If the MEP is an initiator for a two-way ETH-DM session: Number of valid two-way delay measurement
packets received.
If the MEP is an initiator for a two-way ETH-DM session: Number of invalid two-way delay measurement
packets received.
DMRs sent
If the MEP is a responder for a ETH-DM session: Number of Delay Measurement Reply (DMR) frames
sent.
For all other cases, this field displays 0.
If the MEP is an initiator for a two-way ETH-DM session: Number of valid DMRs received.
For all other cases, this field displays 0.
If the MEP is an initiator for a two-way ETH-DM session: Number of invalid DMRs received.
For all other cases, this field displays 0.
Number of LBRs received that were valid messages and not in sequence.
LBRs sent
LTMs sent
LTMs received
LTRs sent
LTRs received
Sequence number of
next LTM request
1724
Field Description
LMM sent
If the interface is attached to an initiator MEP for a ETH-LM session: Number of loss measurement
message (LMM) PDU frames sent to the peer MEP in this session.
If the interface is attached to an initiator MEP for a ETH-LM session: Number of valid loss measurement
request packets received.
If the interface is attached to an initiator MEP for a ETH LM session: Number of invalid loss
measurement request packets received.
LMR sent
If the interface is attached to a responder MEP for a ETH-LM session: Number of loss measurement
reply (LMR) frames sent.
If the interface is attached to an initiator MEP for a ETH LM session: Number of valid LMR frames
received.
If the interface is attached to an initiator MEP for a ETH-LM session: Number of invalid LMR frames
received.
SLM sent
If the interface is attached to an initiator MEP for a ETH-SLM session: Number of synthetic loss
measurement (SLM) request packets transmitted from the source MEP to the remote or destination
MEP in this session.
If the interface is attached to a responder MEP for a ETH-SLM session: Number of valid SLM PDUs
transmitted from the source MEP to the remote or destination MEP.
If the interface is attached to a responder MEP for a ETH-SLM session: Number of invalid SLM PDUs
transmitted from the source MEP to the remote or destination MEP.
SLR sent
If the interface is attached to a responder MEP for a ETH-SLM session: Number detail extensive of
synthetic loss reply (SLR) frames sent.
If the interface is attached to an initiator MEP for a ETH-SLM session: Number of valid SLR PDUs that
the source MEP received from the remote or destination MEP.
If the interface is attached to an initiator MEP for a ETH-SLM session: Number of invalid SLR PDUs
that the source MEP received from the remote or destination MEP.
MAC address
Type
Whether the remote MEP MAC address was learned using automatic discovery or configured.
Interface
Interface of the remote MEP. A seven-digit number is appended if CFM is configured to run on a routing
instance of type VPLS.
1725
Field Description
Last flapped
Date, time, and how long ago the remote MEP interface went from down to up. The format is Last
flapped: year-month-day hours:minutes:seconds timezone (hours:minutes:seconds ago). For example,
Last flapped: 2002-04-26 10:52:40 PDT (04:33:20 ago).
Remote defect
indication
Whether the remote defect indication (RDI) bit is set in messages that have been received or
transmitted.
In the Maintenance domain section, displays the last transmitted port status TLV value.
In the Remote MEP section, displays the last value of port status TLV received from the remote
MEP.
In the Action profile section, displays, the last occurred event port-status-tlv blocked event. This
event occurred due to the reception of blocked value in the port status TLV from remote MEP.
In the Maintenance domain section, displays the last transmitted interface status TLV value.
In the Remote MEP section, displays the last value of interface status TLV received from the remote
MEP.
In the Action profile section, if displays, the last occurred event interface-status-tlv event ( either
lower-layer-down or down). This event occurred due to the reception of either lower or down value
in the interface status TLV from remote MEP.
Action profile
Last event
When an action profile occurs, displays the last event that triggered it.
When all the configured and occurred events (under action profile) are cleared, then the action taken
gets reverted (such as down interface is made up) and the corresponding time is noted and displayed.
Action
Sample Output
show oam ethernet connectivity-faultmanagement mep-database
user@host> show oam ethernet connectivity-fault-management mep-database
maintenance-domain vpls-vlan2000 maintenance-association vpls-vlan200
Maintenance domain name: vpls-vlan2000, Format: string, Level: 5
Maintenance association name: vpls-vlan200, Format: string
Continuity-check status: enabled, Interval: 100ms, Loss-threshold: 3 frames
MEP identifier: 200, Direction: up, MAC address: 00:19:e2:b0:74:01
Auto-discovery: enabled, Priority: 0
Interface status TLV: none, Port status TLV: none
Connection Protection TLV: no Interface name: ge-0/0/1.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:
1726
CCMs sent
: 1476
CCMs received out of sequence
: 0
LBMs sent
: 85
Valid in-order LBRs received
: 78
Valid out-of-order LBRs received
: 0
LBRs received with corrupted data
: 0
LBRs sent
: 0
LTMs sent
: 1
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 1
Sequence number of next LTM request
: 1
1DMs sent
: 0
Valid 1DMs received
: 0
Invalid 1DMs received
: 0
DMMs sent
: 0
DMRs sent
: 0
Valid DMRs received
: 0
Invalid DMRs received
: 0
Remote MEP count: 1
Identifier
MAC address
State
Interface
100
00:19:e2:b2:81:4b
ok vt-0/1/10.1049088
1727
Identifier
MAC address
201
00:90:69:0a:43:94
State
ok
Interface
ge-0/2/5.0
1728
: no
1729
: no
: no
: no
MAC address
00:12:1e:fb:ea:7d
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
328703
0
85
78
0
0
0
0
0
0
0
0
10
10
0
20
0
10
0
10
20
0
20
10
0
:
:
:
:
:
:
10
20
0
20
10
0
: 1
State
ok
Interface
ge-1/0/0.0
1730
1731
Release Information
Description
Options
1732
view
Table 127 on page 1733 lists the output fields for the show oam ethernet
connectivity-fault-management mep-statistics command. Output fields are listed in the
approximate order in which they appear.
Field Description
MEP identifier
MAC address
Index
Index number that corresponds to the ETH-DM entry in the CFM database.
For a one-way ETH-DM session, the frame delay time, in microseconds, measured
at the receiver MEP.
For a detailed description of one-way Ethernet frame delay measurement, see
the ITU-T Y.1731 Ethernet Service OAM topics in the Junos OS Network Interfaces
Library for Routing Devices.
For a two-way ETH-DM session, the frame delay time, in microseconds, measured
at the initiator MEP.
For a detailed description of two-way Ethernet frame delay measurement, see
the ITU-T Y.1731 Ethernet Service OAM topics in the Junos OS Network Interfaces
Library for Routing Devices.
1733
Field Description
Total number of synthetic loss message (SLM) PDU frames sent from the source
MEP to the remote MEP during this ETH-SLM session.
Total number of synthetic loss message (SLM) PDU frames that the remote
MEP received from the source MEP during this ETH-SLM session.
Total number of synthetic loss reply (SLR) PDU frames that the remote MEP
sent to the source MEP during this measurement session.
Total number of synthetic loss reply (SLR) PDU frames that the source MEP
received from the remote MEP during this measurement session.
Number of synthetic frames transmitted to the peer MEP for a test ID. A test ID
is used to distinguish each synthetic loss measurement because multiple
measurements can be simultaneously activated also on a given CoS and MEP
pair. It must be unique at least within the context of any SLM for the MEG and
initiating MEP.
Number of synthetic frames received from the peer MEP for a test ID. The MEP
generates a unique Test ID for the session, adds the source MEP ID, and initializes
the local counters for the session before SLM initiation. For each SLM PDU
transmitted for the session (test ID), the local counter TXFC1 is sent in the packet.
Value of the local counter TxFCl at the time of SLM frame transmission.
Value of the local counter RxFCl at the time of SLR frame transmission.
Sample Output
show oam ethernet connectivity-faultmanagement mep-statistics (CIR counters only)
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md1 maintenance-association ma-1 local-mep 3 remote-mep 103 count 3
MEP identifier: 100, MAC address: 00:05:85:73:7b:39
Remote MEP count
: 1
CCMs sent
: 6550
CCMs received out of sequence
: 0
LBMs sent
: 0
Valid in-order LBRs received
: 0
Valid out-of-order LBRs received
: 0
LBRs received with corrupted data
: 0
1734
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
Sequence number of next LTM request : 0
1DMs sent
: 5
Valid 1DMs received
: 0
Invalid 1DMs received
: 0
DMMs sent
: 5
DMRs sent
: 0
Valid DMRs received
: 5
Invalid DMRs received
: 0
LMM sent
: 5
Valid LMM received
: 5
Invalid LMM received
: 0
LMR sent
: 0
Valid LMR received
: 5
Invalid LMR received
: 0
Remote MEP identifier
: 101
Remote MAC address
: 00:05:85:73:39:4a
Delay measurement statistics:
Index
One-way delay
(usec)
1
259
2
273
3
287
4
299
5
313
Two-way delay
(usec)
519
550
571
610
650
:
:
:
:
:
:
:
286 usec
62 usec
259 usec
580 usec
26 usec
519 usec
650 usec
Near-end
Frame loss
(EIR)
:
:
:
:
:
:
:
:
:
:
:
:
Far-end
Frame loss
(EIR)
6.2
6.2%
6.2
6.2%
3
3%
9
9%
5
5%
9
9%
1735
show oam ethernet connectivity-faultmanagement mep-statistics (CIR and EIR counters enabled)
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md1 maintenance-association ma-1 local-mep 3 remote-mep 103 count 3
MEP identifier: 100, MAC address: 00:05:85:73:7b:39
Remote MEP count
: 1
CCMs sent
: 6550
CCMs received out of sequence
: 0
LBMs sent
: 0
Valid in-order LBRs received
: 0
Valid out-of-order LBRs received
: 0
LBRs received with corrupted data
: 0
LBRs sent
: 0
LTMs sent
: 0
LTMs received
: 0
LTRs sent
: 0
LTRs received
: 0
Sequence number of next LTM request : 0
1DMs sent
: 5
Valid 1DMs received
: 0
Invalid 1DMs received
: 0
DMMs sent
: 5
DMRs sent
: 0
Valid DMRs received
: 5
Invalid DMRs received
: 0
LMM sent
: 5
alid LMM received
: 5
Invalid LMM received
: 0
LMR sent
: 0
Valid LMR received
: 5
Invalid LMR received
: 0
Remote MEP identifier
: 101
Remote MAC address
: 00:05:85:73:39:4a
Delay measurement statistics:
Index
One-way delay
(usec)
1
259
2
273
3
287
4
299
5
313
Average one-way delay
Average one-way delay variation
Best case one-way delay
Average two-way delay
Average two-way delay variation
Best case two-way delay
Worst case two-way delay
Loss measurement statistics:
Index
Near-end
Far-end
Frame loss
Frame loss
(CIR)
(CIR)
1
9
9
2
3
5
3
7
5
4
9
6
5
3
6
1736
Two-way delay
(usec)
519
550
571
610
650
:
:
:
:
:
:
:
286 usec
62 usec
259 usec
580 usec
26 usec
519 usec
650 usec
Near-end
Frame loss
(EIR)
2
4
0
8
6
Far-end
Frame loss
(EIR)
4
6
2
2
4
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
6.2
6.2%
6.2
6.2%
3
3%
9
9%
5
5%
9
9%
4
4%
3.4
3.4%
0
0%
8
8%
2
2%
6
6%
1737
Two-way delay
(usec)
519
550
571
610
650
:
:
:
:
:
:
:
286 usec
62 usec
259 usec
580 usec
26 usec
519 usec
650 usec
Far-end
Frame loss
(EIR)
show oam ethernet connectivity-faultmanagement mep-statistics remote-mep (CIR and EIR counters enabled)
user@host> show oam ethernet connectivity-fault-management mep-statistics
maintenance-domain md1 maintenance-association ma-1 local-mep 3 remote-mep 103 count 3
remote-mep 101
MEP identifier: 100, MAC address: 00:05:85:73:7b:39
CCMs sent
:7762
CCMs received out of sequence
: 0
LBMs sent
: 0
1738
0
0
0
0
0
0
0
0
0
5
0
0
5
0
5
0
5
5
0
0
5
0
101
00:05:85:73:39:4a
Two-way delay
(usec)
519
550
571
610
650
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
286 usec
62 usec
259 usec
580 usec
26 usec
519 usec
650 usec
Near-end
Frame loss
(EIR)
5
6
0
8
6
:
:
:
:
:
:
:
:
:
Far-end
Frame loss
(EIR)
12
16
2
2
4
6.2
6.2%
6.2
6.2%
3
3%
9
9%
5
1739
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
5%
9
9%
4
4%
3.4
3.4%
0
0%
8
8%
2
2%
6
6%
1740
259 usec
313 usec
580 usec
26 usec
519 usec
650 usec
100
0
100
0
:
:
:
:
100
100
100
100
: 0 (0.00 %)
: 0 (0.00 %)
1741
5
313
650
Average one-way delay
:
Average one-way delay variation:
Best case one-way delay
:
Worst case one-way delay
:
Average two-way delay
:
Average two-way delay variation:
Best case two-way delay
:
Worst case two-way delay
:
statistics:
SLM packets sent
SLM packets received
SLR packets sent
SLR packets received
Accumulated SLM statistics:
Local TXFC1 value
Local RXFC1 value
Last Received SLR frame TXFCftc
Last Received SLR frame TXFCbtc
SLM Frame Loss:
Frame Loss (far-end)
Frame Loss (near-end)
1742
286 usec
62 usec
259 usec
313 usec
580 usec
26 usec
519 usec
650 usec
100
0
100
0
:
:
:
:
100
100
100
100
: 0 (0.00 %)
: 0 (0.00 %)
Release Information
Description
Options
view
Field Description
Linktrace to
Interface
Interface identifier.
Maintenance
domain name
Format
(Maintenance
domain)
Level
Maintenance
association name
1743
Field Description
Local Mep
Sample Output
show oam ethernet
connectivity-fault
-management
path-database
user@host> show oam ethernet connectivityfault-management path-database
maintenance-domain md1 maintenance-association ma1 00:05:85:79:39:ef
Linktrace to 00:05:85:79:39:ef, Interface : ge-3/0/0
Maintenance Domain: md1, Level: 7
Maintenance Association: ma1, Local Mep: 201
1744
Release Information
Description
Options
option is not specified, policer statistics are displayed for all maintenance associations
for all maintenance domains.
maintenance-association ma-nameName of an existing CFM maintenance association.
If this option is not specified, policer statistics are displayed for all maintenance
associations for given maintenance domain. This option cannot be specified without
specifying maintenance-domain name.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
view
Field Description
Describes the symbols used under the Scope and Type headings:
G - Global scope
S - Service scope
Maintenance Domain
Level
1745
Table 129: show oam ethernet connectivity-fault-management policer Output Fields (continued)
Field Name
Field Description
Maintenance
association
Policer
Type
Policer type. Value cc means this policer is used only to police continuity check CFM messages. Value
other means this policer is used only to police non-continuity check CFM messages. Value all means
this policer is used to police all CFM messages.
Scope
Policer scope. Displays whether the global (G) policer configuration is applicable or the session (S)
specific policer config is applicable.
Drop count
Sample Output
show oam ethernet
connectivity-fault
-management
policer
Displays the policer information for all maintenance associations and their maintenance
domains.
show oam ethernet connectivity-fault-management policer
Legend for Policer
G - Global scope
S - Service scope
cc - Continuity check
Maintenance
Maintenance
ma1
ma1-2
ma1-2
Maintenance
Maintenance
ma2
ma2
Type
all
cc
other
Type
cc
other
1746
Level: 1
Policer
cfm-policer1
cfm-policer1
cfm-policer1
Type
all
cc
other
Level: 5
Policer
Type
cfm-policer
cc
cfm-policer-2 other
1747
Release Information
Description
Options
view
Output Fields
Table 130 on page 1748 lists the output fields for the show oam ethernet
connectivity-fault-management sla-iterator-statistics command. Output fields are listed
in the approximate order in which they appear.
Maintenance domain
1748
Level
Maintenance association
Local MEP id
Remote MEP id
Iterator name
Name of iterator.
Iterator Id
Number of cycles (in milliseconds) taken between back-to-back transmission of SLA frames for
this connection
Iteration period
Iterator status
Infinite iterations
Reset reason
Delay weight
DMM sent
Delay measurement message (DMM) PDU frames sent to the peer MEP in this session.
Number of DMM frames sent to the peer MEP in this session skipped during threshold hit.
Number of DMM frames sent to the peer MEP in this session skipped during the last threshold hit
window.
DMR received
1749
Average one-way forward delay variation for the statistics displayed in microseconds.
Average one-way backward delay variation for the statistics displayed in microseconds.
Weighted average two-way delay variation for the statistics displayed in microseconds.
Weighted average one-way backward delay variation for the statistics displayed in microseconds.
Weighted average one-way forward delay variation for the statistics displayed in microseconds.
Total number of synthetic loss message (SLM) PDU frames sent from the source MEP to the
remote MEP during this ETH-SLM session.
Total number of synthetic loss message (SLM) PDU frames that the remote MEP received from
the source MEP during this ETH-SLM session.
Total number of synthetic loss reply (SLR) PDU frames that the remote MEP sent to the source
MEP during this measurement session.
Total number of synthetic loss reply (SLR) PDU frames that the source MEP received from the
remote MEP during this measurement session.
Number of synthetic frames transmitted to the peer MEP for a test ID. A test ID is used to distinguish
each synthetic loss measurement because multiple measurements can be simultaneously activated
also on a given CoS and MEP pair. It must be unique at least within the context of any SLM for the
MEG and initiating MEP.
Number of synthetic frames received from the peer MEP for a test ID. The MEP generates a unique
Test ID for the session, adds the source MEP ID, and initializes the local counters for the session
before SLM initiation. For each SLM PDU transmitted for the session (test ID), the local counter
TXFC1 is sent in the packet.
Value of the local counter TxFCl at the time of SLM frame transmission.
1750
Value of the local counter RxFCl at the time of SLR frame transmission.
Sample Output
show oam ethernet connectivity-fault
-management sla-iterator-statistics
user@switch> show oam ethernet connectivity-fault-management sla-iterator-statistics
sla-iterator i1 maintenance-domain default-1 maintenance-association ma1 local-mep 1
remote-mep 2
Iterator statistics:
Maintenance domain: md6, Level: 6
Maintenance association: ma6, Local MEP id: 1000
Remote MEP id: 103, Remote MAC address: 00:90:69:0a:43:92
Iterator name: i1, Iterator Id: 1
Iterator cycle time: 10ms, Iteration period: 1 cycles
Iterator status: running, Infinite iterations: true
Counter reset time: 2010-03-19 20:42:39 PDT (2d 18:24 ago)
Reset reason: Adjacency flap
Iterator delay measurement statistics:
Delay weight: 1, Delay variation weight: 1
DMM sent
DMM skipped for threshold hit
DMM skipped for threshold hit window
DMR received
DMR out of sequence
DMR received with invalid time stamps
Average two-way delay
Average two-way delay variation
Average one-way forward delay variation
Average one-way backward delay variation
Weighted average two-way delay
Weighted average two-way delay variation
Weighted average one-way forward delay variation
Weighted average one-way backward delay variation
:
:
:
:
:
:
:
:
:
:
:
:
:
:
23898520
11000
0
23851165
1142
36540
129 usec
15 usec
22 usec
22 usec
134 usec
8 usec
6 usec
2 usec
Sample Output
show oam ethernet connectivity-fault-management sla-iterator-statistics (MX Series routers)
user@switch> show oam ethernet connectivity-fault-management sla-iterator-statistics
maintenance-domain mdu maintenance-association mau local-mep 4 remote-mep 3 sla-iterator
lm
Iterator statistics:
Maintenance domain: 2, Level: 2
Maintenance association: W-160432000-001, Local MEP id: 2
Remote MEP id: 1, Remote MAC address: 00:90:69:0a:43:39
1751
1752
Release Information
Description
On MX Series routers with Modular Port Concentrators (MPCs) with Ethernet interfaces,
display the on-demand ETH-SLM statistics.
Options
count entry-count(Optional) Number of entries to display from the statistics table. The
Output Fields
view
1753
Field Description
MEP identifier
MAC address
Total number of synthetic loss message (SLM) PDU frames sent from the source
MEP to the remote MEP during this ETH-SLM session.
Total number of synthetic loss message (SLM) PDU frames that the remote
MEP received from the source MEP during this ETH-SLM session.
Total number of synthetic loss reply (SLR) PDU frames that the remote MEP
sent to the source MEP during this measurement session.
Total number of synthetic loss reply (SLR) PDU frames that the source MEP
received from the remote MEP during this measurement session.
Number of synthetic frames transmitted to the peer MEP for a test ID. A test ID
is used to distinguish each synthetic loss measurement because multiple
measurements can be simultaneously activated also on a given CoS and MEP
pair. It must be unique at least within the context of any SLM for the MEG and
initiating MEP.
Number of synthetic frames received from the peer MEP for a test ID. The MEP
generates a unique Test ID for the session, adds the source MEP ID, and initializes
the local counters for the session before SLM initiation. For each SLM PDU
transmitted for the session (test ID), the local counter TxFC1 is sent in the packet.
Value of the local counter TxFCl at the time of SLM frame transmission.
Value of the local counter RxFCl at the time of SLR frame transmission.
Sample Output
show oam ethernet connectivity-faultmanagement
1754
synthetic-loss-statistics
user@switch> show oam ethernet connectivity-fault-management synthetic-loss-statistics
maintenance-domain md6 maintenance-association ma6
MEP identifier: 100, MAC address: 00:05:85:73:7b:39
Remote MEP count: 2
Remote MEP identifier: 101
Remote MAC address: 00:05:85:73:39:4a
Synthetic Loss measurement statistics:
SLM packets sent
: 100
SLM packets received
: 0
SLR packets sent
: 100
SLR packets received
: 0
Accumulated SLM statistics:
Local TXFC1 value
: 100
Local RXFC1 value
: 100
Last Received SLR frame TXFCftc
: 100
Last Received SLR frame TXFCbtc
: 100
SLM Frame Loss:
Frame Loss (far-end)
: 0 (0.00 %)
Frame Loss (near-end)
: 0 (0.00 %)
1755
Release Information
Description
On MX Series routers with OAM Ethernet Virtual Connection (EVC) configurations, displays
the EVC configuration and status information.
Options
Required Privilege
Level
View
Output Fields
Table 132 on page 1756 lists the output fields for the show oam ethernet evc command.
Output fields are listed in the approximate order in which they appear.
Field Description
EVC identifier
Header for the EVC information showing the EVC name, configuration, and active/inactive status.
UNI count
Protocol
Local UNIs
UNI Identifier
Interface
Interface type-dpc/pic/port.unit-number.
Status
Sample Output
show oam ethernet evc
user@host> show oam ethernet evc
EVC identifier: evc1, Point-to-Point, Active
UNI count: Configured(2), Active(2)
Protocol: cfm, Management domain: md, Management association: ma
Local UNIs:
UNI Identifier
Interface
Status
uni1
ge-1/1/1
Operational
uni2
ge-1/1/1
Not Operational
1756
Release Information
Description
On MX Series routers with Gigabit Ethernet, Fast Ethernet, or aggregated Ethernet PICs,
displays OAM Ethernet Failure Notification Protocol (FNP) information for Ethernet
interfaces.
Options
interface only.
routing-instance-name(Optional) Display FNP for the specified routing instance.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Interface
VLAN
State
Sample Output
show oam ethernet fnp interface
user@host> show oam ethernet fnp interface
The FNP controlled interfaces are:
Interface
VLAN
State
FNP message
Interface
ge-0/0/0.30
ge-0/0/0.20
30
20
down
down
lsi.1054976
lsi.1054976
FNP message
Source MAC
a0:aa:aa:aa:aa:aa
a0:aa:aa:aa:aa:aa
1757
Release Information
Description
Options
interface only.
routing-instance-name(Optional) Display FNP messages for the specified routing
instance.
Required Privilege
Level
List of Sample Output
Output Fields
view
1758
Field Name
Field Description
Domain ID
STP Root ID
Trigger Reason
Effected VLANs
Disabled interfaces
Sample Output
show oam ethernet fnp messages
user@host> show oam ethernet fnp messages
Active FNP messages on interface lsi.1054465
Message source MAC: a0:aa:aa:aa:aa:aa
Originating port number: 141077
Time since last message: 00:00:00
Time since last message update: 00:00:00
Total messages received: 1
Domain ID: 0
STP Root ID: 0.f0:ff:ff:ff:ff:ff
Trigger reason: todo
Effected VLANs: 10
Disabled interfaces:
Interface VLAN
ge-0/0/0.10 10
1759
Release Information
Description
On MX Series routers with Gigabit Ethernet, Fast Ethernet, or aggregated Ethernet PICs,
displays OAM Ethernet Failure Notification Protocol (FNP) status.
Options
interface only.
routing-instance-name(Optional) Display FNP for the specified routing instance.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
FNP interval
Loss threshold
Interface
Domain ID
STP Root ID
FNP Messages
Sample Output
show oam ethernet fnp status
user@host> show oam ethernet status
FNP interval:
Loss threshold
FNP enabled interfaces
Interface
Domain ID
STP Root ID
1760
FNP Messages
ge-0/0/0.1278
100
0.f0:ff:ff:ff:ff:ff
1761
Release Information
Description
Options
Output Fields
view
Field Description
Level of Output
Status
All levels
Discovery state
Peer address
1762
Passive Wait
Send Any
Fault
All levels
All levels
Field Description
Level of Output
Flags
Information about the interface. Possible values are described in the Link Flags
section under Common Output Fields Description.
All levels
indicates that remote DTE has seen and is satisfied with local state
information.
local DTE has seen and is satisfied with remote state information.
Indicates the remote loopback status. An OAM entity can put its remote peer
into loopback mode using the Loopback control OAM PDU. In loopback mode,
every frame received is transmitted back on the same port (except for OAM
PDUs, which are needed to maintain the OAM session).
All levels
Remote entity
information
All levels
Remote parser actionIndicates the state of the parser function of the OAM
unsupported.
Variable Request OAM PDU, is used to request one or more MIB variables
from the remote peer.
Loopback Tracking
All levels
Loop Status
Indicates that a loopback issue is either found, not found, or unknown when
loopback tracking is enabled.
All levels
detail
1763
Field Description
Level of Output
Event
detail
Variable request
detail
Variable response
detail
Loopback control
detail
Organization
specific
detail
detail
Event
detail
Variable request
detail
Variable response
detail
Loopback control
detail
Organization
specific
detail
The number of symbol error event TLVs that have been received since the OAM
sublayer was reset.
detail
Window
detail
The protocol default value is the number of symbols that can be received in
one second on the underlying physical layer.
Threshold
The number of errored symbols in the period required for the event to be
generated.
detail
Errors in period
The number of symbol errors in the period reported in the received event PDU.
detail
Total errors
The number of errored symbols that have been reported in received event TLVs
since the OAM sublayer was reset.
detail
1764
The number of errored frame event TLVs that have been received since the
OAM sublayer was reset.
detail
Field Description
Level of Output
Window
The duration of the window in terms of the number of 100 ms period intervals.
detail
Threshold
The number of detected errored frames required for the event to be generated.
detail
Errors in period
detail
Total errors
The number of errored frames that have been reported in received event TLVs
since the OAM sublayer was reset.
detail
The number of frame seconds errors event TLVs that have been received since
the OAM sublayer was reset.
detail
Window
detail
Threshold
detail
Errors in period
detail
Total errors
The number of frame seconds errors that have been reported in received event
TLVs since the OAM sublayer was reset.
detail
The number of symbol error event TLVs that have been transmitted since the
OAM sublayer was reset.
detail
Window
detail
Threshold
The number of errored symbols in the period required for the event to be
generated.
detail
Errors in period
The number of symbol errors in the period reported in the transmitted event
PDU.
detail
Total errors
The number of errored symbols reported in event TLVs that have been
transmitted since the OAM sublayer was reset.
detail
The number of symbol error TLVs that have been generated regardless of
whether the threshold for sending event TLVs has been crossed.
detail
Window
detail
Threshold
The number of errored symbols in the period required for the event to be
generated.
detail
1765
Field Description
Level of Output
Errors in period
detail
Total errors
The number of errored symbols reported in event TLVs that have been generated
regardless of whether the threshold for sending event TLVs has been crossed.
detail
The number of errored frame event TLVs that have been transmitted since the
OAM sublayer was reset.
detail
Window
The duration of the window in terms of the number of 100 ms period intervals.
detail
Threshold
The number of detected errored frames required for the event to be generated.
detail
Errors in period
detail
Total errors
The number of errored frames that have been detected since the OAM sublayer
was reset.
detail
The number of errored frame event TLVs that have been generated regardless
of whether the threshold for sending event TLVs has been crossed.
detail
Window
The duration of the window in terms of the number of 100 ms period intervals.
detail
Threshold
The number of detected errored frames required for the event to be generated.
detail
Errors in period
detail
Total errors
detail
Sample Output
show oam ethernet link-fault-management brief
user@host> show oam ethernet link-fault-management brief
Interface: ge-3/1/3
Status: Running, Discovery state: Send Any, ISSU
Peer address: 00:90:69:72:2c:83
Flags:Remote-Stable Remote-State-Valid Local-Stable 0x50 Remote loopback status:
Disabled on local port, Enabled on peer port
Remote entity information:
Remote MUX action: discarding, Remote parser action: loopback
Discovery mode: active, Unidirectional mode: unsupported
Remote loopback mode: supported, Link events: supported
Variable requests: unsupported, Remote in ISSU
1766
1767
Options
only.
Required Privilege
Level
Output Fields
View
Table 137 on page 1768 lists the output fields for the show oam ethernet lmi command.
Output fields are listed in the approximate order in which they appear.
Field Description
Physical Interface
Header for the EVC information showing the Ethernet virtual circuit (EVC) name, configuration, and
active/inactive status.
UNI Identifier
EVC configuration.
E-LMI state
Priority/Untagged VLAN
ID
To be provided.
Default EVC
Associated EVCs
EVC Indentifier
EVC name.
1768
Field Description
Reference ID
To be provided.
Status
CE VLAN IDs
Sample Output
show oam ethernet lmi interface
user@host> show oam ethernet lmi interface ge-1/1/1
Physical interface: ge-1/1/1, Physical link is Up
UNI identifier: uni-ce1, EVC map type: Bundling
Polling verification timer: Enabled, E-LMI state: Operational
Priority/Untagged VLAN ID: 20, Default EVC: evc1
Associated EVCs:
EVC
Reference
Status
CE VLAN IDs
Identifier ID
evc1
1
Active (New)
1-2048
evc2
2
Not Active
2049-4096
1769
Options
interface only.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Physical interface
Reliability errors
Protocol errors
Sample Output
show oam ethernet lmi statistics
user@host> show oam ethernet lmi statistics interface ge-1/1/1
1770
Protocol errors
694
0
1771
Release Information
Description
Options
can be a value from 0 through 16385. The logical unit number for dynamic interfaces
can be a value from 1073741824 through the maximum number of logical interfaces
supported on your router.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
view
Field Description
Level of Output
Logical interface
All levels
Index
Index number of the logical interface, which reflects its initialization sequence.
State
All levels
Session ID
Session ID.
All levels
Type
Origin of the logical interface: Static or Dynamic. Indicates whether the interface
was statically or dynamically created.
Logical Interface
1772
Field Description
Level of Output
Service name
Configured AC
name
Session AC name
Remote MAC
address or Remote
MAC
MAC address of the remote side of the connection, either the access
concentrator or the PPPoE client.
All levels
Session uptime
Dynamic Profile
Name of the dynamic profile that was used to create this interface. If the
interface was statically created, this field is not displayed.
Underlying
interface
All levels
Agent Circuit ID
Agent circuit identifier (ACI) that corresponds to the DSLAM interface that
initiated the client service request. An asterisk is interpreted as a wildcard
character and can appear at the beginning, the end, or both the beginning and
end of the string. If the agent circuit ID is not configured, this field is not displayed.
Agent Remote ID
Agent remote identifier that corresponds to the subscriber associated with the
DSLAM interface that initiated the service request. An asterisk is interpreted as
a wildcard character and can appear at the beginning, the end, or both at the
beginning and end of the string. If the agent remote ID is not configured, this
field is not displayed.
1773
Field Description
Level of Output
Packet Type
Number of packets sent and received during the PPPoE session, categorized
by packet type and packet errors:
extensive
Service name errorPackets for which the Service-Name request could not
be honored.
error in performing the host request. For example, the host had insufficient
resources to create a virtual circuit.
Sample Output
show pppoe interfaces
user@host> show pppoe interfaces
pp0.0 Index 66
State: Down, Session ID: None,
Service name: None, Configured AC name: sapphire,
Session AC name: None, Remote MAC address: 00:00:00:00:00:00,
Auto-reconnect timeout: 100 seconds, Idle timeout: Never,
Underlying interface: at-5/0/0.0 Index 71
1774
State
Session Up
Session Up
Session Up
Session
ID
27
28
29
Remote
MAC
00:90:1A:42:0A:C1
00:90:1A:42:0A:C1
00:90:1A:42:0A:C1
pp0.1073741825
pp0.1073741826
ge-2/0/3.1
ge-2/0/3.1
Session Up
Session Up
30
31
00:90:1A:42:0A:C1
00:90:1A:42:0A:C1
show pppoe interfaces (PPPoE Subscriber Interface with ACI Interface Set)
user@host> show pppoe interfaces pp0.1073741827
pp0.1073741827 Index 346
State: Session Up, Session ID: 4, Type: Dynamic,
Service name: AGILENT, Remote MAC address: 00:00:64:39:01:02,
Session AC name: nbc,
Session uptime: 6d 02:22 ago,
Dynamic Profile: aci-vlan-pppoe-profile,
Underlying interface: demux0.1073741826 Index 345
Agent Circuit ID: aci-ppp-dhcp-dvlan-50
ACI Interface Set: aci-1002-demux0.1073741826 Index 2
1775
Release Information
Description
Options
Required Privilege
Level
Related
Documentation
Output Fields
view
Field Description
Level of Output
none
Service Name
none
<any>Default service for non-empty service entries that do not match the
Action
Action taken when the PPPoE underlying interface interface receives a PPPoE
Active Discovery Initiation (PADI) packet with the specified named service,
empty service, any service, or ACI/ARI pair:
none
Dynamic Profile
1776
Name of the dynamic profile with which the router creates a dynamic PPPoE
subscriber interface. A dynamic profile can be assigned to a named service,
empty service, any service, or ACI/ARI pair.
none
Field Description
Level of Output
Routing Instance
none
Max Sessions
Maximum number of active PPPoE sessions that the router can establish with
the specified named service, empty service, or any service.
none
Active Sessions
Current count of active PPPoE sessions created using the specified named
service, empty service, or any service. The Active Sessions value cannot exceed
the Max Sessions value.
none
ACI
Agent circuit identifier (ACI) that corresponds to the DSLAM interface that
initiated the client service request. An asterisk is interpreted as a wildcard
character and can appear at the beginning, the end, or both the beginning and
end of the string. An ACI can be configured as part of an ACI/ARI pair for a named
service, empty service, or any service.
none
ARI
none
Static Interface
Name of the static PPPoE interface reserved for exclusive use by the PPPoE
client with matching ACI/ARI information. A static interface can be configured
only for an ACI/ARI pair.
none
Sample Output
show pppoe service-name-tables
user@host> show pppoe service-name-tables
Service Name Table: test1
Service Name Table: test2
Service Name Table: test3
1777
Action: Terminate
Static Interface: pp0.101
Service Name: Wholesale
Action: Terminate
Dynamic Profile: WholesalePppoeProfile
Routing Instance: WholesaleRI
Max Sessions: 16000
Active Sessions: 4
1778
Release Information
Description
Options
established with the specified agent circuit identifier. The agent circuit identifier
corresponds to the DSLAM interface that initiated the service request.
ari remote-id-string(Optional) Display information only for active PPPoE sessions
established with the specified agent remote identifier. The agent remote identifier
corresponds to the subscriber associated with the DSLAM interface that initiated
the service request.
service service-name(Optional) Display information only for active PPPoE sessions
established with the specified service, where service-name can be empty, any, or a
named service.
Required Privilege
Level
Related
Documentation
Output Fields
view
Field Description
Level of Output
Interface
none
Underlying
interface
none
1779
Field Description
Level of Output
State
State of the PPPoE session; displays Session Up for active PPPoE sessions.
none
Session ID
none
Remote MAC
MAC address of the remote side of the connection, either the access
concentrator or the PPPoE client.
none
Sample Output
show pppoe sessions (For All Active Sessions)
user@host> show pppoe sessions
Interface
Underlying
interface
pp0.0
ge-2/0/3.2
pp0.1
ge-2/0/3.2
pp0.1073741824 ge-2/0/3.1
pp0.1073741825 ge-2/0/3.1
pp0.1073741826 ge-2/0/3.1
State
Session
Session
Session
Session
Session
Up
Up
Up
Up
Up
Session
ID
27
28
29
30
31
Remote
MAC
00:90:1A:42:0A:C1
00:90:1A:42:0A:C1
00:90:1A:42:0A:C1
00:90:1A:42:0A:C1
00:90:1A:42:0A:C1
show pppoe sessions (For All Active Sessions Matching the Agent Circuit Identifier)
user@host> show pppoe sessions aci velorum-ge-2/0/3
Interface
Underlying
State
interface
pp0.0
ge-2/0/3.2
Session Up
pp0.1
ge-2/0/3.2
Session Up
1780
Session
ID
27
28
Remote
MAC
00:90:1A:42:0A:C1
00:90:1A:42:0A:C1
Release Information
Description
Options
Required Privilege
Level
view
Related
Documentation
Output Fields
Table 142 on page 1781 lists the output fields for the show pppoe statistics command.
Output fields are listed in the approximate order in which they appear.
Field Description
Total number of active PPPoE sessions and the number of packets sent and received during the
PPPoE session, categorized by packet type and packet errors:
Service name errorPackets for which the Service-Name request could not be honored.
AC system errorPackets for which the access concentrator experienced an error in performing the
host request. For example, the host had insufficient resources to create a virtual circuit.
Malformed packetsMalformed or short packets that caused the packet handler to discard the
frame as unreadable.
1781
Field Description
Timeouts
Information about timeouts that occurred during the PPPoE session (not displayed for M120, M320,
and MX Series routers):
PADINo PADR packet has been received within the timeout period. (This value is always zero and
is not supported.)
PADONo PPPoE Active Discovery Offer packet has been received within the timeout period.
PADRNo PADS packet has been received within the timeout period.
Sample Output
show pppoe statistics
user@host> show pppoe statistics
Active PPPoE sessions: 1
PacketType
Sent
PADI
0
PADO
0
PADR
0
PADS
0
PADT
0
Service name error
0
AC system error
0
Generic error
0
Malformed packets
0
Unknown packets
0
Timeouts
PADI
0
PADO
0
PADR
0
Received
0
0
0
0
0
0
0
0
0
0
1782
Received
5
0
5
0
1
0
0
0
0
0
Release Information
Description
Options
lockout grace period for PPPoE clients on the PPPoE underlying interface.
logical-interface-name(Optional) Name of a PPPoE underlying logical interface.
Required Privilege
Level
Related
Documentation
Output Fields
view
Field Description
Level of Output
Underlying
Interface
All levels
Service Name
Table
All levels
1783
Field Description
Level of Output
Dynamic Profile
Name of the dynamic profile that was used to create this interface. If the
interface was statically created, then the value is none.
All levels
Index
Index number of the logical interface, which reflects its initialization sequence.
detail extensive
State
Origin of the logical interface: Static or Dynamic. Indicates whether the interface
was statically or dynamically created.
detail extensive
Operational States
Fields in this block are actual operational values rather than simply the
configured values. The operational values can be the result of RADIUS-initiated
changes.
detail extensive
Max Sessions
detail extensive
Whether the router is configured to ignore (clear) the PPPoE maximum session
value returned by RADIUS in the Max-Clients-Per-Interface Juniper Networks
VSA [26-143] and restore the PPPoE maximum session value on the underlying
interface to the value configure with the max-sessions statement: Off (default)
or On.
Active Sessions
detail extensive
Agent Circuit
Identifier
Duplicate
Protection
detail extensive
Short Cycle
Protection
detail extensive
Direct Connect
State of the configuration to ignore DSL Forum VSAs: On or Off. When configured,
the router ignores any of these VSAs received from a directly connected CPE
device on the interface.
1784
Field Description
Level of Output
AC Name
detail extensive
PacketType
Number of packets sent and received during the PPPoE session, categorized
by packet type and packet errors:
extensive
Service name errorPackets for which the Service-Name request could not
be honored.
error in performing the host request. For example, the host had insufficient
resources to create a virtual circuit.
The PPPoE lockout time range, the number of PPPoE clients in lockout condition,
and the number of PPPoE clients in a lockout grace period if Short Cycle
Protection is enabled (On):
extensive
interface.
interface.
lockout grace period. A lockout grace period occurs when the time between
lockout events is greater than either 15 minutes or the maximum lockout time.
Client Address
extensive
Current
Current lockout time, in seconds; displays 0 (zero) if the PPPoE client is not
undergoing lockout.
extensive
Elapsed
Time elapsed into the lockout period, in seconds; displays 0zero) if the PPPoE
client is not undergoing lockout
extensive
Next
Lockout time, in seconds, that the router uses for the next lockout event; displays
a nonzero value if the PPPoE client is currently in a lockout grace period.
extensive
Sample Output
show pppoe underlying-interfaces brief
user@host> show pppoe underlying-interfaces brief
1785
Underlying Interface
ge-4/0/3.1
ge-4/0/3.2
Dynamic Profile
None
PppoeProfile
Sent
Received
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
ge-4/0/3.2 Index 78
Operational States:
State: Dynamic, Dynamic Profile: PppoeProfile,
Max Sessions: 4000, Max Sessions VSA Ignore: Off
Active Sessions: 3,
Service Name Table: None,
Direct Connect: Off,
1786
Sent
0
5
0
4
0
0
0
0
0
0
Received
5
0
5
0
1
0
0
0
0
0
Sent
0
3
0
3
2
0
0
0
0
0
Received
7
0
3
0
1
0
0
0
0
0
Current
4
Elapsed
3
Next
8
show pppoe underlying-interfaces detail (Autosensing Configured for ACI-based Dynamic VLANs)
user@host> show pppoe underlying-interfaces demux0.1073741826 detail
demux0.1073741826 Index 345
State: Dynamic, Dynamic Profile: aci-vlan-pppoe-profile,
Max Sessions: 32000, Max Sessions VSA Ignore: Off,
Active Sessions: 1,
1787
1788
Field Description
version n
PPPoE version number and RFC. For example, version 1, rfc 2516.
PPPoE protocol
Maximum Sessions
Maximum active sessions supported per router. The default is 256 sessions.
Initial time, in seconds, that the router waits to receive a PPoE Active Discovery Offer (PADO) packet
for the PPoE Active Discovery Initiation (PADI) packet sent. This timeout doubles for each successive
PADI packet sent. Not displayed for M120 and M320 routers.
Initial time, in seconds, that the router waits to receive a PPoE Active Discovery Session Confirmation
(PADS) packet for the PPoE Active Discovery Request (PADR) packet sent. This timeout doubles for
each successive PADR packet sent. Not displayed for M120 and M320 routers.
Maximum value, in seconds, that the PADI or PADR resend timer can accept. The maximum value is
64. Not displayed for M120 and M320 routers.
Max Configured AC
timeout
Time, in seconds, during which the configured access concentrator must respond. Not displayed for
M120 and M320 routers.
Sample Output
show pppoe version
user@host> show pppoe version
Point-to-Point Protocol Over Ethernet, version 1. rfc2516
PPPoE protocol
= Enabled
Maximum Sessions
= 256
PADI resend timeout
= 2 seconds
PADR resend timeout
= 16 seconds
1789
1790
= 64 seconds
= 4 seconds
Description
Options
Required Privilege
Level
Related
Documentation
Output Fields
Table 145 on page 1791 lists the output fields for the show protection-group ethernet-ring
aps command. Output fields are listed in the approximate order in which they appear.
Field Description
Ethernet Ring
1791
Field Description
Request/State
the ring.
in the ring.
NOTE: Both FS and MS values are valid only when G.8032v2 is
supported.
Ring Protection Link Blocked
No Flush
Indicates the value of the Do Not Flush (DNF) flag in the received
RAPS PDU. If the value is Yes, then FDB flush is not triggered
as part of processing of the received RAPS PDU.
Originator
Remote Node ID
Sample Output
show protection-group ethernet-ring aps (EX Switches)
user@switch>show protection-group ethernet-ring aps
Ring Name
Request/state No Flush RPL Blocked
erp1
NR
No
Yes
Originator
No
Remote Node ID
00:1F:12:30:B8:81
Sample Output
show protection-group ethernet-ring aps (MX RPL Owner Node, Ring in IDLE state)
user@host>show protection-group ethernet-ring aps
Ethernet Ring
Request/state RPL Blocked
No Flush
pg_major
NR
Yes
Yes
Originator
Yes
1792
BPR
0
Remote Node ID
NA
show protection-group ethernet-ring aps (MX Ring Node, Ring in IDLE state)
user@host>show protection-group ethernet-ring aps
Ethernet Ring
Request/state
RPL Blocked No Flush
pg102
NR
Yes
Yes
Originator
No
Remote Node ID
00:01:01:00:00:01
show protection-group ethernet-ring aps (MX RPL Owner Ring Node, Failure condition on non-RPL link of the
ring)
user@host>show protection-group ethernet-ring aps
Ethernet Ring
Request/state
RPL Blocked No Flush
pg101
SF
No
No
Originator
No
Remote Node ID
00:01:02:00:00:01
show protection-group ethernet-ring aps (MX Interconnection Ring Node, Failure condition in major ring on
non-RPL link of the ring)
user@host>show protection-group ethernet-ring aps
Ethernet Ring
Request/state RPL Blocked No Flush
pg_major
SF
No
No
pg_subring
NR
Yes
Yes
Originator
No
No
BPR
0
0
Remote Node ID
00:01:00:00:00:01
00:02:00:00:00:02
Yes
Yes
BPR
Originator
Remote
Yes
NA
No
:
:
:
:
:
:
:
Inst_Vlans_16-30
NR
Yes
Yes
0
No
00:00:00:03:00:02
1793
show protection-group ethernet-ring aps (MX Interconnection Ring Node as RPL owner of major ring, rings in
IDLE state)
user@host>show protection-group ethernet-ring aps detail
1794
Ethernet-Ring name
Request/State
Ring Protection Link blocked
No Flush Flag
Blocked Port Reference
Originator
Remote Node ID
:
:
:
:
:
:
:
pg_major
NR
Yes
Yes
0
Yes
NA
Ethernet-Ring name
Request/State
Ring Protection Link blocked
No Flush Flag
Blocked Port Reference
Originator
Remote Node ID
:
:
:
:
:
:
:
pg_subring
NR
Yes
Yes
0
No
00:00:03:00:00:03
Description
Required Privilege
Level
Related
Documentation
Output Fields
Table 146 on page 1795 lists the output fields for the show protection-group ethernet-ring
configuration command. Output fields are listed in the approximate order in which they
appear.
Field Description
G8032 Compatability
Version
This is the compatibility version mode of ERP. This parameter always takes the
value 1 in the case of G8032v1. This parameter is valid only for MX Series routers.
East Interface
One of the two switch interfaces that participates in a ring link. When Junos
supports G8032v2, this interface is treated as interface 0.
West Interface
One of the two interfaces in a switch that participates in a ring link. When Junos
supports G8032v2, this interface is treated as interface 1.
1795
Field Description
Restore Interval
Configured interval of wait time after a link is restored. When a link goes down,
the RPL link is activated. When the down link becomes active again, the RPL
owner receives a notification. The RPL owner waits for the restore interval before
issuing a block on the RPL link. The configured restore interval can be 5 through
12 minutes for ERPv1 and 1 through 12 minutes for ERPv2. This configuration is
a global configuration and applies to all Ethernet rings if the Ethernet ring does
not have a more specific configuration for this value. If no parameter is configured
at the protection group level, the global configuration of this parameter uses
the default value.
Configured interval of wait time for link restoration when a manual command
(manual switch or force switch) is cleared. On clearing the manual command,
the RPL owner receives NR messages, which starts a timer with interval Wait
to Block to restore the RPL link after its expiration. This delay timer is set to be
5 seconds longer than the guard timer. The configured number can be from 5
seconds through 10 seconds. The parameter is valid only for G.8032v2.
Guard Interval
This is the interval at which the link is held down even before declaring that the
link is down. Because the parameter is not supported at present, its value is
always considered 0. This parameter is valid only for MX Series routers.
Node ID
Node ID for the switch or router. If the node ID is not configured, it is assigned
by default. For EX Series switches, the Node ID value cannot be configured,
whereas for MX Series routers, it can be configured..
Ring ID
In G8032v2, the ring ID can be within the range 1239. All the nodes in a ring
should have the same ring ID. In the case of G8032v1, the value of the ring ID is
always 1. This parameter is valid only for MX Series routers.
Node Role
Revertive Mode of
Operation
The RAPS Tx Dot1p priority is a parameter with which the RAPS is transmitted
from the ring node. For G8032v1, the value of this parameter is always 0. For
G8032v2, the value of this parameter can be within the range 07. This
parameter is valid only for MX Series routers.
1796
Field Description
Node type
Indicates whether ring node is a normal ring node having two ring-links or a open
ring-node having only a single ring-link or a interconnection ring-node. An
interconnection ring node can be connected to major ring in non virtual-channel
mode or in virtual channel mode. Ring interconnection is not supported for
G8032v1. This parameter is valid only for MX Series routers.
If the node type is interconnection in the ring, this parameter takes the name of
the major ring to which the sub-ring node is connected. This parameter is valid
only for MX Series routers.
Interconnection mode
Propagate Topology
Change event
When Propagate Topology Change event is set to 1, the change in the topology
of sub-ring is propagated to the major ring, enabling the transmission of EVENT
FLUSH RAPS PDU in the major ring. When the parameter is set to 0, the topology
change in the sub-ring is not propagated to the major ring blocking EVENT
FLUSH RAPS PDU transmission in the major ring. This parameter is valid only
for MX Series routers.
Control Vlan
The VLAN that transfers ERP PDUs from one node to another.
Physical Ring
Physical ring if the east and west interfaces are nontrunk ports. For MX Series
routers, the ring is termed a physical ring if no data channels are defined for the
ring and the entire physical port forwarding is controlled by ERP.
Data VLANs for which forwarding behavior is controlled by the ring instance.
Sample Output
show protection-group ethernet-ring configuration (EX Switch)
user@switch>show protection-group ethernet-ring configuration
Ethernet ring configuration parameters for protection group erp1
East Interface
: ge-0/0/3.0
West Interface
: ge-0/0/9.0
Restore Interval : 5 minutes
Guard Interval
: 500 ms
Node Id
: 00:1F:12:30:B8:81
Control Vlan
: 101
Physical Ring
: yes
1797
:
:
:
:
:
:
:
:
:
:
:
:
5 seconds
500 ms
0 ms
64:87:88:65:37:D0
1
normal
1
0
Normal
100
No
200,300
1798
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
xe-2/3/0.1
(no erp)
5 minutes
5 seconds
500 ms
0 ms
64:87:88:65:37:D0
1
rpl-owner
east-port
1
0
Open
100
No
200,300
1799
1800
Release Information
Description
Options
optional field, all protection group statistics for configured groups will be displayed.
Required Privilege
Level
Related
Documentation
Output Fields
view
Field Description
Interface
STP index
1801
Field Description
Forward State
Sample Output
show protection-group ethernet-ring data-channel
user@host> show protection-group ethernet-ring data-channel
Ethernet ring data channel information for protection group pg301
Interface
xe-5/0/2
xe-2/2/0
STP index
78
79
Forward State
forwarding
discarding
STP index
80
81
Forward State
forwarding
forwarding
: xe-5/0/2
: 78
: forwarding
Interface name
STP index
Forward State
: xe-2/2/0
: 79
: discarding
1802
Interface name
STP index
Forward State
: xe-5/0/2
: 80
: forwarding
Interface name
STP index
Forward State
: xe-2/2/0
: 81
: forwarding
Output Fields
Table 148 on page 1803 lists the output fields for the show protection-group ethernet-ring
flush-info command. Output fields are listed in the approximate order in which they
appear.
Field Description
Interface
Originating Node
Sample Output
show protection-group ethernet-ring flush-info (MX Series Router)
user@host> show protection-group ethernet-ring flush-info
Ethernet ring flush port information for protection group pg100
Interface
Originating Node
xe-5/0/2.4001 00:00:00:00:00:00
xe-2/2/0.4001 00:00:00:00:00:00
1803
1804
Interface name
Originating Node
Blocked Port Reference
: xe-5/0/2.4001
: 00:00:00:00:00:00
: 0
Interface name
Originating Node
Blocked Port Reference
: xe-2/2/0.4001
: 00:00:00:00:00:00
: 0
Options
Required Privilege
Level
Related
Documentation
Output Fields
Table 149 on page 1805 lists the output fields for both the EX Series switch and the MX
Series router show protection-group ethernet-ring interface commands. Output fields are
listed in the approximate order in which they appear.
Field Description
Interface
Control Channel
Forward State
1805
Field Description
Signal Failure
Admin State
Sample Output
show protection-group ethernet-ring interface (EX Series Switch Owner Node)
user@host> show protection-group ethernet-ring interface
Ethernet ring port parameters for protection group pg101
Interface
Forward State
RPL End
ge-0/0/3.0
ge-0/0/9.0
discarding
forwarding
Yes
No
Signal Failure
Admin State
Clear
Clear
ready
ready
Control Channel
ge-1/2/0.100
ge-1/2/2.100
Direction
east
west
Forward State
forwarding
forwarding
RPL End
No
No
SF
Admin State
Clear IFF ready
Clear IFF ready
:
:
:
:
:
:
:
ge-1/2/0
ge-1/2/0.100
east
No
Clear
forwarding
IFF ready
Interface name
Control channel name
Interface direction
Ring Protection Link End
Signal Failure
Forward State
Interface Admin State
:
:
:
:
:
:
:
ge-1/2/2
ge-1/2/2.100
west
No
Clear
forwarding
IFF ready
1806
Forward State
RPL End
ge-0/0/3.0
ge-0/0/9.0
discarding
forwarding
Yes
No
Signal Failure
Admin State
Clear
Clear
ready
ready
Control Channel
ge-1/2/1.1
ge-1/0/2.1
Forward State
forwarding
forwarding
RPL End
No
No
1807
Description
Options
Required Privilege
Level
Related
Documentation
show protection-group ethernet-ring node-state (MX Series Router - RPL Owner Node,
Normal Operation) on page 1810
show protection-group ethernet-ring node-state (MX Series Router - Normal Ring
Node, Normal Operation) on page 1810
show protection-group ethernet-ring node-state (MX Series Router - RPL Owner Node,
Remote Failure Condition) on page 1810
show protection-group ethernet-ring node-state (MX Series Router - Owner Node,
Local Failure Condition) on page 1810
show protection-group ethernet-ring node-state detail (MX Series Routers - Node
state at RPL-owner after signal failure condition is cleared in the ring and before
reversion) on page 1810
show protection-group ethernet-ring node-state detail (MX Series Router - RPL Owner
Node, Normal Operation) on page 1810
Output Fields
Table 150 on page 1808 lists the output fields for the show protection-group ethernet-ring
node-state command. Output fields are listed in the approximate order in which they
appear.
1808
Field Name
Field Description
Field Description
APS State
ring.
ring.
Event
active on one or more ring links of any other node of the ring.
Guard Timer
Op State / Operational
State
1809
Sample Output
show protection-group ethernet-ring node-state (MX Series Router - RPL Owner Node, Normal Operation)
user@host> show protection-group ethernet-ring node-state
Ethernet ring
APS State Event
RPL Owner WTR Timer
Timer Operation state
pg101
idle
NR-RB
Yes
disabled
operational
pg102
idle
NR-RB
No
disabled
operational
WTB Timer
Guard
disabled
disabled
disabled
disabled
show protection-group ethernet-ring node-state (MX Series Router - Normal Ring Node, Normal Operation)
user@host> show protection-group ethernet-ring node-state
Ethernet ring
APS State
Event
RPL Owner
pg102
idle
NR-RB
No
WTR Timer
disabled
WTB Timer
disabled
Guard Timer
disabled
Operation state
operational
show protection-group ethernet-ring node-state (MX Series Router - RPL Owner Node, Remote Failure Condition)
user@host> show protection-group ethernet-ring node-state
Ethernet ring
APS State
Event
RPL Owner
pg101
protected
remote SF
Yes
WTR Timer
disabled
Operation state
operational
show protection-group ethernet-ring node-state (MX Series Router - Owner Node, Local Failure Condition)
user@host> show protection-group ethernet-ring node-state
Ethernet ring
APS State
Event
RPL Owner
pg102
protected
local SF
No
WTR Timer
disabled
WTB Timer
disabled
Guard Timer
disabled
Operation state
dperational
show protection-group ethernet-ring node-state detail (MX Series Routers - Node state at RPL-owner after
signal failure condition is cleared in the ring and before reversion)
user@host> show protection-group ethernet-ring node-state detail
Ethernet-Ring name
APS State
Event
Ring Protection Link Owner
Wait to Restore Timer
Wait to Block Timer
Guard Timer
Operation state
:
:
:
:
:
:
:
:
pg_major
pending
WTR running
Yes
running (time to expire: 269 sec)
disabled
disabled
operational
show protection-group ethernet-ring node-state detail (MX Series Router - RPL Owner Node, Normal Operation)
user@host> show protection-group ethernet-ring node-state detail
Ethernet-Ring name
: pg101
APS State
: idle
Event
: NR-RB
Ring Protection Link Owner
: Yes
Wait to Restore Timer
: disabled
1810
: disabled
: disabled
: operational
Ethernet-Ring name
APS State
Event
Ring Protection Link Owner
Wait to Restore Timer
Wait to Block Timer
Guard Timer
Operation state
:
:
:
:
:
:
:
:
pg102
idle
NR-RB
No
disabled
disabled
disabled
operational
1811
Release Information
Description
Options
group-nameDisplay statistics for the protection group. If you omit this option, protection
Required Privilege
Level
Related
Documentation
Output Fields
view
1812
Field Name
Field Description
Field Description
Local SF
Remote SF
NR event
NR event sent
NR event received
NR-RB event
Table 152 on page 1814 lists the output fields for the show protection-group ethernet-ring
statistics command when the detail option is used. These fields are valid only for MX
Series routers.
1813
Field Description
Sample Output
show protection-group ethernet-ring statistics (EX Series Switch)
user@switch> show protection-group ethernet-ring statistics
Ring Name Local SF Remote SF NR Event NR-RB Event
erp1
2
1
2
3
1814
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
1
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1815
Release Information
Description
Options
interfaces, vlan, and bridge-domain. If you omit this optional field, details for all
configured protection groups will be displayed.
Required Privilege
Level
Related
Documentation
Output Fields
view
1816
Field Name
Field Description
Interface
Vlan
Name of the VLAN associated with the interface configured for the
Ethernet protection ring.
STP index
Field Description
Bridge Domain
Sample Output
show protection-group ethernet-ring vlan
user@host> show protection-group ethernet-ring vlan
Ethernet ring IFBD parameters for protection group vkm01
Interface
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
Vlan
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
8
9
9
10
10
11
11
12
12
13
13
14
14
15
15
STP Index
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
Bridge Domain
default-switch/bd1
default-switch/bd1
default-switch/bd2
default-switch/bd2
default-switch/bd3
default-switch/bd3
default-switch/bd4
default-switch/bd4
default-switch/bd5
default-switch/bd5
default-switch/bd6
default-switch/bd6
default-switch/bd7
default-switch/bd7
default-switch/bd8
default-switch/bd8
default-switch/bd9
default-switch/bd9
default-switch/bd10
default-switch/bd10
default-switch/bd11
default-switch/bd11
default-switch/bd12
default-switch/bd12
default-switch/bd13
default-switch/bd13
default-switch/bd14
default-switch/bd14
default-switch/bd15
default-switch/bd15
Vlan
1
1
2
2
3
3
STP Index
78
79
78
79
78
79
Bridge Domain
default-switch/bd1
default-switch/bd1
default-switch/bd2
default-switch/bd2
default-switch/bd3
default-switch/bd3
1817
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
4
4
5
5
6
6
7
7
8
8
9
9
10
10
11
11
12
12
13
13
14
14
15
15
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
78
79
default-switch/bd4
default-switch/bd4
default-switch/bd5
default-switch/bd5
default-switch/bd6
default-switch/bd6
default-switch/bd7
default-switch/bd7
default-switch/bd8
default-switch/bd8
default-switch/bd9
default-switch/bd9
default-switch/bd10
default-switch/bd10
default-switch/bd11
default-switch/bd11
default-switch/bd12
default-switch/bd12
default-switch/bd13
default-switch/bd13
default-switch/bd14
default-switch/bd14
default-switch/bd15
default-switch/bd15
:
:
:
:
xe-5/0/2
1
78
default-switch/bd1
Interface name
Vlan
STP index
Bridge Domain
:
:
:
:
xe-2/2/0
1
79
default-switch/bd1
Interface name
Vlan
STP index
Bridge Domain
:
:
:
:
xe-5/0/2
2
78
default-switch/bd2
Interface name
Vlan
STP index
Bridge Domain
:
:
:
:
xe-2/2/0
2
79
default-switch/bd2
Interface name
Vlan
STP index
Bridge Domain
:
:
:
:
xe-5/0/2
3
78
default-switch/bd3
1818
Interface
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
xe-5/0/2
xe-2/2/0
Vlan
16
16
17
17
18
18
19
19
20
20
21
21
22
22
23
23
24
24
25
25
26
26
27
27
28
28
29
29
30
30
STP Index
80
81
80
81
80
81
80
81
80
81
80
81
80
81
80
81
80
81
80
81
80
81
80
81
80
81
80
81
80
81
Bridge Domain
default-switch/bd16
default-switch/bd16
default-switch/bd17
default-switch/bd17
default-switch/bd18
default-switch/bd18
default-switch/bd19
default-switch/bd19
default-switch/bd20
default-switch/bd20
default-switch/bd21
default-switch/bd21
default-switch/bd22
default-switch/bd22
default-switch/bd23
default-switch/bd23
default-switch/bd24
default-switch/bd24
default-switch/bd25
default-switch/bd25
default-switch/bd26
default-switch/bd26
default-switch/bd27
default-switch/bd27
default-switch/bd28
default-switch/bd28
default-switch/bd29
default-switch/bd29
default-switch/bd30
default-switch/bd30
1819
Release Information
Description
Options
Command introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Display the status of the active MACsec connections on the router.
noneDisplay MACsec connection information for all interfaces on the switch.
interface interface-name(Optional) Display MACsec connection information for the
view
Field Description
CA name
Cipher suite
Encryption
Encryption setting. Encryption is enabled when this output is on and disabled when this
output is off.
The encryption setting is set using the no-encryption statement in the connectivity
association when using static connectivity association key (CAK) security mode and is
set using the encryption statement in the secure channel when using static secure
association key (SAK) or dynamic security mode.
Offset setting.
The offset is set using the offset statement when configuring the connectivity association
when using static connectivity association key (CAK) or dynamic security mode or the
secure channel when using static secure association key (SAK) security mode.
1820
Field Description
Include SCI
SCI tagging. The SCI tag is included on packets in a secure channel when this output is
yes, and not included on packets in a secure channel when this output is no.
SCI tagging is automatically enabled on EX4300 switch interfaces that have enabled
MACsec using static connectivity association key (CAK) or dynamic security mode. You
can enable SCI tagging using the include-sci statement in the connectivity association.
Replay protection setting. Replay protection is enabled when this output is on and disabled
when this output is off.
Replay protect
You can enable replay protection using the replay-protect statement in the connectivity
association.
Replay protection window setting. This output is set to 0 when replay protection is
disabled, and is the size of the replay window, in number of packets, when replay
protection is enabled.
Replay window
The size of the replay window is configured using the replay-window-size statement in
the connectivity association.
Sample Output
show security macsec connections
user@host> show security macsec connections
Interface name: xe-0/1/0
CA name: CA1
Cipher suite: GCM-AES-128
Encryption: on
Key server offset: 0
Include SCI: no
Replay protect: off
Replay window: 0
1821
Release Information
Description
Options
Command introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Display Media Access Control Security (MACsec) statistics.
noneDisplay MACsec statistics in brief form for all interfaces on the router.
brief | detail(Optional) Display the specified level of output. Using the brief option is
equivalent to entering the command with no options (the default). The detail option
displays additional fields that are not visible in the brief output.
NOTE: The field names that only appear in this command output when
you enter the detail option are mostly useful for debugging purposes by
Juniper Networks support personnel.
only.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Level of Output
Interface name
All levels
All levels
1822
Field Description
Level of Output
Encrypted bytes
All levels
All levels
All levels
All levels
All levels
All levels
All levels
1823
Field Description
Level of Output
Decrypted bytes
All levels
All levels
All levels
All levels
Sample Output
show security macsec statistics interface xe-0/1/0 detail
user@host> show security macsec statistics interface xe-0/1/0 detail
Interface name: xe-0/1/0
Secure Channel transmitted
Encrypted packets: 123858
Encrypted bytes:
32190903
Protected packets: 0
Protected bytes:
0
Secure Association transmitted
Encrypted packets: 123858
Protected packets: 0
Secure Channel received
Accepted packets: 123877
Validated bytes:
0
Decrypted bytes:
32196238
Secure Association received
Accepted packets: 123877
1824
Validated bytes:
0
Decrypted bytes:
32196238
Error and debug
Secure Channel transmitted packets
Untagged: 0, Too long: 0
Secure Channel received packets
Control: 0, Tagged miss: 3202804
Untagged hit: 0, Untagged: 0
No tag: 0, Bad tag: 0
Unknown SCI: 0, No SCI: 0
Control pass: 0, Control drop: 0
Uncontrol pass: 123877, Uncontrol drop: 0
Hit dropped: 0, Invalid accept: 0
Late drop: 0, Delayed accept: 0
Unchecked: 0, Not valid drop: 0
Not using SA drop: 0, Unused SA accept: 0
1825
Release Information
Description
Options
Command introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Display MACsec Key Agreement (MKA) session information.
view
Field Description
Interface name
Member identifier
CAK name
Transmit interval
Outbound SCI
Message number
Key number
Key number.
Key server
Latest SAK AN
Latest SAK KI
1826
Field Description
Hold time
Message number
SCI
Lowest acceptable PN
Sample Output
show security mka sessions
user@host> show security mka sessions
Interface name: xe-0/1/0
Member identifier: 0CCBEE42F8778300F8D0C1DC
CAK name: 1234567890
Transmit interval: 2000(ms)
Outbound SCI: 2C:6B:F5:9D:4B:1B/1
Message number: 1526465
Key number: 0
Key server: no
Key server priority: 15
Latest SAK AN: 0
Latest SAK KI: 4F18CE25228178FD15976E4C/1
Previous SAK AN: 0
Previous SAK KI: 000000000000000000000000/0
Peer list
1. Member identifier: 4F18CE25228178FD15976E4C (live)
Message number: 1526484 Hold time: 14500 (ms)
SCI: 2C:6B:F5:9D:3A:1B/1
Lowest acceptable PN: 121198
1827
Release Information
Description
Command introduced in Junos OS Release 15.1 for MX240, MX480, and MX960 routers.
Display MACsec Key Agreement (MKA) protocol statistics.
The output for this command does not include statistics for MACsec data traffic. For
MACsec data traffic statistics, see show security macsec statistics.
Options
interface only.
Required Privilege
Level
List of Sample Output
Output Fields
view
Field Description
Received packets
Transmitted packets
1828
Field Description
Sample Output
show security mka statistics
user@host> show security mka statistics
Received packets:
Transmitted packets:
Version mismatch packets:
CAK mismatch packets:
ICV mismatch packets:
Duplicate message identifier packets:
Duplicate message number packets:
Duplicate address packets:
Invalid destination address packets:
Formatting error packets:
Old Replayed message number packets:
1525844
1525841
0
0
0
0
0
0
0
0
0
1829
show vrrp
Syntax
Release Information
Description
Options
show vrrp
<brief | detail | extensive | summary>
<interface interface-name <group number>>
<logical-system (all | logical-system-name )>
<nsr>
<track <interfaces>>
about the specified VRRP interface and, optionally, the group number.
logical-system (all | logical-system-name)(Optional) Perform this operation on all logical
switchover (GRES) with nonstop active routing (NSR) is configured. Use only on the
backup Routing Engine.
track <interfaces>(Optional) Display information and status about VRRP track
interfaces.
Required Privilege
Level
Related
Documentation
List of Sample Output
Output Fields
1830
view
clear vrrp
Field Description
Level of Output
Interface
Interface index
extensive
Groups
extensive
Active
Total number of VRRP groups that are active (that is, whose interface state is
either up or down).
extensive
Interface VRRP
PDU statistics
extensive
the interface.
interface.
extensive
Invalid IPAH next type receivedNumber of packets received that use the IP
version is not 2.
count exceeds 8.
detail extensive
Unit
All levels
Address
none
Index
detail extensive
SNMP ifIndex
detail extensive
1831
Field Description
Level of Output
VRRP-Traps
detail extensive
VRRP-Version
VRRP version: 2 or 3.
detail extensive
Interface state or
Int state
unknownThe VRRP process has not had time to query the kernel about the
Group
State
extensive
bringupVRRP is just starting and the physical device is not yet present.
idleVRRP is configured on the interface and is disabled. This can occur when
initVRRP is initializing.
software upgrade.
If the interface inherits its state and configuration from the active VRRP group,
or if it is part of the active VRRP group.
detail extensive
Priority
detail extensive
Advertisement
interval
detail extensive
Authentication type
detail extensive
1832
Field Description
Level of Output
Advertisement
Threshold
A value from 1 through 15, used for setting the time when a peer should be
considered down.
detail extensive
Computed Send
Rate
How many protocol data units (PDUs) are generated per second.
detail extensive
detail extensive
Accept-data mode
Whether the interface is configured to accept packets destined for the virtual
IP address: yes or no.
detail extensive
VIP count
detail extensive
VIP
detail extensive
Advertisement
timer
detail extensive
Master router
IP address of the interface that is acting as the master. If the VRRP interface is
down, the output is N/A.
detail extensive
Virtual router
uptime
How long, in seconds, that the virtual router has been up.
detail extensive
Master router
uptime
How long, in seconds, that the master route has been up.
detail extensive
Virtual MAC
detail extensive
Tracking
detail extensive
Current priority
detail extensive
Configured priority
detail extensive
Priority hold-time
detail extensive
Remaining-time
(track option only) Displays the time remaining in the priority hold-time interval.
detail
Interface tracking
detail extensive
1833
Field Description
Level of Output
Interface/Tracked
interface
detail extensive
Int state/Interface
state
detail extensive
Int speed/Speed
detail extensive
Incurred priority
cost
Operational priority cost incurred due to the state and speed of this tracked
interface. This cost is applied to the configured priority to obtain the current
priority.
detail extensive
Threshold
Speed below which the corresponding priority cost is incurred. In other words,
when the speed of the interface drops below the threshold speed, the
corresponding priority cost is incurred.
detail extensive
An entry of down means that the corresponding priority cost is incurred when
the interface is down.
Route tracking
Whether route tracking is enabled or disabled. When enabled, the output also
displays the number of tracked routes.
detail extensive
Route count
detail extensive
Route
detail extensive
VRF name
The VPN routing and forwarding (VRF) routing instance that the tracked route
is in.
detail extensive
Route state
detail extensive
Priority cost
Configured priority cost. This value is incurred when the interface speed drops
below the corresponding threshold or when the tracked route goes down.
detail extensive
Active
Whether the threshold is active (*). If the threshold is active, the corresponding
priority cost is incurred.
detail extensive
extensive
1834
Field Description
Level of Output
extensive
(password). The password for simple authentication must be the same for
all routers in the VRRP group
Bad MD5 digest receivedNumber of VRRP PDUs received for which the MD5
digest computed from the VRRP PDU differs from the digest expected by the
VRRP instance configured on the router.
advertisement time interval that is inconsistent with the one in use among
the routers in the VRRP group.
counts differ from the count that has been configured on the VRRP instance.
differ from the list of virtual IP addresses configured on the VRRP instance.
Group state
transition statistics
extensive
bringupVRRP is just starting, and the physical device is not yet present.
idleVRRP is configured on the interface and is disabled. This can occur when
initVRRP is initializing.
1835
Field Description
Level of Output
NSR
VRRP nonstop active routing is enabled for the configured VRRP group: yes or
no.
brief none
NOTE: A yes value means that the new master Routing Engine will immediately
start with the VRRP State value from the original master Routing Engine.
A no value means that the VRRP session will:
Start afresh.
Wait for the D Timer to run out before becoming the master (only if the master
has not been configured already).
RPD-NSR
The routing options have been set to nonstop active routing: yes or no.
brief none
Timer
brief none
Sample Output
show vrrp
user@host> show vrrp
Interface
State
fe-0/0/0.121
up
fe-0/0/2.131
up
Group
1
VR state
master
master
Timer
A 1.052
A 0.364
Type
lcl
Address
fec0::12:1:1:1
vip
fe80::12:1:1:99
vip
lcl
fec0::12:1:1:99
fec0::13:1:1:1
vip
fe80::13:1:1:99
vip
fec0::13:1:1:99
1836
fec0::12:1:1:99
Advertisement timer: 1.121s, Master router: fe80::12:1:1:1
Virtual router uptime: 00:03:47, Master router uptime: 00:03:41
Virtual MAC: 00:00:5e:00:02:01
Tracking: disabled
Physical interface: fe-0/0/2, Unit: 131, Vlan-id: 213, Address: fec0::13:1:1:1/120
Index: 69, SNMP ifIndex: 47, VRRP-Traps: enabled
Interface state: up, Group: 1, State: master
Priority: 200, Advertisement interval: 1, Authentication type: none
Preempt: yes, Accept-data mode: no, VIP count: 2, VIP: fe80::13:1:1:99,
fec0::13:1:1:99
Advertisement timer: 0.327s, Master router: fe80::13:1:1:1
Virtual router uptime: 00:03:47, Master router uptime: 00:03:41
Virtual MAC: 00:00:5e:00:02:01
Tracking: disabled
1837
Invalid
Invalid
Invalid
Invalid
Invalid
Invalid
VRRP
VRRP
VRRP
VRRP
VRRP
VRRP
1838
VR state
master
VR Mode
Active
Type
lcl
NSR
yes
RPD-NSR
yes
vip
ge-1/0/1.0
up
master
Active
lcl
10.0.0.3
yes
yes
vip
ge-1/0/1.0
up
master
Active
lcl
up
master
Active
lcl
yes
yes
up
master
Active
lcl
30.0.0.1
30.0.0.3
yes
yes
vip
ge-1/0/1.0
20.0.0.1
20.0.0.3
vip
ge-1/0/1.0
Address
10.0.0.1
40.0.0.1
40.0.0.3
yes
yes
50.0.0.1
1839
vip
ge-1/0/1.0
up
master
Active
50.0.0.3
lcl
yes
yes
1000::1
vip
fe80::200:5eff:fe00:1
vip
ge-1/0/1.0
up
master
Active
1000::3
lcl
yes
yes
2000::1
vip
fe80::200:5eff:fe00:2
vip
ge-1/0/1.0
up
master
Active
2000::3
lcl
yes
yes
3000::1
vip
fe80::200:5eff:fe00:3
vip
ge-1/0/1.0
up
master
Active
3000::3
lcl
yes
yes
4000::1
vip
fe80::200:5eff:fe00:4
vip
ge-1/0/1.0
up
master
Active
4000::3
lcl
yes
yes
5000::1
vip
fe80::200:5eff:fe00:5
vip
5000::3
VR state
backup
Type
lcl
vip
Address
10.57.0.2
10.57.0.100
1840
VRRP if
ae0.210
Group
1
VR State
master
Current priority
200
1841
traceroute ethernet
Syntax
Release Information
Description
traceroute ethernet
local-mep mep-id
maintenance-association ma-name
maintenance-domain md-name
<ttl value>
<wait seconds>
mac-address | mep-id
<detail>
Options
local-mep mep-id(Required when multiple MEPs are configured) Identifier for the local
maintenance endpoint.
detail(Optional) Provide detailed information of the responder hostname, ingress port
8191.
maintenance-association ma-nameSpecifies an existing maintenance association from
default is 4.
wait seconds(Optional) Maximum time to wait for a response to the traceroute request.
1842
network
Output Fields
Table 159 on page 1843 lists the output fields for the traceroute ethernet command. Output
fields are listed in the approximate order in which they appear.
Field Description
Linktrace to
Interface
Maintenance Domain
Level
Maintenance Association
Local Mep
Transaction Identifier
Hop
TTL
MAC address of the egress interface of the node to which the LTM
is forwarded or
the next-hop MAC address derived from the next egress identifier
in the Egress-ID TLV of the LTR PDU.
Responder Hostname
Flags
1843
Field Description
Relay Action
The associated relay action. Relay action can be one of the following:
Sample Output
traceroute ethernet
user@host> traceroute ethernet maintenance-domain md1 maintenance-association ma1
00:01:02:03:04:05
Linktrace to 00:01:02:03:04:05, Interface : ge-5/0/0.0
Maintenance Domain: MD1, Level: 7
Maintenance Association: MA1, Local Mep: 1
Hop
TTL
Source MAC address
Transaction Identifier:100001
1
63
00:00:aa:aa:aa:aa
2
62
00:00:bb:bb:bb:bb
3
61
00:00:cc:cc:cc:cc
4
60
00:01:02:03:04:05
RelayAction:
Relay hit, Target MAC address matches the MP mac address
Relay FDB, output port decided by consulting FDB database
Relay MIP, output port decided by consulting MIP database
1844
Flags
RlyFDB
HFRlyFDB
HFRlyHit
H-T
1845
1846
PART 6
Index
1847
1848
Index
Symbols
#, comments in configuration statements................xlviii
( ), in syntax descriptions.................................................xlviii
10-Gigabit Ethernet interfaces.............................................4
802.3ah OAM................................................................618
DWDM
data and alarms, displaying..........................1518
status information, displaying..................1636, 1639
10-Gigabit Ethernet LAN/WAN PIC
control queue disable.................................................374
handling oversubscription........................................377
line rate mode...............................................................373
no-pre-classifier statement..................................1084
oversubscribed Ethernet mode
control queue disable...........................374, 1084
oversubscribed mode.................................................373
100-Gigabit Ethernet
configuration
forwarding-mode......................................976, 977
interoperability modes......................................414
sa-multicast.....................................414, 1162, 1163
vlan-rule...............................................................1244
vlan-steering..............................................414, 1245
forwarding-mode
sa-multicast.........................................................1163
forwarding-options
sa-multicast.........................................................1162
vlan-steering.......................................................1245
vlan-steering
vlan-rule...............................................................1244
100-Gigabit Ethernet interfaces....................................1518
Overview.........................................................................403
100-Gigabit Ethernet PIC
configuration..................................................................410
Overview.........................................................................407
100-Gigabit Ethernet PIC on Type 5 FPC
configuration
interoperability modes.............................421, 423
sa-multicast.................................................421, 423
Overview..........................................................................416
40-Gigabit Ethernet interfaces......................................1518
A
accept-source-mac statement......................................857
usage guidelines...........................................................473
access interface
interface-mode statement......................................262
access-concentrator statement....................................858
usage guidelines..........................................................343
account-layer2-overhead (PIC level)
statement...........................................................................859
accounting of Layer 2 overhead
viewing............................................................................468
ACI (agent circuit identifier) interface sets
status information, displaying..............................1636
action statement
OAM.................................................................................859
action-profile statement...................................................863
applying to remote MEP..........................................860
CFM...................................................................................861
LFM...................................................................................862
active statement
usage guidelines...........................................................160
adaptive......................................................................864, 1034
adaptive services interfaces..........................................1490
status information, displaying..............................1490
Address Resolution Protocol See ARP
address statement..............................................................865
adjacency-loss statement................................................867
ADSL
example configuration...............................................347
1849
advertisement-interval statement...............................868
age statement......................................................................869
agent-specifier statement
PPPoE..............................................................................870
aggregate statement
usage guidelines............................................................471
aggregated devices, configuring......................................152
aggregated Ethernet
clearing load balance states in a periodic
manner.......................................................................1150
defining stateful load-balancing
configuration...........................................................1035
enabling stateful load-balancing for traffic
flows ..............................................................1036, 1109
aggregated Ethernet interfaces.......................................138
example configuration.................................................151
LACP.................................................................................160
example configuration.......................................167
interval.....................................................................162
traceoptions..........................................................166
link speed.........................................................................155
minimum links................................................................157
multicast statistics.......................................................212
status information, displaying..............................1498
VLAN IDs.........................................................................245
aggregated Ethernet interfaces with link protection
manually switching to the backup link..............1294
reverting to the primary link...................................1294
aggregated Ethernet LACP link protection
manually switching...................................................1295
aggregated Ethernet on PTX Series Packet
Transport Routers
configuring......................................................................140
aggregated-devices statement.......................................872
usage guidelines...........................................................152
aggregated-ether-options statement..........................873
aging timer
ARP.......................................................................................21
ais-trigger-condition statement.....................................874
alarm statement...................................................................875
alarms
Fast Ethernet interfaces, checklist.......................804
Gigabit Ethernet interfaces, checklist.................804
LINK, displaying...........................................................804
alarms statement.................................................................875
all (tracing flag)
VRRP....................................................................................21
all-defects statement.........................876, 920, 949, 1150
allow-remote-loopback statement..............................876
1850
apply-action-profile statement......................................877
APS (automatic protection switching)
unidirectional switching, bidirectional switching,
selective selectors, merging selectors,
revertive switching, non-revertive
switching.....................................................................215
ARP
aging timer.........................................................................21
ARP configuration steps....................................................799
arp statement........................................................................878
asynchronous-notification statement.........................879
authentication-profile-name statement.....................881
authenticator statement........................................880, 882
auto-discovery statement................................................883
auto-negotiation statement
Gigabit Ethernet..........................................................884
auto-reconnect statement..............................................885
usage guidelines..........................................................343
autonegotiation, table........................................................790
B
backward-frr-enable statement...................................890
bandwidth-limit statement
policer for Gigabit Ethernet interface...................891
usage guidelines............................................................471
bcm0 interface.........................................................................23
ber-threshold-signal-degrade statement.................898
BERT
configuring interface diagnostics...........................779
bert-algorithm statement
usage guidelines...........................................................779
bert-error-rate statement
usage guidelines...........................................................779
bert-period statement
usage guidelines...........................................................779
bfd-liveness-detection statement
BFD
LAG...........................................................................901
bit error rate test See BERT
braces, in configuration statements.............................xlviii
brackets
angle, in syntax descriptions..................................xlviii
square, in configuration statements...................xlviii
Bridge Domain........................................................................531
bridge network
trunk interface..............................................................264
bridge-domain........................................................................531
bridge-domain statement................................................892
bridge-domains statement..............................................893
Index
burst-size-limit statement
policer for Gigabit Ethernet interface..................903
usage guidelines............................................................471
bypass statement...................................................903, 1068
bytes statement...................................................................904
C
cables
damaged or dirty.........................................................798
mismatch.......................................................................798
multimode fiber............................................................792
single-mode fiber........................................................792
calculation-weight statement........................................905
captive-portal statement (Unified Access Control
policy)..................................................................................906
CCC
encapsulation
VLAN-bundled dual-tag logical
interfaces.........................................................1248
VLAN-bundled single-tag logical
interfaces.........................................................1239
CCM
Configuring CCM for Better Scalability................578
Configuring Faster Convergence............................581
Configuring Faster Protection Switching............579
Configuring Primary VLAN ID..................................582
Remote Maintenance Association.......................583
centralized ppm statement.............................................909
CFM statistics
clearing...........................................................................1275
displaying for CFM interfaces..................................1721
displaying for interfaces..........................................1703
chassis
installed hardware, displaying..............................1296
serial numbers, displaying......................................1296
chassis statement................................................................910
checklist for alarms
Fast Ethernet interfaces ..........................................804
Gigabit Ethernet interfaces ....................................804
checklist for monitoring
Fast Ethernet interfaces............................................784
Gigabit Ethernet interfaces......................................784
circuit cross-connect (CCC)
encapsulation
VLAN-bundled dual-tag logical
interfaces.........................................................1248
VLAN-bundled single-tag logical
interfaces.........................................................1239
circuit problems
Fast Ethernet interfaces ..........................................803
Gigabit Ethernet interfaces ....................................803
classifier statement...............................................................911
usage guidelines...........................................................473
clear interfaces aggregate forwarding-options
load-balance statecommand........................1266, 1267
clear interfaces interface-set statistics
command..........................................................................1262
clear interfaces interval command..............................1263
clear interfaces statistics command
Fast Ethernet interfaces............................................792
Fast Ethernet statistics............................................800
clear interfaces transport pm statement..................1268
clear lldp neighbor command.......................................1269
clear lldp statistics command.......................................1270
clear oam ethernet connectivity-fault-management
continuity-measurement command........................1271
clear oam ethernet connectivity-fault-management
linktrace path-database command.........................1272
clear oam ethernet connectivity-fault-management
loss-statistics command.............................................1273
clear oam ethernet connectivity-fault-management
policer command............................................................1274
clear oam ethernet connectivity-fault-management
statistics.............................................................................1275
clear oam ethernet connectivity-fault-management
synthetic-loss-measurement command..............1276
clear oam ethernet link-fault-management state
command...........................................................................1277
clear oam ethernet link-fault-management
statistics command.......................................................1278
clear protection-group ethernet-ring statistics
command..........................................................................1279
clear statement.......................................................................911
client statement....................................................................912
comments, in configuration statements....................xlviii
community-vlan statement....................................912, 1011
compatibility-version statement....................................913
configuration
aggregated devices......................................................152
configuring
LLDP.................................................................................326
Configuring a Layer 2 Circuit on a VLAN-Bundled
Logical Interface..............................................................268
Configuring a VLAN-Bundled Logical
Interface................................................259, 266, 267, 268
Configuring CCM for Better Scalability........................578
Configuring Faster Convergence.....................................581
1851
D
data-channel statement....................................................921
data-tlv-size statement.....................................................922
database (tracing flag)..........................................................21
default-actions statement...............................................923
delay statement...................................................................924
PPPoE service name tables....................................925
delay-variation statement................................................926
delegate-server-processing statement.......................926
detect statement..................................................................927
detection-time statement
BFD
LAG...........................................................................901
device-count statement...................................................928
usage guidelines...........................................................152
direction statement............................................................930
1852
disable statement
802.1X connections....................................................932
link protection................................................................931
LLDP..................................................................................931
documentation
comments on.................................................................xlix
domain-id statement.........................................................935
dot1p-priority statement...................................................932
dot1x
configuration statements........................................848
dot1x statement....................................................................933
authenticator................................................................933
authentication-profile-name.........................933
interface.................................................................933
See also maximum-requests
See also quiet-period
See also reauthentication
See also retries
See also server-timeout
See also supplicant
See also supplicant-timeout
See also transmit-period
for MX Series routers in enhanced LAN
mode...........................................................................934
drop statement
PPPoE service name tables....................................935
dual-tag framing
VLAN ID list..................................................................1248
DWDM 10-Gigabit Ethernet interfaces
data and alarms, displaying...................................1518
dynamic PPPoE statements
max-sessions-vsa-ignore......................................1056
pp0...................................................................................1126
pppoe-underlying-options......................................1129
dynamic profiles statements
vlan-tags........................................................................1247
dynamic subscribers
max-sessions-vsa-ignore statement................1056
pppoe-underlying-options statement...............1129
dynamic-profile statement
PPPoE service name tables....................................936
E
E-LMI.............................................................................546, 1033
east-interface statement..................................................937
edit interfaces command
Fast Ethernet interfaces ..........................................799
Gigabit Ethernet interfaces .....................................799
edit interfaces fastether-options command ............796
Index
ETH-SLM
configuration scenarios.............................................641
displaying statistics and frame counts...............653
format of PDUs or messages.................................643
guidelines to configure..............................................647
overview.........................................................................640
steps to troubleshoot failures.................................657
transmission of PDUs or messages.....................645
ETH-SLM frame counts (with CFM statistics)
displaying for MEPs by enclosing CFM................1721
displaying for MEPs by interface or domain
level.............................................................................1703
ETH-SLM statistics (only)
displaying......................................................................1753
ether-options statement..................................................950
Ethernet
CFM.............................................................584, 586, 590
LFM example...................................619, 620, 622, 624
OAM overview...............................................................524
ring protection example............................................746
ring protection failure condition..............................771
ring protection normal operation..........................769
ring protection overview..................................743, 745
Ethernet 802.3ah OAM on PTX Series Packet
Transport Routers
configuring.....................................................................602
Ethernet bridging...................................................................316
Ethernet continuity measurement
displaying statistics and frame counts..............696
Ethernet failure notification protocol
configuring.....................................................................697
overview..........................................................................639
Ethernet frame
delay measurement (ETH-DM),
displaying..................................................................1282
loss-measurement (ETH-LM),
displaying..................................................................1287
Ethernet frame delay
examples.......................................................705, 710, 714
statistics................................................................739, 740
Ethernet frame delay measurement
configuring routers to support......................670, 677
displaying statistics and frame
counts................................................................673, 685
overview..........................................................................628
starting an ETH-DM session...........................671, 681
Ethernet frame loss measurement
displaying statistics and frame counts...............695
for dual tagged LMM/LMR PDUs...........................727
1853
1854
VLAN IDs........................................................................1237
VLAN tagging..............................................................1246
Ethernet link aggregation...................................................138
Ethernet Local Management Interface See E-LMI
ethernet ring
protection group APS................................................1791
protection group data channel..................1801, 1816
protection group flush-info...................................1803
protection group interface.....................................1805
protection group node state.................................1808
protection group statistics......................................1812
Ethernet Ring Protection
configuration statements........................................853
ethernet statement....................................................951, 952
chassis..............................................................................951
usage guidelines...........................................................152
Ethernet switching................................................................316
Ethernet synthetic loss measurement
debugging procedure for failures...........................657
displaying statistics and frame counts...............653
format of PDUs or messages.................................643
guidelines to configure..............................................647
overview.........................................................................640
scenarios for deployment.........................................641
transmission of PDUs or messages.....................645
Ethernet TCC
applying............................................................................361
example configuration...............................................361
Ethernet VLAN circuit
VLAN ID list..................................................................1239
ethernet-policer-profile statement..............................955
usage guidelines............................................................471
ethernet-ring statement...................................................956
ethernet-switch-profile statement......................476, 957
usage guidelines..................................................471, 493
evcs statement.....................................................................959
event statement....................................................................961
convey-loss-threshold statement.........................919
interface-status-tlv statement............................1007
port-status-tlv statement.......................................1125
event-thresholds
frame-error statement..............................................978
frame-period statement...........................................979
frame-period-summary statement....................980
symbol-period statement.......................................1196
event-thresholds statement............................................961
example
LLDP.................................................................................329
Index
examples
Ethernet frame delay................................705, 710, 714
Ethernet LFM...................................619, 620, 622, 624
Ethernet ring failure condition..................................771
Ethernet ring normal operation..............................769
Ethernet ring protection............................................746
extended VLAN
CCC
applying..................................................................258
example configuration.....................................258
TCC
applying..................................................................359
F
failover-delay statement..................................................963
usage guidelines..........................................................334
failure notification, Ethernet See Ethernet failure
notification
family bridge
VLAN ID list....................................................................1241
family statement.................................................................964
Fast Ethernet interfaces
alarms, LINK.................................................................804
autonegotiation, table...............................................790
circuit problems..................................................791, 803
clear interfaces statistics command..................800
counters .........................................................................805
edit interfaces command ........................................799
Ethernet link aggregation..........................................138
example configuration....................................................5
ignoring Layer 3 incomplete errors..........................20
ingress rate-limit...............................................................11
LINK alarms, checklist .............................................804
link modes.........................................................................14
link protection...............................................................168
local loopback, configuring ....................................796
loopback mode................................................................19
MAC address filtering....................................................15
monitor checklist.........................................................784
monitor interface command ...................................791
monitoring.......................................................................791
physical loopback........................................................795
ping interface command.........................................800
set arp command .......................................................799
set cli terminal command ........................................791
set loopback local command ................................796
show interfaces command ..................787, 797, 802
show interfaces extensive
command........................................................788, 804
1855
frame-period-summary statement.............................980
framing statement
10-Gigabit Ethernet interfaces................................981
G
general (tracing flag)..............................................................21
Gigabit Ethernet interfaces....................................................4
alarms, LINK.................................................................804
autonegotiation, table...............................................790
circuit problems...........................................................803
counters..........................................................................805
demultiplexing interface information,
displaying.................................................................1509
diagnostics information, displaying.....................1518
edit interfaces command.........................................799
Ethernet link aggregation..........................................138
example configuration...................................................6
flow control.......................................................................13
ignoring Layer 3 incomplete errors..........................20
LACP, displaying.........................................................1674
LINK alarms, checklist .............................................804
link protection...............................................................168
local loopback, configuring.....................................796
loopback mode................................................................19
loopback plug, creating.............................................795
MAC address filtering....................................................15
MAC database, displaying......................................1656
monitor checklist.........................................................784
monitor interface command....................................791
monitoring.......................................................................791
physical loopback, creating ....................................795
ping interface command.........................................800
set arp command .......................................................799
set cli terminal command.........................................791
set loopback local command.................................796
show interfaces command.............................787, 797
show interfaces extensive
command........................................................788, 804
show interfaces terse command...........................786
static ARP entry, configuring ..................................799
statistics
checking error.......................................................801
monitoring.............................................................801
resetting................................................................800
status
description, table................................................786
displaying specific...............................................787
errors, table...........................................................789
1856
extensive................................................................788
verifying...................................................................797
status information,
displaying...............................1561, 1585, 1636, 1639
VLAN IDs...................................................245, 1237, 1242
VLAN tagging..............................................................1246
Gigabit Ethernet IQ interfaces
MAC address accounting.........................................463
MAC address filtering.................................................475
policer
example configuration......................................476
rate limiting.....................................................................471
Gigabit Ethernet IQ PIC
traffic and MAC statistics.......................................1585
Gigabit Ethernet uPIM interfaces
speed...................................................................................10
gigether-options statement............................................982
gratuitous ARP.........................................................................20
gratuitous-arp-reply statement.....................................983
usage guidelines.............................................................20
guard-interval statement.................................................985
guest-vlan statement........................................................984
H
hardware, installed, displaying......................................1296
hardware-assisted-timestamping statement.........986
hold-interval statement
connectivity-fault management...........................986
Ethernet ring protection switching.......................987
hold-multiplier statement................................................987
holddown-interval statement
BFD
LAG...........................................................................901
I
iccp
configuration statements........................................848
IEEE 802.1p inheritance
and transparent tag.....................................................515
swap-by-poppush statement..................................517
transparent statement...............................................517
transparent tag..............................................................517
IEEE 802.1p policer profile
usage guidelines...........................................................472
ieee802.1p statement........................................................989
IGMP snooping
enabling.........................................................................990
multicast-router interface......................................1074
igmp-snooping statement...............................................990
Index
ignore-l3-incompletes statement..................................991
ignoring Layer 3 incomplete errors...................................20
ingress-policer-overhead statement...........................993
ingress-rate-limit statement...........................................993
usage guidelines...............................................................11
inner-tag-protocol-id statement...................................994
usage guidelines..........................................................495
inner-vlan-id statement....................................................995
usage guidelines..........................................................495
input-policer statement....................................................996
input-priority-map statement.........................................997
usage guidelines...........................................................472
input-three-color statement...........................................998
instance....................................................................................532
Instance....................................................................................532
instance statement..........................................................1000
integrated routing and bridging interfaces
integrated routing and bridging interfaces,
displaying.................................................................1650
interface statement..........................................................1004
IEEE 802.1X..................................................................1002
IEEE 802.3ah..............................................................1003
LLDP................................................................................1001
usage guidelines..........................................................264
interface-down statement...................................923, 1004
interface-mode statement
usage guidelines................................................262, 263
interface-status-tlv statement.....................................1007
interfaces
configuration statements........................................824
Gigabit Ethernet IQ policer
example configuration......................................476
mixed VLAN tagging..............................248, 972, 1077
interfaces (tracing flag).........................................................21
interfaces statement........................................................1005
internal Ethernet interface
status information, displaying...............................1610
interval statement................................................1008, 1009
IP addresses
management Ethernet interface.............................28
is-ma statement.................................................................1010
iteration-count statement...............................................1012
iteration-period
statement................................886, 887, 888, 889, 1012
Iterator
verifying configuration..............................................660
Iterator profile
configuration......................................................650, 658
iterator statistics..................................................................663
iterators
VPLS connections......................................................669
ITU-T standards
Y.1731................................................................................639
Y.1731 ETH-DM..............................................................628
Y.1731 ETH-LM...............................................................634
ITU-Y.1731
VPLS connections......................................................669
ixgbe0 interface.......................................................................23
ixgbe1 interface........................................................................23
J
jitter, Ethernet frame See Ethernet frame delay
measurement
L
LACP
displaying......................................................................1674
Ethernet aggregation..................................................160
example configuration.......................................167
interval.....................................................................162
traceoptions..........................................................166
tracing operations........................................................166
lacp
force-up...........................................................................975
lacp statement
802.3ad..........................................................................1015
Aggregated Ethernet.................................................1016
usage guidelines...........................................................160
laser-enable statement.....................................................1017
Layer 2 bridging
Ethernet...........................................................................316
learning properties, displaying..................1668, 1670
Layer 2.5 VPNs
Ethernet.......................................................258, 359, 361
Layer 3 incomplete errors..................................................991
layer2-policer statement..................................................1018
learning properties
Layer 2, displaying.........................................1668, 1670
level statement....................................................................1019
line-loopback statement................................................1020
link aggregation.....................................................................138
link layer discovery protocol See LLDP
link modes..................................................................................14
link protection
aggregated Ethernet interfaces
configuring.............................................................168
configuring primary and backup links.........168
1857
disabling.................................................................169
reverting traffic to primary link.......................169
disable statement........................................................931
non-revertive statement........................................1086
revertive statement....................................................1158
link speed
Ethernet aggregation..................................................155
link-adjacency-loss statement......................................1021
link-discovery statement..................................................1021
link-down statement........................................................1022
link-event-rate statement...............................................1022
link-fault management.....................................................862
link-fault-management statement.............................1023
link-mode statement........................................................1025
usage guidelines..............................................................14
link-protected aggregated Ethernet interfaces
manually switching to the backup link..............1294
reverting to the primary link...................................1294
link-protected aggregated Ethernet LACP links
manually switching...................................................1295
link-protection statement...............................................1027
link-speed statement
usage guidelines...........................................................155
linktrace
database, displaying..................................................1714
tracing............................................................................1842
linktrace statement...........................................................1020
LLDP
configuration statements.......................................1205
configuring.....................................................................326
displaying......................................................................1678
example..........................................................................329
local information, displaying..................................1681
neighbor
clearing.................................................................1269
neighbors, displaying...............................................1684
overview..........................................................................325
port description TLV
configuring.............................................................1121
port ID TLV
configuring............................................................1124
remote global statistics, displaying...................1690
statistics
clearing..................................................................1270
statistics, displaying.................................................1692
tracing operations.......................................................330
lldp statement
LLDP................................................................................1031
1858
lldp-configuration-notification-interval
statement.........................................................................1032
lmi statement
Ethernet OAM.............................................................1033
load-balance........................................................................1034
local-address statement
BFD
LAG...........................................................................901
local-loopback statement..............................................1037
lockout statement..............................................................1037
log files
number of PPPoE.............................................349, 350
size of PPPoE......................................................349, 350
log-and-generate-ais statement.................................1038
logical devices........................................................................152
logical interfaces
VLAN IDs.............................................................1237, 1242
VLAN-bundled
dual-tag................................................................1248
single-tag.............................................................1239
logical systems
configuration statements........................................840
logical-interface-policer statement............................1039
loopback mode........................................................................19
loopback statement
Aggregated Ethernet, Fast Ethernet, and Gigabit
Ethernet...................................................................1040
Fast Ethernet interfaces
usage guidelines.....................................................19
Gigabit Ethernet interfaces
usage guidelines.....................................................19
loopback testing....................................................................777
loopback, configuring local
Fast Ethernet interfaces ..........................................796
Gigabit Ethernet interfaces......................................796
loopback, creating physical
Fast Ethernet interfaces ...........................................795
Gigabit Ethernet interfaces .....................................795
loopback, plug.......................................................................795
loss-priority statement.....................................................1041
usage guidelines...........................................................473
loss-threshold statement...............................................1042
lowest-priority-defect statement................................1043
M
MAC address accounting
Gigabit Ethernet IQ interfaces................................463
Index
maximum-requests statement....................................1058
mc-ae statement...............................................................1059
measurement-type statement.....................................1062
mep statement...................................................................1063
minimum links for aggregation
Ethernet links..................................................................157
minimum-interval statement
BFD
LAG...........................................................................901
minimum-links statement..............................................1065
usage guidelines............................................................157
minimum-receive-interval statement
BFD
LAG...........................................................................901
minimum-receive-ttl statement
BFD
LAG...........................................................................901
MIP Half Function.................................................................532
mip-half-function.................................................................532
mip-half-function statement........................................1066
mixed VLAN tagging.......................................248, 972, 1077
monitor ethernet delay-measurement
command..........................................................................1282
monitor ethernet loss-measurement
command..........................................................................1287
monitor interface command
Fast Ethernet interfaces ............................................791
Gigabit Ethernet interfaces.......................................791
monitor-end-point statement
monitor-end-point...................................................1068
mtu statement....................................................................1070
multi-chassis link aggregation interface
displaying.......................................................................1661
multi-chassis-protection
peer statement.............................................................1110
multi-chassis-protection statement...........................1075
multicast-router-interface statement
IGMP snooping............................................................1074
multicast-statistics statement
usage guidelines
aggregated Ethernet...........................................212
Ethernet.....................................................................22
multichassis aggregated Ethernet interfaces
reverting to the primary link immediately.........1292
reverting to the primary link in non-revertive
mode..........................................................................1292
multimode fiber cable........................................................792
1859
multiplier statement
BFD
LAG...........................................................................901
MX Series
Ethernet OAM...............................................................524
MX Series Routers.....................................................................4
N
name-format statement.................................................1076
native-vlan-id statement.................................................1077
negotiate-address statement.......................................1078
usage guidelines..........................................................343
negotiation-options
allow-remote-loopback statement.....................876
no-allow-link-events statement.........................1079
negotiation-options statement....................................1078
neighbor
LLDP...............................................................................1269
no-adaptation statement
BFD
LAG...........................................................................901
no-allow-link-events statement..................................1079
no-asynchronous-notification statement..................879
no-auto-mdix statement.................................................1081
no-flow-control statement..............................................973
usage guidelines..............................................................13
no-gratuitous-arp-reply statement..............................983
usage guidelines.............................................................20
no-gratuitous-arp-request statement........................1081
usage guidelines.............................................................20
no-keepalives statement................................................1082
no-loopback statement..................................................1040
usage guidelines..............................................................19
no-mac-learn-enable statement.................................1047
usage guidelines..........................................................463
no-odu-backward-frr-enable.......................................1083
no-odu-signal-degrade-monitor-enable.................1083
no-reauthentication statement...................................1084
no-send-pads-ac-info statement
PPPoE............................................................................1085
no-source-filtering statement.........................................1181
usage guidelines....................................................15, 475
non-revertive statement.................................................1086
non-vc-mode statement.................................................1087
normal (tracing flag)
arp aging timer.................................................................21
number-of-frames statement......................................1088
1860
O
OAM
configuration statements........................................849
E-LMI................................................................................546
Ethernet CFM...........................................584, 586, 590
Ethernet overview.......................................................524
OAM state
clearing...........................................................................1277
oam statement....................................................................1091
OAM statistics
clearing...........................................................................1278
oc192 statement.................................................................1093
odu-backward-frr-enable..............................................1094
odu-delay-management statement..........................1094
bypass.............................................................................903
number-of-frames...................................................1088
start-measurement...................................................1189
odu-signal-degrade statement....................................1095
odu-signal-degrade-monitor-enable........................1096
odu-ttim-action-enable statement...........................1096
optical attenuation..............................................................798
optics-options statement...............................................1097
alarm................................................................................875
bytes................................................................................904
fec......................................................................................970
is-ma...............................................................................1010
laser-enable..................................................................1017
line-loopback..............................................................1020
local-loopback............................................................1037
odu-delay-management.......................................1094
odu-signal-degrade.................................................1095
odu-ttim-action-enable.........................................1096
otu-ttim-action-enable..........................................1099
prbs..................................................................................1140
preemptive-fast-reroute...........................................1141
rate...................................................................................1148
signal-degrade...................................................895, 1177
trigger.............................................................................1220
tti......................................................................................1225
warning..........................................................................1252
otn-options statement....................................................1098
otu-ttim-action-enable statement............................1099
otu2 statement...................................................................1093
otu4 statement....................................................................1100
output-policer statement.................................................1101
output-priority-map statement.....................................1102
usage guidelines...........................................................473
output-three-color statement.......................................1103
Index
output-vlan-map statement
Aggregated Ethernet.................................................1104
Gigabit Ethernet IQ....................................................1105
P
packets (tracing flag).............................................................21
pado-advertise statement..............................................1106
parentheses, in syntax descriptions.............................xlviii
pass-through statement..................................................1106
passive statement
usage guidelines...........................................................160
passive-monitor-mode statement...............................1107
path-database-size statement.....................................1108
pdu-interval statement....................................................1108
pdu-threshold statement................................................1109
peer statement......................................................................1110
per-flow, stateful statement
aggregated Ethernet.....................................1036, 1109
per-packet............................................................................1034
performance-monitoring statement..............................1111
periodic statement...............................................................1112
usage guidelines...........................................................162
physical devices, aggregating...........................................152
physical interfaces
Ethernet link aggregation..........................................138
flow control.......................................................................13
link modes.........................................................................14
loopback mode................................................................19
MAC address filtering....................................................15
mixed VLAN tagging..............................248, 972, 1077
VLAN tagging..............................................................1246
physical link down
Fast Ethernet interfaces, table...............................798
Gigabit Ethernet interfaces, table.........................798
physical link up
Fast Ethernet interfaces...................................787, 797
Gigabit Ethernet interfaces.............................787, 797
physical loopback
Fast Ethernet interfaces............................................795
Gigabit Ethernet interfaces......................................795
PICs
installed, displaying list............................................1297
status
displaying for a specific PIC...........................1472
ping interface command
Fast Ethernet interfaces..........................................800
Gigabit Ethernet interfaces ....................................800
policer statement
CFM firewall...................................................................1113
CFM global level...........................................................1114
CFM session level.........................................................1115
CoS....................................................................................1116
interface MAC................................................................1117
usage guidelines............................................................471
policing
Gigabit Ethernet IQ interfaces.................................471
pop statement
Gigabit Ethernet IQ interfaces................................1118
usage guidelines.........................................................500
pop-pop statement
Gigabit Ethernet IQ interfaces................................1119
usage guidelines...........................................................501
pop-swap statement
Gigabit Ethernet IQ interfaces...............................1120
usage guidelines..........................................................502
port-description-type statement
LLDP..................................................................................1121
port-id-subtype statement
LLDP.................................................................................1124
port-priority statement
LACP................................................................................1123
port-status-tlv statement................................................1125
pp0 statement
dynamic PPPoE...........................................................1126
ppm statement.....................................................................1127
PPPoE
example configuration...............................................347
flags for tracing operations............................350, 351
interfaces, displaying.....................................1626, 1772
log file access for tracing operations..........349, 351
log file size and number..................................349, 350
log filenames for tracing operations..........349, 350
message severity levels for tracing
operations...................................................................351
regular expressions for tracing
operations.........................................................349, 351
service name tables
verifying the configuration...............................347
service name tables, displaying............................1776
service name tables, displaying active
sessions.....................................................................1779
statistics
displaying..............................................................1781
tracing operations.......................................................348
underlying interfaces, displaying..........................1783
version, displaying.....................................................1789
1861
PPPoE server
example configuration...............................................347
pppoe-options statement...............................................1128
usage guidelines..........................................................343
pppoe-underlying-options statement
static and dynamic PPPoE......................................1129
pps.............................................................................................864
prbs statement....................................................................1140
preemptive-fast-reroute statement..............................1141
backward-frr-enable.................................................890
no-odu-backward-frr-enable..............................1083
no-odu-signal-degrade-monitor-enable........1083
odu-backward-frr-enable.....................................1094
odu-signal-degrade-monitor-enable...............1096
signal-degrade-monitor-enable...........................1178
premium
policer.....................................................................1131, 1142
premium statement
output priority map...........................................1131, 1142
usage guidelines..................................................471, 473
priority statement................................................................1132
CFM SLA iterator.........................................................1132
OAM connectivity-fault management................1133
Proactive mode
overview..........................................................................638
propagate-tc statement...................................................1133
protect-maintenance-association statement
connectivity-fault management...........................1143
protection group
ethernet ring APS........................................................1791
ethernet ring flush-info...........................................1803
ethernet ring interface.............................................1805
ethernet ring node state.........................................1808
ethernet ring statistics..............................................1812
ethernet ring VLANs.......................................1801, 1816
protection group statistics
clearing...........................................................................1279
protection-group
configuration statements........................................853
protection-group statement...........................................1134
protocol statement.............................................................1137
protocol-down statement................................................1137
protocols connections
configuration statements...............................847, 852
protocols dot1x
configuration statements........................................848
protocols Ethernet Ring Protection
configuration statements........................................853
1862
protocols iccp
configuration statements........................................848
protocols OAM
configuration statements........................................849
protocols statement...........................................................1136
protocols VRRP
configuration statements........................................849
proxy statement...................................................................1143
usage guidelines...........................................................361
proxy-arp statement..........................................................1144
pseudowires
mixed VLAN tagging...................................................972
ptopo-configuration-maximum-hold-time
statement..........................................................................1138
ptopo-configuration-trap-interval statement.........1138
push statement
Gigabit Ethernet IQ interfaces.....................1139, 1145
usage guidelines..........................................................499
push-push statement
Gigabit Ethernet IQ interfaces....................1140, 1146
usage guidelines.........................................................500
PVLANs
configuring.............................................................912, 1011
Q
quiet-period statement.....................................................1147
R
rate statement......................................................................1148
fixed-stuff-bytes...........................................................971
otu2.................................................................................1093
otu4.................................................................................1100
pass-through...............................................................1106
real-time monitoring
Ethernet frame delay measurement
(ETH-DM)................................................................1282
Ethernet frame loss-measurement
(ETH-LM).................................................................1287
reauthentication statement............................................1149
rebalance statement
aggregated Ethernet.................................................1150
receive-options-packets statement..............................1151
receive-ttl-exceeded statement.....................................1151
remote MEP with iterator profile
configuration................................................................668
remote statement...............................................................1152
usage guidelines.......................................258, 359, 361
remote-loopback statement...........................................1152
Index
remote-maintenance-association statement
connectivity-fault management...........................1153
remote-mep statement....................................................1153
request interface (revert | switchover) (Aggregated
Ethernet Link Protection) command.....................1294
request interface mc-ae switchover (Multichassis
link aggregation) command.......................................1292
request lacp link-switchover command....................1295
retries statement..................................................................1157
revertive statement............................................................1158
rewrite VLAN tag on untagged frame
usage guidelines..........................................................504
ring protection
Ethernet overview..............................................743, 745
ring-id statement.................................................................1158
ring-protection-link-end statement.............................1159
ring-protection-link-owner statement........................1159
RJ-45 Ethernet interface....................................................795
routing-instance statement............................................1160
PPPoE service name tables.....................................1161
S
sa-multicast statement..........................................1162, 1163
scan-interval.........................................................................864
send-critical-event statement........................................1167
serial numbers, displaying..............................................1296
server statement..................................................................1167
server-fail statement.........................................................1168
server-reject-vlan statement..........................................1169
server-timeout statement................................................1170
service name tables
PPPoE
verifying the configuration...............................347
service statement
PPPoE...............................................................................1171
service-level agreement measurement
overview..........................................................................636
service-name statement...................................................1172
usage guidelines..........................................................343
service-name-table statement
PPPoE underlying interface.....................................1173
service-name-tables statement
PPPoE..............................................................................1174
set arp command
Fast Ethernet interfaces ..........................................799
Gigabit Ethernet interfaces......................................799
set cli terminal command
Fast Ethernet interfaces ............................................791
Gigabit Ethernet interfaces ......................................791
1863
1864
Index
swap-swap statement
Gigabit Ethernet IQ interfaces...............................1194
usage guidelines..........................................................508
switch-options statement...............................................1194
switch-port statement
access switching.........................................................1195
symbol-period statement................................................1196
Symmetrical Load Balancing
on 802.3ad Link Aggregation on MX Series.........171
syntax conventions..............................................................xlvii
system processes
configuration statements........................................855
system-priority statement
LACP................................................................................1198
T
tag protocol IDs on PTX Series Packet Transport
Routers
configuring.....................................................................494
tag-protocol-id statement
TPID to rewrite...........................................................1200
TPIDs expected to be sent or received...............1199
usage guidelines..........................................................495
tca statement.......................................................................1201
technical support
contacting JTAC............................................................xlix
terminate statement
PPPoE service name tables...................................1203
timer (tracing flag)
Ethernet interface speed..............................................21
tolerance.................................................................................864
trace operations
VRRP....................................................................................21
traceoptions (LACP) statement
usage guidelines...........................................................166
traceoptions statement....................................................1215
ICCP.................................................................................988
interface processes...................................................1208
LACP................................................................................1210
LLDP...............................................................................1204
usage guidelines.................................................330
PPPoE..............................................................................1212
VRRP
usage guidelines.....................................................21
traceroute ethernet............................................................1842
traceroute ethernet command.....................................1842
1865
tracing operations
LACP.................................................................................166
LLDP.....................................................................330, 1204
PPPoE..............................................................................348
transmit light level................................................................792
transmit-delay statement
LLDP................................................................................1216
transmit-interval statement
BFD
LAG...........................................................................901
transmit-period statement..............................................1218
transparent statement........................................................517
transparent tag operations...............................................515
transport-monitoring statement...................................1219
Tri-Rate Ethernet copper interfaces
speed...................................................................................10
trigger statement................................................................1220
trunk interface
interface-mode statement......................................263
usage guidelines..........................................................264
vlan-id-list statement................................................263
trunk port.................................................................................263
VLAN ID list....................................................................1241
tti statement.........................................................................1225
tx-power statement..........................................................1226
U
uac-policy statement........................................................1226
underlying-interface statement.....................................1227
unit statement.....................................................................1228
unnumbered-address statement
PPP..................................................................................1234
unnumbered-interface statement
usage guidelines..........................................................343
V
version statement
BFD
LAG...........................................................................901
version-3 statement..........................................................1235
virtual links
aggregated devices......................................................152
virtual-control-channel statement.............................1236
virtual-switch statement.................................................1236
VLAN
Configuring a Layer 2 Circuit on a
VLAN-Bundled Logical Interface......................268
Configuring a VLAN-Bundled Logical
Interface............................................................267, 268
1866
Index
VPLS
statistical frame loss measurement...................669
VRRP
configuration statements........................................849
statistics
displaying............................................................1830
trace operations...............................................................21
tracing flag.........................................................................21
vrrp
failover-delay................................................................963
version-3........................................................................1235
W
wait-to-block-interval statement.................................1251
warning statement.............................................................1252
wavelength statement......................................................1253
weighted random early detection.....................................22
west-interface statement................................................1257
WRED...........................................................................................22
1867
1868