IBM 8654 Hardware Maintenance Manual - Page 77

IBM Netfinity 10/100 Ethernet Security Adapters and IBM 10/100 Ethernet

Get IBM 8654 - Eserver xSeries 330 PDF manuals and user guides
UPC - 087944618102
View all IBM 8654 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 77 highlights

Note: IEEE 802.1p tagging increases the size of the packets it tags. Some hubs and switches will not recognize the larger packets and will drop them. Check your hub or switch documentation to see if they support 802.1p. (You can configure the switch to strip the tags from the packets and send it on to the next destination as normal traffic.) If these devices do not support 802.1p or if you are not sure, use High Priority Queue (HPQ) to prioritize network traffic. The requirements for effectively using IEEE 802.1p tagging are: • The other devices receiving and routing 802.1p tagged packets must support 802.1p. • The adapters on these devices must support 802.1p. The Ethernet controller in all IBM Netfinity 10/100 Ethernet Security Adapters and IBM 10/100 Ethernet Server Adapters support 802.1p. • The adapter cannot be assigned to an adapter team. • If you are setting up VLANs and packet tagging on the same adapter, 802.1p/802.1Q Tagging must be enabled on the IBMSet Advanced tab. If your network infrastructure devices do not support IEEE 802.1p or you are not sure, you can still define filters and send packets as high priority. While High Priority Queue (HPQ) does not provide the precise priority levels of 802.1p tagging, it does assign traffic as either high or low priority and sends high priority packets first. Therefore, if there are multiple applications on a system sending packets, the packets from the application with a filter are sent out first. HPQ does not change network routing, nor does it add any information to the packets. To assign HPQ, you can specify it using Priority Packet when you create or assign a filter. To effectively use HPQ tagging, the adapter cannot be assigned to an adapter team. Virtual LAN Mode: A virtual LAN (VLAN) is a logical grouping of network devices put together as a LAN, regardless of their physical grouping or collision domains. Using VLANs increases network performance and improves network security. VLANs offer you the ability to group users and devices together into logical workgroups. This can simplify network administration when connecting clients to servers that are geographically dispersed across the building, campus, or enterprise network. Normally, VLANs are configured at the switch and any computer can be a member of one VLAN per installed network adapter. Your Ethernet controller supersedes this by communicating directly with the switch, allowing multiple VLANs on a single network adapter (up to 64 VLANs). To set up VLAN membership, your Ethernet controller must be attached to a switch that has VLAN capability. You also need to use Windows NT 4.0 or later, or Novell NetWare 4.1x or later. Notes: 1. Windows NT versions prior to 4.0 do not support VLANs. 2. VLANs require NT 4.0 with Service Pack 3.0 and the NDIS driver hotfix from Microsoft. 3. In Windows NT, VLANs cannot be implemented on controllers that have been configured for teaming options. NetWare can support teaming options and VLANs on the same adapters. To join a VLAN from Windows NT 4.0: Chapter 5. Installing options 69

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
Chapter 5.
Installing options
69
Note:
IEEE 802.1p tagging increases the size of the packets it tags.
Some hubs and
switches will not recognize the larger packets and will drop them.
Check your
hub or switch documentation to see if they support 802.1p.
(You can configure
the switch to strip the tags from the packets and send it on to the next
destination as normal traffic.)
If these devices do not support 802.1p or if you
are not sure, use High Priority Queue (HPQ) to prioritize network traffic.
The requirements for effectively using IEEE 802.1p tagging are:
•
The other devices receiving and routing 802.1p tagged packets must support
802.1p.
•
The adapters on these devices must support 802.1p.
The Ethernet controller in all
IBM Netfinity 10/100 Ethernet Security Adapters and IBM 10/100 Ethernet
Server Adapters support 802.1p.
•
The adapter cannot be assigned to an adapter team.
•
If you are setting up VLANs and packet tagging on the same adapter,
802.1p/802.1Q Tagging must be enabled on the IBMSet Advanced tab.
If your network infrastructure devices do not support IEEE 802.1p or you are not sure,
you can still define filters and send packets as high priority.
While High Priority
Queue (HPQ) does not provide the precise priority levels of 802.1p tagging, it does
assign traffic as either high or low priority and sends high priority packets first.
Therefore, if there are multiple applications on a system sending packets, the packets
from the application with a filter are sent out first.
HPQ does not change network
routing, nor does it add any information to the packets.
To assign HPQ, you can specify it using Priority Packet when you create or assign a
filter.
To effectively use HPQ tagging, the adapter cannot be assigned to an adapter team.
Virtual LAN
Mode:
A virtual LAN (VLAN) is a logical grouping of network devices
put together as a LAN, regardless of their physical grouping or collision domains.
Using VLANs increases network performance and improves network security.
VLANs offer you the ability to group users and devices together into logical
workgroups.
This can simplify network administration when connecting clients to
servers that are geographically dispersed across the building, campus, or enterprise
network.
Normally, VLANs are configured at the switch and any computer can be a member of
one VLAN per installed network adapter.
Your Ethernet controller supersedes this by
communicating directly with the switch, allowing multiple VLANs on a single
network adapter (up to 64 VLANs).
To set up VLAN membership, your Ethernet controller must be attached to a switch
that has VLAN capability.
You also need to use Windows NT 4.0 or later, or Novell
NetWare 4.1x or later.
Notes:
1.
Windows NT versions prior to 4.0 do not support VLANs.
2.
VLANs require NT 4.0 with Service Pack 3.0 and the NDIS driver hotfix from
Microsoft.
3.
In Windows NT, VLANs cannot be implemented on controllers that have been
configured for teaming options.
NetWare can support teaming options and
VLANs on the same adapters.
To join a VLAN from Windows NT 4.0: