7940 stuck on tftp timeout (o/a) !!

Hi,
I have an old 7940, which seems to be stuck on "TFTP timeout o/a".
The o/a is a single control char.
I tried a factory reset, but it does not help.
None of the buttons seem to work.
The screen shows "Universal Application Loader"
The phone gets an IP address, and I can see CDP packets and DHCP requests going out on Wireshark.
The Software version according to CDP packets seems to be P00308000300
Any ideas on how I can revive this phone ?
Thanks

No, because I want to manually configure this phone on a new network.
However, when I re-plugged it back into an existing CM network, it upgraded its firmware, and now it seems ok.
I then plugged it back into a switchport on a standalone switch, and can now access the network settings.
So I guess it was a previous firmware upgrade that failed or soemthing like that....

Similar Messages

7940 TFTP Timeout

Hi everyone,
I enable CCME, but the issue comes when I connect the IP Phone to the router. I can not configure anything in the IP Phone. I press the settings button and nothing.
Only received the following message in the phone:
"TFTP Timeout"
I hope somebody can help me.
Regards,

Thanks, to everything.
In this moment is working again the IP phone.
I've to reset default factory. After that I can edit Networks settigs. Because before I cann't do that.
To reset default you have to press the following in the IP Phone when is restarting:
1234567898*0#
and after that the IP Phone ask to you if you want erase Network settings. Later of that I can manipulate again the IP Phone settings.
Thanks
Edgar E Carreon P

TFTP Timeout in IP Phone.

Hi Friends,
Can any one tell me why IP Phone showing TFTP Timeout.
Regards,
PVR.

7940 SIP loads are somewhat out of scope for SBCS deployments. If you have CUCM server handy, instructions for conversion is below. If this does not work please kindly open a TAC case.
Rgds,
Tomoo
http://www.cisco.com/en/US/products/hw/phones/ps379/products_tech_note09186a0080094584.shtml

TFTP Timeout Error on PXE Boot

Ok this is what happened. I tried to patch a image with windows updates - It filled up my hard drive. So I canceled the process and attempted to remove the folder it created on my hard drive. I went to try pxe boot a machine and I got the
blue screen:
After this I removed the check next to pxe to uninstall WDS and I waited for it to uninstall and reboot. After that I clicked the check box next pxe so it would install everything again. I redistributed the x86 and x64 boot images but now when
I try to pxe boot a machine I get the following in event viewer:
The Following Client failed TFTP Download:
IP *.*.*.*
Filename: SMSBoot\x64\wdsnbp.com
ErrorCode: 1460
I even made added the entry in the registry to change the TFTP block size. I have no idea what to do at this point. I am running Windows Server 2008 R2 and SCCM 2012 SP1. On the client machine I am getting TFTP timeout.

1460 (0x5B4) =ERROR_TIMEOUT
This operation returned because the timeout period expired.
Have you seen this KB?
Operating system deployment over a network by using WDS fails in Windows Server 2008 and in Windows Server 2008 R2
http://support.microsoft.com/kb/975710
For more information, see the following TechNet articles:
WDS TFTP Server:
http://technet.microsoft.com/en-us/library/cc753134(WS.10).aspx
(http://technet.microsoft.com/en-us/library/cc726631(WS.10).aspx)
Network Boot Programs (NBP):
http://technet.microsoft.com/en-us/library/cc753134(WS.10).aspx
(http://technet.microsoft.com/en-us/library/cc753134(WS.10).aspx)
How to Modify the BCD Store Using Bcdedit: http://technet.microsoft.com/en-us/library/cc731245(WS.10).aspx#BKMK_41
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

TFTP timeout message

Running callmanager 8.6.2 and have cisco 7962 and 7961 deploy in one of our site utilizing SCCP however the ssue: currently I'm unable to get my 7962 or 7961 phone to register with cucm. Error message on 7962 phone "TFTP Timeout"
any idea

these are a new 7962 phone that we are peploying remote. the phones are getting
correct IP address address from DHCP
correct TFTP address
however we are getting tftp timeout error
If I go into the options menu and view IPv4 Configuration, it says:
DCHP - Enabled
IP Address - 10.68.44.11
Subnet Mask - 255.255.255.0
Default Router 1,2,3,4,5 are blank
DNS Server 1 - 10.232.0.15
DNS Server 2 - 10.232.0.14
DNS Server 3 - 10.224.95.15
DNS Server 4 - 10.224.96.14
DNS Server 5 - 10.216.0.15
DHCP Server - 10.232.0.46
DHCP Address Released - No
Alternate TFTP - No
TFTP Server - 10.138.244.21
TFTP Server 2 -
BOOTP Server - No
MAC address - 3COE236D5FF3
Host Name - SEP3C0E236D5FF3
Domain Name - Infosolco.net
Operational VLAN ID - 20
Admin. VLAN Id -
SW Port Configuration - Auto Negotiate
PC Port Configuration - Auto Negotiate
PC VLAN -
VPN - Not Connected

7940 Stuck in DND - Site running CCME

Hi,
I have a 7940 at a location running CCME that is stuck in DND mode and I can't find anything to get it to clear. Did the reset of the phone but that didn't clear it.
Any advice would be appreciated.
Phone state:
gandt-5057-vpn>sh ephone dnd
ephone-2 Mac:0021.A0D7.8194 TCP socket:[10] activeLine:0 REGISTERED in SCCP ver 11 and Server in ver 5
mediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0 caps:8
IP:10.204.8.164 49827 Telecaster 7960 keepalive 1750 max_line 6 DnD
button 1: dn 2 number 2012 CH1 IDLE overlay shared
button 6: dn 9 number 2025 CH1 IDLE mwi overlay shared
overlay 1: 2(2012) 17(2012) 1(2011) 16(2011)
overlay 6: 9(2025) 10(2025) 11(2025) 12(2025) 13(2025)

Im having the exact same issue today. I have a user in a remote office with a 7960 saying she cant use her phone and that DND is set and will not remove. She also claims that she just came in and it was like this, she didnt do anything (magic I guess). She is currently set to use template 2.
We are running CME 7.0(0) on a 2811. Im in the process of blowing away her ephone and rebuilding, we will see if that fixes it.
Below is our current ephone templates:
ephone-template 1
softkey idle Redial Newcall
softkey seized Redial Endcall
softkey alerting Callback Endcall
softkey connected Hold Endcall Trnsfer Confrn
features blocked CFwdAll GPickup
conference drop-mode never
conference add-mode all
conference admin: No
max-calls-per-button 8
busy-trigger-per-button 0
privacy default
Always send media packets to this router: No
Preferred codec: g711ulaw
keepalive 30 auxiliary 30
speed-dial 5 919199265175 label Helpdesk
speed-dial 7 919199265175 label Helpdesk
User Locale: US
Network Locale: US
ephone-template 2
softkey idle Redial Newcall Cfwdall
softkey seized Redial Endcall
softkey alerting Callback Endcall
softkey connected Hold Endcall Trnsfer Confrn
features blocked GPickup
conference drop-mode never
conference add-mode all
conference admin: No
max-calls-per-button 8
busy-trigger-per-button 0
privacy default
Always send media packets to this router: No
Preferred codec: g711ulaw
keepalive 30 auxiliary 30
speed-dial 5 919199265175 label Helpdesk
User Locale: US
Network Locale: US
ephone-template 3
softkey idle Redial Newcall Cfwdall
softkey seized Redial Endcall
softkey alerting Callback Endcall
softkey connected Hold Endcall Trnsfer Confrn
features blocked GPickup
conference drop-mode never
conference add-mode all
conference admin: No
max-calls-per-button 8
busy-trigger-per-button 0
privacy default
Always send media packets to this router: No
Preferred codec: g711ulaw
keepalive 30 auxiliary 30
speed-dial 5 919199265175 label Helpdesk
User Locale: US
Network Locale: US

TFTP Timeout

I've install ZenWorks 7 on OES and am trying to do a manual image (Ctrl +
Alt) from a desktop PC.
The desktop picks up an IP address from DHCP and communicates with Novell
Preboot Server, however when it tries to download the linux boot ISO you
get:
PXE-E32: TFTP open timeout
TFTP...
I would appreciate any help,
Andrew.

Andrew wrote:
> I've install ZenWorks 7 on OES and am trying to do a manual image (Ctrl
> + Alt) from a desktop PC.
>
> The desktop picks up an IP address from DHCP and communicates with
> Novell Preboot Server, however when it tries to download the linux boot
> ISO you get:
> PXE-E32: TFTP open timeout
> TFTP...
>
> I would appreciate any help,
> Andrew.
>
OES Netware or linux?

Image recovery on 5520 IDS Module (ASA-SSM-10) TFTP timeout failure

I have an ASA 5520 with an ASA-SSM-10 module in it for IDS. It has (from what I can tell) never been used or configured. In fact, I only recently found that it existed! I would like to begin using it, starting with replacing the software image with the latest (I do NOT need any configuration from it now).
Details ...
KCH-ASA-Primary# sh module 1 details
Getting details from the Service Module, please wait...
ASA 5500 Series Security Services Module-10
Model:              ASA-SSM-10
Hardware version:   1.0
Serial Number:      JAF10422581
Firmware version:   1.0(11)2
Software version:   6.0(1)E1
MAC Address Range: 0018.b91b.69f1 to 0018.b91b.69f1
App. name:          IPS
App. Status:        Up
App. Status Desc:
App. version:       6.0(1)E1
Data plane Status: Up
Status:             Up
Mgmt IP addr:       172.17.1.20
Mgmt web ports:     443
Mgmt TLS enabled:   true
The problem that I am having is that when I set it up to pull down the new software through TFTP, it just hangs and times out.
KCH-ASA-Primary# hw module 1 recover config
Image URL [tftp://10.10.10.9/IPS-sig-S789-req-E4.pkg]:
Port IP Address [172.17.1.20]:
VLAN ID [950]:
Gateway IP Address [172.17.1.1]:
KCH-ASA-Primary#
And then ...
KCH-ASA-Primary# debug module-boot
debug module-boot enabled at level 1
KCH-ASA-Primary# hw module 1 recover boot
The module in slot 1 will be recovered. This may
erase all configuration and all data on that device and
attempt to download a new image for it.
Recover module in slot 1? [confirm]
Recover issued for module in slot 1
KCH-ASA-Primary# Slot-1 215> Cisco Systems ROMMON Version (1.0(11)2) #0: Thu Jan                             26 10:43:08 PST 2006
Slot-1 216> Platform ASA-SSM-10
Slot-1 217> GigabitEthernet0/0
Slot-1 218> Link is UP
Slot-1 219> MAC Address: 0018.b91b.69f1
Slot-1 220> ROMMON Variable Settings:
Slot-1 221>   ADDRESS=172.17.1.20
Slot-1 222>   SERVER=10.10.10.9
Slot-1 223>   GATEWAY=172.17.1.1
Slot-1 224>   PORT=GigabitEthernet0/0
Slot-1 225>   VLAN=950
Slot-1 226>   IMAGE=IPS-sig-S789-req-E4.pkg
Slot-1 227>   CONFIG=
Slot-1 228>   LINKTIMEOUT=20
Slot-1 229>   PKTTIMEOUT=4
Slot-1 230>   RETRY=20
Slot-1 231> tftp [email protected] via 172.17.1.1
KCH-ASA-Primary# Slot-1 232> TFTP failure: Packet verify failed after 20 retries
Slot-1 233> Rebooting due to Autoboot error ...
Slot-1 234> Rebooting....
I know that I can reach 10.10.10.9 from 172.17.1.x. And this is the present port IP of the device. If I do a 'session1' and ping 10.10.10.9, I get replies. I know my TFTP is working ... I use it for all of my switches for config backups and installing new IOS. And watching my TFTP server window, I am not seeing any connection attempts.
What am I doing wrong here? :-(

Thanks for your response. As I mentioned earlier in my email, I tried 2 different images (IPS-SSC_5-K9-sys-1.1-a-6.2-2-E4.img and IPS-SSM_10-K9-sys-1.1-a-7.1-5-E4.img) without any success. Since there are no packets coming from IPS on the TFTP server, I think the problem is something else.
When I run the "debug cplane 255" command, I see some errors mentioned below:
asa(config)# debug cplane 255
debug cplane enabled at level 255
asa(config)#
cp_connect: Connecting to card 1, socket 3, port 7000
cp_connect: Error - cp_connect() returned -1
cp_check_connection: handle -1, conflicts with connection 1 (-1)
cp_check_connection: handle -1, conflicts with connection 2 (-1)
cp_check_connection: handle -1, conflicts with connection 3 (-1)
cp_update_connection: Error updating connection_id 0
Is this a hardware issue?

TFTP timeout over WAN

I am trying to copy a file on to the flash of a router over the WAN using TFTP. After some time it gets timed out. Even if I try to copy the file using the windows command over the WAN using TFTP it does not complete. Is it that TFTP does not support large file downloads over the WAN?
If I do a debug on the router, i get replies only till the 3rd or 4th block of data. Then, only the requests are send. I used two different TFTP servers suspecting an issue with TFTP. The router was Cisco 1841 and the link 512Kbps. The IOS file size 22MB.

Hi,
If I recall going way back a few years ago, I tried something very similar with a Allied Telesis TFTP server software on my PC trying to upgrade IOS on a remote router.
Wireshark indicated that my PC was actually at fault and not streaming the UDP traffic to the router. The UDP stream just stopped, go figure :-)
My resolution was to try another freeware TFTP server, in my case it was the freeware 3COM TFTP server, and all worked ok. Wireshark capture confirmed that the new server streamed fine to the remote router.
So what i got out of that experience was;
1. I learnt how to use wireshark.
2. replaced my old faithful TFTP server software and try another TFTP package and try the upgrade again.
regards Dave

Flashing 7940 phone

Hi all,
I've read loads of posts about this but none that actually give me a solution. I'd really appreciate some expert advice!
I have a cisco 7940 phone, I need to flash firmware to sip. The phone came with a strange firmware that renders all the keys locked. I can reset to factory defaults, but the settings button doesn't work at all. So I don't know what firmware it's running.
I've connected it to tftp server with dhcp and it says 'tftp timeout' or sometimes 'tftp error'. I've tried a few sip firmware versions, all cause same error.
Can anyone help me flash this crazy phone?
Many thanks!

Yes, it should be possible.
Try **#, and see if it unlocks anything at all?
My guess is, when the phone was previously connected to the CCM Server, it was in a "Locked Down" config mode, hence nothing is visible.
Secondly, if that is the case, the only option is to update it with a default config file (and getting the old config erased).
Can you install CCM Server (in a VMWare Wkstn) on your MAC? If yes, then, there would another challenge, how to get the phone be able to talk to the CCM Server on a VM Wkstn on your MAC.. and if that can be done, you should be good :-)
HTH

SCCM 2012R2 OSD PXE-boot-smstftp .var file download times out errorcode 0x00000001- at this point: "Preparing Network" and Reboots

Hello All,
Please I need help! I have not seen the above error without relationship to two of the known causes for sometime during a Windows 7 osd in an SCCM 2012 R2 environment with a remote DP/PXE server. I understand this error: to occur when the boot images
does not have "Network drivers in the past Winpe version ( i.e. 3.0, 4.0), not Winpe 5.0 which has all the Network and storage drivers for Windows 7" or when Port fast is not enabled on the switch port the pxe device is plugged into. These two causes
stated here have been verified and confirmed not to be the cause in this case within the environment. The PXE boot device has ip-address (verified using ip-config, diskpart as well reveals the disk is online) and can ping the wds/pxe server and the sccm server.
Port fast is enabled on the switch port the device is plugged into. I am stuck on this one; as I could not ascertain the cause on this occasion.
Please see details below and I welcome any help any body can offer, thanks in advance guys!
Client – Winpe x64
Server - Windows Server 2008 R2 configured as a PXE / WDS / SCCM DP
Network - both devices on the same subnet
Problem: Client performs PXE boot, downloads Winpe without problems. Client then tries to download .var file. This is not successful and TFTP timeout is received. Error code in
smsts.log states:
<![LOG[Executing: X:\sms\bin\x64\smstftp.exe -i PXE-Server get \SMSTemp\2014.07.01.14.09.09.0001.{46173825-3EDA-4352-8947-3549830D77A7}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:13:57.285+480"
date="07-01-2014" component="TSPxe" context="" type="0" thread="376" file="tspxe.cpp:177">
<![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="14:13:57.332+480" date="07-01-2014" component="TSPxe" context="" type="0"
thread="376" file="commandline.cpp:228">
<![LOG[Set command line: "X:\sms\bin\x64\smstftp.exe" -i PXE-Server get \SMSTemp\2014.07.01.14.09.09.0001.{46173825-3EDA-4352-8947-3549830D77A7}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:13:57.332+480"
date="07-01-2014" component="TSPxe" context="" type="0" thread="376" file="commandline.cpp:731">
<![LOG[Executing command line: "X:\sms\bin\x64\smstftp.exe" -i PXE-Server get \SMSTemp\2014.07.01.14.09.09.0001.{46173825-3EDA-4352-8947-3549830D77A7}.boot.var X:\sms\data\variables.dat]LOG]!><time="14:13:57.332+480"
date="07-01-2014" component="TSPxe" context="" type="1" thread="376" file="commandline.cpp:827">
<![LOG[Process completed with exit code 1]LOG]!><time="14:14:45.379+480" date="07-01-2014" component="TSPxe" context="" type="1" thread="376"
file="commandline.cpp:1123">
Network trace is detailed below:
324994 11:47:35 04/07/2014        166.7634594
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:320, UDP:319, IPv4:72}
325069 11:47:36 04/07/2014        167.7554047       svchost.exe        Client Server
TFTP      TFTP: Read Request - File: \SMSTemp\2014.07.03.15.45.31.0001.{549002A3-C9C9-4189-8AFE-9F8B272BECC1}.boot.var, Transfer Mode: octet
{UDP:321, IPv4:72}
325070 11:47:36 04/07/2014        167.7556504
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:320, UDP:319, IPv4:72}
325071 11:47:36 04/07/2014        167.7598345
Server Client TFTP      TFTP: Data - Block Number: 1                {UDP:322, IPv4:72}
325072 11:47:36 04/07/2014        167.7607151
Client Server TFTP      TFTP: Acknowledgement - Block Number: 1          {UDP:322, IPv4:72}
325073 11:47:36 04/07/2014        167.7608240
Server Client TFTP      TFTP: Data - Block Number: 2                {UDP:322, IPv4:72}
325074 11:47:36 04/07/2014        167.7615948
Client Server TFTP      TFTP: Acknowledgement - Block Number: 2          {UDP:322, IPv4:72}
325075 11:47:36 04/07/2014        167.7616991
Server Client TFTP      TFTP: Data - Block Number: 3                {UDP:322, IPv4:72}
325076 11:47:36 04/07/2014        167.7624602
Client Server TFTP      TFTP: Acknowledgement - Block Number: 3          {UDP:322, IPv4:72}
325077 11:47:36 04/07/2014        167.7625635
Server Client TFTP      TFTP: Data - Block Number: 4                {UDP:322, IPv4:72}
325078 11:47:36 04/07/2014        167.7629426
Client Server TFTP      TFTP: Acknowledgement - Block Number: 4          {UDP:322, IPv4:72}
325079 11:47:36 04/07/2014        167.7630452
Server Client TFTP      TFTP: Data - Block Number: 5                {UDP:322, IPv4:72}
325080 11:47:36 04/07/2014        167.7637927
Client Server TFTP      TFTP: Acknowledgement - Block Number: 5          {UDP:322, IPv4:72}
325081 11:47:36 04/07/2014        167.7638947
Server Client TFTP      TFTP: Data - Block Number: 6                {UDP:322, IPv4:72}
325082 11:47:36 04/07/2014        167.7643324
Client Server TFTP      TFTP: Acknowledgement - Block Number: 6          {UDP:322, IPv4:72}
325083 11:47:36 04/07/2014        167.7644367
Server Client TFTP      TFTP: Data - Block Number: 7                {UDP:322, IPv4:72}
325084 11:47:36 04/07/2014        167.7652140
Client Server TFTP      TFTP: Acknowledgement - Block Number: 7          {UDP:322, IPv4:72}
325085 11:47:36 04/07/2014        167.7653183
Server Client TFTP      TFTP: Data - Block Number: 8                {UDP:322, IPv4:72}
325086 11:47:36 04/07/2014        167.7660907
Client Server TFTP      TFTP: Acknowledgement - Block Number: 8          {UDP:322, IPv4:72}
325087 11:47:36 04/07/2014        167.7661940
Server Client TFTP      TFTP: Data - Block Number: 9                {UDP:322, IPv4:72}
325088 11:47:36 04/07/2014        167.7669372
Client Server TFTP      TFTP: Acknowledgement - Block Number: 9          {UDP:322, IPv4:72}
325089 11:47:36 04/07/2014        167.7670323
Server Client TFTP      TFTP: Data - Block Number: 10                {UDP:322, IPv4:72}
325090 11:47:36 04/07/2014        167.7674067
Client Server TFTP      TFTP: Acknowledgement - Block Number: 10        {UDP:322, IPv4:72}
325091 11:47:36 04/07/2014        167.7674809
Server Client TFTP      TFTP: Data - Block Number: 11                {UDP:322, IPv4:72}
325092 11:47:36 04/07/2014        167.7681308
Client Server TFTP      TFTP: Acknowledgement - Block Number: 11        {UDP:322, IPv4:72}
325093 11:47:36 04/07/2014        167.7682056
Server Client TFTP      TFTP: Data - Block Number: 12                {UDP:322, IPv4:72}
325094 11:47:36 04/07/2014        167.7685383
Client Server TFTP      TFTP: Acknowledgement - Block Number: 12        {UDP:322, IPv4:72}
325095 11:47:36 04/07/2014        167.7686108
Server Client TFTP      TFTP: Data - Block Number: 13                {UDP:322, IPv4:72}
325096 11:47:36 04/07/2014        167.7692475
Client Server TFTP      TFTP: Acknowledgement - Block Number: 13        {UDP:322, IPv4:72}
325097 11:47:36 04/07/2014        167.7693216
Server Client TFTP      TFTP: Data - Block Number: 14                {UDP:322, IPv4:72}
325098 11:47:36 04/07/2014        167.7696477
Client Server TFTP      TFTP: Acknowledgement - Block Number: 14        {UDP:322, IPv4:72}
325099 11:47:36 04/07/2014        167.7697202
Server Client TFTP      TFTP: Data - Block Number: 15                {UDP:322, IPv4:72}
325100 11:47:36 04/07/2014        167.7703651
Client Server TFTP      TFTP: Acknowledgement - Block Number: 15        {UDP:322, IPv4:72}
325101 11:47:36 04/07/2014        167.7704386
Server Client TFTP      TFTP: Data - Block Number: 16                {UDP:322, IPv4:72}
325102 11:47:36 04/07/2014        167.7707479
Client Server TFTP      TFTP: Acknowledgement - Block Number: 16        {UDP:322, IPv4:72}
325103 11:47:36 04/07/2014        167.7708214
Server Client TFTP      TFTP: Data - Block Number: 17                {UDP:322, IPv4:72}
325104 11:47:36 04/07/2014        167.7714862
Client Server TFTP      TFTP: Acknowledgement - Block Number: 17        {UDP:322, IPv4:72}
325105 11:47:36 04/07/2014        167.7715603
Server Client TFTP      TFTP: Data - Block Number: 18                {UDP:322, IPv4:72}
325106 11:47:36 04/07/2014        167.7718715
Client Server TFTP      TFTP: Acknowledgement - Block Number: 18        {UDP:322, IPv4:72}
325107 11:47:36 04/07/2014        167.7719450
Server Client TFTP      TFTP: Data - Block Number: 19                {UDP:322, IPv4:72}
325108 11:47:36 04/07/2014        167.7726029
Client Server TFTP      TFTP: Acknowledgement - Block Number: 19        {UDP:322, IPv4:72}
325109 11:47:36 04/07/2014        167.7726800
Server Client TFTP      TFTP: Data - Block Number: 20                {UDP:322, IPv4:72}
325110 11:47:36 04/07/2014        167.7733471
Client Server TFTP      TFTP: Acknowledgement - Block Number: 20        {UDP:322, IPv4:72}
325111 11:47:36 04/07/2014        167.7734203
Server Client TFTP      TFTP: Data - Block Number: 21                {UDP:322, IPv4:72}
325112 11:47:36 04/07/2014        167.7737411
Client Server TFTP      TFTP: Acknowledgement - Block Number: 21        {UDP:322, IPv4:72}
325113 11:47:36 04/07/2014        167.7738142
Server Client TFTP      TFTP: Data - Block Number: 22                {UDP:322, IPv4:72}
325114 11:47:36 04/07/2014        167.7744648
Client Server TFTP      TFTP: Acknowledgement - Block Number: 22        {UDP:322, IPv4:72}
325115 11:47:36 04/07/2014        167.7745386
Server Client TFTP      TFTP: Data - Block Number: 23                {UDP:322, IPv4:72}
325116 11:47:36 04/07/2014        167.7748657
Client Server TFTP      TFTP: Acknowledgement - Block Number: 23        {UDP:322, IPv4:72}
325117 11:47:36 04/07/2014        167.7749395
Server Client TFTP      TFTP: Data - Block Number: 24                {UDP:322, IPv4:72}
325118 11:47:36 04/07/2014        167.7755914
Client Server TFTP      TFTP: Acknowledgement - Block Number: 24        {UDP:322, IPv4:72}
325119 11:47:36 04/07/2014        167.7756649
Server Client TFTP      TFTP: Data - Block Number: 25                {UDP:322, IPv4:72}
325120 11:47:36 04/07/2014        167.7760109
Client Server TFTP      TFTP: Acknowledgement - Block Number: 25        {UDP:322, IPv4:72}
325277 11:47:37 04/07/2014        168.7554246
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:320, UDP:319, IPv4:72}
325278 11:47:37 04/07/2014        168.7709396
Client Server TFTP      TFTP: Acknowledgement - Block Number: 25        {UDP:322, IPv4:72}
325397 11:47:39 04/07/2014        170.7708892
Client Server TFTP      TFTP: Acknowledgement - Block Number: 25        {UDP:322, IPv4:72}
326185 11:47:40 04/07/2014        171.7552905
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:320, UDP:319, IPv4:72}
327030 11:47:43 04/07/2014        174.7588879
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
327031 11:47:43 04/07/2014        174.7707730
Client Server TFTP      TFTP: Acknowledgement - Block Number: 25        {UDP:322, IPv4:72}
327178 11:47:44 04/07/2014        175.7552028
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
327510 11:47:45 04/07/2014        176.7551962
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
328598 11:47:48 04/07/2014        179.7552497
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
328630 11:47:51 04/07/2014        182.7551309
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
328631 11:47:51 04/07/2014        182.7707620
Client Server TFTP      TFTP: Acknowledgement - Block Number: 25        {UDP:322, IPv4:72}
328658 11:47:54 04/07/2014        185.7550375
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
328669 11:47:57 04/07/2014        188.7709719
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
328677 11:47:59 04/07/2014        190.7862445
Client Server TFTP      TFTP: Acknowledgement - Block Number: 25        {UDP:322, IPv4:72}
328690 11:48:00 04/07/2014        191.7708666
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
328717 11:48:03 04/07/2014        194.7706918
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
328730 11:48:06 04/07/2014        197.7704623
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
328736 11:48:07 04/07/2014        198.7861669
Client Server TFTP      TFTP: Acknowledgement - Block Number: 25        {UDP:322, IPv4:72}
329217 11:48:09 04/07/2014        200.7705229
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
329420 11:48:12 04/07/2014        203.7704633
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
329795 11:48:15 04/07/2014        206.7704298
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
329796 11:48:15 04/07/2014        206.7858646
Client Server TFTP      TFTP: Acknowledgement - Block Number: 25        {UDP:322, IPv4:72}
329990 11:48:18 04/07/2014        209.7704360
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
330005 11:48:21 04/07/2014        212.7703291
Client Server AuthIP AuthIP:version 1.0, Main Mode, Initiator, First Exchange with Unknown peer SPN, Initiator provide proposal Anonymous for negotiation ,Payloads = HDR, CRYPTO, SA, AUTH, Ni, VID, KE, NAT-D, Flags = ..., Length =
440       {AuthIP:419, UDP:319, IPv4:72}
330014 11:48:23 04/07/2014        214.7862410
Client Server TFTP      TFTP: Error - ErrorCode: 0, ErrorMessage: timeout on receive           {UDP:322, IPv4:72}

Hi,
According to the logs, this issue still should be related to network driver. It failed after network driver initialized. Please try to use another network driver.
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

CUCM 8.6.2 Phones not registering 7841 and 8831

Hi all
I am trying to register some new phones - 7841 and 8831. We installed the COP and Device Pack and rebooted the cluster. Firmware defaults in the server are sip78xx.10-1-1SR2-1 and sip8831.9-3-3-5.
These are the first phones of these models that we are trying to use. All other devices are up and working. I added the phones manually, auto-reg is disabled. These new phones are both displaying the same behavior - they booted, but neither device will register. They are both running the the same firmware version configured as the default in the server.
I have looked at some other discussions but haven't seen any solutions that match up with our issue. Your input and ideas appreciated, thanks

I'm having this same problem. Over the weekend, I installed the latest device packs and restarted both servers in the cluster. I'm running CUCM 8.6.2 and the phones are 8831.
What's really strange is that the phone is getting incorrect info from the switch port. It's getting a DHCP address from the VLAN2 subnet, when it should be receiving an IP from the VLAN100 subnet.
VLAN2 = Data
VLAN100 = Voice
The original port config:
interface FastEthernet0/25
description Workstations on VLAN2 - Phones on VLAN 100
switchport access vlan 2
switchport trunk encapsulation dot1q
switchport trunk native vlan 2
switchport mode trunk
switchport voice vlan 100
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
mls qos trust device cisco-phone
mls qos trust cos
auto qos voip cisco-phone
spanning-tree portfast
end
I even changed the switch port configuration to this:
interface FastEthernet0/25
description Workstations on VLAN2 - Phones on VLAN 100
switchport access vlan 100
switchport trunk encapsulation dot1q
switchport trunk native vlan 100
switchport mode trunk
switchport voice vlan 100
srr-queue bandwidth share 10 10 60 20
srr-queue bandwidth shape 10 0 0 0
mls qos trust device cisco-phone
mls qos trust cos
auto qos voip cisco-phone
spanning-tree portfast
end
VLAN 2 isn't even in the configuration, but the phone (even after a RESET) is still getting an IP from the DHCP server on VLAN2.
Very strange behavior.
Additional info:
The phone status menu is showing a continuous message of:
TFTP Timeout : SEPXXXXXXXXXXXX.cnf.xm.
No Trust List Installed.
Any suggestions / ideas would be appreciated.

AIR-CAP3602E-E-K9 can not download autonomous IOS image ?!

Hi all.
AIR-CAP3602E can not connect to tftp after format flash. Flash has been erased to free space for autonomous IOS.
When I reset it using mode button , I've got this on the console screen :
IOS Bootloader - Starting system.
flash is writable
FLASH CHIP: Macronix Mirrorbit (00C2)
Xmodem file system is available.
flashfs[0]: 1 files, 1 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 31997952
flashfs[0]: Bytes used: 1536
flashfs[0]: Bytes available: 31996416
flashfs[0]: flashfs fsck took 11 seconds.
Reading cookie from SEEPROM
Base Ethernet MAC address: 7c:ad:74:xx:xx:xx
Ethernet speed is 100 Mb - FULL Duplex
Mode button pressed.
Mode button held for at least 20 seconds.
process_config_recovery: set IP address and config to default 10.0.0.1
process_config_recovery: image recovery
image_recovery: Download default IOS tar image tftp://255.255.255.255/ap3g2-k9w7-tar.default
examining image...
DPAA Set for Independent Mode
DPAA_INIT = 0x0
%Error opening tftp://255.255.255.255/ap3g2-k9w7-tar.default (connection timed out)
issuing command arp I see only this
ap: arp
     255.255.255.255 ff:ff:ff:ff:ff:ff 0 25
configuring it manually :
ap: set
    DEFAULT_ROUTER=10.0.0.1
    IP_ADDR=10.0.0.1
    NETMASK=255.255.255.224
ap: ether_init
    Initializing ethernet port 0...
    Ethernet speed is 100 Mb - FULL Duplex
ap: tftp_init
ap: flash_init
     Initializing Flash...
     ...The flash is already initialized.
ap: tar -xtract tftp://10.0.0.2/ap3g2-k9w7-tar.default Flash:
and I've got this:
extracting info (285 bytes)Flash:/info: permission denied
Then I tried arp again
ap: arp
     255.255.255.255 ff:ff:ff:ff:ff:ff 0 299
           10.0.0.2 00:1f:c6:xx:xx:xx 0 299
ap:
This is the TFTP log:
===============================================
TFTP log
Connection received from 10.0.0.1 on port 1025 [01/02 19:18:03.631]
Read request for file <ap3g2-k9w7-tar.default>. Mode octet [01/02 19:18:03.631]
Using local port 52999 [01/02 19:18:03.633]
TIMEOUT waiting for Ack block #1 [01/02 19:18:18.647]
===============================================
Tftp timeout is set to 30 s
Thanks in advance for any help

What TFTP server are you using? Try either 3CDeamon or TFTPd32. Also make sure the MD5 has matches for the image you download. This will verify the image is indeed good.
Sent from Cisco Technical Support iPhone App

Connectivity issues for random phones in CUCM 8.6 on Vmware

I have a client that has problems with around half of there ip phones (6921 & 7945) after a situation with overheating in the serverroom.
The solutions was a 1 Publisher, 1 subscriber setup with each on a separate Vmware server.
The Publisher is connected to the Core Switch which is further connected to 4 distribution switches which again connect to 5 more distribution switches. They have around 200 ip phones connected to these switches that get assigned IP's with DHCP.
The physical disk that the Subscriber was on was destroyed the incident. The Publisher they recovered, but to do this they had to recreate the vm descriptor file and attach it to the flat-file.
So the current situation is that the system is running with only 1 Publisher and no Subscriber.
There is also a license warning in the CCM Admin section, stating a License Overage (2 nodes used, but only 1 licensed.)
The license status is not invalid though, and the license state is "Uploaded". This second node I suppose might be the Subscirber that no longer exists? The phones have more than enough licenses.
When powered up the system seems to run as it should, but only about half the phones have connectivity to and can register with CUCM.
I have tried to reboot some phones remotely by cutting the power on the switch interfaces where they are attached, but that made no difference.
The console log on the phones that are down show TFTP Timeout & File Transfer Error.
The phones that are up and running can be pinged successfully from the CUCM cli, but when pinging the others I get "Destination Host Unreachable".
The strange thing is that it seems completely random as to what phones are up or down. On all switches there are connected phones with both working and non-working connections to CUCM.
To try to pinpoint the fault I chose 2 devices on the same switch and compared the config for each interface, one that has connectivity and is registered, and one that does not have connectivity and is unreachable.
Everything seems to be identical so I can't see what causes this error on the one, but not on the other.
Also when I ping the ip phone with no connectivity to CUCM from any of the switches, the ping is successful.
Anyone know what could be the cause of this behaviour?

Hello and thank you for your time.
The phones get there IP’s from a DHCP Server (Not the built in one in CUCM, but an external server). I have tested that the DHCP process works by powering off a phone (one of the phones with connectivity issues), deleting the lease, and then powering the phone back on and seeing the device request and receive a new lease.
There is only one CCM group active and both servers are in this group with the Publisher as highest priority server. All phones are in the same Device Pool attached to this group.
There are a lot of warnings regarding dbReplication & missing node due to the subscriber being gone. Also there is an issue with NTP server (see below). I will post more on this tomorrow morning.
I have also attached the console log from one of the phones that can't register.
NTP Alert:
At Tue Jan 13 21:24:10 BRST 2015 on node 192.168.50.2; the following SyslogSeverityMatchFound events generated: SeverityMatch : Critical MatchedEvent : Jan 13 21:23:49 CUCMPUB user 2 ntpRunningStatus.sh: Primary node NTP server; 192.168.50.6; is currently inaccessible or down. Verify the network between the primary and secondary nodes. Check the status of NTP on both the primary and secondary nodes via CLI 'utils ntp status'. If the network is fine; try restarting NTP using CLI 'utils ntp restart'. AppID : Cisco Syslog Agent ClusterID : NodeID : CUCMPUB TimeStamp : Tue Jan 13 21:23:49 BRST 2015 SeverityMatch : Critical MatchedEvent : Jan 13 21:23:53 CUCMPUB user 2 ntpRunningStatus.sh: The local NTP client is off by more than the acceptable threshold of 3 seconds from its remote NTP system peer. The normal remedy is for NTP Watch Dog to automatically restart NTP. However; an unusual number of automatic NTP restarts have already occurred on this node. No additional automatic NTP restarts will be done until NTP time synchronization stabilizes. This is likely due to an excessive number of VMware Virtual Machine migrations or Storage VMotions. Please consult your VMware Infrastructure Support Team. AppID : Cisco Syslog Agent ClusterID : NodeID : CUCMPUB TimeStamp : Tue Jan 13 21:23:53 BRST 2015

NAT overload is not working when i configure Double NAT for VPN

I have Cisco 2921 router with OS version 15.1(4)M1.
the router is configured for NAT overload and working fine, i have site to site VPN tunnel with peer with normal NAT translation. now we need to configure Double NAT on the VPN tunnel as we need to free the subnet on peer network. for double nat i use 3.2.21.x - 3.2.23.x / 24 network and apply following command
Double NAT translation
ip nat inside source static network 192.168.10.0 3.2.21.0 /24 no-alias
ip nat inside source static network 192.168.20.0 3.2.22.0/24 no-alias
ip nat inside source static network 192.168.30.0 3.2.23.0 /24 no-alias
Nonat
access-list 101 deny   ip 3.2.21.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 101 deny   ip 3.2.22.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 101 deny   ip 3.2.23.0 0.0.0.255 3.2.1.0 0.0.0.255
VPN encrypted traffic over the tunnel
access-list 115 permit ip 3.2.21.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 115 permit ip 3.2.22.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 115 permit ip 3.2.23.0 0.0.0.255 3.2.1.0 0.0.0.255
Problem:
as soon as i apply Double NAT translation command the NAT overload stop working and client cannot reach to the internet
the router partial configuration is as below
REACH-R01(config)#do sh run
Building configuration...
Current configuration : 19233 bytes
! Last configuration change at 09:56:45 MST Tue Jan 29 2013 by admin
! NVRAM config last updated at 13:57:54 MST Wed Jan 30 2013
! NVRAM config last updated at 13:57:54 MST Wed Jan 30 2013
version 15.1
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
hostname REACH-R01
boot-start-marker
boot-end-marker
card type t1 0 0
logging buffered 51200 warnings
no aaa new-model
clock timezone MST -7 0
clock summer-time MST recurring
network-clock-participate wic 0
network-clock-select 1 T1 0/0/0
no ipv6 cef
ip source-route
ip cef
ip dhcp excluded-address 192.168.20.1 192.168.20.99
ip dhcp excluded-address 192.168.20.250 192.168.20.255
ip dhcp pool CISCO_PHONES
network 192.168.20.0 255.255.255.0
default-router 192.168.20.254
option 150 ip 192.168.20.254
no ip domain lookup
ip domain name reach.local
ip inspect name ethernetin ftp timeout 3600
ip inspect name ethernetin h323 timeout 3600
ip inspect name ethernetin http timeout 3600
ip inspect name ethernetin rcmd timeout 3600
ip inspect name ethernetin realaudio timeout 3600
ip inspect name ethernetin smtp timeout 3600
ip inspect name ethernetin sqlnet timeout 3600
ip inspect name ethernetin streamworks timeout 3600
ip inspect name ethernetin tcp timeout 3600
ip inspect name ethernetin tftp timeout 30
ip inspect name ethernetin udp timeout 15
ip inspect name ethernetin vdolive timeout 3600
multilink bundle-name authenticated
isdn switch-type primary-ni
trunk group PRI
crypto pki token default removal timeout 0
crypto pki trustpoint TP-self-signed-3180627716
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3180627716
revocation-check none
rsakeypair TP-self-signed-3180627716
voice-card 0
dsp services dspfarm
voice service voip
allow-connections sip to sip
fax protocol t38 version 0 ls-redundancy 0 hs-redundancy 0 fallback none
sip
voice translation-rule 1
rule 5 /^7804981231/ /401/
voice translation-rule 2
rule 5 // /7804981231/
voice translation-profile DID_INBOUND
translate called 1
voice translation-profile DID_OUTBOUND
translate calling 2
license udi pid CISCO2911/K9 sn FGL1540114P
license accept end user agreement
license boot module c2900 technology-package securityk9
hw-module ism 0
hw-module pvdm 0/0
username test test
redundancy
controller T1 0/0/0
cablelength long 0db
pri-group timeslots 1-6,24
no ip ftp passive
crypto isakmp policy 10
encr aes 256
authentication pre-share
group 2
crypto isakmp key P@ssw0rd address 33.33.33.33 no-xauth
crypto ipsec transform-set ESP-AES256-SHA esp-aes 256 esp-sha-hmac
crypto map VPN-TUNNEL 1 ipsec-isakmp
description COMPUGEN
set peer 33.33.33.33
set transform-set ESP-AES256-SHA
match address 115
interface Embedded-Service-Engine0/0
no ip address
shutdown
interface GigabitEthernet0/0
description Outside Interface To the Internet
ip address dhcp
ip access-group outside_access_in in
ip nat outside
ip virtual-reassembly in
duplex auto
speed auto
crypto map VPN-TUNNEL
interface ISM0/0
ip unnumbered GigabitEthernet0/1.20
service-module ip address 192.168.20.2 255.255.255.0
!Application: CUE Running on ISM
service-module ip default-gateway 192.168.20.254
interface GigabitEthernet0/1
no ip address
ip nat inside
ip virtual-reassembly in
duplex auto
speed auto
interface GigabitEthernet0/1.10
description VLAN 10 DATA VLAN
encapsulation dot1Q 10
ip address 192.168.10.254 255.255.255.0
ip nat inside
ip inspect ethernetin in
ip virtual-reassembly in
interface GigabitEthernet0/1.20
description VLAN 20 VOICE VLAN
encapsulation dot1Q 20
ip address 192.168.20.254 255.255.255.0
ip nat inside
ip virtual-reassembly in
interface GigabitEthernet0/1.30
description VLAN 30 WIRELESS VLAN
encapsulation dot1Q 30
ip address 192.168.30.254 255.255.255.0
ip nat inside
ip inspect ethernetin in
ip virtual-reassembly in
interface GigabitEthernet0/2
no ip address
shutdown
duplex auto
speed auto
interface ISM0/1
description Internal switch interface connected to Internal Service Module
no ip address
interface Serial0/0/0:23
no ip address
encapsulation hdlc
isdn switch-type primary-ni
isdn incoming-voice voice
trunk-group PRI
no cdp enable
interface Vlan1
no ip address
ip forward-protocol nd
ip http server
ip http access-class 23
ip http authentication local
ip http secure-server
ip http timeout-policy idle 60 life 86400 requests 10000
ip http path flash:CME8.6/GUI
ip nat inside source static tcp 192.168.10.10 443 interface GigabitEthernet0/0 443
ip nat inside source static tcp 192.168.10.10 25 interface GigabitEthernet0/0 25
ip nat inside source static tcp 192.168.10.10 1723 interface GigabitEthernet0/0 1723
ip nat inside source static tcp 192.168.10.10 3389 interface GigabitEthernet0/0 3389
ip nat inside source static tcp 192.168.10.10 123 interface GigabitEthernet0/0 123
ip nat inside source static tcp 192.168.10.10 987 interface GigabitEthernet0/0 987
ip nat inside source list 101 interface GigabitEthernet0/0 overload
ip route 0.0.0.0 0.0.0.0 GigabitEthernet0/0 75.152.248.1
ip route 0.0.0.0 0.0.0.0 75.152.248.1 254
ip route 0.0.0.0 0.0.0.0 205.206.0.1 254
ip route 192.168.20.2 255.255.255.255 ISM0/0
ip access-list extended outside_access_in
permit udp any any eq bootps
permit udp any any eq bootpc
permit tcp any host 22.22.22.22 eq 1723
permit tcp any host 22.22.22.22 eq 3389
permit tcp any host 22.22.22.22 eq smtp
permit tcp any host 22.22.22.22 eq 443
permit tcp any host 22.22.22.22 eq domain
permit udp any host 22.22.22.22 eq domain
permit tcp any host 22.22.22.22 eq 123
permit icmp any host 22.22.22.22 unreachable
permit icmp any host 22.22.22.22 echo-reply
permit icmp any host 22.22.22.22 packet-too-big
permit icmp any host 22.22.22.22 time-exceeded
permit icmp any host 22.22.22.22 traceroute
permit icmp any host 22.22.22.22 administratively-prohibited
permit icmp any host 22.22.22.22 echo
permit tcp any host 22.22.22.22 eq 987
permit tcp any host 22.22.22.22 eq 47
permit gre any host 22.22.22.22
permit udp any host 22.22.22.22 eq isakmp
permit esp any host 22.22.22.22
access-list 23 permit any
access-list 101 deny   ip 192.168.20.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 101 deny   ip 192.168.30.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 101 deny   ip 192.168.10.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 101 deny   ip 3.2.21.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 101 deny   ip 3.2.22.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 101 deny   ip 3.2.23.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 101 permit ip 192.168.10.0 0.0.0.255 any
access-list 101 permit ip 192.168.20.0 0.0.0.255 any
access-list 101 permit ip 192.168.30.0 0.0.0.255 any
access-list 110 permit ip 0.0.0.0 255.255.255.0 0.0.0.0 255.255.255.0
access-list 115 permit ip 3.2.21.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 115 permit ip 3.2.22.0 0.0.0.255 3.2.1.0 0.0.0.255
access-list 115 permit ip 3.2.23.0 0.0.0.255 3.2.1.0 0.0.0.255
Solution: Support forums team

I have the same problem also. Restarting isn't helping and the auto lock/unlock button is on. Plus a couple of time when I turn it on it is asking if I want to power off. That is when I push the button on the front to wake it up. Not the power button on top. I have an IPAd 2. Worked fine before the update.

7940 stuck on tftp timeout (o/a) !!

Similar Messages

Maybe you are looking for