cisco router 3700series

With on-board LAN/WAN connectivity, new high-density service modules, and support for multiple advanced integration modules, the Cisco 3700 Series Multiservice Access Router delivers new levels of service density for branch offices in a compact form factor.

When configured with the 16- or 36-port EtherSwitch network module, the Cisco 3700 Series offers a single, integrated platform that combines flexible routing and low-density switching. In addition, it can support internal inline power for the EtherSwitch ports, delivering a single-platform IP telephony and voice gateway solution that facilitates flexible, incremental, and scalable migration to a converged network. These single-platform solutions help lower total cost of ownership by simplifying training, deployment, and management, and modular expansion options help protect current network investment.

As a cornerstone of Cisco AVVID (Architecture for Voice, Video and Integrated Data), the Cisco 3700 Series supports rich Cisco IOS Software features such as availability, quality of service, and security to address the resiliency needs of the branch office. The Cisco 3700 Series combines these features with flexible application and services consolidation to offer branch offices a platform optimized for integrating future services.

Key features for the Cisco 3725 and 3745:

Two Integrated 10/100 LAN ports

Two Integrated Advanced Integration Modules (AIM) slots

Three Integrated WAN Interface Card (WIC) slots

Two (Cisco 3725) or four (Cisco 3745) Network Module (NM) slots

One (Cisco 3725) or two (Cisco 3745) High Density Service Module (HDSM)-capable slots

32MB Compact Flash (default); 128MB maximum

128MB DRAM (default, single 128MB DIMM); 256MB DRAM maximum

Optional In-Line Power for 16-port EtherSwitch NM and 36-port EtherSwitch HDSM

Support for all major WAN protocols and media: LL, FR, ISDN, X.25, ATM, fractional T1/E1, T1/E1, xDSL, T3/E3, HSSI

Support for selected NMs, WICs and AIMs from the Cisco 1700, 2600 and 3600 Series 2 RU (Cisco 3725) or 3 RU (Cisco 3745) Rack-mountable chassis

Key features for the Cisco 3725 and 3745:

Two Integrated 10/100 LAN ports

Two Integrated Advanced Integration Modules (AIM) slots

Three Integrated WAN Interface Card (WIC) slots

Two (Cisco 3725) or four (Cisco 3745) Network Module (NM) slots

One (Cisco 3725) or two (Cisco 3745) High Density Service Module (HDSM)-capable slots

32MB Compact Flash (default); 128MB maximum

128MB DRAM (default, single 128MB DIMM); 256MB DRAM maximum

Optional In-Line Power for 16-port EtherSwitch NM and 36-port EtherSwitch HDSM

Support for all major WAN protocols and media: LL, FR, ISDN, X.25, ATM, fractional T1/E1, T1/E1, xDSL, T3/E3, HSSI

Support for selected NMs, WICs and AIMs from the Cisco 1700, 2600 and 3600 Series 2 RU (Cisco 3725) or 3 RU (Cisco 3745) Rack-mountable chassis

Cisco Router Configuration Tutorial

Josh Gentry, [email protected], 6 September, 1999

This document covers basic Cisco router IP configuration using the command-line interface

AcknowledgmentsThe following sources where extremely useful:

Leinwand, Pinsky, and Culpepper. Cisco Router Configuration. Indianapolis, Indiana: Cisco Press, 1998.

Cisco Systems, Inc., http://www.cisco.com

Thank you to Martin Newman for giving me my first lesson in configuring Cisco routers.

The information for this document was originally gathered for, or derived from, completing a project for Mr. James Hart, instructor at the Technical/Vocational Institute in Albuquerque, NM. A big thank you to him for allowing me to work on that project.

DisclaimerThis document carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this document is accurate. It is offered in the hopes of helping others, but you use it at your own risk. Neither the author nor TVI will be liable for any damages that occur as a result of using this document.

ConventionsImportant terms and concepts, when they are introduced, may be displayed in bold. Commands included in the body of the text will be displayed in this font. All names and addresses used in examples are just that, examples, and should not be used on your network. Do not type them in verbatim when configuring your system. Finally, in some examples where the command rquires an IP address as an argument, the IP address may be represented in this way, xx.xx.xx.xx, or aa.bb.cc.dd. You will never actually use these strings when configuring your system. They are mearly a convention of this document to specify that you should substitute the appropriate IP address at that point.

1. What this document covers

There are several methods available for configuring Cisco routers. It can be done over the network from a TFTP server. It can be done through the menu interface provided at bootup, and it can be done from the menu interface provided by using the command setup. It can also be done from a configuration saved to memory. This tutorial does not cover these methods. It covers configuration from the IOS command-line interface only.

Note that this tutorial does not cover physically connecting the router to the networks it will be routing for. It covers operating system configuration only.

1.1 Reasons for using the command-line

There are two main reasons for using the command-line interface instead of a menu driven interface. One is speed. Once you have invested the time to learn the command-line commands, you can perform many operations much more quickly than by using a menu. This is basically true of all command-line vs. menu interfaces. What makes it especially efficient to learn the command-line interface of the Cisco IOS is that it is standard across all Cisco routers.

Secondly, there is the ability to configure individual interfaces without interrupting service on other interfaces. By definition, routers have multiple interfaces. Routers such as those in the Cisco 7200 series have several hot-swapable modules of multiple ports each. It is a valuable skill to be able to configure these individually from the command-line.

1.2 Document structure

The first part of this document will introduce the command modes of the IOS, and the commands necessary to do a basic configuration of a Cisco router. The second part of the document will demonstrate the use of these commands in a case study. The case study is an actual configuration completed by the author of this document.

2. Getting started

Initially you will probably configure your router from a terminal. If the router is already configured and at least one port is configured with an IP address, and it has a physical connection to the network, you might be able to telnet to the router and configure it across the network. If it is not already configured, then you will have to directly connect to it with a terminal and a serial cable. With any Windows box you can use Hyperterminal to easily connect to the router. Plug a serial cable into a serial (COM) port on the PC and the other end into the console port on the Cisco router. Start Hyperterminal, tell it which COM port to use and click OK. Set the speed of the connection to 9600 baud and click OK. If the router is not on, turn it on.

If you wish to configure the router from a Linux box, either Seyon or Minicom should work. At least one of them, and maybe both, will come with your Linux distribution.

Often you will need to hit the Enter key to see the prompt from the router. If it is unconfigured it will look like this:

Router> If it has been previously configured with a hostname, it will look like this:

hostname of router> If you have just turned on the router, after it boots it will ask you if you wish to begin initial configuration. Say no. If you say yes, it will put you in the menu interface. Say no.

2.1 Modes

The Cisco IOS command-line interface is organized around the idea of modes. You move in and out of several different modes while configuring a router, and which mode you are in determines what commands you can use. Each mode has a set of commands available in that mode, and some of these commands are only available in that mode. In any mode, typing a question mark will display a list of the commands available in that mode.

Router>? 2.2 Unprivileged and privileged modes

When you first connect to the router and provide the password (if necessary), you enter EXEC mode, the first mode in which you can issue commands from the command-line. From here you can use such unprivileged commands as ping, telnet, and rlogin. You can also use some of the show commands to obtain information about the system. In unprivileged mode you use commands like, show version to display the version of the IOS the router is running. Typing show ? will diplay all the show commands available in the mode you are presently in.

Router>show ? You must enter privileged mode to configure the router. You do this by using the command enable. Privileged mode will usually be password protected unless the router is unconfigured. You have the option of not password protecting privileged mode, but it is HIGHLY recommended that you do. When you issue the command enable and provide the password, you will enter privileged mode.

To help the user keep track of what mode they are in, the command-line prompt changes each time you enter a different mode. When you switch from unprivileged mode to privileged mode, the prompt changes from:

Router> to

Router# This would probably not be a big deal if there were just two modes. There are, in fact, numerous modes, and this feature is probably indispensable. Pay close attention to the prompt at all times.

Within privileged mode there are many sub-modes. In this document I do not closely follow Cisco terminology for this hierarchy of modes. I think that my explanation is clearer, frankly. Cisco describes two modes, unprivileged and privileged, and then a hierarchy of commands used in privileged mode. I reason that it is much clearer to understand if you just consider there to be many sub-modes of privileged mode, which I will also call parent mode. Once you enter privileged mode (parent mode) the prompt ends with a pound sign (#). There are numerous modes you can enter only after entering privileged mode. Each of these modes has a prompt of the form:

Router(arguments)#

They still all end with the pound sign. They are subsumed within privileged mode. Many of these modes have sub-modes of their own. Once you enter priliged mode, you have access to all the configuration information and options the IOS provides, either directly from the parent mode, or from one of its submodes.

3. Configuring

If you have just turned on the router, it will be completely unconfigured. If it is already configured, you may want to view its current configuration. Even if it has not been previously configured, you should familiarize yourself with the show commands before beginning to configure the router. Enter privileged mode by issuing the command enable, then issue several show commands to see what they display. Remember, the command show ? will display all the showcommands aavailable in the current mode. Definately try out the following commands:

Router#show interfacesRouter#show ip protocolsRouter#show ip routeRouter#show ip arp When you enter privileged mode by using the command enable, you are in the top-level mode of privileged mode, also known in this document as "parent mode." It is in this top-level or parent mode that you can display most of the information about the router. As you now know, you do this with the show commands. Here you can learn the configuration of interfaces and whether they are up or down. You can display what IP protocols are in use, such as dynamic routing protocols. You can view the route and ARP tables, and these are just a few of the more important options.

As you configure the router, you will enter various sub-modes to set options, then return to the parent mode to display the results of your commands. You also return to the parent mode to enter other sub-modes. To return to the parent mode, you hit ctrl-z. This puts any commands you have just issued into affect, and returns you to parent mode.

3.1 Global configuration (config)

To configure any feature of the router, you must enter configuration mode. This is the first sub-mode of the parent mode. In the parent mode, you issue the command config.

Router#configRouter(config)# As demonstrated above, the prompt changes to indicate the mode that you are now in.

In connfiguration mode you can set options that apply system-wide, also refered to as "global configurations." For instance, it is a good idea to name your router so that you can easily identify it. You do this in configuration mode with the hostname command.

Router(config)#hostname ExampleNameExampleName(config)# As demonstrated above, when you set the name of the host with the hostname command, the prompt immediately changes by replacing Router with ExampleName. (Note: It is a good idea to name your routers with an organized naming scheme.)

Another useful command issued from config mode is the command to designate the DNS server to be used by the router:

ExampleName(config)#ip name-server aa.bb.cc.ddExampleName(config)#ctrl-ZExampleName# This is also where you set the password for privileged mode.

ExampleName(config)#enable secret examplepasswordExampleName(config)#ctrl-ZExampleName# Until you hit ctrl-Z (or type exit until you reach parent mode) your command has not been put into affect. You can enter config mode, issue several different commands, then hit ctrl-Z to activate them all. Each time you hit ctrl-Z you return to parent mode and the prompt:

ExampleName# Here you use show commands to verify the results of the commands you issued in config mode. To verify the results of the ip name-server command, issue the command show host.

3.2 Configuring interfaces

Cisco interface naming is straightforward. Individual interfaces are referred to by this convention:

media type slot#/port# "Media type" refers to the type of media that the port is an interface for, such as Ethernet, Token Ring, FDDI, serial, etc. Slot numbers are only applicable for routers that provide slots into which you can install modules. These modules contain several ports for a given media. The 7200 series is an example These modules are even hot-swapable. You can remove a module from a slot and replace it with a different module, without interrupting service provided by the other modules installed in the router. These slots are numbered on the router.

Port number refers to the port in reference to the other ports in that module. Numbering is left-to-right, and all numbering starts at 0, not at one.

For example, a Cisco 7206 is a 7200 series router with six slots. To refer to an interface that is the third port of an Ethernet module installed in the sixth slot, it would be interface ethernet 6/2. Therefor, to display the configuration of that interface you use the command:

ExampleName#show interface ethernet 6/2 If your router does not have slots, like a 1600, then the interface name consists only of:

media type port# For example:

ExampleName#show interface serial 0 Here is an example of configuring a serial port with an IP address:

ExampleName#configExampleName(config)#interface serial 1/1ExampleName(config-if)#ip address 192.168.155.2 255.255.255.0ExampleName(config-if)#no shutdownExampleName(config-if)#ctrl-ZExampleName# Then to verify configuration:

ExampleName#show interface serial 1/1 Note the no shutdown command. An interface may be correctly configured and physically connected, yet be "administratively down." In this state it will not function. The command for causing an interface to be administratively down is shutdown.

ExampleName(config)#interface serial 1/1ExampleName(config-if)#shutdownExampleName(config-if)#ctrl-ZExampleName#show interface serial 1/1 In the Cisco IOS, the way to reverse or delete the results of any command is to simply put no infront of it. For instance, if we wanted to unassign the IP address we had assigned to interface serial 1/1:

ExampleName(config)#interface serail 1/1ExampleName(config-if)#no ip address 192.168.155.2 255.255.255.0ExampleName(config-if)ctrl-ZExampleName#show interface serial 1/1 Configuring most interfaces for LAN connections might consist only of assigning a network layer address and making sure the interface is not administratively shutdown. It is usually not necessary to stipulate data-link layer encapsulation. Note that it is often necessary to stipulate the appropriate data-link layer encapsulation for WAN connections, such as frame-relay and ATM. Serial interfaces default to using HDLC. A discussion of data-link protocols is outside the scope of this document. You will need to look up the IOS command encapsulation for more details.

3.3 Routing

IP routing is automatically enabled on Cisco routers. If it has been previously disabled on your router, you turn it back on in config mode with the command ip routing.ExampleName(config)#ip routingExampleName(config)#ctrl-Z There are two main ways a router knows where to send packets. The administrator can assign static routes, or the router can learn routes by employing a dynamic routing protocol.These days static routes are generally used in very simple networks or in particular cases that necessitate their use. To create a static route, the administrator tells the router operating system that any network traffic destined for a specified network layer address should be forwarded to a similiarly specified network layer address. In the Cisco IOS this is done with the ip route command.

ExampleName#configExampleName(config)#ip route 172.16.0.0 255.255.255.0 192.168.150.1ExampleName(config)#ctrl-ZExampleName#show ip route Two things to be said about this example. First, the packet destination address must include the subnet mask for that destination network. Second, the address it is to be forwarded to is the specified addres of the next router along the path to the destination. This is the most common way of setting up a static route, and the only one this document covers. Be aware, however, that there are other methods.

Dynamic routing protocols, running on connected routers, enable those routers to share routing information. This enables routers to learn the routes available to them. The advantage of this method is that routers are able to adjust to changes in network topologies. If a route is physically removed, or a neighbor router goes down, the routing protocol searches for a new route. Routing protocols can even dynamically choose between possible routes based on variables such as network congestion or network reliability.

There are many different routing protocols, and they all use different variables, known as "metrics," to decide upon appropriate routes. Unfortunately, a router needs to be running the same routing protocols as its neighbors. Many routers can, however, run mutliple protocols. Also, many protocols are designed to be able to pass routing information to other routing protocols. This is called "redistribution." The author has no experience with trying to make redistribution work. There is an IOS redistribute command you can research if you think this is something you need. This document's compagnion case study describes an alternative method to deal with different routing protocols in some circumstances.

Routing protocols are a complex topic and this document contains only this superficial description of them. There is much to learn about them, and there are many sources of information about them available. An excelent source of information on this topic is Cisco's website, http://www.cisco.com.

This document describes how to configure the Routing Information Protocol (RIP) on Cisco routers. From the command-line, we must explicitly tell the router which protocol to use, and what networks the protocol will route for.

ExampleName#configExampleName(config)#router ripExampleName(config-router)#network aa.bb.cc.ddExampleName(config-router)#network ee.ff.gg.hhExampleName(config-router)#ctrl-ZExampleName#show ip protocols Now when you issue the show ip protocols command, you should see an entry describing RIP configuration.

3.4 Saving your configuration

Once you have configured routing on the router, and you have configured individual interfaces, your router should be capable of routing traffic. Give it a few moments to talk to its neighbors, then issue the commands show ip route and show ip arp. There should now be entries in these tables learned from the routing protocol.

If you turned the router off right now, and turned it on again, you would have to start configuration over again. Your running configuration is not saved to any permanent storage media. You can see this configuration with the command show running-config.

ExampleName#show running-config You do want to save your successful running configuration. Issue the command copy running-config startup-config.

ExampleName#copy running-config startup-config Your configuration is now saved to non-volatile RAM (NVRAM). Issue the command show startup-config.

ExampleName#show startup-config Now any time you need to return your router to that configuration, issue the command copy startup-config running-config.

ExampleName#copy startup-config running-config 3.5 Example configuration

1. Router>enable

2. Router#config

3. Router(config)#hostname N115-7206

4. N115-7206(config)#interface serial 1/1

5. N115-7206(config-if)ip address 192.168.155.2 255.255.255.0

6. N115-7206(config-if)no shutdown

7. N115-7206(config-if)ctrl-z

8. N115-7206#show interface serial 1/1

9. N115-7206#config

10. N115-7206(config)#interface ethernet 2/3

11. N115-7206(config-if)#ip address 192.168.150.90 255.255.255.0

12. N115-7206(config-if)#no shutdown

13. N115-7206(config-if)#ctrl-z

14. N115-7206#show interface ethernet 2/3

15. N115-7206#config

16. N115-7206(config)#router rip

17. N115-7206(config-router)#network 192.168.155.0

18. N115-7206(config-router)#network 192.168.150.0

19. N115-7206(config-router)#ctrl-z

20. N115-7206#show ip protocols

21. N115-7206#ping 192.168.150.1

22. N115-7206#config

23. N115-7206(config)#ip name-server 172.16.0.10

24. N115-7206(config)#ctrl-z

25. N115-7206#ping archie.au

26. N115-7206#config

27. N115-7206(config)#enable secret password

28. N115-7206(config)#ctrl-z

29. N115-7206#copy running-config startup-config

30. N115-7206#exit

4. Troubleshooting

Inevitably, there will be problems. Usually, it will come in the form of a user notifying you that they can not reach a certain destination, or any destinattion at all. You will need to be able to check how the router is attempting to route traffic, and you must be able to track down the point of failure.

You are already familiar with the show commands, both specific commands and how to learn what other show commands are available. Some of the most basic, most useful commands you will use for troubleshooting are:

ExampleName#show interfacesExampleName#show ip protocolsExampleName#show ip routeExampleName#show ip arp 4.1 Testing connectivity

It is very possible that the point of failure is not in your router configuration, or at your router at all. If you examine your router's configuration and operation and everything looks good, the problem might be be farther up the line. In fact, it may be the line itself, or it could be another router, which may or may not be under your administration.

One extremely useful and simple diagnostic tool is the ping command. Ping is an implementation of the IP Message Control Protocol (ICMP). Ping sends an ICMP echo request to a destination IP address. If the destination machine receives the request, it responds with an ICMP echo response. This is a very simple exchange that consists of:

Hello, are you alive?Yes, I am.ExampleName#ping xx.xx.xx.xx If the ping test is successful, you know that the destination you are having difficulty reaching is alive and physically reachable.

If there are routers between your router and the destination you are having difficulty reaching, the problem might be at one of the other routers. Even if you ping a router and it responds, it might have other interfaces that are down, its routing table may be corrupted, or any number of other problems may exist.

To see where packets that leave your router for a particular destination go, and how far, use the trace command.

ExampleName#trace xx.xx.xx.xx It may take a few minutes for this utility to finish, so give it some time. It will display a list of all the hops it makes on the way to the destination.

4.2 debug commands

There are several debug commands provided by the IOS. These commands are not covered here. Refer to the Cisco website for more information.

4.3 Hardware and physical connections

Do not overlook the possibility that the point of failure is a hardware or physical connection failure. Any number of things can go wrong, from board failures to cut cables to power failures. This document will not describew troubleshooting these problems, except for these simple things.

Check to see that the router is turned on. Also make sure that no cables are loose or damaged. Finally, make sure cables are plugged into the correct ports. Beyond this simple advice you will need to check other sources.

4.4 Out of your control

If the point of failure is farther up the line, the prolem might lie with equipment not under your administration. Your only option might be to contact the equipment's administrator, notify them of your problem, and ask them for help. It is in your interest to be courtious and respectful. The other administrator has their own problems, their own workload and their own priorities. Their agenda might even directly conflict with yours, such as their intention to change dynamic routing protocols, etc. You must work with them, even if the situation is frustrating. Alienating someone with the power to block important routes to your network is not a good idea.

5. Case study (Under Construction)

6. References

Leinwand, Pinsky and Culpepper Cisco Router Configuration. Indianapolis, Indiana: Cisco Press, 1998.

Cisco Systems, Inc., http://www.cisco.com

7. More documentation

For more information on Cisco products, and many documents on networking in general: http://www.cisco.comFor more documentation by the author of this document: http://www.swcp.com/~jgentry

Authored by Josh Gentry

Top

IP Subnet Calculations

1. IP Addressing

At this point you should know that IP, the Internet Protocol, is a network layer (OSI layer 3) protocol, used to route packets between hosts on different networks. To suit this purpose, IP must define an addressing scheme, so that a packet's intended destination can be indicated.

An IP address is composed of 32 bits. These 32 bits are divided into 4 octets of 8 bits each. You may have seen an IP address represented like this: 172.68.15.24. We must remember, however, that the computer understands this number only in binary, so we must often deal with them in binary. Many people are intimidated by this initially, but soon find that it is not difficult. If you do not allow yourself to be flustered, you can master this topic.

IP addresses are assigned to orginazations in blocks. Each block belongs to one of three classes: class A, class B, or class C. You can tell what class an IP address is by the value in its first octet.

Class A1-126

Class B128-191

Class C192 -->

An IP address consists of two fields. The first field identifies the network, and the second field identifies the node on the network. Which bits of the address are in the network field and which bits are in the host field is determined by the subnet mask.

When a class A IP license is granted, you are assigned something like this: 99.0.0.0. Only the value of the bits in the first octet are assigned. This means you are free to assign any values you wish in the second, third and fourth octets.

The defualt subnet mask for a class A network is 255.0.0.0. High bits, ones, indicate the bits that are part of the network field of the IP address. The default subnet mask does not create subnets. Therefor, a class A network with the default subnet mask is one network. The three octets that are unassigned and unmasked are part of the host field of the address. There is a total of 24 bits in those three octets. Each bit can be in one of two states. Therefor, 2^24 is the number of host addresses that can be assigned on that network, almost. Two addresses are reserved on every network, x.x.x.0 and x.x.x.255. So the total number of hosts possible on this network is 2^24. 2^24-2=16,777,214 hosts for a class A IP network.

When a class B license is granted, the first two octets are assigned. For example, 172.198.x.x. The default subnet mask for a class B is 255.255.0.0. One network, two octets free, 16 bits for the host address field. 2^16-2=65,534 possible host addresses on a class B IP network.

When a class C license is granted, the first three octets are assigned, for example: 193.52.16.0. The default subnet mask for a class C is 255.255.255.0. Once octet makes up the host address field. 2^8-2=254 host addresses possible on a class C network.

2. Reason for Subnetting

We said that the default subnet mask for a class A IP network is 255.0.0.0. Once octet only of a class A network address identifies the network, with this subnet mask. This leaves three octets of 8 bits each, or 24 bits, to identify the host on that one network. 2^24=16,777,216 addresses. Two addresses are reserved, x.x.x.0 and x.x.x.255. 16,777,214 nodes can be assigned an IP address on this network.

It is highly unlikely that any organization would want one network of 16,777,214 nodes. They might want that many devices connected in a wide area network (WAN), thus capablee of communicating when neccessary, but they will want to subdivide this huge network into mostly self-contained subnetworks of nodes that communicate with each other often. This is called subnetting.

To understand why, consider what would happen in either a broadcast or a token passing network that consisted of over 16,000,000 nodes. Nothing would happen. It simply would not work. Though the problem is not as drastic, class B and class C IP networks are often subnetted, also.

The subnet mask is used to subdivide an IP network into subnets. This is a division that takes place in OSI layer 3, so it is a logical division that is created by the addressing scheme. This logical division is usually combined with a physical division. Many subnets are physically isolated from the rest of the network by a device such as a router or a switch. This aspect of subnetting is discussed in Unit 3--Data Link Layer.

3. How Subnetting Works

The bits of an address that are masked by the subnet mask are the bits that make up the network field of the address. To subnet, the default subnet mask for a network is extended to cover bits of the address that would otherwise be part of the host field. Once these bits are masked, they become part of the network field, and are used to identify subnets of the larger network.

Here is where we begin dealing with both addresses and subnetmasks in binary. Get yourself a cold beverage, stretch, take a deep breath and don't worry. Once you get your brain around the concepts, it is not difficult. You just have to keep trying until the light goes on.

3.1 Translating Binary to Decimal

Both IP addresses and subnet masks are composed of 32 bits divided into 4 octets of 8 bits each. Here is how a single octet translates from binary to decimal. Consider an octet of all ones: 11111111.

128 64 32 16 8 4 2 1

--- -- -- -- - - - -

1 1 1 1 1 1 1 1

128 + 64 + 32 + 16 + 8 + 4 + 2 + 1 = 255

Here's another: 10111001

128 64 32 16 8 4 2 1

--- -- -- -- - - - -

1 0 1 1 1 0 0 1

128 + 0 + 32 +16 + 8 + 0 + 0 + 1 = 185

and 00000000

128 64 32 16 8 4 2 1

--- -- -- -- - - - -

0 0 0 0 0 0 0 0

0 + 0 + 0 + 0 + 0 + 0 + 0 + 0 = 0

3.2 Converting Decimal to Binary

Converting decimal to binary is similar. Consider 175:

128 64 32 16 8 4 2 1

--- -- -- -- - - - -

1 0 1 0 1 1 1 1

128 + 0 + 32 + 0 + 8 + 4 + 2 + 1 = 175

175=10101111

3.3 Simple Subnetting

The simpliest way to subnet is to take the octet in the subnet mask that covers the first unassigned octet in the IP address block, and make all its bits high. Remember, a high bit, a 1, in the subnet mask indicates that that corresponding bit in the IP address is part of the network field. So, if you have a class B network 172.160.0.0, with the subnet mask 255.255.0.0, you have one network with 65, 534 possible addresses. If you take that subnet mask and make all the bits in the third octet high

128 64 32 16 8 4 2 1

--- -- -- -- - - - -

1 1 1 1 1 1 1 1

128 + 64 + 32 + 16 + 8 + 4 + 2 + 1 = 255

you get the subnet mask 255.255.255.0.

172.60. 0. 0

255.255.255.0

Now the third octet of all the addresses on this network are part of the network field instead of the host field. That is one octet, or eight bits, that can be manipulated to create subnets. 2^8-2=254 possible subnets now on this class B network.

One octet is left for the host field. 2^8-2=254 possible host addressed on each subnet.

3.4 Advanced Subnetting

That is the simplist way to subnet, but it may not be the most desirable. You might not want 254 subnets on your class B network. Instead, you might use a subnet mask like 255.255.224.0. How many subnets would this give you? The first step is to see how many bits are allocated to the network by this mask.

128 64 32 16 8 4 2 1

--- -- -- -- - - - -

1 1 1 0 0 0 0 0

128 + 64 + 32 + 0 + 0 + 0 + 0 + 0 = 224

3 bits are allocated. 2^3-2=6 subnets.

How many hosts on each subnet? Well, 5 bits from this octet are left for the host field, and 8 bits in the fourth octet, for a total of 13 bits in the host field. 2^13-2=8190 possible hosts on each subnet.

The subnet mask is always extended by masking off the next bit in the address, from left to right. Thus, the last octet in the subnet mask will always be one of these: 128, 192, 224, 240, 248, 252, 254 or 255.

Given the IP address of a host and the subnet address for the network, you need to be able to calculate which subnet that host is on. To do this we compare the binary representation of the pertinent octet of the subnet mask witht he binary representation of the corresponding octet in the IP address. Example:

IP address=172.60.50.2

subnet mask=255.255.224.0

50= 00110010

224=11100000

We perform a logical on these two numbers. We will be left with only the bits where there is a one in both octets.

00110010

11100000

--------

00100000=32

This host is on subnet 172.60.32.0.

We also need to be able to find the range of assignable IP addresses on this subnet. To do this, we take the binary that tells us the subnet address, in this case 00100000, and compare it with the subnet mask.

00100000

11100000

The bits convered by the mask we will leave as they are. The rest of the bits we make high. So

00100000

11100000

--------

0011111=63

The range of assignable IP addresses on the subnet 172.60.32.0 is 172.60.32.1-172.60.63.254.

On every network and subnet, two addresses are reserved. At the low end of the range of addresses for the network or subnet, in this case 172.60.64.0, is the address for the network or subnet itself. The address at the high end of the range of addresses, in this case 172.60.95.255, is the broadcast address. Any message sent to the broadcast address will be received by every host on the network.

4. Sample Problem

Here is a sample problem for you to calculate. When you are done, you can check your answers using an online subnet calcualtor at Tactix Engineering.

IP address: 154.16.52.16

subnet mask: 255.255.240.0

Find:

Number of subnets possible on this network:

Number of hosts possible on each subnet:

Which subnet this address is on:

Range of addresses on that subnet:

Authored by Josh Gentry

Top

Table of Contents

Overview

Supported Protocols

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crovr.htm" \l "xtocid90182" Software Images

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crovr.htm" \l "xtocid90183" Administrative Configuration Options

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crovr.htm" \l "xtocid90184" Command Levels

Overview

Cisco700 series routers connect small office Ethernet LANs to corporate networks through Integrated Services Digital Network (ISDN) Basic Rate Interface (BRI) lines. After configuration, the router automatically routes packets to and from remote destinations using IP or Internetwork Packet Exchange (IPX).

The Cisco700 series router is a fixed configuration router. The router operating system is called CiscoIOS-700 software and is unique to the Cisco700 series router.

Supported Protocols

The Cisco700 series routers support the following protocols:

IP

IPX

Internet Protocol Control Protocol (IPCP)

Internet Control Message Protocol (ICMP)

Internetwork Packet Exchange Control Protocol (IPXCP)

Point-to-Point Protocol (PPP)

Bridge Control Protocol (BCP)

Multilink PPP (MLPPP)

Address Resolution Protocol (ARP)

Service Advertisement Protocol (SAP)

Password Authentication Protocol (PAP)

Trivial File Transfer Protocol (TFTP server)

Simple Network Management Protocol (SNMP)

Routing Information Protocol (RIP) for IP and IPX

Triggered RIP for IP

Challenge Handshake Authentication Protocol (CHAP)

Dynamic Host Configuration Protocol (DHCP)

Port and Address Translation (PAT)

Remote Common Application Programmers Interface (RCAPI)

ISDN Device Control Protocol (ISDN-DCP)

Software Images

The Cisco 700 Series routers run a proprietary Cisco software (CiscoIOS-700 software) image, which is different than traditional Cisco IOS software. The image you use varies, depending on the region in which the router is used and what feature set you desire. The image name, for example, c760-in.r-TPH.43-1.bin, designates the region and features. The regions are as follows:

US for use in North America

NET3 for use in Europe

TR6 for use in Germany

INS for use in Japan

TPH for use in Australia

The features are indicated as follows:

Internet Ready (IP only, 30 users with data compression on) images have a "b" designation.

Internet Ready X.25 (IP only, four LAN devices, compression, X.25) images have a "bxd" designation.

Remote Office (IP/IPX, 1500 LAN devices, compression) images have an "r" designation.

Remote Office X.25 (IP/IPX, 1500 LAN devices, compression, X.25) images have an "rxd" designation.

So the example image named "c760-in.b-TPH.43-1.bin" is a Series 760 router image software Release 4.3(1), with the Internet Ready feature set for Australia. (All Cisco700 series routers run Series 760 router images. There is no Series 770 router images.)

You can verify the image loaded on your router by entering the version command at the command-line prompt. The following example shows a router running a Cisco 760 (c760) image for the United States (US), release 4.0(1), and using the Remote Office (r) feature set:

guest> versionSoftware Version c760-in.r.US 4.0(1) - Jan 14 1997 19:00:23Cisco 766ISDN Stack Revision US 2.10 (5ESS/DMS/NI-1)

Administrative Configuration Options

You can configure routers through the configuration port or across an IP network using Telnet. In addition, CiscoIOS-700 software supports Cisco700 Fast Step software applications. These tools are on the Cisco700 Fast Step CD-ROM in the Cisco700 Quick Reference Guide.

Command Levels

Commands and parameters have different results depending on where they are entered. There are two primary levels, system and profile. The system mode commands are global in nature. The profile mode commands are groups of command parameters that relate to a specific switch or port. For additional information regarding profiles, refer to the Cisco700 Series Router Configuration Guide.

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/index.htm"

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crisd.htm"

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crppp.htm"

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/cisintwk/ita/index.htm"

HYPERLINK "http://www.cisco.com/feedback"

HYPERLINK "http://www.cisco.com/univercd/home/search.htm"

HYPERLINK "http://www.cisco.com/univercd/cc/lib/help.htm"

Posted: Thu Jul 8 12:48:53 PDT 1999 Copyright 1989-1999Cisco Systems Inc.

Table of Contents

System Management Commands

cd

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid150882" help

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid150883" log

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid150884" ping

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid150885" reboot

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid150886" reset packets

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid150887" set baudrate

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid150888" set callduration

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid150889" set calltime

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508810" set compression

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508811" set date

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508812" set default

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508813" set echo

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508814" set ipx trace

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508815" set loopback

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508816" set screenlength

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508817" set serialport

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508818" set systemname

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508819" set time

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508820" set tpad parity

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508821" show

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508822" show callduration

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508823" show calltime

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508824" show configuration

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508825" show connection

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508826" show demand

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508827" show memstat

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508828" show packets

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508829" show tpad

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508830" show users

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508831" swl

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508832" test

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508833" upload

HYPERLINK "http://www.cisco.com/univercd/cc/td/doc/product/access/acs_fix/750/700cr44/700crsys.htm" \l "xtocid1508834" version

System Management Commands

This chapter describes the commands for system interfaces, system booting, and terminal sessions. The system interface commands display the router configuration in various forms using the show commands. The system booting commands are used to reboot the router, download software, and reset configuration value to their defaults. The terminal session commands manage communications between an ASCII terminal or a PC running terminal emulation software and the router. (The Cisco700 Series Installation Guide provides instructions for connecting a terminal to the router.)

cd

To create a profile, enter an existing profile, or return to system mode, use the cd command (also known as the change user command).

CD [username]

Syntax Description

usernameProfile name.

Command Mode

System or profile mode

Usage Guidelines

This command creates a profile if the user name does not exist or moves to the specified profile if the user name does exist. From within a profile, this command returns from the profile to system mode.

The user name displays in the prompt, following the router name.

The user name can be abbreviated to the fewest number of characters that make the name unique. The minimum is two characters. The maximum is 64 characters. User names are not case-sensitive. If no user name is specified, you return to system mode.

For authentication purposes, the user name is the string the remote device uses as a username when authenticating itself through Point-to-Point Protocol (PPP).

Example

The following example moves from system mode (where the router name is Host) to a profile named 2503:

Host> cd 2503Host:2503>

help

To display a list of commands and the syntax for each command, use the help command.

HElp [cmd [modifier]]

Syntax Description

cmdAll commands for the specified group are listed. The most useful are set commands, reset commands, show commands, log commands, test commands, and unset commands.

modifierAll modifiers for the specified command are listed. The most useful are ip (Internet Protocol), ipx (Internetwork Packet Exchange), and snmp (Simple Network Management Protocol).

Default

NoneCommand Mode


Usage Guidelines

Use this command to display online help information about commands. You can enter a question mark (?) in place of the word "help." Used without parameters, the command displays all the commands.

Example

The following example displays help for the call command:

Host> help callCAll [ C# | L# | # | C#/L# | C#/# | #/# ] [ P# | CH# | P#/CH# ] []

where

C# indicates a Connection number

# or L# indicates a Link number

C#/L# or #/# indicates Link of a Connection

P# indicates Port

CH# indicates Channel

P#/CH# indicates Channel of a Port

and to Quit or for MORE

log

To implement the logging functions, use the log command.

LOg NOne | CAlls | MEssage | ERrors | IPx [TIme] [VErbose] LOg [LAN | connection] PAckets | TRaffic [CHannel = channel] [VErbose [INbound | OUtbound]]

NOneDisable all logging.

CAllsLog call statistics. Each major call event is logged, and a message displays every time a channel is assigned a connection.

MEssageDisplay a message when a channel is assigned a connection.

ERrorsLog error messages that otherwise are not displayed, including buffer allocation errors, mail delivery errors, and chip-level errors.

IPxDisplay messages when Service Advertisement Protocol (SAP) entries get changed, interface characteristics are set or changed, or when erroneous Routing Information Protocol (RIP) information is received.

TImeDisplay time and date of each logged event or message.

VErboseLog all layers of the ISDN call control stack and traffic by printing the entire packet.

LANEnable logging for the LAN connection. Used with packets or traffic.

PAckets Display statistics on packet routing once per second. Number of packets filtered, forwarded, received, and the packet queue lengths are displayed.

TRafficDisplay a one-character indicator of each packet sent on the connection or the whole packet when verbose is specified.

CHannelProvide the channel number (logs traffic on a channel before the channel is assigned to a connection). This is primarily used to diagnose Point-to-Point Protocol (PPP) negotiation problems.

INbound OUtboundIn conjunction with verbose, restrict the packet content display to either incoming or outgoing packets.

Syntax Description

Default

Log callsCommand Mode


Usage Guidelines

The log command displays all enabled logged entries. More than one keyword can be entered at a time.

Examples

The following example shows output from the log calls command:

Host> log calls timecb760>ca16545

04/04/199600:24:08L0506545OutgoingCallInitiated

cb760>cb760>01/01/199500:24:10L040LineDeactivated

cb760>01/01/199500:24:10L270Disconnected

cb760>

The following example shows output from the log messages command:

Host> log messages> Host> 04/04/1996 04:19:26 L05 0 814159031604 Outgoing Call Initiated

Host>0500-->04000001

01000280131d180200032c

0c383134313539303331

3630356c090000373734

3238363504028890

Host>04/04/199604:19:26L050814159031605OutgoingCallInitiated

Host0400-->03000180120340b548

0801008004028890180183

2c0c3831343135393033

313630346c0900803737

3432383635

Host>0400-->03000280130340b548

0801008004028890180183

2c0c3831343135393033

313630356c0900803737

3432383635

Host>0300-->04000280130341b3f6

02011498180189

The following example shows output from the log messages verbose command:

Host> log messages verboseHost>0300-->020a0280150240b3f6

0801160f

Host>0400-->05000004

04000280150418020101

Host>020a-->02000200000140b3f6

0093fa2e

0801160f

Host>0200-->020a0000000141b3f6

02810ce0

08019507

Host>04/04/1995604:22:48L082814159031605CallConnected

Host>020a-->03000100000241b3f6

02810ce0

08019507

Host>020a-->02000100000140b0c6

0281010e

The following example shows output from the log errors command:

2865_66> log errors2865_66> Log Errors: 11003 IPX RIP Not Sent To Virtual Conn 3

2865_66> Log Errors: 11003 IPX RIP Not Sent To Virtual Conn 3




2865_66>

ping

To determine whether a system can be reached on any connected interface, use the ping command.

PIng ipaddressSyntax Description

ipaddressIP address of the target system.

Default

None

Command Mode


Usage Guidelines

The router generates a ping packet that includes the source address of the profile from which it was sent. If the destination can be reached, the round-trip delay is determined and reported. If the destination cannot be reached, a "no response" message is generated.

The ping command automatically tries three times to reach the destination.

Example

The following example illustrates a successful ping:

Host> ping 172.16.2.1start sending : round trip time is 40 msec.

start sending : round trip time is 40 msec.

start sending : round trip time is 40 msec.

The following example illustrates an unsuccessful ping:

Host> ping 172.16.2.1start sending : no response

start sending : no response

start sending : no response

reboot

To boot the router manually, use the reboot command.

REBootDefault

None

Command Mode


Example

The following example shows a manual reboot:

Host> rebootBoot version 2.1(1) 08/13/97 17:33

Copyright (c) 1993-1997. All rights reserved.

POST ............ OK (1.5MB).

Validating FLASH ... OK.

Booting up ............................

01/01/199500:00:00Connection1Opened

tomd>01/01/199500:00:00L010StartedOperation

tomd>01/01/199500:00:01Connection2Opened

Related Commands

set baudrateset defaultreset packets

To set accumulated packet counts to zero for one connection, use the reset packets command.

REset [connection | LAN] PACkets [ALl]

Syntax Description

connectionReset accumulated packet counts to zero on the specified connection. If neither a connection number nor LAN is specified, packet counts for the connection associated with the current profile are reset.

LANReset accumulated packet counts to zero on the LAN connection.

ALlReset all accumulated packets.

Default

None

Command Mode

Profile mode

Example

The following example resets the packet counts for profile 2503:

Host:2503> reset packetsRelated Command

show packetsset baudrate

To configure the baud rate for the console port, use the set baudrate command.

SEt BAudrate 300 | 1200 | 2400 | 4800 | 9600 | 19200 | 38400 Syntax Description

300Configure the console port for 300 baud.

1200 Configure the console port for 1200 baud.






Default

9600 baudCommand Mode

System mode

Example

The following example configures the console port for 2400 baud:

Host> set baudrate 2400Related Command

rebootset callduration

To place a limit on the length of time a data call is up, use the set callduration command.

SEt CALLDuration minutesSyntax Description

minutesMaximum duration of a call in minutes. Enter any value between 1 and 1430. A value of 0 turns off any configured limit on data call duration.

Default

None

Command Mode


Usage Guidelines

The set callduration command is allowed only after system-level password authentication is complete.

This command does not affect voice calls.

Example

The following example sets the duration of a data call to 10 minutes:

Host> set callduration 10Related Commands

set calltimeset passwordshow calldurationset calltime

To set the time of day when calls can be made or accepted, use the set calltime command.

SEt CALLTime [VOice | DAta] INcoming | OUTgoing [starttime | endtime]SEt CALLTime [VOice | DAta] INcoming | OUTgoing OFf]

Syntax Description

VOiceTime-of-day parameters affect voice calls only.

DAtaTime-of-day parameters affect data calls only.

INcomingTime-of-day parameters affect incoming calls only.

OUTgoingTime-of-day parameters affect outgoing calls only.

starttimeStarting time of day when calls are allowed. The router uses a 24-hour clock, and the parameter is entered HH:MM format, where HH is a number from 0 to 23, and MM is a two-digit number from 00 to59.

endtimeEnding time of day when calls are no longer allowed. Enter the parameter in HH:MM format, where HH is a number from 0 to 23, and MM is a two-digit number from 00 to 59.

OFf Turn off any configured time-of-day limits on calls.

Default

None

Command Mode

System mode

Usage Guidelines

The system time on the router must be set correctly for this feature to be accurate and effective. System-level password authentication is required before the set calltime command is allowed. The router does not have an auxiliary power supply, such as a battery, to maintain the router clock. If you power-cycle the router, reenter the system date and time.

Example

The following example allows incoming voice calls from 8:00am to 4:00pm:

Host> set calltime voice incoming 08:00 16:00Related Commands

set calldurationset dateset passwordset sntp serverset timeshow calldurationshow calltime set compression

To enable or disable data compression, use the set compression command.

SEt COmpression STac | OFfSyntax Description

STacEnable data compression.

OFfDisable data compression.

Default

STac (enabled)

Command Mode

Profile mode

Usage Guidelines

Turn compression off if you are using High Level Data Link Control (HDLC) protocol.

Example

The following example disables compression for the profile 2503 connection:

Host:2503> set compression offset date

To set the current date, use the set date command.

SEt DAte MM/DD/YYYYSyntax Description

MMA two-digit number from 01 to 12.

DDA two-digit number from 01 to 31.

YYYYA four-digit number from 1994 to 2020.

Default

The default date is 01/01/1995.

Command Mode

System mode

Usage Guidelines

You must reset the date every time the router is booted. The date appears during logging.

Example

The following example configures the date in the router for August 13, 1999:

Host> set date 08/13/1999Related Command

set timeset default

To set all variable parameters to their default values, use the set default command.

SEt DEfaultDefault

None

Command Mode


Usage Guidelines

The set default command resets all parameters to their default values, deletes the user-defined profiles, sets the Auto_Config flag to FALSE, and reboots the router. Setting the Auto_Config flag to FALSE triggers the auto-configuration procedure in the power-up operation.

The auto-configuration feature allows the router to obtain the configuration file from a remote server by using Bootstrap Protocol(BOOTP). Upon power-up, the router examines the Auto_Config flag stored in nonvolatile RAM (NVRAM). If the Auto_Config flag is FALSE, the router initiates a BOOTP to request an IP address from the server when a connection is established. (If the flag is TRUE, the BOOTP request is not initiated.)

When the router and BOOTP and TFTP servers at the central site are set up, use ping to generate traffic and trigger the ISDN call. When the call is connected, the Cisco700 series router sends a BOOTP request. If the server finds a matching MAC address from BOOTPTAB, the server returns a client profile that includes an IP address and configuration filename. The router initiates a TFTP client request, requesting the server download the configuration file. (The U.S. image requires SPID and switch configuration information before the ISDN connection can be established.)

After successfully loading the configuration file, the router sets the Auto_Config flag to TRUE in NVRAM. In a subsequent power-up operation, if the Auto_Config flag is TRUE, the router does not initiate BOOTP to request a configuration file from the server.

This should be done on the LAN side (Ethernet interface) only. If this operation fails, the Auto_Config flag remains FALSE. If this is done on the WAN side and there is a WAN/PPP connection established, this process is triggered repeatedly on the WAN link.

Example

The following example configures the router to default values:

Host> set defaultRelated Command

rebootset echo

To enable and disable terminal echo of keyboard entries, use the set echo command.

SEt ECho ON | OFf

Syntax Description

ONEnable terminal echo.

OFfDisable terminal echo.

Default

On

Command Mode

System mode

Example

The following example disables terminal echo for the router:

Host> set echo offset ipx trace

To convert IPX packets to hexadecimal values for troubleshooting purposes, use the set ipx trace command.

SEt IPX TRace length | OFf | ONSyntax Description

lengthPacket length (from 1 to 65535).

ONEnable IPX packet conversion to hexadecimal numbers.

OFfDisable IPX packet conversion to hexadecimal numbers.

Default

OffCommand Mode

Profile mode

Examples

The following example enables IPX trace and sets packet length to 4096:

Host> set ipx trace 4096 onThe following example disables IPX trace:

Host> set ipx trace offset loopback

To create a loop from the Cisco700 series router toward the remote router on the ISDN line, use the set loopback command.

SEt [connection] LOOpback ON | OFf

Syntax Description

connectionA connection number on which to create a loop. If no connection number is specified, a loop is created on the connection associated with the current profile. If the router cannot determine the connection number from the profile, the router displays an error message.

ONEnable a loop.

OFfDisable a loop.

Default

Disabled

Command Mode


Usage Guidelines

This command is used with the test command for troubleshooting purposes. In system mode, this command must be used with the connection-number argument. The router displays an error message if a connection number is not specified. In profile mode, the command uses the connection number for the profile. Use the show connection command to display which profiles have a loopback.

Example

The following example creates a loopback on connection 1:

Host> set 1 loopback onRelated Commands

show connectiontestset screenlength

To set the maximum number of lines to display on the terminal, use the set screenlength command.

SEt SCreenlength linesSyntax Description

linesMaximum screen length to display on your terminal. The length can be from 2 to 128 lines.

Default

20 lines

Command Mode

System mode

Example

The following example configures the terminal to display 30 lines:

Host> set screenlength 30Related Commands

set baudrateset serialportset serialport

To toggle the serial port to function as a configuration port or a TPAD (Controller PAD) port, use the set serialport command.

SEt SErialport TPad | COnfigSyntax Description

TPAD Set the serial port as a TPAD port.

COnfigSet the serial port as a configuration port.

Default

COnfig

Command Mode

System mode

Usage Guidelines

When you enable the serial port as a TPAD, communications from a configuration terminal to the serial port are not possible. You can enter configuration commands by using Telnet. (Refer to the Cisco700 Series Installation Guide for information on connecting a terminal to the router.)

To switch from TPAD mode to configuration mode, do one of the following:

From the terminal connected to the serial port, enter ^A three times, followed by a Return to restore the prompt.

From a Telnet session, enter the set serial config command.

Attention (AT) commands are entered at the prompt on the TPAD terminal.

There are two mode of operation in the TPAD implementation that respond to the enhanced point-of-sale system (EPOS), Verbose and Terse. In Verbose mode, the response is in strings, such as "CONNECT," "NO CARRIER," "BUSY" and so forth. In Terse mode the response is in numbers, such as 1 (CONNECT), 3 (DISCONNECT), 7 (BUSY), and so forth.

When the router is in TPAD mode, these responses are echoed to a terminal attached to the router serial port. Prior to software Release 4.3(1), the mode of operation was always verbose with echo on. In software Release 4.3(1), a series of TPAD commands were implemented to support RIVA functionality.

Multiple commands can be entered on a single line.

Table2-1: AT Commands

Command Description

ATV0Response strings display in Terse mode (as numbers).

ATV1Response strings display in Verbose mode (as strings). Default.

ATE0Disable echoing commands.

ATE1Enable echoing commands (default).

ATPPulse dial prefix.

ATDTTone dial prefix.

AT&F Force factory defaults.

ATS7Set carrier wait time.

The current state of the serial port can be displayed by using the show configuration command.

Example

The following example sets the serial port as a TPAD port:

Host> set serialport tpad

Related Commands

set tpad parityshow configurationshow tpadset systemname

To configure the router name as the system prompt and for Point-to-Point Protocol (PPP) authentication, use the setsystemname command.

SEt SYstemname [systemname]

Syntax Description

systemnameName used as the system prompt.

Default

No system name

Command Mode

System mode

Usage Guidelines

The system name is case sensitive and can be from 1 to 64 characters. If no system name is entered, the system name is blanked.

The system name identifies the router when making PPP connections to an Internet service provider (ISP) if there is no PPP client name in the profile defined with the set ppp clientname command. If a PPP client name is defined in the profile, the router uses the PPP client name for PPP authentication; the router retains the system name as part of the prompt. To delete the system name, enter the systemname command without an argument.

Example

The following example sets the system name to Host:

> set systemname HostHost>

Related Command

set ppp clientnameset time

To set the current time, use the set time command.

SEt TIme HH:MM:SSSyntax Description

HHA two-digit number from 00 to 23.

MMA two-digit number from 00 to 59.

SSA two-digit number from 00 to 59.

Default

None

Command Mode

System mode

Usage Guidelines

The time must be reset whenever the router is rebooted.

Example

The following example configures the current time in the router:

Host> set time 08:48:20Related Command

set calltimeset tpad parity

To select the communications parameters for TPAD, use the set tpad parity command.SEt TPad PArity EVen | ODd | NoneSyntax Description

EVen7 data bits, 1 stop bit, and even parity.

ODd7 data bits, 1 stop bit, and odd parity.

None8 data bits, 1 stop bit, and no parity.

Default

None (8 data bits, 1 stop bit, and no parity)

Command Mode

System mode

Usage Guidelines

You can change parity of TPAD communications in software Release4.1(2) and higher. (In software Release4.1(1), serial port communication is limited to 8 data bits, 1 stop bit, and no parity.)

The TPAD protocol requires the following X.25 fixed parameters:

LAPB (Link Access Procedure, Balanced)

T1 Timer - 1 second

N2 Retry Count - 2

DTE only

K frame count - 7

Module 8 only

The X.25 protocol requires the following fixed parameters:

Packet Size - 128 bytes

VC - 1024 to 1279

Window Size - 2

Facility - No

DTE only

Reverse Charging - No

X.28 and other X.25 Packet Assembly Disassemblies (PADs) are not supported because there is no provision for protocol sensing.

The call direction is dial-out only. Incoming calls and two-way calls are not supported.

Cisco700 series router software Release 4.2(1) supports Network User Information (NUI) and Network User Address (NUA), as described in British Telecom CardWay 0800 Phase3 Access Platform specification.

Example

The following example sets the TPAD to even parity, 7 data bits, and 1 stop bit:

Host> set tpad parity even Related Commands

set serialportshow tpadshow

To display the configuration and the status of both ISDN B channels, use the show command.

SHowCommand Mode


Usage Guidelines

In profile mode, the show command displays only the profile-based configuration parameters. Parameters that have been changed are indicated by an asterisk (*). Values without an asterisk are inherited from the profile template.

In system mode, the show command displays the profile template.

Example

The following example shows output from the show command in system mode:

Host>showSystemParameters

Environment

ScreenLength20

EchoModeON

CountryGroup1

BridgingParameters

LANForwardModeANY

WANForwardModeONLY

AddressAgeTimeOFF

CallStartupParameters

MultidestinationOFF

LineParameters

SwitchType5ESS

AutoSPIDandSwitchDetectionOFF

CallParametersLink1Link2

RetryDelay3030

ProfileParameters

BridgingParameters

BridgingON

RoutedProtocols

LearnModeON

PassthruOFF


LineParameters

LineSpeedAUTO

NumberingPlanNORMAL


AutoONON

CalledNumber

BackupNumber

RingbackNumber

CLICallbackOFF

Status01/01/199500:01:00

LineStatus

LineDeActivated

TerminalIdentifierUnassigned

PortStatusInterfaceConnectionLink

Ch:1WaitingforCall

Ch:2WaitingforCall

Related Command

show configurationshow callduration

To show the current setting for call duration, use the show callduration command.

SHow CALLDurationDefault

None

Command Mode


Example

The following example shows the time limit of a call:

Host> show calldurationHost> Call Duration Limit 10 min.

Related Commands

set calldurationshow calltimeshow calltime

To show the current of time-of-day limits on calls, use the show calltime command.

SHow CALLTimeDefault

None

Command Mode

Profile mode

Example

The following example displays the call-time limits:

Host:2503> show calltime *** Call Time Limits ***

DATA CallsStarttimeEndtime

Incoming00:0014:59

Outgoing00:0023:59

VOICE CallsStarttimeEndtime

Incoming00:0004:59

Outgoing00:0020:59

Related Commands

set calldurationset calltimeshow calldurationshow configuration

To display a subset of the current configuration parameters, use the show configuration command.

SHow COnfig [ALl]Syntax Description

ALlDisplays system configurations and profile configurations in both system mode and profile mode.

Command Mode


Usage Guidelines

In profile mode, the show configuration command without an argument displays only profile-based configurations. Parameters that have been changed are indicated by an asterisk (*). Values without an asterisk are inherited from the profile template. To display the profile template, type the show command in system mode.

Example

The following example shows output from the show configuration command in profile mode:

Host> show configSystemParameters

Environment

ScreenLength20

EchoModeON

CountryGroup1

BridgingParameters

LANForwardModeANY

WANForwardModeONLY

AddressAgeTimeOFF


MultidestinationOFF

LineParameters

SwitchType5ESS

SvcProfileID1123123123

DirectoryNumber(s)01123412345

AutoSPIDandSwitchDetectionOFF


RetryDelay3030

Profile Parameters

BridgingParameters

BridgingON

RoutedProtocolsIP

LearnModeON

PassthruOFF


LineParameters

LineSpeedAUTO

NumberingPlanNORMAL

CallParametersLink1Link2LinkD

AutoONONOFF

PermanentModeONOFFOFF

CalledNumber

BackupNumber

Related Command

show demand show connection

To display all current connections, use the show connection command.

SHow CONNectionCommand Mode

System mode

Example

The following example shows output from the show connection command:

Host> show connectionConnections12/04/199617:49:38

StartDate&Time#Name#Ethernet

112/04/199600:00:00##000000000000

212/04/199600:00:00#Top#

Link:1Channel:1telephone:9018

Link:2Channel:2telephone:9018

Table 2-2 describes the fields shown in the display.

Table2-2: Show Connection Field Descriptions

Field Description

ConnectionsConnection number assigned by the router.

Start DateConnection start date.

Start TimeConnection start time.

NameSystem ID of the remote device.

Ethernet Ethernet address of the remote device.

show demand

To display demand and timeout configurations, use the show demand command.

SHow DEmandCommand Mode


Usage Guidelines

In profile mode, the show demand command displays only profile-based configurations. Parameters that have been changed are indicated by an asterisk (*). Values without an asterisk are inherited from the profile template. To display the profile template, enter the show command in system mode.

Example

The following example displays the profile template:

Host>showdemandDemandCallingParametersLink1Link2

ConnectionTypeAutoONAutoON

Threshold0kbs48kbs

Duration1sec1sec

SourceLANBOTH

Timeout(callteardown)Parameters

Threshold0kbs48kbs

DurationOFFOFF

SourceLANBOTH

Related Commands

demandset timeoutshowtimeoutshow memstat

To display the memory configuration, use the show memstat command.

SHow MEmstatCommand Mode

System mode

Usage Guidelines

The RAM size displays in hexadecimal. For example, a Cisco700 series router with 1MB displays 0x100000, and a router with 1.5MB displays 0x180000.

Table 2-3 lists the RAM size hexadecimal values reported by the show memstat command and the corresponding RAM size in megabytes.

Table2-3: Device RAM Sizes

RAM Size (hex) Memory

0x1000001 MB

0x1800001.5 MB

0x2000002 MB

Example

The following example shows output from the show memstat command:

Host>showmemstatID0:Size:10Avail:8Max:8Used:1Addr:0x000DDBA8

ID1:Size:30Avail:69Max:80Used:16Addr:0x000DDDE2

ID2:Size:18Avail:35Max:35Used:0Addr:0x000DE5A8

ID3:Size:4Avail:36Max:36Used:0Addr:0x000DE850

ID4:Size:8Avail:220Max:220Used:1Addr:0x000DE908

ID5:Size:32Avail:223Max:400Used:180Addr:0x000E0650



ID8:Size:14Avail:124Max:200Used:76Addr:0x000E41E0

ID9:Size:54Avail:38Max:50Used:17Addr:0x000E629A

ID10:Size:8Avail:1Max:2Used:1Addr:0x000EEC40

ID11:Size:54Avail:6Max:6Used:0Addr:0x000EEC70

ID12:Size:462Avail:4Max:4Used:0Addr:0x000EF588

ID13:Size:134Avail:2Max:2Used:0Addr:0x000F00C0

ID14:Size:68Avail:5Max:5Used:1Addr:0x000F0BB8

ID15:Size:96Avail:5Max:6Used:2Addr:0x000F0DA0

ID16:Size:112Avail:2Max:2Used:0Addr:0x000F0FA8

NVStoreUsed:1203,Remaining6989(Deleted77+Unused6912),Total8192

RamStoreUsed:0,Remaining10000,Total10000

RAMSize=0x180000

Availablememory=517088,Allocs=119,Frees=0

MbufAllocs=0x5,MbufFrees=0x5,MbufFail=0x0

IbufAllocs=0x0,IbufFrees=0x0,IbufFails=0x0

MlenMax=0xe0,MlenAvail=0xe0,MlenLow=0xdf,MlenAllocs=0x5,MlenFails=0x0

ZeroMax=0x0,ZeroAvail=0x0,ZeroLow=0x7fff,ZeroAllocs=0x0,ZeroFails=0x0

show packets

To display packet count statistics, use the show packets command.

SHow [connection | LAn] PAckets

Syntax Description

connectionDisplay packet statistics for the connection number. If no connection number is entered, the router displays statistics for the current profile.

LAnDisplay packet statistics for the LAN connection.

Command Mode


Examples

The following example shows the statistics for connection 14:

host> show 14 packetsPacketStatisticsforConnection14

Filtered:11013246Forwarded:8400Received:5993

Dropped:263Lost:0Corrupted:0Misordered:1

CompressionRatio:1.73:1

EthernetType:0806Count:3375


EthernetType:80f3Count:1068

EthernetType:809bCount:48718

The following example shows statistics for the LAN connection:

Host> show lan packetsPacketStatisticsforLAN

Filtered:11001795Forwarded:12411637Received:25496880

Dropped:0Lost:6911Corrupted:46Misordered:0



EthernetType:80f3Count:1068

EthernetType:809bCount:48718

Table 2-4 describes the fields.

Table2-4: Show Packets Field Descriptions

Field Description

FilteredPackets received by the bridge engine and not forwarded.

Forwarded Packets forwarded to specified connection.

ReceivedPackets received from the specified connection.

DroppedPackets received from the connection and dropped because the queue of packets to be forwarded was too long.

LostPackets received from the connection but not successfully transmitted (often because of a faulty Ethernet connection).

CorruptedPackets received from the connection with a bad checksum (CRC) that were discarded as corrupted.

Misordered Packet received out of sequence when using ordered or fragmented protocol.

CompressionPackets compressed.

Ethernet Type Broadcast packet types received.

Count Number of packets of this type received.

show tpad

To display the TPAD parity, use the show tpad command.

SHow TPadDefault

None

Command Mode

System or profile level

Example

The following example displays the TPAD parity setting:

Host> show tpadTPADSerialPortParity:NONE

TPADEchoResponse:ON

TPADResponseMode:VerboseMode

TPADCarrierWaitTime:10seconds

Related Commands

set serialportset tpad parityshow users

To display all profiles and their status, use the show users command.

SHow USersCommand Mode

System mode

Example

The following example shows output from the show users command:

Host> show usersUserStateConnection

--------------------------------------------

LANActiveLAN

InternalActiveINTERNAL

StandardActive1

tomdInactive

Table 2-5 describes the fields shown in the display.

Table2-5: Show Users Field Descriptions

Field Description

Profile NameName of profile.

StateActive or inactive.

ConnectionName or number of the connection assigned to the profile.

swl

To download new router software or configuration files across a TCP/IP network using Trivial File Transfer Protocol (TFTP) or through the configuration port using a serial cable link, use the swl command.

SWL [TFTP] [CONFIG] [ipaddress filename]

Syntax Description

TFTPLoad the software across a TCP/IP network by using TFTP or use the router as a TFTP server, depending on the status of the ipaddress and filename parameters. When the parameters are not included, the router is a TFTP (proxy) server.

CONFIGLoad a configuration file across a TCP/IP network by using TFTP.

ipaddressTFTP server IP address used when the router acts as a TFTP client. When the ipaddress is included, the filename must also be included.

filenameName of the software image file when the router acts as a TFTP client during download. The filename should include the directory path if the file is not in the server default directory. When the filename is included, the ipaddress must also be included.

Default

None

Command Mode

System mode

Usage Guidelines

The swl command assumes that communications occur through the configuration port. (See Cisco700 Series Installation Guide for information on connecting a terminal to the router.)

The swl tftp command assumes that communications occur through a TFTP server.

The swl tftp command loads the software across a TCP/IP network by using TFTP when the ipaddress and filename are included. The command sets the router as a TFTP proxy server when an ipaddress and filename are not included. The software or configuration file must be stored on a client server. (TFTP server mode times out in 1minute.)

On the TFTP client, you must use binary file transfer mode to transfer the software file. If the transfer is successful, the router reboots using the downloaded software and the downloaded configuration (if a configuration file was also downloaded). If the transfer was not successful, the router displays an error message or fails to boot, and the software must be reloaded.

The TFTP client and TFTP server implementation is based on RFC 1350. TFTP timeout interval and transfer size options are not implemented.

Examples

The following example loads the operating system software in the router through a serial connection from the terminal to the configuration port. (You can use an ASCII terminal or a personal computer running terminal emulation software.)

To load software with the swl command, follow these steps:

Step1 Connect your terminal to the configuration port on the router.

Step2 Set the baud rate for the terminal to 9600 and the protocol to 8N1.

Step3 Turn on power to the router. The router boots, and when the boot process is complete, the router displays a prompt.

Step4 Enter the swl command:

Host> swlYou are prompted to verify that you are downloading the software image.

Step5 Enter y to continue:

Are you sure? yYou are prompted for the baud rate.

BOOT version 2.0(1) 04-16-96 12:03:06

Copyright (c) 1993-1996. All rights reserved.

Ready to upload new firmware into flash. Select baud rate:

1 - 300 baud

2 - 1200 baud

3 - 2400 baud

4 - 4800 baud

5 - 9600 baud

6 - 19200 baud

7 - 38400 baud

8 - 57600 baud

9 - 115200 baud

Step6 At the prompt, enter one of the baud rates listed (do not press the Return key), and make sure that the load rate you choose is supported by your terminal emulation software. Table 2-6 shows the approximate software load times.

Table2-6: Approximate Software Load Time

Load Rate (Baud) Approximate Time (Minutes)

240048

960012

192006

38400 3

576002

1152001

Step7 Change the baud rate of the terminal to the appropriate download rate.

Step8 Set the protocol to ASCII on the terminal.

Step9 Download the file containing the new software to the router by following the prompts on your terminal. (The LINE LED blinks throughout the loading process.)

You are prompted to change the terminal baud rate to 9600.

Change settings to 8n1/9600 baud and press a key

Step10 Change the baud rate of the terminal emulation software to the appropriate baud rate and press any key.

When the download is successful, the LINE LED turns off, and the RDY LED turns on. If the download was not successful, use Table 2-7, which shows symptoms and possible solutions.

Table2-7: Software Download Command Troubleshooting

Symptom Probable Cause and Solution

Download takes significantly longer than the approximate time listed in Table 2-6.The terminal emulation program interline and intercharacter delays are not set to zero. If the load was successful, no further action is necessary. If the load was terminated prematurely, reset the interline and intercharacter delays to zero, and reload the software.

The terminal displays unrecognizable text after the download is completed.The terminal has not been reset to 9600 baud. Reset the terminal any time after loading the new software. After changing the terminal baud rate, press Return to gain access to the standard prompt (>).

Two or more LEDs are blinking.Incorrect configuration of the PC COM port or a defective console cable. Press Esc on the keyboard, and try to load the software again.

TFTP File Transfer Example

The following example shows the transfer of an image by using TFTP. The router is the server and the workstation is the client. (Before beginning this procedure, configure your workstation to operate as a TFTP client. In server mode, the workstation only accepts put requests for the file.

Step1 Check the file directory to confirm that the new software and, optionally, the new configuration file are installed on the TFTP server.

Step2 Ping the TFTP server from the router to confirm that the router can be reached from the client machine:

Host> ping clientipaddressCaution When the swl tftp command is entered, the existing software is erased. If a catastrophic event such as a power failure occurs before the file transfer is complete, the router must be initialized through the configuration port.

Step3 Enter the swl tftp command to load the software image on the router:

Host> swl tftp 171.69.91.33 foxus.flAre you sure? yHost>

SWL TFTP: Starting transfer ...

SWL TFTP: Transfer successful.

Image received successfully.

Burning flash, standby (15 seconds max.) ...

The software is downloaded. You can follow the same procedure using the swl tftp config command to download a configuration:

Host> swl tftp config 171.69.91.33 efoxcfg.txtAre you sure? yHost>

SWL TFTP: Starting transfer ...

S

cisco router 3700series

Documents