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:
We’re excited to take to the road for another edition of our VMware Software-Defined Data Center Seminar Series. Only this time, we’ll be joined by some great company.
VMware & Palo Alto Networks invite you along for a complementary, half-day educational event for IT professionals interested in learning about how Palo Alto Networks and VMware are transforming data center security.
Thousands of IT professionals attended our first SDDC seminar series earlier this year in more than 20 cities around the globe. Visit #VirtualizeYourNetwork.com to browse the presentations, videos, and other content we gathered.
This free seminar will highlight:
Who should attend?
People who will benefit from attending this session include:
Agenda
Cisco has announced their plans to transition the CCIE Service Provider certification blueprint from Version 3.0 to Version 4.0 starting May 22nd, 2015. The official announcement for the Written and Lab Exam Content Updates can be found here.
There are four key points to this announcement, which are:
CCIE SPv4 Lab Exam Format Changes
The Lab Exam format of SPv4 has been updated to follow the same format as the new CCIE Routing & Switching Version 5.0. This means the exam now consists of three sections: Troubleshooting, Diagnostic, and Configuration.
CCIE SPv4 Hardware & Software Version Changes
Following along with the current CCIE RSv5, CCIE SPv4 now uses all virtual hardware as well. Specifically the new hardware and software variants are as follows:
Both the IOS XR and IOS XE variants are already available as virtual machines that you can download from cisco.com Continue reading
Some fun today. Juniper recently ran a competition they called the Junos Cup 2014. It was modeled after a world cup of sorts, with each challenge involving a country in the name, four Tournament and then – because in the … Continue reading
If you liked this post, please do click through to the source at Juniper’s Day One: Junos Cup 2014 Book and give me a share/like. Thank you!
Do you really need genuine SFP and QSFP modules in your network equipment ? We talk technical with a supplier of OEM modules for your network equipment about the technology, functions and operation of non-vendor SFP optics and modules.
The post PS Show 35 – OEM SFP and QSFP Modules – Do They Work ? appeared first on Packet Pushers Podcast and was written by Greg Ferro.
