|
|
United States-English | |
|
|
 |
|
HP 9000 Networking: Installing and Administering OSI Transport Services > Chapter 2 Planning Your Network
Determine the Network Structure |
|
|
At this point, you have identified the nodes and the services you will be using for your network. The next step is to draw a network map to visualize the structure of your network. If this is an addition to an existing network, update the existing network map, otherwise, follow these steps to draw your map. A simple example of a network map is shown below.
At this point, you have determined the layout of your network. Now develop an addressing scheme that facilitates routing in your existing network, as well as future expansion. Most network address formats allow you to segment your network into routing domains and areas. Examine your network map and consider:
After you have done the partition into domains and areas, you can then assign an appropriate network address prefix for each node, and the full address can be completed by using each node's End System address. You may also want to dictate the selector values to be used for the upper layer addresses. (Note that HP OSI services use default addresses. For instance, FTAM uses 0x0001 (hex) for P-, S-, and T- selectors. X.400 uses blank (null) P- and S- selectors and 4D4853 (hex) as the T-selector. Refer to the appropriate product manuals to see what, if any, default addresses are used.) If you wish to change the default addresses, you might assign all FTAM responders to have the P-, S- and T-selectors of 0x0010. For an XTI application you are developing, you may want all initiators to use T-selectors 0x0020 and all responders to use T-selectors of 0x0021. You have a wide array of addresses to choose from. The selectors may fall in the following range: P-selector: 0 to 16 bytes S-selector: 0 to 16 bytes T-selector: 0 to 32 bytes Remember that the longer or more complicated you make your selector values, the more room you leave for error during configuration.
If you are using FTAM or X.500, you will use Directory Distinguished Names (DDNs) in some capacity. These are hierarchical names, for example, "/C=us/O=hp/OU=hpnode1/AP=mms/AE=demo_prog". At this time, you should define what components of the naming hierarchy you plan to use and define conventions for assigning values to each component. As an example, you might decide that the Country attribute will not be used, the Organization attribute will always be your company's name in all lower case, and the Organization Unit will correspond to the node name given on the network map in all lower case. See the discussion of naming in the configuration manuals for the respective services for more information about what attribute classes are available and which ones are required. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 Printable version |
|
|
|
|
|
|||||||||||||||
|
|||||||||||||||
