A couple of other things to look for.
1) Where are you trying to ping the 10.1.1.6 IP from? I assume something on Gi0/1? 2) Make sure the devices plugged into Gi0/0 and Gi0/1 are either set up as trunk ports allowing VLAN100, or access ports in VLAN100. (since you're giving it a dot1q encapsulation on the subints) 3) Make sure that you have a route in the route table for 10.1.1.0/24 going towards this chassis. 4) Make sure you have a valid route back to the destination from this chassis. Ken Matlock Network Analyst Exempla Healthcare (303) 467-4671 [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, March 04, 2009 11:28 AM To: [email protected]; Leslie Meade Subject: Re: [c-nsp] (no subject) On Wed Mar 4 13:21 , "Leslie Meade" sent: >I am trying to bridge my 2821 to one ip to give me redundancy. >I am using this config to bridge the two ints and I see gig0/1 up and the bvi up but I am not able to ping it > >The original config gig0/1 had the ip of 10.1.1.6 and I could ping everything and get to everything >Ios C2800NM-IPVOICEK9-M > >Any ideas ? > > >bridge irb >! >interface gig0/0.100 >encapsulation dot1Q 100 >bridge-group 100 >! >interface gig0/1.100 >encapsulation dot1Q 100 >bridge-group 100 >! >interface BVI100 >ip address 10.1.1.6 255.255.255.0 >no shutdown >! >bridge 100 protocol ieee >bridge 100 route ip Do you have a default route configured? If you are pinging from a remote subnet you'll need a default route. -chris _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
