Customers may observe repeated log messages similar to the following while RPM (Real-Time Performance Monitoring) tests continue to pass successfully:
packetio[19229]: [t:19890] [Error] RPM_HDLR:PKT_HDLR: not supported option
The issue is commonly seen when RPM ICMP probes are configured over GRE tunnel interfaces (fti0). Although the RPM tests complete successfully and report TEST_PASSED, the packet timestamping handler generates error messages because it receives GRE-encapsulated packets that are not supported by the current RPM timestamping implementation.
TEST_PASSED
This behavior can generate unnecessary alarms or concerns in production environments and may require Engineering review when observed on customer systems.
Log messages:
Repeated throughout the logs while RPM tests continue to pass:
rmopd[14070]: TEST_PASSED: test-owner=icmp_gre test-owner-type=RPM test-name=icmp
rmopd[14070]: TEST_PASSED: test-owner=icmp_gre_backup test-owner-type=RPM test-name=icmp_backup
The customer is using RPM ICMP probes over GRE tunnel interfaces:
set services monitoring rpm owner icmp_gre test icmp probe-type icmp-ping
set services monitoring rpm owner icmp_gre test icmp target X.X.X.X
set services monitoring rpm owner icmp_gre test icmp source-address X.X.X.X
Traffic traverses GRE tunnels configured on fti0:
fti0
set interfaces fti0 unit 0 tunnel encapsulation gre
RPM_HDLR:PKT_HDLR: not supported option
The RPM packet timestamping/offload functionality does not support GRE-encapsulated packets.
When RPM ICMP probes traverse fti0 GRE tunnels, GRE-encapsulated packets enter the RPM packet handler. The handler only supports native UDP or ICMP packets and does not recognize GRE (IP Protocol 47).
This results in log messages indicating an unsupported packet type even though the RPM probe operation itself completes successfully.
Do not use RPM timestamping offload with GRE tunnel-based RPM probes.
Configure RPM with:
offload-type none
instead of:
offload-type pfe-timestamp