This article explains the following error message:
The mime-pattern junos-default-bypass-mime error!
and provides procedures for checking memory.
Commit fails with the following error messages while configuring chassis cluster:
error: The mime-pattern junos-default-bypass-mime error! error: The filename-extension junos-default-extension error! error: The custom-url-category Adult_Sexually_Explicit error! error: configuration check-out failed
These error messages will appear if clustering is enabled in two devices with different memory units. For example if you try to configure chassis clustering in 210-1 (Base Memory) as Primary node and 210-2 (High Memory) as secondary node, and then issue the command commit check , that will succeed. While issuing commit you will see the following behavior.
commit check
commit
{primary:node0}[edit] root@210-1# commit node0: configuration check succeeds node1: error: The mime-pattern junos-default-bypass-mime error! error: The filename-extension junos-default-extension error! error: The custom-url-category Adult_Sexually_Explicit error! error: configuration check-out failed node0: error: remote commit-configuration failed on node 1 error: commit failed
As mentioned, the memory units are different in both devices. To enable clustering, it is important to make sure they are the same hardware models, running on the same version of the software.
To check the hardware, use command show chassis hardware . In the base memory device, the output will resemble this:
show chassis hardware
show chassis hardware Hardware inventory: Item Version Part number Serial number Description Chassis AU4209AF1198 SRX210B Routing Engine REV 08 750-021773 AT4209AF1198 RE-SRX210B FPC 0 FPC PIC 0 8x FE Base PIC Power Supply 0
In high memory devices, the output will resemble this:
show chassis hardware Hardware inventory: Item Version Part number Serial number Description Chassis AD4109AA0352 SRX210H Routing Engine REV 33 750-021779 AAAX5645 RE-SRX210H FPC 0 FPC PIC 0 2x GE, 6x FE, 1x 3G Power Supply 0
After enabling chassis cluster on devices with the same memory units (Base to Base or High to High), these error messages will no longer be seen.