If Applied Epic will bring up the RightSignature page there is a Switch User button in the top right.
If Applied Epic is giving the document exceeded error, go to Account > API > Manage 3rd Parties and revoke the API access for Applied Epic.
Then Applied Epic requests the user to enter new RightSignature credentials when they send a document.
Wireless Access Points going offline after initial configuration
This can be caused if you are using a PoE enabled switch and have manually set the power on the ports to a maximum of less than a certain wattage depending on access points used. Below is a list of the APX access points and their maximum used power ratings:
In addition to the maximum power ratings that could be configured on the PoE switch, below are the supported PoE types:
This article describes the steps to resolve the issue of the access points failing to power up after initial configuration is sent to it.
The following sections are covered:
Applies to the following Sophos products and versions
Sophos UTM
Sophos Firewall
Sophos Central Wireless
We recommend using a separate PoE injector to see if the problem is power from the switch. If using a separate PoE injector fixes the problem, then you will need to investigate the power supplied to the unit via your PoE enabled switch and ensure it is set to a value that supports the APX device in use.
Sign up to the Sophos Support SMS Notification Service to get the latest product release information and critical issues.
If you’ve spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.
This is invaluable to us to ensure that we continually strive to give our customers the best information possible.
Broker agent Won’t start, crashing after power outtage on network switch.
Exception:
System.Management.ManagementException Invalid class
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at Citrix.MetaInstaller.CoreUtilities.IsVirtualMachine(VMType type)
at Citrix.MetaInstaller.MetaInstallerApplication.Run(String[] args)
at Citrix.MetaInstaller.MetaInstallerApplication.InstallResultMain(String[] args)
Application: BrokerAgent.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Citrix.Cds.PluginLoader.PluginProxy.StartPlugin()
at Citrix.Cds.PluginLoader.PluginProxy.StartPlugin()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()
Faulting application name: BrokerAgent.exe, version: 7.1.0.4019, time stamp: 0x5255694d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
Exception code: 0xe0434352
Fault offset: 0x000000000000940d
Faulting process id: 0x1988
Faulting application start time: 0x01d019c5969618fd
Faulting application path: C:Program FilesCitrixVirtual Desktop AgentBrokerAgent.exe
Faulting module path: C:Windowssystem32KERNELBASE.dll
Report Id: d5d91837-85b8-11e4-86a5-b499babae614
Hi SJRWMD,
I’m not an engineer, but I’m looking into this from a documentation perspective. This switch has changed a couple of times since Unity came out, so because it could depend on your OE, I’d recommend running the -h option on /prot/snap create to get the correct info.
I believe the switch should be -replicateSnap and you should drop the “yes” after it.
/prot/snap create [ -async ] -source <value> [ -name <value> ] [ -descr <value> ] [ -access { ckpt | share } ] [ { -keepFor <value> | -allowAutoDelete { yes | no } } ] [ -replicateSnap [ { -keepSameAsSource | -keepRemotelyFor <value> | -allowRemoteAutoDelete { yes | no } } ] ]
Hopefully I can confirm this shortly with Engineering and get the document updated for our next release.
Thanks,
Holly
| Article Number: 500152 | Article Version: 3 | Article Type: Break Fix |
Data Computing Appliance V2,Data Computing Appliance V3,Data Computing Appliance V1
DCA V1/V2/V3: Dial Home Code 14.12008,14.12009,14.12010, 14.13001 and 14.13007
The following table shows the switch related error codes and their description:
Error code Description14.12008 Switch Thermal Status14.12009 Switch power supply status 114.12010 Switch power supply status 2 14.13001 Status errors from switch sensors: Fans / Power Supplies / Thermal.14.13007 Arista switch sensors: Fans
Need to ‘ssh‘ onto the correct Component. For example: ssh admin@a-sw-1
Run the following commands to collect the logs:
How do I verify the output?
[root@mdw ~]# ssh admin@a-sw-1i-sw-1#show environment allSystem temperature status is: Ok Alert CriticalSensor Description Temperature Threshold Threshold------- ------------------------------------ ------------- ---------- ----------1 Cpu temp sensor 31.622C 95C 100C2 Rear temp sensor 25.750C 55C 65C3 Board temp sensor 33.000C 65C 75C4 Front-panel temp sensor 33.000C 65C 75C5 Trident Bottom Right Outer 35.744C 100C 110C6 Trident Bottom Left Outer 35.744C 100C 110C7 Trident Top Left Outer 35.744C 100C 110C8 Trident Top Right Outer 34.117C 100C 110C9 Trident Bottom Right Inner 39.541C 100C 110C10 Trident Bottom Left Inner 35.744C 100C 110C11 Trident Top Left Inner 34.659C 100C 110C12 Trident Top Right Inner 36.829C 100C 110CSystem cooling status is: OkAmbient temperature: 25CAirflow: back-to-frontFan Tray Status Speed-------------- --------------- ------1 Ok 65%2 Ok 65%3 Ok 65%4 Ok 65%PowerSupply1 Ok 65%PowerSupply2 Ok 65%Power Input Output OutputSupply Model Capacity Current Current Power Status------- -------------------- --------- -------- -------- -------- -------------1 PWR-460AC-R 460W 0.36A 4.75A 55.0W Ok2 PWR-460AC-R 460W 0.28A 3.38A 37.0W Oki-sw-1#
i-sw-1#show environment temperature detailTempSensor1 - Cpu temp sensor Current State Count Last Change Temperature 32.127C Max Temperature 57.890C 663 days, 22:09:16 ago Alert False 0 neverTempSensor2 - Rear temp sensor Current State Count Last Change Temperature 26.000C Max Temperature 31.000C 485 days, 17:22:37 ago Alert False 0 neverTempSensor3 - Board temp sensor Current State Count Last Change Temperature 33.000C Max Temperature 38.000C 39 days, 17:20:26 ago Alert True 2003765 0:02:56 agoTempSensor4 - Front-panel temp sensor Current State Count Last Change Temperature 33.000C Max Temperature 38.000C 485 days, 17:06:28 ago Alert False 0 neverTempSensor5 - Trident Bottom Right Outer Current State Count Last Change Temperature 35.202C Max Temperature Unknown never Alert False 0 neverTempSensor6 - Trident Bottom Left Outer Current State Count Last Change Temperature 35.744C Max Temperature Unknown never Alert False 0 neverTempSensor7 - Trident Top Left Outer Current State Count Last Change Temperature 35.744C Max Temperature Unknown never Alert False 0 neverTempSensor8 - Trident Top Right Outer Current State Count Last Change Temperature 33.574C Max Temperature Unknown never Alert False 0 neverTempSensor9 - Trident Bottom Right Inner Current State Count Last Change Temperature 38.998C Max Temperature Unknown never Alert False 0 neverTempSensor10 - Trident Bottom Left Inner Current State Count Last Change Temperature 36.286C Max Temperature Unknown never Alert False 0 neverTempSensor11 - Trident Top Left Inner Current State Count Last Change Temperature 34.659C Max Temperature Unknown never Alert False 0 neverTempSensor12 - Trident Top Right Inner Current State Count Last Change Temperature 36.829C Max Temperature Unknown never Alert False 0 neveri-sw-1#
i-sw-1#show uptime 12:30:48 up 819 days, 7:03, 1 user, load average: 0.02, 0.03, 0.00
i-sw-1#i-sw-1#show versionArista DCS-7050S-52-RHardware version: 01.03Serial number: JxxxxxxxxxxSystem MAC address: 001c.xxxx.xxxxSoftware image version: 4.9.8.1Architecture: i386Internal build version: 4.9.8.1-1271700.EOS498Internal build ID: db78ef10-50a8-40a5-8ec1-xxxxxxxxUptime: 117 weeks, 0 days, 7 hours and 3 minutesTotal memory: 4030776 kBFree memory: 2512992 kBi-sw-1#
From the above output its clear that the alert is false, as we can see the all the temperatures, Power supplies and cooling devices are ok.
If the temperatures,Power supplies and cooling devices are ok then the issue can be considered recovered for that component.
If there is anything abnormal, take the following steps before escalating the case:
If you have any questions or concerns please open a Service Request with DELL EMC SUPPORT and provide the data found and reference this article.
| Article Number: 497178 | Article Version: 5 | Article Type: Break Fix |
XtremIO Family,XtremIO X2,XtremIO HW X2-S,XtremIO X2-R,XtremIO X2-R Encrypt Disable,XtremIO X2-S Encrypt Disable,XtremIO HW X2-T Encrypt Disable,XtremIO HW X2-T
The following alerts are triggered for fan and fan module failures of the InfiniBand (IB) switch:
| Alert Name | Symptom Code | Description |
| ibswitch_fan_module1_one_fan_failed | XTR1401402 | One Fan in Fan Module1 has failed |
| ibswitch_fan_module1_failed | XTR1401403 | Fan Module1 of the IB Switch has failed |
| ibswitch_fan_module2_one_fan_failed | XTR1401502 | One Fan in Fan Module2 has failed |
| ibswitch_fan_module2_failed | XTR1401503 | Fan Module2 of the IB Switch has failed |
| ibswitch_fan_module3_one_fan_failed | XTR1401602 | One Fan in Fan Module3 has failed |
| ibswitch_fan_module3_failed | XTR1401603 | Fan Module3 of the IB Switch has failed |
| ibswitch_fan_module4_one_fan_failed | XTR1401702 | One Fan in Fan Module4 has failed |
| ibswitch_fan_module4_failed | XTR1401703 | Fan Module4 of the IB Switch has failed |
An occurrence of the above alert should be addressed as soon as possible, since multiple fan failures within an IB switch will cause the entire switch to fail.
The alerts in this article are triggered in case of individual fan or fan module failure(s) within an IB switch.
Note: Resolution of this issue may require XtremIO Global Technical Support to dispatch a field engineer to the site
An automatic Dell EMC Global Services Service Request (SR) will be generated for the symptom codes of this article, if the cluster is configured to Dial Home.
| Article Number: 482186 | Article Version: 3 | Article Type: How To |
Isilon Switch QLOGIC 48-PORT QDR SWITCH 12800-040,Isilon Switch QLOGIC 48-PORT QDR SWITCH 12800-120,Isilon Switches
When installing or upgrading the hardware on the EMC Intel 12800 Infiniband (IB) Isilon Switch, the following tips and guidelines should be reviewed. Please review this entire article before doing any work on an EMC Intel 12800 Infiniband Switch.
For further detailed information, please refer to the Intel-supplied “True Scale Fabric Switches 12000 Series” documentation package. These can be found on the Intel documentation site.
INFORMATION ABOUT POWER SUPPLIES
The number of power supplies required depends on the number of switch ports installed. For each power supply supplied and present in the IB switch, a power cord must be installed in the corresponding power inlet. For the 12800 switches, make certain that the DC ON/OFF switch is illuminated. If it is not, press the button to supply power.
The following guideline should be considered when upgrading and installing the Switch:
Model 12800-040 (up to 96 IB ports): Minimum 2 power supplies required.
Model 12800-120 (up to 288 IB ports): Minimum 3 power supplies required. Power supplies required for AC redundancy = 4.
Example: If you have 97 IB ports, you should consider having 4 active power supplies installed.
If you need more information about power, please consult Appendix A of the TrueScale 12000 Hardware Installation Guide.
INFORMATION ABOUT THE MANAGEMENT MODEL
All True Scale switch models can take a maximum of 2 Management modules. Important to note, is that BEFORE power-up and after install in the customer rack, the following steps must be controlled and completed.
A management module (MM) installed in a 12800 system system normally has a label which protects the mechanical release latch (MRL) switch inside the MM from shock and vibration during shipping. This label must be removed after install in the customer rack and BEFORE power-on (otherwise the management module will not correctly initialize and activate).
To remove the protective label, do the following:
1. Disengage the thumb ***** and partially rotate the lever.
2. Peel off and remove the protective label.
3. Re-engage the lever and tighten the thumb *****. The MRL LED should be GREEN when the MRL thumbscrew is secured to the serial-Ethernet-chassis-EEPROM (SEEB) board, as shown in the image below.
INFORMATION CONSIDERATIONS DURING INSTALLATION AND HARDWARE UPGRADE
FANS
1. It is recommended that the intake fan side is installed towards the cold aisle.
2. It is recommended that the exhaust fan side is installed towards the hot aisle.
Whether or not exhaust fans are present are dependent on the IB switch model.
Model 12800-040 (up to 96 IB ports): 4 Intake and 0 Exhaust fans will be present.
Model 12800-120 (up to 288 IB ports): 5 intake and 3 exhaust fans will be present.
If you need more information about fans, please consult Appendix A of the TrueScale 12000 Hardware Installation Guide.
To determine whether you have an intake or an exhaust fan, please consider the following image and information:
MANAGEMENT MODULE and LEAF RELATIONSHIP
The minimum requirement for each switch is one leaf module per management module. This leaf must be installed in the corresponding management leaf slot. In a dual management module EMC-supplied switch, leaf modules are supplied in management slots L101 and L102.
Power ON the switch ONLY AFTER making sure the MRL is correctly engaged.
LEAF MODULES AND INSTALLATION
18 or 24-port leaf modules are available. Leafs are added from bottom to top, and left to right. Leafs can be added on-line. To install the leaf, remove the supplied protective cover from the switch and simply push the leaf module in place.
In the diagram below, the correct LEAF INSTALLATION process would be to populate Slot 101, then Slot 102, then Slot 103, then Slot 104, and so on, filling the chassis up and then right. Follow this method for leaf installation until all Leaf Modules are installed. In the diagram below, a spine Module is shown in Slot 105.
It is always recommended to verify that the hardware installation has succeeded. The recommendation is to connect to the Switch Chassis Viewer WEBUI, as follows:
Default IP of Isilon IB Switches: 192.168.100.9
Most customers will not have the IB switch on the customer LAN. If the customer has connected the IB switch to the LAN, ask the network adminstrator to provide connectivity. The standard method will be that the on-site Engineer will connect to a RJ-45 Management Port on the Switch Management Module using a standard Cat 5 Ethernet cable.
1. Connect to the WEBUI
Open a browser window and connect to IP 192.168.100.9:
User login name: admin
User Password: adminpass
The Chassis Viewer home page is displayed. All modules should be present.
2. Connect via SSH and control Firmware Version
Open PuTTY or your preferred SSH client and connect to IP 192.168.100.9.
User login name: admin
User password: adminpass
switchPrompt> fwVersion
(Verify the customer firmware level.). This should be 7.2.x. If not, follow How to upgrade firmware on Intel (QLogic) 12300 and 12800 InfiniBand switches to update the firmware.
MODULE LED INFORMATION
Below is general LED information. The above-mentioned Hardware Installation Guide provides more details about the LEDs.
Leaf Module LEDs:
| Article Number: 495817 | Article Version: 2 | Article Type: Break Fix |
Connectrix – M-Series,Connectrix MDS-9250i,Connectrix MDS-Series Firmware 6.X 6.2(11c)
Description:
Missing FCIP information in show tech-support details on mds 9250i switch.
Symptom:
MDS 9250i show tech-support details with ‘feature fcip’ does not provide fcip information.
Conditions:
MDS 9250i with feature “fcip” configured.
Further Problem Description:
Known Affected Release: 6.2(13)
The “show tech-support details” on an MDS-9250i with ‘feature fcip’ does not get the below fcip outputs:
`show ips stats tcp all`
`show ips stats errors all`
‘show fcip profile`
`show fcip profile all`
The MDS-9250i switch is hit by the Cisco BUG: CSCuw48990.
Workaround:
Need to gather the below logs to get the fcip information :
# show tech-support fcip
Resolution:
The switch should be upgraded to NX-OS 6.2(15) and above.
| Article Number: 488738 | Article Version: 2 | Article Type: Break Fix |
Connectrix MDS-Series Firmware 6.X,Connectrix MDS-9148S,Connectrix MDS-9396S
Issue 1: Device manager gui shows an amber light for fan in the display of the switch status lights.
Issue 2: switch log is showing all fans good status under show environment:
Fan:
——————————————————
Fan Model Hw Status
——————————————————
ChassisFan1 FAN Module 1 — Ok
ChassisFan2 FAN Module 2 — Ok
ChassisFan3 FAN Module 3 — Ok
ChassisFan4 FAN Module 4 — Ok
Fan_in_PS1 — — Ok
Fan_in_PS2 — — Ok
Fan Air Filter : NotSupported
Issue 3: seems this may have been triggered by power supply failures initially as the PS has fan as well.
show logging log:
2016 Jun 24 20:02:16 copsw2B %PLATFORM-5-PS_FOUND: Power supply 1 found (Serial number QCS20012LSY)
2016 Jun 24 20:02:16 copsw2B %PLATFORM-2-PS_OK: Power supply 1 ok (Serial number QCS20012LSY)
2016 Jun 24 20:02:16 copsw2B %PLATFORM-5-PS_STATUS: PowerSupply 1 current-status is PS_OK
2016 Jun 24 20:02:17 copsw2B %PLATFORM-2-PS_FANOK: Fan in Power supply 1 ok
2016 Jun 24 20:07:58 copsw2B %PLATFORM-5-PS_STATUS: PowerSupply 2 current-status is PS_FAIL
2016 Jun 24 20:07:58 copsw2B %PLATFORM-2-PS_FAIL: Power supply 2 failed or shut down (Serial number QCS20012LHY)
2016 Jun 24 20:07:59 copsw2B %PLATFORM-2-PS_FANFAIL: Fan in Power supply 2 failed
2016 Jun 24 20:08:26 copsw2B %PLATFORM-5-PS_FOUND: Power supply 2 found (Serial number QCS20012LHY)
2016 Jun 24 20:08:26 copsw2B %PLATFORM-2-PS_OK: Power supply 2 ok (Serial number QCS20012LHY)
2016 Jun 24 20:08:26 copsw2B %PLATFORM-5-PS_STATUS: PowerSupply 2 current-status is PS_OK
2016 Jun 24 20:08:27 copsw2B %PLATFORM-2-PS_FANOK: Fan in Power supply 2 ok
Appears to be Cisco bug CSCur74325 in code below 6.2.13a.
no changes made, issue was seen in device manager at multiple versions.
Fix:
Upgrade 9148s/9396s switches to nx-os 6.2.13a or higher.
Workaround:
Ignore the amber status for fan in Device manager on 9148 switches below NX-OS 6.2.13a. it is a cosmetic issue. check fan status in switch cli with the following command:
show environment.
Hi, I have upgraded DCS from version 6.6.1 to 6.7.3. While running version 6.6.1, I could generate/create reports from the DCS java console. Now that I have upgraded to version 6.7.3, the reports are blank. Is anyone else experiencing this issue or is it just me? Please assist as I pull these reports on a monthly basis.
This is how I run these reports:
1. Open the DCS java console with a ” -csp” switch so that I can have the reports tab.
2. Reports >> Reports >> Then generate my reports. (It comes out blank)
When I run from Reports >> Queries >> Then the queries run with no issues and I can see results.
Thanks in advanced for your help.
MabundaG