chabot college cisco networking academy chabot college semester 3 novell ipx

CHABOT COLLEGE CISCO NETWORKING ACADEMYCHABOT COLLEGE CISCO NETWORKING ACADEMY

Chabot CollegeChabot College

Semester 3 Semester 3

Novell IPXNovell IPX


NetWare NetworksNetWare Networks

In the early 1980’s, Novell developed a network operating system (NOS)(NOS) that grew to dominate the market: NetWare.

– Based on work done by Xerox (XNS)

– Client/Server

– Multi-platform support (Mac, PC, UNIX)

– Proprietary Protocol Stack: IPX/SPX

– NetWare servers act as routers


Major NetWare VersionsMajor NetWare Versions

– NetWare 2.x

– NetWare 3.12

– NetWare 4.11 (dubbed IntraNetWare)

– NetWare 5 (current release)

In the last 15 years, NetWare has seen major changes in Ethertype, directory services, and layer 3 protocols.


Decline of NovellDecline of Novell

With the rapid emergence of another NOS, Microsoft NTMicrosoft NT, and the TCP/IP-driven Internet:

– Novell no longer leads the NOS market

– NetWare 5.0 is IP-based

– Novell’s Directory Services (NDS) remains viable


Novell TodayNovell Today

“IPX and NLMs are dead” -- 9/00, Carl Ledbetter, Novell chief technology officer.


Legacy NetworksLegacy Networks

There is an enormous installed base of NetWare networks. These legacy networks require support for:

– IPX/SPX– Multiple Ethernet Frame Types– Proprietary Novell routing protocols and

service advertisements.


The hero of our story...The hero of our story...

Cisco Systems continues to support legacy NetWare networks with a rich feature-set that can be added to any release of its IOS.


Cisco Routers in NetWareCisco Routers in NetWare

NetWare servers can route, but Cisco routers add flexibility, manageability and scalability to a NetWare network.


Novell’s Legacy Protocol SuiteNovell’s Legacy Protocol Suite


Key NetWare FeaturesKey NetWare Features


Novell IPX AddressingNovell IPX Addressing


A true story….A true story….


Multiple Novell EncapsulationsMultiple Novell Encapsulations

• Remember the defaults!


Ethernet Frame Type HistoryEthernet Frame Type History

• 1980 - Xerox, Intel and DEC release Ethernet Version I (no longer used)

• 1982 - Xerox, Intel and DEC release Ethernet Version II, aka – Ethernet v2– Ethernet II– DIX Ethernet



• 1982+ - Ethernet II becomes the de facto standard for framing TCP/IP.– TCP/IP is the Internet’s protocol.

– The Internet evolved from the DoD’s ARPANET. (Remember: TCP/IP -> Internet-> ARPA)

Preamble DA SA Type Data FCS64 bits 48 bits 48 bits 16 bits variable 32 bits

Ethernet II (used with TCP/IP networks)Ethernet II (used with TCP/IP networks)



Meanwhile…

• 1982 - IEEE’s 802 committee begins working on their own Ethernet standard, 802.3



The plot thickens...

• 1983 - Upstart Novell, newly incorporated, can’t wait for IEEE and releases a frame format based on the preliminary 802.3 specification.

Preamble DA SA Length Data FCS64 bits 48 bits 48 bits 16 bits variable 32 bits

Ethernet_802.3 (used in legacy Novell Netware)Ethernet_802.3 (used in legacy Novell Netware)



Novell’s frame format has no field for indicating what Layer 3 protocol should get the packet.

After all, IPX is the only Layer 3 protocol worth running, right?

Preamble DA SA Length Data FCS64 bits 48 bits 48 bits 16 bits variable 32 bits

Ethernet_802.3 (used in legacy Novell Netware)Ethernet_802.3 (used in legacy Novell Netware)



1985 - IEEE releases the 802.3 spec with the LLC fields (which use Service Access Points to point to layer 3 protocols), making Novell’s format incompatible.

Preamble DA SA Length DSAP SSAP64 bits 48 bits 48 bits 16 bits 8 bits8 bits

Data FCSvariable 32 bits

Ethernet_802.2 (an 802.3 frame with LLC)Ethernet_802.2 (an 802.3 frame with LLC)



Quick note:

There are two SAPs in this chapter, they are not the same:

LLC: Service Access Points

Novell: Service Advertisement Protocol



• Finally, Ethernet 802.3 SNAP was created because of compatibility issues between Ethernet II and 802.3.


Ethernet Frame Type RecapEthernet Frame Type Recap

• Ethernet II– aka DIX Ethernet, Ethernet v2, arpa

• Ethernet 802.3– aka 802.3 raw, Novell Proprietary, novell ether

• Ethernet 802.3/802.2– aka IEEE 802.3, Ethernet 802.2, sap

• Ethernet 802.3 SNAP– aka Ethernet SNAP, snap


Cisco Encapsulation NamesCisco Encapsulation Names

These Ethernet frame types and their IOS names are on the CCNA exam.


Default Frame TypeDefault Frame Type

Note: The default Ethernet encapsulation type on Cisco routers does not match the default Ethernet encapsulation type on Novell servers after NetWare 3.11.


Important!Important!

• Every frame type in use on your network must have it’s own logical network.logical network.

• Ethernet 802.3 and Ethernet II can live together on the same wire, but an 802.3 station can’t “talk” to a node that only uses Ethernet II.


Multiple Frame TypesMultiple Frame Types

If two frame types are in use on the same segment that a Cisco router lives on, that router’s interface will need two logical (network) addresses, one for each frame type.

How can e0 have two addresses?


SubinterfacesSubinterfaces

• Actually, one Cisco router interface can have over 4 billion logical addresses.

• This is done using the subinterface command.



In global configuration mode, invoke the serial interface using a decimal point followed by the subinterface you wish to create.

Router(config)#int s0.1

Router(config-subif)#



By using subinterfaces you put one physical interface on multiple logical networks:

e0.1 ip address 169.199.69.190 255.255.255.192

e0.2 ip address 169.199.69.254 255.255.255.192

e0.3 ip address 10.0.0.1 255.0.0.0



This allows a single interface to have multiple IPX addresses (and thus encapsulation types)

Ethernet0.1 is up, line protocol is up

IPX address is 4F.0000.0c04.8c8b, SAP [up] line-up


IPX address is 219A.0000.0c04.8c8b, NOVELL-ETHER [up] line-up


IPX address is 3B.0000.0c04.8c8b, ARPA [up] line-up


Novell Uses RIP for RoutingNovell Uses RIP for Routing

• Novell RIP is different than IP RIP.


IP RIP vs. Novell RIPIP RIP vs. Novell RIP

Novell RIP:

– has more than one metric (hop count & ticks)– can equal-cost load balance over multiple paths– sends updates every 60 seconds by default, not 30


Novell SAPNovell SAP

All servers and routers keep a complete list of the services available throughout the network in server information tables.


Novell SAPNovell SAP

• SAP updates– are broadcast– are sent by file servers, print servers, etc.– occur every 60 seconds (default)– are NOT forwarded by routers

To prevent excessive traffic across WAN links, routers build comprehensive SAP tables and send those instead of forward individual updates.


GNS Get Nearest ServerGNS Get Nearest Server

If there are no NetWare servers on the local network, the Cisco

router will respond with a server address from its own SAP table.


IPX Configuration TasksIPX Configuration Tasks


IPX Global Configuration TasksIPX Global Configuration Tasks


IPX Configuration ExampleIPX Configuration Example


Verifying IPX OperationVerifying IPX Operation


TroubleshootingTroubleshooting

chabot college cisco networking academy chabot college semester 3 novell ipx

Documents