A device type represents a particular make and model of hardware that exists in the real world. Device types define the physical attributes of a device (rack height and depth) and its individual components (console, power, and network interfaces).
Device types are instantiated as devices installed within racks. For example, you might define a device type to represent a Juniper EX4300-48T network switch with 48 Ethernet interfaces. You can then create multiple devices of this type named "switch1," "switch2," and so on. Each device will inherit the components (such as interfaces) of its device type at the time of creation. (However, changes made to a device type will not apply to instances of that device type retroactively.)
Some devices house child devices which share physical resources, like space and power, but which functional independently from one another. A common example of this is blade server chassis. Each device type is designated as one of the following:
A parent device (which has device bays)
A child device (which must be installed in a device bay)
This parent/child relationship is not suitable for modeling chassis-based devices, wherein child members share a common control plane.
For that application you should create a single Device for the chassis, and add Interfaces directly to it. Interfaces can be created in bulk using range patterns, e.g. "Gi1/[1-24]".
Add Inventory Items if you want to record the line cards themselves as separate entities. There is no explicit relationship between each interface and its line card, but it may be implied by the naming (e.g. interfaces "Gi1/x" are on line card 1)
Each device type must be assigned to a manufacturer. The model number of a device type must be unique to its manufacturer.
Device Component Templates
Each device type is assigned a number of component templates which define the physical components within a device. These are:
- Console ports
- Console server ports
- Power ports
- Power outlets
- Network interfaces
- Front ports
- Rear ports
- Device bays (which house child devices)
Whenever a new device is created, its components are automatically created per the templates assigned to its device type. For example, a Juniper EX4300-48T device type might have the following component templates defined:
- One template for a console port ("Console")
- Two templates for power ports ("PSU0" and "PSU1")
- 48 templates for 1GE interfaces ("ge-0/0/0" through "ge-0/0/47")
- Four templates for 10GE interfaces ("xe-0/2/0" through "xe-0/2/3")
Once component templates have been created, every new device that you create as an instance of this type will automatically be assigned each of the components listed above.
Assignment of components from templates occurs only at the time of device creation. If you modify the templates of a device type, it will not affect devices which have already been created. However, you always have the option of adding, modifying, or deleting components on existing devices.
Console Port Templates
A template for a console port that will be created on all instantiations of the parent device type.
Console Server Port Templates
A template for a console server port that will be created on all instantiations of the parent device type.
Power Port Templates
A template for a power port that will be created on all instantiations of the parent device type.
Power Outlet Templates
A template for a power outlet that will be created on all instantiations of the parent device type.
A template for an interface that will be created on all instantiations of the parent device type.
Front Port Templates
A template for a front-facing pass-through port that will be created on all instantiations of the parent device type.
Rear Port Templates
A template for a rear-facing pass-through port that will be created on all instantiations of the parent device type.
Device Bay Templates
A template for a device bay that will be created on all instantiations of the parent device type.