Cisco IOS Bundles

Cisco IOS Packaging

Cisco IOS Packaging consists of eight packages for Cisco routers and five packages for Cisco switches. (See Figure 6.)

Figure 6—Cisco IOS Packaging for Cisco Routers and Switches

Four packages are designed to satisfy requirements in four typical service categories:

• IP data

• Converged voice and data

• Security and VPN

• Enterprise protocols

Three additional premium packages offer new Cisco IOS Software feature combinations that address more complex network requirements. All features merge in the Advanced Enterprise Services package that integrates support for all routing protocols with Voice, Security, and VPN capabilities.

Feature inheritance is another powerful aspect of Cisco IOS Packaging. After a feature is introduced, it is included in the more comprehensive packages. The feature inheritance facilitates migration by clarifying the feature content of the different packages and how they relate to each another.

Cisco IOS Packaging also simplifies image naming. Each name is designed to effectively convey the high-level feature content of, and the inheritance characteristics for the new packages.

These categories summarize the new naming convention:

• Base—entry level image (IP Base, Enterprise Base)

• Services—addition of IP Telephony Service, MPLS, Voice over IP (VoIP), Voice over Frame Relay (VoFR), and ATM (SP Services, Enterprise Services)

• Advanced—addition of VPN, Cisco IOS Firewall, 3DES encryption, SSH, Cisco IOS IPsec and Intrusion Detection Systems (IDS) (Advanced Security, Advanced IP Services)

• Enterprise—addition of multi-protocols, including IBM, IPX, AppleTalk (Enterprise Base, Enterprise Services)

These packages are new:

• IP Base

• IP Voice

• Enterprise Base

• Advanced Security

• SP Services

• Advanced IP Services

• Enterprise Services

• Advanced Enterprise Services

http://www.cisco.com/warp/public/620/1.html

Alias for CLI Access to the CUE

!creating an alias to enable CLI access to the CUE module much more easily.

! alias exec

!do a sh ip int brief and look for the service-engine or integrated service-engine number to fill in the proper one. It is usually 0/0 though.

!alias exec cue service-module service-Engine <Service-engine location> session

Examples:

alias exec cue service-module service-Engine 0/0 session

alias exec cue service-module integrated-Service-Engine 0/0 session

rtr#conf t

rtr(config)#alias exec cue service-module service-Engine 0/0 session

rtr(config)#end

rtr#cu?

*cue="service-module service-Engine 0/0 session"

rtr#cue

Trying 10.1.10.1, 2194 ... Open

rtrcue#

Rebooting Cisco Phones

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_r1ht.html#wp1013890

Note that when resetting or restarting phones, the phone will not be rebooted immediately if it is currently in use. Instead, it will be rebooted once the phone call is over. Thus, resetting or restarting should both be safe to do during business hours as long as call traffic is not high at that point in time.

reset (ephone)

To perform a complete reboot of a single phone associated with a Cisco CallManager Express (Cisco CME) router, use the reset command in ephone configuration mode.

reset

Syntax Description

This command has no arguments or keywords.

Command Default

No reset is performed.

Command Modes

Ephone configuration (config-ephone)

Command History

Cisco IOS Release	Cisco Product	Modification
12.1(5)YD	Cisco ITS 1.0	This command was introduced
12.2(8)T	Cisco ITS 2.0	This command was integrated into Cisco IOS Release 12.2(8)T

Usage Guidelines

After you update information for one or more phones associated with a Cisco CME router, the phone or phones must be rebooted. There are two commands to reboot the phones: reset and restart. The reset command performs a "hard" reboot similar to a power-off-power-on sequence. It reboots the phone and contacts the Dynamic Host Configuration Protocol (DHCP) server and the TFTP server to update from their information as well. The restart command performs a "soft" reboot by simply rebooting the phone without contacting the DHCP and TFTP servers. The reset command takes significantly longer to process than the restart command when you are updating multiple phones, but it must be used after updating phone firmware, user locale, network locale, or URL parameters. For simple button, line, or speed-dial changes, you can use the restart command.

Use the reset (ephone) command to perform a complete reboot of an IP phone when you are in ephone configuration mode. This command has the same effect as a reset (telephony-service) command that is used to reset a single phone.

This command has a no form, but the no form has no effect.

Examples

The following example resets the SCCP phone with a phone-tag of 1:

Router(config)# ephone 1

Router(config-ephone)# reset

Related Commands

	Description
reset (telephony-service)	Performs a complete reboot of one or all phones associated with a Cisco CME router.
restart (ephone)	Performs a fast reboot of a single phone associated with a Cisco CME router.
restart (telephony-service)	Performs a fast reboot of one or all phones associated with a Cisco CME router.

reset (telephony-service)

To perform a complete reboot of one or all phones associated with a Cisco CallManager Express (Cisco CME) router, use the reset command in telephony-service configuration mode. To interrupt and cancel a sequential reset cycle, use the no form of the command with the sequence-all keyword.

reset {all [time-interval] | cancel | mac-address | sequence-all}

no reset {all [time-interval] | cancel | mac-address | sequence-all}

Syntax Description

all	Resets all Cisco IP phones served by the Cisco CME router. The router pauses for 15 seconds between the reset starts for each successive phone unless the time-interval argument is used to change that value.
time-interval	(Optional) Time interval, in seconds, between each phone reset. Range is from 0 to 60. Default is 15.
cancel	Interrupts a sequential reset cycle that was started with a reset sequence-all command.
mac-address	MAC address of a particular Cisco IP phone.
sequence-all	Resets all phones in strict one-at-a-time order by waiting for one phone to reregister before starting the reset for the next phone. The sequencing of resets prevents possible conflicts between phones trying to access TFTP services simultaneously. There is a reset timeout of 4 minutes, after which the router stops waiting for the currently registering phone to complete registration and starts to reset the next phone.

Command Default

No reset is performed.

Command Modes

Telephony-service configuration (config-telephony)

Command History

Cisco IOS Release	Cisco Product	Modification
12.1(5)YD	Cisco ITS 1.0	This command was introduced.
12.2(8)T	Cisco ITS 2.0	This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)YT	Cisco ITS 2.1	The time-interval range maximum was increased from 15 to 60 and the default was changed from 0 to 15.
12.2(11)YT1	Cisco ITS 2.1	The cancel and sequence-all keywords were introduced.
12.2(15)T	Cisco ITS 2.1	This command was integrated into Cisco IOS Release 12.2(15)T.

Usage Guidelines

After you update information for one or more phones associated with a Cisco CME router, the phone or phones must be rebooted using either the reset command or the restart command. The reset command performs a "hard" reboot similar to a power-off-power-on sequence and contacts the Dynamic Host Configuration Protocol (DHCP) server and the TFTP server for updated information as well. The restart command performs a "soft" reboot by simply rebooting the phone without contacting the DHCP and TFTP servers. The reset command takes significantly longer to process than the restart command when you are updating multiple phones, but it must be used after you make changes to phone firmware, user locale, network locale, or URL parameters. For simple button, line, or speed-dial changes, you can use the restart command.

When you use the reset command, the default time interval of 15 seconds is recommended so that phone reset operations are staggered in order to avoid all phones attempting to access router system resources at the same time. A shorter interval may be used on systems with only a small number of phones or for cases where a simple reset of the phones is desired that does not result in the phones downloading updates to the phone firmware (using the router's TFTP service).

When you use the reset sequence-all command, the router waits for one phone to complete its reset and reregister before starting to reset the next phone. The delay provided by this command prevents multiple phones from attempting to access the TFTP server simultaneously and therefore failing to reset properly. Each reset operation can take several minutes when you use this command. There is a reset timeout of 4 minutes, after which the router stops waiting for the currently registering phone to complete registration and starts to reset the next phone.

If the router configuration is changed so that the eXtensible Markup Language (XML) configuration files for the phones are modified (changes are made to user locale, network locale, or phone firmware), then whenever you use the reset all or restart all command, the router automatically executes the reset sequence-all command instead. The reset sequence-all command resets phones one at a time in order to prevent multiple phones from trying to contact the TFTP server simultaneously. This one-at-a-time sequencing can take a long time if there are many phones. To avoid this automatic behavior, use the reset all time-interval or the restart all time-interval with an explicit argument that is not equal to the default 15-second time interval; for example, set a time interval of 14 seconds. If a reset sequence-all command has been started in error, use the reset cancel command to interrupt and cancel the sequence of resets.

The restart command allows the system to perform quick phone resets in which only the button template, line information, and speed-dial information is updated. See the documentation for the restart command for more information.

The no form of this command has an effect only when used with the all or sequence-all keyword, when it interrupts and cancels the sequential resetting of phones.

Examples

The following example resets all IP phones served by the Cisco CME router:

Router(config)# telephony-service

Router(config-telephony)# reset all

The following example resets the Cisco IP phone with the MAC address CFBA.321B.96FA:

Router(config)# telephony-service

Router(config-telephony)# reset CFBA.321B.96FA

The following example resets all IP phones in sequential, not-overlapping order:

Router(config)# telephony-service

Router(config-telephony)# reset sequence-all

Related Commands

	Description
reset (ephone)	Performs a complete reboot of a single phone associated with a Cisco CME router.
restart (ephone)	Performs a fast reboot of a single phone associated with a Cisco CME router.
restart (telephony-service)	Performs a fast reboot of one or all phones associated with a Cisco CME router.
telephony-service	Enters telephony-service configuration mode.

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