Search

Train your workforce easily and effectively with Cisco On-Demand Learning from Global Knowledge.

Find out which training path is best to earn your Cisco Certified Network Associate (CCNA) Routing and Switching certification with some self-assessments, information about exam requirements and recommendations for test preparation.

Understand Cisco FabricPath find out why routing at Layer 2 can be an acceptable description of Cisco FabricPath.

Learn about the uplink strategies for traffic coming in and out of a Cisco Unified Computing Solution (UCS) chassis.

This white paper compares the implementation of IP Multicast in the Cisco IOS and in the Nexus OS and provides some background on the evolution and challenges of implementing multicast in the IOS is appropriate.

Where should you apply the CSS, and why are there two places to apply it? One approach is to pick one of the parameters and apply the permissions there. Quite often, an administrator will pick the phone-level CSS and configure it there so that it applies to all calls made from all lines. The goal is to specify what partitions are allowed to be called.

In a properly designed IP network, a VLAN should map to a single broadcast domain, which should map to a unique IP network. For ease of troubleshooting, traffic from one VLAN should not reach another VLAN without an OSI Layer 3 device, such as a router.

RTMT provides a set of canned views of both system resources and application counters that provide you with a snapshot of your environment right out of the box. Read on to learn how you can make RTMT even more helpful by customizing it to show you different views of your resources and CUCM environment.

Spanning Tree Protocol (STP) is dead, or at least it should be. It’s too slow to converge when there’s a change, and it causes issues with performance because there is only one forwarding path. It was developed in 1985 by Radia Perlman at Digital Equipment Corporation to allow for redundant paths within a Layer 2 topology, which was great in 1985. In fact, it was huge! So much so, that it was later standardized by the IEEE as 802.1D, and we’ve been living with it ever since.

One size does not always fit all. At times there’s a need to run more than one routing protocol and have more than one routing domain: multivendor shops, migration from one protocol to another, scalability issues of a single protocol, political or personal preference, production versus test networks, mergers, and acquisitions.