Disable binary logging in your session, drop the table, and enable binary logging.

SET sql_log_bin = 0;
DROP TABLE IF EXISTS ... ;
SET sql_log_bin = 1;

This works because if the Slaves do not see the DROP TABLE command registered in the Master's binary logs, it cannot run the DROP TABLE.

I have recommended using SET sql_log_bin = 0; before in my earlier posts

• Nov 12, 2012 : Mysql replication and ignore tables
• Feb 03, 2012 : Scheduled optimization of tables in MySQL InnoDB
• Jul 11, 2011 : ALTER TABLE on a large table with an indexed column (This is where I use SET sql_log_bin = 0; to directly prevent data from being written to Slaves)

Give it a Try !!!

Replication filtering rules will only work on the situations where you do

USE mysql;
DROP TABLE failover_console;

When you do DROP TABLE mysql.failover_console;, that will slip through the cracks. Why?

The problem stems from you using Binlog_Ignore_DB: mysql. This looks for mysql to the the default database. Still, you explicitly use mysql. in front of the table name failover_console. Please note how this happens as explained in the MySQL Documentation:

When using statement-based logging, the following example does not work as you might expect. Suppose that the server is started with --binlog-ignore-db=sales and you issue the following statements:

USE prices;
UPDATE sales.january SET amount=amount+1000;

The UPDATE statement is logged in such a case because --binlog-ignore-db applies only to the default database (determined by the USE statement). Because the sales database was specified explicitly in the statement, the statement has not been filtered. However, when using row-based logging, the UPDATE statement's effects are not written to the binary log, which means that no changes to the sales.january table are logged; in this instance, --binlog-ignore-db=sales causes all changes made to tables in the master's copy of the sales database to be ignored for purposes of binary logging.

Next time, you should do one of two things:

Either

USE mysql
DROP TABLE failover_console;

or

DROP TABLE IF EXISTS mysql.failover_console;

GIVE IT A TRY !!!