Proper routing of outboard gear

External hardware compressor question.
i have an issues with something that seems should be pretty straight forward to me.
I just got a first outboard compressor. I worked for years now ITB using plugs and a few pre amps with my Fireface 800 interface.
Well I got a overstayer stereo bus compressor, that was recommended to me.
I also have a UA pre with a T4 optical compressor but I have used it only on the actual pre inputs and not using it's line in.
OK So I got the compressor, hooked it up via Fireface 3/4 inputs and 3/4 outputs. (out of the comp to in of the ff and vice versa)
I fired up Logic, took a overhead stereo track and sent it to bus 1.
On bus one I inserted the I/O with 3/4 as inputs and 3/4 as outputs. So now, if I am understanding correctly Logic should be sending its out thru the FF to the compressor and back into the daw.
Well, I hear the return sound, if I set the OH drum track to pre fader and turn it down, I hear that same signal. When I turn up the OH track, you can hear the two tracks sounding weird, either due to latency (thiner, slightly doubled sound). I imagine that this would have to be fixed with the sample delay control right with in the I/O plug in, I don't know how to do that but I will try to find it in the forums.
My question actually has to do with the sound that I think is coming back from the compressor. I hear no compression, changing the input or output does not change the sound. I have worked with compression in the box long enough that I can hear it when it's subtle applied but this signal has none of it.
SO what am I doing wrong? I know I am a noob when it comes to outboard gear but what else is there to do? Am I supposed to route something with in the environment, am I screwing up something with in the FF800 mixer, I really have no idea.
Any insight would be appreciated.

Hi,
Instead of using a buss object (track)
Do the following :
Assign the output of the track to be compressed (mono?) to another output that is not your main 1-2.
Example : MONO audio track.
Route "Kick" track to outboard compressor, and back into Logic.
Assign Kick track main output to output 3 (mono).
Patch your output 3 from your interface to the input of your compressor.
Patch the output of your compressor into Input 3 of your interface.
Inside Logic, create a new MONO AUX track, and assign it's input as input 3.
Now, play back the kick, and set your compressor the way you like it.
The only issue you will have, is the roundtrip latency.
So, once you have the kick sounding the way you like, you might want to create a new audio track, and record the signal into it, so you can then move it back to where it should be.
"Logic don't do latency compensation for external hardware" and anyone else telling you otherwise is insane.
Cheers

Similar Messages

  • Outboard gear and logic.

    I wanted to start using some out board gear for my mixes....mostly reverb effects, only thing is - if you were to try and do a bus method you would need an interface with a bus output (or some sort of send return routing options) right?
    It seems that most interfaces or controllers only have outputs. Long story short, I don't want to mix 100% in the box or 100% on some analog board, I want to be in-between these two things.
    I think digi design has a bunch of controller boards with these options, but it seems that logic doesn't support any controllers with a send return routing option (a bus out put on the back to be simple about it).
    Please share your knowledge relative to routing to outboard gear from Logic...but not just simple output input stuff.... I want to blend dry signal with wet signal.
    Sorry if I worded this in a confusing way? And thanks for any help.

    yea but if you make the output of a channel a send out, the only return you could get is a wet signal...no blend option.
    After thinking about it, it seems that you could duplicate a track and do what you mentioned and have one be dry and the other sending to outboard effects. The fader sending to the effect could be be similar to a buss send (on whatever channel it would return on). Not sure how that would sound.
    I think one could also buss the signal to an aux, have the output of that aux send to outboard gear and return on an additional aux...but at that point it seems pretty complex...one track, two aux's...there's got to be a better way.

  • Help on Logic 9 with outboard gear?

    I use logic pro 9 and although plugins are great i wanted to use my outboard compressors and eq's such as my avalon on audio and midi tracks ive already recorded. how do i go about routing my tracks to go out of my control surface into my outboard gear and back into logic?

    Route the aux busses to the other (non 1-2) outputs of your audio interface, which should either be
    patched into either channels on your mixing console (so that you can use the mixer's aux sends to address your FX hardware), or
    patched directly into the FX hardware's inputs.

  • Using Outboard Gear With M-Audio Fast Track Pro And Logic Express

    My Fast Track Pro has 2 insert jacks on the back where you can run a send and return to use outboard gear. The cable you use has 2 female 1/4" jacks (one is send and the other is return) that go to a 1/4" male jack that you plug into the back of the interface.
    My question is this:
    How can I get Logic Express to send a track through the outboard gear connected to my interface? On the track's output settings in Logic there are "Output 1+2", which run to my monitors I think, and "Output 3+4", which don't have anything plugged into them. There don't appear to be any other options for sending the track. How can I get Logic to recognize the Inserts jack on the Fast Track Pro? I'm running all the latest drivers if that means anything. Any help is much appreciated.

    Thanks for helping me on this. I'm still a bit confused on how to send the channel through the insert. The jacks on the back of my interface are "TRS Output 1+2" (my monitors are plugged into these outputs), a RCA "Output 1,2,3, and 4", an S/PDIF out and in, and then 2 TRS inserts jacks, marked 1 and 2. Each jack does it's own separate send and return which is why I had to buy the cable with the 2 female jacks on it.
    I've been able to use the I/O plugin and get the track to accept a signal from the insert on input 1 (I have a looping pedal running in the send chain and was able to get it to play a loop over top of the audio already recorded on the channel), but am unable to send the recorded track through the fx send. What would I need to set the output to to be able to do this? Thanks for your time.

  • Latency when using outboard gear

    Hi! Can anyone tell me how to fix the delay in sound when using outboard gear insertet on a Logic track??
    I have set latency compensation to "All", still the signal is clearly delayed.
    I'm using Logic Pro 8 with a Digi 002 audio interface.

    http://www.collective.co.uk/expertsleepers/latencyfixer.html

  • Logic, Ensemble, and outboard gear

    Hi,
    I am experiencing a strange problem with Logic Express, my drum machine and some outboard synths. I have searched on here, the LUG, Apple discussions, and even asked at another producers forum, and haven't quite gotten an answer.
    The problem goes like so. When I record my parts in from my MIDI synths thru the Ensemble, the recordings come in early by about 1200 samples. Considering that latency is usually the issue, how is this possible?
    It is so annoying and discouraging to have to time correct all my parts to get them to loop correctly, that I am nearly in tears over it. Does anyone have any insight at all as to how this can be corrected (and safely? I tried delay recording, but that makes me feel uneasy)??
    I read all about plugin delay compensation and have tried all settings possible and tested each one, none helps.
    My setup is iMac G5 1.8, Logic Express 7.2.3 on OS X 10.4.9, Jomox xBase09, and and an SE-1x
    help, please, as I dont want to think that even Ableton Live is better than Logic with MIDI synths.

    Route the aux busses to the other (non 1-2) outputs of your audio interface, which should either be
    patched into either channels on your mixing console (so that you can use the mixer's aux sends to address your FX hardware), or
    patched directly into the FX hardware's inputs.

  • Using Eventide Eclipse as outboard gear with Logic Pro 8/9

    Hi, people,
    Anyone using Eventide's Eclipse as outboard FX box with Logic Pro? I'm thinking of getting one and running it via digital I/O into my RME Fireface 800. Any info appreciated.
    Thanks, Scorpii.

    Yes it is possible, first connect your outboard to the soundcard.....then load the I/O (inserts) plug in on the track you want to process....you can find it in the utility menu....then set the routing of the signal in the I/O window....if you want to record the processed track create a new track with the right routing and the work is done.hope this replay help you . Regards

  • Proper routing for lan through verizon private network (GRE) to airlink gateways

    Okay, I give up, and think I have done my due diligence (I have been engrossed and fascinated spending many more hours than allotted to try and learn some of the finer details).  Time for some advice.  My usual trade is controls engineering which generally require only basic knowledge of networking principals.  However I recently took a job to integrate 100 or so lift stations scattered around a county into a central SCADA system.  I decided to use cellular technology to connect these remote sites back to the main SCADA system.  Well the infrastructure is now in and it’s time to get these things talking.  Basic topology description is as follows:  Each remote site has an Airlink LS300 gateway.  Attached to the gateway via Ethernet is a system controller that I will be polling via Modbus TCP from the main SCADA system.  The Airlinks are provisioned by Verizon utilizing a private network with static IP's.  This private networks address is 192.168.1.0/24.  Back at the central office the SCADA computer is sitting behind a Cisco 2911.  The LAN address of the central office is 192.168.11.0/24.  The 2911 is utilizing GRE tunnels that terminate with Verizon.  The original turn up was done with another contractor that did a basic config of the router which you will find below.  As it stands now I am pretty confident the tunnels are up and working (if I change a local computers subnet to 255.255.0.0 I can surprisingly reach the airlinks in the field), but this is obviously not the right way to solve the problem, not to mention I was unable to successfully poll the end devices on the other side of the Airlinks.  I think I understand just about every part of the config below and think it is just missing a few items to be complete.  I would greatly appreciate anyone’s help in getting this set up correctly.  I also have a few questions about the set up that still don’t make sense to me, you will find them below the config.  Thanks in advance.
    no aaa new-model
    ip cef
    ip dhcp excluded-address 10.10.10.1
    ip dhcp pool ccp-pool
     import all
     network 10.10.10.0 255.255.255.248
     default-router 10.10.10.1 
     lease 0 2
    ip domain name yourdomain.com
    no ipv6 cef
    multilink bundle-name authenticated
    username cisco privilege 15 one-time secret 
    redundancy
    crypto isakmp policy 1
    encr 3des
    hash md5
     authentication pre-share
     group 2
    crypto isakmp key AbCdEf01294 address 99.101.15.99  
    crypto isakmp key AbCdEf01294 address 99.100.14.88 
    crypto ipsec transform-set VZW_TSET esp-3des esp-md5-hmac 
    mode transport
    crypto map VZW_VPNTUNNEL 1 ipsec-isakmp 
     description Verizon Wireless Tunnel
     set peer 99.101.15.99
     set peer 99.100.14.88
     set transform-set VZW_TSET 
     match address VZW_VPN
    interface Tunnel1
     description GRE Tunnel to Verizon Wireless
     ip address 172.16.200.2 255.255.255.252
     tunnel source 22.20.19.18
     tunnel destination 99.101.15.99
    interface Tunnel2
    description GRE Tunnel 2 to Verizon Wireless
     ip address 172.16.200.6 255.255.255.252
     tunnel source 22.20.19.18
     tunnel destination 99.100.14.88
    interface Embedded-Service-Engine0/0
     no ip address
     shutdown
    interface GigabitEthernet0/0
     description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
     ip address 10.10.10.1 255.255.255.248
     shutdown
     duplex auto
     speed auto
    interface GigabitEthernet0/1
     ip address 192.168.11.1 255.255.255.0
     duplex auto
     speed auto
    interface GigabitEthernet0/2
     ip address 22.20.19.18 255.255.255.0
    duplex full
     speed 100
     crypto map VZW_VPNTUNNEL
    router bgp 65505
     bgp log-neighbor-changes
     network 0.0.0.0
     network 192.168.11.0
     neighbor 172.16.200.1 remote-as 6167
     neighbor 172.16.200.5 remote-as 6167
    ip forward-protocol nd
    ip http server
    ip http access-class 23
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip route 0.0.0.0 0.0.0.0 22.20.19.19
    ip access-list extended VZW_VPN
     permit gre host 99.101.15.99 host 22.20.19.18
     permit icmp host 99.101.15.99 host 22.20.19.18
     permit esp host 99.101.15.99 host 22.20.19.18
     permit udp host 99.101.15.99 host 22.20.19.18 eq isakmp
     permit gre host 22.20.19.18 host 99.101.15.99
     permit gre host 22.20.19.18 host 99.100.14.88
    access-list 23 permit 10.10.10.0 0.0.0.7
    control-plane
    end
    So after spending countless hours analyzing every portion of this,  I think that adding one line to this will get it going (or at least closer).
    ip route 192.168.1.0 255.255.0.0 22.20.19.19
    That should allow my internal LAN to reach the Airlink gateways on the other side of the tunnel (I think)
    Now for a couple of questions for those that are still actually hanging around.
    #1 what is the purpose of the Ethernet address assigned to each tunnel?  I only see them being used in the BGP section where they are receiving routing tables from the Verizon side (is that correct?).  Why wouldn't or couldn't you just use the physical Ethernet address interface in its place (in the BGP section)?
    #2 is the config above correct in pointing the default route to the physical Ethernet address?  Does that force the packets into the tunnel, or shouldn’t you be pointing it towards the tunnel IP's (172.16.200.2)?  If the config above is correct then I should not need to add the route I described above as if I ping out to 192.168.1.X that should catch it and force it into the tunnel where Verizon would pick it up and know how to get it to its destination??
    #3 Will I need to add another permit to the VZW_VPN for TCP as in the end I need to be able to poll via Modbus which uses port 502 TCP.  Or is TCP implicit in some way with the GRE permit?
     I actually have alot more questions, but I will keep reading for now.
    I really appreciate the time you all took to trudge through this.  Also please feel free to point anything else out that I may have missed or that can be improved.  Have a great day!

    My first comment is that you have two posts in this forum and as far as I can tell they are exact duplicates, other than changing the title of the posts. It is better to figure what you want to ask and then to ask once.
    My second comment is that you have given us information about your central site. At some point we may also need some information about what is at the remote and how that is set up. But for now we will deal with what we know about your site.
    Before I deal with your specific questions I will comment that if you are able to access the remote airlinks that it is a pretty good indicator that the tunnels are probably working. But to understand the significance of this it would help if you clarify for us what address is on the local computer when you change the subnet to 255.255.0.0.
    Also what you have shown us allows us to see that BGP is configured but provides no insight into whether BGP is working or now. It would provide helpful information if you would post the output of show ip bgp sum.
    So to address your specific questions:
    You suggest that adding a static route for 192.168.1.0 might be part of the solution. But we have no information about what that network is or its significance. So we have no way to know whether the static route would help or not. But my guess (based on very scant information and therefore based mostly on assumptions) is that if BGP is working correctly that the static route is not needed.
    1) asks about an Ethernet address on the tunnel. I assume that you really meant to ask about the IP address assigned to the tunnel. The reason that the tunnel needs it own IP address is that we want a unique subnet assigned to the tunnel. If we used the address from the physical interface as you suggest then both tunnels would have the same address and that implies that they both connect to the same place, and that assumption is not correct.
    2) Yes it is correct to point the default route to the IP address that is the next hop from the Ethernet interface. You might want to have a route pointing at the tunnel address for remote subnets reached via the tunnel. But in looking at the config and trying to understand what was intended it is pretty obvious that running BGP over the tunnel is intended to learn the remote addresses over the tunnel and therefore there is no need for static routes for the remote resources.
    3) You should not need an additional permit for TCP 402. The TCP packet will be carried through the tunnel and the access list you are referring to will see the packet will modbus polling as GRE traffic and not as TCP traffic.
    HTH
    Rick

  • Mixing through outboard gear

    Trying to mix my master and sometimes individual tracks through outboard EQ etc. Just getting feedback . Went to utility tried different I/O `s . Any thoughts .My interface is Focusrite saffire pro 26 I/O

    Try flipping the S/Card - Track setting in SaffireControl.

  • Apogee Duet 2 + Outboard Gear

    I've spent countless hours trying to figure out how to use my outboard compressor with my new duet 2 using logic pro 9.
    How should I plug into/out of the duet ?
    How should I set up Maestro
    How would i create the "master" track (all tracks thru my compressor condensed into the final track)
    thank you everyone..

    Put it in the signal chain? With the mic pre i.e.?
    The duet only has 2 input channels, a stereo headset out and left/right mono speaker outputs so I have a hard time seeing how you can effectively make use of an outboard compressor by sending stuff out of the Duet for compression and then back in. At least without not having to cable and move stuff around alot.
    Ask Apogee tech support by email. They will give you the best answer in a flash at
    http://www.apogeedigital.com/company/support.php

  • MPLS - How are external/internal routes distinguished?

    Hi all
    I was setting up an MPLS environment and wanted to get some more information about how MPLS VPN's work. Basically I have three sites connected to the MPLS cloud. Site A runs EIGRP on the customer side and Site B runs OSPF on the customer side. Site C is the one in question. The way I have it designed, Sites A and C have full visability into one another and sites B and C have full visibility into one another. When I configure site C with eigrp, all proper routes are seen, but the OSPF routes from site B are seen as EIGRP external routes. When I switch site C to OSPF, EIGRP routes from site A are seen as OSPF External type 2 routes. I guess my ultimate question is, How does the PE router at site C know the originating protocol? All the routes it receives are from BGP. Does a certain attribute carry this? If so, is this feature specific to Cisco gear or an RFC standard? Thanks in advance for all your help. I can include configs if that would help, below I'll show you my RD and RT's for each VRF and the routing tables of the CE router at Site C before and after the change.
    Site A
    ip vrf a
    rd 1:111
    route-target export 1:100
    route-target import 1:101
    Site B
    ip vrf c
    rd 3:333
    route-target export 3:301
    route-target import 1:101
    Site C
    ip vrf a
    rd 1:111
    route-target export 1:101
    route-target import 1:100
    route-target import 3:301
    Change from EIGRP to OSPF
    Gateway of last resort is not set
         6.0.0.0/32 is subnetted, 1 subnets
    D       6.6.6.6 [90/435200] via 10.2.1.1, 00:05:26, Ethernet0/0
         7.0.0.0/32 is subnetted, 1 subnets
    C       7.7.7.7 is directly connected, Loopback1
         8.0.0.0/32 is subnetted, 1 subnets
    D EX    8.8.8.8 [170/2560025856] via 10.2.1.1, 00:02:13, Ethernet0/0
    D EX 111.0.0.0/8 [170/2560025856] via 10.2.1.1, 00:02:13, Ethernet0/0
         10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
    C       10.2.1.0/24 is directly connected, Ethernet0/0
    D       10.1.1.0/24 [90/307200] via 10.2.1.1, 00:05:56, Ethernet0/0
    D       10.20.0.0/16 [90/435200] via 10.2.1.1, 00:05:56, Ethernet0/0
    C       10.77.0.0/16 is directly connected, Loopback2
    D EX 192.168.1.0/24 [170/2560025856] via 10.2.1.1, 00:02:43, Ethernet0/0
    R7(config)#no router eigrp 22
    *Mar  1 02:10:20.747: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 22: Neighbor 10.2.1.1 (Ethernet0/0) is
    down: interface down
    R7(config)#router ospf 3
    R7(config-router)#network 10.0.0.0 0.255.255.255 area 0
    R7(config-router)#network 7.7.7.7 0.255.255.255 area 0
    R7(config-router)#end
    R7#show ip route
    Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, * - candidate default, U - per-user static route
           o - ODR, P - periodic downloaded static route
    Gateway of last resort is not set
         6.0.0.0/32 is subnetted, 1 subnets
    O E2    6.6.6.6 [110/409600] via 10.2.1.1, 00:00:27, Ethernet0/0
         7.0.0.0/32 is subnetted, 1 subnets
    C       7.7.7.7 is directly connected, Loopback1
         8.0.0.0/32 is subnetted, 1 subnets
    O IA    8.8.8.8 [110/21] via 10.2.1.1, 00:00:27, Ethernet0/0
    O IA 111.0.0.0/8 [110/21] via 10.2.1.1, 00:00:27, Ethernet0/0
         10.0.0.0/8 is variably subnetted, 4 subnets, 2 masks
    C       10.2.1.0/24 is directly connected, Ethernet0/0
    O E2    10.1.1.0/24 [110/1] via 10.2.1.1, 00:00:26, Ethernet0/0
    O E2    10.20.0.0/16 [110/409600] via 10.2.1.1, 00:00:26, Ethernet0/0
    C       10.77.0.0/16 is directly connected, Loopback2
    O IA 192.168.1.0/24 [110/11] via 10.2.1.1, 00:00:26, Ethernet0/0
    R7#trace 6.6.6.6
    Type escape sequence to abort.
    Tracing the route to 6.6.6.6
      1 10.2.1.1 652 msec 396 msec 192 msec
      2 40.1.1.9 [MPLS: Labels 18/24 Exp 0] 2264 msec 2640 msec 2532 msec
      3 30.1.1.3 [MPLS: Labels 18/24 Exp 0] 2320 msec *  *
      4 10.1.1.1 [MPLS: Label 24 Exp 0] 1816 msec 1792 msec 2148 msec
      5 10.1.1.2 1940 msec *  2200 msec
    R7#

    Hello Edward,
    I see nothing strange in the results you have posted. They are completely natural to the process of carrying customer routes over MPLS L3 VPN.
    You know yourself that the customer routes are carried between PE routers using BGP, and from PE towards CE, these routes are redistributed from BGP into the particular routing protocol running between PE and CE. Each of these routing protocols automatically marks redistributed networks as external networks. For OSPF, this is a normal part of the open protocol specification - that routes injected into OSPF via redistribution shall be represented as external routes (and carried in LSA-5). Similarly, when you redistribute into EIGRP from a different routing protocol, these routes will be carried by EIGRP as external networks. So what you see here is natural and normal. Even if all sites ran the same routing protocol (EIGRP or OSPF), one site would see networks from other sites as external routes.
    In fact, there are extensions to BGP using extended community attributes that try to preserve the original nature of the redistributed routes. The prerequisite is that all sites run the same IGP, either OSPF or EIGRP. In that case, EIGRP routes carried over MPLS can be made look like internal routes although they are redistributed, and OSPF will make the routes appear as inter-area routes, not as external routes. There is even a modification to OSPF allowing you to see other sites as intra-area routes (though this requires configuring so-called OSPF sham links between PEs). All of this is done because an internal network is always preferred to an external network. This causes trouble if there is a backup link directly interconnecting two sites, bypassing the MPLS cloud. As the routing protocol run over this link advertises all networks as internal, this link would always be preferred to the MPLS VPN which is exactly the opposite of what you want to do.
    Please feel welcome to ask further!
    Best regards,
    Peter

  • Routing to Apogee Duet

    Not sure where to post this, but I thought this would be my best bet.
    I have several keyboards etc. on various channels in a Mackie 32 X 8 mixer. Anything that I want to send to the Logic I route through Bus 1&2 and then using a 1/4" balanced cable I send it to my Duet "Instrument Ins". However, I get way too much noise to make this a practical way to record my outboard gear no matter how low I set the Input.
    Is there a better way to be able to do this (using the Mackie buses) as opposed to directly plugging in instruments into the Duet? Would using the "Line In" on the Duet be better? If so, do I need an XLR to 1/4" cord (balanced or unbalanced)?
    Thank you,
    paul

    Hey Pancenter,
    Thank you so much for heading me in the right direction. Actually what I ended up doing was going from a TRS output on the Mackie to an XLR (Line) input on the Duet. But you can be sure that I'll be sure that phantom power is off when I connect a mic to the inputs.
    It's nice that someone from the American desert can help a snowbound guy in midwest Canada.
    Thank you
    paul

  • The growth of the internet routing table + LISP

    I have been challenged with the task of putting together a 15-20 minute presentation of how I might go about solving the problem of the growth of the internet routing table.
    If I am understanding the question correctly - as the internet grows so will the number of IPv4 and (moreso) IPv6 prefixes that appear in the global internet routing table. This will mean that the PE and P routers in a Service Provider network will find themselves having to deal with more prefixes that will in turn increase the possibility of bogons interferring with proper routing and increase the load on the routers themselves.
    Besides being a very open ended question, I am trying to look at it from the perspective of a Service Provider (whom I work for) and have come up with the following options (admittedly this is only after a quick google on the topic):
    > Improvise in the short term by adjusting CAM table allocation
    > Use selective hearing by filtering prefixes that are not important
    > Use external assistance like LISP and DNS
    > Spend Money and upgrading existing routers to handle the load
    Obviously with only a 20 minute window I cannot talk about much and I would like the options to be innnovative and interesting. LISP seems like an interesting option and I would like to learn about it - however I am having trouble tracking down resources that give a basic introduction to exactly what and how LISP works (every time I try and search for it a get pushed to sites talking about the programming language ).
    So this leads me to two questions:
    1. Is there anything important, vital or interesting that I have not included in my quickly put together list above.
    2. Is anyone aware for a good site/resource that explains LISP from a beginners/tutorial-type perspective.

    I have been challenged with the task of putting together a 15-20 minute presentation of how I might go about solving the problem of the growth of the internet routing table.
    If I am understanding the question correctly - as the internet grows so will the number of IPv4 and (moreso) IPv6 prefixes that appear in the global internet routing table. This will mean that the PE and P routers in a Service Provider network will find themselves having to deal with more prefixes that will in turn increase the possibility of bogons interferring with proper routing and increase the load on the routers themselves.
    Besides being a very open ended question, I am trying to look at it from the perspective of a Service Provider (whom I work for) and have come up with the following options (admittedly this is only after a quick google on the topic):
    > Improvise in the short term by adjusting CAM table allocation
    > Use selective hearing by filtering prefixes that are not important
    > Use external assistance like LISP and DNS
    > Spend Money and upgrading existing routers to handle the load
    Obviously with only a 20 minute window I cannot talk about much and I would like the options to be innnovative and interesting. LISP seems like an interesting option and I would like to learn about it - however I am having trouble tracking down resources that give a basic introduction to exactly what and how LISP works (every time I try and search for it a get pushed to sites talking about the programming language ).
    So this leads me to two questions:
    1. Is there anything important, vital or interesting that I have not included in my quickly put together list above.
    2. Is anyone aware for a good site/resource that explains LISP from a beginners/tutorial-type perspective.

  • IP routing utilizing Verizon private network (GRE tunnel) with remote cellular gateways

    Okay, I give up, and think I have done my due diligence (I have been engrossed and fascinated spending many more hours than allotted to try and learn some of the finer details).  Time for some advice.  My usual trade is controls engineering which generally require only basic knowledge of networking principals.  However I recently took a job to integrate 100 or so lift stations scattered around a county into a central SCADA system.  I decided to use cellular technology to connect these remote sites back to the main SCADA system.  Well the infrastructure is now in and it’s time to get these things talking.  Basic topology description is as follows:  Each remote site has an Airlink LS300 gateway.  Attached to the gateway via Ethernet is a system controller that I will be polling via Modbus TCP from the main SCADA system.  The Airlinks are provisioned by Verizon utilizing a private network with static IP's.  This private networks address is 192.168.1.0/24.  Back at the central office the SCADA computer is sitting behind a Cisco 2911.  The LAN address of the central office is 192.168.11.0/24.  The 2911 is utilizing GRE tunnels that terminate with Verizon.  The original turn up was done with another contractor that did a basic config of the router which you will find below.  As it stands now I am pretty confident the tunnels are up and working (if I change a local computers subnet to 255.255.0.0 I can surprisingly reach the airlinks in the field), but this is obviously not the right way to solve the problem, not to mention I was unable to successfully poll the end devices on the other side of the Airlinks.  I think I understand just about every part of the config below and think it is just missing a few items to be complete.  I would greatly appreciate anyone’s help in getting this set up correctly.  I also have a few questions about the set up that still don’t make sense to me, you will find them below the config.  Thanks in advance.
    no aaa new-model
    ip cef
    ip dhcp excluded-address 10.10.10.1
    ip dhcp pool ccp-pool
     import all
     network 10.10.10.0 255.255.255.248
     default-router 10.10.10.1 
     lease 0 2
    ip domain name yourdomain.com
    no ipv6 cef
    multilink bundle-name authenticated
    username cisco privilege 15 one-time secret 
    redundancy
    crypto isakmp policy 1
    encr 3des
    hash md5
     authentication pre-share
     group 2
    crypto isakmp key AbCdEf01294 address 99.101.15.99  
    crypto isakmp key AbCdEf01294 address 99.100.14.88 
    crypto ipsec transform-set VZW_TSET esp-3des esp-md5-hmac 
    mode transport
    crypto map VZW_VPNTUNNEL 1 ipsec-isakmp 
     description Verizon Wireless Tunnel
     set peer 99.101.15.99
     set peer 99.100.14.88
     set transform-set VZW_TSET 
     match address VZW_VPN
    interface Tunnel1
     description GRE Tunnel to Verizon Wireless
     ip address 172.16.200.2 255.255.255.252
     tunnel source 22.20.19.18
     tunnel destination 99.101.15.99
    interface Tunnel2
    description GRE Tunnel 2 to Verizon Wireless
     ip address 172.16.200.6 255.255.255.252
     tunnel source 22.20.19.18
     tunnel destination 99.100.14.88
    interface Embedded-Service-Engine0/0
     no ip address
     shutdown
    interface GigabitEthernet0/0
     description $ETH-LAN$$ETH-SW-LAUNCH$$INTF-INFO-GE 0/0$
     ip address 10.10.10.1 255.255.255.248
     shutdown
     duplex auto
     speed auto
    interface GigabitEthernet0/1
     ip address 192.168.11.1 255.255.255.0
     duplex auto
     speed auto
    interface GigabitEthernet0/2
     ip address 22.20.19.18 255.255.255.0
    duplex full
     speed 100
     crypto map VZW_VPNTUNNEL
    router bgp 65505
     bgp log-neighbor-changes
     network 0.0.0.0
     network 192.168.11.0
     neighbor 172.16.200.1 remote-as 6167
     neighbor 172.16.200.5 remote-as 6167
    ip forward-protocol nd
    ip http server
    ip http access-class 23
    ip http authentication local
    ip http secure-server
    ip http timeout-policy idle 60 life 86400 requests 10000
    ip route 0.0.0.0 0.0.0.0 22.20.19.19
    ip access-list extended VZW_VPN
     permit gre host 99.101.15.99 host 22.20.19.18
     permit icmp host 99.101.15.99 host 22.20.19.18
     permit esp host 99.101.15.99 host 22.20.19.18
     permit udp host 99.101.15.99 host 22.20.19.18 eq isakmp
     permit gre host 22.20.19.18 host 99.101.15.99
     permit gre host 22.20.19.18 host 99.100.14.88
    access-list 23 permit 10.10.10.0 0.0.0.7
    control-plane
    end
    So after spending countless hours analyzing every portion of this,  I think that adding one line to this will get it going (or at least closer).
    ip route 192.168.1.0 255.255.0.0 22.20.19.19
    That should allow my internal LAN to reach the Airlink gateways on the other side of the tunnel (I think)
    Now for a couple of questions for those that are still actually hanging around.
    #1 what is the purpose of the Ethernet address assigned to each tunnel?  I only see them being used in the BGP section where they are receiving routing tables from the Verizon side (is that correct?).  Why wouldn't or couldn't you just use the physical Ethernet address interface in its place (in the BGP section)?
    #2 is the config above correct in pointing the default route to the physical Ethernet address?  Does that force the packets into the tunnel, or shouldn’t you be pointing it towards the tunnel IP's (172.16.200.2)?  If the config above is correct then I should not need to add the route I described above as if I ping out to 192.168.1.X that should catch it and force it into the tunnel where Verizon would pick it up and know how to get it to its destination??
    #3 Will I need to add another permit to the VZW_VPN for TCP as in the end I need to be able to poll via Modbus which uses port 502 TCP.  Or is TCP implicit in some way with the GRE permit?
     I actually have alot more questions, but I will keep reading for now.
    I really appreciate the time you all took to trudge through this.  Also please feel free to point anything else out that I may have missed or that can be improved.  Have a great day!

    This post is a duplicate of this thread
    https://supportforums.cisco.com/discussion/12275476/proper-routing-lan-through-verizon-private-network-gre-airlink-gateways
    which has a response. I suggest that all discussion of this question be done through the other thread.
    HTH
    Rick

  • CK11N , bom and routing not copied

    Dear all,
    At time of costing run through CK11N , bom and routing not copied I have checked all validity/ status /uses / lot size of bom and routing also . but when i will run costing for next month system has copied bom and routing .
    plz guide me

    Dear Surendra Patil,
    Check the costing variant that you use for executing CK11N, is it PPC1?
    If this is correct means check in T code OKKN and choose PPC1 and check for the quantity structure
    control and check the BOM apllication and the routing selection ID.
    This should match with your BOM that you have created and also the routing that you have created.
    1. Check the BOM status in CS03---> header.
    2.Check the status & usage of routing in CA03,generally it will be
    Usage                1    Production
    Status               4    Released (general)
    3. If you are using Production version check whether have you assigned proper routing group & counter
    and along with the BOM.Also check whether is the production version locked?
    Check & Revert back.
    Regards
    Mangalraj.S

Maybe you are looking for