RedvsGreen Documentation

Transcription

1 RedvsGreen Documentation Release 0.5 redvsgreen-admin May 15, 2016

2

3 Contents 1 Introduction What is RedvsGreen Supported Vendors Screenshots Feedback Inital Setup and Installation Requirements Default Credentials VM Setup Placement in the datacenter Management IP TimeZone NTP Accessing the WebGui Troubleshooting Cacti and dashinga2 stops working after timezone change: Adding your first devices Cacti Automation Network Scanning Scanning A Network Adding Devices to Trees Troubleshooting Network Scanning i

4 ii

5 Contents: Contents 1

6 2 Contents

7 CHAPTER 1 Introduction 1.1 What is RedvsGreen RedvsGreen is a VM with a collection of open source monitoring solutions as well as templates and default monitoring plugins for common vendors. The inspiration for creating this came from the amazing CactiEZ. It consists of: * Cacti v Weathermap * Icinga v Web2 + Director * Oxidized v * Netdata * Dashinga2(icinga2-dashing with some modifications) Its running on Centos 7 Kernel 3.10 with: * SSL enabled on everything * KSM memory deduping enabled * Latest updates The goal with RedvsGreen is to provide a complete network/data center monitoring tool that is fast and easy to configure. 1.2 Supported Vendors * Juniper - EX/SRX/Netscreen * PulseSecure - MAG * Palo ALto - VM/Appliance * Bluecoat - ProxySG * F5 - LTM/APM 3

8 1.3 Screenshots 1.4 Feedback 4 Chapter 1. Introduction

9 CHAPTER 2 Inital Setup and Installation 2.1 Requirements The.OVF is made for VMWARE ESX/ESXi but it might work for other Hypervisors as well. * 4 Cpus * 4 Gb Ram * 200 Gb Disk (Prefferably SSD) 2.2 Default Credentials All Default credentials can be found in the /root/redsvgreen folder * centos: root/redvsgreen * Webinterface: admin/redvsgreen 2.3 VM Setup Installing is as simple as importing the.ovf template on the Hypervisor. Verify that the requirements(cpu/mem etc) are met. Thin provisioning the harddrives is possible. It should not use more than 10gb of disk, but specify 200 GB so you have time to catch any issues. 2.4 Placement in the datacenter Example of two setups: 1. Directly in the OOB network. OOB-Network: /24 redvsgreen-ip: This allows you to monitor all equipment even if there is a router/firewall failure. 2. On a separate monitoring network 5

10 OOB-Network: /24 Monitoring-Network: /24 redvsgreen-ip: This allows for a more secure setup as protocols can be limited and traffic can be inspected by a intermediate device. If the intermediate device fails you loose your monitoring capabilites. For uptime concers go with option 1, for security concerns go with options 2. Note: As always the traffic to and from the monitoring device should be limited. Escpecially true if you are using it to store backups with oxidized which uses SSH. More on how to secure this is in the oxidized chapter. 2.5 Management IP After you have imported and started it head for the console access. The default ip of RedvsGreen is , its unlikely this fits your needs so lets change it: 1. Login with root/redvsgreen. You will be shown a prompt with the logo as well as some default settings. 2. Type: nmtui 3. Edit a connection 4. Choose your interface eno Edit it to fit your needs Note: Make sure you add the correct dns settings, as it will become very slow if it cannot resolve dns names. 6. When you are done hit OK and exit the application 7. Now we need to restart it. Type: shutdown -r now Verify that it works by accessing the device by ssh this time. 2.6 TimeZone Timezone is easily change by editing two files. First we store the old timezone as a backup: mv /etc/localtime /etc/localtime.bak It will prompt you to overwrite it, this is ok. As an example we list all available timezones in europe: 6 Chapter 2. Inital Setup and Installation

11 ls -al /usr/share/zoneinfo/europe/ Then we make a symlink to our chosen timezone: ln -s /usr/share/zoneinfo/europe/stockholm /etc/localtime Verify the new timezone by typing: date Second file we need to edit is the php.ini: vi /etc/php.ini When the file is open type /timezone to search for it. Change the line to reflect your needs. Example: date.timezone = Europe/Stockholm Restart the httpd deamon to make use the new timezone: systemctl restart httpd 2.7 NTP Warning: Alot of plugins and tools rely on time being exact to the second. Do not proceed without syncing to a ntp server. Edit ntp.conf: vi /etc/ntp.conf Change the line server iburst to fit your needs. server ntp1.example.com iburst server ntp2.example.com iburst After you have made the change restart the server: shutdown -r now When it boots up verify that time is synced: ntpstat Example output: synchronised to NTP server ( ) at stratum 3 time correct to within 8522 ms polling server every 64s 2.8 Accessing the WebGui Webgui can be accessed on: 2.7. NTP 7

12 Default credentials are: admin/redvsgreen Tip: You probably want to add a easily accessible bookmark ASAP since it will be alot of back and forth between the applications. 2.9 Troubleshooting Cacti and dashinga2 stops working after timezone change: If you change the time backwards in time the poller will stop until you reach the old time you had. To fix this we need to force it to run once. php /var/www/html/cacti/poller.php --force Run it for 10 seconds and then hit CTRL + C to quit. You should also stop dashinga2 and start it from commandline: systemctl stop dashinga2 cd /usr/share/dashinga2 dashing start Run it for 10 seconds then stop it using CTRL + C systemctl start dashinga2 8 Chapter 2. Inital Setup and Installation

13 CHAPTER 3 Adding your first devices This section describes how to scan your first network and adding the devices to RedvsGreen. Tip: V3. Before proceding it can be good to standardize on a common snmp standard for all devices. Example SNMP 3.1 Cacti Automation Network Scanning Scanning A Network Login in to RedvsGreen via the Webgui and Click on the Cacti button. First we need to setup the default snmp credentials for your network. Go to: Console -> Automation -> SNMP Options Open the default option set and add all your SNMP credentials. After you filled out all of your credentials: Go to: Console -> Automation -> Networks Open Test Network and change it to reflect the network you will scan. After you changed it hit the save button and go back to the previous page. Here you can select Test network and manually issue a Discover Now event. After you are done scanning: Go to: Console -> Devices Verify that the devices have been added correctly. Tip: You can reuse the Test Network for other scans, or you can create your own network and have them continuously scanned for automatic device addition. 9

14 Note: All devices needs to be reachable by ICMP ping and SNMP(UDP 161) Adding Devices to Trees Go to: Console -> Devices Mark all devices by clicking the checkbox in the top right corner. in the dropdown select Apply Automation Rules Verify by opening the graphs tab: Go to: Graphs 3.2 Troubleshooting Network Scanning Common resons for device not being found: 1. Does not respond to ICMP: Issue a ping from CLI to the device: ping Success: PING ( ) 56(84) bytes of data. 64 bytes from : icmp_seq=1 ttl=64 time=0.537 ms 64 bytes from : icmp_seq=2 ttl=64 time=0.654 ms ping statistics packets transmitted, 2 received, 0% packet loss, time 1000ms rtt min/avg/max/mdev = 0.537/0.595/0.654/0.063 ms 2. Does not respond to snmp: Issue a snmpwalk from CLI to the device: snmpwalk -v2c -c public Success shows lots of SNMP-MIB information:... SNMPv2-MIB::sysDescr.0 = STRING: Linux ntp.lab el7.x86_64 #1 SMP Tue Jan 5 16:07:00 UT SNMPv2-MIB::sysObjectID.0 = OID: NET-SNMP-MIB::netSnmpAgentOIDs Chapter 3. Adding your first devices

15 3. Device is not automatically detected in RedvsGreen Not all vendors have been added. Look for currently supported Vendors in the introduction section. Note that you can still add them manually and import templates that are not supported out of the box Troubleshooting 11