9231 Irvine Blvd., Irvine, CA 92618 USA

949.226.7185 info@vubiqnetworks.com


Forgetting the Second Save

Talking to customers there is a common mistake that people make with a HaulPass V60s terminal.  I’m aware of this mistake myself as I have made it, too.  The error is forgetting the second save.

The V60s has three configurations that it maintains:

  1. The running-config
  2. The default-config
  3. The startup-config

The running-config is the actual configuration that is loaded into memory and is actively in use. When you change a setting via the web interface or telnet the change is only made in the currently running configuration. If the switch stops working in your network you can power cycle the terminal and bring it up in the last saved configuration. This allows you to make non-permanent or trial changes without committing to them.

The default-config holds the factory default settings and is not changeable by the user. If you need to, you can restore the factory defaults from the left hand side menu:  Maintenance > Factory Defaults.  If you are locked out of the web interface, you can reset the device to factory defaults by creating a loop between the two RJ45 ports and the POE Injector. See the IP and Password Restore Tech Note.

The startup-config is saved in non-volatile memory and is copied to the running-config on system boot. The startup-config is changed by copying the running-config to startup-config. This is also known as the second save. The second save is accomplished by selecting the menu choice Maintenance > Save startup-config and then pressing the Save Configuration button.

A change that we made in the latest firmware revisions (Radio Firmware Version 2.04.23, Software Version 2_4_9) was to make it easier to know if you have performed the second save or not. When you make a change to the running-config the banner in the upper right hand of the web displays changes to CFG STATUS: SAVE startup-config indicating that you need to save your changes if you intend to keep them. Anytime the running-config and the startup-config are different this is the message displayed.

After you successfully perform the second save, the status will change to be CFG STATUS: SAVED indicating that the current running-config has been saved to non-volatile memory and the current running-config will be restored on the next power cycle or reboot.

So after making changes, double check the CFG STATUS before closing the web browser window to be sure that you have saved the configuration that you want to save.

One last item. You may notice in the pictures that I have set the terminal NAME to be V60s-Demo. You can change this to almost anything you’d like to change it to in order to help you identify which terminal you are working with when you have the web browser window open. The terminal name is set with menu option Configuration > System > Information.

What else would you like to learn about? Send me an email and let me know. Michael Klett.

V60s Field Link Monitoring

A service that Vubiq Networks, Inc. offers our customers is performance monitoring of our links out in the field.  We monitor the links using SNMP, Simple Network Management Protocol, data.  In order to capture the SNMP data we only need IP access to the terminal via a public IP address or a VPN and the Read SNMP Community string, typically “public”.

The SNMP variables and their alarm limits that give us the most information are:

  • Vubiq RF DSSI, OID:
    Digital signal strength indicator from 0 (no signal) to 100 (perfect signal).  Integer32 (0..100), Read Only
    Vubiq recommends:  Warning limit:  below 90%; Error limit:  below 50%
  • Vubiq RF Board Temp, OID:
    Board temperature in ⁰C.  Integer32, Read Only
    Vubiq recommends:  Warning limit:  above 80 ⁰C; Error limit:  above 85 ⁰C
  • Vubiq RF TX Temp, OID:
    Transmit module temperature in ⁰C.  Integer32, Read Only
    Vubiq recommends:  Warning limit:  above 70 ⁰C; Error limit:  above 80 ⁰C
  • Vubiq RF RX Temp, OID:
    Receiver module temperature in ⁰C.  Integer32, Read Only
    Vubiq recommends:  Warning limit:  above 70 ⁰C; Error limit:  above 80 ⁰C
  • Vubiq RF Board Uptime,
    The number of seconds since the unit was powered on.  Basically, (sysUpTime * 100).  Integer32, Read Only
    Vubiq recommends:  Warning limit:  below 300 seconds.
  • Vubiq RF RX FEC Errors, OID:
    The raw FEC correctable error counts.  Counter32, Read Only

The entire list of Vubiq V60s SNMP variables can be found here.

To have your terminal’s performance monitored and tracked or for more information about Vubiq’s SNMP Data please contact Michael Klett.