DCE 7.4.1 Email alert "from" address not showing

[DCIM_Support]

Hi,

Has anyone come across this before?

DCE 7.4.1(virtual machine) is sending alerts for a symmettra UPS and PDU's.

The PDU's show the "from" address OK. But the UPS from address is blank.

See below emails:

PDU Email Alert

From: DC1-R05-PDU-B [mailto:KGH-DC1-EMS-DCE-Alerts@kgh.nhs.uk]
Sent: 22 February 2017 14:57
To: BackupTeam
Subject: Value Too Low (returned to normal) - Error - Temperature - DC1-R4-PDUB-Temp-Bottom - DC1-R05-PDU-B (192.168.101.30)
Importance: High

Alert Title:	Temperature - DC1-R4-PDUB-Temp-Bottom - value is normal (was too low)
Alert Description:	The value of 'Temperature - DC1-R4-PDUB-Temp-Bottom' was too low, but has now returned to normal.
Alert Type:	Value Too Low
Severity:	Error (returned to normal)
Alert Level:	Return To Normal
Sensor:	Temperature - DC1-R4-PDUB-Temp-Bottom
Sensor Value:	19.9 ° C
Device:	DC1-R05-PDU-B (192.168.101.30)
Time Detected:	02/22/17 02:51:59 pm
Time Returned to Normal:	02/22/17 02:56:56 pm
Notification Time:	02/22/17 02:56:56 pm
Action Name:	ICT Alerts
User-provided Description:	Normal range is (16C-25C)
Location:	KGH-DC1-R5-RearLeft
Notes:	APC Web/SNMP Management Card (MB:v4.1.0 PF:v6.4.6 PN:apc_hw05_aos_646.bin AF1:v6.4.6 AN1:apc_hw05_rpdu2g_646.bin MN:AP8981 HR:02 SN: ZA1534016434 MD:08/21/2015)
Alert ID:	nbErrorCond_69517361
Version:	7.4.1.5

UPS Email Alert

From:
Sent: 22 February 2017 15:35
To: BackupTeam
Subject: Device Alarm - Critical - DC1-UPS01 SN:PD1539150017 (192.168.101.232)
Importance: High

Alert Title:	Input Voltage Or Frequency Cannot Support Bypass
Alert Description:	An input voltage or frequency problem prevents switching to bypass mode. Recommended Action: Correct the input power problem, if possible, or wait for the input power problem to clear. Note: Some UPS systems have settings that allow the UPS to switch to bypass if this status exists when a hardware failure occurs. In such cases, correct the power problem, or shut down the equipment powered by the UPS. For either action, contact APC Support (http://www.apc.com/go/direct/index.cfm?tag=support) for assistance in correcting the internal hardware failure.
Alert Type:	Device Alarm
Severity:	Critical
Alert Level:	ICT Alerts
Device:	DC1-UPS01 SN:PD1539150017 (192.168.101.232)
Time Detected:	02/22/17 03:34:37 pm
Notification Time:	02/22/17 03:34:37 pm
Notification Policy:	KGH-DC1 Monitoring Notification Policy
Action Name:	ICT Alerts
Location:	KGH-DC1
Notes:	APC Web/SNMP Management Card (MB:v4.0.6 PF:v3.7.8 PN:apc_hw03_aos_378.bin AF1:v3.7.7 AN1:apc_hw03_px2_377.bin MN:0G-9354 HR:0C SN: QD1538111140 MD:09/17/2015) (Embedded PowerNet SNMP Agent SW v2.2 compatible)
Alert ID:	nbErrorCond_B30A89A2
Version:	7.4.1.5

Is it because the UPS Device label name has a space character in it(DC1-UPS01 SN:PD1539150017)  and the SMTP server rejects it? I don't currently have the facility to test this on my setup....

Any Help appreciated. Thanks

Bruce

(CID:111939343)

[DCIM_Support]

Hi Bruce Duncanson,

What is UPS name and NMC2 card name in this UPS?

I have also similar bug for a long time and constantly meets under a condition if at a name of the device there are Cyrillic symbols. Especially it is urgent for virtual sensors in my case.

Very thanks for the support.

(CID:111939388)

[DCIM_Support]

Hi,

The UPS name(label) assigned to the UPS is DC1-UPS01 SN:PD1539150017

This is configured in the Identification section of the NMC1 GUI or telnet/putty access.

Note: this is a Symmettra PX 2 with an embedded card. The FW for this is still GEN1

I'm not sure what you mean by NMC2 card name. Please confirm if you can.

I will be changing my hardware setup within the next two weeks which will allow simulation of a VM DCE posting to --> exchange email server -> simulating  ETL devices. I can also test Virtual sensors for your issue. 

If the community has no response I will post my results.

Kind Regards

Bruce

(CID:111939401)

[DCIM_Support]

Hi Bruce Duncanson,

Yes of course I meant the embedded card. FW or DCE version in this case doesn't matter.

I once again rechecked today and I can tell in the affirmative, that the reason is higher specified bug - it is presence of a symbol of a colon ":" at a name of the device or the virtual sensor. Change a colon symbol in name UPS, for example, on a hyphen and everything will be normal.

Despite it, I can't tell in the affirmative, what is a bug of the DCE server. As, in my case, the same e-mails with a colon synbol in a name of the device or a virtual sensor are send both on my local mail server, and on external Internet webmail. And in the latter case, i.e. in external Internet webmail below the described bug isn't visible.

From here the logical question follows: and what you use the SMTP server for send and recive emails?

We, for example, use the internal SMTP server MS Exchange Server, and for viewing of local mail we use MS Outlook. And that's it in such configuration above the described bug is also visible. The question, after all, needs to be addressed on Microsoft Co...

P.S.: I wrote about this bug on local APC techsupport in 2014...

(CID:111939533)

[DCIM_Support]

Hi guys,

I ran a quick test on the colon in a virtual sensor and it seemed to send at least part of the name as the from address:

Subject:	Value Too High - Error - test:colon - test:colon
From:	"colon" me.com>
Date:	Tue, February 28, 2017 2:42 pm

As you can see, I named the virtual sensor test:colon. The From address only used the 2nd half of that name and the "netbotz@me.com" is from the e-mail server configuration from field.

Steve

(CID:112626267)

[DCIM_Support]

...And what from this follows, how you think?

(CID:112626277)

[DCIM_Support]

Well, Since Bruce's e-mail is not showing up at all, I can not say with 100% confidence that I have replicated his issue. This does seem like AN issue and I have put it in as an issue... hopefully they will get to it soon. 
As for Bruce's issue, I would hope that whatever testing he could do on this part would confirm it.

Steve 

(CID:112626303)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.