What good is IPv6?

Introduction to IPv6 – O’Reilly Media

# Bigger address space
# Support for mobile devices
# Built-in security

لینک آموزشی سیسکو

http://www.ciscobible.net/

Sybex – CCNA 640-802 PPT by Todd Lammle

http://www.ciscobible.net/archives/842

IPv6

http://www.laynetworks.com/ipv6.htm#

Block Size=256-Last number in Subnet Mask

Frame Relay concepts

Unlike LANs, you cannot send a data link layer broadcast
over Frame Relay. Therefore, Frame Relay networks are called nonbroadcast multiaccess
(NBMA) networks. Also, because Frame Relay is multiaccess, it requires the use of an
address that identifies to which remote router each frame is addressed.

The LMI is a definition of the messages used between the DTE (for example, a router) and the DCE (for example, the Frame Relay switch owned by the service provider)

■ Perform a keepalive function between the DTE and DCE. If the access link has a
problem, the absence of keepalive messages implies that the link is down.
■ Signal whether a PVC is active or inactive. Even though each PVC is predefined, its status can change. An access link might be up, but one or more VCs could be down. The router needs to know which VCs are up and which are down. It learns that information from the switch using LMI status messages.

Inverse ARP is disabled on each point-to-point subinterface by default.

As you willsee, Inverse ARP is not needed with point-to-point subinterfaces.
The subinterface numbers do not have to match on the router on the other end of the PVC,nor does the DLCI number.

Mapping via Inverse ARP or static frame-relay map statements is needed only when more than two VCs terminate on the interface or subinterface, because those are the only instances in which confusion about which DLCI to use might occur.

تغییر آزمون CCNA

http://www.ariasystem.net/index.php?option=com_content&task=view&id=27&Itemid=39

Chapter 10: Virtual LAN Concepts

 

Chapter 10: Virtual LAN Concepts

A virtual LAN (VLAN) is a broadcast domain created by one or more switches:

• To group users by department, or by groups that work together, instead of by physical location
  
• To reduce overhead by limiting the size of each broadcast domain
  
• To enforce better security by keeping sensitive devices on a separate VLAN
  
• To separate specialized traffic from mainstream traffic—for example, putting IP telephones on a separate VLAN from user PCs
  

 

• Port-based VLANs, the typical choice for configuring VLANs in a switch, can be done very easily, without needing to know the MAC address of the device. However, you need good documentation to make sure that you cable the right devices into the right switch port, thereby putting them in the right VLANs.
  
• A rarely used alternative for creating VLANs is to group devices into a VLAN based on MAC address. The engineer would discover all the MAC addresses of all the devices and then would configure the MAC addresses in the various switches, associating each MAC address with a VLAN. When a device moves to a different switch port and sends a frame, the device stays in the same VLAN.
  

   

   

When using VLANs in networks that have multiple interconnected switches, you need to use VLAN trunking between the switches. When sending a frame to another switch, the switches need a way to identify the VLAN from which the frame was sent. With VLAN trunking, the switches tag each frame sent between switches so that the receiving switch knows which VLAN the frame belongs to.

 

Trunking protocols:

• Inter-Switch Link (ISL)
  
• IEEE 802.1q.
  

 

with the encapsulated original Ethernet frame being unchanged

Because the original header is now longer, 802.1q encapsulation forces a recalculation of the original FCS field in the Ethernet trailer because the FCS is based on the contents of the entire frame.

 

both allow the use of a 12-bit-long VLAN ID field.

both support a separate instance of spanning tree for each VLAN.

802.1q did not support multiple spanning trees:

 

Although the concept of a VLAN and a subnet are indeed different concepts, they have a one-to-one relationship.

 

 

You might be thinking that using three interfaces on the router in Figure 10-7 seems wasteful—and it is. Alternately, you can use a router with a Fast Ethernet port that supports trunking and use a single physical connection from the router to the switch (trunking is not supported on 10 Mbps Ethernet interfaces).

 

You might be thinking that using three interfaces on the router in Figure 10-7 seems

wasteful—and it is. Alternately, you can use a router with a Fast Ethernet port that supports

trunking and use a single physical connection from the router to the switch (trunking is not

supported on 10 Mbps Ethernet interfaces).

The only difference between routing using a router and using a Layer 3 switch lies in the internal processing. Outwardly, nothing is different.

The switch ASICs (Application Specific Integrated Circuits) on an L3 switch have been built

 

Layer 4 Switching

The term Layer 4 switches (L4 switches) refers to a type of switching in which the switch considers the information in the Layer 4 headers when forwarding the packet. In some cases, the forwarding decision is based upon information inside the Layer 4 headers. In other cases, L3 forwarding is used, but the switch does accounting based on the Layer 4 headers. Both are considered to be Layer 4 switching.

it can also simply keep track of the numbers of packets and bytes sent per TCP port number, while still performing Layer 3 forwarding.

L4 switching does not always imply a change in how packets are forwarded. A switch can perform accounting to track the volumes of traffic per TCP and UDP port number but still make the decisions based on L3 switching logic. With Cisco switches, you can enable a feature called NetFlow switching, which performs the accounting based on Layer 4 information while forwarding traffic like a Layer 3 switch.

 

 

Layer 5-7 switching typically falls into a category of features and products that Cisco calls Content Delivery Networks (CDN).

Chapter 7

Chapter 7

IOS supplies network services to computers that use networked applications.

 

The cable from the console to a PC requires a special eight-wire cable, called a rollover cable, in which pin 1 connects to pin 8 on the other end of the cable, pin 2 connects to pin 7, and so on.

 

The login
command actually tells the router to display a password prompt.

 

Several concurrent Telnet connections to a router are allowed. The line vty 0 4 command signifies that this configuration applies to vtys (virtual teletypes/terminals) 0 through 4.Originally, IOS allowed for only these five vtys, unless the router was also a dial access server,such as a Cisco AS5300. At IOS Version 12.2, 16 vtys are allowed by default on all models of routers. Regardless, all the configured vtys typically have the same password, which is handy because users connecting to the router through Telnet cannot choose which vty they get. User exec mode is one of two command exec modes in the IOS user interface. Enable mode (also known as privileged mode or privileged exec mode) is the other. Enable mode is so named because the enable command is used to reach this mode, as shown in Figure 7-2; privileged mode earns its name because powerful, or privileged, commands can be executed there.

The key sequences in Table 7-4 are part of what Cisco calls enhanced editing mode. IOS enables enhanced editing mode by default and has for a long time. However, you can turn off these keystrokes with the no terminal editing
exec command, and turn them back on with the terminal editing command. Why would you bother? Well, occasionally, you might be using a scripting language to run commands automatically on the router through a Telnet session, and enhanced editing mode sometimes can interfere with the scripts. For the exam, just remember that you can enable and disable enhanced editing mode.

 

The debug
command actually tells the router to spend some CPU cycles to do things besides its normal functions…

 

When you use the debug command, IOS creates messages when different events occur and, by default, sends them to the console. These messages are called syslog messages. If you have used the console of a router for any length of time, you likely have noticed these messages— and when they are frequent, you probably became a little frustrated. You can view these same messages when you have Telnetted to a router by using the terminal monitor
command.

 

• Be aware that some debug options create so many messages that the IOS cannot process them all, possibly crashing the IOS. You might want to check the current router CPU utilization with the show process command before issuing any debug command. You also should know that the no debug all command disables all debugs. Before enabling an unfamiliar debug command option, issue a no debug all and then issue the debug that you want to use; then quickly retrieve the no debug all command using the up arrow or Ctrl-p key sequence. If the debug quickly degrades router performance, press Enter immediately, executing the no debug all command, to try to prevent the router from crashing.
  

 

The banner motd (motd stands for “message of the day”) command causes a text banner to display when someone accesses the router from the console, Telnet, or an auxiliary port.

 

■ RAM—Sometimes called DRAM for dynamic random-access memory, RAM is used by the router just as it is used by any other computer: for working storage. The running or active configuration file is stored here.

■ ROM—This type of memory (read-only memory) stores a bootable IOS image, which typically is not used for normal operation. ROM contains the code that is used to boot the router until the router knows where to get the full IOS image or as a backup bootable image, in case there are problems.

■ Flash memory—Either an EEPROM or a PCMCIA card, Flash memory stores fully functional IOS images and is the default location where the router gets its IOS at boot time. Flash memory also can be used to store any other files, including configuration files.

■ NVRAM—Nonvolatile RAM stores the initial or startup configuration file.

copy {tftp | running-config | startup-config} {tftp | running-config | startup-config}

 

The copy command always replaces the existing file when the file is copied into NVRAM or into a TFTP server. In other words, it acts like the destination file was erased and the new file completely replaced the old one.

 

When the copy command copies a configuration file into RAM, the configuration file in RAM is not replaced. Effectively, any copy into RAM works just as if you typed the commands in the “from” configuration file in the order listed in the config file. In other words, it works as if the RAM configuration file and the newly copied files were merged.

 

Three key commands can be used to erase the contents of NVRAM. The write erase and erase startup-config commands are older, whereas the erase nvram: command is the more recent,

 

The show flash
command then can be used to verify the contents of Flash memory

 

Flash memory access time is much slower than RAM’s

 

In some cases, Flash memory can be in read-only mode. That is the case when a router loads only part of the IOS into RAM, to conserve RAM. Other parts of the IOS file are kept in Flash memory (Flash memory access time is much slower than RAM’s). In this case, if Flash memory must be erased to make room for a new image, the IOS could not continue to run. So, if the router is running from a portion of IOS in Flash memory, the router must be booted using IOS in ROM. Then the Flash memory is in read/write mode and the erase and copy processes can be accomplished. The copy tftp flash command in later releases of the IOS actually performs the entire process for you. In earlier releases, you had to boot the router from ROM and then issue the copy tftp flash command.

 

When using the limited-function IOS in ROM, the router is in a mode called Rxboot mode. Routers cannot route packets while in Rxboot mode, but it can send and receive IP packets like an IP host. So, one of two things must be true for the router to be capable of sending packets to the TFTP server. First, the TFTP server could reside on the same subnet as one of the interfaces on the router. Alternately, you could configure a default route on the router,

pointing to another router that is on one of the same subnets as the router in Rxboot mode.

 

Chapter 6: Fundamentals of TCP and UDP

 

Chapter 6: Fundamentals of TCP and UDP

TCP provides error recovery, but to do so, it consumes more bandwidth and uses more processing cycles. UDP does not do error recovery, but it takes less bandwidth and uses fewer processing cycles.

TCP provides:

• Multiplexing using port numbers
• Error recovery (reliability)
• Flow control using windowing
• Connection establishment and termination
• End-to-end ordered data transfer
• Segmentation

Multiplexing by TCP and UDP involves the process of how a computer thinks when receiving data.

The ports below 1024 are reserved for well-known applications, such as web servers.

Multiplexing relies on the use of a concept called a socket. A socket consists of three things: an IP address, a transport protocol, and a port number. So, for a web server application on Jessie, the socket would be (10.1.1.2, TCP, port 80) because, by default, web servers use the well-known port 80.

In Figure 6-3, Hannah and Jessie used three applications at the same time—hence, there were three socket connections open.

 

A socket on a single computer should be unique.

The window starts small and then grows until errors occur. The window then “slides” up and down based on network performance.

Notice that the web server must wait after sending the third segment because the window is exhausted.

This three-way connection-establishment flow must complete before data transfer can begin.

 

 

 

 

■ Connection-oriented protocol—A protocol either that requires an exchange of messages

before data transfer begins or that has a required pre-established correlation between two endpoints

■ Connectionless protocol—A protocol that does not require an exchange of messages and

that does not require a pre-established correlation between two endpoints

 

Many people confuse the real meaning of connection-oriented with the definition of a reliable, or error-recovering, protocol. TCP happens to do both, but just because a protocol is connection-oriented does not mean that it also performs error recovery. Table 6-4 lists some popular protocols and tells whether they are connected or reliable.

 

Ethernet included, the MTU is 1500 bytes.

IP and TCP headers are 20 bytes each, TCP typically segments large data into 1460 byte.

 

UDP data transfer differs from TCP data transfer in that no reordering or recovery is accomplished.