3 Introduction This is part of the documentation of the AONode product, it holds the description of the optional management module, which can be used for surveillance of the AONode. The hardware consists of the basic AONode, based on the AO 801 series architecture, and a management module holding an Ethernet interface, RJ-45. SNMP can be used to for surveillance and settings. E.g. read system settings, optical Rx power level, temperature and power supply status. The module can be inserted into the AONode, when power has been shut off. The management module holds a CPU, which can be provisioned with firmware from a central server.

4 The boot process of the AONode The boot process is split in two: - First the node issue a dhcp request with dhcp option 60 set to <file name>vx_xx (where x_xx is the version number of the firmware). - Afterwards the node start it's operation system (OS). The OS also issue a dhcp request, with dhcp option 60 set to the version of the software. When a new node is unpacked it doesn t contain any firmware on the management module, and before the management part of the node can be used, it must be updated with the latest revision. This means that when the AONode is installed, it will be required to remotely update with firmware, before the management part will be working. The first bootp/dhcp request from the device can be used to remote upgrade the firmware. If a bootfile and a bootserver is given in the bootp response then the file is downloaded via tftp and executed by the device. DHCP Discover DKT_firstboot (option 60) DHCP Offer DKT_firmware (filename, server info, etc) DHCP Discover Request IP Address AONode DHCP Server DHCP Offer IP Address TFTP Request filename TFTP transfer of firmware DHCP Discover configuration (option 66, 67) DHCP Offer configuration (filename, server info, etc) TFTP Request configuration TFTP transfer of configuration Configuration is download at each reboot/start-up. Download of firmware only happens if requested in DHCP configuration

5 DHCP Settings The AONode requires a dhcp server connected to the fiber WAN port before power on. As an example we have used Linux Kubunto platform and installed the following component via adept dhcp3 tftpd Make sure that DHCP server has its unique static IP address settings, so it doesn t conflict with its own leasing of IP Addresses. To edit DHCP Server Setup, edit the DHCP setup configuration file: sudo kate /etc/dhcp3/dhcpd.conf # DHCP SECTION: insert the following default-lease-time <SECONDS>; # Ex: default-lease-time 600 max-lease-time <SECONDS>; # Ex: max-lease-time 7200 # The following routine is necessary in the first boot process, in order to download firmware into the AONode. The AONode is born without firmware image. dkt_fw_01_00.img indicates the flashing instruction image to be downloaded. Remember to place this firmware file in tftp server root directory class "Initial_Firmware" { match if substring (option vendor-class-identifier, 0, 13) = "DKT_firstboot"; filename = "<Latest_Firmware_Name>"; # Ex: filename = dkt_fw_01_03.img }

8 TFTP Settings After the DHCP server is configured a TFTP server should be configured, so firmware image and configuration file for the AONode can be downloaded correctly. As an example we have used Linux tftpd and xinetd The TFTP configuration file must be edited. And a tftpboot directory must be created in root and made accessible from AONodes mkdir tftpboot # creates tftpboot directory chmod a+ wrx tftpboot # changes rights so directory is readable, writeable and executable from AONODEs sudo kate /etc/xinetd.d/tftp # starts an editor where TFTP settings can be inserted Insert the following: service tftp { protocol = udp port = 69 # CONFIGURATION FILE SECTION: insert the following socket_type wait user server server_args disable = dgram = yes = nobody = /usr/sbin/in.tftpd = /tftpboot = no }

9 Custom configuration When the OS issue a dhcp request a filename of a configuration file can be sent to the node. This configuration file is then downloaded by tftp during the boot process and issued instead of the default configuration. In this way it is possible to persist settings for each node The server and the filename of the configuration file should be sent in respective tftp-server-name (option 66) and bootfile-name (option 67) from the dhcp server. Notice these options are different from the bootfile/bootserver used in the bootp response. If it is not feasible that the dhcp server distinguish the AONode configurations base on the hardware address an alternativ method can be used. The dhcp server send out the name of a generic configuration. This configuration can then include instruction to the node of fetching a AONode specific configure by tftp where the requested filename is a combination of the node hardware address. An example of a configuration file could be the following: #################################################################### # DKT configuration # Firmware version: 1_03 #################################################################### telnetd -l /bin/sh # End of DKT configuration ####################################################################

10 Device script commands The following commands are supported in the script that will be downloaded to the AONode via TFTP during boot-up process. This command is used to configure the switch in the unit. The command takes one or more of the following parameters. Basic settings: -v, --version -h, --help Prints the version number. Prints this help. SNMP settings: TO BE UPDATED

11 Explanation of feature settings SNMP settings The unit can be configured via a script file that is provisioned to the unit at boot up. Configuration of SNMP values The following SNMP values can be set by the configuration file: SysContact the administrive contact for the network # touch command ensures that SNMP local settings file is created, must be used before any SNMP settings are appended to the device, and must be created only once touch /etc/snmp/snmpd.local.conf echo "syscontact >> /etc/snmp/snmpd.local.conf SysLocation for the location of the system # Ensure that touch is used in any previous SNMP setting echo "syslocation somewhere" >> /etc/snmp/snmpd.local.conf SysName the name of the system e.g the customer identification # Ensure that touch is used in any previous SNMP setting echo "sysname customerxyz" >> /etc/snmp/snmpd.local.conf

12 Surveillance via SNMP Information about the current temperature, power supply voltage as well as optical Rx level can be access via SNMP. Also traps are being generated if preconfigured levels are exceeded. Two MIBs are provided, which can be integrated into the SNMP application: DKT-MIB.txt DKT-AONODE.txt The MIBs will be present in the private section under dkt folder, which is shown below. The dktaonodemib holds the information about the current temperature, power supply voltage as well as optical Rx level. Also the criterias for trap generation can be configured, see below.

14 The device can be programmed to generate the following traps dktaonodetemphighnotif: Temperature exceeded high limit dktaonodetemplownotif: Temperature exceeded low limit dktaonodevoltagelownotif: Voltage exceeded low limit dktaonodeoptrxlevelhighnotif: Optical rx level exceeded high limit dktaonodeoptrxlevellownotif: Optical rx level exceeded low limit based on the settings of the temperature, power supply and optical RX levels. In order to start trap generation the destination must be specified with the use of the following command: trap2sink HOST [COMMUNITY [PORT]] It is possible to embed this in the configuration file by appending the command to the device SNMP settings # Specify IP Address of the trap destination # Ensure that touch is used in any previous SNMP setting # touch command ensures that SNMP local settings file is created, must be used before any SNMP settings are appended to the device, and must be created only once touch /etc/snmp/snmpd.local.conf echo "trap2sink <IP Address> private 162" >> /etc/snmp/snmpd.local.conf Please note that the optical Rx input level is represented in uw (micro Watt), 1000 uw = 1 mw = 0 dbm. Reboot The device can be accessed via TELNET, and is rebooted with the use of reboot command. TELNET access must however be configured in the configuration file. # The following command enables TELNET access from WAN telnetd -l /bin/sh

Procedure to Create and Duplicate Master LiveUSB Stick A. Creating a Master LiveUSB stick using 64 GB USB Flash Drive 1. Formatting USB stick having Linux partition (skip this step if you are using a new

Booting Palacios/Kitten and Palacios/Linux Over the Network Using PXE Yuan Tang Lei Xia November 11, 2011 PXE allows us to boot operating systems over the network. This is incredibly useful for debugging

Cork Institute of Technology Master of Science in Computing in Education National Framework of Qualifications Level 9 February 2005 System and Network Management (Time: 2 Hours) Answer any THREE questions

Setting up your K12LTSP or LTSP loadbalancing and dhcp failover. What you'll need: Two servers running K12LTSP or LTSP in single NIC mode A good solid high speed connection (gigabit recommended) An external

SNMP-1 Configuration Guide You must configure the Net Logic Card before it can operate properly. You have two methods to configure the Net Logic Card: Using telnet or terminal. Using Telnet 1. Make sure

How to Configure an Initial Installation of the VMware ESXi Hypervisor I am not responsible for your actions or their outcomes, in any way, while reading and/or implementing this tutorial. I will not provide

pplications Note Setting Up Linux PXE on Server and Client Systems 1 Prerequisites The example in this document was performed on a PXE server running RHEL5.2 64-bit with DHCP, TFTP, and NFS servers running

Note: This case study utilizes Packet Tracer. Please see the Chapter 5 Packet Tracer file located in Supplemental Materials. CHAPTER 5 OBJECTIVES Configure a router with an initial configuration. Use the

Lab 6: Dynamic Host Configuration Protocol The purpose of this lab is to configure a DHCP server for multiple subnets. You will configure additional options along with an IP address and netmask, and you

Title Page Web/SNMP Management SmartSlot Card AP9606 User s Guide Thank You! Thank you for selecting the APC Web/SNMP Management SmartSlot Card. It has been designed for many years of reliable, maintenance-free

1:1 NAT in ZeroShell Requirements The version of ZeroShell used for writing this document is Release 1.0.beta11. This document does not describe installing ZeroShell, it is assumed that the user already

6 Command Line Interface The D-Link SmartPro Switch allows a computer or terminal to perform some basic monitoring and configuration tasks by using the Command Line Interface (CLI) via TELNET protocol.

CSCI 312 - DATA COMMUNICATIONS AND NETWORKS FALL, 2014 Lab 1: Introduction to the network lab NOTE: Be sure to bring a flash drive to the lab; you will need it to save your data. For this and future labs,

APPENDIXA This appendix contains information about configuring thin clients using a central file server as an alternative to Cisco VXC Manager. Cisco VXC Manager is the standard tool for central management.

Chapter 6 Using Network Monitoring Tools This chapter describes how to use the maintenance features of your RangeMax Wireless-N Gigabit Router WNR3500. You can access these features by selecting the items

Authenticating a Lucent Portmaster 3 with Microsoft IAS and Active Directory The following tutorial will help you to setup a Portmaster 3 to authenticate your dial in users to Active Directory using IAS

I N S T A L L A T I O N M A N U A L 2015 Fastnet SA, St-Sulpice, Switzerland. All rights reserved. Reproduction in whole or in part in any form of this manual without written permission of Fastnet SA is

First Edition, March 2009 www.moxa.com/product 2009 Moxa Inc. All rights reserved. Reproduction without permission is prohibited. Moxa Device Manager 2.0 User Guide The software described in this manual

Chapter 6 Using Network Monitoring Tools This chapter describes how to use the maintenance features of your RangeMax Dual Band Wireless-N Router WNDR3300. You can access these features by selecting the

IOS is the most critical part of any cisco device. We should always keep a backup copy of IOS to deal with any unwanted situation. In this article I will explain the backup and restore process of IOS in

Network Management Card AP9617 AP9618 AP9619 Installation and Quick-Start Manual How to Avoid Equipment Damage Disconnect UPS power You do not need to turn off a Symmetra or a Silcon model UPS to install

StarMOBILE Network Configuration Guide A guide to configuring your StarMOBILE system for networking INTRODUCTION... 3 BEFORE YOU BEGIN... 3 1) CONFIRM YOU HAVE THE LATEST SOFTWARE... 3 2) INSTALL THE STARMOBILE

Lab 6: Dynamic Host Configuration Protocol The purpose of this lab is to configure a DHCP server for multiple subnets. You will configure additional options along with an IP address and netmask, and you

Chapter 7 Using Network Monitoring Tools This chapter describes how to use the maintenance features of your RangeMax NEXT Wireless Router WNR854T. These features can be found by clicking on the Maintenance

Reboot the ExtraHop System and Test Hardware with the Rescue USB Flash Drive This guide explains how to create and use a Rescue USB flash drive to reinstall and recover the ExtraHop system. When booting

APPENDIXE This module provides basic guidelines for the (VCS) configuration in a Subscriber Manager (SM) cluster installation. It assumes basic knowledge of the VCS environment; it does not replace the

3.1 Connecting to a Router and Basic Configuration Objective This lab will focus on the ability to connect a PC to a router in order to establish a console session and observe the user interface. A console

FAQs Hills Professional Series NVRs and Cameras (V1.1) 1. What is the default NVR resolution? By Default NVR video output resolution is 1080P. Resolution may be changed if necessary to suit the attached

Application Note 013 a Visual Plus Corporation Company Connecting EWS using DDNS ver.1.0 This application note explains how to establish communication between PROS and EWS over internet, in case EWS is

Manual Manual Copyright Version 1.3.5, 2012 1 Manual Legal Notice Aim and purpose This document describes a software application for the management of Teldat devices. For the latest information and notes