ios v junos... memory...

most cisco ios flavors use a flat memory space which means that the current processes have access to all allocated memory at any given time... this allows for a loose and fast process allocation per requesting process...

junos, conversely, uses protected memory resources which means that specific memory is reserved for use by specific processes at any given time...

the argument can be made for advantages in both models; the flat memory model is arguably faster while the protected memory model disallows process corruption vis a vis, one process cannot subsume the others memory area; it is protected...

ios is non preemptive multitasking which means that the process gives back the resources when the process decides to, with some limits...

in ios, a process can be in one of 5 self-evident states, determined by the scheduler...

New— The process has just been created and has no resources. It has never been scheduled to run.

Ready— The process is ready to run and should be scheduled on the processor the next time it is eligible.

Run— The process is currently running.

Idle— The process is waiting for some event to become ready to run.

Dead— The process is dead; it is being cleaned up.

forgot to mention...

to get multiple olives running in gns3, make a new directory, copy your olive.img into it and rename it j1.img or something... do it again and call the next one, j2.img, etc...

go back to gns3 and drag a juniper router into the environment... right click and configure... point the image directory to the directory for each olive individually... drag another out, repeat... connect up interfaces BEFORE you start them... then start them, and let the games begin...

do a little homework on navigating the cli and you will be all over it...

i needed no special command sequences, shown below...

if your juno doesn't start, you probably have path problems with qemuwrapper...  be sure to test that in the qemu general tab...

it doesn't get better than this...

junos routes ospf...

wow...

root@junosA> show ospf database
    OSPF database, Area 0.0.0.0
 Type       ID               Adv Rtr           Seq      Age  Opt  Cksum  Len
Router  *1.1.1.1          1.1.1.1          0x80000004   693  0x22 0x42e6  60
Router   2.2.2.2          2.2.2.2          0x80000006   726  0x22 0xb264  60
Router  *192.168.1.1      192.168.1.1      0x80000001   736  0x22 0xae42  36
Network  192.168.1.2      2.2.2.2          0x80000003   716  0x22 0x5b2   32
root@junosA> show ospf interface
Interface           State   Area            DR ID           BDR ID          Nbrs
em0.0               BDR     0.0.0.0         2.2.2.2         1.1.1.1            1
lo0.0               DR      0.0.0.0         1.1.1.1         0.0.0.0            0
root@junosA> show route
inet.0: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1.1.1.0/24         *[Direct/0] 00:12:32
                    > via lo0.0
1.1.1.1/32         *[Local/0] 00:12:32
                      Local via lo0.0
2.2.2.0/24         *[OSPF/10] 00:12:08, metric 1
                    > to 192.168.1.2 via em0.0
2.2.2.2/32         *[OSPF/10] 00:12:08, metric 1
                    > to 192.168.1.2 via em0.0
192.168.1.0/24     *[Direct/0] 01:06:14
                    > via em0.0
192.168.1.1/32     *[Local/0] 01:06:14
                      Local via em0.0
224.0.0.5/32       *[OSPF/10] 00:12:36, metric 1
                      MultiRecv
root@junosA> ping 2.2.2.2
PING 2.2.2.2 (2.2.2.2): 56 data bytes
64 bytes from 2.2.2.2: icmp_seq=0 ttl=64 time=1.693 ms
64 bytes from 2.2.2.2: icmp_seq=1 ttl=64 time=4.832 ms
64 bytes from 2.2.2.2: icmp_seq=2 ttl=64 time=3.762 ms
^C
--- 2.2.2.2 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 1.693/3.429/4.832/1.303 ms

root@junosA> show configuration | display set
set version 10.1R1.8
set system host-name junosA
set system root-authentication encrypted-password "$1$ALnM4HQI$/VI9YObWi1PmMT4J0uJVn1"
set system syslog user * any emergency
set system syslog file messages any notice
set system syslog file messages authorization info
set system syslog file interactive-commands interactive-commands any
set interfaces em0 unit 0 family inet address 192.168.1.1/24
set interfaces lo0 unit 0 family inet address 1.1.1.1/24
set protocols ospf area 0.0.0.0 interface em0.0
set protocols ospf area 0.0.0.0 interface lo0.0
set protocols lldp advertisement-interval 10
root@junosA>
it's like candy...

junos pings in gns3...

it actually works... this is really exciting, i mean it this time..

root@junosA> show configuration
## Last commit: 2012-08-08 22:25:11 UTC by root
version 10.1R1.8;
system {
    host-name junosA;
    root-authentication {
        encrypted-password "$1$ALnM4HQI$/VI9YObWi1PmMT4J0uJVn1"; ## SECRET-DATA
    }
    syslog {
        user * {
            any emergency;
        }
        file messages {
            any notice;
            authorization info;
        }
        file interactive-commands {
            interactive-commands any;
        }
    }
}
interfaces {
    em0 {
        unit 0 {
            family inet {
                address 192.168.1.1/24;
            }
        }
    }
}
protocols {
    lldp {
        advertisement-interval 10;
    }
}
root@junosA>

or

root@junosB> show configuration | display set
set version 10.1R1.8
set system host-name junosB
set system root-authentication encrypted-password "$1$.65Y7GJ5$IIOJYhHJYNpeN4s4G2VXa1"
set system syslog user * any emergency
set system syslog file messages any notice
set system syslog file messages authorization info
set system syslog file interactive-commands interactive-commands any
set interfaces em0 unit 0 family inet address 192.168.1.2/24
set protocols lldp advertisement-interval 10
root@junosB>

now that's some creamy goodness... still working on lldp..

junos in gns3...

 step by step...

this is based on http://www.youtube.com/watch?v=f4ZNqcu-a4o

most excellent guide for performing this tricky install...

as the video points out, you need qemu 0.11 you can get from gns3.net (windows all in one is best)
a bsd iso (4.4-mini-iso in this example)
and a juniper.bin (10.1R1.8)

my thrust in doing this is to smooth some of the rough patches and to also assemble the later unix commands as

text strings so i don't have to keep rewinding the video... if you figure out how to scrape the commands in, let

me know... you should definitely be familiar with ezzin's video which you can find here...

http://www.youtube.com/watch?v=f4ZNqcu-a4o

and don't forget to thank ezzin for this amazing effort...

sets parameters for olive image from qemu directory

qemu-img.exe create j10.img -f qcow2 6G formatting 'j10.img', fmt=qcow2 size=6442450944 encryption=off

cluster_size=0

place mini bsd into qemu folder, then bring it into qemu with:

qemu.exe -L . -m 256 -hda j10.img -boot d -localtime -cdrom 4.4-mini.iso

now it's pucker time...

at kernel config menu choose

skip kernel config and continue with install

remember ctrl-alt gets your mouse back

next screen choose express

fdisk partition part, kind of scary, you are building a 6G partition for olive only, so don't be alarmed, notice

it says 6143MB in upper right corner...

to choose A (use entire disk, meaning the 6G you are partitioning) enter A then Q... counterintuitive...

A then Q... if you just press A without Q, you'll sit there looking at it... A then Q...

choose standard mbr

create partitions for the partition, use C

1. enter 2048M, type FS, /
2. enter 1024M, type swap
3. enter 100M, type FS /config
4. give the rest as type FS to /var

good


again, counterintuitive,


press Q


next screen select 8 (user) by scrolling down and hitting the space bar to X it


next screen, no to free bsd ports

brings you back, X is still in user, scroll up to exit, enter

accept 1 cd/dvd

next screen warning... go for it, yes, because you are sure...

now be patient... it is important to let it build it's file system... later, there will be times that you will

have to wait for the prompt to come back... WAIT FOR THE PROMPT TO COME BACK... did i mention WAIT FOR THE PROMPT

TO COME BACK before inputting any keystrokes...

after building, visit the general configuration menu to set the root password YES

scroll to root password and set a root password

back to config menu
exit, exit install...

ctrl-alt-2 then at qemu prompt Q

it goes away, breathe in...

seems odd, just do it...

now you have to make a cd image of the juno.bin... like ezzin, i used 10.1R1.8

why?  BECAUSE HE MADE IT WORK WITH THAT FILE...

follow the procedure on the video for burning the image...

let me know when you're done...

time to boot the iso

PUT THE ISO IN THE DIRECTORY THAT CONTAINS QEMU

qemu -L . -m 256 -boot c -hda j10.img -cdrom j10.iso

login as root

now the fun begins...

mount /cdrom

mkdir /var/tmp/j/

cd /var/tmp/j/

tar zxvf /cdrom/jinstall-10.1R1.8-domestic-olive.tgz

now wait for the prompt... WAIT...

mkdir pkgtools

cd pkgtools

tar zxfv ../pkgtools.tgz

cd bin

cp /usr/bin/true ./checkpic

cd ..

tar zcvf ../pkgtools.tgz *

cd ..

rm -rf pkgtools

tar zcfv ../junos.tgz *

wait for the prompt

pkg_add -f /var/tmp/junos.tgz

wait for the prompt

init 6

ctrl-alt-2

Q from qemu prompt

i know, it just seems wrong but...

now for telnet...

i have windows 7 so i use putty, but prep qemu with this telnet command first

qemu -L . -m 512 -hda j10.img -serial telnet:127.0.0.1:1001,server,nowait,nodelay -localtime

then launch putty using the telnet setting, 127.0.0.1 and port 1001...

it takes a while, but it will come up... let it cook... have at it...

junos in the house...

a picture's worth a thousand qemu's...

step by step tomorow on how... if you can't wait, go here... it's how i did it...
http://www.youtube.com/watch?v=f4ZNqcu-a4o

and thank him...

not sure what this means but...

looks promising...