|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: SCSI MIB: Open IssuesAttempting to push this draft forward, Michelle listed three issues that she was looking for guidance on before publishing a new draft: > " scsiLuOutQueueFullStatus OBJECT-TYPE > > [... snip ...] > > COMMENT: There is no QUEUE FULL in SCSI-3; that's a SCSI-2 term. Use > "TASK SET FULL". > > MHS>>>>>>>>>> Knowing that we are SCSI-2 compliant and not > SCSI-3, how should we call this MIB object? As has been pointed out, just to keep us all on our toes, the current versions are SAM-2 and SCSI-3, with SAM-3 being a work in progress, so this change should be made. > 6)scsiInstAlias, scsiDeviceAlias, etc -why are these admin strings > limited to 79 characters? IMO, these SYNTAX should just be > SnmpAdminString w/no additional size limitation. > > MHS>>>>>>>>>> I would like to hear other opinions. Unless there's a better reason than "fits conveniently on one line", I believe Marj is correct that this restriction should be removed. > 8) scsiDscLunLun - the discovered LUN number is a natural index for this > table, there is no need for another artificial index. So this table > should look like: ...... > > MHS>>>>>>>>>>> LUN is generally an 8-bytes integer that can be 0: > 1. To have it as an index looks heavy from my point of view. > 2. It is generally not recommended to have 0 as an index. > I would like to get other opinions before doing the changes. I'm going to refer this issue to Keith for his opinion. Thanks, --David ---------------------------------------------------- David L. Black, Senior Technologist EMC Corporation, 176 South St., Hopkinton, MA 01748 +1 (508) 293-7953 FAX: +1 (508) 293-7786 black_david@emc.com Mobile: +1 (978) 394-7754 ----------------------------------------------------
Home Last updated: Tue Feb 11 14:19:18 2003 12297 messages in chronological order |