IPV6 Address Type

Well, to make a long story short; the Interface command "ipv6 address" is used to assign (configure) a layer 3 IPv6 address to a Cisco router's interface.

Currently, there are five different ways the "ipv6 address" command can be used.


View Examples Below:

1. Syntax: Router(config-if)#ipv6 address ipv6 address/prefix-length

Example: Router(config-if)#ipv6 address 2001:100:100:100::1/64



2. Syntax: Router(config-if)#ipv6 address ipv6 prefix/prefix-length anycast

Example: Router(config-if)#ipv6 address 2001:0DB8:1:1::/64 anycast



3. Syntax: Router(config-if)#ipv6 address autoconfig [default]

Example: Router(config-if)#ipv6 address autoconfig



4. Syntax: Router(config-if)#ipv6 address ipv6 prefix/prefix-length eui-64

Example: Router(config-if)#ipv6 address 2001:100:100:100::/64 eui-64
    


5. Syntax: Router(config-if)#ipv6 address ipv6 link-local address/prefix-length link-local

Example: Router(config-if)#ipv6 address FE80::260:3EFF:FE11:5770/64 link-local



IPv6 Address Command Examples Explained:

1. Syntax: Router(config-if)#ipv6 address ipv6 address/prefix-length
Example: Router(config-if)#ipv6 address 2001:100:100:100::1/64
The first example is using the "ipv6 address" command to assign (configure) an IPv6 Global Unicast Address (GUA) to an interface. Notice, in the first example the "ipv6 address" command is requiring the complete IPv6 address and the prefix-length. The prefix-length (/64) is indicating how many high order bits are being used for the network portion of the GUA.


2. Syntax: Router(config-if)#ipv6 address ipv6 prefix/prefix-length anycast
Example: Router(config-if)#ipv6 address 2001:0DB8:1:1::/64 anycast
The second example is using the "ipv6 address" command to assign (configure) an IPv6 Anycast Address to an interface. Notice, in the second example the "ipv6 address" command is only requiring the IPv6 prefix (network portion) of an IPv6 address and the prefix-length, followed by the word "anycast".


3. Syntax: Router(config-if)#ipv6 address autoconfig [default]
Example:Router(config-if)#ipv6 address autoconfig
The third example is using the "ipv6 address" command to make the interface in question automatically autoconfigure itself with an IPv6 address using stateless autoconfiguration. You can also use the keyword "default" to make the interface install a default route. But remember, the keyword "default" can only be used on one interface.


4. Syntax: Router(config-if)#ipv6 address ipv6 prefix/prefix-length eui-64
Example: Router(config-if)#ipv6 address 2001:100:100:100::/64 eui-64
The fourth example is using the "ipv6 address" command to assign (configure) an IPv6 Global Unicast Address (GUA) to an interface. But, unlike the first example; this example is requiring that the "ipv6 address" command use the IPv6 prefix (network portion) of an IPv6 address and the prefix-length; followed by the word "eui-64". In other words, in this example, the interface is going to assign (configure) a GUA to itself; by combining the IPv6 prefix (network portion) which are the first sixty four (/64) high order bits; with the remaining sixty four low-order bits which are the EUI-64 Interface Identifier. The EUI-64 Interface Identifier, is actually the interface's layer 2 address (MAC Address) that has been modified into EUI-64 format.


5. Syntax: Router(config-if)#ipv6 address ipv6 link-local address/prefix-length link-local
Example: Router(config-if)#ipv6 address FE80::260:3EFF:FE11:5770/64 link-local
The fifth example is using the "ipv6 address" command to assign (configure) a specific (certain) layer 3 Link-Local Address to an interface. Notice, that in the fifth example, the "ipv6 address" command is requiring the entire IPv6 link-local address and the prefix-length, followed by the word "link-local". The "link-local" word is telling the interface, to configure (assign) the link-local address (FE80::260:3EFF:FE11:5770) to the interface and also overwrite any link-local address that may have been configured (assigned) earlier "automatically" from the interface's MAC Address.

Upgrade IOS 3750 stack

Upgrade IOS  3750 stack 
from old ios c3750-ipbase-mz.122-35.SE5  to new IOS c3750-ipbasek9-mz.122-55.SE5.bin

Copy new IOS from my laptop 10.0.0.1

RxxxBBBSEC01#copy tftp flash
Address or name of remote host []? 10.0.0.1
Source filename []? c3750-ipbasek9-mz.122-55.SE5.bin
Destination filename [c3750-ipbasek9-mz.122-55.SE5.bin]?
Accessing tftp://10.0.0.1/c3750-ipbasek9-mz.122-55.SE5.bin...
Loading c3750-ipbasek9-mz.122-55.SE5.bin from 10.0.0.1 (via GigabitEthernet1/0/6): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
[OK - 12098310 bytes]
12098310 bytes copied in 247.287 secs (48924 bytes/sec)

l'IOS è stato copiato sullo switch 1


RxxxBBBSEC01#show flash
Directory of flash:/
    2  -rwx       80395  Oct 29 2013 15:57:56 +01:00  config.text
    3  -rwx        1996  Jun 23 2013 17:16:29 +02:00  vlan.dat
    4  -rwx        5144  Oct 29 2013 15:57:56 +01:00  multiple-fs
    5  -rwx           5  Oct 29 2013 15:57:56 +01:00  private-config.text
    6  -rwx    12098310  Nov 12 2013 11:31:01 +01:00  c3750-ipbasek9-mz.122-55.SE5.bin
    7  drwx         192   Mar 1 1993 01:09:25 +01:00  c3750-ipbase-mz.122-35.SE5

ora deve essere copiato sullo switch 2


RxxxBBBSEC01#dir flash2:
Directory of flash2:/
    2  -rwx       80395  Oct 29 2013 15:58:02 +01:00  config.text
    3  -rwx           5  Oct 29 2013 15:58:02 +01:00  private-config.text
    4  -rwx        1996  Jun 23 2013 17:16:33 +02:00  vlan.dat
    5  -rwx        5144  May 17 2013 01:38:52 +02:00  multiple-fs
    7  drwx         192   Mar 1 1993 01:10:15 +01:00  c3750-ipbase-mz.122-35.SE5


queste sono le attuali BOOT VAR DEVONO ESSERE CAMBIATE


RxxxBBBSEC01#sh boot
BOOT path-list      : flash:c3750-ipbase-mz.122-35.SE5/c3750-ipbase-mz.122-35.SE5.bin
Config file         : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break        : no
Manual Boot         : no
HELPER path-list    :
Auto upgrade        : yes
Auto upgrade path   :
-------------------
Switch 2
-------------------
BOOT path-list      : flash:c3750-ipbase-mz.122-35.SE5/c3750-ipbase-mz.122-35.SE5.bin
Config file         : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break        : no
Manual Boot         : no
HELPER path-list    :
Auto upgrade        : no
Auto upgrade path   :



RxxxBBBSEC01#dir flash:
Directory of flash:/
    2  -rwx       80395  Oct 29 2013 15:57:56 +01:00  config.text
    3  -rwx        1996  Jun 23 2013 17:16:29 +02:00  vlan.dat
    4  -rwx        5144  Oct 29 2013 15:57:56 +01:00  multiple-fs
    5  -rwx           5  Oct 29 2013 15:57:56 +01:00  private-config.text
    6  -rwx    12098310  Nov 12 2013 11:31:01 +01:00  c3750-ipbasek9-mz.122-55.SE5.bin
    7  drwx         192   Mar 1 1993 01:09:25 +01:00  c3750-ipbase-mz.122-35.SE5
32514048 bytes total (10698752 bytes free)



RxxxBBBSEC01#dir flash2:                    
Directory of flash2:/
    2  -rwx       80395  Oct 29 2013 15:58:02 +01:00  config.text
    3  -rwx           5  Oct 29 2013 15:58:02 +01:00  private-config.text
    4  -rwx        1996  Jun 23 2013 17:16:33 +02:00  vlan.dat
    5  -rwx        5144  May 17 2013 01:38:52 +02:00  multiple-fs
    6  -rwx    12098310  Nov 12 2013 14:52:37 +01:00  c3750-ipbasek9-mz.122-55.SE5.bin
    7  drwx         192   Mar 1 1993 01:10:15 +01:00  c3750-ipbase-mz.122-35.SE5



RxxxBBBSEC01(config)#boot system flash:/c3750-ipbasek9-mz.122-55.SE5.bin



RxxxBBBSEC01#show boot
BOOT path-list      : flash:/c3750-ipbasek9-mz.122-55.SE5.bin
Config file         : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break        : no
Manual Boot         : no
HELPER path-list    :
Auto upgrade        : yes
Auto upgrade path   :
-------------------
Switch 2
-------------------
BOOT path-list      : flash:/c3750-ipbasek9-mz.122-55.SE5.bin
Config file         : flash:/config.text
Private Config file : flash:/private-config.text
Enable Break        : no
Manual Boot         : no
HELPER path-list    :
Auto upgrade        : no
Auto upgrade path   :

RxxxBBBSEC01#dir flash:
Directory of flash:/
    2  -rwx       80395  Oct 29 2013 15:57:56 +01:00  config.text
    3  -rwx        1996  Jun 23 2013 17:16:29 +02:00  vlan.dat
    4  -rwx        5144  Oct 29 2013 15:57:56 +01:00  multiple-fs
    5  -rwx           5  Oct 29 2013 15:57:56 +01:00  private-config.text
    6  -rwx    12098310  Nov 12 2013 11:31:01 +01:00  c3750-ipbasek9-mz.122-55.SE5.bin
    7  drwx         192   Mar 1 1993 01:09:25 +01:00  c3750-ipbase-mz.122-35.SE5
32514048 bytes total (10698752 bytes free)

RxxxBBBSEC01#dir flash2:
Directory of flash2:/
    2  -rwx       80395  Oct 29 2013 15:58:02 +01:00  config.text
    3  -rwx           5  Oct 29 2013 15:58:02 +01:00  private-config.text
    4  -rwx        1996  Jun 23 2013 17:16:33 +02:00  vlan.dat
    5  -rwx        5144  May 17 2013 01:38:52 +02:00  multiple-fs
    6  -rwx    12098310  Nov 12 2013 14:52:37 +01:00  c3750-ipbasek9-mz.122-55.SE5.bin
    7  drwx         192   Mar 1 1993 01:10:15 +01:00  c3750-ipbase-mz.122-35.SE5
32514048 bytes total (10698752 bytes free)

ip local policy route-map" vs "ip policy route-map"

one is in global configuration mode, another is in interface configuration mode.

ip local policy route-map

The "ip local policy route-map" command is used to policy-route traffic generated locally on the router. For example, if you are logged into the router itself executing a ping, the local policy would apply. The same would apply for GRE / IPSec / Telnet traffic etc. coming from the router itself.

ip policy route-map

The "ip policy route-map" looks at traffic entering an interface and policy-routes accordingly. This traffic would be external, transiting the router. Hope that clears your first question.

MSDP - ANYCAST - RP

TRAFFIC-SHAPING LEGACY on MAP-CLASS

Legacy FRTS

 

This is the most well-known FRTS method, which has been available for quite a while on Cisco routers. It is now being outdated by MQC configurations.
The key characteristic is that all settings are configured under map-class command mode, and later are applied to a particular set PVCs. The
same configuration concept was used for legacy ATM configuration mode (map-class atm).

Legacy FRTS has the following characteristics:

- Enabled with frame-relay traffic-shaping command at physical interface level
- Incompatible with GTS or MQC commands at subinterfaces or physical interface levels
- With FRTS you can enforce bitrate per-VC (VC-granular, unlike GTS), by applying a map-class to PVC
- When no map-class is explicitly applied to PVC, it’s CIR and Tc are set to 56K/125ms by default
- Shaping parameters are configured under map-class frame-relay configuration submode
- Allows to configure fancy-queueing (WFQ/PQ/CQ) or simple FIFO per-VC
- No option to configure fancy-queueing at interface level: interface queue is forced to FIFO (if no FRF.12 is configured)
- Allows for adaptive shaping (throttling down to minCIR) on BECN reception (just as GTS) and option to reflect incoming FECNs as BECNs
- Option to enable adaptive shaping which responds to interface congestion (non-empty interface



R25#sh frame-relay pvc 253
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 253, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
  input pkts 3753          output pkts 1313         in bytes 246264   
  out bytes 120733         dropped pkts 0           in pkts dropped 0        
  out pkts dropped 0                out bytes dropped 0        
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0        
  out BECN pkts 0          in DE pkts 0             out DE pkts 0        
  out bcast pkts 1234      out bcast bytes 100994   
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 02:55:56, last time pvc status changed 02:28:38
R25#


interface Serial0/0
 ip address 10.10.10.11 255.255.255.248
 ip pim dr-priority 100
 ip pim nbma-mode
 ip pim sparse-mode
 encapsulation frame-relay
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 cisco
 ip ospf network point-to-multipoint
 ipv6 address FE80::25 link-local
 ipv6 address 2001:CC1E:ABCD:100:10:10:2:11/64
 ipv6 ospf network point-to-multipoint
 ipv6 ospf 1 area 0
 serial restart-delay 0
 frame-relay map ipv6 2001:CC1E:ABCD:100:10:10:2:9 253 broadcast
 frame-relay map ipv6 2001:CC1E:ABCD:100:10:10:2:10 254 broadcast
 frame-relay map ipv6 FE80::23 253
 frame-relay map ipv6 FE80::24 254
 frame-relay map ip 10.10.10.10 254 broadcast
 frame-relay map ip 10.10.10.9 253 broadcast
 frame-relay interface-dlci 253  
  class frts
 no frame-relay inverse-arp

R25(config)#interface Serial0/0
R25(config-if)#frame-relay traffic-shaping  

IN QUESTO MODO SI ABILITA IL TRAFFIC SHAPING   E L'OUTPUT DEL COMANDO PRECEDENTE CAMBIA "sh frame-relay pvc 253"

R25#sh frame-relay pvc 253
PVC Statistics for interface Serial0/0 (Frame Relay DTE)
DLCI = 253, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial0/0
  input pkts 3820          output pkts 1337         in bytes 250704   
  out bytes 123017         dropped pkts 0           in pkts dropped 0        
  out pkts dropped 0                out bytes dropped 0        
  in FECN pkts 0           in BECN pkts 0           out FECN pkts 0        
  out BECN pkts 0          in DE pkts 0             out DE pkts 0        
  out bcast pkts 1257      out bcast bytes 102950   
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
  pvc create time 02:59:05, last time pvc status changed 02:31:47
  cir 1000      bc 8000      be 0         byte limit 15     interval 125 <--  parametri prima assenti
  mincir 500       byte increment 15    Adaptive Shaping none     <--  parametri prima assenti
  pkts 4         bytes 366       pkts delayed 0         bytes delayed 0  <--  parametri prima assenti    
  shaping inactive   
  traffic shaping drops 0
  Output queue 0/40, 0 drop, 0 dequeued

ROUTE-REFLECTOR - TS5

bgp redistribute-internal

FRAME-RELAY MQC vs LEGACY

GTS Generic Traffic Shaping


MQC" way to configuer Frame Realy traffic shaping. I have my configuration as follows:
!
class-map VOICE
match ip dscp ef
!
class-map DATA
match ip dscp cs1
!
! "Child" policy-map, used to implement CBWFQ
!
policy-map CBWFQ
class VOICE
priority 64
class DATA
bandwidth 128
class class-default
fair-queue
!
! "Parent" policy map, used for PVC shaping
!
policy-map SHAPE_384K
class class-default
shape average 384000
shape adaptive 192000
service-policy CBWFQ

interface Serial 0/0/0:0.1
ip address 177.0.112.1 255.255.255.0
service-policy output SHAPE_384K
frame-relay interface-dlci 112

TS5 IGP ticket