1. CHABOT COLLEGE CISCO NETWORKING ACADEMY Chabot College Semester 3 Novell IPX

2. CHABOT COLLEGE CISCO NETWORKING ACADEMY NetWare Networks (NOS) In the early 1980’s, Novell developed a network operating system (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

3. CHABOT COLLEGE CISCO NETWORKING ACADEMY Major 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.

4. CHABOT COLLEGE CISCO NETWORKING ACADEMY Decline of Novell Microsoft NT With the rapid emergence of another NOS, Microsoft 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

5. CHABOT COLLEGE CISCO NETWORKING ACADEMY Novell Today “IPX and NLMs are dead” -- 9/00, Carl Ledbetter, Novell chief technology officer.

6. CHABOT COLLEGE CISCO NETWORKING ACADEMY Legacy 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.

7. CHABOT COLLEGE CISCO NETWORKING ACADEMY 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.

8. CHABOT COLLEGE CISCO NETWORKING ACADEMY Cisco Routers in NetWare NetWare servers can route, but Cisco routers add flexibility, manageability and scalability to a NetWare network.

9. CHABOT COLLEGE CISCO NETWORKING ACADEMY Novell’s Legacy Protocol Suite

10. CHABOT COLLEGE CISCO NETWORKING ACADEMY Key NetWare Features

11. CHABOT COLLEGE CISCO NETWORKING ACADEMY Novell IPX Addressing

12. CHABOT COLLEGE CISCO NETWORKING ACADEMY Novell IPX Addressing

13. CHABOT COLLEGE CISCO NETWORKING ACADEMY A true story….

14. CHABOT COLLEGE CISCO NETWORKING ACADEMY Multiple Novell Encapsulations Remember the defaults!

15. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet 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

16. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet Frame Type History 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) PreambleDASATypeDataFCS 64 bits48 bits 16 bitsvariable 32 bits Ethernet II (used with TCP/IP networks)

17. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet Frame Type History Meanwhile… 1982 - IEEE’s 802 committee begins working on their own Ethernet standard, 802.3

18. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet Frame Type History 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. PreambleDASALengthDataFCS 64 bits48 bits 16 bitsvariable 32 bits Ethernet_802.3 (used in legacy Novell Netware)

19. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet Frame Type History 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? PreambleDASALengthDataFCS 64 bits48 bits 16 bitsvariable 32 bits Ethernet_802.3 (used in legacy Novell Netware)

20. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet Frame Type History 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. PreambleDASALengthDSAPSSAP 64 bits48 bits 16 bits 8 bits DataFCS variable 32 bits Ethernet_802.2 (an 802.3 frame with LLC)

21. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet Frame Type History Quick note: There are two SAPs in this chapter, they are not the same: LLC: Service Access Points Novell: Service Advertisement Protocol

22. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet Frame Type History Finally, Ethernet 802.3 SNAP was created because of compatibility issues between Ethernet II and 802.3.

23. CHABOT COLLEGE CISCO NETWORKING ACADEMY Ethernet 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

24. CHABOT COLLEGE CISCO NETWORKING ACADEMY Cisco Encapsulation Names These Ethernet frame types and their IOS names are on the CCNA exam.

25. CHABOT COLLEGE CISCO NETWORKING ACADEMY Default 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.

26. CHABOT COLLEGE CISCO NETWORKING ACADEMY Important! logical network.Every frame type in use on your network must have it’s own 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.

27. CHABOT COLLEGE CISCO NETWORKING ACADEMY Multiple 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?

28. CHABOT COLLEGE CISCO NETWORKING ACADEMY Subinterfaces Actually, one Cisco router interface can have over 4 billion logical addresses. This is done using the subinterface command.

29. CHABOT COLLEGE CISCO NETWORKING ACADEMY Subinterfaces 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)#

30. CHABOT COLLEGE CISCO NETWORKING ACADEMY Subinterfaces 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

31. CHABOT COLLEGE CISCO NETWORKING ACADEMY Subinterfaces 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 Ethernet0.2 is up, line protocol is up IPX address is 219A.0000.0c04.8c8b, NOVELL-ETHER [up] line-up Ethernet0.3 is up, line protocol is up IPX address is 3B.0000.0c04.8c8b, ARPA [up] line-up

32. CHABOT COLLEGE CISCO NETWORKING ACADEMY Subinterfaces

33. Novell Uses RIP for Routing Novell RIP is different than IP RIP.

34. CHABOT COLLEGE CISCO NETWORKING ACADEMY IP 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

35. CHABOT COLLEGE CISCO NETWORKING ACADEMY Novell SAP All servers and routers keep a complete list of the services available throughout the network in server information tables.

36. CHABOT COLLEGE CISCO NETWORKING ACADEMY Novell 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.

37. CHABOT COLLEGE CISCO NETWORKING ACADEMY GNS 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.

38. CHABOT COLLEGE CISCO NETWORKING ACADEMY IPX Configuration Tasks

39. CHABOT COLLEGE CISCO NETWORKING ACADEMY IPX Global Configuration Tasks

40. CHABOT COLLEGE CISCO NETWORKING ACADEMY IPX Configuration Example

41. CHABOT COLLEGE CISCO NETWORKING ACADEMY Verifying IPX Operation

42. CHABOT COLLEGE CISCO NETWORKING ACADEMY Troubleshooting

43. Troubleshooting

44. Troubleshooting

45. Troubleshooting

46. Troubleshooting

47. Troubleshooting