Search

In this post I’ll focus on a topic that’s mentioned in the Cisco FIREWALL training class but isn’t emphasized there or in the online Cisco ASA documentation. When configuring failover on a pair of ASA security appliances, a situation can arise in which network disruption occurs due to the secondary ASA in a failover pair becoming active first and then the primary comes online second. Both the documentation and the courseware point out that this causes the secondary (and active ASA) to swap its interface MAC addresses with those of the primary. Being naturally skeptical about this behavior, I decided to investigate. The rest of this post illustrates my confirmation of this phenomenon.

Learn how to get your best practices in order with ITSM in our webinar.

If you're losing top talent and having trouble attracting quality candidates, the no. 1 reason is that they don't see a future with you. If you're not leveraging professional development, here are a couple tips to start.

Cloud adoption continues to soar. In fact, worldwide Infrastructure-as-a-Service (IaaS) public cloud services grew by 29.5 percent in 2017, according to Gartner. If it’s not in a company’s current plans to utilize cloud technology, it most certainly will be (or should be) in the next couple of years.

In light of the recent tragic events in Haiti, it might be a good time to review some of the requirements for a well designed Uninterruptible Power Source (UPS) to be included in all of our critical network installations. As a CCNA, we are called upon to help maintai...

AMC’s television series “Halt and Catch Fire” shows North Texas’ rise as the “Silicon Prairie.” In the 1980s and early 1990s, it’s where IBM PC cloning was explored and where first-person shooter games were created. It’s also the site of the first “logic bomb”—the source of my horror story.

Recently, I was asked the following question: “We plan to implement Windows 7 in our network very soon. We want to use Windows 2003 Domain Controllers for the next couple of years. Can we make the hundreds of new Group Policy setting available to Windows 7 Windows Server 2003 DCs?” This is not an unusual situation. Some organizations find they need to replace their desktop computers immediately because of age or obsolescence and others wish to upgrade to Windows 7 because of its superior security and performance. But there may be no budget or desire to upgrade to Windows 2008 or 2008 R2. Luckily, it is not difficult to adapt Server 2003 to work with Windows 7.

Learn OpenStack from the Experts at Red Hat in our webinar.