Sign In Help
Schneider Electric
HelpSign In
Schneider Electric Exchange
  • Home
  • Collaborate
  • Develop
  • Shop
Home Collaborate Develop Shop Log in or Register Help

Invite a Co-worker

Send a co-worker an invite to the Exchange portal.Just enter their email address and we’ll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel

Invitation Sent

Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close
  • Home
  • Collaborate
  • Exchange Community
  • :
  • EcoStruxure IT
  • :
  • EcoStruxure IT forum
  • :
  • Rack Monitor Netbotz 250 : Syslog Severity Configuration
Community Menu
  • Forums
    • By Topic
        • EcoStruxure IT
          • EcoStruxure IT forum
        • Industrial Automation
          • Industry Automation and Control Forum
          • Alliance System Integrators Forum
          • Machine Solutions in the Digital Transformation
          • EcoStruxure Automation Expert / IEC 61499 Forum
          • Industrial Edge Computing Forum
          • Level and Pressure Instrumentation Forum
          • Modicon User Group
          • PLC Club Indonesia
          • SEE Automation Club Forum
          • Fabrika ve Makina Otomasyonu Çözümleri
          • Форум по промышленной автоматизации СНГ
        • SCADA & Telemetry Solutions
          • Geo SCADA Expert Forum
          • SCADA and Telemetry Devices Forum
        • Power Distribution IEC
          • Power Distribution and Digital
          • Power Standards & Regulations
          • Paneelbouw & Energie Distributie
          • Eldistribution & Fastighetsautomation
        • Power Distribution Softwares
          • EcoStruxure Power Design Forum
          • SEE Electrical Building+ Forum
          • LayoutFAST User Group Forum
        • Wireless Information Network Solutions
          • Instrument Area Network
          • Remote Monitoring
          • Tank Level Monitoring
          • Remote Data Collection
        • Solutions for your Business
          • Solutions for Food & Beverage Forum
          • Solutions for Healthcare Forum
    • By Segment
        • Food & Beverage
          • Solutions for Food & Beverage Forum
        • Healthcare
          • Solutions for Healthcare Forum
      • EcoStruxure IT
        • EcoStruxure IT forum
      • Industrial Automation
        • Industry Automation and Control Forum
        • Alliance System Integrators Forum
        • Machine Solutions in the Digital Transformation
        • EcoStruxure Automation Expert / IEC 61499 Forum
        • Industrial Edge Computing Forum
        • Level and Pressure Instrumentation Forum
        • Modicon User Group
        • PLC Club Indonesia
        • SEE Automation Club Forum
        • Fabrika ve Makina Otomasyonu Çözümleri
        • Форум по промышленной автоматизации СНГ
      • SCADA & Telemetry Solutions
        • Geo SCADA Expert Forum
        • SCADA and Telemetry Devices Forum
      • Power Distribution IEC
        • Power Distribution and Digital
        • Power Standards & Regulations
        • Paneelbouw & Energie Distributie
        • Eldistribution & Fastighetsautomation
      • Power Distribution Softwares
        • EcoStruxure Power Design Forum
        • SEE Electrical Building+ Forum
        • LayoutFAST User Group Forum
      • Wireless Information Network Solutions
        • Instrument Area Network
        • Remote Monitoring
        • Tank Level Monitoring
        • Remote Data Collection
      • Solutions for your Business
        • Solutions for Food & Beverage Forum
        • Solutions for Healthcare Forum
      • Food & Beverage
        • Solutions for Food & Beverage Forum
      • Healthcare
        • Solutions for Healthcare Forum
  • Blogs
    • By Topic
        • Industrial Automation
          • Industrial Edge Computing Blog
          • Industry 4.0 Blog
          • Industrie du Futur France
        • SCADA & Telemetry Solutions
          • SCADA and Telemetry Blog
        • Power Distribution IEC
          • Power Events & Webinars
          • Power Foundations Blog
        • Power Distribution NEMA
          • NEMA Power Foundations Blog
        • Power Distribution Softwares
          • EcoStruxure Power Design Blog
          • SEE Electrical Building+ Blog
        • Solutions for your Business
          • Solutions for Food & Beverage Blog
          • Solutions for Healthcare Blog
          • Solutions for Retail Blog
        • Community experts & publishers
          • Publishers Community
    • By Segment
        • Food & Beverage
          • Solutions for Food & Beverage Blog
        • Healthcare
          • Solutions for Healthcare Blog
        • Retail
          • Solutions for Retail Blog
      • Industrial Automation
        • Industrial Edge Computing Blog
        • Industry 4.0 Blog
        • Industrie du Futur France
      • SCADA & Telemetry Solutions
        • SCADA and Telemetry Blog
      • Power Distribution IEC
        • Power Events & Webinars
        • Power Foundations Blog
      • Power Distribution NEMA
        • NEMA Power Foundations Blog
      • Power Distribution Softwares
        • EcoStruxure Power Design Blog
        • SEE Electrical Building+ Blog
      • Solutions for your Business
        • Solutions for Food & Beverage Blog
        • Solutions for Healthcare Blog
        • Solutions for Retail Blog
      • Community experts & publishers
        • Publishers Community
      • Food & Beverage
        • Solutions for Food & Beverage Blog
      • Healthcare
        • Solutions for Healthcare Blog
      • Retail
        • Solutions for Retail Blog
  • Ideas
        • Industrial Automation
          • Modicon Ideas & new features
        • SCADA & Telemetry Solutions
          • Geo SCADA Expert Ideas
          • SCADA and Telemetry Devices Ideas
  • Knowledge Center
    • Building Automation Knowledge Base
    • Industrial Automation Knowledge Base
    • Industrial Automation How-to videos
    • SCADA & Telemetry Solutions Knowledge Base
    • Digital E-books
    • Success Stories Corner
    • Power Talks
  • Events & Webinars
    • Innovation Talks
    • Innovation Summit
    • Let's Exchange Series
    • Technology Partners
  • Support
    • Ask Exchange
    • Leaderboard
    • Our Community Guidelines
    • Community User Guide
    • How-To & Best Practices
    • More
Join Now
How can we help?
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
51269members
Join Now
245489posts
Join Now

Rack Monitor Netbotz 250 : Syslog Severity Configuration

Options
  • Subscribe to RSS Feed
  • Mark Topic as New
  • Mark Topic as Read
  • Float this Topic for Current User
  • Bookmark
  • Subscribe
  • Mute
  • Printer Friendly Page
Solved Go to Solution
Back to EcoStruxure IT forum
Solved
rf2019
Lieutenant JG rf2019
Lieutenant JG
‎2020-11-16 03:23 AM
0 Likes
4
457
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2020-11-16 03:23 AM

Rack Monitor Netbotz 250 : Syslog Severity Configuration

Hello,

I am currently working on the Syslog severity of the Rack Monitor NetBotz 250 and after reading the User Manual and the Configuraiton file (.ini), I have questions regarding the Severity level of my syslog.

 

[NetworkSYSLOG]
Syslog=enabled
Facility=User
Server1=0.0.0.0
Server2=0.0.0.0
Server3=0.0.0.0
Server4=0.0.0.0
Port1=514
Port2=514
Port3=514
Port4=514
Protocol1=1
Protocol2=0
Protocol3=0
Protocol4=0
Language1=enUs
Language2=enUs
Language3=enUs
Language4=enUs
SyslogMapCritical=Info
SyslogMapWarning=Warning
SyslogMapInformational=Info

 

What are the differences between SyslogMapCritical, SyslogMapWarning and SyslogMapInformational.

If I want to have a Debugging severity level, where should I input the value ?

 

Thank you in advance.

Best Regards,

 

Raphaël

Solved! Go to Solution.

Labels
  • DDF
  • NetBotz
Tags (1)
  • Tags:
  • english
Share
Reply

Accepted Solutions
Valentin_Kozlov
Lieutenant Valentin_Kozlov Lieutenant
Lieutenant
‎2020-11-17 04:08 AM
1 Like
1
432
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2020-11-17 04:08 AM

Re: Rack Monitor Netbotz 250 : Syslog Severity Configuration

Raphael you may refer to RFC to get more deep Syslog description.

 

Each Syslog message have PRI field which comes after header and means emergency level of the message.

The Priority value is calculated by first multiplying the Facility
   number by 8 and then adding the numerical value of the Severity.  For
   example, a kernel message (Facility=0) with a Severity of Emergency
   (Severity=0) would have a Priority value of 0.  Also, a "local use 4"
   message (Facility=20) with a Severity of Notice (Severity=5) would
   have a Priority value of 165.  In the PRI of a syslog message, these
   values would be placed between the angle brackets as <0> and <165>
   respectively. 

 

I'm not sure what exact Facility code Netbotz use for Syslog messages.

 

Let's imagine that it will "local use 4" as in example above with Facility=20.

 

Then we map our Netbotz messages to Syslog Severity:

 

SyslogMapCritical=Critical

SyslogMapWarning=Warning

SyslogMapInformational=Info

 

As per FRC table

       Numerical         Severity
             Code

              0       Emergency: system is unusable
              1       Alert: action must be taken immediately
              2       Critical: critical conditions
              3       Error: error conditions
              4       Warning: warning conditions
              5       Notice: normal but significant condition
              6       Informational: informational messages
              7       Debug: debug-level messages

 

 

SyslogMapCritical=Critical => 2

SyslogMapWarning=Warning => 4

SyslogMapInformational=Info => 6

 

So you will receive PRIVAL=162 (Facility*8+Severity = 20*8+2) in case of Critical Netbotz alert, PRIVAL=164 (Facility*8+Severity = 20*8+4) in case of Warning alert and PRIVAL=166 (Facility*8+Severity = 20*8+6) for Informational events.

 

Considering this numbers you can work with messages on your Syslog server.

 

If you set

 

SyslogMapCritical=Info => 6

SyslogMapWarning=Info => 6

SyslogMapInformational=Info => 6

 

All messages from Netbotz will have equal priority level PRIVAL=166 (Facility*8+Severity = 20*8+6) for syslog server.

 

If you would like to receive Debugging severity level for all events from Netbotz, you should set this level for all alert types^

SyslogMapCritical=Debug

SyslogMapWarning=Debug

SyslogMapInformational=Debug

 

 

See Answer In Context

Tags (1)
  • Tags:
  • english
Share
Reply
  • All forum topics
  • Previous Topic
  • Next Topic
4 Replies 4
Valentin_Kozlov
Lieutenant Valentin_Kozlov Lieutenant
Lieutenant
‎2020-11-17 12:11 AM
0 Likes
3
441
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2020-11-17 12:11 AM

Re: Rack Monitor Netbotz 250 : Syslog Severity Configuration

Hi Raphael!

 

Netbotz have three levels of severity - Informational, Warning and Critical.

In described section you can map Netboz levels to desired Syslog levels.

 

As per RFC3164 there are eight levels:

        Numerical         Severity
          Code

           0       Emergency: system is unusable
           1       Alert: action must be taken immediately
           2       Critical: critical conditions
           3       Error: error conditions
           4       Warning: warning conditions
           5       Notice: normal but significant condition
           6       Informational: informational messages
           7       Debug: debug-level messages

 

In your example when Netbotz register Warning alarm, you will receive syslog message with "warning" severity level, in other two cases you will receive messages with  "informational" severity level.

 

It is just a way to prioritize messages from Netboz on your Syslog server.

 

You will not receive more detailed message if you set "debug" level there.

Tags (1)
  • Tags:
  • english
Share
Reply
rf2019
Lieutenant JG rf2019
Lieutenant JG
‎2020-11-17 01:54 AM
0 Likes
2
436
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2020-11-17 01:54 AM

Re: Rack Monitor Netbotz 250 : Syslog Severity Configuration

Hi Valentin,

Thank you for your reply.

I understand that there are only three severity level for the NetBotz.

However, I still have difficulties to understand what the three parameters are about:

  • SyslogMapCritical
  • SyslogMapWarning
  • SyslogMapInformational

 

Thank you in advance.

Best Regards,

Raphaël

Tags (1)
  • Tags:
  • english
Share
Reply
Valentin_Kozlov
Lieutenant Valentin_Kozlov Lieutenant
Lieutenant
‎2020-11-17 04:08 AM
1 Like
1
433
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2020-11-17 04:08 AM

Re: Rack Monitor Netbotz 250 : Syslog Severity Configuration

Raphael you may refer to RFC to get more deep Syslog description.

 

Each Syslog message have PRI field which comes after header and means emergency level of the message.

The Priority value is calculated by first multiplying the Facility
   number by 8 and then adding the numerical value of the Severity.  For
   example, a kernel message (Facility=0) with a Severity of Emergency
   (Severity=0) would have a Priority value of 0.  Also, a "local use 4"
   message (Facility=20) with a Severity of Notice (Severity=5) would
   have a Priority value of 165.  In the PRI of a syslog message, these
   values would be placed between the angle brackets as <0> and <165>
   respectively. 

 

I'm not sure what exact Facility code Netbotz use for Syslog messages.

 

Let's imagine that it will "local use 4" as in example above with Facility=20.

 

Then we map our Netbotz messages to Syslog Severity:

 

SyslogMapCritical=Critical

SyslogMapWarning=Warning

SyslogMapInformational=Info

 

As per FRC table

       Numerical         Severity
             Code

              0       Emergency: system is unusable
              1       Alert: action must be taken immediately
              2       Critical: critical conditions
              3       Error: error conditions
              4       Warning: warning conditions
              5       Notice: normal but significant condition
              6       Informational: informational messages
              7       Debug: debug-level messages

 

 

SyslogMapCritical=Critical => 2

SyslogMapWarning=Warning => 4

SyslogMapInformational=Info => 6

 

So you will receive PRIVAL=162 (Facility*8+Severity = 20*8+2) in case of Critical Netbotz alert, PRIVAL=164 (Facility*8+Severity = 20*8+4) in case of Warning alert and PRIVAL=166 (Facility*8+Severity = 20*8+6) for Informational events.

 

Considering this numbers you can work with messages on your Syslog server.

 

If you set

 

SyslogMapCritical=Info => 6

SyslogMapWarning=Info => 6

SyslogMapInformational=Info => 6

 

All messages from Netbotz will have equal priority level PRIVAL=166 (Facility*8+Severity = 20*8+6) for syslog server.

 

If you would like to receive Debugging severity level for all events from Netbotz, you should set this level for all alert types^

SyslogMapCritical=Debug

SyslogMapWarning=Debug

SyslogMapInformational=Debug

 

 

See Answer In Context

Tags (1)
  • Tags:
  • english
Share
Reply
rf2019
Lieutenant JG rf2019
Lieutenant JG
‎2020-11-17 04:15 AM
0 Likes
0
428
  • Mark as New
  • Bookmark
  • Subscribe
  • Mute
  • Subscribe to RSS Feed
  • Permalink
  • Print
  • Email to a Friend
  • Report Inappropriate Content
‎2020-11-17 04:15 AM

Re: Rack Monitor Netbotz 250 : Syslog Severity Configuration

Thank you for your explanations 🙂

Best Regards,

 

Raphaël

Tags (1)
  • Tags:
  • english
Share
Reply
Top Experts
User Count
Jef
Commander Jef Commander
41
APC_Steve
Lt. Commander APC_Steve Lt. Commander
24
gsterling
Lt. Commander gsterling Lt. Commander
20
Cory_McDonald
Lieutenant Cory_McDonald Lieutenant
13
GavanOB
Lieutenant GavanOB Lieutenant
7
See More Top Experts
Find a Service Provider
Find a certified partner to help you address your integration, installation, maintenance and project needs.
View all Providers
Support

Have a question? Please contact us with details, and we will respond.

Contact Us
FAQ

Look through existing questions to find popular answers.

Learn More
About

Want to know more about Exchange and its possibilities?

Learn More

Full access is just steps away!

Join Exchange for FREE and get unlimited access to our global community of experts.

Connect with Peers & Experts

Discuss challenges in energy and automation with 30,000+ experts and peers.

Get Support in Our Knowledge Base

Find answers in 10,000+ support articles to help solve your product and business challenges.

Ask Questions. Give Solutions

Find peer based solutions to your questions. Provide answers for fellow community members!

Register today for FREE

Register Now

Already have an account?Log in

About Us FAQ Terms & Conditions Privacy Notice Change your cookie settings
©2020, Schneider Electric