Just wanted to confirm that I was able to get DMVPN runing on this platform. Just tested it out right now:
ESR63000(config-if)#do sh plat
Chassis type: ESR-6300-CON-K9
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ESR-6300-CON-K9 ok 00:49:26
0/0 ESR-6300-2x1GE ok 00:47:28
0/1 ESR-6300-ES-4 ok 00:47:28
R0 ESR-6300-CON-K9 ok, active 00:49:26
F0 ESR-6300-CON-K9 ok, active 00:49:26
P0 PWR-12V ok 00:48:27
ESR63000(config-if)#
ESR63000(config)#int tun100
ESR63000(config-if)#no shut
ESR63000(config-if)#end
ESR63000#
*Aug 28 22:22:56.628: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is ON
ESR63000#
ESR63000#
*Aug 28 22:22:57.620: %SYS-5-CONFIG_I: Configured from console by console
ESR63000#
ESR63000#
*Aug 28 22:22:58.616: %LINK-3-UPDOWN: Interface Tunnel100, changed state to up
ESR63000#
*Aug 28 22:22:59.617: %LINEPROTO-5-UPDOWN: Line protocol on Interface Tunnel100, changed state to up
ESR63000#
ESR63000(config-if)#do sh dmvpn
Legend: Attrb --> S - Static, D - Dynamic, I - Incomplete
N - NATed, L - Local, X - No Socket
T1 - Route Installed, T2 - Nexthop-override, B - BGP
C - CTS Capable, I2 - Temporary
# Ent --> Number of NHRP entries with same NBMA peer
NHS Status: E --> Expecting Replies, R --> Responding, W --> Waiting
UpDn Time --> Up or Down Time for a Tunnel
==========================================================================
Interface: Tunnel100, IPv4 NHRP Details
Type:Spoke, NHRP Peers:1,
# Ent Peer NBMA Addr Peer Tunnel Add State UpDn Tm Attrb
----- --------------- --------------- ----- -------- -----
1 10.44.92.87 10.1.1.254 UP 00:00:31 S
ESR63000(config-if)#
ESR63000(config-if)#do sh cry sess
Crypto session current status
Interface: Tunnel100
Profile: IKEv2_PROFILE
Session status: UP-ACTIVE
Peer: 10.44.92.87 port 500
Session ID: 4
IKEv2 SA: local 10.47.113.18/500 remote 10.44.92.87/500 Active
IPSEC FLOW: permit 47 host 10.47.113.18 host 10.44.92.87
Active SAs: 2, origin: crypto map
ESR63000(config-if)#
ESR63000(config-if)#