![]() |
Cisco IOS IP Addressing Services Command Reference
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
show ip masks through vrf DHCP pool
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Contents
show ip masks through vrf DHCP pool show ip masksTo display the masks used for network addresses and the number of subnets using each mask, use the show ip masks command in EXEC mode. Command History
show ip nat nvi statisticsTo display NAT virtual interface (NVI) statistics, use the show ip nat nvi statisticscommand in user EXEC or privileged EXEC mode. ExamplesThe following is sample output from the show ip nat nvi statistics command:
Router# show ip nat nvi statistics
Total active translations: 0 (0 static, 0 dynamic; 0 extended) NAT Enabled interfaces:
Hits: 0 Misses: 0
CEF Translated packets: 0, CEF Punted packets: 0 Expired translations: 0 Dynamic mappings:
-- Inside Source
[Id: 1] access-list 1 pool pool1 refcount 1213 pool pool1: netmask 255.255.255.0
start 192.168.1.10 end 192.168.1.253
start 192.168.2.10 end 192.168.2.253
start 192.168.3.10 end 192.168.3.253
start 192.168.4.10 end 192.168.4.253
type generic, total addresses 976, allocated 222 (22%), misses 0
[Id: 2] access-list 5 pool pool2 refcount 0 pool pool2: netmask 255.255.255.0
start 192.168.5.2 end 192.168.5.254
type generic, total addresses 253, allocated 0 (0%), misses 0
[Id: 3] access-list 6 pool pool3 refcount 3 pool pool3: netmask 255.255.255.0
start 192.168.6.2 end 192.168.6.254
type generic, total addresses 253, allocated 2 (0%), misses 0
[Id: 4] access-list 7 pool pool4 refcount 0 pool pool4 netmask 255.255.255.0
start 192.168.7.30 end 192.168.7.200
type generic, total addresses 171, allocated 0 (0%), misses 0
[Id: 5] access-list 8 pool pool5 refcount 109195 pool pool5: netmask 255.255.255.0
start 192.168.10.1 end 192.168.10.253
start 192.168.11.1 end 192.168.11.253
start 192.168.12.1 end 192.168.12.253
start 192.168.13.1 end 192.168.13.253
start 192.168.14.1 end 192.168.14.253
start 192.168.15.1 end 192.168.15.253
start 192.168.16.1 end 192.168.16.253
start 192.168.17.1 end 192.168.17.253
start 192.168.18.1 end 192.168.18.253
start 192.168.19.1 end 192.168.19.253
start 192.168.20.1 end 192.168.20.253
start 192.168.21.1 end 192.168.21.253
start 192.168.22.1 end 192.168.22.253
start 192.168.23.1 end 192.168.23.253
start 192.168.24.1 end 192.168.24.253
start 192.168.25.1 end 192.168.25.253
start 192.168.26.1 end 192.168.26.253
type generic, total addresses 4301, allocated 3707 (86%),misses 0 Queued Packets:0
The table below describes the fields shown in the display.
show ip nat nvi translationsTo display active NAT virtual interface (NVI) translations, use the show ip nat nvi translations command in user EXEC or privileged EXEC mode. Syntax DescriptionExamplesThe following is sample output from the show ip nat nvi translations command:
Router# show ip nat nvi translations
Pro Source global Source local Destin local Destin global
icmp 172.20.0.254:25 172.20.0.130:25 172.20.1.1:25 10.199.199.100:25
icmp 172.20.0.254:26 172.20.0.130:26 172.20.1.1:26 10.199.199.100:26
icmp 172.20.0.254:27 172.20.0.130:27 172.20.1.1:27 10.199.199.100:27
icmp 172.20.0.254:28 172.20.0.130:28 172.20.1.1:28 10.199.199.100:28
The table below describes the fields shown in the display. show ip nat statisticsTo display Network Address Translation ( NAT) statistics, use the show ip nat statisticscommand in EXEC mode. Command History
ExamplesThe following is sample output from the show ip nat statisticscommand:
Router# show ip nat statistics
Total translations: 2 (0 static, 2 dynamic; 0 extended)
Outside interfaces: Serial0
Inside interfaces: Ethernet1
Hits: 135 Misses: 5
Expired translations: 2
Dynamic mappings:
-- Inside Source
access-list 1 pool net-208 refcount 2
pool net-208: netmask 255.255.255.240
start 172.16.233.208 end 172.16.233.221
type generic, total addresses 14, allocated 2 (14%), misses 0
The table below describes the significant fields shown in the display.
Related Commands
show ip nat translationsTo display active Network Address Translation ( NAT) translations, use the show ip nat translationscommand inEXEC mode.
show
ip
nat
translations
[inside global-ip]
[outside local-ip]
[esp]
[icmp]
[pptp]
[tcp]
[udp]
[verbose]
[vrf vrf-name]
Syntax Description
Command History
ExamplesThe following is sample output from the show ip nat translations command. Without overloading, two inside hosts are exchanging packets with some number of outside hosts.
Router# show ip nat translations
Pro Inside global Inside local Outside local Outside global
--- 10.69.233.209 192.168.1.95 --- ---
--- 10.69.233.210 192.168.1.89 --- --
With overloading, a translation for a Domain Name Server (DNS) transaction is still active, and translations for two Telnet sessions (from two different hosts) are also active. Note that two different inside hosts appear on the outside with a single IP address.
Router# show ip nat translations
Pro Inside global Inside local Outside local Outside global
udp 10.69.233.209:1220 192.168.1.95:1220 172.16.2.132:53 172.16.2.132:53
tcp 10.69.233.209:11012 192.168.1.89:11012 172.16.1.220:23 172.16.1.220:23
tcp 10.69.233.209:1067 192.168.1.95:1067 172.16.1.161:23 172.16.1.161:23
The following is sample output that includes the verbose keyword:
Router# show ip nat translations verbose
Pro Inside global Inside local Outside local Outside global
udp 172.16.233.209:1220 192.168.1.95:1220 172.16.2.132:53 172.16.2.132:53
create 00:00:02, use 00:00:00, flags: extended
tcp 172.16.233.209:11012 192.168.1.89:11012 172.16.1.220:23 172.16.1.220:23
create 00:01:13, use 00:00:50, flags: extended
tcp 172.16.233.209:1067 192.168.1.95:1067 172.16.1.161:23 172.16.1.161:23
create 00:00:02, use 00:00:00, flags: extended
The following is sample output that includes the vrf keyword: Router# show ip nat translations vrf abc Pro Inside global Inside local Outside local Outside global --- 10.2.2.1 192.168.121.113 --- --- --- 10.2.2.2 192.168.122.49 --- --- --- 10.2.2.11 192.168.11.1 --- --- --- 10.2.2.12 192.168.11.3 --- --- --- 10.2.2.13 172.16.5.20 --- --- Pro Inside global Inside local Outside local Outside global --- 10.2.2.3 192.168.121.113 --- --- --- 10.2.2.4 192.168.22.49 --- --- The following is sample output that includes the esp keyword:
Router# show ip nat translations esp
Pro Inside global Inside local Outside local Outside global
esp 192.168.22.40:0 192.168.122.20:0 192.168.22.20:0 192.168.22.20:28726CD9
esp 192.168.22.40:0 192.168.122.20:2E59EEF5 192.168.22.20:0 192.168.22.20:0
The following is sample output that includes the esp and verbose keywords:
Router# show ip nat translation esp verbose
Pro Inside global Inside local Outside local Outside global
esp 192.168.22.40:0 192.168.122.20:0 192.168.22.20:0 192.168.22.20:28726CD9
create 00:00:00, use 00:00:00,
flags:
extended, 0x100000, use_count:1, entry-id:192, lc_entries:0
esp 192.168.22.40:0 192.168.122.20:2E59EEF5 192.168.22.20:0 192.168.22.20:0
create 00:00:00, use 00:00:00, left 00:04:59, Map-Id(In):20,
flags:
extended, use_count:0, entry-id:191, lc_entries:0
The following is sample output that includes the insidekeyword:
Router# show ip nat translations inside 10.69.233.209
Pro Inside global Inside local Outside local Outside global
udp 10.69.233.209:1220 192.168.1.95:1220 172.16.2.132:53 172.16.2.132:53
The table below describes the significant fields shown in the display. Related Commands
show ip nhrpTo display Next Hop Resolution Protocol (NHRP) mapping information, use the show ip nhrp command in user EXEC or privileged EXEC mode.
show
ip
nhrp
[dynamic | incomplete | static]
[address | interface]
[brief | detail]
[purge]
[shortcut]
Syntax Description
Command History
Usage GuidelinesThe table below lists the valid types, number ranges, and descriptions for the optional interface argument.
ExamplesThe following is sample output from the show ip nhrpcommand. This output shows the NHRP group received from the spoke:
Router# show ip nhrp
10.0.0.2/32 via 10.0.0.2, Tunnel0 created 00:17:49, expire 00:01:30
Type: dynamic, Flags: unique registered used
NBMA address: 172.17.0.2
Group: test-group-0
10.0.0.3/32 via 10.0.0.3, Tunnel0 created 00:00:11, expire 01:59:48
Type: dynamic, Flags: unique registered used
NBMA address: 172.17.0.3
Group: test-group-0
11.0.0.2/32 via 11.0.0.2, Tunnel1 created 00:17:49, expire 00:02:10
Type: dynamic, Flags: unique registered used
NBMA address: 172.17.0.2
Group: test-group-1
The following is sample output from the show ip nhrp shortcut command:
Router#show ip nhrp shortcut
10.1.1.1/24 via 1.1.1.22 Tunnel0 created 00:00:05, expire 00:02:24
Type: dynamic, Flags: router rib
NBMA address: 10.12.1.1
10.1.1.2/24 via 1.1.1.22 Tunnel0 created 00:00:05, expire 00:02:24
Type: dynamic, Flags: router rib nho
NBMA address: 10.12.1.2
The following is sample output from the show ip nhrp detailcommand:
Router# show ip nhrp detail
10.1.1.1/8 via 10.2.1.1, Tunnel1 created 00:46:29, never expire
Type: static, Flags: used
NBMA address: 10.12.1.1
10.1.1.2/8 via 10.2.1.2, Tunnel1 created 00:00:12, expire 01:59:47
Type: dynamic, Flags: authoritative unique nat registered used
NBMA address: 10.12.1.2
10.1.1.4, Tunnel1 created 00:00:07, expire 00:02:57
Type: incomplete, Flags: negative
Cache hits: 4
The table below describes the significant fields shown in the displays. Related Commands
show ip nhrp group-mapTo display the details of NHRP group mappings, use the show ip nhrp group-mapcommand in user EXEC or privileged EXEC mode. Usage GuidelinesThis command displays the details on NHRP group mappings on the hub along with the list of tunnels using each of the NHRP groups defined in the mappings. In combination with the show ip nhrp command, this command lets you easily determine which QoS policy map is applied to a specific tunnel endpoint. This command displays the details of the specified NHRP group mapping. The details include the associated QoS policy name and the list of tunnel endpoints using the QoS policy. If no option is specified, it displays the details of all NHRP group mappings. ExamplesThe following is sample output from the show ip nhrp group-mapcommand:
Router# show ip nhrp group-map
Interface: Tunnel0
NHRP group: test-group-0
QoS policy: queueing
Tunnels using the QoS policy:
Tunnel destination overlay/transport address
10.0.0.2/172.17.0.2
10.0.0.3/172.17.0.3
Interface: Tunnel1
NHRP group: test-group-1
QoS policy: queueing
Tunnels using the QoS policy:
Tunnel destination overlay/transport address
11.0.0.2/172.17.0.2
NHRP group: test-group-2
QoS policy: p1
Tunnels using the QoS policy: None
The following is sample output from the show ip nhrp group-mapcommand for an NHRP group named test-group-0:
Router# show ip nhrp group-map test-group-0
Interface: Tunnel0
NHRP group: test-group-0
QoS policy: queueing
Tunnels using the QoS policy:
Tunnel destination overlay/transport address
10.0.0.2/172.17.0.2
10.0.0.3/172.17.0.3
The table below describes the significant fields shown in the displays.
Related Commands
show ip nhrp multicastTo display Next Hop Resolution Protocol (NHRP) multicast mapping information, use the show ip nhrp multicastcommand in user EXEC or privileged EXEC mode. Usage GuidelinesThe table below lists the valid types, number ranges, and descriptions for the optional interface argument.
ExamplesThe following is sample output from the show ip nhrp multicastcommand:
Router# show ip nhrp multicast
I/F NBMA address
Tunnel1 1.1.1.1 Flags: static
The table below describes the fields shown in the display.
Related Commands
show ip nhrp nhsTo display Next Hop Resolution Protocol (NHRP) next hop server (NHS) information, use the show ip nhrp nhscommand in user EXEC or privileged EXEC mode. Command History
Usage GuidelinesThe table below lists the valid types, number ranges, and descriptions for the optional interfaceargument.
ExamplesThe following is sample output from the show ip nhrp nhs detail command:
Router# show ip nhrp nhs detail
Legend:
E=Expecting replies
R=Responding
Tunnel1:
5.1.1.1 E req-sent 128 req-failed 1 repl-recv 0
Pending Registration Requests:
Registration Request: Reqid 1, Ret 64 NHS 5.1.1.1
The table below describes the significant field shown in the display. Related Commands
show ip nhrp summaryTo display Next Hop Resolution Protocol (NHRP) mapping summary information, use the show ip nhrp summarycommand in user EXEC or privileged EXEC mode. Command History
ExamplesThe following is sample output from the show ip nhrp summary command:
Router# show ip nhrp summary
IP NHRP cache 1 entry, 256 bytes
1 static 0 dynamic 0 incomplete
The table below describes the significant field shown in the display.
Related Commands
show ip nhrp trafficTo display Next Hop Resolution Protocol (NHRP) traffic statistics, use the show ip nhrp trafficcommand in privileged EXEC mode. show ip nhrp traffic [interface tunnel number] Command History
ExamplesThe following example shows output for a specific tunnel, tunnel0: Router# show ip nhrp traffic interface tunnel0 Tunnel0: Max-send limit:100Pkts/10Sec, Usage:0% Sent: Total 79 18 Resolution Request 10 Resolution Reply 42 Registration Request 0 Registration Reply 3 Purge Request 6 Purge Reply 0 Error Indication 0 Traffic Indication Rcvd: Total 69 10 Resolution Request 15 Resolution Reply 0 Registration Request 36 Registration Reply 6 Purge Request 2 Purge Reply 0 Error Indication 0 Traffic Indication The table below describes the significant fields shown in the display.
show ip route dhcpTo display the routes added to the routing table by the Dynamic Host Configuration Protocol (DHCP) server and relay agent, use the show ip route dhcp command in privileged EXEC configuration mode. Command History
Usage GuidelinesTo display information about global routes, use the show ip route dhcp command. To display routes in the VRF routing table, use the show ip route vrf vrf-name dhcp command. ExamplesThe following is sample output from the show ip route dhcpcommand when entered without an address. This command lists all routes added by the DHCP server and relay agent.
Router# show ip route dhcp
10.5.5.56/32 is directly connected, ATM0.2
10.5.5.217/32 is directly connected, ATM0.2
The following is sample output from the show ip route dhcp command when an address is specified. The output shows the details of the address with the server address (who assigned it) and the lease expiration time.
Router# show ip route dhcp 10.5.5.217
10.5.5.217 is directly connected, ATM0.2
DHCP Server: 10.9.9.10 Lease expires at Nov 08 2001 01:19 PM
The following is sample output from the show ip route vrf vrf-name dhcpcommand when entered without an address:
Router# show ip route vrf abc dhcp
10.5.5.218/32 is directly connected, ATM0.2
The following is sample output from the show ip route vrf vrf-name dhcpcommand when an address is specified. The output shows the details of the address with the server address (who assigned it) and the lease expiration time.
Router# show ip route vrf red dhcp 10.5.5.218
10.5.5.218/32 is directly connected, ATM0.2
DHCP Server: 10.9.9.10 Lease expires at Nov 08 2001 03:15PM
show ip snatTo display active Stateful Network Address Translation (SNAT) translations, use the show ip snat command in EXEC mode. Syntax Description
ExamplesThe following is sample output from the show ip snat distributed command for stateful NAT connected peers:
Router# show ip snat distributed
Stateful NAT Connected Peers
SNAT: Mode PRIMARY
:State READY
:Local Address 192.168.123.2
:Local NAT id 100
:Peer Address 192.168.123.3
:Peer NAT id 200
:Mapping List 10
The following is sample output from the show ip snat distributed verbosecommand for stateful NAT connected peers:
Router# show ip snat distributed verbose
SNAT: Mode PRIMARY
Stateful NAT Connected Peers
:State READY
:Local Address 192.168.123.2
:Local NAT id 100
:Peer Address 192.168.123.3
:Peer NAT id 200
:Mapping List 10
:InMsgs 7, OutMsgs 7, tcb 0x63EBA408, listener 0x0
show ip source bindingTo display IP-source bindings configured on the system, use the show ip source command command in privileged EXEC mode.
show
ip
source
binding
[ip-address]
[mac-address]
[dhcp-snooping | static]
[vlan vlan-id]
[interface type mod/port]
Syntax Description
ExamplesThis example shows the output without entering any keywords: Router# show ip source binding MacAddress IpAddress Lease(sec) Type VLAN Interface ------------------ --------------- ---------- ------------- ---- -------------------- 00:00:00:0A:00:0B 17.16.0.1 infinite static 10 FastEthernet6/10 00:00:00:0A:00:0A 17.16.0.2 10000 dhcp-snooping 10 FastEthernet6/11 This example shows how to display the static IP binding entry for a specific IP address:
Router# show ip source binding 17.16.0.1 0000.000A.000B static vlan 10 interface gigabitethernet6/10
MacAddress IpAddress Lease(sec) Type VLAN Interface
------------------ --------------- ---------- ------------- ---- --------------------
00:00:00:0A:00:0B 17.16.0.1 infinite static 10 FastEthernet6/10
The table below describes the significant fields in the display.
show ip verify sourceTo display the IP source guard configuration and filters on a particular interface, use the show ip verify source command in EXEC mode. Syntax Description
Usage GuidelinesEnable port security first because the DHCP security MAC filter cannot apply to the port or VLAN. ExamplesThis example shows the display when DHCP snooping is enabled on VLANs 10 to 20, the interface has IP source filter mode that is configured as IP, and there is an existing IP address binding 10.0.0.1 on VLAN 10:
Router# show ip verify source interface gigabitethernet6/1
Interface Filter-type Filter-mode IP-address Mac-address Vlan
--------- ----------- ----------- --------------- -------------- ---------
gi6/1 ip active 10.0.0.1 10
gi6/1 ip active deny-all 11-20
This example shows how to display the IP source guard configuration and filters on a specific interface:
Router# show ip verify source interface gigabitethernet6/1
Interface Filter-type Filter-mode IP-address Mac-address Vlan
--------- ----------- ----------- --------------- -------------- ---------
gi6/1 ip inactive-trust-port
This example shows the display when the interface does not have a VLAN enabled for DHCP snooping:
Router# show ip verify source interface gigabitethernet6/3
Interface Filter-type Filter-mode IP-address Mac-address Vlan
--------- ----------- ----------- --------------- -------------- ---------
gi6/3 ip inactive-no-snooping-vlan
This example shows the display when the interface has an IP source filter mode that is configured as IP MAC and an existing IP MAC binds 10.0.0.2/aaaa.bbbb.cccc on VLAN 10 and 10.0.0.1/aaaa.bbbb.cccd on VLAN 11:
Router# show ip verify source interface gigabitethernet6/4
Interface Filter-type Filter-mode IP-address Mac-address Vlan
--------- ----------- ----------- --------------- -------------- ---------
gi6/4 ip-mac active 10.0.0.2 aaaa.bbbb.cccc 10
gi6/4 ip-mac active 10.0.0.1 aaaa.bbbb.cccd 11
gi6/4 ip-mac active deny-all deny-all 12-20
This example shows the display when the interface has an IP source filter mode that is configured as IP MAC and an existing IP MAC binding 10.0.0.3/aaaa.bbbb.ccce on VLAN 10, but port security is not enabled on the interface:
Router# show ip verify source interface gigabitethernet6/5
Interface Filter-type Filter-mode IP-address Mac-address Vlan
--------- ----------- ----------- --------------- -------------- ---------
gi6/5 ip-mac active 10.0.0.3 permit-all 10
gi6/5 ip-mac active deny-all permit-all 11-20
This example shows the display when the interface does not have IP source filter mode configured:
Router# show ip verify source interface gigabitethernet6/6
DHCP security is not configured on the interface gi6/6.
This example shows how to display all the interfaces on the switch that have DHCP snooping security enabled:
Router# show ip verify source
Interface Filter-type Filter-mode IP-address Mac-address Vlan
--------- ----------- ----------- --------------- -------------- ---------
gi6/1 ip active 10.0.0.1 10
gi6/1 ip active deny-all 11-20
gi6/2 ip inactive-trust-port
gi6/3 ip inactive-no-snooping-vlan
gi6/4 ip-mac active 10.0.0.2 aaaa.bbbb.cccc 10
gi6/4 ip-mac active 11.0.0.1 aaaa.bbbb.cccd 11
gi6/4 ip-mac active deny-all deny-all 12-20
gi6/5 ip-mac active 10.0.0.3 permit-all 10
gi6/5 ip-mac active deny-all permit-all 11-20
Router#
This example shows how to display all the interfaces on the switch that have DHCP snooping security enabled:
Router# show ip verify source interface gi5/0/0 efp_id 10
Interface Filter-type Filter-mode IP-address Mac-address Vlan EFP ID
--------- ----------- ----------- --------------- ----------------- ---------- ----------
Gi5/0/0 ip-mac active 123.1.1.1 00:0A:00:0A:00:0A 100 10
Gi5/0/0 ip-mac active 123.1.1.2 00:0A:00:0A:00:0B 100 20
Gi5/0/0 ip-mac active 123.1.1.3 00:0A:00:0A:00:0C 100 30
show logging ip access-listTo display information about the logging IP access list, use the show logging ip access-list command in privileged EXEC mode. Usage GuidelinesThis command is supported on Cisco 7600 series routers that are configured with a Supervisor Engine 720 only. OAL is supported on IPv4 unicast traffic only. ExamplesThis example shows how to display all the entries in the OAL cache:
Router# show logging ip access-list cache
Matched flows:
id prot src_ip dst_ip sport dport status count
total lastlog
--------------------------------------------------------------------------------------
1 17 10.2.1.82 10.2.12.2 111 63 Permit 0
3906 2d02h
2 17 10.2.1.82 10.2.12.2 1135 63 Permit 0
3906 2d02h
3 17 10.2.1.82 10.2.12.2 2159 63 Permit 0
3906 2d02h
4 17 10.2.1.82 10.2.12.2 3183 63 Permit 0
3906 2d02h
5 17 10.2.1.82 10.2.12.2 4207 63 Permit 0
3906 2d02h
6 17 10.2.1.82 10.2.12.2 5231 63 Deny 0
3906 2d02h
7 17 10.2.1.82 10.2.12.2 6255 63 Deny 0
3906 2d02h
8 17 10.2.1.82 10.2.12.2 7279 63 Permit 0
3906 2d02h
9 17 10.2.1.82 10.2.12.2 8303 63 Permit 0
3906 2d02h
10 17 10.2.1.82 10.2.12.2 9327 63 Permit 0
3905 2d02h
11 17 10.2.1.82 10.2.12.2 10351 63 Permit 0
3905 2d02h
12 17 10.2.1.82 10.2.12.2 11375 63 Permit 0
3905 2d02h
13 17 10.2.1.82 10.2.12.2 12399 63 Deny 0
3905 2d02h
14 17 10.2.1.82 10.2.12.2 13423 63 Permit 0
3905 2d02h
15 17 10.2.1.82 10.2.12.2 14447 63 Deny 0
3905 2d02h
16 17 10.2.1.82 10.2.12.2 15471 63 Permit 0
3905 2d02h
17 17 10.2.1.82 10.2.12.2 16495 63 Permit 0
3905 2d02h
18 17 10.2.1.82 10.2.12.2 17519 63 Permit 0
3905 2d02h
19 17 10.2.1.82 10.2.12.2 18543 63 Permit 0
3905 2d02h
20 17 10.2.1.82 10.2.12.2 19567 63 Permit 0
3905 2d02h
Number of entries: 20
Number of messages logged: 112
Number of packets logged: 11200
Number of packets received for logging: 11200
This example shows how to display information about the logging IP access-list configuration:
Router# show logging ip access-list config
Logging ip access-list configuration
Maximum number of cached entries: 8192
Logging rate limiter: 0
Log-update interval: 300
Log-update threshold: 0
Configured on input direction:
Vlan2
Vlan1
Configured on output direction:
Vlan2
Related Commands
show nat64 adjacencyTo display information about the stateless Network Address Translation 64 (NAT64) managed adjacencies, use the show nat64 adjacency command in user EXEC or privileged EXEC mode. Usage GuidelinesAn adjacency is a node that can be reached by one Layer 2 hop. The stateless NAT64 adjacencies include adjacency addresses and the total number of adjacencies. ExamplesThe following is sample output from the show nat64 adjacency all command:
Router# show nat64 adjacency all
Adjacency Counts
IPv4 Adjacencies: 2
IPv6 Adjacencies: 1
Stateless Prefix Adjacency Ref Count: 1
Adjacencies
IPv6 Adjacencies
::42
IPv4 Adjacencies
0.0.19.137 (5001)
0.0.19.140 (5004)
The table below describes the significant fields shown in the display. show nat64 ha statusTo display information about the stateless Network Address Translation 64 (NAT64) high availability (HA) status, use the show nat64 ha statuscommand in user EXEC or privileged EXEC mode. ExamplesThe following is sample output from the show nat64 ha status command:
Router# show nat64 ha status
NAT64 HA Status
Role: active
Peer is ready: TRUE
Peer is compatible: TRUE
Synchronization enabled: TRUE
Is hot (standby): FALSE
Bulk sync PID: NO_PROCESS
ISSU negotiation status: IPC, CF
ISSU context IDs: IPC(198), CF(197)
Synchronization capabilities: 0x00000001
Adjacency mappings: TRUE
CF info: handle(0x0000011B), peer ready(TRUE),
flow control(TRUE)(FALSE)(0x0)
Initialized: HA(TRUE) ISSU(TRUE)
Message stats:
Adjacency mapping: rx(0) tx(5001) tx err(0)
Bulk sync done: rx(0) tx(1) tx err(0)
Errors:
Bulk sync: 0
CF tx: 0
The table below describes the significant fields shown in the display. show nat64 prefix statelessTo display information about the configured Network Address Translation 64 (NAT64) stateless prefixes, use the show nat64 prefix statelesscommand in user EXEC or privileged EXEC mode.
show
nat64
prefix
stateless
{global | {interfaces | static-routes} [prefix ipv6-prefix/prefix-length] }
Syntax Description
Usage GuidelinesThe output of the show nat64 prefix stateless command displays the interfaces that use a specific prefix and the number of prefixes that use a static route. ExamplesThe following is sample output from the show nat64 prefix stateless globalcommand:
Router# show nat64 prefix stateless global
Global Prefix: is valid, 2001::/96
IFs Using Global Prefix
Fa0/3/4
Fa0/3/5
The table below describes the significant fields shown in the display.
The following is sample output from the show nat64 prefix stateless interfacescommand.
Router# show nat64 prefix stateless interfaces
Interface NAT64 Enabled Global Stateless Prefix
FastEthernet0/3/4 TRUE FALSE 2001::/96
The table below describes the significant fields shown in the display.
The following is sample output from the show nat64 prefix stateless static-routescommand. The output fields are self-explanatory.
Router# show nat64 prefix stateless static-routes
Stateless Prefix Static Route Ref Count
2001::/96 1
show nat64 routesTo display information about the configured Network Address Translation 64 (NAT64) routes, use the show nat64 routescommand in privileged EXEC mode. Syntax Description
Usage GuidelinesThe output of the show nat64 routes command displays the stateless prefix and adjacency used by the routes and information on whether the routes are enabled. ExamplesThe following is sample output from the show nat64 routes command:
Router# show nat64 routes
IPv4 Prefix Adj. Address Enabled Output IF Global IPv6 Prefix
192.0.2.1/24 0.0.19.137 FALSE Fa0/3/4
198.51.100.253/24 0.0.19.140 TRUE Fa0/3/0 FALSE 3001::/96
The table below describes the significant fields shown in the display.
show nat64 statisticsTo display Network Address Translation 64 (NAT64) packet count statistics, use the show nat64 statisticscommand in user EXEC or privileged EXEC mode. Syntax Description
Usage GuidelinesThe output of the show nat64 statistics command displays the interfaces configured for stateless NAT64 and the packets that were translated or dropped. ExamplesThe following is sample output from the show nat64 statistics command:
Router# show nat64 statistics
NAT64 Statistics
Global Stats:
Packets translated (IPv4 -> IPv6): 21
Packets translated (IPv6 -> IPv4): 15
GigabitEthernet0/0/1 (IPv4 configured, IPv6 configured):
Packets translated (IPv4 -> IPv6): 5
Packets translated (IPv6 -> IPv4): 0
Packets dropped: 0
GigabitEthernet1/2/0 (IPv4 configured, IPv6 configured):
Packets translated (IPv4 -> IPv6): 0
Packets translated (IPv6 -> IPv4): 5
Packets dropped: 0
The table below describes the significant fields shown in the display. show nhrp debug-conditionTo display the Next Hop Resolution Protocol (NHRP) conditional debugging information, use the show nhrp debug-conditioncommand in privileged EXEC mode. ExamplesThe following is sample output from the show nhrp debug-condition command:
Router# show nhrp debug-condition
Peer NBMA addresses under debug are:
1.1.1.1,
Interfaces under debug are:
Tunnel1, Peer Tunnel addresses under debug are:
2.2.2.2,
The output if self-explanatory. It displays the conditional debugging information for NHRP. show platform hardware qfp featureTo display feature-specific information in the Cisco Quantum Flow Processor (QFP), use the show platform hardware qfp featurecommand in privileged EXEC mode.
show
platform
hardware
qfp
{active | standby}
feature
alg
{memory | statistics [protocol | clear [clear] ] }
Syntax Description
Usage GuidelinesThe show platform hardware qfp feature command when used withthe netbios keyworddisplays the NetBIOS ALG memory usage and statistics information of the processor. ExamplesThe following example displays the NetBIOS ALG statistics information of the processor:
Router# show platform hardware qfp active feature alg statistics netbios
NetBIOS ALG Statistics:
No. of allocated chunk elements in L7 data pool:0
No. of times L7 data is allocated:0 No. of times L7 data is freed:0
Datagram Service statistics
Total packets :0
Direct unique packets :0
Direct group packets :0
Broadcast packets :0
DGM Error packets :0
Query request packets :0
Positive Qry response packets :0
Netgative Qry response packets:0
Unknown packets :0
Total error packets :0
Name Service statistics
Total packets :0
Query request packets :0
Query response packets :0
Registration req packets :0
Registration resp packets:0
Release request packets :0
Release response packets :0
WACK packets :0
Refresh packets :0
Unknown packets :0
Total error packets :0
Session Service statistics
Total packets :0
Message packets :0
Request packets :0
Positive response packets:0
Negative response packets:0
Retarget response packets:0
Keepalive packets :0
Unknown packets :0
Total error packets :0
The table below describes the significant fields shown in the display.
The following example displays SIP statistics information of the processor. The field descriptions are self-explanatory.
Router# show platform hardware qfp active feature alg statistics sip
SIP info pool used chunk entries number: 0
RECEIVE
Register: 0 -> 200-OK: 0
Invite: 0 -> 200-OK: 0 Re-invite 0
Update: 0 -> 200-OK: 0
Bye: 0 -> 200-OK: 0
Trying: 0 Ringing: 0 Ack: 0
Info: 0 Cancel: 0 Sess Prog: 0
Message: 0 Notify: 0 Prack: 0
OtherReq: 0 OtherOk: 0
Events
Null dport: 0 Media Port Zero: 0
Malform Media: 0 No Content Length: 0
Cr Trunk Chnls: 0 Del Trunk Chnls: 0
Cr Normal Chnls: 0 Del Normal Chnls: 0
Media Addr Zero: 0 Need More Data: 0
Errors
Create Token Err: 0 Add portlist Err: 0
Invalid Offset: 0 Invalid Pktlen: 0
Free Magic: 0 Double Free: 0
Retmem Failed: 0 Malloc Failed: 0
Bad Format: 0 Invalid Proto: 0
Add ALG state Fail: 0 No Call-id: 0
Parse SIP Hdr Fail: 0 Parse SDP Fail: 0
Error New Chnl: 0 Huge Size: 0
Create Failed: 0
Writeback Errors
Offset Err: 0 PA Err: 0
No Info: 0
show platform software trace messageTo display trace messages for a module, enter the show platform software trace message command in privileged EXEC mode or diagnostic mode. Syntax Description
Usage GuidelinesThe show platform software trace message command is used to display trace messages from an in-memory message ring of a moduleâs process that keeps a condensed historical record of all messages. Although all messages are saved in a trace log file unmodified, only the first 128 bytes of a message are saved in the message ring. The size limitation does not apply to the traceback portion of a message. ExamplesThe following example shows how to display the trace messages for the Host Manager process in RP slot 0 using the show platform software trace message command:
Router# show platform software trace message host-manager R0
08/23 12:09:14.408 [uipeer]: (info): Looking for a ui_req msg
08/23 12:09:14.408 [uipeer]: (info): Start of request handling for con 0x100a61c8
08/23 12:09:14.399 [uipeer]: (info): Accepted connection for 14 as 0x100a61c8
08/23 12:09:14.399 [uipeer]: (info): Received new connection 0x100a61c8 on descriptor 14
08/23 12:09:14.398 [uipeer]: (info): Accepting command connection on listen fd 7
08/23 11:53:57.440 [uipeer]: (info): Going to send a status update to the shell manager in slot 0
08/23 11:53:47.417 [uipeer]: (info): Going to send a status update to the shell manager in slot 0
The following example shows a truncated message that has a traceback. The truncated portion of the message is indicated by an ellipsis (...): 03/02 15:47:44.002 [errmsg]: (ERR): %EVENTLIB-3-TIMEHOG: read asyncon 0x100a9260: 60618ms, Traceback=1#862f8780825f93a618ecd9 ...Traceback=1#862f8780825f93a618ecd9dd48b3be96 evlib:FCAF000+CC00 evlib:FCAF000+A6A8 evutil:FFCA000+ADD0 evutil:FFCA000+5A80 evutil:FFCA000+A68C uipeer:FF49000+10AFC evlib:FCAF000+D28C evlib:FCAF000+F4C4 :10000000+1B24C c:EF44000+1D078 c:EF44000+1D220 show redundancy application control-interface groupTo display control interface information for a redundancy group, use the show redundancy application control-interface groupcommand in privileged EXEC mode. Usage GuidelinesThe show redundancy application control-interfacecommand shows information for the redundancy group control interfaces. ExamplesThe following is sample output from the show redundancy application control-interface command:
Router# show redundancy application control-interface group 2
The control interface for rg[2] is GigabitEthernet0/1/0
Interface is Control interface associated with the following protocols: 2 1
BFD Enabled
Interface Neighbors:
Related Commands
show redundancy application data-interfaceTo display data interface-specific information, use the show redundancy application data-interfacecommand in privileged EXEC mode. Usage GuidelinesThe show redundancy application data-interfacecommand displays information about the redundancy group data interfaces. ExamplesThe following is sample output from the show redundancy application data-interface command:
Router# show redundancy application data-interface group 1
The data interface for rg[1] is GigabitEthernet0/1/1
Related Commands
show redundancy application faults groupTo display fault-specific information for a redundancy group, use the show redundancy application faults groupcommand in privileged EXEC mode. Usage GuidelinesThe show redundancy application faultscommand shows information returned by redundancy group faults. ExamplesThe following is sample output from the show redundancy application faults command:
Router# show redundancy application faults group 2
Faults states Group 2 info:
Runtime priority: [150]
RG Faults RG State: Up.
Total # of switchovers due to faults: 2
Total # of down/up state changes due to faults: 2
The table below describes the significant fields shown in the display.
Related Commands
show redundancy application groupTo display the redundancy group information, use the show redundancy application groupcommand in privileged EXEC mode. Usage GuidelinesUse the show redundancy application groupcommand to display the current state of each interbox redundancy group on the device and the peer device. ExamplesThe following is sample output from the show redundancy application group all command:
Router# show redundancy application group all
Faults states Group 1 info:
Runtime priority: [200]
RG Faults RG State: Up.
Total # of switchovers due to faults: 3
Total # of down/up state changes due to faults: 2
Group ID:1
Group Name:grp2
Administrative State: No Shutdown
Aggregate operational state : Up
My Role: ACTIVE
Peer Role: UNKNOWN
Peer Presence: No
Peer Comm: No
Peer Progression Started: No
RF Domain: btob-one
RF state: ACTIVE
Peer RF state: DISABLED
RG Protocol RG 1
------------------
Role: Active
Negotiation: Enabled
Priority: 200
Protocol state: Active
Ctrl Intf(s) state: Down
Active Peer: Local
Standby Peer: Not exist
Log counters:
role change to active: 2
role change to standby: 0
disable events: rg down state 1, rg shut 0
ctrl intf events: up 0, down 2, admin_down 1
reload events: local request 3, peer request 0
RG Media Context for RG 1
--------------------------
Ctx State: Active
Protocol ID: 1
Media type: Default
Control Interface: GigabitEthernet0/1/0
Hello timer: 5000
Effective Hello timer: 5000, Effective Hold timer: 15000
LAPT values: 0, 0
Stats:
Pkts 0, Bytes 0, HA Seq 0, Seq Number 0, Pkt Loss 0
Authentication not configured
Authentication Failure: 0
Reload Peer: TX 0, RX 0
Resign: TX 1, RX 0
Standby Peer: Not Present.
Faults states Group 2 info:
Runtime priority: [150]
RG Faults RG State: Up.
Total # of switchovers due to faults: 2
Total # of down/up state changes due to faults: 2
Group ID:2
Group Name:name1
Administrative State: No Shutdown
Aggregate operational state : Up
My Role: ACTIVE
Peer Role: UNKNOWN
Peer Presence: No
Peer Comm: No
Peer Progression Started: No
RF Domain: btob-two
RF state: ACTIVE
Peer RF state: DISABLED
RG Protocol RG 2
------------------
Role: Active
Negotiation: Enabled
Priority: 150
Protocol state: Active
Ctrl Intf(s) state: Down
Active Peer: Local
Standby Peer: Not exist
Log counters:
role change to active: 1
role change to standby: 0
disable events: rg down state 1, rg shut 0
ctrl intf events: up 0, down 2, admin_down 1
reload events: local request 2, peer request 0
RG Media Context for RG 2
--------------------------
Ctx State: Active
Protocol ID: 2
Media type: Default
Control Interface: GigabitEthernet0/1/0
Hello timer: 5000
Effective Hello timer: 5000, Effective Hold timer: 15000
LAPT values: 0, 0
Stats:
Pkts 0, Bytes 0, HA Seq 0, Seq Number 0, Pkt Loss 0
Authentication not configured
Authentication Failure: 0
Reload Peer: TX 0, RX 0
Resign: TX 0, RX 0
Standby Peer: Not Present.
The table below describes the significant fields shown in the display.
Related Commands
show redundancy application if-mgrTo display interface manager information for a redundancy group, use the show redundancy application if-mgrcommand in privileged EXEC mode. Usage GuidelinesThe show redundancy application if-mgrcommand shows information of traffic interfaces protected by redundancy groups. When a traffic interface is functioning with the redundancy group, the state is no shut on the active device, and shut on the standby device. On the other hand, it is always shut on the standby device. ExamplesThe following is sample output from the show redundancy application if-mgr command:
Router# show redundancy application if-mgr group 2
RG ID: 2
Interface VIP VMAC Shut Decrement
==========================================================
GigabitEthernet0/1/7 10.1.1.3 0007.b422.0016 no shut 50
GigabitEthernet0/3/1 11.1.1.3 0007.b422.0017 no shut 50
The table below describes the significant fields shown in the display.
Related Commands
show redundancy application protocolTo display protocol-specific information for a redundancy group, use the show redundancy application protocolcommand in privileged EXEC mode. Usage GuidelinesThe show redundancy application protocolcommand shows information returned by redundancy group protocol. ExamplesThe following is sample output from the show redundancy application protocol command:
Router# show redundancy application protocol 3
Protocol id: 3, name:
BFD: ENABLE
Hello timer in msecs: 0
Hold timer in msecs: 0
The table below describes the significant fields shown in the display.
Related Commands
show redundancy application transportTo display transport-specific information for a redundancy group, use the show redundancy application transportcommand in privileged EXEC mode. Usage GuidelinesThe show redundancy application transportcommand shows information for redundancy group transport. ExamplesThe following is sample output from the show redundancy application transport group command:
Router# show redundancy application transport group 1
Transport Information for RG (1)
Related Commands
snmp-server enable traps dhcpTo enable DHCP Simple Network Management Protocol (SNMP) trap notifications, use the snmp-server enable traps dhcp command in global configuration mode. To disable DHCP trap notifications, use the no form of this command.
snmp-server
enable
traps
dhcp
[duplicate]
[interface]
[pool]
[subnet]
[time]
no
snmp-server
enable
traps
dhcp
[duplicate]
[interface]
[pool]
[subnet]
[time]
Syntax Description
Usage GuidelinesIf you do not specify any of the optional keywords, all DHCP trap notifications are enabled. ExamplesThe following example shows how to send SNMP trap notifications to the SNMP manager when the secondary subnet utilization falls below or exceeds the configured threshold: Router(config)# ip dhcp pool pool2 Router(dhcp-config)# utilization mark high 80 log Router(dhcp-config)# utilization mark low 70 log Router(dhcp-config)# network 192.0.2.0 255.255.255.0 Router(dhcp-config)# network 192.0.4.0 255.255.255.252 secondary Router(config-dhcp-subnet-secondary)# override utilization high 40 Router(config-dhcp-subnet-secondary)# override utilization low 30 ! Router(config)# snmp-server enable traps dhcp subnet In the following example, all DHCP trap notifications will be sent to the SNMP manager in response to DHCP server events: Router(config)# snmp-server enable traps dhcp subnet prefix-lengthTo configure a subnet allocation pool and determine the size of subnets that are allocated from the pool, use the subnet prefix-length command in DHCP pool configuration mode. To unconfigure subnet pool allocation, use the no form of this command. Usage GuidelinesThis command is used to configure a Cisco IOS router as a subnet allocation server for a centralized or remote Virtual Private Network (VPN) on-demand address pool (ODAP) manager. This command is configured under a DHCP pool. The prefix-length argument is used to determine the size of the subnets that are allocated from the subnet allocation pool. The values that can be configured for the prefix-length argument follow CIDR bit count notation format. Configuring Global Subnet Pools Global subnet pools are created in a centralized network. The ODAP server allocates subnets from the subnet allocation server based on subnet availability. When the ODAP manager allocates a subnet, the subnet allocation server creates a subnet binding. This binding is stored in the DHCP database for as long as the ODAP server requires the address space. The binding is destroyed and the subnet is returned to the subnet pool only when the ODAP server releases the subnet as address space utilization decreases. Configuring VPN Subnet Pools A subnet allocation server can be configured to assign subnets from VPN subnet allocation pools for Multiprotocol Label Switching (MPLS) VPN clients. VPN routes between the ODAP manager and the subnet allocation server are configured based on VRF name or VPN ID configuration. The VRF and VPN ID are configured to maintain routing information that defines customer VPN sites. This customer site is attached to a provider edge (PE) router. A VRF consists of an IP routing table, a derived Cisco Express Forwarding (CEF) table, a set of interfaces that use the forwarding table, and a set of rules and routing protocol parameters that control the information that is included in the routing table. Configuring VPN Subnet Pools for VPN clients with VPN IDs A subnet allocation server can also be configured to assign subnets from VPN subnet allocation pools based on the VPN ID of a client. The VPN ID (or Organizational Unique Identifier [OUI]) is a unique identifier assigned by the IEEE. VPN routes between the ODAP manager and the subnet allocation server are enabled by configuring the DHCP pool with a VPN ID that matches the VPN ID that is configured for the VPN client. ExamplesThe following example configures a router to be a subnet allocation server and creates a global subnet allocation pool named GLOBAL-POOL from the 10.0.0.0 network. The configuration of the subnet prefix-length command in this example configures each subnet that is allocated from the subnet pool to support 254 host IP addresses. ip dhcp pool GLOBAL-POOL network 10.0.0.0 255.255.255.0 subnet prefix-length 24 ExamplesThe following example configures a router to be a subnet allocation server and creates a VPN routing and forwarding (VRF) subnet allocation pool named VRF-POOL from the 172.16.0.0 network and configures the VPN to match the VRF named pool1. The configuration of the subnet prefix-length command in this example configures each subnet that is allocated from the subnet pool to support 62 host IP addresses. ip dhcp pool VRF-POOL vrf pool1 network 172.16.0.0 /16 subnet prefix-length 26 ExamplesThe following example configures a router to be a subnet allocation server and creates a VRF subnet allocation pool named VPN-POOL from the 192.168.0.0 network and configures the VRF named abc. The VPN ID must match the unique identifier that is assigned to the client site. The route target and route distinguisher are configured in the as-number:network number format. The route target and route distinguisher must match. The configuration of the subnet prefix-length command in this example configures each subnet that is allocated from the subnet pool to support 30 host IP addresses. ip vrf abc rd 100:1 route-target both 100:1 vpn id 1234:123456 ! ip dhcp pool VPN-POOL vrf abc network 192.168.0.0 /24 subnet prefix-length /27 Related Commands
term ip netmask-formatTo specify the format in which netmasks are displayed in show command output, use the term ip netmask-formatcommand inEXEC configuration mode. To restore the default display format, use the no form of this command.
term
ip
netmask-format
{bitcount | decimal | hexadecimal}
no
term
ip
netmask-format
[bitcount | decimal | hexadecimal]
Command History
Usage GuidelinesIP uses a 32-bit mask that indicates which address bits belong to the network and subnetwork fields, and which bits belong to the host field. This range of IP addresses is called a netmask. By default, show commands display an IP address and then its netmask in dotted decimal notation. For example, a subnet would be displayed as 131.108.11.55 255.255.255.0. However, you can specify that the display of the network mask appear in hexadecimal format or bit count format instead. The hexadecimal format is commonly used on UNIX systems. The previous example would be displayed as 131.108.11.55 0XFFFFFF00. The bitcount format for displaying network masks is to append a slash (/) and the total number of bits in the netmask to the address itself. The previous example would be displayed as 131.108.11.55/24. timers hellotimeTo configure timers for hellotime and holdtime messages for a redundancy group, use the timers hellotimecommand in redundancy application protocol configuration mode. To disable the timers in the redundancy group, use the no form of this command.
timers
hellotime
[msec]
seconds
holdtime
[msec]
seconds
no
timers
hellotime
[msec]
seconds
holdtime
[msec]
seconds
Syntax Description
Command DefaultThe default value for the hellotime interval is 3 seconds and for the holdtime interval is 10 seconds. Usage GuidelinesThe hello time is an interval in which hello messages are sent. The holdtime is the time before the active or the standby device is declared to be in down state. Use the msec keyword to configure the timers in milliseconds. ExamplesThe following example shows how to configure the hellotime and holdtime messages: Router# configure terminal Router(config)# redundancy Router(config-red)# application redundancy Router(config-red-app)# protocol 1 Router(config-red-app-prtcl)# timers hellotime 100 holdtime 100 Related Commands
update arpTo secure dynamic Address Resolution Protocol (ARP) entries in the ARP table to their corresponding DHCP bindings, use the update arpcommand in DHCP pool configuration mode. To disable this command and change secure ARP entries to dynamic ARP entries, use the no form of this command. Usage GuidelinesThe update arp DHCP pool configuration command is used to secure ARP table entries and their corresponding DHCP leases. However, existing active leases are not secured. These leases will remain insecure until they are renewed. When the lease is renewed, it is treated as a new lease and will be secured automatically. If this feature is disabled on the DHCP server, all existing secured ARP table entries will automatically change to dynamic ARP entries. This command can be configured only under the following conditions:
The configuration of this command is not visible to the client. When this command is configured, secured ARP table entries that are created by a DHCP server cannot be removed from the ARP table by the clear arp-cache command. This is designed behavior. If a secure ARP entry created by the DHCP server must be removed, the clear ip dhcp binding command can be used. This command will clear the DHCP binding and secured ARP table entry.
update dnsTo dynamically update the Domain Name System (DNS) with address (A) and pointer (PTR) Resource Records (RRs) for some address pools, use the update dns command in global configuration mode. To disable dynamic updates, use the no form of this command. Syntax Description
Usage GuidelinesIf you configure the update dns both override command, the DHCP server will perform DDNS updates for both PTR and A RRs associated with addresses assigned from an address pool, even if the DHCP client specified in the FQDN that the server should not. If the server is configured using this command with or without any of the other keywords, and if the server does not see an FQDN option in the DHCP interaction, then it will assume that the client does not understand DDNS and act as though it were configured to update both A and PTR records on behalf of the client. utilization mark highTo configure the high utilization mark of the current address pool size, use the utilization mark high command in DHCP pool configuration mode. To remove the high utilization mark, use the no form of this command. Usage GuidelinesThe current pool size is the sum of all addresses in all the subnets in the pool. If the utilization level exceeds the configured high utilization mark, the pool will schedule a subnet request. This command can be used with both network and on-demand pools. However, in the case of a network pool, only the log option of this command can be used. In the case of an on-demand pool, the autogrow sizeoption of the origin command must be configured. In certain network deployments, it is important for the network administrator to receive asynchronous notification when the DHCP pools are nearly exhausted so that preventive action can be taken. One common method for such notification is the generation of a system message. If you use the log option, a system message can be generated for a DHCP pool when the pool utilization exceeds the configured high utilization threshold. A system message can also be generated when the pool's utilization is detected to be below the configured low utilization threshold. ExamplesThe following example sets the high utilization mark to 80 percent of the current pool size: utilization mark high 80 The following pool configuration using the log keyword option generates a system message: ! ip dhcp pool abc utilization mark high 30 log utilization mark low 25 log network 10.1.1.0 255.255.255.248 ! The following system message is generated when the second IP address is allocated from the pool: 00:02:01: %DHCPD-6-HIGH_UTIL: Pool "abc" is in high utilization state (2 addresses used out of 6). Threshold set at 30%. The following system message is generated when one of the two allocated IP addresses is returned to the pool: 00:02:58: %DHCPD-6-LOW_UTIL: Pool "abc" is in low utilization state (1 addresses used out of 6). Threshold set at 25%. utilization mark lowTo configure the low utilization mark of the current address pool size, use the utilization mark low command in DHCP pool configuration mode. To remove the low utilization mark, use the no form of this command. Usage GuidelinesThe current pool size is the sum of all addresses in all the subnets in the pool. If the utilization level drops below the configured low utilization mark, a subnet release is scheduled from the address pool. This command can be used with both network and on-demand pools. However, in the case of a network pool, only the log option of this command can be used. In the case of an on-demand pool, the autogrow sizeoption of the origin command must be configured. In certain network deployments, it is important for the network administrator to receive asynchronous notification when the DHCP pools are nearly exhausted so that preventive action can be taken. One common method for such notification is the generation of a system message. If you use the log option, a system message can be generated for a DHCP pool when the pool utilization exceeds the configured high utilization threshold. A system message can also be generated when the pool's utilization is detected to be below the configured low utilization threshold. view (DNS)To access or create the specified Domain Name System (DNS) view list member in the DNS view list and then enter DNS view list member configuration mode, use the view command in DNS view list configuration mode. To remove the specified DNS view list member from the DNS view list, use the no form of this command.
view
[vrf vrf-name]
{default | view-name}
order-number
no
view
[vrf vrf-name]
{default | view-name}
order-number
Syntax Description
Usage GuidelinesThis command enters DNS view list member configuration mode--for the specified view list member--so that usage restrictions can be configured for that view list member. If the DNS view list member does not exist yet, the specified DNS view is added to the DNS view list along with the value that indicates the order in which the view list member is to be checked (relative to the other DNS views in the view list) whenever the router needs to determine which DNS view list member to use to address a DNS query.
The view command can be entered multiple times to specify more than one DNS view in the DNS view list. To display information about a DNS view list, use the show ip dns view-list command. Subsequent Operations on a DNS View List Member After you use the view command to define a DNS view list member and enter DNS view list member configuration mode, you can use any of the following commands to configure usage restrictions for the DNS view list member:
These optional, additional restrictions are based on query source authentication, the query hostname, and the query source host IP address, respectively. If none of these optional restrictions are configured for the view list member, the only usage restriction on the view list member is the usage restriction based on its association with a VRF. Reordering of DNS View List Members To provide for efficient management of the order of the members in a view list, each view list member definition includes the specification of the position of that member within the list. That is, the order of the members within a view list is defined by explicit specification of position values rather than by the order in which the individual members are added to the list. This enables you to add members to an existing view list or reorder the members within an existing view list without having to remove all the view list members and then redefine the view list membership in the desired order: ExamplesThe following example shows how to add the view user3 to the DNS view list userlist5 and assign this view member the order number 40 within the view list. Next, the view user2, associated with the VRF vpn102 and assigned the order number 20 within the view list, is removed from the view list. Router(config)# ip dns view-list userlist5 Router(cfg-dns-view-list)# view user3 40 Router(cfg-dns-view-list-member)# exit Router(cfg-dns-view-list)# no view vrf vpn102 user2 20 Related Commands
vrf (DHCP pool)To associate the on-demand address pool with a VPN routing and forwarding instance (VRF) name, use the vrf command in DHCP pool configuration mode. To remove the VRF name, use the no form of this command. Usage GuidelinesAssociating a pool with a VRF allows overlapping addresses with other pools that are not on the same VRF. Only one pool can be associated with each VRF. If the pool is configured with the origin dhcp command or origin aaa command, the VRF information is sent in the subnet request. If the VRF is configured with an RFC 2685 VPN ID, the VPN ID will be sent instead of the VRF name. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||