Delete Normal VLANs

• 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.

Basic Palo Alto FW Commands

• Show VLANs on a Palo Alto

o uname@FW-Name(active)# show network interface vlan

• Show Interfaces on Palo Alto

o uname@FW-Name(active)# show network interface Ethernet

• Basic show logging of traffic on PA

o uname@FW-Name(active)# show log traffic src in x.x.x.x receive_time in last-hour dport equal 443

• Show NAT policies on a PA

o >show running nat-policy

• Show DHCP configuration info for PA

o >conf t

o #show network dhcp interface vlan.your-vlan relay

• PA privilege mode is with the > sign.

• Config mode for a PA is with the # sign

Clearing UCSM error F0933 “named VLAN for vNIC cannot be resolved” errors

1.    First off upon logging onto your UCSM you find this lovely error:

2.    So what is happening here is you done messed up A A Ron! A VLAN was deleted from the global LAN Cloud area and more than likely is still attached to a vNIC template out there. There can be some other causes, but this has been the most common issue I have found with this error. Your UCS has a VLAN it does not know what to do with.
3.    So, from the error screen, go ahead and go to your LAN section in your UCS and go to your vNIC templates section:

4.    Now we can go ahead and select this VLAN we thought was gone, and click on the Delete at the bottom.

5.    Once you delete the VLAN, the errors should go down or start going away. You want to check all your vNIC templates to ensure it has been removed.

Adding VLANs to Cisco UCSM & HyperFlex

I know there are a few more ways to do these procedures, but this is just one example in this overall SOP.

1.    First, from the UCS manager, go to the LAN section on the left hand side, then expand LAN> Policies> root>Sub-Organizations>YourDataCenter>vNIC Templates>vNIC Template vm-network-a, and vNIC Template vm-network-b

2.    Once you navigate here, you can click on the “Modify VLANs” Action under the “General” tab.

3.    On the menu on the pop-up, click on “Create VLAN”

4.    On the Create VLANs screen, fill in your VLAN Name/Prefix with a name you wish to call this VLAN, example: MyTestVLAN-100. Then put in your VLAN number, example: 100

 5.    Now make sure to go to the second “vNIC Template vm-network-b” or whatever other vm-template policies you have to ensure it added there too (it should do this automatically with linked templates, but always good to check).

6.    Oh we are not done yet folks! Now, we have the VLAN added to the vm-network templates, now we can add the VLANs to the actual servers so they can start processing the VLAN tagging. This part is easy, just check the box on the new VLAN/VLANs you wish to add to the vm-network templates.

7.    Now, in the top tabs, next to the “General” tab, you can click on VLANs and verify your VLAN has appeared and is now showing in the VLANs for the UCS vNIC Template. You can now add your Port-Group/VLAN information into the VMware vSphere and your Cisco equipment. Ensure the VLAN tag is connected all the way through the Layer 2 systems for it to fully pass through.


Reference:
https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/ucs-manager/GUI-User-Guides/Network-Mgmt/4-0/b_UCSM_Network_Mgmt_Guide_4_0/b_UCSM_Network_Mgmt_Guide_4_0_chapter_0110.html

Enable a Routable/Switched Virtual Interface (SVI) for a Layer 3 Switch

1.    First off, if it is a brand-new switch with no routing interfaces already on the device (usually straight out of the box), then you need to enable IP routing on the switch. This enables the switch to do routing on the device itself.
    a.    #configure terminal
    b.    #ip routing
2.    Now that routing is enabled, we can create our SVI, or our vlan interface. This is creating a default gateway on the switch itself to allow inter-vlan routing within the switch. This eliminates the need for a router in between the switch and its separate networks/VLANs.
    a.    #configure terminal
    b.    #interface vlan 100
    c.    #ip address X.X.X.1 255.255.255.0
    d.    #no shut (don’t forget to do this since your SVI interfaces can be shut down by default. Just check to be sure)
3.    Now you can test your traffic and ensure it passes through.


References: https://www.cisco.com/c/en/us/support/docs/lan-switching/inter-vlan-routing/41860-howto-L3-intervlanrouting.html