Agilent Technologies J3972A User's Guide Page 356

  • Download
  • Add to my manuals
  • Print
  • Page
    / 551
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 355
Protocol Analyzer
Using Packet Capture Instances
5967–9446 355
To arm an instance
1 Attach to the instance, if necessary.
2 Choose InstanceArm.
When you arm an instance, the current configuration (settings and filter)
is applied to the instance, the instance is configured on the agent, and
agent resources are allocated for the instance. Packet capture is not
started, although the packet match counter does track how many
packets match the current filter.
The primary reason to arm an instance, rather than start one, is to make
the instance available to the Alarms utility. You can then connect the
packet capture instance to an alarm. For example, you might configure
an alarm such that it starts capturing packets when network utilization
exceeds a specified percentage. For details, refer to page 430.
You can also arm an instance by giving the protanal command, as
discussed on page 405. In this case, the filter and settings to use are read
from a file specified on the command line.
See Also “Working with Configuration Files” on page 399.
“To save captured packets in a trace file” on page 393.
“To save filter/settings in a file” on page 400.
“Using the protanal Command” on page 405.
“Setting Alarms” on page 430.
Caution
If you are arming an instance that has already been either armed or
started and stopped, the current configuration supersedes the previous
settings and filter. In addition, any previously captured packets for that
instance are discarded. To keep the captured packets, ensure that you
save them in a file before you arm the instance. Refer to page 393 for
instructions.
Page view 355
1 2 ... 351 352 353 354 355 356 357 358 359 360 361 ... 550 551

Comments to this Manuals

No comments