Home > Support > Legacy Products >

print

RMONGrabber

Versions Compatible with other WildPackets Products

Recommended System Requirements

The recommended system requirements for RMONGrabber are those meeting the system requirements for the compatible versions of OmniPeek or EtherPeek.

FAQs

• If I did not click the Stop Capture button, why does my capture stop?
• How can I see the packets in real-time while capturing?
• If I set a buffer size in Peek do I also need to set a buffer size for the probe?
• Can the probe capture VLAN tags?
• Can the probe filter on certain Ports and IP Addresses?
• How do I disable RMONGrabber?
• RMONGrabber 1.6 is compatible with which Peek products?
• Will RMONGrabber work with OmniPeek Enterprise Connect?
• When using "Save to disk" I am unable to open the saved capture file, why?
• While using RMONGrabber 1.6, the application hangs. What can I do fix this?
• How can I make RMONGrabber work with my Cisco Switch?
• What is the product activation mentioned in the installer?
• Why is my Netscout probe capturing packets with extra bytes?
• Why am I unable to use a filter as a Start Trigger?
• Why do I see packets that do not match my filter?

Remote captures will stop automatically when the buffer on the RMON probe is full. The buffer is set in the RMONGrabber Probe Capture Options.

Within the RMONGrabber Probe Capture Options, select collect packets during capture. Captured packets will then be sent to the Capture window while the remote capture is still in progress. If this option is not selected, packets are not seen in the local Capture window until the remote capture is stopped.

If Triggers are used, make sure that Collect packets during capture is selected and that

Collect packets after capture is stopped is not selected.

Yes, the capture buffer on the RMON probe is separate from the capture buffer defined for the Capture window in Peek. When the remote buffer on the RMON probe is full, the remote capture will stop. If the remote buffer size is smaller than the buffer size set for the Capture window, the remote capture will stop, even though the Memory usage indicator for the Capture window shows space remaining in the local capture buffer.

Yes, within the RMONGrabber Probe Filter Options select 802.1Q (VLAN tags).

Yes, within the RMONGrabber Probe Filter Options select Exclusive or Inclusive:

Inclusive: Select this option to have the probe accept all packets matching the defined filter. Only packets that match the filter are passed to the capture buffer.

Exclusive: Select this option to have the probe reject all packets matching the defined filter. Only packets that do not match the filter are passed to the capture buffer.

To disable RMONGrabber as an Analysis Module:

1. Choose Tools > Options…. The Options dialog appears.
2. Click Analysis Modules in the navigation pane to open the Analysis Modules view.
3. Select or clear the Enabled check box for the RMONGrabber analysis module.
4. Click OK.

RMONGrabber 1.6 is compatible with:

• OmniPeek Enterprise 4.0.1 or later
• OmniPeek Enterprise with Enhanced Media Option 4.0.1 or later
• OmniPeek Workgroup 4.0.1 or later
• OmniPeek Workgroup Pro 4.0.1 or later
• OmniPeek Workgroup Pro with Enhanced Media Option 4.0.1 or later

No, RMONGrabber will not function when installed with OmniPeek Enterprise Connect.

Using the Capture option "Save to disk" to save packets during capture is not recommended, as corrupt capture files may result. To turn off Save to Disk, uncheck the "Save to disk" checkbox in the General section of the Capture Options dialog. Note: saving packets to disk manually (via File->Save All Packets) is fully supported.

The monitor adapter may be active which is not recommended.

To disable the Monitor Adapter, choose Monitor->Monitor Options, select "None" in the Adapter list, and click "OK".

RMONGrabber will successfully capture packets from a Cisco Catalyst® 6500 Series switch with the proper Network Analysis Modules (NAM) installed. In order to properly capture packets, the packet slicing option needs to be enabled. This is true even when you do not wish to slice the packets, and you want the entire packet. In order to make this work without actually effecting any change in the packet, select the packet slicing length to greater than 1518 bits, or the maximum length of an Ethernet packet.

When you install RMONGrabber version 1.6 the installer sends a secure message to a web server located at WildPackets. The installer sends the following information: serial number, product information, name, company name, and an ID number associated with your computer. This process will assist us in reducing software piracy, as we can ensure that our software is used solely by authorized customers. Please visit http://www.wildpackets.com/activation for more information.

Some NetScout probes include Frame Check Sequence (FCS) bytes with captured packets. When capturing from these probes an extra 4 bytes are added to the end of each packet, as RMONGrabber erroneously adds its own FCS bytes.

Because of the way RMONGrabber interacts with RMON probes, you cannot use a filter as a Start Trigger when capturing from an RMON device. As a result, the Filter option is disabled when configuring a Start Trigger. You can use filters for Stop Triggers, and to filter packets while capturing.

Filters are sent as a network message to the probe. Expect to see a small delay between when a filter is set and when it takes effect on the RMON probe. Because of this delay, you may see a few packets not matching the filter criteria at the beginning of a capture window.

Additional Support and Resources

If you still need assistance, please select one of the following links for additional support.

Downloads

MyPeek

Networking Resources

Contact Technical Support