I'm playing with vSRX (with active service contract) and I am totally stuck with Junos: 18.4R1.8.
1. I exported my configuration file
2. I deployed a brand new VM
3. I put 16Go ram and 8 vpu according the vSRX Deployment Guide
4. I injected the configuration with an iso
The configuration is loaded, I can connect with the fxp0 interface but all ge-0/0/x interfaces are down
The VMware configuration is correct : The VMXNET 3 interfaces are connected
The show interfaces terse commande reports no interface :
user@vSRX-SG-01> show interfaces terseInterface Admin Link Proto Local Remotedsc up upem0 up upem0.0 up up inet 188.8.131.52/2em1 up upem1.32768 up up inet 192.168.1.2/24em2 up downfti0 up upfxp0 up upfxp0.0 up up inet 192.168.x.x/22gre up upipip up upirb up uplo0 up uplo0.16384 up up inet 127.0.0.1 --> 0/0lo0.16385 up up inet 10.0.0.1 --> 0/010.0.0.16 --> 0/0184.108.40.206 --> 0/0220.127.116.11 --> 0/018.104.22.168 --> 0/0lo0.32768 up uplsi up upmtun up uppimd up uppime up uppp0 up upppd0 up upppe0 up upst0 up uptap up upvlan up downvtep up up
what should I do to recover my interfaces ?
Looks like PFE is in offline state. Please check:
show chassis fpc pic-status
show chassis alarm
show system core
user@vSRX-SG-01> show chassis fpc pic-statusSlot 0 Offline FPC
user@vSRX-SG-01> show chassis alarmsNo alarms currently active
user@vSRX-SG-01> show system core-dumps/var/tmp/*core*: No such file or directory/var/tmp/pics/*core*: No such file or directory/var/crash/kernel.*: No such file or directory/var/jails/rest-api/tmp/*core*: No such file or directory/tftpboot/corefiles/*core*: No such file or directory
/var/crash/corefiles:total blocks: 16total files: 0
what do you advise me to do?
fpc is offline. Please check the license "show system licenses" and ensure all the interfaces are VMXnet type only.
The licence is OK but not the interfaces ....
Shoud I open a case ?
Thanks for your help
License usage:Licenses Licenses Licenses ExpiryFeature name used installed neededlogical-system 1 3 0 permanentVirtual Appliance 1 1 0 permanentremote-access-ipsec-vpn-client 0 2 0 permanent
Licenses installed:License identifier: E420588xxxLicense version: 4Software Serial Number: 20150xxxCustomer ID: vSRX-JuniperEvalFeatures:Virtual Appliance - Virtual Appliancecount-down, Original validity: 60 days
License identifier: JUNOS384906xxxLicense version: 4Software Serial Number: 155928301xx-JWW0lCustomer ID: UNIVERSITEFeatures:Virtual Appliance - Virtual Appliancepermanent
It may need some log review etc so better to open a case if you can.
Vikas - Are you trying to spin up vSRX-L ? 9 vCPUs are needed for vSRX-L BTW.
4. I injected the configuration with an iso
Vikas - How are you injecting the config in the ISO ? Cloud-init etc . Can you try zerozing the device and check ?
I have not experience with vSRX, I only worked with SRX240H.
I used the vSRX Deployment Guide for VMware. I put 16Gb RAM according to Table 4: Specifications for vSRX on VMware
I have a french keyboard and it hard to type commands thus I mounted an iso cd to start an initial config and works with SSH commands ("Starting in Junos OS Release 15.1X49-D40 and Junos OS Release 17.3R1, you can use amounted ISO image to pass the initial startup Junos OS configuration to a vSRX VM.")
I will follow the advices :
1. I will deploy media-vsrx-vmdisk-15.1X49-D160.2.ide (I had junos-media-vsrx-x86-64-vmdisk-18.4R1.8.ide)
2. Il will check the presence of the ge-0/x interfaces
3. If OK I will inject the correct config files
I'll keep you informed
As agreed I did several tests :
1.Deploying junos-media-vsrx-x86-64-vmdisk-18.4R1.8.ide without any configuration
-> show interface terse : shows no interface ge-0/0/X
2.Deploying jmedia-vsrx-vmdisk-15.1X49-D160.2.ide without any configuration
-> show interface terse report interface ge-0/0/X : The command correctly reports the interfaces
I imported my configuration with an iso file and all is OK
The junos-media-vsrx-x86-64-vmdisk-18.4R1.8.ide firwamre is buggy, at least with my vmware environment
The 18.3 worked properly
I will wait for the 19.1 version 🙂
Looks like you are tying to install vSRX2 in 18.4R1 version. If you need 18.4R1 specifically then Can you please try vSRX3 instead which has the better RE boot time etc: junos-vsrx3-x86-64-18.4R1.8.ide.ova
All is OK with junos-vsrx3-x86-64-18.4R1.8.ide.ova with 5vCPU and 16Go.
For information, with 9vCPU no ge-0/0/x interfaces goes up
I quickly tried vSRX-3 in LAB with 9 vCPU and 16GB RAM with 3 default vNICs . It spawn up fine and has 2 ge interfaces without any issue. It may need some troubleshooting and log review in your environment , please open a case if you need vSRX Large flavor.