Author Archive admin


دوره آموزشی CCNA

نام دوره : CCNA: Certified Cisco Network Associate -ICND1+ICND2

 تعداد ساعت : 60
شهريه : 8,000,000 ریال
ثبت نام دوره آموزشی امنیت CEH
سیلابس دوره

Module 1:Operation of IP Data Networks

  • Operation of IP Data Networks
  • Recognize the purpose and functions of various network devices such as Routers, Switches, Bridges and Hubs.
  • Select the components required to meet a given network specification.
  • Identify common applications and their impact on the network
  • Describe the purpose and basic operation of the protocols in the OSI and TCP/IP models.
  • Predict the data flow between two hosts across a network.
  • Identify the appropriate media, cables, ports, and connectors to connect Cisco network devices to other network devices and hosts in a LAN

Module 2:LAN Switching Technologies

  • Determine the technology and media access control method for Ethernet networks
  • Identify basic switching concepts and the operation of Cisco switches.
    • Collision Domains
    • Broadcast Domains
    • Types of switching
    • CAM Table
  • Configure and verify initial switch configuration including remote access management.
    • Cisco IOS commands to perform basic switch setup
  • Verify network status and switch operation using basic utilities such as ping, telnet and ssh.
  • Identify enhanced switching technologies
    • RSTP
    • PVSTP
    • Ethercnannels
  • Describe how VLANs create logically separate networks and the need for routing between them.
    • Explain network segmentation and basic traffic management concepts
  • Configure and verify VLANs
  • Configure and verify trunking on Cisco switches
    • DTP
    • Auto negotiation
  • Configure and verify PVSTP operation
    • describe root bridge election
    • spanning tree mode

Module 3:IP addressing (IPv4 / IPv6)

  • Describe the operation and necessity of using private and public IP addresses for IPv4 addressing
  • Identify the appropriate IPv6 addressing scheme to satisfy addressing requirements in a LAN/WAN environment.
  • Identify the appropriate IPv4 addressing scheme using VLSM and summarization to satisfy addressing requirements in a LAN/WAN environment.
  • Describe the technological requirements for running IPv6 in conjunction with IPv4 such as dual stack
  • Describe IPv6 addresses
    • Global unicast
    • Multicast
    • Link local
    • Unique local
    • eui 64
    • autoconfiguration

Module 4:IP Routing Technologies

  • Describe basic routing concepts
    • CEF
    • Packet forwarding
    • Router lookup process
  • Describe the boot process of Cisco IOS routers
    • POST
    • Router bootup process
  • Configure and verify utilizing the CLI to set basic Router configuration
    • Cisco IOS commands to perform basic router setup
  • Configure and verify operation status of a device interface, both serial and ethernet
  • Verify router configuration and network connectivity
    • Cisco IOS commands to review basic router information and network connectivity
  • Configure and verify routing configuration for a static or default route given specific routing requirements
  • Manage Cisco IOS Files
    • Boot preferences
    • Cisco IOS image(s)
    • Licensing
      • Show license
      • Change license
  • Differentiate methods of routing and routing protocols
    • Static vs. Dynamic
    • Link state vs. Distance Vector
    • Administrative distance
    • split horizon
    • metric
    • next hop
    • ip routing table
    • Passive Interfaces
  • Configure and verify OSPF (single area)
    • Benefit of single area
    • neighbor adjacencies
    • OSPF states
    • Discuss Multi area
    • Configure OSPF v2
    • Configure OSPF v3
    • Router ID
    • Passive interface
    • LSA types
  • Configure and verify EIGRP (single AS)
    • Feasible Distance / Feasible Successors /Administrative distance
    • Feasibility condition
    • Metric composition
    • Router ID
    • Auto summary
    • Path selection
    • Load balancing
      • Equal
      • Unequal
    • Passive interface
  • Configure and verify interVLAN routing (Router on a stick)
    • sub interfaces
    • upstream routing
    • encapsulation
  • Configure SVI interfaces

Module 5:IP Services

  • Configure and verify DHCP (IOS Router)
    • configuring router interfaces to use DHCP
    • DHCP options
    • excluded addresses
    • lease time
  • Describe the types, features, and applications of ACLs
    • Standard
      • Sequence numbers
      • Editing
    • Extended
    • Named
    • Numbered
    • Log option
  • Configure and verify ACLs in a network environment
    • Named
    • Numbered
    • Log option
  • Identify the basic operation of NAT
    • Purpose
    • Pool
    • Static
    • 1 to 1
    • Overloading
    • Source addressing
    • One way NAT
  • Configure and verify NAT for given network requirements
  • Configure and verify NTP as a client
  • Recognize High availability (FHRP)
    • VRRP
    • HSRP
    • GLBP
  • Configure and verify Syslog
    • Utilize Syslog Output
  • Describe SNMP v2 & v3

Module 6:Network Device Security

  • Configure and verify network device security features such as
    • Device password security
    • Enable secret vs enable
    • Transport
    • Disable telnet
    • SSH
    • VTYs
    • Physical security
    • Service password
    • Describe external authentication methods
  • Configure and verify Switch Port Security features such as
    • Sticky MAC
    • MAC address limitation
    • Static / dynamic
    • Violation modes
      • Err disable
      • Shutdown
    • Protect restrict
    • Shutdown unused ports
    • Err disable recovery
    • Assign unused ports to an unused VLAN
    • Setting native VLAN to other than VLAN 1
  • Configure and verify ACLs to filter network traffic
  • Configure and verify an ACLs to limit telnet and SSH access to the router

Module 7:Troubleshooting

  • Identify and correct common network problems
  • Utilize netflow data
  • Troubleshoot and correct common problems associated with IP addressing and host configurations.
  • Troubleshootand Resolve VLAN problems
    • identify that VLANs are configured
    • port membership correct
    • IP address configured
  • Troubleshoot and Resolve trunking problems on Cisco switches
    • correct trunk states
    • correct encapsulation configured
    • correct vlans allowed
  • Troubleshoot and Resolve Spanning Tree operation issues
    • root switch
    • priority
    • mode is correct
    • port states
  • Troubleshoot and Resolve routing issues
    • routing is enabled
    • routing table is correct
    • correct path selection
  • Troubleshoot and Resolve OSPF problems
    • neighbor adjancies
    • Hello and Dead timers
    • OSPF area
    • Interface MTU
    • Network types
    • Neighbor states
    • OSPF topology database
  • Troubleshoot and Resolve EIGRP problems
    • neighbor adjancies
    • AS number
    • Load balancing
    • Split horizon
  • Troubleshoot and Resolve interVLAN routing problems
    • Connectivity
    • Encapsulation
    • Subnet
    • Native VLAN
    • Port mode trunk status
  • Troubleshoot and Resolve ACL issues
    • Statistics
    • Permitted networks
    • Direction
      • Interface
  • Troubleshoot and Resolve WAN implementation issues
    • Serial interfaces
    • PPP
    • Frame relay
  • Troubleshoot and Resolve Layer 1 problems
    • Framing
    • CRC
    • Runts
    • Giants
    • Dropped packets
    • Late collision
    • Input / Output errors
  • Monitor NetFlow statistics
  • Troubleshoot etherchannel problems

Module 8:WAN Technologies

  • Identify different WAN Technologies
    • Metro Ethernet
    • VSAT
    • Cellular 3G / 4G
    • MPLS
    • T1 / E1
    • ISDN
    • DSL
    • Frame relay
    • Cable
    • VPN
  • Configure and verify a basic WAN serial connection
  • Configure and verify a PPP connection between Cisco routers
  • Configure and verify Frame Relay on Cisco routers
  • Implement and troubleshoot PPPoE

استوریج HP 3PAR StoreServ 7000 Storage


Have budget constraints forced you to settle for midrange storage with compromised performance and scalability? Is managing your storage taking up more and more time while delivering diminishing returns? The gold standard platform for Tier-1 storage has extended its offerings—delivering effortless, efficient, bulletproof, and future-proof storage for the entire midrange. HP 3PAR StoreServ 7000 Storage delivers the same industry-leading architecture chosen by 3 out of 4 of the world’s largest managed service providers (MSPs) with pricing that makes compromises a thing of the past.

Store all your data on a single system that supports advanced features including storage federation and automated tiering that enable you to start small and grow without disruption. Make storage effortless with models that give you a range of options that support true convergence of block and file protocols, all-flash array performance, and the use of solid-state drives (SSDs) tiered with spinning media.

What’s new

  • HP 3PAR File Persona Software Suite delivers a tightly integrated, converged solution for provisioning block storage volumes as well as file shares from a single capacity store
  • HP 3PAR Thin Deduplication with patented Express Indexing increases capacity efficiency, protects flash performance, and extends flash life span to make your SSD tier more cost-efficient
  • HP 3PAR StoreServ Management Console provides a modern look and consistent feel for all HP 3PAR StoreServ arrays, making management effortless
  • HP 3PAR Online Import now supports an effortless migration path to 3PAR StoreServ Storage from EMC Symmetrix VMAX as well as existing support for EMC CLARiiON CX4, EMC VNX, and HP EVA
  • Support for VMware Virtual Volumes (VVOLs) enables granular VM-level storage control, disaster recovery, and quality of service in VMware environments with VMware vSphere6
  • New 600 GB 15k FIPS encrypted HDD


Grow with Freedom in any Direction

One architecture and a single stack from midrange to high end.

Meet converged block, file, and object access.

Ease data migration with storage federation software.

Affordable entry pricing and non-disruptive scalability to four nodes.

Get Tier-1 Features, “Six-nines” Availability, and Data Mobility at a Midrange Price

Automated DR configuration protects your data with one step.

Mixed workload support increases consolidation opportunities.

Persistent technologies deliver high availability and Tier-1 resiliency.

Industry-leading thin technologies cut capacity requirements by up to 75 percent.

Automated sub-volume tiering optimizes service levels and reduces costs.

Simple to Install, Own, and Upgrade

Software suites simplify purchasing and lower costs.

HP 3PAR SmartStart and HP 3PAR Rapid Provisioning get you up and running in minutes.

Reconfigurable in just seconds without disruption.

Shares a single, simple management console with all HP 3PAR StoreServ Storage.

Manage Block, File, and Object access from a single interface for maximum agility.


استوریج HP 3PAR StoreServ 10000 Storage

استوریج HP 3PAR StoreServ 10000 Storage

سری HPE 3PAR 10000 یکی دیگر از محصولات SAN Storage است که از استاندارد پلاتینیوم برای استفاده از enterprise Tier 1 storage بهره می بردو برای کاربریهای Enterprise و برای کاربریهای Hybrid private cloud و ITaaS مورد استفاده قرار میگیرد و دارای پورت های پر سرعت فیبر نوری16GB/s است و بسته به مدل آن از 48 تا 96 عدد پورت فیبر نوری 16Gb/s در اختیار می گذارد. این محصول برای مجازی سازی بسیاری ایده آل بوده و آنرا به گزینه های بسیار مطلوب و قابل اطمینان تبدیل کرده است و با تکنولوژیهای به کار رفته در آن باعث کاهش 50 درصدی هزینه های اجرایی san storage می شود.
حداکثر فضای ذخیره سازی آن به صورت Raw Capacity نیز بسته به مدل انتخابی از 1600TB تا 3200TB است.
سری HPE 3PAR 10000 دارای 2 مدل به نام های 10400,10800 است که در جدول زیر به بررسی کاملتر این مدلها می پردازیم:

HPE PAR StoreServ 10000 Storage

HPE PAR StoreServ 10000 Storage2


NOTE: Support for SAS drives on HPE 3PAR StoreServ 10000 Storage is currently available with HPE 3PAR OS version 3.1.2 and later versions.
NOTE: Native FCoE support is available only for limited host configurations. Please check with your regional manager for more details
NOTE: A dedicated CNA is required for FCoE host connectivity
NOTE: The 1600TB and 3200 TB maximum raw capacity limits for the HPE 3PAR StoreServ 10400 and 10800 Storage respectively are applicable only to systems running HPE 3PAR OS version 3.1.3 or later
NOTE: Specifications are subject to change without notice
1- Each port is full bandwidth 8 Gbit/s or 16 Gbit/s Fibre Channel capable as aplicable
2- Recommended minimum is 32 drives which results in a 9.6 TB minimum raw capacity.
3- Maximum raw capacity currently supported with any and all drive types
4- For storage capacity, 1 GiB = 230bytes and 1 TiB = 1,024 GiB
5- RAID MP is HPE 3PAR Fast RAID 6 Technology
6- SSDs are Solid State Drives
7- SAS drives are Serial Access SCSI Drives
8- NL drives are Nearline (7.2k) disks
9- Recommended minimum is 4 drive chassis per pair of controller nodes
10- Each port is full bandwidth 10 Gbit/s iSCSI capable
11- Each port is full bandwidth 10 Gbit/s FCoE capable
12- Applies to the array storage assigned to 3PAR StoreServ File Controller for file services
13- For details, please refer to the 3PAR StoreServ File Controller v2 section in this document
14- Two built-in 1-GbE RCIP ports per node pair; maximum of 8 usable; RCFC works out of the FC Host ports





دوره آموزشی استوریج NetApp

با مشاهده این کورس آموزشی مبانی فناوری های Storage را خواهید آموخت ، همچنین بر استفاده از امکانات حیرت انگیز و بسیار مفید NetApp ( سخت افزارها و نرم افزارهای حیرت انگیز Storage ) در زمینه Storage مسلط خواهید شد.
با مشاهده این مجموعه آموزش می توانید خود را برای پاسخ به پروژه های بازار کار و همچنین شرکت و قبولی در آزمون NCSA ( NS0-145 ) آماده کنید.
مخاطب این مجموعه آموزش تکنسین ها ، مدیران و مهندسان شبکه هستند.

عنوان اصلی : NetApp Certified Storage Associate (NCSA) NS0-145

این مجموعه آموزش ویدیویی محصول موسسه آموزشی CBT Nuggets است که بر روی 1 حلقه DVD و به مدت زمان 7 ساعت و 5 دقیقه در اختیار علاقه مندان قرار می گیرد.
در ادامه با برخی از سرفصل های درسی این مجموعه آموزش NetApp Certified Storage آشنا می شویم :

آشنایی با این کورس آموزشی NCSA
مقدمه ای بر مباحث ذخیره سازی داده ها
آموزش مبانی DAS , NAS و SAN و مقایسه این موارد با یکدیگر
آشنایی با فناوریهای جدید ذخیره سازی همچون Cloud و مجازی سازی
آموزش مجازی سازی سرورها
آموزش مباحث iSCSI , SAS , FC , File Block Storage , HA , HPC
آموزش مبانی کلود و استفاده از آن در ذخیره سازی داده ها
پاسخ به نگرانی های شما در زمینه امنیت و حریم شخصی در استفاده از کلود
آشنایی با حوزه بسیار مهم Flash Storage
آشنایی با اجزای تشکیل دهنده و کارایی سیستم های Flash Storage
مروری بر تکنولوژی های SSD
آموزش در رابطه با Flash Endurance
آشنایی با 6 خط اصلی در محصولات NetApp برای پوشش دادن صنعت ذخیره سازی
آموزش استفاده از رابطهای گرافیکی موجود برای مدیریت محصولات NetApp
آموزش کار با سیستم عامل محصولات NetApp و کار با داده های کلاستر شده ONTAP
آشنایی با سیستمهای عامل جایگزین و تشریح و آشنایی با OnTAP 7-Mode و معماری آن
آشنایی با مبانی و اجزای سخت افزاری NetApp
آموزش کار با سری محصولات NetApp FAS2500
آموزش کار با NetApp Fabric Attached Storage
آموزش کار با دیگر محصولات NetApp
آموزش متصل شدن به System Manager و استفاده از آن به منظور مدیریت سیستم ها و سرویسهای مختلف
آموزش کار با رابط خط فرمانی
آموزش کار با Aggregates
آموزش بالابردن کارایی در استفاده از Flash Pools بدون نیاز به افزایش هزینه ها
آشنایی با تکنولوژیهای ساخت و مدیریت Volume ها در NetApp بویژه تکنولوژی FlexVol
استفاده از قابلیت های Qtrees برای پشتیبان گیری از محتوا و تنظیم مجوزهای امنیتی دسترسی دیگران
آموزش شیوه های محاسبه مقدار فضای قابل استفاده در دیسک سخت
آموزش استفاده از امکان SnapShot Copy
آموزش جامع و کاربردی مدیریت شبکه ( DNS , VLAN )
استفاده از تکنولوژی LUN برای ارائه فضای ذخیره سازی به کاربران به شکل درایوهای دیسک Local
آموزش استفاده از برنامه SnapDrive برای اتصال و مدیریت LUN ها
آموزش ایجاد کردن منابع NAS برای کلاینت های یونیکسی و ویندوزی به کمک NFS Exports و CIFS Shares
آموزش استفاده از BranchCache برای اتصال به دفاتر شرکت
آموزش ایجاد کردن محدودیت در میزان داده هایی که کاربران می توانند ذخیره نمایند
آموزش استفاده از شیوه دسترسی مبتنی بر نقش کاربر ( Role-Based Access Control — RBAC )
آموزش نگهداری و ترمیم سیستم ذخیره سازی NetApp
آموزش نظارت و نگهداری میزان فضای ذخیره سازی در NetApp
آموزش مفاهیم Clustered Data ONTAP
آموزش کار با رابط کاربری Clustered Data ONTAP
آموزش استفاده از Volume ها و Namespace ها در محیط Clustered ONTAP
آشنایی با قابلیت حیرت انگیز Clustered File Access
آموزش موازنه بار ( Load Balancing ) در فضای کلاستر شده
آشنایی با امکانات ویژه NetApp برای تکنولوژی SAN
مبحث FC Connectivity
آشنایی بیشتر با مدرک NCSA
پیشنهادات مدرس برای قبولی در آزمون NCSA
آشنایی با مباحث که به قبولی شما در آزمون کمک می کنند

ثبت نام دوره آموزشی امنیت CEH


کانفیگ کردن SAN Switch Zoning

در این پست به چگونگی انجام پیکربندی های ساده بر روی سوییچ های فیبر خواهیم پرداخت. مبنای این آموزش Zoning و تنظیمات مربوط به سطح دسترسی های میان HBA Host Bus Adapter های بر روی سرورها و HBA های سمت Storage Array خواهد بود.

نمونه ای که ما بر روی آن بحث میکنیم دارای چهار عدد سرورهای VMware ESX که هر کدام دارای دو کارت HBA می باشند که بصورت ضربدری متصل شده اند و به دو عدد سوییچ فیبر وصل شده اند.

در تصویر زیر دید کلی از محیط نصب را خواهیم دید مسیردهی ایده آل زمانی است که ما Node Name یا World Wide Node Name WWNN و شماره پورتها یا همان World Wide Port Name هر آداپتور را داشته باشیم و به بیان دیگر لازمه این کار این است که ما بدانیم کدام پورت با کدام WWNN ارتباط دارند.

در بالا WWPN و WWNN سرورها برای انجام Zoning در سوییچهای فیبر مورد نیاز می باشد. راه اندازی این قابلیت به امن تر شدن محیط و نیز اعمال محدودیت های لازم و مدیریت آسان و قابل درک کمک خواهد کرد. با راه اندازی این قابلیت دیگر هیچ درگیری ذهنی در خصوص نحوه تخصیص

LUN ها که بسیار به هم شبیه هستند و یا دارای کارکرد های مشابه هستند نخواهید داشت و ترکیب این دو پیکربندی باعث کانفیگ کردن ایده آل برای محیط شبکه SAN می باشد. شبکه ما دارای دو عدد سوییچ فیبر می باشد و دارای اطلاعات متفاوت WWNN و WWPN و Name و Alias و … می باشند.

ما از طریق یک Browser به سوییچ وصل می شویم البته قبلا باید یک آدرس IP بر روی کنسول آن ست کنیم و یا تولید کننده آن سوییچ یک آدرس IP بر روی آن بصورت پیش فرض ست شده است.

نام کاربری و کلمه عبور را وارد می کنیم

کنسول مدیریتی بصورت ذیل خواهد بود در این کنسول کلیات سوییچ و پورتهای استفاده شده و وضعیت کلی آنها را مشاهده می کنیم.

بر روی دکمه Switch Admin  کلیک می کنیم تا بتوانیم تنظیمات پایه را روی سوییچ انجام دهیم.

چگونگی تغییر نام سوییچ و یا تغییر آدرس IP سوییچ و آپدیت Firmware سوییچ ها با یک نسخه مشخص و استفاده ار لایسنس ها و یا تغییر پسورد USERID و نیز ایجاد کاربران جدید را در این مرحله می بینید. کلیه این قابلیت ها در تب های Switch – Network – Firmware – Download – License – User و با کلیک کردن بر روی گزینه Apply انجام می گیرد.

تغییرات کلی در وضعیت به ما اطلاع داده می شود و بدلیل اینکه این تغییرات را تایید کرده ایم ثبت و یادداشت کردن آنها ضروری می باشد.

ما از قبل اسم را تصحیح کرده ایم.

اگر ما کاربری از نوع Port Admin  باشیم می توانیم کلیه پورتهای موجود بر روی این سوییچ و یا سوییچ های دیگر را مدیریت کنیم.

از آنجا که پورتهای مشخص شده برای این کار داریم با پیش فرض Port Disabled کار را آغاز می کنیم و در این نمونه پورتهای سوییچ و خارجی بصورت Disabled  می باشند و ما می توانیم پورتهای مورد دلخواه را از طریق گزینه Persistent Enableروی آن Enable کنیم. در این حالت ما هیچ سرور وصل شده ای به پورتها را مشاهده نمی کنیم و آن بخاطر درایور های HBA و یا سیستم عامل آنها می تواند باشد.

پورت مورد نظر را Enable  می کنیم.

زمانی که پورت Enable  می شود یک Ack با متن Online نشان می دهد.

پیکربندی اصلی Zone Admin می باشد که در آن می توانیم نحوه دسترسی Device ها را در آن تعریف کنیم.

در Tab با نام Alias ما می توانیم کلیه Device های متصل به سوییچ را مشاهده نماییم که در مثال ما شامل چهار عدد سرور با کارتهای Qlogic HBA می باشند و چهار عدد دیگر از این اتصالات بر روی سوییچ دوم وجود دارد. با تنظیم Alias بر روی کارتهای HBA می توانیم براحتی اتصالات و Zone ها را تشخیص دهیم.

پس ابتدا بر روی دکمه New Alias کلیک می کنیم.

ما به اسم و Alias اشاره خواهیم کرد تا بتوانیم بهتر کارتهای HBA را از هم تشخیص بدهیم. در مثال ما دستگاه IBM N3300 با دو کنترلر UP و Down می باشد و طبق شکل نامگذاری می کنیم.

ما این HBA را انتخاب کرده ایم و آن را Add Member می کنیم.

Alias  با این Member مرتبط شده است.

و در این مرحله این کار را بر روی کلیه کارتهای HBA انجام می دهیم.

نام Alias Name را وارد کرده و سپس بر روی دکمه OK کلیک می کنیم.

مطابق شکل بالا HBA را Add Member می کنیم.

این کل کاری است که ما باید انجام دهیم.

زمانی که ما کلیه Alias ها را پیکربندی کردیم باید Area ها را ایجاد کنیم که این ناحیه ها می توانند اجازه ارتباط بین Alias ها را می دهد.

بر روی Tab با نام Zone کلیک کرده و Zone جدید را ایجاد می کنیم.

ما در این مثال به نام Zone اشاره کرده ایم و آن را ZONA_ESX01 نامگذاری کرده ایم و ترافیک میان کارت HBA سرور و استوریج را از خود عبور می دهد.

پس از این مرحله بر روی هر کدام از Alias های سرور و استوریج کلیک کرده و Add Member را کلیک می کنیم.

تنظیمات مربوط به Area ها را انجام می دهیم و در این محیط ترافیک و دسترسی بین سرور ESX و استوریج تعریف خواهد شد.

بنابراین ما یک Zone ایجاد می کنیم.

نام Area  و سپس OK

مرحله اضافه نمودن Member ها

مراحل آماده می باشند.

زمانیکه کلیه Area ها نصب شدند یک Global Configuration ایجاد می کنیم و آن را ذخیره و فعال می کنیم و به این منظور بر روی Tab مربوط به Zone Config می رویم.

نام Global Configuration ما در اینجا CONFIG_SW10 می باشد.

بر روی Area هایی که ایجاد و به عنوان Member به این Configuration اضافه کرده ایم Add Member می کنیم.

کلیه تنظیمات را از طریق Save Config نگهداری می کنیم.

تایید Zone Configuration

تنظیمات پیش فرض که در آن دسترسی ها کلا باز هستند و آن Effective Zone Config می باشد.

کانفیگ تولید شده توسط خودتان را انتخاب و بر روی OK کلیک نمایید.

کانفیگ فعال سازی می شود.

شکل سوییچ بعد از اعمال تغییرات

اگر شما عضو گروه Port Admin  باشید می توانید وضعیت پورتها را مشاهده کنید.

امیدواریم از این پستبهره لازم را برده باشید.

برای کسب اطلاعات بیشتر و یا ارائه مشاوره فنی با ما در ارتباط باشید.


بوت کردن سرور HP با فلش حاوی HP Smartstart

با توجه به اینکه درخواستهای بسیار زیادی از دوستان برای قرار دادن این پست شده بود تیم فنی و مهندسی وی سنتر تصمیم به قرار دادن این پست گرفت.

امیدواریم از این پست لذت ببرید.

Had long wanted to put this post, simplon thing as above, but many times we find (by saving issues) HP servers without CD, so before installing the operating system need to update the firmware on all components of the server with the HP Firmware Maintenance CD and later with the HP SmartStart CD prepare boot, install utilities and drivers from HP on the machine. In the case of not having a CD server can with an HP utility dump them to an external USB or flash drive.

The tool is called HP USB Key Utility, you can download from the official website HP. After downloading can install or remove it to run directly.

With this tool you can transfer images from CD-ROM or DVD-ROM drive to USB (pendrive).

We note that the minimum version is the 7.50 for both HP SmartStart CD cómo HP Firmware Maintenance CD.

Simply select CD / DVD USB drive origin and destination indicate!

From version 1.5 HP USB tool and can combine Smart Start and Maintenance firmaware and even several smart start x86 and x64 in one pendrive. Besides that must be the latest versions of Smart Start and Firmware Maintenance for these combinations.



نصب و راه اندازی HP BladeSystem

In this paper we see a system of servers already quite common in any environment more or less nice, not go into the issue of whether it is better for some environments or other, or if it is more convenient, simple, spend less… see an environment based on HP blades, this is a HP BladeSystem, any particular model and see all the settings that can be done from your OA, HP Onboard Administrator, will be the management console all the chassis, the ‘irons’, from this console can manage any component / element, and view its status at all times.

So by way of introduction, this is what would be a blade system, that is a drawer where we put depending on the model 8 blades, 16… all in itself would be redundancy and compact, since it does not occupy the same 16 servers in a rack format 16 blades. We have so many power supplies as we need to feed the chassis, not individually, if not comprehensively, and fans to cool the environment. Could set by the sensors depending on the temperature more or less operating at speed, and power sources and depends on our environment we ride up the blades could be turned off if not needed (for example a VMware), with all that we can save a lot $$$ into electricity,air conditioners, physical space / racks,… I can see every blade (server) is in a bay, each server operating system would, totally independent of other blades (or not), we have a small display to view the status of all the chassis and to set some parameters. In the back we have the switches, since such servers prevent wiring, and wired ethernet are internal connections, and fiber, all switches are duplicated to prevent falls and have high redundancy. Besides having one or two chassis management devices, that is where we administer the system, from the so-called HP Onboard Administrator. Each HP BladeSystem es different, as well as between different manufacturers (an IBM BladeCenter example), but still the same ‘philosophy’ and are ‘almost’ set equal.

The question is first of all install the chassis (Irons) and then we start setting, for how to mount the bars there everyone who read the official doc if you do not know 😉 since in this document we perform configuration. After connecting the HP Onboard Administrator to switch him or us, we can connect to the default IP with the default username and password (admin / password). By this we understand that the first thing to change would be the IP for which we are interested and admin password. Another way would be from the Insight Display or display that has the chassis front panel, from there we can make basic changes such.

In “Rack overview” A brief summary of our chassis, of the items we have in him, a front and a rear. Come the name of our enclosure, and serial number and part number.

In “Enclosure information” shows the condition of the components, if we aluna warning or everything is OK.

In “Enclosure information, flange “Information” we can change the name of our chassis / BladeSytem / enclosure, or name that owns CPD. Besides the serial ebseñarnos, also indicates a support for chassis connections, UID LED on the identification, the connection port between the chassis rest of our CPD (we make the connection with the BladeSystem continue below) llamado Enclosure link downlink port, Enclosure and also have the uplink port that will link to connect to the upper chassis or to connect a computer if necessary.

In “Enclosure information”, flange “Virtual Buttons” can turn on or off LED Light UID, to indicate any administrator what unit must do their homework.

In “Enclosure information” > “Enclosure Settings”. is a summary of BladeSystem devices and see if we need one to connect / enable and firmware all, we must always consider that we can have the latest firmware and all common elements have the same firmware!

In “Enclosure information” > “Enclosure Settings” > “AlertMail” for that, as the name suggests, to activate email alerts of our chassis.

In “Enclosure information” > “Enclosure Settings” > “Device Power Sequence”, flange “Device Bays”, can enable the lighting of the blades in the chassis with a priority order.

In “Enclosure information” > “Enclosure Settings” > “Device Power Sequence”, flange “Interconnect Bays”, can enable the bays on the chassis connection (switches) with an order of priority.

In “Enclosure information” > “Enclosure Settings” > “Date and Time” to configure the time service of the chassis, be a manual or schedule an NTP time server or.

In “Enclosure information” > “Enclosure Settings” > “Enclosure TCP/IP Settings” is where you can configure the name, IP, netmask, gateway and DNS servers to the chassis, the Onboard Administrator.

In “Enclosure information” > “Enclosure Settings” > “Network Access” flange “Protocols”, are the connection protocols that will qualify to enter the chassis. We have web access with HTTP or HTTPS, seguro shell with SSH, Telnet y XML reply.

In “Enclosure information” > “Enclosure Settings” > “Network Access” flange “Trusted Hosts” if we enable only give access to the enclosure from these IP’s and not from the entire network.

In “Enclosure information” > “Enclosure Settings” > “Network Access” flange “Anonymous Data” simply if we enable chassis give you some information before it loguearnos, you can sign in to be information that interests us as Darla track 😉

In “Enclosure information” > “Enclosure Settings” > “Link Loss Failover”, if te Devices Onboard Administrator, and want to do that when the primary OA lose connection, al otro pass Onboard Administrator, we enable and indicate what time of seconds that pass without a network connection, primary OA (long as the network has secondary OA!),

In “Enclosure information” > “Enclosure Settings” > “SNMP Settings” in case we have configured our network monotorización system, to manage alerts, ads… Denial Nagios, was x put 😉

In “Enclosure information” > “Enclosure Settings” > “Enclosure Bay IP Adresses”, tab “Device Bays”, we configured the IP’s of the blades, not your operating system, if the iLO IP’s so we could later connect to each bay.

In “Enclosure information” > “Enclosure Settings” > “Enclosure Bay IP Adresses”, tab “Interconnect Bays”, we configured the IP’s of the rear chassis modules, of fiber switches, the ethernet…

In “Enclosure information” > “Enclosure Settings” > “Configuration scripts”, can import the configuration scripts to automate configuration chassis and do it faster, we import it from a file or from a URL.

In “Enclosure information” > “Enclosure Settings” > “Reset Factory Defaults”, because for that, to reset the chassis to the default settings from the factory,

In “Enclosure information” > “Enclosure Settings” > “Device Summary”, is one of the most commonly used screens to document a blade environment, is a summary of all the components that we have in our chassis, with the description, serial, part number, manufacturer, model, spare part number, firmware, hardware version… all, the blades, switches, power, coolers / fans, mezzanines of the blades, info of the chasis…

In “Enclosure information” > “Enclosure Settings” > “DVD Drive”, from here we can connect the CD / DVD of the chassis to a specific blade, case we need to get a CD / DVD on a particular blade. Man, is best done from the iLO connection… but tb is here 😛

In “Enclosure information” > “Active Onboard Administrator” tab “Status e Information”, we see the state of the chassis says, at temperatures of about, and others on our chassis.

In “Enclosure information” > “Active Onboard Administrator” tab “Virtual Buttons”, we have two buttons, one for the chassis completely Resetar, I hope this does not have to do ever, since there is no reason to reboot the entire chassis, or to turn on the LED UID information.

In “Enclosure information” > “Active Onboard Administrator” > “TCP/IP Settings”, is informational, on aand Onboard Administrator, network name information, and other IP data,

In “Enclosure information” > “Active Onboard Administrator” > “Certificate administration”, tab “Information” we have that, information on the certificate for the SSL web server.

In “Enclosure information” > “Active Onboard Administrator” > “Certificate administration”, tab “Certificate Request”, serve to generate a certificate our, using a self-signed certificate or CSR by power give it to a certificate authority for us to generate one ‘good’. And in the flange “Certificate Upload” I would climb.

In “Enclosure information” > “Active Onboard Administrator” > “Firmware Update”, could update the firmware of our chassis, if we want the, downgrade could make it, can upload it from a file of our team, from a URL or directly from a USB flash drive connected to the chassis.

In “Enclosure information” > “Active Onboard Administrator” > “System Log”, tab “System Log” We have everything that happens in our chassis, a LOG.

In “Enclosure information” > “Active Onboard Administrator” > “System Log”, tab “Log Options” LOG can redirect a server’s LOG’s, to a Kiwi Syslog type.

In “Enclosure information” > “Device Bays” we have all our blades, with their status, if the UID is on or not, bay number, state on / off, iLO IP address, and state of the DVD drive if it is connected or not.

In “Enclosure information” > “Device Bays” > BLADE > flange “Status”, have the information on our blade, if you would have some warning here would tell us what the problem, or if you have a high temperature. Certainly, if we select hardware element, we indicated in the drawing on the right on which device we, helps when we have enough elements or in the theme of the switches.

In “Enclosure information” > “Device Bays” > BLADE > flange “Information”, blade shows information in question, all of it is quite interesting, o a anotar, as the MAC or WWPN…

In “Enclosure information” > “Device Bays” > BLADE > flange “Virtual Devices”, we have different options on our blade power button, and turn it the UID.

In “Enclosure information” > “Device Bays” > BLADE > flange “Boot Options”, select the boot order of the blade, or next boot,

In “Enclosure information” > “Device Bays” > BLADE > flange “Log IML”, o Integrated Management Log, have the log’s of the blade, everything that happens will be recorded.

In “Enclosure information” > “Device Bays” > BLADE > “iLO” flange “Processor Information”, can do remote management of equipment, ideally to remotely control the computer, so we click on “Integrated Remote Console” for control of the team and to manage their devices or if we have it in Java JRE “Remote Console”.

We open in a new window control on remote computer, to do everything we need, mount remote units, connect CD / DVD the remote site, restart, shutdown…

In “Enclosure information” > “Device Bays” > BLADE > “iLO” tab “Event Log”, filtered records have a team at iLO.

In “Enclosure information” > “Device Bays” > BLADE > “Port Mapping”, tab “Graphical View” we can see the internal connections of the blade, This screen is used to understand the inner connection between the blade and the switches we have in our chassis, we can see the blade adapters (Embedded or integrated and Mezzanines) each with its internal ports, are usually additional network cards or HBA’s (fiber) with one or more ports. And each port on each adapter looks at what port or ethernet fiber switch is connected.

In “Enclosure information” > “Device Bays” > BLADE > “Port Mapping”, tab “Table View” have the same information as in the previous tab but different view 😉

In “Enclosure information” > “Interconnect Bays” shows the chassis switches, back, in my case, two swtiches Ethernet and two fiber, shows the state of them, and if you have the power UID, switch type and model, su IP address management.

In “Enclosure information” > “Interconnect Bays”tab “Status” can view the status and diagnostic switch in question, if you have any electrical issues alert, Temperature…

In “Enclosure information” > “Interconnect Bays” > Bay ethernet > tab “Information” see it, information about this device, certain to score in the correct documentation or to arrange a future of trouble,

In “Enclosure information” > “Interconnect Bays” > Bahia ethernet , flange “Virtual Buttons” same as above, is a virtual button to turn off / reboot the device or to turn on the UID if necessary,

In “Enclosure information” > “Interconnect Bays” > Bahia ethernet > “Port Mapping” we can see the blades we have connected to this ethernet switch indicating which mezzanine what blade is what switch port, MAC also shows the device in question, and if a switch would display the WWNN fiber.

In “Enclosure information” > “Interconnect Bays” > Bahia ethernet > “Management Console”, We initiate the switch management console, and would switch level configuration, to set it up the zoninga that interest, through “HP Virtual Connect Manager”,

In “Enclosure information” > “Interconnect Bays” > BAY fiber > tab “Status”, can view the status and diagnostic fiber switch in question, if you have any electrical issues alert, Temperature…

In “Enclosure information” > “Interconnect Bays” > BAY fiber > tab “Information” see it, information about this device, certain to score in the correct documentation or to arrange a future of trouble,

In “Enclosure information” > “Interconnect Bays” > BAY fiber, flange “Virtual Buttons” is the virtual button to turn off / reboot the device or to turn on the UID if necessary,

In “Enclosure information” > “Interconnect Bays” > BAY fiber > “Port Mapping” we can see the blades we have connected to this ethernet switch indicating which mezzanine what blade is what switch port, also shows the connected HBA WWNN, perfect to have everything well documented and annotated for configuration issues paths.

In “Enclosure information” > “Interconnect Bays” > Bahia ethernet > “Management Console”, We initiate the switch management console fiber, and would switch level configuration, to set it up the zoninga that interest, we have a tutorial here on how to configure a switch fiber,

In “Enclosure information” > “Power and Thermal” see the status of the chassis electrical issue, and su temperature and in case of any mistakes we mark with error.

In “Enclosure information” > “Power and Thermal” > “Power Management” We can manage the configuration of the redundancy on the chassis power, so as to enable “Dynamic Power” for putting cost savings F.A. you do not need a standby state not to use them unless necessary. Note, it sounds a tall tale with this issue of saving or putting virtualization topics such chassis, saving is true, just take a calculator and multiply the servers so you spend so worth the hour kilowatt (kWh) and you can amaze with the costs in one year! all this you must add the cost of air conditioning of course… if we reverse, there is nothing better than a blade virtualization environment.

In “Enclosure information” > “Power and Thermal” > “Enclosure Power Allocation” spending shows us that we need the items currently in the chassis, our blades, switches, modules… and what would be our total capacity. One should always keep in mind that if we damaged a power supply, if we covered!

In “Enclosure information” > “Power and Thermal” > “Power Meter”, tab “Graphical View” shows a graph of our chassis consumption,

In “Enclosure information” > “Power and Thermal” > “Power Meter”, tab “Tablel View” records shows a consumption of our chassis,

In “Enclosure information” > “Power and Thermal” > “Power Subsystem” shows the status of all our power supplies, and the power mode, and if we would have redundancy.

In “Enclosure information” > “Power and Thermal” > “Power Subsystem” > “Power Supply X” will show specific information and a power source in question as its capacity / consumption, serial, part number, spare part number…

In “Enclosure information” > “Power and Thermal” > “Thermal Subsystem” tab “Fan Summary” shows a generic view of the fans or coolers that have our chassis and their use.

In “Enclosure information” > “Power and Thermal” > “Thermal Subsystem” tab “Fan Zones”, shows areas of our chassis ventilation and whether they are covered or not by fans to cool the area, normal is placed behind the blades fans, because it does not make much sense to place them on the other side, sometimes anyway not us who assemble the chassis if not an HP engineer, so not all our decisions 😉

In “Enclosure information” > “Power and Thermal” > “Thermal Subsystem” > “Fan X” and shows the individual status of each fan or cooler, and their use,

In “Enclosure information” > “Users / Authentication” > “Local Users” we have a local user management on the chassis, manage access to blade environment.

In “Enclosure information” > “Users / Authentication” > “Local Users” > “Directory Settings”, to configure access instead of local users with service users through LDAP Directory,

In “Enclosure information” > “Users / Authentication” > “Local Users” > “Directory Groups” to manage groups of users from LDAP,

In “Enclosure information” > “Users / Authentication” > “Local Users” > “SSH Administration”, manages the keys for SSH,

In “Enclosure information” > “Users / Authentication” > “Local Users” > “HP SIM Integration” > sirve para integrar el Onboard Administrator con HP Systems Insight Manager, to pass credentials.

In “Enclosure information” > “Users / Authentication” > “Local Users” > “Signed in Users” shows the currently logged users on the chassis of blades or historic logins,

In “Enclosure information” > “Insight Display”, shows the small screen that has the front of the chassis, a small display that will enable us to perform certain basic configurations with a couple of buttons, and view the status of the chassis briefly.

Well, the interesting thing is that if we set some of this is well documented, as well as for us to deliver to the customer and who come after us know what and how it is mounted, with logical drawings like this on the connections and documentation of IP’s, MAC’s, WWNN, WWPN, cabling… and perfectly in this structure would blade, more comfortable to manage and maintain! a bargain!!!


نصب و راه اندازی HP LeftHand

This paper vera certain generic configurations that allow these cabins HP SAN HP Lefthand calls, This case is made by a virtual booths under a VMware, and for working smoothly in an environment much more flexible laboratiorio. HP has several models cabinas Lefthand físicas, all with the same system, but with different capacities, Disk models, bocas ethernet… serían la serie HP LeftHand P4500 y HP LeftHand P4300. But also for production environments has the virtual cabin HP LeftHand P4000 Virtual SAN Appliance o VSA.

In this document we will see the main features of the cabins, such as the Storage clustering (gives higher performance and capacity), Network RAID (greater availability of data), Thin provisioning (reduces costs and improves the utilization of disk capacity), iSCSI (Ethernet technology) Snapshots and replication using Remote Copy (for local or remote replication, to improve the protection and availability of data).

This is the scenario that will be mounted in the wake of this document, be mounted four cabins SAN HP Lefthand, will create a multisite cluster type, create a LUN, RAID network configure replication to see that senses going and what it means, LUN’es to present the host. You will see how to create a snapshot of the LUN to use as a backup or dump it on another LUN, to use the SmartClone… what we need are as iSCSI across a private network environment where they will be booths and legs ethernet hosts that want to connect to them, clients / positions must not be connected to this network. The network should be at least 1GB to be supported and ideally have a 10Gb iSCSI network!

Good, we started the first cabin, have little configuration, with agregarles management IP address we would be better. So we started and when we asked for a login ‘start’.

We press the Enter here the “Login”,

And we will “Network TCP/IP Settings” > “eth0”, select “Use the following IP address” and specify the IP address for this cabin. “OK”,

“OK” to save changes,

“OK”, and with this we completed the minimum set in the cabins HP Lefthand.

Now what we have to do is connect to manage booths, we will use the Management Console calling cabs “HP LeftHand Centralized Management Console” the “HP LeftHand CMC”.

Instalando HP LeftHand Centralized Management Console,

The need to install Windows on a computer that is connected to the iSCSI network, and that management is on the private network iSCSI.

Installation is a simple wizard, we follow and have the console installed to manage our cabins independently or general level by the Management Group. “Next” to start the wizard,

Accept the license agreement “I accept the terms of the license Agreement”, “Next”,

Select custom installation marking “Custom” & “Next”,

Selected “Application” to install the console, optionally “SNMP Support” SNMP to audit with booths and “Documentation” for that, documentation & help. “Next”

Select the installation path, by default: “C:Archivos de programaLefthand NetworksUI”, “Next”,

If we icon…

If we want to open the console to finish & Miscellaneous,

A summary of the installation and click “Install” to finally start the installation of the management console,

… wait a few seconds while installing…


Open the console “HP LeftHand Centralized Management Console”

If this is the first time we open this console, we need to configure, namely, add storage arrays, create a group the various management groups, create a cluster, or create a LUN. All this we can do by attending. So first we have to add the cabins from “1. Find Nodes Wizard”

“Next” to start the wizard,

We can search the cabins for fixed IP address, name or directly we make a broadcast on the network to look for, I choose the first option, more comfortable.

From “Add…” add the IP range where are my cabins, and frame option “Auto Discover” So the next time you open the console I automatically save these cabins on the console, press “Finish”,

Well, We detected four cabins, with their names, IP’s… click on “Close” to close the wizard.

Then hit “2. Management Groups, Clusters and Volumes Wizard” to create, first administrative group to manage booths, second, create a cluster between interests us and the type that we are interested. And finally (optional) create the LUN’s.

“Next” to start the wizard,

We create a management group to our environment from “New Management Group” & “Next”,

We indicate the group a name and select booths belonging to want this administrative group, In principle it is interesting to add all cabs to work with them,

We create a username and a password to protect this administrative group, to only authorize us or who can manage, “Next”,

Configure group time, the interesting thing will be to use an NTP server on the network that have (un firewall, a domain controller…), in my case I set it up manually from the second option, “Next”,

Well, Here we set the type of cluster that we; if only we will have a site, location, select one “Standard Cluster”, in return, if we have at least two sites, physically separated, select one “Multi-Site Cluster”. In this paper we will multisite cluster,

We give a name to the cluster and select cabins (o storage node) we want to participate in balancing the information with our organization, selected in principle all,

But now we must set (if we) sites, or physical locations, for proper administration, so click on “New…” to create sites,

In my case I will create two sites and cabins will associate a site adding them to your location. Eye, must have the same cabin somewhere in the other sites, and of course the same model.

Well, shows no cabins available and teaches us that we have configured sites, “Next”,

We add from “Add…” an IP address (Virtual IP) for the cluster, that is where we connect to our iSCSI iniciaciadores,

Indicate an IP address and a netmask, “OK”,

The wizard also asks us if we want to create a volume and, a LUN, this is optional, but I prefer to do it later as it is not that I have neither space! So frame “Skip Volume Creation” & “Finish”,

… waited a while while creating the management group, unites all canbinas, creates the cluster…

Once, click on “Close” to manage this new environment.

Here we have the Management Group, with the cluster, nodes, and all settings that could manipulate,

If we want a computer to connect to our volumes or our LUN’es, first we have to discharge the initiator of that team, for this, we will “Servers” and Right “New Server…”

This Get, allow this computer to access the LUNs I tell you later, is a type to aliases, indicate their name, description, if it reads give access via iSCSI on, if we want to use the load balancing (that do not support all initiators), if we want to use CHAP on the, and the name of the originator or Initiator Node Name. The iSCSI initiator name you can get from the host properties that will be attached to cars. “OK”,

Las cabinas HP Lefthand, Managers need to have all the data correctly replicated cabins, to communicate with the storage cabinets,or fall to withstand different nodes… Being number quorum = n; N = Number of managers + 1. Manager is a process which controls the environment, associated with a management group. It is recommended that the number of Managers is odd, namely,in the configuration I have now, I have four cabins with manager initiated in each, Debere start a manager more, and I have the option (less desirable) de usar a Virtual Manager (that run under one of the cabins) and only be lifted manually and after dropping one of the nodes, so do not miss the quorum. Or else, have the option of using a Manger Failover, that this should be a part of the booths (advisable) at a third site (or at least network separate booths), yes would rise automatically when a fall from a node. This runs on a virtual machine in VMWare ESX or is a VMware Server.

So achieve that if a node drops, or two; have 3 manager’s raised and you can continue working on the current status of our organization and quorum remains.

And would select which node we want the Virtual Manager.

Good, we will create a volume, a LUN, order subsequently to iSCSI initiators and can work with our cabins share alamcenamiento. From “Volumes and Snapshots” with right “New Volume…”

Tab “Basic”, indicate the name of the volume, a description, a size that we want to give and that is what we want to present servers from “Assign and Unassign Servers…”. We recommend creating a volume with the size needed, because then you can resize and make it smaller or larger is very simple.

Select the server you want to see this record, mark “Assigned” and select the permissions you want to have, indicated for full access “Read/Write”, “OK”,

Tab “Advanced” important to indicate the type of replication that we want this LUN between nodes or cabins that is a characteristic of this type of cabins (see the image below for more detail). In addition to setting the priority of replication between the cabins “Availability” or availability “Redundancy” or redundancy. And the type of LUN, is primary or remote

The type of replication indicates how many times the data is to be copied, namely, 2-Way indicates that the information is duplicated, 3-The info will be tripled Way and 4-Way will cuatriplicada. Now, depends on the nodes that have to follow the patterns of writing, for it is better to seek our case. As we shall see, to have higher levels of replication, more room will be reserved, more we occupy our information but we will be much more protected.

This is the aspect of the newly created LUN.

On a volume, we can create snapshots or snapshots, to stay in a fixed point and could go back at any given time, losing the information that has been written subsequently. Or directly to rely on them to back serguridad (remote), we also present these snapshots to teams if our interest. To manually create a snapshot volume right “New Snapshot…”

We indicate the name of the snapshot, default uses the terminology of two SS to indicate that it is a snapshot. “OK”.

And these would be the options we have on a snapshot, Roll back the interesting 😉

We can see the performance of the cabins, or any member of our organization since “Performance Monitor” can add or remove counters to our graph.

Or for example, from “Use Summary” we can see a graph where the actual uses of our data, data reserved (or provisioned), but these snapshots, what is not used, the total size, Thin Provisioning or would use instead of the LUN Full’d see that I have different information.

The above, snapshots can do remotely, namely, they can be put in a volume, for this, volume on right “New Remote Snapshot…”

We have to keep the points we asked, first, click on “New Snapshot…” to create the snapshot,

Same as above, first create a snapshot, we name, “OK”,

And now we must specify a remote volume displaying the combo, if we do not have, will have to create one from “New Remote Volume…”

“Next” to select the management group,

Existing cluster (“Existing Cluster” & “Add a Volume to the Existing Cluster”), “Next”,

In this cluster, that automatically discovers, “Next”,

We put a name to this volume, and if we want to have replication or not your content, “Finish”,

We confirm and “Close”,

Now, we give “OK” and we will create a snapshot of the source volume and we will mount / copy as if it were another volume.

After a while of copies and replicas of information, see that we would have two volumes with the same information,

We can use another feature of the HP Lefthand cabins to create volumes SmartClone, this is to save space in our cabins. A practical example, if we have teams (servers x example) with the same base system, create a LUN for it, install the operating system on it and configurations necessary, this will occupy (2Eg Gb), if we have 10 2Gb for servers using the same information we are wasting 20Gb. The idea is to create a volume with this setup and create SmartClone, each server to use only the information you need using the base disk; each server and store your information in your individual LUN, without having to duplicate information senseless.

Good, for this, on a volume and with the information we want to use the other teams, Right “New SmartClone Volumes…”

First we make a snapshot “New Snapshot…”

Ditto, “OK”,

We indicate how we want to call this volume basis, the type that will supply the volumes that we create, for these environments is recommended to use “Thin”, and not “Full” to occupy what is used (so we can create more volumes with size not have available, very dangerous but can, may). Selected servers (iSCSI initiators) we want to see each SmartClone and permissions (the example graph is not adequate, since I did not have more teams to make the sample). We “OK”,

And if we go back to the graph before, see (in my case) or we are going to use more space than we dispobible! (eso es Thin Provisioning). Full Provisioning reserve all the space we assign a LUN, although not used.

Well, we can get through all the tabs you need console can also get information from our hardware, the status of their connections…

And if we drop a cab and have raised the Virtual Manager (o el Fault Manager) we will see how we can support simultaneous fall to two nodes at once.

To connect to this storage, if possible we will use the iSCSI initiator that provides HP Lefthand, since it allows a better balancing of the connections, although only for Windows, HP MPIO Lefthand DSM Dynamic Load Balancing, do dynamic balancing of obtaining data from different connections cabins. However with a traditional iSCSI initiator such as Microsoft iSCSI Initiator, redirected by asking the host cluster and bringing more liberated (Virtual IP Static Load Balancing).


محصولات F5


شرکت F5 که کار خود را با تولید محصولات Load Balancer در سال 1996 آغاز نمود ، توانست در سال 2010 میلادی در زمره 100 شرکت برتر در حال رشد آمریکا قرار گیرد و امروزه محصولاتش در تمام کشورهای دنیا مورد استفاده قرار میگیرد.از مهمترین محصولات این شرکت BIG-IP نام دارد که در ابتدا صرفا جهت load balancing و local traffic management مورد استفاده قرار میگرفت ، ولی اکنون دارای قابلیت هایی نظیر : کنترل دسترسی ، امنیت سیستم ها و برنامه ها ، فیلتر نمودن ایمیل ها و فرشده سازی هوشمند نیز میباشد .به گزارش گارتنر (Gartner) شرکت F5 هموراه در چند سال اخیر به عنوان پرچمدار بازار فروش تجهیزات و محصولات Application Delivery Controller و Application Delivery Networking بوده است .  f5_networks_logo شرکت
مروری بر محصولات :از مهم ترین محصولات این کمپانی می توان به BIG-IP اشاره نمود که یک اپلاینس شبکه بوده ( مجازی و یا سخت افزاری ) و روی آن سیستم عامل معروف F5 به نام TMOS یا Traffic Management Operating System اجرا میگردد . بر روی این محصول ماژول های گوناگونی نصب میگردد که در نهایت ماهیت و عمکلکرد BIG-IP را تعیین میکند .از آن جمله می توان به موارد ذیل اشاره نمود :
 f5 networks-viprion-4480 محصولات ·         Local Traffic Manager (LTM): Local load balancing based on a full-proxy architecture.·         Global Traffic Manager (GTM): Global server load balancing using DNS.·         Link Controller: Inbound and outbound ISP load balancing.·         Application Security Manager (ASM): A web application firewall.·         WebAccelerator: An asymmetric or symmetric advanced caching solution for HTTP and HTTPS traffic.·         Edge Gateway: An SSL VPN.

·         WAN Optimisation Module: A data centre symmetric WAN optimization solution.

·         Access Policy Manager (APM): Provides access control and authentication for HTTP and HTTPS applications.

از محصولات دیگر میتوان به FirePass نیز اشاره نمود که یک دستگاه SSL VPN میباشد . SSL VPN نسبت به IPsec VPN مزایای قایل توجهی دارد . محصول FirePass به صورت مجازی نیز ارائه میگردد .خانواده ARX نیز از محصولات دیگر این کمپانی بوده گه جهت سرویس دادن فایل ها به صورت مجازی و به عنوان یک واسط با پروتکل های CIFS و NFS ارائه سرویس مینماید . گروه فنی و مهندسی وی سنتر فروش تجهیزات F5 را در ایران انجام می دهد  و با در اختیار داشتن چندین Source و Supplier قوی در کشورهای متعدد به همراه تجربه و دانش فنی خویش ، نه تنها امکان تامین سریع محصولات این کمپانی را با قیمت مناسب داشته ، بلکه امکان پشتیبانی و آموزش های لازم نیز میسر میباشد .شما میتوانید جهت دریافت قیمت و زمان تحویل با ایمیل این آدرس ایمیل توسط spambots حفاظت می شود. برای دیدن شما نیاز به جاوا اسکریپت دارید مکاتبه نمایید .


شرکت مهندسین مشاور تکین توسعه کیان | امنیت نرم افزارهای تحت وب | F5 ASM محصول

معرفی محصول F5 Application Security Manager

امروزه با رشد و گسترش و همچنین تنوع در ترافیک وب سایت ها و در نتیجه افزایش حساسیت داده ها ما با چالش امنیت سرویس های تحت وب و امنیت برنامه های کاربردی روبرو خواهیم شد . با توجه به، آسیب پذیری های امنیتی و حملات و تهدیدات پیشرفته و جدید در چندین لایه شبکه محافظت از دارای های اطلاعاتی امری اجتباب ناپذیر در سازمان شما خواهد بود در عین حال حفظ شهرت شما با محرمانه بودن، در دسترس بودن، و عملکرد مناسب برنامه های کاربردی است که باعث اعتبار و پایداری در کسب و کار شما می شود.

محصول F5 BIG-IP® Application Security Manager یکی از منعطف ترین محصولات در زمینه امنیت وب سرویس ها و برنامه های کاربردی تحت وب معرفی می شود و همچنین از محصولات پر فروش و محبوب در بازار فن آوری می باشد.

این فایروال امنیت برنامه های وب را در محیط های مختلف شبکه از جمله مجازی ، رایانش ابری و همچنین خصوصی و شبکه های ساخت یافته تامین می کند.

BIG-IP® ASM حفاظت کاملی را در مقابل تهدیدات و آسیب پذیری های ناشناخته در جهت با لا بردن امنیت برنامه های کاربردی تحت وب و سرویس تحت وب فراهم کرده و سطوح دسترسی مناسبی به منابع در راه حل های دیتا سنتر فراهم می آورد

ویژگی های محصول F5 BIG-IP® Application Security Manager
اطمینان از امنیت وب و پایداری سرویس تحت وب:

    • • امکان شناسایی تهدیدات و حملات تحت وب بر اساس مکان مبدا حملات و همچنین حملات انکار سرویس به صورت نمایش گرافیکی و مقابله با جلوگیری از تزریق SQL و تهدیدات بر اساس OWASP Top Ten
    • • محافظت حداکثری در مقابل تهدیدات و حملات بر روی برنامه های تحت وب web 2.0

اطمینان از کارایی و پایداری برنامه های کاربری:

    • • امکان امنیت پیشرفته برای برنامه های کاربردی و افزایش کارایی وکاهش هزینه ها بر اساس حفاظت حداکثری
    • • امکان پایش و مانیتورینگ رفتار ها و اعمال کاربران برنامه های کاربردی تحت وب
    • • امکان بررسی فایل های بارگذاری شده از نظر آسیب پذیری و اثرات بد افزار ها

اطمینان از پیاده سازی سیاست ها به صورت متمرکز:

  • • امکان تعریف و ویرایش و گسترش سیاست های امنیتی به صورت متمرکز و ساخت یافته و کاربر پسند
  • • سازگاری و مطابقت با انواع استاندارد های مرتبط شامل (PCI DSS, HIPAA, Basel II, SOX )

در حال حاضرگروه تکتا کام شرکتی است که خدمات مشاوره،فروش، نصب پیشرفته ، آموزش و پشتیبانی محصولات F5 را به صورت یک Package یا به صورت جداگانه ارائه می نماید و تمامی مراحل کار را به صورت مستند شده در اختیار کار فرما قرار می دهد


نرم افزار مجازی سازی KVM


Kernel-Based Virtual Machine و یا به اصطلاح KVM به یک زیرساخت مجازی سازی برای Linux Kernel مورد استفاده قرار می گیرد و این هسته را به یک Hypervisor تبدیل می کند.

KVM به پردازنده هایی با قابلیت مجازی سازی سخت افزاری نیاز دارند.

KVM یک راهکار کامل مجازی سازی شرکت لینوکس بر روی سخت افزارهای X86 می باشد که دارای افزونه های لازم برای Intel VT و AMD-V می باشد.

با استفاده از KVM می توانید ماشین های مجازی بسیار زیادی را راه اندازی نمایید و هر ماشین از سخت افزار و منابع مخصوص خود استفاده کند.

KVM یک نرم افزار Open source می باشد و براحتی می توان کلیه تغییرات مورد نیاز را در هسته آن انجام داد.

اين ابزار متولد سال 2006 از روش مجازي سازي Para Virtual استفاده مي کند و مي تواند يک کارت شبکه ٬ پردازنده٬ هارد ديسک يا بخشي از دسکتاپ و ابزارهايش يا سيستم عامل را به صورت اختصاصي براي سيستم عامل ميهمان تعريف و در اختيار آن قرار دهد. سيستم عامل هاي اصلي روي اين ابزار٬ لينوکس و ويندوز هستند٬ اما سيستم عامل هاي ميهمان طيف وسيعي شامل نسخه هاي مختلف ويندوز٬ نسخه هاي مختلف لينوکس٬ بي اس دي٬ سولاريس٬مک و برخي از سيستم عامل هاي سرور تجاري هستند. در تصوير 7 کارکرد اين ابزار نمايش داده شده است. KVM از يک هسته اصلي لينوکس استفاده مي کند و براي سيستم عامل هاي ميهمان يک ارتباط ميان آن ها و هسته برقرار مي کند؛ به طوري که به نظر مي رسد هرکدام از آن ها در حال استفاده از يک هسته اختصاصي اما کوچک و مشخص شده هستند. KVM بيشتر براي مجازي سازي پروسه هاي خاص طراحي شده و با توجه به اپن سورس بودن و امکان کامپايل روي هسته لينوکس٬ بهترين ابزار براي توسعه دهندگان و برنامه نويسان است.

برای دانلود نرم افزار بر روی دکمه دانلود کلیک کنید.

دانلود نرم افزار آموزشهای دیتاسنتر