Showing posts with label Command Reference. Show all posts
Showing posts with label Command Reference. Show all posts

Monday, June 27, 2016

Sending an F11 to ESXi from a Macbook Pro when using RDP to a Windows system for installation

Many more irritating moments spent wishing I had written this down somewhere.

I work remotely much of the time.  I'm currently reinstalling ESXi on a number of hosts and using a workstation located on the LAN of my office to hold the install ISO.  I'm accessing it via RDP from a Mac connected by VPN.  I have configured my Mac to use F-keys in a more traditional manner like I recorded in this post, but for some reason the F11 would show the desktop instead of actually instructing the ESXi installation to continue.

The secret key sequence is:

Command+F11

I don't know what it is about the Mac that makes it behave like this, but I'm tired of wasting time searching for this answer.  I hope I remember it now...

Tuesday, December 1, 2015

Sending that pesky F11 to ESXi through a Mac

OK, the alternative method I've just discovered is to go to the keyboard settings under System Preferences and check the box that says:

Use all F1, F2, etc. keys as standard function keys.

This worked today.  We'll see what happens tomorrow.

Friday, February 20, 2015

Data Domain CLI commands

In the process of replicating data from a DD640 to DD2500 and we're hitting capacity issues.  The Data Domain locks data and won't allow cleaning to have access when it is replicating.

So...

I cancelled replication and manually started cleaning.  Last night there was no decrease in data size once cleaning finished.  I'm running it again today manually.  The commands of the day are:

#filesys clean stat

which displays the current condition of the cleaning, such as:

DD640# filesys clean status
Cleaning started at 2015/02/20 09:00:50: phase 1 of 10 (pre-enumeration)
  2.5% complete,  1130 GiB free; time: phase  0:57:55, total  0:57:57

Which is nice, but when you're as retentive as me, you want real-time info on the condition.  That's when we use:

filesys clean watch

That will present real-time, updating status of the cleaning job, such as:

DD640# filesys clean watch
Beginning 'filesys clean' monitoring.  Use Control-C to stop monitoring.

Cleaning: phase 1 of 10 (pre-enumeration)
    3.4% complete,  1130 GiB free; time: phase  1:24:26, total  1:24:28

I also allocated more resources to the cleaning in hope that it gets finished sooner than later.  I'm not running any backup during the day to speak of, so I can afford to let those jobs take a back seat to the emergency maintenance.

More as it happens...

Wednesday, August 14, 2013

Troubleshooting Command Blitz

#show controllers serial 0/0
Shows clock rate and DCE/DTE

#show ip interfaces brief
Shows ip addresses, L1/L2 status

#debug ip nat
shows source IP->NAT IP, destination IP and time

#show ip nat translations
shows static nat with inside global, inside local and outside local/global

#show ip nat translations
shows inside and outside interfaces, hits and ACL number

#show ip route
Shows routing table, with indication of how route was learned

#sho ip protocols
info about routing protocols running on router, including interfaces included, networks being routed

#debug ip rip
shows updates, routing table being sent, flash or regular

#debug ip ospf
shows hello, timers, new adjacency

#sho ip ospf neighbor (no "s" at the end)
sho ID of neighbor routers, dead timers, neighbor IP and interface route was learned on (local)

#sho ip ospf database
Shows link states for neighbor (advertising) router, along with the age

#show ip ospf interface serial 0/0
Shows whether or not ospf is running on this interface, process ID, router ID, neighbor counts

# sho ip eigrp neighbors (note - add "s" to eigrp)
Shows address and receiving interface, hold timers,

#show ip eigrp topology
Shows routes in topology table, receiving interface and feasible distance

#sho ip eigrp interfaces
Which interfaces are participating in the eigrp AS

#show cdp neighbors
Connected Cisco devices, local interface they are connected on, capability of the devices, plaform and which port on the connected device

#sho cdp neighbors detail
 Also shows IOS version

#sho ip dhcp binding
Who received an IP address from our pool

#ping 192.168.1.1
U.U.U means that the packet is being blocked by an ACL

#show ip access-lists
#sho access-lists
Both do the same thing, show access lists and hits

#show interface serial 0/0
Find WAN encapsulation type, condition of line

#debug ppp packet
PPP negotiation, state, authentication and errors

#show frame-relay map
interface, IP address and DLCI

#sho frame-relay PVC
statistics for FR

#sho frame-relay lmi
LMI type, send/receive of status updates

#debug frame-relay lmi
shows LMI info, watch for "myseq" and "yourseq" incrementing, "status 0x2" means FR is operational

#show vlans
Which switch interfaces are included in which vlan - a missing interface indicates it is a trunk

#show interfaces trunk
Shows ports that are trunking, their status, encapsulation type and allowed vlans

#show vtp status
version, operating mode, domain name, config revision number

#show vtp password
--self-explanatory





Thursday, July 18, 2013

Random ACL thoughts and things I want to remember

Some thoughts on ACLs, as well as some commands to review:

distribute-list <#> [ in | out] - permit or deny routing protocols from adding a network into the routes propagated

Standard ACLs:  1-99, 1300-1999
Extended ACLs:  100-199, 2000-2699

A Cisco router removes the host inverse mask (0.0.0.0) from an ACL when doing a show running-config, because anything without a mask is assumed to be a host.

Apply standard ACLs on the interface closest to the destination.

An empty ACL allows all traffic.

When working on a router or firewall remotely, start with the reload in command to reload the device  autmatically in case an error is made and everyone is locked out.  Then cancel the reload to remove the reload command before the timer is up if everything is working correctly:

reload in 5
reload cancel


When configuring extended ACLs, be cautious about the source port and its placement.  Entering port numbers after the source IP, you only filter that source port.  Leaving source port information off the ACL means to assume all source ports

Best practice is to apply extended ACLs on the interface closest to the source.  This is directly contrary to the best practice for standard ACLs.

(Standard near destination, Extended near source)

Use the established keyword to allow any packets with an ACK or RST through.  This is commonly applied on the Internet interface inbound to allow any sessions initiated from the LAN back through the router.

A named ACL can have a single line deleted without removing the entire ACL.  One major difference is that the named list must be prepended with the ip keyword.

A Cisco router creates entries in a named ACL starting at line number 10 and incrementing by 10.

resequence allows you to move an ACL line from one number to another.

More thoughts as they come to me...

Show commands for ACLs

Some "show" commands for quick reference:

show ip interface  -  IP settings, ACLs applied, NAT configuration

show int - Interface config, stats, encapsulation, errors at L2

show access-lists, show ip access-lists - simply list ACLs, these are the same