MCSE Bootcamp Training : mcse training windows 2003 ccna mcsa a+ certification mcsd and ...

About Virtual LANs

Virtual LANs enable network managers to group users logically rather than by physical location. A virtual LAN (VLAN) is an emulation of a standard LAN that allows data transfer and communication to occur without the traditional restraints placed on the network. It can also be considered a broadcast domain set up within a switch. With VLANs, switches can support more than one subnet (or VLAN) on each switch, and give routers and switches the opportunity to support multiple subnets on a single physical link. A group of devices that belong to the same VLAN, but are part of different LAN segments, are configured to communicate as if they were part of the same LAN segment. Layer 3 switching supports up to 244 VLAN subinterfaces per system.

VLANs enable efficient traffic separation and provide excellent bandwidth utilization. VLANs also alleviate scaling issues by logically segmenting the physical LAN structure into different subnetworks so that packets are switched only between ports within the same VLAN. This can be very useful for security, broadcast containment, and accounting.

Layer 3 switching software supports a port-based VLAN on a trunk port, which is a port that carries the traffic of multiple VLANs. Each frame transmitted on a trunk link is tagged as belonging to only one VLAN.

Layer 3 switching software supports VLAN frame encapsulation through the Inter-Switch Link (ISL) protocol and the 802.1Q standard on both the Catalyst 2948G-L3 and the Catalyst 4908G-L3 switch routers.

Figure 5-1 shows a network topology where two VLANs span a Catalyst 5500 switch and a Catalyst 2948G-L3 switch router. Both VLANs in this topology are bridged using the Inter-Switch Link (ISL) protocol.

Figure 5-1 VLANs Spanning Devices in a Network

Note Four adjacent Fast Ethernet ports on the Catalyst 2948G-L3 (such as Fast Ethernet 1 through 4 or Fast Ethernet 45 through 48) must all use the same VLAN encapsulation; that is, either ISL or 802.1Q.

Second Scenario

This scenario describes how to create a two-way recipient Connection Agreement between an Exchange Server 5.5 computer that is running in a separate Windows NT 4.0 domain and a new Windows 2000 Active Directory domain. This scenario requires at least a one-way trust relationship in which Windows 2000 Active Directory trusts the Windows NT 4.0 domain. However, to ease administrative effort, a two-way trust relationship is recommended.

Important: if your migration strategy is to have users log on to your newly-created Active Directory, then you can run the ADMT before you create your two-way recipient Connection Agreement. If you run a domain migration tool that migrates SidHistory such as ADMT before you create your two-way recipient Connection Agreement, you do not have to run the ADClean Utility. ADMT settings allow the Administrator to create enabled users with which a valid 5.5 mailbox can match.

To create a two-way recipient Connection Agreement between an Exchange Server 5.5 computer that is running in a separate Windows NT 4.0 domain and a new Windows 2000 Active Directory domain:

Perform all of the steps in the "First Scenario" section of this article.

Start the Windows 2000 Active Directory Users and Computers snap-in, and then confirm that Exchange Server 5.5 users have been replicated as disabled users. Note that these objects are located in the default import container that is specified on the From Exchange tab of the Recipient Connection Agreement.

Important: Do not enable these disabled users. These accounts are only place holders for the Exchange Server 5.5 mailboxes; these accounts are not security principals, and are not meant to be logged on to.

Determine which one of the following methods you want to use to migrate your user accounts to Windows 2000 Active Directory:

Upgrade the Windows NT 4.0 domain to Windows 2000.

Use the Active Directory Migration Tool (ADMT) to migrate users, including SidHistory.

Use a third-party migration utility that supports SidHistory migration.

After you migrate the users to Windows 2000 Active Directory, you can run the Active Directory Cleanup Wizard (ADClean) to merge the mail attributes from the ADC-created place holder accounts with your newly migrated users.

CCNA Boot Camp
CCNA Boot Camp

About Virtual LANs

mcse training CCNA A+ certification :

Second Scenario

CCNA Boot Camp CCNA Boot Camp

About Virtual LANs

mcse training CCNA A+ certification :

Second Scenario

CCNA Boot Camp
CCNA Boot Camp