Let me start with couple of statements that would explain the issue in broader terms. JUNOS is system based on fairly old version of FreeBSD UNIX (I think something like version 4.X). The BSD serves as the underlying layer for services that run like daemons on top of the OS. This is great for many reasons as you can do thing like separate various functions completely in daemons. Or you can use some existing BSD packages without much work allowing for faster implementation of needed features. Also BSD in general is quite good for for the way it treats the kernel/network stack (which is different from Linux). So how does this look like? In the traditional JUNOS the logic would be something like this:
SLA probe IP-monitoring default route withdrawal
When an SRX is your wan facing router/firewall you might want to continuously test your connectivity. That is when the RPM probes do come in handy. The RPM probes are very similar to ip-sla from cisco but way more limited. On their own they just provide statistics which is nice but not very helpful. Juniper also has a feature called ip-monitoring that works in conjunction with the rpm probes and can take a result of an rpm probe and take some action on it.
ex3300 – removing virtual chassis (autobonding)
The ex3300 has a feature out of the box which is that specific ports are by default used for virtual chassis function. This might be handy in some situations but most of the time it is annoying and bit obscure. This short article will explain how to disable this feature completely and permanently.
10 years anniversary
So it is a 10 years anniversary of this blog and with it there is a new challenges ahead. Due to series of unfortunate events I have lost all the content of this blog and all its backups. Though it is quite painful to see 10 years of one’s work gone I see it also as an opportunity for a fresh start. So what going to happen here next ? Well I have couple of things I would like to write about which I haven’t so far so that will be the new content.
How to test IPv6 with iperf
Lately there has been yet again a big surge of interest in IPv6 and I did find to my surprise that even thought IPerf supports IPv6 for quite some time no-one actually has written how to actually do this rather trivial test.
First thing about IPv6 is that your interface on the end-point PCs will auto-assign a link-local address to itself. The link local address is in fe80::macaddress format (where one bit of the mac address can be changed depending on the implementation). So this looks fine – no problems. You should be able to ping between those ip addresses using ipv6 ping riight? Lets try to ping localhost’s ipv6 link-local address. In order to do this you need to specify the interface you are using as ping can’t lookup the address automatically as it can with IPv4.