Edgewater Networks EdgeView 5300LF System Administration Manual
  1. Manuals
  2. Brands
  3. Edgewater Networks Manuals
  4. Network Hardware
  5. EdgeView 5300LF
  6. System administration manual

Edgewater Networks EdgeView 5300LF System Administration Manual

Hide thumbs Also See for EdgeView 5300LF:
Table of Contents

Advertisement

Quick Links

Download this manual
EdgeView 5300LF
System Administration
Guide
Version 1.0
Edgewater Networks / 2895 Northwestern Parkway, Santa Clara, CA 95051
Phone: +1 (408) 351-7200
/ Email: support@edgewaternetworks.com

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the EdgeView 5300LF and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Edgewater Networks EdgeView 5300LF

Summary of Contents for Edgewater Networks EdgeView 5300LF

  • Page 1 EdgeView 5300LF System Administration Guide Version 1.0 Edgewater Networks / 2895 Northwestern Parkway, Santa Clara, CA 95051 Phone: +1 (408) 351-7200 / Email: support@edgewaternetworks.com...
  • Page 2 EdgeMarc is a trademark of Edgewater Networks, Inc. in the United States and other countries. Any other trademarks appearing in this manual are owned by their respective companies.
  • Page 3 Additional EdgeView Publications EdgeView 5300LF Hardware Installation Guide • Getting Started with the EdgeView 5300LF • You can download these documents and additional application notes to help you configure, administer, and troubleshoot your EdgeView appliance from http://www.edgewaternetworks.com/kb.

  • Page 4: Table Of Contents

    Contents Before You Start ....................... 1
 Standalone System: ......................1
 High Availability System (in addition to that described for Standalone System): .... 2
 Main Menu ......................... 2
 Exit To CLI Prompt Or Exit Login Session..............2
 Rebooting and Shutting down EdgeView ..............3
 System Configuration ......................

  • Page 5: Before You Start

    Overview The EdgeView appliance provides a text-based system administration menu (also referred to as the “Menu”) to allow the system root user to configure EdgeView for initial deployment and to perform various administrative tasks. The “system root user” is normally the System or Network Administrator at a company charged with the task of configuring servers on the corporate network.

  • Page 6: High Availability System (In Addition To That Described For Standalone System)

    Prerequisite Task: Login in to the CLI using the root account. For instructions about how to login in to the CLI using the console or SSH, refer to the EdgeView 5300LF Hardware Installation Guide. Upon root login to the CLI via the console or SSH, you will receive the following Main Menu: The text-based menu is designed to run on the console of the EdgeView SuSE Linux server using only a keyboard.

  • Page 7: Rebooting And Shutting Down Edgeview

    You should not need to access the system CLI under normal circumstances. You can return to the Menu by typing “menu” on the CLI. If you wish to exit the login session completely, you may also choose option # 2 from the Main Menu (or type “exit” on the CLI). Rebooting and Shutting down EdgeView To reboot or shutdown your EdgeView server, simply arrow down to option #5 from the Main Menu and click <Select>:...
  • Page 8 To Reboot EdgeView, choose option #1 and click <OK>. Select <Yes> when you are asked to confirm the action as shown: To Shutdown your EdgeView, choose option #2 from the Reboot or Shutdown menu:...

  • Page 9: System Configuration

    Select <Yes> when you are asked to confirm the action as shown: System Configuration To perform the necessary configuration steps for the deployment of an EdgeView server, choose option #3 (“System Configuration”) from the Main Menu and click <Select> as shown:...
  • Page 10 You will receive the “System Configuration Menu” as shown: To return to the Main Menu, simply choose option #1 and click <Select>.

  • Page 11: Configuring Network Cards (Ip Address And Default Gateway)

    Configuring Network Cards (IP Address And Default Gateway) Select option #5 from the “System Configuration Menu” to configure the network cards on your EdgeView system. You will receive a confirmation screen as shown: Choose <Yes> to continue. You will now begin a series of screens to configure each network interface available on your EdgeView system.
  • Page 12 The default address for your eth0 interface is 192.168.1.1. Confirm or enter the IP Address and Netmask for your eth0 interface and click <OK> to continue. You will be taken to the next appropriate interface for your platform: If you wish to configure that interface, simply click <Yes> and you will receive the appropriate interface protocol selection screen as described above.
  • Page 13 Select <Yes> if you wish to add a default gateway on your EdgeView server. If you use static IP addresses for your network interfaces, you should always configure a default gateway as shown on the screen below: Enter the default gateway and then click <OK> to begin the system configuration process: You should reboot your EdgeView once network card configuration is complete.

  • Page 14: Configuring Hostname And Dns Servers

    Configuring Hostname And DNS Servers Select option #6 from the “System Configuration Menu” to configure the Hostname and DNS servers on your EdgeView system: You will receive the Host Name and Domain Name screen where you can enter the hostname and domain name of your EdgeView system based on the naming practices of your network.
  • Page 15 You may specify static IP addresses for your network name servers (most common) or you may allow DHCP to configure the name servers for you. If you choose to use the static server setting, you will receive a screen to enter the DNS servers as shown below: You will next be allowed to enter an optional search list of DNS servers.

  • Page 16: Configuring Network Date And Time

    If you changed the previous hostname and domain name (or change the default settings) you will receive a notice that a reboot is required as shown below. We strongly suggest you reboot at this time. If you are implementing a high availability configuration, you are required to reboot prior to configuring HA. Configuring Network Date And Time Your EdgeView system ships initially using the BIOS system clock as the source to keep time (also known as the “local”...
  • Page 17 To configure NTP to start at boot, choose the “Now and On Boot” option under the “Start NTP Daemon” sub-section of the General Settings section as shown below: You will need to delete the default local Synchronization Type (“Undisciplined Local Clock”) by clicking the Delete button.
  • Page 18 You will need to select “Server” from the next screen as shown below: Continue to the next screen and choose “Public NTP Server” for the NTP server. If your company uses a local NTP server, you may also choose the “Local NTP Server” option and designate that server according to your company policy.
  • Page 19 If you choose to use a public NTP server, you will now need to designate the server of your choice as shown below: Click [OK] to confirm the server setting and then [OK] again to complete the final network time configuration steps and you will be returned to the System Configuration Menu.

  • Page 20: Configuring Outbound Mail Settings

    Configuring Outbound Mail Settings EdgeView utilizes the postfix mail transfer agent to send email messages for a variety of system activity. Choose option #8 from the System Configuration Menu to configure postfix beyond the default settings in order to customize outbound mail from your EdgeView server with the following features: ●...
  • Page 21 Choosing <Yes> will take you to the Envelope Masquerading step of the configuration process as shown below: You should enter a domain name to use for the From header of email addresses that are sent from this EdgeView as it pertains to the normal email domain of your company. For example, if email from your company is normally listed as “mycompany.com”, then you should enter “mycompany.com”...
  • Page 22 If you wish for email sent from local users of the system to have a different user name in “From” header, you may enter the desired email address to show in the From header in the “Local User Email Masquerading” screen. This step is optional, but we suggest you populate the root and nobody users with the email address of your EdgeView administrator.
  • Page 23 “Outgoing Mail Server” screen. Remember that sending mail directly is rare and to avoid typical SPAM restrictions, your EdgeView server should have a reverse DNS entry. If you choose to relay mail through a company mail server, you will likely need to authenticate before sending the mail (another SPAM restriction).

  • Page 24: Creating And Loading System Configuration Xml

    Creating and Loading System Configuration The System Configuration Menu also provides you a way to save the settings of your EdgeView system and re-load them to another system or to use as a restore point in the event of a disk crash. Choose option #3 to create an XML file based on the configuration steps described above.
  • Page 25 You will see an alert when the settings have been saved. You may copy this XML file from your EdgeView system as a backup or to load back into this or another system. To load a previously saved XML settings file, choose option #4 from the System Configuration Menu: You will then receive a screen that allows you to select the appropriate file from your file system:...
  • Page 26 Select the desired XML configuration file and click <OK> to receive a confirmation screen: If you choose <Yes>, your EdgeView system will be configured with the settings found in the chosen XML configuration file:...

  • Page 27: Installing And Configuring High Availability (Ha)

    You should reboot your EdgeView at this point. Installing and Configuring High Availability (HA) If your EdgeView license provides for High Availability (HA) functionality, you will need to configure each of your two EdgeView HA servers (also known as the “HA pair” or “HA cluster”) by clicking option #9 from the System Configuration Menu.
  • Page 28 You will receive a menu that allows you to select the configuration options for your HA configuration. For the initial install and configuration of HA, you should keep the three default actions. If you are re- configuring one HA function or feature, you may de-select an option. You will now receive a hostname warning screen as shown below:...

  • Page 29: Heartbeat Configuration

    You MUST properly assign a hostname and have configured the network cards on the EdgeView system before you configure HA. Please note that when setting the hostname of the node members of your HA pair, the standard practice (but not required) is to number each node member using a zero-based index. For example, the primary (or “master”) EdgeView server of an HA pair would normally be called “edgeview0”...
  • Page 30 primary mode. This feature will typically only be used if the EdgeView servers are on the same network segment (typically connected to each other by network cable) so that the virtual IP address can reach the server that is acting as the primary of the HA cluster. Please note that a geographically redundant HA pair (also known as “GEO HA”) does not utilize a VIP as the cluster members are typically not on the same network segment.
  • Page 31 You will then receive a screen that allows you to enter the cluster members of this EdgeView HA pair as shown: Enter the hostnames of the HA cluster members and then click <OK> to continue the configuration process. You will receive a screen that allows you to enter the broadcast ucast address of the other EdgeView HA cluster member of this HA pair as shown:...
  • Page 32 This value is typically set to the IP address of the other node of this HA pair. The next step in the configuration process allows you to configure the IP address of the broadcast interface that was configured above. On a typical EdgeView HA setup, this will be the eth1 network interface.
  • Page 33 Click <OK> to begin the broadcast interface configuration process as shown: This process may take a few minutes and the screen may look as though nothing is happening but the process is ongoing in the background and requires you to wait until the screen changes. Once the broadcast network configuration has completed, you will receive the Heartbeat Configuration screen as shown:...
  • Page 34 You should typically use the default UDP port of 694 as the heartbeat port. The Upstream router input should be the IP address of the default gateway of this EdgeView system. Linux heartbeat validates that an EdgeView HA pair is able to connect to its default gateway and route out before it will bring up a cluster member as the primary.

  • Page 35: Unison (File Replication) Configuration

    Click <EXIT> to proceed to the Unison configuration steps. Unison (File Replication) Configuration EdgeView HA utilizes the Linux unison application to replicate system files between cluster members. In order to communicate using SSH and unison without the need to enter a password, you must exchange SSL certificates between the cluster members of your HA pair.

  • Page 36: Mysql Configuration

    Enter the root user password for the other member of the HA pair and click <OK> to exchange SSL certificates. Once this is complete, you will proceed to the MySQL configuration process. MySQL Configuration EdgeView HA configuration utilizes bidirectional replication between the HA cluster members. This means that each cluster member acts as the master AND slave to the other member in regards to database replication.
  • Page 37 Click <EXIT> to complete the HA configuration process. You will receive a reboot notice as shown below: This notice warns you to reboot both machines after the second member of the HA pair has been configured. This means that if you are configuring the first machine of the HA pair, you'll need to reboot this machine once again after you configure the second member of the pair.

  • Page 38: Troubleshooting Using Sanity And Health Check Tools

    You will receive a notice when the HA configuration process is complete. Click <OK> to return to the System Configuration Menu. Troubleshooting using Sanity and Health Check Tools Once your EdgeView system has been configured, you may validate the settings of your system using option #4 from the Main Menu: Sanity Checks should be performed any time your system is experiencing problems, including if your HA system stops functioning as expected.
  • Page 39 The system health checks available in the Sanity Menu include: ● Database Corruption Check ● Database Relationship Check ● Database Replication Check (for High Availability Systems) ● Required Process Functionality Check (Services Up/Down) ● File Replication Check (for High Availability Systems) ●...
  • Page 40 Please note that you must have a properly functioning outbound mail configuration as described in this document before these logs can be emailed directly from the EdgeView to our support team.
  • Page 41 Edgewater Networks, Inc. 2895 Northwestern Parkway Santa Clara, CA 95051 Phone: (408) 351-7200 info@edgewaternetworks.com Converged Networking. Simplified. All rights reserved. Copyright © 2011 Edgewater Networks, Inc.

Table of Contents