Loading...
Loading...
Error messages similar to this are present in the ltm log: -- err mcpd[9369]: 01020036:3: The requested monitor instance (/part10/test_mon 90.90.90.90%10 443 ltm-pool-member) was not found. -- err mcpd[9369]: 01070734:3: Configuration error: Configuration from primary failed validation: 01020036:3: The requested monitor instance (/part10/test_mon 90.90.90.90%10 443 ltm-pool-member) was not found.
Monitor instances in a partition that uses a non-default route domain can fail validation on secondary blades. mcpd restarts.
A chassis-based system with multiple blades. This can occur a few different ways: - A monitor is attached to an object that is configured in a partition that uses a non-default route domain, but the address of the monitor is explicitly using the default route domain (e.g. %0). - A monitor defined in the Common partition is attached to an object from a partition where the default route domain is different.
There are two possible workarounds: -- Move the monitor to the /Common/ partition and do not specify %0 in the Alias Address. -- Do not use monitors from other partitions where the default route domain is different.
The complete state for addresses on the primary blade is propagated to secondary blades.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.