Power management mibs
Christopher LILJENSTOLPE <[email protected]>
| Newsgroups | gmane.ietf.ops |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greetings, Chair hat off, operator hat on. I like the level of work that has gone on here, and would like to see it combined into one draft. As I stated virtually this morning, I would like to see the richness of the data presented in the quittek draft, but do realize that many elements may not report much of the data. However, please remember that there are plenty of locations that are not data centre powered, even in an operator network. Also, that data becomes more important when you have IT kit (i.e. I may decide to report switchgear out using that mib). To that point, I do think we have to have a way of having non-IP capable kit report via the mib(s). One model is the parent/child, but another could be to take the gateway approach (I've seen some monitoring kit do this before in private mibs). Basically, treat the non-IP kit as enumerated "ports" on whatever is their IP gateway. There may be a LARGE number of ports if something like a scada bus is in use, but it is fairly clean. Just some thoughts. Chris - --- 李柯睿 Check my PGP key here: https://www.asgaard.org/~cdl/cdl.asc -----BEGIN PGP SIGNATURE----- iQEcBAEBAgAGBQJLqlEWAAoJEGmx2Mt/+Iw/5UsH/Auhr4Ulr9gL5neWa7w+d+60 jzTa42b26It0rtvaJamcDGkk/viYPjLhxY6qRDuFIUZ0/f4+3LrVzlq+K+nqglET L81pfo32oOgZmW3PrQiqT6vO8L6mjzKUAGDnmqirMBTfLRkfvk5q8PNHxYXI2Wdc Cy52RA3RUeinw9vEFU353SeV9TvuMhxYY7a6gVKClcyRQym90ZixGLsv1IVraKq3 HxMxzRahTBnk7TDOCDZXJFfPnH4vBm9rJflp0KHVN16L1im6CIMWphX8yMxnnQ5a iVIDb/nsyShcooAAPezu3AECL/yzqMGOrBI9gDX8YK5v3QQElJ8f9D2Ac8iP/uw= =ODon -----END PGP SIGNATURE----- _______________________________________________ OPS-AREA mailing list [email protected] https://www.ietf.org/mailman/listinfo/ops-area