Xerox 7300DN User Guide - Page 47

Format, Editing the, Mib.ini File, Updating, PrinterMap, After Mib.ini, File Changes, Pmap.ini File

Get Xerox 7300DN - Phaser Color Laser Printer PDF manuals and user guides View all Xerox 7300DN manuals
Add to My Manuals
Save this manual to your list of manuals

Page 47 highlights

Format Each vendor section within the Mib.ini file follows the format shown in the sample text above. In this case the Xerox vendor has 5 valid MIB II System Object Identifiers (SysObjIDs) associated with it. Concatenated to the SysObjID is an integer value delimited by a colon (':'). Valid values for this integer value are 0, 1 or 2. This integer value is used to indicate whether or not the printer with the specified SysObjID has a built in HTTP server. A value of 0 indicates that the printer does NOT have an HTTP server, a value of 1 indicates that it does have an HTTP server, and a value of 2 indicates PrinterMap is to determine whether the printer has a built in HTTP server. NOTE: The Mib.ini file may contain comment lines shown in the previous sample. The first two characters of comment lines should be two forward slashes ("//") for consistency. Editing the Mib.ini File The Mib.ini file may be modified with any text editor. Be careful not to damage the file structure or modify any default entries because PrinterMap may not function properly afterwards. To edit the Mib.ini file the user needs the vendor of the printer being added, the printer's System Object Identifier, and whether the printer has a built in HTTP server. The printer's System Object Identifier may be determined using any MIB browser to view the printer's MIB II System values. Using a text editor, find the vendor portion of the Mib.ini file to be modified. Next, update the number= entry under the vendor block identifier field with the total number of System Object Identifiers for this vendor following the modifications. Next append the new System Object Identifiers to the end of the vendor block by adding new validN= entries for each new SysObjID:HTTP_flag combination. Save and exit the file after modifying. NOTE: The PrinterMap Topology window must be exited and restarted to register the new Mib.ini entries. Updating PrinterMap After Mib.ini File Changes Following changes to the Mib.ini file, the discover process may be run to find any new printers on the network which match the new Mib.ini file entries. However, Generic printers already discovered by PrinterMap prior to the Mib.ini file changes are unaffected. PrinterMap's Update process may be used to convert any Generic printers now identified in the Mib.ini file to the appropriate vendor printer. Refer to "Update" in Chapter 4 for more information on PrinterMap's Update process. Pmap.ini File The [xerox_models] section of PrinterMap's Pmap.ini file contains entries which map Xerox printer models to model-specific icon files. PrinterMap Topology uses these entries to determine the icons to display for supported Xerox printers. If a Xerox printer is discovered but contains no entry in the Pmap.ini file associating it PrinterMap User Guide 31

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
PrinterMap User Guide
31
Each vendor section within the Mib.ini file follows the format shown in the sample
text above. In this case the Xerox vendor has 5 valid MIB II System Object
Identifiers (SysObjIDs) associated with it. Concatenated to the SysObjID is an
integer value delimited by a colon (‘:’). Valid values for this integer value are 0, 1
or 2. This integer value is used to indicate whether or not the printer with the
specified SysObjID has a built in HTTP server. A value of 0 indicates that the
printer does NOT have an HTTP server, a value of 1 indicates that it does have an
HTTP server, and a value of 2 indicates PrinterMap is to determine whether the
printer has a built in HTTP server.
NOTE:
The Mib.ini file may contain comment lines shown in the previous
sample. The first two characters of comment lines should be two
forward slashes (“//”) for consistency.
The Mib.ini file may be modified with any text editor.
Be careful not to damage
the file structure or modify any default entries because PrinterMap may not
function properly afterwards. To edit the Mib.ini file the user needs the vendor of
the printer being added, the printer’s System Object Identifier, and whether the
printer has a built in HTTP server. The printer’s System Object Identifier may be
determined using any MIB browser to view the printer’s MIB II System values.
Using a text editor, find the vendor portion of the Mib.ini file to be modified. Next,
update the
number=
entry under the vendor block identifier field with the total
number of System Object Identifiers for this vendor following the modifications.
Next append the new System Object Identifiers to the end of the vendor block by
adding new
validN=
entries for each new SysObjID:HTTP_flag combination.
Save and exit the file after modifying.
NOTE:
The PrinterMap Topology window must be exited and restarted to
register the new Mib.ini entries.
Following changes to the Mib.ini file, the discover process may be run to find any
new printers on the network which match the new Mib.ini file entries. However,
Generic printers already discovered by PrinterMap prior to the Mib.ini file
changes are unaffected. PrinterMap’s Update process may be used to convert any
Generic printers now identified in the Mib.ini file to the appropriate vendor
printer.
Refer to “Update” in Chapter 4 for more information on PrinterMap’s Update
process.
The [xerox_models] section of PrinterMap’s Pmap.ini file contains entries which
map Xerox printer models to model-specific icon files. PrinterMap Topology uses
these entries to determine the icons to display for supported Xerox printers. If a
Xerox printer is discovered but contains no entry in the Pmap.ini file associating it
Format
Editing the
Mib.ini File
Updating
PrinterMap
After Mib.ini
File Changes
Pmap.ini File