|  |  |  | miniSDH systems (<63E1, ETH & E1, V.35) | | |  |  | AN-miniSDH |
| | | Console cable is not working in Mini-SDH, what should I do now? |  | Versions of mini-SDH realeased after 2007 doesn't support F interface console at present. Please use NMS or telnet to management the equipment. |
| My customer has changed ip address now, and forgot it, so I can not access it by using NMS port. Now tell me that how can I reset the IP address? | | Mini-SDH has a special IP address: 192.192.192.192, and the subnet mask is 255.255.0.0 There are two way to change mini-SDH IP to this special IP. 1) There are 4 DIPs on the front panel. Put the 1st DIP swith to down status. Then mini-SDH will use the special IP. 2) Connect Orderwire phone to miniSDH, and pick up the phone. Then dial "*56#", the special IP will be enalbed. If you change the IP address or dial "*78#" or restart, the special IP will be disabled. When the special IP is enabled, you can telnet the mini-SDH and change a new IP for it through "setaddr" command. |
| Can I connect the miniSDH with any other vendor SDH product, like Huawei, Siemens, Lucent and others? | | Yes, AN-miniSDH is standard SDH multiplexer, and can be used with any other suppliers equipment |
| We successfully integrated our units with Lucent SDH, and E1's and Ethernet traffic is working fine. But, NMS information from Lucent SDH is not passing through AD-net node. Why? | | The mini-SDH occupy DCC channel(D1~D3) to transmit the NMS information, which is the same as Lucent muxes. For this application, I suggest the Lucent devices encapsulates NMS information in a VC-12 timeslot, then the VC-12 timeslot can pass through AN-miniSDH. |
| What is the switchover time for 1+1 optical uplink protection for STM-1 modules? | | The switch-over time of 1+1 protection is 33 ms, which is less than the international standard(50ms). |
| It's good for the suggestion with a changing IP adress, but what are default IP's you usually set at factory? | | 192.192.4.3 or 192.192.4.2 |
| I had done all the steps mentioned in manual for adding the new unit in AN-NM-VIEW, and can see the new area & unit. But I still can not access it, and can not see any alarms pulling out. | | For this problem, it seems that you had not set up Socket connection between NMS and the equipment, yet.
Please click on the “Connection setting and operations” as shown:
Then configuration the connection as followed: Note: the adapter IP is the address of NMS. 
Then click on “OK”. 
Then click on “Apply”, the configuration will be saved. And click on “Connect”, then NMS will connected to the equipment. |
| What is the total speed I can get on the 4 port and 2 port Ethernet modules? Is it more than 100 Mbit/s? | | Theoretically you should be able to reach about 155 Mbit/s but practical tests shows usually result about 135 Mbit/s. Roughly say, the total speed that can get is around: for one VC12, the data speed is around 2.15Mbit/s. So for your application, if you use 31 VC12 for one FE, the speed is about 66Mbit/s. if you use 32 VC12 (32=63-31) for one FE, the speed is about 69Mbit/s. The total speed is about 135Mbits. |
| Can the V.35 port support ITU-T V.54 remote loopback? | | No, it can not. But miniSDH can another various helpful loopbacks, please check manual for more details |
| | | | |  | | AN-CWDM-MUX modular access system
AN-CWDM-MUX modular access system dramatically saves dark fiber rental costs by multiplexing various traffic streams and protocols like 10/100/1000 Ethernet, E1, STM-1/4/16 and CATV using CWDM technology over same fiber. see more | | |
| | | | | 8 x E1 over IP 8 x E1 G.703 TDM over IP | E1 over IP | E1 to Ethernet converter |, for highest capacity - up to 8 E1 lines, with pure PRI/SS7 and GSM/CDMA related signalling supported. see more | | |
|
