I encountered the M3UA problem on ITP. If enable multi-instance, the latency for ITP response SACK to ASP is almost 190ms. So ASP will resend the message. But if I disable multi-instance, ITP send SACK is shortly, ASP will not resend message to ITP.
There is no problem with the BEAT message you included, and the ITP responded properly with BEAT ACK. The "No Message Parameters" text is simply debug output indicating that there are no parameters included with this message....that is *NOT* an error.
I mean the selective ack (know as âdelayed ackâ) message response to ASP was too slow after enable multi-instance.
I try to modify the delayed SACK value to 40ms that recommend for the Telecoms industry on ITP. But the minimum is 100ms.
Range is 100 through 500 milliseconds. The default is 200 milliseconds.
So I set to 100ms.
I found every SACK latency for data chunk to ASP was between 90ms to 106ms. And don't see duplicate data chunk from ASP, the problem has been resolved. By the way the network latency from ITP to ASP is within 1ms to 6ms.
Introduction: The "external-out enable" command is available for
configuration under the "router ospf process" in case of the IOS-XR
operating system. This command basically enables advertisement of
intra-area routes on the device as external routes in th...
Introduction Basic configuration for netflow Scale parameters for
netflow Netflow support Architecture Packet flow for netflow Inside the
LC CPU Netflow Cache size, maintenance and memory Sample usage Cache
Size Aging Permanent cache Characteristics Which...