CSA on Solaris 10?

CSA 4.5.1 only lists Sol 8; 5.0 lists up to Sol 9.
Is there an expected ETA for support on Solaris 10 or would one of the current CSA versions be okay to use?

Hi
I'd like to know also if CSA is available on Solaris 10. You asked this question in January. Do you have more information? The current version of CSA is 5.1 and it supports Solaris 8 and 9. Do you know of any plans to support Solaris 10?
Alex

Similar Messages

Download csa for solaris

hello
i am to deploy csa on some solaris 9 servers (dns,mgt,mail...etc...).how can i download the csa?is there any discripancy when the csa is installing on the servers?

Yes. I'd also look at the release notes:
"The Management Center for Cisco Security Agents CD contains a license key which is used to operate the MC itself. If you need further license keys, before deploying Cisco Security Agents, you should obtain a license key from Cisco. To receive your license key, you must use the Product Authorization Key (PAK) label
affixed to the claim certificate for CSA MC located in the separate licensing
envelope.
To obtain a production license, register your software at the following web site.
https://tools.cisco.com/SWIFT/Licensing/PrivateRegistrationServlet
After registration, the software license will be sent to the email address that you
provided during the registration process."
The lowest price entry point is the Start Bundle:
"The Cisco Security Agent Version 5.1 Starter Bundle is a low-cost entry point for initial server and desktop deployments within an enterprise, or for small to medium-size businesses. It contains:
Management Center for Cisco Security Agents
1 Cisco Security Agent for servers
10 Cisco Security Agents for desktops
Incremental agents can be purchased for use with the Cisco Security Agent Starter Bundle."
At one point you could download a demo version of this product but I don't see it on CCO. Maybe someone else could point the way.
Hope this helps.

Solaris 10 Support for CSA

Is solaris 10 supported for CSA software, I can only see solaris 8 and 9 on the tech specs

Currently Solaris 10 is not supported in CSA 5 or the upcoming CSA 6. I am told that they will be adding Solaris 10 for CSA 6 but it is unknown as to when this will be released.

CSA 5.1.0.69 install fails on Solaris 9

Hi,
pkgadd -a CSCOcsa/reloc/cfg/admin -d .
I have ran it with truss and it fails with:
THIS SOFTWARE CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF
CISCO SYSTEMS, INC. USE, DISCLOSURE, OR REPRODUCTION IS PROHIBITED
WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF CISCO SYSTEMS, INC.
waitid(P_PID, 6387, 0xFFBFF028, WEXITED|WTRAPPED) (sleeping...)
## Executing checkinstall script.
/tmp/installmkayEm/checkinstallpkayEm: /usr/sbin/patchadd: cannot execute
Need patch version 111711-11 or higher.
Aborting installation.
pkgadd: ERROR: checkinstall script did not complete successfully
Installation of <CSCOcsa> failed.
No changes were made to the system.
waitid(P_PID, 6387, 0xFFBFF028, WEXITED|WTRAPPED) = 0
sigaction(SIGINT, 0xFFBFEFE8, 0xFFBFF068) = 0
sigaction(SIGINT, 0xFFBFF050, 0xFFBFF0D0) = 0
open("/tmp/jp", O_RDONLY|O_NDELAY|O_LARGEFILE) = 3
fstat64(3, 0xFFBFF408) = 0
fcntl(3, F_SETFD, 0x00000001) = 0
getdents64(3, 0x0012DE30, 8192) = 176
open("/tmp/jp/CSCOcsa/pkginfo", O_RDONLY) = 4
llseek(4, 0, SEEK_CUR) = 0
close(4) = 0
access("/tmp/jp/.save.CSCOcsa/pkginfo", 0) Err#2 ENOENT
access("/tmp/jp/CSCOcsa/pkginfo", 0) = 0
open("/tmp/jp/CSCOcsa/pkginfo", O_RDONLY) = 4
fstat64(4, 0xFFBFF160) = 0
Anyone have seen this?
# showrev -p | grep 111711
Patch: 111711-12 Obsoletes: Requires: Incompatibles: Packages: SUNWlibC
Patch: 111711-16 Obsoletes: Requires: Incompatibles: Packages: SUNWlibC
Patch: 111712-12 Obsoletes: Requires: 111711-12 Incompatibles: Packages: SUNWlibCx
Patch: 111712-16 Obsoletes: Requires: 111711-16 Incompatibles: Packages: SUNWlibCx
Thanks,
JP

in 5.1-0.91 also, to install the pkg I have to
1) comment in CSCOcsa/install/checkinstall the test that check for the patch
#if [ ${release} = "5.9" ]; then
# check_and_exit_if_no_patch 111711 11
# check_and_exit_if_no_patch 111712 11
#fi
2) modify the numbers in CSCOcsa/pkgmap to reflect the changes to size and cksum:
16 1 i checkinstall 3517 19425 1170094945
file size <3517> expected <3521> actual
file cksum <19425> expected <19565> actual
# pkgadd -a CSCOcsa/reloc/cfg/admin -d .
The following packages are available:
1 CSCOcsa CSAagent
(sun4u) 5.1-0 Build 91
Select package(s) you wish to process (or 'all' to process
all packages). (default: all) [?,??,q]: all
Processing package instance from
CSAagent
(sun4u) 5.1-0 Build 91
The following package has already been installed:
PKGINST: CSCOcsa
NAME: CSAagent
CATEGORY: application
ARCH: sun4u
VERSION: 5.1-0 Build 69
BASEDIR: /opt/CSCOcsa
DESC: CSAagent
PSTAMP: Cisco Systems
STATUS: completely installed
FILES: 65 installed pathnames
7 directories
44 executables
24685 blocks used (approx)
Do you want to overwrite the installed package with version 5.1-0 Build
91? [y,n,?,q] y
Conflict approval questions may be displayed. ## Executing checkinstall script.
Using as the package base directory.
## Processing package information.
## Processing system information.
7 package pathnames are already properly installed.
## Verifying package dependencies.
## Verifying disk space requirements.
Installing CSAagent as
## Executing preinstall script.
Cisco Security Agent is not running
## Installing part 1 of 1.
< snip file list >
[ verifying class ]
## Executing postinstall script.
Checking for connectivity between the agent and the management console: CSAMC51
This may take a few seconds...
CSCMA51 successfully reached via 'ping' - continuing
i.csacenter: /usr/sbin/rem_drv csacenter
i.csacenter: /usr/bin/rm -f /kernel/drv/csacenter /kernel/drv/csacenter.conf /kernel/drv/sparcv9/csacenter
i.csacenter: /usr/bin/cp csacenter.conf /kernel/drv
i.csacenter: /usr/bin/cp csacenter /kernel/drv/sparcv9
i.csacenter: /usr/sbin/add_drv -m '* 0666 root sys' csacenter
Warning: Pathname support will be discontinued in future releases of add_drv.
i.csacenter: rm -f /dev/csacenter0
i.csacenter: ln -s /devices/pseudo/csacenter@0:0 /dev/csacenter0
/usr/bin/cp csafile /kernel/fs/sparcv9
csafile has been installed
Modifing /etc/system
"forceload: fs/csafile" has been added in /etc/system
csafile already been loaded, not loading the new csafile.
The new csafile will be loaded after rebooting the system,
or unload csafile first and run this script again.
/usr/bin/cp csatdi /kernel/strmod/sparcv9
csatdi has been installed
csatdi already been loaded, not loading the new csatdi.
The new csatdi will be loaded after rebooting the system,
or unload csatdi first and run this script again.
Buffer overflow libraries appear to be installed...
I will uninstall them (with ./r.BO) first
Uninstall of Buffer Overflow libraries complete
Installation of Buffer Overflow libraries complete
Previous version of libcsarule shared libraries appear to be installed...
I will uninstall them first.
Uninstall of libcsarule libraries complete
and the system crash ;)

CSA getting error when adding solris 9.0 server as agent

Hai,
I am using VMS2.2 with MC for CSA version 4.0 build 540.
But wehn i try to add my sun solaris server 9.0 i am getting error that
"Not supported install on solaris 5.8"
But i am having all my servers running solaris 9.0
Is there is any way to update my CSA or with this CSA can i add my solaris server as agents Help me to go ahead .
Expecting reply.
Regards
Viswanathan.

I understand your concern and would like to ask for your assistance.
Please be in touch with your account team to have them contact the Product Team on your behalf with the number of servers that are impacted by this lack of support.
Doing so will help receive support for your OS's hopefully sooner.
thanks
peter

Dstat on Solaris 9

I use this nifty utility on my RedHat servers:
http://dag.wieers.com/home-made/dstat/
Has anyone bothered with getting dstat to work on Solaris 9? This utility needs Python which will want a few other things installed, I wonder if anyone has bothered to try...
Thanks!

Hey there -
CSA is not supported on Solaris 9 currently.
I have seen messages from customers who receive an error message during install.
Hope this helps,
peter

Solaris 8 support for CMD-649

Does Solaris 8 support the CMD-649 PCI to IDE device?
dp

Currently Solaris 10 is not supported in CSA 5 or the upcoming CSA 6. I am told that they will be adding Solaris 10 for CSA 6 but it is unknown as to when this will be released.

Intel network interface with Solaris 10 x86

Hi,
I have been Googling all evening to try and find a solution to this, but here is the problem:
I have a PC built around an Asus P4C800-E system board, and I have Solaris 10 x86 01/2006 installed. I would like to get the Ethernet interface (Intel adaptor, running on a CSA bus) up and running - but for some reason I can't seem to get the driver to bind to the proper address (pci8086,1019 - from what I have been able to find out): It instead insists on binding to pci1043,80f7. Even though pci8086,1019 is listed in /etc/device_aliases, it won't play nice.
I know the NIC is working, and have tried it under other OSes (including Linux).
Although Solaris x86 "sees" something there, and the interface is plumbed (it can even tell when the network link is up or down), I can't get the interface to work - pings do not work, etc.
Is there a way I can convince the driver to bind to pci8086,1019 instead of pci1043,80f7?
Any assistance would be greatly appreciated.
Joovilhar.

<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Joovilhar wrote on Wed, 08 March 2006 02:14</b></td></tr><tr><td class="quote">
I can't seem to get the driver to bind to the proper address (pci8086,1019 - from what I have been able to find out): It instead insists on binding to pci1043,80f7. Even though pci8086,1019 is listed in /etc/device_aliases, it won't play nice.
</td></tr></table>
Is 1043,80f7 the device's pci subsystem vendor and subsystem device id?
And 8086,1019 is the normal vendor/device id?
In this case everything would work as expected.
What is listed by "/usr/X11/bin/scanpci -v" for the ethernet controller?
<table border="0" align="center" width="90%" cellpadding="3" cellspacing="1"><tr><td class="SmallText"><b>Quote:</b></td></tr><tr><td class="quote">
I know the NIC is working, and have tried it under other OSes (including Linux).
Although Solaris x86 "sees" something there, and the interface is plumbed (it can even tell when the network link is up or down), I can't get the interface to work - pings do not work, etc.
</td></tr></table>
Try to boot the kernel with various settings of the "acpi-user-options" variable,
to disable / enable ACPI. In previous Solaris x86 releases, when
something went wrong configuring an interrupt vector for a nic device,
the typical end result is a nic that is unable to receive incomming
packets. Maybe your Asus P4C800-E is still problematic with ACPI, with
S10 x86 1/2006, and needs the acpi-user-options workaround.
http://blogs.sun.com/roller/page/danasblog?anchor=configurin g_solaris_acpi_at_boot
To change the "acpi-user-options" variable, edit the grub boot command
line and edit the "multiboot" line, e.g. append "-Bacpi-user-options=0x2".

The requirements of the CSA system

Dear All
I need to debloy the CSA solution on my network and I need to know the Hardware and Sotwatre requirements for the server and the clients and any thing related to the CSA to be deployed successfully.
Please mention them in details.
Thanks in advance,

You can read the requirements in the document located here:
http://www.cisco.com/en/US/docs/security/csa/csa60/release_notes/CSA60RN.html#wp136711
Or read below:
System Requirements (CSA MC)
Minimum Server Requirements
System Component
Hardware
â¢ IBM PC-compatible computer
â¢ Color monitor with video card capable of 16-bit
Processor
1 GHz or faster Pentium processor
Operating System
Windows 2003 R2 Standard or Enterprise Editions, Service Pack 0, 1, or 2
Note To run terminal services on the CSA MC system, you must edit the MC policy.
File System
NTFS
Memory
1 GB minimum memory
Virtual Memory
2 GB virtual memory
Hard Drive Space
9 GB minimum available disk drive space
System Requirements (Agent)
To run Cisco Security Agent on your Windows servers and desktop systems, the requirements are as follows:
Agent Requirements (Windows)
System Component
Processor
Intel Pentium 200 MHz or higher
Note Up to eight physical processors are supported.
Operating Systems
Windows Vista Business and Enterprise editions with service pack 0 or 1.
Windows Server 2003 (Standard, Enterprise, Web, or Small Business Editions) Service Pack 0, 1, or 2
Windows XP (Professional, Tablet PC Edition 2005, or Home Edition) Service Pack 0, 1, 2, or 3.
Windows Embedded Point of Service (WEPOS) 1.1
Windows 2000 (Professional, Server or Advanced Server) with Service Pack 0, 1, 2, 3, or 4
Note Citrix Metaframe and Citrix XP are supported. Terminal Services are supported on Windows 2003, Windows XP, and Windows 2000.
Memory
256 MB minimum-all supported Windows 2003, Windows XP, and Windows 2000 platforms
512 MB minimum-for Windows Vista.
Hard Drive Space
60 MB or higher
Note This includes program and data.
Network
Ethernet
Note Maximum of 64 IP addresses supported on a system.
To run Cisco Security Agent on your Solaris server systems, the requirements are as follows:
Agent Requirements (Solaris)
System Component
Processor
UltraSPARC 400 MHz or higher
Note Uni-processor, dual processor, and quad processor systems are supported.
Operating Systems
Solaris 9, 64 bit, patch version 111712-11 or higher installed.
Solaris 8, 64 bit 12/02 Edition or higher (This corresponds to kernel Generic_108528-18 or higher.)
Memory
256 MB minimum
Hard Drive Space
50 MB or higher
Note This includes program and data.
Network
Ethernet
Note Maximum of 64 IP addresses supported on a system.
To run the Cisco Security Agent on your Linux systems, the requirements are as follows:
Agent Requirements (Linux)
System Component
Processor
500 MHz or faster x86 processor (32 bits only)
Operating Systems
RedHat Enterprise Linux 4.0 WS, ES, or AS
RedHat Enterprise Linux 3.0 WS, ES, or AS
Memory
256 MB minimum
Hard Drive Space
50 MB or higher
Network
Ethernet
Note Maximum of 64 IP addresses supported on a system.

CSA on Other Platforms

We are rolling out CSA at my current place of business and really want to see more platforms get complete support. Even though the current versions support Solaris 8 and 9 and Red Hat 3.0, I want more support. Red hat 4.0 has been out for quite sometime now, as well as solaris 10. What about Novell Linux? We also have a huge issue with OS X, there is no centrally managed security software for this OS.
If we all post our desire to see these OS'es get support, hopefully the BU within Cisco will see it and work on this issue.
Thanks

Maybe Blackberry and the other one aren't Android compatible because they work fine when sending to other Android devices of a non Sony make so maybe it's them that aren't using standard code but lets all blame Sony because that's what people like to do
For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled. Richard P. Feynman

Pstack on Solaris 9

Hello,
Is there a way to filter out the "pstack" command so that it does not print the stack output of every thread of my multithreaded application but only the one thread that crashes?
My multithreaded application runs on Solaris 9.
Thanks,
Greg

Hey there -
CSA is not supported on Solaris 9 currently.
I have seen messages from customers who receive an error message during install.
Hope this helps,
peter

Csa - policy

can someone help please
1) all remote users who use laptop should not use any internet service without connecting to VPN ( ftp,http, https, downloads of any file, p2p)ftp should not be allowed even from command prompt
2) no user even in administrator group should be able to disable the csa service but only the local administrator.
3) users should only connect to allowed wireless networks
4)nobody should be able to use any removable media. can they be restricted to a certain zip drives?
all these users are currently running in test mode. i would like the above modules and the default modules for unknow virus, malware and rootkit to run in protected mode.
Thanks
Thanks

when you configure a policy, you are combining multiple rule modules under a common name. That policy name is then attached to a group of hosts and the group uses the rules that comprise the policy to control the actions that are allowed and denied on those hosts. You can have several different types of rules in a rule module and consequently within one policy. The policy level is the common ground by which host groups acquire the rules that make up their security policy. You can attach rule modules of differing architectures to the same policy. This way, you can configure task-specific, self-contained, inclusive policies across all supported architectures (Windows, Solaris, Linux) for software that is supported on all platforms.

Logical interface in solaris 10

Hi there,
I need to configure logical interface in a solaris 10 3/05 server. After reading the Solaris 10 IP services manual, I am not quite sure what to do. All the examples and explanation are about using the new subcommand addif of ifconfig. It was not clear in the documentation if the setting logical interfaces via addif will persist across boot.
Can one still configure logical interface in Solaris 10 in a more traditional way like in Solaris 8? In an Solaris 8 server I will do the following.
Let's assume I want to configure in a solaris 8 server a logical interface named hme0:1 with IP address 192.168.20.28 with netmask 255.255.255.0 for hostname host001
# cat /etc/hostname.hme0:1
host001
^D
# echo "192.168.20.28 host001" >> /etc/inet/hosts
# echo "192.168.20.0 255.255.255.0" >> /etc/inet/netmasks
# reboot -- -r
Can one still do that in solaris 10 3/05 server?

Hi there,
I need to configure logical interface in a solaris 10
3/05 server. After reading the Solaris 10 IP services
manual, I am not quite sure what to do. All the
examples and explanation are about using the new
subcommand addif of ifconfig. It was not clear in the
documentation if the setting logical interfaces via
addif will persist across boot.No. No 'ifconfig' command is persistent.
Can one still configure logical interface in Solaris
10 in a more traditional way like in Solaris 8? In an
Solaris 8 server I will do the following.
Let's assume I want to configure in a solaris 8
server a logical interface named hme0:1 with IP
address 192.168.20.28 with netmask 255.255.255.0 for
hostname host001
# cat /etc/hostname.hme0:1
host001
^D
# echo "192.168.20.28 host001" >> /etc/inet/hosts
# echo "192.168.20.0 255.255.255.0" >>
/etc/inet/netmasks
# reboot -- -r
Can one still do that in solaris 10 3/05 server?Absolutely.
You don't need to reboot (you can run ifconfig for this boot and let the files do the work next time) and the -r doesn't do anything with interfaces (expecially virtual interfaces) anyway.
Darren

Installation problem on Solaris

I am trying to install sun one 7.0 on Solaris 8. The install is failing with this error:
ERROR - library load failed with following error: Can't load library: /opt/SUNWappserver7/lib/libinstallCore.so
INFO - End core server uninstallation
anyone know what causes this??
cheers

Looks like Solaris package installation failed and installer reverted to uninstallation sequence. For low level pkgadd log please check /var/sadm/install/logs/Sun_ONE_Application_Server_install.B<timestamp> file (timestamp is date and time of your installation attempt in mmddHHMM format).
Look for any errors in this file. Most likely thing that could have happened is that the installation of Java Help (SUNWjhrt) package failed because you didn't have existing package based J2SE installation on the system. If that's the case, workaround is to either preinstall package based J2SE installation or to selected option to install bundled J2SE that comes with application server.

Installation problem on Solaris 10

Dear All,
We are trying to install j2sdk 1.4.2_13 on solaris server zone. I have downloaded j2sdk-1_4_2_13-nb-5_0-solsparc-ml.bin
But when I try to execute this:
#./j2sdk-1_4_2_13-nb-5_0-solsparc-ml.bin
It gives me error: The installer is unable to run in graphical mode. Try running the installer with the -console or -silent flag
Tried with -console:
The wizard cannot continue because of the following error: Invalid command line option: console is not supported (10
01) (403)
WARNING: could not delete temporary file /tmp/ismp001/2599368
WARNING: could not delete temporary file /tmp/ismp001/6183226
WARNING: could not delete temporary file /tmp/ismp001/1222839
Then tried with -silent:
This time command just completed w/o any output at all.
Please suggest what can I do?
regards, Sean.

Dear Siddhesh,
Thanks for your reply.
I tried using X Manager GUI for my Solaris. But when I double click the j2sdk-1_4_2_13-nb-5_0-solsparc-ml.bin file to run it, it simply denies saying:
The filename "j2sdk-1_4_2_13-nb-5_0-solsparc-ml.bin" indicates that this file is of type "Unknown type". The contents of the file indicate that the file is of type "Shell script". If you open this file, the file might present a security risk to your system.
Do not open the file unless you created the file yourself, or received the file from a trusted source. To open the file, rename the file to the correct extension for "Shell script", then open the file normally. Alternatively, use the Open With menu to choose a specific application for the file.
Also /tmp has full authorizations:
drwxrwxrwt 7 root sys 557 Jun 24 08:34 tmp
I dont have Hummingbird for X11 forwarding with this client. Do I have any other option??
regards, Sean.

CSA on Solaris 10?

Similar Messages

Maybe you are looking for