
HP OpenView NetMetrix/UX Release Notes version 6.0
October 1, 1998
Known Problems and Work-Arounds
5967–4358 35
you might configure the following filter on the agent:
(host ip kermit) and (status crc)
then post filter the instance with this filter:
(proto udp nfs)
For details on post filtering, refer to page 381 of User’s Guide.
Description When using Protocol Analyzer with a multi-interface LanProbe,
the base window may not initially show the correct interface
Symptom If you do not explicitly specify an instance name, Protocol Analyzer
always attaches to the “default” instance, no matter what interface that
instance uses and no matter what interface you chose when launching
the tool.
Note that a newly-created capture instance uses the correct interface.
Work-Around To view an existing instance for the correct interface, Choose
Instance➤Attach… and select the correct instance_name. Alternatively,
include an instance name when starting Protocol Analyzer, as discussed
in the protanal(1) man page.
Description Protocol Analyzer cannot decode SNMP v1 64-bit counters
Symptom SNMP packets contain SNMP v1 64-bit counters are marked as packets
with errors. The detail decode indicate “UNKNOWN TYPE” in the value
field. [Defect ID 0804–22764]
Work-Around None.
Description Not all packets are decoded in Protocol Analyzer
Symptom Packets have blank summary description lines.
Details Packets that Protocol Analyzer does not understand have blank sum-
mary descriptions. This happens in AAL/5 instances. Protocol Analyzer
does understand LANE control packets and NetBios in LANE packets.
[Defect ID 0804–022863]
Work-Around None.
Comentários a estes Manuais