Step 1: UCS-A# scope security
Step 2: UCS-A /security # scope keyring default
Step 3: UCS-A /security/keyring # set regenerate yes
Step 4: UCS-A /security/keyring # commit-buffer
This blog consists of configurations and processes I have performed in a lab environment. In no way do I recommend or imply these processes need to be followed or are the correct way to execute on any network. Perform at your own risk. Also, please feel free to leave comments if my configurations are too old/need updating.
###First you need to create a server profile under the LDAP section. DEVICE>Server Profiles>LDAP then click on the Add down at the bo...
Step 1: UCS-A# scope security
Step 2: UCS-A /security # scope keyring default
Step 3: UCS-A /security/keyring # set regenerate yes
Step 4: UCS-A /security/keyring # commit-buffer
####You must use the local admin account in order for the option to be listed.
####Login through SSH to the FI VIP (or the current primary FI).
####Next connect to the local management CLI then execute the rease conifig command.
FI-A#local-mgmt
FI-A(local-mgmt)erase configuration
All UCS configurations will be erased and system will reboot. Are you sure? (yes/no):yes
####Make sure to do the same process on the other FI if you have a secondary.
####The configurations will be erased and the FIs will reboot.
###First, create the Remote SPAN (RSPAN) VLAN. You must do this on both switches
SW1#configuration terminal
SW1(config)#vlan 999
SW1(config-vlan)#name RSPAN-VLAN
SW1(config-vlan)#remote-span
SW1(config-vlan)#exit
SW2#configuration terminal
SW2(config)#vlan 999
SW2(config-vlan)#name RSPAN-VLAN
SW2(config-vlan)#remote-span
SW2(config-vlan)#exit
###Next, create your monitor session for your source ports you are mirroring
SW1#configuration terminal
SW1(config)#monitor session 1 source interface gi 1/0/2 both ###This enables both transmit and receive to be recorded
###Now you can add the RSPAN VLAN to your monitor session as a destination to drop the data into the RSPAN VLAN:
SW1#configure terminal
SW1(config)#monitor session 1 destination remote vlan 999
###Now, go to your next switch in the destination and create a monitor session pulling from the RSPAN VLAN
SW2#configuration terminal
SW2(config)#monitor session 1 source remote vlan 999
###Finally, create a destination monitor session to dump the RSPAN VLAN traffic to your system analyzing the traffic
SW2#configuration terminal
SW2(config)#monitor session 1 destination interface gi 1/0/2
#set service dhcp-relay interface YOUR_INTERFACE
Or,
#set service dhcp-relay server YOUR_SERVER_IP
#commit
#save
Reference:
https://docs.vyos.io/en/equuleus/configuration/service/dhcp-relay.html
#set interfaces ethernet YOUR_INTERFACE address YOUR_IP|dhcp|dhcpv6
#set interfaces ethernet YOUR_INTERFACE description DESCRIPTION_FOR_INTERFACE
#set interfaces ethernet YOUR_INTERFACE disable
#set interfaces ethernet YOUR_INTERFACE enable
#commit
#save
Reference:
https://docs.vyos.io/en/equuleus/configuration/interfaces/ethernet.html
Set a password for Console login
RTR-01#config t
RTR-01(config)#line console 0
RTR-01(config-line)#login (turns on login enable ability. Otherwise will not prompt)
RTR-01(config-line)#password cisco123
RTR-01(config-line)#end
Set an enable secret password
RTR-01#config t
RTR-01(config)#enable secret cisco123
RTR-01(config)#exit
RTR-01#disable (takes you back to user mode)
RTR-01>enable
Enter password: YOUR_PASSWORD_NOW
Set VTY password
RTR-01#config t
RTR-01(config)#line vty 0 15
RTR-01(config-line)#login (enables the login feature to the VTY line)
RTR-01(config-line)#password cisco123 (sets the password for the line login)
RTR-01(config-line)#end
Enable Global Password Encryption
RTR-01#config t
RTR-01(config)#service password-encryption
1. First you need to add the rule:
a. user@test>firewalld-cmd --add-port=YOUR_PORT_#/udp-or-tcp --permanent
2. Restart the firewall:
a. user@test>firewall-cmd --reload
3. Check the firewall list:
a. user@test>firewall-cmd --list-all
• Check Status of Pods
o kubectl get pods (quick detail)
o kubectl get pods -A (more details)
• Check the logs on a pod
o kubectl logs POD_NAME
o kubectl logs POD_NAME CONTAINER_NAM (For pods with multiple containers)
• Delete one pod, or selected ones:
o kubectl delete pod YOUR_POD, NEXT_POD
• Delete All Pods
o kubectl delete pod --all
• Pull evicted pods and then Delete them
o kubectl get pod | grep Evicted | awk '{print $1}' | xargs kubectl delete pod
• Get services for each pod (service is the gateway into the pod)
o kubectl get endpoints
• Get service endpoints for specific pod:
o kubectl get endpoints YOUR_POD_NAME
• Get service cluster IPs for Pods
o kubectl get services
• Check the logs for the Kubernetes Startup/Shutdown
o journalctl -u kubelet
• Get service information for a specific pod
o kubectl describe service YOUR_SERVICE/POD
• Get pod information for specific pod
o kubectl describe YOUR_POD
• Find information on your nodes
o kubectl get nodes
• get pods under a specific namespace
o kubectl get pods --namespace YOUR_NAMESPACE -A
• First verify your time by typing in:
o #timedatectl
• Set NTP or Disable
o #timedatectl set-ntp yes
o #timedatectl set-ntp no
• Set Timezones
o #timedatectl set-timezone UTC
o #timedatectl set-local-rtc 1(YOUR_LOCAL_TIMEZONE)
• Change the Clock
o #timedatectl set-time HH:MM:SS
o #timedatectl set-time YYYY-MM-DD
• List Timezones
o #timedatectl list-timezones
o #timedatectl list-timezones | grep keyword(Time-Zone)
• Set Hardware Clock to Sync with UTC
o #timdatectl set-local-rtc 0
• Display the Hardware Clock (Older Ubuntu Versions)
o #sudo hwclock -r
o #sudo hwclock --show
o #sudo hwclock --show --verbose
• Display the date and change the date/time (Older Ubuntu Versions)
o #date (display)
o #sudo date -s YY-MM-DD HH:MM:SS
• First off, VLANs are sorted through identifiers. Regular VLANs are identified with 1-4096.
• There are actually VLANs 1-1001 which are called normal VLANs and they are stored in the vlan.dat file. These cannot be deleted by deleting the config or running file. They are stored in flash. Every once in a while, you might have to delete them completely though.
• The only way to delete them is by deleting this vlan.dat file and then reloading the switch.
• You can delete these by doing the following steps:
o SW-01>enable
o SW-01#delete vlan.dat
Delete filename [vlan.dat]?
• This displays the vlan.dat filename, press ENTER to confirm.
Delete flash:/vlan.dat? [confirm]
• This asks again that you are about to delete the vlan.dat file from system flash, press ENTER to confirm again.
o SW-01#reload
• Once you reload your switch you can check your VLANs with:
o SW-01#show vlan brief
• Verify the VLANs are fully cleared out.