This is Part 1 of a 2 part blog series on the topic of Network Assessments delivery unification. Over the last 19 years of my systems / networking career I have successfully
Often times during an infrastructure project you need to create a quick mirror network environment to stage equipment or systems that will later be moved into production networks. But having to go sit in the lab plugged into the lab isn’t always an option for efficient work-flows!
1: Write code
2: Use a Mac
3: Use git for version control
…then you likely will contaminate one of your repos with a slew of files named “Iconr” and .DS_Store at some point in your development cycle. Often it takes people a while to realize that the Icon files aren’t actually named Iconr, but are named Icon with special carriage return characters appended to the end of them. You’ll see them represented in a shell as
Icon\r\r depending on what tool you’re using.
Here is the cleanest way to prevent you from dealing with this issue across your projects.
The Cisco® UCS Fabric Interconnect family does not support generic 3rd party transceivers since they do not offer CLI access. This has left Cisco® UCS customers the one option of purchasing overly expensive Cisco® OEM branded optical transceivers.
IVI Optics solves this problem and brings economical transceiver options to Cisco® UCS customers.
The Arista 7050QX-32S is a fantastic 1RU switch that provides a whopping thirty-two (32) ports of 40gbps (QSFP+) plus four (4) additional SFP+ ports. Under the hood the 7050QX-32S switch is built using the Broadcom Trident II chipset which provides wire-speed forwarding with buffering Latency from 550ns. (Note: Arista also makes the 7050QX-32 which is 32-40gbps ports only without the SFP+ ports). This powerful switch also has a very low energy footprint with 460w 1+1 redundant power supplies AC (DC power also an option) and four (4) N+1 redundant fans.
The 7050QX-32S is a very good fit in your Leaf blocks, small spines, DCI block, and/or service leaf block. Importantly the “S” on end of the Arista “7050QX-32S” means that this switch comes with four (4) SFP+ ports in addition to the 32-40gbps .. (which is the main reason for this article)
I have noticed that some software seems to fall into one of two categories from past experience:
1. Fantastic UI design, with less than optimal functionality.
2. Fantastic functionality, with less than optimal UI design.
The obvious desired outcome for most developers would be to have an equal combination of both; good clean UI with efficient functionality. With just a little attention to detail, your UI can become much more consistent, and provide a much better user-experience.
Some developers put a massive amount of time and effort into the actual coding of their software, and then in an attempt to get it out to the public as quickly as possible, spend only a minimal amount of time on the UI, almost as if it’s some kind of afterthought.
Intelligent Visibility, Inc. has submitted the Arista Navigator to the Apple Mac App Store for approval to sell and distribute world wide. The Arista® Navigator is a beautiful, yet powerful software tool designed for supporting Arista® network infrastructures; and offers many advantageous features such as:
The advent of server virtualization over the last 10 or so years has sparked data center / server teams to drive requirements for layer 2 adjacency while network infrastructure teams have been going the opposite direction by reducing layer 2 adjacent spanning-tree domains. Over the last same time span we had certain suboptimal technologies available to try and deliver this requirement.
Customers with multiple data centers across a routed MPLS WAN I am sure had either tried or mulled over layer-2 over layer-3 encapsulation features such as L2TPv3 / GRE or Cisco OTV. In addition many customers that have the good fortunate of owning or leasing dark fiber had resorted to just allowing specific data center VLANs across these fiber links configured as 802.1q trunks. In my opinion customers in both above mentioned examples have suffered from many technology related layer 2 issue or technology limiting situations. Thankfully, today we have VXLAN (RFC 7348) to solve this requirement confidently and effectively.
VXLAN is the product of networking industry’s top talent including Arista’s CTO Ken Duda that created a standard for layer 2 encapsulation over layer 3 (UDP transport). A specification if only specification until a company implements it in a clean code manor in my opinion. This blog will focus on Arista’s implementation of VXLAN since from my experience I believe is a superb implementation of VXLAN.
I released the “Dropbox API SDK for Xojo” as an open source project hosted on our Github page. If you are a Xojo or C# developer this blog entry will be of interest to you. My intent is to cover the whole process of creating your Dropbox App all the way through using my Dropbox API SDK to make Dropbox Core API calls.
I personally have a passion for effective network management and deterministic network behavior. I championed many network management systems (NMS), NetFlow, and sFlow solutions in a vast array of networks over the last 19 years. One of my biggest network management accomplishments was creating a successfully global managed services program that featured a cloud based network management software-as-a-service that we served. This entire program was built around a strong open-source multi-tenant NMS with our thousands of hours of custom mined SNMP OID objects that provides a myriad of information.
When I first heard our Arista SE, Eric Schuller, say “you can configure your Arista switches to email you when interfaces go down or on boot” I thought to myself “WHAAAAT…. Are you saying man!”. Since then I have been working on EOS email-feature scenarios putting those statements into the lab. Once my lab work realized that the EOS email feature worked in conjunction with EOS event-handler then it became a “real management” possibility. In my opinion this is an example of yet another innovative way Arista’s software development teams are able to give us completely new and useful management features.
In this blog I will show you how to setup your Arista EOS to enable the “mail” feature in which we will perform some manual email tasks from using the CLI. Secondly I will show you how to automate the Arista switches ability to email you when interface issues occur. Once again these examples are all lab based and please create a management strategy for your organization that may utilize these features effectively.