VMS v3.6.
VMS v3.6.x VIPERSAT Management System User Guide Part Number MN/22156 Document Revision 3 Software version 3.6.
COMTECH EF DATA VIPERSAT Network Products Group 3215 Skyway Court Fremont, CA 94539 USA Phone: (510) 252-1462 Fax: (510) 252-1695 www.comtechefdata.com Part Number: MN/22156 Revision: 3 Software Version: 3.6.x ©2008 by Comtech EF Data, Inc. All rights reserved. No part of this document may be copied or reproduced by any means without prior written permission of Comtech EF Data. All products, names and services are trademarks or registered trademarks of their respective companies.
Document Revision History Revision Description 0 Initial Release. Note: This new document part number, MN/22156, supersedes the previous VMS User Guide part number, 22156. 1 New functionality in v3.5.x: VMS N:1 Redundancy; Site Distribution Lists; CDM-700 Outof-Band Driver; CDD-564IF InBand Driver 2 New functionality in v3.6.0: VMS SOTM, VNO and Global Map View 3 New functionality in v3.6.
{ This Page is Intentionally Blank }
Table of Contents Chapter 1 General How to Use This Manual . . . . . . . . . . . 1-1 Manual Organization . . . . . . . . . . . . 1-1 Chapter 1 — General . . . . . . . . . 1-1 Chapter 2 — VMS Installation . . . . . 1-1 Chapter 3 — VMS Configuration . . . 1-2 Chapter 4 — Configuring Network Modems . . . . . . . . . . . . . . . 1-2 Chapter 5 — VMS Services . . . . . . 1-2 Chapter 6 — Out-of-Band Units . . . . 1-2 Appendix A — VMS Cross Banding . . 1-2 Appendix B — Antenna Visibility. . . .
Configure Addresses and Assign ID. VMS Network Build Procedure . . . . . Subnet Manager Configuration . . . Setting the Alarm Masks . . . . . . Enabling Auto Home State . . . . Bandwidth Manager Configuration . Create Satellite(s) . . . . . . . . . Create Transponders . . . . . . . Create Antennas . . . . . . . . . . Create Antenna Devices . . . . . . InBand Manager Configuration . . . Pool Management . . . . . . . . . . Network Manager Configuration and ViperGlobe . . . . . . . . . . . . .
Appendix B Antenna Visibility General . . . . . . . . . . . . . . . . . . . . B-1 Using Antenna Visibility . . . . . . . . . . . . B-2 Example — Blocking Spectrum Affected by Local Ground Frequency Interference .B-5 Appendix C Redundancy General . . . . . . . . . . . . . . . . . . . . C-1 VMS Redundancy . . . . . . . . . . . . Description. . . . . . . . . . . . . . Redundant Hot-Standby . . . . . . . Protection Switch-over. . . . . . Active to Standby Switch . . . Active Server Role . . . . . . . .
Load switching . . . . . . . . . . . . . . . . F-2 Bandwidth Allocation and Load Switching by the STDMA Controller:. . . . . . . . . F-3 Load Switching Process . . . . . . . . . F-7 Load Switching by a Remote . . . . . . F-7 Determining Need-for-Change. . . . . . F-9 Load Switch Example . . . . . . . . . . . . . F-10 Reduced data flow in switched mode (SCPC) . . . . . . . . . . . . . . . F-12 Application switching . . . . . . . . . . . . . F-13 Type of Service (ToS) switching. . . . . . . .
List of Figures Chapter 1 Figures Figure 1-1 VMS ViperView display . . . . . . . . . . 1-6 Figure 1-2 ViperView Client, Server (VOS) Relationship . . . . . . . . . . . . . . . . . . . . . . 1-8 Chapter 2 Figures Figure 2-1 Automatic Updates window, Recommended Setting . . . . . . . . . . . . . 2-2 Figure 2-2 System Properties menu. . . . . . . . . 2-5 Figure 2-3 Advanced tab . . . . . . . . . . . . . . . . . 2-5 Figure 2-4 DEP tab. . . . . . . . . . . . . . . . . . . . . .
Figure 3-15 Create Transponder dialog . . . . . 3-16 Figure 3-16 Create Antenna dialog . . . . . . . . 3-17 Figure 3-17 Antenna Visibility, Default Settings . . 3-18 Figure 3-18 Create Up Converter dialog . . . . 3-19 Figure 3-19 Create Down Converter dialog . . 3-19 Figure 3-20 Converter Icons on Antenna View3-20 Figure 3-21 New Devices Added to Converters . . 3-21 Figure 3-22 BC Carrier Flag Setting, CDM-570/ 570L. . . . . . . . . . . . . . . . . . . . . . . . . . .
5-23 Figure 5-30 Distribution List Window . . . . . . . 5-24 Figure 5-31 Add Site Dialog, Search Network 5-24 Figure 5-32 Add Site Dialog, Select Subnet . . 5-25 Figure 5-33 Distribution List Window, Configured 5-25 Figure 5-34 Distribution List Created . . . . . . . 5-25 Figure 5-35 Subnet Manager . . . . . . . . . . . . . 5-26 Figure 5-36 Separate window. . . . . . . . . . . . . 5-27 Figure 5-37 Subnet Manager . . . . . . . . . . . . . 5-27 Figure 5-38 Subnet Manager configuration . .
Figure C-4 VMS Server Properties, General Tab. C-8 Figure C-5 VMS Server Properties, Traps Tab . . C-10 Figure C-6 Activate Command, VMS Server Menu C-11 Figure C-7 Synchronize Command, VMS Server Menu . . . . . . . . . . . . . . . . . . . . . . . . . .C-11 Figure C-8 N:M redundancy logic diagram. . .C-14 Figure C-9 N:M block diagram . . . . . . . . . . . .C-17 Figure C-10 Typical N:M redundant installation . . C-18 Figure C-11 N:M Redundancy Hierarchy . . . .C-19 Figure C-12 Redunancy Manager Tree . . . .
Figure D-33 Additional domain controller with domain name. . . . . . . . . . . . . . . . . . . .D-22 Figure D-34 Directory and log folders dialog .D-23 Figure D-35 Shared system volume . . . . . . . .D-23 Figure D-36 Directory services restore mode administrative password . . . . . . . . . . .D-24 Figure D-37 Summary screen . . . . . . . . . . . .D-24 Figure D-38 Active directory installation wizard screen . . . . . . . . . . . . . . . . . . . . . . . . .
{ This Page is Intentionally Blank } x VMS User Guide
List of Tables Chapter 4 Tables Table 4-1 CDM-570/570L Modem/Router Manual Connection Options . . . . . . . . . . . . . . . . . . .
{ This Page is Intentionally Blank } xii VMS User Guide
CHAPTER GENERAL How to Use This Manual This manual documents the features and functions of the Vipersat Management System (VMS), and guides the user in how to install, configure, and operate this product in a Vipersat network. NOC administrators and operators responsible for the configuration and maintenance of the Vipersat network, as well as earth station engineers, are the intended audience for this document.
How to Use This Manual Chapter 3 — VMS Configuration Covers the Quick Configuration procedure as well as detailed steps for full System Configuration in building the Vipersat network. Chapter 4 — Configuring Network Modems Describes how VMS is used to configure modems in the Vipersat network. Chapter 5 — VMS Services Describes the various service managers that comprise VMS and how ViperView is used to monitor and control the Vipersat network.
How to Use This Manual Appendix G — Entry Channel Mode Switching Supplement on how ECM provides a method for remotes to switch from STDMA to SCPC and back. Appendix H — VMS Billing Log Translator (VBLT) Covers how to install and operate VBLT, an application that converts switch events into billing log format. Appendix I — Glossary A glossary of terms that pertain to Vipersat satellite network technology.
How to Use This Manual • CDD-562L/-564 Demodulator with IP Module Installation and Operation Manual (Part Number MN/CDD562L-564.
P r o d u c t D e s c r i p t io n Product Description Introduction The Vipersat Management System (VMS) is a network management system that uses information it receives from the network’s VMS controlled modems. The VMS controlled modem’s internal microprocessor based input/output (I/O) controller measures, captures, and transmits these detected, real-time network operating parameters to VMS via PLDM (Path Loss Data Message) packets.
Product Description ble and can be modified by the operator at any time, as described in this User’s Guide, to optimize network Management and Control. Figure 1-1 VMS ViperView display Vipersat uses IP connections between network nodes, supporting UDP connectivity. The Vipersat VMS controlled modem, consisting of a satellite modem with an imbedded microprocessor router, which is the interface between LAN traffic and the satellite links that connect remote stations to the hub.
P r o d u c t D e s c r i p t io n is stored in a single place, processed by VMS running on the central server, and the results are available to all clients across the network. Through its client/server architecture, VMS supports centralized management, control, and distribution of data, alarms, and events. VMS also simultaneously supports multiple clients, network management, and complete visibility of the entire network operation.
Product Description analyzes and acts on this information to intelligently control network operation to optimize bandwidth utilization and overall network performance. VMS Vipersat Operating System (VOS) Server Redundant VMS Servers VMS Vipersat Operating System (VOS) Server VMS Client ViperView VMS Client ViperView Figure 1-2 ViperView Client, Server (VOS) Relationship The VMS management and monitoring system uses an intuitive graphic display, as illustrated in figure 1-1.
P r o d u c t D e s c r i p t io n • Bandwidth resource allocations • Modem, RF equipment, and VSAT station management The network map displays an integrated view of the entire network including all nets, subnets, equipment, and equipment interconnections. You can doubleclick on an icon to display its status information and/or sub-components. Right clicking on an icon displays a drop-down menu allowing the operator to issue commands, change configurations, or change the unit’s state, as applicable.
Product Description CDM-570/570L Full MIB OOB M&C The CDM-570/570L is supported as an OOB device operating without IP option card. This new device driver provides the monitoring and control of standard base modem control within and IP overlay network through SNMP. Satellite Advanced Switching (Remote Roaming) This new remote roaming feature provides advanced switching per remote to any given satellite.
P r o d u c t D e s c r i p t io n SLM-5650A Demodulator Only Support The SLM-5650A optioned through FAST Codes produces a new device structure that masks all modulator functions. This new product is supported in this release by reading feature sets from the device providing for demodulator only.
C u s t o m e r S up p o r t Customer Support Contact Information Contact Comtech Vipersat Networks Customer Support for information or assistance with product support, service, or training on any Vipersat product. Mail: 3215 Skyway Court Fremont, CA 94539 USA Phone: 1+510-252-1462 Fax: 1+510-252-1695 Email: supportcvni@comtechefdata.com Web: www.comtechefdata.
CHAPTER VMS INSTALLATION General The Vipersat Management System software should be installed on a highperformance, industry-standard computer running the Microsoft Windows Server 2003 or later operating system. For specifications for the minimum recommended VMS hardware configuration, please refer to the VMS Release Notes for the version of software that will be installed. Both Server and Client configurations are provided. The VMS software is installed using an Installation Wizard.
General VMS Server - MS Automatic Updates Setting The Microsoft Windows OS Automatic Updates feature provides a selection of configuration settings. The default setting, Automatic, will automatically download and install Windows updates. Typically, this process includes an automatic reboot of the server to implement the updates.
General Types of Installation The VMS can be installed in three different configurations: 1. On a single VMS server; Vipersat Operating System (VOS). 2. On two or more (N:1) VMS servers in the optional fault-tolerant, redundant configuration; Vipersat Operating System (VOS). 3. On a client workstation; Viperview User Interface.
Preparing Server for VMS Installation Preparing Server for VMS Installation If not already done, perform the following tasks before proceeding with installation of VMS on the server: • Limit DEP (Data Execution Prevention) — see following section. • Create a user account in the Active Directory (example: VMS). • Add the VMS user to the DCOM Limits. • Reboot the server before continuing with the VMS installation.
P r e p a r i n g S er v e r f o r V M S I n s t a l l a t i o n Figure 2-2 System Properties menu 2. Click the Advanced tab to display the dialog page shown in figure 2-3.
Preparing Server for VMS Installation 3. In the Performance box on the Advanced tab, click the Settings button then click the Data Execution Prevention tab to show the dialog shown in figure 2-4. Figure 2-4 DEP tab 4. Select the Turn on DEP for essential Windows Programs and services only radio button. If the CPU processor does not support DEP, this radio button will be greyed out and unavailable. 5. Click the OK button to complete this procedure.
P r e p a r i n g S er v e r f o r V M S I n s t a l l a t i o n it has been brought online as the active server. Use the following procedure to enable Global Caching on backup servers. 1. From the Server Start menu, open the NTDS Site Settings Properties window from: Administrative Tools > Active Directory Sites and Services > Default-First-Site-Name. 2.
Preparing Server for VMS Installation Configuring Server as Domain Controller and/or DNS NOTE Note: If the server is to be used as a domain controller, it must be configured as a domain controller at this time before proceeding with the VMS installation. In a redundant configuration, the servers must be configured as domain controllers and DNS.
P r e p a r i n g S er v e r f o r V M S I n s t a l l a t i o n Figure 2-6 Backup Command, VMS Server 2. Enter the Name for the backup file and select the directory location for saving the file from the Save As dialog window that opens (figure 2-7).
Preparing Server for VMS Installation Stopping Previous VMS Version (Upgrade) If you are installing VMS on a server which does not have a previous version of VMS installed, skip this “Stopping Previous VMS Version (Upgrade)” section and proceed with the instructions in the section “VMS Server Installation” on page 2-14. Caution: If a prior version of VMS is installed and running on the server, you must first stop, then uninstall, this prior version as described in the following procedure.
P r e p a r i n g S er v e r f o r V M S I n s t a l l a t i o n 3. Select each process and click on the End Process button. A Task Manager Warning dialog will appear (figure 2-9)—click on the Yes button to terminate the process. Figure 2-9 Task Manager Warning dialog 4. After each of the three processes have been terminated, close the Task Manager window then re-open it to confirm that the processes are no longer running. 5.
Preparing Server for VMS Installation Figure 2-10 Add or Remove Programs Control Panel 2. Select Vipersat Management System and click the Remove button (figure 2-11).
P r e p a r i n g S er v e r f o r V M S I n s t a l l a t i o n Figure 2-11 VMS, Remove Program 3. Close the Add or Remove Programs window.
VMS Server Installation VMS Server Installation NOTE Note: For VMS Redundancy Server configurations, after installing VMS on each of the servers as described in this section, refer to Appendix C, “Redundancy”, for detailed instructions for configuring the redundant servers. The installation process is highly automated and typically does not require manual intervention unless the installation is to be non-standard. 1. Locate the file VMS 3.x Install.
V M S S e r v e r I n s t a l l a t io n Figure 2-13 License Agreement screen 4. From the Installation Type screen shown in figure 2-14, select the radio button for the type of installation you will be making. The VMS software is comprised of two main components, the Server component and the Client component. • Full Install - This type of installation installs both components, and allows a local user to operate VMS locally on the server and also remotely.
VMS Server Installation Figure 2-14 Installation Type screen 5. Click the Next button to proceed to the VMS Setup screen. 6. The Service Configuration defaults with all three boxes checked as shown in figure 2-15. It should be left this way. Figure 2-15 Service Configuration dialog 7. Enter the User name for the account (e.g., VMS). Note: If this is an upgrade, use the same name as before.
V M S S e r v e r I n s t a l l a t io n 8. If the VMS server is to operate in a Domain, enter the domain name in the Domain field exactly as the domain is named. Caution: Failure to have an exact match between the assigned domain name and the domain name entered in this dialog will cause VMS to fail, requiring re-installation. 9. The Password field is auto-filled with the default password, vipersat. Enter a new password, if desired, to change the default setting.
VMS Server Installation Figure 2-17 Choose Install Location dialog 14. From the Choose Start Menu Folder dialog shown in figure 2-18, accept the default folder name, VMS 3.x, and click the Install button to start the installation process. Figure 2-18 Choose Start Menu Folder dialog 15. The installation process will be interrupted with the notice shown in figure 2-19. Click on the Continue Anyway button to continue.
V M S S e r v e r I n s t a l l a t io n Figure 2-19 Software Installation notice 16. During installation, the Waiting dialog shown in figure 2-20 asking you to insert USB key will pop up and the installation progress bar will stop. Note: This step will not occur if the key is already plugged in or when performing a Client Install, since a USB key is not required for this installation type. Install the Vipersat Crypto-Box key by plugging it into an available USB port on the VMS server.
VMS Server Installation Figure 2-20 Install Cypto-Box Key prompt 17. The Found New Hardware Wizard will start. Select the No, not this time radio button, then click Next to continue. Figure 2-21 Found New Hardware Wizard 18. On the Hardware Installation notice shown in figure 2-22, click the Continue Anyway button to continue.
V M S S e r v e r I n s t a l l a t io n Figure 2-22 Hardware Installation 19. The installation process will continue and, when completed, the screen shown in figure 2-23 will be displayed. Click the Finish button to exit. Figure 2-23 Hardware Installation Completed screen 20. Click the OK button in the Waiting dialog shown in figure 2-20 to complete the installation and updating of the Crypto-Box Key.
VMS Server Installation 21. After installing and/or updating the key, the installation will complete as shown in figure 2-24. Click the Next and then the Finish button to exit the installation wizard. Figure 2-24 Installation Complete dialog NOTE Note: If this is a standalone on a workgroup server, or an upgrade installation, move on to the section “Verifying Successful Server Installation” on page 2-27.
Setting Com Security for VMS Setting Com Security for VMS 1. From the Windows Start menu, select Settings and open up the Control Panel, as shown in figure 2-25 below. Figure 2-25 Control Panel 2. Select Administrative Tools and then Component Services, as shown in figure 2-26. Figure 2-26 Administrative Tools 3. Expand the Component Services tree until “My Computer” appears, and select Properties, as shown in figure 2-27.
Setting Com Security for VMS Figure 2-27 Component Services, My Computer Menu 4. Select the COM Security tab, then the Edit Limits button under Launch and Activation Permissions, as shown below in figure 2-28. Figure 2-28 Com Security, Edit Limits 5. In the Launch Permissions window, select Add as shown in figure 2-29.
Setting Com Security for VMS Figure 2-29 Launch Permissions 6. Ensure the Location is the domain, then type “VMS” in the object box and select Check Names. If the location was correct you should see the result shown in figure 2-30. Figure 2-30 Select Users 7. Click on OK. This will return you to the Launch Permissions window with the new user highlighted. Check Allow on any boxes that are blank as shown in figure 2-31, then click the OK button.
Setting Com Security for VMS Figure 2-31 Launch Permissions with New User This concludes setting the Component Securities on the Domain Controller.
V e r i f y i n g S u c c e s s f u l S er v e r I n s t a l l a t i o n Verifying Successful Server Installation 1. Open the Services window on the server by selecting Services from the Start>Administrative Tools menu. Figure 2-32 Services, Administrative Tools menu 2. Select Vipersat Management System from the Services list as shown in figure 2-33, then click on Start the service. This will start the VOS (Vipersat Operating System).
V e r i f y i ng S u c c e s s f u l S e r v e r I n s t a l l a t i o n Figure 2-33 Vipersat Management System Service 3. From the Program File directory, find VMS 3.x and click the Connection Manager. Accept “localhost” and click on the OK button in the Connect To dialog. The Viperview window will appear, as shown in figure 2-34.
V e r i f y i n g S u c c e s s f u l S er v e r I n s t a l l a t i o n This completes the VMS server installation procedure. • For VMS Standalone Server configurations, proceed to Chapter 3, “VMS Configuration”, to configure the VMS database for the satellite network. Note: If this is an upgrade, the network database will already exist and configuration is not required. • For VMS Redundancy Server configurations, proceed to Appendix C, “Redundancy”, for instructions on configuring redundant servers.
VMS Client Installation VMS Client Installation The Vipersat Management System client software should be installed on a highperformance, industry-standard workstation computer running Microsoft Windows XP Professional with SP2. For specifications for the minimum recommended VMS platform configuration, please refer to the VMS Release Notes for the version of software that will be installed.
V M S C l i e n t I n s t a l l a t io n Figure 2-35 Client Install Once the installation wizard is finished, return to continue with the following section. Creating Client Accounts It is necessary to configure the appropriate security settings for the Client workstation to gain network access privileges to the VMS server. If this is a client for a standalone VMS, an account must be created on the VMS server for the client to log into. The VMS account must also be added to the Client machine.
VMS Client Installation Figure 2-36 Admistrative Tools menu 2. Expand the Domain name tree, right-click on Users and select New Group from the drop-down menu, as shown below in figure 2-37. Figure 2-37 Create Group 3. The New Object–Group dialog will open. Under Group Name, enter VMS Users and ensure that the Group Scope and Group Type are set as shown in figure 2-38. Click on the OK button to close the dialog.
V M S C l i e n t I n s t a l l a t io n Figure 2-38 Create Group Dialog 4. Right-click on Users again in the Active Directory window and select New User. The New Object–User dialog will open (figure 2-39). The user name can be anything desired and will be used to log onto the server from the client machine. Figure 2-39 Create User Dialog 5. Click Next and the User Password dialog will open, as shown in figure 2-40. Create and confirm a password and set the properties as indicated.
VMS Client Installation Figure 2-40 Setting the User Password 6. Move the new user to the VMS users group. Do this by right-clicking on the user that was just created and opening the Client Properties page shown below in figure 2-41. Open the Member Of tab.
V M S C l i e n t I n s t a l l a t io n 7. Click the Add button. The Select Group dialog will open, as shown in figure 2-42. Ensure that the location is the domain, then enter VMS Users as the object name and click Check Names to verify. Click OK to close the dialog. Figure 2-42 Select Group Dialog 8. Close the Active Directory window. 9. Open up Adminsitrative Tools and select Component Services to open the Component Services window, as shown below in figure 2-43. 10.
VMS Client Installation Figure 2-44 Edit Limits 12. From the Launch Permission dialog, click on the Add button. • Enter VMS Users in the Select Users, Computers, or Groups dialog to add the group to the launch permissions. • Check all of the Allow boxes for VMS Users, as shown in figure 2-45.
V M S C l i e n t I n s t a l l a t io n Figure 2-45 Launch Permissions 13. Click on the OK button to launch the selected permissions and close the dialog. Verifying Successful Client Installation After installation, verify that the VMS Client installation was successful by running the program. The VMS Server must be running VOS. 1. From the Program File directory, find VMS 3.x and click the Connection Manager. 2.
VMS Client Installation 3. The ViperView window will appear, as shown in figure 2-47. Figure 2-47 ViperView window, VMS Client ViperGlobe Install ViperGlobe is a small separate installation and is installed only on a VMS Client workstation that has the necessary supporting video graphic hardware. Located on the VMS install disk, VMS 3.6.x.xxx Globe View Setup will install in the same directory as the VMS Client. Double-click on the Setup file to install the application.
V M S C l i e n t I n s t a l l a t io n Verifying ViperGlobe Installation After installation, and with all Client connections established to the VMS server, launch ViperGlobe: 1. From the Program File directory, find VMS 3.x and click the Vipersat Network Globe shortcut. 2. At the connection prompt, enter the IP address of the Active VMS server and click on the OK button in the Connect To dialog. 3. The Vipersat Map View window will appear, as shown in figure 2-49.
VMS Client Installation VNO Install VNO Overview Comtech EF Data - Vipersat Network Products Group VNO solution provides an interface into a defined subset of the actual network managed by VMS. This is exposed as a Web Services SOAP interface provided by the VNO-WS.exe service. The VNO web service supports both non-redundant stand-alone and redundant VMS deployments. With redundant VMS servers, figure 2-50 depicts the VNO-WS.
V M S C l i e n t I n s t a l l a t io n Installation Procedure The VNO installation process consists of installing software, highlighted in yellow sections in figure 2-50, on the IIS Server and the Client PC. Although the VNO_WS Server can run on the VMS server, it is recommended that it be installed only on the client PC running Viperview. 1. If running, terminate the Viperview.exe and VConMgr.exe applications on the server. Use the Task Manager to end the applications and processes. 2.
VMS Client Installation Figure 2-51 VNO-WS Installer 4. Refresh the Service Control Manager and verify that the VMS VNO WS services entry is displayed in the list of services. 5. Start the VMS VNO service. A single beep will indicate that the service started. Verify that the status has changed to Running. The vno-ws-log.txt log file in the Vipersat\VMS\3.0\Data directory will also show if the service started.
CHAPTER VMS CONFIGURATION General NOTE Note: For a Redundant VMS Server configuration, perform the VMS configuration procedure on the Active server only. When completed, perform a server synchronization to synchronize the server databases. Before proceeding with configuring the network using VMS, the following network information should be available, for reference. • A list of all equipment used in the network, broken down by site. • A schematic or other documentation of the network’s topology.
General • A list of the VMS licensing options that have been purchased. Details can be found on the Purchase Order, or a Vipersat representative can provide detailed information on licensing options and pricing for the VMSmanaged network. • A list of network modem equipment and the FAST features associated with each. This information can be obtained either via Telnet from the Main>Administration>Feature Configuration screen, or with Vload and the use of the Parameter Editor (Features tab).
H a r d w a r e C o n f i g u r a t io n Hardware Configuration NOTE Note: For VMS compatibility, see the product Release Notes for specific versions of each modem supported. Once all of the needed information is obtained, configuration can begin. Before making the physical installation of hardware into a network, each modem/router must be pre-configured using either Telnet (CLI) or HTTP. Refer to the modem/ router’s documentation for details.
H a r d w a r e C o n f i g u r a t i on Once the modem/routers have the minumum required configuration and an installer successfully points the antenna at the satellite and establishes a receive link, the operator at the Hub site can push frequencies, bit rates, and FEC code rates to the units at remote sites using the VMS. The frequencies can be anywhere in the customer’s frequency pool, allowing a thin-route SCPC connection to be established with the satellite network’s modems.
V M S Ne t w o r k C o n f i g u r a t io n VMS Network Configuration This procedure assumes that the user is experienced with the VMS or has attended the System Operator training course, and gives summary instructions for configuring an installed VMS. If difficulties are experienced during configuration, contact Comtech EF Data’s Vipersat CTAC for assistance. Once VMS is installed and started up, the VMS immediately starts gathering and storing information from the units which make up the network.
VMS Network Configuration 3. The Connection Manager will prompt for the server with which to connect (figure 3-3). Enter the IP address of the active VMS Server and click the OK button. Figure 3-3 Connect dialog The ViperView window will open. Activate the Server Processes In ViperView, right-click on the Server icon on the top menu bar and select Activate from the drop-down menu (figure 3-4) to manually initialize the VMS server processes.
V M S Ne t w o r k C o n f i g u r a t io n Configure Auto Activate 1. Right-click on the Server icon and select Properties from the drop-down menu. 2. In the General tab, check the box for Auto Activate as shown in figure 3-6. This will automatically activate the server processes the next time the VOS service is started. Figure 3-6 Server Properties, Auto Activate Configure Addresses and Assign ID 1. Right click on Vipersat Manager from the ViperView tree view list and select Properties.
VMS Network Configuration Figure 3-7 Vipersat Manager, General tab 3. The Local VMS Address will default to 0.0.0.0 on new installations and must be changed to reflect the IP address of the NIC that connects the VMS server to the Vipersat Hub LAN. This address configuration is necessary because of multiple LAN ports on the server. 4. The Base Port sets the starting IP port addressing for all VMS messages.
V M S Ne t w o r k C o n f i g u r a t io n 8. The Force Multicast Port Restart check box provides the option to reset the port used by the VMS server for multicast transmissions. This action is recommended whenever the Local VMS Address or base port setting is changed, especially for servers that have multiple NICs. Activate the check box, then click on the Apply button to execute the restart. 9.
VMS Network Configuration is how long the VMS will wait before determining communications failure commanding a device redundancy switchover. The Debounce is a message count on how long the VMS will receive messages sent from the modem with alarm information set. This value is important to reduce the possible spurious alarm redundancy triggers. 12. The Communications timer values set timeouts for command messages. The Retry Timeout is the wait between messages which works in conjunction with Retry Count.
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-9 Vipersat Manager, Registration tab 16. Select the Monitor & Control radio button if this network is to be managed by this VMS, otherwise select Monitor Only. 17. Click the OK button to save these settings for the Vipersat Manager Properties. VMS Network Build Procedure Subnet Manager Configuration Most of the work here will be done by VMS. The operator needs to verify that each subnet has all of the expected elements populated in the subnet.
VMS Network Configuration Setting the Alarm Masks Network alarms must be set to insure an alarm alerts the operator to an actual problem. If there are spurious alarms, or alarms which have no operational meaning the operator will become desensitized and critical network failures can be missed. This section addresses masking alarms that represent normal network conditions. VMS allows the masking of these nuisance alarms.
V M S Ne t w o r k C o n f i g u r a t io n CDM-570/570L, CDD-56X SLM-5650A Figure 3-10 Mask Unlock Alarm setting Enabling Auto Home State A critical feature of Vipersat Networks is the modem Home State. Since the topology of the network is changing on the fly, it is necessary to ensure that remote units will recover from a communications outage in a known state. If a remote loses power, its home state parameters will cause it to boot up into its burst configuration, awaiting maps from the hub.
VMS Network Configuration 3. Right-click on the unit icon again and select Force Registration. This will force the parameter set in the modem. VMS will then set the parameter every time it registers the unit. CDM-570/570L SLM-5650A Figure 3-11 Auto Home State Timeout setting Bandwidth Manager Configuration Create Satellite(s) The first step is to create the satellite for the network with the appropriate operating frequency information. 1.
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-12 Create Satellite menu command Figure 3-13 Create Satellite dialog 3. After a Refresh command, the newly created satellite will appear under Bandwidth Manager in the ViperView window. 4. Repeat the previous steps to create additional satellites, as required Create Transponders The next step is to create transponders in the newly created satellite. Each transponder is entered with its center frequency and bandwidth.
VMS Network Configuration 1. Right-click on the satellite icon and select Create Transponder from the drop-down menu (figure 3-14). 2. Enter the transponder Name, Center Frequency, and Bandwidth Span in the Create Transponder dialog (figure 3-15). Leave the Pad and Translation Override entries at the default values, if unknown. The Pad value sets the gain variation between transponders for automatic switching power calculations.
V M S Ne t w o r k C o n f i g u r a t io n Create Antennas The following steps cover creation of the network antennas. Each antenna is a site container for upconversion/downconversion and modem devices. First create a Hub antenna, followed by the Remote antennas, as described below. 1. Right-click on the satellite icon and select Create Antenna from the drop- down menu. 2. In the General tab of the Create Antenna dialog (figure 3-16), enter the Name, Operator and Contact Information.
VMS Network Configuration If multiple remotes are involved in a SHOD connection, the VMS uses the lowest remote gain value for compensation control. 4. Select the Visibility tab to configure the Antenna Visibility range, as shown in figure 3-17. Caution: Unless specific limitations are required for the antenna range, the recommended settings are 500 GHz center frequency and 1 THz bandwidth (defaults). Refer to Appendix B, "Antenna Visibility", for more information on this feature.
V M S Ne t w o r k C o n f i g u r a t io n Also, check the Bandwidth and Power Limit settings. If the RF hardware does not exactly match the satellite parameters, the Bandwidth setting may have to be changed. Contact the Vipersat Network Product Group CTAC for further information. Figure 3-18 Create Up Converter dialog 2. Right-click on the Antenna icon again and select Create Down Converter (figure 3-19). Ensure that the frequency settings here are correct.
VMS Network Configuration 3. Notice that the newly created Up and Down Converters appear in the Antenna View (figure 3-20). Figure 3-20 Converter Icons on Antenna View 4. Bind node Modulators and Demodulators to the Up and Down Converters: • Expand the Subnet Manager tree down to the Modulator and Demodulator level for those units that will utilize this Antenna. • Click on the Antenna icon in the left window panel to display the Converters in the Antenna View in the right window panel.
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-21 New Devices Added to Converters 5. Make the Expansion Unit Demodulators available by right-clicking on them in the Antenna View and selecting Allocatable from the drop-down menu. 6. Repeat the previous steps for each Antenna. InBand Manager Configuration A precursor to configuring InBand management is to set the carrier flags. Carrier flags provide carrier type information to the system switching function.
VMS Network Configuration Figure 3-22 BC Carrier Flag Setting, CDM-570/570L Figure 3-23 BC Carrier Flag Setting, SLM-5650A 1. Enable InBand Management on each remote subnet. On nodes which are part of the switched network, right-click on the Subnet icon from the Tree View and select InBand Management, as shown in figure 3-24.
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-24 InBand Settings for Remotes 2. When InBand Management is selected, as shown in figure 3-24, a window will open prompting the operator to select the Modulator for switching from the Name list shown in figure 3-25. Figure 3-25 Select Switching Modulator 3. Select the remote’s modulator, open the Subnet View, as shown in figure 3-26, and refresh the device view to verify that the VMS has picked up the home state.
VMS Network Configuration Figure 3-26 InBanding a Remote 4. Right-click on the Subnet and open the Properties page. The General tab, which opens first, allows the operator to enter a Subnet Name, if desired, and add External Subnets. External Subnets are additional networks beyond the local area network of the modem. If the remote site has a router, and applications you wish to switch on (voice, e.g.) reside on the other side, insert the Subnet Address and Mask here. See figure 3-27, below.
V M S Ne t w o r k C o n f i g u r a t io n If the initial InBand setting failed (did not show the correct Home State in the Subnet view), check to ensure these settings are correct. This tab can be used to change Home State settings for a remote. Enter the desired settings and revert the uplink carrier. Remember to reset the Home State parameters in the modem and save them after doing this. Figure 3-28 Subnet Properties, InBand tab 6.
VMS Network Configuration Figure 3-29 Properties Policy Tab The check boxes have 3 states: Clear — The policy or switch type is not allowed Clear with Check — The policy or switch type is controlled locally Gray with Check — The policy or switch type uses global settings Application Policy Type numbers have the following convention: 1 — Scheduled Switching and VFS 2 — Voice 3 — Video 4-64 — Reserved for the System 65-253 — User Defined 254 — Uninterruptable Switch (used to ensure that additional applicati
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-30 Properties Distribution List tab 8. The Distribution List dialog (figure 3-31) provides a Destination box and a Name box, and allows the operator to select Sites to add to the list. If the destination is left as 0.0.0.0 and the network is in Entry Channel Mode with switch type Load, the effect is to permanently PAMA the links in the list. Figure 3-31 Distribution List dialogs The Satellite Advanced Switching (S.A.S.
VMS Network Configuration tion and FEC Rate, can occur. Note, however, that Turbo mode should never be changed. To configure a roaming remote and different specifications per satellite are required, perform the following steps. Otherwise, proceed to the next section, “Pool Management”. Figure 3-32 S.A.S. tab with SOTM Enabled 9. Right-click in the center of the S.A.S. tab and select Insert to open the Select Object dialog. 10.
V M S Ne t w o r k C o n f i g u r a t io n Pool Management The next step is to set up bandwidth pool(s) in the transponder(s) created earlier. Bandwidth pools are the heart of the switching engine. They are the only portion of the space segment actively controlled by the VMS. 1. Right-click on the satellite in the tree view and select Open (figure 3-33). Figure 3-33 Satellite Open menu command This opens the Spectrum Analyzer / Bandwidth ViperView window (figure 3-34).
VMS Network Configuration Figure 3-35 Create Pool dialog 3. The Center Frequency setting will reflect the Transponder frequency value corresponding to the point where the mouse was clicked to create the pool. Correct this setting to the desired value for this pool, and adjust the Bandwidth to the correct width. Click OK and the new pool will appear (figure 3-36). Figure 3-36 New Bandwidth Pool 4. Repeat the previous steps to create additional bandwidth pools. 5.
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-37 Resize Uplink Carrier, Subnet Returning to the Spectrum View, the blue shaded area represents the slot assigned by the VMS for the switch. Upon receipt of the next PLDM (Path Loss Data Message), a carrier will appear showing the current EbN0 and bandwidth (figure 3-38).
VMS Network Configuration 7. From the Tree View, click on the Hub antenna under the Bandwidth Manager to display the Hub devices in the right window panel. From this view, the operator can see the switched demodulator that the VMS selected, the carrier frequency in L-Band, the bit rate, the current EbN0, and the subnet/subnet mask (figure 3-40).
V M S Ne t w o r k C o n f i g u r a t io n mation received from the antenna ACU. An example of this type of network is depicted in figure 3-41, below. Figure 3-41 Vipersat Network, Global Map View This section describes the procedure for configuring Network Manager in the VMS, and graphically displaying the network using ViperGlobe. 1. From the Tree View, right-click on the Network Manager icon and select Create Network (figure 3-42). 2.
VMS Network Configuration Figure 3-42 Creating the Network 4. Drag and Drop the satellite(s) for this network from the Bandwidth Manager onto the Network icon (figure 3-43). Figure 3-43 Drag and Drop Satellite(s) NOTE Note: References to ViperGlobe in the following steps apply to Client machines that have the optional ViperGlobe application installed. 5. Open the Vipersat Map View window by one of two methods: • Double-click on the Network Map View icon (Desktop Shortcut).
V M S Ne t w o r k C o n f i g u r a t io n • From the Start menu, select Programs then VMS 3.6 followed by Vipersat Network Globe. A Connect dialog will open, prompting for the Server Name. Enter the IP address of the server and click Connect. The Vipersat Map View window will open, displaying the globe (figure 3-44). Figure 3-44 Globe View with Network Icon 6. In the upper right corner of the window, the Vipersat network will appear as an orange icon.
VMS Network Configuration corresponding to the mouse position appear in the upper left corner of the window as a reference. Figure 3-45 Adding Sites, Network Manager and ViperGlobe 7. Execute the Create Site command and enter the Name to be used for the site. In the Tree View, expand the Network to expose the newly created site. 8. Right-click on the Site icon and select Properties. The exact coordinates can be entered in the dialog that opens. 9.
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-46 Map View with Linked Sites In order to have the sites on the Map View indicate alarms, it is also necessary to drag and drop the subnet icons associated with each site into the Network Manager. 11. Drag and drop the associated Subnet from the Subnet Manager onto the Site. 12. Repeat the above Create Site steps to create all desired sites for the Network. Multiple Networks can be created under Network Manager by repeating the above procedure.
VMS Network Configuration switch a terminal to its CIR. Requests for rates above the CIR are granted on a first-come, first-serve, best effort basis. A terminal that does not have an assigned CIR has no guarantee for any bandwidth, and is only granted bandwidth on a purely opportunistic basis. The Basic Guaranteed Bandwidth / CIR function depends on the pre-allocation of system resources, namely RF spectrum and network hardware devices (demodulators).
V M S Ne t w o r k C o n f i g u r a t io n Enable CIR on the Satellite Right-click on the Satellite appearance in the Tree View and select CIR Enabled from the drop-down menu (figure 3-48). Figure 3-48 CIR Enabled Command CIR Policy Setting The CIR assigned to a Remote is equal to the Minimum Bit Rate setting, which is determined by the local Subnet policy setting. Any Remote that has the local policy set to 0 bps (the default) will use the global policy setting as its CIR value.
VMS Network Configuration Figure 3-49 Global CIR Setting The Minimum Bit Rate setting on the Policy tab establishes the global CIR value for the Network. Perform the following steps for all Remotes that will utilize a CIR that is different than the global value. 1. Right-click on the local Subnet appearance for the Remote and select the Properties command. 2. Open the Policy tab and set the Minimum Bit Rate for the Remote (figure 3-50).
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-50 Remote CIR Setting Enable CIR on Remote Antennas 1. Right-click on the Antenna appearance for the desired Remote and enable CIR for either Normal or Priority bandwidth from the drop-down menu (figure 3-51).
VMS Network Configuration Selecting CIR Normal will allow this Remote to access the Low Priority Bandwidth spectrum (see figure 3-47) when attempting to switch above its CIR. Selecting CIR Priority will grant access to the High Priority Bandwidth spectrum for this Remote. 2. Repeat for each Antenna associated with a CIR Remote.
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-53 Satellite CIR tab Because the Remote CIR policies have been configured previously, the available bandwidth for Guaranteed and Normal has been calculated by the VMS and is displayed here. 3. If Priority Bandwidth is required, enter the amount and click on the Apply button. Note that the Normal Bandwidth will be reduced by this amount.
VMS Network Configuration N:M Device Redundancy If device redundancy for hub primary modems is desired, it should be configured at this point. Complete instructions for configuring this feature can be found in Appendix C, "Redundancy". VMS Redundancy If VMS server redundancy is desired, it should be configured at this point. Complete instructions for configuring this feature can be found in Appendix C, "Redundancy".
V M S Ne t w o r k C o n f i g u r a t io n Figure 3-54 SOTM Transitioned Site 1. Open the Vipersat Map View and highlight the Network icon to make the network active. 2. Right-click on a mobile Remote site and open the Properties window (figure 3-55).
VMS Network Configuration Figure 3-55 Enable Dynamic Function for SOTM Remote 3. Check the Dynamic box and select the browse button beneath it. This will open a dialog box in which the subnet should appear (figure 3-56). Note that, if the subnet icon was not copied into the Network Manager site as described in Network Manager Configuration, this box will be empty. Figure 3-56 Selecting ROSS Unit for SOTM 4. Select the Subnet and click OK. This will open up a dialog showing the subnet components. 5.
V M S Ne t w o r k C o n f i g u r a t io n At this point, the Remote site icon will snap to a location on the globe based on the GPS reading that the ROSS is receiving from the antenna. 6. Repeat the above procedure for all mobile remote sites. The next step will be to set up the VMS to push the routes to the TDM outbounds.
VMS Network Configuration Figure 3-57 Dynamic Routing Entry, CDM-570/570L 9. Push the new route to the modem with a Force Registration. The modem will generate a RIPv2 update to the router identified as its default gateway. This can be verified by right-clicking on the modem, selecting Configure, then opening the Routing tab as shown in the figure. 10. Repeat this route procedure for each TDM outbound modem. If Quality of Service rules apply, configure them now.
V M S Ne t w o r k C o n f i g u r a t io n currently active TDM outbound. Configure QOS rules for the remotes that use this modem as their “home” TDM. 11. Right-click on the Hub unit with the first TDM outbound and open the Properties page. 12. Enable QOS Management by checking the box, then click on the Rules button (figure 3-58). Figure 3-58 QOS Rules Configuration, CDM-570/570L 13. Right-click in the QOS Rules window to Insert a rule, then edit the rule settings that will apply to the remote.
VMS Network Configuration This concludes the VMS Network Configuration.
CHAPTER CONFIGURING NETWORK MODEMS General This section describes using VMS to configure Vipersat network modems. Configuration of modem parameter files is accomplished using the Parameter Editor. The Parameter Editor, as used from the VMS, performs the same functions as the Parameter Editor accessed via Vipersat’s VLoad utility. The uses of the Parameter Editor in VMS and VLoad differ, however, in the way the edited parameters are stored and applied.
General Figure 4-1 Modem Equipment Drop-Down Menu, ViperView • Open – This item causes the selected modem/router to pop open a separate window displaying the device parameters for the unit. • Soft Reset – This command causes the selected modem/router to perform a refresh of all latched alarms, clearing all internal table entries. • Firm Reset – This command overwrites active memory in the modem/ router with the contents of the unit’s flash memory and executes it.
General Hardware Configuration Refer to the user documentation for each modem/router in the satellite network for details on the physical installation of the device. The hardware documentation also has detailed information on using either the unit’s front panel controls or a Telnet connection and the command line interface for directly configuring the target modem/router.
C o nf i g ur i n g a N e t w o r k M o d e m Configuring a Network Modem A modem/router, when controlled by the VMS as part of a communications network, has its performance automatically controlled as VMS monitors the modem/router’s role and performance in the network. VMS then commands the modem to modify its configuration, as needed, to optimize network performance. In addition, the modem portion of each modem/router in a network can be controlled manually.
CHAPTER VMS SERVICES General This section covers using the various Services that make up the VMS, a satellite network management system with an intuitive, user-friendly, graphical user interface which displays: • Continuously updated network health and status information • Multiple networks managed from a single server • Centralized network configurations • Organized network layouts • Automated equipment detection • Large network management with intuitive drag-and-drop bandwidth management and configuratio
ViperView—Monitor and Control ViperView—Monitor and Control ViperView and the VMS Services function to monitor and control network operations as well as to provide an interface for the administrator/operator to manage and perform modifications to the network. Caution: In a redundant VMS configuration, when any changes are made to the VMS database, a Synchronize command should be executed (available by right-clicking on the Servers icon, as shown in figure 5-1).
ViperView—Monitor and Control Figure 5-2 ViperView, Multiple Window Views For example, the Subnet Manager View shown in figure 5-3 can be opened to display the current switch status, bit-rate, and RF frequency of all network remotes. Figure 5-3 Subnet Manager View Similarly, the Antenna View displays the current status of a site’s Modulators and Demodulators, as shown for the Hub site in figure 5-4.
ViperView—Monitor and Control Figure 5-4 Antenna View NOTE Note: The Antenna View shows L-Band frequencies. Use the Event Log to stay current on recent network activity, as shown in the Event View window shown in figure 5-5. Figure 5-5 Event View The Event View lists the details of network configuration changes, alarms, and switch events. The Spectrum View displays a simulated spectrum analyzer, shown in figure 5-6, letting the operator monitor carriers and pools.
ViperView—Monitor and Control Figure 5-6 Spectrum View The Parameter View, shown in figure 5-7, constantly supplies the operator with updated information for a selected unit.
ViperView—Monitor and Control • Unit Ethernet Right-clicking on a unit icon in the tree view displays the drop-down menu shown in figure 5-8. Use the commands from this menu to: • Open a separate window for the unit’s operating parameters • Perform Soft, Firm and Hard Resets • Save to Flash • Force Registration • Remove • Manipulate router parameters with the Configure and Properties commands.
ViperView—Monitor and Control Green is used, as shown in figure 5-9, to show which sites, links, and equipment which are operating normally. Red, on both the map and for entries in the menu tree to the left of the map, indicates that there is an alarm condition. Gray indicates that no status multicast (PLDM) being received. Tip: The red error condition indicator indicates that at least one of the devices in a site is reporting an alarm condition for a link.
ViperView—Monitor and Control Figure 5-10 Drop-down menu Right-clicking on the Modulator and selecting Properties opens the tabbed dialog shown in figure 5-11.
ViperView—Monitor and Control The General tab displays the current name assigned to the modulator and allows renaming, if required. Clicking the Modem tab (CDM only) displays the dialog shown in figure 5-12. This tab allows setting the Flags and the Carrier Type for the device. Figure 5-12 Modem tab, CDM modulator and Demodulator only These same settings also appear in the Demodulator Properties window for both the CDM-570/570L and CDD-56X.
ViperView—Monitor and Control Figure 5-13 Event Log View Each log entry is displayed using the standard VMS color scheme: • Green – the logged item was completed successfully • Red – The logged item failed and caused an alarm • Grey – The unit was not available • White – Items which do not have a status associated with them • Yellow – Command • Blue – Configuration change • Purple – Corrupted entry Clicking on the Event View icon on the Object Bar, as shown in figure 5-13, displays a drop-down menu with f
ViperView—Monitor and Control Clear Selecting Clear from the menu deletes all previously recorded events from the log. Twelve Hour Selecting the Twelve Hour clock setting will toggle between 12 or 24 hour event time stamping. Filters... Selecting the Filters... command from the menu opens the Event Log View dialog shown in figure 5-15. Here, the log entries appearance can be tailored to display either a particular type of event and/or a specified date range.
ViperView—Monitor and Control Figure 5-16 Event Log Filter Selection Note: Currently, there is a set of predefined filters available for the Event Log. As additional filters become available, they can be added to the VMS program through an installer utility. Clicking the Finish button adds the selected object type to the Event Log View Filters tab. Multiple filters can be inserted.
ViperView—Monitor and Control Figure 5-17 Event Log Dates tab The parameters entered on the Filters and Dates tabs work together to provide customized Event Views of network activity. NOTE Note: A billing translation program is available in the VMS for processing the event log to extract billing information. This program, described in Appendix H, "VMS Billing Log Translator (VBLT)", filters entries in the event log into a format which can be used for billing purposes.
ViperView—Monitor and Control Viewing/Setting Alarm Masks Demodulators that are typically being locked and unlocked, such as switched demodulators/burst controllers, should have the Unlock Alarm masked. The setting of other alarm masks will depend on usage and whether or not a BUC is installed. Alarms masks are viewed and set for the modem in the device view, as shown in figure 5-18 and figure 5-19.
ViperView—Monitor and Control Table 5-2 Alarm Masking in a Typical Network Device Type TDM/ Burst Cont. Remote Hub Expansion Remote Expansion Demodulator Lock Status Demodulator Level Alarm Demodulator Auto Gain Ctrl X X X X X X X X X Unlock Alarm Masks InBand modem device Mask Unlock Alarm flags mask and set park states every time the modem registers with the VMS. These flags simplify and reduce the device item-by-item settings, making them persistent during active state.
ViperView—Monitor and Control CDM-570/570L, CDD-56X SLM-5650A Figure 5-20 Mask Unlock Alarm Flag 5-16 V M S U s e r G u id e
VMS Service Managers VMS Service Managers When VMS is started on the server and ViperView is opened on the client workstation, the Server View, shown in figure 5-21, displays the installed VMS Services. Included in this display are the Network Manager, the InBand Manager, the Out-of-Band Manager, the Subnet Manager, the Bandwidth Manager (replaces the Upstream Manager in previous versions), the SNMP Modem Manager, the Redundancy Manager, the Out-of-Band Circuit Manager, and the Vipersat Manager.
VMS Service Managers Figure 5-22 Vipersat Manager Network View The health status of each unit in the Network View is indicated by the unit’s status color and the supporting text. InBand Manager Right-clicking on the InBand Manager icon displays the Properties command, shown in figure 5-23.
VMS Service Managers Figure 5-23 InBand Manager Properties Command Selecting the Properties command displays the InBand Manager window shown in figure 5-24.
VMS Service Managers Policy Tab From the InBand Manager Policy tab you can set the global policies under which switching will occur in the Vipersat network. These policy settings are set globally for all networks and are propagated down to all remotes in the system. Independently each remote’s policy will inherent the global policies, but the operator may choose the break the inherent settings and configure each site independently.
VMS Service Managers Figure 5-25 Application Policy dialog Using this dialog, you can establish policy parameters for Type and Bitrate (Maximum and Minimum). Type Enter the type of circuit here.
VMS Service Managers Figure 5-26 Revised Policy Tab Application policies can be modified by directly clicking on them and editing the parameters. To remove a policy, right-click on the policy and select Remove from the pull-down menu. A confirmation is required to execute this command.
VMS Service Managers Figure 5-28 InBand Manager, Distribution Lists tab 1. Right-click in the blank area of the Distribution Lists box to display the Insert command for inserting a new list. Right-click on an existing list to display a choice to Insert a new list, Modify the existing list, or Remove the existing list. Figure 5-29 Distribution Lists, Insert Command 2. Choose Insert to open the Distribution List window shown in figure 5-30.
VMS Service Managers Figure 5-30 Distribution List Window 3. Enter the desired Destination IP address. Typically, this will be a unique multicast address for a specific remote or remotes utilizing the same application. Note, however, that the destination address does not have to be a valid IP address; it can be a non-valid IP address that is used exclusively for a distribution list, for example. 4. Enter the Name for identifying this distribution list. 5. Click on the Add Site button.
VMS Service Managers Figure 5-32 Add Site Dialog, Select Subnet 7. Repeat this process until all of the desired subnets have been added to the list. Figure 5-33 Distribution List Window, Configured 8. Click on the OK button to insert this list in the Distribution Lists tab. Figure 5-34 Distribution List Created 9. The new list can be enabled or disabled by clicking in the check box.
VMS Service Managers InBand management allows Application Policies and Distribution Lists to be selected on a remote site-level basis and allows the system operator to enable and disable mesh and upstream switching or use policies/lists for selected remotes that differ from the global policies/lists. These site-level policies and lists are established using the Subnet Manager. Subnet Manager The Subnet Manager provides a tree view from which the operator can drill down to investigate alarms.
VMS Service Managers Figure 5-36 Separate window NOTE Note: The same information is displayed in both the right-panel display in figure 5-35 and the separate window display shown in figure 5-36. Both of these displays are continually updated by VMS as new data is received from the network. Clicking on an individual subnet displays all of the units associated with the subnet with their Status, Alarm State, current device State, unit Type and IP Address information displayed as shown in figure 5-37.
VMS Service Managers Subnet Manager Configuration Right clicking on an individual subnet displays a drop-down menu, as shown in figure 5-38, allowing the operator to: • Open • Soft Reset • InBand Management • Resize Uplink Carrier • Revert Uplink Carrier • Reset Uplink Carrier • Delete • Properties Figure 5-38 Subnet Manager configuration Open Clicking the Open command creates an independent window with the data shown in the right portion of the screen in figure 5-38.
VMS Service Managers Figure 5-39 Subnet Mananger open command window The independent window can be placed anywhere on the screen and is constantly updated by VMS as new information is received from the network. InBand Management Selecting the InBand Management command shown in figure 5-38 brings up the Select Modem dialog shown in figure 5-40.
VMS Service Managers Figure 5-41 Disable in-band extension warning Clicking the Yes button will disable in-band extension and you will lose the home state and policy settings set when In-Band Extensions were enabled. Soft Reset Selecting the Soft Reset command from the drop-down menu causes an immediate soft reset of the selected unit. Resize Uplink Carrier Selecting the Resize Uplink Carrier command from the drop-down menu in figure 5-38 displays the dialog shown in figure 5-42.
VMS Service Managers Using this dialog you can change the FEC and Modulation characteristics of the uplink SCPC carrier when manually switched. Revert Uplink Carrier The Revert Uplink Carrier command returns the remote modem to its home state settings. This command is appropriate to use when SCPC transmission is no longer required, switching back to STDMA mode, or communications with the remote have been lost and it is unknown whether or not the modem is still transmitting.
VMS Service Managers Caution: Read the Reset Uplink warning carefully, as performing this operation on a unknown transmitting unit may cause carrier interference on operating network. It is safe to reset resources for a remote if it is known that the remote is not transmitting, powered down or faulty. Delete Click the Delete command will delete the subnet from the network, Properties The Subnet Properties page tabs are described below.
VMS Service Managers Figure 5-47 New subnet dialog • Modify - Selecting an existing subnet from the External Subnet listing then clicking the Modify button brings up the New Subnet dialog displayed in figure 5-47. The existing subnet IP address and subnet mask will be displayed. Make the modifications required in this dialog then click the OK button to make the changes.
VMS Service Managers Figure 5-48 In Band Tab, Subnet Properties Clicking on the Extra tab displays the Modem Extra dialog shown in figure 5-49, allowing the operator to set the type of Modulation, FEC Rate, and Code Type for the unit’s home state. Figure 5-49 Modem Extra dialog These settings can be modified by clicking on the desired parameter and choosing a new setting from the pull-down menu that appears.
VMS Service Managers Figure 5-50 Modify, Modem Extra NOTE Note: During initial unit registration the set information in the modem is propagated to the VMS database which fills in the Home State values. The In Band tab also identifies the switching Modulator (the remote data modulator) for the subnet, Downlink Modulator is the hub forwarding (outbound) TDM modulator to remote (used for Roaming applications) and the Uplink Demodulator is the Home State hub demodulator (typically is the STDMA demodulator).
VMS Service Managers Figure 5-52 Select demodulator dialog. Using this dialog you can select a different demodulator for the subnet to replace the existing demodulator. Clicking the OK button will change the selection. NOTE Note: Home State Demodulators are associated and linked by transmission settings, frequency, data rate, modulation and FEC rate. If changing system selected unit to another will require manual tuning and realignment of remote unit configurations.
VMS Service Managers Figure 5-53 Policy Tab, Subnet Selecting an existing application policy, as shown in figure 5-53, and then clicking directly on one of the parameters allows you to modify the policy for the selected policy type. However, an existing policy cannot be removed from the Subnet site level; an application policy can only be removed from the InBand Manager global level.
VMS Service Managers Figure 5-54 Distribution Lists Tab, Subnet The enable/disable check boxes for the existing lists are greyed and checked, indicating that global settings are in effect. At the subnet level, these lists can be altered by clicking on the box until the desired state for that list is displayed: • Click once to uncheck (disable) the list for this subnet. • Click twice to check white box for list to be modified for this subnet.
VMS Service Managers Figure 5-56 Modify Site List In this example, the Modify command is selected, opening the Distribution List window shown in figure 5-57. Figure 5-57 Distribution List Window, Site Modification Here, the list can be modified by adding and/or removing sites from the list. To add a site, click on the Add Site button and follow the procedure outlined in section “Distribution Lists Tab” on page 5-22. To remove a site, select the desired site and click on the Remove Site button.
ViperView ViperView When VMS ViperView starts, the top view displays the installed services as shown in figure 5-58. Each of these services is discussed in the following sections. Figure 5-58 ViperView top view • Vipersat Manager • Subnet Manager • SNPM Modem Manager • Bandwidth Manager • InBand Manager • Network Manager.
ViperView { This Page is Intentionally Blank } C h ap t e r 5 - V M S S e r v i c e s 5-41
ViperView 5-42 V M S U s e r G u id e
CHAPTER OUT-OF-BAND UNITS General This chapter describes integrating out-of-band units into a VMS-controlled satellite network. Controlling Non-IP Modems Before VMS can communicate with a non-IP capable modem, the modem must have an IP-addressable unit, such as the Comtech CiM-25/600 or CiM-25/600L attached and assigned a valid IP address using procedures described in the appropriate product documentation, and described in the following procedure.
General NOTE Note: The CiM-25 must be plugged into an operating modem (except during setup) in order for it to operate reliably. A CiM-25 operating disconnected from a modem will exhibit erratic ethernet communications. Refer to the CiM-25 manual for additional information. SNMP Manager The SNMP Modem Manager is the controlling service for all out-of-band modems.
General The percent of allocation applied to carriers when switched by VMS. The default is 35% allowing for an allocation factor of 1.35. NOTE Note: Currently this carrier guardband setting for OOB is separate from the inband setting under the Vipersat Manager and must be set to the same value. The following procedure demonstrates using the SNMP Manager using a CDM-600L as an example. 1. From ViperView, right-click on the SNMP Manager to display the drop- down menu shown in figure 6-2.
General Figure 6-4 New SNMP modem dialog 5. The unit will now appear listed in the SNMP Modem Manager. Right click on the added unit and select Properties from the drop down menu to display the General tab shown in figure 6-5. a. Assign a name to the CDM-600L in the top dialog box for reference. b. The IP Address box is a read-only display of the IP address of the target CDM-600L. Add the Subnet Mask in the provided dialog c. Insure the SNMP settings are correct.
General Figure 6-6 SNMP Modem Manager Parameter View The Parameter View display shown in figure 6-7, displays unit information and options available for the unit selected in the SNMP Modem Manager. The following discussion shows the type of information available, but you should refer to each unit’s documentation for detailed information on setting or changing any of the parameters listed here.
General Figure 6-7 Parameter View Before continuing with this process, you should click the Refresh button on the drop-down menu shown in. This will ensure that you have the most current information available for the unit before continuing. The information available in the Parameter View contains both information you can edit and information which is hard-coded in the unit which cannot be changed. This can be useful for out-of-band units allowing you to modify their configuration using the VMS.
Configuring the RF Chain Configuring the RF Chain The following procedure shows how to configure the SNMP Modem’s RF chain and enable it for switching. 1. Expand the modem icon to show the Modulator and Demodulator. Select the appropriate antenna and expand the up and down converters as shown in figure 6-8 below: Figure 6-8 Configuring the RF Chain 2. Drag and drop the modulator on to the up converter and the demodulator to the down converter. 3.
C o nf i g ur i n g t h e R F C h a i n Figure 6-9 Out of Band Antenna Tab 4. Highlight the Modulator for the new SNMP modem and click Enable as shown in figure 6-10 below: Figure 6-10 Selecting the Out of Band Modem 5. A dialog box will open prompting for a bit rate and power.
Configuring the RF Chain switch to. Set them to a combination that will give an appropriate level. The dialog box is shown in figure 6-11. These two values set the base levels from which all SCPC switched modifications are referenced for this unit. Example, if the set power of -28dBm was calibrated to represent a satellite link of 10dB Eb/No and the VMS modified (switched) the carrier bit rate from 256k to 512k the modulators power would change from -28dBm to -25dBm respectively.
S w i t c h i ng S N M P O u t o f B a n d M o d e m s Switching SNMP Out of Band Modems Overview SNMP controlled modems are defined as Out-of-Band in the VMS. This means the traffic interface for these modems is not part of the IP infrastructure the Vipersat Network belongs to. SNMP modems use either a serial traffic interface such as V.35 or G.
S w it c h i n g S N M P O u t o f B a n d M o d e m s Configuring the OBCM If the steps above for configuring the RF chain have been completed the following procedure can be used to configure the OBCM. This also assumes that each of the OOB units have been correctly declared and associated with there proper antenna components. 1. Open the Out of Band Circuit Manager by left clicking on the icon in the tree view as illustrated in figure 6-13. Figure 6-13 Out of Band Circuit Manager 2.
S w i t c h i ng S N M P O u t o f B a n d M o d e m s • • • • • IP address of the first modem IP address of the second modem A channel bit rate The channel priority (will be used in future release) The Group number (used in conjunction with the channel priority. 4. Once the channel is configured it will be possible to manually switch it. Right click on the channel and select “Setup” from the drop down menu.
S w it c h i n g S N M P O u t o f B a n d M o d e m s remote modem right clicking on the hub modem will allow the operator to free up the bandwidth resources by selecting Reset. Unless you are certain the remote modem is no longer transmitting do not free up its resources as it will then act as a foreign carrier in the network. Figure 6-17 7.
S w i t c h i ng S N M P O u t o f B a n d M o d e m s Vipersat Circuit Scheduler Another way of switching SNMP Out-of-Band modems is with the Vipersat Circuit Scheduler. If you have purchased this option see the manual for instructions on scheduling Out of Band switches. You will still need to follow the instructions above through Configuring the RF chain for the VCS to work.
APPENDIX VMS CROSS BANDING The VMS has the capability to accommodate applications involving satellite cross strapping and cross banding. The VMS is able to recognize, manage, and control satellite circuits which utilize more than one frequency. The typical satellite bands currently in use include: • C-Band • Downlink 3.7 to 4.2GHz • Uplink 5.9 to 6.4GHz • 24 36MHz transponders • Ku Band • Downlink 11.7 to 12.2 GHz • Uplink 14.0 to 14.
• The satellite has mapped the transponder from one antenna to a transponder on another antenna. • The satellite serves as an RF inter-band relay which is also referred to as cross strapping In the example shown in figure A-1 the C-band and Ku-band transponders 20 through 24 are cross banded.
Vipersat Cross Banding Solution Figure A-2 illustrates a schematic representation of a cross banded satellite network.
Figure A-3 VMS Cross Banded Network Configuration In response to the network configuration shown in figure A-3 the VMS would: 1. Create Satellite - Set center frequency to 6.1375GHz and translation frequency to 2.225GHz 2. Create Transponder 4C (cross banded to Ku) - 6.005GHz, 36MHz 3. Perform a Translation Override = (6.005 – 11.78) = -5.775GHz 4. Create Pool, 3MHz at 6.020GHz 5. Create Transponder 12C - 6.165GHz, 36MHz 6. Create Pool 4, 2MHz at 6.166GHz 7. Create Transponder 4Ku - 14.155GHz, 36MHz 8.
Figure A-4 illustrates the results of the VMS solution for managing and controlling the cross banded network described above. Figure A-4 VMS Cross Banded Network Solution The VMS calculated Translation Override Frequency (TOF) is an integer value in Hertz that represents frequency offset of the cross banded transponders, mapping the modulator frequency to the demodulator frequency.
Figure A-5 Transponder dialog, C to Ku Figure A-6 Transponder dialog, Ku to C To create a new transponder, right-click on the Satellite icon and choose Create Transponder from the pull-down menu that appears. On existing networks, right-click in the black portion of the satellite spectrum view, choose Properties, and the transponder window will open displaying the current settings. Alternatively, edits can be performed by displaying the antenna and transponder list.
APPENDIX ANTENNA VISIBILITY General Antenna Visibility is a powerful tool in the VMS that allows an operator to control the spectrum used by the VMS switching engine. Simply stated, it allows the operator on a site by site basis to block portions of the satellite or transponder bandwidth from being used by the bandwidth manager, even if a defined bandwidth pool exists within the blocked portion. Antenna visibility can be used in a variety of ways.
Using Antenna Visibility Using Antenna Visibility Antenna Visibility is accessed by right-clicking on the desired satellite antenna and selecting Properties. The antenna properties window will open. Click on the Visibility tab to display the antenna visibility window. The figure below shows the antenna visibility flag as defaulted by the VMS. The default values ensure that the entire spectrum is available so that there are no limitations in effect when this feature is not used.
U s i n g A n t e n n a V i s i b i li t y Figure B-2 Ku-band Visibility Ranges, Center/Bandwidth The frequencies can be viewed, as above, with a center frequency and bandwidth, or as shown below with frequency ranges. Clicking in the View as Base/ Top box will toggle between these two views. Figure B-3 Ku-band Visibility Ranges, Base/Top The Add and Subtract buttons are used to modify the visibility by either adding or subtracting frequency ranges to/from the antenna.
Using Antenna Visibility bility tab, showing either a center frequency with bandwidth, or a base frequency and top frequency. This appearance can be toggled using the View as Base/Top check box. Figure B-4 Frequency Range dialogs Enter the range of bandwidth to be added or subtracted and select OK. Subtracting a frequency range from within visible bandwidth creates a visibility block, or mask, for that portion of the spectrum.
U s i n g A n t e n n a V i s i b i li t y Example — Blocking Spectrum Affected by Local Ground Frequency Interference In the example shown here, Antenna Visibility is used to block off a portion of a bandwidth pool at a given remote site due to ground interference on the lower part of the transponder spectrum. In this case, assume there is ground interference on the lower end of the transponder that overlaps into the bandwidth pool, as illustrated in the figure below.
Using Antenna Visibility Using the visibility Subtract function, a new block for this area of interference can be created for the remote antenna, as shown in the figure below. Figure B-8 Visibility Subtract dialog The revised visibility map now shows a visibility block between 12.1245GHz and 12.1255GHz which represents the bottom 1MHz portion of the pool experiencing ground interference.
U s i n g A n t e n n a V i s i b i li t y This configuration results in the VMS switching as shown below. The receive carrier for the remote is now outside of the area of interference.
Using Antenna Visibility { This Page is Intentionally Blank } B-8 V M S U s e r G u id e
APPENDIX REDUNDANCY General This appendix describes the optional redundancy services that protect critical Vipersat network equipment. The two main services offered are VMS Redundancy and Hub Modem Redundancy. VMS Redundancy provides for N:1 redundant VMS server(s) (standby) colocated at the Hub alongside the active VMS server. This configuration provides for the automatic switch-over to a standby server in the event of a failure of the active server.
VMS Redundancy VMS Redundancy Description VMS redundancy (protection) increases the system availability of a Vipersatenabled network by protecting the network from a VMS server failure. In the current release, N:1 redundancy is a monitored hot-standby configuration with N+1 VMS servers running in parallel.
VMS Redundancy NOTE Note: It is recommended that all servers be co-located at the same site and be connected to the same Ethernet LAN. The monitoring workstation should also be co-located. This is to eliminate reliability issues that may be associated with the terrestrial data-link communications between a geographically remote server and NOC units. A data-link failure may result in contention of automatic switch-over control and interruption of restoral processing.
VMS Redundancy Active Server Role The active VMS server has the following specific privileges that differ from a standby server: • There can be only one (1) VMS server actively managing the network. • The active server is considered the default VMS server for configuration and network topology purposes. • The active server's database is considered the master copy.
VMS Redundancy Automatic Synchronization As the name implies, automatic synchronization occurs automatically by the active VMS and is performed whenever any changes occur that are associated with automatic system functions, such as automatic switching, device redundancy, etc. The active server maintains a memory cache that holds the updates until they can be pushed out to the standby servers by an automatic synchronization that occurs during the VMS heartbeat.
VMS Redundancy ing server contention, refer to the section “Clearing Server Contention” on page C-12. Server Status The VMS Connection Manager provides the status of the VMS and each of the servers in a redundancy group. The Connection Manager, when running, will display its icon in the Windows Task bar at the bottom right of the screen. When the mouse is positioned over this icon, a status pop-up appears displaying information on the VMS and the servers, as shown in figure C-2, below.
VMS Redundancy • A common domain for the redundant servers and the client workstation. Refer to Appendix D, “Domain Controller and DNS”, in this document for details for establishing the VMS server as a domain server. Starting a redundant VMS configuration requires bringing up the VMS servers and the workstation using the following procedure: 1. Install VMS on each of the servers following the instruction in Chapter 2, “VMS Installation”. 2. Start the Vipersat Management System service and ViperView.
VMS Redundancy 3. From the VMS Server drop-down menu, select the Properties command to display the VMS Server (VIPERLAB1 in this example) dialog window shown in figure C-4. Figure C-4 VMS Server Properties, General Tab 4. Configure the redundancy settings for this server. The General tab provides redundancy information on the server role and local status, and current server redundancy settings which can be edited as required.
VMS Redundancy • with Auto Activate de-selected, a server will be activated only by an operator manually issuing an Activate command on one of the servers. When choosing to use Auto Activate, each VMS server in the redundant group should be configured with the Auto Activate function selected. Redundant Servers The Redundant Servers box lists, by IP address, the other VMS servers that are in the redundancy group with this server.
VMS Redundancy Click the Traps tab, shown in figure C-5, to display the existing SNMP Manager traps. Use the Insert, Modify, and Remove buttons to add new traps and modify or remove existing traps. Refer to Appendix E, “SNMP Traps”, for detailed information on the SNMP Manager. 6. When finished, click the OK button to save the server properties settings. Figure C-5 VMS Server Properties, Traps Tab 7. Repeat steps 2 through 5 for each VMS server in the redundancy group. 8.
VMS Redundancy Figure C-6 Activate Command, VMS Server Menu 9. From the Active VMS server, select the Synchronize command from the Server drop-down menu to force the Standby server(s) to synchronize with the current status of the Active server. This manual synchronization command must be executed whenever a Standby server is started or comes back into the group, as well as whenever any database changes are made to a unit. A synchronization can only be executed from the Active server.
VMS Redundancy • The next step is to configure the VMS database for the satellite network on the Active server. Refer to Chapter 3, “VMS Configuration”, for details on this procedure. • Once the VMS configuration is completed on the Active server, perform a server synchronization to synch the Standby server database(s) with the Active server database. Manual Switching Manual switching can be used to designate a different server to be the active VMS server in the redundancy group. 1.
N:M Hub Modem Redundancy N:M Hub Modem Redundancy Description The N:M Hub Modem Redundancy service provides for the protection of critical VMS network modems operating in Hub mode and enhances overall network reliability. The N:M redundancy in VMS version 3.
N:M Hub Modem Redundancy Network Controlled AC Power Bus V MS Primary Parameter List Watchdog OK Status Fault Primary Units SNMP IP RF Combiner/Splitter OK ETHERNET Poller AC Power Control N Spares Parameter Copy N to N Redundancy Process Spares Backup Figure C-8 N:M redundancy logic diagram The switching control mechanism is completely monitored and controlled by the host master processing VMS as shown in the logic diagram in figure C-8.
N:M Hub Modem Redundancy The spare unit is selected in order of IP address. If the spare unit fails to respond or process, it is marked as unavailable by VMS and the VMS repeats the process by selecting the next available unit in the list. Also, as part of the copy command, a separate message is sent to the IP remote controlled AC power bus removing power to the primary failed unit, shutting it down.
N:M Hub Modem Redundancy • The VMS, managed power strip, and hub modems must be on the same LAN segment • All modems must share the same RF infrastructure, such as combiners and splitters Once devices have been installed in the satellite network as described in the section “Installing N:M Redundancy” on page C-15, a group of identical, active, primary devices functioning in the satellite network under VMS control and another group of N devices, identical to the active devices in a spare device pool are cre
N:M Hub Modem Redundancy Figure C-9 N:M block diagram Sample installation Figure C-10 shows a diagram of a sample installation of an N:M redundant VMS installation. As shown in figure C-10, the units in the primary and secondary groups share a common Ethernet LAN with the IP controlled power switch.
N:M Hub Modem Redundancy SNMP IP Input Current Serial Ethernet IP Network Controlled A/C Power Strip International Model 230 VAC, 50/60 Hz CVNI P/N: PWRTWR-H-INTL-16 VMS ETHERNET Modem-to-Power Tower Cord CVNI P/N 22220 Primary Units Power Tower to A/C Mains Cord CVNI P/N 22223 Europe N Spares Power Tower to A/C Mains Cord CVNI P/N 22224 United Kingdom Power Tower to A/C Mains Cord CVNI P/N 22225 Australia Spares Backup Figure C-10 Typical N:M redundant installation The URL http://www.servertech.
N:M Hub Modem Redundancy Setting up N:M redundancy There are 3 hierarchal objects in N:M Redundancy, as shown in figure C-11. They are: 1. Redundancy Manager 2. Containers 3. Power Strips and Groups Figure C-11 N:M Redundancy Hierarchy Expanding the Redundancy Manager icon, shown in figure C-12, shows a typical N:M redundancy installation. Under the Redundancy Manager service icon are the icons for a container named Hub, in this example.
N:M Hub Modem Redundancy Redundancy Manager The Device Redundancy Manager is loaded as a service in ViperView. By rightclicking on it, as shown in figure C-13, the operator can enable device redundancy, create the main container for the site, and backup or restore the redundancy service. Figure C-13 Redundancy Manager Drop-Down Menu Create Container Selecting Create Container from the drop-down menu in figure C-13, brings up the Create New Redundancy Group dialog shown in figure C-14.
N:M Hub Modem Redundancy Figure C-15 Group drop-down menu Once the container is created, right-clicking on its icon brings up the drop-down menu shown in figure C-16. Figure C-16 Group drop-down menu Power Strips Selecting Create Strip from the drop-down menu shown in figure C-16, displays the New Power Strip dialog shown in figure C-17.
N:M Hub Modem Redundancy Figure C-17 New power strip dialog The operator can name the strip (such as reference to a specific rack), enter the IP address, and select the type using the dialog in figure C-17. At this time VMS supports the Sentry 3 and 1 model of APC power strips. Vipersat recommends the Sentry 3. Leave the read and write communities public and private. It will then be necessary to populate the strip with the primary and backup units.
N:M Hub Modem Redundancy Figure C-19 Create Group dialog Once the group is created, drag the port to the group sub-container as shown in figure C-20. Group sub-containers can have entries from multiple strips. Figure C-20 Dragging port to group sub-container Enabling Heartbeats Next, enable heartbeats in the VMS and the devices. From the Subnet Manager, right-click on the desired device and open the properties page shown in figure C-21. Check the Enable Heart Beat box.
N:M Hub Modem Redundancy Figure C-21 Enable hearbeat in VMS, left window CDM-570/570L, right window SLM5650A Right-click on the device again from the drop-down menu select Configure. On the Features tab, shown in figure C-22, check the Primary Heartbeat box. Click the OK button to continue. Figure C-22 Enabling heatbeat in CDM-570/570L modem Force registration on the device. On the next PLDM the Status in the group window should turn green and change to OK.
N:M Hub Modem Redundancy Hub SLM-5650A Modem Connect to the hub modem using Web interface, select the Vipersat page as shown on figure C-23 to enable HeartBeat messaging. Figure C-23 Enabling HeartBeat in SLM-5650A Hub modem Roles Once the group sub-container is populated and heartbeats are enabled, roles can be defined for each of the ports by right-clicking on the device and selecting the appropriate role from the drop-down menu shown in figure C-33.
N:M Hub Modem Redundancy There are four possible status indications: 1. Ok – Hearbeats are enabled in both VMS and the device, are being received by VMS and have no fault indications. 2. Unknown – Heartbeats are not enabled in VMS. May be enabled or not in the device. 3. Faulted – Hearbeats are enabled in VMS but not in the device or heartbeats are being received with a fault indication (non-zero status). 4. N/A – The port is not in use. VMS will select only appropriate units from the list of backups.
N:M Hub Modem Redundancy Should the operator desire to return to the original rack profile the following steps are mandatory and will require a system/segment outage! Pre-Configuring Backup Files The files created in the preceding step are used by VMS for automatic redundancy and are not available to the operator for restoring device units to their original role. It will be necessary to create these files so they will be available for this purpose.
N:M Hub Modem Redundancy Figure C-27 New configuration dialog Give the configuration file an appropriate name in the New Configuration dialog in figure C-27 and click the OK button. Then highlight the file name as shown in figure C-28 and click the Backup button. Figure C-28 Creating a backup configuration file. By default the file will be saved in the location shown in figure C-29.
N:M Hub Modem Redundancy Figure C-29 Saved file location Storing Spare Configurations in the Primary Units Once these backup files have been created, it is necessary to add all possible spare units to the Configurations tab for each of the primary units. This is done by creating a new configuration file name, highlighting it, then clicking the Import button as shown in figure C-30 and importing the file from the directory shown in figure C-31.
N:M Hub Modem Redundancy Figure C-30 Importing file Select the appropriate file from the list: Figure C-31 Selecting file Preparing the repaired/replacement unit Pre-configure the repaired/replacement unit with the configuration of the primary unit being replaced. This step should be performed on a separate LAN segment from the satellite network to avoid conflicts. Vipersat strongly recommends using VLOAD to maintain backups of all network units. These backup files can be used for this purpose.
N:M Hub Modem Redundancy Install the replacement unit in the desired rack location and make all connections. The unit should be powered on, but insure the switch port is powered off. Restoring the acting primary unit spare configuration Since the backup unit assumed the identity of the failed primary unit during restoration, it will appear in the Subnet Manager as the original unit. Right-click on the unit and open the Properties page.
N:M Hub Modem Redundancy How N:M Redundancy Works In the event of failure of any active device, a unit from the spare device pool is configured with the configuration of the failed device, including its IP address, and re-initialized without a hard reset. VMS switches off power to the failed device immediately after detecting failure to ensure the failed device will not conflict with its replacement device when the replacement device is booted into service.
N:M Hub Modem Redundancy 2. When an event is detected that requires a redundancy switch, VMS sends a notification event to the VMS Log service. 3. VMS sends notification to the Redundancy Manager that a switch-over is required. Redundancy Manager The Redundancy Manager receives the switch-over request from VMS which starts the following process: 1. The Redundancy Manager checks that the VMS notification is a for a valid switch condition.
N:M Hub Modem Redundancy Caution: A repaired failed unit will have the same IP address and function as its replacement unit which is currently online. Use the following procedure when returning the unit back into service as a backup. To avoid conflict with the online primary unit and possible loss or degradation of satellite network communications, use the following procedure. Use the following procedure when putting a VMS controlled modem into service.
N:M Hub Modem Redundancy 2. On the Administration > Feature Configuration page shown in figure C-33, enter the unit’s features and unlock codes. Figure C-33 Feature configuration page, CDM-570/570L 3. Disable STDMA 4. On the Administration page shown in figure C-34, set the Working Mode to Router - Vipersat. Figure C-34 Administration page, CDM-570/570L 5. Using the Internet Interface page shown in figure C-35, set the unit’s IP address to the IP address of the backup unit which replaced it.
N:M Hub Modem Redundancy Figure C-35 Ethernet Interface page, CDM-570/570L 6. On the Vipersat Configuration page shown in figure C-36, set the Unit Role to Hub Expansion. 7. This completes setting the unit to the Passive Configuration mode if it is a CDM-564L. It is possible the unit was being used to supply voltage to a LNB, which is described below. Figure C-36 Vipersat configuration page, CDM-570/570L 8.
N:M Hub Modem Redundancy Figure C-37 Transmit configuration page, CDM-570/570L 9. On the Satellite Modem > Configuration > Configuration > Rx Configuration page shown in figure C-38, set the Rx Frequency to the low end (50 or 950). Figure C-38 Set receive frequency to low end, CDM-570/570L 10. Disable the Satellite Modem > Configuration > Configuration > Block Up Converter (BUC) > BUC DC Power as shown in figure C-39.
N:M Hub Modem Redundancy Figure C-39 BUC configuration, CDM-570/570L 11. Disable the Satellite Modem > Configuration > Configuration > Low Noise Block Converter (LNB) LNB DC Supply Voltage as shown in figure C-40. Figure C-40 LNB configuration, CDM-570/570L 12. This completes the process of setting the VMS controlled modem to parked configuration mode and it now ready to be put back into service. 13.
APPENDIX DOMAIN CONTROLLER AND DNS This appendix describes configuring the VMS server or servers to perform the roles of network domain controller and DNS server for the VMS network. It is especially necessary that these functions be installed if the VMS installation is to be a redundant, fault-resistant installation.
• All existing disk volumes use the NTFS file system. Active Directory requires at least one NTFS volume in which to store the SYSVOL folder and its contents. FAT32 volumes are not secure, and they do not support file and folder compression, disk quotas, file encryption, or individual file permissions. • Disable any extra Ethernet adapters on the server and ensure that only one gateway is assigned to the server. • Disable the Windows Firewall.
C o n f i g u r i n g a Do m ai n C o n t r o l l e r a n d D N S Configuring a Domain Controller and DNS Before you begin configuring your server as a domain controller, verify whether or not: • TCP/IP configuration settings for the server are correct, particularly those used for DNS name resolution. The servers should have active Ethernet connections to each other. • All existing disk volumes use the NTFS file system.
C o nf i g ur i n g a D o m a i n C o nt r o l l e r a n d D N S Figure D-1 Manage Your Server dialog 3. Review the Preliminary Steps shown in figure D-2 and then click the Next button to proceed once you have verified these steps have been completed.
C o n f i g u r i n g a Do m ai n C o n t r o l l e r a n d D N S Figure D-2 Preliminary Steps 4. From the Configuration Options dialog shown in figure D-3, select the Custom Configuration radio button then click Next button. Figure D-3 Configuration Options 5. From the Server Role dialog shown in figure D-4, select the Domain Controller (Active Directory) item, then click the Next button.
C o nf i g ur i n g a D o m a i n C o nt r o l l e r a n d D N S Figure D-4 Server Role dialog 6. Verify your selection displayed in the Summary of Selections listing shown in figure D-5, then click the Next button to proceed. Figure D-5 Summary of Selections dialog 7. From the Active Directory Installation Wizard shown in figure D-7, click the Next button to begin the installation.
C o n f i g u r i n g a Do m ai n C o n t r o l l e r a n d D N S Figure D-6 Active Directory Installation Wizard 8. After reviewing the Operating System Compatibility information, shown in figure D-6, click the Next button. Figure D-7 Active directory installation wizard 9. After reviewing the Operating System Compatibility information, click the Next button. 10. From the dialog shown in figure D-8, select Domain controller for a new domain (default) radio button, and then click the Next button.
C o nf i g ur i n g a D o m a i n C o nt r o l l e r a n d D N S Figure D-8 Domain controller type dialog 11. From the Create New Domain dialog shown in figure D-9, select the Domain in a new forest (default) radio button, then click the Next button. Figure D-9 Create new domain dialog 12. In the New Domain Name dialog, enter a fully qualified domain name in the Full DNS name for the new domain box. A full DNS name has the structure similar to AnyName.company.com as shown in the example in figure D-10.
C o n f i g u r i n g a Do m ai n C o n t r o l l e r a n d D N S Figure D-10 New domain name dialog 13. In the NetBIOS Domain Name dialog shown in figure D-11, enter the NetBIOS name you have assigned to this domain. TACLAB0 is the NetBIOS name used in the example illustrated in figure D-11, but you should assign an appropriate name appropriate to your network. A NetBIOS name gives down-level compatibility. Figure D-11 NetBIOS domain name 14.
C o nf i g ur i n g a D o m a i n C o nt r o l l e r a n d D N S entries, click the Next button to continue. This is the default location for Windows. Figure D-12 Database and log folders dialog 15. Use the default folder location, C:\WINDOWS\SYSVOL as shown in figure D-13, for the Shared System Volume. Click the Next button to procede. Figure D-13 Shared system volume dialog 16.
C o n f i g u r i n g a Do m ai n C o n t r o l l e r a n d D N S to continue. The wizard will install and configure DNS support on the server. NOTE Note: The screen shown in figure D-14 will be displayed if you are configuring a server which has not had a previous DNS server installation. If you see a different screen at this point, check to make sure that the server has not been a previously configured as a DNS server. Figure D-14 DNS registration diagnostics screen 17.
C o nf i g ur i n g a D o m a i n C o nt r o l l e r a n d D N S Figure D-15 Permissions dialog 18. In the Directory Services Restore Mode Administrator Password dialog shown in figure D-16, enter the password assigned to the Administrator account to be used when the server is started in the Directory Services Restore mode. You should use a complex password with at least 1 alpha and 1 numeric character, such as V1persat. When the password has been entered and verified, click the Next button to continue.
C o n f i g u r i n g a Do m ai n C o n t r o l l e r a n d D N S Figure D-17 Summary screen 20. The wizard will begin configuring the Primary domain controller as shown in figure D-18. Figure D-18 Configuring primary domain controller 21. When prompted by the screen shown in figure D-19, click the Finish button to complete the setup.
C o nf i g ur i n g a D o m a i n C o nt r o l l e r a n d D N S Figure D-19 Complete installation screen 22. Click the Restart button shown in Figure D-20 to reboot the server. Figure D-20 Restart screen This completes setting the primary server as a domain controller.
Configuring a Secondary Domain Controller Configuring a Secondary Domain Controller The procedure in the section describes configuring a Domain Controller on the Secondary VMS server in a redundant installation. The following steps assume that the server is to be configured as the VMS Secondary Domain Controller (SDC) and has had a clean install of Windows 2003 server with service pack-1 and all updates. This procedure also assumes that the server’s device drivers have been loaded and are fully functional.
C o nf i g ur i n g a S e c o n d a r y D o m a i n C o n t r o l l e r Figure D-21 Manage your server dialog 3. Review the Preliminary Steps shown in figure D-22 and then click the Next button to proceed once you have verified these steps have been completed.
Configuring a Secondary Domain Controller Figure D-22 Preliminary steps 4. The wait screen shown in figure D-23 will be displayed while your network settings are being detected. Figure D-23 Network detection wait screen 5. From the Configuration Options dialog shown in figure D-24, select the Custom Configuration radio button then click Next button.
C o nf i g ur i n g a S e c o n d a r y D o m a i n C o n t r o l l e r Figure D-24 Configuration options 6. From the Server Role dialog shown in figure D-25, select the Domain Controller (Active Directory) item, then click the Next button. Figure D-25 Server role dialog 7. Verify your selection displayed in the Summary of Selections listing shown in figure D-26, then click the Next button to proceed.
Configuring a Secondary Domain Controller Figure D-26 Summary of selections dialog 8. From the Active Directory Installation Wizard shown in figure D-27, click the Next button to begin the installation. Figure D-27 Active directory installation wizard start 9. After reviewing the Operating System Compatibility information, shown in figure D-28, click the Next button.
C o nf i g ur i n g a S e c o n d a r y D o m a i n C o n t r o l l e r Figure D-28 Active directory installation wizard 10. After reviewing the Operating System Compatibility information, click the Next button. 11. From the dialog shown in figure D-29, select Additional Domain controller for an existing domain radio button, and then click the Next button. Figure D-29 Domain controller type dialog 12.
Configuring a Secondary Domain Controller created above. When you have completed entering the data, click the Next button to continue. Figure D-30 Network credentials 13. from the Additional Domain Controller dialog shown in figure D-31, click the Browse button on the Domain Name dialog box. 14.
C o nf i g ur i n g a S e c o n d a r y D o m a i n C o n t r o l l e r 15. Clicking the Browse button shown in figure D-31 brings up the Browse for Domain list shown in figure D-32. From the list of domains shown in the Browse for Domain list, select the Primary VMS server’s domain, then click the OK button to proceed. Figure D-32 Browse for domain list 16. The Additional Domain Controller screen shown in figure D-33 will be displayed the selected domain displayed. Click the Next button to continue.
Configuring a Secondary Domain Controller Figure D-34 Directory and log folders dialog 18. Leave the default folder location for the Shared System Volume, as shown in figure D-35, then click the Next button to continue. Figure D-35 Shared system volume 19. Type in the password for use by the Administrator account to be used when this server is started Directory Services Restore Mode. Enter the password in the Restore Mode Password and Confirm password dialog boxes as shown in figure D-36.
C o nf i g ur i n g a S e c o n d a r y D o m a i n C o n t r o l l e r Figure D-36 Directory services restore mode administrative password 20. Review the Summary screen shown in figure D-37, then click the Next button to proceed. Figure D-37 Summary screen 21. The Active Directory Installation Wizard screen shown in figure D-38 will be displayed while Microsoft Windows configures your server.
Configuring a Secondary Domain Controller Figure D-38 Active directory installation wizard screen 22. Review the screen shown in figure D-39 is displayed, then click the Finish button Figure D-39 Domain Controller confirmation screen 23. From the screen shown in figure D-40, click the Restart Now button.
C o nf i g ur i n g a S e c o n d a r y D o m a i n C o n t r o l l e r 24. After reboot, Windows displays the confirmation screen shown in figure D-41. Figure D-41 This completes setting the secondary server as a domain controller.
Installing Secondary DNS Server Installing Secondary DNS Server This procedure configures the secondary server to prepared take over the DNS function in the network if the primary server fails.
I n s t a l l i n g S e c o n d a r y DN S S e r v e r 2. Review the information in the Preliminary Steps screen shown in figure D-43 before proceeding and then click then Next button to proceed. Figure D-43 Preliminary steps screen 3. Highlight DNS server in the table shown in figure D-44 and then click Next button.
Installing Secondary DNS Server Figure D-44 DNS server role dialog 4. Review options selected as shown in figure D-45 and click the click the Next button to proceed. Figure D-45 DNS Selection summary 5. When prompted as shown in figure D-46, insert disc containing Service Pack 1 and click the OK button to start the installation process.
I n s t a l l i n g S e c o n d a r y DN S S e r v e r Figure D-46 Insert disk prompt 6. Setup will copy the required files and then proceed with configuring components as shown by progress bar in figure D-47. Figure D-47 Configuring components status 7. Click the DNS Checklists button shown in figure D-48 to display the checklist. After reviewing the DNS Checklist, click the Next button to continue.
Installing Secondary DNS Server Figure D-48 DNS server wizard welcome screen 8. Select the radio button Forward Lookup Zone as shown in figure D-49. Click the Next button to continue. Figure D-49 Select configuration action 9. Select the radio button This server maintains the zone as shown in figure D-50. Click the Next button to continue.
I n s t a l l i n g S e c o n d a r y DN S S e r v e r Figure D-50 Primary server location 10. Enter your DNS zone name in the Zone name dialog box shown in figure D-51. Click the Next button to continue. Figure D-51 zone name dialogr 11. Select the Allow only secure dynamic updates radio button shown in figure D-52. Click the Next button to continue.
Installing Secondary DNS Server Figure D-52 Dynamic update dialog 12. Review the Fowarders dialog shown in figure D-53 and enter the IP address of DNS servers that this server will forward to if it is unable to resolve the request locally. Click the Next button when ready to continue. Figure D-53 Forwarders 13. After reviewing the Completing the Active Directory Installation Wizard screen shown in figure D-54, click the Finish button to continue.
I n s t a l l i n g S e c o n d a r y DN S S e r v e r Figure D-54 Completing the configure a DNS server wizard 14. Carefully review the information in figure D-55 then click the Finish button. Figure D-55 Completion screen 15. When the DNS error message shown in figure D-56 is displayed, dick the OK button.
Installing Secondary DNS Server Figure D-56 DNS error message This completes the installation of the DNS server on the Secondary VMS server in a redundant con figuration. At this point return to section “Stopping Previous VMS Version (Upgrade)” on page 2-10 of Chapter 2, “VMS Installation” to complete the VMS installation.
I n s t a l l i n g S e c o n d a r y DN S S e r v e r { This Page is Intentionally Blank } D-36 V M S U s e r G u id e
APPENDIX SNMP TRAPS Introduction This appendix describes the use of SNMP traps by the Vipersat Management System (VMS). SNMP traps enable the VMS to capture significant network events, then generate an SNMP message reporting the event.
Introduction Using SNMP Traps SNMP (Simple Network Management Protocol) along with the associated Vipersat Management Information Base (MIB), provides trap-directed notification of network changes. VMS can be responsible for a large number of network parameters as defined in the Vipersat MIB. It is impractical for VMS to poll or request information from each device in a satellite network.
C o nf i g u r i n g S N M P T r a p s Configuring SNMP Traps To configure SNMP traps, from ViperView, shown in figure E-1, right click on the server’s icon and select the Properties command from the drop-down menu. Figure E-1 Server drop-down menu Clicking the Traps tab on the server’s properties screen displays the Traps dialog shown in figure E-3. Figure E-2 Properties general tab Select the Traps tab to display the SNMP Manager TRAP dialog shown in figure E-3.
C o nf i g ur i n g SN M P T r a p s • Community String Figure E-3 Server traps tab Insert Clicking the Insert button displays the Trap Destination dialog shown in figure E-4 allowing you to enter the Trap’s destination: • IP Address • Community String • Port Number Figure E-4 Trap desitination Modify Selecting an existing Trap Destination from the list as shown in figure E-3 then clicking the Modify button will display the destination as shown in figure E-4 allowing you to change the Trap’s destinatio
C o nf i g u r i n g S N M P T r a p s Remove Selecting a Trap Destination from the list shown in figure E-3 then clicking the Remove button will remove the Trap Destination.
Summary Summary You should keep in mind the following characteristics of an SNMP Trap. • SNMP is not a “reliable” transport protocol. If the Trap message is lost due to network issues (congestion, noise, delays, etc.), the SNMP protocol will NOT retransmit the lost trap message. • SNMP (v1&v2) is not a secure protocol. It is not difficult to eavesdrop or spoof messages. Isolating SNMP traffic from end-user channel is recommended. • VMS will generate a trap message for each destination entered.
APPENDIX AUTOMATIC SWITCHING General The basic signal topology in a Vipersat network is TDM (Time Division Multiplex) outbound and Vipersat’s proprietary STDMA (Selected Time Division Multiple Access) inbound. The STDMA slots can have their duration and bandwidth allotments varied to tailor bandwidth allocation to meet the bursty traffic load of a typical data network. When required, a network is switched from STDMA to SCPC.
L o a d s wi t c h i n g Bandwidth Allocation and Load Switching Load Switching is the mechanism by which the Vipersat network switches a remote terminal from STDMA to SCPC mode or SCPC-to-SCPC dynamic based on traffic levels at the remote. There are two components of load switching in a Vipersat system: VMS (Vipersat Network Management), MODEM (CDM-570/570L, SLM-5650A).
L o a d s w i t c h in g Bandwidth Allocation and Load Switching by the STDMA Controller: As part of normal STDMA processing, the hub monitors the traffic levels from each of the remotes for which it is allocating bandwidth. This is done using the STDMA ACK management message (Table 1) which is transmitted at the beginning of each burst from the remote. The STDMA ACK contains two metrics that are used by the hub: 1. The number of bytes received for transmission (Queued Bytes) since the last cycle. 2.
L o a d s wi t c h i n g the traffic requirements of the remote, or if the remote has exceeded the maximum allocation, some data will be held for the next cycle. In this case, the number of Bytes in Queue will start to grow and will exceed the Queued Bytes. (In other words, the Bytes in Queue is the sum of the data not yet transmitted plus the new data received).
L o a d s w i t c h in g needed. Note that the GIR allocations are restricted so that the assigned GIR totals cannot exceed available bandwidth. If this restriction is somehow violated, then it will not be possible to properly allocate bandwidth when the network is overloaded.) • Entry Channel Mode - This is the same as Dynamic Cycle, except that as soon as the Hub receives an STDMA ACK, it initiates a switch to SCPC mode based on the policy set for that remote.
L o a d s wi t c h i n g Figure F-2 Hub Load switching menu, SLM-5650A • Auto Switching - This is a Vipersat feature which is enabled in the CDM-570/570L Features menu. If Auto Switching is not enabled, Load Switching will be ignored. There is no auto switching enable button in SLM-5650A modem configuration menus, the operator only needs to enable each switching function. • Load Switching - This is a type of Automatic Switching that is based on the amount of traffic at a remote.
L o a d s w i t c h in g Load Switching Process Each time the hub receives an STDMA ACK, it computes the average load for that remote. This average is then compared to the bandwidth currently allocated to the remote. For example, if a remote gets a 50 ms slot in an upstream that is running at 512000 bps then it can transmit 0.050 * 512000 = 25600 bits = 3200 bytes. If the Queued Bytes was 3000, then for that cycle, the remote was at 3000/3200 = 93.75% of capacity.
L o a d s wi t c h i n g Figure F-3 Switching menu for a remote, CDM-570/570L Figure F-4 Load switching menu for remote, SLM-5650A • Auto Switching - Same as Hub • SCPC Step Up Threshold - Same as STDMA Slot Capacity at hub. • SCPC Step Down Threshold - Similar to STDMA Slot Capacity at hub except Step Down is used to trigger a switch if the average load falls below this value • SCPC Step Delay - Same as STDMA Switch Delay at hub • SCPC Stepup Excess - Same as Percent Allocation at hub.
L o a d s w i t c h in g Determining Need-for-Change The following process is used to determine if bandwidth utilization warrants a need-for-change. The user defines both a Step Up and Step Down threshold in terms of percent utilization, a bandwidth margin value, and a latency or averaging period. Once per second, the CDM router software determines the current percent utilization by dividing the bits transmitted by the current transmit data rate.
Load Switch Example Load Switch Example An automatic load switching example, illustrated in the schematic diagram in figure F-5, illustrates how a network can respond to changes in traffic volume or load conditions. The network’s capability and method of response to load changes is determined by the setting and capability of each of the components in the system such as the transmitter power output, the antenna capabilities for each of the sites in the network, and the policies set in VMS.
Load Switch Example 3. The STDMA Hub Controller compares the remote CDM-570/570L’s preselected buffer limits with its buffer status and if the buffer status exceeds the preselected limits the STDMA Hub Controller increases the time-slot allocated to that channel. If this brings the buffer status within established limits no further changes are made. 4. If the buffer status continues to exceed the preselected limits, the STDMA Controller sends an Automatic Switch Request (ASR) to the VMS. 5.
Load Switch Example Reduced data flow in switched mode (SCPC) In the event the data flow is reduced, for example a streaming file transfer terminates, the SCPC switched demodulator detects the reduced flow and notifies the VMS. The VMS will then send a switch command to reduce the size of the carrier bandwidth to the new calculated bandwidth requirement. This entire process is automatic following the policies established for the network.
A p p l i c a t i o n s w i t c h in g Application switching Application switching, diagramed in figure F-6, also is capable of changing bandwidth used, but the change is determined entirely by the type of application being requested ignoring load requirements. Figure F-6 Application switching diagram, CDM-570/570L Note: Application switching is not available for SLM-5650A modems. The following application switching section refers to CDM-570/570L modems.
Application switching The modem/router sends a switch request to the VMS requesting a carrier for the application type. Typical applications include: • Video • Voice over IP (VoIP) Each application type will have been assigned a bandwidth allocation when the policy for the remote site is established. The voice application, for example, might have had the bandwidth set in the policy to handle three simultaneous voice connections. When a VoIP protocol is detected in the H.
T y p e o f S e r v i c e ( T o S ) S w i t c h in g Type of Service (ToS) Switching Type of Service (ToS) switching is used on circuits carrying encrypted traffic where the packets cannot be examined to determine the type of traffic being carried. Normally, in a non-encrypted Vipersat network, packets are classified by the remote CDM-570/570L using protocol classification detection and the results are forwarded to VMS via Automatic Switch Request (ASR) messages.
T y p e o f S e r vi c e ( T o S ) S w i tc h i n g { This Page is Intentionally Blank } F-16 V M S U s e r G u id e
APPENDIX ENTRY CHANNEL MODE SWITCHING Entry Channel Mode (ECM) STDMA entry channel mode provides a method for remotes requiring SCPC access channels to enter/re-enter the network initially or after a power or other site outage. The switch time will be variable based on the burst rate (bps) of the STDMA group, the number of remotes with slots in the group, and where in the burst cycle the remote is when it acknowledges receipt of the burst map.
E n t r y C h a n n e l M od e ( E C M ) After all remotes are processed into ECM, the Burst Controller drops into sanity mode sending a keep alive map to service remotes which may have their SCPC carrier inhibit flag set. The keep alive message is sent once every two seconds until re-entry is invoked. Fail Safe Operation For a detailed description of the features of VMS applications switching, refer to Appendix F, "Automatic Switching".
Entry Channel Mode (ECM) ECM Switch Recovery< 3min. VMS State Connected Burst Demod Switched Demod Remote 0 Satellite Delay 250 ms + 30ms E-E State Disconnected 180 Registration Acknowledgment Failure 189 Revert Switch Command 189.025 Switch Command ECM 189.6 No Switch wait ACK Switch Acknowledgment Force Connected 0 Unit Reboot 30 Home State- STDMA Wait for TX Grant 180.28 State Unknown Force Registration Set ID 189. 305 Process Switch Command 190.31 STDMA TX Grant Burst ACK 191.
E n t r y C h a n n e l M od e ( E C M ) ECM Switch Recovery> 3min. VMS State Connected Burst Demod Switched Demod Remote 0 0 Unit Reboot Satellite Delay 250 ms + 30ms E-E State Disconnected 180 Registration Acknowledgment Failure 189 Revert Switch Command 189.05 Revert Acknowledgment Failure 192 Switch Command ECM 240.28 Failure Failure 180.28 No Communications 189.35 No Communications > 240 Home State- STDMA TX Grant Burst ACK 240.61 Process Switch Command 240.
Entry Channel Mode (ECM) NOTE Note: Refer to the SLM-5650A modem manual for Entry Channel configuration setup. The text referenced within are similar between modems only the page layouts are different. Figure G-3 STDMA tab with ECM mode, CDM-570/570L Switching an ECM Remote from SCPC to STDMA Use the following procedure to switch a remote operating in SCPC mode while in the ECM mode. 1.
E n t r y C h a n n e l M od e ( E C M ) 3. Click the Modify... button to display the Remote Entry dialog shown in figure G-5. You can use the up and down arrows next to the button to change the selected remote. Figure G-5 Remote bandwidth entry, CDM-570/570L 4. To force a switch from ECM SCPC mode to STDMA mode, set the current value in the SCPC Data Rate dialog box to 0 (zero) as shown in figure G-5 then click the OK button. NOTE Note: This switch must be performed manually. 5.
Entry Channel Mode (ECM) { This Page is Intentionally Blank } Appendix G - Entry Channel Mode Switching G-7
E n t r y C h a n n e l M od e ( E C M ) G-8 VMS User Guide
APPENDIX VMS BILLING LOG TRANSLATOR (VBLT) Description VBLT is a windows console application that converts switch events, stored in the VMS 3.x event log, into a billing log format. VBLT can be run directly from the command line console, or using VBLT.ui, a graphical user interface frontend, or as a scheduled task using the windows task scheduler.
D e s c r i p ti o n Consult your VMS or system administrator for more information on accessing a remote VMS server. Console Mode VBLT has the following command line options when used in console mode: -r days - Number of days (24hr period) to retrieve starting from current time. Default is 1 day. -v server - IP address, UNC, or DNS name of VMS 3.1 server. If this option is not specified, the local VMS server (localhost) is used. -s session - Sets the starting session ID. Zero (0) is used as default.
GUI Mode GUI Mode VBLT.ui provides a Windows user interface to the VBLT application. It also allows the user to specify start/end time & date range for billing log retrieval where as the console mode retrieves logs based on number of days from current time. To use VBLT.ui, start the VBLT.ui application from the Windows Explorer by double clicking it. Verify that the VBLT.EXE application is in the same directory as VBLT.ui.EXE. Operation 1.
GUI Mode Figure H-1 VLBT graphic user interface 3. Selecting the Use Local Time option in the Options box determines whether to use local time zone references with respect to start and end time, and the time stamp on the output file. Selecting the Quiet Mode option will suppress any output to a VBLT console window. 4. The VMS Server entry is optional. Leaving it empty, or entering localhost will retrieve the logs from the local VMS server running on the same PC as VBLT.
3.3 Scheduled Task Mode 3.3 Scheduled Task Mode The billing log retrieval process can be automated by using the Windows Task Scheduler. The Windows Task Scheduler will execute VBLT on a scheduled basis. To create a scheduled VBLT task, use the Scheduled Task Wizard. Follow the steps below: 1. Open the Windows Task Scheduler, shown in figure H-2, by clicking Start, click All Programs, point to Accessories, point to System Tools, and then click Scheduled Tasks. Figure H-2 Scheduled tasks 2.
3.3 Scheduled Task Mode Figure H-3 Scheduled task wizard 5. Set the start time, start date, and recurrence options. 6. Enter your user and name password to confirm the new task entry. This username and password should be a valid VMS user. 7. In the last step, check the “Open advanced properties for this task ….” Option, then click Finish. 8. The last step is to add the VLBT command options to the task. In the Run text box shown in figure H-4, go to the end of the VBLT.exe and add the desired options.
3.3 Scheduled Task Mode An alternative method to running a scheduled VBLT task is to create a batch file that calls VBLT with the desired options. A scheduled task is created to run this batch file. This simplifies the maintenance as only the batch file needs to be modified if they are any changes to VBLT options.
B i l li n g L o g F o r m a t Billing Log Format The billing log format is created from switch events logged by the VMS. The billing log consists of eight (8) comma separated value fields as follows: 1. Satellite Name - name of satellite, as shown in VMS, that contains the subnet which generated the switch event. 2. Antenna Name - name of Antenna, as shown in VMS, associated with the Subnet which generated the switch event. 3. Date - logged date of switch event in “dd/mm/yyyy” format 4.
APPENDIX GLOSSARY A ALC Automatic Limit Control – A closed loop mechanism controlling the gain stabilization of the HPA’s RF output power. APL Asynchronous Party Line – A Vipersat term for RS-485 multi-drop bus used for control of indoor equipment. See also SPL. ARP Address Resolution Protocol – A protocol for a LAN device to determine the MAC address of a locally connected device given its IP address. See also MAC.
BUC Block Up Converter – An upconverter so called because it converts a whole band or “block” of frequencies to a higher band. IF is converted to final transmit frequency for satellite communications. BPS Bits Per Second – A measure of transmission speed. See also Kb/s & Mb/s. BPSK Binary Phase Shift Keying – A modulation technique in which the carrier is phase shifted +/-180 degrees. See also QPSK.
DRAM Dynamic Random Access Memory DSCP Differentiated Services Code Point – The 6-bit field in an IP packet header that is used for packet classification purposes and is the portion of ToS that is detected by Vipersat modems. DSP Digital Signal Processor – A microprocessor chip optimized for signal processing applications. DVB Digital Video Broadcast DVP Digital Voice Processor – Used in packet voice applications.
G G.729 GIR Group ID GUI ITU standard for LD-CELP (Low Delay – Code Excited Linear Prediction) voice encoding at 8 kb/s. Guaranteed Information Rate A number assigned to equipment which defines it as a member of a group when addressed by the VMS burst controller. Graphical User Interface – A form of graphical shell or user interface to a computer operating system or software application. H HDLC High Level Data Link Control – A standard defining how data may be transmitted down a synchronous serial link.
K Kb/s Ku-Band Kilo bits per second – 1000 bits/second. A measure of transmission speed. See also bps & Mb/s. A frequency band used for satellite communications. For terrestrial earth stations the receive frequency band is in the range 10.95–12.75 GHz and the transmit frequency band is 14.0–14.5 GHz. See also C-band. L L-Band A frequency band commonly used as an IF for satellite systems using block up/ down conversion. Usually 950–1450 MHz.
N NAT Network Address Translation – An Internet standard that enables a LAN to use one set of IP addresses for internal (private) traffic and a second set of addresses for external (public) traffic. NIC Network Interface Controller – The network interface for a PC/workstation that provides Ethernet connectivity. Depending on the computer, the NIC can either be built into the motherboard, or be an expansion card. Some computers (e.g., servers) have multiple NICs, each identified by a unique IP address.
Q QPSK QoS Quaternary Phase Shift Keying – A modulation technique in which the carrier is phase shifted +/- 90 or +/-180 degrees. See also BPSK. Quality of Service R Remote Satellite earth site that links to a central network site (hub). RF Radio Frequency – A generic term for signals at frequencies above those used for baseband or IF. RFC Request For Comment – The de-facto Internet standards issued by the Internet Engineering Task Force (IETF).
Star Topology A network topology which, if drawn as a logical representation, resembles a star with a hub at the center. STDMA Selective Time Division Multiple Access – A multiple access technique where users time-share access to a common channel with variable-sized time slots allocated on usage. Streamload Protocol A proprietary Vipersat data streaming protocol.
VCS Vipersat Circuit Scheduler – A proprietary satellite communication scheduling system used to schedule Vipersat network resources in support of a variety of high-priority applications such as video conferencing and scheduled broadcasting. VFS Vipersat File Streamer – A file transfer application utilizing UDP and a proprietary Streamload protocol to transmit data across the Vipersat network.
{ This Page is Intentionally Blank } I-10 V M S U s e r G u id e
INDEX automatic F-2 A automatic load switching log event log viewer F-2 M B basic guaranteed bandwidth 3-37 C carrier type flag 3-21 CIR 3-37 committed information rate 3-37 Connection Manager 3-5, C-6 D distribution lists global level 5-22 site level 5-37 E G-6 F 3-21 H 2-1, 2-30 hardware requirements Heartbeat enable C-24 heartbeat C-32 L load switching VMS User Guide main screen Monitor & Control Explorer 5-7 Monitor & Control Explorer main screen 5-7 P Passive Configuration C-34 policy g
contention C-5, C-12 manual switching C-12 priority C-9 properties C-8 standby role C-4 status C-6 synchronization C-4 service installing F-2 SNMP Manager TRAP E-3 SOTM 3-44 T ToS Index-2 application type F-15 description F-15 V VMS initial setup 3-5 installing services F-2 network build 3-11 redundancy C-1 W WRED enabling I-9 VMS User Guide
