Systems Network Architecture - Revision history

Jnc: Jnc moved page SNA to Systems Network Architecture: Use full name

2018-10-21T13:31:28Z

Jnc moved page SNA to Systems Network Architecture: Use full name

Jnc: Proper cat, fix error

2018-10-21T13:30:24Z

Proper cat, fix error

Neozeed at 14:07, 29 October 2009

2009-10-29T14:07:23Z

Neozeed: New page: SNA is the protocol that is used by IBM midrange AS/400's and mainframe 370/390's to communicate over a 'lan' to FEP's and other networked devices. A common machine found ...

2009-07-12T13:44:54Z

New page: SNA is the protocol that is used by IBM midrange AS/400's and mainframe 370/390's to communicate over a 'lan' to FEP's and other networked devices. A common machine found ...

New page

SNA is the protocol that is used by IBM midrange [[AS/400]]'s and mainframe [[370]]/[[390]]'s to communicate over a 'lan' to [[FEP]]'s and other networked devices. A common machine found on SNA networks is Microsoft's SNA server which allows users to use a Windows client protocols to communicate to the mainframe/midrange.

One of the 'annoying' things about SNA is that every 2 seconds the host will send a ACK request, and if it is not responded to quickly enough all the sessions associated with that endpoint will be dropped. The SNA protocol was designed with local TokenRing in mind. However cisco routers do incorporate a 'local ack' feature to cheat the ack's and allow SNA to operate over a wan.

There is some work involved when connected to a Token Ring network from an Ethernet as the destination MAC addresses all have to be flipped from big endian to little endian.

{{stub}}
[[Category:Network Protocols]]

@@ Line 1: / Line 1: @@
-SNA is the protocol that is used by IBM midrange [[AS/400]]'s and mainframe [[System/370|370]]/[[System/390|390]]'s to communicate over a 'lan' to [[FEP]]'s and other networked devices.  A common machine found on SNA networks is Microsoft's SNA server which allows users to use a Windows client protocols to communicate to the mainframe/midrange.
+'''Systems Network Architecture''' ('''SNA''' for short), originally designed in 1974, is the [[protocol]] used by [[International Business Machines|IBM]]'s [[mainframe]] computers to communicate; originally master-slave, it was updated for [[peer-peer]] use.
-One of the 'annoying' things about SNA is that every 2 seconds the host will send a ACK request, and if it is not responded to quickly enough all the sessions associated with that endpoint will be dropped.  The SNA protocol was designed with local TokenRing in mind.  However cisco routers do incorporate a 'local ack' feature to cheat the ack's and allow SNA to operate over a wan.
+It is used by IBM midrange [[AS/400]]'s and mainframe [[IBM System/370|370]]/[[IBM System/390|390]]'s to communicate over a [[LAN]] to [[FEP]]'s and other networked devices. A common machine found on SNA networks is Microsoft's SNA server which allows users to use a Windows client protocols to communicate to the mainframe/midrange.
-There is some work involved when connected to a Token Ring network from an Ethernet as the destination MAC addresses all have to be flipped from big endian to little endian.
+One of the 'annoying' things about SNA is that every 2 seconds the host will send a [[ACK]] request, and if it is not responded to quickly enough all the sessions associated with that endpoint will be dropped.  The SNA protocol was designed with local Token Ring in mind. However cisco routers do incorporate a 'local ack' feature to cheat the ack's and allow SNA to operate over a [[WAN]].
-{{stub}}
+[[Category: Network Protocols]]

← Older revision		Revision as of 14:07, 29 October 2009
Line 1:		Line 1:
−	SNA is the protocol that is used by IBM midrange [[AS/400]]'s and mainframe [[370]]/[[390]]'s to communicate over a 'lan' to [[FEP]]'s and other networked devices. A common machine found on SNA networks is Microsoft's SNA server which allows users to use a Windows client protocols to communicate to the mainframe/midrange.	+	SNA is the protocol that is used by IBM midrange [[AS/400]]'s and mainframe [[System/370\|370]]/[[System/390\|390]]'s to communicate over a 'lan' to [[FEP]]'s and other networked devices. A common machine found on SNA networks is Microsoft's SNA server which allows users to use a Windows client protocols to communicate to the mainframe/midrange.

	One of the 'annoying' things about SNA is that every 2 seconds the host will send a ACK request, and if it is not responded to quickly enough all the sessions associated with that endpoint will be dropped. The SNA protocol was designed with local TokenRing in mind. However cisco routers do incorporate a 'local ack' feature to cheat the ack's and allow SNA to operate over a wan.		One of the 'annoying' things about SNA is that every 2 seconds the host will send a ACK request, and if it is not responded to quickly enough all the sessions associated with that endpoint will be dropped. The SNA protocol was designed with local TokenRing in mind. However cisco routers do incorporate a 'local ack' feature to cheat the ack's and allow SNA to operate over a wan.

← Older revision	Revision as of 13:31, 21 October 2018
(No difference)