Extreme Networks Slx 20.4.1 Commandref
Extreme Networks Slx 20.4.1 Commandref
20.4.1
9037402-00 Rev AA
April 2022
Copyright © 2022 Extreme Networks, Inc. All rights reserved.
Legal Notice
Extreme Networks, Inc. reserves the right to make changes in specifications and other information
contained in this document and its website without prior notice. The reader should in all cases
consult representatives of Extreme Networks to determine whether any such changes have been
made.
The hardware, firmware, software or any specifications described or referred to in this document
are subject to change without notice.
Trademarks
Extreme Networks and the Extreme Networks logo are trademarks or registered trademarks of
Extreme Networks, Inc. in the United States and/or other countries.
All other names (including any product names) mentioned in this document are the property of
their respective owners and may be trademarks or registered trademarks of their respective
companies/owners.
For additional information on Extreme Networks trademarks, see: www.extremenetworks.com/
company/legal/trademarks
Commands A - B........................................................................................................................................51
aaa accounting............................................................................................................................................................54
aaa authentication ....................................................................................................................................................57
aaa authorization command................................................................................................................................ 59
accept-lifetime............................................................................................................................................................. 61
accept-tolerance........................................................................................................................................................ 63
action (management-heartbeat).......................................................................................................................64
acl-log-raslog...............................................................................................................................................................66
acl-mirror....................................................................................................................................................................... 68
acl-policy....................................................................................................................................................................... 70
action python-script.................................................................................................................................................. 71
action-profile ...............................................................................................................................................................73
action-timeout.............................................................................................................................................................74
activate (telemetry collector).............................................................................................................................. 75
activate (telemetry server)................................................................................................................................... 76
activate (VXLAN overlay gateway)...................................................................................................................77
adaptive..........................................................................................................................................................................78
add (telemetry)...........................................................................................................................................................79
additional-paths...........................................................................................................................................................81
additional-paths select............................................................................................................................................83
address-family ipv4 flowspec.............................................................................................................................. 85
address-family l2vpn evpn (BGP)......................................................................................................................87
address-family unicast (BGP)..............................................................................................................................88
address-family unicast (IS-IS)............................................................................................................................. 90
adjustment-interval....................................................................................................................................................91
adjustment-threshold.............................................................................................................................................. 92
admin-group................................................................................................................................................................ 93
advertise dot1-tlv ...................................................................................................................................................... 95
advertise dot3-tlv .....................................................................................................................................................96
advertise optional-tlv ..............................................................................................................................................97
advertise-backup ......................................................................................................................................................99
advertise-best-external.........................................................................................................................................100
advertisement-interval (VRRP).......................................................................................................................... 101
advertisement-interval-scale .............................................................................................................................102
agent-enable .............................................................................................................................................................104
agent-port .................................................................................................................................................................. 105
agent-uuid ..................................................................................................................................................................106
aggregate-address (BGP)....................................................................................................................................107
alias ................................................................................................................................................................................109
alias-config ..................................................................................................................................................................110
allow-conflicting-rules.............................................................................................................................................. 111
allow-duplicate-rules................................................................................................................................................113
allow multiple-ep-per-port....................................................................................................................................115
always-compare-med ............................................................................................................................................ 116
always-propagate .....................................................................................................................................................117
anycast-rp..................................................................................................................................................................... 118
area authentication (OSPFv3)........................................................................................................................... 120
area nssa (OSPFv2).................................................................................................................................................122
area nssa (OSPFv3).................................................................................................................................................124
area prefix-list (OSPFv2)...................................................................................................................................... 126
area range (OSPFv2).............................................................................................................................................. 128
area range (OSPFv3)............................................................................................................................................. 130
area stub (OSPFv2).................................................................................................................................................132
area stub (OSPFv3)................................................................................................................................................ 134
area virtual-link (OSPFv2)....................................................................................................................................136
area virtual-link (OSPFv3)....................................................................................................................................138
area virtual-link authentication (OSPFv3)................................................................................................... 140
arp .................................................................................................................................................................................. 142
arp access-list............................................................................................................................................................ 144
as-path-ignore ..........................................................................................................................................................146
auth-check...................................................................................................................................................................147
auth-key........................................................................................................................................................................149
auth-mode.................................................................................................................................................................... 151
auth-port...................................................................................................................................................................... 153
auto-cost reference-bandwidth (OSPFv2)..................................................................................................154
auto-cost reference-bandwidth (OSPFv3)..................................................................................................156
auto-shutdown-new-neighbors.........................................................................................................................158
autobw-threshold table.........................................................................................................................................159
backup-advertisement-interval ....................................................................................................................... 160
bandwidth-ceiling..................................................................................................................................................... 161
banner............................................................................................................................................................................163
beacon enable........................................................................................................................................................... 164
bestpath prefix-validation disable................................................................................................................... 166
bestpath prefix-validation disallow-invalid.................................................................................................. 167
bfd................................................................................................................................................................................... 168
bfd holdover-interval..............................................................................................................................................170
bfd interval...................................................................................................................................................................172
bfd shutdown............................................................................................................................................................. 174
bgp-redistribute-internal ..................................................................................................................................... 175
bpdu-drop-enable....................................................................................................................................................176
breakout mode.......................................................................................................................................................... 177
bridge-domain........................................................................................................................................................... 179
bridge-domain (EVPN)...........................................................................................................................................181
bridge-priority .......................................................................................................................................................... 183
bsr-candidate.............................................................................................................................................................184
bypass-lsp....................................................................................................................................................................186
bypass-lsp (Telemetry) .........................................................................................................................................187
cluster........................................................................................................................................................................... 343
cluster-track.............................................................................................................................................................. 344
commit......................................................................................................................................................................... 346
compare-med-empty-aspath .......................................................................................................................... 347
compare-routerid .................................................................................................................................................. 348
confederation identifier....................................................................................................................................... 349
confederation peers.............................................................................................................................................. 350
configure terminal ...................................................................................................................................................351
config-drift-track..................................................................................................................................................... 352
connector.................................................................................................................................................................... 353
control-word..............................................................................................................................................................354
console......................................................................................................................................................................... 356
copy ..............................................................................................................................................................................358
core-isolation-disable ............................................................................................................................................361
core-isolation-track ...............................................................................................................................................362
cos (MPLS)................................................................................................................................................................. 363
cos (Y1731) ................................................................................................................................................................ 364
crypto ca authenticate......................................................................................................................................... 365
crypto ca enroll........................................................................................................................................................ 367
crypto ca import..................................................................................................................................................... 369
crypto ca import-pkcs .......................................................................................................................................... 371
crypto ca trustpoint...............................................................................................................................................374
crypto cert .................................................................................................................................................................375
crypto import ...........................................................................................................................................................377
crypto key ..................................................................................................................................................................379
csnp-interval............................................................................................................................................................... 381
cspf-computation-mode..................................................................................................................................... 382
cspf-interface-constraint.....................................................................................................................................384
cspf-group.................................................................................................................................................................. 385
cspf-group-computation.....................................................................................................................................386
dampening ................................................................................................................................................................ 388
database-overflow-interval (OSPFv2)..........................................................................................................390
database-overflow-interval (OSPFv3)........................................................................................................... 391
debug access-list-log buffer .............................................................................................................................392
debug arp packet buffer..................................................................................................................................... 393
debug dhcp packet buffer ................................................................................................................................ 395
debug dot1x packet................................................................................................................................................397
debug ip bgp ........................................................................................................................................................... 399
debug ip bgp neighbor ...................................................................................................................................... 402
debug ip igmp ........................................................................................................................................................ 404
debug ip pim ........................................................................................................................................................... 406
debug ipv6 bgp.......................................................................................................................................................408
debug ipv6 bgp neighbor....................................................................................................................................410
debug ipv6 ospf graceful-restart..................................................................................................................... 412
debug lacp ................................................................................................................................................................. 413
debug lldp dump .....................................................................................................................................................415
debug lldp packet .................................................................................................................................................. 416
debug spanning-tree .............................................................................................................................................418
debug udld packet ............................................................................................................................................... 420
Commands E - F.....................................................................................................................................499
enable............................................................................................................................................................................ 501
enable (ERP)............................................................................................................................................................. 502
enable (GRUB) ........................................................................................................................................................503
enable (management-heartbeat)................................................................................................................... 504
encryption-level.......................................................................................................................................................506
enable-all-interfaces.............................................................................................................................................. 507
enforce-first-as ....................................................................................................................................................... 508
eol...................................................................................................................................................................................509
erp................................................................................................................................................................................... 510
error-disable-timeout enable ..............................................................................................................................511
error-disable-timeout interval ........................................................................................................................... 512
esi..................................................................................................................................................................................... 514
esi (BGP EVPN Multi-homing)........................................................................................................................... 516
ethernet-segment.................................................................................................................................................... 517
event ..............................................................................................................................................................................518
event-handler............................................................................................................................................................520
event-handler abort action.................................................................................................................................522
event-handler activate.......................................................................................................................................... 523
evpn............................................................................................................................................................................... 526
exclude-any................................................................................................................................................................ 527
exclude-interface.....................................................................................................................................................529
exp................................................................................................................................................................................... 531
export-vrf-leaked-routes .................................................................................................................................... 533
export-map ............................................................................................................................................................... 534
extend bridge-domain .........................................................................................................................................535
extend vlan ................................................................................................................................................................536
external-lsdb-limit (OSPFv2).............................................................................................................................537
external-lsdb-limit (OSPFv3).............................................................................................................................538
facility-backup.......................................................................................................................................................... 539
fast-convergence......................................................................................................................................................541
fast-external-fallover ............................................................................................................................................ 542
fast-flood.....................................................................................................................................................................543
fastboot....................................................................................................................................................................... 544
fast-wtr-time............................................................................................................................................................. 545
fec mode ....................................................................................................................................................................546
fec (telemetry)......................................................................................................................................................... 548
filter-change-update-delay................................................................................................................................ 549
filter-fec-in..................................................................................................................................................................550
filter-fec-out...............................................................................................................................................................552
firmware activate ................................................................................................................................................... 553
firmware commit ....................................................................................................................................................554
firmware download ............................................................................................................................................... 555
firmware download ftp ........................................................................................................................................558
firmware download fullinstall ...........................................................................................................................560
firmware download interactive ........................................................................................................................562
firmware download scp ...................................................................................................................................... 563
firmware download sftp ..................................................................................................................................... 565
firmware download tftp ......................................................................................................................................567
firmware download usb ......................................................................................................................................569
firmware peripheral-update cpld...................................................................................................................... 571
firmware peripheral-update fpga.................................................................................................................... 572
firmware recover .....................................................................................................................................................573
firmware restore ..................................................................................................................................................... 574
flex-cli show link-fault-signaling ......................................................................................................................575
flex-cli show local-fault interface ....................................................................................................................576
flex-cli show local-fault slot ...............................................................................................................................577
flex-cli show remote-fault interface .............................................................................................................. 578
flex-cli show remote-fault slot ......................................................................................................................... 579
flow-label.................................................................................................................................................................... 580
flowspec validation..................................................................................................................................................581
force-switch............................................................................................................................................................... 583
format RFC-5424 ...................................................................................................................................................584
forward-delay .......................................................................................................................................................... 586
from............................................................................................................................................................................... 588
frr.................................................................................................................................................................................... 590
Commands G - J......................................................................................................................................591
gNMI Server Configuration.................................................................................................................................597
graceful-restart (BGP).......................................................................................................................................... 598
graceful-restart (LDP)........................................................................................................................................... 601
graceful-restart (OSPFv2)..................................................................................................................................602
graceful-restart (OSPFv3)..................................................................................................................................604
graceful-restart helper (OSPFv3)................................................................................................................... 605
graceful-restart helper-disable (IS-IS)..........................................................................................................606
graceful-shutdown................................................................................................................................................. 607
grub ..............................................................................................................................................................................609
guard-time...................................................................................................................................................................610
handle-isis-neighbor-down...................................................................................................................................611
hardware.......................................................................................................................................................................613
hardware media-database activate.................................................................................................................614
hardware smt..............................................................................................................................................................615
hello (LLDP)................................................................................................................................................................616
hello (MPLS RSVP).................................................................................................................................................. 617
hello (UDLD)...............................................................................................................................................................619
hello padding............................................................................................................................................................ 620
hello-acknowledgements.................................................................................................................................... 622
ip arp-aging-timeout ............................................................................................................................................687
ip dhcp relay address .......................................................................................................................................... 689
ip dhcp relay gateway.......................................................................................................................................... 690
ip dhcp snooping..................................................................................................................................................... 691
ip dhcp snooping enable.....................................................................................................................................692
ip dhcp snooping information option...........................................................................................................693
ip dhcp snooping trust.........................................................................................................................................694
ip directed-broadcast .......................................................................................................................................... 695
ip dns ........................................................................................................................................................................... 696
ip extcommunity-list..............................................................................................................................................698
ip flowspec rules statistics................................................................................................................................. 700
ip forward.....................................................................................................................................................................701
ip global-subnet-broadcast-acl........................................................................................................................702
ip icmp-fragment enable.....................................................................................................................................703
ip icmp rate-limiting .............................................................................................................................................704
ip icmp redirect........................................................................................................................................................705
ip icmp unreachable.............................................................................................................................................. 706
ip igmp immediate-leave ................................................................................................................................... 707
ip igmp last-member-query-interval ............................................................................................................708
ip igmp query-interval .........................................................................................................................................709
ip igmp query-max-response-time ................................................................................................................ 710
ip igmp router-alert-check-disable................................................................................................................... 711
ip igmp snooping enable .....................................................................................................................................712
ip igmp snooping fast-leave .............................................................................................................................. 713
ip igmp snooping last-member-query-interval......................................................................................... 714
ip igmp snooping mrouter interface ..............................................................................................................715
ip igmp snooping querier enable .................................................................................................................... 716
ip igmp snooping query-interval.......................................................................................................................717
ip igmp snooping query-max-response-time.............................................................................................718
ip igmp snooping static-group.......................................................................................................................... 719
ip igmp snooping version................................................................................................................................... 720
ip igmp ssm-map......................................................................................................................................................721
ip igmp static-group .............................................................................................................................................723
ip igmp version.........................................................................................................................................................724
ip interface loopback (overlay gateway)..................................................................................................... 725
ip irdp............................................................................................................................................................................ 726
ip large-community-list extended................................................................................................................... 727
ip large-community-list standard.................................................................................................................... 728
ip mtu .......................................................................................................................................................................... 730
ip option disable ..................................................................................................................................................... 732
ip ospf active ............................................................................................................................................................733
ip ospf area ............................................................................................................................................................... 734
ip ospf auth-change-wait-time ........................................................................................................................735
ip ospf authentication-key .................................................................................................................................737
ip ospf bfd...................................................................................................................................................................738
ip ospf cost ............................................................................................................................................................... 739
ip ospf database-filter .........................................................................................................................................740
ip ospf dead-interval ............................................................................................................................................ 742
ip ospf hello-interval .............................................................................................................................................743
key-rollover-interval............................................................................................................................................... 875
key-string.................................................................................................................................................................... 876
keychain....................................................................................................................................................................... 877
keypair.......................................................................................................................................................................... 878
label-withdrawal-delay ........................................................................................................................................879
lacp auto ......................................................................................................................................................................881
lacp default-up ........................................................................................................................................................882
lacp port-priority ....................................................................................................................................................883
lacp system-id ......................................................................................................................................................... 884
lacp system-priority ..............................................................................................................................................885
lacp timeout ............................................................................................................................................................. 886
lacp-pdu-forward enable.....................................................................................................................................887
lag hash........................................................................................................................................................................888
ldap-server host .......................................................................................................................................................891
ldap-server maprole .............................................................................................................................................894
ldp...................................................................................................................................................................................895
ldp-enable...................................................................................................................................................................896
ldp-params................................................................................................................................................................. 897
ldp-sync....................................................................................................................................................................... 898
left-interface vlan................................................................................................................................................... 900
license add ................................................................................................................................................................902
license eula................................................................................................................................................................ 904
line vty exec-timeout ...........................................................................................................................................906
link-error-disable..................................................................................................................................................... 907
link-fault-signal........................................................................................................................................................ 909
link-oam allow-loopback........................................................................................................................................911
link-oam enable......................................................................................................................................................... 912
link-oam remote-failure......................................................................................................................................... 913
link-oam remote-loop-back................................................................................................................................ 914
listen-limit.....................................................................................................................................................................915
listen-range ................................................................................................................................................................ 917
lldp profile ...................................................................................................................................................................919
load-balance hash.................................................................................................................................................. 920
load-sharing............................................................................................................................................................... 922
local-as ........................................................................................................................................................................ 923
local-switching......................................................................................................................................................... 924
log (OSPFv2).............................................................................................................................................................925
log (OSPFv3).............................................................................................................................................................927
log adjacency............................................................................................................................................................929
log invalid-lsp-packets......................................................................................................................................... 930
log-dampening-debug ......................................................................................................................................... 931
log-shell........................................................................................................................................................................932
logging auditlog class ..........................................................................................................................................933
logging raslog console ........................................................................................................................................934
logging raslog console stop...............................................................................................................................935
logging syslog-facility local .............................................................................................................................. 936
logging syslog-server ...........................................................................................................................................937
logging syslog-server-host ............................................................................................................................... 939
logging utility ............................................................................................................................................................941
logical-interface....................................................................................................................................................... 943
loop-detection..........................................................................................................................................................946
loop-detection shutdown-disable.................................................................................................................. 948
loop-detection vlan............................................................................................................................................... 949
lsp................................................................................................................................................................................... 950
lsp (Telemetry) ......................................................................................................................................................... 951
lsp-gen-interval........................................................................................................................................................ 952
lsp-interval.................................................................................................................................................................. 953
lsp-refresh-interval................................................................................................................................................. 954
lsr-id ..............................................................................................................................................................................955
ma-name..................................................................................................................................................................... 956
mac access-group ................................................................................................................................................. 958
mac access-list extended .................................................................................................................................. 960
mac access-list standard .....................................................................................................................................961
mac-address withdrawal..................................................................................................................................... 962
mac-address-table aging-time.........................................................................................................................964
mac-address-table mac-move..........................................................................................................................965
mac-address-table static ................................................................................................................................... 967
maid-format ............................................................................................................................................................. 969
management-heartbeat manager (management-heartbeat).......................................................... 970
management-security ......................................................................................................................................... 972
manual-switch vlan.................................................................................................................................................973
map bridge-domain (overlay gateway)....................................................................................................... 974
map dscp.....................................................................................................................................................................975
map vlan .....................................................................................................................................................................977
map vni auto (VXLAN gateway)..................................................................................................................... 979
master-vlan (STP).................................................................................................................................................. 980
match (route maps)................................................................................................................................................ 981
match access-group .............................................................................................................................................985
match additional-paths advertise-set...........................................................................................................986
match bridge-domain...........................................................................................................................................988
match community ................................................................................................................................................. 989
match destination-port........................................................................................................................................990
match dscp................................................................................................................................................................ 992
match extcommunity............................................................................................................................................994
match fragment-type............................................................................................................................................995
match ip.......................................................................................................................................................................997
match ip address acl ............................................................................................................................................ 998
match ip icmp-code.............................................................................................................................................. 999
match ip icmp-type...............................................................................................................................................1001
match ipv6 address acl...................................................................................................................................... 1003
match large-community....................................................................................................................................1004
match packet-length...........................................................................................................................................1005
match port................................................................................................................................................................1007
match protocol.......................................................................................................................................................1009
match rpki................................................................................................................................................................... 1011
match source-port................................................................................................................................................. 1013
match tcp-flags....................................................................................................................................................... 1015
match vlan ................................................................................................................................................................ 1018
neighbor additional-paths................................................................................................................................1090
neighbor additional-paths advertise............................................................................................................1092
neighbor additional-paths disable................................................................................................................1094
neighbor advertisement-interval ..................................................................................................................1096
neighbor allowas-in .............................................................................................................................................1098
neighbor alternate-as ......................................................................................................................................... 1100
neighbor announce-rpki-state..........................................................................................................................1102
neighbor as-override ........................................................................................................................................... 1104
neighbor bfd ............................................................................................................................................................1106
neighbor capability as4 ......................................................................................................................................1108
neighbor capability orf prefixlist...................................................................................................................... 1110
neighbor default-originate ................................................................................................................................. 1112
neighbor description .............................................................................................................................................1113
neighbor ebgp-btsh ...............................................................................................................................................1115
neighbor ebgp-multihop ..................................................................................................................................... 1117
neighbor enable-peer-as-check........................................................................................................................1118
neighbor encapsulation........................................................................................................................................ 1119
neighbor enforce-first-as ...................................................................................................................................1120
neighbor filter-list .................................................................................................................................................. 1122
neighbor flowspec redirect................................................................................................................................ 1124
neighbor flowspec validation............................................................................................................................1126
neighbor graceful-restart ...................................................................................................................................1128
neighbor graceful-shutdown ........................................................................................................................... 1130
neighbor local-as ................................................................................................................................................... 1133
neighbor maxas-limit in ...................................................................................................................................... 1135
neighbor maximum-prefix .................................................................................................................................1137
neighbor next-hop-self ...................................................................................................................................... 1140
neighbor next-hop-unchanged........................................................................................................................1142
neighbor password ...............................................................................................................................................1143
neighbor peer-dampening ................................................................................................................................1145
neighbor peer-dampening (peer-group) ...................................................................................................1147
neighbor peer-group ........................................................................................................................................... 1149
neighbor peer-group-name alternate-as-range...................................................................................... 1150
neighbor prefix-list ................................................................................................................................................. 1151
neighbor remote-as .............................................................................................................................................. 1153
neighbor remove-private-as.............................................................................................................................. 1155
neighbor route-map ............................................................................................................................................. 1157
neighbor route-reflector-client ....................................................................................................................... 1159
neighbor send-community .................................................................................................................................1161
neighbor shutdown .............................................................................................................................................. 1163
neighbor soft-reconfiguration inbound ...................................................................................................... 1165
neighbor static-network-edge......................................................................................................................... 1166
neighbor timers ...................................................................................................................................................... 1167
neighbor unsuppress-map ................................................................................................................................1169
neighbor update-source ......................................................................................................................................1171
neighbor weight ..................................................................................................................................................... 1173
net...................................................................................................................................................................................1175
network .......................................................................................................................................................................1176
next-hop-enable-default .................................................................................................................................... 1178
next-hop-mpls.......................................................................................................................................................... 1179
next-hop-recursion ................................................................................................................................................ 1181
no debug.....................................................................................................................................................................1182
node.............................................................................................................................................................................. 1184
non-revertive-mode...............................................................................................................................................1185
nonstop-routing (IS-IS)........................................................................................................................................1186
nonstop-routing (OSPF)..................................................................................................................................... 1187
notification-timer.................................................................................................................................................... 1188
ntp authenticate......................................................................................................................................................1189
ntp authentication-key ....................................................................................................................................... 1190
ntp disable..................................................................................................................................................................1192
ntp peer....................................................................................................................................................................... 1193
ntp server .................................................................................................................................................................. 1195
ntp trusted-key........................................................................................................................................................ 1197
operational-state.....................................................................................................................................................1198
optimized replication............................................................................................................................................ 1199
oscmd......................................................................................................................................................................... 1200
overlay access-group...........................................................................................................................................1202
overlay access-list type vxlan extended.................................................................................................... 1203
overlay access-list type vxlan standard .................................................................................................... 1204
overlay-gateway ....................................................................................................................................................1205
overlay-service-policy......................................................................................................................................... 1207
overlay-transit......................................................................................................................................................... 1209
partial-spf-interval..................................................................................................................................................1210
password-attributes ...............................................................................................................................................1211
password-encryption convert-enc-to-level-10......................................................................................... 1215
path................................................................................................................................................................................1216
pdu-rate....................................................................................................................................................................... 1218
peer................................................................................................................................................................................1219
peer (MCT)................................................................................................................................................................ 1222
peer-dampening ....................................................................................................................................................1223
peer-interface.......................................................................................................................................................... 1225
peer-keepalive (optional).................................................................................................................................. 1226
penalty........................................................................................................................................................................ 1228
permit ip host.......................................................................................................................................................... 1229
ping ...............................................................................................................................................................................1231
pki ocsp...................................................................................................................................................................... 1234
police cir.....................................................................................................................................................................1236
policy-map ............................................................................................................................................................... 1238
port-channel path-cost ..................................................................................................................................... 1240
preempt-mode .......................................................................................................................................................1242
prefix-independent-convergence.................................................................................................................. 1243
primary-path............................................................................................................................................................1244
priority ....................................................................................................................................................................... 1246
priority-group-table ............................................................................................................................................ 1247
priority-table ...........................................................................................................................................................1249
process-restart......................................................................................................................................................... 1251
profile (LLDP) .........................................................................................................................................................1254
profile (telemetry)................................................................................................................................................. 1256
profile counters.......................................................................................................................................................1258
profile etcam............................................................................................................................................................1260
profile lag.................................................................................................................................................................... 1261
profile qos ................................................................................................................................................................ 1263
profile route..............................................................................................................................................................1264
profile tcam...............................................................................................................................................................1267
profile tcam cam-share.......................................................................................................................................1269
protocol........................................................................................................................................................................1271
protocol cfm ............................................................................................................................................................1272
protocol link-oam ................................................................................................................................................. 1273
protocol lldp ............................................................................................................................................................1274
protocol loop-detection......................................................................................................................................1275
protocol mvrp..........................................................................................................................................................1276
protocol spanning-tree ...................................................................................................................................... 1277
protocol udld .......................................................................................................................................................... 1279
protocol vrrp .......................................................................................................................................................... 1280
protocol vrrp-extended ...................................................................................................................................... 1281
prune-wait................................................................................................................................................................. 1282
pw-profile.................................................................................................................................................................. 1283
pw-profile (bridge domain).............................................................................................................................. 1285
python......................................................................................................................................................................... 1286
qos cos-traffic-class............................................................................................................................................. 1289
qos cpu slot ............................................................................................................................................................ 1290
qos dscp-cos .......................................................................................................................................................... 1292
qos dscp-mutation .............................................................................................................................................. 1293
qos dscp-traffic-class .........................................................................................................................................1294
qos flowcontrol....................................................................................................................................................... 1295
qos map cos-mutation .......................................................................................................................................1297
qos map cos-traffic-class.................................................................................................................................. 1299
qos map dscp-cos ................................................................................................................................................ 1301
qos map dscp-mutation ................................................................................................................................... 1303
qos map dscp-traffic-class ..............................................................................................................................1305
qos map traffic-class-cos .................................................................................................................................1307
qos port-speed-up............................................................................................................................................... 1309
qos random-detect traffic-class......................................................................................................................1310
qos red-profile........................................................................................................................................................... 1311
qos rx-queue cos-threshold ............................................................................................................................. 1313
qos rx-queue multicast........................................................................................................................................ 1314
qos rx-queue unicast traffic-class...................................................................................................................1316
qos service-policy...................................................................................................................................................1317
qos traffic-class ...................................................................................................................................................... 1318
qos traffic-class-cos.............................................................................................................................................. 1319
qos-mpls map dscp-exp.................................................................................................................................... 1320
qos-mpls map exp-dscp .................................................................................................................................... 1321
qos-mpls map exp-traffic-class ..................................................................................................................... 1322
qos-mpls map traffic-class-exp...................................................................................................................... 1324
qos-mpls map-apply dscp-exp.......................................................................................................................1326
qos-mpls map-apply exp-dscp....................................................................................................................... 1327
qos-mpls map-apply exp-traffic-class........................................................................................................ 1328
summary-prefix..................................................................................................................................................... 2289
support autoupload-param.............................................................................................................................. 2291
suppress-arp........................................................................................................................................................... 2292
suppress-nd.............................................................................................................................................................2293
switch-attributes...................................................................................................................................................2294
switchport ............................................................................................................................................................... 2295
switchport access ............................................................................................................................................... 2296
switchport mode ................................................................................................................................................. 2297
switchport mode trunk-no-default-native .............................................................................................. 2298
switchport port-security ..................................................................................................................................2299
switchport port-security mac-address .................................................................................................... 2300
switchport port-security max ........................................................................................................................ 2301
switchport port-security shutdown-time ................................................................................................2302
switchport port-security sticky ....................................................................................................................2303
switchport port-security violation ..............................................................................................................2304
switchport trunk allowed ................................................................................................................................ 2305
switchport trunk native-vlan-untagged ...................................................................................................2306
switchport trunk native-vlan-xtagged ......................................................................................................2307
switchport trunk tag native-vlan .................................................................................................................2309
sync-interval.............................................................................................................................................................2310
sysmon fe-acces-check ..................................................................................................................................... 2312
sysmon link-crc-monitoring..............................................................................................................................2314
sysmon sfm-walk .................................................................................................................................................. 2315
system maintenance.............................................................................................................................................2317
system maintenance turn-off...........................................................................................................................2319
system-description .............................................................................................................................................2320
system-monitor tm................................................................................................................................................2321
system-monitor-mail ..........................................................................................................................................2322
system-monitoring power alert state removed action raslog........................................................ 2324
system power-cycle-db-shutdown.............................................................................................................. 2325
system-name ......................................................................................................................................................... 2326
table-map ................................................................................................................................................................ 2327
tacacs-server ......................................................................................................................................................... 2329
tag-type ................................................................................................................................................................... 2332
telemetry client-cert........................................................................................................................................... 2334
telemetry collector...............................................................................................................................................2335
telemetry profile....................................................................................................................................................2336
telemetry profile (MPLS).................................................................................................................................. 2339
telemetry server..................................................................................................................................................... 2341
telnet...........................................................................................................................................................................2342
telnet server............................................................................................................................................................ 2344
terminal......................................................................................................................................................................2345
test-profile .............................................................................................................................................................. 2347
threshold...................................................................................................................................................................2348
threshold (ETH-DM) .......................................................................................................................................... 2349
threshold (ETH-SLM) ........................................................................................................................................ 2350
threshold-monitor Cpu ..................................................................................................................................... 2352
threshold-monitor memory ............................................................................................................................2354
threshold-monitor sfp ....................................................................................................................................... 2356
trustpoint sign.........................................................................................................................................................2441
ttl.................................................................................................................................................................................. 2442
tunable-optics........................................................................................................................................................2443
tunneled-arp-trap enable................................................................................................................................. 2448
tx-frame-count ..................................................................................................................................................... 2449
tx-interval ................................................................................................................................................................2450
tx-label-silence-timer........................................................................................................................................... 2451
type ............................................................................................................................................................................ 2452
udld enable .............................................................................................................................................................2453
underflow-limit...................................................................................................................................................... 2454
underlay-mdt-default-group...........................................................................................................................2455
underlay-mdt-group........................................................................................................................................... 2456
undeploy-force ..................................................................................................................................................... 2458
unlock username ................................................................................................................................................. 2459
update onie.............................................................................................................................................................2460
update-time ............................................................................................................................................................ 2461
usb ..............................................................................................................................................................................2463
usb dir .......................................................................................................................................................................2464
usb remove .............................................................................................................................................................2465
use-v2-checksum................................................................................................................................................. 2466
user (alias configuration)..................................................................................................................................2467
username ................................................................................................................................................................ 2468
username .................................................................................................................................................................. 2471
vc-id.............................................................................................................................................................................2472
vc-mode.................................................................................................................................................................... 2473
version (ERP)..........................................................................................................................................................2475
virtual-ip ...................................................................................................................................................................2476
virtual-mac ............................................................................................................................................................. 2478
vlan.............................................................................................................................................................................. 2479
vlan (EVPN)............................................................................................................................................................ 2480
vpn-statistics.......................................................................................................................................................... 2482
vrf ................................................................................................................................................................................2483
vrf (epvn IRB) ....................................................................................................................................................... 2484
vrf forwarding........................................................................................................................................................ 2486
vrf-lite-capability ................................................................................................................................................. 2487
vrrp-acceptmode-disable................................................................................................................................ 2488
vrrp-extended-group ........................................................................................................................................ 2489
vrrp-group ..............................................................................................................................................................2490
vtep-discovery ......................................................................................................................................................2492
write erase............................................................................................................................................................... 2493
wtb-time................................................................................................................................................................... 2494
wtr-time.................................................................................................................................................................... 2495
y1731 ...........................................................................................................................................................................2496
Text Conventions
Unless otherwise noted, information in this document applies to all supported environments for the
products in question. Exceptions, like command keywords associated with a specific software version,
are identified in the text.
When a feature, function, or operation pertains to a specific hardware product, the product name is
used. When features, functions, and operations are the same across an entire product family, such as
ExtremeSwitching switches or SLX routers, the product is referred to as the switch or the router.
Table 2: Text
Convention Description
screen displays This typeface indicates command syntax, or represents information as
it is displayed on the screen.
The words enter and type When you see the word enter in this guide, you must type something,
and then press the Return or Enter key. Do not press the Return or
Enter key when an instruction simply says type.
Key names Key names are written in boldface, for example Ctrl or Esc. If you must
press two or more keys simultaneously, the key names are linked with a
plus sign (+). Example: Press Ctrl+Alt+Del
Words in italicized type Italics emphasize a point or denote new terms at the place where they
are defined in the text. Italics are also used when referring to
publication titles.
New information. In a PDF, this is searchable text.
Extreme Networks offers product training courses, both online and in person, as well as specialized
certifications. For details, visit www.extremenetworks.com/education/.
Before contacting Extreme Networks for technical support, have the following information ready:
• Your Extreme Networks service contract number, or serial numbers for all involved Extreme
Networks products
• A description of the failure
• A description of any actions already taken to resolve the problem
• A description of your network environment (such as layout, cable type, other relevant environmental
information)
• Network load at the time of trouble (if known)
• The device history (for example, if you have returned the device before, or if this is a recurring
problem)
• Any related RMA (Return Material Authorization) numbers
1. Go to The Hub.
2. In the list of categories, expand the Product Announcements list.
3. Select a product for which you would like to receive notifications.
4. Select Subscribe.
5. To select additional products, return to the Product Announcements list and repeat steps 3 and 4.
Send Feedback
The Information Development team at Extreme Networks has made every effort to ensure that this
document is accurate, complete, and easy to use. We strive to improve our documentation to help you
in your work, so we want to hear from you. We welcome all feedback, but we especially want to know
about:
• Content errors, or confusing or conflicting information.
Provide the publication title, part number, and as much detail as possible, including the topic heading
and page number if applicable, as well as your suggestions for improvement.
New commands
The following commands are added:
• neighbor peer-dampening
• neighbor peer-dampening (peer-group)
• peer-dampening
• show grubversion
• show [ip|ipv6] bgp peer-dampened
• show onieversion
• show selinux status
• snmp-server trap
• update onie
Modified commands
The following commands were modified:
• dns (tpvm mode)
• interface management (tpvm mode)
• ntp (tpvm mode)
• set ip next-hop
• set ipv6 next-hop
• speed
• threshold-monitor Cpu
• threshold-monitor Memory
• tpvm download
Deprecated commands
No commands were deprecated in this release.
Supported Hardware
For instances in which a topic or part of a topic applies to some devices but not to others, the topic
specifically identifies the devices.
Note
All configurations and software features that are applicable to SLX 9150 and SLX 9250
devices are also applicable for the Extreme 8520 and Extreme 8720 devices respectively.
The "Measured Boot with Remote Attestation" feature is only applicable to the Extreme 8520
and Extreme 8720 devices. It is not supported on the SLX 9150 and SLX 9250 devices.
Note
Although many software and hardware configurations are tested and supported for this
release, documenting all possible configurations and scenarios is beyond this document's
scope.
For information about other releases, see the documentation for those releases.
User accounts
A user account specifies that user's level of access to the device CLI.
The SLX-OS software uses role-based access control (RBAC) as the authorization mechanism. A role is a
container for rules, which specify which commands can be executed and with which permissions. When
you create a user account you need to specify a role for that account. In general, user (as opposed to
user-level) refers to any account—to which any role can be assigned—user, admin, or a non-default role.
The software ships with two default accounts—admin and user—and two corresponding default roles:
• admin—Accounts with admin permissions can execute all commands supported on the device. (For
the initial admin login, refer to the relevant Hardware Installation Guide.)
• user—Accounts with user-level permissions can execute all show commands supported on the
device. User-level accounts can also execute the following operational commands: cfm, execute-
script, exit, mtrace, no, ping, rasman, ssh, sysmon, telnet, timestamp, trace-l2,
and traceroute.
For more information on user accounts and roles, refer to the Extreme SLX-OS Security Configuration
Guide.
For more information on a serial console connection, see the relevant SLX-OS Hardware Installation
Guide. For information on a session connection, see the Extreme SLX-OS Management Configuration
Guide.
The procedure to access the CLI is the same through either the console interface or through a Telnet or
SSH session; both access methods bring you to the login prompt. The following example shows the
admin role logging into the device:
device login: admin
Password:**********
device#
Note
Multiple users can open sessions on the device and issue commands. The device supports a
maximum of 32 CLI sessions.
Command modes
The SLX-OS CLI uses an industry-standard hierarchical shell familiar to networking administrators.
For example, if you are configuring an Ethernet interface and you want to execute a privileged EXEC
mode command, such as the dir command, you would first have to exit the Interface configuration
mode. By using the do command with the dir command, you can ignore the need to change
configuration modes, as shown in the following example.
device(config-if-eth-1/2)# do dir
total 32
drwxrwxr-x 3 21487 1011 4096 Mar 26 17:58 .
drwxrwxr-x 3 21487 1011 4096 Mar 13 06:45 ..
-rw-r--r-- 1 root sys 495 Mar 16 15:41 defaultconfig.cluster
-rw-r--r-- 1 root sys 210 Mar 16 15:41 defaultconfig.standalone
drwxrwxr-x 5 root sys 4096 Mar 26 17:57 flex-cli
-rw-r--r-- 1 root root 11093 Mar 26 18:04 startup-config
Enter a question mark (?) in any command mode to display the list of commands available in that
mode.
device# ?
Possible completions:
alias Creat/Update Alias
beacon Enable/Disable beacon
cd Change working directory
certutil Security Certificate Management Operations
cfm
cipherset Configure FIPS-compliant secure ciphers for RADIUS/LDAP
clear Clear parameter
clock set switch date, time, and timezone
cluster Cluster
configure Manipulate software configuration information
copy RAS copy operation
crypto Crypto Certificate Management Operations
debug Debugging Options
delete delete a file
devtools Enable/disable development tools
df show filesystem disk space usage
dhcp Commands to manage DHCP auto-deployment
(output truncated)
To display a list of commands that start with the same characters, type the characters followed by a
question mark (? ).
device# e?
Possible completions:
event-handler Event Handler Commands
execute-script Run user-level BASH scripts
exit Exit the management session
To display the keywords and arguments associated with a command, enter the keyword followed by a
space a then a question mark (?).
device# terminal ?
Possible completions:
length Sets Terminal Length for this session
monitor Enables terminal monitoring for this session
no Sets Terminal Length for this session to default :24.
timeout Sets the interval that the EXEC command interpreter wait for user input.
If the question mark (?) is typed within an incomplete keyword, but the keyword matches several
keywords, the CLI displays help for all the matching keywords.
device# show d?
Possible completions:
debug Display the udld debug configuration
defaults Display default configuration
dot1x Show dot1x
The CLI accepts abbreviations for commands. This example is the abbreviation for the show qos
interface all command.
device# sh q i a
If the device does not recognize a command after you press Enter, an error message displays.
device# hookup
^
syntax error: unknown argument.
If there is more than one command or keyword associated with the characters typed, the CLI displays all
choices. For example, at the CLI command prompt, type show l and press Tab.
device# show l
The first example shows the use of the ! symbol to introduce a blank line for better visibility and
grouping of commands within the output of a command. The second example shows how the mark is
used to indicate empty lines within the output of the show running-config command.
configure terminal
!
crypto ca trustpoint t1 ! configure a trustpoint
keypair k1 ! configure the keypair
!
do show running-config crypto ! view the configuration
SLX(config-management-heartbeat-manage) # no action
SLX(config-management-heartbeat-manage)# do show running-config management-heartbeat
manager
management-heartbeat manager
enable
threshold-timer 1
action no-action
!
SLX(config-management-heartbeat-manage)#
Note
In privileged EXEC mode, use the show history command to list the commands most
recently entered. The device retains the history of the last 1000 commands entered for the
current session.
However, characters dependent on combinations of the AltGr key and another key are never supported.
Note
The AltGr key is the Alt key to the right of the spacebar.
Extreme Networks recommends that you work closely with Extreme technical support in executing
such commands and interpreting their results.
Note
Not all diagnostic commands are documented.
Procedure
3. Enter the alias command, specifying the alias and its corresponding command.
device(config-alias-config)# alias ck "show clock"
Procedure
4. Enter the alias command, specifying the alias and its corresponding command.
device(config-user-jdoe)# alias int2 "interface ethernet 1/2"
Note
The following verification example assumes that the user jdoe defined the user-level alias
"int2". If an admin defined the alias for this user, the example would show the admin
logging out of the CLI and jdoe logging into the CLI.
device(config-alias-config)# exit
device(config-user-jdoe)# exit
device(config-alias-config)# exit
device(config)# int2
<Displayed automatically:>
device(config)#interface ethernet 1/2
device(config-if-eth-1/2)#
aaa accounting
Enables accounting for command or login information; information is forwarded to the accounting
server.
Syntax
aaa accounting { commands | exec } default start-stop [ none | radius |
tacacs+ ]
no aaa accounting { commands | exec } default start-stop [ none | radius
| tacacs+ ]
Command Default
Accounting is disabled.
Parameters
commands
Causes command accounting.
exec
Causes login accounting.
default
Causes the sending of logged information to the default server.
start-stop
Causes the sending of a "start" accounting notice at the beginning of a process and a "stop"
accounting notice at the end of a process. The "start" accounting record is sent in the
background. The requested user process begins regardless of whether the "start" accounting
notice was received by the accounting server.
none
Disables accounting services.
radius
Specifies using the RADIUS server for accounting.
tacacs+
Specifies using the TACACS+ server for accounting.
Modes
Global configuration mode
Usage Guidelines
Before enabling login (EXEC) or command accounting for RADIUS, at least one RADIUS server must be
configured on the device.
• traceroute
• quit
• help
The no form of the command disables accounting. You can also disable accounting by using the aaa
accounting command specifying the none option.
Examples
The following example configures command accounting, with the CLI information being forwarded to
the TACACS+ server.
device(config)# aaa accounting commands default start-stop tacacs+
The following example configures command accounting, with the CLI information being forwarded to
the RADIUS server.
device(config)# aaa accounting commands default start-stop radius
The following example disables login accounting by specifying the none option; command accounting
(when also configured) remains active.
device(config)# aaa accounting exec default start-stop none
The following example disables login accounting by using the no aaa accounting command;
command accounting (when also configured) remains active.
device(config)# no aaa accounting exec default start-stop
aaa authentication
Configures the Authentication, Accounting, and Authorization (AAA) log-in sequence.
Syntax
aaa authentication login { default | ldap | local | oauth2| radius |
tacacs+} { local | local-auth-fallback }
no aaa authentication login
Command Default
The default server is Local.
Parameters
login
Specifies the type of server that will be used for AAA on the device. The local server is the
default. Specify one of the following options.
default
Specifies the default mode (local server). Authenticates the user against the local database only.
If the password does not match or the user is not defined, the login fails.
ldap
Specifies the Lightweight Directory Access Protocol (LDAP) servers.
local
Specifies the local device database if previous authentication methods are inactive.
oauth2
Specifies the OAuth2 token.
radius
Specifies the RADIUS servers.
tacacs+
Specifies the TACACS+ servers.
local-auth-fallback
Specifies the local device database if previous authentication methods are not active or if
authentication fails.
Modes
Global configuration mode
Usage Guidelines
This command selects the order of authentication sources to be used for user authentication during the
login process. Two sources are supported: primary and secondary. The secondary source of
authentication is optional and will be used if the primary source fails or is not available.
The authentication mode can only be set and cannot be added or deleted. For example, to change a
configuration from "radius local" to radius only, execute the no aaa authentication login
command to resets the configuration to the default mode, and then reconfigure the AAA mode with the
desired setting.
In a configuration with primary and secondary sources of authentication, the primary mode cannot be
modified alone. For example, you cannot change from “radius local" or "radius local-auth-fallback” to
“tacacs+ local" or "tacacs+ local-auth-fallback” respectively. First remove the existing configuration and
then configure it to the required configuration.
With OAuth2 authentication, the log-in request from the north-bound interface uses the OAuth2 token
as a password. The device authenticates the user based on the validity of the OAuth2 token. Only in
OAuth2 authentication, the local and local-auth-fallback options allow fallback to the local database if
the secondary source of authentication is configured as "local" or "local-auth-fallback".
If login fails through the primary source because none of the configured servers respond or the login is
rejected by the server, authentication is done again through the secondary source or local option.
When “local-auth-fallback” option is specified, local authentication is tried only when the primary AAA
authentication service (TACACS+/Radius/LDAP) is either “unreachable” or “not available”. Unlike the
“local” option, local authentication is not be attempted if the authentication with primary service fails.
Use the no form of the command to restore the authentication mode to local mode.
Examples
This example changes the AAA server to TACACS+ using the local device database as a secondary
source of authentication.
device# configure terminal
device(config)# aaa authentication login tacacs+ local
Broadcast message from root (pts/0) Tue Apr 5 16:34:12 2011...
This example changes the AAA server from TACACS+ and local to TACACS+ only (no secondary
source).
device# configure terminal
device(config)# no aaa authentication login tacacs+ local
device(config)# aaa authentication login tacacs+
device(config)# show running-config aaa
aaa authentication login tacacs+
Syntax
aaa authorization command { none | tacacs+ [ local ] }
no aaa authorization command
Command Default
By default, AAA command authorization is disabled.
Parameters
none
Disables command authorization.
tacacs+
Specifies using TACACS+ servers for command authorization.
local
Specifies using local authorization when the TACACS+ server is not active.
Modes
Global configuration mode.
Usage Guidelines
You can only enable command authorization when at least one TACACS+ server host is configured.
When a TACACS+ server is not configured and you attempt to enable command authorization, the
following error message is displayed and added to syslog.
% Error: No active TACACS server configuration exists to support the mode.
Similarly, when command authorization is enabled and there is only one TACACS+ server configured,
you cannot remove the TACACS+ server (using the no tacacs-server command).
When, based on TACACS+ server configuration, the TACACS+ server rejects a command authorization
request, the following error message is displayed and added to syslog.
Aborted: permission denied
With the current version of confd, custom RPC REST queries do not work when the aaa
authorization command tacacs+ local form of the command is configured.
Examples
The following example shows how to enable AAA command authorization on a TACACS+ server and
specify using local authorization if the TACACS+ server is not active.
device# configure terminal
device(config)# aaa authorization command tacacs+ local
accept-lifetime
Defines the time period when a key is active.
Syntax
accept-lifetime [ local { true | false}] { start-time | infinite | end-
time }
no accept-lifetime
Command Default
By default, the key lifetime is infinite. The key is always valid.
Parameters
local { true | false}
By default, the device treats the start time and end time as UTC. Specify the local key word to
use local times.
start-time
Specifies the time of day and date when the key becomes active. In HH:MM:SS|MM/DD/YYYY
format.
end-time
Specifies the time of day and date when the key expires. In HH:MM:SS|MM/DD/YYYY format.
infinite
Indicates that the accept lifetime of the key never expires.
Modes
Key configuration mode
Usage Guidelines
Use the no form of the command to revert to the default lifetime.
Examples
The following example configures a lifetime from June 6 2020 to December 4 2020 (UTC) for key 10 in
key chain 1.
device# configure terminal
device(config)# keychain keychain1
device(config-keychain1)# key 10
device(config-keychain1-key10)# accept-lifetime 00:00:00|06/04/2020 23:59:59|12/04/2020
The following example configures a lifetime from June 6 2020 to December 4 2020 (local) for key 10 in
key chain 1.
device# configure terminal
device(config)# keychain keychain1
device(config-keychain1)# key 10
device(config-keychain1-key10)# accept-lifetime local true 00:00:00|06/04/2020 23:59:59|
12/04/2020
accept-tolerance
Defines the number of seconds for which expired or soon-to-be activated keys can be used for
validating received packets.
Syntax
accept-tolerance number-of-seconds
no accept-tolerance
Command Default
By default, the accept tolerance time is 600 seconds.
Parameters
number-of-seconds
Specifies the number of seconds by which activation time is decreased or expiration time is
decreased. The default is 600. Valid values range from 0 to 600.
Modes
Keychain configuration mode
Usage Guidelines
Use the no form of the command to revert to the default of 600 seconds.
You can use the command to extend the validity of an expired key to ensure a smooth key rollover for
the processing of a received packet.
You can use the command to decrease the activation time of a new key so that a received packet can be
authenticated with the new key.
A longer accept tolerance period can reduce security if an old key was exposed.
Examples
The following example configures an accept tolerance of 500 seconds in key chain 1.
device# configure terminal
device(config)# keychain keychain1
device(config-keychain1)# accept-tolerance 500
action (management-heartbeat)
Specifies an action to be performed when the SLX device does not receive heartbeat messages from
EFA within a preconfigured threshold time duration.
Syntax
action { maintenance-mode-enable | no-action }
no action
Parameters
maintenance-mode-enable
Sets the SLX device into the maintenance mode.
no-action
This is the default. No action is performed when the SLX device does not receive a heartbeat
message from EFA within the threshold time.
Modes
Management Heartbeat mode
Usage Guidelines
You can assign only one action from the list.
Examples
The following example configures the action which sets the SLX device into maintenance mode.
SLX(config-management-heartbeat-manage) # action management-mode-enable
SLX(config-management-heartbeat-manage)# do show running-config management-heartbeat
manager
management-heartbeat manager
enable
threshold-timer 1
action maintenance-mode-enable
!
SLX(config-management-heartbeat-manage)#
The following example configures the action as no-action. When the SLX devices does not receive any
heartbeat messages from EFA and the threshold time has exceed, no action is taken.
SLX(config-management-heartbeat-manage) # action no-action
SLX(config-management-heartbeat-manage)# do show running-config management-heartbeat
manager
management-heartbeat manager
enable
threshold-timer 1
action no-action
!
SLX(config-management-heartbeat-manage)#
The following example resets the current action to the default action. The default action for
Management Heartbeat context is no-action.
SLX(config-management-heartbeat-manage) # no action
SLX(config-management-heartbeat-manage)# do show running-config management-heartbeat
manager
management-heartbeat manager
enable
threshold-timer 1
action no-action
!
SLX(config-management-heartbeat-manage)#
acl-log-raslog
Enables Raslog messages for ACL rules with log keywords, and specifies how long the system waits
before sending an ACL Raslog message.
Syntax
acl-log-raslog [ log-interval minutes ]
no acl-log-raslog
no acl-log-raslog log-interval
Command Default
ACL Raslogs are not enabled.
Parameters
log-interval minutes
Specifies, in minutes, the interval between ACL Raslog message. Values range from 1 through 10
minutes. The default value is 5 minutes.
Modes
ACL policy configuration mode
Usage Guidelines
When this feature is enabled, the initial Raslog message is generated at the first match for an ACL rule
that includes the log keyword. Consequent Raslog messages are generated according to the current
no acl-log-raslog value.
To restore the default disablement of this feature, use the no acl-log-raslog form of this
command.
To restore the default 5-minute setting of this feature, use the no acl-log-raslog log-interval
form of this command.
Examples
The following example enables ACL Raslogs on the device.
device# configure terminal
device(config)# acl-policy
device(config-acl-policy)# acl-log-raslog
The following example restores the current log-interval setting to the default value of 5 minutes.
device# configure terminal
device(config)# acl-policy
device(config-acl-policy)# acl-log-raslog log-interval 8
acl-mirror
Defines a destination for ACL-based mirroring of a physical interface. This command will be deprecated
in the future.
Syntax
acl-mirror source { ethernet slot / port | port-channel index | ve
index } destination { ethernet slot / port | port-channel index }
no acl-mirror source { ethernet slot / port | port-channel index | ve
index } destination { ethernet slot / port | port-channel index }
Command Default
No ACL mirror is defined.
Parameters
source
Specifies the interface for which you are defining a mirror.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
port-channel index
Specifies a valid port-channel interface number.
ve index
Specifies a valid virtual ethernet interface number.
destination
Specifies the physical-interface or port-channel mirror to use as the destination for mirroring.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
Modes
Global configuration mode
Usage Guidelines
ACL mirroring applies to extended-ACL rules that include the mirror keyword.
There are parsing priorities among the copy-sflow, log, and mirror keywords, as follows:
• Although in a standard-ACL rule you can include log and copy-sflow, only one of the two is
processed, as follows:
◦ In a permit rule, the order of precedence is copy-sflow > log.
◦ In a deny or hard-drop rule, the order of precedence is log > copy-sflow.
• Although in an extended-ACL rule you can include log, mirror, and copy-sflow, only one of the
three is processed, as follows:
◦ In a permit rule, the order of precedence is mirror > copy-sflow > log.
◦ In a deny or hard-drop rule, the order of precedence is log > copy-sflow > mirror.
Examples
The following example defines a physical port as the source port for mirroring.
device# config term
device(config)# acl-mirror source ethernet 0/1 destination ethernet 0/2
The following example defines a Virtual Ethernet port as the source for mirroring.
device# config term
device(config)# acl-mirror source ve 99 destination port-channel 2
The following example displays the running config output for acl-mirror
device# show running-config acl-mirror
acl-mirror source port-channel 10 destination ethernet 0/9
acl-mirror source ve 10 destination ethernet 0/9
acl-policy
Accesses the ACL policy configuration mode, from which you can change the default settings regarding
conflicting and duplicate ACL rules.
Syntax
acl-policy
Modes
Global configuration mode
Usage Guidelines
To return to global configuration mode, enter the exit command.
Examples
The following example accesses the ACL policy configuration mode and then disables the default
restriction on duplicate rules within ACLs.
device# configure terminal
device(config)# acl-policy
device(config-acl-policy)# allow-duplicate-rules
action python-script
Specifies a Python file that runs when a trigger condition occurs.
Syntax
action python-script file-name
no action python-script file-name
Parameters
file-name
Specifies a Python script file-name. Valid values range from 4 through 32 characters (including
the .py extension). The first character must be alphabetic.
Modes
Event-handler configuration mode
Usage Guidelines
You can assign only one action to a given event-handler profile.
You can also specify the Python file as part of the event-handler command.
To change the file assigned to a profile, you do not need to enter the no form of this command. You
only need to enter action python-script file-name, specifying the new file name.
Running this command copies the Python script file from the flash:// directory to the database.
After specifying a file for all relevant event-handler profiles, you can delete it from the flash://
directory.
If the event-handler for which you are modifying this command is active on the device, the changes
take effect with no need to de-activate and re-activate the event-handler.
If an event-handler profile is not activated, the no form of this command deletes its action.
Examples
The following example specifies Python files for two event-handler profiles.
device# configure terminal
device(config)# event-handler eventHandler1
device(config-event-handler-eventHandler1)# action python-script example.py
device(config-event-handler-eventHandler1)# event-handler eventHandler2
device(config-event-handler-eventHandler2)# action python-script example2.py
action-profile
Creates an action profile.
Syntax
action-profile action-profile-name
no action-profile
Parameters:
action-profile-name
Specifies the action profile name. An action profile can be up to 32 characters.
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the corresponding configured action profile also its
association with source and remote MEP pair.
Examples
This example shows how to create an action profile.
device# configure terminal
device (config-cfm)# y1731
device(config-cfm-y1731)# action-profile a1
device(config-cfm-y1731-action-profile-a1)# event ccm-up actions all
action-timeout
For an implementation of an event-handler profile, specifies the maximum number of minutes to wait
for an action-script to complete execution. If the action-timeout expires, then script execution ends.
Syntax
action-timeout minutes
no action-timeout
Command Default
No action timeout is defined.
Parameters
minutes
Specifies the number of minutes to wait for an action-script to complete execution. If you specify
"0", no timeout is set. Valid timeout values are any positive integer.
Modes
Event-handler activation mode
Usage Guidelines
To restore the default setting of no timeout, enter the no form of this command.
Examples
The following example specifies an action timeout of 30 minutes.
device# configure terminal
device(config)# event-handler activate eventHandler1
device(config-activate-eventHandler1)# action-timeout 30
Syntax
activate
no activate
Command Default
The collector is deactivated.
Modes
Telemetry-collector configuration mode
Usage Guidelines
Activates the collector object, which streams telemetry information to the external telemetry collector.
Use the no activate command to disable streaming to the external telemetry collector.
Examples
Typical command execution.
device# configure terminal
device(config)# telemetry collector collector1
device(config-collector-collector1)# ip 10.24.12.87 port 8080
device(config-collector-collector1)# encoding json
device(config-collector-collector1)# profile system-profile
default_system_utilization_statistics
device(config-collector-collector1)# activate
Syntax
activate
no activate
Command Default
The internal gRPC telemetry-server is deactivated.
Modes
Telemetry-server configuration mode
Usage Guidelines
This command activates the internal gRPC telemetry-server.
To disable the internal gRPC telemetry-server, use the no form of this command.
Examples
Typical command execution.
device# configure terminal
device(config)# telemetry server
device(config-server-mgmt-vrf)# activate
device(config-server-mgmt-vrf)#
Syntax
activate
no activate
Command Default
By default, a gateway is not activated during initial configuration.
Modes
Overlay gateway configuration mode
Usage Guidelines
It is recommended that you configure all gateway parameters before activating the gateway. This
operation enables all tunnels that are associated with this gateway.
The following conditions that must be in place before you can execute the activate command:
• Loopback interfaces must be configured on all gateways. Refer to the interface loopback
command,
• The IP address of the VXLAN gateway must be configured. Refer to the ip interface command.
Use the no activate command in VXLAN overlay gateway configuration mode to deactivate the
gateway. All associated tunnels are also deactivated.
Examples
The following example activates a VXLAN gateway named gateway1. The gateway was previously
configured by means of the overlay-gateway command:
adaptive
Bypass LSPs can be made adaptive using the adaptive command. Bypass LSPs are non-adaptive by
default. The user can modify the adaptive bypass LSPs adaptive-parameters without disabling the LSP.
If the LSP is UP, then modifying an adaptive parameter, like exclude-interface or bandwidth, leads to the
creation of a new instance of the bypass LSP. Adaptiveness can be manually enabled by using the
adaptive command and can be disabled by no form of the same command. Use the adaptive to
set the adaptive option for the dynamic bypass LSPs to be created for the MPLS protected interface.
Syntax
adaptive [ disable | enable ] [ record ]
Command Default
By default, LSPs are not adaptive.
Parameters
disable
Disables the adaptive command.
enable
Enables the adaptive command.
record
Specifies RSVP session route recording.
Modes
MPLS LSP configuration mode
Examples
The following example configures an LSP named to20 as an adaptive LSP.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp to20
device(config-router-mpls-lsp-to20)# adaptive
The following example enables the adaptive command for dynamic bypass MPLS Ethernet interface
0/8.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# adaptive enable
add (telemetry)
Restores a previously removed field to a telemetry profile.
Syntax
add telemetry-field
no add telemetry-field
Command Default
All default fields are included in the telemetry profile.
Parameters
telemetry-field
Specifies the telemetry field to be included.
Modes
Telemetry profile configuration mode
Usage Guidelines
Use the no add command to remove a field.
Examples
The following example adds the add-discard-byte-count field to the default_queue_statistics
profile.
device# configure terminal
device(config)# telemetry profile queue default_queue_statistics
device(config-queue-default_queue_statistics)# add add-discard-byte-count
You must change profile configuration modes to change fields in another profile. Below is an example of
adding fields to multiple profiles.
device# configure terminal
device(config)# telemetry profile interface default_interface_statistics
device(config-interface-default_interface_statistics)# add out-pkts
device(config-interface-default_interface_statistics)# exit
device(config)# telemetry profile queue default_queue_statistics
device(config-queue-default_queue_statistics)# add enq-byte-count
device(config-queue-default_queue_statistics)# add enq-pkt-count
The following example adds the out-packets and out-bytes fields to the
default_mpls_traffic_lsp_statistics profile.
device(config)# telemetry profile mpls-traffic-lsp default_mpls_traffic_lsp_statistics
device(config-mpls-traffic-lsp-default_mpls_traffic_lsp_statistics)# add out-packets
device(config-mpls-traffic-lsp-default_mpls_traffic_lsp_statistics)# add out-bytes
additional-paths
Enables an additional-paths capability for all peers in a Border Gateway Protocol (BGP) address family.
Syntax
additional-paths { receive [ send ] | send }
no additional-paths receive
no additional-paths send
Command Default
Peer devices configured under a BGP address family are not capable of receiving or sending additional-
paths.
Parameters
receive
Enables all peer devices configured under a BGP address family to receive additional-paths.
send
Enables all peer devices configured under a BGP address family to send additional-paths.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Note
Changes to the additional-paths capability for peers in a BGP address family take effect only
after the BGP session is restarted.
Additional-paths can be enabled as receive only, send only, or both receive and send.
The no form of the command disables the specified (receive or send) additional-paths capability.
To remove the configuration when both the receive and send options have been set, you should
enter both the no additional-paths command, specifying the receive option to disable the
receive additional-paths capability, and the no additional-paths command, specifying the send
option to disable the send additional-paths capability.
Examples
The following example shows how to enable peers configured under the IPv4 unicast address family to
both receive and send additional-paths.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-ipv4u)# additional-paths receive send
The following example shows how to disable the capability to receive additional-paths for all peers in
the IPv4 unicast address family.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-ipv4u)# no additional-paths receive
additional-paths select
Configures routes that are eligible for selection as additional-paths by peers configured under a Border
Gateway Protocol (BGP) address family.
Syntax
additional-paths select { all [ best num ] [ group-best ] | best num |
group-best }
no additional-paths select all
no additional-paths select best num
no additional-paths select group-best
Parameters
all
Causes all routes to be eligible for selection as additional-paths. A maximum of 16 routes is
allowed.
best num
Specifies the number of best paths allowed for selection as additonal-paths. The number ranges
from 2 through 16.
group-best
Causes all group-best paths to be eligible for selection as additional-paths. Only routes with a
rank less than or equal to 16 are allowed. Even when it is the group best, a route with a rank
greater than 16 is not eligible for selection as an additional path.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The all, best, and group-best options are not mutually exclusive. When you perform a
combination of these commands, the combined configuration is applied to the BGP address family.
When more than one option is configured, it is recommended that you disable each configured option
separately; for example, disable the all configuration by using the no additional-paths
select command specifying the all option, and so on.
Examples
The following example shows how to configure all (up to a maximum of 16) routes to be eligible for
selection as additional-paths by all peers in the IPv4 unicast address family.
device# configure terminal
device(condig)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-router-ipv4u)# additional-paths select all
The following example shows how to restore the default configuration when the all, best, and
group-best options were previously configured for the IPv4 unicast address family. It is
recommended that you disable each configuration option separately.
device# configure terminal
device(condig)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-router-ipv4u)# no additional-paths select all
device(config-bgp-router-ipv4u)# no additional-paths select best 2
device(config-bgp-router-ipv4u)# no additional-paths select group-best
Syntax
address-family ipv4 flowspec [ vrf vrf-name ]
no address-family ipv4 flowspec [ vrf vrf-name ]
Command Default
BGP flowspec IPv4 address family is disabled.
Parameters
vrf vrf-name
Specifies the name of a VRF instance in which the BGP flowspec IPv4 address family is to be
configured.
Modes
BGP configuration mode
Usage Guidelines
BGP flowspec IPv4 address-family configuration is only allowed in a VRF that is already configured with
an IPv4 unicast address family.
When the vrf option is not specified, the address-family ipv4 flowspec command enables
the BGP flowspec IPv4 address family for the default VRF; the IPv4 unicast address family is always
configured on the default VRF.
The no form of the command disables BGP flowspec IPv4 address family.
You must disable BGP flowspec in a VRF by using the no address-family ipv4 flowspec
command before removing the IPv4 unicast address-family configuration from the VRF.
Examples
The following example shows how to enable BGP flowspec address family in the default VRF.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv4 flowspec
device(config-bgp-ipv4fs)#
The following example shows how to enable BGP flowspec address family in a VRF named red.
device# configure terminal
device(config)# router bgp
Syntax
address-family l2vpn evpn
no address-family l2vpn evpn
Command Default
Disabled.
Modes
BGP configuration mode
Usage Guidelines
Use this command in BGP configuration mode to enter BGP address-family L2VPN EVPN configuration
mode. The L2VPN EVPN configuration mode supports the EVPN Subsequent Address Family Identifier
(SAFI), an address qualifier that provides additional information about the Network Layer Reachability
Information (NLRI) type for a given attribute. The no form of this command removes the L2VPN EVPN
address family configuration from the device and removes all configurations under the L2VPN address
family.
Examples
This example enables BGP address family L2VPN EVPN configuration mode.
Syntax
address-family { ipv4 | ipv6 } unicast [ vrf vrf-name ]
no address-family { ipv4 | ipv6 } unicast [ vrf vrf-name ]
Command Default
Disabled.
Parameters
ipv4
Specifies an IPv4 address family.
ipv6
Specifies an IPv6 address family.
vrf vrf-name
Specifies a VRF instance.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of this command to remove IPv4 or IPv6 address family configurations from the
device.
Examples
The following example enables BGP IPv4 address-family configuration mode.
The following example enables BGP IPv4 address-family configuration mode for VRF "green".
This example enables BGP IPv6 address-family configuration mode for VRF "red".
Syntax
address-family { ipv4 | ipv6 } unicast
Command Default
Disabled.
Parameters
ipv4
Specifies the IPv4 address family.
ipv6
Specifies the IPv6 address family.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables IS-IS address-family IPv4 unicast configuration mode.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv4 unicast
device(config-router-isis-ipv4u)#
The following example enables IS-IS address-family IPv6 unicast configuration mode.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv6 unicast
device(config-router-isis-ipv6u)#
adjustment-interval
There are two mechanisms of configuring LSP level parameters. The direct configuration and template-
based configuration.
Syntax
adjustment-interval value
no adjustment-interval value
Command Default
The adjustment-interval is disabled.
Parameters
value
Specifies the time interval after which the LSP bandwidth must be adjusted. The range is from
300 through 259200 seconds (30 days). The default value is 86400 seconds (one day).
Modes
MPLS LSP configuration mode.
Usage Guidelines
The no option disables the auto-bandwidth for the LSP. The bandwidth immediately is set back to the
traffic-engineering configured value.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the bandwidth reallocation interval to 86400 seconds for LSP xyz.
device>enable
device# configure terminal
device(config)# router mpls
device(config-mpls)# lsp xyz
device(config-mpls-lsp-xyz)# auto-bandwidth
device(config-mpls-lsp-xyz-auto-bandwidth)# adjustment-interval 86400
adjustment-threshold
Specifies the automatic bandwidth adjustment sensitivity of an LSP to changes in bandwidth utilization.
Syntax
adjustment-threshold use-threshold-table
no adjustment-threshold
Command Default
The adjustment threshold is set to the default value.
Parameters
use-threshold-table
Specifies that the template use the autobw-threshold table to determine the threshold.
Modes
MPLS sub-configuration modes
config-mpls-template-template1
config-mpls-lsp-lsp1-autobw
Usage Guidelines
When automatic bandwidth adjustment is configured, bandwidth demand for the current interval is
calculated and compared to the LSP current bandwidth allocation.
The no form of the command sets the adjustment threshold to the default value.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
admin-group
Administrative groups, also known as resource classes or link colors, allows the user to assign MPLS-
enabled interfaces to various classes. When a device calculates the path for an LSP, it can take into
account the administrative group to which a interface belongs; the user can specify which
administrative groups the device can include or exclude when making its calculation.
Syntax
admin-group admin_name admin_group_num
no admin-group admin_name admin_group_num
Command Default
The command is disabled, by default.
Parameters
admin_name
Specifies the selected administrative group name.
admin_group_number
Specifies the selected administrative group number. The number range is 0-31.
Modes
MPLS policy mode.
Usage Guidelines
Up to 32 administrative groups can be configured on the device. The user can see an administrative
group either by its name or its number. Before the user can see an administrative group by its name, the
user must specify a name for the group at the MPLS policy level and associate the name with that
administrative group’s number.
After the user associates an administrative group name with a number, the user can see it by name
when assigning interfaces to the group or including or excluding the group from LSP calculations.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example establishes three administrative groups.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
advertise dot1-tlv
Advertises globally to any attached device IEEE 802.1 organizationally specific Type, Length, Values
(TLV) values, or for a specific LLDP profile.
Syntax
advertise dot1-tlv
no advertise dot1-tlv
Command Default
Advertisement is disabled.
Modes
Protocol LLDP and profile configuration modes
Usage Guidelines
Enter no advertise dot1-tlv to return to the default setting.
Examples
The following example advertises TLV configuration for IEEE 802.1
The following example advertises TLV configuration for IEEE 802.1 for a specific LLDP profile.
advertise dot3-tlv
Advertises to any attached device IEEE 802.3 organizationally specific Type, Length, Values (TLV)
values, or for a specific LLDP profile.
Syntax
advertise dot3-tlv
no advertise dot3-tlv
Command Default
Advertisement is disabled.
Modes
Protocol LLDP and profile configuration modes.
Usage Guidelines
Enter no advertise dot3-tlv to return to the default setting.
Examples
The following example advertises TLV configuration for IEEE 802.3.
The following example advertises TLV configuration for IEEE 802.3 for a specific LLDP profile.
advertise optional-tlv
Advertises the optional Type, Length, and Values (TLV) values, or for a specific LLDP profile.
Syntax
advertise optional-tlv { management-address | port-description | system-
capabilities | system-description | system-name }
no advertise optional-tlv
Command Default
Advertisement is disabled.
Parameters
management-address
Advertises the management address of the system.
port-description
Advertises the user-configured port.
system-capabilities
Advertises the capabilities of the system.
system-description
Advertises the system firmware version and the current image running on the system.
system-name
Advertises the name of the system.
Modes
Protocol LLDP and profile configuration modes
Usage Guidelines
Enter no advertise optional-tlv to return to the default setting.
Examples
The following example advertises the management address of the system and the user-configured port.
The following example advertises the management address of the system for a specific LLDP profile.
advertise-backup
Enables a backup VRRP router to send advertisement frames to the master VRRP router.
Syntax
advertise-backup
no advertise-backup
Command Default
Advertisement is disabled.
Modes
Virtual-router-group configuration mode
Usage Guidelines
Advertisement packets (or frames) are sent to all members of a VRRP group to indicate that the master
router is operational. When the master router is not operational, the backup router becomes the master
router. When you run this command, the backup router sends the frames every 60 seconds.
Enter no advertise backup to return to the default setting (no periodic transmission).
Examples
This example enables the backup VRRP routers to send advertisement frames to the master VRRP
router.
advertise-best-external
Stores and advertises the best external route for a Border Gateway Protocol (BGP) address family.
Syntax
advertise-best-external
no advertise-best-external
Command Default
The best external route for a BGP address family is not stored or advertised.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default configuration.
The advertise-best-external command enables storing and advertising of the best external
route under an address family; the best external route is advertised in addition to the best route.
Examples
The following example shows how to store and advertise the best external route under the IPv4 address
family in unicast mode.
device# configure terminal
device(bgp)# address-family ipv4 unicast
device(config-bgp)# advertise-best-external
advertisement-interval (VRRP)
Configures the interval at which the master VRRP router advertises its existence to the backup routers.
Syntax
advertisement-interval range
Command Default
The default is 1 second for version 2, 1000 milliseconds for version 3.
Parameters
range
Interval at which the master VRRP router advertises its existence to the backup routers. Valid
values range from 1 through 255 seconds for VRRPv2 and from 1000 through 40900
milliseconds for VRRPv3.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This interval is the length of time, in seconds, between each advertisement sent from the master to its
backup VRRP routers. The advertisement notifies the backup routers that the master is still active. If the
backup routers do not receive an advertisement from the master in a designated amount of time, the
backup with the highest priority can assume the role of master.
This command can be used for either VRRP or VRRP-E and for VRRPv3 and VRRP-Ev3.
Examples
To set the advertisement interval to 30 seconds for VRRP-E group 10:
To set the advertisement interval to 3000 milliseconds for VRRP-Ev3 group 19:
advertisement-interval-scale
Configures the sub-second intervals at which the master VRRP-Ev3 device advertises its existence to
the backup routers.
Syntax
advertisement-interval-scale scale
Command Default
The default advertisement interval scale is 1.
Parameters
scale
Number representing the scale of the division of a configured interval at which the master
VRRP-Ev3 device advertises its existence to the backup devices. Valid values are 1, 2, 5, and 10.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This command scales the advertisement interval of the master VRRP-Ev3 device as configured by the
advertisement-interval command. A value of 1, 2, 5, or 10 can be set and the existing
advertisement interval value is divided by the scaling value. For example, if the advertisement interval is
1 second and the scaling value is 10, the new advertisement interval is 100 milliseconds.
When all the advertisement intervals in a VRRP-Ev3 session are scaled, sub-second VRRP-Ev3
convergence is possible if a master fails. The advertisement notifies the backup devices that the master
is still active. If the backup devices do not receive an advertisement from the master in a designated
amount of time, the backup device with the highest priority can assume the role of master. Using sub-
second advertising intervals, sub-second device redundancy can be achieved.
Note that the minimum advertisement interval for the ipv6-vrrp-extended-group command is
1000 milliseconds, so configure the intervals for the advertisement-interval and
advertisement-interval-scale commands accordingly.
Examples
This example sets the scaling of the advertisement interval to 500 milliseconds for VRRP-Ev3 group 19.
device# configure terminal
device(config)# interface ve 2019
device(config-ve-25)# ipv6 vrrp-extended-group 19
device(config-vrrp-extended-group-10)# advertisement-interval 1
device(config-vrrp-extended-group-10)# advertisement-interval-scale 2
agent-enable
Enables the Keylime agent on the SLX device. This agent registers itself with remote keylime
server(registrar) and listens for queries from the remote Keylime server(verifier).
Syntax
agent-enable
Modes
Remote Attestation mode
Examples
This example shows the complete configuration of Remote Attestation on this SLX device.
Platform Availability
This command and mode is only available on the Extreme 8720 and Extreme 8520 devices.
agent-port
Assigns the port on which the Keylime agent communicates.
Syntax
agent-port port-number
Parameters
port-number
The port number on which the Keylime Remote Attestation agent is communicating.
Command Default
The default port used by the Keylime agent is 9002.
Examples
This example shows the complete configuration of Remote Attestation on this SLX device.
Platform Availability
This command and mode is only available on the Extreme 8720 and Extreme 8520 devices.
agent-uuid
Assigns a UUID value to the Keylime agent installed on the SLX device.
Syntax
agent-uuid UUID
Parameters
UUID
A unique value assigned to this Keylime agent. If this parameter is not provided, it is
automatically generated.
Command Default
When a value is not supplied to the agent-uuid command, it is automatically generated and assigned
to the Keylime agent.
Modes
Remote Attestation mode
Examples
This example shows the complete configuration of Remote Attestation on this SLX device.
Platform Availability
This command and mode is only available on the Extreme 8720 and Extreme 8520 devices.
aggregate-address (BGP)
Configures the device to aggregate routes from a range of networks into a single network prefix.
Syntax
aggregate-address { ip-addr ip-mask | ipv6-addr ipv6-mask } [ advertise-
map map-name | as-set | attribute-map map-name | summary-only |
suppress-map map-name ]
no aggregate-address { ip-addr ip-mask | ipv6-addr ipv6-mask }
[ advertise-map map-name | as-set | attribute-map map-name | summary-
only | suppress-map map-name ]
Command Default
The address aggregation feature is disabled. By default, the device advertises individual routes for all
networks.
Parameters
ip-addr
IPv4 address.
ip-mask
IPv4 mask.
ipv6-addr
IPv6 address.
ipv6-mask
IPv6 mask.
advertise-map
Causes the device to advertise the more-specific routes in the specified route map.
map-name
Specifies a route map to be consulted. Range is from 1 through 63 ASCII characters.
as-set
Causes the device to aggregate AS-path information for all routes in the aggregate routes from a
range of networks into a single network prefix.
attribute-map
Causes the device to set attributes for the aggregate routes according to the specified route
map.
map-name
Specifies a route map to be consulted.
summary-only
Prevents the device from advertising more-specific routes contained within the aggregate route.
suppress-map
Prevents the more-specific routes contained in the specified route map from being advertised.
map-name
Specifies a route map to be consulted.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of this command to restore the defaults.
Examples
The following example aggregates routes from a range of networks into a single network prefix under
the IPv6 address family and advertises the paths for this route as AS_SET.
alias
Configures global or user-level aliases for device commands.
Syntax
alias alias-name expansion
no alias alias-name
Parameters
alias-name
Specifies the alias name. The number of characters can be from 1 through 255.
expansion
Specifies the CLI command to be triggered when the alias is entered. If the command is more
than one word, type double quotes (") around the command. The number of characters can be
from 1 through 1023.
Modes
Alias configuration mode
Usage Guidelines
Global aliases are available to all users.
In the alias configuration mode, to delete a global alias use the no form of his command.
In the user-alias configuration mode, to delete a user alias use the no form of his command.
Examples
The following example defines ck as a global alias that enters the show clock command.
device# configure terminal
device(config)# alias-config
device(config-alias-config)# alias ck "show clock"
For the user jdoe, the following example defines sv as a user-level alias that enters the show
version command.
device# configure terminal
device(config)# alias-config
device(config-alias-config)# user jdoe
device(config-user-jdoe)# alias sv "show version"
alias-config
Launches the alias configuration mode, enabling you to define aliases.
Syntax
alias-config
no alias-config [ alias | user username ]
Parameters
alias
(For the no option) Deletes all global aliases.
user username
(For the no option) Deletes all aliases defined for the specified user.
Modes
Global configuration mode
Usage Guidelines
From the alias configuration mode—which you access by entering this command—you can manage
global aliases. From that mode, you can also access the user-alias configuration mode for a specified
user, from which you can manage aliases for that user.
To delete all global aliases, use the no alias-config alias form of this command.
To delete all aliases defined for a specified user, use the no alias-config user form of this
command.
Examples
The following example accesses the alias configuration mode. It then defines ck as a global alias for the
show clock command.
device# configure terminal
device(config)# alias-config
device(config-alias-config)# alias ck "show clock"
The following example deletes all aliases defined for the user jdoe.
device# configure terminal
device(config)# no alias-config user jdoe
allow-conflicting-rules
Towards editing ACLs, disables the default restriction on conflicting rules within an ACL. You can then
create a conflicting rule before deleting the previous version.
Syntax
allow-conflicting-rules
no allow-conflicting-rules
Command Default
Conflicting rules are not allowed within an ACL.
Modes
ACL policy mode
Usage Guidelines
If the only difference between two rules is that one is a deny and the other a hard-drop, they are not
considered conflicting. However, they are considered duplicates; refer to the allow-duplicate-
rules topic.
Towards modifying ACL rules, you do not need to first remove ACLs from interfaces. Changes are
implemented "on the fly," with no gap in protection.
We recommend that after ACL-editing sessions towards which you enabled allow-conflicting-
rules, restore the default setting—by entering the no allow-conflicting-rules command.
Entering no allow-conflicting-rules launches a check of all ACLs for conflicting rules. If you
did not immediately restore the default setting, and created ACLs with conflicting rules, you will need to
delete conflicting rules before the software accepts no allow-conflicting-rules.
Examples
When modifying ACLs by changing a rule from permit to deny or hard-drop—or vice versa—the
following flow is typical.
1. Enter the show running-config command to display the rules in the ACL that you need to
modify.
device# show running-config mac access-list extended mac1
mac access-list extended mac1
seq 10 permit host 0001.0001.0001 any
seq 20 deny host 0001.0001.0002 any count
seq 30 hard-drop host 0001.0001.0003 any mirror
3. In the ACL that you need to modify, create the new rule and then delete the old rule.
device(config-acl-policy)# exit
device(config)# mac access-list mac1
device(conf-macl-ext)# seq 21 permit host 0001.0001.0002 any count
device(conf-macl-ext)# no seq 20
allow-duplicate-rules
Towards editing ACLs, disables the default restriction on duplicate rules within an ACL. You can then
create a duplicate rule at a new sequence before deleting the previous version.
Syntax
allow-duplicate-rules
no allow-duplicate-rules
Command Default
Duplicate rules are not allowed within an ACL.
Modes
ACL policy mode
Usage Guidelines
If the only difference between two rules is that one is a deny and the other a hard-drop, they are
considered duplicates.
Towards modifying ACL rules, you do not need to first remove ACLs from interfaces. Changes are
implemented "on the fly," with no gap in protection.
We recommend that after ACL-editing sessions towards which you enabled allow-duplicate-
rules, restore the default setting—by entering the no allow-duplicate-rules command.
Entering no allow-duplicate-rules launches a check of all ACLs for duplicate rules. If you did
not immediately restore the default setting, and created ACLs with duplicate rules, you will need to
delete duplicates before the software accepts no allow-duplicate-rules.
Examples
When editing ACLs by duplicating a rule into a new sequence and then deleting the original rule, the
following flow is typical.
1. Enter the show running-config command to display the rules in the ACL that you need to
modify.
device# show running-config mac access-list extended mac1
mac access-list extended mac1
seq 10 permit host 0001.0001.0001 any
seq 20 deny host 0001.0001.0002 any count
seq 30 hard-drop host 0001.0001.0003 any mirror
3. In the ACL that you need to modify, create the duplicate rule—specifying the new sequence number
—and then delete the old rule.
device(config-acl-policy)# exit
device(config)# mac access-list mac1
device(conf-macl-ext)# seq 11 hard-drop host 0001.0001.0003 any mirror
device(conf-macl-ext)# no seq 30
allow multiple-ep-per-port
Enables configuring multiple endpoints on VPLS ports.
Syntax
allow multiple-ep-per-port
no allow multiple-ep-per-port
Command Default
Enables configuring multiple endpoints on VPLS ports.
Modes
Router Interface context
Usage Guidelines
This command enables multiple endpoint on the VPLS ports. Use this command after enabling routing
on a BD and binding a router interface to the Bridge Domain. Use this command to enable configuring
your Virtual Ethernet interface on a VPLS instance so that VE routing packets can reach remote VPLS
endpoints.
Examples
This example turns on support of multiple endpoints on a VE interface.
always-compare-med
Configures the device always to compare the Multi-Exit Discriminators (MEDs), regardless of the
autonomous system (AS) information in the paths.
Syntax
always-compare-med
no always-compare-med
Modes
BGP configuration mode
Usage Guidelines
The no form of the command disallows the comparison of the MEDs for paths from neighbors in
different autonomous systems.
Examples
The following example configures the device always to compare the MEDs.
always-propagate
Enables the device to advertise BGP routes even though they are not installed in the RIB Manager.
Syntax
always-propagate
no always-propagate
Command Default
This feature is disabled.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
Examples
This example configures the device to advertise routes that are not installed in the RIB manager.
This example configures the device to reflect advertise that are not installed in the RIB manager in IPv6
address-family unicast configuration mode.
This example configures the device to advertise routes that are not installed in the RIB manager in a
nondefault VRF instance.
anycast-rp
Configures PIM Anycast rendezvous points (RPs) in IPv4 multicast domains.
Syntax
anycast-rp rp-address [anycast-rp-peer-prefix-list]
no anycast-rp rp-address
Command Default
By default, PIM Anycast RPs are not configured.
Parameters
rp-address
Specifies a shared RP address used among multiple PIM routers.
anycast-rp-peer-prefix-list
Specifies the list of Anycast IPv4 or IPv6 peers that are configured with the same Anycast RP
address.
Modes
PIM router configuration mode
Usage Guidelines
PIM Anycast RP provides load balancing and fast convergence to PIM RPs in an IPv4 multicast domain.
The RP address of the Anycast RP is a shared address used among multiple PIM routers, known as PIM
RP. The PIM RP routers create an Anycast RP set. Each router in the Anycast RP set is configured using
two IP addresses: a shared RP address in their loopback address and a separate, unique IP address. The
loopback address must be reachable by all PIM routers in the multicast domain. The separate, unique IP
address is configured to establish static peering with other PIM routers and communication with the
peers.
When the source is activated in a PIM Anycast RP domain, the PIM first hop (FH) registers the source to
the closest PIM RP. The PIM RP decapsulates the packet and creates the (s,g) state. If there are external
peers in the Anycast RP set, the router re-encapsulates the packet with the local peering address as the
source address of the encapsulation. The router distributes the packet to all Anycast RP peers. This re-
encapsulation ensures source state distribution to all RPs in a multicast domain.
Examples
The following example shows how to configure IPv4 PIM Anycast RP.
Syntax
area { A.B.C.D | decimal } authentication spi value { ah | esp null }
{ hmac-md5 | hmac-sha1 } key key
no area { A.B.C.D | decimal } authentication spi value
Command Default
Authentication is not enabled on an area.
Parameters
A.B.C.D
Area address in dotted decimal format.
decimal
Area address in decimal format.
spi
Specifies the Security Policy Index (SPI).
value
Specifies the Security Policy Index (SPI) value. Valid values range from decimal numbers 512
through 4294967295
ah
Specifies authentication header (ah) as the protocol to provide packet-level security.
esp
Specifies Encapsulating Security Payload (ESP) as the protocol to provide packet-level security.
null
Specifies that the ESP payload is not encrypted.
hmac-md5
Enables Hashed Message Authentication Code (HMAC) Message Digest 5 (MD5) authentication
on the OSPF area.
hmac-sha1
Enables HMAC Secure Hash Algorithm 1 (SHA-1) authentication on the OSPF area.
key
Number used in the calculation of the message digest.
key
The 40 hexadecimal character key.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Enter no area authentication spi to remove an authentication specification for an area from
the configuration.
Note
MD5 passwords cannot have ASCII character 32 ('SPACE') as a part of the password string.
Examples
The following example enables ah and MD5 authentication for an OSPF area, setting a SPI value of 750.
The following example enables esp and SHA-1 authentication for an OSPF area, setting a SPI value of
900.
Syntax
area { ip-addr | decimal } nssa { metric [ no-summary ] | default-
information-originate }
no area nssa
Command Default
No areas are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address In decimal format.
metric
Additional cost for using a route to or from this area.
no-summary
When configured on the NSSA area border router (ABR), this parameter prevents any Type 3
and Type 4 summary link-state advertisement (LSA) from being injected into the area. The only
exception is that a default route is injected into the NSSA by the ABR, and strictly as a Type 3
LSA (not a Type 7, because that could cause intra-AS traffic to get routed out the AS). This
makes the NSSA an NSSA totally stubby area, which can only have Type 1, 2 and 7 LSAs. Note:
This parameter is disabled by default, which means the default route must use a Type 7 LSA.
default-information-originate
When configured on the ABR, this parameter injects a Type 7 default route into the NSSA area.
As a result, the other NSSA routers install the default route through the advertising NSSA ABR.
By default the NSSA ABR does not originate a default route to the NSSA.
Modes
OSPF router configuration mode
Usage Guidelines
NSSAs are typically needed when one-way transmission of Type-5 LSAs (out of the area) is desired but
injection of the same LSAs into the area is not acceptable.
Once created, the type of the area cannot be changed. The only exception to this rule is that an NSSA or
stub area can be changed to a totally NSSA or a totally stub area, respectively.
Examples
The following example sets an additional cost of 5 on an NSSA identified as 2, includes the no-summary
parameter, and prevents the device from importing type 3 and type 4 summary LSAs into the NSSA
area.
Syntax
area { ip-addr | decimal } nssa [ metric ] [ default-information-
originate [ metric num ] [ metric-type { type1 | type2 } ] ] [ no-
redsitribution ] [ no-summary ] [ translator-always ] [ translator-
interval interval ]
no area nssa
Command Default
No areas are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
metric
Additional cost for using a route to or from this area. Valid values range from 1 through 1048575.
default-information-originate
When configured on the ABR, this parameter injects a Type 7 default route into the NSSA area.
As a result, the other NSSA routers install the default route through the advertising NSSA ABR.
By default the NSSA ABR does not originate a default route to the NSSA.
metric-type
Specifies how the cost of a neighbor metric is determined.
type1
The metric of a neighbor is the cost between itself and the router plus the cost of using this
router for routing to the rest of the world.
type2
The metric of a neighbor is the total cost from the redistributing routing to the rest of the world.
no-redistribution
The no-redistribution parameter prevents an NSSA ABR from generating external (type-7) LSA
into a NSSA area. This is used in the case where an ASBR should generate type-5 LSA into
normal areas and should not generate type-7 LSA into a NSSA area. By default, redistribution is
enabled in a NSSA.
no-summary
When configured on the NSSA area border router (ABR), this parameter prevents any Type 3
and Type 4 summary link-state advertisement (LSA) from being injected into the area. The only
exception is that a default route is injected into the NSSA by the ABR, and strictly as a Type 3
LSA (not a Type 7, because that could cause intra-AS traffic to get routed out the AS). This
makes the NSSA a NSSA totally stubby area, which can only have Type 1, 2 and 7 LSAs. Note:
This parameter is disabled by default, which means the default route must use a Type 7 LSA.
translator-always
Configures the translator-role. When configured on an ABR, this causes the router to
unconditionally assume the role of a NSSA translator. By default, translator-always is not set, the
translator role by default is candidate.
translator-interval interval
Configures the time interval for which an elected NSSA translator continues to perform its duties
even after its NSSA translator role has been disposed by another router. Valid values range from
10 through 60 seconds. By default the stability-interval is 40 seconds.
Modes
OSPFv3 router configuration mode
Usage Guidelines
NSSAs are typically needed when one-way transmission of Type-5 LSAs (out of the area) is desired but
injection of the same LSAs into the area is not acceptable.
Once created, the type of the area cannot be changed. The only exception to this rule is that a NSSA or
stub area can be changed to a totally NSSA or a totally stub area, respectively.
Examples
The following example sets an additional cost of 4 on a NSSA identified as 8 (in decimal format), and
prevents any Type 3 or Type 4 summary LSAs from being injected into the area.
Syntax
area { ip-addr | decimal } prefix-list name { in | out }
no area { ip-addr | decimal } prefix-list name { in | out }
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
prefix-list name
Specifies a prefix-list between 1 and 32 characters.
in
Specifies that the prefix list is applied to prefixes advertised to the specified area from other
areas.
out
Specifies that the prefix list is applied to prefixes advertised out of the specified area to other
areas.
Modes
OSPF router configuration mode
Usage Guidelines
This command is only applicable to ABRs. The no form of the command changes or cancels the
configured filter and advertises all type 3 LSAs.
Examples
The following example applies a prefix list to type 3 LSAs advertised out of an area with the area-id
10.1.1.1.
The following example applies a prefix list to type 3 LSAs advertised in to an area with the area-id
10.1.1.1.
Syntax
area { A.B.C.D | decimal } range E.F.G.H I.J.K.L advertise [ cost
cost_value ]
area { A.B.C.D | decimal } range E.F.G.H I.J.K.L not-advertise [ cost
cost_value ]
area { A.B.C.D | decimal } range E.F.G.H I.J.K.L cost cost_value
no area range
Parameters
A.B.C.D
Area address in IP address format.
decimal
Area address in decimal format.
E.F.G.H I.J.K.L
Specifies the IP address and mask portion of the range. All network addresses that match this
network are summarized in one route and advertised by the ABR.
advertise
Sets the address range status to advertise and generates a Type 3 summary LSA.
cost cost_value
Sets the cost value for the area range. This value is used as the generated summary LSA cost.
The range for cost_value is 1 to 6777214. If this value is not specified, the cost value is the default
range metric calculation for the generated summary LSA cost.
not-advertise
Sets the address range status to DoNotAdvertise; the Type 3 LSA is suppressed, and the
component networks remain hidden from other networks. This setting temporarily pauses the
route summary from the area.
Modes
OSPF router configuration mode
Usage Guidelines
Use this command only on ABRs to specify a route summary for an existing area. The result is that one
summary route is advertised to other areas by the ABR, in the form of a Type 3 LSA. Routing
information is condensed at area boundaries and external to the area, and only one route is advertised
for each address range.
For example, use this command is if you have many small networks advertised from area 0 to any other
area, or from any non-backbone area into the backbone. This command gives you a summary route
instead of many smaller routes. In an area, the OSPF database on each router must be an exact copy of
the databases of the other routers. This means that no summary is allowed in the area.
The no form of the command disables the specification of range parameters on an ABR.
Examples
The following example advertises to Area 3 all the addresses on the network 10.1.1.0 255.255.255.0 in the
ABR you are signed into.
device# configure terminal
device(config)# router ospf
device(config-router-ospf-vrf-default-vrf)# area 3 range 10.1.1.0 255.255.255.0 advertise
Syntax
area { ip-addr | decimal } range ipv6 address/mask [ advertise | not-
advertise ] [ cost cost_value ]
no area range
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
ipv6 address/mask
Specifies the IPv6 address in dotted-decimal notation and the IPv6 mask in CIDR notation. All
network addresses that match this network are summarized in a single route and advertised by
the ABR.
advertise
Sets the address range status to advertise and generates a Type 3 summary LSA.
cost cost_value
Sets the cost value for the area range. This value is used as the generated summary LSA cost.
The range for cost_value is 1 to 6777214. If this value is not specified, the cost value is the default
range metric calculation for the generated summary LSA cost.
not-advertise
Sets the address range status to DoNotAdvertise; the Type 3 LSA is suppressed, and the
component networks remain hidden from other networks. This setting is used to temporarily
pause route summarization from the area.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Use this command only on ABRs to specify route summarization for an existing area. The result is that a
single summary route is advertised to other areas by the ABR, in the form of a Type 3 LSA. Routing
information is condensed at area boundaries and external to the area, and only a single route is
advertised for each address range.
An example of when you might want to use this command is if you have many small networks
advertised from area 0 to any other area, or from any non-backbone area into the backbone. This
command gives you a summary route instead of many smaller routes. In an area, the OSPF database on
each router must be an exact copy of the databases of the other routers. This means that no
summarization is allowed within the area.
The no form of the command disables the specification of range parameters on an ABR.
Examples
The following example advertises to Area 3 all the addresses on the network 2001:db8:8::/45 in the ABR
you are signed into.
Syntax
area { ip-addr | decimal } stub metric [ no-summary ]
no area stub
Command Default
No areas are created.
Parameters
A.B.C.D
Area address in IP address format.
decimal
Area address In decimal format.
metric
Additional cost for using a route to or from this area. Valid values range from 1 through 6777215.
no-summary
When configured on the ABR, this parameter prevents any Type 3 and Type 4 summary LSAs
from being injected into the area. The only exception is that a default route is injected into the
stub/totally stubby area by the ABR as a Type 3 LSA. Enabling this parameter makes the area a
so-called totally stubby area, which can only have Types 1 and 2. This parameter is disabled by
default.
Modes
OSPF router configuration mode
Usage Guidelines
Once created, the type of the area cannot be changed. The only exception to this rule is that a NSSA or
stub area can be changed to a totally NSSA or a totally stub area, respectively.
Examples
The following example sets an additional cost of 5 on a stub area called 2.
Syntax
area { ip-addr | decimal } stub metric
area { ip-addr | decimal } stub no-summary metric
no area stub
Command Default
No areas are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address In decimal format.
metric
Additional cost for using a route to or from this area. Valid values range from 3 through 1048575.
no-summary
When configured on the ABR, this parameter prevents any Type 3 and Type 4 summary LSAs
from being injected into the area. The only exception is that a default route is injected into the
stub/totally stubby area by the ABR as a Type 3 LSA. Enabling this parameter makes the area a
so-called totally stubby area, which can only have Types 1 and 2. This parameter is disabled by
default.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Once created, the type of the area cannot be changed. The only exception to this rule is that a NSSA or
stub area can be changed to a totally NSSA or a totally stub area, respectively.
Examples
The following example sets an additional cost of 5 on a stub area called 2.
Syntax
area { ip-addr | decimal } virtual-link E.F.G.H [ authentication-key
password ] [ dead-interval time ] [ hello-interval time ] [ md5-
authentication { key-activation-wait-time time | key-id num key } ]
[ retransmit-interval time ] [ transmit-delay time ]
no area virtual-link
Command Default
No virtual links are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
E.F.G.H
ID of the OSPF router at the remote end of the virtual link.
authentication-key password
Sets the password and encryption method. Only one encryption method can be active on an
interface at a time. All OSPF packets transmitted on the interface contain this password. All
OSPF packets received on the interface are checked for this password. If the password is not
present, then the packet is dropped.
dead-interval time
How long a neighbor router waits for a hello packet from the current router before declaring the
router down. This value must be the same for all routers and access servers that are attached to
a common network. Valid values range from 3 through 65535 seconds. The default is 40
seconds.
hello-interval time
Time between hello packets that the router sends on an interface. The value must be the same
for all routers and access servers that are attached to a common network. Valid values range
from 1 through 65535 seconds. The default is 10 seconds.
md5-authentication
Sets either MD5 key-activation wait time or key identifier.
key-activation-wait-time time
Time before a newly configured MD5 authentication key is valid. This parameter provides a
graceful transition from one MD5 key to another without disturbing the network. All new packets
transmitted after the wait time ends will use the newly configured MD5 Key. OSPF packets that
contain the old MD5 key are accepted for up to five minutes (300 seconds) after the new MD5
key is in operation. Valid values range from 0 through 14400 seconds. The default is 300
seconds.
key-id num key
The num is a number between 1 and 255 which identifies the MD5 key being used. This
parameter is required to differentiate among multiple keys defined on a device. When MD5 is
enabled, the key is an alphanumeric password of up to 16 characters that is later encrypted and
included in each OSPF packet transmitted. You must enter a password in this field when the
system is configured to operate with either simple or MD5 authentication. By default, the MD5
authentication key is encrypted.
retransmit-interval time
Time between Link State Advertisement (LSA) retransmissions for adjacencies belonging to the
interface. Set this interval to a value larger than the expected round-trip delay between any two
routers on the attached network. Valid values range from 0 through 3600 seconds. The default is
5 seconds.
transmit-delay time
Estimated time required to send an LSA on the interface. This value must be an integer greater
than zero. The age of each LSA in the update packet is incremented by the value of this
parameter before transmission occurs. Valid values range from 0 through 3600 seconds. The
default is 1 second.
Modes
OSPF router configuration mode
Usage Guidelines
The no form of the command removes a virtual link.
Examples
The following example creates a virtual link for an area whose decimal address is 1, and where the ID of
the OSPFv2 device at the remote end of the virtual link is 10.1.2.3.
Syntax
area { ip-addr | decimal } virtual-link A.B.C.D [ dead-interval time |
hello-interval time | hello-jitter interval | retransmit-interval
time | transmit-delay time ]
no area virtual-link
Command Default
No virtual links are created.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
A.B.C.D
ID of the OSPFv3 device at the remote end of the virtual link.
dead-interval time
How long a neighbor device waits for a hello packet from the current device before declaring the
device down. This value must be the same for all devices and access servers that are attached to
a common network. Valid values range from 3 through 65535 seconds. The default is 40
seconds.
hello-interval time
Time between hello packets that the device sends on an interface. The value must be the same
for all devices and access servers that are attached to a common network. Valid values range
from 1 through 65535 seconds. The default is 10 seconds.
hello-jitter interval
Sets the allowed jitter between hello packets. Valid values range from 1 through 50 percent (%).
The default value is 10%.
retransmit-interval time
Time between Link State Advertisement (LSA) retransmissions for adjacencies belonging to the
interface. Set this interval to a value larger than the expected round-trip delay between any two
devices on the attached network. Valid values range from 1 through 3600 seconds. The default is
5 seconds.
transmit-delay time
Estimated time required to send an LSA on the interface. This value must be an integer greater
than zero. The age of each LSA in the update packet is incremented by the value of this
parameter before transmission occurs. Valid values range from 0 through 3600 seconds. The
default is 1 second.
Modes
OSPFv3 router configuration mode
Usage Guidelines
The values of the dead-interval and hello-interval parameters must be the same at both
ends of a virtual link. Therefore, if you modify the values of these parameters at one end of a virtual link,
you must make the same modifications on the other end of the link. The values of the other virtual link
parameters do not require synchronization.
Examples
The following example creates a virtual link for an area whose decimal address is 1, and where the ID of
the OSPFv3 device at the remote end of the virtual link is 209.157.22.1.
Syntax
area { ip-addr | decimal } virtual-link E.F.G.H authentication spi spi-
value { ah | esp null } { hmac-md5 | hmac-sha1 } key key
no area { A.B.C.D | decimal } virtual-link E.F.G.H authentication spi
spi
Command Default
Authentication is not enabled on a virtual-link.
Parameters
ip-addr
Area address in IP address format.
decimal
Area address in decimal format.
E.F.G.H
ID of the OSPFv3 device at the remote end of the virtual link.
spi spi-value
Specifies the security policy index (SPI) value. Valid values range from decimal numbers 512
through 4294967295
ah
Specifies authentication header (ah) as the protocol to provide packet-level security.
esp
Specifies Encapsulating Security Payload (ESP) as the protocol to provide packet-level security.
null
Specifies that the ESP payload is not encrypted.
hmac-md5
Enables Hashed Message Authentication Code (HMAC) Message Digest 5 (MD5) authentication
on the OSPF area.
hmac-sha1
Enables HMAC Secure Hash Algorithm 1 (SHA-1) authentication on the OSPF area.
key key
Number used in the calculation of the message digest. 40 hexadecimal character key. The 40
hexadecimal character key is encrypted by default.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Enter no area { A.B.C.D | decimal } virtual-link E.F.G.H authentication spi
spi to remove authentication from the virtual-links in the area.
Examples
The following example configures IPsec on a virtual link in an OSPFv3 area.
arp
Creates a static Address Resolution Protocol (ARP) entry.
Syntax
arp A.B.C.D mac-address interface { ethernet slot / port | port-channel
number | ve ve_id }
no arp A.B.C.D
Parameters
A.B.C.D
Specifies a valid IP address.
mac-address
Specifies a valid MAC address.
interface
Specifies an interface type.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel.
ve ve_id
Specifies a virtual Ethernet (VE) interface.
Modes
Global configuration mode
Usage Guidelines
The no form of the command deletes a static ARP entry.
Examples
The following example creates a static ARP entry that associates an IP address, a MAC address, and a
physical port.
device# configure terminal
device(config)# arp 10.53.4.2 1245.7654.2348 interface ethernet 2/1
arp access-list
Creates an Address Resolution Protocol (ARP) access control list (ACL), which is one of the steps
implementing Dynamic ARP Inspection (DAI) on a VLAN.
Syntax
arp access-list acl-name
no arp access-list acl-name
Command Default
No ARP ACLs are defined.
Parameters
acl-name
Specifies the name of the ARP ACL. The name can be up to 63 characters in length, and must
begin with an alphanumeric character. No special characters are allowed, except for the
underscore (_) and hyphen (-).
Modes
Global configuration mode
Usage Guidelines
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC
addresses are accepted only if all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an
IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
You can also append the permit ip host command to the arp access-list command.
You also need ARP ACLs to implement ARP Guard on a physical or port-channel interface.
The no form of the command deletes the ARP ACL if the ACL is not applied on any VLAN or port.
Examples
The following example creates an ARP ACL named "host2" and then defines one permit rule in that ACL.
device# configure terminal
device(config)# arp access-list host2
device(config-arp-acl)# permit ip host 1.1.1.1 mac host 0000.0011.0022
The following example creates an ARP ACL, creates permit ip host rules within, applies it to a
VLAN, and enables Dynamic ARP Inspection (DAI) on the VLAN.
device# configure terminal
device(config)# arp access-list arp_acl_1
device(config-arp-acl)# permit ip host 1.1.1.1 mac host 0020.2222.2222
device(config-arp-acl)# permit ip host 1.1.1.2 mac host 0020.2222.2223
device(config-arp-acl)# exit
The following example creates an ARP ACL, creates permit ip host rules within, and applies it to
an interface. This is the first stage of ARP Guard implementation.
device# configure terminal
device(config)# arp access-list arp_acl_2
device(config-arp-acl)# permit ip host 1.1.1.1 mac host 0020.2222.2222
device(config-arp-acl)# permit ip host 1.1.1.2 mac host 0020.2222.2223
device(config-arp-acl)# exit
Note
At this point in the flow, ARP Guard is not yet enabled. For enablement details, refer to the
"ARP Guard" section of the Extreme SLX-OS Layer 3 Routing Configuration Guide.
as-path-ignore
Disables the comparison of the autonomous system (AS) path lengths of otherwise equal paths.
Syntax
as-path-ignore
no as-path-ignore
Command Default
The comparison of the AS path lengths of otherwise equal paths is enabled.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores default behavior.
Examples
The following example configures the device to always disable the comparison of AS path lengths.
auth-check
Disables Intermediate System-to-Intermediate System (IS-IS) authentication checking globally.
Syntax
auth-check { level-1 | level-2 } disable
no auth-check { level-1 | level-2 }
Command Default
IS-IS authentication checking is enabled by default.
Parameters
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
disable
Disables authentication checking.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example disables IS-IS authentication checking for Level 1 packets.
device# configure terminal
device(config)# router isis
device(config-isis-router)# auth-check level-1 disable
The following example re-enables IS-IS authentication checking for Level 1 packets.
device# configure terminal
device(config)# router isis
device(config-isis-router)# no auth-check level-1
The following example disables IS-IS authentication checking for Level 2 packets.
device# configure terminal
device(config)# router isis
device(config-isis-router)# auth-check level-2 disable
auth-key
Configures an authentication key for Intermediate System-to-Intermediate System (IS-IS) globally.
Syntax
auth-key { level-1 | level-2 } string
no auth-key { level-1 | level-2 }
Command Default
No authentication key is configured.
Parameters
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
string
Specifies a text string that is used as an authentication password. The string can be from 1
through 63 ASCII characters in length.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
Supported Hardware on page 42 in this document.
The authentication mode must be configured using the auth-mode command before an
authentication password can be configured. If the authentication mode is reset for the level specified,
the authentication key must also be reset. For more information, see auth-mode on page 151.
Note
MD5 passwords cannot have ASCII character 32 ('SPACE') as a part of the password string.
Examples
The following example configures an authentication key for Level 1 packets.
device# configure terminal
device(config)# router isis
device(config-isis-router)# auth-key level-1 mykey
auth-mode
Specifies the type of authentication used in Intermediate System-to-Intermediate System (IS-IS)
packets globally.
Syntax
auth-mode md5 { level-1 | level-2 }
no auth-mode md5 { level-1 | level-2 }
Command Default
Disabled.
Parameters
md5
Specifies Message Digest 5 (MD5) authentication.
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command removes the configured authentication mode. The authentication key
must be removed using the no auth-key command before removing the configured authentication
mode. If the authentication mode is reset for the specified level, the authentication key must also be
reset.
Examples
The following example specifies that MD5 authentication is performed on Level 1 packets.
device# configure terminal
device(config)# router isis
device(config-isis-router)# auth-mode md5 level-1
The following example specifies that MD5 authentication is performed on Level 2 packets.
device# configure terminal
device(config)# router isis
device(config-isis-router)# auth-mode md5 level-2
auth-port
Configures a user datagram protocol (UDP) port for Remote Authentication Dial-In User Service
(RADIUS) server authentication.
Syntax
auth-port portnum
no auth-port
Command Default
By default, port 1812 is used for RADIUS server authentication.
Parameters
portnum
Specifies the UDP port to use for RADIUS server authentication. The valid range is 0 through
65535. The default port is 1812.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the command default value.
Examples
The following example shows how to configure port 1234 as the port used for connection to the RADIUS
server for authentication.
Syntax
auto-cost reference-bandwidth { value | use-active-ports }
no auto-cost reference-bandwidth
Command Default
Reference bandwidth is 100 Mbps.
Parameters
value
Reference bandwidth in Mbps. Valid values range from 1 through 4294967.
use-active-ports
Specifies that any dynamic change in bandwidth immediately affects the cost of OSPF routes.
This parameter enables cost calculation for currently active ports only.
Modes
OSPF router configuration mode
Usage Guidelines
Use this command to configure the cost of an interface that a device advertises to it's OSPF neighbors.
OSPF calculates the cost of a route as the ratio of the reference bandwidth to the bandwidth of the
egress interface. An increase in the reference bandwidth results in an increased cost. If the resulting cost
is less than 1, the software rounds the cost up to 1.
The bandwidth for interfaces that consist of more than one physical port is calculated as follows:
• LAG group — The combined bandwidth of all the ports.
• Virtual interface — The lowest individual bandwidth of all the ports that carry the VLAN for the
associated VE.
If a change to the reference bandwidth results in a cost change to an interface, the device sends a link-
state update to update the costs of interfaces advertised by the device.
Note
If you specify the cost for an individual interface (by using the ip ospf cost command),
the cost you specify overrides the cost calculated by the software.
Examples
The following example configures a reference bandwidth of 500.
The reference bandwidth specified in this example results in the following costs:
• 10 Mbps port’s cost = 500/10 = 50.
• 100 Mbps port’s cost = 500/100 = 5.
• 1000 Mbps port’s cost = 500/1000 = 0.5, which is rounded up to 1.
The costs for 10 Mbps and 100 Mbps ports change as a result of the changed reference bandwidth.
Costs for higher-speed interfaces remain the same.
Syntax
auto-cost reference-bandwidth value
no auto-cost reference-bandwidth
Command Default
Reference bandwidth is 100 Mbps.
Parameters
value
Reference bandwidth in Mbps. Valid values range from 1 through 4294967. The default is 100
Mbps.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Use this command to configure the cost of an interface that a device advertises to it's OSPF neighbors.
OSPFv3 calculates the cost of a route as the ratio of the reference bandwidth to the bandwidth of the
egress interface. An increase in the reference bandwidth results in an increased cost. If the resulting cost
is less than 1, the software rounds the cost up to 1.
The bandwidth for interfaces that consist of more than one physical port is calculated as follows:
• LAG group — The combined bandwidth of all the ports.
• Virtual interface — The lowest individual bandwidth of all the ports that carry the VLAN for the
associated VE.
If a change to the reference bandwidth results in a cost change to an interface, the device sends a link-
state update to update the costs of interfaces advertised by the device.
Note
If you specify the cost for an individual interface using the ipv6 ospf cost command, the
cost you specify overrides the cost calculated by the software.
The no form of the command restores the reference bandwidth to its default value and, thus, restores
the default costs of the interfaces to their default values.
Examples
The following example configures a reference bandwidth of 500.
The reference bandwidth specified in this example results in the following costs:
• 10 Mbps port’s cost = 500/10 = 50.
• 100 Mbps port’s cost = 500/100 = 5.
• 1000 Mbps port’s cost = 500/1000 = 0.5, which is rounded up to 1.
• 155 Mbps port cost = 500/155 = 3.23, which is rounded up to 4
• 622 Mbps port cost = 500/622 = 0.80, which is rounded up to 1
• 2488 Mbps port cost = 500/2488 = 0.20, which is rounded up to 1
The costs for 10 Mbps, 100 Mbps, and 155 Mbps ports change as a result of the changed reference
bandwidth. Costs for higher-speed interfaces remain the same.
auto-shutdown-new-neighbors
Disables the establishment of BGP connections with a remote peer when the peer is first configured.
Syntax
auto-shutdown-new-neighbors
no auto-shutdown-new-neighbors
Command Default
This feature is disabled.
Modes
BGP configuration mode
Usage Guidelines
The auto-shutdown-new-neighbors command applies to all neighbors configured under each
VRF. When the auto-shutdown-new-neighbors command is used, any new neighbor configured
will have the shutdown flag enabled for them by default. Once all the neighbor parameters are
configured and it is ready to start the establishment of BGP session with the remote peer, the BGP
neighbor’s shutdown parameter has to disabled by removing the shutdown command for the neighbor.
Examples
The following example enables auto shutdown of BGP neighbors on initial configuration.
The following example disables the peer shutdown state and begins the BGP4 session establishment
process.
autobw-threshold table
Changes the parser mode to the config-router-mpls-autobw-threshold-table mode, allowing the user to
change the absolute adjustment threshold values.
Syntax
autobw-threshold-table
no autobw-threshold-table
Command Default
There are no entries in the adjustment-threshold table.
Modes
MPLS configuration mode
Usage Guidelines
The no form of the command clears all entries in adjustment-threshold table.
Examples
The following example configures the autobw-threshold table
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# autobw-threshold-table
device(config-mpls-autobw-threshold-table)# bandwidth-ceiling 10 threshold 2000
device(config-mpls-autobw-threshold-table)# bandwidth-ceiling 1000 threshold 3000
device(config-mpls-autobw-threshold-table)# bandwidth-ceiling 10000 threshold 5000
backup-advertisement-interval
Configures the interval at which backup VRRP routers advertise their existence to the master router.
Syntax
backup-advertisement-interval interval
Command Default
The default backup advertisement-interval is 60 seconds.
Parameters
interval
Interval at which a backup VRRP router advertises its existence to the master router. Valid values
range from 60 through 3600 seconds.
Modes
Virtual-router-group configuration mode
Usage Guidelines
The interval is the length of time, in seconds, between each advertisement sent from the backup routers
to the master router. The advertisement notifies the master router that the backup is still active. If the
master router does not receive an advertisement from the backup in a designated amount of time, the
backup with the highest priority can assume the role of master.
Examples
To set the backup advertisement interval to 120 seconds for VRRP-E group 10:
bandwidth-ceiling
This command adds a new threshold change point to the autobw-threshold table. When the change
point is already there, the threshold value updates to the new value.
Syntax
bandwidth-ceiling [ bw in kbps | max-bw-threshold [ threshold _n_kbps |
[ percentage threshold_percentage ] ]
no bandwidth-ceiling
Command Default
There are no bandwidth ceiling entry.
Parameters
bw_in_kbps
The bandwidth in kilobytes per second. 0 - 0x7FFFFFFF. Range of bandwidth in kbps.
max-bw-threshold theshold _in_kbps
The threshold in kilobytes per second. 0 - 0x7FFFFFFF. Rangeof bandwidthin kbps.
threshold threshold_percentage
The threshold percentage per second. 0 - 100%. By default, the last ceiling is used.
Note
The first parameter indicates that any rate above the maximum ceiling configured. The second
parameter is the threshold in kbps. for those rates.
Modes
MPLS global adjustment threshold configuration mode.
Usage Guidelines
Review the updated global adjustment-threshold table after executing this command.
The max keyword sets the threshold for any traffic-rate above the maximum bandwidth-ceiling
configured in the table.
The no function of the command remove the bandwidth ceiling entry from the table.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the bandwidth ceiling maximum threshold percentage to 10.
device>configure
device(config)# router mpls
device(config-router-mpls)# autobw-threshold-table
device(config-router-mpls-autobw-threshold-table)# max threshold percentage 10
banner
Defines an incoming, login, or message of the day banner.
Syntax
banner { incoming | login | motd } string
no banner incoming | login | motd
Parameters
incoming
Sets the incoming terminal line banner that is displayed on the console when a user establishes a
Telnet session.
login
Sets the login banner that is displayed on the user terminal when the user logs into the device.
motd
Sets the message of the day (MOTD) that is displayed on the user terminal when a Telnet CLI
session is established.
string
Specifies a text string from 1 through 2048 characters in length including spaces.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to delete the banner.
The banner can appear on multiple lines if you enter multiline mode by using Esc-M and exit by using
CTRL-D.
Examples
To create a login banner with a single line:
beacon enable
Configures LED beacons at device or interface level.
Syntax
beacon enable chassis [ length length | start start-time ]
beacon enable interface { ethernet {slot/port [ length length start
start-time ] } | { port-channel port-channel } }
Parameters
length
Specifies the duration in minutes. The range can be an integer in the range 1 to 1440.
start-time
Specifies the start time in the format (CCYY-MM-DDTHH:MM:SS). Date and time are separated
by a delimiter T.
port-channel
Specifies the port channel ID.
Modes
Privileged EXEC mode
Usage Guidelines
The chassis option affects all device interfaces.
RASLOG messages are generated for chassis beacon enable and disable.
Examples
The following example configures beacon LEDs at device level.
device# beacon enable chassis ?
Possible completions:
length Duration in minutes
start Start time
| Output modifiers
<cr>
The following example configures beacon LEDs based at interface or port-channel level.
The following example shows RASLOG messages for chassis beacon enable and disable.
Syntax
bestpath prefix-validation disable
[no] bestpath prefix-validation disable
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The default behavior is to allow the use of all prefixes for best path calculation.
Examples
This example shows the commands to disable validation of prefixes while calculating best path,
irrespective of the prefix validation state received from the RPKI cache server.
SLX(config)#router bgp
SLX(config-bgp-router)# address-family ipv4 unicast
SLX(config-bgp-ipv4u)# bestpath prefix-validation disable
SLX(config-bgp-ipv4u)#
Syntax
bestpath prefix-validation disallow-invalid
[no] bestpath prefix-validation disallow-invalid
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The [no] form of this command enables the default behavior of allowing all prefixes (including invalid
prefixes) to be used for bestpath calculation.
Examples
This example shows the commands to prevent invalid prefixes being used when calculating bestpath.
This is irrespective of the prefix validation state received from the RPKI cache server.
SLX(config)#router bgp
SLX(config-bgp-router)# address-family ipv4 unicast
SLX(config-bgp-ipv4u)# bestpath prefix-validation disallow-invalid
SLX(config-bgp-ipv4u)#
bfd
Enables Bidirectional Forwarding Detection (BFD).
Syntax
bfd
no bfd
Modes
IS-IS router configuration mode
Usage Guidelines
Use the bfd command in IS-IS router configuration mode to enable BFD sessions on all IS-IS interfaces
on which BFD has been configured using the isis bfd command.
Use the bfd command in OSPF router configuration mode to enable BFD sessions on all OSPFv2
interfaces on which BFD has been configured using the ip ospf bfd command. Use the bfd
command in OSPFv3 router configuration mode to enable BFD sessions on all OSPFv3 interfaces on
which BFD has been configured using the ipv6 ospf bfd command.
Examples
The following example enables BFD globally in IS-IS router configuration mode.
The following example enables BFD globally in OSPF router configuration mode.
The following example disables BFD globally in OSPFv3 router configuration mode.
bfd holdover-interval
Sets the time interval for which Open Shortest Path First (OSPF), Intermediate System to Intermediate
System (IS-IS), or Border Gateway Protocol (BGP) routes are withdrawn after a Bidirectional Forwarding
Detection (BFD) session is declared down.
Syntax
bfd holdover-interval time
no bfd holdover-interval time
Command Default
The BFD holdover interval is set to 0 by default.
Parameters
time
Specifies the BFD holdover interval in seconds. In BGP configuration mode, valid values range
from 0 through 30 and the default is 0. In IS-IS router configuration mode, OSPF router VRF and
OSPFv3 router VRF configuration mode, valid values range from 0 through 20 and the default is
0.
Modes
BGP configuration mode
Usage Guidelines
The BFD holdover interval is supported for both single-hop and multihop sessions.
In BGP configuration mode, use this command to set the BFD holdover interval globally for BGP. In
OSPF router configuration mode or OSPF router VRF configuration mode, use this command to set the
BFD holdover interval globally for OSPFv2. In OSPFv3 router or OSPFv3 router VRF configuration mode,
use this command to set the BFD holdover interval globally for OSPFv3. In IS-IS router configuration
mode, use this command to set the BFD holdover interval globally for IS-IS.
The IS-IS options are supported only on devices based on the DNX chipset family. For a list of such
devices, see "Supported Hardware".
The no form of the command removes the configured BFD holdover interval from the configuration,
and reverts to the default value of 0.
Examples
The following example sets the BFD holdover interval globally to 15 in BGP configuration mode.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# bfd holdover-interval 15
The following example sets the BFD holdover interval globally to 12 in OSPF router configuration mode.
device# configure terminal
device(config)# router ospf
device(config-router-ospf-vrf-default-vrf)# bfd holdover-interval 12
The following example sets the BFD holdover interval globally to 20 in OSPFv3 router configuration
mode.
device# configure terminal
device(config)# ipv6 router ospf
device(config-ipv6-router-ospf-vrf-default-vrf)# bfd holdover-interval 20
The following example sets the BFD holdover interval globally to12 in IS-IS router configuration mode.
device# configure terminal
device(config)# router isis
device(config-isis-router)# bfd holdover-interval 12
bfd interval
Configures Bidirectional Forwarding Detection (BFD) session parameters on an interface.
Syntax
bfd interval transmit-time min-rx receive-time multiplier number
no bfd interval transmit-time min-rx receive-time multiplier number
Parameters
transmit-time
Specifies the interval, in milliseconds, that a device waits to send a control packet to BFD peers.
Valid values range from 50 through 30000. The default is 300.
min-rx receive-time
Specifies the interval, in milliseconds, that a device waits to receive a control packet from BFD
peers. Valid values range from 50 through 30000. The default is 300.
multiplier number
Specifies the number of consecutive BFD control packets that must be missed from a BFD peer
before BFD determines that the connection to that peer is not operational. Valid values range
from 3 through 50. The default is 3.
Modes
BGP configuration mode
Usage Guidelines
The transmit-time and min-rx receive-time parameters are the intervals desired by the local
device. The actual values in use are the negotiated values.
Use the bfd interval command in BGP configuration mode for multihop sessions only. Single-hop
sessions in BGP use the values that are configured at the interface level with the bfd interval
command. Otherwise, the default BFD interfal is used.
Examples
The following example sets the BFD session parameters for an Ethernet interface.
The following example sets the BFD session parameters for a virtual Ethernet (VE) interface.
The following example sets the BFD session parameters globally for BGP.
bfd shutdown
Disables Bidirectional Forwarding Detection (BFD) on an interface.
Syntax
bfd shutdown
no bfd shutdown
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command re-enables BFD sessions on an interface.
Examples
The following example disables BFD sessions on an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/4
device(conf-if-eth-1/4)# bfd shutdown
The following example disables BFD sessions on a virtual Ethernet (VE) interface.
device# configure terminal
device(config)# interface ve 24
device(config-if-ve-24)# bfd shutdown
bgp-redistribute-internal
Causes the device to allow the redistribution of IBGP routes from BGP into OSPF for non-default VRF
instances.
Syntax
bgp-redistribute-internal
no bgp-redistribute-internal
Command Default
This feature is disabled.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of the command to restore the defaults.
By default, with default VRF instances, the device does not allow the redistribution of IBGP routes from
BGP4 and BGP4+ into OSPF. This helps to eliminate routing loops. In non-default VRF instances, use this
command to allow the redistribution of IBGP routes from BGP into OSPF. This command is enabled only
if a non-default VRF instance has been specified.
Examples
This example enables BGP4 route redistribution.
This example enables BGP4+ route redistribution for VRF instance "red".
bpdu-drop-enable
Enables dropping Layer 2 (L2) bridge protocol data units (BPDUs) on endpoints in L2 interfaces.
Syntax
bpdu-drop-enable
no bpdu-drop-enable
Command Default
Dropping of L2 BPDUs is disabled. L2 BPDUs are allowed on endpoints in L2 interfaces.
Modes
Global Configuration Mode
Usage Guidelines
The no form of the command disables dropping of Layer 2 (L2) bridge protocol data units (BPDUs) in
Layer 2 interfaces.
Examples
The following example shows how to enable dropping of L2 BPDUs for all L2 Interfaces.
device# configure terminal
device(config)# bpdu-drop-enable
The following example shows how to enable dropping of L2 BPDUs for L2 Physical Interface.
device# configure terminal
device(config)# interface Ethernet 0/40
device(conf-if-eth-0/40)# bpdu-drop-enable
The following example shows how to enable dropping of L2 BPDUs for L2 Port-Channel Interface.
device# configure terminal
device(config)# interface Port-channel 30
device(conf-Port-channel-30)# bpdu-drop-enable
breakout mode
Configures breakout mode for the supported connectors.
Syntax
breakout mode { 4x10g | 4x25g | 4x1g }
no breakout
Command Default
By default, breakout mode is not configured.
Parameters
4x10g
Configures four 10g breakout interfaces on a port.
4x25g
Configures four 25g breakout interfaces on a port.
4x1g
( SLX 9250 only) Configures four 1g breakout interfaces on a port.
Modes
Hardware connector configuration mode
Usage Guidelines
You do not need to reboot a device for the breakout configuration change to take effect.
When you configure a breakout mode on an Ethernet port, the original interface is deconfigured and
deleted. The new breakout interfaces in the default configuration are created automatically. These new
interfaces are identified with the name of the original interface followed by a suffix. For example, the
breakout interfaces of connector 0/25 have the following naming convention:
interface ethernet 0/25:1
interface ethernet 0/25:2
interface ethernet 0/25:3
interface ethernet 0/25:4
Use the no form of the command to reset the port to non-breakout mode. When you run the no form of
the command, the breakout interfaces are deconfigured and deleted. The original Ethernet interface in
the default configuration is created automatically.
To switch from one breakout mode to another, set the port to non-breakout mode and then run the
command to configure the new breakout mode.
( SLX 9250) This platform supports only the 4x1g breakout mode, which supports the redundant
management interface feature. This feature is used with Mellanox network adapters and 1GB copper
SFPs.
( SLX 9150, SLX 9540, SLX 9640) These platforms support the 4x10g and 4x25g breakout modes. The
number of connectors and connector IDs that support the breakout function varies by platform. For
more information, see the Technical Specifications guide for your platform.
( SLX 9740) This platform has breakout restrictions related to port macros (PM). A PM is a port group.
Each PM has four ports, which are contiguous. PM0 has ports 0/1 – 0/4, PM1 has ports 0/5 – 0/8, PM2
has ports 0/9 – 0/12, and so on. In any PM, 40g and 10g ports cannot coexist with 25g ports. The
following configurations are not supported.
• If any port in a PM is configured as 40g or 4x10g breakout, no 4x25g breakout is allowed in the PM
unless the 40g ports will be removed as part of the breakout operation. For example:
◦ If 0/1 or 0/2 is 40g, you cannot configure 0/3 as 4x25g breakout.
◦ If 0/1 or 0/2 is 40g, you can configure 0/1 as 4x25g breakout because 0/1 and 0/2 will be
removed.
• If 4x25g breakout is configured in a PM, no 40g or 4x10g is allowed in the PM. For example:
◦ If 0/1 is configured as 4x25g breakout, you cannot configure 0/3 or 0/4 as 40g.
◦ If 0/3 is configured as 4x25g breakout, you cannot configure 0/1 as 4x10g breakout.
Examples
This example configures 4x25g breakout mode on connector 0/25 on SLX 9640.
device(config)# hardware
device(config-hardware)# connector 0/25
device(config-connector-0/25)# breakout mode 4x25g
This example configures 4x10g breakout mode on connector 0/25 on SLX 9640.
device(config)# hardware
device(config-hardware)# connector 0/25
device(config-connector-0/25)# breakout mode 4x10g
This example configures 4x1g breakout mode on connector 0/15 on SLX 9250.
device(config)# hardware
device(config-hardware)# connector 0/21
device(config-connector-0/15)# breakout mode 4x1g
bridge-domain
Creates a bridge domain, which represents a switching or inter-connection domain for a wide range of
service end-point types.
Syntax
bridge-domain bd-id [ p2mp | p2p ]
no bridge-domain bd-id [ p2mp | p2p ]
Command Default
No bridge domain is configured.
Parameters
bd-id
Specifies a unique numeric bridge-domain identifier. For supported values, see the Usage
Guidelines.
p2mp
Specifies a multipoint service type. This is the default service type.
p2p
Specifies a point-to-point cross-connect service type.
Modes
Global configuration mode.
Usage Guidelines
The range of supported bridge-domain ID values varies with device:
• XGS devices—From 1 through 1024.
• DNX devices—From 1 through 4096.
(DNX devices only) VPLS performs any-to-any switching between Ethernet attachment circuits (ACs)
and MPLS pseudowires (PWs). VLL performs one-to-one switching between Ethernet AC and MPLS
PWs. Use the bridge-domain to specify the related configuration for both VPLS and VLL.
Examples
The following example shows how to configure bridge domain 1 and specifies a point-to-point cross-
connect service for the domain.
The following example shows the error message that is displayed when the specified bridge-domain ID
is out of range.
The following example shows the error message that is displayed when the bridge-domain creation is
not successful in the back-end.
bridge-domain (EVPN)
Specifies a bridge domain (BD), or adds or removes a range VLANs from the BD, for an Ethernet Virtual
Private Network (EVPN) instance.
Syntax
bridge-domain BD-ID
no bridge-domain BD-ID
bridge-domain { add | remove } {VLAN-range }
Command Default
Disabled
Parameters
BD-ID
Specifies a BD.
add
Adds a range of VLANs to the BD for default EVPN instance.
remove
Removes a range of VLANs from the BD for the default EVPN instance.
VLAN-range
Specifies a hyphen-delimited VLAN range to be added to or removed from BD for the EVPN
instance.
Modes
EVPN configuration mode
Usage Guidelines
Each VLAN/BD added to an EVPN configuration is considered as an EVPN instance and is assigned a
unique EVPN instance ID (EVI) internally. The EVI is calculated as shown in the following table.
When adding a bridge domain, use the clear bgp evpn neighbor all soft in command for
the change to take effect.
Important
To interoperate with third-party vendors, the RTs across the interoperating devices must be
the same. If third-party devices do not support automatic RT assigment, or the EVIs are not
calculated as shown in the above table, the VLAN/BD instances must be configured manually
to ensure that RTs across the devices are compatible.
Examples
To specify a BD and enter EVPN BD configuration mode:
device# configure terminal
device(config)# evpn
device(config-evpn-default)# bridge-domain 100
device(evpn-bridge-domain-100)#
To remove BDs 150 through 180 from the default EVPN instance:
device# configure terminal
device(config)# evpn
device(config-evpn-default)# bridge-domain remove 150-180
device(config-evpn-default)#
bridge-priority
Specifies the bridge priority for the common instance.
Syntax
bridge-priority priority
no bridge-priority
Command Default
The default priority is 32768.
Parameters
priority
Specifies the bridge priority. Valid values range from 0 through 61440 in increments of 4096.
Modes
Protocol Spanning Tree mode
Usage Guidelines
The priority values can be set only in increments of 4096.
Using a lower priority value indicates that the bridge might become root.
Examples
To specify the bridge priority:
bsr-candidate
Configures a bootstrap router (BSR) as a candidate to distribute rendezvous point (RP) information to
the other PIM-SM (Sparse Mode) devices in a PIM-SM domain.
Syntax
bsr-candidate interface {ethernet | loopback | port-channel | ve } num
mask length [priority value]
no bsr-candidate
Command Default
By default, the PIM router is not part of the BSR election process.
Parameters
ethernet num
Specifies the Ethernet interface for the candidate BSR.
loopback num
Specifies the loopback interface for the candidate BSR.
ve num
Specifies the virtual interface for the candidate BSR.
port-channel num
Specifies the port-channel number for the candidate BSR.
mask
Specifies the mask for the candidate BSR.
length
Specifies the hash mask length. Valid values range from 1-32 for IPv4 PIM.
priority value
Specifies the BSR priority. Valid values range from 0-255.
Modes
PIM Router configuration mode
Usage Guidelines
Each PIM-SM domain has one active BSR. For redundancy, you can configure ports on multiple devices
as candidate BSRs. PIM-SM uses an election process to select one of the candidate BSRs as the BSR for
the domain. The BSR with the highest BSR priority is elected. If the priorities result in a tie, the
candidate BSR interface with the highest IP address is elected.
Although you can configure the device as only a candidate BSR or an RP, a best practice is to configure
the same interface on the same device as both a BSR and an RP.
The no bsr-candidate form of this command makes the PIM router cease to act as a candidate
BSR.
Examples
The following example configures a physical interface as a candidate BSR.
device(config)# router pim
device(config-pim-router)# bsr-candidate ethernet 2/2 30 255
bypass-lsp
Creates a bypass LSP by using the bypass-lsp command. Thereafter, in the bypass LSP context, you
must specify at least one interface as an excluded or protected interface.
Syntax
bypass-lsp name
no bypass-lsp name
Parameters
name
Specifies the name of the target LSP.
Modes
MPLS router configuration mode
Usage Guidelines
The name variable must be unique among all regular LSPs and bypass LSPs.
The no form of the command deletes the bypass LSP from the system.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example selects the xm4-by LSP as a bypass LSP.
device>configure
device(config)# router mpls
device(config-router-mpls)# bypass-lsp xm4-by
device(config-router-mpls-bypasslsp-xm4-by)#
bypass-lsp (Telemetry)
Indicates the MPLS Bypass-LSP to be used for the mpls-traffic-bypass profile.
Syntax
bypass-lsp { bypass-lsp-name }
no bypass-lsp { bypass-lsp-name }
Parameters
bypass-lsp-name
Specifies the name of the target LSP for the profile.
Modes
Telemetry profile configuration mode
Usage Guidelines
The bypass-lsp-name variable must be unique among all regular LSPs and bypass LSPs.
The no form of the command deletes the bypass LSP from the profile.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example selects the xm2by LSP as the bypass LSP for the profile.
capability as4-enable
Enables 4-byte autonomous system number (ASN) capability at the BGP global level.
Syntax
capability as4-enable
no capability
Command Default
This feature is disabled.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of this command to disable this functionality.
Examples
The following example enables 4-byte ASN capability.
device#configure terminal
device(config)# router bgp
device(config-bgp-router)# capability as4-enable
ccm-interval
Sets the time interval between two successive Continuity Check Messages (CCMs) that are sent by
Maintenance End Points (MEP) in the specified Maintenance Association (MA).
Syntax
ccm-interval [1-second | 10-second | 3.3-ms | 10-ms | 100-ms ]
Parameters
1-second
Sets the time interval between two successive CCM packets to 1 second.
10-second
Sets the time interval between two successive CCM packets to 10 seconds.
3.3-ms
Ssets the time interval between two successive CCM packets to 3.3 milliseconds.
10-ms
Sets the time interval between two successive CCM packets to 10 milliseconds.
100-ms
Sets the time interval between two successive CCM packets to 100 milliseconds.
Modes
CFM protocol configuration mode
Usage Guidelines
The default value is 10 seconds.
Examples
device# configure terminal
device(config)# protocol cfm
device(config-cfm)# domain name md1 level 4
device(config-cfm-md-md1)# ma-name ma1 id 1 vlan-id 30 priority 4
device(config-cfm-md-ma-ma1)#ccm-interval 10-second
cee-map
Converged Enhanced Ethernet (CEE) enables you to configure the ETS/CEE parameters including
mapping of incoming priorities (traffic with different CoS) to traffic-classes, assigning weights and
corresponding bandwidths to those priorities, and scheduling of all occupied traffic-class traffic to
egress wire.
Syntax
cee-map <cee map name>
Parameters
<cee map name>
Sets the name of the CEE policy being created.
Modes
Priv EXEC Mode
Usage Guidelines
You can define only one CEE map and the name that must be assigned to this policy should always be
default. All other names will result in an error. Attempts to create more than one CEE map will also
result in an error.
Examples
device# configure terminal
device(config)# cee-map default
device(config-cee-map-default)#
Syntax
certutil import sshkey directory ssh_public_key_path file file-name host
remote_ip_address login login_id password password source-ip source-
ip user user_acct
Parameters
directory path
Specifies the path to the certificate on the remote host.
file filename
Specifies the SSH public key with a .pub extension.
host remote_ip
Specifies the IP address of the remote host.
login login_id
Specifies the login name in the remote host.
password password
Specifies the password to access the remote host.
source-ip source-ip
(SCP only) Specifies the source IP address to use in the header.
user user_acct
Specifies a local user name.
Modes
Privileged EXEC mode
Usage Guidelines
When using the password parameter with special characters (such as #$@`) use single or double-
quotes around the password. Alternatively, precede the special characters by a backslash (\) character.
To delete a public key for a specific user, use to the no cerutil sshkey command.
Examples
The following example shows how to import an SSH public key for an SSH user named admin from a
remote host (10.70.4.106). The command specifies the SSH public key directory on the remote host as
well as login credentials to the remote host.
device# certutil import sshkey user admin host 10.70.4.106 directory /users/home40/
bmeenaks/.ssh file id_rsa.pub login fvt password pass1
certutil sshkey
Enters an SSH public key for a specific user by using the command line interface (CLI).
Syntax
certutil sshkey user user-acct pubkey public-key
no certutil sshkey user user-acct
Parameters
user user-acct
Specifies a user name. The user must be a pre-existing user on the device. By default there are
two users: “admin” and “user”.
pubkey public-key
Specifies a public key.
Modes
Privileged EXEC mode
Usage Guidelines
After an SSH public key is configured, the SSH server restarts on all VRF instances and all existing SSH
connections are disconnected.
The user for whom a public key is to be configured by using the certutil sshkey command must
already be configured on the device. By default, two users (admin and user) are configured on the
device. Additional users are configured by using the username command in global configuration
mode.
The public key must be entered within double quotes (" ").
To generate a public key, run the ssh-keygen -t rsa command on any server from which you want
to start an SSH session to the device. Once you run this command, and have not entered any other path
while generating the key, the public key is generated at /root/.ssh/id_rsa.pub by default. Open this file
and copy all its contents after the pubkey option in the CLI.
The no form of the command removes the public key configuration for the specified user.
Examples
The following example shows how to enter an SSH public key directly into the CLI under the username
admin.
device# certutil sshkey user admin pubkey “ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDnim
+Ofjx/id3z2jDxXu9DcMuQqVq/NKi2Lms
+q7dA5Dqww8jlrOGawG8tMySOvnB1ZEvJt1kqNneRi4l6Ot4/7hfd99rIOPGBP/NJs6xTLUrQhDgxB78ddTg
+6euBtkYLTAaTC7kbXGXcO8VVB9+4xrH+0bkvjU9RRvGJguUfdiFKEfIGVOyt0atdHi1dmgQ9BE0cO65nc/
i9MjMJedBe174/QT4TxeGeEgaQ57c2AL5It2V4CzrZBDtnixdnHUO5w2vmBR61LZIDVT1fuX/
xYxDAm9H8SDpDX8pZlfFpQBy/wrkIYPZ/p4OLrUApB/XAJGujrlNlZLEu9U9MPVM/ root@ldap.hc-fusion.in”
certutil sshx509v3
Configures the SSH user certificate Distinguished Name (DN).
Syntax
certutil sshx509v3 { user user-name DN DN-attributes }
no certutil sshx509v3 { user user-name }
Command Default
By default, a DN is not configured.
Parameters
user user-name
Specifies the user name associated with the DN.
DN DN-attributes
Specifies the attributes of the DN, which can include any of the following:
• SERIALNUMBER: Certificate serial number
• emailAddress: Email address
• UID, USERID: User ID
• CN: Common name
• T: Title
• OU: Organizational Unit
• DC: Domain component
• O: Organization
• STREET: Street or street address
• L: Locality
• ST, SP, S: State or Province
• PC: Postal or zip code
• C: Country
Modes
Privileged EXEC mode
Usage Guidelines
Use the no form of the command to remove the DN.
Examples
This following is a typical example.
device# certutil sshx509v3 user user1 DN “C=US, ST=California, L=SJC,
O=ExtrNet Inc, OU=DCIP EMIS, CN=user1/emailAddress=myname@mycompany.com”
cfm linktrace
Transmits a linktrace message to a Maintenance End Point (MEP) in the domain
Syntax
cfm linktrace { domain name | ma ma-name | src-mep mep-id { target-mip
HH:HH:HH:HH:HH:HH | target-mep mep-id }| timeout time | ttl ttl-value
Parameters
domain name
Specifies the maintenance domain to be used for a linktrace message. The name attribute is
case-sensitive.
ma ma-name
Specifies the maintenance association to be used for a linktrace message. The ma-name
attribute is case-sensitive.
src-mep mep-id
Specifies the Source ID. The range of valid values is from 1 through 8192.
target-mip HH:HH:HH:HH:HH:HH
Specifies the MAC address of the MIP linktrace destination.
target-mep mep-id
Specifies the destination ID. The range of valid values is from 1 through 8192.
ttl ttl-value
specifies the initial TTL field value. The range of valid values is from 1 through 64.
timeout time
Specifies the timeout used to wait for linktrace reply in seconds.
Modes
Privileged EXEC mode .
Usage Guidelines
The cfm linktrace command sends a trace message to a specified MEP in the domain to diagnose
the path of the MEP link.
Examples
The following example transmits a successful trace from MEP 21 to MEP 1.
device# cfm linktrace domain md1 ma ma1 src-mep 21 target-mep 1 timeout 10
cfm loopback
Transmits a loopback message to a specific Maintenance End Point (MEP) or Maintenance Intermediate
Point (MIP) in a specified domain.
Syntax
cfm loopback { domain name | ma ma-name | src-mep mep-id { target-mip
HH:HH:HH:HH:HH:HH | target-mep mep-id }| number value | timeout time
Parameters
domain name
Specifies the maintenance domain to be used for a loopback message. The name attribute is
case sensitive.
ma ma-name
Specifies the maintenance association to be used for a loopback message. The ma-name
attribute is case-sensitive.
src-mep mep-id
Specifies the Source ID. The range of valid values is from 1 through 8192.
target-mip HH:HH:HH:HH:HH:HH
Specifies the MAC address of the MIP loopback destination.
target-mep mep-id
Specifies the destination ID. The range of valid values is from 1 through 8192.
number value
Specifies the number of loopback messages to be sent.
timeout time
Specifies the timeout used to wait for loopback reply in seconds.
Modes
Privileged EXEC mode
Usage Guidelines
The cfm loopback command sends a loopback message to a specific MEP or MIP in a specified domain
for testing purposes.
Examples
Command example sending a message from MEP 2 to MEP 1 a total of ten times.
device# cfm loopback domain md1 ma ma1 src-mep 2 target-mep 1 timeout 10 number 10
Syntax
cfm y1731 domain domain-name ma ma-name src-mep mep-id target-mep mep-id
test-profile profile-name
Parameters:
domain-name
Specifies the domain name.
ma
Specifies the maintenance association (MA).
ma-name
Specifies the MA name.
src-mep mep-id
Specifies the source mep-id.
target mep-id
Specifies the taraget mep-id.
profile
Specifies the default or configured test profile.
profile-name
Specifies the profile name.
Modes
Privilieged EXEC mode
Examples
This example shows how to run on-demand two-way delay measurement or two-way synthetic loss
measurement parameters.
device# cfm y1731 domain md1 ma ma1 src-mep 1 target-mep 2 test-profile
2dm_default_profile
device# cfm y1731 domain md1 ma ma1 src-mep 1 target-mep 2 test-profile
2slm_default_profile
channel-group
Enables link aggregation on an interface.
Syntax
channel-group number mode { active | passive | on } [ type standard ]
no channel-group
Command Default
The value for type is set to standard.
Parameters
number
Specifies the port-channel to which you are assigning the interface.
mode
Specifies the mode of Link Aggregation.
active
Enables the initiation of LACP negotiation on an interface.
passive
Disables LACP on an interface.
on
Enables static link aggregation on an interface.
type standard
Specifies the 802.3ad standard-based LAG.
Modes
Interface subtype configuration mode
Usage Guidelines
Port channel scale and support for SLX 9740
Note
• For the 1U SLX 9740-40, the number of LAGs will be 77, where:
◦ 76 are the front end ports (all breakouts)
◦ 1 (insight port)
• For the 2U SLX 9740-80, the number of LAGs will be 153. where:
◦ 152 are the front end ports (all breakouts)
◦ 1 (insight port)
(For SLX 9540 and SLX 9640) Maximum numbers of port-channel IDs and links per port-channel vary
with device and LAG profile, as follows:
Table 8: Port-channel scale for SLX 9540 and SLX 9640 devices
Device or series LAG profile Supported port-channel Maximum links per port-
IDs channel
( SLX 9150 and SLX 9250) Maximum numbers of port-channel IDs and links per port-channel vary only
with device, as follows:
Table 9: Port-channel support for SLX 9150 and SLX 9250 devices
Note
Non-default LAG profiles are not supported for the SLX 9150 and SLX 9250 devices.
To remove the interface from a port-channel, enter the no form of this command.
Examples
The following example associates interface 0/9 with port-channel 4 and activates LACP.
device# configure terminal
device(config)# interface ethernet 0/9
device(conf-if-eth-0/9)# channel-group 4 mode active
chassis
Sets the IPv4 or IPv6 address of a device.
Syntax
chassis { virtual-ip IPv4-address | virtual-ipv6 IPv6-address }
no chassis
Command Default
The default is the initial device address.
Parameters
virtual-ip IPv4-address
Sets an IPv4 address in dotted-decimal notation with a CIDR prefix (mask).
virtual-ipv6 IPv6-address
Sets an IPv6 address in colon-separated hexadecimal notation with a CIDR prefix.
Modes
Global configuration mode
Usage Guidelines
This command changes the current IPv4 or IPv6 address.
Use this command to change the IP address to facilitate management, for example, if a device is moved
to a different subnet. The IP address of the management platform should be in the same subnet as the
devices it manages.
Examples
IPv4:
IPv6:
cipherset
Configures FIPS-compliant ciphers for the Lightweight Directory Access Protocol (LDAP).
Syntax
cipherset { ldap | radius }
Command Default
There are no restrictions on LDAP ciphers.
Parameters
radius
Specifies secure RADIUS ciphers.
ldap
Specifies secure LDAP ciphers.
Modes
Privileged EXEC mode
Usage Guidelines
A device must be configured with secure ciphers for SSH before that device can be FIPS compliant. If
LDAP authentication is to be used, the LDAP ciphers are also required before a device can be FIPS
compliant.
This command can be used only from a user account to which an administrative role is assigned.
Note
Use the ssh client cipher or the ssh server cipher commands to set the SSH
client's cipher lists for SSH clients and servers.
Examples
This example configures secure RADIUS ciphers.
device# cipherset radius
cisco-interoperability
Configures the device to interoperate with some legacy Cisco switches.
Syntax
cisco-interoperability { disable | enable }
Command Default
Cisco interoperability is disabled.
Parameters
disable
Disables Cisco interoperability for the Multiple Spanning Tree Protocol (MSTP) device.
enable
Enables Cisco interoperability for the MSTP enabled device.
Modes
Protocol Spanning Tree MSTP mode
Usage Guidelines
For some devices, the MSTP field, Version 3 Length, does not adhere to the current standards.
If Cisco interoperability is required on any device in the network, then all devices in the network must be
compatible, and therefore enabled using this command for interoperability with a Cisco switch.
Examples
To enable Cisco interoperability on a device:
class
Creates a class map in a policy map and enters the class map configuration mode.
Syntax
class class-mapname
no class class-mapname
Command Default
A policy map is not created.
Parameters
class-mapname
The designated name for the class map.
Modes
Policy map configuration mode
Usage Guidelines
Use this command to configure a class map for a police policy map with QoS and policing parameters
for inbound or outbound traffic. The class map must be previously created and associated with match
criteria using the class-map command. (Refer to the qos cos command.)
When you enter the class command and access policy-map class configuration mode, you can
configure QoS and policing parameters for the class map using the commands for the specific
parameters.
Enter no police while in config-policymap-class mode to remove all policing parameters for the class
map.
Enter no police command followed by a policing parameter name to remove a specific parameter.
Note
The cir is mandatory for configuring a class map. Other parameters are optional. If optional
parameters are not set then they will be treated as disabled. To delete the mandatory CIR
parameter, you must delete all policer parameters while in the policy map class configuration
mode using the no police command.
Examples
This example configures a class-map called "default" within a policy-map.
class-map
Enters class (classification) map configuration mode.
Syntax
class-map class-map-name
no class-map class-map-name
Command Default
The class map name "default" is reserved and cannot be created by users.
Parameters
class-map-name
Name of classification map. The map name is restricted to 64 characters.
Modes
Global configuration mode.
Usage Guidelines
Enter no map class-map class-map-name while in global configuration mode to remove the
classification map.
Examples
The following example accesses class map configuration mode for the default class map:
The following example creates a class map, accesses class map configuration mode, and adds a match
statement to a VLAN:
device(config)# class-map c1
device(config-classmap)# match vlan 500
The following example creates a class map, accesses class map configuration mode, and adds a match
statement to a bridge domain:
clear arp
Clears some or all Address Resolution Protocol (ARP) entries.
Syntax
clear arp [ ethernet slot / port | ip ip-address | ve ve-id ] [ no-
refresh ] [ vrf vrf-name ]
Parameters
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
ip ip-address
Specifies a next-hop IP address.
ve ve-id
Specifies a virtual Ethernet (VE) interface.
no-refresh
Clears the ARP cache without resending ARP requests to the local hosts.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
If the no-refresh keyword is not included, ARP requests are automatically triggered for the cleared
entries. To avoid this triggering, include the no-refresh keyword. It is required to include the no-
refresh keyword, in case the number of ARP entries reaches the system threshold
Examples
The following example clears all ARP entries on the device.
device# clear arp
Syntax
clear bfd neighbors [ ipv4-addr | ipv6-addr ]
Parameters
ipv4-addr
Specifies an IPv4 address.
ipv6-addr
Specifies an IPv6 address.
Modes
Privileged EXEC mode
Examples
The following example clears a specified IPv4 BFD neighbor.
Syntax
clear bgp evpn l2routes type { arp |igmp-join-sync | igmp-leave-sync |
inclusive-multicast | mac | nd}
Parameters
type
Specifies the type of route.
arp
Specifies Address Resolution Protocol routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
inclusive-multicast
Specifies inclusive multicast routes.
mac
Specifies MAC routes.
nc
Specifies neighbor discovery routes.
Modes
Privileged EXEC mode
Examples
This example clears all routes from the BGP EVPN route table.
device# clear bgp evpn l2routes
This example clears all Leave Sync routes from the BGP EVPN route table.
device# clear bgp evpn l2 routes type igmp-leave-sync
Syntax
show bgp evpn local routestype { arp |igmp-join-sync | igmp-leave-sync |
ipv4-prefix | ipv6-prefix |mac | nd}
Parameters
type
Specifies the type of route.
arp
Specifies Address Resolution Protocol routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
ipv4-prefix
Specifies IPv4 routes.
ipv6-prefix
Specifies IPv6 routes.
mac
Specifies MAC routes.
nc
Specifies neighbor discovery routes.
Modes
Privileged EXEC mode
Examples
The following example clears all Leave Sync routes from the BGP EVPN local route table.
device# clear bgp evpn local routes type igmp-leave-sync
Syntax
clear bgp evpn neighbor { all | ipv4-addr | ipv6-addr } [ soft [ in |
out ] ]
clear bgp evpn neighbor { all | ipv4-addr | ipv6-addr } [ soft-outbound ]
Parameters
all
Resets and clears all BGP EVPN connections to all neighbors.
ipv4-addr
Specifies an IPv4 address.
ipv6-addr
Specifies an IPv6 address.
soft
Refreshes routes received from or sent to the neighbor.
in
Refreshes received routes.
out
Refreshes sent routes.
soft-outbound
Refreshes all outbound routes by applying new or changed filters, but sends only the existing
routes affected by the new or changed filters to the neighbor.
Note
Use soft-outbound only if the outbound policy is changed. This operand
updates all outbound routes by applying the new or changed filters. However,
the device sends to the neighbor only the existing routes that are affected by the
new or changed filters. The soft out operand updates all outbound routes and
then sends the entire route table on the device to the neighbor after the device
changes or excludes the routes affected by the filters.
dynamic all
Clears all dynamic neighbors in the EVPN address family.
Modes
Privileged EXEC mode
Examples
This example refreshes all BGP EVPN neighbor connections.
device# clear bgp evpn neighbor all
This example clears BGP EVPN connections with a specified IPv6 address.
device# clear bgp evpn neighbor 2001::1
This example refreshes routes received from a neighbor with the IP address 10.0.0.1.
device# clear bgp evpn neighbor 10.0.0.1 soft in
Syntax
clear bgp evpn neighbor dynamic all
Modes
Privileged EXEC mode
Examples
This example clears all dynamic neighbors in an EVPN address family.
device# configure terminal
device(config)# clear bgp evpn neighbor dynamic all
Syntax
clear bgp evpn routes
clear bgp evpn routes type arp ip address mac mac address ethernet-tag
tag-id
clear bgp evpn routes type ipv4-prefix ip address/mask
clear bgp evpn routes type ipv6-prefix ipv6 address/mask
clear bgp evpn routes type mac mac addressethernet-tag tag-id
clear bgp evpn routes type nd IPv6 address mac mac address ethernet-tag
tag-id
clear bgp evpn routes type [ igmp-join-sync| igmp-leave-sync]
Parameters
arp
Specifies address-resolution protocol (ARP) routes.
ip address
Specifies an IP address.
mac mac address
Specifies Media Access Control (MAC) routes and a MAC address. The valid format is
HHHH.HHHH.HHHH.
ethernet-tag tag-id
Specifies an Ethenet tag. Valid values range from 1 through 4294967295.
ipv4-prefix
Specifies IPv4 prefix routes.
IPv4 address/mask
Specifies an IPv4 address and mask.
ipv6-prefix
Specifies IPv6 prefix routes.
IPv6 address/mask
Specifies an IPv6 address and mask.
mac
Specifies MAC routes.
nd
Specifies neighbor-discovery (ND) routes.
igmp-join-sync
Modes
Privileged EXEC mode
Examples
This example clears all routes from the BGP EVPN route table.
This example clears all ARP routes from the BGP EVPN route table.
This example clears a specified MAC route from the BGP EVPN route table.
This example clears all Leave Sync routes from the BGP EVPN route table.
Syntax
clear bgp ip flowspec local routes vrf vrf-name
Parameters
routes
Specifies clearing BGP route information.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows how to remove and re-install local routes for BGP flowspec in a VRF
named red.
device# clear bgp ip flowspec local routes vrf red
Syntax
clear bgp ip flowspec neighbor { asn-number | ip-address | peer-group |
dynamic |all } [ soft ] [ soft-outbound ] [ vrf vrf-name ]
Parameters
asn-number
Specifies the autonomous system number of the neighbors.
ip-address
Specifies a neighbor IP address in IPv4 format.
peer-group
Specifies a neighbor peer group.
dynamic
Specifies dynamic BGP flowspec neighbors.
all
Clears all BGP flowspec neighbors.
soft
Causes a soft reconfiguration.
soft-outbound
Causes a soft reconfiguration and advertisement only of updated routes.
vrf vrf-name
Specifies a neighbor VRF instance.
Modes
Privileged EXEC mode
Examples
This example shows how to refresh BGP flowspec information for all BGP flowspec neighbors.
device# clear bgp ip flowspec neighbor all
This example shows how to clear all dynamic BGP flowspec neighbors.
device# clear bgp ip flowspec neighbor dynamic all
Syntax
clear bgp ip flowspec routes [vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows how to uninstall and re-install BGP flowspec rules into the hardware.
device# clear bgp ip flowspec routes
Syntax
clear bgp ip neighbor ipv6 {as-num | ipv6-addr [ last-packet-with-error |
notification-errors | soft [ in | out ] | soft-outbound | traffic ]
clear bgp ip neighbor ipv6 all [ soft [ in | out ] | soft-outbound ]
clear bgp ip neighbor ipv6 dynamic all
Parameters
as-num
Specifies an autonomous system number. Range is from 1 through 4294967295.
ipv6-addr
Specifies an IPv6 address in dotted-decimal format.
last-packet-with-error
Specifies clearing connections identified as having the last packet received with an error.
notification-errors
Specifies clearing connections identified as having notification errors.
soft
Refreshes routes received from or sent to the neighbor.
in
Refreshes only received routes.
out
Refreshes only sent routes.
soft-outbound
Refreshes all outbound routes by applying new or changed filters, but sends only the existing
routes affected by the new or changed filters to the neighbor.
Note
Use soft-outbound only when the outbound policy is changed. This operand
updates all outbound routes by applying the new or changed filters. However,
the device sends to the neighbor only the existing routes that are affected by the
new or changed filters. The soft out option updates all outbound routes and
then sends the entire BGP4 route table on the device to the neighbor after the
device changes or excludes the routes affected by the filters.
traffic
Clears the counters (resets them to 0) for BGP4 messages.
all
Modes
Privileged EXEC mode
Examples
The following example refreshes connections with all IPv4 over IPv6 neighbors.
device# clear bgp ip neighbor ipv6
Syntax
clear cfm y1731 client-signal-fail statistics
Command Default
Interfaces are not cleared by default.
Modes
Privileged EXEC mode
Examples
This example clears ETH-CSF statistics.
device# clear cfm y1731 client-signal-fail statistics
Syntax
clear cfm y1731 statistics
Modes
Privileged EXEC mode
Examples
This example shows how to clears all Y.1731 statistics.
device# clear cfm y1731 statistics
Syntax
clear cfm y1731 statistics delay-measurement
Modes
Privileged EXEC mode
Examples
This example shows how to clears all Y.1731 statistics for Two-Way ETH-DM.
device# clear cfm y1731 statistics delay-measurement
Syntax
clear cfm y1731 statistics
Modes
Privileged EXEC mode
Examples
This example shows how to clears all Y.1731 statistics for Two-Way ETH-SLM.
device# clear cfm y1731 statistics
clear counters
Clears the IP counter statistics on the device.
Syntax
clear counters { all | interface { ve ve-id } }
clear counters slot slot-id
Parameters
all
Clears all IP counter statistics on the device or the selected interface. It also clears all VE
Statistics.
interface
Specifies an interface.
ve ve-id
Clears all VE statistics for the specified VE ID.
slot slot-id
For devices that do not support line cards, specify 0.
Modes
Privileged EXEC mode
This example clears all VE statistics for the specified VE ID.
9540
SLX# clear counters interface ve 138
9640
SLX# clear counters interface ve 15
Syntax
clear counters access-list interface { ethernet slot / port | port-
channel index | vlan vlan-id } { in | out }
clear counters access-list interface management mgmt-id in
clear counters access-list interface ve vlan-id { in | out }
clear counters access-list global-subnet-broadcast ip acl-name
clear counters access-list { ip | ipv6 } [ acl-name { in | out } ]
clear counters access-list subnet-broadcast ip [ acl-name [ interface
{ ethernet slot / port | ve vlan-id } ] ]
clear counters access-list { ip | ipv6 } acl-name interface { ethernet
slot / port | port-channel index | ve vlan-id } { in | out }
clear counters access-list { ip | ipv6 } acl-name interface management
mgmt-id in
clear counters access-list receive { ip | ipv6 } [ acl-name ]
clear counters access-list mac [ acl-name { in | out } ]
clear counters access-list mac acl-name interface { ethernet slot / port
| port-channel index | vlan vlan-id } { in | out }
Parameters
interface
Specifies an interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
global-subnet-broadcast ip
( SLX 9540 and SLX 9640 devices) Specifies an IP broadcast ACL (bACL) applied at device level.
management mgmt-id
Specifies the management interface. The only supported value is 0.
port-channel index
Specifies a port-channel.
in
Specifies incoming binding direction.
out
Specifies outgoing binding direction.
subnet-broadcast ip
( SLX 9540 and SLX 9640 devices) Specifies an IP broadcast ACL (bACL) applied at physical-
interface or VE level.
vlan vlan-id
(Available only on Layer 2) Specifies a VLAN.
ve vlan-id
(Available only on Layer 3) Specifies a virtual Ethernet (VE) interface.
ip
Specifies the IPv4 Layer 3 network protocol.
ipv6
Specifies the IPv6 Layer 3 network protocol.
mac
Specifies the medium access control (MAC) Layer 2 network protocol.
receive
Specifies an ACL that applies to device recieve-path traffic.
acl-name
Specifies the ACL name. To clear statistics on all counters of an ACL-type, do not specify acl-
name.
Modes
Privileged EXEC mode
Usage Guidelines
You can clear all statistics for a specified ACL or only for that ACL on a specified interface.
You can also clear statistical information for all ACLs bound to a specified Ethernet or management
interface, a port-channnel, VLAN, or VE.
Examples
The following example clears ACL statistics on a specified Ethernet interface.
device# clear counters access-list interface ethernet 0/1
The following example clears ACL statistics for a specified MAC ACL on a specified Ethernet interface.
device# clear counters access-list mac MAC_ACL_1 interface ethernet 0/2
The following example clears ACL statistics for a specified MAC ACL on all interfaces on which this ACL
is applied.
device# clear counters access-list mac MAC_ACL_1
The following example clears ACL statistics for a specified IPv4 ACL on a specified interface.
device# clear counters access-list ip IP_ACL_1 interface ethernet 0/3
The following example clears ACL statistics for a specified IPv4 ACL on all interfaces on which it is
applied.
device# clear counters access-list ip IP_ACL_1
The following example clears incoming ACL statistics for a specified IPv6 ACL on a virtual Ethernet (VE)
interface.
device# clear counters access-list ipv6 ip_acl_3 interface ve 10 in
Syntax
clears counters access-list overlay type vxlan acl-name
Parameters
acl-name
Specifies the ACL name.
Modes
Privileged EXEC mode
Usage Guidelines
This command clears counters for overlay VXLAN ACLs applied to overlay transit nodes.
Overlay ACLs are not supported for SLX 9150 or SLX 9250 devices.
Examples
The following example clears the statistics of a specific overlay VXLAN ACL.
device# clear counters access-list overlay type vxlan abc_ext
Syntax
clear counters storm-control
clear counters storm-control [ broadcast | multicast | unknown-unicast ]
[ interface ethernet slot/port ]
Parameters
broadcast
Clears all BUM-related counters in the system for the broadcast traffic type.
multicast
Clears all BUM-related counters in the system for the multicast traffic type.
unknown-unicast
Clears all BUM-related counters in the system for the unknown-unicast traffic type.
interface ethernet slot/port
Clears all BUM-related counters in the system for the specified interface. For devices that do not
support linecards, specify 0.
Modes
Privileged EXEC mode.
Usage Guidelines
This command clears the counters for broadcast, unknown-unicast, and multicast traffic for the entire
system, for specified traffic types, for specified interfaces, or for specified traffic types on specified
interfaces.
Examples
Clear counters for broadcast traffic on an Ethernet interface.
Syntax
clear dot1x statistics [ interface ethernet slot/port ]
Parameters
interface ethernet slot/port
Specifies to clear all dot1x statistics for a specified interface port.
Modes
Privileged EXEC mode
Examples
This example clears all accumulated dot1x port authentication statistics on all ports.
This example clears all dot1x statistics for a specified interface port.
device# clear dot1x statistics interface ethernet 1/1
Syntax
clear erp statistics [ erp_id ]
Parameters
erp_id
Specifies an ERP ID.
Modes
Privileged EXEC mode
Usage Guidelines
This command clears the statistics of all the ERP instances present in the device. Use the erp_id to
clear the statistics of a given ERP instance.
Examples
The following example clears all ERP statistics.
device# clear erp statistics
Syntax
clear erp wtb-time erp_id
Parameters
erp_id
Specifies an ERP ID.
Modes
Privileged EXEC mode
Usage Guidelines
This command is allowed only on the RPL-owner node. An error message is issued if it is executed on
another node.
Examples
The following example clears the WTB timer for ERP instance 1.
device# clear erp wtb-time 1
Syntax
clear erp wtr-time erp_id
Parameters
erp_id
Specifies an ERP ID.
Modes
Privileged EXEC mode
Usage Guidelines
This command is allowed only on the RPL-owner node. An error message is issued if it is executed on
another node.
Examples
The following example clears the WTR timer for ERP instance 1.
device# clear erp wtr-time 1
clear filter-change-update
Clears the filter change update delay period.
Syntax
clear filter-change-update
Modes
Privileged EXEC mode
Usage Guidelines
When a previously-distributed BGP flowspec route map is updated, by default the changes are applied
after a delay of 10 seconds. When you make multiple updates and to send a lesser number of changes
to the hardware, you can configure a longer delay period by using the filter-change-update-
delay command.
The clear filter-change-update command clears any previously-configured delay time. This
prevents unnecessary delay in installing BGP flowspec rule changes in the hardware. When the delay
time is cleared, all route-map changes are propagated to the hardware.
Examples
The following example shows how to clear the filter change update delay period so that all route-map
changes are propagated to the hardware.
device# clear filter-change-update
Syntax
clear ip arp inspection statistics
Modes
Privileged EXEC mode
Usage Guidelines
The capacity of each statistic counter is 64 bits, beyond which such a counter is reset to zero.
Examples
The following example clears DAI statistics for all DAI-enabled VLANs.
device# clear ip arp inspection statistics
Syntax
clear ip arp suppression-cache [ bridge-domain bridge-domain-id | vlan
vlan-id ]
Parameters
bridge-domain bridge-domain-id
Specifies a bridge domain.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Usage Guidelines
Running this command might impact traffic.
Examples
The following example clears the ARP-suppression cache.
device# clear ip arp suppression-cache
Syntax
clear ip arp suppression-statistics [ bridge-domain bridge-domain-id |
vlan vlan-id ]
Parameters
bridge-domain bridge-domain-id
Specifies a bridge domain.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Examples
The following example clears all ARP suppression statistics.
device# clear ip arp suppression-statistics
Syntax
clear ip bgp dampening [ ip-addr { / mask } ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a specified route in dotted-decimal notation.
mask
(Optional) IPv4 mask of a specified route in CIDR notation.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
This example unsuppresses all suppressed BGP4 routes.
Syntax
clear ip bgp flap-statistics [ ip-addr { / mask } | neighbor ip-addr |
regular-expression string ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a specified route in dotted-decimal notation.
mask
(Optional) IPv4 mask of a specified route in CIDR notation.
neighbor
Clears dampening statistics only for routes learned from the specified neighbor.
ip-addr
IPv4 address of the neighbor.
regular-expression
Specifies a regular expression.
string
Regular expression.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
This example clears the dampening statistics for a BGP4 route.
This example clears the dampening statistics for a BGP4 route for VRF "red".
Syntax
clear ip bgp local routes [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
This example clears all BGP4 local routes.
Syntax
clear ip bgp neighbor { all | as-num | ip-addr | peer-group-name }
[ last-packet-with-error | notification-errors | soft [ in [ prefix-
filter] | out ] | soft-outbound | traffic ] [ vrf vrf-name ]
Parameters
all
Resets and clears all BGP4 connections to all neighbors.
as-num
Clears all BGP4 connections within this autonomous system. Range is from 1 through
4294967295.
peer-group-name
Clears all BGP4 connections in this peer group. Range is from 1 through 63 characters.
ip-addr
Clears all BGP4 connections with this IPv4 address, in dotted-decimal notation.
last-packet-with-error
Clears all BGP4 connections identified as having the last packet received with an error.
notification-errors
Clears all BGP4 connections identified as having notification errors.
soft
Refreshes routes received from or sent to the neighbor.
in
Refreshes received routes.
prefix-filter
Refreshes Outbound Route Filters (ORFs) that are prefix-based.
out
Refreshes sent routes.
soft-outbound
Refreshes all outbound routes by applying new or changed filters, but sends only the existing
routes affected by the new or changed filters to the neighbor.
Note
Use soft-outbound only if the outbound policy is changed. This operand
updates all outbound routes by applying the new or changed filters. However,
the device sends to the neighbor only the existing routes that are affected by the
new or changed filters. The soft out operand updates all outbound routes and
then sends the entire BGP4 route table on the device to the neighbor after the
device changes or excludes the routes affected by the filters.
traffic
Clears the counters (resets them to 0) for BGP4 messages.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
This example refreshes all BGP4 neighbor connections.
device# clear ip bgp neighbor all
This example refreshes all BGP4 neighbor connections for VRF "red".
Syntax
clear ip bgp neighbor dynamic [ all | vrf vrf-name ]
clear ip bgp vpnv4 neighbor dynamic all
clear ip bgp vpnv6 neighbor dynamic all
Parameters
all | vrf
Specifies whether to clear all dynamic neighbors or only the neighbors in the specified VRF.
vrf-name
Specifies the name of the VRF from which to clear neighbors.
Modes
Privileged EXEC mode
Examples
This example removes all dynamic BGP4 neighbors.
device# configure terminal
device(config)# clear ip bgp neighbor dynamic all
This example removes all dynamic BGP4 neighbors from the VRF named vrf-red.
device# configure terminal
device(config)# clear ip bgp neighbor dynamic vrf vrf-red
Syntax
clear ip bgp routes [ ip-addr [ / mask ] ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a specified route in dotted-decimal notation.
mask
(Optional) IPv4 mask of a specified route in CIDR notation.
vrf vrf-name
Specifies the name of the VRF instance to associate with subsequent address-family
configuration mode commands.
Modes
Privileged EXEC mode
Examples
This example clears all BGP4 routes.
Syntax
clear ip bgp rpki server { hostname | address } port port no
clear ip bgp rpki server all
Parameters
hostname
The hostname of the remote RPKI cache server. You can use one of hostname or IP address.
address
The IP address of the remote RPKI cache server. You can use one of hostname or IP address.
port port no
The port number on which this RPKI cache server can be accessed.
all
This keyword indicates that the command must be performed on all the remote RPKI cache
servers configured on this device.
Modes
Privileged EXEC mode
Usage Guidelines
Note
Since you can only connect to one remote RPKI server at a time, the two commands perform
the same function.
Examples
This example command closes the TCP connection to the remote RPKI cache server with IP address
192.168.14.2, purges the ROAs downloaded from the server, reconnects back to the server, and
downloads the ROAs again.
SLX# clear ip bgp rpki server 192.168.14.2 port 1030
Possible completions:
<cr>
Syntax
clear ip bgp traffic [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example clears the BGP4 message counters.
Syntax
clear ip dhcp relay statistics ip-address ip-address
Command Default
DHCP relay statistics are present on the DHCP server.
Parameters
ip-address ip-address
IPv4 address of DHCP server where client requests are to be forwarded.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to clear IP DHCP Relay statistics for a specific IP DHCP Relay address or all addresses
on the device.
Examples
The following example clears statistics for IP DHCP Relay
device# clear ip dhcp relay statistics ip-address 10.1.0.1
Syntax
clear ip dhcp snooping binding [ [ mac-addr| ip-addr ] |vlan vlan-id |
interface switchport interface ]
clear ip dhcp snooping binding vlan vlan-id
clear ip dhcp snooping binding interface switchport interface
Command Default
By default, DHCP snooping binding entries are present in the binding database.
Parameters
binding [ mac-addr| ip-addr ]
Specifies the MAC or IP address of the host for the entry in the binding database.
vlan vlan-id | interface [ switchport | physical interface ]]
Deletes the specified binding entry from the binding database.
vlan vlan-id
Deletes all binding entries for the specified VLAN from the binding database.
interface switchport interface
Deletes all binding entries from the binding database that were learned on the specified
switchport.
Modes
Privileged EXEC mode
Examples
This example clears one binding entry from the database.
device# clear ip dhcp snooping binding <mac-addr> <ip-addr> vlan <vlan-id>
interface <switchport/physical interface>
This example clears all binding entries for the specified VLAN.
device# clear ip dhcp snooping binding vlan <vlan-id>
This example clears all binding entries learned on the specified switchport.
clear ip dhcp snooping binding interface <switchport/physical interface>
Syntax
clear ip flowspec rules statistics [ vrf vrf-name ]
Parameters
vrf-name
Name of a VRF instance in which BGP flowspec rules are used.
Modes
Privileged EXEC mode
Usage Guidelines
When a VRF is not specified, the clear ip flowspec rules statistics command clears BGP
flowspec rule statistics for the default VRF.
Examples
The following example shows how to clear BGP flowspec rule statistics for a VRF named red.
The following example shows how to clear BGP flowspec rule statistics for the default VRF.
Syntax
k
clear ip igmp groups [ vlan id | bridge-domain id | cluster id | client
id ]
Parameters
vlan
Specifies the VLAN for which you want to remove group information.
id
Specifies the ID of the VLAN.
bridge-domain
Specifies the bridge domain for which you want to remove group information.
id
Specifies the ID of the bridge domain.
cluster
Specifies the MCT cluster for which you want to remove group information.
id
Specifies the ID of the cluster.
client
Specifies the CCEP client for which you want to remove group information.
id
Specifies the ID of the client.
Modes
Privileged EXEC mode
Examples
The following example clears the groups information for a VLAN.
clear ip igmp groups vlan 100
Syntax
clear ip igmp statistics [ vlan id | bridge-domain id ]
Parameters
vlan
Specifies the VLAN for which you want to remove IGMP statistics.
id
Specifies the ID of the VLAN.
bridge-domain
Specifies the bridge domain for which you want to remove IGMP statistics.
id
Specifies the ID of the bridge domain.
Modes
Privileged EXEC mode
Examples
The following example clears the statistics for a VLAN.
clear ip igmp statistics vlan 100
Syntax
clear ip multicast snooping mcache [ vlan id | bridge-domain id ]
Parameters
vlan
Specifies the VLAN for which you want to clear the forwarding cache.
id
Specifies the ID of the VLAN.
bridge-domain
Specifies the bridge domain for which you want to clear the forwarding cache.
id
Specifies the ID of the bridge domain.
Modes
Privileged EXEC mode
Examples
The following example clears the forwarding cache for a VLAN.
clear ip multicast snooping mcache vlan 100
Syntax
clear ip pim mdt [ group GROUP-IP-ADDRESS ]
Parameters
group GROUP-IP-ADDRESS
Specifies the group ip address.
Modes
Privileged EXEC mode
clear ip ospf
Clears OSPF data processes, graceful restart, counters, neighbors, or routes.
Syntax
clear ip ospf all [ vrf vrf-name ]
clear ip ospf graceful-restart { vrf vrf-name | all-vrf }
clear ip ospf counters { all | ethernet slot/port | loopback number |
port-channel number | ve vlan-id } [ vrf vrf-name ]
clear ip ospf neighbor { ip-addr | all } [ vrf vrf-name ]
clear ip ospf routes { ip-addr/mask | all } [ vrf vrf-name ]
Parameters
all
Clears all OSPF data processes.
vrf name
Specifies a VRF.
gr vrf-name
Gracefully restarts the OSPF session for the specified VRF. If no VRF is specified, the default-vrf
session is restarted.
counters
Clears OSPF counters.
all
Clears all counters.
ethernet slot / port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
port-channel number
Specifies a port-channel.
ve vlan-id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
neighbor
Clears neighbors.
ip-addr
Specifies the IP address of the neighbor.
all
Clears all neighbors.
routes
Clears matching routes or clears all routes.
ip-addr/mask
Clears all routes that match the prefix and mask that you specify.
all
Clears all routes.
Modes
Privileged EXEC mode
Examples
The following example restarts all OSPF processes.
device# clear ip ospf all
This example gracefully restarts the OSPF session for the VRF named "red."
device# clear ip ospf gr red
clear ip route
Clears a specified route or all IP routes in the IP routing tables.
Syntax
clear ip route { A.B.C.D | A.B.C.D/M } [ vrf vrf-name ]
clear ip route all [ vrf vrf-name ] ]
clear ip route slot line-card-number [ A.B.C.D | A.B.C.D/M ] [ vrf vrf-
name ]
Parameters
A.B.C.D
Specifies an IPv4 address.
A.B.C.D/M
Specifies an IPv4 address and mask.
vrf vrf-name
Specifies a VRF instance from which the user is currently retrieving routes.
all
Specifies all routes.
slot line-card-number
Specifies a line card.
Modes
Privileged EXEC mode
Examples
The following example clears the IP route specified by IP address 192.158.1.1/24.
device# clear ip route 192.158.1.1/24
Syntax
clear ipv6 bgp dampening [ ipv6-addr { / mask } ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
mask
IPv6 mask of a specified route in CIDR notation.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example unsuppresses all suppressed BGP4+ routes.
The following example unsuppresses suppressed BGP4+ routes for VRF "red".
Syntax
clear ipv6 bgp flap-statistics [ ipv6-addr { / mask } | neighbor ipv6-
addr | regular-expression string ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
mask
(Optional) IPv6 mask of a specified route in CIDR notation.
neighbor
Clears route-flap statistics only for routes learned from the specified neighbor.
ipv6-addr
IPv6 address of the neighbor.
regular-expression
Specifies a regular expression.
string
Regular expression.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
This example clears all dampening statistics for a BGP4+ route.
This example clears the dampening statistics for a BGP4+ route for VRF "red".
Syntax
clear ipv6 bgp local routes [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
This example clears all BGP4+ local routes.
Syntax
clear ipv6 bgp neighbor [ all | as-num | peer-group-name | ipv6-addr ]
[ last-packet-with-error | notification-errors | soft [ in [ prefix-
filter ] | out ]] | soft-outbound | traffic ] [ vrf vrfname ]
Parameters
all
Resets and clears all BGP4+ connections to all neighbors.
as-num
Clears all BGP4+ connections within this autonomous system. Range is from 1 through
4294967295.
peer-group-name
Clears all BGP4+ connections in this peer group. Range is from 1 through 63 characters.
ipv6-addr
Clears all BGP4+ connections with this IPv6 address, in dotted-decimal notation.
last-packet-with-error
Clears all BGP4+ connections identified as having the last packet received with an error.
notification-errors
Clears all BGP4+ connections identified as having notification errors.
soft
Refreshes routes received from or sent to the neighbor.
in
Refreshes received routes.
prefix-filter
Refreshes Outbound Route Filters (ORFs) that are prefix-based.
out
Refreshes sent routes.
soft-outbound
Refreshes all outbound routes by applying new or changed filters, but sends only the existing
routes affected by the new or changed filters to the neighbor.
Note
Use soft-outbound only if the outbound policy is changed. This operand
updates all outbound routes by applying the new or changed filters. However,
the device sends to the neighbor only the existing routes that are affected by the
new or changed filters. The soft out operand updates all outbound routes and
then sends the entire BGP4+ route table on the device to the neighbor after the
device changes or excludes the routes affected by the filters.
traffic
Clears the counters (resets them to 0) for BGP4+ messages.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
This example refreshes all BGP4+ neighbor connections.
device# clear ipv6 bgp neighbor all
This example clears BGP4+ connections with a specified peer group for VRF "red".
device# clear ipv6 bgp neighbor P1 vrf red
Syntax
clear ipv6 bgp neighbor dynamic [ all | vrf vrf-name ]
Parameters
all | vrf
Specifies whether to clear all dynamic neighbors or only the neighbors in the specified VRF.
vrf-name
Specifies the name of the VRF from which to clear neighbors.
Modes
Privileged EXEC mode
Examples
This example removes all dynamic BGP4+ neighbors.
device# configure terminal
device(config)# clear ipv6 bgp neighbor dynamic all
This example removes all dynamic BGP4+ neighbors from the VRF named vrf-red.
device# configure terminal
device(config)# clear ipv6 bgp neighbor dynamic vrf vrf-red
Syntax
clear ipv6 bgp routes [ ipv6-addr [ / mask ] ] [ vrf vrfname ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
mask
(Optional) IPv6 mask of a specified route in CIDR notation.
vrf vrf-name
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
This example clears specific BGP4+ routes.
Syntax
clear ipv6 bgp traffic [ vrf vrf-name ]
Modes
Privileged EXEC mode
Parameters
vrf vrf-name
Specifies the name of a VRF instance.
Examples
This example clears all BGP4+ message counters.
Syntax
clear ipv6 counters { all | interface { ethernet slot/port | loopback
port-number | port-channel number | ve ve-id }}
Parameters
all
Specifies all interfaces.
ethernet
Represents a valid, physical Ethernet subtype.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
loopback
Specifies a loopback interface.
port-number
Port number of the loopback interface. The range is from 1 through 255.
port-channel number
Specifies a port-channel.
ve
Specifies a virtual Ethernet (VE) interface.
ve_id
ID of the VE interface. The range is from 1 through 4096.
Modes
Privileged EXEC mode
Examples
The following example clears counters on Ethernet 2/3.
device# clear ipv6 counters interface ethernet 2/3
Syntax
clear ipv6 dhcp relay statistics ip-address ip-address
Command Default
DHCP relay statistics are present on the DHCP server.
Parameters
ip-address ip-addr
IPv6 address of DHCP server where client requests are to be forwarded.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to clear all the DHCP Relay statistics.
Examples
Clear all the DHCP Relay statistics on the device.
Syntax
clear ipv6 nd suppression-cache [ bridge-domain bridge-domain-id | vlan
vlan-id ]
Parameters
bridge-domain bridge-domain-id
Specifies a bridge domain. The range is from 1 through 8192.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Examples
The following example clears the ND-suppression cache.
device# clear ipv6 nd suppression-cache
Syntax
clear ipv6 nd suppression-statistics [ bridge-domain bridge-domain-id |
vlan vlan-id ]
Parameters
bridge-domain bridge-domain-id
Specifies a bridge domain.
vlan vlan-id
Specifies a VLAN interface. The range is from 1 through 4090.
Modes
Privileged EXEC mode
Examples
The following example clears all neighbor discovery suppression statistics.
device# clear ipv6 nd suppression-statistics
Syntax
clear ipv6 neighbor [ ipv6-address ] [ ethernet port/slot | ve ve-
number ] [ force-delete | no-refresh | vrf vrf-name ]
Parameters
ipv6-address
Removes cache entries for the specified IPv6 address.
ethernet
Removes neighbor entries for the Ethernet interface.
ve ve-number
Removes neighbor entries for the the specified Virtual Ethernet (VE) interface.
force-delete
Force deletes all the dynamic neighbor entries.
no-refresh
Deletes all the dynamic neighbor entries.
vrf vrf-name
Removes entries from the IPv6 neighbor table for the specified VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
You must specify the ipv6-address parameter in hexadecimal using 16-bit values between colons as
documented in RFC 2373.
Examples
The following example removes neighbor entries for Ethernet interface 1/3.
device# clear ipv6 neighbor ethernet 1/3 force-delete
Syntax
clear ipv6 ospf all [ vrf vrf-name ]
clear ipv6 ospf graceful-restart { vrf vrf-name | all-vrf }
clear ipv6 ospf counts [ vrf vrf-name ]
clear ipv6 ospf counts neighbor A.B.C.D [ vrf vrf-name ]
clear ipv6 ospf counts neighbor interface { ethernet slot/port | loopback
number | port-channel number | ve vlan_id } [ A.B.C.D ]
clear ipv6 ospf { force-spf | redistribution | traffic } [ vrf vrf-name ]
clear ipv6 ospf neighbor A.B.C.D [ vrf vrf-name ]
clear ipv6 ospf neighbor all [ vrf vrf-name ]
clear ipv6 ospf neighbor interface { ethernet slot/port | loopback number
| port-channel number | ve vlan_id } [ A.B.C.D ]
clear ipv6 ospf routes { IPv6addr | all } [ vrf vrf-name ]
Parameters
all
Clears all OSPFv3 data.
gr vrf-name
Gracefully restarts the OSPFv3 session for the specified VRF. If no VRF is specified, the default-
vrf session is restarted.
counts
Clears OSPFv3 counters.
neighbor
Clears all OSPFv3 counters for a specified neighbor.
A.B.C.D
Specifies a neighbor.
vrf vrf-name
Specifies a VRF.
interface
Specifies an interface.
ethernet slot / port
Specifies an Ethernet slot and port.
loopback number
Modes
Privileged EXEC mode
Usage Guidelines
Use the force-spf keyword to perform the shortest path first (SPF) calculation without clearing the
OSPFv3 database.
Examples
The following example restarts the OSPFv3 processes.
device# clear ipv6 ospf all
The following example clears all OSPFv3 counters for a specified neighbor.
device# clear ipv6 ospf counts neighbor 10.10.10.1
This example gracefully restarts the OSPFv3 session for the VRF named "red."
device# clear ipv6 ospf gr red
Syntax
clear ipv6 route [ ipv6-address vrf vrf-name ] [ all vrf vrf-name ]
Parameters
ipv6-address
Removes IPv6 routes for the specified IPv6 address.
vrf vrf-name
Removes IPv6 routes for the specified VPN Routing and Forwarding (VRF) instance.
all
Removes all IPv6 routes.
slot line-card-number
(Not currently supported) Removes IPv6 routes for the specified line card.
Modes
Privileged EXEC mode
Examples
The following example clears IPv6 routes associated with the prefix 2000:7838::/32.
device# clear ipv6 route 2000:7838::/32
Syntax
clear ipv6 vrrp statistics [ all ]
clear ipv6 vrrp statistics [ interface { ethernet slot/port | ve
vlan_id } ]
clear ipv6 vrrp statistics [ session VRID ]
Parameters
all
Clears all IPv6 VRRP statistics.
session VRID
Specifies the virtual group ID on which to clear statistics. The range is from 1 through 128.
interface
Specifies an interface.
ethernet slot port
Specifies a valid, physical Ethernet interface with a slot and port number.
ve vlan_id
Specifies the VE VLAN number. The range is from 1 through 4096.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported in IPv6 VRRPv3 and VRRP-E-v3.
Examples
The following example clears all IPv6 VRRPv3 statistics for all virtual groups.
device# clear ipv6 vrrp statistics all
The following example clears statistics for an IPv6 VRRPv3 session of virtual group 25.
device# clear ipv6 vrrp statistics session 25
The following example clears IPv6 VRRPv3 statistics on a specified virtual Ethernet interface.
device# clear ipv6 vrrp statistics interface ve 10
Syntax
clear isis all
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example clears all IS-IS information for a device.
device# clear isis all
Syntax
clear isis counts
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example clears IS-IS error statistics.
Syntax
clear isis database [ lsp-id level-1 | level-2 ]
Parameters
lsp-id
Specifies a link-state packet (LSP) n HHHH.HHHH.HHHH.HH-HH format or by entering a name,
HH-HH.
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example clears IS-IS database entries, specifying an LSP name of “XMR.00-00”.
device# clear isis database XMR-1.00-00
Syntax
clear isis force-spf [ level-1 | level-2 ]
Parameters
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example specifies that SPF calculations can be performed without clearing the IS-IS database for
Level 2 packets.
device# clear isis force-spf level-2
Syntax
clear isis force-v6spf [ level-1 | level-2 ]
Parameters
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example specifies that IPv6 SPF calculations can be performed without clearing the IS-IS database
for Level 1 packets.
device# clear isis force-v6spf level-1
Syntax
clear isis ipv6 spf-log [ level-1 | level-2 ]
Parameters
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example clears IPv6 IS-IS logs for Level 1 packets.
device# clear isis ipv6 spf-log level-1
Syntax
clear isis neighbor { lsp-id | all } [ ethernet slot/port | ve vlan_id ]
Parameters
lsp-id
Specifies a link-state packet (LSP) n HHHH.HHHH.HHHH.HH-HH format or by entering a name,
HH-HH.
all
Specifies all neighbors.
ethernet slot / port
Specifies an Ethernet slot and port.
ve vlan_id
Specifies a virtual Ethernet (VE) interface.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example clears IS-IS neighbors, specifying a LSP name of “XMR.00-00”.
device# clear isis neighbor XMR-1.00-00
This example clears all IS-IS connections for a specified Ethernet interface.
device# clear isis neighbor all ethernet 1/1
Syntax
clear isis route { ip-address | ip-address/mask | all }
Parameters
ip-address
Clears all routes that match the prefix that you specify.
ip-address/mask
Clears all routes that match the prefix and mask that you specify.
all
Specifies all routes.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example clears IS-IS routes that match the IP address 10.1.1.1.
device# clear isis route 10.1.1.1
Syntax
clear isis spf-log [ level-1 | level-2 ]
Parameters
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example clears IPv4 IS-IS logs for Level 2 packets.
device# clear isis spf-log level-2
Syntax
clear isis traffic
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
This example clears IS-IS packet counters.
device# clear isis traffic
clear lacp
Clears the Link Aggregation Group Control Protocol (LACP) counters on a specific port-channel.
Syntax
clear lacp number counters
Parameters
number
Specifies the port channel-group number.
counters
Clears traffic counters.
Modes
Privileged EXEC mode
Examples
To clear the LACP counters for a specific port-channel:
device# clear lacp 10 counters
Syntax
clear lacp counters
Modes
Privileged EXEC mode
Examples
To clear the counters for all port-channels:
device# clear lacp counters
Syntax
clear link-oam statistics
Modes
Privileged EXEC mode
Examples
This example shows how to clears the Link OAM statistics.
device# clear link-oam statistics
Syntax
clear lldp neighbors [ interface ethernet slot/port ]
Parameters
ethernet
Use this parameter to specify an ethernet interface, followed by the slot or port number.
slot
Specifies a valid slot number.
port
Specifies a valid port number.
Modes
Usage Guidelines
If the interface parameter is not specified, this command clears the LLDP neighbor information
received on all the interfaces.
Examples
To clear the LLDP neighbor information for all interfaces:
1/9
1/10
1/11
1/12
1/13
1/14
1/15
1/16
1/17
1/18
1/19
1/20
1/21
1/22
1/23
1/24
1/25
1/29
1/30
1/31
device# clear lldp neighbors interface ethernet 1/24
device#
Syntax
clear lldp statistics [ interface ethernet slot/port ]
Parameters
ethernet
Use this parameter to specify an ethernet interface, followed by the slot or port number.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
If the interface parameter is not specified, this command clears all the LLDP statistics on all
interfaces.
Examples
To clear all the LLDP statistics for all interfaces:
0/12
0/13
0/14
0/15
0/16
0/17
0/18
0/19
0/20
0/21
0/22
0/23
device#clear lldp statistics interface ethernet 0/23
device#
Syntax
clear logging raslog [ message-type { DCE | SYSTEM } ]
Command Default
Clear all RASLog messages on the local router.
Parameters
message-type
Clears RASLog messages of the specified repository type.
SYSTEM
Clears system LOG messages.
DCE
Clears DCE application messages.
Modes
Privileged EXEC mode
Usage Guidelines
This command clears all RASLog messages by default.
SLX-OS maintains two separate internal message storage repositories, SYSTEM and DCE. A RASLog
message can have one or more type attributes. For example, a message can be of type DCE, FFDC, and
AUDIT.
Note
A message cannot have both LOG and DCE type attributes. LOG type messages are stored in
the SYSTEM message-type repository and DCE type messages are stored in the DCE
message-type repository. LOG type messages are not stored in the DCE message-type
repository and DCE type messages are not stored in the SYSTEM message-type repository.
Examples
To clear all RASLog messages:
clear loop-detection
Enables ports that were disabled by the loop detection (LD) protocol, and clears LD statistics at the
global, interface, or VLAN level.
Syntax
clear loop-detection [ interface { ethernet interface | port-channel
interface } | vlan vlan-id ]
Command Default
This feature is disabled.
Parameters
interface
Specifies an Ethernet or port-channel interface.
ethernetinterface
Specifies an Ethernet interface.
port-channelinterface
Specifies a port-channel interface.
vlan vlan-id
Specifies a VLAN.
Modes
Privileged EXEC mode
Examples
To enable LD-disabled ports and clear LD statistics on all interfaces:
device# clear loop-detection
Syntax
clear loop-detection bridge-domain BD_ID
Command Default
None
Parameters
BD_ID
Specifies a BD.
Modes
Privileged EXEC mode
Examples
The following example enables ports associated with BD 8 and clears LD statistics for that BD.
device# clear loop-detection bridge-domain 8
clear mac-address-table
Removes interface entries from the MAC address table.
Syntax
clear mac-address-table { cluster cluster-id [client [client-id] ] }
clear mac-address-table dynamic [address mac-address | bridge-domain
[id ] | interface ethernet slot/port | port-channel number | logical-
interface ethernet slot/port [:brk-out]. lif-id | vlan vlan-id]
clear mac-address-table mac-move [shut-list ]
Parameters
bridge-domain
Specifies clearing MAC addresses learned under a bridge domain.
id
Specifies a bridge-domain identifier.
cluster cluster-id
Specifies clearing MAC addresses from an MCT cluster ID. The ID range is 1 - 65535.
client client-id
Specifies clearning the client instance. Specify the client ID with a maximum of 64 characters.
dynamic address MAC-address
Specifies clearning the dynamic MAC address. The valid format is H.H.H (available in Privileged
EXEC mode only).
interface ethernet slot/port
Specifies clearning the ethernet interface with a valid slot number/port number.
port-channel number
Specifies clearning the port channel interface number.
logical-interface ethernet slot/port [:brk-out]. lif-id
Specifies clearning the logical ethernet interface on a specified slot/port number. The breakout
interface option can be used with the LIF ID.
vlan vlan id
Specifies clearning the VLAN interface. The VLAN ID range is from 1 - 4090.
shut-list
Specifies clearning the interfaces from the shutdown list.
Modes
Privileged EXEC mode.
Usage Guidelines
When a bridge-domain identifier is not specified, MAC addresses learned under all bridge domains are
removed from the MAC address table. If a specific address is not specified, all dynamic mac-addresses
are deleted from the MAC address table.
Examples
The following example shows how to clear MAC addresses learned under bridge domain 1 from the MAC
address table.
The following example shows how to clear MAC addresses learned from vlan 1 from the MAC address
table.
The following example shows how to clear MAC addresses from a logical interface ethernet 3/10 LIF
breakout interface.
Syntax
clear mpls auto-bandwith-samples [ lsp lsp_name | all ]
Parameters
lsp lsp_name
The lsp option clears the auto-bandwidth sample history for the LSP specified through the
lsp_name.
all
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example clears the sample history for LSP1.
device# auto-bandwidth-samples lsp lsp1
Syntax
clear mpls lsp lsp_name [ primary | secondary ]
Parameters
lsp_name
Specifies the target LSP by name.
primary
Specifies that the primary LSP path associated with the lsp_name is reset and restarted.
secondary
Specifies that the secondary LSP path associated with the lsp_name is reset and restarted.
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
When the user resets an LSP with the clear mpls lsp command, the following information message is
displayed.
"Disconnecting signaled LSP name"
"Connecting signaled LSP name"
Syntax
clear mpls statistics oam
clear mpls statistics { transit [ label label | ldp [ ip_addr | submask |
label ] | rsvp label ] }
clear mpls statistics { tunnel [ destination ip_addr | index vif_index |
ldp [ destination ip_addr | index vif_index ] | rsvp [ destination
ip_addr | index vif_index | name name ] ] }
Parameters
oam
Clears the MPLS OAM statistics.
transit
Clears the MPLS transit statistics.
label label
Clears the MPLS transit statistics for the selected label.
ldp ip_addr
Clears the MPLS transit LDP statisticsfor the selected IP address.
rsvp
Clears the MPLS transit RSVP statistics .
tunnel
Clears the MPLS tunnel statistics.
destination destination
Clears the MPLS tunnel statistics for the selected tunnel destination.
index vif_index
Clears the MPLS tunnel statistics for the selected tunnel index.
ldp
Clears the MPLS tunnel LDP statistics.
destination destination
Clears the MPLS tunnel statistics for the selected tunnel destination.
index vif_index
Clears the MPLS tunnel statistics for the selected tunnel index.
rsvp
Clears the MPLS tunnel RSVP statistics.
destination destination
Clears the MPLS tunnel statistics for the selected tunnel destination.
index vif_index
Clears the MPLS tunnel statistics for the selected tunnel index.
name name
Clears the MPLS tunnel statistics for the selected named tunnel.
Modes
MPLS policy mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example clears the MPLS statistics.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-mpls-policy)# clear mpls statistics
Syntax
clear mvrp statistics [ interface { ethernet slot/port | port-channel
number } ]
Parameters
interface
Clears the MVRP statistics for a specific interface.
ethernet slot/port
Specifies an Ethernet interface.
port-channel number
Specifies the port-channel interface.
Modes
Privileged EXEC mode
Usage Guidelines
If you enter this command without any options, the MVRP statistics for all Ethernet and port-channel
interfaces are cleared.
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
Examples
The following command clears the MVRP statistics for all Ethernet and port-channel interfaces.
device# clear mvrp statistics
The following command clears the MVRP statistics for a specified Ethernet interface.
device# clear mvrp statistics interface ethernet 0/1
clear overlay-gateway
Clear counters for the specified gateway.
Syntax
clear overlay-gateway name { statistics | vlan statistics }
Parameters
name
Specifies the name of the VXLAN gateway profile.
statistics
Clears all statistics for the VXLAN gateway.
vlan statistics
Clears per-VLAN statistics for the VXLAN gateway.
Modes
Privileged EXEC mode
Usage Guidelines
If you specify the VXLAN gateway name, the gateway must already be configured.
If you specify VLAN IDs, these VLANS must already be configured as exported VLANs for the gateway.
Examples
The following example clears all counters for the already configured VXLAN gateway named gateway1.
clear policy-map-counters
Clears the policy map counters.
Syntax
clear policy-map-counters [ control-plane [ policy-map-name ]]|
[ interface ethernet slot/port ] [ in | out ]
Parameters
control-plane [ policy-map-name ]
Clears the control-plane policy map counters. You can optionally enter the name of the policy-
map name.
interface
Specifies an interface.
ethernet
Represents a valid, physical Ethernet type for all available Ethernet speeds.
slot/port
Specifies a slot and port number.
in
Specifies clearing the ingress counters.
out
Specifies clearing the egress counters.
Modes
Privileged EXEC mode
Usage Guidelines
Use the clear policy-map-counters command without any keyword options to clear all of the
policy map counters.
Examples
To clear the control-plane policy map counters, use the following command:
To clear the policy map counters for a specific interface use the following command:
Syntax
clear qos flowcontrol statistics { all | ethernet slot/port | port-
channel number }
Parameters
all
Clears the flow control statistics on all interfaces in the device.
ethernet slot/port
Clears the flow control statistics on the specified interface.
port-channel number
Clears the flow control statistics on the interface for the specified port channel.
Modes
Privileged EXEC mode
Examples
The following example clears the flow control statistics for all interfaces, as displayed by the show qos
flowcontrol interface command.
device# clear qos flowcontrol statistics interface all
Syntax
clear spanning-tree counter [ interface { ethernet slot/port | port-
channel number } ]
Parameters
interface
Specifies an interface.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel.
Modes
Privileged EXEC mode
Usage Guidelines
If the interface parameter is not specified, spanning-tree counters are cleared for all interfaces.
Examples
To clear spanning-tree counters for all interfaces:
Syntax
clear spanning-tree detected-protocols [ interface { ethernet slot/port |
port-channel number } ]
Parameters
interface
Specifies an interface.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel.
Modes
Privileged EXEC mode
Usage Guidelines
If the interface parameter is not specified, spanning-tree detected protocols are cleared for all
interfaces.
Examples
To clear detected protocols on all interfaces:
Syntax
clear statistics bridge-domain bd-id
Parameters
bd-id
The bridge domain ID.
Command Default
Statistics are disabled.
Modes
Privileged EXEC mode
Usage Guidelines
This command is also available in global configuration mode.
The clear statistics bridge-domain bd-id command clears the statistics for all the logical
interfaces on a specific bridge domain.
Examples
The following example shows how to clear the statistics for all the logical interfaces on all bridge
domains.
The following example shows how to clear the statistics for all the logical interfaces on bridge domain 1.
Syntax
clear statistics vlan vlan-id
Parameters
vlan-id
The specific VLAN ID.
Command Default
Statistics are disabled.
Modes
Privileged EXEC mode
Usage Guidelines
This command is also available in global configuration mode.
The clear statistics vlan vlan-id command clears the statistics for all the ports and port
channels on the given VLAN.
Examples
The following example shows how to clear the statistics for all the ports and port channels on the given
VLAN.
The following example shows how to clear the statistics for all the ports and port channels on VLAN 10.
Syntax
clear tm voq-stat ingress-device ethernet slot/port egress-port
{ ethernet slot/port | all }
clear tm voq-stat ingress-device all egress-port { ethernet slot/port |
all }
Parameters
ethernet slot/port
Specifies the Ethernet interface in slot/port format.
egress-port ethernet slot/port
Specifies clearing the traffic management statistics on the egress Ethernet slot/ port.
all
Specifies clearing the traffic management statistics for all ports.
Modes
Privileged EXEC mode
Examples
To clear VOQ statistics information on the egress-port for Ethernet 0/1, use the following command.
device# clear tm voq-stat ingress-device ethernet 0/1 egress-port ethernet 0/1
To clear all VOQ statistics information on the egress-port for Ethernet 0/1, use the following command.
device# clear tm voq-stat ingress-device all egress-port ethernet 0/1
Syntax
clear tm voq-stat slot line-card-number cpu-group { all | cpu-group-id }
clear tm voq-stat slot line-card-number egress-port { all | ethernet
slot/port }
Parameters
line-card-number
Specifies the line card slot. For devices without line cards, specify 0.
cpu-group cpu-group-id
Specifies the ID number for the CPU group.
egress-port
Specifies an Ethernet egress port.
ethernet slot/port
Specifies the Ethernet interface in slot/port format.
all
Specifies clearing the traffic management statistics for all CPU groups or all egress ports.
Modes
Privileged EXEC mode
Examples
The following example clears information about the VOQ for the line card in slot 0 CPU group 1.
Syntax
clear tunnel statistics tunnel-id
Parameters
tunnel-id
Specifies the tunnel ID.
Modes
Privileged EXEC mode
Examples
This example removes statistics from a tunnel interface.
device# clear tunnel statistics 10
Syntax
clear udld statistics[ interface { ethernet slot/port } ]
Parameters
interface
Specifies an interface.
ethernet slot port
Specifies a valid, physical Ethernet interface with a slot and port number.
Modes
Privileged EXEC mode
Usage Guidelines
Clears either all unidirectional link detection (UDLD) protocol statistics or clears the statistics on a
specified port.
Examples
To clear UDLD statistics on a specific interface:
Syntax
clear vrrp statistics
clear vrrp statistics [ interface { ethernet slot/port | ve vlan_id } ]
clear vrrp statistics session VRID
Parameters
interface
Specifies an interface.
ethernet slot port
Specifies a valid, physical Ethernet interface with a slot and port number.
ve vlan_id
Specifies the VE VLAN number. The range is from 1 through 6144.
session VRID
Specifies the virtual group ID on which to clear statistics. The range is from 1 through 255.
Modes
Privileged EXEC mode
Usage Guidelines
This command clears VRRP session statistics for all virtual groups, for a specified interface or for a
specified virtual group.
This command is for VRRP and VRRP-E. VRRP-E supports only the ve vlan_id interface type.
To clear all vrrp statistics, use the clear vrrp statistics command with no operands.
Examples
The following example clears all VRRP statistics for all virtual groups.
device# clear vrrp statistics
The following example clears statistics for a session for a VRRP virtual group called "vrrp-group-25".
device# clear vrrp statistics session 25
The following example clears VRRP statistics on a specified virtual Ethernet (VE) interface.
device# clear vrrp statistics interface ve 10
CLI
In a Python shell, runs a device CLI command or series of commands. You can also assign the output of
such commands to a Python object.
Syntax
CLI (' device-CLI-command ' [ \n ' device-CLI-command ' ] [ [ do_print
= ] { True | False } ] )
Parameters
device-CLI-command
An SLX-OS CLI command. You separate additional commands with \n.
do_print =
Specify whether or not to print the output of device-CLI-command to the default device. The
default is to print the output.
True
Print the output.
False
Do not print the output.
Modes
Python command shell
Usage Guidelines
Divergences between the CLI syntax and Python syntax include the following differences:
• Although in general, the CLI syntax is not case-sensitive, our convention is to use lower-case.
• Python syntax is case sensitive. Regarding the syntax documented in the current topic, note the
following:
◦ The syntax of the command is upper case (CLI) and not lower case (cli).
◦ The syntax of the do_print = options is to capitalize the first letter: { True | False }
In Python, double quotes (") and single quotes (') are equivalent.
There is a difference between running a sequence of SLX-OS CLI commands in the Python shell rather
than in the standard SLX-OS interface. Whereas in the standard interface the result of a command is
persistent, in the Python shell each CLI( ) statement is independent of any preceding ones.
For support of the CLI( ) command, although a Python script must include a from CLI import
CLI statement, this statement is automatically implemented when launching the Python interpreter
interactively.
Within a script or interactive session, if you assign a CLI command or series of commands to a Python
variable, you can then append the following functions to the variable:
• .rerun()—updates the variable from a new run of the CLI command or series of commands.
device# python
Python 3.5.2 (default, Apr 11 2019, 13:05:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> cmd_show_running_ve = CLI('show running-config interface ve')
!Command: show running-config interface ve
!Time: Mon Aug 22 16:53:13 2016
% No entries found.
# The SLX-OS show running-config interface ve command is run,
# and that command is assigned to the Python variable cmd_show_running_ve.
>>> cmd_show_running_ve.rerun()
# The rerun() function appended to cmd_show_running_ve gives the following output:
!Command: show running-config interface ve
!Time: Mon Aug 22 16:53:13 2016
interface Ve 101
shutdown
!
interface Ve 102
shutdown
!
interface Ve 103
shutdown
!
!
• .get_output()—returns the value of a new run of the CLI command or series of commands, as a
list. Running this script displays the "Firmware name" line of the show version command.
#Required in all scripts for SLX:
from CLI import CLI
# Using .get_output(), assign the result of show ver to a Python object named output:
output = cmd_show_ver.get_output()
print("FIRMWARE:\n")
for key in slot_firmware:
print("\t", key, "\t=> ", slot_firmware[key])
Examples
The following example launches the Python shell and then both assigns a series of CLI configuration
commands to a Python variable and runs those commands.
device# python
Python 3.5.2 (default, Apr 11 2019, 13:05:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> cmd_config_ve = CLI('configure \n interface ve 101-103')
!Command: configure
interface ve 101-103
!Time: Mon Aug 22 16:57:36 2016
>>>
The following example launches the Python shell and then both assigns a CLI operational command
(reload system) to a Python variable and runs that command.
device# python
Python 3.5.2 (default, Apr 11 2019, 13:05:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> cmd_reload_system = CLI('reload system \n y')
client
Configures a Multi-Chassis Trunking (MCT) client for a cluster and access cluster client configuration
mode.
Syntax
client client-name client-id
no client client-name client-id
Parameters
client-name
Specifies the client name as an ASCII string. The name can be up to 64 characters in length.
client-id
Specifies the cluster client ID. The ID value range can be from 1 through 512.
Modes
Cluster client configuration mode
Usage Guidelines
On both MCT nodes, you must configure the same client ID.
The no form of the command removes the client from the MCT cluster configuration.
Examples
The following example configures a cluster client.
device(config)# cluster MCT1 1
device(config-cluster-1)# client MCT1-client 200
device(config-cluster-client-200)#
client-interface
Configures a CEP or CCEP interface to the cluster client instance.
Syntax
client-interface { ethernet slot/port | port-channel number }
no client-interface
Parameters
ethernet slot/port
Configures the specified Ethernet port as the client CEP or CCEP.
port-channel number
Configures the specified port channel as the client CEP or CCEP. The port channel number
specifies the LAG ID.
Modes
Cluster client configuration mode
Usage Guidelines
The no form of the command removes the client interface.
The same client interface cannot be added under multiple client entries.
A client interface is not allowed to be updated when the client is in deploy state. It needs to be removed
first before adding a new interface.
Examples
The following example shows how to configure a client interface.
device(config)# cluster MCT1 1
device(config-cluster-1)# client MCT1-client 200
device(config-cluster-client-200)# client-interface port-channel 3
client-interface (Y1731)
Associates either a physical interface or a port-channel interface to a Y1731 Maintenance Entity Group
End Point (MEP) as a client interface.
Syntax
client-interface { ethernet slot/port [:subport ] | port-channel number }
csf-type { loss-of-signal } tx-period [1-minute | 1-second ]
no client-interface { ethernet slot/port [:subport ] | port-channel
number }
Command Default
This command has no defaults.
Parameters
ethernet slot/port
Specifies an Ethernet slot and port with optional subport.
port-channel number
Specifies a port-channel.
csf-type loss-of-signal
Specifies the Client Signal Failure (CSF) type as C-LOS (the currently supported option).
tx-period
Specifies a transmission period. The following options are currently supported.
1-minute
Specifies 1 minute.
1-second
Specifies 1 second.
Modes
MEP configuration mode
Usage Guidelines
This command associates an Ethernet Client Signal Fail (ETH-CSF) client interface to an MEP and
configures a transmission-period for the ETH-CSF frames to be transmitted towards the peer Remote
MEP (RMEP).
Use the no form of this command to remove the association of the client interface with the MEP.
Examples
This example specifies a client interface on Ethernet interface 1/2 with CSF type C-LOS and transmission
period of 1 minute for Down MEP 1 in MD md1 and MA ma1.
device# configure terminal
Entering configuration mode terminal
device(config)# protocol cfm
device(config-cfm)# domain-name md1 id 1 level 3
device(config-cfm-md-md1)# ma-name ma1 id 1 vlan 10 priority 7
device(config-cfm-md-ma-ma1)# mep 1 down ethernet 1/1
device(config-cfm-md-ma-mep-1)# client-interface ethernet 1/2 csf-type loss-of-signal tx-
period 1-minute
This example removes the association of the client interface with the MEP.
device(config-cfm-md-ma-mep-1)# no client-interface ethernet 1/2
client-interfaces-shutdown
Disables the local client interfaces administratively in the cluster to move all traffic on the device to a
remote MCT peer device, resulting in failover of traffic to the peer device.
Syntax
client-interfaces shutdown
no client-interfaces shutdown
Modes
Cluster configuration mode
Usage Guidelines
You can use this command to move traffic to a peer device when you are upgrading the local client
interfaces.
Examples
The following example shows the disabling of all the client interfaces in the cluster.
device(config)# cluster MCT1 1
device(config-cluster-1)# client-interfaces shutdown
client-pw
Configures the pseudowire (PW) client for an MCT cluster used with VPLS or VLL and access cluster
client PW configuration mode.
Syntax
client-pw
no client-pw
Modes
Cluster configuration mode
Usage Guidelines
This command is not supported on the SLX 9150 or SLX 9250 devices.
Only one instance of the PW client represents all VPLS or VLL PWs over all bridge domains.
The no form of the command removes the PW client from the MCT cluster configuration.
Examples
The following example configures a cluster client.
device# configure terminal
device(config)# cluster MCT1 1
device(config-cluster-1)# client-pw
device(config-cluster-client-pw)#
client-to-client-reflection
Enables routes from one Route Reflector (RR) client to be reflected to other clients by the host device
on which it is configured.
Syntax
client-to-client-reflection
no client-to-client-reflection
Command Default
Enabled
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
When this command is used, the host device on which it is configured becomes the route-reflector
server.
Examples
The following example configures client-to-client reflection on the BGP host device for the IPv4 unicast
address-family.
The following example disables client-to-client reflection on the BGP host device for the IPv6 unicast
address-family.
The following example configures client-to-client reflection in L2VPN EVPN configuration mode.
clock set
Sets the local clock time and date.
Syntax
clock set hh:mm:ss mm-dd-yy/yyyy
Parameters
hh:mm:ss
Specifies the local clock time in hours, minutes, and seconds.
mm-dd-yy/yyyy
Specifies the local clock date in month, day, and year format. Year may be specified with two or
four numbers.
Modes
Privileged EXEC mode
Usage Guidelines
Valid date and time settings range from January 1, 1970 to December 31, 2035.
An active NTP server, if configured, automatically updates and overrides the local clock time.
Examples
The following example sets the time and date to 31 minutes past 4 pm in the afternoon on July 28, 2016,
for the local device:
device# clock set 16:31:35 07-28-16
clock timezone
Sets the device system clock time zone options using either Greenwich Mean time (GMT) or one of the
US time zones that uses Universal Time Coordinated (UTC) plus or minus a number of hours.
Syntax
clock timezone { gmt gmt-time | us us-time }
no clock timezone { gmt gmt-time | us us-time }
Parameters
gmt gmt-time
Specifies the GMT time zone. The value can be one of the following: gmt+00 (United Kingdom),
gmt+01 (France, Germany), gmt+02 (Eastern Europe, South Africa), gmt+03, gmt+03:30, gmt
+04, gmt+04:30, gmt+05, gmt+05:30 (India), gmt+06, gmt+06:30, gmt+07, gmt+08 (China,
Hong Kong, Taiwan), gmt+09 (Japan, Korea), gmt+09:30, gmt+10 (Australia), gmt+10:30, gmt+11,
gmt+11:30, gmt+12, gmt-01, gmt-02, gmt-03, gmt-03:30, gmt-04, gmt-05, gmt-06, gmt-07,
gmt-08, gmt-08:30, gmt-09, gmt-09:30, gmt-10, gmt-11, gmt-12.
us us-time
Specifies the US time zone. The value can be one of the following: alaska, aleutian, arizona,
central, east-indiana, eastern, hawaii, michigan, mountain, pacific, samoa.
Modes
Global configuration mode
Examples
The following example sets the system date and time to the US Samoa time zone.
device(config)# clock timezone us samoa
cluster
Configures a Multi-Chassis Trunking (MCT) cluster and access the cluster configuration mode.
Syntax
cluster cluster-name
no cluster cluster-name
Parameters
cluster-name
Specifies the cluster name as an ASCII string. The cluster name can be up to 64 characters in
length.
Modes
Global configuration mode
Usage Guidelines
The no form of the command removes the MCT cluster configuration.
Examples
The following example configures an MCT cluster.
device(config)# cluster MCT1
device(config-cluster-MCT1)#
cluster-track
Configures interface to track state of MCT cluster.
Syntax
cluster-track
[no] cluster-track
Parameters
cluster-track
Configures interface to track state of MCT cluster.
Modes
Interface sub-mode
Usage Guidelines
This command helps reduce convergence for reload cases by diverting traffic to alternate paths. The
cluster tracked ports are brought down along with MCT clients for these reasons:
Once the cluster status comes up, the cluster tracking interfaces are brought up along with the cluster
clients. When none of the above conditions are true, the configuration has no effect on the interface
state.
When the interface is disabled due to cluster status, admin shut/no shut on the port has no effect. [no
cluster-track] removes the cluster-track configuration from the port. This port no longer tracks
the status of the MCT cluster.
This command can be configured on L2 or L3 Ethernet or port-channel interfaces. The interface should
not be a port channel member and is only valid when cluster configuration is present.
Examples
SLX(config)# int eth 0/3
SLX(conf-if-eth-0/3)# cluster-track
SLX(conf-if-eth-0/3)# do sh run int eth 0/3
interface Ethernet 0/3
description uplink_spine1
cluster-track
switchport
switchport mode trunk
switchport trunk tag native-vlan
no shutdown
commit
Use the commit command to commit modifications done to adaptive parameters of a bypass LSP. This
command also applies to LSPs. This is not a configuration persistent command; it is a functional
command.
Syntax
commit
Command Default
Automatic commit is considered when it is configured to do so in the MPLS global mode.
Modes
MPLS router bypass LSP configuration mode (config-router-mpls-bypass-lsp_name ).
Usage Guidelines
Once modifying one or more adaptive parameters, the user can commit the changes such that the new
instance of the bypass LSP can be brought up. When successful, then a make-before-break switch
happens from the current instance of the bypass to the new UP instance.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example shows the configuration for the commit command.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# bypass-lsp my-bypass-lsp
device(config-router-mpls-bypass-lsp-my-bypass-lsp)# commit
compare-med-empty-aspath
Enables comparison of Multi-Exit Discriminators (MEDs) for internal routes that originate within the
local autonomous system (AS) or confederation
Syntax
compare-med-empty-aspath
no compare-med-empty-aspath
Command Default
Disabled.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example configures the device to compare MEDs.
compare-routerid
Enables comparison of device IDs, so that the path-comparison algorithm compares the device IDs of
neighbors that sent otherwise equal-length paths.
Syntax
compare-routerid
no compare-routerid
Modes
BGP configuration mode
Examples
The following example configures the device always to compare device IDs.
confederation identifier
Configures a BGP confederation identifier.
Syntax
confederation identifier autonomous-system number
no confederation identifier
Command Default
No BGP confederation identifier is identified.
Parameters
autonomous-system number
Specifies an autonomous system number (ASN). The configurable range of values is from 1
through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes a BGP confederation identifier.
Examples
The following example specifies that confederation 65220 belongs to autonomous system 100.
confederation peers
Configures subautonomous systems to belong to a single confederation.
Syntax
confederation peers autonomous-system number [ …autonomous-system
number ]
no confederation peers
Command Default
No BGP peers are configured to be members of a BGP confederation.
Parameters
autonomous-system number
Autonomous system (AS) numbers for BGP peers that will belong to the confederation. The
configurable range of values is from 1 through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes an autonomous system from the confederation.
Examples
The following example configures autonomous systems 65520, 65521, and 65522 to belong to a single
confederation under the identifier 100.
configure terminal
Enters global configuration mode.
Syntax
configure terminal
Modes
Privileged EXEC mode
Examples
The following example moves from privileged EXEC mode to global configuration mode.
device# configure terminal
Entering configuration mode terminal
device(config)#
config-drift-track
Disables configuration drift detection for the current session.
Syntax
config-drift-track off
Parameters
off
Switches off configuration drift detection for the current session.
Modes
Privilege Execution Mode
Usage Guidelines
Configuration drift detection is turned off for the current session when this command is executed. Any
configuration changes made after turning off drift detection is not tracked by SLX.
Configuration drift detection is enabled by default for all sessions. It must be explicitly turned off for a
session to prevent SLX from tracking configuration changes made in that session.
Examples
The following example shows how to switch off the configuration drift tracking feature.
SLX# config-drift-track off
connector
Accesses connector configuration mode for the ports that support the breakout feature and the insight
port feature.
Syntax
connector 0/port
Parameters
0/port
Specifies a valid port number on the device that supports breakout mode or insight mode.
Modes
Hardware configuration mode
Usage Guidelines
In connector configuration mode, you can break out the port that supports the breakout feature into
four 10G or 25G breakout interfaces, or you can enable or disable the port that supports the insight port
feature.
Examples
This example shows how to access the connector configuration mode on a supported port on SLX
9640.
device# configure terminal
device(config)# hardware
device(config-hardware)# connector 0/25
control-word
Enables control word for a pseudowire (PW) profile.
Syntax
control-word
no control-word
Command Default
By default, control word is disabled for PW profiles.
Modes
Pseudowire profile configuration mode
Usage Guidelines
The no form of the command disables control word for a PW profile.
For a PW that is sensitive to packet misordering to operate correctly, all packets in the PW must follow
the same path over a Multi-Protocol Label Switched (MPLS) packet switched network (PSN).
PW control word is a mechanism that prevents packet misordering. Without the control word
mechanism, a label switching router (LSR) performing, for example, equal-cost multiple-path load-
balancing (ECMP) could mistake a PW payload for an IPv4 or IPv6 packet and route it over a different
path, resulting in misordered packet delivery to the egress provider edge (PE) device.
When control word is enabled, LSRs use it to distinguish a specific PW payload from an IP payload and
ensure that all packets for the PW follow the same path over the MPLS PSN.
Note
When control word is enabled for a previously configured PW, control word capabilities
between PE devices are activated only after LDP neighbors are cleared by using the clear
mpls ldp neighbor command. For further information on clearing LDP neighbors, refer
to Extreme SLX-OS MPLS Configuration Guide.
Examples
The following example shows how to enable PW control word for a PW profile named pw_example
The following example shows how to disable PW control word for a PW profile named pw_example
console
Configures the height and width of the serial console terminal.
Syntax
console [ height number_of_rows] [ width number_of_columns ]
Command Default
By default, the serial console is 24 rows high and 80 rows wide.
Parameters
height number_of_rows
Specifies the height of the serial console in rows. Valid values range from 1 through 256.
width number_of_columns
Specifies the width of the serial console in columns. Valid values range from 1 through 256.
Modes
Privileged EXEC mode
Usage Guidelines
Configure the size of the serial console terminal to prevent overwritten or misaligned console output
when multiple users connect to the serial console. The terminal emulators that connect to the console
must have the same window size as the console to prevent overwritten or misaligned output.
The configuration of the console size does not persist after a reboot.
Use the console command without options to display the size of the serial console terminal.
Examples
The following example displays the size of the serial console terminal.
device# console
The following example configures a height of 43 rows and a width of 132 columns.
device# console height 43 width 132
copy
Copies configuration data.
Syntax
copy source_file destination_file [ remove-tpvm ]
Parameters
source_file
The source file to be copied. Specify one of the following parameters:
default-config
The default configuration.
running-config
The running configuration.
startup-config
The startup configuration.
flash:// filename
A file in the local flash memory.
ftp:// username:password@host_ip_address/path
A file on a remote host. Transfer protocol is FTP.
scp:// username:password@host_ip_address/path
A file on a remote host. Transfer protocol is SCP.
sftp:// username:password@host_ip_address/path
A file on a remote host. Transfer protocol is SFTP.
tftp:// username:password@host_ip_address/path
A file on a remote host. Transfer protocol is TFTP.
usb:// path
A file on an attached USB device.
destination_file
The destination file. Specify one of the following parameters:
default-config
The default configuration.
running-config
The running configuration.
startup-config
The startup configuration.
flash:// filename
A file in the local flash memory.
ftp:// username:password@host_ip_address//path
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to back up and restore configuration files with various protocols.
The special characters of dollar sign "$" and exclamation point "!" can be used as part of the password
variable, provided they are paired with the correct escape characters. The "$" must be paired with two
backslashes "\\". For example, if your password choice was "$password" on a remote server, you must
use "username:\\$password@1.1.1.1" for the copy command. The exclamation point must be paired with
a single backslash in the copy command, such as "username:\!password@1.1.1.1".
When using a file to restore a backed up configuration as the startup configuration, care must be taken
to ensure that the source file's TPVM configuration is the same as the running TPVM's configuration.
Particularly, if the source's TPVM configuration is partial, and does not have some of the configured
parameters of the running TPVM instance. In such a scenario, it is advised not to proceed with this
change as it will result in the configuration of the installed TPVM not being similar to the configuration
of the previous TPVM instance.
Examples
To save the running configuration to a file:
To overwrite the startup configuration with a configuration file saved on an attached USB device:
To overwrite the startup configuration with the default configuration. This will wipe out the device's
configuration but will reinstall and reconfigure the TPVM installation on the device.
To overwrite the startup configuration with the default configuration. This will wipe out the device's
configuration including the TPVM installed on the device.
core-isolation-disable
Core Isolation feature shuts down ESI interface(s) when all the core interfaces between the Leaf and
Spine nodes go down. This feature is enabled by default. Use this command to disable this feature.
When disabled, the ESI interface will not be brought down when all the core interfaces between the
Leaf and Spine go down.
Syntax
core-isolation-disable
no core-isolation-disable
Command Default
Core Isolation is enabled by default. It has to be explicitly disabled using this command.
Modes
Global configuration mode
Examples
The following example shows the disabling of the core-isolation feature
SLX # configure terminal
SLX (config)# core-isolation-disable
core-isolation-track
Core Isolation feature shuts down ESI interface(s) when all the core interfaces between the Leaf and
Spine nodes go down. During core-isolation, data traffic will be black-holed in the multi-homing nodes if
the single homed edge port interfaces are present and the Ethernet VPN Instance VLANs are shared
with these interfaces. These single homed edge port interfaces need to be brought up/down along with
the ESI client interfaces for better data convergence. This command enables tracking these single
homed edge port interfaces to ensure that they are brought up/down along with ESI client interfaces.
Syntax
core-isolation-track
no core-isolation-track
Command Default
Core Isolation tracking is disabled by default. It has to be explicitly enabled using this command.
Modes
Interface Configuration Mode (for Ethernet and Port Channel interfaces only).
Usage Guidelines
This command ensures that that the configured single homed edge port interface is brought down
along with the ESI interfaces. When the BGP EVPN sessions come up, these tracked single homed edge
port interfaces are brought up along with the ESI interfaces to have better data traffic convergence.
This feature is only available when ESI is configured on (at least) a single interface.
Core Isolation Tracking cannot be applied to an interface that is a port-channel member. That is, the
interface must not have channel-group configuration present.
The interface on which Core Isolation Tracking is applied to, must not be a multi-homed client. Post this
configuration, the tracked interface cannot be assigned as a PO member or a multi-homing client.
Examples
The following example shows the configuration of Core Isolation Tracking on a port-channel interface.
SLX (config)# interface port-channel 1
SLX (config-Port-channel-1)# core-isolation-track
The following example shows the configuration of Core Isolation Tracking on an ethernet interface.
SLX (config)# interface ethernet 0/1
SLX (config)# core-isolation-track
cos (MPLS)
Configures the a Class of Service (CoS) priority value for all packets traveling through the LSP.
Syntax
cos number
no cos number
Parameters
number
Specifies the CoS priority value. Enter a number from 0 to 7. The lowest priority is 0, the default
value. The highest priority is 7.
Modes
MPLS LSP configuration mode.
Usage Guidelines
The 3-bit EXP field in the MPLS header defines a CoS value for packets traveling through the LSP. When
you set the CoS value, it is applied to the EXP field in the MPLS header of all packets entering this LSP.
Then, all packets traveling through an LSP have the same priority as they travel the MPLS domain.
The MPLS CoS value determines the priority within an MPLS domain only. When the label is pops, the
CoS value in the MPLS header is discarded and it is not copied back to the IP ToS field.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
cos (Y1731)
Configures class of service (CoS).
Syntax
cos class-of-service
no cos
Parameters
class-of-service
Specifies the CoS value. The range is from 1 to 8. The default value is 7.
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the CoS configuration.
Examples
This example shows how to configure CoS.
device# configure terminal
device (config-cfm)# prtocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device(config-cfm-y1731-test-profile-my_test_profile)# tx-interval 60
device(config-cfm-y1731-test-profile-my_test_profile)# measurement-interval 30
device(config-cfm-y1731-test-profile-my_test_profile)# start at 00:00:00 daily
device(config-cfm-y1731-test-profile-my_test_profile)# stop at 23:59:00
device(config-cfm-y1731-test-profile-my_test_profile)# cos 7
crypto ca authenticate
Identifies the root CA certificate, which is used to sign the Certificate Signing Request (CSR) to
generate the server certificate.
Syntax
crypto ca authenticate {trustpoint-name cert-type { commoncert | https |
ssh-x509v3}directory dirname file file-name host host-address
protocol source-ipsource-ip{FTP | SCP} user user-name password
password}
no crypto ca authenticate { trustpoint_name cert-type { commoncert |
https | ssh-x509v3}
Parameters
trustpoint-name
Defines the name of the trustpoint you are authenticating. This name needs to be the same as
that of the trustpoint created by the crypto ca trustpoint command. The string for the
name cannot be left blank. The length of the string can range from 1 through 64 characters.
cert-type {commoncert | https | ssh-x509v3}
Indicates that the certificate is used for common, HTTPS, or SSH-x509v3 server authentication.
directory dir-name
Defines the path to the directory where the certification file resides.
file file-name
Defines the name of the certification file.
host host-address
Specifies the host name or IP address of the remote certificate server.
protocol {FTP | SCP}
Specifies the use of either FTP or SCP protocol for accessing the certification file.
user user-name
Specifies the user name for the host server.
source-ip source-ip
(SCP only) Specifies the source IP address to use in the header.
password password
Specifies the password for the user to access the host server.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to identify the CA certificate of the Trusted CA that you want to sign the CSR and
generate the identity certificate.
The trustpoint-name name needs to be the same as that of the trustpoint created by the crypto
ca trustpoint command.
Note
As a best practice, do not list the password in the command line for security purposes. The
user will be prompted for the password.
Examples
This example specifies HTTPS authentication and the SCP protocol.
device# crypto ca authenticate t1 cert-type https protocol SCP host 10.70.12.102
user fvt directory /users/home/crypto file cacert.pem password ****
crypto ca enroll
Enrolls the trustpoint by generating the Certificate Signing Request (CSR) and exporting it to the
remote certificate server.
Syntax
crypto ca enroll {trustpoint-name cert-type {commoncert | https | ssh-
x509v3} common common-name country country-name state state-name
locality locality-name organization org-name orgunit org-unit
directory dir-name file file-name host host-address source-ip source-
ip protocol {FTP | SCP} user user-name password password}
Parameters
trustpoint-name
Defines the name of the trustpoint you are enrolling. This name needs to be the same as that of
the trustpoint created by the crypto ca trustpoint command. The string for the name
cannot be left blank. The length of the string can range from 1 through 64 characters.
cert-type commoncert | https | ssh-x509v3}
Indicates that the certificate is used for common, HTTPS, or SSH-x509v3 server authentication.
common common-name
Identifies the name used to connect to the device through HTTPS. Enter a Fully Qualified Domain
Name (FQDN) or IP address. If a FQDN is used, you need to configure a domain name and name
server on the device.
country country-name
Defines the two-letter country code for generating the CSR.
state state-name
Defines the state name for generating the CSR.
locality locality-name
Defines the locality name for generating the CSR.
organization org-name
Defines the organizational unit name for generating the CSR.
orgunit orgunit
Defines the name of the certification file.
directory dir_name
Defines the path of the directory to export the Certificate Signing Request.
file file-name
Defines the file name of the CSR.
host host-address
Specifies the host name or IP address of the remote certificate server.
source-ip source-ip
Note
As a best practice, do not list the password in the command line for security
purposes. The user will be prompted for the password.
Modes
Privileged EXEC mode
Usage Guidelines
The trustpoint_name name needs to be the same as that of the trustpoint created by the crypto
ca trustpoint command.
Examples
Typical command example:
device# crypto ca enroll t1 cert-type https country US state CA locality SJ
organization EXT orgunit SFI common myhost.extreme.com protocol SCP host 10.70.12.102
user fvt directory /proj/crypto
crypto ca import
Imports the Identity Certificate for security configuration.
Syntax
crypto ca import { trustpoint-name cert-type {commoncert | https | ssh-
x509v3 } protocol {FTP | SCP} directory dir-name file file-name host
host-address user user-name password password source-ip source-ip}
no crypto ca import {trustpoint-name cert-type {commoncert | https | ssh-
x509v3 } }
Parameters
trustpoint-name
Defines the name of the trust point you are authenticating. This name needs to be the same as
that of the trust point created by the crypto ca trustpoint command. The string for the
name cannot be left blank. The length of the string can range from 1 through 64 characters.
cert-type commoncert | https | ssh-x509v3}
Indicates that the certificate is used for common, HTTPS, or SSH-x509v3 server authentication.
protocol {FTP | SCP}
Specifies the use of either FTP or SCP protocol for accessing the certificate file.
directory dir-name
Defines the directory where the certificate resides.
file file-name
Defines the name of the certificate file.
host host-address
Defines the host name or IP address of the remote certificate server.
user user-name
Defines the user name for the host server.
source-ip source-ip
(SCP only) Specifies the source IP address to use in the header.
password password
Defines the password for the user name on the host server.
Note
As a best practice, do not list the password in the command line for security
purposes. The user will be prompted for the password.
Modes
Privileged EXEC mode
Usage Guidelines
The trustpoint-name name needs to be the same as that of the trust point created by the crypto
ca trustpoint command.
Examples
This example specifies HTTPS authentication and the SCP protocol.
device# crypto ca import t1 certificate cert-type https protocol SCP host 10.70.12.102
user fvt directory /users/crypto file cacert.pem
Password: **********
crypto ca import-pkcs
Imports a TLS certificate and a private key in PKCS12 format.
Syntax
crypto ca import-pkcs { type pkcs12 cert-type { gNMI-server | https |
ldap-client | radius-client | syslog-client } protocol { FTP | SCP }
directory dir-name file file-name source-ip source-ip host host-
address user user-name password scp-password [ pkcs-passphrase pkcs-
export-password ] [ use-vrf vrf-name ] }
no crypto ca import-pkcs type pkcs12 cert-type {gNMI-server | https |
ldap-client | radius-client | syslog-client }
Parameters
type pkcs12
Indicates that the private key for the CA certificate is in the <term>pkcs12</term> format.
cert-type {https | gNMI-server | https | ldap-client radius-client |
syslog-client }
Indicates that the certificate is used for HTTPS and gNMI server authentication. Additionally, now
certificates for LDAP Client, RADIUS Client, and SYSLOG Clients can be imported and used for
authentication.
protocol { FTP | SCP }
Specifies the use of either FTP or SCP protocol for accessing the remote certificate file.
directory dir_name
Defines the remote directory where the certificate resides.
file file-name
Defines the file name of the certificate file in .pfx or .p12 format.
host host-address
Defines the host name or IP address of the remote certificate server.
source-ip source-ip
(SCP only) Specifies the source IP address to use in the header.
user user-name
Defines the user name for the remote certificate server.
password scp-password
Defines the password for the user name on the remote certificate server.
Note
When the password is not provided in the CLI command, the user will be
prompted for it when the CLI is executed.
pkcs-passphrase pkcs-export-password
Defines the password used at the creation of the .pfx or .p12 certificate file.
use-vrf vrf-name
Defines the VRF to use to reach the remote certificate server.
Modes
Privileged EXEC mode
Usage Guidelines
Use the below mentioned command to import a TLS server certificate and private key (in PKCS12
format) to an SLX device (with no trust point) and establish a secure connection.
Note
Server Certificates are to be imported on the SLX device mandatorily, before configuring
gNMI server.
CLI Command:
crypto ca import-pkcs {type pkcs12 cert-type gNMI-server } protocol {FTP | SCP} directory
dir-name file file-name source-ip source-ip host host-address user user-name password scp
password [ pkcs-passphrase pkcs-export-password ] [ use-vrf vrf-name ]}
crypto ca import-pkcs {type pkcs12 cert-type https } protocol {FTP | SCP} directory dir-
name file file-name source-ip source-ip host host-address user user-name password scp
password [ pkcs-passphrase pkcs-export-password ] [ use-vrf vrf-name ]}
• HTTPS Server
• gNMI Server
Examples
This example specifies HTTPS authentication and SCP using a VRF named red.
device# crypto ca import-pkcs12 cert-type https protocol SCP host 10.70.12.102
user fvt directory /users/crypto file pkcs12cert.p12 password **********
pkcs-passphrase ******** use-vrf red
crypto ca trustpoint
Defines the trust point for HTTPS security configuration.
Syntax
crypto ca trustpoint trustpoint-name
no crypto ca trustpoint trustpoint-name
Parameters
trustpoint-name
Defines the name of the trustpoint. The string for the name cannot be left blank. The length of
the string can range from 1 through 64 characters.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to remove the trustpoint.
Examples
Typical command examples:
device(config)# crypto ca trustpoint t1
device(config)# crypto ca trustpoint trustpoint2
device(config)# crypto ca trustpoint tp3
device(config)# crypto ca trustpoint t4
device(config)# crypto ca trustpoint t5
crypto cert
Configures generating RASLog entries for certificate expiry. Depending on the number of days to
certificate expiry, RASLog entries with different warnings can be generated.
Syntax
crypto cert expiry-level [ info | minor | major | critical ] period 1-90
no crypto cert expiry-level [ info | minor | major | critical ] period
1-90
Parameters
expiry-level [ info | minor | major | critical ]
Type of certificate expiry warning.
period 1-90
Number of days till certificate expires.
Modes
Configuration mode
Usage Guidelines
When configured, a RASLog is created with a warning with the configured severity level along with a
serial number of the certificate for which this entry is being generated. A RASLog entry is generated for
every certificate that will expire within the next ninety (90) days.
A single warning is generated when the number of days remaining for expiry is equal to (=) or becomes
(<) lesser than the configured period for that severity level.
Certificate expiry checks are done once every day at 00:00 hours (midnight). Depending on the setting
of the notAfter field in each certificate, RASLog generation may be delayed up to 24 hours.
Note
RASLog is generated only after the configuration.
When a certificate expires, a RASLog with an severity error is generated every 24 hours till the expired
certificate is renewed. This RASLog is not affected by the configurations of the expiry levels.
If the SLX device's system time is manually changed after a RASLog is generated, SLX does not send
the RASLog again unless the specific crypto severity level is reconfigured to previous RASLog or the
specfic certificate for which RASLog is sent is re-imported.
Server certificates imported using the crypto commands are provided with pkcs12 option. This pkcs12
option is considered when expiry is checked. CAs of TLS clients are imported using different import
commands. These import commands do not support pkcs12 options and are not considered for expiry
check.
When more than one alert level is configured with same period value, RASLog is generated for higher
severity level.
Examples
The following example show the configuration of the four (4) certificate expiry warning levels.
SLX # configure terminal
SLX (config)# crypto cert expiry-level info period 90
SLX (config)# crypto cert expiry-level minor period 45
SLX (config)# crypto cert expiry-level major period 15
SLX (config)# crypto cert expiry-level critical period 5
SLX (config)#
crypto import
Imports the Identity Certificate for security configuration.
Syntax
crypto import { ldapca | radiusca | syslogca | gnmiclientca |
httpsclientca } directory dir-name file file-name host host-address
protocol { FTP | SCP } source-ip source-ip user user-name password
password
no crypto import { ldapca | radiusca | syslogca |gnmiclientca |
httpsclientca }
Parameters
ldapca | radiusca | syslogca | gnmiclientca | httpsclientca
Defines the type of certificate to import. Select from ldapca, radiusca, syslogca, gnmiclientca, or
httpsclientca.
directory dir-name
Defines the remote directory where the certificate file resides.
file file-name
Defines the name of the certification file.
host host-address
Defines the host name or IP address of the remote certificate server.
protocol { FTP | SCP }
Specifies the use of either FTP or SCP protocol for accessing the certificate file.
source-ip source-ip
(SCP only) Specifies the source IP address to use in the header.
user user-name
Defines user name for the remote certificate server.
password password
Defines the password for the user name for the remote certificate server.
Note
When the password is not provided in the CLI command, the user will be
prompted for it when the CLI is executed.
Note
gNMI Client CA is needed for mutual TLS communication. For server based
authentication, gNMI Client CA is optional.
Modes
Privileged EXEC mode
Usage Guidelines
Use the no form of the command to remove the Identity Certificate.
Examples
This example imports a RADIUS certificate over SCP.
device# crypto import radiusca t1 certificate protocol SCP host 10.10.10.10
user fvt directory /users/crypto file cacert.pem password ****
crypto key
Generates an RSA, ECDSA, or DSA key pair to sign or encrypt and decrypt the security payload during
security protocol exchanges for applications. You must sign and encrypt or decrypt the key pair before
you obtain a certificate for your device.
Syntax
crypto key label key-name [rsa | ecdsa | dsa] [modulus bit-value]
no crypto key label key-name
Parameters
label key-name
The name of the key pair.
rsa
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to remove the key pair.
Examples
Typical command examples for generating a key pair.
device(config)# crypto key label k1 rsa modulus 1024
device(config)# crypto key label key2 rsa modulus 2048
device(config)# crypto key label pvtkey3 dsa modulus 1024
device(config)# crypto key label k4 ecdsa modulus 384
device(config)# crypto key label k5 ecdsa modulus 521
csnp-interval
Configures the Complete Sequence Number PDU (CSNP) interval.
Syntax
csnp-interval secs
no csnp-interval
Command Default
The default CSNP interval is 10 seconds.
Parameters
secs
Specifies the interval in seconds. Valid values range from 0 through 65535 seconds.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The interval configured on the device applies to both Level 1 and Level 2 CSNPs and Partial Sequence
Number PDUs (PSNPs).
Examples
The following example configures a CSNP interval of 25 seconds.
device# configure terminal
device(config)# router isis
device(config-isis-router)# csnp-interval 25
cspf-computation-mode
The path calculation metric implementation allows you to specify the path calculation for a given tunnel.
Syntax
cspf-computation-mode { [ ignore-overload-bit | metric-type [ use-bypass-
metric | use-igp-metric | use-te-metric ] ] }
no cspf-computation-mode { [ ignore-overload-bit | metric-type [ use-
bypass-metric | use-igp-metric | use-te-metric ] ] }
Command Default
By default, all LSPs use the TE-metric global configuration.
Parameters
ignore-overload-bit
Ignores the overload bit during CSPF computation.
metric-type
Select for CSPF computation.
use-bypass-metric
Use the bypass metric to enable the bypass path cost for the backup path.
use-igp-metric
Use to configure the metric plane to IGP-configured metric while computing the CSPF path.
use-te-metric
Use to configure the metric plane to the TE-configured metric while computing the CSPF path.
Modes
Global level (config-router-mpls-policy): This configuration covers all RSVP LSPs (primary, secondary
LSPs).
Usage Guidelines
The CLI configuration at the LSP level always overrides the configuration at the global level. That is, the
decision to use-te-metric or use-igp-metric for CSPF path calculation if configured at the LSP
level, always overrides the configuration at the global level.
The user can configure the CSPF computation mode for the CSPF Path calculation of dynamic bypass
LSPs that get created. CSPF can make use of either the TE-metric as cost or the IGP metric as cost for
the shortest path first algorithm.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
In the following example, the CSPF computation mode is set back to a default value of the te-metric
at the global level.
device# configure
device(config)# router-mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# cspf-computation-mode metric-type use-igp-metric
device(config-router-mpls-policy)# no cspf-computation-mode metric-type use-te-metric
Error:CSPF computation is configured to use igp-metric
device(config-router-mpls-policy)# no cspf-computation-mode metric-type use-igp-metric
In the following example, the CSPF computation mode is set back to a default value of the use-te-
metric at the LSP level.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp test
device(config-router-mpls-lsp-test)# cspf-computation-mode metric-type use-igp-metric
device(config-router-mpls-policy)# no cspf-computation-mode metric-type use-te-metric
Error:CSPF computation is configured to use-igp-metric
device(config-router-mpls-policy)# no cspf-computation-mode metric-type use-igp-metric
In the following example, both the cost and number of riding backups are considered using the use-
bypass-metric command.
device# configure
device(config)# router-mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# cspf-computation-mode metric-type use-bypass-metric
In the following example, both the cost and number of riding backups are considered using the use-
igp-metric command for dynamic bypass MPLS Ethernet interface 0/8.
device# configure
device(config)# router-mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# cspf-computaion-mode use-igp-
metric
cspf-interface-constraint
Forces the CSPF calculation to include any specified interface when creating an LSP.
Syntax
cspf-interface-constraint
no cspf-interface-constraint
Command Default
The command is disabled, by default.
Modes
MPLS policy mode.
Usage Guidelines
The command may be dynamically turned on or off. Turning the command off or on has no effect on
LSPs that have already been established (primary and secondary). For LSPs that are currently retried,
changing the constraint setting changes the behavior on the next retry such as when an LSP whose
path is configured to use that interface fails to come up due to an interface down condition.
The command has significance for the ingress node only, where the CSPF calculation takes place for an
LSP or a detour segment.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the command.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# cspf-interface-constraint
cspf-group
Configures a CSPF fate-sharing group by assigning a name to the group.
Syntax
cspf-group group_name
no cspf-group
Command Default
The command is disabled by default.
Parameters
group_name
Specifies the name of the fate-sharing group. The group-name variable can be up to128
characters. The objects that can be specified for a fate-sharing group are interface, point-to-
point link, node, and subnet.
Modes
MPLS router mode
Usage Guidelines
The no form of the command disables the command.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example assigns the name group3 to the fate sharing group configuration.
device# configure
device(config)# router mpls
device(config-router-mpls)# cspf-group group3
cspf-group-computation
Use the cspf-group-computation mode when setting up a fate-sharing group.
Syntax
cspf-group-computation [ add-penalty | ignore-overload-bit | metric-type
[ use-igp-metric | use-te-metric ] | use-bypass-metric ]
no cspf-group-computation
Command Default
The CSPF group computation mode is disabled, by default.
Parameters
add-penalty
Adds penalty of all matching cspf-groups to TE metric of the TE link.
ignore-overload-bit
Ignores the overload bit during CSPF computaton.
metric-type
Selects the metric type for CSPF computation.
use-igp-metric
Uses the IGP metric of the link for CSPF computation.
use-te-metric
Uses the TE metric of the link for CSPF computation.
use-bypass-metric
Uses the bypass LSPs path cost for the selection between bypass LSPs
Modes
MPLS policy configuration mode (config-router-mpls-policy).
Usage Guidelines
The no form of the command disables the CSPF group computation mode.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example specifies the CSPF-group computation for a fate-sharing group, and enables the
add-penalty option.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# cspf-group-computation add-penalty
The following example enables the liberal mode of the bypass LSP selection.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# cspf-group-computation use-bypass-liberal
dampening
Sets dampening parameters for the route in BGP address-family mode.
Syntax
dampening { half-life reuse suppress max-suppress-time | route-map route-
map }
no dampening
Command Default
Disabled.
Parameters
half-life
Number of minutes after which the route penalty becomes half its value. Range is from 1 through
45. Default is 15.
reuse
Minimum penalty below which the route becomes usable again. Range is from 1 through 20000.
Default is 750.
suppress
Maximum penalty above which the route is suppressed by the device. Range is from 1 through
20000. Default is 2000.
max-suppress-time
Maximum number of minutes a route can be suppressed by the device. Range is from 1 through
255. Default is 40.
route-map
Enables selection of dampening values established in a route map by means of the route-map
command.
route-map
Name of the configured route map.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of this command to disable dampening.
Use dampening without operands to set default values for all dampening parameters.
To use the dampening values established in a route map, configure the route map first, and then enter
the route-map command, followed by the name of the configured route map.
A full range of dampening values (half-life, reuse, suppress, max-suppress-time) can also
be set by means of the set as-path prepend command.
Examples
The following example enables default dampening as an IPv4 address-family function.
The following example changes all the dampening values as an IPv6 address-family function.
database-overflow-interval (OSPFv2)
Configures frequency for monitoring database overflow.
Syntax
database-overflow-interval interval
no database-overflow-interval
Command Default
0 seconds. If the device enters OverflowState, you must reboot before the device leaves this state.
Parameters
interval
Time interval at which the device checks to see if the overflow condition has been eliminated.
Valid values range from 0 through 86400 seconds.
Modes
OSPF router configuration mode
Usage Guidelines
This command specifies how long a device that has entered the OverflowState waits before resuming
normal operation of external LSAs. However, if the external link state database (LSDB) is still full, the
device lapses back into OverflowState. If the configured value of the database overflow interval is zero,
then the device never leaves the database overflow condition.
When the maximum size of the LSDB is reached (this is a configurable value in the external-lsdb-limit
CLI), the device enters OverflowState. In this state, the device flushes all non-default AS-external-LSAs
that the device had originated. The devie also stops originating any non-default external LSAs. Non-
default external LSAs are still accepted if there is space in the database after flushing. If no space exists,
the Non-default external LSAs are dropped and not acknowledged.
Examples
The following example configures a database-overflow interval of 60 seconds.
database-overflow-interval (OSPFv3)
Configures frequency for monitoring database overflow.
Syntax
database-overflow-interval interval
no database-overflow-interval
Command Default
10 seconds. If the router enters OverflowState, you must reboot before the router leaves this state.
Parameters
interval
Time interval at which the device checks to see if the overflow condition has been eliminated.
Valid values range from 0 through 86400 seconds (24 hours).
Modes
OSPFv3 router configuration mode
Usage Guidelines
This command specifies how long after a router that has entered the OverflowState before it can
resume normal operation of external LSAs. However, if the external link state database (LSDB) is still full,
the router lapses back into OverflowState.
When the maximum size of the LSDB is reached (this is a configurable value in the external-lsdb-limit
CLI), the router enters OverflowState. In this state, the router flushes all non-default AS-external-LSAs
that the router had originated. The router also stops originating any non-default external LSAs. Non-
default external LSAs are still accepted if there is space in the database after flushing. If no space exists,
the Non-default external LSAs are dropped and not acknowledged.
Examples
The following example configures a database-overflow interval of 120 seconds.
Syntax
debug access-list-log buffer { circular | linear } packet-count count-
value
debug access-list-log buffer clear
no debug access-list-log buffer
Parameters
circular
Specifies circular buffer type.
linear
Specifies linear buffer type.
packet-count count-value
Specifies a value from 64 through 2056.
clear
Clears the buffer contents.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
Examples
The following example clears the buffer.
device# debug access-list-log buffer clear
Syntax
debug arp packet buffer all
no debug arp packet buffer all
debug arp packet buffer { circular | linear } packet-count num-packets
[ vrf vrf-name ]
debug arp packet buffer clear [ vrf vrf-name ]
debug arp packet buffer interface { ethernet slot / port | port-channel
number | ve ve-id } [ rx | tx ]
no debug arp packet buffer interface { ethernet slot / port | port-
channel number | ve ve-id } [ rx | tx ]
Parameters
all
Specifies all ARP-packet buffers.
circular
Specifies circular buffer type.
linear
Specifies linear buffer type.
packet-count num-packets
Specifies a value from 64 through 2056.
clear
Clears the buffer contents.
vrf vrf-name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
interface
Specifies an Ethernet or VE interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
port-channel number
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
If neither rx nor tx are specified, both transmitted and received packets are captures.
To disable ARP packet capture on a specified interface, use the no debug dhcp packet buffer
interface command.
To disable ARP packet capture on all interfaces, use the no debug dhcp packet buffer all
command.
Examples
The following command enables ARP packet capture for transmitting data on Ethernet interface 1/5.
device# debug arp packet buffer interface ethernet 1/5 tx
Syntax
debug dhcp packet buffer [all | circular packet count | clear vrf name |
interface ethernet/port-channel | linearpacket count]
Command Default
The buffer wraps around to overwrite earlier captures (circular).
Parameters
circular
Buffer wraps around to overwrite earlier captures.
linear
Buffer stops capture when the packet-count value is reached.
clear
Clears the packet buffer.
all
Captures DHCP packets on all interfaces.
interface
Represents a valid interface such as Ethernet or port channel.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
This command configures the capturing buffer behavior by allowing captures to wrap and overwrite
earlier captures or stop capturing when a packet-count limit is reached. The current buffer content is
cleared when the configuration changes.
Examples
The following example configures a buffer to capture 510 maximum packets in a circular fashion.
device# debug dhcp packet buffer circular packet-count 510
Syntax
debug dot1x packet { all | interface ethernet slot/port } [ detail ]
[ both | rx | tx ]
no debug dot1x packet { all | interface ethernet slot/port }
Parameters
all
Causes the display of information for all interfaces.
interface
Causes the display of information for a specific interface.
ethernet slot/port
Specifies an Ethernet interface in slot and port number format; when the device does not
contain slots, the slot number must be 0.
detail
Causes the display of detailed information.
both
Causes the display of information about received and transmitted packets. By default,
information about both received and transmitted packets is displayed.
rx
Causes the display of information about only received packets.
tx
Causes the display of information about only transmitted packets.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
The no form of the command disables the display of processing information related to IEEE 802.1X
port-based access control.
Examples
The following example shows how to display detailed processing information related to IEEE 802.1X
port-based access control for all interfaces.
device# debug dot1x packet all detail
The follow example shows how to disable the display of processing information related to IEEE 802.1X
port-based access control for port 0/1.
device# no debug dot1x packet interface ethernet 0/1
debug ip bgp
Displays information related to the processing of BGP4, with a variety of options.
Syntax
debug ip bgp { cli | dampening | events | general | graceful-restart |
ip-prefix ip-addr/mask-len | ip-prefix-list name | keepalives |
route-map name | route-selection | traces | updates [ rx | tx ] }
[ all-vrfs | vrf vrf-name ]
no debug ip bgp
Parameters
cli
Displays information about BGP CLI
dampening
Displays BGP4 dampening.
events
Displays all BGP4 events.
general
Displays BGP4 common events.
graceful-restart
Displays BGP graceful restart events.
ip-prefix
Displays information filtered by IP prefix.
ip-addr
IPv4 address in dotted-decimal notation.
mask-len
IPv4 mask length in CIDR notation.
ip-prefix-list
Displays information filtered by IP prefix list.
name
Name of IP prefix list.
keepalives
Displays BGP4 keepalives.
route-map
Displays configured route map tags.
name
Name of route map.
route-selection
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
If you want to see BGP4 keepalives for a specific neighbor, you must first specify the neighbor using the
debug ip bgp neighbor command. Only keepalive traces for the specified neighbor will appear in
the debugging message.
Examples
The following example sets debugging on BGP4 events.
The following example specifies that BGP4 keepalives for a specified neighbor appear in debugging
messages.
The following example sets debugging on BGP4 events for VRF instance "red".
Syntax
debug ip bgp neighbor ip-addr [ all-vrfs | vrf vrf-name ]
no debug ip bgp neighbor ip-addr [ all-vrfs | vrf vrf-name ]
Parameters
ip-addr
IPv4 address in dotted-decimal notation.
all-vrfs
Specifies all VRFs.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
Examples
The following example sets debugging on information related to the processing of BGP4 for a specific
neighbor.
The following example specifies that BGP4 keepalives for a specified neighbor appear in debugging
messages.
The following example sets debugging on information related to the processing of BGP4 for a specific
neighbor for VRF instance "red".
The following example sets debugging information related to the processing of BGP4 for a specific
neighbor for all VRFs.
debug ip igmp
Enables or disables debugging for IGMP information.
Syntax
debug ip igmp { all | errors | group A.B.C.D | packet | rx | tx |
interface ethernet | port-channel tunnel | vlan vlan_id | bridge-
domain bd_id }
no debug ip igmp
Parameters
all
Enables all debugs.
errors
Enables only error type debugs, such as memory allocation failures.
group A.B.C.D
Specifies the group address, as a subnet number in dotted decimal format (for example,
10.0.0.1), as the allowable range of addresses included in the multicast group.
packet
Enables debug for queries or reports per the chosen option.
rx
Specifies only ingressing flow debugs to be captured in traces.
tx
Specifies only egressing packet flows to be captured in traces.
interface
Specifies the interface (ethernet, port-channel, tunnel) to be monitored.
vlan
Specifies the VLAN to be monitored.
bridge-domain
Specifies the bridge domain to be monitored.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
When debugging is enabled, all of the IGMP packets received and sent and IGMP-host related events
are displayed.
Examples
The following example enables error debug flags.
device# debug ip igmp error
debug ip pim
Enables debugging for IP Protocol Independent Multicast.
Syntax
debug ip pim { add-del-oif | bootstrap | group | join-prune | nbr-change
| packets | parent | regproc | route-change | rp | source | state |
all }
no debug ip pim all
Command Default
All flags are disabled.
Parameters
add-del-oif
Controls the OIF change flag.
bootstrap
Controls the bootstrap processing flag.
group
Controls the processing for a group flag.
join-prune
Controls the Join/Prune processing flag.
nbr-change
Controls the neighbor changes flag.
packets
Controls the packet processing flag.
parent
Controls the parent change processing flag.
regproc
Controls the register processing flag.
route-change
Controls the route changes flag.
rp
Controls the Rendezvous Point (RP) processing flag.
source
Controls the processing for a source flag.
state
Controls the state processing flag.
all
Controls all of the states.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
Syntax
debug ipv6 bgp ipv6-prefix ipv6-address /mask [ all-vrfs | vrf vrf-name ]
debug ipv6 bgp ipv6-prefix name [ all-vrfs | vrf vrf-name ]
debug ipv6 bgp ipv6-prefix-list name [ all-vrfs | vrf vrf-name ]
no debug ipv6 bgp ipv6-prefix ipv6-address /mask [ all-vrfs | vrf vrf-
name ]
no debug ipv6 bgp ipv6-prefix name [ all-vrfs | vrf vrf-name ]
no debug ipv6 bgp ipv6-prefix-list name [ all-vrfs | vrf vrf-name ]
Parameters
ipv6-address /mask
Specifies an IPv6 address and network mask.
all-vrfs
Specifies all VRFs.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance
name
Specifies a prefix list name.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
Examples
This example enables debugging for IPv6 prefix list "myv6list" for VRF instance "red".
device# debug ipv6 bgp ipv6-prefix-list myv6list vrf red
This example enables debugging for a specified IPv6 address for all VRFs.
device# debug ipv6 bgp ipv6-prefix 2001::/16 all-vrfs
Syntax
debug ipv6 bgp neighbor ipv6-addr [ all-vrfs | vrf vrf-name ]
no debug ipv6 bgp neighbor ipv6-addr [ all-vrfs | vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor.
all-vrfs
Specifies all VRFs.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
Examples
The following example sets debugging for a neighbor.
device# debug ipv6 bgp neighbor 2000::1
The following example specifies that BGP keepalives for a specified neighbor appear in debugging
messages.
The following example sets debugging for a neighbor for VRF instance "red".
device# debug ipv6 bgp neighbor 2000::1 vrf red
The following example sets debugging for a neighbor for all VRFs.
device# debug ipv6 bgp neighbor 2000::1 all-vrfs
Syntax
debug ipv6 ospf graceful-restart {all-vrfs | vrf vrf-name }
no debug ipv6 ospf graceful-restart {all-vrfs | vrf vrf-name }
Parameters
all-vrfs
Specifies the IPv6 OSPFv3 debugs on all VRFs.
vrf vrf-name
Specifies the IPv6 OSPFv3 debugs on the indicated VRF.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
When this command is enabled, it begins logging debugs related to graceful restart.
Examples
This example enables debug logging for the VRF named "red."
device# debug ipv6 ospf graceful-restart vrf red
debug lacp
Enables or disables debugging for the Link Aggregation Control Protocol (LACP).
Syntax
debug lacp { all | cli | event | ha | pdu [ rx { all | interface ethernet
slot/port | tx { all | sync | timer | trace level number }
no debug lacp
Command Default
LACP debugging is disabled.
Parameters
all
Turns on all debugging.
cli
Turns on command line interface debugging.
event
Turns on event debugging.
ha
(Not currently supported) Echo HA events to the console.
pdu
Echo PDU content to the console.
rx all
Turns on debugging for received LACP packets on all interfaces.
rx interface
Turns on debugging for received LACP packets on the specified interface.
interface
Specifies the interface to be monitored.
ethernet
Represents a valid, physical Ethernet interface.
slot
Specifies a valid slot number. The only valid value is 0.
port
Specifies a valid port number.
tx all
Turns on debugging for transmitted LACP packets on all interfaces.
tx interface
Modes
Privileged EXEC mode
Usage Guidelines
Enter terminal monitor to display debugging outputs on a particular cmsh session.
Examples
To enable debugging of LACP PDUs for transmitted and received packets on all interfaces:
device# debug lacp pdu tx all
Syntax
debug lldp dump { all | [ ethernet slot/port ] [ both ] ] | [ detail
[ both | rx | tx ] }
Command Default
LLDP debugging is disabled.
Parameters
all
Dumps all information to the console.
ethernet
Represents a valid, physical Ethernet port.
slot
Specifies a valid slot number. The only valid value is 0.
port
Specifies a valid port number.
both
Turns on debugging for both transmit and receive packets.
detail
Turns on debugging with detailed information.
both
Turns on detailed debugging for both transmit and receive packets.
rx
Turns on detailed debugging for only received LLDP packets.
tx
Turns on detailed debugging for only transmitted LLDP packets.
Modes
Privileged EXEC mode
Syntax
debug lldp packet { all | [ ethernet slot/port ] [ both ] ] | [ detail
[ both | rx | tx ] }
no debug lldp packet { all | interface ethernet slot/port }
Command Default
LLDP debugging is disabled.
Parameters
all
Turns on LLDP packet debugging on all interfaces.
ethernet
Represents a valid, physical Ethernet port.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
both
Turns on debugging for both transmit and receive packets.
detail
Turns on debugging with detailed information.
both
Turns on detailed debugging for both transmit and receive packets.
rx
Turns on detailed debugging for only received LLDP packets.
tx
Turns on detailed debugging for only transmitted LLDP packets.
Modes
Privileged EXEC mode
Usage Guidelines
Enter terminal monitor to display debugging outputs on a particular cmsh session.
Examples
To enable debugging of LLDP for both received and transmitted packets on the 10-gigabit Ethernet
interface 0/1:
device# debug lldp packet interface ethernet 0/1 both
debug spanning-tree
Enables debugging for the Spanning Tree Protocol (STP).
Syntax
debug spanning-tree { all | bpdu [ rx | tx [ all | [ interface { ethernet
slot/port | port-channel number }
no debug spanning-tree { all | bpdu [ rx | tx [ all | [ interface
{ ethernet slot/port | port-channel number }
Command Default
STP debugging is disabled.
Parameters
all
Turns on spanning tree packet debugging on all interfaces.
bpdu
Turns on Bridge Protocol Data Unit debugging.
rx
Turns on debugging for only received spanning-tree packets.
tx
Turns on debugging for only transmitted spanning-tree packets.
interface
Specifies an interface.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
Examples
To enable debugging of spanning-tree for both Rx and Tx on Ethernet interface 0/1:
Syntax
debug udld packet { all | interface ethernet slot/port } { both | rx |
tx }
no debug udld packet
Command Default
UDLD debugging is disabled.
Parameters
all
Activates UDLD debugging on all ports on the switch.
ethernet
Represents a valid, physical Ethernet type for all available Ethernet speeds.
slot/port
Specifies a valid slot and port number. For devices that do not support linecards, specify 0 for
the slot.
both
Sets debugging for both received and transmitted packets.
rx
Sets debugging for received packets only.
tx
Sets debugging for transmitted packets only.
Modes
Privileged EXEC mode
Usage Guidelines
Diagnostic commands are developed and intended for specialized troubleshooting. Work closely with
Extreme Networks technical support when running debug or show system internal commands
and interpreting their results.
When debugging is enabled, UDLD PDUs are written to the console as they are transmitted and
received on one or all ports.
Use the show debug udld command to view your current debug settings.
Use the no form of this command to turn off either all dumping of UDLD PDUs or dumping on a specific
port.
Examples
To turn on debugging of transmitted packets on a specific ethernet interface:
default-information-originate (BGP)
Configures the device to originate and advertise a default BGP route.
Syntax
default-information-originate
no default-information-originate
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example originates and advertises a default BGP4 route.
The following example originates and advertises a default BGP4+ route for VRF "red".
default-information-originate (IS-IS)
Generates a default route into an Intermediate System-to-Intermediate System (IS-IS) routing domain.
Syntax
default-information-originate [ route-map name ]
no default-information-originate [ route-map name ]
Command Default
Disabled.
Parameters
route-map name
Specifies that the default route is generated if the route map is satisfied. The route map name
can be from 1 through 63 characters in length.
Modes
IS-IS address-family IPv4 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example generates a default external route into an IS-IS domain.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv4 unicast
device(config-router-isis-ipv4u)# default-information-originate
The following example generates a default external route into an IS-IS domain if the route map
“myroutemap” is satisfied.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv6 unicast
device(config-router-isis-ipv6u)# default-information-originate route-map myroutemap
default-information-originate (OSPFv2)
Controls distribution of default information to an OSPFv2 device.
Syntax
default-information-originate [ always ] [ metric metric ] [ metric-type
{ type1 | type2 } ] [ route-map name ]
no default-information-originate
Command Default
The default route is not advertised into the OSPFv2 domain.
Parameters
always
Always advertises the default route. If the route table manager does not have a default route, the
router advertises the route as pointing to itself.
metric metric
specifies the cost for reaching the rest of the world through this route. If you omit this parameter
and do not specify a value using the default-metric router configuration command, a
default metric value of 1 is used. Valid values range from 1 through 65535. The default is 10.
metric-type
Specifies how the cost of a neighbor metric is determined. The default is type1. However, this
default can be changed with the metric-type command.
type1
Type 1 external route.
type2
Type 1 external route,
route-map name
Specifies that the default route is generated if the route map is satisfied. This parameter
overrides other options. If the set metric and set metric-type commands are specified
in the route-map, the command-line values of metric and metric-type if specified, are “ignored”
for clarification.
Modes
OSPF router configuration mode
Usage Guidelines
This configuration provides criteria for the redistribution of any default routes found in the route table
manager (RTM),whether static or learned from another protocol, to its neighbors.
The corresponding route-map should be created before configuring the route-map option, along
with the default-information-originate command. If the corresponding route-map is not
created beforehand, an error message is displayed stating that the route-map must be created.
The route-map option cannot be used with a non-default address in the match conditions. The default
route LSA is not generated if a default route is not present in the routing table and a match ip
address condition for an existing non-default route is configured in the route-map. The match ip
address command in the route-map is a no-op operation for the default information originate
command.
Examples
The following example creates and advertises a default route with a metric of 30 and a type 1 external
route.
default-information-originate (OSPFv3)
Controls distribution of default information to an OSPFv3 device.
Syntax
default-information-originate [ always ] [ metric metric ] [ metric-type
{ type1 | type2 } ]
no default-information-originate
Command Default
The default route is not advertised into the OSPFv3 domain.
Parameters
always
Always advertises the default route. If the route table manager (RTM) does not have a default
route, the router advertises the route as pointing to itself.
metric metric
Used for generating the default route, this parameter specifies the cost for reaching the rest of
the world through this route. If you omit this parameter, the value of the default-metric
command is used for the route. Valid values range from 1 through 65535.
metric-type
Specifies the external link type associated with the default route advertised into the OSPF
routing domain.
type1
The metric of a neighbor is the cost between itself and the router plus the cost of using this
router for routing to the rest of the world.
The default is type1.
type2
The metric of a neighbor is the total cost from the redistributing routing to the rest of the world.
Modes
OSPFv3 router configuration mode
Usage Guidelines
This configuration provides criteria for the redistribution of any default routes found in the RTM
(whether static or learned from another protocol) to its neighbors.
Examples
The following example specifies a metric of 20 for the default route redistributed into the OSPFv3
routing domain and an external metric type of Type 2.
default-ipv6-gateway
Configures the IPv6 address of the default gateway on a VLAN.
Syntax
default-ipv6-gateway ipv6-address [metric ]
no default-ipv6-gateway
Parameters
ipv6-address
IPv6 address of the default gateway.
metric
A decimal value from 1 through 5.
Modes
VLAN configuration mode
Usage Guidelines
A device should have a default gateway, for the following reasons:
• Although IPv6 discovers neighbors and routes dynamically, in some cases Router Advertisement
(RA) and Router Solicitation (RS) operations are disabled and a default gateway is required to send
traffic. RA and RS are not suppressed if a default gateway is confifured.
• Management devices (for example, TFTP servers, Telnet or SSH clients) are not members of the
same subnet as the management IPv6 address.
If a management VLAN is not configured, the device can have only one IPv6 default gateway in the
global configuration.
If a management VLAN is configured, the device can have a maximum of 5 IPv6 default gateways, with
an optional metric (1 through 5), under the management VLAN. Multiple gateways can have the same
metric value.
Configured gateway addresses and the default gateway address must be in same subnet.
The best default gateway is first chosen as the device whose neighbors are reachable (in the REACH
state), in the sequence of metric values. Otherwise, the gateway with the highest priority (the lowest
metric value) is chosen.
If a static default gateway is configured, that gateway takes precedence over the best default gateway
configured by means of RA. If the static default-gateway configuration is removed, the best default
gateway learned by RA is restored.
Use the no form of the command to remove the IPv6 address and disable the default gateway.
Selection of the best default router among configured IPv6 routers occurs under the following
conditions:
• Disabling an interface
• Processing of an NA message receipt
• Adding or deleting an IPv6 neighbor to or from the neighbor list
• Configuring the IPv6 static default gateway by means of the CLI
The process of resolving the link layer for the IPv6 default gateway by sending NS occurs during the
following conditions:
• Configuration of the default gateway configured by means of the CLI
• Addition or deletion of a management VLAN configuration
Examples
The following example configures the maximum of 5 IPv6 default gateways with the management
VLAN configuration, and specifies metrics for each.
device# configure terminal
device(config)# vlan 66
device(config-vlan-66)# default-ipv6-gateway 2620:100:c:fe23:10:37:65:129 3
device(config-vlan-66)# default-ipv6-gateway 2620:100:c:fe23:10:37:65:129 2
device(config-vlan-66)# default-ipv6-gateway 2620:100:c:fe23:10:37:65:130 2
device(config-vlan-66)# default-ipv6-gateway 2620:100:c:fe23:10:37:65:131 1
device(config-vlan-66)# default-ipv6-gateway 2620:100:c:fe23:10:37:65:132 5
Use the show ipv6 command to confirm the configuration and view the best default gateway
(router).
device(config)# show ipv6
Global Settings
IPv6 is enabled
Link-local address(es):
fe80::768e:f8ff:fef9:6d80 [Preferred]
Global unicast address(es):
2620:100:c:fe23:768e:f8ff:fef9:6d80 [Preferred], subnet is 2620:100:c:fe23::/64
Joined group address(es):
ff02::1:fff9:6d80
ff02::1
Best Default Router : 2620:100:c:fe23:10:37:65:129 PMTUS : 0
MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 3
ND reachable time is 30000 miliseconds
ND retransmit interval is 1000 miliseconds
Current Hop Limit is 64
Hosts use stateless autoconfig for addresses
No Inbound Access List Set
No Outbound Access List Set
No IPv6 Domain Name Set
No IPv6 DNS Server Address set
default-link-metric
Configures the metric value globally on all active Intermediate System-to-Intermediate System (IS-IS)
interfaces for a specified address family.
Syntax
default-link-metric { level-1 | level-2 } value
no default-link-metric { level-1 | level-2 }
Command Default
Disabled.
Parameters
level-1
Specifies the default-link-metric parameter as Level 1.
level-2
Specifies the default-link-metric parameter as Level 2.
value
Specifies the default-link-metric value in metric style. The narrow metric range is from 1 through
63. The wide metric range is from 1 through 16777215. The default is 10.
Modes
IS-IS address-family IPv4 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
This command is useful when you have a common IS-IS metric value on all IS-IS interfaces (other than
the default metric value of 10). This command is not applicable to MPLS IS-IS shortcuts and tunnel
interfaces.
If you change the metric style configuration, the value of the default link metric also changes. The new
value of the default link metric is equal to the minimum of the configured value and the maximum value
supported by the new metric style. For example, if the metric style changes from wide metric to narrow
metric, and the default-link-metric value is greater than 63, the default-link-metric value changes to 63
because it is the maximum value supported in the narrow metric style. When the metric style changes
from a narrow metric to a wide metric, there is no change to the default-link-metric value.
You can change the metric value for a specific interface using the isis metric command or the
isis ipv6 metric command. The isis metric command configuration takes precedence over
the default-link metric value command configuration.
The no form of the command resets the metric value to the default value 10.
Examples
The following example configures the IS-IS default-link-metric value to 30 for Level 1 for the IPv4 unicast
address family.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv4 unicast
device(config-router-isis-ipv4u)# default-link-metric level-1 30
The following example configures the IS-IS default-link-metric value to 30 for Level 1, and the IS-IS
default-link-metric value to 40 for Level 2 for the IPv6 unicast address family.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family-ipv6 unicast
device(config-router-isis-ipv6u)# default-link-metric level-1 30
device(config-router-isis-ipv6u)# default-link-metric level-2 40
default-local-preference
Enables setting of a local preference value to indicate a degree of preference for a route relative to that
of other routes.
Syntax
default-local-preference num
no default-local-preference
Parameters
num
Local preference value. Range is from 0 through 65535. The default is 100.
Modes
BGP configuration mode
Usage Guidelines
Local preference indicates a degree of preference for a route relative to that of other routes. BGP4
neighbors can send the local preference value as an attribute of a route in an UPDATE message.
Examples
The following example sets the local preference value to 200.
default-metric (BGP)
Changes the default metric used for redistribution.
Syntax
default-metric value
no default-metric
Command Default
The default metric value is 1.
Parameters
value
Metric value. Range is from 0 through 4294967295.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example changes the default metric used for redistribution to 100.
default-metric (IS-IS)
Sets the default redistribution metric value for the Intermediate System-to-Intermediate System (IS-IS)
routing protocol.
Syntax
default-metric value
no default-metric
Command Default
The default metric value is 0.
Parameters
value
Specifies the default metric value. Valid values range from 0 through 65535. The default is 0.
Modes
IS-IS address-family IPv4 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command resets the default metric value to the default value of 0.
Examples
The following example sets the default metric value to 20 for the IPv4 unicast address family.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv4 unicast
device(config-router-isis-ipv4u)# default-metric 20
The following example sets the default metric value to 40 for the IPv6 unicast address family.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv6 unicast
device(config-router-isis-ipv6u)# default-metric 40
default-metric (OSPF)
Sets the default metric value for the OSPFv2 or OSPFv3 routing protocol.
Syntax
default-metric metric
no default-metric
Parameters
metric
OSPF routing protocol metric value. Valid values range from 1 through 65535. The default is 10.
Modes
OSPF router configuration mode
Usage Guidelines
This command overwrites any incompatible metrics that may exist when OSPFv2 or OSPFv3
redistributes routes. Therefore, setting the default metric ensures that neighbors use the correct cost
and router computation.
Examples
The following example sets the default metric to 20 for OSPF.
default-passive-interface
Marks all OSPFv2 and OSPFv3 interfaces passive by default.
Syntax
default-passive-interface
no default-passive-interface
Modes
OSPF router configuration mode
Usage Guidelines
When you configure the interfaces as passive, the interfaces drop all the OSPFv2 and OSPFv3 control
packets.
You can use the ip ospf active and ip ospf passive commands in interface subconfiguration
mode to change active/passive state on specific OSPFv2 interfaces. You can use the ipv6 ospf
active and ipv6 ospf passive commands in interface subconfiguration mode to change the
active and passive state on specific OSPFv3 interfaces.
Examples
The following example marks all OSPFv2 interfaces as passive.
delay
For an implementation of an event-handler profile, specifies a delay from when a trigger is received until
execution of the event-handler action.
Syntax
delay seconds
no delay
Command Default
There is no delay from when a trigger is received until execution of the event-handler action.
Parameters
seconds
Specifies the number of seconds from when a trigger is received until the execution of the
specified action begins. Valid values are 0 or a positive integer.
Modes
Event-handler activation mode
Usage Guidelines
The no form of this command resets the delay setting to the default 0 seconds.
Examples
The following example specifies a delay of 60 seconds.
device# configure terminal
device(config)# event-handler activate eventHandler1
device(config-activate-eventHandler1)# delay 60
delay-link-event
Configures the port transition hold timer to set a delay in the sending of port up or down port events, or
both, to Layer 2 protocols.
Syntax
delay-link-event multiple-iteration { down | up | both }
no delay-link-event
Command Default
The sending of an up or down port event is not delayed.
Parameters
multiple-iteration
Specifies the number of times that the polling iteration occurs. Enter an integer from 1 to 200.
The polling iteration is 50 ms. The delay time is the multiple-iteration times 50 ms.
both
Sets the delay for the port down and up events.
down
Sets the delay for the port down event.
up
Sets the delay for the port up event.
Modes
Interface Ethernet configuration mode.
Usage Guidelines
Use the no form of the command to remove the delay from the port events on the interface.
While link down events are reported immediately in the Syslog, their effect on higher level protocols
such as OSPF is delayed according to how the hold timer is configured. When configured, the timer
affects the physical link events. However, the resulting logical link events are also delayed.
Note
All LAG member ports must have the same delayed-link-event configuration.
Note
The delayed-link-event configuration is applicable only on a physical interface. It is not valid
on a VLAN, VE, LAG, or loopback interfaces.
Note
The port transition hold timer does not take effect when the interface is administratively shut
down.
Examples
The following example shows the steps in the previous configuration.
device# configure terminal
device(config)# interface ethernet 4/2
device(conf-if-eth-4/2)# delay-link-event 2 down
delete
Deletes a user-generated file from the flash memory.
Syntax
delete file
Parameters
file
The name of the file to be deleted.
Modes
Privileged EXEC mode
Usage Guidelines
The delete operation is final; there is no mechanism to restore the file.
System configuration files cannot be deleted. If you try to delete a system configuration file, an
appropriate message is displayed.
Examples
To delete a user-generated copy of a configuration file:
delete-packet
Configures the logging or monitoring interval for all Traffic Management (TM) deleted packets on the
SLX-OS device.
Syntax
delete-packet { logging-interval minutes } | { threshold deleted-
packets }
no delete-packet logging-interval | threshold
Command Default
The logging interval is 60 minutes.
Parameters
logging-interval minutes
Specifies the logging interval in minutes. Enter an integer from from 10 to 2880.
threshold deleted-packets
Specifies the threshold limit for all deleted packets of the TM device. Enter a value from 0 to
10000. The value of 0 disables the monitoring of the all TM deleted packets.
Modes
System monitor TM configuration mode
Usage Guidelines
Use the no version of this command to reset the default interval or threshold values.
A RASlog message for the TM device statistics is generated within the logging interval similar to the
following format:
M1 | Active, WARNING, SLX, TM threshold, Head deleted packets 34462
on device 3.1.1.
Examples
The following example configures the logging interval to 120 minutes.
device# configure terminal
device(config)# system-monitor tm
device(config-sys-mon-tm)# delete-packet logging-interval 120
deploy
Deploys the MCT cluster or cluster client.
Syntax
deploy
no deploy
Modes
Cluster configuration mode
Cluster client PW configuration mode ( SLX 9540 and SLX 9640 devices only)
Usage Guidelines
Before deploying a cluster, the cluster client must be configured.
Before deploying a cluster client, the client interface and ESI settings must be configured under the
client configuration.
The client will not operate in MCT mode unless the remote client is also deployed.
When the client is undeployed, all MAC addresses are removed locally and a withdraw message is sent
to the MCT peer to remove all associated client MAC addresses.
Examples
The following example shows the deployment of a cluster.
device(config)# cluster MCT1 1
device(config-cluster-1)# deploy
On the SLX 9540 and SLX 9640 devices, the following example shows the deployment of a PW cluster
client.
device(config)# cluster MCT1 1
device(config-cluster-1)# client-pw
device(config-cluster-client-pw)# deploy
description (BD)
Specify a string that contains the description for a bridge-domain or multiple bridge-domains.
Syntax
description [ description-string ]
no description [ description-string ]
Parameters
description-string
Specifies the description in a string format. The space character between the description
keyword and the description-string is allowed.
Modes
Global bridge-domain configuration mode.
Usage Guidelines
The no description of the command removes the description specified for a bridge-domain.
The show bridge-domain command displays an extra field in the output displaying the description
of the bridge-domain.
Examples
The following example shows how to specify a description for bridge-domain 10.
description (event-handler)
Defines a description for an event-handler profile.
Syntax
description description-text
no description
Command Default
No description is defined.
Parameters
description-text
Characters describing the event-handler profile. The string can be 1 through 128 ASCII characters
in length. Do not use the ? character. If you need to use ! or \, precede each with \.
Modes
Event-handler configuration mode
Usage Guidelines
An event-handler profile supports only one description.
To change a description, you do not need to first delete the existing description. Just create a new
description.
Examples
The following example defines a description for eventHandler1.
device# configure terminal
device(config)# event-handler eventHandler1
device(config-event-handler-eventHandler1)# description This is a sample description.
description (interfaces)
Specify a string that contains the description of a specified interface.
Syntax
description line
Parameters
line
Specifies characters describing the interface. The string must be between 1 and 63 ASCII
characters in length.
Modes
Interface subtype configuration mode
Examples
To set the string describing internal Ethernet interface 3/2:
description (LLDP)
Specifies a string that contains the LLDP description.
Syntax
description string
no description
Parameters
string
Characters describing LLDP. The string must be between 1 and 50 ASCII characters in length.
Modes
Protocol LLDP and profile configuration modes
Usage Guidelines
Enter no description to remove the LLDP description.
The LLDP description can also be configured for a specific LLDP profile. When you apply an LLDP
profile on an interface using the lldp profile command, it overrides the global configuration. If a
profile is not present, then the default global profile is used until you create a valid profile.
Examples
To set the strings describing LLDP:
To set the strings describing LLDP for a specific LLDP profile, test2, enter the following:
description (STP)
Describes an xSTP configuration.
Syntax
description description
no description
Parameters
description
Characters describing the xSTP configuration. The string must be between 1 and 64 ASCII
characters in length.
Modes
xSTP configuration mode
Usage Guidelines
Enter no description to remove the description.
Examples
To specify the bridge priority:
description (VRRP)
Describes a Virtual Router Redundancy Protocol extended (VRRP-E) interface.
Syntax
description description
no description
Parameters
description
Characters describing the VRRP-E interface. The string must be between 1 and 64 ASCII
characters in length.
Modes
Virtual-router-group configuration mode
Usage Guidelines
Enter no description to remove the description.
Examples
To describe the VRRP-E group 10 interface:
designated-forwarder-hold-time
Configures the time in seconds to wait before electing a designated forwarder.
Syntax
designated-forwarder-hold-time seconds
designated-forwarder-hold-time
Command Default
The default setting is three seconds.
Parameters
seconds
Specifies the hold time in seconds. Enter an integer from 1 to 60.
Modes
Cluster configuration mode
Usage Guidelines
Use the no form of the command to reset the default setting of three seconds.
The designated forwarder is a PE in a set of multi-homing PEs connected to the same Ethernet segment
that is responsible for sending BUM traffic to a client for a particular VLAN ID on an Ethernet segment.
DF election is not triggered unless at least one remote CCEP is configured. When a CCEP goes up or
down, DF election is triggered as soon as the Ethernet route acknowledgment from remote peer is
received.
When a client is deployed locally or remotely, or the BGP session comes up, the DF timer does not start
and DF election is not performed until the timer expired.
Examples
The following example configures a 20-second hold time for DF election.
device(config)# cluster MCT1 1
device(config-cluster-1)# designated-forwarder-hold-time 20
destination
Configures the destination address for the tunnel interface.
Syntax
destination ip-address
no destination ip-address
Command Default
No tunnel interface destination is configured.
Parameters
ip-address
Modes
Interface tunnel configuration mode
Usage Guidelines
Use the no tunnel destination command to remove the destination configuration.
You must ensure that a route to the tunnel destination exists on the tunnel source device and create a
static route if necessary.
Examples
This example configures the IP address 10.1.2.3 as the destination address.
Syntax
dhcp ztp cancel
Modes
Privileged EXEC mode
Usage Guidelines
By default, cancelling the ZTP session stops the session and stops all retry attempts, regardless of
whether the process succeeds or not. If the firmware download has completed successfully, the device
returns to Normal mode. The following limitations apply:
• If the firmware download has not started, you will need to reboot the switch manually to bring the
switch back to normal mode.
• If the firmware download has already started, you must wait for firmware download to complete
before running any other commands, power cycling the switch, starting a new firmware download,
or starting a new ZTP session.
• If the firmware download completes and the switch fails to reboot, you must reboot the switch
manually to bring the switch back to normal mode.
Examples
The following example cancels the ZTP retry.
device# dhcp ztp cancel
Warning: This command will terminate the existing ZTP session
Do you want to continue? [y/n] y
You can confirm that ZTP is canceled by running the dhcp ztp cancel command again. The output
confirms that ZTP is disabled.
device# dhcp ztp cancel
ZTP is not enabled.
Syntax
dhcp ztp log
Modes
Privileged EXEC mode
Usage Guidelines
The progress log displays if Zero Touch Provisioning is enabled.
Examples
The following example shows the ZTP progress log.
dir
Lists the contents of the device flash memory.
Syntax
dir
Modes
Privileged EXEC mode
Examples
The following example lists the contents of the flash memory.
device# dir
total 572
drwxr-xr-x 2 251 1011 4096 Jun 5 07:08 .
drwxr-xr-x 3 251 1011 4096 Mar 11 00:00 ..
-rw-r--r-- 1 root sys 410 Jun 3 00:56 defaultconfig.standalone
-rw-r--r-- 1 root sys 695 Jun 3 00:56 defaultconfig.cluster
-rw-r--r-- 1 root root 185650 Jun 5 09:38 startup-config
disable
Use the disable command to disable the dynamic bypass in MPLS router or on a MPLS Ethernet
interface without deleting the configurations of dynamic bypass configuration block.
Syntax
disable
no disable
Command Default
The default configuration is no disable.
Modes
MPLS router dynamic bypass configuration mode (config-router-mpls-dynamic-bypass).
Usage Guidelines
The command brings down and deletes all the existing dynamic bypasses in the system.
The no form of the command enables the dynamic bypass configuration on the MPLS interface.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example disables the dynamic bypass in the MPLS router.
device# configure
device(config)# router mpls
device(config-router-mpls)# dynamic-bypass
device(config-router-mpls-dynamic-bypass)# disable
The following example disables dynamic bypass on MPLS Ethernet interface 0/8 .
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if ethernet-0/8)# dynamic bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# disable
disable-adjacency-check
Disables Intermediate System-to-Intermediate System (IS-IS) IPv6 protocol-support consistency checks
that are performed prior to forming adjacencies on hello packets.
Syntax
disable-adjacency-check
no disable-adjacency-check
Command Default
Disabled.
Modes
IS-IS address-family IPv6 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command re-enables the IS-IS IPv6 protocol-support consistency checks.
Examples
The following example disables the IS-IS IPv6 protocol-support consistency checks.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv6 unicast
device(config-router-isis-ipv6u)# disable-adjacency-check
The following example re-enables the IS-IS IPv6 protocol-support consistency checks.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv6 unicast
device(config-router-isis-ipv6u)# no disable-adjacency-check
disable-incremental-spf-opt
Disables incremental full SPF optimizations for Intermediate System-to-Intermediate System (IS-IS).
Syntax
disable-incremental-spf-opt
no disable-incremental-spf-opt
Command Default
Disabled.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
If you disable the partial SPF optimizations using the disable-partial-spf-opt command, IS-IS
automatically disables the incremental SPF optimizations and always runs full SPF. However, if you
disable incremental SPF optimizations using this command, IS-IS does not disable partial optimizations.
The no form of the command restores incremental SPF optimizations for IS-IS.
Examples
The following example disables incremental SPF optimizations for IS-IS.
disable-inc-stct-spf-opt
Disables incremental shortcut LSP SPF optimization.
Syntax
disable-inc-stct-spf-opt
disable-inc-stct-spf-opt
Command Default
Disabled.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command restores incremental shortcut LSP SPF optimization.
Examples
The following example disables incremental shortcut LSP SPF optimization.
device# configure terminal
device(config)# router isis
device(config-isis-router)# disable-inc-stct-spf-opt
disable-partial-spf-opt
Disables partial SPF optimizations for Intermediate System-to-Intermediate System (IS-IS).
Syntax
disable-partial-spf-opt
no disable-partial-spf-opt
Command Default
Disabled.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
If you disable the partial SPF optimizations using this command, IS-IS automatically disables the
incremental SPF optimizations and always runs full SPF. However, if you disable incremental SPF
optimizations using the disable-incremental-spf-opt command, IS-IS does not disable partial
optimizations.
The no form of the command restores partial SPF optimizations for IS-IS.
Examples
The following example disables partial SPF optimizations for IS-IS.
device# configure terminal
device(config)# router isis
device(config-isis-router)# disable-partial-spf-opt
disallow-oar-ac
Allows multiple attachment circurit (AC) endpoints on a virtual router interface that is configured for a
VPLS instance.
Syntax
disallow-oar-ac
no disallow-oar-ac
Command Default
A bridge domain created for a Virtual Private LAN Service (VPLS) application is also known as a VPLS
instance. By default, multiple AC endpoints are allowed on a virtual router interface that is bound to a
VPLS instance.
Modes
Router interface configuration mode.
Usage Guidelines
This feature is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
When multiple AC endpoints are not required on a VPLS instance and to help with system scaling of
hardware resources, use this command to disallow multiple AC endpoints.
This command cannot be used when multiple AC endpoints already exist on the interface.
Examples
The following example shows how to bind a virtual router interface numbered 10 to a bridge domain
numbered 5 and to then disallow multiple AC endpoints on router interface 10.
device# configure terminal
device(config)# bridge-domain 5
device(config-bridge-domain-5)# router interface 10
device(config-router-interface-10)# disallow-oar-ac
discard-packet
Configures the logging or monitoring interval for all Traffic Management (TM) discarded packets on the
SLX-OS device.
Syntax
discard-packet { logging-interval minutes | threshold discarded-packets }
no discard-packet { logging-interval | threshold }
Command Default
The logging interval is 60 minutes.
Parameters
logging-interval minutes
Specifies the logging interval in minutes. Enter an integer from from 10 to 2880.
threshold discarded-packets
Specifies the threshold limit for all discarded packets of the TM device. Enter a value from 0 to
10000. The value of 0 disables the monitoring of the all TM device packets.
Modes
System monitor TM configuration mode
Usage Guidelines
Use the no version of this command to reset the default interval or threshold values.
A RASlog message for the TM device statistics is generated within the logging interval. The message
consists of the time stamp, the number of discarded packets, and ingress slot, tower and core, similar to
the following example:
device# show logging raslog reverse count 10
2017/01/05-10:56:58, [SYSD-1005], 788, M2 | Active | DCE, WARNING, SLX, TM threshold,
Tail discarded packets 20734462 on device 3.1.1.
Examples
The following example configures the logging interval to 120 minutes.
device# configure terminal
device(config)# system-monitor tm
device(config-sys-mon-tm)# discard-packet logging-interval 120
discard-voq-packet
Configures the logging interval or threshold for all Virtual Output Queue (VOQ) discarded packets.
Syntax
discard-voq-packet { logging-interval minutes | threshold discarded-
packets }
no discard-voq-packet { logging-interval | threshold }
Command Default
The logging interval is 60 minutes.
Parameters
logging-interval minutes
Specifies the logging interval in minutes. Enter an integer from from 10 to 2880.
threshold discarded-packets
Specifies the threshold limit for all VOQ discarded packets. Enter a value from 0 to 10000. The
value of 0 disables the monitoring of the all VOQ packets.
Modes
System monitor TM configuration mode
Usage Guidelines
Use the no version of this command to reset the default interval or threshold values.
A RASlog message for the TM VOQ statistics is generated within the logging interval. The message
consists of the time stamp, destination slot and port, priority, and ingress slot, tower and core, similar to
the following example.
device# show logging raslog reverse count 100 | inc SYSD-1003
2017/01/05-11:03:59, [SYSD-1003], 793, M2 | Active | DCE, WARNING, SLX, TM threshold
2017/01/05-11:00:34, Discarded packets 930587727, interface 3/2 prio 0 on device 3.1.0
The slot and port in the message determines the destination port that is congested at the ingress slot,
tower, and core.
Examples
The following example configures the logging interval to 120 minutes.
device# configure terminal
device(config)# system-monitor tm
device(config-sys-mon-tm)# discard-voq-packet logging-interval 120
distance (BGP)
Changes the default administrative distances for eBGP, iBGP, and local BGP.
Syntax
distance external-distance internal-distance local-distance
no distance
Parameters
external-distance
eBGP distance. Range is from 1 through 255.
internal-distance
iBGP distance. Range is from 1 through 255.
local-distance
Local BGP4 and BGP4+ distance. Range is from 1 through 255.
Modes
BGP configuration mode
Usage Guidelines
To select one route over another according to the source of the route information, the device can use
the administrative distances assigned to the sources. The administrative distance is a protocol-
independent metric that IP devices use to compare routes from different sources. Lower administrative
distances are preferred over higher ones.
Examples
The following example configures the device to change the administrative distance.
distance (IS-IS)
Configures an administrative distance value for Intermediate System-to-Intermediate System (IS-IS)
routes.
Syntax
distance number
no distance number
Command Default
The default is 115.
Parameters
value
Specifies the administrative distance. Valid values range from 1 through 255. The default is 115.
Modes
IS-IS address-family IPv4 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Routes with a distance value of 255 are not installed in the routing table.
The no form of the command resets the distance value to the default value of 115.
Examples
The following example sets an administrative distance of 40 for the IPv4 unicast address family.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv4 unicast
device(config-router-isis-ipv4u)# distance 40
The following example sets an administrative distance of 60 for the IPv6 unicast address family.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv6 unicast
device(config-router-isis-ipv6u)# distance 60
distance (OSPF)
Configures an administrative distance value for OSPFv2 and OSPFv3 routes.
Syntax
distance { external | inter-area | intra-area } distance
no distance
Command Default
The administrative distance value for OSPFv2 and OSPFv3 routes is 110.
Parameters
external
Sets the distance for routes learned by redistribution from other routing domains.
inter-area
Sets the distance for all routes from one area to another area.
intra-area
Sets the distance for all routes within an area.
distance
Administrative distance value assigned to OSPF routes. Valid values range from 1 through 255.
The default is 110.
Modes
OSPF router configuration mode
Usage Guidelines
You can configure a unique administrative distance for each type of OSPF route.
The distances you specify influence the choice of routes when the device has multiple routes from
different protocols for the same network. The device prefers the route with the lower administrative
distance. However, an OSPFv2 or OSPFv3 intra-area route is always preferred over an OSPFv2 or
OSPFv3 inter-area route, even if the intra-area route’s distance is greater than the inter-area route’s
distance.
Examples
The following example sets the distance value for all external routes to 125.
The following example sets the distance value for intra-area routes to 80.
The following example sets the distance value for inter-area routes to 90.
distribute
Enables advertisement of Border Gateway Protocol flow specification (BGP flowspec) rules that are
configured under a route map.
Syntax
distribute route-map-name
no distribute route-map-name
Command Default
The advertisement of BGP flowspec rules is disabled.
Parameters
route-map-name
Name of a route map that is configured with the flowspec rules to be advertised.
Modes
BGP address-family IPv4 flowspec configuration mode
Usage Guidelines
The no form of the command disables advertisement of BGP flowspec rules.
Examples
The following example shows how to enable advertisement of flowspec rules configured under a route
map named route_map_flowspec1 for the IPv4 address family.
Syntax
distribute-list prefix-list list-name in
no distribute-list prefix-list
Command Default
Prefix lists are not applied to OSPFv3 for IPv6 routing updates.
Parameters
list-name
Name of a prefix-list. The list defines which OSPFv3 networks are to be accepted in incoming
routing updates.
in
Applies the prefix list to incoming routing updates on the specified interface.
Modes
OSPFv3 router configuration mode
Usage Guidelines
The no form of the command removes the prefix list.
Examples
The following example configures a distribution list that applies the filterOspfRoutes prefix list globally:
distribute-list route-map
Creates a route-map distribution list.
Syntax
distribute-list route-map map in
no distribute-list route-map
Parameters
map
Specifies a route map.
in
Creates a distribution list for an inbound route map.
Modes
OSPF router configuration mode
Usage Guidelines
The distribution list can filter Link State Advertisements (LSAs) received from other OSPF devices
before adding the corresponding routes to the routing table.
Examples
The following example creates a distribution list using a route map named filter1 that has already been
configured.
domain-name
Creates a maintenance domain at a specified level and name and enters the maintenance domain mode
specified in the command argument.
Syntax
domain-name name level level
no domain-name name level level
Command Default
There is no domain configured.
Parameters
name
Specifies the domain name.
level level
Sets the domain level.
Modes
CFM protocol configuration mode
Usage Guidelines
The name parameter is case sensitive. The level parameter sets the domain level in the range 0 - 7.
When the domain already exists, the level argument is optional. Typically, the levels are:
• Customer’s Domain Levels: 5 - 7
• Provider Domain Levels: 3 - 4
• Operator Domain Levels: 0 – 2
The no form of the command removes the specified domain from the CFM protocol configuration
mode.
Examples
device# configure terminal
device(config)# protocol cfm
device(config-cfm)# domain-name md1 level 4
device(config-cfm-md-md1)#
dot1ag-compliance
Enables IEEE 802.1ag (Dot1ag) compliance configuration mode to configure left and right interfaces, by
associating MD name, MA name, MEP ID, and RMEP ID per interface for both ERP left and right
interfaces for signal failure and recovery. This allows MDs, MAs, and MEPs to be configured as part of
Dot1ag and to be associated with an Ethernet Ring Protection (ERP) instance to achieve faster
convergence.
Syntax
dot1ag-compliance
no dot1ag-compliance
Command Default
IEEE 802.1ag compliance is not configured by default.
Modes
ERP configuration mode
Usage Guidelines
IEEE 802.1ag can be used to monitor ERP interfaces for signal failures. This command uses Dot1ag link
status as a signal failure/recovery indication following a link status change on ERP ring interfaces,
linking Dot1ag MEP status to ERP switching functionality.
Examples
The following example uses the erp command to enter Dot1ag compliance configuration mode. In this
mode the user configures MD name, MA name, MEP ID, and RMEP ID per interface for both ERP left and
right interfaces.
device# configure terminal
Entering configuration mode terminal
device(config-erp-2)# dot1ag-compliance
device(config-dot1ag-compliance)# left-interface domain-name md1 ma-name ma4 mep 2 remote-
mep 1
device(config-dot1ag-compliance)# right-interface domain-name md1 ma-name ma3 mep 1
remote-mep 2
dot1x authentication
Enables 802.1x authentication on a port.
Syntax
dot1x authentication
no dot1x authentication
Command Default
802.1x authentication is disabled for ports.
Modes
Interface configuration mode
Usage Guidelines
Port control must be configured to activate authentication on an 802.1x-enabled interface using the
dot1x port-control auto command from interface configuration mode.
Before activating the authentication using the dot1x port-control auto command on a port, you
must remove configured static ACLs and static VLANs, if any, from the port.
Enter the no dot1x authentication command to disable dot1x on the port and remove the
configuration from 802.1x management.
Examples
The following example enables 802.1x authentication on a specific port:
device# configure terminal
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x authentication
dot1x enable
Enables 802.1X authentication globally.
Syntax
dot1x enable
Command Default
802.1x authentication is not enabled.
Modes
Global configuration mode
Usage Guidelines
The dot1x enable command enables 802.1x authentication globally on all ports.
Note
802.1x port authentication is not supported by LAG (Link Aggregation Group) or interfaces
that participate in a LAG.
Examples
The following example enables 802.1X authentication globally on all interfaces.
dot1x filter-strict-security
Enables or disables strict filter security for dot1x authentication on the interface.
Syntax
dot1x filter-strict-security
no dot1x filter-strict-security
Command Default
Strict filter security is enabled.
Modes
Interface configuration mode
Usage Guidelines
By default, strict security mode is enabled; that is the client is not authenticated if the Filter-Id attribute
returned by RADIUS contains invalid information, or if insufficient system resources are available to
implement the IP ACLs or MAC address filters.
Examples
The following example enables strict filter security.
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x filter-strict-security
dot1x max-req
Configures the retransmission parameter that defines the maximum number of times EAP request/
challenge frames are retransmitted when EAP response/identity frame is not received from the client.
Syntax
dot1x max-req count
no dot1x max-req count
Command Default
The device retransmits the EAP-request/challenge twice.
Parameters
count
Specifies the number of EAP frame re-transmissions. Th range is from from 1 through 10. The
default value is 2.
Modes
Interface configuration mode
Usage Guidelines
The no form of the command disables this functionality.
Examples
The following example configures the device to retransmit an EAP-request/challenge frame to a client a
maximum of three times.
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x max-req 3
dot1x port-control
Controls port-state authorization and configures the port control type to activate authentication on an
802.1X-enabled interface.
Syntax
dot1x port-control { auto | force-authorized | force-unauthorized }
no dot1x port-control { auto | force-authorized | force-unauthorized }
Command Default
The default port state is auto.
Parameters
auto
Enables authentication on a port. It places the controlled port in the unauthorized state until
authentication takes place between the client and authentication server. Once the client passes
authentication, the port becomes authorized. This activates authentication on an 802.1X-enabled
interface. The controlled port remains in the authorized state until the Client logs off.
force-authorized
Places the controlled port unconditionally in the authorized state, allowing all traffic to pass
between the client and the authenticator. This also allows connection from multiple clients.
force-unauthorized
Places the controlled port unconditionally in the unauthorized state, denying any traffic to pass
between the client and the authenticator.
Modes
Interface subtype configuration mode
Usage Guidelines
Before activating the authentication using the dot1x port-control auto command on a port, you
must remove the configured static ACL and static VLANs, if any, from the port.
802.1x port authentication is not supported by LAG (Link Aggregation Group) or interfaces that
participate in a LAG.
The no form of the command resets the port control type to the default state.
Examples
The following example configures the interface to place the port unconditionally in the unauthorized
state until authentication takes place between the client and authentication server. Once the client
passes authentication, the port becomes authorized.
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x port-control auto
The following example configures the interface to place the controlled port unconditionally in the
authorized state.
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x port-control force-authorized
The following example configures the interface to place the controlled port unconditionally in the
unauthorized state.
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x port-control force-unauthorized
dot1x quiet-period
Configures the time interval that the device remains idle between a failed authentication and a
reauthentication attempt.
Syntax
dot1x quiet-period seconds
no dot1x quiet-period
Command Default
The default quiet period is 60 seconds.
Parameters
seconds
Specifies the time between failed reauthentication and reauthentication attempt. Valid values
range from 1 through 65535 seconds.
Modes
Interface configuration mode
Usage Guidelines
Changing the quiet-period interval time to a number lower than the default can result in a faster
response time.
Examples
The following example sets the idle time as 200 seconds for the device before attempting
reauthentication after an authentication failure.
dot1x reauthenticate
Initiates 802.1X reauthentication on a specified interface.
Syntax
dot1x reauthenticate interface ethernet slot/port
Parameters
interface ethernet slot/port
Specifies a physical inteface ethernet port in terms of slot number and port nummber.
Modes
Privileged EXEC mode
Examples
The following example initiates reauthentication of a client connected to physical interface 1/1:
dot1x reauthentication
Configures the device to periodically reauthenticate the clients connected to 802.1X-enabled interfaces
at regular intervals.
Syntax
dot1x reauthentication
no dot1x reauthentication
Command Default
Periodic reauthentication is disabled.
Modes
Interface configuration mode
Usage Guidelines
When periodic reauthentication is enabled using the dot1x reauthentication command, the
device reauthenticates the clients every 3,600 seconds by default.
The reauthentication interval is configurable using the dot1x timeout re-authperiod command.
The reauthentication interval configured using the dot1x timeout re-authperiod command
takes precedence.
Examples
The following example enables 802.1x reauthentication.
device# configure terminal
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x reauthentication
dot1x reauthMax
Sets the maximum number of times that a port attempts 802.1x reauthentication before the port
changes to the unauthorized state.
Syntax
dot1x reauthMax number
no dot1x reauthMax
Command Default
The number of times that a port attempts 802.1x authentication is 2.
Parameters
number
Specifies the maximum number of reauthentication attempts before the port goes to the
unauthorized state. Valid values range from 1 through 10.
Modes
Interface configuration mode
Usage Guidelines
The no dot1x reauthMax command restores the default setting.
Examples
The following example sets the maximum number of reauthentication attempts to 5.
device# configure terminal
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x reauthMax 5
Syntax
dot1x test eapol-capable interface ethernet slot/port
Parameters
interface ethernet slot/port
Specifies a physical inteface ethernet port in terms of slot number and port nummber.
Modes
Privileged EXEC mode
Usage Guidelines
This command monitors 802.1x activity on all the switch ports and displays information about the
devices connected to the ports that support 802.1x. You can use this feature to determine if the devices
connected to the switch ports are 802.1x-capable. When you configure the dot1x test eapol-
capable command on an 802.1x-enabled port, and the link comes up, the port queries the connected
client about its 802.1x capability. When the client responds with a notification packet, it is designated as
802.1x-capable.
The readiness check can be sent on a port that handles multiple hosts (for example, a PC that is
connected to an IP phone). The readiness check is not available on a port that is configured with the
command dot1x port-control force-unauthorized .
The readiness check is typically used before 802.1x is enabled on the switch.
802.1x authentication cannot be initiated while the 802.1x readiness test is in progress.
The 802.1x readiness test cannot be initiated while 802.1x authentication is active.
802.1x readiness can be checked on a per-interface basis. Readiness check for all interfaces at once is
not supported.
Examples
The following example configures readiness check on an interface to determine if the devices connected
to the ports are 802.1x-capable.
Syntax
dot1x test timeout timeout
Command Default
The default readiness test interval is 10 seconds.
Parameters
timeout
Specifies the readiness test interval value in seconds. Valid values range from 1 through 65535.
Modes
Global configuration mode
Examples
The following example sets the test timeout to 30 seconds:
dot1x timeout
Configures the timeout parameters that determine the time interval for client reauthentication and EAP
retransmissions.
Syntax
dot1x timeout {re-authperiod seconds | supp-timeout seconds | tx-period
seconds }
no dot1x timeout {re-authperiod seconds | supp-timeout seconds | tx-
period seconds }
Command Default
The timeout parameters are not applied to the device.
Parameters
re-authperiod seconds
Specifies the interval at which clients connected to 802.1X authentication enabled ports are
periodically reauthenticated. When periodic reauthentication is enabled using the dot1x
reauthentication command, the device reauthenticates the clients every 3,600 seconds by
default. The re-authperiod option allows you to specify the time interval between
reauthentication attempts. The reauthentication interval configured using the dot1x timeout
re-authperiod command takes precedence.
supp-timeout seconds
Specifies the EAP response timeout for 802.1x authentication. By default, when the device relays
an EAP-Request frame from the RADIUS server to the client, it expects to receive a response
from the client within 30 seconds. If the client does not respond within the allotted time, the
device retransmits the EAP-Request frame to the client. The timeout value for retransmission of
EAP-Request frames to the client can be configured using the supp-timeout seconds
parameters.
tx-period seconds
Specifies the EAP request retransmission interval, in seconds, with the client. By default, if the
device does not receive an EAP-response/identity frame from a client, the device waits 30
seconds, then retransmits the EAP-request/identity frame. You can optionally change the
amount of time the device waits before re-transmitting the EAP-request/identity frame to the
client. If the client does not send back an EAP-response/identity frame within 60 seconds, the
device will transmit another EAP-request/identity frame. The tx-period is a value from 1 through
4294967295. The default is 30 seconds.
Modes
Interface configuration mode
Usage Guidelines
The no form of the command disables dot1x timeout.
Examples
The following example sets 25 seconds as the amount of time between reauthorization attempts on a
specific interface.
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x timeout re-authperiod 25
The following example sets 45 seconds as the switch-to-client retransmission time for the EAP request
frame on a specific interface.
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x timeout supp-timeout 45
The following example sets 34 seconds as the waiting period for a response to an EAP-request or
identity frame from the client before retransmitting the request on a specific interface.
device(config)# interface Ethernet 1/1
device(conf-if-eth-1/1)# dot1x timeout tx-period 34
dpod
Manages Dynamic Ports on Demand (POD) assignments.
Syntax
dpod slot/port { reserve | release }
Parameters
slot
Specifies a slot number.
port
Specifies a port number.
reserve
Reserves a POD assignment for a port that is currently not able to come online but is expected
to be viable in the future. A port license assignment that is reserved will be associated with the
first port set that has a vacancy.
release
Removes a port from the port set to which it is currently assigned.
Modes
Global configuration mode
Usage Guidelines
A port POD assignment can only be released if the port is currently offline. Enter shutdown to take the
port offline.
Do not release a port unless you plan to disconnect the optical link or disable the port persistently. If the
link (server or optical) is left in a state where the port could be brought online, the Dynamic POD
mechanism will detect this unassigned port and attempt to reassign it to a port set.
Examples
The following example reserves a POD assignment.
device(config-dpod-8/15)# exit
dscp (QoS)
Defines the DSCP-to-EXP values for an MPLS QoS DSCP-to-EXP mutation map.
Syntax
dscp dscp-value to exp exp-value ]
no dscp dscp-value
Command Default
The default DSCP value.
Parameters
dscp-value
Specifies the DSCP value.
exp exp-value
Specifies the EXP value.
Modes
DSCP-EXP configuration mode
Usage Guidelines
Use the no form of the command to reset the DSCP value.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example defines the DSCP-to-EXP mutation map.
device# configure terminal
device(config)# qos-mpls map dscp-exp dscpExpMap
device(dscp-exp-dscpExpMap)# dscp 0 to exp 7
dscp (Tunnel)
Configures the tunnel differentiated services code point (DSCP).
Syntax
dscp dscp-value
no dscp
Parameters
dscp-value
Specifies the DSCP value. The range is from 0 to 63.
Command Default
The default value is 0.
Modes
Interface tunnel configuration mode
Usage Guidelines
Use the no form of this command to remove the DSCP configuration.
Examples
This example configures DSCP value for the tunnel interface.
device# configure terminal
device(config)# interface tunnel 5
device(config-intf-tunnel-5)# mode gre ip
device(config-intf-tunnel-5)# source 10.1.1.10
device(config-intf-tunnel-5)# source ve 4
device(config-intf-tunnel-5)# destination 10.1.1.11
device(config-intf-tunnel-5)# router-interface ve 3
device(config-intf-tunnel-5)# dscp-ttl-mode pipe
device(config-intf-tunnel-5)# dscp 10
dscp-ttl-mode
Configures tunnel differentiated services code point (DSCP) time to live (TTL) mode.
Syntax
dscp-ttl-mode { pipe | uniform }
no dscp-ttl-mode
Command Default
By default, set to pipe mode for all tunnels.
Parameters
pipe
Specifies pipe mode.
uniform
Specifies uniform mode.
Modes
Interface tunnel configuration mode
Usage Guidelines
Use the no form of this command to remove the QoS mode configuration.
Examples
This example shows how to configure the quality of service (QoS) mode.
device# configure terminal
device(config)# interface tunnel 5
device(config-intf-tunnel-5)# mode gre ip
device(config-intf-tunnel-5)# source 10.1.1.10
device(config-intf-tunnel-5)# source ve 4
device(config-intf-tunnel-5)# destination 10.1.1.11
device(config-intf-tunnel-5)# router-interface ve 3
device(config-intf-tunnel-5)# dscp-ttl-mode pipe
Syntax
duplicate-mac-timer interval max-count interval
no duplicate-mac-timer interval max-count interval
Parameters
interval
Specifies the duplicate MAC detection timer interval in seconds. Valid values range from 5
through 300. The default is 5.
max-count value
Specifies the maximum threshold of MAC moves that can occur within the configured time
interval before the MAC address is treated as a duplicate address and further advertisements for
that MAC address are blocked. Valid values range from 3 through 10. The default is 3.
Modes
EVPN instance configuration mode
Usage Guidelines
The no form of the command restores the default values.
Examples
The following example sets the duplicate MAC detection timer interval to 180 and the maximum count
to 5 for the default EVPN instance.
The following example restores the default duplicate MAC detection timer and maximum count values.
dynamic-bypass
The dynamic-bypass command enables dynamic bypass on a MPLS router or on an Ethernet
interface.
Syntax
dynamic-bypass
no dynamic-bypass
Command Default
There is no dynamic bypass configuration in the default mode.
Modes
MPLS router configuration mode (config-router-mpls).
Usage Guidelines
Dynamic bypass is enabled or disabled in the MPLS router using this command. Upon configuring this
command, the configuration mode changes to dynamic bypass and enables dynamic bypass. If the
dynamic bypass is already configured under router MPLS, then there is no change in the configured
state of dynamic bypass.
Use the dynamic-bypass command to manually enable dynamic bypass on a MPLS interface.
The no form of the command in the MPLS router mode removes dynamic bypass from the MPLS router,
and dynamic bypass is disabled in the system. The command deletes all configurations under the router
mode dynamic bypass configuration block. This command brings down and deletes all the existing
dynamic bypasses in the system.
The no form of the command in the interface mode deletes the dynamic bypass configuration from the
MPLS interface and disables dynamic bypass on the interface when the MPLS router mode enable-
all-interfaces is not configured.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables dynamic bypass.
device>configure
device(config)# router-mpls
device(config-router-mpls)# dynamic-bypass
device(config-router-mpls-dynamic-bypass)#
enable
Enables the bypass LSP.
Syntax
enable
no enable
Command Default
The default value is disabled.
Modes
MPLS router bypass LSP configuration mode
Usage Guidelines
Enable the bypass LSP only after configuring the to-address and exclude-interface.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables the bypass LSP with the name my-bypass-lsp.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# bypass-lsp my-bypass-lsp
device(config-router-mpls-bypass-lsp-my-bypass-lsp)# enable
enable (ERP)
Activates an Ethernet Ring Protection (ERP) instance by accepting the configurations and initializing
protocol state machines.
Syntax
enable
no enable
Command Default
An ERP instance is not enabled by default.
Modes
ERP configuration mode
Usage Guidelines
Within an interconnected ring topology, in the major ring, you must first configure two interfaces. In a
sub-ring, you must configure at least one interface before enabling the ERP instance.
Note
You must enable the major ring before enabling any sub-rings attached to the major ring
(whose ERP ID is configured as parent-ring-id). Conversely, this order must be followed in
reverse to disable an ERP instance.
Examples
The following example configures a non-RPL node in a major ring.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# right-interface vlan 2 e 1/2
device(config-erp-1)# left-interface vlan 2 e 1/1
device(config-erp-1)# enable
enable (GRUB)
Enables securing the GRUB bootloader with a password on the SLX device.
Syntax
enable
no enable
Command Default
By default, GRUB is not secured with a password. This command is used to explicitly enable this feature.
Once enabled, the username command becomes available for configuring the username and
password to secure GRUB.
Note
Reboot is required for this feature to take effect.
Modes
GRUB mode
Usage Guidelines
The enable command is executed to enable securing the GRUB with a username and password
combination. When enabled, this username and password combination is applicable to the ONIE and
Offline Diagnostics options of the GRUB menu and and GRUB environment “e” - edit the commands
before booting and “c” - command-line. It is not applicable to the SLX-OS option of the GRUB menu.
You can launch the SLX-OS without providing credentials.
When enabled, the password protection feature get enabled from the next reboot of the SLX device.
The no form of the command disables GRUB Password Protection. This is also applicable from the next
reboot of the SLX device.
Examples
The following example enables the GRUB Password Protection.
SLX (config-grub)# enable
SLX (config-grub)#
GRUB Password Protection is enabled from the next reboot of the SLX device.
enable (management-heartbeat)
Enables Management Heartbeat mode on the SLX device.
Syntax
enable
no enable
Command Default
By default, Management Heartbeat mode is disabled. This command is used to explicitly enable this
mode.
Modes
Management Heartbeat mode
Usage Guidelines
The enable command must only be executed after setting the desired threshold and action for the
Management Heartbeat mode. This command can be executed immediately if you want to retain the
default values for threshold and action for this mode. When this command is executed, the SLX device's
Admin state becomes UP.
The no form of the command disables Management Heartbeat mode. However, the mode is not
removed from the running-config.
Examples
The following example enables the Management Heartbeat mode.
SLX(config-management-heartbeat-manage) # enable
SLX(config-management-heartbeat-manage)# do show running-config management-heartbeat
manager
management-heartbeat manager
enable
threshold-timer 1
action no-action
SLX(config-management-heartbeat-manage) #
SLX(config-management-heartbeat-manage) # no enable
SLX(config-management-heartbeat-manage)# do show running-config management-heartbeat
manager
management-heartbeat manager
threshold-timer 1
action no-action
SLX(config-management-heartbeat-manage) #
encryption-level
Configures the encryption level to use for communication with the Remote Authentication Dial-In User
Service (RADIUS) server.
Syntax
encryption-level encryption_level_value
no encryption-level
Command Default
The default value is 7; the key is stored in encrypted format.
Parameters
encryption_level_value
Specifies the encryption level value for shared-secret key operation. Valid values are 0 and 7. A
value of 0 sprecifies that the key is stored in cleartext format. A value of 7 specifies that the key
is stored in encrypted format. The default value is 7.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the command default value.
Note
Before downgrading to a software version that does not support the encryption-level
command, set the encryption level value to 0. Otherwise, the firmware download displays an
error requesting that the encryption level value be set to 0.
Examples
The following example shows how to specify an encryption level of 0; the shared secret key is stored in
cleartext format
enable-all-interfaces
Use the enable-all-interfaces command to enable dynamic bypass on all the MPLS interfaces. This
command disables dynamic bypass on all interfaces where dynamic bypass is not disabled using the
interface level commands. MPLS interface specific dynamic bypass configurations take precedence over
this configuration.
Syntax
enable-all-interfaces
no enable-all-interfaces
Command Default
Disabled on all interfaces unless the user enables dynamic bypass on the MPLS interfaces.
Modes
MPLS router dynamic bypass configuration mode (config-router-mpls-dynamic-bypass).
Usage Guidelines
The no form of the command disables dynamic bypass on all interfaces where dynamic bypass is not
enabled using the interface level commands.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables dynamic bypass on all interfaces.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# dynamic-bypass
device(config-router-mpls-dynamic-bypass)# enable-all-interfaces
enforce-first-as
Enforces the use of the first autonomous system (AS) path for external BGP (eBGP) routes.
Syntax
enforce-first-as
no enforce-first-as
Command Default
The device does not require the first AS listed in the AS_SEQUENCE field of an AS path update
message from eBGP neighbors be the AS of the neighbor that sent the update.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command disables this feature.
This command causes the router to discard updates received from eBGP peers that do not list their AS
number as the first AS path segment in the AS_PATH attribute of the incoming route.
The device accepts the update only if the AS numbers match. If the AS numbers do not match, the
device sends a notification message to the neighbor and closes the session. This requirement applies to
all updates received from eBGP neighbors.
Examples
The following example configures the device to enforce the use of the first AS path.
eol
Enables the end-of-lib configuration mode.
Syntax
eol
no eol
Modes
MPLS LDP configuration mode
Usage Guidelines
Use the no form of this command to remove this mode and attribute under it.
The end-of-lib mode contains all the attributes of the end of lib capability and notification. Also, when
you enable the end-of-lib mode, you can determine whether the two RFCs 5561 and 5919 are enabled
by the LSR.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables the end-of-lib configuration mode.
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# eol
device(config-router-mpls-ldp-eol)#
erp
Asigns an an Ethernet Ring Protection (ERP) ID and creates an ERP instance.
Syntax
erp erp_id
no erp erp_id
Command Default
An ERP instance is not configured by default.
Parameters
erp_id
Specifies an ERP instance. Range is from 1 through 255.
Modes
Global configuration mode
Usage Guidelines
You must assign an ERP ID. This ID number is used to do the following:
• Filter and clear statistics associated with a particular ERP ID
• Delete the nonrevertive mode in the case of an RPL owner
• Clear WTR and WTB timers
Examples
The following example specifies ERP instance 1 and enters ERP configuration mode.
device# configure terminal
device(config)# erp 1
device(config-erp-1)#
error-disable-timeout enable
Enables the timer to bring the interface out of the error-disabled state.
Syntax
error-disable-timeout enable
Modes
Spanning tree configuration mode
Usage Guidelines
When the Spanning Tree Protocol (STP) Bridge Protocol Data Unit (BPDU) guard disables a port, the
port remains in the disabled state unless the port is enabled manually. This command allows you to
enable the interface from the disabled state.
Examples
To bring the interface out of the disabled state:
error-disable-timeout interval
Sets the timeout interval for errors on an interface.
Syntax
error-disable-timeout interval seconds
no error-disable-timeout interval
Command Default
300 seconds
Parameters
seconds
Specifies the time for the interface to time out. Valid values range from 10 through 1000000
seconds.
Modes
Spanning tree configuration mode
Usage Guidelines
Enter no error-disable-timeout interval to return to the default setting.
Examples
Follow these examples to set the timeout interval.
esi
Sets the Ethernet Segment ID (ESI) value, which is used to uniquely identify the client for the MCT
client, or configures an auto-generated ESI value for a port channel client interface running LACP.
Syntax
esi {HH:HH:HH:HH:HH:HH:HH:HH:HH | auto lacp }
no esi
Parameters
HH:HH:HH:HH:HH:HH:HH:HH:HH
Specifies the 9-octect ESI value. Enter HH in hexadecimal format.
auto lacp
Configures an auto-generated ESI value for a port channel client interface running LACP.
Modes
Cluster client configuration mode
Cluster client PW configuration mode ( SLX 9540 and SLX 9640 devices only)
Usage Guidelines
Use the no form of the command to delete the ESI setting for the client.
You must configure the same ESI value on both devices in an MCT cluster.
For an MCT client, the configuration of the ESI value creates the MCT client LAG.
The esi auto lacp command is available only in cluster client configuration mode. When a client
interface is a port channel and LACP is running on the port channel, MCT supports an automatically-
generated ESI value, as defined in RFC 7432. This ESI is encoded as type 1, as follows:
• 1-byte ESI type = 1
• 9-byte ESI value = 6-byte LACP system MAC address of the client followed by the 2-byte LACP port
key, and then a 1-byte 0x00
Examples
The following example shows the setting of the ESI value for the cluster client.
device(config)# cluster MCT1 1
device(config-cluster-1)# client MCT1-client 200
device(config-cluster-client-200)# esi 00.a1.b2.c3.d4.e5.f6.89.00
The following example shows the configuration of an auto-generated ESI for the cluster client.
device(config)# cluster MCT1 1
device(config-cluster-1)# client MCT1-client 200
device(config-cluster-client-200)# esi auto lacp
On the SLX 9540 and SLX 9640 devices, the following example shows the setting of the ESI for the
cluster PW client.
device(config)# cluster MCT1 1
device(config-cluster-1)# client-pw
device(config-cluster-client-pw)# esi 01:02:03:04:05:06:07:08:0a
Syntax
esi es-id
[no] esi es-id
Parameters
es-id
The 10 digit ESI value. Manually assigned ESI values must be in Hexadecimal and should always
start with 0x00.
Modes
Ethernet Segment mode within Ethernet and Port-channel interface modes.
Usage Guidelines
Ethernet Segment Identifier is a 10-octet identifier value that denotes an Ethernet Segment. It is used to
discover and group the various interfaces of a multi-homed client.
The [no] format of the command removes the Ethernet Segment Identifier value mapped to ethernet
segment of the selected interface.
Examples
The following example shows the configuration of a leaf node with connections to two different multi-
homed hosts.
SLX(config)# interface Ethernet 0/1
SLX(conf-if-eth-0/1)#ethernet-segment
SLX(conf-if-eth-0/1-es)# esi 00:11:22:33:44:55:66:77:88:99
SLX(config)# interface Port-channel 1
SLX(config-Port-channel-1)# ethernet-segment
SLX(config-Port-channel-1-es)# esi 00:11:11:22:22:33:33:44:44:55
ethernet-segment
When a host device connects to multiple leaf nodes in a fabric through its interfaces, the aggregation of
these links is termed as an Ethernet Segment (ES). Each host is assigned an unique 10-octet Ethernet
Segment Identifier (ESI) that identifies this aggregation of connected ports. The assigned ESI value is
used to discover other leaf nodes within the same ESI. This command navigates into a new
configuration mode within which all ES configuration must be done.
ESI values are not assigned to single homed nodes.
Syntax
ethernet-segment
[no] ethernet-segment
Modes
Ethernet and Port-Channel modes. Navigates into the Ethernet Segment configuration mode.
Usage Guidelines
The command indicates that the current interface is a part of an Ethernet Segment and an Ethernet
Segment Identifier (ESI) value must be assigned to it.
The [no] function removes the current interface from the ES.
Examples
The following example creates the Ethernet-Segment for configuring and generating the Ethernet
Segment Identifier (ESI) value for a multi-homed client. In this example, two different interfaces are
configured. For each interface, the Ethernet Segment mode is enabled.
SLX(config)# interface Ethernet 0/1
SLX(conf-if-eth-0/1)#ethernet-segment
SLX(conf-if-eth-0/1-es)#
SLX(config)# interface Port-channel 1
SLX(config-Port-channel-1)# ethernet-segment
SLX(config-Port-channel-1-es)#
event
Configures an event and action.
Syntax
event{ average-threshold | max-threshold | ccm-down | ccm-up } actions
{ interface-down | event-handler | all }
no event
Parameters
average-threshold
Specifies average thereshold.
max-threshold
Specifies maximum thereshold.
ccm-down
Specifies CCM is down
ccm-up
Specifies CCM is up.
actions
Specifies the actions.
interface-down
Specifies interface down.
event-handler
Specifies event handler.
all
Specifies all.
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command delete the corresponding configured action profile also
corresponding associations with Source and Target MEP pair.
Examples
This example shows how to create an action profile.
device# configure terminal
device(config)# protocol cfm
device(config-cfm)# y1731
event-handler
Creates or accesses an event-handler profile, which can execute a Python script when a specified
trigger occurs.
Syntax
event-handler event-handler-name [ action python-script file-name ]
event-handler event-handler-name [ description description-text ]
event-handler event-handler-name [ trigger trigger-id raslog raslog-id
[ pattern posix-ext-regex ] ]
no event-handler event-handler-name
Command Default
No event-handler profile is enabled.
Parameters
event-handler-name
Specifies the name of the event-handler profile. Valid values can have from 1 through 32
characters. The first character must be alphabetic.
action python-script file-name
Specifies a Python file that runs when a trigger-condition occurs. Valid values range from 4
through 32 characters (including the .py extension). The first character must be alphanumeric.
description description-text
Specifies a string describing the event-handler profile. The string can be 1 through 128 ASCII
characters in length. Do not use the ? character. If you need to use ! or \, precede each with \.
trigger trigger-id
Defines an event-handler trigger and specifies an ID number for the trigger. Valid values are 1
through 100, and must be unique per event-handler profile. When the trigger-condition occurs, a
Python script is run.
raslog raslog-id
Specifies a RASlog message ID as the trigger.
pattern posix-ext-regex
Specifies a POSIX extended regular expression to search for a match within the specified RASlog
message ID. For examples, refer to the "trigger" topic.
Modes
Global configuration mode
Event-handler configuration mode for an existing event handler. (There is no need to enter the exit
command to return to global configuration mode.)
Usage Guidelines
You can create multiple event-handler profiles.
You can optionally specify a description, a trigger, or the Python script with this command; or specify
them later.
An event-handler command creates or accesses an event-handler profile and can also define one of
the following parameters:
• Description
• One trigger
• The Python-script action that runs on any trigger
You can also define the above parameters—including one or more triggers—from event-handler
configuration mode.
If an event-handler profile is not activated, the no form of this command deletes it.
Examples
The following example creates an event-handler profile and accesses its configuration mode.
device# configure terminal
device(config)# event-handler eventHandler1
device(config-event-handler-eventHandler1)#
Syntax
event-handler abort action event-handler-name
Parameters
event-handler-name
Specifies the name of the event-handler profile.
Modes
Privileged EXEC mode
Examples
The following command successfully aborted event-handler action "eh1".
device# event-handler abort action eh1
This operation will abort an event handler action that is currently running and may leave
the switch in an inconsistent state. Do you want to continue? [y/n]:y
Operation completed successfully.
event-handler activate
Activates an event handler and accesses event-handler activation mode, from which you can enter
advanced configuration commands. You can also append the advanced commands to event-
handler activate.
Syntax
event-handler activate event-handler-name
event-handler activate event-handler-name [ action-timeout minutes ]
[ delay seconds ] [ iterations num-iterations ] [ interval seconds ]
[ trigger-mode mode ] [ trigger-function { OR | AND [ time-window
seconds ] } ]
no event-handler activate event-handler-name
Command Default
No event handler is activated on the device.
Parameters
event-handler-name
Specifies the name of the event-handler profile.
action-timeout minutes
Specifies the number of minutes to wait for an action-script to complete execution. If you specify
"0", no timeout is set. Valid timeout values are any positive integer.
delay seconds
Specifies a number of seconds from when a trigger is received until the execution of the
specified action begins. Valid values are 0 or a positive integer.
iterations num-iterations
Specifies the number of times an event-handler action is run, when triggered. Valid values are
any positive integer. The default value is 1.
interval seconds
Specifies the number of seconds between iterations of an event-handler action, if triggered.
Valid values are 0 or a positive integer. The default is 0.
trigger-mode mode
Specifies if an event-handler action can be triggered only once or more than once. The default is
each time the trigger condition occurs, the event-handler action is launched.
each-instance
The event-handler action is launched on each trigger instance received.
on-first-instance
As long as the device is running, the event-handler action is launched only once. Following a
device restart, the event-handler action can be triggered again.
only-once
For the duration of a device's configuration, the event-handler action is launched only once.
trigger-function
For an implementation of an event-handler profile, if multiple triggers are defined for an event-
handler action, specifies if the action runs only if all of the triggers occur; or if one is sufficient.
OR
The event-handler action runs if any of the triggers occur.
AND
The event-handler action runs only if all of the triggers occur.
time-window seconds
In seconds, specify the time window within which all of the triggers must occur in order that the
event-handler action runs. Once all triggers have been received and on each subsequent trigger
received, the action will be launched when the time difference between the latest trigger and the
oldest trigger is less than or equal to the configured time-window.
Modes
Global configuration mode
Event-handler activation mode for an existing event handler. (There is no need to enter the exit
command.)
Usage Guidelines
You can activate up to 10 different event-handler profiles on a device.
Following an initial triggering of an event-handler action, any subsequent trigger launches the action an
additional time if the following conditions are true:
• The trigger-mode parameter is set to the default each-instance.
• The subsequent trigger occurs within the specified time-window.
For additional usage guidelines regarding the advanced configuration commands, see the following
topics:
• action-timeout
• delay
• iterations
• interval
• trigger-mode
• trigger-function
To inactivate an event-handler instance on a device, use the no form of this command. If an event-
handler Python script is running, it is executed to completion before inactivation of the event handler.
Examples
This example activates eventHandler1 on the device.
device# configure terminal
device(config)# event-handler activate eventHandler1
device(config-activate-eventHandler1)#
evpn
Creates an EVPN instance and enables EVPN instance configuration mode.
Syntax
evpn [ name ]
no evpn { default |name }
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to remove the EVPN instance.
When you enter the evpn command without a name, a default EVPN instance is created.
Examples
The following example configures the default EVPN instance.
device# configure terminal
device(config)# evpn
device(config-evpn-default)#
exclude-any
Interfaces that are not part of these groups, as well as interfaces that are not part of any group, are
eliminated from consideration.
Syntax
exclude-any admin_group_name | admin_group_name [admin_group_name |
admin_group_name ]
no exclude-any admin_group_name | admin_group_name [admin_group_name |
admin_group_name ]
Command Default
There are no excluded interfaces in the command default mode.
Parameters
name
Specifies the group, by name, the interface must be a member of. The name can be the name of
the administrative group to which an administrative group number is associated by configuration
in router MPLS mode. More than one parameter can be provided.
number
Specifies the group, by number, the interface must be a member of. Number can be from 0 to 31
representing 32 admin groups. More than one parameter can be provided.
Modes
MPLS LSP configuration mode (config-router-mpls lsp-lsp_name)
Usage Guidelines
More than one group may be configured at a time.
Use the interface level exclude-any command to configure administrative groups for dynamic
bypass LSPs to be created corresponding to a protected link.
The no form of the command removes the interface administrative group configuration.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example eliminates interfaces in either administrative group gold or silver when the
path for LSP tunnel1 is calculated.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp tunnel1
device(config-router-mpls-lsp-tunnel1)# exclude-any gold silver
The following example eliminates groups 10 and 11 from consideration for dynamic bypass MPLS
Ethernet interface 0/8.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# exclude-any 10 11
exclude-interface
Configures one or more exclude interfaces for the bypass LSP.
Syntax
exclude-interface { [ ethernet slot/port | port-channel number | ve ve-
num ] }
no exclude-interface { [ ethernet slot/port | port-channel number | ve
ve_num ] }
Command Default
There is no default value. This is a mandatory parameter.
Parameters
ethernet slot/port
Specifies the physical slot and port on the Ethernet interface.
port-channel number
Specifies a port-channel interface.
ve ve_num
Specifies the Virtual Ethernet (VE) number on the VE interface.
Modes
MPLS router Bypass LSP configuration mode.
Usage Guidelines
The no form of this command removes an exclude interface of the bypass LSP.
The user can configure one or more exclude interfaces for the bypass LSP. The interface can be an
Ethernet or a virtual Ethernet type. To enable a bypass LSP, the system requires at least one exclude
interface configuration.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example excludes Ethernet interface2/8 on bypass LSP my-bypass-lsp.
device# configure
device(config)# router mpls
device(config-router-mpls)# bypass-lsp my-bypass-lsp
device(config-router-mpls-bypass-lsp-my-bypass-lsp)# exclude-interface Ethernet 0/8
exp
Defines the QoS MPLS EXP-to-DSCP or EXP-to-traffic class mutation mapping.
Syntax
exp exp-value to { dscp dscp-value } | { traffic class traffic-class-
value drop-precedence }
no exp exp-value
Command Default
The default EXP-to-DSCP mapping is as follows:
Exp : 0 1 2 3 4 5 6 7
--------- --------------------------------
Dscp : 0 8 16 24 32 40 48 56
The default EXP-to-traffic class mapping with the drop precedence is as follows:
Exp : 0 1 2 3 4 5 6 7
---------------- -------------------------
traffic-class : 0 1 2 3 4 5 6 7
drop-precedence : 0 0 0 0 0 0 0 0
Parameters
exp-value
Specifies the EXP value. Enter an integer from 0 through 7.
dscp dscp-value
Specifies the DSCP value. Enter an integer from 0 through 63.
traffic class traffic-class-value
Specifies the traffic class value. Enter an integer from 0 through 7.
drop-precedence
Specifies the drop precedence for the traffic class. Enter an integer from 0 through 3.
Modes
QoS MPLS map EXP-DSCP and EXP-traffic-class configuration mode
Usage Guidelines
After configuring the mutation mapping, you can apply the map globally.
Examples
The following example is an MPLS QoS EXP-to-DSCP mutation map configuration.
device# configure terminal
device(config)# qos-mpls map exp-dscp expDscpMap
device(exp-dscp-expDscpMap)# exp 0 to dscp 7
device(exp-dscp-expDscpMap)# exp 1 to dscp 23
device(exp-dscp-expDscpMap)# exp 3 to dscp 31
The following example is an MPLS QoS EXP-to-traffic class mutation map configuration.
device# configure terminal
device(config)# qos-mpls map exp-traffic-class expTcMap
device(exp-traffic-class-expTcMap)# exp 0 to traffic-class 7 drop-precedence 0
export-vrf-leaked-routes
Allows exporting VRF leaked routes to Layer VPN.
Syntax
export-vrf-leaked-routes
no export-vrf-leaked-routes
Modes
BGP address-family IPv4 unicast VRF configuration mode
Usage Guidelines
The no form of the command disables exporting VRF leaked routes to Layer VPN.
Examples
This example shows how to export VRF leaked routes to Layer VPN.
device# configure terminal
device(config)# router bgp
device(config-bgp)# address-family vpnv4 unicast
device(config-bgp-vpnv4u)# export-vrf-leaked-routes
export-map
Exports the target-VPN community.
Syntax
export-map route-map
no export-map route-map
Parameters
route-map
Specifies the route-map name.
Modes
VRF configuration mode
Usage Guidelines
The no form of the command to apply a route-map filter on the routes to be exported.
Examples
The following example shows how to export the target-VPN community.
device# configure terminal
device(config)# vrf vpn1
device#(config-vrf-vpn1)# rd 1:2
device#(config-vrf-vpn1)# vpn-statistics
device#(config-vrf-vpn1)# address-familin ipv4 unicast
device#(config-vrf-vpn1-ipv4-unicast)# route-target-import 100:1
device#(config-vrf-vpn1-ipv4-unicast)# export-map import-route-map1
extend bridge-domain
Configures a bridge domain (BD) to a site for a VXLAN Layer 2 gateway.
Syntax
extend bridge-domain { add | remove } bridge_domain_id
Parameters
add
Adds a bridge-domain ID to a tunnel.
remove
Removes a bridge-domain ID from a tunnel.
bridge_domain_id
Specifies the configured bridge domain ID.
Modes
Site configuration mode
Examples
The following example configures the bridge domain to the site of the VXLAN Layer 2 gateway.
device# configure terminal
device(config)# overlay-gateway gateway1
device(config-overlay-gw-gateway1)# site mysite
device(config-overlay-gw-gateway1-site-mysite)# extend bridge-domain add 10
extend vlan
Configures switchport VLANs for the tunnels to the containing site in VXLAN overlay gateway
configurations.
Syntax
extend vlan { add | remove } vlan_id
no extend vlan
Parameters
add
Specifies a VLAN ID or range of VLAN IDs to be added to a tunnel.
remove
Specifies a VLAN ID or range of VLAN IDs to be removed from a tunnel.
vlan_id
A VLAN ID or range of VLAN IDs. See the Usage Guidelines.
Modes
VXLAN overlay gateway site configuration mode
Usage Guidelines
The VXLAN Network Identifier (VNI) classification is derived from the "map vlan" configuration of the
parent overlay gateway. This command results in the provisioning or unprovisioning of the VLANs. Use
the no extend vlan vlan_id command to unprovision a VLAN.
All of the VLAN IDs that are specified must be VLANs that have been mapped by means of the map
vlan vlan_id vni vni command on the parent overlay gateway, unless automatic VNI mapping has
been enabled by means of the map vlan vni auto command.
Use the no attach vlan vlan_id command to remove all switchport configurations from the
tunnels to the containing site.
Examples
To configure a switchport VLAN and range of VLANs:
device# configure terminal
device(config)# overlay-gateway gateway1
device(config-overlay-gw-gateway1)# site mysite
device(config-overlay-gw-gateway1-site-mysite)# extend vlan add 10,20-30
external-lsdb-limit (OSPFv2)
Configures the maximum size of the external link state database (LSDB).
Syntax
external-lsdb-limit value
no external-lsdb-limit
Parameters
value
Maximum size of the external LSDB. Valid values range from 1 through 14913080. The default is
14913080.
Modes
OSPF router configuration mode
Usage Guidelines
If you change the value, make sure to save the running-config file and reload the software. The change
does not take effect until you reload or reboot the software.
Examples
The following example sets the limit of the LSDB to 20000.
external-lsdb-limit (OSPFv3)
Configures the maximum size of the external link state database (LSDB).
Syntax
external-lsdb-limit value
no external-lsdb-limit
Parameters
value
Maximum size of the external LSDB. Valid values range from 1 through 250000. The default is
250000.
Modes
OSPFv3 router configuration mode
Usage Guidelines
If you change the value, you must save the running-config file and reload the software. The change does
not take effect until you reload or reboot the software.
Examples
The following example sets the limit of the external LSDB to 15000.
facility-backup
Enables facility backup (many-to-one) Fast Reroute (FRR) on a Label Switched Path (LSP).
Syntax
facility-backup [ bandwidth | exclude-any name | hop-limit name |
include-all | include-any | link-protection | priority | revertive ]
no facility-backup [ bandwidth | exclude-any name | hop-limit name |
include-all | include-any | link-protection | priority | revertive ]
Command Default
By default, a FRR LSP is a one-to-one (detour) protection LSP with the desired node protection.
Parameters
bandwidth
Specifies the bandwidth for the detour or backup LSP.
exclude-any name
Excludes any of the specified administrative groups.
hop-limit num
Specifies the limit of hops the detour or backup LSP can traverse.
include-all
Specifies to include all of the administrative groups.
include-any
Specifies to include any of the administrative groups.
link-protection
Requests link protection for the LSP.
priority
Requests setup and hold priorities.
revertive
Activates FRR revertiveness.
Modes
MPLS router LSP FRR configuration mode.
Usage Guidelines
When enabled at every Point of Local Repair (PLR), the LSP outgoing interface is expected to be
protected by a bypass LSP. The user can create bypass LSPs manually or they can be created
automatically using dynamic bypass.
The no form of the command sets the FRR LSP to the detour (one-to-one) mode.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables facility backup on LSP named my-fbkup-lsp.
device# kconfigure
device(config)# router mpls
device(config-router-mpls)#lsp my-fbkup-lsp
device(config-router-mpls-lsp-my-fbkup-lsp)# frr
device(config-router-mpls-lsp-my-fbkup-lsp-frr)# facility-backup
fast-convergence
Enables fast convergence of devices in the Ethernet Ring Protection (ERP) ring.
Syntax
fast-convergence
no fast-convergence
Command Default
Fast convergence is disabled by default.
Modes
ERP configuration mode
Usage Guidelines
A convergence time of less than 50-msec can be achieved with 4-device ring topology on 1-RU devices.
If the number of nodes in the topology increases, a small linear increase in convergence time occurs
accordingly.
Examples
The following example enables fast convergence in the ERP instance 1.
device# configure terminal
device(config)# erp 1
device(config-erp-1) fast-convergence
fast-external-fallover
Resets the session if a link to an eBGP peer goes down.
Syntax
fast-external-fallover
no fast-external-fallover
Modes
BGP configuration mode
Usage Guidelines
Use this command to terminate and reset external BGP sessions of a directly adjacent peer if the link to
the peer goes down, without waiting for the timer, set by the BGP timers command, to expire. This
can improve BGP conversion time, but can also lead to instability in the BGP routing table as a result of
a flapping interface.
Examples
The following example configures the device to reset the session if a link to an eBGP peer goes down.
fast-flood
Configures Intermediate System-to-Intermediate System (IS-IS) to flood Link State PDUs to other
devices in the network before running SPF.
Syntax
fast-flood lsp-count
no fast-flood sp-count
Command Default
Four LSPs are flooded before running SPF.
Parameters
lsp-count
Specifies the number of LSPs that must be flooded before running SPF. Valid values range from 1
through 15. The default value is 4.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command resets the LSP count to the default value of 4.
Examples
The following example configures IS-IS to flood 10 LSPs before running SPF.
device# configure terminal
device(config)# router isis
device(config-isis-router)# fast-flood 10
fastboot
Reboots the device without a power-on self-test (POST).
Syntax
fastboot
Modes
Privileged EXEC mode
Usage Guidelines
All reboot operations are disruptive, and the commands prompt for confirmation before executing.
When you reboot a device, all traffic to and from it stops. All ports on that device remain inactive until
the device comes back online.
Examples
The following example shows the use of the fastboot command.
device# fastboot
fast-wtr-time
Sets the Wait to Restore (WTR) time for Ethernet Ring Protection (ERP) from minutes to seconds.
Syntax
fast-wtr-time
no fast-wtr-time
Command Default
The WTR value is in minutes by default.
Modes
ERP configuration mode
Usage Guidelines
Use the no form of this command to restore the WTR value to minutes.
Examples
The following example configures a WTR time value to seconds.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# fast-wtr-time
fec mode
Configures the various Forward Error Corrections (FEC) parameters for the interface.
Syntax
fec mode { FC-FEC | RS-FEC | auto-negotiation | disable }
no fec mode
Command Default
By default, SLX-OS selects one of FC-FEC, RS-FEC or disable based on port type, configured
speed, and the optic inserted in that port.
Parameters
FC-FEC
Set the FEC mode to FC-FEC in manual mode.
RS-FEC
Set the FEC mode to use RS-FEC in manual mode.
auto-negotiation
Set the FEC mode to auto-negotiation. This setting is only applicable for 25G DAC cables.
disable
Disable FEC on the interface.
Modes
Interface Ethernet mode
Usage Guidelines
The no format of this command resets the FEC configuration on the interface to the default
configuration.
Examples
The following example configures the ethernet port 0/1 with RS-FEC.
SLX # config terminal
SLX (config)# interface Ethernet 0/1
SLX (conf-if-eth-0/1)# fec mode RS-FEC
fec (telemetry)
Indicates the MPLS FEC address to be used for the mpls-traffic-fec profile.
Syntax
fec fec-address
no fec fec-address
Parameters
fec-address
Specifies the address of the target FEC for the profile.
Modes
Telemetry profile configuration mode
Usage Guidelines
The fec-address variable must be unique.
The no form of the command deletes the FEC address from the profile.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example selects 20.10.3.4 as the FEC address for the profile.
filter-change-update-delay
Configures the delay period before application of a change to a Border Gateway Protocol flow
specification (BGP flowspec) route-map rule.
Syntax
filter-change-update-delay delay
no filter-change-update-delay
Command Default
By default, changes to BGP flowspec route-map rules are applied after a delay of 10 seconds.
Parameters
delay
Delay period (in seconds) before changes to BGP flowspec route-map rules are applied.
Modes
Global configuration mode
Usage Guidelines
The no from of the command restores the default configuration.
Examples
The following example shows how to set (to 500 seconds) the delay period for application of changes
to BGP flowspec route-map rules.
device# configure terminal
device(config)# filter-change-update-delay 500
filter-fec-in
Configures LDP inbound or outbound FEC filtering to filter inbound label bindings on a MPLS router.
Syntax
filter-fec-in prefix-list-name
no filter-fec-in prefix-list-name
Command Default
By default, LDP distributes all FECs that are learned locally or from LDP neighbors to all other LDP
neighbors.
Parameters
prefix-list-name
Specifies the prefix-list name.
Modes
MPLS LDP configuration mode
Usage Guidelines
Use the no form of this command to remove the FEC filtering configuration.
LDP inbound-FEC filtering allows the control the amount of memory and CPU processing involved in
installing and advertising label bindings not used for forwarding. It also serves as a tool to avoid DOS
attack. For inbound FEC filter, consider the following:
• The FECs filtered by the LDP inbound-FEC filter do not install in the forwarding plane or advertise to
the upstream neighbors. The FEC remains in the retained state.
• The LDP inbound-FEC filter are changed directly without deleting the one previously configured.
The change automatically applies and triggers the filtering of inbound FECs.
• Changes to a referenced prefix-list automatically applies to LDP inbound-FEC filtering. This triggers
filtering by way of the new configuration, filtering any existing FECs which violate the filter.
• To allow multiple route filter updates, the device waits for default 10 seconds before notifying the
application of the filter change. The time for notification is configurable.
• When the LDP inbound-FEC filter is not configured, LDP does not filter any inbound FECs.
• By default, when the prefix-list referenced by the LDP inbound-FEC filter has no configuration, it is
an implicit deny. All inbound FECs are filtered out and retained. The behavior is the same when the
prefix list is deleted after setting it in the inbound FEC filter configuration. This behavior is consistent
with other protocols which use device filters and also with the use of the advertise-fec
command for LDP route injection.
• Inbound FEC filtering is applicable only for Layer 3 FECs and not for VC FECs. Inbound FEC filtering
is not applicable for Layer 2 VPNs.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the LDP inbound-FEC filter.
device# configure terminal
device(config)# ip prefix-list list-abc permit 10.20.20.0/24
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# filter-fec-in list-abc
filter-fec-out
Configures LDP outbound FEC filtering to filter outbound label bindings on a MPLS router.
Syntax
filter-fec-out prefix-list-name
no filter-fec-out prefix-list-name
Command Default
By default, LDP distributes all FECs that are learned locally or from LDP neighbors to all other LDP
neighbors.
Parameters
prefix-list-name
Specifies the prefix-list name.
Modes
MPLS LDP configuration mode
Usage Guidelines
Use the no form of this command to remove the FEC filtering configuration.
LDP outbound FEC filtering gives you the ability to control which FECs can be advertised and to which
LDP neighbors. It also reduces the number of labels distributed to neighbors and the number of
messages exchanged with peers. Through this filtering, LDP scalability and convergence, security, and
performance are improved.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the LDP outbound-FEC filter.
device# configure terminal
device(config)# ip prefix-list list-out deny 10.40.40.0/24
device(config)# ip prefix-list list-out permit 0.0.0.0/0 ge 32
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# filter-fec-out list-out
firmware activate
Activates the firmware that was downloaded with firmware download noactivate command.
Syntax
firmware activate
Command Default
Activation of the firmware is performed manually by default after a download.
Modes
Privileged EXEC mode
Usage Guidelines
By default, the firmware download command downloads the firmware to the system, reboots the
system, and commits the firmware automatically. You can specify the noactivate parameter to
download the firmware to the system without activating it (the node is not rebooted). The user can run
the firmware activate command later to activate the firmware.
Examples
To activate firmware on the device:
firmware commit
Commits a firmware upgrade.
Syntax
firmware commit
Modes
Privileged EXEC mode
Usage Guidelines
The firmware download command updates the secondary partitions only. When the firmware
download command completes successfully and the device reboots, the system swaps partitions. The
primary partition (with the previous firmware) becomes the secondary partition, and the secondary
partition (with the new firmware) becomes the primary partition.
By default, firmware download automatically commits the firmware after the device reboots. If you
disable auto-commit mode when running firmware download, you must execute firmware
commit to commit the new firmware to the secondary partition.
You must run the firmware download command with the nocommit parameter set for the
following firmware commit operation to succeed.
Examples
To commit the firmware:
device# firmware commit
firmware download
Downloads the firmware on the device, reboots the system, and commits the firmware.
Syntax
firmware download { default-config | ftp | scp | sftp | tftp | usb |
interactive } [ manual ] [ nocommit ] [ noreboot ] [ noactivate ]
[ coldboot ] host { hostname | host_ip_address } user username
password password directory directory [ file file_name ] [ use-vrf
vrf-name] ]
Command Default
By default, firmware download downloads the firmware to the system, reboots the system, and
commits the firmware automatically. The user can specify noactivate to download the firmware to
the system without activating it (the node is not rebooted). You can run the firmware activate
command later to activate the firmware.
Parameters
default-config
Sets the configuration back to default.
ftp | scp | sftp | usb
Valid protocols are ftp (File Transfer Protocol), scp (Secure Copy), sftp (SSH File Transfer
Protocol), tftp (Trivial File Transfer Protocol), or usb (Universal Serial Bus). The values are not
case-sensitive.
interactive
Runs firmware download in interactive mode. You are prompted for input.
manual
Currently, this keyword has no effect.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only
to the primary partition. You must execute the firmware commit command manually to
propagate the new image to the secondary partition.
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device
manually.
noactivate
Downloads the firmware to the system without activating it, so the device is not automatically
rebooted. You can run the firmware activate command later to activate the firmware.
coldboot
Downloads the firmware to the system and reboots the device.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file file_name
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file,
release.plist, is used.
user username
Specifies the user login name for the host.
password password
Specifies the account password.
use-vrf vrf-id
Use this option to specify the name of the VRF where the host is located. If this option is not set,
mgmt-vrf is used by default.
Modes
Privileged EXEC mode
Usage Guidelines
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt
traffic.
Examples
Example of firmware download with the coldboot option:
device# firmware download ftp directory /buildsjc/sre/SQA/slxos/17r.1.00/17r.1.00 host
10.31.2.27 user releaseuser password releaseuser coldboot
This command will cause a cold/disruptive reboot and will require that existing telnet,
secure telnet or SSH sessions be restarted.
This command will cause a cold/disruptive reboot and will require that existing telnet,
secure telnet or SSH sessions be restarted.
Syntax
firmware download ftp [ coldboot ] [ manual ] [ noactivate ] [ nocommit ]
[ noreboot ] host { hostname | host_ip_address } use-vrf vrf-name
user username password password directory directory [ file
file_name ]
Command Default
By default, downloads the firmware to the system, reboots the system, and commits the firmware
automatically. The user can specify noactivate firmware download to download the firmware to
the system without activating it (the node is not rebooted). The user can run firmware activate
later to activate the firmware.
Parameters
coldboot
Downloads the firmware to the system and reboots the device.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file file_name
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file,
release.plist, is used.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
manual
Currently, this keyword has no effect.
noactivate
Performs a firmware download without activation on the local device.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only
to the primary partition. You must execute the firmware commit command manually to
propagate the new image to the secondary partition.
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device
manually. If auto-commit mode was disabled, you must perform a manual firmware commit
operation after the device comes back up.
password password
Specifies the account password.
use-vrf vrf-name
Specifies a VRF.
user username
Specifies the user login name for the host.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host.
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt
traffic.
Examples
This example downloads firmware by means of FTP and specifies a path to the directory where the
firmware is located. A user login name is specified for the host and an account password is specified.
device# firmware download ftp directory /buildsjc/sre/SQA/slxos/17r.1.00/17r.1.00 host
10.31.2.27 user releaseuser password releaseuser
Syntax
firmware download { fullinstall | ftp | scp | sftp | tftp | usb }
[ manual ] [ nocommit ] [ noreboot ] [ noactivate ] [ coldboot ] host
{ hostname | host_ip_address } user username password password
directory directory [ file file_name ] [ use-vrf vrf-name] ]
Command Default
By default, firmware download downloads the firmware to the system, reboots the system, and
commits the firmware automatically. The user can specify noactivate to download the firmware to
the system without activating it (the node is not rebooted). You can run the firmware activate
command later to activate the firmware.
Parameters
fullinstall
Downloads a larger file selection to cover the differences between 32-bit and 64-bit firmware
when upgrading or downgrading the device.
ftp | scp | sftp | usb
Valid protocols are ftp (File Transfer Protocol), scp (Secure Copy), sftp (SSH File Transfer
Protocol), tftp (Trivial File Transfer Protocol), or usb (Universal Serial Bus). The values are not
case-sensitive.
manual
Currently, this keyword has no effect.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only
to the primary partition. You must execute the firmware commit command manually to
propagate the new image to the secondary partition.
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device
manually.
noactivate
Downloads the firmware to the system without activating it, so the device is not automatically
rebooted. You can run the firmware activate command later to activate the firmware.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file file_name
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file,
release.plist, is used.
user username
Specifies the user login name for the host.
password password
Specifies the account password.
use-vrf vrf-id
Use this option to specify the name of the VRF where the host is located. If this option is not set,
mgmt-vrf is used by default.
Modes
Privileged EXEC mode
Usage Guidelines
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt
traffic.
The fullinstall option enables upgrading the firmware from a 32-bit version to a 64-bit version.
Additionally, the fullinstall option enables downgrading the firmware from a 64-bit version to a
32-bit version. This feature assumes the device hardware is capable of supporting 64-bit architecture.
The fullinstall option preserves startup-config, SSH host keys, and licenses. However, though the
startup-config is preserved, the system is designed to boot with the default-config. You must manually
apply the configs that were preserved, if configurations are compatible. Manually copying the config file
uses the copy flash://startup-config running-config command or the copy <file>
running-config command.
It is recommended that you back up your running configuration before running the fullinstall command.
Use one of the following commands to do so:
• copy flash://<config> startup-config
• copy scp/ftp/tftp:://<config> startup-config
• copy running-config startup-config .
The system then can use the backed up configuration file to restore your configuration during full install.
Syntax
firmware download interactive
Command Default
By default, firmware download downloads the firmware to the system, reboots the system, and
commits the firmware automatically.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You
can run this command interactively or provide the parameters on the command line.
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt
traffic.
Examples
To perform a firmware download in interactive mode using default parameters:
device# firmware download interactive
Server name or IP address: 10.70.4.106
File name: dist
Protocol (ftp, scp, sftp, tftp) [ftp]: scp
User: fvt
Password: **********
Enter VRF name[mgmt-vrf]:
Select procedure (1=ISSU, 2=coldboot, 3=default-config) [1]:1
This command will cause a cold/disruptive reboot and will require that existing telnet,
secure telnet or SSH sessions be restarted.
Syntax
firmware download scp [ coldboot ] [ manual ] [ nocommit ] [ noreboot ]
host { hostname | host_ip_address } user username password password
directory directory [ file file_name ] [ noactivate ] [ use-vrf vrf-
name]
Command Default
A filename is optional. If no filename is specified, release.plist, is used.
Parameters
coldboot
Downloads the firmware to the system and reboots the device.
manual
Currently, this keyword has no effect.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only
to the primary partition. You must execute the firmware commit command manually to
propagate the new image to the secondary partition. (Skips auto-commit after firmware
download.)
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device
manually. If auto-commit mode was disabled, you must perform a manual firmware commit
operation after the device comes back up.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
user username
Specifies the user login name for the host.
password password
Specifies the account password.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file file_name
Use this option to specify the name of the VRF where the host is located. If this option is not set,
mgmt-vrf is used by default.
Modes
Privileged EXEC mode.
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You
can run this command interactively or provide the parameters on the command line.
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt
traffic.
Examples
This example downloads firmware by means of SCP and specifies a path to the directory where the
firmware is located. A user login name is specified for the host and an account password is specified.
device# firmware download scp directory /buildsjc/sre/SQA/nos/slx17r.1.00/slx17r.1.00
host 10.31.2.27 user releaseuser password releaseuser
Syntax
firmware download sftp [ coldboot ] directory directory [ manual ]
[ nocommit ] [ noreboot ] host { hostname | host_ip_address } user
username password password directory directory [ file file_name ]
[ noactivate ] [ use-vrf vrf-name]
Parameters
coldboot
Downloads the firmware to the system and reboots both the device.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file filename
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file,
release.plist, is used.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
manual
Currently, this keyword has no effect.
noactivate
Performs a firmware download without activation on the local switch.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only
to the primary partition. You must execute the firmware commit command manually to
propagate the new image to the secondary partition. (Skips auto-commit after firmware
download.)
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the switch
manually. If auto-commit mode was disabled, you must perform a manual firmware commit
operation after the switch comes back up.
password password
Specifies the account password.
user username
Use this option to specify the name of the VRF where the host is located. If this option is not set,
mgmt-vrf is used by default.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You
can run this command interactively or provide the parameters on the command line.
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt
traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to
the default settings during the firmware upgrade process.
Examples
This example downloads firmware by means of SFTP and specifies a path to the directory where the
firmware is located. A user login name is specified for the host and an account password is specified.
switch# firmware download sftp directory /buildsjc/sre/SQA/sxlos/slx17r.1.00/slx17r.1.00
host 10.31.2.27 user releaseuser password releaseuser
Syntax
firmware download tftp [ coldboot ] directory directory [ manual ]
[ nocommit ] [ noreboot ] host { hostname | host_ip_address } user
username password password directory directory [ file file_name ]
[ noactivate ] [ use-vrf vrf-name]
Parameters
coldboot
Downloads the firmware to the system and reboots both the active and standby MMs.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
file filename
Specifies the firmware .plist file. This parameter is optional; if unspecified, the default file,
release.plist, is used.
host
Specifies the host by DNS name or IP address.
hostname
Specifies an IPv4 DNS host name.
host_ip_address
Specifies the host IP address. IPv4 and IPv6 addresses are supported.
manual
Currently, this keyword has no effect.
noactivate
Performs a firmware download without activation on the local device.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only
to the primary partition. You must execute the firmware commit command manually to
propagate the new image to the secondary partition. (Skips auto-commit after firmware
download.)
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device
manually. If auto-commit mode was disabled, you must perform a manual firmware commit
operation after the device comes back up.
password password
Specifies the account password.
user username
Use this option to specify the name of the VRF where the host is located. If this option is not set,
mgmt-vrf is used by default.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You
can run this command interactively or provide the parameters on the command line.
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt
traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to
the default settings during the firmware upgrade process.
Examples
This example downloads firmware by means of TFTP and specifies a path to the directory where the
firmware is located. The host is specified by IP address and a firmware .plist file is specified.
device# firmware download tftp directory /buildsjc/sre/SQA/slx/slx17r.1.00/slx17r.1.00
host 10.31.2.27 file release.plist
Syntax
firmware download usb [ coldboot ] [ noactivate ] [ nocommit ]
[ noreboot ] [ manual ] directory directory
Command Default
By default, the firmware download process reboots the system and activates the new image.
Finally, the process performs a firmware commit operation to copy the new image to the other
partition.
Parameters
coldboot
Downloads the firmware to the system and reboots both the active and standby MMs. Caution:
Do not use this option unless instructed to do so by Extreme Technical Support.
directory directory
Specifies a fully qualified path to the directory where the firmware is located.
manual
Currently, this keyword has no effect.
noactivate
Performs a firmware download without activation on the local device.
nocommit
Disables auto-commit mode. When auto-commit mode is disabled, firmware is downloaded only
to the primary partition. You must execute the firmware commit command manually to
propagate the new image to the secondary partition.
noreboot
Disables auto-reboot mode. When auto-reboot mode is disabled, you must reboot the device
manually. If auto-commit mode was disabled, you must perform a manual firmware commit
operation after the device comes back up.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to download firmware from an external host or from an attached USB device. You
can run this command interactively or provide the parameters on the command line.
Unless you specify noactivate, the upgrade or downgrade involves system reboots that disrupt
traffic.
In addition, default-config causes the loss of configuration because it resets the configuration back to
the default settings during the firmware upgrade process.
Examples
To download firmware from an attached USB device using the command line:
Syntax
firmware peripheral-update cpld
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on SLX 9540 and SLX 9640 devices.
WARNING: Hardware image will be upgraded and followed with a board-level power cycling.
Do you want to continue?[y/n]:
Examples
The following example upgrades the firmware on an SLX 9540.
device# firmware peripheral-update cpld
WARNING: Hardware image will be upgraded and followed with a board-level power cycling.
Do you want to continue?[y/n]: y
for cpld0:
erasing ........done
programming .......................... 25% .........................
50% .......................... 75% ......................... 100%
for cpld1:
erasing ........done
programming .......................... 25% .........................
50% .......................... 75% ......................... 100%
Syntax
firmware peripheral-update fpga
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on SLX 9540 and SLX 9640 devices.
WARNING: Hardware image will be upgraded and followed with a board-level power cycling.
Do you want to continue?[y/n]:
Examples
The following example upgrades the firmware on an SLX 9540.
device# firmware peripheral-update fpga
WARNING: Hardware image will be upgraded and followed with a board-level power cycling.
Do you want to continue?[y/n]: y
erasing \ …..
erasing .. ... done
programming .......................... 25% .......
programming .......................... 25% ..........................
50% .......................... 75% .......................... 100%
sysfpga image is upgraded successfully.
device#
firmware recover
Recovers the previous firmware version on the device if a firmware upgrade was unsuccessful.
Syntax
firmware recover
Modes
Privileged EXEC mode
Usage Guidelines
This command reverts the operation that was performed using the firmware download "noactivate"
option.
If you invoke a noactivate firmware download, the firmware is loaded to the secondary node without
swapping partitions. If firmware recover is executed, it performs a forceful commit.
Examples
To recover firmware on the device:
firmware restore
Swaps the partition and reboots the device.
Syntax
firmware restore
Modes
Privileged EXEC mode
Usage Guidelines
Caution
Do not use this command unless instructed by Extreme Technical Support.
Use this command to restore the previously active firmware image. You can run this command only if
auto-commit mode was disabled during the firmware download. After a firmware download and a
reboot (with auto-commit mode disabled), the downloaded firmware becomes active. If you do not
want to commit the firmware, use the firmware restore command.
This command reboots the device and reactivates the previous firmware. After reboot, all primary and
secondary partitions restore the previous firmware image.
This command causes the device to boot up with its older firmware. Later, the image in the primary
partition is automatically committed to the secondary partition.
The firmware download command must have been run with the nocommit parameter for the
firmware restore operation to succeed.
Examples
To restore the previous firmware:
device# firmware restore
Syntax
flex-cli show link-fault-signaling
Modes
Privileged EXEC mode
Output
The flex-cli show link-fault-signaling command displays the following information:
Examples
This example displays information pertaining to LFS.
device# flex-cli show link-fault-signaling
Port Rx-Link-Fault Tx-Link-Fault
0/1 ON ON
0/2 ON ON
0/3 ON ON
0/4 ON ON
0/5 ON ON
0/6 ON ON
0/7 ON ON
0/8 ON ON
0/9 ON ON
0/10 ON ON
0/11 ON ON
0/12 ON ON
0/13 ON ON
0/14 ON ON
0/15 ON ON
0/16 ON ON
0/17 ON ON
0/18 ON ON
0/19 ON ON
0/20 ON ON
0/21 ON ON
0/22 ON ON
Syntax
flex-cli show local-fault interface [ ethernet slot/port | port-channel
port-chnnel-number ]
Parameters
ethernet
Specifies Ethernet interface.
slot-number
Specifies the slot number.
port-channel
Specifies port-channel.
port-channel numbe
Specifies the port-channel number.
Modes
Privileged EXEC mode
Examples
This example displays the local faults of an interface.
device# flex-cli show local-fault interface ethernet 0/9
Port Local-Fault-Detected Local-Fault-Count Time-Last-Local-Fault-Dete
ted
0/9 No 0 N/A
dutC-Aval#
0/4 No 0 N/A
0/5 No 0 N/A
0/6 No 0 N/A
0/7 No 0 N/A
0/8 No 0 N/A
0/9 No 0 N/A
0/10 No 0 N/A
0/11 No 0 N/A
0/12 No 0 N/A
0/13 No 0 N/A
0/14 No 0 N/A
0/15 No 0 N/A
0/16 No 0 N/A
0/17 No 0 N/A
0/18 No 0 N/A
0/19 No 0 N/A
0/20 No 0 N/A
0/21 No 0 N/A
Syntax
flex-cli show local-fault slot slot-number
Parameters
slot-number
Specifies the slot number.
Modes
Privileged EXEC mode
Examples
This example displays the local faults of a slot.
device# flex-cli show local-fault slot 1
Port Local-Fault-Detected Local-Fault-Count Time-Last-Local-Fault-Deteted
0/1 No 0 N/A
0/2 No 0 N/A
0/3 No 0 N/A
Syntax
flex-cli show remote-fault interface [ ethernet slot/port | port-channel
port-channel-number ]
Parameters
ethernet
Specifies an Ethernet interface.
slot/port number
Specifies the slot or port number.
port-channel
Specifies a port-channel.
port-channel-number
Specifies the port-channel number.
Modes
Privileged EXEC mode
Examples
This example displays the remote faults of an interface.
device# flex-cli show remote-fault interface ethernet 0/10
Port RFN-Detected Remote-fault-count Time-last-RFN-Detected
0/10 No 0 N/A
Syntax
flex-cli show remote-fault slot slot-number
Parameters
slot-number
Specifies the slot number.
Modes
Privileged EXEC mode
Examples
This example displays the remote faults of a slot.
device# flex-cli show remote-fault slot 1
Port RFN-Detected Remote-fault-count Time-last-RFN-Detected
0/1 No 0 N/A
0/2 No 0 N/A
0/3 No 0 N/A
0/4 No 0 N/A
0/5 No 0 N/A
0/6 No 0 N/A
0/7 No 0 N/A
0/8 No 0 N/A
0/9 No 0 N/A
0/10 No 0 N/A
0/11 No 0 N/A
0/12 No 0 N/A
0/13 No 0 N/A
0/14 No 0 N/A
0/15 No 0 N/A
0/16 No 0 N/A
0/17 No 0 N/A
0/18 No 0 N/A
0/19 No 0 N/A
0/20 No 0 N/A
0/21 No 0 N/A
0/22 No 0 N/A
flow-label
Enables flow label for a pseudowire (PW) profile.
Syntax
flow-label
no flow-label
Command Default
By default, control word is disabled for PW profiles.
Modes
Pseudowire profile configuration mode
Usage Guidelines
The no form of the command disables flow label for a PW profile.
Flow label configuration improves load balancing of PW traffic over an MPLS network, particularly in the
context of PWs that transport high volumes of traffic that are comprised of multiple individual traffic
flows (for example, the same source-destination pair for a Transport Control Protocol (TCP) connection
is an individual traffic flow).
Examples
The following example shows how to enable flow label for a PW profile named pw_example
The following example shows how to disable flow label for a PW profile named pw_example
flowspec validation
Configures Border Gateway Protocol flow specification (BGP flowspec) route validation at address-
family level.
Syntax
flowspec validation [ redirect ]
no flowspec validation [ redirect ]
Command Default
Flowspec validation is enabled.
Parameters
redirect
Specifies only validation of the redirect IP nexthop address.
Modes
BGP address-family IPv4 flowspec configuration mode
Usage Guidelines
Flowspec validation can be configured at neighbor, peer-group, or address-family level with the
neighbor-level configuration prioritized over peer-group level configuration and the peer-group level
configuration prioritized over the address-family level configuration.
Use the flowspec validation command to configure flowspec validation at address-family level.
To configure flowspec validation at neighbor or peer-group level, refer to the neighbor flowspec
validation command.
By default, flowspec validation is enabled. Use the no form of the flowspec validation command
to completely disable flowspec validation at address-family level. To only disable redirect IP nexthop
validation at address-family level, use the no form of the flowspec validation command
specifying the redirect opton.
Only one flowspec validation configuration is allowed at a time. Configuration operates as follows:
• When complete flowspec validation is aleady disabled, issuing the no flowspec validation
command specifying the redirect option has no impact; complete flowspec validation remains
disabled.
• When the redirect option is already disabled, issuing the no flowspec validation
command without the redirect option changes the configuration to complete flowspec validation
disabled.
Examples
The following example shows how to disable IPv4 flowspec validation. In this example and because the
redirect option is specified, only redirect IP nexthop validation is disabled for the IPv4 address-
family in the default VRF.
When flowspec validation is already completely disabled, issuing the no flowspec validation
specifying the redirect option does not change the configuration. The following example shows how
to completely disable flowspec validation for the IPv4 address family in a VRF named red and to verify
the configuration. The no flowspec validation command is then issued specifying the
redirect option, and the configuration is again displayed to show that flowspec validation remains
completely disabled.
force-switch
Forces the blocking of a specified link for Ethernet Ring Protection (ERP).
Syntax
force-switch { vlan vlan_id ethernet slot/port | port-channel number }
no force-switch { vlanvlan_id ethernet slot/port | port-channel number }
Command Default
This feature is not configured by default.
Parameters
vlan vlan_id
Specifies a VLAN. Range is from 1 through 4090.
ethernet slot/port
Specifies an Ethernet interface.
port-channel number
Specifies a port-channel.
Modes
ERP configuration mode
Usage Guidelines
An operator can use the forced switch (FS) mechanism when no errors, a single error, or multiple errors
are present in the topology. You can enter this command multiple times. You need to explicitly specify
the VLAN and Ethernet slot and port.
Examples
The following example configures FS for a specified interface.
device# configure terminal
device(config)# erp 100
device(config-erp-100)# force-switch vlan 100 ethernet 0/10
device(config-erp-100)#
format RFC-5424
Configures a specified syslog server to log messages using the RFC-5424 format.
Syntax
format RFC-5424
no format RFC-5424
Parameters
RFC-5424
Syslog message format defined in RFC-5424.
Modes
Syslog server configuration mode
Usage Guidelines
Use this command to configure the router to generate log messages with the RFC-5424 format.
<prival><version><space>< time-stamp><space><host-name><space><app
name><space><process id><space><Msg Id>
Where:
• prival is the priority field. This is always <190> for SLXOS 17r.2.00.
• version is the version number of the syslog protocol standard. Currently, this can only be 1.
• time-stamp is the ISO 8601 compatible standard timestamp format (yyyy-mm-ddThh:mm:ss+-
ZONE).
• host-name is the machine that originally sent the message, or if no hostname, a “-“ is present
instead.
• app name is the device or application that generated the message, or if no application, a “-“ is
present instead.
• process id is the process name or PID (process ID) of the syslog application that sent the
message, or if no PID, a “-“ is present instead. This is always - in the SLX-OS 17r.2.00 release.
• Msg Id is the ID number of the message, or if no Message ID, a “-“ is present instead. This is always
- in the SLX-OS 17r.2.00 release.
For example:
<190>1 2017-06-19T09:19:52.000003+00:00 SLX raslogd - -
Note
In the SLX-OS 17r.2.00 release, the process id and Msg Id fields are not filled and are
replaced with - -.
Use the no format RFC-5424 command to remove the RFC-5424 log message format from the
syslog server configuration.
Examples
First, access the global configuration level of the CLI and configure the IP address for the syslog server.
Then, enter the format RFC-5424 command to configure the router to use the RFC-5424 format as
shown in the following example.
device# configure terminal
device(config)# logging syslog-server 192.168.163.233
device(config-syslog-server-192.168.163.233)# format RFC-5424
To verify the syslog server log message format, enter the show running-config logging
syslog-server command as shown in the following example.
device# running-config logging syslog-server
logging syslog-server 192.168.163.233
format RFC-5424
To remove the RFC-5424 format from the configured syslog server, enter the no format RFC-5424
command as shown in the following example.
device(config)# logging syslog-server 192.168.163.233
device(config-syslog-server-192.168.163.233)# no format RFC-5424
forward-delay
Specifies the time an interface spends in each of the listening and learning states.
Syntax
forward-delay seconds
no forward-delay
Command Default
15 seconds
Parameters
seconds
Specifies the time that an interface spends in the Spanning Tree Protocol (STP) learning and
listening states. Valid values range from 4 through 30 seconds.
Modes
Spanning tree configuration mode
Usage Guidelines
This command specifies how long the listening and learning states last before the interface begins the
forwarding of all spanning-tree instances.
When you change the spanning-tree forward-delay time, it affects all spanning-tree instances. When
configuring the forward-delay, the following relationship should be kept:
Examples
To configure the forward-delay time to 18 seconds:
from
Configures only the local interface of the routing device. The command penalizes any link on the
specified interface, but not all links when the link is a multi-access link.
Syntax
from ip_addr
no from ip_addr
Command Default
The command is disabled, by default.
Parameters
ip_addr
Specifies the selected IP address of the fate sharing group
Modes
MPLS CSPF-group configuration mode (config-router-mpls-cspf-group-group_name)
Usage Guidelines
The order in which the local IP address to the remote IP address is configured is insignificant. For
example, the configuration from 10.10.10.10 to 10.20.20.20 and from 10.20.20.20 to 10.10.10.10 has the
same meaning.
The user can configure an interface level from IP address for a dynamic bypass LSP to be created for
the protected MPLS interface. Dynamic bypasses use the from address as the IP address.
The no form of the command removes the from-address and is set to default.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the local address 10.1.1.1 of the fate sharing group.
device# configure
device(config)# router mpls
device(config-router-mpls)# cspf-group group3
device(config-router-mpls-cspf-group-group3)# from 10.1.1.1
The following example configures the from address 11.11.11.11 for dynamic bypass MPLS Ethernet
interface 0/8.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# from 11.11.11.11
frr
Configures a Fast Reroute (FRR) path.
Syntax
frr
Modes
Router MPLS configuration mode
Usage Guidelines
Fast Reroute paths are used as secondary routes or backup routes to increase network high availability.
Several reroute options are available; for example, the bandwidth can be configured for the path using
the bandwidth subcommand and the setup and hold priority can be configured for the path using the
priority subcommand. Refer to the Extreme SLX-OS MPLS Configuration Guide for detailed Fast
Reroute configuration information.
Note
Hardware support for LSP FRR is available only for TPID 0x8100. If you require a label
switched path with fast reroute (LSP FRR) configuration, none of the routable interfaces
(whether a router port or a LIF of a VE) can have a nondefault TPID configuration, because
FRR always assumes that the link layer has the default TPID of 0x8100.
The following error message is displayed if you try to configure a fast reroute path using the
frr command on an interface with a non-default TPID:
%Error: Not allowed, when a non-default TPID (tag-type) is configured on any port-channel or
physical interfaces.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example displays how to configure a Fast Reroute LSP named frr_tunnelA with a
bandwidth of 1000 kbits per second, and a set up and hold priority of 6 and 1.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp frr_tunnelA
device(config-router-mpls-lsp-frr_tunnelA)# frr
device(config-router-mpls-lsp-frr_tunnelA-frr)# bandwidth 1000
device(config-router-mpls-lsp-frr_tunnelA-frr)# priority 6 1
Syntax
gNMI server
no gNMI server
Command Default
By default, non TLS gNMI server runs on port 9339.
Examples
This configures a secure-port for TLS gNMI server. Choose a unique port in the range of 1024 to 49151.
TLS certificates are to be imported for gNMI server should be imported before configuring the secure-
port. For importing TLS server certificate, refer to crypto ca import-pkcs section.
SLX# configure terminal
Entering configuration mode terminal
SLX(config)# gNMI server
SLX(config-gNMI-server)# secure-port ?
Possible completions:
<NUMBER:1024-49151> Port range from 1024 to 49151
SLX(config-gNMI-server)# secure-port <NUMBER>
Example.
SLX(config-gNMI-server)# secure-port 9449
Use the show running-config gNMI command to view the configuration.
Unconfigures the secure gNMI server. Henceforth, non-TLS gNMI server will be running.
SLX(config-gNMI-server)# no secure-port
graceful-restart (BGP)
Enables the BGP graceful restart capability.
Syntax
graceful-restart [ purge-time seconds | restart-time seconds | stale-
routes-time seconds ]
no graceful-restart
Command Default
Disabled.
Parameters
purge-time
Specifies the maximum period of time, in seconds, for which a restarting device maintains stale
routes in the BGP routing table before purging them. The default value is 600 seconds. The
configurable range of values is from 1 to 3600 seconds.
restart-time
Specifies the restart-time, in seconds, advertised to graceful restart-capable neighbors. The
default value is 120 seconds. The configurable range of values is from 1 to 3600 seconds.
stale-routes-time
Specifies the maximum period of time, in seconds, that a helper device will wait for an End-of-
RIB (EOR) message from a peer. All stale paths are deleted when this time period expires. The
default value is 360 seconds. The configurable range of values is from 1 to 3600 seconds.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use this command under a BGP address-family configuration mode to enable or disable the graceful-
restart capability for all BGP neighbors in the address family. When this command is enabled, graceful-
restart capability is negotiated with neighbors in the BGP OPEN message when a session is established.
If the neighbor advertises support for graceful restart, that function is activated for that neighbor
session. Otherwise, graceful restart is not activated for that session, even though it is enabled locally. If
the neighbor has not sent graceful-restart parameters, the restarting device will not wait for the
neighbor to start route calculation, but graceful restart will be enabled.
If the graceful-restart capability is enabled after a BGP session has been established, the neighbor
session must be cleared for graceful restart to take effect.
The purge-time parameter is applicable for both restarting and helper devices. The timer starts when
a BGP connection is closed. The timer ends when an EOR is received from all nodes, downloaded into
BGP and an EOR sent to all neighbors. The configured purge-time timer value is effective only on the
configured node.
The restart-time parameter is applicable only for helper devices. The timer starts at the time the
BGP connection is closed by the remote peer and ends when the Peer connection is established. The
configured restart-time timer value is effective only on the peer node, and not in the configured node.
During negotiation time, the timer value is exchanged.
The stale-routes-time parameter is applicable only for helper devices. The timer starts when the
peer connection is established after the HA-failover. The timer ends at the time an EOR is received from
the peer. The configured stale-time timer value is effective only on the configured node.
For non-default VRF instances, graceful restart timers are inherited from the default VRF. The purge-
time, restart-time, and stale-routes-time parameters are not available in BGP address-
family IPv4 unicast VRF configuration mode and BGP address-family IPv6 unicast VRF configuration
mode.
Use the clear ip bgp neighbor command with the all parameter for the changes to the
graceful-restart parameters to take effect immediately.
The no form of the command disables the BGP graceful-restart capability globally for all BGP neighbors
in the address family.
Examples
The following example enables the BGP graceful restart capability.
The following example enables the BGP graceful restart capability and sets the purge time to 220
seconds in L2VPN EVPN configuration mode.
graceful-restart (LDP)
Enables the MPLS LDP graceful restart capability for all LDP sessions and accesses the graceful restart
(GR) configuration mode .
Syntax
graceful-restart
no graceful-restart
Command Default
Disabled.
Modes
MPLS LDP configuration mode
Usage Guidelines
When you enable LDP GR, the router waits until it receives an LDP Initialization message from its
neighbor to know whether it must delete its states or start the LDP GR recovery procedure. It is
applicable to all LDP sessions regardless of the adjacency type exists between the neighbors.
The no form of the command disables the LDP graceful-restart capability globally for all LDP sessions
and removed the configuration.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables the BGP graceful restart capability.
graceful-restart (OSPFv2)
Enables the OSPF Graceful Restart (GR) capability.
Syntax
graceful-restart [ helper-disable | restart-time seconds ]
no graceful-restart
Command Default
Graceful restart and graceful restart helper capabilities are enabled.
Parameters
helper-disable
Disables the GR helper capability.
restart-time
Specifies the maximum restart wait time, in seconds, advertised to neighbors. The default value
is 120 seconds. The configurable range of values is from 10 through 1800 seconds.
Modes
OSPF router configuration mode
Usage Guidelines
Use no graceful-restart helper-disable to re-enable the GR helper capability.
Examples
The following example disables the GR helper capability.
The following example re-enables the GR capability and changes the maximum restart wait time from
the default value to 240 seconds.
graceful-restart (OSPFv3)
Enables the OSPFv3 Graceful Restart capability.
Syntax
graceful-restart [ helper | restart-time seconds ]
no graceful-restart [ helper | restart-time seconds ]
Command Default
By default, graceful restart and graceful restart helper capabilities are enabled.
Parameters
helper
Sets graceful restart helper options.
restart-time seconds
Specifies the maximum restart wait time, in seconds, advertised to neighbors. The default value
is 120 seconds. Valid values range from 10 through 1800 seconds.
Modes
OSPF IPv6 router configuration mode
Usage Guidelines
Use the no graceful-restart command to disable graceful restart mode.
Use the no graceful-restart helper command to disable the graceful restart helper capability.
Examples
This example disables the graceful restart helper capability.
device# configure terminal
device(config)# ipv6 router ospf
device(config-ipv6-router-ospf-vrf-default-vrf)# no graceful-restart helper
Syntax
graceful-restart helper { disable | strict-lsa-checking }
no graceful-restart helper
Command Default
GR helper is enabled.
Parameters
disable
Disables the OSPFv3 GR helper capability.
strict-lsa-checking
Enables the OSPFv3 GR helper mode with strict link-state advertisement (LSA) checking.
Modes
OSPFv3 router configuration mode
Usage Guidelines
The no form of the command disables the GR helper capability on a device.
Examples
The following example enables GR helper and sets strict LSA checking.
Syntax
graceful-restart helper-disable
no graceful-restart helper-disable
Command Default
The graceful restart helper is enabled by default.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command re-enables the graceful restart helper if it has been disabled.
Examples
The following example disables the IS-IS graceful restart helper.
device# configure terminal
device(config)# router isis
device(config-isis-router)# graceful-restart helper-disable
graceful-shutdown
Gracefully shuts down all BGP neighbors.
Syntax
graceful-shutdown seconds [ community value [ local-preference value ] |
local-preference value [ community value ] | route-map route-map-
name ]
no graceful-shutdown seconds [ community value [ local-preference value ]
| local-preference value [ community value ] | route-map route-map-
name ]
Command Default
Default graceful shutdown parameters are applied.
Parameters
seconds
Specifies the number of seconds in which the BGP graceful shutdown will occur. Valid values
range from 30 through 600 seconds.
community value
Sets the community attribute for graceful shutdown. Valid values range from 1 through
4294967295.
local-preference value
Sets the local preference attribute for graceful shutdown. Valid values range from 0 through
4294967295.
route-map route-map-name
Specifies the route map for graceful shutdown attributes.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command de-activates graceful shutdown.
Examples
The following example gracefully shuts down all BGP neighbors and sets the graceful shutdown timer to
180 seconds.
The following example gracefully shuts down all BGP neighbors and sets the graceful shutdown timer to
600 seconds. The route map “myroutemap” is specified for graceful shutdown attributes.
The following example gracefully shuts down all BGP neighbors and sets the graceful shutdown timer to
600 seconds. The community attribute is set to 10.
grub
This command navigates into the GRUB configuration mode.
Syntax
grub
Modes
Global Configuration mode
Usage Guidelines
The GRUB configuration mode is used to configure a password for securing GRUB from unauthorized
changes.
Examples
The following example navigates into the GRUB configuration mode.
SLX # configure terminal
SLX (config)# grub
SLX (config-grub) #
guard-time
Specifies a value for the Ethernet Ring Protection (ERP) guard timer.
Syntax
guard-time time
no guard-time
Command Default
The guard timer is configured at 1500 milliseconds (ms) by default.
Parameters
time
Time in ms. Range is from 1200 through 4000, in intervals of 100.
Modes
ERP configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
Examples
The following example configures a guard timer value of 1400 ms.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# guard-time 1400
handle-isis-neighbor-down
Globally enables the handling of an IGP neighbor down event by MPLS. This command takes effect
immediately and you can run it as needed.
Syntax
handle-isis-neighbor-down
no handle-isis-neighbor-down
Command Default
By default, RSVP does not handle IGP neighbor down events. RSVP IGP synchronization must be
enabled to handle an IGP neighbor down event.
Modes
MPLS policy mode (config-router-mpls-policy)
Usage Guidelines
The handle-isis-neighbor-down command is independent of MPLS traffic engineering
configurations. The handle-isis-neighbor-down command allows MPLS (RSVP) to handle IGP
neighbor down events and take action, such as tearing down the associated RSVP sessions. For
example, when IS-IS is configured as MPLS TE protocol, the user can still configure MPLS to handle an
OSPF neighbor down event (and vice versa).
An IGP neighbor down event is handled only by the RSVP sub-component of MPLS by tearing down the
associated sessions. This event is not handled by LDP sub-component of MPLS.
MPLS RSVP does not keep track of the current state of IGP neighbor. That is, when an IGP neighbor
goes down, RSVP tears down all the associated sessions. But RSVP does not prevent bringing up any
session while the IGP neighbor to RSVP next-hop is down (or not yet available). That is, the RSVP
session is brought up even when the IGP neighbor to the next-hop does not exist.
An IGP neighbor down is treated as upstream neighbor down or downstream neighbor down event by
RSVP, depending upon the direction of the LSP. When a downstream IGP neighbor goes down, it results
in an LSP tear down or FRR switchover, whichever is applicable.
MPLS receives and processes an IGP neighbor down event only for the cases when an IGP neighbor
goes down because of hellos not received from the peer.
When an IGP neighbor goes down because of an underlying interface down, MPLS does not react to an
IGP neighbor down event as RSVP would also receive the interface down event and tears down
associated LSP sessions. Handling an IGP neighbor down event is redundant in such situations.
When BFD is configured on IGP interfaces, an IGP neighbor down is detected quickly and may help
RSVP converge faster.
When an IGP neighbor is Nonstop Routing or Graceful Restart capable, MPLS does not receive a
neighbor down event when NSR is performed on the peer IGP router.
Faster FRR feature is not be triggered when MPLS detects that IGP neighbor is down. Instead, each FRR
LSP is processed individually to perform local repair.
It is highly recommended to observe extreme caution when implementing this feature when BFD is
enabled for the underlying IGP. Under some circumstances, unnecessary flapping for RSVP sessions/
LSPs can occur with this combination.
The no version of the command does not handle IGP neighbor down events.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example shows how to enable the RSVP to handle IGP neighbor down events for IS-IS.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# handle-isis-neighbor-down
hardware
Accesses hardware configuration mode, from which you can also access the connector and the profile
configuration modes.
Syntax
hardware
Modes
Global configuration mode
Examples
The following example shows the accessing of hardware configuration mode.
device# configure terminal
device(config)# hardware
device(config-hardware)#
Syntax
hardware media-database activate
Command Default
By default, the media-database is not activated.
Modes
Privileged EXEC mode
Usage Guidelines
The media-database contains the list of port media supported on the device. This information is saved
in an .xml file on the device.
The default version of the file is provided in the release package. You can also download your own
version or upload the file to a remote server for modification. After a new media-database is
downloaded to the device, it needs to be activated to take effect.
You can use the show hardware media-database command to see the supported media types in
the media-database file.
After the media-database is activated, the device sends RASLOG to warn against incompatible media
that is detected on the ports. You can use this information to help identify the cause of links that do not
come online.
Examples
This example activates the media-database file.
device# hardware media-database activate
device#
hardware smt
Enables or disables simultaneous multithreading (SMT).
Syntax
hardware smt { enable | disable }
Command Default
By default, SMT is enabled.
Parameters
enable
Enables SMT.
disable
Disables SMT.
Modes
Privileged EXEC mode
Usage Guidelines
SMT is a performance optimization mechanism deployed by Intel processors. To help mitigate security
vulnerabilities related to SMT, use the hardware smt command to enable or disable SMT.
By enabling SMT, you disable the security mitigation in favor of better performance. By disabling SMT,
you enable the security mitigation.
You need to restart the device to enable changes. A warning message in the CLI reminds you to do so.
This command is supported only on devices based on the Broadcom DNX chipset family. For a list of
such devices, see the Supported Hardware topic.
Examples
This example enables SMT.
device# hardware smt enable
Warning: Please reload the switch to activate the new SMT setting.
hello (LLDP)
Sets the interval between LLDP hello messages.
Syntax
hello seconds
no hello
Command Default
30 seconds
Parameters
seconds
Valid values range from 4 through 180 seconds.
Modes
LLDP protocol and profile configuration modes
Usage Guidelines
The LLDP hello messages can also be configured for a specific LLDP profile. When you apply an LLDP
profile on an interface using the lldp profile command, it overrides the global configuration. If a
profile is not present, then the default global profile is used until you create a valid profile.
Examples
To set the time interval to 10 seconds between the transmissions:
To set the time interval to 8 seconds between the transmissions for a specific LLDP profile:
Syntax
hello [ interval seconds ] [tolerance number]
no hello [ interval ] [tolerance ]
Command Default
RSVP Hello is disabled on the device.
Parameters
interval seconds
Specifies the interval in seconds between two RSVP Hello requests. Enter an integer from 1 to 60.
tolerance number
Specifies the number of unacknowledged RSVP Hello requests before timeout. Enter a number
from 1 to 255.
Modes
MPLS RSVP configuration mode
Usage Guidelines
When you configure the interval and tolerance for the RSVP-TE Hello protocol globally, they are pushed
to all MPLS interfaces when MPLS interface configurations are not present. In addition to these two
parameters, you can configure the acknowledgments globally.
You can configure RSVP-TE Hello interval and tolerance on an MPLS interface. The interface
configurations take precedence over global configurations.
By default, acknowledgments are not sent on the MPLS interface supporting RSVP Hello when no
sessions are taken on the interface.
Caution
When disabling RSVP hello, disable it on both sides of the link at the same time to avoid
bringing down all the RSVP sessions going over that link.
Use the no command to disable RSVP Hello, or to reset the default interval or tolerance settings.
The no hello command on the MPLS interface sets the RSVP-TE Hello parameters to the globally
configured RSVP Hello parameter values. If RSVP Hello is not configured globally, it disables the RSVP
Hello on the MPLS interface. Executing this removes the configuration from the interface.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables RSVP hello globally and configures the interval at 15 seconds and a
tolerance of 8.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# rsvp
device(config-router-mpls-rsvp)# hello interval 15 tolerance 8
The following example enables RSVP hello on an MPLS interface and configures the interval at 20
seconds and a tolerance of 10.
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/12
device(config-router-mpls-interface-0/12)# rsvp
device(config-router-mpls-interface-0/12-rsvp)# hello interval 20 tolerance 10
hello (UDLD)
Sets the hello transmit interval.
Syntax
hello hundred_milliseconds
no hello
Command Default
5 is the default value (500 milliseconds).
Parameters
hundred_milliseconds
Valid values range from 1 through 60 (in counts of 100 milliseconds).
Modes
Unidirectional link detection (UDLD) protocol configuration mode
Usage Guidelines
Use this command to set the time interval between the transmission of hello UDLD PDUs from UDLD-
enabled ports.
Examples
To set the time interval to 2,000 milliseconds between hello UDLD PDU transmissions:
hello padding
Re-enables the padding of Intermediate System-to-Intermediate System (IS-IS) hello Protocol Data
Units (PDUs) globally.
Syntax
hello padding [ disable ] [ point-to-point ]
no hello padding [ disable ] [ point-to-point ]
Command Default
Enabled.
Parameters
disable
Disables the padding of IS-IS hello PDUs.
point-to-point
Specifies point-to-point interfaces.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Generally, you do not need to disable padding unless a link is experiencing slow performance. If you
enable or disable padding on an interface using the isis hello padding command, the interface
setting overrides the global setting.
The no form of the command disables the padding of IS-IS hello PDUs.
Examples
The following example globally disables padding of IS-IS hello PDUs.
The following example globally disables padding of IS-IS hello PDUs for point-to-point interfaces.
The following example globally re-enables padding of IS-IS hello PDUs for Point-to-Point interfaces.
hello-acknowledgements
Configures the MPLS RSVP-TE Hello to respond back with Hello ACKs to neighbors not carrying any
RSVP sessions.
Syntax
hello-acknowledgements
no hello-acknowledgements
Command Default
By default, RSVP Hello acknowledgements are disabled.
Modes
MPLS RSVP configuration mode
Usage Guidelines
Use the no form of this command to reset the default behavior.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables RSVP Hello acknowledgements.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# rsvp
device(config-router-mpls-rsvp)# hello-acknowledgements
hello-interval (LD)
Configures a global hello interval for the loop-detection (LD) protocol.
Syntax
hello-interval milliseconds
no hello-interval
Command Default
The default interval is 1000 milliseconds.
Parameters
milliseconds
Range is from 100 through 5000 milliseconds. The default is 1000 milliseconds.
Modes
Protocol Loop Detection configuration mode
Usage Guidelines
Use the no form of this command to revert to the default hello interval.
Examples
To configure a hello interval of 2000 milliseconds:
device# configure terminal
device(config)# protocol loop-detection
device(config-loop-detect)# hello-interval 2000
hello-interval (LDP)
Sets the interval between LDP Hello messages for LDP sessions for LDP interfaces. These messages
maintain LDP sessions between the device and its LDP peers.
Syntax
hello-interval interval
no hello-interval interval
Command Default
For an LDP interface configuration, the default value is the interval for the configured global LDP Hello
messages.
Parameters
interval
Specifies the interval in seconds. Enter an integer from 1 through 32767.
Modes
MPLS interface LDP configuration mode
Usage Guidelines
Use this command to set the interval for LDP Link Hello messages that are multicast to all routers on the
subnet.
When you configure the LDP link interval for an interface, it overrides the global interval.
When a Hello Adjacency already exists, the adjacency remains up and any new configured interval takes
effect upon the expiration of the current Hello Interval timer. Consequently, the next and subsequent
Hello messages are sent at the new interval.
Examples
The following example sets the link Hello message interval for the interface to 30 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 1/2
device(config-router-mpls-interface-1/2)# ldp-params
device(config-router-mpls-interface-1/2-ldp-params)# hello-interval 30
hello-interval (PIM)
Configures the frequency with which the device sends PIM hello messages to its neighbors.
Syntax
hello-interval seconds
no hello-interval
Command Default
By default, the hello-interval is 30 seconds.
Parameters
seconds
Specifies the hello interval in seconds. The range is 10 through 3600 seconds.
Modes
PIM Router configuration mode
Usage Guidelines
Use the no hello-interval form of this command to reset the default interval.
Devices use PIM hello messages to advertise themselves as PIM routing devices to their neighbors. At
the beginning of an interval, a device sends a hello message, and the timer is reset. The device drops
any neighbor that doesn't respond to the message in a period that is 3.5 times the hello interval.
Examples
The following example configures the IPv4 PIM hello interval.
device(config)# router pim
device(config-pim-router)# hello-interval 50
hello-interval-link
Sets the interval between LDP link Hello messages globally which applies to all LDP interfaces. These
messages are used to maintain LDP sessions between the device and its LDP peers.
Syntax
hello-interval-link interval
no hello-interval-link
Command Default
The default is 5 seconds.
Parameters
interval
Specifies the interval in seconds. Enter an integer from 1 through 32767.
Modes
MPLS LDP configuration mode
Usage Guidelines
Use this command to globally set the interval for LDP Link Hello messages that multicast to all routers
on the subnet.
When you configure the LDP link interval for an interface, it overrides the global interval for the
interface.
When a Hello Adjacency already exists, the adjacency remains up and any new configured interval takes
effect upon the expiration of the current Hello Interval timer. Consequently, the next and subsequent
hello messages are sent at the new interval.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the global interval to 10 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# hello-interval-link 10
hello-interval-target
Sets the interval between LDP Targeted Hello messages globally for all LDP interfaces. These messages
are used to maintain LDP sessions between the device and its LDP peers.
Syntax
hello-interval-target interval
no hello-interval-target
Command Default
The default is 15 seconds.
Parameters
interval
Specifies the interval in seconds. Enter an integer from 1 through 32767.
Modes
MPLS LDP configuration mode
Usage Guidelines
Use this command to set the interval for LDP Targeted Hello messages that are unicast to a specific
address, such as a VLL peer.
For targeted LDP sessions, the LDP Hello Interval can only be set globally.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the interval for LDP Targeted Hello messages to 10 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# hello-interval-target 10
hello-time
Sets the interval between the hello Bridge Protocol Data Units (BPDUs) sent on an interface.
Syntax
hello-time seconds
no hello-time
Command Default
2 seconds
Parameters
seconds
Specifies the time interval between the hello BPDUs sent on an interface. Valid values range from
1 through 10 seconds.
Modes
Spanning tree configuration mode
Usage Guidelines
This command configures the spanning-tree bridge hello time, which determines how often the device
broadcasts hello messages to other devices.
If the VLAN parameter is not provided, the hello-time value is applied globally for all per-VLAN
instances. But for the VLANs which have been configured explicitly, the per-VLAN configuration takes
precedence over the global configuration. When configuring the hello-time, the max-age
command setting must be greater than the hello-time setting. The following relationship should be
kept:
Examples
To configure spanning tree bridge hello time to 5 seconds:
hello-timeout (LDP)
Sets how long the device waits for its LDP peers for LDP sessions to send a Hello message for LDP
interfaces.
Syntax
hello-timeout seconds
no hello-timeout seconds
Command Default
For an LDP interface configuration, the default value is the hold time for the configured global LDP Hello
messages.
Parameters
seconds
Specifies the hold time in seconds. Enter an integer from 2 through 65335. The minimum value
that can be configured for the hold time is two times the value set for the Hello interval.
Modes
MPLS interface LDP configuration mode
Usage Guidelines
When the device does not receive a Hello message within this time, the LDP session with the peer can
be terminated. The device includes the hold time in the Hello messages it sends out to its LDP peers.
The new time takes effect immediately and goes in the next Hello message sent. This hold time applies
to only the hold time that the device sends to its peers. It does not affect the hold time the device uses
to time out those peers. The latter is determined from the hold time that peers send to the device.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the link Hello hold time for the interface to 30 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/2
device(config-router-mpls-interface-0/2)# ldp-params
device(config-router-mpls-interface-0/2-ldp-params)# hello-timeout 30
hello-timeout-link
Sets how long the device waits for its LDP peers for link LDP sessions to send a Hello message.
Syntax
hello-timeout-link seconds
no hello-timeout-link
Command Default
The default is 15 seconds.
Parameters
seconds
Specifies the hold time in seconds. Enter an integer from 2 through 65335.
Modes
MPLS LDP configuration mode
Usage Guidelines
When the device does not receive a Hello message within this time, the LDP session with the peer can
be terminated. The device includes the hold time in the Hello messages it sends out to its LDP peers.
The new time takes effect immediately and goes in the next Hello message sent. This hold time applies
to only the hold time that the device sends to its peers. It does not affect the hold time the device uses
to time out those peers. The latter is determined from the hold time that peers send to the device.
Use the no for this command to reset the default hold time.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the global hold time to 10 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# hello-timeout-link 10
hello-timeout-target
Sets how long the device waits for its LDP peers for targeted LDP sessions to send a Hello message.
Syntax
hello-timeout-target seconds
no hello-timeout-target
Command Default
The default is 45 seconds.
Parameters
seconds
Specifies the hold time in seconds. Enter an integer from 2 through 65335.
Modes
MPLS LDP configuration mode
Usage Guidelines
When the device does not receive a Hello message within this time, the LDP session with the peer can
be terminated. The device includes the hold time in the Hello messages it sends out to its LDP peers.
The new time takes effect immediately and goes in the next Hello message sent. This hold time applies
to only the hold time that the device sends to its peers. It does not affect the hold time the device uses
to time out those peers. The latter is determined from the hold time that peers send to the device.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the global hold time to 10 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# hello-timeout-target 10
helper-only
Specifies that the LSR acts as a helper only for LDP graceful restart (GR).
Syntax
helper-only
no helper-only
Command Default
Full LDP GR mode with the router acting either as a restarting router or a GR helper.
Modes
MPLS LDP GR configuration mode
Usage Guidelines
A GR helper is an LSR whose neighbor is restarting its LDP component.
In helper mode, a router does not preserve its forwarding entries on a LDP GR restart. It indicates to its
peers that forwarding state is not preserved by sending an initialization message with the Reconnect
Time and the Recovery Time set to zero (0) in FT session TLV. The configuration commands for
reconnect-time and recovery-time are rejected with informational messages. However, it can help a
neighboring router recover its forwarding entries when the neighbor is going through restart.
The no form of the command removes the LDP GR helper mode and revert back to full LDP GR mode
with the router acting either as a restarting router or a GR helper.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the LSR for LDP GR helper mode only.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# graceful-restart
device(config-router-mpls-ldp-gr)# helper-only
hold-time
Sets the time that a previously down backup VRRP router, which also must have a higher priority than
the current master VRRP router, will wait before assuming mastership of the virtual router.
Syntax
hold-time range
Command Default
0 seconds
Parameters
range
A value between 1 and 3600 seconds that specifies the time a formerly down backup router
waits before assuming mastership of the virtual router.
Modes
Virtual-router-group configuration mode
Usage Guidelines
The hold-time must be set to a number greater than the default of 0 seconds for this command to take
effect.
Examples
To set the hold time to 60 seconds for backup routers in a specific virtual router:
holdoff-time
Specifies a value for the Ethernet Ring Protection (ERP) holdoff timer.
Syntax
holdoff-time time
no holdoff-time
Command Default
The default holdoff-time value is 0 milliseconds (ms).
Parameters
time
Time in ms. Range is from 0 through 10000, in intervals of 100.
Modes
ERP configuration mode
Usage Guidelines
To prevent unnecessary Signal Fail events resulting from port flapping, when a link error occurs the
event is not reported immediately. When the hold-off timer expires, ERP checks to see whether the
error still exists.
Examples
The following example configures a holdoff-time of 100 ms.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# holdoff-time 100
hop-limit
Gives the ability to change the hop limit to a lower number.
Syntax
hop-limit number
hop-limit number
Command Default
By default, there is no hop-limit configuration .
Parameters
number
Specifies the selected number of hops in the path. The range for the number of hops is 0 - 255
with a default number of 255.
Modes
MPLS LSP configuration mode (config-router-mpls-lsp-lsp_name).
Usage Guidelines
The no form of the command removes the specified number of hops and returns to the default hop
number of 255 hops.
The user can configure an interface level hop-limit for dynamic Bypass LSPs to be created
corresponding to a protected link.
Compute the dynamic bypass path, so the hop-limit is the minimum number of the backup requested
hop limit and the interface mode configured hop limit. This computed hop limit sets as the dynamic
bypass LSP hop limit during the initial creation of dynamic bypass.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example limits the CSPF to choosing a path consisting of no more than 20 hops for LSP
tunnel1 .
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp tunnel1
device(config-router-mpls-lsp-tunnel1)# hop-limit 20
The following example configures dynamic bypass MPLS Ethernet interface 0/8 s hop-limit to 5 .
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# hop-limit 5
Syntax
host-table aging-mode conversational
no host-table aging-mode conversational
Command Default
Conversational ARP/ND is disabled.
Modes
Global configuration mode
Usage Guidelines
You can change the aging-time value from the 300 second default—either before or during enablement
—by entering the host-table aging-time conversational command.
If conversational ARP/ND is not enabled, make sure that the software ARP/ND cache size is less than
the hardware profile limit.
Upon disablement, the conversational ARP/ND timers no longer apply: All current entries become
permanent as do all new entries.
Examples
The following example enables conversational ARP/ND.
device# configure terminal
device(config)# host-table aging-mode conversational
Syntax
host-table aging-time conversational seconds
no host-table aging-time conversational
Command Default
If conversational ARP/ND is enabled (by entering the host-table aging-mode
conversational command), the default aging-time value is 300 seconds.
Parameters
seconds
Specifes the aging-time value for conversational ARP/ND. Values range from 60 through 100000
seconds. The default is 300.
Modes
Global configuration mode
Usage Guidelines
You can modify the aging-time value either before or after enabling conversational ARP/ND.
Pre-existing entries age out using the old configured value. A changed age-time configuration applies
only entries added following the change.
To restore the default aging-time value of 300 seconds, enter the no form of this command.
Examples
The following example sets the aging-time value to 600 seconds and then enables conversational
ARP/ND.
device# configure terminal
device(config)# host-table aging-time conversational 600
device(config)# host-table aging-mode conversational
hostname disable
Disables Intermediate System-to-Intermediate System (IS-IS) name mapping on a device.
Syntax
hostname disable
no hostname disable
Command Default
Disabled.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The implementation of IS-IS supports RFC 2763, which describes a mechanism for mapping IS-IS
system IDs to the host names of the devices with those IDs. For example, if you set the host name on
the device to "IS-IS Router 1", the mapping capability uses this name instead of the IS-IS system ID of
the device in the output of the following commands:
• show isis database
• show isis interface
• show isis neighbor
Examples
The following example disables IS-IS name mapping.
device# configure terminal
device(config)# router isis
device(config-isis-router)# hostname disable
http server
Configures HTTP or HTTPS service on a device.
Syntax
http server use-vrf vrf-name shutdown
no http server use-vrf vrf-name shutdown
Parameters
use-vrf vrf-name
Specifies a user-defined VRF.
shutdown
Disables HTTP or HTTPS service.
Modes
Global configuration mode
Usage Guidelines
Use the http server command with the use-vrf parameter to enable HTTP or HTTPS service and
associate it with the specified VRF. The use-vrf parameter configures HTTP or HTTPS service for the
specified VRF only. Service for that VRF is enabled or disabled with no effect on service for other VRFs.
Use the http server command with the use-vrf and shutdown parameters to disable HTTP or
HTTPS service for the specified VRF.
Use the no http server command with the use-vrf parameter to disable HTTP or HTTPS service
and remove its association with the specified VRF. You can disable service for any VRF, including the
management VRF. Disabling service for the management VRF is allowed, but removing the server's
association with the management VRF is not allowed.
HTTPS crypto certificates are required to enable HTTPS mode. HTTPS crypto certificates determine
whether the service is HTTP or HTTPS.
Examples
The following example creates and enables HTTP or HTTPS service on a device and specifies using a
user-defined VRF (myvrf).
device# configure terminal
device(config)# http server use-vrf myvrf
The following example disables HTTP or HTTPS service (or both HTTP and HTTPS services when both
are enabled) on a device for a user-defined VRF.
device# configure terminal
device(config)# http server use-vrf myvrf shutdown
The following example enables HTTP or HTTPS service on an device for a user-defined VRF when
service is disabled.
device# configure terminal
device(config)# no http server use-vrf myvrf shutdown
The following example disables HTTP or HTTPS service on a device for a user-defined VRF and removes
its association with that VRF.
device# configure terminal
device(config)# no http server use-vrf myvrf
implicit-commit
MPLS allows the user to modify the configurable parameters for RSVP LSPs while the LSP is
operational.
Syntax
implicit-commit { all | lsp-reoptimize-timer }
no implicit-commit
Command Default
The is no implicit commit, by default.
Parameters
all
Enables an implicit commit for all triggers.
lsp-reoptimize-timer
Enables an implicit commit for reoptimizations.
Modes
MPLS policy configuration mode (config-router-mpls-policy)
Usage Guidelines
The no form of the command removes the implicit commit.
After modifying the parameters for an operational LSP, the user must execute the commit command to
apply the changes. Applying these configuration changes requires a new instance of the LSP to be
signaled with a modified or new set of parameters, also known as make-before-break. Once the new
instance of the LSP is up, the old instance is removed.
By default, if the adaptive parameters of an LSP have changed, but the changes are not yet committed,
any system-initiated make-before-break, such as an LSP re-optimization event, is ignored. To allow
changes to be automatically applied, the user can use the implicit-commit lsp-reoptimize-
timer command under the router MPLS policy command to enable certain types of events to trigger
implicit commit.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enable the LSP re-optimize timer to trigger an implicit commit.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# implicit-commit lsp-reoptimize-timer
Syntax
import l2vpn evpn reoriginate
no import l2vpn evpn reoriginate
Modes
Router BGP mode
• Address Family VPNv4 Unicast
• Address Family VPNv6 Unicast
Usage Guidelines
The no form of the command disables import of EVPN type-5 prefixes into VPNv4/VPNV6 and
withdraw the prefixes from the L3VPN peers.
Examples
The following example shows how to enable import of BGP type-5 prefixes(IPv6) from EVPN VXLAN
peers into BGP VPNv6.
device# configure terminal
device(config)# router BGP
device(config-bgp-router)# address-family vpnv6 unicast
device(config-bgp-vpnv6u)# import l2vpn evpn reoriginate
Syntax
import vpnv4 unicast reoriginate
no import vpnv4 unicast re-originate
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
The no form of the command disables import of L3VPN VPNv4 prefixes into EVPN and withdraw the
prefixes from EVPN VXLAN peers.
Examples
The following example shows how to enable import of VPNv4 prefixes from L3VPN peers into BGP
EVPN.
device# configure terminal
device(config)# router BGP
device(config-bgp-router)# address-family l2vpn evpn
device(config-bgp-evpn)# import vpnv4 unicast reoriginate
Syntax
import vpnv6 unicast reoriginate
no import vpnv6 unicast re-originate
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
The no form of the command disables import of L3VPN VPNv6 prefixes into EVPN and withdraw the
prefixes from EVPN VXLAN peers.
Examples
The following example shows how to enable import of VPNv6 prefixes from L3VPN peers into BGP
EVPN.
device# configure terminal
device(config)# router BGP
device(config-bgp-router)# address-family l2vpn evpn
device(config-bgp-evpn)# import vpnv6 unicast reoriginate
import-map
Imports the target-VPN community.
Syntax
import-map route-map
no import-map route-map
Parameters
route-map
Specifies the route-map name.
Modes
VRF configuration mode
Usage Guidelines
The no form of the command removes a route-map filter.
Examples
The following example shows how to import target-VPN community.
device# configure terminal
device(config)# vrf vpn1
device(config-vrf-vpn1)# rd 1:2
device(config-vrf-vpn1)# vpn-statistics
device(config-vrf-vpn1)# address-family ipv4 unicast
device(config-vrf-vpn1-ipv4-unicast)# route-target-import 100:1
device(config-vrf-vpn1-ipv4-unicast)# import-map immport-route-map1
device# configure terminal
device(config)# vrf vpn1
device#(config-vrf-vpn1)# rd 1:2
device#(config-vrf-vpn1)# vpn-statistics
device#(config-vrf-vpn1)# address-familin ipv6 unicast
device#(config-vrf-vpn1-ipv6-unicast)# route-target-import 100:1
device#(config-vrf-vpn1-ipv6-unicast)# import-map immport-route-map1
inactivity-timer
Configures the amount of time a forwarding entry can remain unused before the device deletes it.
Syntax
inactivity-timer seconds
no inactivity-timer seconds
Command Default
The default inactive time is 180 seconds.
Parameters
seconds
Specifies the inactivity period in seconds. Valid values range from 60 through 3600 seconds.
Modes
PIM router configuration mode
Usage Guidelines
A device deletes a forwarding entry if the entry is not used to send multicast packets. The PIM inactivity
timer defines how long a forwarding entry can remain unused before the device deletes it.
The no inactivity-timer form of this command restores the default inactive time of 180 seconds.
Examples
This example configures an inactive timer of 90 seconds for IPv4 PIM.
include-all
When a device uses CSPF to calculate the path for an LSP, it takes into account the administrative group
to which an interface belongs. The user can specify which administrative groups the device can include
or exclude for this calculation.
Syntax
include-all admin_group_name | admin_group_number [ admin_group_name | ]
admin_group_number
no include-all admin_group_name | admin_group_number [ admin_group_name
| ] admin_group_number
Command Default
No interfaces are assigned to the administrative groups in the default mode.
Parameters
admin_group_name
Specifies the group, by name, the interface must be a member of. The name can be the name of
the administrative group to which an administrative group number is associated by configuration
in router MPLS mode. More than one parameter can be provided.
admin_group_number
Specifies the group, by number, the interface must be a member of. Number can be from 0 to 31
representing 32 admin groups. More than one parameter can be provided.
Modes
MPLS LSP configuration mode (config-router-mpls-lsp-lsp_name).
Usage Guidelines
Several administrative groups may be assigned to the LSP at the same time. The interface then must be
a member of both groups.
Use the interface level include-all command to configure administrative groups for dynamic
bypass LSPs to be created corresponding to a protected link.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example specifies that the interface must be a member of both the "gold " and "silver
" administrative groups to included in the path calculations for LSP tunnel1.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp tunnel1
device(config-router-mpls-lsp-tunnel1)# include-all gold silver
The following example includes administrative groups 4 and 5 on MPLS Ethernet interface 0/8.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# include-all 4 5
include-any
When a device uses CSPF to calculate the path for an LSP, it takes into account the administrative group
to which an interface belongs. The user can specify which administrative groups the device can include
or exclude for this calculation.
Syntax
include-any admin_group_name | admin_group_name[ admin_group_number |
admin_group_numbe]
no include-any admin_group_name | admin_group_name[ admin_group_number |
admin_group_numbe]
Command Default
No interfaces are assigned to the administrative groups in the default mode.
Parameters
admin_group_name
Specifies the group, by name, the interface must be a member of. The name can be the name of
the administrative group to which an administrative group number is associated by configuration
in router MPLS mode. More than one parameter can be provided.
admin_group_number
Specifies the group, by number, the interface must be a member of. Number can be from 0 to 31
representing 32 admin groups. More than one parameter can be provided.
Modes
MPLS LSP configuration mode (config-router-mpls-lsp-lsp_name )
Usage Guidelines
The no form of the command removes the assigned interface.
Use the interface level include-any command to configure administrative groups for dynamic
bypass LSPs to be created corresponding to a protected link.
Several administrative groups may be assigned to the LSP at the same time.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures LSP tunnel1 path calculations in either of the administrative groups
"gold " or "silver ".
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp tunnel1
device(config-router-mpls-lsp-tunnel1)# include-any gold silver
The following example includes any group designated as group 6 and 7 on dynamic bypass MPLS
Ethernet interface 0/8.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# include-any 6 7
ingress-tunnel-accounting
Excludes the Ethernet header (14 bytes) and Ethernet overhead (20 bytes) and CRC overhead (four
bytes) when collecting byte statistics. In other words, it counts only the size of the MPLS packet.
Syntax
ingress-tunnel-accounting
no ingress-tunnel-accounting
Command Default
The command is disabled, by default.
Modes
MPLS policy configuration mode.
Usage Guidelines
To collect accurate statistics of the bypass LSP, it is necessary to configure ingress tunnel accounting at
Label Switch Routers (LSR).
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The example below is a sample configuration for the command.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy) ingress-tunnel-accounting
init-route-calc-delay
Enables BGP delayed route calculation in specific scenarios: router reload, BGP process restart, and
admin reset of all the BGP peers in a VRF/SAFI using the clear ip | ipv6 bgp neighbor all
command. BGP BEST-path selection is delayed until BGP has the route update information from all of its
RIB-IN peers.
Syntax
init-route-calc-delay [ min-delay min_secs| max-delay max_secs | msg-
idle-time idle_secs]
no init-route-calc-delay [ min-delay | max-delay | msg-idle-time ]
Command Default
By default, BGP delayed route calculation is disabled.
Parameters
min-delay min_secs
Specifies the minimum delay time in seconds by which the BGP BEST-path selection is delayed.
Enter an integer from 60 to 900. When the delay route calculation is enabled, the default is 180
seconds.
max-delay max_secs
Specifies the maximum delay time in seconds by which the BGP BEST-path selection is delayed.
Enter an integer from 180 to 900. When the delay route calculation is enabled, the default is 300
seconds.
msg-idle-time idle_secs
Specifies the message idle time in seconds to detect the end of the learning phase for a peer. A
peer is moved out of the learning phase if the time difference between subsequent update
messages from the peer exceeds the message idle time. Enter an integer from 1 to 60. When the
delay route calculation is enabled, the default is 2 seconds.
Modes
BGP configuration mode
Usage Guidelines
Use the no init-route-calc-delay command to disable the delay route calculation. When an
optional keyword is include with the no form of this command, it resets the default setting for the
keyword.
If you enter the init-route-calc-delay command without any options, the default settings for
the minimum and maximum delay and message idle time are used.
TCP is the underlying transport mechanism used by BGP for propagating BGP update messages.
Optimal usage of TCP directly helps in improving BGP performance and convergence. Configuring
higher IP MTU values (4500 bytes) for the interfaces through which BGP peer IP connectivity is
established helps to select optimal MSS size for BGP TCP sessions.
Examples
The following example enables the BGP delay route calculation.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# init-route-calc-delay
The following example configures the minimum delay time to 200 seconds.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# init-route-calc-delay min-delay 200
insight enable
Configures a port-channel as an insight interface.
Syntax
insight enable
no insight enable
Command Default
Insight is not enabled on the port-channel.
Modes
Interface subtype configuration mode
Usage Guidelines
Use the no form of this command to disable an insight interface on the port-channel.
The connector must be enabled to support the insight interface, by means of the insight mode
command.
Examples
This example enables an insight interface on a connector.
device# configure terminal
device(config)# hardware
device(config-hardware)#
device(config-hardware)# connector 0/48
device(config-connector-0/48)# insight mode
This example uses the insight enable command to enable an insight interface on a port-channel.
device# configure terminal
device(config)# interface port-channel 33
device(config-Port-channel-33)# insight enable
no shutdown
This example uses the show interface port-channel and show port-channel commands
to confirm the configuration.
device# show interface port-channel 33
Port-channel 22 is up, line protocol is up
Hardware is AGGREGATE, address is 609c.9f5a.4558
Current address is 609c.9f5a.4558
Interface index (ifindex) is 671088673
Minimum number of links to bring Port-channel up is 1
MTU 1548 bytes
LineSpeed Actual : 10000 Mbit
insight mode
Enables an insight interface on connector.
Syntax
insight mode
no insight mode
Command Default
By default, the connector is initialized as a regular user port. Insight mode is not enabled by default.
Modes
Hardware configuration mode for a connector
Usage Guidelines
This command enable an insight interface for a port-channel.
The insight functionality supports TPVM. To enable it, a pre-designated connector needs to be
configured as insight mode before enabling the insight interface (0/125) for a port-channel. The insight
mode conversion is dynamic, therefore no switch reboot is required.
When the connector is configured as insight mode, the original Ethernet user interface is deconfigured
and deleted, and the insight interface 0/125 is created automatically.
Use the no form of this command to disable the insight interface and convert the connector to a regular
port.
Examples
This example enables insight mode on connector 0/48 of SLX9540.
device(config)# hardware
device(config-hardware)#
device(config-hardware)# connector 0/48
device(config-connector-0/48)# insight mode
This example uses the insight enable command to enable an insight interface on a port-channel.
The insight interface 0/125 is then added to this port-channel.
device# configure terminal
device(config)# interface port-channel 33
device(config-Port-channel-33)# insight enable
device(config-Port-channel-33)# no shutdown
install-igp-cost
Configures the device to use the IGP cost instead of the default BGP Multi-Exit Discriminator (MED)
value as the route cost when the route is added to the Routing Table Manager (RTM).
Syntax
install-igp-cost
no install-igp-cost
Modes
BGP configuration mode
Usage Guidelines
By default, BGP uses the BGP MED value as the route cost when the route is added to the RTM. Use this
command to change the default to the IGP cost.
Examples
The following example configures the device to compare MEDs.
instance
Maps a VLAN to a Multiple Spanning Tree Protocol (MSTP) instance. You can group a set of VLANs to an
instance.
Syntax
instance instance_id [ vlan vlan_id | priority priority_id ]
no instance
Command Default
The priority value is 32768.
Parameters
instance_id
Specifies the MSTP instance. Valid values range from 1 through 31.
vlan vlan_id
Specifies the VLAN to map an MSTP instance. Refer to the Usage Guidelines.
priority priority_id
Specifies the priority for the specified instance. Valid values range from 0 through 61440. The
priority values can be set only in increments of 4096.
Modes
Spanning tree MSTP configuration mode
Usage Guidelines
The following rules apply:
• VLANs must be created before mapping to instances.
• The VLAN instance mapping is removed from the configuration if the underlying VLANs are deleted.
Enter no instance to remove the VLAN mapping from the MSTP instance.
Caution
This command can be used only after the VLAN is defined.
Examples
To map a VLAN to an MTSP instance:
interface ethernet
Configures an Ethernet interface.
Syntax
interface ethernet slot/port
no interface ethernet
Command Default
No Ethernet interface is configured.
Parameters
slot/port
Specifies an interface name in slot/port format. Separate multiple ports with a comma. Use a
hyphen (-) to indicate a range of ports. For example, 0/1-3,5,7-9 or 0/49:1-2,4. The maximum
number of characters is 253.
Modes
Global configuration mode
Usage Guidelines
All interfaces in a range must use the same speed.
If the breakout mode command has been configured on the port, the breakout ports of the Ethernet
interface appear after the slot and port as breakout ports 1 through 4. For example, the breakout
interfaces of connector 0/25 have the following naming convention:
interface ethernet 0/25:1
interface ethernet 0/25:2
interface ethernet 0/25:3
interface ethernet 0/25:4
To configure Redundant Management, configure a physical port on the device (for example, 0/15) as a
standby management port.
Examples
The following example configures breakout ports of Ethernet interface 0/1:
device# configure terminal
device(config)# interface ethernet 0/1:1
device(config)# interface ethernet 0/1:2
device(config)# interface ethernet 0/1:3
device(config)# interface ethernet 0/1:4
The following example configures port 0/15 as the redundant management port:
device# configure terminal
device(config)# interface ethernet 0/15
device(conf-if-eth-0/15)# redundant-management enable
interface loopback
Configures a loopback interface.
Syntax
interface loopback port_number
no interface loopback port_number
Command Default
A loopback interface is not configured.
Parameters
port_number
Specifies the port number for the loopback interface. Range is 1 through 255.
Modes
Global configuration mode
Usage Guidelines
A loopback is a logical interface traditionally used to ensure stable routing operations.
Use the no form of this command to remove the specified loopback interface.
The following restrictions apply when the loopback interface is part of an active VXLAN overlay
gateway. These restrictions are enforced to maintain consistency across the gateway.
• The loopback interface cannot be deleted.
• The IPv4 address cannot be changed.
• The VRF instance cannot be changed.
You must first use the no activate command in VXLAN overlay gateway configuration mode to
modify the loopback interfaces. .
Use the no form of this command with a port parameter to remove the specified loopback interface.
Examples
The following example creates a loopback interface with a port number of 25.
device# configure terminal
device(config)# interface loopback 25
device(config-Loopback-25)#
interface management
Accesses management configuration mode.
Syntax
interface management mgmt-id
Parameters
mgmt-id
Specifies the management ID. The only supported value is 0.
Modes
Global configuration mode
Usage Guidelines
The mode allows you to configure the management interface.
Examples
The following example accesses management mode.
device# configure terminal
device(config)# interface management 0
device(config-Management-0)#
interface port-channel
Creates and configures a port-channel interface.
Syntax
interface port-channel number
no interface port-channel number
Command Default
No port-channel interface is configured.
Parameters
number
Specifies a port-channel.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to disable the interface.
Note
• For the 1U SLX 9740-40, the number of LAGs will be 77, where:
◦ 76 are the front end ports (all breakouts)
◦ 1 (insight port)
• For the 2U SLX 9740-80, the number of LAGs will be 153. where:
◦ 152 are the front end ports (all breakouts)
◦ 1 (insight port)
( SLX 9540 and SLX 9640) Maximum numbers of port-channel IDs and links per port-channel vary with
device and LAG profile, as follows:
Table 11: Port-channel scale for SLX 9540 and SLX 9640 devices
Device or series LAG profile Supported port-channel Maximum links per port-
IDs channel
( SLX 9150 and SLX 9250) Maximum numbers of port-channel IDs and links per port-channel vary only
with device, as follows:
Table 12: Port-channel support for SLX 9150 and SLX 9250 devices
Note
Non-default LAG profiles are not supported for the SLX 9150 and SLX 9250 devices.
Examples
To configure a port-channel interface:
device# configure terminal
device(config)# interface port-channel 10
device(config-Port-channel-10)#
interface (telemetry)
Specifies monitored interfaces for the interface telemetry profile-type.
Syntax
interface interface
no interface interface
Command Default
No interfaces are defined and the profile is inactive.
Parameters
interfaces
Specifies the profile interfaces, up to 1000 characters. The format options are:
• slot/port, for example, 0/1
• slot/port1-port2, for example, 0/1-5
• slot/port1:breakout1-breakout2, for example, 0/4:3-4
Modes
Telemetry profile configuration mode
Usage Guidelines
If you do not specify at least one interface, the profile has no effect.
For other telemetry profiles that require you to configure interfaces, the syntax of this command is
interface-range.
To remove interfaces from the interface profile, use the no form of this command.
Examples
The following example configures the interfaces to be used in the interface streaming profile.
device# configure terminal
device(config)# telemetry profile interface default_interface_statistics
device(config-interface-default_interface_statistics)# interface 1/2-3,2/1-3,3/6-9
interface ve
Configures a virtual Ethernet (VE) interface.
Syntax
interface ve vlan_id
no interface ve vlan_id
Parameters
vlan_id
Specifies the corresponding VLAN that must already be created before the VE interface can be
created. Refer to the Usage Guidelines. Separate multiple IDs with a comma. Use a hyphen (-) to
indicate a range of IDs. For example, 1-3,5,7-9.
Modes
Global configuration mode
Usage Guidelines
Before you can configure a VE interface, you must create a corresponding VLAN. The VE interface must
use the corresponding VLAN ID.
Examples
This example creates a VE interface with the VLAN ID of 56. This example assumes that VLAN 56 has
already been created.
device# configure terminal
device(config)# interface ve 56
device(config-Ve-56)#
interval
For an implementation of an event-handler profile, specifies the number of seconds between iterations
of an event-handler action, if triggered.
Syntax
interval seconds
no interval
Command Default
Iterations occur with no interval between them.
Parameters
seconds
Specifies the number of seconds between iterations of an event-handler action, if triggered.
Valid values are 0 or a positive integer.
Modes
Event-handler activation mode
Usage Guidelines
The interval command is effective only if the iterations value is non-zero.
The no form of this command resets the interval setting to the default 0 seconds.
Examples
The following example sets the number of iterations to 3 and specifies an interval of 10 seconds
between each iteration.
device# configure terminal
device(config)# event-handler activate eventHandler1
device(config-activate-eventHandler1)# iterations 3
device(config-activate-eventHandler1)# interval 10
interval (telemetry)
Configures the interval delay for telemetry data streaming.
Syntax
interval seconds
no interval
Command Default
For the interface profile-type, the default value is 30 seconds.
For the MPLS profile-types, the default value is 240 seconds. (These profile types are supported only on
SLX 9540 and SLX 9640 devices.)
For the queue profile-types, the default value is 300 seconds. (These profile types are supported only
on SLX 9540 and SLX 9640 devices.)
Parameters
seconds
( SLX 9150 and SLX 9250 devices) Specifies the streaming interval. For the interface profile-
type, values range from 10 through 3600 seconds, in five-second increments. For the system-
utilization profile-type, values range from 60 through 14400 seconds, in five-second
increments.
( SLX 9540 and SLX 9640 devices) Specifies the streaming interval. The range of values, in five-
second increments:
• For the interface profile-type, from 10 through 3600 seconds.
• For the system-utilization profile-type, from 60 through 14400 seconds.
• For the MPLS profile-types, from 240 through 3600 seconds.
• For the queue profile-types, from 240 through 2400 seconds.
Modes
Telemetry profile configuration mode
Usage Guidelines
To reset the interval to the default value, use the no interval command.
Examples
Example of setting the interval in an interface configuration for an interface profile.
device# configure terminal
device(config)# telemetry profile interface default_interface_statistics
device(interface-default_interface_statistics)# interval 2000
Example of setting the interval for a MPLS Traffic statistics data streaming configuration using the mpls-
traffic-lsp profile.
device# configure
device(config)# telemetry profile mpls-traffic-lsp default_mpls_traffic_lsp_statistics
device(config-telemetry-profile)# interval 340
ip access-group
Applies rules specified in an IPv4 access control list (ACL) to traffic entering or exiting an interface.
Syntax
ip access-group ACLname { in | out }
no ip access-group ACLname { in | out }
Parameters
ACLname
Specifies the name of the standard or extended IPv4 access list.
in
Applies the ACL to incoming switched and routed traffic.
out
Applies the ACL to outgoing routed and (for SLX 9150 and SLX 9250 devices) also to switched
traffic.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to apply an IPv4 ACL to one of the following interface types:
• User interfaces
◦ Physical Ethernet interfaces
◦ Port-channels (LAGs).
◦ Virtual Ethernet (VE) (attached to a VLAN or to a bridge domain)
• The management interface
You can apply a maximum of two ACLs to the management interface, as follows:
• One ingress IPv4 ACL
• One ingress IPv6 ACL
You can apply an ACL to multiple interfaces. And you can apply an ACL twice—ingress and egress—to a
given user interface.
Examples
The following example applies an ingress IP ACL on an Ethernet interface:
device(config)# interface ethernet 0/2
device(conf-if-eth-0/9)# ip access-group ipacl2 in
ip access-list
Creates a standard or extended IPv4 access control list (ACL). In ACLs, you can define rules that permit
or deny network traffic based on criteria that you specify.
Syntax
ip access-list { standard | extended } ACLname
no ip access-list { standard | extended } ACLname
Parameters
standard | extended
Specifies one of the following types of access lists:
standard
Contains rules that permit or deny traffic based on source addresses that you specify. The rules
are applicable to all ports of the specified addresses.
extended
Contains rules that permit or deny traffic according to source and destination addresses, as well
as other parameters. For example, you can also filter by port, protocol (TCP or UDP), and TCP
flags.
ACLname
Specifies an ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63
characters in length, and must begin with an alphanumeric character. No special characters are
allowed, except for the underscore and hyphen.
Modes
Global configuration mode
Usage Guidelines
An ACL name can be up to 63 characters long, and must begin with a–z, A–Z or 0–9. You can also use
underscore (_) or hyphen (-) in an ACL name, but not as the first character.
After you create an ACL, use the seq command to create filtering rules for that ACL.
To delete an ACL, use the no access-list command. You can delete an ACL only after you first
remove it from all interfaces to which it is applied, using the no access-group command.
Examples
The following example creates an IPv4 standard ACL.
device# configure
device(config)# ip access-list standard stdACL3
The following example creates an IPv4 extended ACL and adds rules to the ACL that filter TCP packets
to the management IP on port 22.
device# configure
device(config)# ip access-list extended management
device(config-ipacl-ext)# permit tcp x.x.x.x/24 mgt-ip eq 22
device(config-ipacl-ext)# permit tcp x.x.x.x/24 mgt-ip eq 22
device(config-ipacl-ext)# permit tcp host x.x.x.x mgt-ip eq 22
device(config-ipacl-ext)# permit tcp host x.x.x.x mgt-ip eq 22
device(config-ipacl-ext)# permit tcp host x.x.x.x mgt-ip eq 22
deny tcp any mgt-ip eq 22
The following example displays an ACL definition that supports flow based ingress miroring.
device# show access-list int eth 0/2 in
ip access-list ipl on Ethernet 0/2 at Ingress (From User)
seq 10 permit ip host 10.10.10.1 any count mirror (Active)
seq 20 permit tcp any host 15.15.15.1 count (Active)
The following example displays an ACL definition that supports flow based ingress miroring.
device# show access-list int eth 0/2 in
ip access-list ipl on Ethernet 0/2 at Ingress (From User)
seq 10 permit ip host 10.10.10.1 any count mirror (150 frames)
seq 20 permit tcp any host 15.15.15.1 count (0 frames)
ip address
Configures a primary or secondary IP address on an interface.
Syntax
ip address ip-address/mask [secondary][ospf-ignore ][ospf-passive]
no ip address [ ip-address/mask ]
Parameters
ip-address
Specifies the IP address.
mask
Specifies the mask for the associated IP subnet. Dotted-decimal notation is not supported. For
non-loopback interfaces, valid values are from 1 through 31. For loopback interfaces, the only
valid value is 32.
secondary
Specifies that the address is a secondary IP address.
ospf-ignore
Disables adjacency formation with OSPF neighbors and disables advertisement of the interface
to OSPF.
ospf-passive
Disables adjacency formation with OSPF neighbors but does not disable advertisement of the
interface to OSPF.
Modes
Interface configuration mode
Usage Guidelines
• Use this command to configure a primary or secondary IP address for an interface. You can also use
this command to prevent OSPF from running on specified subnets. Multiple primary IP addresses are
supported on an interface.
• You can use this command to configure a primary or secondary IP address for the management
interface.
• For the management interface, only one primary IP address is supported.
• A primary IP address cannot overlap a configured IP subnet.
• A primary IP address must be configured before you configure a secondary IP address in the same
subnet.
• To remove the configured static or DHCP address, enter no ip address. This resets the address
to 0.0.0.0/0.
• The no form of the command removes a specific IP address from the interface.
Gateway IPs from multiple subnets (maximum of 32) can be configured for each FVG session. Multiple
gateway IPs from the same subnet can be configured, but the number of FVG sessions for each
interface remains one. One RBridge becomes the ARP responder for all the gateway IPs configured for
the session.
All restrictions for configuring an FVG gateway also apply to multiple gateway IP addresses. If IP
conflicts are detected for any gateway IP configured on the session, the configuration is accepted with a
RASLOG, but the session is invalidated until the conflict is resolved.
Periodic gratuitous address resolution protocol (GARP), if configured, would be sent out only for the
first gateway address. When a session moves to Master, GARP is sent out for all gateway IP addresses
configured on the session.
After a downgrade to an earlier version of the OS, all gateway IP configurations are removed if multiple
gateway IPs are present. If only one gateway IP present, then the configuration is retained.
Examples
The following example configures a primary IP address on a specified Ethernet interface.
device(config)# interface ethernet 3/2
device(conf-if-eth-3/2)# ip address 10.1.1.1/24
ip address (site)
Specifies the destination IPv4 address of a tunnel for a site in a VXLAN overlay gateway configuration.
Syntax
ip address IPv4_address
no ip address [ IPv4_address ]
Parameters
IPv4_address
Specifies the IPv4 address of the destination tunnel.
Modes
Site configuration mode
Usage Guidelines
The tunnel mode and the source IP address are derived from the parent overlay gateway.
To change an IP addresses, you must first remove the existing address, by means of the no ip
address IPv4_address or the no ip address commands. This also deletes all tunnels to the
site.
Only one IPv4 address is allowed. The following IPv4 addresses are not allowed:
• Broadcast addresses (0.0.0.0 through 0.255.255.255)
• Localhost loopback addresses (127.0.0.0 through 127.255.255.255)
• Multicast addresses (224.0.0.0 through 239.255.255.255)
• Reserved addresses (240.0.0.0 through 255.255.,255.255)
Examples
The following example configures an IPv4 address of a destination tunnel for the site.
device# configure terminal
device(config)# overlay-gateway gateway1
device(config-overlay-gw-gateway1)# site mysite
device(config-site-mysite)# ip address 10.11.12.13
ip anycast-address
Configures an anycast-gateway IPv4 address on an interface, which uses the gateway IPv4 address for
the host.
Syntax
ip anycast-address IPv4-address/mask
no ip anycast-address
Command Default
No address is configured.
Parameters
IPv4-address/mask
IPv4 address and mask.
Modes
Interface configuration mode on a virtual Ethernet (VE) interface.
Usage Guidelines
Use the no form of this command to delete the configured IPv4 anycast address from the interface.
Examples
To configure an IPv4 address and mask on a virtual Ethernet (VE) interface:
device# configure terminal
device(config)# interface ve 10
device(config-Ve-10)# ip anycast-address 2.2.2.2/24
Syntax
ip arp gratuitous none
no ip arp gratuitous none
Command Default
By default, the gratuitous ARP control is enabled.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to re-enable the gratuitous ARP control.
Examples
The following example disables the gratuitous ARP control.
device# configure terminal
device(config)# ip arp gratuitous none
ip arp inspection
Enables Dynamic ARP Inspection (DAI) on a VLAN.
Syntax
ip arp inspection
no ip arp inspection
Command Default
DAI is disabled.
Modes
VLAN configuration mode
Usage Guidelines
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC
addresses are accepted only if all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an
IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
Examples
The following example creates an ARP access-list, applies it to VLAN 200, and enables DAI.
device# configure terminal
device(config)# arp access-list ARP_ACL_01
device(config-arp-acl)# permit ip host 1.1.1.1 mac host 0020.2222.2222
device(config-arp-acl)# permit ip host 1.1.1.2 mac host 0020.2222.2223
device(config-arp-acl)# exit
device(config)# vlan 200
device(conf-vlan-200)# ip arp inspection filter ARP_ACL_01
device(conf-vlan-200)# ip arp inspection
Syntax
ip arp inspection filter ACL-name
no ip arp inspection filter
Command Default
No ARP ACL is applied.
Parameters
ACL-name
Specifies which ACL is applied to the VLAN or interface.
Modes
VLAN configuration mode
Usage Guidelines
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC
addresses are accepted only if all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an
IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
For ARP Guard, this command applies an ARP ACL to a physical or port-channel interface.
The no form of the command removes the current ARP ACL from the VLAN or interface.
Examples
The following example applies an ARP ACL named ARP_ACL_01 to VLAN 200.
device# configure terminal
device(conf)# vlan 200
device(conf-vlan-200)# ip arp inspection filter ARP_ACL_01
Syntax
ip arp inspection trust
no ip arp inspection trust
Command Default
The interface is untrusted.
Modes
Interface subtype configuration mode
Usage Guidelines
This command is supported only on Layer 2 physical or port-channel interfaces.
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC
addresses are accepted only if all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an
IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
Examples
The following example configures an Ethernet interface as trusted.
device# configure terminal
device(conf)# interface ethernet 2/1
device(conf-if-eth-2/1)# ip arp inspection trust
ip arp learn-any
Enables address-resolution protocol (ARP) learning from any ARP request.
Syntax
ip arp learn-any
no ip arp learn-any
Command Default
Default ARP learning
Modes
VE configuration mode
Usage Guidelines
This command enables learning from any ARP request (not necessarily targeted to my ip address).
Examples
The following example enables learn-any on VE 100.
device# configure terminal
device(config)# interface ve 100
device(config-if-Ve-100)# ip arp learn-any
ip arp-aging-timeout
Sets how long a dynamic Address Resolution Protocol (ARP) entry stays in the ARP cache. The aging
timer is reset each time an ARP reply is received.
Syntax
ip arp-aging-timeout value
no ip arp-aging-timeout
Command Default
ARP aging timeout is globally enabled and set to 25 minutes.
Parameters
value
Specifies how long an ARP entry stays in the ARP cache. Values range from 0 through 240
minutes.
Modes
Interface subtype configuration mode
Usage Guidelines
When the device places an entry in the ARP cache, the device also starts an aging timer for the entry.
The aging timer ensures that the ARP cache does not retain learned entries that are no longer valid. An
entry can become invalid when the device with the MAC address of the entry is no longer on the
network.
Aging out affects dynamic (learned) entries only. Static entries do not age out.
You can modify the ARP aging timeout only at the interface level, but not at the global level.
The no form of the command restores the default aging timeout of 25 minutes.
Examples
The following command sets the ARP aging timeout to 100 minutes on an interface.
device(config)# interface ethernet 3/4
device(conf-if-eth-3/4)# ip arp-aging-timeout 100
The following command restores the ARP aging timeout to the default value on an interface.
device(config)# interface ethernet 3/4
device(conf-if-eth-3/4)# no ip arp-aging-timeout
Syntax
ip dhcp relay address ip-addr [ use-vrf vrf-name ]
Parameters
ip-addr
IPv4 address of the DHCP server where the DHCP client requests are to be forwarded.
use-vrf
Use this option if the VRF where the DHCP server is located is different from the VRF of the
interface where the client is connected.
vrf-name
VRF name.
Modes
Interface configuration mode
Usage Guidelines
This command uses the IPv4 address of the DHCP server where the DHCP client requests are to be
forwarded.
Enter the command while in interface configuration mode for a VE or Ethernet interface where you
want to configure the IP DHCP Relay. Configure up to sixteen DHCP server IP addresses per interface.
Use the no version of this command to remove the IP DHCP relay from the interface. If the use-vrf
option is not used, it is assumed that the DHCP server and interface where the client is connected are
on the same VRF.
Examples
To configure an IP DHCP Relay address on a Ve interface:
device# config
device(config)# interface ve 100
device(config-Ve-100)# ip dhcp relay address 3.1.2.255 use-vrf blue
Syntax
ip dhcp relay gateway ip-addr
no ip dhcp relay gateway ip-addr
Parameters
ip-addr
IPv4 gateway address of the DHCP server where the DHCP client requests are to be forwarded.
Modes
Interface configuration mode
Usage Guidelines
Use this command to configure the IP DHCP Relay on the switch Layer 3 gateway interface using the
IPv4 address of the DHCP server where the DHCP client requests are to be forwarded.
Use the no version of this command to remove the IP DHCP Relay from the interface.
Examples
To configure an IP DHCP Relay address on an interface:
device(config)# interface ethernet 0/4
ip dhcp snooping
Enables DHCP snooping globally at the device level.
Syntax
ip dhcp snooping [ binding [ mac-addr| ip-addr ] |vlan vlan-id |
interface [switchport | physical interface] ]
no ip dhcp snooping [ binding [ mac-addr| ip-addr ] |vlan vlan-id |
interface [switchport | physical interface] ]
Command Default
By default, DHCP snooping is not enabled.
Parameters
binding [ mac-addr| ip-addr ]
Specifies the MAC or IP address of the host for the entry in the binding database.
vlan vlan-id
Specifies the VLAN ID of the host for the entry in the binding database.
interface [ switchport physical interface ]
Specifies the ID of the switchport interface.
Modes
Interface configuration mode
Usage Guidelines
DHCPv4 snooping uses trusted ports that have been identified as having legitimate DHCP servers
attached. As clients communicate on the network, the device builds a binding database, which contains
the MAC address of the host, the leased IP address, the lease time, the binding type, and the VLAN
number and interface information associated with the host. The device then filters DHCP server
messages from untrusted ports to protect the integrity of legitimate DHCP servers and their operation.
Syntax
ip dhcp snooping enable
no ip dhcp snooping enable
Command Default
By default, DHCP snooping is not enabled.
Modes
Interface configuration mode
Syntax
ip dhcp snooping information option { allow-untrusted }
no ip dhcp information option { allow-untrusted }
Command Default
By default, Option-82 information is not inserted into snooping packets.
Parameters
allow-untrusted
Globally enables the "Option-82 allow untrusted" feature on the device.
Modes
Interface configuration mode
Usage Guidelines
When you run the command with the allow-untrusted option, the device accepts incoming DHCP
packets with Option-82 information on the untrusted port of the DHCP snooping-enabled VLAN.
Use the no ip dhcp snooping information option form of the command to disable the
insertion of Option-82 information into snooping packets.
Syntax
ip dhcp snooping trust
no ip dhcp snooping trust
Command Default
By default, all switchports are untrusted.
Modes
Interface configuration mode
Usage Guidelines
Use the no form of the command to revert a switch port to the untrusted state.
ip directed-broadcast
Enables directed broadcasts on an interface. A directed broadcast is an IP broadcast to all devices
within a directly attached network or subnet.
Syntax
ip directed-broadcast
no ip directed-broadcast
Command Default
Directed broadcast is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
To disable directed broadcasts on an interface, enter the no form of this command.
Examples
The following example enables directed broadcasts on an Ethernet interface.
device(config)# interface ethernet 0/2
device(config-if-eth-0/2)# ip directed-broadcast
ip dns
Configures the Domain Name System (DNS) domain name and the primary and five additional name
server IP addresses.
Syntax
ip dns { domain-name domain-name | name-server ip-addr }
ip dns name-server [ source-interface { ethernet eth-id | loopback
loopback-id | management mgmt-addr | ve ve-id } ]
ip dns name-server { ip-addr use-vrf vrf name }
no ip dns { domain-name domain-name | name-server ip-addr }
no ip dns name-server [ source-interface { ethernet eth-id | loopback
loopback-id | management mgmt-addr | ve ve-id } ]
Parameters
domain-name domain-name
Specifies the DNS domain name.
name-server ip-addr
Specifies the IPv4 or IPv6 address of the name server.
source-interface
Indicates the type of interface to use as the source interface or address.
ethernet eth-id
Specifies the Ethernet interface to use as the source interface, in slot/port format (0/1).
loopback loopback-id
Specifies the Loopback interface to use as the source interface.
management mgmt-addr
Specifies the management address (active MM or chassis IP) to use as the source address.
ve ve-id
Specifies the VE interface to use as the source interface.
use-vrf vrfname
Specifies the VRF to connect to the DNS server.
Modes
Global configuration mode
Usage Guidelines
Your first run of ip dns name-server specifies the default IP gateway address. Subsequent runs of
the ip dns name-server command specifies the secondary and other IP gateway addresses.
Name servers can only be entered or removed one at a time. The newly entered name server is
appended to the existing name server.
When a source interface is not specified, the default source is the IP address of the interface from which
the packet egresses.
If, at run time, the source interface is not up, or the IP address for the source interface was not
configured, the command behaves as though the source interface was not configured.
Use the no form of the command with the domain-name parameter to disable IP-directed
broadcasts for a specific domain.
Use the no form of the command with the name-server parameter to delete a name server
definition. You can delete one name-server at a time.
Any combination of IPv4 or IPv6 DNS name servers can be configured. You could choose to add 2 IPv6
name servers alongside 4 IPv4 name servers. However, you cannot add more than six name servers for
a domain.
If you add more than six name servers for a domain, an error message displays.
too many 'ip dns name-server', 7 configured, at most 6 must be configured
Examples
The following example configures the DNS domain name and the primary name server IP address.
device# configure terminal
device(config)# ip dns domain-name mycompany.com
device(config)# ip dns name-server 10.70.20.1
This example configures six (6) DNS name servers for the domain www.example.com. Of these six (6)
domain names, two (2) are IPv6 DNS resolvers.
device# configure terminal
device(config)# ip dns domain-name www.example.com
device(config)# ip dns name-server 10.24.15.150
device(config)# ip dns name-server 10.24.18.125
device(config)# ip dns name-server 172.26.71.80
device(config)# ip dns name-server 200:f8::ed:3000
device(config)# ip dns name-server 2001:eb::780:ff87
device(config)# ip dns name-server 10.37.89.80
ip extcommunity-list
Configures a BGP extended community filter.
Syntax
ip extcommunity-list number { deny | permit [ rt value | soo value ] reg-
expr }
no ip extcommunity-list number
Command Default
No BGP extended community filter is set.
Parameters
number
Specifies an extended community list Instance number. Range is from 0 through 99 for a
standard list (RT- or SOO-based), and from 100 through 500 for an expanded list (regular-
expression-based).
deny
Denies access for a matching condition.
permit
Permits access for a matching condition.
rt
Specifies the route target (RT) extended community.
value
This value can be one of the following formats:
• autonomous-system-number : network-number
• ip-address : network-number
soo
Specifies the site of origin (SOO) extended community.
value
This value can be one of the following formats:
• autonomous-system-number : network-number
• ip-address : network-number
reg-expr
Specifies a regular expression. For more information, see the "BGP4 Regular Expression Pattern-
matching" topic in the Extreme SLX-OS Layer 3 Routing Configuration Guide.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to delete a BGP extended community list.
Examples
The following example specifies a standard extended community list, permits a route target, and denies
a site of origin.
device# configure terminal
device(config)# ip extcommunity-list 99 permit rt 123:2
device(config)# ip extcommunity-list 99 deny soo 124:1
The following example specifies an expanded extended community list and permits a regular
expression.
device# configure terminal
device(config)# ip extcommunity-list 101 permit 100:*
Syntax
ip flowspec rules statistics [ vrf vrf-name ]
no ip flowspec rules statistics [ vrf vrf-name ]
Command Default
Flowspec statistics are disabled.
Parameters
vrf vrf-name
Name of a VRF instance.
Modes
Global configuration mode
Usage Guidelines
When statistics are enabled, they appear in the output of the show ip flowspec rules command.
Statistic Description
Matched Number of packets or bytes that match the flowspec rule
Transmitted Number of packets matching the flowspec rule that are transmitted
Dropped Number of packets matching the flowspec rule that are dropped
The no form of the command disables statistics for BGP flowspec rules.
Examples
The following example shows how to enable statistics for BGP flowspec rules.
The following example shows how to disable statistics for BGP flowspec rules in a VRF named red.
ip forward
Enables IPv4 forwarding on a physical or virtual Ethernet interface that is configured for IPv6 only.
Syntax
ip forward
no ip forward
Command Default
By default, IPv4 forwarding is disabled on physical and virtual Ethernet interfaces.
Modes
Interface subtype configuration mode
Usage Guidelines
When IPv4 forwarding is enabled on an IPv6 interface, IPv4 packets are accepted and forwarded over
the interface.
IPv4 forwarding configuration is only allowed on Layer-3 interfaces that have an IPv6 address or IPv6
address link-local configuration. IPv4 forwarding configuration is not allowed on interfaces with an
unnumbered or IPv4-address configuration. Similarly, when IPv4 forwarding is configured on an
interface, you cannot configure the interface as an unnumbered interface or with an IPv4 address.
When IPv4 forwarding is configured on an interface, you cannot delete the last IPv6 address
configuration on that interface.
The no form of the command disables IPv4 forwarding on a physical or virtual Ethernet interface.
Examples
The following example shows how to enable IPv4 forwarding on physical Ethernet interface 0/5.
device# configure terminal
device(config)# interface ethernet 0/5
device(conf-if-eth-0/5)# ip forward
The following example shows how to enable IPv4 forwarding on virtual Ethernet interface 10.
device# configure terminal
device(config)# interface ve 10
device(conf-if-ve-10)# ip forward
ip global-subnet-broadcast-acl
Applies an IP broadcast ACL (bACL) at device level.
Syntax
ip global-subnet-broadcast-acl acl-name
no ip global-subnet-broadcast-acl acl-name
Command Default
No bACL is applied at device level.
Parameters
acl-name
Specifies the standard or extended bACL.
Modes
Global configuration mode
Usage Guidelines
IP broadcast ACLs (bACLs) provide hardware-based filtering of IP subnet-based directed broadcast and
network-address traffic.
Broadcast ACLs are not supported on SLX 9150 or SLX 9250 devices.
Examples
The following example applies a bACL at device level.
device# configure terminal
device(config)# ip global-subnet-broadcast-acl bacl_10
ip icmp-fragment enable
Configures a device to drops all fragmented ICMP packets that are destined to that device.
Syntax
ip icmp-fragment enable
no ip icmp-fragment enable
Command Default
By default, a device does not drop fragmented ICP packets that are destined to itself.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to disable the feature.
Examples
The following example enables a device to drop fragmented ICMP packets.
device# configure terminal
device(config)# ip icmp-fragment enable
ip icmp rate-limiting
Limits the rate at which IPv4 Internet Control Message Protocol (ICMP) messages are sent on a network.
Syntax
ip icmp rate-limiting milliseconds
no ip icmp rate-limiting
Command Default
By default, rate limiting is enabled on the management port, but is disabled on the other ports.
Parameters
milliseconds
Time interval per ICMP packet in milliseconds. The range is from 0-4294967295. The default is
1000.
Modes
Interface configuration mode
Usage Guidelines
This is an interface-specific configuration.
The no form of the command will revert to the default setting. Set the interval to 0 to disable IPv4 ICMP
rate-limiting.
Examples
The following example enables IPv4 ICMP rate-limiting on an Ethernet interface.
device(config)# interface ethernet 3/5
device(conf-int-eth-3/5)# ip icmp rate-limiting 10000
ip icmp redirect
Enables IPv4 Internet Control Message Protocol (ICMP) Redirect messages, which request that packets
be sent on an alternative route.
Syntax
ip icmp redirect
no ip icmp redirect
Command Default
ICMP redirect messages are enabled by default.
Modes
Interface configuration mode
Usage Guidelines
The no form of the command disables IPv4 ICMP Redirect messages.
You can disable ICMP redirect messages when traffic needs to be routed into and out of the same Layer
3 interface. Disabling redirects helps prevent the handling of production traffic in the CPU of Layer 3
switches and routers.
Examples
The following example enables IPv4 ICMP Redirect messages on an Ethernet interface.
device(config)# interface ethernet 2/5
device(conf-int-eth-2/5)# ip icmp redirect
ip icmp unreachable
Enables a Layer 3 device to respond to IPv4 ICMP unreachable messages.
Syntax
ip icmp unreachable
no icmp unreachable
Command Default
By default, the device does not respond to ICMP unreachable notifications.
Modes
Interface configuration mode
Usage Guidelines
Use the no form of the command to disable the feature.
Examples
The following example enables a device to respond to ICMP unreachable notifications to the indicated
source.
device# configure terminal
device(config)# interface ve 2
device(config-int-ve-2)# ip address 2.1.1.1/24
device(config-int-ve-2)# ip icmp unreachable
ip igmp immediate-leave
Removes a group from the IGMP table immediately following receipt of a Leave Group request.
Syntax
ip igmp immediate-leave
no ip igmp immediate-leave
Command Default
This command is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
This command treats an interface as if it had one multicast client, so that the receipt of a Leave Group
request on the interface causes the group to be removed immediately from the multicast database.
Examples
To configure an Ethernet interface to remove a group from the IGMP table immediately following receipt
of a Leave Group request:
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# ip igmp immediate-leave
ip igmp last-member-query-interval
Sets the IGMP last-member query interval for an interface.
Syntax
ip igmp last-member-query-interval milliseconds
no ip igmp last-member-query-interval
Command Default
By default, the query interval is 1000 milliseconds.
Parameters
milliseconds
Response time in milliseconds. Range is from 100-25500 milliseconds. The default is 1000.
Modes
Interface subtype configuration mode
Usage Guidelines
The last-member query interval is the time in milliseconds that the IGMP router waits to receive a
response to a group-specific query message, including messages sent in response to a host-leave
message.
Examples
To set the last-member query interval to 1500 milliseconds on an interface:
ip igmp query-interval
Sets the IGMP query interval for an interface.
Syntax
ip igmp query-interval seconds
no ip igmp query-interval seconds
Command Default
See Parameters.
Parameters
seconds
Response time in seconds. Range is from 1 through 18000 seconds. The default is 125.
Modes
Interface subtype configuration mode
Usage Guidelines
The query interval is the amount of time between IGMP query messages sent by the device.
Examples
To set the query interval to 500 seconds on an interface:
ip igmp query-max-response-time
Sets the maximum response time for IGMP queries for an interface.
Syntax
ip igmp query-max-response-time seconds
no ip igmp query-max-response-time
Command Default
The default is 10 seconds.
Parameters
seconds
Response time in seconds. Range is from 1 through 25 seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
When a host receives the query packet, it starts counting to a random value, less than the maximum
response time. When this timer expires, the switch (host) replies with a report, provided that no other
host from the same group has responded yet.
Examples
To set the maximum response time to 20 seconds:
ip igmp router-alert-check-disable
Disables the snooping check for the presence of the router alert option.
Syntax
ip igmp router-alert-check-disable
no ip igmp router-alert-check-disable
Command Default
By default, the snooping check is enabled.
Modes
Global configuration mode
Usage Guidelines
IGMP snooping checks for the presence of the router alert option in the IP packet header of the IGMP
message. Packets that do not include this option are dropped.
Examples
The following example disables the snooping router alert check globally.
Syntax
ip igmp snooping enable
no ip igmp snooping enable
Command Default
By default, snooping is enabled.
Modes
VLAN configuration mode
Usage Guidelines
IGMP snooping allows a network device to listen in on the IGMP conversation between hosts and
routers. By listening to these conversations, the switch maintains a map of which links need which IP
multicast streams. Multicasts may be filtered from the links which do not need them.
Examples
To enable IGMP on a VLAN:
device(config)# vlan 1
device(config-Vlan-1)# ip igmp snooping enable
Syntax
ip igmp snooping fast-leave
no ip igmp snooping fast-leave
Command Default
By default, fast-leave processing is enabled.
Modes
VLAN configuration mode.
Usage Guidelines
Use the no ip igmp snooping fast-leave form of the command to disable this function.
Examples
To enable snooping fast-leave for a specific VLAN:
device(config)# vlan 1
device(config-Vlan-1)# ip igmp snooping fast-leave
Syntax
ip igmp snooping last-member-query-interval value
no ip igmp snooping last-member-query-interval value
Command Default
The default is 1000 ms.
Parameters
value
Sets the value in milliseconds. The range is 100 to 25500 milliseconds.
Modes
VLAN configuration mode
Usage Guidelines
When a leave is received, a group-specific query is sent. Last member query interval configuration
controls the time interval between last member queries sent.
Examples
The following example sets the IGMP snooping last member query interval.
device(config)# vlan 1
device(config-Vlan-1)# ip igmp snooping last-member-query-interval 2000
Syntax
ip igmp snooping mrouter interface { ethernet slot/port | port-channel
interface number }
no ip igmp snooping mrouter interface { ethernet slot/port | port-channel
interface number }
Command Default
By default, a VLAN port member is not a multicast router interface.
Parameters
ethernet slot/port
Specifies a valid port number.
port-channel interface number
Specifies the interface is a port-channel.
Modes
VLAN configuration mode
Usage Guidelines
A multicast router interface faces toward a multicast router or other Internet Group Management
Protocol (IGMP) querier.
Examples
The following example configures a VLAN port member to be a multicast router interface.
device(config)# vlan 1
device(config-Vlan-1)# ip igmp snooping mrouter interface ethernet 1/1
Syntax
ip igmp snooping querier enable
no ip igmp snooping querier enable
Command Default
By default, the IGMP snooping querier is enabled.
Modes
VLAN configuration mode
Usage Guidelines
Multicast routers use IGMP snooping to learn which groups have members on their attached physical
networks. The snooping querier sends IGMP queries to trigger IGMP responses from devices that are to
receive IP multicast traffic. The IGMP snooping querier receives these responses and maps the
appropriate forwarding addresses.
The no ip igmp snooping querier enable form of the command disables the IGMP snooping
querier.
Examples
The following example enables the IGMP snooping querier on a VLAN.
device(config)# vlan 1
device(config-vlan-1)# ip igmp snooping querier enable
Syntax
ip igmp snooping query-interval seconds
no ip igmp snooping query-interval seconds
Command Default
The query interval is enabled by default with a value of 125 seconds.
Parameters
seconds
Sets the IGMP snooping query interval in seconds. The range is 1-18000 seconds.
Modes
VLAN configuration mode
Usage Guidelines
The snooping query interval is the frequency with which the device sends group membership queries.
Examples
The following example sets the IGMP snooping query interval.
device(config)# vlan 1
device(config-vlan-1)# ip igmp snooping query-interval 200
Syntax
ip igmp snooping query-max-response-time seconds
no ip igmp snooping query-max-response-time seconds
Command Default
The maximum response time is enabled by default with a value of 10 seconds.
Parameters
seconds
Specifies the IGMP snooping query maximum response time in seconds. The range is 1-25
seconds.
Modes
VLAN configuration mode
Usage Guidelines
The IGMP snooping query maximum response time is the number of seconds that a device wait sfor an
IGMP (V1 or V2) response from an interface before concluding that the group member on that interface
is down and removing it from the group.
Examples
The following example sets the IGMP snooping query max response time.
device(config)# vlan 1
device(config-Vlan-1)# ip igmp snooping query-max-response-time 15
Syntax
ip igmp snooping static-group { ip-address } {interface ethernet/port-
channel }
no ip igmp snooping static-group { ip-address } {interface ethernet/port-
channel }
Command Default
By default, an interface in a VLAN is not a static member of a multicast group.
Parameters
ip-address
Specifies the multicast address to be joined in A.B.C.D format.
interface
Specifies the interface.
ethernet/port-channel
Specifies the interface type.
Modes
VLAN configuration mode
Usage Guidelines
A snooping-enabled VLAN cannot forward multicast traffic to ports that do not receive IGMP
membership reports. If clients cannot send reports, you can configure a static group which applies to
specific ports. The static group allows packets to be forwarded to the static group ports even though
they have no client membership reports.
Examples
The following example configures a static group for an Ethernet interface.
device# configure terminal
device(config)# vlan 10
device(config-vlan-10)# ip igmp snooping static-group 225.0.0.1 interface ethernet 6/15
Syntax
ip igmp snooping version [1|2|3]
no ip igmp snooping version
Command Default
By default, snooping uses IGMP version 2.
Parameters
1|2 |3
Specifies the version of IGMP that you want to use.
Modes
VLAN configuration mode
Usage Guidelines
The no ip igmp snooping version form of the command resets IGMP to version 2.
Examples
The following example sets the version to 3 for a VLAN.
device# configure terminal
device(config)# vlan 10
device(config-vlan-10)# ip igmp snooping version 3
ip igmp ssm-map
Enables the IGMPv2 Source Specific Multicast mapping.
Syntax
ip igmp ssm-map [ASCII string| enable source-address]
no ip igmp ssm-map [ASCII string | enable source-address]
Parameters
ASCII string
Specifies the prefix list name.
enable source-address
Specifies the source address.
Modes
Global configuration mode
Usage Guidelines
A prefix list is used for SSM mapping with permit clauses.
Examples
The following example enables the SSM mapping for IGMPv2 and configures an SSM map at the global
level.
device(config)# ip igmp ssm-map enable
device(config)# ip igmp ssm-map ssm-map-230-to-232 203.0.0.10
device(config)# ip igmp ssm-map ssm-map-233-to-234 204.0.0.10
The following example enables the SSM range configuration at the router PIM level.
device(config)# router pim
device(config-pim-router)# ssm-enable range PL_ssm_range -230-to-234
The following example shows a prefix list configuration for the SSM range.
device(config)# ip prefix-list PL_ssm_range seq 5 permit 230.0.0.0/8
device(config)# ip prefix-list PL_ssm_range seq 10 permit 231.0.0.0/8
device(config)# ip prefix-list PL_ssm_range seq 10 permit 232.0.0.0/8
device(config)# ip prefix-list PL_ssm_range seq 10 permit 233.0.0.0/8
device(config)# ip prefix-list PL_ssm_range seq 10 permit 234.0.0.0/8
The following example shows a prefix list configuration for an SSM map.
device(config)# ip prefix-list ssm-map-230-to-232 seq 5 permit 230.0.0.0/8
device(config)# ip prefix-list ssm-map-230-to-232 seq 10 permit 231.0.0.0/8
device(config)# ip prefix-list ssm-map-230-to-232 seq 15 permit 232.0.0.0/8
ip igmp static-group
Configures the IGMP static group membership entries for a specific interface.
Syntax
ip igmp static-group A.B.C.D
no ip igmp static-group A.B.C.D
Parameters
A.B.C.D
Specifies the group address, as a subnet number in dotted decimal format (for example,
10.0.0.1), as the allowable range of addresses to be included in the multicast group.
Modes
Interface subtype configuration mode
Usage Guidelines
Use IGMP static group membership to test multicast forwarding without a receiver host. Traffic is
forwarded to an interface without the need to receive membership reports from host members. Packets
to the group are fast-switched out of a specific interface. Static group membership entries are
automatically added to the IGMP cache and the PIM mcache table.
Examples
The following example creates a static multicast group for an interface.
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# ip igmp static-group 225.0.0.10
ip igmp version
Specifies the IGMP version on a device.
Syntax
ip igmp version version-number
no ip igmp version version-number
Command Default
IGMP Version 2 is enabled.
Parameters
version-number
Specifies the version number: 1, 2, or 3. Version 2 is the default.
Modes
Interface configuration mode
Usage Guidelines
The no form of this command restores the default; IGMP Version 2 is enabled.
Examples
The following example, in interface configuration mode, enables IGMP Version 3 for a physical port.
Syntax
ip interface loopback loopback_id
no ip interface loopback loopback_id
Parameters
loopback_id
Specifies a loopback interface. Range is from 1 through 255.
Modes
Overlay gateway configuration mode
Usage Guidelines
Use the no form of this command to delete the interface from the gateway.
Examples
The following example configures a loopback interface to the overlay gateway instance.
device# configure terminal
device(config)# overlay-gateway gateway1
device(config-overlay-gw-gateway1)# ip interface loopback 10
ip irdp
Enables IPv4 ICMP Router Discovery Protocol.
Syntax
ip irdp
no ip irdp
Command Default
By default, the ICMP Router Discovery Protocol is not enabled.
Modes
Interface configuration mode
Usage Guidelines
Routers use the IPv4 ICMP Router Discovery Protocol to announce their presence to other systems in
the subnet. Hosts use the protocol to dynamically discover IPv4 routers in the same subnet.
The protocol is disabled by default on Layer 3 interfaces. Use the ip irdp command to enable the
protocol at the interface level.
Examples
This example enables the IPv4 ICMP Router Discovery Protocol on Ethernet interface 0/2.
device# configure terminal
device(config)# interface ethernet 0/2
device(config-if-eth-0/2)# ip irdp
ip large-community-list extended
Configures a BGP Large Community access control list (ACL), specifies the large-community name, and
specifies whether to permit or deny traffic, including through the use of a regular expression.
Syntax
ip large-community-list extended large-community-list-name [ seq seq ]
{ deny | permit } string
no ip large-community-list extended large-community-list-name [ [ seq
seq ] { deny | permit } string ]
Command Default
No extended large-community list is configured.
Parameters
large-community-list-name
Specifies an ACL, from 1 through 32 ASCII characters in length.
seq seq-value
Specifies a sequence value. Valid values range from 1 through 65535.
deny
Denies a matching pattern based on a regular expression string.
permit
Permits a matching pattern based on a regular expression string.
string
A regular expression. Range is from 1 through 32 ASCII characters.
Modes
Global configuration mode
Usage Guidelines
Unlike a standard large-community list, this command does accept a regular expression.
Examples
The following example creates an extended community list.
device# configure terminal
device(config)# ip large-community-list extended lc-acl-ext-1 seq 10 permit _4567*
ip large-community-list standard
Configures a BGP Large-Community access control list (ACL), specifies the large-community number or
type, and whether to permit or deny traffic.
Syntax
ip large-community-list standard large-community-list-name [ seq seq-
value ] { deny | permit } ADMIN:OPER1:OPER2
no ip large-community-list standard large-community-list-name [ [ seq
seq-value ]{deny | permit } ADMIN:OPER1:OPER2 ]
Command Default
No large-community ACL is configured.
Parameters
large-community-list-name
Range is from 1 through 32 ASCII characters.
deny
Denies a matching pattern based on a large community pattern specified in the list.
permit
Permits a matching pattern based on a large community pattern specified in the list.
seq seq-value
Specifies a sequence value. Valid values range from 1 through 65535.
ADMIN
A four-octet namespace identifier for a BGP Large-Communities Global Administrator.
OPER1
A four-octet operator-defined value for BGP Large-Communities Local Data Part 1.
OPER2
A four-octet operator-defined value for BGP Large-Communities Local Data Part 2.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to remove the BGP Large-Community ACL.
There are two ways to delete a filter from the list. The first is by using the sequence number parameter
no ip large-community-list standard large-community-list-name seq seq-
value. The second is by executing the syntax no ip large-community-list standard
large-community-list-name , resulting in all filters within the large-community list container,
being removed from the configuration database.
Examples
The following example creates a standard large-community list.
device# configure terminal
device(config)# ip large-community-list standard lc-acl-1 seq 10 permit 64497:1:528
ip mtu
Sets the IP maximum transmission unit (MTU) globally or on an interface.
Syntax
ip mtu size
no ip mtu
Command Default
The default IP MTU size is 1500 bytes.
Parameters
size
Specifies the size of the IP MTU globally or the interface. Enter an integer from 1300 through
9194 bytes.
Modes
Global configuration mode
Usage Guidelines
The no form of the command reverts the MTU size to the default value.
Using the no form of this command in global configuration mode resets the default value on all
interfaces except the interfaces that you manually configured with MTU values.
When you change the IP MTU size globally, the change is applied to all Ethernet and VE interfaces on
the device. However, it does not change a configured interface MTU value. The configured interface
value takes precedence over the configured global MTU value.
The show running-config command displays the the MTU size when it is not the default value. If
you change the global MTU size and do not change the interface MTU size, the show running-
config command does not display the global MTU value at the interface level.
If the interface is part of a VE, change the IPv4 MTU only at the VE interface and not at the physical
port. All member ports of a VE inherit the VE-interface IPv4 MTU value.
Examples
The following example sets the IP MTU to 2000 bytes on the specified Ethernet interface.
device# configure terminal
device(config)# interface ethernet 2/9
device(conf-if-eth-2/9)# ip mtu 2000
ip option disable
Blocks packets that have IP options.
Syntax
ip option disable
no ip option disable
Command Default
By default, packets with IP options are not blocked.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to unblock packets that have IP options.
Examples
The following example blocks packets that have IP options.
device# configure terminal
device(config)# ip option disable
ip ospf active
Sets a specific OSPF interface to active.
Syntax
ip ospf active
Modes
Interface subtype configuration mode
Usage Guidelines
Use the ip ospf active command on each interface participating in adjacency formation. This
command overrides the global passive setting on that interface, and enables transmission of OSPF
control packets.
Examples
The following example sets a specific OSPFv2 Ethernet interface to active.
ip ospf area
Enables OSPFv2 on an interface.
Syntax
ip ospf area area-id | ip-addr
no ip ospf area
Command Default
Disabled.
Parameters
area-id
Area ID in decimal format. Valid values range from 1 through 2147483647.
ip-addr
Area ID in IP address format.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command disables OSPFv2 on the interface.
Examples
The following example enables a configured OSPFv2 area named 1 on a specific OSPFv2 virtual Ethernet
(VE) interface.
ip ospf auth-change-wait-time
Configures authentication-change hold time.
Syntax
ip ospf auth-change-wait-time wait-time
no ip ospf auth-change-wait-time
Command Default
Wait time is 300 seconds
Parameters
wait-time
Time before an authentication change takes place. Valid values range from 0 to 14400 seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset the authentication change hold time for the interface to which you are
connected.
OSPFv2 provides graceful authentication change for the following types of authentication changes:
Changing authentication methods from one of the following to another of the following:
• Simple text password
• MD5 authentication
• No authentication
The no form of the command resets the wait time to the default of 300 seconds.
Examples
The following example sets the wait time to 400 seconds on a specific OSPF virtual Ethernet (VE)
interface.
ip ospf authentication-key
Configures simple password-based authentication for OSPF.
Syntax
ip ospf authentication-key password
no ip ospf authentication-key
Command Default
Authentication is disabled.
Parameters
password
OSPF processes password as a plain text password.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset simple password-based authentication on the OSPFv2 interface to
which you are connected. The no form of the command disables OSPFv2 authentication.
Examples
The following example configures an authentication key for an OSPF virtual Ethernet (VE) interface.
ip ospf bfd
Enables Bidirectional Forwarding Detection (BFD) on a specific OSPFv2 interface.
Syntax
ip ospf bfd
no ip ospf bfd
Modes
Interface subtype configuration mode
Usage Guidelines
BFD sessions are initiated only if BFD is also enabled globally using the bfd command in OSPF router
configuration mode. If BFD is disabled using the no bfd command in OSPF router configuration mode,
BFD sessions on specific OSPFv2 interfaces are deregistered.
The no form of the command removes all BFD sessions from a specified interface.
Examples
The following example enables BFD on an OSPF Ethernet interface.
The following example disables BFD on an OSPF virtual Ethernet (VE) interface.
ip ospf cost
Configures cost for a specific interface.
Syntax
ip ospf cost value
no ip ospf cost
Command Default
Cost value is 1.
Parameters
value
Cost value. Valid values range from 1 through 65535. The default is 1.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset the OSPFv2 cost on the interface. If the cost is not configured with
this command, OSPFv2 calculates the value from the reference and interface bandwidths.
Examples
The following example sets the cost to 520 on a specific Loopback interface.
ip ospf database-filter
Configures filters for different types of outgoing Link State Advertisements (LSAs).
Syntax
ip ospf database-filter { all-external | all-summary-external { allow-
default-and-type-4 | allow-default-out | out } }
ip ospf database-filter all-out
no ip ospf database-filter all-external
no ip ospf database-filter all-out
no ip ospf database-filter all-summary-external
Command Default
All filters are disabled.
Parameters
all-external
Blocks all external LSAs.
all-summary-external
Blocks all summary (Type 3) and external (type 5) LSAs.
allow-default-and-type-4
Allows default-route LSAs and Type 4 LSAs, but block all other LSAs.
allow-default-out
Allows default-route LSAs, but block all other LSAs.
out
Filters outgoing LSAs.
all-out
Blocks all LSAs.
Modes
Interface subtype configuration mode
Usage Guidelines
By default, the device floods all outbound LSAs on all the OSPF interfaces within an area. You can
configure a filter to block outbound LSAs on an OSPF interface. This feature is particularly useful when
you want to block LSAs from some, but not all, of the interfaces attached to the area. When enabled,
this command blocks the specified outgoing LSAs on the interface. Some cases where you might want
to enable filters are:
• To control the information being advertised to the network.
• To use a passive router for debugging only.
Note
You cannot block LSAs on virtual links.
Examples
The following example applies a filter to block flooding of all LSAs on a specific OSPF Ethernet
interface.
ip ospf dead-interval
Configures the neighbor dead interval, which is the number of seconds that a neighbor router waits for
a hello packet from the device before declaring the router down.
Syntax
ip ospf dead-interval interval
no ip ospf dead-interval
Command Default
The specified time period is 40 seconds.
Parameters
interval
Dead interval in seconds. Valid values range from 3 through 65535 seconds. The default is 40.
Modes
Interface subtype configuration mode
Usage Guidelines
If you change the dead interval, the hello interval is automatically changed to a value that is one fourth
that of the new dead interval, unless the hello interval is also explicitly configured using the ip ospf
hello-interval command.
The running-config command displays only explicitly configured values of the hello interval, which
means that a value that was automatically changed as the result of a dead-interval change is not
displayed.
Examples
The following example sets the dead interval to 200 on a specific OSPFv2 virtual Ethernet (VE)
interface.
ip ospf hello-interval
Configures the hello interval, which is the length of time between the transmission of hello packets that
this interface sends to neighbor routers.
Syntax
ip ospf hello-interval interval
no ip ospf hello-interval
Command Default
The default value is 10 seconds.
Parameters
interval
Hello interval in seconds. Valid values range from 1 through 65535.
Modes
Interface subtype configuration mode
Usage Guidelines
If you change the hello interval, the dead interval is automatically changed to a value that is four times
that of the new hello interval, unless the dead interval is also explicitly configured using the ip ospf
dead-interval command.
The running-config command displays only explicitly configured values of the dead interval, which
means that a value that was automatically changed as the result of a hello-interval change is not
displayed.
Examples
The following example sets the hello interval to 50 on a specific OSPFv2 virtual Ethernet (VE) interface:
ip ospf ldp-sync
Enables Label Distribution Protocol (LDP) synchronization with OSPF and configures the hold down
time interval for an interface.
Syntax
ip ospf ldp-sync { disable | enable }
no ip ospf ldp-sync enable
Command Default
Disabled.
Parameters
disable
Disables LDP synchronization.
enable
Enables LDP synchronization.
Modes
Interface subtype configuration mode
Examples
The following example enables LDP synchronization with OSPF for an Ethernet interface.
The following example disables LDP synchronization with OSPF for a loopback interface.
ip ospf md5-authentication
Configures MD5 password and authentication change hold time.
Syntax
ip ospf md5-authentication { key-activation-wait-time wait-time | key-id
id key password }
no ip ospf md5-authentication key-id
Command Default
No authentication.
Parameters
key-activation-wait-time wait-time
Sets the time that OSPFv2 waits before activating a new MD5 key. This parameter provides a
graceful transition from one MD5 key to another without disturbing the network. All new packets
transmitted after the wait time ends use the newly configured MD5 Key. OSPFv2 packets that
contain the old MD5 key are accepted for up to five minutes after the new MD5 key is in
operation. Valid values range from 0 to 14400 seconds.
key-id
Sets MD5 key.
id
Identifies the MD5 key ID. Valid values range from 1 and 255.
key password
Specifies the MD5 authentication ID and sets a password.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset the MD5 password and/or authentication change hold time on the
interface to which you are connected.
By default, the authentication key is encrypted. If you want the authentication key to be in clear text,
insert a 0 between authentication-key and string. The software adds a prefix to the authentication key
string in the configuration. For example, the following portion of the code has the encrypted code "2".
Note
MD5 passwords cannot have ASCII character 32 ('SPACE') as a part of the password string.
Examples
The following example sets the time that OSPFv2 waits before activating a new MD5 key to 240
seconds on an Ethernet interface.
The following example sets the MD5 key ID to 22 and a password “myospfpassword” on an Ethernet
interface.
ip ospf mtu-ignore
Enables or disables maximum transmission unit (MTU) match checking.
Syntax
ip ospf mtu-ignore
no ip ospf mtu-ignore
Command Default
Enabled
Modes
Interface subtype configuration mode
Usage Guidelines
In default operation, the IP MTU on both sides of an OSPFv2 link must be the same, and a check of the
MTU is performed when Hello packets are first exchanged.
Examples
The following example disables MTU-match checking on a specific OSPFv2 Ethernet interface.
The following example enables MTU-match checking on a specific OSPFv2 Ethernet interface.
ip ospf network
Configures the network type for the interface. Point-to-point can support unnumbered links, which
requires less processing by OSPF.
Syntax
ip ospf network { broadcast | non-broadcast | point-to-point }
no ip ospf network
Command Default
Network type is broadcast.
Parameters
broadcast
Network type is broadcast.
non-broadcast
Network type is non-broadcast. An interface can be configured to send OSPF traffic to its
neighbor as unicast packets rather than multicast packets.
point-to-point
Network type is point-to-point.
Modes
Interface subtype configuration mode
Usage Guidelines
On a non-broadcast interface, the devices at either end of the interface must configure non-broadcast
interface type and the neighbor IP address. There is no restriction on the number of devices sharing a
non-broadcast interface.
To configure an OSPF interface as a non-broadcast interface, the feature must be enabled on a physical
interface or a VE, following the ip ospf area statement, and then specify the IP address of the
neighbor in the OSPF configuration. The non-broadcast interface configuration must be done on the
OSPF devices at either end of the link.
Examples
The following example configures an OSPFv2 point-to-point link on a specific OSPFv2 Ethernet
interface.
The following example configures an OSPFv2 broadcast link on a specific OSPFv2 Ethernet interface.
ip ospf passive
Sets a specific OSPFv2interface to passive.
Syntax
ip ospf passive
no ip ospf passive
Command Default
All OSPF interfaces are active.
Modes
Interface subtype configuration mode
Usage Guidelines
Passive interfaces accept and process all OSPF protocol traffic, but they do not send any traffic.
Examples
The following example sets a specific OSPFv2 Ethernet interface to passive.
ip ospf priority
Configures priority for designated router (DR) election.
Syntax
ip ospf priority value
no ip ospf priority
Command Default
The default value is 1.
Parameters
value
Priority value. Valid values range from 0 through 255.
Modes
Interface subtype configuration mode
Usage Guidelines
The OSPFv2 router assigned the highest priority becomes the designated router, and the OSPFv2 router
with the second-highest priority becomes the backup router.
Examples
The following example sets a priority of 10 for the OSPFv2 router that is connected to an OSPFv2 Virtual
Ethernet (VE) interface.
ip ospf retransmit-interval
Configures the retransmit interval. The retransmit interval is the time between Link-State Advertisement
(LSA) retransmissions to adjacent routers for a given interface.
Syntax
ip ospf retransmit-interval interval
no ip ospf retransmit-interval
Command Default
The interval is 5 seconds.
Parameters
interval
Retransmit interval in seconds. Valid values range from 0 through 3600 seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command resets the retransmit interval to its default.
Examples
The following example sets the retransmit interval to 8 for all OSPFv2 devices on a specific OSPFv2
Ethernet interface.
ip ospf transmit-delay
Configures transmit delay for link-update packets. The transmit delay is the estimated time required for
OSPFv2 to send link-state update packets on the interface to which you are connected.
Syntax
ip ospf transmit-delay value
no ip ospf transmit-delay
Command Default
The transmit delay is set to 1 second.
Parameters
value
Transmit delay in seconds. Valid values range from 0 through 3600 seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command restores the default value.
Examples
The following example sets a transmit delay of 25 seconds for devices on a specific OSPFv2 Ethernet
interface.
ip pim dr-priority
Configures the designated router (DR) priority on IPv4 interfaces.
Syntax
ip pim dr-priority priority-value
no ip pim dr-priority priority-value
Command Default
The default DR priority value is 1.
Parameters
priority-value
Specifies the DR priority value as an integer. The range is 0 through 65535.
Modes
Interface configuration mode
Usage Guidelines
The no form of this command restores the default DR priority value, 1.
You can configure the ip pim dr-priority command in either Dense mode (DM) or Sparse mode
(SM).
If more than one device has the same DR priority on a subnet (as in the case of default DR priority on
all), the device with the numerically highest IP address on that subnet is elected as the DR.
The DR priority information is used in the DR election only if all the PIM devices connected to the subnet
support the DR priority option. If at least one PIM device on the subnet does not support this option,
the DR election falls back to the backwards compatibility mode in which the device with the numerically
highest IP address on the subnet is declared the DR regardless of the DR priority values.
Examples
This example configures a DR priority value of 50.
device(config)# interface ethernet 1/1
device(config-if-e10000-1/1)# ip pim dr-priority 50
Syntax
ip pim snooping enable
no ip pim snooping enable
Modes
VLAN configuration mode
Usage Guidelines
The no form of the command disables PIM snooping on the VLAN.
Use this command to enable Layer 2 PIM snooping on a VLAN. You must enable IGMP snooping on the
interface before enabling PIM snooping.
Examples
The following example enables PIM snooping on a VLAN.
device(config)# vlan 1
device(config-vlan-1)# ip pim snooping enable
ip pim-sparse
Enables or disables Protocol Independent Multicast Sparse Mode on port channels, physical or VE
interfaces.
Syntax
ip pim-sparse
no ip pim-sparse
Command Default
Protocol Independent Multicast (PIM) is not enabled on an interface.
Modes
Interface subtype configuration mode
Usage Guidelines
PIM must be enabled on the device before enabling PIM-sparse. PIM-sparse can be enabled on
interfaces
Examples
To enable PIM Sparse Mode on a virtual Ethernet (VE) interface:
device(config)# int ve 1
device(config-if-Ve-1)# ip pim-sparse
ip pim ttl-threshold
Sets the IP PIM time to live (TTL) threshold.
Syntax
ip pim ttl-threshold value
no ip pim ttl-threshold
Command Default
The default value is 1.
Parameters
priority value
Specifies the TTL threshold value. The range is 1 to 64.
Modes
Interface configuration mode
Usage Guidelines
The TTL threshold defines the minimum value required in a packet for it to be forwarded out of the
interface after the TTL has been decremented.
For example, if the TTL for an interface is set at 10, only those packets that enter with a TTL value of 11
or more are forwarded through the TTL-10 interface. With a default TTL threshold of 1, only packets
ingressing with a TTL of 2 or greater are forwarded. The TTL threshold only applies to routed interfaces
and is ignored by switched interfaces. Possible TTL values are 1 to 64. The default TTL value is 1.
Examples
The following example sets the TTL value.
device(config)# interface ethernet 1/1
device(config-if-eth-1/1)# ip pim ttl-threshold 50
ip port (telemetry)
Specifies the IPv4 address and port of a telemetry collector.
Syntax
ip ipv4-address port port-number
no ip
Command Default
The IPv4 port is not designated.
Parameters
ipv4-address
Specifies the IPv4 address of a telemetry collector.
port port-number
Specifies the port.
Modes
Telemetry-collector configuration mode
Usage Guidelines
To remove the IP/port configuration from the telemetry collector, use the no form of this command.
Examples
The following example specifies the telemetry destination IP address and port.
device# configure terminal
device(config)# telemetry collector collector_1
device(config-collector-collector_1)# ip 10.168.112.10 port 1
ip policy route-map
Enables policy-based routing (PBR).
Syntax
ip policy route-map map-name
no ip policy route-map map-name
Command Default
PBR is not enabled.
Parameters
map-name
Specifies the name of the route map.
Modes
Interface configuration mode
Usage Guidelines
The no form of the command disables PBR.
Examples
The following example enables PBR on a specific interface.
device# configure terminal
device(config)# route-map test-route permit 99
device(config-route-map-test-route/permit/99)# match ip address acl 99
device(config-route-map-test-route/permit/99)# set ip next-hop 192.168.3.1
device(config-route-map-test-route/permit/99)# exit
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# ip policy route-map test-route
ip prefix-list
Configures an IP prefix list instance.
Syntax
ip prefix-list name { [ deny ip-prefix/prefix-length | permit ip-prefix/
prefix-length ] ge ge-value [ le le-value ] ] | seq sequence-number }
no ip prefix-list name
Parameters
name
Permitted values are between 1 and 32 characters. Although the first character must be
alphabetic, the others can be alphanumeric, underscores (_) or minus signs (-).
deny ip-prefix/prefix-length
Denies a route specified in the prefix list. The prefix list matches only on the specified prefix and
prefix length, unless you use the ge ge-value or le le-value parameters.
permit ip-prefix/prefix-length
Permits a route specified in the prefix list. The prefix list matches only on the specified prefix and
prefix length, unless you use the ge ge-value or le le-value parameters.
ge ge-value
Specifies the minimum prefix length to be match. The range is from ge-value to 32.
le le-value
Specifies the maximum prefix length to be matched. The range is from the le-value to the
prefix-length parameter.
seq sequence-number
Specifies an IPv4 prefix list sequence number. If you do not specify a sequence number, the
software numbers them in increments of 5, beginning with prefix list entry 5. The device
interprets the prefix list entries in numerical order, beginning with the lowest sequence number.
Modes
Global configuration mode
Usage Guidelines
Enter no ip prefix-list name to disable this feature.
The ge-value or le-value you specify must meet the following condition for prefix-length:
ge-value <= le-value <= 32
If you do not specify le-value ge ge-value or le le-value, the prefix list matches only on the
exact prefix you specify with the ip-prefix/prefix-length parameter.
Examples
This example denies routes on 1.2.0.0/8, where the subnet mask length must be greater than or equal to
20 and less than or equal to 28, and permits routes on 10.1.0.0/16.
device# config
device(config)#
device(config)# ip prefix-list test deny 10.0.0.0/8 ge 20 le 28
device(config)# ip prefix-list test permit 10.1.0.0/16
ip proxy-arp
Enables Proxy Address Resolution Protocol (APR) on an interface.
Syntax
ip proxy-arp
no ip proxy-arp
Command Default
Proxy ARP is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
Proxy ARP enables a device to answer ARP requests from devices in one network on behalf of devices
in another network. Because ARP requests are MAC-layer broadcasts, they reach only the devices that
are directly connected to the sender of the ARP request. Therefore, ARP requests do not cross routers.
Examples
The following example enables Proxy ARP on a specified interface.
device(config)# interface ethernet 3/4
device(conf-if-eth-3/4)# ip proxy-arp
ip receive access-group
Applies an IPv4 access control list (ACL) at global configuration level. Such receive-path ACLs filter
incoming route-processor traffic according to rules that you create, but do not filter data-path traffic.
Syntax
ip receive access-group acl-name
ip receive access-group acl-name sequence seq-number
no ip receive access-group acl-name
Command Default
No receive-path ACLs are applied.
Parameters
acl-name
Specifies the name of the standard or extended IP access list.
sequence seq-number
Specifies the sequence of the rACL you are applying. Values range from 1 through 2047.
Modes
Global configuration mode
Usage Guidelines
For both interface ACLs and receive-path ACLs, you use identical commands to create the ACLs. You
also use identical commands to define permit/deny/hard-drop rules in the ACLs. The only variance is
the command you use to apply the ACL:
• To apply an interface ACL—from an interface-subtype configuration mode—you use the { ip |
ipv6 | mac } access-group command.
• To apply a receive-path ACL—from global configuration mode—you use the { ip | ipv6 }
receive access-group command.
Examples
The following example creates an IPv4 extended ACL, defines rules in the ACL, and applies it as a
receive-path ACL.
device(config)# ip access-list extended ipv4-receive-acl-example
device(conf-ipacl-ext)# hard-drop tcp host 10.0.0.1 any count
device(conf-ipacl-ext)# hard-drop udp any host 20.0.0.1 count
device(conf-ipacl-ext)# permit tcp host 10.0.0.2 any eq telnet count
device(conf-ipacl-ext)# permit tcp host 10.0.0.2 any eq bgp count
device(conf-ipacl-ext)# exit
device(config)# ip receive access-group ipv4-receive-acl-example
The following example creates two IPv4 extended ACLs, defines rules in the ACLs, and applies them as
receive-path ACLs—specifying the priority of each ACL.
device#configure terminal
device(config)# ip access-list extended test-racl-1
device(conf-ipacl-ext)# deny ip 2.2.2.2/32 1.1.1.1/32
device(config)# ip access-list extended test-racl-2
device(conf-ipacl-ext)# permit ip 2.2.2.2/32 any
device(conf-ipacl-ext)# exit
ip route
Adds a static route to the IP routing table.
Syntax
ip route dest-ip-addr [ next-hop-vrf next-vrf-name ] next-hop-address
[ metric ] [ distance distance ] [ tag tag-number ]
ip route dest-ip-addr { ethernet slot/port | port-channel number | ve ve-
number } [ metric ] [ distance distance ] [ tag tag-number ]
ip route dest-ip-addr null 0 [ metric ] [ distance distance ] [ tag tag-
number ]
ip route next-hop-recursion
no ip route dest-ip-addr [ next-hop-vrf next-vrf-name ] next-hop-address
[ metric ] [ distance distance ] [ tag tag-number ]
no ip route dest-ip-addr { ethernet slot/port | ve ve-number} [ metric ]
[ distance distance ] [ tag tag-number ]
no ip route dest-ip-addr null 0 [ metric ] [ distance distance ] [ tag
tag-number ]
no ip route next-hop-recursion
Parameters
next-hop-vrf vrf-name
Specifies the name of the non-default VRF to be used for as the next-hop gateway.
dest-ip-addr
Specifies the destination IPv4 address and mask in the format A.B.C.D/L (where "L" is the prefix
length of the mask).
next-hop-addr
Specifies the IPv4 address of the next hop.
ethernet slot/port
Specifies the destination Ethernet port.
next-hop-vrf next-vrf-name
VRF name of the next hop.
port-channel number
Specifies a port-channel interface.
ve vlan-id
Specifies the outgoing interface type as VE.
null 0
Configures the Layer 3 switch to drop IP packets to a specific network or host address by
configuring a "null" (sometimes called "null0") static route for the address.
metric
Specifies the cost metric of the route. Valid values range from 1 through 16. The default is 1.
distance distance
Specifies the administrative distance of the route. When comparing otherwise equal routes to a
destination, an SLX-OS device prefers lower administrative distances over higher ones. Valid
values range from 1 through 254. The default is 1.
tag tag-number
Specifies the tag value of the route to use for route filtering with a route map. Valid values range
from 0 through 4294967295. The default is 0.
next-hop-recursion
Specifies that if the next hop for a static route is reachable, then that route is added to the
routing table.
Modes
Global configuration mode
Usage Guidelines
The no form of the command followed by the route identifier removes a static route.
If you do not want to specify a next-hop IP address, you can instead specify a physical or virtual
interface on the SLX-OS device. If you specify an Ethernet port, the device forwards packets destined
for the static route’s destination network to the specified interface. Conceptually, this feature makes the
destination network like a directly connected network, associated with an SLX-OS device interface.
The port or virtual interface you use for the static route’s next hop must have at least one IP address
configured on it. The address does not need to be in the same subnet as the destination network.
For a default route, use the following as the destination IP address 0.0.0.0/0.
You can create a null route for traffic for traffic that should not be forwarded. To create a null route, use
the key phrase null 0 as the next hop.
Examples
The following example configures a static route to 10.95.7.0 addresses, using 10.95.6.157 as the next-hop
gateway.
device(config)# ip route 10.95.7.0/24 10.95.6.157
The following example configures a static route with an Ethernet interface as the destination.
device(config)# ip route 192.128.2.69/24 ethernet 4/1
The following example configures a null static route to drop packets destined for network 10.157.22.x.
device(config)# ip route 10.157.22.0/24 null 0
The following example configures non-recursive lookup in a non-default VRF named red.
device(config)# vrf red
device(config-vrf-red)# address-family ipv4 unicast
device(config-vrf-red-ipv4-unicast)# ip route next-hop-recursion
ip route next-hop-recursion
Enables recursive lookup for IPv4 next-hop routes.
Syntax
ip route next-hop-recursion
no ip route next-hop-recursion
Command Default
By default, next-hop recursive lookups are enabled.
Modes
Global configuration mode
Usage Guidelines
The no form of the command disables recursive lookups.
Examples
The following example disables recursive lookups in the default VRF.
device# configure terminal
device(config)# no ip route next-hop-recursion
Syntax
ip route static bfd dest-ip-address source-ip-address [ interval
transmit-time min-rx receive-time multiplier number ]
Command Default
By default, BFD is not configured for an IPv4 static route.
Parameters
dest-ip-address
Specifies the IPv4 address of the BFD neighbor.
source-ip-address
Specifies the source IPv4 address.
interval transmit-time
Specifies the interval, in milliseconds, a device waits to send a control packet to BFD peers. Valid
values range from 50 through 30000. The default is 300 milliseconds.
min-rx receive-time
Specifies the interval, in milliseconds, a device waits to receive a control packet from BFD peers.
Valid values range from 50 through 30000. The default is 300 milliseconds.
multiplier number
Specifies the number of consecutive BFD control packets that must be missed from a BFD peer
before BFD determines that the connection to that peer is not operational. Valid values range
from 3 through 50. The default is 3.
Modes
Global configuration mode
Usage Guidelines
The local device needs the interval transmit-time and min-rx receive-time variables.
The actual values in use will be the negotiated values.
For single-hop static BFD sessions, the interval value is taken from the outgoing interface. For multi-hop
BFD sessions, if the configured interval and min-rx parameters conflict with those of an existing
session, the lower values are used.
Examples
This example configures a BFD session on an IPv4 static route.
device# configure terminal
device(config)#)# ip route static bfd 10.0.2.1 10.1.1.1 interval 500 min-rx 500
multiplier 5
This example configures a BFD session on an IPv4 static route in a non-default VRF instance.
device# configure terminal
device(config)# vrf orange
device(config-vrf-orange)# address-family ipv4 unicast
device(vrf-ipv4-unicast)# ip route static bfd 10.2.2.2 10.3.3.3 interval 600 min-rx 700
multiplier 10
Syntax
ip route static bfd holdover-interval time
no ip route static bfd holdover-interval
Command Default
By default, the BFD holdover interval is 0 seconds.
Parameters
time
Specifies the BFD holdover-time interval in seconds. Valid values range from 1 through 30. The
default is 0.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to revert to the default value of 0.
If the BFD session is restored within the specified time interval, no DOWN notification is sent.
Holdover interval values are configured globally and apply to all VRFs.
Examples
This example sets the BFD holdover interval globally for IP static routes to 15.
This example removes the configured BFD holdover interval for IP static routes.
ip router-id
Changes the router ID that is already in configured.
Syntax
ip router-id A.B.C.D
no ip router-id A.B.C.D
Parameters
A.B.C.D
Specifies the IPv4 address that you want as the router ID.
Modes
Global configuration mode
Usage Guidelines
Though a device has IP addresses assigned to various interfaces, some routing protocols identify the
device by the router ID rather than the IP addresses assigned to the interfaces connected by the
protocol.
The no form of the command removes the configured router ID and restores the default router ID.
Examples
The following example specifies the router ID as 192.158.1.2.
device# configure terminal
device(config)# ip router-id 192.158.1.2
ip router isis
Enables Intermediate System-to-Intermediate System (IS-IS) routing at the interface level.
Syntax
ip router isis
Command Default
Disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Use the no form of this command to disable IS-IS routing for the interface.
Examples
The following example enables IS-IS routing for an interface Ethernet.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# ip router isis
ip source-guard enable
Enables IP Source Guard, which provides filtering on an untrusted Layer 2 access port.
Syntax
ip source-guard enable
no ip source-guard enable
Command Default
By default, IP Source Guard is not enabled.
Modes
Global configuration mode
Usage Guidelines
IP Source Guard provides source IP address filtering on a Layer 2 port to prevent a malicious host from
impersonating a legitimate host by assuming the IP address of the legitimate host.
ip subnet-broadcast-acl
Applies an IP broadcast ACL (bACL) to an interface.
Syntax
ip subnet-broadcast-acl acl-name
no ip subnet-broadcast-acl acl-name
Command Default
No bACL is applied.
Parameters
acl-name
Specifies the standard or extended bACL.
Modes
Interface subtype configuration mode
Usage Guidelines
Broadcast ACLs are not supported on SLX 9150 or SLX 9250 devices.
Examples
The following example applies a bACL to a physical interface.
device# configure terminal
device(config)# interface ethernet 0/2
device(conf-if-eth-0/2)# ip subnet-broadcast-acl bacl_10
ip subnet-rate-limit
Configures the Committed Information Rate (CIR) and Committed Burst Size (CBS) for IPv4 and IPv6
subnet trap frames.
Syntax
ip subnet-rate-limit cir cir-rate [cbs cbs-size]
no ip subnet-rate-limit
Command Default
By default, CIR and CBS are not configured.
Parameters
cir cir-rate
(Required) Defines the value of the CIR. Acceptable values range from 0 to 10,000 Kbps.
cbs cbs-size
Defines the value of the CBS. Acceptable values range from 0 to 32 KB.
Modes
Control plane configuration mode
Usage Guidelines
The CIR is the maximum number of bits that a port can receive or send during a one-second interval.
The rate of the traffic that matches the traffic policing policy cannot exceed the CIR. The CIR represents
a portion of interface bandwidth, expressed in bits per second (bps), and it cannot exceed port
bandwidth. CIR-defined traffic that does not use the available CIR accumulates credit up to the amount
defined by the CBS. This credit is the number of bytes that can be used to accommodate temporary
bursts in traffic that exceed the CIR.
( SLX 9150 and SLX 9250) By default, IPv4 and IPv6 subnet trap frames are diverted to a separate
queue (queue number 9). You can use the ip subnet-rate-limit command to further limit the
rate of IPv6 subnet trap frames .
( SLX 9540 and SLX 9640) By default, IPv4 and IPv6 subnet trap frames are rate-limited to 10,000
Kbps. You can use the ip subnet-rate-limit command to further limit IPv4 and IPv6 subnet trap
frames.
Examples
The following example configures the CIR to 134 Kbps and the CBS to 34 KB.
device# configure terminal
device(config)# control-plane
device(config-control-plane)# ip subnet-rate-limit cir 134 cbr 34
ip vrrp-extended auth-type
Configures the type of authentication used on a Virtual Router Redundancy Protocol Extended (VRRP-
E) interface.
Syntax
ip vrrp-extended auth-type md5-auth auth-text
no ip vrrp-extended auth-type md5-auth
Command Default
No authentication is configured for a VRRP-E interface.
Parameters
auth-type
Authentication type used to verify the password.
md5-auth auth-text
Configures MD5 authentication on the interface. The maximum length of the text string is 64
characters.
Modes
Virtual Ethernet (VE) interface configuration mode
Usage Guidelines
This configuration is for VE interfaces only.
If the md5-auth option is configured, syslog and SNMP traps are generated if a packet is being
dropped due to MD5 authentication failure. Using MD5 authentication implies that the software does
not need to run checksum verification on the receiving device and can rely on the authentication code
(message digest 5 algorithm) to verify the integrity of the VRRP-E message header.
The no form of this command removes the VRRP-E authentication from the interface.
Note
MD5 passwords cannot have ASCII character 32 ('SPACE') as a part of the password string.
Examples
The following example configures MD5 authentication on VE interface 20.
ipv6 access-group
Applies rules specified in an IPv6 access control list (ACL) to traffic entering an interface.
Syntax
ipv6 access-group ACLname in
no ipv6 access-group ACLname in
Parameters
ACLname
Specifies the name of the standard or extended IPv6 access list.
in
Applies the ACL to incoming switched and routed traffic.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to apply an IPv6 ACL to one of the following interface types:
• User interfaces
◦ Physical interfaces
◦ Port-channels (LAGs)
◦ Virtual Ethernet (VE) (attached to a VLAN or to a bridge domain)
• The management interface
You can apply a maximum of two ACLs to the management interface, as follows:
• One ingress IPv4 ACL
• One ingress IPv6 ACL
Examples
The following example applies an IPv6 ACL on an Ethernet interface to incoming traffic.
device# configure terminal
device(config)# interface ethernet 0/1
device(conf-if-eth-0/1)# ipv6 access-group ipv6_acl_7 in
ipv6 access-list
Creates a standard or extended IPv6 access control list (ACL). In ACLs, you can define rules that permit
or deny network traffic based on criteria that you specify.
Syntax
ipv6 access-list { standard | extended } ACLname
no ipv6 access-list { standard | extended } ACLname
Parameters
standard | extended
Specifies one of the following types of access lists:
standard
Contains rules that permit or deny traffic based on source addresses that you specify. The rules
are applicable to all ports of the specified addresses.
extended
Contains rules that permit or deny traffic according to source and destination addresses, as well
as other parameters. For example, you can also filter by port, protocol (TCP or UDP), and TCP
flags.
ACLname
Specifies an ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63
characters in length, and must begin with an alphanumeric character. No special characters are
allowed, except for the underscore and hyphen.
Modes
Global configuration mode
Usage Guidelines
An ACL name can be up to 63 characters long, and must begin with a–z, A–Z or 0–9. You can also use
underscore (_) or hyphen (-) in an ACL name, but not as the first character.
After you create an ACL, use the seq command to create filtering rules for that ACL.
To delete an ACL, use the no access-list command. You can delete an ACL only after you first
remove it from all interfaces to which it is applied, using the no access-group command.
Examples
The following example creates an IPv6 standard ACL:
device# configure
device(config)# ipv6 access-list standard stdV6ACL1
ipv6 address
Configure an IPv6 address for an interface.
Syntax
ipv6 address pv6-prefix//prefix-length [ secondary ] [ anycast | eui-64 ]
no ipv6 address pv6-prefix//prefix-length [ secondary ] [ anycast |
eui-64 ]
ipv6 address ipv6-address link-local
no ipv6 address ipv6-address link-local
Parameters
ipv6-address
Specifies the IPv6 address.
ipv6-prefix
Specifies the IPv6 prefix address in this format: X:X::X:X/M.
prefix-length
A decimal value specifying the length of the IPv6 prefix.
secondary
Specifies that the address is a secondary address. A maximum of 256 secondary addresses can
be configured.
anycast
Configures an address as an anycast address.
eui-64
Configures the global address with an EUI-64 interface ID in the low-order 64 bits. The interface
ID is automatically constructed in IEEE EUI-64 format using the interface's MAC address.
Modes
Interface configuration mode
Usage Guidelines
A secondary address cannot be configured on an interface unless the primary address is configured
first.
The primary address cannot be deleted on an interface unless the secondary addresses are deleted first.
Examples
This example shows how to configure a primary, secondary global, or unique local IPv6 unicast address,
including a manually configured interface ID:
device(config)# configure terminal
device(config)# interface ethernet 3/1
device(conf-if-eth-2/3)# ipv6 address 2001:db8:12d:1300:240z:d0ff:fe48:4672/64
This example shows how to remove the IPv6 unicast address, including a manually configured interface
ID from an interface:
device(conf-if-eth-2/3)# no ipv6 address 2001:db8:12d:1300:240z:d0ff:fe48:4672/64
ipv6 anycast-address
Configures an anycast-gateway IPv6 address on an interface, which uses the gateway IPv6 address for
the host.
Syntax
ipv6 anycast-address { IPv6-address/ mask }
no ipv6 anycast-address
Command Default
No address is configured.
Parameters
IPv6-address / mask
IPv6 address and mask.
Modes
interface configuration mode on a virtual Ethernet (VE) interface.
Usage Guidelines
An IPv4 and IPv6 anycast MAC address cannot be configured as the same MAC address.
Use the no form of this command to delete the configured IPv6 anycast address from the interface.
Examples
To configure an IPv6 address and mask on a virtual Ethernet (VE) interface:
device# configure terminal
device(config)# interface ve 10
device(config-Ve-10)# ipv6 anycast-address fe80::1234/64
Syntax
ipv6 dhcp relay address ipv6-addr [interface interface-type interface-
name] [ use-vrf vrf-name ]
no ipv6 dhcp relay address ipv6-addr [interface interface-type interface-
name] [ use-vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of the DHCP server where the DHCP client requests are to be forwarded.
interface
This parameter specifies the outgoing interface, used when the relay address is a link-local or
multicast address
interface-type
The type of interface - Ethernet or VE.
interface-name
The interface name or VE ID.
use-vrf
Use this option if the VRF where the DHCP server is located is different from the VRF of the
interface where the client is connected.
vrf-name
VRF name.
Modes
Interface subtype configuration mode
Usage Guidelines
This command uses the IPv6 address of the DHCP server where the DHCP client requests are to be
forwarded. You can configure the address on a virtual Ethernet (VE) or an Ethernet interface. You can
configure up to 16 relay destination addresses on an interface.
Enter the command while in interface subtype configuration mode for a VE or Ethernet interface where
you want to configure the IPv6 DHCP Relay. Use the no version of this command to remove the IPv6
DHCP Relay from the interface. If the use-vrf option is not used, it is assumed that the DHCP server
and interface where the client is connected are on the same VRF.
If the relay address is a link local address or a multicast address, an outgoing interface must be
configured for IPv6 relay to function. In instances where the server address is relayed to a different VRF
compared to a client connected interface VRF, in addition to the relay address, you must also specify
the user-vrf, otherwise IPv6 relay may not function correctly. IPv6 route leaking is also required for IPv6
reachability.
The no form of the command deletes the IPv6 DHCP Relay address from the interface.
Examples
To configure an IPv6 DHCP Relay address on a Ve interface:
device# config
device(config)# interface ve 100
device(config-Ve-100)# ipv6 dhcp relay address 2001::1122:AABB:CCDD:3344 use-vrf blue
ipv6 dns
Configures the DNS domain name and the primary and secondary name-server IPv6 addresses.
Syntax
ipv6 dns { domain-name domain_name | name-server name_server }
no ipv6 dns { domain-name domain_name | name-server name_server }
Parameters
domain-name domain_name
Specifies the DNS domain name.
name-server name_server
Specifies the IPv6 address of the primary and secondary name servers. Both the IPv6 and IPv4
addresses are supported.
Modes
Global configuration mode
Usage Guidelines
Your first run of ipv6 dns name-server specifies the default IP gateway address. Your second run
of ipv6 dns name-server specifies the secondary IP gateway address.
Name servers can only be entered or removed one at a time. The newly entered name server will
append to the existing name server.
To disable IP directed broadcasts for a specific domain, enter no ipv6 dns domain-name
domain_name.
Examples
The following example configures DNS.
device(config)# ipv6 dns domain-name mycompany.com
device(config)# ipv6 dns name-server 2001:db8:12d:1300:240z:d0ff:fe48:4672
Syntax
ipv6 icmpv6 rate-limiting milliseconds
no ipv6 icmpv6 rate-limiting
Command Default
This command is enabled on the management port and on the front-end ports.
Parameters
milliseconds
Time interval per ICMP packet. The range is from 1 through 4294967295 milliseconds. The default
is 1000 milliseconds.
Modes
Interface configuration mode
Usage Guidelines
This is an interface-specific configuration.
The no form of this command reverts the rate limiting to the default settings.
Examples
The following example enables IPv6 ICMP rate-limiting on an Ethernet interface.
device(config)# interface ethernet 3/5
device(conf-int-eth-3/5)# ipv6 icmpv6 rate-limiting
Syntax
ipv6 icmpv6 unreachable
no ipv6 icmpv6 unreachable
Command Default
By default, the device does not respond to ICMP unreachable messages.
Modes
Interface configuration mode.
Usage Guidelines
Use the no form of the command to disable the feature.
Examples
The following example enables a device to respond to ICMP unreachable notifications to the indicated
source.
device# configure terminal
device(config)# interface ve 2
device(config-int-ve-2)# ip address 200::1/64
device(config-int-ve-2)# ip icmp unreachable
Syntax
ipv6 nd cache expire seconds
no ipv6 nd cache expire seconds
Command Default
Default expiration time is 1500 seconds.
Parameters
seconds
Specifies how long an entry stays in the Neighbor Discovery cache. The range is from 30 through
14400 seconds. The default is 1500.
Modes
Interface subtype configuration mode
Usage Guidelines
Cache entries expire and are deleted if they remain in a "stale" state as defined by seconds.
You can modify the ND expiration time only at the interface level, but not at the global level.
The no form of this command restores the default aging timeout of 1500 seconds.
Examples
The following example sets the Neighbor Discovery expiration time to 2500 seconds on an Ethernet
interface:
device# configure terminal
device(config)# interface ethernet 1/2
conf-if-eth-1/2)# ipv6 nd cache expire 2500
Syntax
ipv6 nd cache interface-limit 1-97280
no ipv6 nd cache interface-limit
Modes
Global Configuration and Interface Configuration Modes
Usage Guidelines
The minimum neighbor discovery cache limit that can be configured per interface is one (1). The
maximum neighbor discovery limit per interface is the same as the system's maximum neighbor
discovery cache limit. This maximum limit varies between the various systems. The maximum value that
can be configured is 97280 entries.
The command when executed in the Global Configuration mode configures the maximum number of
entries for all IPv6 neighbor discovery tables.
The command when executed within an interface's configuration mode, configures the limit on that
interface's IPv6 neighbor discovery table.
The no format of the global form of this command removes the configured neighbor discovery cache
limit from all the interfaces. However, it does not remove neighbor discovery limitations configured on
individual interfaces which were configured using the ipv6 nd cache interface-limit
command.
Examples
The following example sets the IPv6 neighbor discovery table limit to 100 globally.
SLX(config)# ipv6 nd cache interface-limit 100
The following example sets the IPv6 neighbor discovery table limit to 250 entries for the ethernet
interface 3/5.
SLX (config)# interface ethernet 3/5
SLX (config-if-eth-3/5)# ipv6 nd cache interface-limit 250
This example displays the neighbor discovery cache limit configuration on a VE interface.
SLX # show ipv6 neighbor ve 4227
SLX #
Syntax
ipv6 option disable
no ipv6 option disable
Command Default
By default, IPv6 packets with RH options are not blocked.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to unblock packets that have IP options.
Examples
The following example blocks IPv6 packets that have RH options.
device# configure terminal
device(config)# ipv6 option disable
Syntax
ipv6 ospf active
Modes
Interface subtype configuration mode
Usage Guidelines
Use the ipv6 ospf active command on each interface participating in adjacency formation. This
command overrides the global passive setting on that interface, and enables transmission of OSPFv3
control packets.
Examples
The following example sets a specific OSPFv3 Ethernet interface to active.
Syntax
ipv6 ospf area area-id | ip-addr
no ipv6 ospf area
Command Default
OSPFv3 is disabled.
Parameters
area-id
Area ID in dotted decimal or decimal format.
ip-addr
Area ID in IP address format.
Modes
Interface subtype configuration mode
Usage Guidelines
This command enables an OSPFv3 area on the interface to which you are connected.
Examples
The following example enables a configured OSPFv3 area named 0 on a specific OSPFv3 Loopback
interface.
Syntax
ipv6 ospf authentication ipsec key-add-remove-interval interval
no ipv6 ospf authentication ipsec key-add-remove-interval interval
Command Default
Disabled.
Parameters
key-add-remove-interval interval
Specifies the OSPFv3 authentication key add-remove interval. Valid values range from decimal
numbers 0 through 14400. The default is 300.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command removes IPsec authentication from the interface.
Examples
The following example enables IPsec on a specified OSPFv3 Looback interface.
The following example sets the OSPFv3 authentication key add-remove interval to 480.
Syntax
ipv6 ospf authentication ipsec disable
no ipv6 ospf authentication ipsec disable
Command Default
Authentication is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to disable IPsec if it is enabled on the interface. Packets that are sent out will not be
IPSec encapsulated and the received packets which are IPSec encapsulated will be dropped.
The no form of the command re-enables IPSec on the interface if IPsec is already configured on the
interface.
Examples
The following example disables IPsec on a specific OSPFv3 interface where IPsec is already enabled.
Syntax
ipv6 ospf authentication spi spi { ah | esp null } { hmac-md5 | hmac-
sha1 } key key }
no ipv6 ospf authentication spi
Command Default
Disabled.
Parameters
spi
SPI value. Valid values range from decimal numbers 512 through 4294967295.
ah
Specifies Authentication Header (ah) as the protocol to provide packet-level security.
esp
Specifies Encapsulating Security Payload (ESP) as the protocol to provide packet-level security.
null
Specifies that the ESP payload is not encrypted.
hmac-md5
Enables Hashed Message Authentication Code (HMAC) Message Digest 5 (MD5) authentication
on the OSPFv3 interface.
hmac-sha1
Enables HMAC Secure Hash Algorithm 1 (SHA-1) authentication on the OSPFv3 interface.
key
Number used in the calculation of the message digest.
key
The 40 hexadecimal character key.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no ipv6 ospf authentication spi spi to remove the SPI value from the interface.
Examples
The following example enables ESP and HMAC-SHA-1 on an OSPFv3 Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# ipv6 ospf area 0
device(conf-if-eth-1/1)# ipv6 ospf authentication spi 512 esp null hmac-sha1 key
abcef12345678901234fedcba098765432109876
The following example enables AH and HMAC-MD5 on an OSPFv3 virtual Ethernet (VE) interface.
device# configure terminal
device(config)# interface ve 1
device(config-if-Ve-1)# ipv6 ospf area 0
device(config-if-Ve-1# ipv6 ospf authentication spi 750 ah hmac-md5 key
abcef12345678901234fedcba098765432109876
Syntax
ipv6 ospf bfd
no ipv6 ospf bfd
Modes
Interface subtype configuration mode
Usage Guidelines
BFD sessions are initiated only if BFD is also enabled globally using the bfd command in OSPFv3 router
configuration mode. If BFD is disabled using the no bfd command in OSPFv3 router configuration
mode, BFD sessions on specific interfaces are deregistered.
The no form of the command removes all BFD sessions from a specified interface.
Examples
The following example enables BFD on an Ethernet interface.
The following example disables BFD on an OSPFv3 virtual Ethernet (VE) interface.
Syntax
ipv6 ospf cost value
no ipv6 ospf cost
Command Default
Cost value is 1.
Parameters
value
Cost value. Valid values range from 1 through 65535. The default is 1.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set or reset the OSPFv3 cost on the interface. If the cost is not configured with
this command, OSPFv3 calculates the value from the reference and interface bandwidths.
Examples
The following example sets the cost to 620 on a specific OSPFv3 Virtual Ethernet (VE) interface.
Syntax
ipv6 ospf dead-interval interval
no ipv6 ospf dead-interval
Command Default
The specified time period is 40 seconds.
Parameters
interval
Dead interval in seconds. Valid values range from 3 through 65535 seconds. The default is 40.
Modes
Interface subtype configuration mode
Usage Guidelines
If you change the dead interval, the hello interval is automatically changed to a value that is one fourth
that of the new dead interval, unless the hello interval is also explicitly configured using the ipv6
ospf hello-interval command.
The running-config command displays only explicitly configured values of the hello interval, which
means that a value that was automatically changed as the result of a dead-interval change is not
displayed.
Examples
The following example sets the dead interval to 80 on a specific OSPFv3 Ethernet interface.
Syntax
ipv6 ospf hello-interval interval
no ipv6 ospf hello-interval
Command Default
The length of time between the transmission of hello packets is set to 10 seconds.
Parameters
interval
Hello interval in seconds. Valid values range from 1 through 65535 seconds. The default is 10.
Modes
Interface subtype configuration mode
Usage Guidelines
If you change the hello interval, the dead interval is automatically changed to a value that is four times
that of the new hello interval, unless the dead interval is also explicitly configured using the ipv6
ospf dead-interval command.
The running-config command displays only explicitly configured values of the dead interval, which
means that a value that was automatically changed as the result of a hello interval change is not
displayed.
Examples
The following example sets the hello interval to 20 on a specific OSPFv3 Ethernet interface.
Syntax
ipv6 ospf hello-jitter interval
no ipv6 ospf hello-jitter
Command Default
10%
Parameters
jitter
Allowed interval between hello packets.Valid values range from 1 through 50 percent (%).
Modes
Interface subtype configuration mode
Usage Guidelines
The hello interval can vary from the configured hello-interval to a maximum of percentage value of
configured jitter.
Examples
The following example sets the hello jitter to 20 on a specific OSPFv3 Ethernet interface.
Syntax
ipv6 ospf instance instanceID
no ipv6 ospf instance
Parameters
instanceID
Instance identification number. Valid values range from 0 through 255.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command restores the default value.
Examples
The following example sets the number of IPv6 OSPF instances to 35 on a specific Ethernet interface.
Syntax
ipv6 ospf mtu-ignore
no ipv6 ospf mtu-ignore
Command Default
Enabled.
Modes
Interface subtype configuration mode
Usage Guidelines
In default operation, the IP MTU on both sides of an OSPFv3 link must be the same, and a check of the
MTU is performed when Hello packets are first exchanged.
Examples
The following example disables MTU-match checking on a specific OSPFv3 Ethernet interface.
The following example disables MTU-match checking on a specific OSPFv3 Ethernet interface.
Syntax
ipv6 ospf network { broadcast | point-to-point }
no ipv6 ospf network
Command Default
Network type is broadcast.
Parameters
broadcast
Network type is broadcast, such as Ethernet.
point-to-point
Network type is point-to-point.
Modes
Interface subtype configuration mode
Usage Guidelines
Point-to-point can support unnumbered links, which requires less processing by OSPFv3.
Note
The network type non-broadcast is not supported at this time.
Examples
The following example configures an OSPFv3 point-to-point link on a specific OSPFv3 Ethernet
interface.
The following example configures an OSPFv3 broadcast link on a specific OSPFv3 Loopback interface.
Syntax
ipv6 ospf passive
no ipv6 ospf passive
Modes
Interface subtype configuration mode
Usage Guidelines
The ipv6 ospf passive command disables transmission of OSPFv3 control packets on that
interface. OSPFv3 control packets received on a passive interface are discarded.
Examples
The following example sets a specific OSPFv3 virtual Ethernet (VE) interface to passive.
Syntax
ipv6 ospf priority value
no ipv6 ospf priority
Command Default
The value is set to 1.
Parameters
value
Priority value. Valid values range from 0 through 255. The default is 1.
Modes
Interface subtype configuration mode
Usage Guidelines
The OSPFv3 router assigned the highest priority becomes the designated router, and the OSPFv3 router
with the second-highest priority becomes the backup router.
Examples
The following example sets a priority of 4 for the OSPFv3 router that is connected to an OSPFv3 Virtual
Ethernet (VE) interface.
Syntax
ipv6 ospf retransmit-interval interval
no ipv6 ospf retransmit-interval
Command Default
The interval is 5 seconds.
Parameters
interval
Retransmit interval in seconds. Valid values range from 0 through 3600 seconds. The default is 5.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command resets the retransmit interval to its default.
Examples
The following example sets the retransmit interval to 8 for all OSPFv3 devices on a specific OSPFv3
Ethernet interface.
Syntax
ipv6 ospf suppress-linklsa
no ipv6 ospf suppress-linklsa
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command restores the defaults where link LSA advertisements are not suppressed.
Examples
The following example suppresses link LSAs from being advertised on devices on a specific OSPFv3
Ethernet interface.
Syntax
ipv6 ospf transmit-delay value
no ipv6 ospf transmit-delay
Command Default
The transmit delay is set to 1 second.
Parameters
value
Transmit delay in seconds. Valid values range from 0 through 3600 seconds.
Modes
Interface subtype configuration mode
Usage Guidelines
The no form of the command restores the default value.
Examples
The following example sets a transmit delay of 25 seconds for devices on a specific OSPFv3 Ethernet
interface.
Syntax
ipv6 policy route-map map-name
no ipv6 policy route-map map-name
Command Default
IPv6 PBR is not enabled.
Parameters
map-name
Specifies the name of the route map.
Modes
Interface configuration mode
Usage Guidelines
The no form of the command disables IPv6 PBR.
Examples
The following example enables PBR on a specific interface.
device(config)# route-map test-route permit 99
device(config-route-map-test-route/permit/99)# match ipv6 address acl 99
device(config-route-map-test-route/permit/99)# set ipv6 next-hop
2001:db8:0:0:0:ff00:42:8329
device(config-route-map-test-route/permit/99)# exit
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# ipv6 policy route-map test-route
ipv6 prefix-list
Configures an IPv6 prefix list for basic traffic filtering
Syntax
ipv6 prefix-list name deny ipv6-prefix/prefix-length [ ge ge-value ] [ le
le-value ]
ipv6 prefix-list name permit ipv6-prefix/prefix-length [ ge ge-value ]
[ le le-value ]
ipv6 prefix-list name seq instance-number {deny ge ge-value le le-value |
permit ge ge-value le le-value }
no ipv6 prefix-list name
Parameters
name
Specifies the prefix list name.
deny ip-prefix/prefix-length
Denies a route specified in the prefix list. The prefix list matches only on the specified prefix/
prefix length, unless you use the ge ge-value or le le-value parameters.
ge ge-value
Specifies minimum prefix length to be matched. The range is from ge-value to 128.
le le-value
Specifies maximum prefix length to be matched. The range is from the le-value to the
prefix-length parameter.
permit ip-prefix/prefix-length
Permits a route specified in the prefix list. The prefix list matches only on the specified prefix/
prefix length, unless you use the ge ge-value or le le-value parameters.
seq
Specifies an IPv6 prefix list sequence number of entry.
instance
Specifies an IPv6 prefix list instance number.
Modes
Global configuration mode
Usage Guidelines
An IPv6 prefix list is composed of one or more conditional statements that execute a permit or deny
action if a route matches a specified prefix. In prefix lists with multiple statements, you can specify a
sequence number for each statement. The specified sequence number determines the order in which
the statement appears in the prefix.
You can configure an IPv6 prefix list on a global basis, then use it as input to other commands or
processes, such as route aggregation, route redistribution, route distribution, route maps, and so on.
When an SLX-OS device interface sends or receives an IPv6 packet, it applies the statements within the
IPv6 prefix list in their order of appearance to the packet. As soon as a match occurs, the device takes
the specified action (permit or deny the packet) and stops further comparison for that packet.
You can use permit statements in the prefix list to specify the traffic that you want to send to the other
feature. If you use deny statements, the traffic specified by the deny statements is not supplied to the
other feature. You can configure up to one hundred IPv6 prefix lists.
You must specify the ipv6-prefix parameter in hexadecimal using 16-bit values between colons as
documented in RFC 4291. You must specify the prefix-length parameter as a decimal value. A slash
mark (/) must follow the ipv6-prefix parameter and precede the prefix-length parameter.
The ge-value or le-value you specify must meet the following condition for prefix-length:
Examples
The following example creates a prefix-list that allows routes with the prefix 2001:db8::/32 .
Syntax
ipv6 protocol vrrp
no ipv6 protocol vrrp
Command Default
IPv6 VRRPv3 is not enabled.
Modes
Global configuration mode
Usage Guidelines
The no form of this command globally disables VRRPv3.
Examples
To enable IPv6 VRRPv3 globally:
Syntax
ipv6 protocol vrrp-extended
no ipv6 protocol vrrp-extended
Command Default
IPv6 VRRP-Ev3 is disabled.
Modes
Global configuration mode
Usage Guidelines
The no form of this command globally disables IPv6 VRRP-Ev3.
Examples
To enable IPv6 VRRP-Ev3 globally:
Syntax
ipv6 receive access-group acl-name [ sequence seq-number ]
no ipv6 receive access-group acl-name
Command Default
No receive-path ACLs are applied.
Parameters
acl-name
Specifies the name of the standard or extended IP access list.
sequence seq-number
Specifies the sequence of the rACL you are applying. Values range from 1 through 2047.
Modes
Global configuration mode
Usage Guidelines
For both interface ACLs and receive-path ACLs, you use identical commands to create the ACLs. You
also use identical commands to define permit/deny rules in the ACLs. The only variance is the
command you use to apply the ACL:
• To apply an interface ACL, from an interface-subtype configuration mode you use the { ip |
ipv6 | mac } access-group command.
• To apply a receive-path ACL, from global configuration mode you use the { ip | ipv6 }
receive access-group command.
Examples
The following example creates an IPv6 extended ACL, defines rules in the ACL, and applies it as a
receive-path ACL.
device(config)# ipv6 access-list extended ipv6-receive-acl-example
device(conf-ipacl-ext)# hard-drop tcp host 10::1 any count
device(conf-ipacl-ext)# hard-drop udp any host 20::1 count
device(conf-ipacl-ext)# permit tcp host 10::2 any eq telnet count
device(conf-ipacl-ext)# permit tcp host 10::2 any eq bgp count
device(conf-ipacl-ext)# exit
device(config)# ipv6 receive access-group ipv6-receive-acl-example
The following example creates two IPv6 extended ACLs, defines rules in the ACLs, and applies them as
receive-path ACLs—specifying the priority of each ACL.
device# configure terminal
device(config)# ipv6 access-list extended test-racl-v6-1
device(conf-ip6acl-ext)# deny ipv6 host 2::2 any count
device(conf-ip6acl-ext)# exit
device(config)# ipv6 access-list extended test-racl-v6-2
device(conf-ip6acl-ext)# permit ipv6 host 3::3 any
device(conf-ip6acl-ext)# exit
ipv6 route
Configures an IPv6 static route.
Syntax
ipv6 route dest-ipv6-prefix/prefix-length next-hop-ipv6-address
[ metric ] [ distance number ] [ tag tag-number ]
ipv6 route dest-ipv6-prefix/prefix-length link-local-next-hop-ipv6-
address [ ethernet slot/port ] [ metric ] [ distance number ] [ tag
tag-number ]
ipv6 route dest-ipv6-prefix/prefix-length link-local-next-hop-ipv6-
address [port-channel number ] [ metric ] [ distance number ] [ tag
tag-number ]
ipv6 route dest-ipv6-prefix/prefix-length link-local-next-hop-ipv6-
address [ ve ve-id ] [ metric ] [ distance number ] [ tag tag-
number ]
ipv6 route next-hop-recursion
no ipv6 route dest-ipv6-prefix/prefix-length next-hop-ipv6-address
no ipv6 route dest-ipv6-prefix/prefix-length link-local-next-hop-ipv6-
address [ ethernet slot/port ]
no ipv6 route dest-ipv6-prefix/prefix-length link-local-next-hop-ipv6-
address [port-channel number ]
no ipv6 route dest-ipv6-prefix/prefix-length link-local-next-hop-ipv6-
address [ ve ve-id ]
no ipv6 route next-hop-recursion
Command Default
No IPv6 static route is configured by default.
Parameters
dest-ipv6-prefix
Destination IPv6 prefix in hexadecimal with 16-bit values between colons, as specified in RFC
2373.
prefix-length
A decimal value specifying the length of the IPv6 address prefix.
next-hop-ipv6-address
IPv6 address of the next-hop gateway.
link-local-next-hop-ipv6-address
IPv6 address of the link-local next-hop gateway.
ethernet slot/port
Specifies the Ethernet slot and port.
port-channel number
Specifies a port-channel interface.
ve ve-id
Specifies the virtual Ethernet (VE) interface.
metric
Specifies a value that the Layer 3 switch uses to compare this route to other static routes in the
IPv6 static route table that have the same destination. The metric applies only to routes that the
Layer 3 switch has already placed in the IPv6 static route table. Two or more routes to the same
destination with the same metric will load share (as in ECMP load sharing). The range is from 1
through 16. The default is 1.
distance number
Specifies an administrative distance. The range is from 1 through 254. The default is 1. This is a
value that the Layer 3 switch uses to compare this route with routes from other route sources
that have the same destination. By default, static routes take precedence over routes learned by
routing protocols. To choose a dynamic route over a static route, configure the static route with a
higher administrative distance than the dynamic route. A distance of 255 is considered
unreachable.
tag
Specifies a tag value for the route. The route tag can be used for route redistribution to routing
protocols by means of route maps (as in IPv4 static route redistribution).
tag-number
A number from 0 through 4294967295. The default is 0.
next-hop-recursion
Specifies that if the next hop for a static route is reachable, then that route is added to the
routing table.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command with the same parameters to remove the IPv6 static route.
Examples
The following example creates an IPv6 static route for a destination network with the prefix
2001:DB8::0/32 and a next-hop gateway with the global address 2001:DB8:0:ee44::1.
device# configure terminal
device(config)# ipv6 route 2001:DB8::0/32 2001:DB8:0:ee44::1
The following example configures non-recursive lookup in a non-default VRF named red.
device(config)# vrf red
device(config-vrf-red)# address-family ipv6 unicast
device(config-vrf-red-ipv6-unicast)# ipv6 route next-hop-recursion
Syntax
ipv6 route next-hop-recursion
no ipv6 route next-hop-recursion
Command Default
By default, next-hop recursive lookups are enabled.
Modes
Global configuration mode
Usage Guidelines
The no form of the command disables recursive lookups.
Examples
The following example disables recursive lookups in the default VRF.
device# configure terminal
device(config)# no ipv6 route next-hop-recursion
Syntax
ipv6 route dest-ipv6-prefix/prefix-length null 0 [ metric ] [ distance
number ] [ tag tag-number ]
no ipv6 route dest-ipv6-prefix/prefix-length null 0
Command Default
No IPv6 static route is configured by default.
Parameters
dest-ipv6-prefix
Destination IPv6 prefix in hexadecimal with 16-bit values between colons, as specified in RFC
2373.
prefix-length
A decimal value specifying the length of the IPv6 address prefix.
next-hop-ipv6-address
IPv6 address of the next-hop gateway.
null 0
Causes packets to the selected destination to be dropped by shunting them to the "null 0"
interface. (This is the only available option.)
ethernet slot/port
Specifies the Ethernet slot and port.
metric
Specifies a value that the Layer 3 switch uses to compare this route to other static routes in the
IPv6 static route table that have the same destination. The metric applies only to routes that the
Layer 3 switch has already placed in the IPv6 static route table. Two or more routes to the same
destination with the same metric will load share (as in ECMP load sharing). The range is from 1
through 16. The default is 1.
distance number
Specifies an administrative distance. The range is from 1 through 254. The default is 1. This is a
value that the Layer 3 switch uses to compare this route with routes from other route sources
that have the same destination. By default, static routes take precedence over routes learned by
routing protocols. To choose a dynamic route over a static route, configure the static route with a
higher administrative distance than the dynamic route. A distance of 255 is considered
unreachable.
tag
Specifies a tag value for the route. The route tag can be used for route redistribution to routing
protocols by means of route maps (as in IPv4 static route redistribution).
tag-number
A number from 0 through 4294967295. The default is 0.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command with the same parameters to remove the null route.
Related commands:
• ipv6 route
• ipv6 route next-hop-vrf
Examples
The following example creates a primary route to all 2001 : DB8 : : 0/32 destinations through virtual
interface (ve) 3. The primary route has the default cost metric of 1. The example aslo creates an
alternative null route (with a cost metric of 2) to drop packets when the primary route is not available.
Syntax
ipv6 route ipv6-prefix/prefix-length next-hop-vrf vrf_name next-hop-ipv6-
address [ metric ] [ distance number ] [ tag tag-number ]
no ipv6 route ipv6-prefix/prefix-length next-hop-vrf vrf_name next-hop-
ipv6-address
Command Default
No IPv6 static route is configured by default.
Parameters
dest-ipv6-prefix
Destination IPv6 prefix in hexadecimal with 16-bit values between colons, as specified in RFC
2373.
prefix-length
A decimal value specifying the length of the IPv6 address prefix.
next-hop-ipv6-address
IPv6 address of the next-hop gateway.
next-hop-vrf vrf_name next-hop-ipv6-address
Specifies a VRF instance and a next-hop IPv6 address.
metric
Specifies a value that the Layer 3 switch uses to compare this route to other static routes in the
IPv6 static route table that have the same destination. The metric applies only to routes that the
Layer 3 switch has already placed in the IPv6 static route table. Two or more routes to the same
destination with the same metric will load share (as in ECMP load sharing). The range is from 1
through 16. The default is 1.
distance number
Specifies an administrative distance. The range is from 1 through 254. The default is 1. This is a
value that the Layer 3 switch uses to compare this route with routes from other route sources
that have the same destination. By default, static routes take precedence over routes learned by
routing protocols. To choose a dynamic route over a static route, configure the static route with a
higher administrative distance than the dynamic route. A distance of 255 is considered
unreachable.
tag
Specifies a tag value for the route. The route tag can be used for route redistribution to routing
protocols by means of route maps (as in IPv4 static route redistribution).
tag-number
A number from 0 through 4294967295. The default is 0.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command with the same parameters to remove the IPv6 static route.
Related commands:
• ipv6 route
• ipv6 route null
Examples
The following example creates an IPv6 static route to IPv6 2001:DB8::0/32 destinations through the
VRF named "partners" and the next-hop router with the IPv6 address 2001:DB8:0:ee44::1.
Syntax
ipv6 route static bfd dest-ipv6-address source-ipv6-address [ interface-
type interface-name ] [ interval transmit-time min-rx receive-time
multiplier number ]
no ipv6 route static bfd dest-ipv6-address source-ipv6-address
[ interfacetype interface-name ]
no IPv6 route static bfd dest-ipv6-address source-ipv6-address
[ interfacetype interface-name ] [ interval transmit-time min-rx
receive-time multiplier number ]
Command Default
By default, BFD is not configured for an IPv6 static route.
Parameters
dest-ipv6-address
Specifies the IPv6 address of BFD neighbor.
source-ipv6-address
Specifies the source IPv6 address.
interface-type
The type of interface, such as Ethernet or Ve.
interface-name
The interface number or VLAN ID.
intervaltransmit-time
Specifies the interval, in milliseconds, a device waits to send a control packet to BFD peers. Valid
values range from 50 through 30000. The default is 300 milliseconds.
min-rx receive-time
Specifies the interval, in milliseconds, a device waits to receive a control packet from BFD peers.
Valid values range from 50 through 30000. The default is 300 milliseconds.
multiplier number
Specifies the number of consecutive BFD control packets that must be missed from a BFD peer
before BFD determines that the connection to that peer is not operational. Valid values range
from 3 through 50. The default is 3.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command without the interval parameter to remove the configured BFD IPv6
static route.
Use the no form of this command with the interval parameter to revert the configured interval value to
the default value.
The transmit-time and receive-time variables are the intervals needed by the local device. The
actual values in use will be the negotiated values.
For single-hop static BFD sessions, the interval value is taken from the outgoing interface. For multi-hop
BFD sessions, if the configured interval and min-rx parameters conflict with those of an existing
session, the lower values are used.
For IPv6 static BFD sessions, if the BFD neighbor is link-local, the source IPv6 address must also be link-
local.
If an IPv6 BFD session is running for a link-local BFD neighbor, the interface-type interface-
name parameters are mandatory because the link-local address can be the same on multiple interfaces.
Examples
This example configures a BFD session on an IPv6 static route, specifying a VE interface.
This example configures a BFD session on an IPv6 static route in a non-default VRF instance.
Syntax
ipv6 route static bfd holdover-interval time
no ipv6 route static bfd holdover-interval
Command Default
By default, the BFD holdover interval is 0 seconds.
Parameters
time
Specifies the BFD holdover-time interval in seconds. Valid values range from 1 through 30. The
default is 0.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to revert to the default value of 0.
If the BFD session is restored within the specified time interval, no DOWN notification is sent.
Holdover interval values are configured globally and apply to all VRFs.
Examples
This example sets the BFD holdover interval globally for IPv6 static routes to 25.
This example removes the configured BFD holdover interval for IPv6 static routes.
Syntax
ipv6 router isis
Command Default
Disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command disables IS-IS routing for the interface.
Examples
The following example enables IS-IS routing for an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# ipv6 router isis
Syntax
ipv6 router ospf [ vrf name ]
no ipv6 router ospf
Command Default
Disabled.
Parameters
vrf name
Specifies a nondefault VRF.
Modes
Global configuration mode
Usage Guidelines
If you save the configuration to the startup-config file after disabling OSPFv3, all OSPFv3 configuration
information is removed from the startup-config file.
Use this command to enable the OSPFv3 routing protocol and enter OSPFv3 router or OSPFv3 router
VRFconfiguration mode. OSPFv3 maintains multiple instances of the routing protocol to exchange route
information among various VRF instances.
The no form of the command deletes all current OSPFv3 configurations and blocks any further OSPFv3
configuration.
Examples
The following example enables OSPFv3 on a default VRF and enters OSPFv3 router configuration mode.
Syntax
ipv6 subnet-zero drop
no ipv6 subnet-zero drop
Command Default
By default, packets destined for IPv6 subnet-router anycast addresses are allowed.
Modes
Global configuration mode
Usage Guidelines
When you have previously used the ipv6 subnet-zero drop command to drop packets destined
for IPv6 subnet-router anycast addresses, use the no form of the command to restore the default
configuration and allow IPv6 subnet anycast address traffic.
Examples
The following example configures dropping packets destined for IPv6 subnet anycast addresses.
device# configure terminal
device(config)# ipv6 subnet-zero drop
Syntax
ipv6 vrrp-extended auth-type md5-auth auth-text
no ipv6 vrrp-extended auth-type md5-auth
Command Default
No authentication is configured for a VRRP-E interface.
Parameters
md5-auth auth-text
Configures MD5 authentication on the interface. The maximum length of the text string is 64
characters.
Modes
Virtual Ethernet (VE) interface configuration mode
Usage Guidelines
This configuration is for VE interfaces only.
If the md5-auth option is configured, syslog and SNMP traps are generated if a packet is being
dropped due to MD5 authentication failure. Using MD5 authentication implies that the software does
not need to run checksum verification on the receiving device and can rely on the authentication code
(message digest 5 algorithm) to verify the integrity of the VRRP-E message header.
The no form of this command removes the VRRP-E authentication from the interface.
Examples
The following example configures MD5 authentication on VE interface 20.
ipv6 vrrp-extended-group
Configures an IPv6 VRRP-Ev3 group and enters into the VRRP-E configuration mode.
Syntax
ipv6 vrrp-extended-group group-ID
no ipv6 vrrp-extended-group group-ID
Parameters
group-ID
A number from 1 through 255 that you assign to the VRRP-Ev3 group.
Modes
Virtual Ethernet (VE) interface configuration mode
Usage Guidelines
Enter no ipv6 vrrp-extended-group group-ID to remove the specific IPv6 VRRP-Ev3 group.
If you remove a group, you cannot retrieve it. You would have to redo the configuration procedure.
This configuration is for virtual Ethernet (VE) interfaces only. IPv6 VRRP-Ev3 must be enabled on the
device before the IPv6 VRRP-E group is configured.
Examples
The following example shows how to assign the VE interface with a VLAN number of 2019 to the VRRP-
Ev3 group with the ID of 19.
ipv6 vrrp-group
Configures an IPv6 VRRPv3 group and enters into the virtual router configuration mode.
Syntax
ipv6 vrrp-group group-ID
no ipv6 vrrp-group group-ID
Parameters
group-ID
A value from 1 through 255 that you assign to the VRRPv3 group.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no ipv6 vrrp-group group-ID to remove a specific IPv6 VRRPv3 group. If you remove a
group, you cannot retrieve it. You would have to redo the configuration procedure.
IPv6 VRRPv3 must be enabled on the device before the IPv6 VRRP group is configured.
Examples
The following example shows how to assign an Ethernet interface to the VRRPv3 group with the ID of
18.
device# configure terminal
device(config)# ipv6 protocol vrrp
device(config)# interface ethernet 1/6
device(config-if-eth-1/6)# ipv6 address 2001:2019:8192::125/64
device(config-if-eth-1/6)# ipv6 vrrp-group 18
device(config-vrrp-group-18)#
ipv6 vrrp-suppress-interface-ra
Suppresses interface router advertisement (RA) when VRRPv3 is configured on an interface.
Syntax
ipv6 vrrp-suppress-interface-ra
no ipv6 vrrp-suppress-interface-ra
Command Default
Interface RA is enabled.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no ipv6 vrrp-suppress-interface-ra to remove the suppression of interface RA.
Router advertisements are sent by the VRRP master device and contain the link-local virtual IP address
and the virtual MAC address. For network security reasons, if you do not want the MAC addresses of
interfaces to be viewed, you can disable RA messages.
Examples
This example suppresses interface RA on a virtual Ethernet (VE) interface:
device# configure terminal
device(config)# ipv6 protocol vrrp
device(config)# interface ve 2019
device(config-Ve-2019)# ipv6 vrrp-suppress-interface-ra
is-type
Changes the Intermediate System-to-Intermediate System (IS-IS) level globally.
Syntax
is-type { level-1 | level-1-2 | level-2 }
no is-type { level-1 | level-1-2 | level-2 }
Command Default
The device operates as both a Level 1 (intra-area) and a Level 2 (interarea) device.
Parameters
level-1
Specifies that the device performs only Level 1 (intra-area) routing.
level-1-2
Specifies that the device performs both Level 1 and Level 2 routing.
level-2
Specifies that the device performs only Level 2 (interarea) routing.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command enables support for both IS-IS levels, if one level has been disabled.
Alternatively, the level-1-2 parameter can be used.
Examples
The following example changes the IS-IS level globally to Level-1 only.
device# configure terminal
device(config)# router isis
device(config-isis-router)# is-type level-1
The following example changes the IS-IS level globally to Level-2 only.
device# configure terminal
device(config)# router isis
device(config-isis-router)# is-type level-2
The following example changes the IS-IS level globally to Level-1 and Level-2 if support for one level has
previously been disabled.
device# configure terminal
device(config)# router isis
device(config-isis-router)# is-type level-1-2
isis auth-check
Enables authentication checking for an IS-IS interface.
Syntax
isis auth-check { level-1 | level-2 } disable
no isis auth-check { level-1 | level-2 } disable
Command Default
IS-IS authentication checking is enabled by default.
Parameters
level-1
Specifies Level 1 packets.
level-2
Specifies Level 2 packets.
disable
Disables authentication checking.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command disables IS-IS authentication checking for an IS-IS interface.
Examples
The following example disables IS-IS authentication checking for Level 1 packets for an IS-IS Ethernet
interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# isis auth-check disable
The following example re-enables IS-IS authentication checking for Level 2 packets for an IS-IS
loopback interface.
device# configure terminal
device(config)# interface loopback 1
device(config-Loopback-1)# isis auth-check
isis auth-key
Configures an authentication key for a specified Intermediate System-to-Intermediate System (IS-IS)
interface.
Syntax
isis auth-key { level-1 | level-2 } string
no isis auth-key { level-1 | level-2 } string
Command Default
Disabled.
Parameters
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
string
Specifies a text string that is used as an authentication password. The string can be from 1
through 63 ASCII characters in length.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The authentication mode must be configured on the interface using the isis auth-mode command
before a string can be configured. If the authentication mode is reset, the authentication key must
also be reset.
The no form of the command removes the configured authentication key for the IS-IS interface.
Note
MD5 passwords cannot have ASCII character 32 ('SPACE') as a part of the password string.
Examples
The following example configures an authentication key for Level 1 packets on an IS-IS Ethernet
interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# isis auth-key level-1 mykey
isis auth-mode
Specifies the type of authentication used for an Intermediate System-to-Intermediate System (IS-IS)
interface.
Syntax
isis auth-mode md5 { level-1 | level-2 }
no isis auth-mode md5 { level-1 | level-2 }
Command Default
Disabled.
Parameters
md5
Specifies message Digest 5 (MD5) authentication.
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example specifies that MD5 authentication is performed on Level 1 packets on an IS-IS
Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# isis auth-mode MD5 level-1
isis circut-type
Configures the type of adjacency used for an Intermediate System-to-Intermediate System (IS-IS)
interface.
Syntax
isis circut-type { level-1 | level-1-2 | level-2 }
no circut-type { level-1 | level-1-2 | level-2 }
Command Default
Level 1 and Level 2 adjacency is configured by default.
Parameters
level-1
Specifies Level 1 packets only.
level-1-2
Specifies Level 1 and Level 2 packets.
level-2
Specifies Level 2 packets only.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command resets the type of adjacency to the default value of Level 1 and Level 2
adjacency.
Examples
The following example configures Level 1 adjacency on an IS-IS Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(config-if-eth-1/1)# isis circut-type level-1
isis hello-interval
Specifies how often an Intermediate System-to-Intermediate System (IS-IS) interface sends hello
messages to its IS-IS neighbors.
Syntax
isis hello-interval { level-1 | level-2 } value
no isis hello-interval { level-1 | level-2 } value
Command Default
Disabled.
Parameters
level-1
Configures the hello interval for Level 1 only.
level-2
Configures the hello interval for Level 2 only.
value
Specifies the interval. Valid values range from 1 through 63 seconds. The default is 10.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command resets the hello interval to the default value of 10 seconds.
Examples
The following example changes the hello interval for Level 1 packets to 20 on an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# isis hello-interval level-1 20
The following example changes the hello interval for Level 2 packets to 40 on a loopback interface.
device# configure terminal
device(config)# interface loopback 1
device(config-Loopback-1)# isis hello-interval level-2 20
isis hello-multiplier
Specifies the number of Intermediate System-to-Intermediate System (IS-IS) hello packets a neighbor
must miss before the device declares adjacency as down.
Syntax
isis hello-multiplier { level-1 | level-2 } multiplier
no isis multiplier { level-1 | level-2 } multiplier
Command Default
The default is 3.
Parameters
level-1
Configures the hello multiplier for Level 1 adjacencies.
level-2
Configures the hello multiplier for Level 2 adjacencies.
multiplier
Specifies the multiplier. Valid values range from 3 through 1000. The default is 3.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The hello multiplier is the number by which an IS-IS interface multiplies the hello interval to obtain the
hold time for Level-1 and Level-2 IS-IS hello PDUs.
Examples
The following example changes the hello multiplier for Level 1 packets for an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# isis hello-multiplier level-1 10
The following example changes the hello multiplier for Level 2 packets for a loopback interface.
device# configure terminal
device(config)# interface loopback 1
device(config-Loopback-1)# isis hello-mulitplier level-2 20
Syntax
isis hello padding [ disable ]
no isis hello padding [ disable ]
Command Default
IS-IS hello padding is enabled.
Parameters
disable
Disables hello padding on the interface.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Generally, you do not need to disable padding unless a link is experiencing slow performance. If you
enable or disable padding on an interface, the interface setting overrides the global setting configured
using the hello padding command.
Examples
The following example re-enables IS-IS hello padding on an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(config-if-eth-1/1)# isis hello padding
Syntax
isis ipv6 metric { level-1 | level-2 } metric
no ipv6 metric { level-1 | level-2 } metric
Command Default
The default is 10.
Parameters
level-1
Specifies Level 1 only.
level-2
Specifies Level 2 only.
multiplier
Specifies the metric value. Valid values range from 1 through 16777215. The default is 10.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Each IS-IS interface has a separate metric value. In IPv6 IS-IS MT, different metrics are configured on an
interface for IPv4 and IPv6. When the metric value is configured for an interface, it rebuilds the route
LSP and triggers IPv6 IS-IS MT SPF calculation.
The no form of the command resets the metric value to the default value of 10.
Examples
The following example changes the metric value for Level 1 packets for an Ethernet interface under IPv6
IS-IS MT to 25.
The following example changes the metric value for Level 2 packets for a loopback interface under IPv6
IS-IS MT to 60.
isis ldp-sync
Enables synchronization with Intermediate System-to-Intermediate System (IS-IS) for an interface.
Syntax
isis ldp-sync { disable | enable}
no isis ldp-sync { disable | enable}
Command Default
Disabled.
Parameters
disable
Disables LDP synchronization.
enable
Enables LDP synchronization.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command disables synchronization with IS-IS for an interface.
Examples
The following example enables LDP synchronization for an ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# isis ldp-sync enable
isis metric
Configures the value of an Intermediate System-to-Intermediate System (IS-IS) metric.
Syntax
isis metric { level-1 | level-2 } metric
no metric { level-1 | level-2 } metric
Command Default
The default is 10.
Parameters
level-1
Specifies Level 1 only.
level-2
Specifies Level 2 only.
metric
Specifies the metric. Valid values range from 1 through 63 for the narrow metric style (the default
metric style for IPv4 ISIS). Valid values range from 1 through 16777215 for the wide metric style
(the default metric style for IPv4 ISIS).
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The device applies the interface-level metric to routes originated on the interface and when calculating
routes. The device does not apply the metric to link-state information received from one intermediate
system and flooded to other intermediate systems.
If the metric value you want to use is higher than 63 but you have not changed the metric style to wide,
you must change the metric style first, and then set the metric. The IS-IS neighbors that receive the
advertisements must also be enabled to receive wide metrics.
The no form of the command resets the metric value the default value of 10.
Examples
The following example changes the metric for an Ethernet interface, specifying Level 1 packets.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# isis metric 25 level-1
isis passive
Disables adjacency formation and advertisements on an Intermediate System-to-Intermediate System
(IS-IS) interface.
Syntax
isis passive
no isis passive
Command Default
Adjacency formation and advertisements is disabled on loopback interfaces. Adjacency formation and
advertisements is enabled on all other interfaces.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
A device advertises an IS-IS interface to its area regardless of whether adjacency formation is enabled.
The no form of the command re-enables adjacency formation and advertisements on the IS-IS
interface.
Examples
The following example disables adjacency formation and advertisements on an Ethernet interface.
device#configure terminal
device(config)# interface ethernet 2/2
device(conf-if-eth-2/2)# isis passive
The following example enables adjacency formation and advertisements on a loopback interface.
device#configure terminal
device(config)# interface looback 1
device(config-Loopback-1)# no isis passive
isis point-to-point
Configures the network type for the Intermediate System-to-Intermediate System (IS-IS) interface as
point-to-point.
Syntax
isis point-to-point
no isis point-to-point
Command Default
Disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command removes the configured point-to-point network type.
Examples
The following example configures a network type of point-to-point for an Ethernet interface.
device#configure terminal
device(config)# interface ethernet 2/2
device(conf-if-eth-2/2)# isis point-to-point
isis priority
Determines the priority of the interface for being elected as a Designated IS.
Syntax
isis priority { level-1 | level-2 } value
no isis priority { level-1 | level-2 } value
Command Default
The default is 64.
Parameters
level-1
Sets the priority for Level 1 only.
level-2
Sets the priority for Level 2 only.
value
Specifies the priority. Valid values range from 0 through 127. The default is 64.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
You can configure the same priority for both Level-1 and Level-2 or you can configure a different priority
for each level. If two or more devices have the highest priority within a given level, the device with the
highest MAC address becomes the Designated IS for that level.
You can set the IS-IS priority on an individual interface basis only. You cannot set the priority globally.
The no form of the command resets the priority value to the default value of 64.
Examples
The following example changes the priority for Level 1 packets for an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# isis priority level-1 100
The following example changes the hello multiplier for Level 2 packets for a loopback interface.
device# configure terminal
device(config)# interface loopback 1
device(config-Loopback-1)# isis priority level-2 80
isis reverse-metric
Configures the reverse metric value on a single Intermediate System-to-Intermediate System (IS-IS)
interface.
Syntax
isis reverse-metric [ value ] [ te-def-metric ] [ whole-lan ]
no isis reverse-metric [ value ] [ te-def-metric ] [ whole-lan ]
Command Default
Disabled.
Parameters
value
Specifies the reverse metric value in metric style. The narrow metric range is from 1 through 63.
The wide metric range is from 1 through 16777215. The default value is 16777214 irrespective of
the metric style configured.
whole-lan
Specifies that the configured reverse metric value affects the entire LAN.
te-def-metric
Specifies that the device sends a traffic engineering (TE) default metric sub-type-length-value
(TLV) within the reverse metric TLV.
Modes
Interface subtype configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
When the reverse metric value is configured, the local LSP is updated with the sum of the default metric
and the reverse metric value. When the IS-IS neighbor routing device receives the reverse metric value
through the IS hello, the neighbor router updates the cost to reach the original IS-IS router with the sum
of default metric and the reverse metric value. This helps in shifting traffic to the other alternate paths.
If the whole-lan option is not enabled, the reverse metric value affects only the neighbor router. The
whole-lan option takes effect only on the multi-access LAN. IS-IS point-to-point interfaces are not
affected when the whole-lan option is enabled.
The no form of the command removes the entire reverse metric configuration. The no form of the
command specified with the configured value resets the metric value to the default value of 16777214.
Examples
The following example configures a reverse metric value of 40 on an Ethernet interface. The whole-
lan option is enabled to include the entire LAN.
device#configure terminal
device(config)# interface ethernet 2/2
device(conf-if-eth-2/2)# isis reverse-metric 40 whole-lan
iterations
For an implementation of an event-handler profile, specifies the number of times an event-handler
action is run, when triggered.
Syntax
iterations num-iterations
no iterations
Command Default
When the trigger condition occurs, the event-handler actions runs once.
Parameters
num-iterations
Specifies the number of times an event-handler action is run, when triggered. Valid values are
any positive integer.
Modes
Event-handler activation mode
Usage Guidelines
The no form of this command resets the iterations setting to the default 1 iteration.
Examples
The following example specifies 5 iterations.
device# configure terminal
device(config)# event-handler activate eventHandler1
device(config-activate-eventHandler1)# iterations 5
ka-int-count
Configures the number of keepalive intervals after which the session is terminated when no session
keepalive or other LDP protocol message is received from the LDP peer.
Syntax
ka-int-count number
no ka-int-count number
Command Default
The default is a count of six intervals.
Parameters
number
Specifies the number of keepalive time intervals. Enter an integer from 1 to 65535.
Modes
MPLS LDP configuration mode
Usage Guidelines
Use the no form of the command to reset the default count of six intervals.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures a keepalive interval count of three.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# ka-int-count 3
ka-interval
Sets the keepalive time interval at which the session keepalive message is sent when no other LDP
protocol message is sent to the LDP peer.
Syntax
ka-interval seconds
no ka-interval seconds
Command Default
The default is six seconds.
Parameters
seconds
Specifies the keepalive time interval in seconds. Enter an integer from 1 throughk 65535.
Modes
MPLS LDP configuration mode
Usage Guidelines
The ka-interval and the ka-timeout configurations are mutually exclusive and you may have
only one configured at a time. You must explicitly remove the configuration for one in order to change
to the other configuration.
When the keepalive timeout value is configured, the show mpls ldp command displays keepalive
interval as keepalive timeout divided by the keepalive interval count (ka-timeout/ka-in-count).
Use the no form of the command to reset the default of six seconds.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures a keepalive interval of 10 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# ka-interval 10
ka-timeout
Sets the keepalive timeout after which the session is terminated when the keepalive or LDP protocol
message is not received.
Syntax
ka-timeout seconds
no ka-timeout seconds
Command Default
The default is six seconds.
Parameters
seconds
Modes
MPLS LDP configuration mode
Usage Guidelines
After an LDP session is established, an LSR maintains the integrity of the session by sending keepalive
messages. The keepalive timer for each peer session resets whenever it receives any LDP protocol
message or a keepalive message on that session. When the keepalive timer expires, LDP concludes that
the TCP connection is bad or the peer is dead and terminates the session.
When the keepalive timeout value is configured, the show mpls ldp command displays keepalive
interval as keepalive timeout divided by the keepalive interval count (ka-timeout/ka-in-count).
The ka-interval and the ka-timeout configurations are mutually exclusive and you may have
only one configured at a time. You must explicitly remove the configuration for one in order to change
to the other configuration.
Use the no form of the command to reset the default timeout of six seconds.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures a keepalive timeout of 180 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# ka-timeout 180
key
Specifies a text string to be used as a shared secret between the device and the Remote Authentication
Dial-In User Service (RADIUS) server.
Syntax
key shared_secret
no key
Command Default
The default value is "sharedsecret".
Parameters
shared_secret
The text string that is used as the shared secret between the device and the RADIUS server. The
default string is "sharedsecret". The exclamation mark (!) is supported for RADIUS servers, and
you can specify the shared secret string in either double quotation marks or by using the escape
character (\); for example, "secret!key" or secret\!key.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The key command does not support an empty string.
Examples
The following example shows how to configure the text string "new#radius*secret" as the shared secret
between the device and the RADIUS server.
key (keychain)
Configures a unique key ID in a key chain and enters key configuration mode.
Syntax
key key-id
no key key-id
Command Default
By default, a key ID is not configured.
Parameters
key-id
Specifies a unique key ID. Valid values range from 1 to 65535.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to remove the specified key and all associated configuration.
Examples
The following example configures a key with an ID of 10 in key chain 1.
device# configure terminal
device(config)# keychain keychain1
device(config-keychain1)# key 10
device(config-keychain1-key10)#
key-add-remove-interval
Alters the timing of the authentication key add-remove interval.
Syntax
key-add-remove-interval interval
no key-add-remove-interval interval
Parameters
interval
Specifies the add-remove interval in seconds. Valid values range from 0 through 14400. The
default is 300 seconds.
Modes
OSPFv3 router configuration mode
Usage Guidelines
The no form of the command resets the add-remove interval to the default value of 300 seconds.
Examples
The following example sets the key add-remove interval to 240 seconds.
key-algorithm
Defines the hash algorithm type for a specified key.
Syntax
key-algorithm { HMAC-SHA-1 | HMAC-SHA-256 | HMAC-SHA-384 | HMAC-SHA-512 }
no key-algorithm
Command Default
The default algorithm is HMAC SHA-256.
Parameters
HMAC-SHA-1 | HMAC-SHA-256 | HMAC-SHA-384 | HMAC-SHA-512
Specifies the hash algorithm for the selected key.
Modes
Key configuration mode
Usage Guidelines
Use the no form of the command to remove the hash algorithm configuration and revert to the default
value.
Examples
The following example configures SHA-256 for key 10 in key chain 1.
device# configure terminal
device(config)# keychain keychain1
device(config-keychain1)# key 10
device(config-keychain1-key10)# key-algorithm HMAC-SHA-256
key-rollover-interval
Alters the timing of the existing configuration changeover.
Syntax
key-rollover-interval interval
no key-rollover-interval interval
Parameters
interval
Specifies the key-rollover-interval in seconds. Valid values range from 0 through 14400. The
default is 300 seconds.
Modes
OSPFv3 router configuration mode
Usage Guidelines
In order to have consistent security parameters, rekeying should be done on all nodes at the same time.
Use the key-rollover-interval command to facilitate this. The key rollover timer waits for a
specified period of time before switching to the new set of keys. Use this command to ensure that all
the nodes switch to the new set of keys at the same time.
The no form of the command resets the rollover interval to the default value of 300 seconds.
Examples
The following example sets the key rollover interval to 420 seconds.
The following example re-sets the key rollover interval to the default value.
key-string
Configures a string of text to describe a key and, optionally, encrypts or decrypts the text string.
Syntax
key-string text-string [ encryption-level { 0 | 7}]
no key-string
Command Default
By default, no text string is configured.
Parameters
text-string
Describes the key with a maximum of 128 ASCII characters.
encryption-level { 0 | 7}
Defines the encryption level for the text string. Enter 0 for plain text or 7 for encrypted. The
default is 7.
Modes
Key configuration mode
Usage Guidelines
Use the no form of the command to remove the specified key and all associated configuration.You can
remove a key only if it is not used by an application.
Examples
The following example configures a key string of Mystring1 for key 10 in key chain 1.
device# configure terminal
device(config)# keychain keychain1
device(config-keychain1)# key 10
device(config-keychain1-key10)# key-string Mystring1
The following example configures a key string of Mystring1 with an encryption level of 0 for key 10 in key
chain 1.
device# configure terminal
device(config)# keychain keychain1
device(config-keychain1)# key 10
device(config-keychain1-key10)# key-string Mystring1 encryption-level 0
keychain
Creates a key chain and enters keychain configuration mode.
Syntax
keychain chain-name
no keychain chain-name
Command Default
By default, a key chain is not created.
Parameters
chain-name
Specifies an alphanumeric key chain name, with a minimum of 4 characters and a maximum of
32 characters.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to remove the configuration for the key chain.
You can remove a key chain only if it is not used by any application.
Examples
The following example creates 3 key chains.
device# configure terminal
device(config)# keychain keychain1
device(config-keychain1)# exit
device(config)# keychain keychain2
device(config-keychain2)# exit
device(config)# keychain keychain3
device(config-keychain3)#
keypair
Associates the generated RSA/ECDSA/DSA key pair with a trust point for security protocol exchanges
for applications.
Syntax
Associates the generated RSA/ECDSA/DSA key pair with the trust point.
keypair key_label
no keypair
Parameters
key_label
Specifies the name of the key pair to associate with the trust point.
Modes
Trust point configuration mode
Usage Guidelines
Use the no keypair command to remove the key pair association.
Examples
Typical command usage:
device(config)# crypto ca trustpoint t1
device(config-ca-t1)# keypair k1
device(config-ca-t1)# do show running-config crypto
crypto key label k1 rsa modulus 2048
crypto ca trustpoint t1
keypair k1
!
device# show crypto ca trustpoint
trustpoint: t1; key-pair: k1
label-withdrawal-delay
CLI_section_description
Delays sending a label withdrawal message for a FEC to a neighbor in order to allow the IGP and LDP to
converge.
Syntax
label-withdrawal-delay secs
no label-withdrawal-delay
Command Default
The default is 60.
Parameters
secs
Specifies the delay period in seconds for the label withdrawal delay timer. Enter value from 0 to
300.
Modes
MPLS LDP configuration mode.
Usage Guidelines
Setting the secs variable to zero (0) disables the feature for subsequent events.
Setting the secs variable to a value from 1 to 300, updates the configured value.
When using the no form of the command to restore the default behavior.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the label withdrawal delay timer to 30 seconds.
device(config-router-mpls-ldp)# label-withdrawal-delay 30
device(config-mpls-router-ldp)# no label-withdrawal-delay
device(config-mpls-router-ldp)# label-withdrawal-delay 0
lacp auto
Link Aggregation Control Protocol (LACP) enables bundling of multiple ethernet links into a single
logical bundle that provides better performance and redundancy than single links. LCAP can only be
configured on port-channel interfaces. Use this command to enable auto generation of ESI for these
LACP configured port-channel interfaces. The ESI is a 10-octet Hexadecimal identifier based on LACP
partner system identifier and port key. The same local port-channel id should be used by the multi-
homed leaf peers on links connected to the same host.
Syntax
lacp auto
[no] lacp auto
Parameters
auto
Enable auto assignment of ESI to the LACP enabled port-channel interface.
Modes
Ethernet Segment mode within the port-channel interface mode.
Usage Guidelines
Generates a 10-octet hexadecimal ESI value based on LACP partner system identifier and port key.
The no format of this command removes the ethernet segment identifier associated with this LACP
port-channel.
Examples
The following example shows how to enable auto assignment of ESI for a LACP enabled port-channel
interface.
SLX(config)# interface Port-channel 1
SLX(config-Port-channel-1)# ethernet-segment
SLX(config-Port-channel-1-es)# lacp auto
lacp default-up
Activates an Link Aggregation Control Protocol (LACP) link in the absence of PDUs.
Syntax
lacp default-up
no lacp default-up
Modes
Interface subtype configuration mode
Usage Guidelines
This command forces the port to activate an LACP link if there are no PDUs available on the interface
port.
This command is visible only if the interface is a dynamic and standard member of a port-channel.
Examples
The following example activates an LACP link in the absence of PDUs on an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 0/11
device(conf-if-eth-0/11)# lacp default-up
lacp port-priority
Configures the Link Aggregation Control Protocol (LACP) port priority of a member port of a port-
channel.
Syntax
lacp port-priority value
no lacp port-priority
Parameters
value
Specifies the priority. Valid values range from 1 through 65535. A lower number takes priority
over a higher number. The default value is 32768.
Modes
Interface subtype configuration mode.
Usage Guidelines
An LACP port priority is configured on each port using LACP. The port priority determines which ports
should be put in standby mode when there is a hardware limitation that prevents all compatible ports
from aggregating.
A link with higher priority (smaller in value) gets preference over a link with lower priority (greater in
value).
Examples
The following example sets the LACP port priority to 1000 for an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 0/2
device(conf-if-eth-0/2)# lacp port-priority 1000
lacp system-id
The command is used to assign local LACP System ID. The same System ID should be used by both
peers on the EVPN Multi-homing nodes.
Syntax
lacp system-id
[no] lacp system-id
Command Default
There are no defaults for this command.
Modes
Ethernet Segment mode. Allowed only under port-channel interface.
Usage Guidelines
This command is used to assign local LACP System ID. The same local port-channel id should be used
by the peers (on EVPN Multi-homing nodes).
Examples
The following example enables the Ethernet Segment mode which is allowed only under port-channel
interface.
SLX(config)# interface port-channel 1
SLX(config-Port-channel-1)# ethernet-segment
SLX(config-Port-channel-1-es)# lacp system-id 0011.2233.4455
lacp system-priority
Sets the Link Aggregation Control Protocol (LACP) system priority. The LACP priority determines which
system is responsible for resolving conflicts in the choice of aggregation groups.
Syntax
lacp system-priority value
no lacp system-priority
Command Default
The default value is 32768.
Parameters
value
Specifies the value of the LACP system priority. Valid values range from 1 through 65535.
Modes
Global configuration mode
Usage Guidelines
Lower numerical values have higher priorities.
Enter no lacp system-priority to reset the system priority to the default value.
Examples
The following example sets the LACP system priority value to 68.
device# configure terminal
device(config)# lacp system-priority 68
lacp timeout
Sets the timeout value used by the Link Aggregation Control Protocol (LACP) to exchange packets on
an interface before invalidating a received data unit (DU).
Syntax
lacp timeout { long | short }
no lacp timeout
Command Default
Tkhe default value is the short timeout.
Parameters
long
Specifies that a long-timeout value of 30 seconds will be used. With this value, the port waits
three times this long (90 seconds) before invalidating the information received earlier on this
PDU.
short
Specifies that a short-timeout value of one second will be used. With this value, the port waits
three times this long (three seconds) before invalidating the information received earlier on this
PDU.
Modes
Interface subtype configuration mode
Usage Guidelines
Use this command to set the timeout value based on how frequently you think the switch will receive
LACP PDUs from the partner device.
Make sure that the LACP timeout is the same for all connected devices.
Examples
The following example sets the LACP long-timeout value on an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 0/2
device(conf-if-eth-0/2)# lacp timeout long
lacp-pdu-forward enable
Configures the device to forward LACP PDUs received on an interface where LACP is not configured, to
the VLAN on which the LACP PDUs are received.
Syntax
lacp-pdu-forward enable
no lacp-pdu-forward enable
Command Default
LACP PDUs received on an interface where LACP is not configured are discarded.
Modes
Interface subtype configuration mode
Usage Guidelines
LACP PDUs are forwarded only when they are received on a physical interface or static port channel
interface. LACP PDUs cannot be forwarded if they are received on a LACP based dynamic port channel.
LACP PDU forwarding enabled on a static port channel applies to all the member ports.
When LACP is enabled on a port, it overrides LACP PDU forwarding configuration and the PDUs are
trapped to CPU.
Enabling and disabling of BPDU drop on a bridge domain does not impact LACP PDU forwarding.
Examples
The following example configures LACP PDU forwarding on a physical interface.
device# configure terminal
device(config)# interface ethernet 4/1
device(conf-if-eth-4/1)# lacp-pdu-forward enable
The following example configures LACP PDU forwarding on a static port channel interface.
device# configure terminal
device(config)# interface port-channel 10
device(config-Port-channel-10)# lacp-pdu-forward enable
lag hash
Configures LAG hashing parameters such as where to start picking headers for key generation, the
number of headers to be considered, and so forth.
Syntax
lag hash bos { skip | start }
no lag hash bos { skip | start }
lag hash hdr-count count
no lag hash hdr-count count
lag hash hdr-start { fwd | term }
no lag hash hdr-start { fwd | term }
lag hash normalize
no lag hash normalize
lag hash pwctrlword
no lag hash pwctrlword
lag hash rotate rotate-number
no lag hash rotate rotate-number
lag hash speculate-mpls { enable | inner-eth | inner-ip-raw | inner-ip-
tag | inner-ipv6-raw | inner-ipv6-tag}
no lag hash speculate-mpls
lag hash srcport
no lag hash srcport
Parameters
bos
(DNX devices only) Ignore the entire MPLS label stack and pick only the BOS label for hashing.
skip
Hash from the label following the BOS label.
start
(Default) Start from the BOS label.
hdr-count count
Specifies the number of headers to be considered for LAG hashing. Values range from 1 through
3. The default is 3.
hdr-start
Specifies where to start picking headers for the key generation.
fwd
(Default) Start from the inner header, which is used for forwarding the packet.
term
Start from the outer header, which is the header below the forwarding header and is the last
terminated header.
normalize
(DNX devices only) Configures using the same hash in both directions. The default is disabled.
pwctrlword
(DNX devices only) Include the PW control word in hashing. The default is disabled.
rotate rotate-number
(DNX devices only) Specify hashing randomness. Values range from 0 through 15. The default is
3.
speculate-mpls
(DNX devices only) Enable MPLS speculate or Ethernet/IP.
enable
Enable Speculative MPLS.
inner-eth
Enable inner Ethernet header hash for L2VPN.
inner-ip-raw
Enable inner IPv4 header hash for L2VPN raw mode.
inner-ip-tag
Enable inner IPv4 header hash for L2VPN tag mode
inner-ipv6-raw
Enable inner IPv6 header hash for L2VPN raw mode
inner-ipv6-tag
Enable inner IPv6 header hash for L2VPN tag mode
srcport
Includes the source port in the hashing configuration. The default is not to include it.
Modes
Global configuration mode
Usage Guidelines
To restore default settings, use the no forms of these commands.
Examples
The following example changes the hdr-count value to 2.
device# configure terminal
device(config)# lag hash hdr-count 2
ldap-server host
Configures an LDAP server to connect for external or remote authentication.
Syntax
ldap-server host [ use-vrf { mgmt-vrf | default-vrf |vrf-name } ]
ldap-server host { ipaddr | hostname } [ port portnum ] [ ldaps ][ domain
basedn ] [ timeout secs ] [ retries num ]
ldap-server host { ipaddr | hostname }[source-interface { ethernet eth-id
| loopback loopback-id | management mgmt-addr | ve ve-id } ]
no ldap-server host{ ipaddr | hostname }[source-interface { ethernet
eth-id | loopback loopback-id | management mgmt-addr | ve ve-id } ]
no ldap-server host { ipaddr | hostname } [use-vrf vrf-name ]
Command Default
By default, the LDAP server is not configured.
Parameters
use-vrf
Specifies a VRF though which to communicate with the LDAP server.
mgmt-vrf
(Default) Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf-name
Specifies a VRF name.
ipaddr | hostname
Specifies the IPv4 or IPv6 address or host name of the LDAP server. IPv6 is supported for
Windows 2008 AD server only. The maximum supported length for the LDAP host name is 40
characters.
port portnum
Specifies the TCP port used to connect the LDAP server for authentication. The port range is
from 1024 through 65535. By default, port 389 is used for the startTLS method and port 636 is
used for LDAP over TLS.
ldaps
Specifies that LDAP over TLS is to be used instead of startTLS.
domain basedn
Describes the base domain name of the host.
timeout secs
Specifies the wait time for a server to respond. The range is 1 through 60 seconds. The default is
5 seconds.
retries num
Specifies the number of retries for the server connection. The range is 0 through 100. The default
is 5.
source-interface
Indicates the type of interface to use as the source interface or address.
ethernet eth-id
Specifies the Ethernet interface to use as the source interface, in slot/port format (0/1).
loopback loopback-id
Specifies the Loopback interface to use as the source interface.
management mgmt-addr
Specifies the management address (active MM or chassis IP) to use as the source address.
ve ve-id
Specifies the VE interface to use as the source interface.
Modes
Global configuration mode
Usage Guidelines
Use this command to set up or change a connection to the Lightweight Directory Access Protocol
(LDAP) server host. A maximum of 5 LDAP servers can be configured on a device.
Use the no ldap-server host form of the command to delete the server configuration.
When a source interface is not specified, the default source is the IP address of the interface from which
the packet egresses.
If, at run time, the source interface is not up or the IP address for the source interface was not
configured, the command behaves as though the source interface was not configured.
Examples
This example adds an LDAP server on port 3890 with retries set to 3.
device(config)# ldap-server host 10.24.65.6
device(config-host-10.24.65.6/mgmt-vrf)# domain sec.extreme.com port 3890 retries 3
This example shows how attributes that hold default values are not displayed.
device(config-host-10.24.65.6/mgmt-vrf)# do show running-config ldap-server host
10.24.65.6
ldap-server host 10.24.65.6 use-vrf mgmt-vrf
port 3890 retries 3 timeout 8 basedn security.extreme.com
ldap-server maprole
Maps an Active Directory (AD) group to a device role.
Syntax
ldap-server maprole group group_name role role_name
no ldap-server maprole group group_name
Parameters
group group_name
The name of the AD group.
role role_name
The name of the device role.
Modes
Global configuration mode
Usage Guidelines
Enter no ldap-server maprolegroup group_name without the role role_name parameter
to remove the mapping of the AD group to a role.
Examples
To map the AD group "Administrator" to the device role "admin":
ldp
Enables the Label Distribution Protocol (LDP) mode to configure LDP global parameters.
Syntax
ldp
no ldp
Modes
MPLS configuration mode
Usage Guidelines
Use the no form of this command to remove the LDP configurations from the device.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables LDP configuration mode.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
ldp-enable
Enables LDP on an interface.
Syntax
ldp-enable
no ldp-enable
Modes
MPLS interface configuration mode
Usage Guidelines
For an LDP session between routers, you must configure LDP on an interface to allow the device to
advertise its loopback interface to the peers.
To use LDP, configure a loopback address with a 32-bit mask on the LSR. The first loopback address
configured on the device is used in its LDP identifier. When the loopback address used in the LDP
identifier is removed, all LDP functions on the LSR are shut down. LDP sessions between the LSR and its
peers are terminated, and LDP-created tunnels are removed. When other loopback interfaces are
configured on the device, the lowest-numbered loopback address is used as a new LDP identifier. LDP
sessions and tunnels are set up using this new LDP identifier.
Configure LDP on the same set of interfaces that IGP routing protocols such as OSPF and IS-IS are
enabled.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures LDP on an interface.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/2
device(config-router-mpls-interface-0/2)# ldp-enable
ldp-params
Allows you to access ldp-params subconfiguration mode to configure LDP parameters on an interface.
Syntax
ldp-params
no ldp-params
Modes
MPLS interface configuration mode
Usage Guidelines
When you use this command, you can configure the LDP Hello interval and timeout parameters on the
interface.
Use the no form of the command to remove the LDP parameter configuration.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example accesses ldp-params subconfiguration mode.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/2
device(config-router-mpls-interface-0/2)# ldp-params
device(config-router-mpls-interface-0/2-ldp-params)#
ldp-sync
Enables Multiprotocol Label Switching (MPLS) Label Distribution Protocol-Interior Gateway Protocol
(LDP-IGP) synchronization globally with Intermediate System-to-Intermediate System (IS-IS) or Open
Shortest Path First (OSPF), and configures the hold-down time interval.
Syntax
ldp-sync [ hold-down seconds ]
no ldp-sync [ hold-down ]
Command Default
Disabled.
Parameters
hold-down seconds
Sets the LDP-IGP synchronization hold-down time interval in seconds. The IGP must advertise
the maximum IP metric while waiting for an update from the LDP. Valid values range from 1
through 65535 seconds. The default is 30.
Modes
OSPF router configuration mode
Usage Guidelines
The ldp-sync command supports point-to-point interfaces, but not tunnel interfaces.
The no ldp-sync hold-down command resets the hold down time interval to the default setting of
30 seconds.
MPLS and IS-IS are supported only on devices based on the DNX chipset family. For a list of such
devices, see "Supported Hardware".
Examples
The following example enables MPLS LDP-IGP synchronization globally with OSPF and IS-IS, and sets
the hold-down time interval to 100 seconds.
left-interface vlan
Configures an Ethernet Ring Protection (ERP) left interface.
Syntax
left-interface vlan vlan_id { ethernet slot/port | port-channel number }
no left-interface vlan vlan_id { ethernet slot/port | port-channel
number }
Command Default
No ERP left interface is configured by default.
Parameters
vlan_id
Specifies the VLAN ID of the ERP left ring interface. Range is from 1 through 4090.
ethernet slot/port
Specifies an Ethernet interface.
port-channel number
Specifies a port-channel.
Modes
ERP configuration mode
Usage Guidelines
Each Ethernet Ring Node (ERN) in a major ring must have explicitly defined left and right interfaces so
that ERP can function properly. ERNs in a sub-ring must have at least one interface defined so that ERP
can function properly.
For proper operation you must configure the interfaces following the same manner on each ERN, such
as left/ right, left/ right, and so on.
You must configure the VLAN and configure the Ethernet or port-channel interfaces as switchport, and
then add the VLAN to the interfaces either in trunk or access mode. This is a prerequisite to configuring
the ERP left interface.
Examples
The following example configures a left interface on an Ethernet interface.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# left-interface vlan 5 ethernet 0/1
license add
Adds a license key to a switch.
Syntax
license add { licstr licenseString | FTP-URL ftpPath | SCP-URL scpPath }
[ slot slot-number ]
Command Default
This command is executed on the local switch.
Parameters
licstr licenseString
Specifies the license string to be added to the switch. The license string must be enclosed in
double quotation marks. A maximum of 256 characters is allowed.
FTP-URL ftpPath
Specifies a URL from which to transfer license information using FTP. ftp://
username:password@hostname filepath
SCP-URL scpPath
Specifies a URL from which to transfer license information using SCP. scp://
username:password@hostname/ filepath
slot slot-number
Specifies the LC slot number where the license key is added. The slot zero refers to the chassis
license. The non-zero slot number refer to the physical slot number on the LC, as displayed in the
output of the show slot command.
Modes
Privileged EXEC mode
Usage Guidelines
Depending on the feature being added, you may need to disable and re-enable the affected ports for
this command to take effect. Follow the instructions in the command output.
If you install a license on an unsupported platform, the operation succeeds, but the show license
output indicates that the license is not supported.
Examples
To add a license on slot 1:
20141113164801170PORT_UPGRADE.xml slot 1
license eula
Enables the user to accept or decline the EULA for a SAU licensed feature.
Syntax
license eula { accept feature | decline feature }
Command Default
This command is executed on the local switch.
Parameters
accept
Specifies that the user wants to use the feature without an installed license.
feature
Specifies the displayed license feature name.
decline
Specifies that the user no longer want to use the unlicensed SAU feature.
Modes
Privileged EXEC mode.
Usage Guidelines
When the license eula accept command is entered, you are agreeing to purchase a license
within a specific timeframe. You can begin using the features immediately. Use the show license
command to display the SAU license when the EULA is accepted.
When the license eula decline command is entered, you are no longer able to use the licensed
features. Before you can decline the licensed features, all configuration settings related to the feature
must be restored to default settings.
Examples
The following example shows how to accept the EULA for the SAU license (Advanced Features).
License-Agreement.pdf].
You can decline the EULA acceptance now by entering "license eula decline
ADVANCED_FEATURES"
at the CLI prompt; declining the EULA will prevent use of the licensed feature.
The following CLI message is displayed when you attempt to configure a feature that requires a SAU
license, and you have not accepted the EULA and there is no SAU license installed for that feature.
No ADVANCED_FEATURES EULA accepted for this feature
Syntax
line vty exec-timeout timeout
no line vty exec-timeout
Command Default
If no value is specified, the timeout value is 10 minutes.
Parameters
timeout
Specifies the CLI session timeout period in minutes. The timeout value specifies the amount of
time a CLI session can be idle before it logs you out. Valid values range from 0 through 136. The
default is 10.
Modes
Global configuration mode
Usage Guidelines
The line vty exec timeout command is a recurrent command, applying to all login sessions. The
terminal timeout command applies only to the current session.
Even if other keys are pressed during the timeout period, the only keystroke that prevents logout is
Enter.
To restore the default timeout value of 10 minutes, enter no line vty exec-timeout.
Examples
The following example sets the terminal timeout to 60 minutes.
device(config)# line vty exec-timeout 60
device(config-line-vty)# exit
device(config)# exit
device# show running-config line vty
line vty
exec-timeout 60
!
link-error-disable
Configures port flap dampening for the interface, including the threshold of link flapping to shut down
the port and the time interval in which it remains shut down.
Syntax
link-error-disable toggle-threshold sampling-time-in-sec wait-time-in-sec
no link-error-disable
Command Default
Port flap dampening is disabled on the device.
Parameters
toggle-threshold
Specifies the number of times a port link state goes from up to down and down to up before the
wait period is activated. The value ranges from 1 through 50.
sampling-time-in-sec
Specifies the amount of time, in seconds, during which the specified toggle threshold can occur
before the wait period is activated. Enter an integer from 1 through 65535.
wait-time-in-sec
Specifies the amount of time, in seconds, for which the port remains disabled (down) before it
becomes enabled. The value ranges from 0 through 65535. A value of 0 indicates that the port
will stay down until an administrative override occurs.
Modes
Interface Ethernet configuration mode
Usage Guidelines
Use the no form of the command to disable port flap dampening.
Port flap dampening allows you to configure a wait period before a port, whose link goes down then up,
becomes enabled. This feature is available for all front ports on the device.
If the port link state toggles, from down to up or from up to down, for a specified number of times
within a specified period, the interface is physically disabled for the specified wait period. Once the wait
period expires, the port’s link state is re-enabled. However, if the wait period is set to zero (0) seconds,
or you want to re-enable the port before the wait period expires, the port must be manually re-enabled.
To re-enable the port, reenter the link-error-disable command on the disabled port.
Examples
The following example shows the configuration of port flap dampening. The toggle threshold is set to 10
times. The sampling time is set to 3 seconds. The wait time is set to 10 seconds.
device# configure terminal
device(config)# interface Ethernet 1/4
device(conf-if-eth-1/4)# link-error-disable 10 3 10
link-fault-signal
Configures RX and TX Link Fault Signaling (LFS) detection globally or on an interface port.
Syntax
link-fault-signal rx { off | on } tx { off | on
no link-fault-signal
Command Default
Both TX and RX LFS are enabled.
Parameters
rx
Configure RX LFS detection.
off
Disables LFS.
on
Enables LFS.
tx
Configure TX LFS detection.
Modes
Global and interface configuration modes
Usage Guidelines
Use the no form of the command to reset RX and TX LFS to their default settings of enabled.
The interface must be in the shutdown state before you disable or enable TX LFS.
All SLX devices support LFS detection for interface types of 10G, 40G, 100G, and 40G breakout ports. It
detects local and remote faults.
When the device detects a local fault, it returns a remote fault to the link partner. When the device
detects a remote fault, it returns an idle state.
A port's physical link detection is independent of LFS detection. When either of these link fault signals is
detected, the following behaviors occur:
• The link is declared as DOWN and the management interface should display Protocol Down on the
SLX-OS CLI.
• The physical link is not bought down in both of the previous cases. The peer side based on its
implementation might display that the link is UP when the device displays that the link is DOWN due
to a fault detection.
• The transmit (TX) packets, if any, are dropped at the MAC layer. The receive (RX) packets, if any, are
dropped in the software.
• The detected signal is reported as a RASTRACE message. The same information is reported on the
management interface as a RASLOG. The same behavior occurs when the signal is cleared.
You can enable or disable LFS globally and on the interface level for both RX and TX directions:
• If the LFS is enabled for RX, the normal local and remote fault detection and processing described
previously occur. If it is disabled for RX, local and remote fault detection are ignored.
• If the LFS is enabled for TX and a local fault occurs, a remote fault (pause frame) is generated to the
remote side. If it is disabled for TX, the remote fault is not generated.
Examples
The following example shows the global and interface configuration of LFS. In this example, the global
LFS is disabled for the link fault RX and enabled for link fault TX. The LFS for the interface is enabled for
the link fault RX and disabled for the link fault TX, overriding the global configuration.
device# configure terminal
device(config)# link-fault-signaling rx off tx on
device(config)# interface Ethernet 0/1
device(conf-if-eth-0/1)# shutdown
device(conf-if-eth-0/1)# link-fault-signaling rx on tx off
device(conf-if-eth-0/1)# no shutdown
link-oam allow-loopback
Enables an interface to accept remote loopback.
Syntax
link-oam allow-loopback
no link-oam allow-loopback
Command Default
Allow loopback is disabled.
Modes
Ethernet interface configuration mode
Usage Guidelines
You can allow loopback on one device port only.
The no form of the command disables the interface from accepting loopback.
Examples
device# configure terminal
device(config)# interface ethernet 0/1
device(config-int-eth-0/1)# link-oam allow-loopback
link-oam enable
Enables link oam on an ethernet interface and sets the mode to active or passive.
Syntax
link-oam enable [active | passive]
no link-oam enable
Command Default
Please refer the usage guidelines.
Parameters
active
Configures link-oam in active mode.
passive
Configures link-oam in passive mode.
Modes
Ethernet interface configuration mode
Usage Guidelines
By default, link oam is disabled on the interface. Once this CLI is configured, it cannot be modified. In
order to reconfigure, link-oam has to be deconfigured using no link-oam enable command.
Examples
device# configure terminal
device(config)# interface ethernet 1/1
device(config-int-eth1/1)# link-oam enable passive
link-oam remote-failure
Blocks the interface on receipt of a remote failure message, in addition to the syslog generation.
Syntax
link-oam remote-failure {link-fault | dying-gasp | critical-event} action
block-interface
Command Default
Please refer the usage guidelines.
Parameters
link-fault
Blocks the interface on receipt of a link failure message.
dying-gasp
Blocks the interface on receipt of a dying-gasp message.
critical-event
Blocks the interface on receipt of a critical event message.
Modes
Ethernet interface configuration mode
Usage Guidelines
To run this command, the Link OAM must be configured. By default, on receipt of a remote failure
message, the device will only log the event through syslog. This command allows block-interface action
to be configured for each of the three events that the protocol supports.
Examples
device(config-int-eth1/1)# link-oam remote-failure link-fault action block-interface
device(config-int-eth1/1)# link-oam remote-failure dying-gasp action block-interface
link-oam remote-loop-back
Starts and stops the remote loopback on peer that is connected to a local ethernet interface.
Syntax
link-oam remote-loop-back ethernet slot-number / port-number [ start |
stop]
Parameters
slot-number
Specifies the slot number. For devices without linecards, specify 0.
port-number
Specifies the port number.
start
Start the remote loopback on peer that is connected to the interface.
stop
Stops the remote loopback on peer that is connected to the interface.
Modes
Privileged EXEC mode
Examples
device# link-oam remote-loop-back ethernet 0/1 start
listen-limit
Sets a global limit for BGP4 or BGP4+ dynamic subnet range neighbors.
Syntax
listen-limit max-num
no listen-limit
Command Default
The default listen limit value is 100.
Parameters
max-num
Specifies the listen limit value. Valid values range from 1 through 255.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores the default value.
When the global or peer level limit is increased, any new connection is accepted when it comes in from
the remote end and falls under the range.
If the limit has been reached and you reduce the global or peer-group limit, the previously
ESTABLISHED dynamic neighbors are not destroyed. You must use the clear neighbor command.
When the new sessions are created, the device uses the updated limit. If the limit has been reached and
a request for new connection is received, the connections are not accepted and the information is
logged.
Examples
The following example limits the number of BGP4 dynamic neighbors that can be created to 150
globally.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# listen-limit 150
**Warning: The dynamic neighbor range limit has been changed. Please use
clear bgp neighbor dynamic command for limit to take effect.
device(config-bgp-router)# clear ip bgp neighbor dynamic all
The following example restores the number of BGP4+ dynamic neighbors that can be created to the
default value of 100.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# no listen-limit
**Warning: The dynamic neighbor range limit has been changed. Please use
clear bgp neighbor dynamic command for limit to take effect.
device(config-bgp-router)# clear ipv6 bgp neighbor dynamic all
listen-range
Associates a subnet range with a BGP4 or BGP4+ peer group and sets the maximum number of BGP
dynamic neighbors that can be created for this range.
Syntax
listen-range ip address/mask peer-group peer-group-name [ limit num ]
no listen-range ip address/mask peer-group peer-group-name
Command Default
Disabled.
Parameters
ip address/mask
Specifies an IPv4 or IPv6 address and network mask.
peer-group peer-group-name
Specifies a peer group.
limit num
Specifies the listen limit value. Valid values range from 1 through 255.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command deletes the listen range and tears down all dynamic neighbors formed for
this range.
Examples
This example associates a subnet range of 10.1.0.0/16 with a peer group called “mypeergroup” and sets
the maximum number of BGP4 dynamic neighbors that can be created to 80.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# listen-range 10.1.0.0/16 peer-group mypeergroup limit 80
This example associates a subnet range of 2000:1:1::/48 with a peer group called "leaf-group."
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# listen-range 2000:1:1::/48 peer-group leaf-group
lldp profile
Applies a Link Layer Discovery Protocol (LLDP) profile to an interface.
Syntax
lldp profile name
no lldp profile
Command Default
LLDP profile name.
Parameters
name
Specifies the profile name. Valid profile name length is between 1 and 32 characters.
Modes
Interface subtype configuration mode
Usage Guidelines
You must use the lldp profile command to create an LLDP profile before you can apply the profile
to the interface. Only one LLDP profile can exist at any time for a particular interface. When this
command is not present, the parameters defined in the global LLDP configuration are used.
Examples
To apply an LLDP profile called test on an specific Ethernet interface:
device# configure terminal
device(config)# interface ethernet 0/9
device(conf-if-eth-0/9)# lldp profile test
load-balance hash
For supported header types, selects the fields used for LAG hashing.
Syntax
load-balance hash ethernet { da-mac | etype | sa-mac | vlan }
no load-balance hash ethernet [ da-mac | etype | sa-mac | vlan ]
load-balance hash ip { dst-ip | dst-l4-port | protocol | src-ip | src-l4-
port }
no load-balance hash ip [ dst-ip | dst-l4-port | protocol | src-ip | src-
l4-port ]
load-balance hash ipv6 { ipv6-dst-ip | ipv6-dst-l4-port | ipv6-next-hdr |
ipv6-src-ip | ipv6-src-l4-port }
no load-balance hash ipv6 [ ipv6-dst-ip | ipv6-dst-l4-port | ipv6-next-
hdr | ipv6-src-ip | ipv6-src-l4-port ]
load-balance hash mpls { label1 | label2 | label3 }
no load-balance hash mpls [ label1 | label2 | label3 ]
Command Default
All header parameters are enabled.
Parameters
ethernet
da-mac
Specifies Layer 2 destination address.
etype
Specifies the etype option.
sa-mac
Specifies Layer 2 source address.
vlan
Specifies the vlan option.
ip
dst-ip
Specifies destination IP address.
dst-l4-port
Specifies destination Layer 4 port.
protocol
Specifies the IP protocol.
src-ip
Specifies source IP address.
src-l4-port
Specifies source Layer 4 port.
ipv6
ipv6-dst-ip
Specifies destination IPv6 address.
ipv6-dst-l4-port
Specifies IPv6 destination Layer 4 port.
ipv6-next-hdr
Specifies next IPv6 header.
ipv6-src-ip
Specifies source IPv6 address.
ipv6-src-l4-port
Specifies IPv6 source Layer 4 port.
mpls
(Not supported for SLX 9150 or SLX 9250 devices)
label1
Specifies MPLS label 1.
label2
Specifies MPLS label 2.
label3
Specifies MPLS label 3.
Modes
Global configuration mode
Usage Guidelines
The no forms of these commands cancel selection of the relevant protocol headers for LAG hashing.
Examples
The following example specifies Layer 2 destination address.
device# configure terminal
device(config)# load-balance hash ethernet da-mac
The following example cancels the default enablement of IPv4 headers for hashing. It then enables IPv4
source IP address only.
device# configure terminal
device(config)# no load-balance hash ip
device(config)# load-balance hash ip src-ip
load-sharing
Configures the maximum number of LDP ECMP paths.
Syntax
load-sharing number
no load-sharing
Command Default
The default number of ECMP paths is one.
Parameters
number
Specifies the maximum number of LDP ECMP paths. Enter an integer from 1 to 16.
Modes
MPLS LDP configuration mode
Usage Guidelines
The number of LDP ECMP paths for transit LSR depends on the number of eligible paths that are
available, and the maximum number of LDP ECMP paths that you can configure.
Examples
The following example configures a maximum of four LDP ECMP paths.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# load-sharing 4
local-as
Specifies the BGP autonomous system number (ASN) where the device resides.
Syntax
local-as num
no local-as num
Command Default
No ASN is specified.
Parameters
num
The local ASN. The range is from 1 through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
ASNs in the range from 64512 through 65535 are private numbers that are not advertised to the
external community.
The no form of the command removes the ASN from the device.
Examples
This example assigns a separate local AS number.
local-switching
Configures the local switching mode for a bridge domain.
Syntax
local-switching
no local-switching
Command Default
Local switching is enabled.
Parameters
local-switching
Enables local switching.
Modes
Bridge-domain configuration mode.
Usage Guidelines
This feature is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Local switching allows packets to be switched within a VPLS bridge domain. This command only applies
to multipoint-service bridge domains; that is, bridge domains configured with the p2mp option.
The no form of the command disables local switching in a VPLS bridge domain.
To avoid receipt of traffic with different VLAN tags on local endpoints in a bridge domain that has a PW
profile with VC mode set to raw-passthrough, it is recommended that local switching is disabled.
Raw passthorugh mode is designed to forward packets between two VPLS peer devices and is not
intended for use with local switching.
Examples
The following example disables local switching in VPLS bridge domain 10.
log (OSPFv2)
Controls the generation of OSPFv2 logs.
Syntax
log { adjacency [ dr-only ] | all | bad-packet [ checksum ] | database |
retransmit }
no log { adjacency [ dr-only ] | all | bad-packet [ checksum ] | database
| retransmit }
Command Default
Only OSPFv2 messages indicating possible system errors are logged.
Parameters
adjacency
Specifies the logging of essential OSPFv2 neighbor state changes.
dr-only
Specifies the logging of essential OSPF neighbor state changes where the interface state is
designated router (DR).
all
Specifies the logging of all syslog messages.
bad-packet
Specifies the logging of bad OSPFv2 packets.
checksum
Specifies all OSPFv2 packets that have checksum errors.
database
Specifies the logging of OSPFv2 LSA-related information.
retransmit
Specifies the logging of OSPFv2 retransmission activities.
Modes
OSPF router configuration mode
Usage Guidelines
Use this command to disable or re-enable the logging of specific events related to OSPFv2. If this
command is not enabled only OSPFv2 messages indicating possible system errors are logged.
A limitation with the dr-only sub-option is that when a DR/BDR election is underway, OSPF neighbor
state changes pertaining to non-DR/BDR routers are not logged. Logging resumes once a DR is elected
on that network.
Examples
The following example enables the logging of all OSPFv2-related syslog events.
log (OSPFv3)
Controls the generation of OSPFv3 logs.
Syntax
log { adjacency [ dr-only ] | all | bad-packet [ checksum ] | database |
retransmit }
no log { adjacency | all | bad-packet [ checksum ] | database |
retransmit }
Command Default
Only OSPFv3 messages indicating possible system errors are logged.
Parameters
adjacency
Specifies the logging of essential OSPFv3 neighbor state changes.
dr-only
Specifies the logging only of designated router (DR) interface adjacency changes.
all
Specifies the logging of all syslog messages.
bad-packet
Specifies the logging of bad OSPFv3 packets.
checksum
Specifies all OSPFv3 packets that have checksum errors.
database
Specifies the logging of OSPFv3 LSA-related information.
retransmit
Specifies the logging of OSPFv3 retransmission activities.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Use this command to disable or re-enable the logging of specific events related to OSPFv3. If this
command is not enabled, only OSPFv3 messages indicating possible system errors are logged.
Examples
The following example enables the logging of all OSPFv3-related syslog events.
log adjacency
Logs changes in the status of an adjacency with another intermediate system (IS).
Syntax
log adjacency
no log adjacency
Command Default
Disabled.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables logging of adjacency changes.
device# configure terminal
device(config)# router isis
device(config-isis-router)# log adjacency
log invalid-lsp-packets
Logs invalid Link State PDUs (LSPs) packets.
Syntax
log invalid-lsp-packets
no log invalid-lsp-packets
Command Default
Disabled.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command disables the logging of invalid LSP packets.
Examples
The following example enables logging of invalid LSP packets.
device# configure terminal
device(config)# router isis
device(config-isis-router)# log invalid-lsp-packets
log-dampening-debug
Logs dampening debug messages.
Syntax
log-dampening-debug
no log-dampening-debug
Command Default
This option is disabled.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
Examples
The following example logs dampening debug messages.
log-shell
Controls the remote logging of SLXVM Linux shell command activities.
Syntax
log-shell { start | status | stop }
Command Default
By default, the device logs the SLXVM Linux shell access and all commands executed at the SLXVM
Linux shell locally.
Parameters
start
Restarts remote logging.
status
Checks the remote logging status.
stop
Disables remote logging.
Modes
Privileged EXEC mode
Usage Guidelines
Changes of the log-shell stop and log-shell start commands are applicable only on new
SLXVM Linux shell sessions.
If you configure a remote Syslog server, the same logs can be seen on this server.
When you disable remote logging, local logging of user activities continues.
Examples
The following example disables remote logging.
device# log-shell stop
Syntax
logging auditlog class class
no logging auditlog class class
Command Default
CONFIGURATION, FIRMWARE, and SECURITY audit log classes are enabled.
Parameters
class
Specifies the class name of the audit log. Valid classes are CONFIGURATION, FIRMWARE, and
SECURITY.
Modes
Global configuration mode
Usage Guidelines
The total message storage available is 2048 messages.
Enter no logging auditlog class class to disable the audit logging for the specified class.
Examples
To enable a specific audit log class:
device# configure terminal
device(config)# logging auditlog class security
device(config)#
Syntax
logging raslog console severity
no logging raslog console severity
Command Default
Severity level is INFO.
Parameters
severity
Specifies the minimum severity level of the message to pass through the filter. Valid values
consist of one of the following: INFO, WARNING, ERROR, or CRITICAL. Input values are case-
sensitive.
Modes
Global configuration mode
Usage Guidelines
The total message storage available is 2048 messages.
Examples
To reset the RASLog severity levels to the default value.
device# configure terminal
device(config)# no logging raslog console
2013/11/14-08:42:57, [RAS-3008], 5348, M2 | Active, INFO, VDX8770-4, Logging messages to
console has been reset by user.
Syntax
logging raslog console { start | stop [ minutes ] }
Command Default
RASlog messages display on the console
Parameters
start
Initiates RASLog messages.
stop minutes
Stops RASLog messages for a designated number of minutes.
Modes
Privileged EXEC mode
Usage Guidelines
When stopping or starting RASLog messages, the commands are not configuration commands and
therefore are not persistent.
If the command logging raslog console stop minutes is invoked before the previous time
value expires, the latest CLI duration applies.
Examples
To stop RASLog messages for 1 minute:
device# logging raslog console stop 1
Logging message have been blocked on console for 1 minutes
Syntax
logging syslog-facility local log_level
Command Default
Syslog level is LOG_LOCAL7.
Parameters
log_level
Specifies the syslog facility level. Valid log levels include the following: LOG_LOCAL0,
LOG_LOCAL1, LOG_LOCAL2, LOG_LOCAL3, LOG_LOCAL4, LOG_LOCAL5, LOG_LOCAL6,
LOG_LOCAL7
Modes
Global configuration mode
Usage Guidelines
Use this command to configure the log level for all error log entries to forward to one or more specified
syslog servers. You can configure up to four syslog servers.
Examples
To configure the syslog facility level:
device# configure terminal
device(config)# logging syslog-facility local LOG_LOCAL5
logging syslog-server
Configures a switch to forward system messages to the specified syslog servers.
Syntax
logging syslog-server ip_address [ use-vrf vrf-name ]
no logging syslog-server ip_address [ use-vrf vrf-name ]
Parameters
ip_address
Specifies the IP address of the syslog server in IPv4 or IPv6 format.
use-vrf vrf-name
Specifies a VRF through which to communicate with the server. See the Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
Use this command to configure a switch to forward all error log entries to the specified servers. You can
configure up to four syslog servers; this includes all VRFs. You must execute the command for each
server.
The certutil import syslogca command is required for a secure syslog to be fully functional.
After specifying the ip_address and vrf-name, the secure sub-command can be used to specify
the secure default port (6514) or specify a secure non-default syslog server port. These sub-commands
are only available after specifying the ip_address and vrf-name parameters.
Use the no logging syslog-server command with the optional use-vrf keyword to remove
the specified IP address and VRF.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default
VRF ("default-vrf").
Examples
To configure a server IPv4 address to which system messages are sent on a user-specified VRF:
device# configure terminal
device(config)# logging syslog-server 192.168.163.233 use-vrf myvrf
device(config-syslog-server-192.168.163.233/myvrf)#
Examples
To configure a CLI source-interface in the logging syslog-server option:
device (config-syslog-server-1.1.1.1/mgmt-vrf)# source-interface
Possible completions:
ethernet Use Ethernet interface as source interface
loopback Use Loopback interface as source interface
management Use Managment (Active MM or Chassis ip) as source address
ve Use ve interface as source interface
device (config-syslog-server-1.1.1.1/mgmt-vrf)# source-interface management
Possible completions:
<NUMBER: 0-1> 1=Active-MM-IP 0=Chassis-IP
device (config-syslog-server-1.1.1.1/mgmt-vrf)#
logging syslog-server-host
Configures a switch to forward system messages to a specified syslog server using its host name.
Syntax
logging syslog-server-host host-name [ use-vrf vrf-name ]
no logging syslog-server-host host-name [ use-vrf vrf-name ]
Parameters
host-name
Specifies the hostname of the syslog server. This hostname must be resolved by the configured
DNS server.
use-vrf vrf-name
Specifies a VRF through which to communicate with the server. See the Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
Use this command to configure a switch to forward all error log entries to a specified server using the
server's host name. You can configure only one syslog server using hostname, this includes all VRFs.
The crypto import syslogca command is required for a secure syslog to be fully functional.
After specifying the host-name and vrf-name, the secure sub-command can be used to specify
the secure default port (6514) or specify a secure non-default syslog server port. These sub-commands
are only available after specifying the ip_address and vrf-name parameters.
Use the no logging syslog-server-host command with the optional use-vrf keyword to
remove the specified hostname and VRF.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default
VRF ("default-vrf").
Examples
To configure a server (using its hostname) to which system messages are sent on a user-specified VRF:
device# configure terminal
device(config)# logging syslog-server-host test.server.com use-vrf myvrf
device(config-syslog-server-192.168.163.233/myvrf)#
logging utility
Configures a switch to forward system messages to the configured syslog server(s) using RELP
(Reliable Event Logging Protocol).
Syntax
logging utility enable relp
no logging utility enable
Parameters
relp
Specifies that the logging entries must be forwarded to the configured logging servers using
RELP.
Modes
Global configuration mode
Usage Guidelines
Use this command to configure forwarding all system logs entries to the configured logging servers
using Reliable Event Logging Protocol (RELP).
You can configure up to four SYSLOG servers; this includes all VRFs. You must execute the command for
each server. The crypto import syslogca command is required for secure SYSLOG to be fully
functional. After specifying the ip_address and vrf-name parameters, the secure sub-command
can be used to specify the secure default port (6514) or to specify a secure non-default SYSLOG server
port.
These sub-commands are only available after specifying the ip_address and vrf-name parameters.
Use the no logging syslog-server command with the optional use-vrf keyword to remove
the specified IP address and VRF.
By default, all management services are enabled on the management VRF (mgmt-vrf) and the default
VRF (default-vrf).
Usage Guidelines
When enabling logging over RELP, keep the following in mind.
• When rsyslog over is RELP is configured as secured with TLS, the certificates that are used for
securing SYSLOG are used by rsyslog over RELP.
• After turning on logging over RELP, and when you use the login credentials of the SYSLOG server,
then the same credentials are used for logging over RELP.
• RELP mode does not support syslog-server host configuration. This configuration is automatically
blocked in the RELP mode. An error message is displayed.
Examples
To enable forwarding all system logs entries to the configured logging servers using Reliable Event
Logging Protocol (RELP).
SLX # config terminal
SLX (config)# logging utility enable relp
To disable forwarding all system logs entries to the configured logging servers using Reliable Event
Logging Protocol (RELP).
SLX # config terminal
SLX (config)# no logging utility enable
logical-interface
Configures a logical interface on a physical port or a port-channel (LAG) on an edge port, entering LIF
configuration mode, and optionally binds the interface to a bridge domain (BD).
Syntax
logical-interface { ethernet slot/port.service_instance | port-channel
num.service_instance }
no logical-interface { ethernet slot/port.service_instance | port-channel
num.service_instance }
Command Default
See the Usage Guidelines.
Parameters
ethernet slot/port
Specifies an Ethernet interface.
port-channel num
Specifies a port-channel interface.
service_instance
Specifies a service instance ID. Range is from 1 through 12288.
Modes
Interface subtype configuration mode
Usage Guidelines
The following are some common rules to consider in configuring logical interfaces:
• This command is applicable to an edge port only.
• This command by itself does not create the LIF as it requires more classifications as to what VLAN(s)
should be specified and whether the classifying VLAN is untagged or tagged.
• By default, when the LIF is created it is enabled. it is also "tagged" unless it is explicitly configured
with the "untagged" option.
• The user must specify a service instance ID. If the service instance ID has already been configured,
this command allows the user to specify the VLAN classification for this LIF. Allowed LIF service
instance ranges are from 1 through 12288 (12K LIFs are allowed per interface type). Currently, up to
100K LIFs are supported in the system, with 12K for physical port or LAG combined and 8K for PW
based.
• A LIF service instance ID has no correlation to the VLAN ID of the LIF.
• Each physical/LAG-based LIF must have an associated VLAN configured or else it will not be usable
when the user attempts to add it to a service. Such a configuration request to add the LIF to a
service will be rejected.
• Once the LIF is associated with a Layer 2 service, its VLAN value cannot be changed or deleted
unless it is first removed from the associated service. In case the LIF is not yet associated to a
service, the user is free to remove the VLAN configuration or change the VLAN assignment.
• The "untagged" configuration can only be allowed for one LIF under the same physical port or LAG.
If one LIF is already configured as untagged, all subsequent attempts on the same physical port or
LAG will be rejected.
• Once the "untagged" option is selected, it will only have one VLAN as the next classification option.
There is no dual-tag support for the untagged case.
• In order to configure an untagged LIF, the main interface must be set as "switchport mode trunk-no-
default-native". If it is only set to regular trunk mode, the native VLAN is already associated with a
regular Layer 2 VLAN LIF and no explicit untagged LIF can be configured on that interface.
• Once the LIF is associated with a service (Layer 2) such as bridge domain, its "untagged/tagged"
configuration cannot be changed. The service instance or its current VLAN classification must be
deleted by user first and then added back with the proper "untagged/tagged" option.
• VLANs 4091 through 4095 are reserved VLANs and these should not be used as the VLAN ID for
either the inner or outer VLAN of the LIF.
• The VLAN specified under the LIF ensures that such a VLAN is not already configured under the
switchport command for a regular Layer 2 allowed VLAN.
The no version of the command removes the LIF from the BD configuration. This can be applied any
time if the LIF is not yet associated with (bound to) a service. If it is already associated with a service,
the LIF is also implicitly removed from the BD configuration.
Examples
The following example sets "trunk-no-default-native" mode on an Ethernet interface, so that an
untagged LIF can be configured on service instance 120.
device(config)# interface ethernet 2/6
device(conf-if-eth-2/6)# switchport mode trunk-no-default-native
device(conf-if-eth-2/6)# logical-interface ethernet 2/6.120
device(conf-if-eth-lif-2/6.120)#
The following examples illustrate how up to command options can be configured in a single line.
device(conf-if-eth-2/6)# logical-interface ethernet 2/6.120 name myLIF120
device(conf-if-eth-lif-2/6.120)#
The following example sets "trunk-no-default-native" mode on a port-channel (LAG) interface, so that
an untagged LIF can be configured on service instance 3.
device(config)# int port-channel 10
device(config-port-channel-10)# switchport mode trunk-no-default-native
device(config-port-channel-10)# logical-interface port-channel 10.3
device(config-if-po-lif-10.3)# untagged vlan 3
The following example shows how to create a logical Ethernet interface service instance (1/5.10) and
bind it to bridge domain 4 by means of the bridge-domain command.
device(config)# bridge-domain 4
device(config-bridge-domain-4)# logical-interface ethernet 1/5.10
The following example shows how to bind a logical port-channel interface service instance (2.200) to
bridge domain 4 by means of the bridge-domain command.
The following example shows the error message that displays when an attempt is made to bind a logical
interface that was not previously created to a bridge domain.
The following example shows the error message that displays when an attempt is made to bind a logical
interface that is previously bound to another bridge domain.
device>enable
device# configure terminal
device(config)# bridge-domain 4
device(config-bridge-domain-4)# logical-interface ethernet 1/3.100
Error: LIF already Binded
loop-detection
Enables the loop detection (LD) feature at the interface level, VLAN, or bridge domain (BD) level, and
enters Protocol Loop Detection configuration mode.
Syntax
loop-detection
no loop-detection
Command Default
This feature is disabled.
Modes
Interface subtype configuration mode (Ethernet or port-channel)
Usage Guidelines
When configured at the interface level, this command applies to LD strict mode.
When configured at the VLAN level, this command is applied to all ports in the VLAN.
When configured at the bridge domain (BD) level this command is applied to all the attachment circuit
(AC) logical interfaces (LIFs) and VXLAN tunnels under the BD.
Use the no form of this command to disable loop detection at the interface, VLAN, or BD level.
Examples
The following example enables loop detection on an Ethernet interface and enters Protocol Loop
Detection configuration mode:
device# configure terminal
device(config)# interface ethernet 2/6
device(conf-if-eth-2/6)# loop-detection
device(config-loop-detect)#
The following example enables loop detection on a port-channel interface and enters Protocol Loop
Detection configuration mode.
device# configure terminal
device(config)# interface port-channel 20
device(config-port-channel-20)# loop-detection
device(config-loop-detect)#
The following example enables loop detection on a VLAN and enters Protocol Loop Detection
configuration mode.
device# configure terminal
device(config)# vlan 5
device(config-vlan-5)# loop-detection
device(config-loop-detect)#
loop-detection shutdown-disable
Disables the shutting down of an interface (Ethernet or port-channel), a VLAN VXLAN tunnel, or a
bridge domain (BD) VXLAN tunnel as a result of the loop detection (LD) protocol.
Syntax
loop-detection shutdown-disable
no loop-detection shutdown-disable
Command Default
This feature is disabled.
Modes
Interface subtype configuration mode (Ethernet or port-channel)
Usage Guidelines
Use the no form of this command. to revert to default behavior. (LD protocol shuts down the interface.)
Examples
The following example disables the shutdown of an Ethernet interface as a result of LD protocol.
device# configure terminal
device(config)# interface ethernet 2/6
device(conf-if-eth-2/6)# loop-detection shutdown-disable
loop-detection vlan
Associates a VLAN at the interface level to support the loop detection (LD) protocol.
Syntax
loop-detection vlan vlan-id
no loop-detection vlan
Command Default
This feature is disabled.
Parameters
vlan-id
Specifies a created VLAN. Range is from 1 through 4090.
Modes
Interface subtype configuration mode (Ethernet or port-channel)
Usage Guidelines
The VLAN must already be created.
The no form of this command deletes LD support for all previously configured VLANs, deleting all LD
configurations at the interface level.
Examples
To associate a VLAN to an Ethernet interface for LD support:
device# configure terminal
device(config)# interface ethernet 2/6
device(conf-if-eth-2/6)# loop-detection vlan 20
To disassociate all previously configured VLANs from an Ethernet interface for LD support and delete all
LD configurations at the Ethernet interface level:
device# configure terminal
device(config)# interface ethernet 2/6
device(conf-if-eth-2/6)# no loop-detection vlan 20
lsp
Accesses LSP subconfiguration mode to configure the LSP tunnel.
Syntax
lsp name
no lsp name
Parameters
name
Specifies the name of the LSP tunnel.
Modes
MPLS configuration mode
Usage Guidelines
Use the no form of this command to remove the LSP from the MPLS configuration.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures LSP to2 and accesses LSP subconfiguration mode.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# lsp to2
device(config-router-mpls-lsp-to2)#
lsp (Telemetry)
Indicates the MPLS LSP to be used for the mpls-traffic-lsp profile.
Syntax
lsp { lsp-name }
no lsp { lsp-name }
Parameters
lsp-name
Specifies the name of the target LSP for the profile.
Modes
Telemetry profile configuration mode
Usage Guidelines
The lsp-name variable must be unique among all regular LSPs and bypass LSPs.
The no form of the command deletes the LSP from the profile.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example selects the xm2lsp LSP as the LSP for the profile.
lsp-gen-interval
Sets the minimum number of seconds the device waits between sending updated Link State PDUs
(LSPs) to its Intermediate System-to-Intermediate System (IS-IS) neighbors.
Syntax
lsp-gen-interval interval
no lsp-gen-interval interval
Command Default
The default interval is 10 seconds.
Parameters
secs
Specifies the interval in seconds. Valid values range from 0 through 120 seconds. The default is
10 seconds.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example changes the LSP generation interval to 45 seconds.
device# configure terminal
device(config)# router isis
device(config-isis-router)# lsp-gen-interval 45
lsp-interval
Sets the rate of transmission, in milliseconds, of the Link State PDUs (LSPs).
Syntax
lsp-interval interval
no lsp-interval interval
Command Default
The default interval is 33 milliseconds.
Parameters
secs
Specifies the interval in milliseconds. Valid values range from 1 through 4294967295
milliseconds. The default is 33 milliseconds.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example changes the LSP interval to 45 milliseconds.
lsp-refresh-interval
Sets the maximum number of seconds a device waits between sending updated Link State PDUs (LSPs)
to its Intermediate System-to-Intermediate System (IS-IS) neighbors.
Syntax
lsp-refresh-interval interval
no lsp-refresh-interval interval
Command Default
The default interval is 900 seconds (15 minutes).
Parameters
secs
Specifies the interval in seconds. Valid values range from 1 through 65535 seconds. The default is
900 seconds.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example changes the LSP refresh interval to 20000 seconds.
lsr-id
Configures an IP address to be used as the LSR ID for the LDP identifier.
Syntax
lsr-id ip_addr
no lsr-id ip_addr
Command Default
The LSR-ID is the first available loopback interface address.
Parameters
ip_addr
Specifies the IP address to assign to the LSR identifier.
Modes
MPLS LDP configuration mode
Usage Guidelines
You can configure only an IPv4 address.
Use the no form of the command to reset the default behavior. When you enter the no form of the
command and LDP protocol is in the enabled state, the device uses the same LSR-ID until the LDP
protocol is disabled; the IP address selected as LSR-ID for the LDP protocol is still valid and is the
operationally UP IP address on an enabled loopback interface.
When you enter the no form of the command and LDP protocol is in the disabled state (this happens
when the loopback interface on which IP address is configured is in the disabled state), the device falls
back to default behavior which tries to enable LDP protocol when it finds a valid IP address on any one
of the enabled loopback interfaces.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures an IP address for the LSR identifier.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# lsr-id 10.22.22.22
ma-name
Creates a maintenance association (MA) within a specified domain. The command changes the
maintenance domain mode to the specified maintenance association mode.
Syntax
ma-name ma-name [ id ma-id ] [ vlan-id vlan-id ] [ bridge-domain bridge-
domain ] { priority priority }
no ma-name ma-name
Command Default
There are no MA configured.
Parameters
ma-name
Specifies the maintenance association name. The name attribute is case-sensitive.
ma-id
Specifies the short maid that is transmitted in the CCM PDU. This ID is unique. The range is 1 -
4090.
vlan-id
Specifies a unique VLAN identifier of the maintenance association in the range 1-4090. To create
a MA, a vlan id must be set.
bridge-domain
Specifies a unique L2VPN domain of the maintenance association. This option supports only
Virtual Private LAN Services (VPLS) in this release. VLL is not currently supported for CFM.
priority
Specifies the priority of the CCM messages sent by MEPs, in the range 0-7.
Modes
CFM protocol configuration mode
Usage Guidelines
The no form of the command removes the maintenance association.
Examples
This example demonstrates associating the MA "ma1" to VLAN 30.
device# configure terminal
device(config)# protocol cfm
device(config-cfm)# domain name md1 level 4
mac access-group
Applies rules specified in a MAC access control list (ACL) to traffic entering or exiting an interface.
Syntax
mac access-group ACLname { in | out }
no mac access-group ACLname { in | out }
Parameters
ACLname
Specifies the name of the standard or extended MAC access list.
in
Applies the ACL to incoming switched and routed traffic.
out
Applies the ACL to outgoing routed and (for XGS devices) also to switched traffic.
Modes
Interface-subtype configuration mode
Usage Guidelines
You can apply a maximum of five ACLs to a user interface, as follows:
• One ingress MAC ACL—if the interface is in switchport mode
• One egress MAC ACL—if the interface is in switchport mode
• One ingress IPv4 ACL
• One egress IPv4 ACL
• One ingress IPv6 ACL
On XGS devices, you can apply MAC ACLs to port-channels (LAGs) only ingress.
You can apply an ACL to multiple interfaces. And you can apply an ACL twice—ingress and egress—to a
given user interface.
Examples
The following example applies a MAC ACL to filter inbound packets only, on a specified Ethernet
interface.
device(config)# interface ethernet 0/1
device(conf-if-eth-0/1)# mac access-group macacl2 in
The following example removes a MAC ACL from a specified port-channel interface.
device(config)# interface port-channel 62
device(config-Port-channel-62)# no mac access-group macacl2 in
Syntax
mac access-list extended ACL-name
no mac access-list extended ACL-name
Parameters
ACL-name
Specifies an ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63
characters in length, and must begin with an alphanumeric character. No special characters are
allowed, except for the underscore (_) and hyphen (-).
Modes
Global configuration mode
Usage Guidelines
If the ACL is already created, this command puts the device in MAC extended ACL configuration mode.
An extended ACL contains rules that permit or deny traffic according to source and destination
addresses, as well as other parameters. Extended ACLs allow you to filter traffic based on the following:
• Source MAC address
• Destination MAC address
• EtherType
You can apply MAC extended ACLs to VLANs and to Layer 2 interfaces.
The no form of the command removes a MAC extended ACL from an interface.
Examples
The following example creates a MAC extended ACL named mac1.
device(config)# mac access-list extended mac1
Syntax
mac access-list standard ACLname
no mac access-list standard ACLname
Parameters
ACLname
Specifies an ACL name unique among all ACLs (Layer 2 and Layer 3). The name can be up to 63
characters in length, and must begin with an alphanumeric character. No special characters are
allowed, except for the underscore and hyphen.
Modes
Global configuration mode
Usage Guidelines
Use this command to create a standard MAC access list. If ACL is already created, this command puts
the device in the standard MAC access-list configuration mode.
To remove a MAC ACL from an interface, enter the no form of this command.
Examples
The following command creates a MAC standard ACL named mac1.
device(config)# mac access-list standard mac1
device(conf-macl-std)#
mac-address withdrawal
In a VPLS context on a bridge domain (BD), removes MAC addresses that have been dynamically
learned, thus providing faster convergence.
Syntax
mac-address withdrawal
no mac-address withdrawal
Command Default
MAC address withdrawal is disabled.
Modes
Bridge-domain configuration mode
Usage Guidelines
A MAC address withdrawal message is sent with a MAC list Type Length Value (TLV). 200 MAC
addresses are bulked and sent in one MAC TLV message.
Note
The MAC withdrawal support is only for explicit MAC addresses in a MAC withdrawal TLV. An
empty MAC list, as well as the sending of a MAC withdrawal TLV to a specific subset of peers,
is not supported.
The maximum number of MAC addresses supported is 5000 in a 5-second interval. The remaining MAC
addresses in the attachment circuit (AC) logical interface (LIF) are not sent. After the 5-second interval,
another LIF "down" event triggers a MAC withdrawal message for a new-5 second interval.
MAC withdrawal is supported for both VPLS and MCT-VPLS. MPLS signals the MAC withdraw TLV to all
the peers.
Examples
The following example enables MAC address withdrawal on a BD.
The following example illustrates output of the show bridge-domain command confirming that
withdrawal is enabled.
device# show bridge-domain
Bridge-domain 1
-------------------------------
Bridge-domain Type: MP , VC-ID: 0
Number of configured end-points: 0 , Number of Active end-points: 0
VE if-indx: 0, Local switching: TRUE, bpdu-drop-enable: TRUE
MAC Withdrawal: Enabled
PW-profile: default, mac-limit: 0
Total VPLS peers: 0 (0 Operational):
mac-address-table aging-time
Configures the aging time for dynamic MAC address entries in the MAC address table.
Syntax
mac-address-table aging-time seconds
no mac-address-table aging-time
Command Default
Default aging time is 1800 seconds.
Parameters
aging-time seconds
To disable MAC address aging, specify 0. To enable MAC address aging, specify a value from 60
through 86400.
Modes
Global configuration mode
Usage Guidelines
MAC address aging configuration per VLAN is not supported.
Examples
The following example configures the MAC aging period as 400 seconds.
mac-address-table mac-move
Configures the MAC movement detection parameters
Syntax
mac-address-table mac-move detect
mac-address-table mac-move action{ shutdown | raslog }
mac-address-table mac-move limit
mac-address-table mac-move auto-recovery enable{ time } [ minutes ]
Command Default
MAC movement detection is disabled by default
Parameters
action
Defines the action taken when the MAC movement exceeds the threshold. RASLOG is the
default.
limit
Sets the threshold for MAC movement action. Default is 20. Range is 3 through 500.
auto-recovery
Enables auto-recovery on the port. Default is disabled.
time
Sets the recovery time in minutes. Default is 5 minutes. Range is 3 through 30 minutes.
Modes
Global configuration mode
Usage Guidelines
The no form of the command restores the default value.
Examples
The following example enables MAC movement detection
device# config
device (config)# mac-address-table mac-move detect
The following example configures auto-recovery and sets the recovery time for 3 minutes.
device# config
device (config)# mac-address-table mac-move auto-recovery enable
mac-address-table static
Adds static addresses to the MAC address table.
Syntax
mac-address-table static mac-addr forward ethernet slot/port vlan vlan-id
no mac-address-table static mac-addr forward ethernet slot/port vlan
vlan-id
mac-address-table static mac-addr forward logical-interface ethernet
logical-interface
no mac-address-table static mac-addr forward logical-interface ethernet
logical-interface
mac-address-table static mac-addr forward port-channel port-channel-
number vlan
no mac-address-table static mac-addr forward port-channel port-channel-
number vlan
Command Default
Aging time is 1800 seconds.
Parameters
static mac-addr forward
Specifies the Media Access Control (MAC) address (unicast or multicast) to add to the address
table. Packets with this destination address received in the specified VLAN are forwarded to the
specified interface.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. The slot must be 0 for devices that do not support line cards.
port
Specifies a valid port number.
logical-interface logical-interface
Specifies a logical interface. Logical interfaces are the attachment circuit end-points bound to a
bridge domain.
port-channel number
Specifies the port-channel number. Valid values range from 1 through 63.
vlan vlan-id
Specifies an active VLAN. Values range from 1 through 4090.
Modes
Global configuration mode
Usage Guidelines
The vlan keyword is mandatory because the switch only supports independent VLAN learning (IVL).
To delete a static MAC address for forwarding to a physical interface, use the no mac-address-
table static mac-addr forward ethernet slot/port vlan vlan-id option.
To delete a static MAC address for forwarding to a logical interface, use the no mac-address-table
static mac-addr forward logical-interface ethernet logical-interface
vlan vlan-id option.
To delete a static MAC address for forwarding to a port-channel interface, use the no mac-address-
table static mac-addr forward port-channel port-channel-number vlan option.
Examples
The following example adds a static address to the MAC address table, with forwarding to a physical
interface.
device# configure terminal
device(config)# mac-address-table static 0011.2222.3333 forward ethernet 0/1 vlan 100
The following example adds a static address to the MAC address table, with forwarding to a logical
interface.
device# configure terminal
device(config)#mac-address-table static 0000.1111.2222 forward logical-interface ethernet
0/43.100
The following example deletes a static MAC address forwarding on a physical interface.
device# configure terminal
device(config)# no mac-address-table static aaaa.bbbb.cccc forward ethernet 0/1 vlan 10
maid-format
Sets the Maintenance Association Identifier (MAID) format for a particular maintenance association
(MA).
Syntax
maid format [ long | default ]
Command Default
The default maid format is short.
Parameters
long
Specifies maid format as long.
default
Specifies maid format as default.
Modes
Global configuration mode
Usage Guidelines
The no form of this command reverts back the maid format to short.
You cannot change the MAID format after a MEP is configured under an MA. You must first delete the
MEP and then change the MAID format.
Examples
The following example sets the MAID format to long.
device# configure terminal
device(config)# protocol cfm
device(config-cfm)# domain name md1 level 4
device(config-cfm-md-md1)# ma-name ma1 id 30 vlan-id 30 priority 7
device(config-cfm-md-md1)# maid-format long
Syntax
management-heartbeat manager
no management-heartbeat manager
Command Default
Heartbeat monitoring must be enabled explicitly using the enable command from within this mode.
When this command is executed, an entry for this mode is created in the running-config.
SLX(config-management-heartbeat-manage)# do show running-config management-heartbeat
manager
management-heartbeat manager
threshold-timer 5
action maintenance-mode-enable
!
SLX(config-management-heartbeat-manage)#
The no form of this command removes the management-heartbeat manager configuration from
the running-config.
SLX(config-management-heartbeat-manage)# do show running-config management-heartbeat
manager
management-heartbeat manager
threshold-timer 5
action maintenance-mode-enable
!
SLX(config-management-heartbeat-manage)# exit
SLX(config)#
SLX(config)# no management-heartbeat manager
SLX(config)#
SLX(config)# do show running-config management-heartbeat manager
% No entries found.
SLX(config)#
Examples
The following example changes the context to management-heartbeat-manage mode and lists all the
commands within this context.
SLX# configure terminal
Entering configuration mode terminal
SLX(config)# management-heartbeat manager
Possible completions:
management-security
The management-security sub mode, under the Global Configuration mode, enables configuring the
lowest TLS version supported by the SLX software. SLX uses OpenSSL to provide transport layer
security and the current version of OpenSSL supports TLS v 1.1 to TLS v 1.2. Since the SLX box can be
considered as both a client as well as a server, you can apply different supported TLS versions for each
of these types. The ssl-profile command within this mode allows you to configure these values.
Syntax
management-security
Modes
Configuration Terminal mode
Examples
The following example shows how to navigate into the management-security mode and view the
available commands under this mode.
SLX # configure terminal
Entering configuration mode terminal
manual-switch vlan
Blocks a specified link manually for an Ethernet Ring Protection (ERP) instance.
Syntax
manual-switch vlan vlan_id [ ethernet slot/port | port-channel number ]
no manual-switch vlan vlan_id [ ethernet slot/port | port-channel
number ]
Command Default
This feature is not configured by default.
Parameters
vlan_id
Specifies a VLAN.
ethernet slot/port
Specifies an Ethernet interface.
port-channel number
Specifies a port-channel.
Modes
ERP configuration mode
Usage Guidelines
Manual Switch (MS) is an operator-initiated process that manually blocks a specified interface in a ring.
It can be configured only in an error-free topology. There can be only one MS configuration in a ring.
Examples
The following example configures MS for a specified interface.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# manual-switch vlan 5 ethernet 0/1
Syntax
map bridge-domain bridge_domain_id vni vni
no map bridge-domain bridge_domain_id vni vni
Parameters
bridge_domain_id
Specifies a bridge domain.
vni vni
Specifies a VNI. Enter an integer from 1 through 16777215.
Modes
Overlay gateway configuration mode
Usage Guidelines
Use the no form of this command to remove the mapping.
Examples
The following example maps a bridge domain to a VNI.
device# configure terminal
device(config)# overlay-gateway gateway1
device(config-overlay-gw-gateway1)# map bridge-domain 1 vni 999
map dscp
Maps an ingress DSCP value to an outbound CoS, DSCP, or traffic-class value for a QoS DSCP-to-CoS,
DSCP-mutation, or DSCP-to-traffic class map.
Syntax
map dscp dscp-value to { cos cos-value } | { dscp dscp-out } | { traffic-
class tc-value }
no map dscp dscp-value
Command Default
The default values for DSCP to CoS, DSCP mutation, or DSCP to traffic class mapping.
Parameters
dscp-value
Specifies the ingress DSCP value or range. Enter an integer from 0 to 63.
cos cos-value
Specifies the outbound CoS value. Enter an integer from 0 to 7.
dscp dscp-out
Specifies the outbound DSCP value or range. Enter an integer from 0 to 63.
traffic-class tc-value
Specifies the outbound Traffic Class value. Enter an integer from 0 to 7.
Modes
DSCP CoS configuration mode
Usage Guidelines
Use the no form of the command to reset the default mapping values.
Examples
In DSCP COS configuration mode, the following example maps an ingress DSCP value to an egress CoS
value.
In DSCP mutation configuration mode, the following example maps the ingress DSCP values to an
egress DSCP value.
In DSCP traffic configuration mode, the following example maps the ingress DSCP values to a traffic
class.
map vlan
In a VXLAN overlay gateway configuration that uses Layer 2 extension, associates VLANs with VXLAN
Network Identifiers (VNIs).
Syntax
map vlan [ vlan_id ] vni [ vni ] [ auto ]
no map vlan vlan_id
no map vlan vni
Parameters
vlan_id
A single VLAN ID or range of VLAN IDs. The range is from 1 through 8191. See the Usage
Guidelines.
vni
Specifies the VNI (VXLAN Network Identifier) token.
vni
A single VXLAN VNI or range of VXLAN VNIs. Range is from 1 through 16777215. See the Usage
Guidelines.
auto
Enables automatic VLAN-to-VNI mapping for every VLAN associated with the tunnel.
Modes
VXLAN overlay gateway configuration mode
Usage Guidelines
Note the following conditions:
• Before using this command, you must first set the VXLAN overlay gateway to layer2-
extension, by means of the type command.
• Before using this command, you must first configure the appropriate VLANs to be used by the
gateway.
• Before mapping VLANs to VNIs manually, you cannot have automatic mapping configured (by
means of the map vlan vni auto command).
• You cannot map one VLAN to multiple VNIs. Similarly, you cannot map a single VNI to multiple
VLANs. For example, VLAN-to-VNI mapping should be one to one.
• A single VLAN ID and a range of VLAN IDs can both be specified in a single command as follows:
x,y-z. The same applies to VNIs.
• When using ranges, you must ensure that the number of values in a VLAN ID range corresponds to
the number of values in a VNI range.
• The no forms of this command are allowed only if no VLANs are referenced by means of the
extend vlan command (under a submode of the site command). For example, VLANs
extended to a site should have a VNI mapping.
• The no map vlan vni auto command disables the automatic assignment of VNIs. It is not
allowed if manual VLAN-to-VNI mappings have been configured. For example, "auto" VLAN-to-VNI
mapping and "explicit" VLAN-to-VNI mapping are mutually exclusive.
• The no map vlan vlan_id command removes the VNI mappings for one or more VLANs.
• You cannot delete a VLAN (by means of the no interface vlan command) that is referenced
by means of the map vlan vni command.
• This command does not trigger VLAN provisioning, unlike the behavior of the attach vlan
command.
• Either automatic or manual VLAN mapping is supported. Hybrid mode is not supported.
Examples
To configure a manual mapping of VLANs to VNIs in "gateway1":
switch(config)# overlay-gateway gateway1
switch(config-overlay-gw-gateway1)# map vlan 10,20-22 vni 5000-5002,6000
Syntax
map vni auto
no map vni auto
Command Default
This feature is not enabled.
Modes
VXLAN overlay gateway configuration mode
Usage Guidelines
Use the no form of this command to undo the automatic mapping.
Examples
The following example configures the automatic mapping of VLANs/BDs) to VNIs.
device# configure terminal
device(config)# overlay-gateway mygateway
device(config-overlay-gateway-mygateway)# map vni auto
master-vlan (STP)
Selects a master VLAN for a topology group.
Syntax
master-vlan vlan_id
Command Default
The master VLAN is not configured.
Parameters
vlan_id
The master VLAN ID.
Modes
Topology group configuration mode.
Usage Guidelines
To configure a master VLAN, the VLAN must already be configured. The master VLAN contains the STP
settings for all the VLANs in the STP per VLAN group. An STP group can have only one master VLAN. If
you add a new master VLAN to an STP group that already has a master VLAN, the new master VLAN
replaces the older master VLAN.
If you remove the master VLAN (by entering the no master-vlan command), the software selects
the new master VLAN from member VLANs. A new candidate master VLAN will be in configured as a
member VLAN so that the first added member VLAN will be a new candidate master VLAN. Once you
save and reload, a member VLAN with the youngest VLAN ID will be the new candidate master.
Examples
The following example adds the member VLANs to the STP topology group.
Syntax
match as-path name
match community name exact-match ]
match extcommunity number
match interface { ethernet slot / port | loopback num| ve-interface
vlan_id }
match ip address { acl name [ prefix-list string ] | prefix-list string
[ acl name }
match ip next-hop prefix-list string
match ip route-source prefix-list string
match ipv6 next-hop prefix-list string
match ipv6 route-source prefix-list string
match metric num
match protocol bgp { external | internal | static-network }
match protocol static
match route-type { internal | type-1 | type-2 }
match tag num
match vrf name
no match as-path
no match community
no match extcommunity
no match interface
no match ip address
no match ip next-hop
no match ip route-source
no match ipv6 address
no match ipv6 next-hop
no match ipv6 route-source
no match metric
no match protocol
no match route-type
no match tag
Command Default
This option is disabled.
Parameters
as-path
Matches an AS-path access list name in a route-map instance.
name
Name of an AS-path access list. Range is from 1 through 32 ASCII characters.
community
Matches a BGP community access list name in a route-map instance.
name
Name of a BGP community access list. Values range from 1 through 32 ASCII characters.
exact-match
Matches a route only if the route community attributes field contains the same community
numbers specified in the match statement.
extcommunity number
Matches a BGP extended community list in a route-map instance and specifies an extended
community list number. Valid values range from 1 through 99.
interface
Matches interface conditions in a route-map instance.
ethernet
Specifies an ethernet interface.
slot
Specifies a valid slot number. If the device does not have linecards, specify 0.
port
Specifies a valid port number.
loopback num
Specifies a loopback interface.
ve-interface vlan_id
Specifies a virtual Ethernet VLAN interface.
ip address
Matches an IP address in a route-map instance.
acl name
Name of the access list. Range is from 1 through 32 ASCII characters.
prefix-list string
Specifies an IP prefix list. Range is from 1 through 32 ASCII characters.
ip next-hop
Matches IP next-hop match conditions in a route-map instance.
ip route-source
Matches an IP route source in a route-map instance.
ipv6 address
Matches an IPv6 address in a route-map instance.
ipv6 next-hop
Matches IPv6 next-hop match conditions in a route-map instance.
ipv6 route-source
Matches an IPv6 route source in a route-map instance.
metric num
Matches a route metric in a route-map instance. Values range from 0 through 4294967295.
protocol bgp external
Matches on BGP routes.
protocol bgp internal
Matches on iBGP routes.
protocol bgp static-network
Matches on BGP4 static network routes. This is applicable only for BGP outbound policy.
protocol static
Matches on static routes.
route-type
Matches a route type in a route-map instance.
internal
Internal route type
type-1
OSPF external route type 1
type-2
OSPF external route type 2
tag tag-value
Specifies a route tag and route tag value.
vrf name
Specifies a non-default VRF. Valid values range from 0 through 4294967295.
Modes
Route-map configuration mode
Usage Guidelines
For non-BGP route-maps, refer to the following topics:
• match ip address acl
• match ipv6 address acl
Examples
The following example matches AS-path ACL 1 in route-map instance “myroutes”.
device#configure terminal
device(config)# route-map myroutes permit 10
device(config-route-map myroutes/permit/10)# match as-path 1
match access-group
Matches an ACL to a class map.
Syntax
match access-group name
Parameters
name
The ACL name.
Modes
Class map configuration mode.
Usage Guidelines
The command is used after the class-map command is entered.
Examples
Use this command to match an ACL to a class map.
Syntax
match additional-paths advertise-set [ all ] [ best num ] [ best-range
start-num end-num ] [ group-best ]
no match additional-paths [ all ] advertise-set [ best num ] [ best-range
start-num end-num ] [ group-best ]
Command Default
By default, a route map is not configured to filter advertised paths.
Parameters
all
Causes all (up to a maximum of 16) routes to be advertised.
best num
Specifies the number of best routes to advertise.
best-range
Causes advertisement of routes within a number range.
start-num
Specifies the start number of the range of routes to advertise. The number ranges from 1 through
16.
end-num
Specifies the end number of the range of routes to advertise. The number ranges from 1 through
16.
group-best
Advertises the group-best path.
Modes
Route-map configuration mode
Usage Guidelines
A match occurs when an additional path that is a candidate for advertisement has the same path
marking (tag) as the marking configured by using the match additional-paths advertise-
set command.
Examples
The following example shows how to configure route map (rm_example) to advertise the group-best
route.
device# configure terminal
device(config)# route-map rm_example permit 123
device(config-routemap-rm_example/permit/123)# match additional-paths advertise-set group-
best
match bridge-domain
Matches a bridge domain to a class map.
Syntax
match bridge-domain BD-number
Parameters
BD-number
Specifies a valid bridge-domain number.
Modes
Class map configuration mode.
Usage Guidelines
The command is used after the class-map command is entered.
Examples
The following example matches a bridge domain to a class map.
match community
Matches a community access list name in a route-map instance.
Syntax
match community name
no match community
Parameters
name
Name of a community access list. Values range from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Enter no match community name to disable this feature.
You can configure up to five match community directives within a single stanza.
Examples
Typical command example:
device# config terminal
device(config)# route-map myroutes permit 10
device(config-route-map myroutes/permit/10)# match community ABCPath
match destination-port
Configures matching based on UDP or TCP destination port for a route-map sequence number.
Syntax
match destination-port { eq | gt | lt } port-num-1
match destination-port neq port-num-1 [ ... port-num-32 ]
match destination-port range port-num-1 port-num-2
no match destination-port { eq | gt | lt } port-num-1
no match destination-port neq port-num-1 [ ... port-num-32 ]
no match destination-port range port-num-1 port-num-2
Command Default
Matching based on destination port is not configured.
Parameters
eq port-num-1
Specifies that matching occurs when the packet destination port is equal to the specified port
number, which must be a valid UDP or TCP port number in the range from 0 through 65535.
gt port-num-1
Specifies that matching occurs when the packet destination port is greater than the specified
port number, which must be a valid UDP or TCP port number in the range from 0 through 65535.
lt port-num-1
Specifies that matching occurs when the packet destination port is less than the specified port
number, which must be a valid UDP or TCP port number in the range from 0 through 65535.
neq port-num-1 [ ... port-num-32 ]
Specifies that matching occurs when the packet destination port is not equal to all of the
specified ports. You can specify a maximum of 32 ports. Specified ports must be valid UDP or
TCP port numbers in the range from 0 through 65535.
range port-num-1 port-num-2
Specifies that matching occurs when the packet destination port is within the specified range of
port numbers, which must be valid UDP or TCP port numbers in the range from 0 through
65535.
Modes
Route-map configuration mode
Usage Guidelines
When match protocol and match destination-port are specified in the same stanza, the
protocol specified by the match protocol command must be either TCP or UDP.
Up to 128 match destination-port statements are allowed per route-map sequence number for
the following options:
• eq
• range
When multiple match destination-port statements of the same type exist, matching occurs
when traffic matches any one of the statements.
Only one match destination-port statement is allowed per route-map sequence number for the
following options:
• lt
• gt
• neq
Note
Configuring the range option may create a lot of TCAM entries (due to rule expansion).
Examples
The following example shows how to configure matching based on destination port number 45 for
sequence number 4 in a route-map named rm.
The following example shows how to configure matching based on destination port for sequence
number 4 in a route-map named rm; a match occurs when traffic destination port is not equal to 34 and
56 and 67.
device# configure terminal
device(config)# route-map rm permit 4
device(config-route-map-rm/permit/4)# match destination-port neq 34 56 67
match dscp
Configures matching based on a Differentiated Services Code Point (DSCP) value or range of values for
a route-map sequence number.
Syntax
match dscp { eq | gt | lt } value-1
match dscp neq value-1 [ … value-32 ]
match dscp range value-1 value-2
no match dscp { eq | gt | lt } value-1
no match dscp neq value-1 [ … value-32 ]
no match dscp range value-1 value-2
Command Default
Matching based on DSCP value is not configured.
Parameters
eq value-1
Specifies that matching occurs when the packet DSCP value is equal to the specified DSCP value.
gt value-1
Specifies that matching occurs when the packet DSCP value is greater than the specified DSCP
value.
lt value-1
Specifies that matching occurs when the packet DSCP value is less than the specified DSCP
value.
neq value-1 [ … value-32 ]
Specifies that matching occurs when the packet DSCP value is not equal to all of the specified
DSCP values. You can specify a maximum of 32 values.
range value-1 value-2
Specifies that matching occurs when the packet DSCP value is within the specified range of
DSCP values.
Modes
Route-map configuration mode
Usage Guidelines
Up to 128 match dscp statements are allowed per route-map sequence number for the following
options:
• eq
• range
When multiple match dscp statements of the same type exist, matching occurs when traffic matches
any one of the statements.
Only one match dscp statement is allowed per route-map sequence number for the following
options:
• lt
• gt
• neq
Note
Configuring the range option may create a lot of TCAM entries (due to rule expansion).
Examples
The following example shows how to configure matching based on DSCP value (23) for sequence
number 4 under a route map named rm.
match extcommunity
Matches an extended community list in a route-map instance.
Syntax
match extcommunity number
no match extcommunity
Command Default
BGP extended community access list names are not matched.
Parameters
name
Modes
Route-map configuration mode.
Usage Guidelines
Enter no match extcommunity to remove the community match statement from the configuration
file.
You can configure up to five match extcommunity directives within a single stanza.
Examples
To configure a route map that matches on extended community ACL 1.
device# configure terminal
device(config)# ip extcommunity-list 1 permit 123:2
device(config)# route-map extComRmap permit 10
device(config-route-map-extComRmap/permit/10)# match extcommunity 1
match fragment-type
Configures matching based on fragmentation type for a route-map sequence number.
Syntax
match fragment-type { all | any } [ dont-fragment ] [first-fragment |
not-first-fragment ] [fragment | not-fragment] [ last-fragment | not-
last-fragment ]
no match fragment-type { all | any } [ dont-fragment ] [first-fragment |
not-first-fragment ] [fragment | not-fragment] [ last-fragment | not-
last-fragment ]
Command Default
Matching based on fragmentation type is not configured.
Parameters
all
Specfies that matching occurs when traffic matches all of the subsequent specified options.
any
Specfies that matching occurs when traffic matches any of the subsequent specified options.
dont-fragment
Specifies matching based on fragmentation type being equal to DF
first-fragment
Specifies matching based fragmentation type being equal to FF.
not-first-fragment
Specifies matching based on fragmentation type not being equal to FF.
fragment
Specifies that matching occurs when the packet is an IP fragment.
not-fragment
Specifies that matching occurs when the packet is not an IP fragment.
last-fragment
Specifies matching based on fragmentation type being equal to LF.
not-last-fragment
Specifies matching based on fragmentation type not being equal to FF.
Modes
Route-map configuration mode
Usage Guidelines
When issuing the match fragment-type command, you must specify either all or any and at
least one other option.
You can configure multiple options by using the match fragment-type command.
Up to 128 match fragment-type configurations are allowed per route-map sequence number.
When multiple match fragment-type configurations exist, matching occurs when traffic matches
any one of the configured fragment type configurations.
Examples
The following example shows how to configure matching based on fragmentation type being equal to
first-fragment or not equal to last-fragment for sequence number 4 in a route-map named
rm.
The following example shows how to configure matching based on fragmentation type equal to last-
fragment for sequence number 4 in a route-map named rm.
match ip
Configures matching based on an IPv4 source or destination prefix for a route-map sequence number.
Syntax
match ip { source-address | destination-address } ip-address/ip-mask
no match ip { source-address | destination-address } ip-address/ip-mask
Command Default
IPv4 source or destination prefix matching is not configured.
Parameters
source-address
Specifies matching based on source IP address.
destination-address
Specifies matching based on destination IP address.
ip-address/ip-mask
Specifies an IPv4 address and mask.
Modes
Route-map configuration mode
Usage Guidelines
Only one match ip configuration is allowed per route-map sequence number.
Examples
The following example shows how to configure matching based on a source address (10.2.0.1/16) for
sequence number 4 in a route-map named rm.
Syntax
match ip address acl acl-name
no match ip address acl acl-name
Parameters
acl-name
Specifies an IPv4 ACL name unique among all ACLs (Layer 2 and Layer 3). The name can from 1
through 63 characters in length and must begin with an alphanumeric character. No special
characters are allowed, except for the underscore and hyphen.
Modes
Route-map configuration mode
Usage Guidelines
The absence of a match statement is treated as "match any"; all traffic is forwarded according to the
set statement.
Examples
The following example creates an IPv4 ACL that permits traffic from a specific source IP and then
includes that ACL in a route-map stanza.
device# configure terminal
device(config)# ip access-list standard acl_01
device(conf-ipacl-std)# permit host 192.1.1.1 count
device(conf-ipacl-std)# exit
device(config)# route-map example1 permit 1
device(config-route-map-example1/permit/1)# match ip address acl acl_01
match ip icmp-code
Configures matching based on Internet Control Message Protocol (ICMP) code for a route-map
sequence number.
Syntax
match ip icmp-code { eq | gt | lt } icmp-code-1
match ip icmp-code neq icmp-code-1 [ … icmp-code-32 ]
match ip icmp-code range icmp-code-1 icmp-code-2
no match ip icmp-code { eq | gt | lt } icmp-code-1
no match ip icmp-code neq icmp-code-1 [ … icmp-code-32 ]
no match ip icmp-code range icmp-code-1 icmp-code-2
Command Default
Matching based on ICMP code is not configured.
Parameters
eq icmp-code-1
Specifies that matching occurs when the packet ICMP code is equal to the specified ICMP code
or well-known ICMP code value.
gt icmp-code-1
Specifies that matching occurs when the packet ICMP code is greater than the specified ICMP
code or well-known ICMP code value.
lt icmp-code-1
Specifies that matching occurs when the packet ICMP code is less than the specified ICMP code
or well-known ICMP code value.
neq icmp-code-1 [ … icmp-code-32 ]
Specifies that matching occurs when the packet ICMP code is not equal to all of the specified
ICMP codes or well-known ICMP code values. You can specify a maximum of 32 codes or code
values.
range icmp-code-1 icmp-code-2
Specifies that matching occurs when the packet ICMP code is within the range of specified ICMP
codes or well-known ICMP code values.
Modes
Route-map configuration mode
Usage Guidelines
When match protocol and match ip icmp-code are specified in the same stanza, the protocol
specified by the match protocol command must be ICMP; specifying any other protocol value using
the match protocol command results in the rule being evaluated as false and it becomes inactive.
Up to 128 match ip icmp-code statements are allowed per route-map sequence number for the
following options:
• eq
• range
When multiple match ip icmp-code statements of the same type exist, matching occurs when
traffic matches any one of the statements.
Only one match ip icmp-code statement is allowed per route-map sequence number for the
following options:
• lt
• gt
• neq
Note
Configuring the range option may create a lot of TCAM entries (due to rule expansion).
Examples
The following example shows how to configure matching based on ICMP codes in the range from 3
through 5.
match ip icmp-type
Configures matching based on Internet Control Message Protocol (ICMP) type for a route-map
sequence number.
Syntax
match ip icmp-type { eq | gt | lt } icmp-type-1
match ip icmp-type neq icmp-type-1 [ … icmp-type-32 ]
match ip icmp-type range icmp-type-1 icmp-type-2
no match ip icmp-type { eq | gt | lt } icmp-type-1
no match ip icmp-type neq icmp-type-1 [ … icmp-type-32 ]
no match ip icmp-type range icmp-type-1 icmp-type-2
Command Default
Matching based on ICMP type is not configured.
Parameters
eq icmp-type-1
Specifies that matching occurs when the packet ICMP type is equal to the specified ICMP type or
well-known ICMP type value.
gt icmp-type-1
Specifies that matching occurs when the packet ICMP type is greater than the specified ICMP
type or well-known ICMP type value.
lt icmp-type-1
Specifies that matching occurs when the packet ICMP code is less than the specified ICMP type
or well-known ICMP type value.
neq icmp-type-1 [ … icmp-type-32 ]
Specifies that matching occurs when the packet ICMP type (or ICMP type value) is not equal to
all of the specified ICMP types. You can specify a maximum of 32 ICMP types. S
range icmp-type-1 icmp-type-2
Specifies that matching occurs when the packet ICMP type is within the range of specified ICMP
types or well-known ICMP type values.
Modes
Route-map configuration mode
Usage Guidelines
When match protocol and match ip icmp-type are specified in the same stanza, the protocol
specified by the match protocol command must be ICMP; specifying any other protocol value using
the match protocol command results in the rule being evaluated as false and it becomes inactive.
Up to 128 match ip icmp-type statements are allowed per route-map sequence number for the
following options:
• eq
• range
When multiple match ip icmp-type statements of the same type exist, matching occurs when
traffic matches any one of the statements.
Only one match ip icmp-type statement is allowed per route-map sequence number for the
following options:
• lt
• gt
• neq
Note
Configuring the range option may create a lot of TCAM entries (due to rule expansion).
Examples
The following example shows how to configure matching when the packet ICMP type is not equal to 5.
Syntax
match ipv6 address acl acl-name
no match ipv6 address acl acl-name
Parameters
acl-name
Specifies an IPv6 ACL name unique among all ACLs (Layer 2 and Layer 3). The name can from 1
through 63 characters in length and and must begin with an alphanumeric character. No special
characters are allowed, except for the underscore and hyphen.
Modes
Route-map configuration mode
Usage Guidelines
The absence of a match statement is treated as "match any"; all traffic is forwarded according to the
set statement.
Examples
The following example creates an IPv6 ACL that permits traffic from specific sources and denies traffic
from another source. The example then includes that ACL in a route-map stanza.
device# configure terminal
device(config)# ipv6 access-list extended acl6_01
device(conf-ip6acl-ext)# seq 10 permit ipv6 any host 2000::1 count
device(conf-ip6acl-ext)# seq 20 permit ipv6 any host 2000::2 count
device(conf-ip6acl-ext)# seq 30 deny ipv6 any host 2000::3 count
device(conf-ip6acl-ext)# exit
device(config)# route-map example2 permit 1
device(config-route-map-example2/permit/1)# match ipv6 address acl acl6_01
match large-community
Filters routes by BGP Large Community attributes, using a partial or exact match with Large
Community ACLs.
Syntax
match large-community name [exact-match]
no match large-community name
Command Default
No matching is configured.
Parameters
name
Name of a large community access list. The format is from 1 through 32 ASCII characters.
exact-match
Filters routes by using an exact match.
Modes
Route-map configuration mode
Usage Guidelines
Use the no form of this command to disable matching based on a large-community list.
A maximum of five Large Community ACLs can be configured to do a partial or exact match.
Examples
The following example shows how to configure matching based on a large-community access list
named ABCPath for a route map named myroutes.
device# config terminal
device(config)# route-map myroutes permit 10
device(config-route-map myroutes/permit/10)# match large-community ABCPath
The following example shows how to configure matching based on a large-community access list
named lcstdacl1 with an exact match for a route map named myroutes.
device# config terminal
device(config)# route-map myroutes permit 10
device(config-route-map myroutes/permit/10)# match large-community lcstdacl1 exact-match
match packet-length
Configures matching based on packet length for a route-map sequence number.
Syntax
match packet-length { eq | gt | lt } value-1
match packet-length neq value-1 [ ... value-32 ]
match packet-length range value-1 value-2
no match packet-length { eq | gt | lt } value-1
no match packet-length neq value-1 [ ... value-32 ]
no match packet-length range value-1 value-2
Command Default
Matching based on packet length is not configured.
Parameters
eq value-1
Specifies that matching occurs when the packet length (including the IP header but excluding
the Layer 2 header) is equal to the specified value.
gt value-1
Specifies that matching occurs when the packet length (including the IP header but excluding
the Layer 2 header) is greater than the specified value.
lt value-1
Specifies that matching occurs when the packet length (including the IP header but excluding
the Layer 2 header) is less than the specified value.
neq value-1 [ ... value-32 ]
Specifies that matching occurs when the traffic packet length (including the IP header but
excluding the Layer 2 header)is not equal to all of the specified values. You can specify a
maximum of 32 values.
range value-1 value-2
Specifies that matching occurs when the packet length (including the IP header but excluding
the Layer 2 header) is within the range of specified values.
Modes
Route-map configuration mode
Usage Guidelines
Up to 128 match packet-length statements are allowed per route-map sequence number for the
following options:
• eq
• range
When multiple match packet-length statements of the same type exist, matching occurs when
traffic matches any one of the statements.
Only one match packet-length statement is allowed per route-map sequence number for the
following options:
• lt
• gt
• neq
Note
Configuring the range option may create a lot of TCAM entries (due to rule expansion).
Examples
The following example shows how to configure matching based on a packet length of 1500 for
sequence number 4 in a route map named rm.
match port
Configures matching based on TCP or UDP source or destination port for a route-map sequence
number.
Syntax
match port { eq | gt | lt } port-num-1
match port neqport-num-1 [ … port-num-32 ]
match port range port-num-1 port-num-2
no match port { eq | gt | lt } port-num-1
no match port neqport-num-1 [ … port-num-32 ]
no match port range port-num-1 port-num-2
Command Default
Source port or destination port matching is not configured.
Parameters
eq port-num-1
Specifies that matching occurs when the packet source port or destination port is equal to the
specified port number, which must be a valid UDP or TCP port number in the range from 0
through 65535.
gt port-num-1
Specifies that matching occurs when the packet source port or destination port is greater than
the specified port number, which must be a valid UDP or TCP port number in the range from 0
through 65535.
lt port-num-1
Specifies that matching occurs when the packet source port or destination port is less than the
specified port number, which must be a valid UDP or TCP port number in the range from 0
through 65535.
neqport-num-1 [ … port-num-32 ]
Specifies that matching occurs when neither the packet source port nor packet destination port
is equal to all of the specified ports. Specified ports must be a valid UDP or TCP port number in
the range from 0 through 65535.
range port-num-1 port-num-2
Specifies that matching occurs when the packet source port or destination port is within the
specified range of port numbers, which must be valid UDP or TCP port numbers in the range
from 0 through 65535.
Modes
Route-map configuration mode
Usage Guidelines
When match protocol and match port are specified in the same stanza, the protocol specified
by the match protocol command must be either TCP or UDP.
Up to 128 match port statements are allowed per route-map sequence number for the following
options:
• eq
• range
Only one match port statement is allowed per route-map sequence number for the following
options:
• lt
• gt
• neq
When multiple match port configurations exist, matching occurs when traffic matches any one of the
configured ports.
Note
Configuring the range option may create a lot of TCAM entries (due to rule expansion).
Examples
The following example shows how to configure matching based on port numbered 45 for sequence
number 4 in a route-map named rm; a match occurs when either the packet source or destination port
is in the range from 3 through 6000.
The following example shows how to configure matching based on port for sequence number 4 in a
route-map named rm; a match occurs when both the packet source port and packet destination port
are not equal to 34 and 56 and 67.
device# configure terminal
device(config)# route-map rm permit 4
device(config-route-map-rm/permit/4)# match port neq 34 56 67
match protocol
Configures protocol-based matching for a route-map sequence number.
Syntax
match protocol { eq | gt | lt } protocol-1
match protocol neq protocol-1 [ … protocol-32 ]
match protocol range protocol-1 protocol-2
no match protocol { eq | gt | lt } protocol-1
no match protocol neq protocol-1 [ … protocol-32 ]
no match protocol range protocol-1 protocol-2
Command Default
Protocol-based matching is not configured.
Parameters
eq protocol-1
Specifies that matching occurs when the traffic IP protocol is equal to the specified protocol. The
protocol can be specified in either name or number format.
gt protocol-1
Specifies that matching occurs when the traffic IP protocol is greater than the specified protocol.
The protocol can be specified in either name or number format.
lt protocol-1
Specifies that matching occurs when the traffic IP protocol is less than the specified protocol.
The protocol can be specified in either name or number format.
neq protocol-1 [ … protocol-32 ]
Specifies that matching occurs when the traffic IP protocol is not equal to all of the specified
protocols. You can specify a maximum of 32 protocols. Protocols can be specified in either name
or number format.
range protocol-1 protocol-2
Specifies that matching occurs when the traffic IP protocol is within the specified range of
protocols. Protocols rotocol can be specified in either name or number format.
Modes
Route-map configuration mode
Usage Guidelines
When match protocol and match ip icmp-code are specified in the same stanza, the protocol
specified by the match protocol command must be ICMP; specifying any other protocol value using
the match protocol command results in the rule being evaluated as false and it becomes inactive.
When match protocol and match ip icmp-type are specified in the same stanza, the protocol
specified by the match protocol command must be ICMP; specifying any other protocol value using
the match protocol command results in the rule being evaluated as false and it becomes inactive.
When match protocol and match port, match source-port, or match destination-
port are specified in the same stanza, the protocol specified by the match protocol command
must be either TCP or UDP.
Up to 128 match protocol statements are allowed per route-map sequence number for the
following options:
• eq
• range
When multiple match protocol statements of the same type exist, matching occurs when traffic
matches any one of the statements.
Only one match protocol statement is allowed per route-map sequence number for the following
options:
• lt
• gt
• neq
Note
Configuring the range option may create a lot of TCAM entries (due to rule expansion).
Examples
The following example shows how to configure protocol-based matching for sequence number 4 in a
route-map named rm; a match occurs when traffic is not equal to 34 and 56 and 67.
The following example shows how to configure matching based on a range of protocols (3 through 10)
for sequence number 4 in a route-map named rm.
match rpki
In a route map configuration, this command is used to indicate what actions need to be performed for
the validation state being configured. When a prefix is validated with the RPKI cache, the following
three states are reported, valid, invalid, and not found. Use this command to configure the matching
criteria. Once you have configured the matching parameter, you must configure the various actions that
need to be performed when a prefix is received and is matched with the RPKI cache on the SLX device.
Syntax
match rpki { valid | invalid | not-found }
[no] match rpki { valid | invalid | not-found }
Parameters
valid
Indicates that the received prefix is valid when compared with the local RPKI cache.
invalid
Indicates that the received prefix is invalid when compared with the local RPKI cache.
not-found
Indicates that the received prefix is not-found when compared with the local RPKI cache.
Modes
Route Map
Usage Guidelines
Use the [no] format of this command to remove match rpki configured for a route map
configuration.
Examples
This command shows the steps to create a match rpki configuration within the Route Map (BGP)
permit entry.
This command adds the other configurations for this route map permit entry.
SLX(config-route-map-rm-bgp-p-test-01/permit/1)#
SLX(config-route-map-rm-bgp-p-test-01/permit/1)# match metric 10
SLX(config-route-map-rm-bgp-p-test-01/permit/1)# continue
SLX(config-route-map-rm-bgp-p-test-01/permit/1)# set weight 10
This example shows the steps to remove the match rpki configuration from an existing route-map
configuration.
(1)SLX(config-route-map-rm-bgp-p-test-01/deny/1)#
SLX(config-route-map-rm-bgp-p-test-01/deny/1)# match rpki invalid
SLX(config-route-map-rm-bgp-p-test-01/permit/1)#
match source-port
Configures matching based on UDP or TCP source port for a route-map sequence number.
Syntax
match source-port { eq | gt | lt } port-num-1
match source-port neq port-num-1 [ … port-num-32 ]
match source-port range port-num-1 port-num-2
no match source-port { eq | gt | lt } port-num-1
no match source-port neq port-num-1 [ … port-num-32 ]
no match source-port range port-num-1 port-num-2
Command Default
Matching based on source port is not configured.
Parameters
eq port-num-1
Specifies that matching occurs when the packet source port is equal to the specified port
number, which must be a valid UDP or TCP port number in the range from 0 through 65535.
gt port-num-1
Specifies that matching occurs when the packet source port is greater than the specified port
number, which must be a valid UDP or TCP port number in the range from 0 through 65535.
lt port-num-1
Specifies that matching occurs when the packet source port is less than the specified port
number, which must be a valid UDP or TCP port number in the range from 0 through 65535.
neq port-num-1 [ … port-num-32 ]
Specifies that matching occurs when the packet destination port is not equal to all of the
specified ports. You can specify a maximum of 32 ports. Specified ports must be a valid UDP or
TCP port number in the range from 0 through 65535.
range port-num-1 port-num-2
Specifies that matching occurs when the packet source is within the specified range of port
numbers, which must be a valid UDP or TCP port numbers in the range from 0 through 65535.
Modes
Route-map configuration mode
Usage Guidelines
When match protocol and match source-port are specified in the same stanza, the protocol
specified by the match protocol command must be either TCP or UDP.
Up to 128 match source-port statements are allowed per route-map sequence number for the
following options:
• eq
• range
When multiple match source-port statements of the same type exist, matching occurs when
traffic matches any one of the statements.
Only one match source-port statement is allowed per route-map sequence number for the
following options:
• lt
• gt
• neq
Note
Configuring the range option may create a lot of TCAM entries (due to rule expansion).
Examples
The following example shows how to configure matching based on a source port numbered 45 for
sequence number 4 in a route-map named rm.
The following example shows how to configure matching based on source port for sequence number 4
in a route-map named rm; a match occurs when traffic source port is not equal to 34 and 56 and 67.
device# configure terminal
device(config)# route-map rm permit 4
device(config-route-map-rm/permit/4)# match source-port neq 34 56 67
match tcp-flags
Configures Transmission Control Protocol (TCP) flag-based matching for a route-map sequence
number.
Syntax
match tcp-flags { any | all } [ ack | not-ack ] [ cwr | not-cwr ] [ ece |
not-ece ] [ fin | not-fin ] [ push | not-push ] [ rst | not-rst ]
[ syn | not-syn ] [ urg | not-urg ]
no match tcp-flags { any | all } [ ack | not-ack ] [ cwr | not-cwr ]
[ ece | not-ece ] [ fin | not-fin ] [ push | not-push ] [ rst | not-
rst ] [ syn | not-syn ] [ urg | not-urg ]
Command Default
Matching based on TCP flags is not configured.
Parameters
all
Specfies that matching occurs when traffic matches all of the subsequent specified options.
any
Specfies that matching occurs when traffic matches any of the subsequent specified options.
ack
Configures matching based on TCP Acknowledgement flag.
not-ack
Configures matching based on no TCP Acknowledgement flag.
cwr
Configures matching based on TCP Congestion Window Reduced (CWR) flag. This match
criterion is not supported in the hardware but is still received and advertised by BGP.
not-cwr
Configures matching based on no TCP CWR flag. This match criterion is not supported in the
hardware but is still received and advertised by BGP.
ece
Configures matching based on TCP Explicit Congestion Notification Echo (ECE) flag. This match
criterion is not supported in the hardware but is still received and advertised by BGP.
not-ece
Configures matching based on no TCP ECE flag. This match criterion is not supported in the
hardware but is still received and advertised by BGP.
fin
Configures matching based on TCP FIN (finish) flag.
not-fin
Modes
Route-map configuration mode
Usage Guidelines
When match protocol and match tcp-flags are specified in the same stanza, the protocol
specified by the match protocol command must be TCP; specifying any other protocol value using
the match protocol command results in the rule being evaluated as false and it becomes inactive.
When it is possible to have multiple flag options together in a TCP packet header; for example SYN, ACK
and so on, you can configure all options using one match tcp-flags command.
Up to 128 match tcp-flags configurations are allowed per route-map sequence number.
When multiple match tcp-flags configurations exist, matching occurs when traffic matches any
one of the configurations.
Examples
The following example shows how to configure matching on the SYN and ACK TCP flags for sequence
number 4 under a route-map named rm.
The following example shows how to configure matching on both the PUSH and ACK TCP flags for
sequence number 4 under a route-map named rm.
match vlan
Matches a VLAN to a class map.
Syntax
match vlan VLAN-number
Parameters
VLAN-number
Specifies a valid VLAN number.
Modes
Class map configuration mode.
Usage Guidelines
The command is used after the class-map command is entered.
Examples
The following example matches a VLAN to a class map.
device(config)# class-map p2
device(config-classmap)# match vlan 500
max-age
Sets the interval time in seconds between messages that the spanning tree receives from the interface.
Syntax
max-age seconds
no max-age
Command Default
20 seconds.
Parameters
seconds
Configures the STP interface maximum age. Valid values range from 6 through 40.
Modes
Spanning tree configuration mode
Usage Guidelines
Use this command to control the maximum length of time that passes before an interface saves its
configuration Bridge Protocol Data Unit (BPDU) information.
If the vlan parameter is not provided, the seconds value is applied globally for all per-VLAN
instances. However, for VLANs that have been configured explicitly, the per-VLAN configuration takes
precedence over the global configuration.
When configuring the maximum age, the max-age command setting must be greater than the
hello-time command setting. The following relationship should be kept:
Examples
To configure the maximum age to 10 seconds:
max-bypasses
Use the max-bypasses command to configure the maximum number of dynamic bypass LSPs that
can be created in the system or on a MPLS interface.
Syntax
max-bypasses { max_bypass_count }
no max-bypasses { max_bypass_count }
Command Default
The default value is 250.
Parameters
max_bypass-count
This number must be less than or equal to the global maximum number of bypass LSPs; that is,
the total amount of static bypasses and dynamic bypasses that can be configured on a router or
on an interface. The value can be between 1 and 500.
Modes
MPLS router dynamic bypass configuration mode (config-router-mpls-dynamic-bypass).
MPLS router MPLS interface dynamic bypass configuration mode (config-router-mpls-if ethernet-
slot/port-dynamic-bypass)
Usage Guidelines
The maximum number of bypass LSPs supported on a router is limited to 500. The maximum number
of dynamic bypass LSP that can be configured on a system is (500 - (current number of configured
Bypass LSPs)).
When this parameter is not configured under interface mode, the global max-bypasses parameter
value is considered for this parameter. This parameter value must be less than the globally set max-
bypasses value.
The no form of the command removes the maximum bypass limit and falls back to the default value of
250.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the maximum number of bypasses to 300.
device>configure
device(config)# router mpls
device9Config-router-mpls)# dynamic bypass
device(config-router-mpls-dynamic-bypass)# max-bypasses 300
the following example disables the max-bypasses command for MPLS Ethernet interface 0/8.
device>configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# disable
max-bypasses-per-mp
Use the max-bypasses-per-mp command in the global mode or interface mode to configure the
maximum number of dynamic bypass LSPs that can be created to a merge point.
Syntax
max-bypasses-per-mp { max_bypass_per_mp_count }
no max-bypasses-per-mp { max_bypass_per_mp_count }
Command Default
The system inherits the configured max-bypasses command value.
Parameters
max_bypass_per_mp_count
Specifies the number of maximum bypasses for each merge point. The range is from 1 to 500.
Modes
MPLS router dynamic bypass configuration mode (config-router-mpls-dynamic-bypass).
Usage Guidelines
The global value is taken as the interface mode maximum bypasses per MP default value (when the
user has not configured this value in the interface mode).
This is the limit for the total number of dynamic bypass LSPs that can be created to a MP corresponding
to a protected interface. A PLR can have 'M' number of MP to a protected LSP. There can be 'N' number
of protected LSPs riding on an interface with dynamic bypass enabled. The max-bypasses configuration
limits the maximum number of dynamic bypass LSPs that can be sent to each Merge Point.
When the max-bypasses-per-mp changes to a value which is less than the current active number of
dynamic bypasses, then the limit changes to the new value and this limit is considered for the next new
creations. Existing exceeding number dynamic bypasses do not delete.
When the max-bypasses-per-mp changes to a value which is more than system max-bypasses
limit, then there is a warning message.
The no form of the command removes the maximum bypasses per MP limit and falls back to its default
value, which is the max-bypasses value at the time of issuing this command.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the maximum number of bypasses per merge point to 300.
device>configure
device(config)# router mpls
device(config-router-mpls)# dynamic-bypass
device(config-router-mpls-dynamic-bypass)# max-bypasses-per-mp 100
The following example configures MPLS Ethernet interface 0/8 to a maximum number of bypasses per
merge point to 5.
device>configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# max-bypasses-per-mp 5
max-lsp-lifetime
Sets the maximum number of seconds an unrefreshed Link State PDU (LSP) remains in the LSP
database of a device.
Syntax
max-lsp-lifetime secs
max-lsp-lifetime secs
Command Default
The default maximum lifetime is 1200 seconds (20 minutes).
Parameters
secs
Specifies the maximum lifetime in seconds. Valid values range from 1 through 65535 seconds.
The default is 1200 seconds.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example changes the maximum LSP lifetime to 2400 seconds.
device# configure terminal
device(config)# router isis
device(config-isis-router)# max-lsp-lifetime 2400
max-mcache
Configures the maximum size of the multicast cache.
Syntax
max-mcache num
no max-mcache
Command Default
By default, the size of the multicast cache is 32768 entries for IPv4 and 4096 entries for IPv6.
Parameters
num
Specifies the number of entries in the multicast cache. Valid values range from 1 through 32768
for IPv4 and from 1 through 4096 for IPv6.
Modes
Router PIM configuration mode
Usage Guidelines
If the max-mcache is changed to a value that is less than the current max-mcache value, the existing
cache routes are not automatically deleted. The cache routes are deleted when new routes are added.
The no max-mcache form of the command restores the default size of the maximum multicast cache.
Examples
The following example changes the multicast cache to 500 entries for IPv4.
device(config)# router pim
device(config-pim-router)# max-mcache 500
The following example changes the multicast cache to 500 entries for IPv6.
device(config)# ipv6 router pim
device(config-ipv6-router-pim-vrf-default-vrf)# max-mcache 500
max-metric router-lsa
Advertises the maximum metric value in different Link State Advertisements (LSAs).
Syntax
max-metric router-lsa [ all-vrfs ] [ all-lsas | external-lsa metric-value
| link { all | ptp | stub | transit } | summary-lsa metric-value |
on-startup { time | wait-for-bgp [ all-lsas | summary-lsa metric-
value | external-lsa metric-value | link { all | ptp | stub |
transit } ] } ]
no max-metric router-lsa [ all-vrfs ] [ all-lsas | external-lsa | link
{ all | ptp | stub | transit } | summary-lsa | on-startup { time |
wait-for-bgp [ all-lsas | link [ all ] ] } ]
Parameters
all-vrfs
Applies the configuration change to all instances of OSPF.
all-lsas
Sets the summary-lsa and external-lsa optional parameters to the corresponding default
max-metric value. For a non-default instance of OSPF, only the summary-lsa and external-lsa
parameters are set.
external-lsa metric-value
Modifies the metric of all external type 5 LSAs to equal the specified value or a default value. The
range for metric value is 1 to 16777214 (0x00001 - 0x00FFFFFE), and the default is 16711680
(0x00FF0000).
link
Specifies the types of links for which the maximum metric is advertised. By default, the
maximum metric is advertised only for transit links.
all
Advertises the maximum metric in Router LSAs for all supported link types.
ptp
Advertises the maximum metric in Router LSAs for point-to-point links.
stub
Advertises the maximum metric in Router LSAs for stub links.
transit
Advertises the maximum metric in Router LSAs for transit links. This is the default link type.
summary-lsa metric-value
Modifies the metric of all summary type 3 and type 4 LSAs to equal the specified value or a
default value. The range for metric value is 1 to 16777215 (0x00001 - 0x00FFFFFE), and the
default is 16711680 (0x00FF0000).
on-startup
Modes
OSPF router configuration mode
Usage Guidelines
Use this command to set the maximum metric value advertised in different Link State Advertisements
(LSAs). When enabled, the router configures the maximum value of the metric for routes and links
advertised in various types of LSAs. Because the route metric is set to its maximum value, neighbors
will not route traffic through this router except to directly connected networks. Thus, the device
becomes a stub router, which is desirable when you want:
• Graceful removal of the router from the network for maintenance.
• Graceful introduction of a new router into the network.
• To avoid forwarding traffic through a router that is in critical condition.
Enter no max-metric router-lsa all-lsas to disable advertising the maximum metric value
in different LSAs.
Examples
The following example advertises the maximum metric value using the all-lsas option.
Syntax
max-metric router-lsa [ all-lsas | external-lsa metric-value | include-
stub | on-startup { time | wait-for-bgp } | summary-lsa metric-
value ]
no max-metric router-lsa [ all-lsas | external-lsa | include-stub | on-
startup { time | wait-for-bgp } | summary-lsa ]
Parameters
all-lsas
Sets the summary-lsa and external-lsa optional parameters to the corresponding default
max-metric value. For a non-default instance of OSPFv3, only the summary-lsa and external-lsa
parameters are set.
external-lsa metric-value
Configures the maximum metric value for all external type-5 and type-7 LSAs. The range for
metric value is 1 to 16777214 (0x00001 - 0x00FFFFFE), and the default is 16711680
(0x00FF0000).
include-stub
Specifies the advertisement of the maximum metric value for point-to-point and broadcast stub
links in the intra-area-prefix LSA..
on-startup
Applies the configuration change at the next OSPF startup.
time
Sets the time (in seconds) for which the specified links in Router LSAs are advertised when the
metric is set to the maximum value of 0xFFFF. The range for time is 5 to 86400.
wait-for-bgp
Specifies that OSPFv3 should wait until BGP has finished route table convergence before
advertising the links with the normal metric, or for no more than 600 seconds.
summary-lsa metric-value
Configures the maximum metric value for all summary type 3 and type 4 LSAs. The range for
metric value is 1 to 16777215 (0x00001 - 0x00FFFFFE), and the default is 16711680
(0x00FF0000).
Modes
OSPFv3 router configuration mode
Usage Guidelines
Use this command to set the maximum metric value advertised in different Link State Advertisements
(LSAs). When enabled, the router configures the maximum value of the metric for routes and links
advertised in various types of LSAs. Because the route metric is set to its maximum value, neighbors
will not route traffic through this router except to directly connected networks. Thus, the device
becomes a stub router, which is desirable when you want:
• Graceful removal of the router from the network for maintenance.
• Graceful introduction of a new router into the network.
• To avoid forwarding traffic through a router that is in critical condition.
Enter no max-metric router-lsa to disable advertising the maximum metric value in different
LSAs.
Examples
The following example configures an OSPFv3 device to advertise a maximum metric and sets the
maximum metric value for all external type-5 and type-7 LSAs to 1000.
The following example configures an OSPFv3 device to advertise a maximum metric and specifies the
advertisement of the maximum metric value for point-to-point and broadcast stub links in the intra-
area-prefix LSA.
The following example configures an OSPFv3 device to advertise a maximum metric until BGP routing
tables converge or until the default timer of 600 seconds expires.
The following example configures an OSPFv3 device to advertise a maximum metric and sets the
maximum metric value for all summary type-3 and type-4 LSAs to 100.
max-neighbor-reconnect-time
Specifies the maximum time that this router must wait for a graceful restart (GR) neighbor to restore
the LDP session.
Syntax
max-neighbor-reconnect-time seconds
no max-neighbor-reconnect-time seconds
Command Default
120 seconds
Parameters
seconds
Specifies the maximum time in seconds that this router must wait for a GR neighbor to restore
the LDP session. Enter a integer from 60 to 300. The default setting is 120.
Modes
MPLS LDP GR configuration mode
Usage Guidelines
The no form of the command resets the default time of 120 seconds.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the LDP GR timer to 180 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# graceful-restart
device(config-router-mpls-ldp-gr)# max-neighbor-reconnect-time 180
max-neighbor-recovery-time
Specifies the maximum amount of time that this router waits for a graceful restart (GR) neighbor to
complete its GR recovery after the LDP session has been reestablished.
Syntax
max-neighbor-recovery-time seconds
no max-neighbor-recovery-time seconds
Command Default
The default maximum time is120 seconds.
Parameters
seconds
Specifies the maximum amount of time in seconds that this router waits for a GR neighbor to
complete its GR recovery after the LDP session has been reestablished. Enter a integer from 60
to 3600. The default setting is 120.
Modes
MPLS LDP GR configuration mode
Usage Guidelines
Recovery-time must be chosen accordingly taking into account the time it takes for RTM to recompute
the routes and the number of Layer 3 FECs that need to be recovered as part of the LDP GR recovery.
This is applicable to GR processing on ingress as well as transit LSRs.
The no form of the command resets the default time of 120 seconds.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the LDP GR timer to 240 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# graceful-restart
device(config-router-mpls-ldp-gr)# max-neighbor-recovery-time 240
maxas-limit
Imposes a limit on the number of autonomous systems in the AS-PATH attribute.
Syntax
maxas-limit in num
no maxas-limit in
Command Default
Disabled.
Parameters
in
Allows an AS-PATH attribute from any neighbor to impose a limit on the number of autonomous
systems.
num
Range is from 0 through 300. The default is 300.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
Examples
This example sets the limit on the number of BGP4 autonomous systems in the AS-PATH attribute to
100.
maximum-paths (BGP)
Sets the maximum number of BGP4 and BGP4+ shared paths.
Syntax
maximum-paths num [ use-load-sharing ]
no maximum-paths
Command Default
Disabled.
Parameters
num
Specifies the maximum number of paths across which the device balances traffic to a given BGP
destination. Valid values range is from 1 through 64. The default is 1.
use-load-sharing
Uses the maximum IP ECMP path value supported (64) without enabling BGP level ECMP.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use this command to change the maximum number of BGP4 shared paths, either by setting a value or
using the maximum IP ECMP path value supported (64) without enabling BGP level ECMP.
If the configured num value is less than the possible number of ECMP paths available, BGP routes may
not take the same number of ECMP paths. The set of ECMP paths may not be the same for different
prefixes.
Examples
This example sets the maximum number of BGP4 shared paths to 8.
This example sets the maximum number of BGP4+ shared paths to 64 without enabling BGP level
ECMP.
This example sets the maximum number of BGP shared paths to 2 in a nondefault VRF instance in the
IPv6 address family.
maximum-paths (IS-IS)
Specifies the number of paths Intermediate System-to-Intermediate System (IS-IS) can calculate and
install in the IPv4 or IPv6 forwarding table.
Syntax
maximum-paths number
no maximum-paths number
Command Default
The default is 8 paths.
Parameters
value
Specifies the number of paths. Valid values range from 1 through 64 paths. The default is 8.
Modes
IS-IS address-family IPv4 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command resets number of paths to the default number of 8.
Examples
The following example specifies that the number of paths IS-IS can calculate and install in the IP
forwarding table is 10.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv4 unicast
device(config-router-isis-ipv4u)# maximum-paths 10
The following example resets the number of paths IS-IS can calculate and install in the IPv6 forwarding
table to 8 (the default).
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv6 unicast
device(config-router-isis-ipv6u)# no maximum-paths
maximum-paths (OSPF)
Changes the maximum number of OSPF shared paths.
Syntax
maximum-paths num
no maximum-paths
Parameters
num
Maximum number of paths across which the device balances traffic to a given OSPF destination.
The range is from 1 through 64. The default is 8.
Modes
OSPF router configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example sets the maximum number of shared paths to 22.
Syntax
maximum-paths { ebgp num | ibgp num }
no maximum-paths
Command Default
This option is disabled.
Parameters
ebgp
Specifies eBGP routes or paths.
ibgp
Specifies iBGP routes or paths.
num
The number of equal-cost multipath routes or paths that are selected. Range is from 1 through
64. 1 disables equal-cost multipath.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
Enhancements to BGP load sharing support the load sharing of BGP4 and BGP4+ routes in IP Equal-
Cost Multipath (ECMP), even if the BGP multipath load-sharing feature is not enabled by means of the
use-load-sharing option for the maximum-paths command. You can set separate values for
IGMP and ECMP load sharing. Use this command to specify the number of equal-cost multipath eBGP
or iBGP routes or paths that are selected.
Examples
This example sets the number of equal-cost multipath eBGP routes or paths that will be selected to 6 in
the IPv4 address family.
This example sets the number of equal-cost multipath iBGP routes or paths that will be selected to 4 in
the IPv6 address family.
This example sets the number of equal-cost multipath EBGP routes or paths that will be selected to 3
for the IPv4 address family for VRF instance "red".
measured-boot
Measured Boot is a mechanism to ensure that the integrity of the firmware and software running on a
SLX hardware platform is maintained. This is ensured by the calculating a hash of the values of each
stage in the boot process and comparing these values with the values stored on a remote verification
server.
Syntax
measured-boot [ enable | disable ]
Modes
Global Configuration Mode
Parameters
enable
Usage Guidelines
This configuration requires the SLX device to be rebooted.
Examples
The following is an example of enabling the Measured Boot feature on the SLX device.
SLX #configure terminal
SLX (config)# measured-boot enable
The following is an example of disabling Measured Boot feature on the SLX device.
SLX # configure terminal
SLX (config)# measured-boot disable
Platform Availability
This command and mode is only available on the Extreme 8720 and Extreme 8520 devices.
measurement-interval
Configures the SLM Measurement interval for Connectivity Fault Management (CFM).
Syntax
measurement-interval interval
no measurement-interval
Command Default
The default interval is fifteen minutes.
Parameters
interval
The interval period, in minutes. The range of valid values is from 1 through 1440.
Modes
CFM protocol configuration mode
Usage Guidelines
The no measurement-interval command resets the interval to the default value.
Examples
Example of setting the interval when configured for VLAN 30.
device# configure terminal
device(config-cfm)# domain name md1 level 4
device(config-cfm-md-md1)# ma-name ma1 id 1 vlan-id 30 pri 7
device(config-cfm-md-ma-ma1)# measurement interval 25
med-missing-as-worst
Configures the device to favor a route that has a Multi-Exit Discriminator (MED) over a route that does
not have one.
Syntax
med-missing-as-worst
no med-missing-as-worst
Modes
BGP configuration mode
Usage Guidelines
When MEDs are compared, by default the device favors a low MED over a higher one. Because the
device assigns a value of 0 to a route path MED if the MED value is missing, the default MED comparison
results in the device favoring the route paths that do not have MEDs.
The no form of the command restores the default where a device does not favor a route that has a MED
over other routes.
Examples
The following example configures the device to favor a route containing a MED.
member (cluster)
Defines the bridge-domains and vlans shared between cluster nodes and extended on the ICL.
Syntax
member { bridge-domain | vlan }
Command Default
The cluster has no member bridge-domains or vlans
Parameters
bridge-domain
Configure the bridge-domain on the cluster
all
Modes
Cluster configuration mode
Usage Guidelines
The all parameter is the default configuration for both member bridge-domain and member
vlan.
Examples
The following example configures cluster S1-A1 as a member of all vlans, and all bridge-domains except
those listed (10, 11, 12).
device# config
Entering configuration mode terminal
device(config)# cluster S1-A1
device(config-cluster-S1-A1)# member vlan all
device(config-cluster-S1-A1)# member bridge-domain except 10,11,12
Snowball-MCT1(config-cluster-S1-A1)#
member-bridge-domain
Configures member bridge domains for a topology group.
Syntax
member-bridge-domain { add | remove } bridge_domain_id
Command Default
The topology group has no member bridge domains.
Parameters
add
Add a bridge domain to the topology group.
remove
Remove a bridge domain from the topology group.
bridge_domain_id
Bridge domain ID or the bridge domain range; for example: 1, 2, 4-7, 8, 9-22, 55-66. Tha maximun
is 253 characters.
Modes
Topology group configuration mode.
Usage Guidelines
You must first add a master VLAN to the topology group.
Examples
The following example adds the member VLANs to the STP topology group.
member-vlan (STP)
Adds member VLANs to an STP topology group.
Syntax
member-vlan { add | remove } vlan_id
Command Default
The topology group has no member VLANs.
Parameters
add
Add a VLAN to the topology group.
remove
Remove a VLAN from the topology group.
vlan_id
Adds a member VLAN ID to the STP topology group. This can be a single VLAN or a range of
VLANs. For example: 2, 4-7, 8, 9-22, 55-66. The maximum input is 253 characters.
Modes
Topology group configuration mode.
Usage Guidelines
The VLAN(s) must be configured before adding to the topology group.
All the VLANs in the member group inherit the STP settings of the master VLAN in the group.
Examples
The following example adds the member VLANs to the STP topology group.
mep
Adds local ports as Maintenance End Points (MEPs) to a specific Maintenance Association (MA).
Syntax
mep { mep-id [ up | down ] | [ vlan vlan-id ] | [ ethernet slot/ port] |
[ port-channel channel ]}
no mep mep-id
Command Default
There are no MEP configured.
Parameters
mep-id
Specifies the ID of the MEP.
up
Specifies MEP in the up direction.
down
Specifies MEP in the down direction.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
inner-vlan vlan-id
Specifies the Inner VLAN.
port-channel index
Specifies a port-channel.
vlan vlan-id
Specifies a VLAN.
Modes
CFM protocol configuration mode
Usage Guidelines
The no mep command deletes the MEP from the MA.
A Maintenance Domain (MD) is part of a network controlled by one operator. The MD levels are carried
on all CFM frames to identify different domains. Every MD can be divided into smaller networks having
multiple MEPs. Usually an MA is associated with a service instances (for example a VLAN or a VPLS).
VPLS is not supported on devices based on the XGS chipset family. For a list of such devices, see
"Supported Hardware".
MEP is located on the edge of an MA. It defines the endpoint of the MA. Each MEP has unique ID
(MEPID) within MA. The connectivity in a MA is defined as connectivity between MEPs. The MEP
generates Continuity Check Message and multicasts to all the other MEPs in the same MA to verify
connectivity.
Each MEP has a direction, down or up. Down MEP receives CFM PDUs from the LAN and sends CFM
PDUs towards the LAN. Up MEP receives CFM PDUs from a bridge relay entity and sends CFM PDUs
towards the bridge relay entity on a bridge. End stations support down MEPs only because they have
no bridge relay entities.
Examples
This example defines a MEP for VLAN 30 in the down direction.
device# configure terminal
device(config)# protocol cfm
device(config-cfm)# domain name md1 level 4
device(config-cfm-md-md1)# ma-name ma1 id 1 vlan-id 30 priority 3
device(config-cfm-md-ma-ma1)# mep 1 down ethernet 0/2
message-interval
Configures the frequency with which PIM Join and Prune messages are sent.
Syntax
message-interval num
no message-interval num
Command Default
The default frequency is every 60 seconds.
Parameters
num
The frequency in seconds. Valid values range from 10 through 65535 seconds.
Modes
Router PIM configuration mode
Usage Guidelines
The no message-interval form of the command restores the default frequency of 60 seconds.
Examples
This example configures a frequency of 1 hour for IPv4 PIM.
device(config)# router pim
device(config-pim-router)# message-interval 3600
message-interval
Specifies a value for an Ethernet Ring Protection (ERP) message interval.
Syntax
message-interval time
no message-interval
Command Default
The default message-interval value is 5000 milliseconds (ms).
Parameters
time
Time in ms. Range is from 100 through 5000, in multiples of 100.
Modes
ERP configuration mode
Usage Guidelines
Ring Automatic Protection Switching (R-APS) messages are sent continuously within an ERP ring.
Examples
The following example configures a message interval of 100 ms.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# message-interval 100
metric
Assigns a metric to the LSP, which routing protocols can use to determine the relative preference
among several LSPs towards a given destination.
Syntax
metric number
no metric number
Command Default
All LSPs have a metric of 1.
Parameters
number
Specifies the metric value. Enter an integer from 1 to 65535. A lower value is preferred over a
higher value.
Modes
MPLS LSP configuration mode
Usage Guidelines
When multiple LSPs have the same destination LSR, and they have the same metric, the traffic load is
shared among them.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures LSP to22 with a metric value of 20.
device(config)# router mpls
device(config-router-mpls)# lsp to22
device(config-router-mpls-lsp-to22)# no enable
device(config-router-mpls-lsp-to22)# to 10.1.1.2
device(config-router-mpls-lsp-to22)# from 10.1.1.1
device(config-router-mpls-lsp-to22)# metric 20
device(config-router-mpls-lsp-to22)# enable
device(config-router-mpls-lsp-to22)#exit
metric-style wide
Enables the wide metric type for new style of TLVs with Intermediate System-to-Intermediate System
(IS-IS).
Syntax
metric-style wide [ level-1 | level-2 ]
no metric-style wide
Command Default
The wide metric type is not used.
Parameters
level-1
Modes
IS-IS address-family IPv4 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
When LDP-IGP synchronization is enabled, the wide metric type must be used.
The no form of the command disables the use of the wide metric type.
Examples
The following example enables the wide metric type for Level 1 packets for the IS-IS IPv4 unicast
address family.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv4 unicast
device(config-router-isis-ipv4u)# metric-style wide level-1
metric-type
Configures the default metric type for external routes.
Syntax
metric-type { type1 | type2 }
no metric-type { type1 | type2 }
Command Default
Type 1
Parameters
type1
The metric of a neighbor is the cost between itself and the device plus the cost of using this
device for routing to the rest of the world.
type2
The metric of a neighbor is the total cost from the redistributing device to the rest of the world.
Modes
OSPF router configuration mode
Usage Guidelines
The no form of the command restores the default setting. You must specify a type parameter when
using the no form.
Examples
The following example sets the default metric type for external routes to type 2.
minimum-links
Configures the minimum bandwidth or number of links to be running to allow the port-channel to
function.
Syntax
minimum-links num-of-links
no minimum-links
Command Default
The number of links is 1.
Parameters
num-of-links
Specifies the number of links. Device support for minimum links is as follows:
1–64
SLX 9540
SLX 9640
SLX 9740
Modes
Port-channel interface configuration mode
Usage Guidelines
Use this command to allow a port-channel to operate at a certain minimum bandwidth all the time. If
the bandwidth of the port-channel drops below that minimum number, then the port-channel is
declared operationally DOWN even though it has operationally UP members.
Examples
The following example sets the minimum number of links to 16 on a specific port-channel interface.
device# configure terminal
device(config)# interface port-channel 33
device(config-Port-channel-33)# minimum-links 16
mip-policy
Specifies the conditions in which Maintenance Intermediate Points (MIP) are automatically created on
ports.
Syntax
mip-policy { explicit | default }
no mip-policy
Command Default
The MIP policy is set to default.
Parameters
explicit
Specifies that explicit MIPs are configured only if a MEP exists on a lower MD Level.
default
Specifies that MIPs are always configured.
Modes
CFM protocol configuration mode .
Usage Guidelines
Use the no mip-policy to reset the values to the default.
A Maintenance Intermediate Point (MIP) can be created on a port and VLAN automatically, but only
when either the explicit or default policy has been defined for them. For a specific port and VLAN, a MIP
is created at the lowest level. Additionally, the level created should be the next higher than the MEP level
defined for the port and VLAN.
Use the explicit parameter to specify that explicit MIPs are configured only if a MEP exists on a lower
Maintenance Domain (MD) level.
Use the default parameter to specify that MIPs are always configured.
Examples
Example of the MIP policy command set for explicit when configured for VLAN 30.
device# configure terminal
device(config-cfm)#domain name md1 level 4
device(config-cfm-md-md1)#ma-name ma1 id 1 vlan-id 30 pri 7
device(config-cfm-md-ma-ma1)#mip-policy explicit
mode (LLDP)
Sets the LLDP mode on the device.
Syntax
mode { tx | rx }
Command Default
Both transmit and receive modes are enabled.
Parameters
tx
Specifies to enable only the transmit mode.
rx
Specifies to enable only the receive mode.
Modes
Protocol LLDP configuration mode
Examples
To enable only the transmit mode:
device(conf-lldp)# mode tx
device(conf-lldp)# mode rx
mode gre ip
Enables generic routing encapsulation (GRE) over a tunnel interface and specifies that the tunneling
protocol is IPv4.
Syntax
mode gre ip
no mode
Command Default
GRE is disabled.
Modes
Interface tunnel configuration mode
Usage Guidelines
Use the no mode gre ip command to disable the GRE IP tunnel encapsulation method for the
tunnel interface.
Examples
This example enables GRE IP encapsulation on a tunnel interface.
monitor session
Enables a port mirroring session, which sends copies of packets that enter or exit one port to another
physical port or LAG interface, where the packets can be analyzed.
Syntax
monitor session session_number
source { ethernet slot / port | port-channel index | ve index }
destination { ethernet slot / port | port-channel index } direction
dir
no monitor session session_number
Parameters
session_number
Specifies a session identification number. Valid values range from 1 through 512.
source
Specifies the interface for which you are defining a mirror.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
port-channel index
Specifies a valid port-channel interface number.
ve index
Specifies a valid virtual ethernet interface number.
destination
Specifies the physical-interface or port-channel mirror to use as the destination for mirroring.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support linecards, specify 0.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
direction dir
Specifies the direction of packets to mirror. Acceptable values are both (ingress and egress), rx
(ingress only), or tx (egress only).
Modes
Global configuration mode
Usage Guidelines
All protocols such as LLDP must be disabled on interfaces that you select to be destination interfaces.
Run the no monitor session session_number command to delete the port mirroring session.
Examples
The following example enables session 22 for monitoring traffic from source Ethernet 0/1 to destination
Ethernet 0/2 in the egress direction.
device# configure terminal
device(config)# monitor session 22
device(config-session-22)# source ethernet 0/1 destination ethernet 0/2 direction tx
The following example enables session 23 for monitoring traffic from source Ethernet 0/1 to destination
Ethernet 0/2 in the ingress direction.
device# configure terminal
device(config)# monitor session 23
device(config-session-23)# source ethernet 0/1 destination ethernet 0/2 direction rx
The following example enables session 24 for monitoring traffic from source Ethernet 0/1 to destination
Ethernet 0/2 in both directions.
device# configure terminal
device(config)# monitor session 24
device(config-session-24)# source ethernet 0/1 destination ethernet 0/2 direction both
The following example shows the configuration of mirroring from a Port Channel to a destination that is
a Port Channel. Traffic from both directions is mirrored.
SLX# configure terminal
SLX (config)# monitor session 25
SLX (config-session-25)# source port-channel 1 destination port-channel 11 direction both
mpls reoptimize
Under ordinary conditions, an LSP path does not change unless the path becomes inoperable.
Consequently, the router must be directed to consider configuration changes made to an LSP and to
optimize the LSP path based on those changes.
Syntax
mpls reoptimize { all | lsp lsp_name }
Parameters
all
Reoptimizes all LSPs.
lsplsp_name
Reoptimizes the specified LSP.
Modes
Privileged EXEC mode
Usage Guidelines
On re-optimization of an adaptive LSP, LSP accounting statistics might miss the accounting of some of
the packets.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example uses the mpls re-optimize command to re-optimize LSP to20.
device# mpls reoptimize lsp to20
mpls-interface
Configures MPLS on an interface and accesses MPLS interface sub-configuration mode to configure its
parameters.
Syntax
mpls-interface { ethernet slot/port | port-channel number | ve number }
no mpls-interface { ethernet slot/port | port-channel number | ve
number }
Parameters
ethernet slot/port
Specifies an Ethernet slot and port.
port-channel number
Specifies a port-channel interface.
ve number
Specifies the VE interface number.
Modes
MPLS configuration mode
Usage Guidelines
Use the no form of this command to remove the MPLS interface.
You cannot configure MPLS on a VE interface associated with a protocol based VLAN. The command is
rejected, and an error message is displayed.
After you enable MPLS globally on the device, you can enable it on one or more interfaces.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures MPLS on Ethernet interface 0/12.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/12
device(config-router-mpls-if-0/12)# ldp-params
device(config-router-mpls-if-0/12-ldp-params)# exit
device(config-router-mpls-if-ethernet-0/12)# rsvp
mtu (interface)
Configures the Layer 2 maximum transmission unit (MTU) size for all Ethernet interfaces and Port-
channels.
Syntax
mtu number
no mtu
Command Default
The default is 1548 bytes.
Parameters
number
Size of the Layer 2 MTU in bytes. Range is from 1548 through 9216.
Modes
Global configuration mode
Usage Guidelines
This command can be executed both globally and on an interface. If it is executed globally, interface
configurations take precedence over the global configuration.
Examples
The following example configures the Layer 2 MTU size globally.
device# configure terminal
device(config)# mtu 2000
The following example configures the Layer 2 MTU size on an Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/13
device(conf-if-eth-1/13)# mtu 2000
The following example configures the Layer 2 MTU size on a port-channel interface.
device# configure terminal
device(config)# interface port-channel 10
mtu (PW)
Configures the maximum transmission unit (MTU) for a pseudowire (PW) profile.
Syntax
mtu mtu-value
no mtu
Command Default
The MTU value is set to 1500.
Parameters
mtu-value
Specifies the maximum transmission unit (MTU) for the PW profile. Values range from 64
through 15966.
Modes
Pseudowire-profile configuration mode.
Usage Guidelines
The no form of the command restores the default configuration.
Examples
The following example shows how to set the MTU value to 2000 for a PW profile named test.
mtu-enforce
Configures MTU enforcement check for a pseudowire (PW) profile.
Syntax
mtu-enforce { false | true }
no mtu-enforce
Command Default
MTU enforcement is disabled.
Parameters
false
Disables the MTU enforcement check.
true
Enables the MTU enforcement check.
Modes
Pseudowire-profile configuration mode.
Usage Guidelines
MTU enforcement is only supported during PW signaling.
Examples
The following example shows how to enable MTU enforcement check for a PW profile named test.
multipath
Changes load sharing to apply to only iBGP or eBGP paths, or to support load sharing among paths
from different neighboring autonomous systems.
Syntax
multipath { ebgp | ibgp | multi-as }
no multipath { ebgp | ibgp | multi-as }
Command Default
This option is disabled.
Parameters
ebgp
Enables load sharing of eBGP paths only.
ibgp
Enables load sharing of iBGP paths only.
multi-as
Enables load sharing of paths from different neighboring autonomous systems.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
By default, when BGP load sharing is enabled, both iBGP and eBGP paths are eligible for load sharing,
while paths from different neighboring autonomous systems are not.
Examples
This example changes load sharing to apply to iBGP paths in the IPv4 address family.
This example enables load sharing of paths from different neighboring autonomous systems in the IPv6
address family.
This example changes load sharing to apply to eBGP paths in IPv4 VRF instance "red":
multiplier (LLDP)
Sets the number of consecutive misses of hello messages before LLDP declares the neighbor as dead.
Syntax
multiplier value
no multiplier
Command Default
Multiplier default value is 4.
Parameters
value
Specifies a multiplier value to use. Valid values range from 2 through 10.
Modes
Protocol LLDP and profile configuration modes
Usage Guidelines
Enter no multiplier to return to the default setting.
The LLDP multipler can also be configured for a specific LLDP profile. When you apply an LLDP profile
on an interface using the lldp profile command, it overrides the global configuration. If a profile is
not present, then the default global profile is used until you create a valid profile.
Examples
To set the number of consecutive misses:
device(conf-lldp)# multiplier 2
multiplier (UDLD)
Sets timeout multiplier for missed UDLD PDUs.
Syntax
multiplier value
no multiplier
Command Default
Multiplier default value is 5.
Parameters
value
Specifies a multiplier value to use. Valid values range from 3 through 10.
Modes
Protocol UDLD configuration mode
Usage Guidelines
When the device at one end is an Extreme Networks IP product, the timeout interval is the product of
the "hello" time interval at the other end and the "multiplier" value.
When the UDLD protocol times out waiting for UDLD PDUs, it will block the port.
Examples
To set the multiplier to 8:
multi-topology
Enables IPv6 Intermediate System-to-Intermediate System (IS-IS) MT in an area or a domain so that the
MT-enabled device runs IPv6 IS-IS in multi-SPF mode.
Syntax
multi-topology [ transition ]
no multi-topology [ transition ]
Command Default
The transition option is disabled.
Parameters
transition
Enables IPv6 IS-IS MT transition mode in an area or a domain so that a network operating in IPv6
IS-IS single-topology support mode can continue to work while upgrading devices to include
IPv6 IS-IS MT support.
Modes
IS-IS address-family IPv6 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
When transition mode is not enabled, the routers operating in single-topology mode do not establish
IPv6 connectivity with the routers operating in MT mode.
Examples
The following example enables IPv6 IS-IS MT.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv6 unicast
device(config-router-isis-ipv6u)# multi-topology
mvrp applicant-mode
Configures the MVRP applicant mode on the MVRP-enabled interface as normal-participant to enable
the transmission of MVRP data units (MVRPDUs) or non-participant to disable the transmission of
MVRPDUs; ensuring that no PDU exchange occurs on the port. The non-participant configuration is
recommended on an MVRP-enabled edge port to avoid sending VLAN advertisements to the
connected edge device.
Syntax
mvrp applicant-mode { normal-participant | non-participant }
no mvrp applicant-mode
Command Default
The default setting is normal-participant.
Parameters
normal-participant
Configures the port as a normal participant.
non-participant
Configures the port as a non participant.
Modes
Interface configuration mode
Usage Guidelines
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
Use the no form of this command or the normal-participant keyword to reset the default setting
of normal-participant.
Before configuring this command, you must configure the interface as switchport and enable MVRP
globally on the device and on the interface to allow the MVRP-enabled interface to participate in the
protocol.
Examples
The following example configures the edge port as non-participant.
device# configure terminal
device(config)# protocol mvrp
device(config-mvrp)# exit
device(config)# interface ethernet 0/15
device(conf-if-eth-0/15)# switchport
mvrp enable
Enables MVRP on an Ethernet or port-channel interface.
Syntax
mvrp enable
no mvrp enable
Command Default
MVRP is disabled by default on the interfaces.
Modes
Interface configuration mode
Usage Guidelines
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
Before configuring this command, you must configure the interface as switchport and globally enable
MVRP on the device to allow the MVRP-enabled interface to participate in the protocol.
Examples
The following example enables MVRP on an Ethernet interface.
device# configure terminal
device(config)# vlan 10
device(config-vlan-10)# exit
device(config)# protocol mvrp
device(config-mvrp)# exit
device(config)# interface ethernet 0/1
device(conf-if-eth-0/1)# switchport
device(conf-if-eth-0/1)# switchport mode trunk
device(conf-if-eth-0/1)# switchport trunk allowed vlan add 10
device(conf-if-eth-0/1)# mvrp enable
Syntax
mvrp registration-mode forbidden vlan { add | remove } vlanID
Command Default
By default, the registration mode for an MVRP-enabled interface is set to Normal. For a static VLAN
configuration, the registration mode is automatically set to Fixed. To prune the advertisement
propagation and deregistration of a dynamic VLAN on an MVRP-enabled interface port, you can
register the VLAN as Forbidden.
Parameters
add
Adds the specified VLAN to the forbidden VLAN list on the interface.
remove
Removes the specified VLAN from the forbidden list on the interface and allows advertising of
non-forbidden VLANs through the MVRP messages on the interface.
vlanID
Specifies an individual VLAN or a range of VLANs. For example, to add VLANs 25 through 30 to
the forbidden list, enter mvrp registration-mode forbidden vlan add 25-30.
Modes
Interface configuration mode
Usage Guidelines
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
The add keyword prevents the VLANs specified in the command from being advertised on all other
MVRP-enabled ports and also removes the specified VLANs that are dynamically registered from this
interface.
Before you configure this command, you must configure the interface as switchport and must enable
MVRP both globally and on the interface.
Examples
The following example adds VLANs 25 through 30 to the forbidden list, and removes VLAN 26 from the
forbidden list.
device# configure terminal
device(config)# protocol mvrp
device(config-mvrp)# exit
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# switchport
device(conf-if-eth-1/1)# mvrp enable
device(conf-if-eth-1/1)# switchport mode trunk
device(conf-if-eth-1/1)# switchport trunk allowed vlan add 20-24
device(conf-if-eth-1/1)# mvrp registration-mode forbidden vlan add 25-30
device(conf-if-eth-1/1)# mvrp registration-mode forbidden vlan remove 26
mvrp timer
Sets the MVRP join, leave, and leave-all timer values on an Ethernet or port-channel interface.
Syntax
mvrp timer join cs leave cs leave-all cs
no mvrp timer join cs leave cs leave-all cs
Command Default
The join timer default value is 20 centiseconds (cs).
Parameters
join cs
Specifies the join timer in centiseconds. Enter an integer from 20 to 10000000.
leave cs
Specifies the leave timer in centiseconds. Enter an integer from 100 to 10000000. The leave
timer setting must be greater than or equal to twice the join timer setting plus 30 centiseconds.
leave-all cs
Specifies the leave-all timer in centiseconds. Enter an integer from 1000 to 10000000. The
leave-all timer setting must be a minimum of three times the value of the leave timer setting.
Modes
Interface configuration mode
Usage Guidelines
MVRP is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of this command resets the timers to the global timer configuration. If the global timers
have not been configured, the timers are reset to the default values.
Before configuring this command, you must configure the interface as switchport and globally enable
MVRP on the device and on the interface to allow the MVRP-enabled interface to participate in the
protocol.
This command requires that you configure the timer values in the specified order and you must
configure all values.
When the network radius is large or the expected system load is higher normally, and since the default
timer values are aggressive, Extreme recommends that you change the timer values to higher numbers
to reduce the MVRP message exchanges and load on the system.
The configured timer settings on the individual MVRP-enabled interfaces override the global timer
configuration.
The join timer is not run periodically but is triggered by the MVRP events and the device state changes.
However, the leave-all timer is periodic required for garbage collection purposes.
Examples
The following example configures the MVRP timers on an Ethernet interface.
device# configure terminal
device(config)# protocol mvrp
device(config-mvrp)# exit
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# switchport
device(conf-if-eth-1/1)# mvrp enable
device(conf-if-eth-1/1)# switchport mode trunk
device(conf-if-eth-1/1)# switchport trunk allowed vlan add 20-24
device(conf-if-eth-1/1)# mvrp timer join 40 leave 200 leave-all 2000
device(conf-if-eth-1/1)#
name (ERP)
Specifies an optional name for an Ethernet Ring Protection (ERP) instance.
Syntax
name string
no name string
Command Default
No ERP instance name is configured by default.
Parameters
string
An ASCII string. Range is from 1 through 32 characters. Underscores and dashes are allowed.
Modes
ERP configuration mode
Usage Guidelines
Use the no form of this command to remove the ERP instance name.
Examples
The following example specifies the name of an ERP instance.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# name mainRing
name-prefix
Use the name-prefix interface command to specify a name prefix for the dynamic bypass LSPs to be
created for the MPLS protected interface.
Syntax
name-prefix name
no name-prefix name
Command Default
The default name prefix is dbyp.
Parameters
name
Specifies the selected character string. The length of the character string is between 1 and 21
characters.
Modes
MPLS router MPLS interface dynamic bypass configuration mode (config-router-mpls-if-ethernet-
slot/port -dynamic-bypass).
Usage Guidelines
The no form of the command removes the name prefix and sets its value to the default string dbyp.
When configuring, the dynamic bypass LSPs names must start with this name prefix, appended by
interface IP, Merge Point IP (for node protection), and a unique number.
The name prefix configuration is only allowed when there no existing dynamic bypasses corresponding
to a dynamic bypass interface. When the user wants to change the name prefix, the user must disable
the dynamic bypass on the interface and reconfigure the name prefix, then re-enable the dynamic
bypass on the interface.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the name prefix for MPLS Ethernet interface 0/8 to MyDbypass.
device>configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-rouoter-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# name-prefix MyDbypass
nbr-timeout
Configures the length of time a PIM device waits for hello messages before considering a neighbor to be
absent.
Syntax
nbr-timeout num
no nbr-timeout
Command Default
The default interval is 105 seconds.
Parameters
num
Specifies the timeout value in seconds. Valid values range from 35 through 12600 seconds.
Modes
Router PIM configuration mode
Usage Guidelines
The absence of PIM hello messages from a neighboring device indicates that the neighbor is absent. The
interval should not be less than 3.5 times the hello timer value.
The no nbr-timeout form of the command reverts the timeout to the default of 105 seconds.
Examples
This example configures a timeout of 600 seconds for IPv4 PIM.
device(config)# router pim
device(config-pim-router)# nbr-timeout 600
neighbor activate
Enables the exchange of information with BGP neighbors and peer groups.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } activate
no neighbor { ip-address | ipv6-address | peer-group-name } activate
Command Default
Enabling address exchange for the IPv4 address family is enabled. Enabling address exchange for the
IPv6 address family is disabled.
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command disables the exchange of an address with a BGP neighbor or peer group.
Examples
The following example establishes a BGP session with a neighbor with the IPv6 address
2001:2018:8192::125.
The following example establishes a BGP session with a neighbor with the IP address 10.1.1.1 in L2VPN
EVPN configuration mode.
neighbor additional-paths
Enables an additional-paths capability for a specific peer or peer group in a Border Gateway Protocol
(BGP) address family.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } additional-paths
{ receive [ send ] | send }
no neighbor { ip-address | ipv6-address | peer-group-name } additional-
paths receive
no neighbor { ip-address | ipv6-address | peer-group-name } additional-
paths send
Command Default
Specific peer devices or peer groups configured under a BGP address family are not capable of
receiving or sending additional-paths.
Parameters
ip-address
Address of the neighbor in IPv4 address format.
ipv6-address
Address of the neighbor in IPv6 address format.
peer-group-name
Peer group name of the neighbor.
additional-paths
Enables an additional-paths capability.
receive
Enables the capability to receive additional-paths.
send
Enables the capability to send additional-paths.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Note
An additional-paths capability configured at peer level takes precedence over any additional-
paths capability configured at either the peer group or BGP address family level.
An additional-paths capability can be enabled for a specific peer or peer group as receive only, send
only, or both send and receive.
The no form of the command disables the additional-paths capability for a specific peer device or peer
group.
To remove the configuration when both the receive and send options have been set, you should
enter both the no neighbor additional-paths command, specifying the receive option to
disable the capability to receive additional-paths, and the no neighbor additional-paths
command, specifying the send option to disable the capability to send additional-paths.
Examples
The following example shows how to enable a peer device (10.1.2.3) configured under the IPv4 unicast
address family to both receive and send additional-paths.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-ipv4u)# neighbor 10.1.2.3 additional-paths receive send
The following example shows how to disable the capability to receive additional-paths for a specific
peer device (10.1.2.3) in the IPv4 unicast address family.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-ipv4u)# no neighbor 10.1.2.3 additional-paths receive
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } additional-paths
advertise { all [ best num ] [ group-best ] | best num | group-best }
no neighbor { ip-address | ipv6-address | peer-group-name } additional-
paths advertise all
no neighbor { ip-address | ipv6-address | peer-group-name } additional-
paths advertise best num
no neighbor { ip-address | ipv6-address | peer-group-name } additional-
paths advertise group-best
Parameters
ip-address
Address of the neighbor in IPv4 address format.
ipv6-address
Address of the neighbor in IPv6 address format.
peer-group-name
Peer group name of the neighbor.
all
Causes all routes to be advertised as additional-paths to the specified neighbor or peer group. A
maximum of 16 routes is allowed.
best num
Specifies the number of best paths allowed for advertisement as additional-paths to the
specified neighbor or peer group. The number ranges from 2 through 16.
group-best
Causes group-best paths to be advertised as additional-paths to the specified neighbor or peer
group. Only routes with a rank less than or equal to 16 are allowed. A route with a rank greater
than 16 (even when it is the group best path), is not eligible for selection as an additional path
advertised to a neighbor or peer group.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Note
The set of paths configured by using the neighbor additional-paths advertise
command must be a subset of selected paths; that is, paths previously configured by using
the additional-paths select command under the particular BGP address-family
configuration mode.
The additional-paths advertise command options (all, best, and group-best ) are not
mutually exclusive. When you configure a combination of these options, the combined configuration is
applied to the BGP address family.
The no form of the command removes the specified configuration. When more than one option is
configured, it is recommended that you disable each configured option separately; for example, by
using the no neighbor additional-paths advertise command specifying the all option to
disable the all configuration, and so on.
Examples
The following example shows how to configure the advertisement of all (a maximum of 16 is allowed)
routes for a peer device, 10.123.123.1, under the IPv4 unicast address family.
device# configure terminal
device(condig)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-router-ipv4u)# neighbor 10.123.123.1 additional-paths advertise all
The following example shows how to restore the default configuration when all options (all, best,
and group-best) were previously configured under the IPv4 unicast address family.
device# configure terminal
device(condig)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-router-ipv4u)# no neighbor 10.123.123.1 additional-paths advertise all
device(config-bgp-router-ipv4u)# no neighbor 10.123.123.1 additional-paths advertise best
2
device(config-bgp-router-ipv4u)# no neighbor 10.123.123.1 additional-paths advertise
group-best
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } additional-
paths disable
no neighbor { ip-address | ipv6-address | peer-group-name } additional-
paths disable
Command Default
By default, an additional-paths capability configured for a specific BGP address family applies to all
peer groups and peers configured under the address family, and an additional-paths capability
configured for a peer group applies to all peers within the group.
Parameters
ip-address
Address of the neighbor in IPv4 address format.
ipv6-address
Address of the neighbor in IPv6 address format.
peer-group-name
Peer group name of the neighbor.
Modes
BGP configuration mode
Usage Guidelines
When the capability to send and receive additional-paths is configured at the address family or peer
group level, the capability applies to all neighbors configured under the address family or within the
peer group: you can use the neighbor additional-paths disable command to disable this
capability inheritance for an individual peer or peer-group.
Examples
The following example shows how to disable additional-paths capability inheritance (from the address-
family configuration) for an IPv4 address-family peer (10.123.123.1).
device# configure terminal
device(config)# router bgp
The following example shows how to restore additional-paths capability inheritance (from the address-
family configuration) for an IPv4 peer (10.123.123.1).
device# configure terminal
device(config)# router bgp
device(config-bgp)# address-family ipv4 unicast
device(config-bgp)# no neighbor 10.123.123.1 additional-paths disable
neighbor advertisement-interval
Enables changes to the interval over which a specified neighbor or peer group holds route updates
before forwarding them.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } advertisement-
interval seconds
no neighbor { ip-address | ipv6-address | peer-group-name }
advertisement-interval
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
seconds
Range is from 0 through 3600. The default is 0.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores the default interval.
Examples
The following example changes the BGP4 advertisement interval from the default to 60 seconds.
The following example changes the BGP4+ advertisement interval from the default for VRF instance
"red".
neighbor allowas-in
Disables the AS_PATH check function for routes learned from a specified neighbor so that BGP does
not reject routes that contain the recipient BGP speaker's AS number.
Syntax
neighbor {ip-address | ipv6-address | peer-group-name } allowas-in
number
no neighbor allowas-in {ip-address | ipv6-address | peer-group-name }
allowas-in
Command Default
The AS_PATH check function is enabled and any route whose path contains the speaker's AS number is
rejected as a loop.
Parameters
ip-address
Specifies the IP address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
number
Specifies the number of times that the AS path of a received route may contain the recipient
BGP speaker's AS number and still be accepted. Valid values are 1 through 10.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
If the AS_PATH check function is disabled after a BGP session has been established, the neighbor
session must be cleared for this change to take effect.
Examples
The following example specifies that the AS path of a received route may contain the recipient BGP4+
speaker's AS number three times and still be accepted.
The following example specifies for VRF instance "red" that the BGP4+ AS path of a received route may
contain the recipient BGP speaker's AS number three times and still be accepted.
The following example specifies that the AS path of a received route may contain the recipient BGP
speaker's AS number three times and still be accepted in L2VPN EVPN configuration mode.
neighbor alternate-as
Adds a range of alternate autonomous system numbers (ASNs) for BGP dynamic neighbors.
Syntax
neighbor peer-group-name alternate-as { add | remove } as-range
no neighbor peer-group-name alternate-as add
Command Default
Disabled.
Parameters
add
Adds an AS to the alternate AS range.
remove
Removes an AS from the alternate AS range.
as-range
Specifies an alternate AS value. Enter an integer from 1 through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
This command is supported only on devices based on the DNX chipset family. For a list of such devices,
see "Supported Hardware".
For dynamic neighbors, the remote AS in the peer-group configuration allows the configuration of an
alternate AS range, a range under which the EBGP peer can fall under for the listen range that includes
the peer group.
When the device receives an OPEN message from a peer, it checks whether this AS number falls under
the range configured for the peer group. Then it accepts and makes the session IBGP or BGP peer.
Examples
The following example sets an alternate AS of 100 for listen range neighbors in a peer group called
“mypeergroup”.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# neighbor mypeergroup remote-as 400
device(config-bgp-router)# neighbor mypeergroup alternate-as add 100
The following example sets an alternate AS range of 200 through 300 for listen range neighbors in a
peer group called “mypeergroup”.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# neighbor mypeergroup remote-as 400
device(config-bgp-router)# neighbor mypeergroup alternate-as add 200-300
The following example removes the configured alternate AS number 100 for listen range neighbors in a
peer group called “mypeergroup”.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# neighbor mypeergroup alternate-as remove 100
neighbor announce-rpki-state
This command enables the SLX device to announce the RPKI state to its iBGP neighbors also to receive
the RPKI state with prefixes from the configured neighbor. The state is announced to the iBGP neighbor
through the extended community attribute. RPKI state is only announced to the iBGP neighbor when
neighbor send-community is enabled using the extended, all, or both settings for the command.
Syntax
neighbor <neighbor-address> announce-rpki-state
[no] neighbor <neighbor-address> announce-rpki-state
Parameters
<neighbor-address>
IPv4 or IPv6 address of the iBGP neighbor based on address family mode.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
By default, RPKI states with prefixes are not shared with the iBGP neighbors. Even if the iBGP neighbor
share prefixes with RPKI states, it is not considered. Sharing of RPKI states with iBGP neighbors must be
explicitly enabled.
RPKI state will be announced to the iBGP neighbor only when neighbor send-community is
enabled using the extended, all, or both settings for the command. If this command is not enabled in the
appropriate context, a warning message to enable neighbor send-community with extended
parameter.
The [no] format of this command stops the device from sending and receiving the RPKI state with
prefixes to iBGP neighbors.
The default state is RPKI state with prefixes are not shared with iBGP neighbors.
Examples
The following example shows the steps to enable sharing of RPKI state and prefix with iBGP neighbor
with IPv4 address of 10.10.11.1.
This command enters in to the router bgp mode and then enters into the IPv4 unicast address family
configuration mode.
SLX(config)#router bgp
SLX(config-bgp-router)# address-family IPv4 unicast
This command enables the ability to send extended community information to iBGP peers.
SLX(config-bgp-ipv4u)# neighbor 10.10.11.1 send-community extended
SLX(config-bgp-ipv4u)#
This command enables announcing and receiving RPKI states and prefixes with the configured iBGP
peer.
SLX(config-bgp-ipv4u)# neighbor 10.10.11.1 announce-rpki-state
neighbor as-override
Replaces the autonomous system number (ASN) of the originating device with the ASN of the sending
BGP device.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } as-override
no neighbor { ip-address | ipv6-address | peer-group-name } as-override
Command Default
This feature is disabled.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of this command to disable this feature.
BGP loop prevention verifies the ASN in the AS path. If the receiving router sees its own ASN in the AS
path of the received BGP packet, the packet is dropped. The receiving router assumes that the packet
originated from its own AS and has reached the place of origination. This can be a significant problem if
the same ASN is used among various sites, preventing sites with identical ASNs from being linked by
another ASN. In this case, routing updates are dropped when another site receives them.
Examples
This example replaces the ASN globally.
This example replaces the BGP4+ ASN for VRF instance "red".
neighbor bfd
Enables Bidirectional Forwarding Detection (BFD) sessions for specified Border Gateway Protocol
(BGP) neighbors or peer groups.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } bfd [ holdover-
interval time | interval transmit-time min-rx receive-time multiplier
number ]
no neighbor { ip-address | ipv6-address | peer-group-name } bfd
[ holdover-interval time | interval transmit-time min-rx receive-time
multiplier number ]
Command Default
BFD sessions are not enabled on specific BGP neighbors or peer groups.
Parameters
ip-address
Specifies the IP address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
holdover-interval time
Specifies the holdover interval, in seconds, for which BFD session down notifications are delayed
before notification that a BFD session is down. Valid values range from 1 through 30.
interval transmit-time
Specifies the interval, in milliseconds, a device waits to send a control packet to BFD peers. Valid
values range from 50 through 30000.
min-rx receive-time
Specifies the interval, in milliseconds, a device waits to receive a control packet from BFD peers.
Valid values range from 50 through 30000.
multiplier number
Specifies the number of consecutive BFD control packets that must be missed from a BFD peer
before BFD determines that the connection to that peer is not operational. Valid values range
from 3 through 50.
Modes
BGP configuration mode
Usage Guidelines
Before using the holdover-interval, interval, min-rx, and multiplier parameters, you
must first enable BFD using the neighbor {ip-address | ipv6-address | peer-group-
name } bfd command.
For single-hop BFD sessions, BFD considers the interval values that are configured on the interface, but
not the nondefault values that are configured with this global command.
The no form of the command removes the BFD for BGP configuration for BGP neighbors or peer
groups.
Examples
The following example configures BFD for a specified peer group and sets the BFD holdover interval to
18.
The following example configures BFD for a BGP neighbor with the IP address 10.10.1.1 and sets the BFD
session timer values.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } capability as4
[ disable | enable ]
no neighbor { ip-address | ipv6-address | peer-group-name } capability
as4 [ disable | enable ]
Command Default
4-byte ASNs are disabled by default.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor .
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
disable
Disables 4-byte numbering.
enable
Enables 4-byte numbering.
Modes
BGP configuration mode
Usage Guidelines
Use the disable keyword or the no form of this command to remove all neighbor capability for 4-
byte ASNs.
4-byte ASNs are first considered at the neighbor, then at the peer group, and finally at the global level.
Examples
This example enables 4-byte ASNs for a specified neighbor.
Syntax
neighbor { ip_address | ipv6_address | peer-group-name } capability orf
prefixlist [ receive | send ]
no neighbor { ip_address | ipv6_address | peer-group-name } capability
orf prefixlist [ receive | send ]
Command Default
ORF capabilities are not advertised to a peer device.
Parameters
ip_address
Specifies the IPv4 address of the neighbor.
ipv6_address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
receive
Enables the ORF prefix list capability in receive mode.
send
Enables the ORF prefix list capability in send mode.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of this command to disable ORF capabilities.
Examples
This example advertises the ORF send capability to a neighbor with the IP address 10.11.12.13.
This example advertises the ORF receive capability to a neighbor with the IPv6 address
2001:2018:8192::125 for VRF instance "red".
neighbor default-originate
Configures the device to send the default route 0.0.0.0 to a neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } default-
originate
no neighbor { ip-address | ipv6-address | peer-group-name } default-
originate
Command Default
Disabled.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the defaults.
Examples
The following example sends the default route to the BGP4 neighbor 10.11.12.13.
neighbor description
Specifies a name for a neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } description
string
no neighbor { ip-address | ipv6-address | peer-group-name } description
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
description string
Specifies the name of the neighbor, an alphanumeric string up to 220 characters long.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes the name.
Examples
The following example specifies a BGP4 neighbor name.
The following example specifies a BGP4+ neighbor name for VRF instance "red".
neighbor ebgp-btsh
Enables BGP time to live (TTL) security hack protection (BTSH) for eBGP.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } ebgp-btsh
no neighbor { ip-address | ipv6-address | peer-group-name } ebgp-btsh
Command Default
Disabled.
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
Modes
BGP configuration mode
Usage Guidelines
To maximize the effectiveness of this feature, the neighbor ebgp-btsh command should be
executed on each participating device. The neighbor ebgp-btsh command is supported for both
directly connected peering sessions and multihop eBGP peering sessions. For directly connected
neighbors, when the neighbor ebgp-btsh command is used, the device expects BGP control
packets received from the neighbor to have a TTL value of either 254 or 255. For multihop peers, when
the neighbor ebgp-btsh command is used, the device expects the TTL for BGP control packets
received from the neighbor to be greater than or equal to 255 minus the configured number of hops to
the neighbor.
Examples
The following example enables GTSM between a device and a neighbor with the IP address 10.10.10.1.
The following example enables GTSM between a device and a neighbor with the IPv6 address
2001:2018:8192::125.
neighbor ebgp-multihop
Allows eBGP neighbors that are not on directly connected networks and sets an optional maximum hop
count.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } ebgp-multihop
[ max-hop-count ]
no neighbor { ip-address | ipv6-address | peer-group-name } ebgp-multihop
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
max-hop-count
Maximum hop count. Range is from 1 through 255.
Modes
BGP configuration mode
Examples
The following example enables eBGP multihop and sets the maximum hop count to 20.
The following example enables BGP4+ eBGP multihop for VRF instance "red" and sets the maximum
hop count to 40.
neighbor enable-peer-as-check
Enables the outbound AS_PATH check function so that a BGP sender speaker does not send routes
with an AS path that contains the ASN of the receiving speaker.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } enable-peer-as-
check
no neighbor { ip-address | ipv6-address | peer-group-name } enable-peer-
as-check
Command Default
Disabled.
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
When the neighbor enable-peer-as-check command is used for a BGP address family, a
neighbor reset is required.
Examples
The following example enables the outbound AS_PATH check function for the L2VPN EVPN unicast
address family.
neighbor encapsulation
Sets the encapsulation type for an IPv4 neighbor, an IPv6 neighbor, or a peer group.
Syntax
neighbor { IPv4-address | IPv6-address | peer-group-name } { vxlan }
no neighbor { IPv4-address | IPv6-address | peer-group-name } {vxlan }
Command Default
None ( SLX 9150 and SLX 9250 devices)
Parameters
IPv4-address
Specifies an IPv4 address.
IPv6-address
Specifies an IPv6 address.
peer-group-name
Specifies a peer group.
vxlan
Specifies VXLAN encapsulation.
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following example configures VXLAN encapsulation for an IPv4 neighbor.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family l2vpn evpn
device(config-bgp-evpn)# neighbor 10.1.1.1 encapsulation vxlan
neighbor enforce-first-as
Ensures that a device requires the first ASN listed in the AS_SEQUENCE field of an AS path-update
message from EBGP neighbors to be the ASN of the neighbor that sent the update.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } enforce-first-as
[ disable | enable ]
no neighbor { ip-address | ipv6-address | peer-group-name } enforce-
first-as [ disable | enable ]
Command Default
Disabled by default.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
disable
Disables this feature.
enable
Enables this feature.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of this command to disable this requirement globally for the device.
Examples
This example enables the enforce-first-as feature for a specified neighbor.
This example enables the enforce-first-as feature for a BGP4+ specified neighbor for VRF instance "red".
neighbor filter-list
Specifies a filter list to be applied to updates from or to the specified neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } filter-list ip-
prefix-list-name { in | out }
no neighbor { ip-address | ipv6-address | peer-group-name } filter-list
ip-prefix-list-name { in | out }
Command Default
No filter list is applied.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
ip-prefix-list-name
Name of the filter list. The name must be between 1 and 63 ASCII characters in length.
in
Specifies that the list is applied on updates received from the neighbor.
out
Specifies that the list is applied on updates sent to the neighbor.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of the command to restore the defaults.
Examples
This example specifies that filter list “myfilterlist” be applied to updates to a neighbor with the IP
address 10.11.12.13 for the default VRF.
This example specifies that filter list “2” be applied to updates from a neighbor with the IPv6 address
2001:2018:8192::125 for the default VRF.
This example specifies that filter list “2” be applied to updates from a neighbor with the IPv6 address
2001:2018:8192::125 for VRF instance "red".
Syntax
neighbor { ip-address | peer-group } flowspec redirectholder { nrli |
extended-community } type { 0x0800 | 0x080c }
no neighbor { ip-address | peer-group } flowspec redirecttype { 0x0800 |
0x080c } holder { nrli | extended-community }
Command Default
By default, BGP flowspec redirect nexthop holder is set to nrli and the action type is set to 0x080c.
Parameters
ip-address
IP address in IPv4 format.
peer-group
Name of a peer group.
holder
Specifies where the IP address of redirect nexthop is encoded in the BGP update packet.
nrli
Specifies encoding as Network Layer Reachability Information (NRLI) in the BGP update packet.
extended-community
Specifies encoding as extended-community information in the BGP update packet.
type
Specifies the extended-community type for the redirect IP nexthop action.
0x0800
Specifies an extended-community type of 0x0800 .
0x080c
Specifies an extended-community type of 0x080c .
Modes
BGP address-family IPv4 flowspec configuration mode
Usage Guidelines
Settings configured by using the neighbor flowspec redirect command only apply to locally-
generated BGP flowspec routes; they are not applied to the advertisement of remote routes.
Examples
The following example shows how to specify encoding the nexthop IP address as nrli in the BGP
update packet and configure the BGP flowspec redirect nexthop action type as x0800.
Syntax
neighbor { ip-address | peer-group } flowspec validation [ redirect ]
no neighbor { ip-address | peer-group } flowspec validation [ redirect ]
Command Default
By default, flowspec validation is enabled at neighbor or peer-group level.
Parameters
ip-address
IP address in IPv4 format.
peer-group
Name of a peer group.
redirect
Specifies the validation of only the redirect IP nexthop address.
Modes
BGP address-family IPv4 flowspec configuration mode
Usage Guidelines
Flowspec validation can be configured at neighbor, peer-group or address-family level with the
neighbor-level configuration prioritized over peer-group level configuration and the peer-group level
configuration prioritized over the address-level configuration.
Use the neighbor flowspec validation command to configure flowspec validation at neighbor
or peer-group level. To configure flowspec validation at address-family level, refer to the flowspec
validation command.
By default, flowspec validation is enabled. Use the no form of the command to completely disable
flowspec validation at neighbor or peer-group level. To only disable redirect IP nexthop validation at
neighbor or peer-group level, use the no form of the command specifying the redirect option.
Only one flowspec validation configuration is allowed at a time. Configuration operates as follows:
• When complete flowspec validation is already disabled at neighbor or peer-group level, issuing the
no neighbor flowspec validation command specifying the redirect option has no
impact; complete flowspec validation remains disabled.
• When the redirect option is already disabled, issuing the no neighbor flowspec
validation command without the redirect option changes the configuration to complete
flowspec validation disabled at neighbor or peer-group level.
Examples
The following example shows how to disable IPv4 flowspec validation. In this example, only redirect IP
nexthop validation is disabled for a peer group named peer-group1 in the default VRF.
neighbor graceful-restart
Enables BGP graceful restart of individual BGP neighbors.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } graceful-
restart
no neighbor { ip-address | ipv6-address | peer-group-name } graceful-
restart disable
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies a peer group.
graceful-restart
Enables the graceful restart of BGP neighbor.
disable
Disables graceful-restart when it is enabled.
Modes
Global level graceful-restart configuration is avilable under inside <term> address family configuration
mode and neighbour level graceful configuration is avialble under router bgp configuration mode.
Usage Guidelines
The disable parameter of this command must be used. The graceful restart disable
command must be used to disable graceful restart. The 'no' form of the command will not disable
graceful restart.
Examples
The following example configures graceful restart of BGP session with a neighbor with the IPv6 address
2001:2018:8192::125.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# neighbor 2001:2018:8192::125 graceful-restart
The following example removes graceful-restart configuration for a BGP session with a neighbor with
the IP address 10.1.1.1 in L2VPN EVPN configuration mode.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# neighbor 10.1.1.1 graceful-restart disable
neighbor graceful-shutdown
Configures graceful shutdown of a link to a BGP neighbor or peer group.
Syntax
neighbor [ ipv4-address | ipv6-address | peer-group-name ] graceful-
shutdown seconds { community value [ local-preference value ] |
local-preference value } [ route-map route-map-name ]
no neighbor [ ip-address | ipv6-address | peer-group-name ] graceful-
shutdown seconds { community value [ local-preference value ] |
local-preference value } [ route-map route-map-name ]
Command Default
BGP graceful shutdown is disabled.
Parameters
ipv4-address
Specifies a neighbor in IPv4 address format.
ipv6-address
Specifies a neighbor in IPv6 address format.
peer-group-name
Specifies a neighbor as a peer group name (that is configured by using the neighbor peer-
group-name command).
graceful-shutdown seconds
Specifies the number of seconds to elapse before graceful shutdown occurs. The range is from
30 through 600.
community value
Specifies the community attribute for BGP graceful shutdown. The range is from 1 through
4294967295.
local-preference value
Specifies the local preference attribute for BGP graceful shutdown. The range is from 0 through
4294967295.
route-map route-map-name
Specifies the route map to apply for BGP graceful shutdown.
Modes
BGP configuration mode
Usage Guidelines
Note
neighbor send-community configuration enables sending community attribute
information to a BGP peer. Before the graceful shutdown community attribute can be sent,
the send community must be negotiated by using the neighbor send-community
command specifying the both option.
When a neighbor address is not specified, this command configures graceful shutdown for all neighbors
on the device.
This command s supported only on devices based on the DNX chipset family. For a list of such devices,
see "Supported Hardware."
When a route map is not specified, the default GRACEFUL_SHUTDOWN parameters are applied.
Note
Modifications made to the specified route map during the graceful-shutdown period, which is
specified using the graceful-shutdown parameter, are not effective for graceful
shutdown advertisement routes.
The no form of the command removes the specified BGP graceful shutdown configuration.
Examples
The following example shows how to configure BGP graceful shutdown for a neighbor (10.11.22.23) and
set the shutdown to occur after 580 seconds.
The following example shows how to configure BGP graceful shutdown for a peer group named grp-1
and set the shutdown to occur after 620 seconds.
The following example shows how to configure BGP graceful shutdown for a neighbor (10.11.22.23) and
apply the attributes of a route map named myroutemap to the shutdown which is set to occur after
600 seconds.
The following example shows how to configure BGP graceful shutdown for a neighbor (10.11.22.23) with
community attribute 20. The shutdown which is set to occur after 600 seconds.
neighbor local-as
Causes the device to prepend the local autonomous system number (ASN) automatically to routes
received from an eBGP peer.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } local-as num
[ no-prepend ]
no neighbor { ip-address | ipv6-address | peer-group-name } local-as num
[ no-prepend ]
Command Default
This feature is disabled.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
num
Local ASN. Range is from 1 through 4294967295.
no-prepend
Causes the device to stop prepending the selected ASN.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of this command to remove the local ASN.
Examples
This example ensures that a device prepends the local ASN.
This example stops the device from prepending the selected ASN.
neighbor maxas-limit in
Causes the device to discard routes received in UPDATE messages if those routes exceed a maximum
AS path length.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } maxas-limit in
{ num | disable }
no neighbor { ip-address | ipv6-address | peer-group-name } maxas-limit
in
Command Default
This command is disabled by default.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
num
Maximum length of the AS path. Range is from 0 through 300. The default is 300.
disable
Prevents a neighbor from inheriting the configuration from the peer group or global
configuration and instead uses the default system value.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of this command to remove this configuration.
Examples
This example changes the length of the maximum allowed AS path length from the default.
This example prevents a neighbor from inheriting the configuration from the peer group or global
configuration and instead use the default system value.
neighbor maximum-prefix
Specifies the maximum number of IP network prefixes (routes) that can be learned from a specified
neighbor or peer group.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } maximum-prefix
num [ threshold ] [ teardown ] [ restart-interval restart-interval-
in-minutes ]
no neighbor { ip-address | ipv6-address | peer-group-name } maximum-
prefix num [ threshold ] [ teardown ] [ restart-interval ]
Command Default
This feature is disabled.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor.
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
num
Maximum number of IP prefixes that can be learned. Range is from 0 through 2147483647.
Default is 0 (unlimited).
threshold
Specifies the percentage of the value specified by num (IP prefixes) that causes a syslog
message to be generated. Range is from 1 through 100.
teardown
Tears down the neighbor session if the maximum number of IP prefixes is exceeded.
restart-interval restart-interval-in-minutes
After a session is tore down, this value controls the duration after which the session is restarted.
Range is 1-65535 minutes.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the defaults.
When a neighbor session is torn down due to maximum-prefix value being exceeded, The maximum
number of prefixes that can be learned from a specific neighbor or from a peer-group is specified in the
maximum-prefix configuration. The teardown parameter for this command indicates that the neighbor
session will be brought down when the number of learned prefixes exceeds the value configured in the
maximum-prefix configuration.
When a session is brought down due to the above reason, it has to be manually restored using either of
the clear ip bgp neighbor all or the clear ip bgp neighbor commands.
Examples
The following example sets the maximum number of prefixes that will be accepted from the neighbor
with the IP address 10.11.12.13 to 100000, and sets the threshold value to 80%.
The following example, for VRF instance "red," sets the maximum number of prefixes that will be
accepted from the neighbor with the IPv6 address 2001:2018:8192::125 to 100000, and sets the
threshold value to 90%.
The following example sets the maximum number of prefixes that will be accepted from the neighbor
with the IP address 10.1.2.3 to 100000 in L2VPN EVPN configuration mode.
The following example extends the previous example to configure a threshold value to generate a
RASLOG entry. The threshold value is set at 80% of the configured prefixes.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family l2vpn evpn
device(config-bgp-evpn)# neighbor 10.1.2.3 maximum-prefix 100000 80
The following example sets the maximum number of prefixes that will be accepted from the neighbor
with the IP address 10.1.2.3 to 100000 in L2VPN EVPN configuration mode. It also configures a threshold
for generating a RASLOG entry. The example command then configures a restart interval to restart the
session after 7 minutes when the interface is shut down due to maximum prefixes being exceeded.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family l2vpn evpn
device(config-bgp-evpn)# neighbor 10.1.2.3 maximum-prefix 100000 80 restart-interval 7
neighbor next-hop-self
Causes the device to list itself as the next hop in updates that are sent to the specified neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } next-hop-self
[ always ]
no neighbor { ip-address | ipv6-address | peer-group-name } next-hop-self
[ always ]
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies the peer group name configured by the neighbor peer-group-name command.
always
Enables this feature for route reflector (RR) routes.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command disables this feature.
Examples
The following example causes all updates destined for the neighbor with the IP address 10.11.12.13 to
advertise this device as the next hop.
The following example, for the VRF instance "red," causes all updates destined for the neighbor with the
IPv6 address 2001:2018:8192::125 to advertise this device as the next hop.
neighbor next-hop-unchanged
Enables BGP to send updates to eBGP peers with the next-hop attribute unchanged.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } next-hop-
unchanged
no neighbor { ip-address | ipv6-address | peer-group-name } next-hop-
unchanged
Command Default
This functionality is not enabled.
Parameters
ip-address
Specifies an IPv4 address.
ipv6-address
Specifies an IPv6 address.
peer-group-name
Specifies a peer group.
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
By default, BGP speakers change the next hop while sending the updates to eBGP neighbors. Use this
command to override this behavior. When this command is used, the next hop attribute remains
unchanged while updates are sent to eBGP peers, and the BGP speaker is forced to retain the next hop
address in the BGP updates received from neighbors.
The no form of the command disables the sending of updates to eBGP peers with the next-hop
attribute unchanged.
Examples
The following example disables the sending of updates to eBGP peers with the next-hop attribute
unchanged.
neighbor password
Specifies an MD5 password for securing sessions between the device and a neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } password string
no neighbor { ip-address | ipv6-address | peer-group-name } password
Command Default
No password is set.
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group-name
Specifies the peer group name configured by the neighbor peer-group-name command.
password string
Password of up to 63 characters in length that can contain any alphanumeric character. MD5
passwords cannot have ASCII character 32 ('SPACE') as a part of the password string.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes a configured MD5 password.
Examples
The following example specifies a password for securing sessions with a specified neighbor.
The following BGP4+ example, for VRF instance "red," specifies a password for securing sessions with a
specified neighbor.
neighbor peer-dampening
Enables peer-dampening for a single neighbor.
Syntax
neighbor { x.x.x.x | A:B::C:D } peer-dampening [ delay-hold 0-65535 |
penalty 1-65535 | max-penalty 1-65535 | stability-interval 0-65535 ]
no neighbor { x.x.x.x | A:B::C:D } peer-dampening [ delay-hold | penalty
| max-penalty | stability-interval ]
Parameters
{ x.x.x.x | A:B::C:D }
The IP address of the neighbor device in IPv4 or IPv6 format.
delay-hold 0-65535
The amount of time, in seconds, that a session remains in the idle-state after the first peer flap
event is received. During this time, all route advertisements from this peer are ignored. The
default value is zero (0) seconds.
penalty 1-65535
The amount of time, in seconds, which gets added to idle-hold timer every time a peer flap event
is received. The default value is 300 seconds.
max-penalty 1-65535
The maximum amount of time, in seconds, that a session remains in the idle- state after it has
experienced repeated instability. The default value is 3600 seconds.
stability-interval 0-65535
The interval of time, in seconds, the session must be error-free in order to consider it to be
stable. The default value is 1800 seconds.
Modes
Router BGP
Usage Guidelines
• BGP peer dampening can be global or on individual neighbor/peer-group.
• All routes from a dampened peer will be removed from the routing table
• When route dampening is also configured, peer dampening will take precedence over route
dampening.
• Dampening cannot be applied to dynamic peers.
• Dampening cannot be applied to administratively down neighbors.
• When downgrading to a firmware that does not support peer-dampening, an error will be displayed.
You must remove this configuration to successfully complete the downgrade.
Examples
The following example shows how to enable Peer Dampening feature for a single neighbor.
SLX (config)# router bgp
SLX (config-bgp-router)# neighbor 10.9.9.10 peer-dampening delay-hold 10 penalty 300 max-
penalty 3600 stability-interval 1800
SLX (config-bgp-router)#
Syntax
neighbor peer-group peer-dampening [ delay-hold 0-65535 | penalty
1-65535 | max-penalty 1-65535 | stability-interval 0-65535 ]
no neighbor peer-dampening (peer-group) [ delay-hold | penalty | max-
penalty | stability-interval ]
Parameters
peer-group
The name of the peer-group to which this configuration must be applied to.
delay-hold 0-65535
The amount of time, in seconds, that a session remains in the idle-state after the first peer flap
event is received. During this time, all route advertisements from this peer are ignored. The
default value is zero (0) seconds.
penalty 1-65535
The amount of time, in seconds, which gets added to idle-hold timer every time a peer flap event
is received. The default value is 300 seconds.
max-penalty 1-65535
The maximum amount of time, in seconds, that a session remains in the idle- state after it has
experienced repeated instability. The default value is 3600 seconds.
stability-interval 0-65535
The interval of time, in seconds, the session must be error-free in order to consider it to be
stable. The default value is 1800 seconds.
Modes
Router BGP
Usage Guidelines
• BGP peer dampening can be global or on individual neighbor/peer-group.
• All routes from a dampened peer will be removed from the routing table
• When route dampening is also configured, peer dampening will take precedence over route
dampening.
• Dampening cannot be applied to dynamic peers.
• Dampening cannot be applied to administratively down neighbors.
• When downgrading to a firmware that does not support peer-dampening, an error will be displayed.
You must remove this configuration to successfully complete the downgrade.
Examples
The following example shows how to enable Peer Dampening for a peer-group.
SLX (config)# router bgp
SLX (config-bgp-router)# neighbor 50.0.0.1 peer-group pg-level-1
SLX (config-bgp-router)# neighbor pg-level-1 peer-dampening delay-hold 10 penalty 300 max-
penalty 3600 stability-interval 1800
SLX (config-bgp-router)#
neighbor peer-group
Configures a BGP neighbor to be a member of a peer group.
Syntax
neighbor { ip-address | ipv6-address } peer-group string
no neighbor { ip-address | ipv6-address } peer-group string
Parameters
ip-address
Specifies the IPv4 address of the neighbor.
ipv6-address
Specifies the IPv6 address of the neighbor.
peer-group string
Specifies the name of a BGP peer group. The name can be up to 63 characters in length and can
be composed of any alphanumeric character.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes a neighbor from the peer group.
Examples
The following example assigns a specified neighbor to a peer group called “mypeergroup1”.
The following BGP4+ example, for VRF instance "red," assigns a specified neighbor to a peer group
called "mypeergroup1".
Syntax
neighbor peer-group-name alternate-as-range {add | remove as-range } [as-
range ]
no neighbor peer-group-name alternate-as-range
Command Default
By default, AS neighbors are not added to the BGP neighbor table
Parameters
add | remove
Specifies whether to add or remove the indicated AS number or range.
as-range
Specifies the AS number or range of AS numbers to add to the BGP neighbor table. Separate
multiple entries with a comma. Separate contiguous ranges with a hyphen. For example: 100,
200-300.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of the command to reset the default functionality.
Examples
This example adds an AS number and a range of AS numbers.
device# configure terminal
device(cofig)# neighbor peer-group-name alternate-as-range add 100,200-300
neighbor prefix-list
Filters the outgoing and incoming route updates to or from a particular BGP neighbor according to IP
address and mask length.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } prefix-list
string { in | out }
no neighbor { ip-address | ipv6-address | peer-group-name } prefix-list
string { in | out }
Command Default
This feature is disabled.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
string
Name of the prefix list. Range is from 1 through 63 ASCII characters.
in
Applies the filter in incoming routes.
out
Applies the filter in outgoing routes.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of the command to restore the defaults.
Examples
This example applies the prefix list "myprefixlist" to incoming advertisements to neighbor 10.11.12.13 for
the default VRF.
This example applies the prefix list "myprefixlist" to outgoing advertisements to neighbor
2001:2018:8192::125 for the default VRF.
This example applies the prefix list "myprefixlist" to outgoing advertisements to neighbor
2001:2018:8192::125 for VRF instance "red," .
neighbor remote-as
Specifies the autonomous system (AS) in which a remote neighbor resides.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } remote-as num
no neighbor { ip-address | ipv6-address | peer-group-name } remote-as
Command Default
No AS is specified.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
num
Remote AS number (ASN). Range is from 1 through 4294967295.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command removes the neighbor from the AS.
Examples
The following example specifies AS 100 for a neighbor.
The following BGP4+ example, for VRF instance "red," specifies AS 100 for a neighbor.
neighbor remove-private-as
Configures a device to remove private autonomous system numbers (ASNs) from UPDATE messages
that the device sends to a neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } remove-private-
as
no neighbor { ip-address | ipv6-address | peer-group-name } remove-
private-as
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
Modes
BGP configuration mode
Usage Guidelines
The device will remove ASNs 64512 through 65535 (the well-known BGP4 private ASNs) from the AS-
path attribute in UPDATE messages that the device sends to a neighbor.
The no form of the command restores the default so that private ASNs are not removed from UPDATE
messages sent to a neighbor by a device.
Examples
The following example removes private ASNs globally.
The following example removes private ASNs for VRF instance "red".
neighbor route-map
Filters the outgoing and incoming route updates to or from a particular BGP neighbor according to a set
of attributes defined in a route map.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } route-map { in
string | out string }
no neighbor { ip-address | ipv6-address | peer-group-name } route-map
{ in string | out string }
Command Default
This feature is disabled.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
in
Applies the filter on incoming routes.
string
Name of the route map. Range is from 1 through 63 ASCII characters.
out
Applies the filter on outgoing routes.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the defaults.
Examples
The following example applies a route map named "myroutemap" to an outgoing route from 10.11.12.13.
The following example applies a route map named "myroutemap" to an incoming route from
2001:2018:8192::125.
The following example applies a route map named "myroutemap" to an outgoing route from 10.11.12.13 in
L2VPN EVPN configuration mode.
neighbor route-reflector-client
Configures a neighbor as a route-reflector client.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } route-reflector-
client
no neighbor { ip-address | ipv6-address | peer-group-name } route-
reflector-client
Parameters
ip-address
Specifies the IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Specifies the peer group name configured by the neighbor peer-group-name command.
Modes
BGP configuration mode
Usage Guidelines
Use this command on a host device to configure a neighbor to be a route-reflector client. The host
device from which the configuration is made becomes a route-reflector server.
Examples
The following example configures an IPv4 neighbor as a route-reflector client.
device# configure terminal
device(config)# router bgp
device(config-bgp)# address-family ipv4 unicast
device(config-bgp-ipv4u)# neighbor 10.11.12.13 route-reflector-client
The following example configures an IPv6 neighbor to be a route-reflector client for VRF instance "red".
neighbor send-community
Enables sending the community attribute in updates to the specified BGP neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } send-community
[ all | both | extended | large | standard ]
no neighbor { ip-address | ipv6-address | peer-group-name } send-
community [ all | both | extended | large | standard ]
Command Default
The device does not send community attributes.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
all
Sends all community attributes: extended, large, and standard. BGP address-family L2VPN EVPN
configuration mode does not support this keyword.
both
Sends both standard and extended attributes.
extended
Sends extended attributes.
large
Sends BGP large community attributes. BGP address-family L2VPN EVPN configuration mode
does not support this keyword.
standard
Sends standard attributes.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
If the send-community attribute is enabled after a BGP session has been established, the neighbor
session must be cleared for this change to take effect.
Examples
The following example sends standard community attributes to a neighbor.
The following example sends extended community attributes to a neighbor for VRF instance "red".
The following example sends standard and extended community attributes to a neighbor in L2VPN
EVPN configuration mode.
neighbor shutdown
Causes a device to shut down the session administratively with its BGP neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } shutdown
[ generate-rib-out ]
no neighbor { ip-address | ipv6-address | peer-group-name } shutdown
[ generate-rib-out ]
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
generate-rib-out
When a peer is put into the shutdown state, Routing Information Base (RIB) outbound routes are
not produced for that peer. Use this option to produce those routes.
Modes
BGP configuration mode
Usage Guidelines
Shutting down a session lets you configure the neighbor and save the configuration without the need to
establish a session with that neighbor.
Examples
The following example causes a device to shut down the session administratively with its neighbor.
The following example causes a device to shut down the session administratively with its neighbor and
generate RIB outbound routes for VRF instance "red".
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } soft-
reconfiguration inbound
no neighbor { ip-address | ipv6-address | peer-group-name } soft-
reconfiguration inbound
Parameters
ip-address
Specifies the IPv4 address of the neighbor
ipv6-address
Specifies the IPv6 address of the neighbor
peer-group-name
Specifies the peer group name.
Modes
BGP configuration mode
Usage Guidelines
Soft reconfiguration stores all the route updates received from a neighbor. If you request a soft reset of
inbound routes, the software compares the policies against the stored route updates, instead of
requesting the neighbor’s BGP4 or BGP4+ route table or resetting the session with the neighbor.
Examples
The following example globally stores route updates from a BGP4 neighbor.
The following example stores route updates from a BGP4+ neighbor for VRF instance "red".
neighbor static-network-edge
Overrides the default BGP4 behavior and advertises the network to a neighbor or peer group only when
the corresponding route is installed as a forward route in the routing table.
Syntax
neighbor { ip-address | peer-group-name } static-network-edge
no neighbor { ip-address | peer-group-name } static-network-edge
Parameters
ip-address
Specifies the IPv4 address of the neighbor
peer-group-name
Specifies the peer group name configured by the neighbor peer-group-name command.
Modes
BGP configuration mode
Usage Guidelines
A BGP static network is always advertised to neighbors or a peer group, and if the corresponding route
is not present in the routing table, BGP installs the null0 route. This command overrides the default
behavior. This command is not supported for BGP4+.
Examples
The following example globally overrides the default BGP4 behavior.
The following example overrides the default BGP4 behavior for VRF instance "red".
neighbor timers
Specifies how frequently a device sends KEEPALIVE messages to its BGP neighbors, as well as how
long the device waits for KEEPALIVE or UPDATE messages before concluding that a neighbor is dead.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } timers keep-
alive keepalive_interval hold-time holdtime_interval
no neighbor { ip-address | ipv6-address | peer-group-name } timers keep-
alive keepalive_interval hold-time holdtime_interval
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
keep-alive keepalive_interval
Frequency (in seconds) with which a device sends keepalive messages to a peer. Range is from 0
through 65535 seconds. The default is 60.
hold-time holdtime_interval
Interval in seconds that a device waits to receive a keepalive message from a peer before
declaring that peer dead. Range is from 0 through 65535 seconds. The default is 180.
Modes
BGP configuration mode
Usage Guidelines
The no form of the command restores the defaults.
Examples
The following example sets the keepalive timer for a device to 120 seconds and the hold-timer to 360
seconds.
The following example sets the keepalive timer to 120 seconds and the hold-timer to 360 seconds for
VRF instance "red".
neighbor unsuppress-map
Removes route suppression from BGP neighbor routes when those routes have been suppressed as a
result of aggregation. All routes matching route-map rules are unsuppressed.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } unsuppress-map
string
no neighbor { ip-address | ipv6-address | peer-group-name } unsuppress-
map string
Command Default
This feature is disabled.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
string
Name of the route map. Range is from 1 through 63 ASCII characters.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of the command to restore the defaults.
Examples
The following BGP4 example removes route suppression for the default VRF.
The following BGP4+ example removes route suppression for VRF instance "red".
neighbor update-source
Configures the BGP device to communicate with a neighbor through a specified interface.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } update-source
{ ip-address | ethernet slot / port | loopback num| ve-interface
vlan_id }
no neighbor { ip-address | ipv6-address | peer-group-name } update-source
{ ip-address | ethernet slot / port | loopback num| ve-interface
vlan_id }
Command Default
Disabled.
Parameters
ip-address
IPv4 address of the neighbor
ipv6-address
IPv6 address of the neighbor
peer-group-name
Peer group name configured by the neighbor peer-group-name command.
ip-address
IP address of the update source.
ethernet
Specifies an ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
loopback num
Specifies a loopback interface.
ve-interface vlan_id
Specifies a virtual Ethernet VLAN interface.
Modes
BGP configuration mode
Usage Guidelines
Use the no form of the command to restore the defaults.
Examples
The following example configures the device to communicate with a neighbor through the specified
IPv4 address and Ethernet interface 3/2.
device#configure terminal
device#(config)# router bgp
device(config-bgp-router)# neighbor 10.11.12.13 update-source ethernet 3/2
neighbor weight
Specifies a weight that the device will add to routes that are received from the specified BGP neighbor.
Syntax
neighbor { ip-address | ipv6-address | peer-group-name } weight num
no neighbor { ip-address | ipv6-address | peer-group-name } weight
Command Default
The default for num is 0.
Parameters
ip-address
IPv4 address of the neighbor.
ipv6-address
IPv6 address of the neighbor
peer-group-name
Name of the peer group.
num
Value from 1 through 65535.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of the command to restore the defaults.
Examples
This example changes the weight from the default.
This example changes the weight from the default for VRF instance "red".
net
Configures an Intermediate System-to-Intermediate System (IS-IS) network entity title (NET) for the
routing process.
Syntax
net NSAP address
no net NSAP address
Command Default
900 seconds (15 minutes).
Parameters
NSAP address
Specifies a Network Service Access Point (NSAP) address; composed of both an area ID and a
system ID.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The area-id parameter specifies the area and has the format xx or xx.xxxx. For example, 49 and
49.2211 are valid area IDs.
The system-id parameter specifies the device’s unique IS-IS router ID and has the format
xxxx.xxxx.xxxx. You can specify any value for the system ID. A common practice is to use the base MAC
address of the device as the system ID. The base MAC address is also the MAC address of port 1.
You must use the same system ID in all the NETs on the device.
Examples
The following example configures a NET that has the area ID 49.2211, the system ID 0000.00bb.cccc
(the base MAC address), and the SEL value 00.
device# configure terminal
device(config)# router isis
device(config-isis-router)# net 49.2211.0000.00bb.cccc.00
network
Configures the device to advertise a BGP network.
Syntax
network network/mask [ backdoor | route-map map-name | weight num ]
no network network/mask [ backdoor | route-map map-name | weight num ]
Command Default
No network is advertised.
Parameters
network/mask
Network and mask in CIDR notation.
backdoor
Changes administrative distance of the route to this network from the eBGP administrative
distance (the default is 20) to the local BGP weight (the default is 200), tagging the route as a
backdoor route.
route-map map-name
Specifies a route map with which to set or change BGP attributes for the network to be
advertised. Range is from 1 through 63 ASCII characters.
weightnum
Specifies a weight to be added to routes to this network. Range is 0 through 65535. The default
is 0.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of the command to restore the defaults.
Examples
This example imports the IP prefix 10.1.1.1/32 into the BGP4 database and specifies a route map called
“myroutemap”.
This example imports the IPv6 prefix 2001:db8::/32 into the BGP4+ database and sets a weight of 300.
next-hop-enable-default
Configures the device to use the BGP default route as the next hop.
Syntax
next-hop-enable-default
no next-hop-enable-default
Command Default
This feature is disabled.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
The no form of the command restores the default.
Examples
The following BGP4 example configures the device to use the default route as the next hop for the
default VRF.
The following BGP4+ example configures the device to use the default route as the next hop for the
default VRF.
next-hop-mpls
Configures BGP shortcuts using next-hop MPLS to force BGP to use an MPLS tunnel as the preferred
route to a destination network when an MPLS LSP tunnel is available.
Syntax
next-hop-mpls [ compare-lsp-metric | follow-igp ]
no next-hop-mpls [ compare-lsp-metric | follow-igp ]
Command Default
BGP uses the default BGP decision process and native IP forwarding to build BGP EMCP routes. Only IP
routing tables are used to resolve routes for the routing table.
Parameters
compare-lsp-metric
Enables BGP to compare the configured LSP metrics as the IGP cost for the next hop.
follow-igp
Ignores the MPLS metric cost in the BGP decision process and uses the IGP cost. BGP checks
when an MPLS LSP is present, and totally ignores the LSP metric.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
When the next-hop-mpls command is enabled without either option, BGP sets the LSP metrics to
one.
Enabling or disabling an option takes effect immediately. BGP automatically recalculates the existing
BGP routes.
When the compare-lsp-metric option is configured and you change the LSP metric, the routing
table is updated.
When you use the no form of the command with the compare-lsp-metric or follow-igp
option, all LSP metrics become equal cost. However, global next-hop MPLS remains enabled.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables BGP shortcuts through next-hop MPLS and BGP to set the next hop IGP
cost to one instead of the actual LSP metric.
The following example enables BGP shortcuts through next-hop MPLS and BGP to use the configured
LSP metrics as the IGP cost for the next hop.
The following example enables BGP shortcuts through next-hop MPLS and BGP to ignore the LSP
metrics and to use the IGP cost for the next hop.
next-hop-recursion
Enables BGP recursive next-hop lookups.
Syntax
next-hop-recursion
no next-hop-recursion
Command Default
This feature is disabled.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
If the BGP next hop is not the immediate next hop, a recursive route lookup in the IP routing information
base (RIB) is needed. With recursion, a second routing lookup is required to resolve the exit path for
destination traffic. Use this command to enable recursive next-hop lookups.
Examples
This example enables recursive next-hop lookups for BGP4.
no debug
Disables the debug process for the selected module or all modules.
Syntax
no debug { all | arp | bfd | dhcp | dot1x | endpoint-tracking | icmp | ip
| ipv6 | lacp | link-oam | lldp | mpls | sflow | spanning-tree | udld
| vrrp}
Parameters
all
Disables the debug on all modules for which it is enabled.
arp
Disables the Address Resolution Protocol packet debug.
bfd
Disables the Bidirectional Forwarding Detection debug.
dhcp
Disables the Dynamic Host Configuration Protocol packet debug.
dot1x
Disables the IEEE 802.1x port-based access control debug.
endpoint-tracking
Disables the endpoint tracking debug.
icmp
Disables the Internet Control Message Protocol packet debug.
ip
Disables the IPv4 packet debug.
ipv6
Disables the IPv6 packet debug.
lacp
Disables the Link Aggregation Control Protocol debug.
link-oam
Disables the link OAM debug.
lldp
Disables the Link Layer Discovery Protocol debug.
mpls
Disables the Multiprotocol Label Switching debug.
sflow
Disables sFlow (sampled flow) debug.
spanning-tree
Disables the Spanning-Tree Protocol debug.
udld
Disables the Unidirectional Link Detection debug.
vrrp
Disables the VRRP debug.
Modes
Privileged EXEC mode
Examples
This example disables the debug for VRRP.
no debug vrrp
node
Penalizes all links originating from the node IP address.
Syntax
node ip_addr
no node ip_addr
Command Default
The command is disabled by default.
Parameters
ip_addr
All links that originate from the specified IP address are penilized.
Modes
MPLS CSPF-group configuration mode.
Usage Guidelines
The no form of the command disables the configuration.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The example below configures a fate sharing group and specifies node 10.1.1.1 as the penalizing IP
address.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# cspf-group computation-mode add-penalty
device(config-router-mpls-policy)# exit
device(config-router-mpls)# cspf-group group3
device(config-router-mpls-cspf-group-group3)# penalty 100
device(config-router-mpls-cspf-group-group3)# from 10.1.1.1
device(config-router-mpls-cspf-group-group3)# link 10.1.1.1 10.1.1.2
device(config-router-mpls-cspf-group-group3)# subnet 10.1.2.0/24
device(config-router-mpls-cspf-group-group3)# node 10.1.1.1
non-revertive-mode
Sets non-revertive mode for Ethernet Ring Protection (ERP).
Syntax
non-revertive-mode
no non-revertive-mode
Command Default
Non-revertive mode is not set by default.
Modes
ERP configuration mode
Usage Guidelines
After the Ethernet Ring enters a protected state, if you do not want the topology to return to the
original state (even after the failure has cleared) you can use the non-revertive-mode command.
Run this command on the RPL owner only, and then run the enable command.
This command is allowed only on the RPL-owner node. An error message is issued if it is executed on
another node.
Examples
The following example configures non-revertive mode and enables the configuration.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# non-revertive-mode
device(config-erp-1)# enable
nonstop-routing (IS-IS)
Enables nonstop routing (NSR) for Intermediate System-to-Intermediate System (IS-IS).
Syntax
nonstop-routing
no nonstop-routing
Command Default
Enabled
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables NSR for IS-IS on a device.
device# configure terminal
device(config)# router isis
device(config-isis-router)# nonstop-routing
nonstop-routing (OSPF)
Enables nonstop routing (NSR) for OSPF.
Syntax
nonstop-routing
no nonstop-routing
Command Default
Enabled.
Modes
OSPF router configuration mode
Usage Guidelines
The no form of the command disables non-stop routing.
Examples
The following example re-enables NSR on a device.
notification-timer
Sets the length of the EOL notification timer for LDP-IGP synchronization.
Syntax
notification-timer milliseconds
no notification-timer milliseconds
Command Default
The default value is 60000 milliseconds.
Parameters
milliseconds
Specifies the length of the EOL notification timer in milliseconds. Enter an integer from 100 to
120000.
Modes
MPLS LDP end-of-lib (eol) configuration mode
Usage Guidelines
Use the no form of the command to reset the default value.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the EOL notification timer to 80000 milliseconds.
device(config)# router mpls
device(config-mpls)# ldp
device(config-mpls-ldp)# end-of-lib
device(config-mpls-ldp-eol)# notification-timer 80000
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# eol
device(config-router-mpls-ldp-eol)# notification-timer 80000
ntp authenticate
This command enables or disables the NTP authentication at global level. If the authentication is
enabled, the NTP packets from servers, peers, clients not having MAC is dropped. Only those servers/
peers configured with key authentication is considered for time synchronization. Client requests only
with authentication is served, whose key-IDs match with one of the trusted key-IDs.
Syntax
ntp authenticate
no ntp authenticate
Command Default
By default the authentication is disabled.
Modes
Global configuration mode
Usage Guidelines
The no form of ntp authenticate disables the NTP authentication.
Examples
device(config)# ntp authenticate
ntp authentication-key
Creates an authentication key to associate with the NTP server, thereby enabling NTP authentication.
Syntax
ntp authentication-key key-id {md5 | sha1 }key-string
no ntp authentication-key key-id
Command Default
By default the authentication keys are not configured.
Parameters
key-id
Specifies an ID for an authentication key. The range is from 1 through 65534.
md5
The MD5 encryption.
sha1
The SHA1 encryption.
key-string
Specifies a key string. The string can be a maximum of 15 ASCII characters.
Modes
Global configuration mode
Usage Guidelines
This command adds an NTP authentication key to a list of authentication keys in the database. The key
is shared by the client (device) and an external NTP server.
The maximum number of configurable NTP authentication keys is five. You cannot configure a duplicate
key ID with a different key string. Use the no ntp authentication-key key-id command to
remove the specified authentication key.
Authentication key must be created before associating the key with any server. Refer to the ntp
server command for information on how to create this association.
Before downgrading the firmware to a version that does not support the encryption-level option, the
encryption-level should be set to 0.
Examples
To create an authentication key with an ID of 33, an MD5 string called check, and an encryption level of
0:
device# configure
device(config)# ntp authentication-key 33 md5 check encryption-level 0
ntp disable
Disables the NTP server/client mode. Disabling the NTP server/client mode does not remove the
configuration.
Syntax
ntp disable { ntp disable} [ serve]
no ntp disableserve
Command Default
By default, the NTP is enabled.
Parameters
serve
If this keyword is specified, then NTP will not serve the time to downstream devices. This
keyword disables the NTP server mode functionalities.If this keyword is not specified, then both
NTP client mode and NTP server mode functionalities will be disabled.
Modes
Global configuration mode
Examples
Use no to disable NTP server and client mode.
Disable NTP server and client mode:
device(config)# ntp disable
Disable NTP client mode:
device(config)# ntp disable serve
ntp peer
Configures the NTP peers and specifies the peers to synchronize the system clock. A maximum of 8
NTP peers can be configured.
Syntax
ntp peer {ip_address } [ key key_id ] [ maxpoll interval ] [ minpoll
interval] [ use-vrfvrf_name] [ version 3 | 4]
no ntp peer{ip_address }
Command Default
No default peers are configured.
Parameters
ip_address
Specifies the IPv4 or IPv6 address of the NTP peer.
key key_id
Specifies the symmetric key ID. By default, no symmetric key is configured. The range is 1 to
65,534.
maxpoll interval
Specifies the longest polling interval. The range is 4 to 17. Default is 10. The interval argument is
power of 2, for example: 3=8s, 4=16s, 5=32s, 6=64s, 7=128s, 8=256s, 9=512s.
minpoll interval
Specifies the shortest polling interval. The range is 4 to 17. The default is 6. The interval argument
is power of 2, for example: 3=8s, 4=16s, 5=32s, 6=64s, 7=128s, 8=256s, 9=512s.
use-vrfvrf_name
Specifies the VRF name to synchronize the time with server. The default is mgmt-vrf.
version 3 | 4
Specifies the NTP version supported by the peer. The default is 4.
Modes
Global configuration mode
Usage Guidelines
This command is not effective if the NTP is enabled in client-only mode. If the peer is already mobilized
as symmetric passive, then configuring statically will not be effective.
The no form of the command removes the peer configuration and applied options.
Examples
Configures the NTP peers and specify the peers to synchronize the system clock.
device(config)# ntp peer 1.2.3.4
device(config-peer-1.2.3.4/mgmt-vrf)# key 1 maxpoll 9 minpoll 7 version 3
The following error message is displayed when the minimum poll value is greater than maximum poll
value: Minimum poll interval cannot be greater than maximum poll interval.
ntp server
Specifies or adds an NTP server IP address and optionally associates an authentication key to the server.
Syntax
ntp server {ip_address } [ source-interface-type {ethernet source-
interface-number | loopback source-interface-number | management
source-interface-number| ve source-interface-number }][ key key_id ]
[ maxpoll interval ] [ minpoll interval] [ use-vrf vrf_name]
[ version 3 | 4 ]
no ntp server {ip_address }
Command Default
No default peer is configured.
Parameters
ip_address
Specifies the IPv4 or IPv6 address of the NTP peer.
source-interface-type
Specifies the type of interface.
ethernet
Specifies an Ethernet interface as the source type.
loopback
Specifies a loopback interface as the source type.
management
Specifies a management interface as the source type.
ve
Specifies a VE as the source type.
source-interface-number
Specifies the interface number. Valid values range from 1 through 4096.
key key_id
Specifies the symmetric key ID. By default, no symmetric key is configured. The range is 1 to
65,534.
maxpoll interval
Specifies the longest polling interval. The range is 4 to 17. Default is 10. The interval argument is
power of 2, for example: 3=8s, 4=16s, 5=32s, 6=64s, 7=128s, 8=256s, 9=512s.
minpoll interval
Specifies the shortest polling interval. The range is 4 to 17. The default is 6. The interval argument
is power of 2, for example: 3=8s, 4=16s, 5=32s, 6=64s, 7=128s, 8=256s, 9=512s.
use-vrfvrf_name
Specifies the VRF name to synchronize the time with server. The default is mgmt-vrf.
version 3 | 4
Specifies the NTP version supported by the peer. The default is 4.
Modes
Global configuration mode
Usage Guidelines
Use this command to add an NTP server IPv4 or IPv6 address to a list of server IP addresses, or to
associate an existing authentication key with an NTP server IP address.
Network Time Protocol (NTP) commands must be configured on each individual switch.
Use the no ntp server ip-address command to remove the specified NTP server IP address.
Removing the current active NTP server resets the NTPstatus to "LOCL" until a new, active server is
selected.
Use the no ntp server ip-address key key-id command to remove the key from the specified
NTP IP address.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default
VRF ("default-vrf").
Examples
This example associates a configured key ID of 15 to an NTP server on the management VRF.
device(config)# ntp peer 1.2.3.4
device(config-server-1.2.3.4/mgmt-vrf)# key 15
ntp trusted-key
This command configures additional subset of trusted key-IDs which can be used for NTP and client
authentication. The keys configured for server/peer is implicitly considered as part of trusted keys.
Syntax
ntp trusted-key [key-id-1 key-id-2key-id-n]
no ntp trusted-key
Command Default
By default the trusted key-IDs are not configured.
Parameters
key-id-1key-id-2key-id-n
List of authentication keys.
Modes
Global configuration mode
Usage Guidelines
A key must be configured as an authentication key before you can use it as a trusted key.
The no form of the command clears a configured key-ID from the trusted key list.
Examples
This command configures an additional subset of trusted key-IDs.
device(config)# ntp trusted-key 1 5 15
device(config)# no ntp trusted-key 15
operational-state
Enables or disables support for OpenConfig Telemetry Support for SLX.
Syntax
operational-state syncup enable { all | interface | bgp | platform }
Parameters
all
Indicates that OpenConfig Telemetry support must be enabled on all supported modules.
interface
Indicates that OpenConfig Telemetry Support is only to be enabled for the Interface module.
bgp
Indicates that OpenConfig Telemetry Support is only to be enabled for the BGP module.
platform
Indicates that OpenConfig Telemetry Support is only to be enabled for the Platform module.
Modes
Configuration Mode
Usage Guidelines
Examples
The following command lists the options available for the command.
SLX (config)#
The following example enables OpenConfig Telemetry Support for the BGP module.
optimized replication
Enables optimized replication.
Syntax
optimized replication
no optimized replication
Modes
Global configuration mode
Usage Guidelines
no optimized-replication removes the entire mode and disables all underlay groups.
The default mdt group needs to be configured first and removed last in the optimized-replication mode.
When all vlans are removed from a group and the group config is removed. The same rule applies to
BDs as well.
Examples
overlay-gateway 10
type layer2-extension
optimized-replication
underlay-mdt-default-group 239.0.0.100 ! default MDT for all VNIs
underlay-mdt-group 239.0.0.1 vlan add 10-12,20 ! shared MDT; but not the default
underlay-mdt-group 239.0.0.3 vlan add 30 ! MDT dedicated to vlan 30
underlay-mdt-group 239.0.0.4 vlan add 40
underlay-mdt-group 239.0.0.5 bridge-domain add 50,60-70
oscmd
Runs commands or scripts supported by the Linux OS directly from the SLX-OS CLI.
Syntax
oscmd { Linux-command | script-name }
Parameters
Linux-command
Specifies the Linux command that you want to run.
script-name
Specifies the script that you want to run.
Modes
Privileged EXEC mode
Usage Guidelines
This command is only available for users with admin-level permissions.
After writing and testing a user-defined script file, you can copy it to the SLX-OS device. Imported
scripts are stored in the /var/config/vcs/scripts directory.
You can also create scripts from the Linux shell using the "vi" editor. The newly-created scripts must
exist in the /fabos/users/admin directory.
Although as an SLX-OS admin you have permissions to run the following commands from the Linux
shell, you do not have permissions to run them—from the SLX-OS CLI—appended to the oscmd
command.
• bash
• script
• vi
• vim
Examples
In the following example, the Linux ps -ef command lists the process status from the CLI.
device# oscmd ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Jul24 ? 00:00:04 /sbin/init
root 2 0 0 Jul24 ? 00:00:00 [kthreadd]
root 3 2 0 Jul24 ? 00:00:00 [migration/0]
root 4 2 0 Jul24 ? 00:00:03 [ksoftirqd/0]
...
In the following example, "my_script" is the name of a user-defined script that is downloaded by using
the copy command or exists in the /fabos/users/admin directory; and is executable under the
Linux OS .
device# oscmd my_script
overlay access-group
Applies an overlay ACL to an overlay-transit node.
Syntax
overlay access-group overlay-acl-name in
no overlay access-group overlay-acl-name in
Parameters
overlay-acl-name
Specifies the name of the overlay ACL.
in
Applies the ACL to incoming traffic.
Modes
Overlay-transit mode
Usage Guidelines
Overlay ACLs are not supported for SLX 9150 or SLX 9250 devices.
To remove an overlay ACL from an overlay-transit node, use the no form of this command.
Examples
The following example applies an overlay ACL to an overlay-transit node.
device# configure terminal
device(config)# overlay-transit tr_name
device(config-overlay-transit-tr_name)# overlay access-group ov_trans_acl_01 in
Syntax
overlay access-list type vxlan extended acl-name
no overlay access-list type vxlan extended acl-name
Command Default
No overlay VXLAN extended ACL is defined.
Parameters
acl-name
Specifies the overlay ACL name.
Modes
Global configuration mode
Usage Guidelines
Overlay ACLs are not supported for SLX 9150 or SLX 9250 devices.
Extended ACLs enable you to configure VXLAN tunnel endpoints (VTEP source and destination IP), VNI
and VNI IP range, inner source and destination IP and networks, and inner source and destination ports.
To delete an overlay VXLAN extended ACL, use the no form of this command .
Examples
The following example creates an overlay VXLAN extended ACL and then defines a permit rule.
device# configure terminal
device(config)# overlay access-list type vxlan extended ovr_vxl_ext
device(conf-overlayacl-ext-vxlan)# seq 10 permit dst-vtep-ip any src-vtep-ip 20.1.1.100
vni 50 native tag none dst-ip 100.1.1.1 src-ip any dst-port 5555 src-port 6666 count
mirror ethernet 1/4
Syntax
overlay access-list type vxlan standard acl-name
no overlay access-list type vxlan standard acl-name
Command Default
No overlay VXLAN standard ACL is defined.
Parameters
acl-name
Specifies the overlay ACL name.
Modes
Global configuration mode
Usage Guidelines
Overlay ACLs are not supported for SLX 9150 or SLX 9250 devices.
Enables configuring only the VXLAN tunnel endpoint (VTEP) IP address and VXLAN Network Identifier
(VNI) to match.
To delete an overlay VXLAN standard ACL, use the no form of this command .
Examples
The following example creates an overlay VXLAN standard ACL and then defines a permit rule.
device# configure terminal
device(config)# overlay access-list type vxlan standard ovr_vxl_std_01
device(conf-overlayacl-std-vxlan)# seq 10 permit dst-vtep-ip 10.1.1.100 src-vtep-ip
10.1.1.100 vni 5 count sflow
overlay-gateway
Creates a VXLAN overlay gateway instance and enables VXLAN overlay gateway configuration mode.
Syntax
overlay-gateway name
no overlay-gateway name
Parameters
name
Specifies a name for the VXLAN overlay gateway. Only one gateway instance can be configured.
The name is an alphanumeric, 32-character-maximum string that can also contain hyphens and
underscores.
Modes
Global configuration mode
Usage Guidelines
Use this command to create a VXLAN overlay gateway instance with the given name. An overlay
network is a virtual network that is built on top of existing network Layer 2 and Layer 3 technologies.
Setting up a gateway consists of the following:
• Configuring the source IP address
• Configuring the VLAN or bridge domain
• Mapping a bridge domain to a VNI
• Configuring MAC addresses to export to the VXLAN domain
• Enabling statistics collection for VLAN domains
• Enabling SPAN
One you create the gateway instance, you enter VXLAN overlay gateway configuration mode, where
you can configure other properties for this gateway. The key commands available in this mode are
summarized below:
Table 13: Key commands available in VXLAN overlay gateway configuration mode
Command Description
activate Activates a VXLAN overlay gateway instance.
ip interface loopback Sets the loopback port number for the overlay gateway instance.
map bridge-domain In a VXLAN overlay gateway configuration that uses the Layer 2
extension, maps a bridge domain with VXLAN Network Identifiers
(VNIs).
map vlan In a VXLAN overlay gateway configuration that uses Layer 2 extension,
associates VLANs with VXLAN Network Identifiers (VNIs).
sflow Enables sFlow monitoring of the tunnel endpoints for a VXLAN overlay
gateway.
site Configures a remote Layer 2 extension site in a VXLAN overlay gateway
context.
type layer2-extension Specifies that a VXLAN overlay gateway uses Layer 2 extension.
Use the no overlay-gateway command to delete the VXLAN overlay gateway instance from the
cluster. All tunnels for the gateway are also deleted. There are no other no forms of this command.
By default, a VXLAN overlay gateway instance is inactive. To activate an instance, first configure its
other properties (such as which devices it attaches to), and then enter the activate command.
Examples
The following example creates a VXLAN overlay gateway instance named gateway1 and accesses
VXLAN overlay gateway configuration mode.
device# configure terminal
device(config)# overlay-gateway gateway1
device(config-overlay-gw-gateway1)#
overlay-service-policy
Binds an overlay policy map to an overlay gateway or overlay transit instance.
Syntax
overlay-service-policy in policy-mapname
no overlay-service-policy in policy-mapname
Command Default
No overlay policy map is bound.
Parameters
in
Specifies that the policy be applied on ingress traffic (required).
policy-mapname
Name of an overlay policer policy map.
Modes
Overlay gateway instance configuration mode
Usage Guidelines
This command is not supported for SLX 9150 or SLX 9250 devices.
Examples
The following example binds a policy map to an overlay gateway instance.
device# configure terminal
device(config)# overlay-gateway gw1
device(conf-overlay-gw-gw1)# overlay-service-policy in servicepolicy1
The following example binds a policy map to an overlay transit instance on a spine node.
device# configure terminal
device(config)# overlay-transit transit1
device(conf-overlay-transit-transit1)# overlay-service-policy in servicepolicy1
The following example unbinds the policy map from the above instance.
device# configure terminal
device(config)# overlay-transit myOTinstance
device(conf-overlay-transit-transit1)# no overlay-service-policy in servicepolicy1
overlay-transit
Configures an overlay transit.
Syntax
overlay-transit overlay-transit-name
no overlay-transit overlay-transit-name
Parameters
overlay-transit-name
Specifies the overlay transit name.
Modes
Global configuration mode
Usage Guidelines
This command is not supported for SLX 9150 or SLX 9250 devices.
Use the no form of this command to delete the overlay transit configuration.
Examples
The following example configures an overlay transit.
device# configure terminal
device(config)# overlay-transit vlx_transit
partial-spf-interval
Changes the partial shortest path first (PSPF) interval.
Syntax
partial-spf-interval max-wait initial-wait second-wait
no partial-spf-interval
Parameters
max-wait
Specifies the maximum interval in seconds between SPF recalculations. The range is from 0
through 120 seconds. The default is 5 seconds.
initial-wait
Specifies the initial SPF calculation delay in milliseconds after an LSP change. The range is from
0 through 120000 milliseconds. The default for this variable is value of the max-wait time.
second-wait
Indicates the hold time between the first and second SPF calculation in milliseconds. The range is
from 1 through 120000 milliseconds. The default is 5000 milliseconds (5 seconds). The default
for this variable is value of the max-wait time.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example specifies that the maximum interval between SPF recalculations is 15 seconds,
the initial SPF calculation delay is 10000 milliseconds, and the hold time between the first and second
SPF calculation is 15000 milliseconds.
device# configure terminal
device(config)# router isis
device(config-isis-router)# partial-spf-interval 15 10000 15000
password-attributes
Configures global password attributes.
Syntax
password-attributes { [ max-logins maxlogins ][ max-retry maxretry ]
[ min-length minlen ] [ max-logins maxlogin][ history number] [repeat
minnum ] [ sequence number] [ login-notify-duration hours] [ admin-
lockout | character-restriction { [ lower numlower ] [ numeric
numdigits ] [ special-char numsplchars ] [ upper numupper ] [ force-
default-password-change ][ max-password-age number-of-days ] }
no password-attributes { [ max-logins maxlogins ][ max-retry maxretry ]
[ min-length minlen ] [ max-logins maxlogin][ history number] [repeat
minnum ] [ sequence number] [ login-notify-duration hours] [ admin-
lockout | character-restriction { [ lower numlower ] [ numeric
numdigits ] [ special-char numsplchars ] [ upper numupper ] } ]
[ force-default-password-change ][ max-password-age number-of-
days ] }
Command Default
The default for min-length is 8. All other defaults are 0.
Parameters
admin-lockout
Enables lockout for admin role accounts.
character-restriction
Configures the restriction on various types of characters.
lower numlower
Specifies the minimum number of lowercase alphabetic characters that must occur in the
password. Values range from 0 through 32 characters. The default value is 0.
numeric numdigits
Specifies the minimum number of numeric characters that must occur in the password. Values
range from 0 through 32 characters. The default is 0.
special-char numsplchars
Specifies the number of punctuation characters that must occur in the password. All printable,
non-alphanumeric punctuation characters, except colon (:) are allowed. Values range from 0
through 32 characters. The default value is 0.
upper numupper
Specifies the minimum number of uppercase alphabetic characters that must occur in the
password. Values range from 0 through 32 characters. The default value is 0.
max-logins maxlogins
Specifies the maximum number of log-in sessions for a user. Values range from 0 through 10. The
default value is 0.
max-retry maxretry
Specifies the number of failed password log-ins permitted before a user is locked out. Values
range from 0 through 16. The default value is 0.
min-length minlen
Specifies the minimum length of the password. Valid values range from 8 through 32 characters.
The default is 8 characters.
max-logins maxlogin
Specifies the maximum number of log-in sessions allowed per local user. Valid values range from
0 through 10. The default is 0, representing an infinite number of log-ins.
history number
Specifies the number of old passwords against which a newly configured password is checked.
The new password is discarded if it matches an old password. Valid values range from 0 through
10. The default is 0.
repeat minimum
Specifies the minimum number of consecutive repetitive characters in a newly configured
password. The new password is discarded if it has consecutive repetitive characters (for
example, aaa, xxx,1111). Configure 1 for disabling. The default is 1.
sequence number
Specifies the minimum number of consecutive sequential characters both in forward and reverse
direction (for example, abc, cba) in a newly configured password. The new password is discarded
if it has consecutive sequential characters (for example, abc, xyz, fedc). Configure 1 for disabling.
The default is 1.
login-notify-duration hours
Specifies the duration in hours for which admin is notified of the number of last successful
attempts. Use value 0 to disable the notification. Valid values range from is from 0 through 120.
The default is 0.
force-default-password-change
Force the user to change password at first login. This is applicable to all default accounts on the
system.
max-password-age number-of-days
Specifies the number of days after which the user is forced to change the password. The default
value is zero (0) indicating that the password does not expire and need not be changed.
Modes
Global configuration mode
Usage Guidelines
To reset password attributes to their default values, run the no form of this command.
If you use PuTTY to open a telnet session and then close the session by closing the PuTTY window, the
max-logins feature does not count the session as closed because the client does not send an
application layer closure message to be processed by the PAM module. Therefore, if max-logins is
enabled when you use PuTTY to open a telnet session, use the exit command to close the session.
The max-logins feature does not apply to REST log-ins and RESTCONF log-ins.
Examples
The following example configures global password attributes and verifies the configuration.
device#configure terminal
device(config)# password-attributes max-retry 4
device(config)# password-attributes character-restriction lower 2
device(config)# password-attributes character-restriction upper 1 numeric 1 special-char
1
device(config)# exit
device# show running-config password-attributes
password-attributes max-retry 4
password-attributes character-restriction upper 1
password-attributes character-restriction lower 2
password-attributes character-restriction numeric 1
password-attributes character-restriction special-char 1
The following example resets the character restriction attributes and verifies the configuration.
device#configure terminal
device(config)# no password-attributes character-restriction lower
device(config)# no password-attributes character-restriction upper
device(config)# exit
device# show running-config password-attributes
password-attributes max-retry 4
password-attributes character-restriction numeric 1
password-attributes character-restriction special-char 1
% No entries found.
The following example sets the maximum number of retries to 3 and enables lockout policy for admin
role accounts.
device#configure terminal
device(config)# password-attributes max-retry 3 admin-lockout
The following example shows the configuration to force a user to change their login password the first
time they login in.
Enable forcing default password change:
SLX(config)# password-attributes force-default-password-change
password-attributes force-default-password-change
SLX#
The following example displays how the user can set the maximum number of days for the user account
password. After the maximum no. of days have reached, the user should change the password. The
default value is 0 which means, the password expiration is disabled.
Configure Maximum password age parameter:
SLX(config)# password-attributes max-password-age 4
password-encryption convert-enc-to-level-10
Changes existing AES-256 encrypted passwords and MD5 passwords to SHA-512 .
Syntax
password-encryption convert-enc-to-level-10
Command Default
By default, passwords from previous releases have the encryption with which they were configured.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to convert all existing passwords to make them more secure in SLX-OS 20.1.1 or later.
Any clear-text (enc-level 0) passwords are retained in the configuration database and not converted to
SHA-512.
If you downgrade to a release earlier than SLX-OS 20.1.1, all MD5 passwords that were converted to
SHA-512 will not be available.
Examples
The following example shows the warning and the prompt before passwords are converted.
device# password-encryption convert-enc-to-level-10
%WARN: This operation will convert all existing user passwords to SHA-512 format.
However, the enc level 0 (clear-text) passwords, if any, will be retained as is
in the configuration database. These configurations will be lost if the system is
downgraded to lower releases than SLX 20.1.1.
Do you want to continue? [y/n]y
All passwords are converted successfully.
The following example shows the warning when a configuration rollback is in progress.
device# password-encryption convert-enc-to-level-10
%WARN:This operation will convert all existing user passwords to SHA-512 format.
However, the enc level 0 (clear-text) passwords, if any, will be retained as is
in the configuration database. These configurations will be lost if the system is
downgraded to lower releases than SLX 20.1.1.
Do you want to continue? [Y/N]y
%%ERROR: Password conversion is not allowed when configuration rollback session
is in progress; Please try again later.
path
A path is a list of router hops that specifies a route across an MPLS domain. Once the user creates a
path, the user can create signaled LSPs that see the path.
Syntax
path path_name [ hop ip_addr ] | [ [ insert ip_addr ] [ [ loose |
strict ] ip_addr ]
no path { path_name } [ hop ip_addr ] | [ [ insert ip_addr ] [ [ loose |
strict ] ip_addr ]
Command Default
No paths are modified by default.
Parameters
path_name
Specifies the selected path name.
hop ip_addr
Configures the specified the strict or loose hop.
insert ip_addr
Specifies the inserted path strict or loose hop.
loose ip_addr
There can be other routers in between.
strict ip_addr
The router must be directly connected to the preceding node.
Modes
MPLS path mode (config-router-mpls-path-name).
Usage Guidelines
The no form of the command removes the specified path.
A path is always configured at the ingress LER and assumes that the ingress LER is the beginning of the
path. A path can contain any number of nodes, which correspond to MPLS-enabled routers in the
network.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures a path called sf_to_sj that has four nodes.
device# configure
device(config)# router mpls
device(config-router-mpls)# path sf_to_sj
device(config-router-mpls-path-sf_to_sj)# hop 2.3.4.5 strict
device(config-router-mpls-path-sf_to_sj)# hop 1.2.3.4 strict
device(config-router-mpls-path-sf_to_sj)# exit
pdu-rate
Configures pdu-rate value, which is the number of OAMPDUs per second.
Syntax
pdu-rate rate
Command Default
The default value is 1.
Parameters
rate
Specifies the pdu rate per second.
Modes
Link OAM configuration mode
Usage Guidelines
The range is from 1 through 10. Configure the timeout interval at least three times the pdu interval to
avoid Link OAM protocol flaps against loss of one or two PDUs for any latency issues.
Examples
(config-link-oam)# pdu-rate 10
peer
Configures a peer IP address in a bridge domain. A corresponding pseudowire (PW) interface is created
when the peer IP address is configured.
Syntax
peer ip-address [ control-word ] [ cos num ] [ flow-label ] [ load-
balance ] [ lsp lsp-name1, lsp-name2, . . . lsp-name32 ]
no peer [ ip-address [ lsp lsp-name1, lsp-name2, . . . lsp-name32 ] ]
Command Default
No PW interfaces are configured.
Parameters
ip-address
A PW IP address for a remote peer.
control-word
Enables control word for routing of pseudowire (PW) traffic to the peer.
cos num
Specifies a Class of Service (CoS) value for selecting a label-switched path to reach the peer. The
value ranges is from 0 through 7.
flow-label
Enables flow label to support PW load balancing.
load-balance
Specifies load balancing. As many as16 alternate paths are used for load balancing.
lsp lsp-name1, lsp-name2, . . . lsp-name32
Specifies the name of a label-switched path. As many as 32 label-switched path names can be
configured.
Modes
Bridge-domain configuration mode.
Usage Guidelines
The virtual connection identifier (VC ID) must be configured by using the vc-id command prior to
configuring the peer IP address to create a PW interface.
The no form of the command deletes the peer IP address configuration and the PW interface that
corresponds to the specified peer IP address.
Note
When a peer is already configured, you cannot add a CoS or load balancing configuration. To
configure a CoS value or load-balancing, the peer must be removed by using the no peer
command and reconfigured by specifying the required cos or load-balance options.
To remove the CoS or load-balance configuration, the peer configuration must be removed by
using the no peer command.
Examples
The following example shows how to configure a peer IP address (10.12.12.12) for bridge domain 1 with
the load-balance option.
The following example shows how to configure a peer IP address (10.12.12.12) for bridge domain 1
specifying two label-switched paths (lsp1 and lsp2).
The following example shows how to configure a peer IP address (10.1.1.1) for bridge domain 1 specifying
load balancing and four label-switched paths (lsp1, lsp2, lsp3 and lsp4).
device(config)# bridge-domain 1
device(config-bridge-domain-1)# peer 10.1.1.1 load-balance lsp lsp1 lsp2 lsp3 lsp4
The following example shows the error message that is displayed when you try to configure the load-
balance option for an existing peer. The peer configuration must be removed and reconfigured to
specify the load-balance option, as shown in the example.
peer (MCT)
Configures the IP address for the MCT cluster peer.
Syntax
peer ip-address
no peer [ ip-address ]
Parameters
ip-address
Specifies the IP address for the cluster peer. The address is either the peer loopback address or
nexthop IP address.
Modes
Cluster configuration mode.
Usage Guidelines
Configure a corresponding neighbor for the peer. If the peer is already configured as a neighbor, when
you deploy and undeploy the cluster, the neighbor resets to renegotiate its capability.
If the peer already exists for other address family, clear the IP peer session.
Examples
The following example shows the configuring of the cluster peer IP address.
device(config)# cluster MCT1
device(config-cluster-MCT1)# peer 10.10.10.12
peer-dampening
Enables dampening of unstable BGP Peers globally for all neighbors (IPv4, IPv6 across all VRFs).
Dampening can be enabled on all neighbors or on an individual neighbour/a peer-group. Dampening
cannot be applied on dynamic peers.
Syntax
peer-dampening [ delay-hold 0-65535 | penalty 1-65535 | max-penalty
1-65535 | stability-interval 0-65535 ]
no peer-dampening [ delay-hold | penalty | max-penalty | stability-
interval ]
Parameters
delay-hold 0-65535
The amount of time, in seconds, that a session remains in the idle-state after the first peer flap
event is received. During this time, all route advertisements from this peer are ignored. The
default value is zero (0) seconds.
penalty 1-65535
The amount of time, in seconds, which gets added to idle-hold timer every time a peer flap event
is received. The default value is 300 seconds.
max-penalty 1-65535
The maximum amount of time, in seconds, that a session remains in the idle- state after it has
experienced repeated instability. The default value is 3600 seconds.
stability-interval 0-65535
The interval of time, in seconds, the session must be error-free in order to consider it to be
stable. The default value is 1800 seconds.
Modes
Router BGP
Usage Guidelines
• BGP peer dampening can be global or on individual neighbor/peer-group.
• All routes from a dampened peer will be removed from the routing table
• When route dampening is also configured, peer dampening will take precedence over route
dampening.
• Dampening cannot be applied to dynamic peers.
• Dampening cannot be applied to administratively down neighbors.
• When downgrading to a firmware that does not support peer-dampening, an error will be displayed.
You must remove this configuration to successfully complete the downgrade.
Examples
The following example shows how to enable peer dampening globally.
SLX (config)#router bgp
SLX (config-bgp-router)# peer-dampening delay-hold 10 penalty 300 max-penalty 3600
stability-interval 1800
SLX (config-bgp-router)#
The following example shows how to disable Peer Dampening globally for all peers.
SLX (config)# router bgp
SLX (config-bgp-router)# no peer-dampening
SLX (config-bgp-router)#
peer-interface
Configures the Ethernet interface or port-channel to reach the MCT cluster peer.
Syntax
peer-interface Ethernet slot/port | port-channel number
no peer-interface
Parameters
Ethernet slot/port
Specifies the Ethernet interface for the cluster peer.
port-channel number
Specifies the port-channel for the cluster peer.
Modes
Cluster configuration mode.
Usage Guidelines
The no form of the command deletes the peer interface configuration.
You must configure the peer interface before deploying the cluster configuration.
You cannot change the peer interface when the cluster is deployed.
Examples
The following example shows the configuring of the cluster peer interface.
device(config)# cluster MCT1
device(config-cluster-MCT1)# peer-interface port-channel 20
peer-keepalive (optional)
Configures the keepalive session for the MCT cluster peer.
Syntax
peer-keepalive { auto } [ destination IP address |role primary/secondary]
no peer-keepalive { auto } [ destination IP address |role primary/
secondary]
Command Default
The default is auto.
Parameters
auto
Destination and source IP will be automatically discovered and should not be configured.
destination ip-address source-interface interface
Manually configures the destination and source interface. Overrides the auto discovery default.
role primary/secondary
Configures the role of the node if the ICL goes down, but MCT peer remains up.
Modes
Cluster configuration mode.
Usage Guidelines
no peer-keepalive disables keep-alive session.
The default keepalilve session uses the management VRF and runs between the management IP
addresses of the MCT nodes.
The primary node is responsible for forwarding all traffic when ICL goes down.
The Secondary node brings down all client interfaces and tunnels and isolates all client traffic.
By default, the node with lower IP is selected as primary and higher IP is selected as secondary. This
behavior can be changed by configuring the role.
Examples
The following example automatically configures the peer-keepalive default destination IP, source
interface, and primary/secondary roles.
device(config)# cluster MCT1
device(config-cluster-MCT1)# peer-keepalive
device(config-peer-keepalive)# auto
device(config-peer-keepalive)#
penalty
Sets the penalty value for a CSPF fate-sharing group.
Syntax
penalty { penalty_value }
no penalty
Command Default
The command is disabled by default.
Parameters
penalty_value
Specifies the penalty value that is assigned to objects of the same fate-sharing group. The range
is from 1 through 65535. The default value is one (1). Objects of the same fate-sharing group
share the same penalty value. For example, all objects in group 3 share the same penalty value of
100.
Modes
MPLS CSPF group mode.
Usage Guidelines
The no form of the command disables the command..
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the penalty value to 100.
device# configure
device(config)# router mpls
device(config-router-mpls)# cspf-group group3
device(config-router-mpls-cspf-group-group3)# penalty 100
permit ip host
Creates a rule in an Address Resolution Protocol (ARP) ACL that permits ARP messages from a host
specified by both IP and MAC addresses.
Syntax
permit ip host sender-ip mac host sender-mac-address
no permit ip host sender-ip mac host sender-mac-address
Command Default
No permit rules are defined.
Parameters
sender-ip
Specifies the sender IP address.
mac host sender-mac-address
Specifies the sender MAC address, in hexadecimal format.
Modes
ARP ACL configuration mode
Usage Guidelines
On untrusted interfaces of DAI-enabled VLANs, incoming ARP packets from permitted IP/MAC
addresses are accepted only if all of the following steps were performed:
• Create the ACL, using the arp access-list command.
• In the ACL, create one or more rules, using the permit ip host command. Each rule specifies an
IP/MAC address-pair.
• Apply the ACL to one or more VLANs, using the ip arp inspection filter command.
• Enable DAI on such VLANs, using the ip arp inspection command.
This command is also used to implement ARP Guard. ARP Guard is supported only on devices based on
the DNS chipset family. For a list of such devices, see "Supported Hardware".
The no form of the command removes the permit rule from the ACL.
Examples
The following example defines a permit ip host rule in an ARP ACL, applies the ACL to a VLAN,
and enables DAI on that VLAN.
device# configure terminal
device(config)# arp access-list arp_acl_1
The following example creates a permit ip host rule within the arp access-list command.
device# configure terminal
device(config)# arp access-list host2 permit ip host 1.1.1.1 mac host 0000.0011.0022
The following example creates an ARP ACL, creates permit ip host rules within, and applies it to
an interface. This is the first stage of ARP Guard implementation.
device# configure terminal
device(config)# arp access-list arp_acl_2
device(config-arp-acl)# permit ip host 1.1.1.1 mac host 0020.2222.2222
device(config-arp-acl)# permit ip host 1.1.1.2 mac host 0020.2222.2223
device(config-arp-acl)# exit
Note
At this point, ARP Guard is not yet enabled. For more information, see the "ARP Guard"
section of the Extreme SLX-OS Layer 3 Routing Configuration Guide.
ping
Verifies network connectivity between a source and a destination on a TCP/IP network.
Syntax
ping dest-ipv4-addr [ ipv6 dest-ipv6-addr ] [ host-name ] [ count
[ number ] [ interface { Ethernetslot/port| management | ve
vlan_id } ] ] [ timeout seconds ] [ datagram-size bytes ] [ quiet ]
[ numeric ] [ vrf { mgmt-vrf | default-vrf |vrf-name } }
Command Default
The default for count is 5. The default for timeout is 1. The default for datagram-size is 56.
Parameters
dest-ipv4-addr
Specifies the IPv4 address of the destination device.
ipv6 dest-ipv6-addr
Specifies the IPv6 address of the destination device.
host-name
Specifies the destination host name. The default value is 1.
count number
Specifies the number of transmissions (pings). The range is from 1 through 7200.
interface Ethernet
Represents a valid, physical Ethernet interface.
slot
Specifies a valid slot number.
port
Specifies a valid port number.
interface management
Specifies the management interface.
interface ve vlan_id
Specifies the interface is a virtual Ethernet, and specifies the VLAN ID of the interface.
timeout seconds
Specifies the time (in seconds) to wait for a response. The range is from 1 through 60. The
default value is 1.
Note
This option applies only to IPv4.
datagram-size bytes
Specifies the datagram size (also known as the maximum transmission unit, or MTU) in bytes.
The range is from 36 through 9100. The default value is 56.
quiet
Prints only the first and last line of the command output.
numeric
Does not look up host names.
vrf
Pings the specified VRF instance.
mgmt-vrf
Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf-name
Specifies a VRF name.
Modes
Privileged EXEC mode
Usage Guidelines
This command sends a specified number of pings with configured parameters to the specified
destination device.
Examples
This example pings an IPv4 destination address.
device# ping 172.16.4.80
Type Control-c to abort
PING 172.16.4.80 (172.16.4.80): 56 data bytes
64 bytes from 172.16.4.80: icmp_seq=0 ttl=120 time=101.466 ms
64 bytes from 172.16.4.80: icmp_seq=1 ttl=120 time=122.914 ms
64 bytes from 172.16.4.80: icmp_seq=2 ttl=120 time=145.637 ms
64 bytes from 172.16.4.80: icmp_seq=3 ttl=120 time=170.032 ms
64 bytes from 172.16.4.80: icmp_seq=4 ttl=120 time=103.036 ms
--- 172.16.4.80 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 101.466/128.617/170.032/26.188 ms
This example pings an IPv6 destination address in numeric mode with a datagram size.
device# ping ipv6 fec0:60:69bc:92:218:8bff:fe40:1470 count 3 datagram-size 48
numeric timeout 3
Type Control-c to abort
PING fec0:60:69bc:92:218:8bff:fe40:1470 (fec0:60:69bc:92:218:8bff:fe40:1470): 48
data bytes
56 bytes from fec0:60:69bc:92:218:8bff:fe40:1470: icmp_seq=0 ttl=64 time=6.356 ms
56 bytes from fec0:60:69bc:92:218:8bff:fe40:1470: icmp_seq=1 ttl=64 time=0.170 ms
56 bytes from fec0:60:69bc:92:218:8bff:fe40:1470: icmp_seq=2 ttl=64 time=0.171 ms
--- fec0:60:69bc:92:218:8bff:fe40:1470 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.170/2.232/6.356/2.916 ms
pki ocsp
Configures OCSP (Online Certificate Status Protocol) on a VRF with a source interface.
Syntax
pki ocsp [source-interface { ethernet eth-id | loopback loopback-id |
management mgmt-addr | ve ve-id } ]
no pki ocsp [source-interface { ethernet eth-id | loopback loopback-id |
management mgmt-addr | ve ve-id } ]
Command Default
By default, OCSP is not configured.
Parameters
source-interface
Indicates the type of interface to use as the source interface or address.
ethernet eth-id
Specifies the Ethernet interface to use as the source interface, in slot/port format (0/1).
loopback loopback-id
Specifies the Loopback interface to use as the source interface.
management mgmt-addr
Specifies the management address (active MM or chassis IP) to use as the source address.
ve ve-id
Specifies the VE interface to use as the source interface.
Modes
Global configuration mode
Usage Guidelines
Customers on different networks have their OCSP responder connected to the SLX device by the
management IP or the in-band IP (Ethernet port). Customers prefer that all network packets originating
from a specific device be traceable to a known IP address on the device from which they originate. You
can use this command to configure the source interface, where a network packet from the device is sent
to a server that listens for these packets.
When a source interface is not specified, the default source is the IP address of the interface from which
the packet egresses.
If, at run time, the source interface is not up or the IP address for the source interface was not
configured, the command behaves as though the source interface was not configured.
Examples
This example configures an Ethernet interface as the source address.
device# configure terminal
device(config)# pki ocsp 10.1.1.100
device(config-pki-ocsp-10.1.1.100/mgmt-vrf)# source-interface ethernet 0/1
police cir
Configures the committed information rate, committed burst size, exceeded information rate, and the
exceeded burst size for the class map.
Syntax
police cir cir-bps [ cbs bytes ] [ eir bps [ ebs bytes ] ]
no police cir [ cbs ] [ eir [ ebs ] ]
Parameters
cir-bps
Specifies the committed information rate in bits per second. Enter an integer from 0 to
300000000000.
cbs bytes
Specifies the committed burst size in bytes. Enter an integer from 1250 to 37500000000.
eir bps
Specifies the exceeded information rate in bits per second. Enter an integer from 0 to
300000000000.
ebs bytes
Specifies the exceeded burst size in bytes. Enter an integer from 1250 to 37500000000.
Modes
Policy-map class configuration mode
Usage Guidelines
Use the no version of this command to remove the parameter from the class map.
You can enter CIR and EIR values from 0 to 300000000000, but the operational values are from
22000 to 300000000000.
Only the police cir command is mandatory for configuring a class map.
If the optional parameters for a class map are not set, they are treated as disabled. To delete all
parameters for a class-map, use the no police command.
If CBS and EBS values are not configured, then these values are derived from the CIR and EIR values,
respectively. The burst size calculation is as follows: Burst size (CBS or EBS) = 1.2*information rate (CIR/
EIR)/8.
If the configured CBS value is less than 2*(default MTU) value, then 2*(default MTU) is programmed as
the CBS in the hardware. For example, if you configure CBS at 2000 bytes and the default MTU on an
interface is 1548 bytes, when a policy map is applied on this interface, the CBS programmed in the
hardware is 2*MTU (3096 bytes). If you update the MTU value, the CBS value is not be updated.
If the optional EIR or EBS value is not configured, it is disabled and Always Violated traffic is dropped.
To disable the learning of MAC addresses for stream matching of the ACL-based rate limiting entries,
the CIR and EIR values must be 0.
The MAC address entries in the MAC-address table which are already learned will not be flushed when
you configure the CIR or EIR value as 0. You must explicitly clear the entries in MAC-address table by
using the clear mac-address-table dynamic command.
Examples
The following example sets the committed information rate (cir), committed burst size (cbs), exceeded
information rate (eir), and the exceeded burst size (ebs).
device# configure terminal
device(config)# policy-map policy_2
device(config-policymap)# class default
device(config-policymap-class)# police cir 3000000 cbs 375000000 eir 300000000 ebs
37500000
policy-map
Configures a policy map containing a class map so that you can apply policer and QoS attributes to a
particular interface.
Syntax
policy-map policy-mapname
no policy-map policy-mapname
Command Default
No policy map is created.
Parameters
policy-mapname
Name of police policy map
Modes
Global configuration mode
Usage Guidelines
When you launch the policy-map command, the system is placed in config-policymap mode
for the configured map. At this point, you can add a class map containing policing parameters to the
policy map. (Refer to the description of the class command.)
This command creates a policer policy map to apply policer and QoS attributes to a particular interface.
Each policy map can contain up to 32 class maps. The class map can be associated with specific
policing and QoS parameters.
Associate the policy map to the interface for inbound or outbound direction with the service-
policy command.
Enter no policy-map policy-mapname while in global configuration mode to remove the policy
map.
Examples
Create a policy map and place system into config-policymap mode so that you can add a class map.
port-channel path-cost
Sets the port channel path cost behavior.
Syntax
port-channel path-cost [ custom | standard ]
Command Default
Path cost is standard.
Parameters
custom
Specifies to use the custom behavior, which sets the path cost changes according to the port-
channel’s bandwidth.
standard
Specifies to use the standard behavior, which sets that the path cost does not change according
to port-channel’s bandwidth.
Modes
Spanning tree configuration mode
Examples
To set the behavior for the path cost to custom:
preempt-mode
Enables or disables preempt mode for a VRRP or VRRP Extended (VRRP-E) router session.
Syntax
preempt-mode
no preempt-mode
Command Default
Enabled for VRRP; Disabled for VRRP-E.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This command is for VRRP and VRRP-E.
When set, the highest-priority backup router will always be the master if the owner is not available. If
not set, a higher priority backup will not preempt a lower-priority master.
Examples
To turn on preempt mode for a virtual-router-group 1 session:
device# configure terminal
device(config)# ipv6 protocol vrrp-extended
device(config)# interface ve 10
device(config-if-Ve-10)# ipv6 vrrp-extended-group 1
device(config-vrrp-extended-group-1)# preempt-mode
prefix-independent-convergence
Configures BGP Prefix-Independent Convergence (PIC), providing a BGP next-hop and additional paths
to the routing information base manager (RIBM) and forwarding information base (FIB) if applicable.
Syntax
prefix-independent-convergence
no prefix-independent-convergence
Command Default
This feature is disabled by default.
Modes
Global configuration mode
Usage Guidelines
Use the show running-config command to confirm the configuration. Backup paths are not
displayed in the output.
After enabling and disabling BGP PIC, use the clear ip bgp neighbor command to clear the
configuration.
Examples
The following example configures BGP PIC.
device# configure terminal
device(config)# prefix-independent-convergence
primary-path
Configures an explicit path for the bypass LSP or dynamic bypass LSP.
Syntax
primary-path { path_name }
no primary-path { path_name }
Command Default
By default, there is no configuration of the primary path.
Parameters
path_name
Specifies the name of the configured path in the MPS router.
Modes
MPLS router bypass LSP configuration mode (config-router-mpls-bypass-lsp-bypass_name).
Usage Guidelines
The path must be already defined in MPLS router.
The user can configure an explicit path for dynamic bypass LSPs that are created for a protected
interface.
The no form of this command removes the path from the bypass LSP and considers the primary path as
not configured.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example defines dbyp-path as the primary path.
device>configure
device(config)# router mpls
device(config-router-mpls)# bypass-lsp dbyp-path
device(config-router-mpls-bypass-lsp-dbyp-path)#
The following example defines dbyp-path as the primary path for dynamic bypass MPLS ethernet
interface 0/8.
device>configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# primary-path dbyp-path
priority
Sets the priority of a physical router in a VRRP router group.
Syntax
priority range
Command Default
The default priority is 100.
Parameters
range
The priority of a physical router in a virtual router group. Higher numbers have priority over
lower numbers. Valid values range from 1 to 254.
Modes
Virtual-router-group configuration mode
Usage Guidelines
You can perform this command for VRRP or VRRP-E.
When set, the highest priority backup router will always be the master. (For VRRP, however, the owner
is always the master if it is available.) If not set, a higher priority backup will not preempt a lower priority
backup that is acting as master.
For an owner router in VRRP, the priority automatically becomes 255 if the virtual IP address of the
virtual router and the real IP address of the owner are the same.
Examples
To set the priority to 110 for the VRRP virtual group 1:
device# configure terminal
device(config)# protocol vrrp
device(config)# interface ve 10
device(config-if-Ve-10)# vrrp-group 1
device(config-vrrp-group-1)# priority 110
priority-group-table
Defines the Priority Group ID (PGID) and the scheduling policy associated with it. Each PGID can be
assigned one of 16 values. The valid values are [0-7] and [15.0-15.7]. The value range 0-7 indicate DWRR
priority and the range 15.0-15.7 indicate Strict Priority values. This configuration and the priority-
table configuration sets how traffic is handled when congestion occurs. For DWRR traffic, packets are
dropped when PFC is not enabled for that flow.
Syntax
priority-group-table <Priority Group> weight <weight in percent> pfc
[ on | off ]
priority-group-table <Priority Group> pfc [ on | off ]
[no] priority-group-table <Priority Group>
Parameters
<Priority Group>
Configures the Priority Group. Valid values are 0-7 and 15.0-15.7.
A value in the range 0-7 indicate DWRR priority and unless the PFC is set for the entry, packets
are liable to be dropped if congestion occurs.
A value in the range 15.0-15.7 indicates strict priority traffic. Traffic in this range is never dropped.
Within this range, packets marked with 15.0 has a higher priority than packets marked with 15.1,
packets marked with 15.1 has higher priority than those marked with 15.2, and so on. Packets
marked as 15.7 has the lowest priority within the Strict Priority group.
weight <weight in percent>
For DWRR traffic only. DWRR traffic is in the range 0-7. Sets a value in percentage. For example,
set 10 for 10%, 20 for 20%. Ensure that the sum of all DWRR weights in this table must be equal
to 100%. If the sum does not equal 100%, then an error is thrown.
pfc [ on | off ]
For DWRR traffic only. Configures Priority Flow Control (PFC) for this entry. PFC is enabled when
set to on. It is recommended that no more than one (1) priority group be enabled for PFC.
Modes
CEE Map Mode
Usage Guidelines
PFC can only be enabled for DWRR traffic. It is recommended that only one priority group be
configured as PFC enabled. You must create separate entries for each of the priority groups. There can
be maximum sixteen (16) entries in the Priority Group Table.
The no form of this command removes a priority-group-table configuration entry from the CEE map.
Examples
Configures the Priority Group Table values.
device# configure terminal
device(config)# cee-map default
device(config-cee-map-default)# priority-group-table 15.0 pfc off
device(config-cee-map-default)# priority-group-table 15.1 pfc off
device(config-cee-map-default)# priority-group-table 15.2 pfc off
device(config-cee-map-default)# priority-group-table 15.3 pfc off
device(config-cee-map-default)# priority-group-table 15.4 pfc off
device(config-cee-map-default)# priority-group-table 15.5 pfc off
device(config-cee-map-default)# priority-group-table 15.6 pfc off
device(config-cee-map-default)# priority-group-table 15.7 pfc off
device(config-cee-map-default)#
priority-table
Maps the Priority Group Table entries to priority groups.
Syntax
priority-table <Priority Group ID>
[no] priority-table
Parameters
<Priority Group ID>
Configures the CoS to Priority Group Table mapping. Ensure that you map the CoS to those
priority groups for which bandwidth is allocated.
Modes
CEE Map Mode
Usage Guidelines
Ensure that you map the CoS to those priority groups for which bandwidth is allocated. The CoS 7 is
always reserved for the Strict Priority traffic and is assigned the Priority Group 15.0.
The no form of this command removes the CoS to Priority Group Table mapping.
Examples
This example maps the CoS to priority groups.
device# config term
device(config)# cee-map default
device(config-cee-map-default)# priority-table 2 2 2 1 2 2 2 15.0
Priority Table
CoS: 0 1 2 3 4 5 6 7
----------------------------------------
PGID: 2 2 2 1 2 2 2 15.0
Enabled on the following interfaces:
Ethernet 0/1
process-restart
Enables the process restart (PR) capability (for fault recovery) for BGP, IS-IS, MPLS, OSPFv2, and
OSPFv3.
Syntax
process-restart { bgp | isis | mpls | ospfv2 | ospfv3}
no process-restart { bgp | isis | mpls | ospfv2 | ospfv3}
Command Default
The process restart capability for BGP, IS-IS, OSPFv2, and OSPFv3 is disabled. The process restart
capability for MPLS is enabled.
Parameters
bgp
Specifies the BGP protocol.
isis
Specifies the IS-IS protocol.
mpls
Specifies the MPLS protocol.
ospfv2
Specifies the OSPFv2 protocol.
ospfv3
Specifies the OSPFv3 protocol.
Modes
HA configuration mode (config-ha)
Usage Guidelines
Note
The process restart capability should not be enabled when BGP EVPN is configured. For more
information, see the Extreme SLX-OS Layer 3 Routing Configuration Guide.
The process restart capability for BGP, IS-IS, MPLS, OSPFv2 and OSPFv3 is a fault containment
mechanism that ensures that process-level failures do not cause system-level failures.
All of these processes are COLD restartable processes, meaning when there is a fault inside one of these
processes, and it crashes, the system does not undergo a failover. Instead, the process is restarted on
the same ACTIVE MM. All the other modules and processes that interact with this particular process are
made aware of the process restart, and they adjust accordingly.
All MPLS-based services, such as IPoMPLS, VLL, and VPLS, are disrupted for the duration of MPLS
process restart. After the MPLS process is restarted, the control protocols (LDP and RSVP) re-signal the
tunnels and cross-connects and all the dependent MPLS applications to resume service. For routing
protocols such as BGP, IS-IS and OSPF, all the existing adjacencies are brought down, and are
reestablished after the process comes up again. Some traffic loss can be expected until the adjacency
comes up again.
If more than one process restart happens within a minute, the entire board reboots, resulting in device
reload.
The benefits of the process restart feature can be seen in the following cases:
• The unplanned outage of the routing protocol process can be handled without impacting the whole
system or other dependent services.
• The system returns to a stable state quicker than if nonstop routing (NSR) or graceful restart (GR) is
configured on the device.
The following table lists the precedence of process restart over GR or NSR.
Examples
The following example disables the process-restart capability for MPLS.
device# configure terminal
device(config)# ha
device(config-ha)# no process-restart mpls
profile (LLDP)
Creates an LLDP profile.
Syntax
profile name
no profile name
Parameters
name
Assigns a name to the profile. The name must be between 1 and 63 ASCII characters in length.
name
Assigns a name to the profile. The name must be between 1 and 32 ASCII characters in length.
Modes
Protocol LLDP configuration mode
Usage Guidelines
When you apply an LLDP profile on an interface using the lldp profile command, it overrides the
global configuration. If a profile is not present, then the default global profile is used until you create a
valid profile. Up to 64 profiles can be created.
Examples
The following example creates a profile named test.
profile (telemetry)
Designates telemetry profiles for telemetry collectors.
Syntax
profile enhanced-queue-discard-pkts-profile
default_enhanced_queue_discard_pkts_statistics
no profile enhanced-queue-discard-pkts-profile
default_enhanced_queue_discard_pkts_statistics
profile enhanced-queue-max-queue-depth-profile
default_enhanced_queue_max_queue_depth_statistics
no profile enhanced-queue-max-queue-depth-profile
default_enhanced_queue_max_queue_depth_statistics
profile interface-profile default_interface_statistics
no profile interface-profile default_interface_statistics
profile mpls-traffic-bypass-profile
default_mpls_traffic_bypass_statistics
no profile mpls-traffic-bypass-profile
default_mpls_traffic_bypass_statistics
profile mpls-traffic-fec-profile default_mpls_traffic_fec_statistics
no profile mpls-traffic-fec-profile default_mpls_traffic_fec_statistics
profile mpls-traffic-lsp-profile default_mpls_traffic_lsp_statistics
no profile mpls-traffic-lsp-profile default_mpls_traffic_lsp_statistics
profile queue-profile default_queue_statistics
no profile queue-profile default_queue_statistics
profile system-profile default_system_utilization_statistics
no profile system-profile default_system_utilization_statistics
Command Default
No profile is designated.
Parameters
enhanced-queue-discard-pkts-profile
default_enhanced_queue_discard_pkts_statistics
(Supported only on SLX 9540 and SLX 9640 devices) Specifies profile
default_enhanced_queue_discard_pkts_statistics of the enhanced-queue-
discard-pkts profile type. This profile tracks packets discarded in the 32 queues with the
most discards.
enhanced-queue-max-queue-depth-profile
default_enhanced_queue_max_queue_depth_statistics
(Supported only on SLX 9540 and SLX 9640 devices) Specifies profile
default_enhanced_queue_max_queue_depth_statistics of the enhanced-
queue-max-queue-depth profile type. This profile tracks maximum queue size in the 32
queues with the largest queue size.
interface-profile default_interface_statistics
Specifies profile default_interface_statistics of the interface profile type.
mpls-traffic-bypass-profile default_mpls_traffic_bypass_statistics
(Supported only on SLX 9540 and SLX 9640 devices) Specifies profile
default_mpls_traffic_bypass_statistics of the mpls-traffic-bypass profile
type.
mpls-traffic-fec-profile default_mpls_traffic_fec_statistics
(Supported only on SLX 9540 and SLX 9640 devices) Specifies profile
default_mpls_traffic_fec_statistics of the mpls-traffic-fec profile type.
mpls-traffic-lsp-profile default_mpls_traffic_lsp_statistics
(Supported only on SLX 9540 and SLX 9640 devices) Specifies profile
default_mpls_traffic_lsp_statistics of the mpls-traffic-lsp profile type.
queue-profile default_queue_statistics
(Supported only on SLX 9540 and SLX 9640 devices) Specifies profile
default_queue_statistics of the queue profile type. This profile captures the overall
queue statistics for the device.
system-profile default_system_utilization_statistics
Specifies profile default_system_utilization_statistics of the system-
utilization profile type.
Modes
Telemetry-collector configuration mode
Usage Guidelines
The no version of this command removes the profile details from the collector.
Examples
Typical command execution example.
device# configure terminal
device(config)# telemetry collector collector_1
device(config-telemetry-collector-collector_1)# profile system-profile
default_system_utilization_statistics
profile counters
Optimizes hardware counters.
Syntax
profile counters { counter-profile-1 | counter-profile-2 | counter-
profile-3 | counter-profile-4 | counter-profile-5 | counter-profile-6
| default }
Command Default
The default counter profile is enabled and statistics are collected for ingress and egress L4 traffic.
Parameters
counter-profile-1
Specifies resources optimized for Ingress ACL, OF, and Egress ACL, with forward and drop
counting for Layer 4 ingress traffic.
counter-profile-2
Specifies resources optimized for OF, MPLS, VPLS, VLL, and MCT, with hit counting for Layer 4
ingress traffic.
counter-profile-3
Specifies resources optimized for MPLS, VPLS, VLL, MCT, with hit counting for Layer 4 ingress
traffic.
counter-profile-4
L4-optimized, forward or drop counting for all ingress L4.
Specifies resources optimized for Layer 4 traffic, with forward and drop counting for all Layer 4
ingress traffic.
counter-profile-5
Specifies resources optimized for egress rate limit, with support for counting up to 32,000 VOQs.
counter-profile-6
Specifies resource optimized for reporting egress VE traffic statistics. This is only supported on
SLX 9540 and SLX 9640 devices where the corresponding counter engines are setup for
counting egress VE statistics.
default
Ingress and egress L4.
Modes
Hardware configuration mode
Usage Guidelines
This command is supported only on devices based on the Broadcom DNX chipset family. For a list of
such devices, see the Supported Hardware topic.
For the new setting to take effect, you need to run the copy running-config startup-config
to reload the device. Run this command during a maintenance window so that the profile changes are
activated without interrupting normal network services.
Use the profile counters default form of the command to restore the default setting.
The option counter-profile-6 is only available for SLX 9540 and SLX 9640 devices where the
corresponding counter engines are setup for counting egress VE statistics.
Examples
The following example optimizes bridge domain hit counting for Layer 4 ingress traffic.
device# configure terminal
device(config)# hardware
device(config-hardware)# profile counters counter-profile-2
**Warning: To activate the new profile config, please run 'copy running-config
startup-config' followed by reload system.
The following example configures the device for collecting egress VE traffic statistics.
device# configure terminal
device(config)# hardware
device(config-harware)# profile counters counter-profile-6
**Warning: To activate the new profile config, please run 'copy running-config
startup-config' followed by reload system.
profile etcam
Specifies external TCAM (ETCAM) profiles to support border profiles for Internet peering.
Syntax
profile etcam { default | ipv4-v6-route | ipv6-route }
Command Default
The default ETCAM profile is enabled.
Parameters
default
Specifies the default ETCAM profile: IPv4 unicast routes in the external lookup device (ELK). The
internal longest prefix match (LPM) is used to program IPv6 unicast routes.
ipv4-v6-route
Specifies the profile that programs IPv4 and v6 unicast routes on external TCAM.
ipv6-route
Specifies the profile that programs IPv6 unicast routes in the external TCAM. The internal LPM is
used to program IPv4 unicast routes.
Modes
Hardware configuration mode
Usage Guidelines
This command is supported only on the SLX 9640.
For the new setting to take effect, you need to run the copy running-config startup-config
to reload the device. Run this command during a maintenance window so that the profile changes are
activated without interrupting normal network services.
This command does not have a no form. Specify default to revert to the default settings.
Examples
The following example specifies that IPv4 and IPv6 routes are programmed in the ELK.
device# configure terminal
device(config)# hardware
device(config-hardware)# profile etcam ipv4-v6-route
**Warning: To activate the new profile config, please run 'copy running-config
startup-config' followed by reload system.
profile lag
Configures a LAG profile for hardware support.
Syntax
profile lag { default | lag-profile-1 }
Command Default
The default LAG profile is enabled.
Parameters
default
Specifies the default LAG profile. As described in the Usage Guidelines, the maximum numbers
of port-channel IDs and links per port-channel vary with device and TCAM profile.
lag-profile-1
Specifies lag-profile-1 as the LAG profile. As described in the Usage Guidelines, the maximum
numbers of port-channel IDs and links per port-channel vary with device and TCAM profile.
Modes
Hardware configuration mode
Usage Guidelines
This command is supported only on devices based on the Broadcom DNX chipset family. For a list of
such devices, see the Supported Hardware topic.
To view the current LAG profile, enter the show hardware profile current command.
For the new setting to take effect, you need to run the copy running-config startup-config
to reload the device. Run this command during a maintenance window so that the profile changes are
activated without interrupting normal network services.
This command does not support a no form. Use the profile lag default form of the command
to restore the default LAG profile.
Note
• For the 1U SLX 9740-40, the number of LAGs will be 77, where:
◦ 76 are the front end ports (all breakouts)
◦ 1 (insight port)
• For the 2U SLX 9740-80, the number of LAGs will be 153. where:
◦ 152 are the front end ports (all breakouts)
◦ 1 (insight port)
Maximum numbers of port-channel IDs and links per port-channel vary with device and LAG profile, as
follows.
Table 16: Port-channel scale for SLX 9540 and SLX 9640 devices
Examples
The following example specifies lag-profile-1.
device# configure terminal
device(config)# hardware
device(config-hardware)# profile lag lag-profile-1
**Warning: To activate the new profile config, please run 'copy running-config
startup-config' followed by reload system.
profile qos
Sets the QoS profile for hardware.
Syntax
profile qos { lossless | lossy }
Command Default
No explicit configuration of lossy or lossless profile is configured on the interface.
Parameters
lossless
Sets lossless buffer pool support on the hardware interface.
lossy
Sets lossy buffer pool support on the hardware interface.
Modes
Hardware configuration mode
Usage Guidelines
Use this command on ExtremeSwitching SLX 9150 and ExtremeSwitching SLX 9250 to enable
allocating 25% of the packet buffer to the lossless pool during initialization.
The ExtremeSwitching SLX 9150 and ExtremeSwitching SLX 9250 switches have limited on-board
memory. Allocating a portion of this memory for lossless pool when not required is a waste of this
limited resource. This command enable you to select when to use the lossless pool.
Examples
To set the hardware QoS mode to lossless mode.
profile route
Specifies the hardware route profile and maximum load-sharing path.
Syntax
profile route { default | enable | max-l2 | max-l3-host | max-route |
maximum-paths | route-enhance }
profile route default
profile route enable { ipv6-max-prefix-64 | urpf }
[no] profile route enable { ipv6-max-prefix-64 | urpf }
profile route max-l2
profile route max-l3-hosts
profile route max-routes
profile route maximum-paths { 8 | 16 | 32 | 64 }
profile route route-enhance { hw_opt | multi_vrf | v4_fib_comp |
v6_fib_comp }
Command Default
The default route profile is enabled.
Parameters
default
Specifies the default route profile. (Not supported on SLX 9640.)
enable { ipv6-max-prefix-64 | urpf }
• ipv6-max-prefix-64 - Use this option to enable/disable 64-bit prefix only mode for IPv6
routes. When enabled, IPv6 routes with prefix lengths of > 64 bits will not be accepted. (Only
supported on SLX 9150 and SLX 9250.)
• urpf - Use this option to enable/disable urpf (Unicast Reserve Path Forwarding) support on
the device. When this is enabled, it reduces the maximum route/host capacity on the SLX
device by half. This configuration knob only enables/disables the hardware capability on the
SLX device. rpf-mode configuration CLI needs to be configured on the L3 interface level
for the uRPF function. (Only supported on SLX 9150 and SLX 9250.)
Note
Interface level uprf configuration will not have any impact without this profile
being enabled.
max-l2
Sets a profile that maximizes the addition of L2-MACs over L3 Unicast Hosts or L3 Unicast
Routes.
max-l3-host
Sets a profile that maximizes the addition of L3 Unicast Hosts over L3 Unicast Routes or L2-
MACs.
max-routes
Sets a profile that maximizes the addition of L3 Unicast Routes over L3 Unicast Hosts or L2-
MACs.
maximum-paths { 8 | 16 | 32 | 64 }
Configures the maximum number of load sharing paths for ECMP. Select from one of the
available choices.
route-enhance
(supported only on SLX 9540) Specifies various route enhancement.
hw_opt
Specifies route enhancement for hardware optimization. Disabled by default.
multi_vrf
Specifies route enhancement for multiple VRF support (route scaling) on a non-default VRF.
v4_fib_comp
Specifies route enhancement for IPv4 FIB compression.
v6_fib_comp
Specifies route enhancement for IPv6 FIB compression.
{ off | on }
(supported only on SLX 9540) Disables or enables the specified route-enhance options. By
default, all options are disabled.
Modes
Hardware configuration mode
Usage Guidelines
To display the default and current number of routes supported for your device, run the show
hardware profile command.
Use the profile route default form of the command to restore the default setting.
Use the no profile route enable form of the command to disable the route forwarding
features.
Examples
The following example sets 64 as the maximum paths for ECMP.
The following command enables preferring L2 MACs over L3 Unicast Routes or L3 Unicast Host.
profile tcam
Optimizes hardware resources, by specifying a ternary content-addressable memory (TCAM) profile.
Syntax
profile tcam { app-telemetry | border-routing | default | layer2-
ratelimit | multicast-profile | vxlan-visibility }
Command Default
The default TCAM profile is enabled.
Parameters
app-telemetry
Optimizes resources for application telemetry. MCT is supported.
border-routing
Optimizes resources for border routing and BGP Flowspec features.
default
Optimizes resources with basic support for all applications. MCT is supported.
layer2-ratelimit
Optimizes resources for Layer 2 ACL egress rate-limiting and related applications.
multicast-profile
Optimizes resources for Layer 2 and Layer 3 IPv6 multicast.
vxlan-visibility
Optimizes resources for VXLAN transit visibility and GRE.
Modes
Hardware configuration mode
Usage Guidelines
This feature is supported only on devices based on the Broadcom DNX chipset family. For a list of such
devices, see "Supported Hardware".
This command does not support a no form. Use the profile tcam default form of the command
to restore the default setting.
For the new setting to take effect, you need to run the copy running-config startup-config
to reload the device. Run this command during a maintenance window so that the profile changes are
activated without interrupting normal network services.
Examples
The following example optimizes TCAM resources for Layer 2 applications and VPLS support.
device# configure terminal
device(config)# hardware
device(config-hardware)# profile tcam layer2-ratelimit
Syntax
profile tcam cam-share [ l2-ingress-acl ] [ l3-v4-ingress-acl ] [ l3-v4-
pbr ] [ l3-v6-ingress-acl ] [ l3-v6-pbr ]
no profile tcam cam-share
Command Default
By default, TCAM sharing is disabled.
Parameters
l2-ingress-acl
Enables TCAM sharing for Layer 2 security ACLs applied to ingress traffic.
l3-v4-ingress-acl
Enables TCAM sharing for IPv4 security ACLs applied to ingress traffic.
l3-v4-pbr
Enables TCAM sharing for IPv4 ACLs included in route maps for PBR.
l3-v6-ingress-acl
Enables TCAM sharing for IPv6 security ACLs applied to ingress traffic.
l3-v6-pbr
Enables TCAM sharing for IPv6 ACLs included in route maps for PBR.
Modes
Hardware configuration mode
Usage Guidelines
TCAM sharing is supported only on devices based on the DNX chipset family. For a list of such devices,
see "Supported Hardware". On the SLX 9540, all ports share the same ASIC.
TCAM sharing for security ACLs works as follows: TCAM resources are shared if a specific ACL is applied
to multiple ports.
TCAM sharing for PBR ACLs works as follows: TCAM resources are shared if a specific ACL (included in
one or more route maps) is applied to multiple ports.
When you change the TCAM profile type, also update cam sharing based on the limitation of the new
profile. TCAM sharing is not supported for user-defined ACLs or for ACLs that are applied for rate
limiting.
For the new setting to take effect, you need to run the copy running-config startup-config
to reload the device. Run this command during a maintenance window so that the profile changes are
activated without interrupting normal network services.
Examples
This example enables TCAM cam sharing for Layer 2 ingress ACL.
device(config)# hardware
device(config-hardware)# profile tcam cam-share l2-ingress-acl
**Warning: To activate the new profile config, please run
'copy running-config startup-config' followed by 'reload system'.
protocol
Configures the authentication protocol to use for communication with the Remote Authentication Dial-
In User Service (RADIUS) server.
Syntax
protocol { chap | pap | peap }
no protocol
Command Default
The default protocol is Challenge Handshake Authentication Protocol (CHAP).
Parameters
chap
Specifies using CHAP for communication with the RADIUS server.
pap
Specifies using Password Authentication Protocol (PAP) for communication with the RADIUS
server.
peap
Specifies using Protected Extensible Authentication Protocol (PEAP) for communication with
the RADIUS server.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the command default value.
Examples
The following example shows how to configure PAP as the authentication protocol for communication
with the RADIUS server.
protocol cfm
Enables the CFM protocol globally on the devices and enter into the CFM Protocol Configuration mode.
Syntax
protocol cfm
no protocol cfm
Command Default
This command is executed on the local switch.
Modes
Privileged EXEC mode
Usage Guidelines
The no form of this command disables the CFM protocol on the device.
Examples
device#(config)protocol cfm
device(config-cfm)#
protocol link-oam
Allows you to enter the link OAM global configuration mode.
Syntax
protocol link-oam
Command Default
This command is executed on the local switch.
Modes
Privileged EXEC mode
Examples
protocol lldp
Enters the Link Layer Discovery Protocol (LLDP) configuration mode.
Syntax
protocol lldp
no protocol lldp
Command Default
LLDP protocols are enabled.
Modes
Global configuration mode
Usage Guidelines
Enter no protocol lldp to restore the default settings.
Examples
To enter LLDP mode:
protocol loop-detection
Enables the loop detection (LD) feature globally and enters Protocol Loop Detection configuration
mode.
Syntax
protocol loop-detection
no protocol loop-detection
Command Default
This feature is disabled.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to disable loop detection globally.
Examples
To enable loop detection globally and enter Protocol Loop Detection configuration mode:
device# configure terminal
device(config)# protocol loop-detection
device(config-loop-detect)#
protocol mvrp
Enables Multiple VLAN Registration Protocol (MVRP) globally on the device and accesses MVRP
configuration mode.
Syntax
protocol mvrp
no protocol mvrp
Command Default
MVRP is disabled globally and on all interfaces by default.
Modes
Global configuration mode
Usage Guidelines
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
The no form of this command disables MVRP globally on the device and on all interfaces enabled with
MVRP.
For an interface to participate in MVRP, you must configure MVRP on the interface through the mvrp
enable command.
You cannot enable MVRP when the following features are enabled on the device and vice versa:
• PVST
• RPVST
• MSTIs for MSTP
• Topology groups
• Ring protocols
Examples
The following example shows the enabling of MVRP globally.
device# configure terminal
device (config)# protocol mvrp
device (config-mvrp)#
protocol spanning-tree
Designates the context for spanning tree.
Syntax
protocol spanning-tree { mstp | rstp | stp | pvst | rpvst }
no protocol spanning-tree
Command Default
STP is not enabled. STP is not required in a loop-free topology.
Parameters
mstp
Specifies the Multiple Spanning Tree Protocol (MSTP).
rstp
Specifies the Rapid Spanning Tree (RSTP).
stp
Specifies the Spanning Tree Protocol (STP).
pvst
Specifies Per-VLAN Spanning Tree Protocol Plus (PVST+).
rpvst
Specifies Rapid Per-VLAN Spanning Tree Protocol Plus (R-PVST+).
Modes
Global configuration mode
Usage Guidelines
Consider enabling STP to detect or avoid loops. You must turn off one form of STP before turning on
another form.
Packet drops or packet flooding may occur if you do not enable xSTP on all devices connected on both
sides of parallel links.
Enter no protocol spanning-tree to delete the context and all the configurations defined within
the context or protocol for the interface.
Examples
To enable the Spanning Tree Protocol:
protocol udld
Enables and/or enters unidirectional link detection (UDLD) protocol configuration mode.
Syntax
protocol udld
no protocol udld
Command Default
This protocol is disabled by default.
Modes
Global configuration mode
Usage Guidelines
UDLD detects and blocks a physical link that becomes unidirectional. A unidirectional link can cause
traffic in a network to loop endlessly. When the link becomes bidirectional again, UDLD unblocks the
link.
This protocol applies only to physical ports. In addition to running this command, you must also enable
each desired port for UDLD in interface subconfiguration mode.
Use the no protocol udld command to disable the UDLD protocol and revert all UDLD
configuration to defaults.
Examples
To enable the unidirectional link detection (UDLD) protocol:
device# configure terminal
device(config)# protocol udld
protocol vrrp
Globally enables Virtual Router Redundancy Protocol (VRRP).
Syntax
protocol vrrp
no protocol vrrp
Command Default
VRRP is not enabled.
Modes
Global configuration mode
Usage Guidelines
The no form of this command globally disables VRRP.
Examples
To enable VRRP:
device# configure terminal
device(config)# protocol vrrp
protocol vrrp-extended
Globally enables VRRP-Extended.
Syntax
protocol vrrp-extended
no protocol vrrp-extended
Command Default
Disabled
Modes
Global configuration mode
Usage Guidelines
The no protocol vrrp-extended command globally disables VRRP-E.
Examples
To enable VRRP-Extended:
device# configure terminal
device (config)# protocol vrrp-extended
prune-wait
Configures the amount of time a PIM device waits to stop traffic after receiving a Prune message from a
neighboring device.
Syntax
prune-wait seconds
no prune-wait
Command Default
The default wait time is 3 seconds.
Parameters
seconds
Specifies the wait time in seconds. Valid values range from 0 through 30 seconds.
Modes
PIM router configuration mode
Usage Guidelines
A smaller prune wait time reduces flooding of unwanted traffic. A prune wait time of 0 causes the PIM
device to stop traffic immediately upon receiving a prune message.
Do not configure a prune wait time when there are two or more neighbors on the physical port. One
neighbor may send a prune message while the other sends a join message at the same time, or within
less than 3 seconds.
The no prune-wait form of this command restores the default wait time of 3 seconds.
Examples
This example configures a wait time of 0 seconds for IPv4 PIM.
device(config)# router pim
device(config-pim-router)# prune-wait 0
pw-profile
Creates a pseudowire (PW) profile that can be shared across multiple Virtual Private LAN Services
(VPLS) bridge domains.
Syntax
pw-profile [ pw-profile-name [ mtu mtu-value ] [ mtu-enforce { false |
true } ] [ vc-mode { raw | raw-passthrough | tag } ]
no pw-profile pw-profile-name [ mtu ] [ mtu-enforce ] [ vc-mode ] ]
Command Default
No PW profile is configured.
Parameters
pw-profile-name
Specifies the name of a PW profile.
mtu mtu-value
Specifies the maximum transmission unit (MTU) for the PW profile. The range is from 64 through
15966.
mtu-enforce
Configures MTU enforcement check during PW signaling.
false
Enables the MTU enforcement check.
true
Disables the MTU enforcement check.
vc-mode
Note
When a pseudowire profile is attached to a bridge domain, on which routing is
enabled (by using the router-interface command), you are not allowed to
change the pseudowire profile vc-mode configuration to raw.
when all endpoints are configured as untagged endpoints (even when peer devices signal the
PW VC mode as raw).
tag
Specifies using tag mode. At VC label imposition, when a tagged packet is received on a tagged
AC endpoint, the packet is encapsulated as is and sent out on the wire. When an untagged
packet is received on an untagged AC endpoint, a dummy tag is added and it is sent out on the
wire.
Modes
Global configuration mode.
Usage Guidelines
You can configure up to 64 PW profiles.
Examples
The following example shows how to create a PW profile named test specifying that the VC mode for
the profile is raw-passthrough.
Syntax
pw-profile pw-profile-name
no pw-profile
Command Default
A PW profile is not configured.
Parameters
pw-profile-name
Specifies the name of the PW profile to attach to the bridge profile.
Modes
Bridge-domain configuration mode.
Usage Guidelines
The no form of the command removes the PW profile from the bridge-domain configuration.
Examples
The following example shows how to configure a PW profile named test for bridge domain 1.
python
Launches an interactive Python shell, with an option to launch a Python script.
Syntax
python [ python-statement | python-script-filename ] [ script-arguments ]
Parameters
python-statement
Must be a valid python interpreter argument.
python-script-filename
Runs a Python script file. Valid values range from 4 through 32 characters (including the .py
extension). The first character must be alphabetic.
script-arguments
Passes one or more arguments defined in the script.
Modes
Privileged EXEC mode
Usage Guidelines
This command is available only to users with admin-level permissions.
Entering python python-statement launches an interactive Python shell and runs a valid
python-statement that you enter. For example, entering python -h invokes the Python shell and
displays Python options and arguments.
Entering python python-script-filename launches an interactive Python shell and runs the
Python file. (To make a Python file available to this command, copy the Python file to the flash://
location on the device, using the copy command.)
Note the following divergence between SLX-OS CLI syntax and Python syntax:
• Although in general, SLX-OS CLI syntax is not case-sensitive, Extreme convention is to use lower-
case.
• Python syntax is case sensitive.
To exit the Python environment and return to the CLI, enter either:
• exit()
• Ctrl-D
Examples
The following example launches the Python shell and then both assigns an SLX CLI operational
command to a Python variable and runs that command.
device# python
Python 3.5.2 (default, Apr 11 2019, 13:05:18)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> cmd_show_users = CLI('show users')
!Command: show users
!Time: Tue Aug 9 09:09:39 2016
**USER SESSIONS**
Username Role Host IP Device Time Logged In
jdoe admin 10.11.12.13 Cli 2016-08-09 09:06:46
admin admin 127.1.0.1 Cli 18640
**LOCKED USERS**
Username
no locked users
>>>
The following example (partial) launches the Python shell to run a Python script-file.
Note
For an annotated text of this script, refer to the Extreme SLX-OS Management Configuration
Guide > "Python Event-Management and Scripting" > "Python scripts and run-logs."
vlan 1
!
vlan dot1q tag native
!Command: config
vlan 101-105
!Time: Fri Dec 16 18:35:41 2016
vlan 1
!
vlan 101
!
vlan 102
!
vlan 103
!
vlan 104
!
vlan 105
!
vlan dot1q tag native
% No entries found.
!Command: config
int po 10
switchport
switchport mode trunk
switchport trunk allowed vlan add 101-105
switchport trunk tag native-vlan ; no shut
!Time: Fri Dec 16 18:35:41 2016
interface Port-channel 10
switchport
switchport mode trunk
switchport trunk allowed vlan add 101-105
The following example launches the Python shell to test an event-handler script-file.
Note
For more information, refer to the "Python Event-Management and Scripting" > "Guidelines
for writing Python scripts" topic in the Extreme SLX-OS Management Configuration Guide.
qos cos-traffic-class
Applies a Quality of Service (QoS) CoS-to-traffic class mutation map on an interface.
Syntax
qos cos-traffic-class cos_map_name
Command Default
No explicit QoS CoS-to-traffic class mutation map is applied; the inbound CoS equals the outbound
CoS.
Parameters
cos_tc_map_name
The name of the CoS-to-traffic class mutation map.
Modes
Interface configuration mode.
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress,
mutation mapping occurs before traffic classification and all other actions. On egress, mutation
mapping occurs after traffic classification and before all other actions.
Examples
To activate a QoS CoS-to-traffic class mutation map named cosMutMap on a specific Ethernet
interface:
To activate a QoS CoS-to-traffic class mutation map from a specific port channel interface:
Syntax
qos cpu slot line-card-number { group group_id { prio { priority | all }
| shaper rate shaper_rate burst burst_size | wfq weight
weight_value }
qos cpu slot line-card-number { port shaper rate shaper_rate burst
burst_size }
no qos cpu slot line-card-number { group group_id { prio { priority |
all } | shaper rate shaper_rate burst burst_size | wfq weight
weight_value }
no qos cpu slot line-card-number { port shaper rate shaper_rate burst
burst_size }
Command Default
The Traffic Manager CPU group or port shaper rate is not set.
Parameters
line-card-number
The values are 0 on Pizzabox platforms, 1 through 4 on F4 platforms, and 1 through 8 on F8
platforms.
group group_id
Configures a CPU group.
shaper rate shaper_rate
Configures the Traffic Manager CPU shaper rate (all towers) to the line card CPU for CPU groups.
The rate is in kilo bits per second (Kbps) with a range from 0 through 100000.
prio priority
Configures the Traffic Manager CPU shaper rate (all towers) to the line card CPU for individual
priority VoQs in a CPU group. The priority value ranges from 0 through 7.
burst burst_size
Configures the CPU burst size. The burst size value ranges from 1 through 64 KB.
wfq weight weight_value
Configures the CPU group's weighted fair queue value (all towers). The weight value ranges from
1 through 128.
port
Configures a CPU port.
Modes
Global configuration mode.
Usage Guidelines
The no form of the command removes the QoS CPU shaper configuration.
Examples
This example sets the Traffic Manager CPU port shaper on slot 1 to priority 5, with a rate of 4500 Kbps,
and a burst size of 1KB.
device# configure terminal
device(config)# qos cpu slot 1 port shaper rate 4000 burst 1
This example sets the Traffic Manager CPU port shaper on slot 1 to 4000 Kbps with a burst size of 1KB.
device# configure terminal
device(config)# qos cpu slot 1 port shaper rate 4000 burst 1
This example sets the Traffic Manager CPU on slot 1 group 1 priority to 5, with a rate of 4500 Kbps, and a
burst size of 1KB.
device# configure terminal
device(config)# qos cpu slot 1 group 1 priority 5 shaper rate 4500 burst 1
qos dscp-cos
Applies a user configured QoS DSCP-to-CoS mutation map to an interface.
Syntax
qos dscp-cos dscp_cos_map_name
Command Default
No explicit QoS DSCP-to-CoS mutation map is applied.
Parameters
dscp_cos_map_name
Name of DSCP-to-COS mutation map
Modes
Interface configuration mode.
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress,
mutation mapping occurs before traffic classification and all other actions. On egress, mutation
mapping occurs after traffic classification and before all other actions.
Examples
Follow this example to apply a user configured QoS DSCP-to-COS mutation map named dscpMap to a
specific Ethernet interface.
Follow this example to apply a user configured QoS DSCP-to-COS mutation map named dscpMap to a
specific port channel interface.
qos dscp-mutation
Applies a user configured QoS DSCP mutation map to an interface.
Syntax
qos dscp-mutation dscp_map_name
Command Default
No explicit user configured QoS DSCP-to-DSCP mutation map is applied; the inbound DSCP equals the
outbound DSCP.
Parameters
dscp_map_name
The name of the DSCP mutation map
Modes
Interface subtype configuration mode
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress,
mutation mapping occurs before traffic classification and all other actions. On egress, mutation
mapping occurs after traffic classification and before all other actions.
Examples
Follow this example to apply a QoS DSCP-to-DSCP mutation map to a specific Ethernet interface:
qos dscp-traffic-class
Applies a user configured QoS DSCP-to-traffic- class mutation map to an interface.
Syntax
qos dscp-traffic-class dscp_tc_name
Command Default
No explicit user configured QoS DSCP-to-traffic class map is enabled on the interface.
Parameters
dscp_tc_name
Name of DSCP-to-traffic class map
Modes
Interface configuration mode
Usage Guidelines
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress,
mutation mapping occurs before traffic classification and all other actions. On egress, mutation
mapping occurs after traffic classification and before all other actions.
Examples
Follow this example to apply a QoS DSCP-to-traffic class mutation map to a specific 40-gigabit
Ethernet interface
Follow this example to apply a QoS DSCP-to-traffic class mutation map to a specific port channel
interface
qos flowcontrol
Configures link-level flow control (IEEE 802.3x Flow Control) in the transmission and reception direction
on an interface or enables priority flow control on a CoS of an SLX 9150 or SLX 9250 interface.
Syntax
qos flowcontrol [ pfc CoS-number ]tx { on | off } rx { on | off }
no qos flowcontrol
Command Default
By default, link-level flow control (LLFC) reception is enabled.
Parameters
pfc CoS-number
(Optional) Enables priority flow control (PFC) on the specified CoS of an SLX 9150 or SLX 9250
interface. For the CoS-number variable, enter an integer from 0 to 7.
tx { on | off }
Activates or deactivates the transmission portion of flow control.
rx { on | off }
Activates or deactivates the reception portion of flow control.
Modes
Interface configuration mode
Usage Guidelines
LLFC alleviates system congestion by pausing data transmission. LLFC allows a congested receiver to
communicate a PAUSE frame to a transmitter to stop data transmission until the congestion is cleared.
The device supports the transmission (Tx) and reception (Rx) of PAUSE frames for each physical
interface or port channel.
Examples
The following example configures flow control on an interface.
device# configure terminal
device(config)# interface ethernet 1/4
device(conf-eth-1/4)# qos flowcontrol tx on rx on
Syntax
qos map cos-mutation name cos0 cos1 cos2 cos3 cos4 cos5 cos6 cos7
no qos map cos-mutation name
Command Default
No CoS-to-CoS mutation QoS maps are defined.
Parameters
name
Specifies a unique name across all CoS-to-CoS mutation QoS maps defined within the system. If
the named CoS-to-CoS mutation QoS map does not exist, then it is created. If the named CoS-
to-CoS mutation QoS map already exists, then it is updated and new mapping is automatically
propagated to all interfaces bound to the QoS map.
cos#
Specifies the outbound CoS value.
CoS Description
value
c Sets the outbound CoS value for all packets with inbound CoS 0.
o
s
0
c Sets the outbound CoS value for all packets with inbound CoS 1.
o
s
1
c Sets the outbound CoS value for all packets with inbound CoS 2.
o
s
2
c Sets the outbound CoS value for all packets with inbound CoS 3.
o
s
3
c Sets the outbound CoS value for all packets with inbound CoS 4.
o
s
4
CoS Description
value
c Sets the outbound CoS value for all packets with inbound CoS 5.
o
s
5
c Sets the outbound CoS value for all packets with inbound CoS 6.
o
s
6
c Sets the outbound CoS value for all packets with inbound CoS 7.
o
s
7
Modes
Global configuration mode
Usage Guidelines
A CoS-to-CoS mutation takes an inbound CoS value and maps it to an outbound CoS value. The
inbound CoS value is the user priority after any interface ingress QoS trust and Interface default CoS
policy have been applied. The outbound CoS value is used in selecting Traffic Class and egress packet
marking.
Enter no qos map cos-mutation name command to delete the named CoS-to-CoS mutation QoS
map. A QoS map can only be deleted if it is not bound to any interface.
Examples
To create a CoS-to-CoS QoS mutation map to swap CoS 4 and CoS 5 and apply it on an interface, for
example having inbound CoS 4 mapped to outbound CoS 5 and inbound CoS 5 mapped to outbound
CoS 4; but all other CoS values go through unchanged:
Syntax
qos map cos-traffic-class name
no qos map cos-traffic-class name
Command Default
If CoS-to-traffic class mutation map is not defined, the default CoS-to-traffic class map is used, which is
a one-to-one map for each priority.
Parameters
name
Specifies a unique name for the CoS-to-traffic class mutation QoS map. If the named map does
not exist, then it is created. If the map already exists, then it is updated and new mapping is
automatically propagated to all interfaces bound to the map.
Modes
Global configuration mode
Usage Guidelines
A CoS-to-traffic class mutation map takes an inbound CoS value and maps it to an outbound traffic
class (priority queue) value. The inbound CoS value is the user priority after any interface ingress QoS
trust and Interface default CoS policy have been applied.
Examples
This example creates a QoS CoS-to-traffic-class mutation map and assigns it to the specified Ethernet
interface. The drop-precedence parameter is mandatory.
device# configure terminal
device(config)# qos map cos-traffic-class tcmap1
device(cos-traffic-class-tcmap1)# map cos 2 to traffic-class 4 drop-precedence 0
device(cos-traffic-class-tcmap1)# map cos 3 to traffic-class 4 drop-precedence 1
device(cos-traffic-class-tcmap1)# map cos 3 to traffic-class 6 drop-precedence 1
device(cos-traffic-class-tcmap1)# interface ethernet 1/1
device(conf-if-eth-1/1)# qos cos-traffic-class tcmap1
This example removes the mutation map that is bound to the specified Ethernet interface.
device# configure terminal
device(config)# interface ethernet 1/1
device(conf-if-eth-1/1)# no qos cos-traffic-class tcmap1
device(conf-if-eth-1/1)# exit
device(config)# no qos map cos-traffic-class tcmap1
Syntax
qos map dscp-cos name
no qos map dscp-cos name
map dscp ingress dscp values to cos cos
Command Default
DSCP-to-CoS mutation is not enabled.
Parameters
name
Name of DSCP-to-CoS map
map dscp
Ingress DSCP values.
cos
Egress CoS values.
ingress dscp values
Input DSCP values. The range of ingress DSCP values is 0 through 63.
cos
CoS value. The range is 0 through 7.
Modes
dscp-cos mode for the QoS map dscp commands
Usage Guidelines
This command remaps the incoming DSCP values of the ingress packet to egress CoS 802.1P values.
When you enter qos map dscp-cos, the system is placed in dscp-cos mode for the configured map.
At this point, you can map ingress DSCP values to egress CoS values using the map dscp command.
Enter qos dscp-cos name while in configuration mode for a specific interface to apply the DSCP-to-
CoS map to that interface.
Enter no qos dscp-cos name while in the interface configuration mode to remove the DSCP-to-CoS
map from the interface.
Enter no map dscp-cos name while in global configuration mode to remove the DSCP-to-CoS map.
Examples
To create a QoS DSCP-to-CoS map and place system into dscp-cos mode:
To map an ingress DSCP value to egress CoS value while in dscp-cos mode:
To map multiple ingress DSCP values to egress CoS values while in dscp-cos mode:
Syntax
qos map dscp-mutation name
no map qos dscp-mutation name
map dscp ingress dscp values to dscp egress dscp value
Command Default
DSCP mutation is not enabled.
Parameters
name
Name of DSCP mutation map
map dscp
Inbound DSCP values.
ingress dscp values
The ingress DSCP values. The range is from 0 through 63.
dscp
Outbound DSCP values.
egress dscp values
The egress DSCP value. The range is from 0 through 63.
Modes
dscp-mutation mode for the DSCP mutation map
Usage Guidelines
Enter qos dscp-mutation name while in configuration mode for a specific interface to apply the
DSCP mutation map to that interface. When you enter qos map dscp-mutation, the system is
placed in dscp-mutation mode for the configured map. At this point, you can map ingress DSCP values
to egress DSCP values using the dscp map command.
Enter no qos dscp-mutation name while in interface configuration mode to remove the DSCP
mutation map from that interface.
Enter no map dscp-mutation name while in global configuration mode to remove the DSCP
mutation map.
Examples
To create a QoS DSCP mutation map and place system into dscp-mutation mode:
To map an ingress DSCP value to egress DSCP values while in dscp-mutation mode:
To map multiple ingress DSCP values to egress DSCP values while in dscp-mutation mode:
Syntax
qos map dscp-traffic-class name
no qos map dscp-traffic-class name
map dscp ingress dscp values to traffic-class traffic class [ drop-
precedence out drop precedence ]
Command Default
DSCP-to-traffic class mutation is not enabled.
Parameters
name
Name of the QoS DSCP-to-traffic clas map.
map dscp
Ingress DSCP values. The range of ingress DSCP values is 0 through 63.
traffic-class
Egress traffic class values. The range of ingress traffic class values is from 0 through 7.
drop-precedence
Drop precedence value given egress packets. The range is 0 through 3.
ingress dscp values
Range of input DSCP values. The range is 0 through 63.
traffic class
The traffic class value. the range is from 0 through 7.
out drop precedence
Value of the output drop precedence. The range is 0 through 3.
Modes
dscp-traffic-class mode for the DSCP-to-traffic class map
Usage Guidelines
Enter qos dscp-traffic-class name to apply the QoS DSCP-Traffic-Class map to that interface.
When you enter qos map dscp-traffic-class, the system is placed in dscp-traffic-class mode
for the configured map. At this point, you can map ingress DSCP values to traffic class values using the
mark command.
Enter no qos dscp-traffic-class name while in the interface mode to remove the map from
that interface.
Note
This command is supported on devices based on the XGS chipset family. For a list of such
devices, see "Supported Hardware".
Examples
This example creates a QoS DSCP-to-traffic class map and places the system into dscp-traffic-class
mode.
device# configure terminal
device(config)# qos map dscp-traffic-class test
device(dscp-traffic-class-test)#
This example maps multiple ingress DSCP values to traffic classes and drop precedence.
device# configure terminal
device(config)# qos map dscp-traffic-class test
device(dscp-traffic-class-test)# map dscp 10 to traffic-class 3 drop-precedence 1
device(dscp-traffic-class-test)# map dscp 40 to traffic-class 4 drop-precedence 1
device(dscp-traffic-class-test)# map dscp 45 to traffic-class 5 drop-precedence 0
device(dscp-traffic-class-test)# map dscp 52 to traffic-class 3 drop-precedence 1
Syntax
qos map traffic-class-cos name
no qos map traffic-class-cos name
Command Default
If a QoS traffic class-to-CoS mutation map is not defined, the default traffic class-to-CoS map is used,
which is a one-to-one map for each priority.
Parameters
name
Specifies a unique name for the QoS traffic class-to-CoS mutation map. If the named map does
not exist, then it is created. If the map already exists, then it is updated and new mapping is
automatically propagated to all interfaces bound to the map.
Modes
Global configuration mode
Usage Guidelines
A traffic class can be mapped to the outgoing PCP value when a packet egresses the switch. You can
create a priority mapping table using a traffic class-to-CoS map. This traffic class-to-CoS map can then
be applied to an egress interface to effect the priority re-mapping. This feature only maps the internal
traffic class to outgoing priority.
Enter no qos map traffic-class-cos name command to delete the named QoS traffic class-
to-CoS mutation map.
Examples
To create and apply a QoS traffic class-to-CoS mutation map use the following command:
To delete a QoS traffic class-to-CoS mutation map that is bound to an interface follow this example.
qos port-speed-up
Increases the egress throughput rate on a Traffic Manager port on 10G or 100G ports.
Syntax
qos port-speed-up rate
no qos port-speed-up
Parameters
rate
Increased rate in thousand bits per second. For a 10G port, enter an integer from 300000 to
13000000 (equivalent to 300Mb to 13Gb). For a 100G port, enter an integer from 300000 to
130000000 (equivalent to 300Mb to 130Gb).
Command Default
The default throughput rate of the port.
Modes
Interface configuration mode
Usage Guidelines
Use the no form of the command to reset the default setting.
If you configured a breakout connector on an Ethernet interface, you can also increase the egress
throughput rate on the breakout port.
The maximum speed supported by an interface is 130% of the default interface speed.
Examples
The following example increases the egress throughput rate by 300Mb on Ethernet port 0/1.
device# configure terminal
device(config)# interface ethernet 0/1
device(conf-if-eth-0/1)# qos port-speed-up 300000
The following example increases the egress throughput rate by 325Mb on Ethernet breakout port
0/53:4.
device# configure terminal
device(config)# interface ethernet 0/53:4
device(conf-if-eth-0/53:4)# qos port-speed-up 325000
Syntax
qos random-detect traffic-class traffic-class drop-precedence value red-
profile-id ID
no qos random-detect traffic-class traffic-class drop-precedence
Parameters
traffic-class
Specifies the traffic class to apply the RED profile. Enter an integer from 0 through 7.
drop-precedence value
Specifies the drop precedence value for the traffic class. Enter an integer from 1 from 3.
red-profile-id ID
Specifies the RED profile to assign to traffic class on the interface. Enter the identifier for a
configured profile.
Modes
Interface configuration mode
Usage Guidelines
Use the no form of the command to remove the RED profile from the interface or the drop precedence
for the traffic class on the interface.
Examples
The following example configures a RED profile on an interface.
device# configure terminal
device(config)# interface ethernet 0/2
device(conf-if-eth-0/2)# qos random-detect traffic-class 4 drop-precedence 1 red-profile-
id 22
qos red-profile
Configures a weighted random early detection (WRED) profile which includes the setting of the
thresholds and drop probability by percentage. The command also enables or disable Explicit
Congestion Notification (ECN) feature.
Syntax
qos red-profile profile-ID min-threshold min-percentage max-threshold
max-percentage drop-probability percentage ecn { on | off }
no qos red-profile profile-ID
Parameters
profile-ID
Specifies the profile identifier. Enter an integer from 0 to 383.
min-threshold min-percentage
Specifies the minimum average queue size in percentage for randomly dropping packets. Enter
an integer from 0 through 100.
max-threshold max-percentage
Specifies the maximum average queue size in percentage which all packets are accepted by the
device. Enter an integer from 0 through 100.
drop-probability percentage
Specifies the drop probability in percentage when the queue size is at the maximum. Enter an
integer from 0 through 100.
ecn on off
Enables or disables Explicit Congestion Notification (ECN) feature.
Modes
Global configuration mode
Usage Guidelines
You can configure a maximum on 256 profiles.
After configuring the profile, apply it to an interface with the qos random-detect traffic-
class command.
Use the ecn {on | off} command to enable or disable Explicit Congestion Notification (ECN) for
this device. ECN allows the routers and switches to signal the traffic end-points of the congestion
without dropping any frames, and thus the end-points can adjust their transmission rates without the
added latency and jitter that would have been introduced by dropped frames.
When a device detects a congestion, it is imperative that the device indicates to the other end-points
about the congestion as soon as it is detected. Since a congestion in one direction need not imply a
congestion in its opposite direction, this device has to indicate to the other end-point so that it, the
other end-point, can take appropriate action.
ECN requires that Random Early Detection (RED) profiles are created using the red-profile
command and applied to the interface. ECN is only available for Unicast frames.
Examples
The following example is a WRED configuration.
Syntax
qos rx-queue cos-threshold threshold_value_0 threshold_value_1
threshold_value_2 threshold_value_3 threshold_value_4
threshold_value_5 threshold_value_6 threshold_value_7
[no] qos rx-queue cos-threshold
Command Default
The CoS threshold values for the ingress queue are not configured.
Parameters
threshold_value_n
There are eight entries for this parameter with each entry representing a percentage. Each
position matches a specific inbound CoS with the first position (cos_threshold_0)
representing CoS 0, the second CoS 1, and so on.
Modes
Ethernet interface configuration mode.
Usage Guidelines
The total of all the entries cannot exceed 100%.
Examples
Follow this example to configure the QoS ingress queue CoS thresholds on a specific Ethernet interface.
Syntax
qos rx-queue multicast { best-effort-rate | guarantee-rate } kbps
qos rx-queue multicast traffic class number min-queue-size Mbytes max-
queue-size Mbytes
no qos rx-queue multicast best-effort-rate | guarantee-rate
no qos rx-queue multicast traffic class number min-queue-size Mbytes max-
queue-size Mbytes
Parameters
best-effort-rate kbps
Specifies the multicast best effort data rate in kilobits per second (kbps). Enter an integer from
704 through 600000000.
guarantee-rate kbps
Specifies the multicast data guarantee data rate in kilobits per second (kbps). Enter an integer
from 704 through 600000000.
traffic class number
Specifies the traffic class on the interface. Enter an integer from 0 to 7.
min-queue-size Mbytes
Specifies the minimum queue size in megabytes per second. Enter an integer from 0 through
1024.
max-queue-size Mbytes
Specifies the maximum queue size in megabytes per second. Enter an integer from 0 through
2048.
Modes
Interface configuration mode
Usage Guidelines
Use the no form of this command to remove the packet handling configuration.
Examples
The following example configures the multicast packet handling on the interface for virtual output
queueing.
device# configure terminal
device(config)# interface ethernet 1/2
Syntax
qos rx-queue unicast traffic-class traffic_class min-queue-size
minimum_size max-queue-size maximum_size
no qos rx-queue unicast traffic class number min-queue-size Mbytes max-
queue-size Mbytes
Parameters
traffic class number
Specifies the traffic class on the interface. Enter an integer from 0 to 7.
min-queue-size Mbytes
Specifies the minimum queue size in megabytes per second. Enter an integer from 0 through
1024.
max-queue-size Mbytes
Specifies the maximum queue size in megabytes per second. Enter an integer from 0 through
2048.
Modes
Ethernet interface configuration mode
Examples
The following example configures tan Ethernet interface ingress queue minimum and maximum queue
size by a traffic class. .
device# configure terminal
device(config)# interface ethernet 1/2
device(conf-if-eth-1/2)# qos rx-queue unicast traffic-class 3 min-queue-size 128 max-
queue-size 1024
qos service-policy
Applies a policy map to all inbound traffic.
Syntax
qos service-policy in service_policy_name
no qos service-policy in service_policy_name
Parameters
in
Applies the service policy to inbound traffic.
service_policy_name
The name of the policy map.
Modes
Global configuration mode.
Usage Guidelines
The policy map has been preconfigured.
Examples
This example binds a service policy to inbound traffic at the system level.
qos traffic-class
Applies a QoS default traffic class value to an interface.
Syntax
qos traffic-class default_tc_value
Command Default
No explicit user configured QoS default traffic class priority value is configured.
Parameters
default_tc_value
The assigned traffic class priority value. The traffic class priority values range from 0 through 7.
Modes
Interface configuration mode
Examples
Follow this example to apply a default traffic class value to a specific Ethernet interface:
Follow this example to apply a default traffic class value to a specific port channel interface:
qos traffic-class-cos
Applies a user configured QoS traffic class-to-CoS mutation map to an interface.
Syntax
qos traffic-class-cos tc_cos_map
Command Default
No explicit user configured QoS traffic class-to-CoS mutation maps are applied. The outbound traffic
class equals the inbound traffic class.
Parameters
tc_cos_map
The name of the user configured QoS traffic class-to-CoS mutation map.
Modes
Interface configuration mode.
Usage Guidelines
The mutation maps are preconfigured.
Mutation mapping is a method of modifying a QoS field in all packets on an interface. On ingress,
mutation mapping occurs before traffic classification and all other actions. On egress, mutation
mapping occurs after traffic classification and before all other actions.
Examples
Follow this example to apply a user configured QoS traffic class-to-CoS mutation map to an Ethernet
interface.
Follow this example to apply a user configured QoS traffic class-to-CoS mutation map) to a port
channel interface.
Syntax
qos-mpls map dscp-exp mapname { dscp dscp_value to exp exp_value }
[no] qos-mpls map dscp-exp mapname [ dscp dscp_value to exp exp_value ]
Parameters
mapname
The name of the MPLS QoS DSCP-to-EXP mutation map. The name can be up to 64 characters.
dscp
Specifies that the ingress DSCP value follows.
dscp_value
The ingress DSCP value. The range is from 0 through 63.
exp
Specifies that the egress EXP value follows.
exp_value
The egress EXP value. The range is from 0 through 7.
Modes
Global configuration mode
Usage Guidelines
Creating the map and setting the initial mutation places the device into dscp-exp-mapname
configuration mode where you continue to populate the map using the dscp command.
MAC filter and DSCP marking cannot be configured on the same port.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
Follow this example to create an MPLS QoS DSCP-to-EXP mutation map.
Syntax
qos-mpls map exp-dscp mapname { exp exp_value to dscp dscp_value }
[no] qos-mpls map exp-dscp mapname [ exp exp_value to dscp dscp_value ]
Parameters
mapname
The name of the MPLS QoS EXP-to_DSCP mutation map. The name can be up to 64 characters.
exp
Specifies that the egress EXP value follows.
exp_value
The ingress EXP value. The range is from 0 through 7.
dscp
Specifies that the egress DSCP value follows.
dscp_value
The egress DSCP value. The range is from 0 through 63.
Modes
Global configuration mode
Usage Guidelines
Creating the map and setting the initial mutation places the device into exp-dscp-mapname
configuration mode where you continue to populate the map using the exp command.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
Follow this example to create an MPLS QoS EXP-to-DSCP mutation map.
Syntax
qos-mpls map exp-traffic-class mapname { exp exp_value to traffic-class
traffic_class_value drop-precedence drop_precedence_value }
[no] qos-mpls map exp-traffic-class mapname [ exp exp_value to traffic-
class traffic_class_value drop-precedence drop_precedence_value ]
Parameters
mapname
The name of the MPLS QoS EXP-to-traffic class mutation map. The name can be up to 64
characters.
exp
Specifies that the egress EXP value follows.
exp_value
The ingress EXP value. The range is from 0 through 7.
traffic-class
Specifies that the egress traffic class value follows.
traffic_class_value
The egress traffic class value. The range is from 0 through 63.
drop-precedence
Specifies that the traffic class drop precedence value follows.
drop_precedence_value
The egress traffic class drop precedencevalue. The range is from 0 through 3.
Modes
Global configuration mode
Usage Guidelines
Creating the map and setting the initial mutation places the device into exp-traffic-class-
mapname configuration mode where you continue to populate the map using the exp command.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
Follow this example to create an MPLS QoS EXP-to-traffic class mutation map.
Syntax
qos-mpls map traffic-class-exp mapname { traffic-class
traffic_class_value drop-precedence drop_precedence_value to exp
exp_value }
[no] qos-mpls map traffic-class-exp mapname [ traffic-class
traffic_class_value drop-precedence drop_precedence_value to exp
exp_value ]
Parameters
mapname
The name of the MPLS QoS traffic class-to-EXP mutation map. The name can be up to 64
characters.
traffic-class
Specifies that the ingress traffic class value follows.
traffic_class_value
The ingress traffic class value. The range is from 0 through 63.
drop-precedence
Specifies that the traffic class drop precedence value follows.
drop_precedence_value
The egress traffic class drop precedencevalue. The range is from 0 through 3.
exp
Specifies that the egress EXP value follows.
exp_value
The egress EXP value. The range is from 0 through 7.
Modes
Global configuration mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Creating the map and setting the initial mutation places the device into traffic-class-exp-
mapname configuration mode where you continue to populate the map using the traffic-class
command.
Examples
This example creates create an MPLS QoS traffic class-to-EXP mutation map.
device# configure terminal
device(config)# qos-mpls map traffic-class-exp tcExpMap traffic-class 0 drop-precedence 2
to exp 1
device(traffic-class-exp-tcExpMap)# traffic-class 3 drop-precedence 2 to exp 4
device(traffic-class-exp-tcExpMap)# traffic-class 4 drop-precedence 2 to exp 5
device(traffic-class-exp-tcExpMap)# traffic-class 5 drop-precedence 2 to exp 6
Syntax
qos-mpls map-apply dscp-exp { map_name | all-zero-map | default-map }
{ all }
[no] qos-mpls map-apply dscp-exp
Parameters
map_name
The name of the user-defined map that you are applying.
all-zero-map
Maps the DSCP values to EXP 0.
default-map
Maps the DSCP to EXP values based on the default map.
all
Applies the map globally.
Modes
Global configuration mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
Follow this example to apply a MPLS DSCP to EXP mutation map.
Syntax
qos-mpls map-apply exp-dscp { map_name | all-zero-map | default-map }
{ all }
[no] qos-mpls map-apply exp-dscp
Parameters
map_name
The name of the user-defined map that you are applying.
all-zero-map
Maps the EXP values to DSCP 0.
default-map
The EXP to DSCP value is based on the default map.
all
Applies the map globally.
Modes
Global configuration mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
Follow this example to apply a MPLS EXP to DSCP mutation map.
Syntax
qos-mpls map-apply exp-traffic-class { map_name | all-zero-map | default-
map } { all }
[no] qos-mpls map-apply exp-traffic-class
Parameters
map_name
The name of the user-defined map that you are applying.
all-zero-map
Maps the EXP values to internal traffic class 0 and drop precedence 0.
default-map
Maps the EXP to internal traffic class values and drop precedence based on the default map.
all
Applies the map globally.
Modes
Global configuration mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
Follow this example to apply a MPLS EXP to traffic class mutation map.
Syntax
qos-mpls map-apply traffic-class-exp { map_name | all-zero-map | default-
map } { all }
[no] qos-mpls map-apply traffic-class-exp
Parameters
map_name
The name of the user-defined map that you are applying.
all-zero-map
Maps the nternal traffic class and drop precedence values to EXP 0.
default-map
Maps the nternal traffic class and drop precedence values to EXP based on the default map.
all
Applies the map globally.
Modes
Global configuration mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
Follow this example to apply a MPLS traffic class to EXP mutation map.
qos-ttl-mode
Configures QoS support for MPLS policies and VXLAN Layer 2 gateways, Layer 3 gateways, and Layer 2
and Layer 3 gateway interconnections.
Syntax
qos-ttl-mode [ uniform | pipe ]
no qos-ttl-mode
Parameters
uniform
QoS is supported by the router MPLS policy or VXLAN gateway uniformly. This setting is the
default.
pipe
QoS is supported by the router MPLS policy pipe or VXLAN gateway pipe.
Modes
Router MPLS policy configuration mode
Usage Guidelines
Use the no form of the command to remove the QoS support from the router MPLS policy or VXLAN
gateway.
Note
The gateway must first be configured with the type layer2-extension command for
QoS support on the VXLAN gateway. For example, the following is displayed in the output
when the show overlay-gateway command is entered:
Type Layer2-Extension, Tunnel mode VXLAN
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example shows how to configure uniform QoS support on a VXLAN gateway.
device# configure terminal
device(config)# overlay-gateway gateway_L2
device(config-overlay-gw-gateway_L2)# type layer2-extension
device(config-overlay-gw-gateway_L2)# ip interface loopback 1
device(config-overlay-gw-gateway_L2)# qos-ttl-mode uniform
device(config-overlay-gw-gateway_L2)# map vni auto
device(config-overlay-gw-gateway_L2)# activate
The following example shows how to configure QoS support on a VXLAN pipe.
device# configure terminal
device(config)# overlay-gateway gateway_L2
device(config-overlay-gw-gateway_L2)# type layer2-extension
device(config-overlay-gw-gateway_L2)# ip interface loopback 1
device(config-overlay-gw-gateway_L2)# qos-ttl-mode pipe
device(config-overlay-gw-gateway_L2)# map vni auto
device(config-overlay-gw-gateway_L2)# activate
The following example shows how to configure QoS support on the router MPLS policy pipe.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# qos-ttl-mode pipe
Syntax
qos tx-queue scheduler strict-priority traffic_class dwrr dwrr_weight
[no] qos tx-queue scheduler strict-priority traffic_class dwrr
dwrr_weight
Command Default
The SP value for the egress queue traffic class scheduler is not configured.
Parameters
tarffic_class
There are eight raffic class values:
V Traffic class
al
u
e
0 No strict priority queue.
1 Traffic class 7 strict priority queue.
2 Traffic class 6 through 7 strict priority queues.
3 Traffic class 5 through 7 strict priority queues.
4 Traffic class 4 through 7 strict priority queues.
5 Traffic class 3 through 7 strict priority queues.
6 Traffic class 2 through 7 strict priority queues.
7 Traffic class 1 through 7 strict priority queues.
dwrr dwrr_weight
Configure the DWRR queue weights. There are eight entries for this parameter with each entry
representing a percentage. Tthe total of all the entries cannot exceed 100%. Each entry position
represents a specific traffic class:
Place Assignment
1 Traffic class 0 DWRR weight.
2 Traffic class 1 DWRR weight.
3 Traffic class 2 DWRR weight.
4 Traffic class 3 DWRR weight.
Place Assignment
5 Traffic class 4 DWRR weight.
6 Traffic class 5 DWRR weight.
7 Traffic class 6 DWRR weight.
8 Traffic class 7 DWRR weight.
Modes
Global configuration mode
Usage Guidelines
The no form, of the command removes the SP value for the egress queue traffic class scheduler.
Examples
Use the following command to assign traffic classes 6 through 7 to a SP queue and assign DWRR
weights.
radius-server host
Configures a RADIUS server to connect for external server authentication.
Syntax
radius-server host { ip-address | host-name } [ use-vrf { mgmt-vrf |
default-vrf |vrf-name } ][ auth-port portnum ] [ radsec ] [ timeout
secs ] [ retries num ] [ key shared-secret ] [ protocol { chap | pap
| peap} ] [ encryption-level value-level ]
no radius-server host { ip-address | host-name } [ use-vrf { mgmt-vrf |
default-vrf |vrf-name } ][ auth-port portnum ] [ radsec ] [ timeout
secs ] [ retries num ] [ key shared-secret ] [ protocol { chap | pap
| peap} ] [ encryption-level value-level ]
Command Default
By default, a RADIUS server is not configured.
Parameters
ip-address
Specifies the RADIUS server IP address. Both IPv4 and IPv6 addresses are supported.
host-name
Specifies the host name of the RADIUS server. The maximum supported length for the host
name is 40 characters.
use-vrf
(Optional) Causes communication with the RADIUS server through a specific VRF and enters
configuration mode for RADIUS server communications through that VRF.
mgmt-vrf
Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf-name
Specifies a VRF name.
auth-port portnum
Specifies the port for authentication. The default is UDP port is 1812. The default TCP port (used
for RADIUS over TLS) is 2083.
radsec
Specifies that RADIUS over TLS is to be used instead of RADIUS over UDP.
encryption-levelvalue-level
Designates the encryption level for the shared secret key operation. This operand supports JITC
certification and compliance. The valid values are 0 and 7, with 0 being clear text and 7 being the
most heavily encrypted. The default value is 7.
key shared-secret
Specifies the text string that is used as the shared secret between the device and the RADIUS
server to make the message exchange secure. The key must be between 1 and 40 characters in
length.
In RADIUS over UDP mode, the default key is sharedsecret. In RADIUS over TLS mode, the
default key is radsec, which must not be modified per RFC 6614.
The exclamation mark (!) is supported in RADIUS and TACACS+ servers. You can specify the
password in either double quotes or with the escape character (\), for example "secret!key"
or secret\!key. The only other valid characters are alphanumeric characters (a-z and 0-9)
and underscores. No other special characters are allowed.
protocol {chap | pap | peap}
Specifies the authentication protocol. Options include CHAP, PAP, and PEAP. The default is
CHAP.
retries num
Specifies the number of attempts allowed to connect to a RADIUS server. The default is 5
attempts.
Modes
Global configuration mode
Usage Guidelines
When a RADIUS server with the specified IP address or hostname does not exist, it is added to the
server list. When the RADIUS server already exists, this command modifies the configuration.
Note
When only one RADIUS is configured, you can remove the RADIUS server configuration only
when both login (EXEC) and command accounting are disabled by using, for example, the no
aaa accounting command and when the authentication mode has been set to "non-
radius" with the no aaa authentication login radius command.
If the encryption-level is zero (0) but the key entered is encrypted then the following error
message is displayed: Error: Input key must be plain text when encryption-level
selected is 0.
Examples
This example configures a RADIUS server.
device# configure terminal
device(config)# radius-server host 10.24.65.6
device(config-radius-server-10.24.65.6/mgmt-vrf)#
This example configures a RADIUS server and specifies that communication with the server takes place
through the green-vrf.
device# configure terminal
device(config)# radius-server host 10.24.65.6 use-vrf green-vrf
device(config-radius-server-10.24.65.6/green-vrf)#
raps-default-mac
Sets the default Ring Automatic Protection Switching (R-APS) destination MAC address for Ethernet
Ring Protection (ERP).
Syntax
raps-default-mac
no raps-default-mac
Command Default
The default RAPS destination MAC address is 01:19:A7:00:00:01 for all ring ID and R-APS messages.
Modes
ERP configuration mode
Usage Guidelines
The device appends the number configured by this command to the end of the permanent portion of
the ERP MAC address 01:19:A7:00:00:<01 or ERP ID> in R-APS messages. By default, 01:19:A7:00:00:01
is used as the destination MAC address, which is always used by Version 1 of ITU-T 8032.
Examples
The following example sets a default R-APS destination MAC address.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# raps-default-mac
raps-mel
Configures a Ring Automatic Protection Switching (R-APS) Maintenance Entity Group Level (MEL)
value for Ethernet Ring Protection (ERP).
Syntax
raps-mel mel_value
no raps-mel
Command Default
The default is 7.
Parameters
mel_value
Specifies a R-APS MEL value. Range is from 0 through 7.
Modes
ERP configuration mode
Usage Guidelines
The R-APS MEL value is carried in ERP PDUs.
Examples
The following example configures a nondefault value.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# raps-mel 5
raslog-duration
Configures the interval between RASLog messages that are sent when a port is disabled by the loop
detection (LD) protocol.
Syntax
raslog-duration {minutes }
no raslog-duration
Command Default
See the Usage Guidelines.
Parameters
minutes
Message interval in minutes. Range is from 10 through 1440. The default is 10.
Modes
Protocol Loop Detection configuration mode
Usage Guidelines
Use the no form of this command to revert to the default interval.
Examples
To specify a RASLog message interval of 20 minutes:
device# configure terminal
device(config)# loop-detection
device(config-loop-detect)# raslog-duration
rd (EVPN VLAN/BD)
Configures a Virtual Private Network (VPN) route distinguisher for a VLAN/bridge domain (BD) in an
Ethernet VPN (EVPN) default instance.
Syntax
rd { admin-value:arbitrary-value | IP-address:arbitrary-value }
Parameters
admin-value
The administrative number assigned to the route. This can be a local ASN number or an IP
address. The ASN number can be either a 2-byte number (from 0 through 65535) or a 4-byte
number (from 0 through 4294967295).
arbitrary-value
An arbitrary number you choose. The range of valid values is from 0 through 65535 if the ASN is
is an IP address or a 2 byte ASN. The range is 0 through 4294967295 if the ASN is a 4 byte ASN.
IP-address
An IPv4 or IPv6 address.
Modes
EPVN VLAN/BD configuration mode
Examples
The following example configures an RD and assigns the local ASN number 200:1.
rd auto (EVPN)
Enables auto-generation of a route distinguisher (RD) for an Ethernet Virtual Private Network (EVPN)
default instance.
Syntax
rd auto
no rd auto
Command Default
Disabled.
Modes
EVPN configuration mode
Usage Guidelines
Use the no form of this command to disable autogeneration of an RD.
Examples
The following example enables autogeneration of an RD on an EVPN default instance.
device# configure terminal
device(config)# evpn
device(config-evpn-default)# rd auto
reconnect-time
Specifies the amount of time that a graceful restart (GR) neighbor must wait for the LDP session to be
reestablished.
Syntax
reconnect-time seconds
no reconnect-time seconds
Command Default
The default reconnect time is 120 seconds.
Parameters
seconds
Specifies the amount of time in seconds that a GR neighbor must wait for the LDP session to be
reestablished. This value is advertised to the neighbor using the FT Reconnect Timeout field in
the FT Session TLV. Enter a integer from 60 to 300. The default setting is 120.
Modes
MPLS LDP GR configuration mode
Usage Guidelines
The no form of the command resets the default time of 120 seconds.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the LDP GR timer to 180 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# graceful-restart
device(config-router-mpls-ldp-gr)# reconnect-time 180
record
The user can configure the record route option using the record command.
Syntax
record { enable | disable }
Command Default
The record route option is enabled by default.
Parameters
enable
Enables the record route option
disable
Disables the record route option.
Modes
MPLS router Bypass LSP configuration mode.
Usage Guidelines
When enabled, the RSVP session messages of the bypass LSP records the bypass LSP actual path.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables the record route option for bypass LSP my-bypass-lsp.
device>configure
device(config)# router mpls
device(config-router-mpls)# bypass-lsp my-bypass-lsp
device(config-router-mpls-bypass-lsp-my-bypass-lsp)# record enable
record-route
Use the record-route command's enable or disable options to set the record route option for the
dynamic bypass LSPs to be created for the MPLS protected interface.
Syntax
record-route { disable | enable }
Command Default
Record route is enabled by default.
Parameters
disable
Disable the record-route command.
enable
Enables the record-route command.
Modes
MPLS router MPLS interface dynamic bypass configuration mode (config-router-mpls-if-ethernet-
slot/port-dynamic-bypass).
Usage Guidelines
Based on the value of the parameter, dynamic bypass LSPs create with their record-route option
enabled or disabled.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables record-route on the dynamic bypass MPLS Ethernet interface 0/8 .
device>configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# record-route enable
recovery-time
Specifies the amount of time that this device retains its MPLS forwarding state across LDP graceful
restart (GR).
Syntax
recovery-time seconds
no recovery-time seconds
Command Default
The default recovery time is 120 seconds.
Parameters
seconds
Specifies the amount of time in seconds that this router retains its MPLS forwarding state across
restart. This value is advertised to the neighbor using the Recovery Time field in the FT Session
TLV. Enter a integer from 60 to 3600.
Modes
MPLS LDP GR configuration mode
Usage Guidelines
The recovery time must be chosen accordingly taking into account the time it takes for RTM to
recompute the routes and the number of Layer 3 FECs that need to be recovered as part of the LDP GR
recovery. This is applicable to GR processing on ingress as well as transit LSRs.
The no form of the command resets the default time of 120 seconds.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the LDP GR timer to 240 seconds.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# graceful-restart
device(config-router-mpls-ldp-gr)# recovery-time 240
redistribute
Configures the device to redistribute IPv4 and IPv6 routes from one routing domain to another.
Syntax
redistribute isis [ level-1 | level-1-2 | level-2 | metric num | route-
map string ]
redistribute isis { level-1 into level-2 } [ prefix-list name ]
redistribute isis { level-2 into level-1 } [ prefix-list name ]
redistribute ospf [ match { external1 | external2 | internal } | metric
num | metric-type { type1 | type2 } | route-map string ]
redistribute { source-protocol } [ metric num | metric-type { type1 |
type2 } | route-map string ]
redistribute { source-protocol } [ level-1 | level-1-2 | level-2 | metric
num | metric-type { type1 | type2 } | route-map string ]
no redistribute isis [ level-1 | level-1-2 | level-2 metric num | route-
map string ]
no redistribute isis { level-1 into level-2 } [ prefix-list name ]
no redistribute isis { level-2 into level-1 } [ prefix-list name ]
no redistribute ospf [ match { external1 | external2 | internal } |
metric num | metric-type { type1 | type2 } | route-map string ]
no redistribute { source-protocol } [ metric num | metric-type { type1 |
type2 } | route-map string ]
Command Default
The device does not redistribute routing information.
Parameters
isis
Specifies the IS-IS protocol.
level-1
Specifies L1 LSP, L1 CSNP, and LI PSNP packets.
level-1-2
Specifies L1 LSP, L1 CSNP, and LI PSNP packets and L2 LSP, L2 CSNP, and L2 PSNP packets.
level-2
Specifies L2 LSP, L2 CSNP, and L2 PSNP packets.
metric num
Specifies a metric for redistributed routes. Valid values range from 1 through 65535 in OSPFv2
and OSPFv3 configuration mode. Valid values range from 1 through 4261412863 in ISIS address-
family IPv4/IPv6 unicast configuration mode and BGP address-family IPv4/IPv6 unicast
configuration mode.
route-map string
Specifies a route map to be consulted before a route is added to the routing table.
level-1 into level-2
Redistributes Level 1 routes into Level 2.
level-2 into level-1
Redistributes Level 2 routes into Level 1.
prefix-list name
Specifies a prefix-list.
ospf
Specifies the OSPF protocol.
match
Specifies the type of route.
external1
Specifies OSPF Type 1 external routes.
external2
Specifies OSPF Type 2 external routes.
internal
Specifies OSPF internal routes.
metric-type
Specifies the external link type associated with the default route advertised into the OSPF
routing domain.
type1
Specifies a type 1 external route.
type2
Specifies a type 2 external route.
source-protocol
Specifies the source protocol from which routes are being redistributed. It can be one of the
following keywords: bgp, connected, or static.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
IS-IS is supported on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Routes can be filtered by means of an associated route map before they are distributed.
The metric-type { type1 | type2 } option is only available in OSPFv3 router, OSPFv3 router
VRF, and ISIS address-family /IPv4/IPv6 unicast configuration mode.
The match, metric, and metric-type options are not available in OSPF VRF configuration mode.
Note
The default-metric command does not apply to the redistribution of directly connected
routes. Use a route map to change the default metric for directly connected routes.
Examples
The following example redistributes IS-IS routes, specifying level 1 packets, in BGP address-family IPv4
unicast configuration mode.
The following example redistributes all IPv4 IS-IS routes from Level 2 into Level 1.
The following example redistributes OSPF external type 1 routes with a metric of 200 in BGP address-
family IPv4 unicast configuration mode.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-ipv4u)# redistribute ospf match external1 metric 200
The following example redistributes OSPFv3 external type 2 routes in BGP address-family IPv6 unicast
configuration mode.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv6 unicast
device(config-bgp-ipv6u)# redistribute ospf match external2
The following example redistributes static routes into BGP4 and specifies a metric of 200.
device# configure terminal
device(config)# router bgp
device(config-bgp-router)# address-family ipv4 unicast
device(config-bgp-ipv4u)# redistribute static metric 200
The following example redistributes BGP routes and specifies that route-map "rm7" be consulted in
OSPF VRF configuration mode.
device# configure terminal
device(config)# router ospf
device(config-router-ospf-vrf-default-vrf)# redistribute bgp route-map rm7
The following example redistributes OSPF routes and specifies a type1 external route in OSPFv3 VRF
configuration mode.
device# configure terminal
device(config)# ipv6 router ospf
device(config-ipv6-router-ospf-vrf-default-vrf)# redistribute ospf metric-type type1
redundant-management enable
Enables or disables Redundant Management Interface feature on the device.
Syntax
redundant-management enable
[no] redundant-management enable
Command Default
Redundant Management Interface is disabled by default and need to be configured and enabled on the
interface that is selected as being the redundant management interface. Only one front panel user port
can be used as the redundant management interface.
Parameters
enabled
Enables this interface as the Redundant Management Interface.
Modes
Interface Ethernet
Usage Guidelines
Uses Linux bonding feature.
Any front panel interface on the device can be made the standby redundant management interface.
On breakout boards, if used with Mellanox Adaptor, Redundant Management Interface can only be
enabled on the first port.
Examples
The following example configures the interface eth 0/15 as the Redundant Management Interface.
device(config)# interface ethernet 0/15
device(conf-if-eth-0/15)# redundant-management enable
device(conf-if-eth-0/15)# no shut
device(conf-if-eth-0/15)# exit
refresh-reduction
When the user enables either of the refresh reduction extensions on an interface, outgoing RSVP
packets sent on that interface sets the refresh reduction capability bit in the common RSVP header to
indicate that the device is capable of receiving and processing refresh reduction messages and related
objects.
Syntax
refresh-reduction bundle-message [ bundle-send-delay milliseconds ] |
summary-refresh
no refresh-reduction bundle-message [ bundle-send-delay milliseconds ] |
summary-refresh
Command Default
The RSVP bundle messages on the interface are disabled, by default.
Parameters
bundle-message
bundle-send-delay milliseconds
Specifies the bundle send delay value in milliseconds. the range is 20-1000 milliseconds, with a
default of 40 milliseconds.
summary-refresh
Activates the refresh-reduction summary refresh.
Modes
MPLS RSVP mode (config-router-mpls-rsvp).
Usage Guidelines
Summary refresh is a more effective tool for RSVP refresh message overhead reduction.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following commands enable RSVP bundle messages on interface 0/13 with a bundle-send-
delay of 20 milliseconds.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/13
device(config-router-mpls-eth-0/13)# rsvp
device(config-router-mpls-eth-0/13-rsvp)# refresh-reduction bundle-message bundle-send-
delay 20
region
Assigns a name to a Multiple Spanning Tree Protocol (MSTP) region.
Syntax
region region-name
no region
Parameters
region-name
Assigns a name to an MSTP region.
Modes
Spanning tree MSTP configuration mode
Usage Guidelines
The region-name string must be between 1 and 32 ASCII characters in length, and is case-sensitive.
Examples
To assign a name to an MSTP region named extreme1:
registrar-server
Configures the various settings for accessing the remote Keylime Remote Attestation server.
Syntax
registrar-server ip-address use-vrf vrf-name
Parameters
ip-address
IP address of the remote Keylime Remote Attestation server. IPv4 or IPv6 addresses can be used.
use-vrf vrf-name
The VRF on which the remote Remote Attestation server can be accessed.
Modes
Remote Attestation mode.
Usage Guidelines
If your Remote Attestation server is listening on a non standard port, configure the port using the
registrar-port command. The standard port for the Keylime server is 8890.
Examples
The following example configures the connection details of the Keylime Remote Attestation server. The
IP address of the server is 10.1.1.10 and it can be accessed through the default VRF.
SLX (config-remote-attestation)# registrar-server 10.1.1.10 user-vrf default-vrf
SLX (config-remote-attestation)#
Platform Availability
This command and mode is only available on the Extreme 8720 and Extreme 8520 devices.
registrar-port
Configures the port on which the Keylime Remote Attestation server is listening for incoming
connections.
Syntax
registrar-port port
Command Default
The default port value is 8890.
Parameters
port
Configures the port on which the Keylime Remote Attestation server is listening for incoming
connections.
Modes
Registrar Server VRF Mode.
Examples
This example configures default port as the port on which the Remote Attestation server is listening for
connections.
SLX (config)# remote-attestation
SLX (config-remote-attestation)# registrar-server 10.1.1.10 use-vrf default-vrf
SLX (config-remote-attestation-10.1.1.10/default-vrf)# registrar-port
SLX (config-remote-attestation-10.1.1.10/default-vrf)# exit
SLX (config-remote-attestation)# exit
SLX (config)#
Platform Availability
This command and mode is only available on the Extreme 8720 and Extreme 8520 devices.
reliable-messaging
When RSVP reliable messaging is enabled on an interface of the SLX-OSdevice, RSVP trigger messages
sent out on that interface includes a message ID and a request for acknowledgment from the RSVP
neighbor.
Syntax
reliable-messaging [ rapid-retrans-decay percent ] | [ rapid-retrans-
interval milliseconds ] | [ rapid-retry-limit number ]
no reliable-messaging [ rapid-retrans-decay percent ] | [ rapid-retrans-
interval milliseconds ] | [ rapid-retry-limit number ]
Command Default
The command is disabled, by default.
Parameters
rapid-retrans-decay percent
Specifies the percentage increase in the rapid transmission interval for each consecutive
unacknowledged RSVP message. The range is from 0 - 100, with a default of 100.
rapid-retrans-interval milliseconds
Specifies the interval, in milliseconds, for an unacknowledged message to be resent. The range is
from 100-30000 milliseconds, with a default of 2000 milliseconds.
rapid-retry-limit number
Specifies the maximum number of retries for an unacknowledged message. The range is 1-16,
with a default value of 5.
Modes
MPLS interface RSVP mode (config-router-mpls-eth-x/x).
Usage Guidelines
When acknowledgment is not received, the trigger message is re-transmitted using the retransmission
parameters configured on the interface.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables RSVP reliable messaging on MPLS interface 0/13 .
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/13
device(config-router-mpls-eth-0/13)# rsvp
device(config-router-mpls-eth-0/13-rsvp)# reliable-messaging
The following example configures the rapid-retrans-decay option to 1 percent, the rapid-
retrans-interval option to 100 milliseconds, and the rapid-retry-limit option to 1 try.
device# configure
device(config)# router-mpls
device(config-router-mpls)# rsvp
device(config-router-mpls-rsvp)# reliable-messaging rapid-retrans-decay 1 rapid-retrans-
interval 100 rapid-retry-limit 1
reload
Reboots the device.
Syntax
reload [ system ]
Parameters
system
Reboots the device.
Modes
Privileged EXEC mode
Usage Guidelines
All reboot operations are disruptive, and the commands prompt for confirmation before executing.
When you reboot a device, all traffic to and from it stops. All ports on that device remain inactive until
the device comes back online.
Note
Do not use the reload command without the system parameter.
Examples
The following example performs a reboot of the device.
device# reload system
reload-delay
Sets the wait time before allowing traffic to be routed through interfaces.
Syntax
reload-delay delay-time
no reload-delay
Command Default
No global reload-delay setting is configured.
Parameters
delay-time
Specifies the length of time before allowing traffic to be routed through an interface. The range
is 1 though 3600 seconds.
Modes
Privileged EXEC mode
Usage Guidelines
If a node is reloaded and the traffic flow is directed to an interface before it is operational, the traffic is
dropped. Setting the reload-delay timer allows the interface to become fully operational before traffic is
routed to it.
Use reload-delay to set the delay time for all interfaces where the feature is enabled, but no delay
time is configured. Setting the global reload-delay time is optional, but useful when there are many
interfaces to be configured with the same delay-time.
By default, interface level settings override global settings. If there is no setting at the interface level, the
global setting is used. If no delay-time is set either on the interface or globally, the configuration is
ignored.
Examples
The following example configures a global reload-delay time of 240 seconds.
device(config)# reload-delay 240
reload-delay enable
Enables reload delay on a physical, port-channel, or loopback interface.
Syntax
Command Default
No interface level reload-delay is enabled.
Parameters
delay-time
(Optional) Set the length of time before allowing traffic to be routed through an interface. The
range is 1 through 3600 seconds.
Modes
Privileged EXEC mode
Usage Guidelines
If a node is reloaded and the traffic flow is directed to an interface before it is operational, the traffic is
dropped. Setting the reload-delay timer allows the interface to become fully operational before traffic is
routed to it.
Use the reload-delay enable command to enable reload-delay on an interface. This is a required
configuration; if reload-delay enable is not set at the interface, a configuration error is raised. By
default, interface level settings override global settings.
The reload-delay time on an interface is optional. If there is no delay-time set at the interface level, the
global setting is used. If no delay-time is set either on the interface or globally, the configuration is
ignored.
Examples
The following example configures a reload-delay time of 120 seconds on a port-channel.
device(config)# interface port-channel 10
device(config-Port-channel)# reload-delay enable 120
remote-mep
Associates an action profile to a RMEP for a scheduled Two-Way ETH-SLM or Two-Way ETH-DM.
Syntax
remote-mep rmep-id action-profile profile-name
no remote-mep
Parameters:
rmep-id
Specifies the RMEP ID.
action-profile
Specifies the action profile.
profile-name
Specifies the profile name.
Modes
config-cfm-md-ma-mep configuration mode
Usage Guidelines
Use the no form of the command delete the RMEP action profile associations.
Examples
This example shows how to associate an action profile to a RMEP for a scheduled Two-Way ETH-SLM.
device# configure terminal
device(config)# protocol cfm
device(config-cfm)# domain-name md1 level 4
device(config-cfm-md-md1)# ma-name ma1 id 1 vlan-id 30 priority 3
device(config-cfm-md-ma-ma1)# mep 1 down Ethernet 1/2
device(config-cfm-md-ma-mep-1)# remote-mep 2
device(config-cfm-md-ma-mep-1)# remote-mep 2 action-profile my_action_profile
rename
Renames a file in the device flash memory.
Syntax
rename current_name new_name
Parameters
current_name
Specifies the file name you want to change.
new_name
Specifies the new file name.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
System configuration files cannot be renamed. If you try to rename a system file, a warning message is
displayed.
Examples
The following example renames a file in the flash memory.
device# rename myconfig myconfig_20101010
reoptimize-timer
The user can set a timer to optimize a specific LSP path on a periodic basis.
Syntax
reoptimize-timer { seconds }
no reoptimize-timer { seconds }
Command Default
The re-optimize timer is disabled, by default. Not configurable for a non-adaptive bypass LSP.
Parameters
seconds
Specifies the length, in seconds, from the beginning of one re-optimization attempt to the
beginning of the next attempt. The range is 300-65535 seconds.
Modes
MPLS LSP configuration mode (config-router-mpls-lsp-lsp_name ).
Usage Guidelines
Until a commit is issued the re-optimize timer is disabled.
Configuring a re-optimization timer does not interfere with running the manual reoptimize
command.
When upgrading software, the configured adaptive LSPs are initialized with the no re-optimization
timer.
Use the reoptimize-timer command to configure a re-optimization timer for dynamic bypasses.
Dynamic bypass LSP re-optimization is enabled when the re-optimization value is set to a non-zero
value, and the timer is set for the specified amount of seconds.
The reoptimize-timer value can also be configurable on MPLS interface mode. The global set value
is applicable to all dynamic bypass LSPs for which the corresponding interface level re-optimization
timer value is not set.
Use the reoptimize-timer command to configure a re-optimization timer value for all the dynamic
bypass LSPs that are being created corresponding to a protected interface. When configured, this value
overrides the global mode reoptimize-timer configured value.
When a dynamic bypass is non-adaptive, the reoptimize-timer is not considered for the dynamic
bypass LSP.
The no form of the command removes the reoptimize-timer and sets it to the value set in the
dynamic bypass global mode.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
In the following example, the re-optimize time is configured to 1000 seconds, which specifies the
number of seconds from the beginning of one re-optimization attempt to the beginning of the next
attempt.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp to20
device(config-router-mpls-lsp-to20)# reoptimize-timer 1000
device(config-router-mpls-lsp-to20)# commit
The following example configures the reoptimize-timer to 300 seconds under the MPLS router
dynamic bypass configuration mode.
device>configure
device(config)# router-mpls
device(config-router-mpls)# dynamic-bypass
device(config-router-mpls-dynamic-bypass)# reoptimize-timer 360
The following example configures the reoptimize-timer to 360 seconds for dynamic bypass MPLS
ethernet interface 2/8.
device>configure
device(config)# router-mpls
device(config-router-mpls)# mpls-interface ethernet 0/8
device(config-router-mpls-if-ethernet-0/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-0/8-dynamic-bypass)# reoptimize-timer 360
resequence access-list
Reassigns sequence numbers to entries of an existing MAC, IPv4, or IPv6 access list.
Syntax
resequence access-list { ip | ipv6 | mac } name seq_num increment
Parameters
ip | ipv6 | mac
Specifies the Layer 2 or Layer 3 ACL bound to an interface.
name
Specifies the name of a standard or an extended ACL. A maximum of 63 characters is allowed.
seq_num
Specifies the starting sequence number in the ACL. Valid values range from 1 through 65535.
increment
Specifies a value to increment the sequence number between rules. Valid values range from 1
through 65534.
Modes
Privileged EXEC mode
Usage Guidelines
Reordering the sequence numbers is useful when you need to insert rules into an existing ACL and
there are not enough sequence numbers available. When all sequence numbers between rules are
exhausted, this feature allows the reassigning of new sequence numbers to entries of an existing access
list.
Examples
The following example reorders the rules in a MAC ACL.
device# show running-config mac access-list test
!
mac access-list standard test
seq 1 permit 0011.2222.3333
seq 2 permit 0011.2222.4444
seq 3 permit 0011.2222.5555
seq 4 deny 0011.2222.6666
!
device# resequence access-list mac test 10 10
reservable-bandwidth
The reservable-bandwidth command is configurable on an MPLS-enabled interface at any time.
The configuration of the command takes effect immediately upon preemption of the LSP.
Syntax
reservable-bandwidth { decimal | [ percentage decimal ] }
no reservable-bandwidth { decimal | [ percentage decimal ] }
Command Default
The default value is the total physical bandwidth of the interface.
Parameters
decimal
The decimal variable specifies a value from 0 through 2,000,000,000 in kbps.
percentage decimal
The percentage decimal parameters specify a value from 0 through 100. The percentage value of
100 specifies that the entire interface bandwidth can be used by MPLS LSPs, when needed.
Modes
MPLS interface mode (config-router-mpls-if-eth).
Usage Guidelines
The no form of the command sets the maximum reservable bandwidth back to the default value.
When the maximum reservable bandwidth is configured as a percentage value for LAGs and VE
interfaces, and ports go down, or new ports are added to the interface, the reservable bandwidth is
recalculated as a percentage of the newly available bandwidth for that interface.
When the maximum reservable bandwidth is configured as either an absolute value, or a percentage
value, the value is recalculated and updated to the latest value.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The example below shows the configuration of the maximum reservable bandwidth for MPLS LSPs with
an absolute value of 10000 kbps.
device# configure
device(config)# router mpls
The following example configures the maximum reservable bandwidth as a percentage (80%) of the
total interface bandwidth for the MPLS LSPs on the interface.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/1
device(config-router-mpls-if-eth-0/1)# reservable-bandwidth percentage 80
The following example shows when the maximum reservable bandwidth is changed from an absolute
value to a percentage value, and vice versa, the following advisory message displays on the console to
indicate the configuration change.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/1
device(config-router-mpls-if-eth-0/1)# reservable-bandwidth percentage 40
Maximum reservable bandwidth is changed from 30 kbps to 40%
The following example shows using the no form of the command to set the maximum reservable
bandwidth back to the default value (the total physical bandwidth of the interface) when using the
absolute value or percentage value.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/1
device(config-router-mpls-if-eth-0/1)# no reservable-bandwidth percentage 80
resilient-hash
Resilient Hashing is a feature that ensures that there is minimal disruption in traffic flow when there is a
disruption due to a link failure or a link addition. Resilient Hashing is supported for L3 traffic routed
using BGP (support for both IPv4 and IPv6 traffic) and Static Routes. The resilient-hash is used to
enable and disable this feature as well as configuring the maximum path value.
Syntax
resilient-hash ecmp enable
resilient-hash max-path [ 8 | 16 | 64 ]
no resilient-hash ecmp enable
no resilient-hash max-path
Command Default
The default value for max-path is eight (8).
Parameters
ecmp enable
Enables or disables Resilient Hashing.
max-path [ 8 | 16 | 64 ]
Sets the maximum path value for ECMP group for this VRF.
Modes
Global configuration and VRF configuration modes
Warning
Enabling or disabling Resilient Hashing or making changes to the max-path configuration
value will cause traffic disruption for the corresponding VRF. This is by design. This is because,
by design, routes and next-hops are re-downloaded to both the software and hardware
routing tables for programming Special Attributes.
BFD sessions in unrelated VRFs are not affected. Additionally, when the device boots up,
Resilient Hashing configuration replay will not cause BFD session flap.
Examples
The following example enables Resilient Hashing at a global level and sets the max-path value to 16.
The show running-config resilient-hash command is used to verify the configuration.
SLX # conf term
SLX (config)#
SLX (config)# resilient-hash ecmp enable
SLX (config)# resilient-hash max-path 16
SLX (config)#
SLX (config)#
The following example enables Resilient Hashing at a VRF level and sets the max-path value to 64.
The show running-config vrf <vrf-name> command is used to verify the configuration.
SLX # conf term
SLX (config)#
SLX (config)# vrf vrf2
SLX (config-vrf-vrf2)#
SLX (config-vrf-vrf2)# resilient-hash ecmp enable
SLX (config-vrf-vrf2)# resilient-hash max-path 64
SLX (config-vrf-vrf2)# do show running-config vrf vrf2
vrf vrf2
resilient-hash ecmp enable
resilient-hash max-path 64
address-family ipv4 unicast
!
address-family ipv6 unicast
!
!
SLX (config-vrf-vrf2)#
Syntax
retain route-target all
no retain route-target all
Command Default
This feature is disabled.
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
The no form of the command disables the retaining of all RTs.
Examples
The following example configures a RR to accept all RTs.
retransmit-interval
Sets the time the device waits before it retransmits Link State PDUs (LSPs).
Syntax
retransmit-interval interval
no retransmit-interval interval
Command Default
The default retransmission interval is 5 seconds.
Parameters
secs
Specifies the retransmission interval in seconds. Valid values range from 1 through 65535
seconds. The default is 5 seconds.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example changes the retransmission interval to 7 seconds.
device# configure terminal
device(config)# router isis
device(config-isis-router)# retransmit-interval 7
retries
Configures the number of retries allowed to establish a connection with the Remote Authentication
Dial-In User Service (RADIUS) server.
Syntax
retries num
no retries
Command Default
The number of retries allowed is 5.
Parameters
num
Specifies the number of retries allowed to connect to a RADIUS server. The range is from 0
through 100. The default value is 5.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the command default value.
Examples
The following example shows how to set the number of retries allowed (to establish a connection with
the RADIUS server) to 10.
retry-limit
Configures a limit on the number of times the ingress LER tries to connect to the egress LER in a
signaled LSP.
Syntax
retry-limit number
no retry-limit
Command Default
The command is disabled, by default.
Parameters
number
Specifies a limit on the number of LSP connection attempts.
Modes
MPLS policy mode.
Usage Guidelines
The no form of the command disables the configuration.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
In the following example, when the LSP needs to be established again, the ingress LER makes 20
attempts to establish a connection to the egress LER.
device # configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# retry-limit 20
retry-time
Configures the amount of time the ingress LER waits between connection attempts.
Syntax
retry-time seconds
no retry-time
Command Default
The command is disabled, by default.
Parameters
seconds
Specifies the LSP retry time in seconds. The default is 30 seconds.
Modes
MPLS policy mode
Usage Guidelines
When a signaled LSP is enabled, the ingress LER attempts to connect to the egress LER over the
primary path specified in the LSPs configuration. When the connection is not successful, by default the
ingress LER waits 30 seconds before attempting the connection again.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the retry time to 45 seconds.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# retry-time 45
reverse-metric
Configures the reverse metric value at the Intermediate System-to-Intermediate System (IS-IS) router
level.
Syntax
reverse-metric [ value ] [ te-def-metric ] [ whole-lan ]
reverse-metric tlv-type [ value ]
no reverse-metric [ value ] [ te-def-metric ] [ whole-lan ]
no reverse-metric tlv-type [ value ]
Command Default
The reverse-metric command is disabled by default.
Parameters
reverse-metric
Specifies the reverse metric parameter at the IS-IS router level.
value
Specifies the reverse metric value in metric style. The metric style consists of narrow or wide
style. The narrow metric range is from 1 through 63. The wide metric range is from 1 through
16777215. The default value is 16777214 irrespective of the metric style configured.
te-def-metric
Specifies that the device sends a traffic engineering (TE) default metric sub-type-length-value
(TLV) within the reverse-metric TLV.
whole-lan
Specifies that the configured reverse metric value affects the entire LAN.
tlv-type value
Specifies the TLV type for the reverse metric value. The default value is 254.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
If the reverse-metric value is configured, the local LSP is updated with the sum of the default metric and
the reverse metric value. When the IS-IS neighbor device receives the reverse metric value through the
IS hello, the neighbor router updates the cost to reach the original IS-IS router with the sum of default
metric and the reverse metric value.
The whole-lan option only takes effect on the multi-access LAN. IS-IS point-to-point interfaces are
not affected when the whole-lan option is used.
The no form of the command specified with the configured value resets the metric value to the default
value of 16777214. The no reverse-metric command removes the entire reverse metric
configuration.
Examples
The following example changes the reverse metric value for the entire LAN to 50.
device# configure terminal
device(config)# router isis
device(config-isis-router)# reverse-metric 50 whole-lan
The following example configures the reverse metric TLV type in the range of unassigned IS-IS TLV
values.
device# configure terminal
device(config)# router isis
device(config-isis-router)# reverse-metric tlv-type 230
revert-timer
The path selection revert timer provides an option to stabilize a path before traffic is switched to it.
Without a configured path selection revert timer, the router switches between a primary and secondary
path immediately after the current working path goes down.
Syntax
revert-timer timer_value
no revert-timer
Command Default
There is no revert-timer in the default command mode.
Parameters
timer_value
The number of seconds that the router waits after the primary or selected path comes up before
traffic reverts to that path. The range is 1- 65,535 seconds.
Modes
MPLS LSP configuration mode (config-router-mpls-lsp-lsp_name).
Usage Guidelines
The revert-timer command has no effect on the unconditional select mode. Traffic is
unconditionally switched to the user selected path and stays on it.
The path stability test used with the revert timer is based on the uptime of the latest instance of the
path. This value can be different when the selected path has gone through a "make-before-break"
procedure.
For an LSP going through re-optimization, the new LSP does not carry traffic until the revert timer
expires.
When a user changes the revert timer, the basis of counting is the uptime of the path and is
independent of the sequence or combination of configurations.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the revert-timer to 10 seconds.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp samplelsp
device(config-router-mpls-lsp-samplelsp)# revert-timer 10
revertive global
The revertive mode global command can be executed only on LSPs with FRR and adaptive enabled.
Syntax
revertive global [ disable | enable ]
no revertive mode global
Command Default
Global revertiveness is enabled by default for LSPs with FRR and adaptive enabled.
Parameters
disable
Disables global revertiveness.
enable
Enables global revertiveness.
Modes
MPLS LSP Fast Reroute.
Usage Guidelines
The no option disables global revertiveness on an LSP.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables global revertiveness on LSP t1.
device# config
device(config)# router mpls
device(config-router-mpls)# lsp t1
device(config-router-mpls-lsp-t1)# adaptive
device(config-router-mpls-lsp-t1)# frr
device(config-router-mpls-lsp-t1-frr)# revertive global enable
The following example changes the FRR bandwidth for an adaptive LSP.
device(config)#
device(config)# router mpls
device(config-router-mpls)# lsp t1
device(config-router-mpls-lsp-t1)# frr
device(config-router-mpls-lsp-t1-frr)# bandwidth 1000
device(config-router-mpls-lsp-t1-frr)# exit
device(config-router-mpls-lsp-t1)# commit
The following example show how global revertiveness is enabled by default in FRR mode for an
adaptive LSP.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# retry-limit 20
device(config-router-mpls-policy)# exit
device(config-router-mpls)# lsp t1
device(config-router-mpls-lsp-t1)# adaptive
device(config-router-mpls-lsp-t1)# frr
device(config-router-mpls-lsp-t1-frr)# revertive mode global
device(config-router-mpls-lsp-t1-frr)# revertive holdtime 20
device(config-router-mpls-lsp-t1-frr)# exit
device(config-router-mpls-lsp-t1)# commit
device(config-router-mpls-lsp-t1)#
revertive hold-time
Specifies the time, in seconds, the LSP holds before attempting a new path on the FRR LSP.
Syntax
revertive holdtime value
no revertive holdtime
Command Default
The default is five seconds.
Parameters
value
Specifies the hold time value in seconds. The hold-time ist he time between the primary LSP
failure and the trigger of new instanceof LSP by global revertiveness. The range is one through
60 seconds.
Modes
MPLS LSP fast reroute mode (config-router-mpls-lsp-lsp_name-frr).
Usage Guidelines
The no form of the command removes the revertive hold time.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the revertive hold time to 20 seconds.
device# configure
device(Config)# router mpls
device(config-router-mpls)# lsp t1
device(config-router-mpls-lsp-t1)# adaptive
device(config-router-mpls-lsp-t1)# frr
device(config-router-mpls-lsp-t1-frr)# revertive mode global
device(config-router-mpls-lsp-t1-frr)# revertive holdtime 20
revision
Assigns a version number to the Multiple Spanning Tree Protocol (MSTP) configuration.
Syntax
revision number
no revision
Command Default
The default is 0.
Parameters
number
Specifies the revision or version number of the MSTP region. Valid values range from 0 through
255.
Modes
Spanning tree MSTP configuration mode
Usage Guidelines
The no form of the command resets the default value of 0.
Examples
This example assigns a configuration revision of 1.
device# configure terminal
device(config)# protocol spanning-tree mstp
device(conf-mstp)# revision 1
rfc1583-compatibility (OSPF)
Configures compatibility with RFC 1583.
Syntax
rfc1583-compatibility
no rfc1583-compatibility
Command Default
OSPF is compatible with RFC 1583 (OSPFv2).
Modes
OSPF router configuration mode
Usage Guidelines
OSPF is compatible with RFC 1583 (OSPFv2) and maintains a single best route to an autonomous
system (AS) boundary router in the OSPF routing table. Disabling this compatibility causes the OSPF
routing table to maintain multiple intra-AS paths, which helps prevent routing loops.
Examples
The following example disables compatibility with RFC 1583.
rib-route-limit
Limits the maximum number of BGP Routing Information Base (RIB) routes that can be installed in the
Routing Table Manager (RTM).
Syntax
rib-route-limit num
no rib-route-limit
Command Default
No maximum number of RIB routes is set.
Parameters
num
Decimal value for the maximum number of RIB routes to be installed in the RTM. Valid values
range from 1 through 4294967295.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
This command controls the number of routes installed by BGP, irrespective of whether those BGP routes
are the preferred routes in the system. BGP locally tracks the number of routes installed and the number
of routes withdrawn from RIB. If the total number of routes installed exceeds the value specified by
num, routes will not be installed.
Examples
The following example configures the device to limit the maximum number of BGP4 RIB routes that can
be installed in the RTM.
The following example configures the device to limit the maximum number of BGP4+ RIB routes that
can be installed in the RTM.
right-interface vlan
Configures an Ethernet Ring Protection (ERP) right interface.
Syntax
right-interface vlan vlan_id { ethernet slot/port | port-channel number }
no right-interface vlan vlan_id { ethernet slot/port | port-channel
number }
Command Default
No ERP right interface is configured by default.
Parameters
vlan_id
Specifies the VLAN ID of the ERP right ring interface. Range is from 1 through 4090.
ethernet slot/port
Specifies an Ethernet interface.
port-channel number
Specifies a port-channel.
Modes
ERP configuration mode
Usage Guidelines
Each Ethernet Ring Node (ERN) in a major ring must have explicitly defined left and right interfaces so
that ERP can function properly. ERNs in a sub-ring must have at least one interface defined so that ERP
can function properly.
For proper operation you must configure the interfaces following the same manner on each ERN, such
as left/ right, left/ right, and so on.
You must configure the VLAN and configure the Ethernet or port-channel interfaces as switchport, and
then add the VLAN to the interfaces either in trunk or access mode. This is a prerequisite to configuring
the ERP left interface and right interface.
Examples
The following example configures a right interface on an Ethernet interface.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# right-interface vlan 5 ethernet 0/1
rpl
Configures an Ethernet Ring Protection (ERP) Ring Protection Link (RPL).
Syntax
rpl {vlanvlan_id [ethernet slot/port |port-channel number ] }
no rpl {vlanvlan_id [ethernet slot/port |port-channel number ] }
Command Default
No RPL is configured by default.
Parameters
vlan_id
Specifies the VLAN ID of the ERP left or right ring interface and interface number. Range is from
1 through 4090.
ethernet slot/port
Specifies an Ethernet interface.
port-channel number
Specifies a port-channel.
Modes
ERP configuration mode
Usage Guidelines
Each ring needs to have one RPL owner for each ring. The RPL owner’s role is to block traffic on one
port when no failure exists in the ring. The blocked port will be the left interface that you initially
configured. After configuring the ERN to be the RPL owner, by means of the rpl-owner command,
you next must set the RPL, by means of the rpl command.
You must configure the VLAN and configure the Ethernet or port-channel interfaces as switchport, then
add the VLAN to the interfaces in either trunk or access mode. This is a prerequisite to configuring the
rpl command.
Examples
The following example configures an RPL.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# rpl vlan 5 ethernet 0/1
rpl-owner
Set an Ethernet Ring Protection (ERP) bridge as a Ring Protection Link (RPL) owner.
Syntax
rpl-owner
no rpl-owner
Command Default
The RPL owner is not set by default.
Modes
ERP configuration mode
Usage Guidelines
Each ring needs to have one RPL owner. The RPL owner role is to block traffic on one port when no
failure exists in the ring. After configuring the ERN to be the RPL owner, by means of the rpl-owner
command, you next must set the RPL, by means of the rpl command.
This command is required to set one of the nodes in an ERP ring as the RPL owner.
Examples
The following example sets the ERP bridge as an RPL owner.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# rpl-owner
rpki priority
This command sets the priority of a server configured in the Resource Public Key Infrastructure's (RPKI)
RPKI to Router Protocol (RTR) library. This command sets the priority of the RPKI Server contained in it.
A RPKI server in a priority with a lower value will be chosen over a server in priority with a higher value.
Syntax
rpki priority <1-100>
[no] rpki priority <1-100>
Parameters
<1-100>
The cache server priority number.
Modes
router bgp
Usage Guidelines
At least one RPKI priority value must exist in the RTR library. A maximum of 100 RTR priority values can
be created. RTR priority values are numbered 1 to 100. Values over this range will report an error. Each
RTR priority can store one RPKI server information.
Examples
This example shows the steps to create a new rpki priority entry in the RTR library.
SLX(config)#router bgp
server ssh
This command establishes a SSH connection to the configured cache server. Establishing this
connection enables the validation of prefixes with the RPKI server. Only one (1) cache server can be
configured under one priority. Attempting to configure another RPKI server will report an error. The
RPKI server connection is attempted through the Management VRF. Use the no format of this
command to remove the configured RPKI server from the priority.
Syntax
server ssh { name | ipv4/ipv6 address } port port no username username
password-file client private key path
[no] server ssh { name | ipv4/ipv6 address } port port no username
username password-file client private key path
Syntax
Parameters
name
The hostname of the remote RPKI cache server. You can use one of hostname or IP address.
ipv4/ipv6 address
The IPv4 or IPv6 IP address of the remote RPKI server. You can use one of hostname or IP
address.
port port no
The configured SSH port number on the remote RPKI server. The default SSH port is 22. Port
numbers are in the range of 1-65535.
username
The Username of the account used to connect to the remote RPKI server. This value cannot be
longer than 63 characters.
password-file
The key file for this user credentials. This key file is provided by the operator of the remote RPKI
server. Contact the administrator/operator of the server to get this key. An error is reported
when this file is not found at the supplied path when this server entry is created.
Modes
RPKI Priority
Use the [no] format of this command to remove a configured RPKI server from the current RPKI priority.
Usage Guidelines
Only one RPKI Server can be configured in a priority. Attempts to configure more than one server in a
priority will report an error.
Warning
Every time this command is run, there is a possibility that your CLI console response may
become slow. This is due to the SLX-OS performing CPU intensive tasks of caching ROAs from
the remote RPKI server and then revalidating RPKI state for all existing prefixes. This has been
observed in systems with fully scaled routes in RIB-in when adding a server in the highest
RPKI priority group. Adding servers in the lower priority groups does not cause this issue.
This slowdown is also possible when the connection to the existing RPKI server fails and the
system fails over to the server with the next priority.
Examples
This example shows the steps to add a SSH connection to the configured cache server in the rpki
priority within the router bgp configuration mode. This example also shows adding a SSH server
to another RPKI priority.
SLX(config)# router bgp
SLX(config-bgp-router)# rpki priority 1
SLX(config-bgp-rpki-grp)# server ssh rpki.realmv6.org port 22 username rtr-ssh password-
file "/root/.ssh/id_rsa_realmv6-org"
SLX(config-bgp-rpki-grp)# exit
SLX(config-bgp-router)# rpki priority 2
SLX(config-bgp-rpki-grp)# server ssh 10.10.11.152 port 2200 username rtr-admin-g1
password-file "/root/.ssh/id_rsa_10-10-11-152"
SLX(config-bgp-rpki-grp)#
server tcp
This command establishes a TCP connection to the configured cache server. TCP connections are not
secured by nature. Establishing this connection enables the validation of prefixes with the RPKI server.
Only one (1) cache server can be configured under one priority. Attempting to configure another RPKI
server will report an error. The RPKI server connection is attempted through the Management VRF. Use
the no format of this command to remove the configured RPKI server from the priority.
Syntax
server tcp { name | ipv4/ipv6 address } port port no
Parameters
name
The hostname of the remote RPKI server. You can use one of hostname or IP address.
ipv4/ipv6 address
The IPv4 or IPv6 IP address of the remote RPKI server. You can use one of hostname or IP
address.
port port no
The configured SSH port number on the remote RPKI server. Port numbers are in the range of
1-65535.
Modes
RPKI Priority
Usage Guidelines
Only one RPKI Server can be configured in a priority. Attempts to configure more than one server in a
priority will report an error.
Use the [no] format of this command to remove a configured RPKI server from the current RPKI priority
priority.
Warning
Every time this command is run, there is a possibility that your CLI console response may
become slow. This is due to the SLX-OS performing CPU intensive tasks of caching ROAs from
the remote RPKI server and then revalidating RPKI state for all existing prefixes. This has been
observed in systems with fully scaled routes in RIB-in when adding a server in the highest
RPKI priority group. Adding servers in the lower priority groups does not cause this issue.
This slowdown is also possible when the connection to the existing RPKI server fails and the
system fails over to the server with the next priority.
Examples
This example shows the steps to add a TCP connection to the configured cache server in the rpki
priority within the router bgp configuration mode. This example also shows adding a server to
another RPKI priority.
SLX(config)# router bgp
SLX(config-bgp-router)# rpki priority 1
SLX(config-bgp-rpki-grp)# server tcp rpki.realmv6.org port 113
SLX(config-bgp-rpki-grp)# exit
SLX(config-bgp-router)# rpki priority 2
SLX(config-bgp-rpki-grp)# server tcp 10.10.11.152 port 113
SLX(config-bgp-rpki-grp)#
rmon alarm
Sets the RMON alarm conditions.
Syntax
rmon alarm index snmp_oid interval seconds [ absolute | delta ] rising-
threshold value event number [ falling-threshold value event number
[ owner name ]
no rmon alarm
Command Default
No alarms are configured.
Parameters
index
Specifies the RMON alarm index. Valid values range from 1 through 65535.
snmp_oid
Specifies the MIB object to monitor. The variable must be in the SNMP OID format, for example,
1.3.6.1.2.1.16.1.1.1.5.65535. The object type must be a counter32.
interval seconds
Specifies the RMON alarm sample interval in seconds. Valid values range from 1 through
2147483648.
absolute
Sets the sample type as absolute.
delta
Sets the sample type as delta.
rising-threshold value
Specifies the RMON alarm rising threshold. Valid values range from 0 through 4294967295.
event number
Specifies the event for the rising alarm. Valid values range from 1 through 65535.
falling-threshold value
Specifies the RMON alarm falling threshold. Valid values range from 0 through 4294967295.
event number
Specifies the event for the rising alarm. Valid values range from 1 through 65535.
owner name
Specifies the identity of the owner. The maximum number of characters is 32.
Modes
Global configuration mode
Usage Guidelines
Enter no rmon alarm to disable the alarm conditions.
Examples
To set RMON alarm conditions:
device# configure terminal
device(config)# rmon alarm 100 1.3.6.1.2.1.16.1.1.1.5.65535 interval 5 absolute rising-
threshold 10000 event 100 falling-threshold 1000 event 101 owner admin
Syntax
rmon collection history number [ buckets bucket_number | interval seconds
| owner name ]
no romn collection history number
Command Default
RMON history collection is not enabled.
Parameters
number
Specifies the RMON collection control index value. Valid values range from 1 through 65535.
buckets bucket_number
Specifies the maximum number of buckets for the RMON collection history. Valid values range
from 1 through 65535.
interval seconds
Specifies the alarm sample interval in seconds. Valid values range from 1 through 3600. The
default value is 1800.
owner name
Specifies the identity of the owner. The maximum number of characters is 15.
Modes
Interface subtype configuration mode
Usage Guidelines
This command collects periodic statistical samples of Ethernet group statistics on a specific interface for
later retrieval.
Enter no rmon collection history number to disable the history of statistics collection.
Examples
To collect RMON statistics, with an RMON collection control index value of 5 for the owner named
admin, on a specific Ethernet interface:
device# configure terminal
device(config)# interface ethernet 1/6
device(conf-if-eth-1/6)# rmon collection history 5 owner admin
Syntax
rmon collection stats number [ owner name ]
no rmon collection stats number
Command Default
RMON statistic collection is not enabled.
Parameters
number
Specifies the RMON collection control index value. Valid values range from 1 through 65535.
owner name
Specifies the identity of the owner.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no rmon collection stats number to disable the collection of statistics.
Examples
The following example shows how to collect RMON statistics, with an RMON collection control index
value of 2 for the owner named admin, on a specific Ethernet interface:
device# configure terminal
device(config)# interface ethernet 1/6
device(conf-if-eth-1/6)# rmon collection stats 2 owner admin
rmon event
Adds or removes an event in the RMON event table associated to the RMON alarm number.
Syntax
rmon event index [ description word | log | owner name | trap word ]
no rmon event
Command Default
No events are configured.
Parameters
index
Specifies the RMON event number. Valid values range from 1 through 65535.
description word
Specifies a description of the event.
log
Generates an RMON log when an event is triggered.
owner name
Specifies the owner of the event. The name string must be between 1 and 32 characters in
length.
trap word
Specifies the SNMP community or string name to identify this trap.
Modes
Global configuration mode
Usage Guidelines
Enter no rmon event to remove the event configuration.
Examples
To configure an RMON event:
device# configure terminal
device(config)# rmon event 2 log description "My Errorstoday" owner gjack
role name
Creates or modifies a non-default role.
Syntax
role name role_name [ desc description ]
no role name role_name [ desc description ]
Parameters
role_name
Specifies the name of the role.
desc description
Specifies an optional role description.
Modes
Global configuration mode
Usage Guidelines
For each role that you create, you define one or more rules. Each user is associated with one—and only
one—role.
Role names are from 4 through 32 characters, must begin with a letter, and can contain alphanumeric
characters and underscores. The name cannot be same as that of an existing user.
The description field supports up to 64 characters and can include any printable ASCII character, except
for the following characters: single quotation mark (‘), double quotation mark ("), exclamation point (!),
colon (:), and semi-colon (;). If the description contains spaces, enclose the text in double quotation
marks.
The maximum number of roles supported is 64, including the user and admin default roles.
Examples
The following example creates a role.
device# configure terminal
device(config)# role name tempAdmin desc "Daily admin functions"
Syntax
rollback apply checkpoint [ cp-name [ best-effort | stop-at-first-
failure ] [ verbose ] ]
Command Default
The best-effort mode is applied if it is not specified.
Parameters
cp-name
Specifies the name of a checkpoint.
best-effort
Implements a rollback and skips any errors.
stop-at-first-failure
Implements a rollback and stops at the first failure.
verbose
Displays the execution log.
Modes
Privileged EXEC mode
Usage Guidelines
A configuration checkpoint must exist before this command is issued.
Configuration parameters that have changed are first removed and the previous values are then
reapplied. If cp-name is not specified, the configuration rolls back to the most recent created
checkpoint. This is not the same as an undo/redo scenario. Once the rollback process is complete, the
system runs with the exact configurations in the checkpoint file.
Once the rollback is successfully completed, the execution of the show rollback diff
checkpoint command, comparing the checkpoint and the running configuration file, should not
report any differences.
The user can view any errors/warnings encountered during the rollback operation. The user is
responsible for cleaning up the already applied changes before the error has occurred, by viewing the
configuration differences between checkpoint and the running configuration.
Use of the Control+C key combination is not recommended during the rollback operation. Although
Control+C is not blocked, it could leave the device with an indeterminate configuration. When the user
issues the rollback command, a warning is issued that tells the user not to abort an ongoing rollback
session.
Examples
This example reverts the configuration to a checkpoint named "user_checkpoint1".
device# rollback apply checkpoint user_checkpoint1
This operation will modify the running configuration of the system. Do you want to
continue? [Y/N]y
% Warning: Configuration Rollback is in-progress.
Please do not abort an ongoing session as it can leave the system with an inconsistent
configuration.
......
Rollback completed successfully.
rollback checkpoint
Creates or removes a rollback configuration checkpoint, with an optional name and description.
Syntax
rollback checkpoint [ cp-name [ description string ] ]
no rollback checkpoint { all | cp-name }
Command Default
A checkpoint is not created by default.
Parameters
cp-name
Specifies the name of a checkpoint.
description string
Specifies a description for the checkpoint. See the Usage Guidelines.
all
Specifies all checkpoints.
Modes
Privileged EXEC mode
Usage Guidelines
The user must have admin privileges to execute this command.
The checkpoint name and description string can be any alphanumeric string. The description string
must be inside quotation marks. Checkpoint names must be 64 characters or less. Checkpoint
descriptions must be 128 characters or less.
When the checkpoint name is not specified, the checkpoint is created with a timestamp in
YYYMMDD_HHMISS format. For example, 20180511_23435.
The no form of this command removes all checkpoints or a specified checkpoint. The no rollback
checkpoint all command deletes all checkpoints in the device flash memory.
Examples
This example creates the rollback checkpoint "test" with description "testing checkpoint".
device# rollback checkpoint test description "testing checkpoint"
Checkpoint "test" creation completed successfully.
rollback enable
Enables configuration rollback.
Syntax
rollback enable
no rollback enable
Command Default
Rollback is disabled.
Modes
Privileged EXEC mode
Usage Guidelines
Use the no form of this command to clean up all the checkpoints present in the system.
Examples
This example enables rollback.
device# configure terminal
device(config)# rollback enable
Syntax
root access console
no root access console
Modes
Global configuration mode
Usage Guidelines
The no root access console allows root access to the device through all terminals (SSH, Telnet,
and console).
Examples
Typical command output:
device# configure terminal
device(config)# do show running-config | include root
% No entries found.
device(config)# root access console
device(config)# do show running-config | include root
root access console
device(config)#
root enable
Enables root access to the device following a firmware configuration.
Syntax
root enable
no root enable
Modes
Global configuration mode
Usage Guidelines
The no root enable command disables root access to the device.
Examples
Typical command output:
device# configure terminal
device(config)# do show running-config | include root
% No entries found.
device(config)# root enable
% Info: Root password is at system default, for better security, you may want to change
it.
device(config)# do show running-config | include root
root enable
device(config)#
route-map (BGP)
Creates or modifies a route-map under Border Gateway Protocol (BGP).
Syntax
route-map name { permit | deny } stanza
no route-map name { permit | deny } stanza
Parameters
name
Specifies the name of the route map. The string must be between 1 and 63 ASCII characters in
length.
permit
Allows a matching pattern.
deny
Disallows a matching pattern.
stanza
Specifies the stanza ID. Valid values range from 1 through 65535. A route map can support up to
1024 stanzas.
Modes
Global configuration mode
Usage Guidelines
This command is used in conjunction with the match and set commands.
The continue command configures the route map to continue to evaluate and execute match
statements after a successful match occurs. The continue statement proceeds to the route map with
the specified sequence number. If no sequence number is specified, the statement proceeds to the
route map with the next sequence number (as an "implied" continue).
Examples
The following example configures a route map that allows a matching pattern.
device# configure terminal
device(config)# route-map test permit 5
route-only
Configures VE route-only mode on physical ports and port-channels (LAG ports), to enable the
exclusive IP routing of incoming packets. Incoming switching packets on the port are dropped, and
outgoing switching packets are forwarded.
Syntax
route-only
no route-only
Command Default
This feature is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
Use the no form of this command to disable this feature.
Examples
To configure VE route-only mode on a physical port.
device# configure terminal
device(config)# interface ethernet 1/2
device(conf-if-eth-1/2)# switchport
device(conf-if-eth-1/2)# switchport mode trunk
device(conf-if-eth-1/2)# switchport mode trunk allowed vlan add 100
device(conf-if-eth-1/2)# route-only
device(conf-if-eth-1/2)# no shutdown
route-precedence
Defines the order (precedence) in which unicast routes are selected from the unicast routing table
(uRTM) for Reverse Path Forwarding resolution.
Syntax
route-precedence {none [ priority-1| priority-2 | priority-3 ] | uc-
default [ priority-1| priority-2 | priority-3 ] | uc-non-default
[ priority-1| priority-2 | priority-3 ] }
no route-precedence
Command Default
The default route precedence is uc-non-default followed by uc-default.
Parameters
none
Specifies that this type of route is to be ignored. You can specify this option for any multicast or
unicast route type.
uc-non-default
Specifies the precedence for the non-default unicast route table (uRTM).
uc-default
Specifies the precedence for the default unicast route table (uRTM).
priority-1| priority-2 | priority-3
Specifies the unique priority for the selected route.
Modes
Router PIM configuration mode
Usage Guidelines
The order in which you place the keywords determines the route precedence.
The no route-precedence form of this command restores the default route precedence settings.
Examples
The following example configures the route precedence for IPv4 PIM.
device(config)# router pim
device(config-pim-router)# route-precedence uc-default uc-non-default none
route-target
Configures route-target for distribution of routes between VPN routing tables.
Syntax
route-target { import | export | both } ASN-nn
no route-target
Parameters
import
Specifies export.
export
Specifies export.
both
Specifies both export and import.
ASN-nn
Composed of the local ASN number followed by a colon ":" and a unique arbitrary number. For
example 3:6.
Modes
VRF configuration mode
Usage Guidelines
The no form of the command to delete configuration for the route-target for distribution.
Examples
The following example shows how to configures route-target for distribution of routes between VPN
routing tables.
device# configure terminal
device(config)# vrf vpn1
device#(config-vrf-vpn1)# rd1 1:2
device#(config-vrf-vpn1)# vpn-statistics
device#(config-vrf-vpn1)# address-family ipv4 unicast
device#(config-vrf-vpn1-ipv4-unicast)# route-target-import 100:1
device#(config-vrf-vpn1-ipv4-unicast)# route-target-export 100:1
route-target (EVPN)
Enables auto-generation of the import and export route-target community attributes for an Ethernet
Virtual Private Network (EVPN) default instance.
Syntax
route-target { both | import } auto [ ignore-as ]
route-target export auto
no route-target { both | import } auto [ ignore-as ]
no route-target export auto
Command Default
Disabled.
Parameters
both auto
Specifies auto-generation of the import and export route-target community attributes.
ignore-as
Specifies that the autonomous system (AS) number be ignored.
export auto
Specifies auto-generation of the export route-target community attribute.
import auto
Specifies auto-generation of the import route-target community attribute.
Modes
EVPN configuration mode
Usage Guidelines
The no form of this command removes configured route target parameters.
Examples
The following example configures auto-generation of the import and export route-target community
attributes for EVPN default instance.
The following example configures auto-generation of the import route-target community attribute and
specifies that the AS path be ignored to the route for EVPN default instance.
The following example configures auto-generation of the export route-target community attribute for
EVPN myinstance instance.
Syntax
route-target { both | import } auto [ admin-value:arbitrary-value ]
route-target export auto [ admin-value:arbitrary-value ]
no route-target { both | import } auto [ ignore-as ]
no route-target export auto
Command Default
Disabled.
Parameters
both auto
Specifies auto-generation of the import and export route-target community attributes.
export auto
Specifies auto-generation of the export route-target community attribute.
import auto
Specifies auto-generation of the import route-target community attribute.
admin-value
The administrative number assigned to the route. This can be a local ASN number or an IP
address. The ASN number can be either a 2-byte number (from 0 through 65535) or a 4-byte
number (from 0 through 4294967295).
arbitrary-value
An arbitrary number you choose. The range of valid values is from 0 through 65535 if the ASN is
is an IP address or a 2-byte ASN. The range is 0 through 4294967295 if the ASN is a 4-byte ASN.
Modes
EVPN VLAN/BD configuration mode
Usage Guidelines
The no form of this command removes configured route target parameters.
Examples
The following example configures auto-generation of the import and export route-target community
attributes for EVPN VLAN/BD 200.
router bgp
Enables BGP routing.
Syntax
router bgp
no router bgp
Command Default
BGP routing is not enabled.
Modes
Global configuration mode
Usage Guidelines
Examples
The following example enables BGP routing.
router isis
Enables Intermediate System-to-Intermediate System (IS-IS) routing.
Syntax
router isis
no router isis
Command Default
Disabled
Modes
Global configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables IS-IS routing.
device# configure terminal
device(config)# router isis
device(config-isis-router)#
router mpls
Enables MPLS and accesses MPLS configuration mode
Syntax
router mpls
no router mpls
Command Default
MPLS is disabled by default.
Modes
Global configuration mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables MPLS on the device and accesses MPLS configuration mode.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)#
router ospf
Enables and configures the Open Shortest Path First version 2 (OSPFv2) routing protocol.
Syntax
router ospf [ vrf name ]
no router ospf
Parameters
vrf name
Specifies a nondefault VRF.
Modes
Global configuration mode
Usage Guidelines
Use this command to enable the OSPFv2 routing protocol and enter OSPF router or OSPF router VRF
configuration mode. OSPFv2 maintains multiple instances of the routing protocol to exchange route
information among various VRF instances.
The no form of the command deletes all current OSPF configuration and blocks any further OSPFv2
configuration.
Examples
The following example enables OSPFv2 on a default VRF and enters OSPF VRF router configuration
mode.
router pim
Configures basic global protocol-independent multicast (PIM) Sparse parameters on a device within the
PIM Sparse domain and enters PIM-router configuration mode.
Syntax
router pim
no router pim
Command Default
PIM Sparse is not configured.
Modes
Global configuration mode
Usage Guidelines
The no form of this command disables PIM and removes all configuration for PIM multicast on the
device (router pim level) only.
You do not need to globally enable IP multicast routing when configuring PIM Sparse.
After you enable IP multicast routing and PIM Sparse at the global level, you must enable it on the
individual interfaces connected to the PIM Sparse network.
If you configure PIM Sparse on an interface that is on the border of the PIM Sparse domain, you also
must also configure the ip pim border command on the interface.
You must configure the bsr-candidate ethernet command to identify an interface on at least
one device as a candidate PIM Sparse Bootstrap router (BSR) and candidate PIM Sparse Rendezvous
Point (RP).
You can configure the rp-address command to explicitly identify an RP, including an ACL-based RP,
by its IP address instead of having it identified by the RP election process.
Examples
This example configures basic global PIM Sparse parameters.
device(config)# router pim
router-interface
Binds a router interface to a tunnel or bridge domain.
Syntax
router-interface ve num
no router-interface
Command Default
A router interface is not configured.
Parameters
ve num
Specifies a virtual interface number on the router.
Modes
Bridge domain configuration mode
Usage Guidelines
Note
You cannot enable routing on a VPLS instance when the vc-mode option on the PW
attached to the instance is set to raw.
When routing is enabled on a VPLS instance that has only one PW and no local endpoints, the VPLS
instance is brought to an active state; this state enables routing when the next hop is the PW endpoint.
Examples
The following example shows how to attach a virtual router interface to a tunnel.
device# configure terminal
device(config)# interface tunnel 5
device(config-intf-tunnel-5)# mode gre ip
device(config-intf-tunnel-5)# source 10.1.1.10
device(config-intf-tunnel-5)# source ve 4
device(config-intf-tunnel-5)# destination 10.1.1.11
device(config-intf-tunnel-5)# router-interface ve 3
The following example shows how to bind a virtual router interface to a bridge domain.
device# configure terminal
device(config)# bridge-domain 100
device(config-bridge-domain-100)# router-interface ve 100
rp-address
Configures a device interface as a static rendezvous point (RP) for IPv4 PIM.
Syntax
rp-address ip-address[group-range-prefix-list]
no rp-address ip-address
Command Default
The RP is selected by the PIM-SM (Sparse Mode) RP election process.
Parameters
ip-address
Specifies the IPv4 address of the RP.
group-range-prefix-list
Specifies the IPv4 multicast group range to be mapped to the RP. The default group range for
IPv4 is 224/4.
Modes
Router PIM configuration mode
Usage Guidelines
Devices in the PIM-SM domain use the specified static RP and ignore group-to-RP mappings received
from the bootstrap router (BSR).
The RP is the meeting point for PIM-SM sources and receivers. A PIM-SM domain can have multiple RPs,
but each PIM-SM multicast group address can have only one active RP. PIM-SM routers learn the
addresses of RPs and the groups for which they are responsible from one of the following sources.
• The static RP configuration on each PIM-SM router
• Messages that the BSR sends to each PIM-SM router
The no rp-address form of this command restores the default functionality, in which the RP is
selected by the RP election process.
Examples
This example configures the device interface at IP address 4.4.4.4 as the RP. The default group range is
224/4.
device(config)# router pim
device(config-pim-router)# rp-address 4.4.4.4
This example configures the RP with specific group ranges for IPv4.
device(config)# router pim
device(config-pim-router)# rp-address 4.4.4.4 static-rp-plist
device(config)# ip prefix-list static-rp-plist permit 225.1.1.0/24
rp-candidate
Configures a device as a candidate rendezvous point (RP) for all multicast groups with the prefix
224.0.0.0/4 (IPv4), by default, or for a specified group range.
Syntax
rp-candidate [interface {ethernet | loopback | port-channel |
ve}interface-number ] | [prefix prefix-list ]
Command Default
By default, the PIM router is not available for selection as an RP.
Parameters
interface ethernet | loopback | port-channel | ve interface-number
Specifies an interface for the candidate RP and the interface number in slot or slot/port format.
prefix prefix-list
Specifies the list that identifies the IPv4 or IPv6 group address range.
Modes
Router PIM configuration mode
Usage Guidelines
The RP is the meeting point for PIM-SM (Sparse Mode) sources and receivers. A PIM-SM domain can
have multiple RPs, but each PIM-SM multicast group address can have only one active RP. PIM-SM
routers learn the addresses of RPs and the groups for which they are responsible from messages that
the bootstrap router (BSR) sends to PIM-SM router.
Although you can configure the device as only a candidate BSR or an RP, a best practice is to configure
the same interface on the same device as both a BSR and an RP.
The no rp-candidate form of the command makes the PIM router cease to act as a candidate RP.
Examples
This example configures a physical device as a candidate RP.
Syntax
rpf ecmp rebalance
no rpf ecmp rebalance
Modes
Router PIM configuration mode
Usage Guidelines
When ECMP rebalance is enabled, existing flows are redistributed among all available ECMP paths.
When a new path is added, some existing flows are redistributed to the new path using the ECMP
rebalancing.
The no rpf ecmp rebalance form of the command disables ECMP rebalancing.
Examples
The following example enables IPv4 multicast ECMP load sharing with dynamic rebalancing.
device(config)# router pim
devic(config-pim-router)# rpf ecmp rebalance
rpf-mode
Enables strict or loose unicast Reverse Path Forwarding (uRPF) mode on an interface.
Syntax
rpf-mode { loose | strict }
no rpf-mode
Command Default
uRPF mode is not enabled.
Parameters
strict
Specifies uRPF strict mode. For details, see the Usage Guidelines.
loose
Specifies uRPF loose mode. For details, see the Usage Guidelines.
Modes
Interface configuration mode
Usage Guidelines
This command is applicable only on Layer 3 physical, port-channel, and VE interfaces. On a Layer 3
interface, uRPF is enabled by configuring an uRPF mode on that interface and can be modified to a
different mode dynamically on that interface.
On the SLX 9540, RPF mode is not supported when OptiScale is enabled.
Loose mode permits a packet if the source address matches a routing table entry. Packets are dropped
only if the source address is not reachable through any device interface.
Strict mode requires a packet to match a known route entry (as described in loose mode) and to arrive
at the interface as described in the router table next-hop information. Packets that do not match both
of these criteria are dropped.
Neither loose mode nor strict mode includes the default route in the Source IP (SIP) lookup.
Strict mode is not supported for ECMP routes or for IP over MPLS (IPoMPLS).
uRPF is VRF-aware.
Examples
The following example enables uRPF in strict mode on an Ethernet interface.
device# configure terminal
device(config)# interface eth 1/58
device(conf-if-eth-1/58)# rpf-mode strict
rsvp
Accesses MPLS RSVP configuration mode to configure RSVP-TE Hello.
Syntax
rsvp
no rsvp
Command Default
None
Modes
MPLS configuration mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example accesses MPLS RSVP configuration mode to configure RSVP-TE Hello globally.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# rsvp
device(config-router-mpls-rsvp)#
The following example accesses MPLS RSVP configuration mode to configure RSVP-TE Hello on an
MPLS interface.
device# configure terminal
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/12
device(config-router-mpls-interface-0/12)# rsvp
device(config-router-mpls-interface-0/12-rsvp)#
rsvp-flooding-threshold
The rsvp-flooding-threshold command can be executed multiple times for the same interface.
The threshold values are added to the existing set of values for the interface.
Syntax
rsvp-flooding-threshold [ down | up ] percent *
no rsvp-flooding-threshold [ down | up ] percent *
Command Default
The command is disabled, by default.
Parameters
down percent*
The down option sets the thresholds for decreased resource availability. Valid values are from 0
to 99. The default values for down is 100, 99, 98, 97, 96, 95, 90, 85, 80, 75, 60, 45, 30, 15.
The "*" represents multiple percent values can be given. A minimum one percentage value is
required.
up percent*
The up option sets the thresholds for increased resource availability. Valid values are from 1 to
100. The default values for up is 15, 30, 45, 60, 75, 80, 85, 90, 95, 97, 98, 99, 100.
The "*" represents multiple percent values can be given. A minimum one percentage value is
required.
Modes
MPLS policy mode.
Usage Guidelines
The no form of the command removes the RSVP TE flooding threshold configuration.
Previously configured values are not overwritten. The interface specific configuration overrides the
global configuration.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
In the following example, the UP thresholds contain 10, 50, 55, 95, 96, 97, 98, and 100. The DOWN
thresholds contain 50, 40, 30, 20, and10.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 0/1
device(config-router-mpls-if-eth-0/1)# rsvp-flooding-threshold up 10 50 55 95
device(config-router-mpls-if-eth-0/1)# rsvp-flooding-threshold up 96 97 98 99 100
device(config-router-mpls-if-eth-0/1)# rsvp-flooding-threshold down 50 40
device(config-router-mpls-if-eth-0/1)# rsvp-flooding-threshold down 30 20 10
rsvp-periodic-flooding-time
Sets the interval for RSVP-TE periodic flooding.
Syntax
rsvp-periodic-flooding-time interval
no rsvp-periodic-flooding-time
Command Default
All MPLS interfaces are checked every three minutes by default. The length of interval value is set to
zero.
Parameters
interval
Specifies the length of interval used for periodic flooding (in seconds). Valid range is zero,
30-3600. For value zero, periodic flooding is turned off.
Modes
MPLS policy mode
Usage Guidelines
TE advertisements are triggered when there is a difference in the available bandwidth and advertised
available bandwidth.
The no form of the command can be used to set the periodic flooding timer to default value.
Examples
The following example sets the interval as 240, which triggers periodic flooding every four minutes.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# rsvp-periodic-flooding-time 240
device(config-router-mpls-policy)# no rsvp-periodic-flooding-time
rule
Creates role-based access permissions (RBAC) associated with a role.
Syntax
rule index [ action { accept | reject } ] [ operation { read-only | read-
write } ] role role_name command command_name
no rule index
Command Default
The default for action is accept. The default for operation is read-write.
Parameters
index
Specifies a numeric identifier for the rule. Valid values range from 1 through 512.
action accept | reject
(Optional) Specifies whether the user is accepted or rejected while attempting to execute the
specified command. The default value is accept.
operation read-only | read-write
(Optional) Specifies the type of operation permitted. The default value is read-write.
role role_name
Specifies the name of the role for which the rule is defined.
command command_name
Specifies the command for which access is defined. Separate commands with a space. To display
a list of supported commands, type a question mark (?).
Modes
Global configuration mode
Usage Guidelines
For each role that you create, you define one or more rules. Each account is associated with one—and
only one—role.
When you create a rule, the index, role, and command operands are mandatory; the action and
operation operands are optional.
When you modify a rule, all operands except index and role are optional.
Examples
The following example creates rules enabling the NetworkSecurityAdmin role to create user accounts.
device# configure terminal
device(config)# rule 150 action accept operation read-write role NetworkSecurityAdmin
command config
device(config)# rule 155 action accept operation read-write role NetworkSecurityAdmin
command username
rx-label-silence-time
Defines the length of the receive label silence timer for LDP-IGP synchronization.
Syntax
rx-label-silence-time milliseconds
no rx-label-silence-time
Command Default
The default value is 1000 milliseconds.
Parameters
milliseconds
Specifies the length of time in milliseconds of the receive label silence timer. Enter an integer
from 100 to 60000.
Modes
MPLS LDP configuration mode
Usage Guidelines
Use the no form of the command to reset the default value of 1000 milliseconds.
When labels are not received from the peer for a short period of time, the session is declared In Sync.
When a label is received from a peer, then the receive label silence timer is reset.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example sets the receive label silence timer to 80000 milliseconds.
device(conf)# router mpls
device(config-mpls)# ldp
device(config-router-mpls-ldp)# rx-label-silence-time 80000
secure-port
Configures the port on which the SLX-OS device will listen for incoming secure connections. Configure a
port in the range 1024-49151.
Syntax
secure-port port-number
[no] secure-port
Command Default
By default, the gNMI server listens on port 9339. Connections on this port are not secured.
Parameters
port-number
Configures the port on which the gNMI server will listen for incoming connections. Configure a
port in the range 1024-49151.
Modes
gNMI Server mode.
Usage Guidelines
The presence of this configuration indicates that gNMI access is secure. If this configuration is not
present, then the access is insecure. You can also use the default port 9339 as a secure port. To do so,
configure the port as the secure port. This configuration works along with the minimum TLS version
support to enhance security.
Examples
This example configures the secure gNMI port as 48151
SLX (config)# gnmi server
SLX (config-gNMI-server)# secure-port 48151
sample-recording
Configures the template to record the sample history.
Syntax
sample-recording [ disable | enable ]
no sample-recording
Command Default
The command is disabled by default.
Parameters
disable
Removes the setting for the sample recording for the selected LSP or autobw-template.
enable
Sets the sample recording for ththe selected LSP or autobw-template.
Modes
MPLS sub-configuration modes.
config-router-mpls-autobw-template-template1
config-router-mpls-lsp-lsp1
Usage Guidelines
The no function of the command disables the option.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example shows a configuration to record the sample history for template1.
device>configure
device(config)# router mpls
device(config-router-mpls)# autobw
device(config-router-mpls-autobw)# template template1
device(config-router-mpls-autobw-template-template1)# sample-recording enable
The following example shows a configuration to stop recording sample history for LSP1.
device>configure
device(config)# router mpls
device(config-router-mpls)# lsp lsp1
device(config-router-mpls-lsp-lsp1)# autobw
device(config-router-mpls-lsp-lsp1-autobw)# sample-recording disable
scheduler
Configures the strict priority queues on an interface for QoS egress scheduling.
Syntax
scheduler strict-priority traffic-class-queues dwrr TC0-BW% TC1-BW% TC2-
BW% TC3-BW% TC4-BW% TC5-BW% TC6-BW% TC7-BW% [ TC0 bytes ] [ TC1
bytes ] [ TC2 bytes ] [ TC3 bytes ] [ TC4 bytes ] [ TC5 bytes ] [ TC6
bytes ] [ TC7 bytes ]
no scheduler strict-priority
Parameters
traffic-class-queues
Specifies the traffic class strict priority queues. Enter one of the following integers:
• 0—No strict priority queues
• 1—Traffic class 7 strict priority queue
• 2—Traffic class 6 through 7 strict priority queues
• 3—Traffic class 5 through 7 strict priority queues
• 4—Traffic class 4 through 7 strict priority queues
• 5—Traffic class 3 through 7 strict priority queues
• 6—Traffic class 2 through 7 strict priority queues
• 7—Traffic class 1 through 7 strict priority queues
drww TC0-BW% TC1-BW% TC2-BW% TC3-BW% TC4-BW% TC5-BW% TC6-BW% TC7-BW%
Configures the Deficit Weighted Round Robin queues in percentage for each traffic class, if the
priority is in weighted fair queue (WFQ) mode. Enter an integer from 0 through 100 (TC0-BW for
traffic class 0 through TC7-BW for traffic class 7). The total of all values must equal 100%.
TC0 - TC7 bytes
Sets the maximum bandwidth the queue can transmit. This value is in bytes.
Modes
Policy-map configuration mode
Usage Guidelines
This command is allowed only for the egress direction.
Use the no form of this command to remove QoS egress scheduling from the interface.
Examples
The following example configures QoS egress scheduling on an interface.
device# configure terminal
device(config)# policy-map policy_1
device(config-policymap)# class default
device(config-policymap-class)# scheduler strict-priority 1 dwrr 25 25 25 10 5 5 5
The following example command configures the QoS egress scheduling on an interface with TC0-TC3
with equal weights and TC4-TC7 as strict, but with queue shapers of 2.0 Gbps, 1.5 Gbps, 1.0 Gbps, and
0.5 Gbps respectively.
Syntax
seq seq-value { permit | deny | hard-drop } ip-protocol { S_IPaddress
mask | host S_IPaddress | any } [ source-operator [ S_port-
numbers ] ] [ TCP-flags ] [ vlan vlanID ] [ count ] [ log ]
[ mirror ] [ copy-sflow ] [ fragment | non-fragment ] [ connlimit
connlimit-value ]
no seq seq-value
{ permit | deny | hard-drop } ip-protocol { S_IPaddress mask | host
S_IPaddress | any } [ source-operator [ S_port-numbers ] ] [ TCP-
flags ] [ count ] [ vlan vlanID ] [ log ] [ mirror ] [ copy-sflow ]
[ fragment | non-fragment ] [ connlimit connlimit-value ]
no { permit | deny | hard-drop } ip-protocol { S_IPaddress mask | host
S_IPaddress | any } [ source-operator [ S_port-numbers ] ] [ TCP-
flags ] [ vlan vlanID ] [ count ] [ log ] [ mirror ] [ copy-sflow ]
[ fragment | non-fragment ] [ connlimit connlimit-value ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq
seq-value, the rule is added at the end of the list.
seq-value
Valid values range from 1 through 65535.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a
permit for this address in a preceding rule.
ip-protocol
Indicates the type of IP packet you are filtering. The options are as follows:
<0-255>
Protocol number custom value from 0 through 255.
icmp
Internet Control Message Protocol
ip
Any IP protocol
tcp
(Supported only if the containing ACL is applied to incoming traffic) Transmission Control
Protocol
udp
User Datagram Protocol
S_IPaddress
Specifies a source address for which you want to filter the subnet.
mask
Defines a mask, whose effect is to specify a subnet that includes the source address that you
specified. For options to specify the mask, see the Usage Guidelines.
host
Specifies a source address.
S_IPaddress
The source address.
any
Specifies all source addresses.
source-operator
If you specified tcp or udp ip-protocol, the following optional operators are available:
eq
The policy applies to the TCP or UDP port name or number you enter after eq.
gt
The policy applies to TCP or UDP port numbers equal to or greater than the port number or the
numeric equivalent of the port name you enter after gt.
lt
The policy applies to TCP or UDP port numbers that are equal to or less than the port number or
the numeric equivalent of the port name you enter after lt.
neq
The policy applies to all TCP or UDP port numbers except the port number or port name you
enter after neq.
range
The policy applies to all TCP or UDP port numbers that are between the first TCP or UDP port
name or number and the second one you enter following the range keyword. The range
includes the port names or numbers you enter. For example, to apply the policy to all ports
between and including 23 (Telnet) and 53 (DNS), enter the following: range 23 53 (two values
separated by a space). The first port number in the range must be lower than the last number in
the range.
S_port-numbers
(Valid only when ip-protocol is UDP or TCP) Specifies one or more source port numbers.
vlan vlanID
Specifies a VLAN interface to which the ACL is bound.
TCP-flags
If you specify tcp ip-protocol, one or more of the following flags are available:
ack
Filters packets for which the ack (acknowledge) flag is set.
fin
Filters packets for which the fin (finish) flag is set.
rst
Filters packets for which the rst (reset) flag is set.
sync
Filters packets for which the syn (synchronize) flag is set.
urg
Filters packets for which the urg (urgent) flag is set.
push
Filters packets for which the psh (push) flag is set.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule. In addition, the ACL log buffer must be enabled, using the
debug access-list-log buffer command.
mirror
(Supported for rules in ACLs applied on physical interfaces to inbound traffic. Not supported for
PBR, rACLs, or ACL-RL.) Mirrors packets matching the rule.
copy-sflow
For incoming traffic, sends matching packets to the sFlow collector.
fragment
Filter fragmented packets. This keyword and non-fragment keyword cannot be used together.
non-fragment
Filter non-fragmented packets. This keyword and fragment keyword cannot be used together.
connlimit connlimit-value
Number of connections allowed per IP address.
Modes
ACL configuration mode
Usage Guidelines
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When
creating rules, specifying sequence values determines the order of rule processing. If you do not specify
a sequence value, the rule is added to the end of the list.
Although in an extended-ACL rule you can include log, mirror, and copy-sflow, only one of the
three is processed, as follows:
• In a permit rule, the order of precedence is mirror > copy-sflow > log.
• In a deny or hard-drop rule, the order of precedence is log > copy-sflow > mirror.
If you are defining rules for a QoS ACL, be aware of the following considerations for ACLs implemented
under flow-based QoS. (For details, refer to the Extreme SLX-OS QoS and Traffic Management
Configuration Guide.)
• Because ACLs applied for QoS use implement a unified counter for all rules in an ACL, rule-level
count keywords are ignored.
• The deny keyword functions as a PASS THROUGH: For a match, QoS action defined for that class is
not applied.
For both interface ACLs and receive-path ACLs, you use identical commands to create the ACLs. You
also use identical commands to define permit/deny rules in the ACLs. The only variance is the
command you use to apply the ACL:
• To apply an interface ACL, from an interface-subtype configuration mode you use the { ip |
ipv6 | mac } access-group command.
• To apply a receive-path ACL, from global configuration mode, you use the { ip | ipv6 }
receive access-group command.
Filtering fragmented or non-fragmented packets is only supported on ingress ACLs. On the SLX 9540
and SLX 9640, fragment match is only supported on BGP FS profile. This ACL can also be used with
RACL, PBR, and RL. Do not use Layer-4 matching along with fragment matching. Fragmented packets
might not have Layer-4 information and most likely cause issues. ACL filtering of fragmented and non-
fragmented packets is not supported on SLX 9150 and SLX 9250 devices.
When configured, the connlimit value behaves differently. When used with a permit rule, this command
will limit the concurrent connections from a particular IP address to this value. When used with a deny
rule, this command will allow connections up to this limit and deny any more connections from the
particular IP address. Also, connection limiting is applicable only to the management interfaces and not
applicable to the front panel (ethernet) ports. Existing sessions might be disrupted when this value is
configured.
Examples
The following example creates an IPv4 extended ACL and defines rules.
device(config)# ip access-list extended extdACL5
device(conf-ipacl-ext)# seq 5 deny tcp host 10.24.26.145 any eq 23
device(conf-ipacl-ext)# seq 7 deny tcp any any eq 80
device(conf-ipacl-ext)# seq 10 deny udp any any range 10 25
device(conf-ipacl-ext)# seq 15 permit tcp any any
The following example creates an IPv4 extended ACL, defines rules in the ACL, and applies it as a
receive-path ACL.
device(config)# ip access-list extended ipv4-receive-acl-example
device(conf-ipacl-ext)# hard-drop tcp host 10.0.0.1 any count
device(conf-ipacl-ext)# hard-drop udp any host 20.0.0.1 count
device(conf-ipacl-ext)# permit tcp host 10.0.0.2 any eq telnet count
device(conf-ipacl-ext)# permit tcp host 10.0.0.2 any eq bgp count
device(conf-ipacl-ext)# hard-drop tcp host 10.0.0.3 host 224.0.0.1
count
device(conf-ipacl-ext)# exit
device(config)# ip receive access-group ipv4-receive-acl-example
Syntax
seq seq-value { permit | deny } ip-protocol { S_IPaddress mask | host
S_IPaddress | any } [ source-operator [ S_port-numbers ] ] [ TCP-
flags ] [ vlan vlanID ] [ count ] [ fragment | non-fragment ]
no seq seq-value
{ permit | deny } ip-protocol { S_IPaddress mask | host S_IPaddress |
any } [ source-operator [ S_port-numbers ] ] [ TCP-flags ] [ count ]
[ vlan vlanID ] [ fragment | non-fragment ]
no { permit | deny } ip-protocol { S_IPaddress mask | host S_IPaddress |
any } [ source-operator [ S_port-numbers ] ] [ TCP-flags ] [ vlan
vlanID ] [ count ] [ fragment | non-fragment ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq
seq-value, the rule is added at the end of the list.
seq-value
Valid values range from 1 through 65535.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
For bACLs, equivalent to deny.
ip-protocol
Indicates the type of IP packet you are filtering. The options are as follows:
<0-255>
Protocol number custom value from 0 through 255.
icmp
Internet Control Message Protocol
ip
Any IP protocol
tcp
(Supported only if the containing ACL is applied to incoming traffic) Transmission Control
Protocol
udp
fin
Filters packets for which the fin (finish) flag is set.
rst
Filters packets for which the rst (reset) flag is set.
sync
Filters packets for which the syn (synchronize) flag is set.
urg
Filters packets for which the urg (urgent) flag is set.
push
Filters packets for which the psh (push) flag is set.
count
Enables statistics for the rule.
log
Not supported for bACLs.
mirror
Not supported for bACLs.
copy-sflow
Not supported for bACLs.
fragment
Filter fragmented packets. This keyword and non-fragment keyword cannot be used together.
non-fragment
Filter non-fragmented packets. This keyword and fragment keyword cannot be used together.
Modes
ACL configuration mode
Usage Guidelines
This topic describes filtering rules in an extended IPv4 ACL intended for use as an IP broadcast ACL
(bACL).
Broadcast ACLs are not supported on SLX 9150 or SLX 9250 devices.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When
creating rules, specifying sequence values determines the order of rule processing. If you do not specify
a sequence value, the rule is added to the end of the list.
• Classless Interdomain Routing (CIDR) format—in which you specify the number of bits of the prefix.
For example, appending /24 to an IPv4 address is equivalent to specifying 0.0.0.255 as wildcard
mask format.
Filtering fragmented or non-fragmented packets is only supported on ingress ACLs. On the SLX 9540
and SLX 9640, fragment match is only supported on BGP FS profile. This ACL can also be used with
RACL, PBR, and RL. Do not use Layer-4 matching along with fragment matching. Fragmented packets
might not have Layer-4 information and most likely cause issues. ACL filtering of fragmented and non-
fragmented packets is not supported on SLX 9150 and SLX 9250 devices.
Examples
The following example creates an IPv4 extended bACL, defines rules for it, and applies the bACL to an
interface.
device# configure
device(config)# ip access-list extended bACL_ext_12
device(conf-ipacl-ext)# seq 5 deny tcp host 10.24.26.145 any eq 23
device(conf-ipacl-ext)# seq 7 deny tcp any any eq 80
device(conf-ipacl-ext)# seq 10 deny udp any any range 10 25
device(conf-ipacl-ext)# seq 15 permit tcp any any
device(conf-ipacl-ext)# exit
device(config)# interface ethernet 0/6
device(conf-if-eth-0/6)# ip subnet-broadcast-acl bACL_ext_12
The following example creates an IPv4 extended bACL, defines rules for it, and applies the bACL at
device level.
device# configure
device(config)# ip access-list extended bACL_ext_22
device(conf-ipacl-ext)# seq 5 deny tcp host 10.24.26.145 any eq 23
device(conf-ipacl-ext)# seq 7 deny tcp any any eq 80
device(conf-ipacl-ext)# seq 10 deny udp any any range 10 25
device(conf-ipacl-ext)# seq 15 permit tcp any any
device(conf-ipacl-ext)# exit
device(config)# ip global-subnet-broadcast-acl bACL_ext_22
Syntax
seq seq-value { permit | deny | hard-drop } { S_IPaddress mask | host
S_IPaddress | any } [ count ] [ log ] [ copy-sflow ]
no seq seq-value
{ permit | deny | hard-drop } { S_IPaddress mask | host S_IPaddress |
any } [ count ] [ log ] [ copy-sflow ]
no { permit | deny | hard-drop } { S_IPaddress mask | host S_IPaddress |
any } [ count ] [ log ] [ copy-sflow ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq
seq-value, the rule is added at the end of the list.
seq-value
Valid values range from 1 through 65535.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a
permit for this address in a preceding rule.
S_IPaddress
Specifies a source address for which you want to filter the subnet.
mask
Defines a mask, whose effect is to specify a subnet that includes the source address that you
specified. For options to specify the mask, see the Usage Guidelines.
host
Specifies a source address.
S_IPaddress
The source address.
any
Specifies all source addresses.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule. In addition, the ACL log buffer must be enabled, using the
debug access-list-log buffer command.
copy-sflow
For incoming traffic, sends matching packets to the sFlow collector.
Modes
ACL configuration mode
Usage Guidelines
This command configures rules to permit or drop traffic based on source addresses. You can also enable
counters, logging, and sFlow.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When
creating rules, specifying sequence values determines the order of rule processing. If you do not specify
a sequence value, the rule is added to the end of the list.
Although in a standard-ACL rule you can specify both log and copy-sflow, only one of the two is
processed, as follows:
• In a permit rule, only copy-sflow is processed.
• In a deny or hard-drop rule, only log is processed.
If you are defining rules for a QoS ACL, be aware of the following considerations for ACLs implemented
under flow-based QoS. For details, refer to the Extreme SLX-OS QoS and Traffic Management
Configuration Guide.
• Do not include the count keyword in ACLs intended for flow-based QoS implementation, because
such ACLs automatically share a common counter.
• The deny keyword functions as a "pass-through": For a match, QoS action defined for that class is
not applied.
Examples
The following example shows how to create a IPv4 standard ACL, define rules for it, and apply the ACL
to an interface:
device# configure
device(config)# ip access-list standard stdACL3
device(conf-ipacl-std)# seq 5 permit host 10.20.33.4
device(conf-ipacl-std)# seq 15 deny any
device(conf-ipacl-std)# exit
device(config)# interface ethernet 0/5
device(conf-if-eth-0/5)# ipv4 access-group stdACL3 in
Syntax
seq seq-value { permit | deny | hard-drop } ip-protocol { any |
S_IPaddress / prefix_len | host S_IPaddress } [ source-operator
[ S_port-numbers ] ] [ tcp/udp-flags ] [ vlan vlanID ] [ count ]
[ log ] [ mirror ] [ copy-sflow ] [ connlimit connlimit-value ]
no seq seq-value
{ permit | deny | hard-drop } ip-protocol { any | S_IPaddress /
prefix_len | host S_IPaddress } [ source-operator [ S_port-
numbers ] ] [ tcp/udp-flags ] [ vlan vlanID ] [ count ] [ log ]
[ mirror ] [ copy-sflow ] [ connlimit connlimit-value ]
no { permit | deny | hard-drop } ip-protocol { any | S_IPaddress /
prefix_len | host S_IPaddress } [ source-operator [ S_port-
numbers ] ] [ tcp/udp-flags ] [ vlan vlanID ] [ count ] [ log ]
[ mirror ] [ copy-sflow ] [ connlimit connlimit-value ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq
seq-value, the rule is added at the end of the list.
seq-value
Valid values range from 1 through 65535.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a
permit for this address in a preceding rule.
ip-protocol
Indicates the type of IP packet you are filtering. The options are as follows:
<0-255>
Protocol number custom value from 0 through 255.
ipv6-icmp
Internet Control Message Protocol
ipv6
Any IP protocol
tcp
Modes
ACL configuration mode
Usage Guidelines
IPv6 extended ACLs permit or deny traffic according to source address, as well as other parameters.
The order of the rules in an ACL is critical, because the first matching rule stops further processing.
When you create rules, specify the sequence values to determine the order of rule processing. If you do
not specify a sequence value, the rule is added to the end of the list.
You can abbreviate an IPv6 address by using one or more of the following rules:
• Remove one or more leading zeros from one or more groups of hexadecimal digits, usually for all or
none of the leading zeros. (For example, convert the group 0042 to 42.)
• Omit consecutive sections of zeros, using a double colon (::) to denote the omitted sections. The
double colon is used only once in any given address. The address would be indeterminate if the
double colon were used multiple times. A double colon cannot be used to denote one omitted
section of zeros. (For example, 2001:db8::1:2 is valid, but 2001:db8::1::2 or 2001:db8::1:1:1:1:1 is not
permitted.)
Although in an extended-ACL rule you can include log, mirror, and copy-sflow, only one of the
three is processed, as follows:
• In a permit rule, the order of precedence is mirror > copy-sflow > log.
• In a deny or hard-drop rule, the order of precedence is log > copy-sflow > mirror.
Filtering fragmented or non-fragmented packets is only supported on ingress ACLs. For IPv6 frames,
filtering is only supported if the fragment is the first extension header. Use protocol number 44 for
fragmented extension header. ACL filtering of fragmented and non-fragmented packets is not
supported on SLX 9150 and SLX 9250 devices.
Examples
The following example creates an IPv6 extended ACL, defines a rule for it, and applies the ACL to an
interface.
device# configure
device(config)# ipv6 access-list extended ip_acl_1
device(conf-ip6acl-ext)# seq 10 deny ipv6 2001:2002:1234:1::/64
2001:1001:1234:1::/64 count
device(conf-ip6acl-ext)# exit
device(config)# interface ethernet 0/5
device(conf-if-eth-0/5)# ipv6 access-group ip_acl_1 in
The following example creates an IPv6 extended ACL, defines rules in the ACL, and applies it as a
receive-path ACL (rACL).
device(conf-ip6acl-ext)# exit
The following example creates an IPv6 extended ACL for permitting fragmented packets.
Syntax
seq seq-value { deny | permit | hard-drop } { any | A:B:C:D:E:F:H:I /
prefix_len | host S_IPaddress } [ count ] [ log ] [ copy-sflow ]
no seq seq-value
{ deny | permit | hard-drop } { any | A:B:C:D:E:F:H:I / prefix_len |
host SIP_address | SIP_addressmask } [ count ] [ log ] [ copy-sflow ]
no { deny | permit | hard-drop } { any | A:B:C:D:E:F:H:I / prefix_len |
host SIP_address | SIP_addressmask } [ count ] [ log ] [ copy-sflow ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq
seq-value, the rule is added at the end of the list.
seq-value
Valid values range from 1 through 65535.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Overrides the trap behavior for control frames. However, hard-drop does not override a
permit for this address in a preceding rule.
any
Specifies all source addresses.
S_IPaddress
Specify a source address for which you want to filter the subnet. For options to abbreviate the
address, see the Usage Guidelines.
prefix_len
Indicates how many of the high-order, contiguous bits of the address comprise the IPv6 prefix.
host
Specifies a source address.
SIP_address
The source address. For options to abbreviate the address, see the Usage Guidelines.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule. In addition, the ACL log buffer must be enabled, using the
debug access-list-log buffer command.
copy-sflow
For incoming traffic, sends matching packets to the sFlow collector..
Modes
ACL configuration mode
Usage Guidelines
This command configures rules to permit or drop traffic based on source addresses. You can also enable
counters and either logging or sFlow collection.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When
creating rules, specifying sequence values determines the order of rule processing. If you do not specify
a sequence value, the rule is added to the end of the list.
You can abbreviate an IPv6 address by using one or more of the following rules:
• Remove one or more leading zeros from one or more groups of hexadecimal digits; this is usually
done to either all or none of the leading zeros. (For example, convert the group 0042 to 42.)
• Omit consecutive sections of zeros, using a double colon (::) to denote the omitted sections. The
double colon may only be used once in any given address, as the address would be indeterminate if
the double colon were used multiple times. A double colon may not be used to denote an omitted
single section of zeros. (For example, 2001:db8::1:2 is valid, but 2001:db8::1::2 or 2001:db8::1:1:1:1:1 are
not permitted.)
Although in a standard-ACL rule you can specify both log and copy-sflow, only one of the two is
processed, as follows:
• In a permit rule, only copy-sflow is processed.
• In a deny or hard-drop rule, only log is processed.
Filtering fragmented or non-fragmented packets is only supported on ingress ACLs. For IPv6 frames,
filtering is only supported if the fragment is the first extension header. Use protocol number 44 for
fragmented extension header. ACL filtering of fragmented and non-fragmented packets is not
supported on SLX 9150 and SLX 9250 devices.
Examples
The following example shows how to create an IPv6 standard ACL and define rules for it.
device# configure terminal
device(config)# ipv6 access-list standard ipv6-std-acl
device(conf-ip6acl-std)# seq 10 permit host 0:1::1
device(conf-ip6acl-std)# seq 20 deny 0:2::/64
device(conf-ip6acl-std)# seq 30 hard-drop any count
The following example creates an IPv6 standard ACL for permitting fragmented packets.
Syntax
seq seq-value { permit | deny } { S_IPaddress mask | host S_IPaddress |
any } [ count ] [ fragment | non-fragment ]
no seq seq-value
{ permit | deny } { S_IPaddress mask | host S_IPaddress | any }
[ count ] [ fragment | non-fragment ]
no { permit | deny } { S_IPaddress mask | host S_IPaddress | any }
[ count ] [ fragment | non-fragment ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq
seq-value, the rule is added at the end of the list.
seq-value
Valid values range from 1 through 65535.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
For bACLs, equivalent to deny.
S_IPaddress
Specifies a source address for which you want to filter the subnet.
mask
Defines a mask, whose effect is to specify a subnet that includes the source address that you
specified. For options to specify the mask, see the Usage Guidelines.
host
Specifies a source address.
S_IPaddress
The source address.
any
Specifies all source addresses.
count
Enables statistics for the rule.
log
Not supported for bACLs.
copy-sflow
Not supported for bACLs.
fragment
Filter fragmented packets. This keyword and non-fragment keyword cannot be used together.
non-fragment
Filter non-fragmented packets. This keyword and fragment keyword cannot be used together.
Modes
ACL configuration mode
Usage Guidelines
This topic describes filtering rules in a standard IPv4 ACL intended for use as an IP broadcast ACL
(bACL).
Broadcast ACLs are not supported on SLX 9150 or SLX 9250 devices.
This command configures rules to permit or drop traffic based on source addresses. You can also enable
counters.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When
creating rules, specifying sequence values determines the order of rule processing. If you do not specify
a sequence value, the rule is added to the end of the list.
Filtering fragmented or non-fragmented packets is only supported on ingress ACLs. On the SLX 9540
and SLX 9640, fragment match is only supported on BGP FS profile. This ACL can also be used with
RACL, PBR, and RL. Do not use Layer-4 matching along with fragment matching. Fragmented packets
might not have Layer-4 information and most likely cause issues. ACL filtering of fragmented and non-
fragmented packets is not supported on SLX 9150 and SLX 9250 devices.
Examples
The following example creates an IPv4 standard bACL, defines rules for it, and applies the bACL to an
interface.
device# configure
device(config)# ip access-list standard bACL_int_3
device(conf-ipacl-std)# seq 5 permit host 10.20.33.4
device(conf-ipacl-std)# seq 15 deny any
device(conf-ipacl-std)# exit
device(config)# interface ethernet 0/5
device(conf-if-eth-0/5)# ip subnet-broadcast-acl bACL_int_3
The following example shows how to create a IPv4 standard bACL, define rules for it, and apply the ACL
at device level.
device# configure
device(config)# ip access-list standard bACL_glb_9
device(conf-ipacl-std)# seq 5 permit host 10.20.33.4
device(conf-ipacl-std)# seq 15 deny any
device(conf-ipacl-std)# exit
device(config)# ip global-subnet-broadcast-acl bACL_glb_9
Syntax
[ seq seq-value ] permit { any | SMAC-address mask | host SMAC-address }
{ any | host DMAC-address | DMAC-address mask } [ known-unicast-
only ] [ vlan { any | vlanID } ] [ custom-EtherType | arp [ arp-
guard ] | cfm | ipv4 | ipv6 | mpls ] [count ] [ log ] [ mirror ]
[ copy-sflow ]
[ seq seq-value ] permit { any | SMAC-address mask | host SMAC-address }
{ any | host DMAC-address | DMAC-address mask } [ known-unicast-
only ] [ vlan-tag-format { untagged vlan vlan-id | single-tagged vlan
{ any | vlan-id [ vlan-id-mask ] } | double-tagged outer-vlan { any |
vlan-id [ vlan-id-mask ] } inner-vlan { any | vlan-id [ vlan-id-
mask ] } ] [ custom-EtherType | arp [ arp-guard ] | cfm | ipv4 | ipv6
| mpls ] [count ] [ log ] [ mirror ] [ copy-sflow ]
[ seq seq-value ] { deny | hard-drop } { any | SMAC-address mask | host
SMAC-address } { any | host DMAC-address | DMAC-address mask }
[ known-unicast-only ] [ vlan { any | vlanID } ] [ custom-EtherType |
arp [ arp-guard ] | cfm | ipv4 | ipv6 | mpls ] [ count ] [ log ]
[ mirror ] [ copy-sflow ]
[ seq seq-value ] { deny | hard-drop } { any | SMAC-address mask | host
SMAC-address } { any | host DMAC-address | DMAC-address mask }
[ known-unicast-only ] [ vlan-tag-format { untagged vlan vlan-id |
single-tagged vlan { any | vlan-id [ vlan-id-mask ] } | double-tagged
outer-vlan { any | vlan-id [ vlan-id-mask ] } inner-vlan { any |
vlan-id [ vlan-id-mask ] } ] [ custom-EtherType | arp [ arp-guard ] |
cfm | ipv4 | ipv6 | mpls ] [ count ] [ log ] [ mirror ] [ copy-
sflow ]
no seq seq-value
no permit { any | SMAC-address mask | host SMAC-address } { any | host
DMAC-address | DMAC-address mask } [ known-unicast-only ] [ vlan
{ any | vlanID } ] [ custom-EtherType | arp [ arp-guard ] | cfm |
ipv4 | ipv6 | mpls ] [count ] [ log ] [ mirror ] [ copy-sflow ]
no permit { any | SMAC-address mask | host SMAC-address } { any | host
DMAC-address | DMAC-address mask } [ known-unicast-only ] [ vlan-tag-
format { untagged vlan vlan-id | single-tagged vlan { any | vlan-id
[ vlan-id-mask ] } | double-tagged outer-vlan { any | vlan-id [ vlan-
id-mask ] } inner-vlan { any | vlan-id [ vlan-id-mask ] } ] [ custom-
EtherType | arp [ arp-guard ] | cfm | ipv4 | ipv6 | mpls ] [count ]
[ log ] [ mirror ] [ copy-sflow ]
no { deny | hard-drop } { any | SMAC-address mask | host SMAC-address }
{ any | host DMAC-address | DMAC-address mask } [ known-unicast-
only ] [ vlan { any | vlanID } ] [ custom-EtherType | arp [ arp-
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq
seq-value, the rule is added at the end of the list.
seq-value
Valid values range from 1 through 65535.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Specifies rules to deny traffic.
any
Specifies any source MAC addresses.
SMAC-address
Specifies a source MAC address and a comparison mask.
mask
Specifies the mask using Fs and zeros. For example, to match on the first two bytes of the
address aabb.ccdd.eeff, use the mask ffff.0000.0000. In this case, the clause matches all MAC
addresses that contain "aabb" as the first two bytes and any values in the remaining bytes.
host SMAC-address
Specifies a source MAC address. Use the format HHHH.HHHH.HHHH.
any
Specifies any destination MAC addresses.
DMAC-address
Specifies a destination MAC address and a comparison mask.
mask
Specifies the mask using Fs and zeros. For example, to match on the first two bytes of the
address aabb.ccdd.eeff, use the mask ffff.0000.0000. In this case, the clause matches all MAC
addresses that contain "aabb" as the first two bytes and any values in the remaining bytes.
host DMAC-address
Modes
ACL configuration mode
Usage Guidelines
This command configures rules to permit or drop traffic based on source and destination MAC
addresses and protocol type. You can also enable counters, logging, mirroring , and sending packets to
the sFlow collector per rule.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When
creating rules, specifying sequence values determines the order of rule processing. If you do not specify
a sequence value, the rule is added to the end of the list.
Although in an extended-ACL rule you can include log, mirror, and copy-sflow, only one of the
three is processed, as follows:
• In a permit rule, the order of precedence is mirror > copy-sflow > log.
• In a deny or hard-drop rule, the order of precedence is log > copy-sflow > mirror.
The following guidelines apply to rules that contain one of the vlan-tag-format options:
• Supported only when an ACL containing such rules is applied to physical or port-channel interfaces
for ingress traffic. Ignored for ACLs applied to egress traffic and for ACLs applied to VLANs.
• (DNX devices only) The double-tagged option is supported only for VPLS VLANs. The
untagged and the single-tagged options are supported for all VLANs.
• An implicit LACP BPDU permit rule precedes the implicit deny rule. But to avoid port-channel
interface flap for VPLS endpoints over dynamic LAGs, make sure that the LACP BPDUs do not match
any of the configured deny rules.
To enable ARP Guard on an interface, you create and apply a MAC extended ACL with rules that contain
the arp and arp-guard keywords. ARP Guard is supported on devices based on the DNX chipset
family. For a list of such devices, see "Supported Hardware".
Examples
The following example creates a rule in a MAC extended ACL to deny IPv4 traffic from the source MAC
address 0022.3333.4444 to the destination MAC address 0022.3333.5555 and enable packet counting.
device# configure terminal
device(config)# mac access-list extended ACL1
device(conf-macl-ext)# seq 100 deny 0022.3333.4444 0022.3333.5555 ipv4 count
The following example creates rule in a MAC extended ACL to filter permit traffic by VLAN tag types
and enable packet counting.
device# configure terminal
device(config)# mac access-list extended ACL1
The following example creates an MAC extended ACL with rules that enable ARP Guard and then
applies it to the relevant interface.
device# configure terminal
device(config)# mac access-list extended arp_guard_enable_1
device(conf-macl-ext)# permit host 0014.2211.1111 any vlan 100 arp arp-guard
device(conf-macl-ext)# permit host 0014.2211.1112 any vlan 101 arp arp-guard
device(conf-macl-ext)# deny any any arp
device(conf-macl-ext)# permit any any
device(conf-macl-ext)# exit
Syntax
seq seq-value { deny | permit | hard-drop } { any | SMAC_address mask |
host SMAC_address } [count ] [ log ] [ copy-sflow ]
no seq seq-value
{ deny | permit | hard-drop } { any | SMAC_address mask | host
SMAC_address } [count ] [ log ] [ copy-sflow ]
no seq { deny | permit | hard-drop } { any | SMAC_address mask | host
SMAC_address } [count ] [ log ] [ copy-sflow ]
Parameters
seq
(Optional) Enables you to assign a sequence number to the rule. If you do not specify seq
seq-value, the rule is added at the end of the list.
seq-value
Valid values range from 1 through 65535.
permit
Specifies rules to permit traffic.
deny
Specifies rules to deny traffic.
hard-drop
Specifies rules to deny traffic.
any
Specifies all source MAC addresses.
SMAC_address
Specifies a source MAC address and a comparison mask.
mask
Specify the mask using F's and zeros. For example, to match on the first two bytes of the address
aabb.ccdd.eeff, use the mask ffff.0000.0000. In this case, the clause matches all MAC addresses
that contain "aabb" as the first two bytes and any values in the remaining bytes.
host
Specifies a source MAC address.
SMAC_address
Use the format HHHH.HHHH.HHHH.
count
Enables statistics for the rule.
log
Enables inbound logging for the rule. In addition, the ACL log buffer must be enabled, using the
debug access-list-log buffer command.
copy-sflow
For incoming traffic, sends matching packets to the sFlow collector.
Modes
ACL configuration mode
Usage Guidelines
This command configures rules to permit or drop traffic based on source MAC address.
The order of the rules in an ACL is critical, as the first matching rule stops further processing. When
creating rules, specifying sequence values determines the order of rule processing. If you do not specify
a sequence value, the rule is added to the end of the list.
Although in a standard-ACL rule you can specify both log and copy-sflow, only one of the two is
processed, as follows:
• In a permit rule, only copy-sflow is processed.
• In a deny or hard-drop rule, only log is processed.
Examples
The following command creates statistic-enabled rules in a MAC standard ACL.
device# configure terminal
device(config)# mac access-list standard ACL1
device(conf-macl-std)# seq 100 deny host 0022.3333.4444 count
device(conf-macl-std)# seq 110 permit host 0011.3333.5555 count
The following command deletes a rule in a MAC standard ACL, by specifying the seq number.
device# configure terminal
device(config)# mac access-list standard ACL1
device(conf-macl-std)# no seq 100
service password-encryption
Enables a global password encryption policy that overrides username encryption settings.
Syntax
service password-encryption
no service password-encryption
Command Default
Global password encryption policy is enabled.
Modes
Global configuration mode
Usage Guidelines
If global password encryption policy is enabled, it overrides username encryption settings.
To disable global password encryption policy, enter the no form of this command.
Even if global password encryption policy is disabled, the following username syntax does encrypt
that user's password: encryption-level 10.
Examples
The following example enables global password encryption policy.
device# configure terminal
device(config)# service password-encryption
Syntax
service-policy in policy-mapname
no service-policy in
Command Default
No service policy is created.
Parameters
policy-mapname
Name of the policy map.
Modes
Control-plane configuration mode
Usage Guidelines
The policy map must be configured before you can apply it (refer to the description of the policy-
map command).
The no form of this command removes the service-policy map from the control plane.
Examples
The following example applies a policy map as a service policy to the control plane.
The following example removes a policy map from the control plane.
service-policy (interface)
Binds a policy map as a service policy to an interface.
Syntax
service-policy in | out policy-mapname
no service-policy in | out
Command Default
No service policy is created.
Parameters
in
Binds policy map to inbound traffic.
out
Binds policy map to outbound traffic.
policy-mapname
Name of the policy map.
Modes
Interface, Port Channel, and VE subtype configuration mode
Usage Guidelines
This command applies a policy-map containing a class-map with specific Policer parameters and match
critters to a device interface. The policy map must be configured before you can apply it (refer to the
description of the policy-map command).
Examples
To create a service policy for outbound traffic on a specific Ethernet interface:
device# configure terminal
device(config)# interface ethernet 2/8
device(conf-if-eth-2/8)# service-policy out policymap1
To remove a service policy for outbound traffic from a specific Ethernet interface:
device# configure terminal
device(config)# interface ethernet 2/8
device(conf-if-eth-2/8)# no service-policy out
This example configures IPV4 ACL based ingress rate-limiting on a VE interface. The show command
displays the current configuration for the interface.
SLX(config)# int ve 100
SLX(config-if-Ve-100)#
SLX(config-if-Ve-100)# service-policy in policy-map_1
SLX(config-if-Ve-100)#
This example configures IPV4 ACL based egress rate-limiting on a VE interface. The show command
displays the current configuration for the interface.
SLX(config)# int ve 100
SLX(config-if-Ve-100)#
SLX(config-if-Ve-100)# service-policy out policy-map_1
SLX(config-if-Ve-100)#
The following is the configuration for the Policy map used in the above two (2) examples.
ip access-list extended ipv4acl
seq 100 permit ip 10.10.10.10 255.255.255.0 10.10.10.20 255.255.255.0
class-map class-map_1
match access-group ipv4acl
policy-map policy-map_1
class class-map_1
Police cir 3000000 eir 300000000
session
Configures an LDP session for the neighbor-based filtering of inbound or outbound FECs, You can also
configure an authentication key for the LDP session.
Syntax
session remote-ip-addr { filter-fec-in | filter-fec-outprefix-list } |
{ key string }
no session remote-ip-addr { filter-fec-in | filter-fec-out } | { key }
Command Default
None
Parameters
remote-ip-addr
Specifies the IP address of the LDP peer.
filter-fec-in
Applies neighbor-based LDP FEC filtering on inbound FECs.
filter-fec-out
Applies neighbor-based LDP FEC filtering on outbound FECs.
prefix-list
Specifies the prefix list for the neighbor to which the filter is applied to allow or prevent the
advertisement of FECs.
key string
Configures an authentication key on the LDP session. The LDP session can be to an adjacent
peer (basic discovery) or to the targeted peer (extended discovery).The string variable specifies
a text string of up to 80 characters used for authentication between LDP peers. It must be
configured on both peers.
Modes
MPLS LDP configuration mode
Usage Guidelines
Use the no form of the command to remove the neighbor-based FEC filtering or authentication key
from the LDP session.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures LDP to prevent the advertisement of FEC 10.40.40.0/24 through the
list-out prefix list and allow all others FECs to neighbor 10.12.12.12.
device# configure terminal
device(config)# ip prefix-list list-out deny 10.40.40.0/24
device(config)# ip prefix-list list-out permit 0.0.0.0/0 ge 32
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# session 10.12.12.12 filter-fec-out list-out
set extcommunity
Sets an extended BGP community attribute in a route-map instance.
Syntax
set extcommunity { rt extcommunity value | soo extcommunity value }
no set extcommunity
Command Default
No extended BGP community attribute is set.
Parameters
rt
Specifies the route target (RT) extended community attribute.
soo
Specifies the site of origin (SOO) extended community attribute.
extcommunity value
Specifies the value. The value can be one of the following:
ASN:nn—autonomous-system-number:network-number
Autonomous system (AS) number and network number.
IPAddress:nn—ip-address:network-number
IP address and network number.
Modes
Route-map configuration mode.
Usage Guidelines
Enter no set extcommunity to delete an extended community set statement from the
configuration file.
Examples
The following example sets the route target to extended community attribute 1:1 for routes that are
permitted by the route map.
The following example sets the site of origin to extended community attribute 2:2 for routes that are
permitted by the route map.
set interface
Specifies an egress interface for a route-map.
Syntax
set interface { ethernet slot / port | null0 | port-channel number }
no set interface { ethernet slot / port | null0 | port-channel number }
Parameters
ethernet slot / port
Specifies an Ethernet interface. If the device does not have linecards, specify 0.
null0
Specifies the Null0 interface, dropping the packet.
port-channel number
Specifies a port-channel interface.
Modes
Route-map configuration mode
Usage Guidelines
The order of the set statements in a route-map is critical: In general, a match followed by a valid set
interface statement stops further processing. However a set interface NULL0 statement is
always processed last.
To delete a set interface statement from a route map, enter the no form of this command.
set ip dscp
Configures a Differentiated Services Code Point (DSCP) value for a route-map rule.
Syntax
set ip dscp dscp-value
no set ip dscp dscp-value
Command Default
A DSCP value is not configured.
Parameters
dscp-value
DSCP value. The valid range is from 0 through 63.
Modes
Route-map configuration mode
Usage Guidelines
The no form of the command removes the configuration.
Examples
The following example shows how to set a DSCP value of 23 for rule number 4 under a route map
named rm.
Syntax
set ip interface null0
no set ip interface null0
Modes
Route-map configuration mode
Usage Guidelines
If none of the configured next-hops or interfaces are up, this command drops the traffic.
Examples
The following example configures the next hop as NULL0 interface, dropping the packet instead of
forwarding it.
device(config)# route-map test-route permit 99
device(config-route-map-test-route/permit/99)# set ip interface null0
set ip mirror
Configures an IPv4 mirroring destination for a Border Gateway Protocol flow specification (BGP
flowspec) route-map rule.
Syntax
set ip mirror ip-address
no set ip mirror ip-address
Command Default
A mirroring destination is not configured.
Parameters
ip-address
Specifies the mirroring destination in IPv4 address format.
Modes
Route-map configuration mode
Usage Guidelines
To mirror to multiple destinations, you can configure multiple mirror destination addresses.
When mirroring is configured under a BGP flowspec rule, mirror destinations are advertised to BGP
neighbors but are not installed in the hardware.
Examples
The following example shows how to configure two mirroring destination addresses for IPv4 packets for
a BGP flowspec sequence number 4 under a route map named rm.
set ip next-hop
Sets the IPv4 address of the redirect next hop in a route-map instance.
Syntax
set ip next-hop { ip-address | peer-address }
set ip [ global | vrf vrf-name ] next-hop ip-address
no set ip next-hop ip-address
Parameters
global
Specifies that the specified next-hop address is to be resolved from the global routing table.
vrf vrf-name
Specifies using a VRF routing table to resolve the specified next-hop address.
ip-address
Specifies, in IPv4 address format, the next hop to which to route the packet. The next hop need
not be directly connected or reachable.
peer-address
Specifies, when configured, that the next hop is set to the neighbor peering address.
Modes
Route-map configuration mode
Usage Guidelines
The global and vrf options are not supported for BGP flowspec route maps.
When a route map applies to BGP flowspec, you can redirect traffic to multiple destinations by
configuring multiple set ip next-hop statements in a single route-map instance. However, when
the redirect next-hop holder is NLRI, only the first-configured next-hop IP address is advertised.
When the peer-address keyword is used when defining an inbound route map of a BGP peer, then the
next hop of the matching route will be set to the neighbor peer address. Similarly, when the peer-
address keyword is used when defining an outbound route map of a BGP peer, then the next hop of the
outbound route map will be configured with the peer address of the local router.
Examples
The following example configures an IPv4 address as the next hop to which traffic that matches a
match statement in the route map must be redirected.
SLX(config)# route-map test-route permit 99
SLX(config-route-map-test-route/permit/99)# set ip next-hop 192.168.3.1
The following example shows the configuration of the peer-address parameter when defining the next
hop.
SLX (config)# route-map test-route permit 99
SLX (config-route-map-test-route/permit/99)# set ip next-hop peer-address
Syntax
set ipv6 interface null0
no set ipv6 interface null0
Modes
Route-map configuration mode
Usage Guidelines
If none of the configured next-hops or interfaces are up, this command drops the traffic.
Examples
The following example configures the next hop as NULL0 interface to send the traffic to the null
interface, thus dropping the packet instead of forwarding it.:
device(config)# route-map test-route permit 99
device(config-route-map-test-route/permit/99)# set ipv6 interface null0
Syntax
set ipv6 next-hop { ipv6-address | peer-address }
set ipv6 [ global | vrf vrf-name ] next-hop ipv6-address
no set ipv6 next-hop ipv6-address
Parameters
ipv6-address
IPv6 address of the next hop.
global
Specifies that the next specified hop address is to be resolved from the global routing table.
vrf vrf-name
Specifies from which VRF routing table the specified next hop address will be resolved.
ipv6-address
Specifies, in IPv6 address format, the next hop to which to route the packet. The next hop need
not be directly connected or reachable.
peer-address
Specifies, when configured, that the next hop is set to the neighbor peering address.
Modes
Route-map configuration mode
Usage Guidelines
When the peer-address keyword is used when defining an inbound route map of a BGP peer, then the
next hop of the matching route will be set to the neighbor peer address. Similarly, when the peer-
address keyword is used when defining an outbound route map of a BGP peer, then the next hop of the
outbound route map will be configured with the peer address of the local router.
Examples
The following example configures IPv6 address as the next hop to which the traffic that matches a
match statement in the route map must be routed.
device(config)# route-map test-route permit 99
device(config-route-map-test-route/permit/99)# set ipv6 next-hop
2001:db8:0:0:0:ff00:42:8329
The following example shows the configuration of the peer-address parameter when defining the next
hop.
SLX (config)# route-map test-route permit 99
SLX (config-route-map-test-route/permit/99)# set ipv6 next-hop peer-address
set large-community
Advertises routes with BGP Large Community attributes.
Syntax
set large-community { ADMIN:OPER1:OPER2 } [additive ]
no set large-community
Command Default
No large community is set.
Parameters
ADMIN
A four-octet namespace identifier for a BGP Large-Communities Global Administrator.
OPER1
A four-octet operator-defined value for BGP Large-Communities Local Data Part 1.
OPER2
A four-octet operator-defined value for BGP Large-Communities Local Data Part 2.
additive
Appends updates to existing attributes. See the Usage Guidelines.
Modes
Route map configuration mode.
Usage Guidelines
The maximum number of BGP Large Community values that can be configured in a route-map instance
(per sequence number) is 32.
By default, this command replaces the BGP Large Community in the routes to which it is applied.
Examples
The following example sets a large-community list in a route-map instance.
device# configure terminal
device(config)# route-map myroutes permit 10
device(config-route-map-myroutes/permit/10)# set large-community 64497:1:528
The following example sets a large-community list in a route-map instance and appends updates to
existing attributes.
device# configure terminal
device(config)# route-map myroutes permit 10
device(config-route-map-myroutes/permit/10)# set large-community 64497:1:528 additive
Syntax
set large-community-list name delete
no set large-community-list name delete
Command Default
No large community access list is set.
Parameters
name
Name of a large community access list. Range is from 1 through 32 ASCII characters.
Modes
Route-map configuration mode
Usage Guidelines
Use the no form of this command to undelete BGP Large Community attributes specified in the access
list from the route update.
Examples
The following example sets a community list for deletion in a route-map instance.
device# configure terminal
device(config)# route-map myroutes permit 10
device(config-route-map-myroutes/permit/10)# set large-community-list
mylargecommunitylist delete
Syntax
set police cir cir-value
no set police cir
Command Default
A CIR value is not configured.
Parameters
cir-value
CIR value. Valid values are 0 (drop) and from 22000 through 300000000000 bits per second.
When the cir-value is set to a value in the range from 1 through 21999, matched data traffic is
dropped.
Modes
Route-map configuration mode.
Usage Guidelines
The no form of the command removes the configuration.
Examples
The following example shows how to set a CIR value to 1000 for BGP flowspec sequence number 4
under a route map named rm.
set sflow
Enables traffic sampling for a Border Gateway Protocol flow specification (BGP flowspec) route-map
rule.
Syntax
set sflow
no set sflow
Command Default
Traffic sampling is disabled.
Modes
Route-map configuration mode.
Usage Guidelines
The no form of the command restores the default configuration.
Examples
The following example shows how enable traffic sampling for sequence number 4 under a route map
named rm.
Syntax
set traffic-action continue
no set traffic-action continue
Command Default
By default, traffic evaluation stops after matching a rule.
Modes
Route-map configuration mode
Usage Guidelines
The set traffic-action continue command sets the traffic action to continue to evaluate
traffic against subsequent filtering rules as defined by the ordering procedure. When set traffic-
action continue is not configured, traffic evaluation stops after matching a rule.
The no form of the command restores the default configuration; that is, traffic evaluation stops after
matching a rule.
Examples
The following example shows how to set the traffic action to continue for sequence number 4 in a
route map named rm.
set-debug
Enables debug configurations for Intermediate System-to-Intermediate System (IS-IS).
Syntax
set-debug nsr
no set-debug nsr
Command Default
Disabled.
Parameters
nsr
Specifies nonstop routing (NSR) debugs.
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables NSR debug configurations for IS-IS.
device# configure terminal
device(config)# router isis
device(config-isis-router)# set-debug nsr
set-overload-bit
Configures a device to signal other devices not to use it as an intermediate hop in their shortest path
first (SPF) calculations if the resources of the intermediate system are overloaded and preventing the IS
from properly performing Intermediate System-to-Intermediate System (IS-IS) routing.
Syntax
set-overload-bit
set-overload-bit on-startup value
set-overload-bit on-startup wait-for-bgp [ max-bgp-wait-time ]
no set-overload-bit
no set-overload-bit on-startup interval
no set-overload-bit on-startup wait-for-bgp [ max-bgp-wait-time ]
Command Default
A device automatically sets the overload on in its Link State PDUs (LSPs) to other intermediate systems
if an overload condition occurs.
Parameters
on-startup
Sets the overload bit when the system starts up. The overload bit remains set for the number of
seconds configured or until Border Gateway Protocol (BGP) has converged, depending on the
subsequent argument or keyword specified.
interval
Specifies the number of seconds the overload bit remains set when the system starts up. Valid
values range from 5 through 86400 seconds (24 hours).
wait-for-bgp
Specifies that the overload bit is set when the system starts up and remains set until BGP has
converged.
max-bgp-wait-time
Specifies the maximum time in seconds that IS-IS waits for BGP convergence to complete. When
the configured time interval is exceeded without BGP convergence, IS-IS exits the overload state.
Valid values range from 5 seconds through 86400 seconds (24 hours). The default is 600
seconds (10 minutes).
Modes
IS-IS router configuration mode
Usage Guidelines
The no form of the command removes the configured overload state.
Examples
The following example sets the overload bit to on with immediate effect.
The following example configures the device to set the overload bit on in all its IS-IS LSPs sent to other
ISs during the first five seconds following a successful software reload. After the five seconds expire, the
device resets the overload bit to off in all its IS-IS LSPs.
The following example specifies that the overload bit is set upon system startup and remains set until
BGP has converged and specifies that the device that 86400 seconds is the maximum time that IS-IS
will wait for BGP convergence to complete.
sflow agent-address
Configures the sFlow agent-ID address.
Syntax
sflow agent-address { ipv4 | ipv6 [ ethernet slot/plot | loopback
loopback-number | management mgmt-id | ve ve-inteface ] }
no sflow agent-address
Command Default
By default the sflow agent address is not configured.
Parameters
ipv4
Specifies an agent-address configuration for IPv4 collectors.
ipv6
Specifies an agent-address configuration for IPv6 collectors.
ethernet slot/plot
Specifies an Ethernet slot and port. The only supported slot value on the fixed form factor SLX
devices is 0.
loopback loopback-number
Specifies a loopback interface. Valid values range from 1 through 255.
management mgmt-id
Specifies the management interface. The only supported value is 0.
ve ve-inteface
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to remove the sFlow agent address configuration.
Examples
The following example configures the sFlow agent-address globally. That is, it applies to all IPv4
collectors.
device# configure terminal
device(config)# sflow agent-address ipv4 ethernet 0/5
sflow collector
Configures the forwarding of sFLow datagrams to collectors.
Syntax
sflow collector { IPv4address | IPv6address } [ use-vrf vrf-name ]
no sflow collector { IPv4address | IPv6address } [ use-vrf vrf-name ]
Parameters
IPv4address
Specifies an IPv4 address in dotted-decimal format for the collector.
IPv6address
Specifies an IPv6 address for the collector.
use-vrf vrf-name
Specifies a VRF through which to connect to the collector. See the Usage Guidelines.
Modes
Global configuration mode
Usage Guidelines
You can only specify up to five sFlow collectors; this includes all VRFs.
Use the no form of this command to reset the specified collector address to a null value.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default
VRF ("default-vrf").
Examples
To specify the sFlow collectors for an IPv4 address with the default port on the management VRF:
device# configure terminal
device(config)# sflow collector 192.10.138.176
To specify the sFlow collectors for an IPv4 address with a nondefault port on a user-specified VRF:
device# configure terminal
device(config)# sflow collector 192.10.138.176 50 use-vrf myvrf
To specify the sFlow collectors for an IPv6 address with a nondefault port on the management VRF:
device# configure terminal
device(config)# sflow collector 3ff3:1900:4545:3:200:f8ff:fe21:67cf:6343 50
Syntax
sflow enable
no sflow enable
Command Default
sFlow is disabled on the system.
Modes
Global configuration mode
Usage Guidelines
The no form of this command disable sFlow globally.
Examples
To enable sFlow globally:
device# configure terminal
device(config)# sflow enable
Syntax
sflow polling-interval interval_value
no sflow polling-interval
Parameters
interval_value
Specifies a value in seconds to set the polling interval. Valid values range from 1 through 65535
seconds.
Command Default
The default is 20.
Modes
Global configuration mode
Usage Guidelines
The interval is the maximum number of seconds between successive samples of counters to be sent to
the collector.
Examples
To set the polling interval to 135 seconds:
device# configure terminal
device(config)# sflow polling-interval 135
Syntax
sflow sample-rate samplerate
no sflow sample-rate
Command Default
The default is 32768.
Parameters
samplerate
Specifies the sampling rate value in packets. Valid values range from 2 through 16777215 packets.
Modes
Global configuration mode
Usage Guidelines
Sample-rate is the average number of packets skipped before the sample is taken.
Examples
To change the sampling rate to 4096:
device# configure terminal
device(config)# sflow sample-rate 4096
sflow source-interface
Specifies to pick the IPv4 or IPv6 address of either the Ethernet, Virtual Ethernet (ve), management, or
loopback interface as the source of sFlow packets.
Syntax
sflow source-interface { ethernet slot/port | loopback loopback_num |
management mgmt-id | ve ve_interface }
no sflow source-interface
Command Default
By default, sFlow uses the management port IP address as the source IP.
Parameters
ethernet slot/port
Specifies an Ethernet slot and port. The only supported slot value on the fixed form factor SLX
devices is 0.
loopback loopback_num
Specifies a loopback interface. Valid values range from 1 through 255.
management mgmt-id
Specifies the management interface. The only supported value is 0.
ve ve-interface-number
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
Modes
Global configuration mode
Usage Guidelines
The no form of the command is available after the source type has been specified.
• The sFlow source IP (source interface) configurations are not applicable to sFlow collectors that are
reachable through the management port unless the specified source interface falls in the
management VRF.
• The show sflow command displays the source interface field only when it is configured.
Examples
To specify the Ethernet address as the source of sFlow packets:
device# config
device(config)# sflow source-interface ethernet 0/1
shutdown (link-oam)
Allows you to enable or disable the link-oam protocol.
Syntax
shutdown
no shutdown
Command Default
This command is executed on the local switch.
Modes
Link OAM configuration mode
Usage Guidelines
By default, link oam protocol is enabled when protocol link-oam is configured. Using this command, the
protocol can be disabled or enabled.
Examples
device(config-link-oam)# shutdown
shutdown (STP)
Disables Spanning Tree Protocol (STP), Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree
Protocol (MSTP), Per-VLAN Spanning Tree+ (PVST+), or Rapid PVST+ (R-PVST+) globally.
Syntax
shutdown
no shutdown
Command Default
STP is not enabled as it is not required in a loop-free topology.
Modes
Any of the supported spanning tree configuration modes (STP, RSTP, MSTP, PVST+, R-PVST+)
Usage Guidelines
Enter no shutdown to re-enable any of the supported versions of STP.
Examples
To disable RSTP globally:
shutdown-time
Configures the interval after which an interface that is shut down by loop detection (LD) protocol is
automatically reenabled.
Syntax
shutdown-time minutes
no shutdown-time
Command Default
See the Usage Guidelines.
Parameters
minutes
The interval in minutes. Range is from 0 through 1440. The default is 0. (The interface is not
automatically reenabled.)
Modes
Protocol Loop Detect configuration mode.
Usage Guidelines
Use the no form of this command to revert to the default interval and prevent the interface from being
automatically reenabled.
Examples
To specify a shutdown time of 20 minutes:
device# configure terminal
device(config)# loop-detection
device(config-loop-detect)# shutdown-time 20
To revert to the default interval and prevent the interface from being automatically reenabled:
device# configure terminal
device(config)# loop-detection
device(config-loop-detect)# no shutdown-time
show access-list
Displays ACL information for an ACL type and inbound and outbound directions. You can show
information for a specific ACL or only for that ACL on a specific interface. You can also display
information for all ACLs bound to an interface.
Syntax
show access-list { ip | ipv6 | mac }
show access-list { ip | ipv6 | mac } acl-name { in | out }
show access-list interface { ethernet slot / port | port-channel index |
ve vlan_id | vlan vlan_id } { in | out }
show access-list interface management mgmt-id in
show access-list mac acl-name interface { ethernet slot / port | port-
channel index | vlan vlan_id } { in | out }
show access-list { ip | ipv6 } acl-name interface { ethernet slot / port
| port-channel index | ve vlan_id } { in | out }
show access-list { ip | ipv6 } acl-name interface management mgmt-id in
show access-list global-subnet-broadcast ip acl-name
show access-list subnet-broadcast ip [ acl-name[ interface { ethernet
slot / port | ve vlan-id } ] ]
show access-list receive { ip | ipv6 } acl-name
Parameters
ip
Specifies the IPv4 Layer 3 network protocol.
ipv6
Specifies the IPv6 Layer 3 network protocol.
mac
Specifies the medium access control (MAC) Layer 2 network protocol.
in
Specifies the incoming binding direction.
out
Specifies the outgoing binding direction.
acl-name
Specifies the ACL name.
interface
Filters by interface.
ethernet
Modes
Privileged EXEC mode
Usage Guidelines
You can show information for a specified ACL or only for that ACL on a specified interface. You can also
display information for all ACLs bound to a specified physical interface, port-channel, VLAN or VE.
Output
The show access-list command displays the following information:
Examples
The following example displays the names of IPv4 ACLs applied to the device, interfaces to which they
are applied, and the incoming/outgoing direction.
device# show access-list ip
Interface Ve 171
Inbound access-list is not set
Outbound access-list is IPV4_ACL_000 (From User)
Interface Ethernet 1/2
Inbound switched access-list is IP_ACL_STD_EXAMPLE (From User)
Outbound access-list is IP_ACL_EXT_EXAMPLE (From User)
The following example displays all interfaces on which an IPv4 ACL is applied in the outgoing direction.
device# show access-list ip IPV4_ACL_000 out
ip access-list IPV4_ACL_000 on Ve 171 at Egress (From User)
seq 10 deny ip host 0.0.0.0 host 10.0.0.0 (Active)
The following example displays all interfaces on which an IPv6 ACL is applied in the incoming direction.
device# show access-list ipv6 distList in
ipv6 access-list distList on Ethernet 1/4 at Ingress (From User)
seq 10 deny 2001:125:132:35::/64 (Active)
seq 20 deny 2001:54:131::/64 (Active)
seq 30 deny 2001:5409:2004::/64 (Active)
seq 40 permit any (Active)
The following example displays all ACLs applied on a specified interface in the incoming direction.
device# show access-list interface ethernet 1/4 in
ipv6 access-list ipv6-std-acl on Ethernet 1/4 at Ingress (From User)
seq 10 permit host 0:1::1 (Active)
seq 20 deny 0:2::/64 (Active)
seq 30 hard-drop any count (Active)
This example displays permit and deny rules configured for control plane protection.
device# show access-list receive ip ip-ssh
ip access-list extended ip-ssh
seq 5 deny tcp any 14.14.14.14 0.0.0.0 eq 22 count (Active)
seq 10 permit tcp 10.10.10.10 0.0.0.255 any eq 22 count (Active)
seq 20 permit tcp 11.11.11.11 0.0.0.255 any eq 22 count (Active)
seq 100 deny tcp any any eq 22 count (Active)
The following example displays an ACL definition that supports filtering non-fragmented packets.
device# show access-list interface ethernet 0/7 in
ip access-list new_acl on Ethernet 0/7 at Ingress (From User)
seq 10 permit ip any any non-fragment count (Active)
The following example displays an ACL definition that supports filtering fragmented packets.
device# show access-list int eth 0/8 in
ip access-list test on Ethernet 0/8 at Ingress (From User)
seq 10 permit ip any any fragment (Active)
The following example displays an ACL definition that supports flow based ingress miroring.
device# show access-list int eth 0/2 in
ip access-list mac1 on Ethernet 0/2 at Ingress (From User)
seq 10 permit any host 1111.2222.3333 count mirror (Active)
seq 20 permit host 4444.5555.6666 any count (Active)
The following example displays an ACL definition that supports flow based egress miroring.
device# show access-list int eth 0/1 out
ip access-list mac1 on Ethernet 0/1 at Egress (From User)
seq 10 permit any host 1111.2222.3333 count mirror (Active)
seq 20 permit host 4444.5555.6666 any count (Active)
Syntax
show access-list overlay transit overlay-transit-name
Parameters
overlay-transit-name
Specifies the name of the overlay transit.
Modes
Privileged EXEC mode
Usage Guidelines
Overlay ACLs are not supported on SLX 9150 or SLX 9250 devices.
Examples
device# show access-list overlay transit tr_name
Overlay Transit Global Binding
Inbound access-list is abc_ext (From User)
Outbound access-list is not set
Syntax
show access-list overlay type vxlan acl-name acl-name
Parameters
acl-name
Specifies an overlay VXLAN ACL name.
Modes
Privileged EXEC mode
Usage Guidelines
Overlay ACLs are not supported on SLX 9150 or SLX 9250 devices.
Examples
The following example is an overlay VXLAN ACL applied to an overlay transit.
device# show access-list overlay type vxlan acl-name abc_ext
Number of Rules: 4
seq 1000 permit dst-vtep-ip-host 200.1.1.1 src-vtep-ip-host 150.1.1.1 vni 1 vni-mask 0
redirect Ethernet 2/65 sflow count 44024774(pkts)/52829728800(bytes)
seq 1010 permit dst-vtep-ip-host 200.1.1.2 src-vtep-ip-host 150.1.1.2 vni 2 vni-mask 0
redirect Ethernet 2/19 sflow count 44024773(pkts)/52829727600(bytes)
seq 1020 permit dst-vtep-ip-host 200.1.1.3 src-vtep-ip-host 150.1.1.3 vni 3 vni-mask 0
redirect Ethernet 2/43 sflow count 0(pkts)/0(bytes)
seq 1030 permit dst-vtep-ip-host 200.1.1.4 src-vtep-ip-host 150.1.1.4 vni 4 vni-mask 0
redirect Ethernet 2/67 sflow count 0(pkts)/0(bytes)
Transit : transit_name
Syntax
show access-list-log buffer [ interface { ethernet slot / port | port-
channel index } ]
Parameters
interface
Filters by interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
Modes
Privileged EXEC mode
Output
The show access-list log buffer command displays the following information:
Examples
Sample terminal output:
device# show access-list-log buffer
Frames Logged on interface 0/2 :
--------------------------------
Frame Received Time : Fri Dec 9 3:8:48 2011
Ethernet, Src : (00:34:56:78:0a:ab), Dst: (00:12:ab:54:67:da)
Ethtype : 0x8100
Vlan tag type : 0x800
VlanID : 0x1
Internet proto, Src : 192.85.1.2, Dst: 192.0.0.1
Interface :
Type of service : 0
Length : 110
Identification : 0
Fragmentation : 00 00
TTL : 255
protocol : 253
Checksum : 39 3a
Payload type :
packet(s) repeated : 30
Ingress Deny Logged
-----------------------------------------------------------------------
Syntax
show access-list-log buffer config
Modes
Privileged EXEC mode
Output
The show access-list log buffer config command displays the following information:
Examples
The following example displays the configuration of the ACL buffer.
device# show access-list-log buffer config
ACL Logging is enabled
Buffer exists for interface Eth 2/11
Buffer type is Circular and size is 1000
show arp
Displays the Address Resolution Protocol (ARP) entries.
Syntax
show arp { ethernet slot / port | ve ve-id } [ vrf name ]
show arp ip ip-address [ vrf name ]
show arp [ dynamic | static ] [ summary ] [ vrf name ]
Parameters
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
ve ve-id
Specifies a virtual Ethernet (VE) interface.
vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
ip ip-address
Specifies a next-hop IP address.
dynamic
Displays all the dynamic ARP entries in the ARP table.
static
Displays all the static ARP entries in the ARP table.
summary
Displays a summary of the ARP table.
Modes
Privileged EXEC mode
Output
The show arp command displays the following information:
Age In hh:mm:ss format, displays the time since the most recent renewal
of a dynamic entry. For a static entry, displays "Never".
Type Displays the ARP type. Supported values:
• Dynamic
• Static
• MCT/EVPN: MCT peer ARPS or entries learned through the BGP-
EVPN control plane
• MCT/EVPN Sticky: MCT peer ARPs or entries learned through the
BGP-EVPN control plane—with the "sticky" attribute (static or
MY-IP at the originator).
• LeakArp: An ARP entry leaked from another VRF.
• PreArp: ARP triggered by other than the data traffic, for example,
by the static route.
Examples
The following example displays the output of the basic show arp command.
device# show arp
Entries in VRF default-vrf : 24
Address Mac-address L3 Interface L2 Interface Age Type
------------------------------------------------------------------------------
1.4.67.4 609c.9fde.0f15 Ve 1467 Tu 61441 (4.4.4.4) 00:00:00 LeakArp
1.5.67.5 609c.9fde.1215 Ve 1567 Tu 61442 (5.5.5.5) Never Bgp-Sticky
2.7.0.2 609c.9fde.0015 Ve 2703 Po 27 00:14:45 Dynamic
3.7.0.2 609c.9fde.0d1c Eth 0/2 Eth 0/2 00:04:12 Dynamic
6.7.6.6 609c.9fde.0b15 Ve 4090 Eth 0/31 00:01:43 Dynamic
37.1.1.3 609c.9fde.0d15 Ve 37 PW (3.3.3.3) 00:19:26 Dynamic
37.1.1.10 0010.9400.0002 Ve 37 Eth 0/42.37 00:08:00 Dynamic
37.1.1.100 0000.0001.0002 Ve 37 UnResolved Never Static
37.1.1.101 UnResolved Ve 37 UnResolved 00:00:00 PreArp
The following example displays the output of the show arp summary option.
device# show arp summary
Static Entries : 1
Dynamic Entries : 6
Leaked Entries : 2
Pre-arp Entries : 1
Remote (MCT/EVPN) Entries : 0
Remote (MCT/EVPN) Sticky Entries : 14
Total Entries : 24
Syntax
show arp access-list [ acl-name ]
Parameters
acl-name
Specifies the name of an ARP ACL defined on the device.
Modes
Privileged EXEC mode
Examples
The following example displays the name and permit statements of an ARP ACL named "list1".
device# show arp access-list list1
ARP access list list1
permit ip host 192.85.1.2 mac host 0010.9400.0002
permit ip host 192.85.1.3 mac host 0010.9400.0003 log
permit ip host 196.2.1.2 mac host 0020.3200.0008
The following example displays the name and permit statements of all ARP ACLs.
device# show arp access-list
ARP access list list1
permit ip host 192.85.1.2 mac host 0010.9400.0002
permit ip host 192.85.1.3 mac host 0010.9400.0003 log
permit ip host 196.2.1.2 mac host 0020.3200.0008
ARP access list list2
permit ip host 20.20.20.1 mac host 0011.9400.0001 log
permit ip host 30.30.30.1 mac host 0011.9400.0002
show bfd
Displays Bidirectional Forwarding Detection (BFD) information.
Syntax
show bfd
Modes
Privileged EXEC mode
Output
The show bfd command displays the following information:
Examples
The following example displays typical information.
device# show bfd
BFD State: ENABLED, Version: 1
Supported Protocols: static-ip, ospf6, ospf, bgp
All Sessions: Current HW : 0 Current SW : 0 Max Allowed: 250 Max Exceeded Count: 0
Syntax
show bfd neighbors [ vrf vrfname [ details ] ]
Parameters
vrf vrfname
Specifies the name of a nondefault VRF instance.
details
Displays detailed neighbor information.
Modes
Privileged EXEC mode
Usage Guidelines
Output
The show bfd neighbors command displays the following information:
Examples
The following example shows sample output from the show bfd neighbors command.
Syntax
show bfd neighbors application { bgp | isis | ospf | ospf6 | static-ip}
Parameters
bgp
Specifies Border Gateway Protocol (BGP) sessions.
isis
Specifies Intermediate System to Intermediate System (IS-IS) sessions.
ospf
Specifies Open Shortest Path First (OSPF) sessions.
ospf6
Specifies Open Shortest Path First version 3 (OSPFv3) sessions.
static-ip
Specifies static IPv4 and IPv6 sessions.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show bfd neighbors application command displays the following information:
Examples
The following example shows sample output when the ospf keyword is used.
device# show bfd neighbors application ospf
Syntax
show bfd neighbors dest-ip { ip-address | ipv6-address } [ details ]
show bfd neighbors dest-ip { ip-address | ipv6-address } interface
{ ethernet slot/port | loopback number | port-channel number | ve ve-
interface-number }
Parameters
ip-address
Specifies the IP address of the destination device.
ipv6-address
Specifies the IPv6 address of the destination device.
details
Displays detailed neighbor information about the destination device.
interface
Displays BFD neighbor interface information.
ethernet slot/port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
port-channel number
Specifies a port-channel interface.
ve ve-interface-number
Specifies a virtual Ethernet (VE) interface.
Modes
Privileged EXEC mode
Output
The show bfd neighbors dest-ip command displays the following information:
Examples
The following example shows sample output from the show bfd neighbors dest-ip command
when the details keyword is used.
device# show bfd neighbors dest-ip 5.1.0.1 details
Flags: * indicates State is inconsistent across the cluster
OurAddr NeighAddr
State Int
======= =========
===== ===
5.1.0.2 5.1.0.1
UP ve6
Syntax
show bfd neighbors details
Modes
Privileged EXEC mode
Output
The show bfd neighbors details command displays the following information:
State Int
======= =========
===== ===
121.5.0.1 121.5.0.2
UP ve256
Syntax
show bfd neighbors interface { ethernet slot/port | loopback number |
tunnel number | port-channel number | ve ve-interface-number }
[ details ]
Parameters
ethernet slot/port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
tunnel number
Specifies a tunnel interface. Valid values range from 1 through 100000.
port-channel number
Specifies a port-channel interface.
ve ve-interface-number
Specifies a virtual Ethernet (VE) interface.
details
Specifies detailed information.
Modes
Privileged EXEC mode
Output
The show bfd neighbors interface command displays the following information:
Examples
The following example shows BFD neighbor information with details about a specific VE interface.
device# show bfd neighbors interface ve 6 details
Flags: * indicates State is inconsistent across the cluster
OurAddr NeighAddr
State Int
======= =========
===== ===
5.1.0.2 5.1.0.1
UP ve6
Syntax
show bgp evpn ethernet-segment { esi es-id }
Parameters
esi es-id
Use this option to query for ESI information for a particular ESI value.
Modes
EXEC mode
Examples
The following example displays the ethernet segment information for all interfaces on the multi-homed
client.
sw#show bgp evpn ethernet-segment
ESI : 00.112233445566778899
Interface : po4
Interface state : Up
Load balancing Mode : Active-Active
List of MH Nodes : 1.1.1.1 2.2.2.2
DF Vlans : 100 102 104 106 108 110
DF BD : 50 52 54 56 58 60
Syntax
show bgp evpn l2route type { arp |igmp-join-sync | igmp-leave-sync |
inclusive-multicast | mac | nd}
Parameters
type { arp |igmp-join-sync | igmp-leave-sync | inclusive-multicast |
mac | nd}
Specifies the type of route.
Modes
Privileged EXEC mode
Examples
The following example shows routes in the VPN table.
device# show bgp evpn l2route
Total number of BGP EVPN Routes : 5
Status codes: s suppressed, d damped, h history, * valid, > best, i internal, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop MED LocPrf Weight Path
Route Distinguisher: 3.3.100.3:1
*> IMR:[50][IPv4:3.3.100.3]
0.0.0.0 0 100 0 ?
*>i IMR:[50][IPv4:4.4.100.4]
4.4.100.4 0 100 0 ?
*>i IMR:[50][IPv4:5.5.100.5]
5.5.100.5 0 100 0 ?
*> MAC:[50][0000.0300.0050]
0.0.0.0 0 100 0 ?
*>i MAC:[50][0000.0400.0050]
4.4.100.4 0 100 0 ?
The following example displays details for inclusive-multicast routes. In this example, the EVPN instance
is configured with route-targets configured automatically.
The following example displays details for inclusive-multicast routes. In this example, the EVPN instance
is configured with route-targets configured explicitly.
The following example displays details for MAC routes. BI indicates that the route is "Best" and
"Installed." This ensures that it is downloaded into the system.
Syntax
show bgp evpn l2route next-hop { ipv4-address | ipv6-address } type
{ igmp-join-sync | igmp-leave-sync | inclusive-multicast}
Parameters
ipv4-address
Specifies an IPv4 address.
ipv6-address
Specifies an IPv6 address.
type
Specifies the type of route.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
inclusive-multicast
Specifies Leave Sync routes.
Modes
Privileged EXEC mode
Examples
This example displays inclusive multicast information received from 2.2.2.2.
device# show bgp evpn l2route next-hop 2.2.2.2 type inclusive-multicast
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
1 IMR:[2][IPv4:2.2.2.2]
2.2.2.2 0 100 0 BL
AS_PATH:
L2 Label: 2
Syntax
show bgp evpn l2route unreachable type { igmp-join-sync | igmp-leave-
sync}
Parameters
type
Specifies the type of route.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
Modes
Privileged EXEC mode
Syntax
show bgp evpn l3 vni { all-vrfs | vrf name }
Parameters
all-vrfs
Specifies all VRFs.
vrf name
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows Layer 3 VNI information for all VRFs.
-----------------------------------------------------------------------
L3VNI Prefix Origination Conditions for vrf (2)
-----------------------------------------------------------------------
Address Family under BGP : True
RD Configured : True
L3 VNI Configured : True
VLAN VNI Mapping exists : True
Router mac Exists : True
L3 VNI Link UP : True
Source VTEP : 0x06000006
L3VNI Active : Active
-----------------------------------------------------------------------
L3VNI Prefix Import Conditions for vrf (2)
-----------------------------------------------------------------------
Address Family under BGP : True
L3 VNI Configured : True
VLAN VNI Mapping exists : True
Router mac Exists : True
L3VNI Active : Active
-----------------------------------------------------------------------
L3VNI Prefix Origination Conditions for vrf (3)
-----------------------------------------------------------------------
Address Family under BGP : True
RD Configured : True
L3 VNI Configured : True
VLAN VNI Mapping exists : True
-----------------------------------------------------------------------
L3VNI Prefix Import Conditions for vrf (3)
-----------------------------------------------------------------------
Address Family under BGP : True
L3 VNI Configured : True
VLAN VNI Mapping exists : True
Router mac Exists : True
L3VNI Active : Active
-----------------------------------------------------------------------
L3VNI Prefix Origination Conditions for vrf (4)
-----------------------------------------------------------------------
Address Family under BGP : True
RD Configured : True
L3 VNI Configured : True
VLAN VNI Mapping exists : True
Router mac Exists : True
L3 VNI Link UP : True
Source VTEP : 0x06000006
L3VNI Active : Active
-----------------------------------------------------------------------
L3VNI Prefix Import Conditions for vrf (4)
-----------------------------------------------------------------------
Address Family under BGP : True
L3 VNI Configured : True
VLAN VNI Mapping exists : True
Router mac Exists : True
L3VNI Active : Active
-----------------------------------------------------------------------
L3VNI Prefix Origination Conditions for vrf (5)
-----------------------------------------------------------------------
Address Family under BGP : True
RD Configured : True
L3 VNI Configured : True
VLAN VNI Mapping exists : True
Router mac Exists : True
L3 VNI Link UP : True
Source VTEP : 0x06000006
L3VNI Active : Active
-----------------------------------------------------------------------
L3VNI Prefix Import Conditions for vrf (5)
-----------------------------------------------------------------------
Address Family under BGP : True
L3 VNI Configured : True
VLAN VNI Mapping exists : True
Router mac Exists : True
L3VNI Active : Active
The following example shows Layer 3 VNI information for a specified VRF.
-----------------------------------------------------------------------
L3VNI Prefix Origination Conditions for vrf (red)
-----------------------------------------------------------------------
Address Family under BGP : True
RD Configured : True
IRB I/F Configured : True (0x48000064)
IRB I/F Status : False
IRB EVID Conigured : True (100)
Router mac Exists : True
Source VTEP : 40.40.40.1
VTEP Active : Active
IPv4 L3VNI Active : Active
IPv6 L3VNI Active : Inactive
-----------------------------------------------------------------------
L3VNI Prefix Import Conditions for vrf (red)
-----------------------------------------------------------------------
Address Family under BGP : True
IRB I/F Configured : True (0x48000064)
IRB EVID Configured : True (100)
Router mac Exists : True
IPv4 L3VNI Active : Active
IPv6 L3VNI Active : Inactive
Syntax
show bgp evpn neighbors [ ip-addr | ipv6-addr | routes-summary ]
Parameters
ip-addr
Specifies the IPv4 address of a neighbor.
ipv6-addr
Specifies the IPv6 address of a neighbor.
routes-summary
Displays routes received, routes accepted, number of routes advertised by peer, and so on.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to view configuration information and statistics for BGP EVPN neighbors of the
device. Output shows all configured parameters for the neighbors.
Examples
The following example shows sample output from the show bgp evpn neighbors command.
Syntax
show bgp evpn neighbors { ip address | ipv6 address } advertised-routes
[ detail |type [ arp |auto-discovery | ethernet-segment |igmp-join-
sync | igmp-leave-sync |inclusive-multicast | ipv4-prefix | ipv6-
prefix | mac | nd] ]
Parameters
ip address
Specifies the IPv4 address of a neighbor.
ipv6 address
Specifies the IPv6 address of a neighbor.
type
Specifies the type of route.
detail
Specifies that detailed information be shown for the designated route type.
arp
Specifies Address Resolution Protocol routes.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segment (ES) routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
inclusive-multicast
Specifies inclusive multicast routes.
ipv4-prefix
Specifies IPv4 prefix routes.
ipv6-prefix
Specifies IPv6 prefix routes.
mac
Specifies MAC routes.
nd
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn neighbors advertised-routes
detail command.
Syntax
show bgp evpn neighbors { ip address | ipv6 address } routes [ type ] |
best [ type ] | detail [ type ] | not-installed-best [ type ] |
unreachable [ type ] ]
Parameters
type
Specifies the type of route.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segments (ES) routes.
inclusive-multicast
Specifies inclusive multicast routes.
mac
Specifies MAC routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn neighbors routes best
command.
device# show bgp evpn neighbors 20.0.0.2 routes best
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
1 IMR:[0][IPv4:2.2.2.2]
2.2.2.2 0 100 0 BI
AS_PATH:
L2 Label: 2 (VNI)
2 ARP:[0][609c.9fde.1215]:[IPv4:2.1.1.1]
2.2.2.2 0 100 0 BI
AS_PATH:
L2 Label: 2 L3 Label: 0 (VNI)
ESI : 00.000000000000000000
3 ARP:[0][609c.9fde.1215]:[IPv4:102.1.1.1]
2.2.2.2 0 100 0 BI
AS_PATH:
L2 Label: 2 L3 Label: 0 (VNI)
ESI : 00.000000000000000000
4 MAC:[0][609c.9fde.1215]
2.2.2.2 0 100 0 BI
AS_PATH:
L2 Label: 2 (VNI)
ESI : 00.000000000000000000
Syntax
show bgp evpn routes
Modes
Privileged EXEC mode
Examples
The following example shows routes in the VPN table.
Syntax
show bgp evpn routes best
show bgp evpn routes best [ type { auto-discovery | ethernet-segment |
inclusive-multicast | ipv4-prefix | ipv6-prefix | mac |igmp-join-sync
| igmp-leave-sync } ]
Parameters
type
Specifies the type of route.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segments (ES) routes.
inclusive-multicast
Specifies inclusive multicast routes.
ipv4-prefix
Specifies IPv4 prefix routes.
ipv6-prefix
Specifies IPv6 prefix routes.
mac
Specifies MAC routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn routes best command.
device# show bgp evpn neighbors 20.0.0.2 routes best
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
1 IMR:[0][IPv4:2.2.2.2]
2.2.2.2 0 100 0 BI
AS_PATH:
L2 Label: 2 (VNI)
2 ARP:[0][609c.9fde.1215]:[IPv4:2.1.1.1]
2.2.2.2 0 100 0 BI
AS_PATH:
L2 Label: 2 L3 Label: 0 (VNI)
ESI : 00.000000000000000000
3 ARP:[0][609c.9fde.1215]:[IPv4:102.1.1.1]
2.2.2.2 0 100 0 BI
AS_PATH:
L2 Label: 2 L3 Label: 0 (VNI)
ESI : 00.000000000000000000
4 MAC:[0][609c.9fde.1215]
2.2.2.2 0 100 0 BI
AS_PATH:
L2 Label: 2 (VNI)
ESI : 00.000000000000000000
Syntax
show bgp evpn routes detail
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn routes detail command.
device# show bgp evpn routes detail
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
1 Prefix: IMR:[0][IPv4:2.2.2.2], Status: BI, Age: 0h9m34s
NEXT_HOP: 2.2.2.2, Learned from Peer: 20.0.0.2 (100)
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: RT 100:268435458 RT 100:2 RT 100:1073741826 RT
03:0c:00:00:00:00:00:08
PMSI Attribute Flags: 0x00000000 Label-Stack: 2 Tunnel-Type: 6 Tunnel-IP:
2.2.2.2
Extended Community: ExtCom: Tunnel Encapsulation (Type Vxlan)
L2 Label: 2 (VNI)
RD: 2.2.2.2:32770
As-magic: 20
2 Prefix: ARP:[0][609c.9fde.1215]:[IPv4:2.1.1.1], Status: BI, Age: 0h9m34s
NEXT_HOP: 2.2.2.2, Learned from Peer: 20.0.0.2 (100)
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: RT 100:268435458 RT 100:2 RT 06:00:01:00:00:00:00:00 RT
100:1073741826 RT 03:0c:00:00:00:00:00:08
Mac Mobility Sticky: True
Extended Community: ExtCom: Tunnel Encapsulation (Type Vxlan)
L2 Label: 2 L3 Label: 0 (VNI)
ESI : 00.000000000000000000
RD: 2.2.2.2:32770
As-magic: 22
3 Prefix: ARP:[0][609c.9fde.1215]:[IPv4:1
Syntax
show bgp evpn routes local
show bgp evpn routes local type [ arp |auto-discovery | ethernet-segment
| igmp-join-sync | igmp-leave-sync |inclusive-multicast | ipv4-prefix
| ipv6-prefix | mac | nd]
Parameters
type
Specifies the type of route.
arp
Specifies Address Resolution Protocol routes.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segments (ES) routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
inclusive-multicast
Specifies inclusive multicast routes.
ipv4-prefix
Specifies IPv4 prefix routes.
ipv6-prefix
Specifies IPv6 prefix routes.
mac
Specifies MAC routes.
nd
Specifies Neighbor Discovery routes.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn routes local command.
device# show bgp evpn routes local
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
1 Prefix: IMR:[0][IPv4:1.1.1.1], Status: BL, Age: 0h15m0s
NEXT_HOP: 0.0.0.0, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: RT 100:1073741826 RT 2:2 RT 06:03:60:9c:9f:de:0f:15
Adj_RIB_out count: 1, Admin distance 0
L2 Label: 2 (EVI)
RD: 1:1
As-magic: 8
2 Prefix: IP4Prefix:[0][2.1.1.0/24], Status: BL, Age: 0h14m59s
NEXT_HOP: 0.0.0.0, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: RT 2:2 RT 03:0d:00:00:00:00:00:00 RT 100:1073741826
Default Extd Gw Community: Received
Adj_RIB_out count: 1, Admin distance 0
L3 Label: 2 (EVI)
RD: 1:1
As-magic: 12
3 Prefix: ARP:[0][609c.9fde.0f15]:[IPv4:2.1.1.1], Status: BL, Age: 0h14m59s
NEXT_HOP: 0.0.0.0, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: RT 06:00:01:00:00:00:00:00 RT 100:1073741826 RT 2:2
Mac Mobility Sticky: True
Adj_RIB_out count: 1, Admin distance 0
L2 Label: 2 L3 Label: 2 (EVI)
ESI : 00.000000000000000000
RD: 1.1.1.1:32770
As-magic: 13
4 Prefix: MAC:[0][609c.9fde.0f15], Status: BL, Age: 0h15m0s
NEXT_HOP: 0.0.0.0, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: RT 06:00:01:00:00:00:00:00 RT 03:0d:00:00:00:00:00:00 RT
100:1073741826
Mac Mobility Sticky: True
Default Extd Gw Community: Received
Adj_RIB_out count: 1, Admin distance 0
L2 Label: 2 (EVI)
ESI : 00.000000000000000000
RD: 1.1.1.1:32770
As-magic: 5
This example shows output for the show bgp evpn routes local command when the type and
mac keywords are used.
AS_PATH:
Extended Community: ExtCom:06:00:01:00:00:00:00:00
ExtCom:03:0d:00:00:00:00:00:00 ExtCom:03:0c:00:00:00:00:00:08 RT 65009:22
Mac Mobility Sticky: True
Default Extd Gw Community: Received
Extended Community: ExtCom: Tunnel Encapsulation (Type Vxlan)
Adj_RIB_out count: 3, Admin distance 0
L2_vni: 22
ESI : 00.000000000000000000
2 Prefix: MAC:[0][0000.abba.baba], Status: BL, Age: 1d9h36m12s
NEXT_HOP: 109.0.0.109, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: ExtCom:06:00:01:00:00:00:00:00
ExtCom:03:0d:00:00:00:00:00:00 ExtCom:03:0c:00:00:00:00:00:08 RT 65009:22
Mac Mobility Sticky: True
Default Extd Gw Community: Received
Extended Community: ExtCom: Tunnel Encapsulation (Type Vxlan)
Adj_RIB_out count: 3, Admin distance 0
L2_vni: 22
ESI : 00.000000000000000000
3 Prefix: MAC:[0][0027.f8fd.274b], Status: BL, Age: 1d9h36m32s
NEXT_HOP: 109.0.0.109, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: ExtCom:06:00:01:00:00:00:00:00
ExtCom:03:0d:00:00:00:00:00:00 ExtCom:03:0c:00:00:00:00:00:08 RT 65009:22
Mac Mobility Sticky: True
Default Extd Gw Community: Received
Extended Community: ExtCom: Tunnel Encapsulation (Type Vxlan)
Adj_RIB_out count: 3, Admin distance 0
L2_vni: 22
ESI : 00.000000000000000000
…
Syntax
show bgp evpn routes next-hop { ipv4-address | ipv6-address } type
{ auto-discovery | ethernet-segment | inclusive-multicast | ipv4-
prefix | ipv6-prefix | mac | igmp-join-sync | igmp-leave-sync }
Parameters
ipv4-address
Specifies an IPv4 address.
ipv6-address
Specifies an IPv6 address.
type
Specifies the type of route.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segments (ES) routes.
inclusive-multicast
Specifies inclusive multicast routes.
ipv4-prefix
Specifies IPv4 prefix routes.
ipv6-prefix
Specifies IPv6 prefix routes.
mac
Specifies MAC routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
Modes
Privileged EXEC mode
Syntax
show bgp evpn routes no-best
show bgp evpn routes no-best [ type { auto-discovery | ethernet-segment |
inclusive-multicast | ipv4-prefix | ipv6-prefix | mac | igmp-join-
sync | igmp-leave-sync} ]
Parameters
type
Specifies the type of route.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segments (ES) routes.
inclusive-multicast
Specifies inclusive multicast routes.
ipv4-prefix
Specifies IPv4 prefix routes.
ipv6-prefix
Specifies IPv6 prefix routes.
mac
Specifies MAC routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn routes no-best command.
Syntax
show bgp evpn routes not-installed-best
show bgp evpn routes not-installed-best [ type { auto-discovery |
ethernet-segment | inclusive-multicast | ipv4-prefix | ipv6-prefix |
mac | igmp-join-sync | igmp-leave-sync } ]
Parameters
type
Specifies the type of route.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segments (ES) routes.
inclusive-multicast
Specifies inclusive multicast routes.
ipv4-prefix
Specifies IPv4 prefix routes.
ipv6-prefix
Specifies IPv6 prefix routes.
mac
Specifies MAC routes.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
Modes
Privileged EXEC mode
Syntax
show bgp evpn routes rd ID
Parameters
ID
VPM route distinguisher, in the form of ASN:nn or IP-address:nn.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show bgp evpn routes rd command.
device# show bgp evpn routes rd 2.2.2.2:32770
Status codes: s suppressed, d damped, h history, * valid, > best, i internal, S stale
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop MED LocPrf Weight Path
*> IMR:[0][IPv4:2.2.2.2]
0.0.0.0 0 100 0 ?
*> ARP:[0][609c.9fde.1215]:[IPv4:2.1.1.1]
0.0.0.0 0 100 0 ?
*> ARP:[0][609c.9fde.1215]:[IPv4:102.1.1.1]
0.0.0.0 0 100 0 ?
*> MAC:[0][609c.9fde.1215]
0.0.0.0 0 100 0 ?
Syntax
show bgp evpn routes rd admin-value:arbitrary-value type { auto-discovery
| ethernet-segment | inclusive-multicast | ipv4-prefix | ipv6-prefix
| mac } detail
show bgp evpn routes rd admin-value:arbitrary-value type auto-discovery
esi-value value ethernet-tag tag-id
show bgp evpn routes rd admin-value:arbitrary-value type ethernet-segment
esi-value value { ipv4-address address | ipv6-address address }
show bgp evpn routes rd admin-value:arbitrary-value type inclusive-
multicast ethernet-tag tag-id ipv4-address address [ l2-vni number]
show bgp evpn routes rd admin-value:arbitrary-value type ipv4-prefix ip
address/mask tag tag-id [ l3vni value ]
show bgp evpn routes rd admin-value:arbitrary-value type ipv6-prefix ipv6
address/mask tag tag-id [ l3vni value ]
show bgp evpn routes rd admin-value:arbitrary-value type mac mac
addressethernet-tag tag-id [ l2-vni number ]
show bgp evpn routes rd admin-value:arbitrary-value type [ auto-discovery
| igmp-join-sync | igmp-leave-sync ] [detail ]
Parameters
admin-value
The administrative number assigned to the route. This can be a local ASN number or an IP
address. The ASN number can be either a 2-byte number (from 0 through 65535) or a 4-byte
number (from 0 through 4294967295).
arbitrary-value
An arbitrary number you choose. The range of valid values is from 0 through 65535 if the ASN is
2 byte, or from 0 through 4294967295 if the ASN is 4 byte.
type
Specifies a route type.
auto-discovery
Specifies automatically discovered routes.
ethernet-segment
Specifies Ethernet Segment (ES) information.
inclusive-multicast
Specifies inclusive multicast information.
ipv4-prefix
Specifies IPv4 prefix information information.
ipv6-prefix
Specifies IPv6 prefix information information.
mac
Specifies Media Access Control (MAC) information.
detail
Displays detailed information.
mac mac address
Specifies a MAC address. The valid format is HHHH.HHHH.HHHH.
ethernet-tag tag-id
Specifies an Ethenet tag. Valid values range from 1 through 4294967295.
l2-vni number
Specifies a layer 2 virtual network identifier (VNI). Valid values range from 1 through 16777215.
esi-value value
Specifies a 10 byte Ethernet Segment Identifier (ESI) value in the form of hexadecimal characters
(HH.HH.HH.HH.HH.HH.HH.HH.HH.HH).
ipv4-address address
Specifies an IPv4 address.
ipv6-address address
Specifies an IPv6 address.
ip address/mask
Specifies an IPv4 address and mask.
ipv6 address/mask
Specifies an IPv6 address and mask.
tag tag-id
Specifies an Ethenet tag. Valid values range from 1 through 4294967295.
l3vni value
Specifies a Layer 3 virtual network identifier (VNIs). Valid values range from 1 through 6777215.
igmp-join-sync
Specifies Join Sync route information.
igmp-leave-sync
Specifies Leave Sync route information.
Modes
Privileged EXEC mode
Examples
The following example shows detailed inclusive multicast information for a BGP EVPN route with the RD
2.2.2.2:32770.
device# show bgp evpn routes rd 2.2.2.2:32770 type inclusive-multicast detail
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
1 Prefix: IMR:[0][IPv4:2.2.2.2], Status: BL, Age: 0h18m48s
NEXT_HOP: 0.0.0.0, Learned from Peer: Local Router
LOCAL_PREF: 100, MED: 0, ORIGIN: incomplete, Weight: 0
AS_PATH:
Extended Community: RT 100:1073741826
Adj_RIB_out count: 1, Admin distance 0
L2 Label: 2 (EVI)
RD: 2.2.2.2:32770
As-magic: 47
Syntax
show bgp evpn routes type arp [ IPv4_address | mac MAC_address | brief |
detail ]
show bgp evpn routes type auto-discovery [ brief | detail | esi-value ]
show bgp evpn routes type ethernet-segment [ brief | detail | esi-value
ESI ]
show bgp evpn routes type inclusive-multicast [ brief | detail |
ethernet-tag ]
show bgp evpn routes type ipv4-prefix [ IPv4_address/mask | brief |
detail | l3-label ]
show bgp evpn routes type ipv6-prefix [ IPv6_address/mask | brief |
detail | l3-label ]
show bgp evpn routes type mac [ MAC_address | brief | detail ]
show bgp evpn routes type nd [ IPv6_address | brief | detail ]
show bgp evpn routes type igmp-join-sync [ brief | detail ]
show bgp evpn routes type igmp-leave-sync [ brief | detail ]
Parameters
arp
Specifies ARP details.
IPv4_address
Specifies an IPv4 address in A.B.C.D format.
mac MAC_address
Specifies a MAC address in HHHH.HHHH.HHHH format.
brief
Specifies brief information.
detail
Specifies detailed information.
auto-discovery
Specifies auto-discovery details.
esi-value ESI
Specifies an Ethernet Segment Indicator in the following hexadecimal format:
HH:HH:HH:HH:HH:HH:HH:HH:HH , HH.
ethernet-segment
Modes
Privileged EXEC mode
Examples
The following example displays information related to ARP routes.
device# show bgp evpn route type arp
Total number of BGP EVPN ARP Routes : 4 Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST
C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE
Prefix Next Hop MED LocPrf Weight Status
Route Distinguisher: 40.40.100.50:32869
1 ARP:[0][0000.0a0a.0a0b]:[IPv4:10.10.10.11]
0.0.0.0 0 100 0 BL
AS_PATH:
L2 Label: 101 L3 Label: 100
ESI : 00.000000000000000000
2 ARP:[0][609c.9f5a.4715]:[IPv4:15.143.15.1]
0.0.0.0 0 100 0 BL
AS_PATH:
L2 Label: 101 L3 Label: 100
ESI : 00.000000000000000000
Route Distinguisher: 40.40.100.50:33769
3 ARP:[0][609c.9f5a.4715]:[IPv4:14.13.15.1]
0.0.0.0 0 100 0 BL
AS_PATH:
L2 Label: 1001 L3 Label: 100
ESI : 00.000000000000000000
Route Distinguisher: 40.40.100.60:32869
4 ARP:[0][609c.9f5a.8d15]:[IPv4:6.6.2.5]
40.40.40.2 0 100 0 BE
AS_PATH: 1000
L2 Label: 101 L3 Label: 0
ESI : 00.000000000000000000
The following example displays brief information related to IPv4 prefix routes.
device# show bgp evpn route type ipv4-prefix brief
Total number of BGP EVPN Ipv4Prefix Routes : 4 Status codes: s suppressed, d damped, h
history, * valid, > best, i internal, S stale Origin codes: i - IGP, e - EGP, ? -
incomplete
Network Next Hop MED LocPrf Weight Path
Route Distinguisher: 5:50
*> IP4Prefix:[0][14.13.15.0/24]
0.0.0.0 0 100 0 ?
*> IP4Prefix:[0][15.143.15.0/24]
0.0.0.0 0 100 0 ?
*> IP4Prefix:[0][16.16.16.0/24]
0.0.0.0 0 100 0 ?
Route Distinguisher: 5:100
*> IP4Prefix:[0][17.17.17.0/24]
40.40.40.2 0 100 0 1000 ?
AS_PATH: 20 11
L2 Label: 201 (VNI)
7 IMR:[0][IPv4:11.11.11.11]
11.11.11.11 none 100 0 E
AS_PATH: 21 11
L2 Label: 201 (VNI)
Route Distinguisher: 24.24.24.24:32970
8 IMR:[0][IPv4:11.11.11.11]
11.11.11.11 none 100 0 BE
AS_PATH: 20 11
L2 Label: 202 (VNI)
9 IMR:[0][IPv4:11.11.11.11]
11.11.11.11 none 100 0 E
AS_PATH: 21 11
L2 Label: 202 (VNI)
Syntax
show bgp evpn routes type igmp-join-sync
show bgp evpn routes type igmp-join-sync brief
show bgp evpn routes type igmp-join-sync detail
Parameters
brief
Displays summary information.
detail
Displays detailed information.
Modes
Privileged EXEC mode
Examples
The following example shows routes to join IGMP sync:
Syntax
show bgp evpn routes type igmp-leave-sync
show bgp evpn routes type igmp-leave-sync brief
show bgp evpn routes type igmp-leave-sync detail
Parameters
brief
Displays summary information.
detail
Displays detailed information.
Modes
Privileged EXEC mode
Examples
The following example shows routes to leave IGMP sync:
1 IGMPLeaveSyncPrefix4:[0](101.1.2.3,235.1.2.3):19.1.2.3 (esi
01.010203040506070809)
19.1.2.3 0 100 0
BI
AS_PATH:
2 IGMPLeaveSyncPrefix6:[0](2002::5,ff04::3):19.1.2.3 (esi 03.010203040506070809)
19.1.2.3 0 100 0 BI
AS_PATH:
Syntax
show bgp evpn routes unreachable [ type { igmp-join-sync | igmp-leave-
sync } ]
Parameters
type
Specifies the type of route.
igmp-join-sync
Specifies Join Sync routes.
igmp-leave-sync
Specifies Leave Sync routes.
Modes
Privileged EXEC mode
Syntax
show bgp evpn summary
Modes
Privileged EXEC mode
Examples
The following example displays summarized information for EVPN neighbors.
Syntax
show bgp ip flowspec
show bgp ip flowspec attribute-entries
show bgp ip flowspec routes [ asn-number | age | best | detail | local |
neighbor | no-best | not-installed-best | summary | vrf vrf-name ]
show bgp ip flowspec summary
Parameters
attribute-entries
Specifes the the display of AS-path attribute-entry information for BGP flowspec.
routes
Specifies the display of route configuration information for BGP flowspec.
asn-number
Displays route information starting from the specified autonomous system number (ASN). The
range od from 1 through 4294967295.
age
Displays recently updated route information.
best
Displays information about routes that are selected as best routes.
detail
Displays detailed route information.
local
Displays information about selected local routes.
neighbor
Displays routes from BGP neighbors.
no-best
Displays information about routes that do not have a best path.
not-installed-best
Displays best routes that are not installed in the IP route table.
summary
Displays summary information for BGP flowspec routes.
vrf vrf-name
Displays route information for the specified VRF instance.
summary
Modes
Privileged EXEC mode
Usage Guidelines
For a flowspec route (which is a combination of all match components), specify the detail option to
display all match components and traffic actions. When the detail option is not specified, traffic-
action configuration information is not displayed and only a limited length of match component
imformation is displayed for the route.
Examples
The following example shows output from the show bgp ip flowspec routes command.
device# show bgp ip flowspec routes
The following example shows summary information for the show bgp ip flowspec routes
command.
device# show bgp ip flowspec routes summary
Syntax
show bgp ip flowspec neighbors
show bgp ip flowspec neighbors ip-address advertised-routes
show bgp ip flowspec neighbors ip-address rib-out-routes
show bgp ip flowspec neighbors ip-address routes [ best | detail | not-
installed-best | vrf vrf-name
show bgp ip flowspec neighbors routes-summary
show bgp ip flowspec neighbors vrf vrf-name }
Parameters
ip-address
Specifes the IP address (in IPv4 format) of a BGP flowspec neighbor.
advertised-routes
Displays information about routes advertised to the neighbor.
rib-out-routes
Displays information about RIB-out routes for the neighbor.
routes
Causes the display of information about routes learned from the neighbor.
best
Displays information about routes that are selected as best routes.
detail
Displays detailed information about routes that are learned from the neighbor.
not-installed-best
Displays information about best routes that are not installed in the IP route table.
vrf vrf-name
Displays information about routes that are learned from the neighbor for the specified VRF
instance.
routes-summary
Displays summary information for routes learned from a neighbor.
vrf vrf-name
Displays information for BGP flowspec neighbors for the specified VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example displays detailed RIB-out route information for a BGP flowspec neighbor
(10.61.61.1).
device# show bgp ip flowspec neighbors 10.61.61.1 rib-out-routes detail
Syntax
show bgp ip neigbor ipv6 { all | last-packet-with-error | routes-
summary }
show bgp ip neighbor ipv6 ipv6-addr [ flap-statistics | last-packet-with-
error [ decode ] | received prefix-filter ]
show bgp ip neighbor ipv6 ipv6-addr { advertised-routes | received-routes
| rib-out-routes } [ detail ]
show bgp ip neighbor ipv6 ipv6-addr routes { best | detail [ best | not-
installed-best | unreachable] | not-installed-best | unreachable }
show bgp ip neighbor ipv6 ipv6-addr routes-summary
Parameters
advertised-routes
Specifies the display of information about routes advertised to the BGP4+ neighbor in the
current session.
detail
Specifies the display of detailed information.
all
Specifies the display of information about all routes advertised to the BGP4+ neighbor in the
current session.
flap-statistics
Specifies the display of route flap statistics for routes received from or sent to a BGP4+ neighbor.
last-packet-with-error
Specifies the display of information about the last packet that contained an error received from
any device neighbor.
decode
Specifies decoding the packet.
received-routes
Specifies the display of route information received from BGP4 neighbors in the current session.
detail
Specifies the display of detailed information.
rib-out-routes
Specifies the display of information about BGP4 outbound RIB routes.
detail
Specifies the display of detailed information.
routes
best
Specifies the display of information about routes received from the neighbor that are the best
BGP4+ routes to their destination.
detail
Specifies the display of detailed information.
best
Specifies the display of information about routes received from the neighbor that are the best
BGP4+ routes to their destination.
not-installed-best
Specifies the display of information about routes received from the BGP4+ neighbor that are the
best BGP4+ routes to their destination and that were not installed in the route table because the
device received better routes from other sources.
unreachable
Specifies the display of information about routes that are unreachable because the device does
not have a valid RIP, OSPF, or static route to the next hop.
Modes
Privileged EXEC mode
Examples
The following example shows configuration information and statistics for an IPv6 neighbor that is
configured under an IPv4 address family.
show bgp ip neighbors ipv6 2000::1
Syntax
show bgp ip summary ipv6
Modes
Privileged EXEC mode
Examples
The following example displays summary configuration information and statistics for IPv6 neighbors
that are configured under an IPv4 address family.
device# show bgp ip summary ipv6
BGP4 Summary
Router ID: 10.1.1.1 Local AS Number: 1
Confederation Identifier: not configured
Confederation Peers:
Maximum Number of IP ECMP Paths Supported for Load Sharing: 1
Number of Neighbors Configured: 1, UP: 1
Number of Routes Installed: 0
Number of Routes Advertising to All Neighbors: 0 (0 entries)
Number of Attribute Entries Installed: 0
Syntax
show { ip | ipv6 } bgp peer-dampened [detail] [ all-vrfs | vrf vrf-name ]
Parameters
{ ip | ipv6 }
The address family for which the peer dampening information is required.
all-vrfs
Show the peer dampening information for all VRFs.
vrf vrf-name
Show the peer dampening information for the VRF specified in the vrf-name parameter.
detail Show the peer dampening information in detail including delay-hold and penalty.
Modes
Global Executable Mode
Usage Guidelines
• The Idle-hold-Timer column of the output displays the time remaining to move to next state.
• The Idle-hold column of the output displays the time the neighbor will stay in the idle state.
• The Stability-interval column of the output displays the time the session must remain error-free to
be considered stable.
• The Delay-hold column output displays the time assigned to the Idle-hold-Timer for the first peer-
flap event received.
• The Penalty column of the output displays the time added to Idle-hold-Timer for the second and
more peer-flap event received.
Examples
The following command example displays a list of all dampened BGP peers (IPv4) on all VRFs.
leaf-1# show ip bgp peer-dampened all-vrfs
--------------------------------------------------------------------------------------
VRF - default vrf
--------------------------------------------------------------------------------------
Total number of BGP Neighbors: 1
Neighbor Idle-hold-Timer Idle-Hold Stability-interval
50.1.1.2 03 15 30
The following command example displays a list of all dampened BGP peers (IPv6) on all VRFs.
leaf-1# show ipv6 bgp peer-dampened all-vrfs
--------------------------------------------------------------------------------------
VRF - default vrf
--------------------------------------------------------------------------------------
Total number of BGP Neighbors: 1
Neighbor Idle-hold-Timer Idle-Hold Stability-interval
200:1:1:1:1::1 06 15 30
The following example displays show ipv6 bgp peer-dampened detail all-vrfs
leaf-1# show ipv6 bgp peer-dampened detail all-vrfs
----------------------------------------------------------------------------
VRF: default-vrf
----------------------------------------------------------------------------
Total number of BGP Neighbors:1
Neighbor Idle-hold-Timer Idle-Hold Stability-interval delay-hold penalty
200.1.1.1.1::1 3 15 30 10 10
leaf-1#
show bridge-domain
Displays information about bridge domains.
Syntax
show bridge-domain [ bd-id [ logical-interface ] ]
show bridge-domain brief [ p2mp | p2p ]
show bridge-domain interface { ethernet slot/port | port-channel number }
show bridge-domain vc-peer
Parameters
bd-id
Specifies the bridge-domain identifier.
logical-interface
Causes the display of the ifindex and operational information for logical interfaces configured
under the bridge domain.
brief
Causes the display of summary bridge-domain information.
p2mp
Causes the display of multipoint service information.
p2p
Causes the display of multi-point cross-connect service information.
interface
Displays a list of bridge-domain logical interfaces that are associated with a physical interface.
ethernet slot/port
Specifies an Ethernet interface in slot/port format. For devices that do not support linecards,
specify 0 for the slot.
port-channel number
Specifies a port-channel interface number.
vc-peer
Causes the display of summary virtual connection (VC) peer information for the bridge domain.
Modes
Privileged EXEC mode.
Output
The following table describes elements of information displayed in output from the show bridge-
domain command:
Examples
The following example shows the information displayed by the show bridge-domain command.
Bridge-domain 1
-------------------------------
Bridge-domain Type: mp , VC-ID: 5, MCT Enabled: TRUE
Number of configured end-points: 5 , Number of Active end-points: 4
VE if-indx: 1207959555, Local switching: TRUE, bpdu-drop-enable:TRUE
PW-profile: 1, mac-limit: 128000
Number of Mac’s learned:90000, Static-mac count: 10,
VLAN: 100, Tagged ports: 2(2 up), Un-tagged ports: 0 (0 up)
Tagged ports: Eth 0/2/6, eth 0/2/8
Un-tagged ports:
Bridge-domain 2
-------------------------------
Bridge-domain Type: mp , VC-ID: 100, MCT Enabled: FALSE
Number of configured end-points: 5 , Number of Active end-points: 4
VE if-indx: NA, Local switching: FALSE, bpdu-drop-enable:FALSE
PW-profile: profile_1, mac-limit: 262144
Number of Mac’s learned:90000, Static-mac count: 10,
VLAN: 100, Tagged ports: 2(1 up), Un-tagged ports: 0 (0 up)
Tagged ports: eth 0/2/10, eth 0/1/10
Un-tagged ports:
VLAN: 150, Tagged ports: 1(1 up), Un-tagged ports: 0 (0 up)
Tagged ports: eth 0/1/5
Un-tagged ports:
Bridge-domain 3
-------------------------------
Bridge-domain Type: mp , VC-ID: 200, MCT Enabled: FALSE
Number of configured end-points: 5 , Number of Active end-points: 4
VE if-indx: 120793855, Local switching: FALSE, bpdu-drop-enable:FALSE
PW-profile: 2, mac-limit: 262144
Number of Mac’s learned:90000, Static-mac count: 10,
Local switching: TRUE,
VLAN: 500, Tagged ports: 2(2 up), Un-tagged ports: 2 (1 up)
Tagged ports: eth 0/11/6, eth 0/4/3
Un-tagged ports:
The following example shows information about a bridge domain (501) in which the load-balance
and cos options are configured for the peer device 10.9.9.9.
Bridge-domain 501
-------------------------------
Bridge-domain Type: MP , VC-ID: 501, MCT Enabled: FALSE
Number of configured end-points: 2 , Number of Active end-points: 2
VE if-indx: 0, Local switching: TRUE, bpdu-drop-enable: TRUE
PW-profile: default, mac-limit: 0
VLAN: 501, Tagged ports: 1(1 up), Un-tagged ports: 0 (0 up)
Tagged Ports: eth1/6.501
Un-tagged Ports:
Total VPLS peers: 1 (1 Operational):
The following example shows information about bridge domain 501 in which the load-balance
option, cos option and three assigned label-switched paths (p1001, p1002, and p1003) are configured
for the peer device 10.9.9.9.
Bridge-domain 501
-------------------------------
Bridge-domain Type: MP , VC-ID: 501, MCT Enabled: FALSE
Number of configured end-points: 2 , Number of Active end-points: 2
VE if-indx: 0, Local switching: TRUE, bpdu-drop-enable: TRUE
PW-profile: default, mac-limit: 0
VLAN: 501, Tagged ports: 1(1 up), Un-tagged ports: 0 (0 up)
Tagged Ports: eth1/6.501
Un-tagged Ports:
Total VPLS peers: 1 (1 Operational):
The following example shows the information displayed by the show bridge-domain brief
command.
The following example shows how to display bridge-domain information for a port-channel interface.
show capabilities
Displays whether a variety of network services are enabled ("true") or not ("false").
Syntax
show capabilities
Modes
Privileged EXEC mode
Usage Guidelines
Enter ? to view available options.
Examples
The following example displays the status of all network services:
device# show capabilities
capabilities mqc span true
capabilities qos system-rx-queue-limit false
capabilities qos system-tx-queue-limit true
capabilities qos show-rx-queue-interface false
capabilities qos conf-rx-queue-interface false
capabilities qos cee nas false
capabilities qos cpu slot false
capabilities qos cpu queue false
capabilities l2 port_profile true
capabilities l2 overlap_vlan true
capabilities l2 rspan false
capabilities l2 mac_move true
capabilities l2 consistency_check false
capabilities l2 learning_mode true
capabilities l2 priority_tag true
capabilities l2 internal_nsm true
capabilities l2 lif_untagged_vlan_id false
capabilities l2 bridgedomain_local_switching false
capabilities l2 dot1x false
capabilities l3 ip_mtu true
capabilities ipv6 ipv6Raguard false
capabilities ssm aclTrafficType true
capabilities lag PortchannelRedundancy false
capabilities bgp next-hop-mpls false
capabilities bgp redistribute-isis false
capabilities license eula_display true
capabilities license dpod_display false
capabilities license slot_display false
capabilities ip igmp false
capabilities ip igmp-snooping igmp-snooping-version false
capabilities tm false
capabilities overlay gre false
capabilities cfm false
Syntax
show cee maps default
Parameters
default
The name of the CEE map. Only one CEE map can be defined on a system and the name
assigned to this policy is default.
Modes
Privileged EXEC mode
Examples
This example displays the current CEE Map configuration.
device# config term
device(config)# do show cee maps default
Syntax
show cert-util sshkey user user_id
Parameters
user user_id
The user ID to display.
Modes
Privileged EXEC mode
Examples
The following example shows typical output for the command.
show cfm
Displays the current configuration and status of CFM.
Syntax
show cfm [ brief | connectivity ]
Parameters
brief
Displays the CFM brief output.
connectivity session-id
Dixplays the CFM connectivity configuration
Modes
Privileged EXEC mode
Output
The show cfm command displays the following information:
Examples
Typical command output displaying the CFM settings for domain MD1.
device# show cfm
Domain: md1
Index: 1
Level: 7
Maintenance association: ma5
MA Index: 5
CCM interval: 100 ms
Bridge-Domain ID: 50
Priority: 7
MAID Format: Short
MEP Direction MAC PORT VLAN INNER-VLAN PORT-STATUS-TLV
==== ========= ========= ==== ==== =========== ===============
1 UP 609c.9f5f.700d Eth 1/9 50 -- N
Syntax
show cfm y1731 action-profile
Modes
Privileged EXEC mode
Examples
This example displays the Y. 1731 action-profiles.
device# show cfm y1731 action-profile
----------------------------------------
Name : a1
Syntax
show cfm y1731 client-signal-fail
Modes
Privileged EXEC mode
Examples
This example displays ETH-CSF configuration information and packet statistics.
device# show cfm y1731 client-signal-fail
---------------------------------------------------------------------------------
Domain Name : md1
MA Name : ma1
---------------------------------------------------------------------------------
ETH-CSF Statistics :
---------------------------------------------------------------------------------
MEP RMEP MEP RMEP Client CSF Transmit Transmit Receive Transmit Receive
ID ID Status Status I/F Type Period Frames Frames C-DCI C-DCI
---------------------------------------------------------------------------------
1 2 UP UP 1/1 C-LOS 1 minute 10 10 1 0
2 1 UP DOWN 1/2 C-LOS 1 second 0 0 0 0
This example displays ETH-CSF configuration information and packet statistics after the clear cfm
y1731 client-signal-fail command is issued.
device# show cfm y1731 client-signal-fail
---------------------------------------------------------------------------------
Domain Name : md1
MA Name : ma1
---------------------------------------------------------------------------------
ETH-CSF Statistics :
---------------------------------------------------------------------------------
MEP RMEP MEP RMEP Client CSF Transmit Transmit Receive Transmit Receive
ID ID Status Status I/F Type Period Frames Frames C-DCI C-DCI
---------------------------------------------------------------------------------
1 2 UP UP 1/1 C-LOS 1 minute 0 0 0 0
2 1 UP DOWN 1/2 C-LOS 1 second 0 0 0 0
Syntax
show cfm y1731 delay-measurement
show cfm y1731 delay-measurement brief
show cfm y1731 delay-measurement session session-id
show cfm y1731 delay-measurement statistics
show cfm y1731 delay-measurement statistics brief
show cfm y1731 delay-measurement statistics session session-id brief
show cfm y1731 delay-measurement statistics session session-id brief
Parameters
brief
Specifies brief.
session session-id
Specifies session and the session ID.
statistics
Specifies statistics.
historyhistory-index
Specifies history and the history index..
Modes
Privileged EXEC mode
Examples
This example displays detailed info for all measurement sessions.
device# show cfm y1731 delay-measurement statistics brief
-----------------------------------------------------------------------------
Session Index : 1
Test Profile Name : my_test_profile2
-----------------------------------------------------------------------------
HISTORY TABLE :
------------------------------------------------------------------------------------------
----
Index Start Elapsed Avg Delay(us) Max Delay(us) Min Delay(ns) FDV
Avg(ns) FDV Max(ns) FDV Min(ns)
------------------------------------------------------------------------------------------
----
4 03:13:34 00:15:00 33.281 33.542 32.851 39 79 12
3 02:58:34 00:15:00 27.162 27.690 26.745 41 85 13
Syntax
show cfm y1731 synthetic-loss-measurement
show cfm y1731 synthetic-loss-measurement brief
show cfm y1731 synthetic-loss-measurement session session-id
show cfm y1731 synthetic-loss-measurement statistics
show cfm y1731 synthetic-loss-measurement statistics brief
show cfm y1731 synthetic-loss-measurement statistics session session-id
brief
show cfm y1731 synthetic-loss-measurement statistics session session-id
brief
show cfm y1731 synthetic-loss-measurement statistics session session-id
history history-index
Parameters
brief
Specifies brief.
session session-id
Specifies session and the session ID.
statistics
Specifies statistics.
historyhistory-index
Specifies history and the history index..
Modes
Privileged EXEC mode
Examples
This example displays detailed info for all measurement sessions.
device# show cfm y1731 synthetic-loss-measurement
SLM Session Index : 1
Test Profile Name : my_test_profile1
Status : Active
Session Type : Initiator
Domain : md1
MA : ma1
Source MEP : 1
Target MEP : 2
Cos : 5
Start time : 19:49:55
Start time type : Fixed
Stop time : 00:00:00
Stop time type : Fixed
Tx-interval(sec) : 1
Measurement-interval(min) : 15
Forward Average (milliPercent) : 4294967295
Forward Max (milliPercent) : 4294967295
Backward Average(milliPercent) : 1
Backward Max (milliPercent) : 4
-----------------------------------
Syntax
show cfm y1731 synthetic-loss-measurement
Modes
Privileged EXEC mode
Examples
This example displays the Y.1731 test profile.
--------------------------------------------------
Default Test Profiles:
--------------------------------------------------
Name : 2dm-default-profile
Type : ETH-DM
Cos Value : 7
Tx-Interval : 1 Second
Tx-Frame-Count : 10
Measurement Interval : 15 Minute(s)
Threshold Average : 4294967295 (uSec)
Threshold Max : 4294967295 (uSec)
Start time : 00:05:00 (After)
Stop time : 01:05:00 (After)
Timeout : 1 Second
--------------------------------------------------
--------------------------------------------------
Name : 2slm-default-profile
Type : ETH-SLM
Cos Value : 7
Tx-Interval : 1 Second
Tx-Frame-Count : 10
Measurement Interval : 15 Minute(s)
Threshold Backward Average : 4294967295
Threshold Backward Max : 4294967295
Threshold Forward Average : 4294967295
Threshold Forward Max : 4294967295
Start time : 00:05:00 (After)
Stop time : 01:05:00 (After)
Timeout : 1 Second
show chassis
Displays the status for components in the device.
Syntax
show chassis [ virtual-ip ]
Parameters
virtual-ip
Displays the virtual IP address and status.
Modes
Privileged EXEC mode
Usage Guidelines
This command is executed on the local switch and is supported only on the local switch. The output of
this command depends on the platforms on which it is executed.
Pagination is not supported with this command. Use the "more" parameter to display the output one
page at a time.
Supply power values are positive; consumer power values are negative.
Examples
The following example displays chassis information on an SLX 9540.
device# show chassis
Chassis Name:BR-SLX9540
switchType: 4000
FAN Unit: 1
Time Awake: 0 days
FAN Unit: 2
Time Awake: 0 days
FAN Unit: 3
Time Awake: 0 days
FAN Unit: 5
CHASSIS/WWN Unit: 1
Power Consume Factor: 0
Factory Part Num: 40-1001198-03
Factory Serial Num: FBK0319M00J
Manufacture: Day: 0 Month: 0 Year: 2000
Update: Day: 1 Month: 2 Year: 2018
Time Alive: 646 days
Time Awake: 0 days
Rework: 0
Serial Num: 0
Rework: 0
show cipherset
Displays the current cipherset status for LDAP and SSH.
Syntax
show cipherset { ldap | radius }
Parameters
radius
Specifies secure RADIUS ciphers.
ldap
Specifies secure LDAP ciphers.
Modes
Privileged EXEC mode
Examples
To display configured cipher list on the device:
device# show cipherset
show cli
Displays all the current CLI settings.
Syntax
show cli
Modes
Privileged EXEC mode
Examples
Typical command output display.
device# show cli
autowizard false
complete-on-space false
history 100
idle-timeout 600
ignore-leading-space false
output-file terminal
paginate true
prompt1 \H\M#
prompt2 \H(\m)#
screen-length 73
screen-width 120
service prompt config true
show-defaults false
terminal ansi
show clock
Returns the local time, date, and time zone.
Syntax
show clock
Command Default
The local clock is used.
Modes
Privileged EXEC mode
Usage Guidelines
The command displays the current time for the device.
Examples
The following example shows the clock time.
device# show clock
2017-02-28 17:58:30 Etc/GMT
show cluster
Displays the MCT cluster information including client, PW client, member bridge domain, and member
VLAN information.
Syntax
show cluster
show cluster client [ cluster-ID | A.B.C.D ]
show cluster client-pw
show cluster icl { brief | detail | statistics }
show cluster member { bridge-domain | vlan }
Parameters
client
Specifies the cluster ID or IP address.
cluster-ID
Specifies the cluster client ID.
A.B.C.D
Specifies the cluster IP address.
client-pw
(DNX devices only) Specifies PW client information for VPLS or VLL MCT.
icl
Specifies inter-chassis link (ICL) information.
brief
Specifies brief ICL information.
detail
Specifies detailed ICL information.
statistics
Specifies ICL statistics.
member
Specifies member bridge-domains or VLANs.
bridge-domain
Specifies cluster bridge domains.
vlan
Specifies cluster VLANs.
Modes
Privileged EXEC mode
Usage Guidelines
When you delete an IP router ID that is used as the neighbor ID and IP address on an MCT peer, the
show cluster command on the MCT peer devices displays inconsistent cluster states.
Output
The show cluster command displays the following information:
On the SLX 9540 and SLX 9640 devices, the client-pw option with the show cluster command
displays the following information:
Examples
On the SLX 9540 and SLX 9640 devices, the following example shows the information of the cluster on
the SLX-OS device.
device# show cluster 1
Cluster MCT1 1
==============
Cluster State: Deploy
Client Isolation Mode: Loose
DF Hold Time: 3
Configured Member Vlan Range: 2, 4-7
Active Member Vlan Range: 2, 4-7
Cluster Control Vlan: 4090
Configured Member BD Range:
Active Member BD Range:
No. of Peers: 1
No. of Clients: 2
Peer Info:
----------
Peer IP: 10.10.10.20, State: Up
Peer Interface: Not Configured
ICL Tunnel Type: MPLS, State: Up
Client Info:
------------
Name Id ESI Interface Local/Remote State
On the SLX 9540 and SLX 9640 devices, the following example shows the PW client information.
device#show cluster 1 client-pw
Client Info:
============
Client: Client-pw, client-id: 34816, Deployed, State: Up
Interface: PW
Bridge-domains: 8100-8101
Elected DF for Bridge-domains:
8100
Syntax
show cluster track
Parameters
show cluster track
Displays all interfaces that are currently tracking cluster status using cluster-track configuration.
Modes
Global mode
Output
The show cluster-track command displays the following information:
Examples
show cluster track
show config-drift-track
Displays configuration drift information and status of the current session on the SLX device.
Syntax
show config-drift-track { values | status }
Parameters
values
Displays the current values for the configuration drift Timestamp and Counter values.
status
Displays the status of configuration for the current session.
Modes
Privilege Execution Mode
Examples
The following example displays the current configuration drift tracking values.
SLX# show config-drift-track values
Config Drift Timestamp: 1635487552
Config Drift Counter: 12344
The following example shows the status of configuration drift tracking for the current session.
SLX# show config-drift-track status
Config Drift Tracking is OFF
Syntax
show copy-support status
Modes
Privileged EXEC mode
Usage Guidelines
The status is indicated by the percentage of completion. NORMAL indicates process is proceeding or
completed without errors. FAULTY indicates a faulty blade.
Examples
To display the support upload status:
device# show copy-support status
Syntax
show core-isolation track
Modes
Privilege Exec Mode
Examples
The following example shows the list of tracked interfaces.
SLX # show core-isolation track
show crypto ca
Displays trust point and certificate information.
Syntax
show crypto ca {trustpoint | certificates}
Parameters
trustpoint
Modes
Privileged EXEC mode
Usage Guidelines
To run this command from other configuration modes, use the do command modifier.
Examples
This example shows typical output for a trustpoint.
device# show crypto ca trustpoint
trustpoint: t1; key-pair: k1
Syntax
show crypto key key_name
Modes
Privileged EXEC mode
Usage Guidelines
To execute this command from other configuration modes, use the do command modifier.
Examples
Typical command output:
device# show crypto key mypubkey
key type: ecdsa
key label: k1
key size: 384
Syntax
show debug all
Modes
Privileged EXEC mode
Examples
The following example shows....
Syntax
show debug arp packet [ buffer ]
Parameters
buffer
Displays ARP packets saved in the relevant buffer.
Modes
Privileged EXEC mode
Output
The show debug arp packet command displays the following information:
Examples
The following example is a typical output of the show debug arp packet buffer option.
device# show debug arp packet buffer
Protocol Type : ARP
Packet Flow : Sending
Packet Type : Req
VRF ID : 1
Interface info : Eth 1/1
Ethernet, SrcMAC : 768e.f807.2005, DstMAC: 0000.0000.0000
Internet proto,SrcIP : 11.1.1.1, DstIP: 11.1.1.1
VRF ID : 1
Interface info : Eth 1/1
Ethernet, SrcMAC : 768e.f807.2005, DstMAC: 0000.0000.0000
Internet proto,SrcIP : 11.1.1.1, DstIP: 11.1.1.1
Syntax
show debug dhcp packet
Modes
Privileged EXEC mode
Examples
The following example displays the DHCP packet capture configuration on interfaces.
Syntax
show debug dhcp packet buffer
Modes
Privileged EXEC mode
Examples
The following command displays buffer content for all VRF IDs.
Syntax
show debug ip bgp all
Modes
Privileged EXEC mode
Examples
The following example displays all BGP4 debugging options that are enabled.
Syntax
show debug ip igmp
Modes
Privileged EXEC mode
Examples
The following displays example output.
device# show debug ip igmp
IGMP debugging status:
---------------------------------------
errors : off
group : off
packets : off
query : off
report : off
direction : none
vlan : none
l2_port : none
Syntax
show debug lacp
Modes
Privileged EXEC mode
Syntax
show debug lldp
Modes
Privileged EXEC mode
Examples
The following example displays the status of LLDP debugging on the device.
Syntax
show debug spanning-tree
Modes
Privileged EXEC mode
Syntax
show debug vrrp
Modes
Privileged EXEC mode
Usage Guidelines
This command is for VRRP and VRRP-E. You can modify or redirect the displayed information by using
the default Linux tokens (|, >).
Examples
If you run this command and the debug parameter has already been set to debug all VRRP events, the
following is displayed:
Syntax
show defaults threshold sfp type sfp-type
Parameters
sfp-type
The following SFP types are supported:
1GCOP
— 1G SFP Copper
1GCWDM
— 1G SFP CWDM
1GLR
— 1G SFP LR
1GSR
— 1G SFP SR
10GDWDMT
— 10G SFP+ DWDM Tunable
10GER
— 10G SFP+ ER
10GLR
— 10G SFP+ LR
10GSR
— 10G SFP+ SR
10GUSR
— 10G SFP+ USR
10GZR
— 10G SFP+ ZR
40GER
— 40G QSFP+ ER4
40GESR
— 40G QSFP+ eSR4 INT
40GLM
— 40G QSFP+ LM4
40GLR
— 40G QSFP+ LR4
40GSR
— 40G QSFP+ SR4
40GSRINT
— 40G QSFP+ SR4 INT
100GAOC
— 100G QSFP28 AOC
100GCLR
— 100G QSFP28 CLR4
100GCWDM
— 100G QSFP28 CWDM4
100GESR
— 100G QSFP28 eSR4
100GLR
— 100G QSFP28 LR4
100GLRLT
— 100G QSFP28 LR4 Lite
100GPSM
— 100G QSFP28 PSM4
100GSR
— 100G QSFP28 SR4
Modes
Privileged EXEC mode
Usage Guidelines
You can modify these thresholds with the threshold-monitor sfp command.
Examples
The following example displays the default sfp thresholds for 1G SFP Copper.
+------------+-------+--------+--------+-----------+-------------+--------+
| Current mA | 45 | raslog | none | 1| raslog | 0|
+------------+-------+--------+--------+-----------+-------------+--------+
| Voltage mV | 3700 | raslog | none | 2900| raslog | 0|
+------------+-------+--------+--------+-----------+-------------+--------+
show dot1x
Displays 802.1X-related information.
Syntax
show dot1x [ all ]
show dot1x [ interface ethernet slot/port]
show dot1x [ diagnostics | session-info | statistics ] { interface
ethernet slot/port }
Parameters
all
Displays detailed dot1x information for all of the ports.
interface
Displays the state of a specified interface.
diagnostics
Displays diagnostics information for the authenticator associated with a port.
session-info
Displays all statistical information of an established session.
statistics
Displays the statistics of a specified interface.
Modes
Privileged EXEC mode
Examples
The following example shows the overall state of 802.1X authentication on the system.
device# show dot1x
802.1X Port-Based Authentication: Enabled
PAE Capability: Authenticator Only
Protocol Version: 2
Auth Server: RADIUS
Readiness test timeout: 10
RADIUS Configuration
--------------------
Position: 1
Server Address: 10.24.65.6
Port: 1812
Secret: xxxxxxxxx
Retry Interval: 5 seconds
The following example shows detailed 802.1X authentication information for all of the ports.
device# show dot1x all
802.1X Port-Based Authentication: Enabled
PAE Capability: Authenticator Only
Protocol Version: 2
Auth Server: RADIUS
Readiness test timeout: 10
RADIUS Configuration
--------------------
Position: 1
Server Address: 10.20.106.144
Port: 1812
Secret: testing123
Retry Interval: 4 seconds
Position: 2
Server Address: 10.20.106.189
Port: 1812
Secret: testing123
Retry Interval: 4 seconds
The following example shows all diagnostics information for the authenticator associated with a port.
device# show dot1x diagnostics interface ethernet 1/2
802.1X Diagnostics for interface Eth 1/2
----------------------------------------
authEnterConnecting: 1
authEaplogoffWhileConnecting: 0
authEnterAuthenticating: 1
authSuccessWhileAuthenticating: 1
authTimeoutWhileAuthenticating: 0
authFailWhileAuthenticating: 0
authEapstartWhileAuthenticating: 0
authEaplogoffWhileAuthenticating: 0
authReauthsWhileAuthenticated: 0
authEapstartWhileAuthenticated: 0
authEaplogoffWhileAuthenticated: 0
BackendResponses: 11
BackendAccessChallenges: 10
BackendOtherrequestToSupplicant: 11
BackendAuthSuccess: 1
BackendAuthFails: 0
Tx Period: 30 seconds
Quiet Period: 60 seconds
Supplicant Timeout: 30 seconds
Re-Auth Interval: 3600 seconds
Dynamic VLAN assigned: 50
Filter-strict-security: Enabled
IP ACL assigned (IN|OUT): IPEXT-50 | IPEXT-OUT-50
MAC ACL assigned: mac-ext
The following example shows information for all clients on the port.
device# show dot1x session-info interface ethernet 1/2
802.1X Session info for interface Eth 1/2
-----------------------------------------
Mac Address: 0021.5ec6.15ce
-----------------------------------------
User Name: md5user2
Session Time: 2 secs
Terminate Cause: Not terminated yet
Session Status: Authorized
PAE State: Authenticated
BE State: Idle
VLAN: N/A
IP ACL (IN | OUT): N/A | N/A
MAC ACL: N/A
Current Id: 18
Id From Server: 17
Syntax
show environment fan
Modes
Privileged EXEC mode
Output
The show environment fan command displays the following information:
Examples
The following example displays fan status information:
device# show environment fan
Syntax
show environment history
Modes
Privileged EXEC mode
Usage Guidelines
The history log records insertion and removal events for field-replaceable units (FRUs), such as blades,
power supplies, fans, and world wide name (WWN). The type of FRU supported depends on the
hardware platform.
Output
The show environment history command displays the following information:
Examples
The following example displays the FRU history on a device.
device# show environment history
POWER SUPPLY Unit 1 Inserted at Sun Jul 12 21:59:17 2015
Factory Part Number:
Factory Serial Number:
(Output truncated)
Syntax
show environment power
Modes
Privileged EXEC mode
Output
The show environment power command displays the following information:
Examples
The following example displays the power supply status.
device# show environment power
Power Supply #1 is OK
DELTA type: A V23.45
Power Supply #2 is OK
DELTA type: A V23.45
Power Supply #3 is absent
Power Supply #4 is absent
Power Supply #5 is absent
Power Supply #6 is absent
Syntax
show environment sensor
Modes
Privileged EXEC mode
Usage Guidelines
The command output displays the current temperature, fan, and power supply status readings from
sensors located on the switch. For an explanation of power supply status values, refer to the show
environment power topic.
Examples
The following example displays sensor readings on the device:
device# show environment sensor
sensor 1: (Temperature) is Ok, value is 31 C
sensor 2: (Temperature) is Ok, value is 53 C
sensor 3: (Temperature) is Ok, value is 52 C
sensor 4: (Temperature) is Ok, value is 37 C
sensor 5: (Temperature) is Ok, value is 32 C
(Output truncated)
Syntax
show environment temp
Parameters
detail
(Not currently supported) Specifies to display information in detail.
Modes
Privileged EXEC mode
Examples
This example displays the environment temperature.
device# show environment temp
SensorState Centigrade Fahrenheit
ID
=================================================
1Ok 27 80
2Ok 27 80
3Ok 26 78
4Ok 28 82
5Ok 27 80
6Ok 27 80
7Ok 26 78
show erp
Displays information about all Ethernet Ring Protocol (ERP) instances, or for a specified instance.
Syntax
show erp [ erp_id ]
Parameters
erp_id
Specifies an ERP ID.
Modes
Privileged EXEC mode
Examples
The following example displays information about all ERP instances.
device# show erp
ERP 5 (Version 2) - VLAN 6
=================================================================================
Erp ID Status Oper Node Non-revertive Topo
state role mode group
5 enabled Idle rpl-node disabled -
Syntax
show erp statistics erp_id
Parameters
erp_id
Specifies an ERP ID.
Modes
Privileged EXEC mode
Examples
The following example displays statistics for ERP instance 1.
device# show erp statistics 1
ERP: 1, VLAN 222
Syntax
show event-handler activations
Modes
Privileged EXEC mode
Output
The show event-handler activations command displays the following information:
Examples
The following example displays event-handler operational data.
device# show event-handler activations
Event-handler : evh1
Last Trigger Activation Time: 2015-04-30 17:28:12
Total Trigger Activations: 25
Last Action Completion Time: 2015-04-30 17:28:57
Last Action Completion Status: Exit Code = 0
Total Action Completions: 25
Event-handler : evh2
Last Trigger Activation Time: 2015-04-28 22:02:51
Total Trigger Activations: 8
Last Action Completion Time: 2015-04-28 22:02:58
Last Action Completion Status: Exit Code = 0
Total Action Completions: 8
show file
Displays the contents of a file in the local flash memory.
Syntax
show file filename
Parameters
filename
The name of the file to be displayed.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
Examples
The following example displays the contents of a file in the flash memory.
device# show file defaultconfig.cluster
vlan dot1q tag native
!
cee-map default
remap fabric-priority priority 0
remap lossless-priority priority 0
priority-group-table 15.0 pfc off
priority-group-table 1 weight 40 pfc on
priority-group-table 2 weight 60 pfc off
priority-table 2 2 2 1 2 2 2 15.0
!!
port-profile default
vlan-profile
switchport
switchport mode trunk
switchport trunk allowed vlan all
!
interface Port-channel 1
vlag ignore-split
description Homerun port-channel on MM1
shutdown
!
interface Port-channel 2
vlag ignore-split
description Homerun port-channel on MM2
shutdown
!
protocol lldp
!!
logging auditlog class CONFIGURATION
logging auditlog class FIRMWARE
Syntax
show firmware peripheral cpld
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on devices based on the DNX chipset family. For a list of such devices,
see "Supported Hardware".
The firmware upgrade can be invoked from either Linux shell or SLX CLI console. The Linux shell
command is cpld_upgrade -p.
Output
The show firmware peripheral cpld command displays the following information:
Examples
This example displays output for an SLX 9540.
device# show firmware peripheral cpld
+----------+----------------+----------------+
| Type | Current Version| Latest Version |
+----------+----------------+----------------+
| CPLD0 | 02/09/2017(92) | 02/09/2017(92) |
+--------- +----------------+----------------+
| CPLD1 | 02/09/2017(92) | 02/09/2017(92) |
+--------- +----------------+----------------+
Syntax
show firmware peripheral fpga
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on devices based on the DNX chipset family. For a list of such devices,
see "Supported Hardware".
The firmware upgrade can be invoked from either Linux shell or SLX CLI console. The Linux shell
command is fpga_upgrade -p.
Examples
This example displays output for an SLX 9540.
device# show firmware peripheral fpga
+---------------+--------------------------+-------------------------------------+
| Type | Current Version | Latest Version Availalble |
+---------------+--------------------------+-------------------------------------+
| sysfpga | 09/28/2016(54) | 09/28/2016(54) |
+---------------+--------------------------+-------------------------------------+
show firmwaredownloadhistory
Displays the firmware download history for the device.
Syntax
show firmwaredownloadhistory
Modes
Privileged EXEC mode
Usage Guidelines
The log records the date and time of the firmware download, the device name, slot number, process ID,
and firmware version.
Examples
The following example displays the firmware download history.
SLX# show firmwaredownloadhistory
show firmwaredownloadstatus
Displays the firmware download activity log.
Syntax
show firmwaredownloadstatus [ brief ] [ summary ]
Parameters
brief
Displays only the last entry of the firmware download event log.
summary
Displays a high-level summary of the firmware download status.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display an event log that records the progress and status of events that occur
during a firmware download. The event log is created by the firmware download command and is
retained until you issue another firmware download command. A time stamp is associated with
each event.
Examples
The following example displays the firmware download event log.
device# show firmwaredownloadstatus
[1]: Wed Mar 1 21:58:34 2017
Slot M1: Firmware install begins.
(Output truncated)
The following example displays a high-level summary of the firmware download status.
device# show firmwaredownloadstatus summary
No Firmware Download session in progress.
show grubversion
Displays the installed version of ONIE-GRUB.
Syntax
show grubversion
Modes
Privileged EXEC Mode
Usage Guidelines
This command is only supported on the SLX 9150, SLX 9250, Extreme 8720, and Extreme 8520 devices.
Examples
This example shows the usage of the command.
SLX # show grubversion
grub_version="2.06"
SLX #
Syntax
show hardware media-database [all | sfp | qsfp | qsfp28]
Parameters
all
Specifies all media types in the mediavdatabase.
sfp
Specifies all SFP (small form factor pluggable) media in the media database.
qsfp
Specifies all QSFP (quad small form factor pluggable) media in the media database.
qsfp28
Specifies all QSFP28 (QSFP for 4x28Gbps) media in the media database.
Modes
Privileged EXEC mode
Usage Guidelines
The media database contains the list of port media supported on the device, saved in an .xml file on the
device. The default version is provided in the release package. You can download your own version or
upload the file to a remote server for modification using the copy command. After you download a
new media database to the device, you need to activate it.
Examples
This example displays typical output for the QSFP2 media type.
device# show hardware media-database qsfp28
qsfp28 Media Database
-------------------------------------------------------------------------------
Part Number Vendor Description
-------------------------------------------------------------------------------
NDAAFF-0004 Amphenol 100G-QSFP-28 3m cable passive
NDAAFF-0003 Amphenol 100G-QSFP-28 1m cable passive
58-0000044-01 Extreme Networks 100G-QSFP28 1m Passive Cable 28 5m
EQPC1HPCZ50C0100 Extreme Networks 100G Passive DAC QSFP28 0.5mxSFP2able
EQPT1H4PS4FCM1PG Extreme Networks 100G PSM4 QSFP28 2km Pigtailedm Cable
EQPT1H4SR4UCM100 Extreme Networks 100G SR4 QSFP28 100m0mFP28 10m TAA
EQPT1H4SW4UCL100 Extreme Networks 100G SWDM4 QSFP28 100m8 to 2xQSFP28 3m
EQPA1HQPSP0C0100 Extreme Networks 100G QSFP28 to SFP28 adapterxQSF28 3mm
EQPC1HPC050C0100 Extreme Networks 100G Passive DAC QSFP28 5m 4xSFP2
EQPT1H4BD2UCL100 Extreme Networks 100G SR4 - BiDi QSFP28 100mm
This example displays typical output for the SFP media type.
device# show hardware media-database sfp
SFP Media Database
------------------------------------------------------------------
Part Number Vendor Description
------------------------------------------------------------------
33210-100 AVAGO 1000Base-SX
33210-100 FINISAR 1000Base-SX
33211-100 FINISAR 1000Base-LX
33211-100 AVAGO 1000Base-LX
33002-100 AVAGO 1G Copper SFP
57-1000042-02 Extreme 1000Base(copper)
57-1000042-01 Extreme 1000Base(copper)
57-0000075-01 Extreme 10GE SR SFP+
57-1000130-01 Extreme 10GE LRM SFP+
57-1000130-02 Extreme 10GE SFP+
58-1000019-01 Extreme 10GE Twinax SFP+-P-0501
58-1000023-01 Extreme 10GE Direct Attach 5M Active
58-1000024-01 Extreme 10GE Direct Attach 1M Passive
58-1000026-01 Extreme 10GE Direct Attach 1M Active
58-1000025-01 Extreme 10GE Direct Attach 3M Passive
58-1000027-01 Extreme 10GE Twinax Attach 3M Active
57-1000273-01 Extreme 10GE AOC 7m Optic Cable
57-1000274-01 Extreme 10GE AOC 10m Optic Cable
Syntax
show hardware profile
show hardware profile route profile-name
show hardware profile cam-share
show hardware profile counters { counter-profile-1 | counter-profile-2 |
counter-profile-3 | counter-profile-4 | counter-profile-5| counter-
profile-6 | default }
show hardware profile current [ usage ]
show hardware profile etcam { default | ipv4-v6-route | ipv6-route }
show hardware profile lag { default | lag-profile-1 }
show hardware profile tcam { app-telemetry | border-routing | default |
layer2-ratelimit | multicast-profile | vxlan-visibility }
Parameters
route profile-name
Specifies route information for the specified profile.
cam-share
( SLX 9540 or SLX 9640) Specifies cam-share information.
counters
( SLX 9540 or SLX 9640) Specifies hardware resources for counter profiles.
counter-profile-1
Specifies resources optimized for Ingress ACL, OF, and Egress ACL, with forward and drop
counting for Layer 4 ingress traffic.
counter-profile-2
Specifies resources optimized for OF, MPLS, VPLS, VLL, and MCT, with hit counting for Layer 4
ingress traffic.
counter-profile-3
Specifies resources optimized for MPLS, VPLS, VLL, MCT, with hit counting for Layer 4 ingress
traffic.
counter-profile-4
Specifies resources optimized for Layer 4 traffic, with forward and drop counting for all Layer 4
ingress traffic.
counter-profile-5
Specifies resources optimized for egress rate limit, with support for counting up to 32,000 VOQs.
counter-profile-6
Specifies resource optimized for reporting egress VE traffic statistics. This is only supported on
SLX 9540 and SLX 9640 devices where the corresponding counter engines are setup for
counting egress VE statistics.
default
Specifies resources optimized for VLAN and BD local switching, and MCT, with hit counting for
Layer 4 ingress and egress traffic.
current
Displays details of the current active hardware profile.
usage
Displays usage information for the current active profile.
etcam
( SLX 9640 only) Specifies hardware resources for external TCAM (ETCAM) profiles.
default
Displays the details of the default ETCAM.
ipv4-v6-route
Displays the details of the ETCAM ipv4-v6-route.
ipv6-route
Displays the details of the ETCAM ipv6-route.
lag
( SLX 9540 or SLX 9640) Specifies hardware resources for link aggregation (LAG) profiles.
default
Specifies the default profile.
lag-profile-1
Specifies a modified LAG profile.
tcam
( SLX 9540 or SLX 9640) Specifies hardware resources for TCAM profiles.
app-telemetry
Optimizes resources for application telemetry.
border-routing
Optimizes resources for BGP Flowspec, ACLs, and so forth.
default
Optimizes resources with basic support for all applications.
layer2-ratelimit
Optimizes resources for Layer 2 ACL egress rate-limiting and related applications.
multicast-profile
Optimizes resources for IPv6 multicast. Layer 2 is also supported.
vxlan-visibility
Optimizes resources for VXLAN transit and termination, and GRE tunnel.
Modes
Privileged EXEC mode
Usage Guidelines
If the profile counters are changed from default to counter-profile- and the statistics-based
encapsulations are not available, then the LSPs that need statistics will not be brought up (either due to
exhaustion or due to activating a counter profile that does not support statistics).
You can check whether the statistics-based encapsulations are needed by using the show run
router mpls policy command to see if statistics are enabled in MPLS. LSPs that have auto-
bandwidth configured and bridge-domains that have statistics configured also need statistics-based
encapsulations.
If statistics are enabled, the LSPs and bridge-domains stay down. In the case of LSPs, the show mpls
lsp {detail | extensive | name <lsp name>} command displays, "Statistics not available" in the
down reason code.
Examples
The following example displays details of the current active hardware profile.
device# show hardware profile current
switch type:
v4FibComp: Disabled
v6FibComp: Disabled
multivrf: Disabled
________________________________________________________________
current LAG profile: LAG-DEFAULT
max-lag: 64
_________________________________________________________________
The following example displays information about profile etcam default, ipv4-v6-route, and ipv6 route.
device# show hardware profile etcam default
switch type: SLX9640
Syntax
show hardware smt
Modes
Privileged EXEC mode
Usage Guidelines
This feature is supported only on devices based on the Broadcom DNX chipset family. For a list of such
devices, see "Supported Hardware".
Because new SMT settings take effect only after the device is rebooted, the current and next SMT
settings can be different after you update the SMT settings but before you reboot the device.
Examples
This example shows typical output for the command.
device# show hardware smt
Current: Enabled, Next Reboot: Disabled
show history
Displays the history of commands executed on the device during the current session.
Syntax
show history [ number ]
Parameters
number
Specifies the number of commands to display. Values range from 1 through 1000.
Modes
Privileged EXEC mode
Usage Guidelines
If you enter this command without specifying a number, up to 1000 commands are displayed.
Examples
The following command displays the three last commands entered.
device# show history 3
12:45:23 -- show interface switchport
12:45:37 -- show interface stats brief
12:45:45 -- show arp vrf test
Syntax
show http server status
Modes
Privileged EXEC mode
Output
The show http server status command displays the following information:
Examples
The following example displays HTTP and HTTPS server status information.
device# show http server status
show hw route-info
Displays IP routes information related to longest exact match (LEM) and longest prefix match (LPM).
Syntax
show hw route-info { interface slot/port | linecard number }
Parameters
interface slot / port
Specifies an interface. For devices without slots, specify 0.
linecard number
Specifies the linecard or device level. For devices without slots, specify 0.
Modes
Privileged EXEC mode
Output
The show hw route-info command displays the following information:
Examples
The following example displays hardware route information.
device# show hw route-info linecard 0
HW-Route-Info
====================================================
Slot 0
Tower 0
LEM
Total Entries :750000
95% Threshold :712500
85% Threshold :637500
Total In Use :58 (.000000%)
IPV4 routes :58
IPV6 routes :0
Status :Green
LPM
Total Entries :1000000
95% Threshold :950000
85% Threshold :850000
eTCAM
Total Entries :4000000
95% Threshold :3800000
85% Threshold :3400000
Total In Use :156 (.000000%)
IPV4 routes :156
IPV6 routes :0
Status :Green
show interface
Displays the detailed interface configuration and capabilities of all interfaces or for specified interfaces.
Syntax
show interface [ description ]
show interface [ ethernet slot / port | port-channel number ]
[ switchport ]
show interface loopback number
show interface management [ management-id ]
show interface trunk
Parameters
description
For all device interfaces, displays a summary that includes the Description field.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
port-channel number
Specifies a port-channel number.
switchport
Specifies Layer 2 interfaces.
loopback number
Specifies a loopback interface.
management management-id
Specifies the management interface. The only supported value is 0.
trunk
Displays VLANs on the trunk.
Modes
Privileged EXEC mode
Output
The show interface ethernet command displays the following information:
The show interface ethernet management command displays the following information:
The show interface ethernet switchport command displays the following information:
Examples
The following example displays detailed information for a specified Ethernet interface.
device# show interface ethernet 3/4
Ethernet 3/4 is up, line protocol is up (connected)
Hardware is Ethernet, address is 768d.f804.ca08
Current address is 768d.f804.ca08
Pluggable media present
Interface index (ifindex) is 207650816
MTU 1548 bytes
IP MTU 1500 bytes
10G Interface
LineSpeed Actual : 10000 Mbit
LineSpeed Configured : Auto, Duplex: Full
Priority Tag disable
Forward LACP PDU: Disable
Route Only: Disabled
Last clearing of show interface counters: 11:59:37
Queueing strategy: fifo
Primary Internet Address is 12.2.1.2/24 broadcast is 12.2.1.255
Receive Statistics:
45756 packets, 34003184 bytes
Unicasts: 9094, Multicasts: 36650, Broadcasts: 12
64-byte pkts: 1438, Over 64-byte pkts: 8113, Over 127-byte pkts: 1786
Over 255-byte pkts: 10132, Over 511-byte pkts: 8432, Over 1023-byte pkts: 15855
Over 1518-byte pkts(Jumbo): 0
Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0
Errors: 0, Discards: 0
Transmit Statistics:
33405 packets, 25357172 bytes
Unicasts: 10232, Multicasts: 23162, Broadcasts: 10
Underruns: 0
Errors: 0, Discards: 0
Rate info:
Input 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Output 0.000333 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Route-Only Packets Dropped: 0
The following example displays detailed information for the specified management interface.
device# show interface management 0
interface Management 0
line-speed actual "1000baseT, Duplex: Full"
line-speed configured Auto
oper-status up
ip address "static 10.17.110.59/20"
ip gateway-address 10.17.114.1
ipv6 ipv6-address [ ]
ipv6 ipv6-gateways [ fe80::21b:edff:fe0b:9000 fe80::21b:edff:fe0b:3c00 ]
The following example displays detailed information for a specified loopback interface.
device# show interface loopback 1
Loopback 1 is up, line protocol is up
Hardware is Loopback
Pluggable media not present
Interface index (ifindex) is 1476395009
IP MTU 1500 bytes
LineSpeed Actual : Nil
LineSpeed Configured : Auto
Last clearing of show interface counters: 00:00:23
Queueing strategy: fifo
Primary Internet Address is 50.1.1.1/32
This example shows whether the control plane is receiving packets at the configured rate.
device# show int eth 0/1 | inc rate
Queueing strategy: fifo
Input 8.649182 Mbits/sec, 8446 packets/sec, 0.10% of line-rate
Output 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Syntax
show interface stats brief [ slot line-card-number ]
Parameters
slot line-card-number
(Not currently supported) Specifies a line card.
Modes
Privileged EXEC mode
Examples
The following example displays brief interface statistics.
0
Eth 0/16 0 0 0 0 0 0 0
Eth 0/17 0 0 0 0 0 0 0
Eth 0/18 0 0 0 0 0 0 0
Eth 0/19 0 0 0 0 0 0 0
Eth 0/20 0 0 0 0 0 0 0
(output
truncated)
Syntax
show interface stats detail
show interface stats detail interface { ethernet slot / port | port-
channel index | ve { all | ve-id }}
Parameters
interface
Specifies what type of interface is displayed.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
port-channel
Specifies a port channel interface.
index
Specifies the port channel number.
ve
Specifies a VE interface.
ve-id
Shows VE statistics for the specified VE ID.
all
Shows all VE statistics.
Modes
Privileged EXEC mode
Examples
The following example displays detailed statistics for a specified Ethernet interface.
device# show interface stats detail interface ethernet 0/41
Broadcasts 0 6
Errors 0 0
Discards 0 0
Overruns 0 Underruns 0
Runts 0
Jabbers 0
CRC 0
64-byte pkts 0
Over 64-byte pkts 4
Over 127-byte pkts 1527089
Over 255-byte pkts 0
Over 511-byte pkts 0
Over 1023-byte pkts 0
Over 1518-byte pkts 0
Mbits/Sec 0.000000 0.000338
Packet/Sec 0 0
Line-rate 0.00% 0.00%
The following example displays detailed statistics for a specified port channel.
VE Statistics
Id Rx Pkts Rx Bytes Tx Pkts Tx Bytes
100 543 69504 0 0
This example displays the egress VE statistics. For 9540 and 9640, this output is only relevant in
counter-profile-6.
9540
SLX# show interface stats detail interface Ve all
Interface Ve 38 statistics (ifindex 1207959590 (0x48000026))
RX TX
Packets 0 41718669
Bytes 0 5256551919
Interface Ve 138 statistics (ifindex 1207959690 (0x4800008a))
RX TX
Packets 0 8
Bytes 0 553
SLX#
9640
SLX# show interface stats detail interface Ve all
Interface Ve 15 statistics (ifindex 1207959567 (0x4800000f))
RX TX
Packets 0 0
Bytes 0 0
Interface Ve 115 statistics (ifindex 1207959667 (0x48000073))
RX TX
Packets 0 41718663
Bytes 0 5256551538
SLX#
This example displays the VE statistics. For 9540 and 9640, this output is only relevant in counter-
profile-6.
9540
SLX# show interface stats detail interface Ve 38
Interface Ve 38 statistics (ifindex 1207959590 (0x48000026))
RX TX
Packets 0 41718669
Bytes 0 5256551919
9640
SLX# show interface stats detail interface Ve 115
Interface Ve 115 statistics (ifindex 1207959667 (0x48000073))
RX TX
Packets 0 41718663
Bytes 0 5256551538
Syntax
show interface stats utilization-watermark
show interface stats utilization-watermark interface { ethernet slot /
port | port-channel index }
Parameters
interface
Specifies what type of interface to display.
ethernet
Specifies an Ethernet interface.
slot
Specifies a valid slot number.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel number.
Modes
Privileged EXEC mode
Usage Guidelines
You can filter the results by interface.
Output
The show interface stats utilization-watermark command displays the following
information:
Examples
The following example displays utilization watermarks for a specified Ethernet interface.
device# show interface stats utilization-watermark interface ethernet 1/1
Syntax
show interface status
Modes
Privileged EXEC mode
Output
The show interface status command displays the following information:
Examples
The following example displays the status of all device interfaces.
device# show interface status
--------------------------------------------------------------------------------
Port Status Mode Speed Type Description
--------------------------------------------------------------------------------
Eth 1/1 adminDown -- -- --
Eth 1/2 adminDown -- -- --
Eth 1/3 adminDown -- -- --
...
Eth 1/15 notconnected -- -- 40G-QSFP -
...
Eth 3/4 connected (up) -- 10G 10G-SFP-SR
(output
truncated)
show inventory
Displays the hardware inventory of the device.
Syntax
show inventory [ chassis | fan | module | powerSupply ]
Parameters
chassis
Displays information about the device.
fan
Displays information about the fan.
module
Displays information about the module.
powerSupply
Displays information about the power supply.
Modes
Privileged EXEC mode
Examples
The following is an example of typical command output.
device# show inventory
Syntax
show ip arp inspection [ vlan vlan-range ]
Parameters
vlan vlan-range
Specifies a VLAN, multiple VLANs (separated by commas with no spaces), a range of VLANs, or
a combination of specified VLANs and ranges of VLANs. Valid values are from 1 through 4090.
Modes
Privileged EXEC mode
Output
The show ip arp inspection command displays the following information:
ACL Match Displays the name of the ARP ACL that is applied.
Examples
The following example displays DAI information for all VLANs.
device# show ip arp inspection
Vlan Configuraton Operation ACL Match
-------------------------------------------------
1 Enabled Active
10 Disabled Inactive
100 Enabled Active acl1
1000 Enabled Active
20 Disabled Inactive
200 Disabled Inactive
2000 Enabled Active acl1
The following example displays DAI information for specified VLANs and a range of VLANs.
device# show ip arp inspection vlan 1,100,200-2000
Vlan Configuraton Operation ACL Match
--------------------------------------------------
1 Enabled Active
100 Enabled Active acl1
1000 Enabled Active
200 Disabled Inactive
2000 Enabled Active acl1
Syntax
show ip arp inspection interfaces [ ethernet slot / port | port-channel
index ]
Parameters
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
Modes
Privileged EXEC mode
Usage Guidelines
On VLANs that are enabled for Dynamic ARP Inspection (DAI), interfaces that are not listed in the
command output are untrusted.
Output
The show ip arp inspection interfaces command displays the following information:
Examples
The following example displays all trusted interfaces.
device# show ip arp inspection interfaces
Interface Trust State
---------------------------------------
Po 200 Trusted
Eth 2/0 Trusted
The following example displays the trust state of Ethernet interface 4/0.
device# show ip arp inspection interfaces ethernet 4/0
Interface Trust State
---------------------------------------
Eth 4/0 Trusted
Syntax
show ip arp suppression-cache [ summary ]
show ip arp suppression-cache bridge-domain bridge-domain-id
show ip arp suppression-cache vlan vlan-id
Parameters
summary
Specifies summary format.
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Output
The show ip arp suppression-cache command displays the following information:
Examples
The following example displays the results of the basic form of this command.
device# show ip arp suppression-cache
Flags: L - Locally Learnt Adjacency
R - Remote Learnt Adjacency
RS - Remote Static Adjacency
Number of Locally Learnt Adjacency: 0
Number of Remotely Learnt Adjacency: 2794
Syntax
show ip arp suppression-statistics
show ip arp suppression-statistics bridge-domain bridge-domain-id
show ip arp suppression-statistics vlan vlan-id
Parameters
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Output
The show ip arp suppression-statistics command displays the following information:
Examples
The following example displays the results of the basic form of this command.
device# show ip arp suppression-statistics
Vlan/Bd Forwarded Suppressed Remote-arp Proxy
----------------------------------------------------------
110 (V) 0 24 0
254 (V) 3 10 0
Syntax
show ip arp suppression-status
show ip arp suppression-status bridge-domain bridge-domain-id
show ip arp suppression-status vlan vlan-id
Parameters
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Output
The show ip arp suppression-status command displays the following information:
Examples
The following example displays the results of the basic form of this command.
device# show ip arp suppression-status
Vlan/Bd Configuration Evpn-Register Operation
--------------------------------------------------------------------------------
4003 (V) Enabled Yes Active
show ip bgp
Displays BGP4 route information.
Syntax
show ip bgp
show ip bgp ip-addr [ /prefix ]
show ip bgp ip-addr [ /prefix ] [ longer-prefixes ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation, with an optional mask.
/prefix
IPv4 mask length in CIDR notation.
longer-prefixes
Filters prefixes equal to or greater than that specified by prefix.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays sample output from the show ip bgp command.
device# show ip bgp
Syntax
show ip bgp attribute-entries [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
The route-attribute entries table lists the sets of BGP4 attributes that are stored in device memory. Each
set of attributes is unique and can be associated with one or more routes. In fact, the device typically
has fewer attribute entries than routes. Use this command to view BGP4 route-attribute entries that are
stored in device memory.
Examples
The following example show sample output for the show ip bgp attribute-entries command.
Syntax
show ip bgp dampened-paths [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ip bgp dampened-paths command.
device# show ip bgp dampened-paths
Syntax
show ip bgp filtered-routes [ detail ] [ ip-addr { / mask } [ longer-
prefixes ] ] | as-path-access-list name | prefix-list name ] [ vrf
vrf-name ]
Parameters
detail
Optionally displays detailed route information.
ip-addr
IPv4 address of the destination network in dotted-decimal notation.
mask
(Optional) IPv4 mask of the destination network in CIDR notation.
longer-prefixes
Specifies all statistics for routes that match the specified route, or that have a longer prefix than
the specified route.
as-path-access-list name
Specifies an AS-path ACL. The name must be between 1 and 32 ASCII characters in length.
prefix-list name
Specifies an IP prefix list. The name must be between 1 and 32 ASCII characters in length.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays BGP4 filtered routes.
Syntax
show ip bgp flap-statistics
show ip bgp flap-statistics ip-addr { / mask } [ longer-prefixes [ vrf
vrf-name ] | vrf vrf-name ]
show ip bgp flap-statistics neighbor ip-addr [ vrf vrf-name ]
show ip bgp flap-statistics regular-expression name [ vrf vrf-name ]
show ip bgp flap-statistics vrf vrf-name
Parameters
ip-addr
IPv4 address of a specified route in dotted-decimal notation.
mask
IPv4 mask of a specified route in CIDR notation.
longer-prefixes
Displays statistics for routes that match the specified route or have a longer prefix than the
specified route.
vrf vrf-name
Specifies a VRF instance.
neighbor
Displays flap statistics only for routes learned from the specified neighbor.
ip-addr
IPv4 address of the neighbor.
regular-expression
Specifies a regular expression in the display output on which to filter.
name
Name of an AS-path filter or regular expression.
Modes
Privileged EXEC mode
Examples
The following example displays flap statistics for a neighbor.
Syntax
show ip bgp neighbors [ ip-addr ]
show ip bgp neighbors last-packet-with-error [ vrf vrf-name ]
show ip bgp neighbors routes-summary [ vrf vrf-name ]
show ip bgp neighbors vrf vrf-name
Parameters
ip-addr
Specifies the IPv4 address of a neighbor.
last-packet-with-error
Displays the last packet with an error.
route-summary
Displays routes received, routes accepted, number of routes advertised by peer, and so on.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Output shows all configured parameters for the neighbors. Only the parameters whose values differ
from the default values are shown.
Dynamic neighbors are displayed only by using the show ip bgp neighbors commands with no
options.
Examples
device# show ip bgp neighbors
RefreshCapability: Received
Messages: Open Update KeepAlive Notification Refresh-Req
Sent : 2 15 3339 1 0
Received: 2 0 3356 0 0
Last Update Time: NLRI Withdraw NLRI
Withdraw
Tx: 0h1m32s --- Rx: ---
---
Last Connection Reset Reason:User Reset Peer Session
Notification Sent: Cease/Administrative Reset
Notification Received: Unspecified
Neighbor NLRI Negotiation:
Peer configured for IPV4 unicast Routes
Neighbor AS4 Capability Negotiation:
Outbound Policy Group:
ID: 2, Use Count: 2
BFD:Disabled
Byte Sent: 146, Received: 0
Local host: 123.123.123.2, Local Port: 44575
Remote host: 123.123.123.3, Remote Port: 179
G-Shut:
Enabled: yes, g-shut timer: 600 seconds, Route-map: none
g-shut timer Expire in 200 seconds
local-preference 0 gshut community 1200
The following example shows sample output about dynamically created BGP neighbors.
device# show ip bgp neighbors
RefreshCapability: Received
Address Family : L2VPN EVPN
SendExtendedCommunity: yes
Messages: Open Update KeepAlive Notification Refresh-Req
Sent : 4 18 178 3 0
Received: 4 42 177 0 0
Last Update Time: NLRI Withdraw NLRI
Withdraw
Tx: 1h56m21s --- Rx: 1h56m20s
---
Last Connection Reset Reason:User Reset Peer Session
Notification Sent: Cease/Administrative Reset
Notification Received: Unspecified
Neighbor NLRI Negotiation:
Peer Negotiated L2VPN EVPN address family
Peer configured for IPV4 unicast Routes
Peer configured for L2VPN EVPN address family
Neighbor ipv6 MPLS Label Capability Negotiation:
Neighbor AS4 Capability Negotiation:
Outbound Policy Group:
ID: 2, Use Count: 3
Last update time was 4667 sec ago
BFD:Disabled
Byte Sent: 2968, Received: 0
Local host: 98.0.0.2, Local Port: 8231
Remote host: 98.0.0.1, Remote Port: 179
Syntax
show ip bgp neighbors ip-addr advertised-routes [ detail | / mask-bits ]
[ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
detail
Displays details of advertised routes.
mask-bits
Number of mask bits in CIDR notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays the details of advertised routes.
device# show ip bgp neighbors 123.123.123.3 advertised-routes
Syntax
show ip bgp neighbors ip-addr flap-statistics [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example shows flap statistics.
Syntax
show ip bgp neighbors ip-addr last-packet-with-error [ decode ] [ vrf
vrf-name ]
Parameters
ip-addr
IP address of a neighbor in dotted-decimal notation.
decode
Decodes last packet that contained an error from any of a device's neighbors.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example shows sample output from the show ip bgp neighbors last-packet-with-
error command when no packet from a specified neighbor contained an error.
device# show ip bgp neighbors 123.123.123.3 last-packet-with-error
BGP Header
Marker: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
Message Length: (0x002d) 45
Message Type: (0x01) OPEN
OPEN Message
Version: (0x04) 4
AS Number: (0x014b) 331
Hold Time: (0x00b4) 180
BGP Identifier: (0x09090909) 9.9.9.9
Optional Parameter length: (0x10) 16
Syntax
show ip bgp neighbors ip-addr received
show ip bgp neighbors ip-addr received detail [ vrf vrf-name ]
show ip bgp neighbors ip-addr received prefix-filter [ vrf vrf-name ]
show ip bgp neighbors ip-addr vrf vrf-name
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
detail
Displays detailed information for ORFs received from BGP4 neighbors of the device.
vrf vrf-name
Specifies a VRF instance.
prefix-filter
Displays the results for ORFs that are prefix-based.
Modes
Privileged EXEC mode
Examples
The following example displays output for the show ip bgp neighbors received command.
Syntax
show ip bgp neighbors ip-addr received-routes [ detail ] [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
detail
Displays detailed route information.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays output for the show ip bgp neighbors received-routes
command.
device# show ip bgp neighbors 160.160.160.10 received-routes
Syntax
show ip bgp neighbors ip-addr rib-out-routes ip-addr mask [ vrf vrf-
name ]
show ip bgp neighbors ip-addr rib-out-routes detail ip-addr mask [ vrf
vrf-name ]
show ip bgp neighbors ip-addr rib-out-routes detail [ vrf vrf-name ]
show ip bgp neighbors ip-addr rib-out-routes [ vrf vrf-name ]
Parameters
ip-addr
IP address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
detail
Displays detailed RIB route information.
Modes
Privileged EXEC mode
Examples
This example shows sample output from the show ip bgp neighbors rib-out-routes
command.
device# show ip bgp neighbors 123.123.123.3 rib-out-routes
Syntax
show ip bgp neighbors ip-addr routes
show ip bgp neighbors ip-addr routes { best | not-installed-best |
unreachable } [ vrf vrf-name ]
show ip bgp neighbors ip-addr routes detail { best | not-installed-best |
unreachable } [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
best
Displays routes received from the neighbor that are the best BGP4 routes to their destination.
not-installed-best
Displays routes received from the neighbor that are the best BGP4 routes to their destination but
were not installed in the route table because the device received better routes from other
sources.
unreachable
Displays routes that are unreachable because the device does not have a valid RIP, OSPF, or
static route to the next hop.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays
Syntax
show ip bgp neighbors ip-addr routes-summary [ vrf vrf-name ]
Parameters
ip-addr
IPv4 address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays route summary information received in UPDATE messages.
Syntax
show ip bgp peer-group peer-group-name [ vrf vrf-name ]
Parameters
peer-group-name
Specifies a peer group name.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Only the parameters that have values different from their defaults are listed.
Examples
This example shows sample output from the show ip bgp peer-group command.
Syntax
show ip bgp routes [ num | ip-address/prefix | age num | as-path-access-
list name | best | cidr-only | community-access-list name |
community-reg-expression expression | detail | large-community |
local | neighbor ip-addr | nexthop ip-addr | no-best | not-installed-
best | prefix-list string | regular-expression name | route-map name
| summary | unreachable ] [ vrf vrf-name ]
Parameters
num
Table entry at which the display starts.
ip-address/prefix
Table entry at which the display starts.
age
Displays BGP4 route information that is filtered by age.
as-path-access-list name
Displays BGP4 route information that is filtered by autonomous system (AS)-path access control
list (ACL). The name must be between 1 and 32 ASCII characters in length.
best
Displays BGP4 route information that the device selected as best routes.
cidr-only
Displays BGP4 routes whose network masks do not match their class network length.
community-access-list name
Displays BGP4 route information for an AS-path community access list. The name must be
between 1 and 32 ASCII characters in length.
community-reg-expression expression
Displays BGP4 route information for an ordered community-list regular expression.
detail
Displays BGP4 detailed route information.
large-community
Displays routes that match the large community identifier.
local
Displays BGP4 route information about selected local routes.
neighbor ip-addr
Displays BGP4 route information about selected BGP neighbors.
nexthop ip-addr
Displays BGP4 route information about routes that are received from the specified next hop.
no-best
Displays BGP4 route information that the device selected as not best routes.
not-installed-best
Displays BGP4 route information about best routes that are not installed.
prefix-list string
Displays BGP4 route information that is filtered by prefix list. The string must be between 1 and
32 ASCII characters in length.
regular-expression name
Displays BGP4 route information about routes that are associated with the specified regular
expression.
route-map name
Displays BGP4 route information about routes that use the specified route map.
summary
Displays BGP4 summary route information.
unreachable
Displays BGP4 route information about routes whose destinations are unreachable through any
of the BGP4 paths in the BGP4 route table.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ip bgp routes command when an IP
address is specified.
SLX# show ip bgp routes 93.175.135.0/24
Number of BGP Routes matching display condition : 1
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE x:BEST-EXTERNAL
RPKI State V: Valid I: Invalid N: Not found ?: Undefined
Prefix Next Hop MED LocPrf Weight RPKI State Status
1 93.175.135.0/24 50.0.0.2 none 100 0 I BEx
AS_PATH: 12654
Last update to IP routing table: 0h1m12s
Route is advertised to 1 peers:
40.0.0.1(100)
The following example shows sample input from the show ip bgp routes summary command.
Syntax
show ip bgp routes community { num | internet | local-as | no-advertise |
no-export } [ vrf vrf-name ]
Parameters
community
Displays routes filtered by a variety of communities.
num
Specific community member.
internet
Displays routes for the Internet community.
local-as
Displays routes for a local sub-AS within the confederation.
no-advertise
Displays routes with this community that cannot be advertised to any other BGP4 devices at all.
no-export
Displays routes for the community of sub-ASs within a confederation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows output from the show ip bgp routes community command
when the internet keyword is used.
Syntax
show ip bgp routes [ detail ] large-community ADMIN:OPER1:OPER2 [ vrf
vrf-name ]
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP routes with large-community attributes
matching the specified value. If you omit this keyword, brief information is displayed.
ADMIN
A four-octet namespace identifier for a BGP Large-Communities Global Administrator.
OPER1
A four-octet operator-defined value for BGP Large-Communities Local Data Part 1.
OPER2
A four-octet operator-defined value for BGP Large-Communities Local Data Part 2.
vrf vrf-name
Specifies a VRF instance.
Examples
The following example provides a summary of information about the large community.
device# show ip bgp routes large-community 1:2:3
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE x:BEST-EXTERNAL
Prefix Next Hop MED LocPrf Weight Status
1 150.150.150.0/24 192.168.1.20 0 100 0 BEx
AS_PATH: 1639
2 150.150.151.0/24 192.168.1.20 0 100 0 BEx
AS_PATH: 1639
3 150.150.152.0/24 192.168.1.20 0 100 0 E
AS_PATH: 1639
The following example provides detailed information about the large community.
device# show ip bgp routes detail large-community 1:2:3
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE x:BEST-EXTERNAL
Syntax
show ip bgp routes [ detail ] large-community access-list
large_community_ACL [ vrf vrf-name ]
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP routes matching the specified large
community access list. If you omit this keyword, brief information is displayed.
large_community_ACL
Name of the large community defined in a standard or extended large community access list
vrf vrf-name
Specifies a VRF instance.
Examples
The following example displays brief information of all BGP routes with large community attributes that
match the large community access-list, lcstdacl1.
device# show ip bgp routes large-community access-list lcstdacl1
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE x:BEST-EXTERNAL
Prefix Next Hop MED LocPrf Weight Status
1 150.150.150.0/24 192.168.2.20 0 100 0 E
AS_PATH: 1639
2 150.150.151.0/24 192.168.2.20 0 100 0 E
AS_PATH: 1639
3 150.150.152.0/24 192.168.2.20 0 100 0 E
AS_PATH: 1639
Syntax
show ip bgp routes [ detail ] large-community reg-expression regex_value
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP routes with large-community attributes
matching the specified REGEX. If you omit this keyword, brief information is displayed.
regex_value
REGEX value.
Examples
The following example displays the BGP routes that match the specified REGEX value.
device# show ip bgp routes large-community reg-expression (1|8):(.*):(.*)
Searching for matching routes, use ^C to quit...
Status A:AGGREGATE B:BEST b:NOT-INSTALLED-BEST C:CONFED_EBGP D:DAMPED
E:EBGP H:HISTORY I:IBGP L:LOCAL M:MULTIPATH m:NOT-INSTALLED-MULTIPATH
S:SUPPRESSED F:FILTERED s:STALE x:BEST-EXTERNAL
Prefix Next Hop MED LocPrf Weight Status
1 150.150.150.0/24 192.168.1.20 0 100 0 BEx
AS_PATH: 1639
2 150.150.150.0/24 192.168.2.20 0 100 0 E
AS_PATH: 1639
3 150.150.151.0/24 192.168.1.20 0 100 0 BEx
AS_PATH: 1639
4 150.150.151.0/24 192.168.2.20 0 100 0 E
AS_PATH: 1639
5 150.150.152.0/24 192.168.1.20 0 100 0 E
AS_PATH: 1639
6 150.150.152.0/24 192.168.2.20 0 100 0 E
AS_PATH: 1639
Syntax
show ip bgp rpki details
Modes
Privileged EXEC mode
Usage Guidelines
By default you can use one RPKI server for validation. The current in use server is indicated with the
status RTR_ESTABLISHED.
Examples
This command displays the list of configured RPKI priorities, the RPKI servers configured for those
priorities, and the status of the connection for these RPKI servers.
SLX# show ip bgp rpki details
BGP RPKI Server Detail
Priority number 1
Protocol VRF Host Port Status
TCP mgmt-vrf 141.22.28.252 8283 RTR_ESTABLISHED
Priority number 2
Protocol VRF Host Port Status
TCP mgmt-vrf 1.2.3.4 323 RTR_CLOSED
SLX#
Syntax
show ip bgp rpki server summary
Modes
Privileged EXEC mode
Examples
This example shows the output of the show ip bgp RPKI server summary command which
displays the state of the connection with the RPKI server being used for validation.
SLX(config)# show ip bgp rpki server summary
BGP RPKI Server Summary
Protocol VRF Host Port Status
TCP mgmt-vrf 141.22.28.252 8283 RTR_ESTABLISHED
Syntax
show ip bgp rpki table
Modes
Privileged EXEC mode
Examples
This example shows the output of the show ip bgp rpki table command which displays the
currently cached list of networks and AS numbers received from the RPKI server.
SLX# show ip bgp rpki table
BGP RPKI table
Network Min-Len Max-Len Origin-AS
1.128.0.0 11 11 1221
1.0.7.0 24 24 38803
1.0.6.0 24 24 38803
1.0.5.0 24 24 38803
1.0.4.0 24 24 38803
1.0.0.0 24 24 13335
Syntax
show ip bgp summary [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays summary BGP information.
device# show ip bgp summary
BGP4 Summary
Router ID: 10.10.10.10 Local AS Number: 2040
Confederation Identifier: not configured
Confederation Peers:
Maximum Number of IP ECMP Paths Supported for Load Sharing: 1
Number of Neighbors Configured: 1040, UP: 4
Number of Routes Installed: 3079574, Uses 483493118 bytes
Number of Routes Advertising to All Neighbors: 107925658 (17078048 entries), Uses
1297931648 bytes
Number of Attribute Entries Installed: 1296243, Uses 230731254 bytes
'+': Data in InQueue '>': Data in OutQueue '-': Clearing
'*': Update Policy 'c': Group change 'p': Group change Pending
'r': Restarting 's': Stale '^': Up before Restart '<': EOR waiting
'$': Learning-Phase (for Delayed Route Calculation)
'#': RIB-in Phase
Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend
16.1.1.1 65200 ESTAB 2h26m 8s 10011 0 1 0
17.1.1.1 65200 ESTAB 2h26m 8s 10011 0 10010 0
18.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
19.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
20.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
21.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
22.1.1.1 65200 ESTAB 2h26m 2s 10011 0 10011 0
23.1.1.1 65200 ESTAB 2h26m 7s 10011 0 10011 0
…
The $ : Learning-Phase (for Delayed Route Calculation) notation denotes that the BGP peer with this
notation is learning bulk route updates. More than one peer can be in Learning-Phase. BGP BEST-Path
selection is delayed until all the peers complete Learning-Phase. A peer can be in Learning-Phase only if
BGP delayed route calculation feature is enabled and in specific scenarios as described in the init-
route-calc-delay command.
The # : RIB-IN Phase notation denotes that a peer is learning bulk route updates. When one or more
peer is in RIB-IN phase, BGP provides high preference for learning incoming route-updates and less
preference for advertising routes (to outbound peers). An incoming route-update can possibly cause a
BGP BEST-path change and eventually recompute RIB-OUT for outbound peers. Slowing down RIB-
OUT until all peers complete learning route updates will improve BGP performance. This feature is
enabled by default and does not require additional configuration. Unlike BGP delayed route calculation,
BGP BEST-Path selection is not delayed in this Phase.
This example displays summary information when automatic discovery of neighbors is enabled for BGP.
device# show ip bgp summary
BGP4 Summary
Router ID: 4.4.4.4 Local AS Number: 100
Confederation Identifier: not configured
Confederation Peers:
Maximum Number of IP ECMP Paths Supported for Load Sharing: 1
Number of Neighbors Configured: 1, UP: 1
Number of Routes Installed: 0
Number of Routes Advertising to All Neighbors: 0 (0 entries)
Number of Attribute Entries Installed: 0
*Dynamically created based on a listen range command
Dynamically created neighbors: 0/100(max)
A – Auto discovered LLDP neighbors using LLDP
Auto discovered LLDP neighbors: 1
Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend
A 56.1.1.2 100 ESTAB 0h20m 7s 0 0 0 0
This example displays summary information about dynamically created BGP neighbors.
device# show ip bgp summary
BGP4 Summary
Router ID: 10.1.1.1 Local AS Number: 100
Confederation Identifier: not configured
Confederation Peers:
Maximum Number of IP ECMP Paths Supported for Load Sharing: 1
Number of Neighbors Configured: 3, UP: 1
Number of Routes Installed: 7, Uses 840 bytes
Number of Routes Advertising to All Neighbors: 6 (2 entries), Uses 120 bytes
Number of Attribute Entries Installed: 4, Uses 460 bytes
Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend
*10.1.2.1 100 CONN 1h51m27s 0 0 0 2
* Dynamically created based on a listen range command
Dynamically created neighbors: 1/(200 max)
Syntax
show ip bgp vpnv4 routes [ detail ] large-community ADMIN:OPER1:OPER2
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP VPNv4 routes with large-community
attributes matching the specified value. If you omit this keyword, brief information is displayed.
ADMIN
A four-octet namespace identifier for a BGP Large-Communities Global Administrator.
OPER1
A four-octet operator-defined value for BGP Large-Communities Local Data Part 1.
OPER2
A four-octet operator-defined value for BGP Large-Communities Local Data Part 2.
Examples
The following is an example command.
device# show ip bgp vpnv4 routes large-community 1:2:3
Syntax
show ip bgp vpnv4 routes [ detail ] large-community access-list
large_community_ACL
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP VPNv4 routes matching the specified large
community access list. If you omit this keyword, brief information is displayed.
large_community_ACL
Name of the large community defined in a standard or extended large community access list
Examples
The following example displays brief information of all BGP VPNv4 routes with large community
attributes that match the large community access-list, lcstdacl1.
device# show ip bgp vpnv4 routes large-community access-list lcstdacl1
Syntax
show ip bgp vpnv4 routes [ detail ] large-community reg-expression
regex_value
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP VPNv4 routes with large-community
attributes matching the specified REGEX. If you omit this keyword, brief information is displayed.
regex_value
REGEX value.
Examples
The following example displays the BGP VPNv4 routes that match the specified REGEX value.
device# show ip bgp vpnv4 routes large-community reg-expression _456778*
Syntax
show ip bgp vpnv6 routes [ detail ] large-community ADMIN:OPER1:OPER2
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP VPNv6 routes with large-community
attributes matching the specified value. If you omit this keyword, brief information is displayed.
ADMIN
A four-octet namespace identifier for a BGP Large-Communities Global Administrator.
OPER1
A four-octet operator-defined value for BGP Large-Communities Local Data Part 1.
OPER2
A four-octet operator-defined value for BGP Large-Communities Local Data Part 2.
Examples
The following is an example command.
device# show ip bgp vpnv6 routes large-community 1:2:3
Syntax
show ip bgp vpnv6 routes [ detail ] large-community access-list
large_community_ACL
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP VPNv6 routes matching the specified large
community access list. If you omit this keyword, brief information is displayed.
large_community_ACL
Name of the large community defined in a standard or extended large community access list
Examples
The following example displays brief information of all BGP VPNv6 routes with large community
attributes that match the large community access-list, lcstdacl1.
device# show ip bgp vpnv6 routes large-community access-list lcstdacl1
Syntax
show ip bgp vpn6 routes [ detail ] large-community reg-expression
regex_value
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP VPNv6 routes with large-community
attributes matching the specified REGEX. If you omit this keyword, brief information is displayed.
regex_value
REGEX value.
Examples
The following example displays the BGP VPNv6 routes that match the specified REGEX value.
device# show ip bgp vpnv6 routes large-community reg-expression _456778*
Syntax
show ip dhcp relay address interface [ ethernet slot/port | port-channel
number | ve interface number ]
Parameters
ethernet slot/port
Interface name in slot/port format.
port-channel number
Specifies a port-channel.
ve interface number
Interface name in slot/port format.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example displays DHCP relay address(es) configured on interface 1/4:
device# show ip dhcp relay address interface ethernet 1/4
--------- ------------- --------
Interface Relay Address VRF Name
--------- ------------- --------
Eth 1/4 10.3.4.5 blue
Eth 1/4 10.5.1.1 default-vrf
Syntax
show ip dhcp relay gateway {interface [ ethernet slot/port | port-
channel number | Ve number ]}
Parameters
interface
The interface ethernet slot/port number or the Ve number.
ethernet slot/port
Specifies a physical interface.
port-channel number
Specifies a port-channel.
ve ve-number
Specifies a virtual Ethernet interface.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the gateway address configured on the switch or on the interface.
Examples
To display the gateway address configured on the switch:
device# show ip dhcp relay gateway
--------- -------------
Interface Gateway Address
--------- -------------
Eth 3/5 10.1.1.1
Ve 100 100.1.1.1
Syntax
show ip dhcp relay statistics
Modes
Privileged EXEC mode
Usage Guidelines
The show ip dhcp relay statistics command displays the following information about the IP
DHCP Relay function for IP DHCP Relay addresses configured on the switch:
• DHCP Server IP Address configured in the switch.
• Number of DHCP DISCOVERY, OFFER, REQUEST, ACK, NAK, DECLINE, and RELEASE packets
received.
• Number of DHCP client packets received (on port 67) and relayed by the Relay Agent.
• Number of DHCP server packets received (on port 67) and relayed by the Relay Agent.
DHCP unicast packets are forwarded directly per route. These packets are not trapped to the
management module. As a result, the DHCP renewal Request/ACK and DHCP Release packets are not
be counted toward statistics.
Examples
To display general information about the DHCP relay function:
device# show ip dhcp relay statistics
DHCP Relay Statistics:
------------------------
Address Disc. Offer Req. Ack Nak Decline Inform
------- ----- ----- ---- --- --- ------- ------
10.1.0.1 400 100 2972 2968 0 0
0
20.2.0.1 400 100 2979 2975 0 0
0
30.3.0.1 400 100 3003 2998 0 0
0
40.4.0.1 400 100 3026 3018 0 0
0
Syntax
show ip dhcp snooping brief
show ip dhcp snooping informationoption
show ip dhcp snooping [vlanvlan-id ]
show ip dhcp snooping interface [ switchport interface]
show ip dhcp snoopingbinding entries [vlanvlan-id ] [ interface
switchport interface vlan vlan-id ip-address ip-addr mac mac-addr]
show ip dhcp snoopingbinding stats
Parameters
brief
Displays brief information on DHCP snooping-enabled VLANs and the trusted state of member
ports.
informationoption
Displays the state of the Option-82 feature on the device, including the Circuit-ID and Remote-ID
information for all the DHCP snooping-enabled VLANs.
vlanvlan-id
Displays information about DHCP snooping on all configured VLANs or on the specified VLAN.
interface [ switchport interface
Displays information about DHCP snooping configuration for all switchports or the specified
switchport.
binding entries [vlanvlan-id ] [ interface switchport interface vlan
vlan-id ip-address ip-addr mac mac-addr]
Displays the complete binding database or displays database entries that are specific to the
options you select.
binding stats
Displays statistics about the DHCP snooping binding entry database.
Modes
Privileged EXEC mode
Examples
The following example shows....
Syntax
show ip flowspec rules [ detail ] [ local | remote ] [ vrf vrf-name ]
Parameters
detail
Specifies the display of detailed information which includes statistics for flowspec rules.
local
Specifies the display of only local flowspec rules.
remote
Specifies the display of only remote flowspec rules.
vrf vrf-name
Specifies the display of flowspec rule information for a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
When a VRF is not specified, the show ip flowspec rules command displays information for the
default VRF.
Displayed rules are sorted according to the sorting algorithm described in RFC 5575.
Output
The show ip flowspec rules command displays the following information:
Examples
The following example shows how to display BGP flowspec rule information for the default VRF.
The following example shows how to display detailed BGP flowspec rule information for the default
VRF.
VRF :default-vrf
Total number of Rules: 2
Statistic packets/bytes
------------- ------------
Matched 17412786/12589441782
Transmitted 1453/1048023
dropped 17411333/12588393759
Syntax
show ip igmp groups [ detail | interface | vlan vlan_id | bridge-domain
bridge-domain_id | cluster cluster_id | client client_id]
Parameters
detail
Displays detailed information.
interface
Specifies an interface type.
vlan vlan_id
Specifies a VLAN interface.
bridge-domain bridge-domain_id
Specifies a bridge-domain interface.
cluster cluster_id
Specifies a Multi-Chassis Trunk (MCT) cluster.
client client_id
Specifies a Cluster Client Edge Port (CCEP) client.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the IGMP database, including configured entries for either all groups on all
interfaces, or all groups on specific interfaces, or specific groups on specific interfaces.
Examples
The following example displays the IP IGMP groups.
device# show ip igmp groups
Total Number of Groups: 2
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Version
225.1.1.1 vlan25 00:05:27 00:02:32 25.1.1.120 2
Member Ports: eth 2/24
Syntax
show ip igmp interface [ ethernet slot/port | port-channel | Ve ]
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example displays IGMP protocol information for port-channel 1.
device# show ip igmp interface port-channel 1
Interface po1
IGMP disabled
The following example displays the output for the show ip igmp interface command.
Interface eth1/34
IGMP enabled
IGMP query interval 125 seconds
IGMP other-querier interval 255 seconds
IGMP query response time 10 seconds
IGMP last-member query interval 1
seconds
Interface Ve 10
IGMP enabled
IGMP query interval 125 seconds
IGMP other-querier interval 255 seconds
IGMP query response time 10 seconds
IGMP last-member query interval 1 seconds
IGMP immediate-leave enabled
IGMP querier 10.10.10.10(this system)
IGMP version 2
Syntax
show ip igmp snooping [mrouter vlan vlan_id | vlan vlan_id | bridge-
domain bridge-domain_id]
Parameters
mrouter vlan vlan_id
Specifies which VLAN interface to display the mrouter configuration related information.
vlan vlan_id
Specifies which VLAN interface to display the snooping configuration related information.
bridge-domain bridge-domain_id
Specifies which bridge-domain interface to display the snooping configuration related
information.
Modes
Privileged EXEC mode
Usage Guidelines
Use the show ip igmp snooping command to display IGMP snooping information, display
multicast router port related information for the specified VLAN, or to display snooping statistics for the
specified VLAN in the IGMP protocol module.
Examples
The following example displays IGMP snooping information.
device# show ip igmp snooping vlan 20
Vlan ID: 20
Multicast Router ports: eth4/2
Querier – Enabled,
IGMP Operation mode: IGMPv2
Is Fast-Leave Enabled : Disabled
Max Response time = 10
Last Member Query Interval = 1
Query interval = 125
Number of Multicast Groups: 1
Group: 225.0.0.1
Member Ports: eth4/2 eth6/15 po1
Mapped MAC address: 0100.5e00.0001
Bridge-domain ID: 20
Multicast Router ports: eth3/2.300
Querier – Enabled,
IGMP Operation mode: IGMPv2
Syntax
show ip igmp ssm-map
Modes
Privileged EXEC mode
Output
The show ip igmp ssm-map command displays the following information:
Examples
The following example shows the association between a configured prefix list and source address
mapped to it.
device# show ip igmp ssm-map
+------------------------------------+-------------------+
| PrefixList Name | Source Address |
+------------------------------------+-------------------+
ssm-map-230-to-232 203.0.0.10
ssm-map-233-to-234 204.0.0.11
Syntax
show ip igmp statistics bridge-domain bridge-domain_id
Parameters
bridge-domain bridge-domain_id
Specifies the bridge-domain ID.
Modes
Privileged EXEC mode
Examples
The following example displays the output for the show ip igmp statistics interface
bridge-domain command.
device# show ip igmp statistics interface bridge-domain 20
IGMP packet statistics for all interfaces in bridge-domain 20:
IGMP Message type Edge-Received Edge-Sent Edge-Rx-Errors
Membership Query 40 40 0
V1 Membership Report 40 40 0
V2 Membership Report 0 60 0
Group Leave 20 20 0
V3 Membership Report 0 0 0
PIM hello 0 0 0
IGMP Error Statistics:
Unknown types 0
Bad Length 0
Bad Checksum 0
Syntax
show ip igmp statistics interface [ ethernet slot/port | ve ve interface
ID ]
Parameters
ethernetslot/port
Represents an Ethernet interface name in slot/port format.
ve Ve interface number
Specifies a virtual Ethernet (VE) interface number. The range is 1 - 8192.
Modes
Privileged EXEC mode
Examples
The following example displays the output of the show ip igmp statistics interface
command.
device# show ip igmp statistics interface ve100
Syntax
show ip igmp statistics vlan vlan-id
Parameters
vlan-id
Specifies the VLAN-ID. The range is 1 through 4090.
Modes
Privileged EXEC mode
Examples
The following example displays the IP IGMP statistics on VLAN 1.
show ip interface
Displays the IP address, status, and configuration for a specified interface or for all interfaces.
Syntax
show ip interface { brief | ethernet slot/port | port-channel number }
Parameters
brief
Specifies a brief summary of IP interface status and configuration.
ethernet slot/port
Specifies an Ethernet slot and port.
port-channel number
Specifies a port-channel.
Modes
Privileged EXEC mode
Examples
The following example displays typical summary information about all interfaces.
device# show ip interface brief
Flags: I - Insight Enabled U - Unnumbered interface M - Redundant Management
Interface IP-Address Vrf
Status Protocol
================== ========== ==================
==================== ========
Loopback 42 42.42.42.2 mgmt-vrf
up up
Loopback 45 unassigned default-vrf administratively
down down
Ethernet 0/1 unassigned default-vrf
up down
Ethernet 0/2 unassigned default-vrf
up down
Ethernet 0/3 43.43.43.2 mgmt-vrf
up down
Ethernet 0/4 unassigned default-vrf
up up
Ethernet 0/5 unassigned default-vrf
up down
Ethernet 0/6 unassigned default-vrf
up down
Ethernet 0/7 unassigned default-vrf
up down
Ethernet 0/8 unassigned default-vrf
up down
Ethernet 0/9 unassigned default-vrf
up down
Ethernet 0/10 unassigned default-vrf
up up
The following example displays the IP interface status of a specified Ethernet port.
device# show ip interface ethernet 1/1
Ethernet 1/2 is up, line protocol is down (Link-OAM blocked link), Link-OAM is enabled
Hardware is Ethernet, address is 00e0.0c70.c005
Current address is 00e0.0c70.c005
Pluggable media present
Interface index (ifindex) is 406880257
MTU 1548 bytes
10G Interface
LineSpeed Actual : Nil
LineSpeed Configured : Auto, Duplex: Full
Priority Tag disable
Last clearing of show interface counters: 10:50:20
Queueing strategy: fifo
Receive Statistics:
67181801 packets, 8867997496 bytes
Unicasts: 67181799, Multicasts: 1, Broadcasts: 1
64-byte pkts: 1, Over 64-byte pkts: 4, Over 127-byte pkts: 67181796
Over 255-byte pkts: 0, Over 511-byte pkts: 0, Over 1023-byte pkts: 0
Over 1518-byte pkts(Jumbo): 0
Runts: 0, Jabbers: 0, CRC: 0, Overruns: 0
Errors: 0, Discards: 0
Transmit Statistics:
82627975 packets, 10906817712 bytes
Unicasts: 82627873, Multicasts: 11, Broadcasts: 89
Underruns: 0
Errors: 0, Discards: 0
Rate info:
Input 0.000000 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Output 0.001014 Mbits/sec, 1 packets/sec, 0.00% of line-rate
Time since last interface status change: 00:08:22
Syntax
show ip multicast snooping [ mcache vlan interface | vlan vlan-id ]
Parameters
mcache
Specifies the multicast cache entries.
vlan interface
Specifies which VLAN's snooping mcache entries should be displayed.
vlan
Specifies the VLAN.
vlan-id
Specifies the VLAN-ID.
Modes
User EXEC mode
Examples
The following example displays the output for the show ip multicast snooping mcache
command.
device# show ip multicast snooping mcache
Flags : V2|V3 : IGMP Receiver, P_G : PIM (*,G) Join, P_SG: PIM (S,G) Join
VlanID : 25
-------------
1(*, 225.1.1.1 )00:02:15NumOIF: 1
Outgoing Ports:
eth2/24 Flags: 0x14 ( V2) 00:02:15/126s
The following output displays v3 flag for entries learned through the IGMPv3 report.
device# show ip multicast snooping mca
Flags : V2|V3 : IGMP Receiver, P_G : PIM (*,G) Join, P_SG: PIM (S,G) Join
BR : PIM Blocked RPT
Vlan ID : 10
-------------
1 (20.20.20.20, 232.0.0.10 ) 22:37:48 NumOIF: 1
Outgoing Ports:
eth1/34 Flags: 0x24 ( V3) 00:00:08/252s
show ip ospf
Displays OSPF information.
Syntax
show ip ospf [ vrf name ]
Parameters
vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example shows sample output from the show ip ospf command.
Syntax
show ip ospf area { A.B.C.D | decimal } database link-state [ adv-router
router-id | advertise index | asbr { asbr-id | adv-router router-id }
| extensive | link-state-id id | network { net-id | adv-router
router-id } | nssa { nssa-id | adv-router router-id } | router
{ router-id | adv-router router-id } | self-originate | sequence-
number num | summary { id | adv-router router-id } ] [ vrf vrfname ]
show ip ospf area [ vrf vrfname ]
Parameters
A.B.C.D
Area address in dotted decimal format.
decimal
Area address in decimal format. Valid values range from 0 to 2147483647.
database link-state
Displays database link-state information.
adv-router router-id
Displays the link state for the advertising router that you specify.
advertise index
Displays the link state by Link State Advertisement (LSA) index.
asbr
Displays the link state for all autonomous system boundary router (ASBR) links.
asbr-id
Displays the state of a single ASBR link that you specify.
extensive
Displays detailed information for all entries in the OSPF database.
link-state-id id
Displays the link state by link-state ID.
network
Displays the link state by network link.
net-id
Displays the link state of a particular network link that you specify.
nssa
Displays the link state by not-so-stubby area (NSSA).
nssa-id
Displays the link state of a particular NSAA area that you specify.
router
Displays the link state by router link.
router-id
Displays the link state of a particular router link that you specify.
self-originate
Displays self-originated link states.
sequence-number num
Displays the link-state by sequence number that you specify.
summary
Displays the link state summary. Can specify link-state ID or advertising router ID.
id
Displays the link state for the advertising router that you specify.
vrf vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show ip ospf area command.
Number of Areas is 1
Syntax
show ip ospf border-routers [ A.B.C.D ] [ vrf vrfname ]
Parameters
A.B.C.D
Specifies the router ID in dotted decimal format.
vrf vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display information about area border routers (ABRs) and autonomous system
boundary routers (ASBRs). You can display information for all ABRs and ASBRs or for a specific router.
Examples
The following example displays information for all ABRs and ASBRs:
Syntax
show ip ospf config [ vrf name ]
Parameters
vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example shows sample output from the show ip ospf config command.
Redistribution: Disabled
Default OSPF Metric: 10
Maximum Paths: 8
OSPF Auto-cost Reference Bandwidth: Disabled
Default Passive Interface: Disabled
OSPF Redistribution Metric: Type2
OSPF External LSA Limit: 14913080
OSPF Database Overflow Interval: 0
RFC 1583 Compatibility: Disabled
VRF Lite capability: Disabled
Router id: 10.0.0.4
Syntax
show ip ospf database database-summary [ vrf vrfname ]
show ip ospf database external-link-state [ advertise index | extensive |
link-state-id id | router-id router-id | sequence-number num ] [ vrf
vrfname ]
show ip ospf database grace-link-state [ vrf vrfname ]
show ip ospf database link-state [ adv-router router-id | advertise index
| asbr { asbr-id | adv-router router-id } | extensive | link-state-id
id | network { net-id | adv-router router-id } | nssa { nssa-id |
adv-router router-id } | router { router-id | adv-router router-id }
| self-originate | sequence-number num | summary { id | adv-router
router-id } ] [ vrf vrfname ]
show ip ospf database [ vrf vrfname ]
Parameters
database-summary
Displays how many link state advertisements (LSAs) of each type exist for each area, as well as
total number of LSAs.
vrf name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
external-link-state
Displays information by external link state, based on the following parameters:
advertise index
Displays the hexadecimal data in the specified LSA packet. The index parameter identifies the
LSA packet by its position in the router’s External LSA table. To determine an LSA packet’s
position in the table, enter the show ip ospf external-link-state command.
extensive
Displays LSAs in decrypt format. Do not use this parameter in combination with other display
parameters because the entire database is displayed.
link-state-id id
Displays external LSAs for the LSA source that you specify.
router-id router-id
Displays external LSAs for the advertising router that you specify.
sequence-number num
Displays the External LSA entries for the hexadecimal LSA sequence number that you specify.
link-state
Displays the link state, based on the following parameters:
adv-router router-id
Displays the link state for the advertising router that you specify.
advertise index
Displays the hexadecimal data in the specified LSA packet. The index parameter identifies the
LSA packet by its position in the router’s external-LSA table. To determine an LSA packet’s
position in the table, enter the show ip ospf external-link-state command.
asbr
Displays autonomous system boundary router (ASBR) LSAs.
extensive
Displays LSAs in decrypt format. Do not use this parameter in combination with other display
parameters because the entire database is displayed.
link-state-id id
Displays LSAs for the LSA source that you specify.
network
Displays either all network LSAs or the LSAs for a network that you specify.
nssa
Displays either all NSSA LSAs or the LSAs for a not-so-stubby area (NSSA) that you specify.
router
Displays LSAs by router link.
router-id router-id
Displays LSAs for the advertising router that you specify.
self-originate
Displays self-originated LSAs.
sequence-number
Displays the LSA entries for the hexadecimal LSA sequence number that you specify.
summary
Displays summary information. You can specify link-state ID or advertising router ID.
adv-router router-id
Displays the link state for the advertising router that you specify.
Modes
Privileged EXEC mode
Examples
The following example shows output for the show ip ospf database command.
Link States
The following example shows output for the show ip ospf database command when the
database-summary keyword is used.
Syntax
show ip ospf filtered-lsa area { ip-address | decimal } { in | out }
[ vrf vrf-name ]
Parameters
ip-address
Specifies the IP address of an area.
decimal
Specifies an area address in decimal format. Valid values range from 0 through 2147483647.
in
Specifies the incoming direction.
out
Specifies the outgoing direction.
vrf vrf-name
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays information about type 3 LSA filtering in the out direction for OSPFv2
area 0.
Syntax
show ip ospf interface [ A.B.C.D | brief ] [ vrf vrf-name ]
show ip ospf interface [ ethernet slot/port | | loopback number | port-
channel number | ve vlan_id ] [ brief ] [ vrf vrf-name ]
show ip ospf interface [ vrf vrf-name ]
Parameters
A.B.C.D
Specifies interface IP address in dotted decimal format.
brief
Displays summary information.
vrf vrf-name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
ethernet slot/port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback port number. Valid values range from 1 through 255.
port-channel number
Specifies a port-channel.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example displays OSPF information about all enabled interfaces.
device# show ip ospf interface
Syntax
show ip ospf neighbor [ extensive ] [ ethernet slot/port | port-channel
number | router-id A.B.C.D | ve vlan_id ] [ vrf vrf-name ]
show ip ospf neighbor [ vrf vrf-name ]
Parameters
extensive
Displays detailed neighbor information.
ethernet slot/port
Specifies an Ethernet slot and port.
port-channel number
Specifies a port-channel.
router-id A.B.C.D
Displays neighbor information for the specified router ID (in dotted decimal format).
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
vrf vrf-name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF
instance are shown in the output.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example displays information about OSPF neighbors.
device# show ip ospf neighbor
Syntax
show ip ospf redistribute route [ A.B.C.D:M ] [ vrf vrfname ]
Parameters
A.B.C.D:M
Specifies an IP address and mask for the output.
vrf vrfname
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
Modes
Privileged EXEC mode
Syntax
show ip ospf routes [ A.B.C.D ] [ vrf vrfname ]
Parameters
A.B.C.D
Specifies a destination IP address in dotted decimal format.
vrf vrfname
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display routes that OSPF calculated. You can display all routes or you can display
information about a specific route.
Examples
The following example displays all OSPF-calculated routes.
Syntax
show ip ospf summary [ vrf vrfname | all-vrfs| all-vrfs total]
Parameters
vrf vrfname
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
all-vrfs
Specifies all VRF instances. If this option is not used, details for the default VRF are shown in the
output.
all-vrfs total
Displays the cumulative summary of OSPF information with the total numbers for all of the VRF
intances. If this option is not used, details for the default VRF are shown in the output.
Modes
Privileged EXEC mode
Examples
The following example shows sample output with the details for the default VRF from the show ip
ospf summary command.
The following example shows sample output from the show ip ospf summary all-vrfs
command.
The following example shows sample output from the show ip ospf summary all-vrfs
total command.
---------------------------------------------
Number of VRFs: 1
Number of Interfaces: 200
Number of Neighbors: 200
Number of Neighbors in Full state: 200
Number of LSAs: 182600
Number of Routes: 102600
device#
Syntax
show ip ospf traffic
show ip ospf traffic [ ethernet slot/port | loopback number | ve vlan_id]
[ vrf vrf-name ]
Parameters
interface
Specifies an interface.
ethernet slot / port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
vrf vrf-name
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display details of OSPF traffic sent and received. You can display all traffic or
specify a particular interface.
Examples
The following example shows all OSPF traffic.
device# show ip ospf traffic
Syntax
show ip ospf virtual link [ index ] [ vrf vrfname ]
Parameters
index
Shows information about all virtual links or one virtual link that you specify.
vrf vrfname
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example shows information about all virtual links.
Syntax
show ip ospf virtual neighbor [ index ] [ vrf vrfname ]
Parameters
index
Shows information about all virtual neighbors or one virtual neighbor that you specify.
vrf vrfname
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example shows information about all virtual neighbors:
device# show ip ospf virtual neighbor
Syntax
show ip pim bsr [ vrf vrf-name ]
Parameters
vrf vrf-name
Displays information for a specific VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
When entered without the vrf option, this command displays information for the default VRF instance.
Output
The show ip pim bsr command displays the following information:
Next bootstrap Indicates how much time will pass before the BSR sends the next bootstrap
message in message. The time is displayed in "hh:mm:ss" format.
Next Candidate-RP- Indicates how much time will pass before the BSR sends the next candidate PR
advertisement advertisement message. The time is displayed in "hh:mm:ss" format.
message in
Note: This field appears only if this device is a candidate BSR.
group prefixes Indicates the multicast groups for which the RP listed by the previous field is a
candidate RP.
Examples
The following example shows information for a device that has been elected as the BSR.
device# show ip pim bsr
PIMv2 Bootstrap information
------------------------------------------------------------------------------
This system is the Elected BSR
BSR address: 1.51.51.1. Hash Mask Length 32. Priority 255.
Next bootstrap message in 00:01:00
Configuration:
Candidate loopback 2 (Address 1.51.51.1). Hash Mask Length 32. Priority 255.
Next Candidate-RP-advertisment in 00:01:00
RP: 1.51.51.1
group prefixes:
224.0.0.0 / 4
Candidate-RP-advertisement period: 60
The following example shows information for a device that is not the BSR.
Syntax
show ip pim interface [ vrf vrf-name ]
show ip pim interface { ethernet slot/port-id | loopback loopback-number
| ve vlan ID } [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF.
ethernet slot/port-id
Specifies a physical interface. For devices without linecards, specify 0 for the slot.
loopback loopback-number
Specifies a loopback interface.
ve vlan ID
Specifies a virtual interface.
Modes
Privileged EXEC mode
Examples
The following example displays unfiltered show ip pim interface output.
device# show ip pim interface
-------------+---------------+----+-----+------------------------------+---+------
Interface |Local |Ver|Mode | Designated Router |TTL| DR
|Address | | |Address Port |Thr| Prio
-------------+---------------+---------------------------------------+---+------
Eth 2/30 55.1.1.1 v2 SM Itself 1 1
Ve30 30.1.1.1 v2 SM 30.1.1.20 Ve30 1 1
Lo 1 4.4.4.4 v2 SM Itself 1 1
Syntax
show ip pim mcache [ A.B.C.D | ecmp ipv4 address ]
Parameters
A.B.C.D
Specifies the multicast group or source IP address.
ecmpipv4 address
Specifies the PIM ECMP IPv4 information.
Modes
Privileged EXEC mode
Examples
The following example displays the output for show ip pim mcache.
SLX# sh ip pim mcache 239.1.1.1
IP Multicast Mcache Table
Entry Flags : sm - Sparse Mode, ssm - Source Specific Multicast
RPT - RPT Bit, SPT - SPT Bit, LSrc - Local Source
LRcv - Local Receiver, RegProbe - Register In Progress
RegSupp - Register Suppression Timer, Reg - Register Complete
needRte - Route Required for Src/RP, JDUp - Join Desire Upstream
MDT - Multicast Distribution Tree Join sent/received
Interface Flags: IM - Immediate, IH - Inherited, WA - Won Assert
MJ - Membership Join, MI - Membership Include, ME - Membership Exclude
BR - Blocked RPT, BA - Blocked Assert, BF - Blocked Filter
BI - Blocked IIF, UJ - Unintended Join oif
Total entries in mcache: 16
1 (3.3.3.3, 239.1.1.1) in Eth 0/47, Uptime 02:17:18
SSM=1, RPT=0 SPT=1 Reg=0 RegSupp=0 RegProbe=0 JDUp=0 LSrc=0 LRcv=0 MDT=1
upstream neighbor=15.1.1.200
AgeSltMsk: 0 KAT timer value: Infinity
num_oifs = 0
Flags (0x080281d4)
ssm=1 needRte=0
2 (5.5.5.5, 239.1.1.1) in NIL, Uptime 02:17:17
SSM=1, RPT=0 SPT=1 Reg=0 RegSupp=0 RegProbe=0 JDUp=1 LSrc=0 LRcv=0 MDT=1
No upstream neighbor because source 5.5.5.5 is itself
AgeSltMsk: 0 KAT timer value: Infinity
num_oifs = 1
Eth 0/47(02:17:17/202) Flags: IM
Flags (0x0c0285d0)
ssm=1 needRte=1
Syntax
show ip pim mdt
show ip pim mdt detail
show ip pim mdt group GROUP-IP-ADDRESS
Parameters
detail
Displays detailed output for each MDT.
group GROUP-IP-ADDRESS
Displays detailed output for one MDT.
Modes
Privileged EXEC mode
Examples
The following examples shows brief output of all MDTs.
SLX# show ip pim mdt
Local VTEP IP: 5.5.5.5
MDT Join Role: Primary
Total MDT entries: 4
Group Tunnel Id State
(d)-default
------------ --------- ---------
239.1.1.1(d) 32774 Up
239.1.1.103 32772 Up
239.1.1.110 32773 Up
239.1.1.200 32775 Up
The following examples shows detailed output for one PIM MDT given by Group address.
SLX# show ip pim mdt group 239.1.1.1
Group: 239.1.1.1(default)
Active VLANs: 100-102
Active BDs:
Remote VTEP IPs: 3.3.3.3, 4.4.4.4, 12.12.12.12
Tunnel Id: 32775 (0x7c208007)
Tunnel State: Up
Rx Path Info:
Source VTEP IP IIF NH IP
-------------- ---------- --------------
3.3.3.3 Eth 0/47 15.1.1.200
4.4.4.4 Eth 0/47 15.1.1.200
12.12.12.12 Eth 0/47 15.1.1.200
Tx Path Info:
OIF NH IP
---------- --------------
Eth 0/47 15.1.1.200
Syntax
show ip pim neighbor vrf{ mgmt-vrf | default-vrf |vrf-name }
show ip pim neighbor interface { ethernet slot/port-id | ve vlan ID }
[ vrf vrf-name ]
Parameters
vrf
Specifies a VRF.
mgmt-vrf
Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf-name
Specifies a VRF name.
interface
Specifies an interface.
ethernet slot/port
Specifies a physical interface.
ve vlan ID
Specifies a VE interface.
Modes
Privileged EXEC mode
Output
The command displays the following information.
Age sec The number of seconds since the device received the last hello message from the
neighbor.
UpTime sec The number of seconds the PIM neighbor has been up. This timer starts when the device
receives the first Hello messages from the neighbor.
VRF The VRF in which the interface is configured. This can be a VRF that the port was
assigned to or the default VRF of the device.
Priority The DR priority that is used in the DR election process. This can be a configured value or
the default value of 1.
Examples
The following example shows information about PIM neighbors.
device(config)# show ip pim neighbor
--------+--------+---------------+--------+---+---------+---------+-----+-----------
+-----------+----
Port |PhyPort |Neighbor |Holdtime|T |PropDelay|Override |Age |UpTime |
VRF |Prio
| | |sec |Bit|msec |msec |sec |
| |
--------+--------+---------------+--------+---+---------+---------+-----+-----------
+-----------+----
v2 e1/1 2.1.1.2 105 1 500 3000 0 00:44:10
default-vrf 1
v4 e1/2 4.1.1.2 105 1 500 3000 10 00:42:50
default-vrf 1
v5 e1/1 5.1.1.2 105 1 500 3000 0 00:44:00
default-vrf 1
v22 e1/1 22.1.1.1 105 1 500 3000 0 00:44:10
default-vrf 1
Total Number of Neighbors : 4
Syntax
show ip pim rp-candidate [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF.
Modes
Privileged EXEC mode
Usage Guidelines
When used without the vrf option, this command displays information for the default VRF.
Output
The basic show ip pim rp-candidate command displays the following information.
group prefixes The multicast groups for which the RP listed by the previous field is a
candidate RP.
Examples
The following example shows information for a candidate RP.
device# show ip pim rp-candidate
Next Candidate-RP-advertisement in 00:00:10
RP: 207.95.7.1
group prefixes:
224.0.0.0 / 4
Candidate-RP-advertisement period: 60
Syntax
show ip pim rp-hash rp-hash A.B.C.D [ vrf vrf-name ]
Parameters
A.B.C.D
Specifies the IP address of a PIM Sparse IP multicast group.
vrf vrf-name
Specifies a VRF.
Modes
Privileged EXEC mode
Output
The show ip pim rp-hash command displays the following information:
Examples
The following example shows RP information for a PIM Sparse group.
device# show ip pim rp-hash 239.255.162.1
RP: 207.95.7.1, v2
Info source: 207.95.7.1, via bootstrap
Syntax
show ip pim rp-map [ vrf vrf-name ]
Parameters
vrf vrf-name
Displays information for the specified VRF instance.
Modes
Privileged EXEC mode
Output
The show ip pim rp-map command displays the following information:
Examples
The following general example shows RP-to-group mapping.
device# show ip pim rp-map
Number of group-to-RP mappings: 6
Group address RP address
-------------------------------
1 239.255.163.1 99.99.99.5
2 239.255.163.2 99.99.99.5
3 239.255.163.3 99.99.99.5
4 239.255.162.1 99.99.99.5
5 239.255.162.2 43.43.43.1
6 239.255.162.3 99.99.99.5
Syntax
show ip pim rp-set [ vrf vrf-name ]
Parameters
vrf vrf-name
Displays information for the specified VRF instance.
Modes
Privileged EXEC mode
Output
The basic show ip pim rp-set command displays the following information:
Examples
The following example shows the RP set list for the device elected as BSR.
device# show ip pim rp-set
Static RP
---------
Static RP count: 2
1.51.51.4
1.51.51.5
Number of group prefixes Learnt from BSR: 1
Group prefix = 224.0.0.0/4 # RPs: 2
The following example shows the RP set list for devices that are not elected as BSR.
device# show ip pim rp-set
Static RP
---------
Static RP count: 2
1.51.51.4
1.51.51.5
Number of group prefixes Learnt from BSR: 1
Group prefix = 224.0.0.0/4 # RPs expected: 2
# RPs received: 2
RP 1: 1.51.51.1 priority=0 age=60 holdtime=150
RP 2: 1.51.51.3 priority=0 age=30 holdtime=150
Syntax
show ip pim rpf A.B.C.D [ A.B.C.D ] [ vrf vrf-name ]
Parameters
A.B.C.D
Specifies one or two source addresses for reverse-path forwarding (RPF) check.
vrf vrf-name
Displays information for the specified VRF instance.
Modes
Privileged EXEC mode
Examples
This example shows best reverse path to the specified source:
device# show ip pim vrf eng rpf 130.50.11.10
Source 130.50.11.10 directly connected on e1/1
Syntax
show ip pim traffic [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies information for a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
PIM control packet statistics for interfaces that are configured for standard PIM are listed first by the
display.
Output
The show ip pim traffic command displays the following information:
Note: Unlike PIM Dense, PIM Sparse uses the same messages for Joins and
Prunes.
Examples
This example shows PIM join and prune traffic statistics for received and sent packets:
device# show ip pim traffic
Port |HELLO |JOIN |PRUNE |ASSERT |GRAFT/REGISTER |REGISTER-STOP |BSR-MSGS |RPC-
MSGS
|Rx |Rx |Rx |Rx |Rx |Rx |Rx |
Rx
------------+---------+---------+---------+---------+---------+---------+---------
+---------+
Ve10 54 0 0 0 0 0 0
0
Lo 1 0 0 0 0 0 0 0
0
show ip route
Displays IP route information for IPv4 interfaces.
Syntax
show ip route [ vrf vrf-name ]
show ip route A.B.C.D [ vrf vrf-name ]
show ip route A.B.C.D/M [ longer ] [ vrf vrf-name ]
show ip route all [ vrf vrf-name ]
show ip route bgp [ vrf vrf-name ]
show ip route brief [ vrf vrf-name ]
show ip route connected [ vrf vrf-name ]
show ip route import [ src-vrf-name ] [ vrf vrf-name ]
show ip route isis
show ip route nexthop [ nexthopID [ ref-routes ] ] [ vrf vrf-name ]
show ip route ospf [ vrf vrf-name ]
show ip route[ slot line-card-number ]
show ip route static [ vrf vrf-name ]
show ip route summary [ vrf vrf-name ]
show ip route system-summary
Parameters
vrf vrf-name
Specifies routes for a selected VRF instance.
A.B.C.D/M
Specifies the IPv4 address and optional mask.
longer
Specifies routes that match the specified prefix.
all
Specifies information for all configured IPv4 routes.
bgp
Specifies BGP route information.
brief
Specifies the display of summary route information.
vrf vrf-name
Specifies a VRF instance.
connected
Specifies directly connected routes, such as local Layer 3 interfaces.
import
Specifies imported IPv4 routes.
src-vrf-name
Specifies a VRF instance from which routes are leaked.
isis
Specifies routes learned from the Intermediate System to Intermediate System (IS-IS) protocol.
nexthop
Specifies the configured next hop.
nexthopID
Valid values range from 0 through 4294967294.
ref-routes
Specifies all routes that point to the specified next-hop ID .
ospf
Specifies routes learned from the Open Shortest Path First (OSPF) protocol.
slot line-card-number
Specifies routes with the provided line card number.
static
Specifies configured static routes.
summary
Specifies summary information for all routes.
system-summary
Specifies a system-level routing summary.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
If leaked subnet routes are present, that information displays in the output.
To view the status of management routes, use the show ip route vrf command and enter mgmt-
vrf as follows. You must enter the name of the management VRF manually. Example output is shown
below.
device# show ip route vrf mgmt-vrf
IP Routing Table for VRF "mgmt-vrf"
Total number of IP routes: 3
'*' denotes best ucast next-hop
'[x/y]' denotes [preference/metric]
0.0.0.0/0
*via 10.25.96.1, mgmt 1, [1/1], 8d15h, static, tag 0
10.25.96.0/22, attached
*via DIRECT, mgmt 1, [0/0], 8d15h, direct, tag 0
10.25.96.38/32, attached
*via DIRECT, mgmt 1, [0/0], 8d15h, local, tag 0
Examples
The following example displays output for the system-summary option.
device# show ip route system-summary
System Route Count: 3 Max routes: 4096 (Route limit not exceeded)
System Nexthop Count: 2 Max nexthops: 1024 (Nexthop limit not exceeded)
VRF-Name: default-vrf
Route count: 0 Max routes: Not Set (Route limit not exceeded)
0 connected, 0 static, 0 RIP, 0 OSPF, 0 BGP, 0 ISIS, 0 unnumbered
VRF-Name: mgmt-vrf
Route count: 3 Max routes: Not Set (Route limit not exceeded)
1 connected, 1 static, 0 RIP, 0 OSPF, 0 BGP, 0 ISIS, 0 unnumbered
Syntax
show ip source guard binding entries { interface interface-num | all }
Parameters
interface interface-num
Specifies the interface for which you want to display IP Source Guard binding entries.
all
Specifies that you want to display all IP Source Guard binding entries.
Modes
Privileged EXEC mode
Syntax
show ip subnet-rate-limit stats
Modes
Control plane configuration mode
Examples
The following example shows packets per second and bytes per second for IPv4 and IPv6 subnet traps.
device# configure terminal
device(config)# control-plane
device(config-control-plane)# show ip subnet-rate-limit stats
Syntax
show ipv6 bgp
show ipv6 bgp ipv6-addr [ /prefix ]
show ipv6 bgp ipv6-addr [ /prefix ] [ longer-prefixes ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation, with optional mask.
/prefix
IPv6 mask length in CIDR notation.
longer-prefixes
Filters on prefixes equal to or greater than that specified by prefix.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays sample output from the show ipv6 bgp command.
Syntax
show ipv6 bgp attribute-entries [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
The route-attribute entries table lists the sets of BGP4+ attributes that are stored in device memory.
Each set of attributes is unique and can be associated with one or more routes. In fact, the device
typically has fewer attribute entries than routes. Use this command to view BGP4+ route-attribute
entries that are stored in device memory.
Examples
This example show sample output for the show ipv6 bgp attribute-entries command.
Syntax
show ipv6 bgp dampened-paths [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 bgp dampened-paths
command.
device# show ipv6 bgp dampened-paths
Syntax
show ipv6 bgp filtered-routes [ detail ] [ ipv6-addr { / mask } [ longer-
prefixes ] ] | as-path-access-list name | prefix-list name ] [ vrf
vrf-name ]
Parameters
detail
Optionally displays detailed route information.
ipv6-addr
IPv6 address of the destination network in dotted-decimal notation.
mask
IPv6 mask of the destination network in CIDR notation.
longer-prefixes
Specifies all statistics for routes that match the specified route, or that have a longer prefix than
the specified route.
as-path-access-list name
Specifies an AS-path ACL. The name must be between 1 and 32 ASCII characters in length.
prefix-list name
Specifies an IP prefix list. The name must be between 1 and 32 ASCII characters in length.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays BGP4+ filtered routes.
Syntax
show ipv6 bgp flap-statistics
show ipv6 bgp flap-statistics ipv6-addr { / mask } [ longer-prefixes
[ vrf vrf-name ] | vrf vrf-name ]
show ipv6 bgp flap-statistics neighbor ipv6-addr [ vrf vrf-name ]
show ipv6 bgp flap-statistics regular-expression name [ vrf vrf-name ]
show ipv6 bgp flap-statistics vrf vrf-name
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
mask
IPv6 mask of a specified route in CIDR notation.
longer-prefixes
Displays statistics for routes that match the specified route or have a longer prefix than the
specified route.
vrf vrf-name
Specifies a VRF instance.
neighbor
Displays flap statistics only for routes learned from the specified neighbor.
ip-addr
IPv6 address of the neighbor.
regular-expression
Specifies a regular expression in the display output on which to filter.
name
Name of an AS-path filter or regular expression.
Modes
Privileged EXEC mode
Examples
This example displays flap statistics for a neighbor.
Syntax
show ipv6 bgp neighbors [ ipv6-addr ]
show ipv6 bgp neighbors last-packet-with-error [ vrf vrf-name ]
show ipv6 bgp neighbors routes-summary [ vrf vrf-name ]
show ipv6 bgp neighbors vrf vrf-name
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
last-packet-with-error
Displays the last packet with an error.
route-summary
Displays routes received, routes accepted, number of routes advertised by peer, and so on.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to view configuration information and statistics for BGP4+ neighbors of the device.
Output shows all configured parameters for the neighbors. Only the parameters whose values differ
from defaults are shown.
Examples
This example shows typical output from the command.
device# show ipv6 bgp neighbors
Syntax
show ipv6 bgp neighbors ipv6-addr advertised-routes [ detail | / mask-
bits ] [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
detail
Displays details of advertised routes.
mask-bits
Number of mask bits in CIDR notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays the details of advertised routes.
device# show ipv6 bgp neighbors 123::3 advertised-routes
Syntax
show ipv6 bgp neighbors ipv6-addr flap-statistics [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Syntax
show ipv6 bgp neighbors ipv6-addr last-packet-with-error [ decode ] [ vrf
vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
decode
Decodes last packet that contained an error from any of a device's neighbors.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example shows sample output from the show ipv6 bgp neighbors last-packet-with-
error command when no packet from a specified neighbor contained an error.
device# show ipv6 bgp neighbors 123::3 last-packet-with-error
BGP Header
Marker: 0xffffffff 0xffffffff 0xffffffff 0xffffffff
Message Length: (0x002d) 45
Message Type: (0x01) OPEN
OPEN Message
Version: (0x04) 4
AS Number: (0x014b) 331
Hold Time: (0x00b4) 180
BGP Identifier: (0x09090909) 9.9.9.9
Optional Parameter length: (0x10) 16
Syntax
show ipv6 bgp neighbors ipv6-addr received
show ipv6 bgp neighbors ipv6-addr received detail [ vrf vrf-name ]
show ipv6 bgp neighbors ipv6-addr received prefix-filter [ vrf vrf-name ]
show ipv6 bgp neighbors ipv6-addr vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
detail
Displays detailed information for ORFs received from BGP4+ neighbors of the device.
vrf vrf-name
Specifies a VRF instance.
prefix-filter
Displays the results for ORFs that are prefix-based.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 bgp neighbors received
command when the prefix-filter keyword is used.
Syntax
show ipv6 bgp neighbors ipv6-addr received-routes [ detail ] [ vrf vrf-
name ]
Parameters
ipv6-addr
IPv4 address of a neighbor in dotted-decimal notation.
detail
Displays detailed route information.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays the .
device# show ipv6 bgp neighbors 160:160:160::10 received-routes
Syntax
show ipv6 bgp neighbors ipv6-addr rib-out-routes ipv6-addr mask [ vrf
vrf-name ]
show ipv6 bgp neighbors ipv6-addr rib-out-routes detail ipv6-addr mask
[ vrf vrf-name ]
show ipv6 bgp neighbors ipv6-addr rib-out-routes detail [ vrf vrf-name ]
show ipv6 bgp neighbors ipv6-addr rib-out-routes [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
detail
Displays detailed RIB route information.
Modes
Privileged EXEC mode
Examples
This example shows sample output from the show ipv6 bgp neighbors rib-out-routes
command.
device# show ipv6 bgp neighbors 123::3 rib-out-routes
Syntax
show ipv6 bgp neighbors ipv6-addr routes [ vrf vrf-name ]
show ipv6 bgp neighbors ipv6-addr routes [ best | not-installed-best |
unreachable [ vrf vrf-name ] ]
show ipv6 bgp neighbors ipv6-addr routes detail [ best | not-installed-
best | unreachable [ vrf vrf-name ] ]
show ipv6 bgp neighbors ipv6-addr routes detail [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a neighbor in dotted-decimal notation.
best
Displays routes received from the neighbor that are the best BGP4+ routes to their destination.
not-installed-best
Displays routes received from the neighbor that are the best BGP4+ routes to their destination
but were not installed in the route table because the device received better routes from other
sources.
unreachable
Displays routes that are unreachable because the device does not have a valid OSPF or static
route to the next hop.
vrf vrf-name
Specifies a VRF instance.
detail
Displays detailed information for the specified route types.
Modes
Privileged EXEC mode
Examples
This example shows sample output from the show ipv6 bgp neighbors routes command
when the best keyword is used.
Syntax
show ipv6 bgp neighbors ipv6-addr routes-summary [ vrf vrf-name ]
Parameters
ipv6-addr
IPv6 address of a specified route in dotted-decimal notation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Output
The show ipv6 bgp neighbors routes-summary command displays the following
information.
Routes Selected The number of routes that the device selected as the best routes to their
as BEST Routes destinations.
BEST Routes not The number of routes received from the neighbor that are the best BGP4+ routes
Installed in IPv6 to their destinations, but were nonetheless not installed in the IPv6 route table
Forwarding Table because the device received better routes from other sources (such as OSPFv3, or
static IPv6 routes).
Unreachable The number of routes received from the neighbor that are unreachable because
Routes the device does not have a valid OSPFv3, or static IPv6 route to the next hop.
History Routes The number of routes that are down but are being retained for route flap
dampening purposes.
NLRIs Received in The number of routes received in Network Layer Reachability (NLRI) format in
Update Message UPDATE messages:
• Withdraws - The number of withdrawn routes the device has received.
• Replacements - The number of replacement routes the device has received.
NLRIs Discarded Indicates the number of times the device discarded an NLRI for the neighbor due
due to to the following reasons:
• Maximum Prefix Limit - The device’s configured maximum prefix amount had
been reached.
• AS Loop - An AS loop occurred. An AS loop occurs when the BGP4+ AS-path
attribute contains the local AS number.
• Invalid Nexthop Address - The next hop value was not acceptable.
• Duplicated Originator_ID - The originator ID was the same as the local router
ID.
• Cluster_ID - The cluster list contained the local cluster ID, or contained the local
router ID (see above) if the cluster ID is not configured.
Routes Advertised The number of routes the device has advertised to this neighbor:
• To be Sent - The number of routes the device has queued to send to this
neighbor.
• To be Withdrawn - The number of NLRIs for withdrawing routes the device has
queued up to send to this neighbor in UPDATE messages.
NLRIs Sent in The number of NLRIs for new routes the device has sent to this neighbor in
Update Message UPDATE messages:
• Withdraws - The number of routes the device has sent to the neighbor to
withdraw.
Peer Out of Statistics for the times the device has run out of BGP4+ memory for the neighbor
Memory Count for during the current BGP4+ session:
• Receiving Update Messages - The number of times UPDATE messages were
discarded because there was no memory for attribute entries.
• Accepting Routes(NLRI) - The number of NLRIs discarded because there was
no memory for NLRI entries. This count is not included in the Receiving Update
Messages count.
• Attributes - The number of times there was no memory for BGP4+ attribute
entries.
• Outbound Routes (RIB-out) - The number of times there was no memory to
place a "best" route into the neighbor's route information base (Adj-RIB-Out)
for routes to be advertised.
• Outbound Routes Holder - For debugging purposes only.
Examples
This example shows sample output from the show ipv6 bgp neighbors routes-summary
command.
device# show ipv6 bgp neighbors routes-summary
Syntax
show ipv6 bgp peer-group peer-group-name [ vrf vrf-name ]
Parameters
peer-group-name
Specifies a peer group name.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Only the parameters that have values different from their defaults are listed.
Examples
This example shows sample output from the show ipv6 bgp peer-group command.
1 BGP peer-group is pg
Address family : IPV4 Unicast
activate
Address family : IPV6 Unicast
no activate
Members:
IP Address: 1.1.1.1, AS: 100
IP Address: 1::1, AS: 100
Syntax
show ipv6 bgp routes [ num | ipv6-address/prefix | age num | as-path-
access-list name | best | cidr-only | community-access-list name |
community-reg-expression expression | detail | local | neighbor ipv6-
addr | nexthop ipv6-addr | no-best | not-installed-best | prefix-list
string | regular-expression name | route-map name | summary |
unreachable ] [ vrf vrf-name ]
Parameters
num
Table entry at which the display starts.
ipv6-address/prefix
Table entry at which the display starts.
age
Displays BGP4+ route information that is filtered by age.
as-path-access-list name
Displays BGP4+ route information that is filtered by autonomous system (AS)-path access
control list (ACL). The name must be between 1 and 32 ASCII characters in length.
best
Displays BGP4+ route information that the device selected as best routes.
cidr-only
Displays BGP4+ routes whose network masks do not match their class network length.
community-access-list name
Displays BGP4+ route information for an AS-path community access list. The name must be
between 1 and 32 ASCII characters in length.
community-reg-expression expression
Displays BGP4+ route information for an ordered community-list regular expression.
detail
Displays BGP4+ detailed route information.
local
Displays BGP4+ route information about selected local routes.
neighbor ip-addr
Displays BGP4+ route information about selected BGP neighbors.
nexthop ip-addr
Displays BGP4+ route information about routes that are received from the specified next hop.
no-best
Displays BGP4+ route information that the device selected as not best routes.
not-installed-best
Displays BGP4+ route information about best routes that are not installed.
prefix-list string
Displays BGP4+ route information that is filtered by prefix list. The string must be between 1 and
32 ASCII characters in length.
regular-expression name
Displays BGP4+ route information about routes that are associated with the specified regular
expression.
route-map name
Displays BGP4+ route information about routes that use the specified route map.
summary
Displays BGP4+ summary route information.
unreachable
Displays BGP4+ route information about routes whose destinations are unreachable through any
of the BGP4+ paths in the BGP4+ route table.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example shows sample input from the show ipv6 bgp routes command.
This example shows sample input from the show ip bgp routes command when the summary
keyword is used.
Syntax
show ipv6 bgp routes community { num | internet | local-as | no-advertise
| no-export } [ vrf vrf-name ]
Parameters
community
Displays routes filtered by a variety of communities.
num
Specific community member.
internet
Displays routes for the Internet community.
local-as
Displays routes for a local sub-AS within the confederation.
no-advertise
Displays routes with this community that cannot be advertised to any other BGP4+ devices at all.
no-export
Displays routes for the community of sub-ASs within a confederation.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows output from the show ipv6 bgp routes community command
when the internet keyword is used.
Syntax
show ipv6 bgp routes [ detail ] large-community ADMIN:OPER1:OPER2 [ vrf
vrf-name ]
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP4+ routes with large-community attributes
matching the specified value. If you omit this keyword, brief information is displayed.
ADMIN
A four-octet namespace identifier for a BGP Large-Communities Global Administrator.
OPER1
A four-octet operator-defined value for BGP Large-Communities Local Data Part 1.
OPER2
A four-octet operator-defined value for BGP Large-Communities Local Data Part 2.
vrf vrf-name
Specifies a VRF instance.
Examples
The following is an example command.
device# show ipv6 bgp routes large-community 1:2:3
Syntax
show ipv6 bgp routes [ detail ] large-community access-list
large_community_ACL [ vrf vrf-name ]
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP4+ routes matching the specified large
community access list. If you omit this keyword, brief information is displayed.
large_community_ACL
Name of the large community defined in a standard or extended large community access list
vrf vrf-name
Specifies a VRF instance.
Examples
The following example displays brief information of all BGP4+ routes with large community attributes
that match the large community access-list, lcstdacl1.
device# show ipv6 bgp routes large-community access-list lcstdacl1
Syntax
show ipv6 bgp routes [ detail ] large-community reg-expression
regex_value
Modes
Privileged EXEC mode
Parameters
detail
Optionally displays detailed information for all BGP4+ routes with large-community attributes
matching the specified REGEX. If you omit this keyword, brief information is displayed.
regex_value
REGEX value.
Examples
The following example displays the BGP4+ routes that match the specified REGEX value.
device# show ipv6 bgp routes large-community reg-expression _456778*
Syntax
show ipv6 bgp summary [ vrf vrf-name ]
Parameters
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
This example displays summary BGP4+ information.
BGP4 Summary
Router ID: 10.10.10.10 Local AS Number: 2040
Confederation Identifier: not configured
Confederation Peers:
Maximum Number of IP ECMP Paths Supported for Load Sharing: 1
Number of Neighbors Configured: 1040, UP: 4
Number of Routes Installed: 3079574, Uses 483493118 bytes
Number of Routes Advertising to All Neighbors: 107925658 (17078048 entries), Uses
1297931648 bytes
Number of Attribute Entries Installed: 1296243, Uses 230731254 bytes
'+': Data in InQueue '>': Data in OutQueue '-': Clearing
'*': Update Policy 'c': Group change 'p': Group change Pending
'r': Restarting 's': Stale '^': Up before Restart '<': EOR waiting
'$': Learning-Phase (for Delayed Route Calculation)
'#': RIB-in Phase
Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend
1:2::3 100 CONN 0h 0m18s 0 0 0 1
The $ : Learning-Phase (for Delayed Route Calculation) notation denotes that the BGP peer with this
notation is learning bulk route updates. More than one peer can be in Learning-Phase. BGP BEST-Path
selection is delayed until all the peers complete Learning-Phase. A peer can be in Learning-Phase only if
BGP delayed route calculation feature is enabled and in specific scenarios described in the init-
route-calc-delay command.
The # : RIB-IN phase notation denotes that a peer is learning bulk route updates. When one or more
peer is in RIB-IN phase, BGP provides high preference for learning incoming route-updates and less
preference for advertising routes (to outbound peers). An incoming route-update can possibly cause a
BGP BEST-path change and eventually re-compute RIB-OUT for outbound peers. Slowing down RIB-
OUT until all peers complete learning route updates will improve BGP performance. This feature is
enabled by default and does not require additional configuration. Unlike BGP delayed route calculation,
BGP BEST-Path selection is not delayed in this Phase.
This example displays summary information about dynamically created BGP neighbors.
Neighbor Address AS# State Time Rt:Accepted Filtered Sent ToSend
*2000:1:1:1::2 100 ESTAB 0h4m28s 0 0 0 0
*fe80::629c:9fff:fede:f46
100 ESTAB 0h4m28s 0 0 0 0
Syntax
show ipv6 counters interface [ ethernet slot/plot | loopback loopback-
number | port-channel number | ve ve-number ]
Parameters
interface
Specifies an interface.
ethernet slot/plot
Specifies physical Ethernet interface and a valid slot and port on it.
loopback loopback-number
Specifies the loopback interface.
port-channel number
Specifies a port-channel.
ve ve-number
Specifies the virtual Ethernet (ve) number.
Modes
Privileged EXEC mode
Examples
The following is an example of the show ipv6 counters interface command output.
device# show ipv6 counters interface ethernet 1/1
Syntax
show ipv6 dhcp relay address interface [ ethernet slot/port | ve
interface number ]
Parameters
ethernet
Specifies the ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
ve
Specifies the Ve interface.
interface number
Specifies the Ve interface number.
Modes
Privileged EXEC mode
Examples
The following example displays IPv6 DHCP relay addresses configured per interface.
device# show ipv6 dhcp relay address interface ethernet 3/21
Syntax
show ipv6 dhcp relay statistics
Modes
Privileged EXEC mode
Usage Guidelines
The show ipv6 dhcp relay statistics command displays the following information about the
IP DHCP Relay function for IP DHCP Relay addresses configured on the device:
• Number of DHCP Error packets dropped.
• Number of DHCP SOLICIT, REQUEST, CONFIRM, RENEW, REBIND, RELEASE, DECLINE,
INFORMATION-REQUEST, RELAY-FORWARD, RELAY-REPLY packets received.
• Number of DHCP RELAY-FORWARD, REPLY packets sent.
Examples
The following example displays statistics for the device.
device# show ipv6 dhcp relay statistics
Packets dropped : 0
Error : 0
Packets received : 0
SOLICIT : 0
REQUEST : 0
CONFIRM : 0
RENEW : 0
REBIND : 0
RELEASE : 0
DECLINE : 0
INFORMATION-REQUEST : 0
RELAY-FORWARD : 0
RELAY-REPLY : 0
Packets sent : 0
RELAY-FORWARD : 0
REPLY : 0
Syntax
show ipv6 interface [ brief | ethernet slot/port | loopback loopback-
port-number | port-channel number | ve ve_id ]
Parameters
brief
Displays brief interface information.
ethernet
Specifies Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
loopback loopback-port-number
Specifies the loopback interface. The range is from 1 to 255.
port-channel number
Specifies a port-channel.
ve ve-id
Specifies the VE ID of a virtual Ethernet (VE) interface. The range is from 1 to 4096.
Modes
Privileged EXEC mode
Examples
The following example displays the output of the show ipv6 interface command with an
Ethernet interface specified.
device# show ipv6 interface ethernet 2/25
Ethernet 2/25 is up protocol is up
IPv6 Address: 2025:2525:aaaa::1/64 Primary Confirmed
IPv6 Address: 2500:ffee:1234::12/64 Secondary Confirmed
IPv6 Address: 2500:ffee:1234::14/64 Secondary Confirmed
IPv6 Address: 2500:ffee:1234::16/64 Secondary Confirmed
IPv6 Address: fe80::748e:f8ff:fe09:e10d/128 Link-local Confirmed
IPv6 multicast groups locally joined:
ff02::1
ff02::2 ff02::1:ff00:1 ff02::1:ff00:12
ff02::1:ff00:14 ff02::1:ff00:16 ff02::1:ff09:e10d
show ipv6 nd
Displays the router advertisement information.
Syntax
show ipv6 nd interface [ ethernet slot/plot | prefix | ve ve-number |
vrf vrf-name ]
Parameters
interface
Specifies an interface.
ethernet slot/plot
Specifies physical Ethernet interface and a valid slot and port on it.
prefix
Displays prefix information.
ve ve-number
Specifies the virtual Ethernet (ve) number.
vrf vrf-name
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following is an example of the show ipv6 nd command output.
device# show ipv6 nd interface ethenet 3/5
ICMPv6 ND Interfaces for VRF default-vrf
IPv6 address: 2ffe::1
Router-Advertisement active timers:
Last Router-Advertisement sent: 00:01:25
Next Router-Advertisement sent in: 00:07:06
Router-Advertisement parameters:
Periodic interval: 200 to 600 seconds
Send 'Managed Address Configuration' flag: false
Send 'Other Stateful Configuration' flag: false
Send 'Current Hop Limit' field: 64
Send 'MTU' option value: 1500
Send 'Router Lifetime' field: 1800 secs
Send 'Reachable Time' field: 0 ms
Send 'Retrans Timer' field: 0 ms
Suppress RA: false
Suppress MTU in RA: false
Suppress All RA: false
Neighbor-Solicitation parameters:
NS retransmit interval: 1 secs
DAD Attempts: 2
Syntax
show ipv6 nd suppression-cache [ summary ]
show ipv6 nd suppression-cache bridge-domain bridge-domain-id
show ipv6 nd suppression-cache vlan vlan-id
Parameters
summary
Specifies summary format.
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Output
The show ipv6 nd suppression-cache command displays the following information:
Examples
The following example displays the results of the basic form of this command.
device# show ipv6 nd suppression-cache
Flags: L - Locally Learnt Adjacency
R - Remote Learnt Adjacency
RS - Remote Static Adjacency
Number of Locally Learnt Adjacency: 0
Number of Remotely Learnt Adjacency: 810
Syntax
show ipv6 nd suppression-statistics
show ipv6 nd suppression-statistics bridge-domain bridge-domain-id
show ipv6 nd suppression-statistics vlan vlan-id
Parameters
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
vlan vlan-id
Specifies a VLAN interface.
Modes
Privileged EXEC mode
Output
The show ipv6 nd suppression-statistics command displays the following information:
Examples
The following example displays the results of the basic form of this command.
device# show ipv6 nd suppression-statistics
Vlan/Bd Forwarded Suppressed Remote-arp Proxy
---------------------------------------------------------
110 (V) 0 117 0
254 (V) 3 10 0
Syntax
show ipv6 nd suppression-status
show ipv6 nd suppression-status bridge-domain bridge-domain-id
show ipv6 nd suppression-status vlan vlan-id
Parameters
bridge-domain bridge-domain-id
Specifies one or more bridge domain IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
vlan vlan-id
Specifies one or more VLAN IDs. To specify a range of IDs, insert a hyphen between the
beginning and ending integers (for example, 5-16). To specify individual IDs and ranges of IDs,
separate them with commas (for example: 1,5-7,55). Do not insert spaces after commas. You can
enter a maximum of 253 characters.
Modes
Privileged EXEC mode
Output
The show ipv6 nd suppression-status command displays the following information:
Examples
The following example displays the results of the basic form of this command.
device# show ipv6 nd suppression-status
Vlan/Bd Configuration Evpn-Register Operation
----------------------------------------------------------
4003 (V) Enabled Yes Active
Syntax
show ipv6 neighbor
show ipv6 neighbor { dynamic | static } [ summary ] [ vrf vrf-name ]
show ipv6 neighbor ethernet slot / port [ vrf vrf-name ]
show ipv6 neighbor { ipv6-address | ve vlan_id | summary } [ vrf vrf-
name ]
show ipv6 neighbor vrf vrf-name
Parameters
ipv6-address
Restricts the display to the entries for the specified IPv6 address. Specify this parameter in
hexadecimal using 16-bit values between colons as documented in RFC 2373.
ethernet slot/port
Restricts the display to the entries for the specified Ethernet interface.
static
Displays the static IPv6 neighbors.
dynamic
Displays the dynamic IPv6 neighbors .
summary
Displays the summary of IPv6 neighbors.
ve ve-num
Restricts the display to the entries for the specified VE interface. The range is from 1 to 4096.
vrf vrf-name
Displays the IPv6 neighbor information for the specified Virtual Routing/Forwarding (VRF)
instance.
Modes
Privileged EXEC mode
Output
The show ipv6 neighbor command displays the following information:
Age In hh:mm:ss format, displays the time since the most recent renewal
of a dynamic entry. For a static entry, displays "Never".
Type Displays the neighbor discovery (ND) type. Supported values:
• "Dynamic"
• "BGP-EVPN": Entries learned through the BGP-EVPN control
plane
• "BGP-Sticky": Entries learned through the BGP-EVPN control
plane—with the "sticky" attribute (static or MY-IP at the
originator).
• "LeakNd": A neighbor entry leaked from another VRF.
• "PreNd": ND triggered by other than the data traffic, for example,
by the static route.
• "Static"
Examples
The following example illustrates the output of the show ipv6 neighbor command without
keywords.
device# show ipv6 neighbor
Entries in VRF default-vrf : 37
Address Mac-address L3 Interface L2 Interface Age Type
----------------------------------------------------------------------------
1:4:67::4 609c.9fde.0f15 Ve 1467 Tu 61441 (4.4.4.4) 00:00:00 LeakNd
1:5:67::5 609c.9fde.1215 Ve 1567 Tu 61442 (5.5.5.5) Never Bgp-Sticky
2:7::2 609c.9fde.0015 Ve 2703 Po 27 Never Dynamic
3:7::2 609c.9fde.0d1c Eth 0/2 Eth 0/2 Never Dynamic
37::10 0010.9400.0002 Ve 37 Eth 0/42.37 Never Dynamic
37::100 0000.0001.0002 Ve 37 UnResolved Never Static
37::101 UnResolved Ve 37 UnResolved Never PreNd
The following example displays the output of the show ipv6 neighbor summary option.
device# show ipv6 neighbor summary
Static Entries : 1
Dynamic Entries : 5
Leaked Entries : 2
Pre-arp Entries : 1
Evpn Entries : 0
Evpn Sticky Entries : 28
Total Entries : 37
Syntax
show ipv6 ospf [ vrf name ]
Parameters
vrf name
Specifies the name of the VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example shows sample output from the command.
device# show ipv6 ospf
=====================================================================
OSPFv3 Global Information
=====================================================================
router-id : 127.158.208.0
admin-state : DISABLE
version : 3
area-bdr-rtr-state : FALSE
as-bdr-rtr-state : FALSE
as-scope-lsa-count : 0
lsa-checksum : 0
originate-new-lsas : 0
rx-new-lsas : 0
ext-lsa-count : 0
Helper mode : enabled
Graceful restart time : Enabled with restart interval: 120,
Syntax
show ipv6 ospf area [ A.B.C.D ] [ decimal ] [ vrf vrfname ]
Parameters
A.B.C.D
Area address in dotted decimal format.
decimal
Area address in decimal format. Valid values range from 0 to 2147483647.
vrf vrf name
Specifies a non-default VRF instance.
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 ospf area command when no
arguments or keywords are used.
Syntax
show ipv6 ospf database [ advrtr A.B.C.D | extensive | grace | link-id
decimal | prefix ipv6-addr ] [ vrf vrfname ]
show ipv6 ospf database [ as-external | inter-prefix | inter-router |
intra-prefix | link [ decimal ] | network | router | type-7 ]
[ advrtr A.B.C.D | link-id decimal ] [ vrf vrfname ]
show ipv6 ospf database scope { area { A.B.C.D | decimal } | as | link }
[ vrf vrfname ]
show ipv6 ospf database summary [ all-vrfs | vrf vrfname ]
Parameters
advrtr A.B.C.D
Displays LSAs by Advertising Router Id in dotted decimal format.
extensive
Displays detailed lists of LSA information.
grace
Displays grace LSA information.
link-id decimal
Link-state ID that differentiates LSAs. Valid values range from 1 through 4294967295.
prefix
Display LSAs that contain a prefix.
ipv6-addr
Specifies an IPv6 address.
vrf vrf name
Specifies a non-default VRF instance.
as-external
Displays information about external LSAs.
inter-prefix
Displays information about inter area prefix LSAs.
inter-router
Displays information about inter area router LSAs.
intra-prefix
Displays information about intra area prefix LSAs.
link decimal
Modes
Privileged EXEC mode
Examples
The following is sample output from the show ipv6 ospf database as-external command
using the link-id keyword:
The following is sample output from the show ipv6 ospf database inter-prefix command
using the link-id keyword:
The following is sample output from the show ipv6 ospf database network command:
The following is sample output from the show ipv6 ospf database router command:
The following is sample output from the show ipv6 ospf database type-7 command:
The following is sample output from the show ipv6 ospf database scope command using the
area keyword:
Syntax
show ipv6 ospf interface brief [ all-vrfs | vrf vrf-name ]
show ipv6 ospf interface [ ethernet slot/port | loopback number | port-
channel number | ve vlan_id ]
show ipv6 ospf interface [ vrf vrf-name ]
Parameters
brief
Displays summary information.
all-vrfs
Displays the information for all VRF instances.
vrf vrf-name
Specifies the name of the VRF instance. If this option is not used, details for the default VRF are
shown in the output.
ethernet slot/port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback port number. Valid values range from 1 through 255.
port-channel number
Specifies a port-channel.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following is sample output from the show ipv6 ospf interface command when no
arguments or keywords are used.
The following is sample output from the show ipv6 ospf interface command the brief
keyword is used.
Syntax
show ipv6 ospf memory [ vrf vrfname ]
Parameters
vrf vrfname
Displays the information for the specified VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following is sample output from the show ipv6 ospf memory vrf vrf-name command:
Syntax
show ipv6 ospf neighbor [ all-vrfs | vrf vrf-name ]
show ipv6 ospf neighbor detail [ vrf vrf-name ]
show ipv6 ospf neighbor interface [ ethernet slot/port | loopback number
| port-channel number | ve vlan_id ]
show ipv6 ospf neighbor router-id A.B.C.D [ vrf vrf-name ]
Parameters
all-vrfs
Specifies all VRF instances.
vrf vrf-name
Specifies a non-default VRF instance.
detail
Displays detailed neighbor information.
interface
Displays OSPFv3 interface information.
ethernet slot/port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback port number. Valid values range from 1 through 255.
port-channel number
Specifies a port-channel.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
router-id A.B.C.D
Specifies neighbor information for the specified router ID (in dotted decimal format).
Modes
Privileged EXEC mode
Examples
The following example shows sample output from the show ipv6 ospf neighbor command when
no arguments or keywords are used.
device# show ipv6 ospf neighbor
Total number of neighbors in all states: 1
Number of neighbors in state Full : 1
The following example shows sample output from the show ipv6 ospf neighbor detail
command when no arguments or keywords are used.
device# show ipv6 ospf neighbor detail
Total number of neighbors in all states: 1
Number of neighbors in state Full : 1
Syntax
show ipv6 ospf redistribute route A.B.C.D:M [ vrf vrf-name ]
show ipv6 ospf redistribute route [ vrf vrf-name ]
Parameters
A.B.C.D:M
Specifies an IPv6 address.
vrf vrfname
Specifies the name of a VRF instance.
Modes
Privileged EXEC mode
Examples
The following is sample output from the show ipv6 ospf redistribute route command
when no arguments or keywords are used:
Syntax
show ipv6 ospf routes A.B.C.D:M [ vrf vrfname ]
show ipv6 ospf routes [ vrf vrfname ]
Parameters
A.B.C.D:M
Specifies a destination IPv6 address.
vrf vrfname
Specifies a VRF instance.
Modes
Privileged EXEC mode
Examples
The following example displays OSPFv3-calculated routes.
Syntax
show ipv6 ospf spf { node | table | tree } [ area { A.B.C.D | decimal } ]
[ vrf vrfname ]
Parameters
node
Displays OSPFv3 node information.
table
Specifies a SPF table.
tree
Specifies a SPF tree.
area
Specifies an area.
A.B.C.D
Area address in dotted decimal format.
decimal
Area address in decimal format.
vrf vrfname
Specifies an non-default VRF instance.
Examples
The following example shows sample output from the show ipv6 ospf spf command when the
node keyword is used.
Syntax
show ipv6 ospf summary [ all-vrfs | all-vrfs total | vrf vrfname ]
Parameters
all-vrfs
Specifies all VRF instances. If this option is not used, details for the default VRF are shown in the
output.
vrf vrfname
Specifies a non-default VRF instance. If this option is not used, details for the default VRF are
shown in the output.
all-vrfs total
Displays the cumulative summary of OSPF information with the total numbers for all of the VRF
intances. If this option is not used, details for the default VRF are shown in the output. If this
option is not used, details for the default VRF are shown in the output.
Modes
Privileged EXEC mode
Examples
The following example shows sample default VRF output from the show ipv6 ospf summary
command when no arguments or keywords are used.
The following example shows sample output from the show ipv6 ospf summary all-vrfs
total command.
-----------------------------------------
IPv6 OSPF Summary Total
-----------------------------------------
Number of instances: 1024
Number of interfaces: 2048
Number of neighbors: 2048
Number of neighbors in FULL state: 2048
Number of LSAs: 76786
Number of Routes: 67570
device#
Syntax
show ipv6 ospf virtual-links brief [ vrf vrfname ]
show ipv6 ospf virtual-links [ vrf vrfname ]
Parameters
brief
Displays summary information.
vrf vrfname
Specifies a non-default VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following is sample output from the show ipv6 ospf virtual-links command when no
arguments or keywords are used:
Syntax
show ipv6 ospf virtual-neighbor brief [ vrf vrfname ]
show ipv6 ospf virtual-neighbor [ vrf vrfname ]
Parameters
brief
Displays summary information.
vrf vrfname
Specifies a nondefault VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
Examples
The following example shows sample output from the show ipv6 ospf virtual-neighbor
command when no arguments or keywords are used.
Syntax
show ipv6 prefix-list prefix-list-name
Parameters
prefix-list-name
Specifies an IPv6 prefix list name.
Modes
Privileged EXEC mode
Usage Guidelines
The prefix-list-name parameter restricts the display to the specified prefix list. Specify the name
of the prefix list that you want to display.
Output
The show ipv6 prefix-list command displays the following information:
Examples
The following example shows how to display IPv6 prefix lists.
device# show ipv6 prefix-lists
ipv6 prefix-list routesfor2001: 2 entries
seq 5 permit 2001::/16
seq 10 permit 2001:db8::/32
Syntax
show ipv6 route [ all | bgp | connected | import source-name | nexthop
nexthop-id | ospf | static | summary | system-summary ] vrf-name
show ipv6 route [ isis | slot line-card-number | static | system-summary
| vrf number ]
Parameters
all
Specifies all routes.
bgp
Specifies BGP routes.
connected
Displays the directly connected routes.
import source-name
Specifies import routes and the source VRF name
isis
Specifies routes learned from the Intermediate System to Intermediate System (IS-IS) protocol.
nexthop nexthop-id
Displays the route nexthop table.
ospf
Specifies OSPF routes.
slot line-card-number
Specifies the IPv6 route information on a slot for the specified line card number.
static
Specifies static IPv6 routes.
summary
Displays the route summary.
system-summary
Displays the system-level summary for IPv6 routes.
vrf-name
The name of the VRF context.
vrf number
Specifies a VRF instance.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following is an example of the show ipv6 route command output.
SLX# show ipv6 route
IPv6 Routing Table for VRF "default-vrf"
Total number of IPv6 routes: 11
'*' denotes best ucast next-hop
'[x/y]' denotes [preference/metric]
1200:1201::/64, attached
*via ::, Eth 2/45, [0/0], 45m29s, direct, tag 0
1200:1201::1:1/128, attached
*via ::, Eth 2/45, [0/0], 45m29s, local, tag 0
1200:1202::/64, attached
*via ::, Ve 2, [0/0], 45m26s, direct, tag 0
1200:1202::1:1/128, attached
*via ::, Ve 2, [0/0], 45m26s, local, tag 0
2221::/32
*via 1200:1201::1:2, Eth 2/45, [100/10], 11m41s, static, tag 300
2222::/48
*via fe80::205:33ff:fee6:a531, Eth 2/45, [1/1], 43m44s, static, tag 0
2222::1/128
*via fe80::205:33ff:fee6:a531, Eth 2/45, [110/1], 0m7s, ospfv3, intra, tag 0
2223::/64
*via 1200:1202::1:2, Ve 2, [1/1], 3m45s, static, tag 0
2224::1/128
*via fe80::205:33ff:fee6:a501, Ve 2, [1/1], 43m41s, static, tag 0
fe80::/10, attached
*via ::, , [0/0], 6h30m, local, tag 0
ff00::/8, attached
*via ::, Null0, [0/0], 6h30m, local, tag 0
Syntax
show ipv6 static route [ ipv6prefix | vrf vrf-name ]
Parameters
ipv6prefix
The IPv6 prefix in the A:B::/length format.
vrf vrf-name
The name of the VRF context.
Modes
Privileged EXEC mode
Examples
The following example displays the IPv6 static route information for the default VRF.
Syntax
show ipv6 vrrp
show ipv6 vrrp VRID [ detail | summary ]
show ipv6 vrrp detail
show ipv6 vrrp summary [ vrf { vrf-name | all | default-vrf } ]
show ipv6 vrrp interface { ethernet slot/port | port-channel number | ve
vlan_id } [ detail | summary ]
Parameters
VRID
The virtual group ID about which to display information. The range is from 1 through 16.
detail
Displays all session information in detail, including session statistics.
summary
Displays session-information summaries.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance. For the default vrf, enter default-vrf.
all
Specifies all VRFs.
interface
Displays information for an interface that you specify.
ethernet slot port
Specifies a valid, physical Ethernet interface with a slot and port number.
port-channel number
Specifies a port-channel interface.
ve vlan_id
Specifies the VE VLAN number.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display information about IPv6 VRRP and VRRP-E sessions, either in summary or
full-detail format. You can also specify a particular virtual group ID, or an interface for which to display
VRRP output.
Note
IPv6 VRRP-E supports only the VE interface type.
To display information for IPv6 VRRP sessions using the default VRF, you can use the show ipv6
vrrp summary syntax (with no additional parameters).
To display information for the default or a named VRF, you can use the show ipv6 vrrp summary
vrf syntax with the vrf-name option.
To display information about all VRFs, use the show ipv6 vrrp summary vrf all syntax.
Examples
The following example displays information about all IPv6 VRRP sessions on the device.
device# show ipv6 vrrp
VRID 14
Interface: Ve 2018; Ifindex: 1207961570
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv6
Version: 3
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): fe80::1
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1000 milli sec (default: 1000 milli sec)
Preempt mode: ENABLE (default: ENABLE)
Hold time: 0 sec (default: 0 sec)
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Statistics:
Advertisements: Rx: 0, Tx: 35
Neighbor Advertisements: Tx: 1
VRID 15
Interface: Ve 2019; Ifindex: 1207961571
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv6
Version: 3
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): fe80::1
Configured Priority: unset (default: 100); Current Priority: 100
The following example displays IPv6 VRRP information in detail for a specific virtual group ID of 19,
including session statistics.
device# show ipv6 vrrp 19 detail
The following example displays summary information for IPv6 VRRP statistics on the default VRF. (This
command is equivalent to show ipv6 vrrp summary vrf default-vrf.)
device# show ipv6 vrrp summary
The following example displays summary information for IPv6 VRRP statistics on the VRF named red.
device# show ipv6 vrrp summary vrf red
The following example displays summary information for IPv6 VRRP statistics on all VRFs.
device# show ipv6 vrrp summary vrf all
The following example displays information for IPv6 VRRP-E tracked networks.
device# show ipv6 vrrp detail
VRID 2
Interface: Ve 100; Ifindex: 1207959652
Mode: VRRPE
Admin Status: Enabled
Description :
Address family: IPv6
Version: 3
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): 2001:2019:8192::1
Virtual MAC Address: 02e0.5225.1002
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1 sec (default: 1 sec)
Tracknetwork:
Network(s) Priority Status
========= ======== ==========
2001::/64 20 Up
Global Statistics:
==================
Checksum Error : 0
Version Error : 0
VRID Invalid : 0
Session Statistics:
===================
Advertisements : Rx: 0, Tx: 132
Neighbor Advertisements : Tx: 66
Session becoming master : 1
Advts with wrong interval : 0
Prio Zero pkts : Rx: 0, Tx: 0
Invalid Pkts Rvcd : 0
Bad Virtual-IP Pkts : 0
Invalid Authenticaton type : 0
Invalid TTL Value : 0
Invalid Packet Length : 0
VRRPE backup advt sent : 0
VRRPE backup advt recvd : 0
show isis
Displays general IS-IS information.
Syntax
show isis
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show isis command displays the following information:
IS-Type The intermediate system type. Possible types include the following:
• Level 1 only - The device routes traffic only within the area in which it
resides.
• Level 2 only - The device routes traffic between areas of a routing
domain.
• Level 1-2 - The device routes traffic within the area in which it resides
and between areas of a routing domain.
System ID The unique IS-IS router ID. Typically, the device’s base MAC address is used
as the system ID.
Manual area address(es) Area address(es) of the device.
Level-1-2 Database State The state of the Level 1-2 Database:
• On
• Off
Level-2 Auth-mode One of the following authentication modes set for Level-2 on the router:
• None
• md5
• cleartext
IS-IS Partial SPF This parameter can contain one of the following values:
Optimizations • Enabled
Timers: L1 or L2 SPF: These values are displayed individually for IS-IS levels 1 and 2.
max-wait The maximum time gap that occurs between running of SPF calculations. It
is the value configured as the spf-max-wait variable in thespf-interval
command.
Init-wait The initial time gap between an SPF event and the first running of SPF. This
value reflects the spf-initial-time variable that is configured using the spf-
interval command.
Second-wait The interval between the first running of SPF and the first recalculation of
the SPF tree. If this optional value is configured, it is doubled with each
recalculation of the SPF tree until the value is equal to the max-wait value
This value reflects the spf-second-wait variable that is configured using the
spf-interval command.
SPF run status. This field is not specifically labeled but is displayed directly under the SPF
timers. It can any of the three values shown below:
• SPF is running
• SPF will run in sec where the sec variable is a value in seconds until the
next time that SPF will be run.
• SPF is not scheduled
Timers: PSPF:
max-wait The maximum time gap that occurs between running of PSPF calculations.
It is the value configured as the max-wait value in thepartial-spf-
interval command.
Init-wait The initial time gap between the wait time after an LSP change until the
first PSPF calculation. This value reflects the initial-wait variable that is
configured using the partial-spf-interval command.
Second-wait The wait time between the first and second PSPF calculations. If this
optional value is configured, it is doubled with each PSPF recalculation until
the value is equal to the max-wait value
This value reflects the second-wait variable that is configured using the
partial-spf-interval command.
PSPF run status. This field is not specifically labeled but is displayed directly under the PSPF
timers. It can any of the three values shown below:
• PSPF is running
• PSPF will run in sec where the sec variable is a value in seconds until the
next time that PSPF will be run.
• PSPF is not scheduled
Timers: LSP:
max-lifetime The maximum number of seconds an unrefreshed LSP can remain in the
device’s LSP database.
The default value is 1000 sec.
refresh-interval The maximum number of seconds that a device waits between sending
updated LSPs to its IS-IS neighbors.
Examples
The following example displays sample output from the show isis command.
Syntax
show isis config
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The running-config does not list the default values. Only commands that change a setting or add
configuration information are displayed.
Examples
The following example displays sample output from the show isis config command.
device# show isis config
router isis
net 11.768e.f805.5812.00
address-family ipv4 unicast
!
Syntax
show isis counts
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show isis counts command displays the following information:
Level-2 Database The number of times the Level-2 state on the device changed from Waiting to On
Overload or from On to Waiting.
• The change from Waiting to On can occur when the device recovers from a
previous Level-2 LSP database overload and is again ready to receive new LSPs.
Our LSP Purged The number of times the device received an LSP that was originated by the device
itself and had age zero (aged out).
PDU Drop Count
CSNP Auth The number of CSNP Authentication failures recorded for Level-1 and Level-2. This
Failures counter will only be displayed if it has a value greater than zero.
PSNP Auth The number of PSNP Authentication failures recorded for Level-1 and Level-2. This
Failures counter appears only if it has a value greater than 0.
HELLO Auth The number of HELLO Authentication failures recorded for Level-1 and Level-2. This
Failures counter will only be displayed if it has a value greater than zero.
Adjacency not The number of PDUs dropped at both Level-1 and Level-2 because there is no valid
found adjacency on the interface where they were received. This counter will only be
displayed if it has a value greater than zero.
Adjacency Level The number of PDUs dropped at both Level-1 and Level-2 because the adjacency
Mismatch from which the PDU is received has a different level than the PDU level. This
counter will only be displayed if it has a value greater than zero.
IS Level The number of PDUs dropped at both Level-1 and Level-2 because the IS-IS router
Mismatch level mismatches with the PDU level received. This counter will only be displayed if
it has a value greater than zero.
Length Too Short The number of PDUs dropped at both Level-1 and Level-2 because the received
PDU length is less than the standard PDU header length. This counter will only be
displayed if it has a value greater than zero.
Length Too Long The number of PDUs dropped at both Level-1 and Level-2 because the received
PDU length is greater than the MTU of the link. This counter will only be displayed if
it has a value greater than zero.
Max Area Check The number of PDUs dropped at both Level-1 and Level-2 because the received
Failure PDU has a maximum area count different than what is configured on this IS-IS
router. This counter will only be displayed if it has a value greater than zero.
Zero Checksum The number of PDUs dropped at both Level-1 and Level-2 because the received
PDU has a zero checksum. This counter will only be displayed if it has a value
greater than zero.
Checksum The number of PDUs dropped at both Level-1 and Level-2 because the received
Mismatch PDU has a checksum different than the computed checksum on the received PDU.
This counter will only be displayed if it has a value greater than zero.
Invalid Length The number of PDUs dropped at both Level-1 and Level-2 because the received
PDU has a different length than what is advertised in the PDU header. This counter
will only be displayed if it has a value greater than zero.
Examples
The following example displays sample output from the show isis counts command.
Area Mismatch: 0
Max Area Mismatch: 0
System ID Length Mismatch: 0
LSP Sequence Number Skipped: 0
LSP Max Sequence Number Exceeded: 0
Level-1 Database Overload: 0
Level-2 Database Overload: 0
Our LSP Purged: 0
Syntax
show isis database lsp-id
show isis database detail [ level1 | level2 ]
show isis database level1
show isis database level2
show isis database summary
Parameters
lsp-id
Specifies a link-state packet (LSP) in HHHH.HHHH.HHHH.HH-HH format, for example,
3333.3333.3333.00-00, or by entering a name, for example, XMR.00-00.
detail
Specifies detailed information.
level1
Specifies Level 1 packets only.
level2
Specifies Level 2 packets only.
summary
Specifies summarized information.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show isis database command displays the following information:
Note: If the address has an asterisk ( * ) at the end, this indicates that the LSP is
locally originated.
Note: The IS that originates the LSP sets the timer for the LSP. As a result, LSPs do
not all have the same amount of time remaining when they enter the device’s LSP
database.
ATT A 4-bit value extracted from bits 4 - 7 in the Attach field of the LSP.
P The value in the Partition option field of the LSP. The field can have one of the
following values:
• 0 - The IS that sent the LSP does not support partition repair.
• 1 - The IS that sent the LSP supports partition repair.
OL The value in the LSP database overload field of the LSP. The field can have one of
the following values:
• 0 - The overload bit is off.
• 1 - The overload bit is on, indicating that the IS that sent the LSP is overloaded
and should not be used as a IS-IS transit router for that level.
NLPID The Network Layer Protocol Identifier (NLPID), which specifies the protocol the IS
that sent the LSP is using. Usually, this value is "CC(IP)".
IP address The IP address of the interface that sent the LSP. The device can use this address as
the next hop in routes to the addresses listed in the rows below.
Destination The rows of information below the IP address row are the destinations advertised by
addresses the LSP. The device can reach these destinations by using the IP address listed
above as the next hop.
Each destination entry contains the following information:
• Metric - The value of the default metric, which is the IS-IS cost of using the IP
address above as the next hop to reach this destination.
• Device type - The device type at the destination. The type can be one of the
following:
◦ End System - The device is an ES.
◦ IP-Internal - The device is an ES within the current area. The IP address and
subnet mask are listed.
◦ IS - The device is another IS. The NET (NSAP address) is listed.
Flooding to num Identifies the number of interfaces on which the specific LSP entry will be flooded
interface: and identifies the interfaces.
Acking to num Identifies the number of interfaces on which the specific LSP entry will be
interface: acknowledged and identifies the interfaces.
Examples
The following is sample output for the show isis database command when no argument or
keyword is used.
The following is sample output for the show isis database command when the detail keyword
is used.
Syntax
show isis hostname
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example displays sample output from the show isis hostname command.
Syntax
show isis interface
show isis interface brief
show isis interface ethernet slot/port
show isis interface loopback number
show isis interface port-channel number
show isis interface ve vlan_id
Parameters
brief
Specifies a brief summary of IP interface IS-IS interface information.
ethernet slot / port
Specifies an Ethernet slot and port.
loopback number
Specifies a loopback interface. Valid values range from 1 through 255.
port-channel number
Specifies a port-channel interface.
ve vlan_id
Specifies a virtual Ethernet (VE) interface. Valid values range from 1 through 4096.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show isis interface command displays the following information:
Circuit Mode The IS-IS type in use on the circuit. The mode can be one of the following:
• LEVEL-1
• LEVEL-2
• LEVEL-1-2
Circuit Type The type of IS-IS circuit running on the interface. The circuit type can be one
of the following:
• BCAST (broadcast).
• PTP (Point-to-Point)
Passive State The passive state determines whether the interface is allowed to form an IS-
IS adjacency with the IS at the other end of the circuit. The state can be one
of the following:
• FALSE - The passive option is disabled. The interface can form an
adjacency with the IS at the other end of the link.
• TRUE - The passive option is enabled. The interface cannot form an
adjacency, but can still advertise itself into the area.
Circuit Number The ID that the instance of IS-IS running on the interface applied to the
circuit between this interface and the interface at the other end of the link.
MTU The maximum length supported for IS-IS PDUs sent on this interface.
Level-1 Auth-mode One of the following authentication modes set for Level-1 on the router:
• None
• md5
• cleartext
Level-2 Auth-mode One of the following authentication modes set for Level-2 on the router:
• None
• md5
• cleartext
This parameter is not displayed for interfaces that are configured with a
Point-to-Point circuit type. This is because separate Level-2 Hello messages
are not sent on Point-to-Point interfaces. Consequently, "Hello Interval",
Control Messages Sent The number of IS-IS control PDUs sent on this interface.
Control Messages The number of IS-IS control PDUs received on this interface.
Received
Hello Padding: The Hello Padding configuration, which can be:
• Enabled
Examples
The following example displays information about IS-IS interfaces for a device.
Interface: Ve 301
Circuit State: UP Circuit Mode: Level 1-2
Circuit Type: BCAST Passive State: FALSE
Circuit Number: 2, MTU: 1500
Level-1 Auth-mode: NONE
Level-2 Auth-mode: NONE
Level-1 Metric: 10, Level-1 Priority: 64
Level-1 Hello Interval: 10, Level-1 Hello Multiplier: 3
Level-1 Designated IS: R1-02 Level-1 DIS Changes: 2
Level-2 Metric: 10, Level-2 Priority: 64
Level-2 Hello Interval: 10, Level-2 Hello Multiplier: 3
Level-2 Designated IS: R1-02 Level-2 DIS Changes: 2
Next IS-IS LAN Level-2 Hello in 11 seconds
Number of active Level-2 adjacencies: 0
Next IS-IS LAN Level-1 Hello in 1 seconds
Number of active Level-1 adjacencies: 0
Circuit State Changes: 1 Circuit Adjacencies State Changes: 0
Rejected Adjacencies: 0
Circuit Authentication L1 failures: 0
Circuit Authentication L2 failures: 0
Bad LSPs: 0
Control Messages Sent: 7577 Control Messages Received: 0
Hello Padding: Enabled
IP Enabled: TRUE
IP Addresses:
11.2.1.1/30
IPv6 Enabled: FALSE
MPLS TE Enabled: FALSE
BFD Enabled: FALSE
LDP-SYNC: Disabled, State:
Interface: Ve 302
Circuit State: UP Circuit Mode: Level 1-2
Circuit Type: BCAST Passive State: FALSE
The following example displays summarized information about IS-IS interfaces for a device.
Syntax
show isis neighbor [ detail ]
Parameters
detail
Specifies detailed information.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show isis neighbors command displays the following information:
Note: The device forms a separate adjacency for each IS-IS type. Thus, if the
device has both types of IS-IS adjacencies with the neighbor, the display
contains a separate row of information for each adjacency.
The show isis neighbors detail command displays the following information:
Note: The device forms a separate adjacency for each IS-IS type. Thus, if the
device has both types of IS-IS adjacencies with the neighbor, the display
contains a separate row of information for each adjacency.
Examples
The following example displays information about IS-IS neighbors.
Syntax
show isis routes [ ip-address subnet-mask | ip-address/prefix ]
Parameters
ip-address subnet-mask
Specifies an IP address and network mask.
ip-address/prefix
Specifies an IP address and prefix.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show isis routes command displays the following information:
Examples
The following is sample output for the show isis routes command when no argument or keyword
is used.
Syntax
show isis spf-log
show isis spf-log detail
show isis spf-log level-1 [detail ]
show isis spf-log level-2 [detail ]
Parameters
detail
Specifies detailed information.
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show isis spf-log command displays the following information:
Nodes The number of routers and pseudonodes (LANs) that make up the
topology calculated in this SPF run.
Count The number of events that triggered this SPF run. When a topology
change has occurred, multiple link-state packets (LSPs) are received in a
short time. Since a router waits about 5 seconds before running a full
SPF run, it can include all new information. This count includes the
number of events (such as receiving new LSPs) that occurred while the
router was waiting the 5 second interval before running full SPF.
Last Trigger LSP When a full SPF calculation is triggered by the arrival of a new LSP, the
router stores the LSP ID. The LSP ID can provide a clue about the source
Examples
The following is sample output for the show isis spf-log command.
The following is sample output for the show isis spf-log command when the detail keyword is
used.
The following is sample output for the show isis spf-log command when the level-1 keyword
is used.
Syntax
show isis traffic
Modes
Privileged EXEC mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show isis traffic command displays the following information:
Examples
The following is sample output for the show isis traffic command.
device# show isis traffic
Level-1 PSNP 0 0
Level-2 PSNP 0 0
Syntax
show selinux status
Modes
Privilege Execution Mode
Output
The following information is displayed:
Examples
The following example shows the use of this command to view the current SE Linux status.
SLX # show selinux status
SE Linux status: enabled
SE Linuxfs mount: /sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: mls
Current mode: permissive
Mode from config file: enforcing
Policy MLS status: enabled
Policy deny_unknown status: allowed
Examples
The following example shows the single NHID with Multiple tunnels for Aliasing scenario.
*** show system internal bgp evpn nhid ***
NHID Tunnel Encap ULabel Ref Installed Status Node ESI-Node
0x71100001 10.10.10.10 VXLAN 0x7c008003 TRUE TRUE Up 0x036edbd0 NA
0x71100002 30.30.30.30 VXLAN 0x7c008004 TRUE TRUE Up 0x036edce0 NA 0x71100003 10.10.10.10
VXLAN 0x7c008003 TRUE TRUE Up 0x036eddf0 0x036ed570 30.30.30.30 VXLAN 0x7c008004 TRUE
TRUE Up 0x036eddf0 0x036ed570 [ECMP]
show mac-address-table
Multiple tunnel entries can be present per MAC entry if the MAC is reachable via multiple tunnels.
Examples
The following example shows the multiple tunnel entries can be present per MAC entry if the MAC is
reachable via multiple tunnels.
sw# show mac-address-table
Type Code - CCL:Cluster Client Local MAC
CCR:Cluster Client Remote MAC
CR:Cluster Remote MAC
VlanId/BDId Mac-address Type State Ports/LIF/PW/T 30 (V) 0010.9400.0102 EVPN Active Tu
32771 (1.1.1.1) Tu 32772 (2.2.2.2)
30 (V) 0010.9400.0202 EVPN Active Tu 32771 (1.1.1.1)
30 (V) 0010.9400.0302 EVPN Active Tu 32771 (1.1.1.1)
Following table captures the difference between Simplified MCT and EVPN MH naming convention:
Examples
The following example shows the multiple tunnel entries can be present per ARP.
sw# show ip arp suppression-c
Flags: L - Locally Learnt Adjacency
R - Remote Learnt Adjacency
RS - Remote Static Adjacency
Number of Locally Learnt Adjacency : 0
Number of Remotely Learnt Adjacency: 2794
Vlan/Bd IP Mac Interface Age Flags
------------------------------------------------------------------------------------------
---------
0001 (B) 20.100.0.1 f46e.959f.2c27 Po 17.1801 Never R 0001 (B) 20.100.0.8 887e.25d3.180b
Tu 32771 (1.89.0.2) Never RS Tu 32775 (1.89.0.5)
Examples
The following example shows the multiple tunnel entries can be present per ND.
sw# show ipv6 nd suppression-c
Flags: L - Locally Learnt Adjacency
R - Remote Learnt Adjacency
RS - Remote Static Adjacency
Number of Locally Learnt Adjacency : 0
Number of Remotely Learnt Adjacency: 810
Vlan/Bd IP Mac Interface Age Flags
------------------------------------------------------------------------------------------
-------------------------------
0081 (B) 20:102::2 f46e.95a1.0406 Po 31.1901 Never R 0081 (B) 20:102::8 887e.25d3.180b Tu
32771 (1.89.0.2) Never RS Tu 32775 (1.89.0.5)
Syntax
show bgp evpn ethernet-segment { esi es-id }
Parameters
esi es-id
Use this option to query for ESI information for a particular ESI value.
Modes
EXEC mode
Examples
The following example displays the ethernet segment information for all interfaces on the multi-homed
client.
sw#show bgp evpn ethernet-segment
ESI : 00.112233445566778899
Interface : po4
Interface state : Up
Load balancing Mode : Active-Active
List of MH Nodes : 1.1.1.1 2.2.2.2
DF Vlans : 100 102 104 106 108 110
DF BD : 50 52 54 56 58 60
show lacp
Displays Link Aggregation Control Protocol (LACP) statistics.
Syntax
show lacp { counter [ port-channel ] | sys-id }
Parameters
counter
Displays LACP statistics for all port-channel interfaces.
port-channel
Displays counters for a specified port channel interface.
sys-id
Displays LACP statistics by system ID.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the LACP statistics for each port-channel interface for all port-channel
interfaces or a single port-channel interface, or by system ID.
Examples
The following example displays the local system ID:
device# show lacp sys-id
% System 8000,00-05-1e-76-1a-a6
show license
Displays license information.
Syntax
show license [ eula | id ]
Command Default
Displays the licenses installed on the device.
Parameters
eula
Specifies the EULA statement.
id
Specifies the license ID and information.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display general license information, the license ID, and the EULA text.
The EULA text can be displayed using the show license eula command.
Examples
The following example displays the EULA text.
The following example displays the SAU license when the EULA is accepted.
Syntax
show link-oam info
Modes
Privileged EXEC mode
Output
The show link-oam info command displays the following information:
Examples
The following example displays sample output from the show link-oam info command.
device#show link-oam info
Ethernet Link Status OAM Status Mode Local Stable Remote Stable
1/1 up up active satisfied satisfied
1/2 up up passive satisfied satisfied
1/3 up up active satisfied satisfied
1/4 up init passive unsatisfied unsatisfied
1/5 down down passive unsatisfied unsatisfied
1/6 down down passive unsatisfied unsatisfied
1/7 down down passive unsatisfied unsatisfied
Syntax
show link-oam info detail
Modes
Privileged EXEC mode
Output
The show link-oam info detail command displays the following information:
Examples
This example displays the detailed dump of Link OAM statistics for all ports:
device# show link-oam info detail
OAM information for Ethernet port: 2/1
+link-oam mode: active
+link status: up
+oam status: init
Local information
multiplexer action: forward
parse action: forward
stable: unsatisfied
state: activeSend
dying-gasp: false
critical-event: false
link-fault: false
Remote information
multiplexer action: forward
parse action: forward
stable: unsatisfied
dying-gasp: false
critical-event: false
link-fault: false
critical-event: false
link-fault: false
Remote information
multiplexer action: forward
parse action: forward
stable: unsatisfied
dying-gasp: false
critical-event: false
link-fault: false
Syntax
show link-oam statistics
Modes
Privileged EXEC mode
Output
The show link-oam statistics command displays the following information:
Examples
The following example displays sample output from the show link-oam statistics command.
device# show link-oam statistics
Ethernet Tx PDUs Rx PDUs
2/1 93 92
2/2 45 46
Syntax
show link-oam statistics detail
Modes
Privileged EXEC mode
Output
The show link-oam statistics detail command displays the following information:
Examples
This example displays the detailed dump of Link OAM statistics for all ports:
device# show link-oam statistics detail
OAM statistics for Ethernet port: 1/1
Tx statistics
information OAMPDUs: 587
loopback control OAMPDUs: 0
variable request OAMPDUs: 0
variable response OAMPDUs: 0
unique event notification OAMPDUs: 0
duplicate event notification OAMPDUs: 0
organization specific OAMPDUs: 0
link-fault records: 0
critical-event records: 0
dying-gasp records: 0
Rx statistics
information OAMPDUs: 442
loopback control OAMPDUs: 0
variable request OAMPDUs: 0
variable response OAMPDUs: 0
unique event notification OAMPDUs: 0
duplicate event notification OAMPDUs: 0
organization specific OAMPDUs: 0
unsupported OAMPDUs: 0
link-fault records: 0
critical-event records: 0
dying-gasp records: 0
discarded TLVs: 0
unrecognized TLVs: 0
OAM statistics for Ethernet port: 1/2
Tx statistics
information OAMPDUs: 440
loopback control OAMPDUs: 0
show lldp
Displays Link Layer Discovery Protocol (LLDP) configuration information.
Syntax
show lldp
Modes
Privileged EXEC mode
Examples
The following example displays LLDP configuration information.
device# show lldp
Syntax
show lldp interface [ ethernet slot/port ]
Parameters
ethernet
Use this parameter to specify an Ethernet interface, followed by the slot or port number. For
devices that do not support line cards, specify 0 for the slot.
slot
Specifies a valid slot number. 0 is the only valid entry.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
If the ethernet slot/port parameter is not specified, this command displays the LLDP status
information received on all the interfaces.
Examples
To display all the LLDP ethernet interface information, enter the following:
0/19
0/20
0/21
0/22
0/23
To display the LLDP interface information for a specified ethernet interface, enter the following:
Syntax
show lldp neighbors interface ethernet slot/port [detail]
Parameters
interface ethernet
Causes the display of LLDP information about an Ethernet interface.
slot
Specifies a valid slot number. Must be 0 if the switch does not contain slots.
port
Specifies a valid port number.
detail
Specifies the display of detailed LLDP neighbor information.
Modes
Privileged EXEC mode
Examples
The following example shows how to display LLDP neighbor information for a specific interface
(Ethernet 0/18).
device# show lldp neighbors interface ethernet 1/18
Local Port Dead Interval Remaining Life Remote Port ID Remote Port Descr Chassis
ID Tx Rx System Name
Eth 1/18 120 115 Ethernet 2/25 Eth 2/25
768e.f807.6000 655 654 SLX
The following example displays detailed LLDP neighbor information for a specific interface (Ethernet
0/18).
device# show lldp neighbors interface ethernet 0/18 detail
MANDATORY TLVs
===============
Local Interface: Eth 0/18 (Local Interface MAC: 768e.f805.5816)
Remote Interface: Ethernet 0/25 (Remote Interface MAC: 768e.f807.610d)
Dead Interval: 120 secs
Remaining Life : 118 secs
Chassis ID: 768e.f807.6000
LLDP PDU Transmitted: 656 Received: 655
OPTIONAL TLVs
==============
Port Interface Description: Eth 0/25
System Name: SLX
DCBX TLVs
===========
MANDATORY TLVs
===============
Local Interface: Eth 0/33 (Local Interface MAC: d8c4.9780.f53d)
Remote Interface: Ethernet 0/33 (Remote Interface MAC: d8c4.9780.f43e)
Dead Interval: 120 secs
Remaining Life : 105 secs
Chassis ID: d8c4.9780.f41c
LLDP PDU Transmitted: 10 Received: 10
OPTIONAL TLVs
==============
Port Interface Description: Eth 0/33
System Name: NH-Leaf2
Remote Protocols Advertised: Link Aggregation
Remote VLANs Configured:
VLAN ID: 1 VLAN Name: default
VLAN ID: 5 VLAN Name: VLAN0005
VLAN ID: 10 VLAN Name: VLAN0010
VLAN ID: 50 VLAN Name: VLAN0050
VLAN ID: 500 VLAN Name: VLAN0500
Port Vlan Id: 1
Port & Protocol Vlan Flag: Supported, Not enabled
Port & Protocol Vlan Id: 0
DCBX TLVs
===========
Version : CEE
DCBX Ctrl OperVersion: 0 MaxVersion: 0 SeqNo: 2 AckNo: 2
DCBX ETS OperVersion: 0 MaxVersion: 0 Enabled: 1 Willing: 0 Error: 0
Enhanced Transmission Selection (ETS)
Priority-Group ID Map:
Priority : 0 1 2 3 4 5 6 7
Group ID : 0 0 0 0 0 0 0 0
Group ID Bandwidth Map:
Group ID : 0 1 2 3 4 5 6 7
Percentage: 0 0 0 0 0 0 0 0
Number of Traffic Classes supported: 8
DCBX PFC OperVersion: 0 MaxVersion: 0 Enabled: 1 Willing: 0 Error: 0
Syntax
show lldp statistics [ interface [ethernetslot/port ]]
Parameters
ethernet
Use this parameter to specify an Ethernet interface, followed by the slot or port number. For
devices that do not support line cards, specify 0 for the slot.
slot
Specifies a slot number. 0 is the only valid entry.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
If you do not specify an interface, this command displays the LLDP statistics for all interfaces.
Examples
To display LLDP statistics on the specified interface:
show loop-detection
Displays loop detection (LD) information at the system, interface (Ethernet or port-channel), or VLAN
VXLAN tunnel level.
Syntax
show loop-detection [ disabled-ports | globals | interface { ethernet
interface | port-channel interface } | vlan VLAN_ID]
Parameters
disabled-ports
Displays the ports that are disabled by LD.
globals
Displays global LD configuration values.
interface
Specifies an Ethernet or port-channel interface.
ethernetinterface
Specifies an Ethernet interface.
port-channelinterface
Specifies a port-channel interface.
vlanVLAN_ID
Specifies a VLAN.
Modes
Privileged EXEC mode
Examples
The following example displays LD information at the system level.
device# show loop-detection
Strict Mode:
------------------------
Packet Statistics:
vlan sent rcvd disable-count
100 100 0 0
Loose Mode:
------------------------
Number of LD instances: 2
Disabled Ports: 0/7
Packet Statistics:
vlan sent rcvd disable-count
100 100 0 0
Packet Statistics:
vlan sent rcvd disable-count
100 100 0 0
The following example displays LD configuration values, including logical interfaces (LIFs), for a VLAN
VXLAN tunnel.
device# show loop-detection vlan 20
Number of LD instances: 1
LIF (Logical Interface) Disabled on Ports: eth0/2,VxLAN Tunnel 61441
Packet Statistics:
vlan sent rcvd
20 44225 2
The following example displays LD configuration values for a VLAN VXLAN tunnel if LD shutdown is
disabled.
device# show loop-detection vlan 20
Number of LD instances: 1
LIF (Logical Interface) ShutDown is disabled for VLAN 20
Packet Statistics:
vlan sent rcvd
20 10 10
show mac-address-table
Displays MAC address table information.
Syntax
show mac-address-table
show mac-address-table bridge-domain [ id ]
show mac-address-table cluster cluster-ID [ { bridge-domain [ bd-ID ] } |
[client client-ID ] | client-pw| local | remote | [vlan vlan-ID ] ]
show mac-address-table count [ bridge-domain id ]
Parameters
bridge-domain id
Specifies the displaying of MAC addresses learned under a bridge domain. When a bridge
domain identifier is not specified, information is displayed about MAC addresses learned under
all bridge domains.
cluster cluster-ID
Displays the MAC addresses learned under the specified MCT cluster ID.
bridge-domain id
Displays the MAC addresses learned for the bridge domain of the MCT cluster. When a bridge
domain identifier is not specified, information is displayed about MAC addresses learned under
all bridge domains.
client client-ID
Displays the MAC addresses learned for the client ID of the MCT cluster.
client-pw
Specifies the PW client to display all the MAC addresses learned from other VPLS PE nodes over
MCT bridge domains. ( SLX 9640 and SLX 9540 devices only)
local
Displays the local MAC addresses for the cluster or the specified client ID.
remote
Displays the remote MAC addresses for the cluster or the specified client ID.
vlan vlan-ID
Displays the MAC addresses for the client VLAN ID of the MCT cluster.
address MAC-address
Displays forwarding information for a 48-bit MAC address. The valid format is H.H.H (available in
Privileged EXEC mode only).
aging-time
Displays aging-time.
dynamic address MAC-address
Specifies the dynamic MAC addresses for an Ethernet interface, port-channel, or VLAN. The valid
format is H.H.H (available in Privileged EXEC mode only).
interface ethernet slot/port
Specifies the Ethernet interface with a valid slot number/port number.
port-channel number
Specifies the port channel interface number.
vlan vlan id
Specifies the VLAN interface. The VLAN ID range is from 1 - 4090.
tunnel tunnel id
Specifies the tunnel interface. The tunnel ID range is from 1 - 100000.
mdb MAC-address
Specifies the MDB information for the cluster client specific macs. The valid format is H.H.H
(available in Privileged EXEC mode only).
client client-name
Displays the client instance. Specify the client name with a maximum of 64 characters.
static address mac-address
Specifies the static MAC address for an Ethernet interface, port-channel, or VLAN. The valid
format is H.H.H (available in Privileged EXEC mode only).
mac-move
Displays all mac-move-detect configuration.
shut-list
Displays the interfaces in the shutdown list.
Modes
Privileged EXEC mode.
Usage Guidelines
The MAC Type for an MCT cluster displays the following information:
• On the SLX 9640 and SLX 9540 devices:
◦ The MAC address over the CEP AC endpoints or VPLS PW are learned and treated as EVPN local
MAC addresses over a singled-homed edge node. These local addresses are learned as EVPN and
displayed as Dynamic. Corresponding MAC addresses synchronized to the remote MCT node are
displayed as EVPN. The EVPN MAC addresses are programmed pointing to the MCT PW.
◦ The VPLS MCT MAC on active PWs are learned as Dynamic and the corresponding MAC
addresses are learned as EVPN on remote MCT node.
• For the client MAC behavior, MAC addresses are learned as CCL on the local MCT node and CCR on
the remote MCT node pointing to the CCEP interface.
• Static MAC addresses configured on CEP AC end points are learned as Static. The corresponding
remote MAC addresses are learned as EVPN-Sticky in the remote node.
• For static MAC addresses over client interfaces, Static-CCL and CCR are displayed.
Examples
The following example shows how to display MAC table information for all bridge domains.
The following example shows the number of forwarding entries in the MAC address table for bridge
domain 1.
device# show mac-address-table count bridge-domain 1
The following example shows how to display the MAC address table aging time.
device# show mac-address-table aging-time
MAC Aging-time : 300 seconds
The following example shows how to display the MAC address table for an MCT cluster.
device# show mac-address-table cluster 1
Vlan/BD'Id Mac-address Type State Ports
100(V) 0010.a111.aaaa CCL Active ETH3/1
100(V) 0010.a111.aa22 Static-CCL Active ETH3/1
100(V) 0010.a111.bbbb CCR Active ETH3/1
200(V) 003d.a111.1111 Dynamic Active Eth 1/1
200(V) 003d.a111.1122 Static Active Eth 1/1
200(V) 003d.a111.3333 EVPN Active 10.2.2.2
200(V) 003d.a111.3322 EVPN-Static Active 10.2.2.2
The following example shows the mac-address-table information for BGP EVPN Multi-homed devices.
device# show mac-address-table
Type Code - CCL:Cluster Client Local MAC
CCR:Cluster Client Remote MAC
CR:Cluster Remote MAC
ES:Ethernet Segment
VlanId/BDId Mac-address Type State Ports/LIF/PW/T
30 (V) 0010.9400.0102 EVPN Active Tu 32771 (1.1.1.1)
Tu 32772 (2.2.2.2)
30 (V) 0010.9400.0202 EVPN Active Tu 32771 (1.1.1.1)
30 (V) 0010.9400.0302 EVPN Active Tu 32771 (1.1.1.1)
Syntax
show management-heartbeat manager
Modes
Management Heartbeat mode
Examples
To display the current state of the Management Heartbeat mode, use the following command:
SLX(config-management-heartbeat-manage) # show management-heartbeat manager
Admin state: up
Operational state: up
Threshold time: 30 minutes
Action: Maintenance mode enable
Time to last heartbeat: 4 minutes
show media
Displays the SFP information for all the interfaces present on a device.
Syntax
show media
Modes
Privileged EXEC mode
Usage Guidelines
The command output will be several pages long.
Examples
To display all SFP information, use the following command:
Syntax
show media interface [ethernet slot / port ]
Parameters
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Examples
To display SPF information, use the following command:
switch# show media interface ethernet 5/1
Syntax
show media tunable-optic-sfpp [ channel channel_number]
Parameters
channel channel_number
The channel number to display. The range of valid values is from 0 through 102.
Modes
Privileged EXEC mode
Output
The show media tunable-optic-sfpp command displays the following information:
Examples
Sample output for a single channel.
device# show media tunable-optic-sfpp channel 2
command is show-media-tunable-optic-sfpp-channel-2.
Channel Wavelength
========= ==============
2 1568.36
13 1563.86
14 1563.45
15 1563.05
16 1562.64
17 1562.23
18 1561.83
19 1561.42
20 1561.01
(Output truncated for brevity.)
show monitor
Displays the monitoring information for all port mirroring sessions or for one session.
Syntax
show monitor [ session session_number ]
Parameters
session session_number
Specifies a session identification number. Valid values range from 1 through 512.
Modes
Privileged EXEC mode
Output
The show monitor command displays the following information:
Examples
The following example displays monitoring information for all port mirroring sessions.
device# show monitor
Session : 1
Description : my_first_session
State : Enabled
Source Interface : Eth 0/1 (Up)
Destination Interface : Eth 0/11 (Up)
Direction : Rx
Session : 50
Description : [None]
State : Enabled
Source Interface : Eth 0/2 (Down)
Destination Interface : Eth 0/12 (Up)
Direction : Tx
The following example displays monitoring information for a specific port mirroring session.
device# show monitor session 1
Session : 1
Description : my_first_session
State : Enabled
Source Interface : Eth 0/1 (Up)
Destination Interface : Eth 0/11 (Up)
Direction : Rx
Syntax
show mpls autobw-template [ detail ]
Parameters
detail
Displays the auto-bandwith template information in detail.
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example displays a sample output of the command.
device# show mpls autobw-template
Total number of auto-bandwidth templates: 2
Adjust Adjust Over/und Minimum Maximum Monitor Ref.
Name Interval Threshold Limit Bandwidth Bandwidth Only Count
aaa 1200 10 5/ 15 1000 8000 No 3
bbb 600 Table 3/ 10 200 20000 No 5
The following example displays a sample output of the command using the detail option.
device# show mpls autobw-template detail
Total number of auto-bandwidth templates: 2
Auto-bandwidth template aaa:
adjustment-interval: 1200 sec, adjustment-threshold: 10, mode: monitor-and-signal
overflow-limit: 5, underflow-limit: 15
minimum-bw: 1000 kbps, maximum-bw: 8000 kbps
sample-record: enabled
number of paths associated: 3
Auto-bandwidth template bbb:
adjustment-interval: 600 sec, adjustment-threshold: Table, mode: monitor-and-signal
overflow-limit: 3, underflow-limit: 10
minimum-bw: 200 kbps, maximum-bw: 20000 kbps
sample-record: disabled
number of paths associated: 5
Syntax
show mpls auto-threshold-table
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example displays the output of the command.
device# show mpls autobw-threshold-table
Auto-bandwidth threshold table
Range(kbps) Threshold(kbps)
0-10 2000
11-1000 3000
1001-10000 5000
10001-max 10000
Syntax
show mpls bypass-lsp [ debug | detail | down | dynamic | extensive |
name | static | up [ detail | extensive | wide ] | wide ]
show mpls bypass-lsp dynamic [ debug | detail | extensive | interface
[ ethernet | ve ] | name | wide ]
show mpls bypass-lsp static [ debug | detail | extensive | interface |
name | wide ]
Parameters
debug
Displays the MPLS Bypass LSP extensive debug information.
detail
Displays the MPLS bypass LSP information in detail.
down
Displays the operationally down bypass LSPs information.
extensive
Displays the MPLS bypass LSP information with extensive detailed information.
interface
Displays the MPLS dynamic bypass LSP interface information.
ethernet
Specifies the ethernet interface.
ve
Specifies the VE interface.
name
Displays an MPLS bypass LSP by the specified name.
static
Displays the MPLS static bypass LSP information.
up
Displays the operationally UP bypass LSPs information.
wide
Displays MPLS bypass LSP brief wide information.
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example displays the output of the show mpls bypass-lsp command.
device# show mpls bypass-lsp
Note: Bypass LSPs marked with + are dynamic bypass LSPs
Bypass LSP To Admin Oper Tunnel Up/Dn Retry Active
Name Address State State Intf Times Num Path
my-bypass-lsp 20.20.20.20 UP UP tnl3 1 0 path-for-bypass-lsp
The following example displays the output of the show mpls bypass-lsp command with the
static wide options
device# show mpls bypass-lsp static wide
Bypass LSP To Admin Oper Tunnel Up/Dn Retry Active
Name Address State State Intf Times Num Path
my-bypass-lsp 20.20.20.20 UP UP tnl3 1 0 path-for-bypass-
lsp
The following example displays the output of the show mpls bypass-lsp command using the
extensive option.
device# show mpls bypass-lsp extensive
LSP my-bypass-lsp, to 20.20.20.20
From: 29.29.29.29, admin: UP, status: UP, tunnel interface(primary path): tnl3
Times primary LSP goes up since enabled: 1
Adaptive
Primary path: path-for-bypass-lsp, up: yes, active: yes
Maximum retries: None, no. of retries: 0
ReoptimizeTimer configured 360
ReoptimizeTimer next expiration in 93 seconds
Setup priority: 7, hold priority: 0, cos: 3
Max rate: 1000 kbps, mean rate: 1000 kbps, max burst: 5000 bytes
Tie breaking: random, hop limit: 6
Exclude any of admin groups: 15 16 17
Exclude interface(s): Eth 1/3
CSPF-computation-mode configured: te-metric
Constraint-based routing enabled: yes
Path calculated using constraint-based routing: yes
Path calculated using interface constraint: no
Path calculated using te-metric
Path cost: 2
Explicit path hop count: 1
18.18.18.18(S)
Recorded routes:
Protection codes/Rtr Id flags: P: Local N: Node B: Bandwidth I: InUse R: RtrId
18.29.1.18 -> 18.20.1.20
Bypass Tunnel bandwidth
Maximum bandwidth: 1000 kbps
Reservable bandwidth [priority] kbps:
[0] 1000 [1] 1000 [2] 1000 [3] 1000
[4] 1000 [5] 1000 [6] 1000 [7] 1000
Current signaled rate: 1000 kbps
Active Path:
Tunnel interface: tnl3, outbound interface: Eth 1/1
Tunnel index: 3, Tunnel instance: 1, Out label: 2061
History:
Syntax
show mpls dynamic-bypass interface [ brief | detail | ethernet | port-
channel | ve ]
Parameters
interface
Displays dynamic bypass interface information.
brief
Displays dynamic bypass interface brief information.
detail
Displays dynamic bypass interface detail information.
ethernet
Displays dynamic bypass ethernet interface.
port-channel
Displays dynamic bypass port-channel interface.
ve
Displays dynamic bypass VE interface.
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Syntax
show mpls-interface [ detail | ethernet slot/port | port-channel number |
ve number ]
Parameters
detail
Displays MPLS-enabled interfaces information in detail.
ethernet slot/port
Specifies an Ethernet slot and port.
port-channel number
Specifies a port-channel interface.
ve number
Specifies the VE interface number.
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Syntax
show mpls ldp database [ A.B.C.D | filtered ]
show mpls ldp fec [ prefix [ A.B.C.D or A.B.C.D/L | [ filtered [ in |
out ] | prefix-filter ] ] | summary | vc ]
show mpls ldp interface [ ethernet slot/port | port-channel number | ve
number ]
show mpls ldp neighbor [ A.B.C.D or A.B.C.D/L ]
show mpls ldp path [ A.B.C.D or A.B.C.D/L ]
show mpls ldp peer [ A.B.C.D | brief | detail ]
show mpls ldp session [ A.B.C.D | detail ]
show mpls ldp statistics
show mpls ldp targeted-peer [ A.B.C.D ]
show mpls ldp tunnel [ A.B.C.D or A.B.C.D/L | brief | detail | out-
interface [ ethernet interface | ve ] ]
Parameters
database
Displays the LDP database information.
A.B.C.D
Displays the peer IP address.
filtered
Displays the sessions with inbound filtered mappings.
fec
Displays the FEC information.
prefix
Displays the prefix FEC information.
A.B.C.D or A.B.C.D/L
Displays the IP address/prefix.
filtered
Displays the filtered prefix FEC.
in
Displays inbound filtered prefix FEC.
out
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Syntax
show mpls lsp [ debug | detail | down | extensive | name | up | wide ]
show mpls lsp down [ debug | detail | extensive |wide ]
show mpls lsp up [ detail | extensive | wide ]
Parameters
debug
Displays the MPLS LSP extensive debug information.
detail
Displays the MPLS LSP information in detail.
down
Displays the operationally down LSPs information.
extensive
Displays the MPLS LSP extensive information.
name
Displays an MPLS LSP by the specified name.
up
Displays the operationally UP LSPs information.
wide
Displays MPLS LSP brief wide information.
Modes
This command operates under all modes.
Usage Guidelines
The sample history displays for the current adjustment interval.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
This command can display the underflow-limit parameter and the number of consecutive underflows.
The adjustment-threshold is used from the global table is indicated with the value for current rate. The
show mpls lsp extensive command shows the adjustment event with the previous rate and the
maximum sampled rate.
Output
The show mpls lsp command displays the following information:
Examples
The following example shows the output of the command, specifying the LSP name with the
extensive option.
The following example displays the output of the command when using the detail option.
Router# show mpls lsp extensive
LSP lsp1, to 23.23.23.23
From: 34.34.34.34, admin: UP, status: UP, tunnel interface(primary path): tnl1
Times primary LSP goes up since enabled: 1
Metric: 0, Adaptive
Maximum retries: NONE, no. of retries: 0
Pri. path: NONE, up: yes, active: yes
Setup priority: 7, hold priority: 0
Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
Auto-bandwidth. template: template1, mode: monitor-only
adjustment interval: 86400 sec, adjustment threshold: 0
minimum bw: 0 kbps, maximum bw: 2147483647 kbps
overflow limit: 0, underflow limit: 20, sample-record: disabled
Constraint-based routing enabled: yes
Path calculated using constraint-based routing: yes
The following output displays the command with the autobw-samples option.
device# show mpls lsp name lsp1 autobw-samples
LSP lsp1, to 23.23.23.23
From: 34.34.34.34, admin: UP, status: UP, tunnel interface(primary path): tnl1
Times primary LSP goes up since enabled: 1
Metric: 0, Adaptive
Maximum retries: NONE, no. of retries: 0
Pri. path: NONE, up: yes, active: yes
Setup priority: 7, hold priority: 0
Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
Auto-bandwidth. template: template1, mode: monitor-only
adjustment interval: 86400 sec, adjustment threshold: 0
minimum bw: 0 kbps, maximum bw: 2147483647 kbps
overflow limit: 0, underflow limit: 20, sample-record: disabled
Constraint-based routing enabled: yes
Path calculated using constraint-based routing: yes
Path calculated using interface constraint: no
Path cost: 20
Tie breaking: random, hop limit: 0
LDP tunneling enabled: no
Soft preemption enabled: no
Sec. path: via16, active: no
Hot-standby: no, status: down, adaptive
Setup priority: 7, hold priority: 0
Max rate: 0 kbps, mean rate: 0 kbps, max burst: 0 bytes
Auto-bandwidth. template: NONE, mode: monitor-and-signal
adjustment interval: 300 sec, adjustment threshold: Table
minimum bw: 0 kbps, maximum bw: 2147483647 kbps
overflow limit: 5, underflow-limit: 10, sample-record: enabled
Constraint-based routing enabled: yes
hop limit: 0
Soft preemption enabled: no
Active Path attributes:
Tunnel interface: tnl1, outbound interface: e4/3
Tunnel index: 2, Tunnel instance: 1 outbound label: 2049
Auto-bandwidth running info. Mode: monitor-only
adjustment interval: 1200 sec(T), adjustment threshold: 3000(A)
overflow limit: 0, underflow limit: 4
minimum bw: 0 kbps(T), maximum bw: 9647 kbps(T)
Samples collected: 5, max sampled bw:6598 kbps,last sample: 0 kbps
Overflow-count: 0, Underflow-count: 2,max-underflow-sample: 34kbps
Sample-record: enabled(T)
adjustment due in 1174 seconds
Adjustment ignored: 0 time(s)
No adjustment since activation. Current bandwidth: 0 kbps
Recorded routes:
Protection codes/Rtr Id flag: P: Local N: Node B: Bandwidth I: InUse R: RtrId
31.31.31.16 -> 161.161.161.1
Auto Bandwidth Sample History:
1 Feb 4 19:56:06 : Path p1 active with rate 3000 kbps
2 Feb 4 19:57:06 : 4445 kbps
3 Feb 4 19:58:06 : 4855 kbps
4 Feb 4 19:59:06 : 4501 kbps
5 Feb 4 20:00:06 : 4200 kbps
6 Feb 4 20:01:06 : 4455 kbps
7 Feb 4 20:02:06 : 4319 kbps
8 Feb 4 20:03:06 : 4299 kbps
9 Feb 4 20:04:06 : 4582 kbps
10 Sample recording disabled
11 Feb 4 20:16:31 : 3630 kbps
12 Feb 4 20:17:31 : 2924 kbps
13 Feb 4 20:17:38 : Rate adjusted from 2500 to 4500 kbps
Reason: Adjustment-interval expiry
14 Feb 4 20:18:06 : 4500 kbps
15 Feb 4 20:19:06 : 4500 kbps
16 Feb 4 20:20:06 : 4500 kbps
17 Feb 4 20:21:06 : 4500 kbps
18 Feb 4 20:16:31 : 4500 kbps
19 Feb 4 20:17:31 : 4500 kbps
20 Feb 4 20:17:38 : Adjustment ignored. Threshold not crossed
21 Feb 4 20:16:31 : 9000 kbps
22 Feb 4 20:17:31 : 9000 kbps
23 Feb 4 20:17:38 : Rate adjusted from 4500 to 9000 kbps
Reason: Overflow limit exceeded
24 Feb 4 20:18:06 : 4500 kbps
25 Feb 4 20:19:06 : 4500 kbps
Syntax
show mpls policy
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example shows a sample output of the command.
Router#show mpls policy
Current MPLS policy settings:
CSPF interface constraint: disabled
CSPF-Group computation-mode: disabled
CSPF computation-mode use bypass metric: disabled
CSPF computation-mode use bypass liberal: disabled
TTL propagation for MPLS label: disabled, IPVPN: disabled, IP over MPLS: enabled
Inter-AS route filtering: enabled, Intra-AS iBGP route filtering: disabled
Ingress tunnel accounting: disabled
Polling interval for MPLS LSP traffic statistics: 300 seconds
Advertise TE parameters via: OSPF
Handle IGP neighbor down event - ISIS: No OSPF: No
LSP rapid retry: enabled, maximum number of retries: no limit
LSP periodic retry time: 30 seconds
FRR backup/detour retry time: 30 seconds
Auto-bandwidth: enabled, sample-interval: 60 seconds
Maximum samples recorded per LSP: 1500
Soft preemption cleanup-timer: 30 seconds
MPLS TE Periodic Flooding Timer : 180 seconds
MPLS TE flooding thresholds
Global UP thresholds : None
Global DOWN thresholds : None
Default UP thresholds : 15 30 45 60 75 80 85 90 95 96 97 98 99 100
Default DOWN thresholds : 99 98 97 96 95 90 85 80 75 60 45 30 15
Syntax
show mpls rsvp igp-sync [ link [ detail | ip ipv4 addr ] | lsp [ detail |
name name ] ]
show mpls rsvp interface [ detail | ethernet slot/port | port-channel
number | ve vlan_id ]
show mpls rsvp neighbor [ detail | ipv4 address ]
show mpls rsvp session [ backup | brief | destination | detail | detour
| down | egress | extensive | in-interface | ingress | name | out-
interface | transit | up | wide ]
show mpls rsvp statistics
Parameters
igp-sync
Displays the RSVP IGP synchonization information.
link
Displays the RSVP IGP synchonization link brief information.
detail
Displays the RSVP IGP synchonization link detailed information.
ip ipv4 addr
Displays the RSVP IGP synchonization specified link information.
lsp
Displays the RSVP IGP synchonization LSP brief information.
detail
Displays the RSVP IGP synchonization LSP detailed information.
name name
Displays the RSVP IGP synchonization specified LSP information.
interface
Displays RSVP interface information.
detail
Displays RSVP interface information in detail.
ethernet slot/port
Displays the specifed RSVP Ethernet information.
port-channel number
Specifies a port-channel.
ve vlan_id
Displays the specified VE information.
neighbor
Displays the RSVP neighbor information.
detail
Displays the RSVP neighbor information in detail.
session
Displays the RSVP session information. For addition information, see the show mpls rsvp
session command page.
statistics
Displays the RSVP control packet statistics information.
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example shows the command using the interface option in the interface mode.
device(config-if-e1000-0/8)# show mpls interface e0/7
Admin: Up Oper: Up
MTU: 1500 bytes
Maximum BW: 10000000 kbps, maximum reservable BW: 10000000 kbps
Admin group: 0x00000000
Reservable BW [priority] kbps:
[0] 10000000 [1] 10000000 [2] 10000000 [3] 10000000
[4] 10000000 [5] 10000000 [6] 10000000 [7] 10000000
Last sent reservable BW [priority] kbps:
[0] 10000000 [1] 10000000 [2] 10000000 [3] 10000000
[4] 10000000 [5] 10000000 [6] 10000000 [7] 10000000
Soft Preemption under provisioned BW [priority] kbps: [0] 0 [1] 0 [2] 0 [3] 0
[4] 0 [5] 0 [6] 0 [7] 0
LDP tunnel count: 0
The following example shows the command using the interface detail option in the router mpls
mode.
Syntax
show mpls rsvp interface [ detail | ethernet slot/port | port-channel
number | ve vlan_id ]
Parameters
detail
Displays the RSVP interface information in detail.
ethernet slot/port
Specifies the selected Ethernet interface.
port-channel number
Specifies a port-channel interface.
ve vlan_id
Specifies the selected VE interface.
Modes
Privileged EXEC mode
Usage Guidelines
To clear the RSVP statistics counters, use the clear mpls rsvp statistics command.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show mpls rsvp interface detail command displays the following information:
Examples
The following example shows a abbreviated output of the command with the detail option.
device# show mpls rsvp interface
G = Interface is using global config for Refresh Reduction, Reliable Messaging
L = Interface is using local config for Refresh Reduction, Reliable Messaging
D = Refresh Reduction, Reliable Messaging is exclusively disabled on Interface
Syntax
show mpls rsvp session backup [ detail | extensive | protection-available
[ active | detail | extensive | inactive | wide ] | protection-
unavailable [ detail | extensive | wide ] | wide ]
show mpls rsvp session brief
show mpls rsvp session destination ip_addr
show mpls rsvp session detail
show mpls rsvp session detour
show mpls rsvp session down [ detail | egress | extensive | in-interface
| ingress | out-interface | transit | wide ]
show mpls rsvp session egress
show mpls rsvp session extensive
show mpls rsvp session in-interface [ ethernet slot/port | port-channel
number | ve vlan_id ]
show mpls rsvp session ingress
show mpls rsvp session name
show mpls rsvp session out-interface [ ethernet slot/port | port-channel
number | ve vlan_id ]
show mpls rsvp session transit
show mpls rsvp session up
show mpls rsvp session wide
Parameters
backup
Displays backup session information.
active
Displays active backup session information.
detail
Displays detailed backup session information.
extensive
Displays extensive backup session information, including History.
inactive
Displays inactive, but up backup or detour session information.
protection-available
Modes
Privileged EXEC mode
Usage Guidelines
Many options in the show mpls rsvp session command can be combined for a more specific
result. For example, the show mpls rsvp session backup name lsp1 command is helpful for
limiting the output to useful information by session name.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example displays a sample output of the show mpls rsvp session command.
105
13.14.13.14 30.11.1.30 Up SE - 2057 Eth 0/5 to13_f30_9
105
13.14.13.14 30.11.1.30(DI) Up SE - 2158 Eth 0/6 to13_f30_9
06
13.14.13.14 30.11.1.30 Up SE - 2059 Eth 0/5 to13_f30_9
06
13.14.13.14 30.11.1.30(DI) Up SE - 3319 Eth 0/5 to13_f30_9
07
13.14.13.14 30.11.1.30 Up SE - 2849 Eth 0/6 to13_f30_9
07
13.14.13.14 30.11.1.30(DI) Up SE - 2160 Eth 0/6 to13_f30_9
08
13.14.13.14 30.11.1.30 Up SE - 2061 Eth 0/5 to13_f30_9
08
13.14.13.14 30.11.1.30(DI) Up SE - 2161 Eth 0/5 to13_f30_9
09
13.14.13.14 30.11.1.30 Up SE - 2063 Eth 0/6 to13_f30_9
09
The following example displays a sample output of the show mpls rsvp session backup
command.
_p3_p3_104
172.16.50.1 172.16.20.1(BI) Up - - 4089 Ve 52 R20_to_R50
_p3_p3_104
172.16.50.1 172.16.20.1 Up SE - 2124 Ve 41 R20_to_R50
_p3_p3_105
172.16.50.1 172.16.20.1(BI) Up - - 4085 Ve 52 R20_to_R50
_p3_p3_105
172.16.50.1 172.16.20.1 Up SE - 2123 Ve 41 R20_to_R50
_p3_p3_106
172.16.50.1 172.16.20.1(BI) Up - - 4084 Ve 52 R20_to_R50
_p3_p3_106
172.16.50.1 172.16.20.1 Up SE - 2122 Ve 41 R20_to_R50
_p3_p3_107
172.16.50.1 172.16.20.1(BI) Up - - 4083 Ve 52 R20_to_R50
_p3_p3_107
172.16.50.1 172.16.20.1 Up SE - 2121 Ve 41 R20_to_R50
_p3_p3_108
172.16.50.1 172.16.20.1(BI) Up - - 4079 Ve 52 R20_to_R50
_p3_p3_108
172.16.50.1 172.16.20.1 Up SE - 2120 Ve 41 R20_to_R50
_p3_p3_109
172.16.50.1 172.16.20.1(BI) Up - - 4077 Ve 52 R20_to_R50
_p3_p3_109
172.16.50.1 172.16.20.1 Up SE - 2119 Ve 41 R20_to_R50
_p3_p3_11
172.16.50.1 172.16.20.1(BI) Up - - 4069 Ve 52 R20_to_R50
_p3_p3_11
172.16.50.1 172.16.20.1 Up SE - 2118 Ve 41 R20_to_R50
_p3_p3_110
172.16.50.1 172.16.20.1(BI) Up - - 4068 Ve 52 R20_to_R50
_p3_p3_110
172.16.50.1 172.16.20.1 Up SE - 2117 Ve 41 R20_to_R50
_p3_p3_111
172.16.50.1 172.16.20.1(BI) Up - - 4066 Ve 52 R20_to_R50
Aborted: by user
device#
The following example displays a sample output of the show mpls rsvp session command using
the wide option.
device# show mpls rsvp session wide
Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour
DE:Egress Detour BI:Ingress Backup BM: Merged Backup BE:Egress Backup
RP:Repaired Session BYI: Bypass Ingress
The following example displays a sample output of the show mpls rsvp session command with
the detail option.
device# show mpls rsvp session detail
Codes: DI:Ingress Detour DT:Transit Detour DM:Merged Detour
DE:Egress Detour BI:Ingress Backup BM: Merged Backup BE:Egress Backup
RP:Repaired Session BYI: Bypass Ingress
20.20.20.20 (S)
PATH rcvfrom: None (downstream only)
PATH sentto: 20.20.20.20 (Eth 0/1 ) (MD5 OFF), Message ID: --
Riding bypass lsp: my-bypass-ingress
19.19.19.19 (S)
PATH rcvfrom: None (downstream only)
PATH sentto: 19.19.19.19 (Eth 1/4 ) (MD5 OFF), Message ID: --
Riding bypass lsp: my-bypass-transit
Syntax
show mpls statistics { oam }
show mpls statistics { transit [ label label | ldp [ ip_addr | submask |
label ] | rsvp label ] }
show mpls statistics { tunnel [ destination ip_addr | index vif_index |
ldp [ destination ip_addr | index vif_index ] | rsvp [ destination
ip_addr | index vif_index | name name ] ] }
Parameters
oam
Displays the MPLS OAM statistics.
transit
Displays the MPLS transit statistics.
label label
Displays the MPLS transit statistics for the selected label.
ldp ip_addr
Displays the MPLS transit LDP statisticsfor the selected IP address.
rsvp
Displays the MPLS transit RSVP statistics .
tunnel
Displays the MPLS tunnel statistics.
destination destination
Displays the MPLS tunnel statistics for the selected tunnel destination.
index vif_index
Displays the MPLS tunnel statistics for the selected tunnel index.
ldp
Displays the MPLS tunnel LDP statistics.
destination destination
Displays the MPLS tunnel statistics for the selected tunnel destination.
index vif_index
Displays the MPLS tunnel statistics for the selected tunnel index.
rsvp
Displays the MPLS tunnel RSVP statistics.
destination destination
Displays the MPLS tunnel statistics for the selected tunnel destination.
index vif_index
Displays the MPLS tunnel statistics for the selected tunnel index.
name name
Displays the MPLS tunnel statistics for the selected named tunnel.
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Output
The show mpls statistics command displays the following information:
Examples
The following example shows the command using the tunnel option.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp t2
device(config-router-mpls-lsp-t2)# show mpls statistics tunnel
Total Since Last clear Rate
Name Intf Prot Packets Bytes Packets Bytes Pkts/sec Bytes/sec
t1 tnl0 R 2004 28175882 2004 28175882 6 93919
t2 tnl1 L 3101 40373763 3101 40373763 10 134579
The following example shows the command using the tunnel rsvp option.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp t2
device(config-router-mpls-lsp-t2)# show mpls statistics tunnel rsvp
The following example shows the command using the transit option.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp t2
device(config-router-mpls-lsp-t2)# show mpls statistics transit
Total Since Last clear Rate
IN Label Prot Packets Bytes Packets Bytes Pkts/sec Bytes/sec
2048 R 2004 28175882 2004 28175882 6 93919
2050 L 3101 40373763 3101 40373763 10 134579
The following example shows the command using the transit ldp option.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp t2
device(config-router-mpls-lsp-t2)# show mpls statistics transit ldp
Total Since Last clear Rate
IN Label Packets Bytes Packets Bytes Pkts/sec Bytes/sec
2050 3101 40373763 3101 40373763 10 134579
Syntax
show mpls te [ area ipv4_addr | detail | link ipv4_addr | node
ipv4_addr ]
Parameters
area ipv4_addr
Displays the specified OSPF area or IS-IS level information.
detail
Displays detailed information.
linkipv4_addr
Displays the specified link information.
nodeipv4_addr
Displays the specified node information by the node router ID.
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Fate-sharing group membership for any given TE link or node consists of its own membership to the
group, and the TE node to which it belongs. The output from the show mpls te database
detail command displays the fate-sharing groups to which the TE links or nodes belong.
Examples
In the following example output, node 10.20.20.20 displays fate-sharing group information for
group1/100 and group2/10 .
show mvrp
Displays the global MVRP information on the device including configured ports, global enable status,
and global timer settings.
Syntax
show mvrp
Modes
Privileged EXEC mode
Usage Guidelines
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
Output
The show mvrp command displays the following information:
Examples
The following example displays the global MRVP information on the device.
device# show mvrp
----------------------------------------------------------------
Total configured mvrp ports : 5
Global Status : Enabled
Join-timer(in centiseconds) : 20
Leave-timer(in centiseconds) : 100
Leaveall-timer(in centiseconds) : 1000
----------------------------------------------------------------
MVRP Port(s): eth1/1, eth1/5, eth1/7, eth1/9, po11
Syntax
show mvrp attributes [ interface {ethernet slot/port | port-channel
number } ] [ vlan ID ]
Parameters
interface
Displays the MVRP information for a specific MVRP-enabled interface.
ethernet slot/port
Specifies an Ethernet interface.
port-channel number
Specifies the port-channel interface.
vlan ID
Specifies the VLAN ID.
Modes
Privileged EXEC mode
Usage Guidelines
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
The show mvrp attributes command without any options displays the VLAN information and
MVRP FSM states for each VLAN for all MVRP-enabled Ethernet and port-channel interfaces.
Output
The show mvrp attributes command displays the following information:
Applicant State Applicant record for each attribute; whether it has been actively
making a declaration, or has been passive.
Examples
The following example displays MVRP attributes for all interfaces.
device# show mvrp attributes
Port : eth0/17 State : Disabled
-----------------------------------------------------------------------------
VLAN Registrar Registrar Applicant
State Mgmt State
-----------------------------------------------------------------------------
Port : eth0/5 State : Forwarding
-----------------------------------------------------------------------------
VLAN Registrar Registrar Applicant
State Mgmt State
-----------------------------------------------------------------------------
1 In Fixed Quiet Active
5 Empty Normal Quiet Active
10 In Fixed Quiet Active
Port : po10 State : Forwarding
-----------------------------------------------------------------------------
VLAN Registrar Registrar Applicant
State Mgmt State
-----------------------------------------------------------------------------
1 In Fixed Quiet Active
5 In Normal Very Anxious Observer
10 Empty Normal Quiet Active
Syntax
show mvrp inteface { ethernet slot/port | port-channel number }
Parameters
ethernet slot/port
Specifies the Ethernet interface.
port-channel number
Specifies the port channel of the interface.
Modes
Privileged EXEC mode
Usage Guidelines
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
Output
The show mvrp interface command displays the following information:
Examples
The following example displays the MVRP information for an Ethernet interface.
device# show mvrp interface ethernet 0/1
-----------------------------------------------------------------------------------------
MVRP Status : Enabled
Join-timer(in centiseconds) : 20
Leave-timer(in centiseconds) : 100
Leaveall-timer(in centiseconds) : 1000
P2p : Yes
Applicant Mode : normal-participant
-----------------------------------------------------------------------------------------
Registered Vlan(s) : 1 to 60 77 100 to 500 999
Declared Vlan(s) : 1 to 60 77 100 to 500 999
Forbidden Vlan(s) : 10
-----------------------------------------------------------------------------------------
Syntax
show mvrp statistics [ interface {ethernet slot/port | port-channel
number } ]
Parameters
interface
Displays the MVRP statistics for a specific MVRP-enabled interface.
ethernet slot/port
Specifies an Ethernet interface.
port-channel number
Specifies the port-channel interface.
Modes
Privileged EXEC mode
Usage Guidelines
This feature is supported on the SLX 9250, SLX 9540, SLX 9640, and SLX 9740 devices.
The show mvrp statistics command when executed without any options, displays the statistics
for all MVRP-enabled interfaces. Execute the show mvrp statistics command with the interface
option to display statistics of ethernet or port-channel interfaces.
Output
The show mvrp statistics command displays the following information:
Examples
The following example displays the statistics for all MVRP-enabled interfaces.
device# show mvrp statistics
Port : eth0/1
-----------------------------------------------------------------------------
Message type Transmitted Received
-----------------------------------------------------------------------------
New 0 0
In 0 1809
Join In 1816 0
Join Empty 1788 0
Empty 0 771
Leave 99 0
Leave-all 264 512
-----------------------------------------------------------------------------
Total PDUs 1827 1293
-----------------------------------------------------------------------------
Port-channel : Po100
----------------------------------------------------------
Message type Transmitted Received
-----------------------------------------------------------------------------
New 0 2
In 693 0
Join In 1800 1777
Join Empty 0 1956
Empty 396 0
Leave 0 96
Leave-all 369 346
-----------------------------------------------------------------------------
Total PDUs 1807 1799
-----------------------------------------------------------------------------
show netconf
Displays NETCONF session.
Syntax
show netconf
Modes
Privileged EXEC mode
Usage Guidelines
The text output is extensive. Extreme Networks recommends redirecting the output to a text file.
Examples
Typical NETCONF session output.
device# show netconf
netconf-state capabilities capability urn:ietf:params:netconf:base:1.0
netconf-state capabilities capability urn:ietf:params:netconf:base:1.1
netconf-state capabilities capability urn:ietf:params:netconf:capability:writable-
running:1.0
netconf-state capabilities capability urn:ietf:params:netconf:capability:startup:1.0
netconf-state capabilities capability urn:ietf:params:netconf:capability:xpath:1.0
netconf-state capabilities capability urn:ietf:params:netconf:capability:validate:1.0
netconf-state capabilities capability urn:ietf:params:netconf:capability:validate:1.1
netconf-state capabilities capability http://tail-f.com/ns/netconf/actions/1.0
<output truncated>
Syntax
show netconf capabilities
Modes
Privileged EXEC mode
Usage Guidelines
Because the text output is extensive, we recommend redirecting the output to a text file.
Examples
Typical command example of output.
device# show netconf capabilities
netconf-state capabilities capability urn:ietf:params:netconf:base:1.0
netconf-state capabilities capability urn:ietf:params:netconf:base:1.1
netconf-state capabilities capability urn:ietf:params:netconf:capability:writable-
running:1.0
netconf-state capabilities capability urn:ietf:params:netconf:capability:startup:1.0
netconf-state capabilities capability urn:ietf:params:netconf:capability:xpath:1.0
netconf-state capabilities capability urn:ietf:params:netconf:capability:validate:1.0
netconf-state capabilities capability urn:ietf:params:netconf:capability:validate:1.1
netconf-state capabilities capability http://tail-f.com/ns/netconf/actions/1.0
<output truncated>
Syntax
show notification stream
Modes
Privileged EXEC mode
Examples
Typical output example for this command.
device# show notification stream ?
Possible completions:
no event streams present
Syntax
show ntp status
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the active NTP server. If an NTP server is not configured, the command
output displays the server as "LOCL". Otherwise, the command displays the NTP server IP address.
Examples
To show the local device NTP status when NTP server is configured:
device# show ntp status
Clock is synchronized, stratum 3, reference clock is 10.20.232.222
precision is 2**-22
reference time is e0bdcea2.94df0a0d (10:59:46.2497645069 GMT Wed Jun 26 2019)
clock offset is 0.0854 msec, root delay is 69.0540 msec
root dispersion is 34.5350 msec, peer dispersion is 31.9061 msec
system poll interval is 64, last clock update was 300 sec ago
Syntax
show ntp status association detail { ipv4 address | ipv6 address }
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to view detailed information of one NTP server and peer.
Examples
To show the NTP status association details.
device# show ntp status association detail
Syntax
show ntp associations
Modes
Privileged EXEC mode
Examples
To show the NTP server status associations.
device# show ntp status associations
remote refid st t when poll reach delay offset jitter
==============================================================================
2620:100:0:f404 .PPS. 1 u 20 64 17 0.460 -4.844 0.897
+216.45.57.38 20.162.227.208 2 u 502 1024 377 241.941 12.103 10.920
-172.19.69.1 172.82.134.51 3 u 741 1024 377 223.985 -7.426 2.571
*216.45.57.38 128.252.19.1 2 u 884 1024 377 230.046 1.422 5.871
+10.0.017 208.75.89.4 3 u 858 1024 377 211.094 -1.801 6.431
The character in the left margin indicates the fate of this server/peer in the clock selection process.
show overlay-gateway
Displays status and statistics for the VXLAN overlay-gateway instance.
Syntax
show overlay-gateway [ name name [ vlan statistics | statistics ]
Parameters
name
Name of the configured VXLAN gateway.
vlan statistics
Displays statistics for each VLAN for the VXLAN gateway. Statistics include transmitted and
received packet counts and byte counts exchanged for each exported VLAN. Because each
exported VLAN maps to a VXLAN, these statistics apply on a per-VXLAN-counters basis. Per-
VLAN counters are not enabled by default. You need to first run the enable statistics
direction command for the gateway to enable statistics for specified VLAN IDs.
statistics
Displays statistics for the VXLAN gateway. Statistics include transmitted and received packet
counts and byte counts. These counters are derived by aggregating tunnel counters for all the
tunnels of the gateway.
Modes
Privileged EXEC mode
Usage Guidelines
Output includes the gateway name, the system-assigned gateway ID, source IP address, VRF,
administration state, and number of tunnels associated.
If you specify the gateway name, the gateway must already be configured.
Examples
To show the status for a gateway instance that is configured for Layer 2 extension with a loopback
interface:
device# show overlay-gateway
Packets Bytes
VLAN VNI Tx Rx Tx Rx
-----------------------------------------------------
10 1010 10000 200000 1110111 22227772
11 1011 2200 - 221334 -
21 1021 - 1 - 100
show onieversion
Displays the installed version of ONIE.
Syntax
show onieversion
Modes
Privileged EXEC Mode
Usage Guidelines
This command is only supported on the SLX 9150, SLX 9250, Extreme 8720, and Extreme 8520 devices.
Examples
This example shows the usage of the command.
SLX # show onieversion
ONIE Version=2020.05.00.07
SLX #
show policy-map
Displays information for the configured policy maps including class-map policer parameters.
Syntax
show policy-map [ control-plane [ map-name policyname ] ] | [ details
policyname | [ { interface [ ethernet slot/port | ve ve-id ] } |
system ] [ input | output ] ]
Parameters
control-plane [ map-name policyname ]
Displays the policy map in the control plane.
details policyname
Displays the detail configuration of the policy map along with binding information.
interface [ ethernet slot/port | ve ve-id ]
Displays the information of the policy map for the specified interface. Enter a valid slot and port
number for an Ethernet or a Virtual Ethernet (VE) interface.
system map-name policyname
Displays the information for the globally-applied policy map.
input
Inbound - direction where the policy map is applied.
output
Outbound - direction where the policy map is applied.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command without any keywords to display all policy map binding information including the
control plane and all interfaces.
Examples
The following example displays all policy map binding information including the control plane and all
interfaces.
Policy-Map P2-DEFAULT-RL-10000000000
Bound To: Eth 1/27(in)
Policy-Map P3-DEFAULT-RL-1500000000
Bound To:None
….
The following example displays the policy map in the control plane.
Ingress Direction :
Policy-Map cp-pmap1
Class cm1
matches 480661 packets 61524608 bytes
Police cir 22222
Stats:
Operational cir:22000 cbs:3332 eir:0 ebs:0
Conform Byte:0 Exceed Byte:0 Violate Byte:0
Ingress Direction :
Policy-Map p2
Class c2
matches 7867567 packets 1007048576 bytes
Police cir 1000000
Stats:
Operational cir:1010000 cbs:149999 eir:0 ebs:0
Conform Byte:1180928 Exceed Byte:0 Violate Byte:1005867648
Ingress Direction :
Policy-Map pm1
Class cm1
matches 480661 packets 61524608 bytes
Police cir 100000
Stats:
Operational cir:109000 cbs:14999 eir:0 ebs:0
Conform Byte:265088 Exceed Byte:0 Violate Byte:0
This example shows the configuration of the policy map that is attached to a control plane interface.
device# show policy-map control-plane
Ingress Direction :
Policy-Map map-ssh
Class class-ssh-2
matches 91785 packets 11748480 bytes
Police cir 100000
Stats:
Operational cir:102000 cbs:15000 eir:0 ebs:0
Conform Byte:11748480 Exceed Byte:0 Violate Byte:0
Class class-ssh-3
matches 91764 packets 11745792 bytes
Police cir 1000000
Stats:
Operational cir:997000 cbs:150000 eir:0 ebs:0
Ingress Direction :
Policy-Map policy-map_1
Class class-map_1
matches 0 packets 0 bytes
Police cir 1111111 eir 1111111
Stats:
Operational cir:1112000 cbs:166665 eir:1112000 ebs:166665
Conform Byte:0 Exceed Byte:0 Violate Byte:0
SLX#
Egress Direction :
Policy-Map policy-map_2
Class class-map_2
matches 0 packets 0 bytes
Police cir 1111111 eir 1111111
Stats:
Operational cir:1112000 cbs:166665 eir:1112000 ebs:166665
Conform Byte:0 Exceed Byte:0 Violate Byte:0
SLX#
Ingress Direction
Policy-Map policy-map_1
Class class-map_1
matches 0 packets 0 bytes
Police cir 1111111 eir 1111111
Stats:
Operational cir:1112000 cbs:166665 eir:1112000 ebs:166665
Conform Byte:0 Exceed Byte:0 Violate Byte:0
Egress Direction
Policy-Map policy-map_1
Class class-map_1
matches 0 packets 0 bytes
Police cir 1111111 eir 1111111
Stats:
Operational cir:1112000 cbs:166665 eir:1112000 ebs:166665
Conform Byte:0 Exceed Byte:0 Violate Byte:0
SLX#
To clear the policy-map counters at ingress direction:
SLX# clear policy-map-counters interface Ve 100 in
show port-channel
Displays the link aggregation group (LAG) information for a port-channel.
Syntax
show port-channel [ number | detail | load-balance | summary ]
Parameters
number
Specifies a LAG port-channel group number.
detail
Displays detailed LAG information for a port-channel.
load-balance
Displays the load-balance or frame-distribution scheme among ports in the port-channel.
summary
Displays the summary information per channel-group.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the LAGs present on the system with details about the LACP counters on
their member links. LAG interfaces are called port-channels.
When using the show port-channel number command, an asterisk in the command output
designates that the designated port channel is the primary link through which the BUM (broadcast,
unknown unicast and multicast) traffic flows.
Examples
The following example displays detailed port-channel information.
device# show port-channel detail
LACP Aggregator: Po 10
Aggregator type: Standard
Actor System ID - 0x8000,f4-6e-95-9f-13-e2
Admin Key: 0010 - Oper Key 0010
Receive link count: 2 - Transmit link count: 2
Individual: 0 - Ready: 1
Partner System ID - 0x8000,f4-6e-95-9f-15-a4
Partner Oper Key 0010
Flag * indicates: Primary link in port-channel
Number of Ports: 2
Minimum links: 1
Member ports:
Link: Eth 0/9 (0xC012140) sync: 1
Link: Eth 0/10 (0xC014140) sync: 1 *
(members)
U - Up (port-channel) * - Primary link in port-
channel
S - Switched
M - Not in use. Min-links not met
===== =============== ========== ===============
Group Port-channel Protocol Member ports
===== =============== ========== ===============
1 Po 1 (D) None
Syntax
show port port-channel ethernet port_id
Parameters
port_id
Specifies the port to display.
Modes
Privileged EXEC mode
Examples
The following example displays the LACP attributes for an Ethernet interface.
show port-security
Displays the configuration information related to port security.
Syntax
show port-security [ addresses | interface ethernet slot/port ]
Modes
Privileged EXEC mode
Output
The show port-security command displays the following information:
Examples
To display the port MAC security configuration details across ports on the device, enter the following
command:
device(conf-if-eth-3/2)# do show port-security
Secure MaxSecureAddr CurrentAddr StaticSec Violated Action Sticky
Port (count) (count) (count)
Eth 3/2 10 0 1 No Shutdown No
To display the statistics of the port MAC security configured for an interface, enter the following
command:
device(conf-if-eth-3/2)# do show port-security interface ethernet 3/2
Port Security : Enabled
Port Status : Up
Violation Mode : Shutdown
Violated : No
Sticky Enabled : No
Maximum MAC addresses : 10
Total MAC addresses : 0
Configured MAC addresses : 1
Last violation time :
Shutdown time (in Minutes) : 0
To list the secure MAC addresses configured on the device, enter the following command.
Syntax
show process cpu [ summary ] [ history ] [ top ] [ all-partitions ]
Parameters
summary
Displays a summary view of cpu usage.
history
Displays the history of CPU usage.
top
Displays current CPU utilization.
all-partitions
Displays a summary view of all partitions.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
For an explanation of process states, refer to the UNIX manual page for the ps command.
Examples
The following example displays a summary of all processes.
device# show process cpu summary
Realtime Statistics:
Total CPU Utilization: 0% (user procs:0%, system-kernel:0%, iowait:0%)
Load Average: One minute: 0.00; Five minutes: 0.03; Fifteen minutes: 0.01
Syntax
show process info
Modes
Privileged EXEC mode
Usage Guidelines
Pagination is not supported with this command. Use more in the terminal window to display the output
one page at a time.
Examples
device# show process info
PID CMD
2 kthreadd
3 \_ migration/0
4 \_ ksoftirqd/0
5 \_ watchdog/0
6 \_ migration/1
7 \_ ksoftirqd/1
8 \_ watchdog/1
9 \_ migration/2
10 \_ ksoftirqd/2
11 \_ watchdog/2
12 \_ migration/3
13 \_ ksoftirqd/3
14 \_ watchdog/3
15 \_ migration/4
16 \_ ksoftirqd/4
17 \_ watchdog/4
18 \_ migration/5
19 \_ ksoftirqd/5
20 \_ watchdog/5
21 \_ migration/6
22 \_ ksoftirqd/6
[Output truncated]
Syntax
show process memory [ summary ]
Parameters
summary
Displays a summary view of memory usage.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
Examples
To show memory usage information by individual processes:
Syntax
show qos cpu cfg slot slot_id [ burst | shaper | rate ]
Parameters
slot slot_id
Specifies a valid slot number. For devices that do not support line cards, specify 0.
burst
Specifies port and group traffic burst rates for IPv6 subnet rate limiting.
shaper
Specifies port and group traffic shaper rates for IPv6 subnet rate limiting.
rate
Specifies shaping rate for IPv6 subnet rate limiting.
Modes
Privileged EXEC mode
Usage Guidelines
IPv6 subnet rate limiting is configured by means of the ipv6 subnet-rate-limit command.
Examples
To display information about the CPU configuration.
To display information only about the IPv6 subnet rate-limiting traffic shaper configuration.
To display information only about the IPv6 subnet shaping rate configuration.
---------------------------------------------------------------------------------
Protocol 7f80 0 0 0 0 0
Management 7f81 1
IP Host 7f82 2 11907 173855778 724 845632
MC RPF Fail 7f83 3 0 0 0 0
MC LHR 7f84 4 0 0 0 0
Syntax
show qos cpu info
Modes
Privileged EXEC mode
Examples
device# show qos cpu info
Syntax
show qos flowcontrol interface { all | ethernet slot/port | port-channel
number }
Parameters
all
Displays the flow control information on all interfaces.
ethernet slot/port
Displays the flow control information on the specified interface.
port-channel number
Displays the flow control information on the interface for the specified port channel.
Modes
Privileged EXEC mode
Usage Guidelines
This command displays the flow control mode, generation (Tx) and reception (Rx) status, and Tx and Rx
PAUSE frame counts.
Examples
The following example displays the flow control information for all interfaces.
device# show qos flowcontrol interface all
Interface Ethernet 1/1
Mode Off
Interface Ethernet 1/2
Mode Off
Interface Ethernet 1/3
Mode Off
Interface Ethernet 1/4
Mode Off
...
Interface Ethernet 3/18
Mode 802.3x
TX RX TX Output Paused RX
Admin Admin Frames 512 BitTimes Frames
-----------------------------------------------
Off On 0 0
The following example displays the flow control information on a specific interface.
device# show qos flowcontrol interface ethernet 3/18
Interface Ethernet 3/18
Mode 802.3x
TX RX TX Output Paused RX
Admin Admin Frames 512 BitTimes Frames
-----------------------------------------------
Off On 0 0
Syntax
show qos interface all
Modes
Privileged EXEC mode.
Usage Guidelines
This command can produce pages of output.
Examples
To show QoS information for all interfaces use the following command.
...
TC: 0 1 2 3 4 5 6 7
------------------------------------------------------------------
Threshold: 0 0 0 0 0 0 0 0
Syntax
show qos interface ethernet slot/port
Parameters
slot/port
A specific Ethernet interface slot and port number.
Modes
Privileged EXEC mode.
Examples
To display the QoS configuration for a specific interface use the following command.
1 : 1/0 1/0 1/0 1/0 1/0 1/0 2/0 2/0 2/0 2/0
2 : 2/0 2/0 2/0 2/0 3/0 3/0 3/0 3/0 3/0 3/0
3 : 3/0 3/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0
4 : 5/0 5/0 5/0 5/0 5/0 5/0 5/0 5/0 6/0 6/0
5 : 6/0 6/0 6/0 6/0 6/0 6/0 7/0 7/0 7/0 7/0
6 : 7/0 7/0 7/0 7/0
Syntax
show qos interface port-channel port_channel_number
Parameters
port_channel_number
A specific port channel number.
Modes
Privileged EXEC mode.
Usage Guidelines
The insight interface port management module is on port-channel 1.
Examples
Follow this example to view information about the insight interface port channel.
0 : 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/0 1/0 1/0
1 : 1/0 1/0 1/0 1/0 1/0 1/0 2/0 2/0 2/0 2/0
2 : 2/0 2/0 2/0 2/0 3/0 3/0 3/0 3/0 3/0 3/0
3 : 3/0 3/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0
4 : 5/0 5/0 5/0 5/0 5/0 5/0 5/0 5/0 6/0 6/0
5 : 6/0 6/0 6/0 6/0 6/0 6/0 7/0 7/0 7/0 7/0
6 : 7/0 7/0 7/0 7/0
4 : 5/0 5/0 5/0 5/0 5/0 5/0 5/0 5/0 6/0 6/0
5 : 6/0 6/0 6/0 6/0 6/0 6/0 7/0 7/0 7/0 7/0
6 : 7/0 7/0 7/0 7/0
Follow this example to view information about a specific port channel interface.
3 : 3/0 3/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0
4 : 5/0 5/0 5/0 5/0 5/0 5/0 5/0 5/0 6/0 6/0
5 : 6/0 6/0 6/0 6/0 6/0 6/0 7/0 7/0 7/0 7/0
6 : 7/0 7/0 7/0 7/0
------------------------------------------------
0 : 0/0 0/0 0/0 0/0 0/0 0/0 0/0 0/0 1/0 1/0
1 : 1/0 1/0 1/0 1/0 1/0 1/0 2/0 2/0 2/0 2/0
2 : 2/0 2/0 2/0 2/0 3/0 3/0 3/0 3/0 3/0 3/0
3 : 3/0 3/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0
4 : 5/0 5/0 5/0 5/0 5/0 5/0 5/0 5/0 6/0 6/0
5 : 6/0 6/0 6/0 6/0 6/0 6/0 7/0 7/0 7/0 7/0
6 : 7/0 7/0 7/0 7/0
...<output truncated>
1 : 1/0 1/0 1/0 1/0 1/0 1/0 2/0 2/0 2/0 2/0
2 : 2/0 2/0 2/0 2/0 3/0 3/0 3/0 3/0 3/0 3/0
3 : 3/0 3/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0 4/0
4 : 5/0 5/0 5/0 5/0 5/0 5/0 5/0 5/0 6/0 6/0
5 : 6/0 6/0 6/0 6/0 6/0 6/0 7/0 7/0 7/0 7/0
6 : 7/0 7/0 7/0 7/0
Syntax
show qos interface ve ve_number
Parameters
ve_number
A specific Virtual Ethernet number.
Modes
Privileged EXEC mode.
Examples
Follow this example to view information about a specific VE interface.
6 : 07 07 07 07
Syntax
show qos maps cos-traffic-class
Modes
Privileged EXEC mode.
Examples
To display information on defined QoS CoS-to-traffic class mutation maps and where they are applied,
use this command.
Syntax
show qos maps dscp-cos
Modes
Privileged EXEC mode
Examples
To display information on defined QoS DSCP to CoS mutation maps and where they are applied, use
this command.
Syntax
show qos maps dscp-mutation [ map-name ]
Parameters
map-name
Displays the specified DSCP mutation map.
Modes
Privileged EXEC mode
Examples
To display information on defined QoS DSCP mutation maps and where they are applied, use this
command.
Syntax
show qos maps dscp-traffic-class [map-name]
Parameters
map-name
Name of the QoS DSCP-to-traffic-class map.
Modes
Privileged EXEC mode
Usage Guidelines
Note
This command is supported on devices based on the XGS chipset family. For a list of such
devices, see "Supported Hardware".
Examples
This example displays information on defined QoS DSCP to traffic class mutation maps and where they
are applied.
device# show qos maps dscp-traffic-class
Out-DSCP(DP=1): 00 08 13 24 32 43 48 56
Out-DSCP(DP=2): 00 00 00 00 00 00 00 00
Out-DSCP(DP=3): 00 00 00 00 00 00 00 00
Syntax
show qos maps traffic-class-cos
Modes
Privileged EXEC mode
Examples
To display information on defined QoS DSCP to traffic class to CoS mutation maps and where they are
applied, use this command.
Syntax
show qos-mpls maps dscp-exp
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
device# show qos-mpls maps dscp-exp
Syntax
show qos-mpls maps exp-dscp
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
device# show qos-mpls maps exp-dscp
Syntax
show qos-mpls maps exp-traffic-class
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
device# show qos-mpls maps exp-traffic-class
Syntax
show qos-mpls maps inexp-outexp
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
device# show qos-mpls maps inexp-outexp
Syntax
show qos-mpls maps traffic-class-exp
Modes
Privileged EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
device# show qos-mpls maps traffic-class-exp
Syntax
show qos tx-queue interface { ethernet slot/port }
Parameters
ethernet
Represents a valid, physical Ethernet interface.
slot
Specifies a valid slot number. The only valid value is 0.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Examples
This example displays the runtime egress queue state information retrieved from the data plane.
device# show qos tx-queue interface ethernet 0/1
Interface Ethernet 0/1
In-use Max TX Dropped TX
Dropped
TC Bytes Bytes Packets Packets Bytes
Bytes
------------------------------------------------------------------------------------------
-
0 0 748288 0 0
0 0
1 0 748288 35739153669 0
1133120185038 0
2 0 748288 0 0
0 0
3 0 748288 0 0
0 0
4 0 748288 0 0
0 0
5 0 748288 0 0
0 0
6 0 748288 0 0
0 0
7 0 748288 30715725 2 2765239372
164
show rmon
Displays the current RMON status on the device.
Syntax
show rmon [ alarms [ number ] [ brief ] | events [ number ] [ brief ] |
logs [ event_number ] | statistics [ number ] [ brief ] ]
Parameters
alarms
Specifies to display the RMON alarm table.
number
Specifies the alarm index identification number. Valid values range from 1 through 65535.
brief
Specifies to display a brief summary of the output.
events
Specifies to display the RMON events table.
number
Specifies the event index identification number. Valid values range from 1 through 65535.
brief
Specifies to display a brief summary of the output.
logs
Specifies to display the RMON log table.
event_number
Specifies the event log index identification number. Valid values range from 1 through 65535.
statistics
Specifies to display the statistics identification number.
number
Specifies the statistics identification number. Valid values range from 1 through 65535.
brief
Specifies a brief summary of the output.
Modes
Privileged EXEC mode
Examples
To display the RMON statistics:
device# show rmon statistics
event Index = 4
Description "My Description"
Event type Log & SnmpTrap
Event community name admin
Last Time Sent = 00:00:00
Owner admin
Syntax
show rmon history [ statistics | history_index ]
Parameters
statistics
Displays a more detailed synopsis.
history_index
Specifies the RMON history identification number. Valid values range from 1 through 65535.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display a synopsis of the statistics collected by the rmon event and rmon
alarm commands.
Examples
To display the RMON history:
device# show rmon history
show remote-attestation
Displays the status of Remote Attestation and the calculated boot-aggregate value.
Syntax
show remote-attestation [ status | boot-aggregate ]
Parameters
boot-aggregate
Displays the calculated boot aggregate for this SLX-OS device.
status
Displays details of the remote Keylime server used for remote attestation. This command also
displays the details of Keylime agent(local) details such as uuid, and agent-port.
Modes
Privileged EXEC mode
Examples
This example displays the boot aggregate.
device# show remote-attestation boot-aggregate
sha1:fcd94d739efd625fb774202de99961d9ed1ccdaf
Platform Availability
This command is only available on the Extreme 8720 and Extreme 8520 devices.
Syntax
show rollback checkpoint [ all | cp-name | summary ]
Parameters
all
Specifies all checkpoints created by the user.
cp-name
Specifies the name of a checkpoint.
summary
Specifies brief details.
Modes
Privileged EXEC mode
Usage Guidelines
The default is all if this is not specified.
Examples
This example displays summary information.
device# show rollback checkpoint summary
User checkpoint summary
-------------------------------
1) checkpoint_before_vlans :
Created by admin
Created at Thu Apr 5 08:10:55 2018
Size is 8912 bytes
Description: "Before VLAN configs“
2) default :
Created by admin
Created at Thu Apr 5 09:18:53 2018
Size is 8907 bytes
Description: "Default Configs"
root enable
Syntax
show rollback diff checkpoint cp-name [checkpoint cp-name ]
Parameters
cp-name
Specifies the name of the first checkpoint for comparison.
checkpointcp-name
Specifies the name of the second checkpoint for comparison.
Modes
Privileged EXEC mode
Usage Guidelines
Differences are noted by - (removed) and + (added).
The show rollback diff checkpoint cp-name command displays the differences between
the running configuration and the checkpoint configuration provided.
Examples
This example displays a comparison between checkpoints "default" and "test".
device# show rollback diff checkpoint default checkpoint test
interface Ethernet 1/10
- switchport port-security shutdown-time 10
- switchport trunk native-vlan 2
+ switchport port-security max 100
Syntax
show rollback feature-status
Modes
Privileged EXEC mode
Examples
This example displays configuration rollback status.
device# show rollback feature-status
Syntax
show rollback log [ errors ]
Parameters
errors
Specifies rollback errors, whether from the plugin or the backend.
Modes
Privileged EXEC mode
Usage Guidelines
The command and option display ongoing logs of a rollback operation that is in progress. Otherwise,
the logs of the last completed rollback are displayed.
Examples
This example displays errors.
device# show rollback log errors
event-handler ev1
action python-script show_interface.py
Error: flash://show_interface.py script for event handler ev1 could not be found or read.
Syntax
show rollback patch checkpoint cp-name
Parameters
cp-name
Specifies the name of a checkpoint.
Modes
Privileged EXEC mode
Examples
This example displays the configuration rollback patch between the running configuration and the
checkpoint named "chkpt1".
device# show rollback patch checkpoint chkpt1
Collecting Running-Config...
Generating Rollback Patch...
interface Ethernet 0/10
no switchport trunk native-vlan 7
no switchport trunk tag native-vlan
no switchport trunk allowed vlan add 1,3-10
interface Ve 10
ip address 10.10.10.10/24
shutdown
vlan 10
name VLAN100
Syntax
show rollback status { current | history }
Parameters
current
Specifies current rollback status.
history
Specifies the status of the last five rollbacks.
Modes
Privileged EXEC mode
Usage Guidelines
The current option displays information about the rollback when it is in process, such as the rollback
operation, checkpoint name, rollback status, and timestamp when rollback was issued. Status is
displayed as "In Progress" with all other fields updated except End Time.
The history option displays information about rollback execution status, such as who issued the
rollback, the checkpoint name, rollback status, timestamp when rollback was issued, and time taken for
rollback to complete.
Examples
This example displays current status.
device# show rollback status current
Operation : Rollback To Checkpoint
Checkpoint Name : vlan-config
Rollback done By : admin
Rollback Mode : best-effort
Start Time : Thu Apr 5 09:32:24 2018
Status : In-Progress
show route-map
Displays route-map configuration details.
Syntax
show route-map [ name ]
show route-map interface [ ethernet slot/port | port-channel index | ve
ve-number ]
Parameters
name
Specifies the name of the route-map.
interface
Specifies an interface.
ethernet slot/port
Specifies a physical interface.
port-channel index
Specifies a port-channel.
ve ve-number
Specifies a virtual Ethernet interface.
Modes
Privileged EXEC mode
Output
The show route-map command displays the following information:
Examples
The following example displays route-map details for all route-maps.
device# show route-map
Interface Ethernet 1/6
ip policy route-map route1
Syntax
show run router mpls cspg-group group_name [ from | link| node
[ ip_addr ] ] | subnet ip_addr/mask ]
Parameters
from ip_addr
Configures the CSPF group from the specified IP address.
link ip_addr
Configures the CSPF group from and to the specified IP address.
node ip_addr
Configures the CSPF group node IP address.
subnet ip_addr/mask
Configures the CSPF group subnet address.
Modes
EXEC mode
Usage Guidelines
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example displays the fate-sharing group configuration for all groups currently configured
on the device.
device# show run router mpls cspf-group gold
cspf-group test8
penalty 65535
node 10.7.7.3
node 10.7.7.8
show running-config
Displays the contents of the running configuration.
Syntax
show running-config
Parameters
Refer to the Usage Guidelines.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display the running configuration.
The show running-config option displays the global configuration and also the configuration on
all interfaces.
The show running-config interface options display only the configuration for the interfaces
specified.
Examples
The following command example displays the contents of the device running configuration.
device# show running-config
Syntax
show running-config aaa [ accounting [ commands | exec ] | authentication
[ login ] ]
Parameters
accounting
Configures Login or Command accounting
commands
Enable/Disable Command accounting
exec
Enable/Disable Login accounting
authentication
Configures preferred order of Authentication output modifiers
login
Configures the order of sources for login (default = ‘local’)
Modes
Privileged EXEC mode
Usage Guidelines
Refer to the aaa authentication command for a description of the displayed attributes.
Examples
To display the authentication mode:
device# show running-config aaa
aaa authentication radius local
aaa accounting exec default start-stop none
aaa accounting commands default start-stop none
Syntax
show running-config aaa accounting
Modes
Privileged EXEC mode
Usage Guidelines
Refer to the aaa authentication command for a description of the displayed attributes.
Examples
To displaying the authentication mode:
Syntax
show running-config aaa authorization
Modes
Privileged EXEC mode
Examples
The following example shows how to display AAA authorization status.
show running-config aaa authorization
Syntax
show running-config aaa authorization command
Modes
Privileged EXEC mode
Usage Guidelines
This command displays the current status for TACACS+ authorization of command privileges for the
user role. You must configure at least one TACACS+ server in order for this feature to function.
Examples
Example of the active status:
device# show running-config aaa authorization command
aaa command authorization tacacs+
Syntax
show running-config access-list overlay type vxlan { standard |
extended } [ overlay-vxlan-acl-name ]
Parameters
standard
Specifies one or all standard overlay VXLAN ACLs.
extended
Specifies one or all extended overlay VXLAN ACLs.
overlay-vxlan-acl-name
Specifies an ACL.
Modes
Privileged EXEC mode
Usage Guidelines
Overlay ACLs are supported only on devices based on the DNX chipset family. For a list of such devices,
see "Supported Hardware".
Examples
The following example displays the running config for an extended overlay ACL.
device# show running-config access-list overlay type vxlan extended overlay_vxlan_ext
overlay access-list type vxlan extended overlay_vxlan_ext
seq 10 permit dst-vtep-ip 10.1.1.1 src-vtep-ip any vni 5 native dst-ip any src-ip
100.1.1.1 dst-port any src-port 5555 count sflow (Active)
Syntax
show running-config arp
show running-config arp ip-address [ ethernet slot / port | ve ve-id ]
show running-config arp access-list
show running-config arp access-list arp-acl-name [ permit ip host
[ host-ip-address [ mac host [ host-mac-address ] ] ] ]
Parameters
ip-address
Specifies the IPv4 address of a static ARP.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
ve ve-id
Specifies a virtual ethernet (VE) interface.
access-list arp-acl-name
Specifies the name of an ARP ACL defined on the device.
permit ip host host-ip-address
Specifies rules that permit ARP messages from hosts specified by both IPv4 and MAC addresses.
host-ip-address
Specifies the IPv4 address.
mac host host-mac-address
Specifies the MAC address.
Modes
Privileged EXEC mode
Examples
The following example displays a sample run of the show running-config arp command.
device# show running-config arp
device# arp 12.1.1.2 0000.0000.0001 interface Ethernet 1/72
The following example displays a sample run of the show running-config arp access-list
option.
device# show running-config arp access-list
device# arp access-list acl1
permit ip host 13.1.1.2 mac host 0000.0000.0002
!
Syntax
show running-config control-plan ip subnet-rate-limit
Modes
Control plane configuration mode
Examples
The following example shows the configured CIR and CBS.
device# configure terminal
device(config)# control-plane
device(config-control-plane)# show running-config control-plane ip subnet-rate-limit
control-plane
ip subnet-rate-limit cir 220 cbs 20
Syntax
show running-config dpod [ slot/port ]
Command Default
Displays all port reservations on the local switch.
Parameters
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display port reservations for a specified port or for all ports on the local switch.
Examples
To display port reservations for all ports on the local switch:
To display port reservations on a switch that does not support the DPOD feature:
Syntax
show running-config event-handler [ event-handler-name ]
show running-config event-handler event-handler-name description
show running-config event-handler event-handler-name action
show running-config event-handler event-handler-name trigger [ trigger-
id [ raslog raslog-id [ pattern posix-ext-regex ] ] ]
Parameters
event-handler-name
Specifies the name of the event-handler profile. Valid values can have from 1 through 32
characters. The first character must be alphabetic.
action
Displays by Python script file-names.
description
Describes the event-handler profile. The string can be 1 through 128 characters in length.
trigger trigger-id
Specifies an event-handler trigger. When the trigger-condition occurs, a Python script is run.
raslog raslog-id
Specifies a RASlog message ID as the trigger.
pattern posix-ext-regex
Specifies a POSIX extended regular expression to search for a match within the specified RASlog
message ID. For examples, refer to the "trigger" topic.
Modes
Privileged EXEC mode
Output
The show running-config event-handler command displays the following information:
Examples
The following example displays the details of all triggers defined for a specified event-handler.
device# show running-config event-handler evh1 trigger
event-handler evh1
trigger 1 raslog NSM-1001
The following example displays the details of the action defined for a specified event-handler.
device# show running-config event-handler evh1 action
event-handler evh1
action python-script vlan.py
event-handler evh1
trigger 10 raslog NSM-1001
action python-script vlan.py
event-handler evh2
trigger 100 raslog NSM-1003
action python-script vlan.py
!
Syntax
show running-config ip access-list [ { standard | extended }
[ ACL_name ] ]
Parameters
standard
Specifies the standard ACL type.
extended
Specifies the extended ACL type.
ACL_name
Specifies the ACL name.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Not specifying standard or extended displays a list of all IPv4 ACLs defined on the switch.
To display details of IPv4 ACLs bound to interfaces, use the show access-list ip command.
Examples
The following example displays the IPv4 ACLs defined on the switch.
device# show running-config ip access-list
Syntax
show running-config ip receive [ access-group [ acl-name [ sequence ] ] ]
Parameters
access-group
Specifies IPv4 ACLs applied at device-level.
acl-name
Specifies an IPv4 standard or extended ACL.
sequence
Displays the sequence number. For devices with only one rACL applied, the default sequence
number is 10.
Modes
Privileged EXEC mode
Usage Guidelines
Output
The show running-config ip receive command displays the following information:
Examples
The following example displays the sequence numbers for two rACLs applied to a device.
device# show running-config ip receive access-group ext1 sequence
ip receive access-group ext1 sequence 10
Syntax
show running-config ipv6 [ access-list [ extended | standard ] ipv6-acl-
name seq sequence-number ]
show running-config ipv6 [ import routes ]
show running-config ipv6 [ nd [ global-suppress-ra | ra-dns-server | ra-
domain-name ]]
show running-config ipv6 [ prefix-list [ ge | le ] prefix-length ]
show running-config ipv6 [ protocol [ vrrp | vrrp-extended ]
show running-config ipv6 [ receive access-group ]
show running-config ipv6 [ route ]
show running-config ipv6 [ router ospf [ vrf ]]
Parameters
access-list
Specifies the access-control list (ACL)
extended
Specifies the extended IP ACL.
standard
Specifies the standard IP ACL.
ipv6-acl-name
The IPv6 ACL name.
seq sequence-number
Specifies the sequence number.
import routes
Specifies import IPv6 routes.
nd
Displays neighbor discovery commands.
global-suppress-ra
Sets the suppress-ra option globally .
ra-dns-server
Sets the global DNS server option applied on all ND6.
ra-domain-name
Set the global domain name option that applied on all ND6 interfaces.
prefix-list
Modes
Privileged EXEC mode
Examples
The following is an example of the show running-config ipv6 command output.
device# show running-config ipv6
ipv6 route 3063:6363::/64 fe80::52eb:1aff:fe97:cf51 ve 4050
ipv6 nd ra-dns-server 2000:1234:122:ffff::ffee
ipv6 nd ra-dns-server 3500:35:0:35::1
ipv6 nd ra-domain-name extreme.com
ipv6 nd ra-domain-name user.co.in
ipv6 nd ra-domain-name netiron.com
Syntax
show running-config ipv6 access-list [ { standard | extended }
[ ACL_name ] ]
Parameters
standard
Specifies the standard ACL type.
extended
Specifies the extended ACL type.
ACL_name
Specifies the ACL name.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Not specifying standard or extended displays a list of all IPv6 ACLs defined on the switch.
To display details of all IPv6 ACLs bound to interfaces, use the show access-list ipv6 command.
Examples
The following example displays all standard IPv6 ACLs defined on the switch:
device# show running-config ipv6 access-list standard
ipv6 access-list standard distList
seq 10 deny 2001:125:132:35::/64
seq 20 deny 2001:54:131::/64
seq 30 deny 2001:5409:2004::/64
seq 40 permit any
!
ipv6 access-list standard ipv6_acl_std_1
seq 10 deny 2001:2001::/64 count log
Syntax
show running-config keychain chain-name
Parameters
chain-name
Specifies the name of the key chain for which you want to view configuration details.
Modes
Global configuration mode
Examples
The following example shows typical output for the command.
device(config)# show running-config keychain child
keychain child
accept-tolerance 500
key 1
key-string $9$XutLBELmbQ765dsLycIP/A== encryption-level 4
accept-lifetime local true 11:49:11|11/09/2017 11:45:16|11/10/2017
key-algorithm HMAC-SHA-256
!
Syntax
show running-config lag hash [ bos ] [ hdr-count ] [ hdr-start ]
[ normalize] [ pwctrlword ] [ rotate ] [ speculate-mpls ] [ srcport ]
Parameters
bos
(DNX devices only) Ignore the entire MPLS label stack and pick only the BOS label for hashing.
hdr-count count
Specifies the number of headers to be considered for LAG hashing. Values range from 1 through
3. The default is 1.
hdr-start
Specifies where to start picking headers for the key generation.
normalize
(DNX devices only) Configures using the same hash in both directions. The default is disabled.
pwctrlword
(DNX devices only) Include or exclude the PW control word in hashing.
rotate rotate-number
(DNX devices only) Specify hashing randomness. Values range from 0 through 15. The default is
3.
speculate-mpls
(DNX devices only) Enable MPLS speculate or Ethernet/IP.
srcport
Includes the source port in the hashing configuration. The default is not to include it.
Modes
Privileged EXEC mode
Usage Guidelines
To display all configured values (including defaults), enter the show port-channel load-
balance command.
Examples
The following example displays the output of the basic show running-config lag hash
command.
device# show running-config lag hash
lag hash hdr-start term
lag hash hdr-count 2
lag hash srcport
Syntax
show running-config ldap-server [ host ipaddr | host-name ]
Parameters
host
Identifies the IPv4 address of the host.
ipaddress
IPv4 address of the host.
host-name
Name of the host.
Modes
Privileged EXEC mode
Usage Guidelines
LDAP server configuration is placed at the beginning of the running-config and is part of the global
configuration of the device. No entry is shown in the running-config when set to default.
Examples
device# show running-config ldap-server host 10.24.65.6
ldap-server host 10.24.65.6 use-vrf mgmt-vrf
port 3890 retries 3 timeout 8 basedn security.extreme.com
device#
Syntax
show running-config mac access-list [ { standard | extended }
[ ACL_name ] ]
Parameters
standard
Specifies the standard ACL type.
extended
Specifies the extended ACL type.
ACL_name
Specifies the ACL name.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Not specifying standard or extended displays a list of all MAC ACLs defined on the switch.
To display details of all MAC ACLs bound to interfaces, use the show access-list mac command.
Examples
The following example displays all MAC ACLs defined on the switch.
device# show running-config mac access-list
mac access-list standard stdmacaclin
seq 11 permit 1111.1112.1113 7777.7777.7777 count log
seq 12 permit 1111.1112.1114 7777.7777.7777 count log
Syntax
show running-config password-attributes [ admin-lockout | history |
login-notify-duration | max-retry | min-length | repeat | sequence]
show running-config password-attributes character-restriction [ lower |
numeric | special-char | upper ]
Parameters
admin-lockout
Displays lockout for admin role accounts.
history
Specifies the number of old passwords against which a newly configured password is to be
checked.
login-notify-duration
Specifies the duration in hours for which the number of last successful attempts should be
notified to administrator when logging in. Use value 0 to disable the notification.
max-retry
Displays the number of failed password logins permitted before a user is locked out. Values
range from 0 through 16 attempted logins. The default value is 0.
min-length
Displays the minimum length of the password. Valid values range from 8 through 32 characters.
The default is 8 characters.
repeat
Specifies the maximum number (n-1) of consecutive and repetitive characters allowed in a newly
configured password.
sequence
Specifies the maximum number (n-1) of consecutive and sequential characters allowed in both
forward and reverse direction in a newly configured password.
character-restriction
Displays the restriction on various types of characters.
lower
Displays the minimum number of lowercase alphabetic characters that must occur in the
password. Values range from 0 through 32 characters. The default value is 0.
numeric
Displays the minimum number of numeric characters that must occur in the password. Values
range from 0 through 32 characters. The default is 0.
special-char
Displays the number of punctuation characters that must occur in the password. All printable,
nonalphanumeric punctuation characters, except colon (:) are allowed. Values range from 0
through 32 characters. The default value is 0.
upper
Displays the minimum number of uppercase alphabetic characters that must occur in the
password. Values range from 0 through 32 characters. The default value is 0.
Modes
Privileged EXEC mode
Usage Guidelines
The attributes are not displayed when they hold default values.
Examples
The following example displays all global password attributes.
device# show running-config password-attributes
password-attributes max-retry 4
password-attributes character-restriction upper 1
password-attributes character-restriction lower 2
password-attributes character-restriction numeric 1
password-attributes character-restriction special-char 1
password-attributes history 3
password-attributes login-modify-duration 1
password-attributes repeat 1
password-attributes sequence 1
Syntax
show running-config radius-server host { ip-address | hostname }
Parameters
host
Identifies the RADIUS server by host name or IP address.
hostname
Specifies the host name of the RADIUS server.
ip-address
Specifies the IP address of the RADIUS server. IPv4 and IPv6 are supported.
Modes
Privileged EXEC mode
Examples
device# show running-config radius-server host 10.38.37.180
Syntax
show running-config rmon [ alarm | event ]
Parameters
alarm
Displays the Remote Monitor alarm configuration.
event
Displays the Remote Monitor event configuration
Modes
Privileged EXEC mode
Syntax
show running-config role [ name role_name [ desc ] ]
Parameters
name role_name
Displays roles defined for users.
desc
Displays role descriptions.
Modes
Privileged EXEC mode
Examples
The following example displays all roles configured on the device.
device# show running-config role
Syntax
show running-config rule [ index ]
show running-config rule index { action | command command_name |
operation | role }
show running-config rule { action { reject | accept } | command
command_name | operation { read-only | read-write } | role role-
name }
Parameters
index
Displays the rule with the specified index number. Values range from 1 through 512.
action reject | accept
Following the index parameter, indicates whether reject or accept is specified for that
rule. If the index parameter is not specified, displays all rules with the specified action.
command command_name
Displays rule configuration for the specified command. To display a list of supported commands,
type a question mark (?). This list varies according to whether or not you specify a rule index.
operation read-only | read-write
Following the index parameter, indicates whether read-only or read-write is specified
for that rule. If the index parameter is not specified, displays all rules with the specified
operation.
role role-name
Displays rule configuration for the specified role.
Modes
Privileged EXEC mode
Examples
The following example displays the configured roles and their rules.
device# show running-config rule
rule 30
action accept operation read-write role NetworkSecurityAdmin command role
Syntax
show running-config ssh
Modes
Privileged EXEC mode
This example shows common output for the command.
device# show running-config ssh
ssh server key rsa 2048
ssh server key ecdsa 256
ssh server key dsa
ssh server use-vrf default-vrf
ssh server use-vrf mgmt-vrf
device#
Syntax
show running-config ssh server
Modes
Privileged EXEC mode
Usage Guidelines
SSH server configuration is placed at the beginning of the running-config and is part of the global
configuration of the device. By default, the SSH server listens on mgmt-vrf and default-vrf.
Output
The show running-config ssh server command displays the following information:
Examples
This example shows output when the SSH service is shutdown on the mgmt-vrf.
device# show running-config ssh server
ssh server key rsa 2048
ssh server key ecdsa 256
ssh server key dsa
ssh server use-vrf default-vrf
ssh server use-vrf mgmt-vrf shutdown
device#
Syntax
show running-config ssh server key-exchange
Modes
Privileged EXEC mode
Examples
Typical command output:
device# show running-config ssh server key-exchange
ssh server key-exchange dh-group-14
Syntax
show running-config system-monitor [ fan | power | temp | cid-card |
compact-flash | MM | LineCard | SFM ]
Parameters
fan
Displays the threshold and alert setting for the FAN component.
power
Displays the threshold and alert setting for the power component.
temp
Displays the threshold for the temperature sensor component.
cid-card
Displays the threshold for the CID card component.
compact-flash
Displays the threshold for the compact flash device.
MM
Displays the threshold for the management module.
LineCard
Displays the threshold for the line card.
SFM
Displays the threshold for the switch fabric module.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local switch.
Examples
This example shows typical results. Results vary by device.
device# show running-config system-monitor
system-monitor fan threshold marginal-threshold 1 down-threshold 2
system-monitor fan alert state removed action raslog
system-monitor power threshold marginal-threshold 2 down-threshold 3
system-monitor power alert state removed action raslog
system-monitor temp threshold marginal-threshold 1 down-threshold 2
Syntax
show running-config telemetry collector [ collector-name ]
Modes
Privileged EXEC mode
Parameters
collector-name
Specifies a telemetry collector.
Usage Guidelines
The output includes the settings for the currently configured collectors.
Examples
The following example is the basic command.
device# show running-config telemetry collector
telemetry collector <collector-profile-1>
ip <ipv4address1> port <portNum>
profile system-profile default_system_utilization_statistics
profile interface-profile default_interface_statistics
use-vrf mgmt-vrf
encoding json
activate
!
Syntax
show running-config telemetry profile [ enhanced-queue-discard-pkts |
enhanced-queue-max-queue-depth | queue ]
Modes
Privileged EXEC mode
Parameters
enhanced-queue-discard-pkts
Displays a subset of the data highlighting discarded packet information.
enhanced-queue-max-queue-depth
Displays a subset of the data highlighting maximum queue depth information.
queue
Displays the field configuration information for the current telemetry profile queue.
Usage Guidelines
The output includes all default profiles and any custom defined telemetry profiles.
Output
The show running-config telemetry profile command displays the following information:
Examples
Typical command example.
device# show running-config telemetry profile
telemetry profile system-utilization default_system_utilization_statistics
interval 60
add total-system-memory
add total-used-memory
…
add uptime
telemetry profile interface default_interface_statistics
interval 30
interface 0/1-20
add out-pkts
add in-pkts
…
add out-discards
add in-discards
!
Syntax
show running-config telemetry profile [ mpls-traffic-lsp | mpls-traffic-
bypass | mpls-traffic-fec ]
Parameters
mpls-traffic-lsp
This profile captures the summary of Out-Bytes and Out-Packets for MPLS RSVP LSPs at Ingress.
mpls-traffic-bypass
This profile captures the summary of Out-Bytes and Out-Packets for the MPLS RSVP Bypass
LSPs at Ingress.
mpls-traffic-fec
This profile captures the summary of Out-Bytes and Out-Packets for the specified MPLS LDP
FEC.
Modes
Privileged EXEC mode
Usage Guidelines
The MPLS profile types are supported only on SLX 9540 and SLX 9640 devices.
The attributes used to gather the MPLS traffic statistics for the mpls-traffic-lsp, mpls-traffic-bypass, and
mpls-traffic-fec type profiles are:
• interval
• out-packets
• out-bytes
Examples
In the following examples, default_mpls_traffic_lsp_statistics, default_mpls_traffic_bypass_statistics,
and default_mpls_traffic_fec_statistics are the default profiles that are already present in the system.
add out-packets
add out-bytes
Syntax
show running-config telemetry profile [ enhanced-queue-discard-pkts |
enhanced-queue-max-queue-depth | queue ]
Parameters
enhanced-queue-discard-pkts
This profile captures the summary of 32 queues having most number of packets discarded in
descending order of the packet discards observed per device.
enhanced-queue-max-queue-depth
This profile captures the summary of 32 queues reaching the maximum max-queue-size in
descending order of the max-queue-size observed per device.
queue
This profile captures the overall queue statistics per device in the system.
Modes
Privileged EXEC mode
Usage Guidelines
The queue profile types are supported only on SLX 9540 and SLX 9640 devices.
• current-queue-size
• max-queue-depth-size
Examples
Example of the attributes configured for the enhanced-queue-discard-pkts profile.
device# show running-config telemetry profile enhanced-queue-discard-pkts
telemetry profile enhanced-queue-discard-pkts
default_enhanced_queue_discard_pkts_statistics
interval 240
interface-range 0/1-2,0/3:1-2
add discard-pkts
Syntax
show running-config telemetry server [ use-vrf ]
Parameters
use-vrf
Displays all VRF configurations. By default, only the default mgmt-vrf is displayed.
Modes
Privileged EXEC mode
Usage Guidelines
The output displays the current configuration for the telemetry server.
Examples
Typical command example.
kdevice# show running-config telemetry server
telemetry server use-vrf mgmt-vrf
transport tcp
port 50051
!
Syntax
show running-config username [ username ] [ access-time ] [ desc ]
[ enable ] [ encryption-level ] [ expire ] [ password ] [ role ]
Parameters
username
Displays the configuration of a specified username. The maximum number of characters is 40.
access-time
Displays access-time configuration.
desc
Displays the description of the user configuration.
enable
Displays the account enablement status.
encryption-level
Password encryption level. Valid values are 0, 7, and 10. The default is 0.
expire
Date until the password remains valid in YYYY-MM-DD format. Valid year values range from 1902
through 2037. By default, passwords do not expire.
password
Account password.
role
The role associated with the account.
Modes
Privileged EXEC mode
Usage Guidelines
To display details for one user only, specify username . Otherwise, this command displays all user
accounts on the device.
Examples
The following example displays the user accounts on the device.
device# show running-config username
The following example displays the enabled status for a specific user account.
device# show running-config username admin enable
show sflow
Displays sFlow configuration information and statistics.
Syntax
show sflow {interface | all}
Command Default
sFlow is disabled on all interfaces.
Parameters
all
Displays all sFlow information and statistics.
interface
Displays sFlow information for an Ethernet interface.
Modes
Privileged EXEC mode
Examples
The following example displays sFlow information.
Syntax
show span path session session-number
Parameters
session-number
Specifies the SPAN session.
Modes
Privileged EXEC mode
Examples
The following example displays the SPAN path information.
Session :1
Path :Eth 0/10 -> Eth 0/1 (ISL-exit port) -> Eth 0/16
show spanning-tree
Displays Spanning Tree Protocol (STP) information.
Syntax
show spanning-tree [ brief | interface { ethernet slot/port | port-
channel port_channel_number } | pvst | mst [ brief | detail |
instance instance_id | interface ] mst-config | vlan vlan_id ]
Parameters
brief
Display brief spanning tree information.
interface
Display iinformation about the spanning tree configuration on an interface.
ethernet slot/port
Display spanning tree information about a specific Ethernet interface.
port-channel port_channel_number
Display spanning tree information about a port channel interface.
pvst
Display PVST+ information.
mst
Display MSTP information.
detail
Display detailed MSTP tree information.
instance instance_id
Display MSTP information about a specivic instance.
mst-config
Display MSTP region configuration information.
vlan vlan_id
Display spanning tree information about a specific VLAN.
Modes
Privileged EXEC mode.
Usage Guidelines
Note
Extreme Networks supports the PVST+ and R-PVST+ protocols. The PVST and R-PVST
protocols are proprietary to Cisco and are not supported.
Examples
To display spanning tree information:
Syntax
show ssh client status
Modes
Privileged EXEC mode
Examples
This example shows the status when the SSH server is enabled.
device# show ssh client status
SSH Client Cipher: aes128-cbc,aes192-cbc
SSH Client Mac : hmac-sha1,hmac-sha1-96,hmac-md5
SSH Client Key Exchange Algorithm: diffie-hellman-group-exchange-sha256
device#
Syntax
show ssh server status
Modes
Privileged EXEC mode
Examples
This example shows the output of the command from privileged EXEC mode.
device# show ssh server status
SSH Server Rekey Volume: 1024
SSH Server Auth Tries: 6
SSH Server Login Timeout: 120
VRF-Name: default-vrf Status: Enabled
VRF-Name: mgmt-vrf Status: Enabled
device#
This example shows the output of the command from global configuration mode.
device# configure terminal
device(config)# do show ssh server status
SSH Server Rekey Volume: 1024
SSH Server Auth Tries: 6
SSH Server Login Timeout: 120
VRF-Name: mgmt-vrf Status: Enabled
VRF-Name: default-vrf Status: Enabled
show startup-config
Displays the contents of the startup configuration.
Syntax
show startup-config
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
Examples
The following example displays the contents of the startup configuration file.
device# show startup-config
Syntax
show statistics access-list { ip | ipv6 | mac } acl-name { in | out }
show statistics access-list interface { ethernet slot / port | port-
channel index | ve vlan_id | vlan vlan_id } { in | out }
show statistics access-list interface management mgmt-id in
show statistics access-list { ip | ipv6 } acl-name interface [ ethernet
slot / port | port-channel index | ve vlan_id ] { in | out }
show statistics access-list { ip | ipv6 } name interface management mgmt-
id in
show statistics access-list mac acl-name interface [ ethernet slot / port
| port-channel index | vlan vlan_id ] { in | out }
show statistics access-list receive { ip | ipv6 } acl-name
show statistics access-list global-subnet-broadcast ip acl-name
show statistics access-list subnet-broadcast ip acl-name [ interface
{ ethernet slot / port | ve vlan-id } ]
Parameters
interface
Filter by interface.
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
port-channel index
Specifies a port-channel interface.
ve vlan_id
Specifies a virtual Ethernet (VE) interface.
vlan vlan_id
Specifies a VLAN interface.
management mgmt-id
Specifies the management interface. The only supported value is 0.
in | out
Modes
Privileged EXEC mode
Usage Guidelines
You can show statistics for a specific ACL or only for that ACL on a specific interface. You can display
statistical information for all ACLs bound to a device physical or management interface, VLAN or VE.
You can display statistical information for IPv4 or IPv6 receive-path ACLs. You can display statistical
information for IP broadcast ACLs (bACLs).
Statistics are displayed only for rules that contain the count keyword.
When ACLs of multiple types are applied to an interface, for multiple matches the counter is
incremented only for the higher priority match. Processing priority is as follows: rACLs > PBR > Layer 3
ACLs > Layer 2 ACLs.
Output
The show statistics access-list command displays the following information:
Examples
The following example displays inbound ACL statistics for a named IPv4 ACL.
device# show statistics access-list ip l3ext in
ip access-list l3ext Ethernet 1/8 in
seq 76 deny ip 10.10.75.10 0.0.0.0 any count log (795239 frames)
The following example displays inbound ACL statistics for a specific interface. The ACL named ipv6-std-
acl is applied on interface 4/1 to filter incoming routed traffic only.
device# show statistics access-list interface ethernet 4/1 in
ipv6 routed access-list ipv6-std-acl on Ethernet 4/1 at Ingress (From User)
seq 10 permit host 0:1::1
seq 20 deny 0:2::/64
seq 30 deny any count (100 frames)
The following example displays inbound statistics for all ACLs bound to a specific VE interface.
device# show statistics access-list interface ve 3010 in
ipv6 access-list ip_acl_3 on Ve 3010 at Ingress (From User)
seq 10 deny ipv6 2001:3010:131:35::/64 2001:1001:1234:1::/64 count (0 frames)
seq 20 permit ipv6 2001:3010:131:35::/64 2001:3001:1234:1::/64
The following example displays inbound statistics for ACLs on the management interface.
device# show statistics access-list interface management 0 in
ip access-list mgmt-acl on Management 0 at Ingress (From User)
seq 1 deny tcp host 1.1.1.1 any count (12854 frames)
seq 2 deny udp host 2.2.2.2 any count (94 frames)
seq 3 permit tcp any any
seq 4 permit udp any any
This example displays statistics for packets that meet the permit and deny rules that are configured for
control plane protection.
device# show statistics access-list receive ip ip-ssh
ip access-list extended ip-ssh
seq 5 deny tcp any 14.14.14.14 0.0.0.0 eq 22 count (25 frames)
seq 10 permit tcp 10.10.10.10 0.0.0.255 any eq 22 count (26 frames)
seq 20 permit tcp 11.11.11.11 0.0.0.255 any eq 22 count (26 frames)
seq 100 deny tcp any any eq 22 count (26 frames)
The following example displays an ACL definition that supports filtering non-fragmented packets.
device# show statistics access-list interface ethernet 0/7 in
ip access-list new_acl on Ethernet 0/7 at Ingress (From User)
seq 10 permit ip any any non-fragment count (0 frames)
The following example displays an ACL definition that supports filtering fragmented packets.
device# show statistics access-list interface ethernet 0/7 in
ip access-list test on Ethernet 0/8 at Ingress (From User)
seq 10 permit ip any any fragment
The following example displays an ACL definition that supports flow based ingress miroring.
device# show statistics access-list interface ethernet 0/2 in
ip access-list mac1 on Ethernet 0/2 at Ingress (From User)
The following example displays an ACL definition that supports flow based egress miroring.
device# show statistics access-list interface ethernet 0/1 out
ip access-list mac1 on Ethernet 0/1 at Egress (From User)
seq 10 permit any host 1111.2222.3333 count mirror (0 frames)
seq 20 permit host 4444.5555.6666 any count (0 frames)
Syntax
show statistics access-list overlay type vxlan acl-name
Parameters
acl-name
Specifies an overlay VXLAN ACL.
Modes
Privileged EXEC mode
Usage Guidelines
Overlay ACLs are not supported on SLX 9150 or SLX 9250 devices.
Examples
The following example displays statistics for a specific overlay ACL.
device# show statistics access-list overlay type vxlan abc_ext
Number of Rules: 2
seq 1000 permit dst-vtep-ip-host 200.1.1.1 src-vtep-ip-host 150.1.1.1 vni 1 vni-mask 0
redirect Ethernet 2/65 sflow count 0(pkts)/0(bytes)
seq 1010 permit dst-vtep-ip-host 200.1.1.2 src-vtep-ip-host 150.1.1.2 vni 2 vni-mask 0
redirect Ethernet 2/19 sflow count 44024773(pkts)/52829727600(bytes)
Syntax
show statistics bridge-domain bd-id
Parameters
bd-id
The bridge domain ID.
Modes
Privileged EXEC mode
Usage Guidelines
Enter the show statistics bridge-domain bd- id command to view the statistics for a specific
bridge domain.
Output
The show statistics bridge-domain command displays the following information:
Field Description
Interface The interface whose counter statistics are displayed.
RxPkts The number of packets received at the specified interface.
RxBytes The number of bytes received at the specified interface.
TxPkts The number of packets transmitted from the specified interface.
TxBytes The number of bytes transmitted from the specified interface.
Examples
The following example displays statistics for all logical interfaces in all bridge domains.
TxBytes
eth 1/6.400 821729 821729 95940360 95940360
eth 1/21.100 8884 8855 9684 9955
po 2.40 884484 885855 95969584 95484555
The following example displays statistics for all logical interfaces in the bridge domain 1.
Syntax
show statistics vlan vlan id
Parameters
vlan ID
The specific VLAN ID.
Modes
Privileged EXEC mode
Usage Guidelines
Enter the show statistics vlan vlan- id command to view the statistics for all ports and port
channels on a specific VLAN.
Output
The show statistics vlan command displays the following information:
Field Description
Interface The interface whose counter statistics are displayed.
RxPkts The number of packets received at the specified port.
RxBytes The number of bytes received at the specified port.
TxPkts The number of packets transmitted from the specified port.
TxBytes The number of bytes transmitted from the specified port.
Examples
The following example displays statistics for all ports and port channels on configured VLANs.
Vlan 10 Statistics
Interface RxPkts RxBytes TxPkts TxBytes
eth 1/1 821729 821729 95940360 95940360
eth 1/2 884484 885855 95969584 95484555
po 1 8884 8855 9684 9955
Vlan 20 Statistics
Interface RxPkts RxBytes TxPkts TxBytes
eth 1/6 821729 821729 95940360 95940360
The following example displays statistics for all ports and port channels in the VLAN 10.
Vlan 10 Statistics
Interface RxPkts RxBytes TxPkts TxBytes
eth 1/1 821729 821729 95940360 95940360
eth 1/2 884484 885855 95969584 95484555
po 1 8884 8855 9684 9955
Syntax
show statistics vpn vrf vrf-id
Modes
Privileged EXEC mode
Output
The show statistics vpn command displays the following information:
Examples
This example displays the VPN statistic for a VRF.
device# show statistics vpn
Output:
VRF Name Tnl In-Pkt Tnl Out-Pkt
red 0 0
show storm-control
Displays all BUM (broadcast, unknown unicast and multicast)-related information in the system.
Syntax
show storm-control [ broadcast | multicast | unknown-unicast | interface
ethernet slot/port | system ]
Parameters
storm-control
Displays all BUM-related information in the system.
broadcast
Displays all BUM-related information in the system for the broadcast traffic type.
multicast
Displays all BUM-related information in the system for the multicast traffic type.
unknown-unicast
Displays all BUM-related information in the system for the unknown-unicast traffic type.
interface ethernet slot/port
Displays all BUM-related information in the system for the specified interface.
system
Displays the global storm-control configured rate for the BUM traffic type on the device.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display BUM storm-control-related configuration for the entire system, for
specified traffic types, for specified interfaces, or for specified traffic types on a specified interface or
globally on the device.
Examples
This example displays storm control information for broadcast traffic on an Ethernet interface.
device# show storm-control broadcast interface ethernet 2/1
This example displays storm control information for all traffic on an Ethernet interface.
device# show storm-control interface ethernet 2/1
Interface Type Rate (bps) Operational Rate (bps) Conformed
Violated Total
Et 2/1 broadcast 100000 <value> 12500000000 12500000000
25000000000
Et 2/1 unknown-unicast 100000 <value> 12500000000 12500000000
25000000000
Et 2/1 multicast 100000 <value> 12500000000 12500000000
25000000000
This example displays storm control information for all BUM traffic configured globally on the device
and specific interfaces.
device# show storm-control
Interface Type Rate (bps) Operational Rate (bps) Conformed
Violated Total
System broadcast 100000 <value> 0 0 0
System multicast 8000000000 <value> 0 0 0
Et 2/2 broadcast 100000 <value> 12500000000 12500000000
250000000000
This example displays storm control information for all BUM traffic configured globally on the device.
device# show storm-control system
Interface Type Rate (bps) Operational Rate (bps) Conformed
Violated Total
System broadcast 100000 <value> 0 0 0
System multicast 8000000000 <value> 0 0 0
show support
Displays a list of core files on the device.
Syntax
show support
Command Default
Displays information for the local device.
Modes
Privileged EXEC mode
Usage Guidelines
This command is supported only on the local device.
Pagination is not supported with this command. Use the More option to display the output one page at
a time.
Examples
To display the core files:
Syntax
show system maintenance
Modes
Privileged EXEC mode
Usage Guidelines
Maintenance operations such as software upgrade, SFP replacement, cable replacement, and node
replacement require the device to be shut down, resulting in traffic disruption even if alternative paths
are available. Maintenance mode provides graceful traffic diversion from the maintenance mode node,
helping to minimize traffic loss during such planned operations.
Use this command to show the status of maintenance mode, stage information, and the configured time
to enter and exit maintenance mode.
Examples
The following example shows sample output of the command.
device# show system maintenance
Syntax
show system monitor tm {delete-packets | discard-packets | discard-voq-
packets}
Parameters
delete-packets
Displays the monitoring configuration of the TM device deleted packets.
discard-packets
Displays the monitoring configuration of the TM device discarded packets.
discard-voq-packets
Displays the monitoring configuration of the VOQ discarded packets.
Modes
Privileged EXEC
Output
The show system monitor tm command displays the following information:
Examples
The following example displays the monitoring configuration of the VOQ discarded packets.
device# show system monitor tm discard-voq-packet
Discard VOQ packet count monitoring configuration:
Logging-interval : 60 minutes
Threshold : 10 packets
show tech-support
Displays the technical support data using the set of SLX CLI and Linux commands.
Syntax
show tech-support
Usage Guidelines
The output of the show tech-support command is extensive. The information is displayed on the
terminal in a telnet/SSH session. In the console session, the output of the command is saved to a file
rather than displayed on the console due to the time required to display the results. The output is saved
to the file "flash://SLX_show_techsupport.txt" where "SLX" is the hostname of the switch.
Output
The show tech-support command displays the technical support data using the following
commands.
show arp
show bfd
show bfd neighbors vrf all
show bfd neighbors vrf all details
show bridge-domain
show bridge-domain brief
show buffmgr stats slot
show chassis
show clock
show cluster
show cluster member bridge-domain
show cluster member vlan
show environment fan
show environment history
show environment power
show environment sensor
show environment temp
show firmwaredownloadhistory
show firmwaredownloadstatus
show hardware profile current
show hw route-info
show interface
show interface stats brief
show interface status
show inventory
show ip bgp routes all-vrfs
show ip dhcp relay address
show ip dhcp relay statistics
show ip igmp groups detail
show ip igmp interface
show ip igmp snooping
show ip igmp snooping mrouter
show ip interface brief
show ip multicast snooping
show ip multicast snooping mcache
show ip pim bsr
show ip pim group
show ip pim interface
show ip pim mcache
Examples
The following example shows the output of the command when executed from the console.
device# show tech-support
%INFO: The output to the console is slow. It is saved to flash://
<hostname>_show_techsupport.txt
device#
The following example shows the output of the command in a telnet/ssh session as displayed on the
terminal, and is truncated below for brevity.
device# show tech-support
********************************************************
SLXCLI "show clock"
********************************************************
2019-02-18 17:16:31 Etc/GMT
********************************************************
SLXCLI "show version"
********************************************************
SLX-OS Operating System Version: 19.1.00
Copyright (c) 1995-2019 Extreme Networks, Inc.
Firmware name: 19.1.00d
Build Time: 21:15:15 Feb 16, 2019
Install Time: 12:20:19 Feb 18, 2019
Kernel: 4.14.67
Control Processor: GenuineIntel
Memory Size: SLXVM: 23916 MB System Total: 32079 MB
System Uptime: 0days 4hrs 52mins 22secs
Name Primary/Secondary Versions
------------------------------------------
SLX-OS 19.1.00d
19.1.00d
…
Syntax
show telemetry client-cert
Modes
Privileged EXEC mode
Usage Guidelines
There is no display if there are no certificates configured.
Examples
Typical command example.
device# show telemetry client-cert
-----BEGIN CERTIFICATE-----
MIIC2jCCAcICAQEwDQYJKoZIhvcNAQEFBQAwMzELMAkGA1UEBhMCQ0ExEDAOBgNV
BAoMB0Jyb2NhZGUxEjAQBgNVBAMMCWxvY2FsaG9zdDAeFw0xNzAzMjExNzQ1NDNa
Fw0xODAzMjExNzQ1NDNaMDMxCzAJBgNVBAYTAkNBMRAwDgYDVQQKDAdCcm9jYWRl
MRIwEAYDVQQDDAlsb2NhbGhvc3QwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC+YG/CkiNm/BO+u1mYLKP8cpz/0O9CE+fusO0spXxjKfjPAvK7kiogxABm
bg9MQeWl4SbFa5x3q5uyZJxApJ+tAnnWZa+cbj5pmNsQFfIbFOwSAmFyhh/NIp7Y
/wApskKjnVsMFkarqX8W2xKxZreapZFMa9DGpOeh8Jo2yvcTAimFfSJ4nyKlCr1C
DuuaTSvAttC8Z9mEqD9TOaSYwQI0pnfVO+ySgY8ndqDXYdRvl+bV1taghlKOgxMY
J78lyZxYf6CIn22BAaz/f9a5ffS13Hh5Cmurj2dUmmqDE49p2KEVtXQ3D6nuopli
V49ok+z93/40Uq4OVJZJk5Kx8ZuxAgMBAAEwDQYJKoZIhvcNAQEFBQADggEBAI1d
1VkMH9i3SorPIHpbVqbeDe7LPdaFmrT0COr3AFUECw3gBj1Zy82Kp8XkIJJdVCu8
MNm3wTARqeNBY2c3luw6QeA6l4qRIVM4FqNj6rvtqtNZQ9EEKRRwAm0GSVp+uSvu
E88XSXO+r6N+SXQemRIyhNQ7LJq+cDEaP5WfNtKg+zj085Xd0qiB94BKFt5Q+xAa
B7lwuUvT7Yt92aUVXIaZ6aY5oMv4t7+lPBBKjg8cNeywDa9h3yVZYIzSggghu0qu
GZO57qUh5agxqKiEVf9Ya325u5gj73UJsKOSsyVA1HB8RsPEEdz8j8FBAqMNSTQj
8UDtUGpYiYlzyiBUELc=
-----END CERTIFICATE-----
Syntax
show telemetry collector name collector-name
Parameters
collector-name
Specifies the name assigned to the telemetry collector.
Modes
Privileged EXEC mode
Output
The show telemetry collector name command displays the following information:
Examples
The following example displays the status of a collector.
device# show telemetry collector name col1
Syntax
show telemetry collector summary
Modes
Privileged EXEC mode
Usage Guidelines
This command displays the status of the currently active telemetry collector sessions. These are
initiated with collectors in the "activated" state.
Output
The show telemetry collector summary command displays the following information:
Examples
Example output of the collector configuration summary.
device# show telemetry collector summary
Activated Collectors:
--------------------
Name IP Address:Port VRF Name Streaming/Connection Status
------- ---------------- -------- ---------------------------
col1 10.24.12.86:8080 mgmt-vrf streaming
col2 10.24.12.86:8080 mgmt-vrf streaming_errored
Syntax
show telemetry server status
Modes
Privileged EXEC mode
Output
The show telemetry server status command displays the following information:
Examples
Example of typical command output with no errors.
device# show telemetry server status
Telemetry Server running on port 50051, with transport as tcp
Syntax
show telnet server status
Modes
Privileged EXEC mode
Examples
To display Telnet server status:
Syntax
show threshold monitor [ interface all area | security area [ login-
violation | telnet-violation ] | sfp all area [ current | rxp |
temperature | txp | voltage ]
Parameters
interface all area
Displays status of interface thresholds and alerts.
security area
Displays status of security thresholds and alerts.
login-violation
Displays status of login violations.
telnet-violation
Displays status of Telnet violations.
sfp all area
Displays status of SFP thresholds and alerts.
current
Amount of current supplied to the SFP transceiver.
rxp
Amount of incoming laser power, in microWatts (μW).
temperature
Temperature of the SFP, in degrees Celsius.
txp
Amount of outgoing laser power, in microWatts (μW).
voltage
Amount of voltage supplied to the SFP.
Modes
Privileged EXEC mode
Examples
Syntax
show tm voq-stat ingress-device all discards [ priority traffic_class ]
[ max-display max_display_number ]
Parameters
priority traffic_class
Displays discards for the specified traffic class priority. Enter an integer from 0 through 7.
max-display max_display_number
Displays the specified maximum number of discard entries. Enter an integer from 1 through 32.
Modes
Privileged EXEC mode
Usage Guidelines
This command does not apply to SLX 9150 and SLX 9250 devices.
If you do not enter the max-display max_display_number option, a maximum of eight entries is
displayed.
Examples
The following example displays the traffic management VOQ ingress discard statistics.
The following example displays the traffic management VOQ ingress discard statistics for a specific
traffic class priority.
Syntax
show tm voq-stat ingress-device all egress-port ethernet slot/port
[ priority number ]
Parameters
slot/port
Specifies the slot and port of the interface.
priority number
Optionally specifies the traffic-class priority of the VOQ statistics. Enter an integer from 0
through 7. If you do not include this option, all priorities are displayed.
Modes
Privileged EXEC
Output
The show tm voq-stat ingress-device all egress-port ethernet command displays
the following information:
Examples
The following example displays the VOQ statistics for traffic-class priority 0 on Ethernet interface 1/4.
show tm voq-stat ingress-device all egress-port ethernet 1/4 priority 0
VOQ-Counters:
====================================================
Priority 0
----------------------------------------------
EnQue Pkt Count 0
EnQue Bytes Count 0
Total Discard Pkt Count 0
Total Discard Bytes Count 0
Current Queue Depth 0
Maximum Queue Depth since Last read 0
Syntax
show tm voq-stat ingress-device all max-buffer-util
Modes
Privileged EXEC mode.
Usage Guidelines
This command does not apply to SLX 9150 and SLX 9250 devices.
Examples
The following example displays the VOQ maximum buffer utilization statistics.
Syntax
show tm voq-stat ingress-device all max-queue-depth [ max-display
max_display_number ] [ min-threshold filter_number ] [ priority
traffic_class ]
Parameters
max-display max_display_number
Specifies the maximum displayed entries. Enter an integer from 1 to 32.
min-threshold filter_number
Ignores the maximum queue depths below the specified min-threshold filter in bytes. Enter an
integer from 1 through 1048640.
priority traffic_class
Displays only the specified traffic-class priority. Enter an integer from 0 through 7.
Modes
Privileged EXEC mode.
Usage Guidelines
The entries are sorted by the highest number of discards.
If you do not enter the max-display max_display_number option, a maximum of eight entries is
displayed.
Examples
The following example displays the traffic management VOQ maximum queue depth statistics.
....
Syntax
show tm voq-stat ingress-device ethernet slot/port { discards [ max-
display max_display_number | priority traffic_class ] | egress-port
ethernet slot/port [ priority traffic_class ] | max-buffer-util |
max-queue-depth [ max-display max_display_number | min-threshold
minimum_threshold [ max-display max_display_number | priority
traffic_class ] | priority traffic_class ] }
Parameters
slot/port
The Ethernet slot and port
discards
Specifies discarded
max-display max_display_number
Limits the display of discards. The values range from 1 to a maximum of 32.
priority traffic_class
Displays discards by their traffic class priority. Priority values range from 0 through 7.
egress-port slot/port
The outbound port.
max-buffer-util
Displays a summary of traffic management VOQ maximum buffer utilization.
max-queue-depth
Displays a summary of traffic management VOQ maximum queue depth statistics.
max-display max_display_number
Limits the output to a maximum number of display entries. Values range from 1 to 64 entries.
min-threshold minimum_threshold
Specifies that the results omit max-queue-depths values below the minimum byte threshold.
The minimum threshold values range from 1 to 1048640 bytes.
Modes
Privileged EXEC mode.
Usage Guidelines
This command does not apply to SLX 9150 and SLX 9250 devices.
Examples
This example displays traffic management VOQ statistics for an egress interface.
device# show tm voq-stat ingress-device ethernet 2/1 egress-port ethernet 2/7 priority 2
VOQ-Counters:
====================================================
Priority 2
----------------------------------------------
EnQue Pkt Count 67404602
EnQue Bytes Count 1768413221
Total Discard Pkt Count 0
Total Discard Bytes Count 0
Current Queue Depth 0
Maximum Queue Depth since Last read 160
This example displays a summary of traffic management VOQ maximum queue depth statistics for a
specific ingress interface.
This example displays a summary of traffic management VOQ maximum buffer utilization for a specific
ingress interface.
This example displays a summary of traffic management VOQ discards for a specific ingress interface.
Syntax
show tm voq-stat slot slot_number [ cpu-group [ cpu_group_id | all ]]
Parameters
slot_number
The number of the line card slot. For devices that do not support line cards, specify 0 for the slot.
cpu-group cpu_group_id
The ID number for the CPU group.
Modes
Privileged EXEC mode
Examples
The following example displays information about the VOQ for the line card in slot 1 CPU group 1.
device# show tm voq-stat slot 1 cpu-group 1
CPU Group 1 Prio 0
EnQue Pkt Count 100
EnQue Bytes Count 22400
Total Discard Pkt Count 0
Total Discard Bytes Count 0
Current Queue Depth 0
Maximum Queue Depth since last read 0
show topology-group
Displays topology group information.
Syntax
show topology-group [ group-id ]
Parameters
group-id
Displays the information of the topology group of the specified ID.
Modes
Privileged EXEC mode
Output
The show topology-group command displays the following information.
show tpvm
Displays status of Third-Party Virtual Machine (TPVM) applications.
Syntax
show tpvm [ disk { add name { disk_name | auto disk_size } | remove name
{ disk_name | auto }
show tpvm ip-address
show tpvm status [ clear-tag tag-name ]
Command Default
This feature is not enabled.
Parameters
install
Installs TPVM.
disk
Displays disk information.
disk_name
Specifies a disk.
all
Specifies all disks.
ip-address
Displays IPv4 and IPv6 addresses that are configured on TPVM.
status
Displays TPVM information.
Modes
Privileged EXEC mode
Usage Guidelines
This command show tpvm status displays the installed TPVM version and the status of
Passwordless SSH configuration, AutoStart, and TPVM.
If TPVM is installed on older SLX images or if firmware download is done multiple times, SLX cannot
retrieve the TPVM version. If SLX cannot retrieve the TPVM version, the “Version Not Found” message
will be displayed.
Examples
To display the installed TPVM version and status of Passwordless SSH configuration, AutoStart and
TPVM or any errors:
device# show tpvm status
SSH and Sudo passwordless :Disabled
AutoStart :Disabled
Tpvm status :Installed
Tpvm version :4.1.1
device# show tpvm status
SSH and Sudo passwordless :Disabled
AutoStart :Disabled
Tpvm status :Installed
Tpvm version :Version Not Found
To display disk information, by using either the all keyword or specifying a disk name:
disk: vdc
Capacity: 30.00 GiB
Allocation: 196.00 KiB
total:
Capacity: 100.00 GiB
Allocation: 100.00 GiB
Available: 0.00 B
total:
Capacity: 100.00 GiB
Allocation: 100.00 GiB
Available: 0.00 B
To display IPv4 and IPv6 addresses that are configured on TPVM, in this example on MM1:
[SLX]# show tpvm ip-address mm1
[ TPVM running on MM1 ]
IPv4:
eth0 10.24.7.80
IPv6:
eth0 fe80::5054:ff:fe9c:446d
eth1 fe80::7:d0ff:fe02:100
Note
The show ip-address keywords require the qemu-guest-agent package on TPVM. If this
package is removed, the keyword fails.
Note
This section is a new addition and will be used to track changes made to this command from
SLX-OS 20.2.2 release. It will not record command change history previous to this release.
Syntax
show tpvm config {dns | hostname | ldap | ntp | timezone | trusted-peer }
Parameters
dns | hostname | ldap |ntp |timezone |trusted-peer
Specifies the type of configuration you want to display: DNS, Hostname, LDAP, NTP, Timezone
and Trusted-Peer.
Modes
Privileged EXEC mode
Examples
This example shows sample DNS output.
device# show tpvm config dns
nameserver 1.2.3.4
nameserver 1.1.1.1
search example.com
show tunnel
Displays information pertaining to a tunnel interface.
Syntax
show tunnel [ Tunnel Id | brief | replicator | statistics | status ]
show tunnel brief [ tunnel-id | dst-ip < ip address > | mode [ gre |
vxlan [ unicast | multicast ] ] | overlay-gateway | src-ip <ip
address> ]
show tunnel statistics [ tunnel-id | dst-ip < ip address > | mode [ gre |
vxlan [ unicast | multicast ] ] | overlay-gateway | src-ip <ip
address> ]
show tunnel status [ tunnel-id | count | dst-ip < ip address > | mode
[ gre | vxlan [ unicast | multicast ] ] | overlay-gateway | src-ip
<ip address> ]
Parameters
tunnel-id
Specifies the tunnel ID.
brief
Displays brief information of tunnels.
count
Displays tunnels count.
dst-ip
Filters by tunnel destination IP address.
gre
Filters by GRE tunnels.
vxlan
Filters by vxlan tunnels.
mode
Filters by tunnel mode.
multicast
Displays multicast tunnels.
overlay-gateway
Filters by Overlay gateway name.
replicator
Displays tunnels to NSX replicators.
src-ip
Filters by tunnel source IP address.
statistics
Displays tunnel statistics.
status
Displays listing of tunnel id and states.
unicast
Displays uinicast tunnels.
Modes
Privileged EXEC Mode
Examples
This example display tunnel information.
SLX# show tunnel brief
Tunnel 61441, mode VXLAN, node-ids 1
Admin state up, Oper state up, unicast
Source IP 25.25.25.25 ( Loopback 2 ), Vrf default-vrf
Destination IP 30.30.30.30
show udld
Shows global UDLD information.
Syntax
show udld
Modes
Privileged EXEC mode
Usage Guidelines
This command displays global unidirectional link detection (UDLD) protocol configuration values such
as whether the protocol is enabled on the switch and the hello time and timeout values.
Examples
The following example displays global UDLD information for the device.
Syntax
show udld interface [ ethernet slot/port ]
Parameters
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
Modes
Privileged EXEC mode.
Usage Guidelines
The following describes the values that appear in the output headings for this command.
Examples
To display UDLD information for a specific Ethernet interface:
Syntax
show udld statistics [ interface ethernet slot/port ]
Parameters
ethernet
Specifies a physical Ethernet interface.
slot
Specifies a valid slot number. For devices that do not support line cards, specify 0.
port
Specifies a valid port number.
Modes
Privileged EXEC mode
Usage Guidelines
This command displays all unidirectional link detection (UDLD) protocol statistics or shows the statistics
on a specified por
Examples
To show UDLD statistics on a specific Ethernet interface:
show users
Displays the users logged in to the system and locked user accounts.
Syntax
show users
Modes
Privileged EXEC mode
Examples
The following example displays active user sessions and locked user accounts.
device# show users
**USER SESSIONS**
Username Role Host IP Device Time Logged In
jsmith user 192.0.2.0 Cli 2016-04-30 01:59:35
jdoe admin 192.0.2.1 Cli 2016-05-30 01:57:41
**LOCKED USERS**
testUser
show version
Displays the current firmware version.
Syntax
show version [ all-partitions ] [ brief ]
Parameters
all-partitions
Displays firmware information for both the primary and the secondary partitions.
brief
Displays a brief version of the firmware information.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display firmware version information and build dates. The default command
output includes the following information:
• SLX-OS Version—The firmware version number
• Firmware name—The label of the firmware image
• Build Time—The build date and time of the firmware
• Install time—The date and time of the firmware installation
• Host Version—The Linux host version.
• Host Kernel—The Linux kernel version
• Control Processor—The control processor model and memory
Examples
The following example displays all firmware version information.
device# show version
SLX-OS 20.1.1slxosx_main_linux_upgrade_191013_1700
20.1.1slxosx_main_linux_upgrade_191013_1700
Syntax
show vlan brief [ provisioned | unprovisioned ]
Parameters
provisioned
Displays provisioned VLANs.
unprovisioned
Displays unprovisioned VLANs.
Modes
Privileged EXEC mode
Output
The show vlan brief command displays the following information:
Examples
The following example displays the status all VLANs, including MVRP VLANs.
(u)-Untagged
(t)-Tagged
================ =============== ========== ===================== ===============
==============
1 default ACTIVE Static Eth 1/5(t)
Po 60(t)
Syntax
show vlan detail
Modes
Privileged EXEC mode
Usage Guidelines
This command also displays endpoint tracking or MVRP status, including the configuration status of
each Ethernet or port-channel interface, specifying whether the VLAN was added statically or learned
dynamically.
Examples
device# show vlan detail
VLAN: 1, Name: default
Admin state: ACTIVE, Config status: Static
Number of interfaces: 7
Eth 0/4, tagged, Static
Eth 0/3, tagged, Static
Eth 0/2, tagged, Static
Eth 0/8, tagged, Static
Eth 0/6, tagged, Static
Eth 0/9, untagged, Static
Po 20, tagged, Static
VLAN: 10, Name: VLAN0010
Admin state: ACTIVE, Config status: Static
Number of interfaces: 3
Eth 0/3, tagged, Static
Eth 0/2, tagged, Static
Eth 0/4, tagged, Static
Po 20, tagged, Static
VLAN: 11, Name: VLAN0011
Admin state: ACTIVE, Config status: Static
Number of interfaces: 3
Eth 0/3, tagged, Static
Eth 0/2, tagged, Static
Eth 0/4, tagged, Dynamic (MVRP)
VLAN: 12, Name: VLAN0012
Admin state: ACTIVE, Config status: Dynamic (MVRP)
Number of interfaces: 1
Eth 0/4, tagged, Dynamic (MVRP)
VLAN: 13, Name: VLAN0013
Admin state: ACTIVE, Config status: Dynamic (EP tracking)
Number of interfaces: 1
Eth 0/6, tagged, Dynamic (EP tracking)
VLAN: 14, Name: VLAN0014
Admin state: INACTIVE(member port down), Config status: Static
Number of interfaces: 1
Eth 0/8, tagged, Static
show vrf
Displays Virtual Routing and Forwarding (VRF) configuration information for the management VRF, the
default VRF, or a user-defined VRF.
Syntax
show vrf { mgmt-vrf | default-vrf |vrf-name }[detail | interface
interface ]
Parameters
mgmt-vrf
Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf-name
Specifies a named VRF.
detail
Displays detailed information for all VRFs configured.
interface interface
Displays VRF information for the specified interface.
Modes
Privileged EXEC mode
Examples
This example displays basic information for the default VRF.
device# show vrf default-vrf
VRF-Name: default-vrf, VRF-Id: 1
IP Router-Id: 50.50.50.1
Interfaces:
Ve 40, Ve 84, Ve 85, Ve 150, Ve 211,
Ve 501, Ve 503, Ve 504, Ve 505, Ve 1025,
Ve 1059, Ve 2000, Lo 50
Address-family IPV4 unicast
Max routes: - Route count:134
No import route-maps
No export route-maps
This example displays name of length upto 64 characters for all VRFs.
device# show vrf
<WORD:1-64> Name of VRF: mgmt-vrf, default-vrf(default), <user VRF>
detail detail
interface interface
| Output modifiers
<cr>
show vrrp
Displays information about IPv4 VRRP and VRRP-E sessions.
Syntax
show vrrp
show vrrp VRID [ detail | summary ]
show vrrp detail
show vrrp interface { ethernet slot/port | port-channel number | ve
vlan_id } [ detail | summary ]
show vrrp summary [ vrf { vrf-name | all } ]
Parameters
VRID
The virtual group ID about which to display information. The range is from 1 through 16.
detail
Displays all session information in detail, including session statistics.
summary
Displays session-information summaries.
interface
Displays information for an interface that you specify.
ethernet slot port
Specifies a valid, physical Ethernet interface with a slot and port number.
port-channel number
Specifies a port-channel interface number.
ve vlan_id
Specifies the VE VLAN number.
vrf
Specifies a VRF instance or all VRFs.
vrf-name
Specifies a VRF instance. For the default vrf, enter default-vrf.
all
Specifies all VRFs.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to display information about VRRP and VRRP-E sessions, either in summary or full-
detail format. You can also specify a particular virtual group ID or interface for which to display output.
This command is for VRRP and VRRP-E. VRRP-E supports only the VE interface type.
To display information for VRRP sessions using the default VRF, you can use the show vrrp
summary command syntax (with no additional parameters).
For the default or a named VRF, you can use the show vrrp summary vrf command syntax with
the vrf-name option.
To display information for all VRFs, use the show vrrp summary vrf all command.
Examples
The following example shows all VRRP session information in detail, including session statistics.
device# show vrrp detail
VRID 14
Interface: Ve 2018; Ifindex: 1207961570
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv4
Version: 2
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): 10.18.1.100
Virtual MAC Address: 0000.5e00.0112
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1 sec (default: 1 sec)
Preempt mode: ENABLE (default: ENABLE)
Hold time: 0 sec (default: 0 sec)
Master Down interval: 4 sec
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Global Statistics:
==================
Checksum Error : 0
Version Error : 0
VRID Invalid : 0
Session Statistics:
===================
Advertisements : Rx: 0, Tx: 49
Gratuitous ARP : Tx: 1
Session becoming master : 1
Advts with wrong interval : 0
Prio Zero pkts : Rx: 0, Tx: 0
Invalid Pkts Rvcd : 0
Bad Virtual-IP Pkts : 0
Invalid Authenticaton type : 0
Invalid TTL Value : 0
VRID 15
Interface: Ve 2019; Ifindex: 1207961571
Mode: VRRP
Admin Status: Enabled
Description :
Address family: IPv4
Version: 2
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): 10.19.1.100
Virtual MAC Address: 0000.5e00.0113
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1 sec (default: 1 sec)
Preempt mode: ENABLE (default: ENABLE)
Hold time: 0 sec (default: 0 sec)
Master Down interval: 4 sec
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Global Statistics:
==================
Checksum Error : 0
Version Error : 0
VRID Invalid : 0
Session Statistics:
===================
Advertisements : Rx: 0, Tx: 81
Gratuitous ARP : Tx: 1
Session becoming master : 1
Advts with wrong interval : 0
Prio Zero pkts : Rx: 0, Tx: 0
Invalid Pkts Rvcd : 0
Bad Virtual-IP Pkts : 0
Invalid Authenticaton type : 0
Invalid TTL Value : 0
Invalid Packet Length : 0
The following example displays summary information for VRRP statistics on the VRF named Marketing.
device# show vrrp summary vrf Marketing
The following example displays summary information for VRRP statistics on all VRFs.
device# show vrrp summary vrf all
The following example displays summary information for VRRP statistics on the default VRF. (This
command is equivalent to show vrrp summary.)
device# show vrrp summary vrf default-vrf
VRID 3
Interface: Ve 100; Ifindex: 1207959652
Mode: VRRPE
Admin Status: Enabled
Description :
Address family: IPv4
Version: 2
Authentication type: No Authentication
State: Master
Session Master IP Address: Local
Virtual IP(s): 10.1.1.100
Virtual MAC Address: 02e0.523d.750a
Configured Priority: unset (default: 100); Current Priority: 100
Advertisement interval: 1 sec (default: 1 sec)
Preempt mode: DISABLE (default: DISABLED)
Advertise-backup: DISABLE (default: DISABLED)
Backup Advertisement interval: 60 sec (default: 60 sec)
Short-path-forwarding: Disabled
Revert-Priority: unset; SPF Reverted: No
Hold time: 0 sec (default: 0 sec)
Master Down interval: 4 sec
Trackport:
Port(s) Priority Port Status
======= ======== ===========
Tracknetwork:
Network(s) Priority Status
========= ======== ==========
10.20.1.0/24 50 Up
Global Statistics:
==================
Checksum Error : 0
Version Error : 0
VRID Invalid : 0
Session Statistics:
===================
Advertisements : Rx: 0, Tx: 35
Neighbor Advertisements : Tx: 19
Session becoming master : 1
Advts with wrong interval : 0
Prio Zero pkts : Rx: 0, Tx: 0
Invalid Pkts Rvcd : 0
Bad Virtual-IP Pkts : 0
Invalid Authenticaton type : 0
Invalid TTL Value : 0
Invalid Packet Length : 0
VRRPE backup advt sent : 0
VRRPE backup advt recvd : 0
Syntax
show ztp status
Modes
Privileged EXEC mode
Usage Guidelines
This command displays the status of Zero Touch Provisioning (ZTP) on the device. When an attribute is
unavailable or not applicable, the status is "None."
The ZTP History attribute shows the last 10 ZTP processes. However, if you run the fullinstall
firmware download command, the ZTP history is deleted and the ZTP History Countvalue attribute
is reset.
Examples
The following example shows output when the ZTP process is running.
device# show ztp status
ZTP History
...
ZTP history countvalue:1
**1)
ZTP firmware upgrade...
ZTP fwdir [..x.x,anonymous,/fw/slxos20.1.1_bldxx/,a] proto [ftp]
The following example shows status when the ZTP process is not running and there is no history.
device# show ztp status
clientid :None
Switch Configuration File :None
Firmware Directory :None
firmware download state :None
firmware fullinstall :None
ZTP Description msg :No status available
ZTP History :No history available
shutdown (cluster)
Isolates the MCT node by shutting down all components.
Syntax
shutdown { all | clients }
no shutdown { all | clients }
Command Default
The MCT node is disabled.
Modes
Cluster configuration mode
Parameters
all
Shuts down all client interfaces, VxLAN and L2VPN tunnels, and the peer-interface. Any CCP and
keepalive sessions are brought down as well.
all
Shuts down all client interfaces, VxLAN and L2VPN tunnels, and the peer-interface. Any CCP and
keepalive sessions are brought down as well.
client
Shuts down all client interfaces while keeping the peer-interface up.
Usage Guidelines
Enter no shutdown to enable the peers/clients.
Examples
To shutdown all access to an MCT:
device# configure terminal
device(config)# cluster MCT1
device(config-cluster-MCT1)# shutdown all
shutdown (interface)
Disables the current interface.
Syntax
shutdown
no shutdown
Command Default
The interface is disabled.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no shutdown to enable the interface.
If you use in-band management only, you may choose to shut down the management interface (which
is considered out of band). When the management interface is shut down, all services (such as ping,
scp, telnet, ssh, snmp, firmwaredownload, and supportsave) through the management interface IP.
Management interface shutdown is a persistent configuration, meaning that the interface remains down
after a system reboot or failover.
Examples
To disable a specific Ethernet interface:
device# configure terminal
device(config)# interface ethernet 0/1
device(conf-if-eth-0/1)# shutdown
shutdown (LIF)
Removes a physical or port-channel interface on an edge port from participating in logical interface
(LIF) data traffic without the need to shut down the interface.
Syntax
shutdown
no shutdown
Command Default
The LIF service instance is not shut down.
Modes
LIF configuration mode on a physical port or port-channel
Usage Guidelines
Use the no form of this command to restore the service instance status to the default.
Examples
The following example removes a service instance on an Ethernet port from participating in data traffic.
device(config)# interface ethernet 2/6
device(conf-if-eth-2/6)# logical-interface ethernet 2/6.120
device(conf-if-eth-lif-2/6.120)# shutdown
shutdown-time
Specifies a shutdown time for loopback detection (LD).
Syntax
shutdown-time minutes
no shutdown-time
Command Default
The default is 0.
Parameters
minutes
Shutdown time in minutes. Range is from 0 through 1440.
Modes
Protocol Loop Detection configuration mode
Usage Guidelines
By default the shutdown time is 0, which means that an LD-disabled logical interface (LIF) is never
auto-enabled.
If the shutdown time is configured with a nonzero value, the LD-disabled LIF is auto-enabled following
the specified shutdown time.
Examples
This example specifies a shutdown time of 20 minutes.
device# configure terminal
device(config)# loop-detection
device(config-loop-detect)# shutdown-time 1
2017/10/20-16:04:48, [ELD-1005], 3749, M2 | Active | DCE, INFO, SLX, Loop is detected on Ethernet 2/2
VLAN 20, the LIF (logical interface) is shutdown.
2017/10/20-16:05:46, [ELD-1007], 3750, M2 | Active | DCE, INFO, SLX, Loop detection disabled LIF
(Logical interface) on Ethernet 2/2 VLAN 20 is auto-enabled.
site
Creates a remote Layer 2 extension site in a VXLAN overlay gateway context and accesses site
configuration mode.
Syntax
site name
no site name
Parameters
name
Site identifier. An ASCII character string up to 63 characters long, including the alphabet,
numbers 0 through 9, hyphens (-), and underscores (_).
Modes
Overlay gateway configuration mode
Usage Guidelines
The VXLAN overlay gateway type must first be configured for Layer 2 extension, by means of the type
layer2-extension command.
A site represents a remote fabric or the other end of the VXLAN tunnel. A site is associated with a
"container," as data structure that includes the destination IPv4 address of the tunnel, the switchport
VLANs, bridge domain, and the administrative state.
Use the no site command with a specified name to remove the tunnel that corresponds to the
site.One you create the site instance, you enter VXLAN overlay gateway site configuration mode, where
you can configure other properties for the site. The key commands available in this mode are
summarized below:
Table 19: Key commands available in VXLAN overlay gateway site configuration mode
Command Description
bfd Configures Bidirectional Forwarding Detection (BFD) on a tunnel in
VXLAN overlay gateway configurations.
bfd interval Configures BFD session parameters on a tunnel in VXLAN overlay
gateway configurations.
extend bridge-domain Configures a bridge domain for the tunnels to the containing site in a
VXLAN overlay gateway configurations.
extend vlan Configures switchport VLANs for the tunnels to the containing site in a
VXLAN overlay gateway configurations.
ip address Specifies the IPv4 address of a destination tunnel in VXLAN overlay
gateway configurations.
shutdown Administratively shuts down tunnels to a VXLAN overlay gateway site.
Examples
The following example creates a VXLAN overlay gateway site and enters site configuration mode.
Syntax
snmp trap link-status disable { ethernetslot/port | loopback port | port-
channel channel | ve vlan-id }
no snmp trap link-status disable { ethernetslot/port | loopback port |
port-channel channel | ve vlan-id }
By default, the SNMP trap for link-status is enabled for all interfaces.
Parameters
ethernet slot/port
Specifies a physical Ethernet interface and a valid slot and port number.
loopback port
Specifies a loopback interface and a valid port number.
port-channel channel
Specifies a port-channel.
ve vlan-id
Specifies a virtual interface.
Modes
Interface sub-mode
Usage Guidelines
Use the no form of this command to enable SNMP traps for the interface link-status change. Use the
show running-config interface command to view the SNMP traps link-status. SNMP traps are
disabled for "Ethernet 0/1" and Ethernet 0/2" and by default enabled for "Ethernet 0/3" and "Ethernet
0/4". SNMP traps are disabled for Port-channel 21 and 22 and by default enabled for Port-channel 23.
SNMP traps are disabled for Loopback 11 and 12 and by default enabled for loopback 13. SNMP traps are
disabled for VE 1 and 2 and by default enabled for VE 3.
Examples
The following example displays the SNMP traps are disabled for "Ethernet 0/1" and Ethernet 0/2".
Enabled by default for "Ethernet 0/3" and "Ethernet 0/4" :
device# show running-config interface Ethernet
interface Ethernet 0/1
snmp trap link-status disable
shutdown
!
The following example displays the SNMP traps are disabled for Port-channel 21 and 22. Enabled by
default for Port-channel 23:
device# show running-config interface Port-channel
interface Port-channel 21
snmp trap link-status disable
shutdown
!
interface Port-channel 22
snmp trap link-status disable
shutdown
!
interface Port-channel 23
shutdown
!
The following example displays the SNMP traps are disabled for Loopback 11 and 12. Enabled by default
for loopback 13:
device# show running-config interface Loopback
interface Loopback 11
snmp trap link-status disable
shutdown
!
interface Loopback 12
snmp trap link-status disable
shutdown
!
interface Loopback 13
shutdown
!
The following example displays the SNMP traps are disabled for VE 1 and 2. Enabled by default for VE 3:
device# show running-config interface ve
interface Ve 1
snmp trap link-status disable
shutdown
!
interface Ve 2
snmp trap link-status disable
shutdown
!
interface Ve 3
shutdown
!
snmp-server community
Sets the community string and associates it with the user-defined group name to restrict the access of
MIB for SNMPv1 and SNMPv2c requests.
Syntax
snmp-server community string [ group group-name ]
no snmp-server community string [ group group-name ]
Command Default
None
Parameters
string
Specifies the community name string. Enter an alphanumeric string with 2 to 16 characters.
group group-name
Specifies the group name associated with the community name.
Modes
Global configuration mode
Usage Guidelines
Use a no form of this command to remove an community string or the group from the community.
Examples
The following example adds the community string named public and associates the group name named
user with it.
device(config)# snmp-server community public groupname user
snmp-server contact
Sets the SNMP server contact string.
Syntax
snmp-server contact string
no snmp-server contact
Command Default
The default contact string is "Operator 12345".
Parameters
string
Specifies the server contact. Enter an alphanumeric string from 4 to 255 characters. You must
enclose the text in double quotes if the text contains spaces.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to reset the default value.
Examples
The following example sets the SNMP server contact string to "Operator 12345".
snmp-server context
Maps the context name in an SNMPv3 packet protocol data unit (PDU) to the name of a VPN routing
and forwarding (VRF) instance.
Syntax
snmp-server context context_name [ vrf-name vrf_name ]
no snmp-server context context_name [ vrf-name vrf_name ]
Command Default
None
Parameters
context_name
Specifies the context name that is passed in the SNMP PDU.
vrf-name vrf_name
Specifies the VRF instance that can be retrieved when an SNMP request is sent with the context
name.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to delete the SNMP server context.
For SNMPv1 and SNMPv2, you must map the context with the community string. The SNMP agent
supports 256 contexts to support context-to-VRF mapping.
For SNMPv3, you only need to map the context with the VRF. The SNMPv3 request PDU itself provisions
for the context. Only one context is allowed for each VRF instance.
Important
SNMP SET requests work only on the default VRF.
Examples
The following example configures an SNMP server context to a VRF for SNMPv1 or SNMPv2.
device# configure terminal
device(config)# snmp-server community public groupname admin
device(config)# snmp-server context mycontext vrf myvrf
device(config)# snmp-server mib community-map public context mycontext
The following example configures an SNMP server context to a VRF for SNMPv3.
device# configure terminal
device(config)# snmp-server context mycontext1 vrf myvrf1
Syntax
snmp-server enable trap
no snmp-server enable trap
Command Default
The SNMP server traps are enabled by default.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to disable the SNMP traps.
Examples
The following example disables the SNMP traps.
device# configure terminal
device(config)# no snmp-server enable trap
Syntax
snmp-server engineid local engine_id
no snmp-server engineid local
Command Default
A default engine ID is generated during system start up.
Modes
Global configuration mode
Usage Guidelines
SNMP agent Engine ID can be 12 or 13 bytes in hexadecimal format. Each byte must be separated by
colons. When using a 12 byte engine ID, each byte must be entered as 2 char per octet. For example, the
value 1 must be entered as 01. However, for the 13 byte engine ID, each byte can be entered as 1 or 2 char
per octet. For example, the value 1 can be entered as 1 or as 01.
• When a 13 byte SNMP Engine ID is configured in version 20.2.3 and the full install downgrade is
performed, this 13 byte SNMP Engine ID will not be available after downgrade. However, you can
view this 13 byte SNMP Engine ID immediately after a coldboot downgrade and will be lost on
subsequent file replays, config rollback, or copy of startup configuration.
• When the Default SNMP Engine ID is reset using the no snmp-server engineID local
command, a warning message is displayed. This warning message is, however, not displayed when it
is reset using the REST/Netconf query.
SLX(config)# no snmp-server engineID local
80:0:6:34:b2:4:0:0:10:aa:9a:b7:96
%Warning: SNMP engine id is currently default. Removing default engine id would again
set it to default value%.
Use the no form of the command to remove the configured engine ID from database.
Examples
The following example configures an engine ID for the SNMP agent.
The following example removes the configured engine ID from the database.
snmp-server group
Creates user-defined groups for SNMPv1/v2/v3 and configures read, write, and notify permissions to
access the MIB view.
Syntax
snmp-server group groupname { v1 | v2c | v3 { auth | noauth | priv } }
[ read viewname ] [ write viewname ] [ notify viewname ]
no snmp-server group groupname { v1 | v2c | v3 { auth | noauth | priv } }
[ read viewname ] [ write viewname ] [ notify viewname ]
Command Default
None
Parameters
groupname
Specifies the name of the SNMP group to be created.
v1 | v2c | v3
Specifies the version of SNMP.
auth | noauth | priv
Specifies the various security levels for SNMPv3.
auth
Specifies the authNoPriv security level. Password authentication is used based on either MD5 or
SHA hash authentication and no encryption is used for communications between the devices.
noauth
Specifies the noAuthNoPriv security level. If no security level is specified, noauth is the default.
This security level means that there is no authentication password exchanged and the
communications between the agent and the server are not encrypted. The SNMP requests are
authorized based on a username string match similar to the community string for SNMPv1/v2c.
priv
Specifies the authPriv security level. Password authentication is used based on either MD5 or
SHA hash authentication and the communication between the agent and the server are also
encrypted.
read viewname
Specifies the name of the view that enables you to provide read access.
write viewname
Specifies the name of the view that enables you to provide both read and write access.
notify viewname
Specifies the name of the view that enables you to provide access to the MIB for trap or inform.
Modes
Global configuration mode
Usage Guidelines
Maximum number of SNMP groups supported is 10.
Examples
The following example creates SNMP server group entries for SNMPv3 user group with auth or noauth
permission.
device(config)# snmp-server group group1 v3 auth read myview write myview notify myview
device(config)# snmp-server group group2 v3 noauth read all write all notify all
device(config)# snmp-server group group3 v3 auth
snmp-server host
Configures the SNMP trap server host attributes.
Syntax
snmp-server host { ipv4_host | ipv6_host | dns_host } community_string
[ version { 1 | 2c } ] [ udp-port port ] [ severity-level | { none |
debug | info | warning | error | critical } ] [ use-vrfvrf-name ]
[ source-interface { loopback | management { chassis-ip | mgmt-ip } |
ve ]
no snmp-server host { ipv4_host | ipv6_host | dns_host } community_string
[ version { 1 | 2c } ] [ udp-port port ] [ severity-level | { none |
debug | info | warning | error | critical } ] [ use-vrf vrf-name]
[ source-interface { loopback | management { chassis-ip | mgmt-ip } |
ve ]
Parameters
host { ipv4_host | ipv6_host | dns_host }
Specifies the IP address of the host. IPv4, IPv6, and DNS hosts are supported.
community_string
Specifies the community string associated with the host entry. The number of characters
available for the string ranges from 1 through 64.
version { 1 | 2c }
Selects version 1 or 2c traps to be sent to the specified trap host.
udp-port port
Specifies the UDP port where SNMP traps will be received. Valid port IDs range from 0 through
65535. The default port is 162.
severity-level { none | debug | info | warning | error | critical }
Provides the ability to filter traps based on severity level on both the host and the SNMPv3 host.
Only RASLog (swEvent) traps can be filtered based on severity level. The configured severity
level marks the reporting threshold. All messages with the configured severity or higher are
displayed. If the severity level of none is specified, all traps are filtered and no RASLog traps are
received.
use-vrf vrf-name
Specifies a VRF though which to communicate with the SNMP host. By default, all management
services are enabled on the management VRF ("mgmt-vrf") and the default VRF ("default-vrf").
source-interface { loopback | management { chassis-ip | mgmt-ip } |
ve
Specifies whether to use a loopback, management, or VE interface as a source address for
notifications. For management, specifies the chassis or management IP address.
Modes
Global configuration mode
Usage Guidelines
This command sets the trap destination IP addresses and SNMP version, associates a community string
with a trap host community string (for v1 and v2c), and specifies the UDP destination port where SNMP
traps will be received.
To configure SNMP trap hosts associated with community strings, you must create the community
string using the snmp-server community command before configuring the host.
The host supports six communities and their associated trap recipients and trap recipient severity levels.
The default value for the trap recipient of each community is 0.0.0.0. The length of the community
string should be between 2 and 64 characters.
The no snmp-server host host community-string command removes the SNMP server host
from the device configuration altogether.
The no form of the command can be used to remove the following configuration for a given host:
version, udp-port, severity-level, and use-vrf.
Examples
The following example creates an entry for trap host 1050:0:0:0:5:600:300c:326b associated with
community “public.” The trap host receives traps from the configured device.
device(config)# snmp-server host 1050:0:0:0:5:600:300c:326b public severity-level Info
The following example creates an entry for trap host brcd.extremenetworks.com associated with
community “public.” The trap host receives traps from the configured device.
device(config)# snmp-server host brcd1.extremenetworks.com public severity-level info
The following example associates “commaccess” as a read-only community and set 10.32.147.6 as a trap
recipient with SNMP version 2c on target port 162.
device(config)# snmp-server host 10.32.147.6 commaccess version 2c udp-port 162
The following example creates a trap host (10.23.23.45) associated with the community “public”, which
will receive all traps with the severity level of Info.
device(config)# snmp-server host 10.23.23.45 public severity-level info
The following example removes the udp-port configuration and resets the default to 162.
device(config)# no snmp-server host 10.24.61.10 public udp-port
snmp-server location
Sets the SNMP server location string.
Syntax
snmp-server location string
no snmp-server location
Command Default
The default location string is "Building 3 Room 214".
Parameters
location string
Specifies the SNMP server location string. Enter an alphanumeric string from 4 to 255 characters.
You must enclose the text in double quotes if the text contains spaces.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to reset the default value.
Examples
The following example sets the SNMP server location string to "Building 3 Room 214".
Syntax
snmp-server mib community-map community-name context context-name
no snmp-server mib community-map community-name context context-name
Command Default
None
Parameters
community-name
Specifies an SNMP community name.
context context-name
Specifies an SNMP context.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to remove a community string and its associated context name.
Any incoming SNMPv1/v2c requests with the specified community name uses the context name
specified by this command. The context name can be used in SNMP requests for
"ipCidrRouteTable."One community can be mapped to only one context. However, a single context can
be mapped to multiple communities.
Before mapping the community to context, a valid context should be configured by using the snmp-
server context command and a valid community string should be configured by using the snmp-
server community command.
Examples
The following example maps an SNMP community string to a context name.
device# configure terminal
device(config)# snmp-server mib community-map public context mycontext
The following example removes an SNMP community string and its associated context name.
Syntax
snmp-server preserve-statistics disable
no snmp-server preserve-statistics disable
Command Default
SNMP MIB statistics are preserved by default.
Parameters
disable
Disables the preservation of SNMP MIB statistics.
Modes
Global configuration mode
Examples
This following example disables the preservation of statistics.
device(config)# snmp-server preserve-statistics disable
snmp-server sys-descr
Sets the Management Information Base (MIB-2) object identifier (OID) system description.
Syntax
snmp-server sys-descr string
no snmp-server sys-descr
Command Default
The system description varies with the device.
Parameters
string
The text for the system description. The string must be between 4 and 255 characters in length.
Modes
Global configuration mode
Usage Guidelines
Enter no snmp-server sys-descr to return to the default system description.
Examples
To set the system description OID to "Extreme BR-SLX9640, use:
snmp-server trap
Switches between standard and enterprise MIB to generate the BFD traps. When this CLI is configured,
the BFD traps defined in standard MIB get generated.
Syntax
snmp-server trap bfd-std-mib
[no] snmp-server trap bfd-std-mib
Modes
Global configuration mode
Usage Guidelines
The no form of this command will reset to default behavior. i.e., the BFD traps defined in enterprise MIB
get generated.
Examples
The following example provides an option to switch between standard and enterprise MIB.
SLX(config)# snmp-server trap ?
Possible completions:
bfd-std-mib Set standard MIB for BFD trap
SLX(config)# snmp-server trap bfd-std-mib?
Possible completions:
<cr>
snmp-server user
Creates or changes the attributes of SNMPv3 users, and allows the SNMPv3 user to be associated with
the user-defined group name.
Syntax
snmp-server user username [ groupname group-name ] [ auth { md5 | sha |
noauth } ] [ auth-password string [ encrypted ] ] [ priv { DES |
AES128 | nopriv } ] [ priv-password string [ encrypted ]
no snmp-server user username
Command Default
None
Parameters
username
The name of the user that connects to the agent. The name must be between 1 and 16 characters
long.
groupname group-name
The name of the group to which the user is associated. The configured user is allowed to be
associated with the user-defined groups created using the snmp-server group command.
auth
Initiates an authentication level setting session. The default level is noauth .
noauth
Specifies "No Authentication Protocol".
md5
The HMAC-MD5-96 authentication level.
sha
The HMAC-SHA-96 authentication level.
auth-password string
A string that enables the agent to receive packets from the host. Passwords are plain text and
must be added each time for each configuration replay. The password must be between 1 and 32
characters long. If a password contains supported special characters (such as !, @, #, $, %),
enclose the password in double quotes (").
priv
Initiates a privacy authentication level setting session. The default level is nopriv .
DES
Specifies the DES privacy protocol.
AES128
Specifies the AES128 privacy protocol.
nopriv
Specifies "No Privacy Protocol".
priv-password string
Specifies a string (not to exceed 32 characters) that enables the host to encrypt the contents of
the message that it sends to the agent. Passwords are plain text and must be added each time
for each configuration replay. The privacy password alone cannot be configured. You configure
the privacy password with the authentication password. If a password contains supported
special characters (such as, !, @, #, $, %), enclose the password in double quotes (").
encrypted
Encrypts the input for auth/priv passwords. The encrypted key should be used only while
entering the encrypted auth/priv passwords.
Modes
Global configuration mode
Usage Guidelines
This command configures SNMPv3 users that can be associated with a trap and inform response
functionality. This command also allows configured user to be associated with user-defined SNMP
groups created using the snmp-server group command. The maximum number of SNMP users that
can be configured is 10. Optional encryption for auth-password and priv-password is also
provided.
When creating a new SNMPv3 user without group name, by default there is no group name mapped
with the SNMPv3 user. You must map the configured SNMPv3 user with any non-existing or existing
group name available in the group CLI configuration to contact the device through SNMPv3.
This command may not be successful where encrypted passwords are generated by third-party or
open-source tools.
Examples
The following example configures a basic authentication policy.
device(config)# snmp-server user extreme groupname snmpadmin auth md5 auth-password
user123 priv AES128 priv-password user456
The following example creates the SNMP users "user1" and "user2" associated with used-defined group
"group1" under global configuration mode.
device(config)# snmp-server user user1 groupname group1
device(config)# snmp-server user user2 groupname group1 auth md5 auth-password password
priv DES priv-password password
snmp-server v3host
Specifies the host recipient for SNMPv3 trap notification.
Syntax
snmp-server v3host { ipv4_host | ipv6_host | dns_host } user_name
[ notifytype { traps | informs } ] [ engineid engine-id ] [ udp-port
port_number ] [ severity-level | { none | debug | info | warning |
error | critical } ] [ use-vrf { vrf-name} ] [ source-interface
{ loopback | management { chassis-ip | mgmt-ip } | ve ]
no snmp-server v3host { ipv4_host | ipv6_host | dns_host } user_name
[ notifytype {traps | informs}] [ engineid engine-id ] [ udp-port
port_number ] [ severity-level | {none | debug | info | warning |
error | critical } ] [ use-vrf ] [ source-interface { loopback |
management { chassis-ip | mgmt-ip } | ve ]
Parameters
ipv4_host | ipv6_host | dns_host
Specifies the IP address of the host. IPv4, IPv6, and DNS hosts are supported.
user_name
Specifies the SNMPv3 user name to be associated with the SNMPv3 host entry.
notifytype traps | informs
Specifies the type of notification traps that are sent for the host. Traps and informs are
supported. The default notify type is traps.
engineID engine-id
Configures the remote engine ID to receive informs on a remote host.
udp-port port_number
Specifies the UDP port of the host. The default UDP port number is 162.
severity-level { none | debug | info | warning | error | critical }
Provides the ability to filter traps based on severity level on both the host and the SNMPv3 host.
Only RASLog (swEvent) traps can be filtered based on severity level. The configured severity
level marks the reporting threshold. All messages with the configured severity or higher are
displayed. If the severity level of None is specified, all traps are filtered and no RASLog traps are
received. The default severity level is none.
use-vrf vrf-name
Configures SNMP to use the specified VRF to communicate with the host. The default is mgmt-
vrf.
source-interface { loopback | management { chassis-ip | mgmt-ip } |
ve
Modes
Global configuration mode
Usage Guidelines
You can associate a global SNMPv3 host only with global SNMPv3 users and the local SNMPv3 host only
with local SNMPv3 users. You cannot create a SNMPv3 host by associating with the local SNMPv3 users
and vice versa.
The no form of the command can be used to remove the following entities: notifytype, engineID,
udp-port, severity-level, and use-vrf.
Examples
The following example creates an entry for SNMPv3 trap IPv4 host 10.23.23.45 associated with SNMP
user "snmpadmin1."
The following example creates an entry for SNMPv3 trap IPv6 host 1050:0:0:0:5:600:300c:326b
associated with SNMP user "snmpadmin2." The trap host receives SNMPv3 traps from the configured
device.
The following example associates the default-vrf VRF for a trap host recipient.
device(config)# snmp-server v3host 10.24.61.10 public use-vrf default-vrf
snmp-server view
Creates a view entry with MIB object IDs to be included or excluded for user access.
Syntax
snmp-server view view-name mib_tree {included | excluded }
no snmp-server view view-name mib_tree {included | excluded }
Command Default
No SNMP server views are defined.
Parameters
view-name
Specifies the alphanumeric name to identify the view. The name should not contain spaces.
mib_tree
Specifies the MIB object ID called Object Identifiers (OIDs) that represent the position of the
object or sub-tree in the MIB hierarchy.
included | excluded
Specifies whether the specified MIB object ID must be included in the view or excluded from the
view.
Modes
Global configuration mode
Usage Guidelines
The maximum number of views supported with MIB tree entries is 10. Either a single view name
associated with 10 different MIB object IDs or 10 different view names associated with each one of the
MIB object IDs is allowed.
Examples
The following example creates an SNMP view entry "view1" with excluded permission for the MIB object
ID "1.3.6.1.2.1.1.3."
The following example creates an SNMP view entry "view2" with included permission for the MIB object
ID "1.3.6.1."
The following example removes the SNMP view entry "view1" from the configuration list.
soft-preemption
The soft-preemption command enables soft preemption functionality. This command must be
used on both the primary and secondary paths.
Syntax
soft-preemption
no soft-preemption
Command Default
The soft-preemption function is disabled.
Modes
MPLS LSP configuration mode
Usage Guidelines
The no function disables soft preemption for the path on which the command is executed.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example shows how configure a primary path.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp test
device(config-router-mpls-lsp-test)# soft-preemption
soft-preemption cleanup-timer
Sets the amount of time that the point of preemption must wait to receive the path tear notification
from the ingress LSR before sending a hard preemption path error.
Syntax
soft-preemption { cleanup-timer | value }
no soft-preemption { cleanup-timer | value }
Command Default
The soft-preemption cleanup-timer is disables on the router.
Parameters
cleanup-timer value
The value is the time the point of preemptionmust wait to receive the path tear notification from
the ingress LSR, before sending a hard preemption path error. Values ranging from 1 - 29 are not
valid values for this timer. The default setting is 30 seconds. The acceptable range for this timer
is 30 - 300. A value of 0 indicates soft preemption is disabled on the router.
Modes
MPLS policy mode
Usage Guidelines
The no function returns the timer value settings to the default setting (30 seconds).
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the soft-preemption cleanup-timer to 30 seconds, which is the
default setting.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# soft-preemption cleanup-timer 30
source
Configures the source address or a source interface for a tunnel interface.
Syntax
source { ip-address | ethernet slot/port | loopback number | ve vlan_id }
no source
Command Default
No source address or interface is configured.
Parameters
ip-address
Specifies a VE interface.
Modes
Interface tunnel configuration mode
Usage Guidelines
The maximum number of tunnel source supported is 16.
Use the no source command to remove the configured source for the tunnel interface.
The tunnel source address should be one of the router IP addresses configured on a physical, loopback,
or VE interface, through which the other end of the tunnel is reachable. The source interface must have
at least one IP address configured on it.
When the physical/ve interface is specified as the source of the GRE tunnel, the lowest IP address of
that interface is used as the tunnel source IP address. If the smallest IP address is removed from the
interface, the next smallest IP address is used as the tunnel source.
Examples
This example configures the source address for the tunnel interface.
Syntax
[no] source { ethernet <interface-id> | port-channel <port-channel-id> |
vlan { <vlan-id> | <vlan-range> } | ve { <ve-id> | <ve-range> } }
destination { ethernet <interface-id> | port-channel <port-channel-
id> } direction { rx | tx | both } [ flow-based ]
[no] source { ethernet <interface-id> | port-channel <port-channel-id>
vlan { <vlan-id> | <vlan-range> } | ve { <ve-id> | <ve-range> } }
destination rspan-vlan <vlan-id> { ethernet <interface-id> | port-
channel <port-channel-id> } direction { rx | tx | both } [ flow-
based ]
[no] source { ethernet <interface-id> | port-channel <port-channel-id>
vlan { <vlan-id> | <vlan-range> } | ve { <ve-id> | <ve-range> } }
destination erspan <erspan-id> source-ip <ip-address> destination-ip
<ip-address> [ vrf <user-vrf> ] direction { rx | tx | both } [ flow-
based ]
Command Default
There are no defaults for these commands
Parameters
ethernet <interface-id>
The source interface ID in the format 0/3.
port-channel <port-channel-id>
The source Port Channel ID.
vlan { <vlan-id> | <vlan-range> }
The VLAN ID or range of VLANs for the source of the traffic. VLAN is only available for use with
Flow Based Mirroring.
ve { <ve-id> | <ve-range> }
The VE ID or range of VEs for the source of the traffic. VE is only available for use with Flow
Based Mirroring.
destination
Indicates that the configurations following this keyword define the settings for the destination of
the mirrored traffic.
rspan-vlan <vlan-id>
This keyword indicates that the mirroring is RSPAN. Provide the VLAN ID for the VLAN to mirror
traffic to.
erspan <erspan-id>
This keyword indicates that the mirroring is ERSPAN. Provide a unique ERSPAN ID for this entry.
source-ip <ip-address>
The source IP address for the GRE tunnel. This configuration is only available for ERSPAN
mirroring.
destination-ip <ip-address>
The destination IP address for the GRE tunnel. This configuration is only available for ERSPAN
mirroring
vrf <user-vrf>
The user created VRF instance. This configuration is only available for ERSPAN mirroring.
direction { rx | tx | both }
Sets the traffic direction to apply mirroring on. You can apply mirroring on ingress, egress, or bi-
directional traffic.
flow-based
Indicates that Flow Based Mirroring is being applied. For Flow Based Mirroring to work, it is
recommended that ACLs with the mirror action be applied to the source interface before
configuring Flow Based Mirroring with this command. Flow Based Mirroring will activate only
when ACLs are applied to the source interface.
Modes
Monitor Session Mode
Examples
The following are examples for SPAN mirroring.
The following example shows the configuration of SPAN mirroring from a Port Channel interface to an
Ethernet interface. Traffic from both directions is mirrored.
SLX# configure terminal
SLX (config)# interface ethernet 0/2
SLX (conf-if-eth-0/2)# lldp disable
SLX (conf-if-eth-0/2)# exit
SLX (config)# monitor session 23
SLX (config-session-23)# source port-channel 1 destination ethernet 0/1 direction both
The following example shows the configuration of mirroring from a Port Channel to a destination that is
a Port Channel. Traffic from both directions is mirrored.
SLX# configure terminal
SLX (config)# monitor session 24
SLX (config-session-24)# source port-channel 1 destination port-channel 11 direction both
This example displays the complete configuration for Flow Based SPAN mirroring.
SLX # configure terminal
SLX (config)# interface ethernet 0/3
This examples show a configuration for Flow Based Mirroring from a Port Channel port to an Ethernet
port.
SLX (config)# monitor session 26
SLX (config-session-26)# source port-channel 1 destination ethernet 0/3 direction rx flow-
based
This example shows a configuration for Flow Based Mirroring from an Ethernet port to a Port Channel
port.
SLX (config)# monitor session 27
SLX (config-session-27)# source ethernet 0/1 destination port-channel 3 direction tx flow-
based
This example shows a configuration for Flow Based Mirroring from a VE to an Ethernet port.
SLX (config)# monitor session 28
SLX (config-session-28)# source ve 1 destination ethernet 0/3 direction both flow-based
This example show a configuration for Flow Based Mirroring from a VLAN to an Ethernet port.
SLX (config)# monitor session 29
SLX (config-session-29)# source vlan 100 destination ethernet 0/3 direction tx flow-based
This example mirrors the ingress traffic on ethernet port 0/1 to the destination RSPAN VLAN through
the configured ethernet port.
SLX# configure terminal
SLX (config)# interface ethernet 0/3
SLX (conf-if-eth-0/3)# lldp disable
SLX (conf-if-eth-0/3)# exit
SLX (config)# monitor session 28
SLX (config-session-28)# source ethernet 0/1 destination rspan-vlan 120 ethernet 0/3
direction rx
This example shows the configuration of RSPAN mirroring from a source ethernet port to a destination
RSPAN VLAN on a port channel.
SLX (config)# monitor session 30
SLX (config-session-30)# source ethernet 0/1 destination rspan-vlan 120 port-channel 2
direction tx
The following example shows the complete configuration of Flow Based Mirroring of an ethernet port to
a RSPAN VLAN.
SLX # configure terminal
SLX (config)# interface ethernet 0/3
SLX (conf-if-eth-0/3)# lldp disable
SLX (conf-if-eth-0/3)# exit
SLX (config)#ip access-list extended mirror-my-port
SLX (config-ipacl-std)#
SLX (config-ipacl-std)#seq 5 permit ip host 10.10.10.1 any count mirror
SLX (config-ipacl-std)# exit
SLX (config)# interface ethernet 0/1
SLX (config-eth-0/1)# ip access-group mirror-my-port in
SLX (config-eth-0/1)# ip access-group mirror-my-port out
SLX (config-eth-0/1)# exit
SLX (config)# monitor session 25
SLX (config-session-25)# source ethernet 0/1 destination rspan-vlan 120 ethernet 0/3
direction both flow-based
SLX (config-session-25)# exit
The following example shows the configuration of Flow Based Mirroring of a VLAN to a RSPAN VLAN
accessible on a port channel.
SLX # configure terminal
SLX (config)#mac access-list extended mirror-my-port
SLX (config-ipacl-std)#
SLX (config-ipacl-std)#seq 5 permit ip host 10.10.10.1 any count mirror
SLX (config-ipacl-std)# exit
SLX (config)# vlan 100
SLX (config-vlan-100)# mac access-group mirror-my-port in
SLX (config-vlan-100)# mac access-group mirror-my-port out
SLX (config-vlan-100)# exit
SLX (config)# monitor session 31
SLX (config-session-31)# source vlan 100 destination rspan-vlan 120 port-channel 2
direction both flow-based
SLX (config-session-31)# exit
This example configures ERSPAN mirroring of the ingress traffic on ethernet port 0/1 to the destination
IP address over GRE.
SLX# configure terminal
SLX (config)# interface ethernet 0/3
SLX (conf-if-eth-0/3)# lldp disable
SLX (conf-if-eth-0/3)# exit
SLX (config)# monitor session 32
SLX (config-session-32)# source ethernet 0/1 destination erspan 1 source-ip 10.10.10.1
destination-ip 10.20.20.1 vrf vrf-for-erspan direction both
This example shows the configuration of ERSPAN mirroring from a source port channel port to a
destination IP over GRE.
SLX (config)# monitor session 33
SLX (config-session-33)# source port-channel 1 destination erspan 1 source-ip 10.10.10.1
destination-ip 10.20.20.1 vrf vrf-for-erspan direction both
This example shows the configuration of ERSPAN mirroring from a VE (ve 1) to an specific destination
IP(10.20.20.1). This traffic is directed over IP GRE tunnel with a source IP (10.10.10.1).
SLX (config)# monitor session 34
SLX (config-session-34)# source ve 1 destination erspan 1 source-ip 10.10.10.1
destination-ip 10.20.20.1
direction rx vrf vrf-for-erspan flow-based
SLX (config-session-34)# exit
This example shows the configuration of ERSPAN mirroring from a VLAN (vlan 100) to an specific
destination IP(10.20.20.1). This traffic is directed over IP GRE tunnel with a source IP (10.10.10.1).
SLX (config)# monitor session 34
SLX (config-session-34)# source vlan 100 destination erspan 1 source-ip 10.10.10.1
destination-ip 10.20.20.1
direction rx vrf vrf-for-erspan flow-based
SLX (config-session-34)# exit
source-interface (LDAP)
Configures the LDAP server on specific VRF with source interface.
Syntax
source-interface [ ethernet | loopback | management | ve ]
no source-interface
Parameters
ethernet
Uses Ethernet interface as source interface.
loopback
Uses Loopback interface as source interface.
management
Uses Management (chassis IP) as source address.
ve
Uses VE interface as source interface.
Modes
Global configuration mode
Usage Guidelines
If the source-interface is not up or the IP address is not configured for the source-interface, the device
acts like the source-interface is not configured.
You must configure a source interface number for the given source-interface name which is the
interface number configured and viewed using the show ip interface brief command.
Examples
The following example shows configuration of IP address for source-interface.
SLX(config-host-10.1.1.100/mgmt-vrf)# source-interface ethernet 0/1
SLX(config-host-10.1.1.100/mgmt-vrf)# do show running-config ldap-server
ldap-server host 10.1.1.100 use-vrf mgmt-vrf
port 389
source-interface ethernet 0/1
!
SLX(config-host-10.1.1.100/mgmt-vrf)# source-interface ve 10
SLX(config-host-10.1.1.100/mgmt-vrf)# do show running-config ldap-server
ldap-server host 10.1.1.100 use-vrf mgmt-vrf
port 389
source-interface ve 10
!
SLX(config-host-10.1.1.100/mgmt-vrf)# source-interface loopback 5
SLX(config-host-10.1.1.100/mgmt-vrf)# do show running-config ldap-server
ldap-server host 10.1.1.100 use-vrf mgmt-vrf
port 389
source-interface loopback 5
!
SLX(config-host-10.1.1.100/mgmt-vrf)# no source-interface
SLX(config-host-10.1.1.100/mgmt-vrf)# do show running-config ldap-server
ldap-server host 10.1.1.100 use-vrf mgmt-vrf
port 389
!
source-interface (RADIUS)
Configures a source IP address for Remote Authentication Dial-In User Service (RADIUS) packets that
originate on the device.
Syntax
source-interface { ethernet | loopback | management { 0 | 1 } | ve ve-
num }
no source-interface
Command Default
When a source interface is not configured for a RADIUS host, the IP address of the interface through
which a RADIUS packet exits the device is used in the IP header as the source IP address.
Parameters
ethernet
Causes the ethernet interface to be used as the source interface for RADIUS packets that
originate on the device.
loopback
Causes the loopback interface to be used as the source interface for RADIUS packets that
originate on the device.
management
Causes the management interface to be used as the source interface for RADIUS packets that
originate on the device.
0
Causes the chassis IP address to be used as the source IP address.
1
Causes the MM1 IP address to be used as the source IP address.
ve ve-num
Specifies a virtual ethernet interface value to be used as the source interface for RADIUS packets
that originate on the device.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
Note
When an interface without an IP address is configured as the source interface, the egress
interface IP address is used as the source interface.
Note
The source interface configuration should not conflict with the VRF specified for
communications with the RADIUS server host; when the specified source interface is not part
of the VRF configured for communications with the RADIUS server host, the egress interface
IP address is used as the source interface.
Modifications to the interface (such as changing the IP address, VRF, and so on) that is configured as
the source interface, do not affect existing connections unless the corresponding link is dropped due to
these changes.
Examples
The following example shows how to configure an Ethernet interface (0/2) as the source interface for
RADIUS packets that originate on the device and are destined for the RADIUS server host 10.37.73.180.
spanning-tree autoedge
Enables automatic edge detection.
Syntax
spanning-tree autoedge
no spanning-tree autoedge
Command Default
Auto detection is not enabled.
Modes
Interface configuration mode
Usage Guidelines
The port can become an edge port if no Bridge Protocol Data Unit (BPDU) is received.
Examples
To enable automatic edge detection:
spanning-tree bpdu-mac
Sets the MAC address of the Bridge Protocol Data Unit (BPDU).
Syntax
spanning-tree bpdu-mac [ 0100.0ccc.cccd | 0304.0800.0700 ]
no spanning-tree bpdu-mac [ 0100.0ccc.cccd | 0304.0800.0700 ]
Parameters
0100.0ccc.cccd
Cisco Control Mac
0304.0800.0700
Extreme Control Mac
Modes
Interface configuration mode
Usage Guidelines
This command will only take effect when the protocol is PVST+ or R-PVST+.
Extreme devices support PVST+ and R-PVST+only. The PVST and R-PVST protocols are proprietary to
Cisco and are not supported.
Examples
To set the MAC address of the BPDU:
spanning-tree cost
Changes an interface's spanning-tree port path cost.
Syntax
spanning-tree cost cost
no spanning-tree cost cost
Command Default
The default path cost is 200000000.
Parameters
cost
Specifies the path cost for the Spanning Tree Protocol (STP) calculations. Valid values range
from 1 through 200000000.
Modes
Interface configuration mode
Usage Guidelines
Lower path cost indicates a greater chance of becoming root.
Examples
To set the port cost to 128:
spanning-tree edgeport
Enables the edge port on an interface to allow the interface to quickly transition to the forwarding state.
Syntax
spanning-tree edgeport [ bpdu-guard ]
no spanning-tree edgeport [ bpdu-guard ]
Command Default
Edge port is disabled.
Parameters
bpdu-guard
Guards the port against the reception of BPDUs.
Modes
Interface subtype configuration mode
Usage Guidelines
This command is only for RSTP and MSTP. Use the spanning-tree portfast command for STP
Note the following details about edge ports and their behavior:
• A port can become an edge port if no BPDU is received.
• A port must become an edge port before it receives a BPDU.
• When an edge port receives a BPDU, it becomes a normal spanning-tree port and is no longer an
edge port.
• Because ports directly connected to end stations cannot create bridging loops in the network, edge
ports directly transition to the forwarding state, and skip the listening and learning states
Examples
To enable a port to quickly transition to the forwarding state:
Syntax
spanning-tree guard root [ vlan vlan_id ]
no spanning-tree guard root
Command Default
Guard root is disabled.
Parameters
vlan vlan_id
Specifies a VLAN.
Modes
Interface configuration mode
Usage Guidelines
Guard root protects the root bridge from malicious attacks and unintentional misconfigurations where a
bridge device that is not intended to be the root bridge becomes the root bridge. This causes severe
bottlenecks in the data path. Guard root ensures that the port on which it is enabled is a designated
port. If the guard root enabled port receives a superior Bridge Protocol Data Unit (BPDU), it goes to a
discarding state.
If the VLAN parameter is not provided, the guard root functionality is applied globally for all per-VLAN
instances. But for the VLANs which have been configured explicitly, the per-VLAN configuration takes
precedence over the global configuration.
The root port provides the best path from the switch to the root switch.
Examples
To enable guard root:
spanning-tree link-type
Enables and disables the rapid transition for the Spanning Tree Protocol (STP).
Syntax
spanning-tree link-type [ point-to-point | shared ]
Command Default
The spanning-tree link-type is set to point-to-point.
Parameters
point-to-point
Enables rapid transition.
shared
Disables rapid transition.
Modes
Interface subtype configuration mode
Usage Guidelines
This command overrides the default setting of the link type.
Examples
To specify the link type as shared:
spanning-tree portfast
Enables the Port Fast feature on an interface to allow the interface to quickly transition to forwarding
state.
Syntax
spanning-tree portfast [ bpdu-guard ]
no spanning-tree portfast [ bpdu-guard ]
Command Default
Port Fast is disabled.
Parameters
bpdu-guard
Guards the port against the reception of BPDUs.
Modes
Interface subtype configuration mode
Usage Guidelines
This command is applicable the only for the Spanning Tree Protocol (STP). Port Fast immediately puts
the interface into the forwarding state without having to wait for the standard forward time. Use the
spanning-tree edgeport command for MSTP and RSTP.
BPDU guard disables all portfast-enabled ports should they ever receive BPDU frames. It does not
prevent transmitting of BPDU frames.
If you enable spanning-tree portfast bpdu-guard on an interface and the interface receives a
BPDU, the software disables the interface and puts the interface in the ERR_DISABLE state.
Enable Port Fast on ports connected to host. Enabling Port Fast on interfaces connected to switches,
bridges, hubs, and so on can cause temporary bridging loops, in both trunking and nontrunking mode.
Examples
To enable a port to quickly transition to the forwarding state:
spanning-tree priority
Changes an interface's spanning-tree port priority.
Syntax
spanning-tree priority priority
no spanning-tree priority
Command Default
The default value is 128.
Parameters
priority
Specifies the interface priority for the spanning tree. The range of valid values is from 0 through
240. Port priority is in increments of 16.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no spanning-tree priority to return to the default setting.
Examples
To configure the port priority to 16:
spanning-tree restricted-role
Restricts the role of the port from becoming a root port.
Syntax
spanning-tree restricted-role
no spanning-tree restricted-role
Command Default
The restricted role is disabled.
Modes
Interface configuration mode
Usage Guidelines
Enter no spanning-tree restricted-role to return to the default setting.
Examples
To configure the port from becoming a root port:
spanning-tree restricted-tcn
Restricts the Topology Change Notification (TCN) Bridge Protocol Data Units (BPDUs) sent on the port.
Syntax
spanning-tree restricted-tcn
no spanning-tree restricted-tcn
Command Default
The restricted TCN is disabled.
Modes
Interface configuration mode
Usage Guidelines
Enter no spanning-tree restricted-tcn to disable this parameter.
Examples
To restrict the TCN on a specific interface:
spanning-tree shutdown
Enables or disables spanning tree on the interface or VLAN.
Syntax
spanning-tree shutdown
no spanning-tree shutdown
Command Default
Spanning tree is disabled by default.
Modes
Interface (Ethernet or VLAN) configuration mode
Usage Guidelines
Enter no spanning-tree shutdown to enable spanning tree on the interface or VLAN.
Once all of the interfaces have been configured for a VLAN, you can enable Spanning Tree Protocol
(STP) for all members of the VLAN with a single command. Whichever protocol is currently selected is
used by the VLAN. Only one type of STP can be active at a time.
A physical interface (port) can be a member of multiple VLANs. For example, a physical port can be a
member of VLAN 1002 and VLAN 55 simultaneously. In addition, VLAN 1002 can have STP enabled and
VLAN 55 can have STP disabled simultaneously.
Vlan 1002 can not be enabled with the spanning-tree shutdown command.
Examples
To disable spanning tree on a specific interface:
speed (Ethernet)
Sets the speed negotiation value on an Ethernet interface.
Syntax
speed { 100 | 1000 | 1000-auto | 1000-auto-full-duplex | 1000-master-
full-duplex | 1000-master-half-duplex | 1000-slave-full-duplex |
1000-slave-half-duplex | 10000 | 25000 | 40000 | 100000 | auto }
Command Default
The speed is set to auto .
Parameters
100
Forces the speed to 100 Mbps.
1000
Forces the speed to 1 Gbps.
1000-auto
Forces the speed to 1 Gbps and auto negotiation of clock parameters. (802.3 Clause 37 Auto-
Negotiation)
1000-auto-full-duplex
(Supported only on SLX 9150-XT and Extreme 8520-XT) Forces the speed to be 1Gbps in full
duplex mode with auto negotiation of clock parameters.
1000-master-full-duplex
(Supported only on SLX 9150-XT and Extreme 8520-XT) Forces the speed to 1 Gbps with full
duplex capability and as a clock master.
1000-master-half-duplex
(Supported only on SLX 9150-XT and Extreme 8520-XT) Forces the speed to 1 Gbps with half
duplex capability and as a clock master.
1000-slave-full-duplex
(Supported only on SLX 9150-XT and Extreme 8520-XT) Forces the speed to 1 Gbps with full
duplex capability and as a clock slave.
1000-slave-half-duplex
(Supported only on SLX 9150-XT and Extreme 8520-XT) Forces the speed to 1 Gbps with half
duplex capability and as a clock slave.
10000
Forces the speed to 10 Gbps.
25000
Forces the speed to 25 Gbps.
40000
Modes
Interface subtype configuration mode
Usage Guidelines
Use the auto keyword or the no speed command to reset to the default setting.
Examples
The following example changes the speed to 1G.
device# configure terminal
device(config)# interface Ethernet 0/1
device(config-if-eth-0/1)# speed 1000-auto-full-duplex
device(config-if-eth-0/1)# no shutdown
The following example changes the speed of the interface to 1G, half duplex, and in the slave clock
mode.
device# configure terminal
device(config)# interface Ethernet 0/2
device(config-if-eth-0/1)# speed 1000-slave-half-duplex
device(config-if-eth-0/1)# no shutdown
spf-interval
Changes the shortest path first (SPF) interval.
Syntax
spf-interval { level-1 | level-2 } max-wait initial-wait second-wait
no spf-interval
Parameters
level-1
Specifies Level 1 packets only.
level-2
Specifies Level 2 packets only.
max-wait
Specifies the maximum interval between SPF recalculations in seconds. The range is from 0
through 120 seconds. The default is 5 seconds.
initial-wait
Specifies the initial SPF calculation delay in milliseconds after an LSP change. The range is from
0 through 120000 milliseconds. The default is 5000 milliseconds (5 seconds).
second-wait
Indicates the hold time between the first and second SPF calculations in milliseconds. The range
is from 1 through 120000 milliseconds. The default is 5000 milliseconds (5 seconds).
Modes
IS-IS router configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example specifies that the maximum interval in seconds between SPF recalculations is 15
seconds for Level 1 packets. The initial SPF calculation delay is 10000 milliseconds, and the hold time
between the first and second SPF calculations is 15000 milliseconds.
device# configure terminal
device(config)# router isis
device(config-isis-router)# spf-interval level-1 15 10000 15000
spt-threshold infinity
Configures all sources to use the shared rendezvous point (RP) tree instead of the Shortest Path Tree
(SPT).
Syntax
spt-threshold infinity
no spt-threshold
Command Default
By default, the SPT is used for sending packets.
Modes
Router PIM configuration mode
Usage Guidelines
This command uses only the RP to send packets and does not switch over to SPT.
The no spt-threshold infinity form of the command resets the default setting and uses SPT
for sending packets.
Examples
This example configures all sources to use the shared RP tree for IPv4 PIM.
device(config)# router pim
device(config-pim-router)# spt-threshold infinity
ssh
Connects to a remote server by means of the Secure Shell (SSH) protocol.
Syntax
ssh { IP_address | hostname } [ -c | -l | -m | interface {ethernet slot/
port | management | ve vlan-id } | vrf vrf-name ] }
Command Default
SSH connects to port 22.
Parameters
IP_address
Specifies the server IP address in IPv4 or IPv6 format.
hostname
Specifies the host name, a string from 1 through 253 characters.
-c
Specifies the encryption algorithm for the SSH session. This parameter is optional. Supported
algorithms include the following:
aes128-cbc
AES 128-bits
aes192-cbc
AES 192-bits
aes256-cbc
AES 256-bits
-l username
Login name for the remote server. This parameter is optional. If you specify a user name, you will
be prompted for a password. If you do not specify a user name, the command assumes you are
logging in as root and will prompt for the root password.
-m
Specifies the HMAC (Hash-based Message Authentication Code) message encryption algorithm.
This parameter is optional; if no encryption algorithm is specified, the default (hmac-md5) is
used. Supported algorithms include the following:
hmac-md5
MD5 128-bits. This is the default setting.
hmac-md5-96
MD5 96-bits
hmac-sha1
SHA1 160-bits
hmac-sha1-96
SHA1 96-bits
interface
Specifies an interface.
ethernet slot/port
Specifies an Ethernet interface slot and port number. The only supported value is 0.
management
Specifies the management interface.
ve vlan-id
Range is from 1 through 4090 if Virtual Fabrics is disabled, and from 1 through 8191 if Virtual
Fabrics is enabled.
vrf vrf-name
Specifies a VRF instance. See the Usage Guidelines.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to establish an encrypted SSH connection from a switch to a remote networking
device. This implementation is based on SSH v2.
To use the ssh command on the management VRF, use the vrf keyword and enter mgmt-vrf
manually.
Examples
To connect to a remote device using an SSH connection with default settings:
device# ssh 10.70.212.152
To connect to a remote device using an SSH connection with the management VRF:
device# ssh 10.70.212.152 vrf mgmt-vrf
admin@127.2.1.8's password
Syntax
ssh client cipher string
no ssh client cipher
Parameters
string
The string name of the cipher. Refer to the device for the available options.
Modes
Global configuration mode
Usage Guidelines
Use the no ssh client cipher command remove the cipher list from the ssh client.
Examples
Sets the SSH client's cipher list.
device# configure terminal
device(config)# ssh client cipher aes128-cbc
Syntax
ssh client cipher non-cbc
no ssh client ciphe non-cbc
Modes
Global configuration mode
Usage Guidelines
Use the no ssh client cipher non-cbc command remove the non-cbc cipher list from the ssh
client.
Examples
Sets the SSH client's cipher list to non-cbc ciphers.
device# configure terminal
device(config)# ssh client cipher non-cbc
device(config)# do show running-config ssh
ssh server non-cbc
ssh client non-cbc
Syntax
ssh client key-exchange string
no ssh client key-exchange
Parameters
string
The string for the name of the algorithm diffie-hellman-group14-sha1, or a comma-separated list
of supported Key-exchange algorithms, such as diffie-hellman-group14-sha1,diffie-hellman-
group1-sha1. Refer to the device for a complete list of available options.
Command Default
This command is not configured by default.
Modes
Global configuration mode
Usage Guidelines
You can configure the SSH client key-exchange method to DH Group 14. When the ssh client key-
exchange method is configured to DH Group 14, the SSH connection from a remote SSH client is allowed
only if the key-exchange method at the client end is also configured to DH Group 14. Enter no ssh client
key-exchange to restore ssh client key-exchange to the default value.
For backward compatibility, the string "dh-group-14" is also acceptable in place of "diffie-hellman-
group14-sha1"
Examples
To set ssh client key-exchange to DH Group 14:
device(config)#ssh client key-exchange diffie-hellman-group14-sha1
Syntax
ssh client mac string
no ssh client mac
Command Default
SSH server is enabled by default.
Parameters
string
The string name of the default MAC required. Your choices are hmac-sha2-256-
etm@openssh.com, hmac-sha2-512-etm@openssh.com, hmac-sha2-256, hmac-sha2-512, hmac-
sha1,hmac-sha1-96, hmac-md5, hmac-md5-96, hmac-ripemd160, hmac-
ripemd160@openssh.com, umac-64@openssh.com, umac-128@openssh.com, hmac-sha1-
etm@openssh.com, hmac-sha1-96-etm@openssh.com, hmac-md5-etm@openssh.com, hmac-
ripemd160-etm@openssh.com, umac-64-etm@openssh.com, umac-128-etm@openssh.com, and
hmac-ripemd160-etm@openssh.com. The default MACs supported in FIPS mode are hmac-sha1,
hmac-sha2-256, and hmac-sha2-512.
Modes
Global configuration mode
Usage Guidelines
The MAC hmac-md5 is not supported in FIPS mode.
Examples
Typical command example:
device# configure terminal
device(config)# ssh client mac hmac-sha1,hmac-sha2-256,hmac-sha2-512
device(config)# do show running-config ssh client
ssh client mac hmac-sha1,hmac-sha2-256,hmac-sha2-512
!
device(config)# do show ssh client status
SSH Client Mac: hmac-sha1,hmac-sha2-256,hmac-sha2-512
Syntax
ssh server algorithm {hostkey {x509v3-ssh-rsa | x509v3-rsa2048-sha256}}
no ssh server algorithm hostkey
Command Default
The host key algorithm is not configured.
Parameters
hostkey {x509v3-ssh-rsa | x509v3-rsa2048-sha256}
Designates x509v3-SSH-RSA or x509v3-RSA2048-SHA256 as the host key algorithm.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to remove the configured algorithm.
Examples
This example configures x509v3-SSH-RSA as the host key algorithm.
device# configure terminal
device(config)# ssh server algorithm hostkey x509v3-ssh-rsa
Syntax
ssh server certificate profile name
Command Default
By default, a profile name is not configured.
Parameters
profile name
Defines the certificate profile. Only "server" and "user" are valid strings.
Modes
Global configuration mode
Usage Guidelines
Examples
Example of entering server profile configuration mode.
device# configure terminal
device(config)# ssh server certificate profile server
device(ssh-server-cert-profile-server)#
Syntax
ssh server cipher string
no ssh server cipher
Parameters
string
The string name of the cipher. Refer to the device for the available options.
Modes
Global configuration mode
Usage Guidelines
Use the no ssh server cipher command remove the cipher list from the ssh client.
Examples
Sets the SSH server's cipher list.
device# configure terminal
device(config)# ssh server cipher aes256-ctr
Syntax
ssh server key { dsa | rsa [ 1024 | 2048 | 4096 ] | ecdsa 256 }
no ssh server key { dsa | rsa | ecdsa }
Command Default
The default values of SSH keys are:
• DSA is active
• ECDSA value is 256
• RSA value is 2048
Parameters
dsa
Generates the DSA key.
rsa [ 1024 | 2048 | 4096 ]
Generates the RSA key, in either the 1024, 2048, or 4096 bit size.
ecdsa 256
Generates the ECDSA key at 256 bits.
Modes
Global configuration mode
Usage Guidelines
The no ssh server key command zeroizes the SSH keys on the device. Running the no form of the
command requires you to save the configuration and reload the device. See the last example for more
information.
If you generate and delete SSH crypto keys, you must restart the SSH server using the no ssh
server shutdown command to enable the configuration.
Examples
Typical DSA command example:
device(config)# ssh server key dsa
Typical zeroizing example. Note that running the no form of the command requires you to save the
configuration and reload the device.
device(config)# no ssh server key dsa
% Info: Configuration is successful. For this config to take effect
immediately, restart SSH
server via exec command ssh-server restart or save the config and
reload.
Syntax
ssh server key-exchange string
no ssh server key-exchange
Parameters
string
The string for the name of the algorithm diffie-hellman-group14-sha1, or a comma-separated list
of supported Key-exchange algorithms; such as diffie-hellman-group14-sha1,diffie-hellman-
group1-sha1, and so on.
Command Default
This command is not configured by default.
Modes
Global configuration mode
Usage Guidelines
You can configure the SSH server key-exchange method to DH Group 14. When the SSH server key-
exchange method is configured to DH Group 14, the SSH connection from a remote SSH client is allowed
only if the key-exchange method at the client end is also configured to DH Group 14. Enter no ssh server
key-exchange to restore SSH server key-exchange to the default value.
For backward compatibility, the string "dh-group-14" is also acceptable in place of "diffie-hellman-
group14-sha1"
Examples
To set SSH server key-exchange to DH Group 14:
device(config)# ssh server key-exchange diffie-hellman-group14-sha1
Syntax
ssh server mac string
no ssh server mac
Parameters
string
The string name of the required default MAC. Your choices are hmac-sha2-256-
etm@openssh.com, hmac-sha2-512-etm@openssh.com, hmac-sha2-256, hmac-sha2-512, hmac-
sha1, hmac-sha1-96, hmac-md5, hmac-md5-96, hmac-ripemd160, hmac-
ripemd160@openssh.com, umac-64@openssh.com, umac-128@openssh.com, hmac-sha1-
etm@openssh.com hmac-sha1-96-etm@openssh.com, hmac-md5-etm@openssh.com, hmac-
ripemd160-etm@openssh.com, umac-64-etm@openssh.com, umac-128-etm@openssh.com, and
hmac-ripemd160-etm@openssh.com. The default MACs supported in FIPS mode are hmac-sha1,
hmac-sha2-256, and hmac-sha2-512.
Modes
Global configuration mode
Usage Guidelines
The MAC hmac-md5 is not supported in FIPS mode.
Examples
Typical command example:
device# configure terminal
device(config)# ssh server mac hmac-sha1,hmac-sha2-256,hmac-sha2-512
device(config)# do show running-config ssh server
ssh server mac hmac-sha1,hmac-sha2-256,hmac-sha2-512
ssh server key rsa 2048
ssh server key ecdsa 256
ssh server key dsa
Syntax
ssh server max-auth-tries { num-tries }
no ssh server max-auth-tries
Command Default
The default is 6 tries.
Parameters
num-tries
Maximum number of tries. Range of valid values is from 1 through 10.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to reset the default.
This command configures the maximum number of times a user is allowed to try authenticate to the
SSH server. When the number of attempts to log in to an SSH session is more than the defined value,
the session is terminated.
Examples
This example changes the maximum number of tries to 2.
device# configure terminal
device(config)# ssh server max-auth-tries 2
Syntax
ssh server max-idle-timeout { secs }
no ssh server max-idle-timeout
Command Default
By default, there is no timeout.
Parameters
secs
Maximum idle time in seconds. Range of valid values is from 1 through 14400.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to reset the default.
This command configures the maximum interval of time that the SSH session is allowed to idle. When
an SSH session is idle for a time defined by the idle timeout, the session is terminated.
Examples
This example changes the timeout to 15 seconds.
device# configure terminal
device(config)# ssh server max-idle-timeout 15
Syntax
ssh server max-login-timeout { secs }
no ssh server max-login-timeout
Command Default
The default is 120 seconds.
Parameters
secs
Maximum timeout in seconds. Range of valid values is from 1 through 120.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to reset the default.
This command configures the maximum timeout interval for the SSH session. When the loin prompt of
an SSH session is idle for a time defined by the log in timeout, the session is terminated.
Examples
This example changes the timeout to 60 seconds.
device# configure terminal
device(config)# ssh server max-login-timeout 60
Syntax
ssh server rekey-interval interval
no ssh server rekey-interval
Parameters
interval
The value for the rekey interval. Range is from 900 to 3600 seconds.
Modes
Global configuration mode
Usage Guidelines
Use the no ssh server rekey-interval command to remove the rekey-interval.
Syntax
ssh server { rekey-volume value}
no ssh server { rekey-volume value}
Command Default
The command default is 1024.
Parameters
rekey-volume value
The range of valid values is from 512 through 4095 megabytes. In FIPS mode, this value can not
exceed 1024.
Modes
Global configuration mode
Usage Guidelines
The no ssh server command resets to no rekeying.
Examples
Example of setting the rekey value to 768 megabytes.
device# configure terminal
device(config)# ssh server rekey-volume 768
Syntax
ssh server use-vrf vrf-name shutdown
no ssh server use-vrf vrf-name shutdown
Parameters
use-vrf vrf-name
Specifies a user-defined VRF or built-in VRFs such as mgmt-vrf or default-vrf.
Modes
Global configuration mode
Usage Guidelines
The no form of the command enables the SSH service.
The use of the use-vrf keyword brings down the server only for the specified VRF. You can shut down
any server in any VRF, including the management and default VRF.
Examples
This example shuts down the SSH service for a VRF.
device(config)# ssh server use-vrf myvrf shutdown
ssl-profile
Use the ssl-profile command to configure the lowest TLS version supported by the SLX software.
SLX uses OpenSSL to provide transport layer security and the current version of OpenSSL supports TLS
v 1.1 to TLS v 1.2. Since the SLX box can be considered as both a client as well as a server, you can apply
different supported TLS versions for each of these types. This ssl-profile command enables you to
select the SLX operation mode from either Client or Server and then set the lowest supported TLS
version.
Syntax
ssl-profile { client | server }
Parameters
client
Specifies that the configuration is for when the SLX is a client to another device.
server
Specifies that the configuration is for when the SLX acts as a server to other devices.
Modes
Management Security mode
Usage Guidelines
Opens and navigates into the specific configuration modes.
Examples
This example show how to navigate into the Client configuration mode inside the Management Security
mode.
SLX # conf term
Entering configuration mode terminal
SLX (config)#
SLX (config)# management-security
SLX (mgmt-security)# ?
SLX (mgmt-security)# ssl-profile ?
Possible completions:
client management security ssl profile client for tls configuration
server management security ssl profile server for tls configuration
ssm-enable
Enables Source Specific Multicast (SSM) mode for IPv4 PIM.
Syntax
ssm-enable range prefix-list
no ssm-enable range prefix-list
Command Default
By default, PIM-SSM is not enabled.
Parameters
range
Specifies the range of the SSM map. By default, the range is 232.0.0.0/8 for IPv4.
prefix-list
Specifies the IPv4 prefix list that identifies the multicast group address range.
Modes
Router PIM configuration mode
Usage Guidelines
PIM-SSM is a subset of the PIM-SM protocol. In PIM-SSM mode, the Shortest Path Tree (SPT) is created
at the source. The router closest to the receiver host is notified of the unicast IP address of the source
for the multicast traffic. PIM-SSM goes directly to the source-based distribution tree without the need of
the RP connection. In contrast to PIM-SM, PIM-SSM forms its own SPT, without forming a shared tree.
Examples
The following example enables SSM and applies the default IPv4 SSM range of 232.0.0.0/8.
device(config)# router pim
device(config-pim-router)# ssm-enable
The following example enables SSM and configures an SSM map at the global level.
device(config)# ip igmp ssm-map enable
device(config)# ip igmp ssm-map ssm-map-230-to-232 203.0.0.10
device(config)# ip igmp ssm-map ssm-map-233-to-234 204.0.0.10
The following example configures the SSM range at the router PIM configuration level.
start (CFM)
Defines the start time for a delay measurement receiver session.
Syntax
start { now | after HH:MM:SS | HH:MM:SS daily }
no start
Command Default
The start time is not defined
Parameters
now
The session is initiated immediately.
after HH:MM:SS
Initiates the one-way delay measurement receiver session after a period of time has elapsed, in
hours, minutes, and seconds.
HH:MM:SS daily
Initiates the one-way delay measurement receiver session at the specified time every day.
Modes
CFM protocol configuration mode
Usage Guidelines
The no start command deletes the start time.
Relative time is converted to absolute time. Otherwise, the system would not point to the expected time
after a reboot.
Examples
Example of starting the session after one hour and thirty minutes.
device(config-cfm-oneway-dm-receiver-1)# start after 01:30:00
start (Y1731)
Configure the start time.
Syntax
start at hh:mm:ss daily
start after hh:mm:ss daily
no start
Parameters:
at
Spcifies the time to start at.
hh:mm:ss
Specifies the time in hour, minute, and second format.
after
Specifies the measurement interval in minutes.
daily
Specifies time to start daily.
Command Default
The default value is start after 00:05:00 (After).
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the start configuration.
Examples
This example shows how to configure the start time.
device# configure terminal
device (config-cfm)# prtocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device(config-cfm-y1731-test-profile-my_test_profile)# tx-interval 60
device(config-cfm-y1731-test-profile-my_test_profile)# measurement-interval 30
device(config-cfm-y1731-test-profile-my_test_profile)# start at 00:00:00 daily
start-shell
Accesses the SLXVM Linux shell from the SLX-OS CLI.
Syntax
start-shell
Modes
Privileged EXEC mode
Usage Guidelines
This command is only available for users with admin-level permissions.
You can also run this command from Global configuration mode: device(config)# do start-
shell.
Inside the SLXVM Linux shell, you can escalate your privileges to root access, by using the su root
Linux command. Escalation to root access is password protected.
Inside the SLXVM Linux shell, execution of root privilege commands using sudo is not supported.
The idle timeout of Linux shell sessions is five minutes, after which you are automatically logged out of
the Linux shell and returned to the SLX-OS CLI.
Examples
The following example accesses the SLXVM Linux shell from the SLX-OS CLI.
device# start-shell
Entering Linux shell for the user: admUser
[admUser@SLX]#
The following example escalates access from the default SLXVM Linux shell to root.
[admUser@SLX]# su root
Password:
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
In the following example, the Linux ps -ef command lists the process status.
[admUser@SLX]# ps -ef
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Jul24 ? 00:00:04 /sbin/init
root 2 0 0 Jul24 ? 00:00:00 [kthreadd]
root 3 2 0 Jul24 ? 00:00:00 [migration/0]
...
The following example exits a root-level user to the SLXVM Linux shell.
[root@SLX]# exit
exit
[admUser@SLX]#
The following example exits from the SLXVM Linux shell to the SLX-OS CLI.
[admUser@SLX]# exit
exit
Exited from Linux shell
device#
static-network
Configures a static BGP4 network, creating a stable network in the core.
Syntax
static-network network/mask [ distance num ]
no static-network network/mask [ distance num ]
Parameters
network/mask
Network and mask in CIDR notation.
distance num
Specifies an administrative distance value for this network. Valid values range from 1 through
255. The default is 200.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
While a route configured with this command will never flap unless it is deleted manually, a static BGP4
network will not interrupt the normal BGP4 decision process on other learned routes that are installed
in the Routing Table Manager (RTM). Consequently, when there is a route that can be resolved, it will be
installed into the RTM.
Examples
The following example configures a static network and sets an administrative distance of 300.
statistics
Enables statistics on the tunnel interface.
Syntax
statistics
no statistics
Command Default
Statistics is disabled on a tunnel interface.
Modes
Interface tunnel configuration mode
Usage Guidelines
Use the no form of this command to disable statistics on the tunnel interface.
Note that traffic loss might occur when you enable or disable statistics on a tunnel interface.
Examples
This example enables statistics on the tunnel interface.
device# configure terminal
device (config)# interface tunnel 5
device(config-intf-tunnel-5)# statistics
Syntax
statistics
no statistics
Command Default
Statistics are disabled.
Modes
Bridge-domain configuration mode
Usage Guidelines
The no form of the command disables statistics on the bridge domain.
Examples
The following example shows how to enable ingress and egress statistics on bridge domain 2.
statistics (VLAN)
Enables statistics on a VLAN.
Syntax
statistics
no statistics
Command Default
Statistics are disabled.
Modes
VLAN configuration mode
Usage Guidelines
The no form of the command disables statistics on a VLAN.
Examples
The following example shows how to enable statistics on VLAN 10.
stop (CFM)
Defines the stop time for a delay measurement receiver session.
Syntax
stop { now | after HH:MM:SS | HH:MM:SS daily }
no stop
Command Default
The stop time is not defined
Parameters
now
The session is halted immediately.
after HH:MM:SS
Halts the one-way delay measurement receiver session after a period of time has elapsed, in
hours, minutes, and seconds.
HH:MM:SS daily
Halts the one-way delay measurement receiver session at the specified time every day.
Modes
CFM protocol configuration mode
Usage Guidelines
The no stop command deletes the stop time.
The one-way delay measurement receiver session should be started before starting the one-way delay
measurement Initiator session. Also, the one-way delay measurement Initiator session should be
stopped before stopping the one-way delay measurement Receiver session.
Relative time is converted to absolute time. Otherwise, the system would not point to the expected time
after a reboot.
Examples
Example of stopping the session after one hour and thirty minutes.
device(config-cfm-oneway-dm-receiver-1)# stop after 01:30:00
stop (Y1731)
Configure the stop time.
Syntax
stop [ at hh:mm:ss | after hh:mm:ss ]
no stop
Parameters:
at
Spcifies the time to stop at.
hh:mm:ss
Specifies the time in hour, minute, and second format.
after
Specifies the time to stop after.
Command Default
The default value is 01:05:00 (After).
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the stop configuration.
Examples
This example shows how to configure the stop time.
device# configure terminal
device (config-cfm)# protocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device(config-cfm-y1731-test-profile-my_test_profile)# tx-interval 60
device(config-cfm-y1731-test-profile-my_test_profile)# measurement-interval 30
device(config-cfm-y1731-test-profile-my_test_profile)# start at 00:00:00 daily
device(config-cfm-y1731-test-profile-my_test_profile)# stop at 23:59:00
Syntax
storm-control ingress { broadcast | unknown-unicast | multicast } limit-
bps rate
no storm-control ingress { broadcast | unknown-unicast | multicast }
Parameters
broadcast
Specifies that the command operates on broadcast traffic only.
unknown-unicast
Specifies that the command operates on unknown-unicast traffic only.
multicast
Specifies that the command operates on multicast traffic only.
limit-bps rate
Specifies that the value given to the rate parameter is in bits per second. If the traffic on the
interface reaches this rate, no more traffic (for the traffic type specified) is allowed on the
interface. For the rate, enter an integer from 0 to 10000000000. Because each application-
specific integrated circuit (ASIC) may support different bit granularity, bit rates are rounded up
to the next achievable rate.
Modes
Global configuration mode
Usage Guidelines
This command limits the amount of broadcast, unknown unicast, and multicast (BUM) ingress traffic
globally on all device interfaces when configured in global configuration mode.
If you want to modify an active BUM storm control configuration, you must first disable it, then issue the
storm-control ingress command again with the new parameters.
Enter no storm-control ingress to disable BUM storm control for a particular traffic type on the
interface.
Examples
The following example configures storm control on all Ethernet interfaces on the device with a rate
limited to 1000000 bps.
Syntax
storm-control ingress { broadcast | unknown-unicast | multicast } limit-
bps | rate
no storm-control ingress { broadcast | unknown-unicast | multicast }
Parameters
broadcast
Specifies that the command will operate on broadcast traffic only.
unknown-unicast
Specifies that the command will operate on unknown-unicast traffic only.
multicast
Specifies that the command will operate on multicast traffic only.
limit-bps
Specifies that the value given to the rate parameter is in bits per second. If the traffic on the
interface reaches this rate, no more traffic (for the traffic type specified) is allowed on the
interface.
rate
Specifies the amount of traffic allowed, either in bits per second or a percentage of the capacity
of the interface, depending on which parameter was chosen with the rate.
If you are specifying rate in bps, enter an integer from 0 to 10000000000. Because each
application-specific integrated circuit (ASIC) may support different bit granularity, bit rates are
rounded up to the next achievable rate.
If you are specifying rate in percent of interface capacity, enter an integer from 0 to 100.
Modes
Interface configuration mode
Usage Guidelines
This command limits the amount of broadcast, unknown unicast, and multicast (BUM) ingress traffic on
a specified interface.
If you want to modify an active BUM storm control configuration, you must first disable it, then issue the
storm-control ingress command again with the new parameters.
Enter no storm-control ingress to disable BUM storm control for a particular traffic type on an
interface.
Examples
This example configures storm control on an Ethernet interface, with a rate limited to 1000000 bps.
device(config)# interface ethernet 1/2
device(conf-if-eth-1/2)# storm-control ingress broadcast 1000000
subnet
Specifies the local IP address with the subnet mask of the routing device.
Syntax
subnet subnet_addr
no subnet subnet_addr
Command Default
The command is disabled by default.
Parameters
subnet_addr
Specifies the subnet mask of the IP address.
Modes
MPLS CSPF-group configuration mode
Usage Guidelines
When the command is configured, every link in the subnet is penalized.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures subnet 10.1.2.0 with a mask length of 24.
device# configure
device(config)# router mpls
device(config-router-mpls)# cspf-group group3
device(config-router-mpls-cspf-group-group3)# subnet 10.1.2.0/24
sub-ring
Configures a bridge as a sub-ring node for Ethernet Ring Protection (ERP) and specifies a parent ring
ID.
Syntax
sub-ring parent-ring-id id
no sub-ring parent-ring-id id
Command Default
A bridge is not configured as a sub-ring node by default.
Parameters
parent-ring-id id
Specifies a parent ring ID.
Modes
ERP configuration mode
Usage Guidelines
This command sets the major-ring or sub-ring, and optionally the ERP ID, that are associated with this
sub-ring. Both the parent and the sub-ring ERP instances can be configured with the same VLAN.
Examples
The following example sets the sub-ring and a parent-ring ID of 2.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# sub-ring parent-ring-id 2
summary-address (IS-IS)
Configures route summarization to aggregate Intermediate System-to-Intermediate System (IS-IS)
route information.
Syntax
summary-address ip-address subnet-mask level-1 [ level-2 ]
summary-address ip-address subnet-mask level-2 [ level-1 ]
no summary-address ip-address subnet-mask level-1 [ level-2 ]
no summary-address ip-address subnet-mask level-2 [ level-1 ]
Command Default
Disabled.
Parameters
ip-address
Specifies an IP address.
subnet-mask
Specifies a subnet mask.
level-1
Specifies that only routes redistributed into Level 1 are summarized with the configured address
and mask value.
level-2
Specifies that only routes redistributed into Level 2 are summarized with the configured address
and mask value.
Modes
IS-IS address-family IPv4 unicast configuration mode
Usage Guidelines
Route Summarization using this command is applicable only for redistributed routes.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures a summary address of 10.1.0.0 with a mask of 255.255.0.0 for Level 1
redistributed routes.
The following example configures a summary address of 10.1.0.0 with a mask of 255.255.0.0 for Level 2
redistributed routes.
The following example configures a summary address of 10.1.0.0 with a mask of 255.255.0.0 for Level 1
and Level 2 redistributed routes.
summary-address (OSPFv2)
Configures route summarization for redistributed routes for an Autonomous System Boundary Router
(ASBR).
Syntax
summary-address A.B.C.D E.F.G.H
no summary-address
Command Default
Summary addresses are not configured.
Parameters
A.B.C.D E.F.G.H
IP address and mask for the summary route representing all the redistributed routes in dotted
decimal format.
Modes
OSPF router configuration mode
Usage Guidelines
Use this command to configure an ASBR to advertise one external route as an aggregate for all
redistributed routes that are covered by a specified address range. When you configure an address
range, the range takes effect immediately. All the imported routes are summarized according to the
configured address range. Imported routes that have already been advertised and that fall within the
range are flushed out of the AS and a single route corresponding to the range is advertised.
If a route that falls within a configured address range is imported by the device, no action is taken if the
device has already advertised the aggregate route; otherwise the device advertises the aggregate route.
If an imported route that falls within a configured address range is removed by the device, no action is
taken if there are other imported routes that fall within the same address range; otherwise the
aggregate route is flushed.
The device sets the forwarding address of the aggregate route to 0 and sets the tag to 0. If you delete
an address range, the advertised aggregate route is flushed and all imported routes that fall within the
range are advertised individually. If an external link-state-database-overflow condition occurs, all
aggregate routes and other external routes are flushed out of the AS. When the device exits the
external LSDB overflow condition, all the imported routes are summarized according to the configured
address ranges.This parameter affects only imported, type 5 external routes.
Examples
The following example configures a summary address of 10.1.0.0 with a mask of 10.255.0.0. Summary
address 10.1.0.0, includes addresses 10.1.1.0, 10.1.2.0, 10.1.3.0, and so on. For all of these networks, only
the address 10.1.0.0 is advertised in external LSAs:
summary-address (OSPFv3)
Configures route summarization for redistributed routes for an Autonomous System Boundary Router
(ASBR).
Syntax
summary-address IPv6-addr/mask
no summary-address
Command Default
Summary addresses are not configured.
Parameters
A:B:C:D/LEN
IPv6 address and mask for the summary route representing all the redistributed routes in dotted
decimal format.
Modes
OSPFv3 router configuration mode
Usage Guidelines
Use this command to configure an ASBR to advertise one external route as an aggregate for all
redistributed routes that are covered by a specified IPv6 address range. When you configure an address
range, the range takes effect immediately. All the imported routes are summarized according to the
configured address range. Imported routes that have already been advertised and that fall within the
range are flushed out of the AS and a single route corresponding to the range is advertised.
If a route that falls within a configured address range is imported by the device, no action is taken if the
device has already advertised the aggregate route; otherwise the device advertises the aggregate route.
If an imported route that falls within a configured address range is removed by the device, no action is
taken if there are other imported routes that fall within the same address range; otherwise the
aggregate route is flushed.
The device sets the forwarding address of the aggregate route to 0 and sets the tag to 0. If you delete
an address range, the advertised aggregate route is flushed and all imported routes that fall within the
range are advertised individually. If an external link-state-database-overflow condition occurs, all
aggregate routes and other external routes are flushed out of the AS. When the device exits the
external LSDB overflow condition, all the imported routes are summarized according to the configured
address ranges.
Examples
The following example configures a summary address of 2001:db8::/24 for routes redistributed into
OSPFv3. The summary prefix 2001:db8::/24 includes addresses 2001:db8::/1 through 2001:db8::/24.
Only the address 2001:db8::/24 is advertised in an external link-state advertisement.
summary-prefix
Configures summary prefixes to aggregate IPv6 Intermediate System-to-Intermediate System (IS-IS)
route information.
Syntax
summary-prefix ipv6-prefix prefix-length { level-1 | level-2 }
no summary-prefix ipv6-prefix prefix-length { level-1 | level-2 }
Command Default
Disabled.
Parameters
ipv6-prefix prefix-length
Specifies the aggregate address. You must specify the ipv6-prefix parameter in hexadecimal
using 16-bit values between colons as documented in RFC 2373. You must specify the prefix-
length parameter as a decimal value. A slash mark (/) must follow the ipv6-prefix
parameter and precede the prefix-length parameter.
level-1
Specifies that only routes redistributed into Level 1 are summarized
level-2
Specifies that only routes redistributed into Level 2 are summarized.
Modes
IS-IS address-family IPv6 unicast configuration mode
Usage Guidelines
IS-IS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Route Summarization using this command is applicable only for redistributed routes.
Examples
The following example configures a summary prefix of 2001:db8::/32 to be advertised to Level 1
redistributed routes only.
device# configure terminal
device(config)# router isis
device(config-isis-router)# address-family ipv4 unicast
device(config-router-isis-ipv4u)# summary-prefix 2001:db8::/32 level-1
support autoupload-param
Defines autoupload parameters.
Syntax
support autoupload-param hostip hostip | user user_acct | password
password [ protocol [ ftp | scp | sftp ] directory path
Parameters
hostip host-ip
Specifies the IP address of the remote host.
user user_acct
Specifies the user name to access the remote host.
password password
Specifies the password to access the remote host.
protocol FTP | SCP| SFTP
Specifies the protocol used to access the remote server.
directory path
Specifies the path to the directory.
Modes
Global configuration mode
Examples
device(config)# support autoupload-param hostip 10.31.2.27 protocol [ftp|scp |
sftp]username hegdes directory /uers/home40/hegdes/autoupload password
(<string>): *****
suppress-arp
Enables Address Resolution Protocol (ARP) suppression on a current VLAN or bridge domain. ARP
suppression can lessen ARP-related traffic within an IP Fabric.
Syntax
suppress-arp
no suppress-arp
Command Default
ARP suppression is disabled.
Modes
VLAN configuration mode
Usage Guidelines
This feature is required, along with ND suppression, if static anycast gateway is supported in an IP
Fabric.
Examples
The following example enables ARP suppression on a VLAN.
device# configure terminal
device(config)# vlan 100
device(config-vlan-100)# suppress-arp
suppress-nd
Enables Neighbor Discovery (ND) suppression on a VLAN or bridge domain. ND suppression can lessen
the amount of ND control traffic within an IP Fabric.
Syntax
suppress-nd
no suppress-nd
Command Default
ND suppression is disabled.
Modes
VLAN configuration mode
Usage Guidelines
This feature is required, along with ARP suppression, if static anycast gateway is supported in an IP
Fabric.
Examples
The following example enables ND suppression on a specified VLAN.
device# configure terminal
device(config)# vlan 100
device(config-vlan-100)# suppress-nd
switch-attributes
Configures the chassis or host name for the device.
Syntax
switch-attributes [ chassis-name chassis-name ] [ host-name host-name ]
switch-attributes [ chassis-name ][host-name ]
Command Default
The default host name is SLX.
Parameters
chassis-name chassis-name
Specifies the chassis name. A chassis name can be from 1 through 30 characters long, must
begin with a letter, and can contain letters, numbers, and underscore characters.
host-name host-name
Specifies the host name and changes the CLI prompt. A host name can be from 1 through 30
characters long. It must begin with a letter, and can contain letters, numbers, and underscore
characters.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to reset the default settings.
We recommend that you customize the chassis name for each device. Some system logs identify the
device by its chassis name; if you assign a meaningful chassis name, logs are more useful.
Examples
The following example configures the chassis and host names.
device# configure terminal
device(config)# switch-attributes chassis-name SLX-market1
device(config)# switch-attributes host-name SLX-mrkt
SLX-mrkt(config)#
switchport
Puts the interface in Layer 2 mode and sets the switching characteristics of the Layer 2 interface.
Syntax
switchport
no switchport
Command Default
All Layer 2 interfaces are mapped to default VLAN 1 and the interface is set to access mode.
Modes
Interface subtype configuration mode
Usage Guidelines
For changing the interface configuration mode to trunk or changing the default VLAN mapping, use
additional switchport commands.
To redefine the switch from Layer 2 mode into Layer 3 mode, enter no switchport.
Examples
To put a specific Ethernet interface in Layer 2 mode:
device# configure terminal
switch(config)# interface ethernet 1/9
switch(conf-if-eth-1/9)# switchport
switchport access
Sets the Layer 2 interface as access.
Syntax
switchport access { vlan vlan_id}
no switchport access { vlan vlan_id}
Command Default
All Layer 2 interfaces are in access mode and belong to the VLAN ID 1.
Parameters
vlan vlan_id
Sets the port VLAN (PVID) to the specified vlan_id. Range is below 4090 for 802.1Q VLANs.
Modes
Interface subtype configuration mode on edge ports
Usage Guidelines
In access mode, the interface only allows untagged and priority tagged packets.
Enter no switchport access vlan to set the PVID to the default VLAN 1.
Examples
To set the Layer 2 interface PVID to 100 on a specific Ethernet interface:
device# configure terminal
switch(config)# interface ethernet 1/9
switch(conf-if-eth-1/9)# switchport access vlan 100
switchport mode
Sets the mode of the Layer 2 interface.
Syntax
switchport mode { access | trunk }
Parameters
access
Sets the Layer 2 interface as access. Access mode assigns the port to a VLAN
trunk
Sets the Layer 2 interface as trunk. Trunk mode makes the port linkable to other switches and
routers
Modes
Interface subtype configuration mode
Usage Guidelines
You must configure the same native VLAN on both ends of an 802.1 or classified VLAN trunk link.
Failure to do so can cause bridging loops and VLAN leaks.
Examples
To set the mode of a specific Ethernet interface to access:
device# configure terminal
switch(config)# interface ethernet 1/9
switch(conf-if-eth-1/9)# switchport mode access
Syntax
switchport mode trunk-no-default-native
Modes
Interface configuration mode
Usage Guidelines
By assigning this mode, you can configure an untagged logical interface on the specified port. The
device discards any ingress tagged or untagged packet until a switchport classification or native VLAN
classification is configured.
To disable this functionality, issue the no switchport command, or enter a different switchport
mode by using the switchport mode access command or the switchport mode trunk
command.
Before you change the switch port mode from switchport mode access with an explicit
switchport access vlan to switchport mode trunk-no-default-native, you must
enter the no switchport command on the interface level, and then enter the switchport
command to set the interface as a switchport. Now you can configure the switchport mode
trunk-no-default-native command.
Port mode change is not allowed when port security is enabled on the interface.
This is the fundamental difference between this command and the switch mode trunk command,
which implicitly creates VLAN 1 on the port.
The global command dot1q tag native-vlan does not affect the ingress or egress tagging
behavior of the native VLAN configured in this mode.
The following native VLAN commands that are supported in regular trunk mode are NOT supported in
this mode:
• switchport trunk tag native-vlan
• switchport trunk native-vlan
Examples
The following example configures a trunk port without a default native VLAN, then explicitly configures
the native VLAN.
device# configure terminal
device(config)# interface ethernet 0/1
device(config-if-eth-0/1)# switchport mode trunk-no-default-native
device(config-if-eth-0/1)# switchport trunk tagged
switchport port-security
Enables port security on an interface port.
Syntax
switchport port-security
no switchport port-security
Command Default
Port security is not enabled.
Modes
Interface configuration mode
Usage Guidelines
Port mode change is not allowed when port security is enabled on the interface.
Examples
The following example enables port MAC security on an interface:
device(config)# interface Ethernet 3/2
device(conf-if-eth-3/2)# switchport
device(conf-if-eth-3/2)# switchport port-security
Syntax
switchport port-security mac-address address vlan vlan_id
Command Default
MAC address is not configured for port security.
Parameters
mac-address address
Specifies the MAC address-based VLAN classifier rule used to map to a specific VLAN.
vlan vlan_id
Specifies a VLAN.
Modes
Interface configuration mode
Usage Guidelines
Static MAC addresses cannot be configured on a secure port. They must be configured as secure MAC
addresses on the secure port.
When static MAC address is configured on an access secure port, the MACs qualify for access VLANs,
but on trunk port, VLAN must be specified.
Examples
The following example configures static MAC address for port security on an interface:
device(config)# interface Ethernet 3/2
device(conf-if-eth-3/2)# switchport
device(conf-if-eth-3/2)# switchport port-security mac-address 0000.00eb.2d14 vlan 2
Syntax
switchport port-security max value
no switchport port-security max
Parameters
value
The maximum number of secure MAC addresses. Range is from 1 through 8192.
Command Default
The default value is 8192 MAC addresses.
Modes
Interface configuration mode
Usage Guidelines
The maximum MAC address limit for sticky MAC address and static MAC address depends on the device
limit. For dynamically learned MAC addresses, the maximum limit is 8192 per port.
The no switchport port-security max command restores the default value of maximum
number of MAC addresses.
Examples
The following example configures the maximum number of MAC addresses used for port MAC security
on an interface port as 10:
device(config)# interface Ethernet 3/2
device(conf-if-eth-3/2)# switchport
device(conf-if-eth-3/2)# switchport port-security max 10
Syntax
switchport port-security shutdown-time time
Command Default
Auto recovery of ports is not enabled.
Parameters
time
The amount of time in minutes, the port waits before it recovers from forced port shutdown.
Range is from 1 through 15.
Modes
Interface configuration mode
Usage Guidelines
The shutdown and no-shutdown processes initiated as part of the port violation action is independent
of the shutdown process explicitly initiated by an administrator on the same port on which port MAC
security is enabled.
If a port security-based change occurs when a port is shut down, the shutdown timer is not triggered.
Consequently, the user must restore the full functionality of the port.
When port security violation causes a port to be shut down and the user manually changes the
shutdown time, the shutdown timer is reset and the timer starts with the new shutdown time.
Examples
The following example configures the auto recovery time as 4 minutes for ports that shuts down
following a port security violation on an interface.
device(config)# interface Ethernet 3/2
device(conf-if-eth-3/2)# switchport
device(conf-if-eth-3/2)# switchport port-security shutdown-time 4
Syntax
switchport port-security sticky [ mac-address address vlan vlan_id ]
no switchport port-security sticky [ mac-address address vlan vlan_id ]
Command Default
Sticky MAC learning on the port is not enabled.
Parameters
mac-address address
Specifies the MAC address-based VLAN classifier rule used to map to a specific VLAN.
vlan vlan_id
Specifies a VLAN.
Modes
Interface configuration mode
Usage Guidelines
When sticky MAC learning is enabled on a secured port, the interface converts all the dynamic secure
MAC addresses, including those that were dynamically learned before sticky learning was enabled, to
sticky secure MAC addresses. All the subsequent sets of dynamically learned MAC addresses will also be
converted to sticky secure MAC addresses.
The no switchport port-security sticky disables sticky MAC learning on a secure port, and
all the sticky MAC addresses will be converted back to dynamically learned MAC addresses.
Sticky MAC addresses persist even if the port goes down or if the device reboots.
Examples
The following example enables sticky MAC learning on the port and configures port security with sticky
MAC address:
device(config)# interface Ethernet 3/2
device(conf-if-eth-3/2)# switchport
device(conf-if-eth-3/2)# switchport port-security sticky
device(conf-if-eth-3/2)# switchport port-security sticky mac-address 0000.0018.747C vlan 5
Syntax
switchport port-security violation shutdown
Command Default
The port shuts downs if port security violation occurs.
Parameters
shutdown
Puts the interface into the error-disabled state.
Modes
Interface configuration mode
Usage Guidelines
If a MAC address already learned on a secured port ingresses on a non-secured port or through another
secured port, it is not considered security violation. In this scenario, MAC movement happens if it is a
dynamically learned MAC address. If it is a static MAC address or sticky MAC address, MAC movement
does not happen, but the traffic is switched (flooded or forwarded) based on the destination MAC
address.
If the port shuts down after security violation, an administrator can explicitly bring up the interface or a
shutdown timer can be configured using the switchport port-security shutdown-time
command. After the configured shutdown time, the interface automatically comes up and the port
security configuration remains configured on the port.
When the device reboots after port shutdown due to security violation, the ports come up in the
shutdown state.
Examples
The following example configures the violation response action as shutdown for port security on an
interface:
device(config)# interface Ethernet 3/2
device(conf-if-eth-3/2)# switchport
device(conf-if-eth-3/2)# switchport port-security violation shutdown
Syntax
switchport trunk allowed { vlan } { add vlan_id | all | except vlan_id |
none | remove vlan_id }
Parameters
add vlan_id
Adds a VLAN to transmit and receive through the Layer 2 interface. The VLAN can be an 802.1Q
VLAN.
all
Allows only 802.1Q VLANs to transmit and receive through the Layer 2 interface. This keyword
does not apply to classified or transport VLANs.
except vlan_id
Allows only 802.1Q VLANs except the specified VLAN ID to transmit and receive through the
Layer 2 interface.
none
Allows only 802.1Q VLANs to transmit and receive through the Layer 2 interface. This keyword
does not apply to service or transport VFs.
remove vlan_id
Removes a VLAN that transmits and receives through the Layer 2 interface.
Modes
Interface subtype configuration mode
Usage Guidelines
Examples
To add the tagged VLAN 100 to a specific Ethernet interface:
device# configure terminal
switch(config)# interface ethernet 0/9
switch(conf-if-eth-0/9)# switchport trunk allowed vlan add 100
Syntax
switchport trunk native-vlan-untagged vlan_id
no switchport trunk native-vlan-untagged
Parameters
vlan_id
Adds a classified VLAN (VLAN ID > 4095) to transmit and receive through the Layer 2 interface.
Modes
Interface subtype configuration mode on a trunk port
Usage Guidelines
This command is supported when the port is in no-default-vlan trunk mode, as enabled by means of the
switchport mode trunk-no-default-native command.
Port mode change is not allowed when port security is enabled on the interface.
Examples
Configure untagged native VLAN 5000, allow VLAN 6000, and make VLAN 7000 the default VLAN.
device# configure terminal
device(config)# interface ethernet 0/1
device(config-if-eth-0/1)# switchport mode trunk-no-default-native
device(config-if-eth-0/1)# switchport trunk native-vlan untagged 5000
device(config-if-eth-0/1)# switchport trunk add vlan 6000 ctag 100-200
device(config-if-eth-0/1)# switchport trunk default-vlan 7000
Syntax
switchport trunk native-vlan-xtagged vlan_id [ ctag cvid ] egress
{ tagged | untagged | any }
no switchport trunk native-vlan-xtagged
Parameters
vlan_id
Adds a classified VLAN (VLAN ID > 4095) to transmit and receive through the Layer 2 interface.
ctag cvid
Sets an optional C-TAG (802.1Q VLAN ID) for a service or transport VF (VLAN ID > 4095).
egress
Enables the selection of required tagging options.
tagged
Specifies packets as tagged.
untagged
Specifies packets as untagged.
any
Specifies that packets preserve their ingress encapsulation.
Modes
Interface subtype configuration mode on a trunk port
Usage Guidelines
This command is supported when the port is in no-default-vlan trunk mode, as enabled by means of the
switchport mode trunk-no-default-native command.
Port mode change is not allowed when port security is enabled on the interface.
Examples
Configure transport VF 6000 that accepts C-TAG range 100 through 200 and a native VLAN that can
be either tagged or untagged.
device# configure terminal
device(config)# interface ethernet 0/1
device(config-if-eth-0/1)# switchport mode trunk-no-default-native
device(config-if-eth-0/1)# switchport trunk native-vlan-xtagged 6000 ctag 10 egress any
device(config-if-eth-0/1)# switchport trunk allow vlan 6000 ctag 100-200
Syntax
switchport trunk tag native-vlan
no switchport trunk tag native
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no switchport trunk tag native to untag native traffic for a specific interface.
Examples
To enable tagging for native traffic on a specific Ethernet interface:
device# configure terminal
switch(config)# interface ethernet 0/9
switch(conf-if-eth-0/9)# switchport trunk tag native-vlan
sync-interval
Configures the interval between Precision Time Protocol (PTP) synchronization (Sync) messages on an
interface.
Syntax
sync-interval seconds
no sync-interval
Command Default
See Parameters.
Parameters
seconds
Interval between PTP Synch messages, in log seconds. Range is -4 through 2. The default is -1 (2
packets/second). See the Usage Guidelines. Range is -4 through 2. The default is -1 (2 packets/
second).
Modes
PTP configuration mode
Usage Guidelines
The inputs for interval represent base 2 exponents, where the packet rate is 1/(2log seconds).
Configuring this interval on an edge port overrides the switch (global) default.
Important
Do not configure a rate slower than the default on links between SLX devices.
Examples
To configure a PTP Sync interval of 2 on an Ethernet interface:
device# configure terminal
device(config)# interface ethernet 0/1
device(conf-if-eth-0/1)# protocol ptp
device(conf-if-eth-0/1-ptp)# sync-interval 2
sysmon fe-acces-check
Configures system error monitoring.
Syntax
sysmon fe-access-check [ action | disable | poll-interval | recovery-
threshold | threshold]
Parameters
action
Sets Fe-Access-Check action.
disable
Disables the Fe Access Check.
poll-interval
Sets the Fe-Access-Check poll-interval.
recovery-threshold
Sets the Fe-Access-Check recovery threshold.
threshold
sets the Fe-Access-Check threshold.
Modes
Global configuration mode
Usage Guidelines
By default, the Fe access check is disabled. The default recovery threshold is 1 and the default threshold
is 3. The default action is log, which logs the FE acces errors.
Examples
device(config)# sysmon fe-access-check ?
Possible completions:
action Set Fe-Access-Check action
disable Disable Fe Access Check (Default: Enabled)
poll-interval Set Fe-Access-Check poll-interval
recovery-threshold Set Fe-Access-Check recovery threshold
threshold Set Fe-Access-Check threshold
device(config)# sysmon fe-access-check recovery-threshold ?
Possible completions:
<1-3> Default: 1
device(config)# sysmon fe-access-check recovery-threshold 2
device(config)# sysmon fe-access-check threshold?
Possible completions:
threshold Set Fe-Access-Check threshold
device(config)# sysmon fe-access-check threshold ?
Possible completions:
<1-10> Default: 3
device(config)# sysmon fe-access-check threshold 5
device(config)# sysmon fe-access-check action ?
Possible completions:
log Log FE access error (Default action)
recover Recover FE
device(config)# sysmon fe-access-check action log ?
Possible completions:
<cr>
device(config)# sysmon fe-access-check action log?
Possible completions:
log Log FE access error (Default action)
device(config)# sysmon fe-access-check recover ?
Possible completions:
<1-3> Default is 1
device(config)# sysmon fe-access-check recover 2
sysmon link-crc-monitoring
Enables link CRC monitoring.
Syntax
sysmon sfm-walk [ auto | disable-redundancy-check | poll-interval |
threshold]
Parameters
action
Sets Link CRC Monitoring actions.
disable
Disables link CRC Monitoring.
poll-interval
Sets link CRC monitoring poll-interval.
threshold
Sets link CRC Monitoring threshold.
Modes
Global configuration mode
Usage Guidelines
By default, link-crc monitoring is disabled. Default threshold is 5 and default poll-interval is 60 seconds.
Examples
device(config)# sysmon link-crc-monitoring ?
Possible completions:
action Set Link CRC Monitoring action
disable Disable Link CRC Monitoring (Default: Enabled)
poll-interval Set Link CRC Monitoring poll-interval
threshold Set Link CRC Monitoring threshold
device(config)# sysmon link-crc-monitoring threshold ?
Possible completions:
<1-10> Default: 5
device(config)# sysmon link-crc-monitoring threshold 9
device(config)# sysmon link-crc-monitoring poll-interval ?
Possible completions:
<1-300> Default: 60 Sec
device(config)# sysmon link-crc-monitoring poll-interval 500
sysmon sfm-walk
Enables SFM walk.
Syntax
sysmon sfm-walk [ auto | disable-redundancy-check | poll-interval |
threshold]
Parameters
auto
Enable auto SFM walk.
disable-redundancy-check
Disables SFM Walk redundancy check.
poll-interval
Sets SFM Walk poll-interval.
threshold
Sets SFM Walk reassembly error threshold.
Modes
Global configuration mode
Usage Guidelines
By default, SFM walk and redundancy check are disabled.
Examples
device(config)# sysmon sfm-walk ?
Possible completions:
auto Enable Auto SFM Walk (Default: Disabled)
disable-redundancy-check Disable SFM Walk redundancy check (Default:
Enabled)
poll-interval Set SFM Walk poll-interval
threshold Set SFM Walk reassembly error threshold
device(config)# sysmon sfm-walk auto?
Possible completions:
auto Enable Auto SFM Walk (Default: Disabled)
device(config)# sysmon sfm-walk auto ?
Possible completions:
<cr>
device(config)# sysmon sfm-walk disable-redundancy-check?
Possible completions:
disable-redundancy-check Disable SFM Walk redundancy check (Default:
Enabled)
device(config)# sysmon sfm-walk disable-redundancy-check ?
Possible completions:
<cr>
system maintenance
Accesses config-system-maintenance sub-mode, enters system maintenance mode, configures
the convergence time for redirecting traffic to the maintenance mode node, or configures entering
system maintenance mode after a reboot.
Syntax
system maintenance { enable | convergence-time seconds | [no]enable-on-
reboot}
no system maintenance
Command Default
By default, system maintenance mode is not enabled.
Parameters
enable
Enables system maintenance mode.
convergence-time seconds
Specifies the number of seconds allowed per stage of the convergence of traffic to the
maintenance mode node. Valid values range from 100 through 500. The default is 100.
enable-on-reboot
When configured, the system comes up in maintenance mode after reboot.
Modes
Privileged EXEC mode
Config-system-maintenance sub-mode
Usage Guidelines
Planned maintenance operations such as software upgrade, SFP replacement, cable replacement, and
node replacement can require the device to be shut down or restarted, resulting in traffic disruption
even if alternative paths are available. Maintenance mode provides graceful traffic diversion to
alternative traffic paths, helping to minimize traffic loss during such planned operations.
When an alternative path is available, the BGP and MCT protocols redirect traffic away from the node
that is going into maintenance mode. When maintenance mode is enabled, all protocols that are
running on the maintenance mode node are notified and redirection of traffic (convergence) begins in
stages.
The enable-on-reboot parameter allows the device to enter maintenance mode after a reboot,
allowing any network errors detected with EFA to be addressed, and the device added back to the
network.
The no form of the command disables automatically entering maintenance mode after a reboot.
Maintenance mode is not supported for the following features: BGP address-family, Flowspec, Layer 3
VPN, VPLS, and VLL (virtual leased line).
Examples
The following example enables system maintenance mode and specifies a convergence time of 120
seconds.
device# configure terminal
device(config)# system
device(config-system)# maintenance
device(config-system-maintenance)# enable
device(config-system-maintenance)# convergence-time 120
Syntax
system maintenance turn-off
Parameters
system maintenance turn-off
Brings device out of maintenance mode when enable-on-reboot is used to reboot the
device into maintenance mode.
Modes
Operational mode.
Examples
The following example brings the device out of maintenance mode.
device# system maintenance turn-off
device#
system-description
Sets the global system description specific to LLDP.
Syntax
system-description line
no system-description
Parameters
line
Specifies a description for the LLDP system. The string must be between 1 and 50 ASCII
characters in length.
Modes
Protocol LLDP configuration mode
Usage Guidelines
Enter no system-description to clear the global LLDP system description.
Examples
To set the global system description specific to LLDP on the SLX-OS platform, enter the following:
system-monitor tm
Accesses system monitor traffic manager (sys-mon TM) configuration mode to configure the
monitoring of the traffic manager (TM) device or Virtual Output Queue (VOQ) discarded packets.
Syntax
system-monitor tm
no system-monitor tm
Modes
Global configuration mode
Usage Guidelines
By default, the monitoring of the TM device and VOQ discarded packets is disabled until you configure
their threshold.
Use the no form of this command to reset the monitoring of the TM device and VOQ discarded packets
configurations to their default values and disable the monitoring of the packets.
Examples
The following example enables VOQ discarded packets monitoring and accesses sys-mon TM
configuration mode.
device# configure terminal
device (config)# system-monitor tm
device (config-sys-mon-tm)#
system-monitor-mail
Configures various email settings as part of system monitoring.
Syntax
system-monitor-mail [ fru | interface | relay | security |sfp]
Parameters
fru
Configure FRU mail settings.
interface
Configure interface mail settings.
relay
Configure relay ip mail settings.
security
Cconfigure security mail settings.
sfp
Configure sfp mail settings.
Modes
Global configuration mode
Examples
device(config)# system-monitor-mail ?
Possible completions:
fru Configure FRU mail settings
interface Configure interface mail settings
relay Configure relay ip mail settings
security Configure security mail settings
sfp Configure sfp mail settings
device(config)# system-monitor-mail fru ?
Possible completions:
<email:string> e-mail address for FRU alerts
enable Enable FRU email alerts
device(config)# system-monitor-mail fru enable ?
Possible completions:
<cr>
device(config)# system-monitor-mail fru enable?
Possible completions:
enable Enable FRU email alerts
device(config)# system-monitor-mail fruemail ?
^
% Invalid input detected at '^' marker.
device(config)# system-monitor-mail fru email ?
Possible completions:
<cr>
Syntax
system-monitoring power alert state removed action raslog
Parameters
Alert
Configures alerts for the POWER SUPPLY component.
State
Specifies the supported states for component (power supply) that may be monitored.
action
Specifies the action that may be taken when component (power supply) changes from the
configured state.
Modes
Global configuration mode
Examples
device(config)# system-monitor power ?
Possible completions:
alert Configure alerts for component:POWER SUPPLY
threshold Configure threshold for component:POWER SUPPLY
device(config)# system-monitor power alert ?
Possible completions:
action Action that may be taken when component:POWER SUPPLY changes
configured state
state Supported states for component: POWER-SUPPLY that may be monitored
device(config)# system-monitor power alert state ?
Possible completions:
[removed] all faulty inserted none on removed
device(config)# system-monitor power alert state removed ?
Possible completions:
action Action that may be taken when component:POWER SUPPLY changes
configured state
<cr>
device(config)# system-monitor power alert state removed action ?
Possible completions:
[raslog] all email none raslog
device(config)# system-monitor power alert state removed action raslog ?
Possible completions:
<cr>
device(config)# system-monitor power alert state removed action raslog
system power-cycle-db-shutdown
Shuts down the chassis configuration database gracefully without restarting the device for a planned
power-cycle.
Syntax
system power-cycle-db-shutdown
Command Default
The chassis configuration database is running normally.
Modes
Global configuration mode
Usage Guidelines
When devices encounter abrupt power cycles, there have been rare cases of device configuration
database corruption. This database corruption causes the device to reboot and reverts the device to the
startup configuration.
This command shuts down the chassis configuration database, without rebooting the device. All
commands (except for the reload command) are blocked on this node until the node is restarted.
Note
Suppose the configuration database on a switch gets corrupted due to an abrupt power cycle,
run the firmware install or the write erase commands to clean up the corrupted
files and/or to reinstall the firmware.
The node is not fully functional until it restarts. This command should be run as part of any planned
power outages.
Examples
device# configure terminal
device(config)# system power-cycle-db-shutdown
Are you sure you want to shutdown database for power-cycle? [y/n]: y
2017/02/09-13:02:42, [DCM-1015], 51,, INFO, SLX9140, Switch is prepared for power-cycle.
No clis will work henceforth. Need power-cycle or reload to make switch fully functional.
Operation Successful.
system-name
Sets the global system name specific to LLDP.
Syntax
system-name name
no system-name
Command Default
The host name from the device is used.
Parameters
name
Specifies a system name for the LLDP. The string must be between 1 and 32 ASCII characters in
length.
Modes
Protocol LLDP configuration mode
Usage Guidelines
Enter no system-name to delete the name.
Examples
To specify a system name for the LLDP:
table-map
Maps external entry attributes into the BGP routing table, ensuring that those attributes are preserved
after being redistributed into OSPF.
Syntax
table-map string
no table-map string
Command Default
This option is disabled.
Parameters
string
Specifies a route map to be whose attributes are to be preserved. Range is from 1 through 63
ASCII characters.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of the command to remove the table map.
Use this command only to set the tag values. Normally, a route map is applied on routes (and therefore
the routes are updated) before it is stored in the BGP routing table. Use the table-map command to
begin the update before the routes are stored in the IP routing table.
Route maps that contain set statements change values in routes when the routes are accepted by the
route map. For inbound route maps (route maps that filter routes received from neighbors), the routes
are changed before they enter the BGP routing table. For tag values, if you do not want the value to
change until a route enters the IP routing table, you can use a table map to change the value. A table
map is a route map that you have associated with the IP routing table. The device applies the set
statements for tag values in the table map to routes before adding them to the routing table. To
configure a table map, you first configure the route map, then identify it as a table map. The table map
does not require separate configuration. You can have only one table map.
Note
Use table maps only for setting the tag value. Do not use table maps to set other attributes.
To set other route attributes, use route maps or filters. To create a route map and identify it as
a table map, enter commands such those shown in the first example below. These commands
create a route map that uses an address filter. For routes that match the IP prefix list filter, the
route map changes the tag value to 100 and is then considered as a table map. This route
map is applied only to routes that the device places in the IP routing table. The route map is
not applied to all routes. The first example below assumes that IP prefix list p11 has already
been configured.
Examples
This example illustrates the execution of the table-map command.
This example removes the table map for the default VRF.
tacacs-server
Configures a Terminal Access Controller Access-Control System plus (TACACS+) server.
Syntax
tacacs-server { host hostname }[ use-vrf { mgmt-vrf | default-vrf |vrf-
name } ] [ port portnum ] [ protocol { chap | pap } ] [ key shared-
secret ] [ encryption-level value_level ] [ timeout secs ] [ retries
num ] [ source-interface ip-address ]
no tacacs-server { host hostname } [ use-vrf { mgmt-vrf | default-vrf |
vrf-name } ] [ port portnum ] [ protocol { chap | pap}] [ key shared-
secret ] [ encryption-level value-level ] [ timeout secs ] [ retries
num ] [ source-interface ip-address ]
Command Default
See the Parameters section for specific defaults.
Parameters
host hostname
Specifies the IP address or domain name of the TACACS+ server. IPv4 and IPv6 addresses are
supported.
use-vrf
Specifies a VRF though which to communicate with the TACACS+ server. See the Usage
Guidelines.
mgmt-vrf
Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf-name
Specifies a VRF name.
source-interface ip-address
Specifies the source interface for the TACACS host.
port portnum
Specifies the TCP port for authentication. Valid values range from 0 through 65535. The default
is 49.
protocol { chap | pap}
Specifies the authentication protocol. Options include CHAP and PAP. The default is CHAP.
key shared-secret
Specifies the text string that is used as the shared secret between the device and the TACACS+
server to make the message exchange secure. The key must be between 1 and 40 characters in
length.
The default key is sharedsecret. The exclamation mark (!) is supported in RADIUS and
TACACS+ servers. You can specify the password in either double quotes or the escape character
(\), for example "secret!key" or secret\!key. The only other valid characters are
alphanumeric characters (a-z and 0-9) and underscores. No other special characters are allowed.
encryption-level value_level
Designates the encryption level for the shared secret key operation. This operand supports JITC
certification and compliance. The valid values are 0 and 7, with 0 being clear text and 7 being the
most heavily encrypted. The default value is 7.
timeout secs
Specifies the time to wait for the TACACS+ server to respond. The default is 5 seconds.
retries num
Specifies the number of attempts allowed to connect to a TACACS+ server. The default is 5
attempts.
Modes
Global configuration mode
Usage Guidelines
If a TACACS+ server with the specified IP address or host name does not exist, it is added to the server
list. If the TACACS+ server already exists, this command modifies the configuration. The key parameter
does not support an empty string.
Use the no form of the command to reset the specified attributes to their default values.
Before downgrading to a software version that does not support the encryption-level keyword,
set the value of this keyword to 0. Otherwise, the firmware download will generate an error that
requests this value be set to 0.
By default, all management services are enabled on the management VRF ("mgmt-vrf") and the default
VRF ("default-vrf").
If the encryption-level is zero (0) but the key entered is encrypted then the following error
message is displayed: Error: Input key must be plain text when encryption-level
selected is 0.
Examples
This example configures an IPv4 TACACS+ server.
device# configure terminal
device(config)# tacacs-server host 10.24.65.6
device(config-host-10.24.65.6/mgmt-vrf)# tacacs-server source-ip chassis-ip
device(config-host-10.24.65.6/mgmt-vrf)# protocol chap retries 100
device(config-host-10.24.65.6/mgmt-vrf)#
tag-type
Configures Tag Protocol ID (TPID) for the specified interface.
Syntax
tag-type tp-id
no tag-type tp-id
Parameter:
tp-id
Specifies the TPID. TPID is a numerical value in hexadecimal format. Some of the TPIDs
supported are 0x8100, 0x9100, 0x9200, 0x88a8.
Command Default
The default TPID value is 0x8100.
Modes
Interface configuration mode
Usage Guidelines
The interface can be a port or a port-channel (LAG).
Use the no form of the command to revert to the default TPID value.
For the SLX 9740 series devices, only two (2) TPIDs are supported, which include the default TPID.
Therefore, only one additional TPID is available for user configuration.
• LSP FRR limitation: Hardware support for LSP FRR is available only for TPID 0x8100. If you require a
label switched path with fast reroute (LSP FRR) configuration, note that none of the routable
interfaces (whether a router port or a LIF of a VE) can have any nondefault TPID configuration,
because FRR always assumes that the link layer has the default TPID of 0x8100.
Note
The LSP FRR limitation is for any tag-type configured in the device. You can configure either
FRR or tag-type on any interface in the device, as in this example.
device(config-router-mpls-lsp-to-avalanche-1)# frr
%Error: Not allowed, when a non-default TPID (tag-type) is configured on any port-channel
or physical interfaces.
device(config-router-mpls-lsp-to-avalanche-1)#
Important
When the tag type is changed on interface, the interface is brought down first, causing all
learned MAC addresses to be flushed.
Examples
This example shows how to configure a nondefault TPID on an Ethernet interface.
device# configure terminal
device(config)# inteface ethernet 1/1
device(conf-if-eth-1/1)# tag-type 0x9100
telemetry client-cert
Generates the SSL certificate used by Telemetry server and client for a secure connection.
Syntax
telemetry client-cert { generate | delete }
Command Default
There is no SSL certificate.
Parameters
generate
Generates the certificate
delete
Deletes the certificate.
Modes
Privileged EXEC mode
Usage Guidelines
Use the telemetry client-cert delete to delete the SSL certificate for Telemetry server and
clients.
Examples
Typical command execution example.
device# telemetry client-cert generate
telemetry collector
Activates telemetry-collector configuration mode.
Syntax
telemetry collector telemetry-collector
Command Default
Telemetry collector configuration mode is deactivated.
Parameters
telemetry-collector
A unique name for a Telemetry collector. The name can be a string of up to 32 characters,
consisting of letters, digits, and the underscore.
Modes
Global configuration mode
Usage Guidelines
Update operations are allowed only when telemetry collector is in deactivated (“no activate”) state.
Examples
Typical command example for activating Telemetry collector configuration mode.
device# configure terminal
device(config)# telemetry collector collector_1
device(config-telemetry-collector_collector_1)#
telemetry profile
Enters telemetry-profile configuration mode.
Syntax
telemetry profile enhanced-queue-discard-pkts
default_enhanced_queue_discard_pkts_statistics
telemetry profile enhanced-queue-max-queue-depth
default_enhanced_queue_max_queue_depth_statistics
telemetry profile interface default_interface_statistics
telemetry profile mpls-traffic-bypass
default_mpls_traffic_bypass_statistics
telemetry profile mpls-traffic-fec default_mpls_traffic_fec_statistics
telemetry profile mpls-traffic-lsp default_mpls_traffic_lsp_statistics
telemetry profile queue default_queue_statistics
telemetry profile system-utilization
default_system_utilization_statistics
Command Default
The Telemetry profile configuration mode is deactivated.
Parameters
enhanced-queue-discard-pkts
default_enhanced_queue_discard_pkts_statistics
( SLX 9540 and SLX 9640 devices) Accesses configuration mode for profile
default_enhanced_queue_discard_pkts_statistics of the enhanced-queue-
discard-pkts profile type. This profile tracks packets discarded in the 32 queues with the
most discards.
enhanced-queue-max-queue-depth
default_enhanced_queue_max_queue_depth_statistics
( SLX 9540 and SLX 9640 devices) Accesses configuration mode for profile
default_enhanced_queue_max_queue_depth_statistics of the enhanced-
queue-max-queue-depth profile type. This profile tracks maximum queue size in the 32
queues with the largest queue size.
interface default_interface_statistics
Accesses configuration mode for profile default_interface_statistics of the
interface profile type.
mpls-traffic-bypass default_mpls_traffic_bypass_statistics
( SLX 9540 and SLX 9640 devices) Accesses configuration mode for profile
default_mpls_traffic_bypass_statistics of the mpls-traffic-bypass profile
type.
mpls-traffic-fec default_mpls_traffic_fec_statistics
( SLX 9540 and SLX 9640 devices) Accesses configuration mode for profile
default_mpls_traffic_fec_statistics of the mpls-traffic-fec profile type.
mpls-traffic-lsp default_mpls_traffic_lsp_statistics
( SLX 9540 and SLX 9640 devices) Accesses configuration mode for profile
default_mpls_traffic_lsp_statistics of the mpls-traffic-lsp profile type.
queue default_queue_statistics
( SLX 9540 and SLX 9640 devices) Accesses configuration mode for profile
default_queue_statistics of the queue profile type. This profile captures the overall
queue statistics for the device.
system-utilization default_system_utilization_statistics
Accesses configuration mode for profile default_system_utilization_statistics of
the system-utilization profile type.
Modes
Global configuration mode
Usage Guidelines
If a telemetry profile has no attributes, no information is streamed to the collector.
Examples
Example of entering telemetry profile configuration mode.
device# configure terminal
device(config)# telemetry profile interface default_interface_statistics
device(config-interface-default_interface_statistics)#
Syntax
telemetry profile profile-type telemetry-profile-name
Command Default
The Telemetry profile configuration mode is not available until the telemetry profile command is
entered.
Parameters
profile-type
The type of MPLS profile for the telemetry configuration. The available MPLS profile types are
mpls-traffic-lsp, mpls-traffic-bypass, and mpls-traffic-fec.
telemetry-profile-name
The MPLS profile name. The available MPLS profile names are
default_mpls_traffic_lsp_statistics,
default_mpls_traffic_bypass_statistics, and
default_mpls_traffic_fec_statistics.
Modes
Global configuration mode
Usage Guidelines
The MPLS profile types are supported only on SLX 9540 and SLX 9640 devices.
The "no" command is not supported for default telemetry profiles. Only the default telemetry profiles
are supported. These profiles will contain all the streaming attributes supported. You can customize
these profiles by adding or removing attributes using the add or no add sub command or by
changing the interval using the interval sub command.
If a telemetry profile has no attributes, no information is streamed to the collector. The MPLS profile can
be used for streaming after:
• Specifying the required MPLS LSP names for the mpls-traffic-lsp type profile using the lsp sub
command.
• Specifying the required MPLS Bypass LSP names for the mpls-traffic-bypass type profile using the
bypass-lsp sub command.
• Specifying the required MPLS LDP FEC addresses for the mpls-traffic-fec type profile using the fec
sub command.
Examples
Example of entering telemetry profile configuration mode for an MPLS LSP configuration.
telemetry server
Enters telemetry-server configuration mode.
Syntax
telemetry server [ use-vrf [ vrf-name] ]
Command Default
Telemetry-server configuration mode is deactivated.
Parameters
use-vrf vrf-name
Specifies a VRF, rather than the default mgmt-vrf.
Modes
Global configuration mode
Usage Guidelines
You use this command to configure gRPC-server telemetry streaming.
Update and No operations are available only when telemetry server is in deactivated (“no activate”)
state.
Examples
The following example enters telemetry-server configuration mode and activates the internal gRPC
telemetry-server on the default port 50051.
device# configure terminal
device(config)# telemetry server
device(config-server-mgmt-vrf)# activate
telnet
Establishes a Telnet session to a remote networking device.
Syntax
telnet IP_address [ port-number port_number ] [ vrf name ]
telnet hostname } [ port-number port_number ] [ interface { ethernet
slot/port } | management | {ve number } ] [ vrf name ]
Command Default
The default port is 23.
Parameters
IP_address
The server IP address in either IPv4 or IPv6 format.
port-number port
Specifies the port number in the remote device to connect to. Range is from 0 through 65535.
For the connection to succeed, a TCP server must be listening for client connections at the
specified port.
vrf vrf-name
Specifies a VRF instance. See the Usage Guidelines.
hostname
Specifies the host name which is a string between 1 and 63 ASCII characters in length.
port-number port
Specifies the port number in the remote device to connect to. Range is from 0 through 65535.
For the connection to succeed, a TCP server must be listening for client connections at the
specified port.
interface
Specifies an interface.
ethernet slot/port
Specified the Ethernet interface slot and port number.
management
Specifies the management interface.
ve VE-id
Specifies the VE interface number.
Modes
Privileged EXEC mode
Usage Guidelines
You can override the default port. However, the device must be listening on this port for the connection
to succeed.
Examples
The following example establishes a Telnet connection to a remote device.
device# telnet 10.20.51.68 vrf mgmt-vrf
telnet server
Configures the Telnet server on the device.
Syntax
telnet server use-vrf name [ shutdown ]
no telnet server use-vrf name [ shutdown ]
Command Default
The Telnet service is enabled by default.
Parameters
use-vrf name
Specifies a user-defined VRF.
shutdown
Disables the Telnet server.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to re-enable the Telnet service on the device.
Shutting down the Telnet service forcibly disconnects all Telnet sessions running on a device.
Examples
The following example shuts down the Telnet server on the default VRF.
device# configure terminal
device(config)# telnet server use-vrf default-vrf shutdown
terminal
Sets terminal parameters for the current session.
Syntax
terminal length lines
terminal monitor
terminal no length
terminal timeout seconds
no terminal { monitor | timeout }
Command Default
The terminal length is 24 lines.
Parameters
length number_of_lines
Specifies the number of lines to be displayed. Valid values range from 1 through 512. Specify 0 for
infinite length.
monitor
Enables terminal monitoring.
timeout seconds
Specifies the timeout value in minutes. Enter an integer from 1 to 8192. Specify 0 to disable the
timeout.
Modes
Privileged EXEC mode
Usage Guidelines
The timeout overrides the timeout configuration set by the line vty exec-timeout command,
but only for the duration of the current session. When the current session ends, the configured values
apply for any subsequent sessions.
Even if other keys are pressed during the timeout period, the only keystroke that prevents logout is
Enter.
To reset the default number of displayed lines, use the terminal no length command.
Examples
The following example sets the display length to 30 lines.
device# terminal length 30
The following example sets timeout length to 3600 seconds (60 minutes).
device# terminal timeout 3600
The following example restores the session timeout setting its default value of 600 seconds (10
minutes).
device# no terminal timeout
test-profile
Creates a test profile.
Syntax
test-profile test-profile-name
no test-profile
Parameters
test-profile-name
Specifies the test profile name. A test profile name can be can be a maximum of 32 characters .
Command Default
This feature is disabled.
Modes
Y.1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the corresponding configured test profile and also its
associations with Source and Target MEP pair.
Examples
This example shows how to create a test profile .
device# configure terminal
device(config)# protocol cfm
device((protocol-cfm)# test-profile my_test_profile
threshold
Specifies if the measurement exceeds the configured average or max threshold value.
Syntax
threshold { forward | backward } | { average value | max value }
no threshold
Parameters
forward
Defines the forward direction.
backward
Defines the backward direction.
average value
Defines the average value.
max value
Defines the maximum value.
Modes
Y.1731 configuration mode
Usage Guidelines
The threshold command specifies if the measurement exceeds the configured average or max
threshold value in the backward or forward direction, then Syslogs or SNMP traps need to generated..
The average-threshold parameter specifies that when the average-threshold value in the applied profile
is exceeded, take actions as configured in the action profile for this event.
The max-threshold parameter specifies that when the max-threshold value in the applied profile is
exceeded, take actions as configured in the action profile for this event.
Examples
Example of setting the direction and average threshold.
device# configure terminal
device(config)# protocol cfm
device(protocol-cfm)# y1731
device(protocol-cfm-y1731)# test-profile my_test_profile
device(protocol-cfm-y1731-my_test_profile)# threshold backward
device(protocol-cfm-y1731-my_test_profile)# threshold average 25
device(protocol-cfm-y1731-my_test_profile)# exit
threshold (ETH-DM)
Configures the ETH-DM threshold.
Syntax
threshold [ average average-threshold | maximum maximum-threshold ]
no threshold [ average average-threshold | maximum maximum-threshold ]
Parameters:
average average-threshold
Specifies the average threshold. The valid value is from 1 to 4294967295.
maximum maximum-thershold
Specifies the maximum threshold. The valid value is from 1 to 4294967295.
Command Default
The default value for average threshold is 4294967295 uSec. The default value for maximum threshold
is 4294967295 uSec.
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the threshold configuration.
Examples
This example shows how to configure the threshold value.
device# configure terminal
device (config-cfm)# protocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device(config-cfm-y1731-test-profile-my_test_profile)# tx-interval 60
device(config-cfm-y1731-test-profile-my_test_profile)# measurement-interval 30
device(config-cfm-y1731-test-profile-my_test_profile)# start at 00:00:00 daily
device(config-cfm-y1731-test-profile-my_test_profile)# stop at 23:59:00
device(config-cfm-y1731-test-profile-my_test_profile)# cos 7
device(config-cfm-y1731-test-profile-my_test_profile)# threshold maximum 3294967295
threshold (ETH-SLM)
Configures the ETH-SLM threshold.
Syntax
threshold { backward [ average average-value | maximum maximum-value ] |
forward [ average average-value | maximum maximum-value ] }
no threshold { backward [ average average-value | maximum maximum-
value ] | forward [ average average-value | maximum maximum-value ] }
Parameters:
backward
Specifies ETH-SLM backward threshold.
average average-value
Specifies the ETH-SLM backward average threshold value. The average value range is from 1 to
4294967295.
maximum maximum value
Specifies the ETH-SLM backward maximum threshold value. The average value range is from 1 to
4294967295.
forward
Specifies ETH-SLM forward threshold.
Command Default
The default value for average threshold is 4294967295 uSec. The default value for maximum threshold
is 4294967295 uSec.
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the threshold configuration.
Examples
This example shows how to configure the threshold value.
device# configure terminal
device (config-cfm)# protocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device(config-cfm-y1731-test-profile-my_test_profile)# tx-interval 60
device(config-cfm-y1731-test-profile-my_test_profile)# measurement-interval 30
threshold-monitor Cpu
Configures monitoring of CPU usage of the system and alerts the user when configured thresholds are
exceeded.
Syntax
threshold-monitor Cpu { [ actions [ all | loginfo | none | raslog |
snmp ] ] | limit value-in-percentage | poll polling-interval | retry
retry-interval }
no threshold-monitor cpu
Parameters
actions
Specifies the action to be taken when a threshold is exceeded. The values supported are all,
loginfo, none, raslog, and snmp where snmp and all are newly added. Default "action"
is changed to "all".
all
RASLOG and SNMP trap will be sent when the threshold is exceeded.
loginfo
Additional diagnostics data will be collected along with RASLOG when the threshold is
exceeded.
none
No action will be taken when the threshold is exceeded.
raslog
Only RASLOG will be sent when the threshold is exceeded.
snmp
SNMP traps will be sent when the threshold is exceeded.
limit value-in-percentage
Specifies the baseline CPU usage limit as a percentage (%) of available resources that will trigger
the configured action. The range is 0%-95%. The default value is 50%.
poll polling-interval
Specifies the polling interval in seconds after which a sample will be taken. The range is 10-3600
seconds. The default interval is 120 seconds.
retry retry-interval
Specifies the number polling retries that will be attempted before desired action is taken. The
range is 1-100. The default retries is 3.
Modes
Global configuration mode
Usage Guidelines
The default action is all. Prior to SLXOS version 20.4.1, the default value was none.
Examples
SLX(config)# threshold-monitor Cpu ?
Possible completions:
actions Action to be taken when usage exceeds limit
limit PERCENT:0-95 Percent threshold usage for component:CPU
poll NUMBER:10-3600 Polling interval
retry NUMBER:1-100 Number of retries
SLX(config)#
threshold-monitor memory
Configures monitoring of the memory usage of the system and alerts the user when configured
thresholds are exceeded.
Syntax
threshold-monitor Memory { [ actions [ all | loginfo | none | raslog |
snmp ] ] | high-limit value-in-percentage | poll polling-interval |
retry retry-interval }
no threshold-monitor Memory
Parameters
actions
Specifies the action to be taken when a threshold is exceeded. The values supported are all,
loginfo, none, raslog, and snmp where snmp and all are newly added. Default "action"
is changed to "all".
all
RASLOG and SNMP trap will be sent when the threshold is exceeded.
loginfo
Additional diagnostics data will be collected along with RASLOG when the threshold is
exceeded.
none
No action will be taken when the threshold is exceeded.
raslog
Only RASLOG will be sent when the threshold is exceeded.
snmp
SNMP traps will be sent when the threshold is exceeded.
high-limit value-in-percentage
Specifies the high usage limit as a percentage (%) of available memory that will trigger the
configured action. The range is 0%-95%. The default value is 70%.
poll polling-interval
Specifies the polling interval in seconds after which a sample will be taken. The range is 10-3600
seconds. The default interval is 120 seconds.
retry retry-interval
Specifies the number polling retries that will be attempted before desired action is taken. The
range is 1-100. The default retries is 3.
Modes
Global configuration mode
Usage Guidelines
Note
Parameters "limit" and "low-limit" are removed in SLXOS version 20.4.1.
Examples
SLX(config)# threshold-monitor Memory ?
Possible completions:
actions Action to be taken when usage exceeds limit
high-limit PERCENT:0-95: Percent high threshold usage for component:MEMORY
poll NUMBER:10-3600: Polling interval
retry NUMBER:0-100: Number of retries for component:MEMORY
SLX(config)#
threshold-monitor sfp
Configures monitoring of SFP parameters.
Syntax
threshold-monitor sfp { [ apply policy_name | pause | policy
policy_name ] type SFP_type area parameters alert [ above
[ highthresh-action [ [ all | lowthresh-action ] | email | none |
raslog ] | lowthresh-action [ all | email none | raslog ] | below
[ highthresh-action [ all | email | none raslog ] | lowthresh-action
[ all | email | none | raslog ] ] | threshold [ buffer | high-
threshold | low-threshold | timebase [ day | hour | minute |
none ] ] ] }
no threshold-monitor sfp
Command Default
By default, SFP is not monitored.
Parameters
apply policy_name
Applies a custom policy that has been created by the policy operand.
pause
Pause monitoring.
policy
Specifies a policy name for monitoring by means of custom settings, rather than default settings.
A policy name is required before additional configurations can be made. This operation is not
supported from a secondary node.
policy_name
Name of a custom policy configuration that can be saved and applied by means of the apply
operand.
type
Specifies the SFP type. Possible completions are as follows:
1GLR
— SFP Type 1GLR
1GSR
— SFP Type 1GSR
10GLR
— SFP Type 10GLR
10GSR
— SFP Type 10GSR
10GUSR
— SFP Type 10GUSR
100GSR
— SFP Type 100GSR
QSFP
— SFP type QSFP
area
Specifies one of the following SFP parameters to be monitored. See Defaults, below.
Current
Measures the current supplied to the SFP transceiver.
RXP
Measures the incoming laser power, in microWatts (µW).
TXP
Measures the outgoing laser power, in µW).
Temperature
Measures the temperature of the SFP, in degrees Celsius.
Voltage
Measures the voltage supplied to the SFP.
alert
Specifies whether an alert is sent when a threshold value is either above or below a threshold
trigger.
above
Enables setting a value for highthresh-action, which specifies the action to be taken when
a high threshold is exceeded.
below
Enables setting a value for highthresh-action and lowthresh-action, which specifies
the action to be taken when a low threshold is exceeded.
all
Specifies that email and RASLog messaging are used, and that Port Fencing is applied in the
case of highthresh-action only.
all
Specifies that email and RASLog messaging are used.
email
Specifies that an email message is sent.
none
Specifies that no alert is sent.
raslog
Specifies RASLog messaging.
limit
Specifies the percent of threshold usage, from 0 through 80. The default is 75.
poll
Specifies the polling interval in seconds, from 0 through 3600. The default is 120.
retry
Specifies the number of polling retries before desired action is taken, from 1 through 100. The
default is 3.
threshold
Specifies the values for high, low, buffer, and timebase thresholds. These values are used to
trigger different alerts and Port Fencing.
buffer
An integer value.
high-threshold
An integer value.
low-threshold
An integer value.
timebase
Calculates differences between current and previous data taken over a variety of intervals, for
comparison against the preset threshold boundary.
day
Calculates the difference between a current data value and that value a day ago.
hour
Calculates the difference between a current data value and that value an hour ago.
minute
Calculates the difference between a current data value and that value a minute ago.
none
Compares a data value to a threshold boundary level.
Modes
Global configuration mode
Examples
A typical command might look like this:
device(config)# threshold-monitor sfp custom type QSFP area rxp threshold high-threshold
2000 low-threshold 1000
threshold-timer (management-heartbeat)
Configures the threshold value for listening to heartbeat message from EFA. Used within the
management-heartbeat context.
Syntax
threshold-timer time
no threshold-timer
Command Default
By default, threshold value is set at five (5) minutes.
Parameters
time
The time duration in minutes for which this device will listen for a heartbeat message from EFA.
Once this time exceeds, the device proceeds to perform the action configured through the
action command. A value in the range of 1-30 minutes can be configured.
Modes
Management Heartbeat mode
Examples
The following example sets the threshold value to 30 minutes. This is the maximum value that can be
configure for this parameter.
SLX(config-management-heartbeat-manage) # threshold-timer 30
tie-breaking
Configures the device to choose the path with the highest available bandwidth or the lowest available
bandwidth.
Syntax
tie-breaking { [ least-fill | most-fill | random ] }
no tie-breaking { [ least-fill | most-fill | random ] }
Command Default
The default is the tie-breaking random mode.
Parameters
least-fill
Causes CSPF to choose the path with the highest available bandwidth (that is, the path with the
least utilized links).
most-fill
Causes CSPF to choose the path with the lowest available bandwidth (that is, the path with the
most utilized links).
random
Causes CSPF to choose the path randomly from the equal-cost paths.
Modes
MPLS LSP configuration mode (config-router-mpls-lsp-lsp_name )
Usage Guidelines
The no form of the command removes the tie-breaking configuration and reverts to the default mode.
The user can configure an interface level tie-breaking option for the CSPF calculation of dynamic bypass
LSPs to be created for the protected MPLS interface. The set value is used for dynamic bypass LSP path
computation tie-breaking procedure.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
In the following example, the configuration causes the CSPF to select the path with the highest
available bandwidth when choosing among equal cost paths calculated for LSP tunnel1.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp tunnel1
device(config-router-mpls-lsp-tunnel1)# tie-breaking least-fill
The following example configures the tie-breaking path bandwidth to the least-fill option for
dynamic bypass MPLS Ethernet interface 2/8 .
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 2/8
device(config-router-mpls-if-ethernet-2/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-2/8-dynamic-bypass)# tie-breaking least-fill
timeout (link-oam)
Allows you to configure timeout value, which corresponds to hold time before the Discovery process
restarts.
Syntax
timeout sec
no timeout
Command Default
The default wait time is 5 seconds.
Parameters
sec
Specifies the hold time (in seconds) before the discovery process restarts. The range is from 1
through 10. The default value is 5.
Modes
Link OAM configuration mode
Usage Guidelines
The no form of the command restores the command default value.
Examples
The following example shows how to configure a wait time of 10 seconds.
device(config-link-oam)# timeout 4
timeout (RADIUS)
Species the wait time allowed for a Remote Authentication Dial-In User Service (RADIUS) server
response.
Syntax
timeout sec
no timeout
Command Default
The default wait time is 5 seconds.
Parameters
sec
Specifies the wait time (in seconds) allowed for a RADIUS server response. The range is from 1
through 60. The default value is 5.
Modes
RADIUS server host VRF configuration mode
Usage Guidelines
The no form of the command restores the command default value.
Examples
The following example shows how to configure a wait time of 10 seconds.
timeout (Y1731)
Configures timeout in seconds.
Syntax
timeout timeout-value
no timeout timeout-value
Parameters:
timeout-value
Spcifies the timeout value. The range is from 1 to 4 seconds.
Command Default
The default value for timeout is 1 second.
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the timeout configuration.
Examples
This example shows how to configure the timeout value.
device# configure terminal
device (config-cfm)# prtocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device(config-cfm-y1731-test-profile-my_test_profile)# tx-interval 60
device(config-cfm-y1731-test-profile-my_test_profile)# measurement-interval 30
device(config-cfm-y1731-test-profile-my_test_profile)# start at 00:00:00 daily
device(config-cfm-y1731-test-profile-my_test_profile)# stop at 23:59:00
device(config-cfm-y1731-test-profile-my_test_profile)# cos 7
device(config-cfm-y1731-test-profile-my_test_profile)# threshold maximum 3294967295
device(config-cfm-y1731-test-profile-my_test_profile)# timeout 1
timer
Sets the global MVRP join, leave and leave-all timers values on all MVRP-enabled interfaces except the
interfaces configured with the mvrp timer command in interface configuration mode.
Syntax
timer join cs leave cs leave-all cs
no timer join cs leave cs leave-all cs
Command Default
The join timer default setting is 20 centiseconds (cs).
Parameters
join cs
Specifies the join timer in centiseconds. Enter an integer from 20 to 10000000.
leave cs
Specifies the leave timer in centiseconds. Enter an integer from 100 to 10000000. The leave
timer setting must be greater than or equal to twice the join timer setting plus 30 centiseconds.
leave-all cs
Specifies the leave-all timer in centiseconds. Enter an integer from 1000 to 10000000. The
leave-all timer setting must be a minimum of three times the value of the leave timer setting.
Modes
MVRP configuration mode
Usage Guidelines
MVRP is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
The no form of the command resets the default settings globally and on interfaces that are not
configured with the mvrp timer command in interface configuration mode.
This command requires that you configure the timer values in the specified order and you must
configure all values.
When the network radius is large or the expected system load is higher normally, since the default timer
values are aggressive, Extreme recommends that you change the timer values to higher numbers to
reduce the MVRP message exchanges and the load of the system.
The configured timer settings on the individual interfaces override the global timer configuration.
The join timer is not run periodically but is triggered by the MVRP events or state changes. However, the
leave-all timer is periodic; required for garbage collection purposes.
Examples
The following example configures the global MVRP timer settings.
device# configure terminal
device(config)# protocol mvrp
device(config-mvrp)# timer join 40 leave 200 leave-all 2000
device(config-mvrp)#
timers (BGP)
Adjusts the interval at which BGP KEEPALIVE and HOLDTIME messages are sent.
Syntax
timers { keep-alive keepalive_interval hold-time holdtime_interval }
no timers
Parameters
keep-alive keepalive_interval
Frequency in seconds with which a device sends keepalive messages to a peer. Range is from 0
through 65535 seconds. The default is 60.
hold-time holdtime_interval
Interval in seconds that a device waits to receive a keepalive message from a peer before
declaring that peer dead. Range is from 0 through 65535 seconds. The default is 180.
Modes
BGP configuration mode
Usage Guidelines
The KEEPALIVE and HOLDTIME message interval is overwritten when the fast-external-
failover command takes effect on a down link to a peer.
You must enter a value for keep-alive before you can enter a value for hold-time. Both values must
be entered. If you only want to adjust the value of one parameter, enter the default value of the
parameter that you do not want to adjust.
Examples
The following example sets the keepalive timer for a device to 120 seconds and the hold-timer to 360
seconds.
The following example sets the keepalive timer for a device to 0 seconds and the hold-timer to 0
seconds so that the device waits indefinitely for messages from a neighbor without tearing down the
session.
timers (OSPFv2)
Configures Link State Advertisement (LSA) pacing and Shortest Path First (SPF) throttle timers.
Syntax
timers { lsa-group-pacing interval | throttle spf start hold max }
Command Default
See the parameters section for specific defaults.
Parameters
lsa-group-pacing interval
Specifies the interval at which OSPF LSAs are collected into a group and refreshed, check-
summed, or aged by the OSPF process. Valid values range from 10 to 1800 seconds. The default
is 240 seconds.
throttle spf
Specifies start, hold and maximum wait intervals for throttling SPF calculations for performance.
The values you enter are in milliseconds.
start
Initial SPF calculation delay. Valid values range from 0 to 60000 milliseconds. The default is 0.
hold
Minimum hold time between two consecutive SPF calculations. Valid values range from 0 to
60000 milliseconds. The default is 0.
max
Maximum wait time between two consecutive SPF calculations. Valid values range from 0 to
60000 milliseconds. The default is 0.
Modes
OSPF router configuration mode
Usage Guidelines
The device paces LSA refreshes by delaying the refreshes for a specified time interval instead of
performing a refresh each time an individual LSA refresh timer expires. The accumulated LSAs
constitute a group, which the device refreshes and sends out together in one or more packets.
The LSA pacing interval is inversely proportional to the number of LSAs the device is refreshing and
aging. For example, if you have a large database of 10,000 LSAs, decreasing the pacing interval
enhances performance. If you have a small database of about 100 LSAs, increasing the pacing interval
to 10 to 20 minutes may enhance performance.
The no timers lsa-group-pacing command restores the pacing interval to its default value.
The no timers throttle spf command sets the SPF timers back to their defaults.
Examples
The following example sets the LSA group pacing interval to 30 seconds.
The following example sets the SPF delay to 10000 milliseconds, the hold time to 15000 milliseconds,
and the maximum wait time to 30000 milliseconds.
timers (OSPFv3)
Configures Link State Advertisement (LSA) pacing and Shortest Path First (SPF) timers.
Syntax
timers { lsa-group-pacing interval | spf start hold }
Command Default
Enabled.
Parameters
lsa-group-pacing interval
Specifies the interval at which OSPFv3 LSAs are collected into a group and refreshed, check-
summed, or aged by the OSPFv3 process. Valid values range from 10 to 1800 seconds. The
default is 240 seconds.
spf
Specifies start and hold intervals for SPF calculations for performance. The values you enter are
in milliseconds.
start
Initial SPF calculation delay. Valid values range from 0 to 65535 seconds.
hold
Minimum hold time between two consecutive SPF calculations. Valid values range from 0 to
65535 seconds.
Modes
OSPFv3 router configuration mode
Usage Guidelines
The device paces LSA refreshes by delaying the refreshes for a specified time interval instead of
performing a refresh each time an individual LSA refresh timer expires. The accumulated LSAs
constitute a group, which the device refreshes and sends out together in one or more packets.
The LSA pacing interval is inversely proportional to the number of LSAs the device is refreshing and
aging. For example, if you have a large database of 10,000 LSAs, decreasing the pacing interval
enhances performance. If you have a small database of about 100 LSAs, increasing the pacing interval
to 10 to 20 minutes may enhance performance.
The no timers lsa-group-pacing command restores the pacing interval to its default value.
The no timers spf command sets the SPF timers back to their defaults.
Examples
The following example sets the LSA group pacing interval to 30 seconds.
The following example sets the SPF delay time to 10 and the hold time to 20.
tls min-version
The command enables configuring the lowest TLS version supported by SLX OS for the Client and
Server modes of operation of the SLX device. This command is available under the respective modes
under the Management Security SSL Profile mode. SLX uses OpenSSL to provide transport layer
security and the current version of OpenSSL supports TLS v 1.1 to TLS v 1.2. Since the SLX box can be
considered as both a client as well as a server, you can apply different supported TLS versions for each
of these types. The default TLS version supported is v 1.1.
Syntax
tls min-version { 1.1 | 1.2 }
no tls min-version
Command Default
The default supported TLS version is version 1.1.
Parameters
min-version { 1.1 | 1.2 }
Indicates that the minimum version of TLS support is being configured. Select from one of the
available choices.
Modes
Client Profile mode and Server Profile mode in SSL Profile mode. SSL Profile mode is available under
Management Security mode.
Usage Guidelines
The no format of this command resets the manual configuration of TLS support to the defaults. The
default support is for TLS v 1.1 and TLS v 1.2.
Examples
This example shows how to navigate into the Client Profile mode and configure the minimum supported
TLS version to 1.2.
SLX # conf term
Entering configuration mode terminal
SLX # conf term
Entering configurationSLX (config)#
SLX (config)# management-security
SLX (mgmt-security)#
SLX(mgmt-security)# ssl-profile ?
Possible completions:
client management security ssl profile client for tls configuration
server management security ssl profile server for tls configuration
SLX (mgmt-security)# ssl-profile client
SLX (mgmt-sec-ssl-profile-client)#
SLX (mgmt-sec-ssl-profile-client)# tls ?
Possible completions:
min-version min version to be supported by client
SLX(mgmt-sec-ssl-profile-client)# tls min-version ?
Possible completions:
<1.1|1.2> specify TLS version
SLX(mgmt-sec-ssl-profile-client)# tls min-version 1.2
This example shows how to disable the manual configuration for TLS version support.
SLX # conf term
Entering configuration mode terminal
SLX (config)#
SLX (config)# management-security
SLX (mgmt-security)#
SLX (mgmt-security)# ssl-profile client
SLX (mgmt-sec-ssl-profile-client)#
SLX(mgmt-sec-ssl-profile-client)# no tls min-version
tlv-type
Enables the Port Status type-length-value (TLV) metric for the specified Maintenance End Points (MEP).
Syntax
tlv-type port-status-tlv
no tlv-type port-status-tlv
Command Default
The Port Status TLV is not enabled.
Parameters
port-status-tlv
Enables the Port Status TLV metric.
Modes
CFM protocol configuration mode .
Usage Guidelines
The no tlv-type port-status-tlv command disables the Port Status TLV metric for the
specified MEP.
Examples
Command example to enable the Port Status TLV metric.
device# configure terminal
device(config-cfm)# domain name md1 level 4
device(config-cfm-md-md1)# ma-name ma1 id 1 vlan-id 30 priority 3
device(config-cfm-md-ma-ma1)# mep 1 down ethernet 1/2
device(config-cfm-md-ma-mep-1)# tlv-type port-status-tlv
to
Configures a destination address for the bypass LSP.
Syntax
to ip_addr
no to ip_addr
Parameters
ip_addr
Specifies the destination or egress IPv4 address of the bypass LSP.
Modes
MPLS router bypass LSP configuration mode
Usage Guidelines
The destination address is mandatory to enable a bypass LSP.
The no form of the command removes the destination address of the bypass LSP.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the destination address to 33.33.33.33 for bypass LSP my-bypass-lsp.
device# configure
device(config)# router mpls
device(config-router-mpls)# bypass-lsp my-bypass-lsp
device(config-router-mpls-bypass-lsp-my-bypass-lsp)# to 33.33.33.33
topology-group
Configures the topology group.
Syntax
topology-group group-id
no topology-group group-id
Command Default
A topology group is not configured.
Parameters
group-id
Specifies the topology group ID. The ID ranges from 1 through 256.
Modes
Global configuration mode
Usage Guidelines
Each topology group contains a master VLAN and can contain one or more member VLANs and VLAN
groups. You must configure the master VLAN and member VLANs or member VLAN groups before you
configure the topology group.
You can configure up to 30 topology groups. Each group can control up to 4096 VLANs. A VLAN
cannot be controlled by more than one topology group. The topology group must contain a master
VLAN and can also contain individual member VLANs, VLAN groups, or a combination of individual
member VLANs and VLAN groups.
Examples
The following example configures the topology group with ID 2 and adds master VLAN and member
VLANs.
tpvm
Provides administrative support, for users without root privileges, for Third-Party Virtual Machine
(TPVM) applications.
Syntax
tpvm [ install | uninstall [ force ] ]
tpvm [ start | stop ]
tpvm auto-boot [ disable | enable ]
tpvm disk { add name { disk_name | auto disk_size } | remove name
{ disk_name | auto } }
tpvm password
tpvm console
Command Default
This feature is not enabled.
Parameters
install
Installs TPVM.
uninstall
Uninstalls TPVM.
force
Clears installation or uninstallation errors, then tries to force an uninstallation.
start
Starts TPVM.
stop
Stops TPVM.
auto-boot disable
Prevents TPVM from starting at the next reboot of SLX-OS.
auto-boot enable
Starts TPVM at the next reboot of SLX-OS (without the need for the start keyword).
disk add name
Adds a new disk to TPVM.
disk_name
Name of the disk to be added if the auto keyword is not specified.
auto
Assigns a disk name automatically. See the Usage Guidelines.
disk_size
Size of the disk (any positive integer). See the Usage Guidelines.
disk remove name
Removes an additional disk from TPVM.
disk_name
Name of the additional disk to be removed. See the Usage Guidelines.
password
Changes the password on the TPVM for the user account named 'extreme'.
console
Connects to the TPVM console from SLX-OS Telnet or console sessions only on SLX 9640, SLX
9150, and SLX 9250 devices. See the Usage Guidelines.
Modes
Privileged EXEC mode
Usage Guidelines
When the tpvm console command is used, use ctrl+\ to return to the session from where the
TPVM console was started.
The tpvm uninstall force command asks for confirmation before proceeding. This command
removes the TPVM and all its disks, including data.
The tpvm password command sets the password for the user account named 'extreme.' This
password uses SHA-512 hash.
If the auto keyword is not used with the tpvm disk command, the name of the disk must be that of
the next disk. For example, if the last disk added to the system is vdb, the name of the next disk must
be vdc.
You can add one of the following suffixes to specify disk size:
• b or B (bytes)
• k or K (kilobytes)
• m or M (megabytes)
• g or G (gigabytes)
The maximum number of disks supported is currently 3 and if the number of allocated disks exceeds
this number, the add_disk keyword fails. Also, the total disk capacity for TPVM is limited to 117
gigabytes on the SLX 9540 and SLX 9640, and limited to 68.7 gigabytes on the SLX 9150 and SLX
9250.
If the auto keyword is not used with the remove_disk command, the name of the disk must be that
of the last disk added to the system.
Important
If the disk is mounted, it must be unmounted before it is removed from the system. Otherwise,
the next added disk will be labeled incorrectly. If this happens, TPVM must be rebooted to
recover.
Examples
To install TPVM:
device# tpvm install
To uninstall TPVM:
device# tpvm uninstall
To force the clearing of installation or uninstallation errors by means of the force keyword:
device# tpvm uninstall force
To start TPVM at the next reboot of SLX-OS (without the need for the start keyword):
device# tpvm auto-boot enable
Note
In this case, the tpvm start command is required to enable TPVM.
To add a new disk to TPVM, by either using the auto keyword or specifying a disk name:
Note
The maximum number of disks supported is 3. If the number of allocated disks exceeds this
number, the disk add name keywords fail. Also, the total disk capacity for TPVM is limited
to 117 gigabytes on the SLX 9540 and SLX 9640, and limited to 68.7 gigabytes on the SLX
9150 and SLX 9250. If you exceed this limit when you create a disk, the disk add name
keywords fail.
Important
If the disk is mounted, it must be unmounted before it is removed from the system. Otherwise,
the next added disk will be labeled incorrectly. If this happens, TPVM must be rebooted to
recover.
To clear errors by means of the clear <error> keywords, where the error in this example is "disk
add":
device# tpvm disk add name auto 10g
disk add failed
Note
The runtime error can be also removed automatically when the same subcommand succeeds.
Syntax
tpvm config dns add dns-server ipv4-addr [ipv4-addr ]domain-name domain-
name
tpvm config dns remove
Command Default
By default, a DNS server is not configured in TPVM.
Parameters
add
Adds a DNS server.
dns-server ipv4-addr [ipv4-addr ]
Specifies a list of up to 2 IP addresses. One address (primary) is mandatory. The second address
(secondary) is optional.
domain-name domain-name
Specifies the domain name for the DNS server. You can configure only one domain name.
remove
Removes a DNS server.
Modes
Privileged EXEC mode
Usage Guidelines
There is not a no form of this command.
Examples
This example adds two DNS servers and updates the domain name.
device# tpvm config dns add dns-server 1.2.3.4 1.1.1.1 domain-name example.com
Syntax
tpvm config hostname hostname
Command Default
None
Parameters
hostname
TPVM Hostname.
Modes
Privileged EXEC mode
Usage Guidelines
no form of this command is not available. To reset hostname to its default value of tpvm, use the
hostname command from within the TPVM context. For more information, see hostname (tpvm mode)
on page 2409.
The length of the Hostname should be between 1 to 64 characters. The starting letter should be an
alphabet.
The allowed characters are alphabets (a-z), numbers(0-9), “.”(dot), and “-“(hyphen).
Note
Configuring TPVM hostname from the SLX device is not recommended when EFA is
deployed. Doing so will cause unknown state for the EFA and could lead to EFA downtime. To
change the TPVM Hostname, use the procedures provided in EFA documentation. Refer EFA
documents for hostname restrictions and format.
Examples
Example to update the hostname in TPVM
device# tpvm config hostname tpvm
Syntax
tpvm config ldap add host hostname port portnum [secure ]
tpvm config ldap add basedn domain-name rootdn root-domain-name rootdnpw
root-password
tpvm config ldap remove host hostname port portnum
tpvm config ldap remove basedn domain-name rootdn root-domain-name
rootdnpw root-password
Command Default
By default, an LDAP server is not configured in TPVM.
Parameters
add
Adds LDAP configuration.
remove
Removes LDAP configuration.
host hostname
Specifies the IPv4 or IPv6 address or the FQDN of the LDAP server.
port portnum
Specifies the port on the LDAP server. The default secure port is 636. The default non-secure
port is 389.
secure
Enables LDAP over TLS.
basedn domain-name
Specifies the base Domain Name.
rootdn root-domain-name
Specifies the root Domain Name.
rootdnpw root-password
Specifies the password for the root Domain Name.
Modes
Privileged EXEC mode
Usage Guidelines
There is not a no form of this command.
When LDAP replication is in use, no more than 2 LDAP servers can be configured. The base Domain
Name and root Domain Name must be common to both servers.
Configuring a secure LDAP server without importing certificates results in an error. Use the tpvm
config ldap ca-cert command to import certificates.
Examples
This example adds an LDAP host.
device# tpvm config ldap add host 10.24.15.200
This example adds a secure LDAP host with the default port.
device# tpvm config ldap add host 10.24.15.200 secure
This example configures the base Domain Name, the root Domain Name, and the root Domain Name
password.
device# tpvm config ldap add basedn dc=ldap,dc=hc-fusion,dc=in
rootdn cn=admin,dc=ldap,dc=hc-fusion,dc=in rootdnpw pass123
This example resets the configured port to the default (389 if the port was non-secure, 636 if the port
was secure).
device# tpvm config ldap remove host 1.1.1.1 port
This example disables the secure option for the LDAP server. The configured port remains the same and
is not reset to the default. Use the tpvm config ldap remove host <ip-addr> port
command to reset the port.
device# tpvm config ldap remove host 1.1.1.1 secure
This example removes the base Domain Name, the root Domain Name, and the root Domain Name
password.
device# tpvm config ldap remove basedn rootdn rootdnpw
Syntax
tpvm config ldap ca-cert import protocol SCP user username password
password directory dirname file filename
tpvm config ldap ca-cert remove
Command Default
By default, certificates are not imported.
Parameters
import
Imports certificates for LDAP over TLS.
protocol SCP
Specifies the SCP protocol.
host hostname
Specifies the host name or IP address of the remove server from which the CA certificate is
imported.
user username
Specifies the login name for the remote server.
password password
Specifies the password associated with the user name.
directory dirname
Specifies the name of the remote directory that contains the certificate.
file filename
Specifies the file name of the certificate.
remove
Removes certificates for LDAP over TLS.
Modes
Privileged EXEC mode
Usage Guidelines
There is not a no form of this command.
You cannot remove certificates from configured secure LDAP servers. Use the tpvm config ldap
command to disable the secure option and then remove the certificates.
Examples
This example imports certificates needed for the secure LDAP server configuration.
device# tpvm config ldap ca-cert import protocol SCP host 10.6.46.51
user fvt password pray4green directory /home/cert filename cacert.pem
Syntax
tpvm config ntp add server {ipv4-address | fqdn }
tpvm config ntp default
tpvm config ntp remove server {ipv4-address | fqdn }
Parameters
add
Adds NTP configuration.
default
Resets NTP configuration to the default.
remove
Removes NTP configuration.
server {ipv4-address | fqdn}
Identifies the NTP server by IPv4 address or fully qualified Domain Name.
Modes
Privileged EXEC mode
Usage Guidelines
There is not a no form of this command.
There is no limit to the number of NTP servers that you can configure.
Examples
This example adds a server to the list of NTP servers in the /etc/systemd/timesyncd.conf file in
TPVM.
device# tpvm config ntp add server time.google.com
This example removes a server from the list of NTP servers in the /etc/systemd/timesyncd.conf
file in TPVM.
device# tpvm config ntp remove server time.google.com
Syntax
tpvm config timezone <timezone name>
Command Default
None.
Parameters
timezone
Timezone.
Modes
Privileged EXEC mode
Usage Guidelines
There is not a no form of this command.
Examples
Example to update the timezone in TPVM.
device# tpvm config timezone Etc/GMT
Syntax
tpvm config trusted-peer add ipv4-address sudo-user username password
sudo-user-password
tpvm config trusted-peer add ipv4-address password sudo-user-password
tpvm config trusted-peer remove ipv4-address sudo-user username password
sudo-user-password
tpvm config trusted-peer remove ipv4-address password sudo-user-password
Command Default
None.
Parameters
add
Adds Trusted-Peer configuration.
remove
Removes Trusted-Peer configuration.
ipv4-address
Specifies the IPv4 address of the Peer TPVM.
sudo-user username
Specifies the Sudo User in the Peer TPVM. The default sudo-user is "extreme". User-name length
varies from 1-32 characters.
password sudo-user-password
Password for sudo-user in Peer TPVM. Password length varies from 1-512 characters. Special
characters are not supported as part of the password are: double quote (“), single quote (‘), back
slash (\), question mark (?), exclamation mark (!) and pipe (|).
Modes
Privileged EXEC mode
Usage Guidelines
The no form of this command is not available.
The IPv4 address of the Peer TPVM and the password are mandatory parameters.
Examples
This example shows how to add a trusted peer
SLX# tpvm config trusted-peer add 10.23.31.67 password password
This example shows how to add a trusted peer without providing the user ID of the sudo user.
SLX# tpvm config trusted-peer add 10.23.31.67 password password
This example shows how to add a trusted peer and providing the user ID of the sudo user.
SLX# tpvm config trusted-peer add 10.23.31.67 sudo-user extreme password password
Note
This behaviour is common when you try to perform add-add, add-remove, or remove-remove
commands running in parallel.
When the TPVM Peer IP address is not reachable and the user tries to add a trusted peer.
SLX# tpvm config trusted-peer add 10.23.31.68 sudo-user extreme password password
Failed to connect to 10.23.31.68
When the user provides an invalid credential when adding a trusted peer.
SLX# tpvm config trusted-peer add 10.23.31.67 sudo-user test password password
Check input credentials.
Note
This message is displayed when invalid username or invalid password is supplied while
creating a trusted peer.
When the user account used to access the remote trusted peer is not in the sudo user's list or the
account is not configured properly.
SLX# tpvm config trusted-peer add 10.23.31.67 sudo-user testuser password password
Check sudouser configuration for testuser user.
This example shows how to remove a configured trusted peer without providing the remote peer's sudo
user account user name:
SLX# tpvm config trusted-peer remove 10.23.31.67 password password
This example shows how to remove a configured trusted peer by providing the remote peer's sudo user
account user name:
SLX# tpvm config trusted-peer add 10.23.31.67 sudo-user extreme password password
When trying to remove a trusted peer but the peer is not reachable.
SLX# tpvm config trusted-peer remove 10.23.31.68 sudo-user extreme password password
Failed to connect to 10.23.31.68
when trying to remove a trusted peer, but the user credentials are incorrect.
SLX# tpvm config trusted-peer add 10.23.31.67 sudo-user extreme password wrognpass
Check input credentials.
Note
This message is displayed when invalid username or invalid password is supplied while
removing the trusted peer.
When the user account used to access the remote trusted peer is not in the sudo user's list or the
account is not configured properly.
SLX# tpvm config trusted-peer remove 10.23.31.67 sudo-user testuser password password
Check sudouser configuration for testuser user.
tpvm deploy
Performs TPVM and Insight Interface set up and configuration.
Syntax
tpvm deploy insight admin-pwd allow-pwdless confirm-pwd gw ipaddr
tpvm deploy mgmt admin-pwd allow-pwdless confirm-pwd [dhcp ]gw ipaddr
Command Default
This feature is not enabled.
Parameters
insight
Modes
Privileged EXEC mode
Usage Guidelines
This command performs the following operations:
• Installs TPVM
• Sets up TPVM networking
• Enables passwordless ssh from root@slx to extreme@TPVM
• Enable passwordless “sudo” inside TPVM
• Sets the TPVM password for the user account named "extreme".
By default the TPVM management interface eth0 is configured to acquire an IP Address via DHCP,
whereas the eth1 address is manually configured by adding a static entry in /etc/network/
interfaces.
The passwordless parameter in tpvm deploy allows you to configure ssh access from the root user
account on the SLX-OS to TPVM without a password.
The TPVM default user is extreme with sudo privileges. The tpvm deploy command configures
TPVM so sudo for this user does not ask for a password. Setting this parameter once will persist for the
lifetime of the TPVM.
TPVM ships with admin/password as the default login credential. To automate the TPVM setup and
achieve one touch provisioning of TPVM, this optional parameter sets the password for the TPVM
extreme user account. Setting this parameter once will persist for the lifetime of the TPVM.
Auto-boot may be specified to restart the TPVM image automatically in subsequent reboots, such as an
SLX-OS start on a Baremetal platform, or a HOST start on a VM-based platform.
After configuring the TPVM, tpvm deploy will start the TPVM. On a Baremetal platform, a reboot of
SLX will reboot TPVM. On a VM-based platform, an SLX-OS reboot does not affect TPVM. However if
the HOST reboots for any reason, TPVM also reboots.
Examples
The following example configures TPVM on Eth0 with a static IP and an administrative password of
"mypassword".
device# tpvm deploy mgmt ipaddr 10.25.101.121/22 gw 10.25.100.1 admin-pwd mypassword
confirm mypassword
Starting TPVM deploy CLI, please DO NOT hit CTRL+C
Tpvm install started
..Tpvm is installed
Tpvm set_ip succeeds
Tpvm password succeeds
auto-boot enable succeeds
Tpvm is started
The following example configures Eth0 with static IP, default gateway and passwordless login.
device# tpvm deploy mgmt ipaddr 192.168.1.1/24 gw 192.168.1.100 allow-pwdless
The following example configures Eth1 with a static IP address, a default gateway, but no passwordless
login, and new TPVM password setup.
device# tpvm deploy insight ipaddr 10.10.10.1/24 gw 10.10.10.100 admin-pwd admin123
confirm-pwd admin123
The following example configures Eth1 with a static IP address and default gateway.
device# tpvm deploy insight ipaddr 10.10.10.1/24 gw 10.10.10.100
tpvm download
Downloads the TPVM image from the remote location, and then optionally, verifies if the file size and
the version of the downloaded TPVM image is correct.
Syntax
tpvm download { block } directory remote-directory-name filename image-
file-name host [ hostname | ip-address ] password password { sanity
[ yes | no ] } use-vrf vrf-name user user-name
Parameters
block
Optional Parameter. When passed, it enables NetCONF/RPC requests to operate in the blocking
mode. When not passed, NetCONF/RPC operation is always non-blocking. This parameter does
not affect CLI commands as CLI is always considered blocking in nature.
directory remote-directory-name
Specifies the remote directory that contains the TPVM image.
filename image-file-name
Specifies the TPVM Debian image file name.
host [ hostname | ip-address ]
Specifies the remote server. Remote server information can be provided either as a hostname or
ip-address.
password password
Password for the username provide in the user parameter.
sanity [ yes | no ]
Optional parameter. When set to yes, the TPVM image file is verified for size and version number
after being downloaded. When set to no, the TPVM image is downloaded but not verified.
use-vrf vrf-name
Defines the VRF to use to access the remote host.
user user-name
The account that will be used to access the remote host. The password of this account is passed
in the password parameter.
Modes
Privileged EXEC mode
Usage Guidelines
Use the optional sanity key to ensure that the downloaded TPVM image is verified for version and
length after it has been downloaded from the remote server.
Use the optional block key to indicate that NetCONF/RPC calls are considered blocking in nature. By
default, NetCONF/RPC calls are non-blocking. Also, CLI commands are always blocking by nature. This
key does not affect this action when performed through SLX-OS CLI.
Examples
The following example shows the usage of the tpvm download command. This example shows the
interactive mode for this command.
tpvm fileinfo
Displays information for the TPVM image file stored in the /tftpboot/SWD2900 directory of the SLX-
OS. TPVM is installed from this image file.
Syntax
tpvm fileinfo
Modes
Privileged EXEC mode
Usage Guidelines
Debian image file must exist under the /tftpboot/SWBD2900 directory on the SLX-OS device.
If no TPVM image file is found in the above directory, or more than one TPVM images are found, tpvm
fileinfo command will display appropriate error messages.
Examples
The following example shows the use of the tpvm fileinfo command.
SLX# tpvm fileinfo
File Name tpvm-4.2.5-1.amd64.deb
File length 1952933946
File Version 4.2.5
Success
tpvm (mode)
Enters into the TPVM persistence configuration mode. Only one TPVM instance can be configured at
present. Currently, the tpvm-id only allowed value is TPVM, and its optional and default also.
Syntax
tpvm [tpvm-id]
no tpvm [ tpvm-id ]
Modes
Global Configuration Mode
Usage Guidelines
The value for the tpvm-id must always be TPVM.
Examples
This example navigates into the TPVM Configuration mode.
SLX# configure terminal
SLX (config)# tpvm TPVM
SLX (config-tvpm-TPVM)#
ldap host
Configures an LDAP server in the TPVM instance.
Syntax
ldap host hostname [ port portnum ] [ secure ]
ldap [ basedn domain-name ] [ rootdn root-domain-name [ rootdnpw root-
password ] ]
no ldap host hostname port portnum
no ldap [ basedn domain-name ] [ rootdn root-domain-name [ [ rootdnpw
root-password ]
Command Default
By default, an LDAP server is not configured in TPVM.
Parameters
host hostname
Specifies the IPv4 or IPv6 address or the FQDN of the LDAP server.
port portnum
Specifies the port on the LDAP server. The default secure port is 636. The default non-secure
port is 389.
secure
Enables LDAP over TLS.
basedn domain-name
Specifies the base Domain Name.
rootdn root-domain-name
Specifies the root Domain Name.
rootdnpw root-password
Specifies the password for the root Domain Name.
Modes
TPVM Configuration mode
Usage Guidelines
When LDAP replication is in use, no more than 2 LDAP servers can be configured. The base Domain
Name and root Domain Name must be common to both servers.
Configuring a secure LDAP server without importing certificates results in an error. Use the tpvm
config ldap ca-cert command to import certificates.
Examples
This example adds an LDAP host.
SLX (config)# tpvm TPVM
SLX (config-tpvm-TPVM)# ldap host 10.24.15.200
This example adds a secure LDAP host with the default port.
device# tpvm config ldap add host 10.24.15.200 secure
This example configures the base Domain Name, the root Domain Name, and the root Domain Name
password.
SLX (config-tpvm-TPVM)# ldap basedn dc=ldap,dc=hc-fusion,dc=in
rootdn cn=admin,dc=ldap,dc=hc-fusion,dc=in rootdnpw pass123
This example resets the configured port to the default (389 if the port was non-secure, 636 if the port
was secure).
SLX (config-tpvm-TPVM)# no ldap host 1.1.1.1 port
This example disables the secure option for the LDAP server. The configured port remains the same and
is not reset to the default. Use the no ldap host <ip-addr> port command to reset the port.
SLX (config-tpvm-TPVM)# no ldap host 1.1.1.1 secure
This example removes the base Domain Name, the root Domain Name, and the root Domain Name
password.
SLX (config-tpvm-TPVM)# no ldap basedn rootdn rootdnpw
Syntax
ldap ca-cert import protocol SCP host hostname user username password
password directory dirname file filename
no ldap ca-cert
Command Default
By default, certificates are not imported.
Parameters
import
Imports certificates for LDAP over TLS.
protocol SCP
Specifies the SCP protocol.
host hostname
Specifies the host name or IPv4 address of the remove server from which the CA certificate is
imported.
user username
Specifies the login name for the remote server.
password password
Specifies the password associated with the user name.
directory dirname
Specifies the name of the remote directory that contains the certificate.
file filename
Specifies the file name of the certificate.
Modes
TPVM Configuration mode
Usage Guidelines
You cannot remove certificates from configured secure LDAP servers. Use the ldap command to
disable the secure option and then remove the certificates.
Examples
This example imports certificates needed for the secure LDAP server configuration.
SLX (config-tpvm-TPVM)# ldap ca-cert import protocol SCP host 10.6.46.51
user fvt password pray4green directory /home/cert filename cacert.pem
Syntax
ntp { ipv4-address | ipv6-address }
Parameters
{ ipv4-address | ipv6-address }
Configures the NTP server by their IPv4 and / or IPv6 address.
Modes
TPVM Configuration mode
Usage Guidelines
Up to five (5) NTP servers can be configured for TPVM using their IPv4 and / or IPv6 addresses.
Examples
This example configures an IPv6 NTP server address.
SLX(config-tpvm-1)# ntp 100:23::45:55
SLX(config-tpvm-1)#
dns
Configures the DNS server details for the TPVM instance. DNS configuration is supported for IPv4 and
IPv6 addresses.
Syntax
dns primary-server [ ipv4-addr | ipv6-addr ] secondary-server [ ipv4-addr
| ipv6-addr ] { domain domain-name }
no dns [ primary-server ] [ secondary-server ] [ domain ]
Command Default
By default, a DNS server is not configured in TPVM.
Parameters
primary-server [ ipv4-addr | ipv6-addr ]
Adds a DNS server. Specifies the mandatory (primary) DNS server IP. DNS server IP can be in
IPv4 or IPv6 format.
secondary-server [ ipv4-addr | ipv6-addr ]
Adds a secondary DNS server. This server will be used to resolve addresses in case the primary
DNS server fails for any reason. Secondary DNS server IP can be in IPv4 or IPv6 format.
domain-name domain-name
Specifies the domain name for the DNS server. You can configure only one domain name.
Modes
TPVM Configuration mode
Usage Guidelines
• When configuring DNS servers, both the primary and secondary servers should have the same IP
address format.
• When changing the DNS server IP of the primary server from one IP format to another, the
secondary DNS server configuration will not be retained and must be reconfigured.
• The secondary DNS server IP cannot be changed from one IP format to another without making the
same change to the primary DNS server. You cannot modify only the secondary DNS server.
Examples
This example shows the configuration of a IPv4 primary DNS server.
SLX (config-tpvm-TPVM)# DNS primary-server 10.9.9.53
SLX (config-tpvm-TPVM)#
This example shows the configuration of a IPv6 primary DNS server and configures its domain.
SLX(config-tpvm-TPVM)# dns primary-server 100:23::45:55
SLX(config-tpvm-TPVM)# dns primary-server 100:23::45:55 domain example.lan
SLX(config-tpvm-TPVM)# dns
primary-server 100:23::45:55
domain example.lan
This example removes the secondary DNS server configuration from the TPVM.
SLX (config-tpvm-TPVM)# no dns secondary-server
Syntax
hostname hostname
no hostname
Command Default
The default Hostname is tpvm.
Parameters
hostname
The TPVM Hostname.
Modes
TPVM Configuration mode
Usage Guidelines
The no form of this command resets the hostname to its default value of tpvm.
The length of the Hostname should be between 1 to 64 characters. The starting letter should be an
alphabet.
The allowed characters are alphabets (a-z), numbers(0-9), “.”(dot), and “-“(hyphen).
Note
Configuring TPVM hostname from the SLX device is not recommended when EFA is
deployed. Doing so will cause unknown state for the EFA and could lead to EFA downtime. To
change the TPVM Hostname, use the procedures provided in EFA documentation. Refer EFA
documents for hostname restrictions and format.
Examples
Example to update the hostname in TPVM
SLX (config-tpvm-TPVM)# hostname mytpvm
Syntax
timezone <timezone name>
no timezone
Command Default
The default timezone is Etc/GMT.
Parameters
timezone name
Timezone to assign.
Modes
TPVM Configuration mode
Examples
Example to update the timezone in TPVM.
SLX (config-tpvm-TPVM)# timezone Etc/GMT
Syntax
trusted-peer ip ipv4-address password sudo-user-password [sudo-user
username ]
no trusted-peer ip ipv4-address
Command Default
None.
Parameters
ipv4-address
Specifies the IPv4 address of the Peer TPVM.
sudo-user username
Specifies the SUDO User in the Peer TPVM. The default sudo-user is extreme. User-name length
varies from 1-32 characters.
password sudo-user-password
Password for sudo-user in Peer TPVM. Password length varies from 1-512 characters. Special
characters are not supported as part of the password are: double quote (“), single quote (‘), back
slash (\), question mark (?), exclamation mark (!) and pipe (|).
Modes
TPVM Configuration mode
Usage Guidelines
The IPv4 address of the Peer TPVM and the password are mandatory parameters.
Examples
This example shows how to add a trusted peer without providing the user ID of the sudo user.
SLX (config-tpvm-TPVM)# trusted-peer ip 10.23.31.67 password password
This example shows how to add a trusted peer and providing the user ID of the sudo user.
SLX (config-tpvm-TPVM)# trusted-peer ip 10.23.31.67 sudo-user extreme password password
Note
This behaviour is common when you try to perform add-add, add-remove, or remove-remove
commands running in parallel.
When the TPVM Peer IP address is not reachable and the user tries to add a trusted peer.
SLX (config-tpvm-TPVM)# trusted-peer ip 10.23.31.68 sudo-user extreme password password
Failed to connect to 10.23.31.68
When the user provides an invalid credential when adding a trusted peer.
SLX (config-tpvm-TPVM)# trusted-peer ip 10.23.31.67 sudo-user test password password
Check input credentials.
Note
This message is displayed when invalid username or invalid password is supplied while
creating a trusted peer.
When the user account used to access the remote trusted peer is not in the sudo user's list or the
account is not configured properly.
SLX (config-tpvm-TPVM)# trusted-peer ip 10.23.31.67 sudo-user testuser password password
Check sudouser configuration for testuser user.
This example shows how to remove a configured trusted peer without providing the remote peer's sudo
user account user name:
SLX (config-tpvm-TPVM)# no trusted-peer ip 10.23.31.67 password password
This example shows how to remove a configured trusted peer by providing the remote peer's sudo user
account user name:
SLX (config-tpvm-TPVM)# no trusted-peer ip 10.23.31.67 sudo-user extreme password password
When trying to remove a trusted peer but the peer is not reachable.
SLX (config-tpvm-TPVM)# no trusted-peer 10.23.31.68 sudo-user extreme password password
Failed to connect to 10.23.31.68
when trying to remove a trusted peer, but the user credentials are incorrect.
SLX (config-tpvm-TPVM)# no trusted-peer ip 10.23.31.67 sudo-user extreme password
wrognpass
Check input credentials.
Note
This message is displayed when invalid username or invalid password is supplied while
removing the trusted peer.
When the user account used to access the remote trusted peer is not in the sudo user's list or the
account is not configured properly.
SLX (config-tpvm-TPVM)# no trusted-peer ip 10.23.31.67 sudo-user testuser password
password
Check sudouser configuration for testuser user.
Syntax
auto-boot
no auto-boot
Modes
TPVM Configuration mode
Examples
To start TPVM at the next reboot of SLX-OS :
SLX (config-tpvm-TPVM)# auto-boot
Syntax
disk { name { disk_name | auto } { size disk_size }
disk { name { disk_name | auto } { size disk_size }
Parameters
name
disk_name
Adds a new disk to TPVM. Name of the disk to be added if the auto keyword is not specified.
auto
Assigns a disk name automatically. See the Usage Guidelines.
size disk_size
Size of the disk (any positive integer). See the Usage Guidelines.
no disk name
Removes a disk from TPVM.
disk_name
Name of the disk to be removed. See the Usage Guidelines.
Modes
TPVM Configuration mode
Usage Guidelines
If the auto keyword is not used with the tpvm disk command, the name of the disk must be that of
the next disk. For example, if the last disk added to the system is vdb, the name of the next disk must
be vdc.
You can add one of the following suffixes to specify disk size:
• b or B (bytes)
• k or K (kilobytes)
• m or M (megabytes)
• g or G (gigabytes)
The maximum number of disks supported is currently 3 and if the number of allocated disks exceeds
this number, the add_disk keyword fails. Also, the total disk capacity for TPVM is limited to 117
gigabytes on the SLX 9540 and SLX 9640, and limited to 68.7 gigabytes on the SLX 9150 and SLX
9250.
If the auto keyword is not used with the remove_disk command, the name of the disk must be that
of the last disk added to the system.
Important
If the disk is mounted, it must be unmounted before it is removed from the system. Otherwise,
the next added disk will be labeled incorrectly. If this happens, TPVM must be rebooted to
recover.
Examples
To add a new disk to TPVM, by either using the auto keyword or specifying a disk name:
SLX (config-tpvm-1)# disk name auto 10g
disk add succeeds
Note
The maximum number of disks supported is 3. If the number of allocated disks exceeds this
number, the disk add name keywords fail. Also, the total disk capacity for TPVM is limited
to 117 gigabytes on the SLX 9540 and SLX 9640, and limited to 68.7 gigabytes on the SLX
9150 and SLX 9250. If you exceed this limit when you create a disk, the disk add name
keywords fail.
Important
If the disk is mounted, it must be unmounted before it is removed from the system. Otherwise,
the next added disk will be labeled incorrectly. If this happens, TPVM must be rebooted to
recover.
Syntax
password password
no password
Parameters
password
The password to be assigned to the default user account extreme.
Modes
TPVM Configuration mode
Examples
The following example shows how to set the password for the default extreme account.
SLX (config-tpvm-TPVM)# password 2#eXtreme%4
Syntax
allow-pwless
no allow-pwless
Parameters
none
Modes
TPVM Configuration mode
Examples
The following example shows how to enable password less login for SSH and SUDO accounts.
SLX (config-tpvm-1)# allow-pwless
Syntax
interface management ip { dhcp | ipv4-address/net-mask [ gw gw-ip-
address ] }
interface management ipv6 { ipv6-address/length [ gw gw-ipv6-address ] }
no interface management ip { dhcp | ip-address [ gw gw-ip-address ] }
no interface management ipv6 { ipv6-address/length [ gw gw-ipv6-
address ] }
Parameters
dhcp
Indicates that the IPv4 address of the management interface is assigned by DHCP.
ip-address/net-mask
Configures the static IPv4 address of the management interface and its net-mask.
gw gw-ip-address
The interface gateway IPv4 address.
ipv6-address/length
Configures the static IPv6 address of the management interface along with the prefix length.
gw gw-ipv6-address
The interface gateway IPv6 address cannot be changed dynamically.
Modes
TPVM Configuration mode
Examples
The following example shows how to configure the static IPv6 address and default gateway for the
TPVM management interface eth0.
SLX(config-tpvm-TPVM)# interface management ipv6 100:23::45:55/24
SLX (config-tpvm-TPVM)#
Syntax
tpvm deploy
no deploy
Parameters
no parameters
Modes
Privileged EXEC mode
Usage Guidelines
As described above, this configuration will deploy the TPVM instance -
Usage Guidelines
• There is no installing or running TPVM instance.
• The TPVM Debian image file is available at /tftpboot/SWBD2900 folder.
• All intermediate installation steps will succeed, but if it fails, it cleans up the partial installation if any.
Usage Guidelines
• It installs the TPVM Debian file.
• It starts the TPVM (Guest OS) instance.
• It applies the TPVM instance related configuration, to the TPVM/Guest-OS, if found persisted in the
SLX configuration database.
Usage Guidelines
Note
Configurations like password and interface management are applied before starting the
TPVM, means they will always fail, if attempted after deploy. So they should be set in the SLX
configuration database before deploy. Alternatively, TPVM stops through the command tpvm
stop, and then these two configurations will be set in the tpvm config mode, followed by the
tpvm start. However, re-issuing the config deploy command, will be an idempotent operation
with a void affect.
Logs:
It is time consuming operation, which may take few minutes. It publishes following logs.
[DCM-1451], 818,, INFO, SLX, Tpvm-id:TPVM operation:deploy mode:sync started.
[DCM-1452], 819,, INFO, SLX, Tpvm-id:TPVM operation:deploy mode:sync completed.
Examples
The following example configures the default installation of TPVM.
SLX(config-tpvm-TPVM)# deploy
2021/06/15-17:06:17, [DCM-1451], 818,, INFO, SLX, Tpvm-id:TPVM operation:deploy mode:sync
started.
2021/06/15-17:09:10, [DCM-1452], 819,, INFO, SLX, Tpvm-id:TPVM operation:deploy mode:sync
completed.
The following example performs the installation of the TPVM with few already persisted configurations.
Use the show tpvm config … commands to display the output of various configurations, or use the “get-
tpvm-detailRPC for all operational data.
SLX# conf
Entering configuration mode terminal
SLX(config)# tpvm
SLX(config-tpvm-TPVM)# hostname myTpvm
SLX(config-tpvm-TPVM)# interface management ip dhcp
SLX(config-tpvm-TPVM)# password newpassword
SLX(config-tpvm-TPVM)# ntp time.google.com
SLX(config-tpvm-TPVM)# ntp ntp.ubuntu.com
SLX# conf
Entering configuration mode terminal
SLX(config)# tpvm
SLX(config-tpvm-TPVM)# deploy
2021/06/15-17:22:42, [DCM-1451], 820,, INFO, SLX, Tpvm-id:TPVM operation:deploy mode:sync
started.
2021/06/15-17:26:20, [DCM-1452], 821,, INFO, SLX, Tpvm-id:TPVM operation:deploy mode:sync
completed.
tpvm upgrade
Upgrades the TPVM image. This command downloads the TPVM Debian image file using SCP or SFTP
or FTP servers. Any previously installed TPVM instance is upgraded, and TPVM configuration from the
SLX configuration database is applied, if available. Upgrades can be full or incremental. By default, full
upgrades are performed.
Syntax
tpvm upgrade directory directory-name filename image-filename incremental
host hostname password password protocol [ SCP | SFTP | FTP ]
snapshot tpvmid tpvm-instance-name use-vrf vrf-name uselocalfile user
username
Parameters
directory directory-name
Specifies the remote directory that contains the TPVM image.
file image-filename
The Debian TPVM image file name.
incremental
Use to perform an incremental TPVM upgrade.
host hostname
Specifies the host name or IPv4/IPV6 address of the server from where the TPVM image is to be
downloaded.
password password
Specifies the password associated with the user name.
protocol [ SCP | SFTP | FTP ]
Specifies the protocol to be used to download the TPVM image.
snapshot
Takes a snapshot of the current TPVM instance if any, before starting the upgrade process.
tpvmid tpvm-instance-name
The ID of the TPVM that needs to be upgraded. This value is always TPVM and cannot be
modified.
use-vrf vrf-name
The VRF that will be used to access the remote server from where TPVM image is to be
downloaded.
user username
Specifies the login name for the remote server.
uselocalfile
Indicates that the TPVM upgrade process must use the TPVM Debian file located in the /
tftpboot/SWBD2900 directory. Use the snapshot key to indicate that a snapshot must be taken
during the upgrade process.
Modes
Normal EXEC mode
Usage Guidelines
tpvm upgrade is an exec CLI.
The new TPVM Debian image file is downloaded to the /tftpboot/SWBD2900 directory. If any previous
image file is present, it is moved to the /support/OldTpvm directory, provided enough space is available.
Note
The snapshot feature may delete this subfolder, /support/OldTpvm, to free space disk space
when required.
During download of the TPVM image file, if TPVM is running, it is not stopped till the download is
complete. On completion, the running TPVM instance (if any) is stopped and then uninstalled. If the
snapshot parameter is used while upgrading, then a snapshot of the running TPVM is created.
The download may fail due to networking issues or not having enough free space on the device.
If SLX OS configuration database has TPVM configurations set, specially config deploy, then the
upgrade process shall further install the new TPVM Debian image file, start the instance, and also apply
other TPVM related persisted configurations from the SLX configuration database.
The default behavior of the tpvm upgrade command is to perform a full upgrade of the TPVM
instance. To perform an incremental upgrade, you must use the incremental keyword explicitly. While
performing the incremental upgrade, the Ubuntu Packages, TPVM script files, and XML files will be
upgraded.
Note
When you downgrade the existing TPVM version to a version that is lower than SLXOS version
20.4.1, then you will have to remove the IPv6 configurations before downgrading. Appropriate
warning will be displayed.
Examples
This example shows the command to perform a full upgrade of TPVM.
SLX# tpvm upgrade directory /proj/tpvm_upgrade/ filename tpvm-4.5.0-0.amd64.deb host
10.10.10.1 user fav password testpassword protocol scp use-vrf mgmt-vrf
tpvm snapshot
Manually creates and manages TPVM snapshots. These snapshots can then be used to restore a TPVM
to its previous state post any TPVM crash.
Syntax
tpvm snapshot [ create | delete | revert ] tpvm-id
Parameters
create
Creates a snapshot of the current TPVM and stores it to the SLX device.
delete
Deletes an existing snapshot.
restore
Restores the stored TPVM snapshot.
Modes
Privilege Execution mode
Usage Guidelines
Only one snapshot can be created and stored on the SLX device at any point of time.
Examples
The following example creates a snapshot
SLX (config)# tpvm snapshot create
traceroute
Traces the network path of packets as they are forwarded to a destination address.
Syntax
traceroute { ip-address | host-name | ipv6 [ ipv6-address| host-name ] }
[ interface ] [ maxttl value ] [ minttl value ] [ src-addr src-addr ]
[ timeout seconds ] [ vrf { mgmt-vrf | default-vrf |vrf-name } ]
Parameters
ip-address
Specifies the IP address of the destination device.
host-name
Specifies the hostname of the destination device.
ipv6 ipv6-address
Specifies the IPv6 address of the destination device.
interface
Selects the output interface.
maxttl value
Maximum Time To Live value in a number of hops.
minttl value
Minimum Time To Live value in a number of hops.
src-addr address
Specifies the IPv4 or IPv6 address of the source device.
timeout seconds
The traceroute timeout value.
vrf
Specifies a VRF on which to run a traceroute.
mgmt-vrf
Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf-name
Specifies a VRF name.
Modes
Privileged EXEC mode
Examples
This example executes an IPv6 traceroute, with minimum and maximum TTL values.
device# traceroute ipv6 fec0:60:69bc:92:218:8bff:fe40:1470
maxttl 128 minttl 30 src-addr fec0:60:69bc:92:205:33ff:fe9e:3f20 timeout 3
track (VRRP)
Enables VRRP tracking for a specified interface. VRRP Extended (VRRP-E) sessions can track a
specified interface or a network.
Syntax
track { ethernet slot/port| port-channel number } [ priority value ]
track network { ip-addressmask | ipv6-address/mask } [ priority value ]
no track { ethernet slot/port| port-channel number } [ priority value ]
no track network { ip-address/mask | ipv6-address/mask } [ priority
value ]
Command Default
The default priority value is 2.
Parameters
ethernet slot port
Specifies a valid, physical Ethernet subtype with appropriate slot and port number.
port-channel number
Specifies the port-channel number.
priority value
The track priority is a number from 1 through 254, and is used when a tracked interface or
network up or down event is detected. For VRRP, if the tracked interface goes offline, the
specified priority value is subtracted from the priority of the current device. For VRRP-E, if the
tracked interface or network goes offline, the current device priority is reduced by the configured
priority value. If the tracked interface or network comes online, the specified priority value is
added to the priority of the current device.
network
Enables tracking of a specified network. Network tracking is supported only on VRRP-E sessions.
ip-address
Specifies an IPv4 network address.
ipv6-address
Specifies an IPv6 network address.
mask
Specifies a mask for the associated IP or IPv6 subnet.
Modes
Virtual-router-group configuration mode
Usage Guidelines
This command can be used to track interfaces for VRRP or VRRP-E. Only VRRP-E sessions support
network tracking.
For VRRP, the tracked interface can be any Ethernet or port-channel interface other than the one on
which this command is issued.
The networks to be tracked can be either present or absent from the Routing Information Base (RIB).
The maximum number of interfaces or networks you can track per virtual router is 16.
Enter no track with the specified interface or network to remove the tracked port or tracked network
configuration.
Examples
To set the track port to 2/4 and the track priority to 60:
The following example shows how to configure network 10.1.1.0/24 to be tracked, and if the network
goes down, the VRRP-E device priority is lowered by a value of 20. The lower priority may trigger a
switchover and a backup device with a higher priority becomes the new master for VRRP-E group 1.
traffic-engineering (LSP)
Allocating bandwidth to an LSP lets the LSRs determine how much bandwidth the LSP can consume
and how much of the available bandwidth resources can be advertised.
Syntax
traffic-engineering { [ [ max-burst kbps ] | [ max-rate kbps ] | [ mean-
rate kbps ] ] }
no traffic-engineering { [ [ max-burst kbps ] | [ max-rate kbps ] |
[ mean-rate kbps ] ] }
Command Default
There are no allocated bandwidth allocations in the default mode.
Parameters
max-burst kbps
Specifies the maximum burst rate in bytes. The range is from 0-2147483647.
max-rate kbps
Specifies the maximum rate in kbps. The range is from 0-2147483647.
mean-rate kbps
Specifies the average rate in kbps. The range is from 0-2147483647.
Modes
MPLS LSP configuration mode (config-router-mpls-lsp-lsp_name)
Usage Guidelines
The user can specify an average mean-rate kbps for the data on the LSP. When necessary, data can
travel at max-rate Kbps, as long as the burst sent at the maximum rate contains no more than max-
burst bytes.
Use the traffic-engineering command to configure bandwidth parameters for the dynamic
bypass LSPs to be created for the MPLS protected interface.
When the interface mode mean-rate value not configured at all then all dynamic bypass LSPs are
created with the bandwidth the same as the backup path requested bandwidth. This means that system
tries to create a dynamic bypass LSP with the backup path requested bandwidth and the dynamic
bypass LSP bandwidths can vary based on the backup riding on it.
When the interface mode configured mean-rate value is 0 kbps, then the system creates dynamic
bypasses for backup bandwidth requests of only 0 kbps. When the backup path bandwidth is more
than zero, then this request does not create a new dynamic bypass LSP. This option provides a way to
the user to limit the dynamic bypass creations to only non-bandwidth protected backups.
When the interface mode configured mean-rate value is a non-zero value, then the system does not
create dynamic bypasses for the backups which request backup bandwidth that is more than the
interface mode configured value. When the backup bandwidth is less than, or equal to the configured
value, then the request is used to ride an existing dynamic bypass or to create a new dynamic bypass.
With this configuration, all the newly created dynamic bypasses have a fixed bandwidth, meaning the
value is same as the interface mode user configured non-zero mean-rate value.
A mean-rate value that is more than the current interface reservable bandwidth is not desired.
Configuration succeeds with the new value even when it is more than the interface reservable
bandwidth.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the maximum rate of packets that can go through LSP tunnel1 (in
Kbps).
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp tunnel1
device(config-router-mpls-lsp-tunnel1)# traffic-eng max-rate 20
The following example configures the average rate of packets that can go through LSP tunnel1 (in
Kbps).
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp tunnel1
device(config-router-mpls-lsp-tunnel1)# traffic-eng mean-rate 10
The following example configures the maximum size (in bytes) of the largest burst LSP tunnel1 can
send at the maximum rate.
device# configure
device(config)# router mpls
device(config-router-mpls)# lsp tunnel1
device(config-router-mpls-lsp-tunnel1)# traffic-eng max-burst 10
The following example configures the traffic-engineering maximum rate to 1000000 kbps. for dynamic
bypass MPLS Ethernet interface 2/8.
device# configure
device(config)# router mpls
device(config-router-mpls)# mpls-interface ethernet 2/8
device(config-router-mpls-if-ethernet-2/8)# dynamic-bypass
device(config-router-mpls-if-ethernet-2/8-dynamic-bypass)# traffic-eng max-rate 1000000
traffic-engineering (MPLS)
When an MPLS-enabled device receives an IS-IS TE LSP, it stores the traffic engineering information in
its Traffic Engineering database (TED). The device uses information in the TED when performing
calculations to determine a path for an LSP. The user can configure the device to send out IS-IS TE LSPs
for all of its MPLS-enabled interfaces.
Syntax
traffic-engineering { [ isis [ level-1| level-2 ] ] | [ ospf [ area
[ area_id | all ] ] ] }
no traffic-engineering { [ isis [ level-1| level-2 ] ] | [ ospf [ area
[ area_id | all ] ] ] }
Command Default
By default, the device does not send out IS-IS LSPs with TE extensions for its MPLS-enabled interfaces.
Parameters
isis
Advertise by way of ISIS.
level-1
Traffic-engineering for level-1.
level-2
Traffic-engineering for level-2.
ospf
Advertise by way of OSPF.
area
designate OSPF area.
area_id
Specifies OSPF area ID in IP address format.
all
Advertise in all OSPF areas.
Modes
MPLS policy mode
Usage Guidelines
The no for of the command disables the configuration.
The user must enable the device to send out IS-IS LSPs with TE extensions when the user wants CSPF
to perform constraint-based path selection because information in the TED is used to make path
selections using CSPF, and information in the TED comes from IS-IS LSPs with TE extensions.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the device to send out IS-IS TE LSPs to the level-1 MPLS-enabled
interface.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy)# traffic-engineering isis level-1
transit-session-accounting
Enables traffic statistics for transit sessions.
Syntax
transit-session-accounting
no transit-session-accounting
Command Default
By default, the command is disabled.
Modes
MPLS policy mode.
Usage Guidelines
Use the no form of the command disables the traffic statistics for transit sessions.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example enables transit session accounting.
device# configure
device(config)# router mpls
device(config-router-mpls)# policy
device(config-router-mpls-policy) transit-session-accounting
transport
Specifies the transport protocol for network-elements telemetry streaming.
Syntax
transport { tcp | ssl }
no transport
Command Default
TCP is specified.
Parameters
tcp
Specifies TCP as the telemetry transport protocol.
ssl
Specifies SSL as the as the telemetry transport protocol.
Modes
Telemetry-server configuration mode
Usage Guidelines
This command (and the SSL option) are available only for the gRPC-server implementation. They are
not supported for the external-collector telemetry implementation.
To revert to the default TCP protocol, use the no form of this command.
Examples
The following example enables SSL as the telemetry transport protocol.
device# configure terminal
device(config)# telemetry server
device(config-server-mgmt-vrf)# do telemetry client-cert generate
device(config-server-mgmt-vrf)# transport ssl
device(config-server-mgmt-vrf)# activate
trigger
Defines event-handler triggers. When the trigger-condition occurs, a Python script is run.
Syntax
trigger trigger-id raslog raslog-id [ pattern posix-ext-regex ]
trigger trigger-id raslog raslog-id [ pattern trigger-pattern ]
no trigger [ trigger-id ]
Command Default
No trigger is defined.
Parameters
trigger-id
Specifies an ID number for the trigger. Valid values are 1 through 100, and must be unique per
event-handler profile.
raslog raslog-id
Specifies a RASlog message ID as the trigger. String can be 1 through 32 characters long.
pattern posix-ext-regex
Specifies a POSIX extended regular expression to search within the specified RASlog message
ID.
pattern trigger-pattern
Specifies a sequence of strings with included regular expressions to search within the specified
RASlog message ID. Contains alphabets, digits and all characters supported in regex. String can
be 1 through 128 characters long.
Modes
Event-handler configuration mode
Usage Guidelines
You can create from 1 through 100 triggers per profile.
You can also define one trigger as part of the event-handler command.
To delete one or all triggers, use the no form of this command, as follows:
• To delete all triggers, enter no trigger.
• To delete a specific trigger, enter no trigger trigger-id
Note
You cannot delete the last remaining trigger from an activated event-handler profile.
You can modify an existing trigger without deleting it and then re-creating it.
If the event-handler for which you are modifying triggers is active on the device, the changes take effect
with no need to de-activate and re-activate the event-handler.
Examples
The following example defines triggers in two event handlers.
device# configure terminal
device(config)# event-handler eventHandler2
device(config-event-handler-eventHandler2)# trigger 1 raslog NSM-1001
device(config-event-handler-eventHandler2)# trigger 2 raslog NSM-1003
The following example defines a trigger that uses POSIX extended REGEX to search for a match within
a specified RASlog message ID.
device# configure terminal
device(config-event-handler-eventHandler1)# event-handler eventHandler2
device(config-event-handler-eventHandler2)# trigger 1 raslog NSM-1003 pattern Interface
Ethernet 1/[1-9] is link down
RASlog message NSM-1003 includes "interface interface-name is link down", indicating that
an interface is offline because the link is down. The REGEX searches within such a message for an
interface from 1/1 through 1/9.
trigger-function
Specifies whether the action runs only if all of the triggers occur or if one is sufficient, for an
implementation of an event-handler profile when multiple triggers are defined for an event-handler
action.
Syntax
trigger-function { OR | AND time-window seconds }
no trigger-function
Command Default
The event-handler action runs if any of the triggers occur.
Parameters
OR
The event-handler action runs if any of the triggers occur.
AND
The event-handler action runs only if all of the triggers occur.
time-window seconds
In seconds, specify the time window within which all of the triggers must occur in order that the
event-handler action runs.
Following an initial triggering of an event-handler action, any subsequent trigger launches the
action an additional time if the following conditions are true:
• The trigger-mode parameter is set to the default each-instance.
• The subsequent trigger occurs within the specified time-window.
Modes
Event-handler activation mode
Usage Guidelines
The no form of this command sets the trigger-function setting to the default OR option.
Examples
The following example determines that the event-handler action runs only if all of the triggers occur
within 120 seconds.
device# configure terminal
device(config)# event-handler activate eventHandler1
device(config-activate-eventHandler1)# trigger-function AND time-window 120
trigger-mode
For an implementation of an event-handler profile, specifies if recurring trigger conditions can launch an
event-handler action more than once.
Syntax
trigger-mode mode
no trigger-mode
Command Default
Each time the trigger condition occurs, the event-handler action is launched.
Parameters
mode
Specifies if an event-handler action can be triggered only once or more than once.
each-instance
The event-handler action is launched on each trigger instance received.
on-first-instance
As long as the device is running, the event-handler action is launched only once. Following a
device restart, the event-handler action can be triggered again.
only-once
For the duration of a device configuration, the event-handler action is launched only once.
Modes
Event-handler activation mode
Usage Guidelines
The no form of this command resets the trigger-mode setting to the default each-instance
option.
Examples
The following example sets the trigger mode to on-first-instance.
device# configure terminal
device(config)# event-handler activate eventHandler1
device(config-activate-eventHandler1)# trigger-mode on-first-instance
trustpoint sign
Configures the trustpoint to the server certificate profile that is used to sign the server certificate.
Syntax
trustpoint sign { trustpoint-name }
no trustpoint sign
Command Default
By default, the trustpoint is not configured.
Parameters
trustpoint-name
Defines the name of the trustpoint you are configuring. This name needs to be the same as that
of the trustpoint created by the crypto ca trustpoint command. The string for the name
cannot be left blank. The length of the string can range from 1 through 64 characters.
Modes
SSH server profile server configuration mode
Usage Guidelines
Use the no form of the command to remove the trustpoint configured on the device.
The trustpoint must be configured before you run this command. The same trustpoint must be used to
sign and import the server certificate using the following commands: crypto ca authenticate,
crypto ca enroll, crypto ca import, and crypto ca trustpoint.
Examples
The following example configures a trustpoint named myca.
device# configure terminal
device(config)# ssh server certificate profile server
device(ssh-server-cert-profile-server)# trustpoint sign myca
ttl
Configures the time to live (TTL) value for a tunnel interface.
Syntax
ttl ttl-value
no ttl
Parameters
ttl-value
Specifies the TTL value. The range is from 1 to 255.
Command Default
The default TTL value is 255.
Modes
Interface tunnel configuration mode
Usage Guidelines
Use the no form of this command to revert to the default value.
Examples
This example configures the TTL value for the tunnel interface.
device# configure terminal
device (config)# interface tunnel 5
device(config-intf-tunnel-5)# mode gre ip
device(config-intf-tunnel-5)# source 10.1.1.10
device(config-intf-tunnel-5)# source ve 4
device(config-intf-tunnel-5)# destination 10.1.1.11
device(config-intf-tunnel-5)# router-interface ve 3
device(config-intf-tunnel-5)# dscp-ttl-mode pipe
device(config-intf-tunnel-5)# ttl 64
tunable-optics
This command assigns channels to tunable optic interfaces (T-SFP+) for specific wavelengths.
Syntax
tunable-optics sfpp channel channel_number
Command Default
The T-SFP+ optic defaults to a "no wavelength" state before being activated.
Modes
Interface configuration mode
Usage Guidelines
Tunable SFP+ optics are optional hardware that can be installed with optical SFPs.
If you are installing a T-SFP+ in a 144S port, the T-SFP+ optic needs to be installed in both ends of the
cable. The T-SFP+ at each end of the cable link must be configured at the same wavelength by setting
them to the same channel on each device.
Failure to duplicate the channel setting may allow the link to come online, but the link behavior may be
erratic.
If the firmware determines an error is exceeding a specified limit, a RASLOG message event occurs and
the port is taken offline.
The T-SFP+ interface defaults to a "no wavelength" state. When a supported Extreme device boots, the
firmware sets the desired wavelength of the T-SFP+ optic.
When a T-SFP+ interface is installed it is very important that the interface is configured to the same
channel (wavelength) at both ends. Use the show media tunable-optic-sfpp command to
determine the currently configured channel.
T-SFP+ interfaces are tuned to specific wavelengths and frequencies using pre-defined channels.
Refer to the Extreme SLX-OS Monitoring Configuration Guide for complete information on tunable
optics.
The following tables lists the frequency and wavelength assigned to channels for tunable SFP+ optic
interfaces.
Examples
Typical command example.
device# configure terminal
device(config)# interface ethernet 0/1
device(conf-if-eth-0/1)# tunable-optics sfpp channel 5
device(conf-if-eth-0/1)# do show media optical-monitoring
N/A - Not Available.
N/S - Optical-monitoring Not Supported.
Port Module Supply Channel Frequency Wavelength Bias
Channel
Temperature Voltage TX Power Error Error Current
RX Power
( C ) ( mVolts ) ( uWatts ) ( GHz ) ( nm ) ( mAmps )
( uWatts )
=============== =========== ============ ============ ========= ========== ============
============
Eth 0/1 36 3291.6 694.4 0.0 0.000 38.550
748.8
tunneled-arp-trap enable
Enables ARP (Address Resolution Protocol) packets that come through a tunnel to be trapped to CPU.
Syntax
tunneled-arp-trap enable
no tunneled-arp-trap enable
Command Default
By default, ARP packets that come through a tunnel are trapped to CPU.
Modes
Global configuration mode
Usage Guidelines
Use the no form of the command to disable the trapping of ARP packets that come through a tunnel.
Examples
The following example enables the trapping of ARP packets that come through a tunnel.
device# configure terminal
device(config)# tunneled-arp-trap enable
The following example disables the trapping of ARP packets that come through a tunnel.
device# configure terminal
device(config)# no tunneled-arp-trap enable
tx-frame-count
Configures the transmission frame count.
Syntax
tx-frame-count frame-count
no tx-frame-count
Parameters:
frame-count
Specifies the transmission frame count. The range is from 1 to 1000.
Command Default
The default value for tx-frame-count is 10 .
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the transmission frame count configuration.
Examples
This example shows how to configure the transmission frame count.
device# configure terminal
device (config-cfm)# protocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device(config-cfm-y1731-test-profile-my_test_profile)# tx-interval 60
device(config-cfm-y1731-test-profile-my_test_profile)# measurement-interval 30
device(config-cfm-y1731-test-profile-my_test_profile)# start at 00:00:00 daily
device(config-cfm-y1731-test-profile-my_test_profile)# stop at 23:59:00
device(config-cfm-y1731-test-profile-my_test_profile)# cos 7
device(config-cfm-y1731-test-profile-my_test_profile)# threshold maximum 3294967295
device(config-cfm-y1731-test-profile-my_test_profile)# tx-frame-count 300
tx-interval
Configures the transmission interval.
Syntax
tx-interval tx-interval
no tx-interval
Parameters:
tx-interval
Specifies the transmission interval in seconds. Valid values can be 1, 10, 60, or 600 seconds.
Command Default
The default value for tx interval is 1 second.
Modes
Y1731 configuration mode
Usage Guidelines
Use the no form of the command to delete the transmission interval configuration.
Examples
This example shows how to configure the transmission interval.
configure terminal
device (config-cfm)# prtocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device(config-cfm-y1731-test-profile-my_test_profile)# tx-interval 60
tx-label-silence-timer
Sets the length of the EOL transmit label silence timer for LDP-IGP synchronization.
Syntax
tx-label-silence-timer milliseconds
no tx-label-silence-timer
Command Default
The default value is 1000 milliseconds.
Parameters
milliseconds
Specifies the EOL transmit label silence timer in milliseconds. Enter an integer from 100 to
60000.
Modes
MPLS LDP EOL configuration mode
Usage Guidelines
Use the no form of the resets the default value of 1000 milliseconds.
Examples
The following example sets the length of time for the EOL transmit label silence timer to 2000
milliseconds.
device(config)# router mpls
device(config-router-mpls)# ldp
device(config-router-mpls-ldp)# eol
device(config-router-mpls-ldp-eol)# tx-label-silence-timer 2000
type
Configure a profile type as ETH-DM or ETH-SLM.
Syntax
type [ delay-measurement | synthetic-loss-measurement ]
Parameters:
delay-measurement
Specifies the profile type as delay management.
synthetic-loss-measurement
Specifies the profile type as synthetic loss measurement.
Modes
Y.1731 configuration mode
Examples
This example shows how to configure the profile type as delay measurement or as synthetic loss
measurement .
device# configure terminal
device (config-cfm)# prtocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type delay-measurement
device# configure terminal
device (config-cfm)# prtocol cfm
device (config-cfm)# y1731
device(config-cfm-y1731)# test-profile my_test_profile
device(config-cfm-y1731-test-profile-my_test_profile)# type synthetic-loss-measurement
udld enable
Enables the Unidirectional Link Detection (UDLD) protocol on an interface.
Syntax
udld enable
no udld enable
Command Default
Disabled on interfaces by default.
Modes
Interface configuration mode
Usage Guidelines
Use no udld enable to unblock the interface if it has been blocked by the UDLD protocol.
Examples
The following example enable UDLD on a specific Ethernet interface.
device# configure terminal
device(config)# interface ethernet 0/1
device(conf-if-eth-0/1)# udld enable
underflow-limit
Sets the underflow-limit to the input value.
Syntax
underflow-limit value
no underflow-limit
Command Default
The default is set to zero (0), meaning there is no premature adjustment because of underflow.
Parameters
value
The selected number of consecutive samples that have to be below the threshold to trigger a
premature adjustment.
Modes
MPLS sub-configuration modes
config-mpls-autobw-template-template1
config-mpls-lsp-lsp1
Usage Guidelines
The no function of the command sets the underflow-limit back to the default value.
MPLS is supported only on devices based on the DNX chipset family. For a list of such devices, see
"Supported Hardware".
Examples
The following example configures the underflow-limit in auto-bandwidth template1 to 10.
device>configure
device(config)# router mpls
device(config-router-mpls)# autobw-template template1
device(config-router-mpls-autobw-template-template1)# underflow-limit 10
underlay-mdt-default-group
Creates a underlay MDT default group instance.
Syntax
underlay-mdt-default-groupGroup-IP
no underlay-mdt-default-group
Command Default
Global configuration mode
Parameters
Group-IP
Specifies the IP address of the group.
Modes
Global configuration mode
Usage Guidelines
The default mdt group needs to be configured first and removed last in the optimized-replication mode.
When all vlans are removed from a group and the group config is removed. The same rule applies to
BDs as well.
Examples
The following example configures underlay mdt default group.
underlay-mdt-default-group 239.0.0.100
underlay-mdt-group
Creates a underlay MDT group instance.
Syntax
underlay-mdt-group GROUP-IP [ default | [ [ vlan [ add | remove VLAN , |
VLAN-RANGE + ] | [ [ bridge-domain [ add | remove ] ( BD , | ( BD-
RANGE ,) + ]
no underlay-mdt-group
Command Default
Global configuration mode
Parameters
add
Adds the VLAN or bridge-domain.
bridge-domain
Specifies the bridge-domain.
(BD, BD-RANGE) +
Specifies BD and BD range.
default
Specifies the default group.
GROUP-IP
Specifies the IP address of the Group-IP.
remove
Removes the selected VLAN or bridge-domain.
vlan
Specifies the VLAN.
(VLAN, VLAN-RANGE) +
Specifies VLAN and VLAN-RANGE.
Modes
Global configuration mode
Usage Guidelines
The default mdt group needs to be configured first and removed last in the optimized-replication mode.
When all vlans are removed from a group and the group config is removed. The same rule applies to
BDs as well.
Examples
The following example configures underlay mdt group.
underlay-mdt-group 239.0.0.1 vlan add 10-12,20
underlay-mdt-group 239.0.0.3 vlan add 30
underlay-mdt-group 239.0.0.4 vlan add 40
underlay-mdt-group 239.0.0.5 bridge-domain add 50,60-70
undeploy-force
Removes the configured TPVM and its associated disks.
Syntax
undeploy-force
Modes
TPVM Configuration mode
Usage Guidelines
The no format of this command is not available.
The no deploy command will bring down TPVM and remove the TPVM and associated disks from the
running configuration. However, in some cases, the command might fail to remove the configured disks.
To rectify this issue, use this command to completely remove the TPVM and its associated disks. This
command will remove the associated disks from the running configuration without failing.
You can also use this command to forcibly remove any virtual disks that were retained when TPVM was
uninstalled using the no deploy command.
Examples
This example removes the configured TPVM and its associated disks:
SLX (config-tpvm-TPVM)# undeploy-force
unlock username
Unlocks a locked user account.
Syntax
unlock username name
Parameters
name
Specifies the name of the user account.
Modes
Privileged EXEC mode
Usage Guidelines
Use this command to unlock a user who has been locked out because of unsuccessful login attempts. A
user account is locked by the system when the configured threshold for login retries has been reached.
Examples
The following example unlocks a user account.
device# unlock username testUser
Result: Unlocking the user account is successful
update onie
Command to download and install the ONIE, ONIE-GRUB, and DIAG images.
Syntax
update onie { ftp | sftp | scp } directory directory-name file image-
file-name host ip-address user user-name password password use-vrf
vrf-name
Modes
Privileged EXEC Mode
Usage Guidelines
This command is only supported on the SLX 9150, SLX 9250, Extreme 8720, and Extreme 8520 devices.
This command will install ONIE, DIAG, and ONIE-GRUB at the same time. There will be a total of three
device reboots during the update process as each item is installed.
Note
ONIE, DIAG, and ONIE-GRUB cannot be installed individually.
Examples
This example shows the ONIE update command usage.
SLX# update onie sftp host 10.10.10.1 user admin-user password password directory /media/
image-store/ filename onie-updater-x86_64-quanta_dnv-r0-14-ix8t_3abca use-vrf mgmt-vrf
update-time
Configures the interval at which BGP next-hop tables are modified. BGP next-hop tables should always
have IGP (non-BGP) routes.
Syntax
update-time sec
no update-time sec
Command Default
This option is disabled.
Parameters
sec
Update time in seconds. Range is from 0 through 30. Default is 5 seconds.
Modes
BGP address-family IPv4 unicast configuration mode
Usage Guidelines
Use the no form of this command to restore the defaults.
The update time determines how often the device computes the routes (next-hops). Lowering the value
set by the update-time command increases the convergence rate.
By default, the device updates the BGP4 next-hop tables and affected BGP4 routes five seconds
following IGP route changes. Setting the update time value to 0 permits fast BGP4 convergence for
situations such as a link failure or IGP route changes, starting the BGP4 route calculation in subsecond
time.
Note
Use the advertisement-interval command to determine how often to advertise IGP
routes to the BGP neighbor.
Examples
This example sets the BGP4+ update-time interval to 30.
usb
Enables or disables an attached USB device. The device is inaccessible until it is enabled.
Syntax
usb { on | off }
Parameters
on
Turns the USB device on.
off
Turns the USB device off.
Modes
Privileged EXEC mode
Usage Guidelines
This command is executed on the local device. A device reload automatically turns the USB device off.
Examples
To enable a USB device attached to the local device:
device# usb on
usb dir
Lists the contents of an attached USB device.
Syntax
usb dir
Modes
Privileged EXEC mode
Usage Guidelines
This command is executed on the local device. The USB device must be enabled before this function is
available.
Examples
To list the contents of the USB device attached to the local device:
device# usb dir
firmwarekey\ 0B 2016 Aug 15 15:13
support\ 106MB 2016 Aug 24 05:36
support1034\ 105MB 2016 Aug 23 06:11
config\ 0B 2016 Aug 15 15:13
firmware\ 380MB 2016 Aug 15 15:13
Available space on usbstorage 74%
usb remove
Removes a file from an attached USB device.
Syntax
usb remove directory directory file file
Parameters
directory directory
Specifies one the name of the directory where the file you want to remove is located. Valid
USBstorage directories are /firmware, /firmwarekey, /support, and /config.
file file
Specifies the name of the file to be removed.
Modes
Privileged EXEC mode
Usage Guidelines
This command is executed on the local device. The USB device must be enabled before this function is
available.
Examples
To remove a configuration file from a USB device attached to the local device:
device# usb remove directory config file startup-config.backup
use-v2-checksum
Enables the v2 checksum computation method for a VRRPv3 IPv4 session.
Syntax
use-v2-checksum
no use-v2-checksum
Command Default
VRRPv3 uses the v3 checksum computation method.
Modes
Virtual-router-group configuration mode
Usage Guidelines
Some non-Extreme devices only use the v2 checksum computation method in VRRPv3. This command
enables v2 checksum computation method in VRRPv3 and provides interoperability with these non-
Extreme devices.
The no form of this command enables the default v3 checksum computation method in VRRPv3
sessions.
Examples
The following example shows the v2 checksum computation method enabled for an VRRPv3 IPv4
session on an Extreme device.
Syntax
user username
no user username
Parameters
username
Specifies the account login name.
Modes
Alias configuration mode
Usage Guidelines
To delete all aliases defined for a specified user, enter the no form of this command.
Examples
The following example accesses user-alias configuration mode for the user jdoe, and defines a user-level
alias named "sv" for the show version command.
device# configure terminal
device(config)# alias-config
device(config-alias-config)# user jdoe
device(config-user-jdoe)# alias sv "show version"
username
Creates and configures a user account.
Syntax
username username password password role role_name [ access-time HHMM to
HHMM ] [ desc description ] [ enable { true | false } ] [ encryption-
level { 0 | 7 | 10 } ] [ expire { never | YYYY-MM-DD } ] [ role
role_name ] [ acct-inactivity-expiry-period 1-180 ] [ acct-
inactivity-warning-period 1-120 ]
no username name
Parameters
username
Specifies the account login name.
access-time HHMM to HHMM
Restricts the hours that the user may be logged in. Valid values range from 0000 through 2400
in 24-hour format. By default, users are granted 24 hour access.
For example, to restrict access to the daily work schedule, use access-time 0800 to
1800 . By default, there is no access-time limitation. To change access time, include both the
new "from" time and "to" time. To restore default access time, specify access-time 0000 to
2400 .
desc description
This is an optional parameter. Specifies a description of the account (optional). The description
can be up to 64 characters long, and can include any printable ASCII character, except for the
following characters: single quotation marks (‘), double quotation marks ("), exclamation point
(!), colon (:), and semi-colon (;). If the description contains spaces, enclose the complete
description text in double quotation marks.
enable
Enables or disables the account.
true
(Default) Enables the account.
false
Disables the account. A user whose account is disabled cannot log in.
expire
Specifies the password expiration setting.
never
(Default) Does not specify a password expiration date.
YYYY-MM-DD
Specifies a password expiration date.
password password
Specifies the account password. To use the exclamation mark (!) character, either precede it with
the escape character (\)—. secret\!password —or enclose the password within double
quotes—"secret!password".
role role_name
Specifies the role assigned to the account.
encryption-level { 0 | 7 | 10 }
Specifies the password encryption level. The values are 0 (clear text), 7 (encrypted), and 10
(SHA512 hash). SHA512 hash is the default. If service password-encryption is enabled, it overrides
a user-level setting.
acct-inactivity-expiry-period 1-180
Specifies the number of days an account is allowed to be inactive before it is disabled.
acct-inactivity-warning-period 1-120
The time duration (in days) after which warning will be generated prior to account getting
disabled.
Modes
Global configuration mode
Usage Guidelines
The username must be of 1-40 characters. It must begin with a letter or underscore and contain only
letters, numbers, underscore (_) and period(.) symbols. Username is case sensitive and cannot be the
same as that of an existing role.
When creating a username, you must specify a password and a role. When modifying a username, it is
sufficient to enter the username username command, followed by the new values.
Note
When configuring the expiry date for a user account, do not configure beyond 19th of January
2038 (2038-01-19). When you configure a date that is beyond this cut off date, the user
account will not expire and the account will not get locked.
If a user's password, access time, or role is changed, any existing login sessions for that user are
terminated.
To specify access-time, use the system time defined for the Extreme operating system. For the
current system time, use the show clock command.
To delete a user account, enter the no username with the name of the account to be deleted.
Examples
The following example configures a user account.
device# configure terminal
device(config)# username testUser password ******** role user desc
The following example modifies an existing user account, restricting the hours that an existing user may
be logged in from 08:00 AM through 06:00 PM.
device# configure terminal
device(config)# username testUser access-time 0800 to 1800
The following example sets the expiry period for the account testUser to 120 days. It also configures
warning period to 90 days. A warning log entry is generated after the account's inactivity (in number of
days) crosses the configured warning period. The user account gets locked after the expiry period.
Ensure that the acct-inactivity-warning-period value is lesser than or equal to the period
specified in the acct-inactivity-expiry-period setting.
device # configure terminal
device(config)# username testUser acct-inactivity-expiry-period 120 acct-inactivity-
warning-period 90
username
Creates and configures a user account.
Syntax
username username password password
Parameters
username
Specifies the account login name.
password password
Specifies the account password. To use the exclamation mark (!) character, either precede it with
the escape character (\)—. secret\!password —or enclose the password within double
quotes—"secret!password".
Modes
GRUB configuration mode
Usage Guidelines
The username must be of 1-40 characters. It must begin with a letter or underscore and contain only
letters, numbers, underscore (_) and period(.) symbols. Username is case sensitive and cannot be the
same as that of an existing role. When creating a username, you must specify a password.
Examples
The following example configures a user account for securing GRUB.
SLX # configure terminal
SLX (config)# grub
SLX (config-grub)# username testUser password ********
SLX (config-grub)#
vc-id
Configures a virtual connection identifier (VC ID) for a bridge domain.
Syntax
vc-id id
no vc-id
Command Default
A virtual connection identifier is not configured.
Parameters
id
Specifies a virtual connection identifier. The range is from 1 through 4294967295.
Modes
Bridge-domain configuration mode.
Usage Guidelines
This feature is supported only on devices based on the DNX chipset family. For a list of such devices, see
" Supported Hardware."
When a VC ID is configured for a VPLS bridge domain, it is used for all configured pseudowires (circuit
emulation services).
Examples
The following example shows how to configure a VC ID (5) for bridge domain 4.
device# configure terminal
device(config)# bridge-domain 4
device(config-bridge-domain-4)# vc-id 5
vc-mode
Configures the virtual connection (VC) mode for a pseudowire (PW) profile.
Syntax
vc-mode { raw | raw-passthrough | tag }
no vc-mode
Command Default
The default VC mode is raw .
Parameters
raw
Specifies using raw mode. At VC label imposition, when a tagged packet is received on a tagged
AC endpoint, the VLAN tag is removed before it is sent out on the wire. Untagged packets that
are received on an untagged AC endpoint are encapsulated as is and sent out on the wire.
raw-passthrough
(DNX devices only) Specifies using raw-passthrough mode, which enables interoperation with
third-party devices. When all endpoints are configured as tagged endpoints, raw passthrough
mode behaves the same way as tagged mode. When all endpoints are configured as untagged
endpoints, raw-passthrough mode behaves the same way as raw mode. Select the raw-
passthrough option, when all endpoints are configured as untagged endpoints (even when
peer devices signal the PW VC mode as raw).
tag
Note
The tag option is not supported on the SLX 9640 platform.
Specifies using tag mode. At VC label imposition, when a tagged packet is received on a tagged
AC endpoint, the packet is encapsulated as is and sent out on the wire. When an untagged
packet is received on an untagged AC endpoint, a dummy tag is added and it is sent out on the
wire.
Modes
Pseudowire-profile configuration mode.
Usage Guidelines
The no form of the command restores the default value.
The raw-passthrough parameter is supported only on devices based on the DNX chipset family. For
a list of such devices, see "Supported Hardware."
Examples
The following example shows how to set the VC mode to raw-passthrough for a PW profile named
test.
device# configure terminal
device(config)# pw-profile test
device(config-pw-profile-test)# vc-mode raw-passthrough
The following example shows how to set the VC mode to tag for a PW profile named test.
device# configure terminal
device(config)# pw-profile test
device(config-pw-profile-test)# vc-mode tag
version (ERP)
Configures an ITU-T G.8032 Version number for Ethernet Ring Protection (ERP).
Syntax
version number
no version
Command Default
The default Version number is 2.
Parameters
number
Specifies an ITU-T G.8032 Version number.
Modes
ERP configuration mode
Usage Guidelines
Use the no form of this command to restore the default.
Examples
The following example configures Version 1.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# version 1
virtual-ip
Configures a virtual IPv4 address or IPv6 address for the virtual router.
Syntax
virtual-ip { ipv4-address | ipv6-address }
no virtual-ip { ipv4-address | ipv6-address }
Parameters
ipv4-address
Virtual IPv4 address of the virtual router.
ipv6-address
Virtual IPv6 address of the virtual router.
Modes
Virtual-router-group configuration mode
Usage Guidelines
The virtual IPv4 address or IPv6 address is the IP address that an end-host sets as its default gateway.
The virtual IP address must belong to the same subnet as the underlying interface. A maximum of 16
virtual IP addresses can be configured for VRRP; only one virtual IP address can be configured for
VRRP-E. The session is enabled as soon as the first virtual IP address is configured.
You can perform this command for VRRP or VRRP-E. VRRPv3 introduced the ability to use an IPv6
address when an IPv6 VRRPv3 group is configured.
This command accepts both fe80/10 link local addresses or fe80/64 addresses as virtual-IP.
Enter the no virtual-ip command with a specified virtual IP address to delete the specified virtual
IP address
Examples
To assign a virtual IP address of 192.53.5.1 to the VRRP virtual group 1:
To assign a virtual IPv6 address of 2001:2019:8192::1 to the VRRP-Ev3 virtual group 19:
virtual-mac
Enables generation of a virtual MAC with 0 IP hash.
Syntax
virtual-mac virtual_mac_address
Parameters
virtual_mac_address
Specifies a virtual MAC address.
Modes
VRRP-Extended group configuration mode
Usage Guidelines
The distributed VXLAN gateway functionality depends on VRRP-E for multi-homing. By default, the
VRRP-E virtual MAC is derived as 02:e0:52:<2-byte-ip-hash>:<1-byte-vrid>. The VXLAN
gateway requires that the virtual MAC be a function of only VRID. The two-byte hash of the virtual IP
should be set to zeros, for example, 02e0.5200.00xx:100.
Examples
To enable the generation of a virtual MAC:
vlan
Specifies a VLAN and enters VLAN configuration mode.
Syntax
vlan vlan_id
no vlan vlan_id
Command Default
No VLAN is configured.
Parameters
vlan_id
Specifies a VLAN ID. Range is from 1 through 4090.
Modes
Global configuration mode
Usage Guidelines
Use the no form of this command to delete a VLAN.
Examples
To configure VLAN 10:
device# configure terminal
device(config)# vlan 10
device(config-vlan-10)#
vlan (EVPN)
Specifies a VLAN, or adds or removes a range of VLANs, for an Ethernet Virtual Private Network (EVPN)
instance.
Syntax
vlan VLAN-ID
no vlan VLAN-ID
vlan { add | remove } {VLAN-range }
Command Default
Disabled
Parameters
VLAN-ID
Specifies a VLAN.
add
Adds a range of VLANs to the default EVPN instance.
remove
Removes a range of VLANs from the default EVPN instance.
VLAN-range
Specifies a hyphen-delimited VLAN range.
Modes
EVPN configuration mode
Usage Guidelines
Each VLAN/BD added to an EVPN configuration is considered as an EVPN instance and is assigned a
unique EVPN instance ID (EVI) internally. The EVI is calculated as shown in the following table.
Important
To interoperate with third-party vendors, the RTs across the interoperating devices must be
the same. If third-party devices do not support automatic RT assigment, or the EVIs are not
calculated as shown in the above table, the VLAN/BD instances must be configured manually
to ensure that RTs across the devices are compatible.
Examples
The following example specifies a VLAN and enter VLAN configuration mode.
device# configure terminal
device(config)# evpn
device(config-evpn-default)# vlan 100
device(evpn-vlan-100)#
The following example adds VLANs 100 through 200 to the default EVPN instance.
device# configure terminal
device(config)# evpn
device(config-evpn-default)# vlan add 100-200
The following example removes VLANs 150 through 180 from the default EVPN instance.
device# configure terminal
device(config)# evpn
device(config-evpn-default)# vlan remove 150-180
vpn-statistics
Enables VPN statistics for a VRF.
Syntax
vpn-statistics
no vpn-statistics
Command Default
No RD is assigned to the VRF.
Parameters
as-num
Composed of the local ASN number followed by a colon ":" and a unique arbitrary number. For
example 3:6.
ip-num:id
Composed of the local IP address followed by a colon ":" and a unique arbitrary number.
Modes
VRF configuration mode
Usage Guidelines
The no form of the command returns to the default setting.
Examples
The following example shows how to enable VPN statistics for a VRF.
device# configure terminal
device(config)# vrf vpn1
device#(config-vrf-vpn1)# rd 1:2
device#(config-vrf-vpn1)# vpn-statistics
vrf
Creates a Virtual Routing and Forwarding (VRF) instance and enters VRF configuration mode.
Syntax
vrf { mgmt-vrf | default-vrf |vrf-name }
Parameters
mgmt-vrf
Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf-name
Specifies the user-defined name of the VRF. The string can be up 64 characters long and should
not contain punctuation or special characters.
Modes
Global configuration mode
Examples
This example creates the VRF instance "myvrf" and enters VRF configuration mode.
device# configure terminal
device(config)# vrf myvrf
device(config-vrf-myvrf)#
Syntax
evpn irb ve VE-ID [cluster-gateway]
no evpn irb
Parameters
VE-ID
Usage Guidelines
The no form of this command returns to the default setting.
Modes
VRF Configuration mode.
Examples
The following example specifies a VE interface 100 in EVPN IRB to the vrf1 instance.
device# configure terminal
device(config)# vrf vrf1
device(config-vrf-vrf1)# evpn irb ve 100
device(config-vrf-vrf1)#
Examples
The following example specifies a VE interface 100 and sets cluster gateway for Ve 100 in EVPN IRB to
the vrf1 instance.
device# configure terminal
device(config)# vrf vrf1
device(config-vrf-vrf1)# evpn irb ve 100 cluster-gateway
Examples
The following example removes Ve 100 cluster gateway association from the vrf1 instance.
device# configure terminal
device(config)# vrf vrf1
device(config-vrf-vrf1)# no evpn irb
vrf forwarding
Configures any port as a VRF port.
Syntax
vrf forwarding{ mgmt-vrf | default-vrf |vrf-name }
no vrf forwarding { mgmt-vrf | default-vrf |vrf-name }
Parameters
mgmt-vrf
Specifies the management VRF.
default-vrf
Specifies the default-vrf.
vrf_name
Specifies the user-defined name of the VRF.
Command Default
By default, the out-of-band (OOB) management port (the eth0 interface) is part of the predefined VRF
named mgmt-vrf.
Modes
Interface subtype configuration mode
Usage Guidelines
Use the no form of the command to disable the specified VRF.
Examples
This example enables enable the management VRF on an Ethernet interface and assigns the interface
to a subnet.
switch(config)# int te 3/0/2
switch(conf-if-te-3/0/2)# vrf forwarding mgmt-vrf
switch(conf-if-te-3/0/2)# ip addr 10.1.1.1/24
vrf-lite-capability
Sets the download bit (DN bit) check off during MP-BGP redistribution into OSPF.
Syntax
vrf-lite-capability
Parameters
There are no parameters for this command.
Modes
Router OSPF mode
Usage Guidelines
no format of this command is not available.
Examples
The following example show the usage of the vrf-lite-capability command.
SLX (config-router-OSPF-vrf-T1)# vrf-lite-capability
SLX (config-router-OSPF-vrf-T1)#
vrrp-acceptmode-disable
Disables accept mode for the backup Virtual Router Redundancy Protocol (VRRP) virtual IP (VIP).
Syntax
vrrp-acceptmode-disable
no vrrp-acceptmode-disable
Command Default
When configured, accept mode is enabled by default.
Modes
Global configuration mode
Usage Guidelines
The no form of the command enables accept mode for the backup VRRP VIP.
When enabled, accept mode allows a backup VRRP master device to respond to ping, traceroute, and
Telnet packets if it becomes the master VRRP device.
Examples
The following example shows how to disable accept mode for the backup VRRP VIP.
vrrp-extended-group
Configures a virtual-router-extended group and enters into the virtual router configuration mode..
Syntax
vrrp-extended-group group-ID
no vrrp-extended-group group-ID
Parameters
group-ID
A user-assigned number from 1 through 255 that you assign to the virtual router group.
Modes
Port-channel interface configuration mode
Usage Guidelines
This configuration is for virtual Ethernet (VE) interfaces only.
If you remove a group, you cannot retrieve it. You would have to redo the configuration procedure.
Examples
The following example shows how to assign the VE interface with a VLAN number of 20 to the virtual
router extended group with the ID of 1. (First you must enable VRRP-E on the switch.)
vrrp-group
Configures a virtual router group (VRRP) and enters into the virtual router configuration mode.
Syntax
vrrp-group group-ID [ version { 2 | 3 } ]
no vrrp-group group-ID [ version { 2 | 3 } ]
Command Default
VRRP version 2 is the default.
Parameters
group-ID
A value from 1 through 255 that you assign to the virtual router group.
version
Specifies in which version of VRRP the IPv4 VRRP group is to be configured.
2 | 3
Version 2 or version 3 of VRRP.
Modes
Interface subtype configuration mode
Usage Guidelines
Enter no vrrp-group group-ID to remove a specific VRRP group. If you remove a group, you
cannot retrieve it. You would have to redo the configuration procedure.
You can specify in which version of VRRP the VRRP group is configured using the version keyword
and either 2 or 3 as the version number. VRRPv3 supports both IPv4 and IPv6 addresses.
Examples
The following example shows how to assign an Ethernet interface to the virtual router group with the ID
of 1. (First you must enable VRRP on the switch.)
The following example shows how to assign an Ethernet interface to the virtual router group with the ID
of 1 for VRRPv3. (First you must enable VRRP on the switch.)
vtep-discovery
Enables automatic VXLAN tunnel endpoint (VTEP) discovery by BGP.
Syntax
vtep-discovery
no vtep-discovery
Command Default
Enabled.
Modes
BGP address-family L2VPN EVPN configuration mode
Usage Guidelines
The no form of this command disables automatic VTEP discovery and creation of VXLAN tunnels.
Examples
The following example disables automatic VTEP discovery by BGP.
The following example re-enables automatic VTEP discovery and creation of VXLAN tunnels by BGP.
write erase
Returns the switch to factory default state.
Syntax
write erase
Modes
Privileged EXEC mode
Usage Guidelines
This command can be used for device recovery or device configuration reset to the factory default state.
Due to its disruptive nature, this command prompts the user about the consequence of losing all
current user configuration and resetting the switch to the factory default state. It waits for the user's
confirmation before proceeding.
Examples
The following command shows executing the write erase command.
device# write erase
This command will erase all the configuration on the Compact Flash.
The specified VCS parameters will be set appropriately while
preserving the licenses and management ip-address.
wtb-time
Specifies the Wait to Block (WTB) time for Ethernet Ring Protection (ERP).
Syntax
wtb-time time
no wtb-time
Command Default
The default WTB value is 5500 milliseconds (ms).
Parameters
time
Time in ms. Range is from 5100 through 7000, in multiples of 100.
Modes
ERP configuration mode
Usage Guidelines
The WTB time ensures that the clearing of a single Forced Switch (FS) command does not trigger the
reblocking of the Ring Protection Link (RPL) when multiple FS situations exist in an Ethernet ring.
Examples
The following example configures a WTB time of 5100 ms.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# wtb-time 5100
wtr-time
Specifies the Wait to Restore (WTR) time for Ethernet Ring Protection (ERP).
Syntax
wtr-time time
no wtr-time
Command Default
The default WTR value is 5 minutes.
Parameters
time
Time in minutes. Range is from 1 through 12.
Modes
ERP configuration mode
Usage Guidelines
The WTR time is configured on the Ring Protection Link (RPL) owner to prevent the frequent operation
of the protection switching, which can result from detection of intermittent signal failures.
Examples
The following example configures a WTR time of one minute.
device# configure terminal
device(config)# erp 1
device(config-erp-1)# wtr-time 1
y1731
Enters the Y.1731 configuration mode.
Syntax
y1731
no y1731
Command Default
This feature is disabled.
Modes
Protocol CFM configuration mode
Usage Guidelines
Use the no form of the command to delete all test and action profiles configured under Y.1731 mode and
the corresponding associations with source and target MEP pair.
Examples
This example shows how to enters the Y1731 configuration mode.
device# configure terminal
device(config)# protocol cfm
device((protocol-cfm)# y1731