Scenario in brief:

Customer ISP router is connected to both of the IIGs i.e. MANGO and BTCL. Router’s LAN side (i.e. eth0/0) is connected to its entire client through LAN switch. At WAN side it is connected to MANGO as well as BTCL network.
For MANGO clients following packages are offered:

1. SMCIPBW
2. SATIPBW
3. SECIPBW

To introduce client’s flexibility for different packages, the following templates are provided to implement at clients end. The flexibility includes different traffics (VSAT-bound or SEMEWE-4 bound) at single fiber, dynamic route control for SECIPBW clients, etc.

Customer ISP connected to both MANGO and BTCL IIGs.

SMCIPBW (only SEAMEWE BW) client configuration:

No extra configuration is required for submarine bandwidth service on the client side. Client would maintain its list of IP block to be routed to either BTCL or MANGO.

SATIPBW (only VSAT BW) client configuration:

This is the recommended configuration for ISPs getting VSAT only service from Mango. This should be put on the client router connected to Mango.

access-list 101 permit ip <MANGO-VSAT bound client-address> <wildcard bits> any	
                                                      ; defining clients via VSAT	
class-map VSAT                                        ; creating class-map to group VSAT clients
  match access-group 101                              ; matching clients for class VSAT

policy-map VSAT-BW                                    ; defining policy-map via VSAT
  class VSAT                                          ; setting client for VSAT-BW policy
    set ip dscp af11                                  ; marking traffic for VSAT route

interface eth0/0                                      ; interface of ISP LAN 
  service-policy input VSAT-BW                        ; applying service-policy for traffic matching VSAT-BW 

route-map COMMUNITY permit 10                         ; creating route-map 
  match ip address 101                                ; matching access-group for route-map
    set community 17806:100                           ; setting community parameter for sending to upstream
		
route-map COMMUNITY permit 20                         ; allowing other traffics 
	
router bgp <client as>                                ; enabling BGP process 	
  neighbor 114.130.X.X remote-as 17806                ; BGP peering with MANGO
  neighbor 114.130.X.X route-map COMMUNITY out        ; applying route-map for VSAT community triggering for 
  neighbor 114.130.X.X send-community                 ; enabling community triggering

SECIPBW client configuration:

The clients connected to MANGO for SECIPBW package will get 90% SMCIPBW plus 10% SATIPBW for downlink and 90% SMCIPBW plus 2.5% SATIPBW for uplink. Client traffic that is to be sent via MANGO VSAT has to reach with a DSCP bit set as af11 at the packets. This client would also have the facility to route their premium clients through their VSAT bandwidth by marking IP packets with DSCP value af12. If packets marked af12 reaches MANGO while SEAMEWE link is up, it would be routed via submarine. In case of submarine down, these traffics would be routed via VSAT but their aggregate bandwidth policing for VSAT bandwidth wouldn’t be changed. The following is a configuration template to implement at client router along with their other configuration parameters.

access-list 111 permit ip <MANGO-VSAT bound client-address> <wildcard bits> any	
                                                      ; defining clients via VSAT	
access-list 112 permit ip <PREMIUM client-address block> <wildcard bits> any	
                                                      ; defining premium clients via VSAT 
                                                        during SEAMEWE down	
class-map VSAT                                        ; creating class-map for VSAT group
  match access-group 111                              ; matching clients for class VSAT
	
class-map SEC                                         ; creating class-map to group premium clients
  match access-group 112                              ; matching clients for premium class
	
policy-map SECIP                                      ; defining policy-map for VSAT traffic
  class VSAT                                          ; setting client for VSAT-BW policy
    set ip dscp af11                                  ; marking traffic for VSAT route
  class SEC                                           ; setting client for premium policy
    set ip dscp af12                                  ; marking traffic for premium clients 
	
interface eth0/0                                      ; interface of ISP LAN 
  service-policy input SECIP                          ; applying service-policy for traffic
                                                        matching VSAT-BW 

route-map COMMUNITY permit 10                         ; creating route-map for VSAT-only traffic 
  match ip address 111                                ; matching access-group for route-map
    set community 17806:100                           ; setting community parameter for constant MANGO VSAT
route-map COMMUNITY permit 20                         ; creating route-map for premium traffic
  match ip address 112                                ; matching access-group for premium route-map
    set community 17806:101                           ; setting community parameter for sending 
                                                         premium traffic to MANGO
route-map COMMUNITY permit 30                         ; allowing SEAMEWE-4 traffic
		
router bgp <client as>                                ; enabling BGP process 	
  neighbor 114.130.X.X remote-as 17806                ; BGP peering with MANGO
  neighbor 114.130.X.X route-map COMMUNITY out        ; applying route-map for VSAT community triggering for 
  neighbor 114.130.X.X send-community                 ; enabling community triggering