Question : Cisco 3845 - BGP and Static routing conflict

Hardware:
C3845-ADVENTERPRISEK9-M Cisco Router


Question:
I am trying to setup a static route to a server on our network to route traffic over a VPN tunnel.
We are using BGP as the routing protocol for the network.

Ex:
Routing entry for 192.168.72.0/24
  Known via "bgp 1", distance 20, metric 0
  Tag 1234, type external
  Last update from 192.168.1.1 02:36:46 ago
  Routing Descriptor Blocks:
  * 192.168.1.1, from 192.168.1.1, 02:36:46 ago
      Route metric is 0, traffic share count is 1
      AS Hops 2
      Route tag 1234

However when I try to set a static route to the server and remove the BGP route from the routing table, the BGP route is still showing up in the table.

ip route 192.168.72.15 255.255.255.255 2.2.180.150 10 name VPN

show ip route | include 192.168.72.0

B    192.168.72.0/24 [20/0] via 192.168.1.1, 02:44:56

Can anyone explain this?  I was under the assumption that the static route with a metric of 0 would override the BGP route.  However, it is kind of odd that the BGP route is showing up with a 0 metric also.

Answer : Cisco 3845 - BGP and Static routing conflict

Is 2.2.180.150 directly connected? The static route will not be valid if the next-hop address isn't actually a next hop (on a locally connected network). You can also use an interface name for a next hop i.e. ip route 192.168.72.15 255.255.255.255 Serial0/0 10 name VPN
.

By the way, the reason that BGP shows a metric of 0 is that BGP doesn't use metrics- it uses AS paths and other things to make its routing decisions.