2012年5月30日星期三

Forigate - Set Allowaccess

The command for  "Set Allowaccess"

config system interface
edit port8
set ip 10.11.101.102/24
set allowaccess https ping ssh snmp
end

Forigate Console

To connect to the CLI using a local serial console connection

1 Using the null modem or RJ-45-to-DB-9 cable, connect the FortiGate unit’s console
port to the serial communications (COM) port on your management computer.

2 On your management computer, start HyperTerminal.

3 For the Connection Description, enter a Name for the connection, and select OK.

4 On the Connect using drop-down list box, select the communications (COM) port on
your management computer you are using to connect to the FortiGate unit.

5 Select OK.

6 Select the following Port settings and select OK.

Bits per second: 9600
Data bits:8
Parity: None
Stop bits: 1
Flow control: None

7 Press Enter or Return on your keyboard to connect to the CLI.

8 Type a valid administrator account name (such as admin) and press Enter.

9 Type the password for that administrator account and press Enter. (In its default state,
there is no password for the admin account.)
The CLI displays the following text:

Welcome!
Type ? to list available commands.
You can now enter CLI commands, including configuring

2012年5月16日星期三

Error E0BB014B: Volume not found

Restoring Dynamic Disks in the Backup Exec System Recovery (BESR) and Symantec System Recovery (SSR) Symantec Recovery Environment (SRD).

Problem


Restoring Dynamic Disks in the Backup Exec System Recovery (BESR) and Symantec System Recovery (SSR) Symantec Recovery Environment (SRD).

Error


When a non-system disk is restored, Disk Management in Windows can be used to convert the disk to dynamic. In some cases, it might be necessary to restore and preserve a Microsoft Dynamic Disk Volume from within the SRD using the Microsoft tool DISKPART.

Solution


The below process is written for non-system disks. If you are restoring an operating system volume, the option to make the partition bootable may be grayed out during in the SRD restore wizard. If this is the case, that partition should be restored (it will restore as a simple volume), booted into Windows, and Windows Disk Management used to convert the volume back to dynamic.
CAUTION: Be aware that the following steps DELETES the entire disk/drive/array of all volumes and data.

    1. Boot the system using the Symantec Recovery Disk (SRD) CD. 
    2. From the main menu select Analyze then Open Command Shell.
    3. In the command prompt type Diskpart and press Enter.
    4. Type List Disk and press Enter to list the available disks on this system.
    5. Note the disk number of the volume to create dynamic disks upon. 
    WARNING: If removable disks are present, to prevent possible data lost disconnect such drives. After disconnecting them type rescan and press enter. Return to step 4.

    6. Type Sel Disk # and press Enter; where # is the number of the disk from step 5.

    WARNING: 
    If you are sure the correct disk is selected then proceed to next step , the next step will wipe all info on selected disk

    7. Type Clean and press Enter; a message indicating the disk was successfully cleaned should appear.
    8. Type create partition primary and press Enter; a message indicating the primary partition was created should appear.
    9. Type convert dynamic and press Enter; a message indicating that the conversion was successful appears.
    10. Start the recovery wizard, restore the recovery point to the "unknown" volume; dynamic disks appear as "unknown" within SRD. 
    11. Reboot out of the SRD.
    12. In Windows choose Right click on My computer choose Manage from the context menu.
    13. Click Disk Management then right click on the foreign Disk; the disk to which the recovery point was just restored.
    14. Select import Foreign Disks | Assign and choose the appropriate drive letter.
     
ref: http://www.symantec.com/business/support/index?page=content&id=TECH69331

2012年5月9日星期三

SAS vs. SATA Differences, Technology and Cost

Here are the high-level differences between SAS and SATA disk drives:
Capacity:
  • SATA disk drives are the largest on the market.  The largest SATA drives available with widespread distribution today are 1.5TB-2TB.
  • SAS disk drives are typically smaller than SATA.  The largest SAS drives available with widespread distribution today are 450GB.
  • So, for capacity, a SATA disk drive is 3X-4x as dense for capacity than SAS.
  • A good way to quantify capacity comparison is $/GB.  SATA will have best $/GB.
Performance:
  • SATA disk drives spin at 7.2k RPMs.  Average seek time on SATA is 9.5msec.  Raw Disk IOPS (IOs per second) are 106.
  • SAS disk drives spin at 15k RPMs.  Average seek time on SATA is 3.5msec.  Raw Disk IOPS (IOs per second) are 294.
  • So, for performance, a SAS hard drive is nearly 3X as fast as SATA.
  • A good way to quantify performance comparison is $/IOP.  SAS will have best $/IOP.
Reliability: there are two reliability measures – MTBF and BER.
  • MTBF is mean time between failures.  MTBF is a statistical measure of drive reliability.
  • BER is Bit Error Rate.  BER is a measure of read error rates for disk drives.
  • SATA drives have a MTBF of 1.2 million hours.  SAS drives have a MTBF of 1.6 million hours.  SAS drives are more reliable than SATA when looking at MTBF.
  • SATA drives have a BER of 1 read error in 10^15 bits read.  SAS drives have a BER of 1 read error in 10^16 bits read.  SAS drives are 10x more reliable for read errors.  Keep in mind a read error is data loss without other mechanisms (RAID or Network RAID) in place to recover the data.
ref: http://blog.lewan.com/2009/09/14/sas-vs-sata-differences-technology-and-cost/

Dell's Enterprise Hard Drives


http://www.dell.com/content/topics/topic.aspx/global/products/pvaul/topics/en/hard-drives?c=us&cs=555&l=en&s=biz&~tab=4