Virtual 7750 SR Available in 12.0.R4

[ckdo92]

Now, this is great news!
However, how do you get the zip file?

Cheers!

[Stoffen]

OK, so now we have networking as well.

Step 1;
lab@lab:~$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.fe5400192b01 no vnet0
virbr0 8000.fe54001aee21 yes vnet1
vnet2
vnet3

To add local network to the bridge; brctl addif virbr0 eth0 (assuming you are using eth0 for networking)

In VMM, add more network cards to the VM.
Use "Specify shared device name" and enter the Bridgename "virbr0" that KVM has created for you.
Add new NICs for each port in the SR;
The first NIC belongs to CPM ETH port (A/1)
The second NIC belongs to port 1/1/1
The third NIC belongs to port 1/1/2
etc..

I'm running OSPF on double tagged frames between two VM's now, and its working just fine

[Stoffen]

Now, this is great news!
However, how do you get the zip file?

Cheers!

You will find it on Alcatel Lucent's website or perhaps via your ALU representative.

[joel]

@ Stoffen, how does one get hold of the zip file ?

[cavagnaro]

He said it already...on BPWS

[Stoffen]

OK people.

Some of you might have noticed "No license file specified" right after you could modify the BOF during boot.
As of now, I have no information regarding licensing, but I assume that its due to the lack of this license, each system reboots itself after about 1 hour of uptime.
Some systems might crash and produce trace information while rebooting, but most of the times they boot OK.
Remember to save your configuration as often as possible!

My laptop thats running the system, is not a high end box at all. It has a Sandy Bridge Intel i7 CPU, 4 cores, 8 threads with 8 gigs of ram.
Im currently running 6 VMs, all interconnected on this laptop.
Is a bit scary when all 6 nodes reboots at the same time, as memory consumption is at its highest while booting... Touched 92% used memory.. shaking

I am going to talk a bit about interconnecting the VM's.
Since I'm using CentOS, I can only describe how its done there. I'm no Linux guru, just learning by doing. So it might be the same on other distros, but it might not....
And, there might be ways to do this that is way more straight forward than my method, but it works..

OK.

Topology can be like this

SR1 <-> SR2
SR1 <-> SR3
SR2 <-> SR4
SR3 <-> SR4

Plain ring structure.

To make the VM's talk to each other, you have to create bridges.
Treat bridges as links between nodes.

I have done it as simple as this;
[root@centos]#brctl addbr brSR01-SR02
[root@centos]#brctl addbr brSR01-SR03
[root@centos]#brctl addbr brSR02-SR04
[root@centos]#brctl addbr brSR03-SR04

Then you have to make the bridges UP, and available to the system.
[root@centos]#cd /etc/sysconfig/network-scripts/

Here you have to create a file for each bridge.
Lets start with the first;
filename: ifcfg-brSR01-SR02
content:
DEVICE=brSR01-SR02
TYPE=Bridge
BOOTPROTO=static
ONBOOT=yes

Save the file, and make the necessary files, and modify them accordingly.

When this is done, you have to restart your network service;
[root@centos]# service network restart
[root@centos network-scripts]# service network restart
Shutting down interface brSR01-SR02: [ OK ]
Shutting down interface brSR01-SR03: [ OK ]
Shutting down interface brSR02-SR04: [ OK ]
Shutting down interface brSR03-SR04: [ OK ]
Shutting down interface eth0: Device state: 3 (disconnected)
[ OK ]
Shutting down interface wlan0: [ OK ]
Shutting down loopback interface: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: Active connection state: activating
Active connection path: /org/freedesktop/NetworkManager/ActiveConnection/7
state: activated
Connection activated
[ OK ]
Bringing up interface brSR01-SR02: [ OK ]
Bringing up interface brSR01-SR03: [ OK ]
Bringing up interface brSR02-SR04: [ OK ]
Bringing up interface brSR03-SR04: [ OK ]

When this is done, the new network devices are available in VMM, so when you add a new NIC, you can choose the correct bridge for the planned port as mentioned in earlier posts.
Remember to choose NIC e1000.

Good luck!

PS;
I just had to try.. Created a simple topology in GNS3, with a 7200 and a cloud.
Enabled OSPF on SR1 and SR2 on the port pointing towards my LAN, and the same on the 7200 router.

R1#sho ip ospf nei

Neighbor ID Pri State Dead Time Address Interface
1.1.1.1 1 FULL/BDR 00:00:38 192.168.100.241 GigabitEthernet1/0
2.2.2.2 1 FULL/DROTHER 00:00:38 192.168.100.242 GigabitEthernet1/0


R1#sho ip ro summary
IP routing table name is default (0x0)
IP routing table maximum-paths is 32
Route Source Networks Subnets Replicates Overhead Memory (bytes)
connected 0 3 0 180 516
static 0 0 0 0 0
ospf 1 2 14 0 1140 2816
Intra-area: 0 Inter-area: 15 External-1: 0 External-2: 1
NSSA External-1: 0 NSSA External-2: 0
internal 10 2652
Total 12 17 0 1320 5984


Tomorrow;
MPLS and BNG setup

Christoffer out

[Stoffen]

SR-OS 12.0.R5 released.
Not tried the VM yet, but will do this evening.

Additional information:
Alcatel-Lucent-7750_XRS-VM-12.0.R5

Perhaps we get XRS in the VM?

ThumbsUp

[Stoffen]

Just a small tip;
I like SSH, and I like Secure CRT.
So its silly to only console connect to the VM's.

So my workstation is a Windows PC, and I want to use that to connect to all my VM's on my laptop via SSH.
Solution; enable RIP

I have SR01 connected to my LAN via a bridge.
I enable RIPv2 and export all static, direct and OSPF / IGP routes into RIP.
Make sure to set metric if redistributing from IGP. If not it will inherit the metric of the IGP witch will be higher than 16.

Then enable RIP Listener service in Windows. I use Win8.
It also states that it only supports RIPv1 messages.
In my case, my workstation did recieve the v1 messages, but the system didnt parse it.
So I enabled v2 on the SR, and voila;

C:\WINDOWS\system32>route print -4
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.100.1 192.168.100.14 10
1.1.1.1 255.255.255.255 192.168.100.241 192.168.100.14 12
2.2.2.2 255.255.255.255 192.168.100.241 192.168.100.14 13
3.3.3.3 255.255.255.255 192.168.100.241 192.168.100.14 13
5.5.5.5 255.255.255.255 192.168.100.241 192.168.100.14 13
6.6.6.6 255.255.255.255 192.168.100.241 192.168.100.14 13
10.0.0.0 255.0.0.0 192.168.100.241 192.168.100.14 11
10.1.2.0 255.255.255.252 192.168.100.241 192.168.100.14 12
10.1.3.0 255.255.255.252 192.168.100.241 192.168.100.14 12
10.1.5.0 255.255.255.252 192.168.100.241 192.168.100.14 12
10.2.4.0 255.255.255.252 192.168.100.241 192.168.100.14 13
10.2.6.0 255.255.255.252 192.168.100.241 192.168.100.14 13
10.5.6.0 255.255.255.252 192.168.100.241 192.168.100.14 13

Now I can SSH to all my system adresses as long as the routing is intact.

[nerdydad]

Stoffen,

If you happen to be at SReXperts in Orlando next month, I owe you a beer.

Thanks for sharing all of this, saved me a lot of time trying to get things working in VMware.

Kevin

[marek]

Eugh I'm not having a good time with this. Keeps suffering from a system crash before it gets to CLI prompt, just before when it references IPv4 DNS etc.

Interestingly my VMM doesn't allow me change raw to qcow2 in the GUI, I have to do it on linux CLI:

virsh -c qemu:///session dumpxml $your_vm_name$ > $your_vm_name$.xml
vi $your_vm_name$.xml
#edit the line that says
<driver name='qemu' type='raw' cache='none'/>
#and change it to
<driver name='qemu' type='qcow2' cache='none'/>
#If youre not a vi person use x to delete raw then press i to insert and type qcow2 then press esc followed by :wq and return (:q to leave without making changes)
#then do
virsh -c qemu:///session define $your_vm_name$.xml
#once done you can
virsh console $your_vm_name$

try assigning more RAM to your VM. I had similar issue when using 600-700mb of RAM. When i raised it to 1,5G then it booted to CLI.