When the packet size is not configured, packets are sent at the minimum size required to fit all the required
information. Even when the packet size is configured, the packets may be larger than the configured size if
the required information exceeds the configured value.
If a probe packet is too large, it may get dropped somewhere in the network.Note
Task ID
OperationsTask ID
read, writeethernet-services
Examples
The following example shows how to configure the minimum size of outgoing probe packets using default
padding of all 0s as needed:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# ethernet sla
RP/0/RSP0/CPU0:router(config-sla)# profile Prof1 type cfm-loopback
RP/0/RSP0/CPU0:router(config-sla-prof)# probe
RP/0/RSP0/CPU0:router(config-sla-prof-pb)# packet size 9000
RP/0/RSP0/CPU0:router(config-sla-prof-pb)# commit
The following example shows how to configure a hexadecimal test pattern to pad packets with to reach the
minimum packet size:
RP/0/RSP0/CPU0:router# configure
RP/0/RSP0/CPU0:router(config)# ethernet sla
RP/0/RSP0/CPU0:router(config-sla)# profile Prof1 type cfm-loopback
RP/0/RSP0/CPU0:router(config-sla-prof)# probe
RP/0/RSP0/CPU0:router(config-sla-prof-pb)# packet size 9000 test pattern hex 0xabcdabcd
RP/0/RSP0/CPU0:router(config-sla-prof-pb)# commit
Cisco ASR 9000 Series Aggregation Services Router Interface and Hardware Component Command Reference,
Release 5.3.x
290
Ethernet OAM Commands on the Cisco ASR 9000 Series Router
packet size
To Next Page
Loading...
Need help?
General
