Senin, 31 Maret 2008

CCNA TV

Save the Date: CCNA TV: Extending Switched Networks with VLANs, VTP and 802.1Q Trunks, Tuesday April 8, 2008

Join more than 40,000 CCNA Prep Center users for an hour long monthly online TV talk show.

Sign up now: Attendance space is limited, so visit the CCNA Prep Center and click “Register Now” under the Prep Center TV heading to reserve your space today.

Date: Tuesday, April 8, 2008
Time: 11 a.m. Eastern Time, 8 a.m. Pacific Time, and 16:00 GMT
Title: Extending Switched Networks with VLANs, VTP and 802.1Q Trunks

Agenda: The program will focus on the following objectives and is designed to provide information that will assist you in passing your CCNA exam. After the presentation, we’ll be taking live calls from YOU – the viewer— during our Q&A session. You may also submit questions electronically.

Objectives:

During the show, Cisco Experts will discuss:

  • Understanding VLANs
  • 802.1q Trunk Operation
  • Vlan Trunking Protocol (VTP) Overview
  • Configuring VLAN Trunking Features
  • Routing Between VLAN's


To learn more, visit the
www.cisco.com/go/prepcenter page.

Minggu, 09 Maret 2008

Remote Access to Layer 3 MPLS VPN Service

Many different options are available to connect remote users to a Layer 3 MPLS VPN service.The following remote-access solutions are some of the most common:

· Dial-in access via Layer 2 Tunneling Protocol (L2TP) Virtual Private Dialup Network (VPDN)

· Dial-in access via direct Integrated Services Digital Network (ISDN)

· DSL access using Point-to-Point Protocol over Ethernet (PPPoE), Point-to-Point Protocol over ATM (PPPoA), and VPDN (L2TP)

Dial-in Access Via L2TP VPDN

The VPDN solution provides dial-in access via a Public Switched Telephone Network (PSTN) or ISDN. This concept uses a tunneling protocol (such as L2TP) to extend the dial connection from a remote user and terminate it on an L2TP network server (LNS), which in this context is called a Virtual Home Gateway (VHG).

Figure 1 shows a high-level example of the VPDN concept.

Figure 1. Dial-in Using the VPDN Concept

Dial-in Access Via Direct ISDN

Direct ISDN access does not require the use of any tunneling protocol from the remote client to a Layer 3 MPLS VPN PE router, unlike the previous VPDN solution. Instead, a PPP link is established over the ISDN B channel directly to the PE router. The PE router obtains the remote client's credentials using CHAP and then forwards them to a RADIUS server for authentication. Upon successful authentication, the RADIUS server returns configuration parameters for the client (such as VRF name, IP address pool, and so forth). The PE router then creates a virtual-access interface for the PPP session based on local configuration and the information returned by the RADIUS server. The user CHAP authentication process then finishes, and the remote user is afforded access to the relevant VPN.

Figure 2 shows the direct ISDN access solution.

Figure 2. Direct ISDN Connectivity

DSL Access Using PPPoA or PPPoE and VPDN (L2TP)

Digital Subscriber Line (DSL) access is provided by terminating DSL connections using the L2TP VPDN architecture or via a direct connection to a PE router. This provides the infrastructure for large-scale DSL termination. Figure 3 shows the DSL connectivity option using the L2TP VPDN solution.

Figure 3. DSL Connectivity Using PPPoE or PPPoA


As shown in Figure 3, a remote-access client may access his or her Layer 3 MPLS VPN environment using PPPoE (if the CPE acts as a bridge) or PPPoA (if the CPE acts as a router). RFC 1483 routed (PPPoA) and bridged (PPPoE) encapsulation is used, and an L2TP tunnel is built from the receiving NAS/LAC to one of the LNSs within the service provider point of presence (POP).

ICMP

The Internet Control Message Protocol, or ICMP, described in RFC 792, specifies a variety of messages whose common purpose is to manage the network. ICMP messages might be classified as either error messages or queries and responses. Figure 1 shows the general ICMP packet format. The packets are identified by type; many of the packet types have more specific types, and these are identified by the code field. Table 1 lists the various ICMP packet types and their codes, as described in RFC 1700.

Figure 1. The ICMP packet header includes a type field, a code field that further identifies some types, and a checksum. The rest of the fields depend on the type and code.


Table 1. ICMP packet types and code fields.

Type

Code

Name

0

0

ECHO REPLY

3


DESTINATION UNREACHABLE

0

Network Unreachable

1

Host Unreachable

2

Protocol Unreachable

3

Port Unreachable

4

Fragmentation Needed and Don't Fragment Flag Set

5

Source Route Failed

6

Destination Network Unknown

7

Destination Host Unknown

8

Source Host Isolated

9

Destination Network Administratively Prohibited

10

Destination Host Administratively Prohibited

11

Destination Network Unreachable for Type of Service

12

Destination Host Unreachable for Type of Service

4

0

SOURCE QUENCH (deprecated)

5


REDIRECT

0

Redirect Datagram for the Network (or Subnet)

1

Redirect Datagram for the Host

2

Redirect Datagram for the Network and Type of Service

3

Redirect Datagram for the Host and Type of Service

6

0

ALTERNATE HOST ADDRESS

8

0

ECHO

9

0

ROUTER ADVERTISEMENT

10

0

ROUTER SELECTION

11


TIME EXCEEDED

0

Time to Live Exceeded in Transit

1

Fragment Reassembly Time Exceeded

12


PARAMETER PROBLEM

0

Pointer Indicates the Error

1

Missing a Required Option

2

Bad Length

13

0

TIMESTAMP

14

0

TIMESTAMP REPLY

15

0

INFORMATION REQUEST (Obsolete)

16

0

INFORMATION REPLY (Obsolete)

17

0

ADDRESS MASK REQUEST (Near-obsolete)

18

0

ADDRESS MASK REPLY (Near-obsolete)

30

-

TRACEROUTE

Example 1 and Example 2 show analyzer captures of two of the most well-known ICMP messagesEcho Request and Echo Reply, which are used by the ping function.

Example 1. ICMP Echo message, shown with its IPv4 header.
Internet Protocol, Src Addr: 172.16.1.21 (172.16.1.21),
    Dst Addr: 198.133.219.25 (198.133.219.25)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
    Total Length: 84
    Identification: 0xabc3 (43971)
    Flags: 0x00
    Fragment offset: 0
    Time to live: 64
    Protocol: ICMP (0x01)
    Header checksum: 0x8021 (correct)
    Source: 172.16.1.21 (172.16.1.21)
    Destination: 198.133.219.25 (198.133.219.25)
Internet Control Message Protocol
    Type: 8 (Echo (ping) request)
    Code: 0
    Checksum: 0xa297 (correct)
    Identifier: 0x0a40
    Sequence number: 0x0000
    Data (56 bytes)
 
0000  40 fd ab c2 00 0e 73 57 08 09 0a 0b 0c 0d 0e 0f   @.....sW........
0010  10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f   ................
0020  20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f    !"#$%&'()*+,-./
0030  30 31 32 33 34 35 36 37                           01234567

Example 2. ICMP Echo Reply.
Internet Protocol, Src Addr: 198.133.219.25 (198.133.219.25),
    Dst Addr: 172.16.1.21 (172.16.1.21)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
    Total Length: 84
    Identification: 0xabc3 (43971)
    Flags: 0x00
    Fragment offset: 0
    Time to live: 242
    Protocol: ICMP (0x01)
    Header checksum: 0xce20 (correct)
    Source: 198.133.219.25 (198.133.219.25)
    Destination: 172.16.1.21 (172.16.1.21)
Internet Control Message Protocol
    Type: 0 (Echo (ping) reply)
    Code: 0
    Checksum: 0xaa97 (correct)
    Identifier: 0x0a40
    Sequence number: 0x0000
    Data (56 bytes)
 
0000  40 fd ab c2 00 0e 73 57 08 09 0a 0b 0c 0d 0e 0f  @.....sW........
0010  10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f  ................
0020  20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f   !"#$%&'()*+,-./
0030  30 31 32 33 34 35 36 37                          01234567

Although most ICMP types have some bearing on routing functionality, three types are of particular importance:

· Router Advertisement and Router Selection, types 9 and 10, respectively, are used by the ICMP Router Discovery Protocol (IRDP), a protocol used by some operating systems (such as most versions of Microsoft Windows) to discover local routers.

· Redirect, ICMP type 5, is used by routers to notify hosts of another router on the data link that should be used for a particular destination. Suppose two routers, Router A and Router B, are connected to the same Ethernet. Host X, also on the Ethernet, is configured to use Router A as its default gateway; the host sends a packet to Router A, and A sees that the destination address of the packet is reachable via Router B (that is, Router A must forward the packet out the same interface on which it was received). Router A forwards the packet to B but also sends an ICMP redirect to host X informing it that in the future, to reach that particular destination, X should forward the packet to Router B. Example 3 shows a router sending a redirect.

Example 3. Using the debugging function debug ip icmp, this router can be seen sending a redirect to host 10.158.43.25, informing it that the correct router for reaching destination 10.158.40.1 is reachable via gateway (gw) 10.158.43.10.
Pip#debug ip icmp
ICMP packet debugging is on
ICMP: redirect sent to 10.158.43.25 for dest 10.158.40.1, use gw 10.158.43.100
Pip#
An occasionally used trick to avoid redirects on data links with multiple attached gateways is to set each host's default gateway as its own IPv4 address. The hosts will then ARP for any address, and if the address is not on the data link, the correct router should respond via proxy ARP. The benefits of using this tactic merely to avoid redirects are debatable; redirects are decreased or eliminated, but at the expense of increased ARP traffic.

Redirects are enabled by default in IOS and might be disabled on a per interface basis with the command no ip redirects.

Address Resolution Protocol

Routers pass packets across a logical path, composed of multiple data links, by reading and acting on the network addresses in the packets. The packets are passed across the individual data links by encapsulating the packets in frames, which use data-link identifiers (MAC addresses, for example) to get the frame from source to destination on the link. One of the major topics of this book concerns the mechanisms by which routers discover and share information about network addresses so that routing might take place. Similarly, devices on a data link need a way to discover their neighbors' data-link identifiers so that frames might be transmitted to the correct destination.

Several mechanisms can provide this information;[1] IPv4 uses the Address Resolution Protocol (ARP), described in RFC 826. Figure 1 shows how ARP works. A device needing to discover the data-link identifier of another device will create an ARP Request packet. This request will contain the IPv4 address of the device in question (the target) and the source IPv4 address and data-link identifier (MAC address) of the device making the request (the sender). The ARP Request packet is then encapsulated in a frame with the sender's MAC address as the source and a broadcast address for the destination (see Example 1).[2]

[1] NetWare, for example, makes the MAC address of the device the host portion of the network-level addressa very sensible thing to do.

[2] Like an IP broadcast, the MAC broadcast is an address of all ones: ffff.ffff.ffff.

Figure 1. ARP is used to map a device's data-link identifier to its IP address.


Example 1. An analyzer capture of the ARP Request depicted in Figure 1, with its encapsulating frame.
Ethernet II, Src: 00:30:65:2c:09:a6, Dst: ff:ff:ff:ff:ff:ff
    Destination: ff:ff:ff:ff:ff:ff (Broadcast)
    Source: 00:30:65:2c:09:a6 (AppleCom_2c:09:a6)
    Type: ARP (0x0806)
Address Resolution Protocol (request)
    Hardware type: Ethernet (0x0001)
    Protocol type: IP (0x0800)
    Hardware size: 6
    Protocol size: 4
    Opcode: request (0x0001)
    Sender MAC address: 00:30:65:2c:09:a6 (AppleCom_2c:09:a6)
    Sender IP address: 172.16.1.21 (172.16.1.21)
    Target MAC address: 00:00:00:00:00:00 (00:00:00_00:00:00)
    Target IP address: 172.16.1.33 (172.16.1.33)

The broadcast address means that all devices on the data link will receive the frame and examine the encapsulated packet. All devices except the target will recognize that the packet is not for them and will drop the packet. The target will send an ARP Reply to the source address, supplying its MAC address (see Example 2).

Example 2. An analyzer capture of the ARP Reply depicted in Figure 1.
Ethernet II, Src: 00:10:5a:e5:0e:e3, Dst: 00:30:65:2c:09:a6
    Destination: 00:30:65:2c:09:a6 (AppleCom_2c:09:a6)
    Source: 00:10:5a:e5:0e:e3 (3com_e5:0e:e3)
    Type: ARP (0x0806)
    Trailer: 15151515151515151515151515151515...
Address Resolution Protocol (reply)
    Hardware type: Ethernet (0x0001)
    Protocol type: IP (0x0800)
    Hardware size: 6
    Protocol size: 4
    Opcode: reply (0x0002)
    Sender MAC address: 00:10:5a:e5:0e:e3 (3com_e5:0e:e3)
    Sender IP address: 172.16.1.33 (172.16.1.33)
    Target MAC address: 00:30:65:2c:09:a6 (AppleCom_2c:09:a6)
    Target IP address: 172.16.1.21 (172.16.1.21)

Cisco routers will display ARP activity when the debug function debug arp is invoked, as shown in Example 3

Example 3. Router Aretha (172.21.5.1) responds to an ARP request from host 172.19.35.2.
Aretha#debug arp
IP ARP: rcvd req src 172.19.35.2 0002.6779.0f4c, dst 172.21.5.1 Ethernet0
IP ARP: sent rep src 172.21.5.1 0000.0c0a.2aa9, dst 172.19.35.2 0002.6779.0f4c Ethernet0
Aretha#


Figure 2 shows the ARP packet format. As the fields are described, compare them with the ARP packets in Example 1 and Example 2.

Figure 2. ARP packet format.

Hardware Type specifies the type of hardware, as specified by the IETF.[3] Table 1 shows some examples of some of the more common type numbers.

[3] All numbers in use in various fields throughout the TCP/IP protocol suite were originally listed in: J. Postel and J. Reynolds, "Assigned Numbers," RFC 1700, October 1994. This large document (230 pages) is a valuable reference, but is now a bit outdated. A current list of assigned numbers can be found at www.iana.org.

Table 1. Common hardware type codes.

Number

Hardware Type

1

Ethernet

3

X.25

4

Proteon ProNET Token Ring

6

IEEE 802 Networks

7

ARCnet

11

Apple LocalTalk

14

SMDS

15

Frame Relay

16

ATM

17

HDLC

18

Fibre Channel

19

ATM

20

Serial Link

Protocol Type specifies the type of network-level protocol the sender is mapping to the data link identifier; IPv4 is 0x0800.

Hardware Address Length specifies the length, in octets, of the data link identifiers. MAC addresses would be 6.

Protocol Address Length specifies the length, in octets, of the network-level address. IPv4 would be 4.

Operation specifies whether the packet is an ARP Request (1) or an ARP Reply (2). Other values might also be found here, indicating other uses for the ARP packet. Examples are Reverse ARP Request (3), Reverse ARP Reply (4), Inverse ARP Request (8), and Inverse ARP Reply (9).

The final 20 octets are the fields for the sender's and target's data-link identifiers and IPv4 addresses.

In the top screen in Example 4, the IOS command show arp is used to examine the ARP table in a Cisco router.

Example 4. The ARP table for three devices connected to the same network: a Cisco router, a Microsoft Windows host, and a Linux host.
Martha#show arp
Protocol  Address         Age (min)     Hardware Addr  Type  Interface
Internet  10.158.43.34           2     0002.6779.0f4c  ARPA  Ethernet0
Internet  10.158.43.1            -     0000.0c0a.2aa9  ARPA  Ethernet0
Internet  10.158.43.25          18     00a0.24a8.a1a5  ARPA  Ethernet0
Internet  10.158.43.100          6     0000.0c0a.2c51  ARPA  Ethernet0
Martha#
________________________________________________________________________
C:\WINDOWS>arp -a
 
Interface: 148.158.43.25
  Internet Address      Physical Address     Type
  10.158.43.1           00-00-0c-0a-2a-a9    dynamic
  10.158.43.34          00-02-67-79-0f-4c    dynamic
  10.158.43.100         00-00-0c-0a-2c-51    dynamic
_________________________________________________________________________
Linux:~# arp -a
Address                HW type          HW address           Flags   Mask
10.158.43.1            10Mbps Ethernet  00:00:0C:0A:2A:A9    C       *
10.158.43.100          10Mbps Ethernet  00:00:0C:0A:2C:51    C       *
10.158.43.25           10Mbps Ethernet  00:A0:24:A8:A1:A5    C       *
Linux:~#

Notice the Age column. As this column would indicate, ARP information is removed from the table after a certain time to prevent the table from becoming congested with old information. Cisco routers hold ARP entries for four hours (14,400 seconds); this default can be changed. The following example changes the ARP timeout to 30 minutes (1800 seconds):

Martha(config)# interface ethernet 0
Martha(config-if)# arp timeout 1800

The middle screen of Example 4 shows the ARP table of a Microsoft Windows PC, and the bottom shows the ARP table from a Linux machine. Although the format is different from the IOS display, the essential information is the same in all three tables.

ARP entries might also be permanently placed in the table. To statically map 172.21.5.131 to hardware address 0000.00a4.b74c, with a SNAP (Subnetwork Access Protocol) encapsulation type, use the following:

Martha(config)# arp 172.21.5.131 0000.00a4.b74c snap

The command clear arp-cache forces a deletion of all dynamic entries from the ARP table. It also clears the fast-switching cache and the IP route cache.

Several variations of ARP exist; at least one, proxy ARP, is important to routing.

Proxy ARP

Sometimes called promiscuous ARP and described in RFCs 925 and 1027, proxy ARP is a method by which routers might make themselves available to hosts. For example, a host 192.168.12.5/24 needs to send a packet to 192.168.20.101/24, but it is not configured with default gateway information and therefore does not know how to reach a router. It might issue an ARP Request for 192.168.20.101; the local router, receiving the request and knowing how to reach network 192.168.20.0, will issue an ARP Reply with its own data link identifier in the hardware address field. In effect, the router has tricked the local host into thinking that the router's interface is the interface of 192.168.20.101. All packets destined for that address are then sent to the router.

Figure 3 shows another use for proxy ARP. Of particular interest here are the address masks. The router is configured with a 28-bit mask (four bits of subnetting for the Class C address), but the hosts are all configured with 24-bit, default Class C mask. As a result, the hosts will not be aware that subnets exist. Host 192.168.20.66, wanting to send a packet to 192.168.20.25, will issue an ARP Request. The router, recognizing that the target address is on another subnet, will respond with its own hardware address. Proxy ARP makes the subnetted network topology transparent to the hosts.

Figure 3. Proxy ARP enables the use of transparent subnets.

The ARP cache in Example 5 gives a hint that proxy ARP is in use. Notice that multiple IPv4 addresses are mapped to a single MAC identifier; the addresses are for hosts, but the hardware MAC identifier belongs to the router interface.

Example 5. This ARP table from host 192.168.20.66 in Figure 3 shows multiple IPv4 addresses mapped to one MAC identifier, indicating that proxy ARP is in use.
C:\WINDOWS>arp -a
Interface: 192.168.20.66
  Internet Address      Physical Address     Type
  192.168.20.17         00-00-0c-0a-2a-a9    dynamic
  192.168.20.20         00-00-0c-0a-2a-a9    dynamic
  192.168.20.25         00-00-0c-0a-2a-a9    dynamic
  192.168.20.65         00-00-0c-0a-2c-51    dynamic
  192.168.20.70         00-02-67-79-0f-4c    dynamic

Proxy ARP is enabled by default in IOS and might be disabled on a per interface basis with the command no ip proxy-arp.

Gratuitous ARP

A host might occasionally issue an ARP Request with its own IPv4 address as the target address. These ARP Requests, known as gratuitous ARPs, have several uses:

· A gratuitous ARP might be used for duplicate address checks. A device that issues an ARP Request with its own IPv4 address as the target and receives an ARP Reply from another device will know that the address is a duplicate.

· A gratuitous ARP might be used to advertise a new data-link identifier. This use takes advantage of the fact that when a device receives an ARP Request for an IPv4 address that is already in its ARP cache, the cache will be updated with the sender's new hardware address.

· A router running Hot Standby Router Protocol (HSRP) that has just taken over as the active router from another router on a subnet issues a gratuitous ARP to update the ARP caches of the subnet's hosts.

Many IP implementations do not use gratuitous ARP, but you should be aware of its existence. It is disabled by default in IOS but can be enabled with the command ip gratuitous-arps.

Reverse ARP

Instead of mapping a hardware address to a known IPv4 address, Reverse ARP (RARP) maps an IPv4 address to a known hardware address. Some devices, such as diskless workstations, might not know their IPv4 address at startup. RARP might be programmed into firmware on these devices, allowing them to issue an ARP Request that has their burned-in hardware address. The reply from a RARP server will supply the appropriate IPv4 address.

RARP has been largely supplanted by Dynamic Host Configuration Protocol (DHCP), an extension of the Bootstrap Protocol (BootP), both of which can provide more information than the IPv4 address, and which, unlike RARP, can be routed off the local data link.