tag:blogger.com,1999:blog-29773646844367732242024-03-11T21:51:47.328-07:00Belajar Cisco BersamaNgakakhttp://www.blogger.com/profile/08056581306532883030noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-2977364684436773224.post-65877003746266037192009-10-20T22:34:00.000-07:002009-10-20T22:34:48.151-07:00Routers: The IOS and Its User InterfaceBefore examining the IOS, a review of hardware and hardware terminology is useful. This<br />
section of the book reviews common hardware details.<br />
<br />
Most Cisco routers have a console and an auxiliary port. All Cisco routers have a console port,<br />
which is meant for local administrative access, from an ASCII terminal or computer using a<br />
terminal emulator. The auxiliary port, missing on a few models of Cisco routers, is intended for<br />
asynchronous dial access from an ASCII terminal or terminal emulator; the auxiliary port is<br />
often used for dial backup.<br />
Each router has different types of memory as follows:<br />
<a name='more'></a><br />
<b>• RAM</b><br />
—Sometimes called DRAM for<br />
dynamic<br />
random-access memory, RAM is used by<br />
the router just like it is used by any other computer—for working storage.<br />
<b>• ROM</b><br />
—This type of memory stores a bootable IOS image, which is not typically used for<br />
normal operation. ROM does contain the code that is used to boot the router until the<br />
router knows where to get the full IOS image.<br />
<b>• Flash memory</b><br />
—Either an EEPROM or a PCMCIA card. Flash memory stores full<br />
function IOS images and is the IOS default for where the router gets its IOS at boot time.<br />
Flash memory may also be used to store configuration files on Cisco 7500 series platforms<br />
(<br />
copy config flash<br />
).<br />
•<br />
<b>NVRAM</b><br />
—Nonvolatile RAM stores the initial or<br />
startup<br />
configuration file.<br />
All of these types of memory are permanent memory except RAM. There is no hard disk or<br />
diskette storage on Cisco routers. <br />
<br />
The processors in the routers vary from model to model. Although they are not specifically<br />
listed as requirements for the CCNA exam, some reference to terminology is useful. In most<br />
routers, the model number you order or own implies the processor speed; you would not then<br />
order a specific processor type or card. The exception to this is the 7000, 7200, and 7500 series<br />
of routers, for which you choose either a Route Switch Processor 1 (RSP-1), RSP-2, or RSP-4.<br />
In any case, the 2500 series, 3600 series, 4000 series, and 7xxx series all run the IOS. This<br />
commonality allows Cisco to have exams, such as CCNA, that cover the IOS features without<br />
having to cover many hardware details.<br />
Interfaces are used by a router for routing/bridging packets/frames through a router. The types<br />
of interfaces available change over time due to new technology. For example, packet-over-<br />
<b>SONET </b>and voice interfaces are relatively recent additions to the product line. However, some<br />
confusion exists about what to call the actual cards that house the physical interfaces.Ngakakhttp://www.blogger.com/profile/08056581306532883030noreply@blogger.com1tag:blogger.com,1999:blog-2977364684436773224.post-79540732331907371662009-10-20T22:22:00.001-07:002009-10-20T22:22:43.535-07:00What makes Cisco IOS Debug commands so useful?Cisco IOS Show commands can tell you many things about what is going on with your router or switch, but they can’t tell you everything. For example, Show commands cannot tell you when routes drop in or out of the routing table, why an ISDN line failed to connect, whether a packet really went out the router, or what ICMP error code was received. On the other hand, Cisco IOS Debug commands can tell you all these things, and more.<br />
Besides providing more detailed information than what Show commands can provide, Debug commands have the benefit of providing information in “real time” (or dynamically). This is contrary to Show commands that just take a snapshot in time and display the results on your console (somewhat static results). This real-time difference can be very helpful in diagnosing problems.<br />
<a name='more'></a><br />
<h2>How do I use Debug commands?</h2>Let’s take a look at a simple example. We are going to view RIP (Routing Information Protocol) in Debug mode.<br />
<pre>Router# debug ip RIP</pre><pre>RIP protocol debugging is on</pre>To verify what debugging is enabled, use this command:<br />
<pre>Router# show debug</pre><pre>RIP protocol debugging is on</pre>The output from whatever type of debug is enabled will be sent to wherever the Cisco IOS logging system tells that output to go. Either you will receive the output on your screen, it will go to the buffered log on the router, or it will go to a syslog server across the network (or all of these).<br />
To see what level the various outputs are set to and where the output will go, type:<br />
<pre>Router# show logging</pre><pre>Syslog logging: enabled (1 messages dropped, 3 messages rate-limited,</pre><pre>0 flushes, 0 overruns, xml disabled, filtering disabled)</pre><pre>Console logging: level debugging, 8 messages logged, xml disabled,</pre><pre>filtering disabled</pre><pre>Monitor logging: level debugging, 0 messages logged, xml disabled,</pre><pre>filtering disabled</pre><pre>Buffer logging: level warnings, 2 messages logged, xml disabled,</pre><pre>filtering disabled</pre><pre>Logging Exception size (4096 bytes)</pre><pre>Count and timestamp logging messages: disabled</pre><pre>Trap logging: level informational, 12 message lines logged</pre><pre>Log Buffer (51200 bytes):</pre><pre>*Jun 9 20:56:49.195: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up</pre><pre>*Jun 9 20:56:49.231: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up</pre><pre>Router#</pre>The console should display RIP updates that are sent and received through the RIP protocol. Here is an example of what you might see for RIP debugging:<br />
<pre>*Jun 9 21:13:56.471: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (1.1.1.1)</pre><pre>*Jun 9 21:13:56.471: RIP: build update entries - suppressing null update</pre><pre>*Jun 9 21:14:22.519: RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (1.1.1.1)</pre><pre>*Jun 9 21:14:22.519: RIP: build update entries - suppressing null update</pre>Remember that you should use Debug only for a short time to get a snippet of information, and then turn Debug off as it can be a serious performance hit on your router.<br />
There are several commands for turning off Debug. You could type <em>undebug all</em> or a precreated alias, <em>un all</em> (for more information on aliases, see my article “<a href="http://articles.techrepublic.com.com/5100-10878_11-5855141.html" target="_blank">Enter Commands More Efficiently with Cisco Command Aliases</a>“), but the <em>no debug</em> command works fine also.<br />
<pre>Router# no debug</pre>If you type <em>debug ?</em>, you will see that there are over 200+ Debug commands, and each of those has many options. Debugging RIP is just a very simple example.<br />
<h2>What are the three most common mistakes made when using Debug?</h2>Using Debug can be a risky proposition, and even experienced admins have made mistakes when using it.<br />
I’d say the number one common mistake is to forget that you have left Debug on in a production environment. Sometimes, we get so focused on resolving the issue that when we get it resolved, we are on to the next “opportunity” and forget to issue the <em>no debug</em> command to turn off debugging. I think that many a network admin can attest to horror stories of when they brought their router to its knees because they forgot this simple task of turning off Debug.<br />
The second common mistake would be not realizing the effect on your router of issuing a lot of Debug commands at the same time. Remember that the router’s job is to forward packets, not to monitor processes and generate Debug messages. For example, you are having a problem with the packets on your router, so you issue the Debug statement <em>debug ip packet</em>. Then you decide that you want to view the events on the RIP protocol. Now, you have two separate Debug statements that are being processed and sent to the console. Debug statements are processed at a higher priority than other network traffic, so, needless to say, these Debug statements can jeopardize your router’s performance.<br />
The third common mistake made with the Debug command is entering <em>debug all</em> or <em>debug ip packet detail</em> on a production router. Either one of these commands can crash a heavily loaded production router. Luckily, there is an “are you sure” prompt before these take effect; however, that hasn’t prevented every debug-related catastrophe. You should be as specific as possible when using Debug, and then turn it off as quickly as possible. Also, always test your Debug commands on a test router before using them in a production environment.<br />
<h2>What are some common scenarios when using Debug to troubleshoot?</h2>To learn about the top 10 most useful Cisco IOS Debug commands, please read my TechRepublic article “<a href="http://articles.techrepublic.com.com/5100-10878_11-1053788.html" target="_blank">Get IT Done: 10 Ways to Mitigate Problems Using Cisco IOS Debug</a>.”<br />
<strong>In conclusion</strong><br />
The Cisco IOS Debug commands are very powerful commands that every Cisco admin should know how to use properly. With Cisco IOS Debug commands, you can get down to the details of whatever protocol or feature you are troubleshooting in order to resolve your problem.<br />
For more information on Cisco IOS Debug commands, see the <a href="http://www.cisco.com/en/US/docs/ios/12_3/debug/command/reference/123debug.html" target="_blank">Cisco IOS Debug Command Reference</a>.Ngakakhttp://www.blogger.com/profile/08056581306532883030noreply@blogger.com0tag:blogger.com,1999:blog-2977364684436773224.post-56697978459153885362009-10-20T22:19:00.003-07:002009-10-20T22:19:19.116-07:00IPv6 di Router CiscoKemampuan Router Cisco untuk bisa mendukung operasional IPv6 salah satunya versi IOS yang lebih baru dan umumnya sudah stable pada versi IOS 12.2 keatas, serta module supervisor engine (SUP) untuk cisco 6500 & 7600 untuk support ipv6 (Thx to Fjr)<br />
<address>Referensi dari web www.cisco.com untuk IOS yang sudah support IPv6 adalah :</address><address>12.0S, 12.xT, 12.2S, 12.2 SB, 12.2SRA, 12.3, dan 12.4</address>Berikut list Seri Router yang sudah pernah dicoba IPv6 berikut IOS nya<br />
- Router Cisco 7200 (IOS 12.2 T & 12.3)<br />
- Router Cisco 3660 (IOS 12.2 T)<br />
- Router Cisco 3640 (IOS 12.2 T)<br />
Resources memory dan CPU juga perlu dipertimbangkan bila ingin mengembangkan dari Routing dasar ke Advance Routing (IGP & EGP).<br />
Konfigurasi dasar IPv6 di Router Cisco :<br />
1. Contoh Konfigurasi IPv6 Address di Interface Fisik & Sub Interface<br />
<a name='more'></a><br />
gw-ipv6#conf t<br />
gw-ipv6(config)# ipv6 unicast-routing<br />
! untuk mengaktifkan forwarding paket antar interface Router<br />
gw-ipv6(config)# ipv6 cef<br />
! untuk mengaktifkan fitur express forwarding paket IPv6<br />
gw-ipv6(config)#int ethernet 0<br />
gw-ipv6(config-if)#no shutdown<br />
gw-ipv6(config-if)#ipv6 enable<br />
! Untuk mengaktifkan IPv6 di interface<br />
gw-ipv6(config-if)#ipv6 address 2404:177:0253::1/123<br />
gw-ipv6(config-if)#^Z<br />
gw-ipv6#sh run int ethernet 0<br />
! untuk menampilkan konfigurasi khusus Ethernet 0 saja<br />
Building configuration…<br />
!<br />
Current configuration : 189 bytes<br />
!<br />
interface Ethernet3/0<br />
no ip address<br />
ipv6 enable<br />
ipv6 address 2404:177:253::1/123<br />
end<br />
gw-ipv6#wr<br />
! untuk menyimpan konfigurasi di NVRAM<br />
2. Contoh Konfigurasi IPv6 Address di Interface Virtual (Tunnel)<br />
gw-ipv6#conf t<br />
gw-ipv6(config)#int tunnel 100<br />
gw-ipv6(config-if)#ipv6 enable<br />
gw-ipv6(config-if)#ipv6 address 2404:177:A::1/126<br />
gw-ipv6(config-if)#tunnel source ipv4 address/nama interface<br />
! Tunnel Source merupakan ipv4 address disisi router ini / nama interfacenya<br />
gw-ipv6(config-if)#tunnel destin<br />
ation ipv4address<br />
! Tunnel Destination merupakan ipv4 address disisi router lawan yang akan kita bangun tunnel.<br />
! IPv4 tunnel source disisi pertama merupakan IPv4 tunnel destination di router kedua.<br />
! Demikian juga sebaliknya.<br />
gw-ipv6(config-if)#tunnel mode ipv6ip<br />
! ipv6ip merupakan mode tunnel IPv6 langsung (direct).<br />
3. Contoh Konfigurasi Routing Static IPv6<br />
gw-ipv6#conf t<br />
gw-ipv6(config)#ipv6 route 2404:175::/32 tunnel100<br />
! untuk me route paket ke prefix 2404:175::/32 lewat tunnel100<br />
! routing ke nama interface bisa diganti dengan ipv6 address tunnel di seberangNgakakhttp://www.blogger.com/profile/08056581306532883030noreply@blogger.com0tag:blogger.com,1999:blog-2977364684436773224.post-74352936446593255182009-10-20T22:14:00.000-07:002009-10-20T22:14:23.759-07:00Dedicated Servers and PeersIn some networks, a server computer is a server computer and nothing else.<br />
It’s dedicated to the sole task of providing shared resources, such as hard<br />
drives and printers, to be accessed by the network client computers. Such a<br />
server is referred to as a dedicated server because it can perform no other<br />
task besides network services.<br />
<br />
Other networks take an alternative approach, enabling any computer on the<br />
network to function as both a client and a server. Thus, any computer can<br />
share its printers and hard drives with other computers on the network. And<br />
while a computer is working as a server, you can still use that same computer<br />
for other functions such as word processing. This type of network is called<br />
a peer-to-peer network, because all the computers are thought of as peers,<br />
or equals.<br />
<br />
<a name='more'></a><br />
<br />
Here are some points to ponder concerning the difference between dedicated<br />
server networks and peer-to-peer networks while you’re walking the dog<br />
tomorrow morning:<br />
Peer-to-peer networking features are built into Windows. Thus, if your<br />
computer runs Windows, you don’t have to buy any additional software<br />
to turn your computer into a server. All you have to do is enable the<br />
Windows server features.<br />
The network server features that are built into desktop versions of<br />
Windows (such as Windows XP) aren’t very efficient because these versions<br />
of Windows were not designed primarily to be network servers. If<br />
you’re going to dedicate a computer to the task of being a full-time server,<br />
you should use a special network operating system instead of the standard<br />
Windows operating system. A network operating system, also known<br />
as a NOS, is specially designed to handle networking functions efficiently.<br />
The two most commonly used network operating systems are the server<br />
version of Windows — which, depending on the version you use, is known<br />
as Windows Server 2003, Windows 2000 Server, or Windows NT Server —<br />
and Novell NetWare. I describe these alternatives briefly in the next section,<br />
“The NOS Choice.”<br />
Many networks are both peer-to-peer and dedicated-server networks at<br />
the same time. These networks have one or more server computers that<br />
run a NOS such as Windows Server 2003, as well as client computers<br />
that use the server features of Windows to share their resources with<br />
the network.<br />
Besides being dedicated, it’s helpful if your servers are also sincere.Ngakakhttp://www.blogger.com/profile/08056581306532883030noreply@blogger.com0tag:blogger.com,1999:blog-2977364684436773224.post-2176299957324742362009-10-20T22:10:00.000-07:002009-10-20T22:10:23.052-07:00Servers and ClientsThe <b>network computer</b> that contains the hard drives, printers, and other<br />
resources that are shared with other network computers is called a server.<br />
This term comes up repeatedly, so you have to remember it. Write it on the<br />
back of your left hand.<br />
<br />
Any computer that’s not a server is called a client. You have to remember this<br />
term, too. Write it on the back of your right hand.<br />
Only two kinds of computers are on a network: servers and clients. Look at<br />
your left hand and then look at your right hand. Don’t wash your hands until<br />
you have these terms memorized.<br />
The distinction between servers and clients in a network has parallels in<br />
sociology — in effect, a sort of class distinction between the “haves” and<br />
“have-nots” of computer resources:<br />
Usually, the most powerful and expensive computers in a network are<br />
the servers. There’s a good technical reason: Every user on the network<br />
shares the server’s resources.<br />
The cheaper and less powerful computers in a network are the clients.<br />
Clients are the computers used by individual users for everyday work.<br />
Because clients’ resources don’t have to be shared, they don’t have to<br />
be as fancy.<br />
Most networks have more clients than servers. For example, a network<br />
with ten clients can probably get by with one server.<br />
In many networks, a clean line of demarcation exists between servers<br />
and clients. In other words, a computer functions as either a server or a<br />
client, and not both. For the sake of an efficient network, a server can’t<br />
become a client, nor can a client become a server.<br />
Other (usually smaller) networks can be more even-handed, allowing<br />
any computer in the network to be a server and client at the same time.Ngakakhttp://www.blogger.com/profile/08056581306532883030noreply@blogger.com0tag:blogger.com,1999:blog-2977364684436773224.post-14957581723663697882009-10-20T22:00:00.000-07:002009-10-20T22:03:56.294-07:00What Is a Network?A network is nothing more than two or more computers connected by a<br />
cable (or in some cases, by a wireless connection) so that they can exchange<br />
information.<br />
Of course, computers can exchange information in other ways besides networks.<br />
Most of us have used what computer nerds call the sneakernet. That’s<br />
where you copy a file to a diskette and then walk the disk over to someone<br />
else’s computer. (The term sneakernet is typical of computer nerds’ feeble<br />
attempts at humor, and why not? As a way to transfer information, sneakernet<br />
was pretty feeble.)<br />
<a name='more'></a><br />
The whole problem with the sneakernet is that it’s slow — plus, it wears a<br />
trail in your carpet. One day, some penny-pinching computer geeks discovered<br />
that connecting computers together with cables was actually cheaper than<br />
replacing the carpet every six months. Thus the modern computer network<br />
was born.<br />
You can create a computer network by hooking all the computers in your office<br />
together with cables and installing a special network interface card (an electronic<br />
circuit card that goes inside your computer — ouch!) in each computer<br />
so you have a place to plug in the cable. Then you set up your computer’s<br />
operating-system software to make the network work, and — voilà — you have<br />
a working network. That’s all there is to it.<br />
If you don’t want to mess with cables, you can create a wireless network<br />
instead. In a wireless network, each computer is equipped with a special wireless<br />
network adapter that has little rabbit-ear antennas. Thus, the computers<br />
can communicate with each other without the need for cables.Ngakakhttp://www.blogger.com/profile/08056581306532883030noreply@blogger.com0tag:blogger.com,1999:blog-2977364684436773224.post-4344014237589303542009-09-07T03:21:00.000-07:002009-10-20T22:04:18.526-07:00Pengenalan cisco<b>Pendahuluan </b><br />
<br />
Anda dapat memikirkan suatu <b>router Cisco</b> sebagai tujuan khusus komputer. Ia memiliki sistem operasi sendiri, yang disebut <b>Internetwork Operating System (IOS),</b> serta file dan filesystem. Jadi kita akan mulai dengan pembahasan tentang fungsi-fungsi administrasi sistem dasar bahwa sebuah router insinyur harus tampil. Ini mencakup pengelolaan router Anda filesystem, upgrade sistem operasi, melakukan backup, dan memulihkan konfigurasi sistem.<br />
<br />
Cisco router menggunakan flash memory, bukan disk, untuk menyimpan informasi. Media penyimpanan flash secara signifikan lebih mahal dan lebih lambat dari disk penyimpanan, tetapi jumlah penyimpanan yang diperlukan untuk menjalankan sebuah router yang relatif kecil dibandingkan dengan jumlah yang dibutuhkan untuk menjalankan sebuah komputer untuk keperluan umum. Flash juga memiliki manfaat penting bahwa ia cenderung lebih bisa diandalkan daripada penyimpanan disk.<br />
<a name='more'></a><br />
<br />
Flash storage mirip dengan Random Access Memory (RAM), tetapi tidak perlu kekuasaan untuk menyimpan informasi, sehingga hal itu disebut non-volatile. Dan, tidak seperti Read Only Memory (ROM), Anda dapat menghapus dan menulis ulang flash dengan mudah. Ada jenis lain non-volatile solid state penyimpanan, seperti bisa dihapus Programmable Read Only Memory (EPROM) dan elektronik bisa dihapus Programmable Read Only Memory (EEPROM). EPROM tidak sesuai untuk router karena biasanya membutuhkan perangkat eksternal seperti sinar ultraviolet bersinar melalui jendela pada chip untuk menghapusnya. EEPROM, di sisi lain, dapat dihapus dengan menghapus hanya mengirimkan sinyal ke chip. Tetapi ada perbedaan penting antara EEPROM dan flash memory: ketika Anda menghapus sesuatu dari perangkat EEPROM, Anda harus menghapus seluruh perangkat, sementara perangkat flash penghapusan selektif memungkinkan bagian-bagian dari media.<br />
<br />
Ini merupakan fitur penting untuk router, karena Anda tidak selalu ingin menghapus seluruh media penyimpanan untuk menghapus satu file. Dalam 1.11 dan Resep Resep 1,12, kita membahas cara-cara untuk menghapus file tunggal pada beberapa jenis router, tergantung pada jenis filesystem yang digunakan.<br />
<br />
Setidaknya ada dua lembar penyimpanan non-volatile dalam router Cisco. Konfigurasi router informasi yang disimpan dalam perangkat yang disebut Non-Volatile RAM (NVRAM), dan gambar IOS disimpan dalam alat yang disebut lampu kilat (huruf kecil). Penting untuk tetap lurus karena nama-nama ini, tentu saja, semua memori Flash adalah non-volatile RAM. Dan, pada kenyataannya, kebanyakan router menggunakan teknologi Flash untuk NVRAM mereka. Jadi mudah untuk mendapatkan bingung dengan istilah-istilah.<br />
<br />
Pada kebanyakan router Cisco, di daerah NVRAM di suatu tempat antara 16 dan 256KB, tergantung pada ukuran dan fungsi dari router. Router yang lebih besar diharapkan memiliki file-file konfigurasi yang lebih besar, sehingga mereka membutuhkan lebih banyak NVRAM. Perangkat lampu kilat, di sisi lain, biasanya upgradeable, dan dapat di mana saja dari beberapa megabyte untuk ratusan megabyte.<br />
<br />
Kita sering berbicara tentang file konfigurasi router, tetapi sebenarnya ada dua file konfigurasi penting pada setiap router. Ada file konfigurasi yang menggambarkan keadaan saat ini menjalankan router, yang disebut berjalan-config. Kemudian, ada file konfigurasi yang menggunakan router untuk boot, yang disebut startup-config. Hanya startup-config disimpan dalam NVRAM, sehingga sangat penting untuk secara berkala memeriksa versi konfigurasi dalam NVRAM disinkronisasikan dengan versi yang router saat ini berjalan. Jika tidak, anda bisa mendapatkan kejutan dari sejarah kuno waktu berikutnya router reboot. Anda dapat menyinkronkan dua file konfigurasi dengan hanya menyalin berlari-config ke startup-config file:<br />
<br />
Menjalankan <b>Router1 # copy startup-config-config</b><br />
Banyak Engineer Cisco , termasuk penulis, masih menggunakan versi kuno dari perintah ini dari kekuatan kebiasaan:<br />
<br />
<b>Router1 # write memory</b><br />
Namun, perintah ini tidak hanya usang, itu juga kurang deskriptif mengenai apa yang router lakukan.<br />
<br />
Router menggunakan perangkat penyimpanan flash yang lebih besar untuk menyimpan sistem operasi, atau IOS. Tidak seperti sistem operasi pada kebanyakan komputer, IOS adalah sebuah file yang berisi semua fitur dan fungsi yang tersedia pada router. Anda dapat memperoleh file gambar IOS dari Cisco pada CD atau, jika Anda memiliki account pada sistem mereka, Anda dapat men-download file IOS dari Cisco situs web menggunakan FTP.<br />
<br />
Sebagian besar contoh di seluruh buku ini mengasumsikan bahwa Anda telah IOS Version 12. Namun, banyak dari fitur kita bahas juga tersedia dalam versi sebelumnya. Walaupun mungkin ada sedikit perubahan sintaks, kita berharap bahwa Cisco akan terus mendukung semua fitur kita menggambarkan dengan baik ke masa depan. Penting untuk menjadi fleksibel karena jika Anda bekerja dengan router Cisco banyak, Anda akan menemukan berbagai besar versi IOS yang berbeda, dengan berbagai perbedaan halus. Sayangnya, beberapa perbedaan yang halus ini benar-benar bug. Cisco menawarkan sistem pelacakan bug rinci pada situs web mereka untuk pengguna terdaftar.<br />
<br />
Ada beberapa hal penting yang perlu dipertimbangkan ketika Anda pergi untuk mengubah versi IOS pada router. Pertama adalah set fitur. Untuk setiap rilis IOS, Cisco menghasilkan beberapa versi yang berbeda. Mereka biasanya menawarkan Fitur Enterprise Set, yang mencakup semua fitur berbagai pilihan yang tersedia pada waktu tertentu. Karena IOS monolitik adalah file yang berisi semua fitur dan semua perintah, Enterprise IOS file tersebut biasanya cukup besar. Versi Enterprise umumnya jauh lebih mahal daripada dilucuti-down berbagai versi.<br />
<br />
Versi IOS yang paling sederhana biasanya adalah IP Hanya Feature Set. Seperti namanya, ini hanya mencakup TCP / IP berdasarkan fungsionalitas. Di sebagian besar jaringan, Anda akan menemukan bahwa IP Saja Fitur Set lebih dari cukup. Pada kenyataannya, hampir semua resep dalam buku ini akan bekerja dengan IP Hanya versi IOS.<br />
<br />
Jika Anda memerlukan protokol lain seperti IPX atau AppleTalk, Cisco IOS Fitur menghasilkan Set disebut Desktop yang berisi protokol-protokol ini. Mereka juga menawarkan beberapa variasi penting lainnya seperti IP Plus, IP Plus IPSec 56, IP Plus IPSec 3DES, dan sebagainya. Isi versi yang berbeda ini (dan bahkan nama-nama mereka sampai batas tertentu) berbeda dari rilis ke rilis. Kami mendorong Anda untuk berkonsultasi dengan fitur Cisco matrixes untuk memastikan bahwa fitur yang Anda perlukan dalam versi IOS yang Anda miliki.<br />
<br />
Salah satu pertimbangan yang paling penting dengan rilis IOS adalah apakah Anda punya cukup RAM dan Flash memory untuk mendukung versi baru. Anda dapat melihat berapa banyak penyimpanan router Anda dengan melihat output dari perintah show version.<br />
<br />
Penting lainnya yang harus diingat tentang gambar pada Cisco IOS router adalah bahwa setiap router memiliki gambar fallback terletak di router ROM. IOS ini gambar tersebut tidak dapat diubah atau ditingkatkan tanpa mengganti secara fisik chip ROM di router.<br />
<br />
<b>Router ROM berisi tiga item:</b> <b>daya self test (POST), program bootstrap, dan versi terbatas dari sistem operasi router</b>. Router menggunakan program bootstrap saat boot. IOS image dalam ROM biasanya yang sangat dilucuti-down versi yang tidak mendukung banyak fitur-fitur umum (routing protokol, misalnya). Dalam siklus boot normal, router akan memuat pertama POST, maka program bootstrap diikuti oleh IOS image yang sesuai.Ngakakhttp://www.blogger.com/profile/08056581306532883030noreply@blogger.com0