The 6200 series supports the IP routing feature. Use the Routing menu page to configure routing on VLANs.
When a packet enters the switch, the destination MAC address is checked to see if it matches any of the configured routing interfaces. If it does, then the device searches the host table for a matching destination IP address. If an entry is found, then the packet is routed to the host. If there is not a matching entry, then the switch performs a longest prefix match on the destination IP address. If an entry is found, then the packet is routed to the next hop. If there is no match, then the packet is routed to the next hop specified in the default route. If there is no default route configured, then the packet is passed to the 6200 series software to be handled appropriately.
The routing table can have entries added either statically by the administrator or dynamically through RIP or OSPF. The host table can have entries added either statically by the administrator or dynamically through ARP.
The Routingmenu page contains links to the following features:
NOTE: CLI commands are not available for all the Routing pages.
ARP
The 6200 series uses the ARP protocol to associate a layer 2 MAC address with a layer 3 IPv4 address. Additionally, the administrator can statically add entries into the ARP table.
ARP is a necessary part of the internet protocol (IP) and is used to translate an IP address to a media (MAC) address, defined by a local area network (LAN) such as Ethernet. A station needing to send an IP packet must learn the MAC address of the IP destination, or of the next hop router, if the destination is not on the same subnet. This is achieved by broadcasting an ARP request packet, to which the intended recipient responds by unicasting an ARP reply containing its MAC address. Once learned, the MAC address is used in the destination address field of the layer 2 header prepended to the IP packet.
The ARP cache is a table maintained locally in each station on a network. There are no specific requirements for the construction or maintenance of this cache, but at a minimum it needs to contain the information learned from processing ARP protocol packets, which for Ethernet are denoted by an 0x0806 EtherType field. ARP cache entries are learned by examining the source information in the ARP packet payload fields, regardless of whether it is an ARP request or response. Thus, when an ARP request is broadcast to all stations on a LAN segment or virtual LAN (VLAN), every recipient has the opportunity to store the sender's IP and MAC address in their respective ARP cache. The ARP response, being unicast, is normally seen only by the requestor, who stores the sender information in its ARP cache. Newer information always replaces existing content in the ARP cache.
The ARP cache can support 896 entries, although this size is user-configurable to any value between 256 and 896. When multiple network interfaces are supported by a device, as is typical of a router, either a single ARP cache is used for all interfaces, or a separate cache is maintained per interface. While the latter approach is useful when network addressing is not unique per interface, this is not the case for Ethernet MAC address assignment so a single ARP cache is employed.
Devices can be moved in a network, which means the IP address that was at one time associated with a certain MAC address is now found using a different MAC, or may have disappeared from the network altogether (i.e., it has been reconfigured, disconnected, or powered off). This leads to stale information in the ARP cache unless entries are updated in reaction to new information seen on the network, periodically refreshed to determine if an address still exists, or removed from the cache if the entry has not been identified as a sender of an ARP packet during the course of an ageout interval, usually specified through configuration.
The ARP menu page contains links to web pages that configure and display ARP detail. To display this page, click Routing® ARP in the tree view. Following are the web pages accessible from this menu page:
Use the ARP Createpage to add an entry to the Address Resolution Protocol table.
To display the page, click Routing® ARP® ARP Createin the tree view.
Figure 10-1. ARP Create
The ARP Create page contains the following fields:
IP Address — Enter the IP address you want to add. It must be the IP address of a device on a subnet attached to one of the switch's existing routing interfaces.
MAC Address — The unicast MAC address of the device. Enter the address as six two-digit hexadecimal numbers separated by colons, for example 00:06:29:32:81:40.
Adding an Entry to the ARP Table
Open the ARP Createpage.
Specify the addresses to be associated.
Click Apply Changes.
The addresses are now in the ARP cache.
Adding Entries to the ARP Table using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
ARP Commands
ARP Table Configuration
Use this page to change the configuration parameters for the Address Resolution Protocol Table. You can also use this screen to display the contents of the table.
To display the page, click Routing® ARP® ARP Table Configurationin the tree view.
Figure 10-2. ARP Table Configuration
The ARP Table Configuration page contains the following fields:
Age Time (secs) — Enter the value you want the switch to use for the ARP entry ageout time. You must enter a valid integer, which represents the number of seconds it takes for an ARP entry to age out. The range for this field is 15 to 21600 seconds. The default value for Age Time is 1200 seconds.
Response Time (secs) — Enter the value you want the switch to use for the ARP response timeout. You must enter a valid integer, which represents the number of seconds the switch waits for a response to an ARP request. The range for this field is 1 to 10 seconds. The default value for Response Time is 1 second.
Retries — Enter an integer which specifies the maximum number of times an ARP request is retried. The range for this field is 0 to 10. The default value for Retries is 4.
Cache Size — Enter an integer which specifies the maximum number of entries for the ARP cache. The range for this field is 256 to 896. The default value for Cache Size is 896.
Dynamic Renew — This controls whether the ARP component automatically attempts to renew ARP Entries of type Dynamic when they age out. The default setting is Enable.
Total Entry Count — Total number of Entries in the ARP table.
Peak Total Entries — Highest value reached by Total Entry Count. This counter value is restarted whenever the ARP table Cache Size value is changed.
Active Static Entries — Total number of Active Static Entries in the ARP table.
Configured Static Entries — Total number of Configured Static Entries in the ARP table.
Maximum Static Entries — Maximum number of Static Entries that can be defined.
Remove from Table — Allows you to remove certain entries from the ARP Table. The choices listed specify the type of ARP Entry to be deleted:
All Dynamic Entries
All Dynamic and Gateway Entries
Specific Dynamic Gateway Entry
Specific Static Entry
The ARP Table displays at the bottom of the page, and contains the following fields:
IP Address — The IP address of a device on a subnet attached to one of the switch's routing interfaces.
MAC Address — The unicast MAC address for the device. The format is six two-digit hexadecimal numbers separated by colons, for example 00:06:29:32:81:40.
VLAN ID — The routing interface associated with the ARP entry.
Type — The type of the ARP entry.
Age — Age since the entry was last refreshed in the ARP Table. The format is hh:mm:ss.
Configuring ARP Table
Open the ARP Table Configurationpage.
Change parameters as needed.
Click Apply Changes.
Changes are saved, and the ARP table is updated.
Configuring ARP Table with CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
ARP Commands
IP
The IP menu page contains links to web pages that configure and display IP routing data. To display this page, click Routing® IP in the tree view. Following are the web pages accessible from this menu page:
Use the IP Configurationpage to configure routing parameters for the switch as opposed to an interface.
To display the page, click Routing® IP® Configurationin the tree view.
Figure 10-3. IP Configuration
The IP Configuration page contains the following fields:
Default Time to Live — The default value inserted into the Time-To-Live field of the IP header of datagrams originated by the switch, if a TTL value is not supplied by the transport layer protocol.
Routing Mode — Select Enable or Disable from the drop-down menu. You must enable routing for the switch before you can route through any of the interfaces. Routing is also enabled or disabled per VLAN interface. The default value is Disable.
IP Forwarding Mode — Select Enable or Disable from the drop-down menu. This enables or disables the forwarding of IP frames. The default value is Enable.
Maximum Next Hops — The maximum number of hops supported by the switch. This is a compile-time constant.
Configuring IP Routing Parameters
Open the IP Configurationpage.
Change parameters as needed.
Click Apply Changes.
Changes are saved, and routing parameters are updated.
Configuring IP Routing Parameters with CLI Command
For information about the CLI commands that perform this function, see the following chapters in the CLI Reference Guide:
IP Routing Commands
VLAN Commands
IP Statistics
The statistics reported on the IP Statistics page are as specified in RFC 1213.
To display the page, click Routing® IP® Statisticsin the tree view.
Figure 10-4. IP Statistics
The IP Statistics page contains the following fields:
IpInReceives — The total number of input datagrams received from interfaces, including those received in error.
IpInHdrErrors — The number of input datagrams discarded due to errors in their IP headers, including bad checksums, version number mismatch, other format errors, time-to-live exceeded, errors discovered in processing their IP options, etc.
IpInAddrErrors — The number of input datagrams discarded because the IP address in their IP header's destination field was not a valid address to be received at this entity. This count includes invalid addresses (for example, 0.0.0.0) and addresses of unsupported Classes (for example, Class E). For entities which are not IP Gateways and therefore do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address.
IpForwDatagrams — The number of input datagrams for which this entity was not their final IP destination, as a result of which an attempt was made to find a route to forward them to that final destination. In entities which do not act as IP Gateways, this counter includes only those packets which were Source-Routed through this entity, and the Source-Route option processing was successful.
IpInUnknownProtos — The number of locally-addressed datagrams received successfully but discarded because of an unknown or unsupported protocol.
IpInDiscards — The number of input IP datagrams for which no problems were encountered to prevent their continued processing, but which were discarded (for example, for lack of buffer space). Note that this counter does not include any datagrams discarded while awaiting re-assembly.
IpInDelivers — The total number of input datagrams successfully delivered to IP user-protocols (including ICMP).
IpOutRequests — The total number of IP datagrams which local IP user-protocols (including ICMP) supplied to IP in requests for transmission. Note that this counter does not include any datagrams counted in ipForwDatagrams.
IpOutDiscards — The number of output IP datagrams for which no problem was encountered to prevent their transmission to their destination, but which were discarded (for example, for lack of buffer space). Note that this counter would include datagrams counted in ipForwDatagrams if any such packets met this (discretionary) discard criterion.
IpOutNoRoutes — The number of IP datagrams discarded because no route could be found to transmit them to their destination. Note that this counter includes any packets counted in ipForwDatagrams which meet this `no-route' criterion and any datagrams which a host cannot route because all of its default gateways are down.
IpReasmTimeout — The maximum number of seconds which received fragments are held while they are awaiting reassembly at this entity.
IpReasmReqds — The number of IP fragments received which needed to be reassembled at this entity.
IpReasmOKs — The number of IP datagrams successfully re-assembled.
IpReasmFails — The number of failures detected by the IP re-assembly algorithm (for whatever reason: timed out, errors, etc). Note that this is not necessarily a count of discarded IP fragments since some algorithms can lose track of the number of fragments by combining them as they are received.
IpFragOKs — The number of IP datagrams that have been successfully fragmented at this entity.
IpFragFails — The number of IP datagrams that have been discarded because they needed to be fragmented at this entity but could not be, for example, because their Don't Fragment flag was set.
IpFragCreates — The number of IP datagram fragments that have been generated as a result of fragmentation at this entity.
IpRoutingDiscards — The number of routing entries which were chosen to be discarded even though they are valid. One possible reason for discarding such an entry could be to free-up buffer space for other routing entries.
IcmpInMsgs — The total number of ICMP messages which the entity received. Note that this counter includes all those counted by icmpInErrors.
IcmpInErrors — The number of ICMP messages which the entity received but determined as having ICMP-specific errors (bad ICMP checksums, bad length, etc.).
IcmpInDestUnreachs — The number of ICMP Destination Unreachable messages received.
IcmpInTimeExcds — The number of ICMP Time Exceeded messages received.
IcmpInParmProbs — The number of ICMP Parameter Problem messages received.
IcmpInSrcQuenchs — The number of ICMP Source Quench messages received.
IcmpInRedirects — The number of ICMP Redirect messages received.
IcmpInEchos — The number of ICMP Echo (request) messages received.
IcmpInEchoReps — The number of ICMP Echo Reply messages received.
IcmpInTimestamps — The number of ICMP Timestamp (request) messages received.
IcmpInTimestampReps — The number of ICMP Timestamp Reply messages received.
IcmpInAddrMasks — The number of ICMP Address Mask Request messages received.
IcmpInAddrMaskReps — The number of ICMP Address Mask Reply messages received.
IcmpOutMsgs — The total number of ICMP messages which this entity attempted to send. Note that this counter includes all those counted by icmpOutErrors.
IcmpOutErrors — The number of ICMP messages which this entity did not send due to problems discovered within ICMP such as a lack of buffers. This value should not include errors discovered outside the ICMP layer such as the inability of IP to route the resultant datagram. In some implementations there may be no types of error which contribute to this counter's value.
IcmpOutDestUnreachs — The number of ICMP Destination Unreachable messages sent.
IcmpOutTimeExcds — The number of ICMP Time Exceeded messages sent.
IcmpOutParmProbs — The number of ICMP Parameter Problem messages sent.
IcmpOutSrcQuenchs — The number of ICMP Source Quench messages sent.
IcmpOutRedirects — The number of ICMP Redirect messages sent. For a host, this object is always zero, since hosts do not send redirects.
IcmpOutEchos — The number of ICMP Echo (request) messages sent.
IcmpOutEchoReps — The number of ICMP Echo Reply messages sent.
IcmpOutTimestamps — The number of ICMP Timestamp (request) messages.
IcmpOutTimestampReps — The number of ICMP Timestamp Reply messages sent.
IcmpOutAddrMasks — The number of ICMP Address Mask Request messages sent.
IcmpOutAddrMaskReps — The number of ICMP Address Mask Reply messages sent.
Refreshing IP Statistics
Open the IP Statisticspage.
Click Refresh.
The screen displays with the present state of the data in the switch.
Displaying IP Statistics using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
IP Routing Commands
IP Interface Configuration
Use the IP Interface Configurationpage to update IP interface data for this switch.
To display the page, click Routing® IP® Interface Configurationin the tree view.
Figure 10-5. IP Interface Configuration
The IP Interface Configuration page contains the following fields:
Interface — Select the interface to configure from the drop-down menu. The drop-down menu contains loopback interfaces and VLANs created from the Switching® VLAN® VLAN Membership® Add page.
IP Address — Enter the IP address for the interface.
Subnet Mask — Enter the subnet mask for the interface. This is also referred to as the subnet/network mask, and defines the portion of the interface's IP address that is used to identify the attached network.
Routing Mode — Setting this Enables or Disables routing for an interface. The default value is Enable.
Link Speed Data Rate — An integer representing the physical link data rate of the specified interface. This data is valid only for physical interfaces and is measured in Megabits per second (Mbps).
Forward Net Directed Broadcasts — Select how network directed broadcast packets should be handled. If you select Enable from the drop-down menu network directed broadcasts are forwarded. If you select Disable they are dropped. The default value is Disable.
Active State — The state of the specified interface is either Active or Inactive. An interface is considered active if the link is up and it is in forwarding state.
MAC Address — The burned-in physical address of the specified interface. The format is six two-digit hexadecimal numbers separated by colons, for example 00:06:29:32:81:40. This value is valid for physical interfaces. For logical interfaces, such as VLAN routing interfaces, the field displays the system MAC address.
Encapsulation Type — Select the link layer encapsulation type for packets transmitted from the specified interface from the drop-down menu. The possible values are Ethernet and SNAP. The default is Ethernet.
Proxy ARP — Select to Disable or Enable proxy ARP for the specified interface from the drop-down menu.
Local Proxy ARP — Select to Disable or Enable Local Proxy ARP for the specified interface from the drop-down menu.
IP MTU — Specifies the maximum transmission unit (MTU) size of IP packets sent on an interface. Valid range is (68 to 1500). Default value is 1500.
Modifying an IP Interface
Open the IP Interface Configurationpage.
Change values as needed.
Click Apply Changes.
Changes are saved, and the IP Interface is updated.
IP Interface Configuration CLI Commands
For information about the CLI commands that perform this function, see the following chapters in the CLI Reference Guide:
IP Addressing Commands
IP Routing Commands
ARP Commands
OSPF
The Open Shortest Path First (OSPF) routing protocol is an Interior Gateway Protocol (IGP). Every OSPF router builds a shortest path tree of all the routers and networks in the domain. Routing information is propagated in Link State Update packets both periodically and in the event of network topology changes. This information is received, assimilated and stored in the OSPF databases of individual routers. An integral piece of information in the database exchange is the number and IP Addresses of the interfaces that are associated with the router. OSPF treats secondary IP Addresses as stub networks attached to the router. Hence though these networks are advertised in the OSPF routing domain, neighbor adjacencies are never established on secondary addresses. It is also important to note here that all secondary IP Addresses must be in the same area as the primary IP Address so that they get advertised by OSPF. This is always true in the case of the 6200 series implementation because the area configuration is on a per interface basis as against a per network basis.
The OSPF menu page contains links to web pages that configure and display OSPF parameters and data. To display this page, click Routing® OSPF in the tree view. Following are the web pages accessible from this menu page:
Use the OSPF Configurationpage to enable OSPF on a router and to configure the related OSPF settings.
To display the page, click Routing® OSPF® Configurationin the tree view.
Figure 10-6. OSPF Configuration
The OSPF Configuration page contains the following fields:
Router ID — The 32-bit integer in dotted decimal format that uniquely identifies the router within the autonomous system (AS). If you want to change the Router ID you must first disable OSPF. After you set the new Router ID, you must re-enable OSPF to have the change take effect. The default value is 0.0.0.0, although this is not a valid Router ID.
OSPF Admin Mode — Select Enable or Disable from the drop-down menu. If you select Enable OSPF is activated for the switch. The default value is Disable. You must configure a Router ID before OSPF can become operational.
NOTE: Once OSPF is initialized on the router, it remains initialized until the router is reset.
ASBR Mode — Reflects whether the ASBR mode is Enabled or Disabled. Enable implies that the router is an autonomous system border router. Router automatically becomes an ASBR when it is configured to redistribute routes learnt from other protocol.
RFC 1583 Compatibility — Select Enable or Disable from the drop-down menu to specify the preference rules that are used when choosing among multiple AS-external-LSAs advertising the same destination. If you select Enable, the preference rules are those defined by RFC 1583. If you select Disable, the preference rules are those defined in Section 16.4.1 of the OSPF-2 standard (RFC 2328), which prevent routing loops when AS-external-LSAs for the same destination have been originated from different areas. The default value is Enable. To prevent routing loops, you should select Disable, but only if all OSPF routers in the routing domain are capable of operating according to RFC 2328.
ABR Status — The values of this are Enabled or Disabled. Enabled implies that the router is an area border router. Disabled implies that it is not an area border router.
Exit Overflow Interval (sec) — Enter the number of seconds that, after entering overflow state, the router should wait before attempting to leave overflow state. This allows the router to again originate non-default AS-external-LSAs. If you enter 0, the router does not leave Overflow State until restarted. The range is 0 to 2147483647 seconds.
SPF DelayTime (secs) — Enter the number of seconds, Delay time (in seconds) is the time between when OSPF receives a topology change and when it starts an SPF calculation. It can be an integer from 0 to 65535. The default time is 5 seconds. A value of 0 means that there is no delay; that is, the SPF calculation is started immediately.
SPF HoldTime(secs) — Enter the number of seconds, minimum time (in seconds) between two consecutive SPF calculations.It can be an integer from 0 to 65535. The default time is 10 seconds. A value of 0 means that there is no delay; that is, two SPF calculations can be done, one immediately after the other.
External LSA Count — The number of external (LS type 5) LSAs (link state advertisements) in the link state database.
External LSA Checksum — The sum of the LS checksums of the external LSAs (link state advertisements) contained in the link-state database. This sum can be used to determine if there has been a change in a router's link state database, and to compare the link-state databases of two routers. This value is in hexadecimal.
New LSAs Originated — In any given OSPF area, a router originates several LSAs. Each router originates a router-LSA. If the router is also the Designated Router for any of the area's networks, it originates network-LSAs for those networks. This value represents the number of LSAs originated by this router.
LSAs Received — The number of LSAs (link state advertisements) received that were determined to be new instantiations. This number does not include newer instantiations of self-originated LSAs.
Default Metric — Sets a default for the metric of redistributed routes.This field displays the default metric if one has already been set or blank if not configured earlier. The valid values are (1 to 16777214)
Maximum Paths — Configure the maximum number of paths that OSPF can report to a given destination. The valid values are (1 to 2).
Default Route Advertise
Default Information Originate — Enable or Disable Default Route Advertise.
Always — Sets the router advertise 0.0.0.0/0.0.0.0 when set to True.
Metric — Specifies the metric of the default route. The valid values are (1 to 16777214)
Metric Type — Sets the metric type of the default route. Options are External Type 1 and External Type 2. External Type 2 is the default.
Modifying an OSPF Configuration
Open the OSPF Configurationpage.
Change values as needed.
Click Apply Changes.
Changes are saved, and the OSPF Interface is updated.
OSPF Configuration CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Area Configuration
The OSPF Area Configurationpage lets you create a Stub area configuration and NSSA once you've enabled OSPF on an interface through Routing® OSPF® Interface Configuration. At least one router must have OSPF enabled for this web page to display.
To display the page, click Routing® OSPF® Area Configurationin the tree view.
Figure 10-7. OSPF Area Configuration
The OSPF Area Configuration page displays the following fields:
Area — Select the area to be displayed from the drop-down menu. When an area is selected, fields in the Stub Area Information are displayed.
Area ID — The OSPF area. An Area ID is a 32-bit integer in dotted decimal format that uniquely identifies the area to which a router interface connects.
External Routing — A definition of the router's capabilities for the area, including whether or not AS-external-LSAs are flooded into/throughout the area. If the area is a stub area, then these are the possible options for which you may configure the external routing capability, otherwise the only option is Import External LSAs.
SPF Runs — The number of times that the intra-area route table has been calculated using this area's link-state database. This is typically done using Dijkstra's algorithm.
Area Border Router Count — The total number of area border routers reachable within this area. This is initially zero, and is calculated in each SPF Pass.
Area LSA Count — The total number of link-state advertisements in this area's link-state database, excluding AS External LSAs.
Area LSA Checksum — The 32-bit unsigned sum of the link-state advertisements' LS checksums contained in this area's link-state database. This sum excludes external (LS type 5) link-state advertisements. The sum can be used to determine if there has been a change in a router's link state database, and to compare the link-state database of two routers. This value is in hexadecimal.
Stub Area Information
Import Summary LSAs — Select Enable or Disable from the drop-down menu. If you select Enable summary LSAs is imported into stub areas.
Metric Value — Enter the metric value you want applied for the default route advertised into the stub area. Valid values range from 1 to 16,777,215.
Metric Type — Select the type of metric specified in the Metric Value field.
Translator Role — Configure the NSSA Translator Role as always/candidate.
Translator Stability Interval — Configure the Translator Stability Interval for the selected NSSA.
No-Redistribute Mode — Configure the route redistribution for the selected NSSA.
Translator State — Displays the current state of the Translator.
Configuring an OSPF Area
Open the OSPF Area Configurationpage.
Specify an area to configure.
Specify values in the remaining fields as needed.
Click Apply Changes.
The OSPF area is defined and configured.
Displaying an OSPF Area Configuration
Open the OSPF Area Configurationpage.
Select the OSPF area to display from the drop-down menu.
The OSPF area configuration is displayed for this area.
Deleting an OSPF Area Configuration
Use these steps to delete NSSA configuration or Stub area configuration.
Open the OSPF Area Configurationpage.
Select the OSPF area configuration to delete from the drop-down menu.
The configuration displays.
Click Delete.
The OSPF area configuration is removed.
Configuring OSPF Area CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Stub Area Summary
Use the OSPF Stub Area Summarypage to display OSPF stub area detail.
To display the page, click Routing® OSPF® Stub Area Summaryin the tree view.
Figure 10-8. OSPF Stub Area Summary
The OSPF Stub Area Summary page displays the following fields:
Area ID — The Area ID of the Stub area.
Type of Service — The type of service associated with the stub metric. The switch supports Normal only.
Metric Value — Displays the configured metric value.
Metric Type — The type of metric for the stub area where valid types are:
OSPF Metric — Regular OSPF metric
Comparable Cost — External Type 1 metrics that are comparable to the OSPF metric
Non-comparable Cost — External Type 2 metrics that are assumed to be larger than the cost of the OSPF metric
Import Summary LSAs — Whether the import of Summary LSAs is Enabled or Disabled.
Displaying OSPF Stub Area CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Area Range Configuration
Use the OSPF Area Range Configurationpage to configure and display an area range for a specified NSSA.
To display the page, click Routing® OSPF® Area Range Configurationin the tree view.
Figure 10-9. OSPF Area Range Configuration
The OSPF Area Range Configuration page contains the following fields:
Area ID — Select the area for which data is to be configured from the drop-down menu.
IP Address — Enter the IP Address for the address range for the selected area.
Subnet Mask — Enter the Subnet Mask for the address range for the selected area.
LSDB Type — Select the type of Link Advertisement associated with the specified area and address range. The default type is 'Network Summary.'
Advertisement — Select Enable or Disable from the drop-down menu. If you selected Enable the address range is advertised outside the area through a Network Summary LSA. The default is Enable.
Add — Check the Add checkbox if you wish to add an area range.
OSPF Area Range Table
Area ID — Displays the OSPF area.
IP Address — Displays the IP address of an address range for the area.
Subnet Mask — Displays the subnet mask of an address range for the area.
LSDB Type — Displays the link advertisement type for the address range and area.
Advertisement — Displays the advertisement mode for the address range and area.
Remove — Removes the specified area entry.
Defining an OSPF Area Range
Open the OSPF Area Range Configurationpage.
Enter Area ID, IP Address, Subnet Mask, LSDB Type and Advertisement.
Click the Add checkbox.
Click Apply Changes.
The OSPF area range is defined and configured. All configured OSPF area ranges are displayed in the table on the OSPF Area Range Configuration page.
Removing an OSPF Area Range Configuration
Open the OSPF Area Range Configurationpage.
Select the Remove check box in the row of the Area ID to be deleted.
Click Apply Changes.
The address range is removed from the area configuration.
OSPF Area Range Configuration CLI Command
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Interface Statistics
Use the OSPF Interface Statisticspage to display statistics for the selected interface. The information is displayed only if OSPF is enabled.
To display the page, click Routing® OSPF® Interface Statisticsin the tree view.
Figure 10-10. OSPF Interface Statistics
The OSPF Interface Statistics page contains the following fields:
Interface — Select the interface for which data is to be displayed from the drop-down menu.
OSPF Area ID — The OSPF area to which the selected router interface belongs. An OSPF Area ID is a 32-bit integer in dotted decimal format that uniquely identifies the area to which the interface connects.
Area Border Router Count — The total number of area border routers reachable within this area. This is initially zero, and is calculated in each SPF Pass.
AS Border Router Count — The total number of Autonomous System border routers reachable within this area. This is initially zero, and is calculated in each SPF Pass.
Area LSA Count — The total number of link-state advertisements in this area's link-state database, excluding AS External LSAs.
IP Address — The IP address of the interface.
Interface Events — The number of times the specified OSPF interface has changed its state, or an error has occurred.
Virtual Events — The number of state changes or errors that have occurred on this virtual link.
Neighbor Events — The number of times this neighbor relationship has changed state, or an error has occurred.
External LSA Count — The number of external (LS type 5) link-state advertisements in the link-state database.
Displaying OSPF Interface Statistics
Open the OSPF Interface Statisticspage.
Select the interface for which data is to be displayed from the drop-down menu.
Statistics for this interface display.
Displaying OSPF Interface Statistics using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Interface Configuration
Use the OSPF Interface Configurationpage to configure an OSPF interface.
To display the page, click Routing® OSPF® Interface Configurationin the tree view.
Figure 10-11. OSPF Interface Configuration
The OSPF Interface Configuration page contains the following fields:
Interface — Select the interface for which data is to be displayed or configured from the drop-down menu.
IP Address — Displays the address of the VLAN Interface.
Subnet Mask — Displays the subnet mask of the VLAN Interface.
OSPF Admin Mode — You may select Enable or Disable from the drop-down menu. The default value is Disable. You can configure OSPF parameters without enabling OSPF Admin Mode, but they have no effect until Admin Mode is enabled. The following information is displayed only if the Admin Mode is enabled: State, Designated Router, Backup Designated Router, Number of Link Events, LSA Ack Interval, and Metric Cost. For OSPF to be fully functional, you must enter a valid IP Address and Subnet Mask through the IP Interface Configuration page.
NOTE: Once OSPF is initialized on the router, it remains initialized until the router is reset.
OSPF Area ID — Enter the 32-bit integer in dotted decimal format that uniquely identifies the OSPF area to which the selected router interface connects. If you assign an Area ID which does not exist, the area is created with default values.
Router Priority — Enter the OSPF priority for the selected interface. The priority of an interface is specified as an integer from 0 to 255. The default is 1, which is the highest router priority. A value of 0 indicates that the router is not eligible to become the designated router on this network.
Retransmit Interval (secs) — Enter the OSPF retransmit interval for the specified interface. This is the number of seconds between link-state advertisements for adjacencies belonging to this router interface. This value is also used when retransmitting database descriptions and link-state request packets. Valid values range from 0 to 3600 seconds (1 hour). The default is 5 seconds.
Hello Interval (secs) — Enter the OSPF hello interval for the specified interface in seconds. This parameter must be the same for all routers attached to a network. Valid values range from 1 to 65,535. The default is 10 seconds.
Dead Interval (secs) — Enter the OSPF dead interval for the specified interface in seconds. This specifies how long a router waits to see a neighbor router's Hello packets before declaring that the router is down. This parameter must be the same for all routers attached to a network. This value should a multiple of the Hello Interval (for example 4). Valid values range from 1 to 2147483647. The default is 40.
LSA Ack Interval — The number of seconds between LSA Acknowledgment packet transmissions, which must be less than the Retransmit Interval.
Interface Delay Interval (secs) — Enter the OSPF Transit Delay for the specified interface. This specifies the estimated number of seconds it takes to transmit a link state update packet over the selected interface. Valid values range from 1 to 3600 seconds (1 hour). The default value is 1 second.
MTU Ignore — Disables OSPF MTU mismatch detection on receiving packets. The default value is Disable.
Authentication Type — You may select an authentication type other than None by clicking on the Modify button. You then see a new web page, where you can select the authentication type from the drop-down menu. Possible values are:
None — This is the initial interface state. If you select this option from the drop-down menu on the second screen and click Apply Changes, you are returned to the first screen, and no authentication protocols are run.
Simple — If you select Simple, you are prompted to enter an authentication key. This key is included, in the clear, in the OSPF header of all packets sent on the network. All routers on the network must be configured with the same key.
Encrypt — If you select Encrypt, you are prompted to enter both an authentication key and an authentication ID. Encryption uses the MD5 Message-Digest algorithm. All routers on the network must be configured with the same key and ID.
Interface Type — The OSPF interface type, which is always broadcast.
State — The current state of the selected router interface. Possible values are:
Down — This is the initial interface state. In this state, the lower-level protocols have indicated that the interface is unusable. In this state, interface parameters are set to their initial values. All interface timers are disabled, and there are no adjacencies associated with the interface.
Loopback — In this state, the router's interface to the network is looped back either in hardware or software. The interface is unavailable for regular data traffic. However, it may still be desirable to gain information on the quality of this interface, either through sending ICMP pings to the interface or through something like a bit error test. For this reason, IP packets may still be addressed to an interface in Loopback state. To facilitate this, such interfaces are advertised in router- LSAs as single host routes, whose destination is the IP interface address.
Waiting — The router is trying to determine the identity of the (Backup) Designated Router for the network by monitoring received Hello Packets. The router is not allowed to elect a Backup Designated Router or a Designated Router until it transitions out of Waiting state. This prevents unnecessary changes of (Backup) Designated Router.
Designated Router — This router is itself the Designated Router on the attached network. Adjacencies are established to all other routers attached to the network. The router must also originate a network-LSA for the network node. The network- LSA contains links to all routers (including the Designated Router itself) attached to the network.
Backup Designated Router — This router is itself the Backup Designated Router on the attached network. It is promoted to Designated Router if the present Designated Router fails. The router establishes adjacencies to all other routers attached to the network. The Backup Designated Router performs slightly different functions during the Flooding Procedure, as compared to the Designated Router.
Other Designated Router — The interface is connected to a broadcast or NBMA network on which other routers have been selected to be the Designated Router and Backup Designated Router either. The router attempts to form adjacencies to both the Designated Router and the Backup Designated Router.
The State is only displayed if the OSPF admin mode is enabled.
Designated Router — The identity of the Designated Router for this network, in the view of the advertising router. The Designated Router is identified here by its router ID. The value 0.0.0.0 means that there is no Designated Router. This field is only displayed if the OSPF admin mode is enabled.
Backup Designated Router — The identity of the Backup Designated Router for this network, in the view of the advertising router. The Backup Designated Router is identified here by its router ID. Set to 0.0.0.0 if there is no Backup Designated Router. This field is only displayed if the OSPF admin mode is enabled.
Number of Link Events — This is the number of times the specified OSPF interface has changed its state. This field is only displayed if the OSPF admin mode is enabled.
Metric Cost — Enter the value on this interface for the cost TOS (type of service). The range for the metric cost is between 1 and 65,535. Metric Cost is only configurable/displayed if OSPF is initialized on the interface.
Configuring an OSPF Interface Configuration
Open the OSPF Interface Configurationpage.
Specify an interface to configure.
Specify values in the remaining fields as needed.
Click Apply Changes.
The OSPF interface is configured.
Displaying an OSPF Interface Configuration
Open the OSPF Interface Configurationpage.
Select the VLAN interface for which data is to be displayed from the drop-down menu.
Configuration data for this interface display.
Configuring an OSPF Interface using CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Neighbor Table
Use the OSPF Neighbor Tablepage to display the OSPF neighbor table list. When a particular neighbor ID is specified, detailed information about a neighbor is given. The information below is only displayed if OSPF is enabled.
To display the page, click Routing® OSPF® Neighbor Tablein the tree view.
Figure 10-12. OSPF Neighbor Table
The OSPF Neighbor Table page displays the following fields:
Interface — Select the interface for which data is to be displayed from a drop-down menu.
Router ID — A 32-bit integer in dotted decimal format representing the neighbor interface.
IP Address — The IP address of the neighboring router's interface to the attached network. It is used as the destination IP address when protocol packets are sent as unicasts along this adjacency. Also used in router-LSAs as the Link ID for the attached network if the neighboring router is selected to be designated router. The Neighbor IP address is learned when Hello packets are received from the neighbor. For virtual links, the Neighbor IP address is learned during the routing table build process.
Neighbor Interface Index — An interface identifying the neighbor interface index.
Displaying the OSPF Neighbor Table Using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Neighbor Configuration
Use the OSPF Neighbor Configurationpage to display the OSPF neighbor configuration for a selected neighbor ID. When a particular neighbor ID is specified, detailed information about a neighbor is given. The information below is only displayed if OSPF is enabled and the interface has a neighbor. The IP address is the IP address of the neighbor.
To display the page, click Routing® OSPF® Neighbor Configurationin the tree view.
Figure 10-13. OSPF Neighbor Configuration
The OSPF Neighbor Configuration page contains the following fields:
Interface — Select the VLAN interface on which routing is enabled from the drop-down menu.
Neighbor IP Address — Select the IP Address of the neighbor for which data is to be displayed.
Router ID — A 32-bit integer in dotted decimal format that identifies the neighbor router.
Options — The optional OSPF capabilities supported by the neighbor. The OSPF Options field is present in OSPF Hello packets, Database Description packets, and all link-state advertisements. The Options field enables OSPF routers to support (or not support) optional capabilities, and to communicate their capability level to other OSPF routers. Through this mechanism, routers of differing capabilities can be mixed within an OSPF routing domain. The Options value is a bitmap, and it signifies the capability of the neighbor.
Router Priority — Displays the OSPF priority for the specified neighbor. The priority of a neighbor is a priority integer from 0 to 255. A value of 0 indicates that the router is not eligible to become the designated router on this network.
State — The state of a neighbor can be the following:
Down — This is the initial state of a neighbor conversation. It indicates that there has been no recent information received from the neighbor. On NBMA networks, Hello packets may still be sent to Down neighbors, although at a reduced frequency.
Attempt — This state is only valid for neighbors attached to NBMA networks. It indicates that no recent information has been received from the neighbor, but that a more concerted effort should be made to contact the neighbor. This is done by sending the neighbor Hello packets at intervals of Hello Interval.
Init — In this state, a Hello packet has recently been seen from the neighbor. However, bidirectional communication has not yet been established with the neighbor (i.e., the router itself did not appear in the neighbor's Hello packet). All neighbors in this state (or greater) are listed in the Hello packets sent from the associated interface.
2-Way — In this state, communication between the two routers is bidirectional. This has been assured by the operation of the Hello Protocol. This is the most advanced state short of beginning adjacency establishment. The (Backup) Designated Router is selected from the set of neighbors in state 2-Way or greater.
Exchange Start — This is the first step in creating an adjacency between the two neighboring routers. The goal of this step is to decide which router is the master, and to decide upon the initial DD sequence number. Neighbor conversations in this state or greater are called adjacencies.
Exchange — In this state, the router is describing its entire link state database by sending Database Description packets to the neighbor. In this state, Link State Request Packets may also be sent asking for the neighbor's more recent LSAs. All adjacencies in Exchange state or greater are used by the flooding procedure. These adjacencies are fully capable of transmitting and receiving all types of OSPF routing protocol packets.
Loading — In this state, Link State Request packets are sent to the neighbor asking for the more recent LSAs that have been discovered (but not yet received) in the Exchange state.
Full — In this state, the neighboring routers are fully adjacent. These adjacencies appear in router-LSAs and network-LSAs.
Events — The number of times this neighbor relationship has changed state, or an error has occurred.
Permanence — This variable displays the status of the entry. Dynamic and permanent see how the neighbor became known.
Hellos Suppressed — This indicates whether Hellos are being suppressed to the neighbor.
Retransmission Queue Length — The current length of the retransmission queue.
Displaying OSPF Neighbor Configuration
Open the OSPF Neighbor Configurationpage.
Select the interface and the IP address to display.
The neighbor configuration displays.
Displaying OSPF Neighbor Configuration using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Link State Database
Use the OSPF Link State Databasepage to display OSPF link state information.
To display the page, click Routing® OSPF® Link State Databasein the tree view.
Figure 10-14. OSPF Link State Database
The OSPF Link State Database page displays the following fields:
Router ID — The 32-bit integer in dotted decimal format that uniquely identifies the router within the autonomous system (AS). The Router ID is set on the IP Configuration page. If you want to change the Router ID you must first disable OSPF. After you set the new Router ID, you must re-enable OSPF to have the change take effect. The default value is 0.0.0.0, although this is not a valid Router ID.
Area ID — The ID of an OSPF area to which one of the router interfaces is connected. An Area ID is a 32-bit integer in dotted decimal format that uniquely identifies the area to which an interface is connected.
LSA Type — The format and function of the link state advertisement. Possible values are:
Router Links
Network Links
Network Summary
ASBR Summary
AS-external
LS ID — The Link State ID identifies the piece of the routing domain that is being described by the advertisement. The value of the LS ID depends on the advertisement's LS type.
Age — The time since the link state advertisement was first originated, in seconds.
Sequence — The sequence number field is a signed 32-bit integer. It is used to detect old and duplicate link state advertisements. The larger the sequence number, the more recent the advertisement.
Checksum — The checksum is used to detect data corruption of an advertisement. This corruption can occur while an advertisement is being flooded, or while it is being held in a router's memory. This field is the checksum of the complete contents of the advertisement, except the LS age field.
Options — The Options field in the link state advertisement header indicates which optional capabilities are associated with the advertisement. Possible values are:
Q — This enables support for QoS Traffic Engineering.
E — This describes the way AS-external-LSAs are flooded.
MC — This describes the way IP multicast datagrams are forwarded according to the standard specifications.
O — This describes whether Opaque-LSAs are supported.
V — This describes whether OSPF++ extensions for VPN/COS are supported.
Virtual Link Configuration
Use the Virtual Link Configurationpage to create or configure virtual interface information for a specific area and neighbor. A valid OSPF area must be configured before this page can be displayed.
To display the page, click Routing® OSPF® Virtual Link Configurationin the tree view.
Figure 10-15. OSPF Virtual Link Configuration - Create
The OSPF Virtual Link Configuration pages contain the following fields:
Virtual Link (Area ID - Neighbor Router ID) — Select the virtual link for which you want to display or configure data. It consists of the Area ID and Neighbor Router ID. To create a new virtual link, select Create New Virtual Link from the drop-down menu to define a new virtual link. When Create New Virtual Link is selected, the following fields appear:
Area ID — The 32-bit integer in dotted decimal format that uniquely identifies the area to which a router interface connects.
Neighbor Router ID — The 32-bit integer in dotted decimal format that uniquely identifies the neighbor router that is part of the virtual link.
Hello Interval — Enter the OSPF hello interval for the specified interface in seconds. This parameter must be the same for all routers attached to a network. Valid values range from 1 to 65535. The default is 10 seconds.
Dead Interval — Enter the OSPF dead interval for the specified interface in seconds. This specifies how long a router waits to see a neighbor router's Hello packets before declaring that the router is down. This parameter must be the same for all routers attached to a network. This value should a multiple of the Hello Interval (for example, 4). Valid values range from 1 to 65535. The default is 40 seconds.
Interface Delay Interval(secs) — The OSPF Transit Delay for the virtual link in units of seconds. It specifies the estimated number of seconds it takes to transmit a link state update packet over this interface.
State — The current state of the selected Virtual Link. One of:
Down — This is the initial interface state. In this state, the lower-level protocols have indicated that the interface is unusable. In this state, interface parameters are set to their initial values. All interface timers are disabled, and there are no adjacencies associated with the interface.
Waiting — The router is trying to determine the identity of the (Backup) Designated Router by monitoring received Hello Packets. The router is not allowed to elect a Backup Designated Router or a Designated Router until it transitions out of Waiting state. This prevents unnecessary changes of (Backup) Designated Router.
Point-to-Point — The interface is operational, and is connected either to the virtual link. On entering this state the router attempts to form an adjacency with the neighboring router. Hello Packets are sent to the neighbor every HelloInterval seconds.
Designated Router — This router is itself the Designated Router on the attached network. Adjacencies are established to all other routers attached to the network. The router must also originate a network-LSA for the network node. The network- LSA contains links to all routers (including the Designated Router itself) attached to the network.
Backup Designated Router — This router is itself the Backup Designated Router on the attached network. It is promoted to Designated Router if the present Designated Router fails. The router establishes adjacencies to all other routers attached to the network. The Backup Designated Router performs slightly different functions during the Flooding Procedure, as compared to the Designated Router.
Other Designated Router — The interface is connected to a broadcast or NBMA network on which other routers have been selected to be the Designated Router and Backup Designated Router either. The router attempts to form adjacencies to both the Designated Router and the Backup Designated Router.
Neighbor State — The state of the Virtual Neighbor Relationship.
Retransmit Interval — Enter the OSPF retransmit interval for the specified interface. This is the number of seconds between link-state advertisements for adjacencies belonging to this router interface. This value is also used when retransmitting database descriptions and link-state request packets. Valid values range from 0 to 3600 seconds (1 hour). The default is 5 seconds.
Authentication Type — You may select an authentication type other than none by clicking on the Configure Authentication button. You then see a new screen, where you can select the authentication type from the drop-down menu. The choices are:
None — This is the initial interface state. If you select this option from the drop-down menu on the second screen and click Apply Changes, you are returned to the first screen.
Simple — If you select Simple you are prompted to enter an authentication key. This key is included, in the clear, in the OSPF header of all packets sent on the network. All routers on the network must be configured with the same key.
Encrypt — If you select Encrypt you are prompted to enter both an authentication key and an authentication ID. Encryption uses the MD5 Message-Digest algorithm. All routers on the network must be configured with the same key and ID.
Authentication Key — Enter the OSPF Authentication Key for the specified interface. If you do not choose to use authentication you are not prompted to enter a key. If you choose Simple authentication you cannot use a key of more than 8 characters. If you choose Encrypt the key may be up to 16 characters long. The key value is only displayed if you are logged on with Read/Write privileges, otherwise it is displayed as asterisks.
Authentication ID — Enter the ID to be used for authentication. You are only prompted to enter an ID when you select Encrypt as the authentication type. The ID is a number between 0 and 255, inclusive.
Defining a New Virtual Link
Open the OSPF Virtual Link Configurationpage.
Select Create New Virtual Link from the Virtual Link (Area ID - Neighbor Router ID) drop-
down menu.
Specify the neighbor router ID for the new virtual link.
Click Apply Changes.
The remaining fields display when the Virtual Link is created.
Figure 10-16. OSPF Virtual Link Configuration
Click Configure Authentication to modify authentication.
The following page appears:
Figure 10-17. OSPF Virtual Link Authentication Configuration
Select values for Authentication Type and Authentication Key.
Click Apply Changes when finished.
Configuring Virtual Link Data
Open the OSPF Virtual Link Configurationpage.
Specify the area ID and neighbor router ID to configure.
Enter data into the fields as needed.
Click Configure Authentication to modify authentication.
Click Apply Changes when finished.
The virtual link data for the specified IDs is configured, and the device is updated.
Displaying Virtual Link Data
Open the OSPF Virtual Link Configurationpage.
Specify the area ID and neighbor router ID to display.
The virtual link data for these IDs displays.
Removing a Virtual Link
Open the OSPF Virtual Link Configurationpage.
Specify the Area ID and Neighbor Router ID associated with the virtual link to be removed.
The related virtual link data displays.
Click Delete.
The virtual link is removed, and the device is updated.
Configuring Virtual Link Data using the CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Virtual Link Summary
Use the OSPF Virtual Link Summarypage to display all of the configured virtual links.
To display the page, click Routing® OSPF® Virtual Link Summaryin the tree view.
Figure 10-18. OSPF Virtual Link Summary
The OSPF Virtual Link Summary page contains the following fields:
Area ID — The Area ID portion of the virtual link identification for which data is to be displayed. The Area ID and Neighbor Router ID together define a virtual link.
Neighbor Router ID — The neighbor portion of the virtual link identification. Virtual links may be configured between any pair of area border routers having interfaces to a common (non-backbone) area.
Hello Interval(secs) — The OSPF hello interval for the virtual link in units of seconds. The value for hello interval must be the same for all routers attached to a network.
Dead Interval(secs) — The OSPF dead interval for the virtual link in units of seconds. This specifies how long a router waits to see a neighbor router's Hello packets before declaring that the router is down. This parameter must be the same for all routers attached to a common network, and should be a multiple of the Hello Interval (i.e. 4).
Retransmit Interval(secs) — The OSPF retransmit interval for the virtual link in units of seconds. This specifies the time between link-state advertisements for adjacencies belonging to this router interface. This value is also used when retransmitting database descriptions and link-state request packets.
Iftransit Delay Interval(secs) — The OSPF Transit Delay for the virtual link in units of seconds. It specifies the estimated number of seconds it takes to transmit a link state update packet over this interface.
Displaying the Virtual Link Summary using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Route Redistribution Configuration
Use the OSPF Route Redistribution Configurationpage to configure redistribution in OSPF for routes learned through Static, Connected, and RIP. You can choose to redistribute routes learned from all of them or from selected ones.
To display the page, click Routing® OSPF® Route Redistribution Configurationin the tree view.
The OSPF Route Redistribution Configuration page contains the following fields:
Configured Source — A protocol configured for OSPF to redistribute the routes learned through this protocol. Only source routes that have been configured for redistribute by OSPF are available. Create allows you to configure a new source route.
Available Source — A protocol available for configuration for OSPF to re-distribute the routes. This box appears only if you select Create as Configured Source. Possible values are Static, Connected, and RIP.
Metric — Sets the metric value for redistributed routes. This field displays a metric value if the source was preconfigured. The valid values are 0 to 16777214.
Metric Type — Select the OSPF metric type of redistributed routes from the drop-down menu.
Tag — Sets the tag field in routes redistributed. This field displays a tag value if the source was preconfigured, otherwise 0 is displayed. The valid values are 0 to 4294967295.
Subnets — Select whether the subnetted routes should be redistributed or not from the drop-down menu.
Distribute List — Selects the Access List that filters the routes to be redistributed by the destination protocol. Only permitted routes are redistributed. If this command refers to a non-existent access list, all routes are permitted. The drop-down menu lists the ACLs configured from the Switching® Network Security® Access Control Lists® IP Access Control Lists pages. When used for route filtering, the only fields in an access list that get used are:
Source IP Address and netmask
Destination IP Address and netmask
Action (permit or deny)
All other fields (source and destination port, precedence, tos, etc.) are ignored.
The source IP address is compared to the destination IP address of the route. The source IP netmask in the access list rule is treated as a wildcard mask, indicating which bits in the source IP address must match the destination address of the route. (Note that a 1 in the mask indicates a Don't Care in the corresponding address bit.)
When an access list rule includes a destination IP address and netmask (an extended access list), the destination IP address is compared to the network mask of the route destination. The destination netmask in the access list serves as a wildcard mask, indicating which bits in the route's destination mask are significant for the filtering operation.
Creating an OSPF Route Redistribution Source
When no redistributions are configured, the system displays only Create in the Configured Source field and possible sources in the Available Source fields. When you select an Available Source, enter configuration data, and click Apply Changes, the item displays in the Configure Source dropdown list and is removed from the Available Source dropdown list.
Open the OSPF Route Redistribution Configurationpage.
Specify Create in the Configured Source field .
Select Static, Connected, or RIP from the Available Source field.
Click Apply Changes when finished.
The route redistribution data is configured, and the device is updated.
Modifying OSPF Route Redistribution Data
Open the OSPF Route Redistribution Configurationpage.
Select a source from the Configured Source dropdown.
Enter data in the fields as needed.
Click Apply Changes when finished.
The route redistrbution data is configured, and the device is updated.
Configuring OSPF Route Redistribution Data using CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
Route Redistribution Summary
Use the OSPF Route Redistribution Summarypage to display OSPF Route Redistribution configurations.
To display the page, click Routing® OSPF® Route Redistribution Summaryin the tree view.
Figure 10-20. OSPF Route Redistribution Summary
The OSPF Route Redistribution Summary page contains the following fields:
Source — The Source Route to be Redistributed by OSPF.
Metric — The Metric of redistributed routes for the given Source Route. Displays Unconfigured when not configured.
Metric Type — The OSPF metric type of redistributed routes.
Tag — The tag field in routes redistributed. This field displays the tag value if the source was preconfigured, otherwise 0 is displayed.
Subnets — Specifies whether the subnetted routes should be redistributed or not.
Distribute List — The Access List that filters the routes to be redistributed by the Destination Protocol.
Displaying the Route Redistribution Summary using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
BOOTP/DHCP Relay Agent
BootP/DHCP Relay Agent enables BootP/DHCP clients and servers to exchange BootP/DHCP messages across different subnets. The relay agent receives the requests from the clients, and checks the valid hops and giaddr fields. If the number of hops is greater than the configured, the agent assumes the packet is looped through the agents and discards the packet. If giaddr field is zero the agent must fill in this field with the IP address of the interface on which the request was received. The agent unicasts the valid packets to the next configured destination. The server responds with a unicast BOOTREPLY addressed to the relay agent closest to the client as indicated by giaddr field. Upon reception of the BOOTREPLY from the server, the agent forwards this reply as broadcast or unicast on the interface form where the BOOTREQUEST was arrived. This interface can be identified by giaddr field.
The 6200 series DHCP component also supports DHCP relay agent options to identify the source circuit when customers are connected to the Internet with high-speed modem. The relay agent inserts these options when forwarding the request to the server and removes them when sending the reply to the clients.
If an interface has more than one IP address, the relay agent should use the primary IP address configured as its relay agent IP address.
The BOOTP/DHCP Relay Agent menu page contains links to web pages that configure and display BOOTP/DHCP relay agent. To display this page, click Routing® BOOTP/DHCP Relay Agent in the tree view. Following are the web pages accessible from this menu page:
The BOOTP/DHCP Relay Agent Configuration page contains the following fields:
Maximum Hop Count — Enter the maximum number of hops a client request can take before being discarded.
Server IP Address — Enter either the IP address of the BOOTP/DHCP server or the IP address of the next BOOTP/DHCP Relay Agent.
Admin Mode — Select Enable or Disable from the drop-down menu. When you select Enable, BOOTP/DHCP requests are forwarded to the IP address you entered in the Server IP address field.
Minimum Wait Time(secs) — Enter a time in seconds. This value is compared to the time stamp in the client's request packets, which should represent the time since the client was powered up. Packets are only forwarded when the time stamp exceeds the minimum wait time.
Circuit ID Option Mode — Select Enable or Disable from the drop-down menu. If you select Enable, the relay agent adds Option 82 header packets to the DHCP Request packets before forwarding them to the server, and strips them off while forwarding the responses to the client.
Configuring BOOTP/DHCP
Open the BOOTP/DHCP Configurationpage.
Enter data in the fields as needed.
Click Apply Changes when finished.
The BOOTP/DHCP data is configured, and the device is updated.
Configuring BOOTP/DHCP using CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
DHCP and BOOTP Relay Commands
BOOTP/DHCP Relay Agent Status
Use the BOOTP/DHCP Relay Agent Statuspage to display the BOOTP/DHCP Relay Agent configuration and status information.
To display the page, click Routing® BOOTP/DHCP Relay Agent® Statusin the tree view.
Figure 10-22. BOOTP/DHCP Relay Agent Status
The BOOTP/DHCP Status page displays the following fields:
Maximum Hop Count — The maximum number of Hops a client request can go without being discarded.
Server IP Address — The IP address of the BOOTP/DHCP server or the IP address of the next BOOTP/DHCP Relay Agent.
Admin Mode — The administrative mode of the relay. When you select Enable on the configuration page, BOOTP/DHCP requests are forwarded to the IP address you entered in the Server IP address field.
Minimum Wait Time(secs) — The Minimum time in seconds. This value is compared to the time stamp in the client's request packets, which should represent the time since the client was powered up. Packets are only forwarded when the time stamp exceeds the minimum wait time.
Circuit ID Option Mode — This is the Relay agent option, which can be either Enabled or Disabled. If you select Enable, the relay agent adds Option 82 header packets to the DHCP Request packets before forwarding them to the server, and strips them off while forwarding the responses to the client.
Requests Received — The total number of BOOTP/DHCP requests received from all clients since the last time the switch was reset.
Requests Relayed — The total number of BOOTP/DHCP requests forwarded to the server since the last time the switch was reset.
Packets Discarded — The total number of BOOTP/DHCP packets discarded by this Relay Agent since the last time the switch was reset.
Displaying BOOTP/DHCP using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
DHCP and BOOTP Relay Commands
RIP
RIP is an Interior Gateway Protocol (IGP) based on the Bellman-Ford algorithm and targeted at smaller networks (network diameter no greater than 15 hops). The routing information is propagated in RIP update packets that are sent out both periodically and in the event of a network topology change. On receipt of a RIP update, depending on whether the specified route exists or does not exist in the route table, the router may modify, delete or add the route to its route table. Route preferences are conveyed through a configurable metric that indicates the distance for each destination.
The RIP menu page contains links to web pages that configure and display RIP parameters and data. To display this page, click Routing® RIP in the tree view. Following are the web pages accessible from this menu page:
Use the RIP Configurationpage to enable and configure or disable RIP in Global mode. To display the page, click Routing® RIP® Configurationin the tree view.
Figure 10-23. RIP Configuration
The RIP Configuration page contains the following fields:
RIP Admin Mode — Select Enable or Disable from the drop-down menu. If you select Enable,
RIP is enabled for the switch. The default is Disable.
Split Horizon Mode — Select None, Simple, or Poison Reverse from the drop-down menu. The default is Simple. Split horizon is a technique for avoiding problems caused by including routes in updates sent to the router from which the route was originally learned. The options are:
None — No special processing for this case.
Simple — A route is not included in updates sent to the router from which it was learned.
Poison Reverse — A route is included in updates sent to the router from which it was learned, but the metric is set to infinity.
Auto Summary Mode — Select Enable or Disable from the drop-down menu. If you select Enable, groups of adjacent routes are summarized into single entries, in order to reduce the total number of entries. The default is Enable.
Host Routes Accept Mode — Select Enable or Disable from the drop-down menu. If you select Enable, the router accepts host routes. The default is Enable.
Global Route Changes — Displays the number of route changes made to the IP Route Database by RIP. This does not include the refresh of a route's age.
Global Queries — Displays the number of responses sent to RIP queries from other systems.
Default Information Originate — Enable or Disable Default Route Advertise.
Default Metric — Sets a default for the metric of redistributed routes.This field displays the default metric if one has already been set, or blank if not configured earlier. Valid values are 1 to 15.
Configuring RIP
Open the RIP Configurationpage.
Enter data in the fields as needed.
Click Apply Changes when finished.
RIP is configured, and the device is updated.
Configuring RIP using the CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
Routing Information Protocol (RIP) Commands
RIP Interface Summary
Use the RIP Interface Summarypage to display RIP configuration status on an interface.
To display the page, click Routing® RIP® Interface Summaryin the tree view.
Figure 10-24. RIP Interface Summary
The RIP Interface Summary page displays the following fields:
Interface — The interface, such as the routing-enabled VLAN on which RIP is enabled.
IP Address — The IP Address of the router interface.
Send Version — Specifies the RIP version to which RIP control packets sent from the interface conform. The default is RIP-2. Possible values are:
RIP-1 — RIP version 1 packets are sent using broadcast.
RIP-1c — RIP version 1 compatibility mode. RIP version 2 formatted packets are transmitted using broadcast.
RIP-2 — RIP version 2 packets are sent using multicast.
None — RIP control packets are not transmitted.
Receive Version — Specifies which RIP version control packets are accepted by the interface. The default is Both. Possible values are:
RIP-1 — only RIP version 1 formatted packets are received.
RIP-2 — only RIP version 2 formatted packets are received.
Both — packets are received in either format.
None — no RIP control packets are received.
RIP Admin Mode — Specifies whether RIP is Enabled or Disabled on the interface.
Link State — Specifies whether the RIP interface is up or down.
Displaying RIP Interface Summary using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
Routing Information Protocol (RIP) Commands
RIP Interface Configuration
Use the RIP Interface Configurationpage to enable and configure or to disable RIP on a specific interface.
To display the page, click Routing® RIP® Interface Configurationin the tree view.
Figure 10-25. RIP Interface Configuration
The RIP Interface Configuration page contains the following fields:
Interface — Select the interface for which data is to be configured from the drop-down menu.
Send Version — RIP Version that router sends with its routing updates. The default is RIP-2. Possible values are:
RIP-1 — send RIP version 1 formatted packets through broadcast.
RIP-1c — RIP version 1 compatibility mode. Send RIP version 2 formatted packets through broadcast.
RIP-2 — send RIP version 2 packets using multicast.
None — no RIP control packets are sent.
Receive Version — RIP Version of the routing updates that the router must accept. The default is Both. Possible values are:
RIP-1 — accept only RIP version 1 formatted packets.
RIP-2 — accept only RIP version 2 formatted packets.
Both — accept packets in either format.
None — no RIP control packets is accepted.
RIP Admin Mode — Select Enable or Disable from the drop-down menu. Before you enable RIP version 1 or version 1c on an interface, you must first enable network directed broadcast mode on the corresponding interface. The default value is Disable.
Authentication Type — You may select an authentication type other than None by clicking the Modify button. You then see a new screen, where you can select the authentication type from the drop-down menu. Possible values are:
None — This is the initial interface state. If you select this option from the drop-down menu on the second screen and click Apply Changes, you are returned to the first screen without any authentication protocols being run.
Simple — If you select Simple you are prompted to enter an authentication key. This key is included, in the clear, in the RIP header of all packets sent on the network. All routers on the network must be configured with the same key.
Encrypt — If you select Encrypt you are prompted to enter both an authentication key and an authentication ID. Encryption uses the MD5 Message-Digest algorithm. All routers on the network must be configured with the same key and ID.
IP Address — Displays the IP Address of the router interface.
Link State — Specifies whether the RIP interface is up or down.
Bad Packets Received — Displays the number of RIP packets that were found to be invalid or corrupt. This explicitly does NOT include full updates sent containing new information.
Bad Routes Received — Displays the number of routes, in valid RIP packets, which were ignored for any reason, for example, the number of triggered RIP updates actually sent on this interface. This explicitly does NOT include full updates sent containing new information.
Updates Sent — Displays the number of Route updates sent.
Configuring the RIP Interface
Open the RIP Interface Configurationpage.
Specify the interface for which data is to be configured.
Enter data into the fields as needed:
Send Version — From the dropdown box, select None, RIP-1, RIP-1c, or RIP2.
Receive Version — From the dropdown box select None, RIP-1, RIP-2, or Both.
RIP Admin Mode — Select Enable or Disable.
Authentication Type — Click the Modify button to configure different Authentication Types.
Click Apply Changes when finished.
The RIP interface is configured, and the device is updated.
Selecting an Authentication Method
Open the RIP Interface Configurationpage.
Specify the interface for which the authentication method is to be configured.
Click Modify.
The Authentication Method page displays.
Specify the Authentication Type (None, Simple, or Encrypt) from the drop-down menu.
If you specify Simple or Encrypt as the Authentication Type, additional fields appear. Enter
the Authentication Key (Simple or Encrypt) and Authentication Key ID (Encrypt).
Click Apply Changes.
The authentication method is updated, and the device is updated.
Configuring the RIP Interface with the CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
Routing Information Protocol (RIP) Commands
RIP Route Redistribution Configuration
Use the RIP Route Redistribution Configurationpage to configure the RIP Route Redistribution parameters. The allowable values for each fields are displayed next to the field. If any invalid values are entered, an alert message is displayed with the list of all the valid values.
To display the page, click Routing® RIP® Route Redistribution Configurationin the tree view.
The RIP Route Redistribution Configuration page contains the following fields:
Configured Source — This select box is a dynamic selector and would be populated by only those Source Routes that have already been configured for redistribute by RIP. Create allows you to configure an Available Source Route.
Available Source — This select box is a dynamic selector and would be populated by only those Source Routes that have not previously been configured for redistribution by RIP. This select box would appear only if you select Create option as Configured Source. Possible values are:
Static
Connected
OSPF
Metric — Sets the metric value to be used as the metric of redistributed routes. This field displays the metric if the source was pre-configured and can be modified. The valid values are 1 to 15.
Distribute List — This select box sets the Access List that filters the routes to be redistributed by the destination protocol. Only permitted routes are redistributed.
The drop-down menu lists the ACLs configured through the pages under Switching® Network Security® Access Control Lists® IP Access Control Lists. When used for route filtering, the only fields in an access list that get used are:
Source IP Address and netmask
Destination IP Address and netmask
Action (Permit or Deny)
All other fields (source and destination port, precedence, tos, etc.) are ignored.
The source IP address is compared to the destination IP address of the route. The source IP netmask in the access list rule is treated as a wildcard mask, indicating which bits in the source IP address must match the destination address of the route. (Note that a 1 in the mask indicates a Don't Care in the corresponding address bit.)
When an access list rule includes a destination IP address and netmask (an extended access list), the destination IP address is compared to the network mask of the destination of the route. The destination netmask in the access list serves as a wildcard mask, indicating which bits in the route's destination mask are significant for the filtering operation.
Creating a Configured Source
Open the RIP Route Redistribution Configurationpage.
Select an Available Source to configure.
Specify values for the remaining fields.
Click Apply Changes.
The specified Source is now configured, and the device is updated.
Modifying a Configured Source
Open the RIP Route Redistribution Configurationpage.
Select the Configured Source to modify.
Change values on this screen as needed.
Click Apply Changes
Specified changes are saved, and the device is updated.
Configuring RIP Route Redistribution using CLI Command
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
Routing Information Protocol (RIP) Commands
RIP Route Redistribution Summary
Use the RIP Route Redistribution Summarypage to display Route Redistribution configurations.
To display the page, click Routing® RIP® Route Redistribution Summaryin the tree view.
Figure 10-27. RIP Route Redistribution Summary
The RIP Route Redistribution Summary page contains the following fields:
Source — The Source Route to be Redistributed by RIP.
Metric — The Metric of redistributed routes for the given Source Route. Displays Unconfigured when not configured.
Match — List of Routes redistributed when OSPF is selected as Source. The list may include one or more of:
Internal
External 1
External 2
NSSA-External 1
NSSA-External 2
N.A. (if not OSPF)
Distribute List — The Access List that filters the routes to be redistributed by the Destination Protocol. If the Distribute List is not configured, the field is blank.
Displaying RIP Route Redistribution Summary using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
Routing Information Protocol (RIP) Commands
Router Discovery
The Router Discovery protocol is used by hosts to identify operational routers on the subnet. Router Discovery messages are of two types: "Router Advertisements" and "Router Solicitations." The protocol mandates that every router periodically advertise the IP Addresses it is associated with. Hosts listen for these advertisements and discover the IP Addresses of neighboring routers.
The Router Discovery menu page contains links to web pages that configure and display Router Discovery data. To display this menu, click Routing® Router Discovery in the tree view. Following are the web pages accessible from this menu page:
Use the Router Discovery Configurationpage to enter or change Router Discovery parameters.
To display the page, click Routing® Router Discovery® Configurationin the tree view.
Figure 10-28. Router Discovery Configuration
The Router Discovery Configuration page contains the following fields:
VLAN Interface — Select the router interface for which data is to be configured.
Advertise Mode — Select Enable or Disable from the drop-down menu. If you select Enable, Router Advertisements are transmitted from the selected interface.
Advertise Address — Enter the IP Address to be used to advertise the router.
Maximum Advertise Interval(secs) — Enter the maximum time (in seconds) allowed between router advertisements sent from the interface.
Minimum Advertise Interval(secs) — Enter the minimum time (in seconds) allowed between router advertisements sent from the interface.
Advertise Lifetime(secs) — Enter the value (in seconds) to be used as the lifetime field in router advertisements sent from the interface. This is the maximum length of time that the advertised addresses are to be considered as valid router addresses by hosts.
Preference Level — Specify the preference level of the router as a default router relative to other routers on the same subnet. Higher numbered addresses are preferred. You must enter an integer.
Configuring Router Discovery
Open the Router Discovery Configurationpage.
Select the router interface to be configured.
Configure data as needed for the remaining fields.
Click Apply Changes
Specified configuration changes are saved, and the device is updated.
Configuring Router Discovery using the CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
Router Discovery Protocol Commands
Router Discovery Status
Use the Router Discovery Statuspage to display Router Discovery data for each port.
To display the page, click Routing® Router Discovery® Statusin the tree view.
Figure 10-29. Router Discovery Status
The Router Discovery Status page displays the following fields:
Interface — The router interface for which data is displayed.
Advertise Mode — The values are Enable or Disable. Enable denotes that Router Discovery is enabled on that interface.
Advertise Address — The IP Address used to advertise the router.
Maximum Advertise Interval(secs) — The maximum time (in seconds) allowed between router advertisements sent from the interface.
Minimum Advertise Interval(secs) — The minimum time (in seconds) allowed between router advertisements sent from the interface.
Advertise Lifetime(secs) — The value (in seconds) used as the lifetime field in router advertisements sent from the interface. This is the maximum length of time that the advertised addresses are to be considered as valid router addresses by hosts.
Preference Level — The preference level of the router as a default router relative to other routers on the same subnet. Higher numbered addresses are preferred.
Displaying Router Discovery Status using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
Router Discovery Protocol Commands
Router
The Router menu page contains links to web pages that configure and display route tables. To display this page, click Routing® Router in the tree view. Following are the web pages accessible from this menu page:
Use the Router Route Tablepage to display the route table configuration.
To display the page, click Routing® Router® Route Tablein the tree view.
Figure 10-30. Router Route Table
The Router Route Table page displays the following fields:
Total Number of Routes — The total number of routes in the route table.
Network Address — The IP route prefix for the destination.
Subnet Mask — Also referred to as the subnet/network mask, this indicates the portion of the IP interface address that identifies the attached network.
Protocol — This field tells which protocol created the specified route. The possibilities are one of the following:
Local
Static
Default
OSPF Intra
OSPF Inter
OSPF Type-1
OSPF Type-2
RIP
Next Hop Interface — The outgoing router interface to use when forwarding traffic to the destination.
Next Hop IP Address — The outgoing router IP address to use when forwarding traffic to the next router (if any) in the path towards the destination. The next router is always one of the adjacent neighbors or the IP address of the local interface for a directly attached network.
Displaying the Router Route Table using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
IP Routing Commands
Best Routes Table
Use the Router Best Routes Tablepage to display the best routes from the routing table.
To display the page, click Routing® Router® Best Routes Tablein the tree view.
Figure 10-31. Router Best Routes Table
The Router Best Routes Table page displays the following fields:
Total Number of Routes — The total number of routes in the route table.
Network Address — The IP route prefix for the destination.
Subnet Mask — Also referred to as the subnet/network mask, this indicates the portion of the IP interface address that identifies the attached network.
Protocol — This field tells which protocol created the specified route. The possibilities are one of the following:
Local
Static
Default
OSPF Intra
OSPF Inter
OSPF Type-1
OSPF Type-2
RIP
Next Hop Interface — The outgoing router interface to use when forwarding traffic to the destination.
Next Hop IP Address — The outgoing router IP address to use when forwarding traffic to the next router (if any) in the path towards the destination. The next router is always one of the adjacent neighbors or the IP address of the local interface for a directly attached network.
Displaying the Best Routes Table using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
IP Routing Commands
Route Entry Configuration
Use the Router Route Entry Configurationpage to add new and configure router routes.
To display the page, click Routing® Router® Route Entry Configurationin the tree view.
Figure 10-32. Router Route Entry Configuration
The Router Route Entry Configuration page contains the following fields:
Network Address — Specify the IP route prefix for the destination from the drop-down menu. In order to create a route, a valid routing interface must exist and the next hop IP Address must be on the same network as the routing interface. Routing interfaces are created on the IP Interface Configuration page. Valid next hop IP Addresses can be viewed on the Route Table page.
Subnet Mask — Also referred to as the subnet/network mask, this indicates the portion of the IP interface address that identifies the attached network.
Protocol — This field tells which protocol created the specified route. Possible values are:
Local
Static
Default
OSPF Intra
OSPF Inter
OSPF Type-1
OSPF Type-2
RIP
Next Hop Interface — The outgoing router interface to use when forwarding traffic to the destination.
Next Hop IP Address — The outgoing router IP address to use when forwarding traffic to the next router (if any) in the path towards the destination. The next router is always one of the adjacent neighbors or the IP address of the local interface for a directly attached network. When creating a route, the next hop IP must be on the same network as the routing interface. Valid next hop IP Addresses can be seen on the 'Route Table' page.
Metric — Administrative cost of the path to the destination. If no value is entered, default is 1. The range is 0–255.This field is present only when creating a static route.
Preference — Specifies a preference value for the configured next hop.
Adding a Router Route
Open the Router Route Entry Configurationpage.
Click Add Route.
The screen refreshes and the Router Route Entry Configuration page displays new fields as shown in Figure 10-33.
Figure 10-33. Add Route - Default Route Type
Next to Route Type, use the drop-down box to add a Default route or a Static route.
If you select Static, the page refreshes and new fields appear, as Figure 10-34 shows.
Default — Enter the default gateway address in the Next Hop IP Address field.
Static — Enter values for Network Address, Subnet Mask, Next Hop IP Address, and Preference.
Figure 10-34. Route Entry Configuration - Add Static Route Type
Click Apply Changes.
The new route is added, and you are redirected to the Configured Routes page.
Adding a Router Route using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
IP Routing Commands
Configured Routes
Use the Configured Routespage to display the routes that have been configured.
To display the page, click Routing® Router® Configured Routesin the tree view.
Figure 10-35. Configured Routes
The Configured Routes page displays the following fields:
Network Address — The IP route prefix for the destination.
Subnet Mask — Also referred to as the subnet/network mask, this indicates the portion of the IP interface address that identifies the attached network.
Next Hop IP — The outgoing router interface to use when forwarding traffic to the destination.
Preference — Displays the preferences configured for the added routes.
Remove — Use this checkbox to remove a configured route.
Adding a Router Route
Open the Configured Routespage.
Click Add.
The Router Route Entry Configuration page displays, as Figure 10-33 shows.
Next to Route Type, use the dropdown box to add a Default route or a Static route.
Default — Enter the default gateway address in the Next Hop IP Address field. Figure 10-33 shows the fields that display when the Route Type value is Default.
Static — Enter values for Network Address, Subnet Mask, Next Hop IP Address, and Preference. Figure 10-34 shows the fields that display when the Route Type value is Static.
Click Apply Changes.
The new route is added, and you are returned to the Configured Routes page.
Displaying Configured Routes using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
IP Routing Commands
Route Preferences Configuration
Use the Router Route Preferences Configurationpage to configure the default preference for each protocol (for example 60 for static routes). These values are arbitrary values that range from 1 to 255, and are independent of route metrics. Most routing protocols use a route metric to determine the shortest path known to the protocol, independent of any other protocol.
The best route to a destination is chosen by selecting the route with the lowest preference value. When there are multiple routes to a destination, the preference values are used to determine the preferred route. If there is still a tie, the route with the best route metric is chosen. To avoid problems with mismatched metrics (i.e. RIP and OSPF metrics are not directly comparable), you must configure different preference values for each of the protocols.
To display the page, click Routing® Router® Route Preferences Configurationin the tree view.
The Router Route Preferences Configuration page contains the following fields:
Local — This field displays the local route preference value.
Static — The static route preference value in the router. The default value is 1. The range is 1 to 255.
OSPF Intra — The OSPF intra route preference value in the router. The default value is 8. The range is 1 to 255. The OSPF specification (RFC 2328) requires that preferences must be given to the routes learned through OSPF in the following order: intra < inter < type-1 < type-2.
OSPF Inter — The OSPF inter route preference value in the router. The default value is 10. The range is 1 to 255. The OSPF specification (RFC 2328) requires that preferences must be given to the routes learned through OSPF in the following order: intra < inter < type-1 < type-2.
OSPF Type-1 — The OSPF type-1 route preference value in the router. The default value is 13. The range is 1 to 255. The OSPF specification (RFC 2328) requires that preferences must be given to the routes learned through OSPF in the following order: intra < inter < type-1 < type-2.
OSPF Type-2 — The OSPF type-2 route preference value in the router. The default value is 150. The range is 1 to 255. The OSPF specification (RFC 2328) requires that preferences must be given to the routes learned through OSPF in the following order: intra < inter < type-1 < type-2.
RIP — The RIP route preference value in the router. The default value is 15. The range is 1 to 255.
Configuring Route Preferences
Open the Route Preferences Configurationpage.
Define the applicable fields on this page
Click Apply Changes.
The route preferences are configured, and the device is updated.
Configuring Route Preferences using CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
OSPF Commands
VLAN Routing
You can configure 6200 series software with some VLANs that support routing. You can also configure the software to allow traffic on a VLAN to be treated as if the VLAN were a router port.
When a port is enabled for bridging (default) rather than routing, all normal bridge processing is performed for an inbound packet, which is then associated with a VLAN. Its MAC Destination Address (MAC DA) and VLAN ID are used to search the MAC address table. If routing is enabled for the VLAN, and the MAC DA of an inbound unicast packet is that of the internal bridge-router interface, the packet is routed. An inbound multicast packet is forwarded to all ports in the VLAN, plus the internal bridge-router interface, if it was received on a routed VLAN.
Since a port can be configured to belong to more than one VLAN, VLAN routing might be enabled for all of the VLANs on the port or for only some of the VLANs on the port. VLAN Routing can be used to allow more than one physical port to reside on the same subnet. It could also be used when a VLAN spans multiple physical networks, or when additional segmentation or security is required. This section shows how to configure the 6200 series software to support VLAN routing. A port can be either a VLAN port or a router port, but not both. However, a VLAN port may be part of a VLAN that is itself a router port.
The VLAN Routing menu page contains a link to a web page that displays VLAN Routing parameters and data. To display this page, click Routing® VLAN Routing in the tree view. The following web page is accessible from this menu page:
Use the VLAN Routing Summarypage to display information about the VLAN Routing interfaces configured on the system.
To display the page, click Routing® VLAN Routing® Summaryin the tree view.
Figure 10-37. VLAN Routing Summary
The VLAN Routing Summary page displays the following fields:
VLAN ID — The ID of the VLAN whose data is displayed in the current table row.
MAC Address — The MAC Address assigned to the VLAN Routing Interface.
IP Address — The configured IP Address of the VLAN Routing Interface. Note that if a VLAN is created and the IP address is not configured, the page by default shows an IP address of 0.0.0.0. To configure the IP address, go to IP® Interface Configuration.
Subnet Mask — The configured Subnet Mask of the VLAN Routing Interface. This is 0.0.0.0 when the VLAN Routing Interface is first configured and must be entered on the IP Interface Configuration page.
Displaying the VLAN Routing Summary using the CLI Command
For information about the CLI commands that perform this function, see the following chapters in the CLI Reference Guide:
IP Addressing Commands
Virtual LAN Routing Commands
VRRP
The Virtual Router Redundancy protocol is designed to handle default router failures by providing a scheme to dynamically elect a backup router. The driving force was to minimize "black hole" periods due to the failure of the default gateway router during which all traffic directed towards it is lost until the failure is detected. Though static configuration of default routes is popular, such an approach is susceptible to a single point of failure when the default router fails. VRRP advocates the concept of a "virtual router" associated with one or more IP Addresses that serve as default gateways. In the event that the VRRP Router controlling these IP Addresses (formally known as the Master) fails, the group of IP Addresses and the default forwarding role is taken over by a Backup VRRP Router.
The VRRP menu page contains links to web pages that configure and display parameters and data. To display this page, click Routing® VRRP in the tree view. Following are the web pages accessible from this menu page:
Use the VRRP Configurationpage to enable or disable the adminstrative status of a virtual router.
To display the page, click Routing® VRRP® VRRP Configurationin the tree view.
Figure 10-38. VRRP Configuration
The VRRP Configuration page contains the following field:
Admin Mode — This sets the administrative status of VRRP in the router to active or inactive. Select Enable or Disable from the drop-down menu. The default is Disable.
Changing VRRP Status using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
Virtual Router Redundancy Protocol Commands
Virtual Router Configuration
Use the Virtual Router Configuration page to create a new virtual router or to configure an existing one.
To display the page, click Routing® VRRP®Virtual Router Configuration in the tree view.
Figure 10-39. Virtual Router Configuration
The Virtual Router Configuration page contains the following fields:
VRID and Interface — Select Create from the drop-down menu to configure a new Virtual Router, or select one of the existing Virtual Routers, listed by interface number and VRID.
VRID — This field is only configurable if you are creating new Virtual Router, in which case enter the VRID in the range 1 to 255.
Interface — This field is only configurable if you are creating new Virtual Router, in which case select the interface for the new Virtual Router from the drop-down menu.
Pre-empt Mode — Select Enable or Disable from the drop-down menu. If you select Enable, a backup router preempts the master router if it has a priority greater than the master virtual router's priority provided the master is not the owner of the virtual router IP address. The default is Enable.
Priority — Enter the priority value to be used by the VRRP router in the election for the master virtual router. If the Virtual IP Address is the same as the interface IP Address, the priority gets set to 255 no matter what you enter. If you enter a priority of 255 when the Virtual and interface IP Addresses are not the same, the priority gets set to the default value of 100.
Advertisement Interval(secs) — Enter the time, in seconds, between the transmission of advertisement packets by this virtual router. Enter a number between 1 and 255. The default value is 1 second.
Interface IP Address — Indicates the IP Address associated with the selected interface.
IP Address — Enter the IP Address associated with the Virtual Router. The default is 0.0.0.0, which you must change prior to pressing Create.
Authentication Type — Select the type of Authentication for the Virtual Router from the drop-down menu. The default is None. The choices are:
0-None — No authentication is performed.
1-Simple — Authentication is performed using a text password.
Authentication Data — If you selected simple authentication, enter the password.
Status — Select active or inactive from the drop-down menu to start or stop the operation of the Virtual Router. The default is inactive.
If you wish to configure a Secondary VRRP address, first configure one IP address (the Primary address) for the VR. You can then add multiple Secondary addresses to that interface.
Creating a new Virtual Router
Open the Virtual Router Configurationpage.
Select Create from the VRID and Interface drop-down menu.
Specify the VRID and the interface for the new virtual router.
Define the remaining fields as needed.
Click Create.
The new virtual router is saved, and the device is updated.
Configuring a Virtual Router
Open the Virtual Router Configurationpage.
Select the VRID and interface of the virtual router to configure.
Change fields as needed.
Click Apply Changes.
The configuration is saved, and the device is updated.
Configuring a Virtual Router using the CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
Virtual Router Redundancy Protocol Commands
Virtual Router Status
Use the Virtual Router Statuspage to display virtual router status.
To display the page, click Routing® VRRP®Virtual Router Status in the tree view.
Figure 10-40. Virtual Router Status
The Virtual Router Status page displays the following fields:
VRID — Virtual Router Identifier.
VLANID - Indicates the interface associate with the VRID.
Priority — The priority value used by the VRRP router in the election for the master virtual router.
Pre-empt Mode
Enable — If the Virtual Router is a backup router it preempts the master router if it has a priority greater than the master virtual router's priority provided the master is not the owner of the virtual router IP address.
Disable — If the Virtual Router is a backup router it does not preempt the master router even if its priority is greater.
Advertisement Interval(secs) — The time, in seconds, between the transmission of advertisement packets by this virtual router.
Virtual IP Address — The IP Address associated with the Virtual Router.
Interface IP Address — The actual IP Address associated with the interface used by the Virtual Router.
Owner — Set to True if the Virtual IP Address and the Interface IP Address are the same, otherwise set to False. If this parameter is set to True, the Virtual Router is the owner of the Virtual IP Address, and always wins an election for master router when it is active.
VMAC Address — The virtual MAC Address associated with the Virtual Router, composed of a 24-bit organizationally unique identifier, the 16-bit constant identifying the VRRP address block and the 8-bit VRID. The Virtual MAC address is 00:00:5e:00:01:XX where XX is the VRID.
Auth Type — The type of authentication in use for the Virtual Router
None — Specifies that the authentication type is none.
Simple — Specifies that the authentication type is a simple text password.
State — The current state of the Virtual Router:
Initialize
Master
Backup
Status — The current status of the Virtual Router:
Inactive
Active
Secondary IP Address — A secondary VRRP address configured for the primary VRRP.
Displaying Virtual Router Status using the CLI Commands
For information about the CLI commands that perform this function, see the following chapter in the CLI Reference Guide:
Virtual Router Redundancy Protocol Commands
Virtual Router Statistics
Use the Virtual Router Statisticspage to display statistics for a specified virtual router.
To display the page, click Routing® VRRP® Virtual Router Statisticsin the tree view.
Figure 10-41. Virtual Router Statistics
The Virtual Router Statistics page contains the fields listed below. Many of the fields display only when there is a valid VRRP configuration.
Router Checksum Errors — The total number of VRRP packets received with an invalid VRRP checksum value.
Router Version Errors — The total number of VRRP packets received with an unknown or unsupported version number.
Router VRID Errors — The total number of VRRP packets received with an invalid VRID for this virtual router.
VRID and VLAN ID — Select the existing Virtual Router, listed by interface number and VRID, for which you want to display statistical information.
VRID — the VRID for the selected Virtual Router.
VLAN ID — The interface for the selected Virtual Router.
Up Time — The time, in days, hours, minutes and seconds, that has elapsed since the virtual router transitioned to the initialized state.
State Transitioned to Master — The total number of times that this virtual router's state has transitioned to Master.
Advertisement Received — The total number of VRRP advertisements received by this virtual router.
Advertisement Interval Errors — The total number of VRRP advertisement packets received for which the advertisement interval was different than the one configured for the local virtual router .
Authentication Failure — The total number of VRRP packets received that did not pass the authentication check.
IP TTL Errors — The total number of VRRP packets received by the virtual router with IP TTL (Time-To-Live) not equal to 255.
Zero Priority Packets Received — The total number of VRRP packets received by the virtual router with a priority of 0.
Zero Priority Packets Sent — The total number of VRRP packets sent by the virtual router with a priority of 0.
Invalid Type Packets Received — The number of VRRP packets received by the virtual router with an invalid value in the Type field.
Address List Errors — The total number of packets received for which the address list does not match the locally configured list for the virtual router.
Invalid Authentication Type — The total number of packets received with an unknown authentication type.
Authentication Type Mismatch — The total number of packets received with an authentication type different to the locally configured authentication method.
Packet Length Errors — The total number of packets received with a packet length less than the length of the VRRP header.
Displaying Virtual Router Statistics
Open the Virtual Router Statisticspage.
Select the virtual router for which you want to display statistical information from the VRID
and VLANID field. This information displays only if there is a valid VRRP configuration.
Displaying Virtual Router Statistics using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
Virtual Router Redundancy Protocol Commands
Tunnels
The 6200 series provides for the creation, deletion, and management of tunnel interfaces. These are dynamic interfaces that are created and deleted through user-configuration.
There are two classes of tunnels that facilitate the transition of IPv4 networks to IPv6 networks: configured and automatic. The distinction is that configured tunnels are explicitly configured with a destination or endpoint of the tunnel. Automatic tunnels, in contrast, infer the endpoint of the tunnel from the destination address of packets routed into the tunnel.
The 6200 series supports point-to-point tunnels. Point-to-point interfaces provide for routing based only on interface (an explicit next-hop address need not be specified), and allow for the definition of unnumbered interfaces.
The Tunnels menu page contains links to web pages that configure and display tunnel parameters and data. To display this page, click Routing® Tunnels in the tree view. Following are the web pages accessible from this menu page:
Use the Tunnels Configurationpage to create, configure, or delete a tunnel.
To display the page, click Routing® Tunnels® Configurationin the tree view.
Figure 10-42. Tunnels Configuration
The Tunnels Configuration page contains the following fields:
Tunnel — Use the drop-down menu to select from the list of currently configured tunnel IDs. Create is also a valid choice if the maximum number of tunnel interfaces has not been created.
Tunnel ID — When Create is chosen from the tunnel selector this list of available tunnel IDs becomes visible. You must select a tunnel ID to associate with the new tunnel and click Apply Changes before the remaining fields on the page display.
Mode — Selector for the Tunnel mode. IPV6-in-IPV4 is the only supported mode.
Link Local Only Mode — Enable IPv6 on this interface using the Link Local address. This option is only configurable prior to specifying an explicit IPv6 address.
IPv6 Address —Select an IPv6 addresses for the selected Tunnel interface. Add is also a valid choice if the maximum number of addresses has not been configured.
IPv6 Address — When Add is chosen from the IPv6 Address selector this IPv6 address input field becomes visible. Address must be entered in the format prefix/length.
You also have the option to specify the 64-bit extended unique identifier (EUI-64).
Source — Select the desired source, IPv4 Address or Interface. If Address is selected, the source address for this tunnel must be entered in dotted decimal notation. If Interface is selected the source interface for this tunnel must be selected. The address associated with the selected interface is used as the source address.
Destination Address — The IPv4 destination address for this tunnel in dotted decimal notation.
Creating a New Tunnel
Open the Tunnels Configurationpage.
Select Create from the Tunnel drop-down menu.
Specify an ID to use in the Tunnel ID field.
Click Apply Changes.
The Tunnel ID field is removed, and the remaining tunnel fields display.
Figure 10-43. Tunnels Configuration - Entry
Configure the fields as needed.
Enter desired values in the remaining fields.
Click Apply Changes.
The new tunnel is saved, and the device is updated.
Modifying an Existing Tunnel
Open the Tunnels Configurationpage.
Specify the tunnel to modify in the Tunnel drop-down menu.
Change field values as desired in the remaining fields.
Click Apply Changes.
The new configuration is saved, and the device is updated.
Removing a Tunnel
Open the Tunnels Configurationpage.
Specify the tunnel to remove in the Tunnel drop-down menu.
Click Delete Tunnel.
The tunnel is deleted, and the device is updated.
Configuring a Tunnel using CLI Commands
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
Tunnel Interface Commands
Tunnels Summary
Use the Tunnels Summarypage to display a summary of configured tunnels.
To display the page, click Routing® Tunnels® Summaryin the tree view.
Figure 10-44. Tunnels Summary
The Tunnels Summary page contains the following fields:
Tunnel ID — The Tunnel ID.
Mode — The corresponding mode of the Tunnel.
Address — The IPv6 Address(es) of the Tunnel.
Source — The corresponding Tunnel Source Address. In the case where an interface has been configured both the interface and the address are displayed. If the source interface has no address configured the text 'unconfigured' is displayed in place of the address.
Destination — The corresponding Tunnel Destination Address.
Displaying Tunnels Summary using the CLI Command
For information about the CLI command that performs this function, see the following chapter in the CLI Reference Guide:
Tunnel Interface Commands
Loopbacks
The 6200 series provides for the creation, deletion, and management of loopback interfaces. They are dynamic interfaces that are created and deleted through user-configuration. The 6200 series supports multiple loopback interfaces.
A loopback interface is always expected to be up. As such, it provides a means to configure a stable IP address on the device that may be referred to by other switches. This interface provides the source address for sent packets and can receive both local and remote packets. It is typically used by routing protocols.
The loopback does not behave like the network port on Switching systems. In particular, there are no neighbors on a loopback interface. It is a pseudo-device for assigning local addresses so that the router can be communicated with by this address, which is always up and can receive traffic from any of the existing active interfaces. Thus, given reachability from a remote client, the address of the loopback can be used to communicate with the router through various services such as telnet and ssh. In this way, the address on a loopback behaves identically to any of the local addresses of the router in terms of the processing of incoming packets.
The Loopbacks menu page contains links to web pages that configure and display loopback parameters and data. To display this page, click Routing® Loopbacks in the tree view. Following are the web pages accessible from this menu page:
Loopbacks Configuration
Loopbacks Summary
Loopbacks Configuration
Use the Loopbacks Configurationpage to create, configure, or remove loopback interfaces. You can also set up or delete a secondary address for a loopback.
To display the page, click Routing® Loopbacks® Configurationin the tree view.
Figure 10-45. Loopback Configuration
The Loopbacks Configuration pages contain the following fields:
Loopback — Use the drop-down menu to select from the list of currently configured loopback interfaces. Create is also a valid choice if the maximum number of loopback interfaces has not been created.
Loopback ID — When Create is selected in the Loopback field, this list of available loopback ID's displays.
Protocol — Select IPv4 or IPv6 to configure the corresponding attributes on the loopback interface. The protocol selected affects the fields that are displayed on this page.
Link Local Only Mode — Enable IPv6 on this interface using the Link Local address. This option only displays when the Protocol specified is IPv6, and is only configurable prior to specifying an explicit IPv6 address.
IPv6 Address — Select list of configured IPv6 addresses for the selected Loopback interface. Add is also a valid choice if the maximum number of addresses has not been configured. This option only displays when the Protocol specified is IPv6.
IPv6 Address — When Add is chosen from the IPv6 Address selector this IPv6 address input field becomes visible. Enter the address in the format of prefix/length. This option only displays when the Protocol specified is IPv6.
EU164 — You also have the option to specify the 64-bit extended unique identifier (EUI-64). This option only displays when the Protocol specified is IPv6.
IPv4 Address — The primary IPv4 address for this interface in dotted decimal notation. This option only displays when the Protocol specified is IPv4.
IPv4 Subnet Mask — The primary IPv4 subnet mask for this interface in dotted decimal notation. This option only displays when the Protocol specified is IPv4.
The following fields display when a primary address is configured. You can configure multiple secondary addresses.
Secondary Address — Select a configured IPv4 secondary address for the selected Loopback interface from the drop-down menu. A new address can be entered in the Secondary IP Address field by selecting Add Secondary IP Address here (if the maximum number of secondary addresses has not been configured). A primary address must be configured before a secondary address can be added.
Secondary IP Address — The secondary IP address for this interface in dotted decimal notation. This input field is visible only when Add Secondary is selected.
Secondary Subnet Mask — The secondary subnet mask for this interface in dotted decimal notation. This input field is visible only when Add Secondary is selected.
Creating a New Loopback (IPv4)
Open the Loopbacks Configurationpage.
Select Create from the Loopback drop-down menu.
Specify an ID to use in the Loopback ID field.
Click Apply Changes.
The Loopback ID field goes away, and the remaining loopback fields display.
