Warning: session_start(): Cannot send session cookie - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/wp-file-upload/wordpress_file_upload.php on line 2

Warning: session_start(): Cannot send session cache limiter - headers already sent (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/wp-file-upload/wordpress_file_upload.php on line 2

Warning: Cannot modify header information - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/read-offline/lib/phpMobi/MOBIClass/MOBI.php on line 179

Warning: Cannot modify header information - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/read-offline/lib/phpMobi/MOBIClass/MOBI.php on line 180

Warning: Cannot modify header information - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/read-offline/lib/phpMobi/MOBIClass/MOBI.php on line 181

Warning: Cannot modify header information - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/read-offline/lib/phpMobi/MOBIClass/MOBI.php on line 182

Warning: Cannot modify header information - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/read-offline/lib/phpMobi/MOBIClass/MOBI.php on line 183

Warning: Cannot modify header information - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/read-offline/lib/phpMobi/MOBIClass/MOBI.php on line 184

Warning: Cannot modify header information - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/read-offline/lib/phpMobi/MOBIClass/MOBI.php on line 185

Warning: Cannot modify header information - headers already sent by (output started at /home/circui15/public_html/packetpros.com/index.php:4) in /home/circui15/public_html/packetpros.com/wp-content/plugins/read-offline/lib/phpMobi/MOBIClass/MOBI.php on line 186
Cisco Call Home`Є`ЄBOOKMOBI_`x  MOBI" @EXTHdCollini!Network Management ,Routeg

Call me paranoid but I do not like anything automatically sending data somewhere. In all of my templates I disable/remove Cisco's Call Home. The other day I stumbled upon a post on CSC (Cisco Support …

j'Wed, 10 Jun 2015 20:57:06 +0000p$http://packetpros.com/?p=438ePacketprosf Copyright packetpros.comCisco Call Home

Call me paranoid but I do not like anything automatically sending data somewhere. In all of my templates I disable/remove Cisco’s Call Home. The other day I stumbled upon a post on CSC (Cisco Support Community) where the poster showed other options for call home. I was intrigued, mainly because not all of my customers automatically backup their configs. After some tinkering I was able to get the router to send me the config and inventory on a weekly basis.

First we enable the call home service

service call-home

Now we can configure our parameters.

call-home
contact-email-addr archive-config@packetpros.com
mail-server 192.168.0.69 priority 1
customer-id "222876876t9"
sender from RT1@customer.com
sender reply-to alerts@customer.com
source-ip-address "192.168.251.7"
 profile "EMAIL-ENGINEER"
  destination preferred-msg-format long-text
  destination address email archive-config@packetpros.com 
  subscribe-to-alert-group configuration periodic monthly 1 6:00

contact-email-addr is who we want to receive the email
mail-server is the mail server that will relay this email (you will have to permit the router IP in your relay settings on the email server)
customer-id is the same as the Bill-To ID in Cisco’s system. You can see the Bill-To ID in any TAC case
source-ip-address is the source IP on the router which will connect to the email server.
Under profile, the preferred-msg-format has three options; short, which basically has no information, long which has the full config and inventory, and xml which is the same as long but with some xml tags.
subscribe-to-alert-group is what information you want sent (in this case configuration) and when (the 1st of each month at 0600).

There are a lot of cool other things you can do like posting to HTTP, sending statistics, etc. You can setup a secure gateway to Cisco and they will also hold all this information for you in a neat little portal. A ton of information on call home can be found at https://supportforums.cisco.com/community/4816/smart-call-home

I find this very useful as the device sends me the config once a week. I have a rule in Outlook that puts the config in their customer folder. That’s it, I no longer have to worry about finding the latest config when a router dies.

 

 

FLIS00 00 00 0800 4100 0000 00 00 00ff ff ff ff00 0100 0300 00 00 0300 00 00 01ff ff ff ffFCIS00 00 00 1400 00 00 1000 00 00 0100 00 00 0000 00 0a a500 00 00 0000 00 00 2000 00 00 0800 0100 0100 00 00 003918400778