Lexmark X925 Lexmark Document Distributor - Page 123

Solving problems with discovery, Discovery and policy updates run slowly

Get Lexmark X925 PDF manuals and user guides View all Lexmark X925 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 123 highlights

Solving problems with discovery Discovery and policy updates run slowly 1 Check your proxy, firewall, and other network settings on LDD components to make sure all necessary communication is allowed. 2 Make sure other network traffic is not reducing bandwidth during discoveries and policy updates. 3 If you have three or more servers in your system, try reducing the Chunk Size using the General service on the Services tab. A value as low as 2 may improve performance. 4 To reduce the time waiting for non-responsive printers during policy updates, reduce the Timeout per device using the PolicyUpdate service on the Services tab. Note: If you are deploying solutions that include large eSF applications or several eSF applications, a lower setting may not allow enough time to successfully validate eSF application deployment. 5 If you are discovering printers for subsequently added discovery profiles in a device group or groups in which you have previously discovered printers, select Discover new devices only to skip any IP address where a printer has been discovered. Discoveries frequently time out 1 Check your proxy, firewall, and other network settings on LDD components to make sure all necessary communication is allowed. 2 Make sure other network traffic is not reducing bandwidth during discoveries and policy updates. 3 If you have three or more servers in your system, try increasing the initial time-out and retry times using the NPA service on the Services tab. Type a time-out period in milliseconds for each retry in sequence, separating each by a space, in the NPANT Timeout field. Some printers on the network cannot be discovered 1 Check your proxy, firewall, and other network settings on LDD components to make sure all necessary communication is allowed. 2 On the Services tab, make sure the Read Community Name and Write Community name for the SNMP service match the printers on the network. All printers used in the LDD system must use the same read community name and write community name. Troubleshooting 123

  • 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
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
Solving problems with discovery
Discovery and policy updates run slowly
1
Check your proxy, firewall, and other network settings on LDD components to make sure all necessary
communication is allowed.
2
Make sure other network traffic is not reducing bandwidth during discoveries and policy updates.
3
If you have three or more servers in your system, try reducing the Chunk Size using the
General
service on the
Services
tab. A value as low as
2
may improve performance.
4
To reduce the time waiting for non-responsive printers during policy updates, reduce the Timeout per device
using the
PolicyUpdate
service on the
Services
tab.
Note:
If you are deploying solutions that include large eSF applications or several eSF applications, a lower setting
may not allow enough time to successfully validate eSF application deployment.
5
If you are discovering printers for subsequently added discovery profiles in a device group or groups in which
you have previously discovered printers, select
Discover new devices only
to skip any IP address where a printer
has been discovered.
Discoveries frequently time out
1
Check your proxy, firewall, and other network settings on LDD components to make sure all necessary
communication is allowed.
2
Make sure other network traffic is not reducing bandwidth during discoveries and policy updates.
3
If you have three or more servers in your system, try increasing the initial time-out and retry times using the
NPA
service on the
Services
tab. Type a time-out period in milliseconds for each retry in sequence, separating
each by a space, in the NPANT Timeout field.
Some printers on the network cannot be discovered
1
Check your proxy, firewall, and other network settings on LDD components to make sure all necessary
communication is allowed.
2
On the Services tab, make sure the Read Community Name and Write Community name for the SNMP service
match the printers on the network. All printers used in the LDD system must use the same read community name
and write community name.
Troubleshooting
123