and the Alcatel logo are registered trademarks of Alcatel. Xylan®, OmniSwitch®, OmniStack®,
®
are registered trademarks of Alcatel Internetworking, Inc.
OmniAccess™, Omni Switch/Router™, PolicyView™, RouterView™, SwitchManager™, VoiceView™,
WebView™, X-Cell™, X-Vision™, and the Xylan logo are trademarks of Alcatel Internetworking, Inc.
This OmniSwitch product contains components which may be covered by one or more of the following
U.S. Patents:
•U.S. Patent No. 6,339,830
•U.S. Patent No. 6,070,243
•U.S. Patent No. 6,061,368
•U.S. Patent No. 5,394,402
•U.S. Patent No. 6,047,024
•U.S. Patent No. 6,314,106
•U.S. Patent No. 6,542,507
26801 West Agoura Road
Calabasas, CA 91301
(818) 880-3500 FAX (818) 880-3505
info@ind.alcatel.com
US Customer Support—(800) 995-2696
International Customer Support—(818) 878-4507
Internet—http://eservice.ind.alcatel.com
iiRelease 5.1.6.R02 User Guide SupplementJune 2005
Assigning and Removing MAC Addresses ............................................................3-13
Assigning MAC Addresses .............................................................................3-13
Removing MAC Addresses .............................................................................3-14
Configuring Inter-switch Ports for HA VLANs .....................................................3-14
Configuring the Flood Queue Bandwidth ..............................................................3-15
Application Example 1: Firewall Cluster ......................................................................3-16
Application Example 2: Inter-Switch HA VLANs .......................................................3-17
Displaying High Availability VLAN Status and Statistics ...........................................3-19
Release 5.1.6.R02 User Guide SupplementJune 2005v
Page 6
Contents
viRelease 5.1.6.R02 User Guide SupplementJune 2005
Page 7
1 User Documentation
Addendum
This chapter includes information that should be added to or changed in the 5.1.6 release of the set of user
guides for the OmniSwitch 6600 Family, OmniSwitch 7700/7800, and OmniSwitch 8800.
OmniSwitch CLI Reference Guide
The following modifications should be made:
IPv6 Commands
Please refer to Chapter 2, “IPv6 Commands,” in this addendum for CLI commands pertaining to IPv6.
Chapter 40, “High Availability VLAN Commands”
On page 40-2 the following two bullet items should be added to the Usage Guidelines section for the
vlan port-mac ingress-port command:
• Note that removing the last ingress/egress port from an HA VLAN is not allowed. Deleting the VLAN
is required when there is only one ingress/egress port left in the VLAN.
• All HA VLAN related ports must first belong to the same default VLAN before they are configured as
ingress, egress, or inter-switch ports for the HA VLAN.
On page 40-3 the MIB Objects section for the vlan port-mac ingress-port command should be replaced
with the following:
vlanHAPortTable
vlanHAPortVlanId
vlanHAPortType
vlanHAPortIfIndex
On page 40-4 the following two bullet items should be added to the Usage Guidelines section for the
vlan port-mac egress-port command:
• Note that removing the last ingress/egress port from an HA VLAN is not allowed. Deleting the VLAN
is required when there is only one ingress/egress port left in the VLAN.
• All HA VLAN related ports must first belong to the same default VLAN before they are configured as
ingress, egress, or inter-switch ports for the HA VLAN.
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-1
Page 8
User Documentation Addendum
On page 40-5 the MIB Objects section for the vlan port-mac egress-port command should be replaced
with the following:
vlanHAPortTable
vlanHAPortVlanId
vlanHAPortType
vlanHAPortIfIndex
mac-address-table port-mac vlan mac
On page 40-6 the following bullet should be added to the Usage Guidelines section for the
mac-address-table port-mac vlan mac command:
• Note that removing the last MAC address from an HA VLAN is not allowed. Deleting the VLAN is
required when there is only one MAC address left.
On page 40-7 the following MIB information should be added to the MIB Objects section for the mac-address-table port-mac vlan mac command:
vlanHAPortVlanId
The following new command should be included in this chapter:
page 1-2Release 5.1.6.R02 User Guide SupplementJune 2005
Page 9
User Documentation Addendumvlan port-mac bandwidth
vlan port-mac bandwidth
Configures the bandwidth for the ingress flood queue associated with high availability (HA) VLANs.
vlan vid port-mac bandwidth mbps
Syntax Definitions
vidAn existing HA VLAN ID number (1–4094).
mbpsBandwidth value for the specified HA VLAN flood queue (1mbps –
1000mbps).
Defaults
By default, the flood queue bandwidth for an HA VLAN is set to 15 mbps.
Platforms Supported
OmniSwitch 7700, 7800, 8800
Usage Guidelines
• The VLAN ID specified with this command must be the ID for an HA VLAN. An HA VLAN contains
at least one ingress or egress port and one MAC address.
• The ingress flood queue is created when the first HA VLAN is configured on the switch, and deleted
when the last HA VLAN is removed from the switch.
Examples
-> vlan 10 port-mac bandwidth 50
-> vlan 200 port-mac bandwidth 1000
Release History
Release 5.1.6; command was introduced.
Related Commands
vlan port-mac ingress-portAdds and removes ingress ports from an HA VLAN.
vlan port-mac egress-portAdds and removes egress ports from an HA VLAN.
mac-address-table port-mac
Adds and removes MAC addresses from an HA VLAN.
vlan mac
MIB Objects
vlanTable
vlanNumber
vlanHABandwidth
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-3
On page 42-12 the following two new field definitions should be added to the Output Definitions table
for the show 802.1x command:
Guest VLAN ID
Indicates if a guest VLAN is configured for non-802.1x traffic received
on the port. If so, a VLAN ID number appears in this field. Configured
through the 802.1x guest-vlan command This field does not appear on
an OmniSwitch 6800.
Supplicant polling retry
count
The number of times a device is polled for EAP frames to determine
whether or not the device is an 802.1x client. Configured through the
802.1x supp-polling retry command. This field does not appear on an
OmniSwitch 6800.
On page 42-13 the following MIB information should be added to the MIB Objects section for the
show 802.1x command:
alaDot1xGuestVlanConfTable
alaDot1xGuestVlanNumber
alaDot1xSuppPollingCnt
The following three new commands should be included in this chapter:
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-5
Page 12
802.1x guest-vlanUser Documentation Addendum
802.1x guest-vlan
Configures a guest VLAN for an 802.1x port. When non-802.1x traffic is received on the specified port, it
is assigned to the guest VLAN.
802.1x slot/port guest-vlan {vid | disable}
Syntax Definitions
slotThe slot number of the 802.1x port.
portThe 802.1x port number.
vidThe VLAN ID number that will serve as a guest VLAN for the 802.1x
port.
disableDisables the guest VLAN functionality for the 802.1x port.
Defaults
By default a guest VLAN is not configured for 802.1x ports.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
• If a guest VLAN is already configured for the specified 802.1x port, the existing VLAN ID is overwrit-
ten with the new value. For example, if VLAN 10 is configured as a guest VLAN for 802.1x port 10/24
and this command is entered specifying VLAN 20, then VLAN 20 becomes the new guest VLAN for
the port.
• Using the disable pulmotor also removes the guest VLAN association from the 802.1x port. The func-
tionality is enabled again when a new guest VLAN is configured.
• The guest VLAN option is only available for 802.1x ports operating in the auto mode.
• Only one guest VLAN per 802.1x port is allowed.
• The VLAN ID specified with this command must already exist. VLANs are created using the vlan
command.
• Note that on an OmniSwitch 6624/6648, non-802.1x clients learned on the guest VLAN are dropped if
an 802.1x client successfully accesses the same port.
Examples
-> 802.1x 3/1 guest-vlan 5
-> 802.1x 3/1 guest-vlan disable
Release History
Release 5.1.6; command was introduced.
page 1-6Release 5.1.6.R02 User Guide SupplementJune 2005
Page 13
User Documentation Addendum802.1x guest-vlan
Related Commands
802.1xConfigures 802.1X parameters on a particular slot/port.
802.1x supp-polling retryConfigures the number of times a device is polled for EAP frames.
show 802.1xDisplays information about ports configured for 802.1X.
show 802.1x non-suppDisplays non-802.1x devices learned on the switch and their guest
VLAN assignments.
MIB Objects
alaDot1xGuestVlanConfTable
alaDot1xGuestVlanNumber
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-7
The following section should be added to page 13-9:
Configuring a Loopback0 Interface
Loopback0 is the name assigned to an IP interface to identify a consistent address for network management purposes. The Loopback0 interface is not bound to any VLAN, so it will always remain operationally active. This differs from other IP interfaces in that if there are no active ports in the VLAN, all IP
interface associated with that VLAN are not active. In addition, the Loopback0 interface provides a unique
IP address for the switch that is easily identifiable to network management applications.
This type of interface is created in the same manner as all other IP interfaces, using the ip interface
command. To identify a Loopback0 interface, enter Loopback0 for the interface name. For example, the
following command creates the Loopback0 interface with an IP address of 10.11.4.1:
-> ip interface Loopback0 address 10.11.4.1
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-11
Page 18
show 802.1x non-suppUser 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 Router-LSAs (as a Stub link) as an
internal route into all its configured areas.
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 binding the source (i.e., outgoing IP interface for the TCP connection) to its own configured Loopback0 interface. 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 ebgp-multihop parameter may
need to be used.
The following example command configures a BGP peering session using a Loopback0 IP interface
address:
-> ip bgp neighbor 2.2.2.2 update-source Loopback0
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 22-3 the following two new steps should be added to this section:
6 (Optional) Configure a guest VLAN for the 802.1x port using the 802.1x guest-vlan command.
-> 802.1x 3/1 guest-vlan 5
7 (Optional) Configure the number of times supplicant devices are polled for identification using the
802.1x supp-polling retry command.
-> 802.1x 3/1 supp-polling retry 10
On page 22-3 of this section replace the Note information about how to display 802.1x configuration and
user information with the following:
page 1-12Release 5.1.6.R02 User Guide SupplementJune 2005
Page 19
User Documentation Addendumshow 802.1x non-supp
Note. Verify the 802.1X port configuration using the show 802.1x command:
-> show 802.1x 1/13
802.1x configuration for slot 1 port 13:
direction = both,
operational directions = both,
port-control = auto,
See the OmniSwitch CLI Reference Guide for information about the fields in this display.
New Section, page 22-7
The following section should be added to page 22-7:
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-13
Page 20
show 802.1x non-suppUser Documentation Addendum
Guest VLANs for Non-802.1x Supplicants
For those supplicants that are not 802.1x devices—do not send/receive EAP frames—an optional guest
VLAN feature is available to allow traffic from these devices on an 802.1x port. If the user-defined guest
VLAN is not available, then traffic from a non-802.1x device is dropped.
The switch determines whether or not a device is an 802.1x supplicant by sending EAP-Request/Identity
frames on the 802.1x port every 0.5 seconds for a configurable number of times. If no EAP frames are
received from a device after the specified number of attempts, the device is determined to be a non-802.1x
supplicant and is learned on the guest VLAN configured for that port. If no guest VLAN is available, then
the non-802.1x supplicant is blocked from accessing the 802.1x port and no further attempts are made to
solicit EAP frames from the device.
Note the following when using guest VLANs:
• 802.1x supplicants that fail authentication are not eligible for guest VLAN access. This type of VLAN
access is only for those devices identified as non-802.1x supplicants that have not made any attempt to
authenticate.
• Once a non-802.1x supplicant is learned on a guest VLAN, it is no longer eligible for Group Mobility
classification and assignment.
• If a non-802.1x supplicant device becomes 802.1x capable when it is a member of a guest VLAN, upon
authentication the device is automatically moved from the guest VLAN to the appropriate 802.1x specified VLAN. Disconnecting the device from the 802.1x port is not required in this scenario.
• If an authenticated 802.1x supplicant becomes non-802.1x capable, the device is moved to an existing
guest VLAN after the device is rebooted.
By default a guest VLAN is not configured on an 802.1x port. For information about how to configure a
guest VLAN, see “Configuring a Guest VLAN” on page 1-14. For information about how to set the
number of times an unknown device is polled for identification, see “Configuring the Supplicant Polling
Retry Count” on page 1-15.
New Section, page 22-11
The following section should be added to page 22-11:
Configuring a Guest VLAN
To configure a guest VLAN for an 802.1x port, use the 802.1x guest-vlan command with the relevant slot/
port number and specify an existing VLAN ID. For example:
-> 802.1x 3/1 guest-vlan 5
This command associates guest VLAN 5 with 802.1x port 3/1. When a non-802.1x supplicant is identified
on this port, the source MAC address of the supplicant is learned in VLAN 5. This MAC address is then
aged according to the aging timer value for VLAN 5.
To remove a guest VLAN from an 802.1x port, use the disable option with the 802.1x guest-vlan
command. Note that it is not necessary to specify the guest VLAN ID with this command. For example:
-> 802.1x 3/1 guest-vlan disable
Note the following when configuring a guest VLAN:
• The guest VLAN option is only available for 802.1x ports operating in the auto mode.
page 1-14Release 5.1.6.R02 User Guide SupplementJune 2005
Page 21
User Documentation Addendumshow 802.1x non-supp
• Only one guest VLAN is allowed per 802.1x port.
• The VLAN ID specified must already exist in the switch configuration. Use the vlan command to
create a VLAN before configuring it as an 802.1x guest VLAN.
• If a guest VLAN is already configured for the specified 802.1x port when the 802.1x guest-vlan
command is used, the existing VLAN ID is overwritten with the new value.
Configuring the Supplicant Polling Retry Count
To configure the number of times the switch polls an unknown device connected to an 802.1x port, use the
802.1x supp-polling retry command. For example,
-> 802.1x 3/1 supp-polling retry 10
If after the number of polling attempts specified the device has not responded with EAP frames, then the
device is learned as a non-802.1x supplicant in a guest VLAN. If a guest VLAN was not configured for
the 802.1x port, the device is blocked from accessing that port and no other attempts are made to solicit
EAP frames from the device.
Note that the polling interval is set to 0.5 seconds between each retry and is not a configurable at this time.
Chapter 28, “Configuring High Availability VLANs”
Replace all the contents of Chapter 28 with the contents of Chapter 3, “Configuring High Availability
The following section should be added to page 2-29:
Configuring a BGP Peer with the Loopback0 Interface
Loopback0 is the name assigned to an IP interface to identify a consistent address for network management purposes. The Loopback0 interface is not bound to any VLAN, so it will always remain operationally active. This differs from other IP interfaces in that if there are no active ports in the VLAN, all IP
interface associated with that VLAN are not active. In addition, the Loopback0 interface provides a unique
IP address for the switch that is easily identifiable to network management applications.
It is possible to create BGP peers using the Loopback0 IP interface address of the peering router and binding the source (i.e., outgoing IP interface for the TCP connection) to its own configured Loopback0 interface. 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 ebgp-multihop parameter may
need to be used.
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-15
Page 22
show 802.1x non-suppUser Documentation Addendum
The following example command configures a BGP peering session using a Loopback0 IP interface
address:
-> ip bgp neighbor 2.2.2.2 update-source Loopback0
See the OmniSwitch 7700/7800/8800 Network Configuration Guide for more information about configuring an IP Loopback0 interface.
OmniSwitch 6600 Family Network Configuration
Guide
The following modifications should be made:
Chapter 21, “Configuring 802.1X”
Quick Steps for Configuring 802.1X
On page 21-3 the following two new steps should be added to this section:
6 (Optional) Configure a guest VLAN for the 802.1x port using the 802.1x guest-vlan command.
-> 802.1x 3/1 guest-vlan 5
7 (Optional) Configure the number of times supplicant devices are polled for identification using the
802.1x supp-polling retry command.
-> 802.1x 3/1 supp-polling retry 10
On page 22-3 of this section replace the Note information about how to display 802.1x configuration and
user information with the following:
Note. Verify the 802.1X port configuration using the show 802.1x command:
See the OmniSwitch CLI Reference Guide for information about the fields in this display.
New Section, page 21-5
The following section should be added to page 21-5:
Guest VLANs for Non-802.1x Supplicants
For those supplicants that are not 802.1x devices—do not send/receive EAP frames—an optional guest
VLAN feature is available to allow traffic from these devices on an 802.1x port. If the user-defined guest
VLAN is not available, then traffic from a non-802.1x device is dropped.
The switch determines whether or not a device is an 802.1x supplicant by sending EAP-Request/Identity
frames on the 802.1x port every 0.5 seconds for a configurable number of times. If no EAP frames are
received from a device after the specified number of attempts, the device is determined to be a non-802.1x
supplicant and is learned on the guest VLAN configured for that port. If no guest VLAN is available, then
the non-802.1x supplicant is blocked from accessing the 802.1x port and no further attempts are made to
solicit EAP frames from the device.
Note the following when using guest VLANs:
• Non-802.1x clients learned on a guest VLAN are dropped if an 802.1x client successfully authenti-
cates on the same port. This is due to a one VLAN per port restriction (either 802.1x VLAN or guest
VLAN assignment but not both) As a result, using a hub connection to provide access for multiple
users to an 802.1x port is not recommended.
• 802.1x supplicants that fail authentication are not eligible for guest VLAN access. This type of VLAN
access is only for those devices identified as non-802.1x supplicants that have not made any attempt to
authenticate.
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-17
Page 24
show 802.1x non-suppUser Documentation Addendum
• Once a non-802.1x supplicant is learned on a guest VLAN, it is no longer eligible for Group Mobility
classification and assignment.
• If a non-802.1x supplicant device becomes 802.1x capable when it is a member of a guest VLAN, upon
authentication the device is automatically moved from the guest VLAN to the appropriate 802.1x specified VLAN. Disconnecting the device from the 802.1x port is not required in this scenario.
• If an authenticated 802.1x supplicant becomes non-802.1x capable, the device is moved to an existing
guest VLAN after the device is rebooted.
By default a guest VLAN is not configured on an 802.1x port. For information about how to configure a
guest VLAN, see “Configuring a Guest VLAN” on page 1-14. For information about how to set the
number of times an unknown device is polled for identification, see “Configuring the Supplicant Polling
Retry Count” on page 1-15.
New Section, page 21-10
The following section should be added to page 21-10:
Configuring a Guest VLAN
To configure a guest VLAN for an 802.1x port, use the 802.1x guest-vlan command with the relevant slot/
port number and specify an existing VLAN ID. For example:
-> 802.1x 3/1 guest-vlan 5
This command associates guest VLAN 5 with 802.1x port 3/1. When a non-802.1x supplicant is identified
on this port, the source MAC address of the supplicant is learned in VLAN 5. This MAC address is then
aged according to the aging timer value for VLAN 5.
To remove a guest VLAN from an 802.1x port, use the disable option with the 802.1x guest-vlan
command. Note that it is not necessary to specify the guest VLAN ID with this command. For example:
-> 802.1x 3/1 guest-vlan disable
Note the following when configuring a guest VLAN:
• The guest VLAN option is only available for 802.1x ports operating in the auto mode.
• Only one VLAN is allowed per 802.1x port. If a client successfully authenticates on the port, all guest
VLAN users are dropped.
• The VLAN ID specified must already exist in the switch configuration. Use the vlan command to
create a VLAN before configuring it as an 802.1x guest VLAN.
• If a guest VLAN is already configured for the specified 802.1x port when the 802.1x guest-vlan
command is used, the existing VLAN ID is overwritten with the new value.
Configuring the Supplicant Polling Retry Count
To configure the number of times the switch polls an unknown device connected to an 802.1x port, use the
802.1x supp-polling retry command. For example,
-> 802.1x 3/1 supp-polling retry 10
If after the number of polling attempts specified the device has not responded with EAP frames, then the
device is learned as a non-802.1x supplicant in a guest VLAN. If a guest VLAN was not configured for the
page 1-18Release 5.1.6.R02 User Guide SupplementJune 2005
Page 25
User Documentation Addendumshow 802.1x non-supp
802.1x port, the device is blocked from accessing that port and no other attempts are made to solicit EAP
frames from the device.
Note that the polling interval is set to 0.5 seconds between each retry and is not a configurable at this time.
Release 5.1.6.R02 User Guide SupplementJune 2005page 1-19
Page 26
show 802.1x non-suppUser Documentation Addendum
page 1-20Release 5.1.6.R02 User Guide SupplementJune 2005
Page 27
2 IPv6 Commands
This chapter details Internet Protocol Version 6 (IPv6) commands for the switch (including RIPng
commands). IPv6 (documented in RFC 2460) is designed as a successor to IPv 4. The changes from IPv4
to IPv6 fall primarily into the following categories:
Expanded Routing and Addressing Capabilities - IPv6 increases the IP address size from 32 bits to 128
bits, to support more levels of addressing hierarchy and a much greater number of addressable nodes, and
simpler auto-configuration of addresses. The scalability of multicast routing is improved by adding a
"scope" field to multicast addresses.
Header Format Simplification - Some IPv4 header fields were dropped or made optional, to reduce the
common-case processing cost of packet handling and to keep the bandwidth cost of the IPv6 header as low
as possible despite the increased size of the addresses. Even though the IPv6 addresses are four times
longer than the IPv4 addresses, the IPv6 header is only twice the size of the IPv4 header.
Anycast Addressing - A new type of address called a "anycast address" is defined, to identify sets of
nodes where a packet sent to an anycast address is delivered to one of the nodes. The use of anycast
addresses in the IPv6 source route allows nodes to control the path which their traffic flows.
Improved Support for Options - Changes in the way IP header options are encoded allows for more efficient forwarding, less stringent limits on the length of options, and greater flexibility for introducing new
options in the future.
Authentication and Privacy Capabilities - IPv6 includes the definition of extensions which provide
support for authentication, data integrity, and confidentiality. This is included as a basic element of IPv6
and will be included in all implementations.
IPv6 is supported on 6600/7700/7800/8800 series switches running software Release 5.1.6 and up.
MIB information for the IPv6 and RIPng commands is as follows:
mtu sizeMaximum Transmission Unit for the interface.
ra-sendSpecifies whether the router advertisements are sent on this interface.
ra-max-interval intervalMaximum time, in seconds, allowed between the transmission of unso-
licited multicast router advertisements in this interface. The range is 4 1,800.
ra-managed-config-flagValue to be placed in the managed address configuration flag field in
router advertisements sent on this interface.
ra-other-config-flag
Value to be placed in the other stateful configuration flag in
router advertisements sent on this interface.
ra-reachable-time timeValue, in milliseconds, to be placed in the reachable time field in router
advertisements sent on this interface. The range is 0 - 3,600,000). The
special value of zero indicates that this time is unspecified by the router.
ra-retrans-timer timeValue, in milliseconds, to be placed in the retransmit timer field in
router advertisements sent on this interface. The value zero indicates
that the time is unspecified by the router.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-3
Page 30
ipv6 interfaceIPv6 Commands
ra-default-lifetime timeValue, in seconds, to be placed in the router lifetime field in router
advertisements sent on this interface. The time must be zero or between
the value of “ra-max-interval” and 9,000 seconds. A value of zero indicates that the router is not to be used as a default router. The “no radefault-lifetime” option will calculate the value using the formula (3 *
ra-max-interval).
enable | disableAdministratively enable or disable the interface.
ra-send-mtuSpecifies whether the MTU option is included in the router advertise-
ments sent on the interface.
Defaults
parameterdefault
ra-sendyes
ra-max-interval600
ra-managed-config-flagfalse
ra-reachable-time0
ra-retrans-timer0
ra-default-lifetime no
ra-send-mtuno
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
• When you create an IPv6 interface it is enabled by default.
• Use the “no” form of the command to delete an interface.
• All IPv6 VLAN and tunnel interfaces must have a name.
• When creating an IPv6 interface you must specify a VLAN ID, Tunnel ID, or 6to4. When modifying or
deleting an interface, you do not need to specify one of these options unless the name assigned to the
interface is being changed. If it is present with a different value from when the interface was created,
the command will be in error.
• A 6to4 interface cannot send advertisements (ra-send).
• To enable IPv6 routing you must first create a VLAN, then create an IPv6 interface on the VLAN. See
Chapter 21, “VLAN Management Commands,” for information on creating VLANs.
• To route IPv6 traffic over an IPv4 network, you must create an IPv6 tunnel using the ipv6 interface
tunnel source destinationcommand.
page 2-4Release 5.1.6.R02 User Guide SupplementJune 2005
Page 31
IPv6 Commandsipv6 interface
Example
-> ipv6 interface Test vlan 1
-> ipv6 interface Test_Tunnel tunnel 2
-> ipv6 interface Test_6to4 tunnel 6to4
Release History
Release 5.1.6; command was introduced.
Related Commands
show ipv6 interfaceDisplays IPv6 Interface Table
show ipv6 tunnelDisplays IPv6 Tunnel information and whether the 6to4 tunnel is
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-5
Page 32
ipv6 addressIPv6 Commands
ipv6 address
Configures an IPv6 address for an IPV6 interface on a VLAN, configured tunnel, or a 6to4 tunnel. There
are different formats for this command depending on the address type.
page 2-8Release 5.1.6.R02 User Guide SupplementJune 2005
Page 35
IPv6 Commandsipv6 dad-check
ipv6 dad-check
Runs a Duplicate Address Detection (DAD) check on an address that was marked as duplicated.
ipv6 dad-check ipv6_address if_name
Syntax Definitions
ipv6_addressIPv6 address.
ip_nameName assigned to the interface.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
The switch performs DAD check when an interface is attached to the stack and its VLAN first enters the
active state. Use this command to rerun a DAD check on an address that was marked as duplicated.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-9
Page 36
ipv6 hop-limitIPv6 Commands
ipv6 hop-limit
Configures the value placed in the hop limit field in the header of all IPv6 packets that are originated by
the switch. It also configures the value placed in the hop limit field in router advertisements.
ipv6 hop-limit value
no ipv6 hop-limit
Syntax Definitions
valueHop limit value. The range is 0 - 255.
Defaults
parameterdefault
value64
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
Use the “no” form of the command to return the hop limit to its default value.
Example
-> ipv6 hop-limit 64
Release History
Release 5.1.6; command was introduced.
Related Commands
N/A.
MIB Objects
ipv6MibObjects
Ipv6DefaultHopLimit
page 2-10Release 5.1.6.R02 User Guide SupplementJune 2005
Page 37
IPv6 Commandsipv6 pmtu-lifetime
ipv6 pmtu-lifetime
Configures the configure the minimum lifetime for entries in the path MTU Table.
ipv6 pmtu-lifetime time
Syntax Definitions
timeMinimum path MTU entry lifetime, in minutes. Valid range is 10 -
1440.
Defaults
parameterdefault
time60
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
N/A.
Example
-> ipv6 pmtu-lifetime 30
Release History
Release 5.1.6; command was introduced.
Related Commands
show ipv6 pmtu tableDisplays the IPv6 path MTU Table.
clear ipv6 pmtu tableRemoves all entries from the IPv6 path MTU Table.
MIB Objects
alaIPv6ConfigTable
alaIPv6PMTUMinLifetime
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-11
Page 38
ipv6 hostIPv6 Commands
ipv6 host
Configures a static host name to IPv6 address mapping to the local host table.
ipv6 host name ipv6_address
no ipv6 host name ipv6_address
Syntax Definitions
nameHost name associated with the IPv6 address (1 - 255 characters).
ipv6_addressIPv6 address.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
Use the “no” form of the command to remove the mapping from the host table.
page 2-16Release 5.1.6.R02 User Guide SupplementJune 2005
Page 43
IPv6 Commandsping6
ping6
Used to test whether an IPv6 destination can be reached from the local switch. This command sends an
ICMPv6 echo request to a destination and then waits for a reply. To ping a destination, enter the ping6
command and enter either the destination’s IPv6 address or hostname. The switch will ping the destination using the default frame count, packet size, and interval (6 frames, 64 bytes, and 1 second respectively). You can also customize any or all of these parameters as described below.
if_nameIf the target is a link-local address, the name of the interface used to
reach it.
countNumber of packets to be transmitted.
sizeSize of the data portion of the packet sent for this ping, in bytes.
secondsInterval, in seconds, at which ping packets are transmitted.
Defaults
parameterdefault
count6
size56
interval seconds1
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
• If you change the default values they will only apply to the current ping. The next time you use the
ping command, the default values will be used unless you again enter different values.
• When the next hop address is a local link address, the name of the interface used to reach the destina-
tion must be specified.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-17
Page 44
ping6IPv6 Commands
Example
-> ping6 fe80::2d0:95ff:fe6a:f458/64
Release History
Release 5.1.6; command was introduced.
Related Commands
traceroute6Used to find the path taken by an IPv6 packet from the local switch
to a specified destination.
page 2-18Release 5.1.6.R02 User Guide SupplementJune 2005
Page 45
IPv6 Commandstraceroute6
traceroute6
Used to find the path taken by an IPv6 packet from the local switch to a specified destination. This
command displays the individual hops to the destination as well as some timing information.
v6headerSets the display format for the IPv6 header.
extheaderSets the display format for IPv6 extension headers:
none - No extension headers will be displayed
payload - Information on the final payload header only
concise - Concise information on all extension headers
verbose - Verbose information on all extension headers.
etherheaderSpecifies whether the packet's Ethernet header will be displayed.
raw bytesIf bytes is not zero, this number of raw hex bytes of the packet will be
displayed.
boardSpecifies the board(s) on which packet debug is enabled.
ether-filterAllows filtering of packets based on their source and destination MAC
addresses. If a single MAC address is specified, only packets whose
source or destination MAC address match the specified value will be
displayed. If a pair of MAC addresses is specified, only those packets
being exchanged between the two MAC addresses will be displayed.
ipv6-filterAllows filtering of packets based on their source and destination IPv6
addresses. If a single IPv6 address is specified, only packets sent to or
received from that address will be displayed. If a pair of addresses is
specified, only those packets being exchanged between the two
addresses will be displayed.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-21
Page 48
debug ipv6 packetIPv6 Commands
directionAllows filtering of packets based on the direction of flow:
all - debug both incoming and outgoing packets
in - debug incoming IPv6 packets
out - debug outgoing packets
from-cmm - debug packets received from the CMM.
from-ipv4 - debug packets received from an IPv4 interface.
to-cmm - debug packets sent to the CMM.
to-ipv4 - debug packets sent to an IPv4 interface.
outputSpecifies the destination for the debug information.
console - write debug information to the console screen or file
file filename - write debug information to the specified file.
Defaults
parameterdefault
v6headerconcise
extheaderpayload
etherheaderyes
raw bytes0
boardall
ether-filterno ether-filter
ipv6-filterno ipv6-filter
directionall
outputconsole
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
• Use the no form of the command to turn off IPv6 debugging.
• Options are additive across multiple command lines until reset with the “default” option.
Example
-> debug ipv6 packet defaults
Release History
Release 5.1.6; command was introduced.
page 2-22Release 5.1.6.R02 User Guide SupplementJune 2005
Page 49
IPv6 Commandsdebug ipv6 packet
Related Commands
debug ipv6 trace-categoryEnables/disables specific IPv6 EDR trace categories.
MIB Objects
N/A.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-23
Page 50
debug ipv6 trace-categoryIPv6 Commands
debug ipv6 trace-category
Enables/disables specific IPv6 EDR trace categories. If a category is enabled (e.g., vlan, tunnel), switch
log messages generated for that category are written to the switch log.
NameInterface name. This is usually the VLAN on which the interface is
configured.
IPv6 Address/Prefix LengthIPv6 address and prefix length assigned to the interface. If an interface
has more than one IPv6 address assigned to it, each address is shown on
a separate line.
StatusInterface status (e.g., Active/Inactive).
DeviceThe device on which the interface is configured (e.g., VLAN 955).
page 2-30Release 5.1.6.R02 User Guide SupplementJune 2005
Page 57
IPv6 Commandsshow ipv6 interface
-> show ipv6 interface v6if-6to4-137
v6if-6to4-137
IPv6 interface index = 16777216(0x01000000)
Administrative status = Enabled
Operational status = Active
Link-local address(es):
Global unicast address(es):
2002:d423:2323::35/64
Anycast address(es):
2002:d423:2323::/64
Joined group addresses:
ff02::1:ff00:0
ff02::2:93da:68lb
ff02::1
ff02::1:ff00:35
Maximum Transfer Unit (MTU) = 1280
Send Router Advertisements = No
Maximum RA interval (sec) = 600
Minimum RA interval (sec) = 198
RA managed config flag = False
RA other config flag = False
RA reachable time (ms) = 30000
RA retransmit timer (ms) = 1000
RA default lifetime (sec) = 1800
Packets received = 215686
Packets sent = 2019
Bytes received = 14108208
Bytes sent = 178746
Input errors = 0
Output errors = 0
Collisions = 0
Dropped = 0
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-31
Page 58
show ipv6 interfaceIPv6 Commands
-> show ipv6 interface v6if-tunnel-137
v6if-tunnel-137
IPv6 interface index = 16777216(0x01000000)
Administrative status = Disabled
Operational status = Inactive
Link-local address(es):
fe80::2d0:95ff:fe12:f470/64
Global unicast address(es):
137:35:35:35/64
Anycast address(es):
137:35:35:35/64
Joined group addresses:
ff02::1:ff00:0
ff02::1:ff00:35
ff02::2:93da:68lb
ff02::1
ff02::1:ff12:f470
Maximum Transfer Unit (MTU) = 1280
Send Router Advertisements = Yes
Maximum RA interval (sec) = 600
Minimum RA interval (sec) = 198
RA managed config flag = False
RA other config flag = False
RA reachable time (ms) = 30000
RA retransmit timer (ms) = 1000
RA default lifetime (sec) = 1800
Packets received = 0
Packets sent = 2
Bytes received = 0
Bytes sent = 144
Input errors = 0
Output errors = 2
Collisions = 0
Dropped = 0
output definitions
IPv6 interface indexIPv6IfIndex value that should be used in SNMP requests pertaining to
this interface.
Administrative statusAdministrative status of this interface (Enabled/Disabled).
Operational statusIndicates whether the physical interface is connected to a device
(Active/Inactive).
Hardware addressInterface’s MAC address
Link-local addressLink-local address assigned to the interface.
Global unicast address(es)Global unicast address(es) assigned to the interface.
Joined group address(es)Addresses of the multicast groups that this interface has joined.
Maximum Transfer UnitInterface MTU value.
Send Router AdvertisementsIndicates if the router sends periodic router advertisements and
responds to router solicitations on the interface.
Maximum RA interval (sec)Maximum time between the transmission of unsolicited router adver-
tisements over the interface.
Minimum RA interval (sec)Minimum time between the transmission of unsolicited router adver-
tisements over the interface (0.33 * Maximum RA Interval).
page 2-32Release 5.1.6.R02 User Guide SupplementJune 2005
Page 59
IPv6 Commandsshow ipv6 interface
output definitions
RA managed config flagTrue/False value in the managed address configuration flag field in
router advertisements.
RA other config flagThe True/False value in the other stateful configuration flag field in
router advertisements sent over this interface.
RA reachable time (ms)Value placed in the reachable time field in the router advertisements
sent over this interface.
RA retransmit timer (ms)Value placed in the retransmit timer field in router advertisements sent
over this interface.
RA default lifetime (ms)The value placed in the router lifetime field in the router advertisements
sent over this interface.
Packets receivedNumber of IPv6 packets received since the last time the counters were
reset.
Packets sentNumber of IPv6 packets sent since the last time the counters were reset
Bytes receivedNumber of bytes of data received since the last time the counters were
reset.
Bytes sentNumber of bytes of data sent since the last time the counters were reset.
Input errorsNumber of input errors received since the last time the counters were
reset.
Output errorsNumber of output errors received since the last time the counters were
reset.
CollisionsNumber of collisions since the last time the counters were reset.
DroppedNumber of packets dropped since the last time the counters were reset
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 addressConfigures an IPv6 address on a VLAN, configured tunnel, or a
6to4 tunnel.
ipv6 interfaceConfigures an IPv6 interface on a VLAN.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-39
Page 66
clear ipv6 neighborsIPv6 Commands
clear ipv6 neighbors
Removes all entries, except static entries, from the IPv6 Neighbor Table.
clear ipv6 neighbors
Syntax Definitions
N/A.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
This commands only clears dynamic entries. If static entries have been added to the table, they must be
removed using the no form of the ipv6 neighbor command.
Example
-> clear ipv6 neighbors
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 neighborConfigures a static entry in the IPv6 Neighbor Table.
show ipv6 neighborsDisplays IPv6 Neighbor Table.
MIB Objects
alaIPv6NeighborTable
alaIPv6ClearNeighbors
page 2-40Release 5.1.6.R02 User Guide SupplementJune 2005
Page 67
IPv6 Commandsshow ipv6 prefixes
show ipv6 prefixes
Displays IPv6 prefixes used in router advertisements.
show ipv6 prefixes
Syntax Definitions
N/A.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
N/A.
Example
-> show ipv6 prefixes
Legend: Flags: A = Autonomous Address Configuration, L = OnLink
Valid Preferred
Name IPv6 Address/Prefix Length Lifetime Lifetime Flags Source
--------------+----------------------------+----------+----------+-------+--------vlan 955 212:95:5::/64 2592000 604800 LA dynamic
vlan 1002 195:35::/64 2592000 604800 LA dynamic
6to4tunnel 2002:d423:2323::/64 2592000 604800 LA dynamic
tunnel 2 137:35:35::/64 2592000 604800 LA dynamic
output definitions
NameThe interface name. This is usually the VLAN on which the interface is
configured.
IPv6 Address/Prefix LengthThe IPv6 prefix and prefix length for a Router Advertisement Prefix
Option.
Valid Lifetime
Length of time, in seconds, that this prefix will remain valid (i.e., time
until deprecation). A value of 4,294,967,295
represents infinity.
Preferred LifetimeLength of time, in seconds, that this prefix will remain preferred (i.e.
represents infinity.
Flags
time until deprecation). A value of 4,294,967,295
L - Prefix can be used for onlink determination.
A - Prefix can be used for autonomous address configuration (i.e., can
be used to form a local interface address).
Source
config - Prefix has been configured by management.
dynamic - Router Advertisements are using interface prefixes.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-41
Page 68
show ipv6 prefixesIPv6 Commands
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 prefixConfigures an IPv6 prefix on an interface. Used for configuring
page 2-42Release 5.1.6.R02 User Guide SupplementJune 2005
Page 69
IPv6 Commandsshow ipv6 routes
show ipv6 routes
Displays IPv6 Forwarding Table.
show ipv6 routes [ipv6_prefix/prefix_length | static]
Syntax Definitions
ipv6_prefix/prefix_lengthIPv6 prefix. Restricts the display to those routes starting with the speci-
fied prefix.
staticRestricts display to statically configured routes.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
If you do not specify an option (e.g., “static”), all IPv6 interfaces are displayed.
Example
-> show ipv6 routes
Legend:Flags:U = Up, G = Gateway, H = Host, S = Static, C = Cloneable, D = Dynamic,
M = Modified, R = Unreachable, X = Externally resolved, B = Discard,
L = Link-layer, 1 = Protocol specific, 2 = Protocol specific
Destination Prefix Gateway Address Interface Age Protocol Flags
-------------------+----------------+--------+-----------------+------------+---------+----::/0 2002:d468:8a89::137 v6if-6to4-137 18h 47m 26s Static UGS
137:35:35::/64 fe80::2d0:95ff:fe12:f470 v6if-tunnel-137 18h 51m 55s Local UC
195:35::/64 fe80::2d0:95ff:fe12:f470 v6if-to-eagle 18h 51m 55s Local UC
212:95:5::/64 fe80::2d0:95ff:fe12:f470 smbif-5 18h 51m 55s Local UC
2002::/16 2002:d423:2323::35 v6if-6to4-137 18h 51m 55s Other U
output definitions
Destination PrefixIPv6 destination address and prefix.
Gateway AddressIPv6 address of the gateway used to reach the destination network.
InterfaceThe device the interface is using (e.g., VLAN 6to4tunnel); or loopback.
AgeAge of the entry. Entries less than 1 day old are displayed in hh:mm:ss
format. Entries more than 1 day old are displayed in dd:hh format.
ProtocolProtocol by which the route was learned.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-43
Page 70
show ipv6 routesIPv6 Commands
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 routeConfigures a static entry in the IPv6 route.
MIB Objects
IPv6RouteTable
IPv6Routes
IPv6RoutesPrefix
IPV6RoutesStatic
alaIPv6StaticRouteTable
alaIPv6StaticRouteEntry
page 2-44Release 5.1.6.R02 User Guide SupplementJune 2005
Page 71
IPv6 Commandsshow ipv6 tcp ports
show ipv6 tcp ports
Displays TCP Over IPv6 Connection Table. This table contains information about existing TCP connections between IPv6 endpoints.
show ipv6 tcp ports
Syntax Definitions
N/A.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
Only connections between IPv6 addresses are contained in this table.
Example
-> show ipv6 tcp ports
Local Address Port Remote Address Port Interface State
page 2-46Release 5.1.6.R02 User Guide SupplementJune 2005
Page 73
IPv6 Commandsshow ipv6 traffic
show ipv6 traffic
Displays IPv6 traffic statistics.
show ipv6 traffic [if_name]
Syntax Definitions
if_nameInterface name. restricts the display to the specified interface instead of
global statistics.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
The statistics show the cumulative totals since the last time the switch was powered on, the last reset of the
switch was executed or the traffic statistics were cleared using the command.
Example
-> show ipv6 traffic
IPv6 statistics
Packets received
Total = 598174
Header errors = 0
Too big = 12718
No route = 4
Address errors = 0
Unknown protocol = 0
Truncated packets = 0
Local discards = 0
Delivered to users = 582306
Reassembly needed = 0
Reassembled = 0
Reassembly failed = 0
Multicast Packets = 118
Packets sent
Forwarded = 3146
Generated = 432819
Local discards = 0
Fragmented = 0
Fragmentation failed = 0
Fragments generated = 0
Multicast packets = 265
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-47
Page 74
show ipv6 trafficIPv6 Commands
output definitions
To ta lTotal number of input packets received, including those received in
error.
Header errorsNumber of input packets discarded due to errors in their IPv6
headers (e.g., version number mismatch, other format errors, hop
count exceeded, errors discovered in processing their IPv6 options).
Too b igNumber of input packets that could not be forwarded because their
size exceeded the link MTU of the outgoing interface.
No routeNumber of input packets discarded because no route could be
found to transmit them to their destination.
Address errorsNumber of input packets discarded because the IPv6 address in
their IPv6 header's destination field was not a valid address to be
received at this entity. This count includes invalid addresses (e.g., ::0)
and unsupported addresses (e.g., addresses with unallocated prefixes).
Unknown protocolNumber of locally-addressed packets received successfully but dis-
carded because of an unknown or unsupported protocol.
Truncated packetsNumber of input packets discarded because the packet frame
did not carry enough data.
Local discardsNumber of input IPv6 packets for which no problems were encountered
to prevent their continued processing, ut which were discarded (e.g., for
lack of buffer space). Note that this counter does not include any packets discarded while awaiting re-assembly.
Delivered to usersTotal number of packets successfully delivered to IPv6 user protocols
(including ICMP).
Reassembly neededNumber of IPv6 fragments received that needed to be reassembled.
ReassembledNumber of IPv6 packets successfully reassembled.
Reassembly failedNumber of failures detected by the IPv6 reassembly algorithm (for
whatever reason: timed out, errors, etc.).
Multicast packetsNumber of multicast packets received.
ForwardedNumber of output packets that this entity received and forwarded to
their final destinations.
GeneratedTotal number of IPv6 packets that local IPv6 user-protocols (including
ICMP) supplied to IPv6 in requests for transmission. Note that
this counter does not include any packets counted by the Forwarded
statistic.
Local discardsNumber of output IPv6 packets for which no problem was encountered
to prevent their transmission to their destination, but were discarded
(e.g., for lack of buffer space). Note that this counter would include
packets counted by the Forwarded statistic if any such packets met this
(discretionary) discard criterion.
FragmentedNumber of IPv6 packets successfully fragmented.
Fragmentation failedNumber of IPv6 packets discarded because they needed to be frag-
mented but could not be.
Fragments generatedNumber of output packet fragments generated as a result of fragmenta-
tion.
Multicast packetsNumber of multicast packets transmitted.
page 2-48Release 5.1.6.R02 User Guide SupplementJune 2005
Page 75
IPv6 Commandsshow ipv6 traffic
Release History
Release 5.1.6; command was introduced.
Related Commands
show ipv6 icmp statisticsDisplays IPv6 ICMP statistics.
page 2-54Release 5.1.6.R02 User Guide SupplementJune 2005
Page 81
IPv6 Commandsipv6 load rip
ipv6 load rip
Loads RIPng into memory. When the switch is initially configured, you must load RIPng into memory to
enable RIPng routing.
ipv6 load rip
Syntax Definitions
N/A.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
• RIPng will support a maximum of 1,000 routes.
• RIPng will support a maximum of 20 interfaces.
• Use theipv6 rip statuscommand to enable RIPng on the switch.
Example
-> ipv6 load rip
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 rip statusEnables/disables RIPng routing on the switch.
show ipv6 ripDisplays RIPng status and general configuration parameters.
MIB Objects
alaDrcTmConfig
alaDrcTmIPRipngStatus
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-55
Page 82
ipv6 rip statusIPv6 Commands
ipv6 rip status
Enables/disables RIPng on the switch.
ipv6 rip status {enable | disable}
Syntax Definitions
N/A
Defaults
parameterdefault
enable | disableenable
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
RIPng must be loaded on the switch (ipv6 load rip) to enable RIP on the switch.
Example
-> ipv6 rip status enable
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 load ripLoads RIPng into memory.
show ipv6 ripDisplays RIPng status and general configuration parameters.
MIB Objects
alaProtocolripng
alaRipngProtoStatus
page 2-56Release 5.1.6.R02 User Guide SupplementJune 2005
Page 83
IPv6 Commandsipv6 rip invalid-timer
ipv6 rip invalid-timer
Configures the amount of time a route remains active in RIB before being moved to the "Garbage" state.
ipv6 rip invalid-timer seconds
Syntax Definitions
secondsTime, in seconds, that a route will remain in an “Active” state. Valid
range is 1 - 300.
Defaults
parameterdefault
seconds180
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
This timer is reset each time a routing update is received.
Example
-> ipv6 rip invalid-timer 300
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 rip garbage-timerConfigures the RIPng garbage timer value.
ipv6 rip holddown-timerConfigures the amount of time a route is placed in a holddown state.
MIB Objects
alaProtocolripng
alaRipngInvalidTimer
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-57
Page 84
ipv6 rip garbage-timerIPv6 Commands
ipv6 rip garbage-timer
Configures the RIPng garbage timer value. When a route in the RIB exceeds the configured Invalid Timer
Value, the route is moved to a “Garbage” state in the the RIB. The garbage timer is the length of time a
route will stay in this state before it is flushed from the RIB.
ipv6 rip garbage-timer seconds
Syntax Definitions
secondsTime, in seconds, that a route will remain in the RIPng Routing Table
before it is flushed from the RIB. Valid range is 0 - 180.
Defaults
parameterdefault
seconds120
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
Use the ipv6 rip invalid-timercommand to set the Invalid Timer Value.
Example
-> ipv6 rip garbage-timer 180
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 rip invalid-timerConfigures the amount of time a route remains active in RIB before
being moved to the "Garbage" state.
ipv6 rip holddown-timerConfigures the amount of time a route is placed in a holddown state.
MIB Objects
alaProtocolripng
alaRipngGarbageTimer
page 2-58Release 5.1.6.R02 User Guide SupplementJune 2005
Page 85
IPv6 Commandsipv6 rip holddown-timer
ipv6 rip holddown-timer
Configures the amount of time a route is placed in a holddown state. Whenever a route is seen from the
same gateway with a higher metric than the route in the RIB, the route goes into holddown. This excludes
route updates with an INFINITY metric.
ipv6 rip holddown-timer seconds
Syntax Definitions
secondsTime, in seconds, that a route will remain in a holddown state. Valid
range is 0 - 120.
Defaults
parameterdefault
seconds0
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
While in holddown, the route continues being announced as usual and used in the RIB. This interval is
used to control route flap dampening.
Example
-> ipv6 rip holddown-timer 60
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 rip invalid-timerConfigures the amount of time a route remains active in RIB before
being moved to the "Garbage" state.
ipv6 rip garbage-timerConfigures the RIPng garbage timer value.
MIB Objects
alaProtocolripng
alaRipngHolddownTimer
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-59
Page 86
ipv6 rip jitterIPv6 Commands
ipv6 rip jitter
Configures an offset value for RIPng updates. This is the maximum (positive or negative) value that can
be used to offset the update interval. For example, with an update interval of 30 seconds, and a jitter value
of 5 seconds, the RIPng update packet would be sent somewhere (random) between 25 and 35 seconds
from the previous update.
ipv6 rip jitter value
Syntax Definitions
valueTime, in seconds, that a routing update is offset. Valid range is 0 to one-
half the updated interval value (e.g., if the updated interval is 30, the
range would be 0 - 300).
Defaults
parameterdefault
value5
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
As you increase the number of RIPng interfaces/peers, it is recommended that you increase the Jitter value
to reduce the number of RIPng updates being sent over the network.
Example
-> ipv6 rip jitter 10
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 rip update-intervalConfigures the RIPng update interval.
show ipv6 ripDisplays RIPng status and general configuration information.
MIB Objects
alaProtocolripng
alaRipngJitter
page 2-60Release 5.1.6.R02 User Guide SupplementJune 2005
Page 87
IPv6 Commandsipv6 rip route-tag
ipv6 rip route-tag
Configures the route tag value for RIP routes generated by the switch.
ipv6 rip route-tag value
Syntax Definitions
valueRoute tag value. Valid range is 0 – 65535.
Defaults
parameterdefault
value0
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
This value does not apply to routes learned from other routers. For these routes, the route tag propagates
with the route.
Example
-> ipv6 rip route-tag 30
Release History
Release 5.1.6; command was introduced.
Related Commands
show ipv6 ripDisplays RIPng status and general configuration information.
MIB Objects
alaProtocolripng
alaRipngRouteTag
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-61
Page 88
ipv6 rip update-intervalIPv6 Commands
ipv6 rip update-interval
Configures the RIPng update interval. This is the interval, in seconds, that RIPng routing updates will be
sent out.
ipv6 rip update-interval seconds
Syntax Definitions
secondsInterval, in seconds, that RIPng routing updates are sent out. Valid range
is 0 - 120.
Defaults
parameterdefault
seconds30
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
Use this command, along with the ipv6 rip jittercommand to configure RIPng updates.
Example
-> ipv6 rip update-interval 30
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 rip jitterConfigures an offset value for RIPng updates.
show ipv6 ripDisplays RIPng status and general configuration information.
MIB Objects
alaRipng
alaRipngUpdateInterval
page 2-62Release 5.1.6.R02 User Guide SupplementJune 2005
allAll RIPng routes are added to any triggered updates.
updated-onlyOnly route changes that are causing the triggered update are included in
the update packets.
noneRIPng routes are not added to triggered updates.
Defaults
parameterdefault
all | updated-only | noneupdated-only
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
• If set to “all”, all routes are sent in the update, not just route changes, which increases RIPng traffic on
the network.
• If set to “none”, no triggered updates are sent, which can cause delays in network convergence.
Example
-> ipv6 rip triggered-sends none
Release History
Release 5.1.6; command was introduced.
Related Commands
show ipv6 ripDisplays RIPng status and general configuration information.
MIB Objects
alaProtocolripng
alaRipngTriggeredSends
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-63
Page 90
ipv6 rip interfaceIPv6 Commands
ipv6 rip interface
Creates/deletes a RIPng interface.
ipv6 rip interface if_name
[no] ipv6 rip interface if_name
Syntax Definitions
if_nameIPv6 interface name.
Defaults
N/A.
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
• By default, a RIPng interface is created in the enabled state.
• Routing is enabled on a VLAN when you create a router port. However, to enable RIPng routing, you
must also configure and enable a RIPng routing interface on the VLAN’s IP router port. For more
information on VLANs and router ports, see Chapter 21, “VLAN Management Commands.”
• RIPng will support a maximum of 20 interfaces.
Example
-> ipv6 rip interface Test_Lab
Release History
Release 5.1.6; command was introduced.
page 2-64Release 5.1.6.R02 User Guide SupplementJune 2005
Page 91
IPv6 Commandsipv6 rip interface
Related Commands
ipv6 load ripLoads RIPng into memory.
ipv6 rip statusEnables/disables RIPng on the switch.
ipv6 rip interface recv-statusConfigures IPv6 RIPng interface “Receive” status. When this status
is set to "enable", packets can be received on this interface.
ipv6 rip interface send-statusConfigures IPv6 RIPng interface “Send” status. When this status is
set to "enable", packets can be sent on this interface.
show ipv6 rip interfaceDisplays information for all or specified RIPng interfaces.
MIB Objects
alaRipngInterfaceTable
alaRipngInterfaceStatus
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-65
Page 92
ipv6 rip interface metricIPv6 Commands
ipv6 rip interface metric
Configures the RIPng metric or cost for a specified interface. You can set priorities for routes generated by
a switch by assigning a metric value to routes generated by that switch’s RIPng interface. For example,
routes generated by a neighboring switch may have a hop count of 1. However, you can lower the priority
of routes generated by that switch by increasing the metric value for routes generated by the RIPng interface.
ipv6 rip interface if_name metric value
Syntax Definitions
if_nameIPv6 interface name.
valueMetric value. Valid range is 1 - 15.
Defaults
parameterdefault
value1
Platforms Supported
OmniSwitch 6624, 6648, 7700, 7800, 8800
Usage Guidelines
When you configure a metric for a RIPng interface, this metric cost is added to the metric of the incoming
route.
Example
-> ipv6 rip Test_Lab metric 1
Release History
Release 5.1.6; command was introduced.
Related Commands
ipv6 rip interfaceCreates/deletes a RIPng interface.
show ipv6 rip interfaceDisplays information for all or specified RIPng interfaces.
MIB Objects
alaRipngInterfaceTable
alaRipngInterfaceMetric
page 2-66Release 5.1.6.R02 User Guide SupplementJune 2005
Page 93
IPv6 Commandsipv6 rip interface recv-status
ipv6 rip interface recv-status
Configures IPv6 RIPng interface “Receive” status. When this status is set to "enable", packets can be
received on this interface. When it is set to "disable", packets will not be received on this interface.
Release 5.1.6.R02 User Guide SupplementJune 2005page 2-67
Page 94
ipv6 rip interface send-statusIPv6 Commands
ipv6 rip interface send-status
Configures IPv6 RIPng interface “Send” status. When this status is set to "enable", packets can be sent
from this interface. When it is set to "disable", packets will not be sent from this interface.