ccna upgrade exam

ccna upgrade exam.If the interface status is up and up, the interface is operating normally; if it is up and down, the problem is at the data link layer (Layer 2); if it is down and down, there is a problem at the physical layer (Layer 1); if it is administratively down and down, the interface has been disabled using the command shutdown. Hardware is refers to the physical layer (Layer 1) attributes of the interface, while Encapsulation refers to the data link layer (Layer 2) attributes of the interface. If the hardware type is LANCE, the interface is a Fast Ethernet interface (on older routers and switches) oIn the output of the command show interfaces, line 2 indicates the hardware interface type (in this case, Ethernet controller) and the MAC address of the interface. o Line 3 is the IP address and subnet mask configured on the interface (no such information is available for interfaces on Layer 2 switches). Line 4 is the MTU (Ethernet frame length) and routing protocol metric (these metrics are discussed in more depth in Chapters 14, 18, 19, and 20 when discussing routing protocols); the parameter BW in this line refers to the bandwidth of the link, which is used by routing protocols such as Open Shortest Path First (OSPF) and Enhanced Interior Gateway Routing Protocol (EIGRP) to make routing decisions. It is used in routing decisions by routing protocols such as Open Shortest Path First (OSPF) and Enhanced Interior Gateway Routing Protocol (EIGRP). For Ethernet, the value of this parameter is 10000 kbit/so The next line is the type of Layer 2 encapsulation (frame) used; for Ethernet, this could be ARPA (for TCP/IP), Subnet Access Protocol (SNAP), or SAP.Exam Point Be sure to familiarize yourself with the output of the command showinterfaces, where MTU refers to the maximum packet (not frame or data segment) length.Table 10.5 explains some of what is displayed by the command showinterfaces. Note that the output of the command may vary slightly depending on the IOS device and interface type. In the following example, notice that the switch port faO/O has a large number of input and CRC errors.Switch# show interfacesfa0/0FastEthernet 0/1 isup,line protocol isup (connected)Hardware isMCI Ethernet, addressis0000.OcOO.1234 MTU 1500 bytes, BW10000 Kbit, DLY 100000usee, rely255/255,load 1/255 EncapsulationARPA, loopbacknot set, keepalive set(10sec)Full-duplex, 100Mbpsz media type is10/100BaseTx inputflow-control isoff,outputflow-control isunsupported Lastinput 0:00:00,output 0:00:00,output hang never Lastclearing of "show interface" counters 0:00:00 Outputqueue 0/40,0 drops; inputqueue 0/75,0 drops Five minute inputrate 354000 bits/sec,335 packets/sec Five minute outputrate 357000bits/sec,328 packets/sec 12375packetsinput,1900414 bytes, 0 no bufferReceived 1133 broadcasts(0 multicasts)0 runts,0 giants,0 throttles 735 inputerrors,731 CRC, 0 frame, 0 overrun, 0 ignored, 0abortNote that the duplex mode and speed of the interface faO/O are configured to full duplex and 100Mbit/s respectively. If autodetect speed and duplex mode are used (the default setting), the line of output about duplex mode will contain the words autOo culprit maymay be a duplex mode mismatch with the other end.