In order to use AST, you need AST_master (the AST server), and minions for node and link resources.
Currently, we have the minions for node and link in the DRAGON GMPLS environment developed.
The software package ASTSoftware_Apr2008.tar.gz
contains both AST_master and node_agent. In order for AST_master and node_agent to compile, you also need to download libxml2
(a distribution from http://www.xmlsoft.org/
To download the link minions to work in DRAGON environment, please download the latest code from DRAGON Software Page
. Currently, the link minion to provision in DRAGON GMPLS environment is deployed as a component in dragond.
How to use AST
Please note: AST is working in network that's running DRAGON.
Assuming that you're not using any special types of resources in your setup, the following should be sufficient to run AST for you.
Setting up AST_master
- Set up DRAGON at your machines; refer to DRAGON project page
- design the control plan, including TE addressing schema, GRE tunnels naming
- configure OSPFD, RSVPD, dragond etc.
- Configure ast_master
- Edit configuration at /usr/local/dragon/etc/ast_master.conf with the following lines:
- "hostname xxx" - set the text of the prompt in AST CLI
- "password xxx" - set the password to log into CLI
- "set es x.x.x.x y.y.y.y tunnel_t" - set the end system information for ast_master to set up the topology
- x.x.x.x is the IP address that ast_master can use to reach the end system
- y.y.y.y is the TE address of the 1st hop VLSR that the end system is connected to
- tunnel_t is the tunnel that connect the end system and its first hop VLSR
- Start ast_master by command "/usr/local/dragon/bin/ast_master -d"
- The AST CLI port is 2612.
- If you want ast_master to setup the IP address on the end system for you after the topology is set up, you will also need to set up mySQL on the machine that ast_master is running.
- setup "username: dragon" and "password: flame" for the SQL.
- mysql -hlocalhost -udragon -pflame -e "use dragon; select * from data_plane_blocks where in_use='no' limit 1 - is the command that ast_master will run to get a pair of /32 address.
- The expected result from this mysql command is something like the following, and ast_master will parse the result accordingly.
| slash_30 | in_use |
| 184.108.40.206 | no |
Setting up minions (node_agent and dragon) at end system
- the dragond will be automatically set up when you brings up the end system by the command "/usr/local/dragon/bin/dragon.sh start-es"
- Edit the configuration file for node_agent at /usr/local/dragon/etc/node_agent.conf
- Configure node_agent
- "set interface xxx" - xxx is the interface that the end system is connected to the 1st hop VLSR
- Start node_agent by the command "/usr/local/dragon/bin/node_agent -d"
- Now, you can edit an xml file to describe the topology that you want AST to set up.
- Sample file that setup an LSP between a and b.
<resource res_type="node" subtype="dragon_node_pc" name="a">
<resource res_type="node" subtype="dragon_node_pc" name="b">
<resource res_type="link" subtype="dragon_link" name="max-lab4">
<src> <node>a</node> </src>
<dest> <node>b</node> </dest>
<te_params profile="EtherBasic"> </te_params>
- Submit the file to ast_master by "/usr/local/dragon/bin/ast_master -f "; and ast_master will return a file to you in the format of
<topology ast_id="ID" action="setup_resp">
You can continue to track the status of the topology in AST CLI.
- Release the topology by running "/usr/local/dragon/bin/ast_master -r ", or if you want to remove all AST that the ast_master is procesing, you can run "/usr/local/dragon/bin/ast_master -r all".