Running the Agent and Reference Application

The BroadViewAgent and the reference application (BroadViewBstApp or BroadViewPacketTraceApp) communicate over HTTP. Each of the application maintains respective configuration files. The default location of configuration file has to be in the same directory where the application is present. Follow the steps mentioned below, to start BroadViewAgent.

1.cd to directory where BroadViewAgent is located

2.Copy the agent_config.cfg created earlier

# scp <username>\<server_ip>:<file_path>/agent_config.cfg

3.Start BroadViewAgent

# ./BroadViewAgent &

Follow the steps, mentioned below, to start BroadViewBstApp.

1.cd to directory where BroadViewBstApp is located

2.Copy the bstapp_config.cfg created earlier

# scp <username><server_ip>:<file_path>/bstapp_config.cfg .

3.Start BroadViewBstApp

# ./BroadViewBstApp &

Switch can also be configured to use ExampleCfgApp. The arguments passed th BroadViewAgent would be the one shown below

# ./BroadViewAgent -c

The output is displayed below

root@56_07:/root/pt> ./BroadViewBstApp -d
BroadViewBstApp Version 3.0.2.2
BSTAPP : Configuring ...BSTAPP : Reading configuration from bstapp_config.cfg
BSTAPP : Configuration file bstapp_config.cfg not found:
BSTAPP : Setting configuration to defaults
BSTAPP : Using default configuration 127.0.0.1:8080 <–>local:9070, Max 10 Reports
BSTAPP : Configuration CompleteStarting communication with agent
1.Configure BST feature
2.Configure BST tracking
3.Configure BST threshold
4.Clear BST statistics
5.Clear BST threshold
6.Get BST feature
7.Get BST tracking
8.Get BST thresholds
9.Get BST report
10.Exit
Select an option from the menu:

Follow the steps, mentioned below, to start BroadViewPacketTraceApp.

1.cd to directory where BroadViewPacketTraceApp is located
2.Copy the ptapp_config.cfg created earlier

# scp <username><server_ip>:<file_path>/ptapp_config.cfg .

3.Start BroadViewPacketTraceApp

# ./BroadViewPacketTraceApp

The output is displayed below

# ./BroadViewPacketTraceApp BroadViewPacketTraceApp Version 3.0.2.2

1.Configure Packet Trace Feature
2.Get Packet Trace feature status
3.Trace a packet
4.Trace LAG resolution for a packet
5.Trace ECMP resolution for a packet
6.Cancel Packet Trace profile request
7.Cancel Packet Trace LAG resolution request
8.Cancel Packet Trace ECMP resolution request
9.Exit
Select an option from the menu:

Chip configuration can be done using ExampleCfgApp. The ExampleCfgApp is menu based which can be used to configure various L2/L3 features. The application can be used to configure Lag, add members to lag, create L3 interface, add ARP entries, etc. These configurations are required for ECMP or Lag resolution.

1.Configure L2 related parameters
2.Configure L3 related parameters
3.Configure system related parameters
4.Exit
Select an option from the menu:1

1.Create VLAN
2.Delete VLAN
3.Add member to VLAN
4.Delete member from VLAN
5.Configure LAG
6.Delete LAG
7.Add member to LAG
8.Delete member from LAG
15.Exit
Select an option from the menu:

Lag Configuration using ExampleCfgApp:

1.Configure Lag id
2.Add members to the lag

# ./ExampleCfgApp

1.Configure L2 related parameters
2.Configure L3 related parameters
3.Configure system related parameters
4.Exit
Select an option from the menu:2

1.Create L3 Interface
2.Delete L3 Interface
3.Add L3 route
4.Delete L3 route
5.Add ARP entry
6.Delete ARP entry
15.Exit
Select an option from the menu:

L3 Configuration required for ECMP resolution

1.Configure L3 interfaces
2.Add ARP entries for next hop
3.Add L3 route

Once the above mentioned configuration is done a packet will be switched/ routed accordingly.

Note: The default port numbers for the reference applications are same. So, port numbers must be changed to avoid any conflicts.