Release Notes Polycom PathNavigator System v7.0.14

Release Notes Polycom® PathNavigator System v7.0.14 Polycom® announces the release of the PathNavigator™ v7.0.14 software, which resolves several cu...
Author: Janis Chapman
1 downloads 2 Views 208KB Size
Release Notes

Polycom® PathNavigator System v7.0.14

Polycom® announces the release of the PathNavigator™ v7.0.14 software, which resolves several customer issues. For more information on these resolved issues, see page 6.

Topics Who Should Install This Release ........................................................................................................... 2  What’s New in This Release .................................................................................................................. 2  Prerequisites .......................................................................................................................................... 2  Interoperability ...................................................................................................................................... 3  Installation and Upgrade Instructions .................................................................................................. 3  Rollback ................................................................................................................................................. 6  Resolved Issues ...................................................................................................................................... 6  Known Issues and Limitations .............................................................................................................. 6  Appendix A: Polycom PathNavigator Operating System Updates ....................................................... 9 

Copyright Information © 2009 Polycom, Inc. All rights reserved. 3725-20335-002E8 (January 2010) Polycom, Inc. 1765 West 121st Avenue Westminster, CO 80234-2301 U.S.A.

Trademark Information Polycom®, the Triangles logo, ReadiManager®, SoundPoint®, SoundStation®, ViaVideo®, VoiceStation®, and Vortex are TM TM TM TM TM registered trademarks of Polycom, Inc. ConveneT , Global Management System , iPower , MGC , People+Content , People TM TM TM TM TM On Content , Polycom Conference Suite , Polycom HD Voice , Polycom PathNavigator , Polycom VideoPlus , Polycom TM TM TM TM TM TM TM TM TM TM VoicePlus , PVX , RAS , ReadiConvene , RMX 2000 , RSS , V2iU , VS4000 , VSX , and VTX are trademarks of Polycom, Inc. Other product and corporate names may be trademarks of other companies and are only used as a fair use reference without intent to infringe.

1

Who Should Install This Release PathNavigator customers who want to implement the fixes listed in Resolved Issues on page 6 should install this release. This release is compatible with a clustered external database configuration.

What’s New in This Release These fixes changed PathNavigator behavior in the following ways: 1.

Enhance the function of the license limiting the max call number.

2.

Remove the restriction for the minimum initial size of PathNavigator DB during installation.

3.

Enhance the function of recording the Network logs or the WAN Link logs when the remote SQL Server is rebooted.

4.

Enhance the function of WAN Link configuration when using internal DB.

5.

Enhance the support for IE7 in WAN Link configuration.

6.

Enhance the stability of PathNavigator with a new ‘MGCAPIdllRel.dll’ file updated.

Prerequisites The system must have: 

Microsoft Windows Server® 2003 Standard Edition operating system with SP1 or SP2



Microsoft Windows 2008 and Microsoft Windows 7 are not supported at this time. 



One of these Microsoft Internet Information Services™ (IIS) web-server software products: Microsoft IIS 4.0 and SP2 or Microsoft IIS 5.0



For an external database, one of these Microsoft SQL Server™ database software products, installed on a server separate from the PathNavigator server: 

Microsoft SQL Server 2005 Standard or Enterprise Edition with SP2 or SP3



Microsoft SQL Server 2000 Standard or Enterprise Edition with SP3



Effective April 8,2008, Microsoft retired mainstream support for Microsoft SQL Server 2000. Microsoft now offers only limited support for the product. We recommend upgrading to Microsoft SQL Server 2005.

2

Interoperability Polycom will support customers running Polycom GMS and PathNavigator applications on supported operating systems in a VMware virtual machine environment. In general, only the current GA version of VMware and the prior major version of VMware are supported. Any exceptions will be noted in product release notes. The customer is responsible for properly configuring their virtual machine and applications for VMware. The customer should review the following documents prior to installing Polycom products in a VMware virtual machine environment: http://www.vmware.com/pdf/vmware_timekeeping.pdf http://support.microsoft.com/kb/897615/en-us Polycom will provide support for Polycom applications running in a VMware virtual environment in an identical manner as with Polycom products running on any other major x86 based systems without initially requiring reproduction of issues on native hardware. Should Polycom suspect that the virtualization layer is the root cause of an incident; the customer will be required to contact the appropriate VMware support provider to resolve the VMware issue. While functional problems have proven to be rare under VMWare, problems related to performance and capacity are much more commonly reported, particularly with enterprise-class applications that recommend highly configured, dedicated systems for deployment. Diagnosis of this class of problem is likely to require the client to disable other applications and virtualized operating system instances which are competing for physical system resources, and possibly to remove the virtualized environment altogether. While Polycom products are expected to function properly in a VMware virtual environment, there may be performance implications which can invalidate Polycom typical sizing and recommendations.

Installation and Upgrade Instructions PathNavigator v7.0.14 is a full installation file, so it does not require an existing PathNavigator 7.0.x installation. PathNavigator v7.0.14 can also be used to upgrade previous PathNavigator releases. Upgrades from v7.0.10.0001, v7.0.11.0100, v7.0.12.0001, v7.0.13.0004 have been tested. To install this release on a standalone (non-redundant) PathNavigator server: 1.

Run the PN7.0.14.0001.exe file and answer the questions for your installation.

2.

If you have a clustered external database, upgrade the database.

3

To install and configure the PathNavigator v7.0.14 redundancy for the first time: 1.

Install this release on the primary PathNavigator as you would for a standalone (nonredundant) server (see above).

2.

Input the redundancy key code into the primary PathNavigator. To do this: a) Log into the primary PathNavigator by using the correct URL: http:///pathnavigator/default.asp b) Go to Configuration > General > License. c)

Click Redundancy Authentication, input the redundancy key code, and click Submit.

3.

Install this release on the redundant PathNavigator as before, but select an installation type of backup, not standalone.

4.

Configure the virtual IP address on the primary PathNavigator. This IP address will be the shared IP for the primary and redundant servers. To do this: a) Log into the primary PathNavigator by using the correct URL: http:///pathnavigator/default.asp b) Go to Configuration > General > Redundant Server. c)

Configure the Endpoints’ gatekeeper IP address, and click Submit.

d) If a warning message window appears, click OK. 5.

Configure the virtual IP address on the redundant PathNavigator. To do this: a) Log into the redundant PathNavigator by using the correct URL: http:///pathnavigator/default.asp b) Go to Configuration > General > Redundant Server. c)

Configure the Endpoints’ gatekeeper IP address, and click Submit.

d) If a warning message window appears, click OK. After the step 5 is finished, the web page will be changed to the Login page automatically, and the URL is changed to be the configured virtual IP address. 6.

Log into PathNavigator.

7.

Go to Configuration > General > Redundant Server, and click Switch Server Role button to verify that redundancy is configured correctly.

8.

Restart both the primary and redundant PathNavigator servers to verify restore the primary and redundant servers to their role. After the both servers restart, the configuration of PathNavigator redundancy is complete. You can manage the both servers from the URL: http:///pathnavigator/default.asp, and the endpoints can register PathNavigator with the virtual IP.

4

To upgrade to this release on both PathNavigator servers in a redundant server configuration system: 1.

On the primary PathNavigator server, run the PN7.0.14.0001.exe and answer the questions for your installation. If a warning message window appears at the end of the upgrade, click OK and then Finish.

2.

On the redundant PathNavigator server, run the PN7.0.14.0001.exe and answer the questions for your installation. If a warning message window appears at the end of the upgrade, click OK and then Finish.

3.

Turn off both PathNavigator servers.

4.

Turn on the primary PathNavigator server.

5.

Turn on the redundant server.

6.

Using a web browser on another node, verify that you can connect to the primary server using the PathNavigator system’s shared IP address or hostname.

7.

If you can’t connect using the shared virtual IP address or hostname, use the physical IP address of the primary server (if SSL is enabled, an “invalid certificate” warning message appears; click Yes to proceed). Navigate to Configuration->Redundant server, check that the Endpoints’ gatekeeper IP address is correct, and click Submit. Then, repeat step 5.

8.

To configure optional security enhancements for the PathNavigator servers, see the PathNavigator User Guide.

To update the virtual IP address for a redundant PathNavigator system: 1.

Login PathNavigator by using the URL: http:///pathnavigator/default.asp.

2.

Go to Configuration > General > Redundant Server.

3.

Input the new IP address in the endpoints’ gatekeeper IP address field, and click Submit.

4.

If a warning message window appears, click OK. The web page will return to the Login page automatically, with the new virtual IP address and the update operation is complete.



These steps to update the virtual IP address work only for this release. To upgrade from Microsoft SQL Server 2000 to Microsoft SQL Server 2005: 1.

Manually stop all PathNavigator services.

2.

Install Microsoft SQL Server 2005 on the database system according to the product documentation.

3.

Start PathNavigator. The Microsoft SQL Server 2005 setup program automatically saves all PathNavigator system data.

5

Rollback To roll back from this release, uninstall (via Control Panel>Add/Remove Programs) the PathNavigator v7.0.14 application and reinstall the previous PathNavigator release.

Resolved Issues Issue

Description

DSTC-69

PathNavigator reports license exceeded when there are no other calls active.

DSTC-132 PathNavigator

reports license exceeded (SR 1-28796779).

DSTC-151

PathNavigator installation failed with 7.00.12 on a Win2003 SP 2 Server and SQL 2005 SP2 Database.

DSTC-210

PathNavigator is not recording WAN Link history.

DSTC-200

WAN Link configuration lost if the PathNavigator server is restarted. This happened only when using internal DB.

SSGPN-154

"Other networks reached through this WAN Link" error with IE7.

DSTC-71

PathNavigator SNMP memory leak alert.

DSTC-182

When using switch server role to test PathNavigator redundancy setup, PathNavigator lost it licensing for some reason. This happened when only in heavy load.

DSTC-204

Memory leak in PLCMMonitorSvc.exe.

Known Issues and Limitations The following two tables list the known issues and limitations in PathNavigator v7.0.13. Issues reported since the release of PathNavigator v7.0.6 Description

Workaround

There is an issue if you install and configure a redundant PathNavigator using the following steps:

Install a redundant PathNavigator system as described

1. Install the primary PathNavigator; 2. Do any configurations on the primary PathNavigator, such as configure the Diagnostic Configuration, or register some endpoints and make a call. These operations make the database not as the default. 3. Install the redundant PathNavigator on another computer; 4. Go to the primary PathNavigator web page, and check the configurations made before. 5. All the configurations made before are gone. That means that the database is changed to be the default again. This bug appears from v7.0.9

6

Issues reported since the release of PathNavigator v7.0.6 Description

Workaround

Export of .CSV file doesn’t work correctly in all scenarios.

Save the file first, and then browse it.

View Logs > Open View Logs > Save locally > When monitoring active calls, there are times when data is scrunched into a few lines, leaving it unreadable.

Refresh the page .

Issues reported in PathNavigator v7.0.5 and earlier (listed alphabetically) Feature

Description

Alias Limitation

The number of aliases per endpoint is limited to 450. If an endpoint registers with more than 450 aliases, this will hinder the ability of PathNavigator to process each registration message to nearly 1/10 of a second. If PathNavigator or a device like a V2IU, which serves as a proxy to PathNavigator for endpoints and therefore contains many aliases, were to reboot then PathNavigator’s performance will be hindered. If PathNavigator were to reboot and the V2IU serves as a proxied registrant, there may be a lag in reboot time for PathNavigator.

Call Forwarding

When a device like a V2IU is deployed as part of the firewall traversal solution, the forwarding feature is not operational from endpoints registered with the V2IU.

Conference On Demand

If the login information is changed on the MGC and PathNavigator is logged in for the Conference On Demand service, PathNavigator remains logged on with the previous login credentials. However, the next time PathNavigator logs back into the MGC (after restarting PathNavigator), it will log in with the new login information.

Forward No Answer

If two endpoints are registered to the same PathNavigator and one of the endpoints has configured a Forward No Answer to an address belonging to an endpoint registered with a neighbor PathNavigator, a call between the two registered endpoints will not connect using the following aliases, E.164 or an H.323 ID. The call between these two registered endpoints can only connect if the forwarded endpoint is physically powered off.

Interoperability Issues

Running BrightStor ARCserve Backup Agent causes the PathNavigator server to become inoperable every few hours.

Logging Directory

The installation program creates a logging directory called \pathnavigator\reports\WanAddr. To properly create the network WAN Link Usage logs this directory needs to be renamed \pathnavigator\reports\WanLink.

Login to Redundant Server

Since the setup of a redundant PathNavigator prompts and requires a password during the initial login, this may result in different passwords between the primary PathNavigator and the redundant PathNavigator. Use of different passwords is likely to cause confusion when logging into the endpoint’s gatekeeper IP address. To circumvent this problem and avoid confusion, it is best to have the same login account for both the primary and redundant PathNavigator servers.

Neighbor Gatekeeper

There is memory leak when placing calls through hierarchical gatekeepers. This occurs if Microsoft Access is the chosen database. A workaround is to use SQL Server database software as PathNavigator’s database.

Netmeeting Participants

When PathNavigator is in Routed Mode, a Netmeeting dial-in participant can only get into an ongoing conference by dialing the MCU service or the MCU's alias. When PathNavigator is in Direct Mode, a Netmeeting dial-in participant can only get into an ongoing conference is by the MCU's IP address. Netmeeting participants cannot dial Conference On Demand.

7

Issues reported in PathNavigator v7.0.5 and earlier (listed alphabetically) Feature

Description

Registration

Intermittently when the ViewStation FX version 5.0 registers to PathNavigator the Use PathNavigator to Dial Multipoint Call selection doesn’t appear in the ViewStation FX Gatekeeper setup screen. This can be fixed by selecting the ViewStation FX from the Monitor > Endpoints list page and clicking Unregister and Yes.

8

Appendix A: Polycom PathNavigator Operating System Updates The Polycom PathNavigator operating system tested was Microsoft Windows Server 2003 R2, Enterprise Edition SP2 with the following updates/patches applied: Security Update (KB924667) Security Update (KB925398) Security Update (KB925902) Security Update (KB926122) Security Update (KB926122) Security Update (KB929123) Security Update (KB930178) Security Update (KB931784) Security Update (KB932168) Security Update (KB933729) Security Update (KB933854) Security Update (KB935839) Security Update (KB935840) Security Update (KB936021) Security Update (KB936782) Security Update (KB938127) Security Update (KB938464) Security Update (KB953839) Security Update (KB941568) Security Update (KB941569) Security Update (KB941644) Security Update (KB941693) Security Update (KB942830) Security Update (KB942831) Security Update (KB943055) Security Update (KB943485) Security Update (KB943460) Security Update (KB944338-v2) Security Update (KB944653) Security Update (KB945553) Security Update (KB946026) Security Update (KB947864) Security Update (KB953838) Security Update (KB948590) Security Update (KB950760) Security Update (KB952954) Security Update (KB950974) Security Update (KB951066) Security Update (KB951698) Security Update (KB951748) Security Update (KB950762) Security Update (KB957095) Security Update (KB956841) Security Update (KB956803)

Security Update (KB958644) Security Update (KB954211) Security Update (KB956391) Security Update (KB955069) Security Update (KB957097) Security Update (KB956390) Security Update (KB958687) Security Update (KB956802) Security Update (KB960714) Security Update (KB952069) Security Update (KB960715) Security Update (KB954600) Security Update (KB958215) Security Update (KB938464-v2) Security Update (KB958690) Security Update (KB960225) Security Update (KB959426) Security Update (KB923561) Security Update (KB952068) Security Update (KB960803) Security Update (KB961373) Security Update (KB956572) Security Update (KB963027) Security Update (KB952004) Security Update (KB968537) Security Update (KB969897) Security Update (KB969898) Security Update (KB970238) Security Update (KB970483) Security Update (KB961501) Update (KB927891) Update (KB936357) Update (KB951072-v2) Update (KB948496) Update (KB955839) Update (KB967715)

9