Junosphere – inaccessible VMXes
I usually use the ‘experimental’ VMX in my Junosphere topologies because I don’t like the VJX all that much. The VJX has security code in it, so it’s not quite like an MX really. Also I’ve seen oddities where it came up in flow mode with a default firewall policy of denying everything, and I was never able to work out why.
So instead I use the VMX for everything – which is better these days because it doesn’t use two VM units for the data and control planes like it used to. Why VMX is still ‘experimental’ after so long is a mystery to me.
However one thing just keeps cropping up with this that is just a bit annoying. Every so often I start a topology I know was working, but one or more routers aren’t accessible for some reason. The problem is usually caused by the way Junosphere has put the management address onto the VM. To get access to the VM you instead need to telnet to it via the console server at 10.233.255.254 using a specific port number
The fxp0 IP address should be created in the Continue reading