Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Point-to-Point Configuration

Status
Not open for further replies.

Poloboy

Technical User
Aug 26, 2002
58
US
I had bought Cisco 2600, 2 Cisco 1721, and 4 T1 modules. I had 2 branches that I like have point-to-point connected back to Main office. Can some one advise me steps I need to configure these routers to talk. I have T1 point-to-point in already. I don't need steps by steps instruction, I just need the basic of what I need to configure to make these routers talk. Can someone help me with the first step. I'm new to Cisco. Thanks

Jimmy
 
First see if you can ping the remotes after connecting the devices. If you are able to ping, you need to configure either dynamic routing (less config lines) or static routing (more lines). This is the very basic, if you need more help feel free to ask :)
 
Are IP addresses already configured on each end?
Did you already plan an addressing scheme between the 2 branches?

 
Yes, I have plan out IP Addreses for the 2 branches. What I like to do is set both Cisco 1721 as DHCP Server for the branches. The main office is running DHCP from win2k server. Can you lead me how to set up those routers? For example: what protocal I should use, what type of encapsulation, do I need ACL. Please advice me with head start.
 
Rather than use the 1721 as the DHCP server, you should consider using a helper address on the 1721 and use the Windows 2000 server for all sites - makes management of DHCP MUCH easier! Configue a helper address on the remote offices like this:

int fa0/0
ip helper-address x.x.x.x

Where x.x.x.x is your DHCP server. This will convert ip broadcasts (DHCP requests) into unicast packets and send them to your DHCP server on x.x.x.x

You should not need any network protocol other than IP. EIGRP is my preferred routing protocol as it is easy to configure and converges pretty quick. As you are talking about an entirely private network (and your routers don't have a direct internet conn) you don't have to use acls if you don't want to.

If this all seems too hard, you could start with Cisco ConfigMaker (free download from Cisco). This will give you a basic config that you can then edit as you like.

HTH,
Michael.
 
I been playing with these routers for almost a week but I can't seem to make it to work the way I wanted it. Below are my configurations. Can someone please go over it and let me know what else I needed to do to make it talks to one another. The 2 branches will access internet through corporate.

Cisco 2611 configuration:
!
service timestamps debug uptime
service timestamps log uptime
service password-encryption
no service tcp-small-servers
no service udp-small-servers
!
hostname Main
!
enable password xxxx
!
no ip name-server
!
ip subnet-zero
no ip domain-lookup
ip routing
!
interface Ethernet 0/0
no shutdown
description connected to CorporateNetwork
ip address 192.168.1.6 255.255.255.0
keepalive 10
!
interface Ethernet 0/1
no description
no ip address
shutdown
!
interface Serial 0/0
no shutdown
description connected to W.Fulton
service-module t1 clock source line
service-module t1 data-coding normal
service-module t1 remote-loopback full
service-module t1 framing esf
service-module t1 linecode b8zs
service-module t1 lbo none
service-module t1 remote-alarm-enable
ip address 192.168.2.1 255.255.255.0
encapsulation hdlc
!
interface Serial 0/1
no shutdown
description connected to S.Field
service-module t1 clock source line
service-module t1 data-coding normal
service-module t1 remote-loopback full
service-module t1 framing esf
service-module t1 linecode b8zs
service-module t1 lbo none
service-module t1 remote-alarm-enable
ip address 192.168.3.1 255.255.255.0
encapsulation hdlc
!
router eigrp 100
network 192.168.1.0
network 192.168.2.0
network 192.168.3.0
passive-interface Ethernet 0/0
no auto-summary
!
!
ip classless
!
! IP Static Routes
ip route 0.0.0.0 0.0.0.0 Ethernet 0/0
no ip http server
snmp-server community public RO
no snmp-server location
no snmp-server contact
!
line console 0
exec-timeout 0 0
password xxxx
login
!
line vty 0 4
password xxxx
login
!
end

Cisco 1721 Site 1 Config:
!
service timestamps debug uptime
service timestamps log uptime
service password-encryption
no service tcp-small-servers
no service udp-small-servers
!
hostname Site1
!
enable password xxxxx
!
no ip name-server
!
ip subnet-zero
no ip domain-lookup
ip routing
!
interface FastEthernet 0
no shutdown
description connected to EthernetLAN
ip helper-address xxx.xxx.x.xx
keepalive 10
!
interface Serial 0
no shutdown
description connected to E.Paris
service-module t1 clock source line
service-module t1 data-coding normal
service-module t1 remote-loopback full
service-module t1 framing esf
service-module t1 linecode b8zs
service-module t1 lbo none
service-module t1 remote-alarm-enable
ip address 192.168.2.2 255.255.255.0
encapsulation hdlc
!
router eigrp 100
network 192.168.2.0
no auto-summary
!
!
ip classless
no ip http server
snmp-server community public RO
no snmp-server location
no snmp-server contact
ip forward-protocol udp 135
!
line console 0
exec-timeout 0 0
password xxxx
login
!
line vty 0 4
password xxxx
login
!
end

Cisco 1721 Site 2 config:
!
service timestamps debug uptime
service timestamps log uptime
service password-encryption
no service tcp-small-servers
no service udp-small-servers
!
hostname Site2
!
enable password xxxxx
!
no ip name-server
!
ip subnet-zero
no ip domain-lookup
ip routing
!
interface FastEthernet 0
no shutdown
description connected to EthernetLAN_1
ip helper-address xxx.xxx.x.xx
keepalive 10
!
interface Serial 0
no shutdown
description connected to E.Paris
service-module t1 clock source line
service-module t1 data-coding normal
service-module t1 remote-loopback full
service-module t1 framing esf
service-module t1 linecode b8zs
service-module t1 lbo none
service-module t1 remote-alarm-enable
ip address 192.168.3.2 255.255.255.0
encapsulation hdlc
!
router eigrp 100
network 192.168.3.0
no auto-summary
!
!
ip classless
no ip http server
snmp-server community public RO
no snmp-server location
no snmp-server contact
ip forward-protocol udp 135
!
line console 0
exec-timeout 0 0
password xxxx
login
!
line vty 0 4
password xxxx
login
!
end

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top