Lots of views....but no responses...   I think views are related with interest.... many guys looking for answers.   I remember that some time ago posting here was even better than opening a TAC case: quick and precise!     Actually there are lots of question without any answer... this is not good.     ... View more

PI supports 4 types of system defined port groups. Ports of new devices are automatically assigned to the respective groups. Trunk Ports—Ports connected to a Cisco device or other network devices (including Third party devices), operating on “Trunk” mode (all VLANs. Link Ports—Ports that are connected to another Cisco device or other network devices and are operating on “VLAN” mode (assigned to a VLAN) Access Ports—Ports that are connected to an end host, IP phone, servers, Access Points (AP) or video end points and operating on “Access” mode in which they carry traffic for only one particular VLAN. Unconnected Ports—Ports not connected to any device, Operational  and/or Administrative status is down. There is no definition about WAN ports. If you click on (i) in  Inventory > Port Management > Port Groups > System Defined > WAN Interfaces  you obtain 0 members. You can use that system defined group (WAN interfaces) or create a new Group. The only advantange of choosing WAN Interfaces group is that it is included in Automonitoring Policies. If you create a new one, then you must create a new Interface Health policy and select your newly created group. Yet in Inventory > Port Management > Port Groups Now you can select the interfaces you want to include (from Port Types or System Defined) For example I selected all my tunnel interfaces. (SEE ADD IF TO WAN Port Group.jpg) As long as WAN Interfaces is included in Automonitoring Policies, you are done with this.   Then you add a dashlet in any of the dashboards or in a new dashboard, for example Interface Utilization. (SEE ADD DASHLET.jpg)   Finally you customize the dashlet by selecting the WAN Interface por group (SEE CUSTOMIZE DASHLET.jpg)   And that is it! (SEE MY NEW WAN DASHLET.jpg)               ... View more

Thanks a lot!!!! ... View more

Just in case: Full URI from Cisco router is different because it replaces the domain with the actual IP. And FreeDns doesn´t like, it says: HTTP/1.1 404 Not Found  (text/html) The only way I found:  ip sla 1  http get http://freedns.afraid.org/dynamic/update.php?dk1UGUVURXXXXXXXXXXXXVVaNTc6MTYwOTY3MTE= frequency 7200 ip sla schedule 1 life forever start-time now Thank you. ... View more

... Thanks a lot and I´ll appreciate further references. Cheers Julio ... View more

Hi Jeet: I already posted the diagram. Any input? I´ll appreciate it This forum doesn´t seem to be a meteoric, up and doing forum ... Sorry. ... View more

Thank you for your answer. If you are so kind I´ll need some futher reference to some links explaining the alternatives: for instance, I cannot figure how two different IP addresses could help. May be I guess somewhat about running IPSec over TCP, and I am looking if we could make the Site C organization is able to configure this way for us. Thanks a lot and I´ll appreciate further references. Cheers Julio ... View more