TDR Cable Test on EX switches – CLI procedure…

I recently wrote up my experience with a cable-test wizard in the JWeb interface, and was prompted to give it a go at the CLI. Turns out you can do that too of course…

Juniper’s ‘Translator in the Cloud’

Interesting and simple description of how Juniper implement a translator to enable their website for IPv6 users. What’s also interesting is that they don’t make mention of what the ‘translator’ actually is… If it were a Junos device, I’m sure they’d have made a meal of it, but I am assuming it is an F5 or an A10 box.

Juniper SRX 11.1 – SSL VPN termination

Just seen in the release notes for Junos 11.1 for branch SRX that it will terminate SSL VPNs from Pulse clients.  Now that’s a nice thing – but calls into question why I bought my Juniper SA.  I think the SA will do some degree of network access control (NAC) for me on the corporate wired LAN as well, but perhaps I can make do with the SRX for remote access.

The thing to watch out for is that you need to have a licence for remote access on the SRX to terminate Pulse clients there. It is billed as ‘dynamic VPN’ licences, but will apparently work for Pulse clients too.  If you’ve bought licences for SSL VPNs on your SA, you won’t be able to terminate these on your SRX unless you get different licences.

I need to try this out a bit further (when time allows) and report back, I think…

More new Juniper stuff. Big stuff.

Bloody hell – Juniper are on fire at the moment.  First we get the new QFX switches supporting more 10G and FCoE in a single rack U than you can shake a stick at, and now we get the ‘converged supercore’, in the form of the PTX5000 and PTX9000.

Jesus, these things are big…

Lost disk from Junos boot order

I keep forgetting how to do this, hence a note to self…

Every so often Junos routers (in the latest case) an MX seem to lose their hard disk. This can go unnoticed and when you come to do something like upgrade the software, you run into disk space issues since one is much smaller than the other.

Junos logical systems, and logical system users

Logical systems on Junos are quite easy to configure. Their purpose is to partition the system up into completely separate routers, each running its own routing daemon (rpd). The systems don’t talk to each other at all – you connect them together using physical or vlan-tagged virtual interfaces if they need to communicate.

Unless I’m mistaken, the ability to create a user with control over a single logical system is not covered by the manual. I thought I’d write it up here, just in case it is of any use to anyone.