Tassos, the problem is that the EFP (Ethernet Flowpoint) is not programmed to the card using the efp-client , without an EFP the service instance has nothing to attach to.
Am currently waiting on somebody to share the DE notes with me so I can see if I can find a workaround (even if it means a slew of test commands to prod the subsystems directly) I know this is resolved in SRC4 and we are on target to upgrade, would just appreciate a faster solution , we are all out of alternatives :) Dave. Tassos Chatzithomaoglou wrote: > Although i haven't met this, it might mean that the EVC frame matching > config (the "encapsulation dot1q xxx" under the service instance) is not > "converted" into the appropriate TCAM entry in the ES card. A possible > result would be that frames that should be forwarded through this > service instance, are either not forwarded at all or forwarded through a > less specific match criterion of another service instance. > > In any case, your account SE should be able to provide you with more > -internal- details about this bug. > > Regards, > Tassos > > David Freedman wrote on 03/06/2009 18:32: >> Has anybody come across this and if so are there any known workarounds? >> >> Am keen to know under what circumstances an EFP does not get programmed >> to the card, if anybody has any more information on this would be >> appreciative of it online or offline. >> >> Regards, >> >> David Freedman >> >> _______________________________________________ >> cisco-nsp mailing list [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at http://puck.nether.net/pipermail/cisco-nsp/ >> > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
