SPP Command Interface

System Resource Manager (SRM) and Resource Manager Proxy (RMP)

Major Control Software Modules

The page SPP Control Software describes the System Resource Manager (SRM) that runs on the SPP's Control Processor and the Resource Manager Proxy (RMP) that runs on each SPP's GPE, and it describes the programming API provided by the RMP. This page describes the accompanying command line interface which allows users to reserve and configure resources interactively or through a shell script. In brief, the SRM coordinates the use of various SPP resources while the RMP provides an interface through which user slices can request and configure resources. The RMP, in turn, may communicate with the Substrate Control Daemons (SCD) in the Line Card and the NPE to configure packet pathways.

User requests are made through an interface provided by the RMP on the user’s assigned GPE. The RMP forwards these requests to the SRM which manages all system level resources, including external port numbers, physical interface bandwidth and NPE resources. For example, a user can request the use of a specific external port number in order to run a server that listens on that port at the user's GPE. Or a user may want to reserve resources in advance (e.g., port bandwidth and NPE fastpath).

That command line interface is currently provided through three programs: scfg (slice configuration), ip_fpc (IPv4 filter configuration) and ip_fpd (IPv4 fastpath daemon). (Note: These names are likely to change in the near future. The scfg program applies to any fastpath while ip_fpc and ip_fpd are specific to the IPv4 code option.

Program	Functionality
scfg	Interface information, endpoint management, fastpath management, queue management, reservation management
ip_fpc	IPv4 filter management
ip_fpd	IPv4 fastpath configuration, LD and EX traffic handling

There will be other fastpath-specific programs as other code options get developed. It is worth noting that all of these programs implement their functionallity by calling RMP library functions. The fact that these programs exist as separate programs is historic. For example, one could have a single ipv4_control program that included all of the functionality of these programs. Furthermore, a new code option such as vnet would have a vnet_control program that included the functionality in the scfg program above and vnet-specific functionality for filters and handling LD and EX traffic. (Note: The programs ip_fpc and ip_fpd were called fltr and create_fp respectively in The GEC4 Demo.)

Command Interface Syntax

The scfg command uses GNU-style long options (e.g., --cmd get_endpoint, --ipaddr 10.1.2.3). And although they both have a few arguments that control their configuration (e.g., message log noise volume), this page only describes the user commands. In the descriptions below, the following metasymbols are used in the syntactic descriptions:

A	IP address (e.g., 192.168.2.32)		K	The number of Kilobits per second
D	Date in YYYMMDDHHMMSS format
F	Filter identifier		N	Number (non-negative)
FN	Filename		P	Protocol number (e.g., 6 (TCP), 17 (UDP))
I	An identifier or index		Q	Queue identifier
[x]	Optional argument x		S	Statistics index
{ x xxx y }	Alternative arguments x and y		X	Hexadecimal mask or 0

When a command description needs to use multiple instances of a metasymbol, distinction between instances is indicated by following the metasymbol insances by one or more distinguishing symbols (e.g., quote, integer, lowercase letters) (e.g., N and N' or N1, N2 and N3).

Command Interface

That command line interface is provided through three programs: scfg (slice configuration), ip_fpc (IPv4 fastpath filter configuration) and ip_fpd (IPv4 fastpath daemon). The scfg program applies to any fastpath while ip_fpc and ip_fpd are specific to the IPv4 code option. The primary function of the IPv4 daemon ip_fpd is to intialize the IPv4 code option and handle local delivery and error packets for that code option. The program ip_fpc manages filters for the IPv4 code option. All other functions that are generic to any fastpath (e.g., getting information about physical interfaces, allocating resources, making resource reservations, managing fastpath queues) are done by the scfg program.

Getting Interface Information

• scfg --cmd get_ifaces

Display all interfaces

• scfg --cmd get_ifpeer --ifn N

Display the peer of interface num N

• scfg --cmd get_ifattrs --ifn N

Display the attributes of interface num N

• scfg --cmd get_ifn --ipaddr A

Display the interface associated with IP address A

Reservation Management

• scfg --cmd get_resrvs

Display all slice reservations

• scfg --cmd get_resrv [--date D]

Display slice reservation for period covered by date D (default: current).
Date format is YYYYMMDDHHMMSS.

• scfg --cmd make_resrv --xfile FN

Make a reservation described by XML file FN

• scfg --cmd cancel_resrv [--date D]

Cancel slice reservation for period covered by date D (default: current).
Date format is YYYYMMDDHHMMSS.

• scfg --cmd update_resrv --xfile FN

Update slice reservation described by XML file FN

Setup/Free

• scfg --cmd claim_resources

Allocate slowpath (GPE) slice resources

• scfg --cmd free_sp_resources

Free slowpath (GPE) slice resources

• scfg --cmd free_fp_resources --fp I

Free fastpath slice resources for fastpath I

• scfg --cmd setup_sp_endpoint --bw K --ipaddr A --port N --proto P

Create the K Kbps capacity slowpath LC endpoint (A, N, P)

• scfg --cmd free_sp_endpoint --ipaddr A --port N --proto P

Remove the slowpath LC endpoint (A, N, P)

• scfg --cmd setup_fp_tunnel --fp I --bw K --ipaddr A --port N

Add (A, N) as a local end of a fastpath (UDP) tunnel with capacity K Kbps to fastpath I. Return the fastpath interface identifier in scfg's exit code which can be captured in the shell variable $?.

• scfg --cmd free_fp_tunnel --fp I --fpif I'

Free fastpath interface (I, I') where I is the fastpath identifier and I' is the fastpath interface identifier

Queue Management

• scfg --cmd get_queue_params --fp I --qid Q

Get the threshold and bandwidth for (fastpath I, queue Q)

• scfg --cmd get_queue_len --fp I --qid Q

Get the length (bytes) of (fastpath I, queue Q)

• scfg --cmd bind_queue --fp I --fpif I' --qid Q1,Q2,...

Bind queues Q1, Q2, ... to (fastpath I, fastpath interface I')

• scfg --cmd bind_queue --fp I --fpif I' --qid Q1-Q2

Bind queues in the range Q1 to Q2 inclusive to (fastpath I, fastpath interface I')

• scfg --cmd set_queue_params --fp I --qid Q --threshold B --bw K

Set the threshold and bandwidth of (fastpath I, queue Q) to B bytes and K Kbps

IPv4 Filter Management

Filter management for the IPv4 code option is done through the ip_fpc program. The command-line syntax uses GNU-style long options

xxxxx key, mask, peer

 ip_fpc --cmd write_fltr --fpid I --fid I'
   --key_type {0|1}   --key_rxmi M
   --key_saddr Asrc   --key_sport Nsrc   --key_daddr Adst   --key_dport Ndst
   --key_proto P
   --mask_saddr Asrc' --mask_sport Nsrc' --mask_daddr Adst' --mask_dport Ndst'
   --mask_flags P'XXX
   [--res_ld]
   --txdaddr Anxt  --txdport Nnxt
   --qid Q         --sindx S

Install a filter for fastpath I with filter identifier F.
match (key-mask), peer, qid, stats
key_type
F is from the range 0 to n-3 where n is the number of filter resources requested for the fastpath.

 ip_fpc --cmd update_result --fpid I --fid I' RESULT

Update the result part of filter (I, I') where I is the fastpath identifier and I' is the filter identifier.

 ip_fpc --cmd get_fltr_bykey --fpid I KEY

Display the entire filter (key, mask, result) from fastpath I matching KEY.

 ip_fpc --cmd get_fltr_byfid --fpid I --fid I'

Display the filter from fastpath I with filter identifier I'.

 ip_fpc --cmd lookup_fltr --fpid I KEY

Display the result part of the filter from fastpath I matching KEY.

 ip_fpc --cmd rem_fltr_bykey --fpid I KEY

 ip_fpc --cmd rem_fltr_byfid --fpid I --fid I'

Remove the filter (I, I') where I is the fastpath identifier and I' is the filter identifier.

IPv4 Fastpath Creation

 ip_fpd --fpName FN --myIP A --myPort N >> ip_fpd.log &

xxx

Examples

xxx