general port vs trunk port

On a Port in General Mode you can have more than one untagged Vlan. So it is used for 802.1x Ports or Mac based Vlan configuration.

If you want only one untagged Vlan use you can also use the Trunk Mode. With Switchport mode trunk the Switch tagges all vlans (exept the native) so it is not necessary to have a allow list like in general mode.

N Series

##############################################################################################################################################

• Access — The port belongs to a single untagged VLAN.

Configure a Vlan Untagged to a Port,  In the Example VLAN 23.

console(config)# interface gi1/0/8

console(config-if)# switchport mode access

console(config-if)# switchport access vlan 23

##############################################################################################################################################

Trunk vs. General Mode

·         In General Mode are egress more then one untagged Vlans possible

##############################################################################################################################################

• General — The port belongs to VLANs, and each VLAN is user-defined as tagged or untagged (full 802.1Q mode).

Several Vlans tagged and / or untagged configured on a port, eg Uplink (the Vlans 23, 25 are the tagged Vlans, Vlans 24, 27 are untagged, untagged packets that are received in the example will be switched on VLAN 24 (PVID).

The port configuration must be in respect of the tagged / untagged Vlans the same as its counterpart, switch, server can be established). If Only the Command console(config-if)# switchport mode general

is configured then the following Defaults are present:

General Mode PVID: 1 (default)                   -> Vlan 1 untagged

General Mode Ingress Filtering: Enabled

General Mode Acceptable Frame Type: Admit All

General Mode Dynamically Added VLANs:

General Mode Untagged VLANs: 1

General Mode Tagged VLANs:                     -> NO Vlan Tagged

General Mode Forbidden VLANs:

console(config)# interface gi1/0/11

console(config-if)# switchport mode general

console(config-if)# switchport general allowed vlan add 23,25 tagged

console(config-if)# switchport general allowed vlan add 24,27 untagged

console(config-if)# switchport general pvid 24

##############################################################################################################################################

• Trunk — The port belongs to VLANs on which all ports are tagged (except for one per port that can be untagged).

Several Vlans tagged  plus one untagged configured on a port, eg Uplink (the Vlans 23, 24, 25 are the tagged Vlans, Vlan 22 is untagged, untagged packets that are received in the example will be switched on VLAN 22.

The port configuration must be in respect of the tagged / untagged Vlans the same as its counterpart, switch, server can be established). If Only the Command console(config-if)# switchport mode trunk

is configured then the following Defaults are present:

Trunking Mode Native VLAN: 1 (default)    -> Vlan 1 untagged

Trunking Mode Native VLAN Tagging: Disabled

Trunking Mode VLANs Enabled: All            -> ALL Vlans Tagged, except Native Vlan 1

console(config)# interface gi1/0/9

console(config-if)# switchport mode trunk

console(config-if)# switchport mode trunk native vlan 22

console(config-if)# switchport mode trunk allowed vlan add 22-25

##############################################################################################################################################

FORCE 10

##############################################################################################################################################

By default, all interfaces are in Layer 3 mode and not belonging to any Vlan. So you could configure an IP address on the port concerned, as on a classical router.

RVL-S4810-1# show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto       Auto   --           -> member in none Vlan

##############################################################################################################################################

To configure the port in a Vlan, you  must make a change to Layer2 / switch port Mode. It also falls automatically to the default untagged Vlan. This is by default Vlan 1. It can be be changed if necessary RVL-S4810-1(conf)#default vlan-id xxx.

A Default VLAN IP address can not be given. To obtain an IP interface to Vlan 1 you must change the default Vlan to another Vlan first

RVL-S4810-1(conf-if-te-0/46)#switchport

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto    1     -> untagged member in default Vlan

To change untagged Vlan:

RVL-S4810-1(conf)# int vlan 2

RVL-S4810-1(conf-if-vl-2)#untagged tengigabitethernet 0/46

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto   2      -> now untagged member in Vlan 2

##############################################################################################################################################

To make the port to trunk port and to tag multiple Vlans without a untagged native VLAN.

RVL-S4810-1(conf-if-te-0/46)#switchport

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto    1          -> untagged member in default Vlan (will be changed/removed when adding the first tagged Vlan)

To add tagged Vlans (here you can see, that the native vlan is removed and the the switch tag all Vlans):

RVL-S4810-1(conf-if-te-0/46)#int vlan 3

RVL-S4810-1(conf-if-vl-3)#tagged tengigabitethernet 0/46

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto   3

RVL-S4810-1(conf-if-te-0/46)#int vlan 4

RVL-S4810-1(conf-if-vl-4)#tagged tengigabitethernet 0/46

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto   3-4

With RVL-S4810-2# show vlan you can see which Ports are tagged and untagged Members on the Vlans:

RVL-S4810-2# show vlan

Codes: * - Default VLAN, G - GVRP VLANs, R - Remote Port Mirroring VLANs, P - Pimary, C - Community, I - Isolated

       O - Openflow

Q: U - Untagged, T - Tagged

   x - Dot1x untagged, X - Dot1x tagged

   o - OpenFlow untagged, O - OpenFlow tagged

   G - GVRP tagged, M - Vlan-stack, H - VSN tagged

   i - Internal untagged, I - Internal tagged, v - VLT untagged, V - VLT tagged

    NUM    Status    Description                     Q Ports

    1      Active                                             

    2      Active                                   

    3      Active                                    T Te 0/46             -> 0/46 now tagged member in Vlan 3

    4      Active                                    T Te 0/46             -> 0/46 now tagged member in Vlan 4

No untagged native VLAN !!! Port is not in hybride Mode !!

##############################################################################################################################################

To make the port to trunk port and to tag multiple Vlans or to make double tagging on it, it must be configured in the Port Mode Hybrid.

Is it not in the default mode (Layer 3, see above) you have to configure it in these default configure mode:

RVL-S4810-1(conf-if-te-0/46)#portmode hybrid

% Error: Port is in Layer-2 mode Te 0/46.

RVL-S4810-1(conf-if-te-0/46)#int vlan 2

RVL-S4810-1(conf-if-vl-2)#no untagged tengigabitethernet 0/46

RVL-S4810-1(conf-if-te-0/46)#no switchport

Now you can change the port mode:

RVL-S4810-1(conf-if-te-0/46)#portmode hybrid

RVL-S4810-1#show int tengigabitethernet 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto   --           -> member in none Vlan

Now you can add Vlans tagged and untagged to the Port:

RVL-S4810-1(conf-if-te-0/46)#switchport

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto    1          -> untagged member in default Vlan

To change the untagged Vlan:

RVL-S4810-1(conf)# int vlan 2

RVL-S4810-1(conf-if-vl-2)#untagged tengigabitethernet 0/46

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto   2           -> now untagged member in Vlan 2

To add additional tagged Vlans:

RVL-S4810-1(conf-if-te-0/46)#int vlan 3

RVL-S4810-1(conf-if-vl-3)#tagged tengigabitethernet 0/46

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto   2-3

RVL-S4810-1(conf-if-te-0/46)#int vlan 4

RVL-S4810-1(conf-if-vl-4)#tagged tengigabitethernet 0/46

RVL-S4810-1#show int ten 0/46 status

Port     Description  Status Speed     Duplex Vlan

Te 0/46               Down   Auto      Auto   2-4

With RVL-S4810-2# show vlan you can see which Ports are tagged and untagged Members on the Vlans:

RVL-S4810-2# show vlan

Codes: * - Default VLAN, G - GVRP VLANs, R - Remote Port Mirroring VLANs, P - Pimary, C - Community, I - Isolated

       O - Openflow

Q: U - Untagged, T - Tagged

   x - Dot1x untagged, X - Dot1x tagged

   o - OpenFlow untagged, O - OpenFlow tagged

   G - GVRP tagged, M - Vlan-stack, H - VSN tagged

   i - Internal untagged, I - Internal tagged, v - VLT untagged, V - VLT tagged

    NUM    Status    Description                     Q Ports

    1      Active                                    U Te 0/1-45,47-48         

    2      Active                                    U Te 0/46            -> 0/46 now untagged member in Vlan 2

    3      Active                                    T Te 0/46            -> 0/46 now tagged member in Vlan 3

   4      Active                                    T Te 0/46             -> 0/46 now tagged member in Vlan 4

##############################################################################################################################################

vSphere Data Protection (VDP) Troubleshooting Commands

Source: http://www.virten.net/2015/02/vsphere-data-protection-vdp-troubleshooting-commands/ 

You have to connect to the VDP appliance with SSH as root (password was set during initial configuration)

status.dpn
Display VDP status information

dpnctl status
Display service status information

capacity.sh
Analyse space consumption from the last 30 backup jobs. Displays the amount of new data and how much space the garbage collection has recovered.

df -h
Display free partition space. This is not an equivalent to the free space displayed in the GUI but can reveal issues if partitions are full.

cplist
Display Checkpoint status

mccli server show-prop
Display VDP appliance properties. This is an equivalent to the information shown in the vSphere Web Client

mccli activity show
Display backup jobs information. Each activity is a backup job from a single virtual machine. If you have one daily backup job with 10 VMs configured in VDP, you will see 10 activities per day.

mccli activity get-log –id=<ID>
Get the activity log from a backup job. If a backup job failed, you might find useful information here. Produces lots of information, so it’s better to pipe it to a file.

mccli activity show –name=/<VCENTER>/VirtualMachines/<VM>
Display backup jobs information from a single Virtual Machine

Which SFP+ Modules, SFP Modules, and Cables Can I Use with the X520 Series?

Link for more information.

ESX claim disk as SSD

Configuration:

esxcli storage nmp satp rule add --satp VMW_SATP_LOCAL --device mpx.vmbha0:C0:T0:L0 --option=enable_ssd

Application:

esxcli storage core claiming reclaim -d  mpx.vmbha0:C0:T0:L0 

or just restart ESXi  

Verification:

esxcli storage core device list --device=mpx.vmbha0:C0:T0:L0 

Force10 VLT terminology

For the terminology here are the items below to make sure we are on the same page. 

• VLT – is a combined Port-Channel (multiple physical interfaces) between the VLT Peer devices and the attached device.  These Port-channels can come from either a Host or another switch and are just regular Port-Channels (Static or Dynamic) which connect to the pair of VLT peer devices within the VLT Domain.
• VLT Port – is a physical port on a VLT device configured to be part of a VLT Domain.
• VLT peer device – is one of the pair of matching devises (today) that are connected with a Virtual Link Trunk Interconnect (VLTI)
• VLTI – Is the link used to synchronize states between the VLT peer devices.  Needs to be a Static Port-channel or there could be issues per the configuration Documentation and Engineering.

Prevent Logging for ARP-move logs in VLT Domains

Hello,

If you use a VLT Domain, then you will certainly see a lot of the following Messages in your Logging. %STKUNIT0-M:CP %ARPMGR-6-MAC_CHANGE: IP-4-ADDRMOVE

Station-move refers to an event where a host with an unique mac/IP combination is moved from one interface to another. ARP-move refers to an event where ARP entry for an IP address is moved from one Mac (say mac1) to another (mac2). FTOS logs such ARP move message.  

Example: %STKUNIT0-M:CP %ARPMGR-6-MAC_CHANGE: IP-4-ADDRMOVE: IP address 10.1.3.10 is moved from MAC address 00:0c:29:18:ca:3c  to MAC address 00:50:56:aa:ed:6a

So it is a normal behavior but fills your Logging File with an unnecessary number of Messages. There is no way to prevent a single type of log message (ARP) from reporting.

But as you can see above ARP-move syslog is logged with severity-level of 6 (informational). So, if you don’t want to display above ARP-move logs set the logging severity option to 5 so that only logs with severity level 5 and below will be logged.

Commands:

sw1(conf)#logging console ?

<0-7>                   Logging severity level (default = 7)

alerts                  Immediate action needed           (severity=1)

critical                Critical conditions               (severity=2)

debugging               Debugging messages                (severity=7)

emergencies             System is unusable                (severity=0)

errors                  Error conditions                  (severity=3)

informational           Informational messages            (severity=6)

notifications           Normal but significant conditions (severity=5)

warnings                Warning conditions                (severity=4)

<cr>

sw1(conf)#logging console 5     << for console line.

sw1(conf)#logging monitor 5     << for terminal line

sw1(conf)#logging history 5     << for syslog history table

sw1(conf)#logging trap 5        << for syslog

sw1(conf)#logging buffered 5    << for buffer

VSAN performance monitoring and tunning

Ruby vSphere Console (rvc)

• http://blogs.vmware.com/vsphere/2014/07/managing-vsan-ruby-vsphere-console.html
• https://blogs.vmware.com/vsphere/2014/08/managing-virtual-san-rvc-part-2-navigating-vsphere-virtual-san-infrastructure-rvc.html

VSAN Observer

• http://vmexplorer.com/2014/09/16/vsan-setting-up-vsan-observer-in-my-home-lab/