Professional Documents
Culture Documents
0
GA Release Notes v1.0
Document History
Document Title
Summary of Changes
Publication Date
Initial version
Contents
Product Overview................................................................................................................................................... 4
Brocade Network Advisor Version 12.2.0 .............................................................................................................. 4
Key Feature Enhancements .................................................................................................................................... 4
Incremental Hardware/Firmware Support ............................................................................................................. 4
Migrations & Upgrades ............................................................................................................................................ 4
Operating Systems Supported ................................................................................................................................ 5
JRE Support .............................................................................................................................................................. 6
Device Platform & Hardware Support Requirements ............................................................................................ 6
Installing Network Advisor ..................................................................................................................................... 9
To install Network Advisor on Windows (Server) .................................................................................................. 10
To install Network Advisor on Linux (Server) ........................................................................................................ 10
To launch the Network Advisor Client ................................................................................................................... 10
Important SAN Notes ........................................................................................................................................... 11
Important IP Notes .............................................................................................................................................. 14
Common Issues for SAN and IP ........................................................................................................................... 15
Patch Installer troubleshooting ............................................................................................................................. 16
Performance Statistics Counters - Calculation Formulae ................................................................................... 17
SMI Agent ............................................................................................................................................................ 19
Logging for CIMOM ................................................................................................................................................ 19
Service Location Protocol (SLP) support .............................................................................................................. 20
Documentation Updates ..................................................................................................................................... 22
Enhancements (RFEs) in Network Advisor 12.2.0 ............................................................................................... 23
Defects ................................................................................................................................................................ 23
Open Defects in Brocade Network Advisor 12.2.0 .............................................................................................. 23
Closed with Code Change in Brocade Network Advisor 12.2.0 .......................................................................... 32
Closed without Code Change in Brocade Network Advisor 12.2.0 ..................................................................... 40
Product Overview
Brocade Network Advisor greatly simplifies daily operations while improving the performance and reliability of
the overall Storage Area Network (SAN) and IP networking environment. Brocade Network Advisor unifies under
a single platform, full lifecycle network management for SAN, LAN and converged networks. Brocade Network
Advisor provides a consistent user experience, across the entire Brocade portfolio of switches, routers and
adapters. This network management tool offers flexible and proactive SAN/IP network performance analysis in
addition to IP network configuration change deployment and monitoring for compliance. Brocade Network
Advisor supports Fibre Channel SANs, including 16 Gbps platforms, Layer 2/3 IP networks (including those
running Brocade VCS Fabric technology), wireless networks, application delivery networks, and Multiprotocol
Label Switching (MPLS) networks for service providers.
Brocade Network Advisor can reduce operation expenditures and help organizations focus on strategic IT
initiatives by providing a common network management tool for provisioning, monitoring, reporting and
troubleshooting. Brocade Network Advisor provides customizable health and performance dashboards, with an
easy-to-use graphical user interface and comprehensive features that automate repetitive tasks. With Brocade
Network Advisor, storage and network administrators can proactively manage their SAN/IP network
environments to support non-stop networking. BNA also provides network administrators the ability to quickly
access network topology, health and performance data required to troubleshoot and remediate network
issues.
Network OS v4.1.0
VDX6740T-1G
VDX 8770 Modules: 6X100G, 27X40G, 48X10G Base-T
2X10G Management Module for SX800 and SX1600 Chassis
vRouter 5400 v6.6
ICX6680, ICX7750-48C, ICX7750-29Q
Fast Iron firmware v8.0.1
Note 1: Enterprise and Professional Plus editions are not supported on 32-bit servers. To migrate Enterprise
and Professional editions to a 64-bit server, refer to Pre-migration requirements when migrating from one
server to another section of the Installation and Migration Guide.
Note 2: Direction migration from pre-12.0.x releases to 12.2.0 is not supported. Refer to Table 29 from
Installation and Migration Guide for migration paths from DCFM, INM and Network Advisor 12.2.X or earlier
releases.
Note 3: Refer to Table 31 from Installation and Migration Guide for SMI Agent only migration paths
Note 4: SAN users may add IP management to Network Advisor 12.2.0 for SAN+IP network management with
the procurement of the IP functionality. Also, IP users may add SAN management to Network Advisor 12.2.0 for
SAN+IP network management with the procurement of the SAN functionality.
Operating Systems (64-bit) / Architecture (Supported for SAN, IP, and SAN+IP)
Note: All the above Operating Systems are supported as Guest VMs on VMware ESXi 5.5, KVM (RedHat
Enterprise Linux 6.3/6.4 Adv) and Microsoft Hyper-V (Hyper-V Server 2008 R2 SP1, Windows Server 2012)
Browser Support
Internet Explorer 10
Firefox 23
JRE Support
Network Advisor version
11.2.0
JRE 1.6u24
11.2.1
JRE 1.6u26
11.3.0, 12.0.0
JRE 1.6u33
12.0.1
JRE 1.7u11
12.0.2
JRE 1.7u17
JRE 1.7u25
JRE 1.7u45
12.2.0
JRE 1.7u51
Note: Web Tools launch from Network Advisor is also supported for the above combinations.
Network OS v4.1.0
Network OS v4.0.0 & v4.0.1
Network OS v3.0.0, v3.0.0a, v3.0.0b,
v3.0.1, v3.0.1a
Network OS v2.11 , v2.1.1, v2.1.1a,
v2.1.1b, v2.1.2a
2.7.02x, 2.7.03x, 2.8.x, 2.9.x
Device Type
7.1.x, 7.2.x
7.1.x, 7.2.x, 7.3.x, 7.4.x
7.1.x, 7.2.x, 7.3.x, 7.4.x, 8.0.x
7.1.x, 7.2.x, 7.3.x, 7.4.x, 8.0.x
7.3.x, 7.4.x, 8.0.x
7.4.x, 8.0.x
7.5a
Brocade 6650
Operating System
Device Type
ServerIron ADX
ServerIron
TurboIron 24X
Wireless Controllers - RFS 4000, RFS 6000, RFS 7000
4.1.x , 4.1.01x
FastIron FES
v6.6
Footnotes:
1 Network
212.1.0f
Footnotes:
1 Requires
3 Requires
Adapters Types
1.1, 2.1.1.0, 2.0, 2.2, 3.0, 3.1,
3.2
Brocade 415,425,815,825
Brocade 8041
Brocade 1010,1020,10072
Brocade 17413
Brocade 18604
Brocade 18675
Footnotes:
1 Requires
v2.1.1.0 or higher
Requires v2.0 or higher
3 Requires v2.2 or higher
4 Requires v3.0 or higher
5 Requires v3.0.3 or higher
2
4.0, 4.1
ESXi
VCenter
Microsoft Windows
Linux
The Network Advisor Server runs as multiple services on Windows and multiple processes on Linux; and they
start automatically after installation.
2.
3.
4.
To launch the Network Advisor Client on the same local machine as the Network Advisor Server,
launch the client as follows:
Windows: Select Start > Programs > Network Advisor 12.2.0 > Network Advisor 12.2.0
Windows:
Launch command prompt and go to the location <Install location>/bin and type dcmclient
Linux:
Launch terminal and go to the location <Install location>/bin and type sh dcmclient
Windows and Linux: Follow the below steps on launching the client from a web browser.
-
To launch the Network Advisor Client from a remote host, launch the client as follows:
Open a browser window and type the Network Advisor server hostname or IP address in the Address
field; for example:
https://NetworkAdvisorServerhost1.companyname.com/
https://192.x.y.z/
If when the Network Advisor server was installed, a Network Advisor web server HTTPS port number
was specified (instead of the default443); you must specify the port number after the hostname or IP
address. In the following examples, 8080 is the web server port number:
https:// NetworkAdvisorServerhost1.companyname.com:8080/
https://192.x.y.z:8080/
Please note that the required Client Oracle JRE version has now changed to 1.7.0_51. For remote clients, this
JRE needs to be installed prior to establishing a server connection.
Note 1 :
Launching element manager applications within Network Advisor Client is done using Java Web Start
technology. This requires the local systems web browser to be able to run Java web start applications. This
setting may have been turned off in the wake of recent Java zero-day vulnerabilities.
10
To turn on Java content in the browser, please follow the below steps:
1. Launch Java Control Panel (refer to http://java.com/en/download/help/win_controlpanel.xml to
locate Java Control Panel application on Windows)
2. In the Java Control Panel, click on the Security tab.
3. Select the check box for Enable Java content in the browser. This will enable the Java plug-in in
the browser.
4. Click Apply. When the Windows User Account Control (UAC) dialog appears, allow permissions to
make the changes. Click OK in the Java Plug-in confirmation window.
5. Now launch Element Manager from BNA client.
Note 2 :
On a Windows server, if only Administrators have access to a drive, windows does not allow Postgres to
create some required directories and a result, migration from a previous version of Network Advisor to a
newer supported version fails. The following steps need to be followed to resolve the issue:
1.
2.
3.
4.
5.
Make sure that the previous version of Network Advisor is up and running.
Right click on the drive where the new version of Network Advisor is intended to be installed (E.g. :D)
Navigate to the Security tab -> Edit -> Add
Add Authenticated Users and give full permission, click Ok
Now install the new version of Network Advisor and start the migration progress.
3. Network Advisor cannot manage an ESXi 5.0 host due to a VMware issue (KB 2012672: SFCB CIMOM
on ESXi 5.0 is incompatible with JRE 1.6 U29 and later). The user is hence required to update to ESXi
5.0 update 1 or later to be able to manage the host in Network Advisor through the host adapter
discovery.
4. If you see the following error message Signature could not be validated during firmware download or
technical support data collection (Fabric OS and Network OS devices only) or configuration
backup/restore (Network OS devices only) using SCP/SFTP, then it could be due to a mismatch in the
signature key used in the ssh handshake between the switch and SCP/SFTP server. Try the following
cli command work-around to address the issue:
11
If the above does not work, go to Server > Options > Software Configuration > FTP/SFTP/SCP, and
uncheck the SCP/SFTP option.
5. The Encryption Smart Card Driver is only supported for 32 bit Linux. It is not supported on 64 bit
Linux.
6. Firmware Download operation on Fabric OS switches fails via SCP/SFTP when trying to upgrade from
FOS v6.3.2b to v6.4.2b4. The workaround is to use the FTP option in BNA to perform the firmware
download operation.
7. Firmware Download operation on Fabric OS switches fails when trying to upgrade from FOS v6.4.2a to
v7.0.2c. The workaround is to use CLI for this operation.
8. Trying to move 200+ ports to a Logical Switch with Reset to Default option selected, results in
operation time-out.
9. During installation, if Network Advisor database initialization fails on windows Operating System, user
needs to verify access to the drive on which the installation is performed. If the user Administrator
alone has access to the drive, then required permissions should also be provided to Authenticated
Users and then continue with the installation.
10. There will be a delay in populating the Gige port details in the Network Advisor client if the server IP is
not registered on the switch to receive SNMP traps from the switch.
11. When the active and defined zone sets have identical zones which differ only by the case of their
names, user will get alerted that the active zone set is different from the defined configuration in the
zone database. The workaround is to edit the identical zone names (for such zones) in defined set, so
that after modification, both zone names are identical in active and defined zone sets.
12. After upgrading to Network Advisor 12.x from 11.x, SSL-based product communication will fail if the
devices have weak authentication certificates. The user will see a 4002 error on attempting to
discover such devices. Devices discovered prior to migration will not be manageable in Network
Advisor after migration. Java 1.7 used by BNA 12.x disables the use of certificates with weak
authentication. The certificates on such devices need to be updated to be compliant with JRE v1.7.
Please refer to the Secure Sockets Layer protocol section of FOS Admin guide for details on updating
certificates.
13. Receive Throughput measure is not updated in Flow Vision dialog.
14. D-port test fails for F-ports with the result as null in the report.
15. In Real Time performance graphs, percentage utilization will fluctuate between 0 100 if a single port
is selected. The workaround is to select more than one port while generating Real Time performance
graphs.
16. Network Advisor uses SNMPv3 by default to discover SAN products. If required, user can select the
Manual option in Discovery dialog and choose SNMPv1 for discovery.
17. Network Advisor uses SNMPv3 by default to discover SAN products. If required, user can select the
Manual option in Discovery dialog and choose SNMPv1 for discovery.
18. On FOS switches running firmware versions v7.2.0 and v7.2.1, if LSAN tags are added or removed
from CLI, the corresponding events are not received by Network Advisor in Master Log. As a result,
adaptive polling is not initiated and the changed tags are updated in Network Advisor after the next
polling cycle.
19. A delay of 5 to 7 minutes is seen when Web Tools is launched on a system (through Network Advisor
or directly in a web browser) where internet access is not available and the network does not return a
destination unreachable message. This issue occurs as Java tries to validate the SSL certificates with
external CAs. This problem can be avoided on such systems by modifying the below Java properties:
On Windows: C:\Users\<logged in
username>\AppData\LocalLow\Sun\Java\Deployment\deployment.properties
On Linux: home/< logged in user name>/.java/deployment/deployment.properties
Brocade Network Advisor 12.2.0 GA Release Notes v1.0
12
In the deployment.properties file, edit the below parameters and set them to false. If these parameters are
not present, add them and save the file. Then re-launch Web tools.
deployment.security.validation.ocsp = false
deployment.security.validation.crl = false
Destination columns are blank for Brocade Encryption Switch in top talkers dialog
When the Top Talkers dialog box is launched for the Brocade Encryption Switch, the columns Destination,
Destination port and Destination switch port are sometimes empty.
13
Ports from a Logical Switch are moved to default Logical Switch through Left Arrow button,
i.e., from (Logical Switches Device Tree) RHS to (Chassis ports Tree/Tree Table) LHS.
When a Logical Switch is deleted - its ports will not be reset to default before moving to
Default Logical Switch before its deletion
Ports which are moved to the default logical switch can be reset to default, if they are moved from (Chassis
ports Tree/Tree Table) LHS to (Logical Switches Device Tree) RHS device tree.
Note 2: Reset ports to default operation will not clear FCIP configurations in the following scenarios:
In 7500 and FR4-18i, VE ports cannot be reset to default unless their corresponding GE ports
are cleared of their FCIP configurations.
In 7800 and FX8-24, GE ports cannot be reset to default unless their corresponding VE ports
are cleared of their FCIP configurations.
Important IP Notes
Miscellaneous Important Notes that Apply to IP Installations
1. Prior to v12.2.0 release, Network Advisor would attempt to discover IP products with default
community strings (public as read community and private as write community) without requiring
this to be configured in Global Settings tab of IP Discovery dialog. However, this could trigger login
attempts failure and could send alarms to Network Administrators if the write community string
configured on the device did not match Network Advisors default write community string (private).
To avoid this issue, starting Network Advisor v12.2.0 release, discovery process will not use
default write community string if it is not configured in Global Settings. User has to explicitly
configure Read-Write community strings in Add Device dialog or Global Settings dialog.
2. Adaptive polling turned off by default for all IP devices (even for migrated servers).
3. SNMP write credentials will not be populated by default for IOS devices.
4. Each IP product has a System max value that can be configured for various parameters, such as
ip-filter-sys for ACLs. Network Advisor deployments do not check whether the payload being
sent to the device has a number greater than the system-max value. In such deployment
scenarios, the deployment may report success even though the number was limited to the systemmax value. To ensure successful deployments, make sure the payload being sent is no greater
than System max value.
5. NOS device configuration backup will only be collected for the following cases:
In case of VCS cluster, Manual Discovery/Rediscovery of the cluster members
CLI manager configuration deployments
6. Syslog messages will not be received for the VDX 8770 that is configured with different IP
addresses for CPs
7. Simplified image upgrade is recommended for NI devices running 5.3 and above.
8. Fixed Form Factor switches running Network OS 4.0 are displayed with Product Type as Router
in Network Advisor, even when they do not have Layer 3 license.
9. When two ports of the same storage are connected to two VDX devices, only of the attached ports
is displayed in the Zoning dialog.
10. On NOS switches, Technical support data collection will fail, if System Time is not set on the
switch. The operation will be in progress for 10 to 20 minutes and eventually fail. Setting System
Time resolves this issue.
11. On VDX devices managed through in band IP address in Network Advisor, firmware download and
configuration backup operations fail.
Brocade Network Advisor 12.2.0 GA Release Notes v1.0
14
12. Cluster IP address does not fall back to the Physical IP address of the Principal node, when the
Virtual IP Address of the cluster is not reachable from Network Advisor.
13. In VLAN Topology view, RSPAN and TLS information associated with Virtual Fabrics is not
displayed. The VLAN Manager dialog displays this information.
15
8. In Linux 64 bit machines, connecting to the database through Open office using ODBC will not work.
Solution is to connect from Windows ODBC Client to the 64 bit Linux machine where Network Advisor
is running to view the Database tables.
9. If you are using the ODBC connection from a remote host to the database, after migrating to 12.0.X,
you will no longer be able to connect from the remote host. If you want to connect from the remote
host, please refer to the Configuring remote client access to the database section in the Installation
and Migration guide.
10. When attempting to install Network Advisor on a Linux Server, if the message Insert New Media is
displayed, the below command needs to be executed from a terminal:
ulimit n 2000
11. Technical Support data collection for discovered Products fails through an external Linux FTP server on
a Windows installation of Network advisor.
12. Client only application can be installed on a machine other than the server (without using a web
browser) by creating a client bundle on the server, then copying and installing that client on another
machine. Refer to Client only installation section of the Installation and Migration guide for details.
13. During installation on a Linux server, if user sets the password for Network Advisor database starting
with a $, installation of the application will fail.
Domestic and International Modem based Call Home is no longer supported for
Brocade Call Home Centers in 12.0 and above
Alternatively, customers using Domestic or International Call Home Modem feature can reconfigure
their Call Home to utilize the Brocade Email option for continued Call Home notifications in the event
of a system problem. Please refer to the Call Home section of the Brocade Network Advisor User
Manual for more configuration details. Note that EFCM and DCFM customers will also be affected by
this change and need to reconfigure their call home to utilize the Brocade Email option for continued
Call Home notifications in the event of a system problem.
During migration, an option will be given to migrate the switches which are configured with these Call
Home centers to Brocade email call home. If you do not have any switches assigned to the Brocade
Domestic and Brocade International call centers, please select No in the config wizard when the
message is displayed.
Note: EMC and IBM Call Home Centers will continue to support Modem Call Home functionality.
16
Installation onto a windows network mounted drive is not supported but install is allowed and DB fails
to start.
Client disconnects
Under heavy server load or degraded network links, there is a potential for Network Advisor client to
get disconnected from the server. Work around is to restart the client.
Cross-flavor Migration
Migrating same version of BNA (12.2.x) from OEM1 version to OEM2 version:
-
v6.2, v7.1
HP VCEM version
v6.2, v7.1
OA firmware
v3.15
Hardware
Servers
HBA
Brocade 804 8Gb FC HBA, Emulex LPe1205HP 8Gb FC HBA, QLogic QMH2562 8Gb FC HBA
17
Counter Name
Type
Protocol
used
Source value
Formula
TX
FC
SNMP
.1.3.6.1.3.94.4.5.1.6
RX
FC
SNMP
.1.3.6.1.3.94.4.5.1.7
TX
GE
SNMP
.1.3.6.1.2.1.31.1.1.1.10
RX
GE
SNMP
.1.3.6.1.2.1.31.1.1.1.6
TX
FCIP
SNMP
.1.3.6.1.2.1.31.1.1.1.10
RX
FCIP
SNMP
.1.3.6.1.2.1.31.1.1.1.6
Uncompressed
Tx/Rx MB/sec
FCIP
SNMP
.1.3.6.1.4.1.1588.4.1.1.6
TX
EE
Monitors
HTTP
RX
EE
Monitors
HTTP
TX
HBA, CNA
HCM API
NA
RX
HBA, CNA
HCM API
NA
TX
TE
SNMP
.1.3.6.1.2.1.31.1.1.1.6
RX
TE
SNMP
.1.3.6.1.2.1.31.1.1.1.10
TX% / RX%
FC, GE,
FCIP, HBA,
CNA
NA
NA
TE
NA
NA
Cumulative
FCIP
.1.3.6.1.4.1.1588.4.1.1.4
18
Compression Ratio
1000
Since for compression ratio we will take
the current compression ratio value
Receive EOF
TE
.1.3.6.1.2.1.16.1.1.1.5
Other Counters
Current
Compression Ratio
NA
NA
(ifHCInOctets + ifHCOutOctets) /
fcipExtendedLinkCompressedBytes.
1) Delta value1: is the difference of value retrieved between the two consecutive poling cycles.
2) Polling interval2 : duration between the two polling cycle in seconds
SMI Agent
1. For BNA that has more than 30K instances (2 MB zones), the CIMOM takes more memory to generate
CIM instances.
If user performs Enumerate Instances or Enumerate Instances Names and total number of size is
more than 2 MB for all managed fabrics, then CIM_ERROR_FAILED will be thrown as the "Total Zone
DB size is more than 2 MB. For such configuration, User need to use Association calls
Note: if the total zone DB is more than 1 MB/more than 10000 instances then user should change
the max jvm heap size to 2048MB to fetch the data without failure in 64 bit machine
2. SMI alert indication BRCD60 is not sent out to SMI clients if Fabric OS switches are discovered but
SNMP trap registration has failed. Ensure that Brocade Network Advisor server is successfully
registered for traps on all switches.
3. If DCB switches are running Fabric OS 6.3.x and 6.3.1_cee, VLAN/ACL deployment through SMI-A will
fail. It is required to upgrade the DCB Fabric OS to 6.4.x/6.3.1_dcb/7.0.X for VLAN/ACL deployment
support through SMI Agent.
19
accepts WBEM requests over HTTP without SSL on TCP port 5988
accepts WBEM requests over HTTPS using SSL on TCP port 5989
slptool commands
Use the following slptool commands to verify whether the SLP is operating properly.
Use this command to verify that the Management application SMI Agent SLP service is properly advertising its
WBEM services.
Example outputs:
service:wbem:https://10.0.1.3:5989,65535
service:wbem:http://10.0.1.3:5988,65535
This output shows the functionalities of Management application SMI Agent:
accepts WBEM requests over HTTP using SSL on TCP port 5989
accepts WBEM requests over HTTP without SSL on TCP port 5988
slptool findattrs service:wbem:http://IP_Address:Port
o Use this command to verify that Management application SMI Agent SLP service is properly
advertising its WBEM SLP template over the HTTP protocol.
o
20
Note: Where IP_Address:Port is the IP address and port number that display when you use the
slptool findsrvs service:wbem command.
Note: Where IP_Address:Port is the IP address and port number that display when you use
the slptool findsrvs service:wbem command.
You can statically register an application that does not dynamically register with SLP using SLPAPIs by
modifying this file. For more information about these files, read the comments contained in them, or refer to
http://www.openslp.org/doc/html/UsersGuide/index.html
Verifying SLP service installation and operation on UNIX systems:
1. Open a command window.
2. Type % su root and press Enter to become the root user.
3. Type # Management_Application/cimom/bin/slptool findsrvs service:service-agent and press Enter to
verify the SLP service is running as a Service Agent (SA).
4. Type # < Management_Application >/cimom/bin/slptool findsrvs service:wbem and press Enter to
verify the SLP service is advertising its WBEM services.
5. Choose one of the following options to verify the SLP service is advertising the WBEM SLP template
over its configured client protocol adapters.
o
Note: Where IP_Address:Port is the IP address and port number that display when you use the slptool
findsrvs service:wbem command.
21
SLP daemonManagement_Application\cimom\cfg\slp.conf
The SLP daemon can be reconfigure the by modifying this file.
SLP registerManagement_Application\cimom\cfg\slp.reg
statically register an application that does not dynamically register with SLP using SLPAPIs by
modifying this file. For more information about these files, read the comments contained in them, or
refer to http://www.openslp.org/doc/html/UsersGuide/index.html
Documentation Updates
Network Advisor Installation and Migration guide refers to Professional Plus Trial license (Tables 1, 26 and
30). This license is no longer valid and reference to this license will be removed in the subsequent version of
Network advisor documentation.
22
Defects
Open Defects in Brocade Network Advisor 12.2.0
This section lists defects with High and Medium Technical Severity open in Network Advisor 12.2.0 as of 4:00
PM on Feb 13, 2014. While these defects are still formally open, they are unlikely to impede Brocade
customers in their deployment of Network Advisor 12.2.0 and have been deferred to a later release.
None of these defects have the requisite combination of probability and severity to cause significant concern
to Brocade customers. Note that when a workaround/recovery to an issue is available, it is provided;
otherwise, no recommended workaround is available at this time.
Defect ID: DEFECT000465401
Technical Severity: Medium
Probability: Medium
Product: Network Advisor
Technology: Fault Management
Reported In Release: Network Advisor12.1.0
Technology Area: Event Actions
Symptom: User cannot receive special handling events
Condition: Issue occurs when event action is configured with policy as frequency bound and action type as
special handling
Brocade Network Advisor 12.2.0 GA Release Notes v1.0
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
Probability: Low
Function: ENHANCEMENT
Service Request ID: 1201238
40
41
42
43
44
45
46
Probability: Low
Function: ENHANCEMENT
Service Request ID: 1201238
47
48