| |
|
|
The Internet Protocol (IP) is a network-layer protocol that provides addressing and control functions to support routing of data packets. IP is the foundation for the IP routing protocols. IP routing is the process of determining where to forward IP packets so that they can arrive at the destination address.
To operate a router in an IP network, you must first configure the router to support IP addressing and static routes. After these basic steps, you can configure the individual routing protocols in your network. The routing protocol you select depends on the size and configuration of your particular network.
Related Information
Administrators should be familiar with IP operation and theory before configuring the Avici router. The following texts are recommended as further reading:
- TCP/IP Illustrated, Volume 1 The Protocols, Stevens, W. Richard 1994, Addison Wesley Longman, Inc. ISBN 0-201-63346-9
- Internetworking with TCP/IP, Comer, Douglas E. 1995, Prentice-Hall, Inc. ISBN 0-13-216987-8
- Routing in the Internet, Huitema, Christian, 1995, Prentice-Hall, Inc. ISBN 0-13-132192-7
- Interconnections: Bridges and Routers, Perlman, Radia 1992, Addison-Wesley. ISBN 0-201-56332-0
IP Addressing
An IP address is a unique identifier for an interface on an IP network. Each interface on the Avici router must have an IP address assigned before the interface is used to support IP routing.
IP addresses are 32-bit numbers represented by 4 values (each representing 8 bits) separated by decimal points:
Binary format: 10001100. 10110011. 11011100. 00000011 Dotted decimal format: 140. 179. 220. 3 The IP address is divided into two portions: the network prefix identifies the network on which the host resides. The host-number identifies a specific host on the given network.
Classful Addressing
Traditionally, the division between the network prefix and the host number was along the boundaries between octets; i.e., along decimal points:
Figure 1-1. Classful Network Prefix Numbers
This meant that only a limited number of networks with a specific number of hosts could be defined
:
Table 1-1. Maximum Prefix and Host Numbers by Class Maximum # of Prefix Numbers Maximum # of Host Numbers Class A
126
16,777,214
Class B
16,384
65,534
Class C
2,097,152
254
The explosion of the number of sites connected to the Internet has resulted in two problems: depletion of unique IP addresses and the growth of IP routing tables.
Subnetting
Subnetting breaks the host number into two portions: the subnet number and the host number on that subnet to create an extended network prefix:
Figure 1-2. Extended Network Prefix Numbers
All subnets of a given network use the same network prefix, but different subnet numbers. Routers within an organization's subnet must understand their subnet structure, but only a single routing table entry for the prefix number as a whole is advertised to the Internet. Private networks are now able to subnet their internal network structure without increasing the size of the Internet routing tables.
Subnet Masking
The extended network prefix provided by subnetting is identified by the subnet mask. The subnet mask identifies the number of bits in the 32-bit IP address used as the subnet address.
The bits in the subnet mask and the IP address have a one-to-one correspondence. Bits in the subnet mask are set to 1 if the corresponding bit in the IP address is treated as part of the extended prefix number. Conversely, bits in the subnet mask are set to 0 if the corresponding bit in the IP address is treated as a host number.
For example, to use the entire third octet of the IP address 130.5.5.25 as a subnet number, you specify a subnet mask of 255.255.255.0:
The number of bits assigned to the extended prefix length can be expressed by the / <prefix length> notation where prefix length is the number of contiguous 1 bits in the subnet mask. IPriori supports prefix lengths up to /31. In the example above, the subnet mask for IP address 130.5.5.25 starts with 24 contiguous 1 bits. The address and subnet mask can be written as 130.5.5.25/24.
Variable Length Subnet Masks
Since 1987, administrators have been able to divide their networks into subnets with different subnet masks. These variable length subnet masks (VLSM) permit subnets to be tailored to meet specific needs and save valuable IP address space.
The network number is divided into subnets. Some of the subnets may then be further divided into sub-subnets. If required, sub-subnets can also be divided.
Figure 1-3. Dividing Into Subnets
Routing information for each subnet structure is not shared among the subnets.
Supernetting
In 1992, the idea of Classless Interdomain Routing (CIDR) was introduced. CIDR permits supernetting. Supernetting is the practice of extending the classful subnet masks so that a network address and a subnet mask could specify multiple subnets with one address.
Let's say that you need a subnet to support 700 hosts (about three class C networks). You can supernet three class C networks together by extending the network portion of the IP address to include more bits.
PROCEDURE: To calculate the mask for a summary address for three contiguous networks, perform the following steps:
Step 1 Convert each address into binary format
.
10.9.7.0
00001010.00001001.00000111.00000000
10.9.8.0
00001010.00001001.00001000.00000000
10.9.9.0
00001010.00001001.00001001.00000000
Step 2 Determine which bits of the address are the same and which bits are variable.
10.9.7.0
00001010.00001001.00000111.00000000
10.9.8.0
00001010.00001001.00001000.00000000
10.9.9.0
00001010.00001001.00001001.00000000
Step 3 Use 1s in the position of the bits that remain the same and 0s in the position of the bits that change.
10.9.7.0
00001010.00001001.00000111.00000000
10.9.8.0
00001010.00001001.00001000.00000000
10.9.9.0
00001010.00001001.00001001.00000000
mask
11111111.11111111.11110000.00000000
Step 4 Convert back to decimal to determine the summary address mask.
225.225.240.0
11111111.11111111.11110000.00000000
Two important points relevant to addressing in an area:
- Summarization cannot be fully implemented unless the addresses in an area are contiguous assignments.
- The simpler the addressing/subnetting scheme of an area, the simpler the calculation of summary masks.
where the subnet/subnet mask of 130.5.128.0 255.255.252.0 includes all the addresses from 130.5.128.0 to 130.5.131.255. The shorthand notation for the supernet is:
130.5.128.0/22
where the IP address indicates the starting address of the supernet and the subnet mask indicates how many bits are to be used as the network portion of the address.
Overview of IP Configuration
PROCEDURE: To configure IP on your Avici router, use the following steps:
Step 1 Assign IP addresses to interfaces
Step 2 Configure static routes
Step 3 Optionally, configure a default gateway
Assigning IP Addresses to Interfaces
The first step to enable IP routing on your Avici router is to assign an IP address and network mask to each interface. Interfaces are identified by their bay#/slot#port#. All bays are numbered 1- 4.
Use the ip address command to assign an IP address and mask to a specific interface.
Use the show interface command to display the IP address assigned to each interface.
In the following example, the ip address command configures Packet over SONET (POS) interface 1/1/1 with IP address 190.167.0.2 using a 16 bit mask (255.255.0.0)
The show interface pos command displays the new setting:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface pos 1/1/1
router(config-if)#ip address 190.167.0.2 255.255.0.0
router(config-if)#end
router#show interface pos 1/1/1
POS 1/1/1 interface status is up, line protocol is up
Internet address is 190.167.0.2 255.255.0.0
Remote address is 118.12.1.2
MTU 4470 bytes
Payload BW: 150 Mbit/Sec, Total BW: 155 Mbit/Sec
Encapsulation PPP, CRC-32
Loopback: None, Keepalive: Enabled, Scramble: Enabled
LCP: Opened, IPCP: Opened, OSICP: Open, MPLSCP: Closed
Received:
23094 bytes
886 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors, 0 unknown protocols
Transmitted:
26774 bytes
890 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors
Medium Type SONET, Line Coding: NRZ, Line Type: Other
Sonet Loopback: None, Sonet Clock Source: Line
PPP: SNMP Trap link-status: enabled
Sonet/Path: SNMP Trap sonet link-status: enabled
Tx J0 Section Trace: "1"
Rx J0 Section Trace: "1"
Tx Path Trace: "router/POS 1/18/12/3/190.167.0.2"
Rx Path Trace: "router/POS 1/36/11/3/118.11.1.2"
Configuring Static Routes
Static routes move packets to a destination along a specified path. You must explicitly configure static routes using the ip route command. Configure static routes if the routing protocols cannot dynamically discover a route to the destination.
Use the ip route command to configure static routes.
Use the show ip route static command to display the new route.
Configuring Static Routes with Distance
Distance is a value that compares the preference of routes to the same destination learned from a variety of sources. Routes with lower distance values are preferred over routes to the same destination with higher distance values. Each routing protocol has a default distance:
If you use the optional distance value when you configure a static route, you flag the static route for possible override. If a route with a lower distance is learned from another source, the new route overrides that static route.
Example: In the following example, a static route to network 17.1.0.0 is configured with a distance of 120:
router(config)#ip route 17.1.0.0 255.255.0.0 10.1.9.12 120
With the distance value for the static route set to 120:
- Routes that have a lower distance (directly connected networks, or routes learned from OSPF, external BGP, and IS-IS) are preferred over the static route.
- The static route is preferred over routes to the same destination with distance values higher than 120 (routes learned from route aggregation and internal BGP).
Configuring Static Routes with Tag
Route tags communicate information between autonomous system boundary routers. OSPF supports tags. Other protocols have a default tag of zero.
Example: In the following example, a static route is configured with a tag of 1000:
router(config)#ip route 193.1.1.0 255.255.255.0 10.1.9.1 tag 1000
The tag can be used to identify routes for redistribution to other routing protocols or for filtering route advertisements. For example, you can define a match tag clause in a route map to permit or deny only those routes with a specific tag. Tags can be used as the selection criteria for exported routes during redistribution.
Refer to "Redistributing Between Routing Domains for more information about redistribution. Refer to "Route Maps for more information about filtering routes.
Configuring IP Route Verification
IP route verification provides for the discovery and reporting of software to hardware inconsistencies that can cause black holing of traffic, resulting in discarded or mis-forwarded data. Inconsistent state refers to IPv4 route information stored across multiple software and hardware components in the route controller or modules that doesn't agree with respect to the primary source of data reference. Some inconsistencies may be due to transient states caused by changes in network topologies. Verification may fail if the verification process is ongoing during a period of transients. This intentional failure prevents the false reporting of transient states as inconsistencies.
IP route verification is manually initiated at the CLI using a set of commands.
Verification can be configured for all addresses, a range of addresses, or a specific address. The module check can be by-passed for quicker route controller component checking. A specific ingress or egress interface can be optionally specified.
Use the from-interface keyword to perform the verification only on a specific ingress interface.
Use the to-interface keyword to perform the verification only on a specific egress interface.
Use the no-module-check keyword to perform the verification only on the route controller components.
In the syntax formats below ipAddress specifies an IP address/Mask combination.
Complete syntax for IP route verification commands are as follows:
Verifying all IP routes:
Syntax: verify ip route all [from-interface {pos | gbe | composite-link | aggregate-link} interfaceID] [to-interface {pos | gbe | composite-link | aggregate-link} interfaceID] [no-module-check]
Verifying a range of IP routes:
Syntax: verify ip route range start ipAddress [end ipAddress] [from-interface {pos | gbe | composite-link | aggregate-link} interfaceID] [to-interface {pos | gbe | composite-link | aggregate-link} interfaceID] [no-module-check]
Verifying a specific IP route:
Syntax: verify ip route ipAddress [from-interface {pos | gbe | composite-link | aggregate-link} interfaceID] [to-interface {pos | gbe | composite-link | aggregate-link} interfaceID] [no-module-check]
Example 1: In the following example the verify ip route all command verifies all IP routes for this router:
router#verify ip route all
Total Routes verified : 12
Routes consistent in Server : 12
Routes consistent in Modules : 12
Routes inconsistent in Server : 0
Routes inconsistent in Modules : 0
Routes in transient state : 0
Routes Not Verified (unavailability of
system resources) : 0
router#
Example 2: In the following example the verify ip route all no-module-check command verifies all IP routes bypassing the module check:
router#verify ip route all no-module-check
Total Routes verified : 12
Routes consistent in Server : 12
Routes inconsistent in Server : 0
router#
Example 3: In the following example the verify ip route range command verifies IP routes starting and ending at IP address 10.1.1.0/24:
router#verify ip route range start 10.1.1.0/24 end 10.1.1.0/24
Route (10.1.1.0/24) is consistent in server.
Route consistent in # of modules : 12
Route inconsistent in # of modules : 8
router#
Configuring a Default Gateway
Gateway routers connect to more than one network. When configured as a default gateway router, non-local traffic is sent to the router where it is forwarded to the appropriate next hop. If a better route is available, the gateway router sends an ICMP message to the source, indicating the better route.
Use the ip default-gateway command to specify the IP address of a router used as a default gateway.
NOTE The IP address designated as the default gateway must reside on a network directly connected to the router being configured.
Example: In the following example:
- The ip default-gateway command identifies a router at 192.167.10.12 as the default gateway.
- The show running-config command displays the new setting:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface pos 1/1/1
router(config-if)#ip address 190.167.0.2 255.255.0.0
router(config-if)#exit
router(config)#ip route 192.136.136.0 255.255.255.0 10.1.9.12
router(config)#ip default-gateway 192.167.10.12
router(config)#end
router#show running-config
.
.
.
ip default-gateway 192.167.10.12
ip route 7.7.7.0 255.255.255.0 18.5.1.100
ip route 10.0.0.0 255.0.0.0 18.5.1.100
ip route 192.32.228.0 255.255.255.0 80.80.80.2
ip route 192.168.220.0 255.255.255.0 null0
.
.
.
Configuring ECMP
Equal-Cost Multipath (ECMP) sets consist of up to eight routes to same destination address and network mask - but different next-hop gateways. Traffic to the destination is distributed across the next-hops. ECMP is used when:
- There are multiple links to a neighboring router for a destination
- There are multiple neighboring routers that can reach a destination
The IP next-hops in an ECMP set can be neighbors on either standard links or Composite Links.
Each ECMP set can have up to eight next-hops. The links that make up an ECMP set can be of different speeds. Traffic is divided equally between member links regardless of link bandwidth.
NOTE If ECMP members are of different bandwidth and the equal distribution of traffic results in a member receiving traffic that is greater than its bandwidth, loss of traffic will occur.
Refer to "Configuring Static Routes".
To configure the OSPF and IS-IS routing protocols to support ECMP, use the maximum-paths command to set the maximum number of equal-cost paths permitted by the OSPF and/or IS-IS routing protocols.
Example: For example:
router(config)#router isis 13
router(config-router)#maximum-paths 8
router(config-router)#exit
or
router(config)#router ospf 2
router(config-router)#maximum-paths 4
router(config-router)#exit
To configure static routes as an ECMP set, use the ip route command to configure up to four IP static routes or Composite Links with the same destination address and netmask - but different gateway addresses:
router(config)#ip route 192.136.136.0 255.255.255.0 10.1.2.3
router(config)#ip route 192.136.136.0 255.255.255.0 10.3.4.5
router(config)#ip route 192.136.136.0 255.255.255.0 10.5.6.7
router(config)#ip route 192.136.136.0 255.255.255.0 10.7.8.9
Configuring IP Source Routing
The IP header source route option allows the source IP host to set a packet's route through the IP network. With IP source routing enabled, packets containing the source route option are forwarded in accordance with the specified router addresses contained in the header. There are two source route methods: strict and loose. The method used depends upon the contents of the option type field. In the loose source route method, the gateway or host IP is allowed to use any route of any number of other intermediate gateways to reach the next address in the route. In the strict source route method, the gateway or host IP must send the packet directly to the next address in the source route, through only the directly connected network indicated in the next address, to reach the next gateway or host specified in the route. IPriori supports the strict and loose source route IP header options as defined in RFC 791.
If the IP source route option is disabled on this router, IPriori discards all packets containing the IP source route option in its header.
IPriori enables the IP source route option by default.
To disable source routing for this router use the following format in global configuration mode:
no ip source-route
To enable source routing for this router use the following format in global configuration mode:
ip source-route
The following command disables IP source routing for this router:
router#config terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)no ip source-route
Verifying IP Connections
The ping command sends an ICMP echo request packet to a peer's address. The peer replies with an ICMP reply packet. Successful pings verify that the address you ping is valid and alive.
Use the ping command to test network connectivity with a specific peer address.
Example: In the following example, ping sends an echo message to IP address 128.5.23.250:
router>ping 128.5.23.250
PING 128.5.23.250: 56 data bytes
64 bytes from 128.5.23.250: icmp_seq=0. time=0. ms
64 bytes from 128.5.23.250: icmp_seq=1. time=0. ms
64 bytes from 128.5.23.250: icmp_seq=2. time=0. ms
64 bytes from 128.5.23.250: icmp_seq=3. time=0. ms
64 bytes from 128.5.23.250: icmp_seq=4. time=0. ms
----128.5.23.250 PING Statistics----
5 packets transmitted, 5 packets received, 0% packet loss
round-trip (ms) min/avg/max = 0/0/0
Enabling ICMP Unreachable Messaging
If the router receives a non-broadcast packet destined for itself that uses an unknown protocol, it sends an ICMP Protocol Unreachable message back to the source. Similarly, if the router receives a packet that it is unable to deliver to the ultimate destination, because it knows of no route to the destination address, it sends an ICMP Host Unreachable message to the source. This feature is enabled by default.
Use the ip unreachables command to enable the router to send an ICMP unreachable message to the source, if the router receives a packet that has an unrecognized protocol or no route to the destination address.
Use the no ip unreachables command to disable sending ICMP unreachable messages.
Example: In the following example, the ip unreachables command enables sending of ICMP messages on interface POS 1/1/1:
router#config terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#interface pos 1/1/1
router(config-if)#ip unreachables
router(config-if)#end
Specifying Name Servers for Address Resolution
Name servers are servers that contain a mapping database of domain names to IP addresses. This database provides for the matching of fully qualified domains with associated IP addresses. If your network devices require connectivity with devices in networks for which you do not control name assignment, you can assign device names that uniquely identify your devices within the entire internetwork.
Use the ip name-server command to specify up to six name servers to be used for domain name to IP address resolution. The command may be used multiple times as long as the total number of name servers does not exceed six. An error is generated if more than six name servers are specified.
Use the no ip name-server command to delete an IP address from the list of name servers.
Example: In the following example, the ip name-server command specifies two addresses to be used to resolve DNS addressing, and the show hosts command displays the new setting:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#ip name-server 10.1.1.230 10.5.1.240
router(config)#end
router#show hosts
Default domain is avici.com
Domain list: avici.com, avici.webhost.com
Name/address lookup uses domain service
Name servers are 10.1.1.230, 10.5.1.240
Host Flags Age Type Address(es)
testbed24 (perm, OK) ** IP 10.1.2.24
swuser1 (perm, OK) ** IP 10.5.1.9
You can also use the show running-config command to display the new setting:
router#show running-config
.
.
.
ip domain-list avici.com
ip domain-list avici.webhost.com
ip host testbed24 10.1.2.24
ip host swuser1 10.5.1.9
ip domain-name avici.com
ip name-server 10.1.1.230
ip name-server 10.5.1.240
.
.
.
Enabling DNS Name-to-IP Address Translation
If your network devices require connectivity with devices in networks for which you do not control name assignment, you can assign device names that uniquely identify your devices within the entire internetwork. The Internet's global naming scheme, the DNS, accomplishes this task. This service is enabled by default.
Use the ip domain-lookup command to enable DNS host name-to-IP address translation on the Avici router.
Use the no ip domain-lookup command to disable DNS host name-to-IP address translation on the Avici router.
Example: In the following example, the ip domain-lookup command enables DNS host name-to-IP address translation on the Avici router, and the show hosts command displays the new setting:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#ip domain-lookup
router(config)#end
router#show hosts
Default domain is avici.com
Name/address lookup uses domain service
Host Flags Age Type Address(es)
ChicagoPOP (perm, OK) 0 IP 134.34.45.1
BostonPOP (perm, OK) 0 IP 134.34.44.6
LAPOP (perm, OK) 0 IP 134.34.43.60
DenverPOP (perm, OK) 0 IP 134.34.44.8
Defining a Default Domain Name or List
DNS allows you to enter incomplete host names, that is host names without a period followed by a domain name such as "edu" or "com." IPriori uses the default domain name defined by this command to complete such host names.
You can specify a default domain name that the router software will use to complete domain name requests. You can specify either a single domain name or a list of domain names. Any IP host name that does not contain a domain name will have the domain name you specify appended to it before being added to the host table.
If the initial domain name lookup (specified by the ip domain-name command) does not result in a match, IPriori will search the entries in the domain list. Domain lists are searched in the order in which they are defined. Each listing requires a separate command line. The list can contain up to 32 entries.
Use the ip domain-name command to define the default domain name. This default is appended to incomplete host names.
Use the no ip domain-name command to delete the default domain name.
Use the ip domain-list command to define a list of domain names to be searched if the initial domain name resolution does not result in a match.
Use the no ip domain-list command to delete a domain name from the domain list.
Example: In the following example, the ip domain-list command adds two domain names to the list of domain names associated with the default domain name avici.com, and the show hosts command displays the new setting:
router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)#ip domain-list avici.com
router(config)#ip domain-list avici.webhost.com
router(config)#end
router#show hosts
Default domain is avici.com
Domain list: avici.com, avici.webhost.com
Name/address lookup uses domain service
Name servers are 10.1.1.230, 10.5.1.240
Host Flags Age Type Address(es)
testbed24 (perm, OK) ** IP 10.1.2.24
swuser1 (perm, OK) ** IP 10.5.1.9
You can also use the show running-config command to display the new setting:
router#show running-config
.
.
.
ip domain-list avici.com
ip domain-list avici.webhost.com
ip host testbed24 10.1.2.24
ip host swuser1 10.5.1.9
ip domain-name avici.com
ip name-server 10.1.1.230
ip name-server 10.5.1.240
.
.
.
Using IP Trace
IP trace provides a list of routers by both host name (if available) and IP address of all hops between the originating router and the specified destination router.
The trace ip command generates three datagrams addressed to the destination with the time-to-live (TTL) timer set to 1. The first receiving router on the path to the destination reads the timer, discards the packets, and returns an error message.
The trace ip command repeats this process at each level of TTL until the datagram reaches the specified destination, the TTL expires, or you interrupt the sequence.
Output from the trace ip command consists of a list of all the routers between this router and the destination router, including the round trip time for each of the three datagrams sent to that router. The clock granularity is 17ms; any round trip taking less than 17ms will display as 0.000 ms. If a '*' displays instead of a round trip time, the probe datagram timed-out. The timeout interval is five seconds.
Use the trace ip command to display the IP routes a packet will traverse to the specified destination.
Pressing the CTRL-C key sequence aborts the trace.
The format for the trace ip command is as follows:
trace ip dest-address
Example: The following is sample output from the trace ip command initiated at host name server-doc2 and tracing the hops to host name firewall:
router#trace ip firewall
Send to firewall(10.1.1.40) 30 hops max, 40 byte packets
1 sw-gate (10.5.0.1) 0.000 ms 0.000 ms 0.000 ms
2 10.1.4.1 (10.1.4.1) 0.000 ms 0.000 ms 0.000 ms
3 firewall (10.1.1.40) 0.000 ms * 0.000 ms
router#
Configuring an IP Trace Source Address
The source IP address of the trace route IP packets can be optionally specified when using the trace ip command, providing the ability to check for the reachability of a specific source IP address from the trace route destination.
Example: The following is sample output from the trace ip command initiated at host name server-doc2 and tracing the hops to host name firewall from the source address 10.10.10.1:
server-doc2#trace ip firewall 10.10.10.1
Send to firewall(10.1.1.40) from 10.10.10.1 30 hops max, 40 byte packets
1 sw-gate (10.5.0.1) 0.000 ms 0.000 ms 0.000 ms
2 10.1.4.1 (10.1.4.1) 0.000 ms 0.000 ms 0.000 ms
3 firewall (10.1.1.40) 0.000 ms * 0.000 ms
server-doc2#
Displaying IP
The IPriori software includes a variety of commands to display and monitor IP:
Show commands often display network masks as part of the information presented. Network masks can be configured to display in one of three formats: bit-count, decimal and hexadecimal.
Use the term ip netmask-format command to define the format in which netmasks are displayed by the show commands. Network masks are displayed in the decimal format by default.
Example: In the following example:
- The show interface pos command is used to display information about POS interface 1/34/1. The netmask is displayed in bit count format.
- The term ip netmask-format command is used to change the display format for the netmask to decimal.
- The show interface pos command is used to re-display the information about POS interface 1/34/1. The netmask is displayed in decimal format:
router#show interface pos 1/34/1
POS 1/34/1 is up, line protocol is up
Internet address is 20.1.1.2/24
MTU 4470 bytes, BW 622 Mbit/Sec
Encapsulation PPP, CRC-32
Loopback: None, Keepalive: Disabled, Scramble: Enabled
LCP: Opened, IPCP: Opened, OSICP: Closed
Received:
1622 bytes
26 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors, 0 unknown protocols
Transmitted:
110 bytes
6 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors
Medium Type SONET, Line Coding: NRZ, Line Type: MultiMode
Sonet Loopback: None, Sonet Clock Source: Internal
Tx Path Trace: "<NULL>"
Rx Path Trace: "GSRPOS7/0106.10.1.200000000"
router#terminal ip netmask-format decimal
router#show interface pos 1/34/1
POS 1/34/1 is up, line protocol is up
Internet address is 20.1.1.2 255.255.255.0
MTU 4470 bytes, BW 622 Mbit/Sec
Encapsulation PPP, CRC-32
Loopback: None, Keepalive: Disabled, Scramble: Enabled
LCP: Opened, IPCP: Opened, OSICP: Closed
Received:
1982 bytes
31 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors, 0 unknown protocols
Transmitted:
110 bytes
6 directed packets, 0 multicast packets, 0 broadcast packets
0 discards, 0 errors
Medium Type SONET, Line Coding: NRZ, Line Type: MultiMode
Sonet Loopback: None, Sonet Clock Source: Internal
Tx Path Trace: "<NULL>"
Rx Path Trace: "GSRPOS7/0106.10.1.200000000"Ethernet 0
| |
|
|
Copyright © 2005
Avici Systems Inc.
Avici® and TSR®
is a registered trademark of Avici Systems Inc.
IPriori™, Composite Links™, SSR™, QSR, and NSR® are
trademarks of Avici Systems Inc.
Source
File Name: IP.fm
HTML File Name: IP.html
Last Updated: 02/25/05 at 15:33:17