1. Home
    2. /
  2. Manuals
    3. /
  3. Allied-Telesis
    4. /
  4. AT-iMG624A
    5. /
  5. 7
Page 31 / 998 Scroll up to view Page 26 - 30
List of Figures
iMG/RG Software Reference Manual - List of Figures
LOF-1
Figure 1-1 4 MByte Flash Memory partitions - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-6
Figure 1-2 8 MByte Flash Memory partition - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-8
Figure 1-3 Configuration files backup process - example - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-11
Figure 1-4 The Windows™ Loader - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-58
Figure 1-5 The Web Interface main page - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-59
Figure 1-6 The Web Interface Firmware Update page- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-60
Figure 1-7 Normal
SwUpdate
operation mode- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-62
Figure 1-8 SwUpdate scheduling example 1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-65
Figure 1-9
SwUpdate
scheduling example 2- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-66
Figure 1-10 ZTC network architecture - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-75
Figure 1-11
Pull-at-Startup
ZTC phase - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-78
Figure 1-12
Scheduled-pull
ZTC phase - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-80
Figure 1-13 A manager Entity- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-85
Figure 1-14 An agent Entity - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-85
Figure 1-15 hmac expression - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-87
Figure 1-16 vacmViewTreeFamilyMask- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-94
Figure 1-17 vacmViewTreeFamilyMask (continued) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-94
Figure 1-18 snmpNotifyFilterMask - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-100
Figure 1-19 snmpNotifyFilterMask (continued)- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-100
Figure 1-20 snmpTargetAddrTMask - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-103
Figure 1-21 snmpTargetAddrTMask (continued) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-104
Figure 1-22 snmpTargetAddrTMask (continued) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-104
Figure 1-23 snmpTargetAddrTMask (continued) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-104
Figure 1-24 snmpTargetAddrTMask (continued) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 1-105
Figure 2-1 IP packet overview - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-6
Figure 2-2 Tagged frame format according to IEEE 802.3ac standard - - - - - - - - - - - - - - - - - - - - 2-86
Figure 2-3 IP interface over LAN - first steps - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 2-91
Figure 3-1 IGMP messages flow when Snoop-Only mode is active- - - - - - - - - - - - - - - - - - - - - - - 3-5
Figure 3-2 Two Hosts Join Two Different Mulitcast Channels - - - - - - - - - - - - - - - - - - - - - - - - - - 3-8
Figure 3-3 Two Hosts Join Two Different Multicast Channels - - - - - - - - - - - - - - - - - - - - - - - - - 3-10
Figure 3-4 Host Disconnects - No Leave Message - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 3-11
Figure 3-5 One and Two Hosts Leave the Same Multicast Stream - - - - - - - - - - - - - - - - - - - - - - 3-12
Figure 4-1 Security modules on AT-iMG Models - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-58
Figure 4-2 Security interfaces on AT-iMG Models- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-59
Figure 4-3 Address Conservation Using NAT - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 4-135
Figure 5-1 Domain Name System - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 5-83
Figure 6-1 Phone --> iMG(A) --> iMG(B) --> Phone - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-17
Figure 6-2 Phone --> iMG(A) --> SIP IP Phone- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-18
Figure 6-3 VoIP subsystem configuration - basic steps - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-19
Page 32 / 998
LOF-2
iMG/RG Software Reference Manual - List of Figures
Figure 6-4
VoIP subsystem configuration - basic steps - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 6-61
Figure 7-1 Gateway Architecture - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-2
Figure 7-2 Metering for Traffic Control - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-8
Figure 7-3 Overview of Scheduler Functionality - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-10
Figure 7-4 Scheduling Process for Packet Enqueuing - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-13
Figure 7-5 Scheduling Process for Packet Dequeuing - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-14
Figure 7-6 The ADSL Driver - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7-16
Figure 8-1 ADSL upload interface module - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-2
Figure 8-2 Basic software bridge configuration - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-37
Figure 8-3 Example of system architecture to support multiple vlan management - - - - - - - - - - - - 8-38
Figure 8-4 Example
of PPPoE connection - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 8-64
Figure 9-1 Wireless interface usage on a bridged scenario- - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9-2
Figure 9-2 Wireless interface usage on a routed scenario - - - - - - - - - - - - - - - - - - - - - - - - - - - - 9-11
Figure 10-1 HPNA Section of LAN Module Diagram - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10-3
Figure 10-2 Typical CES Deployment Model:- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 10-8
Page 33 / 998
System Configuration
System Management
1-1
iMG/RG Software Reference Manual (System Configuration)
1. System Configuration
1.1
System Management
This section provides information regarding access to the gateway, the login process, command line interface
(CLI) and the different types of user access.
1.1.1
System Configuration
1.1.1.1 Access to the Gateway
The gateway can be configured in different ways,either through the CLI or using the web interface.
The CLI is accessible through the serial interface, Telnet, or an SSH connection.
The web interface is accessible through the Microsoft Internet Explorer WEB browser.
Each different gateway family has a different configuration and access capability according to the following table:
1.1.1.2 Default Factory Configuration
The default configuration stored on the gateway when delivered to the customer is called “factory”.
Group
Serial interface
Telnet
SSH
WEB
Fiber A
NO
YES
NO
NO
Fiber B
YES
YES
NO
YES
Fiber C
YES
YES
NO
NO
Fiber D
YES
YES
YES
YES
Fiber E
YES
YES
YES
YES
Modular
YES
YES
YES
YES
ADSL A
NO
YES
YES
YES
ADSL B
YES
YES
YES
YES
Page 34 / 998
System Management
System Configuration
iMG/RG Software Reference Manual (System Configuration)
1-2
The default “factory” configuration has the DHCP client enabled on all interfaces, including xDSL in the xDSL-
based modem with a bridged RFC1483 over PVC 0.35.
The IP management interface is set dynamically at startup.
It is possible to connect remotely to the gateway using Telnet of SS4 once an IP address has been assigned to
the gateway.
In order to access the gateway, the user is required to enter a username and password.
The following default values give super-user access to the CLI commands and must be used only by administra-
tors to configure the system and create user access with restricted privileges:
•
IP address:
dynamically assigned by the DHCP server
•
Telnet port:
23
•
Login:
manager
•
Password:
friend
For gateways with a serial interface, it is possible to connect using a suitable cable and serial terminal program.
The following configuration parameters must be set on the terminal program for serial access:
•
Baud rate:
38400
•
Data:
8 bit
•
Parity:
none
•
Stop:
1 bit
•
Flow control:
none
Serial access uses the same security credentials as for remote access.
1.1.1.3 Minimal Configuration
To access the gateway CLI when no DHCP server is available on the network, it is possible to load the gateway
with a well known configuration - called the “minimal” configuration.
A default minimal configuration exists on the gateway. This can be customized or replaced with a minimal con-
figuration created by the customer.
The minimal configuration is accessible from the serial interface. To start the gateway using the minimal config-
uration, first power-off the unit. Then keep the “R” button pressed on the PC keyboard for at least 30 seconds
was the unit is powered-on.
If the default minimal configuration has not been replaced by a customised version, once the system has com-
pleted the bootstrap phase it will be possible to connect remotely (via Telnet or SSH) and serially to the gate-
way using the following parameters:
•
IP address:
192.168.1.1
Page 35 / 998
Command Line Interface and Console
System Management
1-3
iMG/RG Software Reference Manual (System Configuration)
•
Login:
manager
•
Password:
friend
•
To install a custom minimal configuration on the gateway see the section related to the software update
module.
1.1.2
Command Line Interface and Console
On the gateway two types of consoles are available:
•
Standard CLI (Command Line Interface): this is used to configure and manage the system. It provides full
access to the system modules included in this manual.
•
Debug console: this is a special console (also named simply as console), available to users with super-user
rights for access to hidden debug commands that are not available in the standard command line. Console
commands are not documented in this administration guide. Access to console is possible only from inside
a CLI session.
1.1.2.1 Access permissions to CLI
There are three CLI access levels (via local craft interface, telnet or SSH), each providing different levels of
allowed operations:
•
Default user
- can use CLI commands. Only “show” and “list” commands are available. Cannot access con-
sole commands.
•
Engineer user
- can use most of CLI commands without restriction. Cannot create or modify CLI users.
Cannot access console commands.
•
Super user
- can use all CLI commands without restriction. Can create or modify CLI users, changing their
passwords. Can access console commands without restriction.
The following table maps the user properties to the corresponding CLI credentials. User properties can be con-
figured via CLI commands by setting the
user access level
(default, engineer, administrator) and the
mayconfigure
flag (enabled, disabled)
access
level
mayConfigure
Allowed CLI operations
default
disabled
No access to CLI
default
enabled
Limited CLI commands access (only read operations)
engineer
disabled
No access to CLI
engineer
enabled
Full CLI commands access except user creation/modify
and debug console

Rate

4 / 5 based on 3 votes.

Popular Allied-Telesis Models

Famous Router IPs
Famous Router Companies
Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top