RecoverPoint: XtremIO: Unable to created new snapshots, SRM “RE” failover fails due to unavailable bookmark

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



RecoverPoint,RecoverPoint SE,RecoverPoint Adaptor for VMware Site Recovery Manager,XtremIO

When XtremIO replica copy configured with ‘Number of Desired Snapshots: 2’, customer is unable to create new snapshots while in Test a Copy mode (or Image Access mode) and SRM fail-over operation also fails.


Symptoms found in the logs:

In replication logs on replica copy site:

2016/03/10 16:45:41.866 – #1 – 8747/8560 – XioSnapConsolidation::findBestSnapToDelete: didn’t find user snap to delete …

2016/03/10 16:45:41.866 – #2 – 8747/8560 – XioDistributorHandler::checkSnapDelete: going to delete the latest snapshot!

Affected versions:
All RecoverPoint versions since XtremIO was introduced (4.1.1)

When maximal number of snapshots is 2 the following will happen:

– After the second snapshot is created there are 2 snapshots in snapshot list.

– When the system try to create the 3rd snapshot – it can’t, so snapshot creation is delayed and internal variable indicating number of reserved snapshots is set to 1.

– The system then delete one snapshot and only then will try to create the new one.

– If the pipe is closed before the system handle the delayed request, number of reserved snapshots will remain 1.

From that moment on the system can only hold 1 snapshot at any given moment. So every time a new snapshot is created the previous is deleted.

Workaround:

Increase ‘Number of Desired Snapshots’ for the relevant Consistency Group using RecoverPoint CLI (via config_copy_policy command)

Permanent Fix:
RecoverPoint version 4.4 SP1

Related:

  • No Related Posts

7023182: Linux Replication Fails with Error “TCPSocket::Bind(): Address already in use”

This document (7023182) is provided subject to the disclaimer at the end of this document.

Environment

PlateSpin Migrate 12.0 and up

PlateSpin Forge 11.1 and up

PlateSpin Protect 11.0 and up

Situation

A Linux replication fails with the message ERROR: “TCPSocket::Bind(): Address already in use” at the step sending files stage.

Resolution

There is an existing connection using port 3725 on the source.
On the source run netstat -nlp to find out what connection using data transfer port exists and what its PID is. By default, the data transfer port is 3725.
If the process using the connection over the data transfer port is the ofx controller process, end the process. If another process is using that connection, consider when would be an appropriate time to run the replication or consider changing the data transfer port to a port number that won’t be used.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

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

VIPR SRM: Getting “Error executing handler Read billing file-FileOpener” in The AWS Collector log

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



ViPR SRM 4.0,ViPR SRM 4.0.1

Received the following error in the collector log for the Amazon AWS SolutionPack:

SEVERE – [2016-05-20 09:03:47 EDT] – AbstractStreamHandlerJob::prepareNextStep(): Error executing handler Read billing file-FileOpener com.watch4net.apg.ubertext.parsing.StreamHandlerException: Error while creating the stream for file /opt/APG/Collecting/StreamCollector/amazon-aws-linux/./incoming/150213616981-aws-billingSolutionPack for Amazon AWS Discovering AWS accounts and services 33 detailed-line-items-with-resources-and-tags-2016-05.csv at com.watch4net.apg.ubertext.parsing.retriever.FileReaderRetriever.newFi leToRead(FileReaderRetriever.java:370) at com.watch4net.apg.ubertext.parsing.retriever.FileReaderRetriever.acces s$200(FileReaderRetriever.java:53) at com.watch4net.apg.ubertext.parsing.retriever.FileReaderRetriever $FileOpenerHandler.handleExecution(FileReaderRetriever.java:452) at com.watch4net.apg.ubertext.parsing.concurrent.AbstractStreamHandlerJob .prepareNextStep(AbstractStreamHandlerJob.java:170) at com.watch4net.apg.ubertext.parsing.concurrent.SimpleStreamHandlerJob.s tep(SimpleStreamHandlerJob.java:43) at com.watch4net.apg.concurrent.executor.AbstractJobExecutor $SequentialJob.step(AbstractJobExecutor.java:421) at com.watch4net.apg.concurrent.executor.AbstractJobExecutor.executeJobRu nner(AbstractJobExecutor.java:124) at com.watch4net.apg.concurrent.executor.AbstractJobExecutor.access $500(AbstractJobExecutor.java:24) at com.watch4net.apg.concurrent.executor.AbstractJobExecutor $JobRunnerImpl.run(AbstractJobExecutor.java:276) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.j ava:1142) at java.util.concurrent.ThreadPoolExecutor $Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.FileNotFoundException: /opt/APG/Collecting/StreamCollector/amazon-aws-linux/./incoming/150213616981-aws-billingdetailed-line-items-with-resources-and-tags-2016-05.csv (No such file or directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at com.watch4net.apg.common.io.ActionOnCloseFileInputStream.(Action OnCloseFileInputStream.java:170) at com.watch4net.apg.ubertext.parsing.retriever.FileReaderRetriever.newFi leToRead(FileReaderRetriever.java:363) Error executing handler Read billing file-FileOpener

When the AWS SolutionPack Collector is installed on a separate Linux machine, and the

AWS CLI is not installed on the default path, then the error above might be displayed in

the collection log file.

Since there is no functionality impact due to this error, you can

ignore this exception.

Please see the EMC® ViPR SRM Version 4.0.1 Solution Pack Guide

for more information.

Related:

  • No Related Posts

Error: “Gateway is not Reachable”, Connection Goes Down After the VPN Tunnel is Established

  • Citrix Virtual Adapter is registered as an Ethernet adapter. Starting with Windows 8, the WCMSVC (Windows Connection Manager) disconnects low speed connections because an Ethernet Adapter is seen as more reliable and provides better performance compared to other adapters. That’s the reason, Wi-Fi, 3G/4G adapters get disconnected. But those connections are needed for actual communication with VPN gateway, VPN plugin shows “Gateway is not reachable”.

  • Related:

    • No Related Posts

    Watch4net | EMC M&R 6.8u2 and up – Traffic Flows Solution Pack: “Unknown field type for template” “Template not found” error in EPM logs

    Article Number: 463760 Article Version: 4 Article Type: Break Fix



    Watch4net 6.6, Watch4net 6.4u1, Watch4net 6.4u3, Watch4net 6.5u1, Watch4net 6.5u2, Watch4net 6.5u3, Watch4net 6.5u4, Watch4net 6.6u1



    The following errors might be seen in processing log files when collecting from a device on Netflow v9:

    WARNING — [2016-01-07 04:52:27 PST] — LogMitigator::inc(): Unknown field type for template. Key: ‘[routerSrc=10.xxx.x.xx, sourceId=1, templateId=257, fieldType=346]’, Count: 1000.

    WARNING — [2016-01-07 04:52:27 PST] — LogMitigator::inc(): Unknown field type for template. Key: ‘[routerSrc=10.xxx.x.xx, sourceId=1, templateId=257, fieldType=56701]’, Count: 1000.

    WARNING — [2016-01-07 04:52:27 PST] — LogMitigator::inc(): Unknown field type for template. Key: ‘[routerSrc=10.xxx.x.xx, sourceId=1, templateId=257, fieldType=56702]’, Count: 1000.

    The above errors indicate that field types 346, 56701, and 56702 are not recognized by the Event-Processing-Manager.

    Also, some warnings in newer version of Watch4net contain the following:

    WARNING — [2018-06-29 09:12:08 EDT] — LogMitigator::inc(): Template not found. Key: ‘FlowTemplateId [routerSrc=XX.XXX.XX.XX, sourceId=3203342338, templateId=256]’, Count: 1.

    Traffic Flows Solution Pack is currently designed to accept Netflows v5 templates. Thus when collecting from v9 devices, an unknown template or unknown field type message might be seen in the logs.

    Note: from a support perspective we can do best effort on these issues, but EMC Professional Services might need to be engaged if the error being received is an unknown template error.

    If receiving an unknown field type error as this article describes, the field types should be added in nf9Fields.properties file. A Palo Alto firewall device is used in this example. Searching the vendor’s website for documentation yielded information on the field types that are unknown.

    In this example, the field types are as follows with their corresponding values:

    346=privateEnterpriseNumber

    56701=App-ID

    56702=User-ID

    To add the field types:

    • From centralized-management, select the Event-Processing-Manager server for Traffic Flows
    • Go to Modules > Event-Processing > Flow-Listener::generic-traffic-flow
    • Click Configuration Files and edit nf9Fields.properties
    • Add the field types that were provided by vendor (using Palo Alto in this example):
    # Palo Alto support

    346=privateEnterpriseNumber

    56701=App-ID

    56702=User-ID
    • Go to Modules > Event-Processing > Event-Processing-Manager::generic-traffic-flow
    • Restart the service
    • Check the logs for any similar warnings: Unknown field type for template. If not present, then the data is going through.

    Note: If the Field types are not known, or the Event Processing logs do not contain the data, you need to do the following:

    1) Take a packet capture of the flows which are coming in from the router.

    2) Open the PCAP in wireshark or similar tool look for the templateID# 256

    User-added image

    3) Make sure the “FieldTypes” present in these templates are mapped in the nf9Fields.properties file.

    4) Restart the Traffic Flows EPM.

    5) Verify the EPM logs and make sure the errors are no longer there

    Related:

    • No Related Posts

    Proxy Chaining with Cisco Iron-pot & DLP

    I need a solution

    Hi,

    One of my client want to do chaining proxy with cisco proxy.

    He will create one reflect IP on Cicso and then he will divert all HTTPS traffic to Symantec Proxy, Symantec Proxy will decyrpt SSL traffic and send it to DLP Web prevent by HTTPS over ICAP

    So need to know what changes need to be done apart from below:

    1) SSL Interception on proxy

    2) SSL certficate on Proxy 

    3) Integration with DLP

    Need to know whether we need to import SSL certificate on end User ?

    Since Cisco Proxy will send the traffic from Reflect IP , will proxy able to see end user IP or only reflect IP ?

    0

    Related:

    • No Related Posts

    Getting “ERROR:Operation not permitted. To do this Enable default ssl profile by setting ‘setssl parameter -defaultProfile E’

    – To enable custom ciphers, the Enhanced SSL profile should be configured by enabling the Enhanced Default SSL profile through the command ‘setssl parameter -defaultProfile E’

    – Before enabling Enhanced Default SSL profile through the aforementioned command, as mentioned in the Citrix document, https://docs.citrix.com/en-us/netscaler/11-1/ssl/ssl-profiles1.html, save the current configuration and take a back up of ns.conf.

    NOTE: When the command ‘setssl parameter -defaultProfile E’ is executed,the Enhanced SSL profile settings will override the existing SSL profile settings bound on the Vserver as well as on the Vservice. Hence, take a backup of existing configuration before executing the above command. So that, customer can check the ns.conf and manually edit the SSL profile settings of specific Vserver with required parameters.

    Related:

    • No Related Posts

    Re: Security settings (TLS & Certificates)

    Whilst it is possible, we don’t recommend disabling TLSv1.0/1.1 on ESRS-VE gateways at this stage. The reason being there are still a few products which can only support TLSv1.0 for HTTPS call-home.

    Note that ESRS-VE always uses TLSv1.2 secured connections across the Internet to the ESRS backend. Any TLSv1.0 connections are on the customer internal network between the Dell EMC product and the ESRS gateway.

    Regarding your other question, to change the ESRS WebUI certificate see the following KB article:

    https://support.emc.com/kb/485953

    Kind Regards,

    Marc

    Related:

    • No Related Posts