Blacklist Table Maintenance

As new blacklist tables are released the customer can upload to /code/lrt and execute the following commands:

ACMEPACKET# config t
ACMEPACKET(configure)# session-router
ACMEPACKET(session-router)# local-routing-config
ACMEPACKET(local-routing-config)# select
<name>:
1: name=blacklist file name=blacklist.xml.gz prefixLength=15

selection: 1

Use the “show” command to verify the local-routing-config entry’s configuration

ACMEPACKET(local-routing-config)# show
local-routing-config
        name                           blacklist
        file-name                      blacklist.xml.gz
        prefix-length                  15
        string-lookup                  disabled
	  match-mode			   best

Change the “file-name” parameter to reflect the original compressed XML file

ACMEPACKET(local-routing-config)# file-name lookup.xml.gz
ACMEPACKET(local-routing-config)# done
local-routing-config
        name                           blacklist
        file-name                      blacklist102612.xml.gz
        prefix-length                  15
        string-lookup                  disabled
	  match-mode			   best

Exit out of configuration mode, save, and activate the configuration.

ACMEPACKET(local-routing-config)# exit
ACMEPACKET(session-router)# exit
ACMEPACKET(configure)# exit
ACMEPACKET#save-config
ACMEPACKET#activate-config
Activate-Config received, processing.
waiting for request to finish
Request to 'ACTIVATE-CONFIG' has Finished,
Activate Complete

After applying a new LRT, verify if by doing the same command from above “show lrt route-entry blacklist 3712900” at the ACLI (again, any of the hotlist numbers can be used). If something went wrong, change your config back to the old file and re-test.

After you have a few LRT files on the SBC you may want to clean the old ones up.