For link local service request, do src port nat. Bind to a local port, and use it as nat src port.
Update test case
Merge remote branch 'upstream/master'
Update for code review
Merge remote branch 'upstream/master'

Conflicts:
	src/vnsw/agent/pkt/flow_table.h
	src/vnsw/agent/pkt/test/test_pkt_flow.cc
UT for Agent UVE introspect commands
Merge branch 'master' into ashoksr_ut
Fix for label mismatch in the path programmed by local peer and remote peer for l2 route
Fix for vnswad core: If multicast object is present in delete state and peer goes down then no rebake is to be done for comp NH
Fix for multicast crash: Rebake comp NH when peer goes down only if multicast object is not deleted
Update multicast.cc
Update multicast.cc
Merge pull request #342 from Juniper/ashoksr_ut

UT for Agent UVE introspect commands
Handle a couple of cases/exceptions when service have gone away
UT for db_handler.cc
Merge pull request #346 from Juniper/rajreddy_ut2

UT for db_handler.cc
Merge pull request #345 from Juniper/dsetia-bugfix

Handle a couple of cases/exceptions when service have gone away
Initial commit of code coverage for config systemless test
Merge pull request #347 from Juniper/anishm_config_cov

Initial commit of code coverage for config systemless test
Changes for flow message processing optimizations in collector:
1. Rewrite FlowTableInsert to traverse the flow message XML
  tree only once and extract the needed fields into an
  array. Use the array to populate the vectors needed to
  populate the FlowRecordTable and the flow index tables.
2. Use the DbDataValueType type to encode the value into
  string rather than using the column family name to determine
  the type. This avoid 2 map lookups per field encoded.
  Add a boost::blank as the first element of DbDataValueType
  variant instead of std::string to determine if the variant
  is populated or not.
3. Add a mock_generator in C++ which sends flow messages and
  can be used to scale test vizd.
4. Use pugixml to decode the SandeshHeader and the sandesh
  message in SandeshServer. Abstract out SandeshMessage
  creation and parsing using SandeshMessageBuilder, change
  vizd to use SandeshMessage.

With the above changes, we are able to increase vizd flow sandesh message
receive performance for 1 generator from around 1.5K msg/sec to
around 3.5K msg/sec using vizd built using compiler optimizations enabled -03
on single box setup - a6s23 - 4 core i3.