Unable to access Storefront through NetScaler Gateway and getting ” Could reach the page ” error.

– After upgrading to 12.0 build 58.15 , unable to access the Storefront server through NetScaler Gateway and getting ” Could reach the page ” error.

NOTE: On NetScaler Gateway Session profile, the Storefront URL is configured with Storefront Load balancing server IP.

– If Storefront Load balancer IP is replaced with Actual Storefront Server IP, then Storefront is accessible through NetScaler gateway.

In the following nstrace screenshot, we could see that the Storefront Load balancer has sent Export cipher in the Server Hello. For which, we could see a FATAL Error message from NetScaler gateway Vserver.

User-added image

Related:

  • No Related Posts

NS12.0 add cluster node, node sync stuck in “IN PROGRESS” state

Synchronization stuck due to new added node cannot establish TCP Connection to CCO.

in ns.log, you may see the following logs for this problem.

Enable debug log on Netscaler through System>Auditing>Syslog settings, You can get more detailed logs about the synchronization process.

Refer log pattern:

cat /var/log/ns.log |grep cluster

Jul 11 15:13:00 <local0.info> ns [1510]: cld_fullsync_req_handler(): Received config sync START message from Clusterd (sync_id=2)

Jul 11 15:13:00 <local0.info> ns [22327]: cfsync_pullcfg_n_apply(): Connection failed [Could not connect to any of master nodes provided in sync start message from clusterd]

Jul 11 15:13:00 <local0.info> ns [22327]: cld_fullsync_req_handler(): Sync FAILURE sent to clusterd for sync_id=2

Jul 11 15:13:00 <local0.info> 172.16.1.73 07/11/2018:07:13:00 GMT 2-PPE-2 : default CLUSTERD Message 1394 1531293180485406 : “REC: status FAILURE from client CFSYNCD for ID 2 “

cfsync_pullcfg_n_apply(): Connection failed [Could not connect to any of master nodes provided in sync start message from clusterd]

After check, customer found it was caused by backplane switch jumbo frame setting.

Related:

  • No Related Posts

SRM 4.0.1 Block ChargebackSP: Chargeback by Group doesn’t show all the groups

Article Number: 493197 Article Version: 2 Article Type: Break Fix



ViPR SRM,ViPR SRM 4.0,ViPR SRM 4.0.1

Customer couldn’t see any data under chargeback by group report. We have created several groups using Group Management UI -> Block Chargeback Grouping, but the metrics devtype=UserDefinedGroup are not created

Metrics coming from the passive host discovery were pushed to the Load Balancer Arbiter, and not the Load Balancer Collector

the filter PTF-GROUP-Tagging is set to skip on the LBA (default config) so the metrics cannot be tagged with the nodegrp property

The nodgrp property gets tagged on the metrics coming from the PassiveHost discovery.

Reconfigure the CISCO Solution Pack to send the data to the Load Balancer Collector (localhost)

Step 1: Go to SRM GUI >> centralized-management>> SolutionPacks >> Infrastructure >> Cisco MDS/Nexus Switch >>then open Data collection component

User-added image

Step 2: expand the Data Collection >> validate the Hostname or IP address to send data to localhost.

User-added image

Step 3. Click reconfigured button to save the change.

Step 4: when it has been reconfigured. Please waiting the Chargeback block task run completed. The task will run at 12:00AM every day.

Related:

  • No Related Posts

Error: “HTTP/1.1 Internal Server Error 43554” When Logging to NetScaler

>> NetScaler Gateway vserver is configured, while getting error “http:// internal service error”

>> Verified the configuration on NetScaler the address in published application was not correct. Correct the address.

Web Browsers –>Web Interface Address: https:<Ip or FQDN of SF Server>/citrix/<StoreName> Receiver: Web Interface Address: https:<Ip or FQDN of SF Server>

>> Also check the policy hit command the session profile policy is also getting hit.

nsconmsg -d current -g pol_hits

>> Created the new test gateway server on the storefront server.

>>Storefront address was incorrect in Session profile.

You can traverse to Session Profile by following this path,

NetScaler Gateway > Virtual Servers > Edit virtual server > Session Policies > Select Session Policy and Click Edit Session Profile > Published Applications > Web Interface Address > Edit the address to the correct one.

Example Configuration,

User-added image

Related:

  • No Related Posts

Response Rule: unable to send “Destination” information to the syslog or mail notification

I need a solution

We have created a response rule to send the incident notification to the Syslog server and over an e-mail as well. This working well, however, it does not send the Destination (to which file was uploaded or transferred). 

Below are the variables used in the response rule: (however, I tried with each and every “Insert Variable” but no luck)

Incident ID: $INCIDENT_ID$
File Name: $FILE_NAME$
File Full Path: $PATH$
Subject: $SUBJECT$
Machine Name: $ENDPOINT_MACHINE$
Sender: $SENDER$
Recipients: $RECIPIENTS$
Severity: $SEVERITY$
Match Count: $MATCH_COUNT$
Protocol: $PROTOCOL$
Policy Name: $POLICY$
Policy Rules: $RULES$
Destination: $TARGET$

Is it achievable and how?

0

Related:

  • No Related Posts

“No Syslog box in the dropdown options”.configuring VNX block only array to send logs to syslog server

Article Number: 483920 Article Version: 3 Article Type: Break Fix



Unisphere for VNX

Customer could not get past step 2c in the attached document.

It was determined that they did not have a host agent installed on the appliance or workstation that they wanted to use as the syslog server. (It was also confirmed that they could not install a Host agent on the server due to security considerations.)

Install the appropriate host agent on the syslog server.

You can find the host agent with the following search:

Here’s a link with additional instructions:

https://support.emc.com/search/

Type in Unisphere Host Agent in the (Scope by Product) search box, leave ‘All support’ default in the ‘Scope by resource’ box and most importantly, click on the ‘Advanced Options’ tab over on the lower right. (otherwise a completely different and larger list will populate in findings as it doesn’t do a ‘full text’ search.)

search page screenshot

This search can be modified to find either Windows specific or Unix and other OS versions of the host agents as well. Here are some of the common ones:

ie;

Unisphere Host Agent for Windows 32 and 64-bit

Unisphere Host Agent (Linux x64)

Unisphere Host Agent for Linux x86

Unisphere Host Agent (Solaris x64)

Unisphere Host Agent (Solaris SPARC)

Unisphere Host Agent for AIX

Unisphere Host Agent for HP-UX

*Note: Purposely I left out the version number in all of these, and tested search functionality and they all pull up the latest and older versions of each type.

On a block only array, a host agent must be installed on the syslog server.


>> Here’s a questionnaire that you can provide to customer to determine their set up status:

1. Do you have a Host agent installed on the system (workstation) that you are going to be using as the Centralized Monitor station?

2. What is the Host agent type and version?

3. What is the OS and version on the Portal system or workstation (or VNX array) that you have designated?

4. Have you added the Portal IP address(es) to the Host Agent config file?

5. Could you verify that the other systems or workstations that you expect to see in the Available systems dropdown are not already functioning as portals? Can you also verify that they are running Unisphere for Windows?

6. *If* you are using VNX as the portal, do you have more than 20 hosts attached to the array? Note: the attached document states -> IMPORTANT: Do not use as a portal a VNX system that has more than 20 attached hosts.

.

Related:

  • No Related Posts

Re: VNX Traps(alert) Properties

The MIB for VNX Block is already installed on both storage processors.

To enable it/set up SNMP responses, be sure the Single Notification for Multiple Events check box is not selected in the Action for events field on the General response tab.

In the systems drop-down list on the menu bar, select a storage system.

2. Select System > Monitoring and Alerts > Notifications for Block > Notification Templates.

3. Right-click the template for which you want to set up SNMP responses and select Properties.

4. Click SNMP.

5. In SNMP Management Host, type the IP address of the third-party enterprise-management application that you want to receive SNMP traps.

6. Click Test to test this response.

7. Click OK to close the Template dialog box

The VNX MIB, by default, does not contain every trap. This is because EMC allows you to customize the notification method for each event that occurs.

https://support.emc.com/kb/463389 Where can I find the Management Information Base (MIB) file for my CLARiiON or VNX storage system?

https://support.emc.com/media48612_How_to_use_SNMP_on_VNX.mp4?language=en_US

https://support.emc.com/docu41454_Configuring_Events_and_Notifications_on_VNX_for_File.pdf?language=en_US

https://support.emc.com/docu41522_Using-SNMPv3-on-VNX.pdf?language=en_US

glen

Related:

  • No Related Posts

Monitor Solution – What suite?

I need a solution

Hi All,

Can anyone confirm what suite the montioring solution is part of? We currently have asset management and the Client management. I dont think I can use monitoring solution with just these two.

If thats the case, is it possible to safely add it to my environment as a trial to see how it works? Remove afterwards if we dont need it? Looking at replacing nimsoft with it if displays similiar information.

Thanks!

0

1527501547

Related:

  • No Related Posts

Re: SNMP Trap when failure recovered

Hello guys,

I’m testing SNMP function of Scaleio Gateway software(v2.0.0.2) with 3node cluster.

According to User Guide document(p.530), Scaleio gateway sends a SNMP trap when system failure has been fixed.

>Open and closing alerts will consist of the same code and issue number, with the

>exception of the first digit (0 or 1) in the <ISSUE> section. For example:

> SIOXX.XX.0XXXXXX indicates that the alert is active

> SIOXX.XX.1XXXXXX indicates that the alert has been closed

I’ve rebooted Secondary MDM to test the function above.

I had expected the trap contains “SIO02.01.1000001″ would be send by gateway after cluster recovered, but it wasn’t.

Is it normal behavior? If so, do I have to any setting or configuring to activate the function to send trap after failure recovered?

#please see packet capture log below:

————————————

tcpdump -i eth0 -T snmp -s 0 “(dst port 162) or (src port 161) or (dst port161)”

[Before reboot MDM2]

10:41:23.734093 IP [SIO-GATEWAY].38650 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222765000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

[After MDM2 shutdown]

10:41:53.734020 IP [SIO-GATEWAY].36025 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222768000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

10:41:53.734251 IP [SIO-GATEWAY].36025 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222768000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=5 E:1139.101.1.2=”MDM.MDM_Cluster.MDM_Not_Clustered” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO02.01.0000001″

[During MDM2 rebooting]

10:45:23.733943 IP [SIO-GATEWAY].59254 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222789000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

10:45:23.734308 IP [SIO-GATEWAY].59254 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222789000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=5 E:1139.101.1.2=”MDM.MDM_Cluster.MDM_Not_Clustered” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO02.01.0000001″

[After MDM2 rebooted]

10:45:53.734101 IP [SIO-GATEWAY].57034 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222792000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

10:46:23.734032 IP [SIO-GATEWAY].52960 > [SNMP-RCV].snmptrap: V2Trap(188) system.sysUpTime.0=222795000 S:1.1.4.1.0=E:1139.101.1 E:1139.101.1.1=3 E:1139.101.1.2=”System.License.Trial_License_Used” E:1139.101.1.3=”[MDM1-id]” E:1139.101.1.4=”SIO01.02.0000003″

————————————

*: “…” means repeating.

Regards,

Ichiro

Related:

  • No Related Posts