User guide

September 2009
Page 36 of 79 OmniSwitch 6400/6850/6855/9000/9000E—Release 6.4.2.R01
IP Route Map Redistribution
Route map redistribution provides the ability to control which routes from a source protocol are learned
and distributed into the network of a destination protocol. A route map consists of one or more user-
defined statements that can determine which routes are allowed or denied access to the network. In
addition, a route map may also contain statements that modify route parameters before they are
redistributed.
Redistribution is configured by specifying a source and destination protocol and the name of an
existing route map. Criteria specified in the route map is applied to routes received from the source
protocol.
IPX Routing
The Internet Packet Exchange (IPX) protocol, developed by Novell for NetWare, is a Layer 3 protocol
used to route packets through IPX networks. (NetWare is Novell’s network server operating system.)
This implementation of IPX routing is software based with limited performance.
IPX specifies a connectionless datagram similar to the IP packet of TCP/IP networks. An IPX network
address consists of two parts: a network number and a node number. The IPX network number is
assigned by the network administrator. The node number is the Media Access Control (MAC) address
for a network interface in the end node.
IS-IS
Intermediate System-to-Intermediate System (IS-IS) is an International Organization for
Standardization (ISO) dynamic routing specification. IS-IS is a shortest path first (SPF), or link state
protocol. Also considered an interior gateway protocol (IGP), IS-IS distributes routing information
between routers in a single Autonomous System (AS) in IP environments. IS-IS chooses the least-cost
path as the best path. It is suitable for complex networks with a large number of routers by providing
faster convergence where multiple flows to a single destination can be simultaneously forwarded
through one or more interfaces.
In-Service Software Upgrade (ISSU)
The In-Service Software Upgrade (ISSU) feature is used to patch the CMM images running on an
OmniSwitch 9000E with minimal disruption to data traffic. The CMM images can be patched on a fully
synchronized, certified, and redundant system running an ISSU capable build without requiring a reboot of
the switch. Only non-NI related issues are ISSU capable.
• Switches running an ‘R##’ build, such as 6.4.2.123.R01 do not support ISSU upgrades. The
switch must first be upgraded to an ‘S##’ build such as 6.4.2 .123.S01.
• Periodic ISSU capable patches will be available on the Service & Support website. These patches
contain all CMM-only related fixes and will support the ISSU capability.
• ISSU patches are only supported within the same ‘S##’ branch. For example, if a switch is running
6.4.2.123.S01 then only 6.4.2.###.S01 images can used to perform an ISSU patch. If a switch is
running 6.4.2.234.S02 then only 6.4.2.###.S02 images can used to perform an ISSU patch.
• Approximately every six months a new ISSU capable branch will be available from Service &
Support (i.e. S01, S02, S03, etc.). Each new branch will include all NI related fixes that were
not supported in the previous ISSU branch. Upgrading from one ISSU branch to another will
require a reboot and should be scheduled during a maintenance window.
• If a critical NI related patch is required, it will be necessary to move to an “R##” related build.
Since “R##” related builds do not support the ISSU feature, a reboot will be required and should