NetScaler SDX – Unknown Device, not supported by Command Center


Environment:

  • Citrix NetScaler SDX appliances
  • Citrix Command Centre 5.x (and think it occurs in version 4.x also) on Windows Server 2008 R2

Issue:

While running a NetScaler SDX discovery in Command Centre the discovery fails with the following error message:

“Unknown device ; <sdx_ip_address> ; not supported by command center”

(The discovery of the NetScaler VPX instances discovered fine independently)

– Checked discovery logs and found the below error:

Troubleshooting Steps:

– Checked from the Command Centre server and was able to ping and SSH to SDX Management IP with same credentials used in the Command Centre NetScaler SDX profile.
– In the C:\Program Files (x86)\Citrix\Citrix Command Center\logs\discoveryLogs.txt log file, I could see it was trying to add the NetScaler SDX as “CBSDX” (CloudBridge SDX I assume).

  • INVENTORYERR: Device not recognized as CBSDX. SYSID null <sdx_ip_address>
  • INVENTORYERR: Exception while login to =<sdx_ip_address>
  • Localized : English : nsroot failed to login

Resolution:

Within Command Centre,

  • On the Administration tab,
  • Under Settings,
  • Click SSL Settings and then
  • Select the Enable TLSv1 option
  • Restart the Command Centre service.

NOTE: After restarting the Command Centre service and its running again, it can take a while before your able to log in again.

Check the service status in the C:\Program Files (x86)\Citrix\Citrix Command Center\logs\wrapper.log file

INFO | jvm 1 | 2016/05/23 14:47:00 | Starting up as Primary Server and correcting the Server information in the Database.
INFO | jvm 1 | 2016/05/23 14:47:00 |
INFO | jvm 1 | 2016/05/23 14:47:01 |
INFO | jvm 1 | 2016/05/23 14:47:01 | Starting Citrix Command Center “Primary” Server Modules, please wait
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 |
INFO | jvm 1 | 2016/05/23 14:47:15 | Process : SyslogServerBE [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:16 | Process : ProcessTest [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:17 | Process : ShutdownDatabaseServer [ Started ]
INFO | jvm 1 | 2016/05/23 14:47:19 | Process : CLIRMIService [ Started ]

If you see a lot of [Failed] statues, restart the Command Centre server.

 

Exchange RPC Timeouts when using Citrix NetScaler


Updated 9 June 2016

Environment


Exchange 2010

Citrix NetScaler 10.x/11.x

Issue


  • Users creating a new email and clicking on To: to browse the Global Address List would receive an Exchange timeout error message.
  • Accepting meeting invites puts the appointment in the recpients calendar but not the organisers and no email gets sent to the organiser of the appectance. Takes clicking the Accept button multiple times before it processes the acceptance.

Resolutions


Create a new TCP Profile

GUI:

  • System
  • Profiles
  • Add
  • Name: RPC_Profile
  • MSS: 1460
  • Keep-Alive Probes – Enable
  • Connection idle time before sending probe (secs) – 30
  • Keep-alive probe interval (secs) – 20
  • Everything else defaults

Bind this profile to the RPC Load Balanced VIP

  • Traffic Management
  • Load Balancing
  • Virtual Servers
  • <Exchange RPC LB VIP Name>
  • Profiles > Add
  • TCP Profile – Select RPC_Profile
  • Ok
  • Done

CLI:

add ns tcpProfile RPC_Profile_RPC -mss 1460 -KA ENABLED -KAconnIdleTime 30 -KAprobeInterval 20

add lb vserver <Exchange RPC LB VIP Name> TCP <IP_Address> * -persistenceType SOURCEIP -timeout 150 -cltTimeout 180 -tcpProfileName RPC_Profile

 

Additional Timeout customization recommendations

  • Add ‘Thresholds & Timeouts node to the RPC ServiceGroup
    • Configure ‘Client Idle Time-out’ setting to: 28800
  • Disable AppFlow on the RPC VIP and ServiceGroup
  • Ensure ‘Surge Protection’ is disabled on the RPC ServiceGroup

 

NetScaler 10 – Use Java Console rather than Web Console


Change the URL of the admin console from:

https://{netscaler_IP} /menu/neo

to

https://{netscaler_IP}/menu/guia