Bruno,
If you can guarantee the router will be connected to the same port on the 3560 every time, you can try this script. It uses tracking and eem. Please let us know how it turns out.
On your 3560:
track 1 interface fa1/2 line-protocol
event manager applet WimaxUp
event track 1 state up
action 1 cli command "enable"
action 2 cli command "config ter"
action 3 cli command "router eigrp 100"
action 4 cli command "network 192.168.20.0"
action 5 cli command "end"
action 6 cli command "exit"
event manager applet WimaxDown
event track 1 state down
action 1 cli command "enable"
action 2 cli command "config t"
action 3 cli command "router eigrp 100"
action 4 cli command "no network 192.168.20.0"
action 5 cli command "end"
action 6 cli command "exit"
What the first script will do is add the network statement (like Jon suggested) while the interface that you're monitoring (the interface of the 3560 when you connect the router) is up. This script only runs once. While the interface is up, your 3560 will advertise the network. Once the interface goes down, either physically or admin shut, the second script will run and remove the network statement.
I can't stress to you enough that you must have control over the port that the router is connects to. The reason I say this is if a user or another administrator simply connects a PC to the port that you're monitoring, the script will still run. This is why I suggested port security earlier. I would at least enable port security and designate a port with the mac address that belongs to the interface of the router. That way you won't have any accidental outages if someone does come behind you and plug the non-router device into the port that will kick the script off. Be sure to change the above to match what you're wanting to advertise, your eigrp AS, and the tracked interace.
HTH,
John
*** Please rate all useful posts ***
HTH,
John
*** Please rate all useful posts ***
