for example
root#While the configuration shown in this recipe provides the minimum needed to access the router from another system on the network, you should add a few other settings to the configuration to provide a more robust level of basic network connectivity:cliroot@> cli>configure[edit] root@#set system host-name router1root@#set system domain-name mynetwork.comroot@#set interfaces fxp0 unit 0 family inet address 192.168.15.1/24root@#set system backup-router 192.168.15.2root@#set system name-server 192.168.15.3root@#set system root-authentication plain-text-passwordNew password: Retype password: root@showsystem { host-name router1 ; domain-namemynetwork.com;backup-router192.168.15.2;root-authentication { encrypted-password "$1$ZUlES4dp$OUwWo1g7cLoV/aMWpHUnC/"; ## SECRET-DATA; } name-server {192.168.15.3;} interfaces { fxp0 { unit 0 { family inet { address 192.168.15.1/24; } } } } root@#commitroot@router1#exitroot@router1>
[edit] root@router1#P address of the router'sset system ntp server192.168.2.100root@router1#set system time-zoneAmerica/Los_Angelesroot@router1#set system services sshroot@router1#set interfaces lo0 unit 0 family inet address207.17.139.42/32root@router1#set system login useravivaclass superuserroot@router1#set system log user aviva authentication plain-text-passwordNew password: Retype new password: root@router1#commit
fxp0 interface, with the
set interfaces fxp0 command. fxp0 is an Ethernet
management interface that provides a separate out-of-band management
network on the router. (The J-series routers do not have a dedicated
management interface. You use one of the built-in Fast Ethernet
interfaces, fe-0/0/0 or fe-0/0/1, instead.) Juniper Networks recommends that you manage all M-series and T-series routers using the fxp0
interface, which is reserved for managing the router, so no traffic is
forwarded through it. As part of the physical setup for the router, you
should connect fxp0 to an Ethernet network over which you can perform
management tasks. Optimally, the router should also be able to reach its
DNS and NTP servers through this network. If you prefer, you can use
any other interface router as a management interface. For the remainder
of this book, we assume that fxp0 (or fe-0/0/0 on J-series routers) is configured as the management interface.IP address of a backup router, with the
set system backup-router command. Choose a router that is
directly connected to the local router. Your router uses this backup
router only when it is booting and only if the JUNOS routing software
(called the routing protocol process,
or RPD) does not start. If RPD does not start, the router will have no
static or default routes, so you will not be able to access it directly
but will have to go through the backup router. When the router is
booting, it creates a static route to the backup router. This route is
removed from the routing table as soon as the routing software starts.For routers with two Routing Engines, the backup Routing Engine, RE1, still uses the backup router as a default gateway after the router has booted, so you can use the backup router to log in to RE1.(RE0 is the primary, or master, Routing Engine.see next post configuring back-router
No comments:
Post a Comment