|
July 2010 |
Introduction:
Openfiler is an open source Linux distribution that is used for NAS systems as it comes with common sharing features already installed .It is administered through a browser based management application making it feel like more of a network appliance than a server.
Setup:
This guide goes through setting up Openfiler when you start it up for
the
first time.
1) First you need to find the IP address to connect to, logon to
the server locally with the username “root” and the password you were
supplied with. Once logged on use the ‘ifconfig’ command, in the output
should be either ‘eth0’ or ‘eth1’, the DHCP assigned address should be
below it among other information. Access the Openfiler management
interface through your browser with the address
“https://[server_ip_address]:446”. Your browser may say that it is an
“Untrusted Connection” as it does not have a validated security
certificate, however as you know the address you are accessing is secure
just add an exception. The default login details are “Openfiler” and
“password”. To change the login password go to the Accounts tab and
select ‘Admin Password’ from the menu on the right.
2) The first step is to change the system settings to what is
required for your network. The System tab contains the main
administration and network settings. Network setup consists of setting
the DNS hostname and server settings, the network interface
configuration if you wish to use static addresses and also the “Network
Access Configuration” which specifies the subnet that the server will be
connected to. To specify the subnet you need to enter the network
address which represents the entire address range. In this example the
server address is 192.168.1.57 with a subnet mask of 255.255.255.0 so
the network address will be 192.168.1.0 which represents the address
range 192.168.1.1-192.168.1.255. You must also specify whether it is a
share network or a UPS monitoring connection. This setting is necessary
for sharing operations to work on the server.
3) The menu to the right of the System page also has other
important administration options; Time/Date setup, UPS management, Email
notification setup (you must put something for the sender’s address for
it to work, even if it’s not an actual email address), system updating,
system configuration backup as well as Shutdown/Reboot commands. You
may want to check system updates from time to time, updating is a
straight forward process.
4) Next go to the ‘Accounts’ page to set up user information
configuration. If Active Directory is present on the network enable
Domain Controller Authentication and enter the required details. In this
example we are going to run the LDAP service from the Openfiler server.
LDAP will be used to manage user access to Openfiler services using its
own user and group database. The domain can be whatever you want however be sure to include "cn=manager" for the Root bind DN and "openfiler" for the password as they are preconfigured on Openfiler. After filling this in the LDAP service
should automatically become enabled in the Services page.
5) Go to ‘Administration’ which is on the right side menu, here
you can create and manage users and groups. Creation is straight
forward; you can override automatic user or group IDs and set your own
for organization reasons (numbering starts at 500), however it’s not
necessary. For share reasons you must assign a user to the correct group when you create it. While you can add/remove users to groups at a later date you can only assign a users primary group when it is created. This can become an issue say for example User1 is originally assigned to Group1, even if he is later removed from that group and added to Group2 he will still retain Group1 share access rights as well the rights of his new Group2. To fix this delete the user and recreate it setting the new primary group upon creation.
6) Go to the Services page; LDAP server, ACPI daemon and iSCSI
initiator should be running by default. Enable the services you wish to
use and your initial setup is complete.
From here you can go on to setup whatever services you want for your network; SMB/CIFS is used for 'Shared Folder' storage on Windows systems and NFS is used to share to other operating systems such as Mac and Linux distributions. FTP is useful as it widely supported and is accesible using a web browser and iSCSI is a powerful protocol with good transfer speeds to give storage to workstations and servers.
|
|
|
July 2010 |
|
Introduction
The advent of IP (Internet Protocol) into Video Surveillance systems has allowed wireless to be part of the solution enabling a significant extension of physical area coverage. This paper is a tutorial on what a wireless bridge is for IPVS use and it points out an important aspect that has often been overlooked.
Access Point & Bridge
Many schools (used interchangeably with businesses and organizations) have installed wireless equipment to connect students and teachers to the cabled network. This type of installation is called Access Point. An Access Point provides two functions: converting the medium for signal transmission from wireless to cable and vice versa, and serving multiple clients at one time like a hub. It is a popular use of wireless. What is not as well known is the subject of this article- wireless bridge and our legal obligations. We raise these issues for the first time as a report of the research and development efforts expended by the Compucon IPVS team. The findings are useful for schools when considering an extension of the school data network for various purposes including video surveillance. Compucon has gone onto this journey with IPVS in mind but applications are not limited to IPVS.
For the full tutorial, please register here.
|
|
|
July 2010 |
|
Introduction
The advent of IP (Internet Protocol) into Video Surveillance systems has allowed wireless to be part of the solution enabling a significant extension of physical area coverage. This paper is a tutorial on what a wireless bridge is for IPVS use and it points out an important aspect that has often been overlooked.
Access Point & Bridge
Many schools (used interchangeably with businesses and organizations) have installed wireless equipment to connect students and teachers to the cabled network. This type of installation is called Access Point. An Access Point provides two functions: converting the medium for signal transmission from wireless to cable and vice versa, and serving multiple clients at one time like a hub. It is a popular use of wireless. What is not as well known is the subject of this article- wireless bridge and our legal obligations. We raise these issues for the first time as a report of the research and development efforts expended by the Compucon IPVS team. The findings are useful for schools when considering an extension of the school data network for various purposes including video surveillance. Compucon has gone onto this journey with IPVS in mind but applications are not limited to IPVS.
For the full tutorial, please register here.
|
|
|
July 2010 |
|
Introduction
The advent of IP (Internet Protocol) into Video Surveillance systems has allowed wireless to be part of the solution enabling a significant extension of physical area coverage. This paper is a tutorial on what a wireless bridge is for IPVS use and it points out an important aspect that has often been overlooked.
Access Point & Bridge
Many schools (used interchangeably with businesses and organizations) have installed wireless equipment to connect students and teachers to the cabled network. This type of installation is called Access Point. An Access Point provides two functions: converting the medium for signal transmission from wireless to cable and vice versa, and serving multiple clients at one time like a hub. It is a popular use of wireless. What is not as well known is the subject of this article- wireless bridge and our legal obligations. We raise these issues for the first time as a report of the research and development efforts expended by the Compucon IPVS team. The findings are useful for schools when considering an extension of the school data network for various purposes including video surveillance. Compucon has gone onto this journey with IPVS in mind but applications are not limited to IPVS.
For the full tutorial, please register here.
|
|
|
July 2010 |
8 March 2017 Update: Our most recent
recommendation is to update both the driver and firmware at the same
time to keep them synchronised, as we have witnessed a case whereby
updating the firmware alone (and not the driver) causes the OS to stop
booting correctly with an inaccessible_boot_device blue screen. Should
this occur you will need to use tools such as Shadow Protect (bootable
media) to inject the new driver back into your OS.
There are three steps to getting your Adaptec RAID controller up to date; updating the controller firmware, updating the controller driver under the Operating System and updating Adaptec Storage Manager (management
GUI). Be sure to perform the actions in that order to ensure proper
interaction between the different firmware/software components. This
example will show the installation of these within the OS, please see at
the bottom of the document for the alternative firmware update method
using a boot disk.
Updating the Controller Firmware
1) The first step in the whole process is to download
the latest firmware, driver, and ASM version. This example will be
using Windows Server 2003 R2 32-bit, however the procedure will be
similar for most Windows operating systems.
2) Open up Adaptec Storage Manager, login, highlight ‘Direct
Attached Storage’ then up the top go to Actions>Update Controller
Images:
3) There are three steps to this part; selecting the image files, selecting the controller and confirming the update details.
4) In the first section click ‘Add’ and then browse to the
folder containing the controller firmware, there should be multiple
images in the folder, add them all then go to the next step.
5) Check the box next to the controller you want to update. It
also shows you the currently installed firmware version and the version
you are updating it to. Hold control and select a controller to force an
update, you would have to do this if you were installing a version
older then the one currently installed.
6) Start the update and be sure to not disturb the system during installation. Restart once it is finished as it suggests.
Updating the Controller Driver
1) To update the driver first open device manager, right click the RAID controller and select ‘Update Driver’
2) Choose to install from a specified location and point it to
the folder containing the most recent driver update. The remainder of
the driver update wizard is straight forward.
Updating Adaptec Storage Manger
1) Before updating to the newest version we have to uninstall
the current version, do this through Add/Remove Programs or the
equivalent in newer Windows operating systems.
2) Restart the system and launch the new ASM installer, the install is straight forward and default settings should be used.
3) When launching ASM for the first time after installing it, it
will ask you to register; click ‘Register Now’ and then close the web
page it opens, it will no longer ask you to register.
4) If you are updating from a past version of ASM check that all
the settings are carried over to the new installation. Also it is
important to test that the email notification is working; on occasion
updating ASM has caused an SMTP failure when trying to send email
notifications. To do this access Email Notifications from the configure menu up the top. In the Email Notifications window right click a configured user and select 'Send test message'.
To fix this problem you need to uninstall ASM, browse to the Program
Files folder (and/or Program Data) and either delete the Adaptec folder or rename it to
something like “Adaptec.OLD” if you wish to keep the old installation
files (old logs etc). After doing this install ASM and set it up again.
Please note that this removes all your old settings and will mean you
have to configure ASM from scratch so only do this if you are
experiencing problems with the new install.
5) It is recommended that you configure email notifications as
this means you can be notified about any potential RAID issues before it
potentially becomes a more severe problem. To do this follow this knowledge base article. Be sure to send a test email notification as explained in the article.
Confirming the Updates Were Successful
1) To check the current versions of the controller
firmware, boot rom and the OS driver open up ASM. Right click the
controller on main page or the left menu and select Properties; go the
the Versions tab and you will be able to see the currently installed
versions of these.
2) To check the current version of ASM go the the Help menu at
the top of the window and select 'About Adaptec Storage Manager'; the
version should be down the bottom of the window.
Special Notes
- If you are updating from controller firmware verion 16501 or if you
have arrays that were originally created under version 16501 you may
find that after updating the firmware that one or more arrays become
inaccesible. Please follow this guide, it tells you how to apply a fix to resolve the issue.
Updating the Controller Firmware from a Boot Disk
1) The first step to updating the firmware is to create an MS-DOS boot disk; floppy or USB. Next download
the latest firmware for your controller. Extract and copy the firmware
folder onto the boot disk; it should include AFU.exe, ACU.exe and a
number of firmware image files.
2) Restart the system and launch the boot disk, if using USB you
may need to add the drive into the boot device list in the
motherboard’s BIOS to make it accessible from the boot menu prompt.
Browse to the firmware folder on the boot disk and once there you can run ‘AFU’ to start the Adaptec Flash Utility.
3) As you can see you can perform a few tasks here. You can
check the currently installed firmware build number and date (4). Also
you can verify the currently installed firmware against the most recent
update using (3) to see whether it is already up to date. It is also
worth saving (2) the currently installed version before updating in case
a roll back is necessary later on due to a bad firmware update. Begin
the update (1) and confirm the folder the firmware images are in.
Restart once it is completed.
|
|
|
|
<< Start < Prev 191 192 193 194 195 196 197 198 199 200 Next > End >>
|
| Results 1783 - 1791 of 2511 |
