1
© 2000, Cisco Systems, Inc.
Managing Networks,
Managing Networks,
Users & Applications in
Users & Applications in
the New Millennium
the New Millennium
John Thomas
John Thomas
johnthom
johnthom
@cisco.com
@cisco.com
2
© 2000, Cisco Systems, Inc.
Agenda
Agenda
• What is Network Management?
• Current Architecture(s)
• Two New Architectures
• Examples
• Concluding Remarks
3
© 2000, Cisco Systems, Inc.
Network Management’s
Network Management’s
Primary Role
Primary Role
• Validate user experience
connectivity, response times

• Anticipate network change
failures, growth, user mobility, new apps online
• Enforce conformance with corporate policies
user auditing/control, user/application differentiation
• Report findings to management
who’s not happy, what’s my ROI
• Identify how to leverage network as an asset
marketing!
4
© 2000, Cisco Systems, Inc.
NetMgmt
NetMgmt
Must Grow w/
Must Grow w/
Networking Trends
Networking Trends
• Users
more mobile, demanding & skilled
expected to conform to corporate policies (e.g. URL blocking)
• Applications
more delay sensitive, bandwidth hungry (aka multimedia)
unsupported apps on network (e.g. DOOM)
• Both Users & Applications
Have Increased dependency on network
Require Service Level differentiation
5
© 2000, Cisco Systems, Inc.
NetMgmt
NetMgmt
Must Grow w/

Must Grow w/
Networking Trends
Networking Trends
• New Network Designs
Intranets
Extranets
VPNs
• Traffic Patterns (e.g. unexpected congestion points)
increasingly short-lived “flows” (e.g. WEB)
dynamic ports
encryption
n-tiered architectures
6
© 2000, Cisco Systems, Inc.
Agenda
Agenda
• What is Network Management?
• Current Architecture(s)
• Two New Architectures
• Examples
• Concluding Remarks
7
© 2000, Cisco Systems, Inc.
Management Instrumentation & Control Mechanisms
Current Network Management
Current Network Management
Architecture
Architecture
Intelligent
Network

Devices
High Performance, Robust Network Infrastructure
SNMP, RMON, Telnet, ICMP
Standards-
based
protocols
e.g. HP OV
Cisco Apps
SAP
BMC Patrol
NMS
Platform
MRTG
3rd Party
Apps
SNMP
NMS
Framework
8
© 2000, Cisco Systems, Inc.
SNMP owned the ‘90s
SNMP owned the ‘90s
• Motivation behind SNMP
manage heterogeneous networking devices
(not systems, users or applications)
enhancement of SGMP
console consolidation
• SNMP “Architecture”
Intelligent Managers, dumb Agents
TRAP-directed polling (unreliable)

Clear-text communities
MIBs document what is available from a device
9
© 2000, Cisco Systems, Inc.
SNMP
SNMP
Needs help in the ‘00s
Needs help in the ‘00s
• SNMP is “practical” & will live-on, but
Security in V3 required for more configuration control
Unwieldy instancing/indexing makes life difficult
Not Extranet friendly (typically not allowed thru FW)
MIB’s continue to pro-create, but don’t define
relationships
10
© 2000, Cisco Systems, Inc.
NMS/Frameworks
NMS/Frameworks
• Still useful
eliminate duplication of efforts (e.g. fault mgmt)
provide structured, documented integration
• But -
Proprietary APIs slow development from ISVs
Integration today requires application co-location,
which complicates
software install
system admin & maintenance
Common place to represent each device, but not
store it’s information
11

© 2000, Cisco Systems, Inc.
Management Instrumentation & Control Mechanisms
Report Card - Current Network
Report Card - Current Network
Management Architecture
Management Architecture
High Performance, Robust Network Infrastructure
SNMP, RMON, Telnet, ICMP
NMS
Apps #1
App #2
App #3
App #4
12
© 2000, Cisco Systems, Inc.
What will happen to our friends?
What will happen to our friends?
• SNMP will continue to be a good data
collection mechanism
You can manage a device with SNMP, not a network
Remember - Simple Network Management Protocol
• NMS Frameworks become a node on the
“Management Intranet”
“… the architectures of the prior generation of management
products are not likely to dominate the market over the next
five years”
September 1999
Susan Aldrich - Patricia Seybold Group
James Herman & Theodore Forbath - Northeast Consulting Resources
13

© 2000, Cisco Systems, Inc.
Agenda
Agenda
• What is Network Management?
• Current Architecture(s)
• Two New Architectures
- WBEM
- DEN
• Examples
• Concluding Remarks
14
© 2000, Cisco Systems, Inc.
Management Instrumentation & Control Mechanisms
WBEM
WBEM
Network Management
Network Management
Architecture
Architecture
Intelligent
System
High Performance, Robust Network Infrastructure
SNMP, RMON, Telnet, ICMP, HTTP, COPS, DMI
Standards-
based
protocols
NMS
BMC Patrol
Cisco
App #n

Microsoft
Management
Intranet
App #1
XML/CIM
15
© 2000, Cisco Systems, Inc.
WBEM Built Upon
WBEM Built Upon
DMTF’s
DMTF’s
CIM
CIM
• WBEM initiative 1996 - Cisco, Compaq, Microsoft, Intel, BMC
- Build a Common Information Model(CIM) for management
- Harness the power of the Web for management interoperation
=> CIM & XML make up the WBEM core technology
16
© 2000, Cisco Systems, Inc.
So What is CIM?
So What is CIM?
The Common Information Model (CIM) defines
the Schemas used to represent the real-world
objects being managed. CIM uses an object-
oriented paradigm, where manageable objects
and their inter-relationships are modeled using
the concepts of classes and instances.
Vendors extend the standard classes to
represent unique feature/functions.
It may be helpful to think of CIM as standard and extended MIBs

that also include relationship definitions
17
© 2000, Cisco Systems, Inc.
What Is CIM(2)?
What Is CIM(2)?
• An object-oriented information model
A conceptual framework within which any
information system may be modeled
independent of repository and implementation
standardizes data and reduces its complexity
Supports enterprise-wide (vs. node-centric)
management of data
Allows integration of management information from
different sources with different syntaxes
18
© 2000, Cisco Systems, Inc.
What is CIM (3)?
What is CIM (3)?
• Core Model
Captures information that is applicable to all knowledge
domains
• Common Models
Information common to particular management areas, but
independent of a particular technology or implementation.
Include Systems, Applications, Devices, Networks, Databases,
and Events
• Extension Models
Represent vendor or technology-specific extensions that are
often dependent on a particular environment or platform
19

© 2000, Cisco Systems, Inc.
Why Object Oriented?
Why Not ‘Just’ a Schema
Why Object Oriented?
Why Object Oriented?
Why Not ‘Just’ a Schema
Why Not ‘Just’ a Schema
• Network elements and services
differ from other directory objects
Standard objects are simple and exist within
static boundaries
a user is always a user
Network elements and services are complex
objects and exist in a constantly changing
environment
a modular switch can change functions
Must model the interaction between network
elements, network services, the network, and
clients of the network
Product
Network
Service
Customer
Device
20
© 2000, Cisco Systems, Inc.
Elements of CIM
Elements of CIM
Elements of CIM
• CIM object-oriented building blocks

Object Class (type)
Inheritance (reuse, vendor extension)
Associations and aggregations (relationships between objects)
Cardinality (number of components that participate in each side
of a relationship)
Methods (interaction with objects)
Constraints and meta-data (how an object or relationship is
used)
“Perhaps CIM’s most important differentiator from previous standards is
its ability to show the relationships between different elements and
components that make up a computer system or a corporate network”
Elisabeth Horwitt
21
© 2000, Cisco Systems, Inc.
Building Blocks of CIM
Building Blocks of CIM
Building Blocks of CIM
• Managed Objects in CIM
PhysicalElement and LogicalElement
Provides ability to abstract a complex object (such as a router) into its physical and
logical aspects
Wide range of applicability (from wires and chips through routers, switches, desktop
computers, and systems)
Associations and Aggregations
Describes relationships between two classes and the characteristics of that
relationship
Example: A Service (OSPF) runs inside a Physical Element (a router) and an
association is used to describe that relationship
22
© 2000, Cisco Systems, Inc.

Using the Building Blocks of CIM
Using the Building Blocks of CIM
Using the Building Blocks of CIM
Physical Realization
Logical
Representation
ManagedSystemElement
Name: string
Description: string
Caption: string
Status: string
InstallDate: datetime
Information
Model
Instance
Instance
Name: "RouterRack"
Description: "Rack used to store routers"
Caption: ""
Status: "In Use"
InstallDate: 8/19/1994 10:53 AM
Name: "RouterRack"
Description: "Rack used to store routers"
Caption: ""
Status: "In Use"
InstallDate: 8/19/1994 10:53 AM
CreationClassName: "Rack"
Tag: "A23498372"
Manufacturer: "Rack-Em-Up Inc."
Model: "R4-10x15"

SKU: "123291990"
SerialNumber: "REU152-3312012"
PartNumber: "REU152"
Name: "RouterRack"
Description: "Rack used to store routers"
Caption: ""
Status: "In Use"
InstallDate: 8/19/1994 10:53 AM
CreationClassName: "Rack"
Tag: "A23498372"
Manufacturer: "Rack-Em-Up Inc."
Model: "R4-10x15"
SKU: "123291990"
SerialNumber: "REU152-3312012"
PartNumber: "REU152”
Removable: False
Replacable: False
HotSwappable: False
Height: "8 ft"
Depth: "18 in"
Width: "18 in"
Weight: "92 lbs”
Name: "RouterRack"
Description: "Rack used to store routers"
Caption: ""
Status: "In Use"
InstallDate: 8/19/1994 10:53 AM
CreationClassName: "Rack"
Tag: "A23498372"
Manufacturer: "Rack-Em-Up Inc."

Model: "R4-10x15"
SKU: "123291990"
SerialNumber: "REU152-3312012"
PartNumber: "REU152”
Removable: False
Replacable: False
HotSwappable: False
Height: "8 ft"
Depth: "18 in"
Width: "18 in"
Weight: "92 lbs”
CableManagementStrategy: "RatsNest"
LockPresent: True
IsLocked: True
PhysicalElement
CreationClassName: string [key]
Tag: string [key]
Manufacturer: string
Model: string
SKU: string
SerialNumber: string
Version: string
PartNumber: string
OtherIdentifyingInfo: string
PoweredOn: boolean
PhysicalElement
CreationClassName: string [key]
Tag: string [key]
Manufacturer: string
Model: string

SKU: string
SerialNumber: string
Version: string
PartNumber: string
OtherIdentifyingInfo: string
PoweredOn: boolean
PhysicalPackage
Removable: boolean
Replaceable: boolean
HotSwappable: boolean
Height: real32
Depth: real32
Width: real32
Weight: real32
PhysicalPackage
Removable: boolean
Replaceable: boolean
HotSwappable: boolean
Height: real32
Depth: real32
Width: real32
Weight: real32
PhysicalFrame
CableManagementStrategy: string
ServicePhilosophy: uint16 [ ]
ServiceDescriptions: string [ ]
LockPresent: boolean
AudibleAlarm: boolean
VisibleAlarm: boolean
SecurityBreach: uint16

BreachDescription: string
IsLocked: boolean
PhysicalFrame
CableManagementStrategy: string
ServicePhilosophy: uint16 [ ]
ServiceDescriptions: string [ ]
LockPresent: boolean
AudibleAlarm: boolean
VisibleAlarm: boolean
SecurityBreach: uint16
BreachDescription: string
IsLocked: boolean
Chassis
NumberOfPowerCords: uint16
CurrentRequiredOrProduced: sint16
HeatGeneration: uint16
ChassisTypes: uint16 [ ]
TypeDescriptions: string [ ]
Rack
TypeOfRack: uint16
CountryDesignation: string
0..1
ChassisInRack
Name: "RouterRack"
Description: "Rack used to store routers"
Caption: ""
Status: "In Use"
InstallDate: 8/19/1994 10:53 AM
CreationClassName: "Rack"
Tag: "A23498372"

Manufacturer: "Rack-Em-Up Inc."
Model: "R4-10x15"
SKU: "123291990"
SerialNumber: "REU152-3312012"
PartNumber: "REU152”
Removable: False
Replacable: False
HotSwappable: False
Height: "8 ft"
Depth: "18 in"
Width: "18 in"
Weight: "92 lbs”
CableManagementStrategy: "RatsNest"
LockPresent: True
IsLocked: True
TypeOfRack: 17
CountryDesignation: "USA"
23
© 2000, Cisco Systems, Inc.
Using the Building Blocks of CIM
Using the Building Blocks of CIM
Using the Building Blocks of CIM
Physical Realization
Logical
Representation
ManagedSystemElement
Name: string
Description: string
Caption: string
Status: string

InstallDate: datetime
Information
Model
Instance
Instance
PhysicalElement
CreationClassName: string [key]
Tag: string [key]
Manufacturer: string
Model: string
SKU: string
SerialNumber: string
Version: string
PartNumber: string
OtherIdentifyingInfo: string
PoweredOn: boolean
PhysicalElement
CreationClassName: string [key]
Tag: string [key]
Manufacturer: string
Model: string
SKU: string
SerialNumber: string
Version: string
PartNumber: string
OtherIdentifyingInfo: string
PoweredOn: boolean
PhysicalPackage
Removable: boolean
Replaceable: boolean

HotSwappable: boolean
Height: real32
Depth: real32
Width: real32
Weight: real32
PhysicalPackage
Removable: boolean
Replaceable: boolean
HotSwappable: boolean
Height: real32
Depth: real32
Width: real32
Weight: real32
PhysicalFrame
CableManagementStrategy: string
ServicePhilosophy: uint16 [ ]
ServiceDescriptions: string [ ]
LockPresent: boolean
AudibleAlarm: boolean
VisibleAlarm: boolean
SecurityBreach: uint16
BreachDescription: string
IsLocked: boolean
PhysicalFrame
CableManagementStrategy: string
ServicePhilosophy: uint16 [ ]
ServiceDescriptions: string [ ]
LockPresent: boolean
AudibleAlarm: boolean
VisibleAlarm: boolean

SecurityBreach: uint16
BreachDescription: string
IsLocked: boolean
Chassis
NumberOfPowerCords: uint16
CurrentRequiredOrProduced: sint16
HeatGeneration: uint16
ChassisTypes: uint16 [ ]
TypeDescriptions: string [ ]
Rack
TypeOfRack: uint16
CountryDesignation: string
0..1
ChassisInRack
Rack:
Rack:
Name=”Rack 1”
Name=”Rack 1”
Chassis:
Chassis:
Name=“Chas A”
Name=“Chas A”
ChassisInRack
Chassis:
Chassis:
Name=“Chas A”
Name=“Chas A”
ChassisInRack
Chassis:
Chassis:

Name=“Chas B”
Name=“Chas B”
ChassisInRack
ChassisInRack
Chassis:
Chassis:
Name=“Chas D”
Name=“Chas D”
ChassisInRack
ChassisInRack
24
© 2000, Cisco Systems, Inc.
Using the Building Blocks of CIM
Using the Building Blocks of CIM
Using the Building Blocks of CIM
Physical Realization
Logical
Representation
ManagedSystemElement
Name: string
Description: string
Caption: string
Status: string
InstallDate: datetime
Information
Model
PhysicalElement
CreationClassName: string [key]
Tag: string [key]
Manufacturer: string

Model: string
SKU: string
SerialNumber: string
Version: string
PartNumber: string
OtherIdentifyingInfo: string
PoweredOn: boolean
PhysicalElement
CreationClassName: string [key]
Tag: string [key]
Manufacturer: string
Model: string
SKU: string
SerialNumber: string
Version: string
PartNumber: string
OtherIdentifyingInfo: string
PoweredOn: boolean
PhysicalPackage
Removable: boolean
Replaceable: boolean
HotSwappable: boolean
Height: real32
Depth: real32
Width: real32
Weight: real32
PhysicalPackage
Removable: boolean
Replaceable: boolean
HotSwappable: boolean

Height: real32
Depth: real32
Width: real32
Weight: real32
PhysicalFrame
CableManagementStrategy: string
ServicePhilosophy: uint16 [ ]
ServiceDescriptions: string [ ]
LockPresent: boolean
AudibleAlarm: boolean
VisibleAlarm: boolean
SecurityBreach: uint16
BreachDescription: string
IsLocked: boolean
PhysicalFrame
CableManagementStrategy: string
ServicePhilosophy: uint16 [ ]
ServiceDescriptions: string [ ]
LockPresent: boolean
AudibleAlarm: boolean
VisibleAlarm: boolean
SecurityBreach: uint16
BreachDescription: string
IsLocked: boolean
Chassis
NumberOfPowerCords: uint16
CurrentRequiredOrProduced: sint16
HeatGeneration: uint16
ChassisTypes: uint16 [ ]
TypeDescriptions: string [ ]

Rack
TypeOfRack: uint16
CountryDesignation: string
0..1
ChassisInRack
Rack:
Rack:
Name=”Rack 1”
Name=”Rack 1”
Chassis:
Chassis:
Name=“Chas A”
Name=“Chas A”
Chassis:
Chassis:
Name=“Chas B”
Name=“Chas B”
Chassis:
Chassis:
Name=“Chas D”
Name=“Chas D”
ChassisInRack
ChassisInRack
Rack:
Rack:
Name=”Rack 2”
Name=”Rack 2”
Chassis:
Chassis:
Name=“Chas A”

Name=“Chas A”
Chassis:
Chassis:
Name=“Chas C”
Name=“Chas C”
Chassis:
Chassis:
Name=“Chas D”
Name=“Chas D”
ChassisInRack
ChassisInRack
25
© 2000, Cisco Systems, Inc.
XML
XML
XML
• Extensible Markup Language
a simplified derivative of SGML
• XML structures data
it uses TAGs much like HTML
with an unambiguous “grammar”
• Transported using HTTP
• Used to encode CIM data for exchange between
management stations
• Courtesy of the W3C (not DMTF)