Re: [j-nsp] trying to upgrade OS on M5, getting "not compatible" error

2007-07-10 Thread Harry Reynolds
Hey Mickey, These messages are somewhat common when you skip a few releases. When wearing my **testing** hat I use the "force" option, and when available the "no-validate" switch, to make things happen when I see such messages. I generally have success with this, especially when upgrading. Sometim

[j-nsp] trying to upgrade OS on M5, getting "not compatible" error

2007-07-10 Thread Mickey Everts
I have an M5 which is running kind of an old version, JUNOS 5.6R2.4. When I attempt to upgrade via this command: request system software add validate reboot /var/tmp/jinstall-7.6R4.3-domestic-signed.tgz I received the following error... WARNING: Current configuration not compatible with /va

Re: [j-nsp] Few question about netscreen ISG 2000

2007-07-10 Thread Premji
Hi, Port translation will not show utilization because theoretically, you have 65535 sessions per public IP (assuming you started with a class- B on the public side). Utilization only applies to fix-port. -Ariff On Jul 10, 2007, at 9:54 AM, [EMAIL PROTECTED] wrote: > Hi, > Thx for reply. I

Re: [j-nsp] Route target configuration for L2VPN route instance

2007-07-10 Thread Rafał Szarecki
Monika, With vrf-target You and-up with only one RT for ingrass and egress. Stephane has right. But You can try with vrf-import/vrf-export instead. You will need to write regular policy-statement and communities under policy-option, and reference them in vrf-import/export. This way You should be

Re: [j-nsp] Policies for VPLS traffic

2007-07-10 Thread Rafał Szarecki
Monika, Let's look for simple cast: 1 ingress PE one egress PE, and multiple ECMP path between them. I will not elaborate how to get 2 or more equaly good transport lsp. But this is possible e.g with LDP but not only. The from ingress PE perspective there are two equaly good pathe to BGP NEXT-Hop

Re: [j-nsp] Overlapping ipv6 address space?

2007-07-10 Thread Aaron Daubman
Jeroen, Some further replies / questions: > > I'm curious as to why the following did not throw an overlapping > > address error when committed: > > Why should it? It is just a more specific route. > > According to what you say you would not be able to route a /48 to one > direction and a piece o

Re: [j-nsp] VLAN Q-in-Q-Termination on Juniper M-Series ?

2007-07-10 Thread sthaug
> is it possible to terminate Q-in-Q-Trunks on M-Series-Router ? > > i.e. > > ge-0/0/0 { > vlan-tagging; > unit 2000 { > vlan-id 2000; > unit 100 { >vlan-id 100; > } > unit 101 { >vlan-id 101; > } > } You can do this

Re: [j-nsp] Few question about netscreen ISG 2000

2007-07-10 Thread lag0da
Hi, Thx for reply. I know this commands. I think that get xlate should be show me DIP utilization, but it is empty: nsisg2000-> get xlate xlate ctx in use: 0/75000, alloc failed: 0 ip port x_ipx_port port_cnt dip_id ref_cnt ---

Re: [j-nsp] Few question about netscreen ISG 2000

2007-07-10 Thread Ariff Premji
Not sure if many screenOS folks are on this list. Hopefully this helps: I think what you are look for is: > get interface dip This info is also available via snmp. The other thing you may find interesting is the alarming on the fix- port pool so that you (example below): > set dip alarm-r

Re: [j-nsp] Overlapping ipv6 address space?

2007-07-10 Thread Jeroen Massar
Aaron Daubman wrote: > Greetings, > > I'm curious as to why the following did not throw an overlapping > address error when committed: Why should it? It is just a more specific route. According to what you say you would not be able to route a /48 to one direction and a piece of it to another int

Re: [j-nsp] Overlapping ipv6 address space?

2007-07-10 Thread Jeroen Massar
Aaron Daubman wrote: > Jeroen, > > Thanks for the reply... > >> Which is also 'overlapping', but why would it error or even warn about >> that? it is what what you want it to do isn't it? > > I suppose a better question would be "why would IOS error on such a > configuration?" While the right q

Re: [j-nsp] Overlapping ipv6 address space?

2007-07-10 Thread Aaron Daubman
Jeroen, Thanks for the reply... > Which is also 'overlapping', but why would it error or even warn about > that? it is what what you want it to do isn't it? I suppose a better question would be "why would IOS error on such a configuration?" (trying to unify configuration methodologies across pl

[j-nsp] Overlapping ipv6 address space?

2007-07-10 Thread Aaron Daubman
Greetings, I'm curious as to why the following did not throw an overlapping address error when committed: [edit] # show interfaces ge-0/0/0.0 family inet6 { address fe80::200:ff:fe12:1/64; address 2001:20:1::5/64; } [edit] # show interfaces lo0.0 family inet6 { address 2001:20:1::1/1

[j-nsp] FW: VLAN Q-in-Q-Termination on Juniper M-Series ?

2007-07-10 Thread jens . hoffmann
sorry... I've found somewhat ... [edit interfaces ge-0/0/0 unit 2000] root# set vlan-tags ? Possible completions: <[Enter]>Execute this command inner[tpid.]vlan-id, tpid format is 0x and is optional outer[tpid.]vlan-id, tpid format is 0x an

[j-nsp] VLAN Q-in-Q-Termination on Juniper M-Series ?

2007-07-10 Thread jens . hoffmann
Dear colleagues, is it possible to terminate Q-in-Q-Trunks on M-Series-Router ? i.e. ge-0/0/0 { vlan-tagging; unit 2000 { vlan-id 2000; unit 100 { vlan-id 100; } unit 101 { vlan-id 101; } } My current release 8.0R2.8 s