Tuesday, September 28, 2010

UC560 CUE 8.02 Choppy Voice Mail / Auto Attendant

This was posted by a friend of mine as a comment. I thought it warranted a separate posting. Thanks Mike.


Here's his LinkedIn page.
http://www.linkedin.com/in/mfoster670


As of today we have a good idea of what the issue is with the Choppy Voice Mail and AA when upgrading to 8.0.2 version of CUE. However there is still not a permanent fix for this issue. First work around is creating a script that reboots CUE everyday at a certain time. The example listed below is for 4 am every day.



config t
event manager applet cue_reset
event timer cron cron-entry "0 4 * * *" (there are spaces between each entry)
action 1 cli command "enable"
action 2 cli command "service-module integrated-Service-Engine 0/0 reset" pattern "confirm"
action 3 cli command "y" 

Monday, September 27, 2010

How to Downgrade Cisco Lightweight AP to Autonomous AP

Revert your Cisco AP using a TFTP server and a new IOS File:

1- The PC on which your TFTP server software runs must be configured with a static IP address in the range    of 10.0.0.2 to 10.0.0.30. The subnet mask will be 255.0.0.0.

2- Make sure that the PC contains the access point image file in the TFTP server folder and that the TFTP server is activated. An example IOS file would be c1130-k9w7-tar.124-10b.JDA3.tar for an 1100 series access point.

3- Rename the access point image file in the TFTP server folder to the default image name. It will be c1200-k9w7-tar.default for a 1200 series AP or c1130-k9w7-tar.default for an 1130 series AP.

4- Connect the PC to the access point using an Ethernet cable.

5- Disconnect power from the access point.

6- Press and hold the MODE button while you reconnect power to the access point.

7- Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds), and release the MODE button. For the 1130 APs, hold the button until the console indicates that the button is pressed (the R LED will be solid red): Console will read something like this: button is pressed, wait for button to be released...

Once it starts uploading, the E & R LEDs will both be blinking (1130 AP). Once you release the button, you should see the console extracting files from the tarball on the TFTP server.

**NOTE** - I have had some TFTP server software fail to start the download. If you run into this issue try a different TFTP server software.

Links to my favorite free TFTP software:
TFTPD32
3COM 3CDaemon

8- Wait until the access point reboots. The best way to see when it has rebooted is to watch the console.

9- After the access point reboots, reconfigure the access point using the GUI or the CLI

CLI REFERENCE (You will need a Cisco Login to Access the following link)

http:/www.cisco.com/en/US/partner/docs/wireless/access_point/ios/release/notes/b311jx1.html

Thursday, September 23, 2010

Vizioncore VReplicator Jobs Failing?

Vizioncore vReplicator
When jobs are failing check these things.
For Changed Block Tarcking (CBT) to work all VMDKs must have a single partition and it must be primary.

If you have issues with jobs failing try this:
 
The CBT file is stale and needs to be recreated
1.  In vReplicator, click on Tools -> Change Block Tracking Options
2.  Find the VM and uncheck CBT
3.  Delete the vreplicator job and recreate it
5.  In VCenter, create a snapshot
6.  In vReplicator, check CBT for the VM
7.  In VCenter, delete the snapshot
8.  Retry the replication.

NetApp Losing IP Config After Reboot


If your interfaces are losing configuration you must edit the /etc/rc file. The filer uses this file at boot for settings. You can change this file by:

1.Running setup again.
2. Edit etc rc file

*****Makes sure you read the /etc/rc file into memory first using:   rdfile /etc/rc *****

CAUTION: If you make a change using wr file and you have NOT run the rdfile command first you will delete the original rc file. 

I would reccomend copying the return of the rdfile command to a notepad just in case.

The command to append your changes to the rc file is:     wrfile -a /etc/rc

**Example RC File**

hostname SAN1
vif create multi Prod1 -b ip e0a e0b
ifconfig Prod1 `hostname`-Prod1 mediatype auto netmask 255.255.255.0 partner Prod2
route add default 10.10.20.1 1
routed on
options dns.enable off
options nis.enable off
savecore

**Example command to append an interface configuration to the file

wrfile -a /etc/rc ifconfig e0P 10.10.10.31 netmask 255.255.255.0 mediatype auto

** Example of the rdfile output after running wrfile -a

hostname SAN1
vif create multi Prod1 -b ip e0a e0b
ifconfig Prod1 `hostname`-Prod1 mediatype auto netmask 255.255.255.0 partner Prod2
route add default 10.10.20.1 1
routed on
options dns.enable off
options nis.enable off
savecore
ifconfig e0P 10.10.10.31 netmask 255.255.255.0 mediatype auto




Can't Connect to vCenter After Changing the ESX Service Console IP Address

-------------------------------------------------------------------
GIVE ROOT SSH ACCESS

Connect via VIClient

Create a user and add it to the "wheel" group

Reset Root user password to what it needs to be
-------------------------------------------------------------------
PERMIT ROOT LOGIN

SSH to ESX Host and login as new user
After connecting do the following:

su
(type root password)
vi /etc/ssh/sshd_config        <- This will open a file to be edited
Find the line that says "PermitRootLogin no"
hit the "i" key for insert
cursor to the line and change it to "PermitRootLogin yes"
hit "esc" to exit insert mode
Save your changes type ":wq" and hit enter

(To make canges work you must restart the sshd service)
/etc/init.d/sshd restart
-------------------------------------------------------------------

Packet Capture on a Cisco ASA

*****DEFINE INTERESTING TRAFFIC*********************

For example: The following access-list will capture traffic going to 192.168.25.100 from any source and the second line will capture traffic coming from 192.168.25.100 to any destination.

access-list capture-list extended permit ip any host 192.168.25.100
access-list capture-list extended permit ip host 192.168.25.100 any
*******************************************************


*****START THE CAPTURES*****************************

ASA# capture <name> interface (interface) access-list (access list) buffer (bytes to capture) packet 1522

For example:

ASA# capture incoming-cap interface inside access-list cap-list buffer 1000000 packet 1522
ASA# capture outgoing-cap interface outside access-list cap-list buffer 1000000 packet 1522
*******************************************************


*****GENERATE TRAFFIC*******************************

This can be done by producing any network traffic that falls within the access lilst you created earlier.
******************************************************


*****VIEW CAPTURES*********************************

Show capture incoming-cap
show capture outgoing-cap
******************************************************


*****REMOVE CAPTURES******************************

no capture incoming-cap
no capture outgoing-cap
******************************************************

Wednesday, September 22, 2010

See the Pre-shared key for a VPN Tunnel on a Cisco Device

Ever need to see the tunnel pre-shared key in a show run on a Cisco device?

For example:

tunnel-group VPNACCESS ipsec-attributes
 pre-shared-key *



Run this command: "more system:running-config"

This will start a new show run and you will see what was left out

For Example:
tunnel-group VPNACCESS ipsec-attributes
 pre-shared-key VpnK3yH@sB33nCh@ng3d