comstop

Abstract

Provides a way to follow transmissions and receptions by setting breakpoints for specific communications.

Syntax

comstop <link_objref> | <tx_objref>:<rx_objref> [<ps_name>]

Argument Type Description
<link_objref> integer or string numeric object ID or hierarchical name of the communications link-of-interest
<tx_objref> integer or string numeric object ID or hierarchical name of a channel, module, or node associated with the transmitter-of-interest
<rx_objref> integer or string numeric object ID or hierarchical name of a channel, module, or node associated with the receiver-of-interest
<ps_name> string [optional] one or more space-separated pipeline stage names

Details

Breakpoints will be set for any communication on either a specified link (<link_objref>) or from a specified transmitter to a specified receiver (<tx_objref> to <rx_objref>). Use the wildcard " * " for <link_objref>, <tx_objref>, or <rx_objref> to match any object of the corresponding type. For example,

comstop * | *:*          -- stop at any communication
comstop <tx_objref>:*    -- stop at any communication from xmtr <tx_objref>

Optionally, multiple pipeline stage names can be specified to set breakpoints at specified pipeline stages. <ps_name> can be any of the following:

Table 28:

Point-to-point links txdel propdel error ecc
Bus links txdel closure propdel coll error ecc
Radio links txdel closure chanmatch tagain propdel ragain
power inoise bkgnoise snr ber error ecc

Example

ODB> comstop * txdel propdel
Added breakpoint #0: stop at communication on any object in "txdel" "propdel" pipeline stage

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com