Beruflich Dokumente
Kultur Dokumente
November 7, 2008
Copyright 2008 VT iDirect, Inc. All rights reserved. Reproduction in whole or in part without permission is prohibited. Information contained herein is subject to change without notice. The specifications and information regarding the products in this document are subject to change without notice. All statements, information, and recommendations in this document are believed to be accurate, but are presented without warranty of any kind, express, or implied. Users must take full responsibility for their application of any products. Trademarks, brand names and products mentioned in this document are the property of their respective owners. All such references are used strictly in an editorial fashion with no intent to convey any affiliation with the name or the product's rightful owner.
Document Name: RN_Release Notes_Release iDS 8.0.2.7_Rev A_110708.pdf Document Part Number: T0000168
ii
Contents
Special Notices
NetModem II+ Remotes and Line Cards No Longer Supported ........................................ 1 NetModem II+ Components Available for Adding to Network in iBuilder [16252] .................. 1
New Features
New Antenna Controller Configuration Parameters [14884] .......................................... 3 Custom Configuration for SeaTel (DAC-97) Antenna Controller Offsets ............................. 5
Bug Fixes
Data Path Issues .............................................................................. 9
13997 [15141] Downstream Bandwidth Group Has Huge Demand and Got Zero Allocation ...... 9 14527 TCP Default Service Level Rejected Connections When Switching from Application-based to Remote-based Mode ............................................................... 9 15474 Network Timeplan Not Properly Allocated Under Specific Carrier Configurations ....... 10 15519 PP Controller Message Buffer Increases Caused PP Blade Failover ......................... 10 15876 TCP Download Rate to HLCs Based on Downstream Information Rate ..................... 10
iii
Known Issues
Data Path Issues ............................................................................ 19
14639 Static Remotes In Roaming Mode Do Not Switch Beams/Frequency ........................ 15054 Upgrade Fails When First PP Blade has No Remote Assigned ................................ 15404 Spectral Inversion for Second Demodulator Not Set Correctly .............................. 16281 Changing from Roaming to Stationary Prevents Remotes Coming into Network .......... 19 20 20 20
iv
Installation Instructions
Prerequisites for iDS 8.0.2.7 Installation ............................................. 23 Downloading Required Files for Release 8.0.2.7 .................................... 23 Special Notices for iDS 8.0.2.7 Upgrades ............................................. 24
vi
Revision History
The following table shows all revisions for this document. Refer to this information to verify that you have the latest version. If you do not have the latest version or you are unsure, you can access the TAC web page at: iDirect.tac.net and click on the Software Releases link. You can then scroll down to the iDS release that is applicable to you and download the latest version of this document.
Revision
A
Date Released
November 7, 2008
Who Updated?
EHoffman
vii
viii
Purpose
These release notes are written to inform our customers of new features and resolved issues that are incorporated into this release. Any issues that you may encounter in this release are also described along with associated resolutions, where applicable.
Intended Audience
The intended audience for this guide is network operators and network architects that work with the iDirect network system.
ix
Document Conventions
This section illustrates and describes the conventions used throughout the manual. Take a look now, before you begin using this manual, so that youll know how to interpret the information presented. Convention Description
Blue Courier font Courier font Used when the user is required to enter a command at a command line prompt or in a console) Used when showing resulting output from a command that was entered at a command line or on a console.
Example
[SWITCH_PORT_n] vid = vlan_id
Output similar to the following sample appears: [SECURITY] password = $idi2$/bFMhf$5H8mYAaP1sTZ0m1Ny/dYyLaS40/ admin_password = $idi2$146rgm$.KtDb4OH5CEBxzH6Ds2xM.ehHCH os_password = $1$UTKh0V$cc/UfNThFmBI7sT.zYptQ0 1. If you are adding a remote to an inroute group, right-click the Inroute Group and select Add Remote. The Remote dialog box has a number of userselectable tabs across the top. The Information Tab is visible when the Dialog opens.
Used when the user is required to type information or values into a field within a windows-type interface software. Used when specifying names of commands, menus, folders, tabs, dialogs, list boxes, and options.
Blue Trebuchet font Bold italic Trebuchet font Red italic Trebuchet font (or see table below)
Used to show all hyperlinked text within a document. Used to emphasize information for the user, such as in notes. Used when the user needs to STRICTLY follow the instructions or have additional knowledge about a procedure or action.
For instructions on adding an iSCPC line card to the network tree and selecting a Hub RFT for the line card, see Adding an iSCPC Line Card on page 108. Note: Several remote model types can be configured as iSCPC remotes.
Symbol
Definition
CAUTION: When you see this alert symbol and the CAUTION heading, strictly follow the warning instructions to avoid personal injury, equipment damage, or loss of data. WARNING! Electric shock hazard: When you see this symbol and the WARNING heading, strictly follow the warning instructions to avoid electric shock injury.
WARNING
Getting Help
The iDirect Technical Assistance Center (TAC) is available to help you 24x7x365. iDS Software users guides, installation procedures, an FAQ page, and other documentation that supports our products are available on the TAC webpage. Please access our TAC webpage at: http://tac.idirect.net. If you are unable to find the answers or information that you need, you can contact the TAC at (703) 648-8151.
xi
xii
Special Notices
This section presents special notices and procedures for implementing iDS Release 8.0.2.7. Please read this information prior to installing the new release.
CAUTION: All support for NetModem II+ remotes and NetModem II+ Universal Line Cards has been removed in this release. If you are using these remotes or line cards in your network, you cannot upgrade to this release.
New Features
This chapter describes all new features and enhancements in iDS Release 8.0.2.7.
iBuilder changes to support all four antenna controller configuration parameters shall be incorporated in a subsequent software release. Note: These new parameters are fully functional with any iNFINITY series remote. NetModem II, NetModem II+ and eVolution remotes are not supported in this release.
Antenna Controller Protocols Supported The appropriate antenna controller protocols are used to issue these commands and are automatically selected by the software based on the Reflector parameter selected for use with the remote.
The protocols used to support these commands shall support the use of the following vendor equipment: SeaTel (DAC-97) Orbit Marine (AL-7104)
In the case of SeaTel, the commands will be sent to both the above-deck and the below-deck controllers. Communicating Antenna Controller Parameters iDirect remotes shall have the ability to select up to four LNB local oscillator frequencies for use with dual and quad band LNBs. The remote shall select specific LO frequencies by commanding various antenna controllers to output discrete LNB voltages, along with the presence or absence of a 22 KHz tone. Four LNB local oscillator frequency selections are available which are generated from the 4 (2x2) combinations of the following two physical configuration parameters: LNB Voltages [iBuilder VSAT tab] LNB Local Oscillator Frequency Selection [custom key configurable]
LNB Voltage Selection A fixed LNB voltage value of either 18V or 13V can be selected in the LNB Voltage field in the Remote Antenna section of the remotes VSAT tab.
These fixed (discrete) LNB voltages are then outputted by the antenna controller to the LNB, signaling the LNB to adjust frequency. The voltage level in this case is only used for signaling purposes. LNB Local Oscillator Frequency Selection Setting this configurable parameters creates a redundant signal to turn on/off the voice band 22 KHz signal on the LNB. This voice band signal has no other operational effect on LNB. This custom key can be set as follows: [SATELLITE] lnb_22khz = 1 A value of 1 activates the 22 KHz tone. The Polarization skew value of the satellite and Installation skew can be communicated to the antenna controller as part of beam selection. These parameters are defined using the additional custom keys defined in Custom Configuration for SeaTel (DAC-97) Antenna Controller Offsets.
The Satellite Polarization Skew (pol_skew) and Installation Skew (install_skew) values are defined using the custom keys documented in this section, and then combined
when communicated to the NMS as the SeaTel pol_offset value. The NMS then communicates these values to the antenna controller as part of beam selection. Defining Satellite Polarization Skew Used for both Orbit Marine and SeaTel antenna controllers, this value is the difference in degrees of the satellite orientation relative to earth horizontal. Polarization skew is set with the following custom key: [SATELLITE] pol_skew = x where: pol_skew = a fixed values that vary 1-to-3 degrees for each satellite. Different satellites have different pol_skew values, since each satellite has a slightly different angular orientation in orbit. This value can be negative or positive. Defining Installation Skew The Installation skew (install_skew) value is the angular difference between the antenna controller mounting relative to "local horizontal," determined at ship-board installation. When the iDirect remote commands the antenna to switch to a new beam, the ship-board remote continues to use the same Installation skew value. Installation skew is set with the following custom key: [ANTENNA] install_skew = 30 where: install_skew = fixed value determined at ship-board antenna installation. Value relates to the actual installation of the physical antenna aboard the ship. This setting defaults to a value of 30. Determining SeaTel Installation Skew Values In order to avoid re-measuring and re-computing the Installation Skew (install_skew) values for each ship in each beam, SeaTel antenna installers and NMS operator should follow these steps to determine the install_skew value for each ship board installation: 1. Perform the usual installation and lineup, ignoring automatic beam switching. 2. Determine the correct SeaTel pol_offset value in the usual manner during the line-up. For a satellite with a zero degree skew and with a perfectly-aligned shipboard, this value will be the nominal value for the particular pedestal type (wither 30 or 40 degrees.) 3. Find the actual satellite pol_skew value as published by the satellite provider. This value is usually a floating point number in the range of about -5.0 to +5.0 degrees, but can be larger. 4. Subtract the satellite pol_skew value from the SeaTel pol_offset value. For example, for a measured SeaTel polarization offset of 35 and a satellite pol_skew of 5, the install_skew would be calculated as follows: install_skew = 35 - 5 = 30
For a measured SeaTel polarization offset of 28 and a satellite pol skew of -3, the install_skew would be calculated as follows install_skew = 28 - (-3) = 31 5. Using iBuilder, define the install_skew and pol_skew custom keys to configure the remote with the install_skew value computed in this procedure, and the satellite pol_skew obtained from the satellite provider.
Bug Fixes
This section lists all bugs that are fixed in iDS Release 8.0.2.7. These fixed bugs are grouped into the following three categories: Data Path (Protocol Processor, Hub Line Card, Remote, NMS Server) iSCPC (all) NMS/Reporting (Client applicationsiBuilder, iMonitor, NMS Server)
14527 TCP Default Service Level Rejected Connections When Switching from Application-based to Remote-based Mode
Fixed the issue occurring after changing the NET QoS mode from Remote-based to Application-based (and the Inroute as well to Application-based), where TCP connections were being rejected from any over-the-air (OTA) source but the NMS. Corrected in this release.
15474 Network Timeplan Not Properly Allocated Under Specific Carrier Configurations
As part bandwidth allocation, the DA on the blade assigned traffic slots to each modem. With a network consisting of multiple upstream carriers in an Inroute Group, a change to the remote's Tx synthesizer was required when a modem was instructed to hop from one frequency to the next. On a limited number of upstream/downstream configurations (and where there was a change in carrier for the first slot in a frame) the transmit frequency was updated incorrectly. This resulted in loss of data at the hub and transmission at the incorrect frequency (at modulo 10MHz of the upstream carrier) until the next carrier change. When the network got into this condition, trying to bring multiple remotes into the network caused all remotes to experience instability. For example, the following network configuration was known to cause this problem: Downstream 512 kbps (Info Rate) [480.117 sym rate] QPSK FEC 0.533 117 blocks per frame (124.834 ms frame length) Upstream 512 kbps (Info Rate) [480.117 sym rate] QPSK FEC 0.533 Acq aperture 824 Guard band 824 106 burst per frame Fixed in this release.
10
iSCPC Issues
12488 iSite is not allowing to add certain IP address to the LAN
Corrected the problem where iSite was not allowing any IP addresses greater than x.x.x.224 to be added to the LAN-side of the remote. This was affecting the iSCPC remotes, since iBuilder was allowing these same higher IP addresses to be configured for the LAN-side of the remote. Fixed in this release.
15647 iSiteCrashes When Selecting Assign VLAN Option Under Port View
Corrected the problem where iSite was crashing after logging into an iSCPC remote, and right-clicking on a port under the Port view (on Switch tab without clicking Configure option) and selecting the Assign Vlan option. Fixed in this release.
15818 iSCPC NMS: Service Profiles Missing Under QoS Tab of iMonitor Control Panel
Fixed the display issue in the QoS tab of the iMonitor control panel where Service Profiles were missing for iSCPC line cards and remotes. If new Filter Profiles were created and assigned to a line card, the newly created Filter Profiles were not getting displayed (with only default profiles displayed). Corrected in this release.
11
NMS/Reporting Issues
14439 iMonitorSAT Longterm Bandwidth Usage Window Overreported Multicast/Broadcast Values
Corrected the issue where the SAT Longterm Bandwidth Usage window was overreporting Multicast/Broadcast values when the Total all remotes option was selected. Instead of displaying Multicast/Broadcast values just once (correct behavior), the values displayed were multiples of the correct valuesmultiplied by the number of remotes in the request. Consequently, the Dn Multicast, Broadcast and Total fields on both the Totals and Averages tab, as well as the Dn % of Max field on Averages tab were all displaying values that were incorrectly high. Fixed in this release.
14722 iBuilderAble to Reorder User Application Before NMS Application and After Default Application
Fixed the problem in both the GQoS Downstream and Upstream Group Profiles screen, where iBuilder erroneously allowed the User Application to be ordered before the NMS Application and after the Default Application. Corrected in this release.
12
15219 iBuilderApplication Order Placement Between Group and Profile Views Out of Synchronization
Corrected the Group QoS issue in iBuilder where creating a new application in a Group View and adding the same application in a Profile View could knock the display ordering of applications out of synchronization. The following scenario describes how this problem occurred: 1. In iBuilder, created two Application Profiles, for example A1 and A2. 2. Moved to a Profile View and added these applications. 3. Reordered the Applications in the Group View such that A2 preceded A1. 4. Moved to a Profile View and confirmed the ordering change took place. 5. Moved to a Group View and added another application, for example A3. In the same view, reorder A3 to go before A2, leaving the Group View application ordering as NMS, A3, A2, A1, Default. 6. Move to a Profile View and add the A3 application. At this point in the Profile View, the A3 application erroneously displayed after the A1 application and before the Default application, with the overall Profile View ordering displaying as NMS, A2, A1, A3, Default.
13
15435 iMonitorSerial Numbers Over 65536 Incorrectly Displayed In Slot Assignment Window
Fixed the issue in iMonitor where serial numbers greater than 65536 were displaying as (actual serial number minus 65536) in the Time Plan >Slot Assignment window. This problem occurred because the serial number shown in this window was a 16 bit number (which can range up to a value of 65535). Consequently, when the serial number was greater than 65535, the number displayed as the actual serial number minus 65536. Corrected in this release.
15565 Some Services Not Starting If OSS Server Not Licensed on NMS
Corrected the problem occurring when there was no OSS Server (osssvr) license enabled on the NMS, and the NMS was started using the idirect_nms start command. In these instances, the nms_monitor and snmpsvr services could, in some instances, fail to start. The idirect_nms script worked fine when the primary server detected [no license] for the OSS, but the script failed to start all servers when the primary server reported [fail] for the OSS. Fixed in this release.
15665 iBuilder"Check versions only" Option for TCP Package Download Does Not Function
Fixed the Check version only option (under Images version check) of the TCP Package Download function. This option was not working, nor did it report the version of the targeted line cards or remotes. Corrected in this release.
14
15671 iBuilderGQoS: Remotes Not Assigned to Correct Service Groups After Unassigning
Fixed the display problems occurring in iBuilder after unassigning and deleting the Service Groups/Service Profiles in which remotes were assigned. The remotes moved to Deactivation pending state, and after applying the Deactivation pending state, the remotes moved to a Nominal state. However, the Options file of the remote indicated the remote was still assigned to the same Service Group, whereas in the Modify window of Network/Inroute Group the remotes were not assigned to any Service Group. Also in the Modify window of the remote, under the GQoS tab, the remote was not assigned to any Service Group. Corrected in this release.
15697 iMonitorPrint and Print Preview Not Working from Events/Conditions Tab
The Print and Print Preview options on the Event/Conditions tab of the iMonitor remote control panel window were not working. Fixed in this release.
15698 iBuilderCrashes When Name Header on Visible to VNO Group Window Selected and Header Sort Attempted
iBuilder was crashing when attempting to sorting the column headers in the Visible to VNO Group window accessed by selecting the Modify VNO option from the iBuilder tree. Corrected in this release.
15
15739 iBuilderGQoS: NMS Application Priority and Cost Values Varying from Group View to Profile View
Fixed the display issue in iBuilder where the NMS Application Priority and Cost display values were varying from the Group View to the Profile View windows (under Group Profiles). Corrected in this release.
15742 iBuilderSwitch Port Not Assigned To Any VLAN After VLAN+1 Deleted from Protocol Processor
Fixed the problem where the switch port which was assigned to VLAN+1 earlier is not automatically changing to the default/All VLANs, after deleting VLAN+1 from the Protocol Processor (in the Switch tab of remote Modify window). A blank space was displaying instead. Corrected in this release.
15750 iBuilderRemote Fields With Dissimilar Values Not Disabled When Modifying in Details View
While modifying multiple remotes (right-clicking and selecting Modify) together in the Details view of an Inroute Group, the options that had different configurations for each remote were available for editing rather than being disabled. Fixed in this release.
15781 iBuilderVNO Users Lose Permissions Selecting "Update Properties" for Remote
Corrected the issue where VNO users were losing their permissions when right-clicking a newly created remote and selecting Update Properties in Roaming (and updating a value such as the remote name). Fixed in this release.
15894 iBuilderDeleting Bandwidth Group From Group View Leaves Remote Without VR0
Corrected the issue where deleting the default Application Bandwidth Group from the Group view of a remote assigned to more than 1 Bandwidth Group, left the remote without the VR_0. Fixed in this release.
16
16082 No Statistics Displayed for "App" Nodes When Mode Set to "App Scaled"
Fixed the problem where there were no records displayed for the "App" nodes in the QoS statistics when the QoS mode was set to "App Scaled. Corrected in this release.
17
18
Known Issues
This section lists all known issues that you can encounter in iDS release 8.0.2.7. These issues are grouped into the following categories: Data Path (Protocol Processor, Hub Line Card, Remote, NMS Server) NMS/Reporting (Client applicationsiBuilder, iMonitor, NMS Server)
19
16281 Changing from Roaming to Stationary Prevents Remotes Coming into Network
There is an issue that occurs after adding a new remote to a network, configuring it as roaming, then changing it back to stationary mode. When examining the generated Options file, the [ANTENNA] group is still present. The continued presence of these options causes the remote to mute, and consequently the remote fails to come into network. Work-around: When changing remotes from mobile to stationary, follow the steps below to manually unselect the configured reflector before applying changes: 1. Change the remote from mobile to stationary in the Geo Location tab of the remote Modify screen. a. Right-click the remote and select the Geo Location tab. b. Click on Stationary and enter the Latitude and Longitude values. 2. Select any non-controllable antenna type available in the Reflector field on the VSAT tab, or change the reflector to be non-controllable.
20
NMS/Reporting Issues
15662 iBuilderDelete Option Disabled with Owned Property at PP Level for VNO System Super User
In iBuilder, after logging in as the System Super User the Delete option is disabled when right-clicking a blade for the VNO System Super User (with Owned permission at protocol processor level). However, the blade can be deleted by clicking the Remove button (which is enabled) after making the following selection: Modify Configuration object PP>Blades tab Logically, if a user has the rights to delete the blade, the Delete option should be enabled after right-clicking the blade. Work-around: Use the Modify Protocol Processor screen to delete the blade if needed.
15758 iBuilderDisplay Issue In Details View When Moving Multiple Remotes Across Inroute Groups
When multiple remotes are selected in the "Details view" and moved to a different Inroute Group (IG), the "Details window" gets to display those remotes as if they are still under the original IG. No issues in the tree view, where remotes are displayed under the destination IG. However, in the Details view, moving away from the IG and then coming back, the remotes are gone from the original IG and are correctly displayed under the destination IG. Work-around: Select any other node in the tree view. Go back to the IG from where the remotes were moved. Now, the "Details view" does not display those remotes.
21
16064 SNMP Proxy - Undetermined Strings In Response To Gets Causes Some SNMP Managers To Output Garbage
There is a problem when obtaining NetModem serial numbers which are not null terminated. When performing a query for latency on a specific modem using its serial number, the results contain unterminated strings. Many SNMP managers are not able to handle such unterminated strings and will output garbage data as a consequence.
22
Installation Instructions
This section contains: Prerequisites for iDS 8.0.2.7 Installation Downloading Required Files for Release 8.0.2.7 Special Notices for iDS 8.0.2.7 Upgrades
23
CAUTION: All support for NetModem II+ remotes and NetModem II+ Universal Line Cards has been removed in this release. If you are using these remotes or line cards in your network, you cannot upgrade to this release.
Note: The iBuilder GUI still displays option selections for NetModem II+ Universal Line Cards. However, selecting these options has no effect.
24
25