Topic
  • 3 replies
  • Latest Post - ‏2013-01-23T21:59:17Z by SystemAdmin
SystemAdmin
SystemAdmin
3234 Posts

Pinned topic E-mail over LAN - invalid email address bug?

‏2013-01-11T17:34:56Z |
I am running an H-Series Blade chassis. When configuring the AMM alerts from the GUI (MM Control > Alerts > Remote Alert Recipient 2) the E-Mail address field will not accept my content. My domain name happens to have a dash (-) in it. When attempting to add my address (xyz@my-domainname.com) I get the following error:

"Your request cannot be completed due to the following error(s): Invalid Email address or multiple addresses not separated by commas or semi-colons."

If I remove the dash from the domain name (xyz@thisisnotmydomainname.com) all is well. Not cool. I have updated the firmware to 'BPET62U' and the problem still exists.
Updated on 2013-01-23T21:59:17Z at 2013-01-23T21:59:17Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: E-mail over LAN - invalid email address bug?

    ‏2013-01-11T18:33:08Z  
    Hi,

    its an existing bug. It works with an older version, e.g. BPET62P or the configuration from the CLI.

    Best regards
    >>>Time-to-Flash<<<
    Germany
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: E-mail over LAN - invalid email address bug?

    ‏2013-01-14T23:47:42Z  
    Hi,

    its an existing bug. It works with an older version, e.g. BPET62P or the configuration from the CLI.

    Best regards
    >>>Time-to-Flash<<<
    Germany
    Thanks. Can you provide the CLI command to change this setting?
  • SystemAdmin
    SystemAdmin
    3234 Posts

    Re: E-mail over LAN - invalid email address bug?

    ‏2013-01-23T21:59:17Z  
    Thanks. Can you provide the CLI command to change this setting?
    Hi,

    the CLI reads as follows:

    to configure alert recipient 2 to receive only critical alert notifications by email (),
    while management module 1 is set as the persistent command environment, at the
    system:mm[1]> prompt, type

    Example: To view the configuration for alert recipient 1, while management
    module 1 is set as the persistent command environment, at the system:mm[1]>
    prompt, type
    alertentries -1

    To configure alert recipient 2 to receive only critical alert notifications by email,
    while management module 1 is set as the persistent command environment, at the
    system:mm[1]> prompt, type
    alertentries -2 -n test2 -status on -f critical -t email -e test2@us.ibm.com

    To configure alert recipient 3 to receive all alert notifications through IBM Systems
    Director, while management module 1 is set as the persistent command
    environment, at the system:mm[1]> prompt, type
    alertentries -3 -n test3 -status on -f none -t director -i 192.168.70.140

    To configure alert recipient 4 to receive all alert notifications through SNMP, while
    management module 1 is set as the persistent command environment, at the
    system:mm[1]> prompt, type
    alertentries -4 -n test4 -status on -f none -t snmp
    The following example shows the information that is returned from these
    commands:
    system:mm[1]> alertentries -1
    -status on
    -n test1
    -f critical
    -t email
    -e test1@us.ibm.com
    system:mm[1]> alertentries -2 -n test2 -status on -f critical -t email
    -e test2@us.ibm.com
    OK
    system:mm[1]> alertentries -3 -n test3 -status on -f none -t director
    -i 192.168.70.140
    OK
    system:mm[1]> alertentries -4 -n test4 -status on -f none -t snmp
    OK
    system:mm[1]>

    Best regards
    >>>Time-to-Flash<<<
    Germany