App Layering: vSphere connector failure ‘Cannot read property ‘root’ of undefined’

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

ShareFile Archiving


Archiving Account Differences

The Archiving feature makes significant changes to the ShareFile main application that prevents files, folders, sent messages and notifications from being deleted from the account for at least 3 years. The items are instead sent to an archive where they can be accessed at a later date, if necessary. This ensures that all communication via ShareFile can be accessed by a Designated Third Party in compliance with SEC rule 17a-4.

When Archiving is enabled on your account all files, folders, sent messages and notifications will be archived instead of deleted. By default the items will be archived for 3 years. This duration can be modified by ShareFile Support.

Items in Pending Archivals can be restored to the account within 7 days or permanently sent to archive.

Certain ShareFile features are not supported on Archiving accounts. Click here to view a list.

How to use Investigative Search

When needed, an internal employee or designated third party can be given access to the InvestigativeSearch menu to access previous files, folders, sent messages and notifications.

Investigative Search can be accessed in the Admin Settings section of your ShareFile account.


Investigative Search Requirements

  1. Employee User
  2. Member of the Super User Group
  3. Granted the Allow this user to run and view archived searches permission.

User-added image

From this menu, you can Schedule a New Search or browse Existing Searches (searches already created on the account).

When creating a new search, provide the terms you wish to search for (or the item ID, if it is known to you), as well as a unique Search Name that you can reference at a later date.

You can search for files, messages, and logs. Logs will display account activity such as uploads or downloads.

You can also limit your search range using the drop-down menu shown below.

User-added image


Once you run a search, it can be found under the tab for Existing Searches. Depending on the size of your account, it may take a few minutes for the search to complete. To view your search results, click on the Name of the search.

User-added image


The results page will allow you to export the data or view additional information on the items. Depending on your search settings, your results may be in the Files, Messages, or Logs tabs.

User-added image


You can view additional information by clicking on the Details button to the right of an item in the search results.You may also download the item from the Details menu.

User-added image

You may use the Run Again or Duplicate options on a completed search.

  • Run Again will repeat the search. The results will appear as a new line item in the Existing Searches tab.
  • Duplicate will bring you to New Search tab with the preferences pre-filled from the existing search. You will then have the option to edit the search before clicking Save and Run Search.



Features that are not supported for Archiving Accounts

  • Share or Send a Folder
  • Edit files
  • Rename files
  • Rename folders
  • Check Out files
  • Add Notes
  • Modify Folder Version Number or Retention Policy
  • Delete files (Archived instead)
  • Sign or Send for Signature via RightSignature
  • Encrypted Email
  • Dynamic Folder Templates
  • File Drops


Additional Info – Drive Mapper Features

Due to the above limitations, accounts with Archiving enabled are currently not able to use the “Create New Folder” button to create new folders in the Windows Explorer window, since this function will first “create” a new folder with the default New Folder folder name, then attempt to “rename” the newly created folder.

Changes to File Version Control

  • Due to the nature of the feature, you cannot set or modify the number of file versions once Archiving has been enabled for your account.
  • The File Versioning menu item will not be present in the Admin or Folder Options sections of your account.
  • Due to the above, you will not have the option of “linking to the latest version of the file” when creating a new Share or Get a Link message.

Related:

  • No Related Posts

Troubleshooting: Common Errors for Chromebook Devices Secured by XenMobile

How do I capture the Secure Hub logs?

To capture the Secure Hub logs you will need to open the extensions dev-tools window:

Go to the extensions page: chrome://extensions

Find the checkbox at the top right of the page labeled “Developer mode” and check it.

On the same page, find the Secure Hub extension.

It should now show a link labeled “background page“, clicking on the link will open a popup dev-tools window.

Sample page below

User-added image

Go the tab labeled “Console

All the logs for the extension are captured here.

Sample page below

User-added image

How can I save the logs?

You can either do “Select all” and copy the logs or right click on the window and click “Save as…” to save the logs to a file.

How are network errors logged?

Any network errors are displayed in Red.

Some of the network level errors from other windows (like “Enrollment” window) may not get logged in the background page. To capture the errors, you’ll have to open the dev-tools for that active window instead and look at its console.

Ex: During enrollment if you see “Network error occurred” in the enrollment window, press (Ctrl+Shift+I) to open the dev-tools for the active window. It can also be opened by right clicking anywhere on the window and then clicking on inspect. In the pop-up dev-tools window, click on the “Console” tab to see more logs.

The actual requests and responses exchanged with the server can be monitored on the Network tab of the dev-tools window.

What are some common errors that might be encountered?

Feature Errors:

403: Feature is not available – Error displayed when the chrome feature is not enable on XenMobile Service

Network errors:

Error Cause Resolution / Workaround
net::ERR_NAME_NOT_RESOLVED DNS resolution issue Verify DNS configuration.
net::ERR_INSECURE_RESPONSE This means the Server certificate is invalid. Usually seen with a XenMobile server that does not have a publicly trusted certificate. To workaround this issue, open the https url in the browser, and manually accept the server’s self signed certificate. (i.e. When you see the warning “Your connection is not private”, click on “ADVANCED” and then click on “Proceed to ..(unsafe)”. You should now be able to go back to the extension and continue enrollment.
net::ERR_FAILED This is usually seen in response to a device checkin request. It usually happens in re-enrollments scenarios where the log out and log in operation was not performed Logging out and logging back in, should fix the issue. After re-login, any open dev-tools windows may have to be closed and re-opened to see the logs again.
net::SSL_CLIENT_AUTH_CERT_NEEDED During device check-in a client cert was not sent. This usually points to a missing or incorrect “auto certificate selection” policy on G-Suite. This can be verified by going to chrome://policy on the Chromebook and search for a policy called “AutoSelectCertficateForUrls” and look at its value.

Related:

  • No Related Posts

NetScaler MAS Troubleshooting Guide

Table of Contents

FAQs During Diagnosis and Troubleshooting of NetScaler MAS Issues Common NetScaler MAS Issues and Troubleshooting Steps

Frequently Asked Questions During Diagnosis and Troubleshooting of NetScaler MAS Issues

The following section lists some of the frequently asked questions during diagnosis and troubleshooting of NetScaler MAS issues:

Q: How to verify the NetScaler MAS build version using CLI and support file?

A: On a live device check the version.conf file under /mps:

bash-2.05b# cat version.conf

11.1-52.15

In support file you can open /var/nslog/dmesg.boot and grep for flash. You should see the build version.

bash-2.05b# grep flash dmesg.boot

/mas-11.1-52.15 -> /flash/mas-11.1-52.15

Back to Top

Q: How does MAS fetch all the dashboard related data from connected devices?

A: MAS does Nitro calls to instances and gets all the details.

To confirm how many vservers each instance has and communicated by NetScaler can be seen in mps_inventory.log:

Wednesday, 22 Mar 17 19:08:02.287 +0530 [Debug] [Emon[#60]] HTTP Request Protocol: https, ContentType: , Method: GET, URL: https://10.107.100.131/nitro/v1/config/lbvserver?attrs=name,ipv46,port,servicetype,effectivestate,curstate,health,tickssincelaststatechange,comment,lbmethod,persistencetype,totalservices,activeservices&pagesize=10000&pageno=1&format=json

Wednesday, 22 Mar 17 19:08:02.371 +0530 [Debug] [Emon[#60]] EMON_LB_VIP: 10.107.100.131, db_objects: 9, new_objects: 8

In the above output you will see differeance in db_objects and new_objects as a vserver was deleted from NetScaler when this call was last made. For performance related dashboard and graphs output look at /var/mps/mps_perf.log

Back to Top

Q: How to capture NetScaler tcpdumps on MAS?

A: Use the following command to capture tcpdumps on MAS:

Tcpdump –i 1 <options>

The switch -i specifies the interface and 1 represents the first interface on the MAS appliance. For further reference please review https://www.freebsd.org/cgi/man.cgi?tcpdump(1)

For example:

tcpdump -i 1 udp and src 10.107.100.131

tcpdump -i 1 tcp

tcpdump -i 1 src NSIP or dst NSIP

Back to Top

Q: How does NetScaler MAS communicate with different devices after adding them?

A: NetScaler MAS periodically communicates through Nitro calls for each and every instance and resource added to it. You can see these calls in mps_inventory.log and mps_config.log

Back to Top

Q: How to upgrade different instances through NetScaler MAS?

A: Complete the following steps to upgrade different instances through NetScaler MAS:

  1. Go to Infrastructure > Configuration Jobs > Maintenance tasks.
  2. Now select the device that you want to upgrade.

Back to Top

Q: How to run techsupport script from CLI of NetScaler MAS?

A: Use the following command to run the techsupport script:

cd /mps/scripts

./techsupport.pl

Back to Top

Q: How to capture effective debug logs to troubleshoot insight related isues?

A: Complete the following steps to capture debug logs:

  1. Whenever you are capturing a support file to troubleshoot an issue, enable ‘Collect Debug logs’ in the tech-support page:

    User-added image

  2. When you enable this, additional debug level afdecoder logs are captured. This will help troubleshoot the issue further.
  3. The time that you will specify is the amount of time these additional debug logs will be captured after clicking on OK.
  4. So if you are troubleshooting HDX insight issue, give a suitable time and click on OK which will start the debugging:

    User-added image

  5. Now replicate the issue within that time interval so that debug logs pertaining to the issue are captured. Support file will automatically be generated after this timer expires.

Back to Top

Q: What are the new features which assists in troubleshooting NetScaler MAS issues?

This is available only from 12.0 onwards.

  • Go to System > Diagnostics > Troubleshooting.
  • You can then select the instance you want to diagnose and get the Diagnostics chart.
  • Remember, only the vservers and instances where AppFlow is enabled will work with this.
  • It will show you different AppFlow related parameters enabled on the device and different vserver states.

User-added image

Back to Top

Q: What are the different processes on NetScaler MAS and how to troubleshoot different issues using mps_*.log in /var/mps/log?

A: The following are the different processes on NetScaler MAS:

  • Control SubSystem (mps_control.log) : Initialize+monitor+stop other subsystems and the database. It is responsible for restarting any subsystem if it crashes.
  • Service SubSystem (mps_service.log) : It has an inbuilt HTTP(s) Request/Response handler. It listens on port 80 and 443. Any request from UI/API will hit the Service SubSystem. Based on the type of request, it might process the request itself or pass it on to the other appropriate SubSystem. Response always goes back via Service SubSystem.
  • Inventory SubSystem (mps_inventory.log) : It does inventory from NetScaler/SD-WAN instances and updates instances’ information in the database. It retrieves build/system information from NetScaler Instances. It runs complete inventory every 30 minutes by default. This subsystem also retrieves statistics from instances to show CPU/Memory usage etc.
  • Config SubSystem (mps_config.log) : It processes any configuration request that is received from Service Process. Configuration request can be adding instance, or any other operations on NetScaler instane or on MAS itself. It is also related to admin user management, device profiles, external authentication server config etc.
  • Event SubSystem (mps_event.log) : It raises internal events in case of any SubSystem failure or configuration changes. This subsystem also registers itself with NetScaler/SD-WAN instances and SDX appliances to receive syslogs and provide event based reporting. All traps and syslogs events come to this process.
  • Perf SubSystem (mps_perf.log) : This subsystem is responsible for performance reporting of NetScaler/SD-WAN instances. This retrieves instance stats every 5 mins and aggregates them on minutely, hourly, daily and weekly basis. There are pre-defined reports.
  • afdecoder SubSystem (mps_afdecoder.log) : This subsystem is responsible to receive AppFlow traffic from NetScaler/SD-WAN instances and process that data.
  • afanalytics SubSystem (mps_afanalytics.log) : This subsystem is responsible for analytics reporting of NetScaler/SD-WAN instances. This subsystem aggregates the data on minutely, hourly, daily and weekly basis. There are pre-defined reports.

Back to Top

Q: How to verify NetScaler MAS configuration using the DB?

A: All the config is stored in a csv files under /var/mps/mpsdb directory.You can open each file and check the config.

Back to Top

Q: What does various NetScaler MAS process states refer to (Output of ‘PS –ax’)?

A: Here are the different values that the s, stat and state output specifiers (header “STAT” or “S”) will display to describe the state of a process:

  • D uninterruptible sleep (usually IO)
  • R running or runnable (on run queue)
  • S interruptible sleep (waiting for an event to complete)
  • T stopped, either by a job control signal or because it is being traced.
  • W paging (not valid since the 2.6.xx kernel)
  • X dead (should never be seen)
  • Z defunct (“zombie”) process, terminated but not reaped by its parent.

For BSD formats and when the stat keyword is used, additional characters may be displayed:

  • < high-priority (not nice to other users)
  • N low-priority (nice to other users)
  • L has pages locked into memory (for real-time and custom IO)
  • s is a session leader
  • l is multi-threaded (using CLONE_THREAD, like NPTL pthreads do)
  • + is in the foreground process group.

Back to Top

Common NetScaler MAS Issues and Troubleshooting Steps

The following section lists some of the most common NetScaler MAS issues and the steps to troubleshoot these issue:

Unable to see all the virtual servers that are present on an instance

  1. Check the licenses for MAS and the virtual servers it supports. You can see that under Infrastructure > Licenses > System Licenses.

    User-added image

  2. Remember the license limit that you see in the above snapshot comprises of all the vservers on the instances including Gateway VIP and GSLB VIP.
  3. Click Modify Licensed Virtual Servers and see if you can find the missing Virtual Server by clicking Add Virtual Servers.

    User-added image

  4. See if you find the missing virtual server there.
  5. You can then go to the above snapshot page again and select the virtual servers you do not need. Then click Mark Unlicensed. You can then replace it with the virtual server that you need.
  6. Alternately, you can go to /var/log/ns.log and try to search for these errors:

    Mar 21 18:22:34 <local0.err> NetScaler MAS-1 mas_event: 10.107.143.118 03/21/2017:12:52:34 GMT : EVENT VIPLICENSELIMITWARNING : 127.0.0.1:VIPLicenses – System discovered more Virtual Servers than license limit, dropping 1 vips

Back to Top

Unable to add instance to NetScaler MAS

  1. You can take a snapshot of the error that you see on GUI when adding an instance.
  2. The following is the flow:

    User-added image

  3. In the collector file you can confirm this by looking at /var/ns.log file.
  4. To understand where the addition failed, examine the /var/mps/mps_Inventory.log and /var/mps/mps_config.log files.
  5. You can also take tcpdump on MAS by using the following command:

    tcpdump -i 1 src NSIP or dst NSIP where NSIP = your NetScaler IP

Back to Top

Service/load balancing state is not shown as DOWN even if that resource is DOWN on NetScaler

  • MAS will only know about the vserver being down when it polls that instance.

    Every 30 minutes, entities are polled by NetScaler MAS by using NITRO calls. An entity is either a policy, virtual server, service, or action attached to a NetScaler instance. While this poling interval is configurable, you cannot set it to less than 10 minutes. To configure it, navigate to Networks > Network Functions > Settings > Configure Polling Interval for Entities. You can also poll the entities configuration when required by navigating to Networks > Network Functions > Load Balancing > Entities Configuration > Poll Now.

    User-added image

  • But you will see the status change in the Application dashboard of MAS. Because it monitors the applications in real time.

    User-added image

  • You will also receive traps for this event and you can see that under Infrastructure > Events > Event Messages.
  • You can see the output of the MAS poll in mps_config.log and mps_inventory.log files.

Back to Top

Cannot see any data on HDX, TCP, Gateway, and Web Insight

The troubleshooting procedure is similar to how you troubleshoot Insight.

  1. Verify if AppFlow is configured on NetScaler vservers. Check if MAS IP is in AppFlow collector list.
  2. Make sure that appropriate AppFlow policies and actions are in place.
  3. Examine mps_afdecoder.log and mps_afanalytics.log under /var/mps/log for any errors.
  4. Verify if traffic is reaching MAS from NetScaler on UDP port 4739. Use tcpdump on MAS to determine this.

Back to Top

Related:

  • No Related Posts

Load Balancing Algorithm Recommended for NetScaler Features Deployed with Hyper-V NIC Teaming

In Hyper-V server, we can combine one or more physical NICs to form a NIC teaming solution and attach it to the NetScaler VPX for bandwidth aggregation and traffic failover to prevent connectivity loss in the event of a network component failure.

This article explains the various load balancing algorithms and Citrix recommendation for some of the NetScaler feature deployed with Hyper-V NIC teaming.

Hyper-V NIC Teaming and Load Balancing Algorithms

Outbound traffic of NIC team can be distributed among the available links in 3 ways using the following load balancing algorithms:

  1. Hyper-V Port
  2. Dynamic
  3. Address hash


User-added image


From the deployment guide of NIC teaming (https://gallery.technet.microsoft.com/windows-server-2012-r2-nic-85aa1318) it is important to note the following facts about each algorithms when used with switch independent NIC Teaming.

Hyper-V port mode

  • Uses single NIC interface from the NIC Team for Ingress and egress traffic distribution of a VM.
  • There is no Source MAC Address changes done by host, peer device always observe the packets from a single mac.
  • This mode limits a single VM to the bandwidth available on single interface of the team.

User-added image

Address Hash mode

  • Creates a hash based on address components of the packet and then assigns packets that have that hash value to one of the available adapters.
  • All special packets including ARP, NetScaler (IPv6 Neighbour Discovery Packets), and ICMP packets are sent on the primary team member.
  • All traffic sent on NICs other than the primary team member are sent with the source MAC address modified to match the NIC on which they are sent.
  • All traffic sent on the primary team member is sent with the original source MAC address (which may be the team’s source MAC address).

User-added image

Dynamic mode

  • Takes the best aspects of each of the other two modes and combines them into a single mode.
  • Outbound loads are distributed based on a hash of the TCP Ports and IP addresses and it also rebalances loads in real time so that a given outbound flow may move back and forth between team members.
  • Every VM is affinitized to a team member. All ARP/NetScaler packets are sent on the team member to which the port is affinitized.
  • Packets sent on the team member that is the affinitized team member have no source MAC address replacement done.
  • Packets sent on a team member other than the affinitized team member will have source MAC address replacement done.


User-added image

Citrix Recommendation

Citrix recommends the underlying load-balancing mode to be Hyper-V port mode when switch Independent NIC teaming is deployed with NetScaler VPX for following features

  1. HA
  2. Cluster
  3. MAC Based Forwarding
  4. MAC mode VServers
  5. Forwarding Sessions configured

This is because Dynamic mode and Address hash mode does source MAC address replacement for the outbound traffic and the peer device receiving the packets sent out of the NIC team interfaces will receive the packets with source MAC of the NIC team interface instead of the sender machine MAC .

Related:

  • No Related Posts

How to Configure GSLB in Active-Passive Mode on NetScaler Appliance

Configuring disaster recovery in an active-passive setup consists of the following tasks.

  • Create the active data center.
    • Add a local GSLB site.
    • Bind the domain to the GSLB virtual server.
    • Add GSLB services and bind the services to active GSLB virtual server.
    • Add a GSLB virtual server, which represents the active data center.
  • Create the passive data center.
    • Add a remote GSLB site.
    • Add GSLB services which represents standby data center and bind the services to the standby GSLB virtual server.
    • Add a GSLB virtual server, which represents standby data center.
    • Designate the standby data center by configuring the standby GSLB virtual server as the backup virtual server for the active GSLB virtual server.


User-added image


To configure GSLB in Active-Passive mode, complete the following procedures:

  1. Configuring Site A as Active GLSB Site

  2. Configuring Site B as Backup GLSB Site

Configuring Site A as Active GLSB Site

Complete the following steps, to configure site A as the active GSLB site:

Note: You can follow the screenshots in this article to configure GSLB using NetScaler GUI.

  1. Run the following command in the command line interface to enable the load balancing and GSLB features:

    enable ns feature LB GSLB

    User-added image

  2. Run the following command to create an authoritative DNS service on the NetScaler MIP or SNIP:

    add service adns_svc 192.168.251.205 adns 53

    User-added image

  3. Run the following commands to create local and remote GSLB site:

    add gslb site sitea 192.168.251.201 -publicIP 192.168.251.201

    add gslb site siteb 192.168.253.201 -publicIP 192.168.253.201

    Note:
    If the type is not specified, the appliance automatically detects and sets the type on the basis of the IP address being assigned to the site. If the specified site IP address is owned by the appliance (for example, a MIP address or SNIP address), the site is a local site. Otherwise, it is a remote site.

    User-added image

    User-added image

  4. Run the following command to add the local GSLB virtual server for HTTP traffic with RTT as the lbmethod:

    add gslb vserver gvserver-a http -lbmethod RTT

    User-added image

    User-added image

  5. Run the following commands to create the local servers and services at site A:

    add service server-a 192.168.152.10 HTTP 80

    User-added image

    Run the following commands to create a virtual server for load balancing:

    add lb vserver vservera HTTP 192.168.251.202 80 -persistenceType NONE -cltTimeout 180

    User-added image

    Run the following commands to bind service-A to load balancing virtual server vservera:

    bind lb vserver vservera server-a

  6. Run the following command to add the GSLB service for the local site A:

    add gslb service gslb-svc-a 192.168.251.202 HTTP 80 -siteName sitea

    bind gslb vserver gvserver-a -serviceName gslb-svc-a

    User-added image

    Note: GSLB service monitoring is not required for a local service, because the load balancing virtual server status is used.

    The local GSLB service should have the same IP address as the load balancing virtual server status added in Step 5.

  7. Run the following command to bind the domain to the primary GSLB virtual server:

    bind gslb vserver gvserver-a -domainName www.example.com

  8. Run the following command to add the remote GSLB virtual server for HTTP traffic with RTT as the lbmethod:

    add gslb vserver gvserver-b HTTP -lbMethod RTT

  9. Run the following commands to add a GSLB service for the remote site B and bind it to the remote GSLB virtual server:

    add gslb service GSLB-svc-b 192.168.253.202 HTTP 80 -publicIP 192.168.253.202 -publicPort 80 -siteName siteb

    bind gslb vserver gvserver-b -serviceName GSLB-svc-b

  10. Run the following command to set up the backup GSLB virtual server:

    set GSLB vserver gvserver-a -backupVServer gvserver-b

    User-added image

Configuring Site B as Backup GLSB Site

Complete the following steps, to configure site B as the backup GSLB site:

  1. Run the following command to enable the load balancing and GSLB features:

    enable ns feature LB GSLB

  2. Run the following command to add an authoritative DNS service on the NetScaler MIP or SNIP:

    add service adns_svc 192.168.253.205 adns 53

  3. Run the following commands to add a remote and local GSLB site:

    add gslb site sitea 192.168.251.201 -publicIP 192.168.251.201

    add gslb site siteb 192.168.253.201 -publicIP 192.168.253.201

  4. Run the following command to add the local GSLB virtual server for HTTP traffic with RTT as the lbmethod:

    add gslb vserver gvserver-b http -lbmethod RTT

  5. Run the following command to add the virtual server for load balancing the servers and services at site B.

    add service server-b 192.168.152.11 HTTP 80

    add lb vserver vserverb HTTP 192.168.253.202 80 -persistenceType NONE –cltTimeout 180

    Bind the service to the virtual server by running the following command:

    bind lb vserver vserverb server-b

  6. Run the following command to add the GSLB service for the local site B:

    add gslb service gslb-svc-b 192.168.253.202 HTTP 80 -siteName siteb

    bind gslb vserver gvserver-b -serviceName gslb-svc-b

    Note: GSLB service monitoring is not required for a local service because the load balancing virtual server status is used. The local GSLB service should have the same IP address as the load balancing virtual server added in Step 5.

  7. Run the following command to add the remote GSLB virtual server for HTTP traffic with RTT as the lbmethod:

    add gslb vserver gvserver-a HTTP -lbMethod RTT

  8. Run the following to add the GSLB service for the remote site A and bind it to the remote GSLB virtual server:

    add gslb service GSLB-svc-a 192.168.251.202 HTTP 80 -siteName sitea

    bind gslb vserver gvserver-a -serviceName GSLB-svc-a

  9. Run the following command to bind the domain to the primary GSLB virtual server:

    bind gslb vserver gvserver-a -domainName www.example.com

  10. Run the following command to set up the backup GSLB virtual server:

    set gslb vserver gvserver-a -backupVServer gvserver-b

Related:

  • No Related Posts

COM Port Redirection: How to map a client COM port to a server COM port

LPT and COM port settings are configurable via Studio in XenApp / XenDesktop 7.9 or newer. In versions 7.0 through 7.8, these settings were only configurable using the registry. For more information, see Port redirection policies in Citrix Documentation.

Client COM port mapping allows devices attached to the COM ports on the user’s endpoint to be used during virtual sessions. These mappings can be used like any other network mappings.

For each COM port, a driver in the OS assigns a symbolic link name such as COM1, COM2, etc, which is then utilized by the applications to access the port.

While most PCs no longer have built-in serial (COM) ports, the ports are easy to add via USB converters.

Beware that even if a device can attach to the endpoint via USB directly does not mean it can be redirected via Generic USB Redirection. Some USB devices function as virtual COM ports, which applications can access in the same way as physical serial port. The OS can abstract COM ports and treat them like fileshares. Two common protocols for virtual COM are CDC ACM or MCT.

(When connected through RS-485 port Applications might not work at all. Get a RS-485-to-RS232 converter to use it as a COM port)

Applications suited for serial ports often involve sensors, controllers, old check readers, pads, etc.

Some USB virtual COM-port devices use vendor-specific drivers in place of the Windows-provided drivers (usbser.sys).

These drivers allow you to force the virtual COM port of the USB device so that it does not change even if connected to different USB sockets. This might be done from Device Manager / Ports (COM & LPT) / Properties, or from the Application itself, that controls the Device.

User-added image

Warning: Some applications will only recognize the Device (e.g. signature pad) consistently if it is connected to COM1 or COM2 on the client workstation.

Related:

  • No Related Posts

Driver Disk for PMC-Sierra aacraid driver v1.2.1-55022 – For XenServer 7.0

Who Should Install this Driver Disk?

Customers running Citrix XenServer 7.0 who use PMC Sierra’s aacraid driver and wish to use the latest version of the following:

Driver Module Version
aacraid 1.2.1.55022

Issues Resolved In this Driver Disk

Includes general enhancements and bug fixes.

Firmware requirements for this Driver Disk

Please ensure that your hardware is running firmware versions greater or equal to the ones specified below, according to the chipset of your particular device:

  • Microsemi Adaptec HBA 1000 Series Host Bus Adapters with Firmware 3.52 [0]
  • Adaptec RAID 8805 with Firmware 33204

Note: If your device has been branded by your OEM, please ensure that you consult them regarding the currently supported driver/firmware versions.

Installing the Driver Disk

Customers should use the XenServer CLI to install this driver disk. Once the driver has been installed, the server must be restarted, in order for the driver to be loaded. As with any software update, Citrix advises customers to back up their data before applying this driver disk.

Please note that the attachment to this article is a zip file. It contains both the drive disk ISO mentioned below, and the source code for the driver. The zip file should be unzipped (to produce the driver disk ISO image), before carrying out the steps below. The source code file is not necessary for driver disk installation: it is provided to fulfill licensing obligations.

The file with filename ending metadata.md5 contains the checksum of the driver disk’s metadata. If, when you install the driver disk, you elect to verify the driver disk when prompted, you should check that the checksum presented by the installer is the same as that in the metadata MD5 checksum file included in this download.

Also present in the zip file is an MD5 checksum for the ISO image named aacraid.iso. This will allow you to verify that your download has been successful. This checksum is of the ISO only, and can be verified by following the instructions at CTX116166: How to verify downloaded ISO images.

Installing as Part of a Clean XenServer Installation

  1. Once you have selected your keyboard layout at the first installer prompt, you will be presented with a welcome screen. At this point, press F9 on your keyboard, and insert the CD with the driver disk in it, or use one of the other methods such as installation over the network.

    Users should note that if installation over HTTP or FTP is to be used, the ISO image must be unpacked at that location (i.e. the installer expects to find the contents of the ISO at that network location, not the ISO itself).

  2. The installer will proceed to attempt to load the driver. If this is successful, you can continue with the installation as normal. Near the end of the installation, you will be prompted to re-insert the driver disk (otherwise known as a XenServer supplemental pack) so that the driver can be installed onto disk. You must re-supply the driver disk at this point. Failure to do so will mean that the installation will not contain the new drivers. After this step, no further action is required.

If the installer fails to load the new driver from the driver disk, it is likely to be because an earlier version of the driver has already been loaded. In general, this is because a hardware component is present that is supported by the version of the driver that ships as part of XenServer (even if another component is present that requires a newer version of the driver). To avoid the existing driver being loaded, use the following procedure.

  1. Reboot the host, leaving the XenServer installation CD-ROM in the drive.
  2. At the boot: prompt, type:

    shell

  3. You will now be presented with a command prompt. Type the following:

    rmmod aacraid

    If this succeeds (i.e. there are no error messages printed),the installer’s versions of the drivers have been unloaded. If error messages are presented, it is likely that other drivers depend on one or more of the drivers you are attempting to unload. If this is the case, please contact Citrix Technical Support.

  4. Type

    exit

    or press Control+D on your keyboard, to return to the installer.

  5. Use the procedure described above to provide the driver disk to the installer, which should now load correctly.

Installing onto a Running XenServer System

  1. Download the driver disk directly to the XenServer host to be updated (Citrix recommends storing it in the /tmp/ directory), or first download the file to an Internet-connected computer, and burn the ISO image to a CD.
  2. Use XenCenter to access the XenServer host’s console, or log in directly using SSH.
  3. Mount the driver disk image. The directory being mounted varies depending on whether the driver disk is still in ISO form, or was burnt to CD. For a CD-ROM, use:

    mkdir -p /mnt/tmp

    mount /dev/<path to cd-rom> /mnt/tmp

    cd /mnt/tmp/

    ./install.sh

    cd /

    umount /mnt/tmp

    If instead, the ISO file is used, the steps are:

    mkdir -p /mnt/tmp

    mount /tmp/<path to ISO> /mnt/tmp -o loop,ro

    cd /mnt/tmp/

    ./install.sh

    cd /

    umount /mnt/tmp

  4. To complete the installation, restart the host. This ensures that the driver loads correctly.

Files

Driver Disk Files

File Name MD5 Checksum
aacraid.iso bdf8c855465804b17906797ef26c6ca6
aacraid.metadata.md5 7cc32babc2d5b40a0efa735f52635268
aacraid-1.2.1.55022-3.zip 8b0f81d8ec75a3969e291ac9ffeabd9a

RPMs Provided

Name Version RPM Name
aacraid-modules 1.2.1.55022 aacraid-modules-1.2.1.55022-3.x86_64.rpm
aacraid-3.10.0+10-modules 1.2.1.55022 aacraid-3.10.0+10-modules-1.2.1.55022-3.x86_64.rpm

More Information

If you experience any difficulties, contact Citrix Technical Support.

For information on how to build driver disks, refer to Citrix XenServer 7.0 Supplemental Packs & the DDK .

Related:

  • No Related Posts

RfWebUI portal theme is causing the following Receiver error: “Your account cannot be added using the server address. Make sure your entered it correctly. You may need to enter your email address instead”

Tradução automática

Эта статья была переведена автоматической системой перевода и не был рассмотрен людьми. Citrix обеспечивает автоматический перевод с целью расширения доступа для поддержки контента; Однако, автоматически переведенные статьи могут может содержать ошибки. Citrix не несет ответственности за несоответствия, ошибки, или повреждения, возникшие в результате использования автоматически переведенных статей.

Related:

  • No Related Posts

Error: The Citrix Desktop Service was refused a connection to the delivery controller ” (IP Address ‘xxx.xxx.xxx.xxx’)

Try to determine which files are taking up disk space. on Identity disk

For access to the junction linked to the Identity Disk volume at C:Program FilesCitrixPvsVmServicePersistedData, you will need to execute the command prompt under the context of the Local System account via PsExec tool

The PsExec tool is available for download at this location

http://docs.microsoft.com/en-us/sysinternals/downloads/psexec

Follow these steps to access the Identity disk volume on the VDA:

1. Open elevated command prompt <Run as administrator>

2. execute the command under the context of the Local System account via PsExec:

PSEXEC -i -s cmd.exe

This it to access to the junction linked to the Identity Disk volume

3. Navigate to the root of the junction “PersistedData”, and execute the following command:

DIR /O:S /S > C:{location}Out.txt

4. Open out.txt using Notepad or text editor

5. Check the files taking up the disk space.

6. Move the unwanted files to an alternate location or delete them

Note: You may see .gpf files which shouldn’t be deleted. BrokerAgent.exe writes changed farm policies to %ProgramData%CitrixPvsAgentLocallyPersistedDataBrokerAgentInfo<GUID>.gpf. BrokerAgent.exe then triggers a policy evaluation via CitrixCseClient.dll.

Related:

  • No Related Posts