Sunday, 14 September 2014
CCNA 200-120 Exam Labs With Simulator
https://drive.google.com/file/d/0BxR3InYMbztvR3ZoMlQ0X3g5cWM/edit?usp=sharing
Wednesday, 10 September 2014
GNS3 Setup with Valid IOS
https://drive.google.com/file/d/0BxR3InYMbztvM0JnTUk5VHBtUkU/edit?usp=sharing
Thursday, 21 August 2014
Juniper Link aggregation Error:logical unit is not allowed on aggregate links ...
Error
root# commit
[edit interfaces ge-0/0/2]
'unit 0'
logical unit is not allowed on aggregated links
error: configuration check-out failed
During deployment I found an above error when i commit my config
Before going to create aggregation and deploying LACP on juniper switches you have to remove interfaces from unit 0.
Run below mentioned commands.
or remove all interfaces which you plan to be the part of aggregation group.
Then run the following commands.
root# edit chassis
{master:0}[edit chassis]
root# set aggregated-devices ethernet device-count 4
{master:0}[edit chassis]
root# commit
configuration check succeedscommit complete
{master:0}[edit chassis]
root# top edit interfaces
{master:0}[edit interfaces]
root# top edit interfaces
{master:0}[edit interfaces]
root# set ae0 unit ?
Possible completions:
<interface-unit-number> Logical unit number
{master:0}[edit interfaces]
root# set ae0 unit 0 family ethernet-switching
{master:0}[edit interfaces]
root# set ae0 aggregated-ether-options lacp active
root# set ge-0/0/1 ether-options 802.3ad ae0
{master:0}[edit interfaces]
root# set ge-0/0/2 ether-options 802.3ad ae0
{master:0}[edit interfaces]
root# commit
configuration check succeedscommit complete
{master:0}[edit interfaces]
Verification
root> show interfaces terse | match ae0
ge-0/0/1.0 up down aenet --> ae0.0
ge-0/0/2.0 up down aenet --> ae0.0
ae0 up down
ae0.0 up down eth-switch
{master:0}
root>
root# commit
[edit interfaces ge-0/0/2]
'unit 0'
logical unit is not allowed on aggregated links
error: configuration check-out failed
During deployment I found an above error when i commit my config
Before going to create aggregation and deploying LACP on juniper switches you have to remove interfaces from unit 0.
Run below mentioned commands.
- root#delete interfaces ge-0/0/0 unit 0
- root#delete interfaces ge-0/0/1 unit 0
or remove all interfaces which you plan to be the part of aggregation group.
Then run the following commands.
root# edit chassis
{master:0}[edit chassis]
root# set aggregated-devices ethernet device-count 4
{master:0}[edit chassis]
root# commit
configuration check succeedscommit complete
{master:0}[edit chassis]
root# top edit interfaces
{master:0}[edit interfaces]
root# top edit interfaces
{master:0}[edit interfaces]
root# set ae0 unit ?
Possible completions:
<interface-unit-number> Logical unit number
{master:0}[edit interfaces]
root# set ae0 unit 0 family ethernet-switching
{master:0}[edit interfaces]
root# set ae0 aggregated-ether-options lacp active
root# set ge-0/0/1 ether-options 802.3ad ae0
{master:0}[edit interfaces]
root# set ge-0/0/2 ether-options 802.3ad ae0
{master:0}[edit interfaces]
root# commit
configuration check succeedscommit complete
{master:0}[edit interfaces]
Verification
root> show interfaces terse | match ae0
ge-0/0/1.0 up down aenet --> ae0.0
ge-0/0/2.0 up down aenet --> ae0.0
ae0 up down
ae0.0 up down eth-switch
{master:0}
root>
Wednesday, 2 July 2014
CCNA New Track 200-120 Instructor Lab Manual
https://drive.google.com/file/d/0BxR3InYMbztvcGVqNHJObkxDUzg/edit?usp=sharing
CCNA EXPLORATION INSTRUCTOR LAB MANUAL
https://drive.google.com/file/d/0BxR3InYMbztvdU02Smt3eWRzNHc/edit?usp=sharing
Tuesday, 1 July 2014
Exchange Server 2010 Installation:Windows Server 2008 R2
Let us learn installing Exchange 2010 Sp2 on Windows Server 2008 R2 Sp1
I would install the Exchange 2010 Sp2 in a Environment where Exchange 2003 Server is already there .
Its as similar . where we need to prepare the legacy Exchange permission to get that installed and working properly
Step 1.
I installed Service pack 1 on Windows Server 2008 R2 where I can overcome without installing hotfixes for Exchange 2010
Prerequisites Differs with the operating Systems
This Technet article would provide you for other versions of operating systems
Step 2.
Download and Install “Microsoft Filter Pack” (64bit Version)
Step 3.
On the Start menu, navigate to All Programs > Accessories > Windows PowerShell. Open an elevated Windows PowerShell console (Right Click – Run as administrator), and run the following command.
Import-Module ServerManager
And Running this command for typical installation where all the roles will be installed HUB , CAS and Mailbox Servers
Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,Web-Asp-Net,Web-Client-Auth,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Http-Redirect,Web-Http-Tracing,Web-ISAPI-Filter,Web-Request-Monitor,Web-Static-Content,Web-WMI,RPC-Over-HTTP-Proxy -Restart
Step 4.
Reboot the Server
Now Prerequisites Installed successfully
Step 5.
Now open Command Prompt “Browse the Command prompt into the setup location”
and Run
setup /PrepareLegacyExchangePermissions or setup /pl
We run this as we prepare the legacy (Exchange 2003) Server permissions,
Running this command won’t harm your environment .
Befor Running this command make sure your Domain Function Level and Forest Functional level in Windows Server 2003 is in native mode and your Exchange 2003 is in native mode,
Otherwise , It won’t allow you to install Exchange 2010

Step 6.
Preparing the Schema
Setup.com /PrepareSchema

Step 7.
Preparing Active Directory
Setup.com /preparead /OrganizationName:”First Organization”
This Switch can be removed if you have an Exchange Server already in your Organization
/OrganizationName:”First Organization”
Or if you want to change the organization name . you can use this switch

Step 8.
Now prepare the domain
Setup.com /Preparedomain
If you have multiple domains run Setup.com /preparealldomains

Step 9.
Now Start the Setup

Step 10.
Choose Typical to Install HUB,CAS and Mailbox
Give a Check mark for Automatically install Windows Server roles

Step 12.
If this is my internetfacing server , Give the external domain name

Step 13.
If Exchange 2003 Exists in your Environment , you will get this option to configure mail flow between these Servers

Step 14.
Now Setup will Run for some time

Step 15.
Reboot your Server

Thanks
Regards
Admin
Monday, 30 June 2014
CCNA 200-120 Latest Dumps
https://drive.google.com/file/d/0BxR3InYMbztvRWx5TmZFa0tETFU/edit?usp=sharing
Friday, 13 June 2014
CCNP ROUTE SWITCH & TSHOOT PPT's
https://drive.google.com/file/d/0BxR3InYMbztva2FmT0ZNNF9HV0E/edit?usp=sharing
CCNA ROUTING & SWITCHING 200-120 PPT's
https://drive.google.com/file/d/0BxR3InYMbztvdDVqcU90TktYRnM/edit?usp=sharing
CCNA EXPLORATION OLD 640-802 PPT's
https://drive.google.com/file/d/0BxR3InYMbztvWllMUVBiTEhXRVE/edit?usp=sharing
CCNA Routing and Switching Bridging Materials:New Topics
https://drive.google.com/file/d/0BxR3InYMbztvVHEwZmxWaVNZS2c/edit?usp=sharing
Tuesday, 10 June 2014
ESXi 5.5 vs Hyper-V 2012 R2 Technology War
VMware has just announced the release of ESXi 5.5 and the contest with Hyper-V 2012 R2 couldn’t be any hotter. In this post, we will compare some of the configuration maximums for the two hypervisors. In addition to raising the limits within the hypervisor, each product has added a ton of new features to draw buyers and existing customers to purchase or upgrade to one of these products.
Thanks
Regards
Blog Admin

Scaling
System | Resource | Microsoft Hyper-V 2012 R2 | VMware vSphere 5.5 | |||
Free Hypervisor | Essential Plus | Enterprise Plus | ||||
Host | Logical Processors | 320 | 320 | 320 | 320 | |
Physical Memory | 4 TB | 4 TB? | 4 TB | 4 TB | ||
Virtual CPUs per Host | 2048 | 4096 | 4096 | 4096 | ||
Nested Hypervisor | ? | Yes | Yes | Yes | ||
VM | Virtual CPUs per VM | 64 | 8 | 8 | 64? | |
Memory per VM | 1 TB | 32 GB | 1 TB | 1 TB? | ||
Maximum Virtual Disk | 64 TB | 64 TB – 1% | 64 TB – 1% | 64 TB – 1% | ||
Hot-Add | Only disks* | Disks/vNIC/USB | Disks/vNIC/USB | All | ||
Active VMs per Host | 1024 | 512 | 512 | 512? | ||
Cluster | Maximum Nodes | 64 | N/A | 32 | 32? | |
Maximum VMs | 8000 | N/A | 4000 | 4000? |
Storage
Capability | Microsoft Hyper-V 2012 R2 | VMware vSphere 5.5 | ||
Free Hypervisor | Essential Plus | Enterprise Plus | ||
Thin disks | Yes (dynamic disks) | Yes | Yes | Yes |
Differential disks | Yes | No (only with API) | No (only with API) | No (only with API) |
SAN | iSCSI/FC | iSCSI/FC | iSCSI/FC | iSCSI/FC |
NAS | SMB 3.0 | NFS 3 over TCP | NFS 3 over TCP | NFS 3 over TCP |
Virtual Fiber Channel | Yes | Yes | Yes | Yes |
3rd Party Multipathing (MPIO) | Yes | No | No | Yes |
Native 4-KB Disk Support | Yes | No | No | No? |
Maximum Virtual Disk Size | 64TB (VHDX) | 64 TB – 1% | 64 TB – 1% | 64 TB – 1% |
Hot Virtual Disk resize | Yes (VHDX) | Yes (only increase) | Yes (only increase) | Yes (only increase) |
Virtual Disk sharing | Yes (VHDX) | Yes | Yes | Yes |
Maximum Pass Through Disk Size | 265TB+ | 64TB | 64TB | 64TB |
Storage Offload | Yes (ODX) | No | No | Yes (VAAI) |
Storage Virtualization | Storage Spaces | No (only 3rd part) | VSA and VSAN | VSA and VSAN |
Storage QoS | Yes | No | No | SIOC |
Storage Encryption | Yes | No | No | No |
Caching | Yes (CSV read-only cache) | No | No | Flash Read Cache |
Networking
Capability | Microsoft Hyper-V 2012 R2 | VMware vSphere 5.5 | ||
Free Hypervisor | Essential Plus | Enterprise Plus | ||
NIC Teaming | Yes | Yes | Yes | Yes |
Extensible Switch | Yes | No | No | Replaceable |
PVLAN Support | Yes | No | No | Yes (DVS or 3rd part) |
ARP/ND Spoofing Protection | Yes | No | No | vCNS/Partner |
DHCP Snooping Protection | Yes | No | No | vCNS/Partner |
Virtual Port ACLs | Yes | No | No | vCNS/Partner |
Trunk Mode to Virtual Machines | Yes | Yes | Yes | Yes |
Port Monitoring | Yes | Per Port Group | Per Port Group | Yes |
Port Mirroring | Yes | Per Port Group | Per Port Group | Yes |
Dynamic Virtual Machine Queue | Yes | NetQueue | NetQueue | NetQueue |
IPsec Task Offload | Yes | No | No | No |
SR-IOV | Yes | Yes (No Live Migration support) | Yes (No Live Migration support) | Yes (No Live Migration support) |
Network Virtualization | NVGRE | No | No | VXLAN / NSX |
Network QoS | Yes | No | No | DVS or 3rd part |
Quality of Service | Yes | No | No | Yes |
Data Center Bridging (DCB) | Yes | Yes | Yes | Yes |
High Availability & Resource control & Resiliency
Capability | Microsoft Hyper-V 2012 R2 | VMware vSphere 5.5 | ||
Free Hypervisor | Essential Plus | Enterprise Plus | ||
Nodes per Cluster | 64 | N/A | 32 | 32 |
VMs per Cluster | 8000 | N/A | 4000 | 4000 |
Virtual Machine Live Migration | Yes | No | Yes | Yes |
Shared-Nothing Live Migration | Yes | No | Yes (only from Web Client) | Yes (only from Web Client) |
CPU Compatibility for Live Migration | Per VM (only one baseline) | No | Cluster EVC (several baselines) | Cluster EVC (several baselines) |
Guest Clustering with Live Migration Support | Yes | N/A | No | No |
Automated Live Migration | Yes | N/A | N/A | Yes (DRS/DPM) |
Simultaneous Live Migrations | Unlimited | N/A | 4 (1GigE) or 8 (10GigE) | 4 (1GigE) or 8 (10GigE) |
Live Storage Migration | Yes | No | No | Yes |
Simultaneous Live Storage Migrations | Unlimited | N/A | N/A | 4 |
Hot and Incremental Backups | Yes | No (some 3rd part tools) | Yes | Yes |
VM Replication | Yes | No | Yes | Yes |
Integrated High Availability | Yes (Fail-Over Cluster) | No | Yes (VMware HA) | Yes (VMware HA) |
VM Lockstep Protection | No (3rd part tools) | No | No | Yes (VMware FT) |
Guest OS Application Monitoring | Yes | N/A | No | App HA |
HA handle storage failure | Yes | N/A | No | No |
Cluster-Aware Updating | Yes | N/A | Yes | Yes |
Failover Prioritization | Yes | N/A | Yes | Yes |
Resource Pool | Yes (host groups) | Yes | No | Yes (DRS is needed) |
Affinity & Anti-Affinity Rules | Yes | N/A | N/A | Yes |
Thanks
Regards
Blog Admin
Active Directory Administrative Center 2008 R2 & 2012
In the Windows Server® 2003 and Windows Server 2008 operating systems, administrators could manage and publish information in their Active Directory® environments by using the Active Directory Users and Computers Microsoft Management Console (MMC) snap-in. Beginning in Windows Server 2008 R2, in addition to using Active Directory Users and Computers, administrators can manage their directory service objects by using the new Active Directory Administrative Center.
You can use Active Directory Administrative Center to perform the following Active Directory administrative tasks:
- Create new user accounts or manage existing user accounts
- Create new groups or manage existing groups
- Create new computer accounts or manage existing computer accounts
- Create new organizational units (OUs) and containers or manage existing OUs
- Connect to one or several domains or domain controllers in the same instance of Active Directory Administrative Center, and view or manage the directory information for those domains or domain controllers
- Filter Active Directory data by using query-building search
Install Active Directory Administrative Center
You can install Active Directory Administrative Center any of the following ways:
- By default, when you install the Active Directory Domain Services (AD DS) server role through Server Manager
- By default, when you make a Windows Server 2008 R2 server a domain controller by running Dcpromo.exe
- With Remote Server Administration Tools (RSAT).
- Active Directory Administrative Center can be installed on computers running Windows Server 2008 R2 and Windows 7 or later. Active Directory Administrative Center cannot be installed on computers running Windows® 2000, Windows Server 2003, Windows Server 2008, or Windows Vista.
- You cannot use Active Directory Administrative Center to manage Active Directory Lightweight Directory Services (AD LDS) instances and configuration sets.
- For Windows Server 2012, Active Directory Administrative Center can be run on any computer that can run Remote Server Administration Tools.
- For Windows Server 2008 R2, Active Directory Administrative Center is available in the following editions:
- Windows Server 2008 R2 Standard
- Windows Server 2008 R2 Enterprise
- Windows Server 2008 R2 Datacenter
- Windows Server 2008 R2 Standard
- Active Directory Administrative Center is not available in the following editions of Windows Server 2008 R2:
- Windows Server 2008 R2 for Itanium-Based Systems
- Windows Web Server 2008 R2
- The Server Core option of any edition of Windows Server 2008 R2
- Windows Server 2008 R2 for Itanium-Based Systems
Manage Different Domains in Active Directory Administrative Center
To open Active Directory Administrative Center, in Server Manager, click Tools, and then click Active Directory Administrative Center.
"Another way to open Active Directory Administrative Center is to click Start, and then type dsac.exe."
To open Add Navigation Nodes, click Manage, then click Add Navigation Nodes as shown in the following illustration.
In Add Navigation Nodes, click Connect to other domains as shown in the following illustration.
- In Connect to, type the name of the foreign domain that you want to manage (for example, contoso.com), and then click OK.
- When you are successfully connected to the foreign domain, browse through the columns in the Add Navigation Nodes window, select the container or containers to add to your Active Directory Administrative Center navigation pane, and then click OK.
Thanks
Regards
Blog Admin
Subscribe to:
Posts (Atom)