Bosch VIPX1 Operation Manual - Page 125

iSCSI connections malfunctions, Alarm sources, Alarm connections, Malfunction, Possible causes - firmware

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

Page 125 highlights

VIP X1 | Installation and Operating Manual EN | 125 Malfunction Possible causes Solution The unit does not report an alarm. Alarm source is not selected. Select possible alarm sources on the Alarm sources configuration page. No alarm response specified. Specify the desired alarm response on the Alarm connections configuration page, change the IP address if necessary. Control of cameras or other units is not possible. The cable connection Check all cable connections and between the serial interface ensure all plugs are properly fitted. and the connected unit is not correct. The interface parameters do Make sure that the settings of all not match those of the other units involved are compatible. unit connected. The unit is not opera- Power failure during protional after a firm- gramming by firmware file. ware upload. Have the unit checked by Customer Service and replace if necessary. Incorrect firmware file. Enter the IP address of the unit followed by /main.htm in your Web browser and repeat the upload. iSCSI connections malfunctions Malfunction Possible causes Solution No LUNs are displayed after connection to the iSCSI server. Incorrect LUN mapping during iSCSI server configuration. Check the iSCSI server configuration and reconnect. „LUN FAIL" is displayed below a node after connection to the iSCSI server. The LUN map was not read- Check the iSCSI server configuraable as it was assigned to tion and reconnect. the wrong network interface. LUN mapping is not Some iSCSI systems don't Delete the initiator extension on the possible. support initiator extensions. iSCSI settings configuration page. Bosch Security Systems | 2006-12 | V2.5 Appendix

  • 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
  • 142
  • 143
  • 144
VIP X1
| Installation and Operating Manual
EN | 125
Bosch Security Systems | 2006-12 | V2.5
Appendix
iSCSI connections malfunctions
The unit does not
report an alarm.
Alarm source is not selected.
Select possible alarm sources on
the
Alarm sources
configuration
page.
No alarm response speci-
fied.
Specify the desired alarm response
on the
Alarm connections
config-
uration page, change the
IP address if necessary.
Control of cameras
or other units is not
possible.
The cable connection
between the serial interface
and the connected unit is not
correct.
Check all cable connections and
ensure all plugs are properly fitted.
The interface parameters do
not match those of the other
unit connected.
Make sure that the settings of all
units involved are compatible.
The unit is not opera-
tional after a firm-
ware upload.
Power failure during pro-
gramming by firmware file.
Have the unit checked by Cus-
tomer Service and replace if nec-
essary.
Incorrect firmware file.
Enter the IP address of the unit fol-
lowed by
/main.htm
in your Web
browser and repeat the upload.
Malfunction
Possible causes
Solution
No LUNs are dis-
played after connec-
tion to the iSCSI
server.
Incorrect LUN mapping dur-
ing iSCSI server configura-
tion.
Check the iSCSI server configura-
tion and reconnect.
„LUN FAIL“ is dis-
played below a node
after connection to
the iSCSI server.
The LUN map was not read-
able as it was assigned to
the wrong network interface.
Check the iSCSI server configura-
tion and reconnect.
LUN mapping is not
possible.
Some iSCSI systems don’t
support initiator extensions.
Delete the initiator extension on the
iSCSI settings
configuration page.
Malfunction
Possible causes
Solution