2013/11/11

Error!!! Command is disabled

Declaration:
1.  CISCO Aironet LAP1131AG-A-K9.
2. Console cable used to CLI config.
3. Terminal emulator: Putty.

Problem:
1a. IP already set by someone, but no longer usable and must be changed.
1b. AP hostname no longer represent correct AP connection with controller, and needed to be changed.
2. Commands attempted to apply, always comes with the same result:
    #Error!!! Command is disabled.

Solution:
use the clear command!

#clear lwapp private-config
#clear lwapp ap hostname
ap#clear lwapp ap controller ip address
ap#lwapp ap hostname NEW-AP-NAME
#lwapp ap ip address x.x.x.x x.x.x.x

notice that your AP state changed from "DISCOVERY" to "JOIN", and watch how it recover its database...

2013/10/21

Reset CISCO Catalyst 3500 to Factory Defaults

re-configuring a long-time-no-use CISCO Catalyst, or a newly purchased a used one can be tricky and considerably to have a reconfiguring before production setup.

Here's simple steps to set CISCO Catalyst 3500 to Factory Defaults.

1. "unplug" the switch.

2. while holding the "mode" button (on the front left of the switch), plug-in the power-cord.

3. issue the "flash_init" command:
    switch: flash_init
    initializing flash...


4. issue the "load_helper" command:
    switch: load_helper 

5. locate pre-config files:
    switch: dir flash:

6. delete pre-config files:
    switch: del flash:config.text
    switch: del flash:vlan.dat


7. reboot switch
    switch: boot
    loading "flash:xxxxxxx"

Good to go..

2013/09/09

Fixing user account profile

receiving an error message: "The User Profile Service failed the logon" could be hell for many users and some not-so-experienced IT Guys..

There are 3 methods to fix this:
1. Fix the user account profile.
2. Logon using another Administrator privilege, and copy data to new account.
3. Delete the error SID, and create new one.

Let's do this..

Method-1: Fix the user account profile.
1. Go to registry editor. (don't ask how to get there)
2. Locate the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
3. Locate the folder begins with S-1-5 (SID Key) which followed by long-set of numbers.
4. Select each of the SID Key, locate the ProfileImagePath entry in details pane.


5. If you find 2 similar SID folder, but one of them ended with .bak, you'll have to rename it. Below 'll shows how:

5.a. Rename the one without .bak to .ba
5.b. Rename the one with .bak to *
5.c. Rename the one with .ba to .bak

the idea is:
the one with .bak actually is your original profile, but somehow system made own decision to re-create profile, so you have the one without .bak which caused problem later on. 
The task is to replace the one with .bak to none, and vice-versa.
(sure you'll get this idea)

6. If you have only 1 SID folder with .bak, simply rename it to *
7. Locate the SID without .bak, edit the RefCount. value should be as follow:
8. edit the State. value should be as follow:
9. restart and then log-in again with your intended account.

* means, delete .bak and leave the original SID folder name

Method-2: Logon using another Administrator privilege, and copy data to new account.
This method is simply rename your corrupted user profile, re-create user profile, and then copy all data from old to new.
Here's How:
1. Logon using Admin privilege account, and locate the "user" folder.
 C:\Users\

2. Change the "folder option view" properties, so you can see all content, including the hidden one.
3. Rename the corrupted user profile folder to something else, e.q: C:\Users\myuser-old
4. Logoff and then login again using the newly re-created user profile ("myuser").
5. Logoff and then login again using admin privilege account.
6. Copy all content within C:\Users\myuser-old to C:\Users\myuser\, except: Ntuser.dat, Ntuser.dat.log, Ntuser.ini
7. Logoff and then login again using "myuser"

Method-3: Delete the error SID, and create new one.
1. Login using Admin privilege account, and open "Change settings", in Computer Properties.
2. Select the "Advanced" tab, and open "User Profiles Settings"
3. In the User Profile dialog box, select the profile you want to delete, and click Delete.
4. Go to registry editor, and locate following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList
5. Delete the SID you want to remove.
6. Restart, and logon using the newly created profile.

==========================================================================
Those 3 methods are best-practice also acknowledge by Microsoft, but for me..
I rather use Method-1 and or Method-3, because it permanently re-configure registry (know that Microsoft is so much relies to its registry), minimise errors in the future, and easier to do.
There is weakness in this two methods, users' documents should be ready to demolish! :D

In other hand, Method-2 backed-up old users' data, and recovers them to the new profile, but sometimes if you keep -old in the C:\Users\.. can caused another "user" problem (if you're not aware of it of course) such as: missing archive files, confusing back-up destination since there are two similar folder, misplaced documents' folders, etc.

Final conclusion:

All 3 methods, would be best applied together!

2013/03/01

Frame-Relay Initial Config


Frame-relay configuration can be tricky for those who are not familiar with.
Below should shows the frame-relay initial config..

before you start, please be noticed that:
1. this config are tested on 'LAB' environment only!
2. Router (config)#frame-relay switching, must be done before configuring interfaces.
3. makes sure all interfaces are in 'shut' mode before you start configuring. After config finished (and you're sure its correct), give 'no shut' command. 

so, here it goes:

FRS#sh run | s interface
mmi polling-interval 60
interface Serial0/0
  no ip address
  encapsulation frame-relay
  serial restart-delay 0
  frame-relay intf-type dce                                            <=== serial cable for backbone-end
  frame-relay route 102 interface Serial 0/1 201     <=== define routing for dlci (in)... via interface ... for dlci (out)...
  frame-relay route 103 interface Serial 0/2 301     <=== define routing for dlci (in)... via interface ... for dlci (out)...
interface Serial0/1
  no ip address
  encapsulation frame-relay
  serial restart-delay 0
  frame-relay intf-type dce
  frame-relay route 201 interface Serial0/0 102
interface Serial0/2
  no ip address
  encapsulation frame-relay
  serial restart-delay 0
  frame-relay intf-type dce
  frame-relay route 301 interface Serial0/0 103
interface Serial0/3
  no ip address
  shutdown
  serial restart-delay 0

HQ#sh run | s interface
mmi polling-interval 60
interface Loopback1
  ip address 10.1.1.1 255.255.255.0
  interface Loopback2
  ip address 10.1.2.1 255.255.255.0
interface Loopback3
  ip address 10.1.3.1 255.255.255.0
interface Serial0/0
  no ip address
  encapsulation frame-relay
  serial restart-delay 0
interface Serial0/0.1 multipoint
  ip address 172.16.124.1 255.255.255.248
  frame-relay map ip 172.16.124.2 102 broadcast     <=== mapping to IP .... using dlci ...., and let everybody know!
  frame-relay map ip 172.16.124.3 103 broadcast
interface Serial0/1
  no ip address
  shutdown
  serial restart-delay 0
interface Serial0/2
  no ip address
  shutdown
  serial restart-delay 0
interface Serial0/3
  no ip address
  shutdown
  serial restart-delay 0

EAST#sh run | s interface
mmi polling-interval 60
interface Loopback1
  ip address 10.2.1.1 255.255.255.0

interface Loopback2
  ip address 10.2.2.1 255.255.255.0
interface Loopback3
  ip address 10.2.3.1 255.255.255.0
interface Serial0/0
  no ip address
  encapsulation frame-relay
  serial restart-delay 0
interface Serial0/0.1 point-to-point
  ip address 172.16.124.2 255.255.255.248
  frame-relay interface-dlci 201                                      <=== this interface is using dlci ... to communicate.
interface Serial0/1
  no ip address
  shutdown
  serial restart-delay 0
interface Serial0/2
  no ip address
  shutdown
  serial restart-delay 0
interface Serial0/3
  no ip address
  shutdown
  serial restart-delay 0

WEST#sh run | s interface
mmi polling-interval 60
interface Loopback1
  ip address 10.3.1.1 255.255.255.0
interface Loopback2
  ip address 10.3.2.1 255.255.255.0
interface Loopback3
  ip address 10.3.3.1 255.255.255.0
interface Serial0/0
  no ip address
  encapsulation frame-relay
  serial restart-delay 0
interface Serial0/0.1 point-to-point
  ip address 172.16.124.3 255.255.255.248
  frame-relay interface-dlci 301
interface Serial0/1
  no ip address
  shutdown
  serial restart-delay 0
interface Serial0/2
  no ip address
  shutdown
  serial restart-delay 0
interface Serial0/3
  no ip address
  shutdown
  serial restart-delay 0



Good Luck!