
show 802.1x | User Documentation Addendum |
|
|
|
|
Note the following when configuring the Loopback0 interface:
•The interface name, “Loopback0”, is case sensitive.
•The admin parameter is the only configurable parameter supported with this type of interface.
•The Loopback0 interface is always active and available.
•Only one Loopback0 interface per switch is allowed.
•Creating this interface does not deduct from the total number of IP interfaces allowed per VLAN or switch.
Loopback0 Address Advertisement
The Loopback0 IP interface address is automatically advertised by the IGP protocols RIP and OSPF when the interface is created. There is no additional configuration necessary to trigger advertisement with these protocols.
Note the following regarding Loopback0 advertisement:
•RIP advertises the host route to the Loopback0 IP interface as a redistributed (directhost) route.
•OSPF advertises the host route to the Loopback0 IP interface in its
Configuring a BGP Peer Session with Loopback0
It is possible to create BGP peers using the Loopback0 IP interface address of the peering router and bind- ing the source (i.e., outgoing IP interface for the TCP connection) to its own configured Loopback0 inter- face. The Loopback0 IP interface address can be used for both Internal and External BGP peer sessions.
For EBGP sessions, if the External peer router is multiple hops away, the
The following example command configures a BGP peering session using a Loopback0 IP interface address:
See the OmniSwitch 7700/7800/8800 Advanced Routing Configuration Guide for more information.
Chapter 22, “Configuring 802.1X”
Quick Steps for Configuring 802.1X
On page
6(Optional) Configure a guest VLAN for the 802.1x port using the 802.1x
7(Optional) Configure the number of times supplicant devices are polled for identification using the 802.1x
On page
page | Release 5.1.6.R02 User Guide Supplement June 2005 |