20 Results Found
The Red Hat® Learning Subscription delivers 12-months of unlimited access to all Red Hat Online Training courses. The Standard RHLS subscription is a higher tier with access to 5 certification exams and up to 2 retakes.
This guide will help you identify the necessary steps for adding a new line of business to your existing Avaya Aura Contact Center.
Learn how Cisco FabricPath combines the benefits of Layer 2 Switching and Layer 3 Routing, allowing for the scalability and flexibility of Layer 2 while supporting traditional Layer 3 components such as optimal paths, equal cost multipath routing and a Time to Live (TTL) field.
Red Hat Taste of Training - JB248
Red Hat Taste of Training - JB348
Avaya introduced IP Office Manager Release 9.1 on December 22, 2014. As we all know from working with IP Office Manager, every new release brings changes to its GUI. Use this white paper to help you prepare to install and administer IP Office Manager 9.1.
Standard Local Survivability (SLS) is a cost-effective alternative well suited to a branch location that does not have sophisticated telephony needs. In contrast to the server-based survivability features, SLS operates entirely from the H.248 Branch Gateway and requires a data set comprised of CM translations (survivable ARS analysis and configuration data). When you log into a H.248 Media Gateway via CLI you have likely noticed the screen message “Survivable-call-engine is disabled.” Let’s take a look at what this means.
This paper explains uplink strategies for traffic coming in and out of a Cisco Unified Computing Solution (UCS) chassis. An uplink can be Ethernet, Fibre Channel, or FCoE and is a physical connection on the FI that leaves the UCS domain directed away from the B Chassis.
Cisco Unified Computing Solution (UCS) is a very popular and powerful solution. Cisco continues to provide updated UCS management options for the full range of data center installations.
While there are differences between the IP Multicast configuration in the IOS and the Nexus OS, the Protocol Independent Multicast (PIM) protocol remains fundamentally the same. If you feel comfortable configuring Multicast in the IOS, you should be able to acclimate fairly easily to the changes in the Nexus OS.