I still don't know if the vlan configuration option should be available.
In the mean time i devised a workaround.
I created a bridge IRB
and placed the two gigabit ethernet ports in bridge-group 1.
I also created a loopback device because i found out the device
also lacks the no autostate command.
I gave the BVI device the IP address of what normally the vlan 1
ip address would have been. So for instance 192.168.3.1/24
I created an SLA track with line protocol watch for monitoring the
up/down state of the bvi device. As soon as the BVI device goes down
because of both gigabit ethernet devices become unconnected i run
an eem script for removing the IP address from the BVI and placing
it on the loopback. In this way i am able to keep an active management
IP (for instance 192.168.3.1) active for my VPN tunnel to reach.
I also have a timer script that keeps pinging the device at the other
end of the VPN tunnel in order to automaticly create a VPN tunnel.
It's a bit slow, it takes 8 minutes from power up to VPN tunnel
active. But it's stable so that is what counts.
Good luck to anyone also involved in getting this device to run.