Welcome to world v2.0

Just to welcome my little son : Clément who was born on 15th april 2013.

I think CCIE studies will be delayed for some time, but my desire is already there… Proof : some 2611, 3550, 1841 are here : ready to study at home So I will be back to game really nearly.

Tip Mysql : Cannot delete or update a parent row: a foreign key constraint fails

For those of you who are faced to this type of error, the command « SHOW ENGINE INNODB STATUS; » is your friend.

[...]
------------------------
LATEST FOREIGN KEY ERROR
------------------------
130322 12:03:42  Cannot drop table `test`.`events`
because it is referenced by `test`.`attachments`
[...]

Here it is my 2 cents of the day

the first of my equipment rack

Here come the first equipements of my future CCIE lab rack. Two nice Cisco 2501

install IOS from tarball

How to install IOS from tarball ? No need to extract it by means of 7zip or UNIX tar command :

Router# archive tar /xtract tftp://X.X.X.X/cme-full-7.0.0.1.tar flash:

This command is your friend

Sting concert in Rouen

For the first time of  life I have seen Sting in concert and it was in rouen : my city. It was great ! It was really great ! Thank you Sting for this awful moment ! This concert will remain etched in my memory. Ok I’m a fan!

MPLS RD, RT, label : where is the truth ?!

I was reading all my RSS feeds and I am subscribed to http://mellowd.co.uk/ccie/ . I have noticed this post for you : http://mellowd.co.uk/ccie/?p=2923 It talks about RD, RT and label about MPLS. I found this post really clear about this terms and concepts.

To sum-up :

• RD = marks routes with an ‘id’. This ‘id’ is composed by two terms (IP_ASN:number)
  • IP_ASN : IP address or ASN
  • Number : which identify the VPN

I recommand to use IP in IP_ASN. I understand it is really easy to read : 3215:100 and not 81.252.160.88:100. The last one is less easy, but when you deploy a large MPLS cloud and you must supply some load-balancing or fail-over on different PE, the RR(Route Reflector) will choice the best route in the two : 3215:100:192.168.1.0 which is received). With IP1:100:192.168.1.0 and IP2:100:192.168.1.0 the two routes will be used, so you will be able to load balance trafic over two links.

• RT = has for job to tell to PE in which VPN the route belongs to.

A route in a VPN is named a VPNv4 route. This route contains :

• RD (see above)
• RT : RT is a special extended community which flag the route such as ASN:300
• Label = 2 labels (outer=per hop label ; inner label : identify the VPN)

In MPLS transit, IP packets are routed by label. No existence for P router of RD, RT. So the VPN existence is carried by inner tag. inner tag <=> 1 VPN.

A simple MPLS lab :

• MP-iBGP between R3 and R5
• OSPF Area 0 includes : R3, R4, R5
• MPLS enabled on R3, R4 and R5

I think I don’t have to give the topology for a so easy topology.

To go further, you can see the pcap trace here : http://www.cloudshark.org/captures/44b14366b515

So : you exchange vpnv4 routes by means of MP-iBGP and access to nexthop by the corresponding tag and route to mpls nexthop MPLS friend (here R4).
Also, to access 10.0.0.0/8 from 2 : R5 must push tag 20 (vpnv4 route to this subnet) and push label 16 (to 3.3.3.3 loopback of R3).

NetBSD-6.0 is on the way…

As said riz@ :

NetSBD 6.0 is currently being copied to ftp.netbsd.org.  Sometime in
the next 24h it will be made world-readable so mirrors can
begin the process of copying it.

It will be announced sometime on Wednesday.

Thanks!
+j

Ready to test it and upgrade/install servers…

21 years later : it is always true …

It is really sad, and it is not finished. I think it is only the beggining…

Linux : Remote desktop && Hamachi

For those of you which need to access by means of « Remote Desktop » you can use :

• Nomachine NX
• Teamviewer
• VNC

And you can use both LogmeIn Hamachi and VNC. Hamachi is a software which can make network betweeen devices. Against logmein product which lot of you know, here it is at ~~Level2~~ (OSI).

How you create your VPN ?

For Linux users, you must install vnc4server and hamachi (supplied by LogmeIn) package (dpkg is your friend). Then you launch your vnc server :

root@plop# vncserver 
New 'plop:1 (clucas)' desktop is plop:1

Starting applications specified in /home/clucas/.vnc/xstartup
Log file is /home/clucas/.vnc/plop:1.log

Now the VNC server is reacheable by means of 5901 (5900 + 1) port.

Then you can create your VPN network by using hamachi :

root@neptune:~# hamachi -h
LogMeIn Hamachi, a zero-config virtual private networking utility, ver 2.1.0.76

  usage: hamachi [command]

  command    specifies an action. Can be one of the following -

             #  set-nick 
                login
                logon
                logout
                logoff
             #  list
                peer 
                network 
             #  create  []
                set-pass  []
                set-access  [lock|unlock] [manual|auto]
                delete 
                evict  
             #  approve  
                reject  
             #  join  []
                do-join  []
                leave 
             #  go-online 
                go-offline 
             #  attach 
                attach-net 
                cancel
             #  gw-config 
                    [dhcp|static [net    ]
                                 [domain ]
                                 [dns  []]]
                    [del  ...]
                    [add  ...]
             #  set-ip-mode ipv4 | ipv6 | both
             #  check-update
                vpn-alias  |0
  If no command is specified, hamachi displays its status including version,
  pid, client id, online status, nickname and the LogMeIn account
root@neptune~# hamachi attach clucas@altern.org
root@neptune~# hamachi join network password
root@neptune~# hamachi go-online network

You have now access to your Linux server/desktop from anywhere by means of hamachi’s device :

For mac users (such as me : not a really experimented user), you have a built-in VNC client in MAC from 10.5 MAC OS X.

Go in your finder window > Go > Connect to server >
Now you can access to your device by means of :
vnc://x.y.z.w:5901 (where 5900 + X display : here :1)

Little challenge : MPLS and Frame-Relay

You can find a little challenge below :

The MPLS is not working… There’s no problem on the Frame-Relay cloud (it works perfectly). But you cannot ping from R5 to R4

• R4.cfg
• R5.cfg
• R6.cfg

Troubleshoot it. It is not really hard.