BFD on interface

Dear all,
Can we configure bfd on interface level for the purpose that if remote IP address is unreachable, bring down the interface.
Regards

Correct, in XR BFD runs as part of an application. The application can be ospf, isis or static.
Tying BFD onto an interface will make you send alerts, traps, syslogs etc, but that is about it.
You can trigger on the syslog message and have EEM shut or unshut an interface if that is the desire, but tying it to an application is more powerful.
For instance, advertising max metric, or bring the routing ADJ down is more graceful in terms of fast convergence routing.
regards
xander

Similar Messages

Bfd support for vrrp interface tracking query !

Hi All
I have a requirement in my typical LAN scenario whereby my LAN server connects in a dual homed fashion to two different LAN switches from a third party vendor. We are using vrrp for the server LAN. The two 3rd party vendor switches are uplinked via L3 links to two c6500. We are tracking the uplink interfaces under vrrp such that no traffic blackholing occurs if the uplink connectivity from master is broken. Now customer has asked to use bfd support in the vrrp uplink interface tracking which is supported by the vendor switches. This topic is confusing to me as what configuration would be required on c6500 to achieve this as the requirement is not to configure bfd for routing protocol but for vrrp interface tracking. As per my understanding BFD works only in integration with routing protocols and there would be no session formed by just enabling BFD under Interface Config. If anyone has any prior experience with implementing such setup please guide me on what needs to be done from c6500 side to achieve this. We are using static routes on c6500 for server LAN reachability and default route on vendor switches towards junos but no bfd for static routing.
Regards Varma

Hi Varma,
your understanding is correct, initially we were supporting BFD in conjunction with BGP/IGPs. Nowadays there's BFD support for VRRP in IOS XR and BFD support for HSRP in IOS. Since you're in multivendor environment, I don't think these options are feasible. You may instead apply subsecond hello timers in VRRP, provided you don't have lots of instances, you should not face a performance burden.
HTH,
Ivan.

IS-IS not working on ASR903.

Hey you all
I have a very strange problem regarding IS-IS routing process on an ASR903 router, that I hope someone can help me with. I am trying to get IS-IS up and running between an ASR903 router and a ME3600X switch. Between the two boxes is a service provider VPLS network. We have IS-IS running on other similar links between this ASR903 and another ME3600X switch also with a VPLS network between. We are running MPLS in our backbone and uses IS-IS as the underlay IGP. It looks like the two IS-IS routers can’t see each other. When I do a debug of isis adj-packets can I see that the ME3600X switch is sending ISIS hellos packets out but does not receive any in. The same debug on the ASR903 do not give anything. It seems like it not even sending ISIS hellos. Logging level debugging is on. The two boxes can ping each other without any problems.
I have tried a couple of things when troubleshooting this problem. I have tried setting the network type to point-to-point, setting the clns mtu, disabled hello padding but nothing worked. I have also tried running OSPF over the link, and it worked without any problems. Then I tried to make a one-hop gre tunnel between them, and then run IS-IS over the gre tunnel and that also worked. When I issue the “show clns interface” command can I see that the “Next IS-IS LAN Level-2 Hello in” is always 0 on the ASR903 router on that interface. On the others interfaces that is running IS-IS the counter is changing. The same on the interface on the ME3600X switch.The software version on the ASR903 is for the IOS-XE is 3.13.1 and the IOS is 15.4(3).S1.
Do you have any idea’s to what the problem could be?
Thanks
Michael H.

Hey Vassilii
Here are the show commands :-)
sh run int gi 0/2/1
interface GigabitEthernet0/2/1
description INX2-ABC 500Mbps
ip address 10.79.171.142 255.255.255.252
ip router isis
negotiation auto
mpls ip
bfd interval 100 min_rx 100 multiplier 3
isis circuit-type level-2-only
isis network point-to-point
isis metric 2000
no isis hello padding
isis bfd disable
end
sh run | sec router isis
router isis
net 01.f84f.5783.1a00.00
is-type level-2-only
metric-style wide
log-adjacency-changes
bfd all-interfaces
mpls ldp sync
sh clns
Global CLNS Information:
9 Interfaces Enabled for CLNS
Configuration Timer: 60, Default Holding Timer: 300, Packet Lifetime 64
ERPDU's requested on locally generated packets
Running IS-IS in IP-only mode (CLNS forwarding not allowed)
NET: 01.f84f.5783.1a00.00
sh clns interface gi 0/2/1
GigabitEthernet0/2/1 is up, line protocol is up
Checksums enabled, MTU 1497, Encapsulation SAP
ERPDUs enabled, min. interval 10 msec.
CLNS fast switching disabled
CLNS SSE switching disabled
DEC compatibility mode OFF for this interface
Next ESH/ISH in 37 seconds
Routing Protocol: IS-IS
    Circuit Type: level-2
    Interface number 0x8, local circuit ID 0x103
    Level-2 Metric: 2000, Priority: 64, Circuit ID: ASR903-AAL01.03
    Level-2 IPv6 Metric: 10
    Number of active level-2 adjacencies: 0
    Next IS-IS Hello in 0 seconds
    No hello padding
    if state DOWN
sh ip protocols
*** IP Routing is NSF aware ***
Routing Protocol is "isis"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: isis
Address Summarization:
    None
Maximum path: 4
Routing for Networks:
    Loopback0
    Loopback1
    BDI602
    BDI3001
    BDI3002
    BDI3100
    BDI1356
    GigabitEthernet0/2/1
    BDI1052
Routing Information Sources:
    Gateway         Distance      Last Update
    100.110.0.19         115      00:02:42
    100.110.0.22         115      00:02:42
    100.110.0.20         115      00:02:42
    100.110.0.21         115      00:02:42
    10.79.144.17         115      00:02:42
    10.79.144.16         115      00:02:42
    10.79.144.15         115      00:02:42
    10.79.144.10         115      00:02:42
Distance: (default is 115)
ping 10.79.171.141
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.79.171.141, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/6/8 ms

Strange Wireshark Capture XR Span

Good afternoon. I am working on Inter-op with a brocade CER and an ASR 9001 and I am running into an issue getting ISIS adjacency up. I was able to solve this on our other systems by paying close attention to wireshark captures of the authentication of Hello and LSP adjacency.
However, when mirroring on the XR, I am getting some strange output. Here is my config:
monitor-session BROCADE ethernet
destination interface GigabitEthernet0/0/0/2
interface GigabitEthernet0/0/0/10
description UPLINK TO BOTTOM BROCADE ETHERNET 2
ipv4 address 10.9.0.94 255.255.255.252
monitor-session BROCADE ethernet
negotiation auto
Here is a screenshot of the packet capture:
http://goo.gl/7xDLxw

Here is the brocade side:
router isis
net 49.0002.0100.0900.0200.00
auth-mode cleartext level-2
auth-key "********" level-2
bfd all-interfaces
log adjacency
log invalid-lsp-packets
set-overload-bit on-startup 30
address-family ipv4 unicast
default-metric 200
metric-style wide
exit-address-family
address-family ipv6 unicast
exit-address-family
interface ethernet 1/2
port-name P2P to West 9001
enable
route-only
ip router isis
ip address 10.9.0.93/30
isis auth-mode cleartext
isis auth-key "********"
isis circuit-type level-2
isis ipv6 metric 200
isis metric 200
isis point-to-point
Here is the Cisco side:
router isis lab
set-overload-bit on-startup 30
net 49.0002.0100.0900.0197.00
nsf ietf
lsp-gen-interval maximum-wait 30000 initial-wait 30000 secondary-wait 30000
lsp-password text encrypted 130232020F3901130F1D0C356205373D11362B425A level 2
address-family ipv4 unicast
metric-style wide
metric 16000000
ispf
default-information originate
address-family ipv6 unicast
metric-style wide
metric 16000000
interface Loopback0
passive
circuit-type level-2-only
address-family ipv4 unicast
   metric 200
interface GigabitEthernet0/0/0/10
circuit-type level-2-only
point-to-point
hello-password text encrypted 121E2007163E093D0E12002E641206290023291555
address-family ipv4 unicast
   metric 200
I have not disabled ISIS authentication because although it is a lab others are working in it and would interrupt some of what they are doing.
So far in the wireshark it looks like I can see hellos from the Cisco, but not from the brocade. Perhaps I am on the wrong support forums? :)

Disable BFD in multiple Router Sub interfaces that participates in OSPF

Hi team,
Please help me on this. Here is the scenario:
We are on an enterprise set up and running on 100+ routers.
We have 200 to 300+ sub interfaces for virtual circuits
Our protocol is OSPF over MPLS
One of our provider in LA encountered link flaps on SONET causing our LA router that is directly connected to that link to recalculate multiple times.
Recalculation of OSPF routes caused disconnection of users in LA VM's.
We were advised by our provider in LA to disable BFD so minor link flaps will no affect recalculation of routes.
We are now tasked by our design team to Disable BFD in multiple Router Sub interfaces that participates in OSPF.
My questions are:
What is the implication in disabling all BFD in routers' interface and sub interface?
Will this improve recalculation of OSPF routes in cause of link flaps or it will totally ignore the link flaps?
Will the routers only recognize a "full down" status of the interface?
How can we Disable BFD in multiple Router Sub interfaces that participates in OSPF in a faster way? Or do we have to do this one by one?
Please advise before we present this to the CAB and implementation. Thank you.

My questions are:
What is the implication in disabling all BFD in routers' interface and sub interface?
Answer: the implication would be eliminating sub-second millisecond convergence.
BFD detect failure at the link layer very fast , once detected it informs the upper layer protocol about the failure causing it to converge immediately.
Will this improve recalculation of OSPF routes in cause of link flaps or it will totally ignore the link flaps?
Answer: if your Provider experiencing intermittent flaps, then yes it will be advisable to turn BFD off. this however doesn't totally ignore the link flaps, once the upper protocol detect the failure based on the dead interval parameter on OSPF, it will recalculate OSPF routes again. Keep in mind, if you have redundant or more links to your provider , then I wouldn't recommend disabling BFD , as it should improve Convergence and you shouldn't notice the failure.
Will the routers only recognize a "full down" status of the interface?
Answer: disabling BFD allows the router recognize a full down status once the upper protocol dead interval occurs or full down status of interface. which ever occurs the earliest.
How can we Disable BFD in multiple Router Sub interfaces that participates in OSPF in a faster way? Or do we have to do this one by one?
You can disable it one by one. or if you have configuration management software, it allows you to do it for all nodes at a time. but this depends if you have it or not.
Please consider not to disable BFD if you have multiple OSPF links towards your provider from any branch, as it shouldn't impact your VMs, it should rather improve Convergence at milliseconds which is absolutely not noticeable.
BR,
Mohamed

Issue in Sub-interface traffic on cisco 7609-s router

Hello please support,
I configured sub-interfaces and it is working properly, but some time sub-interface show traffic more then physical interface .
Like
int gi 3/32 0.13 Mbps 12:00 PM
int gi 3/32.11 855 Mbps 12:00 PM
as per my knowledge physical interface have cumulative traffic of all sub-interfaces.
interface GigabitEthernet3/32
no ip address
interface GigabitEthernet3/32.10
encapsulation dot1Q 10
ip address 172.20.128.77 255.255.255.252
ip ospf network point-to-point
ip ospf bfd
bfd interval 50 min_rx 50 multiplier 5
no bfd echo
no cdp enable
interface GigabitEthernet3/32.11
description interlink MPLS
encapsulation dot1Q 11
ip address 172.20.129.73 255.255.255.252
ip ospf network point-to-point
mpls ip
mpls label protocol ldp
Regards,
Damodar Nagar

I have not that graph so I am just guessing that you are noticing the difference between policing and shaping. It seems to me you are applying these techniques on each platform on a different way. Try to shape/police in the same order or only to shape.
Hope to help
Alessio
Sent from Cisco Technical Support iPad App

LPX issues with LR, BFD, and the GUI looks like Garageband now...

I downloaded LPX a few days ago. Everything worked fine except BFD Eco, which is what I use almost exclusively for drum samples (primarily demo work at this stage).
I also bought an iPad Air per rave reviews of the LR app. Got that setup, and it worked, but as with other users on the forum here, it started to crash on me within moments of turning it on and pairing it with LPX. So I searched the forums and found someone who was advised to delete the .plist files under ~/Library/Preferences, then restart the machine. They were also advised to delete any old .plist files from a previous version of Logic, which I also did.
[Back story: I bought the AC7 Core app a couple years ago to try and perform transport functions from my iPhone. This app "tricks" logic into thinking it's a Mackie interface, so I figure that somewhere during the install, Logic got really confused about my using a Mackie controller which is interfering with my use of the iPad LR app. Other people are having the same issue... seems like a solid bet, right?]
So I deleted the following files:
com.apple.logic10.plist
com.apple.logic.pro.cs
com.apple.logic.pro.plist
And now LPX looks like Garageband. Check it out:
It has those crappy wood panel bars on the left and right, I don't have access to the mix window, I can only see channel strip plugins by using the inspector... this is weird! Which file did I delete that could have caused this? Or am I missing something else?
Additionally, LPX prompted me to download additional Drummer kits AFTER I went through the whole "download additional content" process, telling it to DL anything I didn't already have.
This was all a wild goose chase to reduce latency from my iPad Air to LPX. It can automate faders and sends fine, but playing drum pads and keyboard lines has a noticeable delay (about 50-100ms). So if anyone is willing to help fix the GUI, it would also be super nice if you could give me some pointers on reducing latency & improving stability with the LR.
In case anyone's interested, BFD Eco is still not functioning properly. Bought it in 2011 and apparently I need the 64-bit version. Purchased from fxpansion and now my machine can't find the install script file to actually upgrade my license. eesh.
Nick

Nick,
To get out of GarageBand mode, open your preferences, go to the Advanced tab and be sure to tick "Show Advanced Tools."

Bfd dampening

http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bfd/configuration/xe-3s/irb-xe-3s-book/irb-bfd-damp.html
dampening [ half-life-period reuse-threshold suppress-threshold max-suppress-time]
Example:
Device(config-bfd)# dampening 2 1000 3000 8
err.. so what exactly do these figures mean in plain english?
[ half-life-period reuse-threshold suppress-threshold max-suppress-time]
thank you

See here:
http://www.cisco.com/c/en/us/td/docs/ios/iproute_pi/command/reference/iri_book/iri_pi1.html#wp1011620
half-life-period
(optional) Time (in seconds) after which a penalty is decreased. Once the route has been assigned a penalty, the penalty is decreased by half after the half-life period expires. The range of the half-life period is from 1 to
30 seconds. The default time is 5 seconds.
reuse-threshold
(optional) Reuse value based on the number of penalties. When the accumulated penalty decreases enough to fall below this value, the route is unsuppressed. The range of the reuse value is from 1 to 20000; the default is 1000.
suppress-threshold
(optional) Value of the accumulated penalty that triggers the router to dampen a flapping interface.A route is suppressed when its penalty exceeds this limit. The range is from 1 to 20000; the default is 2000.
max-suppress-time
(optional) Maximum time (in seconds) a route can be suppressed. The range is from 1 to 20000; the default is four times the half-life-period value. If the half-life-period value is allowed to default, the maximum suppress time defaults to 20 seconds.
restart-penalty
(optional) Penalty to applied to the interface when it comes up for the first time after the router reloads. The configurable range is from 1 to 20000 penalties. The default is 2000 penalties. This argument is not required for any other configurations.
hth.

Lowest latency Firewire audio interface for Logic... which should I choose?

Hi Guys,
I'm about to replace my trusty Yamaha n12 with a dedicated firewire audio interface.
My main requirement is super-low latency for running BFD and other virtual instruments, along with monitoring through Logic directly sometimes (to add effects to vocals in real-time, etc).
I've narrowed down my choice (I think!!) to:
- RME Fireface 800
- Apogee Ensemble
- MOTU 896 Mk3
I have been told that the RME drivers are incredible, and hence it has the lowest latency.
I'd love to hear from other Logic users who own any of the above! What kind of latency do you get (round trip in ms)? What is the lowest buffer setting you can use?
Any downfalls or problems you've had with any of these interfaces?
Thanks heaps guys, can't wait to hear some opinions!
Cheers and thanks,
Mike

Thomjinx wrote:
If yeloop is using BFD, then direct monitoring isn't going to help him. That is for audio in.
Exactly.
FWIW, on MOTU Ultralites, I get a little (less than 1 ms) less latency with the Mk 1 rather than the Mk 3.
Perhaps the built-in DSP slows the Mk 3 down?
Interesting--thanks for the info (one more reason not to upgrade MOTU, frankly...)!
It is still 4.3 ms at 32 samples with the Mk 3. For MIDI controlled VIs, it would be less than that.
I think I measured 3.9ms with my Traveler mk2 at 44.1k with a 32 sample buffer. So, it's a bit faster than the mk3. At 96k I can use a 32 sample buffer to get 2.5ms latency, but I can't run BFD2 with a 32 sample buffer. Best I can do with BFD2 is a 64 sample buffer at 96k... 3.16ms.
But, you're exactly right, Thomjinx: with a VI, you won't hear that full amount of latency. Assuming the MIDI latency is negligible, the VI response time will be roughly 1/2 the full analog audio latency. (Logic reports both of the these figures--output latency and full roundtrip latency--if you click on the latency info in the Audio preferences. Be aware, though, that some devices report this information correctly, while others do not. For instance, with the Apogee and Metric Halo products I've used, the numbers reported by Logic are exactly correct, while with MOTU, the numbers shown in Logic are lower than reality: with a 64 buffer at 44.1k the Traveler mk2 indicates 4.3ms roundtrip latency with Logic, but I measured it as 5.6ms... so you may be misled if you try to use the latency values reported by Logic to compare products... in that regard, MOTU seems to cheat, while Apogee and Metric Halo follow the rules
-James

Do BFD or NI Battery plugins work with GB3?

I'm looking for a good software drum package, looking at BFD (awesome sounds and mic set-ups) or Battery.
Can I use these with GB?
Thanks,
S
Mac Book Pro - 17" Mac OS X (10.4.7) Los Angeles Native (one of seven left)

Hey Scott,
Thanks for the reply. I'm REALLY new to this digital recording thing (I do know analog recording though).
Regarding AU: I was reading through the BFD manual and it says that BFD plugs into "your favorite sequencing environment, via the VSTi, DXi, RTAS, AudioUnit and ReWire interfaces."
Now I take it that AU = AudioUnit. Am I right/wrong in thinking this?
Thanks for the info.
Steve
Mac Book Pro - 17" 2GB RAM Mac OS X (10.4.7)
Mac Book Pro - 17" Mac OS X (10.4.7)

Realtime Playing of Guitar Rig thru Logic: FW800 interface?

Hi , it would simplify my life so much to be able to play my N.I. Guitar Rig thru logic as a plugin. I'm about to get the G5 Quad and am wondering about the metric halo 2882(which is FW 400) or the fireface 800. is there a better chance of ultra-low latency thru FW 800 ? I've read that people are playing in realtime through logic , a drummer i spoke with said he's plying the BFD plugin in realtime, so that seems pretty promising, but will i be able to do that with a firewire interface? i have Motu 2408 now but i'm selling it to switch to the quad.

I use GuitarRig all the time and have no latency issues using a Fireface 800. Both the Fireface and the 2882/ULN2 have great and fast converters so there shouldn't be much difference there. However, drivers are the most important. RME's drivers are excellent and the actual hardware does its own metering calculations so you have realtime results in the RME mixer and the host CPU doesn't have to any extra background processing for the driver. I would assume that MH hardware/drivers operate the same way.
One thing to clarify, though, is that you can sum hardware inputs into the DAW mixer using RME's mixer. It's probably a less intuitive process compared to the MH mixer, but it's functionality still resides in RME's TotalMix software.
90% of my sessions are recorded at 24/48 and I usually use a 128 sample buffer without noticeable latency. I've even tried 256 and didn't find it noticeable either. For comparison, I perceive the same amount of latency (which is pretty negligable) when playing through AmpFarm on PT HD Accel, and GuitarRig through the Fireface 800 with a 128 sample buffer (both sessions @ 24/48)
Hope this helps.

Issue using logic pro with bfd 2.0 - not enough RAM?

Right, I posted a little while ago when I first installed BFD 2 on my mac pro, and was having problems whenever I tried to use any effects (either in Logic itself or in the BFD 2 program) whilst using BFD 2. What I think I forgot to mention was I was trying to do different processing on different "areas" of the drum kit, and I wanted to use the Logic effects, so I had a number of tracks with BFD 2 loaded as the instrument.
Well, I phoned a local Apple-certified shop to ask for advice on this, as nothing I'd tried had fixed the issue. The guy suggested I try a clean install of the OS and Logic and BFD 2, to see if that fixed the issue. I* have done this, and logic now works with BFD 2 and effects when I have just one BFD 2 tracks, but as soon as I add another and program some MIDI notes into the 2nd instance, even just a bar or two, then play the whole song, there is a large amount of digital noise. Now, on my mac pro, i only have one HDD - the system disk - and 4 gb ram. I had just now come to the conclusion that, with the minimum spec for Logic being 1GB, and for BFD 2 being 1GB, with the OS running as well it's actually likely the system is short of RAM. But now I see that it can also be an issue if your Logic project is stored on your system disk.
So I'm thinking of getting both an extra, internal (SATA) HDD, and an extra 8GB RAM at least. Is this likely to solve the issue? I'm not currently using an interface with it, and as I say, with just one BFD 2 track, it's fine, the issue is caused when I try to add more BFD 2 tracks. Obviously, without an interface, I am unable to try recording audio to see if there is an issue with that too.

You also need to upgrade to the latest version of BFD2. There were many fixes. You should also install BFD2 samples on another hard drive. The 4 gigs of memory you have is more than enough. Your main problem is probably not installing the samples of a separate drive. Hope this helps. BFD2 is an incredible program once you have it set up properly. As noted previously switching from 24 bit to 16 bits will help also.

%ROUTING-ISIS-4-P2P_CONFIG_MISMATCH : L2 hello-padding configuration on P2P interface Bundle-Ether21

hi,
why this log message keep appearing??
RP/0/RSP0/CPU0:9010-2#
RP/0/RSP0/CPU0:9010-2#RP/0/RSP0/CPU0:Oct 8 14:50:37.023 : isis[1001]: %ROUTING-ISIS-4-P2P_CONFIG_MISMATCH : L2 hello-padding configuration on P2P interface Bundle-Ether21 will not be used
RP/0/RSP0/CPU0:9010-2#
On both side hello padding is disable for level 2.
interface Bundle-Ether22
circuit-type level-2-only
point-to-point
hello-padding disable level 2
hello-password keychain ISIS-key
address-family ipv4 unicast
   metric 10 level 2
   mpls ldp sync level 2
regards
tahir

Router 1 config outup:
RP/0/RSP0/CPU0:9010-1#sh run int bundle-ether 12
Tue Oct 9 14:26:10.591 KSA
interface Bundle-Ether12
description "EtherChannel to 9010-2"
mtu 9216
service-policy output EGRESS-NNI
ipv4 address 10.0.1.30 255.255.255.252
ipv4 unreachables disable
bundle minimum-active links 1
bundle minimum-active bandwidth 10000000
load-interval 30
dampening
RP/0/RSP0/CPU0:9010-1#show isis interface bundle-ether12
Tue Oct 9 14:25:56.600 KSA
Bundle-Ether12              Enabled
Adjacency Formation:      Enabled
Prefix Advertisement:     Enabled
BFD:                      Disabled
BFD Min Interval:         150
BFD Multiplier:           3
Circuit Type:             level-2-only
Media Type:               P2P
Circuit Number:           0
Extended Circuit Number: 134218016
Next P2P IIH in:          9 s
LSP Rexmit Queue Size:    0
Level-2
    Adjacency Count:        1
    LSP Pacing Interval:    33 ms
    PSNP Entry Queue Size: 0
CLNS I/O
    Protocol State:         Up
    MTU:                    9199
    SNPA:                   b414.89e0.9f99
    Layer-2 MCast Groups Membership:
      All ISs:              Yes
IPv4 Unicast Topology:    Enabled
    Adjacency Formation:    Running
    Prefix Advertisement:   Running
    Metric (L1/L2):         10/10
    MPLS LDP Sync (L1/L2): Disabled/Enabled
      Sync Status:          Achieved
IPv4 Address Family:      Enabled
    Protocol State:         Up
    Forwarding Address(es): 10.0.1.30
    Global Prefix(es):      10.0.1.28/30
LSP transmit timer expires in 0 ms
LSP transmission is idle
Can send up to 9 back-to-back LSPs in the next 0 ms
RP/0/RSP0/CPU0:9010-1#
RP/0/RSP0/CPU0:9010-1#
RP/0/RSP0/CPU0:9010-1#sh run router isis
Tue Oct 9 14:26:41.010 KSA
router isis core
net 49.0001.0100.0000.0003.00
nsf cisco
lsp-gen-interval maximum-wait 5000 initial-wait 1 secondary-wait 50 level 2
lsp-refresh-interval 65000 level 2
max-lsp-lifetime 65535 level 2
address-family ipv4 unicast
metric-style wide
spf-interval maximum-wait 5000 initial-wait 1 secondary-wait 50
redistribute static route-policy STATIC-TO-ISIS
redistribute ospf 100 route-policy RP-FROM-OSPF-TO-ISIS
interface Bundle-Ether12
circuit-type level-2-only
point-to-point
hello-padding disable level 2
hello-password keychain ISIS-key
address-family ipv4 unicast
   metric 10 level 2
   mpls ldp sync level 2
Router 2 output config:
RP/0/RSP0/CPU0:9010-2#sh run int bundle-ether 21
Tue Oct 9 14:24:11.346 KSA
interface Bundle-Ether21
description "EtherChannel to 9010-1
mtu 9216
service-policy output EGRESS-NNI
ipv4 address 10.0.1.29 255.255.255.252
bundle minimum-active links 1
bundle minimum-active bandwidth 10000000
dampening
RP/0/RSP0/CPU0:9010-2#
RP/0/RSP0/CPU0:9010-2#show isis interface bundle-ether21
Tue Oct 9 14:23:48.457 KSA
Bundle-Ether21              Enabled
Adjacency Formation:      Enabled
Prefix Advertisement:     Enabled
BFD:                      Disabled
BFD Min Interval:         150
BFD Multiplier:           3
Circuit Type:             level-2-only
Media Type:               P2P
Circuit Number:           0
Extended Circuit Number: 134218208
Next P2P IIH in:          6 s
LSP Rexmit Queue Size:    0
Level-2
    Adjacency Count:        1
    LSP Pacing Interval:    33 ms
    PSNP Entry Queue Size: 0
CLNS I/O
    Protocol State:         Up
    MTU:                    9199
    SNPA:                   0026.980e.d3e2
    Layer-2 MCast Groups Membership:
      All ISs:              Yes
IPv4 Unicast Topology:    Enabled
    Adjacency Formation:    Running
    Prefix Advertisement:   Running
    Metric (L1/L2):         10/10
    MPLS LDP Sync (L1/L2): Disabled/Enabled
      Sync Status:          Achieved
IPv4 Address Family:      Enabled
    Protocol State:         Up
    Forwarding Address(es): 10.0.1.29
    Global Prefix(es):      10.0.1.28/30
LSP transmit timer expires in 0 ms
LSP transmission is idle
Can send up to 9 back-to-back LSPs in the next 0 ms
RP/0/RSP0/CPU0:9010-2#
RP/0/RSP0/CPU0:9010-2#sh run router isis
Tue Oct 9 14:24:41.457 KSA
router isis core
net 49.0001.0100.0000.0002.00
nsf cisco
log adjacency changes
lsp-gen-interval maximum-wait 5000 initial-wait 1 secondary-wait 50 level 2
lsp-refresh-interval 65000 level 2
max-lsp-lifetime 65535 level 2
address-family ipv4 unicast
metric-style wide
spf-interval maximum-wait 5000 initial-wait 1 secondary-wait 50
interface Bundle-Ether21
circuit-type level-2-only
point-to-point
hello-padding disable level 2
hello-password keychain ISIS-key
address-family ipv4 unicast
   metric 10 level 2
   mpls ldp sync level 2

MPLS TE FRR & some BFD

Hi,
I have a few questions:
1. If you have TE tunnel with FRR configured for it, what will trigger the switchover to backup tunnel?
In my mind:
a. Link Protocol down on the interface
b. RSVP signalling
Now two other problematic ones are:
c. IGP neighbor down over a protected link (will it trigger TE reroute WITHOUT using FRR, so IGP neighbors and FRR would be two completely different approaches?)
d. BFD. Is it activated on a specific protected link or on the LSP headend (tailend) to "test" the end-to-end LSP? It is mentioned in BFD docs that when used with TE FRR it can report tunnel down BEFORE the tunnel having sufficient time to be rerouted (because BFD would be acting so fast). Does this mean BFD allows end-to-end LSP testing?
2. More about BFD. The docs say that BFD itself just reports to the protocol employing its services (like IGPs and maybe TE) that the connectivity betweem two points BFD is responsible for is down. If BFD is configured over an interface, does this mean that when BFD senses lack of reachability but Link Protocol stays up (like Ethernet), will it actually bring down the Link Protocol on that particular interface?
If not, it is unclear why would docs also say that BFD is best deployed with Interface Dampening. Interface dampening would work in case Link Protocol flaps...
Thanks!
David

Hi David,
Pls see my what i feel inline...
a. Link Protocol down on the interface
b. RSVP signalling
1(a,b)
Here again RSVP hellos are used as a trigger to achieve the FRR rather than relying on the line protocol to go down.
Which provides us fast upto 50msec protection.
Afaik TE FRR can utilize BFD as its relatively less resource intensive than generating RSVP hellos.
c. IGP neighbor down over a protected link (will it trigger TE reroute WITHOUT using FRR, so IGP neighbors and FRR would be two completely different approaches?)
1(c)
Without using FRR the TE reroute would be pure Tunnel Reoptimization based on your IGP convergence towards your Tunnel TailEnd.
d. BFD. Is it activated on a specific protected link or on the LSP headend (tailend) to "test" the end-to-end LSP? It is mentioned in BFD docs that when used with TE FRR it can report tunnel down BEFORE the tunnel having sufficient time to be rerouted (because BFD would be acting so fast). Does this mean BFD allows end-to-end LSP testing?
1(d)
"BFD can help test end-to-end data plane only just like LSP ping, but there is currently no integration of the results and mapping of the same to control plane in MPLS. hence BFD with LSP ping is being preached. More details can be found at http://www.ietf.org/internet-drafts/draft-ietf-bfd-mpls-03.txt."
2. More about BFD. The docs say that BFD itself just reports to the protocol employing its services (like IGPs and maybe TE) that the connectivity betweem two points BFD is responsible for is down. If BFD is configured over an interface, does this mean that when BFD senses lack of reachability but Link Protocol stays up (like Ethernet), will it actually bring down the Link Protocol on that particular interface?
If not, it is unclear why would docs also say that BFD is best deployed with Interface Dampening. Interface dampening would work in case Link Protocol flaps...
2.
No BFD would not involve itself into getting the link down, it will only enable the protocol bootstrapping or using it to declare a failure.
Now assume if the link is bouncing up and down, or there are intermittent losses because of link intergity. Then BFD would keep sending up down messages to the protocol employing it. Hence if the integration is with Dampening, then such UP or DOWN messages can be considered as flaps in the configured interval and the interface can be dampened. The Dampening as a process would utilize BFD triggers for calculating flaps rather than the Line protocol based UP or DOWN triggers. Thus enabling us to achieve the upto 50ms recovery time which is generally provided by POS/SONET with APS.
HTH-Cheers,
Swaroop

BFD crashes Logic - any ideas?

Hi there. I just bought BFD and installed it on my Mac Pro 2.66 - 2 gigs ram. I had the demo on there before which worked fine. Now whenever I try to play a loop in the interface or drag and drop a midi file onto the arrange page from the BFD interface, Logic crashes. The error log is below. Any ideas? Thank you.
Date/Time: 2007-05-23 21:39:19.243 -0600
OS Version: 10.4.7 (Build 8K1079)
Report Version: 4
Command: Logic Pro
Path: /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MacOS/Logic Pro
Parent: WindowServer [58]
Version: 7.2.0 (954)
Build Version: 4
Project Name: Logic Source Version: 9540000
PID: 5713
Thread: 0
Exception:
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
0 <<00000000>> 0x00000000 0 + 0
1 com.FXpansion.BFDUltra 0x236e7161 BFDCtrlGrooveLibrarian::BFDCtrlGrooveBankList::DoPlayGroove(int) + 365
2 com.FXpansion.BFDUltra 0x236e7313 BFDCtrlGrooveLibrarian::BFDCtrlGrooveBankList::OnMouseLButtonDown(VFoundation:: SPoint const&, long) + 217
3 com.FXpansion.BFDUltra 0x23824950 VCtrl::CtrlRoot::OnMouseLButtonDown(VFoundation::SPoint const&, long) + 472
4 com.FXpansion.BFDUltra 0x238204f5 VCtrl::CtrlRoot::MacOSX_EventHandlerProc(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1685
5 com.apple.HIToolbox 0x91bdf86b DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1093
6 com.apple.HIToolbox 0x91bdef10 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
7 com.apple.HIToolbox 0x91be61f0 SendEventToEventTarget + 56
8 com.apple.HIToolbox 0x91be6683 ToolboxEventDispatcherHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 1169
9 com.apple.HIToolbox 0x91bdfc22 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 2044
10 com.apple.HIToolbox 0x91bdef10 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 304
11 com.apple.HIToolbox 0x91be61f0 SendEventToEventTarget + 56
12 com.apple.HIToolbox 0x91c2a0c7 ToolboxEventDispatcher + 81
13 com.apple.HIToolbox 0x91c28adf RunApplicationEventLoop + 165
14 com.apple.logic.pro 0x001b9e93 0x1000 + 1805971
15 com.apple.logic.pro 0x00010dff 0x1000 + 65023
16 com.apple.logic.pro 0x0000b76e 0x1000 + 42862
17 com.apple.logic.pro 0x0000b689 0x1000 + 42633
Thread 1:
0 libSystem.B.dylib 0x9000a277 machmsgtrap + 7
1 com.apple.CoreFoundation 0x902a52f3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x902b61c8 CFRunLoopRun + 60
3 com.apple.logic.pro 0x0006452f 0x1000 + 406831
4 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 2:
0 libSystem.B.dylib 0x9000a277 machmsgtrap + 7
1 com.apple.CoreFoundation 0x902a52f3 CFRunLoopRunSpecific + 2014
2 com.apple.CoreFoundation 0x902a4b0e CFRunLoopRunInMode + 61
3 com.apple.audio.CoreAudio 0x9082841e HALRunLoop::OwnThread(void*) + 158
4 com.apple.audio.CoreAudio 0x90828239 CAPThread::Entry(CAPThread*) + 93
5 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 3:
0 libSystem.B.dylib 0x90024e47 semaphorewait_signaltrap + 7
1 com.apple.logic.pro 0x00505d7a 0x1000 + 5262714
2 com.apple.logic.pro 0x00505e37 0x1000 + 5262903
3 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 4:
0 libSystem.B.dylib 0x90024e47 semaphorewait_signaltrap + 7
1 com.apple.logic.pro 0x00505d7a 0x1000 + 5262714
2 com.apple.logic.pro 0x00505e37 0x1000 + 5262903
3 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 5:
0 libSystem.B.dylib 0x90024e47 semaphorewait_signaltrap + 7
1 com.apple.logic.pro 0x00502146 0x1000 + 5247302
2 com.apple.logic.pro 0x00502203 0x1000 + 5247491
3 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 6:
0 libSystem.B.dylib 0x90024e47 semaphorewait_signaltrap + 7
1 com.apple.logic.pro 0x00502146 0x1000 + 5247302
2 com.apple.logic.pro 0x00502203 0x1000 + 5247491
3 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 7:
0 libSystem.B.dylib 0x90049467 semaphoretimedwait_signaltrap + 7
1 com.apple.audio.CoreAudio 0x9083565c CAGuard::WaitFor(unsigned long long) + 212
2 com.apple.audio.CoreAudio 0x9083557e CAGuard::WaitUntil(unsigned long long) + 66
3 com.apple.audio.CoreAudio 0x90833efa HP_IOThread::WorkLoop() + 690
4 com.apple.audio.CoreAudio 0x90833c43 HPIOThread::ThreadEntry(HPIOThread*) + 17
5 com.apple.audio.CoreAudio 0x90828239 CAPThread::Entry(CAPThread*) + 93
6 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 8:
0 libSystem.B.dylib 0x90024e47 semaphorewait_signaltrap + 7
1 com.apple.logic.pro 0x000f93e9 0x1000 + 1016809
2 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 9:
0 libSystem.B.dylib 0x90024e47 semaphorewait_signaltrap + 7
1 com.apple.logic.pro 0x000f82c8 0x1000 + 1012424
2 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 10:
0 libSystem.B.dylib 0x90049467 semaphoretimedwait_signaltrap + 7
1 ...ple.CoreServices.CarbonCore 0x904060a7 TSWaitOnSemaphoreCommon + 163
2 ...ple.CoreServices.CarbonCore 0x9040d099 TimerThread + 87
3 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 11:
0 libSystem.B.dylib 0x9000a277 machmsgtrap + 7
1 com.apple.audio.midi.CoreMIDI 0x9670393b XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
2 com.apple.audio.midi.CoreMIDI 0x966fbe8d MIDIInPortThread::Run() + 113
3 com.apple.audio.midi.CoreMIDI 0x966fcb6d XThread::RunHelper(void*) + 17
4 com.apple.audio.midi.CoreMIDI 0x967044ad CAPThread::Entry(CAPThread*) + 93
5 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 12:
0 libSystem.B.dylib 0x90024e47 semaphorewait_signaltrap + 7
1 com.apple.Foundation 0x90aca2f8 -[NSConditionLock lockWhenCondition:] + 39
2 com.apple.AppKit 0x921a0270 -[NSUIHeartBeat _heartBeatThread:] + 377
3 com.apple.Foundation 0x90a7436c forkThreadForFunction + 123
4 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 13:
0 libSystem.B.dylib 0x900380b7 machwaituntil + 7
1 libSystem.B.dylib 0x9003a782 usleep + 82
2 com.FXpansion.BFDUltra 0x23802d9f VFoundation::VThread::Sleep(long) + 29
3 com.FXpansion.BFDUltra 0x237e7e07 VFoundation::VJobServer::ServerThreadProxy(void*) + 275
4 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 14:
0 libSystem.B.dylib 0x900380b7 machwaituntil + 7
1 libSystem.B.dylib 0x9003a782 usleep + 82
2 com.FXpansion.BFDUltra 0x23802d9f VFoundation::VThread::Sleep(long) + 29
3 com.FXpansion.BFDUltra 0x237e7e07 VFoundation::VJobServer::ServerThreadProxy(void*) + 275
4 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 15:
0 libSystem.B.dylib 0x900272dc kevent + 12
1 ...ple.CoreServices.CarbonCore 0x903dcf84 PrivateMPEntryPoint + 51
2 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 16:
0 libSystem.B.dylib 0x90024e47 semaphorewait_signaltrap + 7
1 ...ple.CoreServices.CarbonCore 0x903dd129 MPWaitOnQueue + 198
2 com.apple.DesktopServices 0x90991b5b TNodeSyncTask::SyncTaskProc(void*) + 143
3 ...ple.CoreServices.CarbonCore 0x903dcf84 PrivateMPEntryPoint + 51
4 libSystem.B.dylib 0x900247a7 pthreadbody + 84
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x1c4e1030 ebx: 0x23871989 ecx: 0x2372e11f edx: 0x00000000
edi: 0x00000051 esi: 0x00000066 ebp: 0xbffff2d8 esp: 0xbffff29c
ss: 0x0000001f efl: 0x00010202 eip: 0x00000000 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
Binary Images Description:
0x1000 - 0xcf5fff com.apple.logic.pro 7.2.0 (954) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MacOS/Logic Pro
0x1374000 - 0x13ccfff com.apple.LogicLoopBrowser 7.2 (17) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Frameworks/LogicLoopBrowser.framework/Versions/A/LogicLoopBrow ser
0x1505000 - 0x159cfff com.apple.eloop 3.0 (23) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Frameworks/ELoop.framework/Versions/A/ELoop
0x162d000 - 0x1637fff libaafintp.dylib /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Frameworks/libaafintp.dylib
0x1646000 - 0x1697fff libaafpgapi.dylib /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Frameworks/libaafpgapi.dylib
0x16ca000 - 0x172ffff com.apple.ecore 1.0.0 (43) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Frameworks/ECore.framework/Versions/A/ECore
0x1778000 - 0x178ffff com.apple.EHardwareSupport 1.0.0 (21) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Frameworks/EHardwareSupport.framework/Versions/A/EHardwareSupp ort
0x2008000 - 0x220cfff libcom-api.dylib /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Frameworks/libcom-api.dylib
0x277f000 - 0x27a1fff com.apple.prokit.TigerPanels 3.1.1 (591) /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/TigerPa nels.bundle/Contents/MacOS/TigerPanels
0x18e5a000 - 0x18e62fff com.apple.iokit.IOUSBLib 2.6.0 /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Co ntents/MacOS/IOUSBLib
0x18e6e000 - 0x18e73fff com.apple.audio.AppleHDAHALPlugIn 1.2.4 (1.2.4a19) /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bun dle/Contents/MacOS/AppleHDAHALPlugIn
0x19935000 - 0x19939fff com.apple.gal_anvil 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/anvil.res/Contents/MacOS/anvil
0x19a34000 - 0x19a3afff com.apple.gal_efx 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/efx.res/Contents/MacOS/efx
0x19fd8000 - 0x19fdafff com.apple.gal_egt 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/egt.res/Contents/MacOS/egt
0x1a00b000 - 0x1a00dfff com.apple.gal_emx 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/emx.res/Contents/MacOS/emx
0x1a0d9000 - 0x1a0dbfff com.apple.gal_es1 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/es1.res/Contents/MacOS/es1
0x1a13e000 - 0x1a140fff com.apple.gal_es2 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/es2.res/Contents/MacOS/es2
0x1a1cf000 - 0x1a1d0fff com.apple.gal_esu 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/esu.res/Contents/MacOS/esu
0x1a222000 - 0x1a224fff com.apple.gal_evb3 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/evb3.res/Contents/MacOS/evb3
0x1a2b4000 - 0x1a2b6fff com.apple.gal_evd6 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/evd6.res/Contents/MacOS/evd6
0x1a31f000 - 0x1a321fff com.apple.gal_evoc 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/evoc.res/Contents/MacOS/evoc
0x1a414000 - 0x1a416fff com.apple.gal_evp88 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/evp88.res/Contents/MacOS/evp88
0x1a567000 - 0x1a569fff com.apple.gal_exs24 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/exs24.res/Contents/MacOS/exs24
0x1a5e1000 - 0x1a5e5fff com.apple.gal_revolver 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/revolver.res/Contents/MacOS/revolver
0x1a739000 - 0x1a73bfff com.apple.gal_sphere 1.0 (15) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/Resources/sphere.res/Contents/MacOS/sphere
0x229f4000 - 0x22a30fff com.apple.QuickTimeFireWireDV.component 7.1.2 /System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/MacOS/QuickTim eFireWireDV
0x22a3c000 - 0x22a55fff com.apple.AppleIntermediateCodec 1.1 (141) /Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS/AppleInterme diateCodec
0x22a5a000 - 0x22a73fff com.apple.applepixletvideo 1.2.9 (1.2d9) /System/Library/QuickTime/ApplePixletVideo.component/Contents/MacOS/ApplePixlet Video
0x22ec9000 - 0x230bcfff net.telestream.wmv.import 2.1.0.33 /Library/QuickTime/Flip4Mac WMV Import.component/Contents/MacOS/Flip4Mac WMV Import
0x234be000 - 0x234c0fff com.apple.MIDIDevicePlugIn.CS-32 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/CS-32.bundle/Contents/MacOS/CS-32
0x234cc000 - 0x234cffff com.apple.MIDIDevicePlugIn.FW-1884 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/FW-1884.bundle/Contents/MacOS/FW-1884
0x234e6000 - 0x234eafff com.apple.MIDIDevicePlugIn.HUI 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/HUI.bundle/Contents/MacOS/HUI
0x23535000 - 0x23536fff com.apple.MIDIDevicePlugIn.iControl 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/iControl.bundle/Contents/MacOS/iControl
0x23541000 - 0x23547fff com.apple.MIDIDevicePlugIn.Logic Control 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/Logic Control.bundle/Contents/MacOS/Logic Control
0x2357c000 - 0x2357efff com.apple.MIDIDevicePlugIn.microKONTROL 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/microKONTROL.bundle/Contents/MacOS/microKONTROL
0x2358c000 - 0x2358efff com.apple.MIDIDevicePlugIn.TranzPort 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/TranzPort.bundle/Contents/MacOS/TranzPort
0x23598000 - 0x2359afff com.apple.MIDIDevicePlugIn.US-2400 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/US-2400.bundle/Contents/MacOS/US-2400
0x235a5000 - 0x235a6fff com.apple.MIDIDevicePlugIn.US-428 1.0 (9) /Users/aaronpenton/Desktop/Logic Pro.app/Contents/MIDI Device Plug-ins/US-428.bundle/Contents/MacOS/US-428
0x23667000 - 0x23695fff com.vst_au.instruments.bfdultra ??? (1.0.0.0) /Library/Audio/Plug-Ins/Components/BFDultra.component/Contents/MacOS/BFDUltraCo mponent
0x236d3000 - 0x238cefff com.FXpansion.BFDUltra 1.5.0.45 (1.5.45) /Library/Audio/Plug-Ins/VST/BFD Ultra.vst/Contents/MacOS/BFD Ultra
0x8fe00000 - 0x8fe49fff dyld 46.8 /usr/lib/dyld
0x90000000 - 0x9016ffff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x90218000 - 0x90255fff com.apple.CoreText 1.1.1 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
0x90283000 - 0x9034bfff com.apple.CoreFoundation 6.4.6 (368.27) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x903a2000 - 0x90648fff com.apple.CoreServices.CarbonCore 682.14 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
0x906cb000 - 0x9073efff com.apple.framework.IOKit 1.4.6 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
0x90757000 - 0x907bffff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x90814000 - 0x90814fff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
0x90817000 - 0x9088dfff com.apple.audio.CoreAudio 3.0.4 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
0x908df000 - 0x908dffff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
0x908e2000 - 0x90961fff libobjc.A.dylib /usr/lib/libobjc.A.dylib
0x9098f000 - 0x90a0cfff com.apple.DesktopServices 1.3.4 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
0x90a57000 - 0x90c87fff com.apple.Foundation 6.4.7 (567.2Cool /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x90db0000 - 0x90dc7fff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
0x90ddc000 - 0x90e34fff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
0x90e4f000 - 0x90e75fff com.apple.SystemConfiguration 1.8.6 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x90e8a000 - 0x90e8afff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x90e8d000 - 0x90e99fff com.apple.opengl 1.4.11 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
0x90ea0000 - 0x90ebbfff com.apple.DirectoryService.Framework 3.2 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
0x90f31000 - 0x90f31fff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x90f6e000 - 0x90fb6fff com.apple.bom 8.5 (86.3) /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x9102a000 - 0x91040fff com.apple.LangAnalysis 1.6.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
0x91053000 - 0x9105ffff com.apple.speech.synthesis.framework 3.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
0x9106a000 - 0x910cdfff com.apple.htmlrendering 66.1 (1.1.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
0x910fd000 - 0x911a6fff com.apple.QD 3.10.20 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
0x911e5000 - 0x91258fff com.apple.print.framework.PrintCore 4.6 (177.13) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
0x912a4000 - 0x912acfff com.apple.speech.recognition.framework 3.6 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
0x912b8000 - 0x912d6fff com.apple.openscripting 1.2.5 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x912ef000 - 0x912fffff com.apple.ImageCapture 3.0.4 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x91316000 - 0x9131afff com.apple.help 1.0.3 (32.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
0x91320000 - 0x91325fff com.apple.CommonPanels 1.2.3 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
0x9132e000 - 0x91334fff com.apple.print.framework.Print 5.2 (192.4) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x9133e000 - 0x91344fff com.apple.securityhi 2.0.1 (24742) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
0x91350000 - 0x91391fff com.apple.NavigationServices 3.4.4 (3.4.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
0x913c3000 - 0x913d2fff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
0x913dc000 - 0x913e7fff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
0x9143c000 - 0x91456fff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x9145e000 - 0x91718fff com.apple.QuickTime 7.1.2 /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
0x918a1000 - 0x918bcfff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
0x918cf000 - 0x91a6efff com.apple.security 4.4.1 (27569) /System/Library/Frameworks/Security.framework/Versions/A/Security
0x91b82000 - 0x91bbffff com.apple.LaunchServices 181 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
0x91bd7000 - 0x91ecbfff com.apple.HIToolbox 1.4.8 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x92033000 - 0x9207efff com.apple.HIServices 1.5.2 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
0x920b2000 - 0x92768fff com.apple.AppKit 6.4.8 (824.42) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x92aea000 - 0x92f3ffff com.apple.CoreGraphics 1.258.34 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x9301f000 - 0x93035fff libcups.2.dylib /usr/lib/libcups.2.dylib
0x9303b000 - 0x93181fff com.apple.AddressBook.framework 4.0.4 (485.1) /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
0x932ac000 - 0x932d5fff com.apple.LDAPFramework 1.4.2 (69.1.1) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
0x932e1000 - 0x932f1fff com.apple.WebServices 1.1.3 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
0x93302000 - 0x93302fff com.apple.DiscRecording 3.1.4 (???) /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x93489000 - 0x934a6fff libresolv.9.dylib /usr/lib/libresolv.9.dylib
0x934af000 - 0x9352efff com.apple.SearchKit 1.0.5 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
0x935a1000 - 0x9367ffff libxml2.2.dylib /usr/lib/libxml2.2.dylib
0x936af000 - 0x93740fff com.apple.ink.framework 101.2.1 (71) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
0x93d28000 - 0x93d6afff com.apple.DiscRecordingContent 3.1.4 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingContent.framework/Versions/A/DiscRecordingContent
0x93d83000 - 0x93e01fff com.apple.DiscRecordingEngine 3.1.4 /System/Library/Frameworks/DiscRecording.framework/Versions/A/Frameworks/DiscRe cordingEngine.framework/Versions/A/DiscRecordingEngine
0x93e39000 - 0x94268fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
0x9441a000 - 0x947cefff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
0x94806000 - 0x9485ffff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
0x94df3000 - 0x94ee6fff libicucore.A.dylib /usr/lib/libicucore.A.dylib
0x94f4e000 - 0x95000fff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
0x9505d000 - 0x95082fff libssl.0.9.7.dylib /usr/lib/libssl.0.9.7.dylib
0x95099000 - 0x95186fff libiconv.2.dylib /usr/lib/libiconv.2.dylib
0x9518c000 - 0x9519bfff libsasl2.2.dylib /usr/lib/libsasl2.2.dylib
0x951e1000 - 0x951e9fff com.apple.DiskArbitration 2.1.1 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
0x951f2000 - 0x95204fff libauto.dylib /usr/lib/libauto.dylib
0x953f6000 - 0x9546ffff com.apple.CoreData 90 /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
0x95571000 - 0x9558ffff com.apple.Metadata 10.4.4 (121.36) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
0x95630000 - 0x95632fff com.apple.ExceptionHandling 1.2 (???) /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHand ling
0x95970000 - 0x959b1fff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
0x95a53000 - 0x95a55fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x95a5b000 - 0x95b2ffff com.apple.ColorSync 4.4.6 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
0x95b78000 - 0x95b87fff com.apple.DSObjCWrappers.Framework 1.1 /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
0x95b90000 - 0x95b9efff com.apple.audio.SoundManager 3.9.1 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
0x95bbb000 - 0x95be7fff com.apple.AE 314 (313) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
0x95c05000 - 0x95c43fff com.apple.CFNetwork 129.16 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
0x95c5b000 - 0x95c5bfff com.apple.Accelerate 1.3 (Accelerate 1.3) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
0x95c5e000 - 0x95d30fff com.apple.prokit 3.1.1 (591) /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x95d68000 - 0x95df6fff com.apple.vImage 2.5 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
0x95e67000 - 0x95f3cfff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
0x95fa4000 - 0x95fabfff libbsm.dylib /usr/lib/libbsm.dylib
0x966f7000 - 0x9672dfff com.apple.audio.midi.CoreMIDI 1.5.1 (41) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x96b48000 - 0x96b48fff com.apple.Accelerate.vecLib 3.3 (vecLib 3.3) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
0x96bd4000 - 0x96bd4fff com.apple.vecLib 3.3 (vecLib 3.3) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
0x96c60000 - 0x96c98fff com.apple.ImageIO.framework 1.4.7 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
0x96cad000 - 0x96cb1fff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
0x96cb4000 - 0x96d12fff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x96d26000 - 0x96d42fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
0x96e15000 - 0x96e2ffff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
0x96e35000 - 0x96e37fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
0x96e3a000 - 0x96e95fff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
0x96e9a000 - 0x96ed7fff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
0x96f99000 - 0x96fd3fff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
0x970e2000 - 0x970e7fff com.apple.agl 2.5.9 (AGL-2.5.9) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
0x97109000 - 0x971c1fff com.apple.audio.toolbox.AudioToolbox 1.4.3 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
0x9720c000 - 0x9720cfff com.apple.audio.units.AudioUnit 1.4.2 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
0x9720f000 - 0x973e1fff com.apple.QuartzCore 1.4.9 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
0x9904d000 - 0x99bf9fff com.apple.QuickTimeComponents.component 7.1.2 /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTim eComponents
0x99e0f000 - 0x99e11fff com.apple.QuickTimeH264.component 7.1.2 /System/Library/QuickTime/QuickTimeH264.component/Contents/MacOS/QuickTimeH264
0x9a124000 - 0x9a1e0fff com.apple.QuickTimeMPEG4.component 7.1.2 /System/Library/QuickTime/QuickTimeMPEG4.component/Contents/MacOS/QuickTimeMPEG 4
0x9d6f8000 - 0x9d75cfff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
0x9de32000 - 0x9de56fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
0x9e109000 - 0x9e110fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
0x9e94f000 - 0x9e95dfff libz.1.dylib /usr/lib/libz.1.dylib
Model: MacPro1,1, BootROM MP11.005C.B00, 4 processors, Dual-Core Intel Xeon, 2.66 GHz, 2 GB
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: DIMM Riser A/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz
Memory Module: DIMM Riser A/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz
PCI Card: NVIDIA GeForce 7300 GT, Display, Slot-1
Serial ATA Device: ST3250824AS P, 232.89 GB
Parallel ATA Device: SONY DVD RW DW-D150A, 4.31 GB
USB Device: Hub in Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 500 mA
USB Device: Apple Optical USB Mouse, Mitsumi Electric, Up to 1.5 Mb/sec, 100 mA
USB Device: XSKey, Emagic GmbH, Up to 1.5 Mb/sec, 100 mA
USB Device: Apple Pro Keyboard, Mitsumi Electric, Up to 12 Mb/sec, 250 mA
FireWire Device: PreSonus FIREPOD, PreSonus, Up to 400 Mb/sec
FireWire Device: built-in_hub, unknown_value, Unknown

Hey Grynch,
The crash log is totally Greek to me, but here are some suggestions, especially considering that the demo worked perfect for you.
1. Is the installed version the latest version of BFD? Depending on where you purchased and all that, it could be an older version of BFD that was on the disc. Make sure you've downloaded all the updates.
2. Did you run the installer or did you do it manually? When I got BFD quite a while ago, it was recommended that Mac users installed the Data pieces (i.e., all the samples) manually just by dragging and dropping to the desired location. That may be something to look at as well.
That's what I would start with. Hope that helps.

BFD on interface

Similar Messages

Maybe you are looking for