Cisco PIX Device Manager Version 3.0(2)

Hi
I have a PIX 515E:
Cisco PIX Firewall Version 6.3(4)
Cisco PIX Device Manager Version 3.0(2)
Compiled on Fri 02-Jul-04 00:07 by morlee
CCP-Firewall001 up 2 years 65 days
Hardware: PIX-515E, 32 MB RAM, CPU Pentium II 433 MHz
Flash E28F128J3 @ 0x300, 16MB
BIOS Flash AM29F400B @ 0xfffd8000, 32KB
0: ethernet0: address is 0012.80be.450d, irq 10
1: ethernet1: address is 0012.80be.450e, irq 11
Licensed Features:
Failover: Disabled
VPN-DES: Enabled
VPN-3DES-AES: Disabled
Maximum Physical Interfaces: 3
Maximum Interfaces: 5
Cut-through Proxy: Enabled
Guards: Enabled
URL-filtering: Enabled
Inside Hosts: Unlimited
<--- More ---> Throughput: Unlimited
IKE peers: Unlimited
This PIX has a Restricted (R) license.
Serial Number: 808480455 (0x30306ec7)
Running Activation Key: 0xac646fed 0xf8b86795 0xc3951ec2 0xb32aed09
It's operate with Java plug in 1.4.1 y I have a PC with IE 7 and Plug in 1.6.0 y doesn't download the PDM.
Are there a solution for it?

Try Disable Java on Internet Options. This issue oculd be releated to Java version also.

Similar Messages

Cisco View Device Manager

Hi,
is there anybody who can tell me how to bring the Cisco View Device manager for 6500er up? I've installed the CVDM V.1.1 in the bootflash of my 6500er, IOS version is 12.2(18)SXF4 enterprise services. Installed java on the client is v.1.4.2_06. After launching the CVDM whithout proxy settings the windows starts gathering information, after a few seconds it stops with an error "java.lang.NullPointerException". This failure appeared with Mozilla 2.0.0.8 and IE 6.0, on the 6500er all vty lines are idle. Is anybody here who can help to solve the problem?

Here the text from the readme file; try to get the zip-file via the Bug-Id:
09-December-2005
This patch provides fix for the following bug:
CSCsc10956 - CVDM 1.1 does not work with 12.2(18)SXF
SUPPORTED IOS VERSION:
12.2(18)SXF
SIZE:
5,593,057 Bytes
DOWNLOADING AND MOVING FILES TO TFTP SERVER:
cvdm-c6500-1.1-CSCsc10956.zip contains the following two files
* cvdm-c6500-1.1.tar and
* cvdm-c6500-1.1_K9.tar (for Cisco IOS Cryptographic software)
Unzip cvdm-c6500-1.1-CSCsc10956.zip and copy one of the tar files to a TFTP server
Make sure to enter filenames exactly as they appear; (filenames are case-sensitive).
TRANSFERRING FILES TO YOUR SWITCH:
Step 1 : Access the switch CLI using a Telnet connection or the console port.
Step 2 : Transfer the files from the TFTP server to the bootflash of the switch. Issue
the following command:
# archive tar /xtract tftp:// / bootflash:
where is the filename of the CVDM-C6500 tar file you want to install
and is the IP address of the TFTP server. Make sure to enter filenames
exactly as they appear (filenames are case-sensitive). Make sure you are not in
configuration mode when issuing the archive command.
Step 3 : If you are not in configuration mode, issue the following command:
# configure terminal
Step 4 : Set HTTP server and path. For example:
# ip http path bootflash:
Please refer cvdm-c6500-1_1_readme.pdf in http://www.cisco.com/cgi-bin/tablebuild.pl/cvdm-6k for
further details on CVDM-C6500.

Cisco Unified Communications Manager Version 8.6(2.24106)

Hi,
Cisco has released a new software update for Cisco Unified Communications Manager Version 8.6 Release Version:8.6(2.24106). I have been trying to find the release notes for bugs/fixes resolved in this version and open caveats but the documentation for this release does not mention them. Any idea what does this release covers ?
Software Updates for Cisco Unified Communications Manager Version 8.6
Product Name :
Cisco Unified Communications Manager Version 8.6
Release Version:
8.6(2.24106)
Alert Type:
New File
File Name:
cmterm-devicepack8.6.2.24106-2.cop.sgn
File Description:
Cisco Unified Communications Manager 8.6(2.24106) Device Package - Compatible UCM Version: 8.6
File Release Date:
10-DEC-2013
Regards
Robin Thomas

Hi Robin,
This is actually a "new" Device Pack for CUCM 8.6(2) rather than
a new CUCM version release. See below
Cisco Unified Communications Manager Device Package 8.6(2)
(24106-2) Release Notes
http://www.cisco.com/web/software/282074299/108461/CiscoUnifiedCommunicationsManagerDevicePackage8.6.2.pdf
The latest CUCM release for 8.6(2) is;
8.6(2a)su3 US Export Restricted - full encryption capabilities (non-bootable) - For upgrade from 8.x+. Upgrades from 6.1(4)+, 7.1(3), 7.1(5) need to be requested via PUT (www.cisco.com/upgrade) or purchased to obtain necessary license
UCSInstall_UCOS_8.6.2.23900-10.sgn.iso
Cheers!
Rob
"When it comes to luck you make your own "
- Springsteen

Does Cisco Fabric/Device Manager 5.0(4d) run under VM?

I'd like to upgrade the OS on our W2k3 to W2K8 64-bit via virtual machine. First, is it possible to run Cisco Fabric and Device Manager under VM 2K8 64-bit? Has there been any issues reported running these tools, on VM?
Thanks

Hello Jayson,
Yes, Cisco Fabric Manager and Nevice Managercan run on W2k3 to W2K8 64-bit VM
http://www.cisco.com/en/US/partner/docs/switches/datacenter/mds9000/sw/5_0/release/notes/fm/fm_rel_notes_504d.html
VMs:
VMs that run any qualified or supported operating system version can run Cisco Fabric Manager.
Thanks

Windows 7 64-bit Cisco Fabric/Device Manager Installer

Does anyone know if there is Cisco Device Manager Installer compatible with Windows 7 (64-bit)? I'm trying to install Device Manager onto my Windows 7 PC. this may happen on my Fabricv Manager Installer, as well. Any help would be appreciated.
Thanks

Senthil, Horacio,
I would not recommend using a 8.5(x) client against a 8.0(x) server (the OP suggests UCCE 8.0 is used). Even though they _should_ be compatible, they usually are not.
Upgrading the server side to 8.5 is the way to go IMHO.
G.

Important Updates Required for CIsco Unified Communications Manager Versions 7.1 - 9.1

Folks,
I recently received an Email our Cisco SE letting us know about a specific security hole in CUCM that I figured that you might be interested in:
As your account team, we wanted to make you aware of an important update to Cisco Unified Communications Manager that addresses a security flaw discovered on June 6th. This flaw, if unpatched, could allow a remote attacker to gain access to your Communications Manager. Cisco has released a Cisco Options Package (COP) file for each of the affected versions to mitigate the vulnerability. The updated COP file, cmterm-CSCuh01051-2.cop.sgn, is available on CCO for download now and is located under the Utilities section of the software downloads page for each of the affected versions.
The full details of this vulnerability can be found in the security advisory page: cisco-sa-20130717-cucm - Multiple Vulnerabilities in Cisco Unified Communications Manager. If you have issues downloading the update file or questions about the vulnerability, please don't hesitate to contact your account team so we can assist in you getting access to this.

Hi Craig,
From the ReadMe;
Installation Instructions:
As with any installation or upgrade, it is recommended that you apply this Update during off peak hours.
When applying this Update be advised that a clusterwide reboot is required.
This update must be installed on all machines in the cluster before the cluster is rebooted.
Installation to all machines in the cluster is required; you must start with the Publisher. After the Update has been applied
to all servers you will need to reboot the entire cluster. See
Rebooting the Cluster for detailed instructions.
This package will install on the following System Versions:
7.1.3.10000
xx or any higher version starting with 7
.1.3.xxxxx
7.1.5.10000
xx or any higher version starting with 7.1.5.xxxxx
8.5.1.10000
xx or any higher version starting with 8.5.1.xxxxx
8.6.2.10000
xx or any higher version starting with 8.6.2.xxxxx
9.1.1.10000
xx or any higher version startin
g with 9.1.1.xxxxx
http://www.cisco.com/web/software/282204704/18582/ReadmeForBlindSQLinjectionCOPfile.pdf
Cheers!
Rob

Adding a cisco pix device to CSM 3.3

I've been trying to add a cisco pix6.3 to a New CSM 3.3 server and it complains that my credentials are bogus, I can log in to the pix's PDM using the same credentials so I'm stumped, Is there a way that I can get a better idea of what is happening under the hood? I tried a debug and the server is clearly hitting the pix and it is responding but no go.
I figured it out, the csm was set to use the users login credentials instead of the device credentials.

Try Disable Java on Internet Options. This issue oculd be releated to Java version also.

Cisco PIX SIP Issue

Hello All,
I am having an issue with running SIP through my Cisco Pix. A VOIP solution has just been installed, and softphones from the outside are trying to call in using SIP and are failing. The configuration is below. and the code is 6.3 (5). You'll see below that I have the no fixup protocol for sip, as the fixup wasn't working either. Is there something that needs to be configured that I'm missing or could this be a bug in the code? Any other show commands or debug commands I can provide if needed. The call manager server in the below config is 1.2.3.4. Thanks in advance for all your help, you guys are always so helpful.
XXXt# show ver
Cisco PIX Firewall Version 6.3(5)
Cisco PIX Device Manager Version 3.0(4)
Compiled on Thu 04-Aug-05 21:40 by morlee
XXX up 1 hour 45 mins
Hardware:   PIX-506E, 32 MB RAM, CPU Pentium II 300 MHz
Flash E28F640J3 @ 0x300, 8MB
BIOS Flash AM29F400B @ 0xfffd8000, 32KB
0: ethernet0: address is 001c.582b.3c65, irq 10
1: ethernet1: address is 001c.582b.3c66, irq 11
Licensed Features:
Failover:                    Disabled
VPN-DES:                     Enabled
VPN-3DES-AES:                Enabled
Maximum Physical Interfaces: 2
Maximum Interfaces:          4
Cut-through Proxy:           Enabled
Guards:                      Enabled
URL-filtering:               Enabled
Inside Hosts:                Unlimited
Throughput:                  Unlimited
IKE peers:                   Unlimited
This PIX has a Restricted (R) license.
XXXt# show run
: Saved
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password vQ0/erypfvYyzFoc encrypted
passwd vQ0/erypfvYyzFoc encrypted
hostname DTPIX35thst
domain-name digitaltransitions.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
no fixup protocol sip 5060
no fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list out_in permit udp any host 1.2.3.4 eq 5060
access-list out_in permit tcp any host 1.2.3.43 eq 5060
pager lines 24
logging on
logging buffered informational
logging trap informational
logging queue 2048
mtu outside 1500
mtu inside 1500
ip address outside 4.34.119.130 255.255.255.248
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool vpn_pool 192.168.100.50-192.168.100.75
pdm location 192.168.1.250 255.255.255.255 inside
pdm location 192.168.1.252 255.255.255.255 inside
pdm location 65.215.8.100 255.255.255.255 inside
pdm location 192.168.100.0 255.255.255.0 outside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list nonat
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) 1.2.3.4 172.20.1.2 netmask 255.255.255.255 0 0
access-group out_in in interface outside
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:00:00 sip_media 0:00:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
aaa authentication ssh console LOCAL
http server enable
http 199.96.104.108 255.255.255.255 outside
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable

Hi Jumora,
No need to troubleshoot this direct issue anymore. The client will be upgrading to an ASA 5505. Is there anything you may know of before I configure the ASA that I need to do to allow SIP through with no issues? Thanks again Jumora

ACE-4710 : Device Manager on Primary ACE cannot authenticate

Hi,
In a cluster of redundant ACE-4710, version A5(1.2), the graphical Device Manager on the primary ACE cannot authenticate users. An error message is displayed :
The strange thing is that the standby ACE Device Manager work correctly. Moreover, both ACE are perfectly synchronized :
CH01AC03/P-115-A# sh ft group summary
FT Group                     : 14
Configured Status            : in-service
Maintenance mode             : MAINT_MODE_OFF
My State                     : FSM_FT_STATE_ACTIVE
My Config Priority           : 200
My Net Priority              : 200
My Preempt                   : Enabled
Peer State                   : FSM_FT_STATE_STANDBY_HOT
Peer Config Priority         : 150
Peer Net Priority            : 150
Peer Preempt                 : Enabled
Peer Id                      : 1
No. of Contexts              : 1
Here is the details on the ACE and DM version :
CH01AC03/P-115-A# sh ver
Cisco Application Control Software (ACSW)
TAC support: http://www.cisco.com/tac
Copyright (c) 1985-2012 by Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at
http://www.gnu.org/licenses/gpl.html.
Software
loader:    Version 0.95.1
system:    Version A5(1.2) [build 3.0(0)A5(1.2) adbuild_19:38:58-2012/01/17_/auto/adbure_nightly4/renumber/rel_a5_1_2_throttle/REL_3_0_0_A5_1_2]
system image file: (hd0,1)/c4710ace-t1k9-mz.A5_1_2.bin
Device Manager version 5.1 (0) 20111215:1009
What coud be the problem ?
Thank you
Yves

Hello Yves,
Try with the command "dm reload" in the Admin Context
Cesar R
ANS Team

Device Manager v4.6 SP5 release date

Hi, Can you tell me when HP Device Manager v4.6 SP5 will be released to support ThinPro v5.2 ? Unable to capture v5.2 ThinPro with v4.6 SP4 Regards

Interesting, I logged a warranty call (case:4651877501) against one of our new T620's and a HP support guy (DSO Team) phoned me back and said there was a known issue with capturing ThinPro v5.2 using HP device manager v4.6 SP5 If I get some free time, I'll try again Regarding imaging from thinpro 4 to 5.2 the readme for the thinpro 5.2 download says:- 'NOTE: You *MUST* install a thinstate update package (hptc-thinstate-ng version 1.10.3 or later) for ThinPro 4.x and Smart Zero Core 4.x and then reboot before using Automatic Update or Easy Update to install a ThinPro 5.x image onto a device running ThinPro 4.x or Smart Zero Core 4.x. Failure to do so will result in a corrupted image on the client device requiring manual reimaging. Deploying an image via HP Device Manager (version 4.6 SP1 or newer) does not require this update.' This implies if your using HP device manager you should be able to re-image a thinpro 4 device to v5.2 direct It is not until you try this in the HP device manager console, that a warning displays :- Deploying an image of ThinPro 5.2 or later to the device(s) will fail, update to ThinPro 5.0 or 5.1 first It would be good if the readme for ThinPro 5.2 download states this Regards

HP Device Manager T610 Update Agent Fails

I am trying to clone an image from a T610 Thin client. I can't update the agent or image. I am using HP Device Manager Version 4.4.3. I get the following log.
2014-01-08 15:17:05 Successfully sent task to the Device Management Gateway
2014-01-08 15:17:09 Task has been retrieved by the Agent.
2014-01-08 15:17:13 Fail to execute task.
2014-01-08 15:17:13 ErrorCode: -1

Hi DavidApx,
Welcome to the HP forum.
I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial product. You can do this at http://h30499.www3.hp.com/hpeb/ .
I hope this helps.
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Using the Security Device Manager?

Has anyone tried the latest SDM? If so, any comments on it and it's usefulness?
I'm thinking about using for one of my customers who for instance likes the Pix Device Manager (3.0.1) GUI that tells you interface status and bw usage on the front page.
It looks like this is similar. Any insight is greatly appreciated.
sm

Yes, you can go ahead and use it. More features are being added and for sure your customer will like it in long run.
Regards,
Ravikumar

Unable to open 2 9509 switches at the same time in Cisco Device Manager

Dear Friends,
There are a pair of MDS 9509 switches whose management addresses are 172.16.2.197 and 172.16.2.198.
When we try to manage these Devices through Cisco device manager, the first device opens up without any problem, but when the second 9509 is opened in Cisco Device Manager, it fails giving the following error message:
"Open udp transport failed: Address already in use: Cannot bind"
To get around this issue, if we close the first interface to the 9509 switch, then we are able to open up the second 9509 in Device Manager.
We have this problem only in Cisco device manager. If we open one switch in Cisco device manager and the other switch in Cisco Fabric Manager, it works.
Also, we can telnet to both the devices successfully at a time.
The device manager in use is 4.1.
Please find enclosed the sh version outputs for your kind reference.
Can you please help me understand the cause of this issue?
Thanks a lot
Gautam

Is it always the same MDS that fails to open, or can you open either one first, and then the second one poses the problem (no matter which one is second)?
Can you try from a second work station and see if you can open DM to both switched at the same time? I suspect the address it is complaining about is the local workstation IP, not the MDS IP.
If you open the FM map, then you click on the MDS ICONs, can you open DM to both MDS?
- Mike

Ask the Expert: Upgrading Cisco Unified Communications Manager (CUCM) to Version 9.1 (Drive to 9)

Welcome to the Cisco Support Community Ask the Expert conversation. Learn from experts Vijay Rao and Amit Singh about simplified upgrade process and focused support from Cisco to migrate to version 9.1.
This is a continuation of the live Webcast
Drive to 9 is a comprehensive and holistic program designed to help you upgrade the current Cisco® Unified Communications Manager installed base to version 9.1 or higher. This upgrade will enable customers to have next-generation collaboration experiences.
During the live event, Cisco subject matter experts Vijay Rao and Amit Singh focussed on the simplified upgrade process and focused support from Cisco to migrate to version 9.1. They also talked about the changes made to the licensing model of User Connect Licensing and Cisco Unified Workspace Licensing.
Vijay Rao is a Network Consulting Engineer and is currently a unified communications (UC) consultant for Bank of America. He has been providing consulting assistance to the bank for the past 6 years. He helps design complex UC networks for large enterprise customers. He was previously part of Cisco IT in the Asia Pacific, Japan, and China (APJC) region and was instrumental in designing and implementing the Bangalore campus. He has been working with Cisco for 9 years and has 12 years of UC experience. He has a Cisco CCVP® certification.
Amit Singh is a customer support engineer at the Cisco Technical Assistance Center in Bangalore, India. He has 7 years of experience in his areas of expertise: wireless, Cisco Unified Communications Manager, multiservices, Cisco Unity®, and Cisco Unified Contact Center Express. He has been involved in various escalation requests from India, Singapore, and Australia and is currently working as a technical lead for the Voice team in Bangalore, India. He is a computer science graduate.
Remember to use the rating system to let Vijay and Amit know if you have received an adequate response.
Vijay and Amit might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Collaboration, Voice and Video sub-community forum shortly after the event. This event lasts through July 19, 2013. Visit this forum often to view responses to your questions and the questions of other community members.
Webcast related links:
Webcast Video
FAQ from the live webcast
Slides from the live webcast

Hello Robert,
Apologies for a delayed response, some days get very hectic.
In CallManager, we only define the SRST reference, and CUCM version and SRST version are independent of each other.
The only thing, which is related and will change with CUCM upgrade is Phone F/w version.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/compat/ccmcompmatr1.pdf
You may just want to check your, phone f/w compatibility with the SRST version running on your ISR G1 Gateways:
http://www.cisco.com/en/US/products/sw/voicesw/ps2169/products_device_support_tables_list.html
For Example: SRST version 7.1
http://www.cisco.com/en/US/prod/collateral/voicesw/ps6788/vcallcon/ps2169/data_sheet_c78-520521.html
You may want to do some lab testing with CUCM 9.1 and an SRST supported f/w on your phones.
If you decide to run the old Phone/F/w to support the SRST version, you may not be able to take advantage of new features.
Also, you can try and upgrade your phones(Wih CUCM 9.1) and test them with your SRST version.
It should work fine, but from a troubleshooting perspective, TAC may request you to come into a Cisco Supported combination.
Please, let me know if this clarifies your doubt or we can have a quick phone call.
Regards
Amit Singh

Cisco Prime Infrastructure - I can't see the hardware virtual image when I selected a device managed by Prime Infrastructure. See attached picture

My Cisco Prime Infrastructure ver. 1.2.1.12
Cisco Prime Infrastructure - I can't see the hardware virtual image when I selected a device managed by Prime Infrastructure. See attached picture.
Please let me know how to access or enable the feature.
Thanks,
Tek

This is by no means a full solution, but deleting and re-adding only takes a few minutes if you use the "Export Device" and "Bulk Import" features from the Device Work Center. You can export the desired devices to a CSV file, delete them, then import from the CSV.
Of course, you might lose historical data when deleting the devices, but I'm guessing that's not as relevant since the devices themselves have been replaced by different hardware.

Cisco PIX Device Manager Version 3.0(2)

Similar Messages

Maybe you are looking for