



|
|
OmniPeek Remote AdaptersClick a link below to learn more about the remote adapters available with OmniPeek. Aruba Remote AdapterContents
IntroductionThe Aruba Remote Adapter allows existing Aruba managed APs to be temporarily converted to packet capture devices, forwarding all of their packets back to OmniPeek via TCP/IP over the wired network. Rapid access to packets anywhere in the wireless network is just a few clicks away since OmniPeek can started directly from the Aruba software management system. The Aruba Remote Adapter with OmniPeek allows for packet streams from multiple Aruba APs to be aggregated within a single OmniPeek capture, simplifying data collection and analysis, allowing you to view all wireless data including channels 1, 6 and 11 simultaneously, or allowing you to monitor the roaming of wireless clients from one AP to the next. OmniPeek ConfigurationBefore you can begin capturing packets using the Aruba Remote Adapter (from an Aruba access point), make sure the Aruba Remote Adapter is enabled in OmniPeek (enabled by default). To enable the Aruba Remote Adapter in OmniPeek:
Important: On the OmniPeek computer, use the ipconfig command to obtain the computer’s IP address and Gateway IP. You will need this information when configuring the Aruba access point to send packets, as explained below. Capturing Packets from Aruba Access PointsCapturing packets from Aruba access points begins like you begin a capture from any other adapter in OmniPeek; however, packets will not populate the capture window until the Aruba access point begins sending packets to the OmniPeek computer as noted below. To capture packets from Aruba access points:
Important: When you want to stop sending packets, you must configure the Aruba controller to stop sending packets; otherwise, the OmniPeek computer will send an ICMP Destination Port Unreachable for every incoming packet received. This will impact the performance of the OmniPeek computer and possibly your network. See Configuring the Aruba Access Point to Send Packets below. Configuring the Aruba Access Point to Send PacketsIn an Aruba wireless deployment, Aruba access points can be configured to provide either Access Point (AP) or Air Monitor (AM) functionality. An Aruba access point operating as an Air Monitor will allow you to send packets from the access point to the OmniPeek computer. This section describes how to enable Air Monitor functionality on an Aruba access point, and then how to begin sending packets. To send packets from an Aruba access point to the OmniPeek computer: Note: Depending on your Aruba controller, the following instructions may differ slightly.
Important: When you want to stop sending packets, you must configure the Aruba access point to stop sending packets; otherwise, the OmniPeek computer will send an ICMP Destination Port Unreachable for every incoming packet received. This will impact the performance of the OmniPeek computer and possibly your network. To stop sending packets from an Aruba access point to the OmniPeek computer:
Known Issues
Cisco Remote AdapterContents
IntroductionThe Cisco Remote Adapter allows existing Cisco managed APs to be temporarily converted to packet capture devices, forwarding all of their packets back to OmniPeek via TCP/IP over the wired network. Rapid access to packets anywhere in the wireless network is just a few clicks away. The Cisco Remote Adapter with OmniPeek allows for packet streams from multiple Cisco APs to be aggregated within a single OmniPeek capture, simplifying data collection and analysis, allowing you to view all wireless data including channels 1, 6 and 11 simultaneously, or allowing you to monitor the roaming of wireless clients from one AP to the next. OmniPeek ConfigurationBefore you can begin capturing packets using the Cisco Remote Adapter (from a Cisco access point), make sure the Cisco Remote Adapter is enabled in OmniPeek (enabled by default). To enable the Cisco Remote Adapter in OmniPeek:
Important: On the OmniPeek computer, use the ipconfig command to obtain the computer’s IP address. You will need this information when configuring the Cisco access point to send packets, as explained below. Capturing Packets from a Cisco Access PointCapturing packets from Cisco access points begins like you begin a capture from any other adapter in OmniPeek; however, packets will not populate the capture window until the Cisco access point begins sending packets to the OmniPeek computer as noted below. To capture packets from Cisco access points:
Important: When you want to stop sending packets, you must configure the Cisco controller to stop sending packets; otherwise, the OmniPeek computer will send an ICMP Destination Port Unreachable for every incoming packet received. This will impact the performance of the OmniPeek computer and possibly your network. See Configuring the Cisco Access Point to Send Packets below Configuring the Cisco Access Point to Send PacketsIn a Cisco wireless deployment, Cisco access points can be configured to provide either Access Point (AP) or Sniff mode functionality. A Cisco access point operating in Sniff mode will allow you to send packets from the access point to the OmniPeek computer. This section describes how to enable Sniff mode functionality on a Cisco access point, and then how to begin sending packets. To send packets from a Cisco access point to the OmniPeek computer: Note: Depending on your Cisco controller, the following instructions may differ slightly.
Important: When you want to stop sending packets, you must configure the Cisco access point to stop sending packets; otherwise, the OmniPeek computer will send an ICMP Destination Port Unreachable for every incoming packet received. This will impact the performance of the OmniPeek computer and possibly your network. To stop sending packets from a Cisco access point to the OmniPeek computer:
Known Issues
AirTight Remote AdapterContentsIntroductionThe AirTight Remote Adapter extends the capability of the AirTight Wireless Intrusion Detection and Prevention System (IDS/IPS) by integrating with WildPackets OmniPeek for detailed network analysis and troubleshooting. Any AirTight sensor can be placed into packet capture mode, forwarding all of their packets back to OmniPeek via TCP/IP over the wired network. Rapid access to packets anywhere in the wireless network is just a few clicks away since OmniPeek can be started directly from the AirTight software management system. OmniPeek ConfigurationBefore you can begin capturing packets using the AirTight Remote Adapter (from an AirTight sensor), make sure the AirTight Remote Adapter is enabled in OmniPeek (disabled by default). To enable the AirTight Remote Adapter in OmniPeek:
Capturing Packets from an AirTight SensorIn an AirTight wireless deployment, an AirTight sensor must operate in troubleshooting mode in order to send packets that can be captured from the OmniPeek computer. This section describes how to enable the troubleshooting mode using the "Auto" or "Other" on an AirTight sensor, and then how to begin capturing packets. To capture packets from an AirTight sensor using the "Auto" feature:
To capture packets from an AirTight sensor using the "Other" feature:
Known Issues
SNMP Trap Adapter
Contents
IntroductionThe SNMP Trap Adapter allows OmniPeek to correlate network events from other devices with network events generated by OmniPeek. The remote adapter extends the reach of OmniPeek by allowing it to receive real-time information from third-party applications or devices. The SNMP Trap Adapter is available for download and installation from MyPeek. OmniPeek ConfigurationBefore you can begin capturing SNMP traps from a third-party application or device, make sure the SNMP Trap Adapter is installed and enabled in OmniPeek. To enable the SNMP Trap Adapter in OmniPeek:
Note: Additional configuration may be required by the third-party application or device. Important: On the OmniPeek computer, use the ipconfig command to obtain the computer’s IP address. You will likely need this information when configuring the third-party application or device. Windows SNMP SoftwareOn the machine running OmniPeek you will need to install the SNMP Management and Monitoring Tools Windows Component. To install the Windows SNMP software:
Receiving SNMP Trap Messages from Third-party Applications or DevicesCertain management applications can send SNMP traps to the address of the machine running OmniPeek, and then post an entry in Summary Statistics. To receive SNMP trap messages, begin a capture using the SNMP Trap Adapter in OmniPeek. Note: Please refer to the documentation for the management application sending the SNMP traps for configuration details. Tip: You can set a trigger in OmniPeek to start a capture whenever it receives a trap. This works by creating an advanced filter using Analysis Module/SNMP Trap Adapter. Refer to OmniPeek online help for instructions on creating advanced filters and triggers. |
|
Lawful Intercept
Deploying & Testing Applications
Distributed Networks
Network Baselining
Network Forensics
Network Performance Analysis
- NetFlow
Network Performance Management
Network Security
Network Troubleshooting
Product Development Support
VoIP Monitoring and Analysis
Video Monitoring and Analysis
Wireless Network Analysis
10 Gigabit Networks
Industry Specific Solutions
OmniFlow Collector
NetFlow Collector
sFlow Collector
OmniPeek Network Analyzer
OmniEngine Software Probe
OmniVirtual VMWare Probe
TimeLine Network Recorder
Omnipliance Network Recorder
OmniAdapter Analysis Cards
Omnipliance Portable
Product Activation FAQs
Maintenance Programs
Product Versions
Contact Tech Support
Downloads
Training / Courses
Consulting
Custom Engineering
WildPackets Forums
MyPeek Community Portal
Video How-To's
Product Tips and Tricks
Networking Glossary
Networking Links
Free Utilities
Media Coverage
Media Kit
Blog
Peeks Newsletter
Success Stories
Reviews & Awards
Upcoming Events
Webinars & Webcasts
Industry Alliances
Channel Partners
Training Partners
Integration Partners
Partner Portal
Software Upgrades
Hardware
Training
Maintenance Renewal
Per Incident Support
Sales Policies
Contact Sales
COPYRIGHT © 2010 WILDPACKETS, INC | PrivacyAll registered and unregistered trademarks are the sole property of their respective owners






China
Germany
Japan
Korea
UK
United States












