Sessione IPoE su headend pseudocowire in gateway di rete a banda larga
Sommario
Introduzione
In questo documento viene descritta la procedura per configurare le sessioni IP over Ethernet (IPoE) su Pseudowire Headend (PWHE) su ASR9K.
Prerequisiti
Requisiti
Cisco raccomanda la conoscenza dei seguenti argomenti:
- VPN MPLS layer 2
- Funzionalità BNG su ASR9K
Componenti usati
Il documento può essere consultato per tutte le versioni software, ma la scheda di linea utilizzata con ASR9K è A9K-MPA-20X1GE.
Le informazioni discusse in questo documento fanno riferimento a dispositivi usati in uno specifico ambiente di emulazione. Su tutti i dispositivi menzionati nel documento la configurazione è stata ripristinata ai valori predefiniti. Se la rete è operativa, valutare attentamente eventuali conseguenze derivanti dall'uso dei comandi.
Premesse
BNG fornisce il supporto per gli utenti registrati su PWHE. PWHE fornisce connettività L3 ai nodi periferici del cliente tramite una connessione a pseudofilo. Il PWHE termina i circuiti L2VPN esistenti tra i nodi Access-Provider Edge (A-PE) e un'interfaccia virtuale, ed esegue il routing sul pacchetto IP nativo. Ogni interfaccia virtuale può utilizzare una o più interfacce fisiche verso il cloud di accesso per raggiungere i router del cliente tramite i nodi A-PE.
Configurazione
Esempio di rete
Per eseguire questo test, viene utilizzato un ASR1K con versione 154-3.S2 e un ASR9K con versione IOS-XR 5.2.2. OSPF viene utilizzato come protocollo di routing per raggiungere gli altri indirizzi di loopback.
Indirizzo di loopback ASR9K: 10.1.1.1/32
Indirizzo di loopback ASR1K: 10.2.2.2/32
ASR1K
pseudowire-class MPLS
encapsulation mpls
interface GigabitEthernet1/0/0 no ip address media-type rj45 negotiation auto cdp enable xconnect 10.1.1.1 2020 encapsulation mpls pw-class MPLS end
ASR1K#show etherchannel summary
Flags: D - down P/bndl - bundled in port-channel
I - stand-alone s/susp - suspended
H - Hot-standby (LACP only)
R - Layer3 S - Layer2
U - in use f - failed to allocate aggregator
M - not in use, minimum links not met
u - unsuitable for bundling
w - waiting to be aggregated
d - default port
Number of channel-groups in use: 1
Number of aggregators: 1
Group Port-channel Protocol Ports
------+-------------+-----------+-----------------------------------------------
20 Po20(RU) LACP Gi1/0/1(bndl) Gi1/1/1(bndl)
RU - L3 port-channel UP State
SU - L2 port-channel UP state
P/bndl - Bundled
S/susp - Suspended
interface Port-channel20
ip address 192.168.20.2 255.255.255.0
no negotiation auto
mpls ip
end
ASR9K
Di seguito viene riportata la configurazione di ASR9K, che agisce come BNG PWHE.
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show bundle bundle-ether 20
Thu May 21 06:35:39.294 UTC
Bundle-Ether20
Status: Up
Local links
: 2 / 0 / 2 Local bandwidth
: 2000000 (2000000) kbps MAC address (source): 10f3.1172.02c8 (Chassis pool) Inter-chassis link: No Minimum active links / bandwidth: 1 / 1 kbps Maximum active links: 64 Wait while timer: 2000 ms Load balancing: Default LACP: Operational Flap suppression timer: Off Cisco extensions: Disabled mLACP: Not configured IPv4 BFD: Not configured Port Device State Port ID B/W, kbps -------------------- --------------- ----------- -------------- ---------- Gi0/0/1/18 Local Active 0x8000, 0x0007 1000000 Link is Active Gi0/0/1/19 Local Active 0x8000, 0x0008 1000000 Link is Active interface Bundle-Ether20 ipv4 address 192.168.20.1 255.255.255.0 load-interval 30 !
A questo punto, configurare la connessione x tra ASR1K e ASR9K. Specificare l'indirizzo di loopback di ASR1K (10.2.2.2/32) come router adiacente xconnect.
l2vpn
router-id 10.1.1.1
pw-class ASR1K
encapsulation mpls
transport-mode ethernet
!
!
xconnect group PWHE
p2p ASR1K
interface PW-Ether20
neighbor ipv4 10.2.2.2 pw-id 2020
pw-class ASR1K
!
!
!
!
generic-interface-list BE20_ONLY
interface Bundle-Ether20
interface GigabitEthernet0/0/1/18
interface GigabitEthernet0/0/1/19
!
interface PW-Ether20
ipv4 address 192.168.1.1 255.255.255.0
attach generic-interface-list BE20_ONLY
!
A questo punto, configurare la policy di controllo del destinatario e applicarla all'interfaccia PW-Ethernet a cui il destinatario termina.
dynamic-template type ipsubscriber WDAAR_PWHE_DT ipv4 verify unicast source reachable-via rx ipv4 unnumbered Loopback44 ipv4 unreachables disable ! ! policy-map type control subscriber IPoE_WDAAR_PWHE event session-start match-first class type control subscriber DHCPv4 do-until-failure 5 authorize aaa list WDAAR identifier source-address-mac password cisco 10 activate dynamic-template WDAAR_PWHE_DT ! ! end-policy-map interface PW-Ether20.250 ipv4 address 192.168.10.1 255.255.255.252 service-policy type control subscriber IPoE_WDAAR_PWHE encapsulation dot1q 250 ipsubscriber ipv4 l2-connected initiator dhcp ! !
Verifica
Le informazioni contenute in questa sezione permettono di verificare che la configurazione funzioni correttamente. Di seguito sono elencati i comandi che è possibile utilizzare per verificare che xconnect sia attivo/attivo su ASR9K.
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show l2vpn xconnect
Legend: ST = State, UP = Up, DN = Down, AD = Admin Down, UR = Unresolved,
SB = Standby, SR = Standby Ready, (PP) = Partially Programmed
XConnect Segment 1 Segment 2
Group Name ST Description ST Description ST
------------------------ ----------------------------- -----------------------------
PWHE ASR1K UP PE20 UP 10.2.2.2 2020 UP
----------------------------------------------------------------------------------------
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show l2vpn xconnect brief
AToM
Like-to-Like UP DOWN UNR
PW-Ether 1 0 0
Total 1 0 0
Total 1 0 0
Total: 1 UP, 0 DOWN, 0 UNRESOLVED
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show subscriber session filter ipv4-address 192.168.44.254
Codes: IN - Initialize, CN - Connecting, CD - Connected, AC - Activated,
ID - Idle, DN - Disconnecting, ED - End
Type Interface State IP Address (Vrf)
--------------------------------------------------------------------------------
IP:DHCP PE20.250.ip1 AC 192.168.44.254 (default)
Una volta che l'interfaccia xconnect è attiva e la sessione IPoE è in linea su ASR9K, si può notare che l'interfaccia Access-Ethernet è PW-Ether.
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show subscriber session filter ipv4-address 192.168.44.254 detail
Interface: PW-Ether20.250.ip1
Circuit ID: Unknown
Remote ID: Unknown
Type: IP: DHCP-trigger
IPv4 State: Up, Mon Apr 20 19:32:51 2015
IPv4 Address: 192.168.44.254, VRF: default
Mac Address: 001f.ca3f.7924
Account-Session Id: 00000068
Nas-Port: Unknown
User name: 001f.ca3f.7924
Formatted User name: unknown
Client User name: unknown
Outer VLAN ID: 250
Subscriber Label: 0x000001db
Created: Mon Apr 20 19:32:49 2015
State: Activated
Authentication: unauthenticated
Authorization: authorized
Access-interface: PW-Ether20.250 Policy Executed:
policy-map type control subscriber IPoE_WDAAR_PWHE
event Session-Start match-first [at Mon Apr 20 19:32:49 2015]
class type control subscriber DHCPv4 do-until-failure [Succeeded]
5 authorize aaa list WDAAR [Succeeded]
10 activate dynamic-template WDAAR_PWHE_DT [Succeeded]
Session Accounting: disabled
Last COA request received: unavailable
Verificare ora la connettività di layer 3 del sottoscrittore BNG su PWHE.
RP/0/RSP0/CPU0:ACDC-ASR9000-1#ping 192.168.44.254 Mon Feb 23 19:37:58.188 UTC Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.44.254, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms RP/0/RSP0/CPU0:ACDC-ASR9000-1#
Risoluzione dei problemi
In questa sezione vengono fornite informazioni che è possibile utilizzare per risolvere i problemi relativi alla configurazione e verificare lo stato di xconnect su ASR9K.
Comando per verificare la configurazione di ASR9K
Questi comandi possono essere utilizzati per verificare che la configurazione sia corretta su ASR9K.
- show running-configuration l2vpn
- show running-configuration int PW-Ether<Numero-Interfaccia>
- show running-configuration mpls ldp
- show running-configuration generic-interface-list
Assegno L2VPN XC
controllare la connessione xconnect. xconnect (e quindi AC e PW) deve essere attivo. È possibile utilizzare questi comandi per verificare lo stato.
- mostra riepilogo xconnect l2vpn
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show l2vpn xconnect summary Thu May 21 05:40:05.068 UTC Number of groups: 1 Number of xconnects: 1 Up: 1 Down: 0 Unresolved: 0 Partially-programmed: 0 AC-PW: 1 AC-AC: 0 PW-PW: 0 Monitor-Session-PW: 0 Number of Admin Down segments: 0 Number of MP2MP xconnects: 0 Up 0 Down 0 Advertised: 0 Non-Advertised: 0 Number of CE Connections: 0 Advertised: 0 Non-Advertised: 0 Backup PW: Configured : 0 UP : 0 Down : 0 Admin Down : 0 Unresolved : 0 Standby : 0 Standby Ready: 0 Backup Interface: Configured : 0 UP : 0 Down : 0 Admin Down : 0 Unresolved : 0 Standby : 0
show l2vpn xconnect interface <Interface> detail OR show l2vpn xconnect detai
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show l2vpn xconnect interface pw-eth20 detail
Thu May 21 05:40:55.789 UTC
Group PWHE, XC ASR1K, state is up; Interworking none
AC: PW-Ether20, state is up
Type PW-Ether
Interface-list: BE20_ONLY
Replicate status:
BE20: success
Gi0/0/1/18: success
Gi0/0/1/19: success
MTU 1500; interworking none
Internal label: 16001
Statistics:
packets: received 52970, sent 0
bytes: received 3485714, sent 0
PW: neighbor 10.2.2.2, PW ID 2020, state is up ( established )
PW class asr1k, XC ID 0xc0000001
Encapsulation MPLS, protocol LDP
Source address 10.1.1.1
PW type Ethernet, control word disabled, interworking none
PW backup disable delay 0 sec
Sequencing not set
PW Status TLV in use
MPLS Local Remote
------------ ------------------------------ -----------------------------
Label 16002 17
Group ID 0x920 unknown
Interface PW-Ether20 unknown
MTU 1500 1500
Control word disabled disabled
PW type Ethernet Ethernet
VCCV CV type 0x2 0x2
(LSP ping verification) (LSP ping verification)
VCCV CC type 0x6 0x6
(router alert label) (router alert label)
(TTL expiry) (TTL expiry)
------------ ------------------------------ -----------------------------
Incoming Status (PW Status TLV):
Status code: 0x0 (Up) in Notification message
Outgoing Status (PW Status TLV):
Status code: 0x0 (Up) in Notification message
MIB cpwVcIndex: 3221225473
Create time: 21/05/2015 02:52:43 (02:48:12 ago)
Last time status changed: 21/05/2015 05:21:17 (00:19:38 ago)
Last time PW went down: 21/05/2015 03:10:45 (02:30:10 ago)
Statistics:
packets: received 52970, sent 0
bytes: received 3485714, sent 0
Controllo dell'elenco delle interfacce
Visualizzare l'elenco di interfacce utilizzato dal PWHE: deve esistere e disporre delle interfacce appropriate.
- show generic-interface-list name <NOME>
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show generic-interface-list name BE20_ONLY Thu May 21 05:43:26.649 UTC generic-interface-list: BE20_ONLY (ID: 1, interfaces: 3) Bundle-Ether20 - items pending 0, downloaded to FIB GigabitEthernet0/0/1/18 - items pending 0, downloaded to FIB GigabitEthernet0/0/1/19 - items pending 0, downloaded to FIB Number of items: 1 List is downloaded to FIB
Verifica PWHE utilizzato da un elenco di interfacce
L'output privato seguente indica quali interfacce membro sono "attive", ovvero quali sono state scaricate in FIB.
- show l2vpn generic-interface-list name <NOME>
- show l2vpn generic-interface-list private
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show l2vpn generic-interface-list name BE20_ONLY detail
Thu May 21 05:39:04.983 UTC
Generic-interface-list: BE20_ONLY (ID: 1, interfaces: 3)
Bundle-Ether20 - items pending 0
GigabitEthernet0/0/1/18 - items pending 0
GigabitEthernet0/0/1/19 - items pending 0
Number of items: 1
PW-Ether: 20
Verificare che MA disponga di PWHE con le informazioni corrette
Le informazioni sull'elenco di interfacce, il peso variabile, il tipo VC, ecc., devono essere impostate correttamente in MA.
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show l2vpn ma pwhe interface PW-Ether 20 private
Thu May 21 05:36:28.170 UTC
Interface: PW-Ether20 Interface State: Up, Admin state: Up
Interface handle 0x920
MTU: 1514
BW: 10000 Kbit
Interface MAC addresses (1 address):
10f3.1172.02c5
IDB is not in Replicate Linked List
IDB is not in Create Linked List
IDB is not in Attr Linked List
Opaque flags: 0xe
Flags: 0x3c
Valid : IFH, MTU, MAC, BW
MA trace history [Num events: 32]
---------------------------------------------------
Time Event Value Sticky Many
==== ===== ========== ====== ====
05/21/2015 02:56:05 Remove retry list 0x3 No No
05/21/2015 02:56:05 IDB Set flag 0x3c No No
05/21/2015 03:08:26 IDB Set State 0x1 No No
05/21/2015 03:08:26 IM publish attr 0x45 No No
05/21/2015 03:08:26 IM update init-data 0x1e No No
05/21/2015 03:08:26 IDB Set flag 0x3c No No
05/21/2015 03:08:26 Remove retry list 0x3 No No
05/21/2015 03:08:26 IDB Set flag 0x3c No No
05/21/2015 03:09:54 IDB Set State 0 No No
05/21/2015 03:09:54 IM publish attr 0x45 No No
05/21/2015 03:09:54 IM publish attr 0x52 No No
05/21/2015 03:09:54 IM update init-data 0x1e No No
05/21/2015 03:09:54 IDB Set flag 0x3c No No
05/21/2015 03:09:54 Remove retry list 0x3 No No
05/21/2015 03:09:54 IDB Set flag 0x3c No No
05/21/2015 03:09:54 Remove retry list 0x3 No No
05/21/2015 03:09:54 IDB Set flag 0x3c No No
05/21/2015 03:10:45 IDB Set State 0x1 No No
05/21/2015 03:10:45 IM publish attr 0x45 No No
05/21/2015 03:10:45 IM update init-data 0x1e No No
05/21/2015 03:10:45 IDB Set flag 0x3c No No
05/21/2015 03:10:45 Remove retry list 0x3 No No
05/21/2015 03:10:45 IDB Set flag 0x3c No No
05/21/2015 05:21:17 IDB Set State 0 No No
05/21/2015 05:21:17 IM publish attr 0x45 No No
05/21/2015 05:21:17 IM publish attr 0x52 No No
05/21/2015 05:21:17 IM update init-data 0x1e No No
05/21/2015 05:21:17 IDB Set flag 0x3c No No
05/21/2015 05:21:17 Remove retry list 0x3 No No
05/21/2015 05:21:17 IDB Set flag 0x3c No No
05/21/2015 05:21:17 Remove retry list 0x3 No No
05/21/2015 05:21:17 IDB Set flag 0x3c No No
CLIENT MA trace history [Num events: 27]
---------------------------------------------------
Time Event Value Sticky Many
==== ===== ========== ====== ====
05/21/2015 02:54:01 IM Notify Up 0x50049e10 No No
05/21/2015 02:54:01 FSM state change 0x200 No No
05/21/2015 02:54:01 FSM state change 0x2030d No No
05/21/2015 02:54:02 Double restart detected 0x5 No No
05/21/2015 02:55:00 I/f created/added 0x4000540 No No
05/21/2015 02:55:00 I/f created/added 0x4000580 No No
05/21/2015 02:55:00 I/f created/added 0x4000540 No No
05/21/2015 02:55:00 I/f created/added 0x4000580 No No
05/21/2015 02:55:00 Intf list change 0x3000300 No No
05/21/2015 02:55:00 Intf add error 0x4000540 No No
05/21/2015 02:55:00 Intf add error 0x4000580 No No
05/21/2015 02:55:00 FSM state change 0x30505 No No
05/21/2015 02:55:01 Replicate result 0x13fe No No
05/21/2015 02:55:01 FSM state change 0x5060b No No
05/21/2015 02:55:01 I/f up 0x4000580 No No
05/21/2015 02:55:01 I/f up 0x4000580 No No
05/21/2015 02:55:02 I/f up 0x4000540 No No
05/21/2015 02:55:02 I/f up 0x4000540 No No
05/21/2015 02:56:05 Added to peer 0x6060606 No No
05/21/2015 02:56:05 FSM state change 0x60704 No No
05/21/2015 02:56:05 Fill VIMI attr 0x20002 No No
05/21/2015 03:08:26 FSM state change 0x70605 No No
05/21/2015 03:09:54 FSM state change 0x60704 No No
05/21/2015 03:09:54 Fill VIMI attr 0x20002 No No
05/21/2015 03:10:45 FSM state change 0x70605 No No
05/21/2015 05:21:17 FSM state change 0x60704 No No
05/21/2015 05:21:17 Fill VIMI attr 0x20002 No No
PW-HE IDB client data
---------------------
IDB handle 0x5016db2c
Dot1q vlan: 0x81000000
Label: 16001
Remote VC label: 17
Remote PE: 10.2.2.2
Use flow-label on tx: N
L2-overhead: 0
VC-type: 5
CW: N
FSM state: 'Up'(7)
Fwding is up: Y, got route update: Y
Use OWNED_RESOURCE fwding: N
OWNED_RESOURCE fwding is up: N
OWNED_RESOURCE data: 0
Replication error msg has been printed: N
VIF MA reg_handle: 50049e10
PIC array:
(nil)
Replicate retry count: 0
Configured i/f list name: 'BE20_ONLY'
From L2VPN i/f list name: 'BE20_ONLY', i/f list id: 1
L3 i/f:'Bundle-Ether20', idx=0, repl_status 1, fwding up:N, active:Y
L3 i/f:'GigabitEthernet0/0/1/18', idx=1, repl_status 1, fwding up:Y, active:Y
L3 i/f:'GigabitEthernet0/0/1/19', idx=2, repl_status 1, fwding up:Y, active:Y
List intf: 0x5016e154, PLs size:4, num in use:2
I/f:'Gi0/0/1/18', ifh:0x4000540, bundle: 0xb20, ifl idx:1, in-use:Y, misconfig:Y, in peer route:Y, VIMI active:Y
Repl:Y pending:N failed:N not supp:N, unrepl pending:N failed:N, up:Y us:3
I/f:'Gi0/0/1/19', ifh:0x4000580, bundle: 0xb20, ifl idx:2, in-use:Y, misconfig:Y, in peer route:Y, VIMI active:Y
Repl:Y pending:N failed:N not supp:N, unrepl pending:N failed:N, up:Y us:3
I/f:'', ifh:0x0, bundle: 0x0, ifl idx:0, in-use:N, misconfig:N, in peer route:N, VIMI active:N
Repl:N pending:N failed:N not supp:N, unrepl pending:N failed:N, up:N us:0
I/f:'', ifh:0x0, bundle: 0x0, ifl idx:0, in-use:N, misconfig:N, in peer route:N, VIMI active:N
Repl:N pending:N failed:N not supp:N, unrepl pending:N failed:N, up:N us:0
---------------------------------------------------
Verifica informazioni di riepilogo PWHE
Verificare che i contatori nell'output siano corretti:
- show l2vpn pwhe summary
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show l2vpn pwhe summary Thu May 21 05:35:59.381 UTC Number of PW-HE interfaces: 1 Up: 1 Down: 0 Admindown: 0 PW-Ether: 1 Up: 1 Down: 0 Admindown: 0 PW-IW: 0 Up: 0 Down: 0 Admindown: 0
Etichette assegni
Controllare l'etichetta nella tabella delle etichette. Con questo comando è innanzitutto necessario ottenere le etichette interne dalle informazioni xconnect.
- visualizzazione dei dettagli di xconnect l2vpn
quindi cercare internal Label nell'output ed eseguire questo comando show per verificare l'associazione tra etichetta e interfaccia su ASR9K.
- mostra dettaglio etichetta tabella etichette mpls <internal_label>
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show l2vpn xconnect detail
Thu May 21 05:27:11.762 UTC
Group PWHE, XC ASR1K, state is up; Interworking none
AC: PW-Ether20, state is up
Type PW-Ether
Interface-list: BE20_ONLY
Replicate status:
BE20: success
Gi0/0/1/18: success
Gi0/0/1/19: success
MTU 1500; interworking none
Internal label: 16001
Statistics:
packets: received 27293, sent 0
bytes: received 1996176, sent 0
PW: neighbor 10.2.2.2, PW ID 2020, state is up ( established )
PW class asr1k, XC ID 0xc0000001
Encapsulation MPLS, protocol LDP
Source address 10.1.1.1
PW type Ethernet, control word disabled, interworking none
PW backup disable delay 0 sec
Sequencing not set
RP/0/RSP0/CPU0:ACDC-ASR9000-1#show mpls label table label 16001 detail Thu May 21 05:27:55.760 UTC Table Label Owner State Rewrite ----- ------- ---------------------------- ------ ------- 0 16001 L2VPN:Active InUse Yes (PW-HE, vers:0, intf=PE20)
Sessioni/perdita di traffico non visualizzate
Se la sessione non viene visualizzata, verificare se i pacchetti ignorati in NP. È possibile utilizzare questi comandi per visualizzare il rilascio del pacchetto in NP su ASR9K.
- clear counters
- visualizzazione dei dettagli di xconnect l2vpn | include il pacchetto
- cancella tutti i contatori np dei controller
- mostra tutti i contatori np controller
Comandi Show correlati a BNG
Utilizzare questi comandi per controllare le informazioni relative a BNG su ASR9K.
- mostra riepilogo di tutte le sessioni del sottoscrittore
- show subscriber manager disconnect-history unique summary
- mostra totale debug statistiche di subscriber manager
- mostra totale riepilogo statistiche di gestione sottoscrittori
- show subscriber manager trace event/error
Debug da abilitare
Se la sessione non è stata rilevata su ASR9K e non è stato trovato alcun pacchetto scartato su NP, è possibile attivare questi debug su ASR9K per capire perché la sessione non viene rilevata in ASR9K.
- debug l2vpn ea pwhe platform verbose
- debug l2vpn forwarding platform common all
- percorso api debug pm <percorso>
- percorso errore debug pm <percorso>
- percorso errori api uidb debug <location>
Escalation
Se il problema persiste, rivolgersi a Cisco TAC e raccogliere il messaggio Show tech da ASR9K.
- show tech-support subscriber
- show tech-support l2vpn
Cronologia delle revisioni
| Revisione | Data di pubblicazione | Commenti |
|---|---|---|
1.0 |
20-Oct-2017 |
Versione iniziale |
Feedback