Cisco InfiniBand 4x User's Guide Page 135
- Page / 174
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
Chapter 7. Configuring the Cisco 3012 InfiniBand to Ethernet gateway 121
7.1.2 Some general items to consider
Some general topics that are important to those working with this product include:
Use of the GUI or CLI interface
Either the GUI or the CLI or both can be used to configure the gateway module. In
general, the GUI (either the Element Manager or the built-in http support) is good for
one-off configurations or for use by those that are not familiar with the CLI. The CLI is
usually used by those deploying (scripting) a number of installs, and that are more
comfortable with the greater flexibility (and thus increased complexity) that it offers.
For those that are unfamiliar with the CLI but want to know more about how it operates,
one of the best ways to become familiar with the CLI is to use the GUI to configure a
desired option, and then go in to the CLI of the 3012 and do a show config to see what
changes were made by the GUI.
On that note, it should be kept in mind that making changes through the GUI will result in
those changes becoming part of the CLI configuration. The reverse also applies: making
changes in the CLI are reflected in what is displayed in the GUI.
In both cases, changes made take effect immediately (with CLI, when you press Enter on
a command, and with GUI, when you click OK or the option to Apply).
Any changes made are only stored in the running configuration. You should also save
configuration changes to NVRAM to make them safe in case of a reload or power cycle.
With CLI, saving the configuration is done with the command copy running startup. With
the Element Manager GUI, this is done by clicking Maintenance → Save Config.
What is a trunk?
The term
trunk is used differently by different groups. In most Cisco products (other than
the SFS products) a trunk is an IEEE 802.1Q term for a connection that carries multiple
VLANs.
For the SFS platform (and some other companies) a trunk is created by bundling multiple
physical Ethernet ports into a larger logical port, for increased performance and high
availability. Most other Cisco products refer to this bundling as either aggregation or
EtherChannel.
When referenced in this section, trunk will represent the SFS version of this term
(aggregation/EtherChannel).
What are VLANs?
VLANs are
Virtual LANs. In most cases, each VLAN represents a separate and distinct IP
subnet. VLANs offer a way in the Ethernet world to isolate traffic flows within a switch and
on a shared wire, which helps to reduce the size of broadcast domains. It can also add
some security, in that traffic in one VLAN will not be seen on a different VLAN, unless it
can be carried over an L3 (router) device.
When carrying VLANs between Ethernet switches, some sort of method needs to be used
to let each side of the connection know what VLAN a given packet is to be placed in upon
arrival. This is done by inserting a tag in the header, that among other things, carries a
field defining the VLAN it is part of. The most common protocol used for this tagging is
IEEE 802.1Q, which is the tagging protocol supported by the 3012 gateway.
Whether or not to use VLANs depends on your own network requirements. In general,
using a single VLAN (no tagging) is simplest to configure. Multiple VLANs should be used
when you’re network requires this functionality.
- Redpaper 1
- October 2007 3
- Contract with IBM Corp 4
- Contents 5
- Contents v 7
- Trademarks 10
- Become a published author 13
- Comments welcome 13
- IBM BladeCenter products and 15
- 1.1 BladeCenter chassis 16
- 1.2 Blade servers 19
- 4X InfiniBand networking only 27
- InfiniBand products for 29
- BladeCenter 29
- OK (Green) and Fault (Yellow) 38
- 2.6.2 InfiniBand DDR HCAs 39
- InfiniBand technology 45
- 3.1.1 Upper layer protocols 46
- 3.1.2 Transport layer 46
- 3.1.3 Network layer 47
- 3.1.4 Data link layer 47
- 3.1.5 Physical layer 48
- 12X Link 49
- 3.2.3 Storage RDMA Protocol 50
- 3.3 Hardware 52
- 3.4 Management 52
- 3.5 Common markets 53
- 3.5.1 Application clustering 54
- 3.5.3 Storage area networks 54
- Configuring InfiniBand with 55
- QLogic bridges 55
- 4.1.1 Installing the drivers 56
- 4.1.5 Hints and tips 74
- Figure 4-66 Active SRP Map 89
- Figure 4-67 Add Direct Map 90
- Figure 4-70 93
- 5.2.3 Configuring IPoIB 105
- Cisco 3012 InfiniBand to FC 109
- 6.2 Blade booting from a SAN 110
- Installing hardware 111
- Figure 6-6 Define SRP host 114
- 6.2.5 Configuring storage 118
- 6.2.6 Discovering storage 119
- 6.2.8 Port masking 120
- Loading SCSI driver 128
- Loading ts_srp_host driver 128
- Configuring the Cisco 3012 131
- 7.2 Client information 136
- 7.3.1 The design 137
- EGW = Ethernet Gateway Module 147
- BG1 = Bridge Group 1 147
- Blue = InfiniBand 147
- Green = Ethernet 147
- Int Po5 153
- Figure 7-25 164
- 7.7 Useful CLI commands 169
- 7.7.2 For the 4948 170
- Abbreviations and acronyms 171
- Related publications 173
- Online resources 174
- Help from IBM 174
Related products and manuals for Network switches Cisco InfiniBand 4x
Network switches Cisco MFEBX1 User Manual
(11 pages)
(11 pages)
Network switches Cisco TrustSec User Manual
(10 pages)
(10 pages)
Network switches Cisco MGBLX1 User Manual
(13 pages)
(13 pages)
© 2020, manymanuals.com. All rights reserved. | 0.403 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals