How to use BDIs with DHCP on 4221 Router

[brberg05]

I am trying to configure DHCP so that it can use two physical ports on a Cisco Router. I would like to use two ports for redundancy and believe that the only way to do this is with BDIs because (1) the entire network on a subinterface must match the DHCP pool network and (2) subinterface networks cannot overlap. However, DHCP is not working with the configuration provided below.

RTR3(config)#do show run
Building configuration...

Current configuration : 4287 bytes
!
! Last configuration change at 17:20:34 UTC Wed Mar 13 2024
!
version 16.6
service timestamps debug datetime msec
service timestamps log datetime msec
platform qfp utilization monitor load 80
no platform punt-keepalive disable-kernel-core
!
hostname RTR3
!
boot-start-marker
boot-end-marker
!
!
! card type command needed for slot/bay 0/1
!
no aaa new-model
!
!
ip dhcp pool VLAN10
network 10.1.8.0 255.255.252.0
default-router 10.1.0.1
!
ip dhcp pool VLAN20
network 10.1.20.0 255.255.252.0
default-router 10.1.0.2
!
ip dhcp pool VLAN30
network 10.1.28.0 255.255.252.0
default-router 10.1.0.1
!
ip dhcp pool vlan10
!
!
!
no login on-success log
!
!
!
!
!
!
!
subscriber templating
!
!
multilink bundle-name authenticated
!
!
!
crypto pki trustpoint TP-self-signed-3632866187
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3632866187
revocation-check none
rsakeypair TP-self-signed-3632866187
!
!
crypto pki certificate chain TP-self-signed-3632866187
certificate self-signed 01
30820330 30820218 A0030201 02020101 300D0609 2A864886 F70D0101 05050030
31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274
69666963 6174652D 33363332 38363631 3837301E 170D3234 30333133 31363331
35345A17 0D333030 31303130 30303030 305A3031 312F302D 06035504 03132649
4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D33 36333238
36363138 37308201 22300D06 092A8648 86F70D01 01010500 0382010F 00308201
0A028201 0100B187 36B2C103 F4E51961 6DB98A77 1DE970ED 0867FF48 ED7B86AD
6E7098F7 97B03AE9 F25F0A3D 75132215 973F5DE0 120B3747 7CB36AE4 89228848
78A88AAA 00D4E70D 0B6046EF 8CEA4D51 43FA1E01 5EF89E6E 1914A610 3CE5B103
7069638A 08FDA1EE 82D17FD6 6875003E 2E79AA65 192E602B CF9FC185 ABD4E063
0558AEFE 53EAEE97 DFFDDC03 9481D4B9 60B2F1BC 05D6B844 B46D3E7A 4E49D2BD
81D9F78F 6516F909 0D15A1ED 10B01807 C730181F 6D762865 A88F8225 344CD5B5
CE5F2EF1 B114EF33 CB739A91 83D6F48F D7CFE7C4 A1380246 E0F0C754 D64CE0C7
9E27B0AF A7256D34 7FA915F9 3F2E55A9 8350C920 578079FF F39A60AC A74D8C41
F0477CC4 1A830203 010001A3 53305130 0F060355 1D130101 FF040530 030101FF
301F0603 551D2304 18301680 1448C8B0 F992A4B3 8DD39C76 ED7FB29A 46B8C046
77301D06 03551D0E 04160414 48C8B0F9 92A4B38D D39C76ED 7FB29A46 B8C04677
300D0609 2A864886 F70D0101 05050003 82010100 925AE39A 5F052B93 ED51B8B7
1F9AE6EB 3DF4D7F0 CB0BA96E 31BB88E2 BB9FC2E4 29F09C3C FA3C6DE3 3B304197
AE1AFDC5 BD7D4905 27FB0D46 E0592182 5A4FF2D4 975150B1 A42C04E8 E58EEBC0
C3E46381 7E775290 E8A0DD63 0B3362FC D14C26BD 8BE35EC0 17317E7E FE9ABD05
419A109B 0D9E786F B5F21447 8BB2C06B 006AD29B 16F30D48 4AAF11FB 8D5438B8
04AB6B3B 3D4D4DCC D87E3278 E1023FE9 28DCF0D3 F43E518B 02CAFDE4 DC88542A
36DC4F0B 273CA52F F5B6B38A CF32CF2C 0F1E1FBB 9DF50792 5CBB3D9F 7E80EB6E
23EB176D 56375904 49B7A3BB 0F5F13E2 3D2D1F44 91946136 B796EC93 9DB99C2C
1A99D02D 52E0DA1B 6BB46ECB E983FE5C 4C0A7111
quit
!
!
license udi pid ISR4221/K9 sn FGL214390KZ
diagnostic bootup level minimal
spanning-tree extend system-id
!
!
!
!
redundancy
mode none
bridge-domain 10
bridge-domain 20
bridge-domain 30
!
!
!
bridge irb
!
!
!
!
!
interface Loopback0
ip address 172.16.0.3 255.255.255.0
!
interface GigabitEthernet0/0/0
no ip address
negotiation auto
service instance 10 ethernet
encapsulation dot1q 10
bridge-domain 10
!
service instance 20 ethernet
encapsulation dot1q 20
bridge-domain 20
!
service instance 30 ethernet
encapsulation dot1q 30
bridge-domain 30
!
interface GigabitEthernet0/0/1
no ip address
negotiation auto
service instance 10 ethernet
encapsulation dot1q 10
bridge-domain 10
!
service instance 20 ethernet
encapsulation dot1q 20
bridge-domain 20
!
service instance 30 ethernet
encapsulation dot1q 30
bridge-domain 30
!
!
interface BDI10
ip address 10.1.10.1 255.255.252.0
encapsulation dot1Q 10
!
interface BDI20
ip address 10.1.20.1 255.255.252.0
encapsulation dot1Q 20
!
interface BDI30
ip address 10.1.30.1 255.255.252.0
encapsulation dot1Q 30
!
ip forward-protocol nd
ip http server
ip http authentication local
ip http secure-server
!
!
!
!
!
!
control-plane
!
!
line con 0
transport input none
stopbits 1
line vty 0 4
login
!
!
!
!
!
!
end

[MHM Cisco World]

Sorry I dont get your Q.

MHM

[balaji.bandi]

First where is this 2 Physical Interface connected ( Gig Interface?)

The DHCP Server inside Router (the user connected respected VLAN should get DHCP - if you configured correctly with right Gateway on the DHCP Config)

ip dhcp pool VLAN10
network 10.1.10.0 255.255.252.0
default-router 10.1.10.1
!
ip dhcp pool VLAN20
network 10.1.20.0 255.255.252.0
default-router 10.1.20.1
!
ip dhcp pool VLAN30
network 10.1.30.0 255.255.252.0
default-router 10.1.30.1

By saying that above, if the Gig0/0/0 and Gig0/0/1 connected to switch, you can use port-channel also on the switch and router with sub-interface vlan tag