1 a.dunfey 1.1 // ===================================================================
2 // Title: Network Systems
3 // $State: Preliminary $
4 // $Date: 2005/01/05 00:54:00 $
5 // $Source: /home/dmtf2/dotorg/var/cvs/repositories/dev/Schema/MOF/Network_Systems.mof,v $
6 // $Revision: 1.6 $
7 // ===================================================================
8 //#pragma inLine ("Includes/copyright.inc")
9 // Copyright 1998-2005 Distributed Management Task Force, Inc. (DMTF).
10 // All rights reserved.
11 // DMTF is a not-for-profit association of industry members dedicated
12 // to promoting enterprise and systems management and interoperability.
13 // DMTF specifications and documents may be reproduced for uses
14 // consistent with this purpose by members and non-members,
15 // provided that correct attribution is given.
16 // As DMTF specifications may be revised from time to time,
17 // the particular version and release date should always be noted.
18 //
19 // Implementation of certain elements of this standard or proposed
20 // standard may be subject to third party patent rights, including
21 // provisional patent rights (herein "patent rights"). DMTF makes
22 a.dunfey 1.1 // no representations to users of the standard as to the existence
23 // of such rights, and is not responsible to recognize, disclose, or
24 // identify any or all such third party patent right, owners or
25 // claimants, nor for any incomplete or inaccurate identification or
26 // disclosure of such rights, owners or claimants. DMTF shall have no
27 // liability to any party, in any manner or circumstance, under any
28 // legal theory whatsoever, for failure to recognize, disclose, or
29 // identify any such third party patent rights, or for such party's
30 // reliance on the standard or incorporation thereof in its product,
31 // protocols or testing procedures. DMTF shall have no liability to
32 // any party implementing such standard, whether such implementation
33 // is foreseeable or not, nor to any patent owner or claimant, and shall
34 // have no liability or responsibility for costs or losses incurred if
35 // a standard is withdrawn or modified after publication, and shall be
36 // indemnified and held harmless by any party implementing the
37 // standard from any and all claims of infringement by a patent owner
38 // for such implementations.
39 //
40 // For information about patents held by third-parties which have
41 // notified the DMTF that, in their opinion, such patent may relate to
42 // or impact implementations of DMTF standards, visit
43 a.dunfey 1.1 // http://www.dmtf.org/about/policies/disclosures.php.
44 //#pragma inLine
45 // ===================================================================
46 // Description: The Network Model extends the management concepts to
47 // represent protocol interfaces and network/protocol
48 // services. This file defines network "systems" such
49 // as ITU's M.3100 Network and autonomous systems.
50 //
51 // The object classes below are listed in an order that
52 // avoids forward references. Required objects, defined
53 // by other working groups, are omitted.
54 // ==================================================================
55 // Change Log for v2.9 Preliminary Company Review
56 // CR1465 - Corrected compile errors and warnings.
57 // System_FileServices.mof
58 // was moved to CIM_Schema.mof to resolve compile order issues.
59 //
60 // Change Log for v2.7
61 // CR696 - Add M.3100 concepts of Network and Pipe
62 // CR792 - Add the Composition qualifer to RoutersInAS
63 // CR982 - Removal of Experimental for preliminary to final
64 a.dunfey 1.1 // Change Log for v2.8
65 // CR1231 - Update references
66 // Property CIM_RoutersInAS.Role
67 // (CIM_BGPService.OtherRoleDescription)
68 // Property CIM_RoutersInAS.OtherRoleDescription
69 // (CIM_BGPService.Role)
70 //
71 // Change Log for V2.9
72 // CR1465 - Removed extra space
73 // Values { "Unknown", "None", "Aggregate Only ",
74 // "Aggregate And All Specific Routes",
75 // "Aggregate Based on Subset of Specific Routes" }]
76 // uint16 AggregationType;
77 //
78 // ===================================================================
79
80 #pragma Locale ("en_US")
81
82
83 // ==================================================================
84 // Network
85 a.dunfey 1.1 // ==================================================================
86 [Version ( "2.7.0" ), Description (
87 "Network is a subclass of AdminDomain that groups "
88 "interconnected networking and computing objects capable of "
89 "exchanging information. Instances of CIM_Network can represent "
90 "an enterprise's global network or specific connectivity "
91 "domains within the global network. These concepts are similar "
92 "to those defined for the Network object in ITU's M.3100 "
93 "specification."),
94 MappingStrings { "Recommendation.ITU|M3100.Network" }]
95 class CIM_Network : CIM_AdminDomain {
96 };
97
98
99 // ==================================================================
100 // AutonomousSystem
101 // ==================================================================
102 [Version ( "2.6.0" ), Description (
103 "An Autonomous System (AS) is a fundamental concept in "
104 "networking. An AS provides a structured view of routing by "
105 "segregating the system that is using routing (e.g., the "
106 a.dunfey 1.1 "Internet, or an extranet) into a set of separately "
107 "administered domains that each have their own independent "
108 "routing policies. These domains are called autonomous systems. "
109 "\n\n"
110 "The classic definition of an AS, from RFC1771, is '...a set of "
111 "routers under a single technical administration, using an "
112 "interior gateway protocol and common metrics to route packets "
113 "within the AS, and using an exterior gateway protocol to route "
114 "packets to other ASs'. The RFC continues: 'Since this classic "
115 "definition was developed, it has become common for a single AS "
116 "to use several interior gateway protocols and sometimes "
117 "several sets of metrics within an AS. The use of the term "
118 "Autonomous System here stresses the fact that, even when "
119 "multiple IGPs and metrics are used, the administration of an "
120 "AS appears to other ASs to have a single coherent interior "
121 "routing plan and presents a consistent picture of what "
122 "destinations are reachable through it.'")]
123 class CIM_AutonomousSystem : CIM_AdminDomain {
124
125 [Description (
126 "An ASNumber is an integer between 1 and 65535, with the "
127 a.dunfey 1.1 "range 64512 through 65535 reserved for private use. Every "
128 "AS has a unique AS number, which is assigned to it by an "
129 "Internet Registry or a provider. IANA assigns and "
130 "administers AS numbers.")]
131 uint16 ASNumber;
132
133 [Description (
134 "IsSingleHomed is a boolean that, when its value is TRUE, "
135 "indicates that this AS reaches networks outside of its "
136 "domain through a single exit point.")]
137 boolean IsSingleHomed;
138
139 [Description (
140 "IsTransit is a boolean that, when its value is TRUE, "
141 "indicates that this AS will advertise routes that it learns "
142 "from other ASs. A non-transit AS will only advertise its "
143 "own routes.")]
144 boolean IsTransit;
145
146 [Description (
147 "RequireIGPSync is a boolean that, when its value is TRUE, "
148 a.dunfey 1.1 "indicates that this AS must obey the following rule: a "
149 "router should not advertise destinations learned from "
150 "internal neighbors to external destinations unless those "
151 "destinations are also known via some internal gateway "
152 "protocol. Otherwise, a router may receive traffic that "
153 "cannot yet be routed. However, since this is a costly "
154 "choice, it is common practice to allow this rule to be "
155 "broken under certain carefully controlled circumstances.")]
156 boolean RequireIGPSync;
157
158 [Description (
159 "RoutingUpdateSource defines how routing information is to "
160 "be injected. Statically injected routes are maintained by "
161 "the routing table and are independent of the status of the "
162 "networks to which they refer. This is done simply by "
163 "defining static routes in the routing table. Dynamically "
164 "injected routes are of two types. Dynamic routes refer to "
165 "distributing all of the IGP routes. Semi-dynamic routes "
166 "define a set of specific IGP routes that will be injected."),
167 ValueMap { "0", "1", "2", "3" },
168 Values { "Unknown", "Static", "Dynamic", "Semi-Dynamic" }]
169 a.dunfey 1.1 uint16 RoutingUpdateSource;
170
171 [Description (
172 "Route aggregation refers to summarizing ranges of routes "
173 "into one or more aggregate routes. This is done to minimize "
174 "the number of routes in the global routing table. A "
175 "potential drawback is that specific path information (e.g., "
176 "the Path attribute value) is lost, which may lead to "
177 "potential routing loops. There are a variety of ways to "
178 "ensure that this does not happen. Note that BGP4 is "
179 "required to do this. \n"
180 "\n"
181 "There are many ways to form aggregate routes. The following "
182 "are the most popular: 'Aggregate only', where only the "
183 "aggregate is advertised, and all of its more specific "
184 "routes are suppressed; 'Aggregate Plus Specific Routes', "
185 "where both the aggregate as well as its more specific "
186 "routes are advertised (e.g., send the aggregate to the NAP, "
187 "but send the more specific routes to providers); 'Aggregate "
188 "Based on a Subset of Specific Routes', where the aggregate "
189 "route is formed by looking at certain more specific routes "
190 a.dunfey 1.1 "and forming an aggregate on them, suppressing all others."),
191 ValueMap { "0", "1", "2", "3", "4" },
192 Values { "Unknown", "None", "Aggregate Only",
193 "Aggregate And All Specific Routes",
194 "Aggregate Based on Subset of Specific Routes" }]
195 uint16 AggregationType;
196 };
197
198 // ==================================================================
199 // RoutersInAS
200 // ==================================================================
201 [Association, Aggregation, Composition, Version ( "2.7.0" ),
202 Description (
203 "This aggregation establishes 'whole-part' relationships "
204 "between an AutonomousSystem and the routers that it contains. "
205 "In addition, the routers in the AS share common configuration "
206 "information, and are commonly administered.")]
207 class CIM_RoutersInAS : CIM_SystemComponent {
208
209 [Aggregate, Override ( "GroupComponent" ), Max ( 1 ),
210 Description (
211 a.dunfey 1.1 "The AutonomousSystem that aggregates the routers belonging "
212 "to it and administers them.")]
213 CIM_AutonomousSystem REF GroupComponent;
214
215 [Override ( "PartComponent" ), Description (
216 "The Routers that are contained in the AS.")]
217 CIM_ComputerSystem REF PartComponent;
218
219 [Description (
220 "This is an array of strings that contain the BGP attributes "
221 "supported by this router.")]
222 string BGPSupportedAttributes[];
223
224 [Description (
225 "TRUE means that the community value of this router is added "
226 "to the existing community value, and FALSE means that the "
227 "community value of this router replaces the existing "
228 "community value.")]
229 boolean AddCommunityValue;
230
231 [Description (
232 a.dunfey 1.1 "This is an enumeration that defines the function, from the "
233 "point of view of BGP, of this router."),
234 ValueMap { "0", "1", "2", "3", "4", "5", "6", "7" },
235 Values { "Unknown", "Other", "Conventional BGP Speaker",
236 "Route Reflector", "Router Reflector Client",
237 "Route Reflector Non-Client", "Peer Group Member",
238 "Confederation Member" }]
239 uint16 Role;
240
241 [Description (
242 "A string describing the type of function that this router "
243 "has in its AS when the value of the Role property of this "
244 "class is set to 1 (i.e., \"Other\"). The format of the "
245 "string inserted in this property should be similar in "
246 "format to the values defined for the Role property. This "
247 "property should be set to NULL when the Role property is "
248 "any value other than 1."),
249 MaxLen ( 64 )]
250 string OtherRoleDescription;
251 };
252
253 a.dunfey 1.1
254 // ===================================================================
255 // end of file
256 // ===================================================================
|
Return to
Network_Systems.mof
CVS log
Up to [Pegasus] / pegasus / Schemas / CIMPrelim291