Is it normal (harmless) that HA Po1 ints appear in new vlan data?

[jmaxwellUSAF]

Hello. (obfuscated)...

Nexus-9300-1# sh int p100
port-channel100 is up
admin state is up,
Description: vPC Peer Link to Nexus9300-2
Port mode is trunk
Auto-mdix is turned off
Switchport monitor is off
Members in this channel: Eth1/13, Eth1/14
--

Nexus-9300-1#sh vlan
18 VLAN0018 active Po100, Eth1/13, Eth1/14, Eth 101/1/8

--
Questions:

1. Is it normal (harmless) that Po100, Eth1/13, Eth1/14 are appearing in new vlan 18, because that merely reveals that the new vlan 18 with only new e101/1/8 is now being included in the P100 redundency traffic between the 2 Nexus9300s?

2. So I'm not breaking anything with my creation of new vlan 18 with the single e101/1/8 port added?

Thank you!

[MHM Cisco World · Accepted solution]

 it is normal 
I run my lab and see same 
in VLAN you can see PO and port member 

one more point the NSK have special feature called force, 
this feature make any confing PO is forced add to all other port member  

[Reza Sharifi]

Since you have a trunk port between the switches for vPC peering (the way it should be) any new vlan you create will be added to the trunk. 

HTH