Try it now!
telnet towel.blinkenlights.nl
:)
Tuesday, April 29, 2008
Sunday, April 27, 2008
Saturday, April 26, 2008
Tuesday, April 22, 2008
wget example
wget --http-user=admin --http-password=admin http://$CAM_IP/img/snapshot.cgi?size=640x480 -O $APPS_HOME/photo.jpg -o $APPS_HOME/wget.log
This is an example I capture the snapshot files from my Linksys WVC200.
--http-user and --http-password used to pass the http authentication
-O specify the output file
-o provides output log
This is an example I capture the snapshot files from my Linksys WVC200.
--http-user and --http-password used to pass the http authentication
-O specify the output file
-o provides output log
Pictures conversion with ImageMagick
My Environment: RH FC8 Linux, i386
The package I'm using: ImageMagick-6.3.5.9-1.fc8
There are plenty of choice to convert a picture from one format to another, ImageMagick is an option if you want to do the conversion in command line and run in background.
Example:
- To convert a file from jpg to png
convert photo.jpg photo.png
- Convert and change the size
convert -size 320x240 photo.jpg photo.png
The package I'm using: ImageMagick-6.3.5.9-1.fc8
There are plenty of choice to convert a picture from one format to another, ImageMagick is an option if you want to do the conversion in command line and run in background.
Example:
- To convert a file from jpg to png
convert photo.jpg photo.png
- Convert and change the size
convert -size 320x240 photo.jpg photo.png
Adding 3rd party SIP phone in CUCM
A quick how-to on how to add a 3rd party SIP phone in CUCM, for version 5.0 or above. The environment I'm having here is CUCM 6.1 + X-Lite 3.0 on RH FC8 Linux.
1. From Cisco Unified Communications Manager Administration page, from the menu select User Management > End User and click add new button. Create an user in LDAP if you have done the LDAP integration.
2. Create a user with the following parameters:
- User ID: 1099
- Password: abc123
- PIN: 123456
- Last name: Panda
- First name: SIP
- Telephone number: 1099
3. Click Save.
4. From Cisco Unified Communications Manager Administration page, from the menu select Device > Phones and click add new button.
5. For the phone type select Third Party SIP Device (basic), and click Next.
6. On the Phone configuration page, use the following parameters:
- MAC Address: AABBCCDDEEFF (MAC address of your NIC)
- Phone button template: Third-Party SIP Device (Basic)
- SIP Phone security profile: Non Secure SIP Profile auth by string
- SIP Profile: Standard SIP Profile
- Owner ID: 1099
- Digest User: 1099
7. Click Save and OK
8. Click Line [1]-Add a new DN.
9. Use the following parameter for Directory number configuration:
- Directory number: 1099
10. Click Save.
11. On your laptop, run the X-Lite IP Phone application, and configure the X-Lite to use the following parameters:
- Enabled: Yes
- Display Name: Panda SIP
- Username: 1099
- Authorization user: 1099
- Password: abc123
- Domain/Realm: 192.168.1.1 (Your CUCM address)
- SIP Proxy: 192.168.1.1 (Your CUCM address)
- Out Bound Proxy: 192.168.1.1
The X-Lite Phone will register and login with the Communications Manager.
To Download X-Lite, go here: http://www.counterpath.com/
Try this!
nslookup 69.69.69.69
dig -x 69.69.69.69
:)
Original Post from: http://ardenpackeer.com/asides/geek-humour/
dig -x 69.69.69.69
:)
Original Post from: http://ardenpackeer.com/asides/geek-humour/
Monday, April 21, 2008
Enable routing on your linux box
MeetingPlace - Disable scheduling on voice user interface (VUI)
To disable the scheduling on voice user interface, telnet or console to your MP8106 or 8112 server, then:
1. su
2. Password is a bit tricky. You have to contact Cisco TAC engineers to generate a "password-of-the-day" for you. I recommend you to ask them to generate 7 days passwords for you for safety sake.
3. Then do a mtgmode -?
This will provide you the following list:
mtgplace:csc$ mtgmode -?
usage: mtgmode [-s][-r][-o]
Check or change the reservationless meetings setting.
To change the secondary settings please use 'MeetingTime'.
-s Scheduled meetings only; disable reservationless
meetings
-r Enable both scheduled and reservationless meetings
-o Enable both scheduled and reservationless meetings but VUI menu provided is reservationless-only.
4. To disable the scheduling on VUI, choose the mtgmode -o option. If you want to re-enable it, simply do a mtgmode -r.
1. su
2. Password is a bit tricky. You have to contact Cisco TAC engineers to generate a "password-of-the-day" for you. I recommend you to ask them to generate 7 days passwords for you for safety sake.
3. Then do a mtgmode -?
This will provide you the following list:
mtgplace:csc$ mtgmode -?
usage: mtgmode [-s][-r][-o]
Check or change the reservationless meetings setting.
To change the secondary settings please use 'MeetingTime'.
-s Scheduled meetings only; disable reservationless
meetings
-r Enable both scheduled and reservationless meetings
-o Enable both scheduled and reservationless meetings but VUI menu provided is reservationless-only.
4. To disable the scheduling on VUI, choose the mtgmode -o option. If you want to re-enable it, simply do a mtgmode -r.
Saturday, April 19, 2008
Nexus: Hands on with NX-OS, Part#1
A good article from Mark Lewis on Cisco Subnet about NX-OS:
http://www.networkworld.com/community/node/26877
Some notable difference between NX-OS and IOS are some of the L3 features like OSPF, HSRP, etc.
http://www.networkworld.com/community/node/26877
Some notable difference between NX-OS and IOS are some of the L3 features like OSPF, HSRP, etc.
Wednesday, April 16, 2008
JSP - Wait before redirect page
You might want to add some delay before redirect the page, instead of using sendRedirect(), which will redirect immediately, you can use response.setHeader() in JSP.
response.setHeader("Refresh", "5; URL=http://pandaeatsbamboo.blogspot.com/test.jsp")
You will then be redirected to the page after 5 seconds.
response.setHeader("Refresh", "5; URL=http://pandaeatsbamboo.blogspot.com/test.jsp")
You will then be redirected to the page after 5 seconds.
Tuesday, April 15, 2008
Linksys WVC 200 Snapshots
Linksys WVC200 wireless surveillance camera gives you a way to take snapshots and you can then show or store it.
Take snapshots
http://cam-ip/img/snapshot.cgi?size=640x480
http://cam-ip/img/snapshot.cgi?size=320x240
http://cam-ip/img/snapshot.cgi?size=160x128
Return low quality image
http://cam-ip/img/mobile.htm
Query cam configuration
http://cam-ip/util/query.cgi
Saturday, April 12, 2008
CCIE R&S Lab Attack Plan - Part I
There is a must read article on internetworkexpert blog:
R&S Lab Attack Plan - Part I
Take a look if you are preparing for your lab exam.
R&S Lab Attack Plan - Part I
Take a look if you are preparing for your lab exam.
Flexlink configuration
Flexlink is a fast convergence feature and allows users to configure one of the switchport interface to backup another switchport interface.
Active Interface Configuration
interface GigabitEthernet4/3
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100
switchport mode trunk
switchport backup interface Gi4/4
Backup Interface Configuration - Remains the same
interface GigabitEthernet4/4
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100
switchport mode trunk
Gig4/3 and Gig4/4 will no longer participate in Spanning-Tree after configuring flexlink.
Verify
show interfaces switchport backup
Active Interface Configuration
interface GigabitEthernet4/3
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100
switchport mode trunk
switchport backup interface Gi4/4
Backup Interface Configuration - Remains the same
interface GigabitEthernet4/4
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 100
switchport mode trunk
Gig4/3 and Gig4/4 will no longer participate in Spanning-Tree after configuring flexlink.
Verify
show interfaces switchport backup
Sunday, April 6, 2008
Cat6K - Software Modularity System Tags
Similar to the idea of a database rollback, Cisco IOS Software Modularity can roll back to a set of installed files defined by a tag.
There are 3 Cisco-defined tags that are created by default:
- CISCO_BASE - This tag is defined as the base image with no patches or other tags. Using this tag with the install rollback command takes you back to the installed bsae image.
- CISCO_LATEST - This tag is defined as removing one level of install file. Using this tag with the install rollback command removes the set of files that were added with the last install file command entry. If the patch is in an active state, it will set the patch to a PendRoll state meaning that the changes will not take place until the install activate command is entered. If the patch as been installed but not activated, the install rollback command removes the installed patch.
- CISCO_LATEST_ACTIVATE - This tag is defined as removing one level of install activation. Using this tag with the install rollback command removes the set of files that were most recently activated by the install activate command. If multiple maintenance packs or patches werer installed with the install file command and then got activated simulatenously with a single install activate command, all files are marked to be rolled back.
Create Tag
1. To create a tag, execute the "install commit" command as seen below:
6500-x#install commit disk0:/sys ospf_fix
2. To verify what tags have been installed:
6500-x#show install tags running
Tags defined over software running on location s72033_rp - Slot 1 :
Tagname # of Files Date Committed
------------------------------- ---------- ------------------------
ospf_fix 2 19:31:48 UTC May 9 2006
Tags defined over software running on location s72033 - Slot 1 :
Tagname # of Files Date Committed
------------------------------- ---------- ------------------------
ospf_fix 1 19:31:48 UTC May 9 2006
Repackaging
The repackage feature will copy all necessary files to a single binary file which can be installed on another system. The "install repackage" command will be used.
6500-x#install repackage disk0:/sys disk0:/lab_repackage.bin
To verify, execute dir disk0:
6500-1#dir disk0:
Directory of disk0:/
1 -rwx 69213304 Apr 25 2006 20:08:28 +00:00 s72033-ipservicesk9-vz.sx4-demo
2 -rwx 636416 Apr 25 2006 20:10:44 +00:00 s72033-XMA0001.122-18.SXF4
3 -rwx 769024 Apr 25 2006 20:11:20 +00:00 s72033-XMA0002.122-18.SXF4
4 -rwx 1287168 Apr 25 2006 20:11:46 +00:00 s72033-XMA0003.122-18.SXF4
5 drwx 1 May 9 2006 18:08:48 +00:00 sys
81 -rwx 69963776 May 9 2006 19:44:08 +00:00 lab_repackage.bin
512065536 bytes total (278913024 bytes free)
Rollback
Execute "install rollback" to roll the system back:
6500-x#install rollback disk0:/sys ospf_fix
Verify the patch is in the "PendRoll" state:
6500-1#show install running
Software running on card installed at location s72033_rp - Slot 1 :
B/P C State Filename
--- - -------- --------
B * Active disk0:/sys/s72033_rp/base/DRACO2_MP
MP Maintenance Pack MA0001.122
P * Active disk0:/sys/s72033_rp/patch/patch-XAA2101-00-0-n.so
MP Maintenance Pack
P PendRoll disk0:/sys/s72033_rp/patch/patch-XAA2102-01-0-n.so
Software running on card installed at location s72033 - Slot 1 :
B/P C State Filename
--- - -------- --------
B * Active disk0:/sys/s72033/base/s72033-ipservicesk9-vm(12.2(20060403:18507))
Next step to activate the rollback by issuing the install activate command:
6500-x#install activate disk0:/sys
To remove the ospf_fix tag:
install prune disk0:/sys ospf_fix
There are 3 Cisco-defined tags that are created by default:
- CISCO_BASE - This tag is defined as the base image with no patches or other tags. Using this tag with the install rollback command takes you back to the installed bsae image.
- CISCO_LATEST - This tag is defined as removing one level of install file. Using this tag with the install rollback command removes the set of files that were added with the last install file command entry. If the patch is in an active state, it will set the patch to a PendRoll state meaning that the changes will not take place until the install activate command is entered. If the patch as been installed but not activated, the install rollback command removes the installed patch.
- CISCO_LATEST_ACTIVATE - This tag is defined as removing one level of install activation. Using this tag with the install rollback command removes the set of files that were most recently activated by the install activate command. If multiple maintenance packs or patches werer installed with the install file command and then got activated simulatenously with a single install activate command, all files are marked to be rolled back.
Create Tag
1. To create a tag, execute the "install commit" command as seen below:
6500-x#install commit disk0:/sys ospf_fix
2. To verify what tags have been installed:
6500-x#show install tags running
Tags defined over software running on location s72033_rp - Slot 1 :
Tagname # of Files Date Committed
------------------------------- ---------- ------------------------
ospf_fix 2 19:31:48 UTC May 9 2006
Tags defined over software running on location s72033 - Slot 1 :
Tagname # of Files Date Committed
------------------------------- ---------- ------------------------
ospf_fix 1 19:31:48 UTC May 9 2006
Repackaging
The repackage feature will copy all necessary files to a single binary file which can be installed on another system. The "install repackage" command will be used.
6500-x#install repackage disk0:/sys disk0:/lab_repackage.bin
To verify, execute dir disk0:
6500-1#dir disk0:
Directory of disk0:/
1 -rwx 69213304 Apr 25 2006 20:08:28 +00:00 s72033-ipservicesk9-vz.sx4-demo
2 -rwx 636416 Apr 25 2006 20:10:44 +00:00 s72033-XMA0001.122-18.SXF4
3 -rwx 769024 Apr 25 2006 20:11:20 +00:00 s72033-XMA0002.122-18.SXF4
4 -rwx 1287168 Apr 25 2006 20:11:46 +00:00 s72033-XMA0003.122-18.SXF4
5 drwx 1 May 9 2006 18:08:48 +00:00 sys
81 -rwx 69963776 May 9 2006 19:44:08 +00:00 lab_repackage.bin
512065536 bytes total (278913024 bytes free)
Rollback
Execute "install rollback" to roll the system back:
6500-x#install rollback disk0:/sys ospf_fix
Verify the patch is in the "PendRoll" state:
6500-1#show install running
Software running on card installed at location s72033_rp - Slot 1 :
B/P C State Filename
--- - -------- --------
B * Active disk0:/sys/s72033_rp/base/DRACO2_MP
MP Maintenance Pack MA0001.122
P * Active disk0:/sys/s72033_rp/patch/patch-XAA2101-00-0-n.so
MP Maintenance Pack
P PendRoll disk0:/sys/s72033_rp/patch/patch-XAA2102-01-0-n.so
Software running on card installed at location s72033 - Slot 1 :
B/P C State Filename
--- - -------- --------
B * Active disk0:/sys/s72033/base/s72033-ipservicesk9-vm(12.2(20060403:18507))
Next step to activate the rollback by issuing the install activate command:
6500-x#install activate disk0:/sys
To remove the ospf_fix tag:
install prune disk0:/sys ospf_fix
Cat6K - Software Modularity
Software Modularity is an enhancement to the existing Cat6K IOS, which allows you apply patches to individual subsystem (Subsystem ISSU) and allows the change to be applied with no service disruption.
This example will show you how to enable the software modularity feature on IOS and apply maintenance packs.
You'll quickly identify the difference by doing a "show process cpu"
6500-1#show process cpu
CPU utilization for five seconds: 2%; one minute: 2%; five minutes: 2%
PID 5Sec 1Min 5Min Process
1 0.4% 0.5% 0.3% kernel
3 0.0% 0.0% 0.0% qdelogger
4 0.0% 0.0% 0.0% devc-pty
5 0.0% 0.0% 0.0% devc-mistral.proc
6 0.0% 0.0% 0.0% pipe
7 0.0% 0.0% 0.0% dumper.proc
4104 0.0% 0.0% 0.0% pcmcia_driver.proc
4105 0.0% 0.0% 0.0% bflash_driver.proc
12298 0.0% 0.0% 0.0% mqueue
12299 0.0% 0.0% 0.0% flashfs_hes.proc
12300 0.0% 0.0% 0.0% dfs_bootdisk.proc
You can also get more details on an individual process with "show process detailed iprouting.iosproc"
6500-x#show process detailed iprouting.iosproc
Job Id: 76
PID: 16427
Executable name: iprouting.iosproc
Executable Path: sbin/iprouting.iosproc
Instance ID: 1
Respawn: ON
Respawn count: 1
Respawn since last patch: 1
Max. spawns per minute: 30
Last started: Thu Apr 20 14:15:12 2006
Process state: Run
Feature name: iprouting
Core: SHAREDMEM MAINMEM
Max. core: 0
Level: 100
Mandatory: ON
Last restart userid:
Related Processes:
PID TID Stack pri state Blked HR:MM:SS:MSEC FLAGS NAME
16427 1 32K 10 Receive 1 0:00:00:0264 00000000 iprouting.iospro
16427 2 32K 10 Receive 1 0:00:00:0000 00000000 iprouting.iospro
16427 3 32K 10 Receive 1 0:00:00:0616 00000000 iprouting.iospro
16427 4 32K 11 Nanosleep 0:00:00:0000 00000000 iprouting.iospro
16427 5 32K 10 Receive 1 0:00:00:0068 00000000 iprouting.iospro
16427 6 32K 10 Receive 1 0:00:00:0000 00000000 iprouting.iospro
And "show process cpu detailed iprouting.iosproc"
6500-x#show proc cpu detailed iprouting.iosproc
CPU utilization for five seconds: 2%; one minute: 2%; five minutes: 2%
PID/TID 5Sec 1Min 5Min Process Prio STATE CPU
16427 0.0% 0.0% 0.0% iprouting.iosproc 1.236
1 0.0% 0.0% 0.0% 10 Receive 0.308
2 0.0% 0.0% 0.0% 10 Receive 0.000
3 0.0% 0.0% 0.0% 10 Receive 0.628
4 0.0% 0.0% 0.0% 11 Nanosleep 0.000
5 0.0% 0.0% 0.0% 10 Receive 0.068
6 0.0% 0.0% 0.0% 10 Receive 0.000
Process sbin/iprouting.iosproc, type IOS, PID = 16427
CPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0%
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
1 60 498 120 0.00% 0.00% 0.00% 0 Hot Service Task
2 228 2764 82 0.00% 0.00% 0.00% 0 Service Task
3 0 9 0 0.00% 0.00% 0.00% 0 Service Task
4 0 4 0 0.00% 0.00% 0.00% 0 Service Task
5 3 5 600 0.00% 0.00% 0.00% 0 Chunk Manager
6 0 579 0 0.00% 0.00% 0.00% 0 Load Meter
7 0 1 0 0.00% 0.00% 0.00% 0 Connection Mgr
8 31 569 54 0.00% 0.00% 0.00% 0 OSPF Hello
9 0 291 0 0.00% 0.00% 0.00% 0 Check heaps
10 0 1 0 0.00% 0.00% 0.00% 0 Socket Timers
11 72 538 133 0.00% 0.00% 0.00% 0 IP Background
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
12 0 111 0 0.00% 0.00% 0.00% 0 IP RIB Update
13 0 1 0 0.00% 0.00% 0.00% 0 Service Task
14 0 49 0 0.00% 0.00% 0.00% 0 Per-minute Jobs
15 76 496 153 0.00% 0.00% 0.00% 0 Hot Service Task
16 20 2928 6 0.00% 0.00% 0.00% 0 OSPF Router 1
1. In order to run the system in "installed" mode, the original binary file is expanded into a treed sub-dir file structure that allows for patching.
install file disk0:/s72033-ipservicesk9-vz.sxf4-demo disk0:/sys
2. Verfiy the creation of Directory Structure
dir disk0:/sys
3. Bind the system to the file system directory
install bind disk0:/sys
You'll see something like this after apply the "install bind" command:
6500-x#show running-config | include boot
boot system disk0:/sys/s72033/base/s72033-ipservicesk9-vm
To further verify, do a "show bootvar"
6500-x#show bootvar
BOOT variable = disk0:/sys/s72033/base/s72033-ipservicesk9-vm,12;
CONFIG_FILE variable does not exist
BOOTLDR variable =
Configuration register is 0x2102
4. Reload your system
Then verify your system after reload with the "show install running" command:
6500-1#show install running
Software running on card installed at location s72033_rp - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033_rp/base/DRACO2_MP
Software running on card installed at location s72033 - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033/base/s72033-ipservicesk9-vm(12.2(20060403:18507))
LEGEND:
-------:
B/P/MP - (B)ase image, (P)atch, or (M)aintenance (P)ack
'C' - (C)ommitted
Pruned - This file has been pruned from the system
Active - This file is active in the system
PendInst - This file is set to be made available to run on the
system after next activation.
5. Install maintenance pack
6500-x# install file disk0:/s72033-XMA0001.122-18.SXF4 disk0:/sys
6. Verify the maintenance pack installation
6500-x#show install running
Software running on card installed at location s72033 - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033/base/s72033-ipservicesk9-vm(12.2(20060403:185507))
Software running on card installed at location s72033_rp - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033_rp/base/DRACO2_MP
MP Maintenance Pack MA0001.122
P PendInst disk0:/sys/s72033_rp/patch/patch-XAA2101-00-0-n.so
7. Activate the maintenance pack
6500-x#install activate disk0:/sys
8. Verify activation of maintenance pack
6500-x#show install running
Software running on card installed at location s72033_rp - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033_rp/base/DRACO2_MP
MP Maintenance Pack MA0001.122
P Active disk0:/sys/s72033_rp/patch/patch-XAA2101-00-0-n.so
Software running on card installed at location s72033 - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033/base/s72033-ipservicesk9-vm(12.2(20060403:18507))
This example will show you how to enable the software modularity feature on IOS and apply maintenance packs.
You'll quickly identify the difference by doing a "show process cpu"
6500-1#show process cpu
CPU utilization for five seconds: 2%; one minute: 2%; five minutes: 2%
PID 5Sec 1Min 5Min Process
1 0.4% 0.5% 0.3% kernel
3 0.0% 0.0% 0.0% qdelogger
4 0.0% 0.0% 0.0% devc-pty
5 0.0% 0.0% 0.0% devc-mistral.proc
6 0.0% 0.0% 0.0% pipe
7 0.0% 0.0% 0.0% dumper.proc
4104 0.0% 0.0% 0.0% pcmcia_driver.proc
4105 0.0% 0.0% 0.0% bflash_driver.proc
12298 0.0% 0.0% 0.0% mqueue
12299 0.0% 0.0% 0.0% flashfs_hes.proc
12300 0.0% 0.0% 0.0% dfs_bootdisk.proc
You can also get more details on an individual process with "show process detailed iprouting.iosproc"
6500-x#show process detailed iprouting.iosproc
Job Id: 76
PID: 16427
Executable name: iprouting.iosproc
Executable Path: sbin/iprouting.iosproc
Instance ID: 1
Respawn: ON
Respawn count: 1
Respawn since last patch: 1
Max. spawns per minute: 30
Last started: Thu Apr 20 14:15:12 2006
Process state: Run
Feature name: iprouting
Core: SHAREDMEM MAINMEM
Max. core: 0
Level: 100
Mandatory: ON
Last restart userid:
Related Processes:
PID TID Stack pri state Blked HR:MM:SS:MSEC FLAGS NAME
16427 1 32K 10 Receive 1 0:00:00:0264 00000000 iprouting.iospro
16427 2 32K 10 Receive 1 0:00:00:0000 00000000 iprouting.iospro
16427 3 32K 10 Receive 1 0:00:00:0616 00000000 iprouting.iospro
16427 4 32K 11 Nanosleep 0:00:00:0000 00000000 iprouting.iospro
16427 5 32K 10 Receive 1 0:00:00:0068 00000000 iprouting.iospro
16427 6 32K 10 Receive 1 0:00:00:0000 00000000 iprouting.iospro
And "show process cpu detailed iprouting.iosproc"
6500-x#show proc cpu detailed iprouting.iosproc
CPU utilization for five seconds: 2%; one minute: 2%; five minutes: 2%
PID/TID 5Sec 1Min 5Min Process Prio STATE CPU
16427 0.0% 0.0% 0.0% iprouting.iosproc 1.236
1 0.0% 0.0% 0.0% 10 Receive 0.308
2 0.0% 0.0% 0.0% 10 Receive 0.000
3 0.0% 0.0% 0.0% 10 Receive 0.628
4 0.0% 0.0% 0.0% 11 Nanosleep 0.000
5 0.0% 0.0% 0.0% 10 Receive 0.068
6 0.0% 0.0% 0.0% 10 Receive 0.000
Process sbin/iprouting.iosproc, type IOS, PID = 16427
CPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 0%
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
1 60 498 120 0.00% 0.00% 0.00% 0 Hot Service Task
2 228 2764 82 0.00% 0.00% 0.00% 0 Service Task
3 0 9 0 0.00% 0.00% 0.00% 0 Service Task
4 0 4 0 0.00% 0.00% 0.00% 0 Service Task
5 3 5 600 0.00% 0.00% 0.00% 0 Chunk Manager
6 0 579 0 0.00% 0.00% 0.00% 0 Load Meter
7 0 1 0 0.00% 0.00% 0.00% 0 Connection Mgr
8 31 569 54 0.00% 0.00% 0.00% 0 OSPF Hello
9 0 291 0 0.00% 0.00% 0.00% 0 Check heaps
10 0 1 0 0.00% 0.00% 0.00% 0 Socket Timers
11 72 538 133 0.00% 0.00% 0.00% 0 IP Background
Task Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Task Name
12 0 111 0 0.00% 0.00% 0.00% 0 IP RIB Update
13 0 1 0 0.00% 0.00% 0.00% 0 Service Task
14 0 49 0 0.00% 0.00% 0.00% 0 Per-minute Jobs
15 76 496 153 0.00% 0.00% 0.00% 0 Hot Service Task
16 20 2928 6 0.00% 0.00% 0.00% 0 OSPF Router 1
1. In order to run the system in "installed" mode, the original binary file is expanded into a treed sub-dir file structure that allows for patching.
install file disk0:/s72033-ipservicesk9-vz.sxf4-demo disk0:/sys
2. Verfiy the creation of Directory Structure
dir disk0:/sys
3. Bind the system to the file system directory
install bind disk0:/sys
You'll see something like this after apply the "install bind" command:
6500-x#show running-config | include boot
boot system disk0:/sys/s72033/base/s72033-ipservicesk9-vm
To further verify, do a "show bootvar"
6500-x#show bootvar
BOOT variable = disk0:/sys/s72033/base/s72033-ipservicesk9-vm,12;
CONFIG_FILE variable does not exist
BOOTLDR variable =
Configuration register is 0x2102
4. Reload your system
Then verify your system after reload with the "show install running" command:
6500-1#show install running
Software running on card installed at location s72033_rp - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033_rp/base/DRACO2_MP
Software running on card installed at location s72033 - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033/base/s72033-ipservicesk9-vm(12.2(20060403:18507))
LEGEND:
-------:
B/P/MP - (B)ase image, (P)atch, or (M)aintenance (P)ack
'C' - (C)ommitted
Pruned - This file has been pruned from the system
Active - This file is active in the system
PendInst - This file is set to be made available to run on the
system after next activation.
5. Install maintenance pack
6500-x# install file disk0:/s72033-XMA0001.122-18.SXF4 disk0:/sys
6. Verify the maintenance pack installation
6500-x#show install running
Software running on card installed at location s72033 - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033/base/s72033-ipservicesk9-vm(12.2(20060403:185507))
Software running on card installed at location s72033_rp - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033_rp/base/DRACO2_MP
MP Maintenance Pack MA0001.122
P PendInst disk0:/sys/s72033_rp/patch/patch-XAA2101-00-0-n.so
7. Activate the maintenance pack
6500-x#install activate disk0:/sys
8. Verify activation of maintenance pack
6500-x#show install running
Software running on card installed at location s72033_rp - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033_rp/base/DRACO2_MP
MP Maintenance Pack MA0001.122
P Active disk0:/sys/s72033_rp/patch/patch-XAA2101-00-0-n.so
Software running on card installed at location s72033 - Slot 1 :
B/P C State Filename
--- - -------- --------
B Active disk0:/sys/s72033/base/s72033-ipservicesk9-vm(12.2(20060403:18507))
EEM - Server Failure Detection
This example combine IOS IP SLA + EOT + EEM
1. Setup Email Environmental variables. Please refer to the previous EEM examples. On R4, configure an IP SLA ICMP Echo operation that will ping 3.3.3.3 with a frequency of 3 seconds and timeout of 500 msecs.
ip sla 10
icmp-echo 3.3.3.3
timeout 500
frequency 3
ip sla schedule 10 life forever start-time now
2. Verify that the SLA is being met.
R4#sh ip sla stat
Round Trip Time (RTT) for Index 10
Latest RTT: 1 milliseconds
Latest operation start time: *01:32:54.063 UTC Sat Sep 15 2007
Latest operation return code: OK
Number of successes: 4
Number of failures: 0
Operation time to live: Forever
3. Next, track the IP SLA ICMP-ECHO reachability state using Enhance Object Tracking (EOT). State is defined to be “down” if unreachable for more than 10 seconds. State defined to be “up” if reachable for more than 20 seconds.
!
track 10 rtr 10 reachability
delay down 10 up 20
!
4. Verify EOT reachability is in an “Up” state.
R4#sh track 10
Track 10
Response Time Reporter 10 reachability
Reachability is Up
1 change, last change 00:00:10
Delay up 20 secs, down 10 secs
Latest operation return code: OK
Latest RTT (millisecs) 1
5. Configure the following EEM applet named email_server_unreachable:
event manager applet email_server_unreachable
event track 10 state down
action 1.0 syslog msg "Ping has failed, server unreachable!"
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:server_unreachable"
action 1.3 cli command "show clock | append server_unreachable"
action 1.4 cli command "show ip route | append server_unreachable"
action 1.5 cli command "more flash:server_unreachable"
action 1.6 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Server Unreachable: ICMPEchos
Failed" body "$_cli_result"
action 1.7 syslog msg "Server unreachable alert has been sent to email server!"
6. Verify that the EEM applet has been registered and the required environment variables have been set properly:
R4#sh event manager policy registered
No. Class Type Event Type Trap Time Registered Name
# applet system track Off Sat Sep 15 01:50:52 2007 email_server_unreachable
track 10 state down
action 1.0 syslog msg "Ping has failed, server unreachable!"
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:server_unreachable"
action 1.3 cli command "show clock | append server_unreachable"
action 1.4 cli command "show ip route | append server_unreachable"
action 1.5 cli command "more flash:server_unreachable"
action 1.6 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Server Unreachable: ICMP-Echos
Failed" body "$_cli_result"
action 1.7 syslog msg "Server unreachable alert has been sent to email server!"
R4#sh event manager environment
No. Name Value
1 _email_server 50.50.50.1
2 _email_from router-abc@customer.com
3 _email_to attach@cisco.com
7. Shutdown R3’s Loopback0 interface to trigger the EEM applet.
R3#config t
Enter configuration commands, one per line. End with CNTL/Z.
R3(config)#int loop0
R3(config-if)#shut
8. Go to R4 and issue ‘show track 10’ several times to watch the state of the 3.3.3.3 go DOWN which will cause the EEM applet to trigger.
R4#sh track 10
Track 10
Response Time Reporter 10 reachability
Reachability is Up, delayed Down (1 sec remaining)
1 change, last change 00:22:23
Delay up 20 secs, down 10 secs
Latest operation return code: OK
Latest RTT (millisecs) 1
Tracked by:
EEM applet email_server_unreachable
R4#sh track 10
Track 10
Response Time Reporter 10 reachability
Reachability is Down
2 changes, last change 00:00:00
Delay up 20 secs, down 10 secs
Latest operation return code: Timeout
Tracked by:
EEM applet email_server_unreachable
1. Setup Email Environmental variables. Please refer to the previous EEM examples. On R4, configure an IP SLA ICMP Echo operation that will ping 3.3.3.3 with a frequency of 3 seconds and timeout of 500 msecs.
ip sla 10
icmp-echo 3.3.3.3
timeout 500
frequency 3
ip sla schedule 10 life forever start-time now
2. Verify that the SLA is being met.
R4#sh ip sla stat
Round Trip Time (RTT) for Index 10
Latest RTT: 1 milliseconds
Latest operation start time: *01:32:54.063 UTC Sat Sep 15 2007
Latest operation return code: OK
Number of successes: 4
Number of failures: 0
Operation time to live: Forever
3. Next, track the IP SLA ICMP-ECHO reachability state using Enhance Object Tracking (EOT). State is defined to be “down” if unreachable for more than 10 seconds. State defined to be “up” if reachable for more than 20 seconds.
!
track 10 rtr 10 reachability
delay down 10 up 20
!
4. Verify EOT reachability is in an “Up” state.
R4#sh track 10
Track 10
Response Time Reporter 10 reachability
Reachability is Up
1 change, last change 00:00:10
Delay up 20 secs, down 10 secs
Latest operation return code: OK
Latest RTT (millisecs) 1
5. Configure the following EEM applet named email_server_unreachable:
event manager applet email_server_unreachable
event track 10 state down
action 1.0 syslog msg "Ping has failed, server unreachable!"
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:server_unreachable"
action 1.3 cli command "show clock | append server_unreachable"
action 1.4 cli command "show ip route | append server_unreachable"
action 1.5 cli command "more flash:server_unreachable"
action 1.6 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Server Unreachable: ICMPEchos
Failed" body "$_cli_result"
action 1.7 syslog msg "Server unreachable alert has been sent to email server!"
6. Verify that the EEM applet has been registered and the required environment variables have been set properly:
R4#sh event manager policy registered
No. Class Type Event Type Trap Time Registered Name
# applet system track Off Sat Sep 15 01:50:52 2007 email_server_unreachable
track 10 state down
action 1.0 syslog msg "Ping has failed, server unreachable!"
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:server_unreachable"
action 1.3 cli command "show clock | append server_unreachable"
action 1.4 cli command "show ip route | append server_unreachable"
action 1.5 cli command "more flash:server_unreachable"
action 1.6 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Server Unreachable: ICMP-Echos
Failed" body "$_cli_result"
action 1.7 syslog msg "Server unreachable alert has been sent to email server!"
R4#sh event manager environment
No. Name Value
1 _email_server 50.50.50.1
2 _email_from router-abc@customer.com
3 _email_to attach@cisco.com
7. Shutdown R3’s Loopback0 interface to trigger the EEM applet.
R3#config t
Enter configuration commands, one per line. End with CNTL/Z.
R3(config)#int loop0
R3(config-if)#shut
8. Go to R4 and issue ‘show track 10’ several times to watch the state of the 3.3.3.3 go DOWN which will cause the EEM applet to trigger.
R4#sh track 10
Track 10
Response Time Reporter 10 reachability
Reachability is Up, delayed Down (1 sec remaining)
1 change, last change 00:22:23
Delay up 20 secs, down 10 secs
Latest operation return code: OK
Latest RTT (millisecs) 1
Tracked by:
EEM applet email_server_unreachable
R4#sh track 10
Track 10
Response Time Reporter 10 reachability
Reachability is Down
2 changes, last change 00:00:00
Delay up 20 secs, down 10 secs
Latest operation return code: Timeout
Tracked by:
EEM applet email_server_unreachable
EEM - Layer 3 Path Failure Detection
This example will track the availability of a route using Embedded Object Tracking (EOT) with EEM applet to email an alert as soon as the route is withdrawn from the routing table.
1. Configure your router to tracks 1.1.1.1/32 using the Cisco IOS Embedded Object Tracking (EOT) feature:
track 400 ip route 1.1.1.1/32 reachability
delay down 10 up 10
2. Verify reachability to 1.1.1.1/32 is UP
R4#sh track
Track 400
IP route 1.1.1.1 255.255.255.255 reachability
Reachability is Up (EIGRP)
1 change, last change 00:02:15
Delay up 10 secs, down 10 secs
First-hop interface is FastEthernet0/0
3. Configure the appropriate email environment variables. Refer to other EEM examples.
4. Configured the following environment variable to define the ip prefix wished to be tracked.
R4(config)#event manager environment iproute 1.1.1.1/32
5. On R4, configure the following EEM applet below named “email_track_iproute” so an alarm (in the form of a syslog and email) will be sent when the prefix 1.1.1.1/32 is withdrawn from R4’s routing table:
event manager applet email_track_iproute
event track 400 state down
action 1.0 syslog msg "Prefix to remote site [$iproute] has been withdrawn!"
action 1.1 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Layer 3 Path Failure: Prefix to Remote Site [$iproute] is DOWN" body ""
action 1.2 syslog msg "Layer 3 Path Failure alert has been sent to email server!"
6. Verify that the EEM applet has been registered and the required environment variables have been set properly:
R4#sh event manager policy registered
No. Class Type Event Type Trap Time Registered Name
1 applet system track Off Fri Sep 14 21:16:43 2007 email_track_iproute
track 400 state down
action 1.0 syslog msg "Prefix to remote site [$iproute] has been withdrawn!"
action 1.1 mail server "$mailserver" to "$mailto" from "$mailfrom" subject "Layer 3 Path Failure: Prefix to Remote Site [$iproute] is DOWN"
action 1.2 syslog msg "Layer 3 Path Failure alert has been sent to email server!"
R4#sh event manager environment
No. Name Value
1 _email_server 50.50.50.1
2 _email_from router-abc@customer.com
3 _email_to attach@cisco.com
4 iproute 1.1.1.1/32
7. Shutdown R1’s Loopback0 interface to trigger the EEM applet on R4 .
R1#config t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#int loop0
R1(config-if)#shut
8. Go to R4 and issue ‘show track’ several times to watch the state of the 1.1.1.1/32 go DOWN which will cause the EEM applet to trigger.
R4#sh track
Track 400
IP route 1.1.1.1 255.255.255.255 reachability
Reachability is Up (EIGRP), delayed Down (1 sec remaining) (no route)
3 changes, last change 00:00:29
Delay up 10 secs, down 10 secs
First-hop interface is GigabitEthernet0/0 (was unknown)
Tracked by:
EEM applet email_track_iproute
R4#sh track
Track 400
IP route 1.1.1.1 255.255.255.255 reachability
Reachability is Down (no route)
4 changes, last change 00:00:00
Delay up 10 secs, down 10 secs
First-hop interface is unknown
Tracked by:
EEM applet email_track_iproute
1. Configure your router to tracks 1.1.1.1/32 using the Cisco IOS Embedded Object Tracking (EOT) feature:
track 400 ip route 1.1.1.1/32 reachability
delay down 10 up 10
2. Verify reachability to 1.1.1.1/32 is UP
R4#sh track
Track 400
IP route 1.1.1.1 255.255.255.255 reachability
Reachability is Up (EIGRP)
1 change, last change 00:02:15
Delay up 10 secs, down 10 secs
First-hop interface is FastEthernet0/0
3. Configure the appropriate email environment variables. Refer to other EEM examples.
4. Configured the following environment variable to define the ip prefix wished to be tracked.
R4(config)#event manager environment iproute 1.1.1.1/32
5. On R4, configure the following EEM applet below named “email_track_iproute” so an alarm (in the form of a syslog and email) will be sent when the prefix 1.1.1.1/32 is withdrawn from R4’s routing table:
event manager applet email_track_iproute
event track 400 state down
action 1.0 syslog msg "Prefix to remote site [$iproute] has been withdrawn!"
action 1.1 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Layer 3 Path Failure: Prefix to Remote Site [$iproute] is DOWN" body ""
action 1.2 syslog msg "Layer 3 Path Failure alert has been sent to email server!"
6. Verify that the EEM applet has been registered and the required environment variables have been set properly:
R4#sh event manager policy registered
No. Class Type Event Type Trap Time Registered Name
1 applet system track Off Fri Sep 14 21:16:43 2007 email_track_iproute
track 400 state down
action 1.0 syslog msg "Prefix to remote site [$iproute] has been withdrawn!"
action 1.1 mail server "$mailserver" to "$mailto" from "$mailfrom" subject "Layer 3 Path Failure: Prefix to Remote Site [$iproute] is DOWN"
action 1.2 syslog msg "Layer 3 Path Failure alert has been sent to email server!"
R4#sh event manager environment
No. Name Value
1 _email_server 50.50.50.1
2 _email_from router-abc@customer.com
3 _email_to attach@cisco.com
4 iproute 1.1.1.1/32
7. Shutdown R1’s Loopback0 interface to trigger the EEM applet on R4 .
R1#config t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#int loop0
R1(config-if)#shut
8. Go to R4 and issue ‘show track’ several times to watch the state of the 1.1.1.1/32 go DOWN which will cause the EEM applet to trigger.
R4#sh track
Track 400
IP route 1.1.1.1 255.255.255.255 reachability
Reachability is Up (EIGRP), delayed Down (1 sec remaining) (no route)
3 changes, last change 00:00:29
Delay up 10 secs, down 10 secs
First-hop interface is GigabitEthernet0/0 (was unknown)
Tracked by:
EEM applet email_track_iproute
R4#sh track
Track 400
IP route 1.1.1.1 255.255.255.255 reachability
Reachability is Down (no route)
4 changes, last change 00:00:00
Delay up 10 secs, down 10 secs
First-hop interface is unknown
Tracked by:
EEM applet email_track_iproute
EEM - Watchdog timer
This EEM example applet will trigger every minute (60 seconds):
EEM Applet:
event manager applet goober
event timer watchdog time 60
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:show_tech"
action 1.3 cli command "show clock | append flash:show_tech"
action 1.4 cli command "show version | append flash:show_tech"
action 1.5 cli command "show run | append flash:show_tech"
action 1.6 cli command "more flash:show_tech"
action 1.7 syslog msg "Sending goober output..."
action 1.8 mail server $_email_server to $_email_to from $_email_from subject "Goober Output" body "$_cli_result"
action 1.9 syslog msg "Goober output sent!"
EEM Applet:
event manager applet goober
event timer watchdog time 60
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:show_tech"
action 1.3 cli command "show clock | append flash:show_tech"
action 1.4 cli command "show version | append flash:show_tech"
action 1.5 cli command "show run | append flash:show_tech"
action 1.6 cli command "more flash:show_tech"
action 1.7 syslog msg "Sending goober output..."
action 1.8 mail server $_email_server to $_email_to from $_email_from subject "Goober Output" body "$_cli_result"
action 1.9 syslog msg "Goober output sent!"
EEM - Syslog Pattern Matching
The following example EEM applet trigger when the router generates the following configuration change syslog message:
%SYS-5-CONFIG_I: Configured from console by cisco on console
EEM Applet:
event manager applet foobar
event syslog pattern “.*%SYS-5-CONFIG_I.*”
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:show_tech"
action 1.3 cli command "show ip route | append flash:show_tech"
action 1.4 cli command "show ip interface brief | append flash:show_tech"
action 1.5 cli command "more flash:show_tech"
action 1.6 syslog msg "Sending foobar output..."
action 1.7 mail server $_email_server to $_email_to from $_email_from subject "Foobar Output" body
"$_cli_result"
action 1.8 syslog msg "Foobar output sent!"
Verification:
router#config t
Enter configuration commands, one per line. End with CNTL/Z.
Hit cntl-C to break out
*Sep 13 06:17:13.146: %SYS-5-CONFIG_I: Configured from console by cisco on console
*Sep 13 06:17:14.018: %HA_EM-6-LOG: sendtech: Sending foobar output...
*Sep 13 06:17:15.810: %HA_EM-6-LOG: sendtech: Foobar output sent!
%SYS-5-CONFIG_I: Configured from console by cisco on console
EEM Applet:
event manager applet foobar
event syslog pattern “.*%SYS-5-CONFIG_I.*”
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:show_tech"
action 1.3 cli command "show ip route | append flash:show_tech"
action 1.4 cli command "show ip interface brief | append flash:show_tech"
action 1.5 cli command "more flash:show_tech"
action 1.6 syslog msg "Sending foobar output..."
action 1.7 mail server $_email_server to $_email_to from $_email_from subject "Foobar Output" body
"$_cli_result"
action 1.8 syslog msg "Foobar output sent!"
Verification:
router#config t
Enter configuration commands, one per line. End with CNTL/Z.
Hit cntl-C to break out
*Sep 13 06:17:13.146: %SYS-5-CONFIG_I: Configured from console by cisco on console
*Sep 13 06:17:14.018: %HA_EM-6-LOG: sendtech: Sending foobar output...
*Sep 13 06:17:15.810: %HA_EM-6-LOG: sendtech: Foobar output sent!
EEM - Email the CLI output from router
This example shows how to quickly send the logs and configuration to TAC easily with EEM.
1. Configure the following required email related EEM environment variables:
event manager environment _email_server 1.2.3.4
event manager environment _email_from panda@pandaeatsbamboo.com
event manager environment _email_to attach@cisco.com
2. Configure the following EEM Applet named “sendtech”:
event manager applet sendtech
event none
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:show_tech"
action 1.3 cli command "show tech | append flash:show_tech"
action 1.4 cli command "show ip route | append flash:show_tech"
action 1.5 cli command "show ip interface brief | append flash:show_tech"
action 1.6 cli command "more flash:show_tech"
action 1.7 syslog msg "Sending show tech..."
action 1.8 mail server $_email_server to $_email_to from $_email_from subject " Show Tech Output (SR99999) " body "$_cli_result"
action 1.9 syslog msg "Show tech sent!"
Explanation of EEM Applet:
event manager applet sendtech ! registers applet with the name ‘sendtech’
event none ! specifies the event which will trigger this applet – in this case, the applet will be triggered manually
3. Verify that the EEM applet has been registered and that the environment variables have been set correctly:
R3#show event manager policy registered
No. Class Type Event Type Trap Time Registered Name
1 applet user none Off Sat Mar 16 19:39:39 2002 sendtech
policyname {sendtech} sync {yes}
maxrun 20.000
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:show_tech"
action 1.3 cli command "show tech | append flash:show_tech"
action 1.4 cli command "show ip route | append flash:show_tech"
action 1.5 cli command "show ip interface brief | append flash:show_tech"
action 1.6 cli command "more flash:show_tech"
action 1.7 syslog msg "Sending show tech.."
action 1.8 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Show Tech Output (SR12345)" body "$_cli_result"
action 1.9 syslog msg "Show tech sent!"
R3#show event manager env all
No. Name Value
1 _email_server 1.2.3.4
2 _email_from panda@pandaeatsbamboo.com
3 _email_to attach@cisco.com
4. Manually trigger the script by issuing the command “event manager run sendtech”:
R3#event manager run sendtech
*May 19 20:16:46.440: %HA_EM-6-LOG: sendtech: Sending show tech...
*May 19 20:16:46.801: %HA_EM-6-LOG: sendtech: Show tech sent!
1. Configure the following required email related EEM environment variables:
event manager environment _email_server 1.2.3.4
event manager environment _email_from panda@pandaeatsbamboo.com
event manager environment _email_to attach@cisco.com
2. Configure the following EEM Applet named “sendtech”:
event manager applet sendtech
event none
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:show_tech"
action 1.3 cli command "show tech | append flash:show_tech"
action 1.4 cli command "show ip route | append flash:show_tech"
action 1.5 cli command "show ip interface brief | append flash:show_tech"
action 1.6 cli command "more flash:show_tech"
action 1.7 syslog msg "Sending show tech..."
action 1.8 mail server $_email_server to $_email_to from $_email_from subject " Show Tech Output (SR99999) " body "$_cli_result"
action 1.9 syslog msg "Show tech sent!"
Explanation of EEM Applet:
event manager applet sendtech ! registers applet with the name ‘sendtech’
event none ! specifies the event which will trigger this applet – in this case, the applet will be triggered manually
3. Verify that the EEM applet has been registered and that the environment variables have been set correctly:
R3#show event manager policy registered
No. Class Type Event Type Trap Time Registered Name
1 applet user none Off Sat Mar 16 19:39:39 2002 sendtech
policyname {sendtech} sync {yes}
maxrun 20.000
action 1.1 cli command "enable"
action 1.2 cli command "del /force flash:show_tech"
action 1.3 cli command "show tech | append flash:show_tech"
action 1.4 cli command "show ip route | append flash:show_tech"
action 1.5 cli command "show ip interface brief | append flash:show_tech"
action 1.6 cli command "more flash:show_tech"
action 1.7 syslog msg "Sending show tech.."
action 1.8 mail server "$_email_server" to "$_email_to" from "$_email_from" subject "Show Tech Output (SR12345)" body "$_cli_result"
action 1.9 syslog msg "Show tech sent!"
R3#show event manager env all
No. Name Value
1 _email_server 1.2.3.4
2 _email_from panda@pandaeatsbamboo.com
3 _email_to attach@cisco.com
4. Manually trigger the script by issuing the command “event manager run sendtech”:
R3#event manager run sendtech
*May 19 20:16:46.440: %HA_EM-6-LOG: sendtech: Sending show tech...
*May 19 20:16:46.801: %HA_EM-6-LOG: sendtech: Show tech sent!
Mobile Telepresence on Cisco NERV
Cisco has installed mobile TelePresence on the Network Emergency Response Vehicle.
The Network Emergency Response Vehicle (NERV). Basically, a mobile communications vehicle that can act as a command center for your on-the-ground disaster management, as well as a central processing center for all the communications going on for that effort. Through Cisco's IPICS technology, which allows disparate radio systems to communicate with each other via IP translation, police, who are on one radio system, can talk with fire professionals who are on another radio system, who can talk with the National Guard, who are on another radio system. The NERV also has TelePresence, video surveillance, Wi-Fi, satellite communications, and IP telephony on-board.
In this short video, Bob Browning, Senior Manager of Tactical Operations Support at Cisco, gives us a tour of the NERV's technology and capabilities. This vehicle just returned from the Harris Fire and is exactly why interoperable communications systems are essential to successful disaster response and recovery.
Thursday, April 3, 2008
A robot for your living room
Toshiba's prototype robot can control devices in your living room. The robot, called ApriPoco, learns from users and then can act on their command.
Subscribe to:
Posts (Atom)