A quick post today. As you may recall, I run two Ruckus Wireless APs at home – a Zoneflex 7982 AP and a Zoneflex 7363 AP managed by a Zone Director 1106. The ZF7982 and ZD1106 were provided courtesy of Ruckus … Continue reading
If you liked this post, please do click through to the source at Ruckus Wireless User? Here’s your OS X Yosemite Warning. and give me a share/like. Thank you!
Recently, I spoke at the dotGo 2014 conference in Paris and my colleague (and creator of OpenResty) Yichun Zhang spoke at the first NGINX conference in San Francisco.
If you need to take a break, go grab a drink and enjoy one of these two talks.
Tired of writing NGINX C-modules or setting-up back-end application servers? The ngx_lua module was created to save time and pain, while opening up new possibilities in the world of NGINX. The ngx_lua module embeds the Lua dynamic language into the NGINX core, turning NGINX into a highly scriptable proxy server. Many use it as a non-blocking full-stack web application server as well--also known as OpenResty.
Led by ngx_lua co-creator and sole-maintainer, CloudFlare’s Yichun Zhang, this presentation will introduce all the latest features implemented in the ngx_lua module as well as other new tools. Yichun will focus on features including: light threads, websockets, timers, NGINX worker initialization hooks, SSL/TLS coroutine-based sockets (or “cosockets”), full-duplex cosockets and more.
. .
The session wraps-up covering new advanced tools to troubleshoot and profile ngx_lua-based systems including dynamic tracing utilities based on Systemtap and GDB extension commands.
I am sure our work environment is not all that different from many others. There are large whiteboards everywhere and you cannot find a meeting room that does not have circles, lines and squares drawn on them. Some of our favorite bloggers have written blogs about network drawing tools and aids. Probably not restricted to just networking folks, but we certainly love to visualize the things we do. Out of all the customers I have visited, the amount of them where one of us did not end up on a whiteboard can probably be counted on one hand.
It is not surprising that we are drawn to diagrams of the networks we have created. We build our network one device at a time, then use network links to connect the next and on we go until our network is complete. Which of course it never is. To track how we have connected all our devices we need diagrams. They tell us what devices we have, how they are attached to each other, how they are addressed and what protocols we have used to govern their connectivity. They are multi layered and the layers are semi independent.
I have previously said Continue reading
If you listen to the marketing departments of overlay virtual networking vendors, it looks like the world is a simple place: you deploy their solution on top of any IP fabric, and it all works.
You’ll hear a totally different story from the physical hardware vendors: they’ll happily serve you a healthy portion of FUD, hoping you swallow it whole, and describe in gory details all the mishaps you might encounter on your virtualization quest.
The funny thing is they’re all right (not to mention the really fun part when FUDders change sides ;).
Read more ...
We've just completed another new Ansible case study; Tradesy. Tradesy is an online consignment store where people can offer their fashion and accessories for resale.
Tradesy had been doing everything by hand until making a move to use Ansible Tower in an effort to automate as many things as they could.
Continue reading
I’ve always thought Junosphere was great, and it certainly makes setting up test scenarios really really easy. However there are a few things that really niggle when using it. They don’t seem to be getting much better, which makes me wonder if there’s much development work going on with the platform. Messages to the “junosphere-contactme” email address given get no reply.
Anyway, here’s the list of niggles:
1. Sometimes MXes start up with their management IP address in the wrong place – see this post.
2. If you have a saved set of configs for Junosphere which you import from your hard disk, it doesn’t create a network diagram.
3. Topmost annoyance: every time you start up your topology the routers get different IP addresses. Argh.
4. To edit a predefined config for a device, you have to stop the whole topology. This makes setting up topologies for training courses quite a laborious process because the routers take such a long time to start up and shut down while you try to get the base config right.
5. It would be really nice to have the IP addresses and console addresses as hyperlinks you could Continue reading
MXes in Junosphere are unsupported, but I tend to use them because I want something a bit closer to the real thing somehow. The VJX is ok, but I like the way the MX doesn’t come with any security-related stuff, and the interfaces start at ge-0/0/0 rather than ge-0/0/1!
The only downside with the virtual MX is that it is a non-supported image, unlike the VJX.
Sometimes when usign an VMX, you find that the topology starts up but you can’t SSH to one or two of the nodes. So you console onto it and discover that (for some reason) the management IP address has been put onto em0 rather than being where it should be in the member0 group applied to fxp0:
root@S1> show configuration groups member0
system {
host-name S1;
backup-router 10.233.255.254;
}
interfaces {
fxp0 {
unit 0 {
family inet; <=== IP address missing!
}
}
}
root@S1> show configuration interfaces em0
unit 0 {
family inet {
address 10.233.248.46/20; <== Here it is.
}
}
The solution to this is to console onto the device and move Continue reading
Not content with digging into the A10 health monitors recently, I thought I should do the same for f5 LTM which has some slightly different setting and, it turns out, works really quite differently. I hate to say it again, … Continue reading
If you liked this post, please do click through to the source at f5 Health Monitors – More Surprises and give me a share/like. Thank you!
I’m doing some studying using Junosphere at the moment, but unfortunately Junosphere can’t emulate a LAN at the moment. Basically the same problem that GNS3 has and (as far as I know) Cisco’s VIRL/CML has as well. So you’ve got to bodge it with Integrated Routing and Bridging (IRB). What I needed topology-wise was this:
LAN segment between S1, R1 and R2
I find Junos a bit counter-intuitive when creating bridge domains. Here I need something quite simple – two ports in a bridge group (no VLANs or anything), but I need to give a VLAN tag value to identify the bridge domain.
Anyway, the process for doing this is as follows:
1. Give the physical interfaces the right encapsulation type – ethernet-bridge
2. Create a bridge domain which has a VLAN-ID and references these two interfaces
3. Create an IRB interface (irb.10) with family inet and an IP address on it
4. In the bridge domain, use “routing-interface irb.10″ to tie the bridge domain and the IP interfaces together.
The result is this:
IRB solution for LAN
The configuration I used was this:
root@S1# show interfaces
ge-0/0/0 {
description "to R1 0/0/1";
Continue reading
LEDE: One of the hardest parts of DevOps movement is explaining the unique value to IT Leadership in conventional organisations that rely on ITIL principles. I'm having success by framing the debate in terms of over-capitalised on assets and under-invested in human infrastructure.
The post Blessay: Over-Capitalized and Under-Invested in Human Infrastructure appeared first on EtherealMind.
This post SHOULD have been published on April 1st, but I need to define the terminology for another upcoming post, so here it is ;)
RFC 2119 defines polite words to use when something really shouldn’t be done. Some network designs I see deserve more colorful terminology.
2014-11-02: Updated with reference to RFC 6919 (/HT to @LapTop006)
Read more ...
Boom – you’ve got to love Junosphere. I just created the Proteus JNCIE study lab in 35 minutes flat. I made the topology of 13 routers, gave everything a hostname, loopback and interface descriptions and then just fired it up. When I did my CCIE I was there for >weeks< trying to get the right kit plugged together!
Have a look below:
