Tracking routed vlan interface statistics and bandwidth shaping on Juniper switches - ex4500 series

I have just finished provisioning two different internet customers (one supposed to be 4 Mbps and the other 3 Mbps up/down) on a Juniper ex-4500-40f series switch.
The next step was to do bandwidth limiting on these customers but i have hit 2 very annoying snags with this model of juniper switch.

1. The bandwidth policer can ONLY work for ingress traffic (this would be up-link from the customer) which is usually a non issue for the ISP because Uplink is little traffic compared to down-link!
For egress traffic, am supposed to do "bandwidth-shaping" but yet again it's not supported for logical interfaces! WTF Juniper!

2. The ex-4500 does NOT support tracking RVI (Routed VLAN Interface) statistics! meaning there is no way i will be able to track the throughput for my internet customers. This is really annoying because even you SNMP tool won't be able to monitor such interfaces no matter how fancy it is!

Sorry if you landed on this page because of the same issue. 

Funny thing is RVI stats are supported on the lower versions ex3200 and ex4200! up to now i don't know why the F*** Juniper decided to do it like this. Ideally higher switch models should inherit all the good features from it's predecessors and even get better.

Here are two screen shots from my ex4200 and the annoying ex4500!:

On the 4200 you are able to the the ingress stats whereas on the 4500 there is 0.

I really don't know if there is any work around this "show stopper" on the ex4500! please comment if you have any break through on the 4500 regarding rvi statistics or rvi egress bandwidth limiting.

will appreciate.

Observium - Network Management and Monitoring - Another Great Free tool to Consider

Observium - Another great free network monitoring tool to consider if you are on a search for one. I already finished setting up cacti but will definitely try Observium for my next client. Can't wait to take it for a spin!

Observium - Network Management and Monitoring

Quick Check - Simple CISCO NAT Configuration

Refer to the network layout below:

Configuration: 

Note:- Replace the private IPs at the p2p with the public IPs supplied by your ISP.

           Replace the public dns 8.8.8.8 with your ISP DNS(s)

interface GigabitEthernet0/0

 description Connects-to-ISP-router

 ip address 192.168.201.2 255.255.255.252

 ip nat outside

 ip virtual-reassembly in

end

!

interface GigabitEthernet0/1

 description Connects-to-LAN

 ip address 192.168.1.1 255.255.255.0

 ip nat inside

 ip virtual-reassembly in

 duplex auto

 speed auto

end

interface Loopback1

 ip address 192.168.1.200 255.255.255.255

ip route 0.0.0.0 0.0.0.0 192.168.201.1

ip nat inside source list my-access-list interface GigabitEthernet0/0 overload

ip access-list extended my-access-list

 permit ip any any

ip dhcp pool my-office-dhcp

 network 192.168.1.0 255.255.255.0

 default-router 192.168.1.1 

 dns-server 8.8.8.8

 lease 7

If you have any questions! Please leave a comment.

Quick Check Juniper-Junos "Disable and Enable vlan interface"

This command does the same thing as Cisco's "shutdown" and "no shutdown" interface commands:

> edit 
Entering configuration mode

# set interfaces vlan.231 disable 
# commit 
# exit 
Exiting configuration mode

>
> show interfaces vlan.231 terse    
Interface               Admin Link Proto    Local                 Remote
vlan.231                down  up   inet     10.0.23.1/28    
# delete interfaces vlan.231 disable 
# commit 
# exit 
Exiting configuration mode

> 
> show interfaces vlan.231 terse    
Interface               Admin Link Proto    Local                 Remote
vlan.231                up    up   inet     10.0.23.1/28    
>
>