Xerox WorkCentre 6400 Information Manual

Also see for WorkCentre 6400: Features Configuration guide Manual Specifications Quick use guide

Xerox WorkCentre 6400 Information Manual Manual pdf 39 page image

XEROX WorkCentre 6400 Information Assurance Disclosure Paper39Ver. 1.00, May 2010 Page 39 of 446.2. Appendix B – Supported MIB ObjectsNOTES :(1) The number of objects shown per MIB group represents the number of objects defined by the IETF standard for thatMIB group. It does not represent the instantiation of the MIB group which may contain many more objects.(2) Some MIB objects defined within Input and Output groups of the Printer MIB (RFC 1759) have a MAX-ACCESS of RW.However, the Printer MIBv2 defines a MIB-ACCESS of RO for these MIB objects within the Input and Output groups andall machines assessed support RO access. Therefore, RO access to these MIB objects is considered IETF compliant.(3) It is assumed that mandatory IETF string-related MIB objects shall contain meaningful data; not blank strings(4) The "(C)" notation indicates that the previously stated item is a true caveat condition. The "(I)" notation indicates thatthe previous stated item should be regarded as information only.(5) MIB objects that CANNOT be populated with meaningful data (e.g. a machine may not have paper level sensors, hence,can only support "0" or "-3 for more than 1 sheet" for prtInputCurrentLevel) will be considered a caveat, denoted as"(C)".(6) The Printer MIB requires a few groups from RFC 1213 and RFC 1514 to be supported. Therefore, this assessment willindicate that these groups are "supported" as long as the basic MIB structures have been implemented.Support DefinitionsTerm Definition"supported" all MIB objects exists and are populated w/ meaningful data that is consistent w/ thehardware installed within the machine."supported w/ caveats" all MIB objects exists, however, 2 major bugs or less may exists w/ some of the objects thatwere not fixed"not supported" MIB objects do not exist/implementation was not planned"not fully supported" MIB objects exists, HOWEVER, are NOT populated w/ meaningful data OR provide only defaultvalues OR contain 3 or more major bugs"optional, *" optional group that is NOT required by the RFC, however, an implementation may exist; someMIB objects may not be populated w/ meaningful dataSNMP version / Network Transport support WorkCentreSNMPv1 (RFC 1157) supportedSNMPv2P (RFCs 140x) not supportedSNMPv2C (RFCs 190x) supportedSNMPv3 (RFCs 1902, 2572, 2574) supportedSNMP over UDP (IP) supportedSNMP over IPX (Netware) supportedSNMP over NETBEUI (Microsoft Networking) not supported (implemented but never delivered)