| Bug ID |
8292
|
| Summary |
dissect Y.1731 defect type with reverse order.
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
1.6.12
|
| Hardware |
x86
|
| OS |
Windows XP
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Dissection engine (libwireshark)
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 9923 [details]
mpls oam capture file
Build Information:
dPeerME 01 02 Any peer maintenance entity defect arising outside the MPLS
subnetwork. It is not suggested that these are individually identified and
defined for each type of peer network. Hence, only an indication is needed that
it is not a defect in the MPLS subnetwork. Note that this defect is not
generated by MPLS OAM mechanisms, rather it is an input to MPLS OAM from a
layer network interworking function.
dLOCV 02 01 Simple Loss of Connectivity Verification due to missing CV or
FFD OAM packets with expected TTSI. Note that:
1) If the cause of dLOCV is the server layer (i.e., there is also an
incoming FDI signal from the server layer), then the DT codepoint 01 01Hex is
used.
2) If the cause of dLOCV is the peer maintenance entity (i.e., there is also
an incoming FDI signal from the IWF with a DT codepoint of 01 02), then the DT
codepoint 01 02Hex is used.
The dLOCV codepoint 02 01Hex is only used for MPLS layer simple connectivity
failures only.
--
Wireshark dissects Y.1731 defection type in reverse order,such as defect type
"0201" shall be dLOCV, but it is dissected as dPeerME("0102"). all wireshark
release included this mistake.
You are receiving this mail because:
- You are watching all bug changes.