Forum Discussion
Reselecting route peer in MRF
A new iRule command (MR::message attempted) allows you to specify which hosts cannot be used for routing a message or show which one has already been used. It could be used to retransmit a message to another pool member.
If invoked before a message is routed (MR_INGRESS or MR_FAILED) it can be used to specify which hosts will be ignored. The syntax requires you to also specify either a Virtual Server (virtual) or MR Transport Config (config). The keyword none clears this blacklist.
If invoked after a message is routed (MR_EGRESS or MR_FAILED) the config section shows to which MR transport-config and host the message was routed. The host does not suffice because you may be able to connect using TCP but not SCTP.
The format is the same for MR::message route, MR::message attempted and MR::peer but unlike MR::message route, attempted hosts only contains hosts, so you will not see a pool as a destination
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com