The most recent content from our members.
Four predominant IT use cases any network device configuration management tool must address are: * Configuration change management: scheduling device configuration backups, requiring change approval for configuration changes, scheduling execution of approved changed. * Compliance reporting: defining and enforcing…
Last week I was in San Francisco speaking at Cisco Live! (used to be called Cisco Networkers) and it an awesome event. First off, it was only about 70 degrees there which was 35-40 degrees cooler than here in Austin and that in of itself was worth the trip. Cisco also got smart and changed the hours so that the we could…
As a network administrator, it’s not uncommon to hear the phrase, “The network is down!” User complaints begin to pour in such as the website being down, loss of Internet connectivity, data inaccessibility, emails down, application performance issues, data loss, etc. As a result, the IT department becomes bombarded with…
At some point, all networks deploy devices on a small or large scale. This could be a result of network expansions, device replacements due to end-of-life, vendor changes, hardware upgrades, and even cases of replacing faulty or failed devices. Below are a few tips that can help you simplify the process of configuring…
Every organization, every network and IT administration team is looking for a network configuration management solution. “Why?” you ask. An enterprise network is a composite of uncertainties that can impact network performance and availability at any time. Even a minor change in network device setting can upset your…
As networks grow, manual network configuration and change management (NCCM) becomes extremely cumbersome and can cause costly network downtime. Network administrators using manual processes can experience: * Increased time and effort to manage the growing number of devices * Human errors causing network outage and loss of…
Lack of proper configuration management capabilities lead to many problems that result in serious network downtime and costs to your business. Some commonly faced problems: #1 What happens if a configuration change results in downtime and the network engineer who made the configuration change is not around. For example,…
Network administrators find tracking and maintaining device End-of-Life (EoL) and End-of-Sale (EoS) data difficult because ….. * Hard to collect, verify and manage various multi-vendor device information * Big effort to regularly track and keep a watch on Vendor announcements * Unpractical to check on a daily/regular basis…
DOWNTIME IS NOT GOOD – not good for business, not good for IT and not good for employees. Every network administrator knows that much. Regardless of the size of the network and the type of business, downtime impacts productivity, disrupts business services, causes financial losses and certainly creates headaches for IT.…
I recently saw the results of a survey published by Athena Security entitled “The Corporate Firewall-Playing With Fire” that stated that up to 95% of corporate firewalls may be vulnerable due to the difficulty of auditing them manually. It goes on to state that firewall audits require a review of the configuration rules…
It looks like you're new here. Sign in or register to get started.