configure serial interfaces...
r1#sh run int s0/0
Building configuration...
Current configuration : 116 bytes
!
interface Serial0/0
ip address 10.1.200.1 255.255.255.0
encapsulation ppp
no fair-queue
clock rate 64000
end
r1#ping 10.1.200.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.200.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms
r1#
Building configuration...
Current configuration : 116 bytes
!
interface Serial0/0
ip address 10.1.200.1 255.255.255.0
encapsulation ppp
no fair-queue
clock rate 64000
end
r1#ping 10.1.200.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.200.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms
r1#
r1#sh int s0/0
Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Internet address is 10.1.200.1/24
MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,
the interface is clocked at 64000 k... this is vital... the bw is yet t1 speed... do not confuse these two...
the clock rate does not set the bw, THEY ARE EXCLUSIVE... on serial interfaces these should match because:
1/ Routing protocols – to calculate the cost of a path
2/ QOS (Quality of Service) – to identify how much bandwidth is availble to prioritize, If no bandwidth command has been configured on the interface, Routing protocols and QOS will assume the line is running at the maximum speed supported by the interface which can result in incorrect routing and incorrect prioritization of packets.
match them with the bandwidth command on both sides:
r1(config)#int s0/0
r1(config-if)#bandw 64
r1(config-if)#end
r1(config-if)#bandw 64
r1(config-if)#end
r2#sh int s0/0
Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Internet address is 10.1.200.2/24
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
Serial0/0 is up, line protocol is up
Hardware is PowerQUICC Serial
Internet address is 10.1.200.2/24
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
create loopbacks on r3 according to the diagram, and set the network statements to reflect the proper wildcard masks... and turn off auto-summary please...
r3#config t
Enter configuration commands, one per line. End with CNTL/Z.
r3(config)#int lo11
r3(config-if)#ip add 192.168.100.1 255.255.255.252
r3(config-if)#int lo15
r3(config-if)#ip add 192.168.100.5 255.255.255.252
Enter configuration commands, one per line. End with CNTL/Z.
r3(config)#int lo11
r3(config-if)#ip add 192.168.100.1 255.255.255.252
r3(config-if)#int lo15
r3(config-if)#ip add 192.168.100.5 255.255.255.252
r3(config)#router eigrp 1
r3(config-router)#netw 192.168.100.0 0.0.0.3
r3(config-router)#netw 192.168.100.4 0.0.0.3
r3(config-router)#no auto-summ
r3(config-router)#netw 192.168.100.0 0.0.0.3
r3(config-router)#netw 192.168.100.4 0.0.0.3
r3(config-router)#no auto-summ
r1#sh ip route eigrp
10.0.0.0/8 is variably subnetted, 6 subnets, 2 masks
D 10.1.3.0/24 [90/156160] via 10.1.100.3, 00:38:36, FastEthernet0/0
D 10.1.2.0/24 [90/156160] via 10.1.100.2, 00:38:36, FastEthernet0/0
192.168.100.0/30 is subnetted, 2 subnets
D 192.168.100.4 [90/156160] via 10.1.100.3, 00:03:44, FastEthernet0/0
D 192.168.100.0 [90/156160] via 10.1.100.3, 00:03:44, FastEthernet0/0
r1#
Routing Protocol is "eigrp 1"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 1
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is not in effect
Maximum path: 4
Routing for Networks:
10.0.0.0
192.168.100.0/30
192.168.100.4/30
Routing Information Sources:
Gateway Distance Last Update
(this router) 90 00:18:19
10.1.100.2 90 00:05:16
10.1.100.1 90 00:05:16
Distance: internal 90 external 170
No comments:
Post a Comment