Friday, 31 January 2014

DTH - Direct To Home

DTH (Direct To Home)
DTH stands for Direct-To-Home television. DTH is defined as the reception of satellite programmes with a personal dish in an individual home.

A designation broader than DBS would be direct-to-home signals, or DTH. This has initially distinguished the transmissions directly intended for home viewers from cable television distribution services that are sometimes carried on the same satellite. The term DTH predates DBS and is often used in reference to services carried by lower power satellites which required larger dishes (1.7m diameter or greater) for reception.

How does DTH work?
A DTH network consists of a broadcasting centre, satellites, encoders, multiplexers, modulators and DTH receivers.

A DTH service provider has to lease Ku-band transponders from the satellite. The encoder converts the audio, video and data signals into the digital format and the multiplexer mixes these signals. At the user end, there will be a small dish antenna and set-top boxes to decode and view numerous channels. On the user's end, receiving dishes can be as small as 45 cm in diametre.

DTH is an encrypted transmission that travels to the consumer directly through a satellite. DTH transmission is received directly by the consumer at his end through the small dish antenna. A set-top box, unlike the regular cable connection, decodes the encrypted transmission.


Will DTH be cheaper than cable or more expensive?
DTH will be definitely more expensive than cable as it exists today.

Is DTH superior to cable TV?
Yes. DTH offers better quality picture than cable TV. This is because cable TV in Pakistan is analog. Despite digital transmission and reception, the cable transmission is still analog. DTH offers stereophonic sound effects. It can also reach remote areas where terrestrial transmission and cable TV have failed to penetrate. Apart from enhanced picture quality, DTH has also allows for interactive TV services such as movie-on-demand, Internet access, video conferencing and e-mail. 

Thursday, 30 January 2014

VSAT - Very Small Aperture Terminal

VSAT - VERY SMALL APERTURE TERMINAL 
A very small aperture terminal (VSAT), is a two-way satellite ground station or a stabilized maritime VSAT antenna with a dish antenna that is smaller than 3 meters. The majority of VSAT antennas range from 75 cm to 1.2 m. Data rates typically range from 4 kbit/s up to 16 Mbit/s. VSATs access satellite(s) in geosynchronous orbit to relay data from small remote earth stations (terminals) to other terminals (in mesh topology) or master earth station "hubs" (in star topology).

A VSAT network typically consists of a larger earth station, commonly referred to as a teleport, with hub equipment at one end and a Very Small Aperture Terminal (VSAT ) antenna with remote equipment at the other end. The network equipment can be divided into two sets of equipment connected by a pair of cables: the Outdoor Unit (ODU) and the Indoor Unit (IDU).

ODU
An ODU is the equipment located outside of a building and includes the satellite antenna or dish, a low noise block converter (LNB), and a block-up-converter (BUC). The LNB converter amplifies the received signal and down converts the satellite signal to the L band (950 MHz to 1550 MHz), while the BUC amplifies the uplink transmission when the antenna is transmitting.

IDU
The IDU equipment at the teleport usually consists of a rack-mounted hub system and networking equipment connected to terrestrial networks, like the PSTN or Internet backbone. There is also a device that converts between satellite and IP protocols for local LAN applications such as PCs, voice calls and video conferencing.
At the remote location, a router connects to a small VSAT antenna receiving the IP transmission from the hub over the satellite and converts it into real applications like Internet, VoIP and data.

Topologies
Network topologies define how remote locations connect to each other and to the hub. The link over the satellite from the hub to the remote is called the outbound or downlink transmission, whereas the link from the remote to the hub is referred to as inbound or uplink.
Satellite networks are primarily configured in one of these topologies:

Star (hub & spoke) Networks
In a star network topology the hub connects to the remote, where all communications are passed back through the hub. Virtually an unlimited number of remotes can be connected to the hub in this topology. Smaller, lower powered BUCs can be used at the remote end since they are only connecting back to the larger hub antenna.

Mesh Networks
A mesh network topology allows one remote VSAT location to communicate with another remote location without routing through the hub. This type of connection minimizes delay and often is used for very high quality voice and video conferencing applications.
With this topology, larger antennas are required and more power is needed to transmit, thereby increasing cost.

Hybrid Networks
A hybrid topology is a mix of star and mesh networking solutions. This topology allows the hub to send information to the remotes, with the remotes then able to communicate with other VSAT locations.

Point to Point Connectivity
Contrary to the networking topologies, a point-to-point topology involves a dedicated connection between two antennas. This topology is a direct pipeline with a set bandwidth capacity regardless of usage and is typically designed with Single Carrier per Channel (SCPC) technology.

Wednesday, 29 January 2014

HP SERVERS NIC TEAMING IN WINDOWS

HP Servers NIC Teaming in Windows

What is Teaming?
Teaming NICs is used when you need to group several NICs and make them act as one, Teaming NICs provide fault tolerance, reduce network spikes and eliminate single point of failures from your Servers, you can team 2 NICs or more and then provide a separate IP for Team NIC, below is the image of 4 NICs in our HP server.

Before we continue you can download and install HP Network Config Utility for your OS on HP Server from the following link 
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&prodTypeId=15351&prodSeriesId=3884319&prodNameId=3884320&swEnvOID=4064&swLang=13&mode=2&taskId=135&swItem=MTX-32efdf5d63764165932fbccf02

1. Open HP Network Config. Utlity
2. You can see from the image that only 2 NICs are connected. Select the      
    connected NICs and click on Team.



3. Teaming has been successful

4. Now click on Team NIC and click properties if you want to define what you 
    want to Team Type Selection and Transmit Loadbalancing.

5. Set Team Type Selection to Automatic, as HP NIC teaming is very 
    intelligent and understands the packet transmission.

6. Select Transmit Load Balancing Method

7. Set IP for NIC1 (10.10.0.110) & IP for NIC2 (10.10.0.111), we need to 
   configure the IP for the Team NIC, so we are going to assign IP for the 
   Team NIC as following 10.10.0.112.

There you go, we are done with the teaming configuration of HP Server, make sure you point users to Team NIC’s IP, the Team IP will then balance the load between the two NICs.

RHEV COMPARISON WITH VSPHERE 5.5 AND HYPER-V

RED HAT ENTERPRISE VIRTUALIZATION COMPARISON WITH VMWARE VSPHERE 5.5 AND MICROSOFT HYPER-V 2012
FEATURES
RED HAT ENTERPRISE VIRTUALIZATION
VMWARE VSPHERE 5.5
MICROSOFT HYPER-V 2012
HYPERVISOR
Bare-metal hypervisor can be installed directly on the server hardware without a full operating system.
Y
Y
Y
Small footprint of <200MB
Y
Y
N
Guest device drivers are optimized for virtualization, resulting in high performance network and disk operations.
Y
Y
Y
Red Hat
Enterprise Linux guests require installation of the Linux integration services.
Certified on all hardware certified for Red Hat Enterprise Linux, including the latest Intel Xeon and AMD Opteron chipsets
Y
Y
Y
SCALABILITY LIMITS
Per  Cluster



Cluster
200
32
64
Per Host



Max cores per host
160
160
160
Max Ram per host
3TB/host
4TB/host
4TB/host
Max virtual CPUs per host
No limit
4096
2048
Per virtual machine (VM)



Max vCPUs per VM
160 vCPU/vm
32 vCPU with standard or Enterprise Edition

64 vCPU with Enterprise Plus Edition
64 vCPUs/VM for Win 2012, Win 2008, and Win 7

32 vCPUs/VM for Linux requires the installation of the new Linux integration services
Max vRAM per VM
2TB/VM
1TB/VM
1TB/VM
GUEST OS SUPPORT
Guest OS Support
Windows Server 2003, 2008, 2010, 2012, Windows XP, 7 and 8 (32bit and 64bit)

Red Hat Enterprise Linux 3, 4, 5, 6 (x86 and x64)

Vendor support for SUSE Linux Enterprise Server 10, 11

Other OS are known to work and are community supported
Windows, Linux, UNIX (x86 and x64)

Windows XP, Vista, 7 and 8
Windows 2003, 2008, 2012 (certain SPs only) Windows XP, Vista, 7, and 8

SLES

Red Hat Enterprise Linux 5+, 6+ (certain releases only)

MEMORY MANAGEMENT
Memory overcommitment: Allows the allocation of more virtual memory to its VMs than the host has physical memory
Y
Y
Y
dynamic memory only available with some Microsoft operating systems
Memory page  sharing: Enables VMs with similar operating systems to share physical memory
Y
Y
N
Transparent huge  pages: Large  memory pages can be dynamically created for VMs that require them
Y
Y
N
MANAGEMENT FEATURES
High Availability



VM restart in case of host failure
Y
Y
Y
Restart order can be prioritized, allowing the most critical  VMs to be restarted first
Y
Y
Y
No single point of failure  for high availability
Y
Y
Y
Maintenance mode:  Guest VMs of hosts undergoing maintenance are  automatically migrated to other available hosts
Y
Y
Y
High availability for enterprise management module:  Automatic fail over  to stand-by management server in the event of a primary server failure
Y
Y
Y
MIGRATION



VM live migration
Y
Y
Y
Storage live migration
Y
Y
Requires Enterprise or Enterprise Plus
Y
WORKLOAD AND RESOURCE MANAGEMENT
System scheduler: Cluster policies  automatically distribute workload evenly  across cluster host servers
Y
Y
requires Enterprise or Enterprise Plus
Y
Power saver: During off-peak hours, concentrates VMs on fewer  hosts to save  power
Y
Y
requires Enterprise or Enterprise Plus
Y
Storage load balancing: Automatically balance storage I/O and storage capacity
Y
Y
requires Enterprise Plus
Y
Shared resource pools: CPU, memory, and storage resources are aggregated and managed at the cluster level.
Y
Y
Y
Hot add VM NICs, Disk: Add networks and disk storage to running VMs
Y
Y
requires Enterprise or Enterprise Plus
Y
Hot add VM vCPUs and RAM: Add more vCPUs and RAM to running VM (guest operating system and application must support feature)
N
Y
requires Enterprise or Enterprise Plus
N
IMAGE MANAGEMENT
Thin provisioning: Virtual disks don’t use all of their allowed space upon creation.
Y
Y
Y
Templates: VMs can be deployed from master installations.
Y
Y
Y
VM snapshots: Roll back patches and upgrades
Y
Y
Y
Live VM snapshots: Snapshot a running VM
Y
Y
Y
Import/export VMs in the standard OVF format
Y
Y
Y
VM conversion: Includes tools to convert VMs from other formats to native format
Y
Y
Y
VM backup:  Certified third-party solutions are available for backing up virtual servers (for both data and operating system backup).
Y
Y
Y
SYSTEM ADMINISTRATION AND CONTROL
Single view for centralized control
Y
Y
N
requires multiple management tools
Host and VM system monitoring and management
Y
Y
Y
Self service user portal: Provides administrative access to users for creating/running VMs and managing the environment
Y
N
requires purchase of VMware Lab Manager deprecated or vCloud Director with Enterprise Plus
Y
limited capability through SC2012 App Controller
Roles and permissions: Granular, inheritable, directory-based security roles  for all actions and objects
Y
Y
N
requires Authorization Manager
Identity management: User authentication domains supported
Y
choice  of Active directory, IPA, Red Hat Directory Services, or IBM Tivoli Directory Server
Y
Y
AD only
Remote console: Red Hat Enterprise Virtualization Manager includes access to VMs using a secure graphical console
Y
Y
Y
Remote network boot via PXE (Preboot Execution Environment)
Y
Y
Y
REPORTING AND MONITORING
Provides customizable reporting for historic usage, trending, and quality of service
Y
N
Requires vCenter CapacityIQ
Y
LIMITED
Alerts and notifications: Errors and warnings are immediately reported to administrators via email
Y
Y
Y
Logging: Supports remote logging and crash analysis
Y
Y
Y
Guest agents: Enables monitoring of VM health and status
Y
Y
Y
INTEGRATION, AUTOMATION, AND CUSTOMIZATION
API: Programmatic access to all management commands
Y
all open
N
some proprietary/closed, some open
N
some proprietary/closed, some open
Scripting and automation of management commands
Y
Linux Python-based CLI
Y
Powershell-based CLI
Y
Powershell-based CLI
Hooks: Used to run system commands or to execute scripts that modify VM operation
Y
Y
LIMITED
N
SECURITY
Kernel level: Includes SELinux and sVirt for an effective intrusion detection, isolation, and containment
Y
N
application layer security with add-on vShield products
N
application layer security
Small hypervisor footprint minimizes attack surface
Y
Y
Y
NETWORKING
Device support: All network hardware and interfaces are certified for Red Hat Enterprise Linux
Y
Y
Y
vLANs: Support for virtual LANs are inside the virtual infrastructure
Y
Y
Hyper-V Network Virtualization
Support for OpenStack Neutron networking
Y
Supports OpenvSwitch and Linux Bridge 2
N
Only supports VMware NSX 3
Y
Supports OpenvSwitch 4
Network offload: Offloads virtual networking and network I/O to compatible NIC hardware
Y
Y
Y
Supports jumbo frames
Y
Y
Y
STORAGE
Supports iSCSI, FC, and NFS shared storage infrastructure
Y
Y
Y
Includes native support for Red Hat Storage Server, including a built-in GlusterFS Storage domain and datacenter type that use Gluster as the storage back-end
Y
N
N
Storage multipathing: Redundant path to storage for fault tolerance and enhanced performance
Y
Y
Y
Local disk support
Y
Y
Y
Supports storage domains backed by POSIX-compliant file systems
Y
Y
Y
Shared disks: Includes disks that are shared by multiple VMs at the same time
Y
Y
Y
Direct LUN support: Provides the ability to directly attach any block device to a VM as a disk
Y
Y
Y