Cisco IOS Wide-Area Networking Command Reference 114 debugrgferrors 116 debugrgfevents 117 debugvpdn 118 debugwaas 136 digest 139 dreupload 143 dre-hintsenable 144 dscp(FrameRelayVC-bundle-member)

Cisco IOS Wide-Area Networking Command Reference

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain versionof the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, networktopology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentionaland coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: https://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1721R)

2018 Cisco Systems, Inc. All rights reserved.

https://www.cisco.com/go/trademarkshttps://www.cisco.com/go/trademarks

C O N T E N T S

C H A P T E R 1 Introduction 1

Introduction 1

Frame Relay 1

Frame Relay-ATM Interworking 1

Layer 2 Tunnel Protocol Version 3 (L2TPv3) 2

SMDS 2

X.25 and LAPB 2

C H A P T E R 2 accelerator through cpu-threshold 3

accelerator 5

access-class (X.25) 7

ads-negative-cache 9

aps group 11

aps interchassis group 13

aps l2vpn-state detach 14

arp 16

async-write 18

authentication (L2TP) 20

authentication key-chain (OTV) 23

authentication mode (OTV) 25

authentication send-only (OTV) 27

auto-route-target 28

backup active interface 30

backup delay (L2VPN local switching) 32

backup peer 34

bfe 37

bridge-domain 39

bridge-domain (service instance) 44

Cisco IOS Wide-Area Networking Command Reference iii

bump (Frame Relay VC-bundle-member) 47

cell-packing 50

cipher 53

cipher-list 55

class 57

class (map-list) 60

class-map type waas 62

clear frame-relay-inarp 64

clear l2tun 65

clear l2tun counters 67

clear l2tun counters tunnel l2tp 69

clear otv arp-nd 71

clear otv isis 72

clear otv isis lspfull 73

clear otv isis neighbors 74

clear otv isis rib 75

clear vpdn tunnel pppoe 76

clear waas 77

clear x25 80

clear xot 82

clp-bit 84

cmns enable 86

collect art 87

collect waas 90

connect (Frame Relay) 92

connect (FRF.5) 94

connect (FRF.8) 97

connect (L2VPN local switching) 99

cpu-threshold 102

C H A P T E R 3 de-bit through exp 105

de-bit 107

de-bit map-clp 109

debug l4f 111

debug platform hardware qfp active interface frame-relay multilink 113

Cisco IOS Wide-Area Networking Command Referenceiv

Contents

debug rgf detailed 114

debug rgf errors 116

debug rgf events 117

debug vpdn 118

debug waas 136

digest 139

dre upload 143

dre-hints enable 144

dscp (Frame Relay VC-bundle-member) 146

efci-bit 149

empty-ssl-fragment-insertion 151

encapsulation (Any Transport over MPLS) 153

encapsulation (Frame Relay VC-bundle) 156

encapsulation (L2TP) 158

encapsulation (Layer 2 local switching) 160

encapsulation default 162

encapsulation dot1q (service instance) 164

encapsulation dot1q second-dot1q 166

encapsulation frame-relay 168

encapsulation frame-relay mfr 170

encapsulation l2tpv3 172

encapsulation lapb 174

encapsulation smds 176

encapsulation untagged 178

encapsulation x25 180

ethernet evc 182

exp 184

C H A P T E R 4 fdl through frame-relay lapf n200 187

fdl 189

flow monitor type mace 191

flow record type mace 193

frame-relay accounting adjust 195

frame-relay adaptive-shaping 197

frame-relay address registration auto-address 200

Cisco IOS Wide-Area Networking Command Reference v

Contents

frame-relay address registration ip 202

frame-relay address-reg enable 204

frame-relay bc 206

frame-relay be 208

frame-relay broadcast-queue 210

frame-relay cir 212

frame-relay class 214

frame-relay congestion threshold de 216

frame-relay congestion threshold ecn 218

frame-relay congestion-management 220

frame-relay custom-queue-list 222

frame-relay de-group 224

frame-relay de-list 226

frame-relay end-to-end keepalive error-threshold 228

frame-relay end-to-end keepalive event-window 230

frame-relay end-to-end keepalive mode 232

frame-relay end-to-end keepalive success-events 235

frame-relay end-to-end keepalive timer 237

frame-relay fair-queue 239

frame-relay fecn-adapt 242

frame-relay fragment 244

frame-relay fragment end-to-end 250

frame-relay fragmentation voice-adaptive 252

frame-relay holdq 254

frame-relay idle-timer 256

frame-relay ifmib-counter64 258

frame-relay interface-dlci 260

frame-relay interface-dlci switched 264

frame-relay intf-type 266

frame-relay inverse-arp 268

frame-relay ip tcp compression-connections 270

frame-relay ip tcp header-compression 272

frame-relay lapf frmr 274

frame-relay lapf k 275

frame-relay lapf n200 277

Cisco IOS Wide-Area Networking Command Referencevi

Contents

C H A P T E R 5 frame-relay lapf n201 through fr-atm connect dlci 279

frame-relay lapf n201 281

frame-relay lapf t200 282

frame-relay lapf t203 284

frame-relay lmi-n391dte 285

frame-relay lmi-n392dce 286


frame-relay lmi-n393dce 289


frame-relay lmi-t392dce 292

frame-relay lmi-type 293

frame-relay local-dlci 295

frame-relay map 296

frame-relay map bridge 301

frame-relay map clns 303

frame-relay map ip tcp header-compression 304

frame-relay mincir 306

frame-relay multicast-dlci 308

frame-relay multilink ack 309

frame-relay multilink bandwidth-class 311

frame-relay multilink bid 314

frame-relay multilink hello 316

frame-relay multilink lid 318

frame-relay multilink output-threshold 320

frame-relay multilink retry 322

frame-relay payload-compression 324

frame-relay policing 328

frame-relay priority-dlci-group 330

frame-relay priority-group 332

frame-relay pvc 334

frame-relay qos-autosense 337

frame-relay route 339

frame-relay svc 341

frame-relay switching 343

Cisco IOS Wide-Area Networking Command Reference vii

Contents

frame-relay tc 345

frame-relay traffic-rate 347

frame-relay traffic-shaping 349

frame-relay traps-maximum dlci-status-change 351

frame-relay vc-bundle 353

fr-atm connect dlci 355

C H A P T E R 6 hello through lz entropy-check 357

hello 359

hidden 361

hostname (L2TP) 363

hostname dynamic (OTV) 365

inarp (Frame Relay VC-bundle-member) 366

interface fr-atm 368

interface mfr 370

interface nve 372

interface overlay 373

interface serial multipoint 375

interworking 377

ip dfbit set 380

ip local interface 382

ip pmtu 384

ip protocol 387

ip tos (L2TP) 389

ip ttl 391

keepalive (LMI) 393

l2 router-id 395

l2 vfi autodiscovery 396

l2tp cookie local 398

l2tp cookie remote 400

l2tp hello 402

l2tp id 404

l2tp-class 406

lapb interface-outage 408

lapb k 410

Cisco IOS Wide-Area Networking Command Referenceviii

Contents

lapb modulo 412

lapb n1 414

lapb n2 417

lapb protocol 419

lapb t1 420

lapb t2 422

lapb t4 424

log-adjacency-changes (OTV) 426

logging event frame-relay x25 427

lsp-gen-interval (OTV) 428

lsp-mtu (OTV) 430

lsp-refresh-interval (OTV) 431

lz entropy-check 432

C H A P T E R 7 mace enable through rtcp-regenerate 433

mace enable 436

mace monitor waas 438

map-class frame-relay 440

map-group 442

map-list 444

match fr-de 447

match protocol (L2TPv3) 449

match tcp 451

max-lsp-lifetime (OTV) 453

member (NVE) 454

member vni 455

metadatacache 456

mls l2tpv3 reserve 459

monitor l2tun counters tunnel l2tp 462

neighbor (L2VPN Pseudowire Switching) 464

neighbor (VPLS) 466

nsf (OTV) 468

oam-ac emulation-enable 469

optimize tfo 471

otv active-source 474

Cisco IOS Wide-Area Networking Command Reference ix

Contents

otv adjacency-server unicast-only 476

otv control-group 478

otv data-group 480

otv filter-fhrp 482

otv fragmentation 484

otv isis authentication 486

otv isis csnp-interval 488

otv isis hello-interval 489

otv isis hello-multiplier 490

otv isis hello padding 491

otv isis lsp-interval 492

otv isis metric 493

otv isis overlay 495

otv isis priority 496

otv isis retransmit-interval 497

otv isis retransmit-throttle-interval 498

otv isis site 499

otv join-interface 501

otv mac flood 503

otv site bridge-domain 505

otv site-identifier 506

otv suppress arp-nd 507

otv use-adjacency-server unicast-only 508

otv vpn-name 510

packet drop during-authorization 511

parameter-map type waas 512

passthrough 514

password 515

password (L2TP) 517

peer-cert-verify enable 519

peer-cipherlist 521

peer-ssl-version 523

platform trace runtime process forwarding-manager module mfr 525

policy-map type mace 528

policy-map type waas 530

Cisco IOS Wide-Area Networking Command Referencex

Contents

ppp chap challenge-length 532

ppp packet throttle 534

prc-interval (OTV) 536

precedence (Frame Relay VC-bundle-member) 537

protect (Frame Relay VC-bundle-member) 540

protocol (L2TP) 542

pseudowire 544

pseudowire-class 546

pvc (Frame Relay VC-bundle) 548

read-ahead 550

receive-window 552

retransmit 554

rewrite ingress tag 556

rd (VPLS) 559

route-target (VPLS) 561

rtcp-regenerate 563

C H A P T E R 8 sequence-interval through show platform software otv fp 565

sequence-interval 568

sequencing 569

services host-service peering 571

service pad 573

service pad from-xot 575

service pad to-xot 577

service translation 578

set fr-fecn-becn 580

shape fr-voice-adapt 582

show acircuit checkpoint 584

show ccm group 587

show ccm sessions 589

show connect (FR-ATM) 593

show connection 596

show ethernet service evc 599

show ethernet service instance 601

show ethernet service interface 607

Cisco IOS Wide-Area Networking Command Reference xi

Contents

show flow monitor type mace 610

show flow record type 612

show frame-relay end-to-end keepalive 615

show frame-relay fragment 619

show frame-relay iphc 623

show frame-relay ip tcp header-compression 625

show frame-relay lapf 628

show frame-relay lmi 631

show frame-relay map 634

show frame-relay multilink 640

show frame-relay pvc 647

show frame-relay qos-autosense 663

show frame-relay route 666

show frame-relay svc maplist 668

show frame-relay traffic 671

show frame-relay vc-bundle 672

show l2cac 675

show l2fib 677

show l2tun 680

show l2tun counters tunnel l2tp 682

show l2tun session 689

show l2tun tunnel 697

show l4f 706

show line x121-address 708

show mace metrics 710

show mdns cache 714

show mdns requests 716

show mdns statistics 718

show mlrib common log 719

show mlrib layer2 log 721

show mpls l2transport checkpoint 723

show nve interface 725

show nve peers 726

show nve vni 727

show otv 728

Cisco IOS Wide-Area Networking Command Referencexii

Contents

show otv adjacency 732

show otv adjacency-server replication-list 734

show otv arp-nd-cache 736

show otv data-group 738

show otv isis database 740

show otv isis hostname 743

show otv isis lsp-log 745

show otv isis neighbors 747

show otv isis nsf 749

show otv isis protocol 750

show otv isis rib 752

show otv isis spf-log 754

show otv isis vlan-database 756

show otv log 757

show otv mroute 758

show otv route 760

show otv site 763

show otv statistics 765

show otv summary 767

show otv vlan 769

show parameter-map type waas 771

show policy-map type mace 773

show policy-map type waas 776

show platform hardware qfp feature otv client interface 777

show platform software frame-relay 779

show platform software l2fib fp 781

show platform software l2fib rp 784

show platform software mfr 786

show platform software otv fp 788

C H A P T E R 9 show smds addresses through waas export 791

show smds addresses 794

show smds map 795

show smds traffic 797

show srcp 799

Cisco IOS Wide-Area Networking Command Reference xiii

Contents

show vc-group 801

show vfi 803

show waas accelerator 808

show waas alarms 812

show waas auto-discovery 814

show waas cache http-express metadatacache 817

show waas connection 820

show waas statistics accelerator 828

show waas statistics aoim 835

show waas statistics application 839

show waas statistics auto-discovery 842

show waas statistics class 848

show waas statistics dre 852

show waas statistics errors 856

show waas statistics global 859

show waas statistics lz 862

show waas statistics pass-through 865

show waas statistics peer 868

show waas status 871

show waas token 874

show x25 context 876

show x25 cug 880

show x25 hunt-group 883

show x25 interface 885

show x25 map 887

show x25 profile 891

show x25 remote-red 894

show x25 route 895

show x25 services 897

show x25 vc 899

show x25 xot 908

show x28 hunt-group 910

show x29 access-lists 912

show xconnect 914

shutdown (FR-ATM) 928

Cisco IOS Wide-Area Networking Command Referencexiv

Contents

skeptical interval (OTV) 930

smds address 932

smds dxi 934

smds enable-arp 936

smds glean 937

smds multicast 939

smds multicast arp 941

smds multicast bridge 943

smds multicast ip 945

smds static-map 947

snmp-server enable traps waas 949

source-interface loopback 951

spf-interval (OTV) 952

status admin-down disconnect 953

suppress-server-encoding enable 955

tfo auto-discovery blacklist 957

tfo optimize 959

threshold de 961

threshold ecn 963

timeout setup 965

vc-group 967

vpls-id 969

waas cm-register url 971

waas config 974

waas enable 976

waas-ssl-trustpoint 978

C H A P T E R 1 0 x25 accept-reverse through x25 pvc XOT 981

x25 accept-reverse 983

x25 address 984

x25 address (line) 985

x25 alias 986

x25 bfe-decision 988

x25 bfe-emergency 990

x25 call-record 992

Cisco IOS Wide-Area Networking Command Reference xv

Contents

x25 default 994

x25 facility 996

x25 fail-over 998

x25 hic 1000

x25 hoc 1001

x25 hold-queue 1002

x25 hold-vc-timer 1004

x25 host 1005

x25 htc 1007

x25 hunt-group 1009

x25 idle 1011

x25 ip-precedence 1013

x25 ips 1014

x25 lic 1016

x25 linkrestart 1017

x25 loc 1018

x25 ltc 1019

x25 map 1020

x25 map bridge 1027

x25 map cmns 1032

x25 map compressedtcp 1033

x25 map pad 1035

x25 map rbp local 1037

x25 map rbp remote 1040

x25 modulo 1042

x25 nvc 1044

x25 ops 1046

x25 pad-access 1048

x25 profile 1050

x25 pvc (encapsulation) 1054

x25 pvc (switched PVC to SVC) 1058

x25 pvc (switched) 1061

x25 pvc (XOT) 1063

C H A P T E R 1 1 x25 pvc rbp local through xot access-group 1067

Cisco IOS Wide-Area Networking Command Referencexvi

Contents

x25 pvc rbp local 1069

x25 pvc rbp remote 1072

x25 relay-vc-number 1075

x25 remote-red 1076

x25 retry 1078

x25 roa 1080

x25 rotary 1082

x25 route 1084

x25 routing 1094

x25 security call-conf address out 1096

x25 security clamn 1098

x25 security crcdn 1100

x25 subscribe cug-service 1102

x25 subscribe flow-control 1105

x25 subscribe local-cug 1107

x25 subscribe packetsize 1110

x25 subscribe throughput 1112

x25 subscribe windowsize 1114

x25 suppress-called-address 1116

x25 suppress-calling-address 1117

x25 t10 1118

x25 t11 1119

x25 t12 1120

x25 t13 1121

x25 t20 1122

x25 t21 1123

x25 t22 1124

x25 t23 1125

x25 threshold 1126

x25 use-source-address 1128

x25 version 1129

x25 win 1132

x25 wout 1134

x28 no-padding 1136

x29 access-list 1137

Cisco IOS Wide-Area Networking Command Reference xvii

Contents

x29 profile 1139

x29 inviteclear-time 1141

xconnect 1142

xconnect backup force-switchover 1147

xconnect encapsulation mpls 1149

xconnect logging redundancy 1151

xot access-group 1153

Cisco IOS Wide-Area Networking Command Referencexviii

Contents

Introduction

Introduction, page 1

IntroductionThis manual describes the commands used to configure wide-area networking features with Cisco IOS software.For information about configuration, refer to the Cisco IOS Wide-Area Networking Configuration Guide .

Some commands required for configuring wide-area networking protocols and broadband access are in otherCisco IOS command references. Use the master list of commands or search online to find these commands.

This manual contains commands for configuring the following technologies and features:

Frame Relay

Frame Relay-ATM Interworking

Layer 2 Tunnel Protocol Version 3 (L2TPv3)

SMDS

X.25 and LAPB

This manual is organized alphabetically.

Frame RelayFrame Relay commands are used to configure access to Frame Relay networks.

For Frame Relay configuration information and examples, refer to the Configuring Frame Relay module inthe Cisco IOS Wide-Area Networking Configuration Guide .

Frame Relay-ATM InterworkingThe Frame Relay-ATM interworking commands are used to configure FRF.5 Frame Relay-ATM NetworkInterworking and FRF.8 Frame Relay-ATM Service Interworking.

Cisco IOS Wide-Area Networking Command Reference 1

For Frame Relay-ATM configuration information and examples, refer to the Configuring Frame Relay-ATMInterworking module in the Cisco IOS Wide-Area Networking Configuration Guide .

Layer 2 Tunnel Protocol Version 3 (L2TPv3)L2TPv3 is an Internet Engineering Task Force (IETF) Layer Two Tunneling Protocol Extensions (l2tpext)working group draft that provides several enhancements to L2TP for the capability to tunnel any Layer 2payload over L2TP. L2TPv3 defines the L2TP protocol for tunneling Layer 2 payloads over an IP core networkusing Layer 2 virtual private networks (VPNs).

For L2TPv3 configuration information and examples, refer to the L2TPv3: Layer 2 Tunnel Protocol Version3 new-feature document for Cisco IOS Release 12.3(2)T.

SMDSSMDS commands are used to configure Switched Multimegabit Data Service (SMDS), which is a wide-areanetworking service offered by some regional Bell operating companies (RBOCs) and MCI.

For SMDS configuration information and examples, refer to the Configuring SMDS module in the CiscoIOS Wide-Area Networking Configuration Guide .

X.25 and LAPBX.25 and LAPB commands are used to configure the following:

Link Access Procedure, Balanced (LAPB)

X.25 services (X.25, X.25 over TCP [XOT] and Connection-Mode Network Service [CMNS])

Defense Data Network (DDN) X.25

Blacker Front End (BFE)

For X.25 and LAPB configuration information and examples, refer to the Configuring X.25 and LAPBmodule in the Cisco IOS Wide-Area Networking Configuration Guide .

For information on translating betweenX.25 and another protocol, refer to the Configuring Protocol Translationand Virtual Asynchronous Devices module in the Cisco IOS Terminal Services Configuration Guide .

Cisco IOS Wide-Area Networking Command Reference2

IntroductionLayer 2 Tunnel Protocol Version 3 (L2TPv3)

accelerator through cpu-threshold

accelerator, page 5

access-class (X.25), page 7

ads-negative-cache, page 9

aps group, page 11

aps interchassis group, page 13

aps l2vpn-state detach, page 14

arp, page 16

async-write, page 18

authentication (L2TP), page 20

authentication key-chain (OTV), page 23

authentication mode (OTV), page 25

authentication send-only (OTV), page 27

auto-route-target, page 28

backup active interface, page 30

backup delay (L2VPN local switching), page 32

backup peer, page 34

bfe, page 37

bridge-domain, page 39

bridge-domain (service instance), page 44

bump (Frame Relay VC-bundle-member), page 47

cell-packing, page 50

cipher, page 53

cipher-list, page 55

class, page 57


class (map-list), page 60

class-map type waas, page 62

clear frame-relay-inarp, page 64

clear l2tun, page 65

clear l2tun counters, page 67

clear l2tun counters tunnel l2tp, page 69

clear otv arp-nd, page 71

clear otv isis, page 72

clear otv isis lspfull, page 73

clear otv isis neighbors, page 74

clear otv isis rib, page 75

clear vpdn tunnel pppoe, page 76

clear waas, page 77

clear x25, page 80

clear xot, page 82

clp-bit, page 84

cmns enable, page 86

collect art, page 87

collect waas, page 90

connect (Frame Relay), page 92

connect (FRF.5), page 94

connect (FRF.8), page 97

connect (L2VPN local switching), page 99

cpu-threshold, page 102


accelerator through cpu-threshold

acceleratorTo enter a specific WAAS Express accelerator configuration mode based on the accelerator being configured,use the accelerator command in parameter map configuration mode.

accelerator {cifs-express| http-express| ssl-express}

Syntax Description Enters WAAS CIFS configuration mode and allowsthe configuration of Common Internet File System(CIFS)-Express accelerator parameters.

cifs-express

Enters WAAS HTTP configuration mode and allowsthe configuration of HTTP-Express acceleratorparameters.

http-express

Enters WAAS SSL configuration mode and allowsthe configuration of Secure Sockets Layer(SSL)-Express accelerator parameters.

ssl-express

Command Default WAAS Express accelerator-specific mode is disabled.

Command Modes Parameter map configuration (config-profile)

Command History ModificationRelease

This command was introduced.15.2(3)T

Usage Guidelines To use the accelerator command, enter parameter map configuration mode by using the parameter-maptype waas command.

The accelerator cifs-express command entersWAASCIFS configurationmode, the accelerator http-expresscommand enters WAAS HTTP configuration mode, and the accelerator ssl-express command enters WAASSSL configuration mode.

After entering a WAAS Express accelerator configuration mode, you can enable the respective acceleratorby using the enable command. If an accelerator is not enabled, accelerator-specific parameters do not comeinto effect even if they are configured. Configure the accelerator-specific parameters after entering the respectiveWAAS Express accelerator configuration mode.

Use the no form of the enable command to disable an accelerator. Use the exit command to exit a specificWAAS Express accelerator configuration mode.


accelerator through cpu-thresholdaccelerator

Examples The following example shows how to enter WAAS CIFS configuration mode and enable CIFS-Expressaccelerator:Device(config)# parameter-map type waas waas_globalDevice(config-profile)# accelerator cifs-expressDevice(config-waas-cifs)# enableDevice(config-waas-cifs)# exitThe following example shows how to enter WAAS HTTP configuration mode and enable HTTP-Expressaccelerator:Device(config)# parameter-map type waas waas_globalDevice(config-profile)# accelerator http-expressDevice(config-waas-http)# enableDevice(config-waas-http)# exitThe following example shows how to enter WAAS SSL configuration mode and enable SSL-Expressaccelerator:Device(config)# parameter-map type waas waas_globalDevice(config-profile)# accelerator ssl-expressDevice(config-waas-ssl)# enableDevice(config-waas-ssl)# exit

Related Commands DescriptionCommand

Configures WAAS Express global parameters.parameter-map type waas

Displays information about WAAS Express accelerators.show waas accelerator

Displays statistical information about WAAS Expressaccelerators.

show waas statistics accelerator


accelerator through cpu-thresholdaccelerator

access-class (X.25)To configure an incoming access class on virtual terminals, use the access-class (X.25) command in lineconfiguration mode.

access-class access-list-number in

Syntax Description An integer that identifies the access list. Range isfrom 1 to 199.

access-list-number

Restricts incoming connections between a particularaccess server and the addresses in the access list.

in

Command Default No incoming access class is defined.

Command Modes Line configuration


This command was introduced.10.3

This command was integrated into Cisco IOS Release 12.2(33)SRA.12.2(33)SRA

This command is supported in the Cisco IOS Release 12.2SX train. Supportin a specific 12.2SX release of this train depends on your feature set, platform,and platform hardware.

12.2SX

Usage Guidelines The access list number is used for both incoming TCP access and incoming packet assembler/disassembler(PAD) access.

In the case of TCP access, the access server uses the IP access list defined with the access-list command.

For incoming PAD connections, the same numbered X.29 access list is referenced. If you only want to haveaccess restrictions on one of the protocols, you can create an access list that permits all addresses for the otherprotocol.

Examples The following example configures an incoming access class on virtual terminal line 4. For information on theline vty command, see the publication Configuring the Route Processor for the Catalyst 8540 and UsingFlash Memory Cards.

line vty 4access-class 4 in


accelerator through cpu-thresholdaccess-class (X.25)


Configures the access list mechanism for filteringframes by protocol type or vendor code.

access-list

Limits access to the access server from certain X.25hosts.

x29 access-list


accelerator through cpu-thresholdaccess-class (X.25)

ads-negative-cacheTo configure the alternate data stream negative caching feature of Common Internet File System (CIFS)-Expressaccelerator, use the ads-negative-cache command in WAAS CIFS configuration mode. To disable negativecaching, use the no form of this command.

ads-negative-cache {enable| timeout seconds}

no ads-negative-cache {enable| timeout seconds}

Syntax Description Enables negative caching for alternate data streams.enable

Specifies the timeout value, in seconds, for negativecaching entries. The default value is 3. The range isfrom 1 to 30.

timeout seconds

Command Default Alternate data stream negative caching is enabled, and the default timeout value is 3 seconds.

Command Modes WAAS CIFS configuration (config-waas-cifs)



Usage Guidelines Before you can enable the ads-negative-cache command, use the following commands:

Use the parameter-map type waas command in global configuration mode to enter parameter mapconfiguration mode.

Use the accelerator cifs-express command in parameter map configuration mode to enter WAAS CIFSconfiguration mode.

To enable negative caching, use the ads-negative-cache enable command before configuring the timeout fornegative cache.

Examples The following example shows how to enable alternate data stream negative caching and configure the cachetimeout:Device(config)# parameter-map type waas waas_globalDevice(config-profile)# accelerator cifs-expressDevice(config-waas-cifs)# enableDevice(config-waas-cifs)# ads-negative-cache enableDevice(config-waas-cifs)# ads-negative-cache timeout 15


accelerator through cpu-thresholdads-negative-cache


Enters a specific WAAS Express accelerator configuration modebased on the accelerator being configured.

accelerator



Displays statistical information about WAAS Express accelerators.show waas statistics accelerator


accelerator through cpu-thresholdads-negative-cache

aps groupTo allow more than one protect and working interface and Access Circuit Redundancy (ACR) group to besupported on a router, use the aps group command in interface configuration or controller configurationmode. To remove a group, use the no form of this command.

aps group [acr] group-number

no aps group [acr] group-number

Syntax Description (Optional) Specifies an ACR group.acr

Number of the group. The default is 0.group-number

Command Default No groups exist.

0 is a valid group number.Note

Command Modes Interface configuration (config-if) Controller configuration (config-controller)


This command was introduced.11.1CC



12.2SX

This command was modified. The acr keyword was added.15.1(1)S

Usage Guidelines Use the aps groupcommand to specify more than one working and protect interface on a router--for example,working channel for group 0 and protect channel for group 1 on one router, and working channel for group1 and protect channel for group 0 on another router.

The default group number is 0. The aps group 0 command does not imply that no groups exist.

The aps group command must be configured on both the protect and working interfaces.

Use the acrkeyword to configure an ACR working or protect interface.


accelerator through cpu-thresholdaps group

Examples The following example shows how to configure two working/protect interface pairs. Working interface (3/0/0)is configured in group 10 (the protect interface for this working interface is configured on another router),and protect interface (2/0/1) is configured in group 20.

Router# configure terminalRouter(config)# interface ethernet 0/0Router(config-if)# ip address 10.7.7.6 255.255.255.0Router(config-if)# exitRouter(config)# interface pos 3/0/0Router(config-if)# aps group 10Router(config-if)# aps working 1Router(config-if)# exitRouter(config)# interface pos 2/0/1Router(config-if)# aps group 20Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# endOn the second router, protect interface (4/0/0) is configured in group 10, and working interface (5/0/0) isconfigured in group 20 (the protect interface for this working interface is configured on another router).

Router(config)# interface ethernet 0/0Router(config-if)# ip address 10.7.7.7 255.255.255.0Router(config-if)# exitRouter(config)# interface pos 4/0/0Router(config-if)# aps group 10Router(config-if)# aps protect 1 10.7.7.6Router(config-if)# exitRouter(config)# interface pos 5/0/0Router(config-if)# aps group 20Router(config-if)# aps working 1Router(config-if)# end


Enables a POS interface as a protect interface.aps protect

Configures a POS interface as a working interface.aps working


accelerator through cpu-thresholdaps group

aps interchassis groupTo enable Interchassis Stateful Switchover (IC-SSO) for Multilink PPP (MLPPP) sessions with MultirouterAutomatic Protection Switching (MR-APS), use the aps interchassis group command in controllerconfiguration mode. To disable this functionality, use the no form of this command.

aps interchassis group group-number

no aps interchassis group

Syntax Description Interchassis Redundancy Manager (ICRM) groupnumber.

group-number

Command Default The IC-SSO for MLPPP sessions with MR-APS is disabled.

Command Modes Controller configuration (config-controller)


This command was introduced on Cisco 7600 series routers.15.1(3)S

Usage Guidelines The aps interchassis groupcommandassociates an Automatic Protection Switching (APS) group with anICRM group number to facilitate MR-APS across two routers, while maintaining stateful MLPPP sessionsacross the routers and avoiding session renegotiation in case of APS switchover. This command can only beused on routers that have SONET controllers configured on them.

The ICRM group number is configured on the router using the interchassis group command.

Examples The following example shows how to associate an APS group with an ICRM group number:

Router# configure terminalRouter(config)# controller sonetRouter(config-controller)# aps interchassis group 100


Enables MR-APS.multi-router aps

Configures an interchassis group.interchassis group


accelerator through cpu-thresholdaps interchassis group

aps l2vpn-state detachTo set both the working and protect pseudowires active in an APS configuration, use the aps l2vpn-statedetach command in controller configuration mode. To deactivate, use the no form of this command.

aps l2vpn-statedetach

no aps l2vpn-statedetach

Syntax Description Sets the active and protect pseudowires to stay active.l2vpn-statedetach

Command Default This command is not set by default.

Command Modes Controller configuration (config-controller)


This command was introduced on the Cisco ASR 900 SeriesRouters.

Cisco IOS XE Release 3.18.1SP

Usage Guidelines Use the aps l2vpn-state detach command in the active-active pseudowire redundancy configuration. Thiscommand sets both the working and protect pseudowires in an APS configuration to active.

The aps l2vpn-state detach command takes effect after a controller shutdown command, followed by ano shutown command is performed. Alternately, the command can be configured when the controller isin shut state.

Note

Examples Working Controller Configuration

controller sonet 0/1/0aps group 2aps admaps working 1aps timers 1 3aps l2vpn-state detachaps hspw-icrm-grp 1

Protect Controller Configuration

controller sonet 0/1/0aps group 2


accelerator through cpu-thresholdaps l2vpn-state detach

aps admaps unidirectionalaps protect 1 15.15.15.1aps timers 1 3aps l2vpn-state detachaps hspw-icrm-grp 1


Enables the interface as a protect interface.aps protect

Configures the interface as a working interface.aps working


accelerator through cpu-thresholdaps l2vpn-state detach

arpTo enable Address Resolution Protocol (ARP) entries for static routing over the Switched Multimegabit DataService (SMDS) network, use the following variation of the arp command in global configuration mode. Todisable this capability, use the no form of this command.

arp ip-address smds-address smds

no arp ip-address smds-address smds

Syntax Description IP address of the remote router.ip-address

12-digit SMDS address in the dotted notationnnnn.nnnn.nnnn (48 bits long).

smds-address

Enables ARP for SMDS.smds

Command Default Static ARP entries are not created.

Command Modes Global configuration





12.2SX

Usage Guidelines This command requires a 12-digit (48-bit) dotted-format SMDS address. It does not support 15-digit SMDSaddresses.

Examples The following example creates a static ARP entry that maps the IP address 172.20.173.28 to the SMDS addressC141.5797.1313 on interface serial 0:

interface serial 0arp 172.20.173.28 C141.5797.1313 smds


accelerator through cpu-thresholdarp


Enables dynamic ARP. The multicast address forARP must be set before this command is issued.

smds enable-arp

Configures a static map between an individual SMDSaddress and a higher-level protocol address.

smds static-map


accelerator through cpu-thresholdarp

async-writeTo configure the async write feature of Common Internet File System (CIFS)-Express accelerator, use theasync-write command in WAAS CIFS configuration mode. To disable the async write feature, use the noform of this command.

async-write {enable| quota-threshold mb}

no async-write {enable| quota-threshold mb}

Syntax Description Enables the async write operation.enable

Specifies the quota threshold, in megabytes (MB),for async write to perform the optimization. Thedefault quote threshold is 20. The threshold range isfrom 1 to 1024.

quota-threshold mb

Command Default The async write feature is enabled, and the default quota threshold is 20 MB.

Command Modes WAAS CIFS configuration (config-waas-cifs)



Usage Guidelines Before you can enable the async-write command, use the following commands:

Use the parameter-map type waas command in global configuration mode to enter parameter mapconfiguration mode.

Use the accelerator cifs-express command in parameter map configuration mode to enter WAAS CIFSconfiguration mode.

To enable the async write feature, use the async-write enable command before configuring the quota threshold.

Examples The following example shows how to enable async write and configure the quota threshold:Device(config)# parameter-map type waas waas_globalDevice(config-profile)# accelerator cifs-expressDevice(config-waas-cifs)# enableDevice(config-waas-cifs)# async-write enableDevice(config-waas-cifs)# async-write quota-threshold 1000


accelerator through cpu-thresholdasync-write


Enters a specificWAASExpress accelerator configurationmode basedon the accelerator being configured.

accelerator



Displays statistical information about WAAS Express accelerators.show waas statistics accelerator


accelerator through cpu-thresholdasync-write

authentication (L2TP)To enable Challenge Handshake Authentication Protocol (CHAP) style authentication for Layer 2 TunnelProtocol Version 3 (L2TPv3) tunnels, use the authenticationcommand in L2TP class configuration mode.To disable L2TPv3 CHAP-style authentication, use the no form of this command.

authentication

no authentication

Syntax Description This command has no arguments or keywords.

Command Default L2TPv3 CHAP-style authentication is disabled.

Command Modes L2TP class configuration


This command was introduced.12.0(23)S

This command was integrated into Cisco IOS Release 12.3(2)T.12.3(2)T

This command was integrated into Cisco IOS Release 12.2(25)S.12.2(25)S

Support for this command was integrated into Cisco IOS Release12.2(27)SBC.

12.2(27)SBC

Usage Guidelines Twomethods of control channel authentication are available in Cisco IOS Release 12.0(29)S and later releases.The L2TPv3 Control Message Hashing feature (enabled with the digestcommand) introduces a more robustauthentication method than the older CHAP-style method of authentication enabled with theauthenticationcommand. You may choose to enable both methods of authentication to ensure interoperabilitywith peers that support only one of these methods of authentication, but this configuration will yield controlof which authentication method is used to the peer PE router. Enabling both methods of authentication shouldbe considered an interim solution to solve backward-compatibility issues during software upgrades.

The following table shows a compatibility matrix for the different L2TPv3 authentication methods. PE1 isrunning a Cisco IOS software release that supports the L2TPv3 Control Message Hashing feature, and thedifferent possible authentication configurations for PE1 are shown in the first column. Each remaining columnrepresents PE2 running software with different available authentication options, and the intersections indicatethe different compatible configuration options for PE2. If any PE1/PE2 authentication configuration posesambiguity on which method of authentication will be used, the winning authentication method is indicated inbold. If both the old and new authenticationmethods are enabled on PE1 and PE2, both types of authenticationwill occur.


accelerator through cpu-thresholdauthentication (L2TP)

Table 1: Compatibility Matrix for L2TPv3 Authentication Methods

PE2 Supporting Old andNew Authentication3

PE2 Supporting NewAuthentication2

PE2 Supporting OldAuthentication1

PE1 AuthenticationConfiguration

None

New integrity check

None

New integrity check

NoneNone

Old authentication

Old authentication andnew authentication

Old authentication andnew integrity check

--Old authenticationOld authentication

New authentication


New authentication--New authentication

None

New integrity check

None

New integrity check

NoneNew integrity check

Old authentication

New authentication

Old and newauthentication


New authenticationOld authenticationOld and newauthentication

Old authentication



--Old authenticationOld authentication andnew integrity check

1 Any PE software that supports only the old CHAP-like authentication system.2 Any PE software that supports only the new message digest authentication and integrity checking authentication system, but does not understand the old

CHAP-like authentication system. This type of software may be implemented by other vendors based on the latest L2TPv3 draft.3 Any PE software that supports both the old CHAP-like authentication and the new message digest authentication and integrity checking authentication system,

such as Cisco IOS 12.0(29)S or later releases.

Examples The following example enables CHAP-style authentication for L2TPv3 pseudowires configured using theL2TP class configuration named l2tp class1:

Router(config)# l2tp-class l2tp-class1Router(config-l2tp-class)# authentication




Enables L2TPv3 control channel authentication orintegrity checking.

digest

Creates a template of L2TP control planeconfiguration settings that can be inherited bydifferent pseudowire classes and enters L2TP classconfiguration mode.

l2tp-class

Configures the password used by a PE router forCHAP-style L2TPv3 authentication.

password



authentication key-chain (OTV)To configure an authentication key chain string for an edge device authentication, use the authenticationkey-chain command in OTV IS-IS instance configuration mode. To return to the default setting, use the noform of this command.

authentication key-chain key-chain-name

no authentication key-chain key-chain-name

Syntax Description Authentication key chain. The key-chain-nameargument is case-sensitive and can be an alphanumericstring of up to 16 characters in length.

key-chain-name

Command Default No authentication key chain is configured.

Command Modes OTV IS-IS instance configuration (config-otv-isis)


This command was introduced.Cisco IOS XE Release 3.5S

Usage Guidelines The authentication key-chain command is used to assign a password in the authentication of link-state packet(LSP) protocol data units (PDUs), complete sequence number PDUs (CSNPs), and partial sequence numberPDUs (PSNPs). Only one authentication key chain is applied to an IS-IS interface at one time. If you configurea second authentication key-chain command, the first is overridden. You can specify authentication for anentire instance of IS-IS instead of at the interface level by using the authentication key-chain command.

Examples The following example shows how to configure an authentication key chain string for edge deviceauthentication:Router# configure terminalRouter(config)# otv isis overlay 1Router(config-otv-isis)# authentication key-chain OTVkeyRouter(config-otv-isis)# end


Displays information about OTV.show otv

Displays the IS-IS status and configuration.show otv isis


accelerator through cpu-thresholdauthentication key-chain (OTV)


accelerator through cpu-thresholdauthentication key-chain (OTV)

authentication mode (OTV)To configure an Overlay Transport Virtualization (OTV) authentication type, use the authentication modecommand in OTV IS-IS instance configuration mode. To return to the default setting, use the no form of thiscommand.

authentication mode {md5 | text}

no authentication mode {md5 | text}

Syntax Description Specifies the message digest algorithm (MD5)authentication method.

md5

Specifies the cleartext authentication method.text

Command Default The authentication type is not configured.




Usage Guidelines Use the authentication mode command to configure the authentication type for link-state packet (LSP)protocol data units (PDUs), complete sequence number PDUs (CSNPs), and partial sequence number PDUs(PSNPs) on an interface.

Examples The following example shows how to specify cleartext authentication:Router# configure terminalRouter(config)# otv isis overlay 1Router(config-otv-isis)# authentication mode textRouter(config-otv-isis)# endThe following example shows to specify MD5 authentication:Router# configure terminalRouter(config)# otv isis overlay 1Router(config-otv-isis)# authentication mode md5Router(config-otv-isis)# end




accelerator through cpu-thresholdauthentication mode (OTV)

DescriptionCommand

Displays the IS-IS status andconfiguration.

show otv isis


accelerator through cpu-thresholdauthentication mode (OTV)

authentication send-only (OTV)To disable the authentication check on incoming hello protocol data units (PDUs) on an interface and allowonly sending of authinfo, use the authentication send-only command in OTV IS-IS instance configurationmode. To return to the default setting, use the no form of this command.

authentication send-only

no authentication send-only


Command Default The authentication check is enabled on incoming hello PDUs.




Usage Guidelines The authentication send-only command controls authentication checking on incoming link-state packet(LSP) protocol data units (PDUs), complete sequence number PDUs (CSNPs), and partial sequence numberPDUs (PSNPs).

Examples The following example shows how to disable authentication of hello messages between edge devices:Router# configure terminalRouter(config)# otv isis overlay 1Router(config-otv-isis)# authentication send-onlyRouter(config-otv-isis)# end



Displays the IS-IS status and configuration.show otv isis


accelerator through cpu-thresholdauthentication send-only (OTV)

auto-route-targetTo enable the automatic generation of a route target, use the auto-route-target command in L2 VFIconfiguration or VFI autodiscovery configuration mode. To remove the automatically generated route targets,use the no form of this command.

auto-route-target

no auto-route-target


Command Default A route target is automatically enabled.

Command Modes L2 VFI configuration (config-vfi)

VFI autodiscovery configuration (config-vfi-autodiscovery)


This command was introduced.12.2(33)SRB

This command was modified as part of the Multiprotocol Label Switching(MPLS)-based Layer 2VPN (L2VPN) commandmodifications for cross-OSsupport . This command was made available in VFI autodiscoveryconfiguration mode.

Cisco IOS XE Release 3.7S

Usage Guidelines Use this commandwith the l2 vfi autodiscovery or the autodiscovery (MPLS) command, which automaticallycreates route targets. The no form of this command allows you to remove the automatically generated routetargets. You cannot enter this command if route targets have not been automatically created yet.

Examples The following example shows how to generate route targets for Border Gateway Protocol (BGP) autodiscoveredpseudowire members with Label Discovery Protocol (LDP) signaling:Device(config)# l2vpn vfi context vfi1Device(config-vfi)# vpn id 100Device(config-vfi)# autodiscovery bgp signaling ldpDevice(config-vfi-autodiscovery)# auto-route-target

The following example shows how to remove automatically generated route targets in VFI configurationmode:Device(config-vfi)# no auto-route-target


accelerator through cpu-thresholdauto-route-target


Designates a VFI as having BGP autodiscoveredpseudowire members.

autodiscovery (MPLS)

Enables the VPLS PE router to automatically discoverother PE routers that are part of the same VPLSdomain.

l2 vfi autodiscovery

Specifies a route target for a VPLS VFI.route-target (VPLS)


accelerator through cpu-thresholdauto-route-target

backup active interfaceTo activate primary and backup lines on specific X.25 interfaces, use the backup active interface commandin interface configuration mode. To disable active backup behavior on the X.25 interface, use the no form ofthis command.

backup active interfaceX.25-interface number

no backup active interfaceX.25-interface number

Syntax Description X.25 interface type and number, such as serial 1/3.X.25-interface number

Command Default No default behavior or values

Command Modes Interface configuration



Usage Guidelines The backup active interfacecommand is available only on serial interfaces configured for the X.25 protocol.Use this command to activate dual serial lines (a primary and a backup) to maintain the redundancy andmonitoring capability available from the SCC0 and SCC1 links on a Lucent 5ESS switch in a telco datacommunication network (DCN). The DCN provides telco service providers with communications for networkmanagement applications.

This configuration requires that both serial interfaces be on the same Cisco router. Once the backup activeinterfacecommand is configured, the router will bring up leads on the backup X.25 interface, but will ignoreSet Asynchronous BalancedMode (SABM)messages from the Lucent 5ESS switch until the primary interfacefails.

Examples The following partial example shows how to configure a primary and backup X.25 interface for dual serialline management of the Lucent 5ESS switch in a DCN:

interface serial 1/0description SCC0backup active interface serial 1/1encapsulation x25 dcex25 address 66666666x25 ltc 8x25 ips 256x25 ops 256clockrate 9600!


accelerator through cpu-thresholdbackup active interface

interface serial 1/1description SCC1encapsulation x25 dcex25 address 66666666x25 ltc 8x25 ips 256x25 ops 256clockrate 9600

.

.

.


Monitors the transitions of an interface going downand then back up.

debug backup

Displays interface backup status.show backup


accelerator through cpu-thresholdbackup active interface

backup delay (L2VPN local switching)To specify how long a backup pseudowire virtual circuit (VC) should wait before resuming operation afterthe primary pseudowire VC goes down, use the backup delay command in interface configuration mode orxconnect configuration mode.

backup delay enable-delay {disable-delay| never}

Syntax Description Number of seconds that elapse after the primarypseudowire VC goes down before the Cisco IOSsoftware activates the secondary pseudowire VC. Therange is from 0 to 180. The default is 0.

enable-delay

Number of seconds that elapse after the primarypseudowire VC comes up before the Cisco IOSsoftware deactivates the secondary pseudowire VC.The range is from 0 to 180. The default is 0.

disable-delay

Specifies that the secondary pseudowire VC will notfall back to the primary pseudowire VC if the primarypseudowire VC becomes available again unless thesecondary pseudowire VC fails.

never

Command Default If a failover occurs, the xconnect redundancy algorithmwill immediately switch over or fall back to the backupor primary member in the redundancy group.

Command Modes Interface configuration (config-if) Xconnect configuration (config-if-xconn)



This command was integrated into Cisco IOS Release 12.2(28)SB.12.2(28)SB


This command was integrated into Cisco IOS Release 12.2(33)SRB.12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SXI.12.2(33)SXI

This command was integrated into Cisco IOS XE Release 3.3S.Cisco IOS XE Release 3.3S

This command was integrated into Cisco IOS Release 12.2(33)SCF.12.2(33)SCF


accelerator through cpu-thresholdbackup delay (L2VPN local switching)

Examples The following example shows a Multiprotocol Label Switching (MPLS) xconnect with one redundant peer.Once a switchover to the secondary VC occurs, there will be no fallback to the primary VC unless the secondaryVC fails.

Router(config)# pseudowire-class mplsRouter(config-pw-class)# encapsulation mplsRouter(config)# connect frpw1 serial0/1 50 l2transportRouter(config-if)# xconnect 10.0.0.1 50 pw-class mplsRouter(config-if-xconn)# backup peer 10.0.0.2 50Router(config-if-xconn)# backup delay 0 neverThe following example shows an MPLS xconnect with one redundant peer. The switchover will not beginunless the Layer 2 Tunnel Protocol (L2TP) pseudowire has been down for 3 seconds. After a switchover tothe secondary VC occurs, there will be no fallback to the primary until the primary VC has been reestablishedand is up for 10 seconds.

Router(config)# pseudowire-class mplsRouter(config-pw-class)# encapsulation mplsRouter(config)# connect frpw1 serial0/1 50 l2transportRouter(config-if)# xconnect 10.0.0.1 50 pw-class mplsRouter(config-if-xconn)# backup peer 10.0.0.2 50Router(config-if-xconn)# backup delay 3 10

Examples The following example sets a 2-second delay before resuming operation after the primary pseudowire VCgoes down.

cable l2vpn 0011.0011.0011service instance 1 ethernetencapsulation defaultxconnect 10.2.2.2 22 encapsulation mplsbackup delay 1 2


Configures a redundant peer for a pseudowire VC.backup peer


accelerator through cpu-thresholdbackup delay (L2VPN local switching)

backup peerTo specify a redundant peer for a pseudowire virtual circuit (VC), use the backup peer command in interfaceconfiguration mode or xconnect configuration mode. To remove the redundant peer, use the no form of thiscommand.

backup peer peer-router-ip-addr vcid [pw-class pw-class-name] [priority value]

no backup peer peer-router-ip-addr vcid

Syntax Description IP address of the remote peer.peer-router-ip-addr

32-bit identifier of the VC between the routers at eachend of the layer control channel.

vcid

(Optional) Specifies the pseudowire type. If notspecified, the pseudowire type is inherited from theparent xconnect.

pw-class

(Optional) Name of the pseudowire you created whenyou established the pseudowire class.

pw-class-name

(Optional) Specifies the priority of the backuppseudowire in instances where multiple backuppseudowires exist. The default is 1. The range is from1 to 10.

priority value

Command Default No redundant peer is established.

Command Modes Interface configuration (config-if) Xconnect configuration (config-if-xconn)





This command was integrated into Cisco IOS Release 12.2(33)SRB.12.2(33)SRB

This command was integrated into Cisco IOS Release 12.2(33)SXI.12.2(33)SXI


accelerator through cpu-thresholdbackup peer

ModificationRelease

This command was modified. The ability to add up to three backuppseudowires was added. The priority keyword was added to assignpriority to the backup pseudowires.

Cisco IOS XE Release 2.4

This command was integrated into Cisco IOS Release 12.2(33)SCF.12.2(33)SCF

This command was implemented on the Cisco ASR 901 SeriesAggregation Services Routers.

15.1(2)SNH

Usage Guidelines The combination of the peer-router-ip-addr and vcid arguments must be unique on the router.

In Cisco IOS XE Release 2.3, only one backup pseudowire is supported. In Cisco IOS XE Release 2.4 andlater releases, up to three backup pseudowires are supported.

The Cisco IOS Release 12.2(33)SCF supports up to three backup pseudowires for a primary pseudowire. Thepriority keyword is optional when only one backup pseudowire is configured. This keyword is a requiredchoice when multiple backup pseudowires are configured.

Examples The following example shows how to configure a Multiprotocol Label Switching (MPLS) xconnect with oneredundant peer:Device(config)# pseudowire-class mplsDevice(config-pw-class)# encapsulation mplsRoDeviceuter(config)# interface serial0/0Device(config-if)# xconnect 10.0.0.1 100 pw-class mplsDevice(config-if-xconn)# backup peer 10.0.0.2 200The following example shows how to configure a local-switched connection between ATM and frame relayusing Ethernet interworking. The frame relay circuit is backed up by an MPLS pseudowire.Device(config)# pseudowire-class mplsDevice(config-pw-class)# encapsulation mplsDevice(config-pw-class)# interworking ethernetDevice(config)# connect atm-fr atm1/0 100/100 s2/0 100 interworking ethernetDevice(config-if)# backup peer 10.0.0.2 100 pw-class mplsThe following example shows how to configure a pseudowire with two backup pseudowires:interface ATM4/0.1 point-to-pointpvc 0/100 l2transportencapsulation aal5snapxconnect 10.1.1.1 100 pw-class mplsbackup peer 10.1.1.1 101backup peer 10.10.1.1 110 priority 2backup peer 10.20.1.1 111 priority 9

Examples The following example shows how to set a redundant peer for a pseudowire.cable l2vpn 0011.0011.0011service instance 1 ethernetencapsulation defaultxconnect 10.2.2.2 22 encapsulation mplsbackup peer 10.3.3.3 33




Specifies how long the backup pseudowire VC shouldwait before resuming operation after the primarypseudowire VC goes down.

backup delay



bfe

Effective with Cisco IOS Release 12.2, the bfe command is not available in Cisco IOS Software.Note

To allow the router to participate in emergency mode or to end participation in emergency mode when theinterface is configured for x25 bfe-emergency decision and x25 bfe-decision ask, use the bfe command inuser EXEC mode.

bfe {enter| leave} type number

Syntax Description Causes the Cisco IOS software to send a specialaddress translation packet that includes an enteremergencymode command to the Blacker Front End(BFE) if the emergency mode window is open. If theBFE is already in emergency mode, this commandenables the sending of address translation information.

enter

Disables the sending of address translationinformation from the Cisco IOS software to the BFEwhen the BFE is in emergency mode.

leave

Interface type.type

Interface number.number

Command Default None

Command Modes User EXEC (>)



This command became unsupported.12.2

Examples The following example enables an interface to participate in BFE emergency mode:

bfe enter serial 0


accelerator through cpu-thresholdbfe


Specifies operation of a serial interface as an X.25device.

encapsulation x25

Specifies how a router configured for X.25 BFEemergency decision will participate in emergencymode.

x25 bfe-decision

Configures the circumstances under which the routerparticipates in emergency mode.

x25 bfe-emergency


accelerator through cpu-thresholdbfe

bridge-domainTo enable RFC 1483 ATM bridging or RFC 1490 Frame Relay bridging to map a bridged VLAN to an ATMpermanent virtual circuit (PVC) or Frame Relay data-link connection identifier (DLCI), use thebridge-domaincommand in Frame Relay DLCI configuration, interface configuration, interface ATM VCconfiguration, or PVC range configuration mode. To disable bridging, use the no form of this command.

bridge-domain vlan-id [access| dot1q [ tag ]| dot1q-tunnel] [broadcast] [ignore-bpdu-pid] [pvst-tlvCE-vlan] [increment] [lan-fcs] [split-horizon]

no bridge-domain vlan-id

Syntax Description The number of the VLAN to be used in this bridgingconfiguration. The valid range is from 2 to 4094.

vlan-id

(Optional) Enables bridging access mode, in whichthe bridged connection does not transmit or act uponbridge protocol data unit (BPDU) packets.

access

(Optional) Enables Institute of Electrical andElectronic Engineers (IEEE) 802.1Q tagging topreserve the class of service (CoS) information fromthe Ethernet frames across the ATM network. If thiskeyword is not specified, the ingress side assumes aCoS value of 0 for quality of service (QoS) purposes.

dot1q

(Optional--ATM PVCs only) Specifies the 802.1Qvalue in the range 1 to 4095. You can specify up to32 bridge-domain command entries using dot1q tagfor a single PVC. The highest tag value in a group ofbridge-domain commands must be greater than thefirst tag entered (but no more than 32 greater).

tag

(Optional) Enables IEEE 802.1Q tunneling mode, sothat service providers can use a single VLAN tosupport customers who have multiple VLANs, whilepreserving customer VLAN IDs and segregatingtraffic in different customer VLANs.

dot1q-tunnel

(Optional) Enables bridging broadcast mode on thisPVC. This option is not supported for multipointbridging. Support for this option was removed inCisco IOS Release 12.2(18)SXF2 and Cisco IOSRelease 12.2(33)SRA.

broadcast


accelerator through cpu-thresholdbridge-domain

(Optional for ATM interfaces only) Ignores BPDUprotocol identifiers (PIDs) and treats all BPDUpackets as data packets to allow interoperation withATM customer premises equipment (CPE) devicesthat do not distinguish BPDU packets from datapackets.

ignore-bpdu-pid

(Optional) When the router or switch is transmitting,translates Per-VLAN Spanning Tree Plus (PVST+)BPDUs into IEEE BPDUs.

When the router or switch is receiving, translatesIEEE BPDUs into PVST+ BPDUs.

pvst-tlv

Customer-edge VLAN in the Shared Spanning TreeProtocol (SSTP) tag-length-value (TLV) to be insertedin an IEEE BPDU to a PVST+ BPDU conversion.

CE-vlan

(PVC range configuration mode only) (Optional)Increments the bridge domain number for each PVCin the range.

increment

(Optional) Specifies that the VLAN bridging shouldpreserve the Ethernet LAN frame checksum (FCS)of the Ethernet frames across the ATM network.

This option applies only to routers using aFlexWAN module. Support for this optionwas removed in Cisco IOS Release12.2(18)SXF2 and Cisco IOS Release12.2(33)SRA.

Note

lan-fcs

(Optional) Enables RFC 1483 split horizon mode toglobally prevent bridging between PVCs in the sameVLAN.

split-horizon

Command Default Bridging is disabled.

Command Modes Frame Relay DLCI configuration (config-fr-dlci) Interface configuration (config-if)--Only the dot1q anddot1q-tunnel keywords are supported in interface configuration mode. Interface ATM VC configuration(config-if-atm-vc) PVC range configuration (config-if-atm-range)


This command was introduced as the bridge-vlan command for the 2-portOC-12 ATMWAN Optical Services Modules (OSMs) on Cisco 7600 seriesrouters and Catalyst 6500 series switches.

12.1(13)E



ModificationRelease

This command was integrated into Cisco IOS Release 12.1(12c)E.12.1(12c)E

This command was integrated into Cisco IOS Release 12.1(14)E1. Thedot1q-tunnel keyword was added.

12.1(14)E1

This command was integrated into Cisco IOS Release 12.2(14)SX. Thedot1q-tunnel keyword is not supported in this release.

12.2(14)SX

The split-horizon keyword was added.12.1(19)E

This command was integrated into Cisco IOS Release 12.2(18)S. Thedot1q-tunnel and split-horizon keywords are supported in this release.

12.2(18)S

Support was added for the dot1q-tunnel keyword in Cisco IOS Release12.2(17a)SX.

12.2(17a)SX

This command was renamed from bridge-vlan to bridge-domain. The access,broadcast, ignore-bpdu-pid, and increment keywords were added.

12.2(18)SXE

Support for the lan-fcs and broadcastkeywords was removed. Theignore-bpdu-pidand pvst-tlvkeywords were added.

12.2(18)SXF2


Usage Guidelines RFC 1483 bridging on ATM interfaces supports the point-to-point bridging of Layer 2 packet data units(PDUs) over Ethernet networks. RFC 1490 Frame Relay bridging on Packet over SONET (POS) or serialinterfaces that are configured for Frame Relay encapsulation provides bridging of Frame Relay packets overEthernet networks.

The Cisco 7600 router can transmit BPDUswith a PID of either 0x00-0E or 0x00-07.When the router connectsto a device that is fully compliant with RFC 1483 Appendix B, in which the IEEE BPDUs are sent and receivedby the other device using a PID of 0x00-0E, you must not use the ignore-bpdu-pidkeyword.

If you do not enter the ignore-bpdu-pid keyword, the PVC between the devices operates in compliance withRFC 1483 Appendix B. This is referred to as strict mode . Entering the ignore-bpdu-pid keyword createsloose mode . Both modes are described as follows:

Without the ignore-bpdu-pidkeyword, in strict mode, IEEEBPDUs are sent out using a PID of 0x00-0E,which complies with RFC 1483.

With the ignore-bpdu-pidkeyword, in loose mode, IEEE BPDUs are sent out using a PID of 0x00-07,which is normally reserved for RFC 1483 data.

Cisco-proprietary PVST+ BPDUs are always sent out on data frames using a PID of 0x00-07, regardless ofwhether you enter the ignore-bpdu-pid keyword.

Use the ignore-bpdu-pid keyword when connecting to devices such as ATM digital subscriber line (DSL)modems that send PVST (or 802.1D) BPDUs with a PID of 0x00-07.



The pvst-tlv keyword enables BPDU translation when the router interoperates with devices that understandonly PVST or IEEE Spanning Tree Protocol. Because the Catalyst 6500 series switch ATM modules supportPVST+ only, you must use the pvst-tlv keyword when connecting to a Catalyst 5000 family switch thatunderstands only PVST on its ATMmodules, or when connecting with other Cisco IOS routers that understandIEEE format only.

When the router or switch is transmitting, the pvst-tlv keyword translates PVST+ BPDUs into IEEE BPDUs.

When the router or switch is receiving, the pvst-tlv keyword translates IEEE BPDUs into PVST+ BPDUs.

The bridge-domainand bre-connect commands are mutually exclusive. You cannot use both commandson the same PVC for concurrent RFC 1483 and BRE bridging.

Note

To preserve class of service (CoS) information across the ATM network, use the dot1q option. Thisconfiguration uses IEEE 802.1Q tagging to preserve the VLAN ID and packet headers as they are transportedacross the ATM network.

To enable service providers to use a single VLAN to support customers that have multiple VLANs, whilepreserving customer VLAN IDs and segregating traffic in different customer VLANs, use the dot1q-tunneloption on the service provider router. Then use the dot1q option on the customer routers.

The access, dot1q, and dot1q-tunnel options are mutually exclusive. If you do not specify any of theseoptions, the connection operates in raw bridging access mode, which is similar to access, except that theconnection does act on and transmit BPDU packets.

Note

RFC 1483 bridging is supported on AAL5-MUX and AAL5-LLC Subnetwork Access Protocol (SNAP)encapsulated PVCs. RFC-1483 bridged PVCs must terminate on the ATM interface, and the bridged trafficmust be forwarded over an Ethernet interface, unless the split-horizon option is used, which allows bridgingof traffic across bridged PVCs.

RFC 1483 bridging is not supported for switched virtual circuits (SVCs). It also cannot be configured forPVCs on the main interface.

Note

In interface configuration mode, only the dot1q and dot1q-tunnel keyword options are supported.

Examples The following example shows a PVC being configured for IEEE 802.1Q VLAN bridging using a VLAN IDof 99:

Router# configure terminal

Router(config)# interface ATM6/2

Router(config-if)# pvc 2/101

Router(config-if-atm-vc)# bridge-domain 99 dot1q

Router(config-if-atm-vc)# end



The following example shows how to enable BPDU translation when a Catalyst 6500 series switch is connectedto a device that understands only IEEE BPDUs in an RFC 1483-compliant topology:

Router(config-if-atm-vc)# bridge-domain100 pvst-tlv 150The ignore-bpdu-pid keyword is not used because the device operates in an RFC 1483-compliant topologyfor IEEE BPDUs.

The following example shows how to enable BPDU translation when a Catalyst 5500 ATMmodule is a devicethat understands only PVST BPDUs in a non-RFC1483-compliant topology. When a Catalyst 6500 seriesswitch is connected to a Catalyst 5500 ATM module, you must enter both keywords.

Router(config-if-atm-vc)# bridge-domain100 ignore-bpdu-pid pvst-tlv 150To enable BPDU translation for the Layer 2 Protocol Tunneling ( L2PT) topologies, use the followingcommand:

Router(config-if-atm-vc)# bridge-domain100 dot1q-tunnel ignore-bpdu-pid pvst-tlv 150The following example shows a range of PVCs being configured, with the bridge domain number beingincremented for each PVC in the range:

Router(config)# interface atm 8/0.100

Router(config-if)# range pvc 102/100 102/199Router(config-if-atm-range)# bridge-domain 102 increment


Enables the BRE over a PVC or SVC.bre-connect

Displays the configuration of a particular PVC.show atm pvc



bridge-domain (service instance)To bind a service instance or a MAC tunnel to a bridge domain instance, use the bridge-domain commandin either service instance configurationmode orMAC-in-MAC tunnel configurationmode. To unbind a serviceinstance or MAC tunnel from a bridge domain instance, use theno form of this command.

bridge-domain bridge-id [split-horizon [group group-id]]

no bridge-domain bridge-id [split-horizon [group group-id]]

Syntax on the Cisco ASR 1000 Series Aggregation Device

bridge-domain bridge-id [split-horizon group group-id]

no bridge-domain bridge-id [split-horizon group group-id]

Syntax Description Numerical identifier for the bridge domain instance.The range is an integer from 1 to the platform-specificmaximum (or upper) limit.

The upper limit on the Cisco ASR 1000 deviceis 4096.

bridge-id

(Optional) Configures a port or service instance as amember of a split-horizon group.

This keyword is not supported inMAC-in-MACtunnel configuration mode.

split-horizon

(Optional) Defines the split-horizon group.

This keyword is not supported inMAC-in-MACtunnel configuration mode.

group

(Optional) Identifier for the split-horizon group.Range is 1 to 65533.

This argument is not supported inMAC-in-MAC tunnel configuration mode.

On the Cisco ASR 1000 device, the only valuessupported are 0 and 1.

group-id

Command Default Service instances and MAC tunnels are not bound to a bridge domain instance.

Command Modes Service instance configuration (config-if-svc)


accelerator through cpu-thresholdbridge-domain (service instance)

MAC-in-MAC tunnel configuration (config-tunnel-minm)


This command was introduced.12.2(33)SRB

This command was modified. The split-horizon keyword was added.12.2(33)SRD

This command was modified. Support for this command was added inMAC-in-MAC tunnel configuration mode.

12.2(33)SRE

This command was integrated into Cisco IOS XE Release 3.2S.Cisco IOS XE Release 3.2S

This commandwas implemented on Cisco ASR 901 Series AggregationServices Routers.

15.1(2)SNG

Usage Guidelines Use the bridge-domain(service instance) command to bind either a service instance or a MAC tunnel to abridge domain.

Bridge domains cannot be configured under a service instance under a MAC tunnel without encapsulationalso being configured.

The Cisco ASR 1000 device does not support MAC tunnels.

The bridge-domain(config) command allows a user to configure components on a bridge domain. Forexample, the MAC Address Limiting security component can be configured on a bridge domain usingthis command.

Note

Examples The following example shows how to bind a bridge domain to a service instance:

Device> enableDevice# configure terminalDevice(config)# interface gigabitethernet 2/0/0Device(config-if)# service instance 100 ethernetDevice(config-if-srv)# encapsulation dot1q 100Device(config-if-srv)# bridge-domain 200The following example shows how to bind a MAC tunnel to a service instance:

Device> enableDevice# configure terminalDevice(config)# ethernet mac-tunnel virtual 100Device(config-tunnel-minm)# bridge-domain 200


Enables a user to configure components on a bridgedomain.

bridge-domain (config)



DescriptionCommand

Defines an EVC and enters EVC configurationmode.ethernet evc

Configures an Ethernet service instance on aninterface and enters service instance configurationmode.

ethernet service instance

Defines the matching criteria to be used in order tomap single-tagged 802.1ad frames ingress on aninterface to the appropriate service instance. Thecriteria for this command are single VLAN, range ofVLANS, and lists of these two criteria.

encapsulation dot1ad

Defines the matching criteria to map 802.1Q framesingress on an interface to the appropriate serviceinstance.

encapsulation dot1q

Defines the matching criteria to map Q-in-Q ingressframes on an interface to the appropriate serviceinstance.

encapsulation dot1q second dot1q

Defines the matching criteria to map untagged ingressEthernet frames on an interface to the appropriateservice instance.

encapsulation untagged



bump (Frame Relay VC-bundle-member)To configure the bumping rules for a Frame Relay permanent virtual circuit (PVC) bundle member, use thebump command in Frame Relay VC-bundle-member configuration mode. To specify that the PVC bundlemember does not accept bumped traffic, use the noform of this command.

bump {explicit level| implicit| traffic}

no bump traffic

Syntax Description Specifies the precedence, experimental (EXP), ordifferentiated services code point (DSCP) level towhich traffic on a PVC is bumped when the PVCgoes down. For PVC bundles that use precedence orEXPmapping, valid values for the level argument arefrom 0 to 7. For PVC bundles that use DSCPmapping, valid values are from 0 to 63.

explicit level

Applies the implicit bumping rule, which is thedefault, to a single PVC bundle member. The implicitbumping rule is that bumped traffic is to be carriedby a PVC that has the lower precedence level.

implicit

Specifies that the PVC accept bumped traffic (thedefault condition). The noform stipulates that thePVC does not accept bumped traffic.

traffic

Command Default The PVC accepts bumped traffic, and implicit bumping is used.

Command Modes Frame Relay VC-bundle-member configuration



This command was integrated into Cisco IOS Release 12.2(16)BX.12.2(16)BX

This command was integrated into Cisco IOS Release 12.0(26)S.12.0(26)S


Usage Guidelines The no bump explicit and no bump implicitcommands have no effect.


accelerator through cpu-thresholdbump (Frame Relay VC-bundle-member)

To change the configured bumping rules for a PVC bundle member, override the current configuration witha new bump command entry.

To return to the default condition of implicit bumping, use the bump implicit command.

The effects of different bumping configurations are as follows:

Implicit bumping: If you configure implicit bumping, bumped traffic is sent to the PVC configured tohandle the next-lower service level. When the original PVC that bumped the traffic comes back up, itresumes transmission of the configured service level.When the bump explicit command is not configured,the bump implicitcommandtakes effect by default; however, the bump implicit command does notappear in the show running-config and show startup-config command outputs.

Explicit bumping: If you configure a PVCwith the bump explici t command, you can specify the servicelevel to which traffic is bumped when that PVC goes down, and the traffic is directed to a PVC mappedwith that level. If the PVC that picks up and carries the traffic goes down, the traffic uses the bumpingrules for that PVC. You can specify only one service level for bumping.

Permit bumping: The PVC accepts bumped traffic by default. If the PVC has been previously configuredto reject bumped traffic, you must use the bump traffic command to return the PVC to its defaultcondition.

Reject bumping: To configure a discrete PVC to reject bumped traffic when traffic is directed to it, usethe no bump traffic command.

When no alternative PVC can be found to handle bumped traffic, even when there are no packets of thattraffic type present, the bundle brings itself down. Nomessages are displayed unless the debug frame-relayvc-bundlecommand is enabled or the interface-level command logging event frame-relay vc-bundlestatusis enabled. When default (implicit) bumping is used for all PVCs, the PVC that is handling thelowest service level can be configured to bump explicitly to a PVC handling a higher service level.

Note

The following examples show the alerts that appear during configuration. They describe configuration problemsthat might prevent the bundle from coming up or might cause the bundle to go down unexpectedly:

The following example shows an alert that appears when the bump explicit command is configured:

%DLCI 300 could end up bumping traffic to itselfIt warns that PVC 300 may be configured to bump to a PVC that will in turn bump back to PVC 300, in whichcase the bundle will go down.

The following example shows an alert that appears when a PVC that is explicitly bumped to is configuredwith the no bump traffic command:

%DLCI 306 is configured for bumping traffic to level 7

The following example shows an alert that appears when the service levels handled by a PVC are changed,which leaves other PVCs explicitly configured to bump to levels that are no longer being handled bythat PVC:

%DLCI(s) configured for explicitly bumping traffic to DLCI 300


accelerator through cpu-thresholdbump (Frame Relay VC-bundle-member)

The following example shows an alert that appears when a PVC is configured to explicitly bump to alevel that is not yet handled by any PVCs:

%Presently no member is configured for level 3

The following example shows

Cisco IOS Wide-Area Networking Command Reference 114 debugrgferrors 116 debugrgfevents 117 debugvpdn 118 debugwaas 136 digest 139 dreupload 143 dre-hintsenable 144 dscp(FrameRelayVC-bundle-member)

Documents