Skip to main content

Posts

Showing posts from September, 2015

Juniper DHCP Server Configuration

We already configure our QEMU in GNS3 and run our vSRX Router. Now its time to configure DHCP server in our vSRX router. Lets began. Logical Diagram for this tutorial To configure DHCP server Assign Lowest and highest IP range root# set system services dhcp pool 192.168.1.0/24 address-range low 192.168.1.50 high 192.168.1.200 Assign DNS server (in my case I had used Router interface IP) root# set system services dhcp pool 192.168.1.0/24 name-server 192.168.1.1 Assign IP address of the router root# set system services dhcp pool 192.168.1.0/24 router 192.168.1.1 Assign the lease time root# set system services dhcp pool 192.168.1.0/24 default-lease-time 3600 Assign DHCP as an allowed inbound service for the interface which we are going to enable DHCP. root# set security zones security-zone untrust interfaces ge-0/0/1 host-inbound-traffic system-services dhcp Assign IP address to the client faced interface. root# set interfaces ge-0/0/1 unit 0 family inet ad

vSRX GNS3 QEMU

In this tutorial I'm going to run vSRX JunOS in QEMU and configure it as DHCP Server. Lets began with installing vSRX into QEMU. I have try vSRX to run into Vbox but never succeeded. So I better to choose QEMU otherwise waste of time. In my case I had used junos-vsrx-12.1X46-D10.2-domestic to mount into QEMU. Search for it. Now we have to convert our .vdi file into .image, for that use following command cd d:\junos\ c:\Program Files\GNS3\qemu\>qemu-img.exe convert -O qcow2 d:\junos\junos-vsrx-12.1X46-D10.2-domestic-disk1.vdi d:\junos\junos-vsrx-12.1X46-D10.2-domestic.img We just made our image ready to run into QEMU. Go the GNS3 Note: Strongly recommended to use QEMU in linux and enable KVM otherwise it eats up all your CPU and RAM. -nographic -smp 2 -enable-kvm >edit>preference>choose "QEMU VMs" Click on "New" Choose "Default " Gave Name "vSRX" (in my case). I'll use following topology

Juniper Message from syslogd

While doing some lab test, this weird syslogd message appear every seconds on the console terminal, so it was very difficult to complete the lab. This messages are due the following syslog configuration .  So for now we are going to de-activate it to generating the message #deactivate system syslog user *  #commit