[c-nsp] bridgeing /dhcp problems

Wed Mar 8 16:50:33 EST 2006

I have been able to resolve this problem ...

It amounted to this. when I moved the FastEthernet to the bridge I had to 
move the ip to the BVI and when I did that there were 2 subnets on the 
interface that was attempting to handle the dhcp. this confused the 
interface on where to the broadcast packets where to go. so I removed the 
bridge form the fast Ethernet and removed the subnet from the BVI and the 
tricky part of it was to remove the bridge ip from the bridge group. this 
allowed me to transfer packet to and from the bridge. then it worked like a 
charm

Steven Lamb

----- Original Message ----- 
From: "Steven Lamb" <the_cisco_sheep at adiis.net>
To: "Cisco List" <cisco-nsp at puck.nether.net>
Sent: Wednesday, March 08, 2006 9:44 AM
Subject: [c-nsp] bridgeing /dhcp problems

>I am new to this forum and not very seasoned with Cisco equip. I am the
> Systems Admin of a small Iowa ISP we have recently had to had the 
> capability
> of OC3 to our network so that we can carry enough bandwidth. for this
> purpose we purchased a Cisco 7120 OC3  Router off of eBay. the equipment
> seems to work as best I can tell. It is currently running version 12.3 of
> the IOS. More info available in the Config that I have also posted.
>
> here is what I have going on currently on our network.
>
> we have one rack of servers connected to a hub as well as 2 Cisco routers
> ( a 2620 and the new7120) currently the 2620 will handle all of the 
> outbound
> traffic until we can switch people over to the new Router.
>
> here is the scenario I am having problems with. The teleco I work with has 
> I
> believe a teliant 5000 that they are handing off to me via fiber a point 
> to
> point vc which carries a single DSL customer. I take that vc on a sub
> interface of my OC3 interface which is in a bridge group. when the OC3 was
> the only interface in the bridge group I was unable to ping the rest of my
> router from the DSL modem, so I added the FE port to the bridge this 
> allows
> a statically assigned machine off of the modem to ping and get to the rest
> of the world. however the problem I am running into is when they try to
> DHCP. some times I get a quick response from my DHCP server and some times 
> I
> get a slow response 2+ min. also regardless of how long it takes for the
> DHCP to come back sometimes the modem will not know how to get out to the
> rest of the world. I don't really know what to check or change to resolve
> these two problems. what info other than the config would be useful to 
> see?
>
>
> oatbran#show running-config
> Building configuration...
>
> Current configuration : 2365 bytes
> !
> version 12.3
> no service pad
> service timestamps debug datetime msec
> service timestamps log datetime msec
> no service password-encryption
> !
> hostname oatbran
> !
> boot-start-marker
> boot-end-marker
> !
> enable secret 5
> enable password
> !
> username root password 0
> no aaa new-model
> ip subnet-zero
> !
> !
> ip domain name adiis.net
> ip name-server 207.177.36.1
> ip name-server 207.177.36.2
> !
> ip multicast-routing
> ip cef
> ip audit po max-events 100
> no ftp-server write-enable
> !
> !
> !
> !
> !
> !
> !
> !
> !
> !
> !
> !
> !
> !
> !
> bridge irb
> !
> !
> interface Loopback1
> no ip address
> !
> interface FastEthernet0/0
> no ip address
> no ip route-cache cef
> no ip route-cache
> duplex full
> speed auto
> bridge-group 1
> !
> interface FastEthernet0/1
> ip address 192.168.3.13 255.255.255.0
> no ip route-cache cef
> no ip route-cache
> duplex full
> speed 100
> !
> interface ATM1/0
> no ip address
> no ip route-cache cef
> no ip route-cache
> no ip mroute-cache
> no atm ilmi-keepalive
> !
> interface ATM1/0.4 point-to-point
> ip helper-address 207.177.36.5
> no ip route-cache
> bridge-group 1
> pvc 1/33
>  encapsulation aal5snap
> !
> !
> interface BVI1
> ip address 207.177.36.253 255.255.255.224 secondary
> ip address 69.63.9.254 255.255.255.0
> ip broadcast-address 69.63.9.255
> no ip unreachables
> !
> ip default-gateway 207.177.36.254
> ip classless
> ip default-network 207.177.36.0
> ip route 0.0.0.0 0.0.0.0 207.177.36.254
> ip route 172.16.128.0 255.255.240.0 10.100.16.62
> ip route 172.23.128.0 255.255.240.0 10.100.16.62
> ip route 206.72.1.0 255.255.255.0 FastEthernet0/0
> ip route 206.72.1.32 255.255.255.224 207.177.36.254
> ip route 206.72.1.64 255.255.255.224 207.177.36.254
> ip route 206.72.1.96 255.255.255.224 207.177.36.254
> ip route 206.72.1.128 255.255.255.224 207.177.36.254
> ip route 206.72.1.160 255.255.255.224 207.177.36.254
> ip route 206.72.1.192 255.255.255.224 206.72.1.7
> ip route 207.177.36.0 255.255.255.0 FastEthernet0/0
> no ip http server
> no ip http secure-server
> !
> !
> access-list 100 permit ip 69.63.9.0 0.0.0.255 69.63.9.0 0.0.0.255
> !
> snmp-server engineID local
> snmp-server community  RO
> snmp-server enable traps tty
> !
> bridge 1 protocol ieee
> bridge 1 route ip
> !
> !
> !
> line con 0
> line aux 0
> line vty 0 4
> exec-timeout 60 0
> password
> login local
> line vty 5
> exec-timeout 60 0
> login local
> !
> ntp clock-period 17180494
> ntp server 207.177.36.1 prefer
> !
> end
>
> oatbran#
>
>
>
>
>
>
> -- 
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 268.2.0/276 - Release Date: 3/7/2006
>
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
>
>
> -- 
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.375 / Virus Database: 268.2.0/276 - Release Date: 3/7/2006
>
> 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.2.0/276 - Release Date: 3/7/2006