A lot can change in six months — including comfort of a $40 million funding cushion, apparently. Docker Inc. raised that much with a C round in September. But the startup needs even more, so today, it’s announcing a $95 million Series D round. Yes, already. Interest in open source Linux containers is still exploding, with Docker Read more >
You may have noticed that last week, Plexxi, in partnership with PSSC Labs, announced a new solution that will change how companies install and operate new big data infrastructure. This partnership combines Plexxi’s SDN switching and control with PSSC’s high-performance servers and Cloudera Enterprise big data platform.
The Scale-out Network Comes to Big Data
We already know that the way Enterprise applications are built is changing rapidly. New applications are being written to be far more distributed and designed to scale horizontally across the infrastructure. This allows companies to easily scale performance, storage, and networking power as the application needs grow. Scale-out applications like Cloudera Enterprise’s CDH (Cloudera’s Adache Hadoop distribution) are already built to easily scale across compute and storage – meaning administrators can incrementally add new servers that add more processing power and data storage capabilities to the application. Yet the “state of the art” way to build the network is to pre-determine the total number of servers needed and to build a scale-up (2-tier) leaf/spine network. Plexxi’s network is a true scale-out network – no hierarchies, no pre-determined ceilings for number of server ports, and just a single cable to add a new switch to the Continue reading
A 'single source of truth' for IT.
Finally, it’s the blog you’ve all been waiting for! Yes, that’s right folks; the time has come to discuss the benefits of Real-Time Monitoring Tool (RTMT) in CUCM and CUC. All right, I know it’s not the most exciting subject to discuss all the topics on the CCIE Collaboration lab blueprint, but it can help you perform troubleshooting tasks in a very efficient manner. The goal for this blog is to point out a couple useful features of RTMT to give you a nice boost when tackling different lab topics.
For those that are not familiar with RTMT, it can be used to pull traces (log files) for troubleshooting in all Cisco UC servers, monitor real-time platform statistics, check syslog messages, and display a host of “Performance” parameters that can assist the engineer in gathering system information. While those are all great features worthy of our attention, I’d like to focus specifically on a new RTMT feature available in CUCM 9.x called “Session Trace Log View.” This feature is an excellent troubleshooting tool, especially when used with SIP. Essentially what this does for us is organize the traces in such a way as to provide a cohesive view Continue reading
A massive round for the security startup.
The video of my Troopers 15 IPv6 Microsegmentation presentation has been published on YouTube. As with the Automating Network Security video, it’s hard to read the slides; you might want to look at the slide deck on my public content web site.
You’ll find more about this topic, including tested Cisco IOS configurations, in IPv6 Microsegmentation webinar.
In our last post about SaltStack, we introduced the concept of grains. Grains are bits of information that the Salt minion can pull off the system it’s running on. SaltStack also has the concept of pillars. Pillars are sets of data that we can push to the minions and then consume in state or managed files. When you couple this with the ability to template with Jinja, it becomes VERY powerful. Let’s take a quick look at how we can start using pillars and templates.
Prep the Salt Master
The first thing we need to do is to tell Salt that we want to use Pillars. To do this, we just tell the Salt master where the pillar state files are. Let’s edit the salt master config file…
vi /etc/salt/master
Now find the ‘Pillar Settings’ section and uncomment the line I have highlighted in red below…
Then restart the salt-master service…
systemctl restart salt-master
So we just told Salt that it should use the ‘/srv/pillar/’ directory for pillar info so we need to now go and create it…
mkdir /srv/pillar/
Now we’re all set. Pillar information is exported to the Continue reading