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