PoE port redundancy (link-state tracking or other feature)

[ReneiroTerc2194]

Hello everyone!  Thank you for all of the support you guys provide!

I am testing a theory.

I have two L2 switches (2960s) connected via a trunks on ports 23 and 24.  Both connections are by microwave radios.  Port 24 trunk is a redundant link in case the radio on P23 goes down.  However, I believe that the radio on P24 is causing minor interference that I'd like to get rid of.  But since both are PoE, it's kind of hard to eliminate.

On my lab switches, I tested Link-State tracking and in a very simple environment (no radios, simple config, one vlan), it works like a charm. Because the radio on P23 has a feature that disables it's data port if the RF becomes unstable or loses connectivity, I know that Cisco's link-state tracking will kick in and traffic will start flowing through P24 (this radio does not have the port disabling feature). 

My wish is to have P24 shut down or have not be a PoE source UNTIL P23's line protocol goes down.  Additionally, if/when P23 comes back up, P24 will need to go back to it's "standby" state.  

Is this wishful thinking?

[paul driver]

Hello
flex links would be applicable also

example:

int x/x
switchport backup interface x/y

or 

backup interface x/y

[ReneiroTerc2194]

Thanks for the response.  I need the standby interface to only provide power when the primary loses link.  Will flex link work for this or am I looking at this from the wrong angle?

[paul driver]

Hello

Yes this should be accomplished if backup/flex link feature is supported, as it puts the backup port into a stanby state with its line protocol down

[ReneiroTerc2194]

Thank you for the help Paul.  I was finally able to lab this up and it works just as advertised and it's very handy.  My only problem, as it applies to my application, is that the standby port still provides power to the device.  Do you know if there is a means to kill PoE power while a port is in standby?