NOTE: CLI commands are not available for all the Routing pages.
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 PowerConnect 6200 Series software to be handled appropriately.
The PowerConnect 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 have between 256 and 896 entries 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:
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.
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.
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.
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. The IP configuration settings allow you to enable or disable the generation of various types of ICMP messages.
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.
•
ICMP Echo Replies —Select Enable to allow the switch to generate ECHO reply messages. Select Disable to prevent the switch from generating ICMP echo replies.
•
ICMP Redirects — Select Enable to allow the switch to generate ICMP redirect messages. Select Disable to prevent the switch from generating ICMP redirect messages. The ICMP Redirect feature is also configurable on each interface.
•
ICMP Rate Limit Interval — To control the ICMP error packets, you can specify the number of ICMP error packets that are allowed per burst interval. By default, the rate limit is 100 packets per second, i.e. the burst interval is 1000 milliseconds. To disable ICMP rate limiting, set this field to zero. The valid rate interval range is 0 to 2147483647 milliseconds.
•
ICMP Rate Limit Burst Size — To control the ICMP error packets, you can specify the number of ICMP error packets that are allowed per burst interval. By default, the rate limit is 100 packets.
•
Maximum Next Hops — The maximum number of hops supported by the switch. This is a compile-time constant.
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, and so on). 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.
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.
Use the IP Interface Configurationpage to update IP interface data for this switch. The IP interface configuration includes the ability to configure the bandwidth, Destination Unreachable messages, and ICMP Redirect messages.
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.
•
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 9198). The default value is 1500.
•
Bandwidth — Specifies the configured bandwidth on this interface for the OSPF link cost calculation. This setting does not affect the actual speed of an interface, and the speed of the interface is communicated to higher level protocols. The valid range is (1 to 10000000).
•
Destination Unreachables — Select Enable to allow the interface to generate ICMP Destination Unreachable messages on this interface. Select Disable to prevent the interface from generating ICMP Destination Unreachable messages on this interface. By default, the Destination Unreachables mode is Enable.
•
ICMP Redirects — Select Enable to allow the interface to generate ICMP redirect messages. Select Disable to prevent the interface from generating ICMP redirect messages. The ICMP Redirect feature is also configurable globally. If the ICMP Redirect feature is enabled on the interface, it must be enabled globally in order for the interface to generate ICMP redirect messages.
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 PowerConnect 6200 Series software 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:
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 active 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.
•
Opaque LSA Status — Set this parameter to Enable if OSPF should store and flood opaque LSAs. An opaque LSA is used for flooding user-defined information within an OSPF router domain.
•
Exit Overflow Interval — 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 — 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 — 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.
•
AS_OPAQUE LSA Count — Shows the number of opaque LSAs with domain wide flooding scope.
•
AS_OPAQUE LSA Checksum — Shows the sum of the LS checksums of the opaque LSAs with domain wide flooding scope. 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.
•
External LSDB Limit — The maximum number of AS-External-LSAs that can be stored in the database. A value of -1 implies there is no limit on the number that can be saved. The valid range of values is -1 to 2147483647.
•
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. Enter 0 to unconfigure.
•
Maximum Paths — Configure the maximum number of paths that OSPF can report to a given destination. The valid values are 1 to 4.
•
AutoCost Reference Bandwidth — This field configures the value that OSPF uses in calculating the default metric for an interface. OSPF calculates the link cost of each interface as Cost = (Reference Bandwidth in Mbps) / (Interface Bandwidth). For example, setting this value to 1000 Mbps would cause all 1-Gbps interfaces to have a default cost of 1000/1000 = 1. For 100 Mbps interfaces, the default cost would be 1000/100 = 10.
•
Default Passive Setting — Enable this setting to make all interfaces on the switch operate in passive mode passive. Configuring this field overwrites any present interface level passive mode setting. OSPF does not form adjacencies on passive interfaces, but it does advertise attached networks as stub networks. Interfaces are not passive by default. It is common to configure an OSPF interface to be passive when OSPF must advertise the subnets configured on the interface, but routers on the subnet belong to other OSPF domains, such as an OSPFv3 router at the end of a 6to4 tunnel.
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. If a Stub Area has been created, the fields in the Stub Area Information are available. If a NSSA has been created, the fields in the NSSA Area Information are available.
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.
Import Summary LSAs — Select Enable or Disable from the drop-down menu. If you select Enable summary LSAs is imported into stub areas.
•
Type of Service — Specifies the parameters for the type of service requested. The parameters may be utilized by networks to define the handling of the datagram during transport The type of service is associated with the stub metric. The switch supports Normal only
•
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.
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 check box if you wish to add an area range.
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.
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.
•
Sent Packets — The number of OSPF packets transmitted on the interface.
•
Received Packets — The number of valid OSPF packets received on the interface.
•
Discards — The number of received OSPF packets discarded because of an error in the packet or an error in processing the packet.
•
Bad Version — The number of received OSPF packets whose version field in the OSPF header does not match the version of the OSPF process handling the packet.
•
Source Not On Local Subnet — The number of received packets discarded because the source IP address is not within a subnet configured on a local interface.
•
Virtual Link Not Found — The number of received OSPF packets discarded where the ingress interface is in a non-backbone area and the OSPF header identifies the packet as belonging to the backbone, but OSPF does not have a virtual link to the packet's sender.
•
Area Mismatch — The number of OSPF packets discarded because the area ID in the OSPF header is not the area ID configured on the ingress interface.
•
Invalid Destination Address — The number of OSPF packets discarded because the packet's destination IP address is not the address of the ingress interface and is not the AllDrRouters or AllSpfRouters multicast addresses.
•
Wrong Authentication Type — The number of packets discarded because the authentication type specified in the OSPF header does not match the authentication type configured on the ingress interface.
•
Authentication Failure — The number of OSPF packets dropped because the sender is not an existing neighbor or the sender's IP address does not match the previously recorded IP address for that neighbor.
•
No Neighbor at Source Address — The number of OSPF packets dropped because the sender is not an existing neighbor or the sender's IP address does not match the previously recorded IP address for that neighbor.
•
Invalid OSPF Packet Type — The number of OSPF packets discarded because the packet type field in the OSPF header is not a known type.
•
Hellos Ignored — The number of received Hello packets that were ignored by this router from the new neighbors after the limit has been reached for the number of neighbors on an interface or on the system as a whole.
•
Hellos Sent — The number of Hello packets sent on this interface by this router.
•
Hellos Received — The number of Hello packets received on this interface by this router.
•
DD Packets Sent — The number of Database Description packets sent on this interface by this router.
•
DD Packets Received — The number of Database Description packets received on this interface by this router.
•
LS Requests Sent — The number of LS Requests sent on this interface by this router.
•
LS Requests Received — The number of LS Requests received on this interface by this router.
•
LS Updates Sent — The number of LS updates sent on this interface by this router.
•
LS Updates Received — The number of LS updates received on this interface by this router.
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.
•
Advertise Secondaries — Select Enable or Disable from the drop-down menu to indicate the advertiseability of all secondary addresses. By default all the secondary addresses would be advertised on an interface enabled for OSPF.
•
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 — 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 — 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 — 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.
•
LSA Ack Interval — The number of seconds between LSA Acknowledgment packet transmissions, which must be less than the Retransmit Interval.
•
Interface Delay Interval — 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.
•
Passive Mode — Enable this mode to make the interface passive to prevent OSPF from forming an adjacency on an interface. OSPF advertises networks attached to passive interfaces as stub networks. Interfaces are not passive by default. It is common to configure an OSPF interface to be passive when OSPF must advertise the subnets configured on the interface, but routers on the subnet belong to other OSPF domains, such as an OSPFv3 router at the end of a 6to4 tunnel.
•
Network Type — Sets the OSPF network type on the interface to broadcast or point-to-point.
–
Broadcast — OSPF only selects a designated router and originates network LSAs for broadcast networks. The default network type for Ethernet interfaces is broadcast.
–
Point-to-Point — When there are only two routers on the network, OSPF can operate more efficiently by treating the network as a point-to-point network. For point-to-point networks, OSPF does not elect a designated router or generate a network link state advertisement (LSA). Both endpoints of the link must be configured to operate in point-to-point mode.
•
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.
•
AuthKey — Enter the OSPF Authentication Key for the specified interface. If you do not choose to use authentication you will not be prompted to enter a key. If you choose 'simple' authentication you cannot use a key of more than 8 octets. If you choose 'encrypt' the key may be up to 16 octets long. The key value will only be displayed if you are logged on with Read/Write privileges, otherwise it will be displayed as asterisks.
•
AuthKeyID — Enter the ID to be used for authentication. You will only be prompted to enter an ID when you select Encrypt as the authentication type. The ID is a number between 0 and 255, inclusive.
•
State — If the OSPF admin mode is enabled, this field shows the current state of the selected router interface. If the OSPF admin mode is disabled, this field is blank. 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 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.
•
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.
•
Local Link LSAs — The number of opaque LSAs whose flooding scope is the link on this interface.
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.
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.
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.
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.
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 an effort should be made to contact the neighbor (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.
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:
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.
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.
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.
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.
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 with 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.
Use the OSPF Route Redistribution Configurationpage to configure redistribution in OSPF for routes learned through various protocols. You can choose to redistribute routes learned from all available protocols or from selected ones.
The OSPF Route Redistribution Configuration page contains the following fields:
•
Source — A protocol configured for OSPF to redistribute the routes learned through this protocol. Only source routes that have been configured for redistribution by OSPF are available. 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:
Redistribute — Enables or disables the redistribution for the selected source protocol. This field has to be enabled in order to be able to configure any of the route redistribution attributes.
Graceful restart uses the concept of “helpful neighbors”. A fully adjacent router enters helper mode when it receives a link state announcement (LSA) from the restarting management unit indicating its intention of performing a graceful restart. In helper mode, a switch continues to advertise to the rest of the network that they have full adjacencies with the restarting router, thereby avoiding announcement of a topology change and and the potential for flooding of LSAs and shortest-path-first (SPF) runs (which determine OSPF routes). Helpful neighbors continue to forward packets through the restarting router. The restarting router relearns the network topology from its helpful neighbors.
Graceful restart can be enabled for either planned or unplanned restarts, or both. A planned restart is initiated by the operator (see Enabling and Disabling NSF). The operator may initiate a failover in order to take the management unit out of service (for example, to address a partial hardware failure), to correct faulty system behavior which cannot be corrected through less severe management actions, or other reasons. An unplanned restart is an unexpected failover caused by a fatal hardware failure of the management unit or a software hang or crash on the management unit.
Planned — OSPF will perform a graceful restart for planned restarts. A planned restart is a failover initiated by the administrator (see Enabling and Disabling NSF).
–
Always — OSPF will perform a graceful restart for all planned and unplanned warm restart events.
–
Disable — OSPF will not perform graceful restarts.
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.
T he PowerConnect 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.
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.
The IP Helper feature allows the switch to forward certain configured UDP broadcast packets to a particular IP address. This allows various applications, such as the DHCP relay agent, to reach servers on non-local subnets, even if the application was designed to assume a server is always on a local subnet and uses broadcast packets (with either the limited broadcast address 255.255.255.255, or a network directed broadcast address) to reach the server.
You can configure relay entries both globally and on specific routing interfaces. Each relay entry maps an ingress interface and destination UDP port number to a single IPv4 address (the helper address). You can configure multiple relay entries for the same interface and UDP port, in which case the relay agent relays matching packets to each server address. Interface configuration takes priority over global configuration. In other words, if the destination UDP port of a packet matches any entry on the ingress interface, the packet is handled according to the interface configuration. If the packet does not match any entry on the ingress interface, the packet is handled according to the global IP helper configuration.
The IP Helper Global Configuration page contains the following fields:
•
UDP Relay Mode — Use the menu to enable or disable the UDP relay mode. You must enable the UDP Relay Mode to relay any other protocols for which an IP helper address has been configured. By default UDP Relay Mode is Enabled.
•
UDP Destination Port — Identifies destination UDP port number of UDP packets to be relayed. Table 9‑21 lists UDP Port allocations.
NOTE: If the DefaultSet option is specified, the device by default forwards UDP Broadcast packets for the following services: IEN-116 Name Service (port 42), DNS (port 53), NetBIOS Name Server (port 137), NetBIOS Datagram Server (port 138), TACACS Server (Port 49), and Time Service (port 37).
The IP Helper Interface Configuration page contains the following fields:
•
Source IP Interface — Select the interface to use for UDP/Helper relays. Select All to configure relay entries on all available interfaces.
•
UDP Destination Port — Identifies destination UDP port number of UDP packets to be relayed. For a list of UDP Port allocations, see Table 9‑21.
•
Server Address — The IPv4 address of the server to which packets are relayed for the specific UDP Destination Port.
•
IsDiscard — If True, packets arriving on the given interface with the given destination UDP port are discarded rather than relayed. Discard entries are used to override global IP helper address entries which otherwise might apply to a packet.
•
Hit Count — The number of times a packet has been forwarded or discarded according to this entry.
•
Remove — Select this option and click Apply Changes to remove the relay from the selected source IP interface.
NOTE: If the DefaultSet option is specified, the device by default forwards UDP Broadcast packets for the following services: IEN-116 Name Service (port 42), DNS (port 53), NetBIOS Name Server (port 137), NetBIOS Datagram Server (port 138), TACACS Server (Port 49), and Time Service (port 37).
The IP Helper Statistics page contains the following fields:
•
DHCP Client Messages Received — The number of valid messages received from a DHCP client. The count is only increased if IP helper is enabled globally, the ingress routing interface is up, and the packet passes a number of validity checks, such as having a TTL >1 and having valid source and destination IP addresses.
•
DHCP Client Messages Relayed — The number of DHCP client messages relayed to a server. If a message is relayed to multiple servers, the count is increased once for each server.
•
DHCP Server Messages Received — The number of DHCP responses received from the DHCP server. This count only includes messages that the DHCP server unicasts to the relay agent for relay to the client.
UDP Client Messages Received — The number of valid UDP packets received. This count includes DHCP messages and all other protocols relayed. Conditions are similar to those for the first statistic in this table.
•
UDP Client Messages Relayed — The number of UDP packets relayed. This count includes DHCP messages relayed as well as all other protocols. The count is increased for each server to which a packet is sent.
•
DHCP Client Messages Hop Count Exceeded Max — The number of DHCP client messages received whose hop count is larger than the maximum allowed. The maximum hop count is a configurable value.A log message is written for each such failure. The DHCP relay agent does not relay these packets.
•
DHCP Pkts Rcvd Too Early — The number of DHCP client messages received whose secs field is less than the minimum value. The minimum secs value is a configurable value. A log message is written for each such failure. The DHCP relay agent does not relay these packets.
•
Received DHCP Client Messages With Giaddr As Local Address — The number of DHCP client messages received whose gateway address, giaddr, is already set to an IP address configured on one of the relay agents own IP addresses. In this case, another device is attempting to spoof the relay agents address. The relay agent does not relay such packets. A log message gives details for each occurrence.
•
UDP Pkts With Expired TTL — The number of packets received with TTL of 0 or 1 that might otherwise have been relayed.
•
UDP Pkts Discarded — The number of packets ignored by the relay agent because they match a discard relay entry.
Routing Information Protocol (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.
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:
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 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.
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.
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.
NOTE: For a static reject route, the next hop interface value is Null0. Packets to the network address specified in static reject routes are intentionally dropped.
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 — Select the Access List that filters the routes to be redistributed by the destination protocol. Only permitted routes are redistributed.
Redistribute — Enables or disables the redistribution for the selected source protocol. This field has to be enabled in order to be able to configure any of the route redistribution attributes.
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 0 when not configured.
•
Redistribute — Shows whether route redistribution is enabled for the source.
•
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.
•
Match — Shows the list of routes redistributed when OSPF is selected as the source, which can be any of the following:
–
Match Internal — Shows whether redistribution of OSPF internal routes is enabled.
–
Match External Type 1 — Shows whether the redistribution of OSPF external type 1 routes is enabled.
–
Match External Type 2— Shows whether the redistribution of OSPF external type 2 routes is enabled.
–
Match NSSA External Type 1 — Shows whether the redistribution of OSPF NSSA external type 1 routes is enabled.
–
Match NSSA External Type 2— Shows whether the redistribution of OSPF NSSA external type 2 routes is enabled.
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:
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.
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.
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:
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:
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.
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:
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.
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:
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.
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 check box to remove a configured route.
The Router Route Entry Configuration page displays, as Figure 9‑38 shows.
3.
Next to Route Type, use the drop-down box to add a Default route or a Static route.
Default — Enter the default gateway address in the Next Hop IP Address field. Figure 9‑38 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 9‑39 shows the fields that display when the Route Type value is Static.
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.
NOTE: For a static reject route, the next hop interface value is Null0. Packets to the network address specified in static reject routes are intentionally dropped.
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 110.
•
OSPF Inter — The OSPF inter route preference value in the router. The default value is 110.
•
OSPF External — The OSPF External route preference value in the router (OSPF External are OSPF Type-1 and OSPF Type-2 routes). The default value is 110.
•
RIP — The RIP route preference value in the router. The default value is 120.
You can configure PowerConnect 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 PowerConnect 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:
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: If a VLAN is created and the IP address is not configured, the web page by default shows an IP address of 0.0.0.0. To configure the IP address, go to the Routing → IP → Interface Configuration page. See 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 Routing → IP → Interface Configuration page.
The Virtual Router Redundancy (VRRP) 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:
The VRRP 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.
•
Configured 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.
•
Priority — The operational priority of the VRRP router, which is relative to the configured priority and depends on the priority decrements configured through tracking process. The priority and configured priority are the same unless a tracked event (for example a tracked interface is down) has occurred to change the value.
•
Advertisement Interval — 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:
Open the Router Configurationpage. Because you first configured the primary address, now the Secondary IP Address button appears at the bottom of the page.
Track Interface — Select an interface for the VRRP router to track.
o
Priority Decrement — When a tracked interface goes down, the priority decrement specifies the amount that the router priority will be decreased. The valid range is 1 to 254. The default value is 10.
Priority Decrement — When a tracked route becomes unreachable, the priority decrement specifies the amount that the router priority will be decreased. The valid range is 1 to 254. The default value is 10.
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.
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
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 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.
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.
The PowerConnect 6200 Series switches support the creation, deletion, and management of tunnel interfaces. These are dynamic interfaces that are created and deleted through user-configuration. Each switch also supports the functionality of a 6to4 border router that connects a 6to4 site to a 6to4 domain. It sends and receives tunneled traffic from routers in a 6to4 domain that includes other 6to4 border routers and 6to4 relay routers.
The PowerConnect 6200 Series supports point-to-point tunnels. Point-to-point interfaces provide for routing based only on the 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:
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, which can be one of the following:
–
6-in-4-configured — The 6in4 tunnel mode is configured rather than automatic.
–
6-to-4 — 6to4 tunnels are automatically formed IPv4 tunnels carrying IPv6 traffic. The automatic tunnel's IPv4 destination address is derived from the 6to4 IPv6 address of the tunnel's nexthop. The switch supports the functionality of a 6to4 border router that connects a 6to4 site to a 6to4 domain. It sends/receives tunneled traffic from routers in a 6to4 domain that includes other 6to4 border routers and 6to4 relay routers.
•
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 address 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 drop-down menu, this IPv6 address input field becomes visible. The Address must be entered in the format prefix/length.
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.
Tunnel Mode — The corresponding mode of the Tunnel.
•
IPv6 Mode — Shows whether IPv6 is enabled on 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 then nothing is displayed in place of the address.
•
Destination — The corresponding Tunnel Destination Address.
The PowerConnect 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 PowerConnect 6200 Series supports multiple loopback interfaces.
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:
Use the Loopbacks Configurationpage to create, configure, or remove loopback interfaces. You can also set up or delete a secondary address for a loopback.
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.
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.
