Should I model KVM modules?

[grahamc]

Hi,

My rack has a Raritan Dominion which uses D2CIM modules to connect to targets, like these:

Should these be modeled as Modules? Should I say "whatever" and skip it as not worth it?

[joernheissler]

They've got an ethernet interface, so I'd definitely model them.

Not as a module, but as their own device type:

• Single ethernet (POE?) interface
• One "console server port"; actually it's 3, but that would become tedious. This will be connected to a server's "console port".

Those KVM devices can live on their own, with only ethernet connected (useless, but still in the network). If you've got only a few of them and only connect them to a specific server on demand, modeling them as modules might not work well.

But of course it's up to you. If every server got one one of those it might be a bit easier to use modules.

[svalouch]

It's likely not a real Ethernet interface but just uses an RJ45 socket because everyone's got these cables in abundance and they don't have to engineer a custom cable, so there is no MAC address and no standardized power delivery method, it only works with compatible devices from the same vendor and doesn't work if plugged directly into a network switch. Internally, they are essentially passive devices that just do what's necessary to deliver the required signals between it and the actual KVM appliance that then has LAN for accessing it with a browser.

Despite that, I'd essentially still go with what @joernheissler proposed: an "interface" so you can pull a cable to the KVM appliance, and a console server port representing the trio of plugs. If it's permanent, I'd connect it to the server's console port, perhaps creating a separate one if you want to keep the rs/232 port open for other uses.

[joernheissler]

Sorry, I was under the impression that those are stand-alone devices. That changes my opinion. A KVM switch is required and it got N console ports. With this in mind I think it would be okay to not model that KVM module at all and instead connect the server directly to the KVM switch.
But of course there's nothing wrong with modelling it.