Hoy he tenido un primer contacto con JunOS. Después de oír maravillas sobre los dispositivos de Juniper, decidí probar los routers de este proveedor. Hasta ahora sólo había trabajado con sus cortafuegos, dejando claro que no tienen nada que envidiar a ningún otro.

Pues bien, incluso la simple configuración de una interfaz me llevó unos 2 minutos, cuando Cisco había tardado unos 0,3 segundos en hacerla funcionar. Claramente el cambio en la forma de trabajar y configurar estos dispositivos es muy diferente. “configurar bla bla”. “commit”. “request system halt”. Comandos muy nuevos para meter en mi mente.

Me llevará algún tiempo aclimatarme a esto.

Actualización

Ok, he encontrado un comando fantástico en JunOS. “help topic”. JunOS almacena en el router toda la documentación del software en el paquete jdocs. JunOS está basado en el sistema operativo FreeBSD, pero mejorado para funcionar como router. Así que instalando diferentes paquetes podemos añadir un conjunto diferente de características. Podemos ver la lista de paquetes corriendo en el router con el comando show version. Por cierto, cli es como con Cisco jerárquico, podemos componer comandos de la misma manera.

root> show version brief
 Model: olive
 JUNOS Base OS boot [12.1R1.9]
 JUNOS Base OS Software Suite [12.1R1.9]
 JUNOS Kernel Software Suite [12.1R1.9]
 JUNOS Crypto Software Suite [12.1R1.9]
 JUNOS Packet Forwarding Engine Support (M/T Common) [12.1R1.9]
 JUNOS Packet Forwarding Engine Support (M20/M40) [12.1R1.9]
 JUNOS Online Documentation [12.1R1.9]
 JUNOS Voice Services Container package [12.1R1.9]
 JUNOS Border Gateway Function package [12.1R1.9]
 JUNOS Services AACL Container package [12.1R1.9]
 JUNOS Services LL-PDF Container package [12.1R1.9]
 JUNOS Services PTSP Container package [12.1R1.9]
 JUNOS Services Stateful Firewall [12.1R1.9]
 JUNOS Services NAT [12.1R1.9]
 JUNOS Services Application Level Gateways [12.1R1.9]
 JUNOS Services Captive Portal and Content Delivery Container package [12.1R1.9]
 JUNOS Services RPM [12.1R1.9]
 JUNOS Services HTTP Content Management package [12.1R1.9]
 JUNOS AppId Services [12.1R1.9]
 JUNOS IDP Services [12.1R1.9]
 JUNOS Services Crypto [12.1R1.9]
 JUNOS Services SSL [12.1R1.9]
 JUNOS Services IPSec [12.1R1.9]
 JUNOS Runtime Software Suite [12.1R1.9]
 JUNOS Routing Software Suite [12.1R1.9]

Así pues, el paquete jdocs es un buen punto cuando nos encontramos atascados en algún punto. He aquí un ejemplo de la salida proporcionada.

root> help topic interfaces address
  Configuring the Interface Address
 You assign an address to an interface by specifying the address when
  configuring the protocol family. For the inet or inet6 family, configure
  the interface IP address. For the iso family, configure one or more
  addresses for the loopback interface. For the ccc, ethernet-switching,
  tcc, mpls, tnp, and vpls families, you never configure an address.
 +------------------------------------------------------------------------+
  | | The point-to-point (PPP) address is taken from the loopback |
  | Note: | interface address that has the primary attribute. When the |
  | | loopback interface is configured as an unnumbered interface, |
  | | it takes the primary address from the donor interface. |
  +------------------------------------------------------------------------+
 To assign an address to an interface, include the address statement:
  address address {
  broadcast address;
  destination address;
  destination-profile name;
  eui-64;
  preferred;
  primary;
  }
  You can include these statements at the following hierarchy levels:
  * [edit interfaces interface-name unit logical-unit-number family
  family]
  * [edit logical-systems logical-system-name interfaces interface-name
  unit logical-unit-number family family]
  In the address statement, specify the network address of the interface.
  For each address, you can optionally configure one or more of the
  following:
  * Broadcast address for the interface subnet-Specify this in the
  broadcast statement; this applies only to Ethernet interfaces, such as
  the management interface fxp0, em0, or me0 the Fast Ethernet
  interface, and the Gigabit Ethernet interface.
  * Address of the remote side of the connection (for point-to-point
  interfaces only)-Specify this in the destination statement.
  * PPP properties to the remote end-Specify this in the
  destination-profile statement. You define the profile at the [edit
  access group-profile name ppp] hierarchy level (for point-to-point
  interfaces only).
  * Whether the router or switch automatically generates the host number
  portion of interface addresses-The eui-64 statement applies only to
  interfaces that carry IPv6 traffic, in which the prefix length of the
  address is 64 bits or less, and the low-order 64 bits of the address
  are zero. This option does not apply to the loopback interface (lo0)
  because IPv6 addresses configured on the loopback interface must have
  a 128-bit prefix length.
 +-------------------------------------------------------------+
  | Note: | IPv6 is not currently supported for the QFX Series. |
  +-------------------------------------------------------------+
 * Whether this address is the preferred address-Each subnet on an
  interface has a preferred local address. If you configure more than
  one address on the same subnet, the preferred local address is chosen
  by default as the source address when you originate packets to
  destinations on the subnet.
 By default, the preferred address is the lowest-numbered address on
  the subnet. To override the default and explicitly configure the
  preferred address, include the preferred statement when configuring
  the address.
 * Whether this address is the primary address-Each interface has a
  primary local address. If an interface has more than one address, the
  primary local address is used by default as the source address when
  you send packets from an interface where the destination provides no
  information about the subnet (for example, some ping commands).
  By default, the primary address on an interface is the lowest-numbered
  non-127 (in other words, non-loopback) preferred address on the interface.
  To override the default and explicitly configure the preferred address,
  include the primary statement when configuring the address.
  * Configuring Interface IPv4 Addresses
  * Configuring Interface IPv6 Addresses
 Related-Topics
 * Configuring IPCP Options
  * Configuring Default, Primary, and Preferred Addresses and
  Interfaces