1 a.dunfey 1.1 // ===================================================================
2 // Title: Network_Systems
3 // $State: Exp $
4 // $Date: 2004/12/16 05:21:02 $
5 // $RCSfile: Network_Systems.mof,v $
6 // $Revision: 1.5.2.4 $
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.7
56 // CR696 - Add M.3100 concepts of Network and Pipe
57 // CR792 - Add the Composition qualifer to RoutersInAS
58 // CR982 - Removal of Experimental for preliminary to final
59 // Change Log for v2.8
60 // CR1231 - Update references
61 // Property CIM_RoutersInAS.Role
62 // (CIM_BGPService.OtherRoleDescription)
63 // Property CIM_RoutersInAS.OtherRoleDescription
64 a.dunfey 1.1 // (CIM_BGPService.Role)
65 // Change Log for V2.9
66 // CR1465 - Removed extra space
67 // Values { "Unknown", "None", "Aggregate Only ",
68 // "Aggregate And All Specific Routes",
69 // "Aggregate Based on Subset of Specific Routes" }]
70 // uint16 AggregationType;
71 // ===================================================================
72
73 #pragma Locale ("en_US")
74
75
76 // ==================================================================
77 // Network
78 // ==================================================================
79 [Version ( "2.7.0" ), Description (
80 "Network is a subclass of AdminDomain that groups "
81 "interconnected networking and computing objects capable of "
82 "exchanging information. Instances of CIM_Network can represent "
83 "an enterprise's global network or specific connectivity "
84 "domains within the global network. These concepts are similar "
85 a.dunfey 1.1 "to those defined for the Network object in ITU's M.3100 "
86 "specification."),
87 MappingStrings { "Recommendation.ITU|M3100.Network" }]
88 class CIM_Network : CIM_AdminDomain {
89 };
90
91
92 // ==================================================================
93 // AutonomousSystem
94 // ==================================================================
95 [Version ( "2.6.0" ), Description (
96 "An Autonomous System (AS) is a fundamental concept in "
97 "networking. An AS provides a structured view of routing by "
98 "segregating the system that is using routing (e.g., the "
99 "Internet, or an extranet) into a set of separately "
100 "administered domains that each have their own independent "
101 "routing policies. These domains are called autonomous systems. "
102 "\n\n"
103 "The classic definition of an AS, from RFC1771, is '...a set of "
104 "routers under a single technical administration, using an "
105 "interior gateway protocol and common metrics to route packets "
106 a.dunfey 1.1 "within the AS, and using an exterior gateway protocol to route "
107 "packets to other ASs'. The RFC continues: 'Since this classic "
108 "definition was developed, it has become common for a single AS "
109 "to use several interior gateway protocols and sometimes "
110 "several sets of metrics within an AS. The use of the term "
111 "Autonomous System here stresses the fact that, even when "
112 "multiple IGPs and metrics are used, the administration of an "
113 "AS appears to other ASs to have a single coherent interior "
114 "routing plan and presents a consistent picture of what "
115 "destinations are reachable through it.'")]
116 class CIM_AutonomousSystem : CIM_AdminDomain {
117
118 [Description (
119 "An ASNumber is an integer between 1 and 65535, with the "
120 "range 64512 through 65535 reserved for private use. Every "
121 "AS has a unique AS number, which is assigned to it by an "
122 "Internet Registry or a provider. IANA assigns and "
123 "administers AS numbers.")]
124 uint16 ASNumber;
125
126 [Description (
127 a.dunfey 1.1 "IsSingleHomed is a boolean that, when its value is TRUE, "
128 "indicates that this AS reaches networks outside of its "
129 "domain through a single exit point.")]
130 boolean IsSingleHomed;
131
132 [Description (
133 "IsTransit is a boolean that, when its value is TRUE, "
134 "indicates that this AS will advertise routes that it learns "
135 "from other ASs. A non-transit AS will only advertise its "
136 "own routes.")]
137 boolean IsTransit;
138
139 [Description (
140 "RequireIGPSync is a boolean that, when its value is TRUE, "
141 "indicates that this AS must obey the following rule: a "
142 "router should not advertise destinations learned from "
143 "internal neighbors to external destinations unless those "
144 "destinations are also known via some internal gateway "
145 "protocol. Otherwise, a router may receive traffic that "
146 "cannot yet be routed. However, since this is a costly "
147 "choice, it is common practice to allow this rule to be "
148 a.dunfey 1.1 "broken under certain carefully controlled circumstances.")]
149 boolean RequireIGPSync;
150
151 [Description (
152 "RoutingUpdateSource defines how routing information is to "
153 "be injected. Statically injected routes are maintained by "
154 "the routing table and are independent of the status of the "
155 "networks to which they refer. This is done simply by "
156 "defining static routes in the routing table. Dynamically "
157 "injected routes are of two types. Dynamic routes refer to "
158 "distributing all of the IGP routes. Semi-dynamic routes "
159 "define a set of specific IGP routes that will be injected."),
160 ValueMap { "0", "1", "2", "3" },
161 Values { "Unknown", "Static", "Dynamic", "Semi-Dynamic" }]
162 uint16 RoutingUpdateSource;
163
164 [Description (
165 "Route aggregation refers to summarizing ranges of routes "
166 "into one or more aggregate routes. This is done to minimize "
167 "the number of routes in the global routing table. A "
168 "potential drawback is that specific path information (e.g., "
169 a.dunfey 1.1 "the Path attribute value) is lost, which may lead to "
170 "potential routing loops. There are a variety of ways to "
171 "ensure that this does not happen. Note that BGP4 is "
172 "required to do this. \n"
173 "\n"
174 "There are many ways to form aggregate routes. The following "
175 "are the most popular: 'Aggregate only', where only the "
176 "aggregate is advertised, and all of its more specific "
177 "routes are suppressed; 'Aggregate Plus Specific Routes', "
178 "where both the aggregate as well as its more specific "
179 "routes are advertised (e.g., send the aggregate to the NAP, "
180 "but send the more specific routes to providers); 'Aggregate "
181 "Based on a Subset of Specific Routes', where the aggregate "
182 "route is formed by looking at certain more specific routes "
183 "and forming an aggregate on them, suppressing all others."),
184 ValueMap { "0", "1", "2", "3", "4" },
185 Values { "Unknown", "None", "Aggregate Only ",
186 "Aggregate And All Specific Routes",
187 "Aggregate Based on Subset of Specific Routes" }]
188 uint16 AggregationType;
189 };
190 a.dunfey 1.1
191 // ==================================================================
192 // RoutersInAS
193 // ==================================================================
194 [Association, Aggregation, Composition, Version ( "2.7.0" ),
195 Description (
196 "This aggregation establishes 'whole-part' relationships "
197 "between an AutonomousSystem and the routers that it contains. "
198 "In addition, the routers in the AS share common configuration "
199 "information, and are commonly administered.")]
200 class CIM_RoutersInAS : CIM_SystemComponent {
201
202 [Aggregate, Override ( "GroupComponent" ), Max ( 1 ),
203 Description (
204 "The AutonomousSystem that aggregates the routers belonging "
205 "to it and administers them.")]
206 CIM_AutonomousSystem REF GroupComponent;
207
208 [Override ( "PartComponent" ), Description (
209 "The Routers that are contained in the AS.")]
210 CIM_ComputerSystem REF PartComponent;
211 a.dunfey 1.1
212 [Description (
213 "This is an array of strings that contain the BGP attributes "
214 "supported by this router.")]
215 string BGPSupportedAttributes[];
216
217 [Description (
218 "TRUE means that the community value of this router is added "
219 "to the existing community value, and FALSE means that the "
220 "community value of this router replaces the existing "
221 "community value.")]
222 boolean AddCommunityValue;
223
224 [Description (
225 "This is an enumeration that defines the function, from the "
226 "point of view of BGP, of this router."),
227 ValueMap { "0", "1", "2", "3", "4", "5", "6", "7" },
228 Values { "Unknown", "Other", "Conventional BGP Speaker",
229 "Route Reflector", "Router Reflector Client",
230 "Route Reflector Non-Client", "Peer Group Member",
231 "Confederation Member" }]
232 a.dunfey 1.1 uint16 Role;
233
234 [Description (
235 "A string describing the type of function that this router "
236 "has in its AS when the value of the Role property of this "
237 "class is set to 1 (i.e., \"Other\"). The format of the "
238 "string inserted in this property should be similar in "
239 "format to the values defined for the Role property. This "
240 "property should be set to NULL when the Role property is "
241 "any value other than 1."),
242 MaxLen ( 64 )]
243 string OtherRoleDescription;
244 };
245
246
247 // ===================================================================
248 // end of file
249 // ===================================================================
|
Return to
Network_Systems.mof
CVS log
Up to [Pegasus] / pegasus / Schemas / CIM29