Ciao, I just create the following: access-list 1 deny 10.10.10.0 0.0.0.255 deny 10.10.20.0 0.0.0.254 permit any class-map CAP-INTERNET match access-group 1 policy-map MAX-BW-INTERNET class CAP-INTERNET police 8000000 0 0 conform-action transmit exceed-action drop violate-action drop interface vlan 2 ip address 10.10.30.1 255.255.255.248 service-policy output MAX-BW-INTERNET service-policy input MAX-BW-INTERNET int gi1/1 desc TO-Wan sw sw mode acc sw acc vl 2 platform qos vlan-based   The idea is to cap the traffic not belonging to the networks in the ACL to 8mb (due to the fact that the "priority" command is not supported on SVI): vlan 2 is the gateway to the wan link. What I'm missing is if I need to apply the bw modification (the wan link is 10Mbps) under the SVI or the physical L2 interface or not; moreover I also have SVI belonging to 10.10.10.0/24 and another one belonging to 10.10.20.0/24 but I don't want to cap the local routed traffic.   Any suggestion ?   Thanks and regards, Luciano ... View more

Ciao, P1R1 is running eBGP WAN router speaks with eBGP with P1R1 and redistribute it to OSPF process (E1 type); COREx are speaking with WAN via OSPF area 1 (ptp link) and speaking between them via OSPF area 0 (ptp link). What happened is that CORE2 learn the original eBGP route via WAN and not via CORE1; so I try to add "ip ospf cost" under the interface that link CORE2 via WAN: the cost changed but still learn the route from WAN.   CORE2# sh ip route 100.100.100.0 Routing entry for 100.100.100.0/24   Known via "ospf 10", distance 110, metric 20010   Tag 5, type extern 1   Last update from 5.5.5.1 on Ethernet0/3, 00:08:53 ago   Routing Descriptor Blocks:   * 5.5.5.1, from 9.9.9.9, 00:08:53 ago, via Ethernet0/3       Route metric is 20010, traffic share count is 1       Route tag 5 CORE1#sh ip ro 100.100.100.0 Routing entry for 100.100.100.0/24   Known via "ospf 10", distance 110, metric 20   Tag 5, type extern 1   Last update from 3.3.3.1 on Ethernet0/3, 00:10:50 ago   Routing Descriptor Blocks:   * 3.3.3.1, from 9.9.9.9, 00:10:50 ago, via Ethernet0/3       Route metric is 20, traffic share count is 1       Route tag 5 When I shut the interface from CORE2 to WAN:   CORE2(config-if)#do sh ip ro 100.100.100.0 Routing entry for 100.100.100.0/24   Known via "ospf 10", distance 110, metric 30   Tag 5, type extern 1   Last update from 4.4.4.1 on Ethernet0/2, 00:00:12 ago   Routing Descriptor Blocks:   * 4.4.4.1, from 9.9.9.9, 00:00:12 ago, via Ethernet0/2       Route metric is 30, traffic share count is 1       Route tag 5 ... for sure I'm missing something ... any clues ?   Ciao! L. ... View more

Ciao, in order to create a VSS cluster is it mandatory to put the C6880-X-16P10G line card in performance mode ? BR, Luciano ... View more

Ciao,   we are just facing a strange behavior on a FO SM link (span is about 2km). The link connects one 4506 with X2-10GB-LR to a Nexus 3548 with a 10Gbase-LR: the link is up & running. The strange behavior is the TX power registered by the X2: KL-MENARA-CORE#sh int te1/4/1 trans det ITU Channel not available (Wavelength not available), Transceiver is internally calibrated. mA: milliamperes, dBm: decibels (milliwatts), NA or N/A: not applicable. ++ : high alarm, +  : high warning, -  : low warning, -- : low alarm. A2D readouts (if they differ), are reported in parentheses. The threshold values are calibrated.                               High Alarm  High Warn  Low Warn   Low Alarm           Temperature         Threshold   Threshold  Threshold  Threshold Port       (Celsius)          (Celsius)   (Celsius)  (Celsius)  (Celsius) --------- ------------------  ----------  ---------  ---------  --------- Te1/4/1      9.1                74.0        70.0         0.0       -4.0                               High Alarm  High Warn  Low Warn   Low Alarm            Voltage            Threshold   Threshold  Threshold  Threshold Port       (Volts)            (Volts)     (Volts)    (Volts)    (Volts) ---------  ---------------    ----------  ---------  ---------  --------- Te1/4/1    3.32                   N/A         N/A         N/A        N/A            Optical            High Alarm  High Warn  Low Warn   Low Alarm            Transmit Power     Threshold   Threshold  Threshold  Threshold Port       (dBm)              (dBm)       (dBm)      (dBm)      (dBm) ---------  -----------------  ----------  ---------  ---------  --------- Te1/4/1    -40.0                  4.4         0.4        -8.2      -12.2            Optical            High Alarm  High Warn  Low Warn   Low Alarm            Receive Power      Threshold   Threshold  Threshold  Threshold Port       (dBm)              (dBm)       (dBm)      (dBm)      (dBm) -------    -----------------  ----------  ---------  ---------  --------- Te1/4/1     -7.0                 4.4         0.4       -14.4      -18.4   As you can see it registering a -40.0 TX .... on the other side:   KL-MENARA-L201# sh int Ethernet1/23 trans det Ethernet1/23     transceiver is present     type is 10Gbase-LR     name is OEM     part number is SFP+-LR     revision is     serial number is FNS16480367     nominal bitrate is 10300 MBit/sec     Link length supported for 9/125um fiber is 10 km     cisco id is --     cisco extended id number is 4            SFP Detail Diagnostics Information (internal calibration)   ----------------------------------------------------------------------------                 Current              Alarms                  Warnings                 Measurement     High        Low         High          Low   ----------------------------------------------------------------------------   Temperature   32.51 C        80.00 C    -10.00 C     70.00 C        0.00 C   Voltage        3.20 V         3.63 V      2.97 V      3.46 V        3.13 V   Current       49.50 mA      110.00 mA     1.00 mA   100.00 mA       1.00 mA   Tx Power       -0.41 dBm       2.49 dBm  -10.22 dBm    0.49 dBm     -8.21 dBm   Rx Power       -7.67 dBm        2.49 dBm  -16.57 dBm    0.49 dBm    -14.43 dBm   ----------------------------------------------------------------------------   Note: ++  high-alarm; +  high-warning; --  low-alarm; -  low-warning As you can see below the ports are connected together:   KL-MENARA-L201# sh udld ne Port             Device Name    Device ID   Port ID         Neighbor State -------------------------------------------------------------------------- Ethernet1/21     FOC1852R04H    1           Ethernet1/21    bidirectional Ethernet1/22     FOC1852R04H    1           Ethernet1/22    bidirectional Ethernet1/23     SPE184700LE    1           Te1/4/1         bidirectional   Any Idea ?   BR, Luciano ... View more

Gentlemen, I try to figure out how to configure OTV with ASR "on a stick" with only one OTV edge device per site; the WAN link is a routed port on the cores of each DC. Up to know I understand the following 1 - One link to core\aggregation with L2 Vlan 2 - One L3 link to core (PTP to core /30) for the join interface 3 - There should be reachability between the addresses at point "2" before implementing the OTV One question now arises: if I'm going to deploy the OTV in multicast mode shall I have to enable the SSM on the core devices ?   In this doc: http://www.cisco.com/c/en/us/support/docs/routers/asr-1000-series-aggregation-services-routers/117157-configure-otv-00.html the OTV devices are directly attached on the WAN, which is a little bit different than my design.   Cheers, Luciano ... View more