sh buffers input-interface <interface> packet
sh interface switching
sh interface stat
sh ip protocols
sh cef int x/y

---

switch#debug ethernet-controller address


term exec prompt timestamp <-- yay.

turn off with 'term no exec prompt timestamps'

does this:

Inuyasha#sh ver | inc (IOS|Time)
Time source is NTP, 15:15:42.947 UTC Wed May 10 2006
IOS (tm) RSP Software (RSP-PV-M), Version 12.2(18)S5,  RELEASE SOFTWARE (fc1)

---

N*(N-1)/2 = full mesh peering

255 * .% = load

^[0-9]+$ - any connected as
^[0-9]+(_[0-9]+)?$ - any connected as plus its customers

sh ip bgp neighbor x.x.x.x advertise

med/as_path <--- to AS
weight/local pref ---> from AS

sh ip bgp regex ...

----

AF to decmial - (8x)+(2y) AF31=26

32  16   8 |  4   2   1
0    0   0 |  0   0   0
-----------------------
4    2   1 |  2   1   x
class      | drop probility

vlan dot1q tag native

frf.12 LFI fragsize = max delay * bandwidth

255*.% = load

sh ip ospf broder router

SEC-6-IPACCESSLOGP - TCP and UDP
SEC-6-IPACCESSLOGNP - IP and any other remaining protocols
SEC-6-IPACCESSLOGDP - ICMP
SEC-6-IPACCESSLOGS - Standard access-list entry without any protcol
SEC-6-IPACCESSLOGRP - GRE, IGMP, OSPF, IGRP, NOSIP, NEWIGRP, IPINIP, PIM

Inuyasha(config)#ip tcp path-mtu-discovery
Inuyasha(config)#exit
Inuyasha#sh ip bgp nei | include max data
Datagrams (max data segment is 536 bytes):
Datagrams (max data segment is 4430 bytes):
Datagrams (max data segment is 4430 bytes):
Datagrams (max data segment is 1460 bytes):
Inuyasha#

The SNMP-SERVER  HOST  command specifies which hosts will receive SNMP
notifications, and whether you want the notifications sent as traps or
inform requests.

The SNMP-SERVER ENABLE TRAPS command globally enables the production
mechanism for the specified notification types (such as Border Gateway
Protocol [BGP] traps, config traps, entity traps, Hot Standby Router
Protocol [HSRP] traps, and so on).


-----

In the future you can test for a space by using the below method:

nopants(config-if)#ip os message-digest-key 2 md5 CISCO2 <-space
nopants(config-if)#^Z
nopants#sho run | include CISCO2$
nopants#sho run | include CISCO2 $
ip ospf message-digest-key 2 md5 CISCO2
nopants#

As you can see the regular expression was able to detect the space at
the end of the password.

----

If summary route is announced to BB router, there is no way to find if
it
work or not.

It would actually be really easy to test.  Just create a loopback
interface (or use an existing interface) that has an IP address in part
of the summarized range and then ping the BB router sourcing the ping
off of the loopback (or existing interface).  If you get a reply to the
ping, you will know that the BB is receiving the summarized route.

---

route tagging, circullar topology:

OSPF <-> RIP OSPF tag 10, RIP tag 20

|\ |   Set tag 10 out, deny tag 20 in
|  |
|  |/  Set tag 20 out, deny tag 10 in

inverse on second side


even RTP ports 16384-32767/UDP
odd totaly RTP port range -> 16383
ip rtp priority 16384 (start) 15383 (range) 256 (bandwidth)