Hi rahul,
Yes, it is. I have completed all of that, and, as an add on, for the vMX you also have to add the following command:
set chassis fpc 0 loopback-device-count 1
However, that has brought up another issue.... for the si interface I have configured the following:
set interfaces si-0/0/0 hierarchical-scheduler maximum-hierarchy-levels 2
set interfaces si-0/0/0 encapsulation generic-services
set interfaces si-0/0/0 unit 0 family inet
And for the chassis the following:
set chassis fpc 0 pic 0 tunnel-services bandwidth 1g
set chassis fpc 0 pic 0 inline-services bandwidth 1g
set chassis fpc 0 pic 0 max-queues-per-interface 8
set chassis fpc 0 lite-mode
set chassis fpc 0 flexible-queuing-mode
But, if I try to add the following liune to the dynamic-profile:
set dynamic-profiles dyn-hex-lns-profile interfaces "$junos-interface-ifd-name" unit "$junos-interface-unit" dial-options l2tp-interface-id l2tp-encapsulation
And then commit, I get the following error:
error: Inet family must be configured for the dial-option
error: foreign file propagation (ffp) failed
So, although "inet" is configured on the si interface, it does not seem to be recognising it, unless this is because it wants some configuraiton on ge-0/0/0 instead of ge-0/0/2.... I'll give that a try and let you know the results...