Dear users and customers Thank you for all your feedback here and via other communication channels. We want to inform and announce, that we offer enhancements and more informaiton with the App version 3.0.2. As well the Video Security App verison 3.0.3 and newer versions will offer additinal assistance. The App version 3.0.2 works fine when connectiong to e.g. DIVAR IP 3000 and similar DIVAR IP models which include BVMS onit. These days we received additional questions in regards to the Video Security Client App and messages shown in regards to certificates. Some of our customers asked why expired certificates (marked with red validity period) are shown each time the App is started new on an IOS Smartphone or IOS tablet. Please be aware, that this is normal in App version 3.0.2. Only valid certificates approved once, will not be shown with a request of approval at the new start of the App. Expired certificates will be shown again in the App version 3.0.2 and users are requested to approve those at each new start of the App. Solution Please reach out to your BOSCH support in case you are not sure on how to renew or install valid certificates on your IP cameras. The start date of the validity period of the IP camera certificate must be in the past and the end date and time of the certificate must not be expired. If this is the case the App will not ask for approval each time (see also blue banner text in the App). As well the App verison 3.0.3 will show the approval screen only once. After the certificates are approved the app will not show the approval screen at next new start. It is anyhow recomended to ensure that certificates used on the IP cameras are in a valid state. We do thank you for the kind feedback.
... View more
Dear user. According to NetApp and BOSCH R&D it is essential to update single controller systems and duplex-controller systems. We will come back to you here as soon additional checks are done and after NetApp informed for the special use case to tod 24/7 video recording and replay. For the moment it is advised to update the systems.
... View more
Microsoft Event Logging, when an error occurs, the system administrator or Integrator must determine what caused the error. The operator can then use the event log to help determine what conditions caused the error and identify the context in which it occurred.
Starting Event Viewer
The procedure for starting Event Viewer depends on your starting point, e.g. windows key + R type in ”eventvwr.msc” hit enter.
With the decent administrative access, you can select any computer in your network to view that Microsoft system event logs.
To select computers in Event Viewer:
In the top of the console tree, right-click Event Viewer (local), and then click Connect to another computer.
Enter FQDN/NetBIOS name or browser to the regarding machine
Adjusting Event Viewer Settings
In the console tree, right-click the appropriate log file, and then click Properties. Click the General tab.
Saving Event Logs
In the console tree, right-click the appropriate log file, and then click Save Log File As. Navigate to the subfolder in which you want to save the file, type a name for the file, click the file type, and then click Save.
Clearing Event Logs
In the console tree, right-click the appropriate log file, and then click clear all Events. You are prompted for whether you want to save the log to a file before clearing it. Click “Yes” to save a log and clear all events. If you click No, the log is not saved, but all events are cleared from the selected Event log. If you click Cancel, the request to clear the log is canceled.
Viewing Event Details
In the console tree, right-click the appropriate log file. A list of events in the log file is displayed in the details pane of Event Viewer. Click a specific event in the details pane to display the Event Properties dialog box and details about the event.
In the console tree, right-click the appropriate log file, and then click Properties. Click the Filter tab. Type the appropriate information that you would like to filter.
In the console tree, right-click the appropriate log file. On the View menu, click Find. Type the appropriate information that you would like to find in the dialog box, and then click Find Next.
An event that indicates a significant problem such as loss of data or loss of functionality. For example, if a service fails to load during startup, an Error event is logged.
An event that is not necessarily significant, but may indicate a possible future problem. For example, when disk space is low, a Warning event is logged. If an application can recover from an event without loss of functionality or data, it can generally classify the event as a Warning event.
An event that describes the successful operation of an application, driver, or service. For example, when a network driver loads successfully, it may be appropriate to log an Information event. Note that it is generally inappropriate for a desktop application to log an event each time it starts.
An event that records an audited security access attempt that is successful. For example, a user's successful attempt to log on to the system is logged as a Success Audit event.
An event that records an audited security access attempt that fails. For example, if a user tries to access a network drive and fails, the attempt is logged as a Failure Audit event.
The events themselves are what we’re trying to see, of course, and their usefulness can range from really specific and obvious things that you can fix easily to the totally undefined messages that don’t make any sense and you can’t find any information on your preferred search engine. example:
The regular fields on the display contain:
Log Name – while in older versions of Windows everything got dumped into the Application or System log, in the more modern editions there are dozens or hundreds of different logs to choose from. Each Windows component will most likely have its own log.
Source – this is the name of the software that generates the log event. The name usually doesn’t directly match with a filename, of course, but it is a representation of which component did it.
Event ID – the all-important Event ID can actually be a little confusing. If you were to Google for “event ID 122” that you see in the next screenshot, you wouldn’t end up with very useful information unless you also include the Source, or application name. This is because every application can define their own unique Event IDs.
Level – This tells you how severe the event is – Information just tells you that something has changed or a component has started, or something has completed. Warning tells you that something might be going wrong, but it isn’t all that important yet. Error tells you that something happened that shouldn’t have happened, but isn’t always the end of the world. Critical, on the other hand, means something is broken somewhere, and the component that triggered this event has probably crashed.
User – this field tells you whether it was a system component or your user account that was running the process that caused the error. This can be helpful when looking through things.
OpCode – this field theoretically tells you what activity the application or component was doing when the event was triggered. In practice, however, it will almost always say “Info” and is pretty useless.
Computer – on your home desktop, this will usually just be your PC’s name, but in the IT world, you can actually forward events from one computer or server to another computer. You can also connect Event Viewer to another PC or server.
Task Category – this field is not always used, but it ends up basically being an informational field that tells you a bit more information about the event.
Keywords – this field is not usually used, and generally contains useless information.
As a rule of thumb (common way of doing), you should try searching by the general description, or the Event ID and the source, or a combination of those values. Just remember that the Event ID is unique for each application. So there is a lot of overlap and you can’t just search for “Event ID 122” only. This is because users might find the list is too large and too general, your specific search aspect might not fit your issue.
... View more
IP cameras, Configuration Manager, BVMS Configuration Client
This article provides a background information about syslog, tips for 3 rd party Syslog server options and step by step instructions how to configure, activate and collect the syslog.
Syslog feature is implemented in all IP BOSCH Products. The BOSCH IP cameras as network devices can continuously send system messages via Syslog to a Syslog server software. This function should first be activated and configured.
Once configured syslog will allow a continuous monitoring information even throughout a complete IP camera power cycle (reboot) as the camera starts connecting to the syslog server IP as soon it is getting back online.
Syslog can be useful for analyzing issues that are unpredictable and difficult to reproduce.
3 rd party tools as Syslog server:
There are many different monitoring tools available on the market. Examples of some easy tools to start working with can be e.g.:
PRTG NETWORK MONITOR from PAESSLER
Kiwi Syslog Server
EventLog Analyzer from ManageEngine
Example configuration for KIWI syslog free edition to receive and save the syslog send by the camera.
Syslog server software must be installed on PC/Workstation that is on the same IP-network as the camera/encoder.
One should check the size of the log file per a day and be sure there is enough storage capacity.
1. Enable the logging of the Kiwi software. Access "Setup/Rules/Default/Actions/Log to file", check the box for “Log to file”, then browse to the path where the log files can be saved.
2. Add the IP address of the camera(s) to "Setup/Inputs". Click on the address box, type in the address of the camera, click “Add”, then “OK”. (The Free Edition can log a maximum of 5 cameras.)
3. This point should be done after the camera is configured to send the syslog data. Open the Kiwi software and select “Manage” then Click on “Start the Syslogd service”. Log information should start to scroll in the Syslog main window. How fast or often messages appear depend on which debug command was provided by Tech support
Configure the camera to send the syslog data
The configuration can be done via the Web Interface of the camera, Bosch Configuration Manager (stand-alone configuration software) or BVMS Configuration Client software (part of BVMS management system). The layout of the above 3 interfaces is very similar. The following steps and screenshots are done for Configuration Manager.
1. Ensure that the Date/Time of the Syslog PC, camera(s), and recording system are synchronized (as close as possible)
2. Enable the Time Stamping and ensure that it is set for milliseconds. a. NOTE: The time stamp is important for troubleshooting.
3. Navigate to Configuration Tab “Network/Advanced/Syslog”. Enter the IP address of the Syslog Sever PC/Workstation and click the “Save” icon.
4. Navigate to Configuration Tab “Service/Logging”, then Debug Logging. At the Even Logging text box the debug command that was provided to you by Bosch support team.
If no debug command was provided, use: syslog_dbg. Click on the “Save” icon.
Collecting the logs
Once the issue appears, note the date and time, collect and provide the maintenance.log from the camera and the syslog saved at the of the Syslog Sever PC/Workstation.
... View more