Quagga is an advanced routing software package that provides a suite of TCP/IP based routing protocols. This is the Manual for quagga-0.98.0. Quagga is a fork of GNU Zebra.
Quagga is a routing software package that provides TCP/IP based routing services with routing protocols support such as RIPv1, RIPv2, RIPng, OSPFv2, OSPFv3, BGP-4, and BGP-4+ (see Supported RFC). Quagga also supports special BGP Route Reflector and Route Server behavior. In addition to traditional IPv4 routing protocols, Quagga also supports IPv6 routing protocols. With SNMP daemon which supports SMUX protocol, Quagga provides routing protocol MIBs (see SNMP Support).
Quagga uses an advanced software architecture to provide you with a high quality, multi server routing engine. Quagga has an interactive user interface for each routing protocol and supports common client commands. Due to this design, you can add new protocol daemons to Quagga easily. You can use Quagga library as your program's client user interface.
Quagga is distributed under the gnu General Public License.
Today, TCP/IP networks are covering all of the world. The Internet has been deployed in many countries, companies, and to the home. When you connect to the Internet your packet will pass many routers which have TCP/IP routing functionality.
A system with Quagga installed acts as a dedicated router. With Quagga, your machine exchanges routing information with other routers using routing protocols. Quagga uses this information to update the kernel routing table so that the right data goes to the right place. You can dynamically change the configuration and you may view routing table information from the Quagga terminal interface.
Adding to routing protocol support, Quagga can setup interface's flags, interface's address, static routes and so on. If you have a small network, or a stub network, or xDSL connection, configuring the Quagga routing software is very easy. The only thing you have to do is to set up the interfaces and put a few commands about static routes and/or default routes. If the network is rather large, or if the network structure changes frequently, you will want to take advantage of Quagga's dynamic routing protocol support for protocols such as RIP, OSPF or BGP.
Traditionally, UNIX based router configuration is done by ifconfig and route commands. Status of routing table is displayed by netstat utility. Almost of these commands work only if the user has root privileges. Quagga has a different system administration method. There are two user modes in Quagga. One is normal mode, the other is enable mode. Normal mode user can only view system status, enable mode user can change system configuration. This UNIX account independent feature will be great help to the router administrator.
Currently, Quagga supports common unicast routing protocols. Multicast routing protocols such as BGMP, PIM-SM, PIM-DM may be supported in Quagga 2.0. MPLS support is going on. In the future, TCP/IP filtering control, QoS control, diffserv configuration will be added to Quagga. Quagga project's final goal is making a productive, quality, free TCP/IP routing software.
Traditional routing software is made as a one process program which provides all of the routing protocol functionalities. Quagga takes a different approach. It is made from a collection of several daemons that work together to build the routing table. There may be several protocol-specific routing daemons and zebra the kernel routing manager.
The ripd daemon handles the RIP protocol, while ospfd is a daemon which supports OSPF version 2. bgpd supports the BGP-4 protocol. For changing the kernel routing table and for redistribution of routes between different routing protocols, there is a kernel routing table manager zebra daemon. It is easy to add a new routing protocol daemons to the entire routing system without affecting any other software. You need to run only the protocol daemon associated with routing protocols in use. Thus, user may run a specific daemon and send routing reports to a central routing console.
There is no need for these daemons to be running on the same machine. You can even run several same protocol daemons on the same machine. This architecture creates new possibilities for the routing system.
+----+ +----+ +-----+ +-----+ |bgpd| |ripd| |ospfd| |zebra| +----+ +----+ +-----+ +-----+ | +---------------------------|--+ | v | | UNIX Kernel routing table | | | +------------------------------+ Quagga System Architecture
Multi-process architecture brings extensibility, modularity and maintainability. At the same time it also brings many configuration files and terminal interfaces. Each daemon has it's own configuration file and terminal interface. When you configure a static route, it must be done in zebra configuration file. When you configure BGP network it must be done in bgpd configuration file. This can be a very annoying thing. To resolve the problem, Quagga provides integrated user interface shell called vtysh. vtysh connects to each daemon with UNIX domain socket and then works as a proxy for user input.
Quagga was planned to use multi-threaded mechanism when it runs with a kernel that supports multi-threads. But at the moment, the thread library which comes with gnu/Linux or FreeBSD has some problems with running reliable services such as routing software, so we don't use threads at all. Instead we use the select(2) system call for multiplexing the events.
Currently Quagga supports gnu/Linux, BSD and Solaris. Porting Quagga to other platforms is not too difficult as platform dependent code should most be limited to the zebra daemon. Protocol daemons are mostly platform independent. Please let us know when you find out Quagga runs on a platform which is not listed below.
The list of officially supported platforms are listed below. Note that Quagga may run correctly on other platforms, and may run with partial functionality on further platforms.
Some IPv6 stacks are in development. Quagga supports following IPv6 stacks. For BSD, we recommend KAME IPv6 stack. Solaris IPv6 stack is not yet supported.
Below is the list of currently supported RFC's.
When SNMP support is enabled, below RFC is also supported.
Quagga is still beta software and there is no officially released version.
Zebra's official web page is located at:
http://www.gnu.org/software/zebra/zebra.html.
The original Zebra web site is located at:
As of this writing, development by zebra.org on Zebra has slowed down. Some work is being done by third-parties to try maintain bug-fixes and enhancements to the current Zebra code-base, which has resulted in a fork of Zebra called Quagga, see:
for further information, as well as links to additional zebra resources.
There is a mailing list for discussions about Quagga. If you have any comments or suggestions to Quagga, please subscribe to:
http://lists.quagga.net/mailman/listinfo/quagga-users.
The Quagga site has further information on the available mailing lists, see:
http://www.quagga.net/lists.php
If you think you have found a bug, please send a bug report to:
When you send a bug report, please be careful about the points below.
netstat -rn
and ifconfig -a
.
Information from zebra's VTY command show ip route
will also be
helpful.
Bug reports are very important for us to improve the quality of Quagga. Quagga is still in the development stage, but please don't hesitate to send a bug report to http://bugzilla.quagga.net.
There are three steps for installing the software: configuration, compilation, and installation.
The easiest way to get Quagga running is to issue the following commands:
% configure % make % make install
Quagga has an excellent configure script which automatically detects most host configurations. There are several additional configure options you can use to turn off IPv6 support, to disable the compilation of specific daemons, and to enable SNMP support.
You may specify any combination of the above options to the configure script. By default, the executables are placed in /usr/local/sbin and the configuration files in /usr/local/etc. The /usr/local/ installation prefix and other directories may be changed using the following options to the configuration script.
% ./configure --disable-ipv6
This command will configure zebra and the routing daemons.
Additionally, you may configure zebra to drop its elevated privileges shortly after startup and switch to another user. The configure script will automatically try to configure this support. There are three configure options to control the behaviour of Quagga daemons.
The default user and group which will be configured is 'quagga' if no user or group is specified. Note that this user or group requires write access to the local state directory (see –localstatedir) and requires at least read access, and write access if you wish to allow daemons to write out their configuration, to the configuration directory (see –sysconfdir).
On systems which have the 'libcap' capabilities manipulation library (currently only linux), the quagga system will retain only minimal capabilities required, further it will only raise these capabilities for brief periods. On systems without libcap, quagga will run as the user specified and only raise its uid back to uid 0 for brief periods.
There are several options available only to gnu/Linux systems: 1. If you use gnu/Linux, make sure that the current kernel configuration is what you want. Quagga will run with any kernel configuration but some recommendations do exist.
IPv6 support has been added in gnu/Linux kernel version 2.2. If you try to use the Quagga IPv6 feature on a gnu/Linux kernel, please make sure the following libraries have been installed. Please note that these libraries will not be needed when you uses gnu C library 2.1 or upper.
inet6-apps
inet6-apps
package includes basic IPv6 related libraries such
as inet_ntop
and inet_pton
. Some basic IPv6 programs such
as ping, ftp, and inetd are also
included. The inet-apps
can be found at
ftp://ftp.inner.net/pub/ipv6/.
net-tools
net-tools
package provides an IPv6 enabled interface and
routing utility. It contains ifconfig, route,
netstat, and other tools. net-tools
may be found at
http://www.tazenda.demon.co.uk/phil/net-tools/.
After configuring the software, you will need to compile it for your system. Simply issue the command make in the root of the source directory and the software will be compiled. If you have *any* problems at this stage, be certain to send a bug report See Bug Reports.
% ./configure . . . ./configure output . . . % make
Installing the software to your system consists of copying the compiled programs and supporting files to a standard location. After the installation process has completed, these files have been copied from your work directory to /usr/local/bin, and /usr/local/etc.
To install the Quagga suite, issue the following command at your shell prompt: make install.
% % make install %
Quagga daemons have their own terminal interface or VTY. After installation, you have to setup each beast's port number to connect to them. Please add the following entries to /etc/services.
zebrasrv 2600/tcp # zebra service zebra 2601/tcp # zebra vty ripd 2602/tcp # RIPd vty ripngd 2603/tcp # RIPngd vty ospfd 2604/tcp # OSPFd vty bgpd 2605/tcp # BGPd vty ospf6d 2606/tcp # OSPF6d vty ospfapi 2607/tcp # ospfapi isisd 2608/tcp # ISISd vty
If you use a FreeBSD newer than 2.2.8, the above entries are already added to /etc/services so there is no need to add it. If you specify a port number when starting the daemon, these entries may not be needed.
You may need to make changes to the config files in /etc/quagga/*.conf. See Config Commands.
There are five routing daemons in use, and there is one manager daemon. These daemons may be located on separate machines from the manager daemon. Each of these daemons will listen on a particular port for incoming VTY connections. The routing daemons are:
The following sections discuss commands common to all the routing daemons.
In a config file, you can write the debugging options, a vty's password, routing daemon configurations, a log file name, and so forth. This information forms the initial command set for a routing beast as it is starting.
Config files are generally found in:
Each of the daemons has its own config file. For example, zebra's default config file name is:
The daemon name plus .conf is the default config file name. You can specify a config file using the -f or --config-file options when starting the daemon.
Set password for vty interface. If there is no password, a vty won't accept connections.
These commands are deprecated and are present only for historical compatibility. The log trap command sets the current logging level for all enabled logging destinations, and it sets the default for all future logging commands that do not specify a level. The normal default logging level is debugging. The
no
form of the command resets the default level for future logging commands to debugging, but it does not change the logging level of existing logging destinations.
Enable logging output to stdout. If the optional second argument specifying the logging level is not present, the default logging level (typically debugging, but can be changed using the deprecated
log trap
command) will be used. Theno
form of the command disables logging to stdout. Thelevel
argument must have one of these values: emergencies, alerts, critical, errors, warnings, notifications, informational, or debugging. Note that the existing code logs its most important messages with severityerrors
.
If you want to log into a file, please specify
filename
as in this example:log file /var/log/quagga/bgpd.log informationalIf the optional second argument specifying the logging level is not present, the default logging level (typically debugging, but can be changed using the deprecated
log trap
command) will be used. Theno
form of the command disables logging to a file.
Enable logging output to syslog. If the optional second argument specifying the logging level is not present, the default logging level (typically debugging, but can be changed using the deprecated
log trap
command) will be used. Theno
form of the command disables logging to syslog.
Enable logging output to vty terminals that have enabled logging using the
terminal monitor
command. By default, monitor logging is enabled at the debugging level, but this command (or the deprecatedlog trap
command) can be used to change the monitor logging level. If the optional second argument specifying the logging level is not present, the default logging level (typically debugging, but can be changed using the deprecatedlog trap
command) will be used. Theno
form of the command disables logging to terminal monitors.
This command changes the facility used in syslog messages. The default facility is
daemon
. Theno
form of the command resets the facility to the defaultdaemon
facility.
To include the severity in all messages logged to a file, to stdout, or to a terminal monitor (i.e. anything except syslog), use the
log record-priority
global configuration command. To disable this option, use theno
form of the command. By default, the severity level is not included in logged messages. Note: some versions of syslogd (including Solaris) can be configured to include the facility and level in the messages emitted.
Set system wide line configuration. This configuration command applies to all VTY interfaces.
Set VTY connection timeout value. When only one argument is specified it is used for timeout value in minutes. Optional second argument is used for timeout value in seconds. Default timeout value is 10 minutes. When timeout value is zero, it means no timeout.
Do not perform timeout at all. This command is as same as exec-timeout 0 0.
Below is a sample configuration file for the zebra daemon.
! ! Zebra configuration file ! hostname Router password zebra enable password zebra ! log stdout ! !
'!' and '#' are comment characters. If the first character of the word is one of the comment characters then from the rest of the line forward will be ignored as a comment.
password zebra!password
If a comment character is not the first character of the word, it's a normal character. So in the above example '!' will not be regarded as a comment and the password is set to 'zebra!password'.
Change to configuration mode. This command is the first step to configuration.
Set terminal display length to <0-512>. If length is 0, no display control is performed.
Shows the current configuration of the logging system. This includes the status of all logging destinations.
Send a message to all logging destinations that are enabled for messages of the given severity.
These options apply to all Quagga daemons.
The file name is an run-time option rather than a configure-time option
so that multiple routing daemons can be run simultaneously. This is
useful when using Quagga to implement a routing looking glass. One
machine can be used to collect differing routing views from differing
points in the network.
VTY – Virtual Terminal [aka TeletYpe] Interface is a command line interface (CLI) for user interaction with the routing daemon.
VTY stands for Virtual TeletYpe interface. It means you can connect to the daemon via the telnet protocol.
To enable a VTY interface, you have to setup a VTY password. If there is no VTY password, one cannot connect to the VTY interface at all.
% telnet localhost 2601 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Hello, this is Quagga (version 0.98.0) Copyright © 1999-2004 Kunihiro Ishiguro, et al. User Access Verification Password: XXXXX Router> ? enable Turn on privileged commands exit Exit current mode and down to previous mode help Description of the interactive help system list Print command list show Show running system information who Display who is on a vty Router> enable Password: XXXXX Router# configure terminal Router(config)# interface eth0 Router(config-if)# ip address 10.0.0.1/8 Router(config-if)# ^Z Router#
'?' is very useful for looking up commands.
There are three basic VTY modes:
There are commands that may be restricted to specific VTY modes.
This mode is for read-only access to the CLI. One may exit the mode by
leaving the system, or by entering enable
mode.
This mode is for read-write access to the CLI. One may exit the mode by leaving the system, or by escaping to view mode.
This page is for describing other modes.
Commands that you may use at the command-line are described in the following three subsubsections.
These commands are used for moving the CLI cursor. The <C> character means press the Control Key.
These commands are used for editing text on a line. The <C> character means press the Control Key.
There are several additional CLI commands for command line completions, insta-help, and VTY session management.
help
at the beginning of
the line. Typing ? at any point in the line will show possible
completions.
zebra is an IP routing manager. It provides kernel routing table updates, interface lookups, and redistribution of routes between different routing protocols.
Besides the common invocation options (see Common Invocation Options), the zebra specific invocation options are listed below.
Set the IPv4 or IPv6 address/prefix for the interface.
Set the secondary flag for this address. This causes ospfd to not treat the address as a distinct subnet.
Enable or disables multicast flag for the interface.
Set bandwidth value of the interface in kilobits/sec. This is for calculating OSPF cost. This command does not affect the actual device configuration.
Enable/disable link-detect on platforms which support this. Currently only linux and with certain drivers - those which properly support the IFF_RUNNING flag.
Static routing is a very fundamental feature of routing technology. It defines static prefix and gateway.
network is destination prefix with format of A.B.C.D/M. gateway is gateway for the prefix. When gateway is A.B.C.D format. It is taken as a IPv4 address gateway. Otherwise it is treated as an interface name. If the interface name is null0 then zebra installs a blackhole route.
ip route 10.0.0.0/8 10.0.0.2 ip route 10.0.0.0/8 ppp0 ip route 10.0.0.0/8 null0First example defines 10.0.0.0/8 static route with gateway 10.0.0.2. Second one defines the same prefix but with gateway to interface ppp0. The third install a blackhole route.
This is alternate version of above command. When network is A.B.C.D format, user must define netmask value with A.B.C.D format. gateway is same option as above command
ip route 10.0.0.0 255.255.255.0 10.0.0.2 ip route 10.0.0.0 255.255.255.0 ppp0 ip route 10.0.0.0 255.255.255.0 null0These statements are equivalent to those in the previous example.
Multiple nexthop static route
ip route 10.0.0.1/32 10.0.0.2 ip route 10.0.0.1/32 10.0.0.3 ip route 10.0.0.1/32 eth0
If there is no route to 10.0.0.2 and 10.0.0.3, and interface eth0 is reachable, then the last route is installed into the kernel.
If zebra has been compiled with multipath support, and both 10.0.0.2 and 10.0.0.3 are reachable, zebra will install a multipath route via both nexthops, if the platform supports this.
zebra> show ip route S> 10.0.0.1/32 [1/0] via 10.0.0.2 inactive via 10.0.0.3 inactive * is directly connected, eth0
ip route 10.0.0.0/8 10.0.0.2 ip route 10.0.0.0/8 10.0.0.3 ip route 10.0.0.0/8 null0 255
This will install a multihop route via the specified next-hops if they are reachable, as well as a high-metric blackhole route, which can be useful to prevent traffic destined for a prefix to match less-specific routes (eg default) should the specified gateways not be reachable. Eg:
zebra> show ip route 10.0.0.0/8 Routing entry for 10.0.0.0/8 Known via "static", distance 1, metric 0 10.0.0.2 inactive 10.0.0.3 inactive Routing entry for 10.0.0.0/8 Known via "static", distance 255, metric 0 directly connected, Null0
These behave similarly to their ipv4 counterparts.
Select the primary kernel routing table to be used. This only works for kernels supporting multiple routing tables (like GNU/Linux 2.2.x and later). After setting tableno with this command, static routes defined after this are added to the specified table.
Display current routes which zebra holds in its database.
Router# show ip route Codes: K - kernel route, C - connected, S - static, R - RIP, B - BGP * - FIB route. K* 0.0.0.0/0 203.181.89.241 S 0.0.0.0/0 203.181.89.1 C* 127.0.0.0/8 lo C* 203.181.89.240/28 eth0
Display whether the host's IP forwarding function is enabled or not. Almost any UNIX kernel can be configured with IP forwarding disabled. If so, the box can't work as a router.
RIP – Routing Information Protocol is widely deployed interior gateway protocol. RIP was developed in the 1970s at Xerox Labs as part of the XNS routing protocol. RIP is a distance-vector protocol and is based on the Bellman-Ford algorithms. As a distance-vector protocol, RIP router send updates to its neighbors periodically, thus allowing the convergence to a known topology. In each update, the distance to any given network will be broadcasted to its neighboring router.
ripd supports RIP version 2 as described in RFC2453 and RIP version 1 as described in RFC1058.
The default configuration file name of ripd's is ripd.conf. When invocation ripd searches directory /etc/quagga. If ripd.conf is not there next search current directory.
RIP uses UDP port 520 to send and receive RIP packets. So the user must have the capability to bind the port, generally this means that the user must have superuser privileges. RIP protocol requires interface information maintained by zebra daemon. So running zebra is mandatory to run ripd. Thus minimum sequence for running RIP is like below:
# zebra -d # ripd -d
Please note that zebra must be invoked before ripd.
To stop ripd. Please use kill `cat /var/run/ripd.pid`. Certain signals have special meaningss to ripd.
ripd invocation options. Common options that can be specified (see Common Invocation Options).
The netmask features of ripd support both version 1 and version 2 of RIP. Version 1 of RIP originally contained no netmask information. In RIP version 1, network classes were originally used to determine the size of the netmask. Class A networks use 8 bits of mask, Class B networks use 16 bits of masks, while Class C networks use 24 bits of mask. Today, the most widely used method of a network mask is assigned to the packet on the basis of the interface that received the packet. Version 2 of RIP supports a variable length subnet mask (VLSM). By extending the subnet mask, the mask can be divided and reused. Each subnet can be used for different purposes such as large to middle size LANs and WAN links. Quagga ripd does not support the non-sequential netmasks that are included in RIP Version 2.
In a case of similar information with the same prefix and metric, the old information will be suppressed. Ripd does not currently support equal cost multipath routing.
The
router rip
command is necessary to enable RIP. To disable RIP, use theno router rip
command. RIP must be enabled before carrying out any of the RIP commands.
RIP can be configured to process either Version 1 or Version 2 packets, the default mode is Version 2. If no version is specified, then the RIP daemon will default to Version 2. If RIP is set to Version 1, the setting "Version 1" will be displayed, but the setting "Version 2" will not be displayed whether or not Version 2 is set explicitly as the version of RIP being used. The version can be specified globally, and also on a per-interface basis (see below).
Set the RIP enable interface by network. The interfaces which have addresses matching with network are enabled.
This group of commands either enables or disables RIP interfaces between certain numbers of a specified network address. For example, if the network for 10.0.0.0/24 is RIP enabled, this would result in all the addresses from 10.0.0.0 to 10.0.0.255 being enabled for RIP. The
no network
command will disable RIP for the specified network.
Set a RIP enabled interface by ifname. Both the sending and receiving of RIP packets will be enabled on the port specified in the
network ifname
command. Theno network ifname
command will disable RIP on the specified interface.
Specify RIP neighbor. When a neighbor doesn't understand multicast, this command is used to specify neighbors. In some cases, not all routers will be able to understand multicasting, where packets are sent to a network or a group of addresses. In a situation where a neighbor cannot process multicast packets, it is necessary to establish a direct link between routers. The neighbor command allows the network administrator to specify a router as a RIP neighbor. The
no neighbor a.b.c.d
command will disable the RIP neighbor.
Below is very simple RIP configuration. Interface eth0
and
interface which address match to 10.0.0.0/8
are RIP enabled.
! router rip network 10.0.0.0/8 network eth0 !
Passive interface
This command sets the specified interface to passive mode. On passive mode interface, all receiving packets are processed as normal and ripd does not send either multicast or unicast RIP packets except to RIP neighbors specified with
neighbor
command. The interface may be specified as default to make ripd default to passive on all interfaces.The default is to be passive on all interfaces.
RIP version handling
version can be `1', `2', `1 2'. This configuration command overrides the router's rip version setting. The command will enable the selected interface to send packets with RIP Version 1, RIP Version 2, or both. In the case of '1 2', packets will be both broadcast and multicast.
The default is to send only version 2.
Version setting for incoming RIP packets. This command will enable the selected interface to receive packets in RIP Version 1, RIP Version 2, or both.
The default is to receive both versions.
RIP split-horizon
Control split-horizon on the interface. Default is
ip split-horizon
. If you don't perform split-horizon on the interface, please specifyno ip split-horizon
.
redistribute kernel
redistributes routing information from kernel route entries into the RIP tables.no redistribute kernel
disables the routes.
redistribute static
redistributes routing information from static route entries into the RIP tables.no redistribute static
disables the routes.
Redistribute connected routes into the RIP tables.
no redistribute connected
disables the connected routes in the RIP tables. This command redistribute connected of the interface which RIP disabled. The connected route on RIP enabled interface is announced by default.
redistribute ospf
redistributes routing information from ospf route entries into the RIP tables.no redistribute ospf
disables the routes.
redistribute bgp
redistributes routing information from bgp route entries into the RIP tables.no redistribute bgp
disables the routes.
If you want to specify RIP only static routes:
This command is specific to Quagga. The
route
command makes a static route only inside RIP. This command should be used only by advanced users who are particularly knowledgeable about the RIP protocol. In most cases, we recommend creating a static route in Quagga and redistributing it in RIP usingredistribute static
.
RIP routes can be filtered by a distribute-list.
You can apply access lists to the interface with a
distribute-list
command. access_list is the access list name. direct is in or out. If direct is in the access list is applied to input packets.The
distribute-list
command can be used to filter the RIP path.distribute-list
can apply access-lists to a chosen interface. First, one should specify the access-list. Next, the name of the access-list is used in the distribute-list command. For example, in the following configuration eth0 will permit only the paths that match the route 10.0.0.0/8! router rip distribute-list private in eth0 ! access-list private permit 10 10.0.0.0/8 access-list private deny any !
distribute-list
can be applied to both incoming and outgoing data.
You can apply prefix lists to the interface with a
distribute-list
command. prefix_list is the prefix list name. Next is the direction of in or out. If direct is in the access list is applied to input packets.
RIP metric is a value for distance for the network. Usually ripd increment the metric when the network information is received. Redistributed routes' metric is set to 1.
This command modifies the default metric value for redistributed routes. The default value is 1. This command does not affect connected route even if it is redistributed by redistribute connected. To modify connected route's metric value, please use redistribute connected metric or route-map. offset-list also affects connected routes.
Distance value is used in zebra daemon. Default RIP distance is 120.
Set default RIP distance to specified value.
Set default RIP distance to specified value when the route's source IP address matches the specified prefix.
Set default RIP distance to specified value when the route's source IP address matches the specified prefix and the specified access-list.
Usage of ripd's route-map support.
Optional argument route-map MAP_NAME can be added to each redistribute
statement.
redistribute static [route-map MAP_NAME] redistribute connected [route-map MAP_NAME] .....
Cisco applies route-map _before_ routes will exported to rip route table. In current Quagga's test implementation, ripd applies route-map after routes are listed in the route table and before routes will be announced to an interface (something like output filter). I think it is not so clear, but it is draft and it may be changed at future.
Route-map statement (see Route Map) is needed to use route-map functionality.
This command match to incoming interface. Notation of this match is different from Cisco. Cisco uses a list of interfaces - NAME1 NAME2 ... NAMEN. Ripd allows only one name (maybe will change in the future). Next - Cisco means interface which includes next-hop of routes (it is somewhat similar to "ip next-hop" statement). Ripd means interface where this route will be sent. This difference is because "next-hop" of same routes which sends to different interfaces must be different. Maybe it'd be better to made new matches - say "match interface-out NAME" or something like that.
Match if route destination is permitted by access-list.
Cisco uses here <access-list>, ripd IPv4 address. Match if route has this next-hop (meaning next-hop listed in the rip route table - "show ip rip")
This command match to the metric value of RIP updates. For other protocol compatibility metric range is shown as <0-4294967295>. But for RIP protocol only the value range <0-16> make sense.
This command set next hop value in RIPv2 protocol. This command does not affect RIPv1 because there is no next hop field in the packet.
Set a metric for matched route when sending announcement. The metric value range is very large for compatibility with other protocols. For RIP, valid metric values are from 1 to 16.
Set the interface with RIPv2 MD5 authentication.
Set the interface with RIPv2 simple password authentication.
RIP version 2 has simple text authentication. This command sets authentication string. The string must be shorter than 16 characters.
Specifiy Keyed MD5 chain.
! key chain test key 1 key-string test ! interface eth1 ip rip authentication mode md5 ip rip authentication key-chain test !
RIP protocol has several timers. User can configure those timers' values by
timers basic
command.The default settings for the timers are as follows:
- The update timer is 30 seconds. Every update timer seconds, the RIP process is awakened to send an unsolicited Response message containing the complete routing table to all neighboring RIP routers.
- The timeout timer is 180 seconds. Upon expiration of the timeout, the route is no longer valid; however, it is retained in the routing table for a short time so that neighbors can be notified that the route has been dropped.
- The garbage collect timer is 120 seconds. Upon expiration of the garbage-collection timer, the route is finally removed from the routing table.
The
timers basic
command allows the the default values of the timers listed above to be changed.
The
no timers basic
command will reset the timers to the default settings listed above.
To display RIP routes.
The command displays all RIP routes. For routes that are received through RIP, this command will display the time the packet was sent and the tag information. This command will also display this information for routes redistributed into RIP.
The command displays current RIP status. It includes RIP timer, filtering, version, RIP enabled interface and RIP peer inforation.
ripd> show ip protocols Routing Protocol is "rip" Sending updates every 30 seconds with +/-50%, next due in 35 seconds Timeout after 180 seconds, garbage collect after 120 seconds Outgoing update filter list for all interface is not set Incoming update filter list for all interface is not set Default redistribution metric is 1 Redistributing: kernel connected Default version control: send version 2, receive version 2 Interface Send Recv Routing for Networks: eth0 eth1 1.1.1.1 203.181.89.241 Routing Information Sources: Gateway BadPackets BadRoutes Distance Last Update
Debug for RIP protocol.
debug rip
will show RIP events. Sending and receiving
packets, timers, and changes in interfaces are events shown with ripd.
debug rip packet
will display detailed information about the RIP
packets. The origin and port number of the packet as well as a packet
dump is shown.
This command will show the communication between ripd and zebra. The main information will include addition and deletion of paths to the kernel and the sending and receiving of interface information.
show debugging rip
will show all information currently set for ripd
debug.
ripngd supports the RIPng protocol as described in RFC2080. It's an IPv6 reincarnation of the RIP protocol.
There are no ripngd
specific invocation options. Common options
can be specified (see Common Invocation Options).
Currently ripngd supports the following commands:
This command is the default and does not appear in the configuration. With this statement, RIPng routes go to the zebra daemon.
You can apply an access-list to the interface using the
distribute-list
command. access_list is an access-list name. direct is in or out. If direct is in, the access-list is applied only to incoming packets.distribute-list local-only out sit1
OSPF version 2 is a routing protocol which described in RFC2328 - OSPF Version 2. OSPF is IGP (Interior Gateway Protocols). Compared with RIP, OSPF can provide scalable network support and faster convergence time. OSPF is widely used in large networks such as ISP backbone and enterprise networks.
There is no ospfd specific options. Common options can be specified (see Common Invocation Options) to ospfd. ospfd needs interface information from zebra. So please make it sure zebra is running before invoking ospfd.
Like other daemons, ospfd configuration is done in OSPF specific configuration file ospfd.conf.
To start OSPF process you have to specify the OSPF router. As of this writing, ospfd does not support multiple OSPF processes.
Enable or disable the OSPF process. ospfd does not yet support multiple OSPF processes. So you can not specify an OSPF process number.
type can be cisco|ibm|shortcut|standard More information regarding the behaviour controlled by this command can be found in draft-ietf-ospf-abr-alt-05.txt and draft-ietf-ospf-shortcut-abr-02.txt Quote: "Though the definition of the Area Border Router (ABR) in the OSPF specification does not require a router with multiple attached areas to have a backbone connection, it is actually necessary to provide successful routing to the inter-area and external destinations. If this requirement is not met, all traffic destined for the areas not connected to such an ABR or out of the OSPF domain, is dropped. This document describes alternative ABR behaviors implemented in Cisco and IBM routers."
This rfc2328, the sucessor to rfc1583, suggests according to section G.2 (changes) in section 16.4 a change to the path preference algorithm that prevents possible routing loops that were possible in the old version of OSPFv2. More specifically it demands that inter-area paths and intra-area path are now of equal preference but still both preferred to external paths.
This command specifies the OSPF enabled interface(s). If the interface has an address from range 192.168.1.0/24 then the command below enables ospf on this interface so router can provide network information to the other ospf routers via this interface.
router ospf network 192.168.1.0/24 area 0.0.0.0Prefix length in interface must be equal or bigger (ie. smaller network) than prefix length in network statement. For example statement above doesn't enable ospf on interface with address 192.168.1.1/23, but it does on interface with address 192.168.1.129/25.
Summarize intra area paths from specified area into one Type-3 summary-LSA announced to other areas. This command can be used only in ABR and ONLY router-LSAs (Type-1) and network-LSAs (Type-2) (ie. LSAs with scope area) can be summarized. Type-5 AS-external-LSAs can't be summarized - their scope is AS. Summarizing Type-7 AS-external-LSAs isn't supported yet by Quagga.
router ospf network 192.168.1.0/24 area 0.0.0.0 network 10.0.0.0/8 area 0.0.0.10 area 0.0.0.10 range 10.0.0.0/8With configuration above one Type-3 Summary-LSA with routing info 10.0.0.0/8 is announced into backbone area if area 0.0.0.10 contains at least one intra-area network (ie. described with router or network LSA) from this range.
Instead of summarizing intra area paths filter them - ie. intra area paths from this range are not advertised into other areas. This command makes sense in ABR only.
Substitute summarized prefix with another prefix.
router ospf network 192.168.1.0/24 area 0.0.0.0 network 10.0.0.0/8 area 0.0.0.10 area 0.0.0.10 range 10.0.0.0/8 substitute 11.0.0.0/8One Type-3 summary-LSA with routing info 11.0.0.0/8 is announced into backbone area if area 0.0.0.10 contains at least one intra-area network (ie. described with router-LSA or network-LSA) from range 10.0.0.0/8. This command makes sense in ABR only.
Filter Type-3 summary-LSAs announced to other areas originated from intra- area paths from specified area.
router ospf network 192.168.1.0/24 area 0.0.0.0 network 10.0.0.0/8 area 0.0.0.10 area 0.0.0.10 export-list foo ! access-list foo permit 10.10.0.0/16 access-list foo deny anyWith example above any intra-area paths from area 0.0.0.10 and from range 10.10.0.0/16 (for example 10.10.1.0/24 and 10.10.2.128/30) are announced into other areas as Type-3 summary-LSA's, but any others (for example 10.11.0.0/16 or 10.128.30.16/30) aren't. This command makes sense in ABR only.
Same as export-list, but it applies to paths announced into specified area as Type-3 summary-LSAs.
Filtering Type-3 summary-LSAs to/from area using prefix lists. This command makes sense in ABR only.
Set OSPF authentication key to a simple password. After setting AUTH_KEY, all OSPF packets are authenticated. AUTH_KEY has length up to 8 chars.
Set OSPF authentication key to a cryptographic password. The cryptographic algorithm is MD5. KEYID identifies secret key used to create the message digest. KEY is the actual message digest key up to 16 chars.
Note that OSPF MD5 authentication requires that time never go backwards (correct time is not important, only that it never goes backwards), even across resets, if ospfd is to be able to promptly reestabish adjacencies with its neighbours after restarts/reboots. The host should have system time be set at boot from an external source (eg battery backed clock, NTP, etc.) or else the system clock should be periodically saved to non-volative storage and restored at boot if MD5 authentication is to be expected to work reliably.
Set link cost for the specified interface. The cost value is set to router-LSA's metric field and used for SPF calculation.
Set number of seconds for RouterDeadInterval timer value used for Wait Timer and Inactivity Timer. This value must be the same for all routers attached to a common network. The default value is 40 seconds.
Set number of seconds for HelloInterval timer value. Setting this value, Hello packet will be sent every timer value seconds on the specified interface. This value must be the same for all routers attached to a common network. The default value is 10 seconds.
Set explicitly network type for specifed interface.
Set RouterPriority integer value. Setting higher value, router will be more eligible to become Designated Router. Setting the value to 0, router is no longer eligible to Designated Router. The default value is 1.
Set number of seconds for RxmtInterval timer value. This value is used when retransmitting Database Description and Link State Request packets. The default value is 5 seconds.
Set number of seconds for InfTransDelay value. LSAs' age should be incremented by this value when transmitting. The default value is 1 seconds.
ospf6d is a daemon support OSPF version 3 for IPv6 network. OSPF for IPv6 is described in RFC2740.
Bind interface to specified area, and start sending OSPF packets. area can be specified as 0.
Area support for OSPFv3 is not yet implemented.
Sets interface's Hello Interval. Default 40
Sets interface's Router Dead Interval. Default value is 40.
Sets interface's Rxmt Interval. Default value is 5.
Sets interface's Router Priority. Default value is 1.
Sets interface's Inf-Trans-Delay. Default value is 1.
INSTANCE_ID is an optional OSPF instance ID. To see router ID and OSPF instance ID, simply type "show ipv6 ospf6 <cr>".
This command shows LSA database summary. You can specify the type of LSA.
BGP stands for a Border Gateway Protocol. The lastest BGP version
is 4. It is referred as BGP-4. BGP-4 is one of the Exterior Gateway
Protocols and de-fact standard of Inter Domain routing protocol.
BGP-4 is described in RFC1771
- A Border Gateway Protocol
4 (BGP-4).
Many extentions are added to RFC1771
. RFC2858
-
Multiprotocol Extensions for BGP-4 provide multiprotocol
support to BGP-4.
Default configuration file of bgpd is bgpd.conf. bgpd searches the current directory first then /etc/quagga/bgpd.conf. All of bgpd's command must be configured in bgpd.conf.
bgpd specific invocation options are described below. Common options may also be specified (see Common Invocation Options).
First of all you must configure BGP router with router bgp command. To configure BGP router, you need AS number. AS number is an identification of autonomous system. BGP protocol uses the AS number for detecting whether the BGP connection is internal one or external one.
Enable a BGP protocol process with the specified asn. After this statement you can input any
BGP Commands
. You can not create different BGP process under different asn without specifyingmultiple-instance
(see Multiple instance).
This command specifies the router-ID. If bgpd connects to zebra it gets interface and address information. In that case default router ID value is selected as the largest IP Address of the interfaces. When
router zebra
is not enabled bgpd can't get interface information sorouter-id
is set to 0.0.0.0. So please set router-id by hand.
This command change distance value of BGP. Each argument is distance value for external routes, internal routes and local routes.
This command set distance value to
This command adds the announcement network.
router bgp 1 network 10.0.0.0/8This configuration example says that network 10.0.0.0/8 will be announced to all neighbors. Some vendors' routers don't advertise routes if they aren't present in their IGP routing tables;
bgp
doesn't care about IGP routes when announcing its routes.
This command specifies an aggregate address. Resulting routes inlucde AS set.
This command specifies an aggregate address. Aggreated routes will not be announce.
Creates a new neighbor whose remote-as is asn. peer can be an IPv4 address or an IPv6 address.
router bgp 1 neighbor 10.0.0.1 remote-as 2In this case my router, in AS-1, is trying to peer with AS-2 at 10.0.0.1.
This command must be the first command used when configuring a neighbor. If the remote-as is not specified, bgpd will complain like this:
can't find neighbor 10.0.0.1
In a router bgp
clause there are neighbor specific configurations
required.
Shutdown the peer. We can delete the neighbor's configuration by
no neighbor
peerremote-as
as-number but all configuration of the neighbor will be deleted. When you want to preserve the configuration, but want to drop the BGP peer, use this syntax.
Set description of the peer.
Set up the neighbor's BGP version. version can be 4, 4+ or 4-. BGP version 4 is the default value used for BGP peering. BGP version 4+ means that the neighbor supports Multiprotocol Extensions for BGP-4. BGP version 4- is similar but the neighbor speaks the old Internet-Draft revision 00's Multiprotocol Extensions for BGP-4. Some routing software is still using this version.
When you connect to a BGP peer over an IPv6 link-local address, you have to specify the ifname of the interface used for the connection.
This command specifies an announced route's nexthop as being equivalent to the address of the bgp router.
bgpd's default is to not announce the default route (0.0.0.0/0) even it is in routing table. When you want to announce default routes to the peer, use this command.
This command specifies a default weight value for the neighbor's routes.
This command specifies a distribute-list for the peer. direct is in or out.
Apply a route-map on the neighbor. direct must be
in
orout
.
AS (Autonomous System) is one of the essential element of BGP. BGP
is a distance vector routing protocol. AS framework provides distance
vector metric and loop detection to BGP. RFC1930
-
Guidelines for creation, selection, and registration of an
Autonomous System (AS) describes how to use AS.
AS number is tow octet digita value. So the value range is from 1 to 65535. AS numbers 64512 through 65535 are defined as private AS numbers. Private AS numbers must not to be advertised in the global Internet.
AS path regular expression can be used for displaying BGP routes and
AS path access list. AS path regular expression is based on
POSIX 1003.2
regular expressions. Following description is
just a subset of POSIX
regular expression. User can use full
POSIX
regular expression. Adding to that special character '_'
is added for AS path regular expression.
.
*
+
?
^
$
_
_
has special meanings in AS path regular expression.
It matches to space and comma , and AS set delimiter { and } and AS
confederation delimiter (
and )
. And it also matches to
the beginning of the line and the end of the line. So _
can be
used for AS value boundaries match. show ip bgp regexp _7675_
matches to all of BGP routes which as AS number include 7675.
To show BGP routes which has specific AS path information show
ip bgp
command can be used.
This commands display BGP routes that matches AS path regular expression line.
AS path access list is user defined AS path.
This command defines a new AS path access list.
BGP communities attribute is widely used for implementing policy
routing. Network operators can manipulate BGP communities attribute
based on their network policy. BGP communities attribute is defined
in RFC1997
- BGP Communities Attribute and
RFC1998
- An Application of the BGP Community Attribute
in Multi-home Routing. It is an optional transitive attribute,
therefore local policy can travel through different autonomous system.
Communities attribute is a set of communities values. Each communities value is 4 octet long. The following format is used to define communities value.
AS:VAL
AS
is high
order 2 octet in digit format. VAL
is low order 2 octet in
digit format. This format is useful to define AS oriented policy
value. For example, 7675:80
can be used when AS 7675 wants to
pass local policy value 80 to neighboring peer.
internet
internet
represents well-known communities value 0.
no-export
no-export
represents well-known communities value NO_EXPORT
no-advertise
no-advertise
represents well-known communities value
NO_ADVERTISE
local-AS
local-AS
represents well-known communities value
NO_EXPORT_SUBCONFED
(0xFFFFFF03). All routes carry this
value must not be advertised to external BGP peers. Even if the
neighboring router is part of confederation, it is considered as
external BGP peer, so the route will not be announced to the peer.
When BGP communities attribute is received, duplicated communities value in the communities attribute is ignored and each communities values are sorted in numerical order.
BGP community list is a user defined BGP communites attribute list. BGP community list can be used for matching or manipulating BGP communities attribute in updates.
There are two types of community list. One is standard community list and another is expanded community list. Standard community list defines communities attribute. Expanded community list defines communities attribute string with regular expression. Standard community list is compiled into binary format when user define it. Standard community list will be directly compared to BGP communities attribute in BGP updates. Therefore the comparison is faster than expanded community list.
This command defines a new standard community list. community is communities value. The community is compiled into community structure. We can define multiple community list under same name. In that case match will happen user defined order. Once the community list matches to communities attribute in BGP updates it return permit or deny by the community list definition. When there is no matched entry, deny will be returned. When community is empty it matches to any routes.
This command defines a new expanded community list. line is a string expression of communities attribute. line can include regular expression to match communities attribute in BGP updates.
These commands delete community lists specified by name. All of community lists shares a single name space. So community lists can be removed simpley specifying community lists name.
This command display current community list information. When name is specified the specified community list's information is shown.
# show ip community-list Named Community standard list CLIST permit 7675:80 7675:100 no-export deny internet Named Community expanded list EXPAND permit : # show ip community-list CLIST Named Community standard list CLIST permit 7675:80 7675:100 no-export deny internet
When number is used for BGP community list name, the number has special meanings. Community list number in the range from 1 and 99 is standard community list. Community list number in the range from 100 to 199 is expanded community list. These community lists are called as numbered community lists. On the other hand normal community lists is called as named community lists.
This command defines a new community list. <1-99> is standard community list number. Community list name within this range defines standard community list. When community is empty it matches to any routes.
This command defines a new community list. <100-199> is expanded community list number. Community list name within this range defines expanded community list.
When community list type is not specifed, the community list type is automatically detected. If community can be compiled into communities attribute, the community list is defined as a standard community list. Otherwise it is defined as an expanded community list. This feature is left for backward compability. Use of this feature is not recommended.
In Route Map (see Route Map), we can match or set BGP communities attribute. Using this feature network operator can implement their network policy based on BGP communities attribute.
Following commands can be used in Route Map.
This command perform match to BGP updates using community list word. When the one of BGP communities value match to the one of communities value in community list, it is match. When
exact-match
keyword is spcified, match happen only when BGP updates have completely same communities value specified in the community list.
This command manipulate communities value in BGP updates. When
none
is specified as communities value, it removes entire communities attribute from BGP updates. When community is notnone
, specified communities value is set to BGP updates. If BGP updates already has BGP communities value, the existing BGP communities value is replaced with specified community value. Whenadditive
keyword is specified, community is appended to the existing communities value.
This command remove communities value from BGP communities attribute. The word is community list name. When BGP route's communities value matches to the community list word, the communities value is removed. When all of communities value is removed eventually, the BGP update's communities attribute is completely removed.
To show BGP routes which has specific BGP communities attribute,
show ip bgp
command can be used. The community value and
community list can be used for show ip bgp
command.
show ip bgp community
displays BGP routes which has communities attribute. When community is specified, BGP routes that matches community value is displayed. For this command,internet
keyword can't be used for community value. Whenexact-match
is specified, it display only routes that have an exact match.
This commands display BGP routes that matches community list word. When
exact-match
is specified, display only routes that have an exact match.
Following configuration is the most typical usage of BGP communities attribute. AS 7675 provides upstream Internet connection to AS 100. When following configuration exists in AS 7675, AS 100 networks operator can set local preference in AS 7675 network by setting BGP communities attribute to the updates.
router bgp 7675 neighbor 192.168.0.1 remote-as 100 neighbor 192.168.0.1 route-map RMAP in ! ip community-list 70 permit 7675:70 ip community-list 70 deny ip community-list 80 permit 7675:80 ip community-list 80 deny ip community-list 90 permit 7675:90 ip community-list 90 deny ! route-map RMAP permit 10 match community 70 set local-preference 70 ! route-map RMAP permit 20 match community 80 set local-preference 80 ! route-map RMAP permit 30 match community 90 set local-preference 90
Following configuration announce 10.0.0.0/8 from AS 100 to AS 7675. The route has communities value 7675:80 so when above configuration exists in AS 7675, announced route's local preference will be set to value 80.
router bgp 100 network 10.0.0.0/8 neighbor 192.168.0.2 remote-as 7675 neighbor 192.168.0.2 route-map RMAP out ! ip prefix-list PLIST permit 10.0.0.0/8 ! route-map RMAP permit 10 match ip address prefix-list PLIST set community 7675:80
Following configuration is an example of BGP route filtering using communities attribute. This configuration only permit BGP routes which has BGP communities value 0:80 or 0:90. Network operator can put special internal communities value at BGP border router, then limit the BGP routes announcement into the internal network.
router bgp 7675 neighbor 192.168.0.1 remote-as 100 neighbor 192.168.0.1 route-map RMAP in ! ip community-list 1 permit 0:80 0:90 ! route-map RMAP permit in match community 1
Following exmaple filter BGP routes which has communities value 1:1. When there is no match community-list returns deny. To avoid filtering all of routes, we need to define permit any at last.
router bgp 7675 neighbor 192.168.0.1 remote-as 100 neighbor 192.168.0.1 route-map RMAP in ! ip community-list standard FILTER deny 1:1 ip community-list standard FILTER permit ! route-map RMAP permit 10 match community FILTER
Communities value keyword internet
has special meanings in
standard community lists. In below example internet
act as
match any. It matches all of BGP routes even if the route does not
have communities attribute at all. So community list INTERNET
is same as above example's FILTER
.
ip community-list standard INTERNET deny 1:1 ip community-list standard INTERNET permit internet
Following configuration is an example of communities value deletion.
With this configuration communities value 100:1 and 100:2 is removed
from BGP updates. For communities value deletion, only permit
community-list is used. deny
community-list is ignored.
router bgp 7675 neighbor 192.168.0.1 remote-as 100 neighbor 192.168.0.1 route-map RMAP in ! ip community-list standard DEL permit 100:1 100:2 ! route-map RMAP permit 10 set comm-list DEL delete
BGP extended communities attribute is introduced with MPLS VPN/BGP technology. MPLS VPN/BGP expands capability of network infrastructure to provide VPN functionality. At the same time it requires a new framework for policy routing. With BGP Extended Communities Attribute we can use Route Target or Site of Origin for implementing network policy for MPLS VPN/BGP.
BGP Extended Communities Attribute is similar to BGP Communities Attribute. It is an optional transitive attribute. BGP Extended Communities Attribute can carry multiple Extended Community value. Each Extended Community value is eight octet length.
BGP Extended Communities Attribute provides an extended range compared with BGP Communities Attribute. Adding to that there is a type field in each value to provides community space structure.
There are two format to define Extended Community value. One is AS based format the other is IP address based format.
AS:VAL
AS
part is 2 octets Global Administrator subfield in Extended
Community value. VAL
part is 4 octets Local Administrator
subfield. 7675:100
represents AS 7675 policy value 100.
IP-Address:VAL
IP-Address
part is 4 octets Global Administrator subfield.
VAL
part is 2 octets Local Administrator subfield.
10.0.0.1:100
represents
Expanded Community Lists is a user defined BGP Expanded Community Lists.
This command defines a new standard extcommunity-list. extcommunity is extended communities value. The extcommunity is compiled into extended community structure. We can define multiple extcommunity-list under same name. In that case match will happen user defined order. Once the extcommunity-list matches to extended communities attribute in BGP updates it return permit or deny based upon the extcommunity-list definition. When there is no matched entry, deny will be returned. When extcommunity is empty it matches to any routes.
This command defines a new expanded extcommunity-list. line is a string expression of extended communities attribute. line can include regular expression to match extended communities attribute in BGP updates.
These commands delete extended community lists specified by name. All of extended community lists shares a single name space. So extended community lists can be removed simpley specifying the name.
This command display current extcommunity-list information. When name is specified the community list's information is shown.
# show ip extcommunity-list
This command displays BGP routes. When no route is specified it display all of IPv4 BGP routes.
BGP table version is 0, local router ID is 10.1.1.1 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 1.1.1.1/32 0.0.0.0 0 32768 i Total number of prefixes 1
This command display BGP routes using AS path regular expression (see Display BGP Routes by AS Path).
This command display BGP routes using community (see Display BGP Routes by Community).
This command display BGP routes using community list (see Display BGP Routes by Community).
When adding IPv6 routing information exchange feature to BGP. There were some proposals. IETF IDR working group finally take a proposal called Multiprotocol Extension for BGP. The specification is described in RFC2283. The protocol does not define new protocols. It defines new attributes to existing BGP. When it is used exchanging IPv6 routing information it is called BGP-4+. When it is used for exchanging multicast routing information it is called MBGP.
bgpd supports Multiprotocol Extension for BGP. So if remote peer supports the protocol, bgpd can exchange IPv6 and/or multicast routing information.
Traditional BGP does not have the feature to detect remote peer's capability whether it can handle other than IPv4 unicast routes. This is a big problem using Multiprotocol Extension for BGP to operational network. draft-ietf-idr-bgp4-cap-neg-04.txt is proposing a feature called Capability Negotiation. bgpd use this Capability Negotiation to detect remote peer's capabilities. If the peer is only configured as IPv4 unicast neighbor, bgpd does not send these Capability Negotiation packets.
By default, Quagga will bring up peering with minimal common capability for the both sides. For example, local router has unicast and multicast capabilitie and remote router has unicast capability. In this case, the local router will establish the connection with unicast only capability. When there are no common capabilities, Quagga sends Unsupported Capability error and then resets the connection.
If you want to completely match capabilities with remote peer. Please use strict-capability-match command.
Strictly compares remote capabilities and local capabilities. If capabilities are different, send Unsupported Capability error then reset connection.
You may want to disable sending Capability Negotiation OPEN message optional parameter to the peer when remote peer does not implement Capability Negotiation. Please use dont-capability-negotiate command to disable the feature.
Suppress sending Capability Negotiation as OPEN message optional parameter to the peer. This command only affects the peer is configured other than IPv4 unicast configuration.
When remote peer does not have capability negotiation feature, remote peer will not send any capabilities at all. In that case, bgp configures the peer with configured capabilities.
You may prefer locally configured capabilities more than the negotiated capabilities even though remote peer sends capabilities. If the peer is configured by override-capability, bgpd ignores received capabilities then override negotiated capabilities with configured values.
Override the result of Capability Negotiation with local configuration. Ignore remote peer's capability value.
At an Internet Exchange point, many ISPs are connected to each other by
external BGP peering. Normally these external BGP connection are done by
full mesh
method. As with internal BGP full mesh formation,
this method has a scaling problem.
This scaling problem is well known. Route Server is a method to resolve the problem. Each ISP's BGP router only peers to Route Server. Route Server serves as BGP information exchange to other BGP routers. By applying this method, numbers of BGP connections is reduced from O(n*(n-1)/2) to O(n).
Unlike normal BGP router, Route Server must have several routing tables
for managing different routing policies for each BGP speaker. We call the
routing tables as different view
s. bgpd can work as
normal BGP router or Route Server or both at the same time.
To enable multiple view function of bgpd
, you must turn on
multiple instance feature beforehand.
Enable BGP multiple instance feature. After this feature is enabled, you can make multiple BGP instances or multiple BGP views.
Disable BGP multiple instance feature. You can not disable this feature when BGP multiple instances or views exist.
When you want to make configuration more Cisco like one,
When bgp config-type cisco is specified,
“no synchronization” is displayed. “no auto-summary” is desplayed.
“network” and “aggregate-address” argument is displayed as “A.B.C.D M.M.M.M”
Quagga: network 10.0.0.0/8 Cisco: network 10.0.0.0
Quagga: aggregate-address 192.168.0.0/24 Cisco: aggregate-address 192.168.0.0 255.255.255.0
Community attribute handling is also different. If there is no configuration is specified community attribute and extended community attribute are sent to neighbor. When user manually disable the feature community attribute is not sent to the neighbor. In case of “bgp config-type cisco” is specified, community attribute is not sent to the neighbor by default. To send community attribute user has to specify “neighbor A.B.C.D send-community” command.
! router bgp 1 neighbor 10.0.0.1 remote-as 1 no neighbor 10.0.0.1 send-community !
! router bgp 1 neighbor 10.0.0.1 remote-as 1 neighbor 10.0.0.1 send-community !
BGP instance is a normal BGP process. The result of route selection goes to the kernel routing table. You can setup different AS at the same time when BGP multiple instance feature is enabled.
bgp multiple-instance ! router bgp 1 neighbor 10.0.0.1 remote-as 2 neighbor 10.0.0.2 remote-as 3 ! router bgp 2 neighbor 10.0.0.3 remote-as 4 neighbor 10.0.0.4 remote-as 5
BGP view is almost same as normal BGP process. The result of route selection does not go to the kernel routing table. BGP view is only for exchanging BGP routing information.
Make a new BGP view. You can use arbitrary word for the name. This view's route selection result does not go to the kernel routing table.
With this command, you can setup Route Server like below.
bgp multiple-instance ! router bgp 1 view 1 neighbor 10.0.0.1 remote-as 2 neighbor 10.0.0.2 remote-as 3 ! router bgp 2 view 2 neighbor 10.0.0.3 remote-as 4 neighbor 10.0.0.4 remote-as 5
You can set different routing policy for a peer. For example, you can set different filter for a peer.
bgp multiple-instance ! router bgp 1 view 1 neighbor 10.0.0.1 remote-as 2 neighbor 10.0.0.1 distribute-list 1 in ! router bgp 1 view 2 neighbor 10.0.0.1 remote-as 2 neighbor 10.0.0.1 distribute-list 2 in
This means BGP update from a peer 10.0.0.1 goes to both BGP view 1 and view 2. When the update is inserted into view 1, distribute-list 1 is applied. On the other hand, when the update is inserted into view 2, distribute-list 2 is applied.
To display routing table of BGP view, you must specify view name.
zebra configuration =================== ! ! Actually there is no need to configure zebra ! bgpd configuration ================== ! ! This means that routes go through zebra and into the kernel. ! router zebra ! ! MP-BGP configuration ! router bgp 7675 bgp router-id 10.0.0.1 neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 remote-as as-number ! address-family ipv6 network 3ffe:506::/32 neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 activate neighbor 3ffe:1cfa:0:2:2a0:c9ff:fe9e:f56 route-map set-nexthop out neighbor 3ffe:1cfa:0:2:2c0:4fff:fe68:a231 remote-as as-number neighbor 3ffe:1cfa:0:2:2c0:4fff:fe68:a231 route-map set-nexthop out exit-address-family ! ipv6 access-list all permit any ! ! Set output nexthop address. ! route-map set-nexthop permit 10 match ipv6 address all set ipv6 nexthop global 3ffe:1cfa:0:2:2c0:4fff:fe68:a225 set ipv6 nexthop local fe80::2c0:4fff:fe68:a225 ! ! logfile FILENAME is obsolete. Please use log file FILENAME log file bgpd.log !
Dump all BGP packet and events to path file.
Dump BGP updates to path file.
Dump whole BGP routing table to path. This is heavy process.
The purpose of a Route Server is to centralize the peerings between BGP speakers. For example if we have an exchange point scenario with four BGP speakers, each of which maintaining a BGP peering with the other three (see fig:full-mesh), we can convert it into a centralized scenario where each of the four establishes a single BGP peering against the Route Server (see fig:route-server).
We will first describe briefly the Route Server model implemented by Quagga. We will explain the commands that have been added for configuring that model. And finally we will show a full example of Quagga configured as Route Server.
First we are going to describe the normal processing that BGP announcements suffer inside a standard BGP speaker, as shown in fig:normal-processing, it consists of three steps:
Of course we want that the routing tables obtained in each of the routers are the same when using the route server than when not. But as a consequence of having a single BGP peering (against the route server), the BGP speakers can no longer distinguish from/to which peer each announce comes/goes. This means that the routers connected to the route server are not able to apply by themselves the same input/output filters as in the full mesh scenario, so they have to delegate those functions to the route server.
Even more, the “best path” selection must be also performed inside the route server on behalf of its clients. The reason is that if, after applying the filters of the announcer and the (potential) receiver, the route server decides to send to some client two or more different announcements referred to the same destination, the client will only retain the last one, considering it as an implicit withdrawal of the previous announcements for the same destination. This is the expected behavior of a BGP speaker as defined in RFC1771, and even though there are some proposals of mechanisms that permit multiple paths for the same destination to be sent through a single BGP peering, none of them are currently supported by most of the existing BGP implementations.
As a consequence a route server must maintain additional information and perform additional tasks for a RS-client that those necessary for common BGP peerings. Essentially a route server must:
When we talk about the “appropriate” filter, both the announcer and the receiver of the route must be taken into account. Suppose that the route server receives an announcement from client A, and the route server is considering it for the Loc-RIB of client B. The filters that should be applied are the same that would be used in the full mesh scenario, i.e., first the `Out' filter of router A for announcements going to router B, and then the `In' filter of router B for announcements coming from router A.
We call “Export Policy” of a RS-client to the set of `Out' filters that the client would use if there was no route server. The same applies for the “Import Policy” of a RS-client and the set of `In' filters of the client if there was no route server.
It is also common to demand from a route server that it does not modify some BGP attributes (next-hop, as-path and MED) that are usually modified by standard BGP speakers before announcing a route.
The announcement processing model implemented by Quagga is shown in fig:rs-processing. The figure shows a mixture of RS-clients (B, C and D) with normal BGP peers (A). There are some details that worth additional comments:
Now we will describe the commands that have been added to quagga in order to support the route server features.
This command configures the peer given by peer, A.B.C.D or X:X::X:X as an RS-client.
Actually this command is not new, it already existed in standard Quagga. It enables the transparent mode for the specified peer. This means that some BGP attributes (as-path, next-hop and MED) of the routes announced to that peer are not modified.
With the route server patch, this command, apart from setting the transparent mode, creates a new Loc-RIB dedicated to the specified peer (those named `Loc-RIB for X' in Figure 10.4.). Starting from that moment, every announcement received by the route server will be also considered for the new Loc-RIB.
This set of commands can be used to specify the route-map that represents the Import or Export policy of a peer which is configured as a RS-client (with the previous command).
This is a new match statement for use in route-maps, enabling them to describe import/export policies. As we said before, an import/export policy represents a set of input/output filters of the RS-client. This statement makes possible that a single route-map represents the full set of filters that a BGP speaker would use for its different peers in a non-RS scenario.
The match peer statement has different semantics whether it is used inside an import or an export route-map. In the first case the statement matches if the address of the peer who sends the announce is the same that the address specified by (A.B.C.D|X:X::X:X). For export route-maps it matches when (A.B.C.D|X:X::X:X) is the address of the RS-Client into whose Loc-RIB the announce is going to be inserted (how the same export policy is applied before different Loc-RIBs is shown in Figure 10.4.).
This command (also used inside a route-map) jumps into a different route-map, whose name is specified by WORD. When the called route-map finishes, depending on its result the original route-map continues or not. Apart from being useful for making import/export route-maps easier to write, this command can also be used inside any normal (in or out) route-map.
Finally we are going to show how to configure a Quagga daemon to act as a Route Server. For this purpose we are going to present a scenario without route server, and then we will show how to use the configurations of the BGP routers to generate the configuration of the route server.
All the configuration files shown in this section have been taken from scenarios which were tested using the VNUML tool VNUML.
We will suppose that our initial scenario is an exchange point with three BGP capable routers, named RA, RB and RC. Each of the BGP speakers generates some routes (with the network command), and establishes BGP peerings against the other two routers. These peerings have In and Out route-maps configured, named like “PEER-X-IN” or “PEER-X-OUT”. For example the configuration file for router RA could be the following:
#Configuration for router 'RA' ! hostname RA password **** ! router bgp 65001 no bgp default ipv4-unicast neighbor 2001:0DB8::B remote-as 65002 neighbor 2001:0DB8::C remote-as 65003 ! address-family ipv6 network 2001:0DB8:AAAA:1::/64 network 2001:0DB8:AAAA:2::/64 network 2001:0DB8:0000:1::/64 network 2001:0DB8:0000:2::/64 neighbor 2001:0DB8::B activate neighbor 2001:0DB8::B soft-reconfiguration inbound neighbor 2001:0DB8::B route-map PEER-B-IN in neighbor 2001:0DB8::B route-map PEER-B-OUT out neighbor 2001:0DB8::C activate neighbor 2001:0DB8::C soft-reconfiguration inbound neighbor 2001:0DB8::C route-map PEER-C-IN in neighbor 2001:0DB8::C route-map PEER-C-OUT out exit-address-family ! ipv6 prefix-list COMMON-PREFIXES seq 5 permit 2001:0DB8:0000::/48 ge 64 le 64 ipv6 prefix-list COMMON-PREFIXES seq 10 deny any ! ipv6 prefix-list PEER-A-PREFIXES seq 5 permit 2001:0DB8:AAAA::/48 ge 64 le 64 ipv6 prefix-list PEER-A-PREFIXES seq 10 deny any ! ipv6 prefix-list PEER-B-PREFIXES seq 5 permit 2001:0DB8:BBBB::/48 ge 64 le 64 ipv6 prefix-list PEER-B-PREFIXES seq 10 deny any ! ipv6 prefix-list PEER-C-PREFIXES seq 5 permit 2001:0DB8:CCCC::/48 ge 64 le 64 ipv6 prefix-list PEER-C-PREFIXES seq 10 deny any ! route-map PEER-B-IN permit 10 match ipv6 address prefix-list COMMON-PREFIXES set metric 100 route-map PEER-B-IN permit 20 match ipv6 address prefix-list PEER-B-PREFIXES set community 65001:11111 ! route-map PEER-C-IN permit 10 match ipv6 address prefix-list COMMON-PREFIXES set metric 200 route-map PEER-C-IN permit 20 match ipv6 address prefix-list PEER-C-PREFIXES set community 65001:22222 ! route-map PEER-B-OUT permit 10 match ipv6 address prefix-list PEER-A-PREFIXES ! route-map PEER-C-OUT permit 10 match ipv6 address prefix-list PEER-A-PREFIXES ! line vty !
To convert the initial scenario into one with route server, first we must modify the configuration of routers RA, RB and RC. Now they must not peer between them, but only with the route server. For example, RA's configuration would turn into:
# Configuration for router 'RA' ! hostname RA password **** ! router bgp 65001 no bgp default ipv4-unicast neighbor 2001:0DB8::FFFF remote-as 65000 ! address-family ipv6 network 2001:0DB8:AAAA:1::/64 network 2001:0DB8:AAAA:2::/64 network 2001:0DB8:0000:1::/64 network 2001:0DB8:0000:2::/64 neighbor 2001:0DB8::FFFF activate neighbor 2001:0DB8::FFFF soft-reconfiguration inbound exit-address-family ! line vty !
Which is logically much simpler than its initial configuration, as it now maintains only one BGP peering and all the filters (route-maps) have disappeared.
As we said when we described the functions of a route server (see Description of the Route Server model), it is in charge of all the route filtering. To achieve that, the In and Out filters from the RA, RB and RC configurations must be converted into Import and Export policies in the route server.
This is a fragment of the route server configuration (we only show the policies for client RA):
# Configuration for Route Server ('RS') ! hostname RS password ix ! bgp multiple-instance ! router bgp 65000 view RS no bgp default ipv4-unicast neighbor 2001:0DB8::A remote-as 65001 neighbor 2001:0DB8::B remote-as 65002 neighbor 2001:0DB8::C remote-as 65003 ! address-family ipv6 neighbor 2001:0DB8::A activate neighbor 2001:0DB8::A route-server-client neighbor 2001:0DB8::A route-map RSCLIENT-A-IMPORT import neighbor 2001:0DB8::A route-map RSCLIENT-A-EXPORT export neighbor 2001:0DB8::A soft-reconfiguration inbound neighbor 2001:0DB8::B activate neighbor 2001:0DB8::B route-server-client neighbor 2001:0DB8::B route-map RSCLIENT-B-IMPORT import neighbor 2001:0DB8::B route-map RSCLIENT-B-EXPORT export neighbor 2001:0DB8::B soft-reconfiguration inbound neighbor 2001:0DB8::C activate neighbor 2001:0DB8::C route-server-client neighbor 2001:0DB8::C route-map RSCLIENT-C-IMPORT import neighbor 2001:0DB8::C route-map RSCLIENT-C-EXPORT export neighbor 2001:0DB8::C soft-reconfiguration inbound exit-address-family ! ipv6 prefix-list COMMON-PREFIXES seq 5 permit 2001:0DB8:0000::/48 ge 64 le 64 ipv6 prefix-list COMMON-PREFIXES seq 10 deny any ! ipv6 prefix-list PEER-A-PREFIXES seq 5 permit 2001:0DB8:AAAA::/48 ge 64 le 64 ipv6 prefix-list PEER-A-PREFIXES seq 10 deny any ! ipv6 prefix-list PEER-B-PREFIXES seq 5 permit 2001:0DB8:BBBB::/48 ge 64 le 64 ipv6 prefix-list PEER-B-PREFIXES seq 10 deny any ! ipv6 prefix-list PEER-C-PREFIXES seq 5 permit 2001:0DB8:CCCC::/48 ge 64 le 64 ipv6 prefix-list PEER-C-PREFIXES seq 10 deny any ! route-map RSCLIENT-A-IMPORT permit 10 match peer 2001:0DB8::B call A-IMPORT-FROM-B route-map RSCLIENT-A-IMPORT permit 20 match peer 2001:0DB8::C call A-IMPORT-FROM-C ! route-map A-IMPORT-FROM-B permit 10 match ipv6 address prefix-list COMMON-PREFIXES set metric 100 route-map A-IMPORT-FROM-B permit 20 match ipv6 address prefix-list PEER-B-PREFIXES set community 65001:11111 ! route-map A-IMPORT-FROM-C permit 10 match ipv6 address prefix-list COMMON-PREFIXES set metric 200 route-map A-IMPORT-FROM-C permit 20 match ipv6 address prefix-list PEER-C-PREFIXES set community 65001:22222 ! route-map RSCLIENT-A-EXPORT permit 10 match peer 2001:0DB8::B match ipv6 address prefix-list PEER-A-PREFIXES route-map RSCLIENT-A-EXPORT permit 20 match peer 2001:0DB8::C match ipv6 address prefix-list PEER-A-PREFIXES ! ... ... ...
If you compare the initial configuration of RA with the route server configuration above, you can see how easy it is to generate the Import and Export policies for RA from the In and Out route-maps of RA's original configuration.
When there was no route server, RA maintained two peerings, one with RB and another with RC. Each of this peerings had an In route-map configured. To build the Import route-map for client RA in the route server, simply add route-map entries following this scheme:
route-map <NAME> permit 10 match peer <Peer Address> call <In Route-Map for this Peer> route-map <NAME> permit 20 match peer <Another Peer Address> call <In Route-Map for this Peer>
This is exactly the process that has been followed to generate the route-map RSCLIENT-A-IMPORT. The route-maps that are called inside it (A-IMPORT-FROM-B and A-IMPORT-FROM-C) are exactly the same than the In route-maps from the original configuration of RA (PEER-B-IN and PEER-C-IN), only the name is different.
The same could have been done to create the Export policy for RA (route-map RSCLIENT-A-EXPORT), but in this case the original Out route-maps where so simple that we decided not to use the call WORD commands, and we integrated all in a single route-map (RSCLIENT-A-EXPORT).
The Import and Export policies for RB and RC are not shown, but the process would be identical.
The current version of the route server patch only allows to specify a route-map for import and export policies, while in a standard BGP speaker apart from route-maps there are other tools for performing input and output filtering (access-lists, community-lists, ...). But this does not represent any limitation, as all kinds of filters can be included in import/export route-maps. For example suppose that in the non-route-server scenario peer RA had the following filters configured for input from peer B:
neighbor 2001:0DB8::B prefix-list LIST-1 in neighbor 2001:0DB8::B filter-list LIST-2 in neighbor 2001:0DB8::B route-map PEER-B-IN in ... ... route-map PEER-B-IN permit 10 match ipv6 address prefix-list COMMON-PREFIXES set local-preference 100 route-map PEER-B-IN permit 20 match ipv6 address prefix-list PEER-B-PREFIXES set community 65001:11111
It is posible to write a single route-map which is equivalent to the three filters (the community-list, the prefix-list and the route-map). That route-map can then be used inside the Import policy in the route server. Lets see how to do it:
neighbor 2001:0DB8::A route-map RSCLIENT-A-IMPORT import ... ! ... route-map RSCLIENT-A-IMPORT permit 10 match peer 2001:0DB8::B call A-IMPORT-FROM-B ... ... ! route-map A-IMPORT-FROM-B permit 1 match ipv6 address prefix-list LIST-1 match as-path LIST-2 on-match goto 10 route-map A-IMPORT-FROM-B deny 2 route-map A-IMPORT-FROM-B permit 10 match ipv6 address prefix-list COMMON-PREFIXES set local-preference 100 route-map A-IMPORT-FROM-B permit 20 match ipv6 address prefix-list PEER-B-PREFIXES set community 65001:11111 ! ... ...
The route-map A-IMPORT-FROM-B is equivalent to the three filters (LIST-1, LIST-2 and PEER-B-IN). The first entry of route-map A-IMPORT-FROM-B (sequence number 1) matches if and only if both the prefix-list LIST-1 and the filter-list LIST-2 match. If that happens, due to the “on-match goto 10” statement the next route-map entry to be processed will be number 10, and as of that point route-map A-IMPORT-FROM-B is identical to PEER-B-IN. If the first entry does not match, `on-match goto 10” will be ignored and the next processed entry will be number 2, which will deny the route.
Thus, the result is the same that with the three original filters, i.e., if either LIST-1 or LIST-2 rejects the route, it does not reach the route-map PEER-B-IN. In case both LIST-1 and LIST-2 accept the route, it passes to PEER-B-IN, which can reject, accept or modify the route.
vtysh is integrated shell of Quagga software.
To use vtysh please specify —enable-vtysh to configure script. To use PAM for authentication use —with-libpam option to configure script.
vtysh only searches /etc/quagga path for vtysh.conf which is the vtysh configuration file. Vtysh does not search current directory for configuration file because the file includes user authentication settings.
Currently, vtysh.conf has only two commands.
With this set, user foo does not need password authentication for user vtysh. With PAM vtysh uses PAM authentication mechanism.
If vtysh is compiled without PAM authentication, every user can use vtysh without authentication. vtysh requires read/write permission to the various daemons vty sockets, this can be accomplished through use of unix groups and the –enable-vty-group configure option.
Write out integrated Quagga.conf file when 'write file' is issued.
This command controls the behaviour of vtysh when it is told to write out the configuration. Per default, vtysh will instruct each daemon to write out their own config files when write file is issued. However, if service integrated-vtysh-config is set, when write file is issued, vtysh will instruct the daemons will write out a Quagga.conf with all daemons' commands integrated into it.
Vtysh per default behaves as if write-conf daemon is set. Note that both may be set at same time if one wishes to have both Quagga.conf and daemon specific files written out. Further, note that the daemons are hard-coded to first look for the integrated Quagga.conf file before looking for their own file.
We recommend you do not mix the use of the two types of files. Further, it is better not to use the integrated Quagga.conf file, as any syntax error in it can lead to /all/ of your daemons being unable to start up. Per daemon files are more robust as impact of errors in configuration are limited to the daemon in whose file the error is made.
Quagga provides many very flexible filtering features. Filtering is used for both input and output of the routing information. Once filtering is defined, it can be applied in any direction.
Basic filtering is done by access-list
as shown in the
following example.
access-list filter deny 10.0.0.0/9 access-list filter permit 10.0.0.0/8
ip prefix-list provides the most powerful prefix based filtering mechanism. In addition to access-list functionality, ip prefix-list has prefix length range specification and sequential number specification. You can add or delete prefix based filters to arbitrary points of prefix-list using sequential number specification.
If no ip prefix-list is specified, it acts as permit. If ip prefix-list is defined, and no match is found, default deny is applied.
You can create ip prefix-list using above commands.
- seq
- seq number can be set either automatically or manually. In the case that sequential numbers are set manually, the user may pick any number less than 4294967295. In the case that sequential number are set automatically, the sequential number will increase by a unit of five (5) per list. If a list with no specified sequential number is created after a list with a specified sequential number, the list will automatically pick the next multiple of five (5) as the list number. For example, if a list with number 2 already exists and a new list with no specified number is created, the next list will be numbered 5. If lists 2 and 7 already exist and a new list with no specified number is created, the new list will be numbered 10.
- le
- le command specifies prefix length. The prefix list will be applied if the prefix length is less than or equal to the le prefix length.
- ge
- ge command specifies prefix length. The prefix list will be applied if the prefix length is greater than or equal to the ge prefix length.
Less than or equal to prefix numbers and greater than or equal to prefix numbers can be used together. The order of the le and ge commands does not matter.
If a prefix list with a different sequential number but with the exact same rules as a previous list is created, an error will result. However, in the case that the sequential number and the rules are exactly similar, no error will result.
If a list with the same sequential number as a previous list is created, the new list will overwrite the old list.
Matching of IP Prefix is performed from the smaller sequential number to the larger. The matching will stop once any rule has been applied.
In the case of no le or ge command, the prefix length must match exactly the length specified in the prefix list.
Descriptions may be added to prefix lists. This command adds a description to the prefix list.
Deletes the description from a prefix list. It is possible to use the command without the full description.
With this command, the IP prefix list sequential number is displayed. This is the default behavior.
With this command, the IP prefix list sequential number is not displayed.
Show IP prefix list can be used with a prefix list name and sequential number.
If the command longer is used, all prefix lists with prefix lengths equal to or longer than the specified length will be displayed. If the command first match is used, the first prefix length match will be displayed.
Clears the counters of all IP prefix lists. Clear IP Prefix List can be used with a specified name and prefix.
Route map is a very useful function in zebra. There is a match and set statement permitted in a route map.
route-map test permit 10 match ip address 10 set local-preference 200
This means that if a route matches ip access-list number 10 it's local-preference value is set to 200.
Set the BGP-4+ global IPv6 nexthop address.
Set the BGP-4+ link local IPv6 nexthop address.
Quagga fully supports IPv6 routing. As described so far, Quagga supports
RIPng, OSPFv3 and BGP-4+. You can give IPv6 addresses to an interface
and configure static IPv6 routing information. Quagga IPv6 also provides
automatic address configuration via a feature called address
auto configuration
. To do it, the router must send router advertisement
messages to the all nodes that exist on the network.
Configuring the IPv6 prefix to include in router advertisements. Several prefix specific optional parameters and flags may follow:
- valid-lifetime - the length of time in seconds during what the prefix is valid for the purpose of on-link determination. Value infinite represents infinity (i.e. a value of all one bits (
0xffffffff
)).Range:
<0-4294967295>
Default:2592000
- preferred-lifetime - the length of time in seconds during what addresses generated from the prefix remain preferred. Value infinite represents infinity.
Range:
<0-4294967295>
Default:604800
- off-link - indicates that advertisement makes no statement about on-link or off-link properties of the prefix.
Default: not set, i.e. this prefix can be used for on-link determination.
- no-autoconfig - indicates to hosts on the local link that the specified prefix cannot be used for IPv6 autoconfiguration.
Default: not set, i.e. prefix can be used for autoconfiguration.
The maximum time allowed between sending unsolicited multicast router advertisements from the interface, in seconds. Must be no less than 3 seconds.
Default:
600
The value to be placed in the Router Lifetime field of router advertisements sent from the interface, in seconds. Indicates the usefulness of the router as a default router on this interface. Setting the value to zero indicates that the router should not be considered a default router on this interface. Must be either zero or between value specified with ipv6 nd ra-interval (or default) and 9000 seconds.
Default:
1800
The value to be placed in the Reachable Time field in the Router Advertisement messages sent by the router, in milliseconds. The configured time enables the router to detect unavailable neighbors. The value zero means unspecified (by this router). Must be no greater than
3,600,000
milliseconds (1 hour).Default:
0
Set/unset flag in IPv6 router advertisements which indicates to hosts that they should use managed (stateful) protocol for addresses autoconfiguration in addition to any addresses autoconfigured using stateless address autoconfiguration.
Default: not set
Set/unset flag in IPv6 router advertisements which indicates to hosts that they should use administered (stateful) protocol to obtain autoconfiguration information other than addresses.
Default: not set
interface eth0 no ipv6 nd suppress-ra ipv6 nd prefix 2001:0DB8:5009::/64
For more information see RFC2462 (IPv6 Stateless Address Autoconfiguration) and RFC2461 (Neighbor Discovery for IP Version 6 (IPv6)).
There are several different methods for reading kernel routing table information, updating kernel routing tables, and for looking up interfaces.
netlink
. It makes asynchronous
communication between kernel and Quagga possible, similar to a routing
socket on BSD systems.
Before you use this feature, be sure to select (in kernel configuration) the kernel/netlink support option 'Kernel/User network link driver' and 'Routing messages'.
Today, the /dev/route special device file is obsolete. Netlink communication is done by reading/writing over netlink socket.
After the kernel configuration, please reconfigure and rebuild Quagga. You can use netlink as a dynamic routing update channel between Quagga and the kernel.
SNMP (Simple Network Managing Protocol) is a widely implemented feature for collecting network information from router and/or host. Quagga itself does not support SNMP agent (server daemon) functionality but is able to connect to a SNMP agent using the SMUX protocol (RFC1227) and make the routing protocol MIBs available through it.
There are several SNMP agent which support SMUX. We recommend to use the latest
version of net-snmp
which was formerly known as ucd-snmp
.
It is free and open software and available at http://www.net-snmp.org/
and as binary package for most Linux distributions.
net-snmp
has to be compiled with --with-mib-modules=smux
to
be able to accept connections from Quagga.
To enable SMUX protocol support, Quagga must have been build with the
--enable-snmp
option.
A separate connection has then to be established between between the SNMP agent (snmpd) and each of the Quagga daemons. This connections each use different OID numbers and passwords. Be aware that this OID number is not the one that is used in queries by clients, it is solely used for the intercommunication of the daemons.
In the following example the ospfd daemon will be connected to the snmpd daemon using the password "quagga_ospfd". For testing it is recommending to take exactly the below snmpd.conf as wrong access restrictions can be hard to debug.
/etc/snmp/snmpd.conf: # # example access restrictions setup # com2sec readonly default public group MyROGroup v1 readonly view all included .1 80 access MyROGroup "" any noauth exact all none none # # the following line is relevant for Quagga # smuxpeer .1.3.6.1.4.1.3317.1.2.5 quagga_ospfd /etc/quagga/ospf: ! ... the rest of ospfd.conf has been omitted for clarity ... ! smux peer .1.3.6.1.4.1.3317.1.2.5 quagga_ospfd !
After restarting snmpd and quagga, a successful connection can be verified in the syslog and by querying the SNMP daemon:
snmpd[12300]: [smux_accept] accepted fd 12 from 127.0.0.1:36255 snmpd[12300]: accepted smux peer: \ oid GNOME-PRODUCT-ZEBRA-MIB::ospfd, quagga-0.96.5 # snmpwalk -c public -v1 localhost .1.3.6.1.2.1.14.1.1 OSPF-MIB::ospfRouterId.0 = IpAddress: 192.168.42.109
Be warned that the current version (5.1.1) of the Net-SNMP daemon writes a line
for every SNMP connect to the syslog which can lead to enormous log file sizes.
If that is a problem you should consider to patch snmpd and comment out the
troublesome snmp_log()
line in the function
netsnmp_agent_check_packet()
in agent/snmp_agent.c
.
The following OID numbers are used for the interprocess communication of snmpd and the Quagga daemons. Sadly, SNMP has not been implemented in all daemons yet.
(OIDs below .iso.org.dod.internet.private.enterprises) zebra .1.3.6.1.4.1.3317.1.2.1 .gnome.gnomeProducts.zebra.zserv bgpd .1.3.6.1.4.1.3317.1.2.2 .gnome.gnomeProducts.zebra.bgpd ripd .1.3.6.1.4.1.3317.1.2.3 .gnome.gnomeProducts.zebra.ripd ospfd .1.3.6.1.4.1.3317.1.2.5 .gnome.gnomeProducts.zebra.ospfd ospf6d .1.3.6.1.4.1.3317.1.2.6 .gnome.gnomeProducts.zebra.ospf6d
The following OID numbers are used for querying the SNMP daemon by a client:
zebra .1.3.6.1.2.1.4.24 .iso.org.dot.internet.mgmt.mib-2.ip.ipForward ospfd .1.3.6.1.2.1.14 .iso.org.dot.internet.mgmt.mib-2.ospf bgpd .1.3.6.1.2.1.15 .iso.org.dot.internet.mgmt.mib-2.bgp ripd .1.3.6.1.2.1.23 .iso.org.dot.internet.mgmt.mib-2.rip2 ospf6d .1.3.6.1.3.102 .iso.org.dod.internet.experimental.ospfv3
The following syntax is understood by the Quagga daemons for configuring SNMP:
Zebra Protocol is a protocol which is used between protocol daemon and zebra. Each protocol daemon sends selected routes to zebra daemon. Then zebra manages which route is installed into the forwarding table.
Zebra Protocol is a TCP-based protocol. Below is common header of Zebra Protocol.
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length (2) | Command (1) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Length is total packet length including this header length. So minimum length is three. Command is Zebra Protocol command.
ZEBRA_INTERFACE_ADD 1 ZEBRA_INTERFACE_DELETE 2 ZEBRA_INTERFACE_ADDRESS_ADD 3 ZEBRA_INTERFACE_ADDRESS_DELETE 4 ZEBRA_INTERFACE_UP 5 ZEBRA_INTERFACE_DOWN 6 ZEBRA_IPV4_ROUTE_ADD 7 ZEBRA_IPV4_ROUTE_DELETE 8 ZEBRA_IPV6_ROUTE_ADD 9 ZEBRA_IPV6_ROUTE_DELETE 10 ZEBRA_REDISTRIBUTE_ADD 11 ZEBRA_REDISTRIBUTE_DELETE 12 ZEBRA_REDISTRIBUTE_DEFAULT_ADD 13 ZEBRA_REDISTRIBUTE_DEFAULT_DELETE 14 ZEBRA_IPV4_NEXTHOP_LOOKUP 15 ZEBRA_IPV6_NEXTHOP_LOOKUP 16
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Flags | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Quagga can dump routing protocol packet into file with a binary format (see Dump BGP packets and table).
It seems to be better that we share the MRT's header format for backward compatibility with MRT's dump logs. We should also define the binary format excluding the header, because we must support both IP v4 and v6 addresses as socket addresses and / or routing entries.
In the last meeting, we discussed to have a version field in the header. But Masaki told us that we can define new `type' value rather than having a `version' field, and it seems to be better because we don't need to change header format.
Here is the common header format. This is same as that of MRT.
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Time | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Subtype | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If `type' is PROTOCOL_BGP4MP, `subtype' is BGP4MP_STATE_CHANGE, and Address Family == IP (version 4)
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source AS number | Destination AS number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface Index | Address Family | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Old State | New State | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where State is the value defined in RFC1771.
If `type' is PROTOCOL_BGP4MP, `subtype' is BGP4MP_STATE_CHANGE, and Address Family == IP version 6
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source AS number | Destination AS number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface Index | Address Family | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Old State | New State | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If `type' is PROTOCOL_BGP4MP, `subtype' is BGP4MP_MESSAGE, and Address Family == IP (version 4)
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source AS number | Destination AS number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface Index | Address Family | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BGP Message Packet | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where BGP Message Packet is the whole contents of the BGP4 message including header portion.
If `type' is PROTOCOL_BGP4MP, `subtype' is BGP4MP_MESSAGE, and Address Family == IP version 6
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source AS number | Destination AS number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Interface Index | Address Family | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Source IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Destination IP address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BGP Message Packet | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If `type' is PROTOCOL_BGP4MP, `subtype' is BGP4MP_ENTRY, and Address Family == IP (version 4)
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | View # | Status | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Time Last Change | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Family | SAFI | Next-Hop-Len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Hop Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Prefix Length | Address Prefix [variable] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Attribute Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BGP Attribute [variable length] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
If `type' is PROTOCOL_BGP4MP, `subtype' is BGP4MP_ENTRY, and Address Family == IP version 6
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | View # | Status | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Time Last Change | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Family | SAFI | Next-Hop-Len | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Hop Address | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Hop Address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Hop Address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Next Hop Address (Cont'd) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Prefix Length | Address Prefix [variable] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Address Prefix (cont'd) [variable] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Attribute Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | BGP Attribute [variable length] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
BGP4 Attribute must not contain MP_UNREACH_NLRI. If BGP Attribute has MP_REACH_NLRI field, it must has zero length NLRI, e.g., MP_REACH_NLRI has only Address Family, SAFI and next-hop values.
If `type' is PROTOCOL_BGP4MP and `subtype' is BGP4MP_SNAPSHOT,
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | View # | File Name [variable] | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The file specified in "File Name" contains all routing entries, which are in the format of “subtype == BGP4MP_ENTRY”.
Constants: /* type value */ #define MSG_PROTOCOL_BGP4MP 16 /* subtype value */ #define BGP4MP_STATE_CHANGE 0 #define BGP4MP_MESSAGE 1 #define BGP4MP_ENTRY 2 #define BGP4MP_SNAPSHOT 3
access-class
access-list: Basic Config Commandsaccess-list
name deny
ipv4-network: IP Access Listaccess-list
name permit
ipv4-network: IP Access Listaggregate-address
A.B.C.D/M: Route Aggregationaggregate-address
A.B.C.D/M as-set
: Route Aggregationaggregate-address
A.B.C.D/M summary-only
: Route Aggregationarea <0-4294967295> authentication
: OSPF areaarea <0-4294967295> authentication message-digest
: OSPF areaarea <0-4294967295> export-list NAME
: OSPF areaarea <0-4294967295> filter-list prefix NAME in
: OSPF areaarea <0-4294967295> filter-list prefix NAME out
: OSPF areaarea <0-4294967295> import-list NAME
: OSPF areaarea <0-4294967295> range
a.b.c.d/m: OSPF areaarea <0-4294967295> shortcut
: OSPF areaarea <0-4294967295> stub
: OSPF areaarea <0-4294967295> stub no-summary
: OSPF areaarea <0-4294967295> virtual-link
a.b.c.d: OSPF areaarea
a.b.c.d authentication
: OSPF areaarea
a.b.c.d authentication message-digest
: OSPF areaarea
a.b.c.d default-cost <0-16777215>
: OSPF areaarea
a.b.c.d export-list NAME
: OSPF areaarea
a.b.c.d filter-list prefix NAME in
: OSPF areaarea
a.b.c.d filter-list prefix NAME out
: OSPF areaarea
a.b.c.d import-list NAME
: OSPF areaarea
a.b.c.d range
a.b.c.d/m: OSPF areaarea
a.b.c.d range IPV4_PREFIX not-advertise
: OSPF areaarea
a.b.c.d range IPV4_PREFIX substitute IPV4_PREFIX
: OSPF areaarea
a.b.c.d shortcut
: OSPF areaarea
a.b.c.d stub
: OSPF areaarea
a.b.c.d stub no-summary
: OSPF areaarea
a.b.c.d virtual-link
a.b.c.d: OSPF areaauto-cost refrence-bandwidth <1-4294967>
: OSPF routerbandwidth <1-10000000>
: Interface Commandsbanner motd default
: Basic Config Commandsbgp cluster-id
a.b.c.d: Route Reflectorbgp config-type cisco
: Multiple instancebgp config-type zebra
: Multiple instancebgp multiple-instance
: Multiple instancebgp router-id
A.B.C.D: BGP routercall
WORD: Commands for configuring a Route Serverclear ip bgp
peer: More Show IP BGPclear ip bgp
peer soft in
: More Show IP BGPclear ip prefix-list
: Clear counter of ip prefix-listclear ip prefix-list
name: Clear counter of ip prefix-listclear ip prefix-list
name a.b.c.d/m: Clear counter of ip prefix-listconfigure terminal
: Terminal Mode Commandsdebug event
: More Show IP BGPdebug keepalive
: More Show IP BGPdebug ospf ism
: Debugging OSPFdebug ospf ism (status|events|timers)
: Debugging OSPFdebug ospf lsa
: Debugging OSPFdebug ospf lsa (generate|flooding|refresh)
: Debugging OSPFdebug ospf nsm
: Debugging OSPFdebug ospf nsm (status|events|timers)
: Debugging OSPFdebug ospf packet (hello|dd|ls-request|ls-update|ls-ack|all) (send|recv) [detail]
: Debugging OSPFdebug ospf zebra
: Debugging OSPFdebug ospf zebra (interface|redistribute)
: Debugging OSPFdebug rip events
: RIP Debug Commandsdebug rip packet
: RIP Debug Commandsdebug rip zebra
: RIP Debug Commandsdebug ripng events
: ripngd Terminal Mode Commandsdebug ripng packet
: ripngd Terminal Mode Commandsdebug ripng zebra
: ripngd Terminal Mode Commandsdebug update
: More Show IP BGPdefault-information originate
: Redistribute routes to OSPFdefault-information originate
: How to Announce RIP routedefault-information originate always
: Redistribute routes to OSPFdefault-information originate always metric <0-16777214>
: Redistribute routes to OSPFdefault-information originate always metric <0-16777214> metric-type (1|2)
: Redistribute routes to OSPFdefault-information originate always metric <0-16777214> metric-type (1|2) route-map
word: Redistribute routes to OSPFdefault-information originate metric <0-16777214>
: Redistribute routes to OSPFdefault-information originate metric <0-16777214> metric-type (1|2)
: Redistribute routes to OSPFdefault-information originate metric <0-16777214> metric-type (1|2) route-map
word: Redistribute routes to OSPFdefault-metric <0-16777214>
: Redistribute routes to OSPFdefault-metric <1-16>
: RIP Metric Manipulationdescription
description ...
: Interface Commandsdistance <1-255>
: Redistribute routes to OSPFdistance <1-255>
: RIP distancedistance <1-255>
A.B.C.D/M: BGP distancedistance <1-255>
A.B.C.D/M: RIP distancedistance <1-255>
A.B.C.D/M access-list: RIP distancedistance <1-255>
A.B.C.D/M word: BGP distancedistance bgp <1-255> <1-255> <1-255>
: BGP distancedistance ospf (intra-area|inter-area|external) <1-255>
: Redistribute routes to OSPFdistribute-list
access_list (in|out)
ifname: ripngd Filtering Commandsdistribute-list
access_list direct ifname: Filtering RIP Routesdistribute-list NAME out (kernel|connected|static|rip|ospf
: Redistribute routes to OSPFdistribute-list prefix
prefix_list (in|out)
ifname: Filtering RIP Routesdump bgp all
path: Dump BGP packets and tabledump bgp all
path interval: Dump BGP packets and tabledump bgp routes
path: Dump BGP packets and tabledump bgp updates
path: Dump BGP packets and tabledump bgp updates
path interval: Dump BGP packets and tableenable password
password: Basic Config Commandsexec-timeout
minute: Basic Config Commandsexec-timeout
minute second: Basic Config Commandsflush_timer
time: ripngd Configurationhostname
hostname: Basic Config Commandsinterface
ifname: Interface Commandsinterface
ifname area
area: OSPF6 routerip address
address/prefix: Interface Commandsip address
address/prefix secondary
: Interface Commandsip as-path access-list
word (permit|deny)
line: AS Path Access Listip community-list <1-99> (permit|deny)
community: Numbered BGP Community Listsip community-list <100-199> (permit|deny)
community: Numbered BGP Community Listsip community-list expanded
name (permit|deny)
line: BGP Community Listsip community-list
name (permit|deny)
community: Numbered BGP Community Listsip community-list standard
name (permit|deny)
community: BGP Community Listsip extcommunity-list expanded
name (permit|deny)
line: BGP Extended Community Listsip extcommunity-list standard
name (permit|deny)
extcommunity: BGP Extended Community Listsip ospf authentication-key AUTH_KEY
: OSPF interfaceip ospf cost <1-65535>
: OSPF interfaceip ospf dead-interval <1-65535>
: OSPF interfaceip ospf hello-interval <1-65535>
: OSPF interfaceip ospf message-digest-key KEYID md5 KEY
: OSPF interfaceip ospf network (broadcast|non-broadcast|point-to-multipoint|point-to-point)
: OSPF interfaceip ospf priority <0-255>
: OSPF interfaceip ospf retransmit-interval <1-65535>
: OSPF interfaceip ospf transmit-delay
: OSPF interfaceip prefix-list
name (permit|deny)
prefix [le
len] [ge
len]
: IP Prefix Listip prefix-list
name description
desc: ip prefix-list descriptionip prefix-list
name seq
number (permit|deny)
prefix [le
len] [ge
len]
: IP Prefix Listip prefix-list sequence-number
: ip prefix-list sequential number controlip rip authentication key-chain
key-chain: RIP Authenticationip rip authentication mode md5
: RIP Authenticationip rip authentication mode text
: RIP Authenticationip rip authentication string
string: RIP Authenticationip rip receive version
version: RIP Configurationip rip send version
version: RIP Configurationip route
network gateway: Static Route Commandsip route
network gateway distance: Static Route Commandsip route
network netmask gateway: Static Route Commandsip split-horizon
: RIP Configurationip6 address
address/prefix: Interface Commandsipv6 nd managed-config-flag
: Router Advertisementipv6 nd other-config-flag
: Router Advertisementipv6 nd prefix
ipv6prefix [
valid-lifetime] [
preferred-lifetime] [off-link] [no-autconfig]
: Router Advertisementipv6 nd ra-interval SECONDS
: Router Advertisementipv6 nd ra-lifetime SECONDS
: Router Advertisementipv6 nd reachable-time MILLISECONDS
: Router Advertisementipv6 nd suppress-ra
: Router Advertisementipv6 ospf6 cost COST
: OSPF6 interfaceipv6 ospf6 dead-interval DEADINTERVAL
: OSPF6 interfaceipv6 ospf6 hello-interval HELLOINTERVAL
: OSPF6 interfaceipv6 ospf6 priority PRIORITY
: OSPF6 interfaceipv6 ospf6 retransmit-interval RETRANSMITINTERVAL
: OSPF6 interfaceipv6 ospf6 transmit-delay TRANSMITDELAY
: OSPF6 interfaceipv6 route
network gateway: Static Route Commandsipv6 route
network gateway distance: Static Route Commandsline vty
: Basic Config Commandslink-detect
: Interface Commandslist
: Terminal Mode Commandslog facility
facility: Basic Config Commandslog file
filename: Basic Config Commandslog file
filename level: Basic Config Commandslog monitor
: Basic Config Commandslog monitor
level: Basic Config Commandslog record-priority
: Basic Config Commandslog stdout
: Basic Config Commandslog stdout
level: Basic Config Commandslog syslog
: Basic Config Commandslog syslog
level: Basic Config Commandslog trap
level: Basic Config Commandslogmsg
level message: Terminal Mode Commandsmatch as-path
word: Using AS Path in Route Mapmatch aspath
as_path: Route Map Match Commandmatch community
community_list: Route Map Match Commandmatch community
word: BGP Community in Route Mapmatch community
word exact-match
: BGP Community in Route Mapmatch extcommunity
word: BGP Extended Communities in Route Mapmatch interface
word: RIP route-mapmatch ip address
access_list: Route Map Match Commandmatch ip address prefix-list
word: RIP route-mapmatch ip address
word: RIP route-mapmatch ip next-hop A.B.C.D
: RIP route-mapmatch ip next-hop
ipv4_addr: Route Map Match Commandmatch metric <0-4294967295>
: RIP route-mapmatch metric
metric: Route Map Match Commandmatch peer (A.B.C.D|X:X::X:X)
: Commands for configuring a Route Servermulticast
: Interface Commandsneigbor (A.B.C.D|X.X::X.X|peer-group) route-map WORD (import|export)
: Commands for configuring a Route Serverneighbor
a.b.c.d: RIP Configurationneighbor
A.B.C.D route-server-client
: Commands for configuring a Route Serverneighbor
peer default-originate
: BGP Peer commandsneighbor
peer description ...
: BGP Peer commandsneighbor
peer distribute-list
name [in|out]
: Peer filteringneighbor
peer dont-capability-negotiate
: Capability Negotiationneighbor
peer ebgp-multihop
: BGP Peer commandsneighbor
peer filter-list
name [in|out]
: Peer filteringneighbor
peer interface
ifname: BGP Peer commandsneighbor
peer maximum-prefix
number: BGP Peer commandsneighbor
peer next-hop-self
: BGP Peer commandsneighbor
peer override-capability
: Capability Negotiationneighbor
peer peer-group
word: BGP Peer Groupneighbor
peer port
port: BGP Peer commandsneighbor
peer prefix-list
name [in|out]
: Peer filteringneighbor
peer remote-as
asn: Defining Peerneighbor
peer route-map
name [in|out]
: Peer filteringneighbor
peer route-reflector-client
: Route Reflectorneighbor
peer send-community
: BGP Peer commandsneighbor
peer shutdown
: BGP Peer commandsneighbor
peer strict-capability-match
: Capability Negotiationneighbor
peer update-source
: BGP Peer commandsneighbor
peer version
version: BGP Peer commandsneighbor
peer weight
weight: BGP Peer commandsneighbor
peer-group route-server-client
: Commands for configuring a Route Serverneighbor
word peer-group
: BGP Peer Groupneighbor
X:X::X:X route-server-client
: Commands for configuring a Route Servernetwork
A.B.C.D/M: BGP routenetwork
a.b.c.d/m area
<0-4294967295>: OSPF routernetwork
a.b.c.d/m area
a.b.c.d: OSPF routernetwork
ifname: ripngd Configurationnetwork
ifname: RIP Configurationnetwork
network: ripngd Configurationnetwork
network: RIP Configurationno aggregate-address
A.B.C.D/M: Route Aggregationno area <0-4294967295> authentication
: OSPF areano area <0-4294967295> export-list NAME
: OSPF areano area <0-4294967295> filter-list prefix NAME in
: OSPF areano area <0-4294967295> filter-list prefix NAME out
: OSPF areano area <0-4294967295> import-list NAME
: OSPF areano area <0-4294967295> range
a.b.c.d/m: OSPF areano area <0-4294967295> shortcut
: OSPF areano area <0-4294967295> stub
: OSPF areano area <0-4294967295> stub no-summary
: OSPF areano area <0-4294967295> virtual-link
a.b.c.d: OSPF areano area
a.b.c.d authentication
: OSPF areano area
a.b.c.d default-cost <0-16777215>
: OSPF areano area
a.b.c.d export-list NAME
: OSPF areano area
a.b.c.d filter-list prefix NAME in
: OSPF areano area
a.b.c.d filter-list prefix NAME out
: OSPF areano area
a.b.c.d import-list NAME
: OSPF areano area
a.b.c.d range
a.b.c.d/m: OSPF areano area
a.b.c.d range IPV4_PREFIX not-advertise
: OSPF areano area
a.b.c.d range IPV4_PREFIX substitute IPV4_PREFIX
: OSPF areano area
a.b.c.d shortcut
: OSPF areano area
a.b.c.d stub
: OSPF areano area
a.b.c.d stub no-summary
: OSPF areano area
a.b.c.d virtual-link
a.b.c.d: OSPF areano auto-cost refrence-bandwidth
: OSPF routerno bandwidth <1-10000000>
: Interface Commandsno banner motd
: Basic Config Commandsno bgp multiple-instance
: Multiple instanceno debug event
: More Show IP BGPno debug keepalive
: More Show IP BGPno debug ospf ism
: Debugging OSPFno debug ospf ism (status|events|timers)
: Debugging OSPFno debug ospf lsa
: Debugging OSPFno debug ospf lsa (generate|flooding|refresh)
: Debugging OSPFno debug ospf nsm
: Debugging OSPFno debug ospf nsm (status|events|timers)
: Debugging OSPFno debug ospf packet (hello|dd|ls-request|ls-update|ls-ack|all) (send|recv) [detail]
: Debugging OSPFno debug ospf zebra
: Debugging OSPFno debug ospf zebra (interface|redistribute)
: Debugging OSPFno debug update
: More Show IP BGPno default-information originate
: Redistribute routes to OSPFno default-metric
: Redistribute routes to OSPFno default-metric <1-16>
: RIP Metric Manipulationno distance <1-255>
: Redistribute routes to OSPFno distance <1-255>
: RIP distanceno distance <1-255>
A.B.C.D/M: RIP distanceno distance <1-255>
A.B.C.D/M access-list: RIP distanceno distance ospf
: Redistribute routes to OSPFno distribute-list NAME out (kernel|connected|static|rip|ospf
: Redistribute routes to OSPFno exec-timeout
: Basic Config Commandsno ip address
address/prefix: Interface Commandsno ip address
address/prefix secondary
: Interface Commandsno ip as-path access-list
word: AS Path Access Listno ip as-path access-list
word (permit|deny)
line: AS Path Access Listno ip community-list expanded
name: BGP Community Listsno ip community-list
name: BGP Community Listsno ip community-list standard
name: BGP Community Listsno ip extcommunity-list expanded
name: BGP Extended Community Listsno ip extcommunity-list
name: BGP Extended Community Listsno ip extcommunity-list standard
name: BGP Extended Community Listsno ip ospf authentication-key
: OSPF interfaceno ip ospf cost
: OSPF interfaceno ip ospf dead-interval
: OSPF interfaceno ip ospf hello-interval
: OSPF interfaceno ip ospf message-digest-key
: OSPF interfaceno ip ospf network
: OSPF interfaceno ip ospf priority
: OSPF interfaceno ip ospf retransmit interval
: OSPF interfaceno ip ospf transmit-delay
: OSPF interfaceno ip prefix-list
name: IP Prefix Listno ip prefix-list
name description [
desc]
: ip prefix-list descriptionno ip prefix-list sequence-number
: ip prefix-list sequential number controlno ip rip authentication key-chain
key-chain: RIP Authenticationno ip rip authentication mode md5
: RIP Authenticationno ip rip authentication mode text
: RIP Authenticationno ip rip authentication string
string: RIP Authenticationno ip split-horizon
: RIP Configurationno ip6 address
address/prefix: Interface Commandsno ipv6 nd managed-config-flag
: Router Advertisementno ipv6 nd other-config-flag
: Router Advertisementno ipv6 nd ra-interval
: Router Advertisementno ipv6 nd ra-lifetime
: Router Advertisementno ipv6 nd reachable-time
: Router Advertisementno ipv6 nd suppress-ra
: Router Advertisementno link-detect
: Interface Commandsno log facility
: Basic Config Commandsno log file
: Basic Config Commandsno log monitor
: Basic Config Commandsno log record-priority
: Basic Config Commandsno log stdout
: Basic Config Commandsno log syslog
: Basic Config Commandsno log trap
: Basic Config Commandsno multicast
: Interface Commandsno neighbor
a.b.c.d: RIP Configurationno neighbor
peer default-originate
: BGP Peer commandsno neighbor
peer description ...
: BGP Peer commandsno neighbor
peer dont-capability-negotiate
: Capability Negotiationno neighbor
peer ebgp-multihop
: BGP Peer commandsno neighbor
peer interface
ifname: BGP Peer commandsno neighbor
peer maximum-prefix
number: BGP Peer commandsno neighbor
peer next-hop-self
: BGP Peer commandsno neighbor
peer override-capability
: Capability Negotiationno neighbor
peer route-reflector-client
: Route Reflectorno neighbor
peer shutdown
: BGP Peer commandsno neighbor
peer strict-capability-match
: Capability Negotiationno neighbor
peer update-source
: BGP Peer commandsno neighbor
peer weight
weight: BGP Peer commandsno network
A.B.C.D/M: BGP routeno network
a.b.c.d/m area
<0-4294967295>: OSPF routerno network
a.b.c.d/m area
a.b.c.d: OSPF routerno network
ifname: RIP Configurationno network
network: RIP Configurationno ospf abr-type
type: OSPF routerno ospf rfc1583compatibility
: OSPF routerno ospf router-id
: OSPF routerno passive interface
interface: OSPF routerno passive-interface
IFNAME: RIP Configurationno redistribute (kernel|connected|static|rip|bgp)
: Redistribute routes to OSPFno redistribute bgp
: How to Announce RIP routeno redistribute connected
: How to Announce RIP routeno redistribute kernel
: How to Announce RIP routeno redistribute ospf
: How to Announce RIP routeno redistribute static
: How to Announce RIP routeno route
a.b.c.d/m: How to Announce RIP routeno router bgp
asn: BGP routerno router ospf
: OSPF routerno router rip
: RIP Configurationno router zebra
: Redistribute routes to OSPFno shutdown
: Interface Commandsno smux peer
oid: MIB and command referenceno smux peer
oid password: MIB and command referenceno timers basic
: RIP Timersno timers spf
: OSPF routeroffset-list
access-list (in|out)
: RIP Metric Manipulationoffset-list
access-list (in|out)
ifname: RIP Metric Manipulationospf abr-type
type: OSPF routerospf rfc1583compatibility
: OSPF routerospf router-id
a.b.c.d: OSPF routerpassive interface
interface: OSPF routerpassive-interface (
IFNAME|default)
: RIP Configurationpassword
password: Basic Config Commandsredistribute (kernel|connected|static|rip|bgp)
: Redistribute routes to OSPFredistribute (kernel|connected|static|rip|bgp) metric <0-16777214>
: Redistribute routes to OSPFredistribute (kernel|connected|static|rip|bgp) metric <0-16777214> route-map
word: Redistribute routes to OSPFredistribute (kernel|connected|static|rip|bgp) metric-type (1|2)
: Redistribute routes to OSPFredistribute (kernel|connected|static|rip|bgp) metric-type (1|2) metric <0-16777214>
: Redistribute routes to OSPFredistribute (kernel|connected|static|rip|bgp) metric-type (1|2) metric <0-16777214> route-map
word: Redistribute routes to OSPFredistribute (kernel|connected|static|rip|bgp) metric-type (1|2) route-map
word: Redistribute routes to OSPFredistribute (kernel|connected|static|rip|bgp)
route-map: Redistribute routes to OSPFredistribute bgp
: How to Announce RIP routeredistribute bgp metric <0-16>
: How to Announce RIP routeredistribute bgp route-map
route-map: How to Announce RIP routeredistribute connected
: Redistribute to BGPredistribute connected
: Redistribute routes to OSPF6redistribute connected
: How to Announce RIP routeredistribute connected metric <0-16>
: How to Announce RIP routeredistribute connected route-map
route-map: How to Announce RIP routeredistribute kernel
: Redistribute to BGPredistribute kernel
: How to Announce RIP routeredistribute kernel metric <0-16>
: How to Announce RIP routeredistribute kernel route-map
route-map: How to Announce RIP routeredistribute ospf
: Redistribute to BGPredistribute ospf
: How to Announce RIP routeredistribute ospf metric <0-16>
: How to Announce RIP routeredistribute ospf route-map
route-map: How to Announce RIP routeredistribute rip
: Redistribute to BGPredistribute ripng
: Redistribute routes to OSPF6redistribute static
: Redistribute to BGPredistribute static
: Redistribute routes to OSPF6redistribute static
: How to Announce RIP routeredistribute static metric <0-16>
: How to Announce RIP routeredistribute static route-map
route-map: How to Announce RIP routerefresh age-diff <0-10000>
: OSPF routerrefresh group-limit <0-10000>
: OSPF routerrefresh per-slice <0-10000>
: OSPF routerroute
a.b.c.d/m: How to Announce RIP routeroute
network: ripngd Configurationroute-map
route-map-name permit
priority: Route Map Commandrouter bgp
as-number: BGP instance and viewrouter bgp
as-number view
name: BGP instance and viewrouter bgp
asn: BGP routerrouter ospf
: OSPF routerrouter ospf6
: OSPF6 routerrouter rip
: RIP Configurationrouter ripng
: ripngd Configurationrouter zebra
: Redistribute routes to OSPFrouter zebra
: ripngd Configurationrouter-id
a.b.c.d: OSPF6 routerservice advanced-vty
: Basic Config Commandsservice integrated-vtysh-config
: VTY shell integrated configurationservice password-encryption
: Basic Config Commandsservice terminal-length
<0-512>: Basic Config Commandsset as-path prepend
as-path: Using AS Path in Route Mapset as-path prepend
as_path: Route Map Set Commandset comm-list
word delete
: BGP Community in Route Mapset community
community: Route Map Set Commandset community
community: BGP Community in Route Mapset community
community additive
: BGP Community in Route Mapset community none
: BGP Community in Route Mapset extcommunity rt
extcommunity: BGP Extended Communities in Route Mapset extcommunity soo
extcommunity: BGP Extended Communities in Route Mapset ip next-hop A.B.C.D
: RIP route-mapset ip next-hop
ipv4_address: Route Map Set Commandset ipv6 next-hop global
ipv6_address: Route Map Set Commandset ipv6 next-hop local
ipv6_address: Route Map Set Commandset local-preference
local_pref: Route Map Set Commandset metric <0-4294967295>
: RIP route-mapset metric
metric: Route Map Set Commandset weight
weight: Route Map Set Commandshow debug
: More Show IP BGPshow debugging ospf
: Debugging OSPFshow debugging rip
: RIP Debug Commandsshow debugging ripng
: ripngd Terminal Mode Commandsshow interface
: zebra Terminal Mode Commandsshow ip bgp
: Show IP BGPshow ip bgp
A.B.C.D: Show IP BGPshow ip bgp community
: Display BGP Routes by Communityshow ip bgp community
community: More Show IP BGPshow ip bgp community
community: Display BGP Routes by Communityshow ip bgp community
community exact-match
: More Show IP BGPshow ip bgp community
community exact-match
: Display BGP Routes by Communityshow ip bgp community-list
word: More Show IP BGPshow ip bgp community-list
word: Display BGP Routes by Communityshow ip bgp community-list
word exact-match
: More Show IP BGPshow ip bgp community-list
word exact-match
: Display BGP Routes by Communityshow ip bgp neighbor [
peer]
: More Show IP BGPshow ip bgp regexp
line: More Show IP BGPshow ip bgp regexp
line: Display BGP Routes by AS Pathshow ip bgp summary
: More Show IP BGPshow ip bgp view
name: Viewing the viewshow ip bgp
X:X::X:X: Show IP BGPshow ip community-list
: BGP Community Listsshow ip community-list
name: BGP Community Listsshow ip extcommunity-list
: BGP Extended Community Listsshow ip extcommunity-list
name: BGP Extended Community Listsshow ip ospf
: Showing OSPF informationshow ip ospf database
: Showing OSPF informationshow ip ospf database (asbr-summary|external|network|router|summary)
: Showing OSPF informationshow ip ospf database (asbr-summary|external|network|router|summary) adv-router
adv-router: Showing OSPF informationshow ip ospf database (asbr-summary|external|network|router|summary)
link-state-id: Showing OSPF informationshow ip ospf database (asbr-summary|external|network|router|summary)
link-state-id adv-router
adv-router: Showing OSPF informationshow ip ospf database (asbr-summary|external|network|router|summary)
link-state-id self-originate
: Showing OSPF informationshow ip ospf database (asbr-summary|external|network|router|summary) self-originate
: Showing OSPF informationshow ip ospf database max-age
: Showing OSPF informationshow ip ospf database self-originate
: Showing OSPF informationshow ip ospf interface [INTERFACE]
: Showing OSPF informationshow ip ospf neighbor
: Showing OSPF informationshow ip ospf neighbor detail
: Showing OSPF informationshow ip ospf neighbor INTERFACE
: Showing OSPF informationshow ip ospf neighbor INTERFACE detail
: Showing OSPF informationshow ip ospf refresher
: Showing OSPF informationshow ip ospf route
: Showing OSPF informationshow ip prefix-list
: Showing ip prefix-listshow ip prefix-list detail
: Showing ip prefix-listshow ip prefix-list detail
name: Showing ip prefix-listshow ip prefix-list
name: Showing ip prefix-listshow ip prefix-list
name a.b.c.d/m: Showing ip prefix-listshow ip prefix-list
name a.b.c.d/m first-match
: Showing ip prefix-listshow ip prefix-list
name a.b.c.d/m longer
: Showing ip prefix-listshow ip prefix-list
name seq
num: Showing ip prefix-listshow ip prefix-list summary
: Showing ip prefix-listshow ip prefix-list summary
name: Showing ip prefix-listshow ip protocols
: Show RIP Informationshow ip rip
: Show RIP Informationshow ip ripng
: ripngd Terminal Mode Commandsshow ip route
: zebra Terminal Mode Commandsshow ipforward
: zebra Terminal Mode Commandsshow ipv6 ospf6 [INSTANCE_ID]
: Showing OSPF6 informationshow ipv6 ospf6 database
: Showing OSPF6 informationshow ipv6 ospf6 interface
: Showing OSPF6 informationshow ipv6 ospf6 neighbor
: Showing OSPF6 informationshow ipv6 ospf6 request-list A.B.C.D
: Showing OSPF6 informationshow ipv6 route
: zebra Terminal Mode Commandsshow ipv6 route ospf6
: Showing OSPF6 informationshow ipv6forward
: zebra Terminal Mode Commandsshow logging
: Terminal Mode Commandsshow version
: Terminal Mode Commandsshutdown
: Interface Commandssmux peer
oid: MIB and command referencesmux peer
oid password: MIB and command referencetable
tableno: Static Route Commandsterminal length
<0-512>: Terminal Mode Commandstimers basic
update timeout garbage: RIP Timerstimers spf <0-4294967295> <0-4294967295>
: OSPF routerusername
username nopassword
: VTY shell usernameversion
version: RIP Configurationwho
: Terminal Mode Commandswrite file
: Terminal Mode Commandswrite terminal
: Terminal Mode Commands<DEL>
: CLI Editing Commands<DOWN>
: CLI Advanced Commands<LEFT>
: CLI Movement Commands<RIGHT>
: CLI Movement Commands<TAB>
: CLI Advanced Commands<UP>
: CLI Advanced Commands?
: CLI Advanced CommandsC-a
: CLI Movement CommandsC-b
: CLI Movement CommandsC-c
: CLI Advanced CommandsC-d
: CLI Editing CommandsC-e
: CLI Movement CommandsC-f
: CLI Movement CommandsC-h
: CLI Editing CommandsC-k
: CLI Editing CommandsC-n
: CLI Advanced CommandsC-p
: CLI Advanced CommandsC-t
: CLI Editing CommandsC-u
: CLI Editing CommandsC-w
: CLI Editing CommandsC-z
: CLI Advanced CommandsM-b
: CLI Movement CommandsM-d
: CLI Editing CommandsM-f
: CLI Movement Commands