This document describes how to qualify Ethernet cards for use in a Cisco Agent Desktop environment.
Cisco recommends that you have knowledge of these topics:
Cisco Agent Desktop
Cisco Unified Contact Center Enterprise
Cisco Unified Contact Center Express
Sniffer Pro, or similar software
The information in this document is based on these software and hardware versions:
Cisco Agent Desktop
Cisco Unified Contact Center Enterprise version 4.6(0)
Cisco Unified Contact Center Express version 6.1(1)
Sniffer Pro, or similar software
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.
Refer to Cisco Technical Tips Conventions for more information on document conventions.
On a site where you deploy IP Telephony (or plan to deploy in the future), the Cisco CallManager and the IP phones typically use a Virtual Local Area Network (VLAN) in order to logically separate voice from data. Although both traffic types are carried on the same physical channel, they are transmitted on two different VLANs, one for voice and one for data. This configuration allows voice to be transmitted with higher priority than data.
In a contact center that uses silent monitor, you must ensure that the agent desktop system is connected to the PC port on the back of the IP phone. This enables the silent monitor subsystem to collect voice packets that reach the phone, and to forward the voice packets to the supervisor workstation. The agent desktop system uses one single physical channel to interact with two different VLANs.
The agent desktop accesses the physical channel with the help of an Ethernet Network Interface Controller (NIC). The NIC watches the channel and collects Ethernet frames addressed to the agent computer. Then it runs a pre-processing step to extract IP packets from the Ethernet frames and deliver them to the TCP/IP stack.
During extensive internal testing Cisco identified that some Ethernet NIC card drivers available are not capable of pre-processing Ethernet frames that have an IP packet encapsulated in a VLAN frame. The NIC card driver discards the Ethernet frame altogether if the IP packet is encapsulated in an 802.1Q frame. Some vendors can provide a configuration setting that allows their NIC card driver to forward VLAN traffic to the TCP/IP stack. See table 1.
If an agent desktop NIC card driver discards VLAN traffic, the silent monitor subsystem on that desktop is not able to collect and forward voice packets to the supervisor workstation and silent monitor does not function properly. Cisco has developed a procedure to determine whether a particular Ethernet NIC card driver works with CTI OS Silent Monitor. The procedure is described in the Test Procedure section.
In this test, you send sample VLAN packets to a Test Target NIC card, and ensure that the pre-processing step does not discard the packets, but passes the packets on to the TCP/IP stack on the operating system to the computer that hosts the NIC card. Figure 1 represents the setup you require for this test.Figure 1 – The Test Setup
The Test Target NIC is connected to one port of a simple Hub. The Hub is connected to the network backbone or subnet. You also need a Packet Generator Host that has the ability to generate Ethernet traffic. The Packet Generator Host is connected to another port on the Hub.
The Packet Generator Host equipment can be either a dedicated packet analyzer, or a computer with a software-based packet analyzer with capabilities to generate Ethernet traffic.
There are a good number of software packet analyzers available that can be used for this purpose. For a comprehensive list of reliable analyzers visit the Cooperative Association for Internet Data Analysis web site.
When the environment is set up, load the software tools on the Test Target and Packet Generator Host. Complete these steps:
Download WinPcap .
Run the Install program for WinPcap.
Create a directory on the Test Target computer, and name it "VLANTest".
Download WinDump.exe .
Copy the file to the directory you created in step 3.
Open a console window, go to the directory where you copied WinDump.exe.
Determine the MAC address of the Test Target NIC. To do so, execute ipconfig /all at the command prompt.
Write down the number that appears for the Physical Address, as shown in figure 2:Figure 2 – The ipconfig /all Command Output
For example, notice the Intel Pro/100 NIC card, the MAC address is 00D059d8f7d9.
Determine the device interface number of the Test Target NIC. Execute windump D.
Write down the number of the test NIC (see figure 3).Figure 3 – The Test NIC Number
Notice the interface number 1 that corresponds to the Intel Pro/100 NIC card in figure 3.
Note: If you are not sure which number to pick, repeat the test for each card until the test succeeds for one (sufficient pass) or fails for all cards.
Start WinDump to monitor the Test Target NIC for incoming VLAN packets. Execute windump i <device_number> vlan. As shown in figure 4, the device_number is 1.Figure 4 – The Device Number is 1
Complete these steps in order to prepare the packet generator host:
Obtain a packet analyzer, for example Sniffer Pro.
Load the packet analyzer software onto the Packet Generator Host. Figure 5 shows Sniffer Pro.Figure 5 – Sniffer Pro
Obtain the sample capture file VLANSamplePackets.cap, and save the file to an accessible directory.
Load the sample capture file into the packet analyzer, such as Sniffer Pro. VLANSamplePackets.cap is generated in a format that majority of the dedicated and software packet analyzers can load. Figure 6 displays the opened file in Sniffer Pro.Figure 6 – The File Opened in Sniffer Pro
In this test, you send sample VLAN packets to a Test Target NIC card, and ensure that the pre-processing step does not discard the packets, but passes the packets on to the TCP/IP stack on the computer that hosts the NIC card.
Here is the test case to determine whether or not the Test Target NIC is qualified to work with CTI OS Silent Monitor and Cisco Agent Desktop monitoring:
PA - Packet Analyzer
WD - WinDump
|SMNIC - 1 Send Sample VLAN Packets to Test Target NIC Card|
|Objective||To verify whether the Test Target NIC is able to pre-process VLAN packets and forward them to the TCP/IP stack on the Test Target host.|
|1||PA||Select one of the loaded sample VLAN packets.|
|2||PA||Select the option, "Send the Current Frame".|
|3||PA||Modify the destination MAC address to use the MAC address of the Test Target NIC (see figure 7).|
|4||PA||Send five times the new frame to the Test Target NIC.|
|5||WD||Confirm that there is activity reported on the Test Target NIC.|
|Expected Result||The Test Target computer "windump" displays five packets for VLAN ID=85 (see figure 8). If the test fails, no packets are displayed.|
Figure 8 – Five Packets Displayed for VLAN ID=85
If the outcome of this test is successful, your Test Target NIC works with CTI OS Silent Monitor and Cisco Agent Desktop monitoring. If the test is not successful, contact your NIC card provider and ask for the settings necessary to allow the NIC card driver to forward all packets including VLAN packets to the TCP/IP stack on the computer so the packet analyzer tool can capture and display them.
Apply the appropriate adjustments and re-run this test procedure.
|Manufacturer||Card||Driver Versions Tested||OS Tested||Result|
|Intel||8255x-based PCI Ethernet Adapter||5.067.0 (8/5/2000)||Windows 2000||Does not work|
|220.127.116.11(4/12/2001)||Windows 2000||Does not work|
|Intel||Intel Pro/1000||According to Intel currently no supported but on the roadmap for 2004||Does not work|
|Intel||Pro/100 VE (see below)||18.104.22.168 (3/4/2003) 22.214.171.124 (2/25/2002)||Windows 2000 and Windows XP||Works with a workaround|
While the Intel Pro/100 cards tested did not work in their default configuration, there is a configuration setting (registry key), which enables Intel Pro/100 cards to work with CTIOS Silent Monitor. For more information please visit the Intel web site.
The Cisco Support Community is a forum for you to ask and answer questions, share suggestions, and collaborate with your peers.
Refer to Cisco Technical Tips Conventions for information on conventions used in this document.