The vPC Peer-Switch feature allows a pair of vPC peer devices to appear as a single logical Spanning Tree Protocol root. With vPC Peer-Switch enabled downstream devices see both switches as the STP root. Without vPC Peer-Switch enabled downstream devices still have to funnel Layer 2 traffic via the STP root using the traditional STP traffic flow. The main advantage of vPC peer-swtich is the improvement in term of convergence time during vPC primary peer device failure/recovery. Without vPC peer-switch feature vPC primary peer device failure and recovery can create around 3 seconds of traffic disruption With vPC peer-switch traffic disruption is lowered to sub-second value This is since peer device down an up events do not generate any Rapid Spanning Tree Protocol Sync behavior, because, there is no logical change in the L2 topology. Things to keep in mind: It is a Cisco recommended best practice to activate vPC peer-switch within a vPC environment. vPC peer-swit...
Before following these steps you need to have a token for the API stored in Postman. The process for this can be found here . Creating the Tenant Right Click on your Collection Name (Cisco ACI Sandbox in my case), and click "Add Request" Right Click on your Collection Name (Cisco ACI Sandbox in my case), and click "Add Request" There are a couple steps in this piece: Name the Request "Create Tenant". Change the yype of request from GET to POST, since we're pushing a configuration. You can use the following URL to test against the sandbox, but you can change the hostname to your own APIC. https:// sandboxapicdc.cisco.com /api/mo/uni.json 4. Lastly in the Body you want to put the following JSON in place, and edit the name to whatever you'd like it to be. { "fvTenant" : { "attributes" : { "name" : " DBTN-Tenant " } } } 5. and finally, Click "Send" Now we will want to valid...
Netmon is an "Easy" difficulty Machine on hackthebox.eu First Step: Nmap Scan of the Machine nmap -n -v -Pn -p- -A --reason -oN netmon-10.10.10.152.txt 10.10.10.152 Pretty clearly a Windows Machine. Primary areas of opportunity: FTP/21, HTTP/80, SMB/445 21/tcp open ftp syn-ack ttl 127 Microsoft ftpd 80/tcp open http syn-ack ttl 127 Indy httpd 18.1.37.13946 (Paessler PRTG bandwidth monitor) 135/tcp open msrpc syn-ack ttl 127 Microsoft Windows RPC 139/tcp open netbios-ssn syn-ack ttl 127 Microsoft Windows netbios-ssn 445/tcp open microsoft-ds syn-ack ttl 127 Microsoft Windows Server 2008 R2 - 2012 microsoft-ds 5985/tcp open http syn-ack ttl 127 Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP) 47001/tcp open http syn-ack ttl 127 Microsoft HTTPAPI httpd 2.0 (SSDP/UPnP) 49664/tcp open msrpc syn-ack ttl 127 Microsoft Windows RPC 49665/tcp open msrpc syn-ack ttl 127 Microsoft Windows RPC 4...
Comments
Post a Comment