The customer is unable to configure OAM Iterator profile cycle-time to 30 minutes in MX304 router and the customer claim that they are not running MEF36 mode.
[edit]
labroot@router-re0# set protocols oam ethernet connectivity-fault-management performance-monitoring sla-iterator-profiles IDDM cycle-time 1800000
labroot@router-re0# commit check
[edit protocols oam ethernet connectivity-fault-management performance-monitoring]
'sla-iterator-profiles IDDM'
Iterator cycle time has to be 100ms, 1s, 10s 20s, 30s or 60s for MEF36 mode iterators
error: configuration check-out failed
Once enhanced-cfm-mode (and MEF36) is enabled, and then it is deleted, the router system will remain in MEF36 mode, until you reboot router.
After the system rebooted, and enhanced-cfm-mode is NEVER configured, then the commit (cycle-time 30 minutes) will go through.
Currently, there is no CLI command to check which mode used.
However, for MX304 router, which is AFT based line card, the customer SHOULD always use MEF36 mode for performance-monitoring, which means should apply enhanced-cfm-mode and measurement-interval settings, and cycle-time should also setup correctly in the available range. It makes no sense to commit cycle-time 30 minutes.