Cisco 6500-E and Modules

1- As far as I understood, If we use SUP-2T on C6513-E, the Fabric Switch Capacity will be 80Gbps(2x40Gbps Channels). Is this correct?

yes in 11 slots

2- We can install WS-x6748-SFP on this setup with DFC4. Is this Correct?

Yes

3- Can we install WS-x6708-10G on this setup with DFC4 or Not?

6708 does not have DFC4 or CFC modes, so is not compatible with sup2t, you can use ws-6908-10g.

4- If no then can we use WS-x6716-10G with DFC4?

Yes

http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/hardware/Config_Notes/OL_24918.pdf
C6708-10GE-3CXL Local Switching:

http://www.gossamer-threads.com/lists/cisco/nsp/145906

 

Only 69xx modules  are  40 or more  per channel, all the 67xx and the upgraded 67xx ones with dfc4 (rebadged to 68xx) will still be 20 per channel, the DFC does not matter, the fabric asic and hardware on the older modules is all 20g per channel (40g total on dual channel cards).

Cisco EEM

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/eem/command/eem-cr-book/eem-cr-e1.html#wp2241131084

A state is not an event.
A state *change* is an event.

ip sla 1
  icmp-echo 1.1.1.1 source-ip 1.1.1.2
  vrf GREEN
  tag SITE-DOWN
  frequency 5
!
ip sla schedule 1 life forever start-time now !
event manager applet SITE-DOWN
  description Site 1.1.1.1 is down
  event ipsla operation-id 1
  action 1.0 syslog priority critical msg "ALERT: Site 1.1.1.1 is down"
!

And here is what I see when I look the status of the IP SLA entry and the EEM entry.  IP SLA looks fine, the EEM isn’t triggering despite being registered.

rtr5#sh ip sla statistics 1

IPSLAs Latest Operation Statistics
IPSLA operation id: 1

Latest RTT: NoConnection/Busy/TimeoutLatest operation start time: 11:42:21 EST Mon Jan 18 2016 Latest operation return code: Timeout Number of successes: 0 Number of failures: 301 Operation time to live: Forever !
rtr5#sh event manager policy registered
No.  Class     Type    Event Type          Trap  Time Registered
    Name
1    applet    user    ipsla               Off   Mon Jan 18 11:24:46
2016  SITE-DOWN
  operation-id {1}
  maxrun 20.000
  action 1.0 syslog priority critical msg "ALERT: Site 1.1.1.1 is down"
!
rtr5sh event manager statistics polic
Average        MaximumNo.  Class     Triggered   Suppressed  Run Time       Run Time       Name
-------------------------------------------------------------------------------
1    applet    0           0           0.000          0.000
SITE-DOWN
  event {} ipsla

MPLS and links with limited MTU size

When deal with Mtu issues on all out site to site vpn.  Gre plus IPSec plus other uses up 60 to 90 bytes.

There are some good docs on cisco site. Standard solution for tcp flows is, … for the constrained or tunnel int.

"IP Mtu 1400"
"IP tcp adjust-mss 1360"

This will cause the tcp 3way setup to negotiate a 1360byte mss which then fits into the 1500 byte max physical Mtu size.

In theory, setting the Mtu to 1400 will also cause the pmtu discovery process to auto adjust as well.  This is hit or miss, depending on stack and if icmp is being filtered in the path.

Windows tries hard to guess the Mtu and usually sets the do not frag bit on most packets.   The above usually works. But we often find some non-tcp app defaults to 1500 bytes anyway.  Since windows sends it with do not frag, the router drops it. To fix this use a route-map to clear the DF bit.  I only do this for udp now.  Seems a good compromise.

All this would be done on your Cpe or other edge router. Tunnelled ddos mitigation vendors also do this to avoid Mtu issues.

IP-SLA

 

You are missing a bit more specifics on your event definition… It just doesn’t match a reaction event from IP SLA.

 

If you look here:

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/eem/command/eem-cr-book/eem-cr-e1.html#wp2241131084

 

You can see that there are quite a few options to set what exactly you want to trigger on with regards to IP SLA.

I think you have to define reactions or triggers to match on IP SLA related events (events being state transitions… up to down, down to up, threshold limits, etc)

 

To be honest, I got best results from EEM and IP SLA by EEM matching on the syslog messages IP SLA produces…

 

 

working on an EEM script which is triggered by an IP SLA down

> state on an ASR1000 running IOS-XE 3.11.1S.  While the IP SLA entry

> detects the state properly, the EEM does not trigger.  I’m not finding

> anything relevant on the bug toolkit, and I am not seeing anything

> with my Google-fu.

>

> Here’s the configuration:

>

> ip sla 1

>   icmp-echo 1.1.1.1 source-ip 1.1.1.2

>   vrf GREEN

>   tag SITE-DOWN

>   frequency 5

> ip sla schedule 1 life forever start-time now !

> event manager applet SITE-DOWN

>   description Site 1.1.1.1 is down

>   event ipsla operation-id 1

>   action 1.0 syslog priority critical msg “ALERT: Site 1.1.1.1 is down”

> !

>

> And here is what I see when I look the status of the IP SLA entry and

> the EEM entry.  IP SLA looks fine, the EEM isn’t triggering despite

> being registered.

>

>

> rtr5#sh ip sla statistics 1

> IPSLAs Latest Operation Statistics

>

> IPSLA operation id: 1

>         Latest RTT: NoConnection/Busy/Timeout Latest operation start

> time: 11:42:21 EST Mon Jan 18 2016 Latest operation return code:

> Timeout Number of successes: 0 Number of failures: 301 Operation time

> to live: Forever !

> rtr5#sh event manager policy registered

> No.  Class     Type    Event Type          Trap  Time Registered

>     Name

> 1    applet    user    ipsla               Off   Mon Jan 18 11:24:46

> 2016  SITE-DOWN

>   operation-id {1}

>   maxrun 20.000

>   action 1.0 syslog priority critical msg “ALERT: Site 1.1.1.1 is down”

> !

> rtr5sh event manager statistics policy

>

>                                         Average        Maximum

> No.  Class     Triggered   Suppressed  Run Time       Run Time       Name

>

> ——————————————————————————-

> 1    applet    0           0           0.000          0.000

> SITE-DOWN

event {} ipsla

 

 


 

>(Specifically what I’m looking for is something that hooks into IP SLA

>or Ethernet OAM/CFM and takes a link out of IGP routing if packet loss

>crosses a certain threshold – we recently had a carrier break their

>metro network in interesting ways, leading to 50% packet loss, which

>was enough to effectively take the site offline, but IGP stubbornly

>clung to “I have seen a keepalive!”)

 

something like this could get you started, Gert?

 

1) Trigger based on SNMP interface error counters.

Rate is always calculated per second. Average factor identifies number of data points (one for each poll-interval) will be averaged for calculation of rate. Average factor needs to be a minimum of 2.

 

event manager applet INTERFACE-ERROS trap event snmp oid ifEntry.14.XX get-type exact entry-op ge entry-val 10 entry-type rate average-factor 2 poll-interval 5 action 20.0 syslog msg “disabling Gigxxx due to errors”

action 30.0 cli command “enable”

action 30.1 cli command “config terminal”

action 40.0 cli command “interface Gig XX”

action 50.0 cli command “ip ospf cost 9999”

action 60.0 cli command “end”

 

and a reverse to reduce the cost back in case error rates falls below a threshold?

 

you can also trigger based on IP-SLA, for example below trigger

 

2) Trigger based on RTT delay mib:

Use RTT delay mib associated with RTR probes to trigger when the delay is too long. rttMonLatestJitterOperRTTSum shows the sum of delays for probes sent during the last interval. By default 10 probes are sent. To trigger on 10ms RTT delay trigger value must be set below 100.

 

event manager applet TEST3-SNMP-RTT-Delay trap event snmp oid rttMonLatestJitterOperRTTSum.1 get-type exact entry-op ge entry-val 90 entry-type value exit-op le exit-val 20 poll-interval 10 […]

 

for Ethernet OAM/CFM, you could hook EEM into the syslog messages produced by the syslog? You can also parse the syslog string using regexp, check the applet I found somewhere:

 

event manager applet TunnelLost

event syslog occurs 1 pattern “OSPF-5-ADJCHG.*on Tunnel.*FULL to DOWN”

period 1

action 100 regexp “on (Tunnel[0-9]+) from” “$_syslog_msg” match ifname  action 200 if $_regexp_result eq 1  action 210  cli command “show interface $ifname | include Description:”

 

Veranderen host naam TRA

Changing the Hostname of a Leader Appliance:
1. SSH to the CLI of the Leader Appliance
2. Stop services on the Leader appliance: “services sp stop”
3. Rename the appliance: “service sp device rename old_name new_name”
4. Set the new name on the device: “system name set new_name”
5. Start SP services: “service sp start”
6. Save the configuration: “config write”

1 5 6 7