-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supermicro - divice mis-identification #149
Comments
It's because of this code line: We should be more specific in the detection of blade or not based on the product number. Do you have more information for that ? Forcing server or blade with the command line could be a nice addition I'll open an issue for that |
Sure what kind of information do you need? Also do you need help with the project? |
The blade detection system is based per manufacturer. It's also true with HP, but I have a feeling that it's less easy with Supermicro... they tend to have false dmidecode infos and their product number doesn't reflect the "am I a blade or a pizza box" part If you have a better understanding of their products and know a generic way to check that, I'd be very happy to implement it ! Regarding help with the project, it's more than welcome ! It was a personal project that I thought could be interesting for other netbox user, so I'm always happy to implement or merge additional features! |
All the supermicro servers i've used in the past few years start with SYS including their microcloud( these considered blades?). |
Microcloud are considered blade from my point of view, especially if dmidecode mentions a |
From what I've noticed their product numbers aren't something that's predictable. I think to handle that programmatically would be difficult( at least for me). I have someone working with me to look at solutions. But I think being able to pass an option like is_blade: True|False when the detected vendor is supermicro may be an easy way to do it. |
I understand The agent will need to know the S/N of the chassis to do the lookup, and its blade slot to correctly assign the server to the blade. I will see if I can work on this additional feature this week |
It adds more complexity to the agent, so I preferred to rework the supermicro blade/pizza detection, would you be able to try the branch |
I can try bright and early on Monday.
ryan.jones26@gmail.com
…On Jul 11, 2020, 9:56 AM -0400, Solvik ***@***.***>, wrote:
It adds more complexity to the agent, so I preferred to rework the supermicro blade/pizza detection, would you be able to try the branch supermicro?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I'm free to test the branch today. which branch should I test ? |
This one : https://github.com/Solvik/netbox-agent/tree/supermicro
Le lun. 13 juil. 2020 à 19:58, Ryan Jones <notifications@github.com> a
écrit :
… I'm free to test the branch today. which branch should I test ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABRIIMKKALYF4SVWWSGBGTR3NDNNANCNFSM4OR7HYEA>
.
|
I assume i need to pass an option
|
No, I just forgot I didn't implement supermicro server compatibilty I got a dmidecode of a some kind of blade system to test it Could you retry? |
seems better. still getting an error.
will use the new branch to test other systems. but the box I just tested on is a model that I was having the issue with previously |
deployed on another 6 boxes. All throw the error above however everything else seems to be working fine. |
You're not the first one to raise this error to me, what netbox version are you using ? |
v2.8.6
Ryan
3476787719
ryan.jones26@gmail.com
…On Wed, Jul 15, 2020 at 11:35 AM Solvik ***@***.***> wrote:
You're not the first one to raise this error to me, what netbox version
are you using ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#149 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJFFHASQ6DEQUNFNEXPNA3R3XEEJANCNFSM4OR7HYEA>
.
|
I'm closing this issue since I've merge the supermicro modifications |
the agent is recognizing Supermicro SYS-1029U-E1CRTP-2-LL09G as a chassis. This should be a 1U service not a chassis. Is there a specific override that I can set in the config file? I don't have any chassis in my infra.
Also identifying any servers with motherboard X11SPW-TF as a blade.
The text was updated successfully, but these errors were encountered: