Clavister NetWall 6000 Series, Руководство по началу работы, Страница: 85 / 99

6. Secure the module by hand tightening the two screws on either side. These screws are on
springs and will first need to be pushed in to make contact with the thread in the chassis.
After hand tightening, finish by applying minimal extra tightening with a suitable
screwdriver to ensure the screws are secure.
7. Power up the hardware to restart cOS Core.
8. Check the Ethernet interface list in cOS Core through one of its management interfaces to
make sure the module's interfaces have been correctly added. As explained in detail below,
any new Ethernet interfaces will be automatically detected by cOS Core and will be added
to the configuration with a logical name derived from the chassis slot number and interface
position in the module.
The inserted module may be removed or swapped with a different expansion module by
following the same procedure.
Ethernet Interface and Address Object Naming in cOS Core
After startup, cOS Core will detect the presence of the extra interfaces and add them to the
configuration. No action from the administrator is needed for this to happen. The interfaces will
be named according to the slot they are in (some hardware products have more than one slot)
and their position on the expansion module.
The assigned interface name will always have the following form: En-m . The name always begins
with the letter E . The number n is the slot number and the number m is the position on the
expansion module. For example, the second interface of an expansion module in the first slot will
have the name
E1-2 .
For the NetWall 6000 Series, the slot numbers go from left to right when looking at the front of
the device. In other words, slot number
1 is the left hand slot.
cOS Core will also automatically add an IP and network address object into the configuration's
address book using the normal convention for interfaces. For example, the interface
E1-2 will get
an IPv4 address object called E1-2_ip and an IPv4 network object called E1-2_net .
Removing Interfaces
An expansion module can also be removed after powering off the NetWall 6000 Series. When
cOS Core is then started again, the cOS Core configuration will be unchanged. However, no data
can be received or sent on any Ethernet interfaces that do not physically exist. When details of
such a missing interface are displayed (for example, with the
show EthernetInterface CLI
command), the EthernetDriver value will be shown as NullEthernetDriver .
If another expansion module is then fitted later and it contains an Ethernet interface that has the
same internal bus position as the removed one (in other words, it's logical cOS Core name is the
same), traffic will be able to flow through that new interface since the configuration references
will now have a corresponding physical interface.
Installing SFP/SFP+ Modules
NetWall 6000 Series expansion module options can provide connectivity for Small Form
Pluggable (SFP) and Small Form Pluggable Plus (SFP+) modules. The NetWall 6000 Series does not
come as standard with any SFP or SFP+ modules included but these can be ordered separately
from a Clavister sales office.
Clavister does not use a vendor lock so other, third-party SFP/SFP+ modules could be used but
Chapter 6: Interface Expansion Modules
85