|
|
An Internet router card is a low-end router module, which has functionality similar to the Cisco 2503, that is inserted into a hub. The following interfaces and ports are provided by this card:
With this card inserted, a hub positioned for LAN connectivity can also have the intelligence of a router to direct traffic.
These Internet router cards function within supported 10BaseT hubs.
Depending on which type of hub the router card is inserted in to (such as a 10BaseT hub or 100VG hub), the system software will set up to configure a standard Ethernet interface or a 100VG interface. If the router card is not properly connected to the hub, the default LAN interface is for10BaseT Ethernet.
Except for configuring the 100VG interface, there is no new configuration information provided for configuring a router card. Its configuration is similar to a Cisco 2503. All software functions on the router card can be configured or enabled using existing printed documentation. Refer to the following two documents for configuration information:
The 100VG interface is compatible with and specified by IEEE 802.12. This 100-Mbps interface is indirectly provided over a Category 3 or Category 5 unshielded twisted-pair (UTP) cable, and it supports 802.3 Ethernet packets.
Configure a 100VG interface as you would any Ethernet or Fast Ethernet interface. To configure the 100VG interface, perform the following tasks beginning in global configuration mode:
| Task | Command |
|---|---|
| Step 1 Specify a 100VG-AnyLAN interface and enter interface configuration.1 | interface vg-anylan interface-number |
| Step 2 Specify the IP address and subnet mask to the interface. | ip address ip-address mask |
To display information about the 100VG-AnyLAN interface, use the show interfaces vg-anylan EXEC command.
This section provides two sample configurations to run on the router card, depending on which type of hub (such as 10BaseT or 100VG) the card is connected. Be sure to use your own addresses and passwords.
The output in the following examples is created with the show config user EXEC command after the router card is configured and the configuration file is saved to NVRAM. The content of the router card's configuration file depends on your network's configuration (for example, supported protocols, available interfaces, and installed hardware). See the Cisco 2500 Series Router Installation and Configuration Guide for step-by-step instructions on how to configure the router once you boot it up for the first time.
The router card in the following example is inserted in a 10BaseT hub and has its 10BaseT Ethernet interface configured, which is on the card's backplane.
version 11.1 service udp-small-servers service tcp-small-servers ! hostname UUT ! username router1 password 7 1042081B vines routing 40000003:0001 appletalk routing ! decnet routing 1.3 decnet node-type routing-iv ! clns routing ipx routing 0000.0c00.1234 xns routing 0000.0c00.1234 isdn switch-type basic-ni1 ! interface Serial0 ip address 10.0.0.4 255.0.0.0 no keepalive vines metric 1 appletalk cable-range 40-40 40.236 appletalk zone zone4 decnet cost 10 ipx network 40 xns network 40 clockrate 2000000 clns router iso-igrp bridge-group 1 ! interface Serial1 ip address 10.0.1.4 255.0.0.0 no keepalive vines metric 1 appletalk cable-range 50-50 50.1 appletalk zone zone5 decnet cost 10 ipx network 50 xns network 50 clockrate 2000000 clns router iso-igrp bridge-group 1 ! interface BRI0 ip address 10.0.0.2 255.0.0.0 no ip mroute-cache encapsulation ppp no ip route-cache no keepalive isdn spid1 0835866201 8358662 isdn spid2 0835866401 8358664 dialer map ip 10.0.0.1 broadcast 8358661 dialer-group 1 ppp authentication chap ! interface ethernet0 ip address 10.0.0.5 255.0.0.0 vines metric 1 appletalk cable-range 20-20 20.189 appletalk zone zone2 appletalk zone zone2 decnet cost 4 ipx network 20 xns network 20 clns router iso-igrp bridge-group 1 ! router iso-igrp net 47.0005.004d.0001.0000.0c00.2222.00 ! router igrp 2 network 7.0.0.0 network 8.0.0.0 network 9.0.0.0 network 10.0.0.0 ! no ip classless ip route 172.16.0.1 255.255.255.255 7.0.0.2 ! dialer-list 1 protocol ip permit bridge 1 protocol ieee ! line con 0 exec-timeout 0 0 line aux 0 transport input all line vty 0 4 login end
This section documents new and modified commands. Refer to the Cisco IOS Release 11.2 documentation set for additional commands used with this feature.
To specify the 100VG interface on a Internet router card, use the interface vg-anylan global configuration command.
interface vg-anylan interface-number| interface-number | Specifies the VG interface number. The only available interface number is 0. |
No VG interface is identified.
Global configuration
This command first appeared in Cisco IOS Release 11.2 P.
The 100VG interface is compatible with and specified by IEEE 802.12. This 100-Mbps interface is indirectly provided over a Category 3 or Category 5 unshielded twisted-pair (UTP) cable, and it supports 802.3 Ethernet packets.
You configure the 100VG interface as you would any Ethernet or Fast Ethernet interface. This interface can be monitored with the IEEE 802.12 Interface MIB.
The following example specifies the 100VG interface, which is directly connected to a 100VG hub from the router card's backplane:
Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z. Router(config)#interface vg-anylan 0Router(config-if)#
show interfaces vg-anylan
To show 100VG controller chip information for an Internet router card, use to the show controller vg user EXEC command.
show controller vgUser EXEC
This command first appeared in Cisco IOS Release 11.2 P.
The following is sample output displaying the status of the 100VG controller chip while the Internet router card is connected directly to a 100VG hub via the card's backplane. This command is generally used for debugging purposes.
If the router card was connected to a 10BaseT Ethernet hub, then the LAN type field in the output would read LAN type: 10Mb Ethernet/802.3.
Router# show controller vg
HOOD unit 0, idb 0xADB50, ds 0xAF538, regaddr = 0x2134400, reset_mask 0x2
rx_size=16, tx_size=4, tx_count=0
tx_p=0xAF54E, head_txp=0xAF552, tail_txp=0xAF552
data port: memory mapped (0x02130000), LAN type: 100VG/802.12
station address 0000.0c0c.0a0a,default station address 0000.0c0c.0a0a
buffer size 1524
HOOD Registers:
hw_id: 5048, hw_id & page: 8053, opr1=0x66, opr2=0x00, opr3=0x00
Page 0 - Performance:
isr=0x1000, imr=0x0A06, flreg=0x0000
tx free mem: lsw=0x0020 msw=0x0080
rxcnt=0x0, txcnt=0x0
Page 1 - MAC Address/Hash Table:
paddr: 0000.0c0c.0a0a, hash bytes: 06 00 00 00 00 00 00 00
Page 2 - Hardware Mapping:
mmmsw=0x0000, mmlsw=0x0000, iomap=0x00, irqchn=0x00
sramreg=0x00, bmreg=0x00, mdcnt1=0x00, mdcnt2=0x00
Page 3 - EEPROM/Boot ROM:
sdcr=0x0000, btrom1=0x0000, btrom2=0x0000
Page 4 - LAN Configuration:
tccnf1=0x00, tccnf2=0x00
vccnf=0xFF, vtrrg=0x1820, valow=0x0080
maccr1=0xFE, maccr2=0x00, maccr3=0x00, maccr4=0x01
show interface vg-anylan
To display information about the 100VG interface on an Internet router card, use the show interfaces vg-anylan user EXEC command.
show interfaces vg-anylan [number]| number | (Optional) Specifies the VG LAN interface number. The only available interface number is 0. |
User EXEC
The following is sample output from the show interfaces vg-anylan command.
Router# show interfaces vg-anylan 0
VG-AnyLAN0 is up, line protocol is up
Hardware is HOOD
Frame type is 802.3, address is 0000.0c0c.0a0a (bia 0000.0c0c.0a0a)
Internet address is 4.1.1.2/8
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:09, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 input packets with dribble condition detected
22194 packets output, 2184910 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
0 output buffer failures, 0 output buffers swapped out
0 vg alignment error, 0 vg balance error
0 vg invalid ipm error, 0 vg symbol error
0 vg skew error, 0 vg frame delimit error
0 vg high priority packets, 0 vg high priority octects
Table 2 describes significant fields in this output.
| Field | Description |
|---|---|
| VG-AnyLAN0 is up, line protocol is up | Indicates whether the interface hardware is currently active and can transmit and receive or if it has been taken down by an administrator. |
| Hardware is HOOD | Type of hardware used to create the interface. |
| Frame type is 802.3 | Currently the frame type supported is 802.3. |
| Internet address | Internet address and subnet mask. |
| MTU | Maximum transmission unit of the interface. |
| BW | Bandwidth of the interface in kilobits per second. |
| DLY | Delay of the interface in microseconds. |
| rely | Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes. |
| load | Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes. The calculation uses the value from the bandwidth interface configuration command. |
| Encapsulation | Encapsulation method assigned to interface. |
| loopback | Indicates whether loopbacks are set. |
| keepalive | Indicates whether keepalives are set. |
| ARP type | ARP type on the interface. |
| Last input | Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful in determining when a dead interface failed. |
| output | Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. |
| output hang | Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks (*) are printed. |
| last clearing | Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed. 0:00:00 indicates the counters were cleared more than 231ms (and less then 232ms) ago. |
| Queueing strategy | First-in, first-out queuing strategy (other queuing strategies you might see include priority-list, custom-list, and weighted fair). |
| Output queue, drops; input queue, drops | Number of packets in output and input queues. Each number is followed by a slash (/), the maximum size of the queue, and the number of packets dropped because a queue was full. |
| 5 minute input rate 5 minute output rate | Average number of bits and packets received or transmitted per second in the last 5 minutes. |
| packets input | Total number of error-free packets received by the system. |
| bytes (input) | Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system. |
| no buffer | Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events. |
| broadcasts | Total number of broadcast or multicast packets received by the interface. |
| runts | Number of packets that are discarded because they are smaller than the medium's minimum packet size. |
| giants | Number of packets that are discarded because they exceed the medium's maximum packet size. |
| input errors | Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts. |
| CRC | Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link. |
| frame | Number of packets received incorrectly that have a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems. |
| overrun | Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. |
| ignored | Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented. |
| abort | Illegal sequence of one bits on the interface. |
| input packets with dribble condition detected | Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented for informational purposes only; the router accepts the frame. |
| packets output | Total number of messages transmitted by the system. |
| bytes | Total number of bytes, including data and MAC encapsulation, transmitted by the system. |
| underruns | Number of times that the far-end transmitter has been running faster than the near-end router's receiver can handle. |
| output errors | Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories. |
| collisions | Number of messages retransmitted due to an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). A packet that collides is counted only once in output packets. |
| interface resets | Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down. |
| output buffer failures | Number of times that a packet was not output from the output hold queue because of a shortage of MEMD shared memory, |
| output buffers swapped out | Number of packets stored in main memory when the output queue is full; swapping buffers to main memory prevents packets from being dropped when output is congested. The number is high when traffic is bursty. |
| vg alignment error | Number of non-octets received. |
| vg balance error | Number of incorrect balanced symbols received. |
| vg invalid ipm error | Number of packets received with an invalid packet marker (IPM). |
| vg symbol error | Number of symbols received that were not correctly decoded. |
| vg skew error | Number of skews between four pairs of twisted-pair wire that exceeded the allowable skew. |
| vg frame delimit error | Number of start-of-frame errors or false-start errors received. |
| vg high priority packets | Number of high-priority packets received. |
| vg high priority octets | Number of high-priority octets received. |
interface vg-anylan
The debug vg command is documented in this section.
To monitor error information and 100VG connection activity, use the debug vg EXEC command.
The no debug vg command turns off the debugging function.
The debug vg command could create large amounts of command output.
The following example shows sample output when the debug vg command is issued to monitor connections made to a 100VG hub.
Router# debug vg
VG-AnyLAN network interface debugging is on
Refer to the following documentation for additional software configuration information:
|
|