The installer resolves port conflicts between the ports in use by DCNM-SAN and the default ports that the Cisco DCNM-LAN server uses.įor information about the specific editions of supported server operating systems, see the Cisco DCNM Release Notes, Release 5.x, at the following location:.You cannot choose a database other than the database used by DCNM-SAN. The database that the installer configures the Cisco DCNM-LAN server to use is the database that DCNM-SAN is configured to use.The installation folder is determined by the installer and cannot be configured. If you install the Cisco DCNM-LAN server on a server system that already has an installation of Cisco DCNM-SAN, the Cisco DCNM installer detects the DCNM-SAN installation, which has the following effects on the installation: The installer also provides support for the initial installation of both DCNM-SAN and DCNM-LAN on a server. Note The Cisco DCNM installer is the installer for both DCNM-SAN and DCNM-LAN. Cisco DCNM-SAN SupportĬisco DCNM supports installing the Cisco DCNM-LAN server on a server system that has an installation of Cisco DCNM-SAN however, the Cisco DCNM-LAN release number and the Cisco DCNM-SAN release number must be the same. If the Cisco DCNM installer does not find a previous installation of a supported database, it can install PostgreSQL 8.2 for you. This section includes the following topics:Ĭisco DCNM-LAN supports the following databases: Information About Deploying Cisco DCNM-LAN Downloading the Cisco DCNM-LAN Server Software.Deploying a Clustered-Server Cisco DCNM-LAN Environment.Deploying a Single-Server Cisco DCNM-LAN Environment.Clustered-Server Cisco DCNM-LAN Requirements.Prerequisites for Installing a Cisco DCNM-LAN Server.Information About Deploying Cisco DCNM-LAN.This chapter includes the following sections: Installing modules with XS on Windows 64-bit.This chapter describes how to deploy Cisco Data Center Network Manager for LAN (DCNM-LAN) deployment and general steps for deploying Cisco DCNM-LAN single-server or clustered-server environments. How to install win32::GuidGen on windows 64 bit OS, Problems with Configuring PPM and Module Installations on Win XP-64 after Win XP,īuilding 64 bit perl on a 32 bit windows machine,īuilding DBI, DBD::ODBC for 64 bit perl Win, There is a 64 bit version for 5.8, the version of ActiveState is 5.8.9.827 圆4. Most likely, as it's a 5.8.x version, it's still a 32-bit version, so A guide to installing modules for Win32 applies in full. You haven't told us what version of ActiveState Perl you're using. My PC is not a server at all, and the operating system is Vista (64 bit), yet that compiler works fine with the w64 builds of ActivePerl. Assuming you're going to be using your compiler with ActivePerl, you (ideally) want the same compiler that built ActivePerl - which is the one that I gave the link to. does this mean I should be installing the Microsoft Windows SDK for Windows 7 instead? Re^3: Installing Perl modules on Win64/Perl 5.8 Re^2: Installing Perl modules on Win64/Perl 5.8Īssuming the version of server is Windows Server 2008 R2, does this mean I should be installing the Microsoft Windows SDK for Windows 7 instead? Once it's installed, you run "c:\Program Files\Microsoft Platform SDK\SetEnv.cmd" /XP64 /RETAIL to set up the compilation environment. Not sure about ppm availability but if you install the freely available Microsoft Platform SDK for Windows Server 2003 R2 (which is the compiler that built your w64 ActivePerl) you'll be able to build and install modules from source. Re: Installing Perl modules on Win64/Perl 5.8 Some notes below your chosen depth have not been shown here Re^5: Installing Perl modules on Win64/Perl 5.8 Re^4: Installing Perl modules on Win64/Perl 5.8 "I'd rather go naked than blow up my ass"
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |