08-01016-01 Elastic Networks YesWare Applications User’s Guide Software Release 2.30 Document Revision 2.30.
Elastic Networks YesWare Applications User’s Guide Software Release 2.30 Document Revision 2.30.1 Publication Date: October 2000 2000 Elastic Networks All rights reserved All information contained in this document is subject to change without notice. Elastic Networks reserves the right to make changes to equipment design or program components, as progress in engineering, manufacturing methods, or other circumstances may warrant. EtherLoop is a trademark of Elastic Networks. Software Release 2.
iv Software Release 2.
v Publication history Document Release Date Description Document Revision 2.30.1 October 2000 Document Final release with comprehensive index and minor terminology changes. Document Revision 2.30 September 2000 Document Pilot release, incorporating PMS integration, Print Services, Conference Room Billing, and ftp included in YesWare Software Release 2.30 Document Revision 2.
vi Software Release 2.
vii Contents About this document xv Audience Software version note xv xv SECTION I VISITOR-BASED NETWORKS AND YESWARE Introducing Visitor-Based Networking and YesWare 1-1 YesWare features new for 2.
viii Contents Visitor access controls Port Validation Visitor authentication VBN web site customization VBN page customization Virtual Concierge Service-provider branding Service-provider home/splash page configuration System management and maintenance capabilities Installing a YesWare VBN system Organization of this manual 1-22 1-22 1-23 1-24 1-24 1-24 1-24 1-25 1-26 1-27 1-27 YesWare Server operating system and software modules 2-1 YesWare 2.
Contents ix SECTION II YESWARE INSTALLATION AND CONFIGURATION YesWare Server host network configuration 3-1 YesWare Server YWS functional components YesWare Server console connection methods YWS keyboard/monitor connections YWS PC/VT-100 connection YWS telnet connection YesWare Server console interface EON login default EON commands Configuring the YWS host network interface Setting the YWS date and time Setting the DNS nameserver(s) for the YWS 3-2 3-2 3-4 3-4 3-5 3-5 3-7 3-7 3-8 3-9 3-13 3-15 InterPr
x Contents SECTION III YESWARE SERVICE PROVISIONING EtherLoop system provisioning 6-1 Enhanced Modem Billing provisioning requirements Enhanced Modem Billing CO modem provisioning Enhanced Modem Billing CPE modem provisioning Provisioning Enhanced Modem Billing Modem Connection Billing provisioning requirements Modem Connection Billing provisioning dialogs Provisioning Modem Connection Billing EtherLoop modem management provisioning requirements EtherLoop modem management system requirements Provisioning
Contents xi YesWare service billing 8-1 Billing Manager feature description Guest Room Billing Billing protocol and time settings Billing rate configuration Guest Room Billing and PMS integration Configuring Guest Room Billing Credit Card Billing Credit Port Use Context assignment Authorize.
xii Contents Customizing the VBN web site 10-1 VBN page customization VBN page construction Tasks required for VBN page customization YesWare VBN pages Using tags tags used for visitor authentication tags used for port and service information tags used for VBN graphics Branding and home/splash page configuration Branding Configuration dialog Custom Look and Feel configuration Creating the custom VBN web site Configuring the Virtual Concierge 10-2 10-2 10-2 10-
Contents xiii SECTION IV YESWARE SYSTEM MANAGEMENT YesWare security and administration 13-1 YesWare System Security Adding or removing modem privacy filters Using the Add privacy filters function Restricting web access to the YWS Changing the system manager password Resetting a password Routine Maintenance and Administration Adding a new user Deleting a User Viewing System Logs Viewing VBN user activity Show Active Users Show User History Trace Address Configuring NTP (network time protocol) Backup, Rest
xiv Contents Using the Download Utilities module Download Utilities purpose and function Using Download Utilities Downloader status and logs Upgrading EtherLoop modem firmware Upgrading from Generation 1 to Generation 2 modem firmware 15-1 15-2 15-2 15-2 15-3 15-6 APPENDIX A YESWARE MANAGEMENT USING SNMP Remote YesWare Management using SNMP A-1 YesWare SNMP components YesWare supported MIBs Using YesWare SNMP YesWare SNMP web interface Editing the SNMP configuration parameters YesWare EtherLoop MIB MIB
xv About this document 1- This document provides instructions for using the YesWare software suite to manage an EtherLoop or Ethernet system. Audience The audience for this document includes network planners, installation technicians, network administrators, and anyone who may be charged with provisioning or maintaining the YesWare system. Software version note The YesWare 2.3 software release consists of a base 2.
xvi About this document Software Release 2.
SECTION I VISITOR-BASED NETWORKS AND YESWARE Software Release 2.30 Software Release 2.
1-1 Introducing Visitor-Based Networking and YesWare 1This chapter introduces the concepts of visitor-based networking and the purpose and function of YesWare in a visitor-based network. Chapter topic list This chapter includes the following topics. Topic See YesWare features new for 2.
1-2 Introducing Visitor-Based Networking and YesWare YesWare features new for 2.3 For users familiar with YesWare, this section summarizes the features now available as part of the YesWare 2.3 release. For new users, the remainder of this chapter describes Visitor-Based Networking (VBN) and YesWare’s VBN features and capabilities in more detail.
Introducing Visitor-Based Networking and YesWare 1-3 Visitor-based networking Until recently, nearly all Ethernet local area networks (LANs) were private. Developed for private use, owned and maintained by private organization, these networks were focused on providing connectivity for a select group of people such as employees. Everyone who used the network was supposed to be able to use it, and the costs of providing that network were considered overhead.
1-4 Introducing Visitor-Based Networking and YesWare YesWare and VBN YesWare is a suite of system management software used to manage an EtherLoop or Ethernet VBN (see “YesWare VBN transport systems” on page 1-8).
Introducing Visitor-Based Networking and YesWare 1-5 Local host network connection requirements The network hosting the YWS must have the following: • Ethernet 10/100Base-T termination for the YWS network interface • network connection to an existing local area network (LAN) or wide area network (WAN) router • access to the Internet through an Internet Service Provider (ISP) or other Internet account • valid TCP/IP network address configuration (IP address, network mask, gateway address) for the YWS.
1-6 Introducing Visitor-Based Networking and YesWare Visitor internetwork access YesWare visitors receive access to the Internet or other internetwork through YesWare’s InterProxy capability. The InterProxy function is unique in that it accepts traffic from TCP/IP clients regardless of a client’s IP address configuration.The following sections describe visitor internetwork access using the InterProxy module, and the requirements visitor computers must meet to receive InterProxy-based internetwork access.
Introducing Visitor-Based Networking and YesWare 1-7 Figure 1-2 YesWare VBN system architecture Software Release 2.
1-8 Introducing Visitor-Based Networking and YesWare YesWare VBN transport systems A YesWare VBN system can deliver service using EtherLoop modem pairs, Ethernet switches, or a combination of both EtherLoop and Ethernet transport systems. The following sections describe these YesWare VBN transport systems.
Introducing Visitor-Based Networking and YesWare 1-9 EtherLoop-VBN transport architecture Figure 1-3 shows the transport architecture of an EtherLoop-VBN system. Figure 1-3 YesWare EtherLoop-VBN transport system EtherLoop terminology - CO=SE and CPE=CE In YesWare modules, different terms are used in different modules for the EtherLoop modem pairs.
1-10 Introducing Visitor-Based Networking and YesWare Ethernet-VBN Ethernet-VBN systems are used in areas such as conference and meeting rooms that have an existing Category 5 (CAT 5) Ethernet LAN infrastructure. Visitor computers connect physically to the ports on Ethernet-VBN switches as they would to a conventional Ethernet 10/100Base-T LAN. Note: The Ethernet-VBN transport system cannot be used simultaneously with the Enhanced Modem Billing method.
Introducing Visitor-Based Networking and YesWare 1-11 Ethernet-VBN architecture requirements As shown in Figure 1-4 on page 1-10, Ethernet-VBN switches are set up in a physical "tree" architecture. The YWS ETH 1 interface is provisioned as the "Network Services System" at the "top" of the tree. The Network Services System is provisioned as a single-port switch and serves as the VBN gateway to the host LAN/WAN.
1-12 Introducing Visitor-Based Networking and YesWare Combined EtherLoop/Ethernet VBN The combined EtherLoop/Ethernet system serves areas where VBN service is required using both EtherLoop lines (CAT 3 wiring) and Ethernet switch ports (CAT 5 wiring). YesWare’s Ethernet Port Billing method is used to support the Ethernet (CAT 5) facility, while YesWare’s Modem Connection Billing is used to serve the EtherLoop (CAT 3) facility.
Introducing Visitor-Based Networking and YesWare 1-13 Figure 1-5 Combined EtherLoop/Ethernet transport system Software Release 2.
1-14 Introducing Visitor-Based Networking and YesWare Service and billing options YesWare systems can provide VBN services in the following functional service areas: • Guest rooms • Conference rooms • Public areas Table 1-3 describes each of these YesWare service options and lists the billing methods available for each YesWare service option. The following sections describe the requirements for the available billing methods.
Introducing Visitor-Based Networking and YesWare 1-15 Guest Room Billing Guest Room Billing is used only in visitor guest rooms. Using this billing method, Internet access charges appear on the Service Detail Record (SDR) log for the room generated by YesWare. Guest Room Billing can be integrated with the facility Property Management System (PMS) so that YesWare service charges appear as an additional "room charge" on the guest room bill.
1-16 Introducing Visitor-Based Networking and YesWare Figure 1-6 Port Use Context in Ethernet Port Configuration Port Use Context=guest Table 1-4 Visitor-based networking Port Use Context requirements Billing Method Port Use Context requirement Guest Room Billing guest Credit Card Billing credit Authorization Code Billing meeting, public, or guest Conference Room Billing meeting Software Release 2.
Introducing Visitor-Based Networking and YesWare 1-17 VBN billing configurations YesWare’s VBN billing configurations are selected and provisioned based on the VBN transport system(s) and billing method(s) required to support the facility. YesWare billing configurations include the following: • Enhanced Modem Billing • Ethernet Port Billing • Modem Connection Billing Table 1-5 lists the compatibility of each of these billing configurations with the YesWare billing methods and transport systems.
1-18 Introducing Visitor-Based Networking and YesWare Enhanced Modem Billing The Enhanced Modem Billing configuration serves facilities that have "allEtherLoop" VBN transport systems. Enhanced Modem Billing uses YesWare billing methods to bill the EtherLoop CO modem port(s) provisioned in the system. CPE modems are not billed, but are treated only as remote connection ports that send traffic from the service area to the CO modem ports.
Introducing Visitor-Based Networking and YesWare 1-19 Ethernet Port Billing The Ethernet Port Billing configuration serves facilities that have EthernetVBN transport systems. Ethernet Port Billing uses YesWare billing functions to provision, manage and bill Ethernet switches on a port-by-port basis. Configuration options and restrictions Ethernet Port Billing configurations support all YesWare service areas and billing methods.
1-20 Introducing Visitor-Based Networking and YesWare Modem Connection Billing The Modem Connection Billing configuration is recommended only in facilities that require combined EtherLoop/Ethernet-VBN transport systems. Modem Connection Billing bills EtherLoop CPE modems based on any connection to the modem. The EtherLoop modem pairs in the system are polled at :17 and :47 of each hour, and the system bills the visitor if any traffic is detected across the modem pair.
Introducing Visitor-Based Networking and YesWare 1-21 Figure 1-9 Combined EtherLoop/Ethernet billing configuration Software Release 2.
1-22 Introducing Visitor-Based Networking and YesWare Visitor access controls The following sections describe YesWare’s methods of controlling service access and authentication capabilities for Enhanced Modem Billing and Ethernet Port Billing configurations. Note: Modem Connection Billing configurations do not support the visitor access controls described in this section.
Introducing Visitor-Based Networking and YesWare 1-23 Visitor authentication YesWare visitor service access is controlled using "authentication" web pages that require the user to provide the appropriate information before access is granted to the Internet or other YesWare services. Authentication page usage YesWare uses several types of authentication pages.
1-24 Introducing Visitor-Based Networking and YesWare VBN web site customization YesWare provides several methods for service providers to customize how the VBN web site looks and functions for visitors. The following sections briefly introduce each of these capabilities. Chapter 10, “Customizing the VBN web site,” describes the operation and use of these YesWare capabilities.
Introducing Visitor-Based Networking and YesWare 1-25 Service-provider home/splash page configuration YesWare allows the administrator to designate the home/splash page on the Internet the visitor will see after connecting and authenticating on the VBN. The URL for the home/splash page is entered in the Branding Configuration dialog as shown in Figure 1-12 on page 1-24.
1-26 Introducing Visitor-Based Networking and YesWare System management and maintenance capabilities YesWare has a variety of system management and maintenance capabilities. Table 1-6 lists some of the YesWare modules and functions related to system management and maintenance.
Introducing Visitor-Based Networking and YesWare 1-27 Installing a YesWare VBN system The process of installing a YesWare VBN system, in broad terms, includes the following: 5 Install the TCP/IP Ethernet local host LAN/WAN network to support the YesWare Server connection (if none existing). 6 Install the YesWare VBN infrastructure (EtherLoop or Ethernet). 7 Configure the YWS on an existing local host LAN/WAN. 8 Provision the VBN infrastructure to support YesWare services.
1-28 Introducing Visitor-Based Networking and YesWare Software Release 2.
2-1 YesWare Server operating system and software modules 2This introduces the purpose and function of the YWS operating system and software modules. YesWare terminology / NSS=YesWare or YWS NSS (Network Services System) was the original name for the suite of software modules now known as YesWare, and also for the hardware platform containing the modules now known as the YesWare Server (YWS). This "legacy" name (NSS) still appears in several places throughout the YesWare modules.
2-2 YesWare Server operating system and software modules YesWare 2.3 software functions and versions Table 2-1 lists the YesWare operating system and modules and the version information for the YesWare 2.3 release. Table 2-1 YesWare module functions and versions Module name Function/Description Elastic Operating Network (EON) Operating system for the YesWare Server (YWS). The EON is a 1.
YesWare Server operating system and software modules 2-3 YWS operating system The YWS operating system is called the Elastic Operating Network (EON). Figure 2-1 shows the"Welcome" screen and prompt you should see after entering the EON login and password. At this point you can enter the commands listed in Table 3-2 on page 3-8.
2-4 YesWare Server operating system and software modules Using YesWare web-based modules All YesWare modules are web-based, and are launched by browsing to the IP address configured for the YesWare Server ETH 0 network interface. Connecting to the ETH 0 interface To access the YWS ETH 0 interface, you must have access to the network where the YWS resides. This can be done with a PC connected over a network, internetwork, simple passive hub, or through a direct connection to the YWS ETH 0 interface.
YesWare Server operating system and software modules 2-5 Figure 2-2 Login dialog YWS web interface login user name and password default The YWS default-configured user name/password login for the web-based interface is manager/manager. YesWare main web page After successfully logging in, the YesWare main page should appear as shown in Figure 2-3 on page 2-6. Software Release 2.
2-6 YesWare Server operating system and software modules Figure 2-3 YesWare main page YesWare modules/sections/functions YesWare modules contain "functions" that execute YesWare operations. These functions are accessed through HTML links and control buttons on the module pages. In the Port Manager and NSS Maintenance modules, the module pages are further divided into "sections.
YesWare Server operating system and software modules 2-7 Figure 2-4 Port Manager module sections and functions EtherLoop Port Provisioning section Port Manager module link Add/Search Port List function "Port Configuration" dialog linked to Add/Search Port List Software Release 2.
2-8 YesWare Server operating system and software modules YesWare web-based modules YesWare web-based modules are used to provision and manage the YesWare system. Figure 2-5 shows the module links on the YesWare main web page for this software release. The remainder of this chapter describes the purpose and function of each of these modules. On-line Help is available! Comprehensive on-line Help is available for all YesWare modules by clicking the Help module link in the YesWare main menu.
YesWare Server operating system and software modules 2-9 About NSS The About NSS module contains version and copyright information for the YesWare software release. Figure 2-6 shows the About NSS module page. Figure 2-6 About NSS module page Software Release 2.
2-10 YesWare Server operating system and software modules Conference Scheduler The Conference Scheduler module is used to schedule and bill YesWare service for Ethernet and/or EtherLoop (ELMo 8 only) equipment located in facility meeting rooms. Figure 2-7 shows the Conference Scheduler page. Chapter 11 describes the operation and use of the Conference Scheduler module. Figure 2-7 Conference Scheduler module page Software Release 2.
YesWare Server operating system and software modules 2-11 Download Utilities The Download Utilities module is used to upgrade the firmware in the EtherLoop modems from either a diskette in the YWS floppy drive or a file located on the workstation/network. Figure 2-8 shows the Download Utilities page. Chapter 15 describes the operation and use of the Download Utilities module. Figure 2-8 Download Utilities module page Software Release 2.
2-12 YesWare Server operating system and software modules Billing Manager The Billing Manager module is used to configure and maintain information used for billing of YesWare end-users, such as the billing system type, rate table, and user authorization codes. YesWare’s Billing Manager allows relatively easy integration with a hospitality Property Management System (PMS) and/or credit-card billing service, as well as generating, viewing and auditing the YWS Service Detail Record (SDR) logs.
YesWare Server operating system and software modules 2-13 EtherCraft The EtherCraft module is used to control and monitor EtherLoop modems from a remote PC/workstation using a Web browser. EtherCraft can check and set modem speeds, set modem training levels, reset modems, get and clear logs, and display modem addresses, availability status, and firmware versions. Figure 2-10 shows the EtherCraft page. Chapter 14 describes the operation and use of the EtherCraft module.
2-14 YesWare Server operating system and software modules InterProxy As mentioned in Chapter 1, the InterProxy module is used to route TCP/IPEthernet traffic from YesWare end-users to an external data network such as the Internet or corporate intranet, regardless of end-user IP configurations. The InterProxy functionality is most appropriate for networks that support “guest” users such as a Visitor-Based Network (VBN). Figure 2-11 shows the InterProxy page.
YesWare Server operating system and software modules 2-15 Modex Daemon The Modex Daemon is the YWS module that controls all direct communication between the EtherLoop modems and the YWS. It is started at bootup and runs continuously.
2-16 YesWare Server operating system and software modules NSS Maintenance The NSS Maintenance module is divided into Password Maintenance and System Maintenance sections. Password Maintenance functions allow you to maintain passwords and user accounts. System Maintenance functions include verifying the system architecture, validating the modem database, setting up the SNMP and Modex Daemon configurations, and other system functions. Figure 2-13 shows the NSS Maintenance page.
YesWare Server operating system and software modules 2-17 Print Services The Print Services module gives YesWare visitors the ability to print to a networked printer such as one located behind the front desk of a hotel or an office services retail store. Figure 2-14 shows the Print Services page. Chapter 12, “Providing visitor printing services” describes the operation and use of the Print Services module. Figure 2-14 Print Services module page Software Release 2.
2-18 YesWare Server operating system and software modules Port Manager The Port Manager allows you to provision EtherLoop modems as well as Ethernet switches and their associated ports. From here, you can also configure the subnet mask, gateway address for the InterProxy-VBN system, branding setup, and check-in/check-out times.
YesWare Server operating system and software modules 2-19 Figure 2-15 Port Manager module page Software Release 2.
2-20 YesWare Server operating system and software modules SNMP Proxy Agent EtherLoop modems do not support the Simple Network Management Protocol (SNMP) directly. However, the modems do support the proprietary Modex protocol. Through the SNMP Proxy Agent and the Modex Daemon modules, the YWS implements both protocols and thus serves as the SNMP proxy agent for the EtherLoop modems. The SNMP proxy agent process is started at bootup and runs continuously.
YesWare Server operating system and software modules 2-21 Install or Upgrade The Install or Upgrade module is used to install new YesWare software or upgrade the software currently installed. Figure 2-17 shows the Install or Upgrade page. Chapter 13, “YesWare security and administration” contains the procedure for using the Install or Upgrade module to upgrade the software on the YWS. Figure 2-17 Install or Upgrade module page Software Release 2.
2-22 YesWare Server operating system and software modules Software Release 2.
SECTION II YESWARE INSTALLATION AND CONFIGURATION Software Release 2.30 Software Release 2.
3-1 YesWare Server host network configuration 3- This chapter describes the methods for connecting to the YesWare Server (YWS) and using the Elastic Operating Network (EON) operating system to configure the YWS on the host network. Chapter topic list This chapter includes the following topics. Topic See YesWare Server page 3-2 YesWare Server console connection methods page 3-4 YesWare Server console interface page 3-7 Chapter task list This section includes the following tasks.
3-2 YesWare Server host network configuration YesWare Server The YWS is used to provision and manage services to the YesWare system infrastructure and clients. The YWS resides as a standard "host" on a local TCP/IP Ethernet host network. YesWare terminology - ETH 0 and ETH 1 The YWS contains two Ethernet 10Base-T network interface cards (NICs) called ETH 0 and ETH 1 (see Figure 3-2 on page 3-3). The ETH 0 interface connects the YWS to the host network.
YesWare Server host network configuration 3-3 Figure 3-2 YWS connections Table 3-1 YWS component connector functions YWS Connector Description/Function Primary Power Switch Controls power to unit. Secondary switch on front not used. AC Power Connector 110/120 V AC input. Keyboard Standard PS2 keyboard interface. USB Connector (not used) Universal Serial Bus (USB) device interface. COM 1 RS232 serial interface to Property Management System (PMS) or serial printer.
3-4 YesWare Server host network configuration YesWare Server console connection methods The YWS "console" consists of connectors located on the back of the YWS used to access the EON interface.
YesWare Server host network configuration 3-5 YWS PC/VT-100 connection Figure 3-4 shows the method for connecting a PC with a VT-100 terminal emulator or a VT-100 terminal to the YWS serial port (COM 2). Figure 3-4 YWS PC or VT-100 terminal console connection YWS telnet connection For the initial configuration of the YWS, you can telnet to the EON interface by connecting directly to the ETH 0 interface using a Category 5 cross-over cable.
3-6 YesWare Server host network configuration Figure 3-5 YWS telnet connections Telnet / Direct PC-toYWS connection Telnet / Network-toYWS connection Software Release 2.
YesWare Server host network configuration 3-7 YesWare Server console interface The YWS console interface is called the Elastic Operating Network (EON). The EON is a command-based interface used to configure the YWS on the host network. The EON can also be used to conduct low-level system diagnostics such as "ping" tests and to view route-table and ETH 0/ETH 1 port assignments. The EON interface can only be accessed through the YWS console interface.
3-8 YesWare Server host network configuration EON commands Table 3-2 lists the EON commands used to set up the YWS. Table 3-2 EON commands Command Function Syntax help Displays this list of EON commands. help route Display YWS routing table. route port Display YWS ETH 0 and ETH 1 port settings. port ping Test basic communications between the YWS, ping client computers, and the host network. passwd Change admin user password.
YesWare Server host network configuration 3-9 Procedure 3-1 Configuring the YWS host network interface This procedure explains how to configure the YWS host network interface (ETH 0) using the EON interface.
3-10 YesWare Server host network configuration Procedure 3-1 (continued) Configuring the YWS host network interface Step Action The EON Configuration Manager "welcome" screen and command prompt appear as follows: 4 At the command prompt (NSS#>), type configure and press . The system displays the following: 5 Enter the valid host network IP address assigned to the YWS ETH 0 network interface. The system should appear similar to the following: —continued— Software Release 2.
YesWare Server host network configuration 3-11 Procedure 3-1 (continued) Configuring the YWS host network interface Step Action 6 Enter the valid network mask (subnet) address assigned to the YWS ETH 0 network interface. The system should appear similar to the following: 7 Enter the valid gateway IP address assigned to the YWS ETH 0 network interface. The system should appear similar to the following: 8 Enter the host name assigned to the YWS ETH 0 network interface.
3-12 YesWare Server host network configuration Procedure 3-1 (continued) Configuring the YWS host network interface Step Action 9 Select the time zone from the list in which the YWS resides, and enter the corresponding number. The system should appear similar to the following: 10 If the configuration settings are correct, type y and press . Go to Procedure 3-2 on page 3-13 to set the system date and time, and Procedure 3-3 on page 3-15 to configure the DNS nameserver.
YesWare Server host network configuration 3-13 Procedure 3-2 Setting the YWS date and time This procedure explains how to use the EON date command to set the date and time for the YWS. Requirements To perform this procedure, you need the following: • a connection to the YWS ETH 0 network interface using one of the methods described in “YesWare Server console connection methods” on page 3-4.
3-14 YesWare Server host network configuration Procedure 3-2 (continued) Setting the YWS date and time Step Action 4 Enter the system date and local time. The system should appear similar to the following: STOP You have completed this task. Software Release 2.
YesWare Server host network configuration 3-15 Procedure 3-3 Setting the DNS nameserver(s) for the YWS Use this procedure to identify the DNS nameserver used by the YWS. The EON nameserver command can be used to display, add or delete the IP address(es) of the DNS nameserver(s) supporting the YWS. Nameserver addresses can be added to the beginning or the end of the nameserver list. This procedure describes each of these command capabilities.
3-16 YesWare Server host network configuration Procedure 3-3 (continued) Setting the DNS nameserver(s) for the YWS Step Action 3 To add a nameserver to the beginning of the list of existing nameserver addresses, type nameserver front at the command prompt (NSS#>), and press . The system should appear similar to the following: 4 To add a nameserver to the end of the list of existing nameserver addresses, type nameserver last at the command prompt (NSS#>), and press .
4-1 InterProxy VBN configuration 4- This chapter presents procedures to configure the InterProxy module to support a Visitor-Based Network (VBN) system. Chapter topic list This chapter includes the following topics. Topic See InterProxy module functions page 4-2 InterProxy VBN system configuration page 4-3 Chapter task list This chapter includes the following tasks. Procedure Task See 4-1 Configuring the InterProxy network connection page 4-9 Software Release 2.
4-2 InterProxy VBN configuration InterProxy module functions The InterProxy module contains the following functions: • Configure InterProxy • Backup InterProxy • Configure Remote Access • Virtual Concierge • Configure Proxy IP Address • TFTP Daemon Manager Of these InterProxy module functions, this chapter covers only the Configure InterProxy function used to configure the YWS to support the visitor computers on the VBN.
InterProxy VBN configuration 4-3 InterProxy VBN system configuration The InterProxy function accepts and routes TCP/IP Ethernet traffic from visitor computers connected through a VBN infrastructure to the YWS ETH 1 interface. InterProxy-VBN clients can connect to the network through an EtherLoop, Ethernet, or combined EtherLoop/Ethernet system infrastructure. Upon reaching the ETH 1 interface, the YWS switches the InterProxy traffic from the ETH 1 interface over to the ETH 0 interface.
4-4 InterProxy VBN configuration InterProxy configuration procedure The system administrator must configure the InterProxy ETH 1 interface for VBN routing. This is done using the InterProxy Configuration Page launched using the Configure InterProxy function. Procedure 4-1 on page 4-9 contains the steps required to configure the InterProxy/ETH 1 interface to serve a VBN system.. CAUTION - Potential network outage The InterProxy attempts to serve as the gateway for any network to which it is connected.
InterProxy VBN configuration 4-5 Figure 4-2 InterProxy Configuration Page Software Release 2.
4-6 InterProxy VBN configuration Table 4-1 InterProxy Configuration Page form entries Form Entry Hostname Description The host name and domain name assigned to the InterProxy. This entry is typically configured using the EON console interface configure command. CAUTION If an invalid host name is submitted for a system that requires service from a DNS nameserver, access using DNS will be lost. IP Address primary port (ETH 0) IP address for the YWS ETH 0 interface.
InterProxy VBN configuration 4-7 Table 4-1 InterProxy Configuration Page form entries Form Entry DHCP Address Pool Start and Pool End Description If the InterProxy needs to support DHCP (Dynamic Host Configuration Protocol) for client computers, select and enter the pool of DHCP addresses available on the InterProxy. Note: If you do not specify a DHCP address range, then all “guest” PCs must be configured with static IP addresses.
4-8 InterProxy VBN configuration Table 4-1 InterProxy Configuration Page form entries Form Entry Network Mask network to exclude Description This is optional. If you specify an IP address for the second logical subnet (see previous field), you must also specify a network mask. Check if network Turn this option on if the network has end-systems using proxy address resolution utilizes proxy arps protocol.
InterProxy VBN configuration 4-9 Procedure 4-1 Configuring the InterProxy network connection Use this procedure to configure the InterProxy/ETH 1 interface to serve a VBN system. Action Step Action 1 Using a PC web browser, browse to the IP address configured for the ETH 0 interface, and login to the YWS. 2 From the YesWare main menu, select the InterProxy module and select the Configure InterProxy function. The "InterProxy Configuration Page" is displayed as shown in Figure 4-2 on page 4-5.
4-10 InterProxy VBN configuration Software Release 2.
5-1 VBN gateway and Network Services System switch configuration 5- This chapter presents procedures to configure the YWS to serve as the gateway for the VBN system. Chapter topic list This chapter includes the following topics. Topic See Configuration requirements page 5-2 Chapter task list This chapter includes the following tasks. Procedure Task 5-1 Provisioning the VBN gateway and Network Services page 5-3 System switch Software Release 2.
5-2 VBN gateway and Network Services System switch configuration Configuration requirements The YWS ETH 1 interface is the "gateway" to the external network used by the EtherLoop modems and/or Ethernet switches in the VBN. The "Network Services System" is the switch supporting the VBN system of EtherLoop modems and/or Ethernet switches. The system administrator must provision the ETH 1 interface as the Network Services System switch and also as the gateway serving the VBN.
VBN gateway and Network Services System switch configuration 5-3 Procedure 5-1 Provisioning the VBN gateway and Network Services System switch Use this procedure to provision the InterProxy ETH 1 interface as VBN gateway and Network Services System switch. Note: See Chapter 7, “Provisioning the Ethernet-VBN switches and ports” for more information about the general requirements for Ethernet switch provisioning and the Network Services System function in an EthernetVBN architecture.
5-4 VBN gateway and Network Services System switch configuration Procedure 5-1 (continued) Provisioning the VBN gateway and Network Services System switch Step Action 5 In the System Setup section, select Add/Search Gateway Address. The Gateway Address Configuration dialog appears as shown in Figure 5-2 on page 5-4. Figure 5-2 Gateway Address Configuration dialog 6 Enter the ETH 1 IP address in the Gateway Address field, and click Add. 7 In the System Setup section, select Add/Search Subnet Mask.
VBN gateway and Network Services System switch configuration 5-5 Procedure 5-1 (continued) Provisioning the VBN gateway and Network Services System switch Step Action 9 In the Ethernet Switch and Port Provisioning section, select Add/Search Switch Information. 10 Select the switch address corresponding to ETH 1, and click the edit link or the Search button to launch the Switch Configuration dialog.
5-6 VBN gateway and Network Services System switch configuration Procedure 5-1 (continued) Provisioning the VBN gateway and Network Services System switch Table 5-1 Network Services System switch settings Switch Setting Entry Description/Requirement Switch type Select the "Network Services System " switch type Switch IP Address Select the IP address of the ETH 1 interface provisioned previously in the Add Switch Address dialog.
VBN gateway and Network Services System switch configuration 5-7 Procedure 5-1 (continued) Provisioning the VBN gateway and Network Services System switch Step Action 12 In the Ethernet Switch and Port Provisioning section, select Add Ports to launch the Select A Switch dialog as shown in Figure 5-5. Figure 5-5 Add Ports / Select A Switch dialog 13 Select the Network Services System switch and click Continue to launch the Configure Port dialog.
5-8 VBN gateway and Network Services System switch configuration Procedure 5-1 (continued) Provisioning the VBN gateway and Network Services System switch Table 5-2 Network Services System port settings Port Setting Configuration Requirement Switch IP Address Select the IP address of the Network Services System switch. Port Number In the Add Ports / Configure Port dialog, this number is automatically incremented.
SECTION III YESWARE SERVICE PROVISIONING Software Release 2.30 Software Release 2.
6-1 EtherLoop system provisioning 6- This chapter contains instructions for provisioning EtherLoop-VBN transport systems in Enhanced Modem Billing and Modem Connection Billing configurations. This chapter also includes instructions for provisioning nonbilled EtherLoop modem management systems.
6-2 EtherLoop system provisioning Enhanced Modem Billing provisioning requirements The major tasks required to provision an Enhanced Modem Billing configuration include the following: 1 Provision the EtherLoop CO modem database. 2 Enable the Enhanced Modem Billing feature. 3 Configure the port(s) on the CO modems. Procedure 6-1 on page 6-3 describes the steps to complete these tasks.
EtherLoop system provisioning 6-3 Procedure 6-1 Provisioning Enhanced Modem Billing Use this procedure to configure the YWS to use Enhanced Modem Billing. Enhanced Modem Billing firmware requirement Enhanced Modem Billing requires that all EtherLoop modems in the system use Generation 2.09 (or higher) firmware. If the system contains EtherLoop modems running the older Generation 1 firmware, they must first be upgraded to Gen 2.09 (or higher) before performing this procedure.
6-4 EtherLoop system provisioning Procedure 6-1 (continued) Provisioning Enhanced Modem Billing Step Action 4 Select the Find New Modems function to launch the "Discover EtherLoop Modems" dialog as shown in Figure 6-11. Figure 6-2 Discover EtherLoop Modems dialog 5 Click "Autodetect Modems" button. After procesing the command, the "Discover EtherLoop Modems" dialog reappears with a list of the modems detected by MAC address as shown below.
EtherLoop system provisioning 6-5 Procedure 6-1 (continued) Provisioning Enhanced Modem Billing Step Action 6 Select Port Manager from the YesWare Main Menu to return to the Port Manager module page. 7 In the EtherLoop Modem Provisioning section, select the View/Edit CO Modem Table function. 8 Click the edit link next to the desired modem to launch the Co Modem Configuration dialog. 9 Use the Co Modem Configuration dialog to complete the site-specific provisioning of all CO modems in the system.
6-6 EtherLoop system provisioning Procedure 6-1 (continued) Provisioning Enhanced Modem Billing Table 6-1 CO modem provisioning parameters CO Modem Configuration Parameters Parameter description CO MAC Address MAC address of the CO modem automatically generated by Find New Modems function, or manually entered here. (REQUIRED) Note: MAC addresses manually entered in this field without colons will be rejected. See “EtherLoop modem MAC addressing conventions” on page 6-25.
EtherLoop system provisioning 6-7 Procedure 6-1 (continued) Provisioning Enhanced Modem Billing Step Action 10 Select Port Manager from the YesWare Main Menu to return to the Port Manager module page. 11 Select Enable/Disable Enhanced Modem Billing from the EtherLoop Port Provisioning section to launch the Port-Based Modem Billing Manager dialog (see Figure 6-5). The dialog text explains the YesWare billing options and indicates whether Enhanced Modem Billing is enabled.
6-8 EtherLoop system provisioning Procedure 6-1 (continued) Provisioning Enhanced Modem Billing Step Action 12 In the Port-Based Modem Billing Manager dialog, verify that Enhanced Modem Billing is not enabled. Click the "Use Enhanced Modem Billing" button to enable Enhanced Modem Billing. 13 When the system displays that Enhanced modem billing is enabled, select Port Manager from the YesWare Main Menu to return to the Port Manager module page.
EtherLoop system provisioning 6-9 Procedure 6-1 (continued) Provisioning Enhanced Modem Billing Step Action 16 Use the Port Configuration dialog to complete the site-specific provisioning of the port. 17 Click the "update" button to configure the port in the database. After the system processes the command, the system will display the Port List table with the new port configuration added to the end of the port list.
6-10 EtherLoop system provisioning Procedure 6-1 (continued) Provisioning Enhanced Modem Billing Table 6-2 Port Configuration dialog settings Port Setting Configuration Requirement Switch IP Address Autofilled CO modem MAC address from the Port List table. Do not modify in this dialog. Port Number Autofilled CO modem port number from the Port List table. Do not modify in this dialog.
EtherLoop system provisioning 6-11 Procedure 6-1 (continued) Provisioning Enhanced Modem Billing Step Action 19 Select NSS Maintenance from the YesWare Main Menu to launch the NSS Maintenance module page. 20 In the System Maintenance section, click Validate the Modem Database. The EtherLoop Modem Database Validation dialog should display the results of the database validation similar to the one shown in Figure 6-15.
6-12 EtherLoop system provisioning Modem Connection Billing provisioning requirements The major tasks required to provision a Modem Connection Billing configuration include the following: 1 Provision the EtherLoop CO modem database. 2 Provision the EtherLoop CPE modem database. Procedure 6-2 on page 6-13 describes the steps to complete these tasks.
EtherLoop system provisioning 6-13 Procedure 6-2 Provisioning Modem Connection Billing Use this procedure to build the database of EtherLoop modems managed by the YWS. Using the Find New Modems function To use the Find New Modems function described in this procedure, the EtherLoop modems must reside on the same LAN segment as the YWS. Action Step Action 1 Select the Set ModeX daemon information function in the System Maintenance section of the NSS Maintenance module.
6-14 EtherLoop system provisioning Procedure 6-2 (continued) Provisioning Modem Connection Billing Step Action 5 Click "Autodetect Modems" button. After procesing the command, the "Discover EtherLoop Modems" dialog reappears with a list of the modems detected as shown below. Figure 6-12 Discover Modems Dialog —continued— Software Release 2.
EtherLoop system provisioning 6-15 Procedure 6-2 (continued) Provisioning Modem Connection Billing Step Action 6 Select Port Manager from the YesWare Main Menu to return to the Port Manager module page. 7 In the EtherLoop Modem Provisioning section, use the Co Modem Configuration dialog to complete the site-specific provisioning of the CO modems. Figure 6-13 shows the default Co Modem Configuration dialog. Table 6-3 on page 6-16 lists and describes the acceptable and required entries for this dialog.
6-16 EtherLoop system provisioning Procedure 6-2 (continued) Provisioning Modem Connection Billing Table 6-3 CO modem provisioning parameters CO Modem Configuration Parameters Parameter description CO MAC Address MAC address of the CO modem automatically generated by Find New Modems function, or manually entered in this field. (REQUIRED) Note: MAC addresses manually entered in this field without colons will be rejected. See “EtherLoop modem MAC addressing conventions” on page 6-25.
EtherLoop system provisioning 6-17 Procedure 6-2 (continued) Provisioning Modem Connection Billing Step Action 8 In the EtherLoop Modem Provisioning section, use the Cpe Modem Configuration dialog to complete the site-specific provisioning of the CPE modems. Figure 6-14 shows the default Cpe Modem Configuration dialog. Table 6-4 on page 6-18 lists and describes the acceptable and required entries for this dialog. Figure 6-14 Cpe Modem Configuration dialog —continued— Software Release 2.
6-18 EtherLoop system provisioning Procedure 6-2 (continued) Provisioning Modem Connection Billing Table 6-4 CPE modem provisioning parameters CPE Modem Configuration Parameter/Entry description Parameters CPE MAC Address (REQUIRED) Enter the MAC address of the CPE modem (may be automatically discovered using the Find New Modems function or entered manually in this field). MAC addresses manually entered in this field without colons will be rejected.
EtherLoop system provisioning 6-19 Procedure 6-2 (continued) Provisioning Modem Connection Billing Step Action 9 If required, add modem MAC address privacy filters as described in Procedure 13-1 on page 13-3. 10 Select NSS Maintenance from the YesWare Main Menu to launch the NSS Maintenance module page. 11 In the System Maintenance section, click Validate the Modem Database. The EtherLoop Modem Database Validation dialog appears similar to the one shown in Figure 6-15.
6-20 EtherLoop system provisioning EtherLoop modem management provisioning requirements The main purpose of the YWS is to serve and bill InterProxy clients connected to the ETH 1 interface. However, the YWS can also serve to monitor and manage EtherLoop modems connected to TCP/IP (non-InterProxy) network clients. EtherLoop modem management systems serve EtherLoop modems in networks where InterProxy and YesWare billing capabilities are not required.
EtherLoop system provisioning 6-21 Figure 6-16 YWS in an EtherLoop modem management system TCP/IP LAN EtherLoop-TCP/IP Clients RJ-45 10Base-T C O /SE M o d e m s C PE /C E M o de m s IP or MAC Address TCP/IP LAN or WAN RJ -45 Valid IP Address IP or MAC Address YWS Eth0 10Base-T YesWare Server YWS Host Network EtherLoop modem management systems have the following requirements and features: • client computers connected to EtherLoop modems must have valid IP addresses for the network on which they
6-22 EtherLoop system provisioning Procedure 6-3 Provisioning EtherLoop modem management with a resident YWS The following procedure lists the steps to create and provision an EtherLoop modem management system with the YWS as a permanent resident on the same LAN segment as the EtherLoop modems. This procedure should be done after the EtherLoop client modems have been installed on the host network. Action Step Action 1 Install the EtherLoop modems on the host network.
EtherLoop system provisioning 6-23 Procedure 6-4 Provisioning EtherLoop modem management with a non-resident YWS The following procedure lists the steps to create and provision an EtherLoop modem management system with the YWS as a permanent resident on a different LAN segment from the EtherLoop modems. This procedure should be done after the EtherLoop client modems have been installed on the host network. Action Step Action 1 Install the EtherLoop modems on the host network.
6-24 EtherLoop system provisioning Procedure 6-4 (continued) Provisioning EtherLoop modem management with a non-resident YWS Step Action 9 Provision each CO and CPE modem with a valid TCP/IP address configuration for the LAN on which the EtherLoop modems reside.
EtherLoop system provisioning 6-25 EtherLoop modem MAC addressing conventions The EtherLoop MAC address is the hardware media access control (MAC) address of the CO/CPE modems. MAC addresses for EtherLoop modems can be auto-detected using the Find New Modems function or entered manually. The MAC address is made up of six hexadecimal pairs of numbers, and can be found on a sticker on the CO modem unit.
6-26 EtherLoop system provisioning Software Release 2.
7-1 Provisioning the Ethernet-VBN switches and ports 7Chapter topic list This chapter includes the following topics. Topic See Ethernet-VBN switch architecture and configuration requirements page 7-5 Ethernet-VBN switch and port configuration page 7-6 Ethernet-VBN switch maintenance page 7-21 Chapter task list This chapter contains the following tasks.
7-2 Provisioning the Ethernet-VBN switches and ports Ethernet-VBN switch architecture and configuration requirements The major steps required to provision switches in an Ethernet-VBN system include the following: 1 Install the Ethernet switches on the visitor (ETH 1) network. 2 Install the YWS ETH 1 interface on the same LAN segment as the Ethernet-VBN switches.
Provisioning the Ethernet-VBN switches and ports 7-3 Ethernet-VBN configuration requirements When installing and configuring the Ethernet-VBN system, the following system design and architecture requirements must be observed: 1 The YWS ETH 1 interface must be configured as a "Network Services System" switch (see Chapter 5). 2 The Ethernet-VBN system must be installed in a physical (as opposed to virtual) tree configuration, with the YWS ETH 1 interface configured at the “top” of the system tree.
7-4 Provisioning the Ethernet-VBN switches and ports Ethernet-VBN configuration example notes Note the following about the example shown in Figure 7-1 on page 7-3: • YWS ETH 1 has no parent switch • YWS ETH 1 is the parent of SW#1 • SW#1 is the downlink of YWS ETH 1 (the YWS can have only one downlink) • SW#1 is the parent of SW#2, SW#3, and SW#4 • SW#2, SW#3, and SW#4 are downlinks from SW#1 Also, assume the following for the switches shown in Figure 7-1 on page 7-3: Parent Switch/Port Downlink Switch /
Provisioning the Ethernet-VBN switches and ports 7-5 Ethernet-VBN TCP/IP addressing guidelines All Ethernet-VBN switches must have assigned IP addresses. Ethernet-VBN IP addresses must be identically assigned in both the switch console interface and the YesWare Port Manager module.
7-6 Provisioning the Ethernet-VBN switches and ports Ethernet-VBN switch and port configuration This section describes the configuration requirements to use the BayStack 303- or Cisco 2900XL-compatible switches in Ethernet-VBN switches as described in “Ethernet-VBN switch architecture and configuration requirements” on page 7-2. Procedure 7-1 on page 7-10 describes the Ethernet-VBN switch and port configuration procedure.
Provisioning the Ethernet-VBN switches and ports 7-7 Table 7-2 InterProxy-VBN/Ethernet switch configuration Switch Setting Entry Description/Requirement Switch type Choose "BayStack 303" or "Cisco 2900XL" for all Ethernet-VBN switches. Switch IP Address Select the IP address of a switch provisioned previously using the Add/Search Switch Address function. Gateway Address Select the Gateway address provisioned previously using the Add Gateway Address function.
7-8 Provisioning the Ethernet-VBN switches and ports Port configuration Port configuration for Ethernet-VBN switches is done in the Port Manager / Ethernet Switch and Port Provisioning section using the Add Ports, Add/Search Port List and View/Edit Port Table functions. Table 7-3 describes the purpose and use of these port configuration functions.
Provisioning the Ethernet-VBN switches and ports 7-9 Table 7-4 Ethernet-VBN port configuration settings Port Setting Configuration Requirement Switch IP Address Select the IP address of a switch provisioned previously using the Add/Search Switch Address function. Port Number The number of the port being provisioned. This number is automatically incremented in the Add Ports function dialog, or manually entered in the Add/Search Port List function dialog.
7-10 Provisioning the Ethernet-VBN switches and ports Procedure 7-1 Provisioning the Ethernet-VBN switch and port database This procedure describes the steps required to provision the Ethernet-VBN switches and ports. Action Step Action 1 From the YesWare Main Menu, choose Port Manager. The Port Manager menu appears. 2 In the Ethernet Switch and Port Provisioning section, select Add/Search Switch Address.
Provisioning the Ethernet-VBN switches and ports 7-11 Procedure 7-1 (continued) Provisioning the Ethernet-VBN switch and port database Step Action 4 In the Ethernet Switch and Port Provisioning section, select Add/Search Switch Information. 5 Select a switch IP address, and click the edit link or the Search button to launch the Switch Configuration dialog. 6 In the Switch Configuration dialog, provision the IP address as the "BayStack 303" or "Cisco 2900XL" switch.
7-12 Provisioning the Ethernet-VBN switches and ports Procedure 7-1 (continued) Provisioning the Ethernet-VBN switch and port database Step Action 7 In the Ethernet Switch and Port Provisioning section, select Add Ports to launch the Select A Switch dialog as shown in Figure 7-6. Figure 7-6 Add Ports / Select A Switch dialog 8 Select the Ethernet-VBN switch being provisioned and click Continue. The Configure Port dialog is displayed with all ports added for the switch.
Provisioning the Ethernet-VBN switches and ports 7-13 Procedure 7-1 (continued) Provisioning the Ethernet-VBN switch and port database Step Action Note the following about the example port configuration is shown in Figure 7-7 on page 7-12: 9 • The "Port Status" field must be enabled for the port to function. • The "Validation Policy" must be enabled to ensure that users have to authenticate themselves to use the service. • The "Port Use Context" for "downlink" ports should be set to "Network.
7-14 Provisioning the Ethernet-VBN switches and ports Procedure 7-2 Verifying Ethernet-VBN Architecture After you configure all the ports for a switch, use the following procedure to quickly validate the YesWare configuration database and verify the switches and ports are provisioned in the correct hierarchy. This function presents the verification results and generates a line illustration Switch Diagram of the provisioned system architecture.
Provisioning the Ethernet-VBN switches and ports 7-15 Procedure 7-2 (continued) Verifying the Network Architecture The Database Validation screen presents the results of the verification for the YesWare Ethernet switch and port settings shown in Table 7-5. Table 7-5 Validation Item Description Switch hierarchy Displays the results (passed or failed) of the switch hierarchy verification. Switch hierarchy verification failure can result from a variety of reasons.
7-16 Provisioning the Ethernet-VBN switches and ports Procedure 7-3 Testing the Ethernet-VBN system Configuration After you have provisioned all ports for a switch and have verified the system architecture, use the following procedure to test the configuration of each port.
Provisioning the Ethernet-VBN switches and ports 7-17 Procedure 7-3 (continued) Testing the Ethernet-VBN system Configuration Step Action 4 Verify the port performs according to its provisioned settings as in the following examples: • If the port is provisioned as “enabled” status, verify it allows access to the Internet. • If the port is provisioned as “disabled” status, verify it does not allow access to the Internet.
7-18 Provisioning the Ethernet-VBN switches and ports Procedure 7-4 Viewing Real-Time Switch Status This function displays the status of VBN switches in the YesWare database listed by IP address. Using this function, you can view the "up/down" status of all switches in the database, view packet traffic and status data for all the ports on an individual switch, and configure the time interval used to refresh switch status data.
Provisioning the Ethernet-VBN switches and ports 7-19 Procedure 7-4 (continued) Viewing Real-Time Switch Status 3 To view the port-by-port status of an individual switch, click the underlined IP for the switch. The system displays the status of each port on that switch, including packet traffic data. Figure 7-11 shows an example of this screen. Figure 7-11 Port status on a VBN switch —continued— Software Release 2.
7-20 Provisioning the Ethernet-VBN switches and ports Procedure 7-4 (continued) Viewing Real-Time Switch Status Step Action 4 To configure the refresh time for updating switch status, click the Config button, and enter the refresh time (in seconds) on the VBN Switch Query Config screen. Figure 7-11 shows an example of this screen. Figure 7-12 VBN Switch Query Config dialog STOP You have completed this task. Software Release 2.
Provisioning the Ethernet-VBN switches and ports 7-21 Ethernet-VBN switch maintenance YesWare has the following maintenance capabilities that can be used to maintain Ethernet-VBN switches. Procedure Task 7-5 Upgrading Ethernet-VBN switch firmware using page 7-22 TFTP and HTTP Proxy 7-6 Using the Refresh Switches function page 7-25 7-7 Using the View Database function page 7-26 7-8 Testing Ethernet-VBN ports page 7-27 Software Release 2.
7-22 Provisioning the Ethernet-VBN switches and ports Procedure 7-5 Upgrading Ethernet-VBN switch firmware using TFTP and HTTP Proxy YesWare allows system administrators to upgrade Ethernet-VBN switch firmware using the switches’ web-based graphical user interface (GUI). This procedure describes how to do this using the InterProxy module’s TFTP and HTTP Proxy capabilities.
Provisioning the Ethernet-VBN switches and ports 7-23 Procedure 7-5 (continued) Upgrading Ethernet-VBN switch firmware using TFTP and HTTP Proxy Step Action 4 Return to the InterProxy main page and select the Configure Proxy IP Address function. 5 In the "IP Address" field, enter the IP address of the PC performing the upgrade and click the "Add Address" button. See Figure 7-14.
7-24 Provisioning the Ethernet-VBN switches and ports Procedure 7-5 (continued) Upgrading Ethernet-VBN switch firmware using TFTP and HTTP Proxy Step Action 7 Apply the changes to the browser and close and re-open the browser. You should now be able to browse to the Ethernet-VBN switch IP addresses on the ETH 1 side of the YWS. 8 Browse to the IP address of the Ethernet-VBN switch to receive the firmware upgrade.
Provisioning the Ethernet-VBN switches and ports 7-25 Procedure 7-6 Using the Refresh Switches function Use this function to re-enable all switches connected to the YWS. The Refresh Switches function is located in the System Tools section of Port Manager. Action Step Action 1 Click the Refresh Switches link to initiate the "Switch Connectivity Refresh" process. This process refreshes all switches in the system firewall and reenables all switches in the database.
7-26 Provisioning the Ethernet-VBN switches and ports Procedure 7-7 Using the View Database function Use this function to view, in text form, the system port and switch table databases. Clicking on the Port Table Data and Switch Table Data links displays these database tables as TAB delimited files. Shift-click on the links to save either one to a file. The TAB delimited file format can be viewed with Excel or another spreadsheet viewer. Figure 7-17 shows the "View Port/Switch Data" dialog.
Provisioning the Ethernet-VBN switches and ports 7-27 Procedure 7-8 Testing Ethernet-VBN ports Use this function to set/view the test mode for system ports Figure 7-18 shows the "Port Test Mode Manager" dialog. Figure 7-18 Port Test Mode Manager dialog View Port Test Results Use this function to view logs generated as a result of Port Tests. Port Test Use this function to execute a test on a port. Ports must be in test mode before a test can be executed. STOP You have completed this task.
7-28 Provisioning the Ethernet-VBN switches and ports Software Release 2.
8-1 YesWare service billing 8- This chapter describes how to configure the Billing Manager module and implement the Guest Room Billing, Credit Card Billing, and Authorization Code Billing methods. Note: Conference Room Billing is provisioned and managed using the Conference Scheduler module and is covered in Chapter 11. Chapter topic list This chapter includes the following topics.
8-2 YesWare service billing Billing Manager feature description The Billing Manager module is used to provision and manage Guest Room Billing, Credit Card Billing, and Authorization Code Billing on the YWS. The Billing Manager module is used for the following functions for each of these billing methods: • Guest Room Billing: configure guest room Check-In/Check-Out times, rates, and the interface to the Property Management System (PMS) • Credit-Card Billing: configure credit-card billing with the Authorize.
YesWare service billing 8-3 Guest Room Billing To configure the Billing Manager to use Guest Room Billing, the YesWare administrator must complete the following tasks: • Provision YesWare ports with the guest Port Use Context as described earlier in this document • Configuring the guest room billing protocol and time settings • Configure the guest room billing rate(s) and assign the rate(s) to the YesWare guest room ports • Integrate the YWS into the facility PMS (optional) The following sections and Proce
8-4 YesWare service billing Procedure 8-1 Configuring Guest Room Billing Use this procedure to select and configure the billing system protocol and rate charges as described in “Guest Room Billing” on page 8-3. Action Step Action 1 From the YesWare Main Menu, select the Billing Manager module. 2 Click the Configure Billing Manager function link to launch the Configure Billing Manager dialog. Figure 8-2 shows the default dialog.
YesWare service billing 8-5 Procedure 8-1 (continued) Configuring Guest Room Billing Step Action 3 Complete the Configure Billing Manager dialog according to the specifications listed in Table 8-1. Table 8-1 Configure Billing Manager dialog settings Setting Specification PMS Protocol Select the protocol used to interface with the PMS, if applicable. See Chapter 9 for more information. Check-in Time Select HH:MM for 12 hour clock from the pull-down list.
8-6 YesWare service billing Procedure 8-1 (continued) Configuring Guest Room Billing Step Action 5 Click the Yes button to accept the changes. (Clicking No will discard the changes and the system will return to the Configure Billing Manager dialog). 6 When the system displays "The following settings have been commited:", click the Back To Billing Manager link. 7 Click Add/Search Rate Table to launch the Rate Configuration dialog. Figure 8-3 shows an example of this dialog.
YesWare service billing 8-7 Credit Card Billing To configure the Billing Manager to use Credit Card Billing, the YesWare administrator must complete the following tasks: • Provision YesWare ports with the credit Port Use Context • obtain a merchant account with the Authorize.Net Internet credit-card processing company • Configure Credit Card Billing using the Billing Manager module The following sections describes the requirements to set up Credit Card Billing in the YesWare system.
8-8 YesWare service billing Procedure 8-2 Configuring Credit-Card Billing Use this procedure to configure Credit Card Billing in the YesWare Billing Manager module. Action Step Action 1 From the YesWare Main Menu, select the Billing Manager module. 2 Click the Configure Credit Card Billing function link to launch the credit-card service selection dialog. 3 Verify that Authorize.Net is the service selected and click the "Next" button. See Figure 8-4.
YesWare service billing 8-9 Procedure 8-2 (continued) Configuring Credit-Card Billing Step Action 4 Figure 8-5 shows the default dialog used to configure the YWS credit card billing account. Enter the user ID assigned to the account by Authorize.Net in the "CUSTID:" field of this dialog. Enter the account password in the "LOGIN:" field. CAUTION: Do NOT modify the "AUTHNET_IPADDR:" field.
8-10 YesWare service billing Authorization Code Billing To configure the Billing Manager to use Authorization Code Billing, the YesWare administrator must complete the following tasks: • Provision YesWare ports with the meeting, public, or guest Port Use Context • generate and print duplicate hard-copy Authorization Codes The following sections describes the requirements to use Authorization Code Billing in the YesWare system.
YesWare service billing 8-11 Procedure 8-3 Generating Authorization Codes Use this procedure to procedure to generate the Authorization Codes given to the visitors paying for service on the YesWare system. Requirement The YesWare administrator or operator must know the rate charges and durations used according to the facility rate schedule requirements. Action Step Action 1 From the YesWare main menu, choose Billing Manager. The Billing Manager menu appears.
8-12 YesWare service billing Procedure 8-3 (continued) Generating Authorization Codes 4 In the Total Charge field, enter the total charge billed to the Authorization Code. The entry in this field must be decimal to two places, with no dollarsign. 5 Click Submit to enter the authorization code. A confirmation screen appears as shown below.
YesWare service billing 8-13 YesWare billing record management capabilities This section describes YesWare’s capabilities to view and manage billing records generated by Guest Room Billing, Credit Card Billing, and Authorization Code Billing. Conference Room Billing records are managed using the Conference Scheduler Module as described in Chapter 11. Table 8-2 lists the record management functions available in the Billing Manager module.
8-14 YesWare service billing Guest Room Billing record management YesWare keeps Service Detail Record (SDR) logs for all ports provisioned on the YWS that use Guest Room Billing. SDR log details include the date/time the SDR log was created, PMS configuration data (see Chapter 9), and the fee charged for the service. The Billing Manager module contains functions to view and audit SDR logs.
YesWare service billing 8-15 Procedure 8-4 Retrieving and deleting SDR logs using ftp Use this procedure to retrieve and delete SDR logs on the YWS using ftp. Some service-providers may want to automate this procedure using a custom software script/program. Requirements This procedure requires the following: • basic knowledge of ftp commands • ftp client computer with network access to the YWS Action Step Action 1 Start the ftp client application. 2 Open a connection to the YWS using port 22221.
8-16 YesWare service billing Procedure 8-4 (continued) Retrieving and deleting SDR logs using ftp Step Action 5 To change the ftp data transfer mode to the required binary mode, enter binary. 6 Use the ftp commands to retrieve or delete the SDR logs as required. The login completed in step 4 opens the directory containing the SDR logs, so no change-directory commands are required. SDR log files are stored in the following format: [date].SDR. For example, 20000824.SDR is the SDR log for August 24, 2000.
YesWare service billing 8-17 Procedure 8-5 Creating billing record reports Use this procedure and the View Billing Logs function to create and download reports for any or all of the three billing record logs (SDR logs, credit transaction logs, Auth Code logs). Requirements This procedure requires a client computer with network access to the YWS Action Step Action 1 Browse to the YWS, login and select the Billing Manager module link.
8-18 YesWare service billing Procedure 8-5 (continued) Creating billing record reports Figure 8-10 Example billing report —continued— Software Release 2.
YesWare service billing 8-19 Procedure 8-5 (continued) Retrieving and deleting SDR logs using ftp Step Action 4 To download and save the billing report, click the choose and click the Comma-Delimited or Tab-Delimited button. Figure 8-11 shows an example tab-delimited billing report based on the report shown in Figure 8-10 on page 8-18. 5 Save the report file as required. Figure 8-11 Example tab-delimited billing report STOP You have completed this task. Software Release 2.
8-20 YesWare service billing Software Release 2.
9-1 YesWare PMS integration 9- This chapter describes how to integrate the YWS into a Property Management System (PMS) for facilities using Guest Room Billing. Chapter topic list This chapter includes the following topics.
9-2 YesWare PMS integration YesWare PMS integration process Integrating the YWS into a facility PMS consists of the following major steps: • configure the EtherLoop or Ethernet transport system ports to support Guest Room Billing as described earlier in this document • configure the Billing Manager protocol and time settings using the Configure Billing Manager function, and billing rates using Add/Search Rate Table function as described in Chapter 8 • connect the YWS to the PMS interface • configure the PM
YesWare PMS integration 9-3 YWS direct connection to PMS Figure 9-1 shows the YWS direct connection to the PMS. Note the following requirements about this type of connection: • The direct connection method can be used only when the YWS is less than 50 ft (15 m) from the PMS interface. • The YWS is a PC, which in the RS232 connection standard is a Data Terminal Equipment (DTE) device.
9-4 YesWare PMS integration YWS isolated connection to PMS Figure 9-2 shows the YWS isolated connection to the PMS. The isolated connection method consists of connecting a pair of short-haul modems or line drivers between the YWS and the PMS. The modem pair serves to boost the signal from the YWS to the PMS to ensure the integrity of the signal, and also isolate the YWS from damage caused by transient voltages.
YesWare PMS integration 9-5 Procedure 9-1 Connecting the YWS to the PMS Use this procedure to select and connect the YWS to the PMS as described in “YesWare PMS integration process” on page 9-2.
9-6 YesWare PMS integration Procedure 9-1 (continued) Connecting the YWS to the PMS Action Step Action 1 Connect an RS232 cable from the PMS RS232 serial interface to one end of a mini-tester similar to the one shown in Figure 9-3 on page 9-5. 2 With the device powered off, connect the known DTE device using the second RS232 straight cable to the other end of the RS232 mini-tester. If connecting to the YWS COM 1 port, the cable connector must be a 9-pin female. 3 Start the known DTE device.
YesWare PMS integration 9-7 HOBIC AckNak configuration requirements The HOBIC AckNak configuration uses the acknak file to format output and communicate with the PMS. Several standard billing formats can be used in HOBIC AckNak configurations to integrate the YWS into the facility PMS, including Promus/System 21, Hitachi Standard, and HOBIS Merge. Figure 9-4 shows the default acknak file configuration dialog.
9-8 YesWare PMS integration Table 9-1 HOBIC AckNak configuration settings HOBIC AckNak Default setting Value Specifications and Entry Requirements localFacility 2 YWS internal log facility. Do not edit this field. digits ’’ Enter the digits between single quotes that the PMS system should substitute for the dialed digits in ALL call records fields.
YesWare PMS integration 9-9 Table 9-1 (continued) HOBIC AckNak configuration settings HOBIC AckNak Default setting Value Specifications and Entry Requirements delay 5 Enter the number of 100ms intervals to wait before responding to a message. This field sets the amount of time YWS waits to send the next message, assuming the previous message was successfully acknowledged or placed in the FIFO buffer for a retry. By default, the YWS is set to wait for 5x100ms or 0.5 seconds between messages sent.
9-10 YesWare PMS integration Table 9-1 (continued) HOBIC AckNak configuration settings HOBIC AckNak Default setting Value Specifications and Entry Requirements tocFieldLetter Enter the alphanumeric designator used to indicate the type of call to the PMS in the outgoing call record. The YWS only uses this field if outputType setting is >=3 (see outputType field description). A Note: For Promus/System 21 systems, use the default value of A. Hitachi Standard and HOBIS Merge systems ignore this field.
YesWare PMS integration 9-11 Table 9-2 Output Type 2 call record format Call Record Position Format Specification 0-3 4 digit sequence number 5-7 characters "HTL" 9-13 date in format MM/DD 15-18 4 digit room number 20-24 time in format HH:MM 26-29 4 digit duration 31-37 service charge in format $DDD.CC 39-46 dialed digits format NNN-NNNN 47 blank over 1 digit BCC (block-check character) 48 ETX (end-of-transmission) Software Release 2.
9-12 YesWare PMS integration HOBIC One-Way configuration requirements The HOBIC One-Way configuration uses the hobic file to format output. The HOBIC One-Way configuration does not send an ENQ, and does not accept acknowledgment after a record is sent. This configuration should only be used for output from the YWS to a serial printer. Figure 9-5 shows the default hobic file configuration dialog. Table 9-3 on page 9-13 contains the entry requirements and recommendations for each field in the dialog.
YesWare PMS integration 9-13 Table 9-3 HOBIC One-Way configuration settings HOBIC One-Way Default setting Value Specifications and Entry Requirements localFacility 2 YWS internal log facility. Do not edit this field. digits ’’ Enter the digits between single quotes that the PMS system should substitute for the dialed digits in ALL call records fields.
9-14 YesWare PMS integration Procedure 9-2 Configuring the PMS Interface Use this procedure to configure the PMS interface using the Billing Manager Configure PMS Interface function. Action Step Action 1 From the YesWare Main Menu, select the Billing Manager module. 2 Click the Configure PMS Interface function link to launch the Edit Billing dialog. See Figure 9-6.
YesWare PMS integration 9-15 Procedure 9-3 Generating a Test Record for the PMS The following procedure explains how to generate a test record after the YWS has been connected to the PMS and the PMS has been configured as described earlier in this chapter. Action Step Action 1 From the YesWare main menu, choose Billing Manager. The Billing Manager menu appears. 2 Click Generate Test Record. The Generate Test Record dialog appears.
9-16 YesWare PMS integration SNMP notification of PMS link disruption Occasionally, the PMS loses its ability to communicate with one or all of the posting devices that send billing and guest information to the PMS. This loss of communication may be intentional, such as when the night auditor reconciles the billing records for each guest. However, the loss of communication can also indicate a communications problem between a posting device such as the YWS and the facility PMS.
YesWare PMS integration 9-17 HOBIC AckNak Threshold 2 selection requirements The threshold2 field contains the upper limit of the FIFO buffer. When Threshold 2 is crossed, records are sent to a service log instead of the PMS and another SNMP trap is sent. Records sent to the service log must be manually posted to the billing system after the PMS link is re-established. If Threshold 2 is set too low, records will sent to the service log and not sent to the PMS once the PMS-to-YWS link is re-established.
9-18 YesWare PMS integration Procedure 9-4 Configuring SNMP trap recipient for PMS link disruptions Use this procedure to configure the SNMP trap recipient for PMS link Threshold 1 and Threshold 2 traps. This procedure should be done only after the remainder of the PMS interface has been configured as described in Procedure 9-2 on page 9-14. Action Step Action 1 From the YesWare Main Menu, select the Billing Manager module.
YesWare PMS integration 9-19 Procedure 9-4 (continued) Configuring SNMP trap recipient for PMS link disruptions Step Action 5 Enter the following in the threshold1 field of the acknak configuration file (The command is entered all on one line. It is shown on several lines here because of space limitations.): [Numeric Threshold 1 setting] snmptrap -v 1 [trap recipient host name or IP address] public 1 [YWS hostname or IP address] 2 0 ’’ system.sysDescr.
9-20 YesWare PMS integration Software Release 2.
10-1 Customizing the VBN web site 10- This chapter contains the requirements and procedures to customize the VBN web site used by YesWare visitors. Chapter topic list This chapter includes the following topics. Topic See VBN page customization page 10-2 YesWare VBN pages page 10-3 Using tags page 10-4 Branding and home/splash page configuration page 10-7 Chapter task list This chapter includes the following tasks.
10-2 Customizing the VBN web site VBN page customization Customizing YesWare VBN pages requires knowledge of web page construction and writing HTML code. The default YesWare VBN pages must be used as the basis for creating the custom VBN pages, and must be edited manually to include the custom graphics and style sheets, and any other desired functions such as Javascripts, Java applets, and cgi-perl.
Customizing the VBN web site 10-3 YesWare VBN pages Each VBN page has a specific function in YesWare and certain usage requirements. Table 10-1 lists the VBN pages available for use in the YesWare system, and the purpose for which each page is used. Note: Other VBN pages exist on the YWS (such as passwd.vbn) that are not supported and cannot be used. Only the VBN pages listed in Table 10-1 are supported in this release of YesWare.
10-4 Customizing the VBN web site Using tags Each tag has a specific function on the VBN pages and certain usage requirements. The tags serve the following functions: • Create the forms used to authenticate or refuse service on VBN authentication pages. • Display information about the port connection and the service-provider.
Customizing the VBN web site 10-5 tags used for port and service information The Table 10-3 lists the tags used to provide port and serviceprovider information. These tags are not used when the Port Use Context is network.
10-6 Customizing the VBN web site tags used for VBN graphics The Table 10-3 lists the tags used to display VBN graphics stored on the YWS in the *.gif format. To use these tags, the file names of the custom graphics must be identical to the file names listed in Table 10-5. Note: Other graphics can be used. However, additional graphics must be added using standard HTML links and web-page design techniques.
Customizing the VBN web site 10-7 Branding and home/splash page configuration Service-provider branding is provided using the Branding Configuration and Custom Look and Feel dialogs and the tags listed in Table 10-4 on page 10-5. Branding Configuration dialog The Branding Configuration dialog is launched using Add/Search Branding Setup function located in the System Setup section of the Port Manager module. Figure 10-1 shows the default Branding Configuration dialog.
10-8 Customizing the VBN web site Custom Look and Feel configuration The Custom Look and Feel dialog is launched using Custom Look and Feel function located in the System Tools section of the Port Manager module. This dialog is used to designate how the home/splash page designated in the Branding Configuration appears to the visitor after authenticating on the VBN. Figure 10-2 shows the Custom Look and Feel dialog.
Customizing the VBN web site 10-9 Table 10-7 Custom Look and Feel Settings and Options Custom Look and Feel Setting Configuration Options Splash Window Configuration In this field, choose how you'd like the splash window to appear: • Splash in new window with toolbar • Splash in new window without toolbar • Splash in existing window • Splash disabled See “Splash Window Configuration options” below.
10-10 Customizing the VBN web site Figure 10-3 Elastic Networks home/splash page default Software Release 2.
Customizing the VBN web site 10-11 Procedure 10-1 Creating the custom VBN web site Use this procedure to create the custom VBN web site. Requirements This procedure requires the following: • basic knowledge of ftp commands • ftp client computer with network access to the YWS • knowledge of web page construction and design ftp commands The following ftp commands are useful in this procedure: • binary: Changes the ftp data transfer mode to the required binary mode.
10-12 Customizing the VBN web site Procedure 10-1 (continued) Creating the custom VBN web site Step Action 4 At the Password: prompt, enter the password of the admin user. This is the same password as the one used in the Elastic Operating Network (EON) to configure the YWS on the host network (see Chapter 3). The default admin password is etherloop. Figure 10-4 shows an example ftp-user login to a YWS at 172.17.3.245.
Customizing the VBN web site 10-13 Procedure 10-2 Configuring the Virtual Concierge YesWare’s Virtual Concierge feature enables service providers to create a host-specific site linked to the YWS and filled with free content and advertising. The VBN visitor can browse the Virtual Concierge for free to obtain information about local restaurants and host amenities, but will have to accept the payment terms and conditions to receive Internet access.
10-14 Customizing the VBN web site Procedure 10-2 (continued) Configuring the Virtual Concierge Step Action 2 Click on the Virtual Concierge function link to launch the Virtual Concierge Setup dialog. See Figure 10-5. Figure 10-5 Virtual Concierge Setup dialog 3 Enter the IP address of the Virtual Concierge web server that will provide the free content to YesWare visitors. 4 Add an HTML link to the Virtual Concierge server IP address on the VBN authentication page(s).
11-1 YesWare conference room and meeting services 11This chapter describes the features, provisioning requirements and procedures available in YesWare to schedule and bill YesWare services in conference rooms using Conference Room Billing, and in meeting rooms using the port scheduling function of Port Manager. Chapter topic list This chapter includes the following topics.
11-2 YesWare conference room and meeting services Conference Room Billing Conference Room Billing is set up using the Conference Scheduler module. Conference Room Billing is IP-based conference room service for customers who do not want/need YesWare’s network address translation (NAT) capability. The Conference Scheduler module allows visitors with static, routable IP addresses on the ETH 1 side of the YWS to access the Internet without undergoing NAT.
YesWare conference room and meeting services 11-3 Conference Room Billing using Conference Scheduler The Conference Room Billing method uses Internet-routable IP addresses generated from an address pool using the Conference Scheduler module. These IP addresses must be purchased from the Internet service-provider (ISP) and re-sold for a flat fee by the service-provider. The Conference Scheduler generates a printable receipt to give to the customer and keep for provider records.
11-4 YesWare conference room and meeting services Procedure 11-1 Configuring Conference Room Billing The YesWare/LAN administrator must use this procedure to configure the network used by the Conference Scheduler to provide IP-based conference services.
YesWare conference room and meeting services 11-5 Procedure 11-1 (continued) Configuring Conference Room Billing Step Action 4 Complete the Conference Room Network Configuration dialog according to Table 11-1. Table 11-1 Conference Room Network Configuration dialog settings Field Entry Description Network Gateway Address Enter the IP address of the network gateway used by the host network to access the WAN. This address is typically the first addressable IP address in the range.
11-6 YesWare conference room and meeting services Procedure 11-2 Scheduling conference room IP addresses Use this procedure and the Conference Scheduler Book a Conference Room function to schedule conference meeting rooms.
YesWare conference room and meeting services 11-7 Procedure 11-2 (continued) Scheduling conference room IP addresses Step Action After clicking on the Conference Scheduler link, the Conference Room Scheduler main page should appear as shown in Figure 11-4. Figure 11-4 Conference Room Scheduler main page —continued— Software Release 2.
11-8 YesWare conference room and meeting services Procedure 11-2 (continued) \Scheduling conference room IP addresses Step Action 3 In the Conference Room Scheduler main page, click on the Book a Conference Room link. The Meeting Room Scheduler dialog should appear. 4 Complete the information required for the customer and conference room in the Meeting Room Scheduler dialog. Figure 11-5 shows an example of a completed Meeting Room Scheduler dialog.
YesWare conference room and meeting services 11-9 Procedure 11-2 (continued) Scheduling conference room IP addresses Step Action 6 After clicking the "Add It" button, the system will generate a Reservation Receipt as shown in Figure 11-6. Accept payment and give the customer the Reservation Receipt according to local office administration procedures. Figure 11-6 Conference Scheduler Reservation Receipt STOP You have completed this task. Software Release 2.
11-10 YesWare conference room and meeting services Procedure 11-3 Configuring visitor computers for Conference Room Billing Use this procedure to configure the visitor computers to use Conference Scheduler services and Conference Room Billing. Note: This procedure presents the visitor configuration using a Windows 95 PC. The configuration requirements of other network operating systems will vary, but the basic procedure should be the same.
YesWare conference room and meeting services 11-11 Procedure 11-3 (continued) Configuring visitor computers for Conference Room Billing Step Action 2 Select the TCP/IP protocol associated with the Ethernet NIC and click the "Properties" button. The Network TCP/IP Properties dialog appears as shown in Figure 11-8. Figure 11-8 Network TCP/IP Properties dialog 3 In the IP Address tab, specify an IP address and Subnet Mask for the visitor computer.
11-12 YesWare conference room and meeting services Port-based meeting scheduling and billing Port-based meeting service is set up by turning on and off ports using the Schedule Conference Room Ports function in the Ethernet Switch and Port Provisioning section of Port Manager. This feature uses Authorization Code Billing as its billing method. This section describes the requirements to set up Port-based conference room billing.
YesWare conference room and meeting services 11-13 Procedure 11-4 Scheduling port-based meeting rooms Use this procedure to schedule conference meeting rooms using the Schedule Conference Room Ports in the Ethernet Switch and Port Provisioning section of Port Manager.
11-14 YesWare conference room and meeting services Procedure 11-4 (continued) Scheduling port-based meeting rooms Step Action 3 In Port Manager, scroll down to the Ethernet Switch and Port Provisioning section and click on the Schedule Conference Room Ports link. The Schedule Conference Room Ports dialog should appear as shown in Figure 11-10. Figure 11-10 Schedule Conference Room Ports dialog 4 Click on the "Choose Port Location" pull-down menu and select a port to schedule.
YesWare conference room and meeting services 11-15 Procedure 11-4 (continued) Scheduling port-based meeting rooms Step Action 7 In the Create New schedule for [conference room/port] dialog, complete the "Start Time" and "End Time" information required for the conference room port. Also, select the "Action at start time" to perform on the port (Enable/Disable). Figure 11-12 shows an example of a completed Create New schedule for [conference room/port] dialog for port #1 on Conference Room 1-1.
11-16 YesWare conference room and meeting services Procedure 11-4 (continued) Scheduling port-based meeting rooms Step Action 8 Click the "Continue" button to create the port schedule. The system will display an Scheduler Response dialog. Figure 11-13 shows an example of the Scheduler Response dialog for the schedule illustrated in Figure 11-12 on page 11-15. Figure 11-13 Scheduler Response dialog —continued— Software Release 2.
YesWare conference room and meeting services 11-17 Procedure 11-4 (continued) Scheduling port-based meeting rooms Step Action 9 Verify the information is correct in the Scheduler Response dialog and click the "Continue" button to create the schedule for the port. 10 Select the "View Schedule" button and click "Continue" to verify the schedule created for the conference room and port. Figure 11-14 shows the example schedule created for port #1 on Conference Room 1-1.
11-18 YesWare conference room and meeting services Software Release 2.
12-1 Providing visitor printing services 12- This chapter describes the requirements, functions and procedures for using the Print Services module to provide visitor printing services. Chapter topic list This chapter includes the following topics.
12-2 Providing visitor printing services YesWare’s Print Services module The YesWare Print Services module gives guest visitors the capability of printing from their computer to a networked printer on the YesWare VBN or host network. Figure 12-1 shows the Print Services module link on the YesWare main page. The following sections describe the requirements and functions for using the YesWare Print Services module.
Providing visitor printing services 12-3 Print Services module functions Figure 12-2 shows the functions on the Print Services main page. Table 12-1 describes the purpose of each of these functions. Figure 12-2 Print Services main page Table 12-1 Print Services module functions Function Description Configure Printer(s) This function sets the printer name, Network IP address, location, and space for descriptive comments about the printer.
12-4 Providing visitor printing services Print Services printer requirements and limitations The Print Services module can be configured to support up to five networked printers. The following sections describe the requirements and limitations for the printers used with the Print Services module.
Providing visitor printing services 12-5 Print Services visitor billing Only YesWare visitors connected to "guest" ports can browse to the printing services page and use (and be billed for) visitor printing services. YesWare visitors who use visitor printing services are billed for both YesWare Internet access and printing services.
12-6 Providing visitor printing services Procedure 12-1 Provisioning visitor printing services Use this procedure to provision visitor printing services using the Print Services module.
Providing visitor printing services 12-7 Procedure 12-1 (continued) Provisioning visitor printing services Step Action 3 Login to the YesWare Server and select the Print Services module from the main menu. 4 Select the Configure Printer(s) function to launch the Add/Delete Printer(s) dialog. Figure 12-3 shows this dialog with no printers configured. Note: If this dialog is completely blank (has no text-entry fields), it means that no guest rooms have been provisioned.
12-8 Providing visitor printing services Procedure 12-1 (continued) Provisioning visitor printing services Step Action 6 Click the "Add" button to add the printer configuration to the database. After a few moments, the system should display the printer configuration in the "database table" above the "Add" fields as shown in Figure 12-5. Note: To save re-entering the same information for additional printers, the text-entry fields in the table used to add new printers do not clear when a printer is added.
Providing visitor printing services 12-9 Procedure 12-1 (continued) Provisioning visitor printing services Step Action 7 Repeat steps 5 and 6 for up to five printers. Each additional printer will be added in the database table beneath the first printer configured. Figure 12-6 shows a second printer added in the database table and with the "add" fields cleared.
12-10 Providing visitor printing services Procedure 12-1 (continued) Provisioning visitor printing services Step Action Setting rates for printing services 9 From the Print Services module main page, select the Configure Printer Rates function to launch the Add/Delete Printer Rates dialog. Figure 12-7 shows this dialog with only the default "0.00" rate configured.
Providing visitor printing services 12-11 Procedure 12-1 (continued) Provisioning visitor printing services Step Action Assigning printers and rates to guest rooms 13 From the Print Services module main page, select the Map Printer(s) to Rooms function to launch the Map Printer to Room Database dialog. Figure 12-7 shows the default dialog with several example guest rooms configured. Figure 12-9 Example / Default "Map Printer to Room Database" dialog —continued— Software Release 2.
12-12 Providing visitor printing services Procedure 12-1 (continued) Provisioning visitor printing services Step Action 14 Use the pulldown lists and checkboxes in this dialog to assign and enable printers and rates according to facility requirements and as described in Table 12-3.
Providing visitor printing services 12-13 Procedure 12-1 (continued) Provisioning visitor printing services Figure 12-10 Example / Completed "Map Printer to Room Database" dialog —continued— Software Release 2.
12-14 Providing visitor printing services Procedure 12-1 (continued) Provisioning visitor printing services Step Action Starting visitor printing services 17 From the Print Services module main page, select the Configure Print Service function to launch the Configure Print Services dialog. Figure 12-11 shows this dialog in the default "Off" condition. Figure 12-11 Default "Configure Print Services" dialog 18 Click the "On" radio button, and click the "OK" button to start printing services.
Providing visitor printing services 12-15 Procedure 12-2 Using visitor printing services YesWare visitors can use this procedure to print a document using the YesWare Print Services module. Note: The service-provider can use the instructions in this procedure to create an instruction-sheet for visitors to be placed in guest rooms.
12-16 Providing visitor printing services Procedure 12-2 (continued) Using visitor printing services Step Action 2 Print the document to "file" using the required compatible printer driver (see Figure 12-12). Figure 12-12 Print-to-file PostScript printer driver 3 "Print to file" selected Launch the web-browser and, when prompted, enter the required Authorization Code or click "OK" to accept room charges. —continued— Software Release 2.
Providing visitor printing services 12-17 Procedure 12-2 (continued) Using visitor printing services Step Action 4 From the Web, browse to the following IP address: /cgi-bin/print.cgi Figure 12-13 shows an example of a visitor print services web-page IP address. The web-page should appear as shown in Figure 12-14.
12-18 Providing visitor printing services Procedure 12-2 (continued) Using visitor printing services Step Action 6 Click the "Browse" button and browse to the location of the PostScript or PCL version of the document file (see Figure 12-15). Figure 12-15 PostScript file ready to upload "Browse" button PostScript file (*.ps) —continued— Software Release 2.
Providing visitor printing services 12-19 Procedure 12-2 (continued) Using visitor printing services Step Action 7 When the PostScript or PCL file is listed in the entry field, click the "Upload File to List" button. After a few moments, the file to be printed should appear in the "List of files to print" table as shown in Figure 12-16. Caution - Delete-file checkbox usage Clicking once on the delete-file checkbox (see Figure 12-16) immediately removes a file from the list, whthout a prompt.
12-20 Providing visitor printing services Software Release 2.
SECTION IV YESWARE SYSTEM MANAGEMENT Software Release 2.30 Software Release 2.
13-1 YesWare security and administration13This chapter describes YesWare system security, maintenance and administration capabilities and procedures. Chapter topic list This chapter includes the following topics. Topic See YesWare System Security page 13-2 Routine Maintenance and Administration page 13-12 Backup, Restore, Upgrade, Restart and Shut Down Procedures page 13-23 Software Release 2.
13-2 YesWare security and administration YesWare System Security This section includes the following tasks. Procedure Task See 13-1 Adding or removing modem privacy filters page 13-3 13-2 Restricting web access to the YWS page 13-6 13-3 Changing the system manager password page 13-8 13-4 Resetting a password page 13-10 Software Release 2.
YesWare security and administration 13-3 Procedure 13-1 Adding or removing modem privacy filters Access this function by selecting Port Manager / EtherLoop Modem Provisioning / Add privacy filters. Feature description By default, EtherLoop modems in a YesWare VBN function as an unprotected LAN.
13-4 YesWare security and administration Procedure 13-1 (continued) Adding or removing modem privacy filters Using the Add privacy filters function Separate MAC filter tables exist for CO and CPE modems. If no MAC addresses appear in the MAC Filter table for a particular modem, it will pass all Ethernet traffic. If any MAC addresses appear in the MAC Filter table for a particular modem, the modem will only accept Ethernet packets from those addresses.
YesWare security and administration 13-5 Procedure 13-1 (continued) Adding or removing modem privacy filters Step Action 4 Click the "Add" button to add the MAC address to the Filter Table of the selected group of modems. After processing, the system displays the Figure Note: Clicking the "Remove" button will remove the MAC address from the Filter Table. Figure 13-3 MAC Filter Address added to filter table 5 In the "Number of Minutes" field, enter the duration (in minutes) between refreshes.
13-6 YesWare security and administration Procedure 13-2 Restricting web access to the YWS Use this procedure to restrict access to the YWS web interface by defining a list of valid subnets. If this function is used, only hosts with IP addresses within one of the defined subnets are allowed access to the YWS. By default, the system does not restrict any hosts. If you are unfamiliar with subnet addressing, contact your LAN administrator for assistance with this procedure.
YesWare security and administration 13-7 Procedure 13-2 (continued) Restricting Remote Access Step Action 3 Click View Subnet List and then click Submit Query. The Remote Management Subnets screen appears as shown below. Figure 13-5 Remote Management Subnets screen This screen displays the current list of valid subnets. In the example above, the entry 0.0.0.0/0 is all-inclusive, which means that all addresses are allowed access to the YWS.
13-8 YesWare security and administration Procedure 13-3 Changing the system manager password Once you have logged onto the YesWare interface for the first time, you should change the default manager password so your system is secure. Use the following procedure to change the system manager password. Action Step Action 1 From the YesWare Main Menu, choose NSS Maintenance.
YesWare security and administration 13-9 Procedure 13-3 (continued) Changing the system manager password 3 Enter the new password. The password must be 5-8 characters. 4 Enter the new password again to verify it. 5 Enter the old password, the password you are changing (if this is the first time you have logged on, the password is still manager). 6 Choose one of the following: • Click Change Password to change to the new password.
13-10 YesWare security and administration Procedure 13-4 Resetting a password The Password Reset option is used to change the passwords of Administrators and Operators. This is useful in cases where an Administrator or Manager needs to change a password for security purposes. To change the your own password (the password under which you logged into the system), use the Password Change option (see “Changing the system manager password” on page 13-8).
YesWare security and administration 13-11 Procedure 13-4 (continued) Resetting a Password Action Step Action 1 From the YesWare Main Menu, choose NSS Maintenance. The NSS Maintenance menu appears. 2 Select the Password Reset option. The Reset User Account Password dialog appears. Figure 13-7 Reset User Account Password dialog 3 Enter the identifier for the account to be reset. 4 Enter the new password for the account.The password must be 5-8 characters.
13-12 YesWare security and administration Routine Maintenance and Administration This section includes the following tasks. Procedure Task See 13-5 Adding a new user page 13-13 13-6 Deleting a User page 13-15 13-7 Viewing System Logs page 13-17 13-8 Viewing VBN user activity page 13-19 13-9 Configuring NTP (network time protocol) page 13-22 Software Release 2.
YesWare security and administration 13-13 Procedure 13-5 Adding a new user Use the Add New User Account function to add Operator and Administrator user accounts. Note: Only the YesWare Manager can add YesWare Administrator user accounts. See Table 13-2, “YesWare Maintenance Privileges,” for more information. There three types of YesWare users: • • • Operator Administrator Manager The table below defines YesWare Maintenance privileges for each user type.
13-14 YesWare security and administration Procedure 13-5 (continued) Adding a new user Action Step Action 1 From the YesWare Main Menu, choose NSS Maintenance. The NSS Maintenance menu appears. 2 Select the Add New User option. The Add New User dialog appears.
YesWare security and administration 13-15 Procedure 13-6 Deleting a User The Delete User Account function is used to delete Operator and Administrator user accounts. Note: Only the Manager can delete Administrator accounts. See Table 13-3, “YesWare Maintenance Privileges,” for more information. The current release of YesWare defines the following user types: • • • Operator Administrator Manager The table below defines Maintenance privileges for each user type.
13-16 YesWare security and administration Procedure 13-6 (continued) Deleting a User Action Step Action 1 From the YesWare Main Menu, choose NSS Maintenance. The NSS Maintenance menu appears. 2 Click Delete User. The Delete User dialog appears. Figure 13-9 Delete User Account dialog 3 Enter the identifier for the account to be deleted. The system requires that you enter your own password to verify that you have proper authorization to delete the user’s password.
YesWare security and administration 13-17 Procedure 13-7 Viewing System Logs The following steps describe the procedure for viewing VBN (Visitor Based Network, which includes Billing Manager and Port Manager) event logs. You can display the entire log, or choose from a list of filters to select the information displayed. You can choose to display only error messages, debugging messages, warning messages, or informational messages instead of the entire log.
13-18 YesWare security and administration Procedure 13-7 (continued) Viewing the System Logs 3 To filter the information displayed, select one of the following and then click Filter. • error—error messages • debug—debug messages • warn—warning message • info—informational messages • all—all messages in the log The log is displayed again with only the messages you selected. STOP You have completed this task. Software Release 2.
YesWare security and administration 13-19 Procedure 13-8 Viewing VBN user activity This procedure describes the functions available in YesWare to view VBN user activity. These functions are located in the System Tools section of Port Manager, and include the following: • Show Active Users • • Show User History Trace Address The folllowing sections describe the purpose and use of each of these functions. Show Active Users Use this function to view the list of active users on the InterProxy-VBN system.
13-20 YesWare security and administration Procedure 13-8 (continued) Viewing VBN user activity Show User History Use this function to view a history of all logins on the visitor network in the last two weeks. Figure 13-12 shows a "truncated" user history dialog. Figure 13-12 User History dialog —continued— Software Release 2.
YesWare security and administration 13-21 Procedure 13-8 (continued) Viewing VBN user activity Trace Address Use this function to determine the path of Ethernet-VBN switches a user takes to reach the YWS. To trace a user IP address, enter the IP address in the "Trace IP Address" dialog field and click the "Submit Query" button. Figure 13-13 shows the "Trace IP Address" dialog. Figure 13-13 Trace IP Address dialog STOP You have completed this task. Software Release 2.
13-22 YesWare security and administration Procedure 13-9 Configuring NTP (network time protocol) Use this procedure to edit the list of clock synchronization servers that can be used to keep your system clock accurate. This procedure is optional; Elastic Networks provides a set of default values for NTP configuration which should be adequate for most installations. Action Step Action 1 From the YesWare Main menu, choose NSS Maintenance. 2 Click Set Xntp information. The ntp dialog appears.
YesWare security and administration 13-23 Backup, Restore, Upgrade, Restart and Shut Down Procedures This section contains the following tasks. Procedure Task See 13-10 Installing and Upgrading YesWare modules page 13-24 13-11 Backing Up and Restoring the System Database page 13-26 13-12 Backing up the InterProxy configuration page 13-27 13-13 Restarting the YesWare Server page 13-29 13-14 Shutting Down the YesWare Server page 13-30 Software Release 2.
13-24 YesWare security and administration Procedure 13-10 Installing and Upgrading YesWare modules This procedure explains how to install new YesWare software or upgrade the software currently installed. Use this procedure whenever you need to update your system software. Requirement To perform this procedure, you need the following: • YesWare upgrade software diskette or file Action Step Action 1 Log in to the YesWare Server and choose Install or Upgrade from the main menu.
YesWare security and administration 13-25 Procedure 13-10 (continued) Installing and Upgrading YesWare modules Step Action 2 Proceed according to the following table: Upgrading from Then Diskette Insert the YesWare application diskette in the YesWare Server disk drive and click "Update" button. File located on local or Click the "Browse" button. Browse to the file network disk drive location and click "Update from File" button.
13-26 YesWare security and administration Procedure 13-11 Backing Up and Restoring the System Database The following steps describe the procedure for backing up and restoring the system database. Action Step Action 1 From the YesWare Main Menu, choose NSS Maintenance. The NSS Maintenance menu appears. 2 Click Backup/Restore System Database. The Log Browsing dialog appears as shown.
YesWare security and administration 13-27 Procedure 13-12 Backing up the InterProxy configuration When the initial InterProxy configuration is complete (and whenever the cinfiguration changes thereafter), you should make a backup of the configuration. Use this procedure to backup the InterProxy configuration to diskette. In addition to using this function, the system administrator should use the webbrowser’s print capability to print-out the InterProxy settings for recordkeeping purposes.
13-28 YesWare security and administration Procedure 13-12 (continued) Backing up the InterProxy configuration Step Action 4 Insert a diskette in the disk drive. 5 Click Begin Backup. 6 At any time during the backup process, you can click Display Status to show the current status of the backup. When the status indicates that the backup is complete, you can remove the diskette. STOP You have completed this task. Software Release 2.
YesWare security and administration 13-29 Procedure 13-13 Restarting the YesWare Server This procedure explains how to restart the YesWare Server should you be directed to do so by your Elastic Networks technical support representative. CAUTION Client communications are stopped while the YesWare Server is rebooting. This procedure causes the YesWare Server to reboot. Any client communications will be dropped while the server is rebooting. The reboot process takes approximately one minute.
13-30 YesWare security and administration Procedure 13-14 Shutting Down the YesWare Server This procedure explains how to restart the YesWare Server should you be directed to do so by your Elastic Networks technical support representative. CAUTION Client communications are stopped while the YesWare Server is rebooting. This procedure causes the YesWare Server to shut down. Any client communications will be dropped.When the system is rebooted, the reboot process takes approximately one minute.
14-1 Using EtherCraft 14- The EtherCraft utility provides monitoring and control features for modems used in EtherLoop systems. This chapter describes the features and capabilities of the EtherCraft module, including selecting modems for remote examination of modem speed, throughput, and error tracking information. In addition, this chapter shows EtherCraft’s capabilities to keep up with firmware versions, modem status, and hardware addresses.
14-2 Using EtherCraft EtherCraft feature description EtherCraft is a diagnostics and performance monitoring tool for monitoring EtherLoop modem status and performance. EtherCraft can examine all modems or selected modems that have been provisioned using Port Manager. EtherCraft can only be used after EtherLoop modem database has been provisioned. EtherCraft terminology - Server=CO/SE, Client=CPE/CE EtherCraft terms EtherLoop CO/SE modems as "server" modems and CPE/CE modems as "client" modems.
Using EtherCraft 14-3 EtherCraft speeds tables Table 14-1 on page 14-4 lists the modem speed codes and the estimated throughput for the corresponding QAM16 and QPSK speed values. Software Release 2.
14-4 Using EtherCraft Table 14-1 Estimated throughput at different modem speeds Modem Speed ksps Code Modulation kbps 0 62.50 QPSK 125 1 89.29 QPSK 178 2 125.00 QPSK 250 3 62.50 250 4 178.57 QPSK 357 5 89.29 357 6 250.00 QPSK 500 7 125.00 16 QAM 500 8 357.14 QPSK 714 9 178.57 16 QAM 714 10 500.00 QPSK 1000 11 250.00 16 QAM 1000 12 714.29 QPSK 1428 13 357.14 16 QAM 1428 14 833.33 QPSK 1666 15 1000 2000 16 500.00 16 QAM 2000 17 714.
Using EtherCraft 14-5 Table 14-2 Check Speed training count interpretation Code Description 15 Modem has been trained, speed has been used and the LQF is > or = 98% 11 thru14 Modem has been trained, speed has a high LQF but has burned off at least once.
14-6 Using EtherCraft Check Speeds Use this function to check the transmit speeds of selected client or server modems. You can display the following values for training results based on training at different speeds. • • • Type of modem—client or server modem.
Using EtherCraft 14-7 Modem Details The Modem Details function of EtherCraft displays comprehensive modem data. Figure 14-2 shows an example of the EtherCraft Modem Details page. The following sections present a detailed look at the information available on the Modem Details page. Figure 14-2 EtherCraft / Modem Details Software Release 2.
14-8 Using EtherCraft Modem identification and version table The modem identification and version table (first table on the Modem Details page) shows the following identification and version information for each modem selected: • • • • • MAC address of modem Type of modem—client or server Firmware version installed on modem Revision number of modem board Revision number of modem analog board Figure 14-3 shows an example of the identification and version section.
Using EtherCraft 14-9 Speeds tables, modem speeds and training counts Speeds tables follow the Ethernet Port Metrics table, and present values for these transmit and receive parameters: • Server _Tcount—Transmit speed of CO/SE modems • Client_Tcount—Transmit speed of CPE/CE modems • Retrain_RX—Receive retrain count; value is ‘-’ if run on CPE/CE modem • Retrain_TX—Transmit retrain count; value is ‘-’ if run on CPE/CE modem • • • • Tx_Atten - Attenuation in dB from the maximum transmit output power on the
14-10 Using EtherCraft HDLC Port Metrics An HDLC Metrics table is associated with each speeds table displayed for the modem port. HDLC Metrics include a measurement on the side of the phone link between modems.
Using EtherCraft 14-11 Client Addresses Use this function to display the MAC addresses of clients that correspond to selected server modems. The addresses are displayed in columns by type of modem. If no client modem is assigned, the system displays "No_Client_Modem." Access this function from the EtherCraft page by clicking the Client Addresses button. Figure 14-7 shows the Client Addresses page. Figure 14-7 EtherCraft Client Addresses page Software Release 2.
14-12 Using EtherCraft Status Use this function to test whether modems are responding or are unavailable. The modems are listed by MAC address. The status is either "Ok" in the Responds field or an "X" in the Unavailable field. Access this function from the EtherCraft page by clicking the Status button. Figure 14-8 shows an example of the Status page. Figure 14-8 EtherCraft Status page Software Release 2.
Using EtherCraft 14-13 Version Use this function to retrieve firmware code page (memory location) and FPGA page information, current firmware version, and the modem printed circuit board (PCB) revision. The modems are listed by MAC address. Access this function from the EtherCraft page by clicking the Status button. Figure 14-8 shows an example of the Status page.
14-14 Using EtherCraft Clear Logs Use this function to clear selected EtherCraft logs. Clearing EtherCraft logs offers a way to remove current entries from the following logs: • • • • • IPBOA (same as "Modem Details") Client Address Status Version Reset Modems CAUTION - Removing EtherCraft logs is permanent When clearing EtherCraft logs no backup is made for the logs. By clearing the logs you remove entries permanently from the EtherCraft log files.
Using EtherCraft 14-15 Get Logs Use this function to download selected EtherCraft logs. Log files are stored in a CSV (comma separated value) file format. Upon retrieval, the log files are automatically converted into a Microsoft Excel file that can be saved on the local workstation or network. Access this function from the EtherCraft page by clicking the Get Logs button.
14-16 Using EtherCraft Reset Modems Use this function to reset selected modems. Resetting the modems clears current activity from the modem and restarts modem operation. CAUTION - Reset Modems causes loss of service This procedure will cause temporary loss of service. Do only at low-traffic periods Access this function from the EtherCraft page by clicking the Reset Modems button.
15-1 Using the Download Utilities module 15This chapter describes how to use the Download Utilities module. Chapter Contents This chapter includes the following information. Topic See Download Utilities purpose and function page 15-2 Using Download Utilities page 15-2 Downloader status and logs page 15-2 Chapter task list This chapter includes the following tasks.
15-2 Using the Download Utilities module Download Utilities purpose and function The Download Utilities module is used to download firmware and FPGA (field programmable gate array) code for any number of Elastic system modems. These modems are selected by querying the modem database. The Download Utilities module examines the file header when told to download a certain file to the modem to verify the authenticity, type, and reliability of the file.
Using the Download Utilities module 15-3 Procedure 15-1 Upgrading EtherLoop modem firmware Use this procedure to upgrade the EtherLoop modem firmware using the Download Utilities module. Requirements To do this procedure, you need the following: • A file containing the new modem firmware and/or FPGA code on a 3.5inch diskette, local workstation or reachable network location. Action Step Action 1 From the YesWare Main Menu, choose Downloader.
15-4 Using the Download Utilities module Procedure 15-1 (continued) Upgrading EtherLoop modem firmware Step Action 2 Click the "Upload New Files" button. The Download Utilities / Modem Firmware Uploader appears as shown in Figure 15-2. Figure 15-2 Download Utilities / Modem Firmware Uploader 3 Browse to the location of the file containing the new load for the modem firmware/FPGA code. 4 Click the "Upload Files" button. The system installs the new load into the YWS "downloader" directory.
Using the Download Utilities module 15-5 Procedure 15-1 (continued) Upgrading EtherLoop modem firmware Step Action When the download is complete, the system displays a Download Status page with the following information: • status of download (complete) • start and end times of download • file name of firmware code used in download • number of modems that receiving download • percent of file transfers completed (%) • percent of modem programming completed (%) • number of failed downloads • nu
15-6 Using the Download Utilities module Procedure 15-2 Upgrading from Generation 1 to Generation 2 modem firmware Use this procedure to upgrade ELMo 8 and Elite EtherLoop modem firmware from Generation 1 to Generation 2. Requirements To do this procedure, you need the following: • A file containing the Generation 2 modem firmware on a 3.5-inch diskette, local workstation or reachable network location. Generation 2 firmware fil names all begin with "02_".
Using the Download Utilities module 15-7 Procedure 15-2 (continued) Upgrading from Generation 1 to Generation 2 modem firmware Action Step Action 1 From the Download Utilities main menu, click the "Upload New Files" button to launch the Modem Firmware Uploader dialog as shown in Figure 15-2. Figure 15-3 Download Utilities / Modem Firmware Uploader 2 Browse to the location of the file containing the new load for the modem firmware files. 3 Click the "Upload Files" button.
15-8 Using the Download Utilities module Procedure 15-2 (continued) Upgrading from Generation 1 to Generation 2 modem firmware Step Action 5 In the Download Utilities Main Menu, select "Gen-1 to Gen-2" upgrade to launch the Gen-1 to Gen-2 Upgrade Menu.See Figure 15-4. Figure 15-4 Gen-1 to Gen-2 Upgrade Menu 6 Use the "Target Gen-2 Code File" pull-down menu and select the newlyuploaded Gen-2 firmware load.
Using the Download Utilities module 15-9 Procedure 15-2 (continued) Upgrading from Generation 1 to Generation 2 modem firmware Step Action When the Gen-2 upgrade is complete, the system displays a Downloader Status page as shown in Figure 15-5. Figure 15-5 Firmware Gen-2 upgrade complete STOP You have completed this task. Software Release 2.
15-10 Using the Download Utilities module Software Release 2.
APPENDIX A YESWARE MANAGEMENT USING SNMP Software Release 2.30 Software Release 2.
A-1 Remote YesWare Management using SNMP AThis chapter describes the use of the YesWare SNMP Agent and its supported MIBs. The purpose of YesWare SNMP is to provide Simple Network Management Protocol (SNMP) support to remotely monitor and configure YesWare EtherLoop and Ethernet components. The YWS Server does not contain an SNMP "Network Manager.
A-2 Remote YesWare Management using SNMP YesWare SNMP components The YWS Server SNMP component supports a number of standard and private SNMP management information bases (MIBs). Table A-1 lists the SNMP components of the YesWare. Table A-1 YesWare SNMP components Component Description Operating System YesWare EON Code Dependencies SNMP component is an integrated part of YesWare software. It requires that the YesWare base, ModeX Daemon and other components are present.
Remote YesWare Management using SNMP A-3 Using YesWare SNMP In order for a network manager to manage the YesWare SNMP Agent, the user must load the Elastic Networks private MIBs into their SNMP Network Manager (e.g., HP OpenView) using the procedure accompanying their Network Manager software. This procedure to load and compile a MIB is specific to the Network Manager software.
A-4 Remote YesWare Management using SNMP YesWare EtherLoop MIB The YesWare SNMP Agent supports an Elastic Networks EtherLoop Modem private MIB for managing EtherLoop Modems. The EtherLoop Modem MIB is implemented under the Enterprises tree under the Elastic Networks private Object Identifier. The MIB is a SNMPv2 compliant MIB that conforms to RFC 1902. Table A-3 lists the community strings for accessing the EtherLoop Modem private MIB.
Remote YesWare Management using SNMP A-5 Example SNMP Network Manager with EtherLoop MIB This section contains screen shots of SNMPc, an SNMP manager, from Castle Rock Computing, Inc. being used to manage the EtherLoop Agent. EtherLoop Modem System Table The EtherLoop Modem System Table defines variables that are associated with the EtherLoop system rather than the individual modems. The table contains two rows of variables; one for CO modems and one for CPE modems.
A-6 Remote YesWare Management using SNMP Table A-4 MIB variables for the EtherLoop Modem System Table Object Name Description Access Syntax modemSysCategory The index for the table. Specifies the category read-only for the data is for CO modems or CPE modems. INTEGER coModems cpeModems modemSysNumModems The number of modems present for this category. read-only Integer32 modemSysNumDownMode ms The number of modems, for this category, that have linkStatus of down.
Remote YesWare Management using SNMP A-7 EtherLoop CO and CPE Id Tables The EtherLoop Id table provides information primarily for identifying the modems. The table contains a row for each modem identified in the system. Separate Id tables exist for CO and CPE modems. The figure below shows an example screen shot of the EtherLoop Modem CO Id and CPE Id tables. Table A-5 on page A-8 details the MIB variables supported by these tables. Figure A-2 EtherLoop Modem CO Id and CPE Id tables Software Release 2.
A-8 Remote YesWare Management using SNMP Table A-5 MIB variables for EtherLoop Modem CO Id and CPE Id tables Object Name Description Access Syntax IdMdmIndex The index for each modem interface. The index remains constant from one initialization of the subagent to another. It extends across all tables and uniquely identifies all modems. read-only Integer32 ModemLinkStatus The current link status of this modem. read-only INTEGER up down The current link status of the modem.
Remote YesWare Management using SNMP A-9 EtherLoop CO and CPE Statistics Tables The EtherLoop Statistics Table provides statistic information for modems. The table contains a row for each modem identified in the system. Separate Statistic tables exist for CO and CPE modems. Figure A-3 shows an example screen shot of the EtherLoop CO Stat and CPE Stat tables. Table A-6 on page A-10 details the MIB variables supported by these tables.
A-10 Remote YesWare Management using SNMP Table A-6 MIB variables for EtherLoop CO Stat and CPE Stat tables Object Name Description Access Syntax StatsMdmIndex The index for each modem interface. The index remains constant from one initialization of the subagent to another. It extends across all tables and uniquely identifies all modems. read-only Integer32 ModemTxSpeed The transmit speed for this modem. read-only Integer32 ModemRxSpeed The receive speed for this modem.
Remote YesWare Management using SNMP A-11 EtherLoop CO and CPE MAC Filter Tables The EtherLoop MAC Filter Table provides the ability to manage the MAC Filters for each modem. MAC Filtering is a means whereby communications between modems may be prevented based on MAC addresses. This privacy feature prevents traffic from other clients on the CO LAN from appearing at the CPE modem. Thus, a particular client cannot see traffic destined for other clients.
A-12 Remote YesWare Management using SNMP Table A-7 MIB variables for EtherLoop Modem CO MAC Filter and CPE MAC Filter Tables Object Name Description Access Syntax FilterMdmIndex The index for each modem interface. The index remains constant from one initialization of the subagent to another. It extends across all tables and uniquely identifies all modems. read-only Integer32 ModemMacAddDelete The Add/Delete field for MAC Filter addresses for this modem. Enter a space separated MAC address e.g.
Remote YesWare Management using SNMP A-13 EtherLoop Traps The EtherLoop Enterprise MIB defines notification events (traps) for alerting SNMP manager stations of events occurring in the EtherLoop Modem agent. The supported traps are SNMPv1 Traps and are detailed in Table A-8. Table A-8 SNMPv1 Traps supported by EtherLoop Enterprise MIB Event Number Name Description Objects 3 coModemDownEvent The CO modem identified by the objects has a link status of down and is not communicating.
A-14 Remote YesWare Management using SNMP EloopSwitch MIB The YesWare SNMP Agent supports an Elastic Networks eloopSwitch private MIB for managing ethernet switches configured on the eth1 (private side) of the YesWare Server. The eloopSwitch MIB is implemented under the Enterprises tree under the Elastic Networks private Object Identifier. The MIB is a SNMPv2 compliant MIB that conforms to RFC 1902. The EloopSwitch MIB (enelsw.
Remote YesWare Management using SNMP A-15 EloopSwitch Table The EloopSwitch Table defines variables that are associated with each configured ethernet switch in the system. The table contains a row for each switch in the system. Figure A-6 shows an example screen shot for the EloopSwitch Table. Table A-10 on page A-16 details of the MIB variables. Figure A-6 EloopSwitch Table managed by SNMPc Manager from CastleRock Software Release 2.
A-16 Remote YesWare Management using SNMP Table A-10 EloopSwitch Table Object Name Description Access Syntax swTableIndex The index for each switch interface. The index remains constant from one initialization of the agent to another and uniquely identifies each switch. read-only Integer32 swTableStatus The current status of this switch. read-only INTEGER up down polling swTableNetAddr The Network or IP address of the switch.
Remote YesWare Management using SNMP A-17 EloopSwitch Traps The EloopSwitch Enterprise MIB defines notification events (traps) for alerting SNMP manager stations of events regarding ethernet switches in the YesWare SNMP Agent. The supported traps are SNMPv1 Traps and are detailed in Table A-11. Table A-11 EloopSwitch Traps Event Number Name Description Objects 1 switchDownEvent The switch identified by the objects has a status of down and is not communicating.
A-18 Remote YesWare Management using SNMP MIB II System Group MIB The EtherLoop SNMP Agent supports the system group from the MIB II standard MIB. MIB II is a standard MIB defined by RFC 1213. (For additional information on MIB II refer to the RFC). The MIB II system group defines seven objects that are used for system identification. The objects are detailed in Table A-12. Table A-12 MIB II System Group MIB Objects Object Name Description Access Syntax sysDescr A textual description of the entity.
Remote YesWare Management using SNMP A-19 Table A-12 MIB II System Group MIB Objects sysServices read-only A value which indicates the set of services that this entity potentially offers. The value is a sum. This sum initially takes the value zero, Then, for each layer, L, in the range 1 through 7, that this node performs transactions for, 2 raised to (L - 1) is added to the sum. For example, a node which performs only routing functions would have a value of 4 (2^(3-1)).
A-20 Remote YesWare Management using SNMP MIB II SNMP Group MIB The EtherLoop SNMP Agent supports the SNMP group from the MIB II standard MIB. MIB II is a standard MIB defined by RFC 1213. . (For additional information on MIB II refer to the RFC). The MIB II SNMP group defines objects that show SNMP protocol usage and statistics for the SNMP Agent. The objects are detailed in Table A-13.
Remote YesWare Management using SNMP A-21 Table A-13 MIB II SNMP Group Objects snmpInReadOnlys The total number valid SNMP PDUs which were read-only delivered to the SNMP protocol entity and for which the value of the error-status field is `readOnly'. It should be noted that it is a protocol error to generate an SNMP PDU which contains the value `readOnly' in the error-status field, as such this object is provided as a means of detecting incorrect implementations of the SNMP.
A-22 Remote YesWare Management using SNMP Table A-13 MIB II SNMP Group Objects snmpOutBadValues The total number of SNMP PDUs which were generated by the SNMP protocol entity and for which the value of the error-status field is `badValue'. read-only Counter snmpOutGenErrs The total number of SNMP PDUs which were read-only generated by the SNMP protocol entity and for which the value of the error-status field is `genErr'.
Remote YesWare Management using SNMP A-23 Procedure A-1 Configuring SNMP Use the following procedure to configure start-up parameters for SNMP trap information. Background summary SNMP describes the protocols and object definitions necessary to manage devices on a network. EtherLoop modems do not support the SNMP protocol directly; however, the modems do support a proprietary ModeX protocol. The NSS implements both protocols and serves as the SNMP Proxy Agent for the EtherLoop modems.
A-24 Remote YesWare Management using SNMP Procedure A-1 (continued) Configuring SNMP Requirements To perform this procedure, you need the following: • The EtherLoop MIB file has been obtained from Elastic Networks. This file is named enelmdm0.mib and is distributed by Elastic Networks on a 3.5” floppy disk. Action Step Action 1 Load the enelmdm2.mib file into an SNMP network management station on the network (follow the instructions provided with your network management software).
Remote YesWare Management using SNMP A-25 Procedure A-2 Monitoring and Changing the Status of the SNMP Proxy Agent The SNMP Proxy Agent retrieves statistics about the operation and performance of modems attached to the network. If you do not plan to use the SNMP information generated by the Proxy Agent, you may want to stop the Proxy Agent. This procedure explains how to start, stop, and monitor the status of the SNMP Proxy Agent.
A-26 Remote YesWare Management using SNMP Procedure A-2 (continued) Monitoring and Changing the Status of the SNMP Proxy Agent Action Step Action 1 From the YesWare Main Menu, click SNMP Proxy Agent. The SNMP Proxy Agent dialog appears as shown in Figure A-7. Figure A-7 SNMP Proxy Agent dialog The current status of the SNMP Proxy Agent is displayed. If the Proxy Agent is running, the Stop Proxy Agent button is enabled.
I-1 Index I- A B About NSS Introduction 2-9 Adding user accounts procedure 13-13 Administration Adding user accounts 13-13 Deleting user accounts 13-15 EtherLoop modems Download Utilities, feature description 15-2 Download Utilities, using 15-1 EtherCraft, feature description 14-2 EtherCraft, using 14-1 System logs viewing 13-17 YesWare system 13-1 Administrator Password change procedure 13-10 Authorization Code Billing Introduction 1-15 Meeting room scheduling feature description 11-12 procedure 11-13
I-2 Index Billing (continued) PMS interface configuration 9-2 Port Use Context introduction 1-15 Print Services visitor billing method 12-5 records reporting procedure 8-17 Service provisioning 8-1 conference rooms 11-1 meeting rooms 11-1 VBN configurations 1-17 Billing Manager Feature description 8-2 Guest Room Billing feature description 8-3 Introduction 2-12 Billing protocol and time settings 8-3 Billing rate configuration 8-3 Branding Configuration dialog 10-7 C Check Speeds function EtherCraft 14-6 C
Index I-3 Download Utilities Downloader status and logs viewing 15-2 EtherLoop modems administration 15-1 feature description 15-2 feature description 15-2 Introduction 2-11 using 15-1 E Elastic Operating Network Configuring YWS 3-1 DNS nameserver setting procedure 3-15 EON commands 3-8 YesWare Server login default 3-7 YWS configuration procedure 3-9 YWS date setting procedure 3-13 YWS time setting procedure 3-13 EloopSwitch MIB Ethernet switch traps A-17 Enhanced Modem Biling provisioning 6-1 provisionin
I-4 Index EtherLoop modems (continued) Clear Logs function EtherCraft 14-14 Client Addresses function EtherCraft 14-11 Get Logs function EtherCraft 14-15 Modem Details function EtherCraft 14-7 Reset Modems function EtherCraft 14-16 speeds and training counts EtherCraft 14-2 Status function EtherCraft 14-12 upgrading firmware procedure 15-3 procedure, Gen-1 to Gen-2 15-6 Version function EtherCraft 14-13 EtherLoop system provisioning 6-1 Ethernet Switch Configuration dialog 7-6 Ethernet Port Billing Introdu
Index I-5 Guest rooms Print Services administrator requirements 12-4 billing method 12-5 printer limitations 12-4 printer requirements 12-4 printing procedure 12-15 provisioning 12-1 provisioning procedure 12-6 system requirements 12-2 H HOBIC AckNak Threshold 1 selection requirements 9-16 HOBIC AckNak Threshold 2 selection requirements 9-17 Home page configuration 10-7 Hostname InterProxy entry 4-6 L Login EON default 3-7 Login dialog 2-5 Logs System viewing 13-17 M I Install or Upgrade Introduction 2
I-6 Index Manager Password change procedure 13-8 Meeting rooms provisioning 11-1 Scheduling ports feature description 11-12 procedure 11-13 MIB See Management Information Base MIB II SNMP Group MIB standard MIB A-20 MIB II System Group MIB standard MIB A-18 Modem Administration Download Utilities feature description 15-2 EtherCraft 14-1 EtherCraft feature description 14-2 firmware upgrades 15-1 Check Speeds function EtherCraft 14-6 Clear Logs function EtherCraft 14-14 Client Addresses function EtherCraft 1
Index I-7 Network Mask InterProxy entry 4-6 Network Mask - network to exclude InterProxy entry 4-8 Network Services System Switch configuration 5-1 requirements 5-2 Switch provisioning procedure 5-3 Network Time Protocol configuring procedure NSS Maintenance Introduction 2-16 NTP See Network Time Protocol O Operating System Configuring YWS Operating system and software modules 2-1 Operator Password change procedure 13-10 P Parent switch Configuration example 7-4 Password YesWare administrator resetting 1
I-8 Index Procedure Authorization Code Billing provisioning 8-11 Billing records reporting procedure 8-17 Clock synchronization setting Network Time Protocol Conference Room Billing provisioning 11-4 scheduling IP addresses 11-6 visitor configuration 11-10 Conference Scheduler IP addresses, scheduling 11-6 provisioning 11-4 visitor configuration 11-10 Credit-Card Billing provisioning 8-8 Database backup and restore 13-26 Enhanced Modem Billing provisioning 6-3 EtherLoop modems firmware upgrade 15-3 firmwar
Index I-9 Property Management System (continued) Isolated connection to YWS 9-4 Line-driver connection to YWS 9-4 SNMP notification capabilities 9-16 procedure 9-18 Test record procedure 9-15 YWS connection 9-2 YWS connection procedure 9-5 Provisioning Authorization Code Billing procedure 8-11 Conference Room Billing procedure 11-4 scheduling IP addresses 11-6 visitor configuration 11-10 Conference Scheduler IP addresses, scheduling 11-6 Procedure 11-4 visitor configuration 11-10 Credit-Card Billing proced
I-10 Index SNMP, Network management (continued) YesWare EtherLoop CO and CPE MAC Filter tables A-11 YesWare EtherLoop CO and CPE Statistics tables A-9 YesWare EtherLoop MIB A-4 YesWare EtherLoop Modem System Table example A-5 YesWare EtherLoop traps A-13 YesWare Ethernet switch management, EloopSwitch MIB A-14 YesWare SNMP components A-2 YesWare supported MIBs A-2 YesWare web interface A-3 Proxy Agent A-25 Traps EloopSwitch MIB A-17 EtherLoop MIB A-13 YesWare configuration parameters A-3 EloopSwitch traps
Index I-11 U Upgrade EtherLoop modem firmware procedure 15-3 procedure, Gen-1 to Gen-2 15-6 Upgrading switch firmware 7-22 User YesWare adding user accounts 13-13 deleting user accounts 13-15 User Authentication InterProxy entry 4-7 V VBN See Visitor-based networking VBN authentication pages VBN SHOW tags 10-4 VBN page customization requirements 10-2 functions 10-3 retrieval procedure 10-11 VBN SHOW tags using 10-4 VBN page construction 10-2 VBN page graphics VBN SHOW tags 10-6 VBN port service VBN SHOW t
I-12 Index Visitor-based networking (continued) VBN web site Customization 1-24 Virtual Concierge Introduction 1-24 procedure 10-13 visitor access controls 1-22 web site branding 10-7 home/splash page 10-7 web site customization 10-1 introduction 1-24 VT-100 YWS connection method 3-5 W Web interface Default YesWare login 2-5 Remote network access restricting 13-6 Y YesWare Administration 13-1 Administrator password changing 13-10 Authorization Code Billing provisioning procedure 8-11 Billing Conference R
Index I-13 YesWare (continued) YesWare (continued) EtherLoop modems Meeting rooms firmware upgrade procedure 15-3 scheduling ports, description 11-12 firmware upgrade, Gen-1 to Gen-2 15-6 scheduling ports, procedure 11-13 privacy filters, using 13-3 Modem Connection Biling EtherLoop transport architecture 1-9 provisioning 6-1 EtherLoop transport systems 1-8 provisioning requirements 6-12 Ethernet Port Billing Modem Connection Billing Introduction 1-19 Introduction 1-20 Ethernet transport architecture 1-10
I-14 Index YesWare (continued) Property Management System configuration procedure 9-14 integration SNMP notification capabilities 9-16 SNMP trap configuration procedure 9-18 test procedure 9-15 Remote network access restricting 13-6 SDR logs retrieving procedure 8-15 Security 13-1 Server configuration procedure 3-9 Connection methods 3-4 connection methods 3-4 connections illustration 3-3 date setting procedure 3-13 DNS nameserver procedure 3-15 EON commands 3-8 functional components 3-2 login default (EON
Index I-15 YesWare (continued) Web-based modules 2-8 About NSS 2-9 Billing Manager 2-12 Conference Scheduler 2-10 Download Utilities 2-11 EtherCraft 2-13 Install or Upgrade 2-21 InterProxy 2-14 Modex Daemon 2-15 NSS Maintenance 2-16 Port Manager 2-18 Print Services 2-17 SNMP Proxy Agent 2-20 Web-based software modules using 2-4 YWS configuration procedure 3-9 YWS connection methods 3-4 YWS connections 3-3 YWS date procedure 3-13 YWS operating system EON commands 3-8 login default 3-7 YWS Telnet connection
I-16 Index Software Release 2.
Elastic Networks YesWare Applications User’s Guide Software Release 2.30 Publication Number 08-01016-01 Document Revision 2.30.1 © 2000 Elastic Networks All rights reserved The information contained in this document is subject to change without notice. Elastic Networks reserves the right to make changes to equipment design or program components, as progress in engineering, manufacturing methods, or other circumstances may warrant. EtherLoop is a trademark of Elastic Networks.
