I was looking to setup diverts on Iphone and found there is no way to do it as iphone OS will not let you to select diversion options.These codes will help!
About Call Diverts
With call diverts you can divert incoming calls to a fixed phone, or to another mobile. There are four call diversion options available which you can set up from your mobile:
Not Reachable Divert
* To activate **62* phone number # SEND
* To cancel ##62# SEND
* To check status *#62# SEND
Divert calls when busy
* To activate **62* phone number # SEND
* To cancel ##62# SEND
* To check status *#62# SEND
Divert calls when there is no reply
* To activate **61* phone number *11* no seconds# SEND
* To cancel ##61# SEND
* o check status *#61# SEND
Divert all calls
* To activate **21* phone number # SEND
* To cancel ##21# SEND
* To check status *#21# SEND
To cancel all call diverts
* To cancel ##002# SEND
Friday, 23 October 2009
Thursday, 30 July 2009
Free Custom iPhone Ringtones Using Only iTunes
Create free ringtones for your iPhone using only iTunes and songs you already have on your computer (This method only works with songs that are DRM free. To create ringtones using DRM protected songs please use this method). This method has been tested and works with iTunes 7.7.1 and iPhone 2.0.1 firmware.
To create custom ringtones using only iTunes:
1) Right click on the song you are going to make into a ringer and select “Get Info.”
2) Go to the options tab and go down to the “Start Time” and “Stop Time” check boxes. Check both boxes and input the time you want your ringer to start/stop. The ringer has to be 30 seconds or less. Click OK when you’re done.
3)Right click on your newly “clipped” song and select “Convert Selection to AAC.” The song will be re-encoded using the start and stop times determined (If your menu item does not read “Convert Selection to AAC” and reads “Convert Slection to MP3″ (or some other format) please go to iTunes > Preferences > Advanced > Importing and change the “Import Using” drop down menu to “AAC Encoder”).
4)After the song is done encoding navigate to your iTunes Music folder, locate your song, and drag it to your desktop. After the song is on your desktop go back to iTunes and delete the clipped version from you iTunes library (It won’t delete it from your desktop, it will only remove it from iTunes).
5)Go back the song on your desktop and right click on your song and chose “Get info.” Go to the name and extension section and change the extension from .m4a to .m4r (or you can just change the extension right from your desktop)
6)After the extension is changed simply double click on the file to add it to your iTunes library under the ringtones section. Sync your phone with iTunes and you’re done!
Remember to go back into iTunes and uncheck your custom start and stop times for the original version of your song.
To create custom ringtones using only iTunes:
1) Right click on the song you are going to make into a ringer and select “Get Info.”
2) Go to the options tab and go down to the “Start Time” and “Stop Time” check boxes. Check both boxes and input the time you want your ringer to start/stop. The ringer has to be 30 seconds or less. Click OK when you’re done.
3)Right click on your newly “clipped” song and select “Convert Selection to AAC.” The song will be re-encoded using the start and stop times determined (If your menu item does not read “Convert Selection to AAC” and reads “Convert Slection to MP3″ (or some other format) please go to iTunes > Preferences > Advanced > Importing and change the “Import Using” drop down menu to “AAC Encoder”).
4)After the song is done encoding navigate to your iTunes Music folder, locate your song, and drag it to your desktop. After the song is on your desktop go back to iTunes and delete the clipped version from you iTunes library (It won’t delete it from your desktop, it will only remove it from iTunes).
5)Go back the song on your desktop and right click on your song and chose “Get info.” Go to the name and extension section and change the extension from .m4a to .m4r (or you can just change the extension right from your desktop)
6)After the extension is changed simply double click on the file to add it to your iTunes library under the ringtones section. Sync your phone with iTunes and you’re done!
Remember to go back into iTunes and uncheck your custom start and stop times for the original version of your song.
Wednesday, 29 October 2008
Root access on Cisco Call Manager 5/6 Server
How to get Root access on Call Manager 5/6 Server
I think it is great that Cisco does not require Engineers to understand the underlying system CallManager is built on, but some of us are curious. These steps will let you to create a user on a CUCM 5/6 server with shell access and root privileges.
WARNING: This should not be performed on a Production System! I am not responsible for any destruction to production systems.
1. Boot the CUCM server with CentOS 5.1 Disk1
2. Type ‘linux rescue’ at the boot: prompt
3. Use the chroot command to change the root to the CUCM partition
Type 'chroot /mnt/sysimage'
4. Backup the /etc/passwd, /etc/group, /etc/shadow and /etc/gshadow files
cp -a /etc/passwd /etc/passwd.bak
cp -a /etc/group /etc/group.bak
cp -a /etc/shadow /etc/shadow.bak
cp -a /etc/gshadow /etc/gshadow.bak
These files are protected by the ext2 immutable flag. Check to see if the immutable flag is set. If the immutable flag is set, you will see an ‘i’.
lsattr /etc/passwd /etc/group /etc/shadow /etc/gshadow
5. Remove the immutable flag
chattr -i /etc/passwd /etc/group /etc/shadow /etc/gshadow
6. Add a new user and set a password
useradd username
passwd username
7. Add the immutable flag
chattr +i /etc/passwd /etc/group /etc/shadow /etc/gshadow
8. Add the new user to the /etc/sudoers file and give root privileges.
vi /etc/sudoers
9. Add the following line to the file to give the new user root privileges.
username All=(ALL) ALL
10. Exit Linux rescue mode
11. Login with the new account
12. Test various root level linux commands with ’sudo’ prefix, take a look at the filesystem and play around
I think it is great that Cisco does not require Engineers to understand the underlying system CallManager is built on, but some of us are curious. These steps will let you to create a user on a CUCM 5/6 server with shell access and root privileges.
WARNING: This should not be performed on a Production System! I am not responsible for any destruction to production systems.
1. Boot the CUCM server with CentOS 5.1 Disk1
2. Type ‘linux rescue’ at the boot: prompt
3. Use the chroot command to change the root to the CUCM partition
Type 'chroot /mnt/sysimage'
4. Backup the /etc/passwd, /etc/group, /etc/shadow and /etc/gshadow files
cp -a /etc/passwd /etc/passwd.bak
cp -a /etc/group /etc/group.bak
cp -a /etc/shadow /etc/shadow.bak
cp -a /etc/gshadow /etc/gshadow.bak
These files are protected by the ext2 immutable flag. Check to see if the immutable flag is set. If the immutable flag is set, you will see an ‘i’.
lsattr /etc/passwd /etc/group /etc/shadow /etc/gshadow
5. Remove the immutable flag
chattr -i /etc/passwd /etc/group /etc/shadow /etc/gshadow
6. Add a new user and set a password
useradd username
passwd username
7. Add the immutable flag
chattr +i /etc/passwd /etc/group /etc/shadow /etc/gshadow
8. Add the new user to the /etc/sudoers file and give root privileges.
vi /etc/sudoers
9. Add the following line to the file to give the new user root privileges.
username All=(ALL) ALL
10. Exit Linux rescue mode
11. Login with the new account
12. Test various root level linux commands with ’sudo’ prefix, take a look at the filesystem and play around
Tuesday, 7 October 2008
Easy steps to debrand N95/N95 8GB
Switch off any Anti Virus and disable any firewall
Firstly you will need to Sync your stuff with PC Suite.
DO NOT use backup and restore as this has shown to cause future problems with stability!
If you need your texts message for reference then change the message settings to save on your memory card and you get the option to copy across all existing texts.You will also 'loose' all your installed apps and will have to reinstall these once you have completed the Debrand/upgrade process.
You will also need all your network and internet (data) access settings. You can note them down, get them resent after the debrand/upgrade to your phone by text message from your network provider or from Nokia, or simply get them from here http://www.filesaveas.com/networks.html.
Next step is to download a programme called Nemesis Service Suite (NSS) from here
http://www.b-phreaks.co.uk/files/NSS/NSS103812.zip
Unzip this to a folder that you can find again! Install the application. You may be asked to install the NSS drivers for the N95 so do this when prompted.
Now run NSS and you are starting the debrand process!
When the main NSS window comes up in the top right click scan for new device. Your phone should be detected.
Next click the 'Phone Info' button. This will give a pane to the right of the window and ready should be flashing on the bottom bar. Click the 'Read' button under 'Production Data Edit'. this brings up some phone info including the important 'Product Code'. Your code will relate to your country and network provider and it is this we need to change!
This forum page http://www.allaboutsymbian.com/forum/showthread.php?t=58225 will give you a list of product codes. (while you are on that page consider joining the forum for future assistance).
For most people the generic EURO1 code is what we want so note it down (it doesn't matter whether you use the sand or plum code)!
You now need to input the code in place of the one that NSS returned against it's 'Product Code'
box! Copy and paste will do it! Tick the enable box alongside and then click the 'Write' button. When finished 'Write new values........Done' will appear in the bottom bar at the left. Your 'new' product code will now be shown in the 'Product Code' box.
Your phone is now ready to be upgraded to the latest official Nokia generic firmware release.
Close NSS and open Nokia PC Suite!
Make sure your battery is fully charged.
Click the 'Update phone software' button and the programme will lead you through the process of update. You may be required to download and install a newer version of the 'Nokia Software Updater' so just agree and wait for this to complete.
The NSU (Nokia Sofware Updater) will start and give instructions! It will detect your phone, identify it and search for an available update. Then, if one is available, it will give the option of proceeding with the update. Say yes and once the update has started wait until the process has finished.
Do not touch the phone, do not turn it off, do not disconnect the USB cable.
When the update has finished your phone will restart and you will have installed the latest firmware version of the Operating System.
At this point it does no harm to do a hard reset (see below) just to be sure you have what is refered to as a 'vanilla' phone.
Now re-sync with PC Suite and re-enter your network access and data settings.
Finally, re-install your applicationsto the phone memory (if you use the card memory you can get problems and power consumption goes up so less battery life!
And that's it! You should end up with a stable and zippy phone and the minimum of problems!
I hope all this helps and to anyone undertaking the procedure "GOOD LUCK"
Here are some useful 'Codes' that will interogate the phone
*#06# gives your IMEI (serial) number.
*#0000# gives firmware and phone version.
*#2820# (*#BTA0#) To view Bluetooth device address.
*#62209526# (*#MAC0WLAN) To view the MAC address of the WLAN adapter. This is maybe necessary for wlan encrypted setup.
*#92702689# (*#WAR0ANTY#) To view the life timer information. This is the total time of phone calls in minutes.
Warning : All old data will be lost when hard reset is used.
*#7780# : Soft Reset. Restores ini files from rom but preserves user data (photos, 3rd party apps etc).The phone will ask you a confirmation, enter a security code which is 12345 by default.
*#7370# : Hard (sometimes called 'Deep') Reset. You will get a format of the C: drive. Everything on the drive will be wiped and clean default files will be rewritten. You will be asked to input a security code which is 12345 by default.
There is another method of hard resetting the phone (similar to #*7370#). It is useful in some cases, for example when the phone cannot reboot. Switch off the phone then press and hold Call key (Green key) + * key + 3 key + power button for a couple of seconds. If you hold these buttons until 'Formatting' is shown you will get the same result as using *#7370#
Firstly you will need to Sync your stuff with PC Suite.
DO NOT use backup and restore as this has shown to cause future problems with stability!
If you need your texts message for reference then change the message settings to save on your memory card and you get the option to copy across all existing texts.You will also 'loose' all your installed apps and will have to reinstall these once you have completed the Debrand/upgrade process.
You will also need all your network and internet (data) access settings. You can note them down, get them resent after the debrand/upgrade to your phone by text message from your network provider or from Nokia, or simply get them from here http://www.filesaveas.com/networks.html.
Next step is to download a programme called Nemesis Service Suite (NSS) from here
http://www.b-phreaks.co.uk/files/NSS/NSS103812.zip
Unzip this to a folder that you can find again! Install the application. You may be asked to install the NSS drivers for the N95 so do this when prompted.
Now run NSS and you are starting the debrand process!
When the main NSS window comes up in the top right click scan for new device. Your phone should be detected.
Next click the 'Phone Info' button. This will give a pane to the right of the window and ready should be flashing on the bottom bar. Click the 'Read' button under 'Production Data Edit'. this brings up some phone info including the important 'Product Code'. Your code will relate to your country and network provider and it is this we need to change!
This forum page http://www.allaboutsymbian.com/forum/showthread.php?t=58225 will give you a list of product codes. (while you are on that page consider joining the forum for future assistance).
For most people the generic EURO1 code is what we want so note it down (it doesn't matter whether you use the sand or plum code)!
You now need to input the code in place of the one that NSS returned against it's 'Product Code'
box! Copy and paste will do it! Tick the enable box alongside and then click the 'Write' button. When finished 'Write new values........Done' will appear in the bottom bar at the left. Your 'new' product code will now be shown in the 'Product Code' box.
Your phone is now ready to be upgraded to the latest official Nokia generic firmware release.
Close NSS and open Nokia PC Suite!
Make sure your battery is fully charged.
Click the 'Update phone software' button and the programme will lead you through the process of update. You may be required to download and install a newer version of the 'Nokia Software Updater' so just agree and wait for this to complete.
The NSU (Nokia Sofware Updater) will start and give instructions! It will detect your phone, identify it and search for an available update. Then, if one is available, it will give the option of proceeding with the update. Say yes and once the update has started wait until the process has finished.
Do not touch the phone, do not turn it off, do not disconnect the USB cable.
When the update has finished your phone will restart and you will have installed the latest firmware version of the Operating System.
At this point it does no harm to do a hard reset (see below) just to be sure you have what is refered to as a 'vanilla' phone.
Now re-sync with PC Suite and re-enter your network access and data settings.
Finally, re-install your applicationsto the phone memory (if you use the card memory you can get problems and power consumption goes up so less battery life!
And that's it! You should end up with a stable and zippy phone and the minimum of problems!
I hope all this helps and to anyone undertaking the procedure "GOOD LUCK"
Here are some useful 'Codes' that will interogate the phone
*#06# gives your IMEI (serial) number.
*#0000# gives firmware and phone version.
*#2820# (*#BTA0#) To view Bluetooth device address.
*#62209526# (*#MAC0WLAN) To view the MAC address of the WLAN adapter. This is maybe necessary for wlan encrypted setup.
*#92702689# (*#WAR0ANTY#) To view the life timer information. This is the total time of phone calls in minutes.
Warning : All old data will be lost when hard reset is used.
*#7780# : Soft Reset. Restores ini files from rom but preserves user data (photos, 3rd party apps etc).The phone will ask you a confirmation, enter a security code which is 12345 by default.
*#7370# : Hard (sometimes called 'Deep') Reset. You will get a format of the C: drive. Everything on the drive will be wiped and clean default files will be rewritten. You will be asked to input a security code which is 12345 by default.
There is another method of hard resetting the phone (similar to #*7370#). It is useful in some cases, for example when the phone cannot reboot. Switch off the phone then press and hold Call key (Green key) + * key + 3 key + power button for a couple of seconds. If you hold these buttons until 'Formatting' is shown you will get the same result as using *#7370#
Saturday, 20 September 2008
How to simulate ISDN Back To Back Configuration POTS Dial-Peers?
Connect two routers back-to-back style with cross over cable. Define switch type lets say qsig, then framing, line code, clock source, pri groups, user side, network side. (mean while forget about IP networks).
Here is one basic sample config, see how direct-indward-dial works, try some show and debug commands show isdn status, debug q931and q921 to see call set up signaling stuff.
(ISDN PRI Back To Back Configuration_Pots Dial-Peers)
USER SIDE CONFIGURATION
------------------------------
R1_3640#sh run
!
isdn switch-type primary-qsig
!
controller T1 1/0
framing esf
linecode b8zs
pri-group timeslots 1-4,24
!
interface Serial1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
no cdp enable
!
voice-port 1/0:23
!
voice-port 3/0/0
!
dial-peer voice 1111 pots
destination-pattern 1111
port 3/0/0
!
dial-peer voice 2222 pots
destination-pattern 2222
direct-inward-dial
port 1/0:23
forward-digits all
-------------------------------
NETWORK SIDE CONFIGURATION
-------------------------------
R2_3725#sh run
!
isdn switch-type primary-qsig
!
controller T1 1/0
framing esf
clock source internal
linecode b8zs
pri-group timeslots 1-4,24
!
interface Serial1/0:23
no ip address
isdn switch-type primary-qsig
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
!
voice-port 1/0:23
!
voice-port 2/0/0
!
dial-peer voice 2222 pots
destination-pattern 2222
port 2/0/0
!
dial-peer voice 1111 pots
destination-pattern 1111
direct-inward-dial
port 1/0:23
forward-digits all
Here is one basic sample config, see how direct-indward-dial works, try some show and debug commands show isdn status, debug q931and q921 to see call set up signaling stuff.
(ISDN PRI Back To Back Configuration_Pots Dial-Peers)
USER SIDE CONFIGURATION
------------------------------
R1_3640#sh run
!
isdn switch-type primary-qsig
!
controller T1 1/0
framing esf
linecode b8zs
pri-group timeslots 1-4,24
!
interface Serial1/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-qsig
isdn incoming-voice voice
no cdp enable
!
voice-port 1/0:23
!
voice-port 3/0/0
!
dial-peer voice 1111 pots
destination-pattern 1111
port 3/0/0
!
dial-peer voice 2222 pots
destination-pattern 2222
direct-inward-dial
port 1/0:23
forward-digits all
-------------------------------
NETWORK SIDE CONFIGURATION
-------------------------------
R2_3725#sh run
!
isdn switch-type primary-qsig
!
controller T1 1/0
framing esf
clock source internal
linecode b8zs
pri-group timeslots 1-4,24
!
interface Serial1/0:23
no ip address
isdn switch-type primary-qsig
isdn protocol-emulate network
isdn incoming-voice voice
no cdp enable
!
voice-port 1/0:23
!
voice-port 2/0/0
!
dial-peer voice 2222 pots
destination-pattern 2222
port 2/0/0
!
dial-peer voice 1111 pots
destination-pattern 1111
direct-inward-dial
port 1/0:23
forward-digits all
Friday, 19 September 2008
How to set up a Cisco router to act as an NTP server?
Step 1 Log in to the router.
Step 2 Enter configuration mode:
router# configure terminal
Step 3 Create the key ID and key value:
router(config)# ntp authentication-key key_ID md5 key_value
The key ID can be a number between 1 and 65535. The key value is text (numeric or character). It is encrypted later.
Example:
router(config)# ntp authentication-key 100 md5 attack
Note The sensor only supports MD5 keys.
Note Keys may already exist on the router. Use the show running configuration command to check for other keys. You can use those values for the trusted key in Step 4.
Step 4 Designate the key you just created in Step 3 as the trusted key (or use an existing key):
router(config)# ntp trusted-key key_ID
The trusted key ID is the same number as the key ID in Step 3.
Example:
router(config)# ntp trusted-key 100
Step 5 Specify the interface on the router that the sensor will communicate with:
router(config)# ntp source interface_name
Example:
router(config)# ntp source FastEthernet 1/0
Step 6 Specify the NTP master stratum number to be assigned to the sensor:
router(config)# ntp master stratum_number
Example:
router(config)# ntp master 6
The NTP master stratum number identifies the server's relative position in the NTP hierarchy. You can choose a number between 1 and 15.
Step 2 Enter configuration mode:
router# configure terminal
Step 3 Create the key ID and key value:
router(config)# ntp authentication-key key_ID md5 key_value
The key ID can be a number between 1 and 65535. The key value is text (numeric or character). It is encrypted later.
Example:
router(config)# ntp authentication-key 100 md5 attack
Note The sensor only supports MD5 keys.
Note Keys may already exist on the router. Use the show running configuration command to check for other keys. You can use those values for the trusted key in Step 4.
Step 4 Designate the key you just created in Step 3 as the trusted key (or use an existing key):
router(config)# ntp trusted-key key_ID
The trusted key ID is the same number as the key ID in Step 3.
Example:
router(config)# ntp trusted-key 100
Step 5 Specify the interface on the router that the sensor will communicate with:
router(config)# ntp source interface_name
Example:
router(config)# ntp source FastEthernet 1/0
Step 6 Specify the NTP master stratum number to be assigned to the sensor:
router(config)# ntp master stratum_number
Example:
router(config)# ntp master 6
The NTP master stratum number identifies the server's relative position in the NTP hierarchy. You can choose a number between 1 and 15.
Wednesday, 2 July 2008
How to upgrade IOS on a Cisco router with built-in flash memory
Step 1: Establish a console session to the router
Even if it is possible to connect to the router through a telnet session, it is strongly recommended to be directly connected to the router using the console port. The reason is that if something goes wrong during the upgrade, it might be necessary to be physically located next to the router to power-cycle it. Moreover, the telnet connection will be lost while the router is rebooting during the upgrade procedure.
A rolled cable (usually a flat black cable) is used to connect the console port of the router to one of the COM ports of the PC.
Once the PC is connected to the console port of the router, you need to open Hyperterminal on the PC, and use the following settings:
Speed 9600 bits per second
8 databits
0 parity bits
1 stop bit
No Flow Control
Note: If you are getting any garbage characters in the hyperterminal session, this means that you have not set the hyperterminal properties properly, or the config-register of the router is set to a non-standard value for which the console connection speed is higher than 9600 bps. Check the value of the config-register using the show version command (shown in the last line of the output) and ensure it is set to 0x2102 or 0x102. It is necessary to reload the router for a configuration register change to take effect. Once you are sure the console speed is set to 9600 bps on the router side, you should check the hyperterminal properties as above .
Booting Problems
Once you are connected to the console port of the router, you might notice that the router is either in ROMmon or Boot mode. These two modes are used for recovery and/or diagnostic procedures. If you do not see the usual router prompt, you should follow the recommendations below to proceed with the upgrade procedure installation.
Router boots in rommon mode, and the following message appears when you issue dir flash: command.
rommon 1 > dir flash:
device does not contain a valid magic number
dir: cannot open device "flash:"
rommon 2 >
When you see the above error message, it means the Flash is empty or the filesystem is corrupted. A Xmodem console download procedure using ROMmon may then be necessary.
Router boots in boot mode, with the following messages on the console:
router(boot)>
device does not contain a valid magic number
boot: cannot open "flash:"
boot: cannot determine first file name on device "flash:"
When you get the above error messages on the console output, it means the Flash is empty or the file system is corrupted. Copy a valid image on the Flash by following the procedures provided in this document.
Step 2: Verify that the TFTP server has IP connectivity to the router
The TFTP server must have a network connection to the router, and must be able to ping the IP address of the router targeted for a TFTP software upgrade. To achieve this, the router interface and the TFTP server must have:
an IP address in the same range, or
a default gateway configured.
To verify this, check the IP address of the TFTP server.
Step 3: Copy the new image into the Flash memory of the 2600 Series Router through the TFTP server
Now that you have IP connectivity and can ping between the computer acting as a TFTP server and the router, you can copy the Cisco IOS Software image into the Flash.
Note: Before copying, make sure you have started the TFTP server software on your PC and that you have the filename mentioned in the TFTP server root directory. We recommend that you keep a backup of the router/access server configuration before upgrading. The upgrade itself does not affect the configuration (which is stored in nonvolatile RAM (NVRAM). However, this might happen if the right steps are not followed properly.
For RCP applications, substitute RCP for every occurrence of TFTP. For example, use the copy rcp flash command instead of the copy tftp flash command.
2600> enable
Password:xxxxx
2600#
2600# copy tftp flash
If necessary, you can copy an image from one device to another.
Specify the IP address of the TFTP server.
When prompted, enter the IP address of the TFTP server as in the following example:
Address or name of remote host []? 10.10.10.2
Specify the filename of the new Cisco IOS Software image.
When prompted, enter the filename of the Cisco IOS Software image to be installed, as in the following example:
Source filename []? c2600-i-mz.121-14.bin
Note: The filename is case sensitive, so be sure to enter it correctly.
Specify the destination filename.
This is the name the new software image will have when it is loaded onto the router. The image can be named anything, but common practice is to enter the same image filename.
Destination filename []? c2600-i-mz.121-14.bin
Note: If you see the below error message:
%Error copying tftp://10.10.10.2/c2600-i-mz.121-14.bin
(Not enough space on device)
This indicates that there is not enough room available in Flash to copy the image. You need to erase a file(s) before copying the new image from the TFTP server.
Upgrade the new image from a TFTP server
2610#copy tftp flash
Address or name of remote host []? 10.10.10.2
Source filename []? c2600-i-mz.121-14.bin
Destination filename [c2600-i-mz.121-14.bin]?y
Accessing tftp://10.10.10.2/c2600-i-mz.121-14.bin...
Erase flash: before copying? [confirm]y !---If there is not enough
!--- memory available, erase the Flash
Erasing the flash filesystem will remove all files! Continue? [confirm]y
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeee ...erased
Erase of flash: complete
Loading c2600-i-mz.121-14.bin from 10.10.10.2 (via Ethernet0/0): !!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 4501480/9001984 bytes]
Verifying checksum... OK (0xAC8A)
4501480 bytes copied in 56.88 secs (80383 bytes/sec)
The copying process takes several minutes; the time differs from network to network. During the copy process, messages are displayed to indicate which file has been accessed.
The exclamation point "!" indicates that the copy process is taking place. Each exclamation point indicates that ten packets have been transferred successfully. A checksum verification of the image occurs after the image is written to Flash memory.
After you have upgraded the Flash, you need to reload the router using the reload command.
Before you reload the router, you need to check two things:
The value of the config-register - You can check this using the show version command. The value is shown in the last line of the show version output. It should be set to 0x2102.
2610#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
2610(config)#config-register 0x2102
2610(config)#^Z
The other files on the Flash - If the first file in the Flash is not the Cisco IOS Software image, but a configuration file or something else, then you need to configure a boot system statement in order to boot the specified image. Otherwise, the router will try to boot with the configuration file or the first file in the Flash; this will not work. If there is only one file in the Flash which is the Cisco IOS Software image, then this step is not necessary.
2610#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
2610(config)#no boot system
2610(config)#boot system flash c2600-i-mz.121-14.bin
2610(config)#^Z
Note: If you type the reload command, the router asks you if you want to save the configuration. You should be very cautious here. The reason is that if the router is in boot mode for instance, it is a subset of the full Cisco IOS software which is running and there is no routing functionality. Therefore, all the routing configuration is gone in the running configuration and if you save the configuration at this time, then you erase the good startup-configuration in NVRAM and replace it by the incomplete running-configuration. Save the configuration only if you are sure that you have the full configuration in the output of show run. It is NOT necessary to save the configuration to take into account the new config-register if this one has been changed previously. That is done automatically.
2610#reload
System configuration has been modified. Save? [yes/no]: y
Building configuration...
[OK]
Proceed with reload? [confirm]y
Verify that the router is running with the proper image. After the reload is complete, the router should be running the desired Cisco IOS Software image. Use the show version command to verify.
2610#show version
00:22:25: %SYS-5-CONFIG_I: Configured from console by console
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-I-M), Version 12.1(14), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Mon 25-Mar-02 20:33 by kellythw
Image text-base: 0x80008088, data-base: 0x80828788
ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
2610 uptime is 22 minutes
System returned to ROM by reload
System image file is "flash:c2600-i-mz.121-14.bin"
Even if it is possible to connect to the router through a telnet session, it is strongly recommended to be directly connected to the router using the console port. The reason is that if something goes wrong during the upgrade, it might be necessary to be physically located next to the router to power-cycle it. Moreover, the telnet connection will be lost while the router is rebooting during the upgrade procedure.
A rolled cable (usually a flat black cable) is used to connect the console port of the router to one of the COM ports of the PC.
Once the PC is connected to the console port of the router, you need to open Hyperterminal on the PC, and use the following settings:
Speed 9600 bits per second
8 databits
0 parity bits
1 stop bit
No Flow Control
Note: If you are getting any garbage characters in the hyperterminal session, this means that you have not set the hyperterminal properties properly, or the config-register of the router is set to a non-standard value for which the console connection speed is higher than 9600 bps. Check the value of the config-register using the show version command (shown in the last line of the output) and ensure it is set to 0x2102 or 0x102. It is necessary to reload the router for a configuration register change to take effect. Once you are sure the console speed is set to 9600 bps on the router side, you should check the hyperterminal properties as above .
Booting Problems
Once you are connected to the console port of the router, you might notice that the router is either in ROMmon or Boot mode. These two modes are used for recovery and/or diagnostic procedures. If you do not see the usual router prompt, you should follow the recommendations below to proceed with the upgrade procedure installation.
Router boots in rommon mode, and the following message appears when you issue dir flash: command.
rommon 1 > dir flash:
device does not contain a valid magic number
dir: cannot open device "flash:"
rommon 2 >
When you see the above error message, it means the Flash is empty or the filesystem is corrupted. A Xmodem console download procedure using ROMmon may then be necessary.
Router boots in boot mode, with the following messages on the console:
router(boot)>
device does not contain a valid magic number
boot: cannot open "flash:"
boot: cannot determine first file name on device "flash:"
When you get the above error messages on the console output, it means the Flash is empty or the file system is corrupted. Copy a valid image on the Flash by following the procedures provided in this document.
Step 2: Verify that the TFTP server has IP connectivity to the router
The TFTP server must have a network connection to the router, and must be able to ping the IP address of the router targeted for a TFTP software upgrade. To achieve this, the router interface and the TFTP server must have:
an IP address in the same range, or
a default gateway configured.
To verify this, check the IP address of the TFTP server.
Step 3: Copy the new image into the Flash memory of the 2600 Series Router through the TFTP server
Now that you have IP connectivity and can ping between the computer acting as a TFTP server and the router, you can copy the Cisco IOS Software image into the Flash.
Note: Before copying, make sure you have started the TFTP server software on your PC and that you have the filename mentioned in the TFTP server root directory. We recommend that you keep a backup of the router/access server configuration before upgrading. The upgrade itself does not affect the configuration (which is stored in nonvolatile RAM (NVRAM). However, this might happen if the right steps are not followed properly.
For RCP applications, substitute RCP for every occurrence of TFTP. For example, use the copy rcp flash command instead of the copy tftp flash command.
2600> enable
Password:xxxxx
2600#
2600# copy tftp flash
If necessary, you can copy an image from one device to another.
Specify the IP address of the TFTP server.
When prompted, enter the IP address of the TFTP server as in the following example:
Address or name of remote host []? 10.10.10.2
Specify the filename of the new Cisco IOS Software image.
When prompted, enter the filename of the Cisco IOS Software image to be installed, as in the following example:
Source filename []? c2600-i-mz.121-14.bin
Note: The filename is case sensitive, so be sure to enter it correctly.
Specify the destination filename.
This is the name the new software image will have when it is loaded onto the router. The image can be named anything, but common practice is to enter the same image filename.
Destination filename []? c2600-i-mz.121-14.bin
Note: If you see the below error message:
%Error copying tftp://10.10.10.2/c2600-i-mz.121-14.bin
(Not enough space on device)
This indicates that there is not enough room available in Flash to copy the image. You need to erase a file(s) before copying the new image from the TFTP server.
Upgrade the new image from a TFTP server
2610#copy tftp flash
Address or name of remote host []? 10.10.10.2
Source filename []? c2600-i-mz.121-14.bin
Destination filename [c2600-i-mz.121-14.bin]?y
Accessing tftp://10.10.10.2/c2600-i-mz.121-14.bin...
Erase flash: before copying? [confirm]y !---If there is not enough
!--- memory available, erase the Flash
Erasing the flash filesystem will remove all files! Continue? [confirm]y
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee
eeeeeeeeee ...erased
Erase of flash: complete
Loading c2600-i-mz.121-14.bin from 10.10.10.2 (via Ethernet0/0): !!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 4501480/9001984 bytes]
Verifying checksum... OK (0xAC8A)
4501480 bytes copied in 56.88 secs (80383 bytes/sec)
The copying process takes several minutes; the time differs from network to network. During the copy process, messages are displayed to indicate which file has been accessed.
The exclamation point "!" indicates that the copy process is taking place. Each exclamation point indicates that ten packets have been transferred successfully. A checksum verification of the image occurs after the image is written to Flash memory.
After you have upgraded the Flash, you need to reload the router using the reload command.
Before you reload the router, you need to check two things:
The value of the config-register - You can check this using the show version command. The value is shown in the last line of the show version output. It should be set to 0x2102.
2610#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
2610(config)#config-register 0x2102
2610(config)#^Z
The other files on the Flash - If the first file in the Flash is not the Cisco IOS Software image, but a configuration file or something else, then you need to configure a boot system statement in order to boot the specified image. Otherwise, the router will try to boot with the configuration file or the first file in the Flash; this will not work. If there is only one file in the Flash which is the Cisco IOS Software image, then this step is not necessary.
2610#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
2610(config)#no boot system
2610(config)#boot system flash c2600-i-mz.121-14.bin
2610(config)#^Z
Note: If you type the reload command, the router asks you if you want to save the configuration. You should be very cautious here. The reason is that if the router is in boot mode for instance, it is a subset of the full Cisco IOS software which is running and there is no routing functionality. Therefore, all the routing configuration is gone in the running configuration and if you save the configuration at this time, then you erase the good startup-configuration in NVRAM and replace it by the incomplete running-configuration. Save the configuration only if you are sure that you have the full configuration in the output of show run. It is NOT necessary to save the configuration to take into account the new config-register if this one has been changed previously. That is done automatically.
2610#reload
System configuration has been modified. Save? [yes/no]: y
Building configuration...
[OK]
Proceed with reload? [confirm]y
Verify that the router is running with the proper image. After the reload is complete, the router should be running the desired Cisco IOS Software image. Use the show version command to verify.
2610#show version
00:22:25: %SYS-5-CONFIG_I: Configured from console by console
Cisco Internetwork Operating System Software
IOS (tm) C2600 Software (C2600-I-M), Version 12.1(14), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Mon 25-Mar-02 20:33 by kellythw
Image text-base: 0x80008088, data-base: 0x80828788
ROM: System Bootstrap, Version 11.3(2)XA4, RELEASE SOFTWARE (fc1)
2610 uptime is 22 minutes
System returned to ROM by reload
System image file is "flash:c2600-i-mz.121-14.bin"
Subscribe to:
Posts (Atom)
Posts
