The minimum and maximum range for interface MTU as shown in CLI command completion may not be the true range for that particular interface.
The MTU value that falls outside the minimum and maximum ranges for a particular interface will be caught during commit. Please see the following examples.
Example 1 – SRX100 platform
lab@SRX100# set interfaces fe-0/0/2 mtu ? Possible completions: <mtu> Maximum transmit packet size (256..9192) << The CLI command completion shows min/max range of 256-9192. [edit] lab@SRX100# set interfaces fe-0/0/2 mtu 9192 lab@SRX100# commit check [edit interfaces fe-0/0/2 mtu] 'mtu 9192' MTU should be in range (256..1624) << When configured with 9192, since this falls outside the true MTU range for this particular type of interface, commit error is thrown. The correct range is also displayed as part of commit error. error: configuration check-out failed
Example 2 – SRX210 platform
lab@SRX210# set interfaces ge-0/0/1 mtu ? Possible completions: <mtu> Maximum transmit packet size (256..9192) [edit] lab@SRX210# set interfaces ge-0/0/1 mtu 9192 [edit] lab@SRX210# commit check [edit interfaces ge-0/0/1 mtu] 'mtu 9192' MTU should be in range (256..9014)