Configuring Networking Protocols

• Network address

• Subnetwork address

• IP subnet mask

You must also do the following global configurations:

• Select a routing protocol, such as the Enhanced Interior Gateway Routing Protocol (EIGRP) or the Routing Information Protocol (RIP).

• Assign IP network numbers without specifying subnet values.

EIGRP saves bandwidth by sending routing updates only when routing information changes. The updates contain only information about the link that changed, not the entire routing table. EIGRP also takes into consideration the available bandwidth when determining the rate at which it transmits updates.

	Command	Purpose
Step 1	Router(config)# interface fastethernet slot/subslot/interface Router(config-if)#	Enters Ethernet interface configuration mode to configure a particular Fast Ethernet interface.
Step 2	Router(config-if)# ip address ip-address subnet-mask	Assigns an IP address and subnet mask to the interface.
Step 3	Router(config-if)# exit Router(config)#	Returns to global configuration mode.
Step 4	Router(config)# router rip Router(config-router)#	Defines RIP as the routing protocol and starts the RIP routing process.
Step 5	Router(config-router)# network network-number	Specifies the IP address of the network of directly connected networks. The routing process associates interfaces with the appropriate addresses and begins processing packets on the specified network.
Step 6	Router(config-router)# exit Router(config)#	Returns to global configuration mode.
Step 7	Router(config)# router igrp autonomous-system-number Router(config-router)#	Defines IGRP as the IP routing protocol. The autonomous system number is the autonomous system to which this switch router belongs.
Step 8	Router(config-router)# network network-number	Defines the directly connected networks that run IGRP.
Step 9	Router(config-router)# exit Router(config)#	Returns to global configuration mode.
Step 10	Router(config)# router eigrp autonomous-system-number Router(config-router)#	Defines EIGRP as the IP routing protocol. The autonomous system number is the autonomous system to which this switch router belongs.
Step 11	Router(config-router)# network network-number	Defines the directly connected networks that run EIGRP. The network number is the number of the network that is advertised by this switch router.
Step 12	Router(config-router)# exit Router(config)#	Returns to global configuration mode.
Step 13	Router(config)# router ospf process-id Router(config-router)#	Defines OSPF as the IP routing protocol. The process ID identifies a unique OSPF router process. This number is internal to the switch router only; the process ID does not have to match the process IDs on other routers.
Step 14	Router(config-router)# network network-address wildcard-mask area area-id	Assigns an interface to a specific area. The network address is the address of directly connected networks or subnets. The wildcard mask is an inverse mask used to compare a given address with interface addressing to determine whether OSPF will use this interface. The area parameter identifies the interface as belonging to an area. The area ID specifies the area associated with the network address.
Step 15	Router(config-router)# exit Router(config)#	Returns to global configuration mode.
Step 16	Router(config)# router isis	Defines IS-IS as the IP routing protocol.
Step 17	Router(config-router)# net network-entity-title	Configures network entity titles (NETs) for the routing process; you can specify a name for a NET as well as an address.
Step 18	Router(config-router)# interface interface-type slot/subslot/interface Router(config-if)#	Enters interface configuration mode.
Step 19	Router(config-if)# ip router isis [tag]	Specifies that this interface should run IS-IS.
Step 20	Router(config-router)# end Router#	Returns to privileged EXEC mode.
Step 21	Router# copy system:running-config nvram:startup-config	Saves your configuration changes to NVRAM.

Command	Purpose
show ip protocol	Displays values about routing timers and network information associated with the entire router. Use this information to identify a router that is suspected of delivering bad router information.
show ip route	Displays the contents of the IP routing table. The routing table contains entries for all known networks and subnetworks, and contains a code that indicates how that information was learned.
show ip interfaces	Displays the status and global parameters associated with an interface. Cisco IOS automatically enters a directly connected route in the routing table if the interface is one through which a protocol can send and receive packets. Such an interface is marked "up." If the interface is unusable, it is removed from the routing table.
debug ip rip	Displays RIP routing updates as the updates are sent and received.
debug lss ipucast {events | errors | reload}	Displays updates sent to the interface module for the IP switching control layer.

The routing protocols that the switch router uses to discover multicast groups and build routes for each group follow:

• Protocol Independent Multicast (PIM)

• Distance Vector Multicast Routing Protocol (DVMRP)

• Constrained multicast flooding (CMF)

The Catalyst 8500 supports interoperability with routers configured for DVMRP.

• Senders and receivers are in close proximity to each other.

• The internetwork has fewer senders than receivers.

• The stream of multicast traffic is constant.

When a sender wants to send data, it first sends the data to the rendezvous point. When a router is ready to receive data, it registers with the rendezvous point. After the data stream begins to flow from the sender to the rendezvous point and then to the receiver, routers in the data path optimize the path by automatically removing any unnecessary hops, including the rendezvous point.

PIM sparse mode is optimized for environments in which there are many multipoint data streams and each multicast stream goes to a relatively small number of LANs in the internetwork. PIM sparse mode is most useful under these conditions:

• There are few receivers in the group.

• Senders and receivers are separated by WAN links.

• The stream of multicast traffic is intermittent.

	Command	Purpose
Step 1	Router(config)# ip multicast-routing	Enables IP multicast on the switch router.
Step 2	Router(config)# interface fastethernet slot/subslot/interface Router(config-if)#	Enters Ethernet interface configuration mode to configure the Fast Ethernet interface.
Step 3	Router(config-if)# ip address ip-address subnet-mask	Assigns an IP address and subnet mask to the interface.
Step 4	Router(config-if)# ip pim [dense-mode | sparse-mode | sparse-dense-mode]	Enables IP multicast routing on the interface. You can indicate dense mode, sparse mode, or sparse-dense mode (for internetworks that include both cases).
Step 5	Router(config-if)# end Router#	Returns to privileged EXEC mode.
Step 6	Router# copy system:running-config nvram:startup-config	Saves your configuration changes to NVRAM.

Command	Purpose
show ip mroute	Displays the complete multicast routing table.
show ip mroute count	Displays the combined statistics of packets processed by the route processor and the Ethernet interface modules.
debug lss ipmcast {events | errors | reload}	Displays the updates sent to the interface module for the IP switching control layer.

• A datagram, connectionless protocol that does not require an acknowledgment for each packet

• A Layer 3 (network) protocol that defines the internetwork and internode addresses

• A router specification used to identify the Novell NetWare protocol suite

• Routing Information Protocol (RIP)—Facilitates the exchange of routing information

• NetWare Core Protocol (NCP)—Provides client-to-server connections and applications

• Sequenced Packet Exchange (SPX)—Service for Layer 4 (Transport) connection-oriented services

• Service Advertising Protocol (SAP)—Advertises NetWare services and addresses, which makes service availability dynamic

Note   Layer 3 switching does not support the NetWare Link Services Protocol (NLSP).

Since both the network number and the host address are needed to deliver traffic to a host, addresses are usually given as network numbers, followed by host addresses, separated with dots, as in the example: 4a.0000.0c00.23fe. In this example, the network number is 4a, and the host address is 0000.0c00.23fe.

The serial interface does not have a MAC address. It uses the default Novell node address, which is the MAC address of the first activated interface.

Once you have started IPX routing and enabled load sharing (if needed) on the router, you can configure the interface for Novell IPX routing.

You can assign multiple network numbers to an interface, allowing support of different encapsulation types. The IPX network number is the number of the Novell network to which the interface is attached. IPX packets received on an interface that does not have a network number are ignored.

Step 2   Set the optional encapsulation type, if it is different from the default.

	Command	Purpose
Step 1	Router(config)# ipx routing [node]	Enables Novell IPX routing and start the IPX routing process. If no node address is specified, the switch router uses the MAC address of the interface.
Step 2	Router(config)# ipx maximum-paths paths	Allows load sharing over parallel metric paths to the destination. The maximum number of parallel paths is 6 for the enhanced Gigabit Ethernet interfaces and 2 for other interfaces; the default number is 1.
Step 3	Router(config)# interface fastethernet slot/subslot/interface Router(config-if)#	Enters Ethernet interface configuration mode to configure the Fast Ethernet interface.
Step 4	Router(config-if)# ipx network network [encapsulation encapsulation-type] [secondary]	Assigns a unique hexadecimal IPX network number (up to 8 numbers in length) to the interface. The encapsulation type is optional. You can specify one of the following types: novell-ether (the default), sap, arpa, or snap.
Step 5	Router(config-if)# end Router#	Returns to privileged EXEC mode.
Step 6	Router# copy system:running-config nvram:startup-config	Saves your configuration changes to NVRAM.

Once IPX routing is configured, you can monitor and troubleshoot the protocol operation using the following commands:

Command	Purpose
show ipx cache	Displays the contents of the IPX fast-switching cache.
show ipx interfaces	Displays the status and parameters of the interfaces configured for IPX.
show ipx interface fastethernet slot/subslot/interface	Displays the status and parameters for the specified Fast Ethernet IPX interface.
show ipx route	Displays the contents of the IPX routing table.
show ipx servers	Displays the list of IPX servers discovered through SAP advertisements, plus the network address, port number, and the number of hops and ticks to the server.
show ipx traffic	Displays the number and type of IPX packets transmitted and received, as well as the number of broadcasts, SAPs, and routing packets received.
debug ipx routing activity	Turns on debugging information about RIP update packets.
debug ipx sap	Turns on debugging information about SAP update packets.

The AppleTalk protocol architecture requires that security measures be implemented at higher application levels. Layer 3 switching supports AppleTalk distribution lists, allowing control of routing updates on a per-interface basis.

To prevent any possible corruption of the AARP table in any AppleTalk node that is performing address gleaning through Media Access Control (MAC), Layer 3 switching AppleTalk does not forward packets with local source and destination network addresses.