Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
49 changes: 48 additions & 1 deletion node-definitions/cisco/ise/ise.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ sim:
memory: 1
efi_boot: false
boot:
timeout: 1200
timeout: 3600
uses_regex: false
inherited:
image:
Expand All @@ -50,4 +50,51 @@ inherited:
configuration:
generator:
driver: null
provisioning:
files:
- editable: true
name: ise-ztp.conf
content: |-
hostname=inserthostname-here
ipv4_addr=<IPv4 address>
ipv4_mask=<IPv4 subnet>
ipv4_default_gw=<IPv4 gateway address>
# IPv6 is optional
#ipv6_addr=<IPv6 address>
#ipv6_default_gw=<IPv6 gateway address>
domain=cisco.com
primary_nameserver=<IPv4 address> <--example-8.8.8.8
# secondary and tertiary are optional
#secondary_nameserver=<IPv4 address>
#tertiary_nameserver=<IPv4 address>
primary_ntpserver=<IPv4 address or FQDN of the NTP server> <--example-time.google.com
#secondary and tertiary are optional
#secondary_ntpserver=<IPv4 address or FQDN of the NTP server>
#tertiary_ntpserver=<IPv4 address or FQDN of the NTP server>
#timezone=<timezone>
#ssh=<true/false>
username=admin
password=Cisc@123
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this password meet complexity requirements and do these settings work if IP is provided?

Copy link
Contributor Author

@BregaladTaran BregaladTaran Jun 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • This password does work, since it's the one I used in the last test of ISE.

  • I commented all the settings which are not required (i.e. ISE needed at the very least the settings I left uncommented)

  • Examples for nameserver and ntpserver are ones that work for me when NOT on VPN. I provided them specifically as an example, but I am assuming these will depend on the person running ISE.

  • I do have have all the values for the minimal working configuration (I can send them here if needed), but I have assumed that those should not go here since some of them work just for me (being on cisco vpn).

  • Next, I rewrote the boot timeout to 3600 since from my experience it takes at least an hour for ISE to bootup

  • issues with console:

    • the console can freez-up, so it is preferred to only pay attention to VNC
    • the output from console can be quite confusing - some strings get printed in the same line,
      even though they should be on separate lines; sometimes an issue pops up but if ignored, the setup continues as normal; sometimes the user is prompted to "Press to continue" even though in the same lane it says that Booting OS please wait... and so on, I didn't write down all the weird things these are just some that I remember;
  • possible SERIOUS issue:

    • since the ISE literally pulls 300 gigabytes of data (assuming it's started with external connector and
      correct config), couldn't it be an issue if someone who maybe doesn't realize this fact, started ISE on
      a machine, not knowing that there is not enough space and that if ISE is allowed to go on it wil
      l completely fill the memory of said machine which will (or can) lag it out, or potentially even halt it
      by filling all the memory?
      (I feel like this is something which could realistically be done by accident and it could cause some
      issues)

(These issue and observations were made using this image: http://10.122.58.4/CML2/2.9/images/Cisco-vISE-300-3.4.0.608.qcow2 )

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow. I've never seen an hour for the first boot. But I haven't used ISE 3.4 yet. My last experience was with 3.3. I think we should document things if it does a silent update from the internet. Again, that's not been my experience, but maybe ISE 3.4 is doing this? What does it pull down?

# Public Key Authentication configuration is optional
#public_key=<Public Key>
# Repository Configuration are optional
#repository_name=<repository name>
#repository_protocol=<repository protocol>
#repository_server_name=<IPv4 address>
#repository_path=<repository path>
# Patch Information - optional
#patch=<patch filename>
# HotPatches Information - optional
#hotpatches=<hotpatch filename,comma separated list>
# services - optional
#ers=<true/false>
#openapi=<true/false>
#pxgrid=<true/false>
#pxGrid_Cloud=<true/false>
# Skipping specific checks
#SkipIcmpChecks=<true/false>
#SkipDnsChecks=<true/false>
#SkipNtpChecks=<true/false>
media_type: ext4
volume_name: ISE-ZTP
schema_version: 0.0.1
2 changes: 1 addition & 1 deletion node-definitions/microsoft/Windows10/Readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This directory contains the following node definition:

### Image Availability

VHD images can be downloaded from microsoft on a trial basis here: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise Then the VHD image will have to be converted to a .qcow2 format. Linux qumu-img makes it easy. Documentation: https://docs.openstack.org/image-guide/convert-images.html
VHD images can be downloaded from microsoft on a trial basis here: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-10-enterprise Then the VHD image will have to be converted to a .qcow2 format. Linux `qemu-img` makes it easy. Documentation: https://docs.openstack.org/image-guide/convert-images.html

### Notes

Expand Down
13 changes: 13 additions & 0 deletions node-definitions/microsoft/Windows11/Readme.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
# Microsoft Windows 11

This directory contains the following node definition:

* `win11.yaml` - Microsoft Windows 11 node definition

### Image Availability

VHD images can be downloaded from Microsoft on a trial basis here: https://www.microsoft.com/en-us/evalcenter/evaluate-windows-11-enterprise. Then the VHD image will have to be converted to a .qcow2 format. Linux `qemu-img` makes it easy. Documentation: https://docs.openstack.org/image-guide/convert-images.html

### Notes

This node definition uses 2 VCPUS and 6 GB RAM.
71 changes: 71 additions & 0 deletions node-definitions/microsoft/Windows11/win11.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,71 @@
id: win11
general:
nature: server
read_only: false
description: Windows 11
device:
interfaces:
has_loopback_zero: false
physical:
- eth0
- eth1
- eth2
- eth3
- eth4
- eth5
- eth6
- eth7
serial_ports: 1
default_count: 2
ui:
visible: true
label_prefix: win11-
icon: host
label: Windows 11
description: |-
2 vCPUs 6 GB RAM

Username/Password:
IEUser/Passw0rd! (or whichever is set on installation)

##### Note
**EXPERIMENTAL**

The -waitpkg flag is required for boot with hyperv compatibility,
which speeds up the node; the model setting then required disabling
the other features (hle,rtm,mpx) on the machine used to test this.
sim:
linux_native:
libvirt_domain_driver: kvm
driver: server
disk_driver: sata
ram: 6144
cpus: 2
nic_driver: e1000
video:
model: cirrus
memory: 16
cpu_limit: 20
cpu_model: 'Skylake-Server,-waitpkg,-hle,-rtm,-mpx'
machine_type: q35
enable_tpm: true
efi_boot: true
boot:
timeout: 300
inherited:
image:
ram: true
cpus: true
data_volume: true
boot_disk_size: true
cpu_limit: true
node:
ram: true
cpus: true
data_volume: true
boot_disk_size: true
cpu_limit: true
configuration:
generator:
driver: server
schema_version: 0.0.1