IPX

IPX

Syntax Description

Keywords

Examples

Related Commands

IPX

This section sets parameters that control how IPX packets are handled on each interface of the device.

configure IPX {{Ethernet | WAN} slot:port | VPN number | Bridge [0.sub-interface]}

Syntax Description

Ethernet | WAN

Identifies the type of port for which you want to configure this section.

slot:port

For a modular platform, identify the slot:

For theVPN 5008 chassis, slot 0 is the far left slot.

For the VPN 5002 chassis, slot 0 is the top slot.

For the VPN 5001 concentrator, enter only the port number. For a module with one port, the port is 0.

VPN number

Identifies the VPN port you configured in the Tunnel Partners section for a LAN-to-LAN tunnel.

Bridge [0.sub-interface]

If you enabled bridging on one or more IPX ports, you can bridge all the ports together and assign a single IPX network to the bridge. You can create multiple Bridge sections with unique IPX networks by using sub-interface numbers, from 1 to 255.

Ethernet \| WAN	Identifies the type of port for which you want to configure this section.
slot:port	For a modular platform, identify the slot: For theVPN 5008 chassis, slot 0 is the far left slot. For the VPN 5002 chassis, slot 0 is the top slot. For the VPN 5001 concentrator, enter only the port number. For a module with one port, the port is 0.
VPN number	Identifies the VPN port you configured in the Tunnel Partners section for a LAN-to-LAN tunnel.
Bridge [0.sub-interface]	If you enabled bridging on one or more IPX ports, you can bridge all the ports together and assign a single IPX network to the bridge. You can create multiple Bridge sections with unique IPX networks by using sub-interface numbers, from 1 to 255.

Keywords

After entering the configure command for the section, enter one or more of the following keywords.

Mode = {Routed | Bridged | Off}

The Mode keyword describes the method the interface is to use to forward IPX packets through the device.

Routed enables the port of the device. It specifies that the device is attached to a routed network and the device will forward packets to its other ports if it is a router or to the virtual private networks if it is a VPN access server. If the device is a router, packets are forwarded by looking up the network address in the device's routing table maintained by IPX RIP (Routing Information Protocol). Packets are forwarded to the virtual private network depending on the users that are attached to the server. It will use the routing table maintained by RIP to forward packets from the virtual private network to the local area network.

Bridged enables the port of a router to be attached to a bridged network and forward packets based on the physical address using the router's bridge cache maintained through the IEEE Spanning Tree Protocol or through active listening. If Bridged is specified, bridging must be enabled globally in the router in the Bridging Global section and on the interface in the Bridging section. It is possible to assign an IPX address to the router using the [IPX Bridge] section if it is to be managed by VPN 5000 Manager using the IPX protocol while bridging.

Off disables the port of the device. If Off is specified, then IPX packets received on the interface will be silently discarded.

RipTimer = Number

The RipTimer keyword allows the IPX RIP (Routing Information Protocol) timer to be set on the interface. This value specifies the interval, in seconds, the device sends out IPX RIP packets on the network segment attached to this interface. The RIP packets sent out on this interface contain routing information about networks for which this interface is responsible. The number can be between 1 and 180 seconds. The default is 60.

SapTimer = Number

The SapTimer keyword allows the IPX SAP (Service Advertising Protocol) timer to be set on the interface. This value specifies the interval, in seconds, the device sends out IPX SAP packets on the network segment attached to this interface. The SAP packets sent out on this interface contain information about services (such as servers, printers, etc.) for which this interface is responsible. The number can be between 1 and 180 seconds. The default is 60.

BlockType20 = {On | Off}

The BlockType20 keyword specifies how IPX Packet Type 20 is handled on the interface. In order for certain protocol implementations, like NetBIOS, to function in the NetWare environment, routers must allow a broadcast packet to be propagated throughout an internet. The IPX Packet Type 20 is designated to perform broadcast propagation for these protocols.

When a device receives this packet, it rebroadcasts it across all interfaces, except the one it received it on, and includes the network number of that interface in the data portion of the packet. The IPX Router Specification from Novell notes that Type 20 packets should not be propagated across slower links (line X.25 and asynchronous links) with bandwidths of less than 1 Mbps.

On prevents these packets from being rebroadcast out an interface. This is useful for on-demand WAN links where the link may be brought up as a result of this packet.

Off allows these propagated packets to be rebroadcast out the interface.

OutFilters = "filter_name" ["filter_name"] ["filter_name"] ["filter_name"]

The OutFilters keyword allows a named set of IPX packet filtering rules to be associated with the output side of the interface. Up to four filter sets may be specified, each enclosed in double quotes and separated by white space. If no string is specified, then the keyword is ignored by the parser. This feature can be used to turn off a filter set (or sets) without deleting the keyword.

Packets being transmitted on the interface will be compared against the filter list(s) specified. Any packet not explicitly allowed by the rule set is dropped silently. When more than one set is defined, the filter interpreter will process the sets in the order specified.

See the IPX Filter section for a definition of the rules that may be included in an IPX packet filter.

InFilters = "filter_name" ["filter_name"] ["filter_name"] ["filter_name"]

The InFilters keyword allows a named set of IPX packet filtering rules to be associated with the input side of the interface. Up to four filter sets may be specified, each enclosed in double quotes and separated by white space. If no string is specified, then the keyword is ignored by the parser. This feature can be used to turn off a filter set (or sets) without deleting the keyword.

Packets being received on the interface will be compared against the filter list(s) specified. Any packet not explicitly allowed by the rule set is dropped silently. When more than one set is defined, the filter interpreter will process the sets in the order specified.

See theIPX Filter section for a definition of the rules that may be included in an IPX packet filter.

FrameTypeII = {Seed | Auto | NoSeed | Off}

FrameRaw = {Seed | Auto | NoSeed | Off}

Frame8022 = {Seed | Auto | NoSeed | Off}

FrameSNAP = {Seed | Auto | NoSeed | Off}

Cisco Systems routers support four IPX frame types, and will perform routing between frame types. The four frame types supported are Frame Type II, Frame Raw, Frame 8022, and Frame SNAP. Each Ethernet interface may be configured to simultaneously handle any or all of the frame types. The seed parameter defines what the device is to do with the network information (with respect to the frame type) when starting up.

Seed tells the device to listen for an IPX network number being set by another router (including Novell software routers residing on servers) on the segment connected to this interface and use this number if it exists. If it does not discover a number in use, the device will use the configured IPX network number to set the network number for the segment.

Auto tells the device to listen for an IPX network number being set by another router (including Novell software routers residing on servers) on the segment connected to this interface and use this number if it exists. If it doesn't discover a number in use, the device will automatically generate a valid number using its routing tables.

NoSeed tells the device to listen for an IPX network number being set by another router (including Novell software routers residing on servers) on the segment connected to this interface and use this number if it exists. If it doesn't discover a number in use, the device will wait indefinitely until a number is set by another router on the segment.

Off means that the device will neither listen for, nor send, packets with the specified frame type on this interface.

Numbered = {On | Off}

The Numbered keyword specifies whether the wide area network connected to this interface will have an IPX network number associated with it. If numbered is On then you must set an IPX network number for this WAN interface. On WAN interfaces it is only necessary to specify the network number and not the frame and seed parameters as you do with Ethernet interfaces.

Many wide area network connections are simple point-to-point links. These links do not generally require a network number because there are only two devices on the link. All traffic sent from one end is, by definition, destined for the other end. You generally do not need a numbered WAN interface if you are using the PPP transport protocol.

In contrast, Frame Relay networks may have a number of participating routers connected through a single physical interface. Because of this, use of the Frame Relay transport protocol requires a numbered WAN interface.

Updates = {Periodic | Triggered}

The Updates keyword specifies the way in which the device sends RIP information over the link.

When updates are designated as Periodic, the device will send RIP packets over the link at the time interval defined by the RIPTimer keyword. These periodic update packets will cause a WAN interface set for dial-on-demand operation to either stay up indefinitely or to continuously dial, connect, and then drop the connection.

When updates are designated as Triggered, the device will send RIP packets only when there has been an update to its routing table information, or when it has detected a change in the accessibility of the next hop router.

NodeProxy = {On | Off}

Besides defining a method for router-to-router communication, PPP defines a method for individual client machines to dial in to an interface. Once a client machine has connected to an interface in this fashion, the device provides proxy services which allow the client machine to participate as a node on one of the device's local networks.

The NodeProxy keyword allows the device to dynamically reserve an IPX address on the Ethernet for the WAN interface. This proxy address will be used if the remote PPP IPX implementation requires address negotiation (which is typical of end nodes).

RemoteNet = Hex_number

The RemoteNet keyword specifies an IPX address that is set aside for remote nodes (such as dial-in users accessing the LAN remotely). This net number is set to an IPX network number from the device's Ethernet interface(s). Values for this number may range from 1 to FFFFFFFE.

Net = Hex_number

The Net keyword is a number that must be assigned if the interface is being configured for Frame Relay. This number is assigned to the device's WAN interface, and must be an unused IPX network number. Values for this number may range from 1 to FFFFFFFE.

FrameTypeIINet = Hex_number

FrameRawNet = Hex_number

Frame8022Net = Hex_number

FrameSNAPNet = Hex_number

Ethernet interfaces that have frame types set to Seed must be assigned a net number. These numbers are eight-digit hexadecimal numbers that uniquely identify the network segment connected to this interface. Values range from 1 to FFFFFFFE.

Accidental selection of an IPX network number which is already in use on another network segment may cause hard-to-diagnose problems. You should carefully track which IPX network numbers are in use, and where they are located in your configuration.

Mode = {Routed \| Bridged \| Off}	The Mode keyword describes the method the interface is to use to forward IPX packets through the device. Routed enables the port of the device. It specifies that the device is attached to a routed network and the device will forward packets to its other ports if it is a router or to the virtual private networks if it is a VPN access server. If the device is a router, packets are forwarded by looking up the network address in the device's routing table maintained by IPX RIP (Routing Information Protocol). Packets are forwarded to the virtual private network depending on the users that are attached to the server. It will use the routing table maintained by RIP to forward packets from the virtual private network to the local area network. Bridged enables the port of a router to be attached to a bridged network and forward packets based on the physical address using the router's bridge cache maintained through the IEEE Spanning Tree Protocol or through active listening. If Bridged is specified, bridging must be enabled globally in the router in the Bridging Global section and on the interface in the Bridging section. It is possible to assign an IPX address to the router using the [IPX Bridge] section if it is to be managed by VPN 5000 Manager using the IPX protocol while bridging. Off disables the port of the device. If Off is specified, then IPX packets received on the interface will be silently discarded.
RipTimer = Number	The RipTimer keyword allows the IPX RIP (Routing Information Protocol) timer to be set on the interface. This value specifies the interval, in seconds, the device sends out IPX RIP packets on the network segment attached to this interface. The RIP packets sent out on this interface contain routing information about networks for which this interface is responsible. The number can be between 1 and 180 seconds. The default is 60.
SapTimer = Number	The SapTimer keyword allows the IPX SAP (Service Advertising Protocol) timer to be set on the interface. This value specifies the interval, in seconds, the device sends out IPX SAP packets on the network segment attached to this interface. The SAP packets sent out on this interface contain information about services (such as servers, printers, etc.) for which this interface is responsible. The number can be between 1 and 180 seconds. The default is 60.
BlockType20 = {On \| Off}	The BlockType20 keyword specifies how IPX Packet Type 20 is handled on the interface. In order for certain protocol implementations, like NetBIOS, to function in the NetWare environment, routers must allow a broadcast packet to be propagated throughout an internet. The IPX Packet Type 20 is designated to perform broadcast propagation for these protocols. When a device receives this packet, it rebroadcasts it across all interfaces, except the one it received it on, and includes the network number of that interface in the data portion of the packet. The IPX Router Specification from Novell notes that Type 20 packets should not be propagated across slower links (line X.25 and asynchronous links) with bandwidths of less than 1 Mbps. On prevents these packets from being rebroadcast out an interface. This is useful for on-demand WAN links where the link may be brought up as a result of this packet. Off allows these propagated packets to be rebroadcast out the interface.
OutFilters = "filter_name" ["filter_name"] ["filter_name"] ["filter_name"]	The OutFilters keyword allows a named set of IPX packet filtering rules to be associated with the output side of the interface. Up to four filter sets may be specified, each enclosed in double quotes and separated by white space. If no string is specified, then the keyword is ignored by the parser. This feature can be used to turn off a filter set (or sets) without deleting the keyword. Packets being transmitted on the interface will be compared against the filter list(s) specified. Any packet not explicitly allowed by the rule set is dropped silently. When more than one set is defined, the filter interpreter will process the sets in the order specified. See the IPX Filter section for a definition of the rules that may be included in an IPX packet filter.
InFilters = "filter_name" ["filter_name"] ["filter_name"] ["filter_name"]	The InFilters keyword allows a named set of IPX packet filtering rules to be associated with the input side of the interface. Up to four filter sets may be specified, each enclosed in double quotes and separated by white space. If no string is specified, then the keyword is ignored by the parser. This feature can be used to turn off a filter set (or sets) without deleting the keyword. Packets being received on the interface will be compared against the filter list(s) specified. Any packet not explicitly allowed by the rule set is dropped silently. When more than one set is defined, the filter interpreter will process the sets in the order specified. See theIPX Filter section for a definition of the rules that may be included in an IPX packet filter.
FrameTypeII = {Seed \| Auto \| NoSeed \| Off} FrameRaw = {Seed \| Auto \| NoSeed \| Off} Frame8022 = {Seed \| Auto \| NoSeed \| Off} FrameSNAP = {Seed \| Auto \| NoSeed \| Off}	Cisco Systems routers support four IPX frame types, and will perform routing between frame types. The four frame types supported are Frame Type II, Frame Raw, Frame 8022, and Frame SNAP. Each Ethernet interface may be configured to simultaneously handle any or all of the frame types. The seed parameter defines what the device is to do with the network information (with respect to the frame type) when starting up. Seed tells the device to listen for an IPX network number being set by another router (including Novell software routers residing on servers) on the segment connected to this interface and use this number if it exists. If it does not discover a number in use, the device will use the configured IPX network number to set the network number for the segment. Auto tells the device to listen for an IPX network number being set by another router (including Novell software routers residing on servers) on the segment connected to this interface and use this number if it exists. If it doesn't discover a number in use, the device will automatically generate a valid number using its routing tables. NoSeed tells the device to listen for an IPX network number being set by another router (including Novell software routers residing on servers) on the segment connected to this interface and use this number if it exists. If it doesn't discover a number in use, the device will wait indefinitely until a number is set by another router on the segment. Off means that the device will neither listen for, nor send, packets with the specified frame type on this interface.
Numbered = {On \| Off}	The Numbered keyword specifies whether the wide area network connected to this interface will have an IPX network number associated with it. If numbered is On then you must set an IPX network number for this WAN interface. On WAN interfaces it is only necessary to specify the network number and not the frame and seed parameters as you do with Ethernet interfaces. Many wide area network connections are simple point-to-point links. These links do not generally require a network number because there are only two devices on the link. All traffic sent from one end is, by definition, destined for the other end. You generally do not need a numbered WAN interface if you are using the PPP transport protocol. In contrast, Frame Relay networks may have a number of participating routers connected through a single physical interface. Because of this, use of the Frame Relay transport protocol requires a numbered WAN interface.
Updates = {Periodic \| Triggered}	The Updates keyword specifies the way in which the device sends RIP information over the link. When updates are designated as Periodic, the device will send RIP packets over the link at the time interval defined by the RIPTimer keyword. These periodic update packets will cause a WAN interface set for dial-on-demand operation to either stay up indefinitely or to continuously dial, connect, and then drop the connection. When updates are designated as Triggered, the device will send RIP packets only when there has been an update to its routing table information, or when it has detected a change in the accessibility of the next hop router.
NodeProxy = {On \| Off}	Besides defining a method for router-to-router communication, PPP defines a method for individual client machines to dial in to an interface. Once a client machine has connected to an interface in this fashion, the device provides proxy services which allow the client machine to participate as a node on one of the device's local networks. The NodeProxy keyword allows the device to dynamically reserve an IPX address on the Ethernet for the WAN interface. This proxy address will be used if the remote PPP IPX implementation requires address negotiation (which is typical of end nodes).
RemoteNet = Hex_number	The RemoteNet keyword specifies an IPX address that is set aside for remote nodes (such as dial-in users accessing the LAN remotely). This net number is set to an IPX network number from the device's Ethernet interface(s). Values for this number may range from 1 to FFFFFFFE.
Net = Hex_number	The Net keyword is a number that must be assigned if the interface is being configured for Frame Relay. This number is assigned to the device's WAN interface, and must be an unused IPX network number. Values for this number may range from 1 to FFFFFFFE.
FrameTypeIINet = Hex_number FrameRawNet = Hex_number Frame8022Net = Hex_number FrameSNAPNet = Hex_number	Ethernet interfaces that have frame types set to Seed must be assigned a net number. These numbers are eight-digit hexadecimal numbers that uniquely identify the network segment connected to this interface. Values range from 1 to FFFFFFFE. Accidental selection of an IPX network number which is already in use on another network segment may cause hard-to-diagnose problems. You should carefully track which IPX network numbers are in use, and where they are located in your configuration.

Examples

The following shows an Ethernet interface with the 802.2 frame type set for seed.

[ IPX Ethernet 1 ]
Mode                     = Routed
FrameTypeIINet           = 0
FrameRawNet              = 0
Frame8022Net             = CAFEF00D
FrameSNAPNet             = 0
FrameTypeII              = Off
FrameRaw                 = Off
Frame8022                = Seed
FrameSNAP                = Off

Related Commands

Command Description

configure Bridging

Sets bridging parameters for an interface

configure Bridging Global

Enables bridging for the device

edit config IPX Filter

Creates IPX packet filters

edit config IPX Route Filter

Creates IPX route filters

edit config IPX SAP Filter

Creates IPX server filters

show ipx

Shows IPX configuration and routing

Command	Description
configure Bridging	Sets bridging parameters for an interface
configure Bridging Global	Enables bridging for the device
edit config IPX Filter	Creates IPX packet filters
edit config IPX Route Filter	Creates IPX route filters
edit config IPX SAP Filter	Creates IPX server filters
show ipx	Shows IPX configuration and routing

Table of Contents

IPX

Syntax Description

Keywords

Examples

Related Commands