Reset Search
 

 

Article

While configured to work with vCenter, VDXs crash reporting "Daemon nsm terminated"

« Go Back

Information

 
TitleWhile configured to work with vCenter, VDXs crash reporting "Daemon nsm terminated"
Symptoms
In a VCS configured to work with VMware Center, multiple VDXs crash reporting "Detected termination of process nsm", "Daemon nsm terminated", and "vCenter profile... creation failed :
%%Error : Maximum length of Port Profile Name can be 128 char..
"
Environment
  • VDX6740
  • NOS 7.0.2b, NOS 5.0.1a
  • Logical chassis VCS
  • VCS configured to work with VMware vCenter
  • In vCenter distributed switches (dswitches) are configured with names having non-ASCII Unicode characters.
Cause
vCenter allows the user to enter distributed switch names up to 80 characters long. Each character can be any character in Unicode. When vCenter passes those dswitch names to the VCS, vCenter converts all non-ASCII Unicode and some ASCII symbols into a pure ASCII representation of Unicode. For example, the three character 日本語 (Japanese language) would be converted into the twenty-seven character @e6@97@a5@e6@9c@ac@e8@aa@9e. Some ASCII symbols such as the at mark "@" are also converted in a similar manner so they don't interfere with this encoding. If the single at mark character is used in a dswitch name, vCenter converts it into the three character @40 before handing it off to the VCS. The dollar sign "$", the asterisk "*", and the plus sign "+" are also converted into three character encodings of their ASCII values: @24, @2a, and @2b.

This conversion dramatically increases the length of the string that vCenter passes to the VCS. Depending on the characters used for names, the string that the VCS receives from vCenter can easily end up being much longer than NOS can safely handle.

The VDX NOS 128 character limit on profile names is more than enough when only ASCII letters and numbers are used for distributed switch names in vCenter. When non-ASCII Unicode and some ASCII symbols are used in vCenter for distributed switch names, by the time those names reach the VCS as profile names their encoded forms can be much longer than 128 characters. These overly long profile names trigger the "vCenter profile... creation failed : %%Error : Maximum length of Port Profile Name can be 128 char.." messages and the "Daemon nsm terminated" crashes.
Resolution
The crashes are resolved through a defect found and fixed during the development of NOS 7.4.0. Because it was found and fixed during development, it is not listed in NOS 7.4.0 release notes. After the crashes were found to happen in versions as early as NOS 5.0.1a, the fix was ported in NOS 7.2.0d and documented in NOS 7.2.0d release notes as Parent Defect ID: NOS-67402, Issue ID: NOS-67403. No further patch releases of NOS 7.3.0 are planned. If a user encounters "Daemon nsm terminated" crashes when using non-ASCII Unicode distributed switch names in vCenter, upgrading to NOS 7.2.0d or 7.4.0 or later should prevent the crashes.

However, the maximum length of port profile names does not change in NOS 7.2.0d or 7.4.0. It is still the same 128 characters. Even after upgrading to NOS 7.2.0d or 7.4.0, if non-ASCII Unicode is used in vCenter for dswitch names, the string that vCenter passes to the VCS may be longer than NOS can handle. It is possible that the VCS won't fully recognize it. Even though vCenter allows non-ASCII Unicode for distributed switch names, only ASCII should be used.

As both a workaround and as the safest permanent solution, only ASCII letters, numbers, and unconvertible symbols should be used in vCenter distributed switch names. Letters, numbers, the minus sign "-", and the underbar "_" have been confirmed to be not converted into at-mark encoding by vCenter.
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255