What combination of OIDs or MIBs are needed to correctly attribute Ricoh printers?

[jb2291]

We have over a 1,000 Ricoh printers and are at the beginning of our configuration journey to make the records more accurately attribute the correct model information.  We only have one OID loaded for Ricoh printers so all the printers are being assigned the same model even though the printer description field has populated the actual printer model.   

Are more OIDs needed or is a Ricoh MIB file needed to allow discovery to accurately represent the model?  

Thanks

Jon

Log in

to use Ginger

Limited mode

to make the records more accurately

×

[Ankush13]

You would also need to add OIDs of devices your org is using under CI Classification > SNMP System OIDs.

[jb2291]

I have tried to add Ricoh OIDS that would map to the model by examining the Ricoh MIB pdf documents.  The OIDs that are being populate still do not populate the model ID that matches what is stored in the description.  When I examine the XML discovery logs, I see the model being identified and mapped to some value.  Unfortunately the model is not be updated and instead the identification information is appended to the description field.  I feel I am missing some connecting configuration.  --- Thought --- We have a few year's old implementation of ServiceNow -- Do the out of box printer MIBs that are documented in ServiceNow online documents being updated to the latest version available (London version) or do the ServiceNow discovery MIB libraries need to manually be updated?

[Ankush13]

Are you missing only model ID? Certainly looks like a config issue.

OIDs are usually added automatically during upgrades AFAIK.

[smfoister]

I hate to be the bearer of bad news but I've been on this Ricoh journey for months now and there just simply isn't a good solution that I have found. You can register on the Ricoh RiDP site and download a bunch of PDF's that vaguely tell you how to build your own MIB files, but if you're like me you just simply do not have the time or staff to invest into that effort.

The single OID you added was probably the shared private OID that all of their models have, and unfortunately you'll eventually find that some Cisco devices also share this same OID. It's a mess...

I've decided that I'm just going to create my own pattern and parse the description for the values I need.