Installation and Getting Started Guide
HP's PBR routing is based on standard and extended ACLs and route-maps. The ACLs classify the traffic. Route
maps that match on the ACLs set routing attributes for the traffic. HP's implementation of PBR uses high
performance switching algorithms including route caches and route tables.
For information, see the "Using Access Control Lists (ACLs)" chapter in the Advanced Configuration and
Network Address Translation
Network Address Translation (NAT) enables private IP networks that use nonregistered IP addresses to connect
to the Internet. Configure NAT on the HP device at the border of an inside network and an outside network (such
as the Internet). NAT translates the internal local addresses to globally unique IP addresses before sending
packets to the outside network. NAT also allows a more graceful renumbering strategy for organizations that are
changing service providers or voluntarily renumbering into Classless Interdomain Routing (CIDR) blocks.
Use NAT to translate your private (inside) IP addresses into globally unique (outside) IP addresses when
communicating outside of your network.
NOTE: This feature is supported on all chassis routing switches with Redundant Management modules. It is not
available on HP fixed-port devices.
For information, see the "Network Address Translation" chapter in the Advanced Configuration and Management
HP routing switches support the Internet Packet Exchange (IPX) protocol created by Novell™. IPX is based on a
client-server networking architecture.
The Routing Information Protocol (RIP) and the Service Advertisement Protocol (SAP) are two key components of
Novell NetWare and its IPX protocol suite. By default, Novell NetWare versions 3.x and 4.x broadcast RIP and
SAP updates at 60 second intervals.
Up to four different IPX network numbers and frame encapsulation types can be defined for each IPX interface on
an HP routing switch. Therefore, you can define and receive traffic from four separate IPX networks on a single
interface. Each of the networks must have a distinct network number and encapsulation type (Ethernet SNAP,
Ethernet 802.2, Ethernet 802.3 and Ethernet II).
IPX Forward Filters
You can define IPX filters to control client access to servers. For example, if you want to restrict access to a print
server to specific users, you can define a filter group containing filters that check for the source IPX addresses and
nodes of those users. The filter explicitly permits users that match a filter to access the print server specified by
the destination address, destination node, and socket number of the print server.
For details on IPX filtering and how to configure the filters, see the "Configuring IPX" chapter in the Advanced
Configuration and Management Guide.
IPX/RIP and IPX/SAP Filters
In addition to controlling client access to servers, you can control the following:
Client access to other IPX networks. You control client access to other IPX networks by filtering IPX/RIP
routes received or advertised by the HP routing switch.
Client access to services. You control service by filtering IPX/SAP service advertisements sent by the HP
routing switch. To do so, configure SAP access lists.
For information on configuring IPX/RIP and IPX/SAP filters and ACLs, see the "Configuring IPX" chapter in the
Advanced Configuration and Management Guide.
7 - 22