I had open a post in lan switching for this particular problem and the expert from that forum has given the solution of embedded event manager so i need a help from this forum.
The probelm defination is==
Cisco 6509 (Core switch) connected to firewall on uplink side and on downlink its connected to 2 diffrent Cisco 6509 switches (Distribution) layer.All these links have been configured as Routed link and not as SVI.Now issue is when both the downlinks (coming from both distribution) switches go down i want to make the uplink from core to firewall to go down so that other core switch will take over and transfer teh traffic.
Attached diagram has details.tried configuring HSRP between 2 core switches but as teh links are routed link HSRP not working and both switches remain master but as on oppsite side Juniper firewall NSRP is implemented 2nd firewall not responding and core-2 ==fw2 link not transfer traffic.now when both the links of core go down link from core1-fw1 should go down so Fw2 will get active and will send traffic on link betwene core2-firewall2..please let me know what kind of configursation is required in EEM..
I think this policy should work for you. It requires two environment variables to be set before registering:
intf_watch_interfaces : Comma-separated list of interfaces to watch
intf_watch_uplink : Name of the uplink interface
event manager environment intf_watch_interfaces GigabitEthernet4/1,GigabitEthernet4/2
event manager environment intf_watch_uplink GigabitEthernet6/1
thanks for the reply.
really speaking i am very new to this EEM so dont know how this code will be written and how it will be applied.In real time scenario my down links are Ten gig 9/1 &y 9/3 while my uplink is Gig 1/2.can you guide me further to let me know how the code will look like and how it will be applied.My requirement when both 9/1 -9/3 go down Gig1/2 should come down and when any of teh downlink comes up Gig1/2 should come up.
u can also share the possible configuration guides for the same if u have any.
Thanks for the help.
Do the following (assuming you have a disk0:):
copy tftp://x.x.x.x/sl_intf_watch.tcl disk0:/policies
event manager directory user policy disk0:/policies
event manager environment intf_watch_interfaces TenGigabitEthernet9/1,TenGigabitEthernet9/3
event manager environment intf_watch_uplink GigabitEthernet1/2
event manager policy sl_intf_watch.tcl
Where x.x.x.x is the IP address of your TFTP server.
After that, the policy is registered, and waiting for the interfaces to go down.
So i need to download the TCL file attached in previous post and need to upload the same in my disk:0 via tftp and then need to put those 4 comamnds mentioned above.i have a doubt here.in the comamnds mentioned above we just mention the interfaces to be watched then where exactly we do the script for interfaces to go down and interfaces to come up.is this included in the TCL file or just those two comamnds take care of everything?Do the file attached in previous post has the real interfaces defined there??
Any recommanded guide for this kind of configuration...
The Tcl policy will take care of watching the interfaces, and doing the shutdown and no shutdown. Yes, you must take that script, and upload it to your switch. You must also configure the environment variables as I have indicated. The script will look for those variables to know on what interfaces it will operate.
Thanks for the reply.i will check the same.
==does those enviornmental variable will take care of reverse scenario also ??? i mean when my uplink will go down ideally both the uplink from down should go down.so i need to add 2 more statements or those 4 statements will take care of both scenarios.
last question is this setup is presently
working so do you suggest me to add the scripts as will as those variables in live scenario or during any maintainance window??will the script take care immediately or it will require any reboot.
Thanks in advance.
Yes, the Tcl policy will bring the uplink back up when at least one of the distribution links comes back up.
The policy will take effect immediately. There will be no downtime. However, if you're worried about affecting production, then I strongly recommend you try this out in a lab first.
All this we were doing for the 2 downlinks going down so that uplink will go down...
my query was if the Uplink goes down during normal case whats the remedy to make both downlinks down because this is also a failure scenario in which case firwall2 will transfer data to core 2 and core2 has to take it down.
for this do i need to mention 2 more enviornmental variable and add 1 more Tcl policy or same policy will work with 2 more enviornmental variables or no more change at all required.
with this my problem will get completely resolved
Thanks for teh help.
hope this will resolve my issue completely.will check the same during next possible maintainance window and let u know the result.
just for my info==so changed the policy for this particular requirement right ??