Hi Rick<br><br>The various SF/CPM LED colours and the states they indicate are outlined on page 130 of the latest SR-12 Installation guide. ( same states apply to the SR-7. Concerning the CPM status, the following is mentioned abount the M/S ctl LED on the SF/CPMs:<br>
<br> M/S Ctl Master/Slave SF/CPM designation:<br>• Green: Indicates that the SF/CPM is designated as the primary SF/CPM<br>in a redundant system.<br>• Green (blinking): Indicates that the SF/CPM is operating as the<br>secondary SF/CPM in a redundant configuration.<br>
<br>There is no sim for the 7x50.<br><br>Regards<br>Craig<br><br><br><br><br><br><div class="gmail_quote">On Mon, Aug 10, 2009 at 6:38 PM, Richard Lee <span dir="ltr"><<a href="mailto:rl0001@gmail.com">rl0001@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Thanks Diego,<br>
<br>
I've heard a rumor that on the SR-7/12 the active card has a red light<br>
and the standby has green? :-)<br>
<br>
Is this true? If so, why?<br>
<br>
Also, is there a sim for 7750 etc , similar to gns3/dynamips for cisco?<br>
<br>
Cheers,<br>
Rick<br>
<br>
2009/8/8 GARCIA DEL RIO Diego <<a href="mailto:Diego.Garcia_Del_Rio@alcatel-lucent.be">Diego.Garcia_Del_Rio@alcatel-lucent.be</a>>:<br>
<div><div></div><div class="h5">> Just to add some comments,<br>
><br>
> SAM will always pick up the changes done in CLI, so it will update its<br>
> own database accordingly (the node generates an SNMP trap for every<br>
> change and SAM follows on).<br>
><br>
> As for a change in a policy, what will happen is that as soon as you<br>
> modify the policy in the node, SAM will notice that the node is no<br>
> longer "in synch" for that particular policy. Only if you initiate a<br>
> "push" again from SAM will the policy in the node be overwritten. The<br>
> only way SAM will take the change on the policy and set it as the<br>
> "golden" one is if you manually open the policy window in SAM and tell<br>
> it to synch it from a particular node.<br>
><br>
> It will never push policies without you specifically asking it to do so.<br>
><br>
> As for the reference documentation, it is always available at the server<br>
> and you can access the whole API documentation directly from the help<br>
> menu in the SAM client.<br>
><br>
> Finally, if you have SAM 6 or onwards, the script editor (for service<br>
> templates and so on) provides a very nice way of simplifying the input<br>
> screens a lot and also shows the underlying xml script.<br>
><br>
> Cheers<br>
><br>
> Diego Garcia del Rio<br>
> New Product Introduction - Network Design Engineer<br>
> IP Division<br>
> Alcatel-Lucent - Antwerpen<br>
> Mobile: +32 4734 30 245<br>
> OnNET 2 605 3871<br>
> Phone (+32) 3 2403871<br>
> e-mail <a href="mailto:diego.garcia_del_rio@alcatel-lucent.com">diego.garcia_del_rio@alcatel-lucent.com</a><br>
><br>
> <<<br>
> This message (including any attachments) contains confidential<br>
> information intended for a specific individual and purpose, and is<br>
> protected by law. If you are not the intended recipient, you should<br>
> delete this message. Any disclosure, copying, or distribution of this<br>
> message, or the taking of any action based on it, is strictly prohibited<br>
> without the prior consent of its author.<br>
>>><br>
> -----Original Message-----<br>
> From: <a href="mailto:alcatel-nsp-bounces@puck.nether.net">alcatel-nsp-bounces@puck.nether.net</a><br>
> [mailto:<a href="mailto:alcatel-nsp-bounces@puck.nether.net">alcatel-nsp-bounces@puck.nether.net</a>] On Behalf Of Philip<br>
> Matthews<br>
> Sent: 07 August 2009 21:04<br>
> To: <a href="mailto:alcatel-nsp@puck.nether.net">alcatel-nsp@puck.nether.net</a><br>
> Subject: Re: [alcatel-nsp] Automate SAM Provisioning through text/csv?<br>
><br>
><br>
> On Fri, 7-Aug-09, at 17:24 , Kirby Files wrote:<br>
><br>
>> Richard Lee wrote on 08/07/2009 05:10 PM:<br>
>>> Another issue I have been warned about is that a change to a global<br>
>>> policy on a node could be synchronised back to the SAM and could<br>
>>> break<br>
>>> a lot of services.<br>
>>><br>
>>> Does this sound right?<br>
>><br>
>> Yeah, that's probably possible.<br>
><br>
> What type of policy are you referring to? A QoS policy? A "routing<br>
> policy-options" policy? Or something else? I don't see how this could<br>
> happen.<br>
><br>
> This does bring up one other thing. SAM makes sure that the many<br>
> numbers that the CLI requires are selected appropriately. For example,<br>
> service numbers at both ends of a service have to match. Your scripts<br>
> will have to ensure these rules are followed. However, this is nothing<br>
> new over what you have to do if you configure the routers by hand.<br>
><br>
> - Philip<br>
> _______________________________________________<br>
> alcatel-nsp mailing list<br>
> <a href="mailto:alcatel-nsp@puck.nether.net">alcatel-nsp@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/alcatel-nsp" target="_blank">https://puck.nether.net/mailman/listinfo/alcatel-nsp</a><br>
> _______________________________________________<br>
> alcatel-nsp mailing list<br>
> <a href="mailto:alcatel-nsp@puck.nether.net">alcatel-nsp@puck.nether.net</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/alcatel-nsp" target="_blank">https://puck.nether.net/mailman/listinfo/alcatel-nsp</a><br>
><br>
_______________________________________________<br>
alcatel-nsp mailing list<br>
<a href="mailto:alcatel-nsp@puck.nether.net">alcatel-nsp@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/alcatel-nsp" target="_blank">https://puck.nether.net/mailman/listinfo/alcatel-nsp</a><br>
</div></div></blockquote></div><br>