cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1859
Views
0
Helpful
16
Replies

ASR9001 BNG on PW-HE.

poiz
Level 1
Level 1

Hello, i'm trying to migrate from BE to pw-he subscriber. Now i have an issue that i do not see dhcp offer from dhcp proxy to client in tcpdump, which i've been collected right next to BNG. 

 

It seems that dhcpd working correctly:

Lease
MAC Address IP Address State Remaining Interface VRF Sublabel
-------------- -------------- --------- --------- ------------------- --------- ----------
cc2d.e006.0d62 10.253.178.226 OFFER_SENT 58 PE2100.2100 default 0x75

RP/0/RSP0/CPU0:Jun 10 17:59:58.833 MSK: dhcpd[1101]: DHCPD: TP2663: Lease proxy - client<-server lease timer started at 1560178798 for 60 sec lease, 60 secs to expiry
RP/0/RSP0/CPU0:Jun 10 17:59:58.833 MSK: dhcpd[1101]: DHCPD: TP572: L3 packet TX bcast on intf PW-Ether2100.2100 to port 68, source X.X.X.X, vrf 0x60000000 (1610612736), tbl 0xe0000000 (3758096384)
RP/0/RSP0/CPU0:Jun 10 17:59:58.833 MSK: dhcpd[1101]: DHCPD: dhcpd_iox_vlan_processing: configured val of inner-cos is 6
RP/0/RSP0/CPU0:Jun 10 17:59:58.834 MSK: dhcpd[1101]: DHCPD: dhcpd_iox_vlan_processing: cofigured val of outer-cos is 6
RP/0/RSP0/CPU0:Jun 10 17:59:58.834 MSK: dhcpd[1101]: DHCPD: TP2744: Sending packet on VLAN for client cc2d.e006.0d62 on interface PW-Ether2100.2100
RP/0/RSP0/CPU0:Jun 10 17:59:58.834 MSK: dhcpd[1101]: DHCPD: dhcpd_iox_vlan_processing: vlan_id[0] after possible OR with outer-cos: 0xc834
RP/0/RSP0/CPU0:Jun 10 17:59:58.834 MSK: dhcpd[1101]: DHCPD: dhcpd_iox_vlan_processing: vlan_id[1] after possible OR with inner-cos: 0xcffa
RP/0/RSP0/CPU0:Jun 10 17:59:58.834 MSK: dhcpd[1101]: DHCPD: Calling send_pak with pak 0xddc78667

RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: ---------- IPv4 DHCPD --- dhcpd_iox_l3_broadcast_packet -------
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: VRF name (id): default (0x60000000)
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: L3 src: X.X.X.X
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: L3 dst: 255.255.255.255
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: L3 dst port: 68
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: L3 input Intf: Bundle-Ether1.801
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Output Intf: Null
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: FROM: L3
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: NETWORK_ORDER
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan Info
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan EtherType 1: 0x0
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan Priority 1: 0 (0x0)
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan Format 1: 0 (0x0)
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan ID 1: 2100 (0x834)
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan EtherType 2: 0x0
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan Priority 2: 0 (0x0)
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan Format 2: 0 (0x0)
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: metadata: Vlan ID 2: 4090 (0xffa)
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93:
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: op: BOOTREPLY
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: chaddr: cc2d.e006.0d62
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: xid: 0x034d3c82
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: flags: 0x8000 (broadcast)
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: ciaddr: 0.0.0.0
RP/0/RSP0/CPU0:Jun 10 17:42:32.631 MSK: dhcpd[1101]: DHCPD: pktTx id 93: yiaddr: 10.253.178.226
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: siaddr: 0.0.0.0
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: giaddr: 0.0.0.0
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: cookie: 0x63825363
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: MESSAGE_TYPE: OFFER
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: SERVER_IDENTIFIER: X.X.X.X
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: LEASE_TIME: 300
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: RENEWAL_TIME: 150
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: REBINDING_TIME: 262
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: SUBNET_MASK data: "0xff-ff-80-00"
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: DOMAIN_NAME data: "rt.user.ru"
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: DEFAULT_ROUTER data: "0x0a-fd-80-01"
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: DOMAIN_NAME_SERVER data: "0xd5-f8-00-06-d5-f8-01-06"
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: STATIC_ROUTE data: "0xd5-f8-00-79-0a-fd-80-01"
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: NTP_SERVER data: "0x08-08-08-08-08-08-08-08"
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: VENDOR_SPECIFIC data: "0x01-04-00-00-00-02-02-04-00-00-00-01-ff"
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: RELAY_INFORMATION
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: RELAY_INFORMATION: CIRCUIT_ID: 0x00-04-0f-fa-00-01
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: pktTx id 93: option: RELAY_INFORMATION: REMOTE_ID: 0x01-0e-38-39-2e-32-30-38-2e-31-33-36-2e-31-34-38
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: dhcpd_iox_l3_broadcast_packet Success in send_pak()
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: dhcpd_proxy_os_inc_stat_multi stats ptr not null for vrf 60000000 matches l3intf
RP/0/RSP0/CPU0:Jun 10 17:42:32.632 MSK: dhcpd[1101]: DHCPD: TP2371: Process OFFER for chaddr cc2d.e006.0d62 - successful

interface PW-Ether2100.2100
mtu 1560
ipv4 unnumbered Loopback1
proxy-arp
arp learning disable
service-policy type control subscriber IPOE-POLICYMAP
encapsulation dot1q 2100 second-dot1q 4090
ipsubscriber ipv4 l2-connected
initiator dhcp

Maybe dhcp proxy doesn't work with pw-he, or there's any bug or something?

 

it's okay in this scenario:

int PW-Ether2100.2100
mtu 1560
ipv4 address 10.255.255.1 255.255.255.0
encapsulation dot1q 2100 second-dot1q 4090


ping 10.255.255.100
Mon Jun 10 16:31:00.613 MSK
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.255.255.100, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 2/3/6 ms

what i'm missing?

16 Replies 16

Aleksandar Vidakovic
Cisco Employee
Cisco Employee

DHCP doesn't really care about the type of interface. The solution with PW-Ether and DHCP proxy has to work. As the ping works when you configure the PW-Ether subinterface as L3, it should indicate that that the bridge domain on the access PE is correctly configured. You can also run "debug punt-inject l3-packets dhcpv4 detail" to see how are packets injected into the data-path. If the BNG is dropping the DHCP packets once they have reached the egress NP, the NP counters should give us a clue of the drop reason. 

RP/0/RSP0/CPU0:bng1#sh debug
Tue Jun 11 10:07:27.322 MSK

#### debug flags set from tty 'vty0' ####
punt protocol flag is ON with value '0x42###1##'

 

and there's no packets in debug.

 

after that i cleared subscriber and np counters:

RP/0/RSP0/CPU0:bng1#show controllers np counters all | i DROP
Tue Jun 11 10:06:19.147 MSK
542 MDF_PUNT_POLICE_DROP 647 0  ---- but it doesn't increment.

 

by the way - ios 6.5.3.

RP/0/RSP0/CPU0:bng1#show controllers np counters all
Tue Jun 11 10:17:20.184 MSK

Node: 0/0/CPU0:
----------------------------------------------------------------

Show global stats counters for NP0, revision v2

Last clearing of counters for this NP: 00:20:05

Read 15 non-zero NP counters:
Offset Counter FrameValue Rate (pps)
-------------------------------------------------------------------------------------
16 MDF_TX_LC_CPU 5060 4
21 MDF_TX_FABRIC 9863 6
37 PARSE_INTR_RECEIVE_CNT 619198 514
41 PARSE_INJ_RECEIVE_CNT 10247 6
49 PARSE_TM_LOOP_RECEIVE_CNT 5810 5
68 DBG_RSV_EP_L_RSV_ING_PUNT 4696 4
548 MDF_PUNT_RSP_VIA_HOST_PORT 364 0
609 MDF_LB_TM_LPBK0 5810 5
790 PUNT_DIAGS 20 0
902 PUNT_STATISTICS 4676 4
1235 PRS_HEALTH_MON 5810 5
1244 INTR_FRAME_TYPE_7 4676 4
1289 PARSE_LC_INJ_FAB_CNT 10227 6
1291 PARSE_LC_INJ_DIAGS_CNT 20 0
1501 PARSE_INJECT_TRACE_CNT 187 0


Show global stats counters for NP1, revision v2

Last clearing of counters for this NP: 00:20:05

Read 45 non-zero NP counters:
Offset Counter FrameValue Rate (pps)
-------------------------------------------------------------------------------------
0 NULL_STAT_0 496 1
16 MDF_TX_LC_CPU 18006 18
17 MDF_TX_WIRE 9913 8
33 PARSE_FAB_RECEIVE_CNT 9862 6
37 PARSE_INTR_RECEIVE_CNT 624394 518
41 PARSE_INJ_RECEIVE_CNT 422 0
45 PARSE_ENET_RECEIVE_CNT 9645 8
49 PARSE_TM_LOOP_RECEIVE_CNT 5810 5
53 PARSE_TOP_LOOP_RECEIVE_CNT 982 1
63 DBG_RSV_EP_L_RSV_ING_L3_IFIB 7588 6
64 DBG_RSV_EP_L_RSV_ING_L3_IFIB_MATCH 7588 6
65 DBG_RSV_EP_L_RSV_ING_L3_IFIB_PUNT_LOCAL 7588 6
67 DBG_RSV_EP_L_RSV_ING_L3_RSLTS_MATCH 7588 6
68 DBG_RSV_EP_L_RSV_ING_PUNT 18302 15
470 RSV_PWHE_DECAP_ING_CNT 982 1
524 MDF_PIPE_LPBK 982 1
542 MDF_PUNT_POLICE_DROP 647 0
609 MDF_LB_TM_LPBK0 5810 5
774 PUNT_CDP 22 0
786 PUNT_BUNDLE_PROTO 43 0
790 PUNT_DIAGS 20 0
832 PUNT_FOR_ICMP 155 1
850 PUNT_ADJ 21 0
902 PUNT_STATISTICS 9898 8
908 PUNT_NETIO_RP_TO_LC_CPU 351 0
958 PUNT_LLDP 41 0
1000 PUNT_UDLD 172 0
1040 PUNT_DHCP_BCAST 342 0
1235 PRS_HEALTH_MON 5810 5
1244 INTR_FRAME_TYPE_7 9898 8
1264 PARSE_ING_8023 40 0
1268 PARSE_ING_SLOW_PROTO 43 0
1273 PARSE_RSP_INJ_FAB_CNT 9862 6
1277 PARSE_EGR_INJ_PKT_TYP_UNKNOWN 9 0
1278 PARSE_EGR_INJ_PKT_TYP_IPV4 791 2
1280 PARSE_EGR_INJ_PKT_TYP_MPLS 7131 3
1282 PARSE_EGR_INJ_PKT_TYP_IPV4_PREROUTE 1931 1
1284 PARSE_EGR_INJ_PREROUTE_PUNT_FLAG 342 0
1290 PARSE_LC_INJ_PORT_CNT 402 0
1291 PARSE_LC_INJ_DIAGS_CNT 20 0
1415 PARSE_LLDP 41 0
1416 UNKNOWN_L2_ON_L3_DISCARD 1261 1
1435 PARSE_UDLD 194 0
1470 PARSE_PWHE_DECAP_ING_EP 982 1
1501 PARSE_INJECT_TRACE_CNT 187 0

 

These counters don't help much at this stage. Can you first check the DHCP counters to confirm which DHCP packets (if any) are reaching the DHCP process on the RP. Next step could be to run "debug punt-inject l3-packets dhcpv4 detail" to see how are DHCP packets received from fabric on RP CPU and injected from RP CPU to fabric.

show dhcp ipv4 proxy statistics
Mon Jul  1 10:04:10.422 MSK

                  VRF                     |      RX       |      TX       |       DR      |
-------------------------------------------------------------------------------------------
 default                                  |           20  |           30  |            0  |
 **nVSatellite                            |            0  |            0  |            0  |
 MGMT                                     |            0  |            0  |            0  |
 **eint                                   |            0  |            0  |            0  |
sh debug
Mon Jul  1 10:09:38.863 MSK

####  debug flags set from tty 'vty0'  ####
punt protocol flag is ON with value '0x42###1##'
show dhcp ipv4 proxy binding
Mon Jul  1 10:05:20.165 MSK

                                           Lease
 MAC Address      IP Address      State    Remaining       Interface          VRF      Sublabel
--------------  --------------  ---------  ---------  -------------------  ---------  ----------
cc2d.e006.0d62  10.253.178.234  OFFER_SENT 59         PE2222.1111          default    0x56

but as i already mentioned, debug punt-inject l3-packets dhcpv4 detail doesn't show anything, like there's no such packets.

Sorry, my bad. That debug won't help in this scenario. "debug dhcp ipv4 packet filter-id ..." will show what exactly is DHCP receiving. 

Yes, they are. I saw these packets already. But i don't see them outside of the BNG. I dumped port-channel right next to BNG and there i see only dhcp requests from client side. Like replies drops somewhere or goes not to proper interface.

 

RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: ---------- IPv4 DHCPD --- dhcpd_iox_l3_broadcast_packet -------
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: VRF name (id): default (0x60000000)
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: L3 src: LOOPBACK1
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: L3 dst: 255.255.255.255
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: L3 dst port: 68
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: L3 input Intf: Bundle-Ether1.801
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Output Intf: Null
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: FROM: L3
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: NETWORK_ORDER
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan Info
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan EtherType 1: 0x0
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan Priority 1: 0 (0x0)
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan Format 1: 0 (0x0)
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan ID 1: 2222 (0x8ae)
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan EtherType 2: 0x0
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan Priority 2: 0 (0x0)
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan Format 2: 0 (0x0)
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: metadata: Vlan ID 2: 4090 (0xffa)
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118:
RP/0/RSP0/CPU0:Jul 1 12:50:44.247 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: op: BOOTREPLY
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: chaddr: cc2d.e006.0d62
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: xid: 0xe72fab07
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: flags: 0x8000 (broadcast)
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: ciaddr: 0.0.0.0
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: yiaddr: 10.253.178.234
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: siaddr: 0.0.0.0
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: giaddr: 0.0.0.0
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: cookie: 0x63825363
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: MESSAGE_TYPE: OFFER
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: SERVER_IDENTIFIER: LOOPBACK1
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: LEASE_TIME: 300
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: RENEWAL_TIME: 150
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: REBINDING_TIME: 262
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: SUBNET_MASK data: "0xff-ff-80-00"
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: DOMAIN_NAME data: "rt.user.ru"
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: DEFAULT_ROUTER data: "0x0a-fd-80-01"
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: DOMAIN_NAME_SERVER data: "0xd5-f8-00-06-d5-f8-01-06"
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: STATIC_ROUTE data: "0xd5-f8-00-79-0a-fd-80-01"
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: NTP_SERVER data: "0x08-08-08-08-08-08-08-08"
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: VENDOR_SPECIFIC data: "0x01-04-00-00-00-02-02-04-00-00-00-01-ff"
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: RELAY_INFORMATION
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: RELAY_INFORMATION: CIRCUIT_ID: 0x00-04-0f-fa-00-01
RP/0/RSP0/CPU0:Jul 1 12:50:44.248 MSK: dhcpd[1101]: DHCPD_FILTER_PACKET: pktTx id 118: option: RELAY_INFORMATION: REMOTE_ID: 0x01-0e-38-39-2e-32-30-38-2e-31-33-36-2e-31-34-38

 

poiz
Level 1
Level 1

let's make necropost.

 

the same problem, but now it's iosxr-6.5.3. 

pw-he + bng + dhcp proxy

 

interface PW-Ether1
mtu 1614
attach generic-interface-list BE1
l2overhead 64

interface PW-Ether1.2883
description HOMENET VLAN 2883
mtu 1600
ipv4 unnumbered Loopback2
arp learning disable
service-policy type control subscriber IPOE-POLICYMAP
encapsulation dot1q 4090
ipsubscriber ipv4 l2-connected
initiator dhcp

 

l2vpn
pw-class PW-CL-MPLS
encapsulation mpls
transport-mode ethernet

 

xconnect group XC2883
p2p 2883
interface PW-Ether1
neighbor ipv4 LOOPBACK2 pw-id 2883
pw-class PW-CL-MPLS

 

dhcp proxy State: OFFER_SENT

 

Group XC2883, XC 2883, state is up; Interworking none
AC: PW-Ether1, state is up
Type PW-Ether
Interface-list: BE1
Replicate status:
BE1: success
Te0/0/2/0: success
Te0/0/2/1: success
MTU 1600; interworking none
Internal label: 24102
Statistics:
packets: received 771, sent 0
bytes: received 475594, sent 0
PW: neighbor LOOPBACK2, PW ID 2883, state is up ( established )
PW class PW-CL-MPLS, XC ID 0xa0000013
Encapsulation MPLS, protocol LDP
Source address LOOPBACK
PW type Ethernet, control word disabled, interworking none
PW backup disable delay 0 sec
Sequencing not set
LSP : Up

PW Status TLV in use
MPLS Local Remote
------------ ------------------------------ -----------------------------
Label 24163 1184
Group ID 0x79ba0 unknown
Interface PW-Ether1 unknown
MTU 1600 1600
Control word disabled disabled
PW type Ethernet Ethernet
VCCV CV type 0x2 0x2
(LSP ping verification) (LSP ping verification)
VCCV CC type 0x6 0x2
(router alert label) (router alert label)
(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: 2684354579
Create time: 26/01/2021 12:49:01 (01:57:01 ago)
Last time status changed: 26/01/2021 13:00:27 (01:45:34 ago)
Last time PW went down: 26/01/2021 12:58:59 (01:47:03 ago)
Statistics:
packets: received 771, sent 0
bytes: received 475594, sent 0

 

there's no outgoing packets in pseudowire. seems to me that the trouble is somewhere there, but i can't figure it out.

Did you try to put an IP address on the PW-HE interface first and do an ICMP test? If it's not working then you can focus on PW-HE itself, not the BNG part.

yup, i tried. several posts above.

Ok, my bad.

 

Did you try to run DHCP server on the BNG itself? I usually do my TS like that, so I can eliminate possible reasons.

No, i didn't. I use dhcp proxy on this router on bundle-ether interfaces and it works fine. The only difference between these two ways of termination - PWHE.

Is the PW destination resolved through a recursive route with multiple paths? If yes, this is not a supported config. If not, please raise a service request with our Technical Assistance Centre to have this triaged further.

 

best,

/Aleksandar

smailmilak
Level 4
Level 4

Well, you did your TS. You should open a TAC ticket.
If I would have this setup I would try to make it work, but unfortunately I don't have it.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: