American Power Conversion www.apcc.com
(c) Copyright 1999 All Rights Reserved

MasterSwitch Release Notes 
Firmware Revision : v1.1.2
April 26, 1998

-------------------------------------------------------------------------------
Files Included On This Disk
-------------------------------------------------------------------------------

    * powernet.mib - Includes MasterSwitch MIB.
    
    * pdu.tdf      - HP OpenView trap definition file for MasterSwitch traps.
    
    * pduguide.pdf - MasterSwitch User Guide in PDF format readable with 
                     Adobe Acrobat. Adobe Acrobat Reader is availiable at no 
                     charge at Adobe's web site. 
    
    * qckstart.pdf - Quick Start instructions for MasterSwitch (also included
                     as a hardcopy sheet) in PDF format readable with Adobe 
                     Acrobat.
                     
    * readme.txt   - This file.
    
-------------------------------------------------------------------------------
Modification History
-------------------------------------------------------------------------------
June 12, 1997     - DNS bug report added.
September 1, 1997 - ARP bug report added.
October 1, 1997   - Lockup bug bug report added.
January 14, 1998  - Added MasterSwitch Firmware Release section.
                  - Added New Features section.
                  - Indicate changes to console login procedure.
March 5, 1998     - Final changes for release.
September 3, 1998 - Add New Features v1.1.0 vs. v1.1.1 section
                  - Poor network performance bug report added.
                  - Broadcast levels exceed 30 packet/second bug report added.
                  - Authentication Trap bug report added.
April 26, 1998    - Slow Telnet and Web request from Win98 client report added.
                  - Denial of service attacks report added.
                  - Class C IP addresses do not allow supernetting report added.
                  - TCP connection reset message report added.

-------------------------------------------------------------------------------
MasterSwitch Firmware Release
-------------------------------------------------------------------------------
April 1997        - v1.00
November 1997     - v1.01
March 1998        - v1.1.0
September 1998    - v1.1.1
April 1999        - v1.1.2

-------------------------------------------------------------------------------
New Features : v1.1.1 vs. v1.1.2
-------------------------------------------------------------------------------
*  None


-------------------------------------------------------------------------------
Bug Reports & Fixes
-------------------------------------------------------------------------------

  Date :
    June 12, 1997 

  Problem :
    A DNS entry for a MasterSwitch contains a "-" character.  When a form is
    submitted for processing the MasterSwitch appears to hang for sometime and
    a manual page reload is necessary.

  Resolution :
    There is no known workaround for this problem besides not using a "-" in
    the DNS entry for MasterSwitch.

    You should contact APC tech support to upgrade to the 1.01 Maintenance 
    release or the lastest version.

-------------------------------------------------------------------------------
  Date :
    September 1, 1997 

  Problem :
    The target hardware address field in ARP requests transmitted from the 
    MasterSwitch is filled with the MasterSwitch's hardware address instead
    of being cleared to all zeros.  Typically, this field is ignored by the 
    receiver since it contains no useful information.  It is up to the 
    receiver to fill in this field for the response.  To date, the only known 
    type of receiver which appears to reject the MasterSwitch ARPs has been 
    a Novell Router implemented in software.

  Resolution :
    There is no workaround for this problem since it is the receiver which 
    decides that the packet is corrupt and rejects it.

    You should contact APC tech support to upgrade to the 1.01 Maintenance 
    release or the latest version.

-------------------------------------------------------------------------------
  Date :
    October 1, 1997 

  Problem :
    This bug can manifest itself in several different ways. This bug typically 
    occurs on bursty or switched networks with modest to high traffic levels :

  Symptoms :
    - MasterSwitch does not allow user to login via the Web pages or serially.
    - MasterSwitch allows user to perform one outlet command and subsequently
      rejects further outlet commands.
    - MasterSwitch controller warm starts frequently.
    - MasterSwitch displays conflicting outlet state information on the Web 
      pages.
    - MasterSwitch is inaccessible via Web or serially and does not reboot.
    - MasterSwitch may initiate a cold start sequence erroneously (can 
      potentially turn outlets off.)
    - MasterSwitch Web pages load very slowly.

  Resolution :
    You should contact APC tech support to upgrade to the 1.01 Maintenance 
    release or the latest version.

-------------------------------------------------------------------------------
  Date :
    February 27, 1998 

  Problem :
    The Enterprise OID does not appear correctly in traps.
    
  Symptoms :
    None.
    
  Resolution :
    v1.1.0 ensures that correct enterprise OID is sent with traps. You should
    contact APC tech support to upgrade to the v1.1.0 Feature release or latest
    version.
 
-------------------------------------------------------------------------------
  Date :
    April 14, 1998 

  Problem :
    Poor network performance.
            
  Symptoms :
    Slow system response time.
   
  Resolution :
    v1.1.1 improves network performance.

------------------------------------------------------------------------------
  Date :
    May 4, 1998 

  Problem :
    As broadcast levels exceed 30 packets per second the MasterSwitch web server
    resets the TCP connections.
            
  Symptoms :
    The browser displays an error dialog which indicates that the MasterSwitch
    reset the TCP connection and the web page does not load.
   
  Resolution :
    v1.1.1 will improve performance of the web server so that MasterSwitch web
    pages can be loaded with broadcast levels of at least 40 packets per second.

------------------------------------------------------------------------------
  Date :
    June 23, 1998 

  Problem :
    The Authentication Trap setting is reported incorrectly by the console.
            
  Symptoms :
    If the user sets or views the Authentication Trap setting via the console,
    then they will notice that it doesn't correspond to the setting reported
    via the web page, and that they are actually opposite; i.e. if the console
    reports enabled, then the web reports disabled, and vice versa. In addition,
    if the users sets the Authentication Trap to enabled via the console, then
    they are actually disabling it, and vice versa.
   
  Resolution :
    v1.1.1 will fix the console bug to report and set the Athentication Trap
    setting correctly. However, an immediate solution would be to have the user
    set it via the web, since it is correctly reported and set by that interface.


-------------------------------------------------------------------------------
  Date :
    Sept 30, 1998 

  Problem :
    Telnet and Web may respond very slowly to requests from a WINDOWS 98 client.
		            
  Symptoms :
    Telnet and Web respond slowly to requests from a WINDOWS 98 client with
    little traffic on the network.

  Resolution :
    v1.1.2 will fix a bug in the TCP/IP stack. New TCP options where added
    in WIN98 stack that the stack did not handle correctly.


-------------------------------------------------------------------------------
  Date :
    Nov 16, 1998 

  Problem :
    Denial of service attacks (Ping of Death, Nestea, etc.) cause the Card
    to hang and then reboot.
		            
  Symptoms :
    User cannot login to Card after an attack until the Card reboots.

  Resolution :
    v1.1.2 fixes the TCP/IP stack to not allow fragmented pings. It was tested
    and passed with attacks of the following type: 
    Ping of Death, Nestea, Bonk, Jolt, Land, Newtear, Syndrop, Teardrop, Winnuke.

-------------------------------------------------------------------------------
  Date :
    Nov 19, 1998 

  Problem :
    Class C IP addresses do not allow supernetting.
		            
  Symptoms :
    The user configures the Management Card with a Class C IP address with a
    subnet mask which does not have 0xFF as the first three octets.  The user
    is unable to access the unit from the same supernet.

  Resolution :
    v1.1.2 fixes the TCP/IP stack to not OR the class mask with the user
    defined mask.    

-------------------------------------------------------------------------------
  Date :
    Nov 24, 1998 

  Problem :
    Occasionally, through the web, a TCP connection reset message occurs.
		            
  Symptoms :
    The user is browsing the MasterSwitch, and is given a TCP connection reset
    message.  They then have to reload the page to continue.

  Resolution :
    v1.1.2 fixes the Web server to handle reset conditions.


-------------------------------------------------------------------------------
Network Configuration Notes
-------------------------------------------------------------------------------

1. Network Configuration

    * MasterSwitch ships with BOOTP enabled.  If you are using BOOTP then you
      need to configure your BOOTP server with the MAC address of the 
      MasterSwitch and what IP address, subnet mask, and default gateway it
      will use.

    * If you are NOT using BOOTP then you must set up a terminal session with
      the parameters enumerated in Using the Terminal Interface below.

    * If you do not see the User Name prompt then hit the <ENTER> key. If you 
      still do not see the User Name prompt then you need to reconfirm the serial 
      communication parameters and comport you are attempting to use. Also
      some terminal interfaces, like HyperTerminal, require you to disconnect
      and then reconnect through the menu in order for changes to the serial
      communication parameters to take effect.

    * Once you see the User Name prompt enter lowercase "apc" as the user name.
      You will then be prompted for a password. Enter "apc" as the password.      
      Change your password immediately by using the MasterSwitch->Passwords
      menu.

    * After Accepting Changes for for new password press CTRL-C to get back to
      the Main Menu.  Now select Network->TCP/IP.  If BOOTP is enabled then 
      disable BOOTP and Accept Changes. Now supply the IP, subnet mask, and 
      default gateway for the MasterSwitch.   Select Accept Changes again to 
      save the new settings. You now need to logout of the MasterSwitch for the 
      new network settings to take effect. Press CTRL-C and then select Logout.

    * When the MasterSwitch has been reinitialized you will see the Status LED 
      turn solid green indicating that the unit can be accessed over the network.
    
 
-------------------------------------------------------------------------------
WEB Notes
-------------------------------------------------------------------------------

1. Web Access
    
    * After setting up the network configuration of the MasterSwitch, either
      through BOOTP or the terminal interface, you should be able to view
      the MasterSwitch with a web browser that supports frames by entering
      the IP address of the MasterSwitch as the URL.
      
    * You can define a DNS entry for the MasterSwitch and reference it by a
      name instead of an IP address.
                               
    * The default user name is "apc".

    * The default password is "apc".

    * The MasterSwitch has its own home page at APC.  A link to the home page
      is provided in the navigation frame when viewing the device through a
      web browser.  The link is called <MSwitch HPg>. You will find up-to-date
      information about MasterSwitch and answers to some FAQs as well as some
      useful utilities.

    * Through the Web interface you can configure almost all the options that
      MasterSwitch has to offer.

-------------------------------------------------------------------------------
Serial Interface Notes
-------------------------------------------------------------------------------
	
1. Using a Modem
		
    If a modem is to be hooked up to the PDU's serial port, the
    modem's parameters must be pre-configured. To configure the modem 
    connect it to a PC and use a terminal program like Windows 3.11 Terminal to
    send commands to the modem.
		
        * A standard female DB-9 modem cable should be used.

        * The modem's baud rate must match the user set baud rate stored
          in the PDU's memory. Typically the modem will automatically
          match the baud rate of the MasterSwitch or the terminal session
          which is used to perform configuration.

        * Auto-Answer must be enabled. The standard AT command for
          enabling auto answer in 2 rings is : ATS0=2.

        * All answer mode result codes must be disabled (i.e. RING, 
          CONNECT, ...). The standard AT command for disabling 
          result codes is : ATQ1. ATTENTION : Once you disable result codes
          you will no longer see OK responses for commands you enter at the
          terminal window, but that does NOT mean that the commands you enter
          are not being accepted by the modem.

        * Echo must be disabled. The standard AT command for disabling
          echo is : ATE0. ATTENTION : Once echo has been disabled you will
          no longer see characters appear in your terminal session window
          that does NOT mean that the characters you are typing are not being
          recognized by the modem.  You can enable local echo of characters 
          with your terminal program.

        * It is suggested that this configuration be stored as the power on 
          default for the modem. The standard AT command for saving current
          modem settings to non-volatile memory as a power on default is :
          AT&W0.

        * In general configuring a modem to work in conjunction with a
          MasterSwitch will require experimentation and patience. The AT
          command set is not universally adhered to so you may need to
          use commands different than those above or in addition to those
          above. The MasterSwitch unit does not know whether it is 
          connected to a modem or a PC and it does not need to know.


2.  Using the Terminal Interface

    If a terminal is to be connected to the serial port, the terminal 
    parameters must be set to the following:

        * 8 data bits
 
        * 1 stop bit

        * No flow control

        * No parity

        * The desired baud rate, default is 19200.
 

3.   Serial Interface Password Protection.

    * The user has three chances to log in with the correct password. If the 
      user name and password are not entered correctly after three attempts, 
      the user must wait 2 minutes before another login can be attempted again.
 
    * The default user name is "apc".

    * The default password is "apc".

-------------------------------------------------------------------------------
Miscellaneous Notes 
-------------------------------------------------------------------------------

    * There can be only one user logged into the MasterSwitch for write access
      at any given time.

    * Only one Web user can be logged in at any given time.

    * Only one Control Console user can be logged in at any given time serially
      or via Telnet. Accessing the Control Console serially has priority over
      accessing the Control Console via Telnet.

    * The Control Console has priority over the Web interface and SNMP. The Web
      interface will be logged out by the Control Console if both access the 
      MasterSwitch at the same time.

    * The Web and the serial interface share the same, user configurable 
      inactivity time-out, user name, and password.  
      
    * SNMP does not have the concept of a log in. All SNMP transactions are 
      atomic and sets can only be done when the Web and the Control Console 
      are both logged out. Gets can be done anytime.

	


