We are looking to replace all of our 2801 ISR's with the new 4321 replacement which is running IOS-XR. I am trying to verify the config so have setup GNS3 running XRv
System image file is "bootflash:disk0/xrvr-os-mbi-6.0.0/mbixrvr-rp.vm"
The first hurdle we cannot clear is the setting up of a DHCP Server:
pool vrf default ipv4 voice
network 10.1.1.0/24
!
dhcp ipv4
profile VOICE server
pool voice
dns-server 8.8.8.8
subnet-mask 255.255.255.0
default-router 10.1.1.1
!
interface GigabitEthernet0/0/0/1 server profile VOICE
!
interface GigabitEthernet0/0/0/1
ipv4 address 10.1.1.1 255.255.255.0
ipv4 access-group inbound ingress
!
I can see the interface with mode 'SR':
RP/0/0/CPU0:ios#sh dhcp ipv4 server interface
Fri Jul 29 11:52:30.094 UTC
Codes: Amb - Ambiguous VLAN, B - Base, R - Relay, P - Proxy,
SR - Server, S - Snoop, C - Client, INV - Invalid
CID - Circuit Id, RID - Remote Id, INTF - Interface
Interface Mode Profile Name Amb Lease Limit
------------------------------------------------------------------------------------
Gi0/0/0/1 SR VOICE No None
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: TP2514: L3 RX: vrfid 0x60000000 (1610612736), ifh 0x200 (512), ifhsec 0x0 (0)
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: TP564: L3 Packet RX from addr = 0.0.0.0, port = 68, application len 576, vrf 0x60000000 (1610612736), tbl 0xe0000000 (3758096384)
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: ---------- IPv4 DHCPD --- dhcpd_iox_l3_conn_hlr -------
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: VRF name (id): default (0x60000000)
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: L3 src: 0.0.0.0
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: L3 dst: 255.255.255.255
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: L3 src port: 68
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: L3 dst port: 67
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: metadata: L3 input Intf: GigabitEthernet0_0_0_1
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: metadata: Output Intf: Null
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: metadata: FROM: L3
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: metadata: NETWORK_ORDER
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: op: BOOTREQUEST
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: chaddr: cc03.2b9c.0010
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: xid: 0x00001397
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: flags: 0x8000 (broadcast)
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: ciaddr: 0.0.0.0
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: yiaddr: 0.0.0.0
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: siaddr: 0.0.0.0
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: giaddr: 0.0.0.0
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: cookie: 0x63538263
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: option: MESSAGE_TYPE: DISCOVER
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: option: MAX_MESSAGE_SIZE data: "0x04-80"
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: option: CLIENT_IDENTIFIER data: "0x00-63-69-73-63-6f-2d-63-63-30-33-2e-32-62-39-63-2e-30-30-31-30-2d-45-74-31-2f-30"
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: option: HOST_NAME data: "R3"
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: option: PARAMETER_REQUEST data: "0x01-06-0f-2c-03-21-96-2b"
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: pktRx id 59: option: OPTION_OVERLOAD data: "0x03"
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: dhcpd_proxy_os_inc_stat_multi stats ptr not null for vrf 60000000 matches l3intf
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: dhcpd_proxy_os_inc_stat_multi stats ptr not null for vrf 60000000 matches l3intf
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD SERVER: TP1961: DISCOVER from chaddr cc03.2b9c.0010 in proxy mode dropped
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD SERVER: TP1501: Null client handle
RP/0/0/CPU0:Jul 29 11:55:34.292 : dhcpd[1083]: DHCPD: TP2688: Process invalid packet error, proxy mode
RP/0/0/CPU0:Jul 29 11:55:38.701 : dhcpd[1083]: DHCPD: TP563: L3 packet event received
RP/0/0/CPU0:Jul 29 11:55:38.701 : dhcpd[1083]: DHCPD: TP2514: L3 RX: vrfid 0x60000000 (1610612736), ifh 0x200 (512), ifhsec 0x0 (0)
RP/0/0/CPU0:Jul 29 11:55:38.701 : dhcpd[1083]: DHCPD: TP564: L3 Packet RX from addr = 0.0.0.0, port = 68, application len 576, vrf 0x60000000 (1610612736), tbl 0xe0000000 (3758096384)
RP/0/0/CPU0:ios#sh dhcp ipv4 server statistics
Fri Jul 29 11:59:59.583 UTC
VRF | RX | TX | DR |
-------------------------------------------------------------------------------------------
default | 0 | 0 | 0 |
**nVSatellite | 0 | 0 | 0 |
I can see packets hitting 'base' but cant seem to find much documentation about the mode 'base' and how this links to 'server'
RP/0/0/CPU0:ios#sh dhcp ipv4 base statistics
Fri Jul 29 12:00:47.410 UTC
VRF | RX | TX | DR |
-------------------------------------------------------------------------------------------
default | 117 | 0 | 117 |
**nVSatellite | 0 | 0 | 0 |
It would seem from the debug above that the interface hit is in proxy mode rather than server? any ideas? how close is the XRv config to what we may expect from a 4321?
Many Thanks
