06-30-2004 05:59 AM - edited 03-02-2019 04:44 PM
I have a wide area network comprising of 2 cisco
2600 series routersconneceted by their ethernet
port and 12 cisco 1601 and cisco 1721 routers
stationed at my remote sitesthings have been working
ok for about three years nor.But when I started
conecting the my 13th, 14th and 15th sites I started
experincing complete network diruption both on the Main
LAn and the wide area network. It seems from the look
of things that my main billing server, which is an
IBM setfity server running windows NT 4.0, is getting
problem handling the network traffic since when i remove
the machine from the network the network get up again.
So I dont know know where to start troubleshooting.Is there
any free software which I can use to monitor traffic, traffic
type or any other tool which I can use to isolate this problem
further so thatb i can find a solutioin to my problem?
Below are the configuration files of my two Cisco 2600
series routers:
==
Cisco_2611_IT#sh conf
Using 3118 out of 29688 bytes
!
ve
service config
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname Cisco_2611_IT
!
enable secret
enable password
!
ip subnet-zero
ip host salima 192.168.112.99
ip host Limbe 192.168.10.26
ip host BlantyrePayPoint 192.168.10.1
ip host MaselemaPayPoint 192.168.10.5
ip host LimbePayPoint 192.168.10.25
ip host Blantyre 192.168.10.2
ip host Zomba 192.168.10.22
ip host Mzuzu 192.168.30.30
ip host mangochi 192.168.30.22
ip host LilongweOldTown 192.168.10.14
ip host LilongweCityCentre 192.168.10.18
ip host Maselema 192.168.10.6
!
!
!
interface Ethernet0/0
ip address 192.168.100.207 255.255.255.0
no ip directed-broadcast
ip nat inside
!
interface Serial0/0
description Connecting MTL Head Office(Maselema)
bandwidth 64
ip address 192.168.30.6 255.255.255.252
ip directed-broadcast
ip nat inside
no ip mroute-cache
!
interface Ethernet0/1
ip address 192.168.240.1 255.255.255.0
no ip directed-broadcast
ip nat inside
bridge-group 1
!
interface Serial0/1
description Connecting Salima Customer Care Centre
ip address 192.168.30.9 255.255.255.252
no ip directed-broadcast
ip nat inside
no cdp enable
!
interface Serial1/0
description Connecting Ntcheu CCC
ip address 192.168.40.6 255.255.255.0
no ip directed-broadcast
ip nat inside
no cdp enable
!
interface Serial1/1
description Connecting Kasungu CCC
ip address 192.168.10.16 255.255.255.0
no ip directed-broadcast
ip nat inside
no cdp enable
!
interface Serial1/2
description Connecting Leland Internet Gateway
ip address 10.10.10.2 255.255.255.0
no ip directed-broadcast
ip nat outside
no cdp enable
!
interface Serial1/3
description Connecting Ngabu CCC
ip address 192.168.40.11 255.255.255.0
no ip directed-broadcast
ip nat inside
no cdp enable
!
router rip
version 2
no validate-update-source
redistribute connected
network 10.0.0.0
network 62.0.0.0
network 128.1.0.0
network 192.168.10.0
network 192.168.30.0
network 192.168.40.0
network 192.168.100.0
network 192.168.113.0
network 192.168.116.0
network 192.168.117.0
network 192.168.240.0
neighbor 10.10.10.1
!
ip nat pool Internet_Access netmask 255.255.255.248
ip nat inside source list 101 pool Internet_Access overload
ip nat inside source static 128.1.0.1
ip nat inside source static 192.168.100.8
ip nat inside source static 192.168.100.254
ip nat inside source static 192.168.100.10
ip classless
ip route 0.0.0.0 0.0.0.0 10.10.10.1
!
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
snmp-server community public RO
bridge 1 protocol dec
banner motd ^C
!
line con 0
exec-timeout 0 0
logging synchronous
transport input none
line aux 0
line vty 0 4
password xxxxx
login
!
end
Cisco_2611_IT#
===========
Thanks in advance
06-30-2004 06:37 AM
Hello,
are you saying that when you disconnect the NT server, your network is ok even with the additional sites connected ? You might want to try and turn on ip accounting first on the interface where the NT server is connected to, in order to find out which source address is sending the traffic to your NT serverm, or where your NT server is sending the traffic. To configure this on e.g. your Ethernet0/0 interface, add the following to the interface configuration:
ip accounting
ip accounting output-packets
You can then view the source and destination address pairs with the command:
show ip accounting
There is a free tool called MRTG which allows you to monitor interface load, go to www.mrtg.org for further information. You could also use a sniffer to verify the source of your problems, there is a free one available at www.ethereal.com.
HTH,
GP
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide