Layer 2 Tunnel Protocol Version 3 - Cisco

27.4.2016.
Skiptocontent
Layer2TunnelProtocolVersion3Cisco
Skiptofooter
Layer2TunnelProtocolVersion3
Updated: Mar24,2003
TableOfContents
Contents
PrerequisitesforLayer2TunnelProtocolVersion3
RestrictionsforLayer2TunnelProtocolVersion3
SupportedPortAdaptersfortheCisco7200and7500SeriesRouters
SupportedLineCardsfortheCisco10720InternetRouter
SupportedLineCardsfortheCisco12000SeriesInternetRouters
GeneralL2TPv3Restrictions
Cisco7500SpecificRestrictions
Cisco12000SeriesSpecificRestrictions
FrameRelaySpecificRestrictions
VLANSpecificRestrictions
ATMVPModeSingleCellRelayoverL2TPv3Restrictions
InformationAboutLayer2TunnelProtocolVersion3
MigrationfromUTItoL2TPv3
L2TPv3Operation
BenefitsofUsingL2TPv3
L2TPv3HeaderDescription
SessionID
SessionCookie
PseudowireControlEncapsulation
L2TPv3Features
StaticL2TPv3Sessions
DynamicL2TPv3Sessions
Sequencing
LocalSwitching
DistributedSwitching
IPPacketFragmentation
L2TPv3TypeofServiceMarking
Keepalive
http://www.cisco.com/c/en/us/td/docs/ios/12_0s/feature/guide/l2tpv325.html
1/117
27.4.2016.
MTUHandling
L2TPv3andUTIFeatureComparison
SupportedL2TPv3Payloads
FrameRelay
Ethernet
802.1q(VLAN)
HDLC
PPP
ATM
HowtoConfigureLayer2TunnelProtocolVersion3
ConfiguringL2TPControlChannelParameters
ConfiguringL2TPControlChannelTimingParameters
ConfiguringL2TPControlChannelAuthenticationParameters
ConfiguringL2TPControlChannelMaintenanceParameters
ConfiguringtheL2TPv3Pseudowire
ConfiguringtheXconnectAttachmentCircuit
ManuallyConfiguringL2TPv3SessionParameters
ConfiguringtheXconnectAttachmentCircuitforATMVPModeSingleCellRelay
overL2TPv3
ConfigurationExamplesforLayer2TunnelProtocolVersion3
ConfiguringFrameRelayDLCItoDLCISwitchingExample
ConfiguringFrameRelayTrunkingExample
ConfiguringQoSforL2TPv3ontheCisco7500SeriesExample
ConfiguringMLFRforL2TPv3ontheCisco12000SeriesExample
ConfiguringaStaticL2TPv3SessionforanXconnectEthernetInterfaceExample
ConfiguringaNegotiatedL2TPv3SessionforanXconnectVLANSubinterface
Example
ConfiguringaNegotiatedL2TPv3SessionforLocalHDLCSwitchingExample
ConfiguringaPseudowireClassforFragmentationofIPPacketsExample
ConfiguringtheXconnectAttachmentCircuitforATMVPModeSingleCellRelay
overL2TPv3Example
VerifyinganL2TPv3SessionExample
VerifyinganL2TPControlChannelExample
VerifyingATMVPModeSingleCellRelayoverL2TPv3Configuration
AdditionalReferences
RelatedDocuments
Standards
MIBs
RFCs
TechnicalAssistance
CommandReference
2/117
27.4.2016.
atmpvp
authentication
debugacircuit
debugvpdn
debugxconnect
encapsulationl2tpv3
hello
hidden
hostname
ipdfbitset
iplocalinterface
ippmtu
ipprotocol
iptos
ipttl
l2tpclass
l2tpcookielocal
l2tpcookieremote
l2tphello
l2tpid
password
protocol
pseudowireclass
receivewindow
retransmit
sequencing
showl2tunsession
showl2tuntunnel
snmpserverenabletrapsl2tunsession
timeoutsetup
xconnect
Glossary
TheLayer2TunnelProtocolVersion3featureexpandsonCiscosupportofthe
Layer2TunnelProtocolVersion3(L2TPv3).L2TPv3isanInternetEngineering
TaskForce(IETF)l2tpextworkinggroupdraftthatprovidesseveral
enhancementstoL2TPforthecapabilitytotunnelanyLayer2payloadover
L2TP.Specifically,L2TPv3definestheL2TPprotocolfortunnelingLayer2
payloadsoveranIPcorenetworkusingLayer2virtualprivatenetworks(VPNs).
3/117
27.4.2016.
Benefitsofthisfeatureincludethefollowing:
L2TPv3simplifiesdeploymentofVPNs
L2TPv3doesnotrequireMultiprotocolLabelSwitching(MPLS)
L2TPv3supportsLayer2tunnelingoverIPforanypayload
FeatureSpecificationsforLayer2TunnelingProtocolVersion3
Feature
History
Release
Modification
12.0(21)S
InitialdataplanesupportforL2TPv3wasintroducedonthe
Cisco7200series,Cisco7500series,Cisco10720,and
Cisco12000seriesplatforms.
12.0(23)S
L2TPv3controlplanesupportwasintroducedonthe
Cisco7200series,Cisco7500series,Cisco10720,and
Cisco12000seriesplatforms.
12.0(24)S
L2TPv3wasenhancedtosupportfragmentationofIPpackets
beforeenteringthepseudowireontheCisco7200series,
Cisco7500series,andCisco12000seriesInternetrouters.
12.0(25)S
SupportwasaddedfortheATMVPModeSingleCellRelay
overL2TPv3featureontheCisco7200andCisco7500
seriesrouterswithATMDeluxePAA3interfaces.
12.0(23)S3
12.0(24)S1
12.0(25)S
L2TPv3controlplanesupportwasintroducedonthe
Cisco12000seriesOnePortChannelizedOC12(DS3)line
card.
12.0(27)S
SupportforthefollowingfeatureswasaddedtoCisco12000
seriesTwoPortChannelizedOC3/STM1(DS1/E1)andSix
PortChannelizedT3(T1)linecards:
QoSforFrameRelayattachmentcircuits
BindingL2TPv3sessionstoMultilinkFrameRelay(MLFR)
interfaces
SupportedPlatforms
Cisco7200series,Cisco7500series,Cisco10720Internetrouter,
Cisco12000seriesInternetrouters
4/117
27.4.2016.
NoteSoftwareimagesforCisco12000seriesInternetroutershavebeen
deferredtoCiscoIOSRelease12.0(27)S1.
FindingSupportInformationforPlatformsandCiscoIOSSoftwareImages
UseCiscoFeatureNavigatortofindinformationaboutplatformsupportand
CiscoIOSsoftwareimagesupport.AccessCiscoFeatureNavigatorat
http://www.cisco.com/go/fn.YoumusthaveanaccountonCisco.com.Ifyoudo
nothaveanaccountorhaveforgottenyourusernameorpassword,click
Cancelatthelogindialogboxandfollowtheinstructionsthatappear.
Contents
PrerequisitesforLayer2TunnelProtocolVersion3
RestrictionsforLayer2TunnelProtocolVersion3
InformationAboutLayer2TunnelProtocolVersion3
HowtoConfigureLayer2TunnelProtocolVersion3
ConfigurationExamplesforLayer2TunnelProtocolVersion3
CommandReference
Glossary
PrerequisitesforLayer2TunnelProtocol
Version3
BeforeyouconfigureanXconnectattachmentcircuitforacustomeredge
(CE)device(seethesection"ConfiguringtheXconnectAttachmentCircuit"),
theCEFfeaturemustbeenabled.ToenableCEFonaninterface,usetheip
ceforipcefdistributedcommand.
Youmustconfigurealoopbackinterfaceontherouterfororiginatingand
terminatingtheL2TPv3traffic.TheloopbackinterfacemusthaveanIP
addressthatisreachablefromtheremotePEdeviceattheotherendofan
L2TPv3controlchannel.
ToenableSimpleNetworkManagementProtocol(SNMP)notificationsof
L2TPsessionupanddownevents,enterthesnmpserverenabletraps
l2tunsessioncommandbeforeconfiguringL2TPv3.
RestrictionsforLayer2TunnelProtocol
Version3
Thefollowingsubsectionscontaininformationonrestrictions:
SupportedPortAdaptersfortheCisco7200and7500SeriesRouters
5/117
27.4.2016.
SupportedPortAdaptersfortheCisco7200and7500Series
Routers
L2TPv3issupportedonthefollowingportadaptersintheCisco7200and7500
seriesrouters:
SingleportFastEthernet100BASETX
SingleportFastEthernet100BASEFX
DualportFastEthernet100BASETX
DualportFastEthernet100BASEFX
GigabitEthernetportadapter
12portEthernet/2portFEadapter
4portsynchronousserialportadapter
Enhanced4portsynchronousserialportadapter
8portsynchronousserialportadapter
SingleportHSSIadapter
DualportHSSIadapter
8portmultichannelE1G.703/G.704120ohminterfaces
2portmultichannelE1G.703/G.704120ohminterfaces
8portmultichannelT1withintegratedDSUs
8portmultichannelT1withintegratedCSUsandDSUs
8portmultichannelT1/E1
1portmultichannelT3interface
1portmultichannelE3interface
2portenhancedmultichannelT3portadapter
SingleportT3portadapter
SingleportE3portadapter
2portT3portadapter
2portT3portadapter
SingleportPoS,singlemode,longreach
SingleportPoS,singlemode,intermediatereach
6/117
27.4.2016.
SingleportPoS,multimode
L2TPv3issupportedonthefollowingportadaptersfortheCisco7200series
routersonly:
8portEthernetadapter
4portEthernetadapter
L2TPv3issupportedonthefollowinguplinkandaccesscardsinthe
Cisco10720Internetrouter:
24port10/100MbpsEthernetTXaccesscard
24port100MbpsEthernetFXaccesscardmultimode(MM)
24port100MbpsEthernetFXaccesscardsinglemode(SM)
GigabitEthernetSFPmoduleshortreachlinecard
GigabitEthernetSFPmoduleintermediatereachlinecard
Table1 showsthelinecardsthatsupportL2TPv3fortheCisco12000series
Internetrouters.
Table1
LineCard
Engine
Type
Port
Session
DLCI
Session
VLAN
Session
PoS
Engine
0
Supported
Supported
Unsupported
PoS
Engine
2
Supported
Supported
Unsupported
2portChOC
3/STM1(DS1/E1)
Engine
0
Supported
Supported
Unsupported
6portChT3
Engine
0
Supported
Supported
Unsupported
3portGigabit
Ethernet
Engine
2
Supported
Unsupported
Supported
1portGigabit
Ethernet
Engine
1
Supported
Unsupported
Supported
7/117
27.4.2016.
8portFastEthernet
Engine
1
Supported
Unsupported
Supported
6portE3
Engine
0
Supported
Supported
Unsupported
12portE3
Engine
0
Supported
Supported
Unsupported
6portDS3
Engine
0
Supported
Supported
Unsupported
12portDS3
Engine
0
Supported
Supported
Unsupported
1PortChannelized
OC12(DS3)line
card
Engine
0
Supported
Supported
Unsupported
CiscoExpressForwarding(CEF)mustbeenabledfortheL2TPv3featureto
function.TheXconnectconfigurationmodeisblockeduntilCEFisenabled.
Ondistributedplatforms,suchastheCisco7500andCisco12000series,if
CEFisdisabledwhileasessionisestablished,thesessionistorndownand
remainsdownuntilCEFisreenabled.ToenableCEF,usetheipceforip
cefdistributedcommand.
TheIPlocalinterfacemustbealoopbackinterface.Configuringanyother
interfacewiththeiplocalinterfacecommandwillresultinanonoperational
setting.
ThenumberofsessionsonaPPP,highleveldatalinkcontrol(HDLC),
Ethernet,or802.1qVLANportislimitedbythenumberofinterface
descriptorblocks(IDBs)thattheroutercansupport.ForPPP,HDLC,
Ethernet,and802.1qVLANcircuittypes,anIDBisrequiredforeachcircuit.
WhenL2TPv3isusedtotunnelFrameRelayDLCIs,anIDBisnotrequired
foreachcircuit.Asaresult,thememoryrequirementsaremuchlower.The
scalabilitytargetsfortheEngineeringFieldTest(EFT)programare4000
L2TPsessions,whichexceedstheIDBlimitationsforanyCiscoplatformin
Release12.0(24)S.
FrameRelaysupportincludesonly10bitDLCIaddressing.TheL2TPv3
featuredoesnotsupportFrameRelayextendedaddressing.
8/117
27.4.2016.
Theinterfacekeepalivefeatureisautomaticallydisabledontheinterfaceto
whichXconnectisapplied,exceptforFrameRelayencapsulation,whichis
requiredforLocalManagementInterface(LMI).
StaticL2TPv3sessionsdonotsupportFrameRelayLMIinterworking.
StaticL2TPv3sessionsdonotinteroperatewithUniversalTunnelInterface
(UTI)usingkeepalives.
Theippmtucommandusedtoconfigurethepseudowireclass(seethe
section"ConfiguringtheL2TPv3Pseudowire")isnotsupportedforstatic
L2TPv3sessions.Asaresult,IPpacketfragmentationandIntermediate
SystemtoIntermediateSystem(ISIS)fragmentationthroughastatic
L2TPv3sessionisnotsupported.
IPpacketfragmentationisnotsupportedwhentheCErouterisrunning
specialLayer2(L2)optionssuchasL2sequencing,compression,or
encryption.ExamplesoftheseoptionsareFrameRelaycompressionand
fragmentationorPPPcompression.Inthesescenarios,theIPpayloadisnot
inaformatthatiscompatiblewithIPfragmentation.
AlthoughL2TPv3sequencingissupportedonCisco7500seriesrouters,all
L2TPpacketsthatrequiresequencenumberprocessingwillbesenttothe
RouteSwitchProcessor(RSP)module.
Variablecookiesize,IPpacketfragmentation,andL2TPv3sequencingare
notsupportedinRelease12.0(24)S.
ThereassemblyoffragmentedL2TPv3packetsisperformedontheCisco
10720InternetRouterbytheRouteProcessor(RP)attheprocesslevel,not
intheParalleleXpressForwarding(PXF)forwardingpath.
OntheCisco10720Internetrouter,theutitranslationcommandisnot
migratedforXconnectserviceandisnotsupportedinCiscoIOS
Release12.0(24)S.AlthoughtheuticommandissupportedinL2TPv3
releases,thetranslationoptionislostinthemigration.
OntheCisco10720InternetRouter,althoughitisnotrequired,itishighly
recommendedthatyouconfigurealoopbackinterfaceastheIPlocal
interface.
YoucanalsoconfigureaLANinterfaceastheIPlocalinterfacesothatthe
tunnelcontrolsessionistiedtoanoperationalLAN(GigabitEthernetorFast
Ethernet)interfaceorsubinterface.However,inthiscase,thetunnelcontrol
planeisusedonlyaslongastheGigabitEthernetorFastEthernetinterface
isoperational.
ISISprotocolpacketfragmentationissupportedonlyfordynamicL2TPv3
sessions.
TheIPlocalinterfacemustbealocalloopbackinterface.Configuringany
otherinterfaceastheIPlocalinterfacewillresultinnonoperationalsessions.
TheIPlocalinterfacemustbededicatedfortheuseofL2TPv3sessions.
9/117
27.4.2016.
Thisinterfacemustnotbesharedbyanyotherroutingortunneling
protocols.
Hairpinningisnotsupportedforlocaltolocalswitching.Thestartandendof
anL2TPv3sessionmustterminateondifferentrouterslinkedviaanIPor
MPLSbackbone.
Theaggregateperformanceisboundbytheservercardlimitof2.5million
packetspersecond(pps).
Thededicatedtunnelservercard1portOC48c/STM16cPOS/SDHis
requiredforL2TPv3tofunction.TheservercardwillnotrunanyEngine2
features.
TheipunnumberedcommandandIPaddressshouldbeconfiguredunder
thePoSinterfaceoftheservercardpriortohardwaremoduleconfiguration.
ThisconfigurationmakestheservercardIPawareforbackbonesrequiring
anAddressResolutionProtocol(ARP)tobegeneratedbythelinecard.The
backbonetypesthatrequirethisconfigurationareEthernetandspatialreuse
protocol(SRP).Thisconfigurationisalsoarequirementforsession
keepalives.Theinterfaceportoftheservercardwillautomaticallybesetto
loopbackinternalandnokeepalivesoncethehwmoduleslotslotnumber
modeservercommandisconfigured.
Duetoaframerproblem,theservercardinterfacesaccountingin(packets
out)willnotbeaccurate.
OnlyfeaturesfoundintheVanillauCodebundlearesupportedonEngine2
linecardsthatareassociatedwithanL2TPv3sessionandonadifferent
interface,DLCI,orVLANofthesamelinecard.
ConfiguringEngine2featuresnotfoundintheVanillauCodebundleonany
portoftheEngine2linecardthathasaL2TPv3sessionboundtooneor
moreinterfaceswillcausetheVanillauCodetobeswappedout.This
configurationwillcausealltrafficthroughtheL2TPv3sessiontostoponthat
Engine2linecard.Inthiscase,rebindingoftheL2TPv3sessionwillbe
requiredwhentheVanillauCodebundleisrestored.
Configuringoutputaccesscontrollists(ACLs)onanylinecardwillswapout
therunningEngine2linecardVanillauCodebundleinfavoroftheACL
uCodebundle.ThisconfigurationwillcausealltrafficthroughtheL2TPv3
sessiontostoponthoseEngine2linecards.IfoutputACLsareessentialon
therouter,itisadvisabletooriginateallL2TPv3sessionsonEngine0line
cards.OutputACLswillnotswapouttheservercarduCodebundledueto
thehigherpriority.
Engine2linecardsdonotsupportFrameRelayswitchingandFrameRelay
L2TPv3DLCIsessiononthesamelinecard.
OnEngine2linecards,theinputFrameRelaypermanentvirtualcircuit
(PVC)counterswillnotbeupdated.
The8portFastEthernetlinecardshouldnotbeconnectedtoahubor
switchwhenL2TPv3isconfiguredontheingresssideofoneormoreofits
ports,orduplicatepacketswillbegenerated,causingtheroutertobe
floodedwithpackets.ThisrestrictionresultsfromtherequirementthatCAM
filteringisdisabledwhenL2TPv3isused.
Onthe3portGigabyteEthernetlinecard,performancedegradationcan
occurifIPpacketscomingfromaportaresenttotheslowpathfor
forwarding.Thisperformancedegradationwilloccurifboththefollowing
10/117
27.4.2016.
conditionsaremet:
Theporthasatleastone802.1qsubinterfacethatisinanL2TPv3
session.
TheIPpacketcomesfromtheportinterfaceitself(not802.1q
encapsulated)orfroman802.1qsubinterfacethatisundertheport
interfacebuthasnoL2TPv3sessionboundtoit.
Onthe1portOC48c/STM16cPOS/SDHlinecard,themaximum
performanceof2.5millionppsisachievedonlyifyouusetransmitbuffer
management(TBM)ASICID60F1.OtherASICIDversionscancausethe
performancetobereducedbyhalf.TodeterminetheASICvalueoftheline
card,usetheexecuteonslotslotnumbershowcontrollerfrfabbmareg
|includeasiccommand,whereslotnumberistheslotnumberofthe
servercard.
Theopticsofthe1portOC48c/STM16cPOS/SDHlinecardshouldbe
coveredduetopossibleinterferenceornoisecausingcyclicredundancy
check(CRC)errorsonthelinecard.Theseerrorsarecausedbyaframer
probleminthelinecard.
FrameRelayperDLCIforwardingandporttoporttrunkingaremutually
exclusive.L2TPv3doesnotsupporttheuseofbothonthesameinterfaceat
thesametime.
ThexconnectcommandisnotsupportedonFrameRelayinterfaces
directly.ForFrameRelay,theXconnectisappliedundertheconnect
commandspecifyingtheDLCItobeused.
Changingtheencapsulationtypeonanyinterfaceremovesanyexisting
xconnectcommandappliedtothatinterface.
TheDEbitvaluedoesnotinfluencethetypeofservice(ToS)bits.
TouseDCEoraNetworktoNetworkInterface(NNI)onaFrameRelayport,
youmustconfiguretheframerelayswitchingcommand.
QualityofService(QoS)policiesconfiguredwiththeModularQualityof
Servicecommandlineinterface(MQC)aresupportedbyL2TPv3onFrame
Relayinterfacesasfollows:
OntheCisco7500serieswithdistributedCEF(dCEF),inaQoSpolicy
appliedtoaFrameRelayinterfaceconfiguredforL2TPv3,onlytheMQC
commandsmatchfrdlciinclassmapconfigurationmodeand
bandwidthinpolicymapconfigurationmodearesupported.(See
ConfiguringQoSforL2TPv3ontheCisco7500SeriesExample.)
OntheCisco12000series,aQoSpolicyissupportedbyL2TPv3onlyon
theFrameRelayinterfacesofaTwoPortChannelizedOC3/STM1
(DS1/E1)andSixPortChannelizedT3(T1)linecard.(SeeConfiguring
QoSforL2TPv3ontheCisco12000SeriesExample.)
Thepolicecommandissupportedasfollows:
Onlythetransmitkeywordissupportedwiththeconformactionaction
parameter.
11/117
27.4.2016.
Onlythesetfrdetransmitvalueissupportedwiththeexceedaction
actionparameter.
Onlythedropvalueissupportedwiththeviolateactionaction
parameter.
Backwardexplicitcongestionnotification(BECN)andforwardexplicit
congestionnotification(FECN)configurationarenotsupported.
TheToSbytemustbeconfiguredinIPheadersoftunneledFrameRelay
packetswhenyouconfiguretheL2TPv3pseudowire(seeConfiguringthe
L2TPv3Pseudowire).
AllstandardrestrictionsforconfiguringQoSonCisco12000Seriesline
cardsapplytoconfiguringQoSforL2TPv3onCisco12000Series2port
ChOC3/STM1(DS1/E1)or6portChT3linecards.
OntheingresssideofaCisco12000SeriesFrameRelayinterface:
Weightedrandomearlydetection(WRED)andmodifieddeficitround
robin(MDRR)configurationsarenotsupported.
OntheegresssideofaCisco12000SeriesFrameRelayinterface:
ModifiedDeficitRoundRobin(MDRR)istheonlyqueuingstrategy
supported.
WeightedRandomEarlyDetection(WRED)istheonlypacketdrop
strategysupported.
MDRRissupportedonlyinthefollowingmodes:
Withbothalowlatency(priority)queueandclassdefaultqueue
configured.(Thelowlatencyqueueisonlysupportedincombinationwith
theclassdefaultqueue,andcannotbeconfiguredwithnormaldistributed
roundrobin(DRR)queues.)
Withoutalowlatencyqueueconfigured.(Inthiscase,only6queuesare
supported,includingtheclassdefaultqueue.)
EgressqueuingisdeterminedaccordingtotheIPPrecedencevalue(s)
configuredforclassesofL2TPv3FrameRelaytrafficusingthematchip
precedencecommand,insteadofonaperDLCIbasis.
TheconfigurationofanL2TPv3sessiononaMultilinkFrameRelay(MLFR)
bundleinterfaceissupportedonlyonCisco12000SeriesTwoPort
ChannelizedOC3/STM1(DS1/E1)andSixPortChannelizedT3(T1)line
cards.(Formoreinformation,seeBindingL2TPv3SessionstoMultilink
FrameRelayInterfaces.)
FrameRelaypolicingisnondistributedontheCisco7500series.By
configuringFrameRelaypolicing,youcausetrafficontheaffectedPVCsto
besenttotheRSPforprocessing.FrameRelaypolicingisnotsupportedon
theCisco12000seriesInternetrouter.
FrameRelaysupportisfor10bitDLCIaddresses.FrameRelayExtended
Addressingisnotsupported.
MultipointDLCIisnotsupported.
12/117
27.4.2016.
Thekeepalivewillautomaticallybedisabledoninterfacesthathavean
Xconnectappliedtothem,exceptforFrameRelayencapsulation,whichisa
requirementforLMI.
StaticL2TPv3sessionswillnotsupportFrameRelayLMIinterworking.
Aprovideredge(PE)routerisresponsibleonlyforstaticVLANmembership
entriesthataremanuallyconfiguredontherouter.DynamicVLAN
membershipentries,entryaging,andmembershipdiscoveryarenot
supported.
ImplicittaggingforVLANmembershipoperatingontheotherlayers(suchas
atLayer2,membershipbyMACaddressorprotocoltype,atLayer3,or
membershipbyIPsubnet)isnotsupported.
Pointtomultipointandmultipointtopointconfigurationsarenotsupported.
Thereisa1:1relationshipbetweenanattachmentcircuitandanL2TPv3
session.
TheATMVPModeSingleCellRelayoverL2TPv3featureissupportedonly
ontheCisco7200andCisco7500seriesrouterswithATMDeluxePAA3
interfaces.
OncetheATMVPModeSingleCellRelayfeatureisconfiguredforavirtual
pathconnection(VPC),nootherpermanentvirtualcircuits(PVCs)willbe
allowedforthesamevirtualpathidentifier(VPI).
InformationAboutLayer2TunnelProtocol
Version3
ToconfiguretheLayer2TunnelProtocolVersion3feature,youmust
understandthefollowingconcepts:
L2TPv3Operation
L2TPv3Features
UTIisaCiscoproprietaryprotocolthatoffersasimplehighspeedtransparent
Layer2toLayer2serviceoveranIPbackbone.TheUTIprotocollacksthe
signalingcapabilityandstandardssupportnecessaryforlargescalecommercial
service.Tobegintoanswertheneedforastandardwaytoprovidelargescale
VPNconnectivityoveranIPcorenetwork,limitedmigrationfromUTItoL2TPv3
wasintroducedinCiscoIOSRelease12.0(21)S.TheL2TPv3featurein
13/117
27.4.2016.
CiscoIOSRelease12.0(23)SintroducedamorerobustversionofL2TPv3to
replaceUTI.
Asdescribedinthesection"L2TPv3HeaderDescription,"theUTIdataheader
isidenticaltotheL2TPv3headerbutwithnosequencenumbersandan8byte
cookie.BymanuallyconfiguringanL2TPv3sessionusingan8bytecookie(see
thesection"ManuallyConfiguringL2TPv3SessionParameters")andbysetting
theIPprotocolnumberofoutgoingdatapacketsto120(asdescribedinthe
section"ConfiguringtheL2TPv3Pseudowire"),youcanensurethataPE
runningL2TPv3mayinteroperatewithapeerPErunningUTI.However,
becauseUTIdoesnotdefineasignalingplane,dynamicallyestablishedL2TPv3
sessionscannotinteroperatewithUTI.
WhenacustomerupgradesfromapreL2TPv3CiscoIOSreleasetoapost
L2TPv3release,aninternalUTItoXconnectcommandlineinterface(CLI)
migrationutilitywillautomaticallyconverttheUTIcommandstoXconnectand
pseudowireclassconfigurationcommandswithouttheneedforanyuser
intervention.AftertheCLImigration,theUTIcommandsthatwerereplacedwill
notbeavailable.TheoldstyleUTICLIwillbehiddenfromtheuser.
NoteTheUTIkeepalivefeaturewillnotbemigrated.TheUTIkeepalivefeature
willnolongerbesupportedinpostL2TPv3releases.Youshould
converttousingdynamicL2TPv3sessionsinordertopreservethe
functionalityprovidedbytheUTIkeepalive.
L2TPv3Operation
L2TPv3providessimilarandenhancedservicestoreplacethecurrentUTI
implementation,includingthefollowingfeatures:
XconnectforLayer2tunnelingviaapseudowireoveranIPnetwork
Layer2VPNsforPEtoPErouterserviceviaXconnectthatsupport
Ethernet,802.1q(VLAN),FrameRelay,HDLCandPPPLayer2circuits,
includingbothstatic(UTIlike)anddynamic(usingthenewL2TPv3
signaling)forwardedsessions
TheinitialCiscoIOSRelease12.0(23)Sfeaturessupportedonlythefollowing
features:
Layer2tunneling(asusedinanL2TPaccessconcentrator,orLAC)toan
attachmentcircuit,notLayer3tunneling
L2TPv3dataencapsulationdirectlyoverIP(IPprotocolnumber115),not
usingUserDatagramProtocol(UDP)
Pointtopointsessions,notpointtomultipointormultipointtopointsessions
SessionsbetweenthesameLayer2protocolsforexample,Ethernetto
Ethernet,VLANtoVLAN,butnotVLANtoEthernetorFrameRelay
Theattachmentcircuitisthephysicalinterfaceorsubinterfaceattachedtothe
14/117
27.4.2016.
pseudowire.
Figure1showsanexampleofhowtheL2TPv3featureisusedforsettingup
VPNsusingLayer2tunnelingoveranIPnetwork.Alltrafficbetweentwo
customernetworksitesisencapsulatedinIPpacketscarryingL2TPdata
messagesandsentacrossanIPnetwork.ThebackboneroutersoftheIP
networktreatthetrafficasanyotherIPtrafficandneednotknowanythingabout
thecustomernetworks.
Figure1L2TPv3Operation
InFigure1,thePEroutersR1andR2provideL2TPv3services.TheR1andR2
routerscommunicatewitheachotherusingapseudowireovertheIPbackbone
networkthroughapathcomprisingtheinterfacesint1andint2,theIPnetwork,
andinterfacesint3andint4.
Inthisexample,theCEroutersR3andR4communicatethroughapairof
XconnectEthernetor802.1qVLANinterfacesusinganL2TPv3session.The
L2TPv3sessiontu1isapseudowireconfiguredbetweeninterfaceint1onR1
andinterfaceint4onR2.Anypacketarrivingoninterfaceint1onR1is
encapsulatedandsentviathepseudowirecontrolchannel(tu1)toR2.R2
decapsulatesthepacketandsendsitoninterfaceint4toR4.WhenR4needsto
sendapackettoR3,thepacketfollowsthesamepathinreverse.
PleasenotethefollowingfeaturesregardingL2TPv3operation:
Allpacketsreceivedoninterfaceint1willbeforwardedtoR4.R3andR4
cannotdetecttheinterveningnetwork.
ForEthernetinterfaces,anypacketreceivedfromLAN1byR1onEthernet
interfacee1willbeencapsulateddirectlyinIPandsentviathepseudowire
sessiontu2toR2interfacee2,whereitwillbesentonLAN2.
]AVLANonanEthernetinterfacecanbemappedtoanL2TPv3session.
ForCisco12000seriesInternetrouters,theotherLANportsonthe8port
FastEthernetlinecardthatarenotbeingusedforL2TPv3musthavea
routerconnectedtothem:Whencontentaddressablememory(CAM)
15/117
27.4.2016.
assistedMACfilteringisturnedOFFtoallowL2TPv3towork,itisturned
OFFonallports.
L2TPv3SimplifiesDeploymentofVPNs
L2TPv3isanindustrystandardLayer2tunnelingprotocolthatensures
interoperabilityamongvendors,increasingcustomerflexibilityandservice
availability.
L2TPv3DoesNotRequireMPLS
WithL2TPv3serviceprovidersneednotdeployMPLSinthecoreIPbackbone
tosetupVPNsusingL2TPv3overtheIPbackbone,resultinginoperational
savingsandincreasedrevenue.
L2TPv3SupportsLayer2TunnelingoverIPforAnyPayload
L2TPv3providesenhancementstoL2TPtosupportLayer2tunnelingofany
payloadoveranIPcorenetwork.L2TPv3definesthebaseL2TPprotocolas
beingseparatefromtheLayer2payloadthatistunneled.
ThemigrationfromUTItoL2TPv3alsorequiresthestandardizationoftheUTI
header.Asaresult,theL2TPv3headerhasthenewformatshowninFigure2.
EachL2TPv3packetcontainsanL2TPv3headerthatincludesauniquesession
IDrepresentingonesessionandavariablecookielength.TheL2TPv3session
IDandtheTunnelCookiefieldlengthareassignedviatheCLI.Seethesection
"HowtoConfigureLayer2TunnelProtocolVersion3"formoreinformationon
theCLIcommandsforL2TPv3.
Figure2L2TPv3HeaderFormat
IPDeliveryHeader(20bytes)
ProtocolID:115
L2TPV3Headerconsistingof:
SessionID(4bytes)
Cookie(0,4,or8bytes)
(4bytesbydefault)
Layer2Payload
16/117
27.4.2016.
SessionID
TheL2TPv3sessionIDissimilartotheUTIsessionID,andidentifiesthe
sessioncontextonthedecapsulatingsystem.Fordynamicsessions,thevalue
ofthesessionIDisselectedtooptimizethecontextidentificationefficiencyof
thedecapsulatingsystem.Adecapsulationimplementationmaythereforeelect
tosupportasmallersessionIDbitfield.InthisL2TPv3implementation,an
uppervaluefortheL2TPv3sessionIDwassetat023.TheL2TPv3sessionID
value0isreservedforusebytheprotocol.Forstaticsessions,thesessionIDis
manuallyconfigured.
NoteThelocalsessionIDmustbeuniqueonthedecapsulatingsystemandis
restrictedtotheleastsignificanttenbits.
SessionCookie
TheL2TPv3headercontainsacontrolchannelcookiefieldthatissimilartothe
UTIcontrolchannelkeyfield.Thecontrolchannelcookiefield,however,hasa
variablelengthof0,4,or8bytesaccordingtothecookielengthsupportedbya
givenplatformforpacketdecapsulation.Thecontrolchannelcookielengthcan
bemanuallyconfiguredforstaticsessions,ordynamicallydeterminedfor
dynamicsessions.
Thevariablecookielengthdoesnotpresentaproblemwhenthesameplatform
isatbothendsofanL2TPv3controlchannel.However,whendifferentplatforms
interoperateacrossanL2TPv3controlchannel,bothplatformsneedto
encapsulatepacketswitha4bytecookielength.
TheL2TPv3pseudowirecontrolencapsulationconsistsof32bits(4bytes)and
containsinformationusedtosequenceL2TPpackets(seethesection
"Sequencing").Forthepurposesofsequencing,onlythefirstbitandbits8to31
arerelevant.
Bit1indicateswhethertheSequenceNumberfield,bits8to31,containsavalid
sequencenumberandistobeupdated.
L2TPv3Features
L2TPv3providesXconnectsupportforEthernet,802.1q(VLAN),FrameRelay,
HDLC,andPPP,usingthesessionsdescribedinthefollowingsections:
StaticL2TPv3Sessions(nonnegotiated,PVClikeforwardedsessions)
DynamicL2TPv3Sessions(negotiated,forwardedsessionsusingthe
17/117
27.4.2016.
L2TPv3controlplaneforsessionnegotiation)
L2TPv3alsoincludessupportforthefeaturesdescribedinthefollowing
sections:
Sequencing
LocalSwitching
Keepalive
MTUHandling
StaticL2TPv3Sessions
Typically,theL2TPcontrolplaneisresponsiblefornegotiatingsession
parameters,suchasthesessionIDorthecookie,inordertosetupthesession.
However,someIPnetworksrequiresessionstobeconfiguredsothatno
signalingisrequiredforsessionestablishment.Youcan,therefore,setupstatic
L2TPv3sessionsforaPErouterbyconfiguringfixedvaluesforthefieldsinthe
L2TPdataheader.AstaticL2TPv3sessionallowsthePEtotunnelLayer2
trafficassoonastheattachmentcircuittowhichthesessionisboundcomesup.
NoteInanL2TPv3staticsession,youcanstillruntheL2TPcontrolchannelto
performpeerauthenticationanddeadpeerdetection.IftheL2TP
controlchannelcannotbeestablishedoristorndownbecauseofa
hellofailure,thestaticsessionisalsotorndown.
WhenyouuseastaticL2TPv3session,youcannotperformcircuitinterworking,
suchasLMI,becausethereisnofacilitytoexchangecontrolmessages.To
performcircuitinterworking,youmustuseadynamicsession.
DynamicL2TPv3Sessions
AdynamicL2TPsessionisestablishedthroughtheexchangeofcontrol
messagescontainingattributevaluepairs(AVPs).EachAVPcontains
informationaboutthenatureoftheLayer2linkbeingforwarded:thepayload
type,virtualcircuit(VC)ID,andsoon.
MultipleL2TPsessions(oneforeachforwardedLayer2circuit)canexist
betweenapairofPEs,andcanbemaintainedbyasinglecontrolchannel.
SessionIDsandcookiesaredynamicallygeneratedandexchangedaspartofa
dynamicsessionsetup.Informationsuchassequencingconfigurationisalso
exchanged.Circuitstatechanges(UP/DOWN)areconveyedusingtheSLI
message.
18/117
27.4.2016.
Sequencing
AlthoughthecorrectsequenceofreceivedLayer2framesisguaranteedby
someLayer2technologies(bythenatureofthelink,suchasaserialline)orthe
protocolitself,forwardedLayer2framesmaybelost,duplicated,orreordered
whentheytraverseanetworkasIPpackets.IftheLayer2protocoldoesnot
provideanexplicitsequencingmechanism,youcanconfigureL2TPto
sequenceitsdatapacketsaccordingtothedatachannelsequencing
mechanismdescribedintheL2TPv3IETFl2tpextworkinggroupdraft.
AreceiverofL2TPdatapacketsmandatessequencingthroughtheSequencing
RequiredAVPwhenthesessionisbeingnegotiated.Asenderthatreceivesthis
AVP(orthatismanuallyconfiguredtosendsequencedpackets)usestheLayer
2specificpseudowirecontrolencapsulationdefinedinL2TPv3.
Currently,youcanconfigureL2TPonlytodropoutoforderpacketsyoucannot
configureL2TPtodeliverthepacketsoutoforder.Noreorderingmechanismis
available.
LocalSwitching
Localswitching(fromoneporttoanotherportinthesamerouter)issupported
forbothstaticanddynamicsessions.YoumustconfigureseparateIPaddresses
foreachXconnectstatement.
Seethesection"ConfigurationExamplesforLayer2TunnelProtocolVersion3"
foranexampleofhowtoconfigurelocalportswitching.
DistributedCiscoExpressForwarding(dCEF)switchingissupportedforL2TP
ontheCisco7500seriesandCisco12000seriesInternetrouters.
NoteFortheCisco7500series,sequencingissupported,butallL2TPpackets
thatrequiresequencenumberprocessingaresenttotheRSP.
SequencingisnotsupportedfortheCisco12000seriesInternetrouters
inRelease12.0(24)S.OntheCisco12000seriesInternetrouters,
sequencingwillbesupportedinafuturereleasewithsequencenumber
processingdonebytheservercardfastpath.
Itisdesirabletoavoidfragmentationissuesintheserviceprovidernetwork
becausereassemblyiscomputationallyexpensive.Theeasiestwaytoavoid
19/117
27.4.2016.
fragmentationissuesistoconfiguretheCErouterswithanMTUvaluethatis
smallerthanthepseudowirepathMTU.However,inscenarioswherethisisnot
anoption,fragmentationissuesmustbeconsidered.Previously,L2TP
supportedonlythefollowingoptionsforpacketfragmentationwhenapacketis
determinedtoexceedtheL2TPpathMTU:
Unconditionallydropthepacket
FragmentthepacketafterL2TP/IPencapsulation
DropthepacketandsendanInternetControlMessageProtocol(ICMP)
unreachablemessagebacktotheCErouter
CiscoIOSRelease12.0(24)SintroducestheabilitytoallowIPtrafficfromtheCE
routertobefragmentedbeforethedataentersthepseudowire,forcingthe
computationallyexpensivereassemblytooccurintheCEnetworkratherthanin
theserviceprovidernetwork.Thenumberoffragmentsthatmustbegenerated
isdeterminedbasedonthediscoveredpseudowirepathMTU.TheoriginalL2
headeristhencopiedtoeachofthegeneratedfragments,theL2TP/IP
encapsulationisadded,andtheframesarethenforwarded.Thisfeaturewillbe
implicitlyenabledwhenevertheippmtucommandisenabledinthepseudowire
class.ItwillbeappliedtoanypacketsreceivedfromtheCEnetworkthathavea
Don'tFragment(DF)bitsetto0andthatexceedtheL2TPpathMTUinsize.
FragmentationofIPpacketsbeforethedataentersthepseudowireissupported
ontheCisco7200series,Cisco7500series,andCisco12000InternetRouters
inCiscoIOSRelease12.0(24)S.
WhenLayer2trafficistunneledacrossanIPnetwork,informationcontainedin
theToSbitsmaybetransferredtotheL2TPencapsulatedIPpacketsinoneof
thefollowingways:
IfthetunneledLayer2framesencapsulateIPpacketsthemselves,itmaybe
desirabletosimplycopytheToSbytesoftheinnerIPpacketstotheouterIP
packetheaders.Thisactionisknownas"ToSbytereflection."
StaticToSbyteconfiguration.YouspecifytheToSbytevalueusedbyall
packetssentacrossthepseudowire.
OntheCisco10720,ToSconfigurationcanbedoneusingMQC.Ifboth
staticToSbyteconfigurationandMQCToSbyteconfigurationare
implemented,theMQCconfigurationwilltakeprecedence.
Seethesection"ConfiguringaNegotiatedL2TPv3SessionforLocalHDLC
SwitchingExample"formoreinformationabouthowtoconfigureToS
information.
Keepalive
20/117
27.4.2016.
ThekeepalivemechanismforL2TPv3extendsonlytotheendpointsofthe
tunnelingprotocol.L2TPhasareliablecontrolmessagedeliverymechanism
thatservesasthebasisforthekeepalivemechanism.Thekeepalive
mechanismconsistsofanexchangeofL2TPhellomessages.
Ifakeepalivemechanismisrequired,thecontrolplaneisused,althoughitmay
notbeusedtobringupsessions.Youcanmanuallyconfiguresessions.
InthecaseofstaticL2TPv3sessions,acontrolchannelbetweenthetwoL2TP
peersisnegotiatedthroughtheexchangeofstartcontrolchannelrequest
(SCCRQ),startcontrolchannelreplay(SCCRP),andstartcontrolchannel
connected(SCCCN)controlmessages.Thecontrolchannelisresponsibleonly
formaintainingthekeepalivemechanismthroughtheexchangeofhello
messages.
Theintervalbetweenhellomessagesisconfigurablepercontrolchannel.Ifone
peerdetectsthattheotherhasgonedownthroughthekeepalivemechanism,it
sendsaStopCCNcontrolmessageandthennotifiesallofthepseudowiresto
thepeerabouttheevent.Thisnotificationresultsintheteardownofboth
manuallyconfiguredanddynamicsessions.
MTUHandling
ItisimportantthatyouconfigureanMTUappropriateforaeachL2TPv3
tunneledlink.TheconfiguredMTUsizeensuresthefollowing:
ThelengthsofthetunneledLayer2framesfallbelowtheMTUofthe
destinationattachmentcircuit
Thetunneledpacketsarenotfragmented,whichforcesthereceivingPEto
reassemblethem
L2TPv3handlestheMTUasfollows:
Thedefaultbehavioristofragmentpacketsthatarelargerthanthesession
MTU.TheoneexceptionisonCisco12000seriesInternetrouters,where
fragmentationoftunneledpacketsisnotallowed.
Ifyouenabletheipdfbitsetcommandinthepseudowireclass,thedefault
MTUbehaviorchangessothatanypacketsthatcannotfitwithinthetunnel
MTUaredropped.
Ifyouenabletheippmtucommandinthepseudowireclass,theL2TPv3
controlchannelparticipatesinthepathMTUdiscovery.Whenyouenable
thisfeature,thefollowingprocessingisperformed:
ICMPunreachablemessagessentbacktotheL2TPv3routerare
decipheredandthetunnelMTUisupdatedaccordingly.Inorderto
receiveICMPunreachablemessagesforfragmentationerrors,theDFbit
inthetunnelheaderissetaccordingtotheDFbitvaluereceivedfrom
theCE,orstaticallyiftheipdfbitsetoptionisenabled.ThetunnelMTU
21/117
27.4.2016.
isperiodicallyresettothedefaultvaluebasedonaperiodictimer.
ICMPunreachablemessagesaresentbacktotheclientsontheCEside.
ICMPunreachablemessagesaresenttotheCEwheneverIPpackets
arriveontheCEPEinterfaceandhaveapacketsizegreaterthanthe
tunnelMTU.ALayer2headercalculationisperformedbeforetheICMP
unreachablemessageissenttotheCE.
Table1 comparesL2TPv3andUTIsupport.
Table2ComparisonofL2TPv3andUTISupport
Feature
L2TPv3
UTI
Maximum
numberof
sessions
Cisco7200series:3000
Cisco7200
series:1000
Cisco10720:2000
Cisco7500
series:1000
Cisco10720
series:1000
Cisco12000
series:1000
Tunnel
cookielength
0,4,or8bytecookiesaresupportedfor
theCisco7200seriesandtheCisco7500
seriesrouters.
8bytes
FortheCisco10720Internetrouterandthe
Cisco12000seriesInternetrouters,only8
bytecookiescanbereceivedin
Release12.0(24)S0,4,or8bytecookies
canbesent.
Static
sessions
SupportedinRelease12.0(21)S.
Supported
Dynamic
sessions
Not
supported
StaticToS
Supported
22/117
27.4.2016.
MQCToS
SupportedinRelease12.0(23)Sforthe
Cisco10720only.
Supported
InnerIPToS
mapping
SupportedontheCisco7200seriesrouters,
Cisco7500seriesrouters,andthe
Cisco12000seriesInternetrouters.
Not
supported
Tobesupportedinafuturereleaseforthe
Cisco10720Internetrouter.
802.1p
mapping
SupportedinRelease12.0(23)Sforthe
Cisco10720only.
Not
supported
Keepalive
Supported
onthe
Cisco10720
only.
PathMTU
discovery
SupportedontheCisco7200series,
Cisco7500series,andtheCisco12000
seriesInternetrouters.
Not
supported
ICMP
unreachable
Cisco7500series,andCisco12000Internet
routers.
Not
supported
VLANrewrite
Cisco7500series,andtheCisco10720
InternetrouterinRelease12.0(23)S.
Supported
Tobesupportedinafuturereleasefor
Cisco12000seriesInternetrouters.
VLANand
nonVLAN
translation
Tobesupportedinafuturerelease.
Supported
onthe
Cisco10720
only.
23/117
27.4.2016.
only.
Porttrunking
Supported
ISISpacket
fragmentation
throughan
L2TPv3
session
Cisco7500series,andCisco12000series
Internetrouters.
Not
supported
IPpacket
fragmentation
throughan
L2TPv3
session
Cisco7500series,andCisco12000Internet
routersinRelease12.0(24)S.
Payload
sequence
number
checking
Tobesupportedinafuturerelease.
Not
supported
MIBsupport
VPDNMIBforthepseudowire
IfTableMIBfortheattachmentcircuit.
IfTableMIB
forthe
session
interface.
Not
supported
L2TPv3supportsthefollowingLayer2payloadsthatcanbeincludedinL2TPv3
packetstunneledoverthepseudowire:
FrameRelay
Ethernet
802.1q(VLAN)
HDLC
PPP
ATM
NoteEachL2TPv3tunneledpacketincludestheentireLayer2frameofthe
24/117
27.4.2016.
payloadsdescribedinthissection.Ifsequencingisrequired(seethe
section"Sequencing"),aLayer2specificsublayer(seethesection
"PseudowireControlEncapsulation")isincludedintheL2TPv3header
toprovidetheSequenceNumberfield.
FrameRelay
L2TPv3supportstheFrameRelayfunctionalitydescribedinthefollowing
sections:
PorttoPortTrunking
DLCItoDLCISwitching
PVCStatusSignaling
Sequencing
ToSMarking
CIRGuarantees
BindingL2TPv3SessionstoMultilinkFrameRelayInterfaces
PorttoPortTrunking
PorttoporttrunkingiswheretwoCEFrameRelayinterfacesareconnectedas
byaleasedline(UTI"raw"mode).Alltrafficarrivingononeinterfaceis
forwardedtransparentlyacrossthepseudowiretotheotherinterface.
Forexample,inFigure1,ifthetwoCEroutersareconnectedbyavirtualleased
line,thePErouterstransparentlytransportallpacketsbetweenCER3andCE
R4overapseudowire.PER1andPER2donotexamineorchangetheDLCIs,
anddonotparticipateintheLMIprotocol.ThetwoCEroutersareLMIpeers.
ThereisnothingFrameRelayspecificaboutthisserviceasfarasthePE
routersareconcerned.TheCEroutersshouldbeabletouseanyencapsulation
basedonHDLCframingwithoutneedingtochangetheproviderconfiguration.
DLCItoDLCISwitching
FrameRelayDLCItoDLCIswitchingiswhereindividualFrameRelayDLCIsare
connectedtocreateanendtoendFrameRelayPVC.TrafficarrivingonaDLCI
ononeinterfaceisforwardedacrossthepseudowiretoanotherDLCIonthe
otherinterface.
Forexample,inFigure1,CER3andPER1areFrameRelayLMIpeersCER4
andPER2arealsoLMIpeers.YoucanuseadifferenttypeofLMIbetweenCE
R3andPER1comparedtowhatyouusebetweenCER4andPER2.
TheCEdevicesmaybeaFrameRelayswitchorenduserdevice.EachFrame
RelayPVCiscomposedofmultiplesegments.TheDLCIvalueislocaltoeach
segmentandischangedastrafficisswitchedfromsegmenttosegment.Note
25/117
27.4.2016.
that,inFigure1,twoFrameRelayPVCsegmentsareconnectedbya
pseudowire.FrameRelayheaderflags(FECN,BECN,C/R,DE)arepreserved
acrossthepseudowire.
PVCStatusSignaling
PVCstatussignalingispropagatedtowardFrameRelayendusersbytheLMI
protocol.YoucanconfiguretheLMItooperateinanyofthefollowingmodes:
UNIDTEmodePVCstatusisnotreported,onlyreceived.
UNIDCEmodePVCstatusisreportedbutnotreceived.
NNImodePVCstatusisreportedandreceivedindependently.
L2TPv3supportsallthreemodes.
ThePVCstatusshouldbereportedasACTIVEonlyifthePVCisavailablefrom
thereportingdevicetotheFrameRelayenduserdevice.Allinterfaces,line
protocols,andpseudowiresmustbeoperationalbetweenthereportingdevice
andtheFrameRelayenduserdevice.
NotethatanykeepalivefunctionsonthesessionareindependentofFrame
Relay,butanystatechangesthataredetectedarefedintothePVCstatus
reporting.Forexample,theL2TPcontrolchanneluseshellopacketsasa
keepalivefunction.IftheL2TPv3keepalivefails,allL2TPv3sessionsaretorn
down.LossofthesessionisnotifiedtoFrameRelay,whichcanthenreport
PVCsINACTIVEtotheCEdevices.
Forexample,inFigure1,CER3reportsACTIVEtoPER1onlyifthePVCis
availablewithinCER3.WhenCER3isaswitch,itreportsallthewaytotheuser
deviceinthecustomernetwork.
PER1reportsACTIVEtoCER3onlyifthePVCisavailablewithinPER1andall
thewaytotheenduserdevice(viaPER2andCER3)intheothercustomer
VPNsite.
TheACTIVEstateispropagatedhopbyhop,independentlyineachdirection,
fromoneendoftheFrameRelaynetworktotheotherend.
Sequencing
FrameRelayprovidesanorderedserviceinwhichpacketssenttotheFrame
Relaynetworkbyoneenduserdevicearedeliveredinordertotheotherend
userdevice.Whenswitchingisoccurringoverthepseudowire,packetordering
mustbeabletobepreservedwithaveryhighprobabilitytocloselyemulatea
traditionalFrameRelayservice.IftheCErouterisnotusingaprotocolthatcan
detectmisorderingitself,configuringsequencenumberprocessingmaybe
important.Forexample,iftheLayer3protocolisIPandFrameRelayis
26/117
27.4.2016.
thereforeusedonlyforencapsulation,sequencingisnotrequired.Todetect
misordering,youcanconfiguresequencenumberprocessingseparatelyfor
transmissionorreception.Formoreinformationabouthowtoconfigure
sequencing,seethesection"ConfiguringaNegotiatedL2TPv3Sessionfor
LocalHDLCSwitchingExample."
ToSMarking
TheToSbytesintheIPheadercanbestaticallyconfiguredorreflectedfromthe
internalIPheader.TheFrameRelayDEbitdoesnotinfluencetheToSbytes.
CIRGuarantees
Inordertoprovidecommittedinformationrate(CIR)guarantees,youcan
configureaqueueingpolicythatprovidesbandwidthtoeachDLCItothe
interfacefacingthecustomernetworkontheegressPE.
NoteInCiscoIOSRelease12.0(24)S,CIRguaranteesaresupportedonlyon
theCisco7500serieswithdCEF.Thissupportrequiresthatthecore
hassufficientbandwidthtohandleallCEtrafficandthatthecongestion
occursonlyattheegressPE.
BindingL2TPv3SessionstoMultilinkFrameRelayInterfaces
TheconfigurationofanL2TPv3sessiononaMultilinkFrameRelay(MLFR)
bundleinterfaceissupportedonlyonCisco12000SeriesTwoPortChannelized
OC3/STM1(DS1/E1)andSixPortChannelizedT3(T1)linecards.
TheMultilinkFrameRelayfeatureintroducesfunctionalitybasedontheFrame
RelayForumMultilinkFrameRelayUNI/NNIImplementationAgreement
(FRF.16).Thisfeatureprovidesacosteffectivewaytoincreasebandwidthfor
particularapplicationsbyenablingmultipleseriallinkstobeaggregatedintoa
singlebundleofbandwidth.
ForanexampleofhowtoconfigureL2TPv3tunnelingonamultilinkFrame
Relaybundleinterface,seeConfiguringMLFRforL2TPv3ontheCisco12000
SeriesExample.
ForinformationabouthowconfigureandusetheMLFRfeature,refertothe
MultilinkFrameRelay(FRF.16)publication.
Ethernet
AnEthernetframearrivingataPErouterissimplyencapsulatedinitsentirety
withanL2TPdataheader.Attheotherend,areceivedL2TPdatapacketis
27/117
27.4.2016.
strippedofitsL2TPdataheader.Thepayload,anEthernetframe,isthen
forwardedtotheappropriateattachmentcircuit.
BecausetheL2TPv3tunnelingprotocolservesessentiallyasabridge,itneed
notexamineanypartofanEthernetframe.AnyEthernetframereceivedonan
interfaceistunneled,andanyL2TPtunneledEthernetframeisforwardedout
theinterface.
NoteDuetothewayinwhichL2TPv3handlesEthernetframes,anEthernet
interfacemustbeconfiguredtopromiscuousmodeinordertocapture
alltrafficreceivedontheEthernetsegmentattachedtotherouter.All
frameswillbetunneledthroughtheL2TPpseudowire.
802.1q(VLAN)
L2TPv3supportsVLANmembershipinthefollowingways:
Portbased,inwhichundatedEthernetframesarereceived.
VLANbased,inwhichtaggedEthernetframesarereceived.
InL2TPv3,EthernetXconnectsupportsportbasedVLANmembershipandthe
receptionoftaggedEthernetframes.AtaggedEthernetframecontainsatag
header(definedin802.1Q),whichis4byteslongandconsistsofa2bytetag
protocolidentifier(TPID)fieldanda2bytetagcontrolinformation(TCI)field.
TheTPIDindicatesthataTCIfollows.TheTCIisfurtherbrokendownintothe
followingthreefields:
Userpriorityfield
Canonicalformatindicator(CFI)
A12bitVLANID(VID)
ForL2TPv3,anEthernetsubinterfaceconfiguredtosupportVLANswitching
maybeboundtoanXconnectservicesothatallEthernettraffic,taggedwitha
VIDspecifiedonthesubinterface,istunneledtoanotherPE.TheVLANEthernet
framesareforwardedintheirentirety.ThereceivingPEmayrewritetheVIDof
thetunneledtraffictoanothervaluebeforeforwardingthetrafficontoan
attachmentcircuit.
TosuccessfullyrewriteVLANs,itmaybenecessarytodisabletheSpanning
TreeProtocol(STP).ThiscanbedoneonaperVLANbasisbyusingtheno
spanningtreevlancommand.
NoteDuetothewayinwhichL2TPv3handles802.1qVLANpackets,the
Ethernetinterfacemustbeconfiguredinpromiscuousmodetocapture
alltrafficreceivedontheEthernetsegmentattachedtotherouter.All
framesaretunneledthroughtheL2TPpseudowire.
28/117
27.4.2016.
HDLC
L2TPv3encapsulatesanHDLCframearrivingataPEinitsentirety(including
theAddress,Control,andProtocolfields,butnottheFlagfieldsandtheframe
checksequence)withanL2TPdataheader.
PPP
PEsthatsupportL2TPv3forwardPPPtrafficusinga"transparentpassthrough"
model,inwhichthePEsplaynoroleinthenegotiationandmaintenanceofthe
PPPlink.L2TPv3encapsulatesaPPPframearrivingataPEinitsentirety
(includingtheHDLCAddressandControlfields)withanL2TPdataheader.
ATM
L2TPv3canconnecttwoisolatedATMcloudsoverapacketswitchednetwork
whilemaintaininganendtoendATMServiceLevelAgreement(SLA).
CiscoIOSRelease12.0(25)Ssupportsvirtualpath(VP)singlecellrelay,with
oneATMcellbeingforwardedperpacket.Allpacketsaretransparently
forwardedovertheL2TPv3pseudowire.
HowtoConfigureLayer2TunnelProtocol
Version3
Thissectioncontainsthefollowingprocedures:
ConfiguringL2TPControlChannelParameters(optional)
ConfiguringtheL2TPv3Pseudowire(required)
ConfiguringtheXconnectAttachmentCircuit(required)
ManuallyConfiguringL2TPv3SessionParameters(required)
ConfiguringtheXconnectAttachmentCircuitforATMVPModeSingleCell
RelayoverL2TPv3(optional)
ConfiguringL2TPControlChannelParameters
TheL2TPclassconfigurationprocedurecreatesatemplateofL2TPcontrol
channelparametersthatcanbeinheritedbydifferentpseudowireclasses.L2TP
controlchannelparametersareusedincontrolchannelauthentication,
keepalivemessages,andcontrolchannelnegotiation.InanL2TPv3session,
thesameL2TPclassmustbespecifiedinthepseudowireconfiguredonthePE
routerateachendofthecontrolchannel.ConfiguringL2TPcontrolchannel
parametersisoptional.However,theL2TPclassmustbeconfiguredbeforeitis
withassociatedapseudowireclass(seethesection"ConfiguringtheL2TPv3
Pseudowire").
29/117
27.4.2016.
ThethreemaingroupsofL2TPcontrolchannelparametersthatyoucan
configureinanL2TPclassaredescribedinthefollowingsections:
ConfiguringL2TPControlChannelTimingParameters
ConfiguringL2TPControlChannelAuthenticationParameters
ConfiguringL2TPControlChannelMaintenanceParameters
AfteryouenterL2TPclassconfigurationmode,youcanconfigureL2TPcontrol
channelparametersinanyorder.Ifyouhavemultipleauthentication
requirementsyoucanconfiguremultiplesetsofL2TPclasscontrolchannel
parameterswithdifferentL2TPclassnames.However,onlyonesetofL2TP
classcontrolchannelparameterscanbeappliedtoaconnectionbetweenany
pairofIPaddresses.
ConfiguringL2TPControlChannelTiming
Parameters
ThefollowingL2TPcontrolchanneltimingparameterscanbeconfiguredin
L2TPclassconfigurationmode:
Packetsizeofthereceivewindowusedforthecontrolchannel
Retransmissionparametersusedforcontrolmessages
Timeoutparametersusedforthecontrolchannel
ThistaskconfiguresasetoftimingcontrolchannelparametersinanL2TP
class.Allofthetimingcontrolchannelparameterconfigurationsareoptionaland
maybeconfiguredinanyorder.Iftheseparametersarenotconfigured,the
defaultvaluesareapplied.
SUMMARYSTEPS
1. enable
2. configureterminal
3. l2tpclass[l2tpclassname]
4. receivewindowsize
5. retransmit{initialretriesinitialretries|retriesretries|timeout{max|
min}timeout}
6. timeoutsetupseconds
DETAILEDSTEPS
Commandor
Action
Step1
enable
Purpose
30/117
27.4.2016.
Example:
Router>enable
EnablesprivilegedEXECmode.
Step2
configure
terminal
Enteryourpasswordifprompted.
Entersglobalconfigurationmode.
Example:
Router#
configure
terminal
Step3
l2tpclass
[l2tpclass
name]
SpecifiestheL2TPclassnameandenters
L2TPclassconfigurationmode.
Example:
Router(config)#
l2tpclass
class1
Step4
receivewindow
size
Example:
Router(config
l2tpclass)#
receivewindow
30
Step5
Thel2tpclassnameargumentis
optional.However,ifyouwantto
configuremultipleL2TPclassesyou
mustspecifyauniquel2tpclassname
foreachone.
(Optional)Configuresthenumberof
packetsthatcanbereceivedbytheremote
peerbeforebackoffqueueingoccurs.
Thevalidvaluesrangefrom1tothe
upperlimitthepeerhasforreceiving
packets.Thedefaultvalueistheupper
limit.
retransmit
(Optional)Configuresparametersthataffect
{initial
theretransmissionofcontrolpackets:
retries
initialretriesspecifieshowmany
initialretries
SCCRQsareresentbeforegivingupon
|retries
thesession.Validvaluesfortheinitial
retries|
retriesargumentrangefrom1to1000.
Thedefaultvalueis2.
timeout{max|
min}timeout}
retriesspecifieshowmany
retransmissioncyclesoccurbefore
Example:
determiningthatthepeerPErouter
Router(config
doesnotrespond.Validvaluesforthe
l2tpclass)#
retriesargumentrangefrom1to1000.
retransmit
Thedefaultvalueis15.
retries10
timeout{max|min}specifies
maximumandminimumretransmission
intervals(inseconds)forresending
31/117
27.4.2016.
controlpackets.Validvaluesforthe
timeoutargumentrangefrom1to8.
Thedefaultmaximumintervalis8the
defaultminimumintervalis1.
Step6
timeoutsetup
seconds
Example:
Router(config
l2tpclass)#
timeoutsetup
400
(Optional)Configurestheamountoftime,in
seconds,allowedtosetupacontrol
channel.
Validvaluesforthesecondsargument
rangefrom60to6000.Thedefault
valueis300.
ConfiguringL2TPControlChannel
AuthenticationParameters
ThefollowingL2TPcontrolchannelauthenticationparameterscanbe
configuredinL2TPclassconfigurationmode:
AuthenticationfortheL2TPcontrolchannel
Localhostnameusedforauthenticatingthecontrolchannel
HidingtheAVPsinoutgoingcontrolmessages
PasswordusedforcontrolchannelauthenticationandAVPhiding
Thistaskconfiguresasetofauthenticationcontrolchannelparametersinan
L2TPclass.Alloftheauthenticationcontrolchannelparameterconfigurations
areoptionalandmaybeconfiguredinanyorder.Iftheseparametersarenot
configured,thedefaultvalueswillbeapplied.
SUMMARYSTEPS
1. enable
4. authentication
5. hostnamename
6. hidden
7. password[encryptiontype]password
DETAILEDSTEPS
Commandor
Purpose
32/117
27.4.2016.
Action
Step1
enable
Example:
Router>enable
Step2
configure
terminal
Example:
Router#
configure
terminal
Step3
l2tpclass
[l2tpclass
name]
Example:
Router(config)#
l2tpclass
class1
Step4
authentication
foreachone.
(Optional)Enablesauthenticationforthe
controlchannelbetweenPErouters.
Example:
Router(config
l2tpclass)#
authentication
Step5
hostnamename
Example:
Router(config
l2tpclass)#
hostnameyb2
Step6
(Optional)Specifiesahostnameusedto
identifytherouterduringL2TPcontrol
channelauthentication.
Ifyoudonotusethiscommand,the
defaulthostnameoftherouterisused.
hidden
(Optional)HidestheAVPsincontrol
messages.
Example:
AVPhidingisnothiddenbydefault.
33/117
27.4.2016.
Router(config
l2tpclass)#
hidden
Step7
password
[encryption
type]password
(Optional)Configuresthepasswordusedfor
controlchannelauthentication.
Example:
Router(config
l2tpclass)#
password
tunnel2
Thevalidvaluesfortheoptional
encryptiontyperangefrom0to7.Ifyou
donotusethiscommandtospecifya
password,thepasswordassociatedwith
theremotepeerPEistakenfromthe
valueenteredwiththeusername
passwordvalueglobalconfiguration
command.
ConfiguringL2TPControlChannelMaintenance
Parameters
TheL2TPhellopacketkeepaliveintervalcontrolchannelmaintenance
parametercanbeconfiguredinL2TPclassconfigurationmode.
ThistaskconfigurestheintervalusedforhellomessagesinanL2TPclass.This
controlchannelparameterconfigurationisoptional.Ifthisparameterisnot
configured,thedefaultvaluewillbeapplied.
SUMMARYSTEPS
1. enable
4. hellointerval
DETAILEDSTEPS
Commandor
Action
Purpose
Step1
enable
Example:
Router>enable
Step2
configure
34/117
27.4.2016.
terminal
Example:
Router#
configure
terminal
Step3
l2tpclass
[l2tpclass
name]
Example:
Router(config)#
l2tpclass
class1
Step4
hellointerval
Example:
Router(config
l2tpclass)#
hello100
foreachone.
(Optional)Specifiestheexchangeinterval
(inseconds)usedbetweenL2TPhello
packets.
Validvaluesfortheintervalargument
rangefrom0to1000.Thedefaultvalue
is60.
ConfiguringtheL2TPv3Pseudowire
Thepseudowireclassconfigurationprocedurecreatesaconfigurationtemplate
forthepseudowire.Youusethistemplate,orclass,toconfiguresessionlevel
parametersforL2TPv3sessionsthatwillbeusedtotransportattachmentcircuit
trafficoverthepseudowire.
ThepseudowireconfigurationspecifiesthecharacteristicsoftheL2TPv3
signalingmechanism,includingthedataencapsulationtype,thecontrol
protocol,sequencing,fragmentation,payloadspecificoptions,andIP
properties.Thesettingthatdeterminesifsignalingisusedtosetupthe
pseudowireisalsoincluded.
ForsimpleL2TPv3signalingconfigurationsonmostplatforms,pseudowireclass
configurationisoptional.However,specifyingasourceIPaddresstoconfigurea
loopbackinterfaceishighlyrecommended.Ifyoudonotconfigurealoopback
interface,therouterwillchoosethebestavailablelocaladdress,whichcouldbe
anyIPaddressconfiguredonacorefacinginterface.Thisconfigurationcould
preventacontrolchannelfrombeingestablished.OntheCisco12000series
Internetrouters,specifyingasourceIPaddressismandatory,andyoushould
configurealoopbackinterfacethatisdedicatedfortheuseofL2TPv3sessions
exclusively.Ifyoudonotconfigureotherpseudowireclassconfiguration
commands,thedefaultvaluesareused.
35/117
27.4.2016.
Onceyouspecifytheencapsulationl2tpv3command,youcannotremoveit
usingthenoencapsulationl2tpv3command.Norcanyouchangethe
command'ssettingusingtheencapsulationmplscommand.Thosemethods
resultinthefollowingerrormessage:
Encapsulationchangesarenotallowedonanexistingpwclass.
Toremovethecommand,youmustdeletethepseudowirewiththeno
pseudowireclasscommand.Tochangethetypeofencapsulation,removethe
pseudowirewiththenopseudowireclasscommandandreestablishthe
pseudowireandspecifythenewencapsulationtype.
SUMMARYSTEPS
1. enable
3. pseudowireclass[pwclassname]
4. encapsulationl2tpv3
5. protocol{l2tpv3|none}[l2tpclassname]
6. iplocalinterfaceinterfacename
7. ippmtu
8. iptos{valuevalue|reflect}
9. ipdfbitset
10. ipttlvalue
11. ipprotocol{l2tp|uti|protocolnumber}
12. sequencing{transmit|receive|both}
DETAILEDSTEPS
Commandor
Action
Purpose
Step1
enable
Example:
Router>enable
Step2
configure
terminal
Example:
Router#
configure
terminal
36/117
27.4.2016.
Step3
pseudowire
class[pw
classname]
Enterspseudowireclassconfiguration
modeandoptionallyspecifiesthenameof
theL2TPpseudowireclass.
Example:
Router(config)#
pseudowire
classetherpw
Step4
encapsulation
l2tpv3
SpecifiesthatL2TPv3isusedasthedata
encapsulationmethodtotunnelIPtraffic.
Example:
Router(config
pw)#
encapsulation
l2tpv3
Step5
protocol
{l2tpv3|none}
[l2tpclass
name]
Example:
Router(config
pw)#protocol
l2tpv3class1
Step6
(Optional)SpecifiestheL2TPv3signaling
protocoltobeusedtomanagethe
pseudowirescreatedwiththecontrol
channelparametersinthespecifiedL2TP
class(seethesection"ConfiguringL2TP
ControlChannelParameters").
Ifthel2tpclassnameargumentisnot
specified,thedefaultvaluesforL2TP
controlchannelparameterswillbe
used.Thedefaultprotocoloptionis
l2tpv3.
Ifyoudonotwanttousesignalingin
theL2TPv3sessionscreatedwiththis
pseudowireclass,enterprotocol
none.(Theprotocolnone
configurationisnecessarywhen
configuringinteroperabilitywitha
remotepeerthatrunsUTI.)
iplocal
interface
interfacename
SpecifiesthePErouterinterfacewhoseIP
addressistobeusedasthesourceIP
addressforsendingtunneledpackets.
Example:
Router(config
pw)#iplocal
interfacee0/0
Usethesamelocalinterfacenamefor
allpseudowireclassesconfigured
betweenapairofPErouters.
Note Thiscommandmustbeconfigured
37/117
27.4.2016.
forpseudowireclassconfigurations
usingL2TPv3asthedata
encapsulationmethod.
Step7
ippmtu
Example:
Router(config
pw)#ippmtu
(Optional)Enablesthediscoveryofthe
pathMTUfortunneledtraffic.
Thiscommandenablestheprocessing
ofICMPunreachablemessagesthat
indicatefragmentationerrorsinthe
backbonenetworkthatcarriesL2TPv3
sessiontraffic.Also,thiscommand
enablesMTUcheckingforIPpackets
sentintothesessionandthathavethe
DFbitset.AnyIPpacketlargerthan
theMTUisdroppedandanICMP
unreachablemessageissent.MTU
discoveryisdisabledbydefault.
Note Theippmtucommandisnot
supportedifyoudisabledsignaling
withtheprotocolnonecommand
inStep5.
Thiscommandmustbeenabledinthe
pseudowireclassconfigurationfor
fragmentationofIPpacketsbeforethe
dataentersthepseudowiretooccur.
Note ForfragmentationofIPpackets
beforethedataentersthe
pseudowire,itisrecommendedthat
theipdfbitsetcommandisalso
enabledinthepseudowireclass
configuration.Thisallowsthe
PMTUtobeobtainedmorerapidly.
Step8
iptos{value
value|
reflect}
Example:
Router(config
pw)#iptos
reflect
(Optional)ConfiguresthevalueoftheToS
byteinIPheadersoftunneledpackets,or
reflectstheToSbytevaluefromtheinner
IPheader.
Validvaluesforthevalueargument
rangefrom0to255.ThedefaultToS
bytevalueis0.
38/117
27.4.2016.
Step9
ipdfbitset
Example:
Router(config
pw)#ipdfbit
set
Step10
ipttlvalue
Example:
(Optional)ConfiguresthevalueoftheDF
bitintheouterheadersoftunneled
packets.
(Optional)Configuresthevalueofthetime
tolive(TTL)byteintheIPheadersof
tunneledpackets.
Router(config
pw)#ipttl100
Step11
ipprotocol
{l2tp|uti|
protocol
number}
Validvaluesforthevalueargument
rangefrom1to255.ThedefaultTTL
bytevalueis255.
(Optional)ConfigurestheIPprotocoltobe
usedfortunnelingpackets.
Example:
Router(config
pw)#ip
protocoluti
Step12
Usethiscommandif(forperformance
reasons)youdonotwantreassembly
oftunneledpacketstobeperformedon
thepeerPErouter.Thiscommandis
disabledbydefault.
ForbackwardcompatibilitywithUTI,
enterutior120,theUTIprotocol
number.ThedefaultIPprotocolvalue
isl2tpor115,theL2TPprotocol
number.
sequencing
(Optional)Specifiesthedirectioninwhich
{transmit|
sequencingofdatapacketsina
receive|both} pseudowireisenabled:
Example:
transmitUpdatestheSequence
Numberfieldintheheadersofdata
packetssentoverthepseudowire
accordingtothedataencapsulation
methodthatisused.
receiveKeepstheSequenceNumber
fieldintheheadersofdatapackets
receivedoverthepseudowire.Outof
orderpacketsaredropped.
bothEnablesboththetransmitand
receiveoptions.
Router(config
pw)#sequencing
both
ConfiguringtheXconnectAttachmentCircuit
ThisconfigurationprocedurebindsanEthernet,802.1qVLAN,orFrameRelay
attachmentcircuittoanL2TPv3pseudowireforXconnectservice.Thevirtual
39/117
27.4.2016.
circuitidentifierthatyouconfigurecreatesthebindingbetweenapseudowire
configuredonaPErouterandanattachmentcircuitinaCEdevice.Thevirtual
circuitidentifierconfiguredonthePErouteratoneendoftheL2TPv3control
channelmustalsobeconfiguredonthepeerPErouterattheotherend.
SUMMARYSTEPS
1. enable
3. interfacetypeslot/port
4. xconnectpeeripaddressvcidpseudowireparameters[sequencing
{transmit|receive|both}]
DETAILEDSTEPS
Commandor
Action
Purpose
Step1
enable
Example:
Router>enable
Step2
configure
terminal
Example:
Router#
configure
terminal
Step3
interfacetype
slot/port
Example:
Specifiestheinterfacebytype(forexample,
Ethernet)andslotandportnumber,and
entersinterfaceconfigurationmode.
Router(config)#
interface
ethernet0/0
Step4
xconnectpeer
ipaddressvcid
pseudowire
parameters
[sequencing
{transmit|
receive|
SpecifiestheIPaddressofthepeerPE
routerandthe32bitvirtualcircuitidentifier
sharedbetweenthePEateachendofthe
controlchannel.
ThepeerrouterID(IPaddress)and
virtualcircuitIDmustbeaunique
combinationontherouter.
40/117
27.4.2016.
both}]
Atleastoneofthefollowingpseudowire
classparametersmustbeconfiguredfor
thepseudowireparametersargument:
Example:
Router(config
if)#xconnect
10.0.3.201123
pwclassvlan
xconnect
encapsulation{l2tpv3[manual]|
mpls}Specifiesthetunneling
methodusedtoencapsulatedatain
thepseudowire:
l2tpv3L2TPv3isthetunnelingmethodto
beused.
manual(Optional)Nosignalingistobe
usedintheL2TPv3controlchannel.This
commandplacestherouterinxconnect
configurationmodeformanualconfigurationof
L2TPv3parametersfortheattachmentcircuit.
mplsMPLSisthetunnelingmethodtobe
used.
pwclass{pwclassname}The
pseudowireclassconfigurationfrom
whichthedataencapsulationtype
(L2TPv3)willbetaken.
Theoptionalencapsulationparameter
specifiesthemethodofpseudowire
tunnelingused:L2TPv3orMPLS.Enter
manualifyoudonotwantsignaling
usedintheL2TPv3controlchannel.The
encapsulationl2tpv3manualkeyword
combinationentersxconnect
configurationsubmode.Seethesection
"ManuallyConfiguringL2TPv3Session
Parameters"fortheotherL2TPv3
commandsthatyoumustenterto
completetheconfigurationofthe
L2TPv3controlchannel.Ifyoudonot
enteranencapsulationvalue,the
encapsulationmethodenteredwiththe
passwordcommandinthesection
"ConfiguringtheXconnectAttachment
Circuit"isused.
Theoptionalpwclassparameterbinds
theXconnectstatementtoaspecific
pseudowireclass.Thepseudowireclass
thenservesasthetemplate
configurationforallattachmentcircuits
boundtoit.Specifythepseudowireclass
optionifyouneedtoconfiguremore
advancedoptions.
Note Youmustconfigureeitherthe
encapsulationorthepwclass
41/117
27.4.2016.
option.Youmayconfigureboth
options.
Note IfyouselectL2TPv3asyourdata
encapsulationmethod,youmust
specifythepwclasskeyword.
Theoptionalsequencingparameter
specifieswhethersequencingisrequired
forpacketsthatarereceived,sent,or
bothreceivedandsent.
ManuallyConfiguringL2TPv3SessionParameters
WhenyoubindanattachmentcircuittoanL2TPv3pseudowireforXconnect
serviceusingthexconnectl2tpv3manualcommand(seethesection
"ConfiguringtheXconnectAttachmentCircuit")becauseyoudonotwant
signaling,youmustthenconfigureL2TPspecificparameterstocompletethe
L2TPv3controlchannelconfiguration.
SUMMARYSTEPS
1. enable
4. xconnectpeeripaddressvcidencapsulationl2tpv3manualpwclass
pwclassname
5. l2tpidlocalsessionidremotesessionid
6. l2tpcookielocalsizelowvalue[highvalue]
7. l2tpcookieremotesizelowvalue[highvalue]
8. l2tphellol2tpclassname
DETAILEDSTEPS
Commandor
Action
Purpose
Step1
enable
Example:
Router>enable
42/117
27.4.2016.
Step2
configure
terminal
Example:
Router#
configure
terminal
Step3
interfacetype
slot/port
Example:
Specifiestheinterfacebytype(forexample,
Ethernet)andslotandportnumber,and
entersinterfaceconfigurationmode.
Router(config)#
interface
ethernet0/0
Step4
xconnectpeer
ipaddressvc
id
encapsulation
l2tpv3manual
pwclasspw
classname
Example:
Router(config
if)#xconnect
10.0.3.201123
encapsulation
l2tpv3manual
pwclassvlan
xconnect
Step5
l2tpidlocal
sessionid
remotesession
id
Example:
Router(config
ifxconn)#l2tp
id222111
Step6
l2tpcookie
localsizelow
controlchannel.
Theencapsulationl2tpv3manual
parameterspecifiesthatL2TPv3istobe
usedasthepseudowiretunneling
method,andentersxconnect
configurationmode.
Themandatorypwclasspwclass
namekeywordandargument
combinationspecifiesthepseudowire
classconfigurationfromwhichthedata
encapsulationtype(L2TPv3)willbe
taken.
Configurestheidentifiersforthelocal
L2TPv3sessionandfortheremoteL2TPv3
sessiononthepeerPErouter.
Thiscommandisrequiredtocomplete
theattachmentcircuitconfigurationand
forastaticL2TPv3session
configuration.
(Optional)Specifiesthevaluethatthepeer
PEmustincludeinthecookiefieldof
43/117
27.4.2016.
value[high
value]
incoming(received)L2TPpackets.
Thesizeofthecookiefieldcanbe4or8
bytes.Ifyoudonotenterthiscommand,
nocookievalueisincludedintheheader
ofL2TPpackets.
Ifyouconfigurethecookielengthin
incomingpacketsas8bytes,youmust
specifya4bytehighvalueanda4byte
lowvalue.
Example:
Router(config
l2tpclass)#
l2tpcookie
local454321
ontheCisco12000seriesInternet
routers.
Step7
l2tpcookie
remotesize
lowvalue
[highvalue]
(Optional)Specifiesthevaluethattherouter
includesinthecookiefieldofoutgoing
(sent)L2TPpackets.
Thesizeofthecookiefieldcanbe4or8
bytes.Ifyoudonotenterthiscommand,
nocookievalueisincludedintheheader
ofL2TPpackets.
Ifyouconfigurethecookielengthin
outgoingpacketsas8bytes,youmust
specifya4bytehighvalueanda4byte
lowvalue.
Example:
Router(config
l2tpclass)#
l2tpcookie
remote412345
ontheCisco12000seriesInternet
routers.
Step8
l2tphello
l2tpclassname
Example:
Router(config
l2tpclass)#
l2tphello
l2tpdefaults
(Optional)SpecifiestheL2TPclassnameto
use(seethesection"ConfiguringL2TP
ControlChannelParameters")forcontrol
channelconfigurationparameters,including
theintervaltousebetweenhellokeepalive
messages.
Note Thiscommandassumesthatthereis
nocontrolplanetonegotiatecontrol
channelparametersandthata
controlchannelistobeusedto
providekeepalivesupportthrough
44/117
27.4.2016.
anexchangeofL2TPhello
messages.Bydefault,nohello
messagesaresent.
ConfiguringtheXconnectAttachmentCircuitforATMVPMode
SingleCellRelayoverL2TPv3
TheATMVPModeSingleCellRelayoverL2TPv3featureallowscellscoming
intoapredefinedpermanentvirtualpath(PVP)ontheATMinterfacetobe
transportedoveranL2TPv3pseudowiretoapredefinedPVPontheegress
ATMinterface.Thistaskbindsapermanentvirtualpath(PVP)toanL2TPv3
pseudowireforXconnectservice.
SUMMARYSTEPS
1. enable
4. atmpvpvpi[l2transport]
5. xconnectpeeripaddressvcidpwclasspwclassname
DETAILEDSTEPS
Commandor
Action
Purpose
Step1
enable
Example:
Router>enable
Step2
configure
terminal
Example:
Router#
configure
terminal
Step3
interfacetype
slot/port
Example:
Specifiestheinterfacebytype,slot,andport
number,andentersinterfaceconfiguration
mode.
Router(config)#
interfaceATM
45/117
27.4.2016.
4/1/0
Step4
atmpvpvpi
[l2transport]
SpecifiesthatthePVPisdedicatedto
transportingATMcells.
Example:
Router(config
if)#atmpvp5
l2transport
Step5
Thel2transportkeywordindicatesthat
thePVPisforcellrelay.Onceyouenter
thiscommand,youenterl2transport
PVPconfigurationmode.This
configurationmodeisforLayer2
transportonlyitisnotforterminated
PVPs.
xconnectpeer
ipaddressvcid
pwclasspw
classname
controlchannel.
Example:
Router(config
if)#xconnect
10.0.3.201888
pwclassatm
xconnect
pwclasspwclassnameThe
pseudowireclassconfigurationfrom
whichthedataencapsulationtype
(L2TPv3)willbetaken.Thepwclass
parameterbindstheXconnectstatement
toaspecificpseudowireclass.The
pseudowireclassthenservesasthe
templateconfigurationforallattachment
circuitsboundtoit.
ConfigurationExamplesforLayer2Tunnel
ProtocolVersion3
Thissectionprovidesthefollowingconfigurationexamples:
ConfiguringaStaticL2TPv3SessionforanXconnectEthernetInterface
Example
ConfiguringaNegotiatedL2TPv3SessionforanXconnectVLAN
SubinterfaceExample
ConfiguringaNegotiatedL2TPv3SessionforLocalHDLCSwitching
Example
46/117
27.4.2016.
ConfiguringaPseudowireClassforFragmentationofIPPacketsExample
ConfiguringtheXconnectAttachmentCircuitforATMVPModeSingleCell
RelayoverL2TPv3Example
VerifyingATMVPModeSingleCellRelayoverL2TPv3Configuration
ThefollowingisasampleconfigurationforswitchingaFrameRelayDLCIovera
pseudowire:
pseudowireclassfrxconnect
encapsulationl2tpv3
protocoll2tpv3
iplocalinterfaceLoopback0
sequencingboth
interfaceSerial0/0
encapsulationframerelay
framerelayintftypedce
connectoneSerial0/0100l2transport
xconnect10.0.3.201555pwclassfrxconnect
connecttwoSerial0/0200l2transport
xconnect10.0.3.201666pwclassfrxconnect
Thefollowingisasampleconfigurationforsettingupatrunkconnectionforan
entireserialinterfaceoverapseudowire.Allincomingpacketsareswitchedto
thepseudowireregardlessofcontent.
Notethatwhenyouconfiguretrunkingforaserialinterface,thetrunkconnection
doesnotrequireanencapsulationmethod.Youdonot,therefore,needtoenter
theencapsulationframerelaycommand.Reconfiguringthedefault
encapsulationremovesallXconnectconfigurationsettingsfromtheinterface.
interfaceSerial0/0
xconnect10.0.3.201555pwclassserialxconnect
ThefollowingexampleshowstheMQCcommandsusedonaCisco7500Series
routertoconfigureaCIRguaranteeof256kbpsonDLCI100and512kbpsfor
DLCI200ontheegresssideofaFrameRelayinterfacethatisalsoconfigured
forL2TPv3tunneling:
47/117
27.4.2016.
ipcefdistributed
classmapdlci100
matchfrdlci100
classmapdlci200
matchfrdlci200
policymapdlci
classdlci100
bandwidth256
classdlci200
bandwidth512
interfaceSerial0/0
framerelayinterfacetypedce
servicepolicyoutputdlci
connectoneSerial0/0100l2transport
xconnect10.0.3.201555encapsulationl2tpv3pwclassmqc
connecttwoSerial0/0200l2transport
xconnect10.0.3.201666encapsulationl2tpv3pwclassmqc
ToapplyaQoSpolicyforL2TPv3toaFrameRelayinterfaceonaCisco12000
Series2portChOC3/STM1(DS1/E1)or6portChT3linecard,youmust:
Usethemapclassframerelayclassnamecommandinglobal
configurationmodetoapplyaQoSpolicytoaFrameRelayclassoftraffic.
Usetheframerelayinterfacedclidclinumberswitchedcommand(in
interfaceconfigurationmode)toenterFrameRelayDLCIinterface
configurationmodeandthentheclasscommandtoconfigureaQoSpolicy
foraFrameRelayclassoftrafficonthespecifiedDLCI.Youmustentera
separateseriesoftheseconfigurationcommandstoconfigureQoSforeach
FrameRelayDLCIontheinterface.
Asshowninthefollowingexample,whenyouconfigureQoSforL2TPv3onthe
ingresssideofaCisco12000SeriesFrameRelayinterface,youmustalso
configurethevalueoftheToSbyteusedinIPheadersoftunneledpackets
whenyouconfiguretheL2TPv3pseudowire(seeConfiguringtheL2TPv3
Pseudowire).
ThefollowingexampleshowstheMQCcommandsandToSbyteconfiguration
usedonaCisco12000SeriesroutertoapplyaQoSpolicyforDLCI100onthe
ingresssideofaFrameRelayinterfaceconfiguredforL2TPv3tunneling:
policymapfrtppolicy
classclassdefault
48/117
27.4.2016.
policecir8000bc6000pir32000be4000conformactiontransmitexcee
setfrdetransmitviolateactiondrop
mapclassframerelayfrmap
servicepolicyinputfrtppolicy
interfaceSerial0/1/1:0
framerelayinterfacedlci100switched
classfrmap
connectfrol2tp1Serial0/1/1:0100l2transport
xconnect10.0.3.201666encapsulationl2tpv3pwclassaaa
pseudowireclassaaa
encapsulationl2tpv3
iptosvalue96
ToapplyaQoSpolicyforL2TPv3totheegresssideofaFrameRelayinterface
onaCisco12000Series2portChOC3/STM1(DS1/E1)or6portChT3line
card,youmust:
Usethematchipprecedencecommandinclassmapconfigurationmode
toconfiguretheIPprecedencevalueusedtodeterminetheegressqueue
foreachL2TPv3packetwithaFrameRelaypayload.
Usetherandomdetectcommandinpolicymapclassconfigurationmode
toenableaweightedrandomearlydetection(WRED)droppolicyfora
FrameRelaytrafficclassthathasabandwidthguarantee.Usetherandom
detectprecedencecommandtoconfiguretheWREDandmodifieddeficit
roundrobin(MDRR)parametersforparticularIPPrecedencevalues.
ThenextexampleshowstheMQCcommandsusedonaCisco12000Series
InternetRoutertoapplyaQoSpolicywithWRED/MDRRsettingsforspecifiedIP
PrecedencevaluestoDLCI100ontheegresssideofaFrameRelayinterface
configuredforL2TPv3:
classmapmatchalld2
matchipprecedence2
classmapmatchalld3
matchipprecedence3
policymapo
classd2
bandwidthpercent10
randomdetect
randomdetectprecedence1200packets500packets1
classd3
bandwidthpercent10
randomdetect
49/117
27.4.2016.
randomdetectprecedence11packets2packets1
mapclassframerelayfrmap
servicepolicyoutputo
interfaceSerial0/1/1:0
framerelayinterfacedlci100switched
classfrmap
connectfrol2tp1Serial0/1/1:0100l2transport
xconnect10.0.3.201666encapsulationl2tpv3pwclassaaa
ThefollowingexampleshowshowtoconfigureL2TPv3tunnelingonamultilink
FrameRelaybundleinterfaceonaCisco12000Series2portChOC3/STM1
(DS1/E1)or6portChT3linecard:
framerelayswitching
pseudowireclassmfr
encapsulationl2tpv3
interfacemfr0
framerelayintftypedce
interfaceSerial0/0.1/1:11
encapsulationframerelayMFR0
interfaceSerial0/0.1/1:12
encapsulationframerelayMFR0
connectL2TPoMFRMFR0100l2transport
xconnect10.10.10.103pwclassmfr
ConfiguringaStaticL2TPv3SessionforanXconnectEthernet
InterfaceExample
L2TPv3istheonlyencapsulationmethodthatsupportsamanuallyprovisioned
sessionsetup.Thisexampleshowshowtoconfigureastaticsession
configurationinwhichallcontrolchannelparametersaresetupinadvance.
Thereisnocontrolplaneusedandnonegotiationphasetosetupthecontrol
channel.ThePErouterstartssendingtunneledtrafficassoonastheEthernet
interface(inte0/0)comesup.Thevirtualcircuitidentifier,123,isnotused.The
PEsendsL2TPdatapacketswithsessionID111andcookie12345.Inturn,the
PEexpectstoreceiveL2TPdatapacketswithsessionID222andcookie54321.
l2tpclassl2tpdefaults
50/117
27.4.2016.
retransmitinitialretries30
cookiesize8
pseudowireclassetherpw
encapsulationl2tpv3
protocolnone
interfaceEthernet0/0
xconnect10.0.3.201123encapsulationl2tpv3manualpwclassetherpw
l2tpid222111
l2tpcookielocal454321
l2tpcookieremote412345
l2tphellol2tpdefaults
ConfiguringaNegotiatedL2TPv3SessionforanXconnectVLAN
SubinterfaceExample
ThefollowingisasampleconfigurationofadynamicL2TPv3sessionfora
VLANXconnectinterface.Inthisexample,onlyVLANtrafficwithaVLANIDof5
istunneled.Intheotherdirection,theL2TPv3sessionidentifiedbyavirtual
circuitidentifierof123receivesforwardedframeswhoseVLANIDfieldsare
rewrittentocontainthevalue5.L2TPv3isusedasboththecontrolplane
protocolandthedataencapsulation.
l2tpclassclass1
authentication
passwordsecret
pseudowireclassvlanxconnect
encapsulationl2tpv3
protocoll2tpv3class1
interfaceEthernet0/0.1
encapsulationdot1Q5
xconnect10.0.3.201123pwclassvlanxconnect
ConfiguringaNegotiatedL2TPv3SessionforLocalHDLC
SwitchingExample
ThefollowingisasampleconfigurationofadynamicL2TPv3sessionforlocal
HDLCswitching.Inthisexample,notethatitisnecessarytoconfiguretwo
differentIPaddressesattheendpointsoftheL2TPv3pseudowirebecausethe
virtualcircuitidentifiermustbeuniqueforagivenIPaddress.
interfaceloopback1
ipaddress10.0.0.1255.255.255.255
51/117
27.4.2016.
interfaceloopback2
ipaddress10.0.0.2255.255.255.255
pseudowireclassloopback1
encapsulationl2tpv3
iplocalinterfaceloopback1
pseudowireclassloopback2
encapsulationl2tpv3
iplocalinterfaceloopback2
interfaces0/0
encapsulationhdlc
xconnect10.0.0.1100pwclassloopback2
interfaces0/1
encapsulationhdlc
xconnect10.0.0.2100pwclassloopback1
ConfiguringaPseudowireClassforFragmentationofIPPackets
Example
ThefollowingisasampleconfigurationofapseudowireclassthatwillallowIP
trafficgeneratedfromtheCEroutertobefragmentedbeforeenteringthe
pseudowire:
pseudowireclassclass1
encapsulationl2tpv3
ippmtu
ipdfbitset
ConfiguringtheXconnectAttachmentCircuitforATMVPMode
SingleCellRelayoverL2TPv3Example
ThefollowingconfigurationbindsaPVPtoanXconnectattachmentcircuitto
forwardATMcellsoveranestablishedL2TPv3pseudowire:
pwclassatmxconnect
encapsulationl2tpv3
interfaceATM4/1/0
atmpvp5l2transport
xconnect10.0.3.201888pwclassatmxconnect
TodisplaydetailedinformationaboutcurrentL2TPv3sessionsonarouter,use
theshowl2tunsessionallcommand:
52/117
27.4.2016.
Router#showl2tunnelsessionall
SessionInformationTotaltunnels0sessions1
Sessionid111isup,tunnelid0
Callserialnumberis0
Remotetunnelnameis
Internetaddressis2.0.0.1
Sessionismanuallysignalled
Sessionstateisestablished,timesincechange00:06:05
0Packetssent,0received
0Bytessent,0received
Receivepacketsdropped:
outoforder:0
total:0
Sendpacketsdropped:
exceededsessionMTU:0
total:0
Sessionvcidis123
SessionLayer2circuit,typeisATMVPCCELL,nameisATM3/0/0:100000
CircuitstateisUP
Remotesessionidis222,remotetunnelid0
DFbitoff,ToSreflectdisabled,ToSvalue0,TTLvalue255
Sessioncookieinformation:
localcookie,size8bytes,value0000000000000064
remotecookie,size8bytes,value00000000000000C8
SSSswitchingenabled
Sequencingisoff
TodisplaydetailedinformationtheL2TPcontrolchannelsthataresetupto
otherL2TPenableddevicesforallL2TPsessionsontherouter,usetheshow
l2tuntunnelallcommand.TheL2TPcontrolchannelisusedtonegotiate
capabilities,monitorthehealthofthepeerPErouter,andsetupvarious
componentsofanL2TPv3session.
Router#showl2tunsessionall
Callserialnumberis0
Remotetunnelnameis
53/117
27.4.2016.
outoforder:0
total:0
Sendpacketsdropped:
total:0
Sessionvcidis123
CircuitstateisUP
SSSswitchingenabled
Sequencingisoff
VerifyingATMVPModeSingleCellRelayoverL2TPv3
Configuration
ToverifytheconfigurationofaPVP,usetheshowatmvpcommandinEXEC
mode.
Router#showatmvp5
ATM4/1/0VPI:5,CellRelay,PeakRate:155000,CesRate:0,DataVCs:0,
CesVCs:0,Status:ACTIVE
VCDVCITypeInPktsOutPktsAAL/EncapStatus
83PVC00F4OAMACTIVE
94PVC00F4OAMACTIVE
TotalInPkts:0,TotalOutPkts:0,TotalInFast:0,TotalOutFast:0,
TotalBroadcasts:0
ForadditionalinformationrelatedtoL2TPv3,refertothefollowingreferences:
RelatedDocuments
Standards
MIBs
RFCs
TechnicalAssistance
54/117
27.4.2016.
RelatedDocuments
RelatedTopic
DocumentTitle
FurtherinformationaboutL2TPv3
Layer2TunnelingProtocol
Version3TechnicalOverview
InformationaboutL2TP
Layer2TunnelProtocol
Layer2TunnelingProtocol:A
FeatureinCiscoIOSSoftware
ConfiguringtheCEFfeature
"CiscoExpressForwarding"
chapterintheCiscoIOS
SwitchingConfigurationGuide,
Release12.0
FurtherinformationaboutMTU
discoveryandpacketfragmentation
MTUTuningforL2TP
AdditionalVPNcommands:complete
commandsyntax,commandmode,
defaults,usageguidelinesand
examples.
CiscoIOSRelease12.0Dial
SolutionsCommandReference
AdditionalFrameRelaycommands:
completecommandsyntax,command
mode,defaults,usageguidelinesand
examples.
CiscoIOSRelease12.0Wide
AreaNetworkingCommand
Reference
InformationaboutUTI
UniversalTransportInterface
(UTI)
Standards
Standards
Title
draftietfl2tpextl2tpbase
03.txt
LayerTwoTunnelingProtocol(Version
3)'L2TPv3'
55/117
27.4.2016.
MIBs
MIBs
MIBsLink
ToobtainlistsofsupportedMIBsbyplatformand
CiscoIOSrelease,andtodownloadMIBmodules,
gototheCiscoMIBwebsiteonCisco.comatthe
followingURL:
VPDNMIBMIB
supportfor
L2TPv3isbased
ontheVPDNMIB
http://www.cisco.com/public/sw
center/netmgmt/cmtk/mibs.shtml
TolocateanddownloadMIBsforselectedplatforms,CiscoIOSreleases,and
featuresets,useCiscoMIBLocatorfoundatthefollowingURL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
IfCiscoMIBLocatordoesnotsupporttheMIBinformationthatyouneed,you
canalsoobtainalistofsupportedMIBsanddownloadMIBsfromtheCisco
MIBspageatthefollowingURL:
http://www.cisco.com/public/swcenter/netmgmt/cmtk/mibs.shtml
ToaccessCiscoMIBLocator,youmusthaveanaccountonCisco.com.Ifyou
haveforgottenorlostyouraccountinformation,sendablankemailtocco
locksmith@cisco.com.Anautomaticcheckwillverifythatyouremailaddressis
registeredwithCisco.com.Ifthecheckissuccessful,accountdetailswithanew
randompasswordwillbeemailedtoyou.Qualifieduserscanestablishan
accountonCisco.combyfollowingthedirectionsfoundatthisURL:
http://www.cisco.com/register
RFCs
RFCs1
Title
RFC2661
LayerTwoTunnelingProtocol"L2TP"
NotallsupportedRFCsarelisted.
56/117
27.4.2016.
TechnicalAssistance
Description
Link
TechnicalAssistance
Center(TAC)home
page,containing
30,000pagesof
searchabletechnical
content,including
linkstoproducts,
technologies,
solutions,technical
tips,tools,andlots
more.Registered
Cisco.comuserscan
loginfromthispage
toaccessevenmore
content.
http://www.cisco.com/public/support/tac/home.shtml
CommandReference
Thissectiondocumentsnewandmodifiedcommands.Allothercommands
usedwiththisfeaturearedocumentedintheCiscoIOSRelease12.0command
referencepublications.
atmpvp
authentication
debugacircuit
debugvpdn
debugxconnect
encapsulationl2tpv3
hello
hidden
hostname
ipdfbitset
iplocalinterface
ippmtu
57/117
27.4.2016.
ipprotocol
iptos
ipttl
l2tpclass
l2tpcookielocal
l2tpcookieremote
l2tphello
l2tpid
password
protocol
pseudowireclass
receivewindow
retransmit
sequencing
showl2tunsession
showl2tuntunnel
timeoutsetup
xconnect
atmpvp
Tocreateapermanentvirtualpath(PVP)usedtomultiplex(orbundle)oneor
morevirtualcircuits(VCs),usetheatmpvpcommandininterfaceconfiguration
mode.ToremoveaPVP,usethenoformofthiscommand.
atmpvpvpi[peakrate][l2transport]
noatmpvpvpi
SyntaxDescription
vpi
ATMnetworkvirtualpathidentifier(VPI)oftheVCtomultiplex
onthepermanentvirtualpath.Therangeisfrom0to255.
TheVPIisan8bitfieldintheheaderoftheATMcell.TheVPI
valueisuniqueonlyonasinglelink,notthroughouttheATM
networkbecauseithaslocalsignificanceonly.TheVPIvalue
mustmatchthatoftheswitch.
Thenumberspecifiedforthevpiargumentmustnotalready
exist.Ifthenumberspecifiedforthevpiargumentisalready
beingusedbyanexistingVC,thiscommandisrejected.
peakrate
(Optional)MaximumrateinkbpsatwhichthePVPcansend
data.Therangeis84kbpstolinerate.Thedefaultistheline
58/117
27.4.2016.
rate.
l2transport
(Optional)SpecifiesthatthePVPisfortheAnyTransportover
MPLS(AToM)ATMcellrelayfeatureortheATMCellRelay
overL2TPv3feature.
Defaults
PVPisnotconfigured.
Thedefaultpeakrateisthelinerate.
CommandModes
Interfaceconfiguration
CommandHistory
Release
Modification
11.1
Thiscommandwasintroduced.
12.0(25)S Thiscommandwasupdatedtoincludethel2transport
keyword.
UsageGuidelines
ThiscommandiscommonlyusedtocreateaPVPthatisusedinmultiplexcircuit
emulationservice(CES)anddataVCs.
TheATMCESportadaptersupportsmultiplexingofoneormoreVCsovera
virtualpaththatisshapedataconstantbandwidth.Forexample,youcanbuya
virtualpathservicefromanATMserviceproviderandmultiplexboththeCES
anddatatrafficoverthevirtualpath.
AllsubsequentlycreatedVCswithavpiargumentmatchingthevpivalue
specifiedwiththeatmpvpcommandaremultiplexedontothisPVP.ThisPVP
connectionisanATMconnectionwhereswitchingisperformedontheVPIfield
ofthecellonly.APVPiscreatedandleftupindefinitely.AllVCsthatare
multiplexedoveraPVPshareandarecontrolledbythetrafficparameters
59/117
27.4.2016.
associatedwiththePVP.
ChangingthepeakrateargumentcausestheATMCESportadaptertogo
downandthenbackup.
WhenyoucreateaPVP,twoVCsarecreated(VCI3and4)bydefault.These
VCsarecreatedforVPendtoendloopbackandsegmentloopbackoperation,
administration,andmaintenance(OAM)support.
Whenyouusethel2transportkeywordwiththeatmpvpcommand,the
commandmodebecomesthel2transportPVPsubmode.Youmustissuethe
l2transportkeywordtoconfiguretheATMcellrelayoverMPLSfeatureinport
modeortoconfiguretheATMcellrelayoverL2TPv3feature.
ToverifytheconfigurationofaPVP,usetheshowatmvpcommandinEXEC
mode.
Examples
Thefollowingexamplecreatesapermanentvirtualpathwithapeakrateof
2000kbps.ThesubsequentVCscreatedaremultiplexedontothisvirtualpath.
interfaceatm6/0
atmpvp12000
atmpvc13113aal5snap
exit
interfacecbr6/1
cescircuit0
cespvc9interfaceatm6/0vpi1vci100
exit
ThefollowingexampleconfiguresATMCellRelayoverMPLSinportmode:
interfaceatm5/0
atmpvp1l2transport
xconnect10.0.0.1123encapsulationmpls
ThefollowingexampleconfiguresATMCellRelayoverL2TPv3:
pwclassatmxconnect
encapsulationl2tpv3
interfaceatm4/1/0
atmpvp5l2transport
xconnect10.0.3.201888pwclassatmxconnect
RelatedCommands
60/117
27.4.2016.
Command
Description
showatm
vp
DisplaysthestatisticsforallVPsonaninterfaceorfora
specificVP.
authentication
ToenableLayer2TunnelProtocolVersion3(L2TPv3)authentication,usethe
authenticationcommandinL2TPclassconfigurationmode.TodisableL2TPv3
authentication,usethenoformofthiscommand.
authentication
noauthentication
SyntaxDescription
Thiscommandhasnoargumentsorkeywords.
Defaults
L2TPv3authenticationisdisabled.
CommandModes
L2TPclassconfiguration
CommandHistory
Release
Modification
12.0(23)S Thiscommandwasintroduced.
UsageGuidelines
UsetheauthenticationcommandtoenableL2TPv3authentication.
Examples
ThefollowingexampleenablesauthenticationinL2TPv3pseudowires
configuredusingtheL2TPclassconfigurationnamedl2tpclass1:
Router(config)#l2tpclassl2tpclass1
61/117
27.4.2016.
Router(configl2tpclass)#authentication
RelatedCommands
Command
Description
l2tpclass
CreatesatemplateofL2TPcontrolplaneconfiguration
settingsthatcanbeinheritedbydifferentpseudowireclasses
andentersL2TPclassconfigurationmode.
password
ConfiguresthepasswordusedbyaPErouterforL2TPv3
authentication.
debugacircuit
Totroubleshooteventsandfailuresrelatedtoanattachmentcircuit,usethe
debugacircuitcommandinprivilegedEXECmode.Todisablethedebug
acircuitcommand,usethenoformofthiscommand.
debugacircuit{error|event}
nodebugacircuit{error|event}
SyntaxDescription
error
Displayserrorsthatoccurinattachmentcircuits.
event
Displayseventsthatoccurinattachmentcircuits.
CommandModes
PrivilegedEXEC
CommandHistory
Release
Modification
62/117
27.4.2016.
UsageGuidelines
Usethedebugacircuitcommandtoidentifyprovisioningevents,setupfa
events,andconfigurationfailures.
Examples
Thefollowingexampleshowsoutputfromthedebugacircuitcommandforan
XconnectsessiononanEthernetinterface:
Router#debugacircuit
23:28:35:ACLIB[10.0.3.201,5]:SWACinterfaceUPforEthernetinterfa
23:28:35:ACLIB[10.0.3.201,5]:pthru_intf_handle_circuit_up()calling
23:28:35:ACLIB[10.0.3.201,5]:SettingnewACstatetoAcConnecting
23:28:35:ACLIB[10.0.3.201,5]:SWACinterfaceUPforEthernetinterfa
23:28:35:ACLIB[10.0.3.201,5]:pthru_intf_handle_circuit_up()ignoring
connectedorconnecting.
23:28:35:ACMGR:Receive<CircuitUp>msg
23:28:35:Et2/1ACMGR:circuitupevent,SIPstatechgdowntoconnectin
servicerequest
23:28:35:Et2/1ACMGR:Sentasipservicerequest
23:28:37:%LINK3UPDOWN:InterfaceEthernet2/1,changedstatetoup
23:28:38:%LINEPROTO5UPDOWN:LineprotocolonInterfaceEthernet2/1,c
23:28:53:Et2/1ACMGR:RcvSIPmsg:respconnectforwarded,hdlD6000002
23:28:53:Et2/1ACMGR:serviceconnectedevent,SIPstatechgconnecting
actionisrespondforwarded
23:28:53:ACLIB:pthru_intf_responsehdlisD6000002,responseis1
23:28:53:ACLIB[10.0.3.201,5]:SettingnewACstatetoAcConnected
RelatedCommands
Command
Description
debug
vpdn
DisplayserrorsandeventsrelatingtoL2TPconfigurationand
thesurroundingLayer2tunnelinginfrastructure.
63/117
27.4.2016.
debug
xconnect
DisplayserrorsandeventsrelatedtoanXconnect
configuration.
debugvpdn
TotroubleshootLayer2TunnelProtocolVersion3(L2TPv3)andthe
surroundingLayer2tunnelinginfrastructure,usethedebugvpdncommandin
privilegedEXECmode.Todisablethedebugvpdncommand,usethenoform
ofthiscommand.
debugvpdn{error|event|l2xerrors|l2xevents|l2xpackets|packet|
packetdetail|packeterrors}
nodebugvpdn{error|event|l2xerrors|l2xevents|l2xpackets|packet|
packetdetail|packeterrors}
SyntaxDescription
error
Displayserrorsthatoccurinprotocolindependentconditions.
event
Displayseventsresultingfromprotocolindependent
conditions.
l2xerrors
Displayserrorsthatoccurinprotocolspecificconditions.
l2x
events
Displayseventsresultingfromprotocolspecificconditions.
l2x
packets
Displaysdetailedinformationaboutcontrolpacketsinprotocol
specificconditions.
packet
DisplaysinformationabouthighlevelLayer2controlpackets.
packet
detail
Displaysdetailedpacketinformation,includingpacketdumps.
packet
errors
Displayserrorsthatoccurinpacketprocessing.
64/117
27.4.2016.
CommandModes
PrivilegedEXEC
CommandHistory
Release
Modification
UsageGuidelines
Notethatthedebugvpdnpacketanddebugvpdnpacketdetailcommands
generateseveraldebugoperationsperpacket.DependingontheL2TPtraffic
pattern,thesecommandsmaycausetheCPUloadtoincreasetoahighlevel
thatimpactsperformance.
Examples
Thefollowingexampleshowsoutputfromthedebugvpdncommandforan
Router#debugvpdn
23:31:18:L2X:l2tunsession[1669204400],event[clientrequest],olds
state[open]
23:31:18:L2X:L2TP:ReceivedL2TUNmessage<Connect>
23:31:18:Tnl/Sn58458/28568L2TP:Sessionstatechangefromidletowai
23:31:18:Tnl/Sn58458/28568L2TP:Createsession
23:31:18:Tnl58458L2TP:SMStateidle
23:31:18:Tnl58458L2TP:OSCCRQ
23:31:18:Tnl58458L2TP:Controlchannelretransmitdelaysetto1seco
23:31:18:Tnl58458L2TP:Tunnelstatechangefromidletowaitctlrepl
23:31:18:Tnl58458L2TP:SMStatewaitctlreply
23:31:18:Tnl58458L2TP:ISCCRPfromrouter
23:31:18:Tnl58458L2TP:Tunnelstatechangefromwaitctlreplytoest
23:31:18:Tnl58458L2TP:OSCCCNtoroutertnlid8012
23:31:18:Tnl58458L2TP:SMStateestablished
65/117
27.4.2016.
23:31:18:Tnl/Sn58458/28568L2TP:OICRQtorouter8012/0
23:31:18:Tnl/Sn58458/28568L2TP:Sessionstatechangefromwaitfortu
23:31:20:%LINK3UPDOWN:InterfaceEthernet2/1,changedstatetoup
23:31:21:%LINEPROTO5UPDOWN:LineprotocolonInterfaceEthernet2/1,
up
23:31:25:L2X:SendingL2TUNmessage<ConnectOK>
23:31:25:Tnl/Sn58458/28568L2TP:OICCNtorouter8012/35149
23:31:25:Tnl/Sn58458/28568L2TP:Sessionstatechangefromwaitreply
23:31:25:L2X:l2tunsession[1669204400],event[serverresponse],old
state[open]
RelatedCommands
Command
Description
debugacircuit
Displayseventsandfailuresrelatedtoattachment
circuits.
debug
xconnect
DisplayserrorsandeventsrelatedtoanXconnect
configuration.
debugxconnect
TodebugaproblemrelatedtotheXconnectconfiguration,usethedebug
xconnectcommandinprivilegedEXECmode.Todisablethedebugxconnect
command,usethenoformofthiscommand.
debugxconnect{error|event}
nodebugxconnect{error|event}
SyntaxDescription
error
DisplayserrorsrelatedtoanXconnectconfiguration.
66/117
27.4.2016.
event
DisplayseventsrelatedtoanXconnectconfigurationprocessing.
CommandModes
PrivilegedEXEC
CommandHistory
Release
Modification
UsageGuidelines
UsethiscommandtodisplaydebugginginformationaboutXconnectsessions.
Examples
Thefollowingexampleshowsoutputfromthedebugxconnectcommandfora
Router#debugxconnect
00:01:16:XCAUTH[Et2/1,5]:Event:startxconnectauthorization,state
toAUTHORIZING
00:01:16:XCAUTH[Et2/1,5]:Event:foundxconnectauthorization,state
AUTHORIZINGtoDONE
00:01:16:XCAUTH[Et2/1,5]:Event:freexconnectauthorizationrequest
fromDONEtoEND
RelatedCommands
Command
Description
debug
acircuit
Displayseventsandfailuresrelatedtoattachmentcircuits.
67/117
27.4.2016.
debug
vpdn
DisplayserrorsandeventsrelatingtoL2TPconfigurationand
thesurroundingLayer2tunnelinginfrastructure.
encapsulationl2tpv3
TospecifythatLayer2TunnelProtocolVersion3(L2TPv3)isusedasthedata
encapsulationmethodfortunnelingIPtrafficoverthepseudowire,usethe
encapsulationl2tpv3commandinpseudowireclassorVCclassconfiguration
mode.ToremoveL2TPv3astheencapsulationmethod,usetheno
pseudowireclasscommand(seetheUsageGuidelinesformoreinformation).
encapsulationl2tpv3
nopseudowireclass
SyntaxDescription
CommandDefault
Noencapsulationmethodisspecified.
CommandModes
Pseudowireclassconfiguration
VCclassconfiguration
CommandHistory
Release
Modification
12.0(23)S
Thiscommandwasintroduced.
12.3(2)T
ThiscommandwasintegratedintoCiscoIOS
Release12.3(2)T.
12.2(25)S
ThiscommandwasintegratedintoCiscoIOSRelease
12.2(25)S.
12.2(27)SBC SupportforthiscommandwasintegratedintoCiscoIOS
Release12.2(27)SBC.
68/117
27.4.2016.
UsageGuidelines
Thiscommandmustbeconfiguredifthepseudowireclasswillbereferenced
fromanXconnectconfiguredtoforwardL2TPv3traffic.
Onceyouspecifytheencapsulationl2tpv3command,youcannotremoveit
usingthenoencapsulationl2tpv3command.Norcanyouchangethe
command'ssettingusingtheencapsulationmplscommand.Thosemethods
resultinthefollowingerrormessage:
Encapsulationchangesarenotallowedonanexistingpwclass.
Toremovethecommand,youmustdeletethepseudowirewiththeno
pseudowireclasscommand.Tochangethetypeofencapsulation,removethe
pseudowirewiththenopseudowireclasscommandandreestablishthe
pseudowireandspecifythenewencapsulationtype.
Examples
ThefollowingexampleshowshowtoconfigureL2TPv3asthedata
encapsulationmethodforthepseudowireclassnamedetherpw:
Router(config)#pseudowireclassetherpw
Router(configpw)#encapsulationl2tpv3
ThefollowingexampleconfiguresATMAAL5overL2TPv3inVCclass
configurationmode:
vcclassatmaal5class
encapsulationaal5
RelatedCommands
Command
Description
encapsulation
mpls
ConfiguresMPLSasthedataencapsulationmethodover
AToMenabledIP/MPLSnetworks.
pseudowire
class
SpecifiesthenameofanL2TPpseudowireclassand
enterspseudowireclassconfigurationmode.
hello
69/117
27.4.2016.
ToconfiguretheintervalusedtoexchangehellokeepalivepacketsinaLayer2
TunnelProtocolVersion3(L2TPv3)controlchannel,usethehellocommandin
L2TPclassconfigurationmode.Todisablethesendingofhellokeepalive
packets,usethenoformofthiscommand.
hellointerval
nohellointerval
SyntaxDescription
interval Numberofsecondsaprovideredge(PE)routeratoneendofan
L2TPv3controlchannelwaitsbeforesendingahellokeepalive
packettoitspeerPErouter.Thevalidvaluesrangefrom0to
1000seconds.Thedefaultvalueis60seconds.
Defaults
60seconds
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
YoucanconfiguredifferentvalueswiththehellocommandonthePErouterat
eachendofanL2TPv3controlchannel.
Examples
Thefollowingexamplesetsanintervalof120secondsbetweenthesendingof
hellokeepalivemessagesinL2TPv3pseudowiresconfiguredusingtheL2TP
classconfigurationnamedl2tpclass1:
70/117
27.4.2016.
Router(configl2tpclass)#hello120
RelatedCommands
Command
Description
l2tpclass
hidden
Tohidetheattributevaluepair(AVP)valuesinLayer2TunnelingProtocol
(L2TP)controlmessages,usethehiddencommandinL2TPclass
configurationmode.TounhideAVPs,usethenoformofthiscommand.
hidden
nohidden
SyntaxDescription
Defaults
L2TPAVPhidingisdisabled.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
Usethehiddencommandtoprovideadditionalsecurityfortheexchangeof
controlmessagesbetweenprovideredgeroutersinaLayer2TunnelProtocol
Version3(L2TPv3)controlchannel.Becauseusernameandpassword
71/117
27.4.2016.
informationisexchangedbetweendevicesincleartext,itisusefultoencrypt
L2TPAVPvalueswiththehiddencommand.
Examples
ThefollowingexampleenablesAVPhidingandencryptsAVPsincontrol
messagesinL2TPv3pseudowiresconfiguredusingtheL2TPclass
configurationnamedl2tpclass1:
Router(configl2tpclass)#hidden
RelatedCommands
Command
Description
l2tpclass
hostname
ToconfigurethehostnamethattherouterwillusetoidentifyitselfduringLayer
2TunnelProtocolVersion3(L2TPv3)authentication,usethehostname
commandinL2TPclassconfigurationmode.Toremovethehostname,usethe
noformofthiscommand.
hostnamename
nohostnamename
SyntaxDescription
name
Nameusedtoidentifytherouterduringauthentication.
Defaults
NohostnameisspecifiedforL2TPv3authentication.
CommandModes
72/117
27.4.2016.
CommandHistory
Release
Modification
UsageGuidelines
Ifyoudonotusethehostnamecommand,thehostnameoftherouterisused
forL2TPv3authentication.
Examples
Thefollowingexampleconfiguresthehostnameyb2foraprovideredgerouter
usedatoneendofanL2TPv3controlchannelinanL2TPv3pseudowire
configuredusingtheL2TPclassconfigurationnamedl2tpclass1:
Router(configl2tpclass)#hostnameyb2
RelatedCommands
Command
Description
iplocal
interface
ConfigurestheIPaddressofthePErouterinterfacetobe
usedasthesourceIPaddressforsendingtunneledpackets.
l2tpclass
ipdfbitset
ToenabletheDon'tFragment(DF)bitintheouterLayer2TunnelProtocol
Version3(L2TPv3)header,usetheipdfbitsetcommandinpseudowireclass
configurationmode.TodisabletheDFbitsetting,usethenoformofthis
command.
ipdfbitset
noipdfbitset
73/117
27.4.2016.
SyntaxDescription
Defaults
ThedefaultvalueisDFbitoff,exceptforCisco12000seriesInternetrouters,
whichhavethiscommandenabledbydefault.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
UsethiscommandtosettheDFbitonif,forperformancereasons,youdonot
wanttunneledpacketreassemblytobeperformedontherouter.
NoteOnCisco12000seriesInternetrouters,thenoipdfbitsetcommandis
onlysupportedinIOSRelease12.0(24)Sandlaterreleases.
Examples
ThefollowingexampleshowshowtoenabletheDFbitintheouterL2TPv3
headerinpseudowirescreatedfromthepseudowireclassnamedetherpw:
Router(configpw)#ipdfbitset
RelatedCommands
Command
Description
ippmtu
EnablesthediscoveryofaPMTUforL2TPv3traffic.
pseudowire
class
74/117
27.4.2016.
iplocalinterface
ToconfiguretheIPaddressoftheprovideredgerouterinterfacetobeusedas
thesourceIPaddressforsendingtunneledpackets,usetheiplocalinterface
commandinpseudowireclassconfigurationmode.ToremovetheIPaddress,
usethenoformofthiscommand.
iplocalinterfaceinterfacename
noiplocalinterfaceinterfacename
SyntaxDescription
interface
name
NameofthePEinterfacewhoseIPaddressisusedasthe
sourceIPaddressforsendingtunneledpacketsoveranLayer
2TunnelProtocolVersion3(L2TPv3)pseudowire.
Defaults
Noipaddressisconfigured.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
Usethesamelocalinterfacenameforallpseudowireclassesconfigured
betweenapairofPErouters.Itishighlyrecommendedthataloopbackinterface
isconfiguredwiththiscommand.Ifyoudonotconfigurealoopbackinterface,
therouterwillchoosethe"bestavailablelocaladdress,"whichcouldbeanyIP
addressconfiguredonacorefacinginterface.Thisconfigurationcouldprevent
75/117
27.4.2016.
acontrolchannelfrombeingestablished.
Theiplocalinterfacecommandmustbeconfiguredforpseudowireclass
configurationsusingL2TPv3asthedataencapsulationmethod.
NoteOnCisco12000seriesInternetrouters,theinterfaceconfiguredwiththe
iplocalinterfacecommandmustbealoopbackinterface.
OntheCisco10720InternetRouter,itishighlyrecommendedthatyou
configurealoopbackinterfaceastheIPlocalinterface.ALANinterface
isalsosupportedastheIPlocalinterface.MultipleL2TPv3tunnel
sessionscanexistbetweenCisco10720InternetroutersondifferentIP
LANs.
Examples
ThefollowingexampleshowshowtoconfiguretheIPaddressofthelocal
Ethernetinterfacenamede0/0asthesourceIPaddressforsendingEthernet
packetsthroughanL2TPv3session:
Router(configpw)#iplocalinterfacee0/0
RelatedCommands
Command
Description
pseudowire
class
ippmtu
Toenablethediscoveryofapathmaximumtransmissionunit(PMTU)forLayer
2TunnelProtocolVersion3(L2TPv3)traffic,usetheippmtucommandin
pseudowireclassconfigurationmode.TodisablePMTUdiscovery,usetheno
formofthiscommand.
ippmtu
nopmtu
SyntaxDescription
Defaults
76/117
27.4.2016.
PathMTUdiscoveryisdisabled.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
TheippmtucommandenablestheprocessingofInternetControlMessage
Protocol(ICMP)unreachablemessagesthatindicatefragmentationerrorsinthe
IPbackbonenetworkcarryingthetunneledtraffic.TheMTUoftheL2TPv3
sessionisupdatedaccordingtotheMTUinformationcontainedintheICMP
unreachablemessage.
TheippmtucommandalsoenablesMTUcheckingforIPpacketsthataresent
intoanL2TPv3sessionwiththeDon'tFragment(DF)bitset.IfanIPpacketis
largerthantheMTUofthetunnel,thepacketisdroppedandanICMP
unreachablemessageissent.IfanIPpacketissmallerthantheMTUofthe
tunnel,theDFbitinthepacketheaderisreflectedfromtheinnerIPheaderto
thetunnelheader.
Examples
ThefollowingexampleshowshowtoenablethediscoveryofthepathMTUfor
pseudowirescreatedfromthepseudowireclassnamedetherpw:
Router(configpw)#ippmtu
RelatedCommands
Command
Description
ipdfbitset
EnablestheDFbitintheouterL2TPv3tunnelheader.
pseudowire
class
77/117
27.4.2016.
ipprotocol
ToconfiguretheLayer2TunnelProtocol(L2TP)orUniversalTunnelInterface
(UTI)astheIPprotocolusedfortunnelingpacketsinanL2TPVersion3
(L2TPv3)pseudowire,usetheipprotocolcommandinpseudowireclass
configurationmode.ToremovetheIPprotocolconfiguration,usethenoformof
thiscommand.
ipprotocol{l2tp|uti|protocolnumber}
noipprotocol{l2tp|uti|protocolnumber}
SyntaxDescription
l2tp
ConfiguresL2TPastheIPprotocolusedtotunnelpacketsinan
L2TPv3pseudowire.
uti
ConfiguresUTIastheIPprotocolusedtotunnelpacketsinan
L2TPv3pseudowire,andallowsarouterrunningL2TPv3to
interoperatewithapeerrunningUTI.
protocol
number
TheprotocolnumberofthedesiredIPprotocol.Theprotocol
numberforL2TPv3is115.TheprotocolnumberforUTIis120.
Defaults
ThedefaultIPprotocolisL2TP.
CommandModes
CommandHistory
Release
Modification
78/117
27.4.2016.
UsageGuidelines
Usetheipprotocolcommandtoensurebackwardcompatibilitywithrouters
runningUTI.ThiscommandallowsyoutoconfigureanL2TPv3pseudowire
betweenarouterrunningL2TPv3andapeerrouterrunningUTI.
NoteYoucanusetheipprotocolcommandonlyifyouhavealreadyentered
theencapsulationl2tpv3command.
ToconfigureL2TPastheIPprotocolusedtotunnelpacketsinanL2TPv3
pseudowire,youmayenter115,theIPprotocolnumberassignedtoL2TPv3,
insteadofl2tpintheipprotocolcommand.
ToconfigureUTIastheIPprotocolusedtotunnelpacketsinanL2TPv3
pseudowire,youmayenter120,theIPprotocolnumberassignedtoUTI,
insteadofutiintheipprotocolcommand.
NoteInteroperabilityinanL2TPv3controlchannelbetweenarouterrunning
UTIandarouterconfiguredforL2TPv3encapsulationissupportedonly
ifyoudisablesignalingusingtheprotocolnonecommand.
Examples
ThefollowingexampleshowshowtoconfigureUTIastheIPprotocolusedto
tunnelpacketsinanL2TPv3pseudowirecreatedfromthepseudowireclass
namedetherpw:
Router(configpw)#encapsulationl2tpv3
Router(configpw)#ipprotocoluti
RelatedCommands
Command
Description
encapsulation
l2tpv3
ConfiguresL2TPv3asthedataencapsulationmethod
usedtotunnelIPtraffic.
pseudowire
class
iptos
79/117
27.4.2016.
ToconfiguretheTypeofService(ToS)byteintheheaderofLayer2Tunnel
ProtocolVersion3(L2TPv3)tunneledpackets,usetheiptoscommandin
pseudowireclassconfigurationmode.TodisableaconfiguredToSvalueorIP
ToSreflection,usethenoformofthiscommand.
iptos{valuevalue|reflect}
notos{valuevalue|reflect}
SyntaxDescription
value
value
SetsthevalueoftheToSbyteforIPpacketsinanL2TPv3
session.Validvaluesrangefrom0to255.Thedefaultvalueis0.
reflect
SetsthevalueoftheToSbyteforIPpacketsinanL2TPv3
sessiontobereflectedfromtheinnerIPheader.
Defaults
ThedefaultToSvalueis0.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
TheiptoscommandallowsyoutomanuallyconfigurethevalueoftheToSbyte
usedintheheadersofL2TPv3tunneledpacketsortohavetheToSvalue
reflectedfromtheIPheaderoftheencapsulatedpacket.
NoteThereflectoptionisnotsupportedontheCisco10720andCisco12000
seriesInternetrouters.
80/117
27.4.2016.
NoteIPToSbytereflectionfunctionsonlyiftrafficinanL2TPv3sessioncarries
IPpacketsasitspayload.
Inaddition,youcanconfigurebothIPToSreflectionandaToSprioritylevel
(from0to255)forapseudowireclass.Inthiscase,theToSvalueinthetunnel
headerdefaultstothevalueyouspecifywiththeiptosvaluevaluecommand.
IPpacketsreceivedontheLayer2interfaceandencapsulatedintotheL2TPv3
sessionhavetheirToSbytereflectedintotheouterIPsession,overridingthe
defaultvalueconfiguredwiththeiptosvaluevaluecommand.
Examples
ThefollowingexampleshowshowtoconfiguretheToSbyteintheheadersof
tunneledpacketsinL2TPv3tunnelscreatedfromthepseudowireclassnamed
etherpwtobereflectedfromtheToSvalueintheheaderofeachencapsulated
IPpacket:
Router(configpw)#iptosreflect
RelatedCommands
Command
Description
pseudowire
class
ipttl
Toconfigurethetimetolive(TTL)byteintheIPheadersofLayer2Tunnel
ProtocolVersion3(L2TPv3)tunneledpackets,usetheipttlcommandin
pseudowireclassconfigurationmode.ToremovetheconfiguredTTLvalue,use
thenoformofthiscommand.
ipttlvalue
noipttlvalue
SyntaxDescription
value
ValueoftheTTLbyteintheIPheadersofL2TPv3tunneled
packets.Thevalidvaluesrangefrom1to255.Thedefaultvalueis
255.
81/117
27.4.2016.
Defaults
ThedefaultvalueoftheTTLbyteis255.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
UsethiscommandtosettheDon'tFragment(DF)bitonif,forperformance
reasons,youdonotwanttunneledpacketreassemblytobeperformedonthe
router.
Examples
ThefollowingexampleshowshowtosettheTTLbyteto100intheIPheaderof
L2TPv3tunneledpacketsinpseudowirescreatedfromthepseudowireclass
namedetherpw:
Router(configpw)#ipttl100
RelatedCommands
Command
Description
pseudowire
class
l2tpclass
82/117
27.4.2016.
TocreateatemplateofLayer2TunnelProtocol(L2TP)controlplane
configurationsettingsthatcanbeinheritedbydifferentpseudowireclassesand
toenterL2TPclassconfigurationmode,usethel2tpclasscommandinglobal
configurationmode.
l2tpclass[l2tpclassname]
SyntaxDescription
l2tp
class
name
(Optional)NameoftheL2TPclass.Thel2tpclassnameargument
mustbespecifiedifyouwanttoconfiguremultiplesetsofL2TP
controlparameters.
Defaults
NoL2TPclassesaredefined.
CommandModes
Globalconfiguration
CommandHistory
Release
Modification
UsageGuidelines
Thel2tpclassl2tpclassnamecommandallowsyoutoconfigureanL2TP
classtemplatethatconsistsofconfigurationsettingsusedbydifferent
pseudowireclasses.AnL2TPclassincludesthefollowingconfigurationsettings:
HostnameoflocalrouterusedduringL2TPv3authentication
Authenticationenabled
Timeintervalusedtoexchangehellopackets
Passwordusedforcontrolchannelauthentication
Packetsizeofreceivewindow
Retransmissionsettingsforcontrolpackets
Timeallowedtosetupacontrolchannel
83/117
27.4.2016.
Thel2tpclasscommandentersL2TPclassconfigurationmode,whereL2TP
controlplaneparametersareconfigured.
YoumustusethesameL2TPclassinthepseudowireconfigurationatbothends
ofanL2TPv3controlchannel.
Examples
ThefollowingexampleshowshowtoenterL2TPclassconfigurationmodeto
createanL2TPclassconfigurationtemplatefortheclassnamedetherpw:
Router(config)#l2tpclassetherpw
RelatedCommands
Command
Description
protocol
l2tpv3
SpecifiesthatL2TPv3isthesignalingprotocoltobeusedto
managethepseudowirescreatedfromapseudowireclass
foradynamicL2TPv3session,andthatcontrolplane
configurationsettingsaretobetakenfromthespecified
L2TPclass
pseudowire
class
xconnect
BindsanattachmentcircuittoanL2TPv3pseudowirefor
Xconnectserviceandentersxconnectconfigurationmode.
l2tpcookielocal
ToconfigurethesizeofthecookiefieldusedintheLayer2TunnelProtocol
Version3(L2TPv3)headersofincomingpacketsreceivedfromtheremote
provideredge(PE)peerrouter,usethel2tpcookielocalcommandin
xconnectconfigurationmode.Toremovetheconfiguredcookiefield
parameters,usethenoformofthiscommand.
l2tpcookielocalsizelowvalue[highvalue]
nol2tpcookielocalsizelowvalue[highvalue]
SyntaxDescription
size
ThesizeofthecookiefieldinL2TPv3headers.Thevalidvaluesare
84/117
27.4.2016.
0,4,and8.
low
value
Thevalueofthelower4bytesofthecookiefield.
high
value
(Optional)Thevalueoftheupper4bytesofthecookiefield.For8
bytecookiefields,youmustenterthevaluefortheupper4bytesof
thecookiefield.
Defaults
NocookievalueisincludedintheheaderofL2TPpackets.
CommandModes
Xconnectconfigurationmode
CommandHistory
Release
Modification
UsageGuidelines
Thel2tpcookielocalcommandspecifiesthevaluesthatthepeerPErouter
includesinthecookiefieldinL2TPv3headersofthepacketsitsendstothe
localPErouterthroughanL2TPv3session.Thesevaluesarerequiredina
staticL2TPv3session.
ThecookiefieldisanoptionalpartofanL2TPv3headerwithalengthofeither4
or8bytes.Ifyouspecifyan8bytelength,youmustalsoenteravalueforthe
highvalueargument.
NoteFortheCisco10720andCisco12000seriesInternetrouters,an8byte
cookiemustbeconfiguredwiththiscommand.
Examples
85/117
27.4.2016.
Thefollowingexampleshowshowtoconfigurethecookiefieldof4bytes
startingat54321fortheL2TPv3headersinincomingtunneledpacketssent
fromtheremotePEpeer:
Router(config)#interfaceEthernet0/0
Router(configif)#xconnect10.0.3.201123encapsulationl2tpv3manualp
Router(configifxconn)#l2tpcookielocal454321
RelatedCommands
Command
Description
l2tp
cookie
remote
ConfiguresthesizeofthecookiefieldusedintheL2TPv3
headersofoutgoing(sent)packetsfromtheremotePEpeer
router.
l2tphello
Configurestheintervalusedbetweensendinghellokeepalive
messages.
l2tpid
ConfigurestheIDsusedbythelocalandremotePErouters
ateachendofanL2TPv3session.
xconnect
l2tpcookieremote
ToconfigurethesizeofthecookiefieldusedintheLayer2TunnelProtocol
Version3(L2TPv3)headersofoutgoingpacketssentfromthelocalprovider
edge(PE)peerrouter,usethel2tpcookieremotecommandinxconnect
configurationmode.Toremovetheconfiguredcookiefieldparameters,usethe
noformofthiscommand.
l2tpcookieremotesizelowvalue[highvalue]
nol2tpcookieremotesizelowvalue[highvalue]
SyntaxDescription
size
ThesizeofthecookiefieldinL2TPv3headers.Thevalidvaluesare
0,4,and8.
86/117
27.4.2016.
low
value
Thevalueofthelower4bytesofthecookiefield.
high
value
(Optional)Thevalueoftheupper4bytesofthecookiefield.For8
bytecookiefields,youmustenterthevaluefortheupper4bytesof
thecookiefield.
Defaults
NocookievalueisincludedintheheaderofL2TPpackets.
CommandModes
Xconnectconfiguration
CommandHistory
Release
Modification
UsageGuidelines
Thel2tpcookielocalcommandspecifiesthevaluesthatthelocalPErouter
includesinthecookiefieldinL2TPv3headersofthepacketsitsendstothe
remotePErouterthroughanL2TPv3session.Thesevaluesarerequiredina
staticL2TPv3session.
ThecookiefieldisanoptionalpartofanL2TPv3headerwithalengthofeither4
or8bytes.Ifyouspecifyan8bytelength,youmustalsoenteravalueforthe
highvalueargument.
Examples
Thefollowingexampleshowshowtoconfigurethecookiefieldof4bytes
startingat12345fortheL2TPv3headersinoutgoingtunneledpacketssentto
theremotePEpeer:
87/117
27.4.2016.
Router(configifxconn)#l2tpcookieremote412345
RelatedCommands
Command
Description
l2tp
cookie
local
headersofincoming(received)packetsfromtheremotePE
peerrouter.
l2tphello
messages.
l2tpid
xconnect
l2tphello
TospecifytheuseofahellokeepalivesettingcontainedinaspecifiedLayer2
TunnelingProtocolclassconfigurationforastaticLayer2TunnelProtocol
Version3(L2TPv3)session,usethel2tphellocommandinxconnect
configurationmode.Todisablethesendingofhellokeepalivemessages,use
thenoformofthiscommand.
l2tphellol2tpclassname
nol2tphellol2tpclassname
SyntaxDescription
l2tp
class
name
SpecifiestheL2TPclassconfigurationinwhichthehello
keepaliveintervaltobeusedfortheL2TPv3sessionisstored.
Defaults
Nohellokeepalivemessagesaresent.
88/117
27.4.2016.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
BecauseastaticL2TPv3sessiondoesnotuseacontrolplanetodynamically
negotiatecontrolchannelparameters,youmustusethel2tphellocommandto
specifyanL2TPclassconfigurationthatcontainstheintervalforsendinghello
keepalivemessages.
Thefollowingexampleshowshowtoconfigurethetimeintervalforhello
keepalivemessagesstoredintheL2TPclassconfigurationnamedl2tpdefaults
foranEthernetinterfaceusingtheconfigurationsettingsstoredinthe
pseudowireclassnamedetherpw:
Router(configifxconn)#l2tphellolt2pdefaults
RelatedCommands
Command
Description
l2tp
cookie
local
peerrouter.
l2tp
cookie
remote
headersofoutgoing(transmitted)packetsfromtheremote
PEpeerrouter.
l2tpid
89/117
27.4.2016.
xconnect
l2tpid
Toconfiguretheidentifiersusedbythelocalandremoteprovideredgerouters
ateachendofaLayer2TunnelProtocolVersion3(L2TPv3)session,usethe
l2tpidcommandinXconnectconfigurationmode.Toremovetheconfigured
identifiersforlocalandremotesessions,usethenoformofthiscommand.
l2tpidlocalsessionIDremotesessionID
nol2tpidlocalsessionIDremotesessionID
SyntaxDescription
localsession
ID
TheidentifierusedbythelocalPErouterforasitslocal
sessionidentifier.
remote
sessionID
TheidentifierusedbytheremotePErouterasitslocal
sessionidentifier.
Defaults
Nosessionidentifiersareconfigured.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
TheXconnectconfigurationthatbindsanattachmentcircuittoanL2TPv3
90/117
27.4.2016.
pseudowireisnotcompletewithoutconfiguredvaluesforthelocalsessionID
andremotesessionIDarguments.
Examples
Thefollowingexampleshowshowtoconfiguretheidentifiersnamed222forthe
localPErouterand111fortheremotepeerinanL2TPv3sessionboundtoan
EthernetcircuitusingtheL2TPv3configurationsettingsstoredinthe
pseudowireclassnamedetherpw:
Router(configifxconn)#l2tpid222111
RelatedCommands
Command
Description
l2tp
cookie
local
peerrouter.
l2tp
cookie
remote
headersofoutgoing(transmitted)packetsfromtheremote
PEpeerrouter.
l2tphello
messages.
xconnect
password
Toconfigurethepasswordusedbyaprovideredge(PE)routerforLayer2
TunnelProtocolVersion3(L2TPv3)authentication,usethepassword
commandinL2TPclassconfigurationmode.Todisableaconfiguredpassword,
password[encryptiontype]password
nopassword[encryptiontype]password
91/117
27.4.2016.
SyntaxDescription
encryption
type
(Optional)Specifiesthetypeofencryptiontouse.Thevalid
valuesarefrom0to7.Currentlydefinedencryptiontypesare
0(noencryption)and7(textisencryptedusinganalgorithm
definedbyCisco).
password
SpecifiesthepasswordusedforL2TPv3authentication.
Defaults
IfapasswordisnotconfiguredfortheL2TPclasswiththepasswordcommand,
thepasswordconfiguredwiththeusernamepasswordcommandinglobal
configurationmodeisused.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
Thepasswordthatyoudefinewiththepasswordcommandisalsousedfor
attributevaluepair(AVP)hiding.
ThepasswordhierarchysequenceusedforalocalandremotepeerPEfor
L2TPv3authenticationisasfollows:
TheL2TPv3password(configuredwiththepasswordcommand)isused
first.
IfnoL2TPv3passwordexists,thegloballyconfiguredpassword(configured
withtheusernamepasswordcommand)fortherouterisused.
Examples
Thefollowingexamplesetsthepasswordnamedtunnel2tobeusedto
92/117
27.4.2016.
authenticateanL2TPv3sessionbetweenthelocalandremotepeersinL2TPv3
pseudowiresconfiguredwiththeL2TPclassconfigurationnamedl2tpclass1:
Router(configl2tpclass)#passwordtunnel2
RelatedCommands
Command
Description
l2tpclass
protocol
Tospecifythesignalingprotocoltobeusedtomanagethepseudowirescreated
fromapseudowireclassforadynamicLayer2TunnelProtocolVersion3
(L2TPv3)session,andthatcontrolplaneconfigurationsettingsaretobetaken
fromaspecifiedL2TPclass,usetheprotocolcommandinpseudowireclass
configurationmode.Toremovethesignalingprotocol(andthecontrolplane
configurationtobeused)forapseudowireclass,usethenoformofthis
command.
protocol{l2tpv3|none}[l2tpclassname]
noprotocol{l2tpv3|none}[l2tpclassname]
SyntaxDescription
l2tpv3
SpecifiesthatL2TPv3signalingprotocolwillbeusedinL2TPv3
sessions.
none
SpecifiesthatnosignalingprotocolwillbeusedinL2TPv3
sessions.
l2tp
class
name
(Optional)ThenameoftheL2TPclasswhosecontrolplane
configurationistobeusedforpseudowiresindynamicL2TPv3
sessionssetupfromaspecifiedpseudowireclass.
93/117
27.4.2016.
Defaults
Thedefaultprotocoloptionisl2tpv3.
Ifyoudonotenteravalueforthel2tpclassnameargument,thedefaultcontrol
planeconfigurationsettingsintheL2TPsignalingprotocolareused.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
Usetheprotocoll2tpv3commandtoconfigureL2TPv3asthesignaling
protocoltouseindynamicL2TPv3sessionscreatedfromthespecified
pseudowireclass.Inaddition,youcanusethiscommandtospecifytheL2TP
class(seethesection"ConfiguringtheXconnectAttachmentCircuit")from
whichthecontrolplaneconfigurationsettingsaretobetakenforuseina
dynamicL2TPv3session.
Usetheprotocolnonecommandtospecifythatnosignalingwillbeusedin
L2TPv3sessionscreatedfromthespecifiedpseudowireclass.This
configurationisrequiredforinteroperabilitywitharemotepeerrunningthe
UniversalTunnelInterface(UTI).
Donotusethecommandifyouwanttoconfigureapseudowireclassusedto
createmanualL2TPv3sessions(seethesection"StaticL2TPv3Sessions").
Examples
Thefollowingexampleshowshowtoenterpseudowireconfigurationmode,and
howtoconfigureL2TPv3asthesignalingprotocol.Thecontrolplane
configurationusedintheL2TPclassnamedclass1willbeusedtocreate
dynamicL2TPv3sessionsforaVLANXconnectinterface:
Router(config)#pseudowireclassvlanxconnect
Router(configpw)#protocoll2tpv3class1
RelatedCommands
94/117
27.4.2016.
Command
Description
pseudowire
class
pseudowireclass
TospecifythenameofaLayer2TunnelProtocolVersion3(L2TPv3)
pseudowireclassandenterpseudowireclassconfigurationmode,usethe
pseudowireclasscommandinglobalconfigurationmode.
pseudowireclass[pwclassname]
SyntaxDescription
pw
class
name
(Optional)ThenameofaL2TPpseudowireclass.Ifyouwantto
configuremorethanonepseudowireclass,youmustenteravalue
forthepwclassnameargument.
Defaults
Nopseudowireclassisdefined.
CommandModes
Globalconfiguration
CommandHistory
Release
Modification
UsageGuidelines
Thepseudowireclasscommandallowsyoutoconfigureapseudowireclass
templatethatconsistsofconfigurationsettingsusedbyallattachmentcircuits
boundtotheclass.Apseudowireclassincludesthefollowingconfiguration
95/117
27.4.2016.
settings:
Dataencapsulationtype
Controlprotocol
Sequencing
IPaddressofthelocalL2TPv3interface
TypeofService(ToS)valueinIPheaders
Afteryouenterthepseudowireclasscommand,youswitchtopseudowire
classconfigurationmode,wherepseudowiresettingsmaybeconfigured.
Examples
Thefollowingexampleshowshowtoenterpseudowireclassconfigurationmode
toconfigureapseudowireconfigurationtemplatenamedetherpw:
RelatedCommands
Command
Description
l2tpclass
xconnect
receivewindow
Toconfigurethepacketsizeofthereceivewindowontheremoteprovideredge
routerattheotherendofaLayer2TunnelProtocolVersion3(L2TPv3)control
channel,usethereceivewindowcommandinL2TPclassconfigurationmode.
Todisabletheconfiguredvalue,usethenoformofthiscommand.
receivewindowsize
noreceivewindowsize
SyntaxDescription
size
Thenumberofpacketsthatcanbereceivedbytheremotepeer
beforebackoffqueueingoccurs.Thevalidvaluesrangefrom1tothe
upperlimitthepeerhasforreceivingpackets.Thedefaultvalueis
96/117
27.4.2016.
theupperlimit.
Defaults
Thedefaultvalueistheupperlimittheremotepeerhasforreceivingpackets.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
Todeterminetheupperlimitforthesizeargument,refertotheplatformspecific
documentationforthepeerrouter.
Examples
Thefollowingexamplesetsareceivewindowof30packetstotheremotepeer
inL2TPv3pseudowiresconfiguredwiththeL2TPclassnamedl2tpclass1:
Router(configl2tpclass)#receivewindow30
RelatedCommands
Command
Description
l2tpclass
retransmit
97/117
27.4.2016.
Toconfiguretheretransmissionsettingsofcontrolpackets,usetheretransmit
commandinL2TPclassconfigurationmode.Todisabletheconfiguredvalues,
retransmit{initialretriesinitialretries|retriesretries|timeout{max|min}
timeout}
noretransmit{initialretriesinitialretries|retriesretries|timeout{max|
min}timeout}
SyntaxDescription
initial
retries
initial
retries
Specifieshowmanystartcontrolchannelrequests(SCCRQs)
areresentbeforegivinguponthesession.Validvaluesforthe
initialretriesargumentrangefrom1to1000.Thedefaultvalue
is2
retries
retries
Specifieshowmanyretransmissioncyclesoccurbefore
determiningthatthepeerprovideredge(PE)routerdoesnot
respond.Validvaluesfortheretriesargumentrangefrom1to
1000.Thedefaultvalueis15.
timeout
{max|
min}
timeout
Specifiesmaximumandminimumretransmissionintervals(in
seconds)forresendingcontrolpackets.Validvaluesforthe
timeoutargumentrangefrom1to8.Thedefaultmaximum
intervalis8thedefaultminimumintervalis1.
Defaults
Initialretries:2
Retries:15
Maximumtimeoutinterval:8seconds
Minimumtimeoutinterval:1second
CommandModes
CommandHistory
Release
Modification
98/117
27.4.2016.
UsageGuidelines
Usethiscommandtoconfiguretheamountoftimespenttryingtoestablishor
maintainacontrolchannel.
Examples
ThefollowingexampleconfigurestenretriesforsendingLayer2Tunnel
ProtocolVersion3(L2TPv3)tunneledpacketstoaremotepeerinL2TPv3
pseudowiresconfiguredwiththeL2TPclassnamedl2tpclass1:
Router(configl2tpclass)#retransmitretries10
RelatedCommands
Command
Description
l2tpclass
sequencing
Toconfigurethedirectioninwhichsequencingisenabledfordatapacketsinan
aLayer2TunnelProtocolVersion3(L2TPv3)pseudowire,usethesequencing
commandinpseudowireclassconfigurationmode.Toremovethesequencing
configurationfromthepseudowireclass,usethenoformofthiscommand.
sequencing{transmit|receive|both}
nosequencing{transmit|receive|both}
SyntaxDescription
transmit
UpdatestheSequenceNumberfieldintheheadersofdata
packetssentoverthepseudowireaccordingtothedata
encapsulationmethodthatisused.
receive
KeepsthevalueintheSequenceNumberfieldintheheadersof
datapacketsreceivedoverthepseudowire.Outoforder
99/117
27.4.2016.
packetsaredropped.
both
Enablesboththetransmitandreceiveoptions.
Defaults
Sequencingisoff.
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
Whenyouenablesequencingusinganyoftheavailableoptions,L2TPv3
automaticallyenablesthesendingofsequencenumbersandrequeststhe
remoteprovideredge(PE)peertosendsequencenumbers.Outoforder
packetsreceivedonthepseudowirearedroppedonlyifyouusethe
sequencingreceiveorsequencingbothcommand.
InCiscoIOSRelease12.0(23)S,sequencingisnotsupportedonthe
Cisco10720InternetrouterandtheCisco12000seriesInternetrouters.Ifthe
L2TPv3peerrouterrequestssequencenumbersforanL2TPv3session
configuredonaCisco10720InternetrouterorCisco12000seriesInternet
router,therequesttoestablishthesessionisdenied.
IfsequencingisenabledforL2TPv3pseudowiresontheCisco7500series,all
trafficonthepseudowiresisswitchedthroughtheRouteSwitchProcessor
(RSP)regardlessofthesettingconfiguredwiththeipcefdistributed
command.
Examples
Thefollowingexampleshowshowtoenablesequencingindatapacketsin
L2TPv3pseudowirescreatedfromthepseudowireclassnamedetherpwso
100/117
27.4.2016.
thatSequenceNumberfieldisupdatedintunneledpacketheadersfordata
packetsbothsentandreceivedoverthepseudowire:
Router(configpw)#sequencingboth
RelatedCommands
Command
Description
pseudowire
class
showl2tunsession
TodisplaythecurrentstateofaLayer2sessionanddisplayprotocol
informationaboutaLayer2TunnelProtocolVersion3(L2TPv3)control
channel,usetheshowl2tunsessioncommandinEXECmode.
showl2tunsession[all[ipaddripaddress[vcidnumber]|vcidnumber]|
brief[ipaddripaddress[vcidnumber]|vcidnumber]|circuit[ipaddrip
address[vcidnumber]|vcidnumber]|l2tp[ipaddripaddress[vcidnumber]
|vcidnumber]|packets[ipaddripaddress[vcidnumber]|vcidnumber]|
sequence[ipaddripaddress[vcidnumber]|vcidnumber]|state[ipaddrip
address[vcidnumber]|vcidnumber]]
SyntaxDescription
all
(Optional)DisplaysinformationaboutallcurrentL2TPv3
sessionsontherouter.
ipaddr
(Optional)IPaddressofinterfaceofthepeerprovideredge
ipaddress (PE)routeronwhichoneormoreL2TPv3sessionshavebeen
configured.
SpecifiestheIPaddressofthepeerPErouterandthe32bit
virtualcircuitidentifiersharedbetweenthePEateachendof
thecontrolchannel.ThepeerrouterID(IPaddress)and
virtualcircuitidentifiermustbeauniquecombinationonthe
router.
vcid
number
(Optional)32bitvirtualcircuitidentifiersharedbetweenthe
peerPEandthelocalrouterateachendofthecontrol
channel.
101/117
27.4.2016.
brief
sessions,includingpeerIDaddressandcircuitstatusofthe
L2TPv3sessions.
circuit
sessions,includingcircuitstatus(upordown).
l2tp
(Optional)DisplaysinformationaboutL2TPforallcurrent
L2TPv3sessions.
packets
(Optional)Displaysinformationaboutthepacketcounters(in
andout)associatedwithcurrentL2TPv3sessions.
sequence
(Optional)Displayssequencinginformationabouteach
L2TPv3session,includingnumberofoutoforderand
returnedpackets.
state
sessionsandtheirprotocolstate,includingremotevirtual
circuitidentifiers.
CommandModes
EXEC
CommandHistory
Release
Modification
UsageGuidelines
Whenyouusetheshowl2tunsessioncommandtodisplayinformationabout
currentL2TPv3sessionsontherouter,youcanfiltertheoutputasfollows:
TofiltertheoutputtoincludeonlyL2TPv3sessionssetupforaspecificIP
address,enteripaddripaddressinthecommand.
102/117
27.4.2016.
TofiltertheoutputtoincludeonlytheL2TPv3sessionthatmatchesthe
specifiedremoteIPaddressandvirtualcircuitidentifier,enteripaddrip
addressvcidnumberinthecommand.
TofiltertheoutputtoincludeonlyL2TPv3sessionssetupforaspecificIP
address,entervcidnumberinthecommand.
Examples
Thefollowingexampleshowshowtodisplaydetailedinformationaboutall
currentL2TPv3sessions:
Router#showl2tunsessionall
Callserialnumberis0
Remotetunnelnameis
outoforder:0
total:0
Sendpacketsdropped:
total:0
Sessionvcidis123
CircuitstateisUP
SSSswitchingenabled
Sequencingisoff
ThefollowingexampleshowshowtodisplayinformationonlyabouttheL2TPv3
sessionsetuponapeerPErouterwithanIPaddressof172.18.184.142anda
virtualcircuitidentifierof300:
Router#showl2tunsessionallipaddr172.18.184.142vcid300
L2TPSession
103/117
27.4.2016.
Callserialnumberis2074900020
Remotetunnelnameistun1
SessionisL2TPsignalled
Sessionvcidis300
SessionLayer2circuit,typeisEthernetVlan,nameisFastEthernet0/
CircuitstateisUP
SetDFbitto0
localcookie,size4bytes,valueCFDC5BF3
remotecookie,size4bytes,valueFE3356C4
SSSswitchingenabled
Sequencingison
Ns9932,Nr10001,0outoforderpacketsdiscarded
Thefollowingexampleshowshowtodisplayinformationaboutthecircuitstatus
ofL2TPv3sessionsonarouter:
Router#showl2tunsessioncircuit
LocIDTunIDPeeraddressTypeStatUsername,Intf/
Vcid,Circuit
3251726515172.18.184.142VLANUP100,Fa0/1/0.1:1
3251930866172.18.184.142VLANUP200,Fa0/1/0.2:2
3251835217172.18.184.142VLANUP300,Fa0/1/0.3:3
RelatedCommands
Command
Description
show
l2tun
tunnel
DisplaysthecurrentstateofanL2TPv3sessionanddisplay
informationaboutcurrentlyconfiguredsessions,including
localandremoteL2TPhostnames,aggregatepacket
counts,andL2TPcontrolchannels.
104/117
27.4.2016.
showl2tuntunnel
TodisplaythecurrentstateofaLayer2TunnelProtocolVersion3(L2TPv3)
sessionanddisplayinformationaboutcurrentlyconfiguredsessions,including
localandremoteL2TPhostnames,aggregatepacketcounts,andL2TPcontrol
channels,usetheshowl2tuntunnelcommandinEXECmode.
showl2tuntunnel[all[ididentifier|localnamelocalnameremotename|
remotenameremotenamelocalname]|packets[ididentifier|localname
localnameremotename|remotenameremotenamelocalname]|state[id
identifier|localnamelocalnameremotename|remotenameremotename
localname]|summary[ididentifier|localnamelocalnameremotename|
remotenameremotenamelocalname]|transport[ididentifier|localname
localnameremotename|remotenameremotenamelocalname]]
SyntaxDescription
all
(Optional)DisplaysinformationaboutallcurrentL2TP
sessionsconfiguredontherouter.
ididentifier
(Optional)SpecifiesthelocaltunnelIDnumber.
local
name
localname
remote
name
(Optional)Specifiesthelocalandremotenamesusedinthe
L2TPv3session.
remote
name
remote
name
localname
(Optional)Specifiestheremoteandlocalnamesusedinthe
L2TPv3session.
packets
(Optional)Displaysaggregatepacketcountsforallnegotiated
L2TPv3sessions.
state
(Optional)Displaysinformationaboutthecurrentstateof
L2TPv3sessions,includingthelocalandremotehostnames
foreachcontrolchannel.
105/117
27.4.2016.
summary
(Optional)DisplaysasummaryofL2TPsessionsonthe
routerandtheircurrentstate,includingthenumberofvirtual
privatedialupnetwork(VPDN)sessionsassociatedwitheach
controlchannel.
transport
(Optional)DisplaysinformationabouttheL2TPcontrol
channelsusedineachsessionandthelocalandremoteIP
addressesateachendofthecontrolchannel.
CommandModes
EXEC
CommandHistory
Release
Modification
UsageGuidelines
Whenyouusetheshowl2tuntunnelcommandtodisplayinformationabout
configuredL2TPsessionsontherouter,youcanfiltertheoutputasfollows:
TofiltertheoutputtoincludeonlyL2TPsessionssetupusingthelocal
tunnelID,enterididentifierinthecommand.
TofiltertheoutputtoincludeonlytheL2TPsessionthatmatchesthe
specifiedlocalIPnameandremotename,entereitherlocalnamelocal
nameremotenameorremotenameremotenamelocalnameinthe
command.
Examples
Thefollowingexampleshowshowtodisplaydetailedinformationaboutall
currentlyconfiguredL2TPsessions:
Router#showl2tuntunnelall
TunnelInformationTotaltunnels1sessions1
106/117
27.4.2016.
Tunnelid26515isup,remoteidis41814,1activesessions
Tunnelstateisestablished,timesincechange03:11:50
TunneltransportisIP(115)
Remotetunnelnameistun1
InternetAddress172.18.184.142,port0
LocaltunnelnameisRouter
InternetAddress172.18.184.116,port0
Tunneldomainis
VPDNgroupfortunnelis
0packetssent,0received
0bytessent,0received
ControlNs11507,Nr11506
LocalRWS2048(default),RemoteRWS800
TunnelPMTUcheckingdisabled
Retransmissiontime1,max1seconds
Unsentqueuesize0,max0
Resendqueuesize1,max1
Totalresends0,ZLBACKssent11505
Currentnosessionqueuecheck0of5
Retransmittimedistribution:000000000
Sessionsdisconnectedduetolackofresources0
ThefollowingexampleshowshowtofilterinformationtodisplayL2TPcontrol
channeldetailsonlyforthesessionsconfiguredwiththelocalnameRouterand
theremotenametun1:
Router#showl2tuntunneltransportlocalnameRoutertun1
TunnelInformationTotaltunnels3sessions3
LocIDTypeProtLocalAddressPortRemoteAddressPort
26515IP115172.18.184.1160172.18.184.1420
30866IP115172.18.184.1160172.18.184.1420
35217IP115172.18.184.1160172.18.184.1420
Thefollowingexampleshowshowtodisplayinformationaboutthecurrentstate
ofL2TPsessionswiththelocalandremotehostnamesofeachsession:
Router#showl2tuntunnelstate
LocIDRemID
LocalNameRemoteNameStateL
2651541814
Router
tun1
308666809
Router
tun1
3521737340
Router
tun1
107/117
27.4.2016.
RelatedCommands
Command
Description
show
l2tun
session
DisplaysthecurrentstateofaLayer2sessionanddisplays
protocolinformationaboutanL2TPv3controlchannel.
ToenableSimpleNetworkManagementProtocol(SNMP)notifications(trapsor
informrequests)forLayer2TunnelProtocolVersion3(L2TPv3)sessions,use
thesnmpserverenabletrapsl2tunsessioncommandinglobalconfiguration
mode.TodisableSNMPnotifications,usethenoformofthiscommand.
nosnmpserverenabletrapsl2tunsession
SyntaxDescription
Defaults
Thiscommandisdisabledbydefault.
CommandModes
Globalconfiguration
CommandHistory
Release
Modification
UsageGuidelines
SNMPnotificationscanbesentastrapsorinformrequests.Thiscommand
enablesbothtrapsandinformrequestsforL2TPsessions.Tospecifywhether
thenotificationsshouldbesentastrapsorinforms,usethesnmpserverhost
[traps|informs]command.
108/117
27.4.2016.
Ifyoudonotenterthesnmpserverenabletrapsl2tunsessioncommand,no
notificationsaresent.
Thesnmpserverenabletrapsl2tunsessioncommandisusedinconjunction
withthesnmpserverhostcommand.Usethesnmpserverhostcommandto
specifywhichhostorhostsreceiveSNMPnotifications.
Examples
ThefollowingexampleenablestheroutertosendL2TPsessiontrapstothe
hostspecifiedbythenamemyhost.cisco.com,usingthecommunitystring
definedaspublic:
Router(config)#snmpserverenabletrapsl2tunsession
Router(config)#snmpserverhostmyhost.cisco.compublic
RelatedCommands
Command
Description
snmp
server
host
SpecifieswhetheryouwanttheSNMPnotificationssentas
trapsorinforms,theversionofSNMPtouse,thesecurity
levelofthenotifications(forSNMPv3),andtherecipient
(host)ofthenotifications.
timeoutsetup
Toconfiguretheamountoftimeallowedtosetupacontrolchannelwitha
remoteprovideredge(PE)routerattheotherendofaLayer2TunnelProtocol
Version3(L2TPv3)pseudowire,usethetimeoutsetupcommandinL2TP
classconfigurationmode.Todisabletheconfiguredvalue,usethenoformof
thiscommand.
timeoutsetupseconds
notimeoutsetupseconds
SyntaxDescription
seconds
ThenumberofsecondsallowedtosetupanL2TPv3control
channel.Thevalidvaluesrangefrom60to6000.Thedefault
valueis300seconds.
109/117
27.4.2016.
Defaults
300seconds
CommandModes
CommandHistory
Release
Modification
UsageGuidelines
Usethiscommandtoconfiguretheamountoftimespentattemptingtoestablish
acontrolchannel.
Examples
Thefollowingexamplesetsatimeoutperiodof200secondstoestablisha
controlchannelwitharemotepeerinL2TPv3pseudowiresconfiguredwiththe
L2TPclassnamedl2tpclass1:
Router(configl2tpclass)#timeoutsetup200
RelatedCommands
Command
Description
l2tpclass
xconnect
TobindanEthernet,802.1qVLAN,orFrameRelayattachmentcircuittoaLayer
2TunnelProtocolVersion3(L2TPv3)pseudowireforXconnectserviceand
110/117
27.4.2016.
enterxconnectconfigurationmode,usethexconnectcommandininterface
configurationmodeorl2transportPVPconfigurationmode.
xconnectpeeripaddressvcidpseudowireparameters[sequencing
{transmit|receive|both}]
SyntaxDescription
peerip
address
TheIPaddressoftheremoteprovideredge(PE)peer.
vcid
The32bitidentifierofthevirtualcircuitbetweentherouters
ateachendoftheL2TPv3controlchannel.
pseudowire
parameters
Theencapsulationandpseudowireclassparameterstobe
usedfortheL2TPv3controlchannel.Atleastoneofthe
followingpseudowireparametersmustbeconfigured:
encapsulation{l2tpv3[manual]|mpls}The
encapsulationpseudowireclassparameterspecifiesthe
tunnelingmethodusedtoencapsulatedatainthe
pseudowire:
l2tpv3L2TPv3isthetunnelingmethodtobeused.
manual(Optional)Nosignalingistobeusedinthe
L2TPv3controlchannel.Thiscommandplacesthe
routerinxconnectconfigurationmodeformanual
configurationofL2TPv3parametersforthe
attachmentcircuit.
mplsMultiprotocolLabelSwitching(MPLS)isthe
tunnelingmethodtobeused.
pwclasspwclassnameThepseudowireclass
configurationfromwhichthedataencapsulationtype
(L2TPv3)willbetaken.Thisoptionismandatoryifyou
selectL2TPv3asyourdataencapsulationmethod.
sequencing (Optional)Setsthesequencingmethodtobeusedfor
{transmit|
packetsreceivedorsentinL2TPsessions:
receive|
transmitSequencingofL2TPdatapacketsreceived
both}
fromtheL2TPv3session.
receiveSequencingofL2TPdatapacketssentintothe
L2TPv3session.
bothSequencingofL2TPdatapacketsthatareboth
sentandreceivedfromtheL2TPv3session.
111/117
27.4.2016.
Defaults
ThedefaultbehavioristouseL2TPv3asthedataencapsulationmethodwith
sequencingoff.
CommandModes
Interfaceconfiguration
l2transportPVPconfiguration
CommandHistory
Release
Modification
UsageGuidelines
Thecombinationofthepeeripaddressandvcidmustbeuniqueontherouter.
EachXconnectconfigurationmusthaveauniquecombinationofpeerip
addressandvcidconfiguration.
NoteIftheremoterouterisaCisco12000seriesInternetrouter,thepeerip
addressargumentmustspecifyaloopbackaddressonthatrouter.
Thesamevcidvaluethatidentifiestheattachmentcircuitmustbeconfigured
usingthexconnectcommandonthelocalandremotePErouterateachendof
anL2TPv3session.Thevirtualcircuitidentifiercreatesthebindingbetweena
pseudowireandanattachmentcircuit.
TomanuallyconfiguretheL2TPsettingsusedintheattachmentcircuit,enter
encapsulationl2tpv3manualinthexconnectcommand.Thisconfigurationis
calledastaticL2TPv3session.Therouterisplacedinxconnectconfiguration
modeandyoucanthenconfigurethefollowingoptions:
Localandremotesessionidentifiers(usingthel2tpidcommand)forlocal
andremotePEroutersateachendofthesession.
SizeofthecookiefieldusedintheL2TPv3headersofincoming(sent)
packetsfromtheremotePEpeerrouter(usingthel2tpcookielocal
command).
SizeofthecookiefieldusedintheL2TPv3headersofoutgoing(received)
L2TPdatapackets(usingthel2tpcookieremotecommand).
Intervalusedbetweensendinghellokeepalivemessages(usingthel2tp
112/117
27.4.2016.
hellocommand).
FormoreinformationaboutconfiguringastaticL2TPv3sessions,seethe
section"ManuallyConfiguringL2TPv3SessionParameters."
Ifyoudonotenterencapsulationl2tpv3manualinthexconnectcommand,
thedataencapsulationtypefortheL2TPv3sessionistakenfromthe
encapsulationtypeconfiguredforthepseudowireclassspecifiedwiththepw
classpwclassnamecommand(seethesection"ConfiguringtheL2TPv3
Pseudowire").
ThepwclasspwclassnamevaluebindstheXconnectconfigurationofan
attachmentcircuittoaspecificpseudowireclass.Inthisway,thepseudowire
classconfigurationservesasatemplatethatcontainssettingsusedbyall
attachmentcircuitsboundtoitwiththexconnectcommand.
NoteIfyouspecifytheencapsulationl2tpv3keyword,youmustspecifythe
pwclasskeyword.
Examples
ThefollowingexampleshowshowtoconfigureXconnectserviceforanEthernet
interfacebybindingtheEthernetcircuittotheL2TPv3pseudowirenamed123
witharemotepeer10.0.3.201,andbyusingtheL2TPconfigurationsettingsin
thepseudowireclassnamedvlanxconnect:
Router(config)#interfaceEthernet0/0.1
Router(configif)#xconnect10.0.3.201123pwclassvlanxconnect
RelatedCommands
Command
Description
l2tpclass
ConfiguresatemplateofL2TPcontrolplaneconfiguration
settingsthatcanbeinheritedbydifferentpseudowire
classes.
l2tpcookie
local
.ConfiguresthesizeofthecookiefieldusedintheL2TPv3
headersofincomingpacketsreceivedfromtheremotePE
peerrouter.
l2tpcookie
remote
headersofoutgoingpacketssentfromthelocalPEpeer
router.
113/117
27.4.2016.
l2tphello
Specifiestheuseofahellokeepalivesettingcontainedina
specifiedL2TPclassconfigurationforastaticL2TPv3
session.
l2tpid
Configurestheidentifiersusedbythelocalandremote
provideredgeroutersateachendofanL2TPv3session.
pseudowire
class
Configuresatemplateofpseudowireconfigurationsettings
usedbytheattachmentcircuitstransportedovera
pseudowire.
Glossary
AVPsattributevaluepairs.
BECNbackwardexplicitcongestionnotification.BitsetbyaFrameRelay
networkinframestravelingintheoppositedirectionofframesencounteringa
congestedpath.DTEreceivingframeswiththeBECNbitsetcanrequestthat
higherlevelprotocolstakeflowcontrolactionasappropriate.
CEcustomeredge(FrameRelayswitchoruserdevice).
CIRcommittedinformationrate.RateatwhichaFrameRelaynetworkagrees
totransferinformationundernormalconditions,averagedoveraminimum
incrementoftime.CIR,measuredinbitspersecond,isoneofthekey
negotiatedtariffmetrics.
datalinkcontrollayerLayer2intheSNAarchitecturalmodel.Responsible
forthetransmissionofdataoveraparticularphysicallink.Corresponds
approximatelytothedatalinklayeroftheOSImodel.
DCEdatacircuitterminatingequipment(ITUTexpansion).Devicesand
connectionsofacommunicationsnetworkthatcomprisethenetworkendofthe
usertonetworkinterface.
dCEFdistributedCiscoExpressForwarding.
DLCIdatalinkconnectionidentifier.AuniquenumberassignedtoaPVC
endpointinaFrameRelaynetwork.IdentifiesaparticularPVCendpointwithin
anaccesschannelinaFrameRelaynetworkandhaslocalsignificanceonlyto
thatchannel.
DTEdataterminalequipment.Deviceattheuserendofausernetwork
114/117
27.4.2016.
interfacethatservesasadatasource,destination,orboth.
FECNforwardexplicitcongestionnotification.BitsetbyaFrameRelay
networktoinformDTEreceivingtheframethatcongestionwasexperiencedin
thepathfromsourcetodestination.DTEreceivingframeswiththeFECNbitset
canrequestthathigherlevelprotocolstakeflowcontrolactionasappropriate.
HDLCHighLevelDataLinkControl.Agenericlinklevelcommunications
protocoldevelopedbytheInternationalOrganizationforStandardization(ISO).
HDLCmanagessynchronous,codetransparent,serialinformationtransferover
alinkconnection.
ICMPInternetControlMessageProtocol.Anetworkprotocolthathandles
networkerrorsanderrormessages.
IDBinterfacedescriptorblock.
ISISIntermediateSystemtoIntermediateSystem.OSIlinkstatehierarchical
routingprotocolbasedonDECnetPhaseVrouting,wherebyISs(routers)
exchangeroutinginformationbasedonasinglemetrictodeterminenetwork
topology.
L2TPAnextensiontoPPPmergingfeaturesoftwotunnelingprotocols:Layer
2Forwarding(L2F)fromCiscoSystemsandPointtoPointTunneling(PPTP)
fromMicrosoft.L2TPisanInternetEngineeringTaskForce(IETF)standard
endorsedbyCiscoSystems,andothernetworkingindustryleaders.
L2TPv3DraftversionofL2TPthatenhancesfunctionalityinRFC2661
(L2TP).
LMILocalManagementInterface.
MPLSMultiprotocolLabelSwitching.SwitchingmethodthatforwardsIPtraffic
usingalabel.Thislabelinstructstheroutersandtheswitchesinthenetwork
wheretoforwardthepacketsbasedonpreestablishedIProutinginformation.
MQCmodularqualityofservicecommandlineinterface.
MTUmaximumtransmissionunit.Maximumpacketsize,inbytes,thata
particularinterfacecanhandle.
NNINetworktoNetworkInterface.ATMForumstandardthatdefinesthe
interfacebetweentwoATMswitchesthatarebothlocatedinaprivatenetwork
orarebothlocatedinapublicnetwork.TheUNIstandarddefinestheinterface
betweenapublicswitchandaprivateone.Also,thestandardinterfacebetween
twoFrameRelayswitchesmeetingthesamecriteria.
PEProvideredgerouterprovidingFrameRelayoverL2TPv3functionality.
115/117
27.4.2016.
PPPPointtoPointProtocol.Alinklayerencapsulationmethodfordialupor
dedicatedcircuits.AsuccessortoSerialLineIP(SLIP),PPPprovidesrouterto
routerandhosttonetworkconnectionsoversynchronousandasynchronous
circuits.
PVCpermanentvirtualcircuit.Avirtualcircuitthatispermanentlyestablished.
AFrameRelaylogicallink,whoseendpointsandclassofservicearedefinedby
networkmanagement.AnalogoustoanX.25permanentvirtualcircuit,aPVC
consistsoftheoriginatingFrameRelaynetworkelementaddress,originating
datalinkcontrolidentifier,terminatingFrameRelaynetworkelementaddress,
andterminationdatalinkcontrolidentifier.Originatingreferstotheaccess
interfacefromwhichthePVCisinitiated.Terminatingreferstotheaccess
interfaceatwhichthePVCstops.ManydatanetworkcustomersrequireaPVC
betweentwopoints.PVCssavebandwidthassociatedwithcircuitestablishment
andteardowninsituationswherecertainvirtualcircuitsmustexistallthetime.
Dataterminatingequipmentwithaneedforcontinuouscommunicationuses
PVCs.
PWpseudowire.
SNMPSimpleNetworkManagementProtocol.Networkmanagementprotocol
usedalmostexclusivelyinTCP/IPnetworks.SNMPprovidesameanstomonitor
andcontrolnetworkdevices,andtomanageconfigurations,statisticscollection,
performance,andsecurity.
tunnelingArchitecturethatisdesignedtoprovidetheservicesnecessaryto
implementanystandardpointtopointencapsulationscheme.
UNIUserNetworkInterface.
UTIUniversalTransportInterface.
VPDNvirtualprivatedialupnetwork.Anetworkthatallowsseparateand
autonomousprotocoldomainstosharecommonaccessinfrastructure,including
modems,accessservers,andISDNrouters.AVPDNenablesuserstoconfigure
securenetworksthattakeadvantageofISPsthattunnelremoteaccesstraffic
throughtheISPcloud.
WANwideareanetwork.Datacommunicationsnetworkthatservesusers
acrossabroadgeographicareaandoftenusestransmissiondevicesprovided
bycommoncarriers.FrameRelay,SMDS,andX.25areexamplesofWANs.
NoteRefertotheInternetworkingTermsandAcronymsfortermsnotincluded
inthisglossary.
116/117
27.4.2016.
Copyright2004CiscoSystems,Inc.Allrightsreserved.
2016Ciscoand/oritsaffiliates.Allrightsreserved.
117/117

Layer 2 Tunnel Protocol Version 3 - Cisco

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Layer 2 Tunnel Protocol Version 3 - Cisco

Загружено:

Авторское право:

Доступные форматы

27.4.2016.

Вам также может понравиться