PBR/QoS implementation

-- PBR use ending --

Hans-Werner Braun, 11 May 2011

I removed the PBR implementation (a) since I am not sure it causes more good than problemes (especially during outages), (b) it was not kept up to date after the Quest17 camera left, and (c) in anticipation of revised requirements in the upcoming HPWREN recharge environment.

New router configuration details:

  MPO:
  no ip access-list extended F-MPO-al
  no route-map F-MPO-rm permit 10
  interface Vlan800
   no ip policy route-map F-MPO-rm
  
  NP:
  no ip access-list extended F-MPO-al
  no route-map F-MPO-rm permit 10
  interface fa0/7
   no ip policy route-map F-MPO-rm
  
  no ip access-list extended T-MPO-al
  no route-map T-MPO-rm permit 10
  interface fa0/2
   no ip policy route-map T-MPO-rm
  
  MW:
  no ip access-list extended F-MPO-al
  no route-map F-MPO-rm permit 10
  interface fa0/8
   no ip policy route-map F-MPO-rm
  
  no ip access-list extended T-MPO-al
  no route-map T-MPO-rm permit 10
  interface fa0/7
   no ip policy route-map T-MPO-rm
  
  UCSD:
  no ip access-list extended T-MPO-al
  no route-map T-MPO-rm permit 10
  interface g0/2
   no ip policy route-map T-MPO-rm
  interface vlan800
   no ip policy route-map T-MPO-rm

After disabling bandwidth limits on the OC3 radios, I also changed the bandwidth statements for the OC3 radio port #1 Cisco configurations to 100000, and verified that both ports are now used in parallel. ML#8,NP#8,NP#2,MW#8,MW#7,UCSD#1,MPO#1,NP#7