Wednesday, 28 April 2021

How to Add Report Date to Your Cognos Reports

Note: Here we are using IBM Cognos Analytics 11.1 R5.

This is simple to do.

1) At the top of your report place a Block item.

2) Inside the Block item place two Text items.

3) In the first Text item edit the:
Text Source:
- Text = “Report generated on “

4) In the second Text item edit the:
Text Source:
- Source type = Report expression
- Report expression = ReportDate ()


Image: With second Text item selected


Image: Report expression = ReportDate ()




Sunday, 25 April 2021

Upgrading Cisco Cluster Switches for NetApp ONTAP

NetApp Support Docs & Knowledgebase

First port of call:

NetApp Support Docs & Knowledgebase
https://mysupport.netapp.com/site/docs-and-kb

And on that page there is a link:
Cisco Cluster and Storage Switches

Cisco Cluster and Storage Switches

Check out the button:
Switch Compatibility Matrix
https://mysupport.netapp.com/site/info/cisco-ethernet-switch

Scroll down to the switch type of interest, and determine if your Cisco Cluster Switch needs an upgrade.

For example (data correct as of 25.04.2021):
Nexus 3232C:
Reference Configuration Files
ONTAP 9.3 – 9.8 : Cluster RCF_v1.0
Recommended Cluster NX-OS Versions
ONTAP 9.8, 9.7, 9.6, 9.5 : 9.3(4), 7.0(3)I7(9)
Supported Cluster NX-OS Versions
ONTAP 9.8, 9.7 : 9.3(4), 9.3(3), 9.3(2), 9.2(3), 9.2(2), 9.2(1), 7.0(3)I7(9), 7.0(3)I7(8), 7.0(3)I7(7), 7.0(3)I7(5a)
ONTAP 9.5 : 9.3(4), 9.3(3), 9.3(2), 9.2(3), 9.2(2), 9.2(1), 7.0(3)I7(9), 7.0(3)I7(8), 7.0(3)I7(7), 7.0(3)I7(5a), 7.0(3)I6(1), 7.0(3)I4(1)

Then click the link:
Upgrading ONTAP 9 Cluster Network Switch

Upgrading ONTAP 9 Cluster Network Switch

This is where you're told*:
NetApp customers must register their switch and have a valid CCO ID and contract number in order to install the applicable software for the above Cisco cluster switches.”

*For Cisco Nexus 92300YC, 3232C, 3132Q-V, 5596UP, and 5596T.

And to get the software you must go to:
https://software.cisco.com/download/home

There are various links on the Upgrading 'ONTAP 9 Cluster Network Switch' page, pertaining to relevant Cisco and NetApp documentation for your switch type.

For example:
3232C switches
Product Documentation - Product Library - Cluster, Management and Storage Switches (netapp.com)
https://mysupport.netapp.com/documentation/docweb/index.html?productID=62619
[PDF] Installing NX-OS and Reference Configuration Files (RCFs)
[PDF] Upgrading a Cisco Nexus 3232C Storage* Switch
*Storage switch is not the same as Cluster switch, but the procedure in the PDF is useful reading.
https://www.cisco.com/c/en/us/support/switches/nexus-3000-series-switches/products-release-notes-list.html

Note: The procedure to update the Cisco Cluster switches RCF file is also here:
https://mysupport.netapp.com/site/info/cisco-cluster-sw-instruction

Cisco Software Upgrade and Downgrade Documentation

Depending on what you want, you'll need to google to find the appropriate link.

For example:
Cisco Nexus 3500 Series NX-OS Software Upgrade and Downgrade Guide, Release 9.3(x)
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3548/sw/93x/upgrade/guide/b-cisco-nexus-3500-software-upgrade-downgrade-guide-93x/b-cisco-nexus-3500-software-upgrade-downgrade-guide-93x_chapter_01.html
Note: 3500 Series includes 3000, 3100 and 3500.

Quick Switch CLI Notes from 'Upgrading a Cisco Nexus 3232C Storage Switch'

Installing/upgrading the RCF:

Switch# copy http://172.16.10.1//cfg/Nexus_3232C_RCF_v1.6-Storage.txt bootflash: vrf management
Switch# copy Nexus_3232C_RCF_v1.6-Storage.txt running-config echo-commands
Switch# show running-config
Switch# show banner motd
Switch# copy running-config startup-config

Installing NXOS (Can use FTP, SCP, SFTP - some examples below. The SFTP example will prompt for filename, server, user.):

Switch# ping {YOUR FTP/SCP/SFTP SERVER}

Switch# copy ftp://{YOUR_FTP_SERVER}/nxos.9.3.4.bin bootflash: vrf management
Switch# copy scp://{USER@YOUR_SCP_SERVER}/nxos.9.3.4.bin bootflash: vrf management
Switch# copy sftp: bootflash: vrf management

Switch# show version
Switch# dir bootflash:
Switch# copy running-config startup-config
Switch# show install all impact nxos bootflash:nxos.9.3.4.bin
Switch# install all nxos bootflash:nxos.9.3.4.bin

Switch# show version

The switch should automatically reboot after installing the software. To manually trigger a reboot:

Switch# reload

Also see: https://library.netapp.com/ecm/ecm_download_file/ECMLP2552649


Quick Switch CLI Notes from 'Cisco Cluster Switches Download Instruction'

Procedure to download and install RCFs:

Switch# ping IPADDRESS vrf management
Switch# copy tftp: bootflash: vrf management
Switch# dir bootflash:
Switch# copy bootflash: RCF_name running-config
Switch# show running-config
Switch# copy running-config startup-config

Other Useful Switch CLI Commands

Switch# terminal length 0
Switch# show run
Switch# show start


Saturday, 24 April 2021

Thoughts and Notes on EMC Solutions Enabler (with NetApp OCI)

From a NetApp OnCommand Insight administrators perspective, EMC Solutions Enabler seems like a right ball-ache. When most OCI datasources are simple IP/hostname, username, password, and you're off, affairs; getting EMC Solutions Enabler to work is a lot more effort. Why you cannot have a simple - IP/hostname, username, password - API access to EMC Symmetrix/VMAX/PMAX, I don't know.

Here are some useful notes/links on EMC Solutions Enabler and EMC Solutions Enabler with NetApp OCI:

Configuration

NetApp OnCommand Insight 7.3 Data Source Support Matrix
Check your Symmetrix / VMAX / PMAX is supported.

Dell Technologies: Solutions Enabler 9 Installation and Configuration Guide
Dell Technologies: Solutions Enabler 8 (8.3) Installation and Configuration Guide
For version X Google “solutions enabler X installation and configuration guide”.

NetApp OCI 7.3 Doc Center: EMC Solutions Enabler with SMI-S Performance data source
Mentions:

  • symcfg list
  • EMC Solutions Enabler on the RAU(AU) version must match or be earlier than version on the Solutions Enabler Server.
  • {installdir}\EMC\SYMAPI\config\netcnfg

NetApp OCI 7.2 Docs: EMC Solutions Enabler (CLI) with SMI-S Performance data source
Older documentation version, but still worth a look.

Troubleshooting

NetApp KB: Common EMC Solutions Enabler error messages logged by OnCommand Insight
Also worth doing a search in kb.netapp.com for the issue you are encountering.

NetApp Community: EMC symmetrix array discovery using Solutions Enabler
Mentions:
  • You must define symapi server in /var/symapi/config/netcnfg
  • SYMAPI_SECURE - TCPIP node001 WWW.XXX.YYY.ZZZ 2707 SECURE
  • Solutions Enabler 7.0 introduced SSL only communications (SECURE) by default.
  • SECURE has some annoyances - SE uses mutual certificate authentication, so both the SE host and server need to be able to resolve the other's hostname to an IP.
  • On the sanscreen server, in cmd prompt:
  • set SYMCLI_CONNECT_TYPE=REMOTE_CACHED
  • set SYMCLI_CONNECT=SYMAPI_SERVER
  • From symcli\bin:
  • symcfg list -v

Dell Community: Can't get Solutions Enabler client to connect to my SE appliance
Mentions:
  • nethosts file


Useful Additional Information: SMI-S for Performance

Default settings to configure SMI-S for performance monitoring:

  • IP address or hostname for the array's Solutions Enabler / Remote Solutions Enabler.
  • Provider username. Default = admin
  • Provider password. Default = #1Password
  • Protocol. The default it HTTPS.
  • HTTP port. The default is 5988.
  • HTTPS port. The default is 5989.
  • Interop namespace. The default is: /interop
  • Array namespace: The default is: /root/emc

To test the login you should be able to test the login at:

https://smi-provider-ip:5989/ecomconfig

Notes:

  1. The AU/RAU is not guaranteed to be the SMI-S server you are looking for.
  2. "EMC's SMI-S provider does not scale infinitely - historically it has had device/object limits that mean you can only have 1-3 arrays per SMI-S instance before the SMI-S functionality starts to get janky (their SMI-S implementation is a publishing approach from a statistical standpoint - it is supposed to meet an SLA to publish a new se of statistics every 15 minutes)." (This is why the performance interval is 1000 seconds, no point having less than 900 seconds.)