Search the Community
Showing results for tags 'rpi'.
Found 2 results
Configuring Multi-VLAN support for Remote Network Monitoring with Domotz Pro Domotz Pro is a remote network monitoring software which supports multi-VLAN configurations for remote network and device monitoring. The software which is designed for integration companies and IT professionals enables a host of network monitoring features including: Remote Access, Remote Power Management, Network Mapping, SNMP, Alerts, Network Diagnostics and more. Read more about Domotz’s Remote Network Monitoring Features. Domotz supports monitoring of multi-VLAN network configuration through a variety of network installation options which include: Self Installation on a Raspberry Pi (i.e. your own Raspberry Pi device) or via the Domotz Box or Domotz Pi which are available for purchasing from the Domotz Portal. This post will explain how to configure mutli-VLAN support via your own self-installed Raspberry Pi device. Configuring Multi-VLAN support on a Self-Installed Raspberry Pi device for Remote Monitoring Starting from Package version 1.03-201(April 2016) of the Domotz Agent for Raspberry Pi, the full package can be installed on your own Raspberry Pi device and supports the discovery and monitoring of devices hosted on two or more VLANs accessible from the Raspberry Pi. (Instructions and latest package are available here https://portal.domotz.com/portal/hardware/instructions/raspberry) This short guide is meant for users who have multiple VLAN and are already aware of related configuration and procedures. For further details, and step by step guides, on how to configure VLANs on Switches and Raspberry Pi, the user should refer to detailed guides (for example, please refer to: http://www.sbprojects.com/projects/raspberrypi/vlan.php). In order to allow the Domotz to discover and monitor devices on two or more VLANs, the user should configure both the Switch and the Raspberry Pi to multiple VLANs: Switch Configuration The interface port of the switch which will be used to connect the Raspberry Pi, should be configured: - in Access mode / Untagged for the main interface used by the Raspberry to communicate with the gateway (e.g. eth0). - in Trunk 802.1q mode / Tagged for the additional VLANs to be monitored (e.g. the eth0.10 used for lan 10) Please, refer to your specific switch/model guide on how to configure Trunk 802.1q and Access mode (Untagged/Tagged) for the port. Raspberry Pi Configuration In order to configure the Raspberry Pi to access both the main and VLAN interfaces, execute the following steps: 1. Install vlan package and configure moduels: sudo apt-get install vlan sudo su echo 8021q >> /etc/modules exit 2. Open with your favorite text editor /etc/network/interfaces and configure the Network Interface to access the main and VLANs. E.g. if we have a primary network on 192.168.5.0/24 (DHCP) and a secondary VLAN 10 on network 192.168.100.0/24 (Static IP: 192.168.100.200): auto lo iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet dhcp post-up ifup eth0.10 iface eth0.10 inet static address 192.168.100.200 netmask 255.255.255.0 In bold the part of the configuration due to the VLAN support, if you are using the Stretch version please see bellow the additional steps. 3. Restart the Raspberry Pi Stretch Additional Steps For the new version of Raspbian (Stretch) the "post-up" has no more effect, for this version please do the following: 1 - Create a file “vlans” in /etc/network/if-up.d/: $sudo nano /etc/network/if-up.d/vlans 2 - Add the following to it: #!/bin/sh ifup eth0.10 3 - Make the file executable: $sudo chmod 755 /etc/network/if-up.d/vlans 4 - Reboot the Agent, the interface eth0.10 should be up automatically now. Further reading about Domotz Pro: · Remote Network Monitoring Features · Pricing · Remote Network Management Installation Options
Hi. I have had a couple of times when the agent hasn't been reachable from the web-portal. It shows as offline in the iOS app and portal. The Pi itself is still alive in this instance, but a reboot is required to bring the agent back online. (Perhaps there's a console command that would do the same?). Where should I look for logs to troubleshoot why this is happening? Thanks