Getipconf Usage Notes

Syntax

getipconf [-r runcode] [-t topfile] [-b bwconvfile] [-n muxloc] [-p nodeparam]
[-noBGP] [-i interfaceDir] [-snmp SNMPDir] [-commentBW] [-ignore ipaddr] [-ospf
ospfdatabase] [-atmbw] [-cdp cdpfile1 cdpfile2 ... -conf] config1 config2 ...

BGP-related flags

BGP Files Generated

In addition to the standard files like the spec, muxloc, and bblink files, the following are five output files related to BGP that are generated by getipconf: aclist.x, controllist.x, bgpobj.x, bgpnode.x, bgplink.x, bgpnbr.x, and subnet.x (assuming the runcode is x). Below is a brief explanation of the contents of these files:

• aclist.x contains information about as-path, access-list, and community-list

• controllist.x contains information about access-lists and prefix-list. The controllistobj.x file is a binary file.

• bgpnode.x contains information for BGP speakers

• bgplink.x contains information for BGP neighbors

• bgpnbr.x is a text file that contains all information about neighbors.

• bgpobj.x contains information about BGP neighbors shown in bgpnbr.x and route map structure. The bgpobj file is a binary file designed to save space and to speed up performance of the software. It is partially replaced by bgplink.x and bgpnode.x. How the program decides whether to read the bgpobj file or the bgplink and bgpnode file is explained below.

• subnet.x is used to list those subnetworks originated by a particular router or AS node.

Corresponding Spec File Keywords

In the specification file, the keywords for the first four of these files will be listed as aclist, bgpobj, bgpnode, and bgplink. The bgpnbr file is for informational purposes only and is not included in the specification file.

For an example of the specification file entries related to BGP, see the following example:

# Files used by IP network

bgpobj= bgpobj.x
bgpnode= bgpnode.x
bgplink= bgplink.x
dparam= dparam.x
aclist= aclist.x
jpoBGP=jpoBGP.x
subnet= subnet.x
livebgprtblobj=livebgp.obj
controllistobj=controllistobj.x

Usage Note

Users need to comment out the specification of the bgpobj file in the specification file if they plan to edit BGP attributes manually. When loading the network, the rtserver (or bbdsgn) program reads the bgpobj file, if it is specified, ignoring the bgpnode and bgplink files. However, if the bgpobj file is not specified or it is commented out, rtserver will read the bgpnode and bgplink files instead. When saving the network, all three files: bgpobj, bgpnode and bgplink will be saved.

dparam File

The following are some of the BGP-related parameters in the dparam file that you may want to change. They can also be changed through the Tools > Options menu as described in BGP Options .

chkIBGPflag = 1 # 0: skip IBGP policy checking
IGPoverride= 0 # IGP over ride BGP
useliveBGPrtbl = 1
simskipAS= 1 # 1: skip AS nodes and link down simulation

• If IBGP policies are used in the network to influence routing, set the chkIBGPflag parameter to 1. By default, it is set to 0 to speed up routing.

• The simskipAS parameter is set to 1 by default, meaning that AS nodes and links will not be brought down in an exhaustive failure simulation performed from Simulation > Predefined Scenarios. If you wish to check the impact of an AS node or AS link failure on traffic routing, change the value to 0. Note, however, that if there are a lot of AS nodes, this may greatly increase the time it takes to perform the simulation. To indicate that only a subset of the AS nodes should be failed and the rest of the AS nodes should be ignored, mark the AS nodes or AS links to ignore with the FAIL=0 flag. This parameter can be set in the Modify > Elements > Nodes, Design properties tab (or add it to the end of the muxloc file entry) or Modify > Elements > Links, Properties tab (or add it to the miscellaneous field of the bblink file entry).

  content_copy zoom_out_map

  muxloc entry: SDG SANDIEGO 760 277 US 32.883434 -117.167480 FAIL=0
  bblink entry: LINK7 CHI DET DEF 1 OC3
  MPLSTE,OSPF=477,FAIL=0 AREA=AREA0

• The IGPoverride option is false (0) by default, meaning that for external paths, BGP will be treated as having a higher administrative distance/preference than the IGP such as OSPF. If this is not the case, this parameter can be set to true (1).

bgpnode format

#Node ASno ConfedID clusterID misc
N3    65522 0    0   RR

bgplink format

#lineID nodeA nodeZ Z_AS MED weight local_pref multi_hop RRclient
NBR1  N1  N2  65511  0  0  0  -1 0 

aclist format

# AS path and community lists
# column 1 - router_name separated by comma
# column 2 - AS number
# column 3 - access modifier 1-permit, 0-deny
# column 4 - type a-AS path, c-Community list
# column 5 - regular expression
router1, 65099 0 a ".*"

bgpnbr file

The bgpnbr file is for information purposes and is not read into the specification file. See the following table for a description of the fields in the bgpnbr file.

#Status,AS,Intf,Node,Z_AS,Z_intf,Z_Node,PeerGroup,RRclient,Cluster,Multihop,Loca
l Pref,Weight,Med, InPolicy,OutPolicy,VRF,Confederation_ID,MultiPath
up,65511,Loopback1,S36,65511,"allow_ixp",,"allow_ixp",0, ,-1,0,0,0," "," ",

ASs that are outside of the network and have EBGP peering relationship with BGP speakers of the network are represented by ASnodes in the muxloc file (the node file of NorthStar Planner).

Subnet File

A snippet of a sample subnet file is shown here. The address/mask field denotes the subnetwork originated by the node. The misc field is used to specify any BGP attributes associated with the subnetwork.

#Node address/mask protocol misc
RTA 10.100.1.0/24 bgp
AS65511 10.10.1.0/24 bgp as-path=65510 65500
AS65511 10.10.2.0/24 bgp as-path=65502 65500
AS65522 10.140.10.0/24 bgp community=65501:65520
AS65522 10.140.20.0/24 bgp community=65530:65515