Show ip dhcp pool

shows you the leased DHCP IP addresses.
2811#sh ip dhcp pool

Pool sdm-pool1 :
Utilization mark (high/low) : 100 / 0
Subnet size (first/next) : 0 / 0
Total addresses : 254
Leased addresses : 54
Pending event : none
1 subnet is currently in the pool :
Current index IP address range Leased addresses
10.1.1.163 10.1.1.1 - 10.1.1.254 54
2811#

Ephone-dn-templates

ephone-dn-template

To enter ephone-dn-template configuration mode and create an ephone-dn template containing a standard set of ephone-dn features, use the ephone-dn-template command in global configuration mode. To delete an ephone-dn template, use the no form of this command.

ephone-dn-template template-tag

no ephone-dn-template template-tag

Syntax Description

template-tag

Identifier for this ephone-dn template. Range is from 1 to 15.

Command Default

No ephone-dn template is created.

Command Modes

Global configuration (config)

Command History

Cisco IOS Release	Cisco Product	Modification
12.4(4)XC	Cisco Unified CME 4.0	This command was introduced.
12.4(9)T	Cisco Unified CME 4.0	This command was integrated into Cisco IOS Release 12.4(9)T.

Usage Guidelines

Use this command to create an ephone-dn template. An ephone-dn template contains a set of ephone-dn attributes that you can easily apply to one or more ephone-dns.

If you use an ephone-dn template to apply a command to an ephone-dn and you also use the same command in ephone-dn configuration mode for the same ephone-dn, the value that you set in ephone-dn configuration mode has priority.

Type? in ephone-dn-template configuration mode to see the commands that are available in this mode. The following example shows CLI help for ephone-dn-template configuration mode:

Router(config-ephone-dn-template)# ?

Ephone Dn template configuration commands:

  call-forward         Define E.164 telephone number for call forwarding

  call-waiting         Config call-waiting option

  caller-id            Configure port caller id parameters

  corlist              Class of Restriction on dial-peer for this dn

  default              Set a command to its defaults

  description          dn desc, for DN Qualified Display Name

  exit                 Exit from ephone-dn-template configuration mode

  hold-alert           Set Call On-Hold timeout alert parameters

  huntstop             Stop hunting on Dial-Peers

  mwi                  set message waiting indicator options (mwi)

  no                   Negate a command or set its defaults

  pickup-group         set the call pickup group number for the DN

  translate            Translation rule

  translation-profile  Translation profile

After creating an ephone-dn template, apply the template to one or more ephone-dns using the ephone-dn-template command in ephone-dn configuration mode. Even though you can define up to 15 different ephone templates, you cannot apply more than one template to a particular ephone-dn.

If you try to apply a second ephone-dn template to an ephone-dn that already has a template applied to it, the second template will overwrite the first ephone-dn template configuration after you use the restart command to reboot the phone.

To view your ephone-dn-template configurations, use the show telephony-service ephone-dn-template command. To see which ephone-dns have templates applied to them, use the show running-config command.

Examples

The following example creates ephone-dn template 3, which sets call forwarding on busy and no answer to forward calls to extension 4000 and sets the pickup group to 4. Ephone-dn template 3 is then applied to ephone-dn 23 and ephone-dn 33, which appear on ephones 13 and 14, respectively.

ephone-dn-template 3

call-forwarding busy 4000

call-forwarding noan 4000 timeout 30

pickup group 4

ephone-dn 23

number 2323

ephone-dn-template 3

ephone-dn 33

number 3333

ephone-dn-template 3

ephone 13

button 1:23

ephone 14

button 1:33

Related Commands

Command	Description
ephone-dn-template (ephone-dn)	Applies an ephone-dn template to an ephone-dn.
restart (ephone)	Performs a fast reboot of a single phone associated with a Cisco Unified CME router.
restart (telephony-service)	Performs a fast reboot of one or all phones associated with a Cisco Unified CME router.
show telephony-service ephone-dn-template	Displays ephone-dn-template configurations.

ephone-dn-template (ephone-dn)

To apply an ephone-dn template to an ephone-dn, use the ephone-dn-template command in ephone-dn configuration mode. To remove the ephone-dn template, use the no form of this command.

ephone-dn-template template-tag

no ephone-dn-template template-tag

Syntax Description

template-tag

The template tag for a template created with the ephone-dn-template command in global configuration mode. Range is from 1 to 15.

Command Default

No ephone-dn template is applied to the ephone-dn.

Command Modes

Ephone-dn configuration (config-ephone-template)

Command History

Cisco IOS Release	Cisco Product	Modification
12.4(4)XC	Cisco Unified CME 4.0	This command was introduced.
12.4(9)T	Cisco Unified CME 4.0	This command was integrated into Cisco IOS Release 12.4(9)T.

Usage Guidelines

Use the ephone-dn-template command in ephone-dn configuration mode to apply an ephone-dn template to an ephone. You cannot apply more than one ephone-dn template to an ephone-dn.

If you try to apply a second ephone-dn template to an ephone-dn that already has an ephone-dn template applied to it, the second template will overwrite the first ephone-dn template configuration.

To view your ephone-dn-template configurations, use the show telephony-service ephone-dn-template command.

Examples

The following example shows how to create ephone-dn template 3, which sets call forwarding on busy and no answer to forward calls to extension 4000 and sets the pickup group to 4, and apply the template to ephone-dn 23 and ephone-dn 33, which appear on ephones 13 and 14, respectively.

ephone-dn-template 3

call-forwarding busy 4000

call-forwarding noan 4000 timeout 30

pickup group 4

ephone-dn 23

number 2323

ephone-dn-template 3

ephone-dn 33

number 3333

ephone-dn-template 3

ephone 13

button 1:23

ephone 14

button 1:33

Related Commands

Cisco Commands - Remote Phone Proxy

!show the remote phones associated with the ASA.
show phone-proxy secure-phones

OpenNMS Notes

(8:41:50 AM) lmbc2: I am interested in deploying an opennms setup to monitor 50-100 network devices (routers, switches, etc) and I want to use a hosting company to do this
(8:42:02 AM) lmbc2: anyone have any experience with this?
(8:42:24 AM) lmbc2: I was looking at Slicehost or Westhost but am open to other providers
(8:43:26 AM) markw78: what do you mean by a hosting company
(8:43:36 AM) markw78: you want to host opennms on the internet to monitor public network devices?
(8:48:45 AM) lmbc2: yes
(8:49:34 AM) RangerRick: lmbc2: some folks have run it on an ec2 host, so I don't see why not :)
(8:49:56 AM) RangerRick: as long as there are no firewalls or anything preventing machines from said hosting company from monitoring whatever it is you want to monitor
(8:51:16 AM) lmbc2: all of the machines are publicly accessible and we'd allow SNMP/ICMP from the static public IP for our VPS at the hosting company
(8:51:30 AM) RangerRick: then I don't see why not
(8:51:39 AM) lmbc2: cool
(8:53:09 AM) lmbc2: thanks for the help!
(8:53:10 AM) lmbc2: I haven't been able to find any documentation on anyone who has implemented opennms on any hosting platforms. Do you know of any and what platforms?
(8:55:28 AM) RangerRick: I know it's worked on ec2, and we also ran it on a hosted box at newedge networks
(8:55:52 AM) RangerRick: honestly, as long as you have a "real" system with java and root access, it shouldn't matter in any way that it's at a hosting company
(9:00:12 AM) lmbc2: ok
(9:00:21 AM) lmbc2: that makes sense
(9:00:26 AM) lmbc2: thanks for the help

Linux Stuffs

Backing up all of a certain document type off a hard drive

find /mnt/windows -name '*.doc' -exec cp {} /mnt/myusb/backupdir \;

Cobbled together using info from here:

http://www.codecoffee.com/tipsforlinux/articles/21.html
http://www.wagoneers.com/UNIX/FIND/find-usage.html

test

testing one more time

testing one more time

Testing yet again with force update turned on

Testing yet again with force update turned on

Testing yet again rss feed to email and twitter

Testing yet again rss feed to email and twitter

Testing r2e script - to ta email addy. Take 2

Testing r2e script - to ta email addy. Take.

Testing r2e script - to ta email addy

Testing r2e script - to ta email addy. Take 1.

Generate an RSA key

You need to generate an RSA key after defaulting a router to enable SSH access.

Router(config)# crypto key generate rsa

http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfssh.html

Cisco Commands - Show difference between running config and startup config

Ever wonder exactly what changes have been made to the running config? Should you save them before reloading or would that break everything. Use show archive config differences nvram:startup-config system:running-config to view the difference between the startup config and the current running config.

show archive config differences nvram:startup-config system:running-config

router#show archive config differences nvram:startup-config system:running-config
Contextual Config Diffs:
+ip access-list extended test

120651-149720#

More Info:
http://www.2000trainers.com/cisco-ccna-07/ccna-router-configuration-files/
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gt_diff.html
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gt_diff.html#wp1068464

Cisco Commands - Archive and Archive Config

Automated backups/revisions of configs on Cisco routers.

http://www.cisco.com/en/US/docs/ios/12_3t/fun/command/reference/cfrgt_01.html#wp1094316

archive

To enter archive configuration mode, use the archive command in global configuration mode.

archive

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Global configuration

Command History

Release	Modification
12.3(4)T	This command was introduced.
12.2(25)S	This command was integrated into Cisco IOS Release 12.2(25)S.

Examples

The following example shows how to place the router in archive configuration mode:

Router(config)# archive

Router(config-archive)# path disk0:myconfig

Related Commands

Command	Description
log config	Enters configuration change logger configuration mode.
logging enable	Enables the logging of configuration changes.
maximum	Sets the maximum number of archive files of the running configuration to be saved in the Cisco IOS configuration archive.
path	Specifies the location and filename prefix for the files in the Cisco IOS configuration archive.
time-period	Sets the time increment for automatically saving an archive file of the current running configuration in the Cisco IOS configuration archive.

archive config

To save a copy of the current running configuration to the Cisco IOS configuration archive, use the archive config command in privileged EXEC mode.

archive config

Syntax Description

This command has no arguments or keywords.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(7)T	This command was introduced.
12.2(25)S	This command was integrated into Cisco IOS Release 12.2(25)S.

Usage Guidelines

---

Note Before using this command, you must configure the path command in order to specify the location and filename prefix for the files in the Cisco IOS configuration archive.

---

The Cisco IOS configuration archive is intended to provide a mechanism to store, organize, and manage an archive of Cisco IOS configuration files in order to enhance the configuration rollback capability provided by the configure replace command. Before this feature was introduced, you could save copies of the running configuration using the copy running-config destination-url command, storing the target file either locally or remotely. However, this method lacked any automated file management. On the other hand, the Configuration Replace and Configuration Rollback feature provides the capability to automatically save copies of the running configuration to the Cisco IOS configuration archive. These archived files serve as checkpoint configuration references and can be used by the configure replace command to revert to previous configuration states.

The archive config command allows you to save Cisco IOS configurations in the configuration archive using a standard location and filename prefix that is automatically appended with an incremental version number (and optional timestamp) as each consecutive file is saved. This functionality provides a means for consistent identification of saved Cisco IOS configuration files. You can specify how many versions of the running configuration will be kept in the archive. After the maximum number of files has been saved in the archive, the oldest file will be automatically deleted when the next, most recent file is saved. The show archive command displays information for all configuration files saved in the Cisco IOS configuration archive.

Examples

The following example shows how to save the current running configuration to the Cisco IOS configuration archive using the archive config command. Before using the archive config command, you must configure the path command in order to specify the location and filename prefix for the files in the Cisco IOS configuration archive. In this example, the location and filename prefix is specified as disk0:myconfig as follows:

Router# configure terminal

Router(config)# archive

Router(config-archive)# path disk0:myconfig

You then save the current running configuration in the configuration archive as follows:

Router# archive config

The show archive command displays information on the files saved in the configuration archive as shown in the following sample output:

Router# show archive

There are currently 1 archive configurations saved.

The next archive file will be named disk0:myconfig-2

 Archive #  Name

   0

   1       disk0:myconfig-1 <- Most Recent

   2

   3

   4

   5

   6

   7

   8

   9

   10

Related Commands

Command	Description
archive	Enters archive configuration mode.
configure confirm	Confirms replacement of the current running configuration with a saved Cisco IOS configuration file.
configure replace	Replaces the current running configuration with a saved Cisco IOS configuration file.
maximum	Sets the maximum number of archive files of the running configuration to be saved in the Cisco IOS configuration archive.
path	Specifies the location and filename prefix for the files in the Cisco IOS configuration archive.
show archive	Displays information about the files saved in the Cisco IOS configuration archive.
time-period	Sets the time increment for automatically saving an archive file of the current running configuration in the Cisco IOS configuration archive.

Cisco Commands - config replace

Config replace allows you to overwrite your running config with the startup config or a config from flash, tftp, etc. WITHOUT reloading the router.

More info:
http://articles.techrepublic.com.com/5100-10878_11-6184709.html

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t7/feature/guide/gtrollbk.html

Configuration Replace

The configure replace command provides the capability to replace the current running configuration with any saved Cisco IOS configuration file. This functionality can be used to revert to a previous configuration state, effectively rolling back any configuration changes that were made since the previous configuration state was saved.

When using the configure replace command, you must specify a saved Cisco IOS configuration as the replacement configuration file for the current running configuration. The replacement file must be a complete configuration generated by a Cisco IOS device (for example, a configuration generated by the copy running-config destination-url command), or, if generated externally, the replacement file must comply with the format of files generated by Cisco IOS devices. When the configure replace command is entered, the current running configuration is compared with the specified replacement configuration and a set of diffs is generated. The algorithm used to compare the two files is the same as that employed by the show archive config differences command. The resulting diffs are then applied by the Cisco IOS parser to achieve the replacement configuration state. Only the diffs are applied, avoiding potential service disruption from reapplying configuration commands that already exist in the current running configuration. This algorithm effectively handles configuration changes to order-dependent commands (such as access lists) through a multiple pass process. Under normal circumstances, no more than three passes are needed to complete a configuration replace operation, and a limit of five passes is performed to preclude any looping behavior.

The Cisco IOS copy source-url running-config command is often used to copy a stored Cisco IOS configuration file to the running configuration. When using the copy source-url running-config command as an alternative to the configure replace target-url command, the following major differences should be noted:

•The copy source-url running-config command is a merge operation and preserves all the commands from both the source file and the current running configuration. This command does not remove commands from the current running configuration that are not present in the source file. In contrast, the configure replace target-url command removes commands from the current running configuration that are not present in the replacement file and adds commands to the current running configuration that need to be added.

•The copy source-url running-config command applies every command in the source file, whether or not the command is already present in the current running configuration. This algorithm is inefficient and, in some cases, can result in service outages. In contrast, the configure replace target-url command only applies the commands that need to be applied—no existing commands in the current running configuration are reapplied.

•A partial configuration file may be used as the source file for the copy source-url running-config command, whereas a complete Cisco IOS configuration file must be used as the replacement file for the configure replace target-url command.