We recommend that you check the option: Monitor the Device on which the collector is installed. LogicMonitor does not support non-English languages. If running on a VMware virtual machine, install VMware tools with VMware tools periodic Time Sync disabled. The Collector should have reliable time, thus the server should have NTP setup or Windows Time Services to synchronize via NTP. (More memory permits a Collector to collect data from more resources.) See Collector Capacity. For a detailed list of the ports, see About the LogicMonitor Collector.Ī minimum of 2GB of RAM. In addition, the ports for the monitoring protocols you intend to use (such as SNMP, WMI, JDBC, etc.) must be unrestricted between your Collector and the resources you want to monitor. The server must be able to make outgoing HTTPS (port 443) connection to the LogicMonitor servers (proxies are supported). For both Windows and Linux, we support only 64-bit Operating Systems.We have validated that there are no IPMI issues on this version. You may consider running the Collector on Windows Server 2022.The IPMI DataSources include: IPMI Status Sensors, IPMI Full Sensors, and IPMI Service Status. Although we implicitly support current versions of Windows Server, we recommend that you do not run the Collector on Windows Server 2019 if you have IPMI DataSources installed because of a possible memory issue.We do not support installing the Windows Collector on non-server Windows operating systems.We support the following Linux distributions: LogicMonitor follows the Microsoft Lifecycle Policy for the “Extended Support End Date” and the Red Hat Enterprise Linux Life Cycle for the “End of Maintenance Support 2 (Product retirement)” date to determine which Windows Server and Linux operating systems are supported for Collector installation. Windows Server or Linux running on a physical or virtual server The following table lists general requirements for choosing a server to host the Collector. To ensure reliability, the Collector should not communicate across the internet to poll resources in another datacenter, through firewalls or network address translation (NAT) gateways. Most often, Collectors are installed on machines that function as syslog servers or DNS servers. The first step in adding a Collector is deciding which device will host the Collector.įor each location of your infrastructure, we recommend that you install a Collector on a Windows or Linux server that is physically close to or on the same network as the resources it will monitor. In your LogicMonitor portal, navigate to Settings | Collectors | Add | Collector:įollow the steps in the Add a Collector dialog to complete and verify the Collector installation. See Installing the Collector in a Container. For example, you can only run the full installation, not the bootstrap, and you will need to run the Collector process as root. Installation of a containerized Collector does not support all install options. LogicMonitor also supports installing and running the Collector in a Docker container. This article walks you through the steps to install a Collector in your LogicMonitor portal. You do not need to install a Collector on every device, instead one Collector on a server should be used to monitor all the resources in that location. Note: Windows 7 users, use the Windows 2008 Drivers or use this one.The LogicMonitor Collector monitors your infrastructure and collects the data defined by LogicModules for each resource in that location. For your machine to see the MSA as a device, you need to install a driver, there is a copy of the drivers on the CD that came with the device. Connect to and Manage your MSA via the USB/CLI Cableġ. Once you know the IP address, you can connect with your web browser. If you do have DHCP running, connect your MSA and run the MSA Device Discovery Tool, (On the CD that came with the device).Ģ. The Quickest Solution – is to connect the MSA to the network, and if it cannot get a DHCP address it automatically gives itself 10.0.0.2/24 on controller A and 10.0.0.3/24 on controller B.ġ. Each time I put in a new P2000, I think “I wonder how that USB CLI socket works?” Yesterday I had to find out. With the G3 they have replaced the serial socket with a mini USB socket. With the G1 and G2 models, you got a console/serial cable and could just terminal in. Yesterday I was starting with new virtual infrastructure and had no DHCP. Then I can get the address for the DHCP Scope, and point my web browser at it. Normally I simply connect a new MSA to a clients network, and it gets it’s address from DHCP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |